Electronic device reminding method and electronic device

Abstract

This disclosure provides an electronic device reminder method and an electronic device, relating to the field of electronic device technology. The electronic device reminder method includes: in response to a first interface of the electronic device being connected to a second interface of an external device, determining an interaction mode between the electronic device and the external device; the external device being able to provide power to the electronic device through the second interface; in response to the electronic device being in a first state, issuing a prompt message corresponding to the interaction mode; the first state indicating an abnormal interaction between the electronic device and the external device; the prompt messages corresponding to different interaction modes may be the same or different.

Description

Technical Field

[0001] This disclosure relates to the field of electronic device technology, and in particular to an electronic device reminder method and an electronic device. Background Technology

[0002] During interactions such as charging or data transfer with electronic devices through their interfaces, users may not be able to detect abnormalities in a timely manner, which could affect their subsequent use of the electronic devices. Summary of the Invention

[0003] This disclosure provides a method for reminding electronic devices and an electronic device to at least solve the above-mentioned technical problems existing in the prior art.

[0004] According to a first aspect of this disclosure, an electronic device reminder method is provided, comprising:

[0005] In response to the connection between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined; the external device is able to provide power to the electronic device through the second interface. In response to the electronic device being in a first state, a prompt message corresponding to the interaction mode is issued; the first state indicates an abnormal interaction between the electronic device and the external device; the prompt messages corresponding to different interaction modes may be the same or different.

[0006] In one possible implementation, the interaction mode is a charging mode, and the response to the electronic device being in a first state includes: In response to the fact that no charging start event of the electronic device is detected during a first time period after the connection is established between the first interface and the second interface; and / or, In response to the detection of a charging stop event that meets a first condition; the first condition indicates that the electronic device is in an unused state during a second period of time in which the charging stop event occurs.

[0007] In one possible implementation, detecting the charging start event and charging stop event of the electronic device includes: The charging status signal received by the broadcast receiver of the electronic device is monitored; the charging status signal is generated based on the changes in the electrical signal of the first interface. In response to the charging status signal indicating the start of charging, it is determined that a charging start event of the electronic device has been detected; In response to the charging status signal indicating that charging has stopped, it is determined that a charging stop event of the electronic device has been detected.

[0008] In one possible implementation, the interaction mode is a data transmission mode, and the response to the electronic device being in a first state includes: In response to the fact that no transmission start event is detected between the electronic device and the external device during a third time period after the connection is established between the first interface and the second interface; and / or, In response to the detection of a transmission stop event that meets a second condition; the second condition indicates that the electronic device is in an unused state during the fourth period in which the transmission stop event occurs.

[0009] In one possible implementation, detecting the transmission start event and the transmission stop event includes: In response to detecting that the data interaction protocol state between the electronic device and the external device changes to a data transmission state, it is determined that the transmission start event has been detected; In response to detecting at least one of the following: the number of transmission retries between the electronic device and the external device is greater than a retry threshold, the transmission response duration is greater than a duration threshold, the number of packet losses is greater than a packet loss threshold, and the data interaction protocol state becomes a data interaction disconnection, the transmission stop event is determined to be detected.

[0010] In one possible implementation, the electronic device is in an unused state, including at least one of the following: The electronic device did not detect any input event; The pose change of the electronic device is less than a first threshold; The load change rate of the electronic device is less than the second threshold.

[0011] In one possible implementation, issuing the prompt information corresponding to the interaction mode includes: Based on at least one of the following: interaction anomaly identifier between the electronic device and the external device, interaction anomaly cause, current interaction progress, and interaction anomaly handling suggestion, generate and issue a prompt message corresponding to the interaction mode.

[0012] In one possible implementation, issuing the prompt information corresponding to the interaction mode includes: The prompt message is issued based on at least one of an audio signal, a vibration signal, and a display signal; and / or, Other devices that establish a communication connection with the electronic device may issue the prompt message based on at least one of an audio signal, a vibration signal, and a display signal.

[0013] In one possible implementation, the electronic device reminder method further includes: In response to the electronic device being in the second state, if the third condition is met, interaction progress information between the electronic device and the external device is sent out; the second state indicates that the interaction between the electronic device and the external device is normal. The third condition includes the interaction progress between the electronic device and the external device reaching a target progress threshold.

[0014] According to a second aspect of this disclosure, an electronic device is provided, comprising: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: In response to the connection between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined; the external device is able to provide power to the electronic device through the second interface. In response to the electronic device being in a first state, a prompt message corresponding to the interaction mode is issued; the first state indicates an abnormal interaction between the electronic device and the external device; the prompt messages corresponding to different interaction modes may be the same or different.

[0015] According to a third aspect of this disclosure, a non-transitory computer-readable storage medium is provided storing computer instructions for causing the computer to perform the methods described in this disclosure.

[0016] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0017] The above and other objects, features, and advantages of this disclosure will become readily apparent from the following detailed description of exemplary embodiments, taken in conjunction with the accompanying drawings. Several embodiments of this disclosure are illustrated in the drawings by way of example and not limitation, in which: In the accompanying drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

[0018] Figure 1 This illustration shows a flowchart of an electronic device reminder method according to an embodiment of the present disclosure. Figure 1 ; Figure 2 This illustration shows a flowchart of an electronic device reminder method according to an embodiment of the present disclosure. Figure 2 ; Figure 3 This illustration shows a flowchart of an electronic device reminder method according to an embodiment of the present disclosure. Figure 3 ; Figure 4 A schematic diagram of the composition structure of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0019] To make the objectives, features, and advantages of this disclosure more apparent and understandable, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0020] Figure 1 This illustration shows a flowchart of an electronic device reminder method according to an embodiment of the present disclosure. Figure 1 ,like Figure 1 As shown, an electronic device reminder method includes: Step S101: In response to the connection between the first interface of the electronic device and the second interface of the external device, determine the interaction mode between the electronic device and the external device.

[0021] In this embodiment, the electronic device is any device with interface connection capabilities, such as a smartphone, tablet, laptop, or e-reader. The first interface is the interface on the electronic device used to establish a physical connection with external devices, such as common connection interfaces like USB Type-C, Lightning, and Micro-USB, which have the hardware link foundation for power supply and data transmission. The external device is a device that can connect to the electronic device via an interface and provide power to the electronic device, including but not limited to charging adapters, computers with charging capabilities, power banks, and docking stations. The second interface is an adapter interface on the external device that matches the first interface of the electronic device. This second interface integrates a power supply line, which can transmit power from the external device to the electronic device via a cable, thus providing power to the electronic device.

