Message notification method, electronic device, storage medium and computer program product

Abstract

The invention relates to the technical field of terminals, and provides a message notification method, electronic equipment, a storage medium and a computer program product. In the method, different configuration information is configured in advance according to the type of an equipment event, and the configuration information comprises display positions of notification messages corresponding to the equipment event, display priorities corresponding to the display positions, notification forms and notification parameters corresponding to the notification forms. And then, after the electronic equipment receives the notification message, the configuration information corresponding to the equipment event included in the notification message can be obtained, and the notification message is displayed based on the configuration information corresponding to the equipment event included in the notification message. Thus, the notification messages corresponding to the equipment events are displayed in different forms based on different types of the equipment events to remind a user, the situation that the user neglects the notification messages can be reduced, and the user experience is improved.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a notification message method, electronic device, storage medium and computer program product. Background Art

[0002] In a smart home system, smart devices will generate various device events and send the device events to the server corresponding to the smart device. The server corresponding to the smart device will then generate a notification message A corresponding to the device event and send it to the user's mobile phone or other electronic devices.

[0003] After the electronic device receives notification message A, if the electronic device is in the screen-on state, notification message A will be displayed in the notification bar for a period of time, such as 30 seconds, to remind the user. If it is detected that the user clicks on notification message A at this time, the electronic device will open the application interface corresponding to notification message A, such as the smart device management application interface, to display the complete content of notification message A. If the user does not click on notification message A within the display time, notification message A will no longer be displayed after the display time ends. Subsequently, the user can pull down the notification bar to see various notification messages in the notification bar, including notification message A.

[0004] However, it is understandable that if there are many notification messages in the notification bar, the display mode of notification message A is basically the same as that of other notification messages, without being highlighted, and it is easy to be ignored. If notification message A notifies a more urgent device event, such as a door prying alarm notification message, a children's watch location alarm event, etc., if the user ignores the notification message of the device event, it may cause serious consequences. Summary of the invention

[0005] In order to solve the problem that notification messages are easily ignored, the embodiments of the present application provide a notification message method, an electronic device, a storage medium, and a computer program product, including:

[0006] In a first aspect, the present application provides a notification message method, which is applied to a first electronic device, comprising: receiving a first notification message, determining that the first notification message includes a first device event; displaying the first notification message with first display configuration information corresponding to the first device event; receiving a second notification message, determining that the second notification message includes a second device event, and the second device event is of a different type from the first device event; displaying the second notification message with second display configuration information corresponding to the second device event, wherein the second display configuration information is different from the first display configuration information.

[0007] Based on the above solution, different forms of display are performed on the notification messages corresponding to device events according to different types of device events to remind the user, which can reduce the situation of users ignoring notification messages and improve the user experience.

[0008] In some optional examples of the first aspect, the display configuration information includes at least one of the following: display location, display priority corresponding to each display location, notification form, and notification parameters corresponding to the notification form.

[0009] In some optional examples of the first aspect, the display locations include the lock screen interface, the home screen, the notification bar, the capsule, the negative first screen, the in-capsule notification bar, and the display interface of a second electronic device associated with the first electronic device.

[0010] In some optional examples of the first aspect, the second electronic device includes at least one of the following: a smart wearable device, a virtual reality device, an augmented reality device, a smart driving device.

[0011] In some optional examples of the first aspect, the notification forms include at least one of the following: text, ringtone, vibration.

[0012] In the embodiments of the present application, the reminder methods of notification messages are not limited to the original text. Adding random combinations of text, vibration, and ringtone can further reduce the situation of users ignoring notification messages and improve the user experience.

[0013] In some optional examples of the first aspect, corresponding to the notification form being text, the notification parameters include font size, color, and display duration; corresponding to the notification form being a card, the notification parameters include an icon, a title, a color, and a display duration; corresponding to the notification form being a ringtone, the notification parameters include volume and ringtone duration; corresponding to the notification form being vibration, the notification parameters include vibration frequency and vibration duration.

[0014] In some optional examples of the first aspect, the higher the display priority, the smaller the probability that the notification message is overwritten.

[0015] In some optional examples of the first aspect, the types of device events include at least one of the following: regular events, reminder events, security events, alarm events; among them, regular events include: door opening event, door closing event, door locking event, air conditioner closing event; reminder events include: laundry completion event, microwave heating completion event, kettle boiling completion event; security events include: sweeper failure event, lighting failure event; alarm events include: door prying alarm event, children's watch location alarm event, missed emergency call alarm event.

[0016] In some alternative examples of the first aspect, the display priority of regular events is lower than that of reminder events, the display priority of reminder events is lower than that of security events, and the display priority of security events is lower than that of alarm events.

[0017] In some alternative examples of the first aspect, corresponding to the first device event being an unanswered emergency call alarm event, a first notification message is displayed, including: displaying the first notification message in the form of a card, and the card includes a first-level jump component, and the first-level jump component is used to make a callback to the first device corresponding to the first device event.

[0018] In some alternative examples of the first aspect, the method further includes: detecting a first operation of the user on the first-level jump component, and displaying a callback interface, and the callback interface includes a second-level jump component, and the second-level jump component is used to locate the position of the first device corresponding to the first device event; detecting a second operation of the user on the second-level jump component, and displaying a positioning interface, and the positioning interface includes the current position or historical position of the first device.

[0019] In some alternative examples of the first aspect, the operating system of the first electronic device includes an event configuration table management module in the framework layer, and the method further includes: obtaining a first display configuration table corresponding to the first device event through the event configuration table management module.

[0020] For example, the event configuration table management module may request the device cloud to download / update the first display configuration table corresponding to the first device event.

[0021] In some alternative examples of the first aspect, the operating system of the first electronic device includes an event parsing and decision-making module in the framework layer, and the method further includes: reading the first display configuration table through the event parsing and decision-making module to determine the first display configuration information corresponding to the first device event.

[0022] For example, the notification event parsing and decision-making module can identify the event type of the first device event by reading the Iotlevel field in the event configuration table. The notification event parsing and decision-making module can also determine the display position and notification form of the notification message corresponding to the first device event by reading the touch field in the event configuration table. The notification event parsing and decision-making module can also determine the display style and display content of the card of the notification message corresponding to the first device event by reading fields such as cardBizIcon, cardTitle, cardSubTitle, cardBottomLink1Name+cardBottomLink1Url, cardBottomLink2Name+cardBottomLink2Url, and intentionLevel in the event configuration table. The notification event parsing and decision-making module can also determine the intention level by reading the ntentionLevel field in the event configuration table. And the notification event parsing and decision-making module can also determine the display duration of the notification message corresponding to the first device event by reading the cardCancellationStrategy field in the event configuration table.

[0023] In a second aspect, the present application provides an electronic device, including the method for notification messages mentioned in the first aspect or any one of the first aspect of the present application.

[0024] In a third aspect, the present application provides a readable storage medium, on which instructions are stored, and when the instructions are executed on an electronic device, the electronic device is caused to execute the method for notification messages mentioned in the first aspect or any one of the first aspect of the present application.

[0025] In a fourth aspect, an embodiment of the present application provides a computer program product, including: a non-volatile computer-readable storage medium, and the non-volatile computer-readable storage medium contains computer program code for executing the method for notification messages mentioned in the first aspect or any one of the first aspect of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 According to some examples of the present application, a block diagram of a notification system is shown;

[0027] Figure 2 According to some examples of the present application, a first interface switching schematic diagram is shown;

[0028] Figure 3 According to some examples of the present application, a second interface switching schematic diagram is shown;

[0029] Figures 4A - 4D According to some examples of the present application, a schematic diagram of notification messages at different display positions is shown;

[0030] Figure 5A According to some examples of the present application, a flowchart of a method for a notification message is shown;

[0031] Figure 5B According to some examples of the present application, a third interface switching schematic diagram is shown;

[0032] Figure 5C According to some examples of the present application, a partial code for configuring the configuration information of an unanswered emergency call warning event is shown;

[0033] Figure 6 According to some examples of the present application, a schematic diagram of the system architecture of a notification message is shown;

[0034] Figure 7 According to some examples of the present application, an interaction flowchart of a notification message is shown;

[0035] Figure 8 According to some examples of the present application, a notification form of events of different children's watches at different display positions is shown;

[0036] Figure 9 According to some examples of the present application, a hardware structure of an electronic device is shown. Detailed implementation manners

[0037] Illustrative embodiments of the present application include, but are not limited to, a method for a notification message, an electronic device, a storage medium, and a computer program product.

[0038] It can be understood that the method for a notification message mentioned in the embodiments of the present application can be used in an electronic device. Among them, the electronic device can also be called a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The electronic device can be a mobile phone, a wearable device, a tablet computer (Pad), a virtual reality (VR) electronic device, an augmented reality (AR) electronic device, a wireless terminal in intelligent driving, and so on. For the convenience of description, the following takes the electronic device as the mobile phone 100 as an example for illustration.

[0039] Embodiments of the present application can be applied to smart home systems, smart industrial systems, smart office systems, etc. For example, the smart devices in a smart home system can include multiple smart devices, such as door locks, washing machines, children's watches, floor sweepers, air conditioners, lighting fixtures, curtains, microwave ovens, refrigerators, ovens, TVs, fans, etc. The smart devices in a smart industrial system can include robotic arms, surveillance cameras, temperature sensors, laser sensors, three-machine controllers, etc. The smart devices in a smart office system can include mobile phones, computers, surveillance cameras, printers, web servers, etc. For the sake of convenience of description, the following takes a smart home system as an example for illustration.

[0040] The following introduces the notification process of the notification messages of smart devices in the smart home system.

[0041] Figure 1 A block diagram of a notification system is shown, as Figure 1 shown, the notification system can include a mobile phone 100, smart devices 110 (such as a door lock 111 and a washing machine 112), and servers 120 corresponding to the smart devices (such as a door lock server 121 and a washing machine server 122).

[0042] As mentioned above, smart devices will generate various device events and send the device events to the servers corresponding to the smart devices. Furthermore, the servers corresponding to the smart devices will generate notification messages corresponding to the device events and send them to the mobile phone 100. Or, based on the fact that a Bluetooth connection or the like has been established between the smart device 110 and the mobile phone 100 or they are within the same local area network, the smart device 110 can also directly send the notification message to the mobile phone 100. After the mobile phone 100 receives the notification message, if the mobile phone 100 is in the screen-on state, the notification message will be displayed in the notification bar for a period of time, such as 30 s, to remind the user. If the mobile phone 100 is in the locked screen state, the notification message will be continuously displayed on the locked screen interface to remind the user.

[0043] The following takes the smart device 110 sending the notification message to the server 120 as an example for illustration. For example, when the door lock 111 is pried, the door lock 111 can send a door-prying alarm event to the door lock server 121. The door lock server 121 can receive the door-prying alarm event and generate a door-prying alarm notification message based on the door-prying alarm event and send it to the mobile phone 100. After the mobile phone 100 receives the door-prying alarm notification message, the door-prying alarm notification message will be displayed in the notification bar. For another example, after the washing machine 112 finishes washing, the washing machine 112 can send a washing completion event to the washing machine server 122. The washing server 122 can receive the washing completion event and generate a washing completion reminder message based on the washing completion event and send it to the mobile phone 100. After the mobile phone 100 receives the washing completion reminder message, the washing completion reminder message will be displayed in the notification bar.

[0044] Similarly, the smart device 110 may also include a children's watch (not shown), a floor sweeper (not shown), etc. The mobile phone 100 may also receive a children's watch position warning event when the children's watch is in an abnormal position, a floor sweeper failure event when the wheels of the floor sweeper are stuck or the battery has a low power, etc. The embodiments of the present application do not make specific limitations.

[0045] For example, after a new device is connected to Router A, Router A will generate an access event and send it to the server corresponding to Router A. Then, the server corresponding to Router A will generate a notification message "New device connected" corresponding to the access event and send it to the mobile phone 100.

[0046] In some specific implementations, after the mobile phone 100 receives the notification message, if the mobile phone 100 is in the screen-on state, the notification message will be displayed in the notification bar for a period of time, such as 30 s, to remind the user. If the mobile phone 100 detects that the user clicks on the notification message, the mobile phone 100 will open the application program interface corresponding to the notification message, such as the smart device management application program interface, and display the complete content of the notification message. If the mobile phone 100 does not detect the notification message within 30 s, the notification message "New device connected" will no longer be displayed. Subsequently, the user can view the notification message by pulling down the notification bar.

[0047] For example, after the mobile phone 100 receives the notification message, if the mobile phone 100 is in the screen-on state, it can display the notification message "New device connected" in the notification bar of the main interface 210 as shown in (a) of Figure 2 for 30 s. When the mobile phone 100 detects that the user clicks on the notification message 211 in the main interface 210 as shown in (a) of Figure 2 , it can switch from the main interface 210 to the user interface 220 as shown in (b) of Figure 2 .

[0048] Next, when the mobile phone 100 detects the user's message viewing operation, for example, when the user clicks on the message viewing component 221 in the user interface 220, the mobile phone 100 can respond to the user's message viewing operation and switch from the user interface 220 to the message display interface 230 as shown in (c) of Figure 2 to display the notification message, such as "New device connected to Router A", "The kettle is on standby, it is recommended to turn it off", "New device connected to Router B", etc.

