Reminding event setting method and device, equipment and storage medium

Abstract

The invention discloses a reminding event setting method and device, equipment and a storage medium, and belongs to the field of intelligent wearable equipment. The method is executed by first equipment and comprises the following steps: receiving a setting operation of a first reminding event; setting the first reminding event according to the setting operation; the first reminding event is used for controlling the first equipment to execute event reminding when a reminding condition is met; sending a synchronization message under the condition that the shutdown early warning condition is met; the shutdown early warning condition is used for determining that the first equipment is to be shut down; the synchronization message is used for synchronizing the first reminding event to the second equipment. According to the method, the user experience of reminding event setting on the intelligent equipment can be optimized.

Description

Technical Field

[0001] The present application relates to the field of smart wearable devices, and in particular to a method, device, equipment and storage medium for setting reminder events. Background Art

[0002] The alarm function of smart watches provides users with a convenient personalized reminder service. Users can set alarms on smart watches to remind them of key times or key events.

[0003] However, when the smartwatch suddenly runs out of power, the alarm information pre-set by the user will not be available, resulting in interruption of the alarm function. For example, the user may have set a series of personalized alarms on the smartwatch, such as weekday morning fitness reminders and important meeting reminders, but because the smartwatch is out of power, these preset alarms will become invalid, and the user will miss key time or key events, which seriously affects the user experience. Summary of the invention

[0004] The present application provides a method, apparatus, device and storage medium for setting reminder events, which can optimize the user experience of setting reminder events on smart devices. The technical solution is as follows:

[0005] According to one aspect of the present application, a method for setting a reminder event is provided, the method being executed by a first device, the method comprising:

[0006] Receive a setting operation for a first reminder event;

[0007] The first reminder event is set according to the setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met;

[0008] When a shutdown warning condition is met, a synchronization message is sent; the shutdown warning condition is used to determine that the first device will be shut down; and the synchronization message is used to synchronize the first reminder event to the second device.

[0009] According to another aspect of the present application, a method for setting a reminder event is provided, the method being executed by a second device, the method comprising:

[0010] receiving a synchronization message; the synchronization message is triggered by the first device when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize a first reminder event set on the first device to the second device;

[0011] Setting a second reminder event in the second device according to the synchronization message;

[0012] When the reminder condition of the second reminder event is met, the event reminder is executed.

[0013] According to another aspect of the present application, a device for setting a reminder event is provided, the device comprising:

[0014] An interaction module, configured to receive a setting operation of a first reminder event;

[0015] A first setting module, used for setting the first reminder event according to the setting operation; the first reminder event is used for controlling the first device to execute an event reminder when a reminder condition is met;

[0016] The first sending module is used to send a synchronization message when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will be shut down; and the synchronization message is used to synchronize the first reminder event to the second device.

[0017] According to another aspect of the present application, a device for setting a reminder event is provided, the device comprising:

[0018] A receiving module, configured to receive a synchronization message; the synchronization message is triggered by the first device when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize a first reminder event set on the first device to the second device;

[0019] A second setting module, configured to set a second reminder event in the second device according to the synchronization message;

[0020] The reminder module is used to execute event reminder when the reminder condition of the second reminder event is met.

[0021] According to another aspect of the present application, a computer device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by the processor to implement the method for setting a reminder event as described above.

[0022] According to another aspect of the present application, a computer-readable storage medium is provided, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is loaded and executed by a processor to implement the method for setting a reminder event as described above.

[0023] According to another aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method for setting a reminder event provided in various optional implementations of the above aspects.

[0024] The beneficial effects of the technical solution provided by this application include at least:

[0025] When it is determined that the first device is about to shut down according to the shutdown warning condition, the first device is controlled to send a synchronization message to synchronize the reminder event set in the first device to the second device. The second device can automatically synchronize the reminder event in the first device to the second device according to the synchronization message, so that after the first device is shut down, the event reminder is executed through the second device. This method can automatically synchronize the reminder event of the first device on the second device when the first device is about to shut down, improve the setting efficiency of the reminder event, and avoid the impact of device shutdown on the reminder event, ensuring that the event reminder can be triggered on time when the reminder condition is met, and optimizing the user experience of setting the reminder event. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0027] Figure 1 is a schematic diagram of the structure of a computer system provided by an exemplary embodiment of the present application;

[0028] Figure 2 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application;

[0029] Figure 3 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application;

[0030] Figure 4 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application;

[0031] Figure 5 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application;

[0032] Figure 6is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application;

[0033] Figure 7 It is a structural schematic diagram of a device for setting a reminder event provided by an exemplary embodiment of the present application;

[0034] Figure 8 It is a structural schematic diagram of a device for setting a reminder event provided by an exemplary embodiment of the present application;

[0035] Fig. 9 It is a structural diagram of a computer device provided by an exemplary embodiment of the present application.

[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application. DETAILED DESCRIPTION

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

[0038] Figure 1 A schematic diagram of a computer system provided by an exemplary embodiment of the present application is shown, and the computer system may include a first device 101, a second device 102 and a server 103.

[0039] Exemplarily, the method for setting a reminder event shown in the embodiment of the present application can be applied to the first device 101 or the second device 102. The first device 101 runs an application 104 that supports the setting of reminder events. The first device may include a smart wearable device (such as a smart watch, smart glasses), an Internet of Things device, a mobile phone, a tablet computer, a notebook computer, a laptop computer, a desktop computer, an all-in-one computer, an intelligent robot workstation, a television, a set-top box, a digital camera, an MP4 player, an MP5 player, a learning machine, a point-reading machine, an electronic paper book, an electronic dictionary, a vehicle-mounted device, a virtual reality (VR) player or an augmented reality (AR) player, etc.

[0040] Exemplarily, the method for setting a reminder event provided in the present application may be executed by an operating system in the first device 101. Alternatively, the method for setting a reminder event provided in the present application may also be executed by a client in the first device 101. The client is a client of an application that supports setting reminder events. For example, the application may include at least one of the following: an alarm clock application, a memo application, a calendar application, a memorial application, a video application, a short video application, a social application, a shopping application, a local service application, a live broadcast application, an information application, a browser, and a game application.

[0041] The first device 101 includes a first memory and a first processor. The first memory stores a setting program for a reminder event; the setting program for the reminder event is called and executed by the first processor to implement the setting method for a reminder event provided in the present application. The first memory may include but is not limited to the following: Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), and Electric Erasable Programmable Read-Only Memory (EEPROM).

[0042] The first processor may be composed of one or more integrated circuit chips. Optionally, the first processor may be a general-purpose processor, such as a central processing unit (CPU) or a network processor (NP). Optionally, the first processor may implement the method for setting the reminder event provided in the present application by running a program or code.

[0043] The second device 102 runs an application 104 that supports setting reminder events. The first device may include a smart wearable device (e.g., a smart watch, smart glasses), an IoT device, a mobile phone, a tablet computer, a notebook computer, a laptop computer, a desktop computer, an all-in-one computer, an intelligent robot workstation, a television, a set-top box, a digital camera, an MP4 player, an MP5 player, a learning machine, a point-reading machine, an electronic paper book, an electronic dictionary, a vehicle-mounted device, a virtual reality (VR) player, or an augmented reality (AR) player, etc.

[0044] Exemplarily, the method for setting a reminder event provided in the present application may be executed by an operating system in the second device 102. Alternatively, the method for setting a reminder event provided in the present application may also be executed by a client in the second device 102. The client is a client of an application that supports setting reminder events. For example, the application may include at least one of the following: an alarm clock application, a memo application, a calendar application, a memorial application, a video application, a short video application, a social application, a shopping application, a local service application, a live broadcast application, an information application, a browser, and a game application.

[0045] The second device 102 includes a second memory and a second processor. The second memory stores a setting program for reminder events; the setting program for the reminder events is called and executed by the second processor to implement the setting method for reminder events provided in the present application. The second memory may include but is not limited to the following: RAM, ROM, PROM, EPROM, EEPROM. The second processor may be composed of one or more integrated circuit chips. Optionally, the second processor may be a general-purpose processor, such as a CPU or NP. Optionally, the second processor may implement the setting method for reminder events provided in the present application by running a program or code.

[0046] The first device 101 and the second device 102 may establish a connection through direct communication. The direct communication includes at least one of the following: Bluetooth, WiFi (Wireless Fidelity), NFC (Near Field Communication), infrared communication, Zigbee, UWB (Ultra-Wideband), RFID (Radio Frequency Identification), Ultrasonic Communication, LoRa (Long Range, long-range low-power communication), and wired direct communication.

[0047] In an optional embodiment, the first device 101 and the server 103 may be connected to each other via a wired or wireless network. The second device 102 and the server 103 may be connected to each other via a wired or wireless network.

[0048] The server 103 is used to provide background services for the operating systems of the first device 101 and the second device 102. Alternatively, the server 103 is used to provide background services for the clients of the first device 101 and the second device 102. Optionally, the server 103 undertakes the main computing work, and the first device 101 / the second device 102 undertakes the secondary computing work; or, the server 103 undertakes the secondary computing work, and the first device 101 / the second device 102 undertakes the main computing work; or, the server 103 and the first device 101 / the second device 102 adopt a distributed computing architecture for collaborative computing.

[0049] The server 103 may be a single server, or a server cluster consisting of multiple servers, or a cloud computing service center.

[0050] Optionally, the server 103 includes a second memory and a second processor. The second memory stores a setting program for a reminder event; the setting program for the reminder event is called by the second processor to implement the setting method for the reminder event provided in the present application. Optionally, the second memory may include but is not limited to the following: RAM, ROM, PROM, EPROM, EEPROM. Optionally, the second processor may be a general-purpose processor, such as a CPU or NP.

[0051] Take the first device as a smart watch and the second device as a mobile phone as an example. In the related art, a variety of data interactions can be performed between smart watches and mobile phones. For example, through Bluetooth connection, smart watches can synchronize sports data, notification information, etc. with mobile phones. In terms of alarm settings, users usually set alarms on smart watches and mobile phones separately, and their respective alarm setting information is stored in the local storage of the corresponding devices. When the smart watch has sufficient power, its alarm function runs normally according to the preset time and setting parameters; and the alarm of the mobile phone also runs independently according to its own settings. There is no specific mechanism between the two to automatically transfer the alarm preset when the smart watch is out of power. When the smart watch suddenly runs out of power, the alarm information that the user has carefully set on the smart watch will not be available, resulting in the interruption of the alarm function. For example, the user may set a series of alarms for fitness reminders, important meeting reminders, etc. on the smart watch on weekdays, but these alarm settings will become invalid after the smart watch runs out of power, and the user needs to set them one by one on the mobile phone again, which is extremely inconvenient and easy to miss important events due to forgetfulness or setting errors. This incoherent alarm setting mechanism does not conform to the user experience concept of modern smart devices pursuing convenience and seamless connection. Users need to manage alarm settings separately across different devices, which increases usage costs and complexity. Especially in common emergencies such as smart watches running out of power, existing technical solutions cannot provide effective solutions to ensure that users' alarm services are not interrupted, reducing users' satisfaction with the collaborative use of smart wearable devices and mobile phones.

[0052] In order to solve this problem, the embodiment of the present application provides a method for setting a reminder event. When the first device 101 is about to shut down, the locally set reminder event (such as an alarm clock) can be synchronized to the second device 102 through a direct communication connection with the second device 102. After the first device 101 is shut down, the second device 102 can trigger an event reminder when the reminder condition is met. Alternatively, when the first device 101 is about to shut down, the locally set reminder event can be reported to the server 103, and the second device 102 obtains the reminder event from the server, so that the second device 102 can execute the event reminder after the first device 101 is shut down.

[0053] In an optional embodiment, the first device 101 and the second device 102 are both equipped with a Bluetooth communication module, and both can interact with the server 103. The first device 101 has a built-in alarm setting module (or reminder event setting module), a power monitoring module, a Bluetooth connection module, and a data transmission module. The second device 102 is also equipped with an alarm management module, a Bluetooth connection module, a data receiving and processing module, and a network module for interacting with the server. The server includes a data storage unit and a data processing unit for storing and processing reminder event data and related information from the first device 101 and the second device 102.

[0054] Taking the first device as a smart watch and the second device as a mobile phone as an example, the workflow can be:

[0055] When the smart watch and mobile phone are paired and connected for the first time, a secure connection channel is established through Bluetooth, and registration and binding are carried out with the server to ensure the establishment of identity recognition and data interaction permissions between the three.

[0056] During normal operation of the smartwatch, the user sets the alarm in the usual way. The alarm setting module inside the smartwatch stores the setting information in the local cache and regularly synchronizes and backs up the data with the server to ensure data security and real-time performance.

[0057] When the smart watch power monitoring module detects that the power level is lower than the preset threshold (for example, 2%), the data transmission process is started immediately. The data transmission module first attempts to send the alarm preset information to the mobile phone via Bluetooth connection. If the Bluetooth connection is successful, the mobile phone receives the data and processes it, such as displaying a prompt message to inform the user that the smart watch alarm preset information has been successfully received, and asks the user whether to enable it immediately. If the user confirms, the mobile phone alarm management module will update the alarm settings according to the received information and start running; if the user chooses to process it later, the information will be temporarily stored in a specific cache area of ​​the mobile phone until the user manually enables it. If the Bluetooth connection fails, the data transmission module will encrypt the alarm preset information and upload it to the server, and record the upload status on the smart watch.

[0058] When the Bluetooth connection between the smartwatch and the mobile phone is restored to normal, the mobile phone automatically detects whether there is an unprocessed server alarm preset information download task. If so, the download process is started to download the encrypted data from the server, and after decryption, the alarm setting is updated and operated according to the above mobile phone receiving and processing steps. At the same time, the mobile phone can also regularly and actively query the server for new smartwatch alarm preset information to ensure that the transferred alarm settings can be obtained and processed in time in any case, ensuring the continuity and reliability of the alarm function.

[0059] Figure 2 1 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application. The method can be used for a first device. The method includes the following steps.

[0060] Step 210: Receive a setting operation of a first reminder event.

[0061] Exemplarily, the first device may be a smart wearable device, for example, a smart watch or a smart bracelet. An application supporting the reminder event setting function is installed on the first device, and the method provided in this embodiment is executed by the application; or, the method provided in this embodiment is executed by an operating system on the first device.

[0062] The first device can display a display interface for a reminder event, and the display interface can display an adding control for the reminder event; in response to an operation that triggers the adding control, an adding interface for the reminder event is displayed, and the adding interface is used to edit the event information of the reminder event; a setting operation for the reminder event is received on the adding interface, and in response to a setting completion operation, a first reminder event is set according to the event information edited by the setting operation.

[0063] Reminder events are notifications or reminders set to help users remember or complete a task or activity on time, or pay attention to an important date or event. Event reminders usually appear in the form of sound, pop-up windows, vibrations, etc., to attract the user's attention and prompt them to take action. Reminder events can be set based on a variety of factors such as time, geographic location, operation behavior, important dates, etc. to meet the needs of users in different scenarios. By setting reminder events, users can manage their time and tasks more effectively and avoid missing important time nodes or forgetting to perform a task.

[0064] For example, the reminder event may include at least one of an alarm, a memo, a memorial day, and a to-do list.

[0065] Exemplarily, the setting operation of the first reminder event is used to set the event information of the first reminder event. The event information includes at least a reminder condition. The reminder condition may include at least one of the following: a time condition (e.g., setting a reminder time), a location condition (e.g., setting a reminder location), and an operation condition (e.g., setting a target operation behavior).

[0066] When the first reminder event is an alarm, the event information may include at least one of the following: alarm time, repetition type, alarm ringtone, alarm volume, alarm name, and whether to vibrate.

[0067] When the first reminder event is a memo, the event information may include at least one of the following: memo content, reminder time, repetition type, importance, reminder method (eg, pop-up window, ringtone, notification bar, etc.), and memo category.

[0068] When the first reminder event is a memorial day, the event information may include at least one of the following: memorial day name, date, reminder time, repetition type, and reminder method.

[0069] When the first reminder event is triggered based on a geographical location, the event information may further include the reminder location. When the first reminder event is triggered based on a user's operation behavior, the event information may further include a target operation behavior.

[0070] Step 220: Setting a first reminder event according to a setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met.

[0071] Exemplarily, the first device sets a first reminder event locally on the first device according to the event information edited by the setting operation, and the first device can execute the event reminder when the reminder condition of the first reminder event is triggered.

[0072] Step 230: Send a synchronization message when the shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will be shut down; the synchronization message is used to synchronize the first reminder event to the second device.

[0073] Exemplarily, the shutdown warning condition is used to determine that the first device will be shut down. And / or, the shutdown warning condition is used to determine that the first device will not be able to continue to execute the event reminder of the first reminder event.

[0074] In an optional embodiment, the shutdown warning condition can be set according to the power level of the first device. When the power level of the first device reaches a power level threshold, a synchronization message is sent. The power level threshold can be 2% or 1%.

[0075] Exemplarily, the power threshold may include an automatic shutdown threshold; when the power of the first device reaches the automatic shutdown threshold, an automatic shutdown process is executed; wherein the automatic shutdown process includes: sending a synchronization message.

[0076] Alternatively, the shutdown warning condition may include an automatic shutdown condition, which is used to trigger the automatic shutdown process of the first device. That is, when the first device meets the automatic shutdown condition, the automatic shutdown process is triggered, and the first device is set to send a synchronization message in the automatic shutdown process, and the first device is controlled to shut down after the synchronization message is successfully sent.

[0077] In another optional embodiment, the shutdown warning condition can be determined by a shutdown warning model. The shutdown warning model is a neural network model. The first device can record the device parameters for a period of time before each automatic shutdown, generate training samples based on the recorded device parameters, and use the training samples to automatically train and update the shutdown warning model so that it can accurately predict that the first device is about to shut down. Among them, the device parameters may include at least one of the following: power, network status, processor operating status, memory operating status, device temperature, and ambient temperature. The first device can periodically collect the current device parameters, input the current device parameters into the shutdown warning model to obtain a prediction result, and when the prediction result is that the device is about to shut down, it is determined that the shutdown warning conditions are met.

[0078] In another optional embodiment, the shutdown warning condition can be judged by the device disability model, and the device disability model is used to predict that the first device loses the ability to remind the event. For example, the first device's audio failure or abnormal magnetic field nearby makes the first device unable to trigger or execute event reminders. The server can collect a large amount of operating status information of the same type of devices as the first device, generate negative samples based on the operating status information when the device is disabled, and generate positive samples based on the operating status information when the device is normally running, and use positive and negative samples to train the device disability model. After the model training is completed, the device disability model is sent to the first device, so that the first device periodically collects the operating status information, and the operating status information is input into the device disability model to predict whether the first device is disabled, and when the first device is disabled, it is determined that the shutdown warning condition is met. Among them, the operating status information can include at least one of the following: power, sensor status, audio device status, network status, operating system status, application running status, system log, magnetic field strength, geographic location, and environmental noise.

[0079] Optionally, the first device may send a synchronization message to the second device through a direct communication connection between the first device and the second device; or, send a synchronization message to a server, which is used to synchronize the synchronization message to the second device; or, if sending a synchronization message to the second device through a direct communication connection fails, send a synchronization message to the server.

