CN106648738B

CN106648738B - Method, device and terminal for managing personal applications

Info

Publication number: CN106648738B
Application number: CN201610885246.0A
Authority: CN
Inventors: 黄宏用
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2016-10-10
Filing date: 2016-10-10
Publication date: 2019-12-31
Anticipated expiration: 2036-10-10
Also published as: CN106648738A

Abstract

The embodiment of the invention discloses a method, a device and a terminal for managing personal applications, which relate to the technical field of communication, wherein the method comprises the following steps: acquiring account information in each personal application associated with the main application and/or the number of times of use of each personal application in a preset time period; configuring a correlation value between each sub-body application and the main application based on the account information and/or the using times; when a setting instruction of a main application input by a user is received, acquiring operation information acted in the main application by the user; updating the body application based on the operation information and the correlation value. The embodiment of the invention can manage the personal application through the main application according to the user requirement, and is convenient to operate.

Description

Method, device and terminal for managing personal applications

Technical Field

The invention relates to the technical field of communication, in particular to a method, a device and a terminal for managing personal application.

Background

With the development of the mobile internet, the user demands for applications in the terminal are more and more abundant. In the process of daily use of the terminal, a user needs to log in a same application at the same time through multiple account numbers, for example, for a microblog, the multiple account numbers of the user need to log in and use at the same time, or for a certain game, the multiple account numbers of the user need to log in at the same time to meet the requirements of convenient operations such as switching and trading.

At present, in order to meet the requirement that different accounts log in the same application at the same time, in a terminal, multiple same applications may be started, and different accounts may be logged in the multiple same applications, where the multiple same applications include a primary application and at least one separate application. However, in the course of implementing the prior art solution, the inventors have found that the prior art has the following drawbacks: when a user operates the main application to enable the main application to have a certain function or set the main application, if the user needs to set each of the split applications to have the same function as the main application, the user needs to operate the split applications one by one, which is very inconvenient to operate.

Disclosure of Invention

In view of this, embodiments of the present invention provide an application-based management method, an apparatus, and a terminal, which can manage a body-based application through a main application according to a user requirement, and are convenient to operate.

In a first aspect, an embodiment of the present invention provides a method for managing an application for self-assembly, including:

acquiring account information in each personal application associated with the main application and/or the number of times of use of each personal application in a preset time period;

configuring a correlation value between each sub-body application and the main application based on the account information and/or the using times;

when a setting instruction of a main application input by a user is received, acquiring operation information acted in the main application by the user;

updating the body application based on the operation information and the correlation value.

In a second aspect, an embodiment of the present invention further provides a device for managing a split application, including:

the account information and/or use frequency acquisition module is used for acquiring account information in each body application related to the main application and/or use frequency of each body application in a preset time period;

the association value configuration module is used for configuring association values of the individual applications and the main application based on the account information and/or the use times;

the operation information acquisition module is used for acquiring operation information acted in the main application by a user when a setting instruction of the main application input by the user is received;

and the updating module is used for updating the body application based on the operation information and the correlation value.

In a third aspect, an embodiment of the present invention provides a terminal, where the terminal integrates the split application management apparatus provided in the embodiment of the present invention.

According to the technical scheme provided by the embodiment of the invention, the correlation value of the personal application and the main application is determined through the account information in the personal application and/or the use times of the personal application, the personal application is updated through the correlation value and the acquired operation information acting on the main application, the personal application can be managed through the main application according to the needs of a user, and the operation is convenient.

Drawings

Other features, objects and advantages of the invention will become more apparent upon reading of the detailed description of non-limiting embodiments made with reference to the following drawings:

fig. 1 is a flowchart of a method for managing an application for self-assembly according to an embodiment of the present invention;

fig. 2 is a flowchart of another method for managing an application for individualization according to an embodiment of the present invention;

fig. 3 is a flowchart of another method for managing an avatar application according to an embodiment of the present invention;

fig. 4 is a block diagram of a split application management apparatus according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings.

Fig. 1 is a flowchart of a method for managing a personal application according to an embodiment of the present invention, where the method is performed by a personal application management device, the device is performed by software and/or hardware, and the device is configured in a terminal such as a mobile phone. As shown in fig. 1, the technical solution provided in this embodiment is as follows:

s110: the method comprises the steps of obtaining account information in each body-divided application related to a main application and/or the number of times of use of each body-divided application in a preset time period.

In this embodiment, the main application and the body-separated application corresponding to the main application are the same application program, and the main application and the body-separated application corresponding to the main application can run simultaneously. When a user opens the main application, the terminal generates a source process corresponding to the main application, and when the user clicks an icon of the split application to open the split application, the terminal generates the split process corresponding to the split application so as to realize that the source process and the split process run simultaneously, and if the user has a plurality of accounts, simultaneous login can be realized.

In this embodiment, account information of the user is stored under the installation path of each of the individual applications, wherein there may be one or more account information stored in each of the individual applications, and the account information in each of the individual applications may also be stored in other locations in the terminal, and may be set by the user.

In this embodiment, a file for recording the use information of the corresponding avatar application may also exist in the installation path of each avatar application. The use information comprises information such as time for starting the self-body application each time, closing time, use duration and the like, the use times of the self-body application in a preset time period can be counted by recording files of the use information of the self-body application, and the preset time is set by a user according to needs. The file for recording the use information of the divided application may also exist in other positions in the terminal. And, the record of the number of times of use for each individual application may also be in other forms.

In this embodiment, the main application and each of the individual applications are associated in advance, and the association may be established in the following manner: the identification information of the main application is associated with the identification information of each self-body application so as to realize the association between the main application and the self-body application, wherein the identification information comprises at least one of the following items: the name of the application, the icon of the application, and account information in the application. The method for establishing the association between the main application and each of the individual applications may be other methods, and the purpose of the association relationship between the main application and each of the individual applications may be achieved.

S120: and configuring a correlation value between each sub-body application and the main application based on the account information and/or the using times.

In this embodiment, configuring the association value with the master application for each of the split applications may be as follows: setting a first correlation value by a user according to the importance degree of account information in the personal application; or configuring a second correlation value between each self-body application and the main application according to the number of the using times, wherein the configured second correlation value between each self-body application and the main application is larger when the self-body application with more using times is used; or respectively endowing a weight value according to the account information and the using times, and determining the configured associated value with the main application according to the first associated value, the second associated value and the corresponding weight value.

It should be noted that, the association value with the primary application may also be configured for each of the individual applications based on other parameters in each of the individual applications, and is not limited to the account information and/or the number of times of use.

S130: when a setting instruction of the main application input by a user is received, operation information acted by the user in the main application is obtained.

In this embodiment, the operation information includes at least one of: setting information, function addition information, function deletion information, and control information. Wherein the setting information includes at least one of: a new message reminding mode, a page operation background and a privacy setting mode; the control information comprises information which is input by a user and used for controlling the playing of videos, audios or pictures.

In this embodiment, the setting instruction for the host application input by the user may be a setting operation for the host application by the user. For example, the user clicks a setting position, or the user makes a slide gesture on an operation interface of the main application. The setting instruction for the main application input by the user may be in other forms, and is not limited in form.

It should be noted that, in this embodiment, the operation information may further include other operation information when the user acts as the main application, the setting information may further include other information in the application, and the control information may further include information of other control applications input by the user.

S140: updating the body application based on the operation information and the correlation value.

In this embodiment, for example, the updating the body application based on the operation information and the association value includes: and when the correlation value of the target self-body application is larger than a preset threshold value, sending the operation information to the installation path of the target self-body application so as to update the target self-body application. Wherein, the size of the preset threshold value can be freely set by a user. Therefore, the personal application with the correlation value larger than the preset threshold value can be updated by setting the preset threshold value, and the personal application can be updated according to the needs of the user.

In this embodiment, if the operation information includes setting information, the setting information of the personal application can be updated; if the operation information comprises function adding information or function deleting information, when the main application adds the application function, the same application function can be added or deleted for the corresponding personal application; when the operation information includes the control information, when the user operates to play the picture, the video or the audio in the main application, the same picture, audio or video can be played in the corresponding body-separated application.

It should be noted that, in this embodiment, the main application and the corresponding body-separated application form a multi-open application set. The implementation manner of the multi-open application set may be various, and this embodiment is not particularly limited. For example, applications of different versions can be installed respectively, one version is used as a main application, and other versions are used as separate applications, wherein installation of the same application of different versions can be realized by decompiling and modifying an installation package (APK) file of the application and then installing the modified APK file; for another example, the method can be realized by applying third-party multi-open helper software for simulating user space and dynamically loading technology; as another example, this may be accomplished by modifying the system mechanism.

Preferably, the multiple application sets in this embodiment are implemented based on a multi-user mechanism, where the multi-user mechanism may specifically include a multi-user mechanism supported by an operating system in the terminal, such as a multi-user mechanism of an Android (Android) system and a multi-user mechanism of a Windows (WP) operating system of a mobile Phone.

The multiple-open application set is implemented based on a multi-user mechanism, and specifically, the implementation of the multiple-open application set based on the multi-user mechanism may include the following: the main application is installed under a main user, the body-separated application is installed under a slave user, and the main user comprises an access port for operating the body-separated application.

In one embodiment, the multi-user implementation mechanism of embodiments of the present invention includes the following logic:

1. multi-user management

a) The system defaults to have a master user, and the master user can create other new users (slave users) and delete and manage the new users;

b) common users (non-master users) and guest users, which may be collectively referred to as slave users;

c) the default master user id (identity Identification) is 0, and other newly added user ids are increased one by one from 10;

d) when the user is switched, a series of interface switching such as desktop reloading and the like can be realized;

e) the master user can limit the authorities of other users whether to be capable of making and receiving calls, short messages and the like.

For multi-user management, the slave users can be managed through the master user, the slave users comprise creation, deletion, authority setting and the like of the slave users, ID setting starts from the master user, the IDs of the new slave users are added in sequence and overlapped, and a series of interfaces such as desktops of the corresponding users are reloaded when the users are switched.

2. Multi-user installation, uninstallation applications

a) The default installed application can be installed to all created users, and application icons can be seen on desktops of other users;

b) the application installed in the master user is managed through the file, the application cannot be installed to other users, and the application icons cannot be seen on desktops of other users;

c) the system can specify userid (user identity) when installing and uninstalling the application, specify the application to be installed to a specified user, or uninstall the application at a specified user. Applications may also be installed for all users, or uninstalled.

d) When the user A unloads the application B, the application B still exists for other users, the application icon can be seen on the desktop, and the application B can be normally used on other users.

For multi-user installation and uninstallation of applications, the default installed applications are installed to all the created users (including a master user and a slave user), and application icons are generated on desktops of the users; the application installed through file management under the master user is only installed under the master user, and an application icon is generated on the desktop of the master user and is not installed under the slave user; the application installation/uninstallation can also be based on the user's specification of the user, and the user specifies the application installation/uninstallation in the master user and the slave user by specifying the user identity under a certain user, some users or all users; the same application is unloaded independently under each user, and the application of a certain user is unloaded without influencing the use of the application of other users.

3. User data management

a) User id directory related to system data: various system data stores corresponding to the users are stored, such as: desktop widget lists, setup databases, default application start policies, and the like.

b) User id directory related to application package data: and storing the application package catalog correspondingly installed by the user, and if the application operation generates data, storing the application data in the catalog.

c) System SD Card (Secure Digital Memory Card) catalog: it is not the same that each subscriber sees its sdcard directory, but only its sdcard directory.

For user data management, under a multi-user implementation mechanism, system data and application related data under each user are respectively stored under different data storage paths, for example, various system data under a certain user are stored under a specified first data storage path, and application related data such as an installed application package directory and application data generated by application operation are stored under a specified second data storage path; the data storage of each user is independent, and each user can only view own stored data, such as an own sdcard directory.

4. User rights management

a) After installation, the application applies various permissions (e.g.: read and store the catalogue authority, read and write the message authority, open the camera authority, etc.), will be divided into two parts, one part is insensitive to the authority, while employing and installing, the system allows the application to obtain the authority directly; some sensitive dangerous authorities, such as read-write short message authorities, prompt the user whether the application is allowed to obtain the authority or not when the application is used.

b) The system is independent and isolated for the authority of the same application at different users, the basic insensitive authority obtained by one application is directly obtained in each user after installation, and the partial sensitive dangerous authority is independent. For example: when the user 0 opens the WeChat, if the permission of reading and writing the short message is obtained, the system prompts whether the user allows the WeChat or not when the user 10 is switched to, and the user 0 does not need to be reminded because the WeChat obtains the permission. The same applies to other users.

