WO2024244598A1 - Method for managing shared library, apparatus and electronic device - Google Patents

Abstract

Provided in the embodiments of the present application are a method for managing a shared library, an apparatus and an electronic device. The method, the apparatus and the electronic device can implement: when it is detected that version A of a first shared library is on release, determining whether version A of the first shared library is installed in a system; and, when it is determined that version A of the first shared library is not installed in the system, downloading version A of the first shared library, and can also implement: determining a third shared library list, the third shared library list comprising a shared library among full shared libraries on which an application does not depend, and/or an old-version shared library among the full shared libraries, and the full shared libraries comprising all shared libraries currently installed in the system; and uninstalling shared libraries in the third shared library list. As the shared library has a capability to be independently updated or uninstalled, the method, the apparatus and the electronic device can reduce the integration cost and the updating frequency of application developers for using shared libraries, and can also reduce occupancy of storage spaces.

Description

Method, device and electronic device for managing shared library

This application claims the priority of the Chinese patent application filed with the China Patent Office on May 26, 2023, with application number 202310612762.6 and application name “Method, device and electronic device for managing shared libraries”, the entire contents of which are incorporated by reference in this application.

Technical Field

Embodiments of the present application relate to the field of managing shared libraries, and more specifically, to a method, device, and electronic device for managing shared libraries.

Background Art

With the rapid iteration of the mobile Internet market, third-party application developers often use third-party code, such as shared libraries, in the development process in order to improve efficiency and reduce costs. Currently, shared library providers can provide the code capabilities of their own applications to third-party applications through dynamic loading, so that third-party applications do not need to integrate related content (including code, resources, etc.) in their own installation packages, thereby achieving the purpose of reducing the integration cost of third-party applications.

However, the current shared library cannot update itself, and all applications that rely on the shared library need to be updated and re-listed, which increases the cost of application integration. In addition, there is no effective uninstallation mechanism for multi-version shared libraries, and some redundant shared library versions stored in the system will take up a lot of storage space, resulting in a waste of storage space.

Summary of the invention

The present application provides a method, device and electronic device for managing shared libraries. Through the method, device and electronic device, the shared library has independent update or uninstall capabilities, and the system can automatically load the highest version of the shared library that it depends on when the application is started, so that the update of the shared library can be reflected in real time, which can reduce the integration cost and update frequency of the shared library used by application developers. The timely uninstallation of redundant shared libraries can also reduce the storage space occupied.

In a first aspect, a method for managing shared libraries is provided, the method comprising: when it is detected that version A of a first shared library is released, determining whether version A of the first shared library is installed in the system; when it is determined that version A of the first shared library is not installed in the system, downloading version A of the first shared library.

Among them, version A is the highest version of the first shared library.

In the embodiments of the present application, it is possible to update multiple versions of shared libraries, so that the shared libraries have independent update capabilities, lowering the development threshold for shared library providers, making shared libraries easier to manage and popularize, and also reducing the integration cost and update frequency of application developers when using shared libraries.

In combination with the first aspect, in a possible implementation, the method also includes: installing the Ath version of the first shared library; when it is detected that the first application is started, obtaining the Ath version of the first shared library to run the first application, and the first shared library is a shared library that the first application depends on.

When it is detected that the first application is started, the Ath version of the first shared library is obtained, which may be to obtain the shared library path of the Ath version of the first shared library, so that the first application uses the Ath version of the first shared library according to the shared library path of the Ath version of the first shared library.

In an embodiment of the present application, after completing the update of multiple versions of shared libraries, the system can automatically load the highest version of the shared library it depends on when the application starts, so that the update of the shared library can be reflected in real time, thereby reducing the integration cost and update frequency of application developers when using shared libraries.

In combination with the first aspect, in a possible implementation method, determining whether the Ath version of the first shared library is installed in the system includes: obtaining information about the first shared library, the information about the first shared library including information about one or more versions of the first shared library currently installed; and determining whether the Ath version of the first shared library is installed in the system based on the information about the first shared library.

In an embodiment of the present application, a method is provided in which an application market queries a system for information related to a shared library, which can realize the shared library information interaction between the application market and the system.

In conjunction with the first aspect, in a possible implementation manner, determining whether the Ath version of the first shared library is installed in the system includes: The application market obtains information about the highest version of the first shared library currently installed by querying the system; the application market determines whether the highest version is the Ath version based on the information about the highest version of the first shared library. If not, the application market determines that the Ath version of the first shared library is not installed in the system.

In an embodiment of the present application, another method is provided for an application market to query a system for information related to a shared library, which can realize the shared library information interaction between the application market and the system.

In combination with the first aspect, in a possible implementation method, determining whether the Ath version of the first shared library is installed in the system includes: the application market sends an inquiry message to the system, the inquiry message is used to inquire whether the system has installed the Ath version of the first shared library, the application market receives a reply message to the inquiry message, if the reply message is no, the application market determines that the Ath version of the first shared library is not installed in the system.

In an embodiment of the present application, another method is provided for an application market to query a system for information related to a shared library, which can realize the shared library information interaction between the application market and the system.

In combination with the first aspect, in a possible implementation method, whether the Ath version of the first shared library is installed in the system is determined based on the information of the first shared library, including: when the information of the first shared library does not include the Ath version of the first shared library, determining that the Ath version of the first shared library is not installed in the system.

In an embodiment of the present application, the information of the first shared library includes information of one or more versions of the first shared library currently installed in the system. After obtaining the information, the application market can further determine whether there is version A of the first shared library in the one or more versions of the first shared library currently installed in the system, and then determine whether version A of the first shared library is installed in the system.

In combination with the first aspect, in a possible implementation method, obtaining the information of the first shared library includes: the application market sends a first query message to the system, and the first query message is used to query the information of the first shared library; the application market receives a first reply message, and the first reply message includes the information of the first shared library.

In an embodiment of the present application, the system provides a query interface for the shared library version to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the shared library version information from the system.

In combination with the first aspect, in a possible implementation, the method also includes: determining a third shared library list, the third shared library list including shared libraries in the full shared library that are not dependent on the application, and/or the third shared library list includes lower version shared libraries in the full shared library, the shared libraries in the third shared library list are all in a currently non-running state, and the full shared library includes all shared libraries currently installed in the system; uninstalling the shared libraries in the third shared library list.

Optionally, each shared library in the full shared library has its own version identifier.

Among them, the low version shared library is a shared library that is not the highest version.

In the embodiment of the present application, the shared library has an independent uninstall capability, which lowers the development threshold for shared library providers and makes the shared library easier to manage and popularize; it can timely uninstall shared libraries that are not relied on by applications in the system and low-version shared libraries, which can reduce the storage space occupied in the system and thereby improve the user experience.

In combination with the first aspect, in a possible implementation, determining a third shared library list includes: obtaining information about the full shared library, the information about the full shared library including version information of each shared library in the full shared library, and/or the information about the full shared library including dependency information of each shared library in the full shared library, the dependency information being used to characterize whether a shared library is dependent on an application, or the dependency information being used to characterize which applications depend on a shared library; determining a fourth shared library list based on the information about the full shared library, the fourth shared library list including shared libraries in the full shared library that are not dependent on an application, and/or the fourth shared library list including lower-version shared libraries in the full shared library; obtaining running information of each shared library in the fourth shared library list, the running information being used to characterize whether a shared library is currently in a running state; determining the third shared library list based on the running information, the third shared library list including shared libraries in the fourth shared library list that are not currently running.

Among them, optionally, the information of the full shared library is obtained at a first time, and the first time may be a periodic time, for example: it may be 22:00 every night, or 2:00 every morning, or every 30 hours, or any other periodic time; the first time may also be a time triggered by a user operation, or a time automatically determined by the system according to the current storage or operation status of the device, and the present application does not limit this.

In an embodiment of the present application, the application market can obtain version information and operation information of all shared libraries from the system, and then determine a list of shared libraries that need to be uninstalled, so as to facilitate subsequent uninstallation of the shared libraries in the shared library list.

In combination with the first aspect, in a possible implementation method, obtaining the information of the full shared library includes: the application market sends a second query message to the system, and the second query message is used to query the information of the full shared library; the application market receives a second reply message, and the second reply message includes the information of the full shared library.

In an embodiment of the present application, the system provides a query interface for the full shared library information to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the full shared library information from the system.

In combination with the first aspect, in a possible implementation method, obtaining the operating information of each shared library in the fourth shared library list includes: the application market sends a third query message to the system, and the third query message is used to query the operating information of each shared library in the fourth shared library list; the application market receives a third reply message, and the third reply message is used to indicate the operating information of each shared library in the fourth shared library list.

In an embodiment of the present application, the system provides the application market with a query interface for the running information of the shared library, so that the application market can implement information interaction with the system through the query interface, and then obtain the running information of the shared library from the system.

In combination with the first aspect, in a possible implementation, the full shared library includes the first version of the first shared library and the Ath version of the first shared library, the Ath version of the first shared library is the highest version of the first shared library, and the method also includes: when the first version of the first shared library is uninstalled, pointing the shared library version that the first application depends on to the Ath version of the first shared library.

Uninstalling the first version of the first shared library includes: deleting path information of the first version of the first shared library.

Among them, pointing the shared library version that the first application depends on to the Ath version of the first shared library can be understood as modifying the dependency of the first application, that is, changing the dependency of the first application from relying on the first version of the first shared library to relying on the Ath version of the first shared library.

