System switching method and device, electronic equipment, medium and computer program product

Abstract

The embodiment of the invention discloses a system switching method and device, electronic equipment, a medium and a computer program product, and relates to the field of electronic equipment. The method comprises the steps that a second system monitors an event triggered by an application, and the application is operated by the second system; when the event triggered by the application is monitored, the event meets the system switching condition, and the first system has the screen control authority, the second system obtains the screen control authority from the first system; and under the condition that the screen control authority is obtained, the second system controls the screen to display an application interface of the application. According to the embodiment of the invention, under the condition that the event triggered by the application exists in the second system and the event meets the system switching condition, the first system is automatically switched to the second system, and automatic switching between the dual systems is realized.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of electronic devices, and in particular, to a system switching method, device, electronic device, medium, and computer program product. Background Art

[0002] With the continuous upgrading of electronic devices, users' demand for the use of electronic devices has also increased. In order to improve the battery life of mobile electronic devices, dual-system devices have gradually emerged.

[0003] In the related art, when the screen permission is controlled by the first system, if an application running by the second system requests a system switch, the application needs to send a system switch request through a specific interface, thereby implementing a system switch based on the system switch request.

[0004] It can be seen that in the related technology, the application needs to adapt to a specific interface first, and then send a system switching request to achieve system switching, which makes the system switching process complicated. Summary of the invention

[0005] The embodiments of the present application provide a system switching method, device, electronic device, medium and computer program product. The technical solution is as follows:

[0006] On the one hand, an embodiment of the present application provides a system switching method, the method is used in an electronic device, the electronic device supports running a first system and a second system;

[0007] The method comprises:

[0008] The second system monitors an event triggered by an application, and the application is run by the second system;

[0009] When an event triggered by the application is monitored, and the event meets a system switching condition, and the first system has screen control authority, the second system obtains the screen control authority from the first system;

[0010] When the screen control permission is obtained, the second system controls the screen to display the application interface of the application.

[0011] On the other hand, an embodiment of the present application provides a system switching device, the device is used in an electronic device, the electronic device supports running a first system and a second system;

[0012] The device comprises:

[0013] a second system module, configured to monitor an event triggered by an application, wherein the application is run by the second system module;

[0014] The second system module is further configured to obtain the screen control permission from the first system module when an event triggered by the application is monitored and the event meets a system switching condition and the first system module has the screen control permission;

[0015] The second system module is further configured to control the screen to display the application interface of the application when the screen control authority is obtained.

[0016] On the other hand, an embodiment of the present application provides an electronic device, which includes a processor and a memory; the memory stores at least one computer instruction, and the at least one computer instruction is used to be executed by the processor to implement the system switching method as described in the above aspect.

[0017] On the other hand, an embodiment of the present application provides a computer-readable storage medium, in which at least one computer instruction is stored. The computer instruction is loaded and executed by a processor to implement the system switching method as described in the above aspects.

[0018] On the other hand, an embodiment of the present application provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device performs the system switching method described in the above aspects.

[0019] In an embodiment of the present application, the second system monitors events triggered by applications running in the system in real time, and when an event triggered by an application is monitored and the event meets a system switching condition, if the current first system has screen control authority, the second system obtains screen control authority from the first system, and when the screen control authority is obtained, controls the application interface of the application displayed on the screen, thereby enabling the second system to actively execute system switching based on the monitored events without waiting for the application to send a system switching request before executing the system switching, thereby improving the system switching efficiency between the dual systems. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0021] Figure 1 It is a dual-core communication software framework diagram of an Android operating system provided by an exemplary embodiment of the present application;

[0022] Figure 2 It is a dual-core communication software framework diagram of RTOS provided by an exemplary embodiment of the present application;

[0023] Figure 3 is a flow chart of a system switching method provided by an exemplary embodiment of the present application;

[0024] Figure 4 is a schematic diagram of an interface for system switching provided by an exemplary embodiment of the present application;

[0025] Figure 5 is a flow chart of a system switching method provided by another exemplary embodiment of the present application;

[0026] Figure 6 is a flowchart of determining whether to perform system switching by monitoring a screen-on event provided by an exemplary embodiment of the present application;

[0027] Figure 7 is a flowchart of determining whether to perform system switching by monitoring application self-starting events provided by an exemplary embodiment of the present application;

[0028] Figure 8 is a flow chart of a system switching method provided by another exemplary embodiment of the present application;

[0029] Fig. 9 is a flowchart of determining whether to perform system switching based on an application information blacklist provided by an exemplary embodiment of the present application;

[0030] Fig.10 is a structural block diagram of a system switching device provided by an exemplary embodiment of the present application;

[0031] Fig.11 It is a structural block diagram of an electronic device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to make the objectives, technical solutions and advantages of the present application clearer, the implementation methods of the present application will be further described in detail below with reference to the accompanying drawings.

[0033] In traditional electronic devices, only a single processor is often provided, and events are processed by an operating system running on the processor. However, as users' demand for electronic devices increases, electronic devices are also required to have stronger data processing capabilities. Therefore, electronic devices equipped with dual-core dual systems are produced. In one possible implementation, the electronic device is provided with at least a first processor and a second processor with different processing performance and power consumption, and the first system runs on the first processor, and the second system runs on the second processor. In addition, the electronic device configured with dual-core dual systems is also provided with a system switching mechanism.

[0034] For example, in products such as smart watches or smart bracelets, a high-performance processor and a low-power processor may be included at the same time, running in the first system and the second system (ie, dual-core dual system) respectively.

[0035] In order to reduce power consumption, a system running on a low-power processor often processes events with low performance requirements, and when there are events requiring high-performance processing, the system switches to a system running on a high-power processor for high-performance event processing to meet the performance requirements of electronic equipment.

[0036] Optionally, the first system runs on a low-power processor and the second system runs on a high-performance processor; optionally, the first system runs on a high-performance processor; the second system runs on a low-power processor.

[0037] In the embodiment of the present application, since the first processor and the second processor work asynchronously, and the first system and the second system need to realize system communication (or dual-core communication), in a possible application scenario, the first system is an Android operating system running on a central processing unit (CPU), and the second system is a real-time operating system (RTOS) running on a microcontroller unit (MCU).

[0038] Figure 1 This is a dual-core communication software framework diagram of an Android operating system provided by an exemplary embodiment of the present application. The dual-core communication software framework follows the design principle of "low coupling, high reliability, and high reuse", including the module development of Kernel, HIDL (Hardware Abstract Layer Interface Description Language), Native Service, Framework Service, Framework API, and APP (application) parts.

[0039] Among them, the APP module includes Launcher (desktop launcher), Setting (settings) and SystemUI (system user interface) and other functional modules, the Framework API module includes MCUManager (MCU management), SensorManager (sensor management), LocationManager (location management) and other management modules, the Framework Service module includes MCUManagerService (MCU management service), SystemSensorManager (system sensor management), LocationManagerService (location management service) and other service modules, the Native Service module includes dccservice (dcc service), Sensorservice (sensor service) and other service modules, the HIDL module includes SensorHAL (sensor hardware abstraction layer), GPS HAL (global positioning system hardware abstraction layer) and other modules. The Kernel module includes DCC Transfer Driver (DCC transmission driver) such as dcc_data, Mcu_sensor, and Mcu_gps.

[0040] As the interface layer connecting the upper and lower layers in the dual-core communication software framework, the transport layer shields the transmission details of the lower layer (data link layer) of the system from the application layer and provides service channels for application scenarios. As the main body of service provision, the application layer responds to human-computer interaction and transmits the data generated in the process of human-computer interaction through the transport layer, as well as responds to external data requests.

[0041] RTOS is designed based on the principle of peer-to-peer. Taking the electronic device as a smart watch as an example, Figure 2 It is a dual-core communication software framework diagram of RTOS provided by an exemplary embodiment of the present application.

[0042] like Figure 2 As shown in the figure, the dual-core communication software framework of RTOS is divided into application layer (Application Layer), service layer (Service Layer), framework layer (Framework Layer), hardware abstraction layer (Hardware abstraction layer) and platform layer (Platform Layer).

[0043] The application layer includes watch face, Daily Tracker, Message center, Voice around Apps, Health Apps, Settings and other application modules; the service layer includes Sport & health task, System managertask, AMS, AudioService, Log Service, OFTP Service, BT Service, DelegateService, RPC Service, sensor Service, storage Service and other service modules; the framework layer includes Message Pub, UIFramework, G2D Engine, Audio Middleware, Preference, File The hardware abstraction layer includes hardware abstraction modules such as Screen / TP (screen / touch screen), sensors, Keypad, and Motor; the platform layer includes board support packages (BSP) and low-level drivers, among which BSP includes Screen / TP, Codec (codec), sensors, Flash, PSRAM (pseudo-static random access memory), etc. Low-level drivers include Uart (universal asynchronous receiver / transmitter), ADC (analog-to-digital converter), GPIO (general input and output), SPI (serial peripheral interface), I2C (integrated circuit bus), IOS (input and output system), PCM (pulse code modulation), I2S (integrated audio bus), and HWTimer (hardware timer).

[0044] It should be noted that the above dual-core communication software framework is only used for illustrative purposes. Those skilled in the art may also add, delete or modify the above framework according to actual needs. The embodiments of the present application do not limit the specific structure of the dual-core communication software framework.

[0045] See also Figure 3 , Figure 3 The flowchart of a system switching method provided by an exemplary embodiment of the present application is shown in FIG.

[0046] Step 301: The second system monitors an event triggered by an application, where the application is run by the second system.

[0047] Optionally, the electronic device is a device such as a smart watch or smart bracelet that includes a high-performance processor and a low-power processor.

[0048] The high-performance processor and the low-power processor in the electronic device run the first system and the second system respectively. Since the first processor and the second processor work asynchronously, and the first system and the second system need to realize system communication (or dual-core communication). In the embodiment of the present application, the second system is an Android operating system running on a central processing unit (CPU), and the first system is a real-time operating system (RTOS) running on a microcontroller unit (MCU) as an example for explanation.

[0049] In a possible implementation, the electronic device is provided with a first processor and a second processor, wherein the processing performance of the first processor is lower than the processing performance of the second processor (the processing capability and processing speed of the first processor are lower than those of the second processor), and the power consumption of the first processor is lower than that of the second processor. Accordingly, the second system (run by the second processor) can process events processed by the first system (run by the first processor), while the first system may not be able to process events processed by the second system.

[0050] In another possible implementation, the electronic device may also be provided with a single processor, and the first system and the second system respectively run on different cores of the processor, wherein the processing performance of the core running the second system is higher than the processing performance of the core running the first system.

[0051] For example, if the electronic device is a smart watch, the first processor is an MCU, the second processor is a CPU, the first system is an RTOS, and the second system is an Android system. Accordingly, the events that can be processed by the first system include dial display, dial interface switching, notification message display, and other scenes with low processing performance requirements or weak interaction scenes; the events that can be processed by the second system include answering calls, launching applications, dial editing, function settings, and other scenes with high processing performance requirements or strong interaction scenes.

[0052] In a possible implementation, the working mode of the electronic device includes one or more of a performance mode, a hybrid mode, and a low power consumption mode. The electronic device can be provided with one or more of these modes according to product requirements, all of which are within the scope of protection of the present application. For example, in the performance mode, the control of the display device is always controlled by a high-performance processor (such as the second system with higher performance in the first system and the second system), and both systems are running when processing business; in the low power consumption mode, only the processor with lower power consumption (such as the first processor) remains awake or in sleep mode, while the processor with high power consumption (such as the second processor) remains off, which can also be understood as the low power consumption system is not turned off, and the high power consumption system is turned off; in the hybrid mode, the first system and the second system may both be in operation or sleep mode, and can be automatically switched according to business requirements to balance power consumption and performance. For example, when an event is processed only by the first system, the second processor is in sleep mode. In some embodiments, when the second processor is awakened for processing, the first processor (first system) may not sleep and may assist the second processor (second system); in some embodiments, when there is no business demand, both the first processor (first system) and the second processor (second system) sleep; in some embodiments, in hybrid mode, the control of the display device (such as a display screen) may also be switched between the first system and the second system. For example, when running an application on the second system, the control of the display screen belongs to the second system, and when the second system is asleep, the control of the display screen belongs to the first system. It can be understood that the electronic device of the present application can also be in other operating modes, which is not limited to this.

