CN115586928A - Method for displaying application and related equipment - Google Patents

Abstract

The disclosure provides a method for displaying an application and related equipment. The method comprises the following steps: receiving a starting request of a first application; starting a service component corresponding to the first application based on the starting request of the first application; creating a dialog window corresponding to the first application based on the service component corresponding to the first application; and creating elements in the page corresponding to the first application in the conversation window, and further displaying the page corresponding to the first application.

Description

Method for displaying application and related equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method for displaying an application and a related device.

Background

With the popularization of 5G and the falling of AI technology, various intelligent devices are applied to various scenes, and more entertainment functions are considered by televisions instead of the traditional media playing function. Especially, very large Android (Android) devices have integrated more and more functions of entertainment, social interaction, sports, and the like. How to utilize the advantage that the super-large equipment can show a large area and how to construct an interactive interface becomes a problem to be developed urgently for the super-large equipment.

Disclosure of Invention

The disclosure provides a method for displaying an application and related equipment.

In a first aspect of the present disclosure, a method for displaying an application is provided, including: receiving a starting request of a first application; starting a service component corresponding to the first application based on the starting request of the first application; creating a dialog window corresponding to the first application based on the service component corresponding to the first application; and creating elements in the page corresponding to the first application in the dialog window, and further displaying the page corresponding to the first application.

In a second aspect of the disclosure, a computer device is provided, comprising one or more processors, a memory; and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, the programs comprising instructions for performing the method for deploying distributed tasks according to the first aspect.

In a third aspect of the disclosure, a non-transitory computer-readable storage medium containing a computer program is provided, which, when executed by one or more processors, causes the processors to perform the method of the first aspect.

In a fourth aspect of the present disclosure, a computer program product is provided, comprising a computer-readable storage medium having stored thereon instructions that, when executed, cause at least one central processor unit of a computing device to perform the method according to the first aspect.

According to the method for displaying the application and the related device, the corresponding application is started by utilizing the service component, so that the application can run on the background of the device on the basis of the service component and cannot be interrupted by other started applications. In some embodiments, when the launched application is a video-type application, the video file being played is not interrupted by other launched applications, and the user can continue to watch the video file being played.

Drawings

In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings needed to be used in the description of the embodiments or related technologies are briefly introduced below, and it is obvious that the drawings in the following description are only embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 shows a hardware structure diagram of an exemplary computer device provided by an embodiment of the present disclosure.

Fig. 2 shows a flow diagram of an exemplary method provided by an embodiment of the present disclosure.

Fig. 3A illustrates a schematic diagram of an exemplary interface according to an embodiment of the present disclosure.

Fig. 3B illustrates a schematic diagram of another exemplary interface according to an embodiment of the present disclosure.

Fig. 3C shows a schematic diagram of yet another exemplary interface according to an embodiment of the present disclosure.

Fig. 3D shows a schematic diagram of yet another exemplary interface according to an embodiment of the present disclosure.

Fig. 3E illustrates a schematic diagram of another exemplary interface according to an embodiment of the present disclosure.

Fig. 3F illustrates a flow diagram of another exemplary method according to an embodiment of the present disclosure.

Fig. 3G illustrates a schematic diagram of yet another exemplary interface, in accordance with an embodiment of the present disclosure.

Detailed Description

For the purpose of promoting a better understanding of the objects, aspects and advantages of the present disclosure, reference is made to the following detailed description taken in conjunction with the accompanying drawings.

It is to be noted that technical terms or scientific terms used in the embodiments of the present disclosure should have a general meaning as understood by those having ordinary skill in the art to which the present disclosure belongs, unless otherwise defined. The use of "first," "second," and similar terms in the embodiments of the disclosure is not intended to indicate any order, quantity, or importance, but rather to distinguish one element from another. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items. The terms "connected" or "coupled" and the like are not restricted to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", and the like are used merely to indicate relative positional relationships, and when the absolute position of the object being described is changed, the relative positional relationships may also be changed accordingly.

Activity is one of the four most basic and most common components (Activity, service, content Provider, broadcastReceiver) in Android components. Activity is an application component that can provide a page with which a user can interact to complete a task.

In an Android application program, activity is generally the basis of all programs, each User Interface (UI) is composed of Activity, and all UI sub-controls are also attached to the Activity, wherein the Activity comprises data display and interaction between pages. In addition, the flow of all programs is attached to Activity.

Activity represents one page display of an application program, when jumping to another page of the application program, the Activity life cycle is triggered, and the current Activity is put into a stack for processing. The Activity life cycle comprises states of starting, pausing, destroying and the like, so that the Activity plays an important ring in the construction of the application program.

However, in the development of large-screen android devices, media functions occupy an important ring, and especially, the requirements and the experience of large-size devices on the media functions are different from those of conventional mobile terminal devices of mobile phones. Large-screen android devices tend to require more information feedback to be acquired in the same screen and require no interruption to the media resource being played. However, the construction method of an Application (APP) adopting Activity cannot meet such a requirement.

For example, when one video APP plays a media resource, if another APP runs at the same time, the current media playing APP process is put into the background, which causes the media playing APP to pause, and other APPs are inserted for corresponding interaction when the media APP cannot be played at the same time.

In view of this, the present disclosure provides a method for displaying an application and a related device. The method comprises the following steps: receiving a starting request of a first application; starting a service component corresponding to the first application based on the starting request of the first application; creating a dialog window corresponding to the first application based on the service component corresponding to the first application; and creating elements in the page corresponding to the first application in the conversation window, and further displaying the page corresponding to the first application.

According to the method for displaying the application and the related device, the corresponding application is started by utilizing the service component, so that the application can run in the background of the device on the basis of the service component and cannot be interrupted by other started applications. In some embodiments, when the launched application is a video-class application, the video file being played is not interrupted by other launched applications, and the user can continue to watch the video file being played.

A first aspect of embodiments of the present disclosure provides a computer device.

Fig. 1 shows a hardware structure diagram of an exemplary computer device 100 provided by the embodiment of the present disclosure. The apparatus 100 may comprise: a processor 102, a memory 104, an input/output interface 106, a communication interface 108, and a bus 110. Wherein the processor 102, memory 104, input/output interface 106, and communication interface 108 are communicatively coupled to each other within the device via bus 110.

The processor 102 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present specification.

The Memory 104 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 104 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 104 and called to be executed by the processor 102.

The input/output interface 106 is used for connecting an input/output module to realize information input and output. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.

The communication interface 108 is used for connecting a communication module (not shown in the figure) to realize communication interaction between the device and other devices. The communication module can realize communication in a wired mode (for example, USB, network cable, etc.), and can also realize communication in a wireless mode (for example, mobile network, WIFI, bluetooth, etc.).

Bus 110 includes a path that transfers information between the various components of the device, such as processor 102, memory 104, input/output interface 106, and communication interface 108.

It should be noted that although the above-described device only shows the processor 102, the memory 104, the input/output interface 106, the communication interface 108, and the bus 110, in a specific implementation, the device 100 may also include other components necessary for normal operation. Furthermore, those skilled in the art will appreciate that the apparatus 100 described above may also include only the components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.

In a second aspect of the embodiments of the present disclosure, a method for displaying an application is provided, which can solve a video interruption problem existing when an Activity manner is used to implement an application.

Fig. 2 illustrates a flow diagram of an exemplary method 200 provided by an embodiment of the present disclosure. The method 200 may be implemented by the device 100 shown in fig. 1. In some embodiments, the operating system running in device 100 may be an android system. As shown in fig. 2, the method 200 may include the following steps.

In step 202, the device 100 may receive a start request of a first application.

Fig. 3A shows a schematic diagram of one exemplary interface 300 of the device 100, according to an embodiment of the present disclosure.

As shown in fig. 3A, an application 3002 and an application 3004 are included in the interface 300. The launch request of the first application may be issued, for example, by clicking an icon of the application 3002 in the interface 300.

In step 204, the device 100 may launch a service component corresponding to the first application (e.g., the application 3002 of fig. 3A) based on the launch request of the first application.

In some embodiments, when device 100 is operating in the android system, the service component may be a service component under the android system. By running the service component, the first application can always run in the background of the device after being started without being interrupted by other applications.

In some embodiments, the step of initiating the service component may further comprise the steps of: initiating and creating a first process based on the starting request of the first application; binding the first process with the first application; binding the first application with the corresponding service component; and starting the first application and starting a service component corresponding to the first application.

In some embodiments, the step of initiating the service component may further comprise the following steps.

First, a process is initiated based on a start request. For example, when an application is launched from a desktop, the initiated process may be the native process of an android system desktop Launcher (Launcher), and when a remote process is launched from within an application, the initiated process may be the native process of the application. The initiating process may first send a message to the system _ server process of the android system through the binder communication mechanism of the android system, and then the system _ server process may call the process _ start () method, sending a request to create a new process to the zygate process of the android system through a socket (socket). Then, the zygate process may enter the runselectlooloop () loop after executing the zygate information.main (), wait for the ActivityManagerService to request zygate to create a new application process through infinite polling, and when there is a request to create a new process, the zygate process may execute the zygate connection.runonce () method, and branch (fork) out the new application process (i.e., the aforementioned first process) after calling layer by layer.

After the new application process is created, the new application process may execute the handleChildProc method, then call and execute the activitythread.

After the first application is successfully bound, the first application binds the corresponding service component (service) when being started, and starts the corresponding service component in the first application by using a method of startService (new Intent ()). The service components may then run in the background after startup and may complete some time consuming operations, including some listening actions.

In step 206, device 100 may create a dialog window corresponding to the first application based on the service component corresponding to the first application.

In some embodiments, when creating the corresponding service component for the first application, a system dialog class (systemdiog) required by the first application may be created, and when creating the system dialog class, a required basic window may be created by modifying a window (window) attribute. The window attributes may include a size parameter and a position parameter of the dialog window. For example, the size of the dialog window, where it is on the screen (which may be expressed in coordinates relative to the screen). In this way, when the device 100 creates a dialog window, the device can create a corresponding dialog window according to the corresponding window attribute, and the size, the position, and the like of the obtained dialog window correspond to the size parameter and the position parameter in the window attribute.

Accordingly, in some embodiments, the device 100 may start a system dialog class of the service component corresponding to the first application based on the service component corresponding to the first application, and further create a dialog window corresponding to the first application.

In step 208, the device 100 may create an element in the page corresponding to the first application in the dialog window, and then display the page corresponding to the first application.

In some embodiments, the element may be a view component under the android system. Further, in some embodiments, the view component of each page of the application may be created by inheriting the systemdialog class so that the service component may be responsible for launching each page, including switching between pages, displaying and hiding the view component in the page.

In step 208, if the page to be exposed at this time is the page immediately after the application is started, the elements (view components) to be created are the elements in the page.

Fig. 3B and 3D show schematic diagrams of two exemplary interfaces 302 and 300, respectively, according to embodiments of the present disclosure.

As shown in fig. 3B, the dialog window corresponding to the first application occupies the entire screen, and as shown in fig. 3D, the dialog window 3006 corresponding to the first application is located only in a certain corner of the screen, which is related to the window attribute of the first application. When the window attributes in the system dialog classes corresponding to the service components are different, different dialog windows may be formed for the application.

In some embodiments, by utilizing the create and destroy properties of view components, the implementation of lifecycle properties (creation and destruction) in place of Activity can be modeled using the functions onAttachedToWindow () and onDetacedFromWindow ().

In some embodiments, the device 200 may also employ the method 300 to implement a jump of a page. Fig. 3F shows a flow diagram of an exemplary method 300 in accordance with an embodiment of the present disclosure.

In step 302, the device 100 may receive a page switch request of the first application.

As shown in fig. 3B, elements 3022 and 3024 are also included in the current page 302, and the page switch request may be issued by clicking on element 3022 (equivalent to a function icon).

In step 304, the device 100 may determine elements of the switched page based on the page switch request. Fig. 3G shows a schematic diagram of an exemplary interface 304, in accordance with an embodiment of the present disclosure. For example, as shown in fig. 3G, only element 3022 is included in the elements of the post-switch page 304.

In step 306, the device 100 may determine that the elements of the switched page are the same as the elements of the current page based on the elements of the switched page and the elements of the current page. As can be appreciated from fig. 3G, the same element is element 3022.

In step 308, the device 100 may retain the same element 3022 in the post-switch page 304.

In step 310, device 100 may create other elements in the post-switch page than the same element, e.g., element 3042 in fig. 3G.

In some embodiments, the method 300 may further include the steps of:

in step 312, device 100 may determine, based on the elements of the post-switch page and the elements of the current page, different elements of the current page and the post-switch page, e.g., element 3024 in fig. 3G.

In step 314, the apparatus 100 may determine whether the different element belongs to an element whose usage frequency is lower than a preset usage frequency.

In step 316, if the different element belongs to an element whose usage frequency is lower than the preset usage frequency, the device 100 may destroy the element in the current page that is different from the switched page.

In step 318, if the different element does not belong to an element with a usage frequency lower than the preset usage frequency, the device 100 may hide the different element in the post-switching page 304 (as shown in fig. 3G, the dashed element 3024 indicates that it is hidden).

Thus, the jump of the application page is realized.

In some embodiments, the method 300 described above may be implemented using a stack. Common view components as well as non-common view components can be implemented in the stack. And for the commonly used view component, the commonly used view component is stored at the bottom of the stack after the instance is created, and is directly displayed when needed, and is hidden by utilizing the hidden property of the view component when not needed. For an unusually used view component, it can be recreated each time it is used and can be timely destroyed when it is not needed.