In another possible implementation parallel to this embodiment, when the first version of the first shared library is uninstalled, the system does not modify the dependency of the first application, but obtains the Ath version of the first shared library each time the first application is started.

In an embodiment of the present application, when the shared library version used by an application is uninstalled, the shared library version used by the application automatically points to a higher version of the shared library. In this way, when the application is started, the higher version of the shared library is automatically enabled, and the application will not run abnormally due to the uninstallation of the shared library version, thereby improving the user experience.

In combination with the first aspect, in a possible implementation, the method also includes: in response to a user operation of installing or updating the first application, obtaining a first shared library list that the first application depends on, the first shared library list including M shared libraries, where M is a positive integer greater than or equal to 1; determining a second shared library list based on the installation status of the M shared libraries, the second shared library list including uninstalled shared libraries among the M shared libraries; installing the shared libraries in the second shared library list, and installing or updating the first application.

In the embodiment of the present application, the shared library and the third-party application can be installed together, so that the application can always have the shared library it depends on, which can reduce the occurrence of application operation failures and improve the user experience.

In combination with the first aspect, in a possible implementation, before determining the second shared library list based on the installation status of the M shared libraries, the method also includes: the application market sends a fourth query message to the system, and the fourth query message is used to query the installation status of the M shared libraries; the application market receives a fourth reply message, and the fourth reply message is used to indicate the installation status of the M shared libraries.

In an embodiment of the present application, the system provides a query interface for the installation information of the shared library to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the installation information of the shared library from the system.

In combination with the first aspect, in a possible implementation manner, installing the shared libraries in the second shared library list includes: installing each shared library in the second shared library list in different paths respectively.

In an embodiment of the present application, when the system installs different versions of shared libraries, it will install different versions of shared libraries in different version paths according to the version numbers. In this way, different versions of shared libraries can be relatively independent of each other, different versions of the same shared library can be treated as different applications, and operations such as updating or uninstalling a specific version of the shared library can be implemented.

In a second aspect, a method for managing shared libraries is provided, the method comprising: determining a third shared library list, the third shared library list including shared libraries in the full shared library that are not dependent on applications, and/or the third shared library list including lower version shared libraries in the full shared library, the full shared library including all shared libraries currently installed in the system; uninstalling shared libraries in the third shared library list, the shared libraries in the third shared library list are all in a currently non-running state.

Optionally, each shared library in the full shared library has its own version identifier.

In the embodiment of the present application, the shared library has an independent uninstall capability, which lowers the development threshold for shared library providers and makes the shared library easier to manage and popularize; it can timely uninstall shared libraries that are not relied on by applications in the system and low-version shared libraries, which can reduce the storage space occupied in the system and thereby improve the user experience.

In combination with the second aspect, in a possible implementation, determining a third shared library list includes: obtaining information about the full shared library, the information about the full shared library including version information of each shared library in the full shared library, and/or the information about the full shared library including dependency information of each shared library in the full shared library, the dependency information being used to characterize whether a shared library is dependent on an application, or the dependency information being used to characterize which applications depend on a shared library; determining a fourth shared library list based on the information about the full shared library, the fourth shared library list including The fourth shared library list includes the shared libraries in the full shared library that are not depended on by the application, and/or the fourth shared library list includes the lower version shared libraries in the full shared library; the running information of each shared library in the fourth shared library list is obtained, and the running information is used to indicate whether the shared library is currently in a running state; the third shared library list is determined according to the running information, and the third shared library list includes the shared libraries in the fourth shared library list that are not currently running.

Among them, optionally, the information of the full shared library is obtained at a first time, and the first time may be a periodic time, for example: it may be 22:00 every night, or 2:00 every morning, or every 30 hours, or any other periodic time; the first time may also be a time triggered by a user operation, or a time automatically determined by the system according to the current storage or operation status of the device, and the present application does not limit this.

In an embodiment of the present application, the application market can obtain version information and operation information of all shared libraries from the system, and then determine a list of shared libraries that need to be uninstalled, so as to facilitate subsequent uninstallation of the shared libraries in the shared library list.

In combination with the second aspect, in a possible implementation method, obtaining the information of the full shared library includes: the application market sends a second query message to the system, and the second query message is used to query the information of the full shared library; the application market receives a second reply message, and the second reply message includes the information of the full shared library.

In an embodiment of the present application, the system provides a query interface for the full shared library information to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the full shared library information from the system.

In combination with the second aspect, in a possible implementation method, obtaining the operating information of each shared library in the fourth shared library list includes: the application market sends a third query message to the system, and the third query message is used to query the operating information of each shared library in the fourth shared library list; the application market receives a third reply message, and the third reply message is used to indicate the operating information of each shared library in the fourth shared library list.

In an embodiment of the present application, the system provides the application market with a query interface for the running information of the shared library, so that the application market can implement information interaction with the system through the query interface, and then obtain the running information of the shared library from the system.

In combination with the second aspect, in a possible implementation, the full shared library includes the first version of the first shared library and the Ath version of the first shared library, and the Ath version of the first shared library is the highest version of the first shared library. The method also includes: when uninstalling the first version of the first shared library, pointing the shared library version that the first application depends on to the Ath version of the first shared library, and the first shared library is the shared library that the first application depends on.

Uninstalling the first version of the first shared library includes: deleting path information of the first version of the first shared library.

Among them, pointing the shared library version that the first application depends on to the Ath version of the first shared library can be understood as modifying the dependency of the first application, that is, changing the dependency of the first application from relying on the first version of the first shared library to relying on the Ath version of the first shared library.

In another possible implementation parallel to this embodiment, when the first version of the first shared library is uninstalled, the system does not modify the dependency of the first application, but obtains the Ath version of the first shared library each time the first application is started.

In an embodiment of the present application, when the shared library version used by an application is uninstalled, the shared library version used by the application automatically points to a higher version of the shared library. In this way, when the application is started, the higher version of the shared library is automatically enabled, and the application will not run abnormally due to the uninstallation of the shared library version, thereby improving the user experience.

In combination with the second aspect, in a possible implementation, the method also includes: in response to a user's operation of installing or updating the first application, obtaining a first shared library list that the first application depends on, the first shared library list including M shared libraries, where M is a positive integer greater than or equal to 1; determining a second shared library list based on the installation status of the M shared libraries, the second shared library list including uninstalled shared libraries among the M shared libraries; installing the shared libraries in the second shared library list, and installing or updating the first application.

In the embodiment of the present application, the shared library and the third-party application can be installed together, so that the application can always have the shared library it depends on, which can reduce the occurrence of application operation failures and improve the user experience.

In combination with the second aspect, in a possible implementation, before determining the second shared library list based on the installation status of the M shared libraries, the method also includes: the application market sends a fourth query message to the system, and the fourth query message is used to query the installation status of the M shared libraries; the application market receives a fourth reply message, and the fourth reply message is used to indicate the installation status of the M shared libraries.

In an embodiment of the present application, the system provides a query interface for the installation information of the shared library to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the installation information of the shared library from the system.

In conjunction with the second aspect, in a possible implementation manner, installing the shared libraries in the second shared library list includes: installing each shared library in the second shared library list in a different path.

In the embodiment of the present application, when the system installs different versions of shared libraries, it will install different versions of shared libraries in different folders according to the version number. Under the version path, different versions of shared libraries can be relatively independent of each other, different versions of the same shared library can be treated as different applications, and operations such as updating or uninstalling a specific version of the shared library can be implemented.

In a third aspect, a device for managing shared libraries is provided, the device comprising: a judgment module, for judging whether the Ath version of the first shared library is installed in the system when it is detected that the Ath version of the first shared library is put on the shelf; and a download module, for downloading the Ath version of the first shared library when it is determined that the Ath version of the first shared library is not installed in the system.

Among them, version A is the highest version of the first shared library.

In the embodiments of the present application, it is possible to update multiple versions of shared libraries, so that the shared libraries have independent update capabilities, lowering the development threshold for shared library providers, making shared libraries easier to manage and popularize, and also reducing the integration cost and update frequency of application developers when using shared libraries.

In combination with the third aspect, in a possible implementation, the device also includes: an installation module for installing the Ath version of the first shared library; an acquisition module for acquiring the Ath version of the first shared library when it is detected that the first application is started, so as to run the first application, and the first shared library is a shared library that the first application depends on.

When it is detected that the first application is started, the acquisition module acquires the Ath version of the first shared library. The acquisition module may acquire the shared library path of the Ath version of the first shared library so that the first application uses the Ath version of the first shared library according to the shared library path of the Ath version of the first shared library.

In an embodiment of the present application, after completing the update of multiple versions of shared libraries, the system can automatically load the highest version of the shared library it depends on when the application starts, so that the update of the shared library can be reflected in real time, thereby reducing the integration cost and update frequency of application developers when using shared libraries.

In combination with the third aspect, in a possible implementation method, the acquisition module is used to obtain information about the first shared library, and the information about the first shared library includes information about one or more versions of the first shared library that are currently installed; the judgment module is specifically used to: judge whether version A of the first shared library is installed in the system based on the information about the first shared library.

In an embodiment of the present application, a device is provided for an application market to query a system for information related to a shared library, which can realize the shared library information interaction between the application market and the system.

In combination with the third aspect, in a possible implementation method, the acquisition module is used to obtain information about the highest version of the first shared library currently installed by querying the system; the judgment module is specifically used to: determine whether the highest version is the Ath version based on the information of the highest version of the first shared library; if not, the determination module included in the device determines that the Ath version of the first shared library is not installed in the system.

