112 and the communication link 116 according to the EEE mechanism. In such embodiments, when an alert signal or a wake signal is to be transmitted, the transceiver 156 is configured to power up transmit circuitry to transmit the alert signal and/or the wake signal via the communication link 116 during an alert window. Otherwise, the transceiver 156 keeps the transmit circuitry asleep during the quiet time periods, according to an embodiment. Additionally, the transceiver 156 is configured to power up receive circuitry in connection with each alert window so that the transceiver 56 is prepared to receive an alert signal and/or a wake signal during each alert window. Otherwise, the transceiver 156 keeps the receive circuitry asleep in between alert windows during the quiet time periods, according to an embodiment.

The communication device 108 also comprises MAC layer circuitry 166 that is configured to perform MAC layer actions corresponding to a MAC entity defined by the communication protocol (e.g., the IEEE 802.3 Standard). The MAC layer circuitry 166 is coupled to the PHY circuitry 152 and is configured to send packets to the PHY circuitry 152 for transmission via the communication link 116. The PHY circuitry 152 then transmits the packets via the communication link 116. Additionally, the PHY circuitry 152 is configured to receive packets via the communication link 112, and to provide the packets to the MAC layer circuitry 166. In an embodiment, the MAC layer circuitry 166 is coupled to the PHY circuitry 152 via a suitable media independent interface. In other embodiments, the MAC layer circuitry 166 is coupled to the PHY circuitry 152 via another suitable interface.

In some embodiments, the MAC layer circuitry 166 is coupled to a host processor (not shown) of the communication device 108. In some such embodiments, the MAC layer circuitry 166 receives packets from the host processor and sends the packets to the PHY circuitry 152 for transmission via the communication link 116; and the MAC layer circuitry 166 receives packets from the PHY circuitry 152, and provides the packets to the host processor, the packets having been received by the PHY circuitry 152 via the communication link 112.

The MAC layer circuitry 166 comprises a power save controller 170 that is configured to control the PHY circuitry 152 to transition the communication link 112 and the communication link 116 between the normal mode and the low power mode. In an embodiment, the power save controller 170 is configured to control the PHY circuitry 152 to transition the communication link 112 and the communication link 116 between the normal mode and the LPI mode according to EEE.

In an embodiment, when the communication link 116 is in the low power mode (e.g., the LPI mode) and in response to the power save controller 170 determining that the MAC layer circuitry 166 has one or more packets that are to be transmitted via the communication link 116, the power save controller 170 controls at least transmit circuitry of the PHY circuitry 152 to transition to the normal mode. In an embodiment, when the communication link 116 is in the normal mode and in response to the power save controller 170 determining that the MAC layer circuitry 166 has not received any packets that are to be transmitted via the communication link 112 for a suitable period of time, the power save controller 170 controls at least transmit circuitry of the PHY circuitry 152 to transition to the low power mode (e.g., the LPI mode).

The communication device 108 also comprises a time-sensitive communication controller 174 that is configured to provide time-sensitive packets to the MAC layer circuitry 166 for transmission via the communication link 116. In an embodiment, the time-sensitive communication controller 174 is configured to operate according to the PTP. In an embodiment, the time-sensitive communication controller 174 is configured to provide time-sensitive packets for controlling a component apparatus (e.g., an actuator, a camera, etc.) of a vehicle, industrial equipment, etc.

In an embodiment, the time-sensitive communication controller 174 is implemented in the host processor (not shown) of the communication device 108 discussed above. In other embodiments in which the communication device 108 includes the host processor, the time-sensitive communication controller 174 is implemented in another processor (e.g., a packet processor, an example of which is described below) of the communication device 108 that is separate from the host processor.

The communication device 108 also includes a preemptive wakeup controller 178 that is coupled to the time-sensitive communication controller 174 and the MAC layer circuitry 166. The preemptive wakeup controller 178 is configured to determine that the communication link 116 will be used for a time-sensitive communication at a future time and, in response, prompt the power save controller 170 to transition the communication link 116 from the low power mode to the normal mode prior to the future time so that the communication link 116 is in the normal mode when the future time occurs.

In some embodiments, the time-sensitive communication controller 174 is configured to inform the preemptive wakeup controller 178 of the future time at which the communication link 116 will be used for the time-sensitive communication. In some embodiments, the time-sensitive communication controller 174 maintains a schedule of when the communication link 116 will be used for the time-sensitive communications, and the preemptive wakeup controller 178 accesses the schedule to determine future times at which the communication link 116 will be used for the time-sensitive communications.