[0049] For example, when the mobile phone 100 detects that the user clicks on the message viewing component of a certain device in the device message display interface 230 (for example, Figure 2 the Router A message viewing component 231, the kettle message viewing component 232, the Router B message viewing component 233 in (c) of Figure 2The sub-device message display interface 240 shown in (d) therein displays device notification messages, such as "New device a is accessed at xx moment, new device b is accessed at yy moment, new device c is accessed at zz moment", etc.

[0050] When the mobile phone 100 does not detect that the user clicks Figure 2 the notification message 211 in the main interface 210 shown in (a) therein, the notification message 211 will no longer be displayed after 30s. Subsequently, the user can pull down the notification bar to display various notification messages from the Figure 2 notification bar pull-down interface 250 shown in (e) therein, including the notification message "New device accessed".

[0051] In some other specific implementations, after the mobile phone 100 receives the notification message "New device accessed", if the mobile phone 100 is in the locked screen state, the notification message will continuously be displayed on the locked screen interface 310 shown in (a) therein. It can be understood that the mobile phone 100 not only receives and displays the notification messages of the smart devices in the smart home system, but also displays the notification messages of various installed application programs. And, when receiving a new notification message "There is a new text message" in the locked screen state, as shown in Figure 3 (b) therein, the new notification message "There is a new text message" will overwrite the old notification message "New device accessed". Figure 3

[0052] It can be understood that in the screen-on state, if there are many notification messages in the notification bar and the display methods of all notification messages are basically the same without prominent display, it is easy for the user to ignore the notification messages. And, in the locked screen state, the new notification message will overwrite the old notification message, making it easy for the user to ignore the old notification message. If the user ignores the notification messages of relatively urgent device events, such as the notification message of forced door opening warning, the location warning event of the children's watch, etc., serious consequences may occur.

[0053] To solve the above problems, the embodiment of the present application provides a message notification method. In this method, different configuration information is pre-configured according to the type of device event, where the configuration information includes the display position of the notification message corresponding to the device event, the display priority corresponding to each display position, the notification form, and the notification parameters corresponding to the notification form. Then, after the electronic device receives the notification message, it can obtain the configuration information corresponding to the device event included in the notification message and display the notification message based on the configuration information corresponding to the device event included in the notification message. In this way, different forms of display are performed on the notification messages corresponding to the device events based on different types of device events to remind the user, which can reduce the situation of the user ignoring the notification messages and improve the user experience.

[0054] It can be understood that the notification form includes at least one of the following: text, ringing, and vibration. When the notification form is text, the notification parameters include font size, color, and display duration; when the notification form is a card, the notification parameters include an icon, a title, color, and display duration; when the notification form is ringing, the notification parameters include volume and ringing duration; when the notification form is vibration, the notification parameters include vibration frequency and vibration duration.

[0055] It can be understood that the higher the display priority, the lower the probability that the notification message will be overwritten.

[0056] It can be understood that the display location can refer to the location where the notification message is displayed on the electronic device or the location where it is displayed on other devices associated with the electronic device. For example, the lock screen interface, the home screen, the notification bar, the capsule, the negative first screen, the notification / dynamic notification bar, the capsule, the in-capsule notification bar, the display interface of the smart wearable device associated with the mobile phone 100, the display interface of the virtual reality electronic device associated with the mobile phone 100, the display interface of the augmented reality electronic device associated with the mobile phone 100, the display interface of the intelligent driving associated with the mobile phone 100, and so on.

[0057] In some optional examples, the user or the smart device manufacturer can pre-configure the configuration information of the missed emergency call warning event. This configuration information can be configured on the cloud side or on the electronic device. The electronic device can receive the configuration information of the missed emergency call warning event sent by the cloud side, or read the configuration information of the missed emergency call warning event stored in itself, and determine the display location of the notification message corresponding to the configuration information of the missed emergency call warning event, the display priority corresponding to each display location, the notification form, and the notification parameters corresponding to the notification form.

[0058] Specifically, the type of the missed emergency call event can be pre-configured as a warning event, and the display locations in the configuration information of the missed emergency call warning event include the lock screen interface of the mobile phone 100, the home screen of the mobile phone 100, the message notification bar of the mobile phone 100, and the display interface of the smart watch 200 associated with the mobile phone 100. The display priority in the configuration information of the missed emergency call warning event is the first-level priority, the notification form is text + vibration, the notification parameters corresponding to the text include a font size of No. 5, a color of red, and a display duration of 1800 s, and the notification parameters corresponding to the vibration include a vibration frequency of 100 Hz and a vibration duration of 1800 s.

[0059] Therefore, when the mobile phone 100 receives the missed call notification message from the children's watch, it can display the red notification message 411 "Missed Emergency Call" on the lock screen interface 410 of the mobile phone 100 as shown in Figure 4A shown, and in Figure 4BThe main interface 420 of the mobile phone 100 as shown displays a red notification message card 421 "Missed Emergency Call", as Figure 4C shown, the notification bar 430 of the mobile phone 100 displays a red notification message 431 "Missed Emergency Call", and as Figure 4D shown, the main interface 440 of the smartwatch 200 associated with the mobile phone 100 displays a red notification message 441 "Missed Emergency Call". At the same time, the mobile phone 100 and the smartwatch associated with the mobile phone 100 vibrate to remind the user to view the notification message.

[0060] The method for notification messages mentioned in the embodiments of the present application will be introduced below. Figure 5A The flowchart of a method for notification messages is shown. This method for notification messages can be executed by a first electronic device.

[0061] As Figure 5A shown, this method for notification messages may include:

[0062] 501: Obtain a first notification message corresponding to a first device event, and determine first configuration information of the first notification message from pre-configured event configuration information.

[0063] It can be understood that the user or the smart device manufacturer can pre-configure the configuration information for each event. This configuration information can be configured on the cloud side or on the electronic device. And each device event can be assigned an event identifier, which corresponds one-to-one with the configuration information of the device event.

[0064] In some optional instances, when the configuration information is configured on the cloud side, the electronic device can obtain the first notification message corresponding to the first device event from the cloud side. When the configuration information is configured on the electronic device, the electronic device can read the first notification message corresponding to the first device event stored in itself.

[0065] It can be understood that the first notification message corresponding to the first device event can be uploaded by the smart device to the cloud side and then sent by the cloud side to the electronic device. For example, user A wearing a children's watch makes an emergency call to user B's mobile phone, but user B's mobile phone fails to answer the emergency call. The children's watch can send an event of missed emergency call warning to the cloud side. The cloud side may generate a first notification message corresponding to the event of missed emergency call warning and send it to user B's mobile phone.

[0066] It can be understood that the first notification message corresponding to the first device event can also be directly sent by the first device to the electronic device. For example, a Bluetooth connection or the like has been established between the user A of the children's watch and the mobile phone of user B, or they are in the same local area network. User A wearing the children's watch makes an emergency call to the mobile phone of user B, but the emergency call on user B's mobile phone is not answered. The children's watch can directly generate the first notification message corresponding to the unanswered emergency call warning event and send it to the mobile phone of user B.

[0067] It can be understood that after obtaining the first notification message corresponding to the first device event, the first configuration information such as the display position of the first notification message, the display priority corresponding to each display position, the notification form, and the notification parameters corresponding to the notification form can be determined from the pre-configured event configuration information based on the event identifier of the first device event.

[0068] For example, based on the event identifier "123" of the unanswered emergency call warning event, it can be determined that the configuration information of the unanswered emergency call warning event includes displaying a notification message card on the main interface of the electronic device. The display color of the notification message card is red, the display duration is 1800s, the icon in the notification message card is "Smart Home Service", the main title is "Unanswered Emergency Call", the subtitle is "User A 07:58", the first-level jump is "Callback", the second-level jump is "Location", and the notification form is text + vibration.

[0069] 502: Display the first notification message based on the first configuration information.

[0070] It can be understood that after determining the first configuration information of the first notification message, based on the display position in the first configuration information, at the corresponding display position (such as the lock screen interface, main interface, notification bar, capsule, negative first screen, notification / dynamic notification bar, capsule, in-capsule notification bar, display interface of the smart wearable device associated with the mobile phone, display interface of the virtual reality electronic device associated with the mobile phone 100, display interface of the augmented reality electronic device associated with the mobile phone, display interface of the smart driving electronic device associated with the mobile phone 100), the first notification message can be displayed with the display priority corresponding to each display position, the notification form, and the notification parameters corresponding to the notification form in the first configuration information.

[0071] For example, as Figure 5B shown in (a) of, a red notification message card can be displayed on the main interface 510 of the mobile phone 100. The icon in the notification message card is "Smart Home Service", the main title is "Unanswered Emergency Call", the subtitle is "User A 07:58", the first-level jump is "Callback", and at the same time, the mobile phone 100 can vibrate to remind user B to view the notification message corresponding to the unanswered emergency call warning event.

[0072] It can be understood that by presenting the notification message corresponding to the missed emergency call warning event in the form of a notification message card, the type of the missed emergency call warning event can be prominently displayed. In addition, when the mobile phone 100 detects a trigger operation on the jump icon 511 corresponding to the first-level jump, it can switch from the main interface 510 to the callback interface 520 shown in (b) of Figure 5B to make a callback call to the children's watch of user A.

[0073] Continuing as shown in Figure 5B , the callback interface 520 includes a second-level jump "Location". When the mobile phone 100 detects a trigger operation on the floating ball 521 of the second-level jump, it can switch from the callback interface 520 to the location interface 530 shown in (c) of Figure 5B to determine the current location or historical location of user A based on the real-time location of user A's child (for example, located at location A 10 minutes ago).

[0074] Figure 5C Exemplarily, a part of the code for configuring the configuration information of the missed emergency call warning event is shown. Figure 5C The code in Figure 5C defines the first-level jump and the second-level jump (the second floating ball), etc. For specific content, reference can be made to the annotations of the code in

[0075] 503: Obtain the second notification message corresponding to the second device event, and determine the second configuration information of the second notification message from the pre-configured event configuration table.

[0076] It can be understood that the second device event and the first device event can be different events of the same intelligent device, or different events of different intelligent devices.

[0077] In some optional instances, the method of obtaining the second notification message corresponding to the second device event and the method of determining the second configuration information of the second notification message from the pre-configured event configuration table can refer to step 501. To avoid repetition, it will not be elaborated here.

[0078] 504: Display the second notification message based on the second configuration information, where the first device event and the second device event are different events, and the first configuration information and the second configuration information are different.

[0079] In some optional instances, the method of displaying the second notification message based on the second configuration information can refer to step 502. To avoid repetition, it will not be elaborated here.

[0080] In the embodiments of the present application, different forms of display are performed on the notification messages corresponding to device events based on different types of device events to remind users, which can reduce the situation where users ignore notification messages and improve the user experience. Moreover, without the user entering the application interface corresponding to the notification message to view the notification message, the user experience can be further improved. In addition, the reminder method of the notification message is not limited to the original text, and adding a random combination of text, vibration, and ringing can further reduce the situation where users ignore notification messages and improve the user experience.

[0081] The system architecture of the notification message mentioned in the embodiments of the present application will be introduced below. Taking the example that the smart device side 610 sends a notification message to the cloud side 620, it should be understood that the notification message can also be directly sent from the smart device side 610 to the end side 630.

[0082] Figure 6 A schematic diagram of the system architecture of a notification message is shown. As Figure 6 shown, the system architecture 600 of the notification message can include a smart device side 610, a cloud side 620, and an end side 630.

[0083] It can be understood that the system of the notification message can also include a developer platform (not shown), and the developer platform can be the server of the smart device side 610 or the server of the cloud side 620.

[0084] In some optional instances, Figure 6 Taking the smart device 610 as a children's watch specifically, the cloud side 620 includes a device cloud and a push cloud, and the end side 630 is a mobile phone as an example for illustration.

[0085] It can be understood that when a device event occurs on the smart device side 610, a device event can be sent to the cloud side 620. Specifically, the children's watch can send a device event to the device cloud in the cloud side 620.

[0086] In some optional instances, when an unanswered emergency call warning event occurs on the children's watch, for example, the user wearing the children's watch dials an emergency call to the mobile phone held by the consumer, but the emergency call is not answered on the mobile phone held by the consumer, the children's watch can send an unanswered emergency call warning event to the device cloud.

[0087] In some specific implementations, the device cloud in the cloud side 620 stores event notification templates.

[0088] The device cloud receives the events defined by the intelligent device manufacturer by the operation and maintenance personnel, and refreshes the content of the event notification template. Moreover, after the device cloud receives the request to download / update the event notification template file sent by the notification sharing module on the end side 630, it can return an event configuration table (i.e., the event notification template list file in the following text) to the notification sharing module. This event notification template list file may include the configuration information of the notification messages corresponding to the device events.

[0089] It can be understood that after the device cloud receives a device event, it can determine whether the device event needs to be notified according to whether the display position in the configuration information of the notification message corresponding to the device event is empty. When the display position in the configuration information of the notification message corresponding to the device event is non-empty, it can be determined that the device event needs to be notified, and then the device event is pushed to the push cloud, so as to use the push cloud to push the notification message corresponding to the device event to the end side 630.

[0090] In some specific implementations, the end side 630 may include a cloud configuration download module, an event receiving module, a notification sharing module, a card management module, and a card issuing service module.

[0091] In some optional instances, the cloud configuration download module can store the event configuration table, application list, and card resources downloaded from the device cloud. The cloud configuration download module also includes an HTTPS communication protocol module, which is used to implement the communication between the end side 630 and the device cloud.

[0092] In some optional instances, the event receiving module may include an event distribution and processing module and a push software development kit (push SDK) module.

[0093] Among them, the push SDK module can receive the notification messages corresponding to the device events sent by the push cloud. When the event distribution and processing module determines that the device event needs to be notified, it can perform distribution processing on the device event and send the device event to the notification sharing module.

[0094] In some optional instances, the notification sharing module may include an event configuration table management module, a notification event parsing and decision-making module, and a card issuing / updating / canceling module.

[0095] Among them, the event configuration table management module can request to download / update the event notification template file from the device cloud, and can receive the event notification template list file returned by the device cloud.

[0096] The notification event parsing and decision-making module can identify the event type of a device event by reading the Iotlevel field in the event configuration table. The notification event parsing and decision-making module can also determine the display position and notification form of the notification message corresponding to the device event by reading the touch field in the event configuration table. The notification event parsing and decision-making module can also determine the display style and display content of the card of the notification message corresponding to the device event by reading the cardBizIcon, cardTitle, cardSubTitle, cardBottomLink1Name+cardBottomLink1Url, cardBottomLink2Name+cardBottomLink2Url, intentionLevel and other fields in the event configuration table. The notification event parsing and decision-making module can also determine the intention level by reading the ntentionLevel field in the event configuration table. And the notification event parsing and decision-making module can also determine the display duration of the notification message corresponding to the device event by reading the cardCancellationStrategy field in the event configuration table.

[0097] For example, identify the event type of the missed emergency call warning event as "warning". Determine the display position of the notification message corresponding to the missed emergency call warning event as "home screen, notification bar, lock screen, and smart wearable device associated with the mobile phone", and determine the notification form of the missed emergency call warning event as "text + vibration". Determine the display color of the notification message corresponding to the device event as red, and determine the intention level as "34", where the higher the intention level, the higher the display priority of the card of the notification message corresponding to the device event and the lower the probability of being overwritten. Determine the icon in the notification message card as "smart home service", the main title as "missed emergency call", the subtitle as "User A 07:58", the first-level jump as "callback", and the second-level jump as "location". Read the display duration of the notification message corresponding to the missed emergency call warning event as 1800 seconds.

[0098] In some alternative examples, the card issuing / updating / canceling module can send a notification card drawing instruction to the card issuing service module.

[0099] In some alternative examples, the card issuing service module can include a card issuing, updating, and canceling request management module. Among them, the card issuing, updating, and canceling request management module can forward the card drawing instruction sent by the card issuing / updating / canceling module to the card management module after receiving it. The card issuing, updating, and canceling request management module can also forward the card cancellation request to the card management module after receiving the card cancellation request sent by the card management module.

[0100] In some alternative examples, the card management module may include a card template management module, a card resource management module, and a card instantiation management module.

[0101] Among them, the card template management module can provide a card template to the card instantiation management module. The card resource management module can draw a card of a notification message corresponding to a device event based on a card drawing instruction and send it to the card instantiation management module. Furthermore, the card instantiation management module can update the card of the notification message corresponding to the device event with the card template provided by the card template management module and send it to the card issuing service module.

[0102] In some alternative examples, the card issuing service module may further include a card broadcast data receiving and distributing module, and a card notification and data receiving application programming interface (API) encapsulation.

[0103] Among them, the card broadcast data receiving and distributing module can obtain the card of the notification message corresponding to the device event drawn by the card management module and distribute it to the card notification and data receiving API encapsulation based on the type of the card.

[0104] When the type of the card is the type of the card displayed in the notification center, the screen-off state, the capsule, and the global pop-up window, through the global reach in the card notification and data receiving API encapsulation, and the service interaction management framework, the card is sent to the message reach (notification center, screen-off state, capsule, global pop-up window) for display.

[0105] When the type of the card is a card, through the intelligent engine (such as ) in the card notification and data receiving interface API encapsulation, the card is sent with a suggestion to display the card.

[0106] It can be understood that the global reach and the intelligent engine here can be collectively referred to as the service display framework, the human-computer interaction framework, or the service display framework.

[0107] In some alternative examples, the event notification template may also be stored on the terminal side 630. The intelligent device side 610 can directly send a notification message to the terminal side 630, and the terminal side 630 displays the notification message according to the above method. To avoid repetition, it will not be elaborated here.

[0108] The method of the notification message mentioned in the embodiments of the present application will be introduced in detail below. As Figure 7Shows a schematic diagram of the interaction process of a notification message. Among them, the intelligent device side includes a developer platform and an intelligent device (such as a children's watch). The terminal side 630 may include a smart space application (APP), an event receiving module, a notification sharing module, a card management module, and a service display framework. The cloud side 620 may include a push cloud and a device cloud.

[0109] As Figure 7 shown, the method of this notification message may include:

[0110] 701: The developer platform receives the event content of the intelligent device configured by the developer through the platform.

[0111] It can be understood that developers of intelligent device manufacturers can configure the event content of each intelligent device in the smart home system through the developer platform. For example, developers can configure event content 1 of the door lock "abnormal opening of the door lock", or configure event content 2 of the door lock "normal closing of the door lock". Developers can configure event content 1 of the washing machine "washing completed", or configure event content 2 of the washing machine "washing aborted". Developers can configure event content 1 of the children's watch "the children's watch is in a safe position", or configure event content 2 of the children's watch "the children's watch is in a dangerous position", and can also configure event content 3 of the children's watch "unanswered emergency call", etc. The above are some examples listed in the embodiments of this application, which do not represent all examples. Developers can also configure other event content of other intelligent devices, and the embodiments of this application do not make specific limitations.

[0112] It can be understood that developers can register products through the developer platform. For example, developers can register children's watches, and then the developer platform can assign a product identifier (pro id) to the product. The product identifier can represent the category to which the product belongs. For example, the same product identifier can be assigned to all models of children's watches.

[0113] 702: The developer platform synchronizes the event definition information of the intelligent device with the device cloud.

[0114] It can be understood that after the developer platform receives the event content of the intelligent device configured by the developer, the event content can be defined, and an event identifier (event id) can be assigned to the event content of the intelligent device. For example, the event content 1 of the washing machine, "washing completed", can be defined as a washing completion event, the event content 3 of the children's watch, "emergency call not answered", can be defined as an emergency call not answered warning event, and the event identifier "000" can be assigned to the washing completion event, and the event identifier "123" can be assigned to the emergency call not answered warning event. Moreover, after defining the event content of the intelligent device and assigning the event identifier to the event content of the intelligent device, the defined event content and the event identifier corresponding to the event content of the intelligent device can be sent to the device cloud for synchronization, that is, the definition and event identifier of the device event of the intelligent device are uploaded to the device cloud.

[0115] 703: The operation and maintenance personnel refresh the content of the event notification template according to the events defined by the intelligent device manufacturer.

[0116] It can be understood that the operation and maintenance personnel of the intelligent device manufacturer can refresh the content of the event notification template according to the events defined by the intelligent device manufacturer and send it to the device cloud. Table 1 below shows the content of an event notification template.

[0117] Table 1

[0118]

[0119]

[0120]

[0121] Among them, regular events can include: door open event, door close event, door lock event, air conditioner off event, etc., reminder events can include: washing completed event, microwave heating completed event, kettle boiling water completed event; security events can include: floor sweeper failure event, lighting failure event; warning events can include: door pry warning event, children's watch location warning event, emergency call not answered warning event.

[0122] It can be understood that the operation and maintenance personnel of the intelligent device manufacturer can configure different event notification template files for different intelligent devices based on the content of the event notification template, where the event notification template file of each intelligent device can correspond one-to-one with the device identifier.

[0123] In the embodiments of the present application, through the generalized event notification template, it is possible to dynamically expand the global reach of any device event to the user on the terminal side.

[0124] 704: Consumers add and bind intelligent devices to the smart space application.

[0125] It can be understood that the consumer can bring the smart device close to the electronic device, so that the smart space application in the electronic device can detect the smart device, realizing the addition and binding of the smart device.

[0126] In some embodiments, the consumer is specifically a user on the terminal side. It can be understood that the developer, the operation and maintenance personnel, and the consumer can be the same user or different users.

[0127] 705: The smart space application discovers and binds the smart device.

[0128] It can be understood that after detecting the smart device, the smart space application can send a registration notice to the smart device. For example, when the consumer brings the children's watch close to the mobile phone, the smart space application in the mobile phone can detect the children's watch and send a registration notice to the children's watch. For example, the children's watch can be discovered and bound based on Bluetooth or local area network, etc.

[0129] 706: The smart device registers the smart device with the device cloud.

[0130] It can be understood that after receiving the registration notice sent by the smart space application, the smart device can send a request to register the smart device to the device cloud. For example, the children's watch can send a request to register the smart device to the device cloud.

[0131] 707: The device cloud assigns a device identifier to the smart device.

[0132] It can be understood that after receiving the request to register the smart device sent by the smart device, the device cloud can assign a device identifier (dev id) to the smart device. For example, after receiving the request to register the smart device sent by the children's watch, the device cloud can assign a device identifier to the children's watch to indicate successful registration.

[0133] 708: The smart device returns the registration result to the smart space application.

[0134] It can be understood that after the smart device receives the device identifier (dev id) assigned by the device cloud, it can return the registration result to the smart space application, that is, return the device identifier (dev id) to the smart space application. The smart space application can display the device identifier and name of the smart device in the device list.

[0135] It can be understood that steps 704 - 708 can be executed before steps 701 - 703, steps 704 - 708 can also be executed after steps 701 - 703, and steps 704 - 708 can also be executed synchronously with steps 701 - 703 plus steps 704 - 708.

[0136] 709: The notification sharing module requests the device cloud to download / update the event notification template file.

[0137] It can be understood that after the smart space application receives the device identifier (dev id), it can trigger the notification sharing module to request the device cloud to download / update the event notification template file.

[0138] 710: The device cloud returns the event notification template list file to the notification sharing module.

[0139] It can be understood that after the device cloud receives the request to download / update the event notification template file sent by the notification sharing template, it can return the event notification template list file to the notification sharing module. The event notification template list file can include the configuration information of each smart device in the smart home system (i.e., the event notification template list file), or it can include the configuration information of the device events corresponding to the device identifier (i.e., the event notification template list file). The embodiments of the present application do not make specific limitations. Table 2 shows some of the configuration information of the unconnected emergency call warning event returned by the device cloud to the notification sharing module.

[0140] Table 2

[0141]

[0142] 711: The event receiving module monitors the device events in the push cloud.

[0143] It can be understood that the event receiving module monitors the device events of the smart devices corresponding to the client identifier in the push cloud based on the client identifier (client id). Among them, the client identifier can be the unique identity identifier assigned to the smart device by the smart device manufacturer when producing the smart device. The client identifier (client id) can be associated with the device identifier (dev id). For example, the client identifier (client id) can correspond one-to-one with the device identifier (dev id), or the client identifier (client id) can be the same as the device identifier (dev id).

[0144] 712: The smart device sends the device event to the device cloud.

[0145] It can be understood that when the smart device generates a device event, it can send the device event to the device cloud. In some optional instances, when the smart device sends the device event to the device cloud, it can also send information such as the event identifier (event id) assigned by the developer platform for the event content of the smart device, the device identifier (devid) assigned by the device cloud for the smart device, the current account identifier (user id) of the smart device, the product identifier (prdid) assigned by the developer platform for the smart device, and the event content.

[0146] In some alternative examples, when an unanswered emergency call alert event occurs on a children's smartwatch, for example, the user wearing the children's smartwatch dials an emergency call to the mobile phone held by the consumer, but the emergency call on the consumer's mobile phone is not answered, the children's smartwatch can send the unanswered emergency call alert event to the device cloud. Specifically, the specific form of the unanswered emergency call alert event can be "event id, user id, dev id, pro id, content" "The children's smartwatch of [nickname] called [mobile phone number] [User B] at [time]".

[0147] 713: The device cloud determines whether the device event needs to be notified according to the configuration information of the device event.

[0148] It can be understood that after receiving the device event, the device cloud can determine whether the device event needs to be notified according to whether the display position in the configuration information of the notification message corresponding to the device event (that is, the event notification template list file mentioned above) is empty. When the display position in the configuration information of the notification message corresponding to the device event is non-empty, it can be determined that the device event needs to be notified, and then the device event is pushed to the push cloud. When the display position in the configuration information of the notification message corresponding to the device event is empty, it can be determined that the device event does not need to be notified, and then the process ends.

[0149] 714: The device cloud pushes the notification message corresponding to the device event to the push cloud.

[0150] It can be understood that when the device determines that the device event needs to be notified, it can push the notification message corresponding to the device event to the push cloud, so as to use the push cloud to push the notification message corresponding to the device event to the end side (that is, the electronic device held by the consumer).

[0151] 716: The event receiving module sends a successful receipt message for the notification message corresponding to the device event to the push cloud.

[0152] It can be understood that when the event receiving module monitors the device events of the smart devices corresponding to the client identifiers in the push cloud based on the client identifier (client id), and monitors the device event, and receives the notification message corresponding to the device event sent by the push cloud, it can send a successful receipt message for the notification message corresponding to the device event to the push cloud.

[0153] 716: The event receiving module performs device event distribution processing.

[0154] It can be understood that when it is determined that the device event needs to be notified, the event receiving module can perform distribution processing on the device event and send the device event to the notification sharing module. When it is determined that the device event does not need to be notified, the process can end.

[0155] 717: The event receiving module sends the notification message corresponding to the device event to the notification sharing module for notification template matching.

[0156] It can be understood that the event receiving module can send the notification message corresponding to the device event to the notification sharing module for notification template matching.

[0157] 718: The notification sharing module identifies the event type of the device event.

[0158] It can be understood that the notification sharing module can identify the event type of the device event by reading the Iotlevel field from the event notification template list file returned from the device cloud to the notification sharing module. For example, the event type of the missed emergency call warning event is identified as "warning".

[0159] 719: The notification sharing module determines the display position and notification form of the notification message corresponding to the device event.

[0160] It can be understood that the notification sharing module can determine the display position and notification form of the notification message corresponding to the device event by reading the touch field from the event notification template list file returned from the device cloud to the notification sharing module. For example, it is determined that the display position of the notification message corresponding to the missed emergency call warning event is "home screen, notification bar, lock screen, smart wearable device associated with the mobile phone", and the notification form of the missed emergency call warning event is determined as "text + vibration".

[0161] In some alternative examples, the notification messages corresponding to the device events can all be displayed in the form of cards at each display position. It can be understood that the notification messages corresponding to the device events can also be displayed in other forms at each display position. To avoid repetition, the following description is given with the notification messages corresponding to the device events all being displayed in the form of cards at each display position.

[0162] 720: The notification sharing module reads the display style and display content of the card of the notification message corresponding to the device event.

[0163] It can be understood that the notification sharing module can determine the display style and display content of the card of the notification message corresponding to the device event from the event notification template list file returned from the device cloud by reading fields such as IotLevel, cardBizIcon, cardTitle, cardSubTitle, cardBottomLink1Name+cardBottomLink1Url, cardBottomLink2Name+cardBottomLink2Url, and intentionLevel. For example, when the event type corresponding to the device event is obtained as "alarm" by reading the IotLevel field, it can be determined that the display color of the notification message corresponding to the device event is red. By reading the fields of cardBizIcon, cardTitle, cardSubTitle, cardBottomLink1Name+cardBottomLink1Url, and cardBottomLink2Name+cardBottomLink2Url, it can be determined that the icon in the notification message card is "Smart Home Service", the main title is "Unanswered Emergency Call", the subtitle is "User A 07:58", the first-level jump is "Callback", and the second-level jump is "Location". By reading the intentionLevel field, it can be determined that the intention level is "34", where the higher the intention level, the higher the display priority of the card of the notification message corresponding to the device event.

[0164] 721: The notification sharing module confirms the display duration of the notification message corresponding to the device event.

[0165] It can be understood that the notification sharing module can determine the display duration of the notification message corresponding to the device event from the event notification template list file returned from the device cloud by reading the cardCancellationStrategy field. For example, the display duration of the notification message corresponding to the unanswered emergency call alarm event is read as 1800 seconds.

[0166] 722: The notification sharing module sends a notification card drawing instruction to the card management module.

[0167] It can be understood that after the notification sharing module identifies the event type of the device event, determines the display position and notification form of the notification message corresponding to the device event, reads the display style and display content of the card for displaying the notification message corresponding to the device event, and confirms the display duration of the notification message corresponding to the device event, it can send a card drawing instruction to the card management module to instruct the card management module to draw the card of the notification message corresponding to the device event.

[0168] It can be understood that the above steps 718-721 can also be executed synchronously, and the embodiments of the present application do not limit the execution order of steps 718-721.

[0169] In some embodiments, the cloud side can also directly identify the event type, the display position, the notification form, and the display duration of the notification message corresponding to the device event, etc., and send them to the terminal side. The terminal side can instruct the card management module to draw the card of the notification message corresponding to the device event according to the event type, the display position, the notification form, and the display duration of the notification message corresponding to the device event.

[0170] 723: The card management module draws a card based on the configuration policy and the event content.

[0171] It can be understood that after receiving the card drawing instruction sent by the notification sharing module, the card management module can execute the card drawing instruction and draw the card of the notification message corresponding to the device event based on the event type of the device event, the display position and the notification form of the notification message corresponding to the device event, and the display style and display content of the card of the notification message corresponding to the device event.

[0172] Such as Figure 8 shows the notification form of an event of different children's watches at different display positions.

[0173] Such as Figure 8 As shown, when the child wearing the children's watch arrives at location A or at school, an event of the children's watch arriving at the fence can be generated, and the notification message corresponding to the event of the children's watch arriving at the fence is sent to the screen-off interface, the capsule, the in-capsule notification bar, the notification / dynamic notification bar, the YOYO card, and the main interface of the smart watch worn by the parent for display. Among them, the display color of the notification message can be green.

[0174] When the child wearing the children's watch leaves location A or leaves school, an event of the children's watch leaving the fence can be generated, and the notification message corresponding to the event of the children's watch leaving the fence is sent to the screen-off interface, the capsule, the in-capsule notification bar, the notification / dynamic notification bar, the YOYO card, and the main interface of the smart watch worn by the parent for display. Among them, the display color of the notification message can be blue.

[0175] When the child wearing the children's watch does not arrive at location A or does not arrive at school, an event of the children's watch not arriving at the fence can be generated, and the notification message corresponding to the event of the children's watch not arriving at the fence is sent to the screen-off interface, the capsule, the in-capsule notification bar, the notification / dynamic notification bar, the YOYO card, and the main interface of the smart watch worn by the parent for display. Among them, the display color of the notification message can be orange.

[0176] 724: The card management module sends a card display launch instruction to the service display framework.

[0177] It can be understood that after the card management module finishes drawing the card of the notification message corresponding to the device event, it can send a card display launch instruction to the service display framework to indicate the display position of the notification message corresponding to the device event on the service display framework and display the card of the notification message corresponding to the device event.

[0178] 725: The service display framework feeds back the successful display launch information to the card management module.

[0179] It can be understood that after the service display framework receives the card display launch instruction sent by the card management module, it can execute the card display launch instruction, display the card of the notification message corresponding to the device event at the display position of the notification message corresponding to the device event, and feed back the successful display launch information to the card management module.

[0180] 726: The event receiving module starts the display duration timer.

[0181] It can be understood that when the notification sharing module issues a notification card drawing instruction to the card management module, it can start the display duration timer, and before the service display framework feeds back the successful display launch information to the card management module, the event receiving module determines whether the notification message corresponding to the device event meets the card cancellation policy.

[0182] In some optional examples, the card cancellation policy can be that the displayed duration of the notification message corresponding to the device event is equal to the display duration of the notification message corresponding to the device event, the user removes the notification message corresponding to the device event, and so on.

[0183] 727: When the event receiving module detects that the notification message corresponding to the device event meets the card cancellation policy, it issues a card cancellation request to the card management module.

[0184] It can be understood that when the event receiving module detects that the displayed duration of the notification message corresponding to the device event is equal to the display duration of the notification message corresponding to the device event, or the user removes the notification message corresponding to the device event, it can issue a card cancellation request to the card management module.

[0185] 728: The card management module sends a card destruction request to the service display framework.

[0186] It can be understood that after the card management module receives the card cancellation request issued by the event receiving module, it can send the card cancellation request to the service display framework.

[0187] 729: The service display framework returns the successful destruction information to the card management module.

[0188] It can be understood that after the service display framework receives the card cancellation request sent by the card management module, it can destroy the card corresponding to the device event notification message, that is, no longer display the card corresponding to the device event notification message, and return a successful destruction message to the card management module.

[0189] 730: If the card management module detects that the consumer clicks on the card.

[0190] It can be understood that before the event receiving module sends a card cancellation request to the card management module, if the card management module detects that the consumer clicks on the card, the card management module can confirm the jump / processing logic based on the associated information configured in the event configuration table.

[0191] 731: The card management module confirms the jump / processing logic based on the associated information of the configuration information of the device event.

[0192] It can be understood that before the event receiving module sends a card cancellation request to the card management module, if the card management module detects that the consumer clicks on the card, the card management module can confirm the jump / processing logic based on the associated information of the configuration information of the device event, such as adjusting application programs such as the smart space application program and the phone application program.

[0193] 732: The card management module sends a jump instruction to the smart space application program.

[0194] It can be understood that after the card management module confirms the jump / processing logic, it can jump to application programs such as the smart space application program and the phone application program based on the associated information of the configuration information of the device event.

[0195] In the embodiments of the present application, different forms of display are performed on the notification messages based on different types of notification messages to remind the user, which can reduce the situation where the user ignores the notification messages and improve the user experience.

[0196] The hardware structure of the electronic device will be introduced below. As Figure 9As shown, the electronic device 900 may include a processor 910, an external memory interface 920, an internal memory 921, a universal serial bus (USB) interface 930, a charging management module 940, a power management module 941, a battery 942, an antenna 1, an antenna 2, a mobile communication module 950, a wireless communication module 960, an audio module 970, a speaker 970A, a receiver 970B, a microphone 970C, a headphone jack 970D, a sensor module 980, keys 990, a motor 991, an indicator 992, a camera 993, a display screen 994, and a subscriber identification module (SIM) card interface 995, etc. The sensor module 980 may include a pressure sensor 980A, etc.

[0197] It can be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device 900 may include more or fewer components than those shown, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0198] The processor 910 may include one or more processing units. For example, the processor 910 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0199] In some optional examples, the processor 910 may execute the message notification method mentioned in the embodiments of the present application.