In an embodiment of the present application, another device is provided for the application market to query the system for information related to the shared library, which can realize the shared library information interaction between the application market and the system.

In combination with the third aspect, in a possible implementation, the device also includes a transceiver module for sending an inquiry message to the system, wherein the inquiry message is used to inquire whether the system has installed the Ath version of the first shared library, and the transceiver module is also used to receive a reply message to the inquiry message, and a determination module for determining that the Ath version of the first shared library is not installed in the system when the reply message is no.

In an embodiment of the present application, another device is provided for the application market to query the system for information related to the shared library, which can realize the shared library information interaction between the application market and the system.

In combination with the third aspect, in a possible implementation, the judgment module is specifically used to: when the information of the first shared library does not include the information of the Ath version of the first shared library, determine that the Ath version of the first shared library is not installed in the system.

In an embodiment of the present application, the information of the first shared library includes information of one or more versions of the first shared library currently installed in the system. After obtaining the information, the application market can further determine whether there is version A of the first shared library in the one or more versions of the first shared library currently installed in the system, and then determine whether version A of the first shared library is installed in the system.

In combination with the third aspect, in a possible implementation, the transceiver module is also used to send a first query message to the system, and the first query message is used to query the information of the first shared library; the transceiver module is also used to receive a first reply message, and the first reply message includes the information of the first shared library.

In an embodiment of the present application, the system provides a query interface for the shared library version to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the shared library version information from the system.

In combination with the third aspect, in a possible implementation, the determination module is also used to: determine a third shared library list, the third shared library list includes shared libraries in the full shared library that are not dependent on the application, and/or the third shared library list includes lower version shared libraries in the full shared library, the shared libraries in the third shared library list are all in a currently non-running state, and the full shared library includes all shared libraries currently installed in the system; the device also includes an uninstall module for uninstalling the shared libraries in the third shared library list.

Optionally, each shared library in the full shared library has its own version identifier.

Among them, the low version shared library is a shared library that is not the highest version.

In the embodiment of the present application, the shared library has an independent uninstall capability, which lowers the development threshold for shared library providers and makes the shared library easier to manage and popularize; it can timely uninstall shared libraries that are not relied on by applications in the system and low-version shared libraries, which can reduce the storage space occupied in the system and thereby improve the user experience.

In combination with the third aspect, in a possible implementation, the acquisition module is also used to: obtain information about the full shared library, the information about the full shared library includes version information of each shared library in the full shared library, and/or the information about the full shared library includes dependency information of each shared library in the full shared library, the dependency information is used to characterize whether the shared library is dependent on the application, or the dependency information is used to characterize which applications depend on the shared library; determine a fourth shared library list based on the information about the full shared library, the fourth shared library list includes shared libraries in the full shared library that are not dependent on the application, and/or the fourth shared library list includes lower-version shared libraries in the full shared library; obtain running information of each shared library in the fourth shared library list, the running information is used to characterize whether the shared library is currently in a running state; the determination module is specifically used to: determine the third shared library list based on the running information, the third shared library list includes shared libraries in the fourth shared library list that are not currently running.

Among them, optionally, the acquisition module acquires the information of the full shared library at a first time, and the first time may be a periodic time, for example: it may be 22:00 every night, or 2:00 every morning, or every 30 hours, or any other periodic time; the first time may also be a time triggered by a user operation, or a time automatically determined by the system according to the current storage or operation status of the device, and the present application does not limit this.

In an embodiment of the present application, the application market can obtain version information and operation information of all shared libraries from the system, and then determine a list of shared libraries that need to be uninstalled, so as to facilitate subsequent uninstallation of the shared libraries in the shared library list.

In combination with the third aspect, in a possible implementation, the transceiver module is also used to: send a second query message to the system, the second query message is used to query the information of the full shared library; receive a second reply message, the second reply message includes the information of the full shared library.

In an embodiment of the present application, the system provides the application market with a query interface for information of the full shared library, so that the application market can implement information interaction with the system through the query interface, and then obtain the full shared library information from the system.

In combination with the third aspect, in a possible implementation method, the transceiver module is also used to: send a third query message to the system, the third query message is used for the operation information of each shared library in the fourth shared library list; receive a third reply message, the third reply message is used to indicate the operation information of each shared library in the fourth shared library list.

In an embodiment of the present application, the system provides the application market with a query interface for the running information of the shared library, so that the application market can implement information interaction with the system through the query interface, and then obtain the running information of the shared library from the system.

In combination with the third aspect, in a possible implementation, the full shared library includes the first version of the first shared library and the Ath version of the first shared library, the Ath version of the first shared library being the highest version of the first shared library, and the device also includes: a pointing module, used to point the shared library version on which the first application depends to the Ath version of the first shared library when the first version of the first shared library is uninstalled.

Uninstalling the first version of the first shared library includes: deleting path information of the first version of the first shared library.

Among them, the pointing module points the shared library version on which the first application depends to the Ath version of the first shared library, which can be understood as the pointing module modifying the dependency of the first application, that is, changing the dependency of the first application from the first version depending on the first shared library to the Ath version depending on the first shared library.

In another possible implementation parallel to this embodiment, when the first version of the first shared library is uninstalled, the dependency of the first application is not modified, but the Ath version of the first shared library is acquired through the acquisition module each time the first application is started.

In an embodiment of the present application, when the shared library version used by an application is uninstalled, the shared library version used by the application automatically points to a higher version of the shared library. In this way, when the application is started, the higher version of the shared library is automatically enabled, and the application will not run abnormally due to the uninstallation of the shared library version, thereby improving the user experience.

In combination with the third aspect, in a possible implementation, the acquisition module is also used to: in response to a user's operation of installing or updating the first application, obtain a first shared library list that the first application depends on, the first shared library list including M shared libraries, M being a positive integer greater than or equal to 1; the determination module is also used to: determine a second shared library list based on the installation status of the M shared libraries, the second shared library list including uninstalled shared libraries among the M shared libraries; the installation module is also used to: install the shared libraries in the second shared library list, and install or update the first application.

In the embodiment of the present application, the shared library and the third-party application can be installed together, so that the application can always have the shared library it depends on, which can reduce the occurrence of application operation failures and improve the user experience.

In conjunction with the third aspect, in a possible implementation, the transceiver module is further used to: send a fourth query message to the system, the fourth query message A query message is used to query the installation status of the M shared libraries; and a fourth reply message is received, where the fourth reply message is used to indicate the installation status of the M shared libraries.

In an embodiment of the present application, the system provides a query interface for the installation information of the shared library to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the installation information of the shared library from the system.

In conjunction with the third aspect, in a possible implementation manner, the installation module is specifically configured to: install each shared library in the second shared library list in different paths respectively.

In an embodiment of the present application, when the system installs different versions of shared libraries, it will install different versions of shared libraries in different version paths according to the version numbers. In this way, different versions of shared libraries can be relatively independent of each other, different versions of the same shared library can be treated as different applications, and operations such as updating or uninstalling a specific version of the shared library can be implemented.

In a fourth aspect, a device for managing shared libraries is provided, the device comprising: a determination module, used to determine a third shared library list, the third shared library list including shared libraries in the full shared library that are not dependent on applications, and/or the third shared library list including lower version shared libraries in the full shared library, the full shared library including all shared libraries currently installed in the system; an uninstallation module, used to uninstall shared libraries in the third shared library list, the shared libraries in the third shared library list are all in a currently non-running state.

Optionally, each shared library in the full shared library has its own version identifier.

In the embodiment of the present application, the shared library has an independent uninstall capability, which lowers the development threshold for shared library providers and makes the shared library easier to manage and popularize; it can timely uninstall shared libraries that are not relied on by applications in the system and low-version shared libraries, which can reduce the storage space occupied in the system and thereby improve the user experience.

In combination with the fourth aspect, in a possible implementation, the device also includes an acquisition module, which is used to obtain information about the full shared library, the information about the full shared library includes version information of each shared library in the full shared library, and/or the information about the full shared library includes dependency information of each shared library in the full shared library, the dependency information is used to characterize whether the shared library is dependent on the application, or the dependency information is used to characterize which applications depend on the shared library; a fourth shared library list is determined based on the information about the full shared library, the fourth shared library list includes shared libraries in the full shared library that are not dependent on the application, and/or the fourth shared library list includes low-version shared libraries in the full shared library; the acquisition module is also used to obtain running information of each shared library in the fourth shared library list, the running information is used to characterize whether the shared library is currently in a running state; the determination module is specifically used to: determine the third shared library list based on the running information, the third shared library list includes shared libraries in the fourth shared library list that are not currently running.

Among them, optionally, the acquisition module acquires the information of the full shared library at a first time, and the first time may be a periodic time, for example: it may be 22:00 every night, or 2:00 every morning, or every 30 hours, or any other periodic time; the first time may also be a time triggered by a user operation, or a time automatically determined by the system according to the current storage or operation status of the device, and the present application does not limit this.

In an embodiment of the present application, the application market can obtain version information and operation information of all shared libraries from the system, and then determine a list of shared libraries that need to be uninstalled, so as to facilitate subsequent uninstallation of the shared libraries in the shared library list.

In combination with the fourth aspect, in a possible implementation, the device also includes a transceiver module, which is used to send a second query message to the system, and the second query message is used to query the information of the full shared library; and is also used to receive a second reply message, and the second reply message includes the information of the full shared library.