In some embodiments, the preemptive wakeup controller 178 generates control signals and provides the control signals to the power save controller 170 to prompt the power save controller 170 to transition the communication link 116 from the low power mode to the normal mode prior to the future time so that the communication link 116 is in the normal mode when the future time occurs. In some embodiments, the preemptive wakeup controller 178 generates a wakeup packet (to be described below) and provides the wakeup packet to the MAC layer circuitry 166, where the wakeup packet is configured to prompt the power save controller 170 to transition the communication link 116 from the low power mode to the normal mode prior to the future time so that the communication link 116 is in the normal mode when the future time occurs.

As discussed above, with a power saving mechanism such as EEE, when the communication link 116 is in the low power mode, there will be a variable delay between when a packet is received by the MAC layer circuitry 166 and when the communication link 116 is transitioned to the normal mode and ready to transmit the packet. Thus, if the time-sensitive communication controller 174 provides a time-sensitive packet to the MAC layer circuitry 166 while the communication link 116 is in the low power mode, there will be a variable delay between when the time-sensitive packet was provided to the MAC layer circuitry 166 and when the time-sensitive packet is transmitted on the communication link 116. On the other hand, because the preemptive wakeup controller 178 causes the communication link 116 to transition to the normal mode prior to when a time-sensitive packet is to be transmitted, the communication link 116 will already be in the normal mode when the MAC layer circuitry 166 receives the time-sensitive packet and thus the variable delay discussed above is avoided.

FIG. 2 is a simplified diagram of an example wakeup packet 200 that a communication device uses to transition a communication link from a low power mode to a normal mode prior to the communication link being used for a time-sensitive communication, according to an embodiment. In some embodiments, the wakeup packet 200 is used in the communication system 100 of FIG. 1, and FIG. 2 is described with reference to FIG. 1 for explanatory purposes. In other embodiments, the wakeup packet 200 is used in a suitable communication system different than the communication system 100 of FIG. 1. Also, the communication system 100 does not use a wakeup packet like the wakeup packet 200, according to some embodiments.

The wakeup packet 200 includes a header 204 and a payload 208. In an embodiment, the wakeup packet 200 corresponds to a MAC layer (sometimes referred to L2 layer) packet, and the header 204 corresponds to a MAC layer header. The header 204 includes a destination address (DA) field 212 and a source address (SA) field 216. The destination address field 212 includes a network address (e.g., a MAC address) of an intended recipient of the wakeup packet 200, and the source address field 216 includes a network address (e.g., a MAC address) of the communication device that is sending the wakeup packet 200. For example, when the communication device 104 is to send a time-sensitive packet to the communication device 108, the communication device 104 generates (e.g., the preemptive wakeup controller 144 generates) the wakeup packet 200 to include a network address (e.g., a MAC address) of the communication device 108 in the DA field 212 and a network address (e.g., a MAC address) of the communication device 104 in the SA field 216. As will be discussed further below, the DA field 212 is set to a value corresponding to a multicast address or a broadcast address when multiple communication links corresponding to multiple other communication devices are to transition to the normal mode, according to some embodiments.

The payload 208 of the wakeup packet 200 includes a command type field 228 that indicates a command selected from a set of multiple different commands associated with transitioning communication links between a normal mode and a low power mode, according to an embodiment. The multiple different commands include i) a wakeup command corresponding to transitioning one or more communication links from the low power mode to the normal mode, and ii) a nullify command corresponding to canceling a previous wakeup command to allow the one or more communication links to transition back to the low power mode. In other embodiments, the multiple different commands include a set of other suitable commands.

In some embodiments, a format of the payload 208 varies depending on the type of command indicated in the command type field 228. In other embodiments, the format of the payload 208 is the same for all commands indicated in the command type field 228.

In some embodiments, the command type field 228 is omitted and the wakeup packet 200 corresponds only to transitioning one or more communication links from the low power mode to the normal mode.

The payload 208 also includes a duration field 240 that indicates a minimum time duration for which the one or more communication links are to remain in the normal mode. In some embodiments, the duration field 240 is omitted. For example, the wakeup packet 200 itself signals that the one or more communication links are to remain in the normal mode for a predetermined and/or pre-negotiated minimum time duration, in an embodiment. For instance, the minimum time duration is predetermined/fixed and known a priori by the communication devices 104/108, or the communication devices 104/108 negotiate the minimum time duration prior to using the wakeup packet 200.