[0080] The synchronization message may carry event information of the first reminder event, so that the second device sets the second reminder event in the second device according to the synchronization message.

[0081] Figure 3 1 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application. The method can be used for a second device. The method includes the following steps.

[0082] Step 310: Receive a synchronization message; the synchronization message is triggered by the first device when the shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize the first reminder event set on the first device to the second device.

[0083] Exemplarily, the second device may be a smart terminal device, for example, the first device may be a mobile phone, a tablet or a computer. An application supporting the reminder event setting function is installed on the first device, and the method provided in this embodiment is executed by the application; or, the method provided in this embodiment is executed by an operating system on the first device.

[0084] Optionally, the second device receives a synchronization message sent by the first device through a direct communication connection between the first device and the second device; or, receives a synchronization message sent by a server.

[0085] Step 320: Setting a second reminder event in the second device according to the synchronization message.

[0086] The synchronization message may carry the event information of the first reminder event, and the second device may set a new reminder event locally according to the event information to obtain a second reminder event. The second reminder event is a reminder event set in the second device according to the event information of the first reminder event, and the event information of the first reminder event and the second reminder event may be exactly the same.

[0087] Optionally, the event information of the first reminder event and the second reminder event may also be partially the same. For example, if the first device supports setting the event name of the reminder event, but the second device does not support setting the event name of the reminder event, the event information of the first reminder event may include the first event name, while the event information of the second reminder event does not include the event name. For another example, if the first device does not support setting the reminder ringtone, but the second device supports setting the reminder ringtone, the event information of the first reminder event does not include the reminder ringtone, while the event information of the second reminder event may include the default reminder ringtone of the second device.

[0088] Optionally, the event information of the second reminder event can also be obtained based on the event information of the first reminder event. For example, in combination with the positioning function of the second device, when the reminder event of the first device is transferred to the second device, the second device can intelligently adjust the reminder event according to the current location information. For example, if the user is traveling and sets an alarm based on the local time, when the user crosses the time zone, the second device can automatically adjust the alarm time according to the new time zone information, providing a more intelligent and user-friendly alarm service. That is, the synchronization message includes the first event information of the first reminder event, and the second device corrects the time in the first event information according to the current location information to obtain the corrected second event information, and obtains the second reminder event based on the second event information setting.

[0089] In an optional embodiment, if the second device successfully receives the synchronization message, it can also display the activation inquiry information of the reminder event, asking the user whether to activate the reminder event from the first device. If the user confirms to activate, the reminder event of the first device is set and activated in the second device; if the user chooses not to activate or to process it later, the reminder event of the first device is set in the second device, but it is set to the inactivated state, so that the user can activate the reminder event with one click when it needs to be activated.

[0090] The second device displays the enabling inquiry information of the reminder event, and the enabling inquiry information is used to inquire whether to enable the second reminder event; in response to confirming the enabling operation, the second reminder event is created and enabled in the second device; in response to the later processing operation, the second reminder event is created in the second device, and the second reminder event is set to a pending enabling state.

[0091] Step 330: When the reminder condition of the second reminder event is met, execute the event reminder.

[0092] Exemplarily, the reminder conditions of the first reminder event and the second reminder event are the same, and when the reminder condition is triggered, the second device can execute the event reminder. The reminder method of the event reminder includes at least one of the following: ringing, vibration, displaying message notification, displaying light effects, sending reminder signals to make other devices issue reminders, etc.

[0093] The reminder condition can be set according to at least one of time, location, and behavior operation. For example, the reminder condition can be an alarm at 10 o'clock every day; or the reminder condition can be an alarm when arriving at the workstation; or the reminder condition can be an alarm when the target application is opened between 10 and 11 o'clock every day.

[0094] It should be noted that at this time, the first device is powered off and cannot execute the event reminder, and the second device executes the event reminder instead of the first device.

[0095] In an optional embodiment, in order to avoid repeated reminders from the first device and the second device, the second device can verify the status of the first device before executing the second reminder event, and execute the event reminder of the second reminder event when it is not connected to the first device. That is, when the reminder condition of the second reminder event is met, the second device sends a status verification request to the first device, and executes the event reminder of the second reminder event when no feedback from the first device is received within the preset time. When feedback from the first device is received within the preset time, the event reminder of the second reminder event is not executed, and the second reminder event is set to an inactive state. Optionally, the preset time can be set to a very short time, for example, 1ms.

[0096] In an optional embodiment, the method provided in the embodiment of the present application can not only be used to synchronize reminder events, but also synchronize other personalized settings in the first device to the second device when the first device is about to shut down. For example, some specific display settings, health monitoring reminder settings, etc. on the first device can also be selectively synchronized to the second device when the first device is low on power, allowing users to maintain a consistent personalized experience when using the second device to replace some functions of the first device, enriching the collaborative functions between smart devices and the integrity of the user experience.

[0097] In summary, the method provided in this embodiment, when it is determined that the first device is about to shut down according to the shutdown warning condition, controls the first device to send a synchronization message to synchronize the reminder event set in the first device to the second device. The second device can automatically synchronize the reminder event in the first device to the second device according to the synchronization message, so that after the first device is shut down, the event reminder is executed through the second device. This method can automatically synchronize the reminder event of the first device on the second device when the first device is about to shut down, improve the setting efficiency of the reminder event, and avoid the impact of device shutdown on the reminder event, ensuring that the event reminder can be triggered on time when the reminder condition is met, and optimizing the user experience of setting the reminder event.

[0098] In an optional embodiment, the first device may synchronize the reminder event to the second device through a direct communication connection with the second device.

[0099] Figure 4 1 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application. The method can be used for a first device and a second device. The method can include the following steps.

[0100] Step 401: The first device receives a setting operation of a first reminder event, and sets the first reminder event according to the setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met.

[0101] Step 402: When the shutdown warning condition is met, the first device sends a synchronization message to the second device through a direct communication connection between the first device and the second device; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize the first reminder event to the second device.

[0102] The direct communication may include at least one of the following: Bluetooth, WiFi, NFC, infrared communication, Zigbee, UWB, RFID, ultrasonic communication, LoRa, and wired direct communication.

[0103] Exemplarily, the first device can synchronize reminder events to the second device when it is about to shut down and instruct the second device to enable these reminder events. The first device sends a first synchronization message when the shutdown warning condition is met; the first synchronization message is used to synchronize with the second device and enable the reminder events that have been turned on by the first device; the first synchronization message carries the event information of the first reminder event.

