Device remote wake-up method and apparatus, device, and storage medium

Abstract

The application provides a device remote wake-up method and device, equipment and storage medium, relates to the computer technical field, to improve the reliability of remote wake-up terminal equipment. The method provides a remote wake-up system comprising at least one remote wake-up device, a wake-up client, and a terminal device connected one by one with the remote wake-up device, wherein any remote wake-up device and the terminal device connected therewith share device identification information, for responding to a remote wake-up request message sent by the wake-up client, sending a wake-up data packet to the terminal device connected therewith, and making the terminal device execute a wake-up operation according to the wake-up data packet. The method realizes the remote wake-up function for each terminal device through the remote wake-up device connected one by one with each terminal device, avoids the problem that all terminal devices controlled by the start controller cannot realize remote wake-up when the start controller has a problem in the related art, and improves the reliability of remote wake-up of the device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to the technical field of remote control, and provides a device remote wake-up method and device, equipment and storage medium. BACKGROUND

[0002] Remote wake-up (English: Wake on LAN, abbreviated as WOL) is a remote control technology and related technical specification standard applied in local area network or wide area network, which sends instructions to a target terminal device in a sleep or shutdown state through a terminal device in a normal operating state in the local area network, so as to wake up the target terminal device and restore it to a normal running state or change it to a boot state.

[0003] In the related art, a continuous power-on controller is deployed on the gateway device corresponding to each network segment in the local area network, and the wake-up controller sends a wake-up instruction to the target terminal in the wake-up state through the gateway device, so as to realize remote wake-up of the target terminal device. However, when the power-on controller fails, all terminal devices controlled by the power-on controller cannot be remotely woken up, resulting in low reliability of remote wake-up of the device. SUMMARY

[0004] The embodiments of the present application provide a device remote wake-up method, device, equipment and storage medium, to improve the reliability of remotely woken-up terminal devices.

[0005] In one aspect, a device remote wake-up method is provided, which is applied to any remote wake-up device in at least one remote wake-up device included in a remote wake-up system, the remote wake-up system further including a wake-up client and a terminal device connected one-to-one with the at least one remote wake-up device, the one-to-one connected remote wake-up device and the terminal device sharing device identification information, and the method comprising:

[0006] receiving a remote wake-up request message carrying first device identification information sent by the wake-up client, wherein the remote wake-up request message is sent by the wake-up client in response to a remote wake-up operation for a target terminal device and based on the first device identification information of the target terminal device.

[0007] determining whether the first device identification information is the same as the second device identification information of itself;

[0008] If it is determined that the first device identification information is the same as the second device identification information, a wake-up data packet is sent to the target terminal device, so that the target terminal device performs a wake-up operation based on the wake-up data packet.

[0009] In a possible implementation, before receiving the remote wake-up request message carrying the first device identification information sent by the wake-up client, the method further includes:

[0010] After the connection with the target terminal device is established, obtaining the first device identification information of the target terminal device from the target terminal device;

[0011] Replacing the second device identification information of the device with the first device identification information.

[0012] In a possible implementation, if the remote wake-up device includes a microcontroller and an analog switch, the method further includes:

[0013] Detecting, by the microcontroller, the working state of the target terminal device;

[0014] If it is detected that the target terminal device switches from the normal working state to the wake-up standby state, controlling the analog switch to be in the second working state, so that the target terminal device is connected to the gateway device through the microcontroller.

[0015] In a possible implementation, after the remote wake-up device controls the analog switch to be in the second working state, the method further includes:

[0016] If it is detected that the target terminal device switches from the wake-up standby state to the normal working state, controlling the analog switch to be in the first working state, so that the target terminal device is connected to the gateway device through the analog switch.

[0017] In a possible implementation, if the microcontroller is connected to a power unit of the target terminal device, the method further includes:

[0018] Detecting, by the microcontroller, the working state of the target terminal device;

[0019] If it is determined that the target terminal device is in an abnormal working state, sending, by the microcontroller, a restart control signal to the power unit, so that the target terminal device performs a restart operation, and the abnormal working state indicates that the target terminal device cannot respond to any instruction.

[0020] In an aspect, a device remote wake-up method is provided, applied to a wake-up client in a remote wake-up system, the remote wake-up system further including at least one remote wake-up device and a terminal device connected to the at least one remote wake-up device in one-to-one correspondence, and the remote wake-up device and the terminal device connected in one-to-one correspondence share device identification information, and the method includes:

[0021] obtain a first device identification information set, the first device identification information set comprising first device identification information of each terminal device included in the remote wake-up system;

[0022] display a device wake-up interface comprising a plurality of terminal devices to be woken up based on the first device identification information set;

[0023] in response to a remote wake-up operation on a target terminal device in the device wake-up interface, send a remote wake-up request message to a remote wake-up device corresponding to the target terminal device based on first device identification information corresponding to the target terminal device.

[0024] In one aspect, a device remote wake-up apparatus is provided, which is applied to at least one remote wake-up device included in a remote wake-up system, the remote wake-up system further comprising a wake-up client and a terminal device connected to the at least one remote wake-up device in a one-to-one correspondence, the remote wake-up device and the terminal device connected in a one-to-one correspondence sharing device identification information, and the apparatus comprising:

[0025] a receiving unit configured to receive a remote wake-up request message carrying first device identification information sent by the wake-up client, wherein the remote wake-up request message is sent by the wake-up client in response to a remote wake-up operation on a target terminal device and based on first device identification information of the target terminal device;

[0026] a judging unit configured to judge whether the first device identification information is identical to second device identification information of itself;

[0027] a determining unit configured to, if it is determined that the first device identification information is identical to the second device identification information, send a wake-up data packet to the target terminal device so that the target terminal device performs a wake-up operation based on the wake-up data packet.

