Remote wake-up processing method, device, system, and storage medium

Abstract

The application provides a remote wake-up processing method, device, system and storage medium, the method is applied to a main processor in a target device, the target device further comprises a USB controller, a USB bus, a USB physical layer transceiver and a USB hub, wherein the main processor and the USB controller are connected, the USB controller is connected with at least one USB peripheral device through the USB physical layer transceiver and the USB hub in sequence by using the USB bus, and the method comprises the following steps: in response to a sleep operation of the target device, controlling the USB peripheral devices to be in a suspended state, and switching the USB controller to a sleep state, in the sleep state, after performing a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any USB peripheral device through the USB hub and the USB physical layer transceiver, and waking up the target device. The remote wake-up is realized based on the wake-up signal after the board-level power-down, and the problem of false alarm of the remote wake-up signal is solved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a remote wake-up processing method, device, system, and storage medium. Background Technology

[0002] In remote wake-up scenarios, the USB controller typically wakes up the USB peripheral, or the USB peripheral wakes up the device. For example, when a device is in sleep mode, the target device can be woken up via a USB keyboard. To use the remote wake-up function, the USB peripheral needs to support the remote wake-up function, and the USB peripheral's remote wake-up capability must be reported to the USB controller in the configuration descriptor settings.

[0003] In related technologies, when the USB controller has been set to sleep (STOP) mode, from the perspective of saving power, the USB peripheral that does not support remote wake-up function will be powered off first. However, at this time, the power-off action of the USB peripheral may trigger the Ugreen HUB to report a wake-up signal, thereby erroneously waking up the device. Summary of the Invention

[0004] In view of this, embodiments of this application provide a remote wake-up processing method, device, system, and storage medium to solve the problem of false alarms in remote wake-up signals.

[0005] In a first aspect, embodiments of this application provide a main processor applied in a target device, the target device further comprising: a USB controller, a USB bus, a USB physical layer transceiver, and a USB hub, wherein the main processor and the USB controller are connected, and the USB controller is connected to at least one USB peripheral via the USB bus, sequentially through the USB physical layer transceiver and the USB hub, the method comprising: In response to a sleep operation on the target device, each USB peripheral is put into a suspended state, and the USB controller is switched to a sleep state; In the sleep state, after performing a board-level power-down operation, a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver is obtained to wake up the target device.

[0006] In an optional implementation, the step of acquiring a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver after performing a board-level power-down operation in the sleep state includes: In the sleep state, a board-level power-down operation is performed, and the wake-up detection unit is activated after the board-level power-down. The wake-up detection unit monitors the wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver.

[0007] In an optional implementation, the step of acquiring a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver after performing a board-level power-down operation in the sleep state includes: In the sleep state, the wake-up detection unit is activated and the signal reporting status of the wake-up detection unit is set to the disabled state; After performing the board-level power-down operation, the signal reporting status of the wake-up detection unit is switched to the start state; The wake-up detection unit monitors the wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver.

[0008] In an optional implementation, controlling each USB peripheral to be in a suspended state in response to a sleep operation for the target device includes: In response to the sleep operation, the USB controller is controlled to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state; In response to the USB bus being in an idle state, the USB peripherals are controlled to be in a suspended state.

[0009] In an optional implementation, the step of controlling the USB controller to stop sending frame start packets to each USB peripheral in response to the sleep operation, so that the USB bus is in an idle state, includes: In response to the sleep operation, the USB controller is controlled to complete the currently executing request and to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

[0010] In an optional implementation, the step of acquiring a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver after the main processor performs a board-level power-down operation in the sleep state includes: In the sleep state, after performing a board-level power-down operation, a wake-up signal for the target device is obtained from the target USB peripheral transmitted through the USB hub and the USB physical layer transceiver. The target USB peripheral is a USB peripheral that supports remote wake-up.

[0011] In an optional implementation, the sleep operation for the target device includes: the sleep operation input through a user interface.

[0012] Secondly, this application also provides an electronic device, including: a main processor, a USB controller, a USB physical layer transceiver, and a USB hub, wherein the main processor and the USB controller are connected, and the USB controller is connected to at least one USB peripheral device via a USB bus through the USB physical layer transceiver and the USB hub in sequence. The main processor is used to execute the method described in any of the first aspects.