In an embodiment of the present application, the system provides a query interface for the full shared library information to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the full shared library information from the system.

In combination with the fourth aspect, in a possible implementation method, the transceiver module is also used to: send a third query message to the system, the third query message is used for the operation information of each shared library in the fourth shared library list; receive a third reply message, the third reply message is used to indicate the operation information of each shared library in the fourth shared library list.

In an embodiment of the present application, the system provides the application market with a query interface for the running information of the shared library, so that the application market can implement information interaction with the system through the query interface, and then obtain the running information of the shared library from the system.

In combination with the fourth aspect, in a possible implementation, the full shared library includes the first version of the first shared library and the Ath version of the first shared library, and the Ath version of the first shared library is the highest version of the first shared library. The device also includes: a pointing module, which is used to point the shared library version on which the first application depends to the Ath version of the first shared library when uninstalling the first version of the first shared library, and the first shared library is the shared library on which the first application depends.

Uninstalling the first version of the first shared library includes: deleting path information of the first version of the first shared library.

The pointing module points the shared library version that the first application depends on to the Ath version of the first shared library, which can be understood as the pointing module modifying the dependency of the first application, that is, changing the dependency of the first application from the first version of the first shared library to the Ath version of the first shared library. Version A of a shared library.

In another possible implementation parallel to this embodiment, when the first version of the first shared library is uninstalled, the dependency of the first application is not modified, but the Ath version of the first shared library is acquired through the acquisition module each time the first application is started.

In an embodiment of the present application, when the shared library version used by an application is uninstalled, the shared library version used by the application automatically points to a higher version of the shared library. In this way, when the application is started, the higher version of the shared library is automatically enabled, and the application will not run abnormally due to the uninstallation of the shared library version, thereby improving the user experience.

In combination with the fourth aspect, in a possible implementation, the acquisition module is also used to: in response to a user's operation of installing or updating the first application, obtain a first shared library list that the first application depends on, the first shared library list including M shared libraries, M being a positive integer greater than or equal to 1; the determination module is also used to: determine a second shared library list based on the installation status of the M shared libraries, the second shared library list including uninstalled shared libraries among the M shared libraries; the device also includes an installation module for installing the shared libraries in the second shared library list, and installing or updating the first application.

In the embodiment of the present application, the shared library and the third-party application can be installed together, so that the application can always have the shared library it depends on, which can reduce the occurrence of application operation failures and improve the user experience.

In combination with the fourth aspect, in a possible implementation method, the transceiver module is also used to: send a fourth query message to the system, the fourth query message is used to query the installation status of the M shared libraries; receive a fourth reply message, the fourth reply message is used to indicate the installation status of the M shared libraries.

In an embodiment of the present application, the system provides a query interface for the installation information of the shared library to the application market, so that the application market can implement information interaction with the system through the query interface, and then obtain the installation information of the shared library from the system.

In conjunction with the fourth aspect, in a possible implementation manner, the installation module is specifically used to: install each shared library in the second shared library list in different paths respectively.

In an embodiment of the present application, when the system installs different versions of shared libraries, it will install different versions of shared libraries in different version paths according to the version numbers. In this way, different versions of shared libraries can be relatively independent of each other, different versions of the same shared library can be treated as different applications, and operations such as updating or uninstalling a specific version of the shared library can be implemented.

In a fifth aspect, an electronic device is provided, comprising a memory and a processor, wherein the memory is used to store computer program code, and the processor is used to execute the computer program code stored in the memory to implement the method in the above-mentioned first aspect or any possible implementation of the first aspect, or to implement the above-mentioned second aspect or any possible implementation of the second aspect.

In a sixth aspect, a computer-readable storage medium is provided, in which a computer program or instruction is stored. When the computer program or instruction is executed, the method in the first aspect or any possible implementation of the first aspect is implemented, or the method in the second aspect or any possible implementation of the second aspect is implemented.

In the seventh aspect, a chip is provided, in which instructions are stored. When the chip is executed on a device, the chip executes the method in the first aspect or any possible implementation of the first aspect, or executes the method in the second aspect or any possible implementation of the second aspect.

In an eighth aspect, a computer program product is provided, which includes a computer program code. When the computer program code runs on a computer, it implements the method in the first aspect or any possible implementation of the first aspect, or implements the method in the second aspect or any possible implementation of the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

FIG2 is a software structure block diagram of an electronic device provided in an embodiment of the present application;

FIG3 is a schematic flow chart of a method for managing a shared library provided in an embodiment of the present application;

FIG4 is a schematic flow chart of another method for managing a shared library provided in an embodiment of the present application;

FIG5 is a schematic flow chart of a method for synchronously installing a shared library and an application provided in an embodiment of the present application;

6 is a schematic flow chart of a method for installing a multi-version shared library provided in an embodiment of the present application;

FIG7 is a schematic flow chart of a method for updating a shared library provided in an embodiment of the present application;

FIG8 is a schematic flow chart of a method for uninstalling a shared library provided in an embodiment of the present application;

FIG9 is a schematic flow chart of another method for uninstalling a shared library provided in an embodiment of the present application;

FIG10 is a schematic flow chart of another method for updating a shared library provided in an embodiment of the present application;

FIG11 is a schematic flow chart of a method for updating and uninstalling a shared library provided in an embodiment of the present application;

12 is a schematic diagram of functional modules of a device for synchronously installing an application and a shared library provided in an embodiment of the present application;

13 is a schematic diagram of functional modules of a device for updating a shared library provided in an embodiment of the present application;

FIG. 14 is a schematic diagram of functional modules of a device for unloading a shared library provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solution in the present application will be described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" or "multiple" refers to two or more than two.

In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

The terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "one", "a kind of", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one, two or more. The term "and/or" is used to describe 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, where A and B can be singular or plural. The character "/" generally indicates that the objects associated before and after are in an "or" relationship.

References to "one embodiment" or "some embodiments" etc. described in this specification mean that a particular feature, structure or characteristic described in conjunction with the embodiment is included in one or more embodiments of the present application. Thus, the phrases "one embodiment", "some embodiments", "another embodiment", "some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

The method provided in the embodiments of the present application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR)/virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), etc. The embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

Below, some terms involved in the embodiments of the present application are first introduced in detail.

1. Shared Libraries

A shared library is a library of shared functions that applications can link to at runtime, rather than at compile time. In Windows, shared libraries are called dynamic link libraries; in Mac OS X, they are called frameworks; in Linux, they are called shared objects.

Exemplarily, FIG1 shows a schematic diagram of the structure of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor. processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and/or neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (SIM) interface, and/or a universal serial bus (USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, thereby realizing the touch function of the electronic device 100.

The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to achieve communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to realize the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the electronic device 100.

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

The USB interface 130 is an interface that complies with the USB standard specification, and can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and a peripheral device. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The charging management module 140 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it can also power the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

The mobile communication module 150 can provide solutions for wireless communications including 2G/3G/4G/5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) and the like applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering processing, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of the signal, amplify the signal, and convert it into electromagnetic waves for radiation through the antenna 2.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and/or a satellite based augmentation system (SBAS).

The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light-emitting diode (OLED), or a display panel. Light emitting diode or active-matrix organic light emitting diode (AMOLED), flexible light emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light emitting diodes (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise, brightness, and skin color of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, ISP can be set in camera 193.

The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an App required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

The electronic device 100 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to microphone 170C to input the sound signal into microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

The earphone interface 170D is used to connect a wired earphone. The earphone interface 170D may be the USB interface 130, or may be a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 can also calculate the touch position according to the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

The gyro sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyro sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, the flip cover can be automatically unlocked.

The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in all directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

The distance sensor 180F is used to measure the distance. The electronic device 100 can measure the distance by infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 performs a boost on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

The touch sensor 180K is also called a "touch panel". The touch sensor 180K can be set on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.

The bone conduction sensor 180M can obtain a vibration signal. In some embodiments, the bone conduction sensor 180M can obtain a vibration signal of a vibrating bone block of the vocal part of the human body. The bone conduction sensor 180M can also contact the human pulse to receive a blood pressure beat signal. In some embodiments, the bone conduction sensor 180M can also be set in an earphone and combined into a bone conduction earphone. The audio module 170 can parse out a voice signal based on the vibration signal of the vibrating bone block of the vocal part obtained by the bone conduction sensor 180M to realize a voice function. The application processor can parse the heart rate information based on the blood pressure beat signal obtained by the bone conduction sensor 180M to realize a heart rate detection function.

The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an embedded SIM (eSIM) card, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

It should be understood that the phone cards in the embodiments of the present application include but are not limited to SIM cards, eSIM cards, universal subscriber identity modules (USIM), universal integrated circuit cards (UICC), and the like.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.

FIG2 is a software structure diagram of the electronic device 100 of an embodiment of the present application. The layered architecture divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. The application layer can include a series of application packages.

As shown in FIG. 2 , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

The application framework layer provides application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

As shown in FIG. 2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including connecting, hanging up, etc.).

The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

Android Runtime includes core libraries and virtual machines. Android Runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library can include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

A 2D graphics engine is a drawing engine for 2D drawings.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

It should be understood that the technical solutions in the embodiments of the present application can be used in Android, IOS, Hongmeng and other systems.

The technical solution of the embodiment of the present application can be applied to electronic devices.