[0028] Optionally, before any remote wake-up device in the at least one remote wake-up device receives the remote wake-up request message carrying the first device identification information sent by the wake-up client, the receiving unit is further configured to:

[0029] after a connection is established with the target terminal device, obtain the first device identification information of the target terminal device from the target terminal device;

[0030] replace the second device identification information of itself with the first device identification information.

[0031] Optionally, if the any remote wake-up device comprises a microcontroller and an analog switch, the device remote wake-up apparatus further comprises a control unit configured to:

[0032] The microcontroller is used to detect the working status of the target terminal device.

[0033] If the target terminal device is detected to switch from normal working state to wake-up state, the analog switch is controlled to enter a second working state so that the target terminal device can be connected to the gateway device through the microcontroller.

[0034] Optionally, after the remote wake-up device controls the analog switch to be in the second working state, the control unit is further configured to:

[0035] If the target terminal device is detected to switch from the wake-up state to the normal working state, the analog switch is controlled to be in the first working state so that the target terminal device can be connected to the gateway device through the analog switch.

[0036] Optionally, if the microcontroller is connected to the power supply unit of the target terminal device, the control unit is further configured to:

[0037] The microcontroller is used to detect the working status of the target terminal device.

[0038] If it is determined that the target terminal device is in an abnormal working state, a restart control signal is sent to the power supply unit through the microcontroller to cause the target terminal device to perform a restart operation. The abnormal working state indicates that the target terminal device cannot respond to any instructions.

[0039] On one hand, a device remote wake-up apparatus is provided, applied in a wake-up client included in a remote wake-up system. The remote wake-up system further includes at least one remote wake-up device and terminal devices connected one-to-one with the at least one remote wake-up device. The remote wake-up devices and terminal devices share device identification information. The apparatus includes:

[0040] The acquisition unit is used to acquire a first device identification information set, wherein the first device identification information set includes the first device identification information of each terminal device included in the remote wake-up system;

[0041] The display unit is used to display a device wake-up interface containing multiple terminal devices to be woken up, based on the first set of device identification information.

[0042] The sending unit is configured to respond to a remote wake-up operation performed on a target terminal device in the device wake-up interface by sending a remote wake-up request message to the remote wake-up device corresponding to the target terminal device based on the first device identifier information corresponding to the target terminal device.

[0043] On one hand, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of any of the above methods.

[0044] On the one hand, a computer storage medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the steps of any of the above methods.

[0045] On one hand, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of any of the methods described above.

[0046] The beneficial effects of the embodiments of this application are as follows:

[0047] This application provides a remote wake-up system comprising at least one remote wake-up device, a wake-up client, and terminal devices to be woken up connected one-to-one with the at least one remote wake-up device. Each remote wake-up device shares device identification information with its corresponding connected terminal device. It receives and responds to a remote wake-up request message carrying the first device identification information of the terminal device sent by the wake-up client, and sends a wake-up data packet to the connected terminal device, causing the terminal device to perform a wake-up operation based on the wake-up data packet. This method achieves remote wake-up functionality for each terminal device through remote wake-up devices connected one-to-one, avoiding the problem in related technologies where all terminal devices controlled by the power-on controller cannot be remotely woken up when the power-on controller malfunctions, thus improving the reliability of remote wake-up.

[0048] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0049] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0050] Figure 1 A schematic diagram of the network architecture of an existing local area network (LAN) remote wake-up system.

[0051] Figure 2This is a schematic diagram of an application scenario provided by an embodiment of this application;

[0052] Figure 3 A schematic diagram of the interaction flow of a device remote wake-up method provided in an embodiment of this application;

[0053] Figure 4 This is a schematic diagram of the structure of a remote wake-up device provided in an embodiment of this application;

[0054] Figure 5 This is a schematic diagram of another remote wake-up device provided in an embodiment of this application;

[0055] Figure 6 This is a schematic diagram of the structure of a device remote wake-up device provided in an embodiment of this application;

[0056] Figure 7 This is a schematic diagram of another device remote wake-up device provided in an embodiment of this application;

[0057] Figure 8 This is a schematic diagram of the composition structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application 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 application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. Unless otherwise specified, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

[0059] The design concept of the embodiments of this application is briefly introduced below:

[0060] To facilitate understanding of the technical solutions provided in the embodiments of this application, the background technology related to the embodiments of this application will be introduced first:

[0061] like Figure 1As shown, each network segment in the local area network (LAN) requires the deployment of an uninterruptible power-on controller (UPS) on its gateway device. For example, UPS controller 1 and UPS controller 2 are deployed on Layer 2 switch 1 and Layer 2 switch 2, respectively. UPS controller 1 remotely wakes up PC-1 and PC-2 in network segment-1 through Layer 2 switch 1, and UPS controller 2 remotely wakes up PC-3 and PC-4 in network segment-2 through Layer 2 switch 2. The specific wake-up process is as follows:

[0062] After power-on controllers 1 and 2 are deployed and powered on, they send their unique identifier and Internet Protocol (IP) address to the corresponding power-on server via the Internet. At the same time, personal computers (PCs) that need to be remotely powered on need to send their identifier, IP address, and Media Access Control (MAC) address to the power-on server. This is because the IP address can only locate the network segment where the PC is located. When there are multiple PCs in the network segment, gateway devices such as routers or switches need to find the corresponding PC based on the MAC address that is uniquely associated with the PC to complete the data transmission. As shown in Table 1, the power-on server determines the power-on controller to which each PC belongs by comparing the first three digits of the IP address of each PC and the power-on controller stored in the database. It establishes and stores the mapping relationship between the power-on controller corresponding to each network segment and the PCs managed by each power-on controller. This allows users to access the power-on server via the Internet (web page or client) and select the target PC for remote power-on. Based on the information of the target PC and its corresponding power-on controller selected by the user, the server forwards a wake-up message containing the MAC address of the target PC to the power-on controller. The power-on controller sends a power-on command to the target terminal in the wake-up state through the gateway device, so that the target PC responds to the power-on command to realize remote power-on and realize remote wake-up of the target terminal device.