[0013] Thirdly, embodiments of this application also provide a remote wake-up processing system, including: at least one USB peripheral and the electronic device described in the second aspect.

[0014] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the method described in any of the first aspects.

[0015] This application provides a remote wake-up processing method, device, system, and storage medium. The method is applied to a main processor connected to a USB controller. The USB controller connects to at least one USB peripheral via a USB bus, a USB physical layer transceiver, and a USB hub. The method includes: responding to a sleep operation for the target device, controlling each USB peripheral to be in a suspended state, and switching the USB controller to a sleep state. In the sleep state, after performing a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any USB peripheral via the USB hub and the USB physical layer transceiver to wake up the target device. This ensures that remote wake-up is achieved based on the wake-up signal only after board-level power-down, solving the problem of false alarms in remote wake-up signals. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a diagram illustrating data packet transmission in a USB system. Figure 2 This is a schematic diagram of the existing remote wake-up process; Figure 3A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 1 ; Figure 4 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 2 ; Figure 5 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 3 ; Figure 6 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 4 ; Figure 7 A schematic diagram of a specific remote wake-up processing architecture provided in this application embodiment; Figure 8 This is a schematic diagram of another remote wake-up processing architecture provided in an embodiment of this application; Figure 9 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application; Figure 10 This is a schematic diagram of the structure of the remote wake-up processing device provided in the embodiments of this application. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0019] First, the relevant concepts involved in this application will be explained: SE0 state: When both the D+ and D- data lines are driven low, it is called the SE0 state. The D+ and D- data lines are the channels for data transmission between the host and peripherals.

[0020] J-state: For full-speed devices, the state is called J-state when the D+ data line is high and the D- data line is low. This is an idle state or a state during data transmission.

[0021] Suspend: A power-saving mode that requires a device to enter a suspend state if it does not receive any bus activity for more than 3ms.

[0022] Reset: Forces the device to return to a known initial state.

[0023] In a USB system, under normal conditions, the USB controller periodically sends Start of Frame (SOF) packets to the USB peripheral via the root hub. If the USB peripheral is a full-speed device, an SOF packet is sent every 1 millisecond; if it's a high-speed device, an SOF packet is sent every 125 microseconds. According to the USB protocol, if the USB bus remains idle for more than 3 milliseconds, the USB peripheral treats this as a suspend signal, requiring the device to enter a suspend state within 10 milliseconds. The USB bus being in an idle state means that the USB controller stops sending SOF packets, or that the USB controller does not initiate a request to the USB peripheral. In the suspend state, the USB peripheral needs to provide voltage to the pull-up resistors of D+ / D- to maintain the idle state. For high-speed USB 2.0 devices, there are some additional requirements: 1. After receiving the hang-up signal, the high-speed device should switch to full-speed mode within 0.125 milliseconds. That is, remove the terminating resistor used for high-speed communication and reconnect the 1.5K pull-up resistor on the D+ data line to make the D+ data line high.

[0024] 2. The high-speed device detects the status of the data line within the following 100~875 microseconds. If the status is a full-speed J signal (D+=1, D-=0, that is, the D+ data line is high and the D- data line is low), it means that the USB controller has issued a suspend signal. If the status is an SE0 signal (D+=0, D-=0), it means that the USB controller has driven the data line D+ from high level to 0, which is a reset signal (the reset signal will last for at least 10 milliseconds).

[0025] Figure 1 This is a diagram illustrating data packet transmission in a USB system, such as... Figure 1 As shown, the USB controller stops sending SOF at point a, and the USB peripheral is in SE0 state. Point b is the 3-millisecond time point. In the following 125 microseconds, the device removes the termination resistor and suspends a 1.5K pull-up resistor. If the USB controller sends a Suspend signal at this time, the USB controller will not drive the D+ data line, causing the D+ data line to be pulled high, forming a full-speed J signal.

[0026] Within 100-875 microseconds after point c, the USB peripheral will check the USB controller behavior again. If it is still a Suspend signal, the USB peripheral will enter a low-power suspend state.

