CN108469985B - Application program management method and device - Google Patents
Application program management method and device Download PDFInfo
- Publication number
- CN108469985B CN108469985B CN201810155140.4A CN201810155140A CN108469985B CN 108469985 B CN108469985 B CN 108469985B CN 201810155140 A CN201810155140 A CN 201810155140A CN 108469985 B CN108469985 B CN 108469985B
- Authority
- CN
- China
- Prior art keywords
- application
- application program
- state
- message
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
本发明实施例提供一种应用程序的管理方法和设备，涉及通信领域，以使得应用程序管理设备根据应用程序的应用状态向该应用程序发送系统应用消息，该方法包括：应用程序管理设备获得系统应用消息；其中，该系统应用消息包括属性标识，该属性标识包括前台标识、后台标识和未启动标识中的至少一个，并在该应用程序管理设备获得该系统应用消息后，确定订阅该系统应用消息的应用程序，并获取该应用程序的应用状态；当该应用程序的应用状态与该属性标识对应时，通过该应用程序处理该系统应用消息。本发明实施例用于管理应用程序。
Embodiments of the present invention provide an application management method and device, which relate to the field of communications, so that the application management device sends a system application message to the application according to the application state of the application. The method includes: the application management device obtains a system Application message; wherein, the system application message includes an attribute identifier, and the attribute identifier includes at least one of a foreground identifier, a background identifier and an inactive identifier, and after the application program management device obtains the system application message, it is determined to subscribe to the system application The application program of the message is obtained, and the application state of the application program is obtained; when the application state of the application program corresponds to the attribute identifier, the system application message is processed by the application program. The embodiment of the present invention is used for managing application programs.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for managing an application.
Background
In a terminal based on an Android system, for some applications configured by the Android system, in the prior art, if an application subscribes to a system application message (that is, an application message queue of the application includes the system application message, such as a power control message), the system sends the system application message to the application, so that the application processes the system application message.
However, if the application program is in the non-started state, the application program is converted into the started state after receiving the system application message, and is converted into the non-started state after processing the system application message, so that the load of the system is increased.
Disclosure of Invention
The embodiment of the invention provides a method and equipment for managing an application program, so that the application program management equipment sends a system application message to the application program according to the application state of the application program.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
in a first aspect, a method for managing an application program is provided, including:
the application program management equipment acquires a system application message; the system application message comprises an attribute identifier, wherein the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier;
after the application program management equipment obtains the system application message, determining an application program subscribing the system application message, and obtaining an application state of the application program;
and processing the system application message through the application program when the application state of the application program corresponds to the attribute identification.
In a first possible implementation manner of the first aspect, the obtaining the state of the application includes:
querying a state list, wherein the state list is generated by an operating system according to the application state of the application program, and the state list comprises the application state of the application program;
and determining the application state of the application program according to the state list.
With reference to the first aspect or the first possible implementation manner, in a second possible implementation manner, the processing the system application message through the application program corresponding to the attribute identifier includes:
when the attribute identification comprises a foreground identification and the application program is in a foreground state, processing the system application message through the application program;
when the attribute identification comprises a background identification and the application program is in a background state, processing the system application message through the application program;
and when the attribute identification comprises an un-started identification and the application program is in an un-started state, processing the system application message through the application program.
With reference to any one of the first aspect to the second possible implementation manner, in a third possible implementation manner, before acquiring an application state of the application program, the method further includes:
the application program management equipment inquires an application program starting list;
determining whether to start the application program according to the query result; wherein the application program comprises an application program configured by the system.
With reference to the third possible implementation manner, in a fourth possible implementation manner, the application program startup list includes an identifier of the application program added by the user through the application program management device, or an identifier of the application program added by the application program through a system file access interface.
In a second aspect, there is provided an application management device comprising
The system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a system application message, the system application message comprises an attribute identifier, and the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier;
the processing unit is used for determining an application program subscribing the system application message after the acquisition unit acquires the system application message;
the obtaining unit is further configured to obtain an application state of the application program;
the processing unit is further configured to process the system application message through the application program when the application state of the application program acquired by the acquisition unit corresponds to the attribute identifier.
In a first possible implementation manner of the second aspect, the obtaining unit is specifically configured to query a state list, and determine an application state of the application program according to the state list, where the state list is generated by an operating system according to the application state of the application program, and the state list includes the application state of the application program.
With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the processing unit is specifically configured to,
when the attribute identification comprises a foreground identification and the application program is in a foreground state, processing the system application message through the application program;
when the attribute identification comprises a background identification and the application program is in a background state, processing the system application message through the application program;
and when the attribute identification comprises an un-started identification and the application program is in an un-started state, processing the system application message through the application program.
With reference to the second aspect to the second possible implementation manner of the second aspect, in a third possible implementation manner,
the application management device further includes:
the query unit is used for querying an application program starting list before the acquisition unit acquires the application state of the application program;
the starting unit is used for determining whether to start the application program according to the query result of the query unit; wherein the application program comprises an application program configured by the system.
With reference to the third possible implementation manner, in a fourth possible implementation manner, the application program launch list includes an identifier of the application program added by the user through the application program management device, or an identifier of the application program added by the application program through a system file access interface.
By adopting the scheme, the application program management equipment obtains the system application message; the system application message comprises an attribute identifier, the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier, and after the application program management device obtains the system application message, an application program subscribing the system application message is determined, and the application state of the application program is obtained; when the application state of the application corresponds to the attribute identification, the system application message is processed by the application. Therefore, the application program management device can send the system application message to the application program according to the application state of the application program, and the situation that when the application program is in a background state or an un-started state and the system application message needs to be processed in a foreground, the application program management device still processes the system application message through the application program to increase the load of the system and the occupied memory is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram illustrating a management method of an application according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating another management method for an application according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of an application management device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of another application management device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another application management device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present invention provides a method for managing an application, where as shown in fig. 2, an execution subject of the embodiment of the method is an application management device, and the method further includes:
s101, the application program management equipment obtains a system application message.
The system application message comprises an attribute identifier, the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier, and the system application message is generated by the operating system.
It should be noted that the format of the system application message including the attribute identifier is as follows:
<intent-filter>
<action
android:name＝"android.intent.action.user-define-action-name"/>
<category android.intent.category.background/>
</intent-filter>
the action and the category define to constitute a system application message, where the background in the < category android.
S102, after the application program management device obtains the system application message, the application program management device determines an application program subscribed to the system application message and obtains an application state of the application program.
Specifically, when the system message queue of the application program includes the system application message, it is determined that the application program subscribes to the system application message, the application program management device queries a status list, and determines an application state of the application program according to the status list.
The state list is generated by the operating system according to the application state of the application program, the state list includes the application state of the application program, and the operating system may be an Android system.
S103, when the application state of the application program corresponds to the attribute identification, the application program management device processes the system application message through the application program.
Specifically, when the attribute identifier includes a foreground identifier and the application is in a foreground state, the application management device processes the system application message through the application;
when the attribute identifier comprises a background identifier and the application program is in a background state, the application program management device processes the system application message through the application program;
when the attribute identifier comprises an un-started identifier and the application program is in an un-started state, the application program management device processes the system application message through the application program.
It should be noted that, if the attribute identifier includes a foreground identifier, a background identifier, and an un-started identifier, the application management device may process the system application message through the application program no matter the application program is in any state.
Illustratively, when the attribute identifier of the system application message is a foreground identifier and the application program is in a foreground state, the application program management device processes the system application message through the application program; therefore, when the application program is in the background state, the data and the corresponding interface state do not need to be refreshed, and the data only needs to be updated when the application program is switched from the background state to the foreground state, so that the system load caused by monitoring the system application message in the background is reduced; when the attribute identifier of the system application message is a background identifier and the application program is in a background state, the application program management device processes the system application message through the application program, and when the attribute identifier of the system application message is an un-started identifier, the application program is awakened and processes the system application message even if the application program is not started.
Further, in the prior art, when a system is started, a BOOT startup message (e.g., a BOOT _ complete message) is broadcast, if a configuration file corresponding to the application program in the system includes an identifier of the BOOT startup message (i.e., indicating that the application program registers the BOOT startup message), the application program receives the BOOT startup message and starts according to the BOOT startup message, because whether the application program registers the BOOT startup message is pre-configured in the system, when the system is started, the application program that a user does not want to start is still started or the application program that the user wants to start is not started, and therefore, before the application device obtains an application state of the application program, the application device queries an application program start list and determines whether to start the application program according to a query result.
Wherein the application may be an application configured by the system itself. The application startup list includes the identification of the application added by the user through the application management device or the identification of the application added by the application through the system file access interface.
That is, the addition of the identifier of the application program to the application program launch list includes the following two ways:
the first method is as follows: the user adds the identification of the application to the application launch list through the application management device.
Specifically, the application is configured with a start option provided to the user, and the user determines whether to start the application with the start of the system through the start option, for example, the setting option of the application includes an option of "automatically running this program when starting up", for the user, the "automatically running this program when starting up" in the setting option of the application is not selected, if the user wants the application to be automatically started up when starting up the system, the setting option is selected, at this time, the identifier of the application is added to the start-up list of the application, and if the user does not want the application to be started up when starting up the system, the setting option is not changed.
The second method comprises the following steps: and the application program adds the identification of the application program through the system file access interface.
Specifically, the system file access interface supports the application program to access the system file, and the application program accesses the system file through the system file access interface, so that the identifier of the application program is added to the application program start list.
Specifically, when the system is started, the application program actively accesses the system file access interface, so that the addition of the identifier of the application program is realized, for example, for a user, the "auto-run this program" in the setting options of the application program is selected, if the user wants the application program to be automatically started when the system is started, the setting options are not changed, if the user does not want the application program to be started when the system is started, the setting options are deselected, and at this time, the identifier of the application program is also removed from the application program start list.
It should be noted that, as can be seen from the above first and second modes, for the user, in the first mode, the option of "automatically running the application at startup" of the application is default to being unselected, and the user may set the option according to the need of the user, and in the second mode, the option of "automatically running the application at startup" of the application is default to being selected, and the user may set the option according to the need of the user, that is, in the first mode, the user determines whether to add the identifier of the application to the application start list according to the need of the user, and in the second mode, the user determines whether to remove the identifier of the application from the application start list according to the need of the user because the application start list already includes the identifier of the application.
In addition, the application program may include an application program configured by the system itself, that is, the authority of the application program is higher than that of a third party application program installed by a user, and the higher authority application program can obtain more services from the system.
Specifically, after the user completes configuration of application program start, the application program management device determines whether to add an identifier of the application program to the application program start list according to the setting of the user, and after the system is powered on again, the application program management device queries the application program start list, so as to determine whether to start the application program according to the application program start list.
Further, the querying of the application start list by the application management device includes the following two cases:
the first condition is as follows: the application management device queries a first application launch list.
The first application program starting list comprises identification of application programs to be started.
Specifically, since the first application program launch list includes the identifier of the application program that needs to be launched when the system is launched, the application program management device launches the application program when determining that the first application program launch list includes the identifier of the application program, and obtains a launch instruction when determining that the first application program launch list does not include the identifier of the application program, and launches the application program according to the launch instruction; that is to say, when the first application program start list includes the identifier of the application program, the application program corresponding to the identifier of the application program is automatically started when the system is started, and when the first application program start list does not include the identifier of the application program, that is, it indicates that the application program corresponding to the identifier of the application program does not need to be automatically started when the system is started, therefore, when the application program management device obtains the start instruction corresponding to the application program triggered by the user through the terminal, the application program is started.
In case two, the application management device queries the second application launch list.
Wherein the second application launch list includes an identification of applications that are not launched.
Specifically, since the second application startup list includes the identifier of the application that does not need to be automatically started at system startup, the application management device receives a startup instruction when determining that the second application startup list includes the identifier of the application, starts the application according to the startup instruction, and starts the application when determining that the second application startup list does not include the identifier of the application, that is, when the second application startup list includes the identifier of the application, that is, when the second application startup list indicates that the application corresponding to the identifier of the application does not need to be automatically started at system startup, therefore, when the application management device acquires the startup instruction corresponding to the application triggered by the user, the application is started, and when the second application startup list does not include the identifier of the application, and when the system is started, automatically starting the application program corresponding to the identification of the application program.
By adopting the scheme, the application program management device can send the system application message to the application program according to the application state of the application program, so that the situation that when the application program is in a background state or an un-started state and the system application message needs to be processed in a foreground, the application program management device still processes the system application message through the application program to increase the load of the system and the occupied memory is avoided.
An embodiment of the present invention provides a method for managing an application program, and as shown in fig. 2, the method includes:
s201, after the operating system is started, the application program management equipment acquires a system application message.
The system application message comprises an attribute identifier, wherein the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier.
It should be noted that the format of the system application message including the attribute identifier is as follows:
<intent-filter>
<action
android:name＝"android.intent.action.user-define-action-name"/>
<category android.intent.category.background/>
</intent-filter>
the action and the category define to constitute a system application message, where the background in the < category android.
S202, after the application management device obtains the system application message, the application management device determines an application program subscribed to the system application message.
Specifically, when the system message queue of the application program includes the system application message, it is determined that the application program subscribes to the system application message, the application program management device queries a status list, and determines an application state of the application program according to the status list.
The state list is generated by the operating system according to the application state of the application program, the state list includes the application state of the application program, and the operating system may be an Android system.
S203, the application management apparatus queries the application start list.
And S204, the application program management equipment determines whether to start the application program according to the query result.
Wherein the application may be an application configured by the system itself. The application startup list includes the identification of the application added by the user through the application management device or the identification of the application added by the application through the system file access interface.
That is, the addition of the identifier of the application program to the application program launch list includes the following two ways:
the first method is as follows: the user adds the identification of the application to the application launch list through the application management device.
Specifically, the application is configured with a start option provided to the user, and the user determines whether to start the application with the start of the system through the start option, for example, the setting option of the application includes an option of "automatically running this program when starting up", for the user, the "automatically running this program when starting up" in the setting option of the application is not selected, if the user wants the application to be automatically started up when starting up the system, the setting option is selected, at this time, the identifier of the application is added to the start-up list of the application, and if the user does not want the application to be started up when starting up the system, the setting option is not changed.
The second method comprises the following steps: and the application program adds the identification of the application program through the system file access interface.
Specifically, the system file access interface supports the application program to access the system file, and the application program accesses the system file through the system file access interface, so that the identifier of the application program is added to the application program start list.
Specifically, when the system is started, the application program actively accesses the system file access interface, so that the addition of the identifier of the application program is realized, for example, for a user, the "auto-run this program" in the setting options of the application program is selected, if the user wants the application program to be automatically started when the system is started, the setting options are not changed, if the user does not want the application program to be started when the system is started, the setting options are deselected, and at this time, the identifier of the application program is also removed from the application program start list.
It should be noted that, as can be seen from the above first and second modes, for the user, in the first mode, the option of "automatically running the application at startup" of the application is default to being unselected, and the user may set the option according to the need of the user, and in the second mode, the option of "automatically running the application at startup" of the application is default to being selected, and the user may set the option according to the need of the user, that is, in the first mode, the user determines whether to add the identifier of the application to the application start list according to the need of the user, and in the second mode, the user determines whether to remove the identifier of the application from the application start list according to the need of the user because the application start list already includes the identifier of the application.
Wherein the application program comprises an application program configured by the system.
Specifically, the querying of the application start list by the application management device includes the following two cases:
the first condition is as follows: the application management device queries a first application launch list.
The first application program starting list comprises identification of application programs to be started.
Specifically, since the first application program launch list includes the identifier of the application program that needs to be launched when the system is launched, the application program management device launches the application program when determining that the first application program launch list includes the identifier of the application program, and obtains a launch instruction when determining that the first application program launch list does not include the identifier of the application program, and launches the application program according to the launch instruction; that is to say, when the first application program start list includes the identifier of the application program, the application program corresponding to the identifier of the application program is automatically started when the system is started, and when the first application program start list does not include the identifier of the application program, that is, it indicates that the application program corresponding to the identifier of the application program does not need to be automatically started when the system is started, therefore, when the application program management device obtains the start instruction corresponding to the application program triggered by the user through the terminal, the application program is started.
In case two, the application management device queries the second application launch list.
Wherein the second application launch list includes an identification of applications that are not launched.
Specifically, since the second application startup list includes the identifier of the application that does not need to be automatically started at system startup, the application management device receives a startup instruction when determining that the second application startup list includes the identifier of the application, starts the application according to the startup instruction, and starts the application when determining that the second application startup list does not include the identifier of the application, that is, when the second application startup list includes the identifier of the application, that is, when the second application startup list indicates that the application corresponding to the identifier of the application does not need to be automatically started at system startup, therefore, when the application management device acquires the startup instruction corresponding to the application triggered by the user, the application is started, and when the second application startup list does not include the identifier of the application, and when the system is started, automatically starting the application program corresponding to the identification of the application program.
S205, the application management device queries the status list of the application.
The state list is generated by the operating system according to the application state of the application program, and the state list comprises the application state of the application program.
And S206, the application program management device determines the application state of the application program according to the state list.
It should be noted that, after the application program is started, the user may set the application state of the application program to a foreground state or a background state.
And S207, when the application state of the application program corresponds to the attribute identification, the application program management device processes the system application message through the application program.
Specifically, when the attribute identifier includes a foreground identifier and the application is in a foreground state, the application management device processes the system application message through the application.
And when the attribute identifier comprises a background identifier and the application program is in a background state, the application program management device processes the system application message through the application program.
When the attribute identifier comprises an un-started identifier and the application program is in an un-started state, the application program management device processes the system application message through the application program.
It should be noted that, if the attribute identifier includes a foreground identifier, a background identifier, and an un-started identifier, the application management device may process the system application message through the application program no matter the application program is in any state.
Illustratively, when the attribute identifier of the system application message is a foreground identifier and the application program is in a foreground state, the application program management device processes the system application message through the application program; therefore, when the application program is in the background state, the data and the corresponding interface state do not need to be refreshed, and the data only needs to be updated when the application program is switched from the background state to the foreground state, so that the system load caused by monitoring the system application message in the background is reduced; when the attribute identifier of the system application message is a background identifier and the application program is in a background state, the application program management device processes the system application message through the application program, and when the attribute identifier of the system application message is an un-started identifier, the application program is awakened and processes the system application message even if the application program is not started.
By adopting the scheme, the application program management device can send the system application message to the application program according to the application state of the application program, so that the situation that when the application program is in a background state or an un-started state and the system application message needs to be processed in a foreground, the application program management device still processes the system application message through the application program to increase the load of the system and the occupied memory is avoided.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are all described as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
An embodiment of the present invention provides an application management device 30, as shown in fig. 3, including:
an obtaining unit 30, configured to obtain a system application message.
The system application message comprises an attribute identifier, wherein the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier.
It should be noted that the format of the system application message including the attribute identifier is as follows:
<intent-filter>
<action
android:name＝"android.intent.action.user-define-action-name"/>
<category android.intent.category.background/>
</intent-filter>
the action and the category define to constitute a system application message, where the background in the < category android.
The processing unit 31 is configured to determine an application program subscribed to the system application message after the obtaining unit 30 obtains the system application message.
The obtaining unit 30 is further configured to obtain an application state of the application program.
The processing unit 31 is further configured to process the system application message through the application program when the application state of the application program acquired by the acquiring unit 30 corresponds to the attribute identification.
Specifically, the obtaining unit 30 is specifically configured to query a status list, and determine an application status of the application program according to the status list.
The state list is generated by the operating system according to the application state of the application program, and the state list comprises the application state of the application program.
Further, the processing unit 31 is specifically configured to,
when the attribute identification comprises a foreground identification and the application program is in a foreground state, processing the system application message through the application program;
when the attribute identifier comprises a background identifier and the application program is in a background state, processing the system application message through the application program;
and when the attribute identification comprises an un-started identification and the application program is in an un-started state, processing the system application message through the application program.
It should be noted that, if the attribute identifier includes a foreground identifier, a background identifier, and an un-started identifier, the application management device may process the system application message through the application program no matter the application program is in any state.
Illustratively, when the attribute identifier of the system application message is a foreground identifier and the application program is in a foreground state, the application program management device processes the system application message through the application program; therefore, when the application program is in the background state, the data and the corresponding interface state do not need to be refreshed, and the data only needs to be updated when the application program is switched from the background state to the foreground state, so that the system load caused by monitoring the system application message in the background is reduced; when the attribute identifier of the system application message is a background identifier and the application program is in a background state, the application program management device processes the system application message through the application program, and when the attribute identifier of the system application message is an un-started identifier, the application program is awakened and processes the system application message even if the application program is not started.
Further, as shown in fig. 4, the application management device 30 further includes:
the query unit 33 is configured to query the application start list before the obtaining unit obtains the application state of the application.
A starting unit 34, configured to determine whether to start the application program according to the query result of the querying unit 33.
Wherein the application program comprises an application program configured by the system.
Optionally, the application launch list includes an identification of the application added by the user through the application management device.
Specifically, the application is configured with a start option provided to the user, and the user determines whether to start the application with the start of the system through the start option, for example, the setting option of the application includes an option of "automatically running this program when starting up", for the user, the "automatically running this program when starting up" in the setting option of the application is not selected, if the user wants the application to be automatically started up when starting up the system, the setting option is selected, at this time, the identifier of the application is added to the start-up list of the application, and if the user does not want the application to be started up when starting up the system, the setting option is not changed.
Optionally, the application adds the identification of the application through a system file access interface.
Specifically, the system file access interface supports the application program to access the system file, and the application program accesses the system file through the system file access interface, so that the identifier of the application program is added to the application program start list.
Specifically, when the system is started, the application program actively accesses the system file access interface, so that the addition of the identifier of the application program is realized, for example, for a user, the "auto-run this program" in the setting options of the application program is selected, if the user wants the application program to be automatically started when the system is started, the setting options are not changed, if the user does not want the application program to be started when the system is started, the setting options are deselected, and at this time, the identifier of the application program is also removed from the application program start list.
By adopting the application program management device, the application program management device can send the system application message to the application program according to the application state of the application program, so that the situation that when the application program is in a background state or an un-started state and the system application message needs to be processed in a foreground, the application program management device still processes the system application message through the application program to increase the load of the system and the occupied memory is avoided.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process and description of the application management device described above may refer to the corresponding process in the method embodiment described in the foregoing fig. 1, and details are not described herein again.
An embodiment of the present invention provides an application management device 50, as shown in fig. 5, where the application management device includes: a processor (processor)51, a communication Interface (Communications Interface)52, a memory (memory)53, and a communication bus 54; wherein, the processor 51, the communication interface 52 and the memory 53 complete mutual communication through the communication bus 54.
The processor 51 may be a central processing unit CPU or an application specific Integrated circuit asic or one or more Integrated circuits configured to implement embodiments of the present invention.
The memory 53 is used to store program code, which includes computer operating instructions. The memory 53 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The communication interface 52 is used for realizing connection communication between the devices.
The processor 51 executing program code for obtaining a system application message; the system application message comprises an attribute identifier, wherein the attribute identifier comprises at least one of a foreground identifier, a background identifier and an un-started identifier; after the system application message is obtained, determining an application program subscribed to the system application message, and obtaining an application state of the application program; when the application state of the application corresponds to the attribute identification, the system application message is processed by the application.
Optionally, the processor 51 is specifically configured to query a state list, where the state list is generated by an operating system according to an application state of the application program, the state list includes the application state of the application program, and determine the application state of the application program according to the state list.
Optionally, the processor 51 is specifically configured to, when the attribute identifier includes a foreground identifier and the application is in a foreground state, process the system application message through the application, when the attribute identifier includes a background identifier and the application is in a background state, process the system application message through the application, and when the attribute identifier includes an un-started identifier and the application is in an un-started state, process the system application message through the application.
Optionally, the processor 51 is further configured to, before obtaining the application state of the application, query the application start list by the application management device, and determine whether to start the application according to a query result.
Wherein the application program comprises an application program configured by the system.
Optionally, the application startup list includes an identifier of the application added by the user through the application management device, or an identifier of the application added by the application through the system file access interface.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (18)
1. A method for managing an application program, comprising:
the application program management equipment acquires a system application message; the system application message comprises an attribute identifier, and the attribute identifier is a foreground identifier;
after the application program management device obtains the system application message, determining an application program subscribed to the system application message, and obtaining an application state of the application program, wherein the application program comprises a first application program and a second application program;
the first application processes the system application message, wherein the first application is in the foreground;
the second application does not process the system application message, wherein the second application is in the background.
2. The method of claim 1, wherein obtaining the application state of the application comprises:
querying a state list, wherein the state list is generated by an operating system according to the application state of the application program, and the state list comprises the application state of the application program;
and determining the application state of the application program according to the state list.
3. The method of claim 1 or 2, wherein the application states include being in foreground, being in background, and not launched.
4. The method of claim 1, wherein prior to obtaining the application state of the application program, the method further comprises:
the application program management equipment inquires an application program starting list;
determining whether to start the application program according to the query result; wherein the application program comprises an application program configured by the system.
5. The method of claim 4, wherein the application launch list comprises an identification of the application added by the user via the application management device or an identification of the application added by the application via a system file access interface.
6. The method of claim 1, wherein the system application message comprises a broadcast of a power control message or a power on start message.
7. The method of claim 1, wherein the second application does not refresh the data and the corresponding interface state when the second application is in the background state, and updates the data when the second application is switched from the background state to the foreground state.
8. The method of claim 1, wherein the system application message comprises an attribute identifier, wherein the attribute identifier comprises at least one of a foreground identifier, a background identifier, and an un-launched identifier, and wherein the application management device processes the system application message according to the attribute identifier and the application state.
9. An application management apparatus, comprising:
the acquisition unit is used for acquiring a system application message; the system application message comprises an attribute identifier, and the attribute identifier is a foreground identifier;
the processing unit is used for determining application programs subscribed to the system application message after the acquisition unit acquires the system application message, wherein the application programs comprise a first application program and a second application program;
the obtaining unit is further configured to obtain an application state of the application program;
the processing unit is further configured to process the system application message by the first application, wherein the first application is in a foreground;
the processing unit is further configured to not process the system application message through the second application, wherein the second application is in the background.
10. The device according to claim 9, wherein the obtaining unit is specifically configured to query a state list, and determine the application state of the application program according to the state list, where the state list is generated by an operating system according to the application state of the application program, and the state list includes the application state of the application program.
11. The device of claim 9 or 10, wherein the application states include being in foreground, being in background, and not launched.
12. The apparatus according to claim 9, wherein the application management apparatus further comprises:
the query unit is used for querying an application program starting list before the acquisition unit acquires the application state of the application program;
the starting unit is used for determining whether to start the application program according to the query result of the query unit; wherein the application program comprises an application program configured by the system.
13. The device of claim 12, wherein the application launch list comprises an identification of the application added by the user via the application management device or an identification of the application added by the application via a system file access interface.
14. The apparatus of claim 9, wherein the system application message comprises a broadcast of a power control message or a power on start message.
15. The device of claim 9, wherein the second application does not refresh the data and the corresponding interface state when the second application is in the background state, and updates the data when the second application is switched from the background state to the foreground state.
16. The device of claim 9, wherein the system application message includes an attribute identifier, wherein the attribute identifier includes at least one of a foreground identifier, a background identifier, and an un-launched identifier, and wherein the application management device processes the system application message according to the attribute identifier and the application state.
17. An electronic device comprising a processor and a memory, the memory storing computer instructions that, when executed, cause the electronic device to perform the method of any of claims 1-8.
18. A storage medium storing computer instructions that, when executed, cause an electronic device to perform the method of any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810155140.4A CN108469985B (en) | 2013-12-31 | 2013-12-31 | Application program management method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810155140.4A CN108469985B (en) | 2013-12-31 | 2013-12-31 | Application program management method and device |
| CN201310752520.3A CN103744720B (en) | 2013-12-31 | 2013-12-31 | The management method and equipment of a kind of application program |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310752520.3A Division CN103744720B (en) | 2013-12-31 | 2013-12-31 | The management method and equipment of a kind of application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108469985A CN108469985A (en) | 2018-08-31 |
| CN108469985B true CN108469985B (en) | 2020-05-08 |
Family
ID=50501740
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810155140.4A Active CN108469985B (en) | 2013-12-31 | 2013-12-31 | Application program management method and device |
| CN201310752520.3A Active CN103744720B (en) | 2013-12-31 | 2013-12-31 | The management method and equipment of a kind of application program |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310752520.3A Active CN103744720B (en) | 2013-12-31 | 2013-12-31 | The management method and equipment of a kind of application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN108469985B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108469985B (en) * | 2013-12-31 | 2020-05-08 | 华为终端有限公司 | Application program management method and device |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0942366A2 (en) * | 1998-03-10 | 1999-09-15 | Lucent Technologies Inc. | Event-driven and cyclic context controller and processor employing the same |
| CN101615141A (en) * | 2008-06-26 | 2009-12-30 | 陈鹰 | A kind of method and application program scheduling module of carrying out application program scheduling |
| CN101916197A (en) * | 2010-07-22 | 2010-12-15 | 北京东土科技股份有限公司 | Method for controlling self-starting program of system |
| CN102955560B (en) * | 2011-08-25 | 2015-02-04 | 腾讯科技（深圳）有限公司 | Application program processing method and device |
| US9063775B2 (en) * | 2011-09-01 | 2015-06-23 | Microsoft Technology Licensing, Llc | Event aggregation for background work execution |
| CN103259825A (en) * | 2012-02-21 | 2013-08-21 | 腾讯科技（深圳）有限公司 | Method and device for message pushing |
| CN102779068A (en) * | 2012-07-10 | 2012-11-14 | 宇龙计算机通信科技(深圳)有限公司 | Mobile terminal and application program networking control method |
| CN108469985B (en) * | 2013-12-31 | 2020-05-08 | 华为终端有限公司 | Application program management method and device |
-
2013
- 2013-12-31 CN CN201810155140.4A patent/CN108469985B/en active Active
- 2013-12-31 CN CN201310752520.3A patent/CN103744720B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN108469985A (en) | 2018-08-31 |
| CN103744720B (en) | 2018-05-04 |
| CN103744720A (en) | 2014-04-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103826215B (en) | A kind of method and apparatus for carrying out Root authority management on the terminal device | |
| US9507604B2 (en) | Boot method and boot system | |
| EP2933723A1 (en) | Method, device and terminal equipment for cleaning up memory | |
| JP5821393B2 (en) | Information processing apparatus, activation method, program | |
| CN105824664A (en) | Application program startup monitoring method, device and terminal equipment | |
| US11907153B2 (en) | System and method for distributed subscription management | |
| US12093102B2 (en) | System and method for power state enforced subscription management | |
| US12211021B2 (en) | System and method for subscription based solution implementation | |
| CN108540509B (en) | Processing method and device of terminal browser, server and intelligent terminal | |
| US20230224216A1 (en) | System and method for subscription limitation enforcement in distributed system | |
| CN105260655A (en) | Application program starting protection method, device and system | |
| CN108959139A (en) | A kind of CPLD pin multiplexing method and device | |
| CN107395955A (en) | Method for determining power-on time sequence of camera module and user terminal | |
| US10284614B2 (en) | Method for downloading contents of electronic device and electronic device thereof | |
| CN106020426A (en) | A wake lock release method and device | |
| CN107391120A (en) | One kind starts control method, electronic equipment and computer-readable recording medium | |
| CN111897543A (en) | A software management method, device, management device and storage medium | |
| CN108469985B (en) | Application program management method and device | |
| WO2019100704A1 (en) | Starting method for multi-mode iot device, multi-mode iot device, and storage medium | |
| CN108595195B (en) | Application program updating method, device, terminal and storage medium | |
| WO2020113478A1 (en) | Address information processing method and apparatus, electronic device, and storage medium | |
| WO2016058188A1 (en) | Software upgrading method and apparatus applied to terminal and terminal | |
| CN115495161B (en) | Validation method, device and storage medium of BIOS option modification | |
| CN110413310A (en) | Program upgrade method and terminal device | |
| EP3674894B1 (en) | Processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Applicant after: HUAWEI DEVICE Co.,Ltd. Address before: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Applicant before: Huawei terminal (Dongguan) Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20210428 Address after: Unit 3401, unit a, building 6, Shenye Zhongcheng, No. 8089, Hongli West Road, Donghai community, Xiangmihu street, Futian District, Shenzhen, Guangdong 518040 Patentee after: Honor Device Co.,Ltd. Address before: Metro Songshan Lake high tech Industrial Development Zone, Guangdong Province, Dongguan City Road 523808 No. 2 South Factory (1) project B2 -5 production workshop Patentee before: HUAWEI DEVICE Co.,Ltd. |
|
| TR01 | Transfer of patent right | ||
| CP03 | Change of name, title or address |
Address after: Unit 3401, unit a, building 6, Shenye Zhongcheng, No. 8089, Hongli West Road, Donghai community, Xiangmihu street, Futian District, Shenzhen, Guangdong 518040 Patentee after: Honor Terminal Co.,Ltd. Country or region after: China Address before: 3401, unit a, building 6, Shenye Zhongcheng, No. 8089, Hongli West Road, Donghai community, Xiangmihu street, Futian District, Shenzhen, Guangdong Patentee before: Honor Device Co.,Ltd. Country or region before: China |
|
| CP03 | Change of name, title or address |