The electronic device in the embodiments of the present application may be a television, a desktop computer, a laptop computer, or a portable electronic device such as a mobile phone, a tablet computer, a camera, a camcorder, a video recorder, or other electronic devices with storage functions, electronic devices in a 5G network, or electronic devices in a future evolving public land mobile communication network (public land mobile network, PLMN), etc., and the present application does not limit this.

With the rapid iteration of the mobile Internet market, third-party application developers often use third-party code, such as shared libraries, in the development process in order to improve efficiency and reduce costs. Currently, shared library providers can provide the code capabilities of their own applications to third-party applications through dynamic loading, so that third-party applications do not need to integrate related content (including code, resources, etc.) in their own installation packages, thereby achieving the purpose of reducing the integration cost of third-party applications.

At present, the shared library in the device is different from the overall process of the application. The shared library does not have the mechanism of application installation, and the shared library cannot be updated. For example, when there is a problem with the shared library version 1.0, the shared library cannot solve the problem by updating the 1.1 version like the application. Instead, all applications that rely on the shared library need to be updated and re-updated to the update shelf to solve the problem, which will increase the integration cost of the application. In addition, when there are multiple versions of the same shared library in the system that are backward compatible, multiple low-version shared libraries are subsets of the highest-version shared library. Only the highest-version shared library is required to meet the application requirements. Since there is no effective uninstallation mechanism for shared libraries, undepended shared libraries and low-version shared libraries are still stored in the system, occupying storage space and causing a waste of storage space. In addition, there is no effective mechanism in the system to detect whether a shared library exists and to install a shared library together with a third-party application. This will cause the third-party application to fail to install when the dependent shared library does not exist in the system, thereby affecting the user experience.

In view of this, the embodiments of the present application provide a method, device and electronic device for managing shared libraries. The method can realize the application of shared libraries through collaboration between subjects such as mobile phone systems, application markets and cloud, so that shared libraries have the ability to be independently developed, distributed, installed, updated or uninstalled, which reduces the development threshold of shared library providers and makes shared libraries easy to manage and popularize; moreover, multiple versions of shared libraries can exist in the system, and the highest version of the shared library is automatically enabled when the application is started, so that the update of the shared library can be reflected in real time, reducing the integration cost and update frequency of application developers when using shared libraries; in addition, the method can realize the joint installation of shared libraries and third-party applications through the collaboration between the system framework and the application market, and can also uninstall shared libraries that are not relied on by applications and low-version shared libraries at specific times, thereby improving user experience and reducing storage space occupied in the system.

Exemplarily, Fig. 3 shows a schematic flow chart of a method 300 for managing a shared library provided in an embodiment of the present application. As shown in Fig. 3, the method 300 includes:

S301: When it is detected that the Ath version of the first shared library is released, determining whether the Ath version of the first shared library is installed in the system;

S302: When it is determined that the Ath version of the first shared library is not installed in the system, download the Ath version of the first shared library.

Among them, version A is the highest version of the first shared library.

S303: Install the Ath version of the first shared library;

S304: When it is detected that the first application is started, the Ath version of the first shared library is obtained to run the first application, and the first shared library is a shared library that the first application depends on.

When it is detected that the first application is started, the Ath version of the first shared library is obtained, which may be to obtain the shared library path of the Ath version of the first shared library, so that the first application uses the Ath version of the first shared library according to the shared library path of the Ath version of the first shared library. Version A.

Among them, step S301 and step S302 are executed on the application market side; step S303 and step S304 are executed on the system side.

In one possible implementation, determining whether version A of the first shared library is installed in the system includes: the application market obtains information about the highest version of the first shared library currently installed by querying the system; the application market determines whether the highest version is version A based on the information about the highest version of the first shared library; if not, the application market determines that version A of the first shared library is not installed in the system.

In another possible implementation, determining whether version A of the first shared library is installed in the system includes: the application market sends an inquiry message to the system, the inquiry message is used to inquire whether the system has installed version A of the first shared library, the application market receives a reply message to the inquiry message, if the reply message is no, the application market determines that version A of the first shared library is not installed in the system.

Exemplarily, Fig. 4 shows a schematic flow chart of another method 400 for managing a shared library provided in an embodiment of the present application. As shown in Fig. 4, the method 400 includes:

S401: Determine a third shared library list.

The third shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the third shared library list includes lower-version shared libraries in the full shared library, and the full shared library includes all shared libraries currently installed in the system.

In one implementation, determining the third shared library list includes: obtaining information of the full shared library, the information of the full shared library including version information of each shared library in the full shared library, and/or including dependency information of each shared library in the full shared library.

The dependency information is used to indicate whether the shared library is dependent on the application, or the dependency information is used to indicate which applications depend on the shared library.

Among them, optionally, the information of the full shared library is obtained at a first time, and the first time may be a periodic time, for example: it may be 22:00 every night, or 2:00 every morning, or every 30 hours, or any other periodic time; the first time may also be a time triggered by a user operation, or a time automatically determined by the system according to the current storage or operation status of the device, and the present application does not limit this.

In some embodiments, all shared libraries in the third shared library list are currently not running. Specifically, the step of determining the third shared library list may be:

(1) Acquire information of a full shared library, where the information of the full shared library includes version information of each shared library in the full shared library and/or dependency information of each shared library in the full shared library.

(2) determining a fourth shared library list based on information of the full shared library, wherein the fourth shared library list includes shared libraries in the full shared library that are not depended on by applications, and/or the third shared library list includes lower-version shared libraries in the full shared library, and the current running status of the shared libraries in the fourth shared library list is unknown.

(3) Obtaining running information of each shared library in the fourth shared library list, where the running information is used to indicate whether the shared library is currently in a running state.

(4) Determine a third shared library list, where the third shared library list includes the currently non-running shared libraries in the fourth shared library list.

S402: Uninstall the shared libraries in the third shared library list.

Optionally, each shared library in the full shared library has its own version identifier.

For example, FIG5 shows a schematic flow chart of a method 500 for synchronously installing a shared library and an application provided in an embodiment of the present application. As shown in FIG5 , the method 500 includes:

S501: In response to a user's operation of installing/updating a first application, the application market downloads an installation package of the first application and obtains a first shared library list on which the first application depends.

Optionally, the application market downloads the installation package of the first application from the cloud and parses a configuration file in the installation package of the first application to obtain a first shared library list on which the first application depends.

Among them, the first shared library list that the first application depends on includes one or more shared libraries that the first application depends on, and the one or more shared libraries carry version information. That is to say, the first shared library list may include one or more different shared libraries, and may also include one or more versions of the same shared library with different versions.

In an example, the first shared library list includes a first version of the first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

S502: The application market sends a fourth query message to the package management, where the fourth query message is used to query the installation status of the shared libraries in the first shared library list.

Optionally, the application market queries the installation directory of the shared libraries in the first shared library list by calling the package management query interface in the system framework. Installation situation.

The installation status of the shared libraries in the first shared library list may refer to the installation status of each shared library in the first shared library list (for example, whether it is installed in the system/whether it exists in the system).

S503: Receive a fourth reply message sent by the package management, where the fourth reply message is used to indicate the installation status of the shared libraries in the first shared library list.

S504: The application market determines a second shared library list according to the fourth reply message.

The second shared library list includes the uninstalled shared libraries in the first shared library list, and/or the second shared library list includes the higher version shared libraries corresponding to the installed shared libraries in the first shared library list.

Optionally, the process of the application market determining the second shared library list according to the fourth reply message may be:

(1) Among one or more shared libraries in the first shared library list, which shared libraries are already installed (or exist in the system), which shared libraries (or higher versions of shared libraries) are not installed (or do not exist in the system), and the shared libraries that are not installed (or do not exist in the system) are listed in the second shared library list;

(2) For an installed (already existing) shared library, whether the version of the installed (already existing) shared library is greater than or equal to the version of the shared library in the first shared library list; if not, the version of the shared library in the first shared library list or a higher version of the shared library in the first shared library list is included in the second shared library list.

S505: Download the shared libraries in the second shared library list.

S506: Install the shared libraries in the second shared library list, and install or update the first application.

In the embodiment of the present application, through the collaboration between the system framework and the application market, the shared library and the third-party application can be installed together, so that the application always has the shared library it depends on, which can reduce the occurrence of application operation failures and improve the user experience.

In order to more clearly understand the installation process of a multi-version shared library, illustratively, FIG6 shows a schematic flow chart of a method 600 for installing a multi-version shared library provided in an embodiment of the present application. As shown in FIG6 , the method 600 includes:

S601: When there is a first version of a first shared library and a second version of the first shared library to be installed, install the first version of the first shared library in a first path and generate first shared library information; install the second version of the first shared library in a second path and generate second shared library information.

The first shared library information includes identification information of the first shared library and version information of the first shared library; the second shared library information includes identification information of the second shared library and version information of the second shared library.

Optionally, to ensure the security of the system, the permissions required by the shared library are applied for by the applications that depend on it, and the shared library itself cannot apply for permissions, and the shared library itself does not have a data directory.

In an embodiment of the present application, when the system installs different versions of shared libraries, it will install different versions of shared libraries in different version paths according to the version number, and generate multiple shared library information in the system according to the version. In this way, different versions of shared libraries can be relatively independent, different versions of the same shared library can be treated as different applications, and operations such as updating or uninstalling a specific version of the shared library can be implemented.