[0104] It should be noted that the reminder event will trigger the event reminder only when the reminder conditions are met after it is enabled; when the reminder event is not enabled, the event reminder will not be triggered.

[0105] Step 403: The second device receives the synchronization message, and sets a second reminder event in the second device according to the synchronization message.

[0106] Exemplarily, the second device receives the second synchronization message, and sets and enables the second reminder event in the second device according to the second synchronization message.

[0107] Step 404: The second device executes an event reminder when the reminder condition of the second reminder event is met.

[0108] In summary, the method provided in this embodiment is that when it is determined that the first device is about to shut down according to the shutdown warning conditions, the first device can send a synchronization message to the second device through a direct communication connection with the second device to synchronize the reminder event set in the first device. The second device can automatically synchronize the reminder event in the first device to the second device according to the synchronization message, so that after the first device is shut down, the event reminder is executed through the second device. This method can automatically synchronize the reminder event of the first device on the second device when the first device is about to shut down, improve the setting efficiency of the reminder event, and avoid the impact of device shutdown on the reminder event, ensuring that the event reminder can be triggered on time when the reminder conditions are met, and optimizing the user experience of setting the reminder event.

[0109] In another optional embodiment, when the first device fails to synchronize reminder events to the second device through direct communication, the first device may also synchronize reminder events to the server so that the second device obtains the synchronized reminder events through the server.

[0110] Figure 5 1 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application. The method can be used for a first device and a second device. The method can include the following steps.

[0111] Step 501: The first device receives a setting operation of a first reminder event, and sets the first reminder event according to the setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met.

[0112] Step 502: When the shutdown warning condition is met, the first device sends a synchronization message to the second device through a direct communication connection between the first device and the second device; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize the first reminder event to the second device.

[0113] Exemplarily, the first device may preferentially send a synchronization message to the second device directly through a direct communication connection after the shutdown warning condition is met; if the sending is successful, Figure 4 The method shown in the figure sets a reminder event in the second device. If the sending fails, follow Figure 5 In the method shown, the first device sends a synchronization message to the server.

[0114] Step 503: When the first device fails to send a synchronization message to the second device through the direct communication connection, the first device sends a synchronization message to the server.

[0115] Exemplarily, if the first device cannot synchronize the reminder event to the second device through direct communication, the first device sends a synchronization message of the reminder event to the server, and temporarily stores the local reminder event of the first device on the server.

[0116] The server may receive and store the synchronization message, and the synchronization message may be stored in association with the device identification of the first device.

[0117] Step 504: The second device sends a query request to the server, where the query request is used to request to query the synchronization message of the first device.

[0118] The second device may periodically send a query request to the server, and the query request may carry the device identification of the first device. The server may query the synchronization message of the first device according to the query request and forward it to the second device. Exemplarily, the second device may establish a connection relationship with the first device in advance, obtain the device identification of the first device, and then periodically send a query request to the server to query the synchronization messages of other devices (such as the first device) that have a connection relationship with the second device.

[0119] In an optional embodiment, the server may also actively send a synchronization message of the first device to the second device when the second device is connected to the server. Exemplarily, the server may store a connection relationship between the first device and the second device, and when the server stores a synchronization message of the first device and the second device is connected to the server, the server sends a synchronization message of the first device to the second device.

[0120] Step 505: The second device receives the synchronization message sent by the server.

[0121] Step 506: The second device sets a second reminder event in the second device according to the synchronization message.

[0122] Step 507: The second device executes event reminder when the reminder condition of the second reminder event is met.

[0123] In summary, the method provided in this embodiment establishes an automatic transfer mechanism for reminder events between the first device and the second device under specific conditions (for example, the first device is out of power). By giving priority to direct communication and assisting the server, it ensures that the setting data of the reminder event can be smoothly transferred from the first device to the second device, realizing the deep integration and collaboration of the smart wearable device and the smart terminal in the reminder event setting function.

[0124] In the method provided in this embodiment, during the data transmission and processing process, the first device can automatically determine the connection status of the direct communication and flexibly select the data transmission path (direct communication transmission or server transit), and at the same time, the second device intelligently analyzes and integrates the received data so that it can be seamlessly integrated into the reminder event management system of the second device. This intelligent data processing and interaction method greatly improves the adaptability and reliability of the system, which is different from the traditional simple data transmission and fixed setting mode.

[0125] In yet another optional embodiment, the first device may periodically synchronize local reminder events to the second device, and notify the second device to enable these reminder events when the first device is about to shut down.

[0126] Figure 6 1 is a flow chart of a method for setting a reminder event provided by an exemplary embodiment of the present application. The method can be used for a first device and a second device. The method can include the following steps.

[0127] Step 601: The first device receives a setting operation of a first reminder event, and sets the first reminder event according to the setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met.

[0128] Step 602: the first device periodically sends a second synchronization message; the second synchronization message is used to synchronize the reminder event created in the first device to the second device; the second synchronization message carries the event information of the first reminder event.

[0129] Exemplarily, the first device may also synchronize local reminder events to the second device or server in real time. For example, the first device periodically sends the second synchronization message to the first device, or the first device periodically sends the second synchronization message to the second device.

[0130] Step 603: The second device receives the second synchronization message, and sets a second reminder event in the second device according to the second synchronization message.

[0131] The second device may receive the second synchronization message sent by the first device. Alternatively, the second device may periodically send a query request to the server and receive the second synchronization message of the first device returned by the server. Alternatively, the server may periodically send the second synchronization message of the first device to the second device.

[0132] After receiving the second synchronization message, the second device sets a second reminder event locally according to the second synchronization message, and the second reminder event is obtained according to the first reminder event of the first device. It should be noted that the second reminder event set according to the second synchronization message is in an unactivated state, and the second device will not execute the event reminder of the second reminder event.

[0133] In this way, the first device can synchronize all reminder events set locally to the second device in real time.

[0134] Step 604: When the shutdown warning condition is met, the first device sends a third synchronization message; the third synchronization message is used to instruct the second device to enable the reminder event that has been turned on by the first device; the third synchronization message carries the event identifier of the first reminder event.

[0135] When the first device is about to shut down, the first device can send a third synchronization message, which carries the event identifier of the currently enabled reminder event to instruct the second device to enable these reminder events. Since the event information of the reminder event has been synchronized to the second device in the second synchronization message, the third synchronization message does not need to carry the event information of the reminder event, but only needs to carry the event identifier, which reduces the data volume of the third synchronization message, so that the first device can quickly send the third synchronization message when it is about to shut down.

