Reminding method and device

Abstract

The invention discloses a reminding method and device, and the method comprises the steps: obtaining object state information of a second object in second equipment in response to a target interaction operation for a first object in first equipment; if the object state information meets the object state condition, processing reminding information representing that second processing is executed on a second object is output, and / or second equipment is controlled to execute the second processing on the second object; wherein the second processing corresponds to the first processing, and the first processing is the processing which is triggered by the target interaction operation and executed for the first object.

Description

Technical Field

[0001] The present application relates to the field of electronic technology, and in particular to a reminder method and device. Background Art

[0002] With the widespread use of smart devices, users frequently use a variety of portable electronic devices in their daily lives, such as smart watches, bracelets, headphones, mobile phones, and tablets. During use, users often need to perform the same processing operations on multiple electronic devices, such as charging and data cleaning.

[0003] Generally, if the user has a strong desire, they will operate each device; if the user has a weak desire, they will operate whichever device they remember. This is very inconvenient for the user. Summary of the Invention

[0004] In view of this, embodiments of the present application provide at least one reminder method.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] In a first aspect, an embodiment of the present application provides a reminder method, the reminder method comprising:

[0007] In response to a target interaction operation on the first object in the first device, obtaining object state information of the second object in the second device;

[0008] If the object state information satisfies an object state condition, outputting processing reminder information indicating that a second process is to be performed on the second object, and / or controlling the second device to perform the second process on the second object;

[0009] The second processing corresponds to the first processing, and the first processing is a processing executed on the first object triggered by the target interaction operation.

[0010] In a second aspect, an embodiment of the present application provides a reminder device, the reminder device comprising:

[0011] an acquisition module, configured to acquire object state information of a second object in a second device in response to a target interaction operation on a first object in a first device;

[0012] an output module, configured to output processing reminder information indicating that a second process is to be performed on the second object if the object state information satisfies an object state condition, and / or control the second device to perform the second process on the second object;

[0013] The second processing corresponds to the first processing, and the first processing is a processing executed on the first object triggered by the target interaction operation.

[0014] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and do not limit the technical solutions of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and, together with the specification, are used to illustrate the technical solutions of the present application.

[0016] Figure 1a Schematic diagram 1 of an implementation flow of a reminder method provided in an embodiment of the present application;

[0017] Figure 1b Scenario diagram 1 of a reminder method provided in an embodiment of the present application;

[0018] Figure 1c A scenario diagram of a reminder method provided in an embodiment of the present application Figure 2 ;

[0019] Figure 1d A scenario diagram of a reminder method provided in an embodiment of the present application Figure 3 ;

[0020] Figure 2 Schematic diagram of the implementation process of a reminder method provided in an embodiment of the present application Figure 2 ;

[0021] Figure 3 A schematic diagram of the implementation process of a reminder method provided in an embodiment of the present application Figure 3 ;

[0022] Figure 4 A schematic diagram of the structure of a reminder device provided in an embodiment of the present application;

[0023] Figure 5 This is a schematic diagram of a hardware entity of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to make the purpose, technical solutions and advantages of this application clearer, the technical solutions of this application are further elaborated in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limiting this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0025] In the following description, reference is made to “some embodiments”, which describes a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0026] The terms "first / second / third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that "first / second / third" can be interchanged with a specific order or sequence where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing this application only and are not intended to limit this application.

[0028] In order to solve the technical problems in the related art, the embodiment of the present application provides a reminder method, which can be applied to electronic devices. For example, the electronic devices include but are not limited to smart phones, tablet computers, wearable devices, personal computers (PCs), netbooks, etc. The embodiment of the present application does not have fixed restrictions on its implementation form.

[0029] Figure 1a A schematic diagram of a reminder method implementation process provided in an embodiment of the present application is shown in FIG. Figure 1a As shown, the reminder method can be implemented through steps S101 and S102:

[0030] Step S101 : In response to a target interaction operation on a first object in a first device, object state information of a second object in a second device is acquired.

[0031] Here, the target interaction operation refers to an operation behavior initiated by a user on a first device with respect to a first object, and the operation behavior triggers a process with respect to the first object.

[0032] Exemplarily, when the target interaction operation is a charging operation, when the user connects a charger to the first device, or the user places the first device on the wireless charging apparatus, the first device detects the charging operation;

[0033] When the target interactive operation is an application update operation, the application update operation may be a click operation performed by the user on an update control of a corresponding application of the first device.

[0034] When the target interactive operation is a data cleaning operation, the data cleaning operation may be a click operation performed by the user on a data cleaning control of the first device, or a gesture operation and / or voice operation performed by the user on the first device;

[0035] When the target interaction operation is a permission change operation, the permission change operation can be a click operation of a user on a permission change control of the first device, or a gesture operation and / or a voice operation of the user on the first device.

[0036] When the target interaction operation is a network connection operation, the permission change operation can be a click operation of a user on a network connection control of the first device.

[0037] When the target interaction operation is an application closing operation, the application closing operation can be a click operation of a user on an application closing control of the first device, or a gesture operation and / or a voice operation of the user on the first device.

[0038] In the embodiments of the present application, when the first device detects the target interaction operation of the user on the first object, the object state information of the second object in the second device can be acquired in real time. The second device can be a device in communication connection with the first device, or a device in communication connection with the first device through a third device. The second object is consistent with the first object, or the object type of the second object is consistent with that of the first object. The object state information of the second object is used to determine whether to perform a processing operation corresponding to the processing operation triggered by the target interaction operation on the second object. The object state information can include the current running state and the current attribute information of the second object.

[0039] In the embodiments of the present application, when the first device is in communication connection with the second device, the first device can acquire the object state information of the second object of the second device through communication interaction with the second device when the target interaction operation is detected. When the first device is in communication connection with the second device through a third device, the first device can acquire the object state information of the second object of the second device through communication interaction with the third device when the target interaction operation is detected.

[0040] In some embodiments, the second device can send the object state information of different objects of itself to the first device at a preset frequency, and the first device can store different object state information in the storage space of itself. When the target interaction operation is detected, the first device can acquire the object state information of the second object corresponding to the object type of the first object in the storage space of itself based on the object type of the first object.

[0041] In step S102, if the object state information meets the object state condition, processing reminder information representing execution of a second processing on the second object is output, and / or the second device is controlled to execute the second processing on the second object.

[0042] The second processing corresponds to the first processing, and the first processing is the processing executed on the first object triggered by the target interaction operation.

[0043] Here, the function of determining whether the object status information satisfies the object status condition is to determine whether the second object of the second device needs to perform the second process.

[0044] It can be understood that when the first device performs a first process on the first object in response to the target interaction operation, it is necessary to determine whether the second object of the second device that is communicatively connected to the first device needs to perform a second process corresponding to the first process. In this way, when the second device needs to perform the second process on the second object, it can remind the user to initiate the corresponding interaction operation on the second device in a timely manner, thereby improving the user experience of using the electronic device.

[0045] In an embodiment of the present application, when the object state information satisfies the object state condition, processing reminder information for reminding the user to execute the second process on the second device can be output on the display device of the first device. In some embodiments, the processing reminder information for reminding the user to execute the second process on the second device can also be output via a sound output device.

[0046] In an embodiment of the present application, when the object status information meets the object status condition, the first device may send a control instruction to the second device, and the second device may perform the second processing on the second object in response to the control instruction.

[0047] In some embodiments, if the object status information does not satisfy the object status condition, no processing reminder information is output, and / or the second device is not controlled to perform the second processing on the second object. It is understood that when the object status information does not satisfy the object status condition, it indicates that the second device does not need to perform the second processing on the second object, and therefore the first device does not need to perform an action related to the second device.

[0048] Exemplarily, the first device is a mobile phone and the second device is a watch. When the user performs charging operations on the mobile phone, if the object status information of the watch's battery meets the object status conditions, the mobile phone outputs processing reminder information for charging the watch's battery, and / or the mobile phone controls the watch to charge its own battery; if the object status information of the watch's battery does not meet the object status conditions, the mobile phone does not need to perform actions related to the watch.

[0049] In an embodiment of the present application, when a user performs a target interactive operation on a first object of a first device, the first device will obtain the object status information of the second object in the second device and determine whether the object status information meets the preset conditions. If so, a reminder message is output or the second device is controlled to perform corresponding processing. In this way, by utilizing the communication mechanism between multiple devices, while the user performs a certain operation, it can intelligently identify and remind the user to handle the status issues of other related devices, thereby reducing the occurrence of forgetting to perform the second processing on other devices, thereby improving the user experience and device usage efficiency.

[0050] In some embodiments, the object state information meeting the object state condition indicates that the state of the second object is consistent with the first state of the first object; the first state is the state of the first object before the first processing is performed.

[0051] In an embodiment of the present application, when detecting that a user performs a target interaction operation on a first object, the first device can obtain the state of the first object before executing the first process (i.e., the first state). Then, based on the object state information of the second object, the state of the second object is determined. If the state of the second object is consistent with the first state of the first object, it indicates that the object state information satisfies the object state condition, i.e., the second object of the second device needs to perform the second process.

[0052] It is understandable that the purpose of the user performing the target interaction operation on the first device is to change the state of the first object on the first device through the first processing of the first device triggered by the target interaction operation. In other words, the first state of the first object is not the state expected by the user. Therefore, if the state of the second object is consistent with the first state of the first object, it means that the current state of the second object is also not the state expected by the user, and therefore, the second object on the second device needs to perform the second processing to change its own state.

[0053] Exemplarily, when the target interactive operation is a charging operation, the first object is the battery of the first device, and the second object is the battery of the second device. When the user charges the battery of the first device, it indicates that the battery of the first device is in a low-power state. If the object status information of the battery of the second device obtained by the first device indicates that the battery of the second device is also in a low-power state, it is determined that the object status information of the battery of the second device meets the object status condition, that is, the battery of the second device needs to be charged (that is, the second process).

[0054] When the target interactive operation is an application update operation, the first object is the program object of the first device (such as an application program or a firmware program), and the second object is the program object of the second device. When the user updates the version of the program object of the first device, it indicates that the status of the program object of the first device is a pending update status. If the object status information of the program object of the second device obtained by the first device indicates that the program object of the second device is also a pending update status, it is determined that the object status information of the program object of the second device meets the object status condition, that is, the program object of the second device needs to be updated (that is, the second processing).

[0055] When the target interactive operation is a data cleaning operation, the first object is the memory of the first device (such as storage space or memory), and the second object is the memory of the second device. When the user cleans data on the memory of the first device, it indicates that the status of the memory of the first device is insufficient space. If the object status information of the memory of the second device obtained by the first device indicates that the memory of the second device is also insufficient space, it is determined that the object status information of the memory of the second device meets the object status condition, that is, the memory of the second device needs to be cleaned up (that is, the second processing).

[0056] When the target interactive operation is a permission change operation, the first object is the application permission of the first device, and the second object is the application permission of the second device. When the permission change operation is a permission opening operation, the first state of the application permission of the first device is the closed state; when the permission change operation is a permission closing operation, the first state of the application permission of the first device is the open state. If the object state information of the memory of the second device obtained by the first device indicates that the application permission of the second device and the application permission of the first device are both in the open state, or both are in the closed state, it is determined that the object state information of the application permission of the second device meets the object state condition, that is, the application permission of the second device needs to undergo a permission change operation (i.e., the second processing). Among them, the application permission of the first device and the application permission of the second device may refer to application permissions of the same application type, such as a photo application, a voice application, etc.

[0057] When the target interactive operation is a network connection operation, the first object is the communication connection component of the first device (such as a network connection component or a Bluetooth connection component), and the second object is the communication connection component of the second device. When the user connects to the target communication object (such as a wireless network or a communication object connected via Bluetooth) through the communication connection component of the first device, it indicates that the state of the communication connection component of the first device is not connected to the target communication object. If the object state information of the communication connection component of the second device obtained by the first device indicates that the communication connection component of the second device is also not connected to the target communication object, it is determined that the object state information of the communication connection component of the second device meets the object state condition, that is, it is necessary to connect to the target communication object through the communication connection component of the second device (that is, the second processing).

[0058] When the target interactive operation is an application closing operation, the first object is the background application of the first device, and the second object is the background application of the second device. When the user closes the background application of the first device, it indicates that the background application of the first device is in a state of high power consumption. If the object state information of the background application of the second device obtained by the first device indicates that the background application of the second device is also in a state of high power consumption, it is determined that the object state information of the background application of the second device meets the object state condition, that is, the background application of the second device needs to be closed (that is, the second processing).

[0059] In some embodiments, the object state information meeting the object state condition indicates that the state of the second object is inconsistent with the second state of the first object; the second state is the state of the first object after executing the first processing.

[0060] In an embodiment of the present application, when the first device detects that a user performs a target interactive operation on a first object, it can first perform a first processing on the first object, and then obtain the second state of the first object after the processing. If the state of the second object is inconsistent with the second state of the first object, it indicates that the object state information meets the object state condition, that is, the second object of the second device needs to perform a second processing.

[0061] Exemplarily, when the target interactive operation is a charging operation, the first object is the battery of the first device, and the second object is the battery of the second device. When the battery of the first device is fully charged, the state of the battery of the first device is changed to a fully charged state. If the object state information of the battery of the second device obtained by the first device indicates that the battery of the second device is in a low-power state different from a fully charged state, it is determined that the object state information of the battery of the second device meets the object state condition, that is, the battery of the second device needs to be charged (that is, the second process).

[0062] When the target interactive operation is an application update operation, the first object is the program object of the first device (such as an application program or a firmware program), and the second object is the program object of the second device. When the program object of the first device completes the version update, the state of the program object of the first device is changed to the updated state. If the object state information of the program object of the second device obtained by the first device indicates that the program object of the second device is in a pending update state different from the updated state, it is determined that the object state information of the program object of the second device meets the object state condition, that is, the program object of the second device needs to be updated (that is, the second process).

[0063] When the target interactive operation is a data cleaning operation, the first object is the memory of the first device (such as storage space or memory), and the second object is the memory of the second device. When the memory of the first device completes data cleaning, the state of the memory of the first device is changed to a sufficient space state. If the object state information of the memory of the second device obtained by the first device indicates that the memory of the second device is in an insufficient space state which is different from the sufficient space state, it is determined that the object state information of the memory of the second device meets the object state condition, that is, the memory of the second device needs to be cleaned up (that is, the second processing).

[0064] When the target interactive operation is a permission change operation, the first object is the application permission of the first device, and the second object is the application permission of the second device. After the application permission of the first device is closed, the state of the application permission of the first device is closed; after the application permission of the first device is opened, the state of the application permission of the first device is opened. If the object state information of the memory of the second device obtained by the first device indicates that the application permission of the second device is opened and the application permission of the first device is closed, or the application permission of the second device is closed and the application permission of the first device is opened, it is determined that the object state information of the application permission of the second device meets the object state condition, that is, the application permission of the second device needs to undergo a permission change operation (that is, the second process).

[0065] When the target interactive operation is a network connection operation, the first object is the communication connection component of the first device, and the second object is the communication connection component of the second device. When the communication connection component of the first device is connected to the target communication object, the state of the communication connection component of the first device is a state of being connected to the target communication object. If the object state information of the communication connection component of the second device obtained by the first device indicates that the communication connection component of the second device is not connected to the target communication object, it is determined that the object state information of the communication connection component of the second device meets the object state condition, that is, it is necessary to connect to the target communication object through the communication connection component of the second device (that is, the second processing).

[0066] When the target interactive operation is an application closing operation, the first object is the background application of the first device, and the second object is the background application of the second device. When the background application of the first device is closed, the background application of the first device is in a closed state, that is, in a non-power-consuming state. If the object state information of the background application of the second device obtained by the first device indicates that the state of the background application of the second device is a state with higher power consumption that is different from the closed state, it is determined that the object state information of the background application of the second device meets the object state condition, that is, the background application of the second device needs to be closed (that is, the second processing).

[0067] In an embodiment of the present application, by setting different status conditions to determine whether the object status information of the second device matches the status of the first device, it is possible to flexibly determine whether the second object needs to be processed synchronously based on the changing status of the first object, thereby enhancing the responsiveness of the electronic device.

[0068] In some embodiments, the “outputting processing reminder information indicating that the second processing is to be performed on the second object” in step S102 is implemented by at least one of steps S1021 to S1023:

[0069] Step S1021: Outputting, on the first device, processing reminder information for executing a second process on the second object.

[0070] In the embodiment of the present application, processing reminder information for executing the second process on the second object can be output on the first device executing the first process.

[0071] It is understood that when a user performs a target interactive operation on the first device, it indicates that the user has a high intention to execute a process related to the first process on the electronic device. Therefore, if the second object of the second device requires the second process, a processing reminder message can be output on the first device that is executing the first process. In this way, when the user's execution intention is high, the user can be reminded to also perform the corresponding processing operation on the second object of the second device, thereby improving the timeliness of processing the second object of the second device.

[0072] For example, Figure 1b As shown, when the first device is a mobile phone 101 and the second device is a watch, when the user charges the mobile phone 101 and the watch also needs to be charged, a processing reminder message 102 of "The watch battery is low, please charge as soon as possible" can be displayed on the display interface of the mobile phone 101.

[0073] like Figure 1cAs shown, when the first device is a watch 103 and the second device is a mobile phone, when the user charges the watch 103 and the mobile phone also needs to be charged, a processing reminder message 104 of "Mobile phone battery is low, please charge as soon as possible" can be displayed on the display interface of the watch 103.

[0074] like Figure 1d As shown, when the first device is a watch 103 and the second device is headphones, when the user charges the watch 103 and the headphones also need to be charged, a processing reminder message 105 of "The battery of the headphones is low, please charge as soon as possible" can be displayed on the display interface of the watch 103.

[0075] In some embodiments, when the first device does not have a display device, the processing reminder information can be output through a sound output device.