The payload 208 further includes a delay field 244 that indicates a delay time duration between a time at which a device receives the wakeup packet 200 and ii) a later time at which the device is to transition a communication link from the low power mode to the normal mode. In some embodiments, the delay field 244 is omitted. For example, delaying the time at which the device transitions the communication link is not permitted, in an embodiment. In another embodiment, the wakeup packet 200 itself signals that the transition is to be delayed a predetermined and/or pre-negotiated delay time, in an embodiment. For instance, the delay time is predetermined and fixed, or the communication devices 104/18 negotiate the delay time prior to using the wakeup packet 200.

In some embodiments, one or both of the duration field 240 and the delay field 244 are included in the payload 208 when the command type indicates the wakeup command, and one or both of the duration field 240 and the delay field 244 are omitted from the payload 208 when the command type field 228 indicates the nullify command.

Referring now to FIGS. 1 and 2, in response to the preemptive wakeup controller 144 determining that the communication link 112 and the communication link 116 will be used for time-sensitive communications at a future time, the preemptive wakeup controller 144 generates and provides a first wakeup packet 200 to the MAC layer circuitry 132. The preemptive wakeup controller 144 generates the first wakeup packet 200 with a network address of the communication device 108 in the DA field 212 and with a network address of the communication device 103 in the AA field 216. Additionally, the preemptive wakeup controller 144 with the command type field 228 set to indicate that the first wakeup packet 200 includes a wakeup command corresponding to transitioning one or more communication links from the low power mode to the normal mode. Additionally, the preemptive wakeup controller 144 generates the first wakeup packet 200 to include an indication of a suitable time duration in the duration field 240. Optionally, the preemptive wakeup controller 144 generates the first wakeup packet 200 to include an indication of a suitable delay time duration in the delay field 244.

In response to the MAC layer circuitry 132 receiving the first wakeup packet 200, the power save controller 136 prompts the PHY circuitry 120 to transition the communication link 116 from the low power mode to the normal mode. After the communication link 116 transitions to the normal mode, the transceiver 124 transmits the first wakeup packet 200 to the communication device 108 via the communication link 112.

In some embodiments, the preemptive wakeup controller 144 controls the power save controller 136 to transition the communication link 112 back to the low power mode after the minimum time duration that is indicated in the duration field 240 (or, in some embodiments in which the duration field 240 is omitted, after the minimum time duration that that is predetermined and/or pre-negotiated), at least when there is no other data (e.g., buffered in the MAC processor 132 and/or the PHY circuitry 120) waiting to be transmitted via the communication link 116. In other embodiments, the preemptive wakeup controller 144 allows the power save controller 136 to transition the communication link 112 back to the low power mode after the minimum time duration if and when the power save controller 136 determines that the communication link 112 should transition back to the low power mode.

The PHY circuitry 152 receives the first wakeup packet 200 and provides the first wakeup packet 200 to the MAC circuitry 166. The MAC circuitry 166 analyzes the header 204 (e.g., the DA field 212) of the first wakeup packet 200 and determines that the communication device 108 is the intended recipient of the first wakeup packet 200. The MAC circuitry 166 (or the host processor (not shown), or other suitable circuitry of the communication device 108) provides the first wakeup packet 200 to the preemptive wakeup controller 178. The preemptive wakeup controller 178 receives the first wakeup packet 200 and analyzes the command type field 228 to determine that the first wakeup packet 200 includes a wakeup command. Additionally, the preemptive wakeup controller 178 determines, based on the DA field 212 and the SA field 216, that the wakeup command corresponds to transitioning the communication link 116 from the low power mode to the normal mode. The preemptive wakeup controller 178 further determines a time duration for which the communication link 116 is to remain in the normal mode based on the duration field 240 in the first wakeup packet 200. Then, in response to receiving the first wakeup packet 200, the preemptive wakeup controller 178 prompts the power save controller 170 to transition the communication link 116 from the low power mode to the normal mode. Additionally, the preemptive wakeup controller 178 controls the power save controller 170 to keep the communication link 116 in the normal mode for the time duration indicated by the duration field 240 in the first wakeup packet 200. In some embodiments in which the duration field 240 is omitted, the preemptive wakeup controller 178 controls the power save controller 170 to keep the communication link 116 in the normal mode for a minimum time duration that is predetermined and/or pre-negotiated by the communication devices 104, 108.