[0136] In an optional embodiment, the first device may send a third synchronization message during the automatic shutdown process to indicate the enabled reminder event to the second device.

[0137] Exemplarily, the first device may send the third synchronization message to the second device. The first device may also send the third synchronization message to the server. The first device may also send the third synchronization message to the server after failing to send the third synchronization message to the second device, so that the server sends the third synchronization message to the second device.

[0138] Step 605: The second device receives the third synchronization message, and activates the second reminder event according to the third synchronization message.

[0139] The second device may receive a third synchronization message sent by the first device, the third synchronization message may carry an event identifier of the first reminder event, and the second device may enable a second reminder event corresponding to the first reminder event according to the event identifier of the first reminder event.

[0140] The second device may also receive a third synchronization message sent by the server. The third synchronization message may carry an event identifier of the first reminder event. The second device may enable a second reminder event corresponding to the first reminder event according to the event identifier of the first reminder event.

[0141] Step 606: The second device executes the event reminder when the reminder condition of the second reminder event is met.

[0142] In summary, the method provided in this embodiment allows the first device to periodically synchronize reminder events to the second device, so that the second device can synchronize the reminder events set in the first device in real time. When the first device is about to shut down, it can indicate the currently enabled reminder events to the second device through a synchronization message to control the second device to enable the corresponding reminder events. In this way, the first device can simply and quickly indicate the enabled reminder events to the second device when it is about to shut down or in the shutdown process, thereby improving the efficiency of setting reminder events, avoiding the impact of device shutdown on reminder events, ensuring that event reminders can be triggered on time when the reminder conditions are met, and optimizing the user experience of setting reminder events.

[0143] It should be noted that before collecting relevant data of users and during the process of collecting relevant data of users, this application can display a prompt interface, pop-up window or output voice prompt information, and the prompt interface, pop-up window or voice prompt information is used to prompt the user that its relevant data is currently being collected, so that this application only starts to execute the relevant steps of obtaining relevant data of users after obtaining the confirmation operation issued by the user to the prompt interface or pop-up window, otherwise (that is, when the confirmation operation issued by the user to the prompt interface or pop-up window is not obtained), the relevant steps of obtaining relevant data of users are terminated, that is, the relevant data of users are not obtained. In other words, all user data collected by this application are collected with the consent and authorization of the user, and the collection, use and processing of relevant user data need to comply with the relevant laws, regulations and standards of relevant countries and regions.

[0144] It should be noted that the sequence of the method steps provided in the embodiments of the present application can be appropriately adjusted, and the steps can be increased or decreased accordingly according to the circumstances. Any technician familiar with the technical field can easily think of the changed methods within the technical scope disclosed in the present application, and they should be included in the protection scope of the present application, so they will not be repeated here.

[0145] Figure 7 1 is a schematic diagram of a device for setting a reminder event provided by an exemplary embodiment of the present application. The device includes:

[0146] The interaction module 701 is used to receive a setting operation of a first reminder event;

[0147] A first setting module 702, configured to set the first reminder event according to the setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met;

[0148] The first sending module 703 is used to send a synchronization message when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will be shut down; the synchronization message is used to synchronize the first reminder event to the second device.

[0149] In an optional embodiment, the first sending module 703 is configured to send the synchronization message when the power level of the first device reaches a power threshold.

[0150] In an optional embodiment, the power threshold includes an automatic shutdown threshold;

[0151] The first sending module 703 is used to execute an automatic shutdown process when the power of the first device reaches an automatic shutdown threshold;

[0152] Wherein, the automatic shutdown process includes: sending the synchronization message.

[0153] In an optional embodiment, the first sending module 703 is configured to perform one of the following:

[0154] Sending the synchronization message to the second device through a direct communication connection between the first device and the second device;

[0155] Sending the synchronization message to a server, where the server is used to synchronize the synchronization message to the second device;

[0156] In case sending the synchronization message to the second device through the direct communication connection fails, sending the synchronization message to the server.

[0157] In an optional embodiment, the first sending module 703 is used to send a first synchronization message when the shutdown warning condition is met; the first synchronization message is used to synchronize with the second device and enable the reminder event that has been turned on by the first device; the first synchronization message carries event information of the first reminder event.

[0158] In an optional embodiment, the first sending module 703 is used to periodically send a second synchronization message; the second synchronization message is used to synchronize the reminder event created in the first device to the second device; the second synchronization message carries the event information of the first reminder event;

[0159] The first sending module 703 is used to send a third synchronization message when the shutdown warning condition is met; the third synchronization message is used to instruct the second device to enable the reminder event that the first device has turned on; the third synchronization message carries the event identifier of the first reminder event.

[0160] In an optional embodiment, the first reminder event includes an alarm clock.

[0161] Figure 8 1 is a schematic diagram of a device for setting a reminder event provided by an exemplary embodiment of the present application. The device includes:

[0162] The receiving module 801 is used to receive a synchronization message; the synchronization message is triggered by the first device when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize the first reminder event set on the first device to the second device;

[0163] A second setting module 802, configured to set a second reminder event in the second device according to the synchronization message;

[0164] The reminder module 803 is used to execute event reminder when the reminder condition of the second reminder event is met.

[0165] In an optional embodiment, the receiving module 801 is configured to perform one of the following:

[0166] Receiving the synchronization message sent by the first device through a direct communication connection between the first device and the second device;

[0167] The synchronization message sent by the server is received.

[0168] In an optional embodiment, the device further includes:

[0169] The second sending module 804 is configured to send a query request to a server, where the query request is used to request to query the synchronization message of the first device.

[0170] In an optional embodiment, the second setting module 802 is used to display activation inquiry information of the reminder event, and the activation inquiry information is used to inquire whether to activate the second reminder event;

[0171] The second setting module 802 is used to create and enable the second reminder event in the second device in response to the confirmation and activation operation;

[0172] The second setting module 802 is used to create the second reminder event in the second device in response to a later processing operation, and the second reminder event is set to a to-be-enabled state.

[0173] It should be noted that the device for setting reminder events provided in the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device for setting reminder events provided in the above embodiment and the embodiment of the method for setting reminder events belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0174] The embodiment of the present application also provides a computer device, which includes: a processor and a memory, wherein at least one instruction, at least one program, code set or instruction set is stored in the memory, and the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the setting method of the reminder event provided by the above-mentioned method embodiments. The computer device can be implemented as a first device or a second device.

[0175] For example, Fig. 9 It is a structural diagram of a computer device provided by an exemplary embodiment of the present application.

[0176] Typically, the computer device 1700 includes a processor 1701 and a memory 1702 .

[0177] The processor 1701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 1701 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 1701 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 1701 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 1701 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0178] The memory 1702 may include one or more computer-readable storage media, which may be non-transitory. The memory 1702 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 1702 is used to store at least one instruction, which is used to be executed by the processor 1701 to implement the method for setting a reminder event provided in the method embodiment of the present application.

[0179] In some embodiments, the computer device 1700 may also optionally include: a peripheral device interface 1703 and at least one peripheral device. The processor 1701, the memory 1702 and the peripheral device interface 1703 may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface 1703 via a bus, a signal line or a circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 1704, a display screen 1705, a camera assembly 1706, an audio circuit 1707 and a power supply 1708.

[0180] The peripheral device interface 1703 may be used to connect at least one peripheral device related to I / O (Input / Output) to the processor 1701 and the memory 1702. In some embodiments, the processor 1701, the memory 1702, and the peripheral device interface 1703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 1701, the memory 1702, and the peripheral device interface 1703 may be implemented on a separate chip or circuit board, which is not limited in the embodiments of the present application.

[0181] The radio frequency circuit 1704 is used to receive and transmit RF (Radio Frequency) signals, also known as electromagnetic signals. The radio frequency circuit 1704 communicates with the communication network and other communication devices through electromagnetic signals. The radio frequency circuit 1704 converts the electrical signal into an electromagnetic signal for transmission, or converts the received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 1704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a user identity module card, and the like. The radio frequency circuit 1704 can communicate with other computer devices through at least one wireless communication protocol. The wireless communication protocol includes, but is not limited to: the World Wide Web, a metropolitan area network, an intranet, various generations of mobile communication networks (2G, 3G, 4G and 5G), a wireless local area network and / or a WiFi (Wireless Fidelity) network. In some embodiments, the radio frequency circuit 1704 may also include circuits related to NFC (Near Field Communication), which is not limited in this application.

[0182] The display screen 1705 is used to display a UI (User Interface). The UI may include graphics, text, icons, videos, and any combination thereof. When the display screen 1705 is a touch display screen, the display screen 1705 also has the ability to collect touch signals on the surface or above the surface of the display screen 1705. The touch signal can be input to the processor 1701 as a control signal for processing. At this time, the display screen 1705 can also be used to provide virtual buttons and / or virtual keyboards, also known as soft buttons and / or soft keyboards. In some embodiments, the display screen 1705 can be one, and the front panel of the computer device 1700 is set; in other embodiments, the display screen 1705 can be at least two, which are respectively set on different surfaces of the computer device 1700 or are folded; in some other embodiments, the display screen 1705 can be a flexible display screen, which is set on the curved surface or folded surface of the computer device 1700. Even, the display screen 1705 can also be set to a non-rectangular irregular shape, that is, a special-shaped screen. The display screen 1705 can be made of materials such as LCD (Liquid Crystal Display) and OLED (Organic Light-Emitting Diode).

[0183] The camera assembly 1706 is used to capture images or videos. Optionally, the camera assembly 1706 includes a front camera and a rear camera. Typically, the front camera is arranged on the front panel of the computer device 1700, and the rear camera is arranged on the back of the computer device. In some embodiments, there are at least two rear cameras, which are any one of a main camera, a depth of field camera, a wide-angle camera, and a telephoto camera, so as to realize the fusion of the main camera and the depth of field camera to realize the background blur function, the fusion of the main camera and the wide-angle camera to realize the panoramic shooting and VR (Virtual Reality) shooting function or other fusion shooting functions. In some embodiments, the camera assembly 1706 may also include a flash. The flash can be a monochrome temperature flash or a dual-color temperature flash. A dual-color temperature flash refers to a combination of a warm light flash and a cold light flash, which can be used for light compensation at different color temperatures.

[0184] The audio circuit 1707 may include a microphone and a speaker. The microphone is used to collect sound waves from the user and the environment, and convert the sound waves into electrical signals and input them into the processor 1701 for processing, or input them into the radio frequency circuit 1704 to achieve voice communication. For the purpose of stereo acquisition or noise reduction, there may be multiple microphones, which are respectively arranged at different parts of the computer device 1700. The microphone may also be an array microphone or an omnidirectional acquisition microphone. The speaker is used to convert the electrical signal from the processor 1701 or the radio frequency circuit 1704 into sound waves. The speaker may be a traditional film speaker or a piezoelectric ceramic speaker. When the speaker is a piezoelectric ceramic speaker, it can not only convert the electrical signal into sound waves audible to humans, but also convert the electrical signal into sound waves inaudible to humans for purposes such as ranging. In some embodiments, the audio circuit 1707 may also include a headphone jack.

[0185] The power supply 1708 is used to power various components in the computer device 1700. The power supply 1708 can be an alternating current, a direct current, a disposable battery, or a rechargeable battery. When the power supply 1708 includes a rechargeable battery, the rechargeable battery can be a wired rechargeable battery or a wireless rechargeable battery. A wired rechargeable battery is a battery that is charged through a wired line, and a wireless rechargeable battery is a battery that is charged through a wireless coil. The rechargeable battery can also be used to support fast charging technology.

[0186] In some embodiments, the computer device 1700 further includes one or more sensors 1709 , including but not limited to: an acceleration sensor 1710 , a gyroscope sensor 1711 , a pressure sensor 1712 , an optical sensor 1713 , and a proximity sensor 1714 .

[0187] The acceleration sensor 1710 can detect the magnitude of acceleration on the three coordinate axes of the coordinate system established by the computer device 1700. For example, the acceleration sensor 1710 can be used to detect the components of gravity acceleration on the three coordinate axes. The processor 1701 can control the touch display screen 1705 to display the user interface in a horizontal view or a vertical view according to the gravity acceleration signal collected by the acceleration sensor 1710. The acceleration sensor 1710 can also be used to collect game or user motion data.

[0188] The gyro sensor 1711 can detect the body direction and rotation angle of the computer device 1700, and the gyro sensor 1711 can cooperate with the acceleration sensor 1710 to collect the user's 3D actions on the computer device 1700. The processor 1701 can implement the following functions based on the data collected by the gyro sensor 1711: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

[0189] The pressure sensor 1712 can be set on the side frame of the computer device 1700 and / or the lower layer of the touch display screen 1705. When the pressure sensor 1712 is set on the side frame of the computer device 1700, it can detect the user's grip signal of the computer device 1700, and the processor 1701 performs left and right hand recognition or shortcut operations according to the grip signal collected by the pressure sensor 1712. When the pressure sensor 1712 is set on the lower layer of the touch display screen 1705, the processor 1701 controls the operability controls on the UI interface according to the user's pressure operation on the touch display screen 1705. The operability controls include at least one of a button control, a scroll bar control, an icon control, and a menu control.