[0076] Step S1022: Outputting, on the second device, processing reminder information for executing a second process on the second object.

[0077] In an embodiment of the present application, the first device may send processing reminder information to the second device, and the second device may output the processing reminder information through the display device and / or sound output device of the second device.

[0078] For example, when the first device is headphones and the second device is a watch, when the headphones are charging, the headphones can send processing reminder information for charging the watch to the watch, and then the watch outputs the processing reminder information through its own display device and / or sound output device.

[0079] Step S1023: Outputting, on the third device, processing reminder information for executing the second process on the second object.

[0080] In an embodiment of the present application, the first device may send processing reminder information to the third device, and the third device may output the processing reminder information through the display device and / or sound output device of the third device.

[0081] For example, when the first device is headphones, the second device is a watch, and the third device is a mobile phone, when the headphones are charging, the headphones can send a processing reminder message for charging the watch to the mobile phone, and then the mobile phone outputs the processing reminder message through its own display device and / or sound output device.

[0082] In some embodiments, as Figure 2 As shown, the "obtaining the object status information of the second object in the second device" in the above step S101 can be implemented through steps S201 to S203:

[0083] Step S201: Send an inquiry request to the second device or the third device.

[0084] Here, the inquiry request is a communication instruction issued by the first device for querying the object state information of the second object of the second device. The inquiry request is usually transmitted through a wireless communication protocol and contains an identifier of the second device and object attribute information (such as power, running state, etc.) of the second object to be queried. For example, when a user is charging a mobile phone, the mobile phone can send an inquiry request to a watch paired with the mobile phone to enable the mobile phone to confirm whether the watch is currently in a low power state.

[0085] In some embodiments, when the second device has no direct communication connection with the first device, the first device can send an inquiry request to a third device connected to both of them to obtain the object state information of the second object of the second device through the third device.

[0086] Step S202, receiving feedback information sent by the second device or the third device.

[0087] Step S203, determining the object state information of the second object in the second device based on the feedback information.

[0088] In the embodiments of the present application, after receiving the feedback information, the second device can obtain the object state information of the second object according to the object attribute information of the second object carried in the inquiry request, and then send the object state information to the first device through the feedback information.

[0089] Exemplarily, in the case that the second object is a battery, the object attribute information of the battery can be identification information of the battery, and the second device can obtain a power state value of the battery according to the identification information of the battery. The power state value can be a state of charge (SOC) of the battery.

[0090] In the embodiments of the present application, the inquiry request is sent to the second device or the third device, and the information fed back by the second device or the third device is received, and then the object state information of the second object is determined based on the feedback information. In this way, when the user operates the first device, the state of the second device can be synchronously understood, so that the user can be timely reminded to perform corresponding operations on the second device, and thus the device management efficiency and user experience can be improved.

[0091] In some embodiments, the object state information includes a state value; for example, Figure 3 As shown in the above, the reminding method can also be implemented through steps S301 to S303:

[0092] Step S301, obtaining a state value corresponding to the second object.

[0093] Here, the state value refers to a specific quantitative indicator representing the current running state of the second object. For example, the state value may represent the battery power state value, the memory space state value, and the power consumption state value of the background application.

[0094] In the embodiment of the present application, the state value corresponding to the second object is obtained by real-time acquisition by a sensor or system interface within the second device. After obtaining the state value corresponding to the second object, the second device can send the state value corresponding to the second object to the first device, or to a third device, which can then send the state value to the first device.

[0095] Step S302: If the magnitude relationship between the state value and the target value is a first relationship, the object state information satisfies the object state condition.

[0096] Step S303: If the magnitude relationship between the state value and the target value is a second relationship, the object state information does not satisfy the object state condition; wherein the first relationship is different from the second relationship.

[0097] Here, the target value is a preset threshold value used as a judgment standard. For example, in a battery charging scenario, the target value is the power state value, and the target value can be set to 20%, that is, when the power state value of the second device is lower than 20%, the second device is considered to be in a low power state, that is, the size relationship between the state value and the target value is a first relationship, and the object state information of the second device meets the object state condition; when the power state value of the second device is greater than or equal to 20%, the second device is considered not to be in a low power state, that is, the size relationship between the state value and the target value is a second relationship, and the object state information of the second device does not meet the object state condition. Among them, the target value is usually set according to actual usage needs, and can be preset at the factory or customized by the user.

[0098] In the embodiments of the present application, the first relationship and the second relationship respectively represent different comparison results between the state value and the target value. For example, if the first relationship is that the state value is less than the target value, then the second relationship is that the state value is greater than or equal to the target value; or if the first relationship is that the state value is greater than or equal to the target value, then the second relationship is that the state value is less than the target value.

[0099] In an embodiment of the present application, if the size relationship between the status value and the target value is a first relationship, the first device outputs processing reminder information representing the execution of the second processing on the second object, and / or controls the second device to perform the second processing on the second object; if the size relationship between the status value and the target value is a second relationship, the first device does not perform actions related to the second device.

[0100] In the embodiment of the present application, by introducing the comparison logic between the state value and the target value, it is possible to more accurately determine whether the second object needs to undergo the second process. This can reduce the problem of missed processes caused by ambiguous judgments, thereby improving the accuracy of reminding users.

[0101] In some embodiments, the second object of the second device includes at least one of the following: a battery, a memory, and a background application; the status value corresponding to the object status information includes at least one of the following: a power status value of the battery, a space status value of the memory, and a power consumption status value of the background application; the above step S302 is implemented by at least one of steps S3021 to S3023:

[0102] Step S3021: When the battery power status value is less than or equal to a predetermined power value, determine that the object status information meets the object status condition.

[0103] In an embodiment of the present application, when the power status value of the battery of the second device is less than or equal to a predetermined power value, it indicates that the size relationship between the status value of the second object of the second device and the target value is a first relationship, that is, the object status information of the second object of the second device meets the object status condition, and the battery of the second device needs to be charged.

[0104] In an embodiment of the present application, when the battery power status value is less than or equal to a predetermined power value, processing reminder information indicating that charging processing is to be performed on the battery is output, and / or the second device is controlled to charge the battery.

[0105] In some embodiments, when the power status value of the battery of the second device is greater than a predetermined power value, it indicates that the size relationship between the status value of the second object of the second device and the target value is a second relationship, that is, the object status information of the second object of the second device does not meet the object status condition, and the battery of the second device does not need to be charged, and there is no need to output processing reminder information for performing charging processing on the battery.

[0106] Step S3022: When the space status value of the memory is less than or equal to a predetermined space size value, determine that the object status information meets the object status condition.

[0107] In an embodiment of the present application, when the space status value of the memory of the second device is less than or equal to a predetermined space size value, it indicates that the size relationship between the status value of the second object of the second device and the target value is a first relationship, that is, the object status information of the second object of the second device meets the object status condition, and data cleaning of the memory of the second device is required.

[0108] In an embodiment of the present application, when the space status value of the memory is less than or equal to the predetermined space size value, processing reminder information representing the execution of data cleanup on the memory is output, and / or the second device is controlled to clean up the data on the memory.

[0109] In some embodiments, when the space status value of the memory of the second device is greater than a predetermined space size value, it indicates that the size relationship between the status value of the second object of the second device and the target value is a second relationship, that is, the object status information of the second object of the second device does not meet the object status condition, and there is no need to perform data cleaning on the memory of the second device, and there is no need to output processing reminder information for performing data cleaning on the memory.

[0110] Step S3023 : When the power consumption status value of the background application is greater than or equal to a predetermined power consumption value, determining that the object status information satisfies the object status condition.

[0111] In an embodiment of the present application, when the power consumption status value of the background application of the second device is greater than or equal to a predetermined power consumption value, it indicates that the size relationship between the status value of the second object of the second device and the target value is a first relationship, that is, the object status information of the second object of the second device meets the object status condition, and the background application of the second device needs to be closed.

[0112] In an embodiment of the present application, when the power consumption status value of the background application is greater than a predetermined power consumption value, processing reminder information indicating that a closing operation is performed on the background application is output, or the second device is controlled to close the background application.

[0113] In some embodiments, when the power consumption status value of the background application of the second device is less than a predetermined power consumption value, it indicates that the size relationship between the status value of the second object of the second device and the target value is a second relationship, that is, the object status information of the second object of the second device does not meet the object status condition, and there is no need to close the background application of the second device, and there is no need to output processing reminder information representing the execution of the closing operation for the background application.

[0114] In some embodiments, the "outputting processing reminder information indicating that the second processing is to be performed on the second object, and / or controlling the second device to perform the second processing on the second object" in step S102 may be implemented by at least one of steps S1024 to S1026:

[0115] Step S1024: outputting processing reminder information indicating that a charging process is to be performed on the battery, and / or controlling the second device to charge the battery.

[0116] In the embodiments of the present application, the second device can send the real-time power state value of its battery to the first device. When the first device is charging and determines that the power state value of the battery of the second device is low, the first device outputs the processing reminder information representing performing the charging process on the battery to remind the user to charge the second device at the same time of charging the first device.

[0117] In the embodiments of the present application, the first device can also send the charging control instruction to the second device to control the second device to charge the battery.

[0118] In step S1025, the processing reminder information representing performing the data cleaning on the memory is outputted, and / or the second device is controlled to clean the data of the memory.

[0119] In the embodiments of the present application, the second device can send the real-time space state value of its memory to the first device. When the first device cleans the data of the memory and determines that the real-time space state value of the memory of the second device is low, the first device outputs the processing reminder information representing performing the data cleaning on the memory to remind the user to clean the memory of the second device at the same time of cleaning the memory of the first device.

[0120] In the embodiments of the present application, the first device can also send the data cleaning instruction to the second device to control the second device to clean the data of its memory.

[0121] In step S1026, the processing reminder information representing performing the closing operation on the background application is outputted, or the second device is controlled to close the background application.

[0122] In the embodiments of the present application, the second device can send the real-time power consumption state value of its background application to the first device. When the first device closes the background application and determines that the real-time power consumption state value of the background application of the second device is high, the first device outputs the processing reminder information representing performing the closing operation on the background application to remind the user to close the background application of the second device at the same time of closing the background application of the first device.

[0123] In the embodiments of the present application, the first device can also send the application closing instruction to the second device to control the second device to close the background application.

[0124] In some embodiments, the second object of the second device further includes a program object; the object state information of the second object further includes version information of the program object; and the above step S102 can be implemented by step S1027.

[0125] In a case where the version information of the program object is historical version information, outputting reminder information indicating that an updated version of the program object is to be executed, and / or controlling the second device to update the program object.

[0126] Here, the program object may include an application program and a firmware program. For example, when the first device or the second device is a mobile phone, a watch, or the like, the program object may be an application program; when the first device or the second device is a headset, or the like, the program object may be a firmware program.

[0127] In an embodiment of the present application, the second device can send the version information of its own various program objects to the first device in advance. When the first device receives the user's update operation for the program object of the first device, the first device determines whether there is a program object with historical version information based on the version information of the various program objects of the second device. If so, the first device outputs a processing reminder message indicating the execution of the updated version for the program object, and / or controls the second device to update the version of the program object.

[0128] In some embodiments, when the first device receives an update operation from a user for a program object of the first device, the program type of the program object of the first device can be determined, and then the first device determines whether there is a program object corresponding to the program type that is historical version information. If so, the first device outputs processing reminder information indicating the execution of the updated version for the program object, and / or controls the second device to update the version of the program object.

[0129] In some embodiments, when the first device receives a user update operation for a program object of the first device, it may send a query request for obtaining version information of the program object to the second device, and then the first device receives version information of each program object of the second device.

[0130] In some embodiments, when a first device receives a user's update operation for a program object of the first device, it can send a query request to a second device to obtain version information of a program object of a target program type, where the target program type is the type of program object updated through the user's update operation, and then the first device receives the version information of the program object of the target program type of the second device.

[0131] In some embodiments, the second object of the second device further includes a communication connection component; the above step S102 can also be implemented through step S1028:

[0132] Step S1028: If the connection status information of the communication connection component of the second device indicates that the target communication object is not connected, output connection reminder information indicating that the communication connection component of the second device is connected to the target communication object, and / or control the communication connection component of the second device to connect to the target communication object;

[0133] The target communication object is a communication object to which the communication connection component of the first device is connected after the communication connection component of the first device performs the first processing.

[0134] Here, the target communication object includes a network and other electronic devices that can be connected to the first device for communication. For example, the network can be Wi-Fi, and the other electronic devices can be a projector, a printer, etc.

[0135] In an embodiment of the present application, the second device can send the connection status information of its own communication connection component to the first device in advance. When the first device receives the user's communication connection operation for the communication connection component of the first device (i.e., controlling the first device to communicate and connect with the target communication object through its own communication connection component), the first device determines whether the second device is connected to the target communication object based on the connection status information of the communication connection component of the second device. If not connected, the first device sends connection reminder information indicating that the communication connection component of the second device is connected to the target communication object, and / or controls the communication connection component of the second device to connect to the target communication object.

[0136] In some embodiments, when the first device receives a communication connection operation from a user on the communication connection component of the first device, it can send an inquiry request to the second device to obtain the connection status information of the communication connection component of the second device, and then the first device receives the connection status information of the communication connection component of the second device from the second device.

[0137] In some embodiments, the second object of the second device further includes application permissions; the object state information further includes permission state information; the above step S102 can also be implemented through step S1029:

[0138] Step S1029, when the permission status information of the application permission of the second device is consistent with the first status of the application permission of the first device, or the permission status information of the application permission of the second device is inconsistent with the second status of the application permission of the first device, output processing reminder information representing the change status of the application permission of the second device, or control the second device to change the status of the application permission of the second device.

[0139] Here, the application corresponding to the application permission of the second device is consistent with the application type corresponding to the application permission of the first device. For example, both can be application permissions for a camera or application permissions for a voice application.

[0140] In an embodiment of the present application, when the first device receives a status change operation of the user for the application permission of the first device (for example, turning off the application permission of the camera), it can determine whether the permission status information of the application permission of the second device is consistent with the first status of the application permission of the first device. If they are consistent (for example, the application permission of the camera of the second device and the application permission of the camera of the first device are both in the on state), the first device outputs a processing reminder message representing the execution of the change status of the application permission of the second device, or controls the second device to execute the change status of the application permission of the second device. Alternatively, it is determined whether the permission status information of the application permission of the second device is consistent with the second status of the application permission of the first device. If they are inconsistent (for example, the application permission of the camera of the second device is in the on state, and the application permission of the first device after the status change operation is in the off state), the first device outputs a processing reminder message representing the execution of the change status of the application permission of the second device, or controls the second device to execute the change status of the application permission of the second device.

[0141] The following describes the application of the reminder method provided in the embodiment of the present application in actual scenarios:

[0142] At present, for people who use many mobile devices, such as watches, bracelets, headphones, mobile phones, and tablets, they need to be able to charge the devices in time to avoid running out of power and being unable to use them.

[0143] In order to solve the above technical problems, related technologies have been used to remind users to charge their devices when their battery is low. However, the problem with this solution is that after the reminder, users may not have time to handle it and may forget to charge their devices.

[0144] To address the above-mentioned issues and the shortcomings of existing solutions, the present invention proposes a solution that utilizes a communication mechanism between multiple devices. When a user is charging a device, if the device detects that other devices are also low on battery and need to be charged, it will prompt the user on the interface to charge the other low-battery devices as well. This way, once the user has initiated charging for a device, they can also charge other low-battery devices, thus reducing the awkward situation where other devices become unusable at some point in the future due to low battery.

[0145] In the embodiment of the present application, when a device is in a low-battery state, in addition to reminding the user to charge the device, it also sends its low-battery state to other devices with which it has a communication mechanism. For example:

[0146] When the watch battery is low, the watch can send its low battery status to the paired mobile phone through the Bluetooth channel; or when the mobile phone battery is low, the mobile phone can send its low battery status to the paired watch through the Bluetooth channel.

[0147] When the battery of the headset is low, the headset can send its low-battery status to the paired mobile phone through the Bluetooth channel; or when the battery of the mobile phone is low, the mobile phone can send its low-battery status to the paired headset through the Bluetooth channel.

[0148] When the tablet battery is low, the tablet can send its low battery status to the connected mobile phone through the Bluetooth channel; or when the mobile phone battery is low, the mobile phone can send its low battery status to the connected tablet through the Bluetooth channel.

[0149] Furthermore, with the phone acting as an intermediary, low-battery information from any two devices can be transmitted to each other. For example, when a phone receives a low-battery notification from a watch, it can send this information to the earphones. Then, when the user charges any of the devices, that device will notify the user in some way that the other devices are also low on battery and need to be charged.

[0150] For example, the watch notifies the mobile phone of its low battery status via Bluetooth. Then, when the user is charging the mobile phone, the mobile phone displays the charging interface on the screen to remind the user, "Your watch is in low battery status, please charge as soon as possible."

[0151] The phone notifies the watch of its low battery status via Bluetooth. When the user is charging the watch, the watch charging interface will also notify the user that the phone needs to be charged.

[0152] The low-battery status of the watch and earphones is known to each other through the mobile phone as an intermediary. Therefore, when charging the watch, if the current battery of the earphones is low, a reminder to charge the earphones will also be displayed on the watch charging interface.

[0153] In some embodiments, when the user is charging the headphone case, the headset and headphone case typically lack screens, so the headset will use audio to remind the user to charge other devices with low batteries. For example, if the headset case receives a message that a watch needs to be charged, it will output a voice reminder message like: "Watch battery is low, please charge immediately." The voice file of this voice reminder message (including voice reminders for various devices such as watches, mobile phones, tablets, and laptops) can be stored in the headset case and played when needed.

[0154] In some embodiments, in an updating scenario, when the user is updating the system of the mobile phone, the mobile phone detects that the earphone firmware is out of date, and the mobile phone prompts: "There is a new version of the earphone firmware, do you want to update it together?" When the user is updating the application on the tablet, the tablet prompts: "Your watch also has two applications to be updated". In this way, the inconsistency of device updates can be reduced, the coherence of the ecological experience can be improved, and the operation burden of the user's repeated manual updates in the future can be reduced.

[0155] In some embodiments, in a cleaning scenario, when the user is cleaning the photos or system garbage of the mobile phone, the mobile phone prompts: "Your tablet is also running out of space, do you want to clean it together?" When the user is uninstalling the redundant application of the mobile phone, the mobile phone prompts: "There are also long-unused applications on your watch, do you want to uninstall them together". In this way, the isolated cleaning work can be reduced, and the overall device running efficiency can be improved

[0156] In some embodiments, in a permission / privacy management scenario, when the user closes the microphone access permission on the mobile phone, the mobile phone prompts: "You can also close the same permission on your watch / tablet". When the user closes the voice assistant wake-up permission on the earphone, the earphone suggests: "Do you want to close the assistant permission on the mobile phone together?". In this way, the user's overall control over privacy security can be improved.

[0157] In some embodiments, in a pairing / connection scenario, when the user connects the mobile phone to Wi-Fi at home, the mobile phone prompts: "Do you want to let the watch / earphone also join the same network?" When the user connects the projector to the personal computer in the meeting room, the personal computer prompts: "Do you want to let the tablet also connect to backup the presentation?".

[0158] In some embodiments, in a power saving / performance optimization scenario, when the user closes the background high-power-consumption application of the mobile phone, the mobile phone prompts: "The same application on the tablet can also limit the background activity".

[0159] Figure 4 A component structure schematic diagram of a reminding device provided in an embodiment of the present application is shown in Figure 4 The reminding device 400 includes an obtaining module 401 and an output module 402.

[0160] The obtaining module 401 is configured to, in response to a target interaction operation on a first object in a first device, obtain object state information of a second object in a second device.

[0161] The output module 402 is configured to, if the object state information meets an object state condition, output processing reminding information representing that a second processing is performed on the second object, and / or control the second device to perform the second processing on the second object.

[0162] The second processing corresponds to the first processing, and the first processing is a processing executed on the first object triggered by the target interaction operation.

[0163] In some embodiments, the object state information satisfies the object state condition, indicating that the state of the second object is consistent with the first state of the first object; the first state is the state of the first object before the first processing is performed; or the object state information satisfies the object state condition, indicating that the state of the second object is inconsistent with the second state of the first object; the second state is the state of the first object after the first processing is performed.

[0164] In some embodiments, the output module 402 is used for at least one of the following: outputting processing reminder information for performing the second processing on the second object on the first device; outputting processing reminder information for performing the second processing on the second object on the second device; and outputting processing reminder information for performing the second processing on the third device.

[0165] In some embodiments, the acquisition module 401 is configured to send a query request to the second device or the third device; receive feedback information sent by the second device or the third device; and determine object state information of a second object in the second device based on the feedback information.

[0166] In some embodiments, the object status information includes a status value, and the acquisition module 401 is used to obtain the status value corresponding to the second object; the reminder device 400 includes a determination module; the determination module is used to determine that if the size relationship between the status value and the target value is a first relationship, the object status information meets the object status condition; if the size relationship between the status value and the target value is a second relationship, the object status information does not meet the object status condition; wherein, the first relationship is different from the second relationship.

[0167] In some embodiments, the second object of the second device includes at least one of the following: a battery, a memory, and a background application; the status value corresponding to the object status information includes at least one of the following: the power status value of the battery, the space status value of the memory, and the power consumption status value of the background application; the determination module is used for at least one of the following: when the power status value of the battery is less than or equal to a predetermined power value, determining that the object status information meets the object status condition; when the space status value of the memory is less than or equal to a predetermined space size value, determining that the object status information meets the object status condition; when the power consumption status value of the background application is greater than or equal to a predetermined power consumption value, determining that the object status information meets the object status condition.

[0168] In some embodiments, the output module 402 is used for at least one of the following: outputting processing reminder information representing the execution of charging processing for the battery, and / or controlling the second device to charge the battery; outputting processing reminder information representing the execution of data cleanup for the memory, and / or controlling the second device to clean up data for the memory; outputting processing reminder information representing the execution of a closing operation for the background application, or controlling the second device to close the background application.

[0169] In some embodiments, the second object of the second device also includes a program object; the object status information of the second object also includes version information of the program object; the output module 402 is used to output processing reminder information representing the execution of an updated version of the program object when the version information of the program object is historical version information, and / or control the second device to update the version of the program object.

[0170] In some embodiments, the second object of the second device also includes a communication connection component; the object status information of the second object also includes connection status information of the communication connection component; the output module 402 is used to output connection reminder information indicating that the communication connection component of the second device is connected to the target communication object when the connection status information of the communication connection component of the second device indicates that the target communication object is not connected, and / or control the communication connection component of the second device to connect to the target communication object; wherein, the target communication object is the communication object to which the communication connection component of the first device is connected after the first processing is performed on the communication connection component of the first device.

[0171] The description of the above device embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided in the embodiments of the present application can be used to perform the methods described in the above method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0172] It should be noted that, in the embodiment of the present application, if the above-mentioned reminder method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for making a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the methods of each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific hardware, software or firmware, or any combination of hardware, software and firmware.

[0173] An embodiment of the present application provides a computer device including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.

[0174] The present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements some or all of the steps in the above method. The computer-readable storage medium may be transient or non-transient.

[0175] An embodiment of the present application provides a computer program, including computer-readable code. When the computer-readable code runs in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.

[0176] The present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, some or all of the steps in the above method are implemented. The computer program product can be implemented in hardware, software, or a combination thereof. In some embodiments, the computer program product is embodied as a computer storage medium. In other embodiments, the computer program product is embodied as a software product, such as a software development kit (SDK).

[0177] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between the various embodiments, and their similarities or similarities can be referenced to each other. The descriptions of the above device, storage medium, computer program, and computer program product embodiments are similar to the descriptions of the above method embodiments and have similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the description of the method embodiments of this application for understanding.