[0063] PC identity MAC address IP address IP address of the boot controller to which the PC belongs Boot controller identity PC-1 xx:xx:xx:xx 192.168.77.x 192.168.77.x 0001 PC-2 xx:xx:xx:xx 192.168.77.x 192.168.77.x 0001 PC-3 xx:xx:xx:xx 192.168.66.x 192.168.66.x 0002 PC-4 xx:xx:xx:xx 192.168.66.x 192.168.66.x 0002

[0064] Table 1

[0065] However, during implementation, it was found that the above wake-up process has at least the following problems:

[0066] To achieve remote wake-up of all PCs within a local area network (LAN), the relevant technologies require prior knowledge of the entire LAN's network architecture, such as the number of switches and network segmentation. A power-on controller needs to be deployed on each switch corresponding to a network segment. This makes the existing remote power-on system difficult to set up and cumbersome to deploy, resulting in a low reliability due to various factors affecting the success rate of remote wake-up. This not only limits the flexibility of remote wake-up but also leads to excessively high costs. Furthermore, when the power-on controller malfunctions, all target PCs controlled by that controller cannot be remotely woken up, further complicating the reliability of remote wake-up. Additionally, the power-on controller requires additional IP addresses, wasting limited IP resources.

[0067] Furthermore, when the target PC's system experiences a blue screen or other serious error that causes it to stop responding to any operation, the relevant technology can no longer send a power-on command to the target PC via the power-on controller to achieve remote wake-up.

[0068] In the entire device wake-up process, the power-on server of the relevant technology not only needs to store address information such as the IP address and MAC address of multiple power-on controllers and PCs, but also needs to forward wake-up messages to the power-on controllers, consuming too many server resources and reducing the efficiency of remote device wake-up.

[0069] Therefore, this application provides a remote wake-up system comprising at least one remote wake-up device, a wake-up client, and terminal devices to be woken up connected one-to-one with the at least one remote wake-up device. Each remote wake-up device shares device identification information with its corresponding connected terminal device. It receives and responds to a remote wake-up request message sent by the wake-up client carrying the first device identification information of the terminal device, and sends a wake-up data packet to the connected terminal device, causing the terminal device to perform a wake-up operation based on the wake-up data packet. This method eliminates the need to deploy a power-on controller on each network segment. It achieves remote wake-up of all terminal devices within the local area network simply through remote wake-up devices connected one-to-one with each terminal device. This avoids the problem in related technologies where all terminal devices controlled by the power-on controller cannot be remotely woken up when the power-on controller malfunctions, improving the reliability of remote wake-up. Furthermore, it eliminates the need for prior knowledge of the local area network architecture, reducing the difficulty and cost of setting up a remote power-on system and increasing the flexibility of remote wake-up.

[0070] On the other hand, the system server corresponding to the remote wake-up system provided by this method not only does not need to store information such as the power-on controller, but also does not need to be responsible for processes such as forwarding wake-up messages, thus reducing the consumption of server resources during the remote wake-up process and improving the efficiency of remote wake-up of devices.

[0071] On the other hand, when any one of the remote wake-up devices in this application embodiment malfunctions, other remote wake-up devices in the local area network and their connected terminal devices can still achieve remote wake-up normally, ensuring the reliability of remote wake-up of the devices.

[0072] On the other hand, the remote wake-up device provided in this application embodiment can obtain the first device identification information from the terminal device after establishing a connection with the terminal device, and replace its own second device identification information with the first device identification information, so as to share the device identification information with the terminal device. By sharing the IP address with the connected terminal device, the remote wake-up device no longer occupies other IP addresses, thus avoiding the shortage of limited IP resources.

[0073] On the other hand, the remote wake-up device provided in this application embodiment can detect the working status of the connected terminal device through the microcontroller of any remote wake-up device. When it is determined that the terminal device is in an abnormal state and cannot respond to any instructions, the microcontroller sends a restart control signal to the power unit of the terminal device to make the terminal device perform a restart operation. When the target PC experiences a blue screen or other similar situation, this application embodiment can control the terminal device to restart to restore the normal state through the remote wake-up device, thereby not affecting the normal implementation of the device's remote wake-up process.

[0074] To better understand the above technical solutions, the technical solutions of the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the collection, dissemination, and use of data in the technical solutions of this application all comply with the requirements of relevant national laws and regulations. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed descriptions of the technical solutions of the present invention, rather than limitations on the technical solutions of the present invention. In the absence of conflict, the embodiments of the present invention and the technical features in the embodiments can be combined with each other.

[0075] like Figure 2 The diagram shown is an application scenario provided by an embodiment of this application. In this scenario, the device may include a wake-up client 101, a terminal device 102, a remote wake-up device 110, a gateway device 120, a system server 130, and a network 140.

[0076] Both the wake-up client 101 and the terminal device 102 can be various types of terminal devices, such as mobile stations (MS) and terminal equipment. Examples of terminal devices include: mobile phones, personal computers, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminal devices in industrial control, wireless terminal devices in autonomous driving, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities, or wireless terminal devices in smart homes. Any device that can connect to the Internet through a gateway device and achieve network communication is acceptable, and this embodiment does not impose specific limitations. In this embodiment, the wake-up client 101 communicates with the system server 130 and the remote wake-up device 110 through the gateway device 120. The wake-up client 101 obtains relevant information about the terminal device 102 from the system server 130 and, based on the device remote wake-up method provided in this application embodiment, sends a remote wake-up request message to the remote wake-up device 110. The terminal device 102 is a terminal device in a wake-up state and is connected to the corresponding remote wake-up device 110. The remote wake-up device 110 receives the remote wake-up request message and, based on the device remote wake-up method provided in this application embodiment, sends a wake-up data packet to the terminal device 102 so that the terminal device 102 performs a wake-up operation.