[0022] In this embodiment, it is necessary to detect the connection status between the first interface of the electronic device and the second interface of the external device. When the first interface of the electronic device (e.g., a USB Type-C interface, Lightning interface, or Micro-USB interface on a mobile phone) and the second interface of the external device (e.g., a USB male connector on a charger or a USB male connector on a data cable) establish a physical connection, the electronic device detects that the first interface and the second interface have successfully established a connection. In one example, the connection status between the first interface and the second interface can be determined by pressure detection. That is, a pressure detection device is installed on the inner wall of the socket (female connector) of the first interface of the electronic device. When the second interface of the external device is inserted into the first interface of the electronic device through a plug, the plug will exert pressure on the inner wall of the socket. After the pressure detection device detects the change in pressure value, it can determine that the first interface and the second interface have completed a physical connection. In another example, the connection status between the first and second interfaces can also be determined by capacitance detection. That is, the CC signal in the USB signal of the first interface of the electronic device is connected to the capsensor capacitance detection channel. When no plug is inserted, the capsensor detects the basic capacitance value (e.g., 10pF). When the plug of the second interface is inserted, the CC signal line is extended, and the capacitance value formed by it and its surroundings will increase (e.g., 12pF). By recognizing the change in capacitance value, the electronic device can determine that the first and second interfaces have completed the physical connection.

[0023] In this embodiment, if a connection is established between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined. The interaction mode can be determined based on the hardware configuration of the interface, the device type of the external device, and the negotiation results of the communication protocol between the two parties. Since the second interface of the external device has the capability to provide power to the electronic device, the interaction mode at least includes a charging mode, where the external device only transmits electrical energy to the electronic device through the second interface to achieve charging operation. In addition, the interaction mode may also include a data transmission mode (where the external device and the electronic device only send and receive data, such as file transfer or data synchronization), a composite mode combining the charging mode and the data transmission mode (where the external device simultaneously transmits electrical energy and data to the electronic device), etc.

[0024] In one example, when a user connects the USB port (second port) of a charger to the Type-C port (first port) of a mobile phone via a charging cable, the mobile phone recognizes the physical connection of the port through capacitive sensing and, through protocol negotiation, identifies the external device as a charger with only power supply capability, thus determining the interaction mode as charging mode. When the user connects the USB port (second port) of a computer to the Type-C port (first port) of a tablet via a data cable, the tablet detects the physical connection of the port and recognizes that the computer has both power supply and data transfer capabilities. Both parties negotiate to perform charging and file transfer simultaneously, thus determining the interaction mode as a composite mode combining charging mode and data transfer mode.

[0025] In step S102, in response to the electronic device being in the first state, a prompt message corresponding to the interaction mode is issued.

[0026] In this embodiment, the first state is when, after the electronic device establishes a physical connection with the external device, it fails to perform the expected functions of the corresponding interaction mode, i.e., the interaction process between the two is abnormal. That is, although the first interface and the second interface have established a physical connection, the expected interaction (charging or data transmission, etc.) fails to proceed normally or is unexpectedly interrupted midway. In one example, specific situations of interaction abnormality include, but are not limited to: in charging mode, charging fails to start as expected (e.g., no power in the socket, poor plug contact) or charging unexpectedly stops (e.g., the plug becomes loose or power is interrupted); in data transmission mode, data transmission fails to start as expected or data transmission is unexpectedly interrupted, etc.

[0027] In this embodiment, the prompt information corresponding to the interaction mode refers to the prompt content that matches the interaction mode of the electronic device and the external device. This prompt information is used to provide the user with the core information of the current interaction abnormality, and the prompt information corresponding to different interaction modes can be set to be the same or different according to actual needs. If set to be different, the prompt information will reflect the characteristics of the corresponding interaction mode and accurately point to the interaction abnormality in that mode. For example, for the charging mode, the corresponding prompt information can be a voice-synthesized prompt message "Charging unexpectedly stopped, please check the plug"; for the data transmission mode, the corresponding prompt information can be a prompt box displaying "Transmission unexpectedly stopped" on the screen of the electronic device, plus a flashing breathing light. If set to be the same, a general prompt content can be used to provide feedback on the interaction abnormality without distinguishing between specific interaction modes. For example, for the charging mode and the data transmission mode, the corresponding prompt information is either the vibration of the electronic device or a voice-synthesized prompt message "Device interaction abnormality, please check the connection".

[0028] This disclosure achieves accurate monitoring and targeted alerts for abnormal states during the interaction between electronic devices and external devices by first identifying the physical connection and corresponding interaction mode between the electronic device and the external device, and then issuing a matching prompt message in the first state of interaction abnormality. Specifically, using the physical connection of the interface as the trigger condition ensures the timeliness of subsequent interaction mode determination and abnormality monitoring, avoiding invalid monitoring when there is no physical connection and reducing the hardware resource consumption of the electronic device. Matching the prompt message to the interaction mode ensures that the prompt content aligns with the actual interaction scenario, allowing users to quickly understand the type of interaction abnormality without having to manually check the interaction mode. This improves the accuracy and practicality of abnormality alerts and effectively overcomes the shortcomings of traditional methods where users cannot promptly perceive device interaction abnormalities.

[0029] Figure 2 This illustration shows a flowchart of an electronic device reminder method according to an embodiment of the present disclosure. Figure 2 ,like Figure 2 As shown, an electronic device reminder method includes: Step S201: In response to the connection between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined to be the charging mode.

[0030] In this embodiment, the interaction mode can be a charging mode, that is, after the electronic device establishes a physical connection with the external device, the interaction function between the two is determined to be that the external device transmits electrical energy to the electronic device through the second interface, thereby replenishing the battery of the electronic device. The other specific implementation details of step S201 are similar to those of step S101, and will not be repeated here.

[0031] Step S202: In response to the fact that no charging start event of the electronic device is detected within a first time period after the connection between the first interface and the second interface is established; and / or, in response to the detection of a charging stop event that meets the first condition, a prompt message corresponding to the charging mode is issued.

[0032] In this embodiment, after the first interface of the electronic device establishes a physical connection with the second interface of the external device, the electronic device starts a timer for timing. The duration of the first time period can be set according to the actual application scenario, such as 30 seconds, 1 minute, 2 minutes, or 5 minutes, etc. In this embodiment, it is preferably set to 1 minute. During the first time period after the first interface and the second interface are connected, the electronic device continuously monitors whether a charging start event occurs. The charging start event is a landmark event that the electronic device recognizes itself to have entered a normal charging state. It is a charging start state jointly determined by the electronic device through hardware monitoring and software recognition. It can be manifested as the battery management system of the electronic device detecting a stable input current and voltage, and the charging protocol completing negotiation, and the electronic device switching from a discharging state or standby state to a charging state. If the battery management system, charging monitoring module, etc. of the electronic device do not recognize the above-mentioned charging start event within the timing period of the first time period, that is, although the electronic device has completed the physical connection with the interface of the external device, it has not actually entered a normal charging state. This includes charging start failures caused by reasons such as no power in the socket, loose charging cable, incompatible charging protocol, or power supply failure of the external device. In this case, it can be determined that the electronic device is in the first state.

[0033] In this embodiment, a charging stop event is an event that occurs when an electronic device, after entering a normal charging state, detects the termination of its charging state. Specifically, the electronic device's battery management system and charging monitoring module detect an interruption in input current and voltage, disconnect the charging protocol connection, and switch from a charging state to a non-charging state. After recognizing a charging stop event, the electronic device needs to further determine whether the charging stop event meets a preset first condition. Only when the first condition is met will the charging stop event be used as the basis for determining the first state in the charging mode. If the first condition is not met, the charging stop event is considered a normal situation such as user-initiated operation and is not determined as an abnormal charging interaction. The first condition indicates that the electronic device is in an unused state during a second time period, including the time of the charging stop event. For example, the electronic device determines through its input detection, motion detection, and other modules that it has not been actively operated by the user and that there has been no change in the device state due to user operation. The second time period includes a first sub-period (e.g., 30 seconds) before the charging stop event and a second sub-period (e.g., 1 minute) after the charging stop event. In other words, if the electronic device is in an unused state for a period before and after the charging stop event, it can be determined that the electronic device is in the first state.

[0034] In this disclosure, the problem of abnormal charging start when the plug is plugged in but charging has not actually started is accurately identified by the criterion of "no charging start event detected within the first time period after interface connection". This solves the pain point in the prior art where users do not notice whether charging has started after plugging in the charging cable. On the other hand, the criterion of "charging stop event that meets the first condition" effectively distinguishes between accidental charging stop and user-initiated charging stop, accurately identifying abnormal charging interruptions caused by loose plugs, accidental unplugging by others, etc., and avoiding normal charging stop operations being misjudged as abnormal.

[0035] In another embodiment, detecting charging start events and charging stop events of the electronic device includes: The charging status signal is received by the broadcast receiver of the electronic device; the charging status signal is generated based on the changes in the electrical signal of the first interface. In response to a charging status signal indicating the start of charging, it is determined that a charging start event of the electronic device has been detected. If a charging status signal indicates that charging has stopped, then a charging stop event of the electronic device is detected.

[0036] In this embodiment, the broadcast receiver is a dedicated component in the electronic device used to monitor system-level state changes. It needs to be pre-registered in the electronic device's system configuration file, specifying that it monitors charging status signals. This broadcast receiver operates independently of other applications on the electronic device and can receive charging status signals sent from the system's underlying layer in real time. It features low latency and high real-time performance, and can still function normally even when the electronic device is locked or running in the background. The electronic device's processor configures a dedicated listening thread for the broadcast receiver. This thread is continuously in a waiting state. When the broadcast receiver receives a charging status signal sent by the system, it immediately transmits the signal to the electronic device's processor for parsing, allowing the processor to obtain the charging status signal. The charging status signal is a digital signal generated by the electronic device's system layer to characterize changes in charging status. This signal is a standardized system command signal (such as the ACTION_POWER_CONNECTED and ACTION_POWER_DISCONNECTED signals in Android), containing status indicators for charging start and stop, which can be directly recognized and received by the broadcast receiver. The charging status signal is generated based on the changes in the electrical signal of the first interface. The first interface of the electronic device integrates an electrical signal detection module, which can monitor changes in electrical signals such as current, voltage, and pin continuity in the interface in real time. When the first interface is connected to the second interface of an external device, if the external device is supplying power normally, the first interface will detect a stable input current and voltage (the electrical signal changes from zero to positive). Based on this change in electrical signal, the underlying system of the electronic device automatically generates the charging status signal corresponding to the start of charging. When the electronic device is in the charging state, if the input current and voltage of the first interface are suddenly interrupted (the electrical signal changes from positive to negative), the underlying system automatically generates the charging status signal corresponding to the stop of charging based on this change in electrical signal.

[0037] In this embodiment, the charging status signal indicating the start of charging refers to the charging status signal received by the broadcast receiver containing a preset "charging start" status identifier. This identifier is a standardized identifier defined at the system's underlying level. The identifier format may differ between different systems, but all identifiers are unique and used to represent the state change indicating the start of charging. If a charging status signal indicating the start of charging is detected, it is determined that a charging start event of the electronic device has been detected, and information such as the occurrence time and signal characteristics of the charging start event is recorded in the system log of the electronic device.

[0038] In this embodiment, the charging status signal indicating charging stop refers to the fact that the charging status signal received by the broadcast receiver includes a preset "charging stop" status identifier. This identifier, along with the "charging start" identifier, is a standardized status identifier that is independent of each other. It is uniformly defined by the underlying layer of the electronic device system and has unique directional characteristics, used to represent the state change of charging termination. If a charging status signal indicating charging stop is detected, it is determined that a charging stop event of the electronic device has been detected, and information such as the occurrence time of the event and the reason for the electrical signal interruption (if detectable) is recorded in the system log.

[0039] In one example, listening to the charging status signal received by the broadcast receiver of an electronic device can be achieved based on the following two code snippets: First section: Creating a BroadcastReceiver public class PowerConnectionReceiver extends BroadcastReceiver { @Override public void onReceive(Context context, Intent intent) { if (Intent.ACTION_POWER_CONNECTED.equals(intent.getAction())) { / / Charging begins Log.d("PowerReceiver", "Starting charging"); Toast.makeText(context, "Start charging", Toast.LENGTH_SHORT).show(); } } } Second section: Registering broadcast receivers in AndroidManifest.xml <receiver android:name=".PowerConnectionReceiver"> <intent-filter> <action android:name="android.intent.action.ACTION_POWER_CONNECTED" / > < / intent-filter> < / receiver> The code above is for detecting the charging start event. The code for detecting the charging stop event is similar; you only need to listen to ACTION_POWER_DISCONNECTED, so it will not be described in detail here.

[0040] In this disclosure, on the one hand, the generation of the charging status signal is bound to the actual electrical signal change of the first interface to ensure that the signal generation is completely synchronized with the hardware charging status, thereby avoiding the generation of false charging status signals from the source and improving the accuracy of event detection; on the other hand, a system-level broadcast receiver is used as the listening carrier for the charging status signal. By utilizing its low latency and continuous background operation characteristics, real-time monitoring of charging events is realized. Even if the electronic device is in a locked screen or background running state, it can still accurately identify charging start and stop events, solving the problem of background monitoring failure in traditional detection methods.

[0041] Figure 3 This illustration shows a flowchart of an electronic device reminder method according to an embodiment of the present disclosure. Figure 3 ,like Figure 3 As shown, an electronic device reminder method includes: Step S301: In response to the connection between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined to be a data transmission mode.

[0042] In this embodiment, the interaction mode can be a data transmission mode. That is, after the electronic device establishes a physical connection with the external device, the interaction function between the two is determined to be data transmission, synchronization, reading, and writing operations through the first and second interfaces. In this mode, the core interaction between the external device and the electronic device is data-level transmission. The external device may still have the basic capability to provide power to the electronic device, but in this interaction mode, the focus is on the execution and status monitoring of data transmission functions. Power supply can exist as an auxiliary function and does not affect the determination of the data transmission mode and anomaly detection. Other specific implementation details of step S301 are similar to those of step S101 and will not be repeated here.

[0043] In step S302, in response to the fact that no transmission start event is detected between the electronic device and the external device during the third time period after the connection is established between the first interface and the second interface; and / or, in response to the detection of a transmission stop event that meets the second condition, a prompt message corresponding to the data transmission mode is issued.

[0044] In this embodiment, after the first interface of the electronic device establishes a physical connection with the second interface of the external device, the electronic device starts a timer for timing. The third time period is a fixed time threshold preset by the electronic device for the data transmission mode. The setting of this threshold needs to be determined by combining the negotiation duration of different data interaction protocols and the normal time consumption for establishing a data link between devices. In one example, the third time period can be set to 30 seconds, 1 minute, 90 seconds, etc. Different third time period thresholds can be flexibly adapted for electronic devices with different transmission protocols such as USB 2.0 and USB 3.0. In this embodiment, it is preferably set to 1 minute. During the third time period after the first interface and the second interface establish a connection, the electronic device continuously monitors the transmission start event between the electronic device and the external device. The transmission start event is a landmark event in which the electronic device recognizes that a valid data link has been established between itself and the external device and has started to send and receive data normally. It is a data transmission start state jointly determined by the electronic device through software protocol monitoring and hardware data path detection. It can be manifested as the completion of handshake negotiation of the data interaction protocol between the devices, the physical link of data transmission being established, and the electronic device detecting the successful transmission and reception of the first valid data frame with the external device. If, during the timing period of the third time slot, the data transmission monitoring module and protocol parsing module of the electronic device fail to recognize the aforementioned transmission start event, that is, although the electronic device has completed the physical connection with the external device, it has not actually established a valid data link or started normal data transmission. This failure to start data transmission may be due to reasons such as incompatible data interaction protocols, poor contact of interface pins leading to a disconnection of the data path, or the external device not having data transmission permission. In this case, the electronic device can be determined to be in the first state.

[0045] In this embodiment, a transmission stop event is an event that occurs when an electronic device, after establishing a valid data link with an external device and entering a normal data transmission state, detects the termination of the data transmission process. Specifically, the electronic device's data transmission monitoring module and protocol parsing module detect a disconnection of the data link, interruption of data frame transmission and reception, or failure of the data interaction protocol handshake, switching from a normal data transmission state to a non-transmission state. After recognizing a transmission stop event, the electronic device further needs to determine whether the transmission stop event meets a preset second condition. Only when the second condition is met will the transmission stop event serve as the basis for determining the first state under the data transmission mode. If the second condition is not met, the transmission stop event is considered a normal situation such as user-initiated disconnection or data transmission completion, and is not determined as an abnormal data transmission interaction. The second condition indicates that the electronic device is in an unused state during the fourth time period, including the time of the transmission stop event, such as a user-uninterrupted state determined by the electronic device's input detection, motion detection, or other modules. The second time period includes a first sub-time period (e.g., 30 seconds) before the transmission stop event and a second sub-time period (e.g., 1 minute) after the transmission stop event. In other words, if the electronic device is in an unused state for a period before and after the transmission stop event, it can be determined that the electronic device is in the first state.

[0046] In this disclosure, the judgment condition of "no transmission start event detected within the third time period after interface connection" accurately identifies the startup anomaly problem of plug being plugged in but no data link actually being established and data transmission not starting. This solves the pain point that users do not notice whether data transmission has started after connecting the data cable, and cannot perceive transmission failures due to line / protocol issues in a timely manner. The judgment condition of "transmission stop event that meets the second condition" effectively distinguishes between unexpected data transmission stoppage and normal stoppage caused by user-initiated operation or transmission completion. It accurately identifies transmission interruption anomalies caused by loose interface, line fault, unexpected power failure of external device, etc. during data transmission, avoiding normal transmission stoppage operations being misjudged as anomalies and improving the accuracy of data transmission anomaly judgment.

[0047] In another embodiment, detecting transmission start events and transmission stop events includes: In response to the detection that the data interaction protocol state between the electronic device and the external device has changed to a data transmission state, it is determined that a transmission start event has been detected. A transmission stop event is determined to have been detected in response to at least one of the following: the number of transmission retries between the electronic device and the external device exceeds the retry threshold, the transmission response duration exceeds the duration threshold, the number of packet losses exceeds the packet loss threshold, and the data interaction protocol state changes to data interaction disconnection.

[0048] In this embodiment, the data interaction protocol is a standardized communication rule for data transmission between electronic devices and external devices, including but not limited to USB transmission protocol, TCP / IP protocol, Bluetooth data transmission protocol, Thunderbolt protocol, etc. Different interface types and transmission scenarios correspond to different adapted protocols. The data interaction protocol state refers to the real-time state of the data interaction protocol during operation, including the non-handshake state (the protocol has not started negotiation after the device is connected), the negotiation state (the device is matching protocol parameters and establishing a link), the data transmission state (the protocol negotiation is completed, the data link is connected, and normal data transmission can be carried out), the paused state (data transmission is temporarily interrupted, but can be resumed), and the disconnected state (the protocol connection is terminated, and the data link is closed), etc. The switching between each state has clear triggering conditions and identifiers, which can be accurately identified by the electronic device. If the data interaction protocol state changes to the data transmission state, it proves that the data interaction protocol between the devices has successfully switched from the initial non-handshake state and negotiation state to the data transmission state. It can be determined that a transmission start event has been detected, and the occurrence time of the event, the corresponding protocol type, transmission link parameters, and other information are recorded in the system log of the electronic device.

[0049] In this embodiment, the number of transmission retries refers to the number of times the electronic device retransmits a data frame / request frame to an external device because it has not received a response and the data transmission has failed. This number is an important indicator for measuring the stability of the data transmission link. The retry threshold is a fixed value preset by the electronic device. This value is set according to the fault tolerance of the data interaction protocol. For example, under the USB protocol, the retry threshold can be set to 3 times, 5 times, etc. If the transmission still fails after exceeding the threshold, it means that the data link can no longer achieve effective transmission, and it is determined to be a transmission anomaly. It can be determined that a transmission stop event has been detected.

[0050] In this embodiment, the transmission response time refers to the time it takes for the electronic device to wait for the external device to respond after sending a data transmission request, or the time it takes for the electronic device to provide feedback on the reception status after the external device sends data to the electronic device. This time reflects the real-time nature of data interaction between devices. The time threshold is a fixed time value preset by the electronic device according to the communication delay characteristics of the transmission protocol. For example, it can be set to 500ms or 1s. If the response time exceeds the threshold, it indicates that the data transmission link is stuck or interrupted, and normal interaction cannot be achieved. It can be determined that a transmission stop event has been detected.

[0051] In this embodiment, the number of packet losses refers to the number of valid data frames lost during data transmission between the electronic device and the external device. This includes data packets sent by the sender but not received by the receiver, and data packets received by the receiver but with verification errors. This number is a core indicator for measuring the integrity of data transmission. The packet loss threshold is a fixed value preset by the electronic device. For example, it can be set to 5 or 10. If the number of packet losses exceeds this threshold, it indicates that there is a serious fault in the data transmission link, and effective data transmission cannot be achieved. It can be determined that a transmission stop event has been detected.

[0052] In this embodiment, the data interaction disconnection state is the core abnormal state of the data interaction protocol, which means that the protocol connection between devices is actively or passively terminated, and the logical link of data transmission is completely shut down. The switching of this state includes two situations: active disconnection (user operation, transmission completion) and passive disconnection (interface looseness, line fault, device power failure). The determination is based on the protocol parsing module detecting that the protocol layer feedback disconnection flag, the link conduction signal disappears, and the negotiation connection cannot be re-established. This state is a direct indicator of the stop of data transmission. When the protocol parsing module detects that the protocol state has changed to data interaction disconnection, it can determine that a transmission stop event has been detected.

[0053] In this disclosure, on the one hand, the detection of the transmission start event is deeply bound to the data interaction protocol state, with the protocol changing to a data transmission state as the sole criterion for judgment. This ensures that the detection of the transmission start event is completely synchronized with the actual hardware and logical link state of data transmission, avoiding misjudgments of successful physical connection but transmission not started from the source, and solving the drawback of traditional detection methods that only use physical connection to determine transmission start. On the other hand, four parallel judgment conditions are set for the transmission stop event, covering all possible stop scenarios in the data transmission process from four dimensions: number of retries, response time, number of packet loss, and protocol state. This achieves comprehensive monitoring of unexpected transmission stoppages, ensuring rapid identification of transmission stoppage events and avoiding delays in abnormal alerts caused by missed judgments due to a single detection condition.

[0054] In another embodiment, the electronic device is in an unused state, including at least one of the following: The electronic device did not detect any input event; The pose change of the electronic device is less than the first threshold; The load change rate of the electronic device is less than the second threshold.

[0055] In this embodiment, an input event refers to a hardware input signal change event triggered when a user actively operates the electronic device. It is a direct identifier of interaction between the user and the electronic device. Input events include, but are not limited to: touch / click / swipe events on the touchscreen (the touchscreen detection module remains active regardless of whether the electronic device is locked or unlocked, and can recognize all touch operations), press events on physical buttons (such as power buttons, volume buttons, and function shortcut keys), operation events on external input devices (such as click / keystroke events on a connected mouse or keyboard), and voice wake-up events (device wake-up operations triggered by user voice commands). All of these operations trigger the corresponding hardware module of the electronic device to generate an input signal. Upon receiving this signal, the input detection module determines that an input event has been detected. If the electronic device does not detect an input event, meaning the user has not performed any active operation on the electronic device, it can be determined that the electronic device is in an unused state.

[0056] In this embodiment, the pose change of an electronic device refers to the physical changes in the position and posture of the electronic device in space, including spatial movements such as movement, shaking, tilting, and flipping. It is a direct physical representation of a user moving, picking up, or placing the electronic device. This change is accurately detected by the motion sensors built into the electronic device, enabling contactless real-time monitoring of the device's physical state. Motion sensors used to detect pose changes include, but are not limited to, accelerometers, gyroscopes, and gravity sensors. Accelerometers detect changes in acceleration along the X, Y, and Z axes to identify movement and shaking; gyroscopes detect changes in angular velocity to identify rotation and flipping; and gravity sensors detect changes in the angle between the device and the direction of gravity to identify tilting and placement. All sensors work collaboratively to collect spatial motion data of the device. The motion monitoring module of the electronic device integrates and analyzes the data to calculate the actual pose change. The first threshold is a pre-set pose change threshold value for the electronic device. This threshold is a quantified physical parameter value that can be flexibly configured according to the sensor's detection accuracy and the usage scenario. If the change in the posture of the electronic device is less than the first threshold, that is, the device does not undergo obvious physical changes such as movement, shaking, tilting, or flipping in space, and is in a relatively static spatial state, and is not picked up, moved, or had its posture adjusted by the user, then the device is determined to be in an unused state.

[0057] In one example, detecting changes in the pose of an electronic device using an accelerometer can be achieved using the following code: public class MainActivity extends AppCompatActivity implementsSensorEventListener { private SensorManager sensorManager; private Sensor accelerometer; @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.activity_main); sensorManager = (SensorManager) getSystemService(Context.SENSOR_SERVICE); / / 获取加速度传感器 accelerometer = sensorManager.getDefaultSensor(Sensor.TYPE_ACCELEROMETER); } @Override protected void onResume() { super.onResume(); / / 注册监听器 if (accelerometer != null) { sensorManager.registerListener(this, accelerometer,SensorManager.SENSOR_DELAY_NORMAL); } } @Override protected void onPause() { super.onPause(); / / 取消注册 sensorManager.unregisterListener(this); } @Override public void onSensorChanged(SensorEvent event) { if (event.sensor.getType() == Sensor.TYPE_ACCELEROMETER) { float ax = event.values[0]; float ay = event.values[1]; float az = event.values[2]; Log.d("Sensor", "Acceleration: x=" + ax + ", y=" + ay + ", z=" + az); } / / Here, we determine whether a move has occurred if the absolute values ​​of ax, ay, and az exceed a certain threshold. } @Override public void onAccuracyChanged(Sensor sensor, int accuracy) { / / Optional: Handling of precision changes } } In this embodiment, the load change rate of an electronic device refers to the magnitude of change in the proportion of hardware load of the electronic device within a unit of time. It is an indirect technical characterization of whether the electronic device is actively used by the user. The change in hardware load is directly triggered by the user's operation. When there is no user operation, the hardware load of the electronic device will be in a relatively stable state, and the load change rate will be extremely low. The hardware load of the electronic device includes, but is not limited to, the operating load of core hardware such as processor (CPU) load, memory (RAM) load, disk (storage) read / write load, and network transceiver load. The resource monitoring module of the electronic device will collect the load proportion data of each hardware in real time at a fixed sampling frequency (e.g., once every 100ms) and calculate the load change rate within a unit of time based on the sampled data. The second threshold is a pre-set load change rate threshold value of the electronic device, which can be flexibly configured according to the hardware performance of the electronic device and the background running programs. If the load change rate of the electronic device is less than the second threshold, that is, the hardware resource operation status of the electronic device is stable, there is no large fluctuation in load caused by user operation, and only normal processes are running in the background, then it can be determined that the electronic device is in an unused state.

[0058] In this disclosure, the user's active operation behavior is directly identified through the detection of input events, achieving accurate determination of the unused state from the perspective of human interaction, covering all user operation types without omission; the device has been moved or picked up by the user by detecting pose changes, thus recognizing non-input operations and filling the gap in pure input detection; the device has been used indirectly by the user by detecting load change rate, thus supplementing the first two determination conditions and improving the accuracy of unused state determination.

[0059] In another embodiment, "issuing prompt information corresponding to the interaction mode" in step S102 includes: Based on at least one of the following: interaction anomaly identifier between electronic device and external device, reason for interaction anomaly, current interaction progress, and interaction anomaly handling suggestions, generate and issue the prompt message corresponding to the interaction mode.

[0060] In this embodiment, the interaction anomaly identifier is a unique standardized identifier assigned by the electronic device to different interaction modes and different anomaly types. In one example, the charging mode code can be set to 01, the data transmission mode code to 02, the charging start anomaly code to 001, the charging stop anomaly code to 002, the data transmission start anomaly code to 001, and the data transmission stop anomaly code to 002. Then, the interaction anomaly identifier for the charging start anomaly is 01001, and the interaction anomaly identifier for the data transmission stop anomaly is 02002.

[0061] In this embodiment, the cause of the interaction anomaly is the specific technical reason identified by the electronic device after hardware detection and software analysis. This reason can be divided into direct causes and possible causes. The direct cause is a hardware / protocol failure that can be accurately identified, while the possible cause is a reasonable inference based on the detection results, ensuring that the prompt information can clearly inform the user of the core cause of the anomaly. In one example, the direct cause of not detecting a charging start event in charging mode could be "the first interface did not detect an input electrical signal," and the possible causes could be "the socket is not powered, the charging cable has poor contact, or the charging head is faulty." The direct cause of detecting a transmission stop event in data transmission mode could be "the data interaction protocol becomes disconnected," and the possible causes could be "the data cable interface is loose, the external device is powered off, or the data link is faulty."

[0062] In this embodiment, the current interaction progress is a quantitative statistical result of the completed interaction process when an interaction anomaly occurs on the electronic device. In one example, in charging mode, charging unexpectedly stops when the battery reaches 50%, and the current interaction progress is "50%"; in data transfer mode, file transfer unexpectedly stops when the file transfer reaches 80%, and the current interaction progress is "80%".

[0063] In this embodiment, the interaction anomaly handling suggestion is an actionable and targeted troubleshooting guide provided by the electronic device based on the cause of the interaction anomaly. This suggestion can be automatically generated based on a pre-set troubleshooting library, which stores standardized troubleshooting steps corresponding to different interaction modes and different anomaly causes. In one example, for the anomaly caused by poor charging contact, the handling suggestion could be "re-plug the charging cable and check the connection between the charging head and the socket" or "replace the charging cable / charging head and try a different socket." For the anomaly caused by a loose data transmission interface, the handling suggestion could be "re-plug the data cable and check for foreign objects in the interface" or "replace the original data cable and check if the device interface is damaged."

[0064] In this embodiment, a prompt message corresponding to the interaction mode can be generated and issued based on at least one of the following: an interaction anomaly identifier between the electronic device and the external device, the reason for the interaction anomaly, the current interaction progress, and an interaction anomaly handling suggestion. That is, the prompt message may include an interaction anomaly identifier, the reason for the interaction anomaly, the current interaction progress, or an interaction anomaly handling suggestion, and different prompt messages can be generated based on different interaction anomaly identifiers, reasons for the interaction anomaly, current interaction progress, or interaction anomaly handling suggestions. For example, different interaction anomaly reasons can use different volume voice prompts depending on the severity of the anomaly; different current interaction progress can use different breathing light colors, etc.

[0065] In this disclosure, by integrating information such as interaction anomaly identifiers, anomaly causes, interaction progress, and processing suggestions to generate prompt information, the technical shortcomings of traditional reminder information, such as being monotonous and lacking guidance, are completely solved, and the practicality and guidance of the prompt information are greatly improved.

[0066] In another embodiment, "issuing prompt information corresponding to the interaction mode" in step S102 includes: A prompt message is issued based on at least one of an audio signal, a vibration signal, and a display signal; and / or, Other devices that establish communication connections with electronic devices can issue prompts based on at least one of audio signals, vibration signals, and display signals.

[0067] In this embodiment, the electronic device can issue a prompt message based on at least one of an audio signal, a vibration signal, and a display signal. The audio signal refers to the prompt message transmitted through a sound waveform, which can be played through the electronic device's speaker, earpiece, or a connected audio output device. Specific forms of the audio signal include, but are not limited to: pre-stored prompt music or sound effects (such as a specific melody, a buzzer sound), text-to-speech (TTS) generated voice broadcasts (such as "Charging unexpectedly stopped, please check the plug," "Charging not started, please check the power supply"), or a mixture of voice and background music. The volume of the audio signal can be automatically adjusted according to ambient noise or determined by user settings to ensure that it can be heard by the user even in noisy environments. The vibration signal refers to the prompt message transmitted through mechanical vibration, which can be generated by a vibration motor built into the electronic device (such as an eccentric rotary mass motor ERM, a linear resonant actuator LRA, or a piezoelectric vibrator). The vibration signal can employ different vibration modes to distinguish the type of abnormality or the degree of urgency; for example, continuous vibration indicates that charging has not started, intermittent vibration indicates that charging has unexpectedly stopped; short, single vibrations indicate a minor abnormality, and long, multiple vibrations indicate a serious abnormality. Vibration signals are particularly suitable for noisy environments or when electronic devices are out of sight, such as in a user's pocket or bag, providing a tactile alert. Display signals refer to prompts conveyed through visual elements, which can be presented via the electronic device's screen, status indicator lights (such as LED breathing lights), or connected display devices. Specific forms of display signals include, but are not limited to: full-screen or pop-up text prompts (displaying anomaly descriptions and troubleshooting suggestions), graphical icons (such as flashing charging error icons or red warning signs), status bar notifications, screen brightness changes, or specific color flashing. In one example, display signals can be synchronized with audio or vibration signals; for instance, while playing a voice prompt, the screen displays corresponding text content and operation buttons (such as a "Recheck Connection" button).

[0068] In this embodiment, prompt messages can also be issued by controlling other devices that have established a communication connection with the electronic device. Other devices refer to peripheral devices that have established a data communication link with the electronic device via wired or wireless means, including but not limited to: smartwatches, smart bracelets, Bluetooth headsets, tablets, laptops, smart speakers, smart TVs, etc., paired with a mobile phone. Communication connection methods may include Bluetooth, Wi-Fi Direct, local area network, NFC, UWB (Ultra-Wideband), or other proprietary wireless protocols. When it is determined that a prompt message needs to be issued, the electronic device sends a control command to the other device through the established communication link. This command includes the type of prompt message (audio, vibration, display), specific content (such as voice text, vibration pattern encoding, displayed text), and triggering timing. After receiving the command, the other device uses its own output module (speaker, vibration motor, display screen, etc.) to issue the corresponding prompt message.

[0069] In one example, for a smartphone charging malfunction, the phone simultaneously sends a notification via Bluetooth to the user's smartwatch. Upon receiving the notification, the watch immediately activates its vibration motor to produce a specific vibration pattern (e.g., three short-long-short vibrations), while displaying a text message "Phone charging malfunction" and a charging icon on the watch screen. If the user is wearing Bluetooth headphones at this time, the phone also sends a notification to the headphones, which then play a voice message saying "Your phone charging has been interrupted." Even if the user has left the room where the phone was placed, they can immediately be notified of the charging malfunction through wrist vibration or voice prompts, allowing them to promptly return and check the charging connection.

[0070] This disclosure utilizes single or combined outputs of audio, vibration, and display signals to adapt to different scenarios such as silent and noisy environments, achieving multi-sensory anomaly alerts and avoiding the failure of single-form alerts. Simultaneously, it overcomes the limitations of the device itself, triggering linked alerts from associated smart devices to achieve off-device alerts, addressing the pain point of users not perceiving anomalies when not near the device. The alert process is automated, adaptable to various communication methods and smart devices, improving the reach and accuracy of anomaly alerts and ensuring users can promptly handle interactive anomalies.

[0071] In another embodiment, an electronic device reminder method further includes: In response to the electronic device being in the second state, if the third condition is met, information on the progress of the interaction between the electronic device and the external device is sent; the second state indicates that the interaction between the electronic device and the external device is normal. The third condition includes the progress of interaction between electronic devices and external devices reaching the target progress threshold.

[0072] In this embodiment, the electronic device continuously monitors the interaction status with the external device. When it is determined that it is currently in the second state, it further determines whether the third condition is met. If the condition is met, it sends interaction progress information.

[0073] In this embodiment, the second state refers to the normal interaction state between the electronic device and the external device. That is, after the first interface and the second interface establish a connection, the expected interaction (charging or data transmission) is proceeding smoothly as expected, without any abnormal interruption or significant performance degradation. In charging mode, the second state is characterized by charging having started and continuing, a stable charging current, a continuous increase in battery power, and no detected charging stop event or power anomaly. In data transmission mode, the second state is characterized by a data transmission protocol being established, data packets being continuously sent and received, a stable transmission rate, and no detected transmission interruption or severe packet loss.

[0074] In this embodiment, when the electronic device is determined to be in the second state, it does not continuously send progress information, but only sends interactive progress information when a third condition is met. The third condition refers to the interactive progress reaching a preset target progress threshold. In charging mode, the target progress threshold can be set to a specific battery percentage, such as 50%, 80%, or 100%; it can also be set as a charging stage transition point, such as the moment when the fast charging stage ends and trickle charging begins. In data transmission mode, the target progress threshold can be set to completion percentage nodes such as 25%, 50%, 75%, or 100%. When the real-time monitored interactive progress reaches the target progress threshold, the third condition is determined to be met, triggering the sending of interactive progress information.

[0075] In one example, for a smartphone charging scenario, the phone sets target progress thresholds of 50%, 80%, and 100% battery level. During the charging process, the phone monitors the battery level in real time, and when the battery level reaches 50%, 80%, and 100%, it sends interactive progress information, such as playing a voice message through the speaker: "Your phone is 50% charged," "Your phone is 80% charged," and "Your phone is 100% charged."

[0076] This disclosure provides progress feedback functionality under normal interaction scenarios, forming a complete interaction reminder system. This solves the problem of anomaly detection while also meeting users' needs for awareness of normal interaction progress. By setting target progress thresholds as trigger conditions, frequent reminders are avoided to prevent user interference; information is only issued at key progress nodes, balancing timely feedback and user experience. Different interaction modes are adapted with dedicated progress statistics dimensions and thresholds, ensuring strong adaptability and allowing users to accurately grasp the completion status of interactions such as charging and data transfer, thus improving the method's practicality and user experience.

[0077] According to embodiments of this disclosure, this disclosure also provides an electronic device and a readable storage medium.

[0078] Figure 4 A schematic block diagram of an example electronic device 800 that can be used to implement embodiments of the present disclosure is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present disclosure described and / or claimed herein.

[0079] like Figure 4As shown, the electronic device 800 includes a computing unit 801, which can perform various appropriate actions and processes based on a computer program stored in a read-only memory (ROM) 802 or a computer program loaded from a storage unit 808 into a random access memory (RAM) 803. The RAM 803 may also store various programs and data required for the operation of the electronic device 800. The computing unit 801, ROM 802, and RAM 803 are interconnected via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0080] Multiple components in electronic device 800 are connected to I / O interface 805, including: input unit 806, such as keyboard, mouse, etc.; output unit 807, such as various types of displays, speakers, etc.; storage unit 808, such as disk, optical disk, etc.; and communication unit 809, such as network card, modem, wireless transceiver, etc. Communication unit 809 allows electronic device 800 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0081] The computing unit 801 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 801 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 801 performs the various methods and processes described above, such as an electronic device reminder method. For example, in some embodiments, an electronic device reminder method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 808. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 800 via ROM 802 and / or communication unit 809. When the computer program is loaded into RAM 803 and executed by the computing unit 801, one or more steps of the electronic device reminder method described above may be performed. Alternatively, in other embodiments, the computing unit 801 may be configured to perform an electronic device reminder method by any other suitable means (e.g., by means of firmware).

[0082] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0083] The program code used to implement the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0084] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0085] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0086] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0087] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.

[0088] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this disclosure can be achieved, and this is not limited herein.

[0089] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means two or more, unless otherwise explicitly specified.

[0090] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for providing reminders to electronic devices, comprising: In response to the connection between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined; The external device can provide power to the electronic device through the second interface; In response to the electronic device being in the first state, a prompt message corresponding to the interaction mode is issued; The first state indicates an abnormal interaction between the electronic device and the external device; the prompts for different interaction modes may be the same or different.

2. The method according to claim 1, wherein the interaction mode is a charging mode, and the response to the electronic device being in a first state includes: In response to the fact that no charging start event of the electronic device was detected during the first time period after the connection was established between the first interface and the second interface; And / or, In response to the detection of a charging stop event that meets a first condition; the first condition indicates that the electronic device is in an unused state during a second period of time in which the charging stop event occurs.

3. The method according to claim 2, wherein detecting the charging start event and charging stop event of the electronic device includes: Listen to the charging status signal received by the broadcast receiver of the electronic device; The charging status signal is generated based on the changes in the electrical signal of the first interface; In response to the charging status signal indicating the start of charging, it is determined that a charging start event of the electronic device has been detected; In response to the charging status signal indicating that charging has stopped, it is determined that a charging stop event of the electronic device has been detected.

4. The method according to claim 1, wherein the interaction mode is a data transmission mode, and the response to the electronic device being in a first state includes: In response to the fact that no transmission start event was detected between the electronic device and the external device during the third time period after the connection was established between the first interface and the second interface; And / or, In response to the detection of a transmission stop event that satisfies the second condition; The second condition indicates that the electronic device is in an unused state during the fourth period when the transmission stop event occurs.

5. The method according to claim 4, wherein detecting the transmission start event and transmission stop event includes: In response to detecting that the data interaction protocol state between the electronic device and the external device changes to a data transmission state, it is determined that the transmission start event has been detected; In response to detecting at least one of the following: the number of transmission retries between the electronic device and the external device is greater than a retry threshold, the transmission response duration is greater than a duration threshold, the number of packet losses is greater than a packet loss threshold, and the data interaction protocol state becomes a data interaction disconnection, the transmission stop event is determined to be detected.

6. The method according to any one of claims 2-5, wherein the electronic device is in an unused state, comprising at least one of the following: The electronic device did not detect any input event; The pose change of the electronic device is less than a first threshold; The load change rate of the electronic device is less than the second threshold.

7. The method according to claim 1, wherein issuing the prompt information corresponding to the interaction mode includes: Based on at least one of the following: interaction anomaly identifier between the electronic device and the external device, interaction anomaly cause, current interaction progress, and interaction anomaly handling suggestion, generate and issue a prompt message corresponding to the interaction mode.

8. The method according to claim 1, wherein issuing the prompt information corresponding to the interaction mode includes: The prompt message is issued based on at least one of an audio signal, a vibration signal, and a display signal; And / or, Other devices that establish a communication connection with the electronic device may issue the prompt message based on at least one of an audio signal, a vibration signal, and a display signal.

9. The method according to claim 1, further comprising: In response to the electronic device being in the second state, if the third condition is met, interaction progress information between the electronic device and the external device is sent out; the second state indicates that the interaction between the electronic device and the external device is normal. The third condition includes the interaction progress between the electronic device and the external device reaching a target progress threshold.

10. An electronic device, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform: In response to the connection between the first interface of the electronic device and the second interface of the external device, the interaction mode between the electronic device and the external device is determined; the external device is able to provide power to the electronic device through the second interface. In response to the electronic device being in a first state, a prompt message corresponding to the interaction mode is issued; the first state indicates an abnormal interaction between the electronic device and the external device; the prompt messages corresponding to different interaction modes may be the same or different.

Images