[0053] Optionally, in the awake state, system-related data is cached in the memory (RAM) so that the system-related data can be run at any time. In the sleep state, most of the hardware modules of the processor are turned off, and the system-related data is stored in the hard disk (ROM), and is written to the memory by the hard disk when switching to the awake state.

[0054] Unlike electronic devices with strong interactive properties such as smartphones, wearable devices, as an auxiliary electronic device, only have weak interactions with users in most usage scenarios. For example, in most scenarios, users only raise their wrists to check the time through smart watches. Therefore, when the wearable device processes events through the first system, it controls the second processor to be in a dormant state (the second system is in a dormant state), thereby reducing the overall power consumption of the wearable device.

[0055] Optionally, when the first system is in the awake state, the electronic device displays the system interface of the first system, for example, the wearable device displays the dial interface. In one possible application scenario, when the first system is in the awake state, the second system is in the dormant state; in another possible application scenario, when the first system is in the awake state, the second system is also in the awake state, and the first system is in the foreground running state, while the second system is in the background running state.

[0056] Optionally, the application installed in the electronic device is an application that supports running in the second system. The application may be a native application or a third-party application. Optionally, the application may be started based on a trigger start operation when the second system is running in the foreground, or may be started based on an event triggered by the application when the second system is running in the background or in a dormant state.

[0057] For the case where the application is started based on an event triggered by itself. For example, the application is a map application, and the user sets a destination in the application. After the user is at the destination, the application requests to start running to remind the user that the destination has been reached. For another example, the application is a learning application, and the user sets a target learning time in the application. After the target learning time is reached, the application requests to start running to remind the user that the target learning time has been reached.

[0058] In this embodiment, in order to promptly respond to events triggered by the application, the second system monitors the events triggered by the application in real time.

[0059] Step 302: When an event triggered by an application is monitored and the event meets the system switching condition, and the first system has the screen control authority, the second system obtains the screen control authority from the first system.

[0060] When the second system has screen control authority and monitors events triggered by the application, the second system can directly control the screen to display the application interface of the application.

[0061] When the first system has screen control authority, after the second system monitors the event triggered by the application, in order to improve the accuracy of system switching and avoid invalid switching between the two systems, it can first determine whether the event triggered by the current application meets the system switching condition, so that when the event meets the system switching condition, the second system obtains the screen control authority from the first system. For example, the second system can send a screen control authority transfer request to the first system to obtain the control authority of the screen.

[0062] Optionally, an event that satisfies the system switching condition means that the event triggered by the application is an event that has a screen display requirement. For example, if the application requests for foreground operation and display, the event triggered by the application satisfies the system switching condition. For another example, when the event triggered by the application is a request for background operation, since there is no screen display requirement, the event triggered by the application does not meet the system switching condition.

[0063] Step 303: When the screen control authority is obtained, the second system controls the screen to display the application interface of the application.

[0064] Optionally, after the second system obtains the screen control authority from the first system, it can control the application interface of the screen display application.

[0065] Indicative, such as Figure 4 As shown, the electronic device is a smart wearable device. When the first system has screen control authority, the first system controls the screen to display the first system main interface 41. At the same time, the second system monitors events triggered by applications, and when events triggered by map applications are monitored and the event meets the system switching conditions, the second system sends a screen control authority transfer request to the first system. Therefore, when the second system obtains screen control authority, the second system controls the screen to display the "destination reached" reminder interface 42 corresponding to the map application.

[0066] In a possible implementation, after the second system obtains the screen control authority, the first system is in a background running state.

[0067] To sum up, in the embodiment of the present application, the second system monitors the events triggered by the applications running in the system in real time, and when the events triggered by the applications are monitored and the events meet the system switching conditions, if the current first system has screen control authority, the second system obtains the screen control authority from the first system, and when the screen control authority is obtained, the application interface of the application displayed on the screen is controlled, thereby realizing that the second system actively executes the system switching based on the monitored events, without waiting for the application to send a system switching request before executing the system switching, thereby improving the system switching efficiency between the dual systems.

[0068] In order to improve the efficiency of system switching, in a possible implementation, it is possible to determine whether the event meets the system switching condition according to the event type of the application triggering event. The following uses exemplary embodiments to illustrate the system switching process under different event types.

[0069] See also Figure 5 , Figure 51 is a flowchart of a system switching method provided by another exemplary embodiment of the present application. The method is applied to an electronic device, the electronic device supports running a first system and a second system, and the method includes the following steps.

[0070] Step 501: The second system monitors an event triggered by an application, where the application is run by the second system.

[0071] The implementation of this step may refer to the above step 301, and this embodiment will not be described in detail here.

[0072] Step 502: When an event triggered by an application is monitored, and the event is a screen-on event, and the first system has screen control authority, the second system obtains screen control authority from the first system.

[0073] For an event that meets the system switching conditions, it can be understood that when the first system has screen control authority, the event triggered by the application running in the second system is a screen light event. Therefore, system switching is required to enable the second system to have screen control authority, thereby controlling the application interface of the screen display application.

[0074] In some embodiments, the second system can determine whether the event triggered by the application meets the system switching condition by monitoring whether the event is a screen-on event.

[0075] Optionally, the reasons for causing the second system screen lighting event may include multiple reasons. For example, a user clicks on an application startup control in the first system, presses a physical button, or slides on the first application interface. These are all ways of starting an application run by the second system from the first system, and are all application startup events requested by the first system to the second system. For the second system, these are passive response system switching events.

[0076] In the embodiment of the present application, the second system monitors the screen-on event and determines whether the screen-on event is triggered by an application in the second system, thereby determining that the event meets the system switching condition and obtains the screen control authority from the first system. For the second system, this is an actively initiated system switching event. For example, the second system can send a screen control authority transfer request to the first system to obtain the control authority of the screen.

[0077] Optionally, the screen light event triggered by the application refers to the event that the application requests to run and display in the foreground. For example, when the application is started or switched from background operation to foreground operation, the application will request to trigger the screen light. For another example, when the background service of the application needs to display important information to the user, such as when receiving an emergency notification or reminder, the application will also request to trigger the screen light.