[0077] The remote wake-up device 110 is a computer device with certain computing capabilities, and it is connected one-to-one with the terminal device 102 to be woken up.

[0078] Gateway device 120 is an edge interconnection device used for interconnection between different virtual networks, providing an electrical signal path for any two network nodes connected, including but not limited to Layer 2 switches, Layer 3 switches, routers, etc. The wake-up client 101 and the remote wake-up device 110 realize network communication functions through gateway device 120.

[0079] The system server 130 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms, but it is not limited to these. The system server 130 can also be configured with a database, which can be used to store the mapping relationship between device identification information and terminal device 102 and remote wake-up device 110 involved in the scheme provided in this application embodiment, intermediate data generated during data processing, and other information that needs to be stored sent by terminal device 102.

[0080] The wake-up client 101, terminal device 102, remote wake-up device 110, gateway device 120, and system server 130 can be connected via network 140. This network 140 can be a wired network or a wireless network. For example, the wireless network can be a mobile cellular network, such as a fourth-generation (4G) network, a fifth-generation (5G) network, or a New Radio (NR) network, or a Wireless-Fidelity (WIFI) network. Of course, it can also be other possible networks, and this embodiment of the invention does not limit this.

[0081] It should be noted that, Figure 2 The examples shown are merely illustrative; in reality, the number of terminal devices 102, remote wake-up devices 110, gateway devices 120, and system servers 130 is unlimited and is not specifically limited in this embodiment. Figure 2 The components and structures shown are merely exemplary and not restrictive. In real-world scenarios, other components and structures may be used as needed.

[0082] The following describes the device remote wake-up method provided by the exemplary embodiments of this application in conjunction with the application scenarios described above and with reference to the accompanying drawings. It should be noted that the above application scenarios are only shown to facilitate understanding of the spirit and principles of this application, and the embodiments of this application are not limited in any way in this respect.

[0083] See Figure 3 The diagram shown is an interactive flow illustration of the device wake-up method provided in this application embodiment. The specific implementation flow of this method is as follows:

[0084] Step 301: Wake up the client to obtain the first set of device identification information.

[0085] In this embodiment of the application, if the wake-up client in the remote wake-up system wants to wake up the terminal device to be woken up in the system by sending a remote wake-up request message, it needs to first obtain a set of first device identification information including the first device identification information of each terminal device in the remote wake-up system, so as to determine the network node to which the remote wake-up request message should be sent.

[0086] For example, device identification information can be the address information of a network device on the Internet, including IP address, MAC address, etc. The Internet node where the target device is located can be located through device identification information.

[0087] In this embodiment, since each terminal device is connected to a corresponding remote wake-up device, the first device identification information set corresponding to each terminal device may only include the IP address of the terminal device to be woken up. Other network devices, such as wake-up clients, can send IP unicast messages to the target terminal device via the IP address without needing to combine MAC addresses for addressing. When the target terminal device is in a wake-up state and cannot receive the request data, the target remote wake-up device with the same IP address can receive this unicast message, achieving the purpose of sending a remote wake-up message to the remote wake-up device corresponding to the target terminal device. Unicast is a routing protocol where the gateway device forwards the unicast message data from the source host to the target host located at the specific location in the network indicated by the IP address, enabling communication between a single sender and a single receiver over the network. In related technologies, the power-on server not only needs to determine the power-on controller corresponding to the network segment where the target terminal device is located based on the IP address, but also needs to forward a wake-up message containing the MAC address of the target terminal device to the power-on controller, since the power-on controller controls multiple terminal devices in that network segment, so that the power-on controller can send a power-on command to the target terminal device to achieve remote wake-up.

[0088] In one possible implementation, the wake-up client can send a request to the system server corresponding to the remote wake-up system to obtain a first set of device identification information corresponding to the terminal device to be woken up. After obtaining the first set of device identification information, the wake-up client can also store it locally. When remote wake-up is needed again, there is no need to request the system server to obtain it again, thereby improving the efficiency of remote wake-up.

[0089] Step 302: Wake up the client and display the device wake-up interface containing multiple terminal devices to be woken up based on the first set of device identification information.

[0090] In this embodiment of the application, after the wake-up client obtains the first set of device identification information, it displays the information of multiple terminal devices to be woken up through the device wake-up interface.

[0091] For example, a user can access the device wake-up interface by using the webpage or client corresponding to the remote wake-up system on the wake-up client. In response to the user's access operation, the terminal device will display information on multiple terminal devices to be woken up, indicated by the set of device identification information obtained from the system server or local storage space, in a list or icon format on its display interface.

[0092] Step 303: The wake-up client responds to the remote wake-up operation performed on the target terminal device in the device wake-up interface by sending a remote wake-up request message to the remote wake-up device corresponding to the target terminal device based on the first device identifier information corresponding to the target terminal device.

[0093] In this embodiment of the application, after the user selects the target terminal device to be woken up in the wake-up client and initiates the wake-up operation, the wake-up client parses the remote wake-up operation performed in the device wake-up interface, determines the first device identification information corresponding to the target terminal, and sends a remote wake-up request message through the first device identification information so that the target remote wake-up device corresponding to the target terminal device receives the message and executes the subsequent remote wake-up process.

[0094] In one possible implementation, after the wake-up client displays information about multiple devices to be woken up, indicated by a first set of device identification information, on the device wake-up interface, the user can trigger a remote wake-up operation for the target terminal device by clicking on the target terminal device on the terminal device's display interface. The terminal device parses the user's remote wake-up operation to determine the corresponding device identification information and sends a unicast message requesting remote wake-up to the network device on the network node indicated by the device identification information. Upon receiving the message, the target remote wake-up device corresponding to the target terminal device executes the corresponding remote wake-up process.

