Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/10—Current supply arrangements
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/12—Arrangements for remote connection or disconnection of substations or of equipment thereof
• • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
  • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
  • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
  • Y02D30/00—Reducing energy consumption in communication networks
  • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

• This invention is related to media access controllers, and more specifically, to a method of implementing a power saving feature in a media access controller by placing one or more clocks of the controller in an idle mode during times of low packet activity.
• the Internet has brought a significant number of commercial interests online in order to tap an enormous source of potential customers. Billions of dollars are being invested on hardware, software, and infrastructure to further this potential market bonanza.
• the infrastructure hardware comprises routers and switches for redirecting data packets through the maze of data networks so that the manufacturer can reach the customer, and vice versa. When these data networks fail due to hardware failure, or any number of other causes, the cost to both the customer and the manufacturer can be significant.
• a primary cause of hardware failure is heat. As data transmission speeds increase, so does the amount of power required to process that data. Most high speed microprocessors are now being shipped with cooling fans to keep the device from burning up from the stress of processing an ever-increasing amount of data. However, other devices must be in place to get that data to and from the Internet or local network. With Gigabit Ethernet just around the corner, network interface devices will now be stressed more heavily with the increased data flow, and the use of mechanical cooling methods can be problematic. A power-saving architecture is needed to extend the lifetime of these devices by providing more efficient power consumption.
• the present invention disclosed and claimed herein in one aspect thereof, comprises a media access controller having a power-saving feature.
• the controller comprises a receive logic circuit for receiving incoming data from a physical interface device and processing the incoming data for transmission to a frame processor, and a transmit logic circuit for receiving outgoing data of the frame processor and processing the outgoing data for transmission to the physical interface device.
• a power management control logic operatively connects to each of the receive logic circuit and the transmit logic circuit to control the receive logic circuit and the transmit logic circuit in a first mode or a second mode.
• the power management control logic controls the media access controller in the first mode to conserve power by stopping operation of substantial portions of both the receive and transmit logic circuits, and in the second mode, which is a full power mode, by running both the receive and transmit logic circuits.
• FIG. 1 illustrates a block diagram of a disclosed embodiment
• FIG. 2 illustrates a flow chart of general event-activity processing, according to a disclosed embodiment
• FIG. 3 illustrates a more detailed flow chart of the power saving feature in accordance with a receive event
• FIG. 4 illustrates a more detailed flow chart of the power saving feature in accordance with a transmit event
• FIG. 5 illustrates a block diagram of the clock sources when using a variety of media independent interfaces
• FIG. 6 illustrates a gate diagram of an RMII implementation, according to the disclosed novel embodiments.
• FIG. 7 illustrates a system block diagram having a plurality of power-saving MAC controllers.
• FIG. 1 illustrates a general block diagram of a MAC controller 100 and general interface connections therefrom to both a frame processor (FP) 102 and a physical (PHY) interface 104.
• the MAC controller 100 processes basic data flow between the FP 102 and the PHY interface 104.
• the MAC controller 100 is placed in full operation (or run mode) in response to one or more detected "events.”
• Both the receive logic and the transmit logic of the MAC controller 100 are activated in response to the detection of either a receive event or a transmit event.
• both the receive logic and the transmit logic are placed in the power-savings mode when neither a receive event nor a transmit event is detected.
• the detection of incoming packets by the MAC controller 100 from either of the FP 102 or the PHY interface 104 causes the MAC controller 100 to be transitioned from a power-savings mode to a fully operational mode.
• the receive portion of the MAC controller 100 will be discussed from the perspective of the data being received from the physical interface 104 through the MAC controller 100 to the FP 102, and with the MAC controller 100 starting from an initial idle state.
• the MAC controller 100 In order to process incoming data from the PHY interface 104 to the FP 102, the MAC controller 100 must transition from the power-savings mode to the run mode. This operational transition occurs in response to an event signal from the PHY interface 104. In response to this event signal, the MAC controller 100 initiates a corresponding "activity," and completes this activity before determining whether to transition back to the idle state.
• This event signal is the carrier sense signal of the PHY interface 104 used in accordance with common protocols such CSMA/CA (Carrier Sense Multiple Access/Collision Avoidance) and CSMA/CD (Carrier Sense Multiple Access/Collision detection).
• CSMA/CA Carrier Sense Multiple Access/Collision Avoidance
• CSMA/CD Carrier Sense Multiple Access/Collision detection
• the carrier sense signal is placed on the network medium by a transmitting network device as a prelude to sending data packets, and is detected by the PHY interface 104, resulting in a corresponding signal being sent across one or more receive interface lines 106 from the PHY interface 104 to the MAC controller 100.
• the receive PHY interface lines 106 accommodate data and control signals between the MAC controller 100 and the PHY interface 104.
• the buffer 108 Prior to the portions of the receive logic of the MAC controller 100 "waking up" in response to the carrier sense signal, data may already be received into a buffer 108.
• the buffer 108 is operational at all times (as it receives pulses from a continuously-running system clock 109) and functions to temporarily hold the incoming data packets from the PHY interface 104 until the receive logic of the MAC controller 100 transitions from the power-saving mode to the fully operational run mode (e.g., in one or two clock signals).
• the buffer 108 comprises a series of pipelined flip-flops (not shown) which provide sufficient buffering action until the receive logic becomes fully operational, and then passes the data to internal receive control logic of the MAC controller 100 for processing.
• the buffer 108 connects to the system clock 109 over one or more clock lines 1 12, which system clock 109 is onboard the MAC controller 100 and runs continuously to keep the buffer 108 active at all times to receive incoming data packets from the PHY interface 104.
• the system clock also drive portions of logic of the FP 102, and connects thereto across FP system clock lines 113.
• a power management logic block 114 embodied in the MAC controller 100 is employed to perform the power-saving function, and connects to one or more of the receive PHY interface lines 106 to sense the carrier sense event signal of the PHY interface 104. In response thereto, the power management logic 114 performs the function of waking-up the required logic functions of the MAC controller 100 (i.e., from the idle mode to run mode). More specifically, the power management logic 114 is operational at all times, and receives clock pulses from one or more clock sources depending upon the type of PHY interface 104 utilized. Selector logic 116 (e.g., a multiplexer) connects to select the appropriate clock source corresponding to the particular type of interface used.
• Selector logic 116 e.g., a multiplexer
• the reference clock 110 of the PHY interface 104 is utilized to drive the internal TX CLK 118 and RX CLK 130.
• a raw clock source 111 is used, which raw signals are both raw TX clock signals and raw RX clock signals from the PHY interface 104.
• the raw TX clock signals drive the TX CLK 118 and the raw RX clock signal drives the RX CLK 130.
• the TX CLK 118 is used as the source clock in the Mil or GPSI implementation, since it more closely follows the raw TX clock signals.
• the system clock 109 could be used, however, it would require more synchronizer logic, and there is a potential for more latency between the time of the detected event and the time that the MAC logic 100 starts functioning. If an SMII (Serial Mil), or GMII (Gigabit Mil) or XGMII (Extended GMII) implementation is utilized, the reference clock 110 and the raw RX clock portion of the raw clock source 111 are utilized. The reference clock signal is used to generate the TX clock out signal directed back to the PHY interface 104, and also generates the TX CLK for the MAC control logic 100. When using the additional clock signals (the reference clock 110 and the raw clock source 111) the control logic can become more complex in order to synchronize the signals between the clock sources (110 and 111).
• SMII Serial Mil
• GMII Gigabit Mil
• XGMII Extended GMII
• the selector 116 connects to the external PHY reference clock 110 across one or more clock lines 122, the raw clock source 111 across one or more clock lines 120, and an onboard transmit clock (TX CLK) 118 across one or more clock lines 124.
• the output of the selector 116 connects to the power management logic 114 across one or more clock lines 128.
• the selector 116 may be implemented to operate independently to select the clock source corresponding to the particular type of PHY interface 104 utilized, or may also be operated dependently from the power management logic 114 (interconnect lines not shown) such that if the power management logic 114 senses the type of PHY interface 104, the selector 116 will be controlled to select the appropriate clocking source.
• the wake-up function in the receive portion of the power management logic 114 is performed by gating both a gated receive clock (RX CLK) 130 across receive one or more clock control lines 132, and the TX CLK 118 across one or more clock lines 134.
• the RX CLK 130 provides clock signals to both a receive FIFO control block (RX FIFO Control) 136 and a receive control logic block (RX Control) 138.
• the RX Control logic 138 which receives data from the buffer 108 across buffer interface lines 140, formats the data for insertion into an asynchronous receive FIFO (Async RX FIFO) 142, and checks the status and integrity of the data.
• the RX Control logic 138 also interfaces to the RX FIFO Control logic 136 to provide control signals thereto. In response to the control signals received from the RX Control logic 136, the RX FIFO Control logic 136 synchronizes data input to the Async RX FIFO 142 via the RX Control logic 138.
• Control of the data being passed from the Async RX FIFO 142 to the FP 102 is coordinated across control interface lines 144 between the RX FIFO Control 136 of the MAC controller 100 to the FP 102.
• Data is passed along one or more receive data interface lines 146 from the Async RX FIFO 142 of the MAC controller 100 to the FP 102.
• Both the RX CLK 130 and the TX CLK 118 are turned off when the power management logic 114 makes a determination that all activities related to both the receive and transmit operations on the MAC control logic 100 have been completed.
• the Async RX FIFO 142 is asynchronous, it may continue to operate cooperatively with the FP 102 until the FP 102 has read the end-of-frame data, and the Async RX FIFO 142 has signaled that it is empty.
• the reference clock 1 10 When acting as the clock source, the reference clock 1 10 also provides timing pulses to a small portion of the RX FIFO Control logic 136 across one or more clocking lines 148, a small portion of a transmit FIFO control logic (TX FIFO Control) 150 over the clocking lines 152, and a few registers of both the Async RX FIFO 142 and an asynchronous transmit FIFO (Async TX FIFO) 154 (the clock lines not shown for the latter two sets of logic).
• TX FIFO Control transmit FIFO control logic
• Async TX FIFO asynchronous transmit FIFO
• the transmit logic of the MAC controller 100 operates to receive "outgoing" data from the FP 102, and processes it for transmission onto the PHY interface 104.
• the FP 102 sends a transmit signal to the transmit logic of the MAC controller 100 when the FP 102 is about to commence the transmission of frame packets to the PHY interface 104.
• This transmit signal is perceived by the power management logic 114 as a second type of event.
• the power management logic 114 wakes-up the transmit logic of the MAC controller 100 by gating the gated TX CLK 118.
• a second activity is initiated-the general process of preparing and transmitting packets from the FP 102 to the physical interface 104.
• This second activity includes outputting data to the Async TX FIFO 154 of the MAC controller 100 across one or more transmit interface lines 156, and coordinating this data transfer by communicating control signals between the MAC controller 100 and the FP 102 across one or more FP transmit control interface lines 158 to the TX FIFO Control logic 150.
• Data packet transmission timing is provided by the gated TX CLK 118 which receives start and stop signals across one or more transmit clock lines 134 from the power management block 114.
• the TX CLK 118 provides timing signals to both the TX FIFO Control logic 150 and a transmit control logic block (TX Control) 160.
• the TX Control logic 160 provides the data pathway from the Async TX FIFO 154 across physical interface transmit lines 162 to the PHY interface 104, and the control signals to the TX FIFO Control logic 150 to synchronize data insertion into the Async TX FIFO 1 4 from the FP 102. Control signals from the TX Control logic 160 also communicate data transmit status to the power management logic 114. Both the RX CLK 130 and the TX CLK 118 are implemented to match the ethernet receive and transmit rates, respectively. The second activity (transmit) ends when frame transmission from the FP 102 ends.
• Methods for determining when this occurs are when the interframe gap time exceeds a predefined limit, and the Async TX FIFO 154 is empty.
• the MAC controller 100 utilizes independent clock domains. Since the RX/TX FIFOs (142 and 154, respectively) are asynchronous, and control of the RX/TX Clock logic (130 and 118, respectively) is gated, a substantial portion of the logic of the MAC controller 100 can be placed in idle mode (i.e., stopped). When a valid link is detected between the MAC controller 100 and the PHY interface 104, the disclosed power saving method saves power by shutting down during the idle times which occur between extended packet transmissions.
• the disclosed architecture embraces a more robust application which triggers on the extended absence of data packets being either received or transmitted, representing a significant reduction in power consumption of the MAC circuits.
• a GIGA ethernet MAC controller operates at a high system speed of 125 MHz, which high speed has an impact on chip lifetime, this lifetime impacted by runtime power consumption and implemented cooling mechanisms.
• the capability of selectively shutting down portions of the MAC controller 100 during low packet activity prolongs the life of the MAC circuits without impacting packet throughput.
• the disclosed architecture is also applicable to 10G ethernet.
• the disclosed embodiment provides a power savings method whereby the power management logic 114 of the MAC controller 100 turns both the RX CLK 130 and the TX CLK 118 on together in response to a detected event and then turns both of the clocks (RX CLK 130 and TX CLK 118) off in unison when no more activities are being processed.
• the power management logic 114 could be implemented to control the RX CLK 130 and TX CLK 118 independently, such that the RX CLK 130 and its associated receive logic can be operating to process incoming packet data from the PHY interface 104 while the TX CLK 118 and its associated transmit logic is idle (i.e., no data is available for processing from the FP 102 to the PHY interface 104).
• the RX CLK 130 and its associated receive logic could be placed in idle mode due to the lack of incoming packets, while the TX CLK 118 and its associated transmit logic is in run mode to process packets for transmission to the PHY interface 104.
• both the receive and transmit portions could be simultaneously in idle mode or in run mode, as in the embodiment disclosed hereinabove.
• a more robust logic design includes three capabilities: RX-driven events on the receive logic of the MAC controller 100, TX-driven events on the transmit logic of the MAC controller 100, and RX/TX-driven events which are part of the logic which monitors the network medium for packet activity (in CSMA/CD implementations).
• the RX/TX-driven events can be driven by only the TX event when in a full duplex regime.
• FIG. 2 illustrates a flow chart of the general aspects of a preferred embodiment. Discussion of the general process begins with the assumption that the system is operating in an idle state (i.e., the power management logic 114 has both the RX CLK 130 and the TX CLK 118 of the MAC controller 100 in a stopped mode). Flow begins at a Start bloc!:, and moves to a decision block 200 to determine if a predefined event has occurred. The number of events which can be detected is limited only by the discretion of the oesigner of the MAC controller 100.
• Flow continues to a decision block 206 to determine if the detected event was related to receiving data from the PHY interface 104. If so, flow is out the "Y" path to a function block 208 to begin processing the corresponding activities of that receive event. Flow continues to a decision block 210 to determine when those receive activities have been completed. If the activities have not been completed, flow is out the "N" path to a function block 212 to continue running the receive/transmit clocks (130 and 118) so that the activities can finish. The output of function block 212 then loops back to the input of decision block 210 to continue monitoring for the completion of all activities. If all receive/transmit activities have been completed, flow is out the "Y" path of decision block 210 to a function block 214 to stop the receive/transmit clocks (130 and 118) in order to place the MAC controller 100 in the power-savings mode.
• decision block 200 If the event, as first detected in decision block 200, was not a receive event, flow is out the "N" path of decision block 206 to a decision block 216 to determine if the event is a transmit event. If so, flow is out the "Y" path to a function block 218 to begin processing the corresponding activity. Flow continues to the decision block 210 to determine if all activities are completed. Flow processing then continues in accordance to that which is described hereinabove. On the other hand, if the detected event was not a transmit event, flow is out the "N" path of decision block 216 to a function block 220 to take action in accordance with a possible erroneous detection.
• This action may comprise sending a Resend Frame request, or entering a standby state, or setting a flag to indicate that a frame detection error occurred, or any other actions which may be employed.
• Flow is then to the function block 214 to stop both the RX CLK 130 and the TX CLK 118.
• the flow chart only depicts two events which can be detected. However, the disclosed method is not limited to two events, but may have more events which can be detected, at the discretion of the designer.
• flow is back to the input of decision block 200 to continue monitoring for the occurrence of the receive/transmit events.
• a detected receive event can cause the MAC controller 100 to be placed in run mode. While in run mode, a transmit event from the FP 102 can be detected which also causes the power management logic 114 to maintain the receive/transmit clocks in run mode.
• the detection of both a receive event and a transmit event has the same net effect of starting of the receive/transmit clocks (130 and 118). Thus, it is possible that multiple events and corresponding activities could be processed simultaneously.
• an event triggers an activity which completes one job.
• the receive/transmit clocks (130 and 1 18) are started, and maintained through completion of the corresponding activity. Since a network communication transaction normally accommodates many frames per second (and perhaps in both directions), multiple transmit/receive events and activities may occur simultaneously. Therefore, before the receive/transmit clocks can be stopped due to the completion of one activity, a global check must be made to determine if other events or activities are still in-progress. If so, the clocks have to be maintained in run mode until all events and activities are complete. After all activities are complete, the clocks can be stopped (i.e., set back to idle mode) in order to save power, and to wait for another event.
• the detectable events and corresponding activities for the MAC controller 100 logic are as follows.
• the power management logic 114 interprets this as an event which indicates frames are forthcoming.
• the corresponding activity performed by the MAC control logic 100 is to transfer the received frame(s) to the FP 102.
• the activity is complete when the FP 102 reads the end-of-frame (EOF) data from the Async RX FIFO 142.
• Another event occurs when the MAC control logic 100 receives a Frame Transmit request signal from the FP 102.
• the corresponding activity performed by the MAC control logic 100 is to process the packets for the FP 102 and transmit them to the PHY interface 104.
• FIG. 3 illustrates a more detailed flow chart of the receive event and corresponding activities of the MAC controller 100, in accordance with the disclosed novel features. Discussion is premised on the assumption that the MAC controller is currently in an idle state.
• Flow begins at a starting point and moves to a decision block 300 to determine if a receive event has occurred, the receive event being the detection of a carrier sense signal from the PHY interface 104. If not, flow is out the "N" path and loops back to the input of decision block 300 to continue monitoring for the occurrence of the receive event. If an event has been detected, flow is out the "Y" path of decision block 300 to a function block 302 to start the RX CLK 110 (and the TX CLK 118). While the RX CLK 110 is being started, one or more data frames may have already arrived from the PHY interface 104 and been buffered into the buffer
• Flow is then to a function block 304 where the received packets are processed by the receive logic of the MAC controller 100.
• This processing includes clocking the data into the RX Control logic 138 to check for data status and data integrity, and then formatting it for insertion into the Async RX FIFO 142.
• the MAC controller 100 then transmits the frames to the FP 102. This is accomplished by the RX FIFO
• Control 136 communicating with the FP 102 to coordinate frame transmission from the Async RX FIFO 142.
• an end-of-frame (EOF) signal must be detected by the FP 102
• the Async RX FIFO 142 must be empty.
• flow is to a function block 306 to write EOF data into the Async RX FIFO 142, which EOF data is then detected by the FP 102.
• Flow is to a function block 308 to clear the receive pipeline signaling of the receive logic.
• Flow is then to a decision block 310 to determine if another receive event has been detected. If so, flow is out the "Y" path to the input of function block 304 to continue the packet processing cycle.
• the power management logic 1 14 monitors the processing of packets in both the receive logic and the transmit logic. The lack of packets to process in either the receive logic or the transmit logic triggers the power management logic 114 to perform a global check for any active events and activities prior to shutting down both of the clocks (130 and 118).
• FIG. 4 illustrates a more detailed flow chart of the power saving feature in accordance with a transmit event.
• Flow begins at a starting point and continues to a decision block 400 to determine if full duplex operation is warranted by the presence of incoming receive data to the receive logic. Since the receive logic can be triggered into operation independent of the transmit logic, and vice versa, it can be appreciated that the transmit operation can be initiated without the receive logic being in full operation. Therefore decision block 400 tests for a receive event as well. If full duplex operation is not required since a receive event has not been detected, flow is out the "N" path of decision block 400 to another decision block 402 to determine if a new job has started in the Async TX FIFO 154.
• the FP 102 begins the transmit process by writing start-of- frame data into the Async TX FIFO 154.
• flow is out the "Y" path to a function block 404 to start the TX CLK 118.
• the RX CLK 130 is also started.
• Flow is ther to a function block 406 where data processed from the FP 102 by the MAC controller 100 is written into the PHY interface 104.
• Flow continues to a decision block 408 to determine if the writing process is completed. If not, flow is out the "N" path to the input of the function block 406 to continue writing data into the PHY interface 104.
• flow is out the "Y" path of decision block 408 to a function block 410 to measure and load the interframe gap (IFG) time into a register.
• Flow is then to a decision block 412 to determine of the IFG time has expired. Expiration of this time indicates that no more packets from the FP 102 are likely to follow, and that the transmit (or write) process to the PHY interface 104 can be discontinued.
• the IFG time is measured for each pair of frames being processed by the transmit logic. If the IFG time has not expired, flow is out the "N" path of decision block 412 to the input of function block 410 to continue measuring the IFG time and loading it into a register for the interrogation process.
• flow is out the "Y" path to the input of function block 410 to continue the process of measuring the IFG time. If no more events and activities are being processed, flow is out the "N" path to a function block 418 to stop the TX CLK 118. Flow is then back to the input of decision block 400 to begin the process over by monitoring for any events. If decision block 400 does detect an event, flow is out the "Y" path to a function block 420 to start the TX CLK 118. The output of function block 420 then flows to the input of function block 410 to commence the measurement and loading of the IFG time.
• FIG. 5 illustrates a block diagram of the clock sources when using a variety of media independent interfaces.
• the source clock for the power management logic 114 is the reference clock 110 from the PHY interface 104.
• the source clock for the power management logic 114 is both the raw TX clock signals 500 and the raw RX clock signals 502 from the PHY interface device 104.
• the interface is, for example, a GMII or XGMII
• the source clock pulses for the power management 114 are obtained from both the reference clock 110 and the raw RX clock signals 502 of the PHY interface 104.
• a transmit clock output 504, as controlled by the power management logic 114, is also routed back to the PHY interface 104, in the instance where the Mil interface is either GMII or XGMII, and is not stopped. In any case, the power management logic 114 has control over both the RX CLK 130 and the TX CLK 118.
• the clock domain line 506 indicates that the receive FIFO logic 508 and the transmit FIFO logic 510 are clocked by respective RX CLK 130 and TX CLCK 118 during operation, and that portions of both the receive and transmit logic circuits (508 and 510) receive pulses from the system clock 109.
• FIG. 6 illustrates a gate diagram of an RMII implementation, according to the disclosed novel embodiments.
• the RMII reference clock signal 600 of the reference clock 110 is used as the clocking source for power management control in this device implementation.
• the RX CLK signal 602 and the TX CLK signal 604 are synchronized with the RMII reference clock signal 600 across respective clock lines 606 and 608.
• the RMII reference clock signal 600 also connects to clock a receive power saving flip-flop (RX Saving) 610 and transmit power saving flip-flop (TX Saving) 612 across respective clocking lines 614 and 616.
• Wake-up control signals for the RX Saving device 610 connect at a RX wake-up input 618, and the shutdown control input (RX act done) 620 provides shutdown control when no input packets are detected for processing receive activities from the PHY interface 104 to the FP 102.
• the TX Saving device 612 has at a TX wake-up input 622 when for placing the transmit logic into run mode when a write frame signal is detected from the FP 102, and a shutdown control input (TX act done) 624 provides shutdown control when no input packets are detected for processing transmit activities from the FP 102 to the PHY interface 104.
• a full duplex input allows full duplex operation control where available.
• FIG. 7 illustrates a system block diagram utilizing multiple subsystems each operable to run in a power-saving mode.
• a system e.g., a network switch
• a system 600 contains multiple subsystems (702, 704, 706, and 708) which is common in network devices such as routers, switches, hub, etc., each of which comprises the power-saving features disclosed hereinabove.
• the system 700 is operably disposed on a network medium 710 to route data traffic to one or more sub-networks (also called "subnets"), each distinct subnet associated with a respective one of the subsystems (702, 704, 706, or 708).
• sub-networks also called "subnets”
• the system 700 is configured with a central system power management controller 712, as shown, to control the gated clocks of each subsystem (702, 704, 706, and 708) over a subsystem data and control bus 714.
• implementation of the system power management module 712 negates the need to implement a separate power management logic block 114 in each subsystem (702, 704, 706, and 708).
• data frames placed on the medium are addressable to a predetermined subnet, requiring that only one of the subsystems (702, 704, 706, or 708) wake-up for processing of the data. For example, if data was placed on the medium 710 addressable to a first subnet in association with the first subsystem 702, a first subsystem physical interface 716 detects the carrier-sense signal and communicates the detection of that signal to the system power management logic 712 across a system PHY interface bus 718.
• the system power management logic 712 then gates a receive clock (not shown, but similar to RX CLK 110) of a MAC controller 720 of the first subsystem 702 to operate the receive logic (not shown, but similar to the receive logic RX Control 130, RX FIFO Control 136, and Async RX FIFO 142 disclosed hereinabove with respect to FIG. 1).
• the MAC controller 720 then signals its associated frame processor 722 that frame data is ready for frame processing, and transmits the data to the frame processor 722. Operation continues in the same manner for the transmit portion as that disclosed in FIG. 1, and for overall power-saving operation, in that the system management controller 712 may shutdown or run the gated receive/transmit clocks of the MAC controller 720 based upon the absence or presence of data.
• the system management controller 712 may shutdown or run the gated receive/transmit clocks of the MAC controller 720 based upon the absence or presence of data.
• each subsystem may be placed in idle mode
• the receive/transmit logic portion of a MAC controller 724 of subsystem 704 may be started in response to an event which requires operation of its receive logic. Therefore, different aspects of each subsystem may be in full-power operation while other portions of each subsystem are in the power-conservation mode.
• system 700 can omit the central system power management logic 712, since each subsystem (702, 704, 706, and 708) could contain its own separate power management logic, as disclosed hereinabove with respect to power management logic 1 14. Each subsystem module then operates independently in accordance with the predetermined events.
• the system contains both a central power management block 712, and separate power management blocks 114 for each subsystem (702, 704, 706, and 708) which operate cooperatively and in communication with each other to facilitate the disclosed power-savings features.
• this power-saving feature can be applied to the GPSI 7-bit interface, Mil, RMII, SMII, and GMII interfaces.
• the Mil is part of the Fast Ethernet specification, and replaces the lOBase-T ethernet's AUI (or Attachment Unit Interface).
• the Mil is used to connect the MAC layer 100 to the PHY layer 104.
• RMII reduces the interface between the MAC controller 100 application specific integrated circuit and the transceiver from 16 to 7 pins per port, while the SMII further reduces the interface to just 2 pins per port.

Applications Claiming Priority (3)

Publications (1)

Family

ID=22630020

Family Applications (1)

Country Status (7)

Families Citing this family (6)

Family Cites Families (2)

• 2000
  • 2000-12-18 AU AU22750/01A patent/AU2275001A/en not_active Abandoned
  • 2000-12-18 WO PCT/US2000/034344 patent/WO2001047188A2/en not_active Application Discontinuation
  • 2000-12-18 EP EP00986526A patent/EP1243098A2/de not_active Withdrawn
  • 2000-12-18 KR KR1020027007959A patent/KR20020077366A/ko not_active Application Discontinuation
  • 2000-12-18 DE DE1243098T patent/DE1243098T1/de active Pending
  • 2000-12-18 CN CN00818508A patent/CN1425232A/zh active Pending
  • 2000-12-20 TW TW089127373A patent/TW488136B/zh not_active IP Right Cessation

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events