201235851 六、發明說明： 【發明所屬之技術領域】 本發明涉及藍牙設備通信。更具體地，本發明涉及藍牙低 功耗（BLE)設備的視窗作業系統便攜設備（Wind〇wsp()rtable device，WPD)介面。 【先前技術】 藍牙低功耗（BLE)是藍牙版本4.0中引入的藍牙標準的 i'a強。使用藍牙低功耗無線技術的設備可消耗其他藍牙使能產 品的部分電源。某些情況下，藍牙低功耗設備可能能夠在沒有 再充電的情況下依罪紐扣型電池運行超過一年。這類型設備在 各種場合下的部署可導致上述設備與基於視窗作業系統的機 器交互的需要。 比較本發明後續將要結合附圖介紹的系統，現有技術的其 他局限性和弊端對於本領域的技術人員來說是顯而易見的。 【發明内容】 根據本發明的一個方面，提供一種方法，所述方法包括： 在中央設備（central device)上執行視窗作業系統便攜設 備（WPD)驅動程式以使能中央設備上的—個或多健用程 式與週邊設備對接（interface)，其中： 所述週邊設備與所述中央設備通信連接；以及 將通用屬性配置檔（GATT)(generic attribute proflle) 用於使所述中央設備與所述週邊設備對接；以及 通過所述WPD驅動程式接入與所述週邊設備關聯的 資訊。201235851 VI. Description of the Invention: [Technical Field of the Invention] The present invention relates to Bluetooth device communication. More specifically, the present invention relates to a Windows operating system portable device (Wind〇wsp() rtable device, WPD) interface for Bluetooth low energy (BLE) devices. [Prior Art] Bluetooth Low Energy (BLE) is the i'a strong in the Bluetooth standard introduced in Bluetooth version 4.0. Devices that use Bluetooth low energy wireless technology can consume some of the power of other Bluetooth enabled products. In some cases, Bluetooth low energy devices may be able to operate on a sin-button battery for more than one year without recharging. The deployment of this type of device in a variety of situations can result in the need for the above devices to interact with a Windows based operating system based machine. Other limitations and disadvantages of the prior art will be apparent to those skilled in the art from a comparison of the present invention, which will be described in conjunction with the drawings. SUMMARY OF THE INVENTION According to one aspect of the present invention, a method is provided, the method comprising: executing a Windows Operating System Portable Device (WPD) driver on a central device to enable one or more on a central device The utility program interfaces with the peripheral device, wherein: the peripheral device is in communication with the central device; and a generic attribute proflle is used to make the central device and the periphery Device docking; and accessing information associated with the peripheral device through the WPD driver.
S 4 201235851 優選地’所述接入資訊包括與所述週邊設備關聯的一個或 多個服務和/或一個或多個特徵。 優選地，所述方法還包括： 在所述中央設備中生成代表所述週邊設備的視窗作業系 統便攜設備（WPDdevice)，所述WPD包括一個或多個WPD 物件； 通過所述WPD驅動程式將所述WPD設備的一個或多個 屬性映射為與所述週邊設備關聯的一個或多個服務和/或一個 或多個特徵；以及 通過所述一個或多個應用程式接入所述WPD設備的所述 一個或多個屬性。 優選地，所述週邊設備包括藍牙低功耗（Bluet〇〇th 1〇w energy，BLE)設備。 優選地，所述方法還包括通過所述WPD驅動程式控制與 所述週邊設備關聯的一個或多個功能。 、優選地，所述方法還包括枚舉與所述週邊設備關聯的一個 或多個服務和/或一個或多個特徵。 、」憂選地’所述方法還包括通過所述驅動程式向所述 週邊設備發送註冊(registration) ’從而通知所述中央設備與所 述週邊設備關聯的一個或多個特徵何時已改變。 優選地，所述方法還包括通過所述WPD驅動 週邊設備魏與所賴邊設備_的—個❹_徵變 的指示。 义 優選地’所述方法還包括通過所述伽驅動程式變更與 201235851 所述週邊設備關聯的一個或多個特徵。 優選地’所述方法還包括在所述中央設備内的藍牙主機棧 與所述週邊設備内的藍牙主機棧之間通信。 根據本發明的其他方面，提供一種系統，所述系統包括： 中央設備内的一個或多個處理器和/或電路’所述一個或 多個處理器和/或電路用於： 執行視窗作業系統便攜設備（WPD)驅動程式以使能所 述中央設備上的一個或多個應用程式與週邊設備對接，其中： 所述週邊設備與所述中央設備通信連接；以及 將通用屬性配置檔（GATT)用於使所述中央設備與 所述週邊設備對接；以及 通過所述WPD驅動程式接入與所述週邊設備關聯的 資訊。 優選地’所述接入資訊包括與所述週邊設備關聯的一個或 多個服務和/或一個或多個特徵。 優選地’所述一個或多個處理器和/或電路用於： 生成代表所述週邊設備的WPD設備，所述WPD包括〆 個或多個WPD物件； 通過所述WPD驅動程式將所述WPD設備的一個或多個 屬性映射為與所述週邊設備關聯的一個或多個服務和/或一個 或多個特徵；以及 通過所述一個或多個應用程式接入所述WPD設備的所述 —個或多個屬性。 優選地，所述第二設備包括藍牙低功耗（BLE)設備。 5 201235851 優選地’所述一個或多個處理器和/或電路用於通過所述 WPD驅動程式控制與所述週邊設備關聯的一個或多個功能。 優選地’所述一個或多個處理器和/或電路用於牧舉與所 述週邊設備關聯的一個或多個服務和/或一個或多個特徵/ 優選地，所述一個或多個處理器和/或電路用於通過所述 WPD驅動程式向所述週邊設備發送註冊，從而通知所述中央 設備與所述週邊設備關聯的一個或多個特徵何時已改變。 優選地’所述-個或多個處理器和/或電路用於通過所述 WPD驅動程雜親週邊設備概與所魏輕侧聯的一 個或多個特徵已改變的指示。 優選地，所述-個或多個處理器和/或電路用於通過所述 WPD驅動程式變更與所述週邊設備關聯的一個或多個特徵。 優選地，所述一個或多個處理器和/或電路用於在所述中 央設備内的藍牙主機棧與所述週邊設備内的藍牙主機棧之間 通信。 從以下描述和圖中將更充分理解本發明的各種優點、方面 和新穎特徵以及其闡述實施例的細節。 【實施方式】 本發明可涉及藍牙低功耗設備的視窗作業系統便攜設備 介面的方法及系統。依照本發明的各個實施例，安裝並在中央 5又備上執行的視窗作業系統便攜設備（WPD)驅動程式可使 能中央設備上的一個或多個應用程式與週邊設備（例如，藍牙 低功耗（BLE)設備）對接（interface with)。例如，中央設備 了月b疋基於視窗作業系統的機器。週邊設備可與中央設備通作 201235851 連接’並可_通關性配置織WPD驅動程式對接。通過 WPD驅練式’巾央設備可接人、魏、狐和/或變更與週 邊設備關聯的資訊。此外，同樣通過侧^鶴程式，中央設 備可控制週邊設備的操作和/或功能^與週邊設備關聯的資訊 可包含服務和特徵。每個特徵可具有—個或多個值和/或描述 符。邏輯上或實質上代表週邊設備的WPD設備可由驅 動程式生成。WD設備可包括-個或乡個WPD物件。wpD 物件特性可映射為與週邊設備關聯的服務和/或特徵^與週邊 設備關聯的特徵可包括一個或多個值和/或一個或多個描述 符。某些情況下，當中央設備内出現有多個週邊設備時，一個 以上的WPD設備可能是可利用的。 圖1是依照本發明實施例的利用視窗作業系統便攜設備 介面與一個或多個藍牙低功耗設備交互的基於視窗作業系統 的機器的示例性框圖。參考圖1，顯示了設備10〇、12〇、n〇 和140。設備1〇〇是基於視窗作業系統的機器，其可包括支援 視窗作業系統便攜設備的合適的邏輯、電路、代碼和/或介面。 儘管設備100可能是個人電腦、筆記本電腦、或平板電腦，但 設備100不限於此，也可利用支援基於視窗作業系統的運行的 其他機器。 設備120、130和140可包括合適的邏輯、電路、代碼和/ 或介面’其可用於支援藍牙通信的藍牙低功耗的使用。在這一 點上，例如，設備120、130和140可稱為BLE設備或BLE-使能設備。設備100可用於分別通過藍牙連接122、132和142 與設備120、130和140通信。 201235851 設備100支援的視窗作業系統便攜設備可能指的是一類 基於物件的體系結構或平臺，可在基於視窗作業系統的機器 (即，中央設備）中利用所述基於物件的體系結構或平臺、從 而允許接入一個或多個外部設備（即，週邊設備）。外部或週 邊設備可包括但不限於與基於視窗作業系統的機器通信連接 的密匙卡、便攜醫療設備、媒體播放器、數碼相機和/或數碼 攝像機、移動電話或其他類似設備。圖丨中顯示的設備12〇、 130和140可相當於外部或週邊設備，而設備1〇〇可相當於中 央設備。視窗作業系統便攜設備提供的基於物件的體系結構可 包括一個或多個應用程式介面（^j)，所述一個或多個應用程 式介面使能在基於視窗作業系統的機器上運行或執行的應用 程式與一個或多個外部設備的交互。 設備100上運行或執行的一個或多個應用程式可利用視 _作業系統便攜設備來執行與外部設備相關的各種操作。例 如，視_作業系統便攜設備可使能應用程式與外部設備連接、 從外部設備搜索和/或檢索資訊、解或枚_屬㈣連接的 外部設備、確定外部設備力、發送和/或生成待存儲在外 部設備内的資訊、變更外部設備内的資訊、控制外部設備、和 /或檢測外部設備的存在或缺乏。 圖1中還顯示設備100中分別相當於設備120、130和14〇 的邏輯或虛擬表示的WPD設備124、134和144。設備1〇〇上 執行的應用程式可利用WPD設備124、134和144來分別執 行與設備120、130和140相關的操作。可生成與視窗作業系 統便攜設備支援的基於物件的體系結構相容的WPD設備 201235851 124、134和144。每個WPD設備124、134和144可包括可 稱為WPD物件的一個或多個物件。這些物件可具有屬性、事 件或類似物。物件的實例是存儲物件。 設備120、130和140所支援的藍牙低功耗操作可能指的 是包含在藍牙4.0中的說明書。藍牙低功耗引入新協定以簡化 低功耗配置檔（profile)的發展和實現。例如，新協定可包含 屬性協定（ATT)和通用屬性配置檐（GATT)。 運行中，設備120可通過使用與藍牙連接丨22關聯的藍牙 低功耗協定與設備1〇〇通信。在設備1〇〇上執行的應用程式可 能能夠通過介面與設備120交互，使用設備1〇〇所支援的視窗 作業系統便攜設備基於物件的體系結構實現所述介面。上述介 面可包括允許藍牙低功耗協定與視窗作業系統便攜設備的基 於物件的體糸結構通信的驅動程式。在這一點上，該驅動程式 可用於生成WPD設備124，從而使能設備1〇〇和設備丨2〇之 間的交互。 相似地，設備130和140可分別通過使用與藍牙連接132 和142關聯的藍牙低功耗協定與設備1〇〇通信。設備1〇〇上執 行的一個或多個應用程式可能能夠通過介面與設備13()和14〇 交互，使用設備1〇〇所支援的視窗作業系統便攜設備基於物件 的體系結構實現所述介面這些介面可包括允許藍牙低功耗協 定與視窗作業系統便攜設備的基於物件的體系結構通信的驅 動程式。在這一點上，該驅動程式可用於生成WPD設備134 和144’從而分別使能設備1〇〇與設備13〇和14〇之間的交互。 圖2A和2B各自是依照本發明實施例的基於視窗作業系 201235851 統的機器與BLE設備之間通過wpd介面的對接的實例的示音 圖。參考圖2A，顯示基於視窗作業系統的機器1〇〇和藍牙低 功耗設備250。藍牙低功耗設備250可能與圖i中顯示的設備 120、130和140的任何一個大致相似或相同。 基於視窗作業系統的機器100可包括存儲模組21〇、處理 器模組220和通信模組230。存儲模組210可包括合適的邏輯、 電路、代碼和/或介面’其可用於存儲與—個或多個應用程式 的執行相關聯的資料和/或代碼。存儲模組21〇可用於存儲用 於支援與視窗作業系統便攜設備關聯的進程的資料和/或代 碼。存儲模組210可包括單個存儲裝置或多個存儲裝置。存儲 裝置可能是積體電路’例如，所述碰t路包括祕隨機存取 記憶體（DRAM)、㈤步DRAM (SDRAM)、雙倍數據速率 SDRAM (DDR SDRAM 或 DDR2 SDRAM)、或快閃記憶體。 處理器模組220可包括合適的邏輯、電路、代碼和/或介 面’其可用於運行或執行基於視窗作業系統的作業系統（〇s) 和一個或多個應用程式。處理器模組22G可用於支援與視窗作 業系統便攜設備關聯的進程。處理器模组22〇可包括單個處理 裝置或多個處理裝置。處理裝置可能是積體電路，例如，所述 積體電路包括t央處理H (CPU)或主處驾、基帶處理器、 圖形處理器、或其他類型的專用處理器。處理器模組22〇還可 用於處理與通信模組23〇的發送和/或接操作關聯的資料和/ 或控制信號。 通信模組230可包括合適的邏輯、電路、代碼和/或介面， 其可用於與一個或多個外部設備通信。通信模組230可支援與 201235851 外部设備的無線和/或有線通信。相對於無線通信操作，通信 模組230可包括用於發送和/或接收射頻（RF)信號的一個或 多個無線電（未顯示）。例如，通信模組23〇可包括藍牙無線 電’所述藍牙無線電可祕支觀牙低雜龄和使能與藍牙 低功耗設備25G的通信。通信模組23G還可支援其他類型的無 線電’例如用於無線局域網（WLAN)、個人局域網（pAN)’’、、 或蜂窩網路中通信的無線電。 風牙低功耗§又備250可包括存儲模組26〇、處理器模組27〇 和通信模組280。存儲模組260可包括合適的邏輯、電路、代 碼和/或介面，其可用於存儲與藍牙低功耗設備250的運行相 關聯的資料和/或代媽。例如’存儲模組26〇可用於存儲用於 支援與藍牙低功耗相關聯的進程的資料和/或代碼。與上述存 儲模組210相似的是，存儲模組細可包括單個存儲裝 個存儲裝置。 處理器模組270可包括合適的邏輯、電路、代碼和/或介 面’其可用於運行或執行作業系統和一個或多個應用程式。例 如，處理器模組270可用於支援與藍牙低功耗相關聯的進程。 與上述處理器模組220相似的是，處理器模組27()可包括 :==裝置。處理器模组27°可包括處理藍牙基 =信模組280可包括合適的邏輯、電路、代碼和/或介面， 其可用於與—個或乡_加設備通信。附錢備可 可能是利用不同無線通信技術（例如，WLAN)的 又&點上，通信模組280可包括用於發送和/或接收 201235851 RF信號的-個或多個無線電（未顯示）。例如，通信模組· 可包括藍牙無線電，所健牙無線電可麟域藍牙低功耗協 定和使能與基於視窗作業系統的機器 100的通信。 藍牙低功耗設備250可用於支援各種藍牙相關的協定、配 置檔、和/或進程。可由用於處理時賴鍵的（timingeritical) 無線電介面喊牙控觸和用於處理高級資料的藍牙主機機 實現該藍牙協議機。利用通信模組28〇和處理器模、组27〇可實 現藍牙控纖’所述通信触可包減牙無線電，所述處理器 模組可包括例如微處理H的處理裝置。藍牙域棧可實現為在 處理器模組270上運行的部分〇s、或為〇s頂部的套裝程式 的例示。某些情況下’藍牙控制機和藍牙主機棧可在處理器模 組270中的相同處理裝置上運行或執行。 運行中，藍牙低功耗設備250可通過使用藍牙連接290中 的藍牙低功耗協定與基於視窗作業系統的機器1⑻通信。基於 視窗作業系統的機器100的處理器模組22〇上執行的應用程式 可能能夠通過介面與藍牙低功耗設備25〇交互，使用基於視窗 作業系統的機器100支援的視窗作業系統便攜設備基於物件 的體系結構實現所述介面。上述介面可包括允許藍牙低功耗協 定與視窗作業系統便攜設備的基於物件的體系結構通信的驅 動程式。在這一點上，該驅動程式可用於生成如圖2B中所示 的WPD設備240，從而使能基於視窗作業系統的機器1〇〇與 藍牙低功耗設備250之間的交互。WPD設備240是藍牙低功 耗設備250的邏輯或虛擬表示，基於視窗作業系統的機器100 中的視窗作業系統便攜設備基於物件的體系結構支援所述藍 13 201235851 牙低功耗設備。 圖3是依照本發明實施例的使基於視窗作業系統的機器 與BLE設備對接的示例性WPD體系結構的示意圖。參考圖 3 ’顯示基於視窗作業系統的機器1〇〇和藍牙低功耗設備250。 相對於基於視窗作業系統的機器100，顯示應用程式3〇〇和視 窗作業系統驅動程式基礎（WDF)主進程320,兩者均可能是 基於視窗作業系統的機器100所支援的部分WPD體系結構。 WDF主進程320的實例是Wudfhost.exe進程。應用程式300 可包括一個或多個結合視窗作業系統便攜設備使用的AP工 310。例如’ API 310可稱為WPD API。WDF主進程320可包 括結合視窗作業系統便攜設備使用的驅動程式。例如，驅動程 式330可稱為WPD驅動程式。 驅動程式330可用於生成或例示與藍牙低功耗設備250關 聯的WPD設備。然後WPD設備可由應用程式300利用，從 而與藍牙低功耗設備250交互。WPD設備可相當於藍牙低功 耗設備250的邏輯或虛擬表示，所述WPD設備可包含與藍牙 低功耗設備250關聯的屬性。例如，WPD設備可包括代表藍 牙低功耗設備250的各種屬性的一個或多個物件。 圖3中還顯示可在基於視窗作業系統的機器100上運行或 執行的藍牙主機棧340。藍牙主機棧340可包括各種協定和配 置檔，其包含但不限於GATT 350、ATT 360、低功耗安全管理 器協議（SMP) (security manager protocol) 370、以及邏輯鏈 路控制和適配協議（L2CAP ) 380。ATT 360可用作無線協定、 而GATT350可用作描述在組合服務中如何使用ATT的協定。 201235851 例如，GATT350可用於定義如何將ATT屬性集合至服務中、 以及用於為述與服務關聯的特徵。因此，Ga丁τ 350和ATT 360 可利用特徵來描述設備的狀態、以及利用服務來描述這些特徵 如何彼此相關以及如何使用它們。SMp 37〇可用於配對和傳送 特疋的祗地分配。L2CAP 380可用於在較高層協議、段和重裝 套裝程式之料路傳送資料、f理乡肺料傳輸。某些情況 下 ’ SMP 370 可與 L2CAP 380 綁定。 相對於基於視窗作業系統的機器1〇〇，顯示藍牙控制器 315和藍牙無線電325。藍牙控制器31s可包括用於控制藍牙 無線電介©的合適的賴、電路、代碼和/或介面。藍牙控制 器315可能是圖2B中顯示的處理器模組22〇和/或通信模組 230的一部分。例如，藍牙控制器315可用於實現藍牙控制棧。 藍牙無線電325可包括合適的邏輯、電路、代碼和/或介面， 其可用於與其他設備上的藍牙無線電無線通信。 相對於藍牙低功耗設備250，顯示應用程式3〇5和藍牙主 機棧345。藍牙主機棧345可包括各種協定和配置槽，其包含 但不限於 GATT 355、ATT 365、SMP 375 和 UCAp 385。顯示 的與藍牙主機機345相關的協定可與顯示的與藍牙主機機34〇 相關的那些協疋大致相似。同樣相對於藍牙低功耗設備， 顯示分別與藍牙控制器315和藍牙無線電325大致相似的藍牙 控制器317和藍牙無線電327。 運行中’應用程式300可通過API 310、通過開啟設備處 理（devicehandk)和發送輸入/輸出⑽）控制代碼與驅動程 式33〇通信。儘管未顯示，但是奶31〇和驅動程式33〇可利 15 201235851 用串列器來打包或解包緩衝區中的命令和/或參數。驅動程式 330可用於生成WPD設備’應用程式3〇〇使用所述wpD設 備來與藍牙低功耗設備250交互。驅動程式330可基於低功耗 協定GATT 350和ATT 360與藍牙主機棧340通信。與藍牙低 功耗設備250相關聯的服務和/或特徵可通信至驅動程式33〇， 所述驅動程式330反過來將資訊映射為由視窗作業系統便攜 設備定義的適當物件屬性。例如，與藍牙低功耗設備25〇關聯 的特徵可包括一個或多個值和/或一個或多個描述符。 藍牙低功耗設備250中的應用程式3〇5可與設備所提供的 特定功能相關聯。應用程式305可用於從藍牙低功耗設備25〇 獲取資訊，例如與操作、特徵、或藍牙低功耗設備250的能力 相關的資訊。通過藍牙連接290、通過使資訊從藍牙主機棧345 向藍牙主機棧340傳遞可從藍牙低功耗設備25〇向基於視窗作 業系統的機器100通信這些資訊。當WDF主進程32〇從藍牙 主機棧340接收資訊時，該資訊可由wpD驅動程式33〇映射 為代表藍牙低功耗設備250的WPD設備的屬性。相應地，應 用程式300可從WH)設備接入與藍牙低功耗設備25〇關聯的 資訊。 相似地，應用程式300所提供的控制或命令可通過基於視 窗作業系統的機器100中可利用的WPD設備進入藍牙低功耗 又備250中。例如，應用程式3〇〇可向與藍牙低功耗設備250 關聯的特徵的特定描述符通信註冊，從而通知應用程式3〇〇特 徵何時已改變。-旦在贿符上完雜冊，如果油述符關聯 的特徵改變，可從藍牙低功耗設備250向應用程式3〇〇提供通 201235851 知。 與圖3的描述相關的運行是當藍牙低功耗設備25〇是具有 電池服務和電池電壓特徵的感應袋（proximity )的另一實 例。在這一實例中，驅動程式330揭示了 一方法，通過所述方 法應用程式300可讀取藍牙低功率設備25〇的電池電壓。例 如，通過驅動程式330、應用程式300可從代表藍牙低功耗設 備250的WPD設備的屬性讀取電池電壓的值。可從藍牙低功 耗設備250内的應用程式305產生的資訊中獲取屬性資訊。因 此，當應用程式300要求驅動程式330讀取電池電壓時，驅動 程式330可使用ATT和GATT協定來與感應袋對話、確定電 池電壓的當前值、並提供作為WPD設備中屬性的值。然後， 應用程式300可從WPD設備接入資訊。對於確定藍牙低功耗 設備250的剩餘電池壽命和採取的相應措施，這一資訊是有用 的。 在與圖3的描述相關的運行的另一實例中，藍牙低功耗設 備250可能是具有溫度服務（temperature seryice)和溫度值特 徵的溫度計。在這一實例中，驅動程式33〇揭示了 一方法，通 過所述方法應用程式300可從代表藍牙低功耗設備25〇的 WPD設備讀取藍牙低功耗設備25〇的溫度值。因此，當應用 程式300要求驅動程式33〇讀取當前溫度水準時，驅動程式 33〇可使ATT和GATT協絲與溫度騎話、較溫度水準 的當前值、並提供作為WPD設備中屬性的資訊。然後，應用 程式300可從WPD設備接入資訊。 其他實例包含使用應用程式3〇〇和驅動程式來向密匙 17 201235851 卡的警報特徵寫入值、從而使密匙卡發出蜂鳴，以及使用應用 程式300和驅動程式330從稱重台（weight scale)讀取權值特 徵（weight value characteristic )、從而顯示權值。 儘管上述實例通常涉及藍牙低功耗設備，但本發明不限於 此。還可利用其他設備，例如使能GATT或其他類似協定或配 置檔的使用、從而與利用視窗作業系統便攜設備的設備對接的 設備。例如’這些設備可稱為GATT-使能設備、並可包含藍牙 低功耗設備。 此外’儘管相對於圖3的上述實例涉及單個藍牙低功耗設 備250和基於視窗作業系統的機器1〇〇中的單個應用程式 300，但本發明並不限於此。例如，多個週邊設備可引入基於 視窗作業系統的機器1〇〇中的多個WPD設備。基於視窗作業 系統的機器100中的一個或多個應用程式可用於接入一個或 多個WPD設備。 圖4是依照本發明實施例的與GATT_使能設備的wpD介 面關聯的運行的示例性實例的流程圖。參考圖4，顯示流程圖 400，在所述流程圖中，在步驟41〇，可配對基於視窗作業系 統的機器和GATT-使能設備。例如，基於視窗作業系統的機器 可能是上述基於視窗作業系統的機器1〇〇。例如，GATT_使能 設備可能是設備120、130、140以及上述藍牙低功耗設備250 的其中之一。在步驟420，基於視窗作業系統的機器上的WPD 驅動程式可執行GATT發現程式、從而枚舉GATT-使能設備的 服務、特徵和描述符。在步驟430，WPD驅動程式可在基於 視窗作業系統的機器上生成WPD設備，所述WPD設備具有 201235851 代表與GATT-使能設備關聯的服務和/或特徵的屬性。髓^設 備可包括-個«個物件，那些物件的屬性映射為與GATT_ 使能設備關聯的服務和/或特徵。在步驟44〇，基於視窗作業系 統的機器上運行的應用程式可通過WpD驅動程式接入GATT_ 使能設備的資訊和/或操作。WPD .驅動程式可為接入的應用程 式向WPD設備提供這些資訊。 圖5是依照本發明實施例的與GATT_使能設備的介 面關聯的運行的另-實例的流程圖。參考圖5，顯示流程圖 500，在所述流程圖巾’在步驟51〇，在基於視窗作業系統的 機器（例如，上述基於視窗作業系統的機器1〇〇)中可生成一 個以上的WPD設備。每個wpD設備可由驅動程式生 成’所述WPD驅動程式與WPD設備所代表的該類型的GATT_ 使能設備相關聯。 在步驟520，基於視窗作業系統的機器中的一個或多個應 用程式（例如，上述應用程式300)可通過WPD設備和WPD 驅動程式接入GATT-使能設備的資訊和/或操作。例如，應用 程式可用於管理-個以上的藍牙低功耗設備内的電池電壓。上 述應用程式可從代表藍牙低功耗設備的各種WpD設備中接入 屬性資訊，從而確定這些設備中每個的當前電池電壓。 依照本發明的實施例，中央設備（例如’基於視窗作業系 統的機器100)可執行WPD驅動程式從而使能中央設備上的 一個或多個應用程式與週邊設備對接。例如，週邊設備可能是 设備120、130和14〇、以及藍牙低功耗設備25〇的其中之一。 WPD驅動程式可與參照圖3的上述驅動程式330大致相同或 201235851 相似。此外’週歧備可射央設備通錢接、並可糊㈣了 來與WPD驅絲式對接。—錢行電^軸減，可通過 WPD驅動程式接人與週邊設備_的資訊。接人資訊可包括 與_設備關聯的-個或多個服務和/或一個或多個特徵。例 如，該特徵可包括-個或多個值和/或一個或多個描述符。 “可在中央設備中生成代表週邊設備的WPD言史備。WPD 設備可包括稱為WPD物件的—個或多個物件。中央設備可通 過WPD驅動程式將WPD物件的特性（例如，屬性）映射為 與週邊設備關聯的-個或多個服務和/或一個或多個特徵。採 用上述映射’朗&式可接人侧^設備以與週邊設備交互。 中央α備可通過WPD驅動程式用於控制週邊設備的一個 或多個功能。中央設備可用於枚舉與週邊設備_的一個或多 個服務和/或-個或多個特徵。中央設備可通過糊^驅動程式 用於向週邊δχ備發送註冊，從而通知巾央設備_邊設備關聯 1一個或多個特徵何時已改變。中央設備也可通過謂^驅動 程式用於魏邊設備接收朗邊設賴聯的—個❹個特徵 改變的麵。巾央設備可㈣卿鶴程式臉變更與週 /又備關聯的-個或多個魏。巾央設備與週邊設備之間的通 可通過中央&備中的藍牙主機棧和週邊^備_的藍牙主機 棧發生，兩者均利用ATT和GATT。 本發明的另-實侧提供-辦暫時性機詩/或電腦可 :存儲和/或介質，其上存朗電腦代碼和/或電難式具有至 =個可由機器和則腦執行的代碼段，使得機器和/或電腦 執仃本文所描述的藍牙低雜設備的WPD介面。 201235851 本發明可料财體、倾，或錄、硬騎 本發明可財至少-個電腦祕巾轉巾方式實現 中的不同部分以分散方式實現。任: 了乂實現所妨㈣電腦錢他雜都是可適 =的結合可以是安裝有電腦程式的通用電腦系統，通:安 裝和執行所雜式㈣電腦祕，使其按所述方法運行。 本發明還可以通過電腦程式產品進行實施，所述套裝程式 含能夠實縣發明綠的全部舰，t其安朗電腦系統工中 時’通過運行，可以實現本發明的方法。本”文件中的電腦 程式所指的是：可以_任何程式語言、代碼或槪編寫的一 組指令的任何運算式，該指令組使系統具有資訊處理能力，以 直接實現特定魏，或在進行下述-個或兩個步驟之後，_ 換成其他語言、代碼或符號；b)以不同的格式再現，實現特定 功能。 本發明是通過幾個具體實施例進行說明的，本領域技術人 員應當理解，在不脫離本發明範圍的情況下，還可以對本發明 進行各種變換及等同替代。另外，針對特定情形或具體情況， 可以對本發明做各種修改，而不脫離本發明的範圍。因此，本 發明不局限於所公開的具體實施例，而應當包括落入本發明權 利要求範圍内的全部實施方式。 相關申請的交叉引用 本專利申請參考並享有申請曰為2010年12月6曰、申請 號為No. 61/419,911的美國臨時專利申請的優先權和權益，該 21 201235851 專利申請在此全文引用，以供參考。 【圖式簡單說明】 圖1是依照本發明實施例的利用視窗作業系統便攜設備 介面與一個或多個藍牙低功耗設備交互的基於視窗作業系統 的機器的示例性框圖； 圖2A和2B各自是依照本發明實施例的基於視窗作業系 統的機器與BLE設備之間通過WPD介面的對接的實例的示意 圖； 圖3是依照本發明實施例的使基於視窗作業系統的機器 與BLE設備聯繫的示例性WPD體系結構的示意圖； 圖4是依照本發明實施例的與GATT-使能設備的WPD介 面關聯的運行的示例性實例的流程圖； 圖5是依照本發明實施例的與GATT-使能設備的WPD介 面關聯的運行的另一實例的流程圖。 【主要元件符號說明】 基於視窗操作系統的機器100 設備120、130、140 藍牙連接 122、132、142 視窗操作系統便攜設備（WPD)設備124、134、144 存儲模塊 210 處理器模塊220 通信模塊 230 藍牙低功耗設備250 處理器模塊 270 藍牙連接 290 應用程序 305 WPD設備 240 存儲模塊 260 通信模塊 280 應用程序 300 應用程序接口（API) 310S 4 201235851 Preferably said said access information comprises one or more services and/or one or more features associated with said peripheral device. Preferably, the method further comprises: generating, in the central device, a Windows operating system portable device (WPD device) representing the peripheral device, the WPD comprising one or more WPD objects; Mapping one or more attributes of the WPD device to one or more services and/or one or more features associated with the peripheral device; and accessing the WPD device by the one or more applications Describe one or more attributes. Preferably, the peripheral device comprises a Bluetooth low energy (BLE) device. Advantageously, the method further comprises controlling, by said WPD driver, one or more functions associated with said peripheral device. Preferably, the method further comprises enumerating one or more services and/or one or more features associated with the peripheral device. The method of "sorryly" further includes transmitting, by the driver, a registration to the peripheral device to notify the central device when one or more features associated with the peripheral device have changed. Preferably, the method further comprises: driving, by the WPD, an indication of the neighboring device and the device. Preferably, the method further comprises altering, by the gamma driver, one or more features associated with the peripheral device of 201235851. Preferably said method further comprises communicating between a Bluetooth host stack within said central device and a Bluetooth host stack within said peripheral device. According to other aspects of the present invention, a system is provided, the system comprising: one or more processors and/or circuits within a central device, the one or more processors and/or circuits for: executing a window operating system a portable device (WPD) driver to enable one or more applications on the central device to interface with peripheral devices, wherein: the peripheral device is in communication with the central device; and a generic attribute profile (GATT) Used to interface the central device with the peripheral device; and access information associated with the peripheral device through the WPD driver. Preferably said access information comprises one or more services and/or one or more features associated with said peripheral device. Preferably said one or more processors and/or circuits are operable to: generate a WPD device representing said peripheral device, said WPD comprising one or more WPD objects; said WPD by said WPD driver One or more attributes of the device are mapped to one or more services and/or one or more features associated with the peripheral device; and the accessing the WPD device by the one or more applications - One or more attributes. Preferably, the second device comprises a Bluetooth Low Energy (BLE) device. 5 201235851 Preferably said one or more processors and/or circuits are operable to control one or more functions associated with said peripheral device by said WPD driver. Preferably said one or more processors and/or circuits are for shelving one or more services associated with said peripheral device and/or one or more features/preferably, said one or more processes And/or circuitry for transmitting a registration to the peripheral device via the WPD driver to notify the central device when one or more features associated with the peripheral device have changed. Preferably, the one or more processors and/or circuits are used to indicate an indication that one or more features of the Wei light sideband have changed by the WPD driver. Advantageously, said one or more processors and/or circuits are operable to alter one or more characteristics associated with said peripheral device by said WPD driver. Advantageously, said one or more processors and/or circuits are operative to communicate between a Bluetooth host stack within said central device and a Bluetooth host stack within said peripheral device. The various advantages, aspects, and novel features of the invention and the details of the embodiments of the invention are described. [Embodiment] The present invention may relate to a method and system for a portable device interface of a Windows operating system of a Bluetooth low energy device. In accordance with various embodiments of the present invention, a Windows Operating System Portable Device (WPD) driver installed and executed centrally 5 enables one or more applications and peripheral devices on the central device (eg, Bluetooth low power) Consumption (BLE) device) interface with. For example, the central device has a monthly operating system based on the Windows operating system. Peripheral devices can be connected to the central device for 201235851 and can be docked with the WPD driver. The WPD-assisted 'snap device' can be used to access people, Wei, Fox, and/or change information associated with peripheral devices. In addition, the central device can also control the operation and/or function of the peripheral device through the side program, and the information associated with the peripheral device can include services and features. Each feature can have one or more values and/or descriptors. A WPD device that logically or substantially represents a peripheral device can be generated by a driver. The WD device may include one or a local WPD object. The wpD object characteristics may be mapped to services and/or features associated with peripheral devices. Features associated with peripheral devices may include one or more values and/or one or more descriptors. In some cases, more than one WPD device may be available when multiple peripheral devices are present in the central device. 1 is an exemplary block diagram of a Windows-based operating system-based machine that utilizes a Windows operating system portable device interface to interact with one or more Bluetooth low energy devices in accordance with an embodiment of the present invention. Referring to Figure 1, devices 10〇, 12〇, n〇, and 140 are shown. Device 1 is a Windows operating system based machine that may include suitable logic, circuitry, code, and/or interfaces to support the Windows operating system portable device. Although the device 100 may be a personal computer, a notebook computer, or a tablet computer, the device 100 is not limited thereto, and other machines that support the operation of the Windows-based operating system may be utilized. Devices 120, 130, and 140 may include suitable logic, circuitry, code, and/or interfaces that can be used to support Bluetooth low energy usage for Bluetooth communications. In this regard, for example, devices 120, 130, and 140 can be referred to as BLE devices or BLE-enabled devices. Device 100 can be used to communicate with devices 120, 130, and 140 via Bluetooth connections 122, 132, and 142, respectively. 201235851 The Windows operating system portable device supported by device 100 may refer to a class of object-based architecture or platform that may utilize the object-based architecture or platform in a Windows operating system-based machine (ie, a central device), thereby Allow access to one or more external devices (ie, peripheral devices). External or peripheral devices may include, but are not limited to, a key card, a portable medical device, a media player, a digital camera, and/or a digital video camera, a mobile phone, or the like that is in communication with a Windows operating system based machine. The devices 12〇, 130, and 140 shown in the figure may correspond to external or peripheral devices, and the device 1〇〇 may be equivalent to a central device. The object-based architecture provided by the Windows operating system portable device can include one or more application interfaces (^j) that enable applications to be run or executed on a Windows operating system based machine. Program interaction with one or more external devices. One or more applications running or executing on device 100 may utilize the visual system portable device to perform various operations associated with the external device. For example, the visual system portable device enables the application to connect with external devices, search for and/or retrieve information from external devices, resolve external devices connected to the genus (four), determine external device forces, send and/or generate Information stored in an external device, changing information within an external device, controlling an external device, and/or detecting the presence or absence of an external device. Also shown in FIG. 1 are WPD devices 124, 134, and 144 in device 100 that correspond to logical or virtual representations of devices 120, 130, and 14A, respectively. The application executing on device 1 can utilize WPD devices 124, 134, and 144 to perform operations associated with devices 120, 130, and 140, respectively. WPD devices 201235851 124, 134, and 144 that are compatible with the object-based architecture supported by the Windows operating system portable device can be generated. Each WPD device 124, 134, and 144 can include one or more items that can be referred to as WPD objects. These items may have attributes, events or the like. An example of an object is a storage item. The Bluetooth low energy operation supported by devices 120, 130, and 140 may refer to the instructions contained in Bluetooth 4.0. Bluetooth low energy introduces new protocols to simplify the development and implementation of low-power profiles. For example, a new agreement can include an attribute agreement (ATT) and a generic attribute configuration (GATT). In operation, device 120 can communicate with device 1 by using a Bluetooth low energy protocol associated with Bluetooth port 22. The application executing on device 1 may be able to interact with device 120 through the interface, using the Windows operating system portable device supported by device 1 to implement the interface based on the architecture of the object. The above interface may include a driver that allows the Bluetooth Low Energy Protocol to communicate with the object-based structure of the Windows operating system portable device. In this regard, the driver can be used to generate the WPD device 124 to enable interaction between the device 1 and the device. Similarly, devices 130 and 140 can communicate with device 1 by using Bluetooth low energy protocols associated with Bluetooth connections 132 and 142, respectively. One or more applications executing on device 1 may be able to interact with devices 13() and 14〇 through the interface, using the Windows operating system portable device supported by device 1 to implement the interface based on the architecture of the object. The interface may include a driver that allows the Bluetooth Low Energy Protocol to communicate with the object-based architecture of the Windows operating system portable device. In this regard, the driver can be used to generate WPD devices 134 and 144' to enable interaction between device 1 and device 13A and 14A, respectively. 2A and 2B are each a sound diagram of an example of docking between a machine and a BLE device via a wpd interface, in accordance with an embodiment of the present invention. Referring to Figure 2A, a Windows 1 based operating system and a Bluetooth low energy device 250 are shown. Bluetooth low energy device 250 may be substantially similar or identical to any of devices 120, 130, and 140 shown in FIG. The Windows operating system based machine 100 can include a storage module 21, a processor module 220, and a communication module 230. The storage module 210 can include suitable logic, circuitry, code, and/or interfaces that can be used to store data and/or code associated with execution of one or more applications. The storage module 21A can be used to store data and/or code for supporting processes associated with the Windows operating system portable device. The storage module 210 can include a single storage device or multiple storage devices. The storage device may be an integrated circuit 'for example, the touch channel includes a secret random access memory (DRAM), a (five) step DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM or DDR2 SDRAM), or a flash memory. body. The processor module 220 can include suitable logic, circuitry, code, and/or interfaces that can be used to run or execute a Windows-based operating system (〇s) and one or more applications. The processor module 22G can be used to support processes associated with portable devices of the Windows operating system. The processor module 22A can include a single processing device or multiple processing devices. The processing device may be an integrated circuit, for example, including a central processing H (CPU) or a master driver, a baseband processor, a graphics processor, or other type of dedicated processor. The processor module 22A can also be used to process data and/or control signals associated with the transmission and/or operation of the communication module 23A. Communication module 230 can include suitable logic, circuitry, code, and/or interfaces that can be used to communicate with one or more external devices. The communication module 230 can support wireless and/or wired communication with the 201235851 external device. The communication module 230 can include one or more radios (not shown) for transmitting and/or receiving radio frequency (RF) signals relative to wireless communication operations. For example, the communication module 23A can include Bluetooth radio. The Bluetooth radio can communicate with the Bluetooth low energy device 25G. Communication module 23G may also support other types of radios, such as those used in wireless local area networks (WLANs), personal area networks (pANs), or in cellular networks. The wind power low power consumption § 250 can include a storage module 26A, a processor module 27A, and a communication module 280. The storage module 260 can include suitable logic, circuitry, code, and/or interfaces that can be used to store materials and/or surrogates associated with the operation of the Bluetooth low energy device 250. For example, the 'memory module 26' can be used to store data and/or code for supporting processes associated with Bluetooth low energy. Similar to the storage module 210 described above, the storage module can include a single storage device. Processor module 270 can include suitable logic, circuitry, code, and/or interfaces that can be used to operate or execute an operating system and one or more applications. For example, processor module 270 can be used to support processes associated with Bluetooth low energy. Similar to the processor module 220 described above, the processor module 27() can include: == means. The processor module 27° may include processing Bluetooth base = the letter module 280 may include suitable logic, circuitry, code, and/or interfaces that may be used to communicate with the device or the device. The additional module may be utilizing different wireless communication technologies (eg, WLAN). The communication module 280 may include one or more radios (not shown) for transmitting and/or receiving 201235851 RF signals. . For example, the communication module can include a Bluetooth radio, a Bluetooth radio low power protocol, and communication with the Windows 100 based operating system. Bluetooth low energy device 250 can be used to support various Bluetooth related protocols, profiles, and/or processes. The Bluetooth protocol machine can be implemented by a timing electronic radio interface for handling processing and a Bluetooth host machine for processing advanced data. The communication touch-capture attenuated radio can be implemented using a communication module 28 and a processor module, group 27, which can include a processing device such as a microprocessor H. The Bluetooth domain stack can be implemented as part of the 〇s running on the processor module 270, or as an illustration of the package at the top of the 〇s. In some cases the 'Bluetooth controller and Bluetooth host stack can be run or executed on the same processing device in processor module 270. In operation, the Bluetooth low energy device 250 can communicate with the Windows operating system based machine 1 (8) by using the Bluetooth Low Energy Protocol in the Bluetooth connection 290. The application module executed on the processor module 22 of the Windows operating system based machine may be able to interact with the Bluetooth low energy device 25 through the interface, and the Windows operating system supported by the Windows 100 based operating system is based on the object. The architecture implements the interface. The above interface may include a driver that allows the Bluetooth low energy protocol to communicate with the object based architecture of the Windows operating system portable device. In this regard, the driver can be used to generate the WPD device 240 as shown in Figure 2B to enable interaction between the Windows® based operating system based device and the Bluetooth low energy device 250. The WPD device 240 is a logical or virtual representation of the Bluetooth low power device 250, which is based on the object-based architecture of the Windows operating system portable device in the Windows 100 operating system-based device 100. 3 is a schematic diagram of an exemplary WPD architecture for interfacing a Windows-based operating system with a BLE device in accordance with an embodiment of the present invention. Referring to Figure 3', a Windows 1 based operating system and Bluetooth low energy device 250 are shown. The application program 3 and the window operating system driver base (WDF) main process 320 are displayed relative to the Windows operating system based machine 100, both of which may be part of the WPD architecture supported by the Windows operating system based machine 100. An example of WDF main process 320 is the Wudfhost.exe process. The application 300 can include one or more AP workers 310 that are used in conjunction with the Windows operating system portable device. For example, 'API 310' can be referred to as the WPD API. The WDF main process 320 can include drivers that are used in conjunction with the Windows operating system portable device. For example, driver 330 can be referred to as a WPD driver. Driver 330 can be used to generate or instantiate a WPD device associated with Bluetooth low energy device 250. The WPD device can then be utilized by the application 300 to interact with the Bluetooth low energy device 250. The WPD device may be equivalent to a logical or virtual representation of the Bluetooth low power device 250, which may include attributes associated with the Bluetooth low energy device 250. For example, the WPD device can include one or more items that represent various attributes of the Bluetooth low energy device 250. Also shown in Figure 3 is a Bluetooth host stack 340 that can be run or executed on the Windows operating system based machine 100. The Bluetooth host stack 340 can include various protocols and profiles including, but not limited to, GATT 350, ATT 360, a low power security manager protocol (SMP) 370, and a logical link control and adaptation protocol ( L2CAP) 380. ATT 360 can be used as a wireless protocol, and GATT 350 can be used as a protocol to describe how ATT is used in a composite service. 201235851 For example, GATT 350 can be used to define how ATT attributes are aggregated into services, and for the features associated with the service. Thus, Gadin τ 350 and ATT 360 can utilize features to describe the state of the device and utilize services to describe how these features relate to each other and how to use them. SMp 37〇 can be used for pairing and transmission of local distribution. The L2CAP 380 can be used to transfer data to the higher-level protocols, segments, and reload packages. In some cases the 'SMP 370 can be bound to the L2CAP 380. The Bluetooth controller 315 and the Bluetooth radio 325 are displayed relative to the Windows operating system based machine. The Bluetooth controller 31s may include suitable circuitry, circuitry, code and/or interfaces for controlling the Bluetooth radio. Bluetooth controller 315 may be part of processor module 22A and/or communication module 230 shown in Figure 2B. For example, the Bluetooth controller 315 can be used to implement a Bluetooth control stack. Bluetooth radio 325 may include suitable logic, circuitry, code, and/or interfaces that may be used to wirelessly communicate with Bluetooth radios on other devices. The application 3〇5 and the Bluetooth host stack 345 are displayed relative to the Bluetooth low energy device 250. The Bluetooth host stack 345 can include various protocols and configuration slots including, but not limited to, GATT 355, ATT 365, SMP 375, and UCAp 385. The protocols associated with the Bluetooth host machine 345 that are displayed may be substantially similar to those shown in relation to the Bluetooth host machine 34A. Also with respect to the Bluetooth low energy device, a Bluetooth controller 317 and a Bluetooth radio 327, which are substantially similar to the Bluetooth controller 315 and the Bluetooth radio 325, respectively, are displayed. The in-run application 300 can communicate with the driver 33 via the API 310, through the device handlek and the transmit input/output (10) control code. Although not shown, the milk 31〇 and the driver 33〇利利 15 201235851 use a serializer to package or unpack commands and/or parameters in the buffer. The driver 330 can be used to generate a WPD device' application 3 to use the wpD device to interact with the Bluetooth low energy device 250. Driver 330 can communicate with Bluetooth host stack 340 based on low power protocol GATT 350 and ATT 360. The services and/or features associated with the Bluetooth low energy device 250 can be communicated to the driver 33, which in turn maps the information to the appropriate object attributes defined by the Windows operating system portable device. For example, features associated with the Bluetooth low energy device 25A may include one or more values and/or one or more descriptors. The application 3〇5 in the Bluetooth low energy device 250 can be associated with a particular function provided by the device. The application 305 can be used to obtain information from the Bluetooth low energy device 25, such as information related to the operation, features, or capabilities of the Bluetooth low energy device 250. This information can be communicated from the Bluetooth low energy device 25 to the Windows based system based machine 100 via Bluetooth connection 290 by passing information from the Bluetooth host stack 345 to the Bluetooth host stack 340. When the WDF main process 32 receives information from the Bluetooth host stack 340, the information can be mapped by the wpD driver 33 to the attributes of the WPD device representing the Bluetooth low energy device 250. Accordingly, the application 300 can access information associated with the Bluetooth low energy device 25 from the WH) device. Similarly, the controls or commands provided by the application 300 can be entered into the Bluetooth Low Energy 250 by the WPD device available in the Windows 100 based operating system. For example, the application 3 can register a particular descriptor communication with a feature associated with the Bluetooth low energy device 250 to notify the application that the feature has changed. Once the essay is completed on the bribe, if the characteristics associated with the oil descriptor change, the Bluetooth low energy device 250 can be provided to the application. The operation associated with the description of Figure 3 is another example of when the Bluetooth low energy device 25 is a proximity sensor with battery service and battery voltage characteristics. In this example, driver 330 reveals a method by which the battery voltage of the Bluetooth low power device 25A can be read by the method application 300. For example, the value of the battery voltage can be read from the properties of the WPD device representing the Bluetooth low energy device 250 by the driver 330, the application 300. The attribute information can be obtained from information generated by the application 305 in the Bluetooth low power device 250. Thus, when application 300 requires driver 330 to read the battery voltage, driver 330 can use the ATT and GATT protocols to talk to the inductive bag, determine the current value of the battery voltage, and provide a value that is an attribute in the WPD device. The application 300 can then access the information from the WPD device. This information is useful for determining the remaining battery life and corresponding actions taken by the Bluetooth low energy device 250. In another example of operation associated with the description of FIG. 3, Bluetooth low energy device 250 may be a thermometer with temperature seryice and temperature value characteristics. In this example, the driver 33 discloses a method by which the application 300 can read the temperature value of the Bluetooth low energy device 25 from the WPD device representing the Bluetooth low energy device 25A. Therefore, when the application 300 requires the driver 33 to read the current temperature level, the driver 33 can make the ATT and GATT synergy and temperature ride, the current value of the temperature level, and provide information as an attribute in the WPD device. . The application 300 can then access the information from the WPD device. Other examples include using the application program and driver to write values to the alert feature of the key 17 201235851 card, thereby causing the key card to beep, and using the application 300 and driver 330 from the weighing scale (weight scale) ) Read the weight value characteristic to display the weight. Although the above examples generally relate to Bluetooth low energy devices, the invention is not limited thereto. Other devices may also be utilized, such as devices that enable the use of GATT or other similar agreements or profiles to interface with devices utilizing Windows operating system portable devices. For example, these devices may be referred to as GATT-enabled devices and may include Bluetooth low energy devices. Further, although the above example with respect to Fig. 3 relates to a single Bluetooth low energy device 250 and a single application 300 in a Windows operating system based machine, the present invention is not limited thereto. For example, a plurality of peripheral devices can introduce a plurality of WPD devices in a Windows operating system based machine. One or more applications in the Windows-based operating system 100 can be used to access one or more WPD devices. 4 is a flow diagram of an illustrative example of operation associated with a wpD interface of a GATT_enabled device in accordance with an embodiment of the present invention. Referring to Figure 4, a flow diagram 400 is shown in which, in step 41, a window based operating system based machine and a GATT-enabled device can be paired. For example, a Windows-based operating system-based machine may be the above-described Windows operating system-based machine. For example, the GATT_enabled device may be one of the devices 120, 130, 140 and the Bluetooth low energy device 250 described above. At step 420, the WPD driver on the Windows operating system based machine can execute the GATT discovery program, thereby enumerating the services, features, and descriptors of the GATT-enabled device. At step 430, the WPD driver can generate a WPD device on a Windows operating system based machine having 201235851 attributes representing services and/or features associated with the GATT-enabled device. The medullary device can include - an object whose attributes are mapped to services and/or features associated with the GATT_enabled device. In step 44, the application running on the Windows operating system based machine can access the GATT_ enabled device information and/or operation via the WpD driver. The WPD driver provides this information to WPD devices for incoming applications. Figure 5 is a flow diagram of another example of operation associated with the interface of a GATT_enabled device in accordance with an embodiment of the present invention. Referring to FIG. 5, a flowchart 500 is shown in which at least one WPD device can be generated in a Windows-based operating system-based machine (eg, the above-described Windows operating system-based machine 1). . Each wpD device can be generated by a driver. The WPD driver is associated with a GATT_enabled device of the type represented by the WPD device. At step 520, one or more applications (e.g., the application 300 described above) in the Windows operating system based machine can access the information and/or operations of the GATT-enabled device via the WPD device and the WPD driver. For example, an application can be used to manage battery voltages in more than one Bluetooth low energy device. The application can access attribute information from various WpD devices representing Bluetooth low energy devices to determine the current battery voltage for each of these devices. In accordance with an embodiment of the present invention, a central device (e.g., Windows-based operating system-based machine 100) can execute a WPD driver to enable one or more applications on the central device to interface with peripheral devices. For example, the peripheral device may be one of devices 120, 130, and 14A, and a Bluetooth low energy device 25A. The WPD driver can be substantially the same as the above-described driver 330 of FIG. 3 or 201235851. In addition, Zhou Qiu can shoot the central equipment for money, and can be paste (four) to interface with WPD. - Money line power ^ axis reduction, can be accessed through the WPD driver and peripheral devices _ information. The access information may include one or more services and/or one or more features associated with the device. For example, the feature can include one or more values and/or one or more descriptors. "WPD history can be generated in the central device to represent peripheral devices. WPD devices can include one or more objects called WPD objects. The central device can map the characteristics (eg, attributes) of WPD objects through the WPD driver. For the one or more services and/or one or more features associated with the peripheral device, the above-mentioned mapping 'Lang & can be connected to the peripheral device to interact with the peripheral device. The central alpha device can be used by the WPD driver. To control one or more functions of the peripheral device. The central device can be used to enumerate one or more services and/or one or more features of the peripheral device. The central device can be used by the paste driver to the periphery δχ The device sends a registration to notify the device _ when the device association 1 has changed one or more features. The central device can also use the driver to receive the feature change of the edge device. The surface of the towel can be (4) Qinghe program face change and weekly / again associated with - one or more Wei. The communication between the central device and the peripheral device can pass through the central & standby Bluetooth host stack and week The standby Bluetooth stack takes place, both of which utilize ATT and GATT. The other side of the present invention provides - a temporary machine poem / or computer: storage and / or media, on which the computer code and / / Or the electric hard-working type has a code segment that can be executed by the machine and the brain, so that the machine and/or the computer execute the WPD interface of the Bluetooth low-hetery device described herein. 201235851 The present invention can be used for financial, dumping, or recording, The hard ride of the invention can be at least a computer secret towel transfer method to achieve different parts of the implementation in a decentralized manner. Any: 乂 乂 乂 四 四 四 四 四 四 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑 电脑A general-purpose computer system that: installs and executes a computer (4) computer secret to operate in accordance with the method described above. The present invention can also be implemented by a computer program product, which includes all ships capable of inventing green in the county. The computer program in this document refers to any expression of a set of instructions that can be written in any programming language, code, or 槪. The instruction set enables the system to have information processing capabilities to directly implement a specific Wei, or to change to another language, code or symbol after performing the following one or two steps; b) to reproduce in a different format to achieve a specific function . The present invention has been described in terms of several specific embodiments, and it is understood by those skilled in the art that various modifications and equivalents can be made to the present invention without departing from the scope of the invention. In addition, various modifications may be made to the invention without departing from the scope of the invention. Therefore, the invention is not limited to the specific embodiments disclosed, but all the embodiments falling within the scope of the appended claims. CROSS-REFERENCE TO RELATED APPLICATIONS This application is hereby incorporated by reference in its entirety in its entirety the entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire entire for reference. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an exemplary block diagram of a Windows-based operating system-based machine utilizing a Windows operating system portable device interface to interact with one or more Bluetooth low energy devices in accordance with an embodiment of the present invention; FIGS. 2A and 2B Each is a schematic diagram of an example of a docking between a Windows-based operating system-based machine and a BLE device through a WPD interface in accordance with an embodiment of the present invention; FIG. 3 is a diagram of a Windows-based operating system-based machine in association with a BLE device in accordance with an embodiment of the present invention. Schematic diagram of an exemplary WPD architecture; FIG. 4 is a flow diagram of an illustrative example of operation associated with a WPD interface of a GATT-enabled device in accordance with an embodiment of the present invention; FIG. 5 is a GATT- A flow diagram of another example of a run of a WPD interface associated with a device. [Main component symbol description] Windows operating system based machine 100 device 120, 130, 140 Bluetooth connection 122, 132, 142 Windows operating system portable device (WPD) device 124, 134, 144 storage module 210 processor module 220 communication module 230 Bluetooth Low Energy Device 250 Processor Module 270 Bluetooth Connection 290 Application 305 WPD Device 240 Storage Module 260 Communication Module 280 Application 300 Application Programming Interface (API) 310
S 22 201235851 藍牙控制器 315 藍牙控制器 317 視窗操作系統驅動程序基礎（WDF)主進程 320 藍牙無線電 325 藍牙無線電 327 驅動程序 330 藍牙主機棧 340 藍牙主機棧 345 通用屬性配置文件（GATT ) GATT 355 屬性協議（ATT) 360 ATT 365 低功耗安全管理器協議（SMP) 370 SMP 375 邏輯鏈路控制和適配協議（L2CAP) 380 L2CAP 385 23S 22 201235851 Bluetooth Controller 315 Bluetooth Controller 317 Windows Operating System Driver Base (WDF) Main Process 320 Bluetooth Radio 325 Bluetooth Radio 327 Driver 330 Bluetooth Host Stack 340 Bluetooth Host Stack 345 General Property Profile (GATT) GATT 355 Properties Protocol (ATT) 360 ATT 365 Low Power Security Manager Protocol (SMP) 370 SMP 375 Logical Link Control and Adaptation Protocol (L2CAP) 380 L2CAP 385 23