[0200] The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0201] A memory can also be set in the processor 910 for storing instructions and data. In some embodiments, the memory in the processor 910 is a cache memory. This memory can save the instructions or data that the processor 910 has just used or recycled. If the processor 910 needs to use the instruction or data again, it can be directly called from the memory. This avoids repeated accesses, reduces the waiting time of the processor 910, and thus improves the efficiency of the system.

[0202] In some alternative examples, the memory can store the instructions or data of the message notification method mentioned in the embodiments of the present application, and can also store the configuration information of each smart device in the smart home system (i.e., the event notification template list file mentioned above).

[0203] The wireless communication function of the electronic device can be implemented by antenna 1, antenna 2, mobile communication module 950, wireless communication module 960, modulation and demodulation processor, and baseband processor, etc.

[0204] Antenna 1 and antenna 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example: Antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0205] The mobile communication module 950 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the electronic device. The mobile communication module 950 can include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 950 can receive electromagnetic waves by antenna 1, filter, amplify, etc. the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 950 can also amplify the signal modulated by the modulation and demodulation processor and convert it into electromagnetic waves through antenna 1 for radiation. In some embodiments, at least some functional modules of the mobile communication module 950 can be set in the processor 910. In some embodiments, at least some functional modules of the mobile communication module 950 and at least some modules of the processor 910 can be set in the same device.