[0027] If a 1.5K pull-up resistor is connected to point c of the USB peripheral, the D+ line cannot be pulled high due to the driving effect of the USB controller on the D+ line, and remains in the SE0 state. The USB peripheral will detect the SE0 state within 100~875 microseconds after point C. After 10 milliseconds, it can be determined that this is a reset signal, and the device will be reset.

[0028] When a device is in a suspended state, any activity on the USB bus (non-idle signal) can wake up / resume the device, thus exiting low-power mode. Similarly, USB peripherals can also wake up the host, such as waking up the host via a USB keyboard when the computer is in standby mode. This function is called remote wake-up.

[0029] Because the device processes full-speed signals when suspended, when the USB controller needs to remove the USB peripheral from the suspended state, it needs to send a full-speed K signal lasting more than 20ms. The USB peripheral will wake up within 1.3 microseconds after seeing the end of the K signal, and the USB controller needs to send an SOF packet within 3 milliseconds to maintain the normal high-speed signal mode; otherwise, the USB peripheral will enter the suspended state again.

[0030] Figure 2 This is a schematic diagram of the existing remote wake-up process, such as... Figure 2 As shown, when the sleep operation begins, the USB peripheral enters a suspended state, and the USB controller changes from the RUN state to the STOP state. At this time, the wake-up detection unit starts working, and the power management unit performs a board-level power-down operation, thus completing the entire sleep process. However, when the USB controller is set to the STOP state, from the perspective of saving power, the USB peripheral that does not support remote wake-up function will be powered down first when the board-level power is turned off, such as the camera. Then, the power-down action of the camera will trigger the USB hub (UGREEN HUB) and the USB physical layer transceiver (USB-PHY) to report a wake-up signal, which will cause the wake-up detection unit to mistakenly detect a remote wake-up signal and thus mistakenly wake up the target device.

[0031] The USB controller handles the higher-level parts of the USB protocol, such as managing data transfer requests, processing endpoints, and interacting with the system bus. The USB physical layer transceiver handles the lowest-level physical signals of the USB protocol, such as converting parallel data from the USB controller into a serial data stream for transmission, and converting received serial data streams into parallel data for transmission to the USB controller. The USB hub expands the number of USB-A or USB-C interfaces and conforms to the USB hub specification. It has one upstream port for connecting electronic devices and multiple downstream ports for users to connect USB peripherals.

[0032] See Figure 2 The P0 between the USB controller and the USB physical layer transceiver indicates that the USB controller and the USB physical layer transceiver belong to the same power domain, namely the constant voltage core domain P0, which is controlled uniformly by the power management unit.

[0033] Based on this, this application, while the USB controller is in sleep mode, performs a board-level power-down operation and then acquires a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver to wake up the target device. This ensures that remote wake-up is only achieved based on the wake-up signal after the board-level power-down, resolving the problem of false alarms for remote wake-up signals. Furthermore, after the board-level power-down is completed, the USB peripheral is in a power-off state, thus preventing the wake-up signal mistakenly detected due to the USB peripheral's power-down action from being used as the genuine wake-up signal to wake up the target device.

[0034] Figure 3 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 1 In this embodiment, the execution entity can be the main processor in the target device. The main processor can be, for example, a central processing unit (CPU), a microcontroller unit (MCU), etc.

[0035] The target device also includes: a USB controller, a USB bus, a USB physical layer transceiver (USB-PHY), and a USB hub (e.g., Ugreen HUB). The main processor and the USB controller are connected, and the USB controller uses the USB bus to connect at least one USB peripheral device in sequence through the USB physical layer transceiver and the USB hub.

[0036] At least one USB peripheral may include, for example, a camera, keyboard, mouse, USB flash drive, etc.

[0037] like Figure 3 As shown, the method may include: S101. In response to a sleep operation targeting the target device, control each USB peripheral to be in a suspended state and switch the USB controller to a sleep state.

[0038] In an optional implementation, the sleep operation for the target device includes: a sleep operation input via a user interface.

[0039] The target device provides a user interface, such as the main interface of a computer. The user interface may include a sleep operation control. The sleep operation input through the user interface can be a selection operation for the sleep operation control. The selection control can be, for example, a click operation, a long press operation, or a double-click operation. This embodiment does not make any special limitations on this.

[0040] Alternatively, in some embodiments, the sleep operation for the target device can also be a sleep operation input via voice. Alternatively, the sleep operation can also be input via a physical button, such as a short press of the power button, or the device can automatically enter sleep mode after a preset period of inactivity; no specific limitations are specified here.

[0041] Of course, the above examples are merely exemplary implementations of sleep operations for the target device, and this embodiment does not specifically limit the specific implementation of the sleep operation.

[0042] In response to a sleep operation targeting the device, each USB peripheral is put into a suspend state, in which each USB peripheral is in a power-saving mode, and the USB controller is switched to sleep state.

[0043] S102. In sleep mode, after performing a board-level power-down operation, obtain the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, so as to wake up the target device.

[0044] In sleep mode, a board-level power-down operation is performed. A board-level power-down operation refers to shutting down the main system and related core circuits of the target device, putting it into a low-power state (such as power off, sleep operation, deep sleep, etc.).

[0045] It should be noted that the board-level power-down operation can be performed based on a preset priority order. For example, USB peripherals that do not support remote wake-up will be powered down first. For instance, since the camera is identified as not supporting remote wake-up, the power supply to the camera will be cut off first, followed by the power supply to the core components. At this point, the board-level power-down is officially completed.

[0046] The wake-up signal for the target device can be triggered by any USB peripheral, such as a key operation on the keyboard or a movement or click operation on the mouse.

[0047] When the board is powered down, the power-down action of the USB peripheral will generate a false wake-up signal. However, the false wake-up signal will not be used as a wake-up signal to wake up the target device. Instead, after the board is powered down, the wake-up signal for the target device will be transmitted to the main processor in sequence through the USB hub and the USB physical layer transceiver, so that the main processor can wake up the target device based on the wake-up signal.

[0048] In some embodiments, the power management unit can be implemented by a separate hardware entity. The main processor can control the power management unit to perform a board-level power-down operation. The main processor can receive a wake-up signal for the target device through the power management unit and control the power management unit to perform a board-level power-on operation to wake up the target device.

[0049] In some embodiments, the power management unit can control the power domain P0 to simultaneously power the USB controller and the USB physical layer transceiver.

[0050] In some embodiments, the power management unit may also be integrated into the main processor as a functional module within the main processor.

[0051] In an optional implementation, step S102, after performing a board-level power-down operation in sleep mode, acquiring a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, may include: In sleep mode, after performing a board-level power-down operation, a wake-up signal for the target device is obtained from at least one USB peripheral, which is transmitted through the USB hub and USB physical layer transceiver. The target USB peripheral is a USB peripheral that supports remote wake-up.

[0052] Among them, at least one USB peripheral includes two types: one type is a USB peripheral that supports remote wake-up and the other type is a USB peripheral that does not support remote wake-up. The wake-up signal for USB control is input through the target USB peripheral and transmitted to the main processor in sequence through the USB hub and the USB physical layer transceiver, so that the main processor wakes up the target device based on the wake-up signal.

[0053] In the remote wake-up processing method provided in this embodiment, the wake-up signal that is mistakenly detected when the execution board is powered down is ignored. Instead, the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver is obtained only after the execution board is powered down. This wake-up signal is the real wake-up signal used to wake up the target device, which increases the reliability of the wake-up detection method and fixes the false wake-up problem that occurs in some scenarios.

[0054] Figure 4 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 2 ,like Figure 4 As shown, in an optional embodiment, step S102 above, in sleep mode, after the main processor performs a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, may include: S201. In sleep mode, perform board-level power-down operation, and control the wake-up detection unit to start after board-level power-down.

[0055] S202. Monitor the wake-up signal for the target device transmitted by any USB peripheral through the USB hub or USB physical layer transceiver via the wake-up detection unit.

[0056] In sleep mode, a board-level power-down operation is performed, and the wake-up detection unit is started after the board-level power-down. The wake-up detection unit in the started state is used to collect wake-up signals. When a wake-up signal for the target device is input through any USB peripheral, the wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, so that the main processor wakes up the target device based on the wake-up signal.

[0057] In some embodiments, the wake-up detection unit can be implemented by a separate hardware entity, or it can be integrated into the main processor as a functional module of the main processor.

[0058] In the remote wake-up processing method provided in this embodiment, the wake-up detection unit is started after the board is powered down. By delaying the start time of the wake-up detection unit, it is made to start working only after the board is powered down. Therefore, when a false wake-up signal is generated when the board is powered down, since the wake-up detection unit has not yet started, there will be no situation where the target device is falsely woken up based on the false wake-up signal, thus solving the problem of false alarm of remote wake-up signal.

[0059] Figure 5 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 3 ,like Figure 5 As shown, in an optional embodiment, step S102 above, after performing a board-level power-down operation in sleep mode, acquiring a wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, may include: S301. In sleep mode, start the wake-up detection unit and set the signal reporting status of the wake-up detection unit to disabled.

[0060] The signal reporting status of the wake-up detection unit is used to indicate whether the wake-up detection unit reports a wake-up signal for the target device to the main processor.

[0061] In sleep mode, the wake-up detection unit is activated and its signal reporting status is set to disabled. The disabled status is used to instruct the wake-up detection unit to prohibit reporting wake-up signals for the target device to the main processor. In other words, the signals collected by the wake-up detection unit from the start-up state to the board-level power-down completion stage will be ignored, discarded, and not reported to the main processor, and thus the target device will not be woken up based on the signal.

[0062] S302. After performing the board-level power-down operation, switch the signal reporting status of the wake-up detection unit to the start status.

[0063] After performing the board-level power-down operation, the signal reporting status of the wake-up detection unit is switched to the start status. The start status indicates that the wake-up detection unit is allowed to report the wake-up signal for the target device to the main processor. In other words, the wake-up signal collected by the wake-up detection unit in the start status can be used to wake up the target device.

[0064] S303: Monitor the wake-up signal for the target device transmitted by any USB peripheral through the USB hub or USB physical layer transceiver via the wake-up detection unit.

[0065] When the wake-up detection unit is in the start state, a wake-up signal for the target device is input through any USB peripheral. The wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver, so that the main processor wakes up the target device based on the wake-up signal.

[0066] In the remote wake-up processing method provided in this embodiment, the working time of the wake-up detection unit remains unchanged, but the wake-up signal for the target device is reported to the main processor only after the board is powered down. That is to say, for the wake-up signal that is falsely detected when the board is powered down, the wake-up detection unit can collect it but will not report it to the main processor. By ignoring the falsely detected wake-up signal, there will be no situation where the target device is falsely woken up based on the falsely detected wake-up signal, thus solving the problem of false alarm of remote wake-up signal.

[0067] Figure 6 A flowchart illustrating the remote wake-up processing method provided in this application embodiment. Figure 4 ,like Figure 6 As shown, in an optional implementation, step S101 above, which controls each USB peripheral to be in a suspended state in response to a sleep operation for the target device, may include: S401, in response to sleep operation, controls the USB controller to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

[0068] S402, in response to the USB bus being in an idle state, controls each USB peripheral to be in a suspended state.

[0069] In response to sleep operation, the USB controller stops sending frame start packets to each USB peripheral, so that the USB bus is in an idle state. In response to the USB bus being in an idle state for a preset duration, each USB peripheral is put into a suspended state.

[0070] In some embodiments, the preset duration can be, for example, 3 milliseconds. If the USB bus is still idle after 3 milliseconds, it is considered a suspend signal. The USB peripheral removes its own termination resistor and suspends the pull-up resistor. If the USB controller does not drive the D+ data line of the USB peripheral, the D+ data line of the USB peripheral is pulled high, forming a full-speed J signal. The USB peripheral checks again whether the USB controller drives the D+ data line of the USB peripheral. If it is not driven, the USB peripheral enters the suspend state.

[0071] In an optional implementation, step S401 above, in response to the sleep operation, controlling the USB controller to stop sending frame start packets to each USB peripheral so that the USB bus is in an idle state, may include: In response to sleep operation, the control USB controller completes the execution of the currently executing request and stops sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

[0072] During normal operation, data transfer requests may be being executed on the USB bus. These requests could include, for example, a request from the USB controller to write data to a USB flash drive, a request from a mouse to report movement data to the USB controller, or a request from a camera to transmit video data to the USB controller.

[0073] In response to sleep operation, the USB controller completes the currently executing requests and stops sending frame start packets to each USB peripheral, thus idling the USB bus. In other words, after ensuring all data transfers have been processed, the USB controller stops all active bus activity to prevent data corruption and hardware damage.

[0074] Based on the above embodiments, Figure 7 This is a schematic diagram of a specific remote wake-up processing architecture provided in an embodiment of this application.

[0075] exist Figure 7 In the architecture shown, the execution steps include the following: Step 1: Start the sleep process.

[0076] Step 2: The USB controller begins the sleep operation.

[0077] Step 3: The USB controller first completes the request that is being executed, and then controls the USB bus to be idle, allowing the USB peripheral to enter a suspended state.

[0078] Step 4: Change the USB controller status from working state to sleep operation state.

[0079] Step 5: The power management unit module performs a board-level power-down operation to complete the sleep process.

[0080] Step 6: The wake-up detection unit module starts working, allowing the wake-up detection unit to report wake-up signals to the power management unit.

[0081] Figure 8 This is a schematic diagram of another remote wake-up processing architecture provided in an embodiment of this application. Figure 8 In the architecture shown, the execution steps include the following: Step 1: Start the sleep process.

[0082] Step 2: The USB controller begins the sleep operation.

[0083] Step 3: The USB controller first completes the request that is being executed, and then controls the USB bus to be idle, allowing the USB peripheral to enter a suspended state.

[0084] Step 5: Change the USB controller status from working state to sleep operation state.

[0085] Step 6: The wake-up detection unit module starts working, and the wake-up detection unit module is prohibited from reporting information.

[0086] Step 7: The power management unit module performs a board-level power-down operation to complete the sleep process.

[0087] Step 8: Allow the wake-up detection unit module to report the wake-up signal to the power management unit.

[0088] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The device can be implemented using the aforementioned target device.

[0089] like Figure 9 As shown, the electronic device 50 may include: a main processor 501, a USB controller 502, a USB physical layer transceiver 503, and a USB hub 504. The main processor 501 and the USB controller 502 are connected. The USB controller 502 is connected to at least one USB peripheral via a USB bus through the USB physical layer transceiver 503 and the USB hub 504 in sequence. The main processor 501 is used to execute the above-mentioned related method steps.

[0090] In some embodiments, the power management unit 505 and the wake-up detection unit 506 can be implemented by separate hardware entities. The device may also include the power management unit 505 and the wake-up detection unit 506. The main processor 501, the USB controller 502, the USB physical layer transceiver 503 and the wake-up detection unit 506 can be integrated on a system on a chip (SOC). The power management unit 505, the wake-up detection unit 506 and the USB controller 502 are respectively communicatively connected to the main processor 501.

[0091] This application also provides a remote wake-up processing system, which may include at least one USB peripheral and the aforementioned electronic device.

[0092] Based on the same inventive concept, this application also provides a remote wake-up processing device corresponding to the remote wake-up processing method. Since the principle of the device in this application is similar to the remote wake-up processing method described above in this application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0093] Figure 10 This is a schematic diagram of the structure of a remote wake-up processing device provided in an embodiment of this application. This device can be integrated into an electronic device.

[0094] like Figure 10 As shown, the device may include: Control module 601 is used to control each USB peripheral to be in a suspended state and switch the USB controller to a sleep state in response to a sleep operation for the target device; The acquisition module 602 is used to acquire, after performing a board-level power-down operation in sleep mode, any USB peripheral transmitting a wake-up signal for the target device through the USB hub or USB physical layer transceiver, so as to wake up the target device.

[0095] In an optional implementation, the acquisition module 602 is specifically used for: In sleep mode, a board-level power-down operation is performed, and the wake-up detection unit is activated after the board-level power-down is completed. The wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver.

[0096] In an optional implementation, the acquisition module 602 is specifically used for: In sleep mode, the wake-up detection unit is activated and the signal reporting status of the wake-up detection unit is set to disabled. After performing the board-level power-down operation, the signal reporting status of the wake-up detection unit is switched to the start state; The wake-up detection unit monitors the wake-up signal for the target device transmitted by any USB peripheral through the USB hub and USB physical layer transceiver.

[0097] In an optional implementation, the control module 601 is specifically used for: In response to sleep operation, the control USB controller stops sending frame start packets to each USB peripheral, so that the USB bus is in an idle state. In response to the USB bus being in an idle state, control each USB peripheral to be in a suspended state.

