Pseudo-sleep mode for networked devices

Abstract

The invention relates to a pseudo sleep mode for networked devices. A networked device includes a communication interface, a system-on-chip (SoC), and pseudo-sleep mode logic. The SoC includes a processor, a memory, an internal PHY module, and other internal SoC modules. The pseudo-sleep mode logic is configured to detect receipt of a sleep command and, in response, cause the networked device to enter a pseudo-sleep mode in which the internal SoC module is powered off in addition to the internal PHY module, processor, and memory remaining powered on. The logic is further configured to detect receipt of a wake-up command when the networked device is in the pseudo-sleep mode and, in response, cause the networked device to exit the pseudo-sleep mode.

Description

Background Art

[0001] A networked device such as a switch, router, or access point may include an external communication interface to enable communication with other devices. Such an external communication interface may include, for example, a wired interface including a port to which a communication cable may be removably connected, or a wireless interface including a radio transceiver. (External in this context refers to the ability of the interface to interface with an electronic device external to the networked device, but does not necessarily imply a physical location of the interface; some external interfaces such as a Wi-Fi interface may be physically located internal to the networked device).

[0002] In addition, the networking device may include control circuits that control the operation of the networking device. The control circuits may include processors, memory, and other modules / devices. Among these modules may be one or more "PHYs," which include chips or modules that control the physical layer operations of a particular external communication interface—for example, a chip / module that controls the physical layer operations of an Ethernet interface may be referred to as an Ethernet PHY (or sometimes just a PHY). In some networking devices, some (or all) of the devices / modules that make up the control circuits may be provided as part of a system on a chip (SoC). An SoC is an integrated circuit (IC) that integrates the CPU, memory, and various other components of the system as part of the same IC (i.e., all components are formed on / in the same chip or die), as opposed to the components being provided as separate and distinct ICs that are connected together (e.g., via mounting to a motherboard). BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure can be understood from the following detailed description alone or in conjunction with the accompanying drawings. The accompanying drawings are included to provide a further understanding of the present disclosure and are incorporated into and constitute a part of this specification. The accompanying drawings illustrate one or more examples of the present teachings and together with the description explain certain principles and operations. In the drawings:

[0004] Figure 1 is a block diagram illustrating an example networking device.

[0005] Figure 2 is a block diagram illustrating another example networking device.

[0006] Figure 3 is a block diagram illustrating an example computer program product.

[0007] Figure 4 is a process flow diagram illustrating a first example method.

[0008] Figure 5 is a process flow diagram illustrating a second example method.

[0009] Figure 6is a block diagram illustrating an example system. DETAILED DESCRIPTION

[0010] Even when lightly loaded (sending / receiving little communication) or completely unloaded (no communication is sent / received), a networking device may consume power. This power consumption may be partially due to the control circuitry of the networking device. Specifically, the SoC of the networking device may consume some power even when little or no communication passes through the networking device. In order to reduce this wasteful power usage, some networking devices have provided a sleep mode, which, when entered, causes the networking device to power off its SoC. As mentioned above, the SoC is one of the main factors that cause wasteful power consumption, so by powering off the SoC, the power consumption of the device can be reduced. In sleep mode, the PHY of the networking device, which is separate from the SoC, can remain powered to monitor for a wake-up command, which, when received, causes the networking device to exit sleep mode and power on the SoC. Thus, for example, the network can put one or more networking devices into sleep mode when they are not needed, and then wake up these devices when needed. This type of sleep mode may also be referred to as "full sleep mode" in this article.

[0011] Although the full sleep mode can effectively reduce the wasted power consumption in devices that can utilize this mode, not all networked devices can utilize the full sleep mode. Specifically, the above-mentioned full sleep mode usually requires a discrete PHY chip outside the SoC. Such a PHY is referred to as an "external PHY" in this article. However, some networked devices do not have such an external PHY, but instead utilize a PHY module integrated into the SoC. This PHY integrated into the SoC may be referred to as an "internal PHY" or "integrated PHY" in this article. This device that lacks a discrete external PHY but utilizes an internal PHY integrated into the SoC cannot use the above-mentioned full sleep mode, because in the full sleep mode, the entire SoC is powered off, which means that the integrated PHY module that is part of the SoC is also powered off, so the external communication interface controlled by the PHY will no longer work. Therefore, the device cannot receive any communication, including wake-up commands, so the device cannot be awakened from sleep mode. In contrast, a networked device with an external PHY can safely power off its entire SoC in full sleep mode because the external PHY (which is not part of the SoC) can remain powered on, so that the wake-up command can be received. Thus, the full sleep mode described above is applicable to networking devices with a discrete external PHY, but not to devices with an internal PHY integrated into the SoC. (As used herein, the terms "external" and "internal" when applied to a PHY should be understood to describe the relationship of the PHY to the SoC, and not to imply the location of the PHY relative to the external / internal of the networking device itself).

[0012] Furthermore, adding an external PHY to a networking device that lacks an external PHY may increase the cost and complexity of the networking device, and therefore in some cases this may not be a viable solution to the above-mentioned problems. Not only is the cost of the external PHY itself an issue, but adding an external PHY may also require redesigning the system circuit board or other components of the system, which can be quite expensive. Therefore, it is often the case that high-end networking devices (i.e., more expensive, higher performance, and / or more full-featured devices) have an external dedicated PHY, while more value-oriented networking devices (i.e., cheaper, lower performance, and / or less functional devices) tend to lack such external PHYs to keep costs low. Adding an external PHY to a value-oriented networking device may increase the cost of the product beyond what customers are willing to pay for a value-oriented product. Therefore, there is a need for an energy-saving feature that can be used in a networking device that lacks an external PHY and does not significantly increase the cost of the networking device.

[0013] To address the above problems, the examples disclosed herein provide a pseudo-sleep mode for networked devices that lack an external PHY, which can be entered to reduce the power consumption of networked devices. In pseudo-sleep mode, except for the internal PHY, processor, and memory integrated into the SoC, which remain powered on, the internal modules of the SoC are powered off. The internal PHY that remains powered on controls the external communication interface that sends the wake-up command. Since the SoC module is turned off, the overall power consumption of the SoC can be greatly reduced. However, unlike the above-mentioned full sleep mode, in pseudo-sleep mode, power is not removed from the entire SoC (this is why this article refers to it as a "pseudo" sleep mode). As described above, the internal PHY remains powered on, so the networked device can still receive a wake-up command through the external communication interface controlled by the internal PHY.

[0014] Furthermore, in some examples, the pseudo-sleep mode can be relatively inexpensively integrated into a networking device. For example, in some embodiments, the pseudo-sleep mode can be integrated into a networking device via a software and / or firmware update without adding any new hardware components to the system and without redesigning the system board. This can even allow relatively low-cost networking devices to benefit from the power-saving pseudo-sleep mode.

[0015] In addition, in some examples, in addition to powering the internal SoC module, the pseudo-sleep mode also includes powering off unnecessary external communication interfaces. For example, in some embodiments, all external communication interfaces except one interface for the communication wake-up command can be powered off (in some examples, the same interface is also used for the communication sleep command). For example, in one example, the networked device includes an external communication interface, which includes an Ethernet communication interface, a USB communication interface, and a Wi-Fi communication interface through which the communication wake-up command passes, and in such an example, entering the pseudo-sleep mode can include powering off the USB interface and the Wi-Fi interface while keeping the Ethernet interface operable. Powering off unnecessary external communication interfaces can further reduce the amount of power consumed by the networked device in the pseudo-sleep mode, while still allowing the networked device to receive a wake-up command via an external interface that remains operable.

[0016] In addition, in some examples, in addition to powering off the internal SoC module and / or the external communication interface, the pseudo sleep mode also includes reducing the frequency of the CPU of the SoC. The power consumed by the CPU depends on its operating frequency, so reducing the frequency will reduce the amount of power consumed by the CPU while still allowing the CPU to remain operable. In addition, in some embodiments, in addition to powering off the internal SoC module and / or the external communication interface, the pseudo sleep mode also includes terminating the user process running on the CPU and preventing other user processes from starting. Specifically, in some examples, all user processes are terminated / blocked except for a set of predetermined processes that are considered necessary. In some examples, the necessary processes include wdg and init processes. The amount of power consumed by the CPU depends on its busyness, which in turn depends on the number and type of user processes running. Therefore, reducing the number of user processes running on the CPU will further reduce the amount of power consumed thereby. In some examples, the pseudo sleep mode includes both reducing the CPU frequency and terminating the user process.

[0017] Turning now to the drawings, various apparatus, systems, and methods in accordance with aspects of the present disclosure will be described.

[0018] Figure 1 1 is a block diagram conceptually illustrating an example networking device 100. The networking device 100 may be, for example, a switch, a router, an access point, or any other networking device configured to provide a communication interface (wireless and / or wired) to interconnect computing devices, as will be appreciated by those of ordinary skill in the art. Figure 1 The specific shapes, sizes or other structural details are not intended to be accurate or to scale. Figure 1 The illustrated networking device 100 is an example, and implementations of the networking device 100 may have a different number and arrangement of the illustrated components, and may also include other portions not shown.

[0019] like Figure 1 As shown, the networking device 100 includes a SoC 110, a first external communication interface 140, and a power supply unit (PSU) 180. In some examples, the networking device 100 also includes one or more second external communication interfaces 170.

[0020] The first external communication interface 140 and the second external communication interface 170 are configured to communicatively connect the networked device 100 to other electronic devices (e.g., computing devices, other networked devices, etc.). For example, the first and / or second communication interfaces 140, 170 may include ports for receiving connectors of electrical and / or optical communication cables, wireless interfaces, or any other type of physical communication interface. For example, the interfaces 140, 170 may include an Ethernet interface including an RJ45 port, an optical communication interface including an optical transceiver, a USB communication interface including a USB port, a wireless communication interface including a radio transceiver (e.g., a Wi-Fi interface), or any other desired physical communication interface. The first external communication interface 140 is distinguished from one or more second external communication interfaces 170 (if present) in that the first external communication interface 140 is an interface through which a wake-up command is communicated to the networked device 100. In some examples, the first external communication interface 140 is also an interface for communicating a sleep command. (Sleep and wake-up commands will be described in more detail below). For example, the first external communication interface 140 may be an interface connected to a network controller, and network control and configuration commands are communicated through the interface.

[0021] The power supply unit (PSU) 180 is configured to provide power to the components of the networked device 100. The PSU 180 includes one or more power supply devices that are configured to receive input power from a power source, such as a mains power source or a power distribution unit, and convert the power into a form suitable for use by the networked device 100. The power supply devices of the PSU 180 may include an AC to DC converter, an AC to DC converter, protection devices (e.g., overcurrent protection, overvoltage protection, etc.), and / or other power supply components that participate in, control, or otherwise facilitate the supply of power to the networked device 100. Figure 1 In the figure, the power provided by the PSU 180 is represented by a dotted arrow, and the data communication path is represented by a solid arrow. The PSU of the networking device is familiar to those of ordinary skill in the art, so the PSU 180 is not described in detail here.

[0022] SoC 110 includes circuits configured (e.g., programmed) to perform various operations of controlling the networked device 100. SoC 110 includes a CPU 120 and a memory 125. As is familiar to those of ordinary skill in the art, CPU 120 includes one or more processors. Memory 125 may include volatile memory (e.g., RAM), non-volatile memory (e.g., flash memory), or both. CPU 120 may execute instructions stored in memory 125. SoC 110 also includes a plurality of internal SoC modules integrated into SoC 110, including an internal PHY 130 and one or more other internal SoC modules 160. Internal PHY 130 is configured to control the physical layer operation of the first external communication interface 140. For example, in an embodiment where the first external communication interface 140 is an Ethernet interface, PHY 130 will be an Ethernet PHY. Other SoC modules 160 may include one or more other functional modules of the SoC, which may include a module that controls the second external communication interface 170 (if present), a module that provides peripheral functions, or any other SoC modules familiar to those of ordinary skill in the art

[0023] SoC 110 also includes pseudo sleep mode logic 150. Pseudo sleep mode logic 150 is configured to cause SoC 110 to perform operations associated with the pseudo sleep mode described herein. Specifically, in some examples, pseudo sleep mode logic 150 is configured to perform operations 151 and 156, which will be described in more detail below. As used herein, "logic" refers to dedicated hardware, software instructions stored in a memory and coupled to a processor capable of executing instructions, or some combination thereof. Therefore, in some examples, pseudo sleep mode logic 150 includes instructions stored in memory 125, which can be executed by CPU 120 to perform operations 151 and 156, in some examples, pseudo sleep mode logic 150 includes dedicated hardware configured to perform operations 151 and 156, and in some examples, pseudo sleep mode logic 150 includes some combination of the above operations.

[0024] As described above, the pseudo sleep mode logic 150 is configured to perform operations 151 and 156. Operation 151 includes causing the networked device 100 to enter a pseudo sleep mode in response to receiving a sleep command (which may be received via the first external communication interface 140 in some examples). As described above, in the pseudo sleep mode, one or more internal SoC modules 160 (except the CPU 120, the memory 125, and the PHY 130) are powered off. In some examples, in the pseudo sleep mode, all internal SoC modules 160 except the CPU 120, the memory 125, and the PHY 130 are powered off. In addition, in some examples, in addition to powering off the internal SoC modules, in the pseudo sleep mode, one or more second external communication interfaces 170 (if present) are also powered off. In some examples, all second external communication interfaces 170 that exist are powered off (ie, all external communication interfaces except the first external communication interface 140 are powered off). These measures reduce the amount of power consumed by the networked device while still allowing the integrated PHY 130 to remain powered on and monitor the wake-up signal.

[0025] In some examples, in addition to powering off the internal SoC module 160 and / or the second external interface 170, the pseudo sleep mode according to operation 151 also includes additional power saving measures. For example, in some embodiments, the pseudo sleep mode may also include reducing the frequency parameter of the CPU from the normal operating value of the frequency parameter. The frequency parameter may directly or indirectly control the operating frequency of the CPU. For example, the frequency parameter may directly set the frequency, or may set a target frequency around which the actual frequency may vary, or may be the high or low end point of the frequency range of the actual frequency variation. For example, if the CPU has a basic frequency and a maximum enhanced frequency, the actual frequency of the CPU may vary between these two values, and in such an example, the frequency parameter reduced in the pseudo sleep mode may be the basic frequency, the maximum (e.g., enhanced) frequency, or both the basic and maximum (enhanced) frequencies. Some CPUs may include multiple processors and / or multiple cores, and in some cases, the processors and / or cores may have different frequency parameter settings. In this case, the reduction of the frequency parameter may include a reduction of the frequency parameter for only one core or processor, for all cores or all processors, or for a certain combination of cores or processors.

[0026] As another example, in some embodiments, the pseudo sleep mode may also include terminating all user processes that are running when entering the pseudo sleep mode, and thereafter preventing new user processes from running for the duration of the pseudo sleep mode, except for a set of predetermined processes that are considered necessary and are therefore allowed to continue and / or start running during the pseudo sleep mode. In some examples, a set of processes that are considered necessary and allowed to continue running may include init and wdg processes. These additional power saving measures can further reduce the amount of power consumed by the networked device 100, especially the SoC 110.

[0027] Operation 156 includes responding to a wake-up command (received via the first external communication interface 140) so that the networked device 100 exits the pseudo sleep mode (also referred to as wake-up). The wake-up includes at least repowering the second external communication interface 170 (if present), repowering the previously powered-off SoC module 160, and resuming normal operation. In the example of reducing the CPU frequency in the pseudo sleep mode, the wake-up may further include returning the CPU frequency to its normal value (or normal range). In the example where the user process is terminated and blocked in the pseudo sleep mode, the wake-up may further include allowing the user process to start running in the normal process, and in some cases, actively restarting or resuming the process that was terminated when entering the sleep mode.

[0028] Now turn to Figure 2 , another example networking device 200 will be described. Networking device 200 is one example configuration of networking device 100. Components of networking devices 100 and 200 that are identical or similar to each other are given reference numerals having the same last two digits, such as 110 and 210. The above description of the components of networking device 100 is applicable to similar components of networking device 200, and thus repeated description of certain aspects of these components that have been described above is omitted below. Although networking device 200 is one example configuration of networking device 100, networking device 100 is not limited to networking device 200.

[0029] like Figure 2 As shown, the networking device 200 includes a SoC 210 (which is an example configuration of the SoC 110), a first external communication interface 240 (which is an example configuration of the first external communication interface 140), an example second external communication interface 270 (which is an example configuration of the second external communication interface 170), and a PSU 280 (which is similar to the PSU 180).