[0206] The modulation and demodulation processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. Subsequently, the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 970A, the receiver 970B, etc.), or displays an image or video through the display screen 994. In some embodiments, the modulation and demodulation processor may be an independent device. In other embodiments, the modulation and demodulation processor may be independent of the processor 910 and be provided in the same device as the mobile communication module 950 or other functional modules.

[0207] The wireless communication module 960 may provide solutions for wireless communications applied to the electronic device, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (GNSSs), frequency modulation (FM), near field communication (NFC), infrared technology (IR), etc. The wireless communication module 960 may be one or more devices integrating at least one communication processing module. The wireless communication module 960 receives electromagnetic waves via the antenna 2, frequency-modulates and filters the electromagnetic wave signal, and transmits the processed signal to the processor 910. The wireless communication module 960 may also receive the signal to be transmitted from the processor 910, frequency-modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

[0208] In some embodiments, antenna 1 of the electronic device is coupled to the mobile communication module 950, and antenna 2 is coupled to the wireless communication module 960, enabling the electronic device to communicate with the network and other devices through wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), beidou navigation satellite system (BDS), quasi-zenith satellite system (QZSS), and / or satellite based augmentation systems (SBAS).

[0209] The electronic device realizes the display function through the GPU, the display screen 994, and the application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 994 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 910 may include one or more GPUs, which execute program instructions to generate or change display information.