[0178] Figure 5 This is a hardware entity diagram of an electronic device in an embodiment of the present application, such as Figure 5 As shown, the hardware entity of the electronic device 500 includes: a processor 501, a communication interface 502 and a memory 503, wherein:

[0179] The processor 501 generally controls the overall operation of the electronic device 500 , and the overall operation may be to implement the reminder method provided in the embodiment of the present application.

[0180] The communication interface 502 enables the electronic device 500 to communicate with other terminals or servers through a network.

[0181] The memory 503 is configured to store instructions and applications executable by the processor 501, and can also cache data to be processed or processed by the processor 501 and various modules in the electronic device 500 (for example, image data, audio data, voice communication data, and video communication data). This can be implemented using flash memory (FLASH) or random access memory (RAM). Data can be transmitted between the processor 501, the communication interface 502, and the memory 503 via a bus 504.

[0182] An embodiment of the present application provides a computer storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the steps of the reminder method of any of the above embodiments.

[0183] It should be noted that the above description of the storage medium and device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of the present application, please refer to the description of the method embodiments for understanding.

[0184] The processor can be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, or a microprocessor. It can be understood that the electronic device implementing the functions of the processor can also be other devices, and the embodiments of the present application are not limited in this regard.

[0185] The computer storage medium / memory can be a Read Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Ferromagnetic Random Access Memory (FRAM), a Flash Memory, a magnetic surface memory, an optical disc, a Compact Disc Read-Only Memory (CD-ROM), or the like. It can also be various terminals including one or any combination of the above memories, such as a mobile phone, a computer, a tablet device, a personal digital assistant, and the like.

[0186] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned steps / processes does not mean the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments.

[0187] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0188] The above are only implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the protection scope of the present application.

Claims

1. A reminder method, comprising: In response to a target interaction operation on the first object in the first device, obtaining object state information of the second object in the second device; If the object state information satisfies an object state condition, outputting processing reminder information indicating that a second process is to be performed on the second object, and / or controlling the second device to perform the second process on the second object; The second processing corresponds to the first processing, and the first processing is a processing executed on the first object triggered by the target interaction operation.

2. The method according to claim 1, The object state information satisfies the object state condition, indicating that the state of the second object is consistent with the first state of the first object; the first state is the state of the first object before the first processing is performed; or The object state information meeting the object state condition indicates that the state of the second object is inconsistent with the second state of the first object; the second state is the state of the first object after executing the first processing.

3. The method according to claim 1, wherein the outputting of the processing reminder information indicating the execution of the second processing on the second object comprises at least one of the following: outputting, on the first device, processing reminder information for executing a second process on the second object; outputting, on the second device, processing reminder information for executing a second process on the second object; Outputting, on the third device, processing reminder information for executing the second processing on the second object.

4. The method according to claim 3, wherein obtaining the object state information of the second object in the second device comprises: sending a query request to the second device or the third device; receiving feedback information sent by the second device or the third device; Based on the feedback information, object state information of a second object in the second device is determined.

5. The method according to claim 1, wherein the object status information includes a status value, and the method further comprises: Obtaining a status value corresponding to the second object; If the magnitude relationship between the state value and the target value is a first relationship, the object state information satisfies the object state condition; If the magnitude relationship between the state value and the target value is the second relationship, the object state information does not meet the object state condition; The first relationship is different from the second relationship.

6. The method according to claim 5, wherein the second object of the second device comprises at least one of the following: a battery, a memory, and a background application; and the status value corresponding to the object status information comprises at least one of the following: a power status value of the battery, a space status value of the memory, and a power consumption status value of the background application; If the magnitude relationship between the state value and the target value is a first relationship, the object state information satisfies the object state condition, including at least one of the following: When the battery state value is less than or equal to a predetermined power value, determining that the object state information satisfies the object state condition; When the space status value of the memory is less than or equal to the predetermined space size value, determining that the object status information satisfies the object status condition; In a case where the power consumption status value of the background application is greater than or equal to a predetermined power consumption value, it is determined that the object status information meets the object status condition.

7. The method according to claim 6, wherein outputting processing reminder information indicating that a second processing corresponding to the first processing is to be performed on the second object, and / or controlling the second device to perform the second processing on the second object, comprises at least one of the following: outputting processing reminder information indicating that a charging process is to be performed on the battery, and / or controlling the second device to charge the battery; outputting processing reminder information indicating that data cleanup is to be performed on the memory, and / or controlling the second device to clean up data on the memory; Outputting processing reminder information indicating that a closing operation is executed on the background application, or controlling the second device to close the background application.

8. The method according to any one of claims 1 to 6, wherein the second object of the second device further comprises a program object; and the object state information of the second object further comprises version information of the program object; If the object state information satisfies the object state condition, outputting processing reminder information indicating that a second process corresponding to the first process is to be performed on the second object, and / or controlling the second device to perform the second process on the second object, includes: In a case where the version information of the program object is historical version information, outputting reminder information indicating that an updated version is to be executed on the program object, and / or controlling the second device to update the version of the program object.

9. The method according to any one of claims 1 to 6, wherein the second object of the second device further comprises a communication connection component; and the object state information of the second object further comprises connection state information of the communication connection component; If the object state information satisfies the object state condition, outputting processing reminder information indicating that a second process corresponding to the first process is to be performed on the second object, and / or controlling the second device to perform the second process on the second object, includes: When the connection status information of the communication connection component of the second device indicates that the target communication object is not connected, outputting connection reminder information indicating that the communication connection component of the second device is connected to the target communication object, and / or controlling the communication connection component of the second device to connect to the target communication object; The target communication object is a communication object to which the communication connection component of the first device is connected after the communication connection component of the first device performs the first processing.

10. A reminder device, comprising: an acquisition module, configured to acquire object state information of a second object in a second device in response to a target interaction operation on a first object in a first device; an output module, configured to output processing reminder information indicating that a second process is to be performed on the second object if the object state information satisfies an object state condition, and / or control the second device to perform the second process on the second object; The second processing corresponds to the first processing, and the first processing is a processing executed on the first object triggered by the target interaction operation.

Images