[0095] Step 304: The remote wake-up device determines whether the first device identification information is the same as its own second device identification information. If yes, it proceeds to step 305; otherwise, it ends.

[0096] In this embodiment of the application, after the remote wake-up device receives the remote wake-up request message carrying the first device identification information sent by the wake-up client, it needs to determine whether the first device identification information carried in the message is consistent with its own second device identification information in order to determine whether to execute the subsequent device remote wake-up process.

[0097] For example, the target remote wake-up device can receive a remote wake-up message request sent by a wake-up client in the remote wake-up system through the network path provided by the connected gateway device. The target remote wake-up device can be any of the at least one terminal device included in the remote wake-up system, and the remote wake-up request message it receives carries the first device identification information of the terminal device that is connected to the remote wake-up device in a one-to-one correspondence.

[0098] For example, after receiving a remote wake-up request message, the remote wake-up device needs to determine whether the device identification information carried in the message is consistent with its own device identification information. Only when the device identification information is confirmed to be consistent will the remote wake-up device execute the operation of sending the wake-up data packet to the target terminal device it is connected to. This avoids the situation where the remote wake-up device executes the remote wake-up process after receiving any message, thereby improving the security of remote wake-up of the device.

[0099] In one possible implementation, after establishing a connection with the target terminal device to be woken up, any remote wake-up device among at least one terminal device in the remote wake-up system obtains the target terminal device's first device identification information and replaces its own second device identification information with the first device identification information, so as to achieve sharing of device identification information with the target terminal device.

[0100] For example, taking device identification information including IP address and MAC address as an example, after the target remote wake-up device connects with the target terminal device, it sets its own IP address and MAC address to be consistent with the target terminal device, so that other network devices such as wake-up clients can send remote wake-up message requests to the target terminal device through IP address and MAC address. When the target terminal device is in a waiting wake-up state and cannot receive the request data, the target remote wake-up device with the same IP address and MAC address can receive this data, so as to realize the subsequent remote wake-up process.

[0101] In one possible implementation, since the remote wake-up device and the terminal device share the same IP address and MAC address, other network devices such as the wake-up client can send a remote wake-up message request in the form of an IP unicast packet using only the IP address of the target terminal device. When the target terminal device is in a waiting-to-wake state and cannot receive the request data, the target remote wake-up device with the same IP address can still receive this unicast packet, determine that the IP address indicated by the unicast packet is the same as its own configured IP address, and continue the subsequent remote wake-up process based on the remote wake-up message request.

[0102] In this system, the remote wake-up device shares the IP address and MAC address with the target terminal device, enabling the server to renew the IP address lease. When the terminal device is in a wake-up state, the microcontroller unit (MCU) of the remote wake-up device communicates with the Dynamic Host Configuration Protocol (DHCP) server using the same IP address as the terminal device to be woken up. This prevents the DHCP server from reclaiming the IP address assigned to the terminal device due to prolonged inactivity, thus avoiding disruption to the subsequent remote wake-up process.

[0103] In addition, after the remote wake-up device shares the IP address and MAC address with the target terminal device, it can also implement the Address Resolution Protocol (ARP) response function. When the terminal device is in the wake-up state, the MCU communicates with the gateway device through the ARP response function, so that the ARP table of the gateway device storing the correspondence between the IP address and MAC address of the terminal device does not expire, thus not affecting the subsequent remote wake-up process.

[0104] In one possible implementation, the remote wake-up device may include a microcontroller and an analog switch. The target remote wake-up device can use the microcontroller to detect the operating status of the target terminal device, determine the current state of the target terminal device, and determine whether the state has changed. If the target terminal device is detected to have switched from a normal operating state to a wake-up-ready state, the target remote wake-up device controls the analog switch to a second operating state, enabling the target terminal device to connect to the gateway device via the microcontroller. If the target terminal device is detected to have switched from a wake-up-ready state to a normal operating state, the target remote wake-up device controls the analog switch to a first operating state, enabling the target terminal device to connect to the gateway device via the analog switch. In other words, when the target terminal device is in a normal operating state, it can directly connect to the gateway device to communicate with other devices; when the target terminal device is in a wake-up-ready state, the connection between the target terminal device and the gateway device is disconnected.

[0105] For example, such as Figure 4 The diagram shows the composition of a remote wake-up device, which can consist of a microcontroller, an analog switch, and multiple external interfaces for connecting to external devices such as terminal devices and gateway devices.

[0106] In one possible implementation, the external interface of the remote wake-up device may include a Universal Serial Bus (USB) interface and a network interface.

[0107] The MCU of the remote wake-up device can connect to the terminal device via a USB interface. The USB interface provides a communication channel for the MCU to detect the current working status of the terminal device. The MCU uses the USB protocol to communicate and obtain the USB device enumeration process shown in Table 2. The MCU of the remote wake-up device detects the working status of the terminal device based on the USB device enumeration signals returned by the USB interface. First, after the MCU obtains the insertion signal returned by the USB interface and confirms that the remote wake-up device has connected to the terminal device, it needs to obtain five different enumeration signals indicating that the terminal device is powered on, the terminal device has completed a reset operation, the terminal device has an assigned network address, and the terminal device has been configured. Only when the MCU obtains all of the above enumeration signals can it determine that the terminal device is in normal working status.

[0108] Insertion Power supply Initial Address Configuration Suspended Terminal device operating state × Device not inserted √ × Device inserted, but not powered √ √ × Device inserted and powered, but not reset √ √ √ × Device inserted, powered and reset, but not assigned address √ √ √ √ × Device assigned address, but not configured √ √ √ √ √ × Device configured, device functionality available

[0109] Table 2