For example, Fig. 7 shows a schematic flow chart of a method 700 for updating a shared library provided in an embodiment of the present application. As shown in Fig. 7, the method 700 includes:

S701: When the application market detects that a new version of the first shared library is released, it sends a first query message to the system, where the first query message is used to query information of the first shared library.

The information of the first shared library includes information of one or more versions of the first shared library that are currently installed (already existing).

In an example, the one or more versions of the first shared library may include a first version of the first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

S702: The application market receives a first reply message sent by the system, where the first reply message is used to indicate information of the first shared library.

S703: The application market determines whether the first shared library needs to be updated according to the first reply message.

Specifically, the application market determines whether the new version of the first shared library exists in the information of the first shared library based on the first reply message. In other words, the application market determines whether the new version of the first shared library has been installed (i.e., whether it already exists) based on the first reply message. If so, it is determined that the first shared library does not need to be updated; if not, the first shared library needs to be updated.

In one example, the application market detects that the third version of the first shared library is released. After obtaining the information of the first shared library, the application market determines whether the information of the third version of the first shared library exists in the information of the first shared library. If not, it determines that the first shared library needs to be updated.

S704: When it is determined that the first shared library needs to be updated, a new version of the first shared library is downloaded.

In one example, the application market detects that the third version of the first shared library is released, and when it is determined that the first shared library needs to be updated, the third version of the first shared library is downloaded.

S705: Install the new version of the first shared library.

Optionally, the system installs a new version of the first shared library at a specific time.

Optionally, the specific timing may be, for example, when an application that depends on the first shared library is not running.

In one example, the application market detects that the third version of the first shared library is released, and when it is determined that the first shared library needs to be updated, the third version of the first shared library is downloaded and installed.

S706: When the application that depends on the first shared library is started, the highest version of the first shared library is obtained.

Obtaining the highest version of the first shared library may be obtaining a shared library path of the highest version of the first shared library.

In one example, after the first shared library is updated, the third version of the first shared library is the highest version of the first shared library. Then, when the application that depends on the first shared library is started, the third version of the first shared library is enabled.

In a possible implementation form, the current system is compatible with multiple versions of shared libraries. For example, after a first shared library is updated, when an application that depends on the first shared library is started, the shared library path of the highest version of the first shared library is obtained.

In another possible implementation form, the current system is not compatible with multiple versions of shared libraries. For example, after a first shared library is updated, when an application that depends on the first shared library is started, the path of the shared library configured by the system is obtained.

In the embodiments of the present application, the update of multiple versions of shared libraries is achieved through the collaboration between the mobile phone system and the application market, so that the shared libraries have independent update capabilities, lowering the development threshold for shared library providers, making shared libraries easier to manage and popularize; and, the system can automatically enable the highest version of the shared library it depends on when the application is started, so that the update of the shared library can be reflected in real time, thereby reducing the integration cost and update frequency of application developers when using shared libraries.

Exemplarily, Fig. 8 shows a schematic flow chart of a method 800 for uninstalling a shared library provided in an embodiment of the present application. As shown in Fig. 8, the method 800 includes:

S801: The application market sends a second query message to the system at a first opportunity, where the second query message is used to query information of a full shared library in a device.

Optionally, the application market calls a system interface to query information of the full shared library in the device.

The full shared library includes one or more shared libraries installed (already existing) in the current system, and the one or more shared libraries carry version information.

The information of the full shared library includes version information of each shared library in the full shared library, and/or includes dependency information of each shared library in the full shared library.

The dependency information is used to indicate whether the shared library is dependent on the application, or the dependency information is used to indicate which applications depend on the shared library.

In one example, the one or more shared libraries may include a first version of a first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

S802: The application market receives a second reply message sent by the system, where the second reply message is used to indicate information about the full shared library.

S803: Determine a fourth shared library list according to the second reply message.

The fourth shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the third shared library list includes low-version shared libraries in the full shared library, and the current running status of the shared libraries in the fourth shared library list is unknown.

S804: The application market sends a third query message to the system, the third query message is used to query the running information of each shared library in the fourth shared library list, the running information is used to indicate whether the shared library is currently in a running state. Optionally, the application market calls the system interface to query the running information of each shared library in the fourth shared library list according to the information of all shared libraries.

In one example, the information of the full shared library includes information of multiple shared libraries, which may, for example, include a first version of a first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

S805: The application market receives a third reply message sent by the system, where the third reply message is used to indicate the running information of each shared library in the fourth shared library list.

S806: The application market determines a third shared library list according to the third reply message, where the third shared library list includes the currently non-running shared libraries in the fourth shared library list.

That is, the application market determines the fourth shared library list and the operation information of each shared library in the fourth shared library list. 3. List of shared libraries.

Among them, the third shared library list includes shared libraries in the full shared libraries that are not dependent on the application and/or includes low-version shared libraries in multiple versions of shared libraries that are dependent on the application, wherein the low-version shared libraries are non-highest version shared libraries, and the shared libraries in the third shared library list are all in the currently non-running state.

S807: Uninstall the shared libraries in the third shared library list.

In the embodiments of the present application, through the collaboration between the system and the application market, the shared library has an independent uninstall capability, which lowers the development threshold of the shared library provider and makes the shared library easy to manage and popularize; it is also possible to uninstall shared libraries that are not relied on by the application and low-version shared libraries at specific times, which improves the user experience and reduces the storage space occupied in the system; and in terms of the uninstall (aging) mechanism, it is specifically divided into two cases: compatible with multi-version shared libraries and incompatible with multi-version shared libraries. For the case of compatible with multi-version shared libraries, the low-version shared libraries can be aged; for the case of incompatible with multi-version shared libraries, unused or infrequently used shared libraries can be aged, making the scope of application of the solution wider.

In order to more clearly understand the method for uninstalling a shared library in the embodiment shown in FIG8 , illustratively, FIG9 shows a schematic flow chart of another method 900 for uninstalling a shared library provided in an embodiment of the present application. As shown in FIG9 , the method 900 includes:

In this embodiment, after being updated, the first shared library includes a first version of the first shared library and an Ath version of the first shared library, and the Ath version is the highest version of the first shared library.

S901: When uninstalling the first version of the first shared library, deleting the path information of the first version of the first shared library.

It can be understood that after uninstalling the first version of the first shared library, only the path information of the first version of the first shared library is deleted, and the path information of other versions of the first shared library is still retained.

In an embodiment of the present application, different versions of the same shared library are treated as different applications. When a target version of a shared library is uninstalled, only the target version of the shared library is uninstalled, and other versions of the shared library are still retained, thereby enabling multiple versions of the shared library to have independent uninstall capabilities.

In one achievable manner, when a first application is uninstalled, it is first determined whether a first shared library that the first application depends on is also depended on by other applications. If not, the first shared library is uninstalled at the same time.

Exemplarily, Fig. 10 shows a schematic flow chart of another method 1000 for managing a shared library provided in an embodiment of the present application. As shown in Fig. 10, the method 1000 includes:

In this embodiment, the shared library currently relied on by the first application is the first version of the first shared library. After being updated, the first shared library includes the first version of the first shared library and the Ath version of the first shared library, and the Ath version is the highest version of the first shared library.

S1001: When the first version of the first shared library is uninstalled, the shared library on which the first application depends is automatically pointed to the Ath version of the first shared library.

In an embodiment of the present application, when the shared library version that the application depends on is uninstalled, the shared library version that the application depends on automatically points to the highest version of the shared library. In this way, when the application is started, the path of the shared library with the highest version is automatically obtained, and the application will not run abnormally due to the uninstallation of the shared library version, which can improve the user experience.

For example, FIG11 shows a schematic flow chart of a method 100 for updating and uninstalling a shared library provided in an embodiment of the present application. As shown in FIG11 , the method 1100 includes:

S1101: A shared library provider (or a shared library user) develops, distributes, and installs a shared library as a special type of application.

S1102: The shared library provider exports the interface package (har module) and execution package from the shared library module (library module).

S1103: Upload the interface package (har module) and execution package to the application market to ensure backward compatibility of the shared library version.

S1104: The shared library user completes its own application development through the application market integration interface package.

S1105: Put the developed application on the application market.

S1106: When the user triggers the installation operation of the application, execute step S1107.

S1107: Download the shared library that the application depends on.

S1108: Install the shared libraries that the application depends on.

S1109: Install the application.

S1110: When the user triggers the start of the application, step S1111 is further executed.

S1111: The operation management module obtains information related to the application from the package management.

S1112: The operation management module passes startup parameters to the application incubation module (AppSpawn).

S1113: The application incubation module searches for the shared library path from the shared library module (library module).

S1114: The application incubation module obtains the highest version of the shared library path that the application depends on and enters the application process.

For example, FIG. 12 shows a functional module diagram of a device 1200 for synchronously installing an application and a shared library provided in an embodiment of the present application. As shown in FIG12 , the device 1200 includes:

The first acquisition module 1210 is used to download the installation package of the first application in response to the user's operation of installing/updating the first application, and to acquire a first shared library list on which the first application depends.

Optionally, the first acquisition module 1210 downloads the installation package of the first application from the cloud and parses a configuration file in the installation package of the first application to obtain a first shared library list on which the first application depends.

Among them, the first shared library list that the first application depends on includes one or more shared libraries that the first application depends on, and the one or more shared libraries carry version information. That is to say, the first shared library list may include one or more different shared libraries, and may also include one or more versions of the same shared library with different versions.

