Nothing Special   »   [go: up one dir, main page]

TWI379192B - Buffering techniques for power management - Google Patents

Buffering techniques for power management Download PDF

Info

Publication number
TWI379192B
TWI379192B TW97135495A TW97135495A TWI379192B TW I379192 B TWI379192 B TW I379192B TW 97135495 A TW97135495 A TW 97135495A TW 97135495 A TW97135495 A TW 97135495A TW I379192 B TWI379192 B TW I379192B
Authority
TW
Taiwan
Prior art keywords
buffer
communication
power
subsystem
power management
Prior art date
Application number
TW97135495A
Other languages
Chinese (zh)
Other versions
TW200933356A (en
Inventor
Jr-Shian Tsai
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US12/208,654 external-priority patent/US8112646B2/en
Application filed by Intel Corp filed Critical Intel Corp
Publication of TW200933356A publication Critical patent/TW200933356A/en
Application granted granted Critical
Publication of TWI379192B publication Critical patent/TWI379192B/en

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)
  • Power Sources (AREA)

Description

fl379192 九、發明說明 【發明所屬之技術領域】 本發明係關於用於電力管理之緩衝技術。 【先前技術】 用於諸如電腦系統之電子裝置之電力管理在保存能 量、管理散熱以及改善整體系統效能方面扮演了重要角 色。現代電腦系統以增加之趨勢被設計以用於無可靠外部 電源可用時之設定,以電力管理來保存重要能量。電力管 理技術允許電腦系統之特定元件之供電減少或處於睡眠模 式,其比工作操作時需較少電力,藉以於某段時間降低裝 置所消耗之總能量。對於行動裝置保存電池電力而言,能 量保存尤其重要。即使當可靠外部電源爲可用時,計算系 統內之精確電力管理可降低系統所產生之熱量,這可改善 系統之效能。一般而言,計算系統在較低環境溫度時具有 較好之效能,這是因爲關鍵元件可以較高速度執行而不會 損害其電路。因此,增強電子裝置之電力管理會有許多好 處。 【發明內容及實施方式】 一般而言,各種實施例係關於提供增強電力管理之緩 衝技術。特別地,一些實施例可關於在節點操作時從諸如 電池之能量儲存裝置保存能量之電力管理技術。例如於一 個實施例中,諸如網路裝置之設備可包含具有電力管理控 -4- 制器之電力管理模組,以及用於耦接至電力管理模組之受 管理電力系統。受管理電力系統可包含通訊次系統及計算 次系統。電力管理控制器可被配置成用以將通訊次系統及 計算次系統切換至低電力狀態,以保存能量。 於各種實施例中,第一節點之通訊次系統可被配置成 用以在通訊系統內處理及儲存從其它節點接收之資訊,藉 以增加第一節點之計算次系統之能量保存。於一些實施例 中’通訊次系統可延長一段時間,用於當計算次系統可藉 由緩衝封包及事件資訊而維持在低電力狀態,直到準備就 緒用於受計算次系統處理爲止。這樣可減少當處於低電力 狀態時傳送至計算次系統之中斷數目,其中每一中斷迫使 計算次系統重回高電力狀態,以服務中斷。有時候這種技 術稱爲「中斷結合J 。 例如於一個實施例中,通訊次系統可進一步包含傳收 器、緩衝器、水印產生器、以及緩衝器管理器。傳收器可 被配置成用以於網路上連通資訊。緩衝器可被耦接至傳收 器並被配置成用以於通訊閒置期間儲存傳收器之資訊封 包’用於產生計算閒置期間。例如,通訊閒置期間可代表 當通訊次系統不從網路接收(或期待接收)資訊之時間間 隔。例如’計算閒置期間可代表當計算次系統不從通訊次 系統接收(或期待接收)資訊之時間間隔。水印產生器可 親接至緩衝器,並被配置成用以產生可變接收臨限値。緩 衝器管理器可耦接至緩衝器及水印產生器,並被配置成用 以特別根據可變接收臨限値將所儲存之資訊封包從緩衝器 -5- 1379192 轉送至計算次系統。可根據改變通訊電力狀態資訊而以演 算方式導出可變接收臨限値,如以下所詳細說明者。以這 種方式,藉由實施允許通訊次系統及/或計算次系統進入 並維持於低電力狀態下之緩衝技術及/或邏輯,電力管理 模組可執行用於受管理電力系統之增強能量保存,同時維 持服務品質(QoS )及通訊次系統及/或計算次系統之其它 效能需求。說明並主張其它實施例。 各種實施例可包含一或更多元件。元件可包含被配置 用以執行特定操作之任何結構。因應給定之設計參數組或 效能限制所需,每一元件可被實施爲硬體、軟體或其任何 組合。雖然是利用舉例方式於特定拓撲中之有限元件數目 來說明實施例,但因應給定實施方式所需,該實施例可包 含替代拓撲中之更多或更少元件。必須注意者爲,對「一 個實施例」或「實施例」之任何參考內容係表示關聯該實 施例而說明之特性、結構或特徵係包含於至少一個實施例 中。本說明書中各處出現之用語「於一個實施例中」並不 一定參考相同實施例。 圖1表示通訊系統100之方塊圖。於各種實施例中, 通訊系統100可包含多個節點。依給定之設計參數組或效 能限制所需,節點一般可包含於通訊系統1 〇〇中之用於連 通資訊之任何物質或邏輯實體並可實施爲硬體、軟體或其 任何組合。雖然圖1可表示舉例之於特定拓撲中之有限節 點數目,但必須瞭解者爲,可於不同拓撲中使用更多或更 少之節點用於給定實施方式。 1379192 於各種實施例中,通訊系統丨〇〇可包含有線通訊系 統、無線通訊系統或其兩者之組合,或形成有線通訊系 統、無線通訊系統或其兩者之組合之部分。例如,通訊系 統100可包含~個或更多節點im—m,配置成用以於諸 如有線通訊連結140-1之一個或更多類型之有線通訊連結 上連通資訊。有線通訊連結14 0-1之例子可包含但不限於 電線、電纜、匯流排、印刷電路板(p C B )、乙太網路連 接、對等(P2P )連接、底板、光纖開關、半導體材料、 雙絞線、同軸電纜、光纖連接等等。通訊系統100亦可包 含一個或更多節點11 0-1 -m,配置成用以於諸如無線共享 媒體140-2之一個或更多類型之無線通訊連結上連通資 訊。無線共享媒體140-2之例子可包含但不限於無線電頻 道、紅外線頻道、射頻(RF )頻道、無線保真(WiFi ) 頻道、RF頻譜之一部分、及/或一個或更多授權或免授權 頻帶。於後者之例子中,無線節點可包含用於無線通訊之 一個或更多無線介面及/或元件,諸如一個或更多收音 機、傳送器、接收器、傳收器、晶片組、放大器、濾波 器、控制邏輯、網路介面卡(NIC )、天線、天線陣列等 等。天線之例子可包含但不限於內部天線、全向天線、單 極天線、雙極天線 '端饋天線 '循環極化天線、微條天 線、分集天線、雙天線、天線陣列等等。於一個實施例 中,特定裝置可包含多個天線之天線陣列,以實施各種適 應天線技術及空間分集技術。 如圖1之實施例所示,通訊系統1 〇〇包含多個節點 1379192 110-l-m。節點可包含或實施爲任何型式 或行動電子裝置或資源,包含網路裝置、網路端點 網路基礎建設設備、蜂巢式無線電電話網路設備、 統、電腦系統、電腦次系統、電腦、工作站、終端 -- 服器、個人電腦(PC )、膝上型電腦、超膝上型 : 可攜式電腦、手持電腦、個人數位助理(PDA)、蜂 話、智慧型電話、路由器、開關、橋接器、閘路、 # . 器設備、微處理器、積體電路、可程式邏胃 • (PLD)、數位訊號處理器(DSP)、處理器、電 輯閘、暫存器、微處理器、積體電路、半導體裝 片 '電晶體等等。於一些實施例中,一些節點110. 代表異質性網路裝置。例如於一個實施例中,一 11 0-l_m可包含使用諸如—個或更多電池之行動電 種行動電腦系統(例如膝上型電腦、手持電腦、智 話、蜂巢式電話等等)。 # 雖然—些節點1 ΙΟ-1-m可包含不同之網路裝置 每一個節點UO-1-m可包含如節點110-1-m所示一 之元件。例如,節點1 1 0 -1 - m可各包含各種電力 件,以實施電力管理方法,可操作用以執行節點1 - 之電力管理操作。例如於圖1所示之實施例中,第 101-1可包含耦接至電力管理模組130-1之受管理 統120-1。電力管理模組130-1可操作用於經由通 140-1、140-2於所建立之通訊連接之上與第二節點 節點1 10-2-m其中之一)連通電力狀態資訊。於— 之固定 設備、 處理系 機、伺 電腦、 巢式電 網路電 碧裝置 路、邏 置、晶 -1 -m 可 些節點 源之各 慧型電 ,但是 般數目 管理元 1 0 -1 - m 一節點 電力系 訊連結 (例如 般操作 -8- 1379192 中’電力管理模組130-1可管理第一節點no」之受管理 電力系統12〇-1之各種電力狀態。電力狀態資訊可包含第 —節點110-1之受管理電力系統120-1之—個或更多部分 之過去、目前或將來之電力狀態。如此,受管理電力系統 120-1之該部分可互換電力狀態資訊,以改善或增強第— 節點1 1 0 - 1之電力狀態管理。例如,電力管理模組1 3 〇 _ 1 可使受管理電力系統120-1之次系統210-1、230-1之間 之電力管理操作同步’諸如根據通訊次系統210-1之通訊 元件之操作或預期操作,使計算次系統230-1之計算元件 處於低電力狀態下經過一給定之電力狀態期間,反之亦 然。 雖然節點1 1 0 · 1圖1所示之唯一節點,以包含受管理 電力系統120-1及電力管理模組130-1,但必須瞭解者 爲,每一個節點ΙΙΟ-1-m可包含相同或類似受管理電力系 統120-1-π及電力管理模組130-1-p。例如,節點11〇_2 可包含耦接至電力管理模組130-2之受管理電力系統120-2;節點110-3可包含元件120-3、130-3等等。此外,參 照受管理電力系統120-1及電力管理模組1 30-1而提供之 結構及操作之說明及例子亦可應用於其它節點1 1 O-2-m中 之對應元件。受管理電力系統1 20-1 -η及電力管理模組 1 3 0-1 -ρ之範例實施例可參照圖2更詳細予以說明。 圖2表示受管理電力系統12〇及電力管理模組130之 更詳細區塊圖。於圖2所示之實施例中,受管理電力系統 120可包含通訊次系統210及計算次系統23 0。雖然圖2 -9- 1379192 可表示舉例之於特定配置中之有限數目之電力管理元件, 但必須瞭解者爲,可於不同配置中使用更多或更少之電力 管理元件用於給定實施方式。 於各種實施例中,受管理電力系統120可包含耗用電 源232之電力及適用於電力管理操作之節點110-l-m之任 何電氣或電子元件。電力管理技術允許電子裝置或系統 (例如電腦系統)之特定元件之供電下降或處於比主動操 作時需要較少電力之睡眠模式,藉以於某段時間降低裝置 所消耗之總能量。可藉由電力閘控及/或時脈閘控受管理 電力系統120之各種硬體元件來實施電力管理技術。 更具體而言,受管理電力系統120可包含可於各種電 力狀態操作之節點110-l-m之各種電氣或電子元件,其從 電源232拉引多種位準之電力,如受電力管理模組130之 電力管理控制器234所控制者。各種電力狀態可由任何數 目之電力管理方法來界定。於一些例子中,例如可根據先 進組構及電力介面(ACPI )系列規格(包含其後續內 容、各種版本及修改)來界定電力狀態。於一個實施例 中,例如可根據2005年12月30日之ACPI修訂版本 3 _ 0a (「ACPI 3.0a規格修定版」)來界定電力狀態。 ACPI系列規格界定電子裝置之多種電力狀態,諸如全球 系統狀態(Gx狀態)、裝置電力狀態(Dx狀態)、睡眠 狀態(Sx狀態)、處理器電力狀態(Cx狀態)、裝置及 處理器效能狀態(Px狀態)等等。必須瞭解者爲,可因 應給定之設計參數組及效能限制所需,實施改變電力位準 -10- 1379192 之其它電力狀態。本文並不在於限制實施例。 於一些實施例中,適用於電力管理操作之節點Π0-1-m之各種電氣或電子元件一般可分成群組或組織成通訊次 系統210及計算次系統230。然而可瞭解者爲,這是爲了 舉例明確說明而提供次系統2 1 0,230,但不限於此,受管 理電力系統120可包含適用於受電力管理模組130電力管 理操作之節點1 1 0-1 -m之各種電氣或電子元件。例如節點 1 10-1-m —般可包含電腦監視器或顯示器,諸如數位電子 顯示器或類比電子顯示器。數位電子顯示器之例子可包含 電子紙、數字管顯示器、真空螢光顯示器、發光二極體顯 示器、電場發光顯示器、電漿顯示面板、液晶顯示器、薄 膜電晶體顯示器、有機發光二極體顯示器、表面傳導電子 發射器顯示器、雷射電視顯示器、奈米碳管、奈米晶體顯 示器等等。類比電子顯示器之例子可包含陰極射管顯示 器。當操作系統偵測到電腦已有一段設定時間未從使用者 接收到輸入時,電腦監視器通常被設定成處於睡眠模式。 其它系統元件可包含數位相機、觸控螢幕、錄影機、錄音 機、儲存裝置、振動元件、振盪器、系統時鐘、控制器、 以及其它平台或系統結構設備。當這些其它系統元件不使 用時,這些元件亦可被設定處於睡眠或電力下降狀態,以 保存能量。視需要,電腦系統監視輸入裝置及喚醒裝置。 本文並不在於限制實施例。 於各種實施例中,受管理電力系統120可包含通訊次 系統210。通訊次系統210可包括各種通訊元件,配置成 -11 - 1379192 用以連通資訊並執行節點llO-hm之間之通訊操作。適用 之通訊元件之例子可包含設計用於在通訊連結140]、 140-2上連通資訊之任何電氣或電子元件,包含但不限於 收音機、傳送器、接收器、傳收器、晶片組、放大器、濾 波器、控制邏輯、介面、網路介面、網路介面卡 (NIC )、天線、天線陣列、數位訊號處理器、基頻處理 器、媒體存取控制器、記億體單元等等。 於各種實施例中’通訊次系統210-1可包含能於不同 通訊速率下操作之一個或更多傳收器2 04- 1 -r。傳收器 204-1-r可包含能於在通訊連結140-1、140-2之各種有線 媒體型式(例如銅、單模式光纖 '多模式光纖等等)及無 線媒體型式(例如RF頻譜)上傳送及接收資訊之任何通 訊元件。傳收器204- 1 _r之例子可包含各種基於乙太網路 之 PHY裝置,諸如快速乙太網路PHY裝置(例如 100Base-T、 100Base-TX、 100Base-T4、 1OOB ase-T2、 1 OOBase-FX、1 OOBase-SX、1 OOBaseBX 等等)、十億位元 乙太網路(GbE ) PHY 裝置(l〇〇〇Base-T、lOOOBase-SX 、 1 OOOBase-LX、 1 0 0 0 B as e - B X 1 0 、 1 OOOBase-CX、 1 000Base-ZX 等等)、10 GbE PHY 裝置(例如 lOGBase- SR 、 1 OGBase-LRM 、 1 OGBase-LR 、 1 OGBase-ER 、 lOGBase-ZR .、 1 0GBase-LX4、 1 0GBase-CX4、 1 OGBase-Fl379192 IX. Description of the Invention [Technical Field of the Invention] The present invention relates to a buffering technique for power management. [Prior Art] Power management for electronic devices such as computer systems plays an important role in preserving energy, managing heat dissipation, and improving overall system performance. Modern computer systems are designed to increase the trend to save important energy with power management when no reliable external power is available. Power management techniques allow the power supply to specific components of a computer system to be reduced or in a sleep mode, which requires less power than during operation, thereby reducing the total energy consumed by the device for a certain period of time. Energy conservation is especially important for mobile devices to conserve battery power. Even when a reliable external power source is available, precise power management within the computing system can reduce the amount of heat generated by the system, which can improve system performance. In general, computing systems perform better at lower ambient temperatures because critical components can be executed at higher speeds without damaging their circuitry. Therefore, there are many advantages to enhancing the power management of electronic devices. SUMMARY OF THE INVENTION In general, various embodiments are directed to providing a buffering technique for enhanced power management. In particular, some embodiments may be directed to power management techniques that conserve energy from an energy storage device such as a battery while the node is operating. For example, in one embodiment, a device such as a network device can include a power management module having a power management controller and a managed power system for coupling to the power management module. A managed power system can include a communication subsystem and a computing subsystem. The power management controller can be configured to switch the communication subsystem and the computing subsystem to a low power state to conserve energy. In various embodiments, the communication subsystem of the first node can be configured to process and store information received from other nodes within the communication system to increase the energy storage of the computing subsystem of the first node. In some embodiments, the communication subsystem can be extended for a period of time to maintain the low power state when the computing subsystem can be buffered and event information until ready for processing by the computing subsystem. This reduces the number of interrupts that are transferred to the computing subsystem when in a low power state, with each interrupt forcing the computing subsystem to return to a high power state to service the outage. Sometimes this technique is referred to as "interrupt combination J." For example, in one embodiment, the communication subsystem may further include a transceiver, a buffer, a watermark generator, and a buffer manager. The transceiver may be configured to use For communicating information on the network, the buffer may be coupled to the transceiver and configured to store the information packet of the transceiver during the idle period of the communication for generating a calculation idle period. For example, the communication idle period may represent The time interval during which the communication subsystem does not receive (or expect to receive) information from the network. For example, the calculation of the idle period may represent the time interval when the calculation of the secondary system does not receive (or expect to receive) information from the communication subsystem. Connected to a buffer and configured to generate a variable receive threshold. The buffer manager can be coupled to the buffer and watermark generator and configured to specifically address the variable receive threshold The stored information packet is transferred from the buffer-5-1379192 to the calculation subsystem. The variable reception threshold can be derived by calculation based on changing the communication power status information. As described in detail below, in this manner, the power management module can be implemented by implementing buffering techniques and/or logic that allows the communication subsystem and/or the computing subsystem to enter and remain in a low power state. Enhanced energy conservation of the managed power system while maintaining quality of service (QoS) and communication subsystems and/or other performance requirements of the computing subsystem. Other embodiments are illustrated and claimed. Various embodiments may include one or more components. Any structure configured to perform a particular operation may be included. Each element may be implemented as hardware, software, or any combination thereof, as required by a given set of design parameters or performance limitations, albeit by way of example in a particular topology. The finite element number is used to illustrate the embodiment, but this embodiment may include more or fewer elements in the alternative topology as needed for a given implementation. It must be noted that "one embodiment" or "an embodiment" Any reference to the features, structures, or characteristics described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" and " 1 shows a block diagram of a communication system 100. In various embodiments, communication system 100 can include multiple nodes. A node may generally be included in communication system 1 任何 for any substance or logical entity used for communication information and may be implemented as hardware, software, or any combination thereof, as required by a given set of design parameters or performance limitations. Although Figure 1 may represent a finite number of nodes exemplified in a particular topology, it must be understood that more or fewer nodes may be used in different topologies for a given implementation. 1379192 In various embodiments, the communication system can include a wired communication system, a wireless communication system, or a combination of both, or form part of a wired communication system, a wireless communication system, or a combination of both. For example, communication system 100 can include one or more nodes im-m configured to communicate information over one or more types of wired communication links, such as wired communication link 140-1. Examples of wired communication links 14 0-1 may include, but are not limited to, wires, cables, bus bars, printed circuit boards (P CB ), Ethernet connections, peer-to-peer (P2P) connections, backplanes, fiber optic switches, semiconductor materials, Twisted pair, coaxial cable, fiber optic connections, and more. Communication system 100 can also include one or more nodes 11 0-1 -m configured to communicate communications over one or more types of wireless communication links, such as wireless shared medium 140-2. Examples of wireless shared medium 140-2 may include, but are not limited to, a radio channel, an infrared channel, a radio frequency (RF) channel, a wireless fidelity (WiFi) channel, a portion of an RF spectrum, and/or one or more authorized or unlicensed bands. . In the latter case, the wireless node may include one or more wireless interfaces and/or components for wireless communication, such as one or more radios, transmitters, receivers, transceivers, chipsets, amplifiers, filters , control logic, network interface cards (NICs), antennas, antenna arrays, and more. Examples of antennas may include, but are not limited to, internal antennas, omnidirectional antennas, monopole antennas, dipole antennas, 'end-fed antennas', cyclically polarized antennas, microstrip antennas, diversity antennas, dual antennas, antenna arrays, and the like. In one embodiment, a particular device may include an antenna array of multiple antennas to implement various adaptive antenna techniques and spatial diversity techniques. As shown in the embodiment of Figure 1, the communication system 1 includes a plurality of nodes 1379192 110-l-m. A node may include or be implemented as any type or mobile electronic device or resource, including a network device, a network endpoint network infrastructure device, a cellular radio network device, a computer system, a computer subsystem, a computer, a workstation , terminal -- server, personal computer (PC), laptop, super laptop: portable computer, handheld computer, personal digital assistant (PDA), bee, smart phone, router, switch, bridge , gate, #. device, microprocessor, integrated circuit, programmable logic (PLD), digital signal processor (DSP), processor, gate, register, microprocessor, Integrated circuits, semiconductor packages, transistors, etc. In some embodiments, some nodes 110. represent heterogeneous network devices. For example, in one embodiment, a 110-l_m may include a mobile computer mobile computer system (e.g., a laptop, a handheld computer, a smart phone, a cellular telephone, etc.) using, for example, one or more batteries. # Although - some nodes 1 ΙΟ-1-m may contain different network devices Each node UO-1-m may contain elements such as nodes 110-1-m. For example, nodes 1 1 0 -1 - m may each include various power components to implement a power management method operable to perform power management operations of node 1 -. For example, in the embodiment shown in FIG. 1, the 101-1 may include the managed system 120-1 coupled to the power management module 130-1. The power management module 130-1 is operable to communicate power state information with one of the second node nodes 1 10-2-m over the established communication connection via the ports 140-1, 140-2. In the fixed equipment, processing system, servo computer, nested power grid, electric circuit, road, logic, crystal -1 - some of the node source of each type of power, but the general number of management elements 1 0 -1 - m One-node power system connection (for example, the power state of the managed power system 12〇-1 in the power management module 130-1 can manage the first node no in the operation -8- 1379192. The power status information can include The past, present or future power status of one or more portions of the managed power system 120-1 of the first node 110-1. Thus, the portion of the managed power system 120-1 is interchangeable with power status information, Improving or enhancing the power state management of the first node 1 1 0 - 1. For example, the power management module 13 3 〇 1 can power the secondary systems 210-1, 230-1 of the managed power system 120-1 The management operation synchronizes, such as during operation or expected operation of the communication element of communication subsystem 210-1, to cause the computing element of computing subsystem 230-1 to be in a low power state for a given power state, and vice versa. 1 1 0 · 1 Figure 1 The only node shown to include the managed power system 120-1 and the power management module 130-1, but it must be understood that each node ΙΙΟ-1-m may include the same or similar managed power system 120-1- π and power management module 130-1-p. For example, node 11〇_2 may include managed power system 120-2 coupled to power management module 130-2; node 110-3 may include component 120-3 130-3, etc. Further, the description and examples of the structure and operation provided with reference to the managed power system 120-1 and the power management module 1 30-1 can also be applied to other nodes 1 1 O-2-m. Corresponding components. Example embodiments of managed power system 1 20-1 -η and power management module 1 3 0-1 -ρ can be described in more detail with reference to Figure 2. Figure 2 shows managed power system 12 and power A more detailed block diagram of the management module 130. In the embodiment illustrated in Figure 2, the managed power system 120 can include a communication subsystem 210 and a computing subsystem 230. Although Figures 2-9-1379192 can represent examples. a limited number of power management components in a particular configuration, but must be known to be used in different configurations More or less power management components are used for a given implementation. In various embodiments, managed power system 120 can include any electrical or power that consumes power 232 and a node 110-lm that is suitable for power management operations. Electronic components. Power management techniques allow the power supply to a particular component of an electronic device or system (eg, a computer system) to drop or be in a sleep mode that requires less power than active operation, thereby reducing the total energy consumed by the device for a certain period of time. Power management techniques can be implemented by power gating and/or clock gating of various hardware components of managed power system 120. More specifically, the managed power system 120 can include various electrical or electronic components that can operate at various power states of the node 110-lm, which pull multiple levels of power from the power source 232, such as by the power management module 130. The controller of the power management controller 234. The various power states can be defined by any number of power management methods. In some instances, the power state can be defined, for example, according to the Advanced Fabric and Power Interface (ACPI) family of specifications, including their subsequent content, versions, and modifications. In one embodiment, the power state can be defined, for example, according to ACPI Revision 3_0a ("ACPI 3.0a Specification Revision") of December 30, 2005. The ACPI Series specification defines various power states of an electronic device, such as global system state (Gx state), device power state (Dx state), sleep state (Sx state), processor power state (Cx state), device and processor performance state. (Px status) and so on. It must be understood that other power states that change the power level -10- 1379192 can be implemented in response to a given set of design parameters and performance limitations. This document is not intended to limit the embodiments. In some embodiments, various electrical or electronic components of nodes Π0-1-m suitable for power management operations may generally be grouped or organized into a communication subsystem 210 and a computing subsystem 230. However, it is understood that this is to provide a secondary system 2 1 0, 230 for illustrative purposes, but is not limited thereto, and the managed power system 120 may include a node 1 1 0-1 suitable for power management operations of the power management module 130. -m of various electrical or electronic components. For example, node 1 10-1-m can generally include a computer monitor or display, such as a digital electronic display or an analog electronic display. Examples of digital electronic displays may include electronic paper, digital tube display, vacuum fluorescent display, light emitting diode display, electric field light emitting display, plasma display panel, liquid crystal display, thin film transistor display, organic light emitting diode display, surface Conducting electron emitter displays, laser television displays, carbon nanotubes, nano crystal displays, and the like. An example of an analog electronic display can include a cathode tube display. When the operating system detects that the computer has not received input from the user for a set period of time, the computer monitor is usually set to sleep mode. Other system components may include digital cameras, touch screens, video recorders, recorders, storage devices, vibrating elements, oscillators, system clocks, controllers, and other platform or system architecture devices. When these other system components are not in use, they can also be set to sleep or power down to conserve energy. The computer system monitors the input device and the wake-up device as needed. This document is not intended to limit the embodiments. In various embodiments, managed power system 120 can include communication subsystem 210. The communication subsystem 210 can include various communication components configured to -11 - 1379192 for communicating information and performing communication operations between the nodes 110-hm. Examples of suitable communication components can include any electrical or electronic component designed to communicate information over communication links 140], 140-2, including but not limited to radios, transmitters, receivers, transceivers, chipsets, amplifiers , filters, control logic, interfaces, network interfaces, network interface cards (NICs), antennas, antenna arrays, digital signal processors, baseband processors, media access controllers, cell units, and more. In various embodiments, the communication subsystem 210-1 can include one or more transceivers 204-1-r that can operate at different communication rates. The transceivers 204-1-r can include various wired media formats (eg, copper, single mode fiber 'multimode fiber, etc.) and wireless media types (eg, RF spectrum) that can be used in the communication links 140-1, 140-2. Any communication component that transmits and receives information. Examples of transceivers 204-1_r may include various Ethernet-based PHY devices, such as fast Ethernet PHY devices (eg, 100Base-T, 100Base-TX, 100Base-T4, 1OOB ase-T2, 1 OOBase) -FX, 1 OOBase-SX, 1 OOBaseBX, etc.), Gigabit Ethernet (GbE) PHY device (l〇〇〇Base-T, lOOOOBase-SX, 1 OOOBase-LX, 1 0 0 0 B As e - BX 1 0 , 1 OOOBase-CX, 1 000Base-ZX, etc.), 10 GbE PHY devices (eg lOGBase-SR, 1 OGBase-LRM, 1 OGBase-LR, 1 OGBase-ER, lOGBase-ZR ., 1 0GBase-LX4, 1 0GBase-CX4, 1 OGBase-