[0110] The network interface includes, but is not limited to, a standard RJ45 socket. The remote wake-up device is connected between the terminal device and the gateway device through the network interface, which provides the remote wake-up device with a network connection path such as Ethernet (ETH). The analog switch is a switch controller with at least two operating states. After the MCU of the remote wake-up device detects the operating state of the terminal device, it controls the analog switch to the corresponding operating state to adjust the connection between the terminal device and the gateway device, thereby switching the terminal device to different network connection lines.

[0111] In one possible implementation, the analog switch can be, but is not limited to, a single-pole double-throw (SPDT) switch. The microcontroller controls the SPDT switch to different orientations via a general-purpose input / output (GPIO) interface to adjust different network connection lines. For example, when the MCU detects that a terminal device has switched from a normal operating state to a wake-up state, the MCU controls the analog switch to the MCU orientation via the GPIO interface, allowing the terminal device to connect to the gateway device through the MCU. The MCU can then remotely wake up the terminal device through the network path provided by the gateway device.

[0112] When the MCU detects that the terminal device has switched from the wake-up state to the normal working state, the MCU controls the analog switch to switch to the terminal device through the GPIO interface. The terminal device connects to the gateway device through the analog switch, so that the terminal device in the normal working state can perform normal network communication through the network path provided by the gateway device.

[0113] In one possible implementation, the target remote wake-up device also includes a network transformer. The analog switch is connected to the network interface of an external gateway device via the network transformer. The network transformer is used to isolate the different voltage levels between the analog switch and the gateway device to prevent damage to the analog switch due to different voltage transmissions.

[0114] For example, when gateway devices such as switches have Power Over Ethernet (POE) functionality, they provide a network path and transmit data signals while also providing DC power. If such gateway devices are directly connected to analog switches through the network interface, the DC power supply will damage the analog switches. Therefore, in order to further improve the durability of remote wake-up devices, a network transformer can be set between the network interface and the analog switch to isolate the DC power.

[0115] In one possible implementation, the remote wake-up device can not only function as a standalone device connected to a terminal device via an interface, such as... Figure 5 As shown, the remote wake-up device can also be built into the terminal device, further simplifying the device structure.

[0116] For example, compared to connecting the terminal device as a standalone external device, the built-in remote wake-up device does not require additional network and USB interfaces to connect the terminal device and the gateway device. It can directly connect to the gateway device through the terminal device's network interface. Simultaneously, the microcontroller can be directly connected to the terminal device's CPU via GPIO ports, determining the terminal device's operating status based on CPU signals, eliminating the need for a USB connection. Furthermore, the analog switch can be directly interconnected with the terminal device's network card to control the terminal device's network lines.

[0117] Step 305: The target remote wake-up device sends a wake-up data packet to the target terminal device, so that the target terminal device performs a wake-up operation based on the wake-up data packet.

[0118] In this embodiment of the application, after the remote wake-up device determines that the first device identification information is the same as its own second device identification information, it triggers the operation of sending a wake-up data packet to the terminal device to be woken up connected to it, so that the terminal device to be woken up is remotely woken up.

[0119] In one possible implementation, the remote wake-up device can generate a wake-up data packet with remote wake-up function through a special data format provided by WOL technology, and send the wake-up data packet to the target terminal device it is connected to in the form of broadcast based on a transport protocol such as User Datagram Protocol (UDP).

[0120] In one possible implementation, the remote wake-up device can also send wake-up data packets to the target terminal device via a wired interface.

[0121] In one possible implementation, the wake-up data packet can be, but is not limited to, a Magic Packet. After receiving a remote wake-up request message, the microcontroller of the remote wake-up device generates a Magic Packet in a specific format based on its MAC address information, which is consistent with that of the target terminal device to be woken up, and sends it to the network interface card (NIC) of the target terminal device. The NIC of the target terminal device supports Wake-up Online (WOL) functionality. It can parse and determine whether the received Magic Packet conforms to the preset wake-up data packet format and whether the MAC address it carries matches that of the target terminal device, thereby determining whether to wake up the target terminal device. When the Magic Packet meets the above conditions, the NIC performs the wake-up operation, preventing the target terminal device from being woken up after receiving any message, and further improving the security of remote wake-up.

[0122] In one possible implementation, the MCU of the remote wake-up device can also be connected to the power supply unit of the terminal device. The remote wake-up device detects the working status of the terminal device through the microcontroller. When it is determined that the terminal device is in an abnormal working state that cannot respond to any instructions, the remote wake-up device sends a control signal to the power supply unit through the microcontroller to make the target terminal device perform a restart operation.

[0123] For example, as shown above Figure 5 As shown, the MCU of the remote wake-up device is connected to the power supply unit and CPU of the terminal device through GPIO ports. The MCU determines the working status of the terminal device based on the CPU signals. When it is determined that the terminal device is in an abnormal working state such as a blue screen and cannot respond to any instructions, the microcontroller sends a control signal to the power supply unit it is connected to, simulating forced power-on and power-off methods such as manual button power-on and power-off, so that the terminal device performs a restart operation, so that the terminal device returns to a normal state that can accept instructions, thus not affecting the normal implementation of remote wake-up of the device.

[0124] Please see Figure 6 Based on the same inventive concept, this application also provides a device remote wake-up device 60, applied in at least one remote wake-up device included in a remote wake-up system. The remote wake-up system further includes a wake-up client and terminal devices connected one-to-one with the at least one remote wake-up device. The remote wake-up devices and terminal devices connected one-to-one share device identification information. The remote wake-up system also includes multiple terminal devices, each connected one-to-one with a remote wake-up device. Each remote wake-up device shares device identification information with the terminal devices connected to it. The device includes:

[0125] The receiving unit 601 is used to receive a remote wake-up request message carrying first device identification information sent by the wake-up client. The remote wake-up request message is sent by the wake-up client in response to a remote wake-up operation for the target terminal device and to the corresponding remote wake-up device based on the first device identification information of the target terminal device.

[0126] The judgment unit 602 is used to determine whether the first device identification information is the same as its own second device identification information;

[0127] The determining unit 603 is configured to send a wake-up data packet to the target terminal device if it is determined that the first device identification information is the same as the second device identification information, so that the target terminal device performs a wake-up operation based on the wake-up data packet.

[0128] Optionally, before receiving the remote wake-up request message carrying the first device identification information sent by the wake-up client, the receiving unit 601 is further configured to:

[0129] After establishing a connection with the target terminal device, obtain the first device identification information of the target terminal device from the target terminal device;

[0130] Replace its own second device identification information with its first device identification information.

[0131] Optionally, if any remote wake-up device includes a microcontroller and an analog switch, the device remote wake-up apparatus further includes a control unit 604, used for:

[0132] The working status of the target terminal device is detected by a microcontroller.

[0133] If the target terminal device is detected to switch from normal working state to wake-up state, the control analog switch is put into a second working state so that the target terminal device can be connected to the gateway device through the microcontroller.

[0134] Optionally, after any remote wake-up device controls the analog switch to be in the second operating state, the control unit 604 is further configured to:

[0135] If the target terminal device is detected to switch from the wake-up state to the normal working state, the control analog switch is put into the first working state so that the target terminal device can be connected to the gateway device through the analog switch.

[0136] Optionally, if the microcontroller is connected to the power supply unit of the target terminal device, the control unit 604 is further configured to:

[0137] The working status of the target terminal device is detected by a microcontroller.

[0138] If the target terminal device is determined to be in an abnormal working state, a restart control signal is sent to the power supply unit through the microcontroller to make the target terminal device perform a restart operation. The abnormal working state indicates that the target terminal device cannot respond to any instructions.

[0139] This device can be used to execute the methods performed by the remote wake-up device in the various embodiments of this application. Therefore, the functions that each functional module of this device can achieve can be referred to the description of the foregoing embodiments, and will not be repeated here.

[0140] Please see Figure 7 Based on the same inventive concept, this application also provides a device remote wake-up device 70, applied in a wake-up client included in a remote wake-up system. The remote wake-up system further includes at least one remote wake-up device and terminal devices connected one-to-one with the at least one remote wake-up device. The remote wake-up devices and terminal devices connected one-to-one share device identification information. The device includes:

[0141] The acquisition unit 701 is used to acquire a first device identification information set, which includes the first device identification information of each terminal device included in the remote wake-up system;

[0142] Display unit 702 is used to display a device wake-up interface containing multiple terminal devices to be woken up, based on a first set of device identification information.

[0143] The sending unit 703 is used to respond to a remote wake-up operation performed on a target terminal device in the device wake-up interface, and to send a remote wake-up request message to the remote wake-up device corresponding to the target terminal device based on the first device identification information corresponding to the target terminal device.

[0144] This device can be used to execute the methods used to wake up the client in the various embodiments of this application. Therefore, the functions that each functional module of this device can achieve can be referred to the description of the foregoing embodiments, and will not be repeated here.

[0145] This application embodiment uses a remote wake-up device that shares device identification information with connected terminal devices in a remote wake-up system. It receives and responds to a remote wake-up request message sent by a wake-up client, which carries the first device identification information of the terminal device. It then sends a wake-up data packet to the connected terminal device, enabling the terminal device to perform a wake-up operation based on the wake-up data packet. This avoids the problem in related technologies where all terminal devices controlled by the power-on controller cannot be remotely woken up when the power-on controller malfunctions, thus improving the reliability of remote wake-up of the device.

[0146] For ease of description, the above sections are divided into functional units (or modules) and described separately. Of course, in implementing this application, the functions of each unit (or module) can be implemented in one or more software or hardware components. This device can be used to execute the methods shown in the embodiments of this application; therefore, the functions that each functional module of the device can achieve can be referred to the descriptions of the foregoing embodiments, and will not be repeated here.

[0147] Please see Figure 8 Based on the same technical concept, embodiments of this application also provide a computer device. In one embodiment, as shown in the figure, the computer device may include a memory 801, a communication module 803, and one or more processors 802.

[0148] The memory 801 is used to store computer programs executed by the processor 802. The memory 801 mainly includes a program storage area and a data storage area. The program storage area can store the operating system, and the data storage area can store various operation instruction sets, etc.

[0149] Memory 801 may be volatile memory, such as random-access memory (RAM); memory 801 may also be non-volatile memory, such as read-only memory, flash memory, hard disk drive (HDD), or solid-state drive (SSD); or memory 801 may be any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. Memory 801 may be a combination of the above-mentioned memories.

[0150] The processor 802 may include one or more central processing units (CPUs) or digital processing units, etc. The processor 802 is used to implement the aforementioned remote device wake-up method when calling a computer program stored in the memory 801.

[0151] The communication module 803 is used to communicate with the object category determination device or other network devices.

[0152] This application embodiment does not limit the specific connection medium between the memory 801, communication module 803, and processor 802 described above. This application embodiment... Figure 8 The memory 801 and the processor 802 are connected via a bus 804, and the bus 804 is inFigure 8 The diagram uses thick lines to describe the connections between other components; these are for illustrative purposes only and should not be considered limiting. The 804 bus can be divided into address bus, data bus, control bus, etc. For ease of description, Figure 8 It is described using only a thick line, but does not indicate that there is only one bus or one type of bus.

[0153] The memory 801 stores a computer storage medium containing computer-executable instructions for implementing the device remote wake-up method of the embodiments of this application. The processor 802 is used to execute the device remote wake-up methods of the above embodiments.