[0098] In an optional implementation, the control module 601 is specifically used for: In response to sleep operation, the control USB controller completes the execution of the currently executing request and stops sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

[0099] In an optional implementation, the acquisition module 602 is specifically used for: In sleep mode, after performing a board-level power-down operation, a wake-up signal for the target device is obtained from at least one USB peripheral, which is transmitted through the USB hub and USB physical layer transceiver. The target USB peripheral is a USB peripheral that supports remote wake-up.

[0100] In an optional implementation, the sleep operation for the target device includes: a sleep operation input via a user interface.

[0101] The processing flow of each module in the device and the interaction flow between each module can be referred to the relevant descriptions in the above method embodiments, and will not be detailed here.

[0102] This application also provides a computer-readable storage medium storing a computer program, which is executed by a processor to perform the above-described method.

[0103] In this embodiment, the computer program, when run by the processor, can also execute other machine-readable instructions to perform other methods as described in the embodiments. For details on the specific execution steps and principles, please refer to the description of the embodiments, which will not be repeated here.

[0104] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Additionally, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some communication interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0105] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0106] In addition, the functional units in the embodiments provided in this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0107] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0108] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. In addition, the terms "first", "second", "third", etc. are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0109] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this application; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application. All should be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A remote wake-up processing method, characterized in that, A main processor is applied in a target device, the target device further comprising: a USB controller, a USB bus, a USB physical layer transceiver, and a USB hub, wherein the main processor and the USB controller are connected, and the USB controller connects to at least one USB peripheral device sequentially through the USB physical layer transceiver and the USB hub via the USB bus, the method comprising: In response to a sleep operation on the target device, each USB peripheral is put into a suspended state, and the USB controller is switched to a sleep state; In the sleep state, after performing a board-level power-down operation, a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver is obtained to wake up the target device. The board-level power-down operation is used to shut down the main system and core circuitry of the target device.

2. The method according to claim 1, characterized in that, In the sleep state, after performing a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver includes: In the sleep state, a board-level power-down operation is performed, and the wake-up detection unit is activated after the board-level power-down. The wake-up detection unit monitors the wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver.

3. The method according to claim 1, characterized in that, In the sleep state, after performing a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver includes: In the sleep state, the wake-up detection unit is activated and the signal reporting status of the wake-up detection unit is set to the disabled state; After performing the board-level power-down operation, the signal reporting status of the wake-up detection unit is switched to the start state; The wake-up detection unit monitors the wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver.

4. The method according to claim 1, characterized in that, The step of controlling each USB peripheral to be in a suspended state in response to a sleep operation for the target device includes: In response to the sleep operation, the USB controller is controlled to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state; In response to the USB bus being in an idle state, the USB peripherals are controlled to be in a suspended state.

5. The method according to claim 4, characterized in that, In response to the sleep operation, controlling the USB controller to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state, includes: In response to the sleep operation, the USB controller is controlled to complete the currently executing request and to stop sending frame start packets to each USB peripheral, so that the USB bus is in an idle state.

6. The method according to claim 1, characterized in that, In the sleep state, after performing a board-level power-down operation, acquiring a wake-up signal for the target device transmitted by any of the USB peripherals through the USB hub and the USB physical layer transceiver includes: In the sleep state, after performing a board-level power-down operation, a wake-up signal for the target device is obtained from the target USB peripheral transmitted through the USB hub and the USB physical layer transceiver. The target USB peripheral is a USB peripheral that supports remote wake-up.

7. The method according to claim 1, characterized in that, The sleep operation for the target device includes: the sleep operation input through the user interface.

8. An electronic device, characterized in that, include: The system includes a main processor, a USB controller, a USB physical layer transceiver, and a USB hub. The main processor and the USB controller are connected. The USB controller is connected to at least one USB peripheral via a USB bus through the USB physical layer transceiver and the USB hub. The main processor is used to execute the method described in any one of claims 1-7.

9. A remote wake-up processing system, characterized in that, include: At least one USB peripheral and the electronic device as claimed in claim 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by the main processor, performs the method according to any one of claims 1 to 7.

Images