If the first wakeup packet 200 includes the delay field 244, the preemptive wakeup controller 178 controls the power save controller 170 to transition the communication link 116 from the low power mode to the normal mode after a delay time period indicated by the delay field 244, according to an embodiment.

In an embodiment, if the preemptive wakeup controller 144 determines that the time sensitive communication(s) on the communication link 112 and/or the communication link 116 that prompted the first wakeup packet 200 are completed prior to the time duration indicated in the first wakeup packet 200 having expired, the preemptive wakeup controller 144 optionally generates and provides a second wakeup packet 200 to the MAC circuitry 132. The preemptive wakeup controller 144 generates the second wakeup packet 200 with the network address of the communication device 108 in the DA field 212 and with the network address of the communication device 103 in the AA field 216. Additionally, the preemptive wakeup controller 144 generates the second wakeup packet 200 with the command type field 228 set to indicate that the wakeup packet 200 includes a nullify command corresponding to canceling the wakeup command in the previous first wakeup packet 200.

In response to the MAC layer circuitry 132 receiving the second wakeup packet 200, the transceiver 124 transmits the second wakeup packet 200 to the communication device 108 via the communication link 112. After the transceiver 124 transmits the second wakeup packet 200, the power save controller 136 prompts the PHY circuitry 120 to transition the communication link 116 from the normal mode to the low power mode.

In some embodiments, the preemptive wakeup controller 178 controls the power save controller 170 to transition the communication link 116 back to the low power mode after the minimum time duration that is indicated in the duration field 240 (or, in some embodiments in which the duration field 240 is omitted, after the minimum time duration that that is predetermined and/or pre-negotiated), at least when there is no other data (e.g., buffered in the MAC processor 132 and/or the PHY circuitry 120) waiting to be transmitted via the communication link 116. In other embodiments, the preemptive wakeup controller 178 allows the power save controller 170 to transition the communication link 116 back to the low power mode after the minimum time duration if and when the power save controller 170 determines that the communication link 116 should transition back to the low power mode.

The PHY circuitry 152 receives the second wakeup packet 200 and provides the second wakeup packet 200 to the MAC circuitry 166. The MAC circuitry 166 analyzes the header 204 (e.g., the DA field 212) of the second wakeup packet 200 and determines that the communication device 108 is the intended recipient of the second wakeup packet 200. The MAC circuitry 166 (or the host processor (not shown), or other suitable circuitry of the communication device 108) provides the second wakeup packet 200 to the preemptive wakeup controller 178. The preemptive wakeup controller 178 receives the second wakeup packet 200 and analyzes the command type field 228 to determine that the wakeup packet 200 includes a nullify command. Additionally, the preemptive wakeup controller 178 determines, based on the DA field 212 and the SA field 216, that the nullify command corresponds to transitioning the communication link 116 from the normal mode to the low power mode prior to the time duration indicated in the first wakeup packet 200 has expired. Then, in response to receiving the second wakeup packet 200, the preemptive wakeup controller 178 prompts the power save controller 170 to transition the communication link 116 from the normal mode to the low power mode prior to the time duration indicated in the first wakeup packet 200 expiring.

As briefly discussed above, the preemptive wakeup controller 144 generates the wakeup packet 200 with the DA field 212 set to a value corresponding to a multicast address or a broadcast address when multiple communication links corresponding to multiple other communication devices are to transition to the normal mode, according to some embodiments. For instance, when the DA field 212 is set to a multicast/broadcast value, the wakeup packet 200 is propagated through a communication network, prompting multiple communication links to transition to the normal mode, according to some embodiments. If all communication links of a communication network are to transition to the normal mode, the preemptive wakeup controller 144 sets the DA field 212 to a broadcast address, and if communication links of only a section of the communication network are to transition to the normal mode, the preemptive wakeup controller 144 sets the DA field 212 to a multicast address that corresponds to the section of the communication network, according to an embodiment. When the preemptive wakeup controller 144 sets the DA field 212 to a unicast address, communication links along a path in the communication network to a network device having the unicast address are transitioned to the normal mode, according to an embodiment.