Therefore, the problems that some pages need to store data and some pages need to be refreshed are solved, and the whole APP page skipping process is well simulated.

In some embodiments, the method 200 may further include the following steps.

In step 210, the device 100 may receive a start request of a second application.

As shown in fig. 3B, the launch request of the second application may be issued by clicking on a pop-up message 3026 in the interface 302. As shown in fig. 3D, the launch request of the second application may also be issued by clicking an icon 3004 on the desktop. It will be appreciated that both approaches are exemplary only and do not preclude there being other possible approaches.

In step 212, the device 100 may start a service component corresponding to the second application based on the start request of the second application. The service component is similar to the creation process and function of the service component, and is not described herein again.

In step 214, the device 100 may create a dialog window corresponding to the second application based on the service component corresponding to the second application.

Fig. 3C and 3E show schematic diagrams of exemplary interfaces 302 and 300, respectively, according to an embodiment of the present disclosure.

As shown in fig. 3C, the dialog window 3028 of the second application floats above the interface 302 and does not interrupt the operation of the first application. As shown in fig. 3E, the dialog window 3008 of the second application is arranged in parallel with the dialog window 3006 of the first application without interfering with each other.

In some embodiments, the device 100 may start a system dialog class of the service component corresponding to the second application based on the service component corresponding to the second application, and further create a dialog window corresponding to the second application.

In step 216, the device 100 may create an element in the page corresponding to the second application in the dialog window, and then display the page corresponding to the second application. This element is similar to the creation process and function of the aforementioned elements and will not be described in detail herein.

Due to the fact that the attributes of system dialogs (system dialogs) corresponding to the service components exist at the same time, the service components corresponding to the applications can run at the same time, the problem that other application programs are suspended due to page grabbing after construction does not exist without using Activity, and the problem that large-size equipment wants to use more than two apps at the same time but affects each other is also avoided. And moreover, because each service component corresponding to each application runs on the background at the same time, the service components can be quickly switched to the display interface, and the switching fluency of each application is ensured.

The method for displaying the applications optimizes the process of seamless switching between the APPs, optimizes the experience of a large-screen-end media playing user, solves the problem that some common construction modes cannot solve, and improves the user experience and performance advantages.

According to the method for displaying the application, the UI of the APP is not attached to the Activity, the APP abandons the Activity, and the method comprises an Activity starting mode, UI bearing, page jump interaction and life cycle processing operation.

In the method for displaying an application provided by the embodiment of the present disclosure, a UI of the application is borne on a system popup. At start-up, the APP starts a service component (service) in the background. A service component is an application component that can perform long running operations in the background without a user interface, the service component can be started by other components, and the service component can run in the background all the time once it is started. The service component can process background affairs, can do network operation, play music, media play and the like. The embodiment of the disclosure starts the service component by adopting a startService () mode, once the service component is started, the service component is operated in the background, and the service component is not closed unless the service component is manually operated and closed.

The service component will then initiate systemdalog. SystemDialog is different from conventional Dialog, the default conventional Dialog is usually generated by means of Activity construction, and must depend on Context of Activity, and the service component can realize the start of the Dialog by setting the Dialog as a system, so that after the Dialog becomes a global property, the corresponding Dialog window can be arbitrarily displayed as long as the SystemDialog is started. By utilizing the characteristic, each Activity page can be written into a system level dialog page, all View components inherit the system dialog, and the global UI bearing can be realized without using Activity.

It should be noted that the method of the embodiments of the present disclosure may be executed by a single device, such as a computer or a server. The method of the embodiment can also be applied to a distributed scene and completed by the mutual cooperation of a plurality of devices. In such a distributed scenario, one of the devices may only perform one or more steps of the method of the embodiments of the present disclosure, and the devices may interact with each other to complete the method.

It should be noted that the above describes some embodiments of the disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments described above and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Based on the same inventive concept, corresponding to any of the above-described embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method 200 or 300 according to any of the above embodiments.

Computer-readable media of the present embodiments, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

The computer instructions stored in the storage medium of the foregoing embodiment are used to enable the computer to execute the method 200 or 300 according to any embodiment, and have the beneficial effects of the corresponding method embodiment, which are not described in detail herein.

Based on the same inventive concept, corresponding to any of the embodiment methods 200 or 300 described above, the present disclosure also provides a computer program product comprising a non-transitory tangible computer readable medium having computer readable instructions thereon. In some embodiments, the computer readable instructions are executable by one or more processors to cause the processors to perform the methods 200 or 300. The processor for executing the corresponding steps may belong to the corresponding execution subject corresponding to the steps in the embodiments of the method 200 or 300, and each execution subject may be implemented by using one or more computer devices 100, and when implemented by using a plurality of computer devices 100, the form may be distributed.

The computer program product of the foregoing embodiment is used for enabling a processor to execute the method 300 according to any of the foregoing embodiments, and has the advantages of corresponding method embodiments, which are not described herein again.

Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the idea of the present disclosure, also technical features in the above embodiments or in different embodiments may be combined, steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of brevity.

In addition, well-known power/ground connections to Integrated Circuit (IC) chips and other components may or may not be shown in the provided figures for simplicity of illustration and discussion, and so as not to obscure the embodiments of the disclosure. Furthermore, devices may be shown in block diagram form in order to avoid obscuring embodiments of the present disclosure, and this also takes into account the fact that specifics with respect to implementation of such block diagram devices are highly dependent upon the platform within which the embodiments of the present disclosure are to be implemented (i.e., specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the disclosure, it should be apparent to one skilled in the art that the embodiments of the disclosure can be practiced without, or with variation of, these specific details. Accordingly, the description is to be regarded as illustrative instead of restrictive.

While the present disclosure has been described in conjunction with specific embodiments thereof, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art in light of the foregoing description. For example, other memory architectures, such as Dynamic RAM (DRAM), may use the discussed embodiments.

The disclosed embodiments are intended to embrace all such alternatives, modifications and variances which fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalents, improvements, and the like that may be made within the spirit and principles of the embodiments of the disclosure are intended to be included within the scope of the disclosure.

Claims (12)

1. A method of presenting an application, comprising:

receiving a starting request of a first application;

starting a service component corresponding to the first application based on the starting request of the first application;

creating a dialog window corresponding to the first application based on the service component corresponding to the first application; and

and creating elements in the page corresponding to the first application in the dialog window, and further displaying the page corresponding to the first application.

2. The method of claim 1, further comprising:

receiving a page switching request of the first application;

determining elements of the page after switching based on the page switching request;

determining the same elements of the switched page and the current page based on the elements of the switched page and the elements of the current page;

keeping the same element in the switched page; and

creating other elements in the switched page than the same element.

3. The method of claim 2, further comprising:

determining different elements of the current page and the switched page based on the elements of the switched page and the elements of the current page;

determining whether the different elements belong to elements with the use frequency lower than a preset use frequency;

in response to the fact that the different elements belong to the elements with the use frequency lower than the preset use frequency, destroying the elements, different from the switched page, in the current page;

hiding the different elements in the switched page in response to the different elements not belonging to elements with a use frequency lower than a preset use frequency.

4. The method of claim 1, further comprising:

receiving a starting request of a second application;

starting a service component corresponding to the second application based on the starting request of the second application;

creating a dialog window corresponding to the second application based on the service component corresponding to the second application; and

and creating elements in the page corresponding to the second application in the dialog window, and further displaying the page corresponding to the second application.

5. The method of claim 4, applied to a device running an android system, wherein the service component is a service component, and the element is a view component.

6. The method of claim 5, wherein creating the dialog window for the first application based on the service component for the first application comprises: based on the service component corresponding to the first application, starting a system conversation class of the service component corresponding to the first application, and further creating a conversation window corresponding to the first application; or

Creating a dialog window corresponding to the second application based on the service component corresponding to the second application, including: and starting a system conversation class of the service component corresponding to the second application based on the service component corresponding to the second application, and further creating a conversation window corresponding to the second application.

7. The method of claim 6, wherein the system dialog class includes window attributes including a size parameter and a position parameter of the dialog window;

creating a dialog window corresponding to the first application, including: creating a dialog window corresponding to the first application according to the window attribute corresponding to the first application; or alternatively

Creating a dialog window corresponding to the second application, including: and creating a dialog window corresponding to the second application according to the window attribute corresponding to the second application.

8. The method of claim 6, wherein the view component is created by inheriting the system dialog class.

9. The method of claim 1, wherein launching the service component corresponding to the first application based on the launch request of the first application comprises:

initiating and creating a first process based on the starting request of the first application;

binding the first process with the first application;

binding the first application with the corresponding service component; and

and starting the first application and starting a service component corresponding to the first application.

10. A computer device comprising one or more processors, memory; and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, the programs comprising instructions for performing the method of any of claims 1-9.

11. A non-transitory computer-readable storage medium containing a computer program which, when executed by one or more processors, causes the processors to perform the method of any one of claims 1-9.

12. A computer program product comprising a computer-readable storage medium having stored thereon instructions that, when executed, cause at least one central processor unit of a computing device to perform the method of any of claims 1-9.

Images