In an example, the first shared library list includes a first version of the first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

The first transceiver module 1220 is used to send a fourth query message to the package management module, where the fourth query message is used to query the installation status of the shared libraries in the first shared library list.

Optionally, the application market queries the installation status of the shared libraries in the first shared library list by calling a package management query interface in the system framework.

The installation status of the shared libraries in the first shared library list may refer to the installation status of each shared library in the first shared library list (for example, whether it is installed in the system/whether it exists in the system).

The first transceiver module 1220 is further used to receive a fourth reply message sent by the package management module, where the fourth reply message is used to indicate the installation status of the shared libraries in the first shared library list.

The first determining module 1230 is configured to determine a second shared library list according to the fourth reply message.

The second shared library list includes the uninstalled shared libraries in the first shared library list, and/or the second shared library list includes the higher version shared libraries corresponding to the installed shared libraries in the first shared library list.

Optionally, the process of the first determining module 1230 determining the second shared library list according to the fourth reply message may be:

(1) Among the one or more shared libraries in the first shared library list, which shared libraries are already installed (or exist in the system), and which shared libraries (or higher versions of shared libraries) are not installed (or do not exist in the system), and the first determination module 1230 lists the shared libraries that are not installed (or do not exist in the system) in the second shared library list;

(2) For an installed (already existing) shared library, whether the version of the installed (already existing) shared library is greater than or equal to the version of the shared library in the first shared library list; if not, the first determination module 1230 includes the version of the shared library in the first shared library list or a higher version of the shared library in the first shared library list in the second shared library list.

The first acquisition module 1210 is further configured to download the shared libraries in the second shared library list.

The first installation module 1240 is used to install the shared libraries in the second shared library list, and install or update the first application.

In the embodiment of the present application, through the collaboration between the system framework and the application market, the shared library and the third-party application can be installed together, so that the application always has the shared library it depends on, which can reduce the occurrence of application operation failures and improve the user experience.

For example, Fig. 13 shows a functional module diagram of a device 1300 for updating a shared library provided in an embodiment of the present application. As shown in Fig. 13, the device 1300 includes:

The second transceiver module 1310 is used to send a first query message to the system when detecting that a new version of the first shared library is released, where the first query message is used to query information of the first shared library.

The information of the first shared library includes information of one or more versions of the first shared library that are currently installed (already existing).

In an example, the one or more versions of the first shared library may include a first version of the first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

The second transceiver module 1310 is further used to receive a first reply message sent by the system, where the first reply message is used to indicate information of the first shared library.

The second determination module 1320 is configured to determine whether the first shared library needs to be updated according to the first reply message.

Specifically, the second determination module 1320 determines whether there is a new version of the first shared library in the information of the first shared library based on the first reply message. In other words, the second determination module 1120 determines whether the new version of the first shared library has been installed (i.e., whether it already exists) based on the first reply message. If so, it is determined that the first shared library does not need to be updated; if not, the first shared library needs to be updated.

In one example, when it is detected that the third version of the first shared library is released, after the second transceiver module 1310 obtains the information of the first shared library, the second determination module 1320 determines whether the information of the first shared library contains the information of the third version of the first shared library. If not, the second determination module 1320 determines whether the information of the first shared library contains the information of the third version of the first shared library. The second determination module 1320 determines that the first shared library needs to be updated.

The second acquisition module 1330 is configured to download a new version of the first shared library when it is determined that the first shared library needs to be updated.

In one example, it is detected that the third version of the first shared library is released, and when the second determination module 1320 determines that the first shared library needs to be updated, the second acquisition module (or downloading module) 1330 downloads the third version of the first shared library.

The second installation module 1340 is used to install the new version of the first shared library.

Optionally, the second installation module 1340 installs the new version of the first shared library at a specific time.

Optionally, the specific timing may be, for example, when an application that depends on the first shared library is not running.

The second acquisition module 1330 is further configured to acquire the highest version of the first shared library when the application that depends on the first shared library is started.

Obtaining the highest version of the first shared library may be obtaining a shared library path of the highest version of the first shared library.

In one example, after the first shared library is updated, the third version of the first shared library is the highest version of the first shared library. Then, when the application that depends on the first shared library is started, the third version of the first shared library is enabled.

In the embodiments of the present application, the update of multiple versions of shared libraries is achieved through the collaboration between the mobile phone system and the application market, so that the shared libraries have independent update capabilities, lowering the development threshold for shared library providers, making shared libraries easier to manage and popularize; and, the system can automatically enable the highest version of the shared library it depends on when the application is started, so that the update of the shared library can be reflected in real time, thereby reducing the integration cost and update frequency of application developers when using shared libraries.

For example, Fig. 14 shows a functional module diagram of a device 1400 for uninstalling a shared library provided in an embodiment of the present application. As shown in Fig. 14, the device 1400 includes:

The third transceiver module 1410 is used to send a second query message to the system at a first opportunity, where the second query message is used to query information of the full shared library in the device.

Optionally, the third transceiver module 1410 calls a system interface to obtain information of a full shared library in the device.

The full shared library refers to one or more shared libraries that are currently installed (already exist), and the one or more shared libraries carry version information.

The information of the full shared library includes version information of each shared library in the full shared library, and/or includes dependency information of each shared library in the full shared library.

The dependency information is used to indicate whether the shared library is dependent on the application, or the dependency information is used to indicate which applications depend on the shared library.

In one example, the one or more shared libraries may include a first version of a first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

The third transceiver module 1410 is further used to receive a second reply message sent by the system, where the second reply message is used to indicate information about the full shared library.

The third determining module 1420 is configured to determine a fourth shared library list according to the second reply message.

The fourth shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the third shared library list includes low-version shared libraries in the full shared library, and the current running status of the shared libraries in the fourth shared library list is unknown.

The third transceiver module 1410 is further used to send a third query message to the system, where the third query message is used to query the running information of each shared library in the fourth shared library list, where the running information is used to indicate whether the shared library is currently in a running state.

Optionally, the third transceiver module 1410 calls a system interface according to the information of all shared libraries to obtain the running information of each shared library in the fourth shared library list.

In one example, the information of the full shared library includes information of multiple shared libraries, which may, for example, include a first version of a first shared library, a second version of the first shared library, a third version of the first shared library, a first version of the second shared library, a first version of the third shared library, and a second version of the third shared library.

The third transceiver module 1410 is further used to receive a third reply message sent by the system, where the third reply message is used to indicate the running information of each shared library in the fourth shared library list.

The third determining module 1420 is configured to determine a third shared library list according to the third reply message, where the third shared library list includes the currently non-running shared libraries in the fourth shared library list.

That is, the third determining module 1420 is configured to determine the third shared library list according to the fourth shared library list and the running information of each shared library in the fourth shared library list.

The third shared library list includes the shared libraries in the above-mentioned full sharing that are not relied on by the application, and/or includes the lower version shared libraries in multiple versions of the shared libraries relied on by the application, wherein the lower version shared libraries are non-highest version shared libraries, and the shared libraries in the third shared library list are The shared libraries are not currently running.

The uninstall module 1430 is used to uninstall the shared libraries in the third shared library list.

In the embodiments of the present application, through the collaboration between the system and the application market, the shared library has an independent uninstall capability, which lowers the development threshold of the shared library provider and makes the shared library easy to manage and popularize; it is also possible to uninstall shared libraries that are not relied on by the application and low-version shared libraries at specific times, which improves the user experience and reduces the storage space occupied in the system; and in terms of the uninstall (aging) mechanism, it is specifically divided into two cases: compatible with multi-version shared libraries and incompatible with multi-version shared libraries. For the case of compatible with multi-version shared libraries, the low-version shared libraries can be aged; for the case of incompatible with multi-version shared libraries, unused or infrequently used shared libraries can be aged, making the scope of application of the solution wider.

An embodiment of the present application also provides a computer-readable medium, which stores a program code. When the computer program code runs on a computer, the computer executes any one of the methods in Figures 3 to 11 above.

An embodiment of the present application also provides a chip, including: at least one processor and a memory, wherein the at least one processor is coupled to the memory and is used to read and execute instructions in the memory to execute any one of the methods in Figures 3 to 11 above.

An embodiment of the present application also provides an electronic device, comprising: at least one processor and a memory, wherein the at least one processor is coupled to the memory and is used to read and execute instructions in the memory to execute any one of the methods in Figures 3 to 11 above.

The above embodiments may be used alone or in combination with each other to achieve different technical effects.

For example, the above apparatus 1200 , apparatus 1300 , and apparatus 1400 may be used alone or in combination with each other.

One or more of the modules or units described herein may be implemented in software, hardware, or a combination of the two. When any of the above modules or units are implemented in software, the software exists in the form of computer program instructions and is stored in a memory, and a processor may be used to execute the program instructions and implement the above method flow. The processor may include, but is not limited to, at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or an artificial intelligence processor and other types of computing devices that run software, each of which may include one or more cores for executing software instructions for calculation or processing. The processor may be built into an SoC (system on chip) or an application specific integrated circuit (ASIC), or it may be an independent semiconductor chip. In addition to the core used to execute software instructions for calculation or processing in the processor, it may further include necessary hardware accelerators, such as a field programmable gate array (FPGA), a PLD (programmable logic device), or a logic circuit that implements a dedicated logic operation.

When the modules or units described in this document are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a DSP, an MCU, an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator, or a non-integrated discrete device, which can run the necessary software or be independent of the software to execute the above method flow.