For user authority management, when a certain user installs an application, an insensitive authority can directly obtain permission, and the sensitive authority needs to be obtained by permission of the user; under different users, the permission configurations of the same application are independent and isolated, and when the users switch, the sensitive permission of the application used for the first time needs to prompt the users whether to be entitled.

In one embodiment, the process by which the multi-open application set is implemented based on a multi-user mechanism can be described as follows:

assuming that a default user of the terminal is a master user, the user stores an installation package (APK) file, such as abc.apk, of the application ABC into the terminal by downloading from an application store or copying from other sources under the master user, and after the system installs the abc.apk under the master user, a desktop of the master user generates an icon of the master application ABC. When an avatar creation request for a master application ABC is detected under a master user, an avatar application is installed under a slave user (if no slave user exists, a slave user can be created, the creation process is completed without being perceived by the user, and no account and password are set by the user). After ABC is successfully installed, an appointed notification of 'successful installation' (identification is added in the notification) is sent to a master user, after a desktop under the master user receives the notification, an icon with the identification is generated to be distinguished from an icon of ABC of the master application, the icon can be used as an access port for operating the body application in the master user, after the icon is clicked, the system appoints ABC to be started under a slave user, a relevant process corresponding to ABC is also operated under the slave user, a human-computer interaction interface (abbreviated as an interface) of ABC is displayed under the master user, and the interface of ABC can also be used as an access port for operating the body application in the master user.

For the self-body application, the existence form of the access port in the master user may be various, and this embodiment is not particularly limited, for example, the access port may be a desktop icon including an application identifier, where the application identifier is used to distinguish the current self-body application from the master application and other self-body applications; the application identifier can be attached to the main application icon; an icon containing an application identifier which can also exist in a floating window form; but also items that exist in a notification center or the like.

The terminal user can realize the operation of the main application in the main user, and simultaneously can operate the corresponding personal application in the main user through the access port. It can be understood that the same master application may correspond to a plurality of separate applications, and each separate application is installed in a different slave user, so that each separate application is respectively operated in different slave users, and does not interfere with each other in the operation process.

Compared with third-party multi-open helper software, the multi-open application is realized based on a multi-user mechanism, so that the actions of pushing advertisements and stealing user privacy data by the third-party software are avoided, and the safety is higher; compared with the scheme that the main application and the split application are operated under the same user, the method reduces the process interference between different split applications or main applications under the same user, and avoids the function loss phenomenon caused by a complex operation environment.

For example, in this embodiment, the main application and the body-splitting application may also be distinguished by the user identifier userid and the application identifier Uid.

According to the method for managing the body-splitting application, the association value of the body-splitting application and the main application is determined through the account information in the body-splitting application and/or the use times of the body-splitting application, the body-splitting application is updated through the association value and the acquired operation information acting on the main application, the body-splitting application can be managed through the main application according to the needs of a user, and the operation is convenient.

Fig. 2 is a flowchart of another method for managing an avatar application according to an embodiment of the present invention, where on the basis of the above embodiment, optionally, the configuring, for each avatar application, an association value between the avatar application and the primary application based on the account information or the number of times of use includes:

based on the account information, searching a first associated value corresponding to the account information in a prestored first associated value mapping table; or

And searching a second correlation value corresponding to the using times in a pre-stored second correlation value mapping table based on the using times.

Therefore, the association value of the body-separated application and the main application is configured for the body-separated application through the account information or the using times, and the association value of the body-separated application and the main application can be determined according to the needs of the user, so that the purpose of updating the body-separated application according to the needs of the user is achieved.

Based on the above optimization, as shown in fig. 2, the technical solution provided in this embodiment is specifically as follows:

s210: acquiring account information in each sub-body application associated with the main application or the number of times of use of each sub-body application in a preset time period.

S220: and searching a first associated value corresponding to the account information in a pre-stored first associated value mapping table based on the account information.

In this embodiment, the first associated value mapping table includes account information, a first associated value, and a corresponding relationship between the account information and the first associated value. The first associated value mapping table is generated by the terminal, and when the user sets the first associated value for the account information, the terminal detects the operation of the first associated value input by the user to generate the first associated value mapping table. And when the user inputs a new first correlation value, the terminal completes the updating of the first correlation value mapping table.