FIG. 3 is a simplified diagram of an example network switch 300, according to an embodiment. The network switch 300 includes many of the same or similar components as the communication device 104 and the communication device 108 of FIG. 1, and like-numbered elements are not described again in detail for purposes of brevity. Additionally, the network switch 300 is configured to generate and process wakeup packets such as the example wakeup packet of FIG. 2, according to some embodiments, and FIG. 3 is described with reference to FIG. 2 for explanatory reasons. In other embodiments, the network switch 300 is configured to generate and process other suitable wakeup packets that are different than the wakeup packet 200 of FIG. 2.

The network switch 300 includes multiple instances of the PHY circuitry 120 coupled to respective communication links 112/116. Each communication link 112 is for transmitting from the network switch 300 to another respective communication device (e.g., another network switch, a communication device like the communication device 104/108, etc.), and each communication link 116 is for receiving from the other respective communication device. Each instance of PHY circuitry 120 corresponds to a respective port of the network switch 300.

The PHY circuitry 120 are coupled to the MAC circuitry 132. Although one instance of the MAC circuitry 132 is illustrated in FIG. 3, in other embodiments the network switch 300 includes multiple instances of the MAC circuitry 132 coupled to respective sets of one or more PHY circuitry 120.

The network switch 300 includes a packet processor 304 that is configured to process header information in packets received via the communication links 112 to determine communication links 116 via which the packet is to be forwarded. In an embodiment, the packet processor 304 includes a forwarding database (not shown) that stores forwarding information comprising associations between network addresses and ports of the network switch 300. The packet processor 304 uses i) network address information in a header of a received packet (e.g., DA information), and ii) forwarding information in the forwarding database that corresponds to the network address in the received packet, to determine one or more ports via which the packet is to be transmitted.

FIG. 3 illustrates an example in which the network device 300 receives a wakeup packet 308 via the communication link 116-1, and the wakeup packet has the DA field 212 set to a multicast or broadcast value. Additionally, the command type field 228 is set to indicate that wakeup packet includes a wakeup command corresponding to transitioning one or more communication links from the low power mode to the normal mode. In response to receiving the wakeup packet 308 via the communication link 116-1, the network switch 300 transitions the communication link 112-1 to the normal mode in a manner the same as or similar to actions described above with reference to FIG. 1.

Additionally, the MAC circuitry 132 forwards the wakeup packet 308 to the packet processor 304. The packet processor 304 analyzes header information in the wakeup packet 308 and determines, at least based on the DA field 212 and forwarding information in the forwarding database, that the wakeup packet 308 is to be transmitted via one or more ports of the network switch 300. If the wakeup packet 308 is to be transmitted via more than one port, the packet processor 304 generates one or more additional instances of the wakeup packet 308.

The packet processor 304 provides one or more instances of the wakeup packet 308 to the MAC circuitry 132 along with information that specifies the communication links 116 via which the one or more instances of the wakeup packet 308 are to be transmitted. In an embodiment, the MAC circuitry 132 receiving the one or more instances of the wakeup packet 308 prompts the power save controller 136 to transition the one or more specified communication links 116 to the normal mode. In another embodiment, the preemptive wakeup controller 144 receives the information that specifies the communication links 116 via which the one or more instances of the wakeup packet 308 are to be transmitted, and in response the preemptive wakeup controller 144 prompts the power save controller 136 to transition the one or more specified communication links 116 to the normal mode. In embodiments in which the wakeup packet 308 includes duration information, the preemptive wakeup controller 144 controls the power save controller 136 to keep the one or more specified communication links 116 in the normal mode for a time duration indicated by the wakeup packet 308.

Additionally, the MAC circuitry 132 provides the one or more instances of the wakeup packet 308 to appropriate ones of the PHY circuitry 120, and after the specified communication links 116 have transitioned to the normal mode, the ones of the PHY circuitry 120 transmit the wakeup packet 308 via the specified communication links 116.

In response to receiving a subsequent wakeup packet that includes a nullify command, the network switch 308 forwards the subsequent wakeup packet with the nullify command via one or more ports in a similar manner. Additionally, after forwarding the subsequent wakeup packet via the one or more ports, the preemptive wakeup controller 144 prompts the power save controller 136 to transition the one or more specified communication links 116 to the power save mode, similar to the acts described with reference to FIGS. 1 and 2.

The network switch 300 acts similarly in response to receiving a wakeup packet with a unicast address in the DA field 212, but forwards the wakeup packet to at most one port that corresponds to the unicast address.

FIG. 4 is a flow diagram of an example method 400 of operation in a communication network that is used for time-sensitive communications, according to an embodiment. The method