Kx、10GBase-T等等)、100 GbE PHY裝置等等。傳收器 2 04-1 -r亦可包含各種無線電或無線PHY裝置,諸如用於 行動寬頻通訊系統。行動寬頻通訊系統之例子包含但不限 -12- 1379192 於與電氣和電子工程學會(IEEE )標準相容之系統,尤其 諸如用於無線區域網路(WLAN )及其變化之IEEE 802.11標準、用於無線都會區域網路(WMAN)及其變化 之IEEE 802.16標準、用於行動寬頻無線存取(MBWA) 及其變化之IEEE 802.20標準。傳收器204- 1 -r亦可實施 爲各種其它型式之行動寬頻通訊系統及標準,諸如通用行 動電信系統(UMTS )系統系列標準及其變化、分碼多重 存取(CDMA ) 2000系統系列標準及其變化(例如 CDMA2000 lxRTT,CDMA2000 EV-DO,CDMA EV-DV 等 等)、由歐洲電信標準學會(ETSI )寬頻無線存取網路 (BRAN)所制定之高效能射頻都會區域網路 (HIPERMAN )系統系列標準及其變化、無線寬頻 (WiBro)系統系列標準及其變化、行動通訊之全球系統 (GSM) 與一般封包射頻服務 (GPRS)系統 (GSM/GPRS )系列標準及其變化、全球發展之增強資料 速率(EDGE)系統系列標準及其變化、高速下連結封包 存取(HSDPA)系統系列標準及其變化、高速正交分頻多 工(OFDM)封包存取(HSOPA)系統系列標準及其變 化、高速上連結封包存取(HSUPA)系統系列標準及其變 化等等。本文並不在於限制實施例。 於各種實施例中,控制器208可操作用於使用單—傳 收器(例如204-1)或多個傳收器204-1-r來切換通訊速 率。控制器2 0 8可實施爲能執行邏輯操作之任何計算元件 或邏輯裝置,諸如處理器 '微處理器、晶片組、控制器、 -13- 1379192 微控制器、嵌入式控制器、媒體存取控制器、基頻控制器 等等》傳收器204-l-r可個別地或集體地以不同之通訊速 率或連結速率操作。於一個實施例中,例如,單一傳收器 204-1能以各種通訊速率操作。於另一個實施例中,例 如,第一傳收器204- 1能以第一通訊速率操作,第二傳收 器204-2能以第二通訊速率操作等等。控制器20 8可將第 —傳收器204_1從第一通訊速率切換至第二通訊速率,或 從操作第一傳收器204- 1切換至操作第二傳收器204-2, 以完成所需之通訊速率。控制器208可根據控制策略來切 換通訊速率,例如根據諸如一個或更多能量效率乙太網路 (EEE )控制策略。控制器208亦可根據來自緩衝器管理 器216之指令來切換通訊速率。 於各種實施例中,通訊次系統210-1可包含受緩衝器 管理器216管理之一個或更多緩衝器206-1-t。緩衝器 206-1 -t可操作用以儲存由傳收器2 04-Ι-r所接收之網路封 包,或準備就緒供傳收器204-1 -r傳輸之用。例如,當通 訊次系統210-1或計算次系統230- 1進入低電力狀態且因 此無法連通或處理封包時,緩衝器206- 1 -t可用於緩衝封 包。於另一個例子中,緩衝器206-1-t可用於緩衝封包, 直到傳收器之通訊速率已經完全被切換或修改爲止,因爲 切換傳收器204- 1 -r之通訊速率通常不是即時的。例如緩 衝器206-1-t可被實施成標準先進先出(FIFO)序列。緩 衝器管理器216可實施各種型式之緩衝器邏輯,以管理緩 衝器206-1 -t之操作。 -14- 1379192 於各種實施例中,受管理電力系統120可包含計算次 系統230。計算次系統230可包括各種計算元件,配置成 用以處理資訊並執行節點1 1 0· 1 -m之計算操作。適用之計 算元件之例子可包含設計用於處理資訊之任何電氣或電子 元件,包含但不限於處理器、微處理器、晶片組、控制 器、微控制器、嵌入式控制器、時鐘、振盪器、音訊卡、 視訊卡、多媒體卡、周邊裝置、記憶體單元、記憶體控制 器、視訊控制器、音訊控制器、多媒體控制器等等》 於各種實施例中,電力管理模組 130可包含電源 232。電源232可配置成用以提供電力(一般而言)給節 點110-1-m之元件,且特別是受管理電力系統120。於一 個實施例中,例如電源2 3 2可操作用以提供變化位準之電 力給通訊次系統210及計算次系統230。於各種實施例 中,電源23 2可藉由可再充電電池來予以實施,諸如可移 除及可再充電鋰離子電池,以提供直流(DC)電,以及 交流(AC )轉接器,以從標準AC主電源拉引出電力。 於各種實施例中,電力管理模組130可包含電力管理 控制器234。電力管理控制器234 —般可控制受管理電力 系統120之電力消耗。於一個實施例中,電力管理控制器 234可操作用以根據特定之電力狀態控制提供至通訊次系 統2 1 0及計算次系統23 0之變化位準之電力。例如,電力 管理控制器234可修正、切換或轉變電源23 2提供給次系 統210、2 3 0之電力位準成爲較高或較低之電力位準,藉 以有效地修正次系統210、230之電力狀態。 -15- 1379192 於各種實施例中,電力管理模組130可包含一個或更 多電力控制定時器2 3 6。電力管理控制器234可使用電力 控制定時器2 3 6以維持特定電力狀態一給定電力狀態期 間。電力狀態期間可代表節點或節點一部分在給定之電力 狀態時所界定之時間間隔。例如,電力管理控制器2 3 4可 將計算次系統230從高電力狀態切換至低電力狀態一界定 之時間間隔’且當過了該時間間隔,便將計算次系統230 切換回到高電力狀態。Kx, 10GBase-T, etc.), 100 GbE PHY devices, etc. The transceiver 2 04-1 -r can also include various radio or wireless PHY devices, such as for mobile broadband communication systems. Examples of mobile broadband communication systems include, but are not limited to, -12-1379192 in systems compatible with the Institute of Electrical and Electronics Engineering (IEEE) standards, such as the IEEE 802.11 standard for wireless local area networks (WLAN) and its variations, The Wireless Metropolitan Area Network (WMAN) and its changing IEEE 802.16 standard, the IEEE 802.20 standard for Mobile Broadband Wireless Access (MBWA) and its changes. The transceivers 204-1-r can also be implemented in various other types of mobile broadband communication systems and standards, such as the Universal Mobile Telecommunications System (UMTS) system family of standards and their variations, the Code Division Multiple Access (CDMA) 2000 system family of standards. And its changes (such as CDMA2000 lxRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.), high-performance RF metropolitan area network (HIPERMAN) developed by the European Telecommunications Standards Institute (ETSI) Broadband Wireless Access Network (BRAN) System series standards and their changes, wireless broadband (WiBro) system series standards and their changes, mobile communications global system (GSM) and general packet radio frequency service (GPRS) system (GSM/GPRS) series of standards and their changes, global development The Enhanced Data Rate (EDGE) System family of standards and their variations, the High Speed Linked Packet Access (HSDPA) system family of standards and their variations, the High Speed Orthogonal Frequency Division Multiplexing (OFDM) Packet Access (HSOPA) system family of standards and Its changes, high-speed uplink packet access (HSUPA) system series standards and their changes. This document is not intended to limit the embodiments. In various embodiments, controller 208 is operable to switch the communication rate using a single-receiver (e.g., 204-1) or a plurality of transceivers 204-1-r. The controller 208 can be implemented as any computing element or logic device capable of performing logical operations, such as a processor 'microprocessor, chipset, controller, -13-1379192 microcontroller, embedded controller, media access The controller, baseband controller, etc. "receivers 204-lr can operate individually or collectively at different communication rates or link rates. In one embodiment, for example, a single transceiver 204-1 can operate at various communication rates. In another embodiment, for example, the first transceiver 204-1 can operate at a first communication rate, the second transceiver 204-2 can operate at a second communication rate, and the like. The controller 20 8 can switch the first transceiver 204_1 from the first communication rate to the second communication rate, or switch from operating the first transceiver 204-1 to operating the second transceiver 204-2 to complete the The required communication rate. Controller 208 can switch the communication rate according to a control strategy, such as in accordance with, for example, one or more energy efficient Ethernet (EEE) control strategies. Controller 208 can also switch the communication rate based on instructions from buffer manager 216. In various embodiments, communication subsystem 210-1 can include one or more buffers 206-1-t that are managed by buffer manager 216. The buffers 206-1-t are operable to store network packets received by the transceivers 204-Ι-r or are ready for transmission by the transceivers 204-1-r. For example, when the secondary system 210-1 or the secondary system 230-1 enters a low power state and is therefore unable to communicate or process the packet, the buffers 206-1-t can be used to buffer the packet. In another example, the buffers 206-1-t can be used to buffer the packet until the communication rate of the transceiver has been completely switched or modified, since the communication rate of the switching transceiver 204-1-r is usually not instantaneous. . For example, buffers 206-1-t can be implemented as a standard first in first out (FIFO) sequence. The buffer manager 216 can implement various types of buffer logic to manage the operation of the buffers 206-1 -t. - 14 - 1379192 In various embodiments, managed power system 120 can include computing subsystem 230. The computing subsystem 230 can include various computing elements configured to process information and perform computational operations of nodes 1 1 0· 1 -m. Examples of suitable computing elements can include any electrical or electronic component designed to process information, including but not limited to processors, microprocessors, chipsets, controllers, microcontrollers, embedded controllers, clocks, oscillators , audio card, video card, multimedia card, peripheral device, memory unit, memory controller, video controller, audio controller, multimedia controller, etc. In various embodiments, the power management module 130 can include a power source 232. Power source 232 can be configured to provide power (generally) to the components of nodes 110-1-m, and in particular to managed power system 120. In one embodiment, for example, power source 2 3 2 is operable to provide varying levels of power to communication subsystem 210 and computing subsystem 230. In various embodiments, the power source 23 2 can be implemented by a rechargeable battery, such as a removable and rechargeable lithium ion battery, to provide direct current (DC) power, and an alternating current (AC) adapter to Pull power from a standard AC mains supply. In various embodiments, power management module 130 can include power management controller 234. Power management controller 234 generally controls the power consumption of managed power system 120. In one embodiment, the power management controller 234 is operable to control the power provided to the communication subsystem 210 and the varying level of the secondary system 230 based on the particular power state. For example, the power management controller 234 can modify, switch, or transform the power level provided by the power supply 23 2 to the secondary system 210, 230 to a higher or lower power level, thereby effectively modifying the secondary systems 210, 230. Power status. -15- 1379192 In various embodiments, power management module 130 can include one or more power control timers 236. The power management controller 234 can use the power control timer 236 to maintain a particular power state for a given power state period. The power state period may represent the time interval defined by a node or a portion of a node at a given power state. For example, the power management controller 234 may switch the computing subsystem 230 from a high power state to a low power state for a defined time interval 'and when the time interval elapses, the computing subsystem 230 is switched back to a high power state. .