[0190] The optical sensor 1713 is used to collect the ambient light intensity. In one embodiment, the processor 1701 can control the display brightness of the touch display screen 1705 according to the ambient light intensity collected by the optical sensor 1713. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 1705 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 1705 is reduced. In another embodiment, the processor 1701 can also dynamically adjust the shooting parameters of the camera assembly 1706 according to the ambient light intensity collected by the optical sensor 1713.

[0191] The proximity sensor 1714, also called a distance sensor, is usually arranged on the front panel of the computer device 1700. The proximity sensor 1714 is used to collect the distance between the user and the front of the computer device 1700. In one embodiment, when the proximity sensor 1714 detects that the distance between the user and the front of the computer device 1700 is gradually decreasing, the processor 1701 controls the touch display screen 1705 to switch from the screen-on state to the screen-off state; when the proximity sensor 1714 detects that the distance between the user and the front of the computer device 1700 is gradually increasing, the processor 1701 controls the touch display screen 1705 to switch from the screen-off state to the screen-on state.

[0192] Those skilled in the art will understand that Fig. 9 The structure shown in the figure does not constitute a limitation on the computer device 1700, and the computer device 1700 may include more or less components than shown in the figure, or combine some components, or adopt a different arrangement of components.

[0193] A computer-readable storage medium is also provided in an embodiment of the present application, in which at least one instruction, at least one program, code set or instruction set is stored. When the at least one instruction, at least one program, code set or instruction set is loaded and executed by a processor of a computer device, the method for setting a reminder event provided in the above-mentioned method embodiments is implemented.

[0194] The present application also provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method for setting a reminder event provided by each of the above method embodiments.

[0195] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned readable storage medium may be a read-only memory, a disk or an optical disk, etc.

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

Claims

1. A method for setting a reminder event, characterized in that: The method is performed by a first device, and includes: Receive a setting operation for a first reminder event; The first reminder event is set according to the setting operation; the first reminder event is used to control the first device to execute an event reminder when a reminder condition is met; When a shutdown warning condition is met, a synchronization message is sent; the shutdown warning condition is used to determine that the first device will be shut down; and the synchronization message is used to synchronize the first reminder event to the second device.

2. The method according to claim 1, characterized in that The sending of a synchronization message when the shutdown warning condition is met includes: When the power level of the first device reaches a power threshold, the synchronization message is sent.

3. The method according to claim 2, characterized in that The power threshold includes an automatic shutdown threshold; The sending the synchronization message when the power level of the first device reaches a power threshold includes: When the power of the first device reaches the automatic shutdown threshold, executing the automatic shutdown process; Wherein, the automatic shutdown process includes: sending the synchronization message.

4. The method according to any one of claims 1 to 3, characterized in that: The sending of the synchronization message includes one of the following: Sending the synchronization message to the second device through a direct communication connection between the first device and the second device; Sending the synchronization message to a server, where the server is used to synchronize the synchronization message to the second device; In case sending the synchronization message to the second device through the direct communication connection fails, sending the synchronization message to the server.

5. The method according to any one of claims 1 to 3, characterized in that: The sending of a synchronization message when the shutdown warning condition is met includes: When the shutdown warning condition is met, a first synchronization message is sent; the first synchronization message is used to synchronize with the second device and enable the reminder event that has been turned on by the first device; the first synchronization message carries event information of the first reminder event.

6. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Periodically sending a second synchronization message; the second synchronization message is used to synchronize the reminder event created in the first device to the second device; the second synchronization message carries the event information of the first reminder event; The sending of a synchronization message when the shutdown warning condition is met includes: When the shutdown warning condition is met, a third synchronization message is sent; the third synchronization message is used to instruct the second device to enable the reminder event that the first device has turned on; the third synchronization message carries the event identifier of the first reminder event.

7. The method according to any one of claims 1 to 3, characterized in that: The first reminder event includes an alarm.

8. A method for setting a reminder event, characterized in that: The method is performed by a second device, and includes: receiving a synchronization message; the synchronization message is triggered by the first device when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize a first reminder event set on the first device to the second device; Setting a second reminder event in the second device according to the synchronization message; When the reminder condition of the second reminder event is met, the event reminder is executed.

9. The method according to claim 8, characterized in that The receiving of a synchronization message includes one of the following: Receiving the synchronization message sent by the first device through a direct communication connection between the first device and the second device; The synchronization message sent by the server is received.

10. The method according to claim 9, characterized in that The method further comprises: A query request is sent to a server, where the query request is used to request a query for a synchronization message of the first device.

11. The method according to any one of claims 8 to 10, characterized in that: The setting a second reminder event in the second device according to the synchronization message includes: Displaying activation inquiry information of a reminder event, wherein the activation inquiry information is used to inquire whether to activate the second reminder event; In response to confirming the enabling operation, creating and enabling the second reminder event in the second device; In response to a later processing operation, the second reminder event is created in the second device, and the second reminder event is set to a to-be-enabled state.

12. A device for setting a reminder event, characterized in that: The device comprises: An interaction module, configured to receive a setting operation of a first reminder event; A first setting module, used for setting the first reminder event according to the setting operation; the first reminder event is used for controlling the first device to execute an event reminder when a reminder condition is met; The first sending module is used to send a synchronization message when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will be shut down; and the synchronization message is used to synchronize the first reminder event to the second device.

13. A device for setting a reminder event, characterized in that: The device comprises: A receiving module, configured to receive a synchronization message; the synchronization message is triggered by the first device when a shutdown warning condition is met; the shutdown warning condition is used to determine that the first device will shut down; the synchronization message is used to synchronize a first reminder event set on the first device to the second device; A second setting module, configured to set a second reminder event in the second device according to the synchronization message; The reminder module is used to execute event reminder when the reminder condition of the second reminder event is met.

14. A computer device, characterized in that: The computer device includes a processor and a memory, wherein the memory stores at least one program, and the at least one program is loaded and executed by the processor to implement the method for setting a reminder event as described in any one of claims 1 to 11.

15. A computer-readable storage medium, characterized in that: The readable storage medium stores at least one program, and the at least one program is loaded and executed by the processor to implement the method for setting a reminder event according to any one of claims 1 to 11.

16. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method for setting a reminder event as described in any one of claims 1 to 11.

Images