[0210] The display screen 994 is used to display images, videos, etc. The display screen 994 includes a display panel. The display panel can adopt a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device may include one or N display screens 994, where N is a positive integer greater than 1.

[0211] In some alternative examples, the display screen 994 can display such as Figure 2 , Figure 3 , Figure 4A , Figure 4B , Figure 4C , Figure 4D , Figure 5B the content displayed.

[0212] The pressure sensor 980A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 980A can be disposed on the display screen 994. There are many types of pressure sensors 980A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can include at least two parallel plates with conductive materials. When a force acts on the pressure sensor 980A, the capacitance between the electrodes changes. The electronic device determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 994, the electronic device detects the intensity of the touch operation according to the pressure sensor 980A. The electronic device can also calculate the position of the touch according to the detection signal of the pressure sensor 980A. In some embodiments, touch operations with the same touch position but different touch operation intensities can correspond to different operation instructions. For example: When a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, the instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, the instruction to create a new short message is executed.

[0213] Embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as a computer program or program code executed on a programmable system that includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0214] The program code can be applied to input instructions to perform the various functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit, or a microprocessor.

[0215] The program code can be implemented in a high-level procedural language or an object-oriented programming language in order to communicate with the processing system. When needed, the program code can also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any particular programming language. In any case, the language can be a compiled language or an interpreted language.

