CN107026933B - Multi-open application message management method and device and intelligent terminal - Google Patents
Multi-open application message management method and device and intelligent terminal Download PDFInfo
- Publication number
- CN107026933B CN107026933B CN201610884747.7A CN201610884747A CN107026933B CN 107026933 B CN107026933 B CN 107026933B CN 201610884747 A CN201610884747 A CN 201610884747A CN 107026933 B CN107026933 B CN 107026933B
- Authority
- CN
- China
- Prior art keywords
- application
- message
- target application
- user
- pushing
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/043—Real-time or near real-time messaging, e.g. instant messaging [IM] using or handling presence information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72469—User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72484—User interfaces specially adapted for cordless or mobile telephones wherein functions are triggered by incoming communication events
Abstract
The embodiment of the invention discloses a message management method, a device and an intelligent terminal for multi-open application, wherein the multi-open application is realized based on a multi-user mechanism, and the method comprises the following steps: receiving a message aiming at the current multi-open application under a master user; acquiring an application identifier corresponding to the message; and pushing the message to a target application corresponding to the application identification. By adopting the technical scheme, the message can be pushed to the correct target application according to the application identifier, the main application and the individual application can be ensured to smoothly receive the message of the main application and the individual application, and the multi-open application is realized based on a multi-user mechanism.
Description
Technical Field
The embodiment of the invention relates to the technical field of intelligent terminals, in particular to a multi-open application message management method and device and an intelligent terminal.
Background
Along with the rapid development of the intelligent terminal technology, the scale of an intelligent terminal user group is continuously increased, and the use requirements of users on application programs in the intelligent terminal are more and more abundant.
At present, when a user uses a general intelligent terminal, if an application program is opened, the application program cannot be opened again, that is, only one account of the application program can be logged in. For many users, due to reasons of work, life and the like, a plurality of accounts are set for the same application program, and therefore such users may urgently want to log in the plurality of accounts on the same intelligent terminal at the same time. In order to meet the requirement that a user logs in multiple accounts of the same application program at the same time, in an existing application multi-open scheme, the application program of different versions is installed to achieve the purpose, the application programs of different versions receive various messages, such as system messages containing control instructions and instant messages of chatting or pushing, the messages need to be distinguished, management is difficult and easy to confuse, and the use of the user is influenced when the application program of the current version receives messages of application programs of other versions.
Disclosure of Invention
The embodiment of the invention aims to provide a multi-open application message management method, a multi-open application message management device and an intelligent terminal so as to optimize the existing multi-open application message management scheme.
In a first aspect, an embodiment of the present invention provides a method for managing messages of multiple applications, where the multiple applications are implemented based on a multi-user mechanism, and the method includes:
receiving a message aiming at the current multi-open application under a master user;
acquiring an application identifier corresponding to the message;
and pushing the message to a target application corresponding to the application identifier, wherein the target application comprises a main application and an individual application corresponding to the current multi-open application.
In a second aspect, an embodiment of the present invention provides a message management apparatus for multiple applications, where the multiple applications are implemented based on a multi-user mechanism, and the apparatus includes:
the message receiving module is used for receiving a message aiming at the current multi-open application under the master user;
an application identifier obtaining module, configured to obtain an application identifier corresponding to the message;
and the message pushing module is used for pushing the message to a target application corresponding to the application identifier, wherein the target application comprises a main application and an individual application corresponding to the current multi-open application.
In a third aspect, an embodiment of the present invention provides an intelligent terminal, where the intelligent terminal integrates the message management apparatus for multiple applications according to the embodiment of the present invention.
According to the message management scheme of the multi-open application provided by the embodiment of the invention, the message aiming at the current multi-open application is received under the master user, the application identifier corresponding to the message is obtained, and the message is pushed to the target application corresponding to the application identifier. By adopting the technical scheme, the message can be pushed to the correct target application according to the application identifier, the main application and the individual application can be ensured to smoothly receive the message of the main application and the individual application, and the multi-open application is realized based on a multi-user mechanism.
Drawings
Fig. 1 is a schematic flowchart of a message management method for multiple applications according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating another message management method for multiple applications according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating another message management method for multiple applications according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating another message management method for multiple applications according to an embodiment of the present invention;
fig. 5 is a block diagram illustrating a message management apparatus for multiple applications according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of an intelligent terminal according to an embodiment of the present invention.
Detailed Description
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings. 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 of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Fig. 1 is a flowchart illustrating a message management method for multiple applications according to an embodiment of the present invention, where the method may be executed by a message management device for multiple applications, where the message management device may be implemented by software and/or hardware, and may generally be integrated in an intelligent terminal. As shown in fig. 1, the method includes:
For example, the smart terminal in this embodiment may be a smart phone, a smart watch, a tablet computer, a smart television, and other devices.
For example, the multi-split application in this embodiment may specifically be an application that allows a user to log in a plurality of different accounts at the same time, and generally includes a main application and a split application, where the main application and all split applications corresponding to the main application form a multi-split application (set). For example, for wechat, a common wechat client only allows a user to log in one account a, and when the user needs to log in another account B, the user needs to log out the current account a and then log in the account B; the wechat client with the multi-open attribute can log in the account A and the account B at the same time, for example, the account A can be logged in through the main wechat, and the account B can be logged in through the individual wechat.
In this embodiment, the multi-open application is 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 an intelligent terminal, such as a multi-user mechanism of an Android (Android) system and a multi-user mechanism of a mobile Phone window (Windows Phone, WP) operating system.
Specifically, the implementation of the multi-open application based on the multi-user mechanism may include the following: the main application of the multi-open application is installed under a main user, the sub-application of the multi-open application is installed under a sub-user, and the main user comprises an access port used for operating the sub-application.
In one embodiment, the multi-user implementation mechanism of the present application 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 is implemented based on the multi-user mechanism can be described as follows:
assuming that a default user of the intelligent terminal is a master user, the user stores an installation package (APK) file such as abc.apk of application ABC in the intelligent terminal in a manner of 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 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 intelligent terminal user can realize the operation of the main application in the main user and can also operate the corresponding personal application through the access port in the main user. 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 self-body application may be distinguished by a user identifier userid and an application identifier Uid.
For example, the message in this embodiment may include a system message such as a control instruction, a call instruction, and a system notification, and may further include an instant message such as a chat or a push. Generally, the message may include attribute information such as a name or a code number of the multi-open application, and for example, when the current multi-open application is WeChat, the message may include information such as "weixin", and the system may identify, through the information, to which multi-open application the message is generated or sent.
And 102, acquiring an application identifier corresponding to the message.
For example, when the avatar application is established, an application identifier may be set for the established avatar application, and the application identifier is used to distinguish the current avatar application from the main application and other avatar applications, and may specifically be represented by uid. For example, one multi-division application includes a main application and two separate applications, the application identifier of the main application is u0, the application identifier of the first separate application is u10, and the application identifier of the second separate application is u 11.
In this embodiment, the message may directly include the application identifier, or may include information such as a code corresponding to the application identifier, and the corresponding application identifier may be obtained by analyzing the message.
And 103, pushing the message to a target application corresponding to the application identifier.
The target application comprises a main application and a split application corresponding to the current multi-open application.
For example, after the application identifier corresponding to the message is obtained, it may be determined according to the application identifier whether the message needs to be sent to the main application or a certain self-service application, and the target application may be understood as a final sending object of the message. And pushing the message to the target application to realize the smooth receiving of the message by the target application.
According to the message management method of the multi-open application, the message aiming at the current multi-open application is received under the master user, the application identification corresponding to the message is obtained, and the message is pushed to the target application corresponding to the application identification. By adopting the technical scheme, the message can be pushed to the correct target application according to the application identifier, the main application and the individual application can be ensured to smoothly receive the message of the main application and the individual application, and the multi-open application is realized based on a multi-user mechanism.
Fig. 2 is a schematic flow chart of another message management method for multiple applications according to an embodiment of the present invention, where the embodiment is optimized based on the foregoing embodiment, and in the embodiment, the step "pushing a message to a target application corresponding to an application identifier" is optimized as follows: acquiring the running state of the target application corresponding to the application identifier; and if the target application is in the running state, pushing the message to the target application.
Correspondingly, the method of the embodiment comprises the following steps:
And step 203, acquiring the running state of the target application corresponding to the application identifier.
In this embodiment, the running state may be specifically understood as running state information, including information indicating that the target application is in a running state and information indicating that the target application is not in a running state. Generally, a user may start an avatar application when the user needs to log in multiple accounts at the same time, that is, the avatar application is not necessarily in a running state in real time. However, when an application is not in the running state, such as WeChat 1, other people may also send a message to the account corresponding to WeChat 1. In this step, the running state of the target application corresponding to the application identifier is obtained, so that the message is subsequently processed correspondingly according to different running states.
And step 204, if the target application is in the running state, pushing the message to the target application.
It is understood that if the target application is in the running state, the target application should be able to successfully receive the message sent to the target application.
Optionally, if the target application is not in the running state, the message may be saved, and when the target application is started, the message may be pushed to the target application. The method has the advantages that if the target application is not in the running state, the user does not want to log in the account corresponding to the target application at the moment, the message is stored, the message is not pushed to the target application, and the trouble of the message to the user can be avoided. For example, if the main application of the multi-open application is a living account and the split application is a work account, the split application is generally not started during the vacation period of the user, and the message of the work account is not pushed, so that the vacation of the user is prevented from being influenced by the message.
Optionally, if the target application is not in the running state, the target application may be started, and the message may be pushed to the target application. The method has the advantages that important messages are prevented from being missed by the user, and the user can conveniently enter the target application to perform related operations.
Preferably, if the target application is not in a running state, the message may be pushed to the running application associated with the target application. The advantage of such setting is that, on the premise that the target application is not started, the user is prevented from missing important messages, and compared with the scheme of starting the target application, the message pushing efficiency is higher, because the process of starting the target application generally consumes a certain time, which affects the message pushing efficiency.
It should be noted that, the above message processing manners when the target application is not in the running state may be set by default by the system, or may be set by the user according to personal habits, and the setting of each multi-open application may be independent, or the setting of each individual application may be independent.
According to the message management method for the multi-open application, provided by the embodiment of the invention, after the target application corresponding to the message is determined, the running state of the target application is firstly obtained, and then different message processing strategies are adopted according to different running states, so that the message management efficiency is improved.
Fig. 3 is a flowchart of another message management method for multiple applications according to an embodiment of the present invention, where the present embodiment is optimized based on the foregoing embodiment, and in the present embodiment, after the step "pushing a message to a target application corresponding to an application identifier", the steps are added: and carrying out corresponding message reminding according to the message reminding strategy corresponding to the target application.
Correspondingly, the method of the embodiment comprises the following steps:
And step 304, performing corresponding message reminding according to the message reminding strategy corresponding to the target application.
For example, different applications may correspond to different message reminding policies, for example, the message reminding policies of the main application and the separate applications are different, and the message reminding policies of each two separate applications may also be different. The message reminding strategy can comprise specific reminding modes such as vibration, ringing, combination of vibration and ringing and the like, and can also comprise vibration intensity levels, different prompt tones, different prompt tone volumes and the like, different applications can correspond to different vibration intensity levels, different prompt tones and the same prompt tone with different volumes, and a user can know which application the current message belongs to according to different reminding modes, and then can decide whether to read or otherwise process the message immediately. It is understood that the message reminding policy can be set by default of the system or by the user according to personal habits, and the setting of each multi-open application can be independent, and the setting of each individual application can also be independent. Of course, a unified setting may also be performed, for example, the message reminding policies of the main applications of all the multiple applications are the same, and the message reminding policies of the sub-applications of all the multiple applications are the same.
The message reminding strategy can also comprise what reminding mode is adopted under what conditions, for example, when the target application is in the running state, the message reminding is carried out in a ringing mode, and when the target application is not in the running state, the message reminding is carried out in a vibration mode; for another example, when the target application is in the foreground running state, the message is reminded by using a ringing mode, and when the target application is in the background running state, the message is reminded by using a vibration mode.
According to the message management method for the multi-application, after the message is pushed to the target application, corresponding message reminding is carried out according to the message reminding strategy corresponding to the target application, so that a user can conveniently know an object targeted by the message in time, and further whether the message is read or processed immediately or not is determined, and the message management efficiency is further improved.
Fig. 4 is a flowchart of another message management method for multiple applications according to an embodiment of the present invention, where the present embodiment is optimized based on the foregoing embodiment, and in the present embodiment, after the step "pushing a message to a target application corresponding to an application identifier", the steps are added: and if the target application is detected to be in the background running state, switching the target application to the foreground.
Correspondingly, the method of the embodiment comprises the following steps:
And step 403, acquiring the running state of the target application corresponding to the application identifier.
Illustratively, after the message is pushed to the target application, a general user can read or further process the message, and at this time, if the target application is in a background running state, the message can be automatically switched to a foreground, so that the user can operate the target application conveniently.
And step 409, performing corresponding message reminding according to the message reminding strategy corresponding to the target application.
According to the message management method for the multi-open application, provided by the embodiment of the invention, after the message is pushed to the target application, if the target application is in the background running state, the target application can be automatically switched to the foreground, so that a user can conveniently operate the target application, and the management efficiency of the terminal application is improved.
Fig. 5 is a block diagram of a message management apparatus for multiple applications, which may be implemented by software and/or hardware, and is generally integrated in an intelligent terminal, and may manage messages of the multiple applications by executing a message management method for the multiple applications according to an embodiment of the present invention. Wherein the multi-open application is implemented based on a multi-user mechanism. As shown in fig. 5, the apparatus includes a message receiving module 501, an application identifier obtaining module 502, and a message pushing module 503.
The message receiving module 501 is configured to receive a message for a current multi-open application under a master user; an application identifier obtaining module 502, configured to obtain an application identifier corresponding to the message; a message pushing module 503, configured to push the message to a target application corresponding to the application identifier, where the target application includes a main application and an avatar application corresponding to the current multi-open application.
The message management device for multi-open application provided by the embodiment of the invention can push the message to the correct target application according to the application identifier, ensure that the main application and the individual application can smoothly receive the message of the main application and the individual application, and the multi-open application is realized based on a multi-user mechanism.
On the basis of the above embodiments, the multi-open application is implemented based on a multi-user mechanism, and includes: the main application of the multi-open application is installed under a main user, the sub-application of the multi-open application is installed under a sub-user, and the main user comprises an access port used for operating the sub-application.
On the basis of the above embodiment, the message pushing module may include an operation state obtaining unit and a message pushing unit. The running state acquiring unit is used for acquiring the running state of the target application corresponding to the application identifier; and the message pushing unit is used for pushing the message to the target application when the target application is in a running state.
On the basis of the foregoing embodiment, the message pushing unit is further configured to: and when the target application is not in a running state, pushing the message to the application in the running state associated with the target application.
On the basis of the above embodiment, the apparatus may further include: and the message reminding module is used for carrying out corresponding message reminding according to the message reminding strategy corresponding to the target application after pushing the message to the target application corresponding to the application identifier.
On the basis of the above embodiment, the apparatus may further include: and the switching module is used for switching the target application to a foreground if the target application is detected to be in a background running state after the message is pushed to the target application corresponding to the application identifier.
The embodiment of the invention provides an intelligent terminal which can comprise a multi-application message management device provided by any embodiment of the invention. Fig. 6 is a schematic structural diagram of an intelligent terminal according to an embodiment of the present invention, and as shown in fig. 6, the intelligent terminal may include: memory 601, a Central Processing Unit (CPU) 602, peripheral interfaces 603, RF (Radio Frequency) circuitry 605, audio circuitry 606, speakers 611, a power management chip 608, an input/output (I/O) subsystem 609, a touch screen 612, other input/control devices 610, and an external port 604, which communicate via one or more communication buses or signal lines 607.
It should be understood that the illustrated smart terminal 600 is only one example of a smart terminal, and that the smart terminal 600 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 in detail an intelligent terminal for managing messages of multiple applications provided in this embodiment, where the intelligent terminal is a mobile phone as an example.
A memory 601, the memory 601 being accessible by the CPU602, the peripheral interface 603, and the like, the memory 601 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 603, said peripheral interface 603 may connect input and output peripherals of the device to the CPU602 and the memory 601.
An I/O subsystem 609, the I/O subsystem 609 may connect input and output peripherals on the device, such as a touch screen 612 and other input/control devices 610, to the peripheral interface 603. The I/O subsystem 609 may include a display controller 6091 and one or more input controllers 6092 for controlling other input/control devices 610. Where one or more input controllers 6092 receive electrical signals from or transmit electrical signals to other input/control devices 610, the other input/control devices 610 may include physical buttons (push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels. It is noted that the input controller 6092 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 612, which touch screen 612 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 6091 in the I/O subsystem 609 receives electrical signals from the touch screen 612 or transmits electrical signals to the touch screen 612. The touch screen 612 detects a contact on the touch screen, and the display controller 6091 converts the detected contact into an interaction with a user interface object displayed on the touch screen 612, that is, to implement a human-computer interaction, where the user interface object displayed on the touch screen 612 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 605 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, RF circuitry 605 receives and transmits RF signals, also referred to as electromagnetic signals, through which RF circuitry 605 converts electrical signals to or from electromagnetic signals and communicates with a communication network and other devices. RF circuitry 605 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 606 is mainly used to receive audio data from the peripheral interface 603, convert the audio data into an electric signal, and transmit the electric signal to the speaker 611.
The speaker 611 is used to convert the voice signal received by the handset from the wireless network through the RF circuit 605 into sound and play the sound to the user.
And a power management chip 608 for supplying power and managing power to the hardware connected to the CPU602, the I/O subsystem, and the peripheral interface.
The CPU602 provided in the embodiment of the present invention can perform the following operations:
receiving a message aiming at the current multi-open application under a master user;
acquiring an application identifier corresponding to the message;
and pushing the message to a target application corresponding to the application identifier, wherein the target application comprises a main application and an individual application corresponding to the current multi-open application.
The multi-open application of the present embodiment is implemented based on a multi-user mechanism.
The message management device and the intelligent terminal for multi-open application provided in the above embodiments can execute the message management method for multi-open application provided in any embodiment of the present invention, and have corresponding functional modules and beneficial effects for executing the method. Technical details that are not described in detail in the above embodiments may be referred to a message management method for a multi-open application provided in any embodiment of the present invention.
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 (13)
1. A message management method for multi-open application is characterized in that a main application of the multi-open application is installed under a main user, a sub-application of the multi-open application is installed under a sub-user, and the main user comprises an access port for operating the sub-application, and the method comprises the following steps:
receiving a message aiming at the current multi-open application under a master user;
acquiring an application identifier corresponding to the message;
and pushing the message to a target application corresponding to the application identifier, wherein the target application comprises a main application and an individual application corresponding to the current multi-open application.
2. The method of claim 1, wherein pushing the message to a target application corresponding to the application identifier comprises:
acquiring the running state of the target application corresponding to the application identifier;
and if the target application is in a running state, pushing the message to the target application.
3. The method of claim 2, further comprising:
if the target application is not in a running state, pushing the message to an application in a running state associated with the target application; or the like, or, alternatively,
if the target application is not in the running state, the message is saved, and when the target application is started, the message is pushed to the target application; or the like, or, alternatively,
and if the target application is not in the running state, starting the target application and pushing the message to the target application.
4. The method of claim 1, further comprising, after pushing the message to a target application corresponding to the application identification:
and performing corresponding message reminding according to the message reminding strategy corresponding to the target application.
5. The method of claim 1, wherein the message alert policy comprises a message alert mode taken at different operating states.
6. The method of claim 1, further comprising, after pushing the message to a target application corresponding to the application identification:
and if the target application is detected to be in a background running state, switching the target application to a foreground.
7. A message management apparatus for multiple applications, wherein a master application of the multiple applications is installed under a master user, and a separate application of the multiple applications is installed under a slave user, the master user including an access port for operating the separate application, the apparatus comprising:
the message receiving module is used for receiving a message aiming at the current multi-open application under the master user;
an application identifier obtaining module, configured to obtain an application identifier corresponding to the message;
and the message pushing module is used for pushing the message to a target application corresponding to the application identifier, wherein the target application comprises a main application and an individual application corresponding to the current multi-open application.
8. The apparatus of claim 7, wherein the message pushing module comprises:
the running state acquisition unit is used for acquiring the running state of the target application corresponding to the application identifier;
and the message pushing unit is used for pushing the message to the target application when the target application is in a running state.
9. The apparatus of claim 8, wherein the message pushing unit is further configured to:
if the target application is not in a running state, pushing the message to an application in a running state associated with the target application; or the like, or, alternatively,
if the target application is not in the running state, the message is saved, and when the target application is started, the message is pushed to the target application; or the like, or, alternatively,
and if the target application is not in the running state, starting the target application and pushing the message to the target application.
10. The apparatus of claim 7, further comprising:
and the message reminding module is used for carrying out corresponding message reminding according to the message reminding strategy corresponding to the target application after pushing the message to the target application corresponding to the application identifier.
11. The apparatus of claim 10, wherein the message alert policy comprises a message alert mode taken in different operating states.
12. The apparatus of claim 7, further comprising:
and the switching module is used for switching the target application to a foreground if the target application is detected to be in a background running state after the message is pushed to the target application corresponding to the application identifier.
13. An intelligent terminal, characterized in that the intelligent terminal integrates the message management device of the multi-open application according to any one of claims 7-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610884747.7A CN107026933B (en) | 2016-10-10 | 2016-10-10 | Multi-open application message management method and device and intelligent terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610884747.7A CN107026933B (en) | 2016-10-10 | 2016-10-10 | Multi-open application message management method and device and intelligent terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107026933A CN107026933A (en) | 2017-08-08 |
| CN107026933B true CN107026933B (en) | 2020-03-10 |
Family
ID=59525096
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610884747.7A Active CN107026933B (en) | 2016-10-10 | 2016-10-10 | Multi-open application message management method and device and intelligent terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107026933B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108519922B (en) * | 2018-04-12 | 2022-07-12 | 珠海市魅族科技有限公司 | Information pushing method and device, terminal equipment and computer readable storage medium |
| CN108536512B (en) * | 2018-04-17 | 2021-03-26 | Oppo广东移动通信有限公司 | Interface switching method and device and terminal equipment |
| CN115129196A (en) * | 2018-07-31 | 2022-09-30 | 华为技术有限公司 | Application icon display method and terminal |
| CN109144341A (en) * | 2018-08-10 | 2019-01-04 | 维沃移动通信有限公司 | A kind of application operating method and mobile terminal |
| CN110147176B (en) * | 2019-05-13 | 2022-10-25 | Oppo广东移动通信有限公司 | Control method and device for touch screen, storage medium and electronic equipment |
| CN110610080B (en) * | 2019-09-19 | 2022-02-22 | 武汉统信软件技术有限公司 | Application isolation implementation method, mobile terminal, computer equipment and storage medium |
| WO2022105359A1 (en) * | 2020-11-23 | 2022-05-27 | 深圳传音控股股份有限公司 | Mobile terminal control method, mobile terminal and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103970575A (en) * | 2014-05-22 | 2014-08-06 | 广东欧珀移动通信有限公司 | Method and device for quickly starting application program in mobile terminal |
| CN104199734A (en) * | 2014-09-12 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Android smart terminal based application multi-run management method and system |
| WO2016094253A1 (en) * | 2014-12-08 | 2016-06-16 | Google Inc. | Multi-purpose application launching interface |
| CN105933546A (en) * | 2016-06-29 | 2016-09-07 | 宇龙计算机通信科技(深圳)有限公司 | Message notification method and apparatus, and terminal |
| CN105975156A (en) * | 2016-05-09 | 2016-09-28 | 北京小米移动软件有限公司 | Application interface display method and device |
-
2016
- 2016-10-10 CN CN201610884747.7A patent/CN107026933B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103970575A (en) * | 2014-05-22 | 2014-08-06 | 广东欧珀移动通信有限公司 | Method and device for quickly starting application program in mobile terminal |
| CN104199734A (en) * | 2014-09-12 | 2014-12-10 | 上海斐讯数据通信技术有限公司 | Android smart terminal based application multi-run management method and system |
| WO2016094253A1 (en) * | 2014-12-08 | 2016-06-16 | Google Inc. | Multi-purpose application launching interface |
| CN105975156A (en) * | 2016-05-09 | 2016-09-28 | 北京小米移动软件有限公司 | Application interface display method and device |
| CN105933546A (en) * | 2016-06-29 | 2016-09-07 | 宇龙计算机通信科技(深圳)有限公司 | Message notification method and apparatus, and terminal |
Non-Patent Citations (1)
| Title |
|---|
| android 5.0 创建多用户 双开多开应用;small_role;《https://blog.csdn.net/small_role/article/details/51745307》;20160623;1-3 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107026933A (en) | 2017-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107026933B (en) | Multi-open application message management method and device and intelligent terminal | |
| CN106484547B (en) | Multi-open application management method and device and terminal | |
| CN107402835B (en) | Application program exception handling method and device, storage medium and mobile terminal | |
| CN106445612B (en) | Method and device for opening application and mobile terminal | |
| CN107844342B (en) | Control method and device for keeping application program alive, storage medium and mobile terminal | |
| CN106445647B (en) | Open the data manipulation method, device and mobile terminal of application more | |
| CN106484518B (en) | Display method and device of multi-open application and terminal | |
| CN109508198B (en) | Application program installation method and device, storage medium and terminal | |
| CN108710515B (en) | Application preloading method and device, storage medium and terminal | |
| CN106484478B (en) | A kind of method, device and mobile terminal creating application of attending to anything else | |
| CN106484538B (en) | Memory control method and device of terminal equipment and terminal equipment | |
| CN109408465B (en) | File attribution information recording method, device, storage medium and terminal | |
| CN107831886B (en) | Control method and device for associated starting application, storage medium and intelligent terminal | |
| CN107943270B (en) | Application service control method and device, storage medium and mobile terminal | |
| CN110442426B (en) | Password resetting method, device and storage medium | |
| CN106648736B (en) | A kind of control method of application, device and mobile terminal | |
| CN106502732B (en) | Application closing method and device and intelligent terminal | |
| CN106648737B (en) | A kind of control method of application, device and mobile terminal | |
| CN106357667B (en) | Account management method and device for split application in multi-open application and intelligent terminal | |
| CN106445706B (en) | Open the data transmission method, device and mobile terminal of application more | |
| CN106484514B (en) | Multi-open application operation management method and device and intelligent terminal | |
| CN106648738B (en) | Method, device and terminal for managing personal applications | |
| CN106484482B (en) | Method and device for managing split application in multi-open application and intelligent terminal | |
| CN107885588B (en) | Application service control method and device, storage medium and mobile terminal | |
| CN106484419A (en) | Information searching method, device and mobile terminal in a kind of application program |
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: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant after: OPPO Guangdong Mobile Communications Co., Ltd. Address before: Changan town in Guangdong province Dongguan 523860 usha Beach Road No. 18 Applicant before: Guangdong Opel Mobile Communications Co., Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |