Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
In the following description, suffixes such as "module", "part", or "unit" used to indicate elements are used only for facilitating the description of the present invention, and have no particular meaning in themselves. Thus, "module", "component" or "unit" may be used mixedly.
The wearable device provided by the embodiment of the invention comprises a mobile terminal such as an intelligent bracelet, an intelligent watch, an intelligent mobile phone and the like. With the continuous development of screen technologies, screen forms such as flexible screens and folding screens appear, and mobile terminals such as smart phones can also be used as wearable devices. The wearable device provided in the embodiment of the present invention may include: a Radio Frequency (RF) unit, a WiFi module, an audio output unit, an a/V (audio/video) input unit, a sensor, a display unit, a user input unit, an interface unit, a memory, a processor, and a power supply.
In the following description, a wearable device is taken as an example to be described, please refer to fig. 1, which is a schematic diagram of a hardware structure of a wearable device for implementing various embodiments of the present invention, where thewearable device 100 may include: RF (Radio Frequency)unit 101,wiFi module 102,audio output unit 103, a/V (audio/video)input unit 104,sensor 105,display unit 106,user input unit 107,interface unit 108,memory 109,processor 110, andpower supply 111. Those skilled in the art will appreciate that the wearable device structure shown in fig. 1 does not constitute a limitation of the wearable device, and that the wearable device may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
The following describes the various components of the wearable device in detail with reference to fig. 1:
theradio frequency unit 101 may be configured to receive and send a message or in a call process, receive and send a signal, specifically, theradio frequency unit 101 may send uplink information to a base station, and may also receive downlink information sent by the base station and send the received downlink information to theprocessor 110 of the wearable device for processing, the downlink information sent by the base station to theradio frequency unit 101 may be generated according to the uplink information sent by theradio frequency unit 101, or may be actively pushed to theradio frequency unit 101 after detecting that information of the wearable device is updated, for example, after detecting that a geographic location of the wearable device changes, the base station may send a message notification of the change of the geographic location to theradio frequency unit 101 of the wearable device, after receiving the message notification, theradio frequency unit 101 may send the message notification to theprocessor 110 of the wearable device for processing, and theprocessor 110 of the wearable device may control the message notification to be displayed on thedisplay panel 1061 of the wearable device; typically,radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, theradio frequency unit 101 may also communicate with a network and other devices through wireless communication, which may specifically include: the server may push a message notification of resource update to the wearable device through wireless communication to remind a user of updating the application program if the file resource corresponding to the application program in the server is updated after the wearable device finishes downloading the application program. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access2000 ), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
In one embodiment, thewearable device 100 may access an existing communication network by inserting a SIM card.
In another embodiment, thewearable device 100 may access an existing communication network by setting an esim card (Embedded-SIM), and by using the esim card, the internal space of the wearable device may be saved, and the thickness of the wearable device may be reduced.
It is understood that although fig. 1 shows theradio frequency unit 101, it is understood that theradio frequency unit 101 does not belong to the essential constituents of the wearable device, and can be omitted entirely as required within the scope not changing the essence of the invention. Thewearable device 100 may implement communication connection with other devices or a communication network through thewifi module 102 alone, which is not limited by the embodiment of the present invention.
WiFi belongs to short-distance wireless transmission technology, and the wearable device can help a user to send and receive e-mails, browse webpages, access streaming media and the like through theWiFi module 102, and provides wireless broadband Internet access for the user. Although fig. 1 shows theWiFi module 102, it is understood that it does not belong to the essential constitution of the wearable device, and may be omitted entirely as needed within the scope not changing the essence of the invention.
Theaudio output unit 103 may convert audio data received by theradio frequency unit 101 or theWiFi module 102 or stored in thememory 109 into an audio signal and output as sound when thewearable device 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, theaudio output unit 103 may also provide audio output related to a specific function performed by the wearable device 100 (e.g., a call signal reception sound, a message reception sound, etc.). Theaudio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and amicrophone 1042, theGraphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on thedisplay unit 106. The image frames processed by thegraphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via theradio frequency unit 101 or theWiFi module 102. Themicrophone 1042 can receive sounds (audio data) via themicrophone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and can process such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via theradio frequency unit 101 in case of a phone call mode. Themicrophone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
In one embodiment, thewearable device 100 includes one or more cameras, and by turning on the cameras, capturing of images can be realized, functions such as photographing and recording can be realized, and the positions of the cameras can be set as required.
Thewearable device 100 also includes at least onesensor 105, such as light sensors, motion sensors, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of thedisplay panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off thedisplay panel 1061 and/or the backlight when thewearable device 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the gesture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer, tapping), and the like.
In one embodiment, thewearable device 100 further comprises a proximity sensor, and the wearable device can realize non-contact operation by adopting the proximity sensor, so that more operation modes are provided.
In one embodiment, thewearable device 100 further comprises a heart rate sensor, which, when worn, enables detection of heart rate by proximity to the user.
In one embodiment, thewearable device 100 may further include a fingerprint sensor, and by reading the fingerprint, functions such as security verification can be implemented.
Thedisplay unit 106 is used to display information input by a user or information provided to the user. TheDisplay unit 106 may include aDisplay panel 1061, and theDisplay panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
In one embodiment, thedisplay panel 1061 is a flexible display screen, and when the wearable device using the flexible display screen is worn, the screen can be bent, so that the wearable device is more conformable. Optionally, the flexible display screen may adopt an OLED screen body and a graphene screen body, in other embodiments, the flexible display screen may also be made of other display materials, and this embodiment is not limited thereto.
In one embodiment, thedisplay panel 1061 of the wearable device may take a rectangular shape to wrap around when worn. In other embodiments, other approaches may be taken.
Theuser input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the wearable device. Specifically, theuser input unit 107 may include atouch panel 1071 andother input devices 1072. Thetouch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near thetouch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. Thetouch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to theprocessor 110, and can receive and execute commands sent by theprocessor 110. In addition, thetouch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. Theuser input unit 107 may includeother input devices 1072 in addition to thetouch panel 1071. In particular,other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
In one embodiment, the side of thewearable device 100 may be provided with one or more buttons. The button can realize various modes such as short-time pressing, long-time pressing, rotation and the like, thereby realizing various operation effects. The number of the buttons can be multiple, and different buttons can be combined for use to realize multiple operation functions.
Further, thetouch panel 1071 may cover thedisplay panel 1061, and when thetouch panel 1071 detects a touch operation thereon or nearby, thetouch panel 1071 transmits the touch operation to theprocessor 110 to determine the type of the touch event, and then theprocessor 110 provides a corresponding visual output on thedisplay panel 1061 according to the type of the touch event. Although in fig. 1, thetouch panel 1071 and thedisplay panel 1061 are two independent components to implement the input and output functions of the wearable device, in some embodiments, thetouch panel 1071 and thedisplay panel 1061 may be integrated to implement the input and output functions of the wearable device, and is not limited herein. For example, when receiving a message notification of an application program through therf unit 101, theprocessor 110 may control the message notification to be displayed in a predetermined area of thedisplay panel 1061, where the predetermined area corresponds to a certain area of thetouch panel 1071, and perform a touch operation on the certain area of thetouch panel 1071 to control the message notification displayed in the corresponding area on thedisplay panel 1061.
Theinterface unit 108 serves as an interface through which at least one external device is connected to thewearable apparatus 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. Theinterface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within thewearable apparatus 100 or may be used to transmit data between thewearable apparatus 100 and an external device.
In one embodiment, theinterface unit 108 of thewearable device 100 is configured as a contact, and is connected to another corresponding device through the contact to implement functions such as charging and connection. The contact can also be waterproof.
Thememory 109 may be used to store software programs as well as various data. Thememory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further,memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
Theprocessor 110 is a control center of the wearable device, connects various parts of the entire wearable device by various interfaces and lines, and performs various functions of the wearable device and processes data by running or executing software programs and/or modules stored in thememory 109 and calling up data stored in thememory 109, thereby performing overall monitoring of the wearable device.Processor 110 may include one or more processing units; preferably, theprocessor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into theprocessor 110.
Thewearable device 100 may further include a power source 111 (such as a battery) for supplying power to various components, and preferably, thepower source 111 may be logically connected to theprocessor 110 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system.
Although not shown in fig. 1, thewearable device 100 may further include a bluetooth module or the like, which is not described in detail herein. Thewearable device 100 can be connected with other terminal devices through Bluetooth, so that communication and information interaction are realized.
Please refer to fig. 2-4, which are schematic structural diagrams of a wearable device according to an embodiment of the present invention. The wearable device in the embodiment of the invention comprises a flexible screen. When the wearable device is unfolded, the flexible screen is in a strip shape; when the wearable device is in a wearing state, the flexible screen is bent to be annular. Fig. 2 and 3 show the structural schematic diagram of the wearable device screen when the wearable device screen is unfolded, and fig. 4 shows the structural schematic diagram of the wearable device screen when the wearable device screen is bent.
Based on the wearable device presented in fig. 1 to 4 above, various embodiments of the method of the present invention are presented. The wearable device may include smart bands, smart glasses, smart phones, and the like.
In the android system, event notifications are usually sent by broadcasting, for example, as shown in fig. 5, system broadcasts such as ON SCREEN (ACTION _ SCREEN _ ON) and OFF SCREEN (ACTION _ SCREEN _ OFF) can be sent to the applications a, B, and C by a Power Management Service (PMS). Specifically, the power management Service may transmit a system broadcast through an AMS (Activity Manager Service). However, if the broadcast transmission delay is long, the AMS may assume that the system desktop Application processes the event notification transmitted by the broadcast method and exceeds a predetermined threshold, and thus an ANR (Application Not Responding) problem is raised.
Referring to fig. 6, fig. 6 is a flowchart illustrating steps of an event notification method according to an embodiment of the present invention, where the method is applied to a wearable device, as shown in fig. 6, and the method includes:
step 601, obtaining system events through a window management service.
In this step, the wearable device obtains a system event through a Window Management Service (WMS). The wearable device can monitor the system through the window management service, and when the fact that an event occurs in the system is monitored, the monitored system event is obtained.
The system events may include display state change events, such as screen-out, screen-up, and the like. Specifically, the wearable device may monitor whether a display state in a power management service is changed, and obtain a display state change event of the power management service if the display state in the power management service is changed.
The system events may also include call events, such as incoming call events, call disruption events, and the like. The system event may also include a system operating state change event, such as a system sleep event, a system wake event, and the like.
Step 602, a first interface is called through the window management service, and the system event is notified to the first interface, where the first interface is an interface corresponding to the system event.
In this step, the wearable device calls a first interface through the window management service, and notifies the first interface of the system event, where the first interface is an interface corresponding to the system event. Specifically, the wearable device may determine the first interface according to the system event, for example, determine that the interface corresponding to the system event is the first interface. It will be appreciated that the interfaces for different event types are different. After determining the first interface, the wearable device calls the first interface through the window management service, and notifies the first interface of the system event.
Step 603, remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application.
In this step, after notifying the first interface of the system event, the wearable device remotely calls a system desktop application through the first interface to transfer the system event to the system desktop application, so as to notify the system event to the system desktop application.
In this embodiment, the event notification method obtains a system event through a window management service; calling a first interface through the window management service, and notifying the first interface of the system event, wherein the first interface is an interface corresponding to the system event; and remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application. Therefore, the event notification method calls the first interface corresponding to the system event through the window management service, and then remotely calls the system desktop application through the first interface, so that the system event is transmitted to the system desktop application, the notification of the system event is carried out without depending on a broadcasting mode, the notification speed of the system event can be effectively improved, and the use experience of blocking is avoided for users. In addition, the embodiment of the invention does not need to broadcast by using AMS (automatic maintenance and management system), thereby avoiding the problem of ANR (automatic noise ratio) when the system is busy.
Optionally, the system event comprises at least one of:
and displaying a state change event, a call event and a system working state change event.
In this embodiment, the system event may include one or more of a display status change event, a call event, and a system operating status change event. The display state change event comprises screen off, screen on and the like, the call event comprises an incoming call event, a call interruption event and the like, and the system working state change event comprises a system dormancy event, a system awakening event and the like.
Optionally, the obtaining the system event through the window management service includes:
monitoring, by the window management service, a system of the wearable device;
and acquiring the monitored system event under the condition that the system of the wearable device is monitored to have the event.
In this embodiment, the wearable device monitors the system of the wearable device through the window management service, and acquires the monitored system event when it is monitored that an event occurs in the system of the wearable device.
For example, when the system event includes a display state change event, for example, including turning off a screen, turning on a screen, or the like, the wearable device may monitor, through the window management service, whether a display state in the power management service is changed, and if the display state in the power management service is changed, obtain the display state change event of the power management service.
Referring to fig. 7, fig. 7 is a second flowchart of an event notification method according to an embodiment of the present invention, where the event notification method is applied to a wearable device, as shown in fig. 7, the method includes:
step 701, acquiring a system event through a window management service, wherein the system event comprises a display state change event, and the display state change event comprises screen turning off or screen lighting.
In this step, the wearable device obtains a system event through a window management service, where the system event includes a display state change event, and the display state change event includes a screen being turned off or turned on. The wearable device obtains system events through a window management service. The wearable device can monitor the system through the window management service, and when the fact that an event occurs in the system is monitored, the monitored system event is obtained.
In an Android system, a window management service and a power management service are closely matched, and in an Android framework (Android frames), the window management service can sensitively sense the change of a display state in the power management service. Specifically, the wearable device may monitor whether a display state in the power management service is changed, and obtain a display state change event of the power management service if the display state in the power management service is changed.
It is understood that the window management service and the power management service are different objects in the same process (e.g., a system process), and the window management service may call back data in the power management service. In some embodiments of the present invention, the window management service may monitor whether the display state is changed by calling back the display state data in the power management service.
Step 702, a first interface is called through the window management service, and the system event is notified to the first interface, wherein the first interface is an interface corresponding to the system event.
In this step, the wearable device calls a first interface through the window management service, and notifies the first interface of the system event, where the first interface is an interface corresponding to the system event. Specifically, the wearable device may determine the first interface according to the system event, for example, determine that the interface corresponding to the system event is the first interface. It will be appreciated that the interfaces for different event types are different. After determining the first interface, the wearable device calls the first interface through the window management service, and notifies the first interface of the system event. In this embodiment, the first interface is a screen locking service (service) interface.
And 703, remotely calling the system desktop application through the first interface, and transmitting the system event to the system desktop application.
In this step, after notifying the system event to the first interface, the wearable device remotely calls a system desktop application through the first interface, and transfers the system event to the system desktop application, so as to implement notifying the system event to the system desktop application.
In this embodiment, the event notification method obtains a system event through a window management service, where the system event includes a display state change event, and the display state change event includes turning off or turning on a screen; calling a first interface through the window management service, and notifying the first interface of the system event, wherein the first interface is an interface corresponding to the system event; and remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application. Therefore, the event notification method calls the first interface corresponding to the system event through the window management service, and then remotely calls the system desktop application through the first interface, so that the system event is transmitted to the system desktop application, the notification of the system event is carried out without depending on a broadcasting mode, the notification speed of the system event can be effectively improved, and the use experience of blocking is avoided for users. In addition, the embodiment of the invention does not need to broadcast by using AMS (automatic maintenance and management system), thereby avoiding the problem of ANR (automatic noise ratio) when the system is busy.
Optionally, the first interface comprises a lock screen service interface.
Referring to fig. 8, fig. 8 is a third schematic flowchart of an event notification method according to an embodiment of the present invention, where the event notification method is applied to a wearable device, as shown in fig. 8, the method includes:
step 801, monitoring whether the display state in the power management service is changed or not through the window management service.
In this step, the wearable device monitors whether the display state of the power management service changes through the window management service.
Step 802, if the display state in the power management service is changed, acquiring a display state change event of the power management service.
In this step, if the display state in the power management service is changed, a display state change event of the power management service is acquired.
Inside the android system, the window management service and the power management service are closely matched, and inside the android architecture, the window management service can acutely sense the change of the display state in the power management service. The window management service and the power management service are different objects in the same process (such as a system process), and the window management service can call back data in the power management service. In some embodiments of the present invention, the window management service may monitor whether the display state is changed by calling back the display state data in the power management service.
Step 803, a first interface is called through the window management service, and the display state change event is notified to the first interface, where the first interface is an interface corresponding to the display state change event.
In this step, the wearable device calls a first interface through the window management service, and notifies the display state change event to the first interface, where the first interface is an interface corresponding to the display state change event, that is, a screen locking service interface. The display state change event may include a SCREEN-ON (ACTION _ SCREEN _ ON) or a SCREEN-OFF (ACTION _ SCREEN _ OFF).
Step 804, a system desktop application is remotely called through the first interface, and the display state change event is transmitted to the system desktop application.
In this step, the wearable device remotely calls a system desktop application through the first interface, and transmits the display state change event to the system desktop application. It can be understood that when the display state change event received by the screen locking service interface is received, the semantics can be transmitted to the system desktop application through remote calling, so that the speed of sensing the display state change by the system desktop application can be greatly improved, and the system desktop application can update the display data according to the display state change (for example, the data to be displayed is updated when the display state change event is a bright screen).
In this embodiment, the event notification method monitors whether a display state in the power management service is changed through the window management service; if the display device in the power management service is changed, acquiring a display state change event of the power management service; calling a first interface through the window management service, and notifying the display state change event to the first interface, wherein the first interface is an interface corresponding to the display state change event; and remotely calling a system desktop application through the first interface, and transmitting the display state change event to the system desktop application. Therefore, the event notification method calls the first interface corresponding to the system event through the window management service, and then remotely calls the system desktop application through the first interface, so that the system event is transmitted to the system desktop application, the notification of the system event is carried out without depending on a broadcasting mode, the notification speed of the system event can be effectively improved, and the use experience of blocking is avoided for users.
Optionally, the invoking a first interface by the window management service includes:
calling the first interface across processes through the window management service.
Optionally, the remotely invoking the system desktop application through the first interface includes:
and remotely calling the system desktop application across processes through the first interface.
In this embodiment, the wearable device may invoke the first interface across processes through the window management service, and invoke the system desktop application across processes through the first interface, for example, as shown in fig. 9.
Those skilled in the art will appreciate that all or part of the steps of the method of the above embodiments may be implemented by hardware associated with at least one program instruction, where the at least one program may be stored in thememory 109 of thewearable device 100 shown in fig. 1 and executed by theprocessor 110, and the at least one program when executed by theprocessor 110 implements the steps of:
acquiring a system event through a window management service;
calling a first interface through the window management service, and notifying the first interface of the system event, wherein the first interface is an interface corresponding to the system event;
and remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application.
Optionally, the system event comprises at least one of:
and displaying a state change event, a call event and a system working state change event.
Optionally, the display state change event includes turning off a screen or lighting up a screen.
Optionally, the first interface comprises a lock screen service interface.
Optionally, the obtaining the system event through the window management service includes:
monitoring whether the display state in the power management service is changed or not through the window management service;
and if the display state in the power management service is changed, acquiring a display state change event of the power management service.
Optionally, the invoking a first interface by the window management service includes:
calling the first interface across processes through the window management service.
Optionally, the remotely invoking the system desktop application through the first interface includes:
and remotely calling the system desktop application across processes through the first interface.
The acquiring system events through the window management service includes:
monitoring, by the window management service, a system of the wearable device;
and under the condition that the system of the wearable device is monitored to have an event, acquiring the monitored system event.
In this embodiment, the wearable device obtains a system event through a window management service; calling a first interface through the window management service, and notifying the first interface of the system event, wherein the first interface is an interface corresponding to the system event; and remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application. Therefore, the wearable device calls the first interface corresponding to the system event through the window management service, and then remotely calls the system desktop application through the first interface, so that the system event is transmitted to the system desktop application without depending on a broadcast mode to notify the system event, the notification speed of the system event can be effectively improved, and the use experience of blocking for a user is avoided.
Based on the above embodiments, it can be seen that, if the device is a watch, a bracelet, or a wearable device, the screen of the device may not cover the watchband region of the device, and may also cover the watchband region of the device. Here, the present invention provides an optional embodiment, in which the device may be a watch, a bracelet, or a wearable device, and the device includes a screen and a connection portion. The screen can be a flexible screen, and the connecting part can be a watchband. Optionally, the screen of the device or the display area of the screen may partially or completely cover the wristband of the device. As shown in fig. 10, fig. 10 is a hardware schematic diagram of an implementation manner of a wearable device provided in an embodiment of the present application, where a screen of the device extends to both sides, and a part of the screen covers a watchband of the device. In other embodiments, the screen of the device may also be entirely covered on the wristband of the device.
It will be understood by those skilled in the art that all or part of the steps of the method for implementing the above embodiments may be implemented by hardware associated with at least one program instruction, the at least one program may be stored in a computer readable storage medium, and when executed, the at least one program may comprise the steps of:
acquiring a system event through a window management service;
calling a first interface through the window management service, and notifying the first interface of the system event, wherein the first interface is an interface corresponding to the system event;
and remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application.
Optionally, the system event comprises at least one of:
and displaying a state change event, a call event and a system working state change event.
Optionally, the display state change event includes turning off a screen or lighting up a screen.
Optionally, the first interface comprises a lock screen service interface.
Optionally, the obtaining the system event through the window management service includes:
monitoring whether the display state in the power management service is changed or not through the window management service;
and if the display state in the power management service is changed, acquiring a display state change event of the power management service.
Optionally, the invoking a first interface by the window management service includes:
calling the first interface across processes through the window management service.
Optionally, the remotely invoking the system desktop application through the first interface includes:
and remotely calling the system desktop application across processes through the first interface.
The acquiring system events through the window management service includes:
monitoring, by the window management service, a system of the wearable device;
and acquiring the monitored system event under the condition that the system of the wearable device is monitored to have the event.
In this embodiment, when the at least one program is executed, the system event is obtained through a window management service; calling a first interface through the window management service, and notifying the first interface of the system event, wherein the first interface is an interface corresponding to the system event; and remotely calling a system desktop application through the first interface, and transmitting the system event to the system desktop application. Therefore, when the at least one program is executed, the first interface corresponding to the system event is called through the window management service, then the system desktop application is called remotely through the first interface, the system event is transmitted to the system desktop application, the system event is notified without depending on a broadcasting mode, the notification speed of the system event can be effectively improved, and the use experience of blocking caused to a user is avoided.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a component of' 8230; \8230;" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.