For example, in this embodiment, if the number of the avatar applications associated with the host application is two, the account information in the avatar applications is a1b1c1 and a2b2c2, respectively, and some information in the avatar application with the account information of a1b1c1 is more important for the user, the user may set a larger first association value (for example, the larger first association value may be 10) for the avatar application with the account information of a1b1c1 and a smaller first association value (for example, the smaller first association value may be 6) for the avatar application with the account information of a2b2c2 in the association value setting function options. Some of the information in the avatar application may include contact information, asset information, etc., among others. When the terminal detects the operation of setting the first associated value by the user, a first associated value mapping table is generated and stored. The configuration mode of the first association value may also be other modes, and the purpose of configuring the first association value for the personal application based on the account information may be achieved, and the configuration mode is not limited to the above configuration mode.

S230: and searching a second correlation value corresponding to the using times in a pre-stored second correlation value mapping table based on the using times.

In this embodiment, the second associated value mapping table includes the number of times of use of each avatar application, the second associated value, and a corresponding relationship between the number of times of use and the second associated value. For example, the second association mapping table may be in the form shown in table 1, where table 1 is the second association mapping table, and as shown in table 1, the more times of use, the larger the second association value. The second associated value may be a relative value, and the second associated value may also be other expressions.

When the number of times of use of the self-service application is acquired, the second associated value with the main application can be found according to the second associated value mapping table.

TABLE 1

It should be noted that, in this embodiment, the configuration of the second correlation value of the split application is completed by exemplarily setting the larger second correlation value for the split application with the use times being large, but this embodiment is merely an example, and in other embodiments of the present invention, the split application with the use times being large may be set with the smaller second correlation value, or the configuration of the second correlation value of the split application may be completed in other manners.

S240: when a setting instruction of the main application input by a user is received, operation information acted by the user in the main application is obtained.

S250: updating the body application based on the operation information and the associated value, wherein the associated value comprises a first associated value or a second associated value.

It should be noted that, in the embodiment of the present invention, S220 and S230 may execute one of the steps, and not execute them simultaneously.

According to the method for managing the body-separated application, the association value of the body-separated application and the main application is configured for the body-separated application through the account information or the use times, and the association value of the body-separated application and the main application can be determined according to the needs of the user, so that the purpose of updating the body-separated application according to the needs of the user is achieved.

Fig. 3 is a flowchart of another method for managing an avatar application according to an embodiment of the present invention, where on the basis of the above embodiment, optionally, the configuring, for each avatar application, an association value between the avatar application and the primary application based on the account information and the number of times of use includes:

based on the account information, searching a first associated value corresponding to the account information in a prestored first associated value mapping table, and configuring a first weight value for the first associated value;

based on the using times, searching a pre-stored second associated value mapping table for a second associated value corresponding to the using times, and configuring a second weight value for the second associated value;

determining an association value of each of the split applications and the main application based on the first association value, the first weight value, the second association value and the second weight value;

the first weight value is determined based on the account information, and the second weight value is determined based on the number of times of use.

Therefore, the association value of the body-separated application and the main application is configured for the body-separated application through the account information in the body-separated application and the using times of the body-separated application, and the association value of the body-separated application and the main application can be determined according to the needs of a user, so that the purpose of updating the body-separated application according to the needs of the user is achieved.

Based on the above optimization, as shown in fig. 3, the technical solution provided by this embodiment is specifically as follows:

s310: the method comprises the steps of obtaining account information in each sub-body application related to a main application and the number of times of use of each sub-body application in a preset time period.

S320: based on the account information, a first associated value corresponding to the account information is searched in a pre-stored first associated value mapping table, and a first weight value is configured for the first associated value.

In this embodiment, the first weight value is determined based on the account information. When configuring the first weight value for the first associated value, different first weight values may be configured according to different account information, or the same first weight value may be uniformly configured for the first associated values corresponding to different account information. For example, table 2 is a corresponding table of one kind of account information, a first associated value and a first weight value, and table 3 is a corresponding table of another kind of account information, a first associated value and a first weight value. As shown in table 2, the account information is the personal applications a1b1c1 and a2b2c2, respectively, the corresponding first associated values are all different, and the first weight values configured for the first associated values are also different. The manner of determining the first weight value based on the account information may be as follows: and determining a first weight value according to the number of the contacts contained in the personal application under the corresponding account information, wherein the first weight value is larger when the number of the contacts under the target account information is larger. As shown in table 3, for the split applications with account information a1b1c1 and a2b2c2, the first weight values configured for the first associated values are the same. The configuration mode and the size of the specific first weight value can be set by a user according to needs.