[0030] exist Figure 2 In the example shown, the first external communication interface 240 is an Ethernet communication interface and therefore includes one or more ports 241 (eg, Figure 2Each port may include a connector ("jack") configured to receive a complementary connector ("plug") of an Ethernet cable. For example, port 241 may include a female connector in the form of an RJ45 (also known as 8P8C) jack configured to receive a complementary male connector in the form of an RJ45 (8P8C) plug.

[0031] exist Figure 2 In the example shown, the second communication interface 270 includes a USB communication interface 271 and a Wi-Fi communication interface 272. According to any of the various USB standards, the USB communication interface 271 includes one or more USB ports configured to receive a USB plug. The Wi-Fi communication interface 272 may include an antenna and associated circuitry that facilitates sending and / or receiving Wi-Fi signals via the antenna. For example, the Wi-Fi communication interface 272 may include a portion (or all) of a Wi-Fi transceiver. As another example, the Wi-Fi communication interface 272 may include a Wi-Fi front-end module (FEM), which may include a collection of devices that amplify and route signals between an antenna and the SoC 210, such as a power amplifier, a low noise amplifier, a filter, and a switch.

[0032] Notice, Figure 2 The configuration of the first external communication interface 240 and the second external communication interface 270 shown in is merely an illustrative example, and in other examples of the networked device 100, the number and type of external communication interfaces provided may be different. Specifically, any number of second external communication interfaces may be provided, including zero, one, two, three or more. In addition, the first external communication interface is not limited to an Ethernet interface, and the second external communication interface is not limited to a USB and / or Wi-Fi interface. Specifically, any type of communication interface may be used as the first communication interface, and any type of communication interface may be used as the second communication interface.

[0033] SoC 210 includes a CPU 220 and a memory 225. SoC 110 also includes a plurality of SoC modules integrated into SoC 210, including an Ethernet PHY 230 and a plurality of other SoC modules 260. Ethernet PHY 230 is configured to control the physical layer operation of the first external communication interface 240. Other SoC modules 260 include a Wi-Fi module 261 that controls a Wi-Fi communication interface 272. The Wi-Fi module 261 may include a Wi-Fi PHY and a Wi-Fi MAC. SoC module 260 may further include a USB module 263 to control the USB interface 271. SoC module 260 may also include a PCIe module 262 that controls a peripheral component interconnect express (PCIe) function (e.g., implementing a PCIe 2.0 specification root complex (RC)), a security processing unit (SPU) 264 that provides cryptographic and security functions, a power management controller (PMC) module 265 that provides power management functions, or any other SoC module.

[0034] Notice, Figure 2 The configuration of the SoC module 260 shown in FIG. 1 is merely an illustrative example, and in other examples of the networked device 100, the number and type of SoC modules 260 may be different. Any type of SoC module desired may be used, including Figure 2 A subset of one or more SoC modules 260 shown in Figure 2 One or more SoC modules not shown or any combination of these modules.

[0035] like Figure 2 As shown, SoC 210 also includes pseudo sleep mode logic 250. Pseudo sleep mode logic 250 is configured to cause SoC 210 to perform operations associated with pseudo sleep mode. Specifically, pseudo sleep mode logic 250 is configured to perform operations 252 to 255, which constitute an example configuration of the above-mentioned operation 151. Operation 252 includes detecting the reception of a sleep command. For example, operation 252 may include monitoring the first external communication interface 240 to receive a sleep command. The sleep command may include any predetermined signal that is recognized by the networked device as an instruction to enter a pseudo sleep mode. In some examples, the sleep command is the same as a command that can be used to cause different networked devices to enter different forms of sleep modes (such as the above-mentioned full sleep mode). In this way, in some examples, depending on the capabilities and configuration of the device receiving the command, the same single command can be used to cause a pseudo sleep mode (in a device that can do so) or a full sleep mode (in a device that can do so). For example, this can allow a network administrator to place multiple devices in sleep mode via a single command without having to distinguish which devices can execute a normal sleep mode and which devices can execute a pseudo sleep mode.

[0036] In response to receiving the sleep command, the pseudo sleep mode logic 250 causes the networking device 200 to enter the pseudo sleep mode, which includes executing operations 252 to 255. In operation 252, the pseudo sleep mode logic 250 powers off all second external communication interfaces 270. Figure 2 In the example of , the second external communication interface 270 includes a USB interface 272 and a Wi-Fi interface 272. In addition, in operation 252, the pseudo sleep mode logic 250 powers off all additional SoC modules 260 except the CPU 220, the memory 225, and the PHY 230. In operation 254, as described above, the frequency of the CPU 220 is reduced. In operation 255, as described above, all user processes are terminated except for a predefined set of processes. In some examples, the execution of operations 252 to 255 by the pseudo sleep mode logic 250 may correspond to the method 400 described below.

[0037] Although not shown, the pseudo sleep mode logic 250 also performs operations similar to the above-described operation 156, including detecting a wake-up command and, in response, waking up the networked device 200 by undoing / reversing operations 252 through 255. For example, the pseudo sleep mode logic 250 may perform operations corresponding to the method 500 described below. Like a sleep command, a wake-up command may include any predetermined signal recognized by the networked device as an instruction to wake up from a pseudo sleep mode, and in some examples may be the same as a wake-up command used to wake up a different networked device from a different form of sleep (such as the above-described full sleep mode).

[0038] Now turn to Figure 3 , an example computer program product is described. The computer program product includes a non-transitory computer-readable storage medium 1125 storing instructions 1151 and 1156. These instructions 1151 and 1156 include computer-readable instructions (e.g., software, firmware, etc.) corresponding to operations 151 and 156, respectively. In other words, instructions 1151 and 1156 can be executed by one or more processors of SoC 210 (e.g., a processor of CPU 220 and / or a processor of PHY 230), and when executed, cause the execution of operations 151 and 156, respectively. Therefore, the storage medium 1125 and the instructions 1151 and 1156 stored thereon constitute an example configuration of the pseudo-sleep mode logic 150. More specifically, instruction 1151 includes instructions for entering a pseudo-sleep mode in response to receiving a sleep command (similar to operation 151), and instruction 1156 includes instructions for waking up from a pseudo-sleep mode in response to receiving a wake-up command (similar to operation 156). Although not shown, in some examples, instructions 1151 also include instructions corresponding to operations 252 to 255 described above.

[0039] Now go to Figure 4, method 400 will be described. Method 400 may be performed by pseudo sleep mode logic 150 or 250. The operations performed in method 400 correspond to an example implementation of the above-described operation 151. The operations performed in method 400 also correspond to an example implementation of the above-described operations 252 to 255.

[0040] At block 402, a networked device monitors for a sleep command. For example, a first external communication interface may be monitored for a sleep command.

[0041] At block 404, a determination is made as to whether a sleep command has been received. If not, the process continues along the "no" branch and returns to block 402. If so, the process continues along the "yes" branch to block 406. Thus, blocks 402 and 404 form a loop in which the first external communication is continuously or periodically monitored for a sleep command, and the loop is interrupted when a sleep command is received.

[0042] At block 406, the networking device powers off one or more (in some cases, all) external communication interfaces except the first communication interface through which the sleep command was received. In addition, the networking device powers off one or more (in some cases, all) internal modules of the SoC except for an internal PHY that controls the first communication interface, a CPU of the SoC, and a memory of the SoC.

[0043] At block 408 , the networking device reduces the frequency of the CPU of the SoC.

[0044] At block 410 , the networking device terminates one or more (and in some cases, all) user processes running on the CPU, except for a set of predetermined processes deemed necessary (including init and wdg in some cases).

[0045] In some examples, block 408 is omitted. In some examples, block 410 is omitted. In some examples, blocks 408 and 410 are omitted.

[0046] In some examples, after completing block 410, the Figure 5 The method 500 shown in FIG. 5 is described below.

[0047] Figure 5 Method 500 is shown, which may be performed by pseudo sleep mode logic 150 or 250. The operations performed in method 400 correspond to one example implementation of operation 156 described above. Method 500 may be performed while the networked device is in pseudo sleep mode, such as after method 400 has been performed.

[0048] At block 502, the networking device monitors for a wake-up command. For example, the first external communication interface can be monitored for a wake-up command. In some examples, a signal received through the first external communication interface is received by an internal PHY (e.g., PHY 130 or 230), processed by the PHY into a CPU-readable form, and then forwarded from the internal PHY to the CPU. Thus, the CPU and the PHY can work together to monitor for receipt of a wake-up command.

[0049] At block 504, a determination is made as to whether a wake-up command has been received. If not, the process continues along the "no" branch and returns to block 502. If so, the process continues along the "yes" branch to block 506. Thus, blocks 502 and 504 form a loop in which the first external communication is continuously or periodically monitored for a wake-up command, and the loop is interrupted when a wake-up command is received.

[0050] At block 506, the networking device powers on all external communication interfaces and SoC modules that were previously powered off when entering the pseudo sleep mode. In some examples, the CPU that remains powered on in the pseudo sleep mode can cause the communication interfaces and SoC modules to be powered back on. The memory that also remains powered on in the pseudo sleep mode can store instructions that can be executed by the CPU to cause the CPU to perform these actions.

[0051] At block 508 , if the CPU frequency had been previously reduced in the pseudo sleep mode, the networking device returns the CPU frequency of the SoC to its normal value (or range).

[0052] At block 510, the networking device stops preventing the user process from running on the CPU. In addition, in some examples, the networking device resumes (e.g., starts executing / running) the user process that was previously terminated when entering the pseudo-sleep mode.

[0053] Now go to Figure 6, an example system 1000 will be described. System 1000 includes a network controller 1105 and a network 1109, and network 1109 includes one or more first networked devices 1100 and one or more second networked devices 1101. Networked devices 1100 and 1101 are communicatively connected to each other and / or to other electronic devices (not shown) to form network 1109. Network controller 1105 can be a computing device including a processor and a memory storing instructions, and can be configured to be used by a network administrator to control and configure networked devices 1100 and 1101 in network 1109, as is familiar to those of ordinary skill in the art. Specifically, network controller 1105 can be configured to send sleep and wake commands to networked devices 1100 and 1101 so that they enter a full sleep mode or a pseudo sleep mode depending on the ability of the device to receive commands. Specifically, the first networked device 1100 is configured to enter a pseudo sleep mode in response to receiving a sleep command, and the second networked device 1101 is configured to enter a full sleep mode in response to receiving a sleep command.

[0054] The first networking devices 1100 may each include one of the above-mentioned networking devices 100 or 200. Specifically, the first networking devices 1100 each include a SoC 1110 (which may be similar to the SoC 110), an internal PHY 1130 (similar to the PHY 130) that controls a communication interface, and a pseudo sleep logic 1150 (similar to the pseudo sleep logic 1150) through which a sleep / wake command is received from the system controller 1105. The first networking device 1100 may also include the above-mentioned additional components, but for the sake of clarity, Figure 6 The pseudo sleep logic 1150 is configured to cause the first networked device 1100 to enter the pseudo sleep mode in response to receiving a sleep command and to wake up from the pseudo sleep mode in response to receiving a wake up command, as described above with respect to the networked devices 100 and 200 .

[0055] Each of the second networking devices 1101 includes a SoC 1102, an external PHY 1103 that controls a communication interface, and a sleep logic 1104, through which a sleep / wake-up command is received from a system controller 1105. Unlike the internal PHY 1130 of the first networking device 1100, the external PHY 1103 of the second networking device 1101 is separated from the SoC 1102 and is external to the SoC 1102. Therefore, each second networking device 1101 is capable of entering a full sleep mode, which includes completely powering off its SoC 1102. Specifically, the sleep logic 1104 is configured to cause the second networking device 1100 to enter a full sleep mode and power off the SoC 1102 in response to receiving a sleep command. In this full sleep mode, the external PHY 1103 remains powered on and monitors the receipt of a wake-up signal. The sleep logic 1104 is configured to wake up the device from the full sleep mode in response to receiving a wake-up command.

[0056] It is worth noting that in the system 1000, the network controller 1105 uses the same sleep command to make the first networked device 1100 and the second networked device 1101 enter the sleep mode, wherein the first networked device 1100 enters the pseudo sleep mode and the second networked device 1101 enters the full sleep mode. Similarly, the network controller 1105 uses the same wake-up command to make the first networked device 1100 and the second networked device 1101 wake up from their respective sleep or pseudo sleep modes. In this way, the network controller 1105 does not necessarily need to know which networked devices have which capabilities regarding sleep mode or distinguish between these devices when issuing sleep and wake-up commands, but can issue the same sleep and wake-up commands to the entire network 1109.

[0057] In the above description, various types of electronic circuits are described. As used herein, "electronic" is intended to be broadly understood to include all types of circuits that utilize electricity, including digital and analog circuits, direct current (DC) and alternating current (AC) circuits, circuits for converting electricity into another form of energy, and circuits for using electricity to perform other functions. In other words, as used herein, there is no distinction between "electronic" circuits and "electrical" circuits.

[0058] It should be understood that both the general description and the detailed description provide examples that are illustrative in nature and are intended to provide an understanding of the present disclosure without limiting the scope of the present disclosure. Various mechanical, compositional, structural, electronic and operational changes may be made without departing from the scope of the present specification and claims. In some cases, in order not to confuse the examples, known circuits, structures and techniques are not shown or described in detail. The same numbers in two or more drawings represent the same or similar elements.

[0059] In addition, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context indicates otherwise. In addition, the terms "include", "comprise", "include", etc. specify the presence of the features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups. Unless otherwise specified, the components described as coupled may be directly coupled electronically or mechanically, or they may be indirectly coupled via one or more intermediate components. Unless the context of the specification indicates otherwise, mathematical and geometric terms are not necessarily intended to be used according to their strict definitions, as one of ordinary skill in the art will understand that, for example, substantially similar elements that function in a substantially similar manner may easily fall within the scope of a descriptive term, even if the term also has a strict definition.

[0060] And / or: Sometimes the phrase "and / or" is used here in conjunction with a list of items. This phrase means that any combination of the items in the list - from a single item to all of the items and any permutation in between - is included. So, for example, "A, B, and / or C" means "one of {A}, {B}, {C}, {A, B}, {A, C}, {C, B}, and {A, C, B}."

[0061] Elements and related aspects described in detail with reference to one example may be included in other examples not specifically shown or described, wherever feasible. For example, if an element is described in detail with reference to one example, but not described with reference to a second example, the element may still be claimed to be included in the second example.

[0062] Unless otherwise stated herein or implied by the context, when approximate terms such as "substantially," "approximately," "about," "approximately," and the like are used, this should be understood to mean that mathematical precision is not required, but rather refers to a range of variation that includes, but is not limited to, the stated value, property, or relationship. Specifically, in addition to any ranges expressly stated herein, if any, the range of variation implied by the use of such approximate terms includes at least any insignificant variations, as well as those variations that are typical in the relevant art for the type of item in question due to manufacturing or other tolerances. In any case, unless otherwise stated, the range of variation may at least include values ​​within 1% of the stated value, property, or relationship.

[0063] In view of the disclosure herein, further modifications and alternative examples will be apparent to those of ordinary skill in the art. For example, the devices and methods may include additional components or steps that are omitted from the illustrations and descriptions for operational clarity. Therefore, the description should be interpreted as being merely illustrative and is intended to teach those skilled in the art the general manner of implementing this teaching. It should be understood that the various examples shown and described herein are exemplary. Elements and materials, and the arrangement of these elements and materials, may replace those illustrated and described herein, parts and processes may be reversed, and certain features of this teaching may be used independently, all of which will be apparent to those skilled in the art who benefit from the description herein. Changes may be made to the elements described herein without departing from the scope of this teaching and the appended claims.

[0064] It is to be understood that the particular examples set forth herein are non-limiting and that modifications in structure, dimensions, materials, and methods may be made without departing from the scope of the present teachings.

[0065] Other examples from this disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification and examples are to be considered exemplary only, and the following claims are to be given their fullest scope, including equivalents, under applicable law.

Claims

1. A networking device, comprising: one or more communication interfaces; System on chip (SoC), including: processor, memory, internal PHY module and one or more additional internal SoC modules; as well as Pseudo sleep mode logic, configured as: detecting receipt of a sleep command and, in response, causing the networking device to enter a pseudo sleep mode in which at least one of the one or more additional internal SoC modules is powered off while the internal PHY module remains powered on; and Receipt of a wake-up command is detected while the networked device is in the pseudo sleep mode, and in response, the networked device is caused to exit the pseudo sleep mode.

2. The networking device according to claim 1, in, The one or more additional internal SoC modules include a plurality of additional internal SoC modules; and Wherein, in the pseudo sleep mode, all of the plurality of additional internal SoC modules are powered off, while the processor, the memory, and the internal PHY module remain powered on.

3. The networking device according to claim 1, in, The one or more communication interfaces include a first communication interface and one or more second communication interfaces, the first communication interface being configured to receive a wake-up command; as well as Wherein, in the pseudo sleep mode, at least one of the one or more second communication interfaces is powered off, while the first communication interface remains operable.

4. The networking device according to claim 3, in, The one or more second communication interfaces include a plurality of second communication interfaces; and Wherein, in the pseudo sleep mode, all of the plurality of second communication interfaces are powered off.

5. The networking device according to claim 1, in, In the pseudo sleep mode, a frequency parameter of the processor is reduced relative to a normal value of the frequency parameter.

6. The networking device according to claim 1, in, The pseudo sleep mode logic is configured to terminate any user processes that are running when entering the pseudo sleep mode, and to prevent new user processes from running while in the pseudo sleep mode, except for a predetermined set of processes.

7. The networking device according to claim 1, in, The predetermined set of processes includes an init process and a wdg process.

8. The networking device according to claim 1, in, The one or more communication interfaces include a first communication interface and one or more second communication interfaces, the first communication interface being configured to receive a wake-up command; wherein, in the pseudo sleep mode, at least one of the one or more second communication interfaces is powered off, while the first communication interface remains operable; wherein, in the pseudo sleep mode, a frequency parameter of the processor is reduced relative to a normal value of the frequency parameter; and The pseudo sleep mode logic is configured to terminate any running user process when entering the pseudo sleep mode, and prevent new user processes from running when in the pseudo sleep mode, except for a predetermined set of processes.

9. The networking device according to claim 8, in, The one or more additional internal SoC modules include a plurality of additional internal SoC modules, and the one or more second communication interfaces include a plurality of second communication interfaces; and Wherein, in the pseudo sleep mode, all of the plurality of additional internal SoC modules and all of the plurality of second communication interfaces are powered off.

10. The networking device according to claim 8, in, The predetermined set of processes includes an init process and a wdg process.

11. A system comprising: A network, the network comprising the networked device as claimed in claim 1 and a second networked device; as well as a network controller connected to the network and configured to send a sleep command to the networked device and the second networked device; Wherein, in response to the sleep command, the networking device enters the pseudo sleep mode, and the second networking device enters a full sleep mode, wherein a system on a chip (SoC) of the second networking device is completely powered off.

12. A non-transitory computer-readable medium storing instructions executable by a processor of a network-connected device, the instructions being configured to, when executed, cause the processor to: detecting receipt of a sleep command at the networking device, and in response, causing the networking device to enter a pseudo sleep mode, wherein the networking device comprises a system on a chip (SoC), the SoC comprising a processor, a memory, an internal PHY module, and one or more additional internal SoC modules, and in the pseudo sleep mode, at least one of the one or more additional internal SoC modules is powered off while the internal PHY module remains powered on; and Receipt of a wake-up command is detected while the networked device is in the pseudo sleep mode, and in response, the networked device is caused to exit the pseudo sleep mode.

13. The non-transitory computer readable medium of claim 12, in, The one or more additional internal SoC modules include a plurality of additional internal SoC modules; and Wherein, in the pseudo sleep mode, all of the plurality of additional internal SoC modules are powered off, while the processor, the memory, and the internal PHY module remain powered on.

14. The non-transitory computer readable medium of claim 12, in, The networked device comprises a first communication interface and one or more second communication interfaces, the first communication interface being configured to receive the wake-up command; as well as Wherein, in the pseudo sleep mode, at least one of the one or more second communication interfaces is powered off, while the first communication interface remains operable.

15. The non-transitory computer readable medium of claim 14, in, The one or more second communication interfaces include a plurality of second communication interfaces; and Wherein, in the pseudo sleep mode, all of the plurality of second communication interfaces are powered off.

16. The non-transitory computer readable medium of claim 12, in, In the pseudo sleep mode, a frequency parameter of the processor is reduced relative to a normal value of the frequency parameter.

17. The non-transitory computer readable medium of claim 12, in, The instructions further cause the processor to terminate any user processes that are running when entering the pseudo sleep mode, and to prevent new user processes from running while in the pseudo sleep mode, except for a predetermined set of processes.

18. The non-transitory computer readable medium of claim 17, in, The predetermined set of processes includes an init process and a wdg process.

19. The non-transitory computer readable medium of claim 12, in, The networked device comprises a first communication interface and one or more second communication interfaces, the first communication interface being configured to receive the wake-up command; wherein the one or more additional internal SoC modules include a plurality of internal SoC modules; wherein, in the pseudo sleep mode, all of the second communication interfaces and all of the internal SoC modules are powered off, while the processor, the memory, and the internal PHY module remain powered on, and the first communication interface remains operational; wherein, in the pseudo sleep mode, a frequency parameter of the processor is reduced relative to a normal value of the frequency parameter; and Wherein, in the pseudo-sleep mode, all user processes except a predetermined group of processes are terminated.

20. A method comprising: detecting receipt of a sleep command at a networking device, and in response, causing the networking device to enter a pseudo sleep mode, wherein the networking device comprises a system on a chip (SoC), the SoC comprising a processor, a memory, an internal PHY module, and one or more additional internal SoC modules, and in the pseudo sleep mode at least one of the one or more additional internal SoC modules is powered off while the internal PHY module remains powered on; and Receipt of a wake-up command is detected while the networked device is in the pseudo sleep mode, and in response, the networked device is caused to exit the pseudo sleep mode.

Images