[0216] In some cases, the disclosed embodiments can be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments can also be implemented as instructions carried or stored on one or more transient or non-transient machine-readable (e.g., computer-readable) storage media, which can be read and executed by one or more processors. For example, the instructions can be distributed via a network or via other computer-readable media. Thus, a machine-readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, floppy disks, optical disks, optical discs, compact discs read-only memory (CD-ROMs), magneto-optical discs, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic or optical cards, flash memory, or tangible machine-readable memories for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms using the Internet. Thus, a machine-readable medium includes any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0217] The above describes the possible hardware structures of an electronic device. It can be understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than those shown in the figures, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figures can be implemented in hardware, software, or a combination of software and hardware.

[0218] In the accompanying drawings, some structural or method features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or ordering may not be required. Instead, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Additionally, including a structural or method feature in a particular figure does not imply that such a feature is required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0219] Embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of this application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memories and / or storage elements), at least one input device, and at least one output device.

[0220] The program code can be applied to the input instructions to perform the various functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit, or a microprocessor.

[0221] The program code can be implemented in a high-level procedural language or an object-oriented programming language to communicate with the processing system. When needed, the program code can also be implemented in assembly language or machine language. In fact, the mechanisms described in this application are not limited to the scope of any specific programming language. In any case, the language can be a compiled language or an interpreted language.

