TWI310919B - Context-aware and real-time item tracking system architecture and scenariors - Google Patents

Context-aware and real-time item tracking system architecture and scenariors Download PDF

Info

Publication number
TWI310919B
TWI310919B TW92100575A TW92100575A TWI310919B TW I310919 B TWI310919 B TW I310919B TW 92100575 A TW92100575 A TW 92100575A TW 92100575 A TW92100575 A TW 92100575A TW I310919 B TWI310919 B TW I310919B
Authority
TW
Taiwan
Prior art keywords
information
item
data
mark
tag
Prior art date
Application number
TW92100575A
Other languages
Chinese (zh)
Other versions
TW200307208A (en
Inventor
S Ebert Peter
Haller Stephan
Lin Tao
Weng Jie
K Vogler Hartmut
S Mo Brian
J Swan Richard
Original Assignee
Sap Ag
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 US10/137,207 external-priority patent/US7151453B2/en
Priority claimed from US10/136,852 external-priority patent/US7233958B2/en
Priority claimed from US10/210,859 external-priority patent/US7290708B2/en
Priority claimed from US10/232,764 external-priority patent/US6901304B2/en
Priority claimed from US10/255,115 external-priority patent/US20030132855A1/en
Priority claimed from US10/285,381 external-priority patent/US6843415B2/en
Application filed by Sap Ag filed Critical Sap Ag
Publication of TW200307208A publication Critical patent/TW200307208A/en
Application granted granted Critical
Publication of TWI310919B publication Critical patent/TWI310919B/en

Links

Landscapes

  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Description

1310919 九、發明說明: 【發明所屬之技術領域】 本發明大致係關於追蹤實體項目。 【先前技術】 用來追蹤實體項目的典型系統通常包含電腦裝置以及 軟體。此種系統維護指出狀況的資訊,如追蹤中物件現今 的位置。可想像此為一虛擬世界。 在傳統系統中,一項目的實際狀況與系統指出的狀況之 間經常會有差距。差距時常係因為錯誤的人工資料輸入以 及系統的限制所造成。這類問題所產生的結果是,對於事 實,傳統系統會反映出歪曲的及碎裂的圖像。此外,大多 數的傳統系統僅能觀察到有限的範圍及解析度,舉例來 說,系統僅能分辨產品的種類以及數量而無法分辨個別的 項目。 【發明内容】 本說明書說明方法及設備,包括用於情境感知與即時 追縱項目的電腦程式產品。 「項目(item)」一詞用在本說明書中代表一真實的、 實體的物件,以避免使用「物件(〇bj ect)」一詞的模擬兩可, 該詞在下文中僅用來指稱一種資料處理結構(construct)。 一般來說,本發明之特色為可用於追蹤項目之系統、 方法以及為了執行方法之各種態樣所安裝的元件。依照本 發明的一種系統,其係包含一標記元件,該標記元件包含 6 1310919 可指出對一個或多個項目加上標記之標準的資訊,每個標 記包含一全球唯一識別記號:一含有與標記溝通之裝置的 物件介面元件,且更包含用於接收情境資訊的裝置:一情 境感知智慧包含用於處理情境資訊之邏輯以及指出系統行 動以回應情境資訊之邏輯;以及一通訊中介軟體用於在系 統的元件間溝通以及與系統外部的裝置溝通。 一般來說,本發明之特色為可用於情境感知及即時追蹤 項目之系統、方法以及為了執行方法之各種態樣所安裝的 元件。依據此一態樣的一種方法,係可執行接收多次 (multiple instances)標記讀取資料(tag — read — data)的動 作,每次包含自附著於某個項目上的標記中讀取的資訊, 所讀取的資訊包含一自動從標記中讀取之一唯一數位識別 記號,每次在讀取該一唯一識別記號時也包含狀態資訊, 其包括一對應標記的位置以及其附著的項目,該多個標記 讀取資料全體包含自附著於多個項目的標記中讀取的資 訊;接收一或多次情境資訊,每次描述一相關之不可標記 的實體狀況(physical cirumstances),該情境資訊指出一 包含該狀況之位置的狀態,該多次情境資訊整體係包含可 描述多個狀況的資訊:使用該接收到的標記讀取資料以及 情境資訊以維護一虛擬世界中的虛擬項目及虛擬狀況,該 虛擬項目包括可用於多個項目之每一者的一物件,而該虛 擬狀況包含可用於多個狀況之每一者的一物件,每一物件 代表其所對應的項目或情境的狀態;並偵測發生於虛擬世 7 1310919 界中代表狀況的虛擬狀況與代表項目的虛擬項目之間的互 動。 一般來說,本發明之特色為讓資訊可在企業間取得之系 統、方法以及可執行本發明方法之各種態樣所安裝的元 件。依據此態樣的一種方法,係可執行自一第一企業接收 多次標記讀取資料之動作,每次包含自附著於某個項目上 的標記中自動讀取資訊,所讀取的資訊凡包含至少一種唯 一數位識別記號,每次在讀取該一唯一識別記號時也包含 狀態資訊,其包括一對應標記的位置以及其附著的項目, 自該第一企業所接收之該多次標記讀取資料全體係包含自 附著於第一多次項目的標記中讀取的資訊;該標記讀取資 料包含源自於第一企業之第一資料處理系統的資料:使用 接收自該第一企業的標記讀取資料來維護虛擬世界中的虛 擬代表物(representatives),該虛擬代表物包含代表該多次 項目之每一者的代表物,每個虛擬代表物代表其對應項目 的狀態:自一第二企業接收多次第二標記讀取資料,每次 包含自附著於一項目上並至少含有一個唯一數位識別記號 的標記中自動讀取的資訊,每次亦包含狀態資訊,其包含 相應之標記的位置以及其附著的項目,自第二企業接收的 多個標記讀取資料全體地包含自附著於至少其中一個第一 多次項目的標記中讀取的資訊,自第二企業接收的標記讀 取資料包含源自於第二企業的一種第二資料處理系統的資 料:使用自第二企業接收的標記讀取資料來維護虛擬世界 8 1310919 中的虛擬代表物,該虛擬代表物包含一代表每一個第二多 次項目的代表物,每個虛擬代表物代表其對應項目的狀 態,其中自任一企業接收的代表一特定項目的標記讀取資 料係用於更新對應至該項目的虛擬代表物:並由更新的虛 擬代表物以及虛擬世界產生可使用的資訊給第一及第二企 業。 一般來說,本發明之特色為用於在一附著於一項目的可 寫入標記上更新資訊之系統、方法以及為了執行本發明方 法之各種態樣所安裝的元件。依據本態樣的一種方法,其 係可執行下列動作:在系統内替一第一項目接收第一特性 (attribute)資訊的動作,其中該第一特性資訊取自於附著在 第一項目的一第一標記中自動讀取的資料,該第一特性資 訊包含一第一識別記號以識別第一項目;在系統内替一第 二項目接收第二特性資訊,其中該第二特性資訊取自於附 著在第二項目的一第·二標記中自動讀取的資料,該第二特 性資訊包含一第二識別記號以識別第二項目;在系統内接 收取自於從位於第二項目的一感應器自動讀取的資料;在 系統内接收關係資訊指出第一項目與第二項目間的關係; 在系統内維護分別代表第一及第二項目的一第一及一第二 虛擬項目,該物件維護分別代表第一特性資訊、第二特性 資訊以及感應器資訊的資訊,並在系統内維護代表第一及 第二項目間關係的一虛擬狀況,自實體及虛擬狀況中的資 訊辨識一警示狀況,該警示狀況與第一項目有關:因應警 9 1310919 示 9 處 中 時 過 擬 任 程 在 料 位 記 至 位. 世 反 ,維 狀 預 .狀 .情 示狀況產生更新的特性資訊以寫入第一項目;辨認出警 狀況後,於系統内偵測第一標記於一標記寫入處的存在 並在偵測到標記存在於標記寫入處時使標記寫入處於該 寫入更新的資訊至標記中。 有利的實施可具有一個以上的下列特色。在虛擬世界 有關項目以及狀況的資訊會被對應至虛擬全球標準化的 間維度、三維空間以及唯一標識(identity),其中可以透 空間以及時間相互追蹤項目和狀況。本方法也產生一虛 世界的警示給一使用者一旦決定一偵測到的互動會影響 何一個多數項目,其中該使用者為一自然人或是一電腦 式。本方法也維護虛擬世界中每個項目及每個狀況的現 位置的表示,該每個表示反映最近接收到的標記讀取資 以及情境資訊。本方法也藉由緯度、經度、高度來表示 置及狀況。本方法也維護項目位置及狀況位置的歷史 錄。本方法也基於項目位置的歷史紀錄自虛擬世界導出 少一個項目未來位置的預測。本方法也同樣地基於狀況 置的歷史紀錄導出未來位置的預測。本方法也維護虛擬 界中的每個項目及狀況之現在狀態的表示,該每個表示 映最近接收到的標記讀取資料以及情境資訊。本方法也 護項目狀態及狀況狀態的歷史記錄。本方法也基於項目 態的歷史紀錄自虛擬世界導出至少一個項目未來狀態的 測。本方法也同樣地基於狀況狀態的歷史紀錄導出未來 態的預測。本方法也將時間戳記與每個標記讀取資料與 10 1310919 境資訊的實體結合,每個時間戳記同步至一種單一標準。 不可標記的狀況包含一種與天氣有關的狀況:而該與天氣 有關的狀況的位.置至少由一緯度、經度、高度來描述。該 不可標記的狀況包含一交通事故,而該交通事故的位置至 少由一緯度、經度、高度來描述。本方法也接收一個或多 個階層體系(hierarchy)資訊的實體,每次描述表示於虛擬 世界中的項目彼此之間的一種階層體系;並利用接收到的 階層體系資訊以維護虛擬世界中每個表示階層體系之一的 虛擬狀況。在某些特定項目包含於其他項目内,至少一個 階層體系為項目間的關係。本方法也接收位.於一第一項目 的感應器的感應器資訊:並替第一項目更新威應器資訊至 第一虛擬項目。本方法也自外在系統接收情境資訊的實 體。本方法也接收情境資訊的實體,其中該實體包含取自 位於一特定位置的感應器的遙測資料。本方法也接收由位 於一特定點或區域的感應器所產生的遙測資料並表示位於 此特定點或區域的狀況;並在虛擬世界偵測到一項目在該 點或區域之上或之内會被由遙測資料所表示的狀況所影響 時,產生一警示予使用者,當被表示於虚擬世界時,其中 使用者為一自然人或電腦程式。本方法也接收由位於一特 定點或區域的溫度感應器所產生的溫度資料並表示虛擬世 界中的虛擬狀況内該點或區域的現在溫度.並在虛擬世界 偵測到一項目會被位於該點或區域之上或之内的現在溫度 所影響時產生一警示予使用者,當該項目及現在溫度被表 11 1310919 不於虛擬世界中時 本方法也將一溫度 被滿足時引發一動 者’其中該使用者 規則附加至一虛擬 或依據虛擬世界中 則附加至一虛擬狀 依據虛擬世界中現 理並回應關於一項 現在或過去被表示 並回應關於一項目 特殊項目有特殊關 界中時。 一般來說,本潑 產品’以提供多數 著於項目的標記被 位置資訊由至少译 訊,並將其提供給 率識別標言己各具 電子產品編碼)作 (visibility)可透過. 定項目與商業文件 的裝運文件,自項 其中使用者為一自然人或電腦程式。 異常附加至一虛擬項目;並於温度異常 作發生。該動作包括產生一警示予使用 為一自然人或電腦程式。本方法也將一 貢目中 可操作該規則以觸發警示事件 現在的資訊引發動作。本方法也將—規 況中,可操作該規則以觸發警示事件或 在的資訊引發動作。本方法也接收、處 目於現在或過去之狀態的詢問當該項目 於虛擬世界中時。本方法也接收、處理 狀態的詢問’該項目在現在或過去與一 係當該項目現在或過去被表示於虛擬世 ‘明之特色為方法及設備,包括電腦程式 企業存取一供應鏈中的項目之資訊。附 讀取以及自標記讀取的資訊以及標記的 ί個企業提供並用於維護項目的配置資 供應鏈中的企業。該標記可為無線電頻 有一 ePC(electronic product code, 為唯一識別記號。配置資訊的可見度 授;權來加以控制。可見的資訊可包含特 間如訂單及裝運文件的關係。藉由可見 目標記讀取的資訊可用於確認裝運的身 12 份 次 標 唯 附 收 記 替 取 的 識 當 標 取 維 fe 鏈 可 法 取 次 號 1310919 及完整性·。依照本發明的系統包含自一第一企業接收' 標記讀取資料的的方法,每次包括自附著於一項目的 籤讀取的資訊,該讀取的資訊包含一自動從標記讀取 一標記識別記號,每次也包含一對應標記的位置以及 著項目當標記識別記號自標記讀出時,該自第一企業 的多次標記讀取資料全體係包含自附著於多數項目的 中讀取的資訊;使用自第一企業接收的標記讀取資料 項目維護配置資訊:自一第二企業接收多次第二標記 資料的的方法,每次包括自附著於一項目的一標記讀 資訊,該讀取的資訊包含一自動從標記讀取的唯一標 別記號,每次也包含一對應標記的位置以及其附著項 標記識別記號自標記讀出時,該自第二企業接收的多 記讀取資料的全體地包含自附著於多數項目的標記中 的資訊;使用自第二企業接收的標記讀取資料以對項 護配置資訊,其中對於一特定項目而自任一企業接收 記讀取資料用於更新配置資訊;以及使配置資訊讓供 中的多數企業包括第一企業及第二企業看見。 本發明系統有利的實施可包含額外的特色。本發明系 包含用於自一第三企業接收第三多次標記讀取資料的 ,每次包括自附著於一項目的一標記讀取的資訊,該 的資訊包含一自動從標記讀取的唯一標記識別記號, 也包含一對應標記的位置以及其附著項目當標記識別 自標記讀出時,該自第三企業接收的多次標記讀取資 多 的 其 接 標 以 讀 取 記 目 次 讀 η 的 應 統 方 讀 每 記 料 13 1310919 全體地包含自附著於多數項目的標記中讀取的 自第三企業接收的標記讀取資料以對項目維護 其中對於一特定項目而自任一企業接收的標記 於更新配置資訊。可實施本發明系統以便附著 的標記包含無線電頻率識別(r a d i 〇 identification,RFID)標記,每個 RFID 標記攜帶 編碼(ePC)作為唯一標記識別記號。可實施本發 可見度為受控制的可見度:且本發明系統更包 資訊的方法,其指出配置資訊應讓供應鏈内一 夠看見的程度;以及只有在授權資訊允許配置 下讓特定企業看見的方法。可實施本發明系統 訊包含多個項目特性,且關於至少其中之一的 授權資訊指出企業可看見的項目特性。可實施 以使多數企業包含一來源企業以及一目的企業 業關於一訂單具有由目的企業所開出的一訂單 目的企業所開出關於一實體裝運準備履行訂單 裝運文件:可見度包含標記讀取資料以及包括 裝運文件的商業文件間的關係的可見度;以及 時項目酉己置可見度更包含接收包括下列之裝 法:有關對應於裝運中貨物之項目的標記識別 裝運文件將每個標記識別記號與一裝運編號 訊:以及有關訂單文件將該裝運編號與一訂單 的資訊:使標記讀取資料與該裝運資訊相結合 資訊:使用 配置資訊, 讀取資料用 於多數項目 frequency 一電子產品 明系統使得 含接收授權 特定企業能 資訊的狀況 以使配置資 項目特性, 本發明系統 ,該來源企 文件以及由 之貨物的一 訂單文件及 提供企業即 運資訊的方 記號;有關 相結合的資 編號相結合 的方法;以 14 1310919 及使目的企業可以獲取該結合的方法以使該目的企業對於 裝運中的一項目可利用一標記識別記號以確認裝運。 一般來說,本發明之特色為可在一追蹤項目之分散式系 統節點間聯繫的方法及設備,包括電腦程式產品。本發明 系統包含一節點階層體系於一第一企業,該節點階層體系 包括一個或多個上層(patent)節點以及一個或多個區域 (1 ocal)節點,每一個區域節點是一上層節點的子孫:以及 一節點階層體系於一第二企業,該節點階層體系包括一個 或多個上層節點以及一個或多個區域節點,每一個區域節 點是一上層節點的子孫。在系統中,每個節點在多個項目 與回應的節點間維護一映像(mapping)。該映像對每個項目 指出,對於該項目至少一個節點為指定的回應節點,而對 於至少兩個項目有不同的指定回應節點。可操作每個節點 以接收項目讀取資料的多個實體,每次包含自附著於一項 目的一標記中讀取的資訊,該讀取的資訊包含一自動從標 記中讀取的唯一數位識別記號,每次也包含對應標記及其 附著項目的位置,當標記識別記號自標記讀取時,該多個 標記讀取資料全體係包含自附著於多個項目的多個標記中 讀取的資訊;以及每次對於標記之讀取資料。可操作每個 節點使標記讀取資料與指定的回應節點聯繫,該回應節點 是由節點維護的映像所指定。 本發明系統有利的實施可包含額外的特徵。可實施本發 明系統使建立於一第一節點的映像與建立於一第二節點的 15 1310919 映像不同。可實施 項目自一節點與指 節點接收有關該項 新關於項目的位置 目彼此間可具有一 造者或項目的產品 一般來說,本發明 配置資訊的方法及 包含一監視系統, 的系統,以及一個 以4貞測一個或多個 標記識別記號,一 佈事件至一個或多 目的系統以訂閱關 個或多個事件路由 接收到的事件以對 操作每個事件路由 事件,並送出事件 一般來說,本發 及較高階應用程式 式產品。可操作依 理設備接收一套規 部應用程式:自一 本發明糸統因而在標 定的回應節點聯繫後 目的額外資訊並反應 資訊。關於接收標記 階層關係。該標記識 級別。 之特色為可在一個分 設備,包括電腦程式 一個或多個用戶,包 或多個事件路由器。 標記項目,產生一事 讀取識別記號,以及 個事件路由器。可操 於一個或多個標記項 器接收該事件,且在 一個或多個標記項目 器以維護一用戶名單 至用戶。 明之特色為用於在感 間傳遞資料之方法及 照本發明的一電腦程 則,該規則指出何種 個或多個標記讀取器 記t買取貢料為了該 ,該節點自指定的 接收的額外資訊更 讀取資料的多個項 別記號可指定一製 散系統中聯繫項目 產品。本發明系統 含一追蹤標記項目 可操作該監視系統 件,該事件包含一 一時間戳記,並發 作用於追縱標記項 目的事件,並自一 接受事件時,使用 更新配置資訊。可 ,自監視系統接收 應器或致動器裝置 設備,包括電腦程 式產品以使資料處 資料要配置到一外 接收包括項目識別 16 1310919 E , 置 識 或 識 附 該 項 應 設 格 及 多 用 子 別 會 設 記號的項目資料,每個項目識別記號自附著於一實體項 的數位標記中讀取,該項目識別記號唯一地識別該項目 自其他感應器裝置接收附加的項目資料,該其他感應裝 為標記讀取器以外的裝置,該附加項目資料包含一項目 別記號旁附加的實體項目特性,該附加項目資料與一個 多個由標記讀取器識別的項目有關:使用該規則,項目 別記號,以及附加項目資料以決定哪個項目識別記號及 加項目資料的子集合要配置於外部應用程式;且配置於 外部應用程式資料僅由接收到的項目識別記號以及附加 目資料的子集合組成。可進一步操作該電腦程式自外部 用程式接收資料,該資料包含用於控制一致動器裝置的 定資料;轉換該設定資料為一種相容於致動器裝置的 式;並配置該已轉換的設定資料至檔案致動器裝置。 一般來說,本發明之特色為用於聯繫追蹤資訊的方法 設備。本發明方法包括接收多個識別碼,每個資訊碼唯 地識別一結合的虛擬項目:將多個識別碼整理為一個或 個識別碼集合,在識別碼集合中辨識出與每個識別碼通 的多餘編碼部分;建立一文件包含一個或多個識別碼的 集合;並將文件組織為一階層體系結構因而對於每個識 碼的子集合,該多餘的部分會被一次列出且每個辨識碼 列出略去的多餘部分。 一般來說,本發明之特色為用於過濾追蹤資訊的方法及 備。本方法包括擷取多個與多個虛擬項目結合的辨識碼 17 1310919 該虛擬項目包括項目以及項目的容器,每個識別碼為一 字元唯一地辨識該結合虛擬項目;在每個識別碼内放置 字元指出該結合物件為一項目或一容器;並基於放置的 元決定每個識別碼對應於一項目或容器。 一般來說,本發明之特色為用於聯繫關於項目追蹤資 的方法及設備。本方法包括建立追蹤資訊以收集項目, 追蹤資訊代表每個項目為一個或多個特性及選擇的對 值:藉由使用與其對應的明顯編碼方案編碼追蹤資訊中 個明顯的特性可編碼追蹤資訊;送出該編碼過的追蹤資 至一接收者;決定何種特性該接收者可被授權存取;且 供該接收者一邊碼方案的集合,該集合僅包括關於使用 被授權存取的特性。的編碼方案。 可實施本發明以暸解一個或多個以下的優點。一種依 本發明的系統可意識到一虛擬而不限制數量的項目如同 實世界中的其他事物以及在項目以及其他事物之間的 係。可以一大範圍的尺度實施本發明系統。本發明系統 結構很容易與之配合且可以同時配置各式各樣的應用 式。該結構支援追蹤許多各類事物如一項目或影響一項 的一狀況。同樣地,該結構允許各種特性與一追蹤項目 狀況相結合。可劃分階層式以及其他關係於追蹤事物之 並用來追蹤關係内的事物。該結構開放給任何種類的資 來源,包括所有種類的感應器及掃描器,以及提供狀況 訊的系統例如天氣、交通狀況、運輸計晝如航空及鐵路 串 字 訊 該 應 每 訊 提 者 昭 真 關 的 程 g 或 間 料 資 計 18 1310919 擬 知 系 S 理 及 在 規 整 現 標 施 資 測 統 型 管 晝、到達曰期時間等等。本發明系統於真實世界及一虛 世界間提供一種通用的且聰明的結合可用來提供情境感 與即時追縱的項目。 本發明系統本身整合情境感知智慧。該智慧使本發明 統能夠知道何種地理空間的事件會影響哪個追蹤中的項 且回應這些事件採取行動。本發明系統可利用通用的地 空間能力提供動態的情境感知智慧。基於可用的資料以 遙測數據,本發明系統可瞭解何處、如何以及何種項目 一特定的時間與彼此具有關係且更進一步地依據定義的 則採取行動。 利用非專屬的開放介面可將現有的軟體及硬體系統 合至本發明系統。利用這些介面,本發明系統可相客於 有系統而不需利用外掛程式來升級現有系統。舉例來說 本發明系統可提供非專屬的開放介面以虛擬地整合各種 記、標記讀取器、掃描器、感應器以及應用程式。可實 本發明系統以包含可通用地自項目標記讀取資料並寫入 料至其内的應用程式。本發明系統可包含通用的即時遙 數據追蹤。本發明系統可整合現有的地理資訊系 (Geographical Information Systems,GIS)以及資料。 本發明系統支援一種全範圍遍及各產業之新型或增強 應用程式的開發。此類應用程式包含但不限於與供應鏈 理、資產追蹤與管理、安全與存取控制、運輸、費用徵拍 銷售點以及行李管理有關的那些程式。 19 1310919 本發明系統從一地區到一全梂_麻* J王球階層均可利用。意即可訾 施本發明系統 *接一贪 ^ 既以支援商業早位、一單獨公司或—群公 5 個或多個產業中。本發明系統可即時追蹤項目及 狀=本發明系統可提供項目或群线在及過去的狀 可遠端進行,舉例來說, " 热線通訊或透過一網路如她 際網路。 網 透過種種的創始,未來大量的久彳馆a 記且可全球㈣Μ,* 式項目可個別的加上榡 $辦識’在_多實例中#用自 欲w 貝”甲使用自動知作感應器。太 發明糸統可橫跨產業及公司間操作以提供聰明的企業層: 項目追蹤解決方案。本發明系統提供開放的、冑 可調整的商業方法而可應用遍及於多個產業及應用程式及 本商業方法允許客戶通用地定義及引入項目的虛擬 至網路上的軟體系統,附加基於動態情境資料發出動 的規則,以及詢問本發明系統許多有關的資作 u 取自本發 明糸統取得追蹤物件現在及過去的情境。追機的資料基於 攔位層級(field —丨eve〗)授權定義可在伙伴間分享。 透過非專屬介面,即瀏覽器或自我描述文件如又馗以可1310919 IX. DESCRIPTION OF THE INVENTION: TECHNICAL FIELD OF THE INVENTION The present invention generally relates to tracking physical items. [Prior Art] Typical systems used to track physical projects typically include computer devices and software. Such systems maintain information that indicates conditions, such as where the object is being tracked today. Imagine this as a virtual world. In traditional systems, there is often a gap between the actual situation of an objective and the conditions indicated by the system. Gap is often caused by incorrect manual data entry and system limitations. The result of this type of problem is that, for the fact, traditional systems reflect distorted and fragmented images. In addition, most traditional systems can only observe a limited range and resolution. For example, the system can only distinguish the type and quantity of products and cannot distinguish individual items. SUMMARY OF THE INVENTION This specification describes methods and apparatus, including computer program products for context aware and instant tracking projects. The term "item" is used in this specification to refer to a real, physical object to avoid the use of the word "object (〇bj ect)", which is used hereinafter to refer to only one type of material. Processing structure (construct). In general, the present invention features systems, methods, and components that can be used to track items in various ways. A system in accordance with the present invention comprises a marking element comprising 6 1310919 information indicating a standard for marking one or more items, each marking comprising a globally unique identification symbol: a containing and marking The object interface component of the communication device, and further comprising means for receiving context information: a context-aware wisdom includes logic for processing context information and logic for indicating system actions in response to context information; and a communication intermediary software for Communication between components of the system and communication with devices external to the system. In general, the present invention features systems, methods, and components that can be used to implement context-aware and instant-tracking items. According to one aspect of this aspect, an action of receiving multiple instances of tag read data (tag_read_data) can be performed, each time containing information read from a tag attached to an item. The read information includes a unique digital identification mark automatically read from the mark, and each time the unique identification mark is read, the status information is also included, including a corresponding mark position and an attached item. The plurality of tag reading data includes information read from tags attached to the plurality of items; receiving one or more context information, each describing a related unmarkable physical condition (physical cirumstances), the context information Pointing out a state including a location of the condition, the plurality of contextual information as a whole includes information describing a plurality of conditions: using the received tag to read data and context information to maintain virtual items and virtual conditions in a virtual world The virtual item includes an item that can be used for each of the plurality of items, and the virtual condition includes each of the plurality of conditions A person object, each object represents the state of its corresponding item or situation; and detecting interaction occurs between virtual virtual situation with representatives of the status of the project on behalf of the world community in the virtual 71,310,919 project. In general, the present invention features components, methods, and elements that enable information to be obtained between businesses and that can be implemented in various aspects of the method of the present invention. According to this aspect, a method for receiving a plurality of tags to read data from a first enterprise can be performed, and each time a message is automatically read from a tag attached to an item, the information read is Include at least one unique digit identification mark, each time reading the unique identification mark also includes status information, including a corresponding mark position and an attached item thereof, the multiple mark read received from the first enterprise The data collection system includes information read from a mark attached to the first plurality of items; the mark read data includes data derived from the first data processing system of the first enterprise: use received from the first enterprise Marking the read data to maintain virtual representations in the virtual world, the virtual representations comprising representatives representing each of the plurality of items, each virtual representation representing the state of its corresponding item: The second enterprise receives the second mark reading data multiple times, each time automatically including a mark attached to an item and containing at least one unique digit identification mark. The information obtained, each time also contains status information, including the location of the corresponding mark and the item to which it is attached, and the plurality of mark reading data received from the second enterprise entirely includes self-attachment to at least one of the first plurality of items The information read in the tag, the tag read data received from the second enterprise contains data from a second data processing system of the second enterprise: using the tag read data received from the second enterprise to maintain the virtual world A virtual representation in 8 1310919, the virtual representation comprising a representation of each of the second plurality of items, each virtual representation representing the status of its corresponding item, wherein the token received from any enterprise representing a particular item The reading data is used to update the virtual representation corresponding to the item: and the available virtual information is generated by the updated virtual representation and the virtual world to the first and second businesses. In general, the present invention features a system, method for updating information attached to a writable indicia, and components installed to perform various aspects of the method of the present invention. According to one aspect of the present aspect, the action may be performed to receive a first attribute information in a system for a first item, wherein the first characteristic information is taken from a first item attached to the first item. An information automatically read in a mark, the first characteristic information includes a first identification mark to identify the first item; and the second item is received in the system by the second item, wherein the second characteristic information is taken from the attached The data automatically read in a second mark of the second item, the second characteristic information includes a second identification mark to identify the second item; and the receiving in the system is taken from a sensor located in the second item Automatically reading the data; receiving the relationship information in the system to indicate the relationship between the first item and the second item; maintaining a first and a second virtual item representing the first and second items respectively in the system, the object maintenance Representing information of the first characteristic information, the second characteristic information, and the sensor information, respectively, and maintaining a virtual condition representing the relationship between the first and second items in the system, And the information in the virtual situation identifies a warning condition, and the warning status is related to the first item: in response to the police, 9 1310919 shows that the time of the 9th place is in the position of the material in the place. The world is reversed, the shape is pre-formed. The status information generates updated characteristic information to be written into the first item; after the alarm condition is recognized, the presence of the first mark at a mark write location is detected in the system and the mark is made when the mark is detected at the mark write position Write the information in the write update to the tag. An advantageous implementation may have more than one of the following features. In the virtual world, information about projects and conditions is mapped to inter-dimensional, three-dimensional, and unique identities of virtual global standardization, where projects and conditions can be tracked through space and time. The method also produces a virtual world alert to a user who determines whether a detected interaction affects a majority of the project, wherein the user is a natural person or a computer. The method also maintains a representation of each item in the virtual world and the current location of each condition, each representation reflecting the most recently received token readings and contextual information. The method also expresses the condition by latitude, longitude and altitude. This method also maintains a history of project locations and status locations. The method also derives a prediction of the future location of one project from the virtual world based on the historical record of the project location. The method also derives a prediction of future locations based on the historical record of the status. The method also maintains a representation of the current state of each item and condition in the virtual world, each of which represents the most recently received tag read data and context information. This method also protects the history of project status and status status. The method also derives a measure of the future state of at least one item from the virtual world based on the historical record of the project state. The method also derives predictions of future states based on historical records of status conditions. The method also combines a timestamp with each tag reading data with an entity of 10 1310919 context information, each timestamp being synchronized to a single standard. The unmarkable condition includes a weather-related condition: the position of the weather-related condition is described by at least one latitude, longitude, and altitude. The unmarkable condition includes a traffic accident, and the location of the traffic accident is described by at least one latitude, longitude, and altitude. The method also receives one or more hierarchy information entities, each time describing a hierarchy of items represented in the virtual world; and utilizing the received hierarchy information to maintain each of the virtual worlds A virtual condition that represents one of the hierarchical systems. In some specific projects included in other projects, at least one hierarchy is a relationship between projects. The method also receives the sensor information of the sensor of the first item: and updates the device information to the first virtual item for the first item. The method also receives the entity of the context information from the external system. The method also receives an entity of the contextual information, wherein the entity includes telemetry data taken from a sensor located at a particular location. The method also receives telemetry data generated by sensors located at a particular point or region and indicates conditions at the particular point or region; and detects in the virtual world that an item is above or within the point or region When it is affected by the condition indicated by the telemetry data, a warning is generated to the user, and when it is displayed in the virtual world, the user is a natural person or a computer program. The method also receives temperature data generated by a temperature sensor located at a particular point or region and represents the current temperature of the point or region within the virtual condition in the virtual world. and detecting that an item is located in the virtual world A warning is generated to the user when the current temperature is above or within the point or region. When the item and the current temperature are not in the virtual world, the method will also trigger a move when the temperature is satisfied. Wherein the user rule is attached to a virtual or virtual virtual world attached to a virtual form according to the virtual world and responds to a current or past representation and responds to a special item in a project having a special boundary. In general, this product is provided with a majority of the mark on the item by the location information from at least the translation, and provides it to the rate identification mark. Each has its own electronic product code. The shipping document of the commercial document, the user of which is a natural person or a computer program. An exception is attached to a virtual item; and an abnormality occurs at the temperature. The action includes generating a warning for use as a natural person or computer program. This method will also operate the rule in a tribute to trigger an alert event. The current message triggers the action. This method will also—in the case, the rule can be manipulated to trigger an alert event or an action to trigger an action. The method also receives an inquiry about the current or past state when the item is in the virtual world. The method also receives and processes status queries. The project is now or in the past with a series of projects. The project is now or in the past is represented in the virtual world as a method and device, including computer program companies accessing items in a supply chain. Information. Attached and read-to-mark information and the enterprises in the provisioning supply chain that the company provides and uses to maintain the project. The tag can have an ePC (electronic product code) for the radio frequency. It is controlled by the visibility of the configuration information. The visible information can include the relationship between the special order, such as the order and the shipping document. The information obtained can be used to confirm that the 12 subscripts of the shipment are only attached to the receipt of the identification. The feline chain can be taken as the number 1310919 and the integrity. The system according to the invention includes receiving from a first enterprise. The method of marking the read data, each time including information that is self-attached to a destination tag, the read information includes an automatic reading of a tag identification mark from the tag, each time including a corresponding tag position and When the mark identification mark is read from the mark, the whole system of the multiple mark read data from the first enterprise contains information read from the most items attached; the data is read using the mark received from the first company. Project maintenance configuration information: a method of receiving a plurality of second marked materials from a second enterprise, each time including a self-attachment to a target Reading the information, the read information includes a unique identification mark automatically read from the mark, and the position of the corresponding mark is included each time and the attached mark identification mark is read from the mark, and the received from the second enterprise The entire record of the multi-recorded data contains information from the mark attached to most items; the information is read from the mark received from the second enterprise to configure information for the item, wherein the book is received from any enterprise for a specific item The data is used to update the configuration information; and the configuration information is made available to most enterprises in the supply including the first enterprise and the second enterprise. Advantageous implementations of the system of the present invention may include additional features. The present invention includes The enterprise receives the third plurality of tags to read the data, each time including information that is self-attached to a tag for reading, the information includes a unique tag identification tag that is automatically read from the tag, and also includes a corresponding tag. Position and its attachment item, when the mark is recognized from the mark readout, the multiple mark received from the third enterprise reads the lot of the mark to Reading the reading of the secondary reading η The reading of each receipt 13 1310919 contains the marking reading data received from the third enterprise read from the marking attached to most items to maintain the project for a specific project. The tag received from any enterprise updates the configuration information. The system that can implement the system of the present invention for attachment includes radio frequency identification (RFID) tags, each RFID tag carrying code (ePC) as a unique tag identification token. The visibility of the present invention is controlled visibility: and the system of the present invention is more information-intensive, indicating the degree to which the configuration information should be visible within the supply chain; and the method of allowing a particular enterprise to see only if the authorization information allows configuration. The system in which the present invention can be implemented contains a plurality of project characteristics, and authorization information regarding at least one of them indicates the project characteristics that the enterprise can see. Can be implemented so that most companies include a source company and a destination enterprise for an order with an order from the destination company to issue an order for a physical shipment to prepare to fulfill the order shipment file: visibility includes mark reading data and The visibility of the relationship between the business documents including the shipping documents; the inclusion of the visibility of the items in the project; the inclusion of the following includes the following: the identification of the shipment document corresponding to the item in the shipment, the identification document and each shipment identification mark with a shipment Numbering message: and the relevant order documents to compare the shipping number with an order: to combine the tag reading data with the shipping information: use configuration information, read data for most items frequency, electronic product system, including receiving Authorizing a specific enterprise to be able to inform the status of the information, the system of the present invention, the source enterprise document and an order document of the goods and the party symbol for providing the enterprise shipment information; the method for combining the combined capital numbers With 14 1310919 and making Companies can obtain the combination of methods to make the enterprises for the purpose of shipping an item can be used to confirm a shipping tag identification mark. In general, the present invention features a method and apparatus for communicating between distributed system nodes of a tracking project, including computer program products. The system of the present invention comprises a node hierarchy system in a first enterprise, the node hierarchy comprising one or more upper nodes and one or more ocal nodes, each of which is a descendant of an upper node And a node hierarchy in a second enterprise, the node hierarchy includes one or more upper nodes and one or more regional nodes, each of which is a descendant of an upper node. In the system, each node maintains a mapping between multiple projects and the responding nodes. The image indicates for each project that at least one node for the project is a designated response node and that there are different designated response nodes for at least two items. Each entity can be operated to receive a plurality of entities for reading data from the project, each time containing information read from a tag attached to a destination, the read information including a unique digit identification automatically read from the tag The mark, each time also contains the position of the corresponding mark and its attached item. When the mark identification mark is read from the mark, the plurality of mark read data system includes information read from a plurality of marks attached to the plurality of items. ; and each time the data is read for the tag. Each node can be operated to associate tag read data with a designated response node that is specified by the image maintained by the node. Advantageous implementations of the system of the present invention may include additional features. The system of the present invention can be implemented such that the image established at a first node is different from the image of a 15 1310919 created at a second node. The implementable project receives, from a node and a finger node, a product relating to the location of the new item, which may have a manufacturer or project, generally, a method for configuring information of the present invention, and a system including a monitoring system, and One to identify one or more tag identification tokens, one cloth event to one or more destination systems to subscribe to events received by one or more events to route events for each event, and to send out events. This and higher-end application products. The operative device receives a set of application applications: from the invention, the additional information is communicated to the calibrated response node and the information is reflected. About receiving tags Hierarchy. This tag identifies the level. Features are available in one sub-device, including computer programs, one or more users, packages or multiple event routers. Mark the project, generate something to read the identification token, and an event router. The event can be received by one or more tagged items and in one or more tagged items to maintain a list of users to the user. The feature is a method for transferring data between the senses and a computer program according to the present invention, the rule indicating which one or more mark readers are to buy the tribute for the purpose, the node receives the specified Additional information and multiple item identifiers for reading data can be used to specify a contact product in a system. The system of the present invention includes a tracking mark item operable to monitor the system component, the event including a time stamp, concurrently acting to track the event of the marked item, and updating the configuration information from the time the event is accepted. The self-monitoring system receives the device or the actuator device, including the computer program product, so that the data of the data office is configured to be received, including the project identification 16 1310919 E, and the identification or identification of the device and the multi-user The item data of the mark is not set, and each item identification mark is read from the digital mark attached to an entity item, and the item identification mark uniquely identifies that the item receives additional item data from other sensor devices, and the other sense device For devices other than the tag reader, the additional project material includes a physical item attribute attached to an item identifier, the additional item data being associated with a plurality of items identified by the tag reader: using the rule, the item is marked And the additional project data to determine which project identification mark and the sub-set of the project data are to be configured in the external application; and the external application data is only composed of the received project identification mark and a subset of the additional target data. The computer program can be further operated to receive data from an external program, the data including the fixed data for controlling the actuator device; converting the setting data to a type compatible with the actuator device; and configuring the converted setting Data to the file actuator unit. In general, the present invention features a method for contacting tracking information. The method of the invention comprises receiving a plurality of identification codes, each information code uniquely identifying a combined virtual item: arranging the plurality of identification codes into one or more identification code sets, and identifying each identification code in the identification code set a redundant encoding portion; creating a file containing a collection of one or more identification codes; and organizing the files into a hierarchical architecture so that for each subset of the identification, the redundant portions are listed once and each identified The code lists the excess that is omitted. In general, the present invention features a method and apparatus for filtering tracking information. The method includes extracting a plurality of identification codes 17 1310919 combined with a plurality of virtual items, the virtual item includes a project and a container of the item, each identification code is a character uniquely identifying the combined virtual item; within each identification code The placement character indicates that the combined object is an item or a container; and each identification code corresponds to an item or container based on the placed element. In general, the present invention features a method and apparatus for contacting a project tracking asset. The method includes establishing tracking information to collect items, and tracking information represents each item as one or more characteristics and selected pair values: the tracking information can be encoded by using an obvious encoding feature of the corresponding encoding scheme to encode the tracking information; Sending the encoded tracking resource to a recipient; deciding which feature the recipient can be authorized to access; and providing the recipient with a set of side code schemes that include only features regarding the use of authorized access. The coding scheme. The present invention may be implemented to understand one or more of the following advantages. A system in accordance with the present invention can be aware of a virtual, non-limiting number of items as other things in the real world and between projects and other things. The system of the invention can be implemented on a wide range of scales. The system structure of the present invention is easily compatible with it and can be configured with a wide variety of applications at the same time. The structure supports tracking a wide variety of things such as a project or a situation that affects an item. As such, the structure allows for a variety of features to be combined with a tracking project condition. It can be divided into hierarchies and other things that are related to tracking things and used to track things within relationships. The structure is open to any kind of source, including all types of sensors and scanners, as well as systems that provide status information such as weather, traffic conditions, transportation, such as air and rail links. The process of the g or the inter-materials 18 1310919 is to be known as the system and the standardization of the current measurement, the time of arrival, and so on. The system of the present invention provides a versatile and intelligent combination between the real world and the virtual world to provide contextual and immediate tracking. The system of the present invention integrates context-aware wisdom. This intelligence enables the present invention to know which geospatial events affect which of the items in the tracking and respond to those events to take action. The system of the present invention can provide dynamic context aware intelligence using common ground capabilities. Based on the available data in telemetry data, the system of the present invention can understand where, how, and what projects are related to each other at a particular time and act further based on definitions. Existing software and hardware systems can be incorporated into the system of the present invention using a non-proprietary open interface. Using these interfaces, the system of the present invention can be used as a system to upgrade existing systems without the need for plug-ins. For example, the system of the present invention can provide a non-proprietary open interface to virtually integrate various tags, tag readers, scanners, sensors, and applications. The system of the present invention can include an application that can read data from a project mark and write it into it. The system of the present invention can include universal instant telemetry. The system of the present invention integrates existing geographic information systems (GIS) and data. The system of the present invention supports the development of a new or enhanced application that spans a wide range of industries. Such applications include, but are not limited to, those related to supply chaining, asset tracking and management, security and access control, transportation, expense auction points, and baggage management. 19 1310919 The system of the present invention can be utilized from a region to a full 梂_麻*J king ball class. It means that the system of the invention can be used to support commercial early positions, a single company or a group of five or more industries. The system of the present invention can track items and conditions in real time. The system of the present invention can provide projects or group lines in the past and in the past, for example, " hotline communication or through a network such as her network. Through various kinds of creations, the future will be a large number of long-term museums and can be global (4), *-type projects can be individually added to 榡$ 识 ' ' in _ multi-instance # 用自欲 w 贝" A use automatic knowledge induction The invention system can operate across industries and companies to provide a smart enterprise layer: project tracking solution. The system of the present invention provides an open, scalable business method that can be applied across multiple industries and applications. And the business method allows the customer to generically define and introduce the virtual-to-network software system of the project, attach rules based on dynamic contextual data, and query the system of the present invention for a number of related assets. The current and past situation of the object. The information of the chase is based on the level of the block (field-丨eve). The authorization definition can be shared among the partners. Through the non-proprietary interface, ie the browser or self-describing file can be

延伸性標不語言)文件,本發明系統可供使用 D 及外部應 用程式存取。如果有任何的單獨標記項目及 升通踯數據資 料’本發明系統可透過時間及空間大量地加以 疋峨。本發 明系統提供開放的非專屬介面給感應器、裝 且M及追蹤與 提供其位置的服務,及/或出自其的遙測數據資料,項目哎 其情境至本發明系統。本發明系統也提供開怎 μ非專屬介 20 1310919 面給感應器、裝置以及寫入資料至實體項目的服務或可接 收此資料的其標記。本發明系統提供使用者介面、應用程 式介面以及定義個別的標記項目之虛擬代表以及其階層: 系的工具,包括特定的特性及方法;卩定義基於系统、 的動態情境資料可以引發行動的規則;以定義實體拘:: 其他可影響項目之作用的虛擬代表定義精密的資料存 取過渡器収值在代表項目&其他真實世界事物的資料: 件的-特性層級上;以替大量有關於或導源於追蹤項目之 現在及過去的情境特性詢問系統:並加以顯示;且在網路 上的伙伴之間分享與項目有關的資料。 本發明系,统可供多種實體為其各自的目的❿使用,且 每次可製作關於其標記項目、其資料輸人裝置以及可由其 他使用本發明系統的實體看見的追《況mm㈣= 資訊。該其他實體可使用此資訊並由本發明系統使用者整 體社群的經驗及歷〇獲得好處,不論其目的起初是要收The extended non-language file, the system of the present invention is available for access by D and external applications. If there are any separate marked items and the data is upgraded, the system of the present invention can be largely manipulated in time and space. The system of the present invention provides an open, non-proprietary interface to the sensor, the M and the service that tracks and provides its location, and/or telemetry data from it, the project to its context. The system of the present invention also provides for the service of the sensor, device, and data to the physical item or the marking of the data that can be received by the non-exclusive device. The system of the present invention provides a user interface, an application interface, and a virtual representation of the individual tagged items and their hierarchy: the tools of the system, including specific features and methods; and the definition of rules based on the system, the dynamic contextual data can trigger actions; To define entities:: Other virtual representations that affect the role of the project define sophisticated data access transitions that are included in the data representing the project & other real-world things: the level of the feature - the level of the feature; Guided by the current and past contextual characteristics of the tracking project: and displayed; and share project-related information between partners on the network. The present invention is available to a variety of entities for their respective purposes, and can be tailored each time with respect to its tagged item, its data input device, and the chase that can be seen by other entities using the system of the present invention. This other entity may use this information and benefit from the experience and experience of the entire community of users of the system of the present invention, regardless of its purpose.

集或提供何種資訊,B 貝讯且在各方面不需要未來的使用於及各 種貢獻的好處,或县甘士』, 次疋其有利的互動,於做出貢獻時加以考 量。 本發明系統使裝 車時的人為疏失能夠 中貨物實際配置的最 歷史記錄歸檀以支持 運過程中如準備裝運期間或裝載至貨 早期發現。本發明系統提供一供應鍵 大可見度。本發明系統永久地將所有 可靠度、被保證人、客戶回流、偷竊 證明以及其他商業過程 本發明系統整合現有系統以避免 21 1310919 功能的重複。本發明系統受,4於用於追 予最多的自動功能,I 目的標記 刀踎,舉例來說,藉由以 運基礎使能夠建立清置 ^ 目標處檢 思立巧早。本發明系統可 作。軟體升級可以在π # # 乂無時無刻持 行該資料可儲存於_通用結構中,即使=况下動態 變’該通用結構亦不會改變。在故障的事:广意結 復機制使系統能夠报快的恢復。 "’低延 可縮放本發明& μ , + ^月糸統以支援大量的使 變的機制可脫離扃咨者。用來使資 離在資料上提出詢問的機制琿你 限於過去的資料肤能 乍。可使 負荷過重。 玲因為太多的詢 當每個被追縱+ 、在系統中地理上分散的筋戟n 時,為保證其位署麻r 的即點間 置及配置有一最新同步的觀察,太發 統僅需要一低階的咨ϋ w 4 ’、 的資料聯繫於節點之間。 一 點至系統的其餘邱八 使在一地 餘部分間的通訊無法操作時, 允許在該地區節赴t a a 不發月糸 .未連線的/ 續的商業運作。本發明系統保 、郎點已重新連線,自未連線節 資料已確實地與条& t 收果的未 收到的改變也已二分取得聯繫且自其他節 由只報告也與未連線節點取得聯繫。此外 ' 3的階層體專中高階^ 及項目歷史紀錚储卢目的移動,聯繫 缔储存成本均可降低。 本發明系统可少 『在不需要消耗許多處理能 與過濾的狀況下A 此力以執仃 自大量的智慧項目中即時接收資料。 而歟 測裴 續操 地執 構改 遲恢 料改 詢問 問而 移動 明系 區節 統仍 證一 報告 點接 ,藉 量以 收集 該智 22 1310919 慧項目不需侷限於一垔 Α. τ ^ 士 早一的工廄或商店。本潑 許多地理散佈的地區收焦 收集貧科。本發明系統不 可能的智慧項目種類支接一牲^ 叉援特疋硬體介面。本 輕易地擴張以容納新的聯繫通 瓦迫从及硬體介面 使本發明系統能適應新的設定以Λ & a久局面而不需 程師重新安排操作》 可使用本發明系統以具備適合的即時存貨 管理。捨棄接收匯總的存貨改變的定期報告, 使存貨改變能即時報告且不需要 ° 卜而罟人的介入。捨 (replenishment planning)只依據 _ 固定呀 晝的時間選擇可為適時調整的, ° ^ 攸稞報告的即 以較多或較少的頻率產生。 本發明系統能遮蔽一 UID的 少爾邵分以節 連線_中的頻寬。本發明系統可接此— 又—組自不同 中讀取的UIDs且能夠決定何種 搜項目由一特定 別。藉由此決定’本發明系統 . 過濾掉附屬;^ 類的UIDs並提供一過濾掉的w居 ' 町附屬於某些 集合給一接收者。 目: 本發明系統可提供有選擇Μ &上 / 千f生的存取以 系統能提供可送出同樣的追次 鞭: . 貝訊給所有皆ζ 但依據客戶的授權層級同時 戶 仏不同層紐 別地,本發明系統可將追縱 、'的資 ^舞訊編碼 客戶將該追蹤資訊的部分解 〜僅提 ’的方法 明系統可自 需要為所有 發明系統可 。商業規則 要一軟體工 (inventory) 本發明系統 棄補貨計晝 生,補貨計 時存貨量而 省記憶體或 種類的項目 约UID所識 某些項目種 ft類之UIDs f訊。本發明 的方便性, 訊存取。特 供一特定的 23 1310919 該編碼系統不僅可提供存取的控制且可提供有效的資 訊聯繫。本發明系統可取代追蹤資訊中描述性的文字為比 較短的編碼文字。如果該追蹤資訊儲存於一標記上,此能 讓更多的資訊儲存於標記上。如果該追蹤資訊越過網路傳 遞,此能夠減低該資訊所消耗的頻寬數量。 本發明一個或多個具體實施例的細節會在伴隨的圖示 以及以下的描述中提出。本發明其他的特色及好處會從描 述、圖示以及申請專利範圍中變得顯而易見。 【實施方式】 目錄 1. 系統概述 2. 本發明系統之其中一種實施 2.1跨企業裝運方案 2.2雙向資料流動 3 .本發明系統之另一種實施 3.1軟體升級 3.2跨企業可見度 3.3資料在全球模型間聯繫及協調 3.4 項目方案 3.5資訊取回方案 4.資料於項目追蹤系統及標記讀取器間傳遞 4.1事件路由器 24 1310919 4.2整合引擎 5 .將追蹤資訊壓縮、過濾及編碼 1.系統概述 接 書 用 業 鏈 、 含 系 記 匯 之 型 許 的 一種與本發明一致的系統在一非專屬的開放格式中 收與項目有關的資訊以及影響項目的狀況。在此說明 中,「項目(item)」一詞具有一非常廣泛的意義。其包含 於上述參考專利應用申「項目」一詞的意義。為了與企 資源規劃(enterprise resource planning,ERP)、供應 管理(supply chain management’ SCM)以及物流系統相容 一項目的概念包含當一項目出現在一物料清單、提貨單 裝箱單、選單等等時所有正常必備的事物。因此,其包 任何可具有一位置、被裝運、被賣給客戶等等的實體物科 其亦可包含任何可能在一公司會計或如裝運之其他商業 統中被提及的資產。 一標記項目為一種攜帶一自我識別標記的項目。該標 可與一單一項目(在之前的意義中)相連結或可與一項目 總相連結。因此舉例來說,一標記項目可以足下列其中 一:一單獨項目如一瓶肥皂、一資產如一標記過的筆記 電腦、一容器含有可能各式各樣項目的集合或是一容納 多箱子的貨盤等等、一容器、一卡車或拖車、一飛機、 船以及一火車。 在客戶貨物及其他領域,一項目可以不具有任何一捆 25 1310919 特定項目標記。舉例來說,一標記的箱子可包含4 8瓶肥 皂、其中每瓶均有一相同的UPC(全球產品編碼)或SKU(庫 存管理單位)或其他產品編號的條碼且每平均可單獨賣給 客戶。一追蹤系統可將在標記階層被追蹤的裝運結合至追 蹤單獨標價項目之銷售收入點。條碼一般將不會攜帶一 UID(唯一系統識別記號),僅為一項目種類或 SKU。本發 明系統可製造一些假設將條碼與標記資料相結合。在超級 市場或零售商之標記的裝箱階層存貨可藉由使用一標記讀 取器於曰常的存貨清單中受益,本發明系統假設其内容已 被放置在零售架上而可於任意的訂單中賣出。如果個別的 項目未被辨識,便無法在標記的箱子被打開後具備追蹤系 統的正確性.。 大體上,一標記為一 RFID(無線電頻率識別)標記,但 其並不需要以射頻技術為基礎。舉例來說,可實施一標記 以由光、磁、光磁或其他科技讀取,不論標記與讀取間 是否具有實體接觸。此外,該標記可為被動的(未含有内部 電源以聯繫及傳遞資料)或主動的;且其可具備或不具備運 算能力。在此說明書中,應了解一標記為為一可識別的數 位標記,意味該標記具有利用某些讀取器可直接自該標記 讀出一唯一數位標識的性質。某些數位識別標記也可被寫 入,假使在不依賴一聯繫網路的情形下需要準備好資訊 時,這些標記提供額外的優點。 在此說明書中,「虛擬項1 (virtual item)」一詞用於表 26 1310919 示與項目相符且用於作為其代表的資料。同樣地,「虛擬 況(virtual circumstance)」一詞將會用於表示與實體的 非實體的事物相符且用於作為其代表的資料,包含例如 係及事件。可實施一虛擬項目或一虛擬狀況如同物件於 件感知程式術語中的意義;然而,其亦可以任何其他方 的方式實施,如藉由一資料庫中的紀錄。 大體上,建立及維護虛擬狀況是因為其表示某些事物 一般可稱之為狀況一其可能會影響由一虛擬項目表示的 目。狀況的其中一個例子為地理空間事件,其可包含如 妨礙一運輸船攜帶追蹤中的項目的裝運之颶風、會妨礙 目自運輸船上卸下的勞工攻擊、以及會延遲項目裝運的 通事故。 階層體系一詞係指項目與狀況之間的結合或關係。舉 來說,將一容器置於一裝有容器的貨盤中,影響貨盤的 件也會影響容器。虚擬狀況可表示階層體系。 本發明系統自許多來源接收資訊,該資訊能藉由一網 如網際網路或是直接地連接至系統。可調整本發明系統 用專屬的或非公開的介面自來源接收資訊,於上述惰況 換該資訊的格式以與系統相容。本發明系統包含資料輸 裝置,如標記讀取器、感應器以及掃描器。藉由這些裝i 本發明系統可持續地追蹤並記錄物品的狀態及由實體與 境物件所表示的狀況。一物品的狀態可包含其狀況、特 以及位置。 狀 及 關 物 便 項 會 項 交 例 事 路 利 轉 入 J 情 性 27 1310919 2.系統之一實施 如第 1圖所示,與本發明一致的一項目追蹤系統(item tracking System ’ ITS)可與一標記元件(Tagging component, “ TC” )102、一 物件介面元件(ObjectWhat kind of information is collected or provided? B Beixen does not need future benefits in various aspects and benefits of various contributions, or county Gansu, and its beneficial interactions are considered when making contributions. The system of the present invention enables the most historical record of the actual configuration of the cargo during the loading of the vehicle to support the shipment during the shipment process, such as during shipment or early arrival. The system of the present invention provides a supply key with great visibility. The system of the present invention permanently integrates all reliability, guarantor, customer reflow, theft certificate, and other commercial processes into the existing system to avoid duplication of the functionality of 21 1310919. The system of the present invention is subject to the use of the most automatic functions, and the purpose of the flag is to mark the blade. For example, it is possible to establish a clearing by the basis of the operation. The system of the present invention is operative. The software upgrade can be stored in the _general structure at π # # 乂, and the general structure will not change even if it is dynamically changed. In the event of failure: the extensive recovery mechanism enables the system to report recovery quickly. "' Low Deviation The present invention & μ, + ^ 糸 system to support a large number of enabling mechanisms can be removed from the consultant. The mechanism used to enable the resource to ask questions on the information is limited to the data of the past. Can make the load too heavy. Ling because of too many inquiries, when each is chased +, geographically dispersed in the system, in order to ensure that the location of the location and the configuration of the latest synchronization observation, too only Need a low-level consultation w 4 ', the data is linked between the nodes. One point to the rest of the system, when Qiu Ba, the communication between the rest of the system is inoperable, allows the festival to go to the local area without a monthly connection. Unconnected/continued business operations. The system of the present invention has been re-wired, and the unconnected data has been reliably contacted with the unreceived changes received by the article & t and has not been reported from other sections. The line node gets in touch. In addition, the '3' level of the middle-level high-level ^ and the project's historical records can be reduced, and the cost of contact storage can be reduced. The system of the present invention can "receive data immediately from a large number of smart projects without having to consume a lot of processing power and filtering." In the meantime, the construction of the Ming Dynasty is still a certificate, and the report is collected. The borrowing to collect the wisdom 22 1310919 Hui project does not need to be limited to one. τ ^ 士早一Work or shop. This splashed many geographically dispersed areas to collect the poor. The type of intelligent project that is not possible in the system of the present invention is a support for the hardware interface. The present invention is easily expanded to accommodate new connections and hard-wired interfaces to enable the system of the present invention to adapt to new settings to achieve a long-term situation without requiring the operator to reschedule operations. Instant inventory management. Discarding periodic reports that receive aggregated inventory changes, allowing inventory changes to be reported immediately and without the need for intervention. Replenishment planning can only be adjusted according to the time of _ fixed , ,, ° ^ 攸稞 report is generated with more or less frequent. The system of the present invention is capable of masking the bandwidth of a UID of the UAR to the bandwidth in the splicing line. The system of the present invention can then - in addition - group UIDs read from different sources and can determine which search items are specified by a particular one. By this decision, the system of the present invention filters out the UIDs of the subordinates; and provides a filtered w' to be attached to a certain set to a recipient. The system of the present invention can provide access to select & / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / In New Zealand, the system of the present invention can be used to trace the part of the tracking information to the tracking software, and the system can be used for all the invention systems. Business rules To be an inventory The system of the invention is to abandon the replenishment, replenish the inventory, and save the memory or type of items. About UID. Some items are UIDs of the ft class. The convenience of the present invention, access. Specially available for a specific 23 1310919 The coding system not only provides access control but also provides effective communication links. The system of the present invention can replace the descriptive text in the tracking information as a shorter encoded text. If the tracking information is stored on a tag, this allows more information to be stored on the tag. If the tracking information is transmitted over the network, this can reduce the amount of bandwidth consumed by the information. Details of one or more specific embodiments of the invention are set forth in the accompanying drawings and the description below. Other features and advantages of the present invention will become apparent from the description and drawings. [Embodiment] Table of Contents 1. System Overview 2. One of the implementations of the system of the invention 2.1 Cross-enterprise shipping scheme 2.2 Two-way data flow 3. Another implementation of the system of the invention 3.1 Software upgrade 3.2 Cross-enterprise visibility 3.3 Data contact between global models And coordination 3.4 Project plan 3.5 information retrieval plan 4. Data transfer between project tracking system and tag reader 4.1 Event router 24 1310919 4.2 Integration engine 5. Tracking information compression, filtering and coding 1. System overview book picking A system consistent with the present invention, in a non-exclusive open format, receives information about the project and affects the condition of the project. In this description, the term "item" has a very broad meaning. It is included in the meaning of the term "project" in the above referenced patent application. In order to be compatible with enterprise resource planning (ERP), supply chain management (SCM) and logistics systems, the concept of a project includes the appearance of a project in a bill of materials, bill of lading packing list, menu, etc. All the things that are normal and necessary. Thus, any physical item that can have a location, be shipped, sold to a customer, etc., can also contain any assets that may be mentioned in a company accounting or other business system as shipped. A tagged item is a project that carries a self-identifying tag. The target may be linked to a single item (in the previous sense) or may be linked to a project. Thus, for example, a marking item can be one of the following: a separate item such as a bottle of soap, an asset such as a marked note computer, a container containing a collection of possible items, or a pallet containing multiple boxes. Wait, a container, a truck or trailer, an airplane, a boat, and a train. In customer goods and other areas, a project may not have any bundle of 25 1310919 specific item marks. For example, a labeled box may contain 48 bottles of soap, each of which has a bar code of the same UPC (Global Product Code) or SKU (Storage Management Unit) or other product number and can be sold separately to the customer on average. A tracking system can combine shipments tracked at the mark level to the point of sale revenue tracking individual listing items. Barcodes will generally not carry a UID (Unique System Identification Mark), just a project type or SKU. The system of the present invention can make some assumptions that combine barcodes with tagged material. Inboxed inventory at the supermarket or retailer can benefit from the use of a tag reader in a regular inventory, the system of the present invention assumes that its content has been placed on a retail shelf and can be placed on any order. Sell in. If individual items are not recognized, the correctness of the tracking system will not be available after the marked box is opened. In general, one is labeled as an RFID (Radio Frequency Identification) tag, but it does not need to be based on radio frequency technology. For example, a mark can be implemented to be read by optical, magnetic, magneto-optical or other techniques, regardless of whether there is physical contact between the mark and the read. In addition, the tag can be passive (without internal power to contact and transfer data) or active; and it may or may not have operational capabilities. In this specification, it should be understood that a mark is an identifiable digital mark, meaning that the mark has the property of being able to read a unique digital mark directly from the mark using some readers. Some digital identification tags can also be written, which provide additional advantages if information needs to be prepared without relying on a contact network. In this specification, the term "virtual item" is used in Table 26 1310919 to indicate the material that matches the item and is used as its representative. Similarly, the term "virtual circumstance" will be used to refer to a material that is consistent with an entity's non-physical things and used as a proxy for it, including, for example, systems and events. A virtual item or a virtual condition can be implemented as if it were in an object-aware program term; however, it can be implemented in any other way, such as by a record in a database. In general, virtual conditions are established and maintained because they represent something that is generally referred to as a condition that may affect the purpose represented by a virtual item. An example of a situation is a geospatial event, which may include a hurricane that would impede the shipment of a ship carrying a tracked item, a labor attack that would prevent the removal from the ship, and a delay that would delay the shipment of the item. The term hierarchy refers to the combination or relationship between the project and the situation. For example, placing a container in a pallet with containers affects the container and affects the container. A virtual condition can represent a hierarchy. The system of the present invention receives information from a number of sources that can be connected to the system via a network such as the Internet or directly. The system of the present invention can be adapted to receive information from a source using a proprietary or non-public interface, and the format of the information is changed to be compatible with the system. The system of the present invention includes data transfer devices such as tag readers, sensors, and scanners. By these means, the system of the present invention continuously tracks and records the status of the item and the condition represented by the physical and physical objects. The status of an item can include its status, characteristics, and location. The item tracking system will be transferred to J. 27 1310919 2. One of the implementations of the system As shown in Figure 1, an item tracking system (ITS) consistent with the present invention can be used. With a tagging component ("TC") 102, an object interface component (Object

Interface Component &gt; “OIC” )104、一通訊中介軟體元 件 (Communication Middleware Component , “ CMC” )106、一情境感知智慧元件(Context — Aware Intelligence Component, “CAIC” )10 8 以及一人 類介 面元件(Human Interface COmpOnen, “HIC” )110共同實施。在一替代性的實施中,該H1C 110 與其他元件結合。這些元件個個可實施為電腦程式在一個 或多個電腦上執行並控制裝置執行資料取得、輸出以及傳 輸功能。第1圖也顯示ITS之元件間,以及系統與外部應 用程式11 2、外部市場η 4以及其他外部ITS 1 1 6間的傳輸 流動(由箭頭表示)。可以任何方便、開放的方式實施該傳 輸流動,如透過XML文件的交換。 以一分散式的、即時的以及事件基礎架構來安排該元 件°可自一微小的乃至巨大的程度實施每個或所有的元件 或系統元件的任何組合。微小程度實施係指在一單一裝置 上實施而巨大尺度實施係指在多個裝置如一網路中的電腦 上實施。每個元件可分配遍及多個裝置,包括電腦,而藉 由一網路互連。每個元件可由多個不同應用程式組成,即 28 1310919 如此 能。 時, 性層 電腦 應用 可透 透過 XML 標記 弓 技術 碼以 號加 Ί 系統 發明 物件 編號 特定 規則 實施’該應用程式在匯總(aggregate)中執行元件的功 在確保硬體及軟體可使用非專屬的標準架構立即整合 上述元件結構允許系統使功能可自一區域性至一全球 級分组及縮放。 -元件可包含軟體系統,其包含任何軟體、應用程式、 軟體產品以及相關裝置。舉例來說,一軟體系統可為 程式與伺服器在一企業層級上操作。在系統間的傳輸 過傳輸網路進行。該元件揭露非專屬的開放介面給可 一網路存取的服務,如以開放標準像是HTTP上的 為基礎的服務。以下的文章會更進一步地描述元件。 元件 丨入至系統的項目會使用任何可取得的項目層級標記 ,如主動及被動無線電頻率識別(‘‘ RFID” )標記、條 及可應用於分子基礎上的標記等,並以一唯一識別記 以標記。 「系統首先察覺到一項目或狀況,其將如上所述引入至 ,且建立一對應的物件(即虛擬項目或虛擬狀況)。本 系統4曰派一特定的動態n維内容及特性空間以引入 舉例來說,本發明系統可指派所有者、價格、物品 、及恤度至一引入的物件。本發明系統可任意地附加 規則至引入的物件。舉例來說’本發明系統可附加一 才曰定右對應項目的溫度達到y層級,則使動作2發生。 29 1310919 一特定實施中的TC 1 02以一開放方式指出可與系 用何種標記技術以及如何加以使用。該T C 1 0 2包含 基於網際網路技術的分散知識系統。特別地,該 T C 通常將包含並提供全球唯一識別記號的一規格以及如 以應用;描述相容標記之規格的目錄,其讀取器/寫入 體以及有關其使用的任何態樣:應用於標記項目的特 準及法則;標準化的通訊及内容資料格式與介面的規 讀寫過程的規格,用於使標記作用之處理及傳輸要求 遙測資料規格:最佳工業習慣,即關於選擇及部屬標 標記内容的知識;測試程式;實施導引;以及常見問題。 此外,該TC 102可提供工具、内容、軟體發展套 及特定方案使製造者、系統整合者以及客戶可辨識、 及實施最佳項目標記讀取器/寫入器組合與標準的應 式。該TC 1 02可與任何軟體發展情境共同建立以滿 述提到的要求。 物件介面元件 該01C 1 04將資料自附屬的硬體轉移至系統,反 然。該OIC 1 04也可執行任何要求的局部處理。 該OIC 104是一種精密的、通用的、雙向的以及聰 軟體介面介於系統與真實世界之間。在此物件被引入 統而其狀態及遙測資料被接收、過濾、傳輸、預先處 及必要地處理。因為可實施物件以攜帶可依目前内容 統使 一植 102 何加 器硬 定標 格; 以及 記與 件以 確認 用程 足上 之亦 明的 至系 理以 或狀 30 1310919 態資料而觸發警示事件或使動作發生的規則,故可實施 OIC 1 04以嵌入或連結至一規則引擎以處理此類規則。 由自訂OIC 104,客戶可指定若其中一個客戶的標記讀 器第一次偵測到一項目標記時OIC應該做什麼一其將具 一識別標記使系統可對應至一唯一系統識別記 (“ UID ” )。這些動作可包含與外部應用程式聯繫, ERP(企業資源規劃)應用程式。 該 ΟIC 1 0 4也通用地指定並確認標記介面硬體, RFID讀取器、條碼掃描器、眾合物標記讀取器及威應器 與其作業系統如何與系統聯繫。因此該OIC 1 04作為一 繞所有特定標記讀取/寫入裝置的通用軟體包裝函式,其 供標準化的整合、資料確認、過濾以及傳輸:雙向的、基 事件之安全聯繫;及資料預處理。 因為該OIC 104不僅可接收資料尚可傳送資料至附 於系統的的硬體及軟體,且最終至其標記項目本身,故 發明系統可使用該OIC以寫入資料至此項目或遠端加以 制,如果這些項目是為此控制而設置的話。 該OIC 104可替所有的向内及向外的通訊應用與執 一精密的安全方案,如一種基於數位認證的安全方案。 OIC104可與任何軟體發展情境共同建立以滿足上述提 的要求。 通訊中介軟體元件 該 藉 取 有 號 如 如 等 圍 提 於 屬 本 控 行 該 到 31 1310919 該元件藉由傳送並接收標準化事件聯繫,這些元件可透 過一網路來傳送與接收。該CMC 106確認在OIC 104與 CAIC 1 0 8 (其將在以下說明)之間與通常介於任何系統元件 間的標準化事件並為其安排路徑。該CMC 1 06也可確認介 於任何系統元件與其他應用程式、裝置與元件間的標準化 事件並為其安排路徑。 該 C M C 1 0 6執行功能如資料及認證確認、儲存及擷 取、歸檔、資料解密/加密,以及事件的多點傳送。該C M C 1 0 6 可替所有向内與向外的通訊應用與執行一精密的安全方 案,如一種基於數位認證的安全方案。該CMC 106可與任 何軟體發展情境共同建立以滿足上述提到的要求。 情境感知智慧元件 CAIC 1 08包含邏輯,其提供智慧給系統以接收、處理 及回應關於什麼標記項目在何處如何由引入的物件所代表 以及該項目現在、過去或未來在一特定時間與彼此間或與 真實世界的功能間有關的詢問。該 CAIC 1 0 8提供開放的 内部與外部介面給外掛的附加功能如應用程式及規則,延 伸其通用的服務設定。 如前所述,本發明系統可包含虛擬狀況,其代表可能影 響項目之事件。這類事件的例子包含颶風、某點或某區域 的高温以及交通阻塞。虛擬狀況也可描述項目的特性。特 性的例手包括一地理空間路徑、一速度以及一目標。感應 32 1310919 器的遙測讀數也可引入為虛擬狀況。 該CAIC 1 08包含一資料庫,其允許系統儲存及 入物件的現在狀態和這些物件之狀態改變的歷史記 資料庫可處理地理空間資料且可散布至多個電腦及 區。 該 CAIC 108可應用與執行一精密的安全方案, 基於數位認證的安全方案。該 C AIC 1 0 8可與任何 展情境共同建立以滿足上述提到的要求。 人類介面元件 HIC 1 1 0通用地整合許多適合人類容易自系統存 控制的科技。這些科技包含像是以HTML或XML 的、語音控制的、觸控筆控制的以及包含所有種類 視覺化科技以及相似科技的多型態人類介面。該 將應用程式及基礎架構層與表示及人類互動層分 HIC 1 10可應用與執行一精密的安全方案,如一種基 認證的安全方案。該HIC 11 0可與任何軟體發展情 建立以滿足上述提到的要求。 引入物件至本發明系統 在操作中,可利用標準化及參數化的事件引入」 虛擬項目及虛擬狀況)至系統,該事件包含至少 UID。此外,可附加特定特性、方法以及規則至引 擷取引 錄。此 多個地 如一種 軟體發 取加以 為基礎 的資料 HIC110 開。該 於數位 境共同 勿件(如 一系統 入的物 33 1310919 件(如現在/m度、現在擁有者、製造者、溫度異常、警示、 規則、資料存取以及認證規格)。 唯一識別記號 本發明系統將所有引入的物件對應至一系統UID。為 了系統可以在區域性至全球性層級間縮放並且也滿意地與 其他系統整合’此識別記號須是全球唯一。如果該物件的 指不物具有一帶有一全球唯一識別記號的標記’該識別記 號可以但不一定需要作為UID。這類的唯一識別記號其中 一種為ΜIT (麻省理工學院)自動識別記號中心的電子產品 編碼(ePC)。第2Α圖說明epc的格式。 本發明系統可分割UID以增強搜尋性能。 一種唯一地將項目標記的一種方式為附加RFID晶片 在該項目上。這些電子晶片握有至少一相對的唯一辨識記 號可被特定的讀取器裝置讀取。更多精密的晶月使動態資 料儲存區搭載外部讀取/寫入的能力而智慧晶片包含内建 的處理電源。RFID技術的其中一項優點為在一距離外自動 辨識多種項目而不需將其反組譯(disassemble)或解裝 Unpack)。本發明系統還可選擇使用其他技術,如項目層 級條碼、磁性·標記以及幕合物標記等,以將虛擬項目貼上 可對應至系統UID的識別標記。 事件 34 1310919 本發明系統藉由使用事件於内部及外部相互聯繫。表1 提供一種代表此一事件之XML文件的例子。可使用代表 事件的任何便利格式。 &lt;事件&gt; 〈鍵入 &gt;發現 物件&lt;/鍵入&gt; &lt;參數&gt; &lt;發信人&gt; &lt;UID&gt;XX.XXXXXXX.XXXXXX.XXXXXXXXX&lt;/UID&gt; 〈鍵入&gt;RFID讀取器&lt;/鍵入&gt; &lt;/發信人&gt; &lt;遙測資料&gt; &lt;UID&gt;XX ; XXXXXXX.XXXXXX.XXXXXXXXy&lt;/UID&gt; &lt;溫度&gt; &lt;單位&gt;C&lt;/單位&gt; 〈數值&gt;45.43 &lt;/數值&gt; &lt;/溫度&gt; &lt;/遙測資料&gt; &lt;/參數&gt; &lt;/事件&gt; 表1 時間、空間、唯一識別、情境、階層體系 35 1310919 本發明系統對應每個引入的物件至全系統標準化的維 度,包含時間、空間(三維)、唯一識別記號(UID)以及情境。 本發明系統儲存區帶有全系統同步化時間戳記的輸入資 料。空間係指自一點(單純的位置)至一三維空間中的複雜 三維多面體的一切事物(係指例如位置、大小與一項目的形 狀)。情境可為η維的(係指例如特性像是溫度、速度以及 重量)。 每個維度足以全系統標準單位加以測量,例如基於像是 協調全球時間(Coordinated Univetsal Time,“UTC”)以及國 際單位系統(system of Units,“SI”)之國際標準。 因為時間及空間是全球維度,本發明系統的核心空間與 所有其他系統(如 GIS)相容,該其他系統亦於這些維度或 其子集合内工作。引入的物件可為動態階層體系的一部 份。階層體系可由虛擬狀況加以描述。 基於内部或外部事件資料,本發明系統追蹤並記錄項目 的狀態,該項目由上述空間中的引入物件所代表。之後更 可回答問題或提供關於引入物件於該空間内的狀態及其間 關係的警示,例如: • 項目(UID)200 1年12月12號在何處? • 所有於半徑y内在位址z處的所有X型項目(UID) 在何處? • 我的哪些供應品受到熱帶暴風雨X的影響? • 資產X最接近的剩餘部分在何處且他們多快可以送 36 1310919 達至上廠y ? • 在截止曰期y之前對於我的產X最接近的需求在 何處? • 警告!化學產品X及y彼此間存放得太近。 • 警告!員工X不被允許將筆記型電腦y攜出大樓 z。基於歷史資料、統計或其他方法,本發明系統也 可導出未來狀態或引入物件或其群組的行為。 直接的或導出的位置資料 項目的位置可用許多方法向系統描述。關於一直接描述 的一種例子為以一標準方式配置緯度、經度以及高度資料 集合。 關於一導出的位置描述之例子為一設有一標記讀取器 之設施的街道住址。本發明系統對應該標記讀取器的街道 住址至系統的標準協調系統,假設該標記讀取器遭過的項 目(由其UID表示)在其附近,並將讀取器位置與該項目的 位置相結合。 物件層及資料存取授權模型 該物件模型可包含一 UID、特性以及一事物的定義, 該事物的定義為系統使用者所讀取/寫入/改變其特性、方 法及規則的授權。本發明系統分配一全球唯一識別記號給 每個使用者,該識別記號可基於電子產品編碼(e P C )、巨 PC管理員(為ePC的一部分)等等。 依據分配的授權以及使用標準化參數化事件,系統使用 37 1310919 依 表 例 者寫入、讀取以及改變引入物件的資料。物件資料存取 賴定義的授權設定。表2提供一 XML文件的例子,其 示一實施上述授權模型的虛擬項目。然而這只是一種 子,任何方便的表示均可加以使用。 〈虛擬一項目〉 &lt;UID&gt;XX.XXXXXXX.XXXXXX ' XXXXXXXXX&lt;/UID&gt; &lt;現在,一所有者&gt; &lt;OUID&gt;XXXXXXX&lt;/OUID&gt; 〈改變一授權&gt; &lt;OUID&gt;XXXXXXx&lt;/OUID&gt; &lt;/改變 授權&gt; &lt;/現在一所有者&gt; &lt;價格&gt; 〈單位&gt;USD&lt;/單位&gt; &lt;數值&gt;230000&lt;/數值&gt; &lt;讀取 授權&gt; &lt;OUID&gt;XXxXxxx&lt;/OUID&gt; &lt;OUID&gt;yyyyyyy&lt;/OUID&gt; &lt;OUID&gt;ZZZZZZZ&lt;/OUID&gt; &lt;/讀取一授權&gt; &lt;寫入一授權&gt; &lt;OUID&gt;XXXXXXX&lt;/OUID&gt; 38 1310919 &lt; /寫入一授權&gt; 〈改變一授權&gt; &lt;OUID&gt;XXXXXXX&lt;/OUID&gt; &lt;/改變 授權&gt; &lt;/價格&gt; 〈虛擬一項目&gt; 表2 通訊安全方案 本發明系統包含一通用的授權及安全方案(如一種 數位認證與加密的方案)供元件間的通訊以及與其他 及外部裝置的通訊〇 2.1跨企業裝運方案 系統在.裝運者Y自製造者X裝運至零售商Z時 及紀錄高品質魚貨的位置與溫度,現在將會在此情況 述一種方案。 以下大致描述系統如何完成上述的功能。製造者 產品裝箱並在每個箱子上貼上RFID標記。該RFID標 含一 UID且還可以儲存一有效曰期、一最大溫度臨界 一最大遭遇溫度讀數(Tmax)。製造X將箱子放在貨盤 在每個貨盤上加上一動態的、可回收的溫度感應裝置 可選擇在每個箱子上附加該感應裝置,但會造成較 基於 系統 追蹤 中描 X將 記包 值與 上並 。也 大支 39 1310919 出。這些裝置附有一 RFID標記,其包含一 uid且可儲存 •an·度讀數與一隶大遭遇温度讀數(Tm ax)。該裝置定期地測 1現在温度並在其附加的RFID標記上儲存讀數。當溫度 達到一特定的臨界值時便觸發警示。當到達零售商時,基 於感應器裝置的溫度歷史紀錄而更新的有效曰期以及最大 遭遇溫度資料被寫入至每個箱子的RFID標記。 製造者X想要減少應由裝運者y負責而被零售商Z退 回的箱子數量(退貨)’例如在裝運過程中箱子暴露於 高溫中。裝運者Y想要藉由確保現在位·置與溫度的完全 可見度以提供更好的顧客滿意度,因而得到市場佔有率, 此外,裝運者Y想要察覺品質問題以及由承包商造成的 失竊。零售商Z想要在·送達時能夠識別並退回壞掉的產 品’因而減少退貨而降低成本並同時得到更高的顧客滿意 度。Interface Component &gt; "OIC" 104, a Communication Intermediateware Component ("CMC") 106, a Context-Aware Intelligence Component ("CAIC") 10 8 and a human interface component ( Human Interface COmpOnen, "HIC" 110 is implemented together. In an alternative implementation, the H1C 110 is combined with other components. Each of these components can be implemented as a computer program executing on one or more computers and controlling the device to perform data acquisition, output, and transmission functions. Figure 1 also shows the transmission flow between the components of the ITS, as well as the system and external applications 11 2, the external market η 4 and other external ITS 1 16 (indicated by the arrows). The transport flow can be implemented in any convenient, open manner, such as through the exchange of XML files. Arranging the component in a decentralized, immediate, and event infrastructure can implement any or all of the components or any combination of system components from a small to a large extent. A small degree of implementation refers to implementation on a single device and a large scale implementation refers to implementation on a computer in multiple devices, such as a network. Each component can be distributed across multiple devices, including computers, and interconnected by a network. Each component can be made up of several different applications, 28 1310919. At the same time, the sex layer computer application can implement the function of the execution of the component in the aggregate by using the XML tagging technology code to increase the number of the system invention object number specific rules to ensure that the hardware and software can be used non-exclusively. The standard architecture immediately integrates the above component structure to allow the system to enable functions to be grouped and scaled from a regional to a global level. - Components can include a software system that includes any software, applications, software products, and related devices. For example, a software system can operate at the enterprise level for programs and servers. The transmission between systems is carried out over the transmission network. This component exposes a non-proprietary open interface to a network-accessible service, such as an open standard like HTTP-based service. The following article will describe the components further. Items that are component-incorporated into the system use any available item-level markup, such as active and passive radio frequency identification (''RFID') tags, strips, and markers that can be applied to the numerator, etc., with a unique identification Marked. "The system first perceives an item or condition, which is introduced as described above, and creates a corresponding object (ie, virtual item or virtual condition). The system sends a specific dynamic n-dimensional content and characteristics. Spaces By way of example, the system of the present invention can assign owners, prices, items, and ratings to an incoming item. The system of the present invention can arbitrarily add rules to the imported items. For example, the system of the present invention can be attached Once the temperature of the right corresponding item reaches the y level, action 2 occurs. 29 1310919 TC 1 02 in a particular implementation indicates in an open manner which marking technique can be used and how it is used. 0 2 contains a decentralized knowledge system based on Internet technology. In particular, the TC will typically contain and provide a specification of a globally unique identification token. Such as the application; a catalog describing the specifications of the compatible mark, its reader/writer and any aspect of its use: special features and rules applied to the marked item; standardized communication and content data formats and interfaces The specification of the read and write process is used to make the processing and transmission of the tagging requirements telemetry data specifications: the best industrial habits, that is, the knowledge about the selection and the contents of the subordinate tags; the test program; the implementation guide; and the common problems. The TC 102 provides tools, content, software development kits and specific solutions that enable manufacturers, system integrators, and customers to identify and implement best project mark reader/writer combinations and standard applications. 02 can be established in conjunction with any software development scenario to fully address the requirements mentioned. Object Interface Component The 01C 1 04 transfers data from the attached hardware to the system, and the OIC 104 can perform any required local processing. The OIC 104 is a sophisticated, versatile, bidirectional, and savvy software interface between the system and the real world. State and telemetry data are received, filtered, transmitted, pre-processed, and processed as necessary. Because the object can be implemented to carry the current content, the device can be used to confirm the use of the device. The above-mentioned rules are used to trigger warning events or actions to trigger actions, or OIC 104 can be implemented to embed or link to a rule engine to handle such rules. Custom OIC 104. The customer can specify what the OIC should do if the tag reader of one of the clients first detects an item tag. It will have an identification tag so that the system can correspond to a unique system identification ("UID"). These actions can include contacting an external application, an ERP (Enterprise Resource Planning) application. The ΟIC 1 0 4 also universally identifies and confirms the tag interface hardware, how the RFID reader, bar code scanner, the universal tag reader, and the servo system communicate with the system. The OIC 104 thus acts as a generic software package for all specific tag read/write devices for standardized integration, data validation, filtering and transmission: two-way, base event security; and data preprocessing . Because the OIC 104 can not only receive data but also transfer data to the hardware and software attached to the system, and ultimately to the tagging item itself, the inventive system can use the OIC to write data to the project or to the remote end. If these items are set for this control. The OIC 104 enables a sophisticated security solution for all inbound and outbound communications applications, such as a digital authentication based security solution. The OIC 104 can be built with any software development scenario to meet the above requirements. The communication intermediary software component should be numbered as required by the local control. The device is connected to 31 1310919. The component transmits and receives standardized event contacts, which can be transmitted and received through a network. The CMC 106 acknowledges and schedules a standardized event between the OIC 104 and CAIC 1 0 8 (which will be described below) and typically between any system components. The CMC 06 can also identify and route standardized events between any system component and other applications, devices and components. The C M C 1 0 6 performs functions such as data and authentication confirmation, storage and retrieval, archiving, data decryption/encryption, and event multicasting. The C M C 1 0 6 can be used for all inbound and outbound communications applications and implements a sophisticated security solution such as a digital authentication based security solution. The CMC 106 can be built with any software development scenario to meet the requirements mentioned above. The context-aware smart component CAIC 1 08 contains logic that provides intelligence to the system to receive, process, and respond to information about where the marked items are represented by the imported objects and whether the project is present, past, or future at a particular time and with each other. Or an inquiry about the function of the real world. The CAIC 108 provides open internal and external interfaces for plug-in add-on features such as applications and rules that extend its common service settings. As previously mentioned, the inventive system can include virtual conditions that represent events that may affect the project. Examples of such events include hurricanes, high temperatures at certain points or areas, and traffic jams. Virtual conditions can also describe the characteristics of a project. The traits include a geospatial path, a speed, and a target. The telemetry reading of the sensing 32 1310919 can also be introduced as a virtual condition. The CAIC 1 08 includes a database that allows the system to store and retrieve the current state of the object and the historical database of changes in the state of the objects that can process geospatial data and can be distributed to multiple computers and zones. The CAIC 108 can be applied and implemented with a sophisticated security solution based on a digital authentication security solution. The C AIC 1 0 8 can be established in conjunction with any of the exhibition scenarios to meet the requirements mentioned above. The human interface component HIC 1 1 0 universally integrates many technologies that are suitable for human control. These technologies include multi-type human interfaces such as HTML or XML, voice-controlled, stylus-controlled, and all kinds of visual technologies and similar technologies. The application and infrastructure layer and presentation and human interaction layer HIC 1 10 can be applied and implemented a sophisticated security solution, such as a base-based security solution. The HIC 11 0 can be established with any software development to meet the above mentioned requirements. Introducing Objects to the System of the Invention In operation, standardized and parameterized events can be used to introduce "virtual projects and virtual conditions" to the system, the event containing at least a UID. In addition, specific features, methods, and rules can be attached to the reference. This plurality of locations is based on a software-based data source HIC110. The number is not common (such as a system of 33 1310919 pieces (such as current / m degrees, current owners, manufacturers, temperature anomalies, warnings, rules, data access and certification specifications). Unique identification mark the invention The system maps all incoming objects to a system UID. In order for the system to scale between regional to global levels and also satisfactorily integrate with other systems 'this identification token must be globally unique. If the object has a zone There is a globally unique identifier for the token 'The identification token may, but need not, be a UID. One such unique identification token is the Electronic Product Code (ePC) of the IT (MIT) Automatic Identification Mark Center. Illustrating the format of the epc. The system of the present invention can segment the UID to enhance search performance. One way to uniquely mark items is to attach an RFID chip to the item. The electronic wafer holds at least one relative unique identification mark that can be specified. Read by the reader device. More sophisticated crystal moons enable the dynamic data storage area to be externally read. / Write capabilities and built-in smart chip containing processing power .RFID art wherein a plurality of items automatically recognized advantages outside a distance without the need to disassemble it (the disassemble) or the unpack Unpack). The system of the present invention may also optionally use other techniques, such as project level bar codes, magnetic tags, and slate tags to affix virtual items to identification marks that correspond to system UIDs. Event 34 1310919 The system of the present invention is interconnected internally and externally by the use of events. Table 1 provides an example of an XML file representing this event. Any convenient format that represents an event can be used. &lt;Event&gt; <Type> Discover Objects&lt;/Type&gt;&lt;Parameters&gt;&lt;Sender&gt;&lt;UID&gt;XX.XXXXXXX.XXXXXX.XXXXXXXXX&lt;/UID&gt; <Type> RFID Read &lt;/type&gt;&lt;/sender&gt;&lt;telemetrydata&gt;&lt;UID&gt;XX;XXXXXXX.XXXXXX.XXXXXXXXy&lt;/UID&gt;&lt;temperature&gt;&lt;unit&gt;C&lt;/unit&gt; <Value> 45.43 &lt;/Value&gt;&lt;/Temperature&gt;&lt;/TelemetryData&gt;&lt;/Parameter&gt;&lt;/Event&gt; Table 1 Time, Space, Unique Recognition, Situation, Hierarchy 35 1310919 The system of the present invention corresponds to the dimensions of each introduced object to system-wide standardization, including time, space (three-dimensional), unique identification mark (UID), and context. The system storage area of the present invention has input data for a full system synchronization time stamp. Space refers to everything from a point (simple position) to a complex three-dimensional polyhedron in a three-dimensional space (for example, position, size, and a purpose shape). The context can be n-dimensional (for example, characteristics such as temperature, speed, and weight). Each dimension is sufficient to measure in a system-wide standard unit, for example based on international standards such as Coordinated Univetsal Time ("UTC") and the system of units ("SI"). Because time and space are global dimensions, the core space of the system of the present invention is compatible with all other systems, such as GIS, which also work within these dimensions or subsets thereof. The introduced object can be part of a dynamic hierarchy. The hierarchy can be described by virtual conditions. Based on internal or external event data, the system of the present invention tracks and records the status of the item represented by the imported objects in the space above. You can then answer questions or provide warnings about the status of the objects in the space and their relationships, such as: • Project (UID) 200 Where is December 12, 1st? • Where are all the X-type items (UIDs) at the address z within the radius y? • Which of my supplies are affected by Tropical Storm X? • Where are the closest remaining parts of Asset X and how fast can they send 36 1310919 to the factory y? • Where is the closest requirement for my production X before the deadline y? • caveat! Chemical products X and y are stored too close to each other. • caveat! Employee X is not allowed to carry the laptop y out of the building z. The system of the present invention may also derive future states or the behavior of introducing objects or groups thereof based on historical data, statistics, or other methods. Direct or exported location data The location of the project can be described to the system in a number of ways. An example of a direct description is to configure a set of latitude, longitude, and altitude data in a standard manner. An example of a derived location description is a street address of a facility with a tag reader. The system of the present invention corresponds to marking the street address of the reader to the standard coordination system of the system, assuming that the item that the tag reader has encountered (represented by its UID) is in its vicinity, and the position of the reader and the location of the item Combine. Object Layer and Data Access Authorization Model The object model can contain a UID, a property, and a definition of a transaction defined by the system user's ability to read/write/change its characteristics, methods, and rules. The system of the present invention assigns a globally unique identification token to each user, which may be based on electronic product code (e P C ), giant PC administrator (part of ePC), and the like. Based on the assigned authorization and the use of standardized parameterized events, the system uses 37 1310919 to write, read, and change the data of the imported object by the example. Object data access depends on the defined authorization settings. Table 2 provides an example of an XML file showing a virtual project implementing the above authorization model. However, this is just a sub-me, and any convenient representation can be used. <Virtual One Item> &lt;UID&gt;XX.XXXXXXX.XXXXXX 'XXXXXXXXX&lt;/UID&gt;&lt;Now, One Owner&gt;&lt;OUID&gt;XXXXXXX&lt;/OUID&gt; <Change One Authorization> &lt;OUID&gt;XXXXXXx&lt;/OUID&gt;&lt;/ChangeAuthorization&gt;&lt;/Now One Owner&gt;&lt;Price&gt;<Unit>USD&lt;/Unit&gt;&lt;Value&gt;230000&lt;/Value&gt;&lt;Read Authorization &gt;&lt;OUID&gt;XXxXxxx&lt;/OUID&gt;&lt;OUID&gt;yyyyyyy&lt;/OUID&gt;&lt;OUID&gt;ZZZZZZZ&lt;/OUID&gt;&lt;/read one authorization&gt;&lt;write one authorization&gt;&lt;OUID&gt;XXXXXXX&lt;/OUID&gt; 38 1310919 &lt; /write one authorization&gt; <change one authorization&gt;&lt;OUID&gt;XXXXXXX&lt;/OUID&gt;&lt;/changeauthorization&gt;&lt;/price&gt; <virtual one item> Table 2 Communication Security Solution The system of the present invention includes a common authorization and security scheme (such as a digital authentication and encryption scheme) for communication between components and communication with other and external devices. 2.1 Cross-enterprise shipping solution system. Y from the manufacturer X to the retailer Z and record the location and temperature of high quality fish In this case will now be described a scheme. The following outlines how the system performs the above functions. The manufacturer products are boxed and RFID tags are placed on each box. The RFID is labeled with a UID and can also store an effective cycle, a maximum temperature threshold, and a maximum encounter temperature reading (Tmax). Manufacturing X puts the box on the pallet. Add a dynamic, recyclable temperature sensing device to each pallet. You can choose to attach the sensing device to each box, but it will cause more tracking based on the system tracking. The package value is on and off. Also a large branch 39 1310919 out. These devices are provided with an RFID tag that contains an uid and can store an .an degree reading and a large encounter temperature reading (Tm ax). The device periodically measures the current temperature and stores the reading on its attached RFID tag. A warning is triggered when the temperature reaches a certain threshold. When the retailer arrives, the valid expiration date based on the temperature history of the sensor device and the maximum encounter temperature data are written to the RFID tag of each box. The manufacturer X wants to reduce the number of boxes (returns) that should be returned by the retailer Z and should be returned by the retailer Z, for example, during the shipping process, the boxes are exposed to high temperatures. Shipper Y wants to gain market share by ensuring full visibility of the current position and temperature to provide better customer satisfaction. In addition, Shipper Y wants to detect quality problems and theft caused by the contractor. Retailer Z wants to be able to identify and return broken products when delivered, thus reducing returns and reducing costs while achieving higher customer satisfaction.

以下將詳細地描述系統如何幫助每—古、去U 万建成其目標。第 3圖說明一實行’其中製造者X、裝運者 乂及零售商z 取得系統中在其各自的防火牆33x、33v、 Υ 33Z之後的物件 介面元件(〇IC)34x、34y、34Z並實行—局部 文褒。此外, 他們共同使用一外部應用程式服務提供 、可的標*己_ (TC)32、通訊中介軟體元件(CMC)36、情 、。兀件 ) w境感知智穰_ (CAIC)37以及人類介面元件(Hic)38,該外加 …几件 卜部應用程^ 務提供者透過一種如網際網路的網路提供巧服 、硯些服務。 方也可選擇訂購由一服務提供者所提供的 母— J糸統實行 T在後 40 1310919 者實例中,每一方不需要取得及安裝一 OIC。另外還有一 種選擇,一方或多方可安裝所有五種系統元件以供他們所 有人使用。在此實例中,各方無需向一服務提供者訂購, 他們的C M C ’ S可藉由在一如網際網路的網路上傳送事件 以聯繫。 基於規格、標準、最佳工業實施以及其他自T C得到的 資訊,製造X取得與上述產品及方案需求(如主動或被動 RFID標記、頻率、讀取器範圍、内建溫度感應器、記憶體 大小、價格點、實例原料以及結合需求)相客的讀一寫RFID 標記及詢問器。基於規格、標準、最佳上業實施以及其他 自TC得到的資訊,裝運者Y及零售商2各取得一些與製 造者X的RFID標記及系統相容的RFID詢問器(其可為唯 讀的)。 當製造者 X製造一箱箱的產品,製造者 X貼上一 RFID標記並引入其唯一識別記號、允許的溫度範圍以及初 始有效日期至一系統。第4圖說明此引入橾作。製造一箱 子並貼上一標記(第20步驟)。與OIC相連並屬於製造者的 標記讀取器感應到標記並讀取其UID(第21步驟)。該〇IC 產生並傳送一包含UID的看見事件至CMC(第22步驟), 該CMC安排路徑至CAIC(第23步驟)。如果一關於UID 的物件被知道,該CAIO依據輸入資料(第24步驟“ yes” 的分支;第2 8步驟)更新該物件的狀態及狀態歷史記錄; 否則該 CAIC決定該事件是否為一新的虛擬項目事件(第 41 1310919 25決定步驟)。如果該事件是一新的物件事件,該 CAIC 依據特定資料(第 2 6步驟)產生一新的虛擬項目作為UID 並儲存新的虛擬項目資料(第2 7步驟)。否則以下的動作會 發生。該CAIC傳送一未知物件事件作為UID至CMC(第 46步驟)。該CMC為此事件安排路徑至製造者的生產系統 (第45步驟),其產生一引入虛擬項目事件作為UID,其具 有特性、存取權利、規則以及警示,並傳送此事件至 CMC(第44步驟)。該CMC為此事件安排路徑至該OIC(第 43步驟),其產生一新的虛擬項目事件作為UID並傳送至 該CMC (第42步驟)。該OIC也決定是否具有一請求以寫 入該資料至該標記(第4 1步驟)。如果有的話,該ΟIC寫 入該資料至該標記(第40步驟)。在此說明中,該資料為一 種有效日期、一種溫度臨界值以及一種最大遭遇溫度讀數 (第40步驟)。在任何情況中,該新的虛擬項目事件是由該 CMC安排路徑豆該CAIC(第23步驟)以依照上述操縱。 如第5圖所示,當製造者X載入一貨盤以供運輸,製 造者X附加一動態溫度感應器至該貨盤上,重置感應器 的記憶體並啟動它(第5 0步驟)。該感應器在一時刻表時測 量溫度(第5 2步驟),伴隨時間戳記儲存測量的溫度至該標 記上的一歷史記錄(第5 4步驟)。如果該溫度達到遭過的最 大值,這個新的最大值也會儲存在標記上(第56步驟)。 第6圖描述本發明系統對載入箱子與至具有一感應器 的貨盤上所做的回應(第6 0步驟)。與OIC相連並屬於該 42 1310919 製造者的標記讀取器感應該標記及其UIDs並產生看見事 件作為UID並傳送至該CMC(第64步驟)。該CMC為這些 事件安排路徑至該CAIC(第66步驟)。依據事件中的輸入 資料’該CAIC更新由感應UIDs所識別的虛擬項目的狀 心及狀態歷史6己錄(第6 8步驟)。當屬於裝運者γ並與〇ic 相連的讀取器感應到一標記時,該CAIC更新本發明系 統。第7圖說明此更新操作。屬於該輸送者並與〇IC相連 的標記讀取器感應到貨盤上包含感應標記之箱子的標記, 讀取其UIDs與Tmax資料(第7〇步驟),該〇IC產生並傳 送看見事件與該資料至該CMC(第71步驟)。該cmc為該 事件安排路徑至該CAIC(第72步驟)。該CAIC依據接收 到的資料更新對應的虛擬項目的狀態及歷史記錄(第73步 驟)。該C AIC決定Tmax是否在限制範圍内(第74步驟)。 如果不足的話’該CAIC傳送一警示事件至該CMC(第74 步驟之no的分支;第75步驟),且該CMC為警示安排 路徑至製造者以及裝運㈣耐應用程 &lt;(第76步驟)。 當收到裝運時,零隹命,&amp; , 令售商2自附加的rfID標記及有效日 期讀取並確認該產品沾_ 的確切最大溫度資料。第9圖也說明 此讀取操作。 N工』谓锻的銘2 一 M散 子時’其被識別且C A1C利用 το件警告倉庫管理 , 。為達此目的可利用SMS(短訊 訊息 '啤叫器与!自+ n 11 U 5疋任何其他訊息傳遞的便利形 8圖也說明此警示操作^The following will describe in detail how the system helps each of the ancient and the U. Figure 3 illustrates an implementation in which the manufacturer X, the shipper, and the retailer z obtain the object interface elements (〇IC) 34x, 34y, 34Z in the system after their respective firewalls 33x, 33v, Υ 33Z and implement - Partial literature. In addition, they jointly use an external application service to provide, can be _ (TC) 32, communication media software component (CMC) 36, love. ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) . The party may also choose to order the mother-supplied system provided by a service provider. In the latter example, the party does not need to acquire and install an OIC. There is also an option to install all five system components for one or more of them for use by all of them. In this example, the parties do not need to subscribe to a service provider, and their C M C ' S can be contacted by transmitting events on a network such as the Internet. Based on specifications, standards, best industrial implementation, and other information obtained from TC, manufacturing X meets the above product and program requirements (such as active or passive RFID tags, frequency, reader range, built-in temperature sensor, memory size) , price points, example materials and combined needs) read and write RFID tags and interrogators. Based on specifications, standards, best practices, and other information obtained from the TC, Shipper Y and Retailer 2 each obtain RFID interrogators that are compatible with Manufacturer X's RFID tags and systems (which may be read-only) ). When the manufacturer X manufactures a box of products, the manufacturer X attaches an RFID tag and introduces its unique identification mark, allowed temperature range, and initial effective date to a system. Figure 4 illustrates this introduction. Make a box and attach a mark (step 20). A tag reader connected to the OIC and belonging to the manufacturer senses the tag and reads its UID (step 21). The 〇IC generates and transmits a see event containing the UID to the CMC (step 22), which schedules the path to the CAIC (step 23). If an object related to the UID is known, the CAIO updates the status and status history of the object based on the input data (the 24th step "yes" branch; step 2 8); otherwise the CAIC determines whether the event is a new one. Virtual project event (step 41 1310919 25 decision step). If the event is a new object event, the CAIC generates a new virtual item as a UID based on the specific data (step 26) and stores the new virtual item data (step 27). Otherwise the following actions will occur. The CAIC transmits an unknown object event as a UID to CMC (step 46). The CMC schedules the event to the manufacturer's production system (step 45), which generates an incoming virtual project event as a UID with characteristics, access rights, rules, and alerts, and transmits the event to the CMC (44th) step). The CMC schedules a path to the OIC for this event (step 43), which generates a new virtual project event as a UID and transmits it to the CMC (step 42). The OIC also determines if there is a request to write the data to the tag (step 41). If so, the ΟIC writes the data to the tag (step 40). In this description, the data is an effective date, a temperature threshold, and a maximum encounter temperature reading (step 40). In any case, the new virtual project event is routed by the CMC to the CAIC (step 23) to follow the above manipulation. As shown in Figure 5, when the manufacturer X loads a pallet for shipping, the manufacturer X attaches a dynamic temperature sensor to the pallet, resets the sensor's memory and activates it (step 50). ). The sensor measures the temperature at a time of day (step 52), with the time stamp storing the measured temperature to a history on the mark (step 5). If the temperature reaches the maximum value that has been exceeded, this new maximum value is also stored on the tag (step 56). Figure 6 depicts the response of the system of the present invention to loading a box and onto a pallet having a sensor (step 60). A tag reader connected to the OIC and belonging to the manufacturer of the 42 1310919 senses the tag and its UIDs and generates a see event as a UID and transmits it to the CMC (step 64). The CMC routes the events to the CAIC (step 66). Based on the input data in the event, the CAIC updates the status and status history of the virtual item identified by the inductive UIDs (step 68). The CAIC updates the system of the present invention when a reader belonging to the shipper γ and connected to 〇ic senses a mark. Figure 7 illustrates this update operation. A tag reader belonging to the transporter and connected to the 〇IC senses the tag of the box containing the sensing tag on the pallet, reads its UIDs and Tmax data (step 7), and the 〇IC generates and transmits the see event and This information is sent to the CMC (step 71). The cmc routes the event to the CAIC (step 72). The CAIC updates the status and history of the corresponding virtual item based on the received data (step 73). The C AIC determines whether Tmax is within the limits (step 74). If not enough, the CAIC transmits a warning event to the CMC (the branch of step 74; step 75), and the CMC schedules the route to the manufacturer and the shipment (4) the application is resistant (step 76) . When the shipment is received, Zero Life, &amp;, causes the dealer 2 to read and confirm the exact maximum temperature data of the product from the attached rfID mark and valid date. Figure 9 also illustrates this read operation. N workers are said to be forged 2 when a M scatterer is identified and C A1C uses το pieces to warn the warehouse management. For this purpose, you can use SMS (short message "beer and!" from + n 11 U 5 疋 any other message to convey the convenience of the figure 8 also illustrates this warning operation ^

’其中屬於零售商且與OIC 43 1310919 標記讀取器感應並讀取貨盤上箱子的標記之ulDs包含— 感應器標記帶有一 uID,並感應及讀取_最大溫度Tm”及'The ulDs that belong to the retailer and are tagged with the OIC 43 1310919 tag reader to sense and read the box on the pallet contain - the sensor tag has a uID and senses and reads _max temperature Tm and

—溫度歷史T hisi〇ry (第8 〇步驟)。該〇Ic產生並傳送看 見事件與UID、Tmax、及T hisi〇ry資訊至該CMC(步驟 8〇)。該CMC為該事件安排路徑直CAIC(步驟82&gt;該Caic 依據該輸入資料更新虛擬項目的狀態及歷史記錄(步驟 83)。該CAIC也基於丁max及T hisi〇ry資訊及製造者規則 為每個箱子計算出一新的有效曰期(步驟84) 如果CAIC- Temperature history T hisi〇ry (Step 8). The 〇Ic generates and transmits a view event and UID, Tmax, and T hisi〇ry information to the CMC (step 8〇). The CMC arranges a path straight CAIC for the event (step 82). The Caic updates the status and history of the virtual item based on the input data (step 83). The CAIC is also based on Ding Max and T hisi〇ry information and manufacturer rules for each Boxes calculate a new valid period (step 84) if CAIC

yes”的分支),該CAIC 決定該箱子是損壞的(步驟85之 傳送-警示事件與UID&amp; TmajCMC(步驟86),其為警 不安排路徑至HIC(步驟8 7)。該HIC隨後傳送〆SMS訊 息警告該零售庫存管理員(步驟&quot;)。不論該箱子是否損 壞’該〇IC決定是否有要求將該資料窝入該標記(步驟8 9) ’而如果有的話,的· 以CAIC產生並傳送寫入資料事件伴 隨著UID及關於禅印^^次^The branch of yes", the CAIC determines that the box is damaged (transfer-alert event of step 85 and UID& TmajCMC (step 86), which does not arrange the path to HIC (step 87). The HIC is subsequently transmitted 〆 The SMS message warns the retail inventory manager (step &quot;). Regardless of whether the box is damaged or not, the IC determines whether there is a requirement to insert the information into the mark (step 8 9) 'and if any, with CAIC Generate and transfer write data events accompanied by UID and about Zen printing ^^ times ^

己的資料至該CMC(步驟9〇)。該CMC 為這些事件安排路徑至 其寫入 “直到某時The information is sent to the CMC (step 9〇). The CMC arranges a path for these events to write to it "until some time

Qlc(步驟 91), 、 — v代穴可莰叹傦境資訊,例如3Qlc (step 91), - v generation of acupoints can sigh the dilemma, such as 3

通或天氣資訊。大體卜T 疋讓提供者送出資訊就是使系、# 吸入資訊以將資訊攜至系 ’、、’ 有者此類資訊可讓本發明資 統報告或預測裝運遲廷或 次其他可影響引入項目的移動或沐 況的其他情況。第9圖嗜 χ 說月此實行以及提供者供給資訊_! 系統内。在·此圖解中, 丄 —父通資訊提供者產生一弓丨入虛# 44 1310919 狀況事件與一 UID及特性·並傳送該事件至該 CMC(步驟 12 0),其為該事件安排路徑至一 OIC(步驟 122)。接收的 OIC產生一新的虛擬狀況事件與 UID至該 CMC(步驟 124),其為該事件安排路徑至CAIC(步驟 126)。該CAIC 決定該事件為新的虛擬狀況事件的型態(步驟 128之“yes” 的分支),並依據該特定的資料產生一新的虛擬項目作為 UID(步驟130),並儲存該新的虛擬狀況資料(步驟132)。 2.2雙向資料流動 本發明系統可提供在標記上的資料流動以及雙向資料 流動。第1 〇圖說明一種方案。一標記15 2被貼至一箱子 150上。該標記包含一 UID,且可儲存一有效日期、一最 大溫度臨界植、一最大遭遇溫度讀數以及一價格。在標記 1 5 2上的溫度資料可隨著測量箱子1 5 0的溫度頻率而更 新,例如在一可寫入其讀數至標記1 5 2的溫度測量站或可 操作一溫度感應器連接至標記1 5 2。 標記1 5 2上的資料可由標記讀取器1 5 8自動讀取,例如 使用RFID技術。在一具韹實施例中,標記讀取器1 5 8在· 一特定範圍内定期地“掃瞄”其情境。在另外一種具體實 施例中,觸發標記讀取器以掃瞄其情境,例如藉由一鄰近 (proximity)感應器。如果一掃瞄回報有效的讀取資料(透過 通訊 1 5 4 ),例如因標記1 5 2被移入掃瞄範圍中,標記讀取 器1 58將傳送收到的資料至系統1 66(透過通訊1 62)。在此 例中,假設本發明系統1 6 6維護一事前由一外部應用程式 45 1310919 1 74引入的虛y I74也定羲並丨 則170為“如 單氏45度高 上”。可用任 定義規則1 7〇 料’其將執行^ 系統1 6 6將會 的有效曰期及 訊1 6 4 ),並使 記1 5 2上的有 第11圖說 詢問系統1 6 6 遇溫度的最新 則1 7 1,為外; 送一事件至系 的有效日期、 觸發系統1 6 6 一標記寫入器 標記寫入器將. 域。先前提到 如網際網路的; 在這些方赛 乾項目168(透過通訊172)而該外部應用程式 忖加一規則170至虛擬項目16 8。可定義規 果健存在其標記上之箱子的最大遭遇溫度比 ,則寫入現在日期作為有效日期至其標記 何與系統166相容的格式、語法或電腦編碼 。每當系統1 6 5接收白標記丨5 2讀取的新資 乾則1 70。如果規則丨70回報一確定的結果, 計算一新的有效曰期如現在曰期,並傳送新 標記152的UID至標記寫入器16〇(透過通 標s己寫入器1 6 0寫入新的有效日期資料至標 效曰期資料領域(透過通訊156)。 明另一方案,其中外部應用程式174定期地 關於儲存於標記152上的箱子15〇之最大遭 狀態。在此方案中,可再次定義該邏輯為規 平應用程式的部A。該外部應用程式174傳 統166,該事件包含標記152的um、一新 更新的彳貝格以及更新的控制資訊。此事件 以傳送該接收的有效日期、價格以及UID至 160(透過通訊164)。本發明系統166隨後使 隹收的資料寫入至標記152上對應的資料領 的通訊可透過任何通訊媒介實施,包括在一 _路上。 :中,具備一標記讀取器可讀取儲存在標記 46 1310919 1 5 2上的資料,箱子1 5 0的一接收器將可辨識一有 及價格,該有效日期及價格乃是以追蹤過程中箱子 露於的溫度為基礎。 第1 2圖說明資料流動過程的其中一種態樣。在 的例子中,本發明系統藉由讀取一位於第一項目的 記接收關於第一項目包括其UID的特性資訊(步驟 相似地,本發明系統接收關於一第二項目的資訊以 於資料的情境資訊,其中該資料是從與第二項目相 應器所自動讀取的(步驟1 204)。本發明系統使用此 護一虛擬第一與第二項目(步驟1206)。本發明系統 指出項目間關係的關係資訊並維護一虛擬關係(步 8)。具有此資訊,本發明系統可基於至少部分的虚 辨識與該第一項目有關的一警示狀況(步驟1210)。 應該警示狀況,本發明系統產生更新的特性資訊以 至該第一項目(步驟1 2 1 2)。本發明系統之後在一標 處偵測該第一標記的存在(步驟 1 2 0 4)並使該標記 寫入更新的資訊至該第一標記上(步驟1 2 1 6)。 在這些方案中,該警示狀況可被辨認,且用於回 示並計算更新資訊的規則在.系統本身之中或是在 部的應用程式中完成。在後者情況中,該應用程式 接收源於系統所維護之物件的資訊並產生更新的特 並將其伴隨著寫入至第一標記的要求提供至本發明 第1 3圖說明資料流動過程的另一態樣。在一說 效日期 1 50暴 一說明 第一標 1202) ° 及導源 連的感 資訊維 也接收 驟 120 擬項目 為了回 供寫入 記寫入 寫入處 應該警 系統外 自系統 性資訊 系統。 明的例 47 1310919 子中,本發明系統接收關於一第一項目的特性資訊,該特 性資訊源自藉由一第一標記讀取器從位於第一項目的一第 一標記自動讀取的標記資料(步驟13 02)。本發明系統也接 收關於該第一項目之更新的特性資料(步驟1 3 04)。本發明 系統隨後在一不同的標記寫入處偵測該第一標記的存在 (步驟1 3 0 6)且使該標記寫入處將更新的資訊寫入至該第一 標記(步驟13 0 8)。在此方案中,可在系統本身内計算該更 新的資訊,或足在系統外的應用程式中完成。在後者情況 中,該應用程式自系統接收源於系統所維護之物件的資訊 並產生更新的特性資訊並將其伴隨著寫入至第一標記的要 求提供至本發明系統。 如第14圖所示,可與一共享的ITS(項目追蹤系統)及 多個通常為私有的區域 IT S s共同實施一種和本發明一致 之系統。本發明系統不需具有一明確的最高層級及共用節 點。本發明系統的某些實施將會是企業的一種聯合而不具 有階層體系於企業之上。其他的實施將會是多個最高階 層、共享節點,各自可能在企業階層上支援一特定企業部 門。大致上,該架構將由各種考慮所驅使,包括在支援企 業内的協議。 在第14圖中,既有的ERP(企業資源規劃)系統)40 1可 為任何用於管理貨物移動及儲存的區域企業軟體。用於每 個企業(或一企業的部分)的ERP系統可能有所不同。每個 企業具有多個標記讀取器1 402自數位識別標記供給數位 48 1310919 資訊至一區域ITS内。大致上一標記讀取器為能供給自 何項目或容器收集的數位資料之硬體及軟體的任何組合 可放置讀取器在生產線上、在儲存場所中、在卡車或其 移動載具中’也可以是手持式無線連結裝置。某些實施 意地在實體物理讀取器及ITS之間插入硬體及軟體。 在第14圖中’每個區域ITS 1 403為一種硬體及軟體 系統可被實施於一個或多個電腦系統上。此系統典型的 地理上相對於企業的其他部分為區域的,但實際上可被 置在任何適當地連結至區域ERP系統及標記讀取器的 方。通常一 ITS服務單一企業或該企業的一部份。因此 當具有超過一個區域IrS時,各自可由不同的企業操作 一 ITS也可連接至其他既有的企業軟體系統,如那些用 供應鏈管理、物流、客戶關係管理的軟體系統以及由那 構成ITS之可用的資料所形成的新軟體服務。 一共用的ITS 14 04是一種由多個區域ITS共用的項目 蹤系統。其廣泛地連接至多個區域ITS系統且也可連接 多個其他的共用ITS系統。一共用的1TS也可連接至其 新的以及既有的企業軟體系统。 區域以及共享ITS在一網路連線14 05上通訊,該網 連線可為任何電腦對電腦的連線技術。大致上在企業間 匕訊會為了安全而加密,且會使用數位認證或其他安全 法以驗證通訊中的參與者。該通訊媒介可包含公用網路 此連線通常即時地或接近即時地傳遞表示標記項目之位 任 〇 他 隨 的 在 放 地 5 Ο 於 種 追 至 他 路 該 方 〇 置 49 1310919 的訊息以及其他表示運輸文件、裝運載具等等的資訊。 一單獨位置1406為其為了支援區域橾作所需之硬體及 軟體的集合。一位置可為一製造者、一分配者、一零售機 構、一私人住宅、·一維修站或任何其他處理標記物品的場 所或一場所的部分。 新的以及既有的應用程式1 4 0 7可為既有的企業軟體系 統,例如那些用於供應鏈管理、存貨、客戶關係管理以及 由那種構成ITS之可用的資料所形成的新軟體服務。透過 一網路連線1 40 8,這些應用程式可詢問該ITS關於其追 蹤的項目之現在狀態、過去歷史與其他資訊。這些詢問並 不會改變在該IT S系統内記錄的狀態,且可在損失很少或 不損失實用性的情況下藉由處理存於——永久儲存區中該 ITS的狀態記錄操作這些詢問,而不用處理該ITS中現場 資料上的詢問。 第15圖說明在項目追蹤基礎架構内的基礎軟體元件。 一即時輸入處理軟體1 5 0 1自標記讀取器、既有的ERP系 統以及其他ITS系統接收配置及其他訊息。這些訊息可為 XML或其他格式。該訊息可表示實體或邏輯項目的產物, 或這些項目之配置或狀態的改變。該軟體的這個部分解譯 進來的訊息、洽詢該資料儲存項目1 5 0 2、基於訊息内容及 儲存資料採取適當的行動、更新資料結構並可能回報錯誤 訊息.或其他報告至訊息來源。 資料結構以及永久儲存區1 5 0 2記錄並維護關係以及 50 1310919Pass or weather information. The general information is that the provider sends the information to enable the department to inhale the information to bring the information to the department ', '. The information such that the information can be reported or predicted to be delayed or the other may affect the introduction of the project. Other situations of movement or condition. Figure 9 is a hobby. This is the implementation of the month and the provider provides information _! In this illustration, the 丄-father information provider generates a bow event and a UID and a feature and transmits the event to the CMC (step 12 0), which schedules the event to An OIC (step 122). The received OIC generates a new virtual status event and UID to the CMC (step 124), which schedules the path to CAIC for the event (step 126). The CAIC determines that the event is a new virtual status event type (a branch of "yes" in step 128), and generates a new virtual item as a UID based on the particular material (step 130), and stores the new virtual Status data (step 132). 2.2 Two-way data flow The system of the present invention provides data flow on the mark and two-way data flow. Figure 1 illustrates a scenario. A marker 15 2 is attached to a case 150. The tag contains a UID and stores an expiration date, a maximum temperature threshold, a maximum encounter temperature reading, and a price. The temperature profile on marker 152 can be updated with the temperature frequency of the measurement box 150, such as a temperature measurement station that can write its reading to the marker 152 or an operational temperature sensor connected to the marker 1 5 2. The material on the marker 152 can be automatically read by the marker reader 158, for example using RFID technology. In one embodiment, the indicia reader 158 periodically "scans" its context within a particular range. In another specific embodiment, the indicia reader is triggered to scan its context, such as by a proximity sensor. If a scan returns a valid read data (via communication 1 5 4), for example because marker 1 5 2 is moved into the scan range, tag reader 1 58 will transmit the received data to system 1 66 (via communication 1) 62). In this example, it is assumed that the virtual system y I74 introduced by an external application 45 1310919 1 74 is also fixed and then 170 is "up to 45 degrees high". Any definition rule 1 7 can be used to 'execute ^ system 1 6 6 will be valid and 1 6 4 ), and there will be an 11th picture on page 1 5 to ask the system 1 6 6 temperature The latest is 1 7 1, for the outside; send an event to the effective date of the system, trigger the system 1 6 6 a mark writer mark writer will be . Previously mentioned as the Internet; in these party games 168 (via communication 172) the external application adds a rule 170 to the virtual item 16 8 . The maximum encounter temperature ratio of the box whose criteria are on its mark can be defined, and the current date is written as the effective date to the format, syntax, or computer code whose mark is compatible with system 166. Whenever the system receives the white mark 丨5 2, the new capital is read 1 70. If the rule 回报70 returns a certain result, a new valid period is calculated as in the current period, and the UID of the new flag 152 is transmitted to the marker writer 16〇 (written by the pass s writer 1 60 0) The new valid date data is in the field of the standard effect data (via communication 156). Another solution in which the external application 174 periodically reports the maximum state of the box 15 stored on the marker 152. In this scheme, The logic can be again defined as a portion A of the application. The external application 174 is traditionally 166, the event containing the um of the flag 152, a newly updated 彳berg, and updated control information. This event is used to transmit the received The effective date, price, and UID to 160 (via communication 164). The system 166 of the present invention then writes the collected data to the corresponding data on the tag 152. The communication can be implemented over any communication medium, including on the road. There is a tag reader that can read the data stored on the mark 46 1310919 1 5 2, and a receiver of the box 150 will recognize the price and the price is the tracking process. The temperature at which the box is exposed is based on Figure 12. Figure 2 illustrates one aspect of the data flow process. In an example, the system of the present invention receives a UID by reading a note located in the first item regarding the first item. Characteristic Information (Steps similarly, the system of the present invention receives information about a second item for contextual information of the material, wherein the material is automatically read from the corresponding item with the second item (step 1 204). The system of the present invention The virtual first and second items are used (step 1206). The system of the present invention indicates relationship information between the items and maintains a virtual relationship (step 8). With this information, the system of the present invention can be based on at least partial virtual identification. a warning condition associated with the first item (step 1210). The condition should be alerted, the system of the present invention generates updated characteristic information to the first item (step 1 2 1 2). The system of the present invention detects after a target The presence of the first flag (step 1 2 0 4) and writing the flag to the updated tag (step 1 2 16). In these scenarios, the alert condition can be The rules that are identified and used to recall and calculate updated information are done in the system itself or in the department's application. In the latter case, the application receives information from the objects maintained by the system and generates The updated feature is accompanied by a request to write to the first mark to provide another aspect of the data flow process of Figure 13 of the present invention. On the date of the effect, the first mark 1202) And the sense information of the source and the source also receives the step 120. In order to write back the write to the write, the system should be outside the system information system. In the example 47 1310919, the system of the present invention receives a first The characteristic information of the item is derived from the mark data automatically read from a first mark located in the first item by a first mark reader (step 1300). The system of the present invention also receives the updated profile data for the first item (step 1 3 04). The system of the present invention then detects the presence of the first mark at a different mark write (step 1 306) and causes the mark write to write updated information to the first mark (step 1300) ). In this scenario, the updated information can be calculated within the system itself or in an application outside the system. In the latter case, the application receives information from the system that is derived from the items maintained by the system and produces updated characteristic information and provides it to the system of the present invention along with the requirements for writing to the first indicia. As shown in Fig. 14, a system consistent with the present invention can be implemented in conjunction with a shared ITS (Project Tracking System) and a plurality of generally private area IT Ss. The system of the present invention does not need to have a clear highest level and shared nodes. Some implementations of the system of the present invention will be a combination of enterprises without a hierarchy on the enterprise. Other implementations will be multiple top-level, shared nodes, each of which may support a specific enterprise sector at the enterprise level. In general, the architecture will be driven by a variety of considerations, including agreements to support the industry. In Figure 14, the existing ERP (Enterprise Resource Planning) system 40 1 can be any regional enterprise software used to manage the movement and storage of goods. The ERP system used for each business (or part of a business) may vary. Each enterprise has a plurality of tag readers 1 402 that provide digits from the digital identification tag 48 1310919 information into an area ITS. Roughly any combination of hardware and software that can be supplied to a digital data collected from any item or container can be placed on the production line, in a storage location, in a truck or its mobile vehicle. It can also be a handheld wireless connection device. Some implementations intentionally insert hardware and software between the physical physical reader and the ITS. In Fig. 14, 'Each area ITS 1 403 is a hardware and software system that can be implemented on one or more computer systems. This system is typically geographically relative to other parts of the enterprise, but can be placed in any way that is properly linked to the regional ERP system and the tag reader. Usually an ITS service is a single business or part of that business. Therefore, when there is more than one area IrS, each can be operated by a different enterprise. An ITS can also be connected to other existing enterprise software systems, such as those using supply chain management, logistics, customer relationship management, and the ITS. New software services formed by available materials. A shared ITS 14 04 is a project trace system shared by multiple regional ITSs. It is widely connected to multiple regional ITS systems and can also be connected to multiple other shared ITS systems. A shared 1TS can also be connected to its new and existing enterprise software systems. The zone and shared ITS communicate on a network connection 14 05, which can be any computer-to-computer connection technology. In general, inter-enterprise telex will be encrypted for security and will use digital authentication or other security methods to authenticate participants in the communication. The communication medium may include a public network. This connection usually transmits the information indicating the marked item in real time or near-immediately, and the information that he is following in the land 5 Ο 追 追 追 追 追 追 追 49 49 49 49 Information indicating shipping documents, loading vehicles, etc. A separate location 1406 is a collection of hardware and software needed to support the zone. A location can be a manufacturer, a distributor, a retail facility, a private home, a service station, or any other part of a venue or venue that processes the marked item. New and existing applications 1 4 7 7 can be used for existing enterprise software systems, such as those used for supply chain management, inventory, customer relationship management, and new software services formed by the materials that make up ITS. . Through an Internet connection 1 40 8, these applications can ask the ITS about the current status, past history and other information of the items it tracks. These queries do not change the status of the records in the IT S system, and can operate these queries by processing the status records of the ITS stored in the permanent storage area with little or no loss of utility. Instead of dealing with queries on the live data in the ITS. Figure 15 illustrates the underlying software components within the project tracking infrastructure. An instant input processing software 1 501 receives configuration and other messages from the tag reader, the existing ERP system, and other ITS systems. These messages can be in XML or other formats. This message can represent the product of an entity or logical item, or a change in the configuration or state of those items. This section of the software interprets the incoming message, consults the data storage project 1 5 0, takes appropriate action based on the message content and stored data, updates the data structure and may report an error message or other report to the source of the message. Data structure and permanent storage area 1 5 0 2 record and maintain relationship and 50 1310919

由該ITS追縱的邏輯及實體項目的狀態及歷史的 如這軟體可記錄對應一特定罐裝洗潔劑的某個唯 該洗潔劑實際上可能裝在一箱子中(在ITS ’ΛΙ已 难 ‘ °&amp;以及項目),其可能在—^車上(在ITS 另一唯一標記以及項目)且回應即時訊息以及出 入處理軟體1501的軟體動作,可定期更靳卡車 該資料結構也可記錄該洗潔劑為某個運輪的部$ UID的邏輯項目)。該資料結構以及永久儲存區在 及軟體錯誤中保存該資料結構。可使用任何建立 區的健全方法,例如某人可利用軟體資料庫技術 機以一種不易消失的方式記錄資訊。 一用於詢問的軟體介面1503提供一 its以及 軟體應用程式之間的介面。舉例來說,如果. ERP(企業資源規劃)或Scm(供應鏈管理)系統需 目之現在實際位置上的更新,其會送出一詢問。 久儲存區可提供操作的必要資訊,而用於詢問的 用此資訊來操作像是“報告一特定種類而現在位 的地理區域之内的所有電池(由一產品編碼識另, 問。或一詢問像足:“報告所有在保存期限到達肯 的盒襞牛奶” 3 ·1軟體升級 該IT S基礎架構(如第1 6圖所示)之核心3 1 0 表示。例 一標記。 知的另一 内已知的 於即時輸 的位置。 卜(一具有 任何硬體 永久儲存 以及磁碟 外部企業 -傳統的 要在某項 該ITS永 介面可利 於一給定 [)”的詢 j* 48小時 應時時刻 51 1310919 刻持續地操作。既然經濟;舌動依賴系統的某一部份,停 止系統以維護或升級系統定不實用的。然而,本發明系統 將會需要以各種方式升級。以下將描述其結構以滿足此需 要。 將考慮三種軟體升級:增加或刪除欄位(即屬性)、增加 或改變執行攔位内容之語意通知的編碼(即電腦程式指示) 以及主系統升級。每一種將依序在此討論。 製造者、分配者、零售商以及其他人可能需要增加或刪 除表示單獨項目或項目群組的資料欄位以求區域操作的便 利。舉例來說,也許會希望加上一欄位指出處理項目時的 溫度。此資訊可能很重要,例如用於長期可靠度及產品退 回研究。此處理溫度欄位含有不同於既有的溫度欄位的資 訊,例如現在溫度或在傳輸或儲存裝置時的最大感應溫 度。也可對其有不同地處理。舉例來說,該製造者也許希 望處理溫度數值長期儲存以供可靠度研究,但不要洩露給 其他製造者或任何機構。 其他加入或刪除資料欄位的例子包括:一零售商希望記 錄售出但隨後退回的項目。一規定改變而某些管轄權要求 此種產品的保存期限;該欄位由製造者完成且依照分配者 及零售商的要求動作。 在另一例子中,一分配者負責提供關於項目的退回貨 運,該項目由客戶退回至製造者。該分配者想要加入一欄 位“退回貨運負責方”,其會自動填八分配者的名字,因 52 1310919 此當項目被退回時法律上負責方要承擔此責任。此分酉己 者資訊或許能自歷史取得。但是該額外的攔位使其清楚的 顯示誰要承擔此責任,而不需詢問歷史。 大體而言,本發明系統可以動態地增加一新的資料欄位 (即屬性)至任何既有的物件。次外,該物件記錄可被任何 較高或較低階層體系的系統接收而不用改變程式設計以及 不需改變過去或未來的相同形式物件。 資料欄位只有當該物件位於某狀態時才有意義的話可 能希望將之刪除。舉例來說,與一運輸表或包裝表有關的 欄位只有在該物件表示一項目屬於現在運輸的部分時才有 效。一旦該運輸正式被接收,運輸攔位便被從動態資料結 構中刪除(但保留在歷史中)。如果無效欄位沒有被刪除, 也可選擇將其標示為無效。 增加或改變實行語意行為的編碼可將系統升級,通常大 家都會希望持續地增加系統的能力並改進較舊的功能。這 些改變需要許多選擇,例如:當增加新的能力時,誰設計 程式,怎測試以及如何使對其他活動的影響降至最低。 需要增加或改變語意行為的情形之例子包括:一所的成 員加入一合夥並需要新的功能以管理其各種貨物。既有的 功能改變,例如一種管理保存期限之設定的方法改變,或 發展出一種更好的裝載至卡車的步驟。 增加功能至基礎架構的任何項目可能需要增加新的資 料爛位。 53 1310919 改變語意行為可能會使整個系統當機。因此完全控制的 測試方式以及引入新的編碼而改變語意行為是很危險的。 大體上可以改變一特定項目形式的語意處理以及改變特定 項目而不需停止操作系統。此外對於其他物件的行為有很 大的信心不會被改變。 主要系統的升級是可能的,包括升級以改變所有軟體, 升級磁碟機格式以及升級硬體,通常本發明系統顯然地可 以使中央系統操作在兩種硬體/軟體設定間切換而不會造 成任何可看見的服務損失。此步驟應該是非常好的。 為了系統可靠度因素,可以運行一影子系統。這樣的一 種系統也提供主要系統升級的一種機制。 如第1 6圖所示,將主動的資料儲存與所有的語意方法 分開。該核心1 6 1 0提供一基礎功能的小型集合但在其他方 面獨立於任何特定物件處理。因此,當心的資料欄位或新 的語意處理被加入時,該核心1 6 1 0不需要改變。這樣一種 核心是非常普遍的且可為了其基礎功能及非常高的可靠度 而最佳化。該核心1 6 1 0程式設計將會很少改變。 本發明系統的其他部分透過内部處理通訊或文件交換 來聯繫,因此即使其他部分失敗且必須重新啟動該核心 1 6 1 0仍可繼續操作。 該核心1 6 1 0可從一先前的快照重新啟動。隨後其可藉 由重播過去事件(假設的重複執行,陸)或使用自永久儲存 區中可用的東西以重新建構該現在狀態而成為最新的。如 54 1310919 以下所述,尚未交給永久儲存區1 6 2 0的改變必須重 行。 將以一有效方式支援系統所有各式需求的小型 合將在以下描述。 如第 1 6圖所示,該無狀態(stateless)的即時語 1 6 3 0執行下列動作:(1 )其自網路接收配置訊息。 訊息總是指定至少一個項目。(2)其擷取對應至特定 物件。通常可避免鎖定。(3)其可使用源自物件的資 擇適合的語意處理方法。(4)其擷取任何物件進一 要,若有必要則加以鎖定。(5)其計算更新物件記 其傳遞改變至核心1 6 1 0,且可解除所有物件記錄白〗 該即時語意區段1 6 3 0是完全無狀態的。因此可以 時間關掉任何部分、重新啟動並繼續操作。此大大 動態載入新的語意方法,例如使用Java機制、且自 誤中恢復。 有許多方式選擇方法應用至一進入的配置訊息。 編碼既依賴物件的類型或種類也依賴指出的配置。 說,裝載一運輸載具對於多數物件將可能非常相似, 給最後用戶”的配置可能高度從屬於項目的類型。 種實施可擇一使用:(1)依靠用於ePC中明確的產品 位,這是由麻省理工學院自動ID中心所提出的。 指定的物件以及其可能的根形式(r 〇 〇 t -1 y p e)物件, 一項目種類識別記號。 新被執 功能集 意區段 一配置 項目的 訊以選 步的需 錄。(6) i鎖定。 在任何 地幫助 任何錯 適當的 舉例來 但“賣 至少兩 類型攔 (2)查詢 以得到 55 1310919 第二種方法並不依賴 e P C編號方案的部署且相容於任 何標記系統。再者,其迂迴的層級允許廣大種類的物件由 相同的軟體處理。舉例來說,一生產者的所有洗潔劑產品 可用相同的編碼處理,而其他生產者的洗潔劑可用不同的 編碼。最後,可設定核心1 6 1 0因此個別項目可被插上旗標 以觸發不同的編碼。如此可允許即時測試限於小型集合物 件之新的編碼。為了達到好成果,此編碼為多線程的。這 樣使物件(也可能是由該物件所參照的任何根物件)在該語 意編碼被分派之前可被取回。 可有利地實施該核心1 6 1 0以致於其並不具持久性。為 了提供彈性及速度,該核心 1 6 1 0可唯一電腦記憶體子系 統。該核心 1 6 1 0亦可選擇直接對應至永久儲存區機制 1620 ° 該永久儲存區機制 1 620為一種模組,該模組自核心 1610取得一連串的物件改變通知並將其交給永久儲存 區。可自儲存區資訊快速地建立一種系統狀態的現時快照。 由以下所述提供歷史機制 1 6 4 0。對於本發明系統有兩 種活動的來源:配置訊息,其通常表示源自一獨立項目的 嗶聲或訊號,以及由外部系統向累積的物件資料所做的詢 問。該物件移動嗶聲更新該核心1 6 1 0,因為其代表項目之 領域狀態的改變,但是不需要連線至過去歷史。該外部詢 問與移動歷史以及現在配置有關,但不需要改變該狀態。 本發明系統可累積歷史且對現在狀態亦有一最近的觀 56 1310919 察Q此為了大型的非即時加強詢問可將其最佳化。因為 ,'本質上疋唯項的,可輕易地將其複製以支援大量的詢問。 k歷史機制也需要永久儲存區。因此該歷史功能通常會 被納入永久儲存區機制丨。該核心1 6 1 〇具有一功能性 的最小集合。可建立並延伸物件,包括以下功能:(a)建立 (b)加入或刪除一屬性·名稱值對(pr〇per name— Μ物件名稱S唯4任意大小的…名稱自 可延伸的名單宁取出,以避免激增並避免產生具有不一 致語意之衝突的名稱。 其特別地·^以· 該核心1610可存取並更改屬性值 (a)送回所有屬性(名稱值對),且 (b)更新屬性.名稱值對。 該核心1610具有專門的(内建的)屬性名單171〇功能’ 如命名集合擁有權及成員權,包括:⑷以—種新的類级-名稱集合製造物件所有者(根)的能力,以及 (b)增加及刪除一命名集合中的成員。 最後,該核心1610具有很少使用的物件鎖定,包栝 下列能力: (a) 鎖定物件一提供簽名,且 (b) (b)解鎖物件提供一致的簽名。 這個核心1 6 1 〇功能之非常小的集合與標記及讀取器 關連不大,其也與項目在實體世界中位置關連不大。這是 種主要的優點。該資料結構是足夠普遍的,其不需要改 57 1310919 變通過供應鏈或其他應用程式之項目的語意。該核心1610 軟體是高度最佳化的以執行操作的小型集合,而語意變化 谷納於無狀態的語意方法中。的確許多集合在其發展時會 被鎖在資料結構中,而某些語意變化可能需要重新建構現 時的物件結構。然而’這可在一現場系統中完成而不需要 軟體改變該核心161 〇。下表提供一簡化的例子說明可如何 使用這些架構。 #1147 : {物件 ID ; #1147}{物件-類型;基礎—£]?(::_類 型} {軟體_版本:2} {種類:”洗潔劑 ” }&lt;PML:,,http......,’ } {EPC-類型 __集合—根,#341,#576.......} #341 . {物件ID : #341} {物件類型:EPC_物件—實體} {EPC—類型-集合-成員容器_集合_成員#3328} #576: {物件 iD:#576}{物件類型:EPC一物件—實體} {EPC_類型〜集合一成員:容器一集合_成員#3328 } #621’ {物件ID: #621}{物件類型:Epc —物件—實體} {EPC-類型-集合〜成員;#1147_容器_集合_成員#3348} #2287 . {物件ID ; #22 8 7} {物件類型;ERP — 裝運} {裝運—集合、根;#3328 ··.·...} {裝運〜企業—成員:#3347} {裝運&quot;系统_來源··” R/3 4〜6” } 58 1310919 #3 328 : {物件 ID : #3328}{物件類型·容器} {物件—描述;” 1 4 X 1 8 X 1 0硬紙箱” } {即時_位置_類型:跟隨_較高—階層_容器} {容器_集合_根;#341,#576} {裝運—集合_成員;#228 7} {容器_集合_成員;#4421 } #4421 ; {物件 ID: #4421}{物件類型:容器} {物件_描述:”10,00011?卡車”} {即時_位置_類型;GPS 經度_緯度—高度} {容器_集合_根:#3328 } {緯度:32N}{經度;60,45}{高度;327M}{位置—最後 更新:1/12/200214 ; 27} #334 8 ; {物件 ID ; #334 8 } {物件類型:容器} {物件—描述;”倉庫貨架” } {即時_位置_類型:固定儲存位置} {儲存區_位置_區域:”貨架3” } {容器—集合—根:#621”’ } {容器_集合_成員:#4462} #4462 : {物件ID : #4462 —物件類型:容器} {物件_描述;”倉庫區域” } 59 1310919 {即時_位置_類型:固定儲存位置} {儲存區—位置_區域;”區域1 6” } {容器—集合_根:#3348··· } {容器—集合_成員:#448 1 } #44 8 1 : {物件ID:#44 8 1&gt;&lt;物件類型:容器} {物件_描述:”倉庫” } {即時_位·置_類型;具有緯度/經度/高度之最高階 層固定位置} {容器—集合—根,#4462··.} {緯度:31N —經度;60.45}&lt; 高度 10 0M} 上表描述一相當複雜的情況,也在第1 8及19圖中說 明。如上表所示,# 11 4 7表示產品種類“洗潔劑”。特定 罐裝的洗潔劑由物件實體#341,#576以及#621表示。 如第1 8圖所示,這些罐裝洗潔劑18 1 0中的兩罐在一紙 箱1820中。該紙箱在一卡車1830尚且該卡車具有一 GPS 定位系統以供即時定位回報。該箱子為一特定裝運中的部 分。另有一第三罐洗潔劑1940儲存在一倉庫1950之一區 域1970的一貨架1960中。 該集合機制給予資料結構一種很強的力量,舉例來說: 如果有洗潔劑ePC基礎類型的物件ID,某人可詢問該 集合,並到達所有洗潔劑的實體以及其現在位置。 60 1310919 如果有倉庫的物件ID,某人可發現所有倉庫中的項目 以及其存放位置。 如果有洗潔劑的任何實體的物件ID,某人可找出相應 的運輸號碼,如果該號碼存在的話。 如果有一裝運的物件ID,某人可找到所有的項目以及 其位置。 如果有卡車的物件ID的話,某人可找到所有卡車中的 項目及其有關的裝運文件。資料復原 資料復原是一關鍵議題。當偵測到一嗶聲於網路2 0 1 0 之葉(leave)時,第 20圖說明白此之後系統内的延遲,直 到該嗶聲的含意被記錄至永久儲存區2 0 2 0為止。假設一悲 惨的錯誤在一共享(中央)位置,復原意味著從現在在磁碟 上的資訊開始,然後考慮所有還沒有被處理的變化。一種 復原的方式為記錄一定量的歷史於網路基礎架構本身 20 60之内。舉例來說,可建立發表_訂購配置機制使其具 有可靠的内部永久資料儲存區。另外的方式為在該網路的 每個葉節點具有永久儲存區。 所有需要的儲存區2040等於自該標記讀取器到達系統 永久儲存區時所有遍佈系統的延遲。 通常不容易確定哪些事件有作用而哪些事件已經遺 失。再者,在即時語意區段1 6 3 0以及核心1 6 1 0之中並沒 有事件處理的内在,煩序。假如所有處理為等冪且獨立順 序的,重播足夠的事件以涵蓋最大可能的遺失工作。如果 61 1310919 此條件成立,該引起操作2060之語意為:如果事件 的頂序處理或該相同的事件被處理超過— -人,該最 狀態會是相同的。 以不同 終系統 位置更新 某些高價值項目以及如卡車等運輪载具可用即 系統(RTLS)加以標記。舉例來說,位於加州聖塔克The state and history of the logical and physical items tracked by the ITS, such as the software, can record that a certain detergent can only be contained in a box (in ITS 'ΛΙ Difficult to '°& and project), which may be in the car (in the ITS another unique mark and project) and respond to the instant message and the software action of the access processing software 1501, the truck structure can be periodically changed or recorded. The detergent is a logical item of the UID of a certain wheel.). The data structure and the permanent storage area and the software error are saved in the data structure. Any method of establishing a zone can be used, for example, someone can use the software library technology to record information in a way that is not easy to disappear. A software interface 1503 for interrogation provides an interface between its and software applications. For example, if an ERP (Enterprise Resource Planning) or Scm (Supply Chain Management) system requires an update to the actual location, it will send a query. The long storage area provides the necessary information for the operation, and the information used for the inquiry is to "report all the batteries within a geographical area of a specific category and now (by a product code, another question, or one) Ask the image foot: "Report all the boxes of milk that arrived in Ken during the shelf life" 3 · 1 software upgrade The core of the IT S infrastructure (as shown in Figure 16) 3 1 0 means. Example 1 mark. A location known in the instant to lose. Bu (a hardware with any permanent storage and disk external business - the traditional to be in a certain ITS permanent interface can be given a given [)" query j * 48 hours It should be operated continuously at the time of 51 1310919. Since the economy relies on a certain part of the system, it is not practical to stop the system to maintain or upgrade the system. However, the system of the present invention will need to be upgraded in various ways. Describe the structure to meet this need. Three software upgrades will be considered: adding or deleting fields (ie attributes), adding or changing the encoding of the semantic notifications that perform the blocking content (ie computer program instructions) And the main system upgrades. Each will be discussed here in order. Manufacturers, distributors, retailers, and others may need to add or delete data fields that represent individual projects or groups of projects for regional convenience. Say, you may wish to add a field to indicate the temperature at which the item will be processed. This information may be important, for example for long-term reliability and product return studies. This processing temperature field contains information that is different from the existing temperature field. For example, the current temperature or the maximum sensing temperature at the time of transmission or storage. It can also be treated differently. For example, the manufacturer may wish to process the temperature values for long-term storage for reliability studies, but do not leak to others. Manufacturer or any institution. Other examples of joining or deleting data fields include: a retailer wishing to record a project that was sold but subsequently returned. A provision changes and some jurisdictions require the shelf life of such a product; It is done by the manufacturer and acts according to the requirements of the distributor and the retailer. In another example, a distributor is responsible for providing The item is returned to the shipment, and the item is returned by the customer to the manufacturer. The distributor wants to add a field “Return to the responsible party of the shipment”, which will automatically fill in the name of the assignor, as 52 1310919 when the project is returned The responsible party is responsible for this responsibility. This information may be obtained from history. However, this additional barrier makes it clear that whoever bears this responsibility without asking history. In general, the system of the present invention A new data field (ie, attribute) can be dynamically added to any existing object. In addition, the object record can be received by any higher or lower level system without changing the programming and without changing the past. Or the same form of object in the future. The data field may only be deleted if it is meaningful when it is in a certain state. For example, a field related to a transport or packing list only indicates that an item belongs to the item. The part of the transportation is now valid. Once the shipment is officially received, the transport block is removed from the dynamic profile (but remains in history). If the invalid field is not deleted, you can also choose to mark it as invalid. Increasing or changing the coding of semantic behavior can upgrade the system, and often everyone will want to continuously increase the capabilities of the system and improve older features. These changes require many choices, such as who designs the program, how to test it, and how to minimize the impact on other activities when adding new capabilities. Examples of situations in which a semantic behavior needs to be added or changed include that a member of a club joins a partnership and needs new functions to manage its various goods. Existing functional changes, such as a method of managing the set-up of retention periods, or a better step of loading into a truck. Any project that adds functionality to the infrastructure may need to add new information to the rogue. 53 1310919 Changing semantic behavior may cause the entire system to crash. It is therefore dangerous to have a fully controlled test approach and to introduce new codes to change semantic behavior. In general, it is possible to change the semantic processing of a particular project form and change specific projects without stopping the operating system. In addition, there is a great deal of confidence in the behavior of other objects that will not be changed. Upgrades to major systems are possible, including upgrades to change all software, upgrade disk format, and upgrade hardware. Typically, the system of the present invention clearly allows central system operation to switch between two hardware/software settings without causing Any visible service loss. This step should be very good. For system reliability factors, a shadow system can be run. Such a system also provides a mechanism for major system upgrades. As shown in Figure 16, separate active data storage from all semantic methods. The core 1 6 1 0 provides a small collection of basic functions but is otherwise independent of any particular object processing. Therefore, the core 1 6 1 0 does not need to be changed when the care data field or the new semantic processing is added. Such a core is very common and can be optimized for its underlying functionality and very high reliability. The core 1 6 10 programming will change very little. The other parts of the system of the present invention are contacted by internal processing communication or file exchange, so that operation can continue even if other parts fail and the core must be restarted. The core 1 6 1 0 can be restarted from a previous snapshot. It can then be up-to-date by replaying past events (hypothetical repetitive execution, land) or using what is available from the permanent storage to re-construct the current state. As described below, 54 1310919, changes that have not been handed over to the permanent storage area 1 6 2 0 must be repeated. A small combination that will support all of the system's various needs in an efficient manner will be described below. As shown in Figure 16, the stateless instant language 1 6 3 0 performs the following actions: (1) it receives configuration messages from the network. The message always specifies at least one item. (2) The corresponding corresponds to a specific object. Locking is usually avoided. (3) It may use a semantically appropriate method of processing derived from the object. (4) It takes any object and enters it, and if necessary, locks it. (5) The calculation updates the object record, the transfer changes to the core 1 6 1 0, and all the object records can be released. The instant semantic segment 1 6 3 0 is completely stateless. So you can turn off any part, restart, and continue. This greatly loads new semantic methods, such as using Java mechanisms and recovering from errors. There are many ways to apply the method to an incoming configuration message. Encoding depends on the type or type of object and also on the configuration indicated. Saying that loading a transport vehicle will likely be very similar for most objects, and the configuration for the end user may be highly dependent on the type of project. The implementation can be used alternatively: (1) relying on a clear product location for ePC, this It is proposed by the MIT Automatic ID Center. The specified object and its possible root form (r 〇〇t -1 ype) object, a project type identification mark. (6) i lock. Any help with any wrong example anywhere but "sell at least two types of intercept (2) queries to get 55 1310919 The second method does not rely on e PC numbering The solution is deployed and compatible with any marking system. Furthermore, its roundabout hierarchy allows a wide variety of objects to be processed by the same software. For example, all of the producer's detergent products can be treated with the same code, while other producers' detergents can be coded differently. Finally, the core 1 6 1 0 can be set so individual items can be flagged to trigger different encodings. This allows for immediate testing limited to new encodings for small collections. In order to achieve good results, this code is multi-threaded. This allows the object (and possibly any root object referenced by the object) to be retrieved before the semantic code is dispatched. The core 1 6 1 0 can advantageously be implemented such that it is not persistent. To provide flexibility and speed, the core 1 6 1 0 is the only computer memory subsystem. The core 1 6 1 0 may also choose to directly correspond to the permanent storage area mechanism 1620 °. The permanent storage area mechanism 1 620 is a module that obtains a series of object change notifications from the core 1610 and hands them over to the permanent storage area. . A current snapshot of the system state can be quickly established from the storage area information. The historical mechanism 1 6 4 0 is provided by the following. There are two sources of activity for the system of the present invention: configuration messages, which typically represent a beep or signal originating from a separate project, and an inquiry by the external system to the accumulated object material. The object moves to update the core 1 6 1 0 because it represents a change in the state of the field of the project, but does not need to be wired to past history. This external query is related to the movement history and the current configuration, but does not need to change this state. The system of the present invention can accumulate history and has a recent view of the current state. This is optimized for large non-instant enhanced queries. Because, 'essentially, it can be easily copied to support a large number of queries. The k-history mechanism also requires permanent storage. Therefore, this historical function is usually incorporated into the permanent storage mechanism. The core 1 6 1 〇 has a minimal set of functions. Objects can be created and extended, including the following functions: (a) create (b) add or delete an attribute name value pair (pr〇per name - Μ object name S only 4 any size ... name from the list of extensible To avoid a surge and avoid creating names with inconsistent semantic conflicts. In particular, the core 1610 can access and change attribute values (a) return all attributes (name value pairs), and (b) update Attributes. Name value pairs. The core 1610 has a specialized (built-in) list of attributes 171 〇 function 'such as naming collection ownership and membership rights, including: (4) to create a new object class-name collection object owner ( The ability of the root), and (b) the addition and deletion of members in a named collection. Finally, the core 1610 has very few object locks, including the following capabilities: (a) locking the object one to provide the signature, and (b) (b) The unlocked object provides a consistent signature. This very small collection of core 1 6 1 functions is not as relevant as the tag and reader, nor is it related to the location of the project in the physical world. This is the main type. Advantage The structure is universal enough that it does not require the semantics of changing the project through the supply chain or other applications. The core 1610 software is highly optimized to perform a small set of operations, while the semantic changes are stateless. In the semantic approach, it is true that many collections are locked into the data structure as they evolve, and some semantic changes may require re-constructing the current object structure. However, this can be done in a field system without the need for software changes. Core 161. The following table provides a simplified example of how these architectures can be used. #1147 : {Object ID; #1147}{Object-Type; Basic-£]?(::_Type} {Software_Version: 2 } {Category: "Detergent" }&lt;PML:,,http...,' } {EPC-type__collection-root, #341,#576.......} # 341 . {object ID : #341} {object type: EPC_object - entity} {EPC—type-collection-member container_collection_member#3328} #576: {object iD:#576}{object type: EPC An object-entity} {EPC_type~collection one member: container-collection_member#3328} #621' {object ID: #621}{ Piece Type: Epc - Object - Entity} {EPC-Type-Collection~Member; #1147_容器_集_会员#3348} #2287 . {Object ID; #22 8 7} {Object Type; ERP - Shipment} { Shipment-collection, root; #3328 ····...} {shipment~enterprise-member: #3347} {shipment&quot;system_source··” R/3 4~6” } 58 1310919 #3 328 : {object ID: #3328}{object type·container} {object-description;" 1 4 X 1 8 X 1 0 hard carton" } {immediate_location_type: follow_high_class_container} {container_ Collection_root; #341,#576} {shipment-collection_member; #228 7} {container_collection_member; #4421 } #4421 ; {object ID: #4421}{object type: container} {object_ Description: "10,00011? Truck"} {immediate_location_type; GPS longitude_latitude-height} {container_collection_root: #3328} {latitude: 32N}{longitude; 60,45}{height; 327M }{Location—last updated: 1/12/200214; 27} #334 8 ; {object ID; #334 8 } {object type: container} {object-description; "warehouse shelf" } {immediate_location_type: Fixed storage location} {storage area_location_area:" goods 3" } {container-collection-root: #621"' } {container_collection_member: #4462} #4462 : {object ID: #4462 - object type: container} {object_description; "warehouse area" } 59 1310919 {immediate_location_type: fixed storage location} {storage area-location_area;"area 1 6" } {container-collection_root: #3348··· } {container-collection_member: #448 1 } #44 8 1 : {object ID: #44 8 1&gt;&lt;object type: container} {object_description: "warehouse" } {immediate_bit·set_type; highest level fixed with latitude/longitude/height Location} {container-collection-root, #4462·..} {latitude: 31N-longitude; 60.45}&lt; height 10 0M} The above table describes a rather complicated situation, which is also illustrated in Figures 18 and 19. As shown in the above table, #11 4 7 indicates the product type "detergent". Specific canned detergents are indicated by object entities #341, #576 and #621. As shown in Fig. 18, two of these canned detergents 18 1 0 are in a carton 1820. The carton is in a truck 1830 and the truck has a GPS positioning system for immediate positioning. The box is part of a particular shipment. Another third tank of detergent 1940 is stored in a shelf 1960 in a zone 1970 of the warehouse 1950. This aggregation mechanism gives the data structure a strong force, for example: If there is an item ID of the detergent ePC base type, someone can ask the collection and reach all the detergent entities and their current location. 60 1310919 If you have an item ID for a warehouse, someone can find items in all the warehouses and where they are stored. If there is an item ID for any entity with a detergent, someone can find the corresponding shipping number if it exists. If there is an item ID for the shipment, someone can find all the items and their locations. If there is an item ID for the truck, someone can find the items in all the trucks and their associated shipping documents. Data recovery Data recovery is a key issue. When a click is detected on the network 2 0 1 0, the 20th figure illustrates the delay in the system until the meaning of the beep is recorded to the permanent storage area 2 0 2 0. Assuming a tragic mistake in a shared (central) position, recovery means starting with the information now on the disk and then considering all changes that have not yet been processed. One way to recover is to record a certain amount of history within the network infrastructure itself. For example, a publish_order configuration mechanism can be established to have a reliable internal permanent data store. Another way is to have a permanent storage area at each leaf node of the network. All required storage areas 2040 are equal to all delays throughout the system from when the tag reader reaches the system permanent storage area. It is often not easy to determine which events are active and which have been lost. Moreover, there is no intrinsic, troublesome event handling in the instant semantics section 1 6 3 0 and the core 1 6 1 0. If all processing is idempotent and independent, replay enough events to cover the largest possible loss of work. If 61 1310919 is true, the act of causing operation 2060 means that if the top-order processing of the event or the same event is processed beyond the person, the most state will be the same. Update some high-value items with different end-system locations and ship-to-ship vehicles such as trucks that are available in the system (RTLS). For example, located in Santac, California

WherNet公司便提供WherTag標記,其定期地利用 頻段向區域廣播其識別,且其位置可由三角測量, 些標記廣播在從鞑也^ a 欠數秒至數分之固定間隔,僅能由, 該標記而改變。 此外,廣域系 傳統通訊系統結 以提供定期地位 基地台的現在位 统可利用GPS(全球衛星定位)接收 合’如行動電話或低頻寬衛星上傳 置更新。可向該通訊系統輪流查詢 置·’或者該通訊系統可於能遠瑞設 的時間間隔中呼叫。 一追蹤系統之 w 一基本的能力為接收位置資訊的 然只使用一種方it α 去來報告位置將會很方便,但在· 窄的區域如一建築物 多沒必要之額外計算 或一倉庫中使用緯度及經度將 步驟的風險,因此通常會使用 參照的區域框架 GPS系統的緯度 的偏移量。對於寬廣區域的使用’ 、經度及高度之可得資料足適合的 時位置 拉拉的 2.4GHz 定。這 體存取 器與一 系統, 距離一 計程式 艮告。雖 種很狹 冒著過 離開一 取自一 62 1310919 批次識別 大致上,會提供該項目追蹤系統更多的資訊,而不僅是 當項目被某一讀取器看見時發出嗶聲。此資訊可能為正在 讀取的計晝中一即將來臨的項目批次的配置。舉例來說, “以下項目正被自庫存中取出並被包裝至裝運X ” 。在別 處會提供本發明系統關於此裝運的資訊。 此資訊可來自接近一標記讀取器的終端機,該標記讀取 器直接連接至一系統應用程式(例如以一網頁瀏覽器為主 的應用程式);該資訊亦可間接地來自一區域系統,其可 以傳遞一適當訊息至追蹤系統。 由於項目通常以批次方式到達,可在區域快取嗶聲直到 批次結尾被記錄。然後該讀取器或區域系統送出一包含關 於所有批次中項目資訊的訊息給追蹤系統。該訊息可為一 標記語言的格式如XML。 可給予每個批次一唯一 ID。一批次編號(批次-1D)為一 種方法可簡潔地通訊關於一項目群組的一般資訊。每個讀 取器可具有一預設的批次-ID,並於沒有指定批次-ID時使 用。如果有使用批次-1D,源自讀取器的訊息可為以下形式:WherNet provides the WherTag tag, which periodically broadcasts its identification to the zone using frequency bands, and its location can be triangulated, and these tags are broadcast at a fixed interval from a few seconds to a fraction of a few minutes, which can only be change. In addition, the wide-area legacy communication system provides a regular status. The current location of the base station can be updated using GPS (Global Positioning Satellite) reception, such as mobile phones or low-frequency wide satellites. The communication system can be polled in turn or the communication system can be called in the time interval that can be set. A basic ability of a tracking system to receive location information is only convenient to use a square it α to report the location, but in a narrow area such as a building without additional calculations or use in a warehouse The latitude and longitude will be the risk of the step, so the offset of the latitude of the referenced area frame GPS system will usually be used. For the wide area of use, longitude and height of the available information is suitable for the time position of the pull of 2.4GHz. This system is linked to a system and a program. Although it is very narrow, it is taken from a 62 1310919 batch identification. In general, more information about the project tracking system will be provided, not only when the project is seen by a reader. This information may be the configuration of an upcoming project batch in the meter being read. For example, “The following items are being taken out of stock and packaged to Shipment X”. Information about the shipment of the system of the present invention will be provided elsewhere. This information can come from a terminal that is close to a tag reader, which is directly connected to a system application (for example, a web browser-based application); this information can also be indirectly from a regional system. , it can pass an appropriate message to the tracking system. Since the project usually arrives in batches, the buzz can be cached in the area until the end of the batch is recorded. The reader or zone system then sends a message containing information about the items in all batches to the tracking system. The message can be in the form of a markup language such as XML. Each batch can be given a unique ID. A batch number (batch-1D) is a method for succinctly communicating general information about a group of items. Each reader can have a preset batch-ID and is used when no batch-ID is specified. If a batch-1D is used, the message from the reader can be of the form:

時間戳記,批次_ID(如 96bit ePC),項目一ID 如此使用批次可支援一整理功能,用於當項目被讀取之 前未加以批次時。舉例來說,一裝配線可具有一連串順序 的項目以及一連串的箱子。該讀取器讀取每個項目上的標 記,並決定例如將項目放在箱子1或2或 3。每個箱子可 63 1310919 象徵例如不同的配置。該讀取器將不同的批次-1D置於每 個箱子上,而每個項目與放置在某處之箱子的批次-ID相 連。 基本的寸比次設計可包含具有一唯一 ID的讀取器以及 同樣具有一唯一 ID的裝運。該讀取器與裝運相連以產生 一特定的批次,其擁有一唯一 ID。源自相同的或不同的讀 取器的多個批次可結合至相同的裝運。必要的基本裝運可 包括一唯一 ID、一區域裝運編號(例如用於一區域ERP的 編號)、一貨物目標、一目標傳送日期以及一目標傳送時間。 每個具有一批次而非一讀取器的項目間的結合允許資 訊可安全地被重複且不會混淆。舉例來說,如果重新傳遞 配置資訊,卻由於像是系統錯誤或重開的原因,若使用批 次_項目配對而非讀取器項目配對,本發明系統的狀態將不 會改變。 配置動作 一配置動作描述關於物件及項目之階層體系與一標記 項目有關或相連之狀態變化。配置動作包括如建立項目或 第一次引入項目以追蹤、位置變化、庫存確認、裝運、裝 載、卸載以及結束追蹤。 該配置動作“建立項目”記錄_項目的初始屬性,例如 製造者、類型、製造曰期及地點等等。此動作可包含以某 些提供的資料將該標記初始化。其通常包含關於項目初始 64 1310919 存放位置的指示。 該配置動作“位置變化”係指項目將要或是已經被移 至一個新的給定位置。“庫存確認”係指該項目在一存放 位置被感應時將其加以記錄。 該配置動作“裝運”係指該項目被指定為某裝運的部 分。可給予區域ERP所知道的裝運編號。 該配置動作“裝載”係指當裝載一特定運輸載具時感 應到該項目。該卡車或其他運輸ID可結合至一裝運ID。 該配置動作“卸載”係指當卸載一特定運輸載具時感 應到該項目。該載具ID可結合至一裝運ID。 該配置動作“撤銷”為一動作,其有效地取消任何關於 相同項目及相同批次之過去的配置。常需要撤銷過去的配 置。舉例來說,當裝載太多的項目時撤銷便會出現。此動 作並非等冪的。 該配置動作“結束追蹤”係指追蹤系統不期待再次看到 該項目。此動作可能發生在像是零售銷售或當項目包裝被 打開以及箱子被回收時。本發明系統可能為了以後的保證 或歷史目的將該項目資料歸檔。 還有許多可能的配置。彈性的配置指定足較佳的。 裝運 一裝運識別一包裝表,典型地為以下形式:項目-類型 數量表。一裝運也定義這些項目類型計畫中的移動至一目 65 1310919 標。該目標可為一擁有地址的客戶,或相同公司的其他 置。該追蹤系統測定關於該地址的位置,像是緯度及經肩 或接收此資訊作為裝運描述的部分。 區域ERP系統。道該裝運。該追蹤系統可擷取該裝 資訊,將特定項目與一般項目-類型相配於裝運表中,並 告不一致之處。 一個或多個計晝裝運可連結至一特定的運輸載具。舉 來說,數個不同的裝運中部分送往相同的地址而部分送 不同的地址,仍可被裝載至同一台卡車上。本發明系統 確認正確地裝載該卡車。另外,本發明系統可追蹤卡車 估計其位置,並回應關於貨物位置的詢問。 一特定的邏輯裝運事實上可以分散至數個運輸卡車。 樣的分配可在系統層級之上發生。在此情形中,本發明 統追蹤實體裝運而非邏輯裝運。 本發明系統可識別該運輸載具且指定如何與其通訊。 發明系統因此可回應問題如:“告訴我關於運往舊金山 受污染肉品之駕駛的姓名以及行動電話號碼。” 運輸-路線 該“運輸路線”資訊乃是關於像是船或卡車等運輸 具預期之地理路徑的資訊。其可為一連串的路線_ (way-point),如城市、公路交叉口、獨立公路或街道名賴 緯度及經度等等。可明確地提供該傳輸路線。舉例來說 位 5 運 報 例 往 可 或 這 系 本 的 載 點 66 1310919 可手動輸入該傳輸路線。另外容後所述亦可計算或推斷 傳輸路線。一傳輸路線直接地適用於一傳輸載具,而僅 特定的裝運中為非直接地適用。 配置訊息 一配置訊息係指一特定項目在一指定的時間被感應 為用於一特定配置之一種批次的部分,例如移動至其他 存位置、裝運至一客戶等等。該配置訊息可能為這樣的 式: 時間戳記,批次_ID,項目_ID. 這個簡潔的訊息將一項目、一讀取器以及一種區域ERP 統去。道的裝運編號結合在一起。相同的配置訊息之重 傳送具備高度有利的特性,因為其不會改變追蹤系統的 態。 標記記憶體 所敘述的系統物件以及功能只與追蹤標記項目有關。 而,特定的應用程式在標記被感應時可能需要在某一階 寫入資料至一標記項目。本發明系統可在任何位置寫入 讀取這樣的標記資料。 本發明系統可提供大規模的事件報告。舉例來說,當 定里程碑事件發生時,本發明系統可報告其他的應用 式。舉例來說,當一裝運到達一客戶時,本發明系統可 該 在 且 儲 形 系 複 狀 缺 層 及 特 程 傳 67 1310919 送一訊息,因而觸發清單。 3.2跨企業可見度 本發明系統可使位於一供應鏈中的項目具有跨企業 見度。本發明系統可接收、儲存並創造關於項目的可見 置資訊,例如當項目在一單一企業内移動或跨越多個企 移動時該項目的位置。此外,本發明系統可接收、儲存 創造可見的相關性資訊,該相關性使項目與客戶訂單、 運文件以及其他商業交易相聯繫。本發明系統可自接收 何供應鏈中的參與者或企業接收相關性或配置資訊且可 使該資訊可為其他供應鏈中的參與者或企業看見。如第 圖所示,本發明系統可大規模地追蹤項目並提供存取追 資訊。舉例來說,其基礎架構可追蹤項目,其位於許多 同情境中,如工廠、倉庫、零售商店以及遍及各國或世 的住家。 控制可見度 在一實施中,本發明系統可提供控制的可見度。換 之,只有使一種項目追蹤資訊的子集合可被供應鏈中的 定參與者看見。如第2 8圖所示,本發明系統可接收授權 訊,其指出關於項目之各種特性的授權設定值。本發明 統可使用該授權資訊以決定使何種特性給哪些企業看見 舉例來說,第2 8圖中所示的授權模型指出該項目的目標 可 配 業 並 裝 任 以 26 蹤 不 界 言 特 資 系 〇 特 68 1310919 性應被寄送者看見,但不應被製造者看見。控制的可見度 將會在以下 控制的存取追蹤.項目”標題中做更詳細的討 論。 世界模型結構 第27圖說明一多企業共享的世界模型(WM)結構。該世 界模型疋一種記錄並維護.一描述的結構,該描述是關於由 一 ITS追蹤之項目的關係、狀態以及歷史。可實施該世界 模型為一雙層結構:―較高層的上層WM2710,其持續地 追縱位於一特定企業内的項目;以及一較低層的區域 WM2720 ’其持續地追蹤位於該特定企業内一實體位置上 的項目。該區域VM可容納於一共享ITS1403内(如第14 圖所示)而該上層WM可容納於一共享ITS1404内。透過一 網路連接1405,用於一企業的一上層WM可與其他企業的 上層WM或該企業中其他部門或層級的上層WM通訊。 第2 7圖描述一聯合或對等合作安排,其中每個企業直 接分享資訊給其他企業。本發明系統也可支援其他種類的 安排。舉例來說’第2 9圖顯示一階層體系或組合安排,其 中每個企業的上層WM2920提供資訊給中央WM2910。也 可選擇將聯合及階層體系安排結合。舉例來說,上層 WMs2710其中之一在聯合模型中也可代表該中央 WM 29)0為一上層WMs2920的結合。 在第27圖中,每個企業被描述為具有一單一 WM2710, 69 1310919 然而在某些情況中,例如為了暢銷目的,可實施該上層 WM2710為上層WMs3010的一叢集,如第30圖所示。每 個上層WM3010維護至區域WMs2720、其他企業的其餘· 上層WMS2710以及高層商業應用程式如ERP系統的連線。 3.3資料通訊及世界模型間的緊密結合 下節描述一種用於橫跨一分散架構之多個節點以聯繁 資料的系統及方法,該分散架構例如第29圖中所插述的聯 合架構。 本方法提供區域WMs2720與上層WMS2710間的雙向 傳輸。上層WMs2710可報告其他WMs有關追蹤中的項目 變化(例如對於受污染的肉類的收回通知或定價格變化)。 相反地,區域WMs2720可向上層WMs2710報告項目配置 變化(例如項目建立、移動或終止)。 對於每個項目,指定至少一上層 WM27 1 0為該項目的 負責WM。一般該負責的WM為企業的上層WM,而項目 在該企業被建立(例如製造者)。由任何區域WM2720透過 該聯合所接收到關於該項目的任何資訊被報告給負責的 WM。在此方式中,該負責的WM維護一完整的項目歷史。 可複製該負責的WM以改善資料復原。舉例來說,亦可指 定一第二WM27 1 0為一副則該項目的的WM,任何收到關 於該項目的資訊被送至兩個負責的WMs。 一旦任何“重要的商業”變化已被報告至負責的 70 1310919 WM,其他非負責而握有關於該項目之資訊的WMs便可自 由的清除該資訊。因此,任何獨立的區域WM2720可由一 空白WM重新啟動。然而,在重新啟動前還沒有被報告的 改變將會遺失,除非這些改變在重新啟動前已被儲存在區 域儲存區中。Timestamp, batch_ID (eg 96bit ePC), project ID, use batches to support a collation function for batches that are not batched before the project is read. For example, an assembly line can have a series of sequential items and a series of boxes. The reader reads the mark on each item and decides, for example, to place the item in box 1 or 2 or 3. Each box can be 63 1310919 symbolizing for example different configurations. The reader places a different batch -1D on each box, and each item is connected to the batch-ID of the box placed somewhere. A basic inch design can include a reader with a unique ID and a shipment that also has a unique ID. The reader is coupled to the shipment to produce a particular batch that has a unique ID. Multiple batches from the same or different readers can be combined to the same shipment. The necessary basic shipments may include a unique ID, a regional shipment number (e.g., a number for an area ERP), a cargo destination, a target delivery date, and a target delivery time. The combination of items each with a batch rather than a reader allows the information to be safely repeated without confusion. For example, if the configuration information is re-delivered, but because of a system error or reopening, the status of the system of the present invention will not change if batch_item pairing is used instead of reader item pairing. Configuration Actions A configuration action describes changes in the state of the object and project hierarchy associated with or associated with a marked item. Configuration actions include, for example, setting up a project or first introducing a project for tracking, location change, inventory confirmation, shipping, loading, unloading, and ending tracking. This configuration action "Build Project" records the initial properties of the project, such as the manufacturer, type, manufacturing schedule, and location. This action can include initializing the tag with some of the provided material. It usually contains an indication of where the project was initially 64 1310919. The configuration action "location change" means that the item is or has been moved to a new given location. “Stock Confirmation” means that the item is recorded when it is sensed at a storage location. The configuration action "shipping" means that the item is designated as part of a shipment. The shipping number known to the regional ERP can be given. The configuration action "loading" refers to sensing the item when loading a particular transport vehicle. The truck or other shipping ID can be combined to a shipping ID. The configuration action "unload" means that the item is sensed when a particular transport vehicle is unloaded. The vehicle ID can be combined to a shipping ID. The configuration action "Undo" is an action that effectively cancels any past configuration of the same item and the same batch. It is often necessary to revoke past configurations. For example, revocation occurs when too many items are loaded. This action is not idempotent. The configuration action "End Tracking" means that the tracking system does not expect to see the item again. This action can occur like retail sales or when the project package is opened and the box is recycled. The system of the present invention may archive the project data for future warranty or historical purposes. There are many possible configurations. The flexible configuration specifies that it is better. Shipment A shipment identifies a package, typically in the form of a project-type quantity table. A shipment also defines the move to a target 65 1310919 in these project type plans. The target can be a customer with an address, or another with the same company. The tracking system determines the location of the address, such as latitude and shoulder or receives this information as part of the shipping description. Regional ERP system. The shipment should be made. The tracking system captures the information and matches the specific item to the general item-type in the shipping schedule and inconsistencies. One or more of the billing shipments can be linked to a particular transport vehicle. In other words, several different parts of the shipment are sent to the same address and some are sent to different addresses and can still be loaded onto the same truck. The system of the invention confirms that the truck is loaded correctly. In addition, the system of the present invention can track the truck's estimated position and respond to inquiries regarding the location of the cargo. A particular logical shipment can in fact be spread across several transport trucks. The assignment can occur at the system level. In this case, the present invention tracks physical shipments rather than logical shipments. The system of the present invention can identify the transport vehicle and specify how to communicate with it. The invention system can therefore respond to questions such as: "Tell me the name and mobile phone number of the driving to the contaminated meat in San Francisco." Transportation - Route The "transportation" information is about the expected transportation of a ship or truck. Information about geographic paths. It can be a series of routes (way-points), such as cities, highway intersections, independent roads or street names, latitude and longitude, and so on. This transmission route can be explicitly provided. For example, the transfer method can be manually entered by the bit 5 report or the load point 66 1310919. The transmission route can also be calculated or inferred as described later. A transmission route is directly applicable to a transmission vehicle and is not directly applicable in a particular shipment. Configuration Messages A configuration message is a portion of a particular item that is sensed at a specified time as a batch for a particular configuration, such as moving to another location, shipping to a customer, and so on. The configuration message might look like this: Timestamp, Batch_ID, Item_ID. This simple message will be a project, a reader and a regional ERP. The shipping numbers of the roads are combined. The same configuration message is retransmitted with highly advantageous features because it does not change the state of the tracking system. Marking Memory The system objects and functions described are only relevant to the tracking mark item. However, a particular application may need to write data to a tagged item at a certain level when the tag is sensed. The system of the present invention can be written to read such tag data at any location. The system of the present invention can provide large-scale event reporting. For example, the system of the present invention can report other applications when a milestone event occurs. For example, when a shipment arrives at a customer, the system of the present invention can send a message to and from the replica system and trigger the list. 3.2 Cross-enterprise visibility The system of the present invention enables projects located in a supply chain to have cross-enterprise visibility. The system of the present invention can receive, store, and create visibility information about a project, such as the location of the project as it moves within a single enterprise or across multiple businesses. In addition, the system of the present invention can receive and store visual correlation information that correlates projects with customer orders, shipping documents, and other commercial transactions. The system of the present invention can receive correlation or configuration information from participants or businesses in the receiving supply chain and can make the information visible to participants or businesses in other supply chains. As shown in the figure, the system of the present invention can track items on a large scale and provide access tracking information. For example, its infrastructure tracks projects, which are located in many scenarios, such as factories, warehouses, retail stores, and homes around the world. Controlling Visibility In one implementation, the system of the present invention provides visibility of control. Instead, only a subset of the project tracking information can be seen by the participants in the supply chain. As shown in Figure 28, the system of the present invention can receive an authorization message that indicates an authorized setting for various characteristics of the item. The present invention can use the authorization information to determine which characteristics to see for which companies, for example, the authorization model shown in Figure 28 indicates that the project's objectives can be matched and loaded with 26 undecided 〇特68 1310919 Sex should be seen by the sender, but should not be seen by the manufacturer. The visibility of the control will be discussed in more detail in the following controlled access tracking. Project title. Figure 27 of the world model structure illustrates a multi-enterprise shared world model (WM) structure. The world model is a record and maintained A description of the structure, relating to the relationship, state, and history of an item tracked by an ITS. The world model can be implemented as a two-tier structure: the upper layer of the upper layer, the WM2710, which continues to track down a particular enterprise. Within the project; and a lower-level area WM2720' that continuously tracks items located at a physical location within the particular enterprise. The area VM can be housed in a shared ITS 1403 (as shown in Figure 14) and the upper layer The WM can be housed in a shared ITS 1404. An upper layer WM for an enterprise can communicate with the upper WM of other enterprises or the upper WM of other departments or levels in the enterprise through a network connection 1405. Figure 7 7 depicts a Joint or peer-to-peer cooperative arrangements in which each company directly shares information with other companies. The system of the invention can also support other types of arrangements. For example, '2 9 Display a hierarchy or combination arrangement, in which the upper WM2920 of each enterprise provides information to the central WM2910. It is also possible to combine the joint and hierarchical arrangements. For example, one of the upper WMs2710 can also represent the central in the joint model. WM 29)0 is a combination of an upper layer WMs2920. In Figure 27, each enterprise is described as having a single WM2710, 69 1310919. However, in some cases, for example for bestseller purposes, the upper layer WM2710 can be implemented as the upper layer WMs3010 A cluster is shown in Figure 30. Each upper WM3010 maintains the connection to the regional WMs2720, the rest of the other companies, the upper WMS2710, and the high-level business applications such as the ERP system. 3.3 Data communication and tight integration between world models A system and method for interleaving data across a plurality of nodes of a decentralized architecture, such as the joint architecture interspersed in Figure 29. The method provides bidirectional transmission between the regional WMs 2720 and the upper WMS 2710. The upper WMs2710 can report changes in other WMs related to tracking (eg for the recovery of contaminated meat) Conversely, the regional WMs 2720 can report project configuration changes (such as project creation, movement, or termination) to the upper WMs 2710. For each project, specify at least one upper layer WM27 1 0 for the project's responsible WM. The responsible WM is the upper WM of the enterprise, and the project is established at the enterprise (eg, the manufacturer). Any information received by the WM2720 through the federation about the project is reported to the responsible WM. The responsible WM maintains a complete project history. The responsible WM can be copied to improve data recovery. For example, a second WM27 10 may also be designated as a WM of the item, and any information received about the item is sent to the two responsible WMs. Once any “important business” changes have been reported to the responsible 70 1310919 WM, other WMs who are not responsible and hold information about the project can freely clear the information. Therefore, any separate area WM2720 can be restarted by a blank WM. However, changes that have not been reported before the restart will be lost unless they have been stored in the regional storage area before being restarted.

為資料安排路徑至負責的WM 一區域 WM2720接收多個標記讀取資料的實體,每次 包含當一項目在區域節點被偵測到時,自一標記讀取的資 訊,該標記附著於一項目上。該標記讀取資料的多個實體 可全體地包含自標記讀取的資訊,該標記附著於一批裝運 項目中的多個項目。在一供應鏈中的裝運通常包含一個或 多個項目階層容納於該裝運中(例如一裝運可包含具有單 獨項目的貨盤)。因此,在某些情況中,該區域 WM 2720 可接收自一裝運標記讀取的資料,且關於容納在裝運中的 項目(例如貨盤、箱子以及單獨項目),該區域WM2720变 可接收自其標記讀取的資料。 對於每個項目,該區域WM2 720將標記讀取資料向對 該項目負責的WM報告。為了決定對該項目負責的WM, 該區域WM2720可諮詢一對應表,該對應表維護項目以及 指定負責節點間的結合。可使用所有或任何部分的項目 UID詢問該對應表。 每個位.於一裝運中的項目可對應至一指定的負責 WM。屬於不同產品種類的項目可對應至不同的指定負責 71 1310919 WMs。對於每個項目,該指定負責WM在所有節點 是相同的,也可每個節點有所不同。換句話說,每 可維持其各自的對應表而在每個對應表内的結合可 點有所不同。 舉例來說,在一單一企業内,橾作規則可決定所 的商業項目移動向該企業的一上層WM報告。該上 可為單一 WM或一叢集。一旦該移動已向該上層 告,可設定該上層 WM向其他企業外部的WMs報 目移動。舉例來說,一零售商可向製造者報告項目 實現更有效的供應鏈橾作。因此,當一小零件在一 層被售出時,該區域WM可決定負責的WM使其成 企業内的一上層WM。然而,在上層WM節點,該上 可決定關於同一小零件之負責的WM作為一另外企 層WM。在一範例情況中,該遠端WM可回應該特 件的製造者。在另一例中,該遠瑞WM可能代表所 件製造者的一種商業結合等等。 在某些情況中,一節點可設定作為他節點之轉送 路徑的媒介。舉例來說,一製造者可自企業外部識 於所有更新的單一外部可存取節點。一旦該更新在 被接收,該節點可諮詢其自己内部的負責WM的對 依據該產品種類分散該更新。這樣可以一種企業外 看見的方式分散計算及資料儲存負荷。 下節描述一種協定的實施以在WMs間交換狀態 上可以 個節點 依各節 有重要 層WM WM報 告某項 移動以 零售階 為同一 層WM 業的上 定小零 有小零 並安排 別一用 此節點 應表並 部無法 資訊。 72 1310919 此實施使用一狀態交換訊息以在1WMs間交換 該訊息參數包含該項目的UID、該項目現在的 態最後改變時的時間戳記。狀態交換的接收者 訊息,該訊息指出目前已去。狀態以及時間戰 交換訊息在確認被接收之前足憤慨的(resent)。 項目建立 當一項目在一製造者(企業A)的實體位置 時,該用於實體位置(世界模型WM—AL1)的區 一“項目之建立”配置動作。WM_AU隨後建 示例如該項目的一物件表示,並且指定該物件 的、骯髒的”狀態。 一物件的狀態可使用旗標的組合來指定 “動態的”、“延遲的”、“懸m “骯髒的 的”係指該物件表示其為最新的版本。“延 些其他世界模型具有唯—動態版本。“懸君 的指定,用於系統取回&amp; # _ “ μ正確的指定。“骯髒 最後向負責的WM報告後,肖狀態已經以- 方式改變。 WM A11 隨後向鱼主, _ 说π負責的 WM(WM_AP)報 立〇這個報告可採用狀能^β ή4 4狀態父換訊息的格式。 &quot;WMAP 建立一被;„ „ 一 散知疋為 延遲的 區域拍 隨後為了 WM AL1技# . 一 將該物件放在之何處使用 狀態資料。 狀態以及狀 回應一確認 記。該狀態 首先被建立 域WM收到 立一邏輯表 處於“動態 該旗標包括 旗標。“動態 的”係指某 為一暫時 ”係指自從 業上重大的 告該項目建 7 件。WM_AP (wheleused) 73 1310919 的名單中。該何處使用的名單為一對應,其持續的追蹤位 於何者區域WM中的何者物件。 WM —AP 隨後送出一狀態-交換-及認可訊息至 WM — AL1 〇此狀態交換—及認可訊息也可包含母公司想要與 新建立項目結合的資訊。在接收認可時,WM_AL1自該物 件移除該“骯髒的”指定。 隨後的企業重大變化 一旦一項目被建立,隨後的企業重大變化也被報告給負 責的 WM。WM — AL1改變物件的狀態至“動態的、骯髒 的”,傳送一狀態交換訊息至負責的WM(WM —AP),並在 自 WM — AP收到該變化已被紀錄的認可後清除該“骯髒 的”旗標。 移出該位置 當WM — AL1偵測該項目位於該位置的出口時,WM — AL1 將此狀況視為一企業重大事件並向負責的 WM報告。 WM_AL1設定該物件狀態至“延遲的、骯髒的”並傳送一 狀態交換訊息至WM_AP。WM_AP更新該區域物件為“延 遲的”並傳送一認可至WM — AL1。WM — AL1在收到該認可 後清除該骯髒的旗標。 匯總及通訊目標資訊 74 1310919 在某些情況中,該項目的目標是已知的。該目標可為 何在相同企業内的位置或為其他企業。舉例來說,與該 目結合的企業文件可能包含目標資訊。企業文件資訊藉 與像是ERP (企業資源規劃)這類傳統企業軟體系統通訊 獲得。舉例來說,企業資訊可與特定裝運有關,並由帶 裝運的項目標記之階層體系及傳統系統所了解的訂單編 所表示。機構、位置、裝運住址皆與唯一 UID s相結合 該唯一 UIDs與指定給實體項目的UIDs相似。為了接收 運的進一步通知的目標WM可在裝運記錄的領域中被明 地指定,或可更佳地使用與用來替一實體項目找出負責 WM相同的機制加以計算。 舉例來說,該負責的 WM路徑安排及更新機制可依 以下方式用來指揮裝運階層體系的進一步通矢。可建立 裝運目標記錄伴隨一 UID,其負責的WM計算出做為預 接收此裝運的 WM。一旦此裝運實體地匯總且以經知道 裝運的特定項目標記,此標記階層體系可被記錄為一種 運目標記錄的改變。任何對此記錄的改變可自動地與負 的WM通訊,其已被設定作為實際目標WM。一旦該實 裝運到達該WM,其可擁有所有的標記資訊以完全地確 確實的裝運内容。 在其他情形中,本發明系統内並不矢。道該貨物的 標。這會造成難以與ERP系統整合的結果。這兩種惰形 全體系統皆可處理。 任 項 由 而 有 號 裝 確 的 眧 期 該 裝 責 體 認 g 該 75 1310919 移動至相同企業中的其他位置(位置AL2) 如果知道目標,WM_AP為了 WM —AL2將該物件放在 WM何處使用名單中並傳送一狀態交換訊息至WM —AL2。 當該項目到達 AL2位置時,WM_AL2改變該物件的狀態 至“動態的、骯髒的”並傳送一狀態改變訊息至WM — AP。 WM_AP更新該區域物件並回應一狀態-交換及-認可訊息。 在某些情形中,無法預先知道該目標。當該項目到達 該目標位置AL2時,WM — AL2建立一帶有&quot;延遲的,骯髒 的”狀態的區域物件並傳送一狀態交換訊息至WM_AP 。 WM_AP更新其區域物件,並為WM_AL2移動其區域物件 至“何處使用”名單並回應一狀態_交換_及認可訊息至 WM_AL 1〇 移動至其他企業(位置BL1) 如果已知該目標,WM — AP傳送一狀態交換訊息至該目 標位置的上層 WM(WM_BP)。WM — BP回應一帶有狀態-交 換-及-認可訊息的認可至 WM — AP且亦傳送一狀態交換訊 息至WM_BL1。WM_BL1建立一 “延遲的”物件且將其放在 一進入名單中。WM_BL1回應一狀態交換_及—認可訊息至 WM_BP。 一旦該項目到達位置BL1,WM — BL1改變該物件的狀態 至“動態的、骯髒的”並傳送一狀態交換訊息至WM_BP。 76 1310919 WM_BP更新該區域物件並回應一狀態-交換-及_認可訊 息。WM_BP隨後設立該骯髒的旗標並傳送狀態交換訊息至 負責的WM,其名為WM_AP。WM_AP更新其區域物件以 及何處使用名單並回應一狀態_交換-及-認可訊息至 WM_BP。 如果事先不知道該目標而該項目到達BL1,WM_BL1建 立一“延遲的、動態的、骯髒的”物件並傳送一狀態交換訊 息至WM_BP。WM_BP建立一“延遲的、動態的、骯髒的” 物件並為了 WM_BL1將其放置在何處使用名單中且回應一 狀態_交換—及認可訊息至WM_BL1 〇 WM — BP隨後傳送一 狀態交換訊息至負責的WM,其名為WM — AP。WM — AP更 新其區域物件以及何處使用名單並回應一狀態-交換-及-認可訊息至WM—BP。 降低WMs間的資料通訊量 在一替代的實施中,介於一特定區域 WM以及一特定 負責的WM之間,可調整該二WMs使得不是所有在一裝 運中的項目或項目階層體系都需要向負責的WM報告。要 報告哪些項目可依不同的WM對之間有所不同。 可提供定義項目階層體系的資訊給區域WM以及負責 的WM。對於每個在區域節點上偵測到的項目,該區域WM 可對照階層體系資訊確認每個項目。然而,當報告負責的 WM時,該區域WM僅能報告在階層體系中一特定層級的 77 1310919 項目(例如最高層級)並附帶一額外的關於所有在此 系下的項目均已被確認的指示。 在訊息遺失或副本傳送時的可靠度 由於狀態交換訊息會自動重送直到收到任可為』 “懸宕的”或“骯髒的”狀態乃是將“動態的”或 的”狀態可靠地轉換。在某些情形中,一副本傳送 如一 WM自永久儲存重新啟動後發生。因為狀態改 攜帶一時間戳記,故其只有在延遲實體較進來的更 時才會發生作用。 傳統的機制如NTP(網路時間協定)或GPS時鐘 用來同步網路上的時鐘。然而,本發明系統可在沒 時鐘同步的情況下操作。 本發明系統的冷重心啟動 本發明系統可自空白的區域WMs重建。任何隨 項目的偵測促引起一 “懸宕的”物件建立。一旦已 有的項目,該WM將會結束。 定期的清理 該區域WMs可定期的要求更新”懸宕的”、” 的”物件或是已一段時間未被更新的物件。已一段 未被參照的物件可被清除至空間記憶體。該負責的 清除或移開已一段時間尚未被參照的長期儲存物件 階層體 :,因此 “延遲 可於例 變訊息 新古老 接收可 有向度 後對一 看見所 ”骯髒 時間尚 WM可 78 1310919 3.4項目方案 下節說明項目方案 當建立一項目,以下的方案可發生。該項目被製造隨後 與一特定項目ID結合。隨著該項目自製造業移動,其進 入位於第一讀取器的追蹤系統。其步驟為:(1)建立配置指 出“新項目”以及所有想要的項目屬性:以及(2)建立一批 次ID結合讀取器及配置。本發明系統看見一連串的配置 訊息,該配置訊息被處理以建立關於新項目的系統資料。 當該項目被傳遞至一倉庫中,以下的方案可發生。在 傳遞之前,該倉庫工作人員指示本發明系統帶有該項目的 計畫行動。 如果該讀取器位於一固定的位置且關於預期的位置十 分明確一例如一讀取器位於一小儲藏室的門上或在進入一 儲藏室的輸送帶上一所有此資訊可不出現。此步驟為:(1) 建立配置指出“配置—位置改變”以及位置。(2)建立一批次 ID結合讀取器及配置。本發明系統看見一連串顯示位置變 化的配置訊息。 當裝運項目時下列方案可以發生。·一般該區域FRP或 物流系統具有一入口 ,其說明項目種類的一特定名單以及 應被裝運至位於一給定目標之特定客戶的數量。該客戶可 能為自己。本發明系統可提供下列識別以及確認能力:(1) 識別將被裝運的特定項目。(2)確認事實上與裝運有關的所 有項目種類以及指定數量。舉例來說,對照内部ERP系統 79 1310919 確認裝運以及包裝過程。(3)識別所有打算在一特定運 具上出發的裝運,例如該裝運將裝載至一特定卡車上 確認所有的項目確實地裝載至正確的運輸載具上。 在傳遞過程中,本發明系統報告該運輸載具預計的或 的位置。在更複雜的方案中,貨物在裝運中可被轉售 變方向。本發明系統確認正確的項目在每個目標地 載。本發明系統可選擇性地允許RFID在目標地的運 應以證明傳遞及觸發清單。本發明系統可為了動態裝 擇性地擷取傳遞時間並且更新内部傳遞時間估計。 使用這些基本類型,自儲藏到裝運間可執行以下步 區域ERP系統報告一計晝裝運至一區域ITS 〇儲藏室 使用__系統應用程式以:自名單選擇裝運ID;選擇裝 配置種類:識別區域讀取器ID ;並製造唯一批次ID 人員使用既有的程序以自儲藏室中取出項目並通過 器。該讀取器以下列格式傳送一連串的配置訊息至本 系統:Arranging a path for the data to the responsible WM area WM2720 receives multiple tags to read the data entity, each time containing an item read from a tag when the item is detected at the area node, the tag is attached to an item on. The plurality of entities that the tag reads the material may collectively contain information read from the tag that is attached to a plurality of items in a shipment. Shipments in a supply chain typically include one or more item levels housed in the shipment (e.g., a shipment can contain pallets with separate items). Thus, in some cases, the area WM 2720 can receive material read from a shipping mark, and with respect to items housed in the shipment (eg, pallets, boxes, and individual items), the area WM2720 can be received from Mark the data read. For each project, the region WM2 720 will mark the read data to the WM report responsible for the project. In order to determine the WM responsible for the project, the WM2720 in the region can consult a correspondence table, which maintains the project and the combination of the designated responsible nodes. The correspondence table can be queried using all or any part of the project UID. Each item in a shipment can correspond to a designated responsible WM. Projects belonging to different product categories can be assigned to different designated 71 1310919 WMs. For each project, the designation is responsible for WM being the same at all nodes, or different for each node. In other words, the combination in each correspondence table can be different for each of its respective correspondence tables. For example, in a single enterprise, a production rule can determine that a business item moves to an upper-level WM report for that enterprise. This can be a single WM or a cluster. Once the move has been directed to the upper layer, the upper WM can be set to move to the WMs report outside the other enterprise. For example, a retailer can report a project to a manufacturer to achieve a more efficient supply chain operation. Thus, when a small part is sold on one floor, the area WM can determine the responsible WM to be an upper WM within the enterprise. However, at the upper WM node, the responsible WM for the same small part can be determined as an additional layer WM. In an exemplary case, the remote WM can respond to the manufacturer of the particular component. In another example, the remote WM may represent a commercial combination of the manufacturer and the like. In some cases, a node can be set as the medium for the forwarding path of its nodes. For example, a manufacturer can recognize all updated single externally accessible nodes from outside the enterprise. Once the update is received, the node can consult its own internal responsible WM pair to disperse the update based on the product category. This allows for a decentralized computing and data storage load in a way that is seen outside the enterprise. The following section describes the implementation of a protocol to exchange status between WMs. Nodes can have important layers in each section. WM WM reports a certain move. The retail order is the same level. The WM industry has a small zero and a small zero and arranges another one. This node should be inconsistent with the table. 72 1310919 This implementation uses a state exchange message to exchange between 1WMs. The message parameter contains the UID of the item and the timestamp when the current state of the item was last changed. The status exchange recipient message, which indicates that it has been gone. The status and time war exchange messages are resent before the acknowledgment is received. Project Establishment When a project is in the physical location of the manufacturer (enterprise A), the zone-"project establishment" configuration action for the physical location (world model WM-AL1). WM_AU then builds an example of an object representation of the item and specifies the dirty state of the item. The state of an object can be specified using a combination of flags to specify "dynamic", "delayed", "hanging m" "Dirty" means that the object indicates that it is the latest version. "Extensions of other world models have a only-dynamic version." The designation of the hang-jun is used for system retrieval &amp;# _ "μ correct designation. "Dirty finally to the responsible WM report, the Xiao state has been - in the way change. WM A11 then reports to the fisherman, _ said π responsible WM (WM_AP) that this report can be formatted with the message type ^^ ή4 4 state parent. &quot;WMAP establishes a; „ „ 一 疋 疋 延迟 延迟 延迟 延迟 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后 随后The status and status respond to a confirmation. This state is first established. The domain WM receives the logical table. It is “dynamic. The flag includes the flag. “Dynamic” means that it is a temporary.” This means that the project has been successfully constructed. WM_AP (wheleused) 73 1310919 in the list. The list of where to use is a correspondence that continuously tracks which object in the WM. The WM-AP then sends a status-exchange-and-acceptance message to the WM-AL1 〇This status exchange—and the approval message can also contain information that the parent company wants to combine with the newly created project. Upon receiving the approval, WM_AL1 removes the "dirty" designation from the object. Subsequent major changes in the business Once a project is established, subsequent major corporate changes are also reported to the responsible WM. WM — AL1 changes the state of the object to “Dynamic, Dirty”, transmits a status exchange message to the responsible WM (WM – AP), and clears the WM – AP after receiving the approval that the change has been recorded. "Dirty" flag. Moving out of the location When WM-AL1 detects that the project is at the exit of the location, WM-AL1 treats the condition as a corporate milestone and reports it to the responsible WM. WM_AL1 sets the object status to "Delayed, Dirty" and transmits a status exchange message to WM_AP. WM_AP updates the area object to "delayed" and transmits an acknowledgement to WM - AL1. WM — AL1 clears the dirty flag after receiving the approval. Summary and Communication Target Information 74 1310919 In some cases, the objectives of the project are known. The goal can be for a location within the same enterprise or for another business. For example, an enterprise document combined with this project may contain target information. Corporate document information is obtained through communication with traditional enterprise software systems such as ERP (Enterprise Resource Planning). For example, corporate information can be associated with a specific shipment and is represented by a hierarchy of items marked by the shipment and an order record known to the traditional system. Institution, location, and shipping address are combined with unique UIDs. This unique UIDs are similar to the UIDs assigned to an entity project. The target WM for further notification of receipt may be explicitly specified in the field of shipping records, or may be better calculated using the same mechanism used to find the responsible WM for an entity project. For example, the responsible WM routing and updating mechanism can be used to direct further navigation of the shipping hierarchy in the following manner. A shipment target record can be created with a UID, and the responsible WM calculates the WM as the pre-received shipment. Once the shipment is physically aggregated and marked with a particular item known to be shipped, this mark hierarchy can be recorded as a change in the record of the target. Any changes to this record can be automatically communicated with the negative WM, which has been set as the actual target WM. Once the actual shipment arrives at the WM, it can have all the tag information to fully confirm the shipping content. In other cases, the system of the present invention is not targeted. The standard of the goods. This can result in difficulties in integrating with the ERP system. Both of these two inert systems can be handled. If the target is known, WM_AP places the object in WM for WM-AL2. If the target is known, WM_AP puts the object in WM for WM-AL2. A status exchange message is sent to the list to WM-AL2. When the item reaches the AL2 position, WM_AL2 changes the state of the object to "dynamic, dirty" and transmits a status change message to the WM-AP. WM_AP updates the area object and responds to a status-exchange and-approval message. In some cases, the target cannot be known in advance. When the project reaches the target location AL2, WM-AL2 creates a zone object with a &quot;delayed, dirty&quot; state and transmits a state exchange message to WM_AP. WM_AP updates its zone object and moves its zone for WM_AL2 The object goes to the "where to use" list and responds to a status_exchange_and approval message to WM_AL 1〇 moves to another enterprise (location BL1). If the target is known, the WM-AP transmits a status exchange message to the upper level of the target location. WM (WM_BP). WM - BP responds with a status-switch-and-acknowledgment message to the WM-AP and also transmits a status exchange message to WM_BL1. WM_BL1 creates a "delayed" object and places it in one In the list, WM_BL1 responds to a status exchange _ and - acknowledges the message to WM_BP. Once the item arrives at position BL1, WM - BL1 changes the state of the object to "dynamic, dirty" and transmits a status exchange message to WM_BP. 1310919 WM_BP updates the object in the area and responds to a status-exchange-and__recognition message. WM_BP then sets up the dirty flag and sends a status exchange message to the responsible W. M, which is called WM_AP. WM_AP updates its regional object and where to use the list and responds to a status_exchange-and-approval message to WM_BP. If the item does not know the target beforehand and the item reaches BL1, WM_BL1 establishes a "delayed, Dynamic, dirty "objects" and send a state exchange message to WM_BP. WM_BP creates a "delayed, dynamic, dirty" object and places it in the use list for WM_BL1 and responds to a state_exchange - and the approval message to WM_BL1 〇 WM - BP then transmits a status exchange message to the responsible WM, which is called WM - AP. WM - AP updates its regional objects and where to use the list and responds to a status - exchange - and - approval Message to WM-BP. Reducing data traffic between WMs In an alternative implementation, between a specific area WM and a specific responsible WM, the two WMs can be adjusted so that not all items in a shipment or The project hierarchy needs to report to the responsible WM. It is necessary to report which projects can be different between different WM pairs. Information on defining the project hierarchy can be provided to the regional WM. Responsible WM. For each item detected on the regional node, the area WM can confirm each item against the hierarchy information. However, when reporting the responsible WM, the area WM can only report in the hierarchy. A specific level of 77 1310919 items (such as the highest level) with an additional indication that all items under this system have been confirmed. The reliability of the message loss or copy transmission is automatically resent due to the status exchange message until Receiving a "suspended" or "dirty" state is a reliable conversion of the "dynamic" or "state". In some cases, a copy transfer occurs as a WM restarts after permanent storage. Because the state changes to carry a timestamp, it only works when the delaying entity comes in more time. Traditional mechanisms such as NTP (Network Time Protocol) or GPS clocks are used to synchronize the clocks on the network. However, the system of the present invention can operate without clock synchronization. Cold Center of Gravity Activation of the System of the Invention The system of the present invention can be reconstructed from a blank area WMs. Any detection with the project causes a "suspended" object to be created. Once there is an existing project, the WM will end. Regular cleaning The WMs in the area can be regularly requested to update “hanging”, “things” or objects that have not been updated for a while. An item that has not been referenced can be erased to the spatial memory. It is responsible for the removal or removal of the long-term storage object hierarchy that has not been referenced for a while: therefore, "the delay can be seen in the case of a new change in the old-fashioned information." Dirty time is still WM 78 1310919 3.4 Project plan The following section describes the project plan. When a project is established, the following options can occur. The project is manufactured and then combined with a specific project ID. As the project moves from manufacturing, it enters the tracking system at the first reader. The steps are: (1) establishing a configuration indicating "new project" and all desired project attributes: and (2) establishing a batch of secondary ID combined readers and configurations. The system of the present invention sees a series of configuration messages that are processed to establish system data about new projects. When the project is delivered to a warehouse, the following scenario can occur. Prior to delivery, the warehouse staff instructed the system of the present invention to carry out the project's planning actions. If the reader is in a fixed position and it is clear about the intended position, for example, if the reader is located on the door of a small storage compartment or on a conveyor that enters a storage compartment, this information may not appear. This step is: (1) Establish the configuration to indicate "configuration - location change" and location. (2) Establish a batch ID combined with the reader and configuration. The system of the present invention sees a series of configuration messages that display positional changes. The following scenarios can occur when shipping a project. • Typically the regional FRP or logistics system has an entry that describes a specific list of project categories and the number of specific customers that should be shipped to a given target. This customer may be for himself. The system of the present invention provides the following identification and validation capabilities: (1) Identifying specific items to be shipped. (2) Confirm the type of all items and the specified quantity that are in fact related to the shipment. For example, check the shipping and packaging process against the internal ERP system 79 1310919. (3) Identify all shipments that are intended to be departed on a particular vehicle, for example, the shipment will be loaded onto a particular truck to confirm that all items are indeed loaded onto the correct transport vehicle. During the transfer, the system of the present invention reports the predicted or location of the transport vehicle. In more complex scenarios, the goods can be resold in the direction of shipment. The system of the present invention confirms that the correct project is at each target location. The system of the present invention selectively allows the operation of the RFID at the destination to prove the delivery and trigger list. The system of the present invention can dynamically retrieve the delivery time and update the internal delivery time estimate. Using these basic types, the following steps can be performed from the storage to the shipping area. The ERP system reports a shipment to a regional ITS storage room using the __system application to: select the shipping ID from the list; select the configuration type: identification area Reader ID; and manufacture unique batch ID personnel use existing programs to remove items from the storage compartment and pass the device. The reader transmits a series of configuration messages to the system in the following format:

時間戮記批次ID項目ID 該人員在系統應用程式上指出批次完成。本發明系 用程式可立即地指出任何差異,例如遺漏項目或多 目。可利用逆轉配置局部地修復這些差異。 使用這些基本類型,自裝運到運輸間可執行以下步 該裝運人員使用本發明系統以確認一特定裝運(系統 知道)將會裝載至一特定運輸載具上(如--^車)。此動 輸載 。⑷ 實際 及改 被卸 輸感 運選 驟。 人員 運的 。該 讀取 發明 統應 餘項 驟。 已去 作將 80 1310919 一特定讀取器(位於卡車的裝載區)與一載具結合,且間接 地與一組裝運結合。其結果為一批次ID。該讀取器以下列 格式傳送一連串的配置訊息至本發明系統:Time Note Batch ID Item ID This person indicates the batch completion on the system application. The program of the present invention immediately indicates any differences, such as missing items or multiple items. These differences can be repaired locally using a reversal configuration. Using these basic types, the following steps can be performed from the shipment to the transport bay. The shipper uses the system of the present invention to confirm that a particular shipment (system known) will be loaded onto a particular transport vehicle (e.g., a vehicle). This move is loaded. (4) Actual and change the unloading sensor selection. Personnel transported. The reading of the invention is the remaining one. A specific reader (located in the loading area of the truck) of the 80 1310919 has been combined with a carrier and indirectly combined with a group of shipments. The result is a batch ID. The reader transmits a series of configuration messages to the system of the present invention in the following format:

時間戳記批次ID項目ID 該人員在系統應用程式上指出批次完成。本發明系統應 用程式可立即地指出任何差異,如遺漏項目或多餘項目。 本發明系統知道應被裝載至此卡車上的裝運的所有集合。 可利用逆轉配置局部地修復這些差異。到達系統關於任何 特定項目的任何詢問顯示該項目位於此卡車上並且為區域 ERP系統所知的一指定裝載ID的部分。因此,如果一項 目自一卡車上掉落,所有來自系統以及區域ERP系統的訊 息均可被發現。 使用這些基本類型,自運輸到接收間可執行以下步驟。該 卡車駛入位於其中一個裝運點的裝載區。本發明系統將關 於任何已知運送的運送目標地址與一已知系統位置結合。 該接收人員停住本發明系統應用程式且賣主將預定運送的 裝運集合 告知該人員。該裝運人員輸入該卡車的ID並被給予一 相關裝運的清單。如果曳引式卡車的牵引頭在圖中更換, 該司機可攜帶一運送指定甚至一標記,以明確地識別該裝 運。最後該人員使用由原始裝運人員所使用的相同運輸資 料物件。多個來源可裝載貨物至相同的卡車上。 本發明系統應用程式清楚地知道哪個項目應自卡車上 81 1310919 卸下,即使涉及多個裝運。該配置種類被指定為&quot;在預定位 置卸載”。該結果為一批次ID。該讀取器以下列格式傳送 一連串的配置訊息至本發明系統:Timestamp Batch ID Item ID This person indicates the batch completion on the system application. The system application of the present invention immediately indicates any differences, such as missing items or redundant items. The system of the present invention knows all the collections of shipments that should be loaded onto this truck. These differences can be repaired locally using a reversal configuration. Any inquiry to the system for any particular item indicates that the item is located on this truck and is part of a specified load ID known to the regional ERP system. Therefore, if a project falls from a truck, all information from the system and the regional ERP system can be discovered. Using these basic types, the following steps can be performed from transport to reception. The truck enters the loading area at one of the shipping points. The system of the present invention combines a shipping target address for any known shipment with a known system location. The recipient stops the system application of the present invention and the vendor informs the person of the shipment collection scheduled to be shipped. The shipper enters the ID of the truck and is given a list of related shipments. If the tractor of the traction truck is replaced in the picture, the driver can carry a shipping designation or even a tag to clearly identify the shipment. Finally the person uses the same transport item used by the original shipper. Multiple sources can load cargo onto the same truck. The system application of the present invention clearly knows which item should be removed from the truck 81 1310919, even if multiple shipments are involved. The configuration type is designated as &quot;unloaded at a predetermined location." The result is a batch ID. The reader transmits a series of configuration messages to the system of the present invention in the following format:

時間戳記批次ID項目ID 該人員在系統應用程式上指出批次完成。本發明系統可 即時地辨別多餘的原料是否被卸載或是否裝運的一部份仍 然留在卡車上。 最後,本發明系統知道該裝運被運送,且可觸發一清單 訊息。 可靠度議題 所有的訊息被傳送,但其可能以任意的順序出現且有些 可能被重播。本發明系統可容納本發明系統中多個電腦的 當機以及可能的累積訊息的重播。舉例來說,一連串的每 台電腦可累積一組訊息並記錄至磁碟。當_上游的系統當機 並重開,其可要求重播先前訊息或重播看似局部儲存而未 傳送的訊息。 本發明系統可免於事件任意地重播。舉例來說,本發明 系統可遭遇下列情況; 時間戳記-1項目X被讀取並報告為批次B 1的部分。 時間戳記-2項目X被讀取並報告為批次B 1的部分。 此順序為一簡單的重複且通常可能會在最低階層被過 濾掉,但可能被送至本發明系統。 82 1310919 其次,一操作者可能發現移動項目 X足一錯誤,並輸 入一撤銷:Timestamp Batch ID Item ID This person indicates the batch completion on the system application. The system of the present invention instantly identifies whether excess material has been unloaded or if a portion of the shipment remains on the truck. Finally, the system of the present invention knows that the shipment is being shipped and can trigger a list message. Reliability issues All messages are transmitted, but they may appear in any order and some may be replayed. The system of the present invention can accommodate the downtime of multiple computers in the system of the present invention and the replay of possible accumulated messages. For example, a series of computers can accumulate a set of messages and record them to a disk. When the upstream system crashes and reopens, it may request replay of the previous message or replay the message that appears to be partially stored but not transmitted. The system of the present invention is free from replaying events arbitrarily. For example, the system of the present invention may encounter the following conditions: Timestamp-1 Item X is read and reported as part of Batch B1. Timestamp-2 Item X is read and reported as part of Batch B1. This sequence is a simple repetition and may usually be filtered out at the lowest level, but may be sent to the system of the present invention. 82 1310919 Secondly, an operator may find that the mobile project X is full of errors and enters a revocation:

時間戳記-3撤鎖項目X 隨後本發明系統的某些部分可能當機,產生下列重播: 時間戳記-2項目X被讀取並報告為批次B 1的部分。 如果該撤銷並未被重播,也許由於系統如何當機的某些 態樣,本發明系統將會看見: 時間戳記-1項目X被讀取並報告為批次B1的部分。 時間戳記-3撤銷項目X(批次B 1) 時間戳記-2項目X被讀取並報告為批次B 1的部分。 然而,正確的解釋為沒有項目 X的移動。為了得到這 樣的解釋,使該撤銷為黏滯的(sticky) —舉例來說,撤銷被 累積且在每個屬於一給定批次的無重播事件之後有效地被 重播。 具備一準確的分散時鐘( + /_幾毫秒内),本發明系統記 錄每個配置的時間戳記以及每個項目-包括撤銷。本發明系 統可忽略比最新收到的訊息還年輕的配置訊息,在先前描 述過的順序中產生正確的結果。然而,此方法並不總是產 生正確的結果。 舉例來說,假設該事件以及對應的時間戳記如下: 項目X被移動· 時間戳記-1項目X被讀取並報告為批次B1的部分。 項目X再次移動, 83 1310919 時間戳記_2項目X被讀取報告為批次B2的部分。 操作者認為項目X2的移動足錯誤的: 時間戳記-3撤銷項目X(批次B2) 本發明系統當機或其他事件造成擾亂,因此本發明系統 看見: 時間戳記-2項目X被讀取並報告為批次B 2的部分。 時間戮記-3撤鎖項目X (批次B 2 ) 時間戳記-1項目X被讀取並報告為批次B1的部分。 忽略除了較最近收到關於此項目之訊息還要新的訊息 之外的所有訊息這樣的簡單演算法意味著本發明系統將會 忽略該批次B 1訊息且該批次B 2訊息會被(正確地)忽略。 然而,本發明系統會認為項目X位於較B1之前的狀態但 這是不對的。一種在系統回復期間的更有效運算法為依照 訊息的時間戳記將所有可用的訊息白復原時窗整理並隨後 依序處理所有訊息。 3.5資訊擷取方案 可實施本發明系統以提供一人類層級詢問介面,或可由 結合的系統完成,或者由上述兩種方式共同完成。 不論於何處實施,詢問的例子以及關於詢問介面的某些 功能將如下所述。 最基本的詢問為:一特定項目在何處?例如:适瓶藥在 何處?這個詢問是低成本的且容易使用傳統詢問建置技術 來實施。此技術也可提供一詢問建置機制,其允許互動選 84 1310919 擇限定詞像是項目時間、製造者等等以分離一獨立項目 意即該使用者可能不知道真正的項目ID,而可能必須詢 本發明系統以識別於某一時間製造且運送至某一藥房的 物等等。 另外一個詢問為:一特定種類的項目位.於何處? 如:所有的D -電池心電池在何處?或許有許多關於D電 心電池的項目類型(eUPCs)、多個製造者、多種化學種類 包裝等等。一合理的介面允許建立一種包括多個種類的 問。 其他的詢問為:在一特定地理空間内的項目在何處? 如:距離西雅圖1 0 0英里内的所有D大小的電池在何處 或是:在一給定的裝運範圍内的項目在何處?例如:距 西雅圖四小時之内的所有D大小的電池在何處?可首先 置一種從不同地理位置至西雅圖的預期裝運延遲表單, 可支援這些詢問。由於定義此複雜地理,本發明系統便 在該地理表單内找尋項目。 本發明系統也可支援詢問例如:所有具有特定屬性地 目在何處?例如:所有超過兩年(現在曰期-製造曰期)的 罐在何處?所有Firestone於2000年1月1日至200 1 1月1日間製造製造的輻射胎在何處?此項目_類型的 均儲藏室等待時間是多長? D大小的電池在送往一零售 前於儲藏室中能夠放多久? D大小的電池在零售架上可 放多久? 問 藥 例 池 % 詢 例 ? 離 建 便 可 項 藥 年 平 點 以 85 1310919 可實施本發明系統以提供各種統計選項,例如提供 值計算、標準差、銷售量、最小值以及最大值。因此 發明系統可支援詢問例如:從位置X至位置γ的平均 時間是多久?例如:將Acme製造的產品從芝加哥運 雅圖的時間要多久? 對於進階詢問的實施策略 一整體系統由ITS實施的聯合加上額外的應用軟 成,該ITS實施的聯合在彼此之間聯繫,而該應用軟 括一地理空間的應用程式,其可以利用自簡單地掃瞄 標記所蒐集來的資料以動態地預測項目的為致病回答 的詢問。這些詢問對於每個項目或許需要更多昂貴的 追蹤技術。 進階詢問的例子包含:可以使用普通裝運方式在四 内運往西雅圖的金頂電池在何處?所有通過科羅拉多 道路被封閉了 ,那些裝運可能受到影響?所有絞碎牛 裝運之預計現在位置在何處? 與裝運延遲有關的詢問 本發明系統知道何時一裝運被裝載至一卡車上、裝 目的地以及當到達目的地時何時自裝運卸載。因此本 系統可記錄出現於系統中關於所有開始位置及結束位 配對並將其記入日誌中。此資料的累積允許本發明系 算裝運時間的統計數據,例如平均值、眾數、標準差 平均 ,本 裝運 至西 體組 體包 被動 複雜 位置 小時 的的 肉的 運的 發明 置的 統計 、最 86 1310919 大值、最小值等等。因此,基於時間的詢問足可能的 如:可以使用普通裝運方式在四小時内運往西雅圖的 電池在何處? 有數種可能的方法以回應裝運延遲詢問。舉例來說 第一個方法中其步驟如下:(1)識別所有對應至金頂電 項目類型。(2)基於項目_類型識別所有儲存金頂電地 的最大地理範圍内(例如加拿大與美國)某個擁有金頂 庫存的位置。(3)識別所有在西雅圖統計區域内在過去 收金頂電池的目的地,此動作為一基於西雅圖、電池 種類以及累積歷史的單純地理搜尋。(4)基於自步驟3 的地名單,找出所有進入該目的地的平均裝運時間 找出步驟4的開始位置與步驟 2的可用儲存位置的 點。(6)將步驟5中的開始位置/目標位置/平均延遲記 延遲為基礎加以整理。選擇那些平均延遲達到等於或 四小時之標準的位置。(7)步驟6給予該問題答案;結 位置可出現在地圖上。(8)其他訊息,例如裝運成本可 以優化選擇,因此舉例來說,本發明系統回答可能的 裝運成本來源。 此方法僅考慮過去已被使用過的開始位置以裝運 雅圖。該搜尋可擴大至檢查聯合歷史裝運部分,其中 部預期的延遲在某個忍受程度内,該部分的總合併未 特定的目標。 也可輕易地調整上述方法以尋找供給西雅圖的電 ,例 金頂 ,在 池的 位置 電池 已接 項目 的目 。(5) 交叉 錄以 小於 果的 能可 最小 至西 該全 超過 池最 87 1310919 便宜的來源而不論時間。 第一種方法識別該裝運延遲以及基於電池的歷史裝運 找尋可能的貨物來源。一第二方法使用商業上可用的路徑 安排設計軟體及服務。這些已建立的解決方法估計一最佳 化路徑以及在美國或其他國家境内任何兩位置之間的駕駛 時間(或其他運輸)。使用這些技術為基礎,可使用下列的 步驟以回答詢問:(1)識別所有對應至金頂電池的項目-類 型。(2)基於項目-類型識別所有儲存金頂電地位置的最大 地理範圍内(例如加拿大與美國)某個擁有金頂電池庫存的 位置。(3)使用路徑安排設計軟體,建立一種自每個具有電 池庫存的位·置至西雅圖之駕駛時間表。(4)整理該表格並 識別那些離西雅圖駕駛時間在四小時内的庫存位置 這第二種方法識別可能但不常實際使用的裝運路徑。舉 例來說,由於稅與其他因素,金頂公司可能從未自加拿大 裝運至美國。上述的方法可能顯示離西雅圖最快的來源為 溫哥華。是否採用此來源便屬商業抉擇。 裝運障礙詢問 本發明系統知道所有現在裝運的來源及目的地。本發明 系統也知道每個裝運的開始時間以及關於每對開始位置及 結束位置的平均運送時間。因此,其可回答詢問像是:所 有經過科羅拉多州的道路被封閉了。哪些裝運可能受到影 響? 88 1310919 有數個可能的方法以回答裝運障礙詢問。舉例來說,如 第2 1圖所示之第一種方法,其步驟可能如下:(1 )識別路 線毁壞(travel disruption)的地理區域,例如科羅拉多 州。(2)識別所有現在裝運以及那些計晝於某個有利時期的 裝運。(3)對於每個裝運執行以下步驟:(a)形成該開始位置 2130及結束位置2140的邊界箱子(13〇1111以1^1?〇乂)2120。(13) 決定該邊界箱子交叉還是重疊。(c)如果他們以任何方式交 叉,便認為會有潛在的毁壞。如後所述,即使沒有交叉或 從屬(depending),例如在高速公路、山裡、水路等等,還 是可能會有毀壞。參看下述。 此方法提供依基本且通用的潛在毁壞指示。一種更明確 的指示可藉由自開始位置至結束位置觀看直線路徑7 3 0而 形成。如果路線毁壞與此現交叉,便有更強烈的潛在損壞 指示。 利用第22圖說明在一第二且更明確的方法中,具有一 運輸路徑的想法。 在方法二中,使用方法一的步驟1至5以指出路線毀壞 8 1 0是否可能會影響特定的裝運。如果邊界箱子與路線毀 壞交叉,便檢查計畫中的運輸路線之細節,例如藉由考慮 路途點2 2 2 0。如果計晝中路徑與路線毀壞直角交叉,便有 實質的毁壞潛能。該圖說明當路線毁壞阻擋直線路徑時, 其並未真正地阻擋計晝路線8 1 0。 利用第23圖說明在一方法三中,可提供更詳細的路徑。 89 1310919 可藉由每個路徑的局部直接入口、藉由街道名稱或藉由使 用路徑規劃軟體以提供這些路徑。這些詳細的資訊允許更 精確地偵測影響載具運輸之已建立道路的毁壞。其步驟 為:(1)決定位於被阻擋的高速公路或道路部分的路線毁壞 23 1 0。(2)在時窗内找到對於所有裝運的所有運輸路徑 2 3 2 0。( 3 )將該路徑毁壞道路部分與該計晝路徑配對。在其 相配之處,該指示路徑將被毀壞。 即時位置表示及詢問 一即時位置系統(RTLS)可提供持續地物件追蹤。此追 蹤通常利用一可能很貴的應答器完成。本發明系統可取得 攜帶不貴的被動RFID標記的項目並且提供一 RTLS接近能 力(approximate capability) ° 因此有兩種基本的回答位置詢問的方法。在第一種方法 中,該運輸系統(例如卡車、船、飛機等)具有一 RTLS。所 有運輸系統的即時位置均被監視,且本發明系統將一特定 項目與該運輸結合,因此與該位置結合。在第二種方法中, 自固定位置讀取被動標記所收集的資訊以及關於預定裝運 的資訊用於大略估計項目的現在位置。此方法更為便宜且 提供運輸RTLS許多的好處而不需要任何 RTLS基礎架 構。其亦可與第三方運送人共同作業。 如果在該運輸上具有RTLS能力,該正式的裝運過程將 一裝運與一運輸模式結合。如果該運輸本身是一種被標記 90 1310919 的物件,如帶有一 RTLS型能炉 心棵S己的卡車,本發明 最近的RTLS更新時知道該裴運的確切位置。 一位置詢問的例子為:顯示所有絞碎+肉之裝運 現在位置。該RTLS方法依照下列步冑:⑴查詢欲 碎牛肉裝運之項目㈣。(⑽^種項目 在裝運。(3)識別每個裳運使用的運輸載具。(句藉 最近關於該標記的RTLS更新以找出運輸標記物件 〇(5)以例如緯度及經度顯示現在地理位置。Timestamp-3 Unlock Item X Then some parts of the inventive system may crash, producing the following replay: Timestamp-2 Item X is read and reported as part of Batch B1. If the revocation is not replayed, perhaps due to some aspect of how the system crashes, the system of the present invention will see: Timestamp-1 Item X is read and reported as part of Batch B1. Timestamp-3 Undo Item X (Batch B 1) Timestamp-2 Item X is read and reported as part of Batch B1. However, the correct explanation is that there is no movement of item X. To get this explanation, the undo is made sticky—for example, the undo is accumulated and effectively replayed after each no-replay event belonging to a given batch. With an accurate decentralized clock (within + /_ milliseconds), the system of the present invention records the timestamp of each configuration as well as each item - including revocation. The system of the present invention can ignore configuration messages that are younger than the most recently received message and produce correct results in the previously described sequence. However, this method does not always produce the correct results. For example, assume that the event and the corresponding timestamp are as follows: Item X is moved • Timestamp-1 Item X is read and reported as part of Batch B1. Project X moves again, 83 1310919 Timestamp _2 Item X is read as part of batch B2. The operator considers that the movement of item X2 is erroneous: Timestamp-3 revoke item X (batch B2) The system of the present invention crashes due to crashes or other events, so the system of the present invention sees: Timestamp-2 item X is read and Reported as part of batch B2. Time Note-3 Undo Item X (Batch B 2 ) Timestamp-1 Item X is read and reported as part of Batch B1. A simple algorithm that ignores all messages except the one that received a new message about the item recently means that the system of the present invention will ignore the batch B1 message and the batch B2 message will be ( Correctly) ignored. However, the system of the present invention would consider the item X to be in a state prior to B1 but this is not correct. A more efficient algorithm during system replies is to organize all available messages in a timed window according to the timestamp of the message and then process all messages in sequence. 3.5 Information Capture Scheme The system of the present invention can be implemented to provide a human level interrogation interface, either by a combined system or by both. Regardless of where it is implemented, examples of inquiries and certain functions regarding the interrogation interface will be described below. The most basic question is: Where is a particular project? For example: Where is the bottle of medicine? This inquiry is low cost and easy to implement using traditional query construction techniques. This technique may also provide a query construction mechanism that allows interactive selection of 84 1310919 qualifiers such as project time, manufacturer, etc. to separate a separate project meaning that the user may not know the real project ID, but may have to The system of the present invention is inquired to identify items manufactured and shipped to a certain pharmacy at a certain time, and the like. Another question is: What is the specific type of project location? Where? Such as: Where are all D-cell batteries? There may be many project types (eUPCs) for D-cell batteries, multiple manufacturers, multiple chemical types, and so on. A reasonable interface allows for the creation of a query that includes multiple categories. Other inquiries are: Where are the projects in a particular geospatial space? For example: Where are all D-sized batteries within 100 miles of Seattle or: Where are the items within a given shipping range? For example: Where are all D-sized batteries within four hours of Seattle? You can first place an expected shipping delay form from different geographic locations to Seattle to support these queries. By defining this complex geography, the system of the present invention looks for items within the geographic form. The system of the present invention can also support queries such as: Where are all the specific attributes? For example: Where are all the tanks that are more than two years old (now the flood season - manufacturing flood season)? Where are all the radiation tires manufactured by Firestone from January 1, 2000 to January 1, January 1st? What is the waiting time for this project_type storage room? How long can a D-sized battery last in the storage room before being sent to a retail store? How long can a D-size battery last on a retail shelf? Ask the drug pool % Instances to be re-established The drug can be used at 85 1310919 to implement the system of the present invention to provide various statistical options, such as providing value calculations, standard deviations, sales volumes, minimum values, and maximum values. Thus the inventive system can support the query, for example: How long is the average time from position X to position γ? For example: How long does it take to ship Acme's products from Chicago? Implementation strategy for advanced queries - The overall system is implemented by the combination of ITS implementations plus additional applications, the associations of the ITS implementations are linked to each other, and the application is a geospatial application that can be utilized Simply scan the collected data to dynamically predict the item's query for the diseased answer. These queries may require more expensive tracking techniques for each project. Examples of advanced queries include: Where is the Golden Top battery that can be shipped to Seattle in four shipments using normal shipping methods? All are closed through the Colorado roads, and those shipments may be affected? Where is the expected current location of all minced cattle shipments? Interrogation relating to shipping delays The system of the present invention knows when a shipment is loaded onto a truck, loaded into a destination, and when it is unloaded from shipment when it arrives at the destination. Therefore, the system can record and record all the start and end bit pairs in the system. The accumulation of this data allows the present invention to calculate the statistics of the shipping time, such as the average, the mode, the standard deviation average, and the statistics of the invention of the shipment of the meat that is shipped to the passive body of the West Body group. 86 1310919 Large value, minimum value, etc. Therefore, time-based queries are possible, such as: Where can the batteries shipped to Seattle within four hours using normal shipping methods? There are several possible ways to respond to shipping delay inquiries. For example, the steps in the first method are as follows: (1) Identify all the types corresponding to the Golden Top project. (2) Identify all locations in the largest geographic area (such as Canada and the United States) that have the Golden Top inventory based on the project_type. (3) Identify all destinations in the past in the Seattle Statistical Area for the receipt of the Golden Top Battery. This action is a simple geographic search based on Seattle, battery type and cumulative history. (4) Based on the list of the grounds from step 3, find out the average shipping time of all the destinations. Find the point where the starting position of step 4 and the available storage location of step 2 are found. (6) Sort the start position/target position/average delay in step 5 as a basis. Select those locations where the average delay reaches a standard equal to or four hours. (7) Step 6 gives the answer to the question; the knot position can appear on the map. (8) Other information, such as shipping costs, may optimize the selection, so for example, the system of the present invention answers possible sources of shipping costs. This method only considers the starting position that has been used in the past to ship the Aratu. The search can be expanded to check the joint historical shipment portion, where the expected delay is within a certain tolerance level and the total consolidation for that portion is not specific. It is also easy to adjust the above method to find the electricity supplied to Seattle, such as the Golden Top, where the battery has been connected to the project. (5) Cross-recording is less than the energy of the energy can be the smallest to the west. It is all over the pool. The most expensive source is 87 1310919 regardless of time. The first method identifies the shipping delay and the historical shipment based on the battery to find possible sources of goods. A second method uses a commercially available path to arrange design software and services. These established solutions estimate an optimized path and driving time (or other transportation) between any two locations in the United States or other countries. Based on these techniques, the following steps can be used to answer the query: (1) Identify all project-types that correspond to the Golden Top battery. (2) Identify all locations in the largest geographic area where the Golden Territory location is stored (eg, Canada and the United States) with a gold-top battery inventory based on the project-type. (3) Use the route arrangement design software to establish a driving schedule from each location with battery inventory to Seattle. (4) Organize the form and identify those inventory locations that are within four hours of driving time in Seattle. This second method identifies shipping paths that may be, but are not, often used. For example, due to taxes and other factors, Golden Top may have never shipped from Canada to the United States. The above method may show that the fastest source from Seattle is Vancouver. Whether or not to use this source is a business choice. Shipping Barrier Inquiry The system of the present invention knows the source and destination of all current shipments. The system of the present invention also knows the start time of each shipment and the average transit time for each pair of start and end positions. Therefore, it can answer questions like: All roads passing through Colorado are closed. Which shipments may be affected? 88 1310919 There are several possible ways to answer shipping barrier inquiries. For example, the first method, as shown in Figure 21, may have the following steps: (1) Identify the geographic area of the route disruption, such as Colorado. (2) Identify all current shipments and those that are counted in a favorable period. (3) The following steps are performed for each shipment: (a) forming a boundary box (13〇1111 by 1^1?〇乂) 2120 of the start position 2130 and the end position 2140. (13) Decide whether the boundary box crosses or overlaps. (c) If they cross in any way, they are considered to be potentially damaging. As will be described later, even if there is no cross or dependency, such as on a highway, a mountain, a waterway, etc., it may be destroyed. See below. This method provides a basic and versatile indication of potential damage. A more specific indication can be formed by viewing the straight path 730 from the starting position to the ending position. If the route is broken and there is a crossover, there is a stronger indication of potential damage. The idea of having a transport path in a second and more explicit method is illustrated using Figure 22. In method two, steps 1 through 5 of method one are used to indicate whether the route destruction 8 1 0 may affect a particular shipment. If the boundary box intersects with the route, check the details of the route in the plan, for example by considering the waypoint 2 2 2 0. If the path between the plan and the route is broken at right angles, there is substantial potential for destruction. The figure illustrates that when the route destroys blocking the straight path, it does not really block the metering route 810. Using Figure 23, a more detailed path can be provided in a method three. 89 1310919 These paths can be provided by local direct entry of each path, by street name, or by using path planning software. These detailed information allows for a more accurate detection of the damage to established roads that affect the transport of the vehicle. The steps are: (1) Deciding that the route on the blocked highway or road section is destroyed 23 1 0. (2) Find all transport routes for all shipments in the time window 2 3 2 0. (3) Pairing the path destroying road portion with the counting path. Where it matches, the indicated path will be destroyed. Instant Location Representation and Inquiry A Real Time Location System (RTLS) provides continuous object tracking. This tracking is usually done with a potentially expensive transponder. The system of the present invention achieves an item carrying inexpensive passive RFID tags and provides an RTLS approach capability. Thus there are two basic methods of answering location queries. In the first method, the transportation system (e.g., truck, boat, aircraft, etc.) has an RTLS. The immediate location of all transport systems is monitored and the system of the present invention combines a particular item with the transport and thus combines with that location. In the second method, the information collected by the passive tag from the fixed location and the information about the scheduled shipment are used to roughly estimate the current location of the item. This approach is cheaper and provides many of the benefits of transporting RTLS without the need for any RTLS infrastructure. It can also work with third-party carriers. If there is RTLS capability on the shipment, the formal shipping process combines a shipment with a mode of transportation. If the transport itself is an item marked 90 1310919, such as a truck with a RTLS type furnace, the nearest RTLS update of the present invention knows the exact location of the shipment. An example of a location inquiry is: Display all the minced + meat shipments. The RTLS method follows the following steps: (1) Query the item for which the beef is to be shipped (4). ((10)^ The item is in the shipment. (3) Identify the transport vehicle used for each item. (The sentence is recently updated with the RTLS update for the mark to find the transport mark object 〇(5) to display the current geography, for example, latitude and longitude. position.

雖沒有RTIS能力,本發明糸祕A 个I啊糸統知道該裝運何時 一卡車、裝運的目的地以及何時於該目的地完成卸 運。因此本發明系統可記錄顯示於本發明系統中此 每對開始位置及結束位置的資訊並記入日誌中。本 統隨後可計算中間值、或平均值、裝運時間。此資 本發明系統估計一裝運的現在位置,並可任意地附 心範圍(Confidence range)。 此方法用於下步驟回應該詢問範例(顯示所有絞 之裝運的估計現在位置):(1)查詢欲知的絞碎牛肉 項目-類型。(2)基於過去的歷史找出這些裝運的平 時間。(3)找出所有關於此種項目-類型的現在裝運 於每個運送比較記錄開始時間、現在時間以及平均 間。這個數量估計該行程完成的比例。 可用數種不同方式估計並顯示該現在位置。使; 圖說明在該直線方法中,利用自開始位置至結束位 系統在 的估計 知的絞 所有現 由找到 的位置 裝載上 載該裝 種關於 發明系 訊允許 帶信, 碎牛肉 裝運之 均裝運 。(4)對 運送時 丨第 24 置的直 91 1310919 線路徑大略估計全部的運送行程。藉由計算該行程完成的 估計比例 2 4 1 0並假設一直線路徑,可估計該裝運的位置 2420。此方法並不對應至真實世界的道路及公路,但其給 予相對於目的地之貨物位置的一種可接受的大略估計。 由第25圖所示的另外一種方法中,建立一種對於每個 裝運的詳細路徑,已如前述。此方法可提供例如一種路線 部分2 5 1 0 - 2 5 1 8的詳細順序,其可在一地圖上強調出來。 路線規劃軟體可估計至任何路線上特定點的經過時間。例 如在第2 5圖中,估計並說明到達每個交換點的預計駕駛時 間。基於對於實際開始時間的了解,本發明系統可於位於 一特定道路上的特定位置之層次估計一運送載具的現在位 置。此方法對於決定一已知運輸障礙所造成的影響特別有 用,如一關閉的橋樑。 4.在項目追蹤系統與標記讀取器之間的資料傳遞 以下的章節將描述本發明系統的實施,其在標記讀取器 以及ITS間插入硬體及軟體。插入之硬體及軟體的功能也 可選擇整合至該ITS中,例如為第1圖中該OIC104的部 分。 4.1事件路由器 本發明系統的一種實施使用一個或多個事件路由器以 在該IT S及該標記讀取器之間轉送資訊。事件為自一軟體 92 1310919 實體通過至另一軟體實體的訊息。可使用事件以通知事件 接收者關於某件事情的發生,或傳送一詢問至該接收者。 可使用一事件路由器以在數個實體間分配事件。可使用的 事件路由器的例子包含基於主題的 KnowNow⑧事件路由 器,其可自位於加州的 Mountain View的KnowNow公司 取得•·或者為以内容為基礎的Elvin訊息服務,其可自澳 洲皇后島的 Distributed Systems TechnOlOgy Center 取 得。該以主題為基礎以及以内容為基礎的事件路由器也可 合併使用。 為了說明的目的,將以其用於一特定的庫存管理方案中 來描述本發明系統。 第36圖描述關於項目追蹤系統(ITS)的一零售位置,該 項目追蹤系統用於做為一庫存管理系統的部分。該零售位 置為一商店。該商店具有包含標記項目的庫存。當標記項 目帶入或移出該商店,可被一監控系統3 6 1 0偵測到。 該監控系統 3 6 1 0包含多個置於商店中一個或多個位 置的標記讀取器。該監控系統3610也包含儲存庫存中每 個項目之現在狀態的記憶體。該狀態指出該項目是否存在 於一特定位·置或已自該位置移開。該監控系統 3 6 1 0也包 含電腦邏輯,其決定該項目的狀態何時改變,例如當該項 目被加入或移出該特定位置。 可進一步調整該邏輯以傳送一更新,每當其偵測到一項 目之狀態有改變。該庫存更新可採取一種事件的形式,該 93 1310919 事件包含該項目的ePC、該標記讀取器的ePC以及一 戳記。該事件也可包含一進/出參數,其指出該改變究 一項目的加入還是移除。 在一實施中,該監控系統 3610包含一個或多個智 架(smart shelves)。智慧貨架為一種貨架,其可在實 目被加入或移出該貨架時報告。一智慧貨架包含數個 於一個或多個貨架上位置的標記讀取器。一智慧貨架 含電腦邏輯以決定該項目究竟是被加入還是移出庫存 一 ITS3620為了包括屬於儲存庫存項目的多個項 護追蹤資訊。每當項目進入或離開該商店,該ITS自 控系統3 6 1 0接收一事件並更新其資料儲存以反應事科 一庫存規劃工具 3640——電腦程式解決方案一 在一定期的計晝操作以執行庫存管理功能。在與該商 關的商店中,該庫存規劃工具 3640自該TS 3 67 0擷 存資料並決定是否要補充該商店庫存。該庫存規劃 3 64 0可自一早期警示代理程式(EWA) 3 63 0接收警示 可使該庫存規劃上具在其平常定期計畫表之外執行至 些起碼與該商店有關的庫存管理功能。特別地 EWA3630可送出一警示至該庫存規劃工具 3640以使 定是否補充商店需要的庫存。每當該項目進入或離開 店,甚至隨意地當其自該商店的某一部份移往其他部 該EWA自監控系統 3 6 1 0接收一事件。使用在這些事 接收的資訊,該 EWA決定何時送出警示至庫存規劃 時間 竟是 慧貨 體項 放置 也包 〇 目維 該監 〇 通常 店有 取庫 工具 ,便 少一 ,該 其決 該商 分, 件中 工具 94 1310919 3 640 ° 早期警示代理程式 該EWA3 63 0包含邏輯以決定何時送出一警示。是 出一警訊的決定包含應用一個或多個規則至庫存更新 收的資訊。一規則指定一特定條件以及於條件吻合時 行的一特定動作》例如一規則可指定每當庫存程度低 特定值時應送出一警示。 該E W A 3630可應用一預先決定的規組,或是替代 包含人工智慧邏輯以使其可回應現在或歷史庫存樣本 變其行為。該人工智慧邏輯使該EWA可估計於不遠之 的潛在庫存程度變化以夠旱識別潛在的危險情況而允 正.措施。例如一開始該規則可指定當庫存掉至1 〇以 迅速啟動該警示。然而’如果該EWA3 63 0偵測到在夏 送出警示較其他奉節頻繁許多,該EWA3630可藉由在 將臨界值從1 〇增加到2 0而適應季節變換,因而該庫 劃工具3640會較旱收到逼近的庫存短缺的通知。 該EWA3 6 3 0可擷取並分析現在及歷史庫存資料以 趨勢’例如規劃補貨於實際補貨間的差異,並建立一 庫存需要的預測模型。這些趨勢及預測可利用線性回 分類以及區域樹狀圖來決定’或其他推測運算法來争 在一實施中’該EWA3 63 0估計關於每個規劃補貨 能影響庫存的消耗動作(例如假設歷史執行資料,其估 否送 中接 被執 於一 地可 而改 將來 許修 下時 天其 夏天 存規 偵測 位來 歸、 定。 或可 計一 95 1310919 種取規劃卡車裝載,其來源為B ob的12盘司瓶子。瓶子 會在規劃的運送時間之前四小時到之後六小時之間的任何 時間到達,且其數量在要求數量的95%到100%之間)之潛 在的變化。該EWA3 6 3 0比較過去關於數個庫存之承諾的及 實際的運送時間以產生計晝中但尚未完成之真正傳送曰期 以及未來補貨數量之動作的預測。該EWA 3 6 3 0結合關於數 個獨立動作之潛在變化的估計,使其成為一關於整體庫存 之潛在變化的估計。可使用決策樹狀圖像是分類或區域樹 狀圖來實施這些運算法。 在其他的實施中,該EWA3630基於匯總資料建立該預 測模型而非考慮獨立動作,該累積資料表示補貨及消耗的 累積程度。可使用可能的推論模型如條件高斯近似實施這 些運算法。 關於該EWA3630使用之演算法的進一步細節可於公有 的、一同待審的關於庫存早期警示代理程式的美國專利申 請中找到,該申請為美國臨時申請序號第60/384,63 8號, 2 0 02年5月 3 1日提出,該申請的内容包含於此參照中。 庫存規劃工具 該庫存規劃工具 3640可為任和擬定庫存補貨計畫的 應用程式。一種此類的庫存規劃工具 3640為可從SAP AG 取得的進階規劃工具及最佳化工具(APO)。 該庫存規劃工具 3640包含用於擬定庫存計晝的邏 輯。該邏輯包含一邏輯用於自該EWA 3630接收一警示,且 96 1310919 回應該警示決定是否需要補貨。 在一具體實施例中,該庫存規劃上具3 64 0 存擬定補貨計畫.。一 EWA3 63 0監控一部份的庫 多個E W A 3 6 3 0以涵蓋全部的庫存。一有關一部 示觸發該庫存規劃工具3640已決定對於整個 補貨是否需重新規劃。 該決定可包含自該 ITS3620擷取庫存並基 存資料決定或預報需求。舉例來說,一種關於&gt; 度需求趨勢可促使該庫存規劃工具準備不僅是 X且包括更多的產品Y,已知該產品X為該產 指標。 如第37圖所示,一事件路由中介軟體如一 (ER)37 10可用來在不同的實體間分配事件,舉 該監控系統 3610、該ITS3620、該EWA3630 規劃工具 3 6 4 0之間。適合的事件路由器的例 主題為基礎的KnowNow⑧事件路由器,其可自 Mountain View的KnowNow公司取得:或者為 礎的Elvin訊息服務,其可自澳洲皇后島的 Systems Technology Center 取得。該以主題為 内容為基礎的事件路由器也可合併使用。 以内容為基礎的事件路由 在一具體實施例中,基於每個訊息的内容替 為一完全庫 .存。可結合 份庫存的警 庫存的規劃 於擷取的庫 查品X的高 更多的產品 品Υ的領導 事件路由器 例來說,在 以及該庫存 子包括該以 位於加州的 以内容為基 Distributed 基礎以及以 其安排自發 97 1310919 佈者至用戶的路徑。每個訊息的内容可被分割成多個内容 領域。舉例說,與一具有該 ePC 之項目有關的訊息 01.0037F2.001508.000319F827可被分成下歹ij内容領域: (1) 標頭: 〇1 (2) 製造者: 0037F2 (3) 產品種類:001508 (4) 序號: 0003 1 9F827 (5 )訊息類型:看見@,請求,回應--看見@訊息為 一報告該項目在一特定位置已被偵測到的訊息。一 “請 求”訊息用於傳送一請求至一用戶而一“回應”訊息用於 發佈該回應資訊。也可定義其他訊息類型。 該用戶可指定基於内容領域之數值的訊息過濾器。(例 如:製造者=003 7F2以及訊息類型=看見@) 基於主題的事件路由 在一可供選擇的實施中,可依據標題分類事件。一軟體 實體可能僅對關於某些標題的事件有興趣。該軟體實體可 以只訂閲某些特定標題而其將只會收到關於那些而非其他 標題的事件。 第38圖說明基於一 ePC結構的標題結構。可建立一分 割的標題給該ePC的每個資料領域,即製造者、產品種類 以及序號。舉例來說,對於一具有該ePC01.0037F2.00150 8.000319F827的項目,可建立下列的標題: 98 1310919 (1) \〇61^阻111^\0037?2\〇015081000319[827\看見@一此標題 涵蓋與該項目有關的“看見事件。 (2) \centauri\003 7F2\00 1 508\0003 19F827\* —此標題包含 報告至標題1的事件以及其他種類與該項目有關的 事件,如“要求”與“回應”事件 (3) \centauri\0037F2\001 50 8\*—此標題包含報告至標題2 的事件以及與在同一產品種類001508中其他項 目有關的事件。 (4) \centauri\003 7F2\*—此標題包含所有報告至標題3的 事件,且亦包括與具有相同製造者003 7F2的其他項目 有關的事件。 也可替關於讀取器的事件建立分割標題。例如對於一具有 該 ePC01.0B39C2.000815.004711F 827 的讀取器,可建立 以下的標題。 (l)centauri\0B3 9C20008 1 50047 1 1 F82 7\ 已看見 ePC—此標 題涵蓋與一已偵測到一特定ePC之特定讀取器有關的事 件。 (2)centauri\0B39C2000815004711F827\*—此事件函蓋與 一已偵測到任何的ePC之特定讀取器有關的事件。 一基於標題的事件路由器具有一標題組合且每個標題具有 一位址,如一 URL。藉由傳送該事件至該標題的位址,可 發佈一事件至一標題。為了決定適當標題的URL以發佈出 一訊息,一發佈實體如一監控系統3 6 1 0 (第3 7圖)可諮詢 99 1310919 一延伸物件命名服務(EONS)3720。一 EONS37 20維護在 項目ePCs(或一讀取器ePCs)與一個或多個ERs之間的對應 與其對應的標題。一 EONS將一項目(或讀取器)的ePC視 為輸入並回答關於一個或多個識別標題的URL(sj。可藉由 延伸一傳統的0NS實施該EONS3720,該傳統0NS之例子 為 Oat Systems與麻省理工學院自動-ID 中心所研發的 0NS,該ONS在物件命名服務技術手冊(由麻省理工學院 自動-ID中心發行)中有更詳細的描述。傳統的物件命名系 統相似於知名的網際網路域名系統(DNS)並以其為基礎。 發佈的協定流動 如第39圖所示,在操作中該監控系統3610辨識一項目 被加入或移出該庫存。該監控系統製造一事件,其包含一 標記識別記號、一讀取器識別記號以及一時間戳記。該標 記識別記號識別已改變的項目。該讀取器識別記號識別偵 測到改變的讀取器。而該時間戳記識別何時偵測到該改變。 該監控系統 3 6 1 0隨後諮詢該E ON S 3 7 2 0以決定傳送事 件至何處。該監控系統3610提供該EONS該項目的ePC 以及該讀取器的ePC並且自EONS取回關於項目標題以及 讀取器標題的URLs。該監控系統 3 6 1 0隨後送出該事件至 該兩個標題。 關於標題項目以及讀取器項目的 ER(s)替項目安排路 徑至一個或多個用戶。舉例來說,該ITS可為該項目標題 100 的用戶 接收事 '警示 的補貨 可送出Although there is no RTIS capability, the present invention knows when the shipment is a truck, the destination of the shipment, and when the shipment is completed at that destination. Thus, the system of the present invention can record information displayed in the start and end positions of each pair in the system of the present invention and record it in the log. The system can then calculate the median, or average, and shipping time. The present invention system estimates the current location of a shipment and can optionally have a Confidence range. This method is used in the next step to return to the query example (showing the estimated current position of all twisted shipments): (1) Query the desired ground beef item-type. (2) Find out the time of these shipments based on past history. (3) Find out all the current shipments for this type of project-type comparison start time, current time, and average time for each shipment. This amount estimates the proportion of completion of the trip. The current location can be estimated and displayed in several different ways. In the straight line method, the estimated wraps from the start position to the end position system are all loaded from the found position and loaded on the loading information of the invention, and the shipment of the ground beef. (4) For the transportation, 丨24th straight line 13 1310919 line route roughly estimated the entire shipping itinerary. The location 2420 of the shipment can be estimated by calculating the estimated ratio of completion of the trip 2 4 1 0 and assuming a straight path. This method does not correspond to real-world roads and roads, but it gives an acceptable rough estimate of the location of the cargo relative to the destination. From the other method shown in Fig. 25, a detailed path for each shipment is established as described above. This method can provide, for example, a detailed sequence of route portions 2 5 1 0 - 2 5 1 8 that can be highlighted on a map. The route planning software estimates the elapsed time to a particular point on any route. For example, in Figure 25, the estimated driving time to each switching point is estimated and accounted for. Based on an understanding of the actual start time, the system of the present invention can estimate the current position of a transport vehicle at a level of a particular location on a particular road. This method is particularly useful for determining the effects of a known transport disorder, such as a closed bridge. 4. Data Transfer between Project Tracking System and Tag Reader The following sections describe the implementation of the system of the present invention, which inserts hardware and software between the tag reader and the ITS. The functionality of the inserted hardware and software can also optionally be integrated into the ITS, such as the portion of the OIC 104 in Figure 1. 4.1 Event Router An implementation of the system of the present invention uses one or more event routers to transfer information between the IT S and the tag reader. The event is a message from one software 92 1310919 entity to another software entity. An event can be used to notify the event recipient of the occurrence of something, or to send a query to the recipient. An event router can be used to distribute events among several entities. Examples of event routers that can be used include the subject-based KnowNow8 event router, available from KnowNow of Mountain View, Calif. • or for content-based Elvin messaging services from Distributed Systems TechnOlOgy, Queens Island, Australia Center obtained. This topic-based and content-based event router can also be combined. For purposes of illustration, the system of the present invention will be described in its use in a particular inventory management scheme. Figure 36 depicts a retail location for the Project Tracking System (ITS) that is used as part of an inventory management system. The retail location is a store. The store has an inventory of tagged items. When the marked item is brought into or out of the store, it can be detected by a monitoring system 3 6 1 0. The monitoring system 3 6 1 0 includes a plurality of tag readers placed in one or more locations in the store. The monitoring system 3610 also includes memory for storing the current state of each item in the inventory. This status indicates whether the item exists at a particular location or has been removed from that location. The monitoring system 3 6 1 0 also includes computer logic that determines when the status of the item changes, such as when the item is added or removed from the particular location. The logic can be further adjusted to transmit an update whenever there is a change in the state in which it is detected. The inventory update can take the form of an event that includes the ePC of the item, the ePC of the tag reader, and a stamp. The event may also include an entry/exit parameter indicating whether the change is added or removed. In one implementation, the monitoring system 3610 includes one or more smart shelves. A smart shelf is a shelf that can be reported when a reality is added to or removed from the shelf. A smart shelf contains a number of tag readers on one or more shelves. A smart shelf contains computer logic to determine whether the project is added or removed. ITS3620 is intended to include multiple item tracking information that is part of a stored inventory item. Whenever the project enters or leaves the store, the ITS automated control system 3 6 1 0 receives an event and updates its data store to reflect the transaction-inventory planning tool 3640 - the computer program solution 1 performs in a periodic accounting operation Inventory management function. In the store associated with the merchant, the inventory planning tool 3640 stores the data from the TS 3 67 0 and decides whether to replenish the store inventory. The inventory plan 3 64 0 can receive alerts from an Early Warning Agent (EWA) 3 63 0 to enable the inventory plan to perform inventory management functions associated with the store outside of its usual periodic schedule. In particular, the EWA 3630 can send a warning to the inventory planning tool 3640 to determine whether to replenish the inventory required by the store. Whenever the project enters or leaves the store, it is even arbitrarily moved from one part of the store to the other. The EWA self-monitoring system 3 6 1 0 receives an event. Using the information received in these matters, the EWA decides when to send out the warning to the inventory planning time, which is actually the hustle and bustle item placement, and the 维 维 维 该 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 〇 , Tools in the piece 94 1310919 3 640 ° Early Warning Agent The EWA3 63 0 contains logic to decide when to send a warning. Yes The decision to issue a warning includes the application of one or more rules to the inventory update. A rule specifies a specific condition and a specific action when the condition is consistent. For example, a rule may specify that a warning should be sent whenever the inventory level is low. The E W A 3630 can be applied with a predetermined set of rules, or it can contain artificial intelligence logic to make it respond to current or historical inventory samples. This artificial intelligence logic allows the EWA to estimate the potential stock level changes not far away to aid in the identification of potentially dangerous conditions. For example, at the beginning, the rule can specify that when the inventory falls to 1 〇 to quickly activate the alert. However, if the EWA3 63 0 detects that the warning sent in summer is much more frequent than other festivals, the EWA3630 can adapt to the seasonal change by increasing the threshold from 1 2 to 20, so the library tool 3640 will be more dry. Receive notification of an approaching stock shortage. The EWA3 6 3 0 can capture and analyze current and historical inventory data as trends, such as planning the difference between replenishment and actual replenishment, and establishing a forecasting model for inventory needs. These trends and predictions can be determined using linear back-classifications and regional tree diagrams or 'other speculative algorithms to compete in an implementation'. The EWA3 63 0 estimates the consumption actions that can affect inventory for each planned replenishment (eg, assuming history) Execution of the data, it is estimated that the delivery will be carried out in one place, but it will be changed in the future when it is repaired. It can be counted as a 95 1310919 type of planned truck loading. The source is B. The 12-disc bottle of ob. The bottle will arrive at any time between four hours before the planned delivery time and between six hours after the scheduled delivery time, and the number is between 95% and 100% of the required quantity). The EWA3 6 3 0 compares past commitments regarding several stocks and actual shipping times to produce a forecast of the actual delivery period in the calculation but not yet completed and the future replenishment quantity. The EWA 3 6 3 0 combines estimates of potential changes in several independent actions, making it an estimate of the potential change in overall inventory. These algorithms can be implemented using a decision tree image that is a classification or a region tree. In other implementations, the EWA 3630 builds the predictive model based on aggregated data rather than considering independent actions, which represent the cumulative level of replenishment and consumption. These algorithms can be implemented using possible inference models such as Gaussian approximations. Further details regarding the algorithm used by the EWA 3630 can be found in the publicly-owned, pending review of the U.S. Patent Application Serial No. 60/384,63 8, 2 0. Proposed on May 31, 2002, the contents of this application are included in this reference. Inventory Planning Tool The Inventory Planning Tool 3640 is available for both the application and the inventory replenishment plan. One such inventory planning tool, the 3640, is an advanced planning tool and optimization tool (APO) available from SAP AG. The inventory planning tool 3640 contains logic for developing inventory plans. The logic includes a logic for receiving an alert from the EWA 3630, and 96 1310919 should be alerted to determine if replenishment is required. In a specific embodiment, the inventory plan has a 3640 default plan for replenishment. An EWA3 63 0 monitors a portion of the library Multiple E W A 3 6 3 0 to cover the entire inventory. A related trigger triggered the inventory planning tool 3640 has decided whether to re-plan for the entire replenishment. The decision may include taking inventory from the ITS3620 and determining or forecasting the demand data. For example, a trend regarding &gt; degree demand may cause the inventory planning tool to prepare not only X but also more products Y, which is known to be the production indicator. As shown in Figure 37, an event routing intermediary software such as an (ER) 37 10 can be used to distribute events between different entities, such as between the monitoring system 3610, the ITS 3620, and the EWA 3630 planning tool 3 6 4 0. A suitable event router-based theme is the KnowNow8 event router, available from Mountain View's KnowNow: or the Elvin Message Service, available from Systems Technology Center in Queens Island, Australia. This topic-based event router can also be combined. Content-Based Event Routing In a specific embodiment, the content of each message is replaced by a full library. The portfolio of police inventory that can be combined with the inventory of the inventory of the inventory of the product is higher than the product of the leader. In this case, the inventory includes the content-based distributed basis of the California-based distribution. And the path to the user with the arrangement of spontaneous 97 1310919. The content of each message can be split into multiple content areas. For example, the message 01.0037F2.001508.000319F827 related to a project with the ePC can be divided into the following 内容 content areas: (1) Header: 〇1 (2) Manufacturer: 0037F2 (3) Product Type: 001508 ( 4) Serial number: 0003 1 9F827 (5) Message type: See @, Request, Response - See @Message as a message that the item has been detected at a specific location. A "request" message is used to send a request to a user and a "response" message for posting the response. Other message types can also be defined. The user can specify a message filter based on the value of the content field. (Example: Manufacturer = 003 7F2 and Message Type = See @) Subject-based event routing In an alternative implementation, events can be categorized by title. A software entity may only be interested in events about certain titles. The software entity can subscribe to only certain headlines and it will only receive events about those other than the other headings. Figure 38 illustrates the header structure based on an ePC structure. A split title can be created for each data area of the ePC, namely the manufacturer, product type, and serial number. For example, for a project with the ePC01.0037F2.00150 8.000319F827, the following title can be created: 98 1310919 (1) \〇61^阻111^\0037?2\〇015081000319[827\See @一此The title covers the “see event” associated with the project. (2) \centauri\003 7F2\00 1 508\0003 19F827\* — This title contains the events reported to Title 1 and other types of events related to the project, such as “ Request and Response events (3) \centauri\0037F2\001 50 8\*—This title contains the events reported to Title 2 and events related to other projects in the same product category 001508. (4) \centauri\ 003 7F2\*—This title contains all events reported to Title 3, and also includes events related to other items with the same manufacturer 003 7F2. Split title can also be created for events related to the reader. For example, for one The reader of the ePC01.0B39C2.000815.004711F 827 can be created with the following headings: (l) centauri\0B3 9C20008 1 50047 1 1 F82 7\ ePC has been seen - this title covers a specific ePC that has been detected Specific reader related events. (2) centauri\0B39C2000815004711F827\*—This event message covers an event related to a particular reader that has detected any ePC. A header-based event router has a header combination and each header has an address. Such as a URL. By transmitting the event to the address of the title, an event can be issued to a title. In order to determine the URL of the appropriate title to publish a message, a publishing entity such as a monitoring system 3 6 1 0 (Fig. 3 7 You can consult 99 1310919 An Extended Object Naming Service (EONS) 3720. An EONS37 20 maintains a correspondence between the project ePCs (or a reader ePCs) and one or more ERs corresponding to the title. An EONS will be a project The (or reader) ePC treats the input and answers the URL for one or more identified titles (sj. The EONS3720 can be implemented by extending a traditional 0NS example of Oat Systems and the Massachusetts Institute of Technology. The 0NS developed by the Auto-ID Center, which is described in more detail in the Object Naming Service Technical Manual (issued by the MIT Auto-ID Center). The traditional object naming system is similar to the knowledge. Named Internet Domain Name System (DNS) and based on it. Published Protocol Flow As shown in Figure 39, in operation, the monitoring system 3610 recognizes that an item has been added or removed from the inventory. The monitoring system creates an event that includes a tag identification token, a reader identification token, and a time stamp. The mark identification mark identifies the changed item. The reader identifies the token to identify the reader that detected the change. The timestamp identifies when the change was detected. The monitoring system 3 6 1 0 then consults the E ON S 3 7 2 0 to determine where to transmit the event. The monitoring system 3610 provides the ePC of the EONS item and the ePC of the reader and retrieves the URLs for the item title and the reader title from EONS. The monitoring system 3 6 1 0 then sends the event to the two titles. The ER(s) for the title item and the reader project arranges the route to one or more users. For example, the ITS can receive a reminder for the user of the project title 100.

可為該讀取器標題的用戶。該EWAIER 被送出, 。為了得 事件 警示至該庫存規劃工具《如果 更觸發該庫存規劃工具以重新規劃該庫存 關於庫存的現在資料,該庫存規劃上具 安拂路徑至T ^謗ER要求庫存資料。該ER隨後替該事件 具來回應 劃 -* π IT只竹。隨後替該事件 I ^ ^ 其藉由送出所要求的庫存資料至庫存規 關柃訂 如第 鱗的路定流動 卑40圖 戶首杏 所示,對於每個用戶想要訂購的標題,該用 次峋問p 後留之 0NS以決定關於特定標題之ER的位置並隨 思、關於ϋ ^ 、待發佈至標題的事件。 备收到, ^ 事件時,該用戶可使用容納於該事件的讀取器 織別記號已、玉 m 决定該項目的位置。該位置可為一實體位置(例—*考字八 ’疋緯度、經度及高度)或一邏輯位置(例如位於容器XYZ ^ -t. * 下皁A B c中)。该用戶也可使用該標記識別記號以 確定關於該項目之額外實訊的位置。舉例來說,該標記識 別記號可用於擷取關於该項目的PML(產品標記語言)文 件。 如第41圖所示,〆E〇NS 3720可維護在多個標記項 目(或讀取器)與多個ERS 3710&amp;至3710c之間的對應。如 上所述,該對應支援多梱键,包括一項目鍵以及一讀取器 鍵。該EONS 3720可服務多個監控系統3610以及其他標 記讀取器應用程式。在〆實施中,該E〇NS 3720為一分散 101 1310919 的次系統,其包含對應資訊、用於回應要 問的詢問伺服器以及可接收一 e P C並解相 位置中的名稱解析器。 如第42圖所示,一特定的ER可分散 是 ITS 3 620(如同其他用戶)而一特定的 ERs,像是ER 3710。一使用者可定義關於 的範圍且照著設定該分散計晝。 4.2整合引擎 如第3 1圖所示,本發明系統的一種實 引擎 3 1 1 0,其作為在該 ITS以及該標記 具。可實施該整合引筆於該標讀取器及該 體及硬體。該整合引擎3110也可替代地4 例如為第1圖中QIC 104的部分。 該整合引擎 3110可與該標記讀取器 其他種類的智慧項目般。在此說明書中, 為一種可儲存並與外部系統通訊關於其本 機器。可使用任何通訊通道(如無線電頻i 通訊過程可帶領儲存於該智慧項目令資料 的智慧項目也具有處理能力,使其可與其 地互動,並且舉例來說,協調一公共行為 存並聯繫不同種類的資料包含一唯一項目 以及其他關於該項目的項目特性。某些智 求資訊位置之詢 -該 ePC 至一 ER 至多個ITSs ,像 ITS可訂閱多個 每個IT S之想要 施可使用一整合 讀取器的中間工 ITS之間插入軟 ;合至該ITS中, 1 0 2通訊如同與 一 “智慧項目” 身資料的項目或 ^、紅外線)。該 的改變。更精密 他智慧項目直接 。智慧項目可儲 識另,記號(UID) 慧項目具有感應 102 1310919 器可儲存情境的資料例如溫度、濕度、加速度或位置 通訊資料可為即時資料或歷史資料,或兩者皆是。 智慧項目的例子包括標記項目、RFID詢問器、致 裝置、察覺的貨物以及嵌入的網路應用程式。一詢問 一標記讀取器及寫入器。一致動器裝置為一種移動或 某些事物(例如一輸送帶、一自動販賣機)的機器。察 貨物為可偵測關於其情境資訊(例如裝有位.置或溫度 器的貨物)的貨物。 對於一特定感應器或致動器裝置的支援藉由使用 體介面例如第3 4圖中所示的示範軟體而實施。該整合 3 11 0自不同種類的智慧項目3 1 2 0收集資料並提供該 的資料至高階應用程式 3130包括該ITS 103。該整合 311 0也可寫入資料至智慧項目3 1 20。 整合引擎 該整合引擎3110自智慧項目3120讀取並寫入資 即時處理該資料並提供該處理資料至高階應用 3 1 3 0。即時地這樣做代表接收該資料時便加以處理, 時便提供該資料。該整合引擎3 11 0也可自高階應用 313 0接收資料並寫入資料至智慧項目3120。 處理該資料可包括資料過濾。舉例來說,一應用程 以只對接收UIDs及位置資料有興趣,而其他應用程 能只對從某個智慧項目收集資料有興趣。可提供一分 。該 動器 器為 控制 覺的 感應 一硬 引擎 收集 引擎 料、 程式 處理 程式 式可 式可 離的 103 1310919 過濾器給每個應用程式要求資料。 處理該資料也可包含資料匯總。資料匯總包括將資料結 合在一起以製造高階資料。舉例來說,結合位於卡車中的 一項目的UID與自卡車讀取的溫度以製造一關於該項目的 溫度讀數。匯總資料比起單獨地處理該資料可使該資料更 有意義。匯總也可包含累積即時資料至一批次中,並於預 定的期間傳送該批次資料而非即時傳送。該資料可放上具 有收集日期及時間的時間戳記。 調整該整合引擎3 1 1 0以連接提供基本讀取及寫入功能 之不同種類的硬體介面。該整合引擎3110在特定硬體資 料格式與一通用格式間轉譯,或在某些情況中在特定硬體 資料格式與特定應用程式格式間轉譯。在此狀況中,該整 合引擎3 11 0對該應用程式 313 0隱藏硬體細節。 第32圖說明如何使用多個整合引擎 3110以管理大量 的智慧項目。可指定每個整合引擎3 1 1 0在發現智慧項目 的特定位置間傳送資料(例如工廠、裝載區、商店)。該應 用程式 3130可訂購一個或多個整合引擎 3110。可實施每 個整合引擎 3110為成套的多個整合引擎 3110。一整合引 擎的輪出可為進入一高階整合引擎3110的輸入。 第33圖說明一整合引擎 31 10的示範實施。該整合引 擎 3 1 1 0管理所有涉及與智慧項目互動的資源及物件並控 制整體的過程。該整合引擎 3110包含一控制管理員 3 3 1 0、一詢問器代理程式 3 3 2 0、一處理代理程式 3 3 3 0以 104 1310919 及一通訊代理程式 3 3 4 0。可使用傳統程式設計技術實施該 元件,該技術包含以元件為基礎的技術如 Java,C#或 C” 物件。 該控制管理員 3 3 1 0在該整合引擎 3 1 1 0以及應用程式 3130間提供該程式設計介面。該程式設計介面實施一通用 的(非特定實施的)通訊介面至多個轉接器可被掛入之處。 該轉接器在一特定通訊介面(如RFC,COM’ COKBA,IMS’ HTTP)以及一通用通訊介面之間轉接。 該控制管理員 3310自該應用程式 3130接收並解釋該 規則、接收並解釋客戶端命令、且舉例說明該適當的詢問 器代理程式、處理代理程式以及通訊代理程式以執行規 則。該規則可定義或限制詢問器代理程式《、處理代理程 式以及通訊代理程式之行為的各種態樣。舉例來說,該規 則可定義提供何種資料給一應用程式(例如只提供UID或 位置資料)、寫入何種資料至該硬體(例如如果該卡車的溫 度掉到預定臨界值以,下,則寫入一關掉冷氣的命令)或何 時提供該資料(例如每天)。規則也可定義如何結合收集的 資料以產生高階資料(例如結合位於卡車中一種項目的 UID以及卡車的溫度以決定該項目是否過熱)。當資料接收 時該控制管理員3 3 1 0解釋並應用該規則。 在一實施中,該控制管理員容納於一規則儲存區中或以 某種方式與其結合,以儲存自該應用程式接收的規則:該 控制管理員亦容納於一規則引擎中或以某種方式與其結 105 1310919 合,以執行該儲存規則。自該應用程式接收到的規則可 UML(統一建模語言)模型、EJB(企業 JavaBeans)果實 XML(延伸標記語言)文件表示。如果有必要的話,該控 管理員3 3 1 0轉換該規則為規則引擎使用的一内部格式。 一詢問器代理程式 3 3 20負責整體地控制單一硬體 置介面如一 RFID控制介面。一詢問器代理程式 3320 合一硬體介面、該控制管理員 3310以及一處理代理程 3 3 3 0。可依據該硬體介面的需求調整該詢問器代理程 3 3 20。例如某些硬體介面需要非同步輪詢反之其他介面 生事件或中斷。該詢問器代理程式(3320通常不在收集 資料上執行任何處理,反之其僅僅轉送該資料至一處理 理程式3 3 3 0以供處理。 一處理代理程式3 3 3 0負責資料過濾、匯總以及運輸 作。該處理代理程式 3330與該控制管理員 3310及一詢 器代理程式 3320互動。 為了執行資料過濾,該處理代理程式3 3 3 0接收由一 或多個詢問器代理程式收集的感應器資料。該處理器代 程式3 3 3 0行使該規則引擎以確定是否有任何資料滿足 規則所指定的條件。合乎該條件的資料被轉送至通訊代 程式 3340 〇 為了執行資料匯總,該處理代理程式3 3 3 0儲存該接 資料在一缓衝中直到其已收到一特定規則要求的所有 抖。該處理代理程式3 3 3 0接收一特定硬體格式的資料 用 或 制 裝 結 式 式 產 的 代 操 問 個 理 該 理 收 資 106 1310919 該處理代理程式 3 3 3 0使用對應表以在該特定硬體格式與 通用格式之間轉換,該通用格式為整合引擎 3110輸出至 癟用程式 3130的格式。 該資料載入可在多個處理代理程式間分享。某些處理氏 理程式 3 3 3 0僅可處理含有一特定種類資訊的資料,如購 買訂單編號。在這些情況中,該詢問器代理程式 3 3 2 0基 於硬體的類型(例如一條碼掃描器發出條碼資訊)或描述該 資料的中繼資料(例如參考第3 4圖中說明的邏輯標記類型 定義)決定其已收集的資料類型。某些處理代理程式3 3 3 0 可處理複雜的資料一自數個處理代理程式 3 3 3 0的輸出匯 總的資料。該相同的處理代理程式或代理程式 3 3 3 0可服 務要求同種資料的應用程式。 一通訊代理程式 3340負責使用推入或拉出模型兩者 之一提供資料至該應用程式3130。一應用程式可明確地要 求實施一讀取或寫入操作於該智慧項目3 1 20(拉入模型), 或π應用程式可要求當整合架構自該智慧項目3 1 2 0接收 資料時通知該應用程式(推入模型)。Can be the user of the reader title. The EWAIER was sent out, . In order to get an event alert to the inventory planning tool, if the inventory planning tool is further triggered to re-plan the current information about the inventory, the inventory plan has an ampoule path to the T ^谤ER required inventory data. The ER then responded to the event with a stroke -* π IT only bamboo. Then, for the event I ^ ^, by sending the required inventory data to the inventory regulation, as shown in the first scale, the title is used for the title that each user wants to order. After the question p, leave the 0NS to determine the location of the ER about the specific title and follow the question, about ϋ ^, the event to be posted to the title. Upon receipt of the ^ event, the user can use the reader contained in the event to weave the token, and the jm determines the location of the item. The location can be a physical location (eg - * 字 八 疋 latitude, longitude and altitude) or a logical location (eg, located in the container XYZ ^ -t. * under the soap A B c). The user can also use the tag to identify the token to determine the location of the additional news about the item. For example, the tag identification token can be used to retrieve a PML (Product Markup Language) file for the item. As shown in Fig. 41, the 〆E〇NS 3720 can maintain correspondence between a plurality of tag items (or readers) and a plurality of ERSs 3710&amp; to 3710c. As described above, the corresponding support multi-click key includes a item key and a reader key. The EONS 3720 can serve multiple monitoring systems 3610 as well as other tag reader applications. In an implementation, the E〇NS 3720 is a secondary system of 101 1310919 that contains corresponding information, an inquiry server for responding to the request, and a name resolver that can receive an e P C and resolve the location. As shown in Fig. 42, a particular ER is decentralized to be an ITS 3 620 (like other users) and a specific ER, such as the ER 3710. A user can define the range of the relevant and set the dispersion. 4.2 Integration Engine As shown in Figure 31, a real engine 3 1 1 0 of the system of the present invention acts as the ITS and the tag. The integrated pen can be implemented on the target reader and the body and hardware. The integration engine 3110 may alternatively be, for example, part of the QIC 104 in FIG. The integration engine 3110 can be used with the tag reader for other kinds of smart projects. In this specification, it is a type that can be stored and communicated with an external system about its own machine. Any communication channel can be used (such as the radio frequency i communication process can lead the smart project stored in the smart project order data also has the processing power to enable it to interact with it, and for example, coordinate a common behavior and contact different types The material contains a unique project and other project features about the project. Some inquiries about the location of the information - the ePC to an ER to multiple ITSs, like ITS can subscribe to more than one IT S want to use one The inter-integrated ITS of the integrated reader is inserted softly; in the ITS, the communication is like a project with a "smart project" or ^, infrared. The change. More sophisticated, his smart project is straightforward. Wisdom items can be stored, and UIDs can be sensed. 102 1310919 can store situational information such as temperature, humidity, acceleration or position. Communication data can be real-time or historical data, or both. Examples of smart projects include tagging projects, RFID interrogators, devices, perceived goods, and embedded web applications. A query is made to a tag reader and writer. The actuator device is a machine that moves or something (such as a conveyor belt, a vending machine). The goods are goods that can detect information about their situation (such as goods with a position or temperature). Support for a particular sensor or actuator device is implemented using a bulk interface such as the exemplary software shown in Figure 34. The integration 3 11 0 collects data from different types of smart projects 3 1 2 0 and provides the data to the high-end application 3130 including the ITS 103. The integration 311 0 can also write data to the smart project 3 1 20 . Integration Engine The integration engine 3110 reads and writes the information from the smart project 3120 to process the data and provide the processing data to the high-end application 3 1 3 0. This information is provided when the data is processed as soon as it is received. The integration engine 310 can also receive data from the high-level application 313 0 and write data to the smart item 3120. Processing the data can include data filtering. For example, an application is only interested in receiving UIDs and location data, while other applications are only interested in collecting data from a smart project. One point is available. The actuator is a controllable sensor. A hard engine collects the engine material, and the program processes the programmable 103 1310919 filter to request data for each application. Processing the data can also include a summary of the data. The summary of the data includes combining the data to create high-level data. For example, the UID of an item located in the truck is combined with the temperature read from the truck to create a temperature reading for the item. Aggregating data makes the data more meaningful than treating it separately. The summary can also include accumulating real-time data into a batch and delivering the batch data over a predetermined period instead of instant delivery. This information can be placed on a time stamp with the date and time of collection. The integration engine 3 1 1 0 is adjusted to connect different types of hardware interfaces that provide basic read and write functions. The integration engine 3110 translates between a particular hardware data format and a common format, or in some cases between a particular hardware data format and a particular application format. In this case, the integration engine 310 changes the hardware details to the application 313 0. Figure 32 illustrates how to use multiple integration engines 3110 to manage a large number of smart projects. Each integration engine 3 1 1 0 can be assigned to transfer data (eg, factory, loading area, store) between specific locations where smart items are discovered. The application 3130 can subscribe to one or more integration engines 3110. Each integration engine 3110 can be implemented as a set of multiple integration engines 3110. The rollout of an integrated engine can be an input into a higher order integration engine 3110. Figure 33 illustrates an exemplary implementation of an integration engine 31 10. The integration engine 3 1 1 0 manages all processes and resources that involve interaction with smart projects and controls the overall process. The integration engine 3110 includes a control manager 3 3 1 0, an interrogator agent 3 3 2 0 , a processing agent 3 3 3 0 to 104 1310919 and a communication agent 3 3 4 0. The component can be implemented using conventional programming techniques, including component-based technologies such as Java, C# or C" objects. The Control Manager 3 3 1 0 is provided between the integration engine 3 1 1 0 and the application 3130 The programming interface. The programming interface implements a common (non-specific implementation) communication interface to where multiple adapters can be plugged in. The adapter is in a specific communication interface (eg RFC, COM' COKBA, IMS 'HTTP) and a universal communication interface. The control administrator 3310 receives and interprets the rule from the application 3130, receives and interprets the client command, and exemplifies the appropriate interrogator agent, processing agent Programs and communication agents to enforce rules that define or limit various aspects of the behavior of the interrogator agent, the processing agent, and the communication agent. For example, the rule defines what information is provided for an application. Program (for example, only UID or location data), what kind of data is written to the hardware (for example, if the temperature of the truck falls to the pre- The threshold is written in the next, or when the data is turned off (for example, daily). The rules can also define how the collected data can be combined to produce high-level data (for example, combined with the UID of a project in a truck) The temperature of the truck determines whether the item is overheated. The control manager 3 3 1 0 interprets and applies the rule when the data is received. In one implementation, the control manager is housed in a regular storage area or in some manner In conjunction with it, to store rules received from the application: the control administrator is also housed in a rules engine or in some way with its junction 105 1310919 to execute the storage rule. Rules received from the application can be UML (Unified Modeling Language) model, EJB (Enterprise JavaBeans) fruit XML (Extensible Markup Language) file representation. If necessary, the control administrator 3 3 1 0 converts the rule to an internal format used by the rule engine. The interrogator agent 3 3 20 is responsible for overall control of a single hardware interface such as an RFID control interface. An interrogator agent 3320 is integrated The body interface, the control administrator 3310, and a processing agent 3 3 3 0. The interrogator agent 3 3 20 can be adjusted according to the requirements of the hardware interface. For example, some hardware interfaces require asynchronous polling and vice versa. Event or interruption. The interrogator agent (3320 usually does not perform any processing on the collected data, otherwise it only forwards the data to a processing program 3 3 3 0 for processing. A processing agent 3 3 3 0 is responsible for the data Filtering, summarizing, and shipping. The processing agent 3330 interacts with the control administrator 3310 and an interrogator agent 3320. To perform data filtering, the processing agent 3 3 3 0 receives one or more interrogator agents. Collected sensor data. The processor code 3 3 3 0 exercises the rules engine to determine if any data meets the conditions specified by the rules. The data in accordance with this condition is forwarded to the communication program 3340. In order to perform the data aggregation, the processing agent 3 3 3 0 stores the data in a buffer until it has received all the jitters required by a particular rule. The processing agent 3 3 3 0 receives a data in a specific hardware format or uses the assembly method to generate the data. 106 1310919 The processing agent 3 3 3 0 uses the correspondence table to The conversion between the specific hardware format and the general format is the format that the integration engine 3110 outputs to the application 3130. This data loading can be shared among multiple processing agents. Some processing programs 3 3 3 0 can only process data that contains a specific type of information, such as purchase order numbers. In these cases, the interrogator agent 3 3 2 0 is based on the type of hardware (eg, a code scanner sends out bar code information) or a relay material describing the material (eg, referring to the logical tag type illustrated in FIG. Definition) Determine the type of data that it has collected. Some processing agents 3 3 3 0 can process complex data from a number of processing agents 3 3 3 0 of the output summary data. The same processing agent or agent 3 3 3 0 can service applications that require the same data. A communication agent 3340 is responsible for providing data to the application 3130 using either one of a push-in or pull-out model. An application may explicitly require a read or write operation to be performed on the smart item 3 1 20 (pull-in model), or the π application may request that the integrated architecture notify the when the data is received from the smart item 3 1 2 0 Application (push into the model).

該通訊代理程式 3340字一個或多個處理代理程式 3 3 3 0接收處理的資料並提供該資料給所有訂購的應用程 式 3 1 3 0。該通訊代理程式 3 3 4 0維護一訂購程式 3 1 3 0的 名單以及其各自的目的參數。該通訊代理程式 3340可為 通訊代理程式 3 3 4 0的集合,其中每個通訊代理程式實施 一特定的通訊介面或協定(例如 RPC,COM,CRBA ’ JMS 107 1310919 或 HTTP)。 代替直接地提供該處理的資料給訂購應用程式 3 1 3 0, 該通訊代理程式 3 3 4 0使用一中間工具,例如一事件路由 器。該事件路由器會出現在訂購應用程式的名單中。一事 件路由器為一服務,其於軟體實體間為訊息(事件)安排路 徑。可使用該訊息以通知該訊息接收者關於某些事件發生 或傳送一詢問至該接收者。合適的事件路由器的例子包括 Kno wNo w⑧事件路由器,其可自位於加州的 Mountain View的KnowNow公司取得;或者為以内容為基礎的 Elvi 訊息服務,其可自澳洲皇后島的 Distributed Systems Technology Center 取得。 在一實施中,該通訊代理程式 3 3 4 0以一資料物件(或 物件收集)的格式提供該資料,該資料物件具有方法可被外 部應用程式用於擷取該UID或額外項目資料。在另一實施 中,該資料格式為XML。XML的優點為彈性、可延伸的、 自我描述的以及廣為資料交換所使用。硬體介面 第34圖為--示範的硬體介面 3 40 0的方塊圖。該硬 體介面 3400為一種可使高階軟體與基本硬體互動的軟 體。現今可自多個賣主取得一廣大範圍的RFID技術。依 賴該應用程式方案,需選擇一特定類型的標記(主動/被 動,唯讀/可覆寫等等)。使用開放標準實施該硬體介面足 有利,因此可使用該硬體介面加上自多個賣主取得的多個 RFID技術。該硬體介面可接收詢問以自該硬體介面讀取資 108 1310919 料或要求寫入資料至該硬體介面。源自該硬體介面的資料 可兩者擇一地傳送至詢問器代理程式 3 3 2 0或一處理代理 程式 3330 。The communication agent 3340 words one or more processing agents 3 3 3 0 receive the processed data and provide the information to all subscribed applications 3 1 3 0. The communication agent 3 3 4 0 maintains a list of 3 1 3 0 and its respective destination parameters. The communication agent 3340 can be a collection of communication agents 3 3 4 0, wherein each communication agent implements a particular communication interface or protocol (eg, RPC, COM, CRBA 'JMS 107 1310919 or HTTP). Instead of directly providing the processed data to the ordering application 3 1 3 0, the communication agent 3 3 4 0 uses an intermediate tool, such as an event router. The event router will appear in the list of ordering applications. An event router is a service that arranges paths for messages (events) between software entities. This message can be used to inform the recipient of the message that certain events have occurred or that a query has been sent to the recipient. Examples of suitable event routers include the Kno wNo w8 event router, available from KnowNow Corporation of Mountain View, Calif.; or the content-based Elvi messaging service, available from the Distributed Systems Technology Center in Queens Island, Australia. In one implementation, the communication agent 3 3 4 0 provides the data in the form of a data item (or object collection) having methods for the external application to retrieve the UID or additional project data. In another implementation, the data format is XML. The advantages of XML are flexible, extensible, self-describing, and widely used by data exchange. Hardware Interface Figure 34 is a block diagram of the exemplary hardware interface 3 40 0. The hardware interface 3400 is a software that allows higher-order software to interact with the basic hardware. Today, a wide range of RFID technologies can be obtained from multiple vendors. Depending on the application, you need to select a specific type of tag (active/passive, read/rewritable, etc.). It is advantageous to implement the hardware interface using open standards, so the hardware interface can be used plus multiple RFID technologies from multiple vendors. The hardware interface can receive an inquiry to read the material from the hardware interface or request to write data to the hardware interface. The data from the hardware interface can be alternatively transferred to the interrogator agent 3 3 2 0 or a processing agent 3330.

該介面 3400包括一抽象層一伺服器 3410—其隱藏該 詢問器 3 4 2 0的細節。該伺服器 3 4 1 0透過一硬體附屬介面 與詢問器 3 420溝通。在運作時,一特定伺服器3 4 1 0實體 只對一詢問器 3420負責。然而,數個應用程式可同時與 同樣的伺服器 3410實體通訊。 一伺服器 3 4 1 0支援至少兩個不同種類的讀取詢問。一 分隔的讀取要求回覆資訊只有在可現在.被讀取的標記 上。一持續的讀取要求問回覆資訊在所有已被讀取的標記 上並且在做成之前的讀取要求之後加以缓衝。The interface 3400 includes an abstraction layer-server 3410 that hides the details of the interrogator 3 4 2 0. The server 3 4 1 0 communicates with the interrogator 3 420 through a hardware accessory interface. In operation, a particular server 3 4 1 0 entity is only responsible for an interrogator 3420. However, several applications can simultaneously communicate with the same server 3410 entity. A server 3 4 1 0 supports at least two different kinds of read queries. A separate read request reply message is only available on the mark that can be read now. A continuous read requires that the reply message be buffered on all tags that have been read and after the previous read request is made.

一伺服器3 4 1 0可接收待寫入的資料。該待寫入的資料 可為儲存在一標記上的資料或為控制該硬體行為的控制資 料。舉例來說,一智慧輸送帶可接收在左輸送帶及右輸送 帶間切換的控制資料:一智慧自動販賣機可接收調整一項 目的價格或機器溫度的控制資料。 此外,一伺服器3 4 1 0使下列功能可資利用: 初始億 此功能初始化該介面 3400以供利用。初始化所有硬 體,包括必要的通訊埠、軟體物件與流程。此為一通用的 初始化功能。特定硬體細節可設置於特定硬體設定檔案。 109 1310919 終止 此功能終止該介面 3400的使用。此為初始化的反向功 能。所有的硬體被釋放,通訊埠被關閉且所有有關軟體物 件及流程均被終止(除非它們被其他流程所使用)。這是一 通用的終止功能。特定硬體細節可設置於特定硬體設定檔 案。 偵測標記 此功能偵測現在是否可讀取標記以及多少標記可被讀 取。 定義邏輯標記類型 此功能定義關於一特定標記的邏輯.標記類型。該邏輯 標記類型描述標記上資料的組織。顯示於第3 5圖中的示範 電子標記 3 5 0 0說明這件事。如其所示,在該標記上的使 用者資料實體地由η的3 2為原資料區塊組成。然而邏輯 上,其具有三個命名的資料攔位:一物品編號 (“ ARTNR ” )35 10 、 該物品 的一種描述 (“ARTDESC” )3520 以及其價格(“ PRICE” )3 53 0。如其 所示,該長度以及該欄位的開始地址並不必然要與區塊長 度及開始地址相同。 該邏輯標記類型定義名稱、開始地址以及每個資料攔位 的長度、其資料類型(為了將該欄位輕易地對應至應用程式 資料)以及關於每個欄位的一種描述。該邏輯標記類型也定 義關於儲存一標記識別記號的位置。該邏輯標記類型定義 110 1310919 可延伸包含其他資訊。 取得邏輯標記類型描述極欄位名稱 此功能取得關於一邏輯標記類型的資訊。通常地將使用 此功能以取得該欄位名稱以及欄位長度與資料類型。 開始/結束持續讀取 此功能自所有標記的特定欄位讀取資料,當執行此功能 時可讀取該資料。一參數指出要求一分隔的還是連續的讀 取模式。對於連續模式,該伺服器會缓衝所有讀取標記的 資訊。在連續模式中每個對該讀取功能的呼叫清除此緩 衝。然而,在分隔模式中一呼叫並不清除缓衝。 出自一特定標記的讀取攔位 此功能與之前的功能相似。所不同者為僅讀取出自具有 一特定標記ID之單一標記的欄位。可能需要讀取多個標 記以識別具有該特定標記ID的標記。 寫入欄位至多個標記 此功能寫入相同的資料至所有標記的特定欄位,當執行 此功能時可寫入該資料。該攔位具有名稱且依賴定義該標 記的標記類型。相同的資料被寫入至所有標記。可使用此 功能於大量標記寫入,例如位於生產線的末端。 111 1310919 寫入欄位至特定標記 此功能在標記 —特定標記的# &amp; 記類型。被寫入的 攔位。未在此操作 未有所改變。 讀取器寫入器操作的領域中寫入資料至 攔位。該欄位具有名成且依賴現在的標 標記由其UID指定。資料僅寫入至特定 中指定的所有位於標記攔位中的資料並 資料欄位也可利用兩種寫入功能的任何之一鎖定,只要 硬體支援該功能。彳寫入並同時鎖定該欄位,或是—之前 已寫入的欄位可恰好被鎖定而不需要覆寫其資料。 特定硬體呼叫 某1硬體可能提供一些超越此介面範圍的功能。為了客 戶能使用該功能’此功能提供一機制以直接地從應用程式 通過特定硬體呼叫。 錯誤操作 ^ 一通訊錯誤發生時’該硬體裝置3420或是該伺服器 3410首先嘗試解決自己造成的錯誤,例如藉由重試某操作 數次。當低階錯誤操作失敗時,該介面34〇〇提供關於何 處出錯的資訊因此該應用程式可採取適當行動。除了一定 義錯誤類型的通用錯誤碼之外,亦提供該錯誤的—詳細描 述。該介面3400認出至少下列類型的錯誤狀況: 112 1310919 (1) 詢問器未回應:無法初始化詢問器。 (2) 讀取錯誤:偵測到η標記,但只有m正確地讀] (m&lt;n)。該欄位中沒有標記非為錯誤狀況。 (3) 寫入錯誤:標記無法被寫入,要不是因為在無衾 電攔位中沒有標記就是因為有某些特定的寫入問 題例如鎖住的欄位或一般失敗。 (4) 沒有硬體支援。傢是資料鎖定的功能可能沒有 有的硬體支援。 5 ·追蹤資訊的壓縮、過濾以及加密 下列的章節描述一實施,其中該追蹤資訊在其自一 聯繫至另一企業前被壓縮、過濾或加密。將會描述該 於一方案的上下文中並牵涉到一生產者及一消費者。 產者或消費者可為一製造者、一分配者或是一零售機 或是任何其他位置或一位置的部分,其處理該標記項 如第43圖所示,一生產者4301送出一裝運4303 消費者4302。當消費者43 02收到該裝運43 03,該消 的標記讀取器系統4 3 0 6自該容器標記4 3 0 7以及該項 記4 3 0 8讀取該資訊。為了確認該裝運4 3 0 3,該消費者 需要來自生產者4301的裝運内容資訊4309。此裝運 4309可包含該容器的 UID 以及該容器中所有項 UIDs。其他與每個項目有關的資訊,像是該項目的顏 可與該項目的UID結合或外部儲存於該標記上。透過 被所 企業 實施 一生 構, 目° 至一 費者 目標 43 02 資訊 目的 色, 一通 113 1310919 訊網路 4 3 1 0例如網際網路,該消費者 4 3 0 2可 43 0 1接收裝運資訊43 09且亦可傳送狀態更新資 產者430 1。位於消費者位置的區域ITS431 1自 取系統4 3 0 6擷取資訊並將該標記資訊與該裝運| 配對。 如第45圖所示,用於在一生產者及一消費者 蹤資訊的一方法 4500可藉由一生產者接收多個 開始,每個識別碼唯一地識別一有關項目(45 1 0) &lt; 可自附著於項目的標記讀取該識別碼。為了使 件追蹤可行,每個標記攜帶一關於有關項目的 碼,例如劃分為一 8位元標頭(位元0-7)4510以 料欄位:ePC 管理員(位元 8-3 5)4620、物件韻 36-59)4630以及序號(位元60_95)4640 。每個可 統的組織對於該ePC管理員欄位具有一唯一編碼 織中的每個產品種類具有一唯一編碼於物件種類 一產品的每個單獨項目具有一唯一編碼在序號中 似地使用除了 ePC的UIDs。 該生產者將該識別碼分類成一組或多愈 (4520)。每一組識別碼可對應至一特定類型的項I 自一特定製造者的所有籃球)。 對於每一組識別碼,該生產者認出編碼的多餘 情形對於每組編碼足很普遍的(4 5 3 0)。例如第4 7 關於所有出於一特定製造者的籃球的ePCs包含 自生產者 訊至該生 該標記讀 r 訊 4 3 0 9 間聯繫追 識別碼而 &gt; 跨企業物 唯一識別 及三種資 【類(位元 標言己系 。在一組 攔位中。 。也可類 i識別碼 目(例如出 :部分,該 圖所示, 一多餘部 114 1310919 分4701 —特別地,該ePCs共享相同的ePC管 件種類。此多餘在該ePC的階層體系架構中足梦 該生產者建立一文件包含一組或多組 (4 5 40)。然而在此文件中,該ePC可計算大部 小。例如第47圖所示,一裝運文件包含項目-其包含關於每個裝運項目的ePC。當項目的編 該ePC成為該文件大小的一重要部分。 為了縮小文件的體積,該生產者4301組織 對於每一組識別碼,該編碼的多餘部分會被列 個標記會與省略的多餘編碼部分並列。在此方 用該ePC的階層體系設計以壓縮與每個ePC有 舉例來說,對於所有包裝並裝運至一位置的籃 文件中不需要包含每個籃球的全部ePC。反之 所示,該裝運文件可僅包含關於該 ePC管理 (entry)以及在一 ePC前綴4 802中的物件種類_ 可應用一種與方法4500相似的遮罩技術至 其他上下文。舉例來說,可應用遮單在生產上 小生產訂單的體積。在準備製造項目的一新生 工廠通常擬定一生產訂單,其列出每個項目的 當標頭、ePC管理員以及ePC的物件種類部分 候,上述情況仍然成立。藉由應用方法4 5 0 0至 可減少此多餘且不用列出關於每個項目的所有 略該多餘部分而僅列出序號。 理員以及物 t生倶來的。 的識別碼 分的文件大 層級資訊, 號增加時, 該文件因而 出一次而每 法中,可利 關的資訊。 球,在裝運 如第4 8圖 員的一項目 〇 裝運之外的 下文中以縮 產線時,一 ePC。即使 是相同的時 生產訂單, e P C s,可省 115 1310919 可藉由矢。道序號何時是連續的來進一步降低文件(裝 運、生產或其他)的大小,沒有必要列出所有生產項目的序 號。反之如以下所述,需要被列出的足第一個建立項目的 序號(“ EPC_BASE)以及項目總共被生產的數量(如 1 000)。關於每個項目的額外資訊像走該項目的顏色,可如 下述對每個項目單獨地列出。 〈產品 _訂單 _ID = 123 4 5 66&gt; 〈項目—列表數量 =1000 EPC_ 前綴 =01.000A89.00016F&gt; &lt;EPC_基底 &gt;00 1 68 1 23&lt;/EPC_ &amp; 底 &gt; 〈項目&gt; &lt;顏色 &gt; 紅色&lt;/顏色&gt; &lt;/項目&gt; 〈項目&gt; 〈顏色 &gt;紅.色&lt;/顏色&gt; &lt;/項目〉 〈項目&gt; 〈顏色 &gt;紅色&lt;/顏色&gt; &lt;/項目&gt; &lt;/項目—列表&gt; &lt;/產品—訂單&gt; 116 1310919 沿著一供應鏈,通常將會有被標記以及未被標記的項 目。此外,只有某些類型的項目像是貨盤或包裝會被加上 具有RFID的標記。另外,每個企業可標項目。例如一運 輸公司可標記其裝運包裝以自動化其庫物流過程。因此, 可能會有RFID標記於該項目、該包裝、該貨盤以及該容 器層級,且這些標記可來自不同的企業。然而,一簡單的 讀取器/詢問器無法分辨,例如一項目以及該來自該項目的 項目容器。結果所有被讀取的UIDs必須被報告至一中央 系統並被過濾。此過程對一系統足不足的且非常麻煩,其 必須在一天之中處理上百萬的報告。 用於一企業ePC管理員控制物件種類的任務分配以及 序號。該企業也可定義其自己關於實體物件的概要,該實 體物件作為企業製造的項目的附件。例如由製造者生產的 貨盤及包裝可具有或可不具有其自己的ePC標記。然而, 在一運輸公司的上下文中,具有用於裝運實體項目的容 器。藉由只確認貨盤或包裝而非其全部上下文,可迅速執 行從一裝運區至另一裝運區的傳遞裝運流程。此方法需要 該運輸公司利用其自己的ePC將該容器加上標記。可調整 讀取器以取得ePC樣式的一特定類型。例如可調整讀取器 以註冊該ePC的物件種類部分中僅由字元“ 1 ”開始的容 器。實際的XMK過濾概要看起來將會像是: 〈容器—種類&gt;0 1.1 234566.1 XXXXX&lt;/容器_種類〉 117 1310919 在此例子中,該Xs為萬用字元,其位於形成ePC的 字串中;該讀取器將會接收位於這些位置的任何資料。以 此種方法設置一讀取器允許該讀取器過濾其讀取的 ePCs,並檢查僅在此概要中指出的容器類型。因此,過濾 可減少自讀取器傳送至監控應用程式或過程如裝運確認過 程的訊息。 第49圖說明一方法4900以供過濾追蹤資訊。過濾可由 譆取器或讀取器系統在傳遞過程(即經過多個消費者)以及 於一特定消費者中的不同階段發生。例如由上所述,過濾 發生在標記讀取器階層。替代地或額外地,一消費者的ITS 也可過濾其自標記讀取器接收的資料。 接收與多個項目結合的識別碼,包括獨立的項目以及項 目的容器(4910)。每一個識別碼(例如ePC)為唯一地識別該 結合項目地字_。可自多個來源傢是一標記讀取器、一裝 運文件或是一 ITS(共享的或區域的)擷取該識別碼。放置 一字元於每個識別碼中,該識別碼指出該項目唯一獨立項 目或項目容器(4920)。如上所述,可分辨該容器與位於該 容器中具有“ 1 ”作為該編碼的物件種類部分之開頭字元 的獨立項目;然而,也可使用其他字元以及宇元位置基於 該座落的字元決定該識別碼對應至一獨立項目還是一容器 (4930) ° 當這樣一決定於標記讀取器層級做成時,該標記讀取器 可分辨獨立項目與項目容器,並使用此分別過濾掉與讀取 118 1310919 資訊接收者無關的讀取。舉例來說,如果該接收者為 運公司,其可能只想要知道關於每個標記容器的標 訊,但卻不及於該項目本身。在此情況中,該讀取器 或系統中一高階元件可過濾掉關於獨立項目的編碼並 送關於容器的標記資訊至該接收者。 控制追蹤資訊的存取 在一跨企業電腦情境,該追蹤資訊可被多個消費 耗。然而,該生產者可能不必然希望所有的消費者分 樣程度的存取。例如該製造者可記錄關於一裝運的資 如“負責人”或“品質等級”,其可被某些消費者(例 稅局)有權存取,但其他消費者卻無權存取。 在一實施中,對追蹤資訊的存取藉由提供該消費者 文件的一部份而獲得控制。例如一裝運公司可能只需 道(或得到授權以知道)運送貨物的總數,但該裝運公 能不需要知道(或未得到授權以知道)該貨物的其他 (例如顏色、價格)。 然而,僅傳送該相同編碼的文件至所有消費者將會更 率。因此,一替代的實施提供該相同文件至所有消費 但以一編碼的格式。隨後每個消費者單獨被提供一選 法以解碼該文件的僅僅一部份。該編碼及解碼對於外 統43 12如一 ERP系統可為完全透明的,換句話說, 蹤資訊的輸入及輸出可為徹底未編碼的文件。 一裝 記資 本身 僅傳 者消 享同 訊, 如關 僅該 要知 司可 特性 有效 者, 擇方 部系 該追 119 l3l〇9i9 如第50圖所示,在對控制存取追蹤資訊執行一方法 S 〇〇〇中,一生產者建立關於一項目集合的追蹤資訊該追 蹤資訊以一個或多個特性及選擇對應數值(5〇1〇)表示每個 項目。該生產者藉由將追蹤資訊中每個明確特性的每次利 用其對應的明確編碼方案加以編碼以編碼該追縱資訊。該 生產者傳送該編碼追蹤資訊至一接收者(5030)、決定哪些 特性該接收者有獲授權權存取(5 040)並提供該接收者該編 馬方案的子集合(5 05 0),該子集合僅包括關於使用者被授 權存取之特性的編碼方案。 可在追蹤過程中多 點如在儲存追蹤資訊至一標記之前或該追蹤資訊被存放在 ~共享ITS之前。可執行方法5000無論追蹤資訊何時被釋 玫與該傳送者何時想要控制追蹤資訊的存取。 如第51圖所述’在執行對於項目之收集之一方法 中,一消費者接收關於項目收集之編碼的追蹤資訊。藉由 將追蹤資訊中每個明確特性的每次利用其對應的明確編码 方案加以編碼以編碼該追蹤資訊(5丨丨〇)。該消費者也接收 該編碼方案的一子集合’其僅包含關於該接收者被授權有 取之特性的編碼方案(5120)。最後,該消費者解碼該接收 者被授權存取的特性(513〇)。 可儲存該追縱資訊於- XML文件作為與—實體物件# 合之標記的部分。藉由一讀取器,一消費者可自該標記揭 取該取文件。該消費者也可替代地自其他位置掏取一 120 1310919 XML文件,例如從一共享ITS或其他電腦系統擷取。一文 件類型定義(DTD)或一 XML概要定義一 XML文件的中繼 資料。一 DTD可包含於一 XML文件中或分開儲存。舉例 來說,一 DTD稱呼的產品,如下表所示,產品類型、產品 ID、版本、賣主、販賣價格、產地、製造時間、有效時間、 負責人、品質等級以及重量的特性欄位: &lt; ? xml 版本=“ 1 ·0” 編碼=“UTF-8” ?&gt; &lt;!項目 產品(產品類型、產品ID、版本、賣主、販賣 價格、產地、製造時間、有效時間、負責人、品質等 級)&gt; &lt;!項目產品類型(#PCDATA)&gt; &lt;!項目產品 ID(#PCDATA)&gt; &lt;!項目版本(#PCDATA)&gt; &lt;!項目 賣主.(#PCDATA)&gt; &lt;!項目販賣價格(#PCDATA)&gt; &lt;!項目產地(#PCDATA)&gt; &lt;!項目製造時間(#PCDATA)&gt; &lt;!項目有效曰寄間(#PCDATA)&gt; &lt;!項目 負責人(#PCDATA)&gt; &lt;!項目品質等級(#PCDATA)&gt; &lt;!項目產品組(產品+)&gt; 基於此DTD檔案的一 XML文件於下表: 121 1310919 &lt; ? xml 版本=“ 1.0” 編碼=“ UTF-8” ? &gt; &lt;!文件類型 產品組糸統 產品級· d 1 d &gt; &lt;產品組&gt; 〈產品&gt; &lt;產品類型&gt;χχχχ&lt;/產品類型&gt; &lt;產品 ID&gt;45EF76345&lt;/產品 ID&gt; &lt;版本&gt;E3DF67&lt;/版本&gt; &lt;賣主&gt;AAA&lt;/賣主&gt; &lt;販賣價格&gt; 1 9 8 8 - 1 2-2 8&lt;/販賣價格&gt; &lt;產地&gt;621 &lt;/產地〉 〈製造時間&gt;2000-1 2-28&lt;/製造時間&gt; &lt;有效時間&gt;2002-12-28&lt;/有效時問&gt; &lt;負責人&gt;Kelly De&lt;/負責人&gt; &lt;產品等級&gt;6&lt;/產品等級&gt; &lt;/產品&gt; &lt;產品&gt; &lt;產品類型&gt;χχχγ&lt;/產品類型&gt; 〈產品 ID&gt;45E003 1 23&lt;/產品 ID&gt; 〈版本&gt;9FD56&lt;/版本&gt; &lt;賣主&gt;BBB&lt;/賣主&gt; 〈販賣價格&gt;3.4&lt;/販賣價格&gt; 〈產地&gt;621&lt;/產地〉 〈製造時間&gt;2000-02-28&lt;/製造時間〉 122 1310919 〈有效時間&gt;2002-02-28&lt;/有效時間〉 〈負責人&gt;1^¥111 Smith&lt;/負責人&gt; 〈產品等級&gt; 8 &lt;/產品等級〉 &lt; /產品&gt; &lt; /產品組〉 第52圖說明一文件系統、索引表以及編石 編碼文件用於聯繫一網路 5 2 4 0中的追蹤資訊 5245。一生產者43 01使用一索引表 523 0以轉 XML文件 5210為一編碼XML文件5215。也 引表轉換一生產者DTD檔案5220至一編碼 5225。該消費者自網路上的該生產者接收該編 編碼DTD檔案 5260/5270。該消費者使用一目 以轉換該編碼XML文件至一消費者XML文名 轉換該編碼DTD檔案至消費者DTD檔案5275 使用該消費者XML文件或該消費者DTD檔案· 該索引表 5230用於在生產者端建立XML 引表將標記名稱關連至索引值。任意地,每個 具有一對應值。該標記名稱為一般描述性的而 記名稱的編碼。應選擇對標記的預測值有效率 述用於控制該產品組XML文件的索引表可為以 標記名稱 馬文件 '該 與標記項目 換一生產者 可使用該索 DTD檔案 碼 XML或 的地索引表 -5265 &gt; 或 。該消費者 ) 文件。一索 特性欄位也 索引為該標 的編碼。前 下所述: 索引 123 1310919 產品 1 產品類型 2 產品ID 3 版本 4 賣主 5 售價 6 產地 7 生產時間 8 有效時間 9 負責人 10 產品專級 1 產品組 12A server 3 4 1 0 can receive the data to be written. The material to be written may be data stored on a mark or control material for controlling the behavior of the hardware. For example, a smart conveyor belt can receive control information for switching between the left conveyor belt and the right conveyor belt: a smart vending machine can receive control data for adjusting a target price or machine temperature. In addition, a server 3 4 1 0 enables the following functions to be utilized: Initial 100% This function initializes the interface 3400 for utilization. Initialize all hardware, including the necessary communication ports, software objects, and processes. This is a general initialization function. Specific hardware details can be set in a specific hardware settings file. 109 1310919 Termination This function terminates the use of this interface 3400. This is the reverse function of initialization. All hardware is released, the communication port is closed and all related software objects and processes are terminated (unless they are used by other processes). This is a generic termination feature. Specific hardware details can be set to specific hardware profiles. Detection Flag This function detects whether the marker is now readable and how many markers can be read. Defining Logical Tag Types This function defines the logic. Tag type for a particular tag. This logical tag type describes the organization of the material on the tag. The exemplary electronic marker 3 5 0 0 shown in Figure 3 illustrates this. As shown, the user profile on the tag is physically composed of 3 2 of the original data block. Logically, however, it has three named data blocks: an item number ("ARTNR") 35 10 , a description of the item ("ARTDESC") 3520, and its price ("PRICE") 3 53 0. As shown, the length and the start address of the field are not necessarily the same as the block length and start address. The logical tag type defines the name, the start address, and the length of each data block, its data type (to easily map the field to the application data), and a description of each field. This logical tag type also defines the location for storing a tag identification token. This logical tag type definition 110 1310919 can be extended to include additional information. Get Logical Tag Type Description Polar Field Name This function gets information about a logical tag type. This feature will normally be used to get the field name as well as the field length and data type. Start/End Continuous Read This function reads data from specific fields of all tags and can be read when this function is performed. A parameter indicates whether a separate or continuous read mode is required. For continuous mode, the server buffers all information that reads the tag. Each of the calls to the read function clears this buffer in continuous mode. However, a call in split mode does not clear the buffer. Read block from a specific tag This feature is similar to the previous feature. The difference is that only fields from a single tag with a specific tag ID are read. It may be necessary to read multiple tags to identify the tag with that particular tag ID. Write field to multiple tags This function writes the same data to a specific field of all tags, which can be written when this function is performed. The block has a name and depends on the type of tag that defines the tag. The same data is written to all tags. You can use this feature to write to a large number of tags, for example at the end of a production line. 111 1310919 Write field to specific tag This function is marked - the # & type of the specific tag. The block that was written. No operation has been made here. Write data to the block in the field of reader writer operation. This field has a name and the current tag is dependent on its UID. The data is only written to all of the data specified in the tag block and the data field can be locked with either of the two write functions, as long as the hardware supports the feature.彳 Write and lock the field at the same time, or — the previously written field can be locked just without overwriting its data. Specific hardware calls A 1 hardware may provide some functionality beyond this interface. This feature is available to the customer. This feature provides a mechanism to call directly from the application via a specific hardware. Incorrect operation ^ When a communication error occurs, the hardware device 3420 or the server 3410 first attempts to resolve the error caused by itself, for example, by retrying an operation several times. When the low-order error operation fails, the interface 34 provides information about where the error occurred so the application can take appropriate action. In addition to the generic error code of the wrong type of error, a detailed description of the error is provided. The interface 3400 recognizes at least the following types of error conditions: 112 1310919 (1) The interrogator did not respond: the interrogator could not be initialized. (2) Read error: The η flag is detected, but only m is correctly read] (m&lt;n). No flags in this field are not error conditions. (3) Write error: The tag cannot be written, either because there is no tag in the innocent pad or because there are some specific write issues such as locked fields or generally fail. (4) There is no hardware support. Home is a data lock feature that may not have hardware support. 5 • Tracking Information Filtering, Filtering, and Encryption The following sections describe an implementation in which the tracking information is compressed, filtered, or encrypted before it contacts a business. It will be described in the context of a solution and involves a producer and a consumer. The producer or consumer may be a manufacturer, a distributor or a retail machine or any other location or part of a location that processes the marked item as shown in Figure 43, a producer 4301 sends a shipment 4303 Consumer 4302. When the consumer 43 02 receives the shipment 43 03, the erased tag reader system 4 3 0 6 reads the information from the container tag 4 3 0 7 and the entry 4 3 0 8 . In order to confirm the shipment 4 3 0 3, the consumer needs shipping content information 4309 from the producer 4301. This shipment 4309 can contain the UID of the container and all UIDs in the container. Other information related to each item, such as the color of the item, may be combined with the UID of the item or externally stored on the mark. Through the implementation of a business structure, the target of the target is 43 02 information purpose color, a pass 113 1310919 network 4 3 1 0 such as the Internet, the consumer 4 3 0 2 can 43 0 1 receive shipping information 43 09 and may also transmit status update asset 430 1 . The area located in the consumer location ITS431 1 retrieves the information from the system 4 3 6 and pairs the tag information with the shipment | As shown in Fig. 45, a method 4500 for tracking information between a producer and a consumer can receive a plurality of starts by a producer, each identification code uniquely identifying a related item (45 1 0) &lt;; The ID can be read from the tag attached to the item. In order to make item tracking feasible, each tag carries a code about the item, for example, divided into an 8-bit header (bits 0-7) 4510 for the field: ePC administrator (bits 8-3 5) 4620, object rhyme 36-59) 4630 and serial number (bit 60_95) 4640. Each unity organization has a unique code for each individual item in the ePC administrator field that has a unique coded product category that is uniquely encoded in the item category. A unique code is used in the serial number except for ePC. UIDs. The producer classifies the identification code into one or more (4520). Each set of identification codes may correspond to all of the basketballs of a particular type of item I from a particular manufacturer. For each set of identification codes, the producer recognizes that the excess of the code is common for each set of codes (4 5 3 0). For example, the 4th 7th ePCs for all basketballs of a particular manufacturer include the self-producer's message to the student's mark, the r-reader, the communication number, and the identification code. Class (the bite is already in the set. In a group of intercepts. Also can class i identify the code (for example: out: part, the figure shows, a redundant part 114 1310919 points 4701 - in particular, the ePCs share The same ePC pipe type. This is redundant in the ePC's hierarchical architecture. The producer creates a file containing one or more groups (4 5 40). However, in this document, the ePC can calculate most of the size. For example, as shown in Figure 47, a shipping document contains items - which contain ePCs for each shipment item. When the project's compilation of the ePC becomes an important part of the file size. To reduce the size of the file, the producer 4301 organizes For each set of identification codes, the extra portion of the code will be listed alongside the omitted redundant code portion. Here the ePC hierarchy is designed to be compressed with each ePC for example, for all packages and Shipment to It is not necessary to include all the ePCs of each basketball in the basket file of one location. Conversely, the shipping file may only contain the types of objects related to the ePC entry and an ePC prefix 4 802. 4500 similar masking techniques to other contexts. For example, the size of a small production order in production can be applied. In a new factory that prepares a manufacturing project, a production order is usually drawn up, which lists the bid for each item. This situation is still true for the head, ePC administrator, and ePC object type. By applying Method 4 5 0 0, this redundancy can be reduced without listing all the redundant parts for each item and only the serial number is listed. The staff and the material t are born. The identification code is divided into large-level information of the file. When the number is increased, the file is output once and each method is available. The ball is in the shipment as shown in Figure 48. A member of the project 〇 other than the shipment below the production line, an ePC. Even the same time production orders, e PC s, can save 115 1310919 can be by the vector. Continuously to further reduce the size of the file (shipping, production or other), it is not necessary to list the serial numbers of all production items. Otherwise, as described below, the serial number of the first established project ("EPC_BASE") The total number of items produced by the project (eg 1 000). Additional information about each item is like the color of the item, which can be listed separately for each item as follows. <Product_Order_ID = 123 4 5 66&gt; <Item_list number=1000 EPC_ prefix=01.000A89.00016F&gt;&lt;EPC_base&gt;00 1 68 1 23&lt;/EPC_ &bottom&gt; <item> &lt;color&gt;red&lt;/color&gt;;&lt;/project&gt; <item> <color> red. color&lt;/color&gt;&lt;/item> <item> <color> red&lt;/color&gt;&lt;/item&gt;&lt;/Items-List&gt;&lt;/Products-Orders&gt; 116 1310919 Along a supply chain, there will usually be items marked and unmarked. In addition, only certain types of items such as pallets or packages are tagged with RFID. In addition, each company can mark the project. For example, a shipping company can mark its shipping package to automate its library logistics process. Therefore, there may be RFID tags on the item, the package, the pallet, and the container level, and the tags may come from different businesses. However, a simple reader/interrogator cannot distinguish between a project and the project container from the project. As a result, all read UIDs must be reported to a central system and filtered. This process is inadequate and cumbersome for a system that must process millions of reports in a single day. A task assignment and serial number used by an enterprise ePC administrator to control the type of object. The company can also define its own summary of physical objects that are attached to the company's manufacturing projects. For example, pallets and packages produced by the manufacturer may or may not have their own ePC markings. However, in the context of a transportation company, there is a container for shipping physical items. The delivery shipping process from one shipping area to another can be performed quickly by simply confirming the pallet or package rather than its full context. This method requires the shipping company to tag the container with its own ePC. The reader can be adjusted to take a specific type of ePC style. For example, the reader can be adjusted to register a container starting from the character "1" in the object type portion of the ePC. The actual XMK filtering profile would look like this: <container-category>0 1.1 234566.1 XXXXX&lt;/container_category 117 1310919 In this example, the Xs is a mega character, which is located in the string forming the ePC Medium; the reader will receive any data located at these locations. Setting up a reader in this way allows the reader to filter the ePCs it reads and to check only the type of container indicated in this summary. Therefore, filtering can reduce the amount of information that is sent from the reader to the monitoring application or process, such as the shipping confirmation process. Figure 49 illustrates a method 4900 for filtering tracking information. Filtering can occur at different stages in the delivery process (i.e., through multiple consumers) and in a particular consumer by the picker or reader system. For example, as described above, filtering occurs at the tag reader level. Alternatively or additionally, a consumer's ITS may also filter the data it receives from the tag reader. Receives an identification code combined with multiple items, including separate items and a container for the item (4910). Each identification code (e.g., ePC) is a word _ that uniquely identifies the combined item. The identification code can be retrieved from a plurality of source homes as a tag reader, a shipping file or an ITS (shared or regional). A character is placed in each identification code that indicates the only individual item or project container for the item (4920). As described above, the container can be distinguished from a separate item having "1" in the container as the beginning character of the encoded object category portion; however, other characters can be used as well as the Yuyuan position based on the settled word. The element determines whether the identification code corresponds to a separate item or a container (4930). When such a decision is made on the mark reader level, the mark reader can distinguish between the independent item and the project container, and use the separately to filter out Reads that are unrelated to reading 118 1310919 information recipients. For example, if the recipient is a shipping company, it may only want to know the label for each tag container, but not the item itself. In this case, a higher order component in the reader or system can filter out the code for the individual item and send tag information about the container to the recipient. Controlling access to tracking information In a cross-enterprise computer scenario, this tracking information can be consumed by multiple consumers. However, the producer may not necessarily want all consumer access to a decentralized level. For example, the manufacturer may record information about a shipment such as "responsible person" or "quality level", which may be accessed by certain consumers (eg tax bureaus), but other consumers have no access. In one implementation, access to tracking information is controlled by providing a portion of the consumer file. For example, a shipping company may only need (or be authorized to know) the total number of shipments, but the shipping authority does not need to know (or is not authorized to know) other (eg, color, price) of the shipment. However, transmitting only the same encoded file to all consumers will be more efficient. Therefore, an alternative implementation provides the same file to all consumption but in an encoded format. Each consumer is then individually provided with a selection to decode only a portion of the file. The encoding and decoding can be completely transparent to the external 43 12 such as an ERP system. In other words, the input and output of the trace information can be a completely unencoded file. A registered capital is only transmitted by the same person. If it is only necessary to know the characteristics of the company, the selection department should chase 119 l3l〇9i9 as shown in Figure 50, and perform a control access tracking information. In method S, a producer establishes tracking information about a set of items. The tracking information represents each item with one or more characteristics and a corresponding value (5〇1〇). The producer encodes the tracking information by encoding each of the explicit characteristics of the tracking information with its corresponding explicit coding scheme. The producer transmits the encoded tracking information to a recipient (5030), determines which characteristics the recipient has authorized access to (5 040), and provides a subset of the recipient's programming scheme (5 05 0), This subset only includes coding schemes for the characteristics that the user is authorized to access. It can be done during the tracking process, such as before storing the tracking information to a mark or before the tracking information is stored in the ~Shared ITS. Executable method 5000 is whenever the tracking information is released and when the sender wants to control access to the tracking information. As described in Fig. 51, in a method of performing collection of items, a consumer receives tracking information about the code collected by the item. The tracking information (5丨丨〇) is encoded by encoding each of the explicit features of the tracking information with its corresponding explicit coding scheme. The consumer also receives a subset of the coding schemes that contain only coding schemes (5120) regarding the characteristics that the recipient is authorized to take. Finally, the consumer decodes the characteristics (513 〇) that the recipient is authorized to access. The tracking information can be stored in the - XML file as part of the markup with the - physical object #. With a reader, a consumer can retrieve the retrieved file from the tag. The consumer can alternatively retrieve a 120 1310919 XML file from another location, such as from a shared ITS or other computer system. A file type definition (DTD) or an XML profile defines the relay data of an XML file. A DTD can be included in an XML file or stored separately. For example, a DTD-named product, as shown in the table below, product type, product ID, version, vendor, selling price, origin, manufacturing time, effective time, responsible person, quality level, and weight characteristics field: &lt; ? xml version = "1 · 0" encoding = "UTF-8"? &gt;&lt;! project product (product type, product ID, version, seller, selling price, origin, manufacturing time, effective time, person in charge, quality level) &gt;&lt;! project product type (#PCDATA)&gt;&lt;;!Project Product ID (#PCDATA)&gt;&lt;!Project Version (#PCDATA)&gt;&lt;!ProjectSeller.(#PCDATA)&gt;&lt;! Project Selling Price (#PCDATA)&gt;&lt;! Origin (#PCDATA)&gt;&lt;! Project Manufacturing Time (#PCDATA)&gt;&lt;! Project Effective 曰 间 (#PCDATA)&gt;&lt;! Project Leader (#PCDATA)&gt;&lt;! Project Quality Level (#PCDATA)&gt;&lt;! Project Product Group (Product +)&gt; An XML file based on this DTD file is in the following table: 121 1310919 &lt; ? xml version = "1.0" Encoding = "UTF-8"? &gt;&lt;! file type product group system product level · d 1 d &gt;&lt;productgroup&gt; <product> &lt;product type&gt;χχχχ&lt;/product type&gt;&lt;productID&gt;45EF76345&lt;/ Product ID &gt;&lt;Version&gt;E3DF67&lt;/Version&gt;&lt;Seller&gt;AAA&lt;/Seller&gt;&lt;TrafficPrice&gt; 1 9 8 8 - 1 2-2 8&lt;/Selling Price&gt;&lt;Place of Origin &gt;621 &lt;/Place of Origin> <Manufacturing Time>2000-1 2-28&lt;/Manufacturing Time&gt;&lt;EffectiveTime&gt;2002-12-28&lt;/EffectiveTime&gt;&lt;Responsible&gt;KellyDe&lt;/person in charge&gt;&lt;productgrade&gt;6&lt;/productgrade&gt;&lt;/product&gt;&lt;product&gt;&lt;producttype&gt;χχχγ&lt;/producttype&gt; <product ID>45E003 1 23 &lt;/Product ID&gt;<Version&gt;9FD56&lt;/Version&gt;&lt;Seller&gt;BBB&lt;/Seller&gt; <Selling Price>3.4&lt;/Selling Price&gt; <Place of Origin>621&lt;/Place of Origin> Manufacturing time &gt;2000-02-28&lt;/manufacturing time> 122 1310919 <effective time>2002-02-28&lt;/effective time> <person in charge>1^¥111 Smith&lt;/person in charge&gt; <product grade &gt; 8 &lt;/ Product Level> &lt; / item &gt; &lt; / Product Group> 52 a view illustrating a file system, the index table file for encoding and encoding stone contact tracking information 52455240 in a network. A producer 43 01 uses an index table 523 0 to convert the XML file 5210 into an encoded XML file 5215. The table is also converted to a producer DTD file 5220 to a code 5225. The consumer receives the encoded DTD file 5260/5270 from the producer on the network. The consumer uses a single item to convert the encoded XML file to a consumer XML file name to convert the encoded DTD file to the consumer DTD file 5275 using the consumer XML file or the consumer DTD file. The index table 5230 is used in production The client side establishes an XML index table to associate the tag name to the index value. Optionally, each has a corresponding value. The tag name is a generic descriptive code of the name. The index value of the markup should be selected to be efficient. The index table used to control the XML file of the product group can be a tag name name. The file can be used to replace the markup item with a place index. The producer can use the DTD file code XML or the ground index table. -5265 &gt; or. The consumer) file. A cable feature field is also indexed as the code of the target. Previous Next: Index 123 1310919 Product 1 Product Type 2 Product ID 3 Version 4 Vendor 5 Price 6 Origin 7 Production Time 8 Effective Time 9 Responsible Person 10 Product Level 1 Product Group 12

該索引表中的索引值可為任意的,因而使該編碼 xml文 件在沒有索引表的情況下是很難被解譯的。The index value in the index table can be arbitrary, thus making the encoded xml file difficult to interpret without an index table.

基於該索引表,一 XML文件被傳送至稱為編碼XML文件 5215的一中間資料文件中。一編碼XML文件對應至 上述與該索引表一起被建立的XML文件為: &lt;? Xml version: “1,0” 編碼=“UTF-8” &gt; &lt;!文件類型12系統 “ 12.dtd” &gt; &lt;12&gt; &lt;1&gt; &lt;2&gt;XXXX&lt;/2&gt; &lt;3&gt;45EF76345&lt;/3&gt; 124 1310919 &lt;4&gt;E3DF67&lt;/4&gt; &lt;5&gt;AAA&lt;/5&gt; &lt;6&gt;198 8-12-28&lt;/6&gt; &lt;7&gt;62 1 &lt;/7&gt; &lt;8&gt;2000-12-28&lt;/8&gt; &lt;9&gt;2002-12-28&lt;/9&gt; &lt;10&gt;Kelly De&lt;/10&gt;Based on the index table, an XML file is transferred to an intermediate data file called encoded XML file 5215. An encoded XML file corresponding to the XML file created above with the index table is: &lt;? Xml version: "1,0" encoding = "UTF-8" &gt;&lt;! file type 12 system " 12.dtd &gt;&lt;12&gt;&lt;1&gt;&lt;2&gt;XXXX&lt;/2&gt;&lt;3&gt;45EF76345&lt;/3&gt; 124 1310919 &lt;4&gt;E3DF67&lt;/4&gt;&lt;5&gt;AAA&lt;/5&gt;&lt;;6&gt;1988-12-28&lt;/6&gt;&lt;7&gt;62 1 &lt;/7&gt;&lt;8&gt;2000-12-28&lt;/8&gt;&lt;9&gt;2002-12-28&lt;/9&gt;&lt;10&gt;KellyDe&lt;/10&gt;

&lt;11&gt;6&lt;/11&gt; &lt;/l&gt; &lt;1&gt; &lt;2&gt;XXXY&lt;/1&gt; &lt;3&gt;45E003 1 23&lt;/2&gt; &lt;4&gt;9FD56&lt;/3&gt; &lt;5&gt;BBB&lt;/5&gt; &lt;6&gt;3.4&lt;/6&gt; &lt;7&gt;621&lt;/7&gt;&lt;11&gt;6&lt;/11&gt;&lt;/l&gt;&lt;1&gt;&lt;2&gt;XXXY&lt;/1&gt;&lt;3&gt;45E003 1 23&lt;/2&gt;&lt;4&gt;9FD56&lt;/3&gt;&lt;5&gt;BBB&lt;/5&gt;&lt;6&gt;3.4&lt;/6&gt;&lt;7&gt;621&lt;/7&gt;

&lt;8&gt;2000-02-28&lt;/8&gt; &lt;9&gt;2002-02-28&lt;/9&gt; &lt;10&gt;KeVin Smith&lt;/10&gt; &lt;1 1&gt;8&lt;/11&gt; &lt;/l&gt; &lt;/12&gt; 同時,基於該原始DTD檔案建立一編碼DrD檔案。前述 125 1310919 對應至DTD檔案並與該索引表一同建立的一編碼DTD檔 案為: &lt; ? xml 版本二“ 1 o ” 編碼=“ UTF_8” ? &gt; &lt;!項 S 1(2 , 3 , 4 , 5 , 6 ,7,8,9,10,11 )&gt; &lt;!項 @ 1 (#PCDATA)&gt; &lt;!項 a 2(#PCDATA)&gt; &lt;!項 S 3(#PCDATA)&gt; &lt;!項 g 4(#PCDATA)&gt; &lt;!項 g 5(#PCDATA)&gt; &lt;!項 g 6(#PCDATA)&gt; &lt;!項 a 7(#PCDATA)&gt; &lt;!項 a 8(#PCDATA)&gt; &lt;!項 a 9(#PCDATA)&gt; &lt;!項 g 10(#PCDATA)&gt; &lt;!項 目 H(l+)&gt; 當該 消 費者編碼該文件時 ,該消費者可改變該標 更符合消費者自身命名傳統。 為了控制存取 編碼該資訊進一步的好處為該編碼標記名稱比未編碼 的標記名稱佔用較少的空間,該未編碼的標記名稱通常是 描述性的且可能非常長。可選擇簡潔的索引值像是之前提 到的簡單數字索引方案。 標記具有有限的記憶體或空間。因此,藉由使用簡潔索 126 1310919 引直更多的追蹤資訊(例如特性攔位)可包含在標記中。類 似地,當該追蹤資訊穿越一網路通訊時,較之於未編碼版 本可使用較少的頻寬傳遞該編碼資訊。 第5 3圖說明用於檢查適當的索引表被用於建立一編碼 XML文件的一種方法。本發明系統首先檢查該索引表是否 需要更新(5 3 1 0)。如果不用,便利用該既存的索引表建立 一編碼XML文件或編碼DTD文件。如果該索引表需要更 新,便建立一新的索引表並隨後用於建立一編碼 XML文 件或編碼DTD檔案(5330)。 在一網路上傳送該編碼XML文件或儲存在與一實體物 件結合的一智慧標記中。在該消費者瑞,使用一目的索引 表以將該文件解碼。提到該索引表並如下例所示,該目的 索引表聯繫標記名稱與索引值。 標記名稱 索引 產品 1 產品類型 2 產品識別 3 版本 4 賣主名稱 5 生產時間 8 有效時間 9 產品組 12 所有位於該目的索引表的索引必定出現在對應的來源 127 1310919 索引表,該來源索引表用於建立該編碼文件。然而,所有 位於索引表中的索引可能不會出現於對應的目的索引表。 該 XML文件的消費者接收該標記名稱以及關於那些生產 者授權該消費者分享之僅有特性欄位的索引。舉例來說, 如果一製造者該XMI文件而該消費者為一零售商,且該製 造者不希望該零售商看見名為負責人及產品等級的特性欄 位,則這些索引便不會出現在該零售商的目的索引表中。 與該目的索引表中的一特定索引結合的標記名稱與其 對應的索引表可以足不同的。因此,該消費者可調整該名 稱以使其與該消費者的應用程式一致。 基於上述的目的索引表以及編碼的DTD檔案,該消費者 將看見下列DTD檔案: &lt; ? xml 版本=“ 1 ·0” 編碼=“ UTF-8” ? &gt; &lt;!文件類型 產品組系統“產品組.dtd” &gt; &lt;!項目 產品(產品類型、產品識別、版本編號、賣主 名稱、販賣價格、產地、製造時間、有效時間&gt; &lt;!項目產品類型(#PCDATA)&gt; &lt;!項目產品 ID(#PCDATA)&gt; &lt;!項目版本(#PCDATA)&gt; &lt;!項目 賣主(#PCDATA)&gt; &lt;!項目販賣價格(#PCDATA)&gt; &lt;!項目 產地(#PCDATA)&gt; &lt;!項目製造時間(#PCDATA)&gt; 128 1310919 &lt;!項目有效時間(#PCDATA)&gt; &lt; !項目產品組(產品+ ) &gt; 基於上述的目的索引表以及該編碼 XML 會看見以下XML文件: &lt; ? xml 版本=“1.0” 編碼=“UTF-8” &lt;!文件類型產品組系統“產品組;dtd’ &lt;產品組&gt; &lt;產品&gt; &lt;產品類型&gt;χχχχ&lt;/產品類型&gt; 〈產品識別&gt;45EF76345&lt;/產品識別〉 〈版本編號&gt;E3DF6 7&lt;/版本編號&gt; 〈賣主名稱〉AAA&lt;/賣主名稱&gt; 〈販賣價格&gt;1 98 8- 1 2-28&lt;/販賣價格5 〈產地&gt;621&lt;/產地&gt; 〈製造時間&gt;2000_12-28&lt;/製造時間&gt; 〈有效曰奪間&gt;2002-1 2-28&lt;/有效時間 &lt;/產品&gt; &lt;產品&gt; &lt;產品類型&gt;XXXY&lt;/產品類型&gt; 〈產品識別&gt;45Ε003 1 23&lt;/產品識別〉 〈版本編號&gt;9FD56&lt;/版本編號〉 〈賣主名稱&gt;BBB&lt;/賣主名稱&gt; 〈販賣價格&gt; 3 · 4 &lt;/販賣價格&gt; 文件,該消費者 ? &gt; &gt; &gt; 129 1310919 〈產地&gt;621&lt;/產地&gt; &lt;製造曰奪間&gt;2000 —02 —28&lt;/製造時間&gt; 〈有效時間&gt;2002 — 02 —28&lt;/有效時間&gt; &lt;/產品&gt; &lt; /產品組&gt; 可實施本發明於數位電子電路中,或電腦硬體、軟體 或上述兩者之結合中。可實施本發明為一電腦程式產品 即一電腦程式明白地包含於一資訊載體中,例如在一機 可讀取的裝置或一傳送訊號,其用於被資料操作裝置執 或控制該裴置的操作。一電腦程式可以任何程式設計語 的形式寫成,包含編譯或解譯語言,且其可以任何形式 部署,包含作為一獨立程或為一組件、元件、子程式或 他適合用於一電腦情境中的單位。可部署一電腦程式以 一電腦、同一位置上或分佈於多個位置的多個電腦上執 並由一通訊網路互連。 可藉由一個或多個可程式化處理器以實行本發明的 法步驟,該處理器執行一電腦程式以藉由操作輸入資料 產生輸出資料而執行本發明的功能。方法步驟也可由特 目的邏輯電路如一 FPGA(現場可程式化閘陣列)或 A SIC (特定應用程式整合電路)執行,而也可實行本發明 儀器為該特殊目的邏輯電路。 適用於一電腦程式之執行的處理器包括:例如一般的 及特別的目的微處理器,以及任何數位電腦中的任何一 器 行 言 被 其 在 行 方 並 殊 的 以 個 130 1310919 或多個處理器。一般來說,一處理器會自一唯讀記憶體或 一亂數存取記憶體或其兩者接收指令以及資料。·一電腦的 必要元件為一用於執行指令的處理器以及用於儲存指令及 資料的一個或多個記憶體裝置。通常一電腦也會包含一個 或多個用於儲存資料的大量存取裝置例如磁、磁光碟或光 碟,或操作地與其結合以向其傳送資料或自其接收資料或 兩者皆有。適合包含電腦程式指令以及資料的資訊載體包 含所有形的非揮發性記憶體一包含例如半導體記憶裝置像 是 EPROM、EEPROM以及快閃記憶裝置:磁碟像是内部 硬碟以及行動碟:磁光碟:以及 CD_ROM與DVD_ROM光 碟。該處理器以及記憶體可由特別目的邏輯電路補充,或 包含於其中。 為了提供與一使用者的互動,可在電腦上實施本發明, 該電腦具有一用於顯示資訊給使用者的顯示裝置像是一 CRT(陰極射線管)或LCD(液晶螢幕)顯示器,以及一鍵盤與 一指向裝置像是一滑鼠或一軌跡球,使用者可用其提供輸 入至該電腦。也可使用其他種類的裝置以提供與消費者的 互動,例如提供給消費者的回餚可為任何型的威覺回饋像 是視覺回饋、聽覺回饋或觸覺回饋:且來自消費者的輸入 可以任何形式被接收,包括聽覺的、口述的、或觸覺的輸 入° 可在一電腦系統實施本發明,該電腦系統包括一後端元 件傢是一資料伺服器或包括一中介軟體元件傢是一應用程 131 1310919 式伺服器或句杠 ^ 飞i括一刚鳊凡件像是具有一地理使用者介面或 -網路瀏覽器的客戶瑞電腦’透過上述元件—使用者可與 本發明的一種實施或是任何該後端、中介軟體或前瑞元件 的·且σ互動。|發明系統的元件可藉由像是-通訊網路的 任何數值資料通訊的形式或媒介互連。通訊網路的例子包 括—區域網路(“TAN” 、、 、 ^ )—廣域網路(“ WAN” )以及一網 際網路。 ’ 該電腦系統可包含客戶及飼服器。一客戶及祠服器通常 甚遠且通常透過一通訊網路互動。客戶及词服器的關 係由於電腦程式在各自的電 J €腦上執打且彼此具有一客戶伺 服器關係而產生。 本發明已經用特殊的具體實施例及方案加以插述。其他 的具體實施例位於申請專利範圍+。舉例來說,本發明的 步驟可用一不同的, 頂序加以執行且仍可達到想要的結 果。本發明系統是彈性的曰担μ _ 的且k供許多關於追蹤項目的商業 方法。在一種方法中,一個忐 办 個或多個客戶向一服務提供者提 供的本發明系統訂購,該服兹_担加心 占服務供者將該服務分配至像是 網際網路的一種網路中。 、在此情況中,客戶不需要取得元件或整體系統,因而節 4資金成本。該客戶士 &gt;5^·缺丨L # IS1 也了替代地取得元件或整體系統,因 而節省操作成本。本於明糸站ids蒙方 知月系統也可替代地支援上述商業 法的任何組合。例如某此完玲疋&amp;丄 0 jib 呆二客戶可向本發明系統訂購立系一 客戶可取得元件或整體系統。 132 1310919 其他方案位於申請專利範圍中。本發明系統支援某種範 圍之新的或加強的應用程式,該應用程式遍及自一區域至 一全球範圍的產業。本發明系統的其他應用程式包括供應 鏈管理、資產追蹤管理、安全及存取控制、運送、收費、 銷售應用程式點以及行李處理。以下將進一步說明這些例 子。 供應鏈管理 RFID 系統理想地適合識別於一裝配流程(如汽車或農 業裝備製造)中移動的高單位·高價產品。RFID系統也提供 對於永久識別產品載體如箱子、條板箱以及貨盤不可或缺 的可靠度。在供應鏈管理中的其他應用程式包括在製品追 蹤及包裹運送。 資產追蹤及管理 資產追蹤及管理應用程式包括那些用於監控裝備、人員 以及文件在一空間如大樓、堆置場或總站中流動的應用程 式,以加強像是對於資產的控制及保持項目包括個人的良 好追蹤。 安全及存取控制 有價值的裝備及個人資源的移動及使用可透過附加於 裝備或由裝備或個人攜帶的應答器來監控。應答器也可包 含於一信用卡大小的安全標章中。家庭安全呼叫系統以及 133 1310919 大樓存取為安全及存取控制應用程式的兩種例子。運: 應答器可附著至載具(例如飛機、火車、卡車)並可包 於該載具及其内容的重要資訊。運送應用程式包括飛 別、火車及裝運容器追蹤、公共運輸票務以及秤車站 程式。 收費 收費應用程式包括附加一應答器至”載具。該應答 送識別一預付帳戶的一種編碼至一讀取器,該讀取器 從該帳戶扣除費用。 銷售點 這些應用程式包括零售項目、贗品預防以及銷售交 電子監視並通常包括用低成本的應答器標記獨立的零 目,該應答器本質上為動態標記。 行李處理 在一行李處理應用程式,利用RFID應答器像是智 籤將航空行李標記,以允許航空行李處理操作從一旅 記進入機場開始至該旅客到達其最終目的地為止追 李。 【圖式簡單說明】 第1圖為一方塊圖描述依照本發明的一系統。 含關 機識 應用 器傳 自動 易的 售項 慧標 客登 蹤行 134 1310919 第2圖顯示一唯一識別碼的範例。 第3圖為一方塊圖描述本發明系統的一種實施。 第4圖為一流程圖描述一項目引入過程。 第5圖為一流程圖描述一溫度感應裝置以及一 RFID標記 的操作。 第6圖為一流程圖描述本發明系統對一事件如載入箱子至 一托盤上做出的回應。 第7圖為一流程圖描述一升級操作。 第8圖為一流程圖描述升級、讀取以及警示操作。 第9圖為一流程圖描述一供給操作。 第 1 0圖為一方塊圖描述警示確認以及資料流入或流出一 標記的一種方案(scenario)。 第 11圖為一方塊圖描述警示確認以及資料流入或流出一 標記的另一種方案 第1 2圖為一流程圖描述資料流動過程的一種態樣。 第13圖為一流程圖描述資料流動過程的另一楂態樣。 第1 4圖為一方塊圖描述本發明系統的一種實施。 第1 5圖為一方塊圖描述系統内的軟體元件。 第1 6圖為一方塊圖描述關於儲存、改變以及詢問追蹤資 訊的機制。 第1 7圖為一方塊圖描述資產列表功能。 第18圖為一方塊圖描述一裝運方案。 第19圖為一方塊圖描述另一裝運方案。 135 1310919 第2 0圖為一方塊圖描述用於資料復原的機制。 第2 1圖為一方塊圖描述一用於回應詢問的機制。 第22圖為一方塊圖描述一用於回應詢問的機制。 第23圖為一方塊圖描述一用於回應詢問的機制。 第24圖為一方塊圖描述一用於回應詢問的機制。 第2 5圖為一方塊圖描述一用於回應詢問的機制。 第2 6圖為一方塊圖描述基礎設施一大規模的實施。 第2 7圖為一方塊圖描述描述一世界模型結構。 第28圖為一方塊圖描述描述一授權模型。 第29圖為一方塊圖描述一世界模型結構。 第30圖為一方塊圖描述實施一上層節點為一叢集。 第31圖為一方塊圖描述本發明系統的一種實施。 第3 2圖為一方塊圖描述一種於一階層體系模式中使用多 個整合引擎的實施。 第33圖為一方塊圖描述一整合引擎。 第34圖為一方塊圖描述一硬體介面。 第3 5圖為一方塊圖描述一電子標記。 第3 6圖為一發明管理系統之基本架構的方塊圖,依照本 發明與項目追蹤系統共同實施該發明管理系統。 第37圖為一使用事件路由之實施的一方塊圖 第38圖為一用於事件路由之一主題結構的圖示。 第3 9圖為一用於發佈之一協定流程的圖示。 第40圖為一用於訂閱之一協定流程的圖示。 136 1310919 第 4 1圖為一用於定位事件路由器之物件名稱服務的方塊 圖。 第 42圖為一種關於使用一事件路由器以分散於多個項目 追蹤系統間的說明。 第 43圖為一用於在一製造者與一客戶間聯繫的系統的一 方塊圖。 第 44圖為一種使用一共享的項目追蹤系統用於在一製造 者與一客戶間聯繫的系統的一方塊圖。 第45圖為用於聯繫追蹤資訊的一種方法的一流程圖。 第46圖為一種電子產品編碼結構的一種說明。 第47圖為一種未遮蔽裝運文件的一種說明。 第48圖為一種有遮蔽裝運文件的一種說明。 第49圖為一種用於過濾追蹤資訊的方法的一種流程圖。 第50圖為一種用於聯繫追蹤資訊的方法的一種流程圖。 第51圖為一種用於存取追蹤資訊的方法的一種流程圖。 第52圖為一種檔案、索引表以及用於聯繫追蹤資訊的編 碼文件之系統的說明。 第53圖為一種用於檢查適當的索引表用於建立編碼的 XML文件之方法的一種流程圖。 在許多圖示中相似的參考編號及命名表示相似的元件。 【主要元件符號說明】 137 1310919 2 〇箱子被製造且貼上標記 21 ’62製造者的與物件介面元件相連的標記讀取器“看 見”標記(唯一系統識別記號,UID) 22,64物件介面元件製造並傳送一“看見事件”至通訊中 介軟體元件 23,43,66’ 72’ 82’ 91,122,126 CMC 替該事件安排 路徑至情境感知智慧元件 24情境感知智慧元件:知道物件(UID)嗎? 25情境感知智慧元件:該事件是否為“新實體物件(UID) 事件”的類型? 26情境感知智慧元件依據特定資料製造—新的實體物件 (UID) 27情境感知智慧元件儲存新物件資料 28情境感知智慧元件依據該輸入資料更新物件(uid)的狀 態及狀態歷史記錄 32 ’ 102 標言 己元件(TC) 3 3 X ,33y , 33 z防火牆 34x 製造 .者X :物件介面元件 34y 裝運 者Y : :物件介面元件 3 4 z 零售 商Z ; 物件介面元件 36, 106 通訊1 中介軟體元件(CMC) 37, 108 情境感知智慧元件(CAIC) 38, 1 10 人類 介面元件(HIC) 138 1310919 以及溫度臨界 40物件介面元件寫入如“直到何時有效 值資料至標記(UID)旅重設Tmax 41,89物件介面元件;寫入至要求的標記? 42、物件介面元件製造並傳送一 “新實體物件事件 至通訊中介軟體元件 44生產系統製造一‘‘引入實體物件事件(uid)”包括特 性、存取權利、規則與警示並將其傳送至通訊中介軟 體元件 45通訊中介軟體元件替事件安排路徑至該製造者的生產 糸統 46情境感知智慧元件傳送“物件未知事件(UID)”至通訊 中介軟體元件 50製造者附加該感應器至一貨盤上,重置其記憶體並將 其啟動 5 2感應器··是到了測量溫度的時候了嗎? 54測量溫度T並與時間戳記一同儲存至標記上的歷史記 錄 56如果T&gt;Tmax ’設定Tmax = T並儲存Tmax至標記 60標記的貨盤裝載有箱子及感應器 6 8情境感知智慧元件依據該輸入資料更新看見物件(uid) 的狀態及狀態歷史記錄 70裝運者的與物件介面元件相連的標記讀取器“看見” 在貨盤上箱子的標記(UIDs)包括該感應器標記(UID, 139 1310919&lt;8&gt;2000-02-28&lt;/8&gt;&lt;9&gt;2002-02-28&lt;/9&gt;&lt;10&gt;KeVinSmith&lt;/10&gt;&lt;11&gt;8&lt;/11&gt;&lt;/l&gt;&lt;/12&gt; At the same time, an encoded DrD file is created based on the original DTD file. The aforementioned 125 1310919 corresponds to the DTD file and is combined with the index table to create a coded DTD file: &lt; ? xml version 2 "1 o" code = "UTF_8" ? &gt;&lt;! item S 1 (2, 3, 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 )&gt;&lt;! Item @ 1 (#PCDATA)&gt;&lt;! Item a 2(#PCDATA)&gt;&lt;! Item S 3(# PCDATA)&gt;&lt;! item g 4 (#PCDATA)&gt;&lt;! item g 5 (#PCDATA)&gt;&lt;! item g 6 (#PCDATA)&gt;&lt;! item a 7 (#PCDATA) &gt;&lt;! item a 8 (#PCDATA)&gt;&lt;! item a 9 (#PCDATA)&gt;&lt;! item g 10 (#PCDATA)&gt;&lt;! item H(l+)&gt; When the consumer encodes the file, the consumer can change the logo to conform to the consumer's own naming convention. A further benefit of controlling access to encode this information is that the encoded tag name takes up less space than the unencoded tag name, which is typically descriptive and can be very long. You can choose a concise index value like the simple numeric indexing scheme mentioned earlier. Tags have limited memory or space. Therefore, by using the simple line 126 1310919 to direct more tracking information (such as feature block) can be included in the tag. Similarly, when the tracking information traverses a network communication, the encoded information can be transmitted using less bandwidth than the uncoded version. Figure 5 3 illustrates a method for checking that an appropriate index table is used to create an encoded XML file. The system of the present invention first checks if the index table needs to be updated (5 3 1 0). If not, it is convenient to create an encoded XML file or a coded DTD file using the existing index table. If the index table needs to be updated, a new index table is created and subsequently used to create an encoded XML file or coded DTD file (5330). The encoded XML file is transmitted over a network or stored in a smart tag associated with a physical object. At the consumer, a destination index table is used to decode the file. Referring to the index table and as shown in the following example, the destination index table associates the tag name with the index value. Tag Name Index Product 1 Product Type 2 Product Identification 3 Version 4 Vendor Name 5 Production Time 8 Valid Time 9 Product Group 12 All indexes located in the destination index table must appear in the corresponding source 127 1310919 index table, which is used for the index table Create the encoded file. However, all indexes in the index table may not appear in the corresponding destination index table. The consumer of the XML file receives the tag name and an index of the only property fields that the producer authorizes the consumer to share. For example, if a manufacturer has the XMI file and the consumer is a retailer, and the manufacturer does not want the retailer to see a feature field named responsible person and product level, then these indexes will not be published. Now the retailer's purpose index is in the table. The tag name combined with a specific index in the destination index table may be different from its corresponding index table. Therefore, the consumer can adjust the name to match the consumer's application. Based on the above-mentioned destination index table and the encoded DTD file, the consumer will see the following DTD file: &lt; ? xml version = "1 · 0" code = "UTF-8"? &gt;&lt;! file type product group system "product group.dtd" &gt;&lt;! project product (product type, product identification, version number, vendor name, selling price, origin, manufacturing time, effective time &gt;&lt; !Project Product Type (#PCDATA)&gt;&lt;! Project Product ID (#PCDATA)&gt;&lt;! Project Version (#PCDATA)&gt;&lt;! Project Seller (#PCDATA)&gt;&lt;! Project Selling Price (#PCDATA)&gt;&lt;! project origin (#PCDATA)&gt;&lt;! project manufacturing time (#PCDATA)&gt; 128 1310919 &lt;! project effective time (#PCDATA)&gt;&lt; ! project product group ( Product + ) &gt; Based on the above target index table and the encoded XML, you will see the following XML file: &lt; ? xml version = "1.0" encoding = "UTF-8" &lt;! file type product group system "product group; dtd &lt;Product Group&gt;&lt;Product&gt;&lt;ProductType&gt;χχχχ&lt;/ProductType&gt; <Product Identification&gt;45EF76345&lt;/Product Identification> <Version Number>E3DF6 7&lt;/Version Number&gt; Seller Name>AAA&lt;/Seller Name&gt; <Selling Price>1 98 8- 1 2-28&lt;/Selling Price 5 〈 Place of Origin &gt; 621 &lt;/Place of Origin&gt; <Manufacturing Time>2000_12-28&lt;/Manufacturing Time&gt; <effectively robbed&gt;2002-1 2-28&lt;/valid time&lt;/product&gt;&lt;product&gt;&lt;ProductType&gt;XXXY&lt;/ProductType&gt; <Product Identification> 45Ε003 1 23&lt;/Product Identification> <Version No.>9FD56&lt;/Version Number> <Seller Name>BBB&lt;/Seller Name&gt; <selling price> 3 · 4 &lt;/selling price&gt; File, the consumer? &gt;&gt;&gt; 129 1310919 <Place of Origin> 621 &lt;/Place of Origin&gt;&lt;ManufacturingUstures&gt;2000-02 - 28 &lt;/manufacturing time&gt; <effective time> 2002 - 02 - 28 &lt; / effective time &gt;&lt;/product&gt;&lt; /product group&gt; The present invention can be implemented in a digital electronic circuit, or a computer hard Body, software or a combination of the two. The invention can be embodied as a computer program product, that is, a computer program, which is explicitly included in an information carrier, such as a machine readable device or a transmission signal for being used by a data manipulation device to control or control the device. operating. A computer program can be written in any programming language, including a compiled or interpreted language, and can be deployed in any form, including as a stand-alone process or as a component, component, subroutine, or suitable for use in a computer context. unit. A computer program can be deployed to be interconnected by a communication network on a computer, in the same location, or on multiple computers distributed in multiple locations. The method steps of the present invention can be carried out by one or more programmable processors that execute a computer program to perform the functions of the present invention by operating the input data to produce output data. The method steps can also be performed by special purpose logic circuits such as an FPGA (Field Programmable Gate Array) or A SIC (Application Specific Integration Circuit), and the instrument of the present invention can also be implemented as the special purpose logic circuit. Processors suitable for the execution of a computer program include, for example, general and special purpose microprocessors, and any one of the digits of any one of the digital computers is 130 1310919 or more processors. . Generally, a processor receives instructions and data from a read-only memory or a random access memory or both. The necessary components of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer also contains one or more of a plurality of access devices for storing data, such as magnetic, magneto-optical or optical disks, or operatively coupled thereto to transmit data to or receive data therefrom or both. The information carrier suitable for containing computer program instructions and data includes all forms of non-volatile memory including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices: disks such as internal hard disks and mobile disks: magneto-optical disks: And CD_ROM and DVD_ROM discs. The processor and memory can be supplemented by, or included in, special purpose logic circuitry. In order to provide interaction with a user, the present invention can be implemented on a computer having a display device for displaying information to the user such as a CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display) display, and a The keyboard and pointing device are like a mouse or a trackball that the user can use to provide input to the computer. Other types of devices can also be used to provide interaction with the consumer, such as providing a return to the consumer for any type of visual feedback such as visual feedback, audible feedback or tactile feedback: and input from the consumer can be any The form is received, including an audible, dictated, or tactile input. The invention can be implemented in a computer system including a back end component. The home is a data server or includes an intermediary software component. The home is an application. 131 1310919 type server or statement bar ^ i 一 鳊 像 像 像 像 像 像 像 像 像 像 像 像 像 像 像 像 像 像 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 具有 ' ' ' ' ' Is the σ interaction of any of the backend, mediation software, or pre-render components. The components of the inventive system can be interconnected by any form of digital communication such as a communication network or medium. Examples of communication networks include - regional networks ("TAN", , , ^) - wide area networks ("WAN") and an Internet. The computer system can include customers and feeding machines. A client and server are often far away and usually interact through a communication network. The relationship between the customer and the word processor is due to the fact that the computer programs are executed on their respective computers and have a customer servo relationship with each other. The invention has been described in terms of specific specific embodiments and aspects. Other specific embodiments are located in the scope of the patent application +. For example, the steps of the present invention can be performed in a different, top order and still achieve the desired result. The system of the present invention is flexible and provides a number of commercial methods for tracking projects. In one method, a system or a plurality of customers subscribe to a system provided by a service provider, and the service provider allocates the service to a network such as the Internet. in. In this case, the customer does not need to obtain the component or the overall system, thus saving the capital cost. The customer &gt;5^· deficiency L # IS1 also replaces the component or the overall system, thereby saving operating costs. The ids Mongolian Zhiyue system of Mingben Station can also optionally support any combination of the above commercial laws. For example, a customer who has completed this exquisite &amp; 丄 0 jib can subscribe to the system of the present invention. The customer can obtain the component or the overall system. 132 1310919 Other options are located in the scope of the patent application. The system of the present invention supports a range of new or enhanced applications throughout a region to a global industry. Other applications of the system of the present invention include supply chain management, asset tracking management, security and access control, shipping, charging, sales application points, and baggage handling. These examples are further explained below. Supply Chain Management RFID systems are ideally suited for identifying high-unit, high-priced products that move in an assembly process such as automotive or agricultural equipment manufacturing. The RFID system also provides reliability that is indispensable for permanently identifying product carriers such as boxes, crates, and pallets. Other applications in supply chain management include work in process tracking and package delivery. Asset Tracking and Managed Asset Tracking and Management Applications include applications for monitoring equipment, personnel, and documents flowing in a space such as a building, yard, or terminus to enhance control and retention of assets, including personal Good tracking. Security and Access Control The movement and use of valuable equipment and personal resources can be monitored through transponders attached to equipment or carried by equipment or individuals. The transponder can also be included in a credit card sized security stamp. Home security call systems and 133 1310919 building access are two examples of security and access control applications. Transport: Transponders can be attached to vehicles (eg, airplanes, trains, trucks) and can contain important information about the vehicle and its contents. Shipping applications include fly, train and shipping container tracking, public transport ticketing, and scale station programs. The toll collection application includes the addition of a transponder to the "carrier. The response sends a code identifying a prepaid account to a reader that deducts the fee from the account. The point of sale includes these items including retail items, counterfeits Prevention and sale of electronic monitoring and usually involves marking a separate null with a low-cost transponder, which is essentially a dynamic tag. Baggage handling in a baggage handling application, using an RFID transponder like a smart tag to carry air baggage Marking to allow the air baggage handling operation to be traced from the moment a travel ticket enters the airport until the passenger arrives at its final destination. [Schematic Description] Figure 1 is a block diagram depicting a system in accordance with the present invention. An example of a unique identification code is shown in Figure 2. Figure 3 is a block diagram depicting an implementation of the system of the present invention. Figure 4 is a flow chart. Describe a project introduction process. Fig. 5 is a flow chart depicting the operation of a temperature sensing device and an RFID tag. A flow chart describes the response of the system of the present invention to an event such as loading a box onto a tray. Figure 7 is a flow chart depicting an upgrade operation. Figure 8 is a flow chart depicting upgrade, read, and alert operations. Figure 9 is a flow chart depicting a supply operation. Figure 10 is a block diagram depicting a warning confirmation and a scenario in which a message flows in or out of a tag. Figure 11 is a block diagram depicting a warning confirmation and data. Another scheme for flowing in or out of a mark is shown in Figure 12 as a flow chart describing a flow of data. Figure 13 is a flow chart depicting another aspect of the flow of data. Figure 14 is a The block diagram depicts one implementation of the system of the present invention. Figure 15 is a block diagram depicting software components within the system. Figure 16 is a block diagram depicting the mechanism for storing, changing, and interrogating tracking information. A block diagram depicts the asset list function. Figure 18 is a block diagram depicting a shipping plan. Figure 19 is a block diagram depicting another shipping plan. 135 1310919 Figure 2 0 is a block diagram The mechanism for data recovery is shown in Figure 2. Figure 1 is a block diagram depicting a mechanism for responding to queries. Figure 22 is a block diagram depicting a mechanism for responding to queries. Figure 23 is a block diagram depicting a A mechanism for responding to an inquiry. Figure 24 is a block diagram depicting a mechanism for responding to a query. Figure 25 is a block diagram depicting a mechanism for responding to a query. Figure 26 is a block diagram depicting the basis. A large-scale implementation of the facility. Figure 27 is a block diagram depicting a world model structure. Figure 28 is a block diagram depicting a delegation model. Figure 29 is a block diagram depicting a world model structure. The figure is a block diagram depicting the implementation of an upper node as a cluster. Figure 31 is a block diagram depicting an implementation of the system of the present invention. Figure 32 is a block diagram depicting an implementation of using multiple integration engines in a hierarchical system model. Figure 33 is a block diagram depicting an integration engine. Figure 34 is a block diagram depicting a hardware interface. Figure 35 is a block diagram depicting an electronic tag. Figure 36 is a block diagram of the basic architecture of an inventive management system that is implemented in conjunction with a project tracking system in accordance with the present invention. Figure 37 is a block diagram of an implementation using event routing. Figure 38 is a diagram of a subject structure for event routing. Figure 39 is an illustration of a protocol flow for publishing. Figure 40 is a diagram of a process for subscribing to one of the agreements. 136 1310919 Figure 4 1 is a block diagram of an object name service for locating an event router. Figure 42 is an illustration of the use of an event router to be spread across multiple project tracking systems. Figure 43 is a block diagram of a system for contacting a manufacturer with a customer. Figure 44 is a block diagram of a system for using a shared project tracking system for contacting a manufacturer with a customer. Figure 45 is a flow chart of a method for contacting tracking information. Figure 46 is an illustration of an electronic product coding structure. Figure 47 is an illustration of an unmasked shipping document. Figure 48 is an illustration of a masked shipping document. Figure 49 is a flow chart of a method for filtering tracking information. Figure 50 is a flow diagram of a method for contacting tracking information. Figure 51 is a flow chart of a method for accessing tracking information. Figure 52 is a diagram of a file, an index table, and a system for encoding the tracking information. Figure 53 is a flow diagram of a method for checking an appropriate index table for creating an encoded XML file. Similar reference numbers and designations in the various figures indicate similar elements. [Description of main component symbols] 137 1310919 2 〇 Box is manufactured and labeled with the mark ' 'Seeing' mark (Unique System Identification Symbol, UID) connected to the object interface component of the manufacturer of the object 21,64 Object interface The component manufactures and transmits a "see event" to the communication mediator component 23, 43, 66' 72' 82' 91, 122, 126 CMC arranges the path for the event to context-aware smart component 24 context-aware smart component: knows the object (UID) )? 25 Context-Aware Wisdom Component: Is the event a type of "New Physical Object (UID) Event"? 26 Context-aware smart components are manufactured based on specific data—new physical objects (UIDs) 27 context-aware smart components store new object data 28 context-aware smart components update the state and state history of objects (uid) based on the input data 32 ' 102 Talk element (TC) 3 3 X , 33y , 33 z firewall 34x manufacturing. X: object interface component 34y shipper Y : : object interface component 3 4 z retailer Z ; object interface component 36, 106 communication 1 mediation software Component (CMC) 37, 108 Context-Aware Smart Element (CAIC) 38, 1 10 Human Interface Component (HIC) 138 1310919 and Temperature Critical 40 Object Interface Component Write as "until when RMS Data to Tag (UID) Brigade Reset Tmax 41,89 object interface component; write to the required mark? 42. The object interface component manufactures and transmits a "new physical object event to the communication intermediary software component 44 production system manufacturing a 'introduction physical object event (uid)" including Features, access rights, rules and alerts and transfer them to the communication mediation software component 45 communication mediation software component for the event The routing path to the manufacturer's production system 46 context-aware smart component transmits an "object unknown event (UID)" to the communication intermediary software component 50. The manufacturer attaches the sensor to a pallet, resets its memory and Start the 5 2 sensor... Is it time to measure the temperature? 54 Measure the temperature T and store it with the time stamp on the history of the mark 56. If T&gt;Tmax 'set Tmax = T and store Tmax to mark 60 The pallet is loaded with boxes and sensors. 6 The context-aware smart component updates the status and status history of the object (uid) based on the input data. 70 The tag reader of the shipper connected to the object interface component "sees" on the pallet. The tag (UIDs) of the upper box includes the sensor tag (UID, 139 1310919)

Tmax) 71物件介面元件製造並傳送一 “看見事件,’ (um,Tmax:) 至通訊中介軟體元件 73 ’ 83情境感知智慧元件依據該輸入資料更新物件(UID) 的狀態及歷史記錄 74情境感知智慧元件:溫度Tmax在限制内嗎? 75 ’ 8 6情境感知智慧元件傳送警示事件(UID,Tmax)至該 通訊中介軟體元件 76 CMC替警示安排路徑至該製造者與該裝運者的erp應 用程式 80零售商的與物件介面元件相連的標記讀取器“看見” 在貨盤上箱子的標記(UIDs)包括該感應器標記(UID, Tmax, Thistory) 81物件介面元件製造並傳送一“看見事件”(UID,Tmax Thistory)至通訊中介軟體元件 84情境感知智慧元件基於Tmax、Thisstory以及製造者規 則計算關於每個箱子之新的有效日期 8 5情境感知智慧元件:箱子是不是損毀了? 87通訊中介軟體元件替該警示安排路線至該人類介面元 件。 8 8人類介面无件傳送一簡訊至庫存管理員 90情境感知智慧元件製造並傳送“寫入資料事件(UID、 資料)”至該通訊令介軟體元件 140 1310919 92物件介面元件寫入如“直到何時有效”以及Tmax資 料至標記(UID) 103,3 620項目追蹤系統(ITS) 1 04物件介面元件(OIC) 1 1 2外部應用程式 I 1 4市場 II 6其他情境感知及即時追蹤系統 1 2 0交通資訊提供者製造一包括特性的“引入虛擬狀況事 件(UID)”並將其傳送至該通訊中介軟體元件 1 24物件介面元件製造並傳送一“新的虚擬狀況(UID)事 件”至該通訊中介軟體元件 1 2 8情境感知智慧元件;“該事件是否為“新的虛擬狀況 事件”之類型”? 1 3 0情境感知智慧元件依據該特定資料製造一新的虛擬狀 況(UID) 1 3 2情境感知智慧元件儲存新的虛擬狀況資料 1 5 0物品 152標記(UID,資料) 158 &gt; 1402,4314標記讀取器 1 6 0標記寫入器 1 6 8虚擬項目 170 , 171 規則 1 74應用程式 141 1310919 5 0 0標言己識別記號 1 2 02接收關於一第一物品的特性資訊 1 204接收關於一第二物品的特性資訊以及情境資訊 1206使用該接收資訊維護一第一及第二虚擬物品 1 20 8接收關係資訊並維護一虚擬關係 1 2 1 0認出關於第一物品的警示狀況 1 2 1 2為了回應警示狀況,製造更新的特{生資訊以被寫入 至第一物品 1 2 1 4偵測第一標記出現於一標記寫入處 1 2 1 6使標記寫入處寫入更新資訊至第一標記 1 302接收關於一第一項目的特性.資訊,該特性資訊源自 藉由一第一標記讀取器從位於第一項目的一第一標記 自動讀取的標記資料 1 3 04接收關於該第一項目之更新的特性資料 1 3 0 6在一不同的標記寫入處偵測該第一標記的存在 1 3 0 8使該標記寫入處將更新的資訊寫入至該第一標記 1401商業系統(如企業資源規劃) 1403,4311,4315,4409區域項目追蹤系統 14 04 &gt; 4401 &gt; 4409共享項目追蹤系統 1 4 0 5網路連線 1406 獨立位置 1407 14 07,4407既存的以及新的應用程式 1408 1 408網路連線以攜帶詢問至該ITS而不會改變 142 1310919 ITS狀態 1 409 額外的共享ITS系統 1501即時輸入及處理 1 5 02資料結構與永久儲存 1 5 0 3關於詢問的介面 1 5 0 4,1 5 0 5軟體對軟體的通訊 1 6 1 0核心資料結構無語意 1 620永久儲存機制 1 63 0基本基礎架構(無狀態),即時語意區段 1640歷史及狀態詢問系統 1710物件記錄1.物件ID 2.收集3.會員4屬性 1810 洗潔劑 #341 , #576 1 820紙箱#3328裝運部分#2287 1 830卡車#4421位置緯度/經度/高度 1940洗潔劑#621 1950 倉庫 #4462”}緯度;31N,經度:6 0 45,高度 100 1960 貨架 #3348 1 970 區域 #4462 2010網路(發布-訂購) 2020永久儲存區 2 030核心位置 2040儲存區 2050語意區 143 1310919 2 0 6 0網路基礎架構 2070佇歹丨J 2 11 0路線毁壞 2120邊界箱子 2 1 3 0開始位置 2 1 4 0結束位置 2 1 5 0直線路徑 2 2 2 0路途點 2320運輸路徑 24 1 0行程完成的估計比例 2420估計的現在位置 2510, 2512, 2514, 2516, 2518 路線部分 2710,2720,2910,2920,3010 世界模型 3 110整合引擎 3 120智慧項目 3 1 3 0高階應用程式 3 3 1 0控制管理員 3 3 2 0詢問器代理程式 3330處理代理程式 3340通訊代理程式 3400硬體介面 3 4 1 0伺服器 3420詢問器 144 1310919 3 5 Ο 0電子標記 3 5 1 0 物品編號(“ ARTNR” ) 3 520物品的描述(“ARTDESC” ) 3 5 3 0物品的價格 3 6 1 0監控系統 3630早期警示代理程式(EWA) ' 3 640庫存規劃工具 3710事件路由器(ER) 3 720延伸物件命名服務(EONS) 4301生產者 4302消費者 4303裝運 4304 項 a 4 3 0 6標記讀取器系統 4307 容器標記 43 08 項目標記 4309 裝運内容資訊 4 3 1 0通訊網路 43 1 2,43 1 3外部企業資源規劃系統 4500 , 4900 , 5000 , 5100 方法 45 1 0接收多個識別碼,每個識別碼唯一地識別一有關項目 45 20將該識別碼分類成一組或多組識別碼 4 5 3 0對於每一組識別碼,認出編碼的多餘部分,該情形 145 1310919 對於每組編碼是很普遍的 4 5 4 0建立一文件包含一組或多組的識.別碼 4 5 5 0在一階層體系中組織該文件因而對於每組識別碼, 該多餘部分被列出一次且每個識別碼隨著省略的多餘 部分列出 4 6 1 0標頭 4620電子產品編碼管理員 4630物件種類 4640序號 4701多餘部分 4802前綴 4 9 1 0接收與多個項目結合的識別碼,包括獨立的項目以 及項目的容器 4920放置一字元於每個識別碼中,該識別碼指出該項目 唯一獨立項目或項目容器 4930基於該座落的字元決定該識別碼對應至一獨立項目 還足一容器 5010建立關於一個或多個項目的追蹤資訊,每個項目具 有一個或多個特性 5 0 2 0對於每個特性使用一明確的編碼方案將此追蹤資訊 編碼 5030傳送該追蹤資訊至一接收者 5 040決定該接收者被授權存取哪些特性 146 1310919 5 05 0僅提供該接收者該編碼方案的一子集合,其僅包括 關於接收者被授權存取之特性的編碼方案 5 11 0接收關於一個或多個項目之編碼的追蹤資訊,每個 項目具有一個或多個特性,每個編碼的特性使用一明 癌的編碼方案 5 1 2 0僅接收該編碼方案的一子集合,其僅包括關於接收 者被授權存取之特性的編碼方案 5 1 3 0將接收者被授權存取的特性加以解碼 5 2 1 0生產者可延伸性標示語言文件 5215,5260編碼可延伸性標示語言文件 5 22 0生產者文件類型定義檔案 522 5,5270編碼文件類型定義檔案 5230索引表 5 240網路 5245標言己項目 5265消費者可延伸性標示語言文件 5 275消費者文件類型定義檔案 528 0分佈索引表 53 10索引表是否需要更新? 5 3 2 0建立編碼的可延伸性標示語言文件以及編碼的文件 類型定義檔案 5330建立索引表 147Tmax) 71 object interface component manufactures and transmits a "see event," (um, Tmax:) to communication mediation software component 73 '83 context-aware smart component updates the state of the object (UID) based on the input data and history 74 contextual awareness Smart component: Is the temperature Tmax within the limit? 75 ' 8 6 The context-aware smart component transmits a warning event (UID, Tmax) to the communication mediator component 76. The CMC arranges the route to the manufacturer and the shipper's erp application. 80 retailer's tag reader connected to the object interface component "sees" the tag on the pallet (UIDs) including the sensor tag (UID, Tmax, Thistory) 81 object interface component manufacturing and transmitting a "see event "(UID, Tmax Thistory) to communication mediation software component 84 Context-aware smart component calculates a new effective date for each box based on Tmax, Thisstory, and manufacturer rules. 8 5 Context-aware smart components: Is the box damaged? 87 Communication The mediation software component routes the alert to the human interface component. 8 8 Human interface sends a message to none The inventory manager 90 context-aware smart component manufactures and transmits a "write data event (UID, data)" to the communication command software component 140 1310919 92 object interface component writes such as "until when valid" and Tmax data to mark (UID) 103,3 620 Project Tracking System (ITS) 1 04 Object Interface Component (OIC) 1 1 2 External Application I 1 4 Market II 6 Other Situational Awareness and Instant Tracking System 1 2 0 Traffic Information Provider Creates a Included Feature "Introducing a virtual status event (UID)" and transferring it to the communication mediation software component 1 24 object interface component manufacturing and transmitting a "new virtual condition (UID) event" to the communication mediation software component 1 2 8 context-aware wisdom Component; "Is the event a type of "new virtual status event"? 1 3 0 Context-aware smart component creates a new virtual condition (UID) based on that particular material 1 3 2 Context-aware smart component stores a new virtual state Data 1 0 0 Item 152 mark (UID, data) 158 &gt; 1402, 4314 mark reader 1 60 mark writer 1 6 8 virtual item 170, 171 rule 1 74 application 141 1310919 5 0 0 mark recognition mark 1 2 02 receives characteristic information about a first item 1 204 receives characteristic information about a second item and context information 1206 uses the received information to maintain a first The second virtual item 1 20 8 receives the relationship information and maintains a virtual relationship 1 2 1 0 recognizes the warning condition regarding the first item 1 2 1 2 In order to respond to the warning condition, an updated special information is created to be written to the An item 1 2 1 4 detects that the first mark appears at a mark write location 1 2 16 causes the mark write to write update information to the first mark 1 302 to receive characteristics about a first item. Information, the characteristic The information is derived from a first tag reader that receives the updated profile data 1 3 0 6 about the first item from a tag data 1 3 04 automatically read by a first tag located in the first item. The mark write location detects the presence of the first mark 1 3 0 8 such that the mark writes the updated information to the first mark 1401 commercial system (eg enterprise resource planning) 1403, 4311, 4315, 4409 area Project Tracking System 14 04 &gt; 4401 &gt; 4409 shared project tracking system 1 4 0 5 network connection 1406 independent location 1407 14 07, 4407 existing and new application 1408 1 408 network connection to carry the inquiry to the ITS without changing 142 1310919 ITS Status 1 409 Additional Shared ITS System 1501 Instant Input and Processing 1 5 02 Data Structure and Permanent Storage 1 5 0 3 About the Interrogation Interface 1 5 0 4,1 5 0 5 Software-to-Software Communication 1 6 1 0 Core data structure without semantics 1 620 Permanent storage mechanism 1 63 0 basic infrastructure (stateless), instant semantic segment 1640 history and status query system 1710 object record 1. Object ID 2. Collection 3. Member 4 attribute 1810 detergent #341 , #576 1 820纸箱#3328 Shipping part #2287 1 830 truck #4421 Position latitude/longitude/height 1940 detergent #621 1950 Warehouse #4462”} latitude; 31N, longitude: 6 0 45, height 100 1960 Shelf #3348 1 970 Area #4462 2010 Network (Publish-Order) 2020 Permanent Storage Area 2 030 Core Location 2040 Storage Area 2050 Semantic Area 143 1310919 2 0 6 0 Network Infrastructure 2070伫歹丨J 2 11 0 Route Destruction 2120 border box 2 1 3 0 Start position 2 1 4 0 End position 2 1 5 0 Straight path 2 2 2 0 way point 2320 Transportation path 24 1 0 Estimated ratio of completed stroke 2420 Estimated current position 2510, 2512, 2514, 2516, 2518 Route part 2710, 2720 , 2910, 2920, 3010 World Model 3 110 Integration Engine 3 120 Smart Project 3 1 3 0 Advanced Application 3 3 1 0 Control Manager 3 3 2 0 Interrogator Agent 3330 Processing Agent 3340 Communication Agent 3400 Hardware Interface 3 4 1 0 server 3420 interrogator 144 1310919 3 5 Ο 0 electronic tag 3 5 1 0 item number ("ARTNR") 3 520 description of the item ("ARTDESC") 3 5 3 0 item price 3 6 1 0 monitoring System 3630 Early Alert Agent (EWA) '3 640 Inventory Planning Tool 3710 Event Router (ER) 3 720 Extended Object Naming Service (EONS) 4301 Producer 4302 Consumer 4303 Shipment 4304 Item a 4 3 0 6 Tag Reader System 4307 Container Marking 43 08 Item Marking 4309 Shipping Content Information 4 3 1 0 Communication Network 43 1 2, 43 1 3 External Enterprise Resource Planning System 4500, 4900, 5000, 5100 Method 45 1 0 Receive Multiple Identifications Each identification code uniquely identifies a related item 45 20 that classifies the identification code into one or more sets of identification codes 4 5 3 0 for each set of identification codes, recognizing the redundant portion of the code, the situation 145 1310919 for each group Coding is very common. 4 5 4 0Create a file containing one or more sets of identities. The code 4 5 5 0 organizes the file in a hierarchy and thus the redundant portion is listed once for each set of identification codes and Each identification code is listed with the redundant part omitted. 4 6 1 0 Header 4620 Electronic Product Code Administrator 4630 Object Type 4640 Serial Number 4701 Extra Part 4802 Prefix 4 9 1 0 Receives an identification code combined with multiple items, including independent The item and the container 4920 of the item are placed in a character string in each identification code, the identification code indicating that the item unique independent item or item container 4930 determines that the identification code corresponds to an independent item based on the selected character. The container 5010 establishes tracking information about one or more items, each item having one or more characteristics 5 0 2 0 for each feature using an explicit coding scheme to compile the tracking information 5030 transmits the tracking information to a recipient 5 040 determining which features the recipient is authorized to access 146 1310919 5 05 0 providing only a subset of the recipient's encoding scheme, including only that the recipient is authorized to access The encoding scheme 5 10 0 of the characteristic receives tracking information about the encoding of one or more items, each item having one or more characteristics, each encoding characteristic using only a clearing coding scheme 5 1 2 0 only receiving the encoding A subset of the scheme, which only includes a coding scheme for the characteristics that the recipient is authorized to access. 5 1 3 0 Decodes the characteristics that the recipient is authorized to access 5 2 1 0 Producer Extensibility Markup Language File 5215, 5260 code extensibility markup language file 5 22 0 producer file type definition file 522 5,5270 code file type definition file 5230 index table 5 240 network 5245 markup item 5265 consumer extensibility mark language file 5 275 consumption File Type Definition File 528 0 Distribution Index Table 53 10 Does the index table need to be updated? 5 3 2 0 Create coded extensibility markup language file and coded file type definition file 5330 build index table 147

Claims (1)

柯泠日修正本 PPjs4-^^ 十、申請專利範圍: 1 · 一種情境感知與即時項目追蹤的方法,其至少包含以下 步驟: 接收多次標記讀取資料,每次包括自附著於一項目之一標 記所讀取的資訊,該所讀取的資訊包括自該標記讀取的一 種唯一數位識別記號每次也包括含有該對應標記的一位置 以及其附著項目的狀態資訊、一當該唯一數位識別記號自 該標記被讀取時之時間,描述一物品(a r t i c 1 e)之特徵的特 性資料以及定義被啟動之動作的規則資料,該多次標記讀 取資料全體係包含自附著於多個項目之標記所讀取的資 訊; 接收一次或多次情境資訊,每次描述一關連的不可標記 的實體狀況,該情境資訊指出一種狀態,其包含該狀況之 一位置、一時間、描述該情境之特徵的特性資料以及定義 被啟動之動作的規則資料,該多次情境資訊整體係包括描 述多個狀況的資訊; 使用該接收的標記讀取資料以及情境資訊以維護一虛 擬世界中的實體資料處理結構以及情境資料處理結構,該 等實體資料處理結構包括關於每個物品的資料處理結構, 而該等情境資料處理結構包括關於每個狀況的資料處理結 構,該每個處理結構儲存了一對應項目或狀況的特性資料 及規則資料; 將該等實體資料處理結構以及該等情境資料處理結構對 148 1310919 映(mapping)至丨J虛擬全球標準化的時間維度、三維空間以及 唯一標識,藉此該物品及相關於該等實體資料處理結構以 及該等情境資料處理結構之該不可標記的實體狀況能透過 空間以及時間而相互追蹤;柯泠日修正本PPjs4-^^ X. Patent application scope: 1 · A method for context awareness and real-time project tracking, which includes at least the following steps: receiving multiple tags to read data, each time including self-attachment to a project a message read by the mark, the read information including a unique digital identification mark read from the mark, each time including a position containing the corresponding mark and status information of the attached item, once the unique number The time at which the identification mark is read from the mark, the characteristic data describing the characteristics of an article (artic 1 e), and the rule data defining the action to be activated, the multiple mark read data system including self-adhesive to multiple The information read by the item's tag; receives one or more contextual information, each time describing a related unmarkable entity status, the context information indicating a status that includes one of the statuses, a time, and a description of the situation The characteristic data of the feature and the rule data defining the action to be activated, the multiple context information as a whole includes a description of multiple Information of the status; using the received tag to read the data and the context information to maintain an entity data processing structure and a context data processing structure in a virtual world, the entity data processing structure including a data processing structure for each item, and The contextual data processing structure includes a data processing structure for each condition, the processing structure storing a characteristic data and rule data corresponding to the item or condition; the entity data processing structure and the context data processing structure pair 148 1310919 mapping to the time dimension, three-dimensional space, and unique identifier of the virtual world standardization, whereby the item and the unmarkable entity condition associated with the entity data processing structure and the context data processing structures are transparent Tracking each other in space and time; 依據該等實體資料處理結構以及該等情境資料處理結構 之對映步驟、該位置、該時間及/或該特性資料,而偵測 一發生在虚擬世界中於該等實體資料處理結構以及該等情 境資料處理結構之間發生的互動;以及 依據該互動及該規則資料而啟動動作。 2.如申請專利範圍第1項所述之方法,更包含以下步驟; 每當決定一已偵測的互動而影響到任何物品時,則對該虛 擬世界中的一使用者發出一警示,其中該使用者為一人類 或一電腦程式。Detecting, according to the entity data processing structure and the mapping step, the location, the time and/or the characteristic data of the context data processing structures, detecting a data processing structure occurring in the virtual world in the virtual world and the The interaction between the contextual data processing structures; and the initiation of actions based on the interaction and the rules. 2. The method of claim 1, further comprising the steps of: whenever a detected interaction affects any item, a warning is issued to a user in the virtual world, wherein The user is a human or a computer program. 3 .如申請專利範圍第1項所述之方法,更包含以下步驟; 維護在該虚擬世界中每個物品(其相關於該實體資料處理 結構)之現在位置的一種表示以及每個狀況(其相關於該情 境資料處理結構)之現在位置的一種表示,該等表示各者均 可個別地反應出最近接收到的標記讀取資料以及情境資 訊0 149 1310919 4如申請專利範圍第1項所述之方法,更包含以下步驟: 藉由緯度、經度以及高度來表示位置及狀況。 5如申請專利範圍第3項所述之方法,更包含以下步驟: 維護物品位置之一歷史紀錄以及維護狀況位置之一歷史 紀錄。 6. 如申請專利範圍第4項所述之方法,更包含以下步驟: 基於物品位置之歷史紀錄自該虚擬世界導出至少一物品 之未來位置的預測值。 7. 如申請專利範圍第6項所述之方法,更包含以下步驟: 同樣亦基於狀況位置的歷史紀錄導出該未來位置的預測 值。 8. 如申請專利範圍第1項所述之方法,其中: 該不可標記的狀況包含一種與天氣有關的狀況;以及 與天氣有關之狀況的該位置由至少一緯度、經度及高度來 描述。 9. 如申請專利範圍第1項所述之方法,其中: 該不可標記的狀況包含一交通事故:以及 150 1310919 該交通事故的位置由至少一緯度、經度及高度來描述。 1 0.如申請專利範圍第1項所述之方法,更包含以下步驟: 接收一或多次階層體系資訊,每次均係一介於該虛擬世界 所代表物品間的一種階層的描述;及 使用該接收的階層體系資訊以在該虛擬世界中維護情 境資料處理結構,每個情境資料處理結構代表階層體系之 11.如申請專利範圍第1 0項所述之方法,其中: 至少一階層體系代表物品間的一種關係,其中某些特定物 品係包含於另一物品内。 12.如申請專利範圍第1項所述之方法,更包含以下步驟: 接收感應器資訊,其係取自於與一第一物品相關聯的一 感應器;及3. The method of claim 1, further comprising the steps of: maintaining a representation of the current location of each item in the virtual world (which is related to the entity data processing structure) and each condition (its A representation of the current location of the contextual data processing structure, each of which can individually reflect the most recently received marker reading data and contextual information. 0 149 1310919 4 as described in claim 1 The method further includes the following steps: locating the position and condition by latitude, longitude and altitude. 5 The method of claim 3, further comprising the steps of: maintaining a historical record of the location of the item and a historical record of the status of the maintenance status. 6. The method of claim 4, further comprising the step of: deriving a predicted value of a future location of at least one item from the virtual world based on a history of the item location. 7. The method of claim 6, further comprising the step of: deriving the predicted value of the future location based on the historical record of the location location. 8. The method of claim 1, wherein: the unmarkable condition comprises a weather-related condition; and the location of the weather-related condition is described by at least one latitude, longitude and altitude. 9. The method of claim 1, wherein: the unmarkable condition comprises a traffic accident: and 150 1310919 the location of the traffic accident is described by at least one latitude, longitude and altitude. 1 0. The method of claim 1, further comprising the steps of: receiving one or more hierarchical system information, each time being a description of a hierarchy between items represented by the virtual world; and using The received hierarchy information to maintain a context data processing structure in the virtual world, each context data processing structure representing a hierarchical system. 11. The method of claim 10, wherein: at least one hierarchical system representative A relationship between items in which certain items are contained within another item. 12. The method of claim 1, further comprising the steps of: receiving sensor information from a sensor associated with a first item; 利用該感應器資訊更新該第一物品的一第一實體資料處 理結構。 1 3 .如申請專利範圍第1項所述之方法,其中接收情境資 訊的步驟包含: 自外部系統接收情境資訊。 151 1310919A first entity data processing structure of the first item is updated by the sensor information. The method of claim 1, wherein the step of receiving the contextual information comprises: receiving context information from an external system. 151 1310919 1 4如申請專利範圍第1項所述之方法,其中接收情境資訊 的步驟包含: 接收情境資訊,其中該資訊包含取自於與一特定位置結合 之感測器的遙測資料。The method of claim 1, wherein the receiving the context information comprises: receiving context information, wherein the information comprises telemetry data taken from a sensor coupled to a particular location. 1 5 ·如申請專利範圍第1 4項所述之方法,更包含以下步驟: 接收一由感應器所產生的遙測(t e 1 e m e t r y)資料,該感應 器係與一特定點或區域結合,該遙測資料係代表一位於該 特定點或區域之一狀況;及 當虚擬世界偵測到一物品位於表示於虚擬世界中的該 點或區域之上或之中而可能會被該遙測資料所代表的狀況 影響時,對虛擬世界中的一使用者產生一警示,其中該使 用者為一人類或一電腦程式。1 5 - The method of claim 14, further comprising the steps of: receiving a telemetry data generated by a sensor, the sensor being associated with a specific point or region, Telemetry data represents a condition at a particular point or region; and when the virtual world detects that an item is located on or in the point or area represented in the virtual world, it may be represented by the telemetry data When the situation affects, a warning is generated to a user in the virtual world, wherein the user is a human or a computer program. 1 6.如申請專利範圍第1 4項所述之方法,更包含以下步驟: 接收由一與一特定點或區域所相關之溫度感應器所產 生的溫度資料,並表示在該虚擬世界内之一情境資料處理 結構中的該特定點或區域的現在溫度;及 隨著一物品及現在溫度被表示於該虚擬世界中,當虚擬 世界偵測到該物品位於該點或區域之上或之中而可能會被 該現在温度所影響時,對虚擬世界t的一使用者產生一警 示,其中該使用者為一人類或一電腦程式。 152 13109191 6. The method of claim 14, further comprising the steps of: receiving temperature data generated by a temperature sensor associated with a particular point or region, and representing the virtual world a current temperature of the particular point or region in a contextual data processing structure; and as an item and current temperature are represented in the virtual world, when the virtual world detects that the item is above or in the point or region While being affected by the current temperature, a warning is generated to a user of the virtual world t, wherein the user is a human or a computer program. 152 1310919 1 7 ·如申請專利範圍第1項所述之方法,更包含以下步驟: 附加一溫度異常(exception)至一實體資料處理結構,並 當滿足該溫度異常之條件時,使一動作發生。 1 8.如申請專利範圍第1 7項所述之方法,其中以下步驟: 該動作包含對一使用者產生警示,其中該使用者為一人類 或一電腦程式。 1 9.如申請專利範圍第1項所述之方法,更包含以下步驟: 附加一規則至一實體資料處理結構,可操作該規則以觸發 警示事件或依據虛擬世界中的現在資訊引發動作。 20.如申請專利範圍第1項所述之方法,更包含以下步驟: 附加一規則至一情境資料處理結構,可操作該規則以觸發 警示事件或依據虛擬世界中的現在資訊引發動作。 2 1.如申請專利範圍第1項所述之方法,更包含以下步驟: 接收、處理及回應一詢問,該詢問乃是關於一物品在該虛 擬世界中之現在或過去的狀態。 2 2.如申請專利範圍第2 1項所述之方法,更包含以下步驟: 接收、處理及回應一關於物品狀態的詢問,該物品及特定 物品如虛擬世界中所呈現般,在現在或過去狀態彼此間具 153 1310919 有一特定關係。 2 3. —種更新附著於一項目之一可覆寫標記之資訊的方 法,其至少包含以下步驟: 在一系統中接收一第一項目的第一特性資訊,其中該第 一特性資訊是從附著至該第一項目之一第一標記自動讀取 的資料,該第一特性資料包括識別該第一項目的一第一識 別記號; 在一系統中接收一第二項目的第二特性資訊,其中該第 二特性資訊是從附著至該第二項目之一第二標記自動讀取 的資料,該第二特性資料包括識別該第二項目的一第二識 別記號; 在該系統中接收感應器資訊,其係來自由一結合至該第 二項目的一感應器所感應的資料,故該感應器資訊表示至 少一存在於該第二物品處之狀態; 在該系統中接收關係資訊,其指出該第一項目與第二項 目間之實體上鄰近的一種關係; 在該系統中維護表示該第一項目的一第一實體物件,該 第一實體物件維護代表該第一特性資訊之資訊; 在該系統中維護表示該第二項目的一第二實體物件,該 第二實體物件維護代表該第二特性資訊之資訊; 在該系統中雉護一情境物件,其表示在該第一項目與第 154 1310919 二項目間之實體上鄰近的該關係; 依據在該情境物件中所表示之該第一項目與第二項目間 之實體上鄰近的該關係,而將該感測器資訊與該第一實體 物件相關聯,該感測器資訊係來自由一結合至該第二物品 的一感應器所感應的資料,故該感測器資訊被決定以描述 至少一存在於該第一物品處之狀態; 將該感測器資訊與該第一特性資訊相比較; 依據該感測器資訊與該第一特性資訊之比較結果,而決 定一警示狀態存在於該第一物品處; 因應於該所決定之警示情況,而產生一正待被寫入至該 第一項目之更新的特性資訊; 在該警示情況被決定為存在後,於一系統中偵測到該第 一標記係出現在一標記寫入區;以及 當偵測到該第一標記係位於該標記寫入區時,使該標記 寫入區於該處寫入該更新資訊至該第一標記。 24.如申請專利範圍第23項所述之方法,其中: 該警示情況被決定為存在於系統外部的一應用程式 中,該應用程式自該系統接收來自於由系統維護之物件的 資訊; 該應用程式產生一更新的特性資訊,並提供至系統,且 要求該更新的特性資訊被寫入至該第一標記中:及 系統回應該要求,使該標記寫入區寫入該更新的資訊至 155 1310919 該第一標記。 25. 如申請專利範圍第24項所述之方法,其中: 該第一及第二實體物件代表其於一虛擬世界中所對應 並由系統所維護的項目;及 該應用程式可監控該虛擬世界。 26. 如申請專利範圍第23項所述之方法,其中: 依據提供至系統的一或多個警示規則來操作系統而由 系統之一元件認出一警示情況: 依據提供至系統的一或多個更新規則來橾作系統而由 系統之一元件產生一更新資訊;及 依據提供至系統的一或多個資料可覆寫的規則使得該 標記寫入區寫入該更新資訊至該第一標記。 27. 如申請專利範圍第23項所述之方法,其中該感應器係 附著至該第二標記。 2 8.如申請專利範圍第 23項所述之方法,其中該感應器 為一溫度感應器。 29.如申請專利範圍第28項所述之方法,其中: 由於感應器測量出的溫度超過一臨界值,便產生該警示 156 1310919 情況;以及 該更新資訊為關於該第一項目的一縮短產品有效期限 的資訊。 3 0 ·如申請專利範圍第2 3項所述之方法,其中該第一標記 為一無線電頻率應答器(trnasponder)。 3 1.如申請專利範圍第2 3項所述之方法,其中該第一及第· 二識別記號為全球唯一識別記號。 32.—種於一商業資料處理環境中使用的方法,其中該環境 包括位於一供應鏈中的多個企業,該方法至少包含以下步 驟: 自一第一企業接收多次標記讀取資料,每次包括自附 著於一項目之一標記所讀取的資訊,該所讀取的資訊包括 自動地從該標記讀取的一種唯一標記識別記號,當該標記 識別記號自該標記被讀取時,每次也包括含有該對應標記 之一位置以及其附著項目的狀態資訊,該位置包括了一經 度與一緯度,自該企業讀取的多次標記讀取資料全體係包 含自附著於多個項目之標記所讀取的資訊; 使用自第一企業接收的該標記讀取資料來維護該等 項目的配置資訊; 自一第二企業接收多次第二標記讀取資料,每次包 括自附著於一項目之一標記所讀取的資訊,該項目係相同 157 1310919 或不同於從該第一企業處接收標記讀取資料的該項目,該 所讀取的資訊包括自動地從該標記讀取的一唯一標記識別 記號,當該標記識別記號自該標記被讀取時,每次也包括 含有該對應標記的一位置以及其附著項目的狀態資訊,該 位置包括了一經度與一緯度,自該企業讀取的多次標記讀 取資料整體係包含自附著於多個項目之標記所讀取的資 訊; 使用自第二企業接收的該標記讀取資料來維護該項 目的配置資訊,其中自任一方企業接收的關於一特定項目 之標記讀取資料係被用來更新該配置資訊;以及 使該配置資訊可以被該供應鏈中的多個企業看見, 包括該第一及第二企業。 33.如申請專利範圍第32項所述之方法,更包含以下步驟: 自一第三企業接收多次第三標記讀取資料,每次包括自 附著於一項目之一標記所讀取的資訊,該所讀取的資訊包 括自該標記讀取的一種唯一標記識別記號,當該唯一標記 識別記號自該標記被讀取時,每次也包括含有該對應標記 的一位置以及其附著項目的狀態資訊,自該企業讀取的多 次標記讀取資料整體係包含自附著於多個項目之標記所讀 取的資訊: 使用自第三企業接收的該標記讀取資料來維護該項目 158 1310919 的配置資訊,其中自任一方企業接收的關於一特定項目之 標記讀取資料係被用來更新該配置資訊。 3 4.如申請專利範圍第3 2項所述之方法,其中: 附著至該多個項目的標記包含無線電頻率識別(RFID) 標記,每個RFID標記攜帶一電子產品編碼(ePC)作為其標 記識別記號。1 7 The method of claim 1, further comprising the step of: attaching a temperature exception to an entity data processing structure, and causing an action to occur when the temperature anomaly condition is met. The method of claim 17, wherein the action comprises: alerting a user that the user is a human or a computer program. 1 9. The method of claim 1, further comprising the step of: attaching a rule to an entity data processing structure operable to trigger an alert event or to trigger an action based on current information in the virtual world. 20. The method of claim 1, further comprising the step of: attaching a rule to a context data processing structure operable to trigger an alert event or to initiate an action based on current information in the virtual world. 2 1. The method of claim 1, further comprising the steps of: receiving, processing, and responding to an inquiry regarding a current or past state of an item in the virtual world. 2 2. The method of claim 21, further comprising the steps of: receiving, processing and responding to an inquiry about the status of the item, the item and the particular item being presented in the virtual world, now or in the past The states have a specific relationship with each other 153 1310919. 2 3. A method for updating information attached to one of the items to overwrite the mark, comprising at least the following steps: receiving, in a system, first characteristic information of a first item, wherein the first characteristic information is from Attached to the first item of the first item, the first characteristic data includes a first identification symbol identifying the first item; receiving a second characteristic information of the second item in a system, The second characteristic information is data automatically read from a second mark attached to one of the second items, the second characteristic data includes a second identification mark identifying the second item; receiving a sensor in the system Information, which is derived from a sensor coupled to the second item, such that the sensor information indicates at least one state present at the second item; receiving relationship information in the system, indicating a physical proximity relationship between the first item and the second item; maintaining a first physical object representing the first item in the system, the first physical object maintenance Information indicating the first characteristic information; maintaining a second physical object representing the second item in the system, the second physical object maintaining information representing the second characteristic information; protecting a situation object in the system Representing the relationship physically adjacent between the first item and the 154 1310919 item; based on the physical proximity between the first item and the second item represented in the situation object, Correlating the sensor information with the first physical object, the sensor information is from a sensor sensed by a sensor coupled to the second item, so the sensor information is determined to describe at least a state of being present at the first item; comparing the sensor information with the first characteristic information; determining, according to a comparison result of the sensor information and the first characteristic information, determining that a warning state exists in the The first item; generating, according to the warning situation determined by the decision, an attribute information to be written to the updated item of the first item; after the warning condition is determined to be present Detecting that the first mark appears in a mark writing area in a system; and when detecting that the first mark is located in the mark writing area, causing the mark writing area to write the mark Update the information to the first tag. 24. The method of claim 23, wherein: the alert condition is determined to be present in an application external to the system, the application receiving information from the system maintained by the system; The application generates an updated feature information and provides it to the system, and requests the updated feature information to be written into the first tag: and the system responds to the request, so that the tag write area writes the updated information to 155 1310919 The first mark. 25. The method of claim 24, wherein: the first and second physical objects represent items that are corresponding to and maintained by the system in a virtual world; and the application can monitor the virtual world . 26. The method of claim 23, wherein: the alerting condition is recognized by one of the components of the system based on one or more alerting rules provided to the system: based on one or more provided to the system An update rule to generate an update information by one of the elements of the system; and a rule that can be overwritten according to one or more data provided to the system causes the mark write area to write the update information to the first mark . 27. The method of claim 23, wherein the sensor is attached to the second indicia. The method of claim 23, wherein the sensor is a temperature sensor. 29. The method of claim 28, wherein: the warning 156 1310919 is generated because the temperature measured by the sensor exceeds a threshold; and the update information is a shortened product for the first item Information on the expiration date. The method of claim 23, wherein the first flag is a radio frequency transponder. 3. The method of claim 23, wherein the first and second identification marks are globally unique identification marks. 32. A method for use in a business data processing environment, wherein the environment comprises a plurality of enterprises located in a supply chain, the method comprising at least the following steps: receiving a plurality of tags from a first enterprise to read data, each The second includes information read from a tag attached to an item, the read information including a unique tag identification mark automatically read from the tag, when the tag identification mark is read from the tag, Each time also includes status information including a position of the corresponding mark and an attached item thereof, the position including a longitude and a latitude, and the plurality of mark reading data read from the enterprise includes self-adhesive to the plurality of items Marking the information read; using the mark received from the first enterprise to read the data to maintain the configuration information of the items; receiving a second mark from the second enterprise to read the data, each time including self-adhesive One of the items marks the information read, which is the same as 157 1310919 or a different item from the first enterprise receiving the mark reading material. The captured information includes a unique mark recognition mark automatically read from the mark, and when the mark identification mark is read from the mark, each time including a position including the corresponding mark and status information of the attached item, The location includes a longitude and a latitude, and the plurality of tag reading data read from the enterprise as a whole includes information read from a tag attached to a plurality of items; reading using the tag received from the second enterprise Data to maintain configuration information of the project, wherein the tag reading data received from either enterprise for a particular item is used to update the configuration information; and the configuration information can be seen by multiple enterprises in the supply chain. Including the first and second companies. 33. The method of claim 32, further comprising the steps of: receiving a third mark reading data from a third enterprise, each time including information read from a mark attached to one of the items; The information read includes a unique mark identification mark read from the mark, and when the unique mark identification mark is read from the mark, each time including a position including the corresponding mark and an attached item thereof Status information, the multiple tag read data read from the enterprise contains the information read from the tag attached to multiple items: The tag is used to read the data received from the third enterprise to maintain the project 158 1310919 Configuration information, wherein the tag reading data received from either enterprise for a particular item is used to update the configuration information. 3. The method of claim 3, wherein: the tag attached to the plurality of items comprises radio frequency identification (RFID) tags, each tag carrying an electronic product code (ePC) as its tag Identify the token. 3 5 .如申請專利範圍第3 2項所述之方法,其中: 該配置資訊之可見度為經控制的可見度;以及 該方法更包含以下步驟: 接收授權資訊,其指出應使該供應鏈内的一特定企業 可看見該配置資訊的程度:及 使該特定企業僅看見由該授權資訊所允許的配置資 訊。 3 6.如申請專利範圍第3 5項所述之方法,其中:The method of claim 3, wherein: the visibility of the configuration information is controlled visibility; and the method further comprises the steps of: receiving authorization information indicating that the supply chain should be The extent to which a particular enterprise can see the configuration information: and cause the particular enterprise to see only the configuration information allowed by the authorization information. 3 6. The method of claim 35, wherein: 該配置資訊包含多個項目特性;以及 該授權資訊指出,對於至少一項目特性而言,何個項目 特性可使該企業看見。 3 7.如申請專利範圍第32項所述之方法,其中: 該多個企業包括一來源企業及一目的企業: 該來源企業擁有關於該目的企業所開出之一訂單的一 159 1310919 訂單文件以及關於一實體貨物運送以準備滿足該目的企業 所開出之訂單的一裝運文件; 可見度包括在標記讀取資料以及企業文件間關係的可 見度,該企業文件包括該訂單文件以及該裝運文件;及 提供該企業項目配置的即時可見度,其更包含: 接收裝運資訊,包含下列項目; 關於對應至在裝運中之貨物的標記識別記號; 對於該裝運文件而言,將每個標記識別記號與一裝 運編號結合的資訊,及 關於該訂單文件中與具有一訂單編號之該裝運編號 相關的資訊: 將該標記讀取資料與該裝運資訊相亙關聯;以及 使該關聯可被該目的企業取得,因而該目的企業可使用 關於該裝運中之一項目的一標記識別記號以確認該裝運。 38. —種用於項目之情境認知及即時追蹤的方法,其至少包 含以下步驟: 接收一組規則,該規則指出提供哪些資料至一外部應用 程式; 自一個或多個標記讀取器接收包括項目識別記號的項 目資料,每個自一數位標記讀取中的項目識別記號附著於 一實體項目,該項目識別記號可唯一地識別該項目; 自其他感應器裝置接收額外的項目資料,該其他的感應 160 1310919 器裝置是與標記讀取器不同的裝置,該額外項目資料與一 或多個由該標記讀取器識別的項目相關; 使用該規則、項目識別記號以及額外的項目資料以決定 提供哪些項目識別記號及額外項目資料的子集合給該外部 應用程式:及 提供僅包含該接收之項目識別記號及額外項目資料的 子集合的資料給該外部應用程式 ;從外部應用程式中接收資料,該資料包括用於控制一 致動器裝置之組態資料; 將該組態資料轉換成一相容於該致動器裝置之格式;以 及 提供該經轉換之組態資料給該致動器裝置。 3 9.如申請專利範圍第3 8項所述之方法,其中該決定係即 時完成且該資料係即時提供。 40.如申請專利範圍第3 8項所述之方法,更包含以下步驟: 將一項目識別記號與額外的項目資料加以匯總。 41. 一種實質地儲存在一電腦可讀取記錄媒體上之電腦產 品,其係可用於情境感知與即時項目追蹤,該產品包含可 操作之指令,以使一可程式處理器進行下列步驟·_ 161 1310919 接收多次標記讀取資料,每次包括自附著於一項目之一 標記所讀取的資訊,該讀取的資訊包括自該標記讀取的一 種唯一數位識別記號、該對應標記的一位置以及其附著項 目、一當該唯一數位識別記號自該標記被讀取時之時間、、 特性資料及規則資料,該多次標記讀取資料全體係包含自 附著於多個項目之標記所讀取的資訊; 接收一或多次情境資訊,每次係與一不可標記的實體狀 況相關之描述,該情境資訊包含該狀況之一位置、一時間、 特性資料及規則資料,該多次情境資訊整體係包括可描述 多個狀況的資訊; 使用該接收的標記讀取資料以及情境資訊來維護一虛 擬世界中的實體資料處理結構以及情境資料處理結構,該 等實體資料處理結構包括關於每個物品的資料處理結構, 而該情境資料處理結構包括關於每個狀況的資料處理結 構,該每個資料處理結構儲存一對應項目或狀況的特性資 料及規則資料; 依據該位置、該時間、及/或該特性資料,來偵測發生 在虛擬世界中於該等資料處理結構之間的互動;以及 依據該互動及該規則資料而啟動動作。 42.—種實質儲存在一電腦可讀取記錄媒體上之電腦程式 產品,其係可更新附著於一項目之可覆寫標記上的資訊, 該產品包含可操作之指令,以使可程式處理器進行下列步 162 1310919 驟; 在一系統中接收一第一項目的第一特性資訊,其 一特性資訊是從附著至該第一項目之一第一標記自 的資料,該第一特性資料包括識別該第一項目的一 識別記號; 在該系統中接收一第二項目的第二特性資訊,其 二特性資訊是從附著至該第二項目之一第二標記自 的資料,該第二特性資料包括識別該第二項目的一 識別記號; 在該系統中接收感應器資訊,其係來自由一結合 二項目的一感應器所感應的資料,故該感應器資訊 少一存在於該第二物品處之狀態; 在該系統中接收關係資訊,其指出該第一項目與 目間之實體上鄰近的一種關係; 在該系統中維護表示該第一項目的一第一實體物 第一實體物件維護代表該第一特性資訊之資訊; 在該系統中維護表示該第二項目的一第二實體物 第二實體物件維護代表該第二特性資訊之資訊; 在該系統中維護一情境物件,其表示在該第一項 二項目間之實體上鄰近的該關係; 依據在該情境物件中所表示之該第一項目與第二 之實體上鄰近的該關係,而將該感測器資訊與該第 物件相關聯,該感測器資訊係來自由一結合至該第 中該第 動讀取 種第一 中該第 動讀取 種第二 至該第 表示至 第二項 件,該 件,該 目與第 項目間 一實體 二物品 163 1310919 的一感應器所感應的資料,故該感測器資訊被決定以描述 至少一存在於該第一物品處之狀態; 將該感測器資訊與該第一特性資訊相比較; 依據該感測器資訊與該第一特性資訊之比較結果,而決 定一警示狀態存在於該第一物品處; 因應於該所決定之警示情況,而產生一正待被寫入至該 第一項目之更新的特性資訊; 在該警示情況被決定為存在後,於一系統中偵測到該第 一標記係出現在一標記寫入區;及 於偵測到該第一標記係位於該標記寫入區之後,使該標 記寫入區於該處將該更新資訊寫入至該第一標記。 43·—種實質儲存在一電腦可讀取記錄媒體上之電腦程式 產品,其係可用於一商業資料處理環境t,該環境包含一 供應鏈中的多個企業,該產品係可操作以使資料處理設備 進行下列步驟: 提供該企業位於供應鏈中之項目位置的即時可見度,其 係藉由以下步驟達成: 自一第一企業接收多次標記讀取資料,每次包括自附著 於一項目之一標記所讀取的資訊,該所讀取的資訊包括自 動地從該標記讀取的一種唯一標記識別記號,當該標記識 別記號自該標記被讀取時,每次也包括含有該對應標記之 164 1310919 一位置以及其附著項目的狀態資訊,該位置包括一 一緯度,自該企業讀取的多次標記讀取資料全體係 附著於多個項目之標記所讀取的資訊; 使用自第一企業接收的該標記讀取資料來維 目的配置資訊; 自一第二企業接收多次第二標記讀取資料,每 自附著於一項目之一標記所讀取的資訊,該項目係 不同於從該第一企業處接收標記讀取資料的該項目 讀取的資訊包括自動地從該標記讀取的一種唯一標 記號,當該標記識別記號自該標記被讀取時,每次 含有該對應標記的一位置以及其附著項目的狀態資 位置包括一經度與一緯度,自該企業讀取的多次標 資料整體係包含自附著於多個項目之標記所讀取的 使用自第二企業接收的該標記讀取資料來維 目的配置資訊,其中自任一方企業接收的關於一特 之標記讀取資料係被用來更新該配置資訊;以及 使該配置資訊可以被該供應鏈中的多個企業^ 括該第一及第二企業。 44. 一種實質儲存在一電腦可讀取記錄媒體上之電 產品,其係可於感應器裝置與高階應用程式間做 輸,該產品可操作以使資料處理設備進行下列步驟 接收一組規則,該規則指出提供哪些資料至一外 經度與 包含自 護該項 次包括 相同或 ,該所 記識別 也包括 訊’該 記讀取 資訊; 護該項 定項目 |·見,包 腦程式 資料傳 t 部應用 165 1310919 程式; 自一或更多標記讀取器接收包括項目識別記號 資料,每個自一數位標記讀取中的項目識別記號附 實體項目,該項目識別記號可唯一地識別該項目; 自其他感應器裝置接收額外的項目資料,該其他 器裝置是與標記讀取器不同的裝置,該額外項目資 或更多由該標記讀取器識別的項目相關; 使用該規則、項目識別記號以及額外的項目資料 將哪些項目識別記號及額外項目資料的子集合提供 部應用程式;及 提供僅包含該接收之項目識別記號及額外項目資 集合的資料給該外部應用程式;從外部應用程式中 料,該資料包括用於控制一致動器裝置之組態資料 將該組態資料轉換成一相容於該致動器裝置之格 及 提供該經轉換之組態資料給該致動器裝置。 的項目 著於一 的感應 料與一 以決定 給該外 料的子 接收資 9 式;以 166The configuration information includes a plurality of project characteristics; and the authorization information indicates which project characteristics are visible to the enterprise for at least one project characteristic. 3. The method of claim 32, wherein: the plurality of enterprises comprises a source enterprise and a destination enterprise: the source enterprise has a 159 1310919 order document for one of the orders issued by the enterprise for the purpose. And a shipping document relating to the delivery of a physical shipment to prepare for the order made by the enterprise of the purpose; the visibility includes visibility of the relationship between the marked reading material and the corporate document, the business document including the order document and the shipping document; Providing instant visibility of the enterprise project configuration, which further includes: receiving shipping information, including the following items; marking identification marks corresponding to the goods in the shipment; for the shipping documents, identifying each marking with a shipment The information combined with the number, and information about the shipping number with an order number in the order file: correlating the marked reading data with the shipping information; and making the association available to the destination company, thus The target company can use a label for one of the items in the shipment To confirm that the shipment identification symbol. 38. A method for contextual awareness and instant tracking of a project, comprising at least the steps of: receiving a set of rules indicating which information is provided to an external application; receiving from one or more tag readers comprises Item identification item project data, each item identification mark in the one-digit mark reading is attached to a physical item, the item identification mark can uniquely identify the item; receive additional item data from other sensor devices, the other Inductive 160 1310919 device is a different device than the tag reader, the additional project material is associated with one or more items identified by the tag reader; using the rule, project identification mark and additional project data to determine Providing a subset of the item identification mark and additional item data to the external application: and providing the external application with only a subset of the received item identification mark and additional item data; receiving the data from the external application , the information includes configuration resources for controlling the actuator device ; This configuration transforming data into a format compatible with that of the actuator device; and provide the converted configuration data to the means of the actuator. 3 9. The method of claim 3, wherein the decision is completed immediately and the information is provided immediately. 40. The method of claim 3, further comprising the steps of: summarizing a project identification mark and additional project data. 41. A computer product substantially stored on a computer readable recording medium for context aware and instant item tracking, the product comprising operational instructions for causing a programmable processor to perform the following steps: 161 1310919 receiving multiple mark reading data, each time including information read from a mark attached to one item, the read information includes a unique digital identification mark read from the mark, and one of the corresponding marks The position and the attached item, the time when the unique digit identification mark is read from the mark, the characteristic data, and the rule data, and the multiple mark read data system includes the mark attached to the plurality of items. Information received; one or more contextual information, each time a description related to the status of an unmarkable entity, the context information including a location, a time, characteristic data and rule data of the situation, the multiple context information The entire system includes information that describes multiple conditions; using the received tag to read data and contextual information to maintain a virtual world An entity data processing structure and a context data processing structure, the entity data processing structure including a data processing structure for each item, and the context data processing structure includes a data processing structure for each condition, the data processing structure is stored a characteristic data and rule data corresponding to the item or condition; detecting the interaction between the data processing structures occurring in the virtual world based on the location, the time, and/or the characteristic data; and based on the interaction and The rule data is activated. 42. A computer program product physically stored on a computer readable recording medium, wherein the information attached to the rewritable mark of an item is updated, the product comprising operable instructions for programmatic processing The device performs the following steps 162 1310919; receiving, in a system, a first characteristic information of a first item, wherein a characteristic information is information from a first label attached to one of the first items, the first characteristic data includes Identifying an identification mark of the first item; receiving, in the system, second characteristic information of a second item, wherein the second characteristic information is information from a second tag attached to one of the second items, the second characteristic The data includes an identification mark identifying the second item; receiving sensor information in the system, which is from a sensor sensed by a sensor combined with the two items, so that the sensor information is less than one in the second a state of the item; receiving, in the system, relationship information indicating a relationship between the first item and the entity on the object; maintaining the first in the system The first physical object of the project maintains information representing the first characteristic information; maintaining a second physical object representing the second item in the system to maintain information representative of the second characteristic information Maintaining a contextual object in the system, the entity representing the relationship between the first item and the second item; the first item being adjacent to the second entity represented by the context item a relationship, wherein the sensor information is associated with the first object, the sensor information is derived from a first to the first movable reading species, the second active reading species second to the first Representing the data sensed by a sensor of the second item, the item, the item and the second item 163 1310919 of the item, so the sensor information is determined to describe at least one existing at the first item a state of comparing the sensor information with the first characteristic information; determining, according to a comparison result between the sensor information and the first characteristic information, that a warning state exists at the first item Generating an updated feature information to be written to the first item in response to the determined alert condition; detecting the first tagging system in a system after the alert condition is determined to be present Appearing in a mark write area; and after detecting that the first mark is located in the mark write area, causing the mark write area to write the update information to the first mark there. 43. A computer program product stored substantially on a computer readable recording medium for use in a commercial data processing environment t, the environment comprising a plurality of businesses in a supply chain operable to The data processing device performs the following steps: providing instant visibility of the location of the project in the supply chain, which is achieved by the following steps: receiving multiple tags from a first enterprise to read data, each time including self-attachment to a project One of the marks reads the information, the read information includes a unique mark identification mark that is automatically read from the mark, and when the mark identification mark is read from the mark, each time including the corresponding Marked 164 1310919 a location and status information of its attached items, the location includes one-to-one latitude, the information read from the mark of the multiple-element read data of the whole system attached to the plurality of items; The first enterprise receives the tag to read the data to maintain the configuration information; the second enterprise receives the second tag to read the data, each self Information that is attached to a tag that is read by a tag that is different from the one that is read from the first enterprise and that reads the tag from the first enterprise, including a unique tag number that is automatically read from the tag. When the mark identification mark is read from the mark, each time a position including the corresponding mark and the status position of the attached item include a longitude and a latitude, the plurality of standard data read from the enterprise includes The configuration information read by the tag attached to the plurality of items and used by the second enterprise to retrieve the configuration information, wherein the tag reading data received from either enterprise is used to update the tag information. Configuring information; and enabling the configuration information to be included in the first and second businesses by a plurality of enterprises in the supply chain. 44. An electrical product substantially stored on a computer readable recording medium for transposing between a sensor device and a high level application, the product being operative to cause the data processing device to perform a set of rules by performing the following steps, The rule indicates which information is provided to an external longitude and includes the same or includes the self-protection. The identification also includes the message of the record; the protection of the item | see, the brain-package data transmission t Application 165 1310919 program; receiving, from one or more tag readers, project identification tag data, each item identification tag in a digital tag reading attached to a physical item, the item identification mark uniquely identifying the item; Receiving additional project data from other sensor devices that are different from the tag reader, the additional project or more related to the item identified by the tag reader; using the rule, project identification mark And a subset of the project identification marks and additional project materials provided by the additional project materials; and Providing information to the external application only for the received project identification mark and the additional project resource set; from the external application material, the data includes configuration data for controlling the actuator device to convert the configuration data into one Compatible with the actuator device and providing the converted configuration information to the actuator device. The project is based on one of the sensing materials and one to determine the sub-receipt for the external material;
TW92100575A 2002-01-11 2003-01-10 Context-aware and real-time item tracking system architecture and scenariors TWI310919B (en)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US34767202P 2002-01-11 2002-01-11
US35319802P 2002-02-01 2002-02-01
US10/137,207 US7151453B2 (en) 2002-01-11 2002-04-30 Bi-directional data flow in a real time tracking system
US10/136,852 US7233958B2 (en) 2002-02-01 2002-04-30 Communications in an item tracking system
US10/210,859 US7290708B2 (en) 2002-07-31 2002-07-31 Integration framework
US10/232,764 US6901304B2 (en) 2002-01-11 2002-08-30 Item tracking system architectures providing real-time visibility to supply chain
US10/255,115 US20030132855A1 (en) 2002-01-11 2002-09-24 Data communication and coherence in a distributed item tracking system
US10/285,381 US6843415B2 (en) 2002-01-11 2002-10-30 Event-based communication in a distributed item tracking system

Publications (2)

Publication Number Publication Date
TW200307208A TW200307208A (en) 2003-12-01
TWI310919B true TWI310919B (en) 2009-06-11

Family

ID=45072338

Family Applications (1)

Application Number Title Priority Date Filing Date
TW92100575A TWI310919B (en) 2002-01-11 2003-01-10 Context-aware and real-time item tracking system architecture and scenariors

Country Status (1)

Country Link
TW (1) TWI310919B (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI508008B (en) * 2009-10-07 2015-11-11 Ibm Media system with social awareness
US11514373B2 (en) 2019-06-27 2022-11-29 Bigobject, Inc. Bionic computing system and cloud system thereof

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011014620A1 (en) 2009-07-29 2011-02-03 Reversinglabs Corporation Repairing portable executable files
CN108111489B (en) * 2017-12-07 2020-06-30 阿里巴巴集团控股有限公司 URL attack detection method and device and electronic equipment
CN111062638B (en) * 2019-12-26 2023-09-12 珠海金山数字网络科技有限公司 Project resource processing method and device

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI508008B (en) * 2009-10-07 2015-11-11 Ibm Media system with social awareness
US11514373B2 (en) 2019-06-27 2022-11-29 Bigobject, Inc. Bionic computing system and cloud system thereof
TWI803760B (en) * 2019-06-27 2023-06-01 核桃運算股份有限公司 Bionic computing system and cloud system thereof

Also Published As

Publication number Publication date
TW200307208A (en) 2003-12-01

Similar Documents

Publication Publication Date Title
US7969306B2 (en) Context-aware and real-time item tracking system architecture and scenarios
CN100378714C (en) Context-aware and real-time item tracking system architecture and scenarios
US6901304B2 (en) Item tracking system architectures providing real-time visibility to supply chain
Jones et al. RFID in logistics: a practical introduction
US6941184B2 (en) Exchange of article-based information between multiple enterprises
Banks et al. RFID applied
Asif Integrating the supply chain with RFID: A technical and business analysis
Glover et al. RFID essentials
US7151453B2 (en) Bi-directional data flow in a real time tracking system
US20080215719A1 (en) Data Communication and Coherence in a Distributed Item Tracking System
Schuster et al. Global RFID: the value of the EPCglobal network for supply chain management
US7260553B2 (en) Context-aware and real-time tracking
WO2003060752A1 (en) Context-aware and real-time item tracking system architecture and scenarios
CN112036901A (en) Method for protecting supply chain data in block chain and system for recording supply chain information
US20100241467A1 (en) Secure commerce and asset/supply chain management system
WO2006110257A2 (en) Rfid receiving process for use with enterprise resource planning systems
CN102948117A (en) Information tracking system and method
Zelbst et al. RFID for the Supply Chain and operations professional
CN111539677B (en) System and method for managing RFID fixed asset based on blockchain
Flanagan et al. Auto ID-Bridging the physical and the digital on construction projects
TWI310919B (en) Context-aware and real-time item tracking system architecture and scenariors
ZARE RFID: a bibliographical literature review with future research directions
Rivero-García et al. Blockchain-based ubiquitous transport and logistics monitoring system
JP7247649B2 (en) Information processing program, information processing method, and information processing apparatus
JP6668428B2 (en) Unit control method

Legal Events

Date Code Title Description
MK4A Expiration of patent term of an invention patent