爲了協調節點11 0-1-m之電力管理操作,通訊次系統 2 1 0、計算次系統23 0以及電力管理模組1 3 0可經由通訊 匯流排220及個別電力管理介面214-1、214-2及214-3 來連通各種電力管理訊息24 0- 1 -q。爲了管理系統中所有 裝置之電力’操作系統一般係使用標準技術用於在特別輸 入/輸出(I/O)互連上連通控制資訊。適用於實施爲通訊 匯流排220及關聯介面214之各種輸入/輸出(I/O)互連 之例子可包括但不限於周邊元件互連(PCI) 、PCI快速 (PCIe ) 、CardBus、通用串列匯流排(USB ) 、IEEE 23 94 FireWire 等等。 再次參考圖2,通訊次系統2 1 0可包含網路狀態模組 2 1 2 »網路狀態模組2 1 2可配置成用以監視通訊次系統 210之特定狀態或特徵,諸如通訊連接250-1 -V之交通活 動、能力資訊及通訊次系統210之各種通訊元件之其它操 作。網路狀態模組2 1 2可用所測量之特徵傳送通訊電力管 理訊息2 4 0 -1 - q給電力管理模組1 3 0。電力管理模組1 3 0 -16- 1379192 可部份根據通訊電力管理訊息240-l-q而產生受管理電力 系統120之電力狀態資訊260。 類似地’計算次系統23 0可包含計算狀態模組23 2 ^ 計算狀態模組23 2可配置成用以監視計算次系統23 0之特 定狀態或特徵,諸如系統活動程度、能力資訊及計算次系 統23 0之各種計算元件之其它操作。計算狀態模組23 2可 用所測量之特徵傳送計算電力管理訊息240-l-q給電力管 理模組130。電力管理模組130可部份根據計算電力管理 訊息240-l-q而產生受管理電力系統120之電力狀態資訊 260 ° 於一般操作中,電力管理模組1 30-1可對節點1 1〇-1 之受管理電力系統120-1之部分的操作來進行電源管理, 這項電源管理是根據從第一節點110-1之其它部分所接收 之電力狀態資訊來進行的。於一些例子中,例如,節點 110-1之電力管理模組130-1可操作用以在通訊匯流排 220上從受管理電力系統120-1之通訊次系統210-1的網 路狀態模組2 1 2接收通訊電力狀態資訊。電力管理模組 130-1可根據通訊次系統210-1之通訊電力狀態資訊而管 理節點1 10-1之受管理電力系統120-1之計算次系統23 Ο-ΐ 的各 種電力狀態。 電力管 理模組 130-1 及 次系統 210-1、23 0- 1可根據各種通訊匯流排通訊協定而在通訊匯流 排220連通通訊電力狀態資訊。 通訊電力狀態資訊可代表明確地或隱含地關於通訊次 系統2 1 0之電力狀態之資訊。通訊電力狀態資訊亦可代表 -17- 1379192 通訊次系統210之電力狀態之各種特徵或屬性,諸如 狀態期間、閒置期間、重新開始等待時間等等。於— 施例中,例如’通訊電力狀態資訊可包含但不限於通 力狀態參數、通訊閒置期間參數、通訊重新開始等待 ' 參數、或電力狀態期間。通訊閒置期間參數代表網路 或通訊次系統210-1會維持在給定電力狀態之時間量 . 定之時間間隔。通訊閒置期間參數允許次系統2 1 ( # 23 0- 1以決定論方式進入及離開低電力狀態。通訊重 始等待時間參數代表網路連結或通訊次系統210-1離 定電力狀態並進入高電力狀態所需之時間量或界定之 間隔。通訊重新開始等待時間參數允許次系統2 1C 2 3 0- 1決定會有多快其可期望通訊次系統210-1醒來 備就緒用於提供諸如向外傳輸之服務。可藉由電力管 息240- 1 -q在通訊匯流排220上連通通訊閒置期間參 通訊重新開始等待時間參數。 # 於各種實施例中,網路狀態模組212可配置成用 據通訊次系統210-1的能力產生通訊閒置期間參數及 重新開始等待時間參數。例如,通訊次系統210-1可 各種緩衝器,以儲存從通訊連接250- 1 -V所接收之 • (諸如網路封包),並轉送該資訊以用於由計算次系統 _ 1服務及處理。於另一個實施例中,通訊次系統210· 可實施各種緩衝器,以儲存從通訊匯流排220所接收 訊(諸如網路封包),並轉送該資訊以用於由通訊次 210-1經由通訊連結140-1、140-2在通訊連接250-1 電力 個實 訊電 時間 連結 或界 1-1 > 新開 開給 時間 -1 ' 並準 理訊 數及 以根 通訊 實施 資訊 230-1亦 之資 系統 V上 -18· 1379192 將該資訊連通至其它節點ll〇-2-m。於又另一個例子中’ 通訊次系統210-1可包含各種有線或無線傳收器,其以不 同通訊速度操作,諸如IEEE 802.3-2005標準10十億位 元乙太網路(lOGbE或lOGigE) 、IEEE 802.3ba建議標 準100十億位元乙太網路(lOOGbE或lOOGigE)等等。 於又另一個例子中,通訊次系統210-1可包含以不同速度 操作之各種處理器,諸如基頻或通訊處理器。於又另一個 例子中,網路狀態模組2 1 2可監視資訊經由通訊連結 14 0-1、140-2在通訊連接250-1 -V上被接收之速率。於此 例子中,通訊次系統2 1 0_ 1之網路狀態模組2 1 2可監視通 訊連結140-1、140-2,以測量封包相互間到達時間。通訊 能力之其它例子可包含在通訊連結140-1、140-2上之其 他網路交通負載測量(例如同步交通、非同步交通、脈衝 串交通等等)、訊號雜訊比(SNR )、所接收訊號強度指 示(RSSI)、通訊匯流排220之通量、實體層(PHY)速 度、經由一個或更多電源管理封包資料單元(PMPDU) 150-1-s所接收之其它節點ΙΙΟ-2-m之電力狀態資訊260 等等。網路狀態模組2 1 2可評估這些及其它網路或通訊次 系統210-1之通訊能力,並根據所評估之通訊次系統210-1之通訊能力產生適當之通訊閒置期間參數及通訊重新開 始等待時間參數。 於各種實施例中,節點1 1 0-1 -m可使用電力狀態資訊 去加強給定節點1 1 〇 -1 _ m之電力管理操作’進而改善能量 保存(例如增加電池使用壽命或減少電池大小)'散熱或 -19- 1379192 整體系統效能。於一個實施例中,例如,通訊次系統 210-1之網路狀態模組212可監視通訊連結140-1、140-2 及各種通訊元件(例如無線電、基頻處理器、晶片組、記 憶體單元等等),以決定通訊次系統210-1之通訊電力狀 態資訊。網路狀態模組212可在通訊匯流排220與介面 2 14-1 ' 2 14-3上以通訊電力狀態資訊傳送電力管理訊息 240-1-q給電力管理模組130-1。電力管理模組130-1可接 收電力管理訊息240-1-q,並從電力管理訊息240-1 -q取 回通訊電力狀態資訊。電力管理模組130-1可根據通訊次 系統210-1之通訊電力狀態資訊而管理計算次系統23 0-1 之電力狀態。例如,電力管理模組130-1可使用通訊次系 統210-1之通訊電力狀態資訊修改受管理電力系統12〇-1 之計算次系統230- 1之電力位準,從第一電力位準修改爲 第二電力位準。此外,電力管理模組1 3 Ο-1可如所決定之 使用通訊次系統210-1之通訊電力狀態資訊修改計算次系 統23 0- 1之電力位準,從第一電力位準修改爲第二電力位 準經過一界定之時間間隔,稱之爲電力狀態期間。 每當通訊次系統210-1處於低電力狀態時,然而該通 訊次系統210-1仍可繼續在通訊連結14〇-1、140-2上從 其它節點110-2-m接收資訊封包,並從計算次系統230」 接收資訊封包’用以藉由通訊次系統210-1在通訊連結 14〇-1、14〇-2上將其從計算次系統230-1傳送至其它節點 ΙΙΟ-2-m。如果通訊次系統210-1所接收之每一封包被直 接傳送至計算次系統23 0- 1用於處理,則計算次系統23 0_ -20- 1379192 1會持續地必須離開低電力狀態並進入高電力狀態,以處 理每一封包。如此會消耗電源23 2相當多之能量。 爲解決這些及其它問題,通訊次系統210-1可實施中 斷結合技術。例如,通訊次系統210-1可配置用以使用一 個或更多之緩衝器206-1-t來儲存或緩衝進入之封包,且 緩衝器管理器216可決定何時釋放或轉送儲存之封包至計 算次系統23 0- 1用於處理。緩衝器管理器216可根據設計 用於增加計算次系統230- 1及整個節點1 1〇-1之能量保存 之緩衝器管理策略,決定何時將封包從緩衝器206- 1 -t轉 送至計算次系統2 3 0- 1。 於各種實施例中,緩衝器管理器216可實施緩衝器管 理策略,其設計用以允許通訊次系統210-1及/或計算次 系統230-1進入並維持於低電力狀態中一段較長時間,同 時維持通訊次系統210-1及/或計算次系統230-1之Q〇S、 通量及其它效能需求。於一些實施例中,緩衝器管理策略 可包含各種緩衝器管理規則,以決定何時將封包從緩衝器 206- 1 -t轉送至計算次系統23 0- 1。於一個實施例中,例 如,緩衝器管理器216可實施緩衝器管理規則,於通訊閒 置期間將封包儲存於緩衝器206-1-t中,並當滿足以下4 個緩衝器管理狀況之任何組合時,將儲存之封包從緩衝器 206-Ι-t轉送至計算次系統23 0- 1 : ( 1 )當一個或更多緩衝 器206-1 -t儲存之封包數目超過可變接收臨限値時;(2)當 緩衝器卸載暫停値已失效;(3)當接收到緩衝器卸載事件 訊號;及/或(4 )當通訊閒置期間參數小於通訊閒置期間臨 -21 - 1379192 限値。必須瞭解者爲,這4個緩衝器管理狀況係舉例說 明’不在於限制。本文並不在於限制實施例。 緩衝器管理器216可以各種組合之方式利用一個或更 多緩衝器管理狀況,以觸發釋放或轉送儲存於緩衝器 206-1 -t內之任何封包至計算次系統230」用於處理。於 一個實施例中,例如,緩衝器管理器2 1 6可利用直接記憶 體存取(DMA)技術將儲存於緩衝器206- 1 -t內之封包轉 送至計算次系統230-1,以使封包加速從緩衝器206-1-t 移動至計算次系統2 3 0- 1所使用之記憶體單元2 3 4。然後 緩衝器管理器216可發出中斷給計算次系統23 0- 1 (例如 處理器),以指示封包在記憶體單元234內並準備就緒可 供計算次系統230- 1處理。 於一個實施例中,當一個或更多緩衝器206- 1 -t儲存 之封包數量超過可變接收臨限値時,緩衝器管理器216可 將儲存之封包從緩衝器206- 1 -t轉送至計算次系統23 0-1。例如,通訊次系統2 1 0-1可包含水印產生器2 1 7,其 耦接至緩衝器管理器216及緩衝器206- 1 -t。水印產生器 2 1 7可操作用以產生可變接收臨限値。可變接收臨限値可 包含界定之用於緩衝器20 6-1 -t的臨限値或水印。可變接 收臨限値可用至少以下3個輸入而被計算、導出或決定成 一函數:(1)接收資料速率參數;(2)緩衝器大小參數;以 及(3)通訊重新開始等待時間參數。接收資料速率參數可 代表一個或更多之傳收器204-1-r之通訊速率。緩衝器大 小參數可代表一個或更多緩衝器206-1-t之大小。通訊重 -22- 1379192 新開始等待時間參數可代表網路連結或通訊次系統2“^ 離開給定電力狀態並進入高電力狀態所需之時間量或界定 之時間間隔(例如1 ms )。利用這些或其它通訊參數,水 印產生器217可週期性地、連續地或應需要產生可變接收 臨限値,藉以確保可變接收臨限値準確地反應改變通訊速 率、等待時間及其它網路交通考量。緩衝器管理器216可 從水印產生器217接收可變接收臨限値並從緩衝器20 6- 1 _ t接收目前緩衝器使用參數,且將目前緩衝器使用參數與 可變接收臨限値做一比較,再根據比較結果啓動DMA轉 送。例如,當緩衝器儲存之資訊封包數量超過可變接收臨 限値時,緩衝器管理器216便啓動DMA轉送。 於一個實施例中,當緩衝器卸載暫停値已失效時,緩 衝器管理器216可將儲存之封包從緩衝器206_l-t轉送至 計算次系統23 0- 1。例如,通訊次系統2 1 0-1可包含緩衝 器定時器218,以耦接至緩衝器管理器216。緩衝器定時 器218可爲硬體或軟體定時器,用以設定或測量所界定之 時間間隔。例如,可以緩衝器卸載暫停値來設定或載入緩 衝器定時器218。緩衝器定時器218可監視或執行倒數, 直到緩衝器卸載暫停値已失效。緩衝器管理器216可配置 用以當緩衝器卸載暫停値已失效時,將儲存之資訊封包從 緩衝器206-1-t轉送至計算次系統230-1。當緩衝器管理 器216與另一緩衝器管理狀況組合使用時(諸如可變接收 臨限値),當緩衝器206-1 -t儲存之封包數量超過可變接 收臨限値之前緩衝器卸載暫停値就已失效時,緩衝器管理 -23 - 1379192 器216可轉送所儲存之封包。 於一個實施例中,當緩衝器管理器216接收到緩衝器 卸載事件訊號時,緩衝器管理器216可將儲存之封包從緩 衝器206-Ι-t轉送至計算次系統230- 1。例如,通訊次系 統210-1可隨機地從節點110-1之各部分接收到事件訊 號,其有助於緩衝器管理器216將封包從緩衝器206-1 -t 轉送至計算次系統230-1。例如,假設計算次系統230-1 實施晶片組電腦架構,其包含記憶體控制器集線器 (MCH )及輸入/輸出(I/O )控制器集線器(ICH ),諸 如由加州 Santa Clara之英特爾公司(Intel® Corporation) 所製造之「北橋」及「南橋」控制器集線器。進一步假 設,MCH及ICH利用直接媒體介面(DMI)及關聯連結 來連通資訊。關於計算次系統230-1之其它部分,DMI連 結可處於各種電力狀態,諸如高電力狀態L0及低電力狀 態L1。當因爲其它裝置之活動而使DMI連結從低電力狀 態L 1離開而到高電力狀態L 0,計算次系統2 3 0 - 1可傳送 緩衝器卸載事件訊號至緩衝器管理器216。緩衝器卸載事 件訊號可對緩衝器管理器216指示出計算次系統23 0- 1係 已處於高電力狀態且爲主動,並因此緩衝器管理器216可 趁機會使用計算次系統2 3 0 - 1之高電力狀態,以將封包從 緩衝器206-l_t轉送至記憶體234。當緩衝器管理器216 與另一緩衝器管理狀況組合使用時(諸如可變接收臨限 値),當緩衝器206- 1 -t儲存之封包數目超過可變接收臨 限値之前接收到緩衝器卸載事件訊號時,緩衝器管理器 -24- 1379192 216可轉送所儲存之封包。 於一個實施例中,當通訊閒置期間參數小於通訊閒置 期間臨限値時,緩衝器管理器216可實施緩衝器管理規 則,將儲存之封包從緩衝器2 06- 1 -t轉送至計算次系統 2 3 0- 1。通訊閒置期間臨限値可包含通訊閒置期間參數之 一界定臨限値。一般而言,通訊閒置期間參數愈高,則資 料來到通訊連結140-1、140-2上之通訊速率便愈低,反 之亦然。通訊閒置期間臨限値係可組構的,且可設定成用 以決定何時通訊閒置期間參數夠低而足以指示出夠高之通 訊速率,其不需要容忍緩衝器206-1 -t所引起之額外等待 時間。緩衝器管理器216可配置成用以使一個或更多緩衝 器2 06- 1 -t失能,以當通訊閒置期間參數小於通訊閒置期 間臨限値時,避免緩衝器206- 1 -t儲存資訊封包。 於一些實施例中,緩衝器管理器216可配置成用以發 出訊號給控制器208,以修改傳收器204-1-r之通訊速 率。例如,緩衝器管理器216可根據其FIFO大小及/或留 下之能量來命令控制器208修改通訊速率。於一個實施例 中,例如,緩衝器管理器216可接收或維持緩衝器大小參 數、能量測量參數或兩者參數。緩衝器大小參數可代表 FIFO大小或FIFO餘留容量。能量測量參數可代表爲諸如 電源232之電源所餘留之能量。緩衝器管理器216可配置 成用以發出需求給控制器20 8,用以根據緩衝器大小參數 而調整傳收器204-1-r之通訊速率。類似地,緩衝器管理 器216可配置成用以從電力管理控制器234接收具有能量 -25- 1379192 測量參數之電力管理訊息,並根據能量測量參數傳送需求 以調整傳收器204·1·γ之通訊速率。 圖3表示根據一個或更多實施例之邏輯流程300。可 藉由各種系統及/或裝置來進行邏輯流程3 00,因應給定之 設計參數組或效能限制所需,邏輯流程300可實施爲硬 體' 軟體及/或其任何組合。例如,可藉由邏輯裝置(例 如處理器)及/或被邏輯裝置所執行之邏輯(例如指令、 資料及/或碼)來實施邏輯流程300。爲了解說且不加以限 制,參考圖1及2來說明邏輯流程300。 邏輯流程300可以一般方式說明節點1 10-1-m之各種 操作,而且特別地說明受管理電力系統1 20及電力管理模 組130。如圖3所示,在區塊302,邏輯流程300可修改 通訊次系統及計算次系統之電力狀態,由高電力狀態修改 成低電力狀態。在區塊3 04,邏輯流程3 00可於通訊閒置 期間將資訊封包儲存於通訊次系統之緩衝器中,以產生計 算閒置期間。在區塊3 06,邏輯流程3 00可產生用於緩衝 器之可變接收臨限値。在區塊3 0 8,邏輯流程3 0 0可根據 可變接收臨限値將所儲存之資訊封包從緩衝器轉送至計算 次系統。本文並不在於限制實施例。 於一個實施例中,在區塊302,邏輯流程300可修改 通訊次系統及計算次系統之電力狀態,由高電力狀態修改 成低電力狀態,由高電力狀態修改成低電力狀態。例如, 電力管理控制器234可接收電力管理訊息240-1-q,其具 有由計算狀態模組23 2所產生之計算電力狀態資訊以及由 -26- 1379192 網路狀態模組2 1 2所產生之通訊電力狀態資訊。電力管理 控制器234可經由介面214-1、214-2及214-3從通訊匯 流排220接收電力管理訊息24〇_l-q。電力管理控制器 234可處理電力管理訊息Μ 0-1-q,並決定適當之通訊電 力狀態(例如NL0、NL1、NL2等等)以及適當之計算電 力狀態(例如SO、SOil、S0i2、 S0i3、S4等等)。電力 管理控制器234可於通訊匯流排220及介面214-1、214-2 及214-3上經由電力管理訊息240-1-q傳送通訊電力狀態 及計算電力狀態給個別次系統210-1、210-2,而且次系統 210-1、210-2可因此修改其個別電力狀態。 於一個實施例中,在區塊304,邏輯流程300可於通 訊閒置期間將資訊封包儲存於緩衝器,用於通訊次系統, 以產生計算閒置期間。例如,通訊閒置期間可代表當通訊 次系統210-1不從網路於通訊連結140-1、140-2上接收 (或期待接收)資訊之時間間隔。例如,計算閒置期間可 代表當計算次系統230-1不從通訊次系統210-1接收(或 期待接收)資訊之時間間隔。例如,通訊次系統2 1 0 -1可 從電力管理訊息240-1-q接收通訊閒置期間參數,用於通 訊次系統210.1,其係由電力管理控制器23 4所傳送。於 此例中,可使用從次系統210-1、230-1所接收之電力狀 態資訊藉由電力管理控制器2 3 4來計算通訊閒置期間參 數。於另一個例子中,通訊次系統2 1 0 -1可從網路狀態模 組2 1 2接收通訊閒置期間參數。於任一例子中,通訊次系 統2 1 0 -1可進入由通訊電力狀態所表示之低電力狀態一段 -27- 1379192 時間間隔(其係由通訊閒置期間參數所界定)。可直接藉 由對通訊次系統210-1之所有通訊元件降低電力或間接藉 由修改傳收器204-1-r之通訊速率而進入低電力狀態。— 旦通訊次系統210-1進入低電力狀態,緩衝器管理器216 可於通訊閒置期間(由通訊閒置期間參數所界定)將資訊 封包儲存於一個或更多接收緩衝器206- 1 -t中,用於通訊 次系統210-1,以產生計算次系統230-1之計算閒置期 間。於一些例子中,通訊次系統210-1可對計算次系統 230-1連通計算閒置期間,使計算次系統230-1可因此而 操作,諸如切換到低電力狀態經過一時間間隔,對應到所 期待之計算閒置期間。 於一個實施例中,在區塊306,邏輯流程300可產生 緩衝器之可變接收臨限値。例如,水印產生器217可接 收:接收資料速率參數、緩衝器大小參數及/或通訊重新 開始等待時間參數,並根據這些參數產生接收緩衝器 2 06- 1 -t之可變接收臨限値(例如緩衝器水印)。水印產 生器217可將可變接收臨限値輸出至緩衝器管理器216。 於一個實施例中,在區塊308,邏輯流程300可根據 可變接收臨限値將所儲存之資訊封包從緩衝器轉送至計算 次系統。例如,緩衝器管理器2 1 6可從水印產生器2 1 7接 收可變接收臨限値、以該可變接收臨限値設定緩衝器 206- 1 -t,以及可週期性或非週期性地將接收緩衝器206-1 -t所儲存之資訊封包數量與可變接收臨限値做比較。接 收緩衝器206- 1 -t所儲存之資訊封包數量符合或超過可變 -28- 1379192 接收臨限値,緩衝器管理器便可經由DMA轉送方式而轉 送接收緩衝器2〇6-l-t之內容給計算次系統230之記億體 單元234,以供進一步處理。 圖4表示根據一個或更多實施例之邏輯流程4〇〇。可 藉由各種系統及/或裝置來進行邏輯流程400,因應給定之 設計參數組或效能限制所需,邏輯流程4 0 0可實施爲硬 體、軟體及/或其任何組合。例如,可藉由邏輯裝置(例 如處理器)及/或被邏輯裝置所執行之邏輯(例如指令、 資料及/或碼)來實施邏輯流程400。爲了解說且不加以限 制,參考圖1及2來說明邏輯流程400。 邏輯流程400可以一般方式說明節點丨之各種 操作’而且特別地說明受管理電力系統120及電力管理模 組1 3 0。如圖4所示,邏輯流程4 0 0開始於區塊4 0 2,其 中水印產生器217以接收資料速率參數、緩衝器大小參數 及/或通訊重新開始等待時間參數來計算或再計算可變接 收臨限値(例如緩衝器水印),然後組構緩衝器水印觸發 器。這允許緩衝器管理器216可對各種連結速度及延遲做 出反應。緩衝器管理器2 1 6可利用通訊閒置時間參數來決 定通訊次系統210-1及/或計算次系統230-1可維持於低電 力狀態中多長時間。由於在通訊閒置期間參數沒有所期待 之進入交通,次系統210-1、230-1可受電力閘控(如果沒 有足夠時間使次系統2 1 0 - 1、2 3 0 - 1之分離元件能以經濟 方式這樣做)。例如,實施爲無線傳收器之通訊元件(諸 如傳收器2〇4·1-〇通常需要至少8 ms之通訊閒置期間參 -29- 1379192 數用以變成低電力狀態。當通訊閒置期間參數低於8 ms 時,這種狀況表示進入交通爲高資料速率。根據這種假 設,在菱形區塊404,當通訊閒置期間參數小於8 ms 時,便在區塊406使緩衝器206- 1 -t失能,以消除緩衝器 2 0 6-Ι-t可能導致之額外延遲(等待時間)。在菱形區塊 4 04,當通訊閒置期間參數大於8 ms時,在區塊408,無 論如何,緩衝器管理器216可設定緩衝器206- 1 -t之可變 接收臨限値以及緩衝器定時器218之緩衝器卸載暫停値。 在區塊410,緩衝器管理器216可開始從一個或更多 傳收器204-1-r接收封包,並在區塊412於一個或更多緩 衝器206-1-t中緩衝所接收之封包,直到在菱形區塊414 一個或更多緩衝管理狀況成爲TRUE爲止。於一個實施例 中’菱形區塊414可評估至少4個狀況,包括是否:(1) 第一狀況(狀況一)爲TRUE,根據超過可變接收臨限 値;(2)第二狀況(狀況二)爲TRUE,根據緩衝器卸載暫 停値失效了;(3)第三狀況(狀況三)爲TRUE,根據接收 到緩衝器卸載事件訊號;以及(4)第四狀況(狀況四)爲 TRUE ’根據超過事件計數器◊在第三狀況(狀況三) 中’例如’緩衝器管理器216能使用來自於驅動器之各種 系統事件(例如傳送中斷)或ICH及MCH之間之DMI連 結狀態’做爲輸入來觸發不緩衝來自於接收緩衝器206- 1 -t之封包。例如,當因爲來自於其它裝置之活動而使DMI 從L1變成L0,則其發訊號給通訊次系統之“—丨表示主機 系統已處於主動,且因此緩衝器管理器216應利用這個機 -30- 1379192 會如有可能的話使來自於接收緩衝器206-l-t之已緩衝封 包解除緩衝。參考圖5而更詳細說明第四狀況(狀況 四),如離頁參考4 1 4a所表示。 當於菱形區塊414所測試之4個狀況之一爲TRUE 時’在區塊416緩衝器管理器216使緩衝器定時器218無 效(例如當供電時),而且在區塊418觸發DMI連結離 開低電力狀態L1並進入高電力狀態L0。在區塊420,緩 衝器管理器216利用DMA轉送方式,將封包從緩衝器 206-l-t轉送至計算次系統230-1之記憶體單元234,而不 緩衝封包,並發出中斷給計算次系統230-1。在區塊 422’緩衝器管理器216可選擇性地修改傳收器204-1-r 之通訊速率,以根據其FIFO大小及/或餘留能量來增加或 降低進入封包之速率。 在菱形區塊424,緩衝器管理器216可決定是否有更 多封包已經到達維持清醒之定時器之內。緩衝器管理器 2 1 6可保持最後封包之時間印記。當時間印記減去目前時 間是小於維持清醒之定時器時,就假定網路爲忙錄。在這 種情況下,在區塊4 0 2緩衝器管理器216將持續操作。當 時間印記減去目前時間是大於維持清醒之定時器時,就假 定網路爲閒置。在這種情況下,在區塊426緩衝器管理器 2 16觸發DMI連結離開高電力狀態L0並進入低電力狀態 L1,並在區塊4 02緩衝器管理器216持續操作。 再次參考菱形區塊414’緩衝器管理器216所評估之 狀況之一可包括第四狀況(狀況4),有時稱爲「失敗- -31 - 1379192 安全」觸發。該「失敗-安全」觸發係設計用以避免重回 狀況’亦即少量封包(或單一封包)仍留在緩衝器206- 1 -t內’直到緩衝器定時器218失效爲止。藉由監視當緩衝 器定時器218失效時之單一封包在緩衝器206-1 -t內側的 次數’緩衝器管理器2 1 6可偵測這種狀況。例如,如果這 種狀況發生超過特定之次數(例如3次),則緩衝器管理 器216可暫時使緩衝器2 06- 1 -t失能,直到能設定重新開 始狀況次數爲止,藉以指示緩衝器206- 1 -t應致能或再致 能。重新開始狀況之例子可包括:(1)根據定時器,諸 如在所界定之時間間隔(例如1 〇秒)後,致能緩衝器 2 06- 1 -t ;以及(2 )根據封包計數,諸如在接收到所界定 之封包數目(例如4000個封包)後,致能緩衝器206-1 -t。參考圖5更詳細說明評估第四狀況之範例邏輯流程。 圖5表示根據一個或更多實施例之邏輯流程500。可 藉由各種系統及/或裝置來進行邏輯流程500,因應給定之 設計參數組或效能限制所需,邏輯流程5 00可實施爲硬 體、軟體及/或其任何組合。例如,可藉由邏輯裝置(例 如處理器)及/或被邏輯裝置所執行之邏輯(例如指令、 資料及/或碼)來實施邏輯流程500。爲了解說且不加以限 制’參考圖1及2來說明邏輯流程5 0 0。 邏輯流程5 0 0可以一般方式說明節點1 1 〇 -1 - m之各種 操作,而且特別地說明受管理電力系統120及電力管理模 組1 3 0。邏輯流程5 0 0可提供參考圖4所說明之在區塊 414如離頁參考41 4a所表示之評估第四狀況(狀況四) -32- 1379192 之邏輯流程範例。爲了實施第四狀況(狀況四),緩衝器 管理器216可實施事件計數器,其計算特定事件發生之次 數(X)。事件可包括之情況爲:當緩衝器卸載暫停値失 效時只有有限數量之封包(例如1個)在緩衝器206-1 -t 之內。當事件計數器計算出之事件發生(X)超出事件臨 限値(N)(例如N = 3)時,緩衝器管理器216便可暫時 使緩衝器206-1-t失能,直到符合重新開始狀況爲止。 於一個實施例中,例如,緩衝器管理器216可實施封 包計數器,用以計算緩衝器 506-1-t中之封包之數目 (M) ’並以緩衝器失能暫停値(B)來設定緩衝器定時 器218。如圖5所示,在菱形區塊502,當Μ不等於封包 臨限値時(例如Μ > 1 ),則在區塊5 1 4,緩衝器管理器 2 1 6重設事件計數器(例如Χ = 〇 ),並傳送控制到邏輯流 程400之區塊416。在菱形區塊502,當Μ等於封包臨限 値時(例如M=l),則在區塊504,緩衝器管理器216將 事件計數器加1 (例如Χ = Χ+1 )。在菱形區塊506,緩衝 器管理器216可決定是否事件計數器(X)大於或等於事 件臨限値(例如Ν = 3 )。當在菱形區塊5 0 6爲F A L S Ε,則 在區塊5 02,緩衝器管理器216重新開始。當在菱形區塊 5 06爲TRUE,則在區塊508,緩衝器管理器216便使緩 衝器206- 1 -t失能。然後緩衝器216決定是否發生重新開 始狀況’諸如緩衝器定時器218大於緩衝器失能暫停値 (例如定時器大於L秒)或者由於緩衝器2 06- 1 -t失能而 所接收之封包之數目大於封包臨限値(例如P>4000個封 -33- 1379192 包)。當這兩個重新開始狀況皆爲FALSE 傳回區塊5 08。當任何一種重新開始狀況爲 在區塊510,緩衝器管理器216致能緩衝器 送控制到邏輯流程400之區塊4 1 6。値得名 N、L及P的値是可配置設定的値。 各種實施例可提供數種優點,用於多種 用。於一個實施例中,例如,緩衝器管理器 206- 1 -t可用於允許計算次系統23 0- 1維 態,藉以增加能量保存。於一個實施例中, 約500毫瓦(mW)至2瓦(W)之電力節 通訊情況。 於一些例子中,各種實施例可實施爲製 物品可包含電腦可讀取媒體或儲存媒體,配 輯及/或資料,用於進行一個或更多實施例 腦可讀取媒體或儲存媒體之範例可包含但不 明之範例。於各種實施例中,例如,製造 碟、光碟、快閃記憶體或韌體,其內含電腦 用於在一般用途處理器或特殊應用處理器上 本文並不在於限制實施例。 可使用硬體元件、軟體元件或兩者之組 實施例。硬.體元件之範例可包含先前提出用 任何範例,並且進一步包含微處理器、電 (例如電晶體、電阻器、電容器、電感器等 路、邏輯閘、暫存器、半導體裝置、晶片、 時,則控制被 TRUE時,則 206- 1 -t,並傳 E意的是,Μ、 :使用情況及應 216及緩衝器 持於低電力狀 例如,可達成 省,用於主動 造物品。製造 置用以儲存邏 各種操作。電 限於先前所說 物品可包含磁 程式指令,適 執行。然而, 合來實施各種 於邏輯裝置之 路、電路元件 等)、積體電 微晶片、晶片 -34- 1379192 組等等。軟體兀件之範例可包含軟體部件、程式、應用軟 體、電腦程式、應用程式、系統程式、機器程式、操作系 統軟體、中間軟體、韌體、應用程式介面(API)、指令 集、計算碼、電腦碼、碼段、電腦碼段、字、値、符號或 其任何組合。實施例是否要利用硬體元件及/或軟體元件 來實施之決定係可根據任何數目之因數而改變,諸如所需 之计算速率、電力位準、熱容忍度、處理循環預算、輸入 # 資料速率' 輸出資料速率 '記憶體資源、資料匯流排速度 及其它設計或效能限制,如給定實施方式需求而定。 可能使用語辭「耦接」及「連接」連同其衍生詞。這 些術語並非必定彼此爲同義字。例如,可能使用術語「連 接」及/或「耦接」來表示兩個或更多元件是互相直接實 體或電接觸。然而術語「親接」亦可代表兩個或更多元件 並非互相直接接觸,但仍彼此共同操作或相互作用。 必須強調者爲,本發明之摘要係允許讀者快速確定技 Φ 術揭示之本質的一種摘要。必須瞭解者爲,該摘要並非用 於解釋或限制申請專利範圍之範圍或意義。此外,於發明 內容及實施方式中,各種特性係以集合於單一實施例中, 用以使揭示內容流暢明確。這種揭示之方法不可解釋爲反 . 映所主張實施例比每一申請專利範圍所述內容需要更多特 性。而是如申請專利範圍所反映’發明性之標的在於少於 單一揭示實施例之所有特性。因此,申請專利範圍在此倂 入發明內容及實施方式中,每一申請專利範圍本身係基於 各別實施例。於申請專利範圍中,術語「包含 -35- 1379192 (including)」及「其中(in which)」係分別用做爲各 別術語「包含(comprising)」及「其中(wherein)」之 平易英語之均等術語。此外,術語「第一」、「第二」及 「第三」等等係僅用做標示,並不在於在其目標加上數字 規定。 雖然已經以結構特性及/或方法行爲之特定用語來說 明標的,但必須瞭解者爲,申請專利範圍所界定之標的並 • 不須限於以上說明之特定特性或行爲。而是上說明之特定 特性及行爲係揭示爲實施申請專利範圍之範例形式。後附 爲申請專利範圍。 【圖式簡單說明】 圖1表示通訊系統之一個實施例。 圖2表不設備之一個實施例。 圖3表示第一邏輯圖之—個實施例。 Φ 圖4表示第二邏輯圖之一個實施例。 圖5表示第三邏輯圖之一個實施例。 【主要元件符號說明】 . 100 :通訊系統 110-1 :節點 1 10-2 :節點 1 1 0 - m :節點 120:受管理電力系統 -36- 1379192 120-1 :受管理電力系統 1 3 0 :電力管理模組 130-1 :電力管理模組 1 4 0 - 1 :通訊連結 140-2 :通訊連結 150-1-s:電源管理封包資料單元 204-卜r :傳收器 206-1-t:緩衝器 2 0 8 :控制器In order to coordinate the power management operations of the nodes 11 0-1-m, the communication subsystem 2 1 0, the computing subsystem 23 0 and the power management module 130 can be connected via the communication bus 220 and the individual power management interfaces 214-1, 214. -2 and 214-3 to connect various power management messages 24 0 - 1 -q. In order to manage the power of all devices in the system, the operating system typically uses standard techniques for communicating control information over special input/output (I/O) interconnects. Examples of various input/output (I/O) interconnects suitable for implementation as communication bus 220 and associated interface 214 may include, but are not limited to, Peripheral Component Interconnect (PCI), PCI Express (PCIe), CardBus, Universal Serial Bus (USB), IEEE 23 94 FireWire, and more. Referring again to FIG. 2, the communication subsystem 2 1 0 can include a network status module 2 1 2 » The network status module 2 1 2 can be configured to monitor a particular status or feature of the communication subsystem 210, such as the communication connection 250 -1 -V traffic activity, capability information, and other operations of various communication components of communication subsystem 210. The network status module 2 1 2 can transmit the communication power management message 2 4 0 -1 - q to the power management module 1 300 using the measured characteristics. The power management module 1 3 0 -16-1379192 can generate power status information 260 of the managed power system 120 based in part on the communication power management messages 240-1-q. Similarly, the 'computing subsystem 323 can include a computing state module 23 2 ^ The computing state module 23 2 can be configured to monitor a particular state or feature of the computing subsystem 030, such as system activity level, capability information, and calculations. Other operations of various computing elements of system 230. The computing status module 23 2 can communicate the calculated power management messages 240-1-q to the power management module 130 using the measured features. The power management module 130 can generate the power status information of the managed power system 120 based on the calculated power management information 240-lq. In general operation, the power management module 1 30-1 can be connected to the node 1 1〇-1. Power management is performed by the operation of a portion of the managed power system 120-1, which is based on power status information received from other portions of the first node 110-1. In some examples, for example, the power management module 130-1 of the node 110-1 is operable to communicate from the communication network 220 to the network status module of the communication subsystem 210-1 of the managed power system 120-1. 2 1 2 Receive communication power status information. The power management module 130-1 can manage various power states of the computing subsystems Ο-ΐ of the managed power system 120-1 of the node 1 10-1 based on the communication power state information of the communication subsystem 210-1. The power management module 130-1 and the secondary systems 210-1, 23 0-1 can communicate communication power status information in the communication bus 220 according to various communication bus communication protocols. The communication power status information may represent information explicitly or implicitly regarding the power status of the communication subsystem 2 10 . The communication power status information may also represent various characteristics or attributes of the power status of the -17- 1379192 communication subsystem 210, such as status periods, idle periods, restart wait times, and the like. In the embodiment, for example, the 'communication power status information may include, but is not limited to, a power status parameter, a communication idle period parameter, a communication restart wait 'parameter, or a power status period. The communication idle period parameter represents the amount of time that the network or communication subsystem 210-1 will maintain a given power state.  Set the time interval. The communication idle period parameter allows the secondary system 2 1 (# 23 0-1 to enter and leave the low power state in a deterministic manner. The communication restart waiting time parameter represents the network connection or the communication subsystem 210-1 departs the power state and enters the high state. The amount of time or defined interval required for the power state. The communication restart start time parameter allows the secondary system 2 1C 2 3 0-1 to decide how fast it can expect the communication subsystem 210-1 to wake up ready for providing The service that is transmitted out can be restarted by the power management information 240-1 -q on the communication bus 220 to communicate the communication idle period. # In various embodiments, the network status module 212 can be configured. The communication idle period parameter and the restart wait time parameter are generated according to the capability of the communication subsystem 210-1. For example, the communication subsystem 210-1 can receive various buffers to store the received from the communication connection 250-1 -V. (such as a network packet) and forward the information for service and processing by the computing subsystem _ 1. In another embodiment, the communication subsystem 210 can implement various buffers to store the slave The communication bus 220 receives the message (such as a network packet) and forwards the information for use in the communication connection 210-1 via the communication link 140-1, 140-2 in the communication connection 250-1. Or 1-1 > new opening to time -1 ' and the number of quasi-political signals and the implementation of the information of the root communication communication 230-1 also V -18 · 1379192 to connect this information to other nodes ll 〇 -2- m. In yet another example, the communication subsystem 210-1 may include various wired or wireless transceivers that operate at different communication speeds, such as IEEE 802. 3-2005 standard 10 billion bit Ethernet (lOGbE or lOGigE), IEEE 802. 3ba recommends a standard of 100 billion bit Ethernet (lOOGbE or lOOGigE) and so on. In yet another example, communication subsystem 210-1 can include various processors operating at different speeds, such as a baseband or communication processor. In yet another example, the network status module 2 1 2 can monitor the rate at which information is received over the communication connections 250-1 -V via the communication links 14 0-1, 140-2. In this example, the network status module 2 1 2 of the communication subsystem 2 1 0 1 can monitor the communication links 140-1, 140-2 to measure the arrival time of the packets with each other. Other examples of communication capabilities may include other network traffic load measurements (eg, synchronous traffic, asynchronous traffic, burst traffic, etc.) on the communication links 140-1, 140-2, signal to noise ratio (SNR), Received Signal Strength Indication (RSSI), communication bus 220 flux, physical layer (PHY) speed, other nodes received via one or more power management packet data units (PMPDUs) 150-1-s ΙΙΟ-2- m power status information 260 and so on. The network status module 2 1 2 can evaluate the communication capabilities of these and other network or communication subsystems 210-1 and generate appropriate communication idle period parameters and communication re-establishment based on the communication capabilities of the evaluated communication subsystem 210-1. Start waiting time parameter. In various embodiments, nodes 1 1 0-1 -m can use power state information to enhance power management operations of a given node 1 1 〇-1 _ m to improve energy conservation (eg, increase battery life or reduce battery size) ) 'Cooling or -19- 1379192 overall system performance. In one embodiment, for example, the network status module 212 of the communication subsystem 210-1 can monitor the communication links 140-1, 140-2 and various communication components (eg, radio, baseband processor, chipset, memory) Unit, etc.) to determine the communication power status information of the communication subsystem 210-1. The network status module 212 can transmit power management messages 240-1-q to the power management module 130-1 via the communication power status information on the communication bus 220 and the interface 2 14-1 ' 2 14-3. The power management module 130-1 can receive the power management messages 240-1-q and retrieve the communication power status information from the power management messages 240-1 -q. The power management module 130-1 can manage the power state of the secondary system 23 0-1 based on the communication power status information of the communication subsystem 210-1. For example, the power management module 130-1 may modify the power level of the computing subsystem 123-1 of the managed power system 12〇-1 using the communication power status information of the communication subsystem 210-1, and modify the power level from the first power level. It is the second power level. In addition, the power management module 1 3 Ο-1 can modify the power level of the calculation subsystem 023 by using the communication power state information of the communication subsystem 210-1, and modify the power level from the first power level to the first power level. The second power level passes through a defined time interval and is referred to as the power state period. Whenever the communication subsystem 210-1 is in a low power state, the communication subsystem 210-1 can still continue to receive information packets from the other nodes 110-2-m on the communication links 14〇-1, 140-2, and The receiving information packet from the computing subsystem 230 is used to transmit it from the computing subsystem 230-1 to the other nodes by the communication subsystem 210-1 at the communication link 14〇-1, 14〇-2. m. If each packet received by the communication subsystem 210-1 is directly transferred to the computing subsystem 230-1 for processing, then the computing subsystem 23 0_ -20-1379192 1 will continuously have to leave the low power state and enter high. Power status to handle each packet. This will consume a considerable amount of energy from the power supply 23 2 . To address these and other issues, the communication subsystem 210-1 can implement an interrupt combining technique. For example, the communication subsystem 210-1 can be configured to use one or more buffers 206-1-t to store or buffer incoming packets, and the buffer manager 216 can decide when to release or forward the stored packets to the calculation. The secondary system 23 0-1 is used for processing. The buffer manager 216 can determine when to transfer the packet from the buffer 206-1 -t to the calculation time according to a buffer management strategy designed to increase the energy storage of the calculation subsystem 2-3 and the entire node 1 〇-1. System 2 3 0-1. In various embodiments, the buffer manager 216 can implement a buffer management policy designed to allow the communication subsystem 210-1 and/or the computing subsystem 230-1 to enter and remain in a low power state for a longer period of time. While maintaining the communication subsystem 20-1 and/or calculating the Q〇S, throughput, and other performance requirements of the subsystem 230-1. In some embodiments, the buffer management policy can include various buffer management rules to determine when to forward packets from buffers 206-1 -t to computing subsystems 23 0-1. In one embodiment, for example, the buffer manager 216 can implement buffer management rules to store packets in the buffers 206-1-t during communication idle periods and to satisfy any combination of the following four buffer management conditions. When the stored packet is transferred from the buffer 206-Ι-t to the computing subsystem 23 0-1: (1) when the number of packets stored by one or more buffers 206-1 -t exceeds the variable reception threshold 値(2) When the buffer unload is paused, it has expired; (3) when the buffer unload event signal is received; and/or (4) when the communication is idle, the parameter is less than the communication idle period - 21 - 1379192 limit. It must be understood that these four buffer management conditions are exemplified by 'not limitation. This document is not intended to limit the embodiments. Buffer manager 216 can utilize one or more buffer management conditions in various combinations to trigger the release or transfer of any packets stored in buffers 206-1-t to computing subsystem 230" for processing. In one embodiment, for example, the buffer manager 216 may forward the packets stored in the buffers 206-1 -t to the computing subsystem 230-1 using direct memory access (DMA) techniques. The packet acceleration is moved from the buffer 206-1-t to the memory unit 2 3 4 used to calculate the secondary system 2 3 0-1. The buffer manager 216 can then issue an interrupt to the computing subsystem 230-1 (e.g., a processor) to indicate that the packet is within the memory unit 234 and is ready for processing by the secondary system 230-1. In one embodiment, when the number of packets stored by one or more buffers 206-1 -t exceeds a variable receive threshold, buffer manager 216 can forward the stored packets from buffers 206-1 -t To calculate the secondary system 23 0-1. For example, the communication subsystem 2 1 0-1 can include a watermark generator 2 1 7 coupled to the buffer manager 216 and the buffers 206-1 -t. Watermark generator 2 1 7 is operable to generate a variable receive threshold. The variable reception threshold may include a threshold or watermark defined for the buffer 20 6-1 -t. The variable access threshold can be calculated, derived, or determined as a function using at least the following three inputs: (1) receive data rate parameters; (2) buffer size parameters; and (3) communication restart start time parameters. The Receive Data Rate parameter may represent the communication rate of one or more of the transceivers 204-1-r. The buffer size parameter may represent the size of one or more buffers 206-1-t. Communication Weight -22- 1379192 The New Start Waiting Time parameter represents the amount of time or defined time interval (eg, 1 ms) required for the network link or communication subsystem 2 to leave a given power state and enter a high power state. For these or other communication parameters, the watermark generator 217 can generate variable reception thresholds periodically, continuously, or as needed to ensure that the variable reception threshold accurately reflects changes in communication rate, latency, and other network traffic. The buffer manager 216 can receive the variable receive threshold from the watermark generator 217 and receive the current buffer usage parameters from the buffer 20 6 - 1 t, and the current buffer usage parameters and the variable receive threshold.値 doing a comparison, and then initiating DMA transfer based on the comparison result. For example, when the number of information packets stored in the buffer exceeds the variable reception threshold, the buffer manager 216 initiates DMA transfer. In one embodiment, when buffering When the device unload pause has expired, the buffer manager 216 can forward the stored packet from the buffer 206_l-t to the computing subsystem 230-1. For example, the communication subsystem The 2 1 0-1 may include a buffer timer 218 to be coupled to the buffer manager 216. The buffer timer 218 may be a hardware or software timer to set or measure the defined time interval. The buffer unload pause can be set to load or load the buffer timer 218. The buffer timer 218 can monitor or perform the countdown until the buffer unload pause has expired. The buffer manager 216 can be configured to unload when the buffer is unloaded. When the pause has expired, the stored information packet is forwarded from buffer 206-1-t to computing subsystem 230-1. When buffer manager 216 is used in combination with another buffer management condition (such as variable receive The buffer management -23 - 1379192 216 can forward the stored packet when the buffer unloading pause expires before the buffer 206-1 -t stores the number of packets exceeding the variable reception threshold. In one embodiment, when the buffer manager 216 receives the buffer unload event signal, the buffer manager 216 can forward the stored packet from the buffer 206-Ι-t to the computing subsystem 22-1. For example, through The signaling system 210-1 can randomly receive event signals from portions of the node 110-1 that facilitate the buffer manager 216 to forward packets from the buffers 206-1 -t to the computing subsystem 230-1. For example, assume that computing subsystem 230-1 implements a chipset computer architecture that includes a memory controller hub (MCH) and an input/output (I/O) controller hub (ICH), such as Intel Corporation of Santa Clara, California ( "North Bridge" and "South Bridge" controller hubs manufactured by Intel® Corporation. Further, it is assumed that MCH and ICH use direct media interface (DMI) and associated links to connect information. Regarding the calculation of other portions of the subsystems 230-1, the DMI connections can be in various power states, such as a high power state L0 and a low power state L1. When the DMI link leaves the low power state L1 due to the activity of other devices to the high power state L0, the calculation subsystem 2300-1 can transmit a buffer offload event signal to the buffer manager 216. The buffer unload event signal can indicate to the buffer manager 216 that the computing subsystem 23 0-1 is already in a high power state and is active, and thus the buffer manager 216 can use the computing subsystem 2 3 0 - 1 The high power state is to transfer the packet from the buffer 206-l_t to the memory 234. When the buffer manager 216 is used in combination with another buffer management condition (such as a variable receive threshold), the buffer is received before the number of packets stored in the buffer 202-1-t exceeds the variable reception threshold. When the event signal is unloaded, the Buffer Manager-24-1379192 216 can forward the stored packet. In one embodiment, when the communication idle period parameter is less than the communication idle period threshold, the buffer manager 216 can implement a buffer management rule to transfer the stored packet from the buffer 2 06-1 -t to the computing subsystem. 2 3 0- 1. The communication idle period threshold may include a defined threshold for the communication idle period parameter. In general, the higher the parameters during communication idle, the lower the communication rate of the information on the communication links 140-1, 140-2, and vice versa. The communication idle period is configurable and can be set to determine when the communication idle period parameter is low enough to indicate a high communication rate, which does not need to tolerate the buffer 206-1 -t Extra waiting time. The buffer manager 216 can be configured to disable one or more of the buffers 2 06-1 -t to avoid buffers 206-1 -t when the communication idle period parameter is less than the communication idle period threshold Information packet. In some embodiments, the buffer manager 216 can be configured to send a signal to the controller 208 to modify the communication rate of the transceivers 204-1-r. For example, buffer manager 216 can instruct controller 208 to modify the communication rate based on its FIFO size and/or the amount of energy left. In one embodiment, for example, buffer manager 216 can receive or maintain buffer size parameters, energy measurement parameters, or both. The buffer size parameter can represent the FIFO size or FIFO remaining capacity. The energy measurement parameter can represent the energy remaining for a power source such as power source 232. The buffer manager 216 can be configured to issue a request to the controller 20 8 to adjust the communication rate of the transceivers 204-1-r based on the buffer size parameters. Similarly, the buffer manager 216 can be configured to receive power management messages having energy -25 - 1379192 measurement parameters from the power management controller 234 and to communicate the requirements based on the energy measurement parameters to adjust the transceivers 204·1·γ Communication rate. FIG. 3 illustrates a logic flow 300 in accordance with one or more embodiments. Logic flow 300 may be performed by various systems and/or devices, which may be implemented as a hardware 'software' and/or any combination thereof, as required by a given set of design parameters or performance limitations. For example, logic flow 300 may be implemented by a logic device (e.g., a processor) and/or logic (e.g., instructions, data, and/or code) executed by the logic device. To understand and not limit, logic flow 300 is illustrated with reference to Figures 1 and 2. The logic flow 300 can illustrate various operations of the nodes 1 10-1-m in a general manner, and in particular, the managed power system 120 and the power management module 130. As shown in FIG. 3, at block 302, logic flow 300 can modify the communication subsystem and calculate the power state of the subsystem, from a high power state to a low power state. At block 3 04, logic flow 3 00 may store the information packet in a buffer of the communication subsystem during communication idle to generate a calculated idle period. At block 306, logic flow 300 can generate a variable receive threshold for the buffer. At block 308, logic flow 300 can forward the stored information packet from the buffer to the computing subsystem based on the variable receive threshold. This document is not intended to limit the embodiments. In one embodiment, at block 302, logic flow 300 may modify the communication subsystem and calculate the power state of the subsystem, from a high power state to a low power state, and from a high power state to a low power state. For example, power management controller 234 can receive power management messages 240-1-q having calculated power state information generated by computing state module 23 2 and generated by -26- 1379192 network state module 2 1 2 Communication power status information. Power management controller 234 can receive power management messages 24〇_l-q from communication bus 220 via interfaces 214-1, 214-2, and 214-3. The power management controller 234 can process the power management messages Μ 0-1-q and determine appropriate communication power states (eg, NL0, NL1, NL2, etc.) and appropriate computing power states (eg, SO, SOil, S0i2, S0i3, S4 and so on). The power management controller 234 can transmit the communication power state and calculate the power state to the individual subsystems 210-1 via the power management messages 240-1-q on the communication bus 220 and the interfaces 214-1, 214-2, and 214-3. 210-2, and the secondary systems 210-1, 210-2 may thus modify their individual power states. In one embodiment, at block 304, logic flow 300 may store the information packet in a buffer during communication idle for use in the communication subsystem to generate a computational idle period. For example, the communication idle period may represent a time interval when the communication subsystem 210-1 does not receive (or expect to receive) information from the network on the communication links 140-1, 140-2. For example, the calculation idle period may represent a time interval when the computing subsystem 230-1 does not receive (or expect to receive) information from the communication subsystem 210-1. For example, the communication subsystem 2 1 0 -1 can receive the communication idle period parameter from the power management message 240-1-q for the communication subsystem 210. 1. It is transmitted by the power management controller 234. In this example, the communication idle period parameters can be calculated by the power management controller 234 using the power status information received from the secondary systems 210-1, 230-1. In another example, the communication subsystem 2 1 0 -1 can receive the communication idle period parameter from the network status module 2 1 2 . In either case, the communication subsystem 2 1 0 -1 can enter a low power state represented by the communication power state for a period of time -27 - 1379192 (as defined by the communication idle period parameter). The low power state can be entered directly by reducing the power to all of the communication elements of the communication subsystem 210-1 or indirectly by modifying the communication rate of the transceivers 204-1-r. Once the communication subsystem 210-1 enters a low power state, the buffer manager 216 can store the information packets in one or more receive buffers 206-1 -t during the communication idle period (as defined by the communication idle period parameter). Used in communication subsystem 210-1 to generate a computational idle period for computing subsystem 230-1. In some examples, communication subsystem 210-1 can calculate a idle period for computing subsystem 230-1, such that computing subsystem 230-1 can operate accordingly, such as switching to a low power state for a time interval, corresponding to Expect to calculate the idle period. In one embodiment, at block 306, logic flow 300 may generate a variable receive threshold for the buffer. For example, the watermark generator 217 can receive: a receive data rate parameter, a buffer size parameter, and/or a communication restart wait time parameter, and generate a variable receive threshold of the receive buffer 206-1-t according to the parameters ( For example, a buffer watermark). The watermark generator 217 can output the variable reception threshold to the buffer manager 216. In one embodiment, at block 308, logic flow 300 may forward the stored information packets from the buffer to the computing subsystem in accordance with the variable receive threshold. For example, the buffer manager 216 may receive a variable reception threshold from the watermark generator 2 17 , set the buffers 206 - 1 -t with the variable reception threshold, and may be periodic or non-periodic The number of information packets stored in the receive buffers 206-1 -t is compared to the variable receive threshold. After the number of information packets stored in the receive buffers 206-1 -t meets or exceeds the variable -28 - 1379192 receive threshold, the buffer manager can transfer the contents of the receive buffer 2 〇 6-lt via the DMA transfer mode. The billion unit 234 of the secondary system 230 is calculated for further processing. FIG. 4 illustrates a logic flow 4〇〇 in accordance with one or more embodiments. Logic flow 400 may be performed by various systems and/or devices, which may be implemented as hardware, software, and/or any combination thereof, as desired for a given set of design parameters or performance limitations. For example, logic flow 400 can be implemented by a logic device (e.g., a processor) and/or logic (e.g., instructions, data, and/or code) executed by the logic device. To understand and not limit, logic flow 400 is illustrated with reference to Figures 1 and 2. The logic flow 400 can illustrate the various operations of the node ′ in a general manner and specifically illustrates the managed power system 120 and the power management module 130. As shown in FIG. 4, logic flow 400 begins at block 420, wherein watermark generator 217 calculates or recalculates the variable by receiving data rate parameters, buffer size parameters, and/or communication restart latency parameters. Receive a threshold (such as a buffer watermark) and then fabricate a buffer watermark trigger. This allows the buffer manager 216 to react to various link speeds and delays. The buffer manager 2 16 can utilize the communication idle time parameter to determine how long the communication subsystem 210-1 and/or the computing subsystem 230-1 can be maintained in a low power state. Since the parameters do not have the expected traffic entering during the idle period of communication, the secondary systems 210-1, 230-1 can be electrically gated (if there is not enough time to enable the separate components of the secondary system 2 1 0 - 1 , 2 3 0 - 1 Do this economically). For example, a communication component implemented as a wireless transceiver (such as a transceiver 2〇4·1-〇 typically requires at least 8 ms of communication idle period to reference -29-1379192 to become a low power state. When the communication is idle period parameter Below 8 ms, this condition indicates that the incoming traffic is at a high data rate. According to this assumption, in the diamond block 404, when the communication idle period parameter is less than 8 ms, the buffer 206-1 is enabled at block 406. t disables to eliminate the extra delay (latency) that the buffer 2 0 6-Ι-t may cause. In diamond block 4 04, when the communication idle period parameter is greater than 8 ms, at block 408, anyway, The buffer manager 216 can set the variable receive threshold of the buffers 206-1 -t and the buffer offload pause of the buffer timer 218. At block 410, the buffer manager 216 can begin from one or more. The multi-receiver 204-1-r receives the packet and buffers the received packet in block 412 in one or more buffers 206-1-t until one or more buffer management conditions become available in diamond block 414 TRUE. In one embodiment, 'diamond block 414 can Estimate at least 4 conditions, including: (1) The first condition (condition 1) is TRUE, according to the variable reception threshold; (2) the second condition (condition 2) is TRUE, suspended according to buffer unloading値(3) The third condition (Status 3) is TRUE, according to the receipt of the buffer unloading event signal; and (4) The fourth condition (Status 4) is TRUE 'According to the event counter exceeding the third condition (Status) c) The 'for example' buffer manager 216 can use the various system events (eg, transfer interrupts) from the drive or the DMI link state between the ICH and the MCH as an input to trigger unbuffered from the receive buffer 206- A packet of 1 - t. For example, when the DMI is changed from L1 to L0 because of activity from other devices, its signaling to the communication subsystem "-" indicates that the host system is already active, and thus the buffer manager 216 This machine -30- 1379192 should be used to de-buffer the buffered packets from the receive buffer 206-lt if possible. The fourth condition (condition 4) is explained in more detail with reference to Figure 5, such as Referred to by reference 4 1 4a. When one of the four conditions tested in diamond block 414 is TRUE, 'buffer manager 216 invalidates buffer timer 218 at block 416 (eg, when powered), and Block 418 triggers the DMI link to leave the low power state L1 and enter the high power state L0. At block 420, the buffer manager 216 transfers the packet from the buffer 206-lt to the computing subsystem 230-1 using the DMA transfer mode. The memory unit 234, without buffering the packet, issues an interrupt to the computing subsystem 230-1. At block 422', the buffer manager 216 can selectively modify the communication rate of the transceivers 204-1-r to increase or decrease the rate of incoming packets based on their FIFO size and/or remaining energy. At diamond block 424, buffer manager 216 can determine if more packets have arrived within the awake timer. The buffer manager 2 1 6 maintains the time stamp of the last packet. When the time stamp minus the current time is less than the timer that keeps awake, the network is assumed to be busy. In this case, the buffer manager 216 will continue to operate at block 420. When the time stamp minus the current time is greater than the timer that is awake, the network is assumed to be idle. In this case, at block 426, the buffer manager 216 triggers the DMI link to exit the high power state L0 and enter the low power state L1, and continues operation at block 502 buffer manager 216. Referring again to one of the conditions evaluated by diamond block 414' buffer manager 216 may include a fourth condition (condition 4), sometimes referred to as a "failure - -31 - 1379192 security" trigger. The "fail-safe" trigger is designed to avoid a return condition 'i.e., a small number of packets (or a single packet) remain in the buffers 206-1 -t until the buffer timer 218 fails. This condition can be detected by monitoring the number of times a single packet is inside the buffer 206-1 -t when the buffer timer 218 fails. For example, if this condition occurs more than a certain number of times (eg, 3 times), the buffer manager 216 may temporarily disable the buffer 206-1 -t until the number of restart conditions can be set, thereby indicating the buffer 206- 1 -t should be enabled or reactivated. Examples of restarting conditions may include: (1) enabling buffers 2 06-1 -t according to a timer, such as after a defined time interval (eg, 1 sec); and (2) depending on a packet count, such as After receiving the defined number of packets (eg, 4000 packets), the buffers 206-1 -t are enabled. An example logic flow for evaluating the fourth condition is described in more detail with reference to FIG. FIG. 5 shows a logic flow 500 in accordance with one or more embodiments. The logic flow 500 can be performed by various systems and/or devices, and the logic flow 500 can be implemented as hardware, software, and/or any combination thereof, as desired for a given set of design parameters or performance limitations. For example, logic flow 500 can be implemented by a logic device (e.g., a processor) and/or logic (e.g., instructions, data, and/or code) executed by the logic device. For the sake of understanding and not limiting, the logic flow 500 will be explained with reference to Figs. The logic flow 500 can describe various operations of the node 1 1 〇 -1 - m in a general manner, and specifically describes the managed power system 120 and the power management module 1 130. The logic flow 500 can provide an example of a logic flow for evaluating the fourth condition (Case 4) -32-1379192 as indicated by the block 414 as described in Figure 4, with reference to Figure 4. To implement the fourth condition (Case 4), the buffer manager 216 can implement an event counter that counts the number of occurrences (X) of a particular event. The event may include the case where only a limited number of packets (e.g., one) are within the buffers 206-1 -t when the buffer unload is paused. When the event counter calculated event (X) exceeds the event threshold (N) (eg, N = 3), the buffer manager 216 can temporarily disable the buffer 206-1-t until the match is restarted. The situation is up. In one embodiment, for example, the buffer manager 216 can implement a packet counter to calculate the number (M) of packets in the buffer 506-1-t and set it with a buffer disable pause (B). Buffer timer 218. As shown in FIG. 5, in diamond block 502, when Μ is not equal to the packet threshold Μ (eg, Μ > 1 ), then at block 516, the buffer manager 2 16 resets the event counter (eg, Χ = 〇) and transfer control to block 416 of logic flow 400. At diamond block 502, when Μ is equal to the packet threshold 例如 (e.g., M = 1), at block 504, the buffer manager 216 increments the event counter by one (e.g., Χ = Χ +1). At diamond block 506, buffer manager 216 can determine if event counter (X) is greater than or equal to event threshold (e.g., Ν = 3). When the diamond block 506 is F A L S Ε, then at block 502, the buffer manager 216 is restarted. When the diamond block 506 is TRUE, then at block 508, the buffer manager 216 disables the buffer 206-1 -t. The buffer 216 then determines if a restart condition has occurred, such as when the buffer timer 218 is greater than the buffer disable pause (e.g., the timer is greater than L seconds) or the packet received due to the buffer 2 06-1 -t is disabled. The number is greater than the packet threshold (for example, P> 4000 seals - 33 - 1379192 packages). When both of the restart conditions are FALSE, the block returns to block 5 08. When any of the resume conditions are at block 510, the buffer manager 216 enables the buffer to send control to block 4 16 of logic flow 400.値Names N, L, and P are configurable settings. Various embodiments may provide several advantages for multiple uses. In one embodiment, for example, the buffer manager 206-1 -t can be used to allow calculation of the secondary system 23 0-1 state, thereby increasing energy conservation. In one embodiment, the power section communication is about 500 milliwatts (mW) to 2 watts (W). In some examples, various embodiments may be implemented as an article that may include computer readable media or storage media, compilations and/or materials for performing one or more embodiments of brain readable media or storage media. Examples that can be included but are not known. In various embodiments, for example, a disc, a disc, a flash memory or a firmware, which contains a computer for use in a general purpose processor or special application processor, is not intended to limit the embodiments. A hardware component, a software component, or a combination of both may be used. hard. Examples of physical components may include any of the examples previously proposed, and further include microprocessors, electrical (eg, transistors, resistors, capacitors, inductors, etc., logic gates, registers, semiconductor devices, wafers, when, then When the control is TRUE, then 206-1 -t, and E means that, Μ, : use and 216 and the buffer is held in a low power state, for example, can be achieved for the initiative to create articles. To store various logic operations. The power is limited to the previously mentioned items may include magnetic programming instructions, suitable for implementation. However, the implementation of various logic devices, circuit components, etc.), integrated micro-chip, wafer-34- 1379192 group and many more. Examples of software components can include software components, programs, application software, computer programs, applications, system programs, machine programs, operating system software, intermediate software, firmware, application programming interfaces (APIs), instruction sets, calculation codes, Computer code, code segment, computer code segment, word, 値, symbol or any combination thereof. Whether the embodiment is to be implemented using hardware components and/or software components can be varied according to any number of factors, such as required calculation rate, power level, thermal tolerance, processing cycle budget, input #data rate. 'Output data rate' memory resources, data bus speed and other design or performance limitations, as required for a given implementation. The words "couple" and "connect" may be used together with their derivatives. These terms are not necessarily synonymous with each other. For example, the terms "connected" and/or "coupled" may be used to mean that two or more elements are in direct physical or electrical contact with each other. However, the term "intimate" may also mean that two or more elements are not in direct contact with each other, but still operate or interact with each other. It must be emphasized that the abstract of the present invention allows the reader to quickly determine an abstract of the nature of the disclosure. It must be understood that the abstract is not intended to explain or limit the scope or meaning of the scope of the patent application. In addition, the various features are set forth in a single embodiment for the clarity of the disclosure. This method of revealing cannot be interpreted as a counter.  The claimed embodiment requires more features than what is described in each patent application. Rather, as the scope of the invention is claimed, the invention is intended to be less than all features of a single disclosed embodiment. Therefore, the scope of the patent application is hereby incorporated by reference in its entirety in its entirety in the extent of the disclosure of the disclosure of the disclosure. In the scope of the patent application, the terms "including -35-1379192 (including)" and "in which" are used as the respective terms "comprising" and "wherein". Equal terms. In addition, the terms "first", "second" and "third" etc. are used only for labeling purposes and are not intended to include numerical provisions in their objectives. Although it has been clearly defined in terms of structural characteristics and/or methodological behavior, it must be understood that the subject matter defined by the scope of the patent application is not limited to the specific characteristics or actions described above. Rather, the specific characteristics and behaviors set forth above are disclosed as examples of the scope of the application. Attached to the scope of patent application. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 shows an embodiment of a communication system. Figure 2 shows an embodiment of the device. Figure 3 shows an embodiment of the first logic diagram. Φ Figure 4 shows an embodiment of a second logic diagram. Figure 5 shows an embodiment of a third logic diagram. [Main component symbol description].  100: communication system 110-1: node 1 10-2: node 1 1 0 - m: node 120: managed power system - 36 - 1379192 120-1: managed power system 1 3 0 : power management module 130- 1 : Power Management Module 1 4 0 - 1 : Communication Link 140-2 : Communication Link 150-1-s: Power Management Packet Data Unit 204 - Bu r: Transmitter 206-1-t: Buffer 2 0 8 : controller

2 1 〇 :通訊次系統 2 1 2 ’·網路狀態模組 214-1 :電力管理介面 214-2 :電力管理介面 214-3 :電力管理介面 216 :緩衝器管理器 2 1 7 :水印產生器 218 :緩衝器定時器 2 2 0 :通訊匯流排 2 3 0 :計算次系統 2 3 2 :電源 234:電力管理控制器 236:電力控制定時器 240- 1 -q :電力管理訊息 2 5 0 - 1 -v :通訊連接 -37- 1379192 260 :電力狀態資訊2 1 〇: Communication subsystem 2 1 2 '·Network status module 214-1: Power management interface 214-2: Power management interface 214-3: Power management interface 216: Buffer manager 2 1 7: Watermark generation 218: Buffer Timer 2 2 0: Communication Bus 2 3 0: Calculation Sub System 2 3 2: Power Supply 234: Power Management Controller 236: Power Control Timer 240-1 -q: Power Management Message 2 5 0 - 1 -v : Communication connection -37- 1379192 260 : Power status information

-38--38-

Claims (1)

1379192 囔 r 附件3A :第〇97135495號申請專利範圍修正本 民國101年8月31日修正 十、申請專利範圍 1. 一種電力管理設備,包含: 電力管理模組,具有電力管理控制器,該電力管理控 制器耦接至傳收器:1379192 囔r Annex 3A: No. 97135495 Patent Application Amendment Amendment of August 31, 101 of the Republic of China. Patent Application Area 1. A power management device comprising: a power management module having a power management controller, the power The management controller is coupled to the transceiver: 受管理電力系統,耦接至該電力管理模組,該受管理 電力系統包含通訊次系統及計算次系統,該電力管理控制 器將該通訊次系統及該計算次系統自高電力狀態切換至低 電力狀態,以保存能量,該通訊次系統具有: 該傳收器; 緩衝器,耦接至該傳收器,該緩衝器於通訊閒置 期間儲存該傳收器之資訊封包,用於產生計算閒置期間; 水印產生器,耦接至該緩衝器,該水印產生器可 操作用以產生可變接收臨限値;以及 緩衝器管理器,稱接至該緩衝器及該水印產生 器,該緩衝器管理器可操作用以根據可變接收臨限値將該 儲存之資訊封包從該緩衝器轉送至該計算次系統,以自該 電力管理控制器接收具有能量測量參數之能量電力管理訊 息,並傳送一需求,以根據該能量測量參數來調整該傳收 器之通訊速率。 2 如申請專利範圍第1項之設備,當該緩衝器所儲存 之資訊封包之數目超過該可變接收臨限値時,該緩衝器管 理器可操作用以將該儲存之資訊封包從該緩衝器轉送至該 1379192 户月少I曰修正/¾ . 、 計算次系統。 3_如申請專利範圍第丨項之設備,該水印產生器可操 作用以根據接收資料速率參數、緩衝器大小參數以及通訊 重新開始等待時間參數而產生該可變接收臨限値。 4·如申請專利範圍第1項之設備,當通訊閒置期間參 數小於通訊閒置期間臨限値時,該緩衝器管理器可操作用 以使該緩衝器失能’以避免該緩衝器儲存該資訊封包。 5. 如申請專利範圍第1項之設備,包含緩衝器定時 器’親接至該緩衝器管理器,以緩衝器卸載暫停値來設定 該緩衝器定時器’該緩衝器管理器可操作用以當該緩衝器 所儲存之封包之數目超過該可變接收臨限値之前該緩衝器 卸載暫停値就已失效時’將該儲存之資訊封包從該緩衝器 轉送至該計算次系統。 6. 如申請專利範圍第1項之設備,該緩衝器管理器可 操作用以在該緩衝器所儲存之封包之數目超過該可變接收 臨限値之前接收緩衝器卸載事件訊號,並將該儲存之資訊 封包從該緩衝器轉送至該計算次系統,以回應該緩衝器卸 載事件訊號。 7. 如申請專利範圍第1項之設備,包含控制器,用以 耦接該傳收器,該緩衝器管理器可操作用以傳送一需求, 用於根據緩衝器大小參數來調整該傳收器之通訊速率。 8. —種電力管理方法,包含: 修改通訊次系統及計算次系統之電力狀態,由高電力 狀態修改至低電力狀態; -2- 1379192 AThe managed power system is coupled to the power management module, the managed power system includes a communication subsystem and a calculation subsystem, and the power management controller switches the communication subsystem and the calculation subsystem from a high power state to a low a power state to store energy, the communication subsystem having: the transceiver; a buffer coupled to the transceiver, the buffer storing the information packet of the transceiver during communication idle period, for generating calculation idle a watermark generator coupled to the buffer, the watermark generator operable to generate a variable receive threshold, and a buffer manager coupled to the buffer and the watermark generator, the buffer The manager is operative to forward the stored information packet from the buffer to the computing subsystem based on a variable receiving threshold to receive an energy power management message having energy measurement parameters from the power management controller and transmit A requirement to adjust the communication rate of the transceiver based on the energy measurement parameter. 2 as claimed in claim 1, wherein the buffer manager is operable to buffer the stored information from the buffer when the number of information packets stored in the buffer exceeds the variable reception threshold Transfer to the 1379192 households less than I曰 correction / 3⁄4 . , calculate the secondary system. 3_ The apparatus of claim 3, wherein the watermark generator is operative to generate the variable reception threshold based on the received data rate parameter, the buffer size parameter, and the communication restart waiting time parameter. 4. If the device of claim 1 is used, the buffer manager is operable to disable the buffer when the communication idle parameter is less than the communication idle period threshold to prevent the buffer from storing the information. Packet. 5. The device of claim 1, wherein the buffer timer is 'affined to the buffer manager to set the buffer timer with a buffer unloading pause '. The buffer manager is operable to The stored information packet is forwarded from the buffer to the computing subsystem when the number of packets stored by the buffer exceeds the variable reception threshold before the buffer unloads. 6. The device of claim 1, wherein the buffer manager is operative to receive a buffer unload event signal before the number of packets stored in the buffer exceeds the variable receive threshold, and The stored information packet is forwarded from the buffer to the computing subsystem to respond to the buffer unload event signal. 7. The device of claim 1, comprising a controller for coupling the transceiver, the buffer manager operable to transmit a demand for adjusting the transmission based on a buffer size parameter Communication rate of the device. 8. A power management method comprising: modifying a communication subsystem and calculating a power state of the subsystem, from a high power state to a low power state; -2- 1379192 A 於通訊閒置期間將資訊封包儲存於該通訊次系統之緩 衝器中,用於產生計算閒置期間; 產生用於該緩衝器之可變接收臨限値; 根據該可變接收臨限値將該儲存之資訊封包從該緩衝 器轉送至該計算次系統; 接收具有能量測量參數之電力管理訊息;以及 傳送一需求,以根據該能量測量參數來調整通訊速And storing the information packet in the buffer of the communication subsystem during the communication idle period for generating a calculation idle period; generating a variable reception threshold for the buffer; storing the storage according to the variable reception threshold Transmitting the information packet from the buffer to the computing subsystem; receiving a power management message having energy measurement parameters; and transmitting a demand to adjust the communication speed based on the energy measurement parameter 9 -如申請專利範圍第8項之方法,包含當該緩衝器所 儲存之資訊封包之數目超過該可變接收臨限値時,將該儲 存之資訊封包從該緩衝器轉送至該計算次系統。 1 〇.如申請.專利範圍第8項之方法,包含根據接收資 料速率參數、緩衝器大小參數以及通訊重新開始等待時間 參數而產生該可變接收臨限値。 1 1 ·如申請專利範圍第8項之方法,包含當通訊閒置 φ 期間參數小於通訊閒置期間臨限値時,使該緩衝器失能, 以避免該緩衝器儲存該資訊封包。 12.如申請專利範圍第8項之方法,包含當該緩衝器 所儲存之封包之數目超過該可變接收臨限値之前緩衝器卸 .載暫停値就已失效時,將該儲存之資訊封包從該緩衝器轉 送至該計算次系統。 1 3 ·如申請專利範圍第8項之方法,包含當在該緩衝 器所儲存之封包之數目超過該可變接收臨限値之前接收緩 衝器卸載事件訊號時,將該儲存之資訊封包從該緩衝器轉 -3- 1379192 Μ年於月^ I曰修正灰I 送至該計算次系統。 1 4.如申請專利範圍第8項之方法,包含一組電腦可 讀取程式元件,可操作用以組構一系統,用來實施如申請 專利範圍第8項之方法。9 - The method of claim 8, wherein the stored information packet is forwarded from the buffer to the computing subsystem when the number of information packets stored in the buffer exceeds the variable reception threshold . The method of claim 8, wherein the variable reception threshold is generated based on a received data rate parameter, a buffer size parameter, and a communication restart waiting time parameter. 1 1 · The method of claim 8 includes the method of disabling the buffer when the communication idle period φ is less than the communication idle period threshold to prevent the buffer from storing the information packet. 12. The method of claim 8, comprising storing the stored information when the number of packets stored in the buffer exceeds the variable reception threshold before the buffer is unloaded and expired Transfer from the buffer to the computing subsystem. 1 3 - The method of claim 8, comprising receiving the buffered information packet when the number of packets stored in the buffer exceeds the variable reception threshold before receiving the buffer unloading event signal Buffer to -3- 1379192 The following year ^ I 曰 Correction gray I is sent to the calculation subsystem. 1 4. The method of claim 8, comprising a set of computer readable program elements operable to construct a system for performing the method of claim 8 of the patent application.
TW97135495A 2007-09-17 2008-09-16 Buffering techniques for power management TWI379192B (en)

Applications Claiming Priority (16)

Application Number Priority Date Filing Date Title
US97303107P 2007-09-17 2007-09-17
US97303507P 2007-09-17 2007-09-17
US97303807P 2007-09-17 2007-09-17
US97304407P 2007-09-17 2007-09-17
US4761408P 2008-04-24 2008-04-24
US4788808P 2008-04-25 2008-04-25
US4886208P 2008-04-29 2008-04-29
US4886008P 2008-04-29 2008-04-29
US4885108P 2008-04-29 2008-04-29
US5203408P 2008-05-09 2008-05-09
US5270008P 2008-05-13 2008-05-13
US5373408P 2008-05-16 2008-05-16
US5437908P 2008-05-19 2008-05-19
US5666308P 2008-05-28 2008-05-28
US7898608P 2008-07-08 2008-07-08
US12/208,654 US8112646B2 (en) 2007-09-17 2008-09-11 Buffering techniques for power management

Publications (2)

Publication Number Publication Date
TW200933356A TW200933356A (en) 2009-08-01
TWI379192B true TWI379192B (en) 2012-12-11

Family

ID=44872689

Family Applications (1)

Application Number Title Priority Date Filing Date
TW97135495A TWI379192B (en) 2007-09-17 2008-09-16 Buffering techniques for power management

Country Status (1)

Country Link
TW (1) TWI379192B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9357269B2 (en) * 2009-11-17 2016-05-31 Broadcom Corporation Method and system for providing secure handling of information for complete internet anywhere
US9395795B2 (en) 2013-09-20 2016-07-19 Apple Inc. System power management using communication bus protocols

Also Published As

Publication number Publication date
TW200933356A (en) 2009-08-01

Similar Documents

Publication Publication Date Title
JP5047360B2 (en) Buffering technology for power management
US11656671B2 (en) Negotiating a transmit wake time
TWI586187B (en) Dynamic adaptation of a traffic inactivity timer
CN102959487B (en) Be provided for the wakeup logic waken up from low-power mode by electronic equipment
US20100325463A1 (en) Method and System for Optimized Power Management for a Network Device Supporting PCI-E and Energy Efficient Ethernet
US8732497B2 (en) Data processing apparatus, method for controlling data processing apparatus, and storage medium storing program
TW201203936A (en) Method and system for managing network power policy and configuration of data center bridging
US20110310859A1 (en) Basic service set scheduling based on media access controller states
TWI379192B (en) Buffering techniques for power management
US11832177B2 (en) Transmission system comprising first and second bridge devices
EP3066785B1 (en) Managing idle mode of operation in network switches
JP6827991B2 (en) Communication device, transfer speed change method and program

Legal Events

Date Code Title Description
MM4A Annulment or lapse of patent due to non-payment of fees