[0222] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more transient or non-transient machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or via other computer-readable media. Thus, machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, floppy disks, optical disks, optical discs, compact disc read-only memories (CD-ROMs), magneto-optical discs, read-only memories (ROMs), random access memories (RAMs), erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, flash memory, or tangible machine-readable memories for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms via the Internet. Thus, machine-readable media include any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0223] It should be noted that each unit / module mentioned in the device embodiments of the present application is a logical unit / module. Physically, a logical unit / module may be a physical unit / module, may be a part of a physical unit / module, or may also be implemented as a combination of multiple physical units / module. The physical implementation manner of these logical units / module themselves is not the most important. The combination of the functions implemented by these logical units / module is the key to solving the technical problems proposed by the present application. In addition, in order to highlight the innovative part of the present application, the above device embodiments of the present application do not introduce units / modules that are not closely related to solving the technical problems proposed by the present application, which does not mean that there are no other units / modules in the above device embodiments.

[0224] It should be noted that in the examples and the specification of this patent, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one" does not exclude the presence of additional identical elements in the process, method, article or device comprising the element.

[0225] Although the present application has been illustrated and described with reference to certain preferred embodiments thereof, those of ordinary skill in the art should understand that various changes may be made therein in form and detail without departing from the scope of the present application.

Claims

1. A method for a notification message, applied to a first electronic device, characterized in that, including: Upon receiving a first notification message, determining that the first notification message includes a first device event; Displaying the first notification message with first display configuration information corresponding to the first device event; Upon receiving a second notification message, determining that the second notification message includes a second device event, where the type of the second device event is different from that of the first device event; Displaying the second notification message with second display configuration information corresponding to the second device event, where the second display configuration information is different from the first display configuration information.

2. The method according to claim 1, wherein The display configuration information includes at least one of the following: Display position, display priority and notification form corresponding to each display position, and notification parameters corresponding to the notification form.

3. The method according to claim 2, characterized in that The display position includes a lock screen interface, a home screen, a notification bar, a capsule, a negative first screen, a notification bar inside the capsule, and a display interface of a second electronic device associated with the first electronic device.

4. The method according to claim 3, characterized in that, The second electronic device includes at least one of the following: A smart wearable device, a virtual reality device, an augmented reality device, a smart driving device.

5. The method according to claim 2, wherein The notification form includes at least one of the following: Text, ringtone, vibration.

6. The method according to claim 5, wherein Corresponding to the notification form being text, the notification parameters include font size, color, and display duration; Corresponding to the notification form being a card, the notification parameters include an icon, a title, a color, and display duration; Corresponding to the notification form being a ringtone, the notification parameters include volume and ringtone duration; Corresponding to the notification form being vibration, the notification parameters include vibration frequency and vibration duration.

7. The method according to claim 2, wherein The higher the display priority, the lower the probability that the notification message is overwritten.

8. The method according to claim 2, characterized in that The types of device events include at least one of the following: Regular events, reminder events, security events, alarm events; Among them, the regular events include: door open event, door close event, door lock event, air conditioner off event; The reminder events include: laundry completion event, microwave heating completion event, kettle boiling completion event; The security events include: sweeper failure event, lighting failure event; The alarm events include: door pry alarm event, children's watch position alarm event, missed emergency call alarm event.

9. The method according to claim 8, wherein The display priority of the regular events is lower than that of the reminder events, the display priority of the reminder events is lower than that of the security events, and the display priority of the security events is lower than that of the alarm events.

10. The method according to claim 8, wherein The first device event is the missed emergency call alarm event; and The displaying of the first notification message includes: Displaying the first notification message in the form of a card, where the card includes a first-level jump component for making a callback to the first device corresponding to the first device event.

11. The method according to claim 10, wherein The method further includes: Detecting a first operation by the user on the first-level jump component, Displaying a callback interface, where the callback interface includes a second-level jump component for locating the position of the first device corresponding to the first device event; Detecting a second operation by the user on the second-level jump component, Display a positioning interface, where the positioning interface includes the current location or historical location of the first device.

12. The method according to claim 1, characterized in that, The operating system of the first electronic device includes an event configuration table management module in the framework layer, and The method further includes: Obtain a first display configuration table corresponding to the first device event through the event configuration table management module.

13. The method according to claim 12, wherein The operating system of the first electronic device includes an event parsing and decision-making module in the framework layer, and The method further includes: Read the first display configuration table through the event parsing and decision-making module to determine first display configuration information corresponding to the first device event.

14. An electronic device, characterized in that, Includes: A memory for storing instructions executed by one or more processors of the electronic device, and a processor, which is one of the one or more processors of the electronic device, for executing the method for a notification message according to any one of claims 1-13.

15. A readable storage medium, characterized in that, Instructions are stored on the readable storage medium, and when the instructions are executed on the electronic device, the electronic device executes the method for a notification message according to any one of claims 1-13.

16. A computer program product, characterized in that, The computer program product includes computer instructions, and when executed by the electronic device, the electronic device executes the method for a notification message according to any one of claims 1-13.

Images