[0078] For example, taking the second system as an Android system, the screen-on process is usually managed by the Power Manager Service (PMS). When an incoming call request is detected, the Power Manager Service is responsible for receiving the incoming call screen-on request and executing the related screen-on process, so that when the second system monitors that the Power Manager Service starts to execute the screen-on process, the second system obtains the screen control authority from the first system.

[0079] In a possible implementation, the second system monitors a screen-on event within the system, but the screen-on event is triggered by a user pressing a physical button rather than an application actively triggering the screen-on event. In this case, the second system does not actively obtain screen control authority from the first system.

[0080] For example, when the first system receives a user's start operation on an application in the second system, the first system can directly transfer the screen control authority to the second system. This process is different from the process in which the second system actively monitors events triggered by the application in the embodiment of the present application.

[0081] In another possible implementation, the second system monitors a screen-on event within the system and determines that the screen-on event is triggered by an application, so that the second system actively obtains screen control authority from the first system.

[0082] Step 503: When an event triggered by an application is monitored, and the event is an application self-starting event, and the first system has the screen control authority, the second system obtains the screen control authority from the first system.

[0083] For an event that meets the system switching conditions, it can also be understood that when the first system has screen control authority, the event triggered by the application running in the second system is an application self-start event. Therefore, system switching is required to enable the second system to have screen control authority, thereby controlling the application interface of the screen display application.

[0084] In some embodiments, the second system can determine whether the event triggered by the application meets the system switching condition by monitoring whether the event is an application self-start event.

[0085] Optionally, an application self-start event refers to an event in which an application is automatically started and run without receiving direct user operations and the application is closed. For example, a scheduled task or reminder task set by a user in the application.

[0086] For example, taking the second system as an Android system, when the application starts automatically, the application needs to start the Activity or Service component, so the second system can determine whether the application starts automatically by monitoring whether the application starts the Activity or Service component.

[0087] Optionally, the application self-starting event can also be divided into the application self-starting event running in the foreground and the application self-starting event running in the background. Among them, the application self-starting event running in the foreground requires the second system to obtain the screen control permission first, and the application self-starting event running in the background does not require the second system to obtain the screen control permission.

[0088] Optionally, taking the second system as an Android system, when it is monitored that an application starts an Activity component, it can be determined that the application is started and is running in the foreground; when it is monitored that an application starts a Service component but not an Activity component, it can be determined that the application is started but is running in the background.

[0089] In order to optimize the system switching conditions, in a possible implementation, when an event triggered by an application is monitored, and the event is an application self-start event, and the application self-start event indicates that the application is running in the foreground, and the first system has screen control authority, the second system obtains screen control authority from the first system.

[0090] In another possible implementation, when an event triggered by an application is monitored, and the event is an application self-start event, and the application self-start event indicates that the application is running in the background, and the first system has screen control authority, the second system does not need to send a screen control authority transfer request to the first system.

[0091] Step 504: When the screen control authority is obtained, the second system controls the screen to display the application interface of the application.

[0092] In a possible implementation, in order to obtain screen control authority from the first system, when an event triggered by an application is monitored and the event meets the system switching conditions and the first system has screen control authority, the second system can first send a screen control authority transfer request to the first system, so that when the first system agrees to transfer the screen control authority, the second system obtains the screen control authority from the first system.

[0093] Optionally, after monitoring that the event triggered by the application meets the system switching condition and sending a screen control authority transfer request to the first system, the first system may agree to transfer the screen control authority or may not agree to transfer the screen control authority.

[0094] In order to improve the success rate of system switching, you can also set a response time for the screen control authority transfer request, for example, set the response time to 500ms.

[0095] Optionally, the second system may also determine the corresponding response time in real time according to the application type of the application and the event type of the application triggering event before sending the screen control authority transfer request to the first system.

[0096] In a possible implementation, when receiving a transfer consent response from the first system to the screen control authority transfer request, the second system obtains the screen control authority from the first system. If the second system does not receive a transfer consent response from the first system to the screen control authority transfer request within the response time, the second system may also obtain the screen control authority from the first system.

[0097] Optionally, after sending a request for transferring screen control authority to the first system, the second system may enter a response countdown. When the response time is reached and no response is received from the first system indicating that the second system has agreed to transfer the screen control authority, the second system will no longer wait for a response from the first system and will directly obtain screen control authority from the first system.

[0098] In this embodiment, the events triggered by the application are divided into screen light events and application self-start events, so that by monitoring the screen light events and application self-start events respectively, it is determined whether the events triggered by the application meet the system switching conditions, thereby improving the efficiency of automatic system switching and avoiding invalid switching between systems.

[0099] Among them, for the screen light event, when the screen light event is triggered by an application, it is determined that the system switching condition is met; for the application self-start event, when the application self-start event indicates that the application is running in the foreground, it is determined that the system switching condition is met.

[0100] In addition, in the process of the second system sending a screen control authority transfer request to the first system, by setting the response time, it is ensured that the second system can obtain the screen control authority from the first system, thereby ensuring the success rate of system switching.

[0101] See also Figure 6 , Figure 6 It is a flowchart of determining whether to perform system switching by monitoring the screen-on event provided by an exemplary embodiment of the present application.

[0102] Step 601: The second system monitors a screen-on event.

[0103] Step 602: Is the current screen control authority in the first system?

[0104] When the second system monitors the screen-on event, the second system determines whether the current screen control authority is in the first system.

[0105] Step 603: The second system controls the screen to execute a screen light event.

[0106] When the first system does not have screen control authority and the second system has screen control authority, the second system directly controls the screen to execute a screen light event and displays a screen light interface corresponding to the screen light event.

[0107] Step 604: Is it a screen-lighting event triggered by an application?

[0108] When the first system has the screen control authority, the second system needs to determine whether the screen-on event satisfies the system switching condition, that is, whether the screen-on event is triggered by an application.

[0109] Step 605: The second system exits the screen-lit event response.

[0110] When the screen-lighting event is not triggered by an application, the second system exits the screen-lighting event response, that is, the second system does not execute the screen-lighting event.

[0111] Step 606: The second system sends a screen control authority transfer request to the first system.

[0112] In the case where the screen-on event is triggered by an application, that is, the screen-on event triggered by the application is monitored, and the first system has the screen control authority, the second system sends a screen control authority transfer request to the first system.

[0113] Step 607: Has a transfer consent response from the first system been received?

[0114] Step 608: Has the response time been reached?

[0115] In the case of not receiving a transfer consent response from the first system to the screen control authority transfer request, the second system continues to determine whether the response time has expired.

[0116] Step 609: The second system obtains the screen control authority from the first system, and controls the screen to display the application interface of the application.

[0117] When receiving a transfer consent response from the first system to the screen control authority transfer request, the second system acquires the screen control authority from the first system and controls the screen to display an application interface of the application.

[0118] If the second system does not receive a response from the first system agreeing to transfer the screen control authority request but the response time has expired, the second system acquires the screen control authority from the first system and controls the application interface of the screen display application.

[0119] See also Figure 7 , Figure 7 This is a flowchart of determining whether to perform a system switch by monitoring an application self-starting event, provided by an exemplary embodiment of the present application.

[0120] Step 701: The second system monitors application self-starting events.

[0121] Step 702: Is the current screen control authority in the first system?

[0122] When the second system monitors the application self-starting event, the second system determines whether the current screen control authority is in the first system.

[0123] Step 703: The second system controls the screen to execute an application self-starting event.

[0124] When the first system does not have the screen control authority and the second system has the screen control authority, the second system directly controls the screen to execute the application self-starting event and displays the application interface corresponding to the application self-starting event.

[0125] Step 704: The second system sends a screen control authority transfer request to the first system.

[0126] When the second system monitors the application self-start event and the first system has the screen control authority, the second system sends a screen control authority transfer request to the first system.

[0127] Step 705: Has a transfer consent response from the first system been received?

[0128] Step 706: Has the response time been reached?

[0129] In the case of not receiving a transfer consent response from the first system to the screen control authority transfer request, the second system continues to determine whether the response time has expired.

[0130] Step 707: The second system obtains the screen control authority from the first system, and controls the screen to display the application interface of the application.

[0131] When receiving a transfer consent response from the first system to the screen control authority transfer request, the second system acquires the screen control authority from the first system and controls the screen to display an application interface of the application.

[0132] If the second system does not receive a response from the first system agreeing to transfer the screen control authority request but the response time has expired, the second system acquires the screen control authority from the first system and controls the application interface of the screen display application.

[0133] In order to optimize the system switching process and avoid frequent or meaningless system switching, an application information blacklist can also be set, so as to determine whether the event triggered by the application meets the system switching condition based on the application information blacklist. The system switching process of adding an application information blacklist is described below using an exemplary embodiment.

[0134] See also Figure 8 , Figure 8 1 is a flowchart of a system switching method provided by another exemplary embodiment of the present application. The method is applied to an electronic device, the electronic device supports running a first system and a second system, and the method includes the following steps.

[0135] Step 801: The second system monitors an event triggered by an application, where the application is run by the second system.

[0136] The implementation of this step may refer to the above step 301, and this embodiment will not be described in detail here.

[0137] Step 802: When an event triggered by an application is monitored, the application information of the application does not conform to the application information blacklist, and the first system has the screen control authority, the second system obtains the screen control authority from the first system.

[0138] Optionally, when the event triggered by the application is a screen-on event, the application information of the application may include one or more of an application package name, an application class name, and application screen-on information.

[0139] The application package name is the unique identifier of the application in the system. The application class name is a class instance in the programming code of the application, and the application class name is usually a part of the application package name.

[0140] The application screen-on information refers to the trigger condition information contained when the application triggers the screen-on event. For example, when an application triggers the screen-on event based on a scheduled task, the trigger condition information contained therein may include the scheduled task completion information and the UI interface drawing information.

[0141] Optionally, when the event triggered by the application is an application self-start event, the application information of the application may include one or more of an application package name, an application class name, the number of application self-start times, and the application self-start time.

[0142] The number of application self-starts may be the number of application self-starts within a preset time period. Optionally, the second system may count the number of application self-starts of each application during the process of monitoring the application self-start event.

[0143] Optionally, the application information blacklist refers to a list of application information that does not support system switching, which may include one or more of a blacklist of application package names that do not support system switching, a blacklist of application class names that do not support system switching, application screen light information rules, a threshold for the number of times the first application is self-started, and a time period for self-starting applications that do not support system switching.

[0144] The application screen-on information rule may include an application screen-on information rule for a certain type of application, or an application screen-on information rule for a certain application. Setting the application screen-on information rule can effectively avoid the problem of executing a system switch when the application screen-on information of a certain application is incomplete.

[0145] For example, for applications with scheduled tasks, the application screen information only includes the scheduled task completion information but does not include the UI interface drawing information. In this case, the application screen information is considered incomplete and does not comply with the application screen information rules, that is, the application information complies with the application information blacklist.

[0146] Among them, setting the first application self-starting times threshold can effectively avoid the problem of frequent system switching caused by frequent self-starting of a certain application. For example, the first application self-starting times threshold can be 10 times. If the number of self-starting times of a certain application in a certain day reaches 11 times, the application information is considered to meet the application information blacklist.

[0147] Among them, setting the application self-start time period can effectively avoid the problem of system switching during the user's rest time period. For example, the application self-start time period is from 23:00 to 5:00. If an application triggers an application self-start event at 2:00, it is considered that the application information meets the application information blacklist.

[0148] Therefore, for the case where the application information meets the application information blacklist, it may include one or more of the following: the application package name of the application belongs to the application package name blacklist; the application class name of the application belongs to the application class name blacklist; the application screen light information of the application does not meet the application screen light information rules; the application self-start times of the application exceeds the first application self-start times threshold; the application self-start time of the application belongs to the application self-start time period.

[0149] The process of determining whether the application information of the application complies with the application information blacklist may be performed by the first system or the second system.

[0150] In a possible implementation, when an event triggered by an application is monitored and the first system has screen control authority, the second system first obtains the application information of the application, and directly determines whether the application information of the application complies with the application information blacklist based on the application information blacklist. If it is determined that the application information of the application does not comply with the application information blacklist, the second system obtains the screen control authority from the first system; if it is determined that the application information of the application complies with the application information blacklist, the second system does not obtain the screen control authority from the first system.

