Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are illustrative only and should not be construed as limiting the invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
As will be appreciated by those skilled in the art, a "terminal" as used herein includes both devices having a wireless signal receiver, which are devices having only a wireless signal receiver without transmit capability, and devices having receive and transmit hardware, which have devices having receive and transmit hardware capable of two-way communication over a two-way communication link. Such a device may include: a cellular or other communication device having a single line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (Personal Communications Service), which may combine voice, data processing, facsimile and/or data communication capabilities; a PDA (Personal Digital Assistant), which may include a radio frequency receiver, a pager, internet/intranet access, a web browser, a notepad, a calendar and/or a GPS (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other device having and/or including a radio frequency receiver. As used herein, a "terminal" or "terminal device" may be portable, transportable, installed in a vehicle (aeronautical, maritime, and/or land-based), or situated and/or configured to operate locally and/or in a distributed fashion at any other location(s) on earth and/or in space. As used herein, a "terminal Device" may also be a communication terminal, a web terminal, a music/video playing terminal, such as a PDA, an MID (Mobile Internet Device) and/or a Mobile phone with music/video playing function, or a smart tv, a set-top box, etc.
The inventor of the present invention considers that, taking the first and second container systems in the multi-operation system of the intelligent terminal as an example, for the application of the second container system, a shortcut application corresponding to the application may be preset in the first container system, and an icon of the shortcut application may be set on the desktop of the first container system. After the first container system receives a click event of a user for the icon, the shortcut application takes the identification codes of the first container system and the second container system as the identification codes of a source system and a target system respectively, and the identification codes and a starting command of the application are packaged into a data packet and sent to the master control system; the main control system switches the first container system from a foreground to a background, and sends a starting command to the second container system after switching the second container system to which the application belongs to the foreground; the second container system launches the application in accordance with the received launch command. The method and the device have the advantages that a user does not need to spend a large amount of time to memorize which container system the application belongs to, or actively execute the operation of switching the container systems, and the application in the second container system can be controlled in the first container system, namely, the cross-system application control is realized. The memory burden or the operation burden of the user is greatly reduced, convenience is brought to the user, and the user experience is improved.
The technical solution of the embodiments of the present invention is specifically described below with reference to the accompanying drawings.
The intelligent terminal of the embodiment of the invention can be terminal equipment such as an intelligent mobile phone, a tablet personal computer and the like. A schematic diagram of a framework of an internal structure of the intelligent terminal is shown in fig. 1, and includes: a host system 101 and at least two operating systems.
The application scenario of the embodiment of the invention is kernel lightweight virtualization realized based on a Linux Container virtualization technology and a multi-isolation system realized based on the virtualization technology.
In the embodiment of the present invention, the operating system may be a Linux operating system or a Unix operating system in the conventional sense, or an Android system, an Ubuntu system, a Meego system, or the like derived based on the Linux operating system; the multi-isolation system realized based on the Linux Container virtualization technology is an operating system of the above kind that can run on the intelligent terminal.
Both of the at least two operating systems described above may specifically be container-based operating systems (hereinafter referred to simply as container systems). The container system may be arranged according to the following method: more than two containers are created in the intelligent terminal by utilizing a Linux container virtualization technology, and one operating system is installed and operated in each container. Each container is configured with an independent hardware resource access authority configuration, and the container system can independently access hardware resources, such as CPUs, IO (input output) devices, and the like. The container system can be configured with a set of independent complete system programs and application programs; thereby isolating the container systems from each other.
The main control system 101 includes a kernel, a main management program and a multi-system control program. The kernel may specifically be a Linux-based kernel, such as kernel. The main control system 101 is mainly used for performing foreground and background switching on the container systems, transmitting information between the container systems, and the like, and specific functions are described in detail later.
In the intelligent terminal according to the embodiment of the present invention, the identifier and the identification code of each container system are stored in advance and are shared by the main control system 101 and each container system. For example, the identification codes 1 and 2 of the container system are respectively stored corresponding to the identifications android and syberos of the container system; the identification code 5 of the container system is stored corresponding to the identification all representing all the container systems in the intelligent terminal. The master control system 101 and each container system may access the corresponding stored identification and identification codes of the container system.
Preferably, in the main control system 101 or each container system according to the embodiment of the present invention, the identifier and the identification code of each container system in the intelligent terminal may be respectively stored in advance.
The following takes the first container system 102 and the second container system 103 in the multi-container system of the embodiment of the present invention as an example, and specifically describes the technical solution of the embodiment of the present invention.
Before the intelligent terminal implements the cross-system application control method, for the application to be installed in the second container system 103, the shortcut application corresponding to the application is determined, and the identifier of the determined shortcut application and the identifier of the application are correspondingly stored.
Preferably, the intelligent terminal may use an identifier (e.g. name) of the application as an identifier of the shortcut application, that is, the application and the corresponding shortcut application have the same identifier.
The embodiment of the invention provides a method for setting icons of shortcut applications corresponding to applications of a second container system 103 in a desktop of a first container system 102, wherein a flow chart of the method is shown in fig. 2 and comprises the following steps:
s201: when the application is installed in the second container system 103, the identification code of the first container system 102 is taken as the identification code of the target system according to the user setting information or the predetermined policy, and is packaged into a data packet together with the installation request of the shortcut application and sent to the master control system 101.
Specifically, when the second container system 103 receives an installation request for installing an application into the system, user setting information or a predetermined policy pre-stored in the intelligent terminal is acquired, and whether the user setting information or the predetermined policy relates to the application is determined.
Wherein, the user setting information or the predetermined policy may include: the shortcut application corresponding to the application is installed into the first container system 102. Preferably, the user setting information or the predetermined policy may include: a shortcut application that identifies a correspondence to the identification of the application is installed into the first container system 102.
And when the determination result is that the application is involved in time, the second container system 103 installs the application into the system according to the installation package of the application, and searches out the identifier of the shortcut application corresponding to the application from the identifier of the application and the identifier of the shortcut application which are pre-stored in the intelligent terminal correspondingly. At this point, the second container system 103 may determine that the application supports cross-system control.
When the determination result is that the application is not involved, the second container system 103 may install the application into the system according to the installation package of the application, without searching for the identifier of the shortcut application corresponding to the application. At this point, the second container system 103 may determine that the application does not support cross-system control.
Alternatively, the second container system 103 may attempt to resolve the identification of the shortcut application corresponding to the application from the installation package of the application.
When the second container system 103 analyzes the identifier of the shortcut application corresponding to the application from the installation package of the application, it can be determined that the application supports cross-system control; conversely, it may be determined that the application does not support cross-system control.
The second container system 103 generates an installation request of the shortcut application according to the identification of the application or the identification of the shortcut application corresponding to the application. Preferably, the second container system 103 carries the identity of the application, or the identity of the shortcut application, in the installation request of the shortcut application.
The second container system 103 finds the identification code of the first container system 102 based on the user setting information or the identification of the first container system 102 related to the predetermined policy.
The second container system 103 packages the identification code of the first container system 102 as the identification code of the target system together with the installation request of the shortcut application in a data packet and transmits the data packet to the master control system 101.
Preferably, the second container System 103 packages the identifier of the first container System 102 as the identifier of the target System, together with the installation request of the shortcut application, into a data packet, and then calls a container service (container-service) module or a System manager (System-manager) in the second container System 103; the container service module or the system manager sends the packet to the ncm (namespace container master) device node of the host system 101 through the ncs (namespace container slave) device node of the second container system 103. The ncs and ncm device nodes can be represented as/dev/ncs and/dev/ncm files.
S202: the main control system 101 receives the data packet, and sends an installation request of the shortcut application in the received data packet to the first container system 102 according to the identification code of the target system in the received data packet.
Specifically, after receiving the data packet sent by the second container system 103 in step S201, the main control system 101 analyzes the identification code of the first container system 102, which is the identification code of the target system, and the installation request of the shortcut application from the received data packet.
The main control system 101 sends the installation request of the parsed shortcut application to the first container system 102 according to the parsed identification code of the first container system 102.
Preferably, the master control system 101 determines the identifier of the first container system 102 corresponding to the analyzed identifier of the first container system 102; and sending the installation request of the analyzed shortcut application to the first container system 102 according to the identification of the first container system 102.
Preferably, a Master-manager module in the Master system 101 listens to ncm device nodes in the Master system 101. After the main management module receives the data packet sent by the second container system 103 through ncm device nodes, the identification code of the first container system 102 serving as the identification code of the target system and the installation request of the shortcut application are analyzed from the received data packet; and sending the installation request of the analyzed shortcut application to the ncs equipment node in the first container system 102 according to the analyzed identification code of the first container system 102.
S203: the first container system 102 installs an icon of the shortcut application in a desktop of the first container system 102 according to the received installation request of the shortcut application.
The first container system 102 stores in advance installation packages of a plurality of shortcut applications. The installation package of the shortcut application comprises the following components: an icon of the shortcut application.
For the shortcut application corresponding to the application in the second container system 103, the icon of the shortcut application specifically includes: a LOGO of the second container system 103, and a word representing the name of the application. For example, icons for shortcut applications include: LOGO as syberos of the second container system 103, and "secure note" indicating a name of an application in the syberos.
The first container system 102 correspondingly stores, for each shortcut application, an identification of the shortcut application, an identification of an application corresponding to the shortcut application, and an installation package of the shortcut application.
In this step, after receiving the installation request of the shortcut application sent by the main control system 101, the first container system 102 analyzes the identifier of the shortcut application from the installation request.
Or, the first container system 102 parses the identifier of the application from the installation request, and determines the identifier of the shortcut application corresponding to the identifier of the application from the identifiers of the corresponding stored applications and the identifiers of the shortcut applications.
The first container system 102 determines a pre-stored installation package corresponding to the identifier of the shortcut application according to the identifier of the shortcut application in the installation request or the determined identifier of the shortcut application.
The first container system 102 installs the shortcut application corresponding to the application in the second container system 103 into the first container system 102 according to the determined installation package, and sets the icon of the shortcut application into the desktop of the first container system 102.
Preferably, first container system 102 invokes its container service module to listen for ncs device nodes in first container system 102. After receiving an installation request of a shortcut application sent to the ncs device node by the main control system 101 through the container service module, the first container system 102 analyzes an identifier of the shortcut application from the installation request, or determines the identifier of the shortcut application according to information analyzed from the installation request; further determining an installation package corresponding to the identifier of the shortcut application; and installing the shortcut application corresponding to the application in the second container system 103 into the first container system 102 according to the determined installation package, and setting the icon of the shortcut application into the desktop of the first container system 102.
Those skilled in the art can understand that through the above steps S201 to S203, the intelligent terminal in the embodiment of the present invention installs an application in the second container system 103; a shortcut application corresponding to an application in the second container system 103 is installed in the first container system 102, and an icon of the shortcut application is set on a desktop of the first container system 102. Since the icon of the shortcut application includes LOGO of the second container system 103 and text representing the name of the application, the user can easily recognize that the icon of the shortcut application corresponds to the application in the second container system 103.
Based on the application installed in the second container system 103 and the shortcut application installed in the first container system 102 and corresponding to the application, the embodiment of the present invention provides a cross-system application control method, a flowchart of which is shown in fig. 3a, and includes the following steps:
s301: the first container system 102 runs a display desktop; icons of shortcut applications corresponding to the applications in the second container system 103 are arranged in the desktop; and after receiving the click event of the icon of the shortcut application, operating the shortcut application.
Specifically, when the first container system 102 is in foreground operation, a desktop of the first container system 102 is displayed on a screen of the intelligent terminal; icons of shortcut applications corresponding to the applications in the second container system 103 are provided in the desktop.
Wherein the icon of the shortcut application includes a LOGO of the second container system 103 and a text indicating a name of the application, which is convenient for the user to recognize that the icon corresponds to the application in the second container system 103.
The first container system 102 starts the running shortcut application after receiving a click event for an icon of the shortcut application, which is input by a user, through a touch device in the intelligent terminal.
Preferably, after acquiring the designated gesture input by the user through a camera in the intelligent terminal, the first container system 102 confirms that a click event for an icon of the shortcut application input by the user is received, and starts to run the shortcut application.
Preferably, after the first container system 102 collects a designated moving track made by the user carrying the intelligent terminal through a sensor in the intelligent terminal, it confirms that a click event for an icon of the shortcut application input by the user is received, and starts to run the shortcut application.
S302: the shortcut application in the first container system 102 packages the identifiers of the first and second container systems as identifiers of the source system and the target system, respectively, together with the start command of the application into a data packet, and sends the data packet to the main control system 101.
The first container system 102 starts the running shortcut application in step S301, determines the identifier of the application corresponding to the identifier of the shortcut application in this step, and carries the determined identifier of the application in the start command of the application.
The data packet in the embodiment of the invention comprises: an identification code of the source system, an identification code of the target system, and the content.
The shortcut application packages the identification codes of the first container system 102 and the second container system 103 as the identification codes of the source system and the target system, respectively, together with a start command of the application as the content into a data packet, and transmits the data packet to the main control system 101.
Preferably, the shortcut application calls a container service module in the first container system 102, and the container service module sends the data packet in this step to the ncm device node in the main control system 101 through the ncs device node in the first container system 102.
Preferably, after the shortcut application packages the data packet, the container service invocation request is sent to the first container system 102. After receiving the container service calling request of the shortcut application, the first container system 102 calls a container service module 522; the data packet encapsulated by the shortcut application is sent to the ncm device node in the main control system 101 through the ncs device node in the first container system 102.
S303: the main control system 101 receives the data packet, switches the first container system 102 from the foreground to the background according to the identification codes of the source system and the target system in the received data packet and the start command of the application, and sends the start command of the application to the second container system 103 after switching the second container system 103 to the foreground.
Specifically, the master control system 101 receives the data packet transmitted by the first container system 102.
Preferably, the master control system 101 receives the data packet sent by the first container system 102 through the ncm device node in the master control system 101 according to its master management module.
After analyzing the identification codes of the source system and the target system from the received data packet, the main control system 101 determines the identification of the first container system 102 corresponding to the identification code of the source system and the identification of the second container system 103 corresponding to the identification code of the target system according to the identification and the identification code of the container system which are stored correspondingly in advance.
Preferably, when the master control system determines that the identifier of the container system corresponding to the identifier of the source system in the data packet is the identifier of the first container system 102, it determines that the data packet sent by the first container system 102 is received.
The kernel master control system 101 searches for pre-recorded foreground and background information of the first container system 102 and the second container system 103 according to the application start command parsed from the received data packet.
After determining that the first container system 102 and the second container system 103 are respectively located in the foreground and the background according to the search result, the main control system 101 sends the start command of the application parsed from the received data packet to the second container system 103 according to the identifier of the second container system 103 serving as the target system.
Preferably, after the main control system 101 determines that the first container system 102 and the second container system 103 are respectively located in the foreground and the background, the main management module in the main control system 101 is called according to the identifier of the second container system 103 serving as the target system; the main management module sends the start command of the application in the data packet to the ncs device node in the second container system 103 through the ncm device node in the main control system 101.
S304: the second container system 103 starts the application according to the received start command.
Specifically, the second container system 103 receives a start command of the application transmitted by the master control system 101.
Preferably, the second container system 103 receives, according to the container service module thereof, a start command of the application sent by the main control system 101 through the ncs device node in the second container system 103.
The second container system 103 parses the identifier of the application from the received start command of the application, and starts to run the application according to the parsed identifier.
Preferably, after the second container system 103 is switched from the background to the foreground in step S303 and before the running application is started, a screen locking interface is displayed on the screen of the smart terminal, and an unlocking password dialog box is displayed in the screen locking interface. The second container system 103 verifies the received password after receiving the password input by the user through an unlocking password dialog box in the screen locking interface, and starts running the application if the received password passes the verification; and if the verification fails, stopping starting the application and prompting the user. Therefore, the application in the second container system 103 can be prevented from being called under the condition of not obtaining the authorization of the user, and the safety of starting and running of the application in the second container system 103 is improved.
Preferably, in the embodiment of the present invention, after the second container system 103 starts the application, the application may be further controlled, a flowchart of the control method is shown in fig. 3b, and after the steps S301 to S304, the following steps are further included:
s305: after the application is finished, the second container system 103 packages the identification codes of the first and second container systems as the identification codes of the target system and the source system together with the application finishing information into a data packet and returns the data packet to the master control system 101.
Specifically, the second container system 103 generates application end information for the application after the application started to run in the above step S305 is ended and exited. Preferably, the second container system 103 carries the identification of the application in the application end information.
The second container system 103 packages the identification codes of the first container system 102 and the second container system 103 as identification codes of a target system and a source system together with the application end information into a data packet and returns the data packet to the master control system 101.
Preferably, the second container system 103 calls the container service module in the second container system 103 after the data packet in this step is encapsulated; the container service module sends the data packet to the ncm device node in the master control system 101 through the ncs device node of the second container system 103.
S306: the main control system 101 receives the data packet, switches the second container system 103 to the background and switches the first container system 102 to the foreground according to the identification codes of the source system and the target system and the application end information in the received data packet.
Specifically, the master control system 101 receives the data packet transmitted by the second container system 103.
Preferably, the master control system 101 receives the data packet sent by the second container system 103 through the ncm device node in the master control system 101 according to its master management module.
After analyzing the identification codes of the source system and the target system from the received data packet, the main control system 101 determines the identification of the second container system 103 corresponding to the identification code of the source system and the identification of the first container system 102 corresponding to the identification code of the target system according to the identification and the identification code of the container system which are stored correspondingly in advance.
Preferably, when the master control system determines that the identifier of the container system corresponding to the identifier of the source system in the data packet is the identifier of the second container system 103, it determines that the data packet sent by the second container system 103 is received.
The main control system 101 searches for the pre-recorded foreground and background information of the first container system 102 and the second container system 103 according to the application end information parsed from the received data packet.
After the main control system 101 determines that the first container system 102 and the second container system 103 are respectively located in the background and the foreground according to the search result, the second container system 103 is switched to the background, and the first container system 102 is switched to the foreground.
Those skilled in the art can understand that after the step S306 is completed, the first container system 102 in the smart terminal, which is located in the foreground, runs a desktop on which the system is displayed, and an icon of a shortcut application corresponding to an application in the second container system 103 is set in the desktop, so that a user can conveniently run an application in the second container system 103 by selecting the icon.
Preferably, the embodiment of the present invention further provides a method for the second container system 103 to deliver an update message of an application to the shortcut application of the first container system 102 before the second container system 103 receives a start command of the application, where a flowchart of the method is shown in fig. 4, and includes:
s401: the second container system 103 packages the identification code of the first container system 102 as the identification code of the target system, together with the number and identification of the newly added messages of the application, into a data packet, and sends the data packet to the master control system 101.
Specifically, after the second container system 103 detects that its application receives a new message, it counts the number of new messages for the application. For example, after the second container system 103 detects that a new short message is received from a secure short message therein, it counts that the number of the new short messages added to the secure short message is 10.
The second container system 103 determines the shortcut application corresponding to the application having the new addition information, and further determines the identifier of the container system to which the shortcut application belongs.
Preferably, for the application with the new added information, the second container system 103 determines the identifier of the shortcut application corresponding to the identifier of the application, and further determines that the identifier of the container system corresponding to the identifier of the shortcut application is the identifier of the first container system 102.
The second container system 103 packages the identification code of the first container system 102 as the identification code of the target system, together with the number of newly added messages and the identification of the application, into a data packet according to a predicted policy (e.g., a predetermined time interval), and sends the data packet to the master control system 101.
Preferably, the second container system 103 calls the container service module of the system after the data packet in this step is completely packaged; the container service module sends the data packet to the ncm device node in the master control system 101 through the ncs device node of the second container system 103.
S402: the main control system 101 receives the data packet, and sends the identifier of the application and the number of the newly added messages in the received data packet to the first container system 102 according to the identifier of the target system in the received data packet.
Specifically, the master control system 101 receives the data packet transmitted by the second container system 103.
Preferably, the master control system 101 receives the data packet sent by the second container system 103 through the ncm device node in the master control system 101 according to its master management module.
After the main control system 101 analyzes the identification code of the target system from the received data packet, the identification of the first container system 102 corresponding to the identification code of the target system is determined according to the identification and the identification code of the container system which are stored correspondingly in advance.
The master control system 101 sends the number and the identifier of the newly added messages of the application parsed from the received data packet to the first container system 102 according to the identifier of the second container system 103 as the target system.
Preferably, the main control system 101 calls its main management module; the master management module sends the number and the identifier of the newly added messages of the application in the received data packet to the ncs device node in the first container system 102 through the ncm device node in the master control system 101.
S403: the first container system 102 updates the numbers on the corner marks of the icons of the shortcut applications based on the received identification of the applications and the number of new messages.
Specifically, the first container system 102 receives the identification of the application and the number of newly added messages sent by the master control system 101.
Preferably, the first container system 102 receives, according to the container service module thereof, the identifier of the application and the number of the newly added messages sent by the master control system 101 through the ncs device node in the first container system 102.
The first container system 102 determines, according to the received identifier of the application, an identifier of a shortcut application corresponding to the identifier of the application in the system, and further determines an icon of the shortcut application.
The first container system 102 adds a corner mark for the icon of the shortcut application after receiving the number of the newly added messages of the application. For example, a corner mark is added in the upper right corner of the icon of the shortcut application. Also, the first container system 102 displays a number indicating the number of newly added messages on a corner mark of an icon of the shortcut application.
For example, the first container system 102 displays 10 on the icon of the shortcut application named safe short message, which indicates that the number of the new short messages is 10. Namely, 10 new unread messages are added to the secure messages in the second container system 103 to prompt the user.
In practical applications, the security system may be used as the second container system 103, and the non-security system may be used as the first container system 102.
The security system pays attention to the security of application operation, such as security short messages, security phones, security enterprise applications and the like which are operated in a confidential scene. However, the number of applications in the security system is small. For example, the Security system may specifically be a se (Security-Enhanced) linux-based operating system.
Non-secure systems are more concerned about the diversity and richness of applications than secure systems. Various applications can be installed in the insecure system to meet various needs of users. For example, the non-security system may specifically be an Android system.
The non-safety system and the safety system can be respectively operated in a foreground and a background, and a user can use various applications in the non-safety system in the foreground to experience respective functions of the applications. An icon of the shortcut application corresponding to the application of the security system is arranged on the desktop of the non-security system, so that a user can conveniently switch the security system to the foreground by selecting the icon and start the application of the icon in the security system.
Based on the above cross-system application control method, the main uses of the main control system 101, the first container system 102, and the second container system 103 in the embodiment of the present invention are described below.
The first container system 102 is used to run a display desktop; icons of shortcut applications corresponding to the applications in the second container system are arranged in the desktop; after receiving a click event of the icon of the shortcut application, operating the shortcut application; and the shortcut application respectively takes the identification codes of the first container system and the second container system as the identification codes of the source system and the target system, encapsulates the identification codes and the starting command of the application into a data packet, and sends the data packet.
The main control system 101 is configured to receive a data packet, switch the first container system from a foreground to a background according to the identification codes of the source system and the target system in the received data packet and the start command of the application, and send the start command after switching the second container system to the foreground.
The second container system 103 is used to launch the application according to the received launch command.
Preferably, the second container system 103 is further configured to package the identification code of the first container system 102 as the identification code of the target system together with the installation request of the shortcut application into a data packet for transmission according to user setting information or a predetermined policy when the application is installed into the second container system 103.
The main control system 101 is further configured to receive a data packet, and send an installation request of the shortcut application in the received data packet according to the identification code of the target system in the received data packet.
The first container system 102 is further configured to install an icon of the shortcut application in a desktop of the first container system 102 according to the received installation request of the shortcut application.
Preferably, the second container system 103 is further configured to encapsulate the identification code of the first container system 102 as the identification code of the target system, together with the number of new messages and the identification of the application, into a data packet for transmission before receiving the start command.
The main control system 101 is further configured to receive a data packet, and send an identifier of an application and the number of new messages in the received data packet according to an identifier of a target system in the received data packet.
The first container system 102 is further configured to update the numbers on the corner marks of the icons of the shortcut applications based on the received identification of the applications and the number of new messages.
Preferably, the second container system 103 is further configured to, after the application is started, if the application is ended, encapsulate the identifiers of the first and second container systems into a data packet together with the application end information as identifiers of the target system and the source system, respectively.
The main control system 101 is further configured to receive a data packet, switch the second container system 103 to the background and switch the first container system 102 to the foreground according to the identification codes of the source system and the target system and the application end information in the received data packet.
Preferably, as shown in fig. 5, the main control system 101 according to the embodiment of the present invention includes: multi-system control module 511, master management module 512 and ncm device node 513; the first container system 102 includes: an application control module 521, a container service module 522, and an ncs device node 523; the second container system 103 includes: an application control module 531, a container service module 532, and an ncs device node 533.
In the second container system 103, when the application control module 531 receives an installation request for installing an application into the system, the application control module obtains user setting information or a predetermined policy prestored in the intelligent terminal, and determines whether the user setting information or the predetermined policy relates to the application. And when the determination result is that the application is involved in time, the second container system 103 installs the application into the system according to the installation package of the application, and searches out the identifier of the shortcut application corresponding to the application from the identifier of the application and the identifier of the shortcut application which are pre-stored in the intelligent terminal correspondingly.
The application control module 531 generates an installation request of the shortcut application according to the identifier of the application or the identifier of the shortcut application corresponding to the application. Preferably, the application control module 531 carries the identification of the application, or the identification of the shortcut application, in the installation request of the shortcut application.
The application control module 531 finds the identification code of the first container system 102 based on the user setting information or the identification of the first container system 102 related to the predetermined policy.
The application control module 531 takes the identification code of the first container system 102 as the identification code of the target system, packages the identification code and the installation request of the shortcut application into a data packet, and calls the container service module 532 in the second container system 103; the ncs device node 533 through which the data packet passes is sent by the container service module 532 to ncm device node 513 of the host system 101. Specifically, the ncs device node 533 and the ncm device node 513 may be a/dev/ncs file or a/dev/ncm file.
The master management module 512 in the master control system 101 is configured to monitor ncm the device node, and forward the data packet received by the device node ncm from the container service module 532 in the second container system 103. After the multi-system control module 511 in the main control system 101 analyzes the identification code of the first container system 102 serving as the identification code of the target system and the installation request of the shortcut application from the data packet forwarded by the main management module 512, the main management module 512 is called; the installation request of the parsed shortcut application is transmitted to the ncs device node 522 in the first container system 102 through the ncm device node 513 according to the parsed identification code of the first container system 102 by the main management module 512. The ncs device node 522 may be specifically an/dev/ncs file.
The first container system 102 stores in advance installation packages of a plurality of shortcut applications. The installation package of the shortcut application comprises the following components: an icon of the shortcut application. For the shortcut application corresponding to the application in the second container system 103, the icon of the shortcut application specifically includes: a LOGO of the second container system 103, and a word representing the name of the application.
The application control module 521 in the first container system 102 is configured to, for each shortcut application, correspondingly store an identifier of the shortcut application, an identifier of an application corresponding to the shortcut application, and an installation package of the shortcut application.
The application control module 521 is configured to invoke the container service module 522 in the first container system 102 to listen to the ncs device node 523 in the first container system 102. After receiving an installation request of the shortcut application sent to the ncs device node 523 by the main management module 512 in the main control system 101 through the container service module 522, the application control module 521 analyzes an identifier of the shortcut application from the installation request, or determines the identifier of the shortcut application according to information analyzed from the installation request; further determining an installation package corresponding to the identifier of the shortcut application; and installing the shortcut application corresponding to the application in the second container system 103 into the first container system 102 according to the determined installation package, and setting the icon of the shortcut application on the desktop of the first container system 102.
Based on the above cross-system application control method, the application control module 521 in the first container system 102 is used to run a display desktop; icons of shortcut applications corresponding to the applications in the second container system 103 are arranged in the desktop; after receiving a click event of the icon of the shortcut application, operating the shortcut application; the identification codes of the first container system 102 and the second container system 103 are respectively used as the identification codes of the source system and the target system by the shortcut application and are packaged into a data packet together with the starting command of the application.
The application control module 521 calls the container service module 522 in the first container system 102, and the container service module 522 sends the data packet encapsulated by the shortcut application through the ncs device node 523 in the first container system 102. Preferably, the shortcut application may send a container service call request after the package of the data packet is completed, and the application control module 521 may call the container service module 522 after receiving the container service call request of the shortcut application.
The master management module 512 in the master control system 101 is configured to receive and forward the data packet sent by the container service module 522 in the first container system 102 through the ncm device node 513 in the master control system 101.
The multi-system management module 511 is configured to, after analyzing the identification codes of the source system and the target system from the data packet forwarded by the main management module 512, determine, according to the identifier and the identification code of the container system stored in advance, an identifier of the first container system 102 corresponding to the identification code of the source system and an identifier of the second container system 103 corresponding to the identification code of the target system. And searching pre-recorded foreground and background information of the first container system 102 and the second container system 103 according to the application starting command analyzed from the received data packet.
After the multi-system management module 511 determines that the first container system 102 and the second container system 103 are respectively located in the foreground and the background, the main management module 512 in the main control system 101 is called according to the identifier of the second container system 103 serving as a target system; the start command of the application in the data packet is sent by main management module 512 to ncs device node 533 in second container system 103 through ncm device node 513 in main control system 101.
The application control module 532 in the second container system 103 is configured to receive, according to the container service module 532 in the second container system 103, a start command of the application sent by the main management module 512 in the main control system 101 through the ncs device node 533 in the second container system 103; and analyzing the application identifier from the received application starting command, and starting to run the application according to the analyzed identifier.
For the method for implementing the functions of the multi-system control module 511, the main management module 512, and the device node ncm in the main control system 101, the application control module 521, the container service module 522, and the ncs device node 523 in the first container system 102, and the application control module 531, the container service module 532, and the ncs device node 533 in the second container system 103, reference may be made to the specific contents of the flow steps in fig. 2, fig. 3a, fig. 3b, and fig. 4, which are not described herein again.
In the embodiment of the invention, the desktop of the first container system is provided with the icon of the shortcut application corresponding to the application in the second container system, and after the click event of the icon is received, the shortcut application sends the identification codes of the first and second container systems and the starting command of the application to the master control system; the main control system respectively switches the first container system and the second container system to a background and a foreground and sends a starting command; the second container system launches the application in accordance with the received launch command. The method and the device have the advantages that a user does not need to spend a large amount of time to memorize the container system to which the application belongs, the user does not need to actively execute the operation of switching the container system, the application in the second container system can be controlled in the first container system, and the cross-system application control is realized. The memory burden or the operation burden of the user is greatly reduced, convenience is brought to the user, and the user experience is improved.
Also, in an embodiment of the present invention, the icon of the shortcut application in the first container system includes a logo of the second container system and a text indicating a name of an application corresponding to the shortcut application. For example, icons for shortcut applications include: LOGO of syberos as a second container system, and "secure note" indicating a name of an application in syberos. The user can easily recognize that the icon of the shortcut application corresponds to the application in the second container system, that is, the icon obviously prompts the name of the application and the information of the container system to which the application belongs, so that the user can start or call the corresponding application according to the icon, and the user experience is improved.
Further, in the embodiment of the present invention, when the application is installed in the second container system, the installation request of the shortcut application corresponding to the application is sent to the first container system through the master control system; the first container system installs an icon of the shortcut application in its desktop. The phenomenon that only one of the application and the shortcut application is installed is prevented, and the corresponding installation between the shortcut application in the first container system and the application in the second container system is realized, so that the cross-system application control method of the embodiment of the invention is realized.
In addition, in the embodiment of the present invention, when an application newly added message (for example, a new short message is received) is located in the second container system in the background, the second container system sends the number and the identifier of the newly added message of the application to the first container system located in the foreground through the main control system; and the first container system updates the numbers on the corner marks of the icons of the shortcut applications according to the received identifications of the applications and the number of the newly added messages. For example, the number 10 is displayed on the corner mark of the icon of the shortcut application named secure sms, which indicates that there are 10 unread sms in the secure sms in the second container system. Therefore, the user is reminded to inquire the newly added message of the application in the second container system at the background in time, compared with the prior art, the step that the frequency of the user is switched to the second container system to check whether the application has the newly added message is saved, the operation of the user is greatly saved, convenience is brought to the user, and the experience of the user is improved.
Those skilled in the art will appreciate that the present invention includes apparatus directed to performing one or more of the operations described in the present application. These devices may be specially designed and manufactured for the required purposes, or they may comprise known devices in general-purpose computers. These devices have stored therein computer programs that are selectively activated or reconfigured. Such a computer program may be stored in a device (e.g., computer) readable medium, including, but not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magnetic-optical disks, ROMs (Read-Only memories), RAMs (Random Access memories), EPROMs (Erasable programmable Read-Only memories), EEPROMs (Electrically Erasable programmable Read-Only memories), flash memories, magnetic cards, or optical cards, or any type of media suitable for storing electronic instructions, and each coupled to a bus. That is, a readable medium includes any medium that stores or transmits information in a form readable by a device (e.g., a computer).
It will be understood by those within the art that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. Those skilled in the art will appreciate that the computer program instructions may be implemented by a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the features specified in the block or blocks of the block diagrams and/or flowchart illustrations of the present disclosure.
Those of skill in the art will appreciate that various operations, methods, steps in the processes, acts, or solutions discussed in the present application may be alternated, modified, combined, or deleted. Further, various operations, methods, steps in the flows, which have been discussed in the present application, may be interchanged, modified, rearranged, decomposed, combined, or eliminated. Further, steps, measures, schemes in the various operations, methods, procedures disclosed in the prior art and the present invention can also be alternated, changed, rearranged, decomposed, combined, or deleted.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.