TABLE 2

Account information	First correlation value	First weight value
			a1b1c1	10	0.8
a2b2c2	6	0.6

TABLE 3

Account information	First correlation value	First weight value
			a1b1c1	10	0.8
a2b2c2	6	0.8

S330: based on the using times, a second correlation value corresponding to the using times is searched in a pre-stored second correlation value mapping table, and a second weight value is configured for the second correlation value.

In the present embodiment, the second weight value is determined based on the number of times of use. When configuring the second weight value for the second associated value, different second weight values may be configured for the second associated value according to different numbers of times of use of the personal application. Or the same second weight value may be uniformly configured for the second associated values corresponding to different use times of each self-identification application.

For example, table 4 is a correspondence table of the number of times of use, the second correlation value, and the second weight value, and table 5 is another correspondence table of the number of times of use, the second correlation value, and the second weight value. As shown in table 4, the number of times of use of the split application is different, and the second weight values corresponding to the second correlation values are not completely the same. As shown in table 5, the number of times of use of the split application is different, but the second weight values corresponding to the second association values are the same.

TABLE 4

TABLE 5

S340: and determining the association value of each personal application and the main application based on the first association value, the first weight value, the second association value and the second weight value.

In this embodiment, referring to table 2 and table 4, for an avatar application with account information a1b1c1, if the number of times of use of the avatar application is 15, the association value between the avatar application and the main application is: 10 × 0.8+6 × 0.6 ═ 11.6. Referring to tables 3 and 5, the association value between the personal application and the primary application with account information a1b1c1 is: 10 × 0.8+6 × 0.5 ═ 11.

S350: updating the body application based on the operation information and the associated value, wherein the associated value comprises a first associated value or a second associated value.

According to the method for managing the body-separated application, the association value between the body-separated application and the main application is configured for the body-separated application through the account information in the body-separated application and the use times of the body-separated application, and the association value between the body-separated application and the main application can be determined according to the needs of the user, so that the purpose of updating the body-separated application according to the needs of the user is achieved.

Fig. 4 is a block diagram illustrating an architecture of a self-organizing application management apparatus according to an embodiment of the present invention, where the apparatus is configured to execute a self-organizing application management method. As shown in fig. 4, the apparatus includes an account information and/or usage number obtaining module 410, an association value configuring module 420, an operation information obtaining module 430, and an updating module 440.

The account information and/or use number obtaining module 410 is configured to obtain account information in each of the avatar applications associated with the primary application and/or use numbers of each of the avatar applications within a preset time period;

a correlation value configuration module 420, configured to configure a correlation value between each of the individual applications and the primary application based on the account information and/or the number of times of use;

an operation information obtaining module 430, configured to obtain operation information that the user acts on the primary application when receiving a setting instruction for the primary application, which is input by the user;

an updating module 440, configured to update the avatar application based on the operation information and the association value.

Further, the update module 440 is specifically configured to:

and when the correlation value of the target self-body application is larger than a preset threshold value, sending the operation information to the installation path of the target self-body application so as to update the target self-body application.

Further, the operation information includes at least one of:

setting information, function adding information, function deleting information, and control information;

wherein the setting information includes at least one of: a new message reminding mode, a page operation background and a privacy setting mode;

the control information comprises information which is input by a user and used for controlling the playing of videos, audios or pictures.

Further, the association value configuration module 420 is specifically configured to:

The embodiment provides a personal application management device, which determines a correlation value between a personal application and a main application through account information in the personal application and/or the number of times of using the personal application, updates the personal application through the correlation value and acquired operation information acting on the main application, can manage the personal application through the main application according to user needs, and is convenient to operate.

The present invention provides a terminal, which integrates the personal application management device provided in the foregoing embodiment, and fig. 5 is a schematic structural diagram of a terminal provided in the embodiment of the present invention, and as shown in fig. 5, the terminal may include: memory 501, a Central Processing Unit (CPU) 502, a peripheral interface 503, RF (radio frequency) circuitry 505, audio circuitry 506, speakers 511, a power management chip 508, an input/output (I/O) subsystem 509, a touch screen 512, other input/control devices 510, and an external port 504, which communicate via one or more communication buses or signal lines 507.

It should be understood that the illustrated terminal 500 is only one example of a terminal, and that the terminal 500 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The following describes the terminal for personal application management provided in this embodiment in detail, where the terminal is a mobile phone as an example.

A memory 501, the memory 501 being accessible by the CPU502, the peripheral interface 503, and the like, the memory 501 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other volatile solid state storage devices.

A peripheral interface 503, the peripheral interface 503 may connect input and output peripherals of the device to the CPU502 and the memory 501.

An I/O subsystem 509, which I/O subsystem 509 may connect input and output peripherals on the device, such as a touch screen 512 (equivalent to the screen in the above embodiment) and other input/control devices 510, to the peripheral interface 503. The I/O subsystem 509 may include a display controller 5091 and one or more input controllers 5092 for controlling other input/control devices 510. Where one or more input controllers 5092 receive electrical signals from or send electrical signals to other input/control devices 510, the other input/control devices 510 may include physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels. It is noted that the input controller 5092 may be connected to any one of: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.

A touch screen 512, which is an input interface and an output interface between the user terminal and the user, displays visual output to the user, which may include graphics, text, icons, video, and the like.

The display controller 5091 in the I/O subsystem 509 receives electrical signals from the touch screen 512 or transmits electrical signals to the touch screen 512. The touch screen 512 detects a contact on the touch screen, and the display controller 5091 converts the detected contact into an interaction with a user interface object displayed on the touch screen 512, that is, implements a human-computer interaction, and the user interface object displayed on the touch screen 512 may be an icon for running a game, an icon networked to a corresponding network, or the like. It is worth mentioning that the device may also comprise a light mouse, which is a touch sensitive surface that does not show visual output, or an extension of the touch sensitive surface formed by the touch screen.

The RF circuit 505 is mainly used to establish communication between the mobile phone and the wireless network (i.e., network side), and implement data reception and transmission between the mobile phone and the wireless network. Such as sending and receiving short messages, e-mails, etc. In particular, the RF circuitry 505 receives and transmits RF signals, also referred to as electromagnetic signals, through which the RF circuitry 505 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other devices. The RF circuitry 505 may include known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC (CODEC) chipset, a Subscriber Identity Module (SIM), and so forth.

The audio circuit 506 is mainly used to receive audio data from the peripheral interface 503, convert the audio data into an electric signal, and transmit the electric signal to the speaker 511.

The speaker 511 is used for restoring the voice signal received by the handset from the wireless network through the RF circuit 505 to sound and playing the sound to the user.

And a power management chip 508 for supplying power to the CPU502, the I/O subsystem 509, and the hardware connected to the peripheral interfaces and performing power management.

The CPU502 provided in the embodiment of the present invention may perform the following operations:

when a setting instruction of the main application input by a user is received, acquiring operation information acted by the user in the main application;

The terminal can execute the method provided by any embodiment of the invention, and has the corresponding functional module and beneficial effect of the execution method.

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for managing a split application, comprising:

when the correlation value of the target personal application is larger than a preset threshold value, the operation information is sent to the installation path of the target personal application so as to update the target personal application; the main application and the separate application corresponding to the main application are the same application program.

2. The method of claim 1, wherein the operational information comprises at least one of:

3. The method of claim 1,

configuring a correlation value between each sub-body application and the main application based on the account information or the using times, wherein the correlation value comprises:

4. The method according to claim 1, wherein the configuring, for each of the divided applications, an association value with the primary application based on the account information and the number of times of use comprises:

determining an association value of each of the split applications with the master application based on the first association value, the first weight value, the second association value, and the second weight value;

5. A device for managing an application for personal use, comprising:

and the updating module is used for sending the operation information to the installation path of the target body-splitting application to update the target body-splitting application when the correlation value of the target body-splitting application is larger than a preset threshold value, wherein the main application and the body-splitting application corresponding to the main application are the same application program.

6. The apparatus of claim 5, wherein the operational information comprises at least one of:

7. The apparatus of claim 5,

the correlation value configuration module is specifically configured to:

8. The apparatus according to claim 5, wherein the association value configuration module is specifically configured to:

9. A terminal characterized in that it integrates the split application management device of any of claims 5-8.