When the modules or units described herein are implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium may be any available medium with a configuration capability similar to a cache that a computer can access, or a server, a data center, or other data storage device that includes one or more available media integrated with a configuration capability similar to a cache.

Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (29)

A method for managing a shared library, characterized in that the method comprises: When it is detected that the Ath version of the first shared library is released, determining whether the Ath version of the first shared library is installed in the system; When it is determined that the Ath version of the first shared library is not installed in the system, the Ath version of the first shared library is downloaded. The method according to claim 1, characterized in that the method further comprises: Installing version A of the first shared library; When it is detected that the first application is started, the Ath version of the first shared library is obtained to run the first application, where the first shared library is a shared library that the first application depends on. The method according to claim 1 or 2, characterized in that the step of determining whether the Ath version of the first shared library is installed in the system comprises: Acquire information about the first shared library, where the information about the first shared library includes information about one or more versions of the first shared library that are currently installed; It is determined whether the Ath version of the first shared library is installed in the system according to the information of the first shared library. The method according to claim 3, characterized in that the step of determining whether the Ath version of the first shared library is installed in the system according to the information of the first shared library comprises: When the information of the first shared library does not include information of the Ath version of the first shared library, it is determined that the Ath version of the first shared library is not installed in the system. The method according to claim 3 or 4, characterized in that the obtaining the information of the first shared library comprises: The application market sends a first query message to the system, where the first query message is used to query information of the first shared library; The application market receives a first reply message, where the first reply message includes information about the first shared library. The method according to any one of claims 1 to 5, characterized in that the method further comprises: Determine a third shared library list, wherein the third shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the third shared library list includes lower-version shared libraries in the full shared library, and all shared libraries in the third shared library list are currently not running, and the full shared library includes all shared libraries currently installed in the system; The shared libraries in the third shared library list are uninstalled. The method according to claim 6, characterized in that the determining the third shared library list comprises: Acquire information of the full shared library, wherein the information of the full shared library includes version information of each shared library in the full shared library, and/or the information of the full shared library includes dependency information of each shared library in the full shared library, wherein the dependency information is used to indicate whether the shared library is dependent on an application, or the dependency information is used to indicate which applications depend on the shared library; Determine a fourth shared library list according to the information of the full shared library, wherein the fourth shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the fourth shared library list includes low-version shared libraries in the full shared library; Acquire running information of each shared library in the fourth shared library list, where the running information is used to indicate whether the shared library is currently in a running state; The third shared library list is determined according to the running information, and the third shared library list includes the currently non-running shared libraries in the fourth shared library list. The method according to claim 7, characterized in that the step of obtaining the information of the full shared library comprises: The application market sends a second query message to the system, where the second query message is used to query information of the full shared library; The application market receives a second reply message, where the second reply message includes information about the full shared library. The method according to claim 7 or 8, characterized in that the step of obtaining the running information of each shared library in the fourth shared library list comprises: The application market sends a third query message to the system, where the third query message is used to query the running information of each shared library in the fourth shared library list; The application market receives a third reply message, where the third reply message is used to indicate the running information of each shared library in the fourth shared library list. The method according to any one of claims 6 to 9, characterized in that the full shared library includes a first version of the first shared library and an Ath version of the first shared library, and the Ath version of the first shared library is the highest version of the first shared library. The method further comprises: When the first version of the first shared library is uninstalled, the shared library version on which the first application depends is pointed to the Ath version of the first shared library. The method according to any one of claims 1 to 10, characterized in that the method further comprises: In response to a user's operation of installing or updating the first application, obtaining a first shared library list that the first application depends on, the first shared library list including M shared libraries, where M is a positive integer greater than or equal to 1; Determine a second shared library list according to the installation status of the M shared libraries, wherein the second shared library list includes the shared libraries among the M shared libraries that are not installed; The shared libraries in the second shared library list are installed, and the first application is installed or updated. The method according to claim 11, characterized in that before determining the second shared library list according to the installation status of the M shared libraries, the method further comprises: The application market sends a fourth query message to the system, where the fourth query message is used to query the installation status of the M shared libraries; The application market receives a fourth reply message, where the fourth reply message is used to indicate the installation status of the M shared libraries. The method according to claim 11 or 12, characterized in that the step of installing the shared libraries in the second shared library list comprises: Each shared library in the second shared library list is installed in a different path. A method for managing a shared library, characterized in that the method comprises: Determine a third shared library list, wherein the third shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the third shared library list includes lower-version shared libraries in the full shared library, and all shared libraries in the third shared library list are currently not running, and the full shared library includes all shared libraries currently installed in the system; The shared libraries in the third shared library list are uninstalled. The method according to claim 14, characterized in that the determining the third shared library list comprises: Acquire information of the full shared library, wherein the information of the full shared library includes version information of each shared library in the full shared library, and/or the information of the full shared library includes dependency information of each shared library in the full shared library, wherein the dependency information is used to indicate whether the shared library is dependent on an application, or the dependency information is used to indicate which applications depend on the shared library; Determine a fourth shared library list according to the information of the full shared library, wherein the fourth shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the fourth shared library list includes low-version shared libraries in the full shared library; Acquire running information of each shared library in the fourth shared library list, where the running information is used to indicate whether the shared library is currently in a running state; The third shared library list is determined according to the running information, and the third shared library list includes the currently non-running shared libraries in the fourth shared library list. The method according to claim 15, characterized in that the obtaining of the information of the full shared library comprises: The application market sends a second query message to the system, where the second query message is used to query information of the full shared library; The application market receives a second reply message, where the second reply message includes information about the full shared library. The method according to claim 15 or 16, characterized in that the obtaining the running information of each shared library in the fourth shared library list comprises: The application market sends a third query message to the system, where the third query message is used to query the running information of each shared library in the fourth shared library list; The application market receives a third reply message, where the third reply message is used to indicate the running information of each shared library in the fourth shared library list. The method according to any one of claims 14 to 17, characterized in that the full shared library includes a first version of the first shared library and an Ath version of the first shared library, the Ath version of the first shared library being the highest version of the first shared library, and the method further comprises: When the first version of the first shared library is uninstalled, the shared library version on which the first application depends is pointed to the Ath version of the first shared library, where the first shared library is the shared library on which the first application depends. The method according to any one of claims 14 to 18, characterized in that the method further comprises: In response to a user's operation of installing or updating a first application, a first shared library list dependent on the first application is obtained, wherein the first shared library list The library list includes M shared libraries, where M is a positive integer greater than or equal to 1; Determine a second shared library list according to the installation status of the M shared libraries, wherein the second shared library list includes the shared libraries among the M shared libraries that are not installed; The shared libraries in the second shared library list are installed, and the first application is installed or updated. The method according to claim 19, characterized in that before determining the second shared library list according to the installation status of the M shared libraries, the method further comprises: The application market sends a fourth query message to the system, where the fourth query message is used to query the installation status of the M shared libraries; The application market receives a fourth reply message, where the fourth reply message is used to indicate the installation status of the M shared libraries. The method according to claim 19 or 20, characterized in that the step of installing the shared libraries in the second shared library list comprises: Install each shared library in the second shared library list in a different path. A device for managing a shared library, characterized in that the device comprises: A judgment module, configured to judge whether the Ath version of the first shared library is installed in the system when detecting that the Ath version of the first shared library is released; The download module is used to download the Ath version of the first shared library when it is determined that the Ath version of the first shared library is not installed in the system. The device according to claim 22, characterized in that the device further comprises: An installation module, used for installing the Ath version of the first shared library; The acquisition module is used to acquire the Ath version of the first shared library to run the first application when detecting that the first application is started, wherein the first shared library is a shared library that the first application depends on. A device for managing a shared library, characterized in that the device comprises: A determination module, configured to determine a third shared library list, wherein the third shared library list includes shared libraries in the full shared library that are not relied upon by the application, and/or the third shared library list includes lower-version shared libraries in the full shared library, wherein the full shared library includes all shared libraries currently installed in the system; The uninstall module is used to uninstall the shared libraries in the third shared library list. The device according to claim 24, characterized in that the device further comprises: An acquisition module, used for acquiring information of the full shared library, wherein the information of the full shared library includes dependency information of each shared library in the full shared library, and each shared library in the full shared library carries a version identifier; The acquisition module is further used to acquire the operation information of each shared library in the full shared library; A determination module is used to determine the third shared library list according to the information of the full shared library and the operation information of each shared library in the full shared library. An electronic device, comprising: processor; Memory; And a computer program, wherein the computer program is stored in the memory, and the computer program includes instructions, which, when executed by the processor, enable the electronic device to perform the method as described in any one of claims 1 to 13, or perform the method as described in any one of claims 14 to 21. A computer-readable storage medium, characterized in that a program or instruction is stored in the storage medium, and when the program or instruction is executed, the method as claimed in any one of claims 1 to 13 is implemented, or the method as claimed in any one of claims 14 to 21 is implemented. A chip, characterized by comprising: processor; A memory, wherein the processor is coupled to the memory and configured to read and execute instructions in the memory to execute the method according to any one of claims 1 to 13, or to execute the method according to any one of claims 14 to 21. A computer program product, characterized in that the computer program product includes computer program code, and when the computer program code is run on a computer, it implements the method as claimed in any one of claims 1 to 13, or implements the method as claimed in any one of claims 14 to 21.