[0151] In another possible implementation, when an event triggered by an application is monitored and the first system has screen control authority, the second system first obtains application information of the application and sends the application information to the first system, and the first system determines whether the application information of the application complies with the application information blacklist according to the application information blacklist. Then, when receiving an information confirmation message returned by the first system, the second system obtains screen control authority from the first system, wherein the information confirmation message indicates that the application information of the application does not comply with the application information blacklist.

[0152] Optionally, in order to improve the data transmission efficiency between the first system and the second system, when the first system determines whether the application information of the application complies with the application information blacklist, the second system can send the application information of the application and the screen control authority transfer request to the first system at the same time, so that when the application information does not comply with the application information blacklist, the first system directly transfers the screen control authority to the second system; when the application information complies with the application information blacklist, the first system can feedback a response of rejecting the authority transfer to the second system.

[0153] Optionally, the data in the application information blacklist may be preset by a developer, may be manually added by a user, or may be dynamically updated by the first system or the second system based on actual application data.

[0154] In a possible implementation, the first system or the second system may dynamically update the application information blacklist according to application usage data and application self-start data of each application in the second system.

[0155] Optionally, if the number of application self-start times of a certain application in the second system reaches a second application self-start time threshold, and the application usage frequency of the application is lower than the application usage frequency threshold, the first system or the second system may add the application package name of the application to the application package name blacklist.

[0156] Optionally, when the number of application self-start times of a certain application in the second system does not reach a second application self-start time threshold and the application usage frequency of the application is higher than the application usage frequency threshold, the first system or the second system removes the application package name of the application from the application package name blacklist.

[0157] Optionally, when there is an application in the second system that is frequently self-started and a certain application class name in the application is frequently used, the first system or the second system may also add the application class name of the application to the application class name blacklist.

[0158] It should be noted that, as one of the judgment conditions for determining whether the event triggered by the application meets the system switching conditions, the data included in the application information blacklist can be determined based on the problems in the actual system switching process. The embodiment of the present application only illustrates the data that may be included in the application information blacklist, but does not limit it.

[0159] Step 803: When the screen control authority is obtained, the second system controls the screen to display the application interface of the application.

[0160] The implementation of this step may refer to the above step 303, and this embodiment will not be described in detail here.

[0161] In this embodiment, by setting an application information blacklist, after monitoring the event triggered by the application, it is determined whether the application information of the application meets the application information blacklist to determine whether the second system obtains screen control permission from the first system, thereby optimizing the system switching conditions, avoiding invalid system switching, and improving the system switching efficiency.

[0162] See also Fig. 9 , Fig. 9 It is a flowchart of determining whether to perform system switching based on an application information blacklist provided by an exemplary embodiment of the present application.

[0163] Step 901: The second system monitors events triggered by the application.

[0164] The second system monitors an event triggered by the application, which may be a screen-on event requested by the application or an application self-start event of the application.

[0165] Step 902: Is the current screen control authority in the first system?

[0166] When the second system monitors the event triggered by the application, the second system determines whether the current screen control authority is in the first system.

[0167] Step 903: the second system controls the screen to execute a screen light event.

[0168] When the first system does not have the screen control authority and the second system has the screen control authority, the second system directly controls the screen to execute the event triggered by the application and displays the application interface corresponding to the event triggered by the application.

[0169] Step 904: Does the application information of the application comply with the application information blacklist?

[0170] In the case that the first system has the screen control authority, the second system obtains application information of the application, and determines whether the application information of the application complies with the application information blacklist according to the application information blacklist.

[0171] Step 905: Second system exits event response.

[0172] When the application information of the application meets the application information blacklist, that is, the event triggered by the application does not meet the system switching condition, the second system exits the event response.

[0173] Step 906: The second system sends a screen control authority transfer request to the first system.

[0174] When the application information of the application does not conform to the application information blacklist, that is, when an event triggered by the application is monitored and the application information of the application does not conform to the application information blacklist, and the first system has screen control authority, the second system sends a screen control authority transfer request to the first system.

[0175] Step 907: Has a transfer consent response from the first system been received?

[0176] Step 908: Has the response time been reached?

[0177] In the case of not receiving a transfer consent response from the first system to the screen control authority transfer request, the second system continues to determine whether the response time has expired.

[0178] Step 909: The second system obtains the screen control authority from the first system, and controls the screen to display the application interface of the application.

[0179] When receiving a transfer consent response from the first system to the screen control authority transfer request, the second system acquires the screen control authority from the first system and controls the screen to display an application interface of the application.

[0180] If the second system does not receive a response from the first system agreeing to transfer the screen control authority request but the response time has expired, the second system acquires the screen control authority from the first system and controls the application interface of the screen display application.

[0181] See also Fig.10 , Fig.10: is a structural block diagram of a system switching device provided by an exemplary embodiment of the present application. The device is used in an electronic device, and the electronic device supports running a first system and a second system, and the device includes:

[0182] The second system module 1002 is used to monitor events triggered by an application, and the application is run by the second system module 1002;

[0183] The second system module 1002 is further configured to obtain the screen control permission from the first system module 1001 when an event triggered by the application is monitored and the event meets the system switching condition and the first system module 1001 has the screen control permission;

[0184] The second system module 1002 is further configured to control the screen to display the application interface of the application when the screen control authority is obtained.

[0185] Optionally, the second system module 1002 is used to:

[0186] When an event triggered by the application is monitored, and the event is a screen-on event, and the first system module 1001 has the screen control authority, obtaining the screen control authority from the first system module 1001; or,

[0187] When an event triggered by the application is monitored, and the event is an application self-start event, and the first system module 1001 has the screen control permission, the screen control permission is obtained from the first system module 1001.

[0188] Optionally, the second system module 1002 is used to:

[0189] When an event triggered by the application is monitored, and the event is a self-starting event of the application, and the self-starting event of the application indicates that the application is running in the foreground, and the first system module 1001 has the screen control permission, obtaining the screen control permission from the first system module 1001;

[0190] The second system module 1002 is further used for:

[0191] When an event triggered by the application is monitored, and the event is a self-start event of the application, and the self-start event of the application indicates that the application is running in the background, and the first system module 1001 has the screen control permission, the screen control permission is not obtained from the first system module 1001.

[0192] Optionally, the second system module 1002 is used to:

[0193] When an event triggered by the application is monitored, the application information of the application does not conform to the application information blacklist, and the first system module 1001 has the screen control permission, the screen control permission is obtained from the first system module 1001.

[0194] Optional,

[0195] In the case where the event triggered by the application is a screen-on event, the application information of the application includes one or more of an application package name, an application class name, and application screen-on information; wherein the application screen-on information refers to trigger condition information included when the application triggers a screen-on event;

[0196] In the case where the event triggered by the application is an application self-start event, the application information of the application includes one or more of an application package name, an application class name, the number of application self-starts, and an application self-start time;

[0197] The application information blacklist is a list of application information that does not support system switching, including one or more of an application package name blacklist, an application class name blacklist, application screen light information rules, a first application self-start times threshold, and an application self-start time period.

[0198] Optionally, the situation where the application information meets the application information blacklist includes one or more of the following:

[0199] The application package name of the application belongs to the application package name blacklist;

[0200] The application class name of the application belongs to the application class name blacklist;

[0201] The application screen-on information of the application does not comply with the application screen-on information rule;

[0202] The number of times the application is self-started by the application exceeds the first application self-started number threshold;

[0203] The application self-start time of the application belongs to the application self-start time period.

[0204] Optionally, the first system module 1001 or the second system module 1002 is used to:

[0205] The application information blacklist is dynamically updated according to the application usage data and application self-starting data of each application in the second system module 1002 .

[0206] Optionally, the first system module 1001 or the second system module 1002 is used to:

[0207] When the number of application self-start times of the application in the second system module 1002 reaches the second application self-start times threshold, and the application usage frequency of the application is lower than the application usage frequency threshold, adding the application package name of the application to the application package name blacklist;

[0208] When the number of application self-start times of the application in the second system module 1002 does not reach the second application self-start time threshold and the application usage frequency of the application is higher than the application usage frequency threshold, the application package name of the application is removed from the application package name blacklist.

[0209] Optionally, the second system module 1002 is used to:

[0210] When an event triggered by the application is monitored and the first system module 1001 has the screen control permission, obtaining the application information of the application;

[0211] When it is determined that the application information of the application does not conform to the application information blacklist, the screen control authority is obtained from the first system module 1001 .

[0212] Optionally, the second system module 1002 is used to:

[0213] When an event triggered by the application is monitored and the first system module 1001 has the screen control permission, obtaining the application information of the application and sending the application information to the first system module 1001;

[0214] Upon receiving an information confirmation message returned by the first system module 1001 , the screen control permission is obtained from the first system module 1001 , wherein the information confirmation message indicates that the application information of the application does not conform to the application information blacklist.

[0215] Optionally, the second system module 1002 is used to:

[0216] When an event triggered by the application is monitored, and the event meets a system switching condition, and the first system has screen control authority, sending a screen control authority transfer request to the first system;

[0217] Upon receiving a transfer consent response from the first system module 1001 to the screen control authority transfer request, acquiring the screen control authority from the first system module 1001; or,

[0218] In the case where no response of consent to transfer of the screen control authority transfer from the first system module 1001 is received within the response time, the screen control authority is acquired from the first system module 1001 .

[0219] To sum up, in the embodiment of the present application, the second system monitors the events triggered by the applications running in the system in real time, and when the events triggered by the applications are monitored and the events meet the system switching conditions, if the current first system has screen control authority, the second system obtains the screen control authority from the first system, and when the screen control authority is obtained, the application interface of the application displayed on the screen is controlled, thereby realizing that the second system actively executes the system switching based on the monitored events, without waiting for the application to send a system switching request before executing the system switching, thereby improving the system switching efficiency between the dual systems.

[0220] Please refer to Fig.11 , Fig.11 11 is a block diagram of an electronic device provided by an exemplary embodiment of the present application. The electronic device in the present application may include one or more of the following components: a processor 1110 and a memory 1120 .

[0221] Optionally, the processor 1110 includes at least a first processor 1111 and a second processor 1112, wherein the first processor 1111 is used to run the first system and the second processor 1112 is used to run the second system. In some embodiments, the power consumption of the first processor 1111 is lower than the power consumption of the second processor 1112, and the performance of the first processor 1111 is lower than the performance of the second processor 1112. In other embodiments, the power consumption of the first processor 1111 is higher than the power consumption of the second processor 1112, and the performance of the first processor 1111 is higher than the performance of the second processor 1112. For example, the power consumption of the first processor 1111 and the power consumption of the second processor 1112 can be understood as standby (sleep) power consumption, power consumption for processing the same business, or overall power consumption, etc., and can be measured with an ammeter. For example, the performance of the first processor 1111 and the performance of the second processor 1112 can be understood as computing power or hardware resources, etc. The processor 1110 uses various interfaces and lines to connect various parts of the entire electronic device, and executes various functions of the electronic device and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 1120, and calling data stored in the memory 1120. Optionally, the processor 1110 can be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), and programmable logic array (PLA). The processor 1110 can integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a neural network processor (NPU), and a modem. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content that needs to be displayed on the touch display; the NPU is used to implement artificial intelligence (AI) functions; and the modem is used to process wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor 1110, but may be implemented by a separate chip.

[0222] The memory 1120 may include a random access memory (RAM) or a read-only memory (ROM). Optionally, the memory 1120 includes a non-transitory computer-readable storage medium. The memory 1120 may be used to store instructions, programs, codes, code sets, or instruction sets. The memory 1120 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the following various method embodiments, etc.; the data storage area may store data created according to the use of the electronic device (such as audio data, a phone book), etc.

[0223] The electronic device in the embodiment of the present application further includes a communication component 1130 and a display component 1140. The communication component 1130 may be a Bluetooth component, a WiFi (Wireless Fidelity) component, an NFC (Near Field Communication) component, etc., and is used to communicate with an external device (server or other terminal device) via a wired or wireless network; the display component 1140 is used to display a graphical user interface and / or receive user interaction operations.

[0224] In addition, those skilled in the art can understand that the structure of the electronic device shown in the above drawings does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown in the drawings, or combine certain components, or arrange the components differently. For example, the electronic device also includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a speaker, a microphone, and a power supply, which will not be described in detail here.