[0154] Based on the same inventive concept, embodiments of this application also provide a storage medium storing a computer program, which, when executed on a computer, causes the computer processor to perform the steps in the device remote wake-up method according to various embodiments of this application described above.

[0155] In some possible implementations, various aspects of the device remote wake-up method provided in this application can also be implemented in the form of a program product, which includes program code. When the program product is run on a computer device, the program code is used to cause the computer device to perform the steps in the device remote wake-up method according to the various exemplary embodiments of this application described above. For example, the computer device can perform the steps of the various embodiments.

[0156] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of readable storage media include: electrical connections having one or more wires, portable 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 thereof.

[0157] The program product of the embodiments of this application may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on a computing device. However, the program product of this application is not limited thereto. In this application, the readable storage medium may be any tangible medium that contains or stores a program that may be used by or in conjunction with a command execution system, apparatus, or device.

[0158] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. This propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with a command execution system, apparatus, or device.

[0159] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0160] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0161] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.

[0162] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0163] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0164] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0165] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for remotely waking up a device, characterized in that, The method is applied to any one of at least one remote wake-up devices included in a remote wake-up system, wherein the remote wake-up system further includes a wake-up client and terminal devices connected one-to-one with the at least one remote wake-up device, and the one-to-one connected remote wake-up devices and terminal devices share device identification information. The method includes: The system receives a remote wake-up request message carrying first device identification information sent by the wake-up client, wherein the remote wake-up request message is sent by the wake-up client in response to a remote wake-up operation for a target terminal device and based on the first device identification information of the target terminal device to the corresponding remote wake-up device; Determine whether the first device identification information is the same as its own second device identification information; If it is determined that the first device identification information is the same as the second device identification information, a wake-up data packet is sent to the target terminal device so that the target terminal device performs a wake-up operation based on the wake-up data packet.

2. The method as described in claim 1, characterized in that, Before receiving the remote wake-up request message carrying the first device identification information sent by the wake-up client, the method further includes: After establishing a connection with the target terminal device, the first device identification information of the target terminal device is obtained from the target terminal device; Replace its own second device identification information with the first device identification information.

3. The method as described in claim 1, characterized in that, If any of the remote wake-up devices includes a microcontroller and an analog switch, then the method further includes: The microcontroller is used to detect the working status of the target terminal device. If the target terminal device is detected to switch from normal working state to wake-up state, the analog switch is controlled to enter a second working state so that the target terminal device can be connected to the gateway device through the microcontroller.

4. The method as described in claim 3, characterized in that, After controlling the analog switch to the second operating state, the method further includes: If the target terminal device is detected to switch from the wake-up state to the normal working state, the analog switch is controlled to be in the first working state so that the target terminal device can be connected to the gateway device through the analog switch.

5. The method as described in claim 3, characterized in that, If the microcontroller is connected to the power supply unit of the target terminal device, the method further includes: The microcontroller is used to detect the working status of the target terminal device. If it is determined that the target terminal device is in an abnormal working state, a restart control signal is sent to the power supply unit through the microcontroller to cause the target terminal device to perform a restart operation. The abnormal working state indicates that the target terminal device cannot respond to any instructions.

6. A method for remotely waking up a device, characterized in that, The method is applied to a wake-up client included in a remote wake-up system, wherein the remote wake-up system further includes at least one remote wake-up device and terminal devices connected one-to-one with the at least one remote wake-up device, and the one-to-one connected remote wake-up devices and terminal devices share device identification information. The method includes: Obtain a first set of device identification information, which includes the first device identification information of each terminal device included in the remote wake-up system; Based on the first set of device identification information, a device wake-up interface containing multiple terminal devices to be woken up is displayed; In response to a remote wake-up operation performed on a target terminal device in the device wake-up interface, a remote wake-up request message is sent to the remote wake-up device corresponding to the target terminal device based on the first device identifier information corresponding to the target terminal device.

7. A device remote wake-up device, characterized in that, The device is applied to at least one remote wake-up device included in a remote wake-up system, wherein the remote wake-up system further includes a wake-up client and terminal devices connected one-to-one with the at least one remote wake-up device, and the remote wake-up devices and terminal devices share device identification information. The device includes: The receiving unit is configured to receive a remote wake-up request message carrying first device identification information sent by the wake-up client, wherein the remote wake-up request message is sent by the wake-up client in response to a remote wake-up operation for a target terminal device and based on the first device identification information of the target terminal device to the corresponding remote wake-up device; The judgment unit is used to determine whether the first device identification information is the same as its own second device identification information; The determining unit is configured to send a wake-up data packet to the target terminal device if it is determined that the first device identification information is the same as the second device identification information, so that the target terminal device performs a wake-up operation based on the wake-up data packet.

8. A device remote wake-up device, characterized in that, The device is applied to a wake-up client included in a remote wake-up system, wherein the remote wake-up system further includes at least one remote wake-up device and terminal devices connected one-to-one with the at least one remote wake-up device, and the remote wake-up devices and terminal devices share device identification information. The device includes: The acquisition unit is used to acquire a first device identification information set, wherein the first device identification information set includes the first device identification information of each terminal device included in the remote wake-up system; The display unit is used to display a device wake-up interface containing multiple terminal devices to be woken up, based on the first set of device identification information. The sending unit is configured to respond to a remote wake-up operation performed on a target terminal device in the device wake-up interface by sending a remote wake-up request message to the remote wake-up device corresponding to the target terminal device based on the first device identifier information corresponding to the target terminal device.

9. A computer device, characterized in that, include: At least one processor, and Memory connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the method as described in any one of claims 1-6 by executing the instructions stored in the memory.

10. A computer storage medium, characterized in that, The computer storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-6.

11. A computer program product comprising computer program instructions, characterized in that, When executed by a processor, the computer program instructions implement the steps of the method described in any one of claims 1-6.

Images