[0225] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores at least one computer instruction, and the computer instruction is loaded and executed by a processor to implement the system switching method as described in the above embodiment.

[0226] Optionally, the computer readable storage medium may include: ROM, RAM, solid state drives (SSD) or optical disks, etc. Among them, RAM may include resistance random access memory (ReRAM) and dynamic random access memory (DRAM).

[0227] An embodiment of the present application also provides a computer program product, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium; a processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the system switching method described in the above embodiment.

[0228] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A system switching method, characterized in that: The method is used in an electronic device, wherein the electronic device supports running a first system and a second system; The method comprises: The second system monitors an event triggered by an application, and the application is run by the second system; When an event triggered by the application is monitored, and the event meets a system switching condition, and the first system has screen control authority, the second system obtains the screen control authority from the first system; When the screen control permission is obtained, the second system controls the screen to display the application interface of the application.

2. The method according to claim 1, characterized in that: The second system obtaining the screen control permission from the first system when the event triggered by the application is monitored and the event meets the system switching condition and the first system has the screen control permission, includes: When an event triggered by the application is monitored, and the event is a screen-on event, and the first system has the screen control permission, the second system obtains the screen control permission from the first system; or, When an event triggered by the application is monitored, and the event is an application self-start event, and the first system has the screen control permission, the second system obtains the screen control permission from the first system.

3. The method according to claim 2, characterized in that The second system obtaining the screen control permission from the first system when an event triggered by the application is monitored and the event is an application self-starting event and the first system has the screen control permission includes: When an event triggered by the application is monitored, and the event is a self-starting event of the application, and the self-starting event of the application indicates that the application is running in the foreground, and the first system has the screen control permission, the second system obtains the screen control permission from the first system; The method further comprises: When an event triggered by the application is monitored, and the event is a self-start event of the application, and the self-start event of the application indicates that the application is running in the background, and the first system has the screen control permission, the second system does not obtain the screen control permission from the first system.

4. The method according to claim 1, characterized in that The second system obtaining the screen control permission from the first system when the event triggered by the application is monitored and the event meets the system switching condition and the first system has the screen control permission, includes: When an event triggered by the application is monitored, the application information of the application does not conform to the application information blacklist, and the first system has the screen control permission, the second system obtains the screen control permission from the first system.

5. The method according to claim 4, characterized in that In the case where the event triggered by the application is a screen-on event, the application information of the application includes one or more of an application package name, an application class name, and application screen-on information; wherein the application screen-on information refers to trigger condition information included when the application triggers a screen-on event; In the case where the event triggered by the application is an application self-start event, the application information of the application includes one or more of an application package name, an application class name, the number of application self-starts, and an application self-start time; The application information blacklist is a list of application information that does not support system switching, including one or more of an application package name blacklist, an application class name blacklist, application screen light information rules, a first application self-start times threshold, and an application self-start time period.

6. The method according to claim 5, characterized in that The situation where the application information meets the application information blacklist includes one or more of the following: The application package name of the application belongs to the application package name blacklist; The application class name of the application belongs to the application class name blacklist; The application screen-on information of the application does not comply with the application screen-on information rule; The number of times the application is self-started by the application exceeds the first application self-started number threshold; The application self-start time of the application belongs to the application self-start time period.

7. The method according to claim 5, characterized in that The method further comprises: The first system or the second system dynamically updates the application information blacklist according to application usage data and application self-starting data of each application in the second system.

8. The method according to claim 7, characterized in that The first system or the second system dynamically updates the application information blacklist according to application usage data and application self-start data of each application in the second system, including: When the number of application self-starts of an application in the second system reaches a second application self-start number threshold, and the application usage frequency of the application is lower than the application usage frequency threshold, the first system or the second system adds the application package name of the application to the application package name blacklist; When the number of application self-start times of the application in the second system does not reach the second application self-start time threshold and the application usage frequency of the application is higher than the application usage frequency threshold, the first system or the second system removes the application package name of the application from the application package name blacklist.

9. The method according to claim 4, characterized in that The second system obtains the screen control permission from the first system when the event triggered by the application is monitored, the application information of the application does not conform to the application information blacklist, and the first system has the screen control permission, including: When an event triggered by the application is monitored and the first system has the screen control permission, the second system obtains the application information of the application; When it is determined that the application information of the application does not conform to the application information blacklist, the second system obtains the screen control authority from the first system.

10. The method according to claim 4, characterized in that The second system obtains the screen control permission from the first system when the event triggered by the application is monitored, the application information of the application does not conform to the application information blacklist, and the first system has the screen control permission, including: When an event triggered by the application is monitored and the first system has the screen control permission, the second system obtains the application information of the application and sends the application information to the first system; Upon receiving the information confirmation message returned by the first system, the second system obtains the screen control authority from the first system, wherein the information confirmation message indicates that the application information of the application does not comply with the application information blacklist.

11. The method according to claim 1, characterized in that: The second system obtaining the screen control permission from the first system when the event triggered by the application is monitored and the event meets the system switching condition and the first system has the screen control permission, includes: When an event triggered by the application is monitored, and the event meets a system switching condition, and the first system has screen control authority, the second system sends a screen control authority transfer request to the first system; Upon receiving a transfer consent response from the first system to the screen control authority transfer request, the second system acquires the screen control authority from the first system; or, If the second system does not receive a response of consenting to the screen control authority transfer request from the first system within the response time, the second system obtains the screen control authority from the first system.

12. A system switching device, characterized in that: The device is used in an electronic device, and the electronic device supports running a first system and a second system; The device comprises: a second system module, configured to monitor an event triggered by an application, wherein the application is run by the second system module; The second system module is further configured to obtain the screen control permission from the first system module when an event triggered by the application is monitored and the event meets a system switching condition and the first system module has the screen control permission; The second system module is further configured to control the screen to display the application interface of the application when the screen control authority is obtained.

13. An electronic device, characterized in that: The electronic device includes a processor and a memory; the memory stores at least one computer instruction, and the at least one computer instruction is used to be executed by the processor to implement the system switching method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one computer instruction, and the computer instruction is loaded and executed by a processor to implement the system switching method according to any one of claims 1 to 11.

15. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; a processor of an electronic device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the electronic device executes the system switching method as described in any one of claims 1 to 11.

Images