A method and system for storing, retrieving, and managing data for tags
Abstract
This record has no abstract on file.
Term
Term ended
Expired 28 October 2024, 1.9 years ago.
- Priority
- Filed
- Granted
- Expired
- Today
27 claims: 8 independent, 19 dependent
- 11つまたは複数のオブジェクトに関するデータを格納し、取得し、および管理するためのシステムであって、 1つまたは複数のオブジェクトに関連付けられた1つまたは複数のタグと、 前記タグの少なくとも1つと通信する1つまたは複数のコンポーネントと、 前記コンポーネントと前記タグの間における前記通信を円滑にするための少なくとも1つの通信ネットワークとを含み、 前記複数のタグの少なくとも1つのタグは、制御ソフトウェアと当該制御ソフトウェアを実行するように動作するプロセッサを有し、前記少なくとも1つのタグに関連付けられた前記オブジェクトに関連するデータ、又は前記少なくとも1つのタグの動作に関するデータ、又はその両方のデータ、を送受信するように動作し、 前記コンポーネントの少なくとも1つは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストの少なくとも1つを前記少なくとも1つのタグに送信する制御権限部を含み、 前記プロセッサは、前記少なくとも1つのタグの動作に関するデータを処理し、前記制御権限部から前記クエリブロードキャストを受信し、前記少なくとも1つのタグに関連付けられた前記オブジェクトに関する前記データを前記制御権限部に送信し、前記イネーブルブロードキャストを前記制御権限部から受信し、他のタグからデータを受信するように前記少なくとも1つのタグを制御するように動作し、前記ディセーブルブロードキャストを前記制御権限部から受信し、前記少なくとも1つのタグが前記他のタグからのデータを受信することを無効にするように動作する、システム。
- 2前記関連付けられたオブジェクトに関する前 記デ ータは、前記関連付けられたオブジェクトと接触した人々の身元と、前記関連付けられたオブジェクトがさらされた少なくとも1つの環境条件の少なくとも1つの測定値と、前記オブジェクトの学業成績と、前記オブジェクトの運動成績と、前記オブジェクトの容体の少なくとも1つの測定値と、前記オブジェクトに関する真贋鑑定データと、前記オブジェクトの価格履歴と、前記オブジェクトの動きとから成るセットの1つまたは複数のメンバを含む請求項1に記載のシステム。
- 3前記1つまたは複数のコンポーネントは、前記少なくとも1つのタグから前 記デ ータを受け取るため、および 前記少なくとも1つのタグからの 前 記デ ータを管理するための少なくとも1つのデータベースを含む請求項1に記載のシステム。
- 4前記制御 権限部 は、前記少なくとも1つのタグがデータを受信することができる前記1つまたは複数のコンポーネントの少なくとも1つを指定する請求項1に記載のシステム。
- 5前記制御 権限部 は、前記少なくとも1つのタグが受信することを許可されている1つまたは複数のデータタイプを指定する請求項1に記載のシステム。
- 6前記1つまたは複数のコンポーネントは、クライアントコンピュータ、データベース、サーバコンピュータ、入力ユーティリティ、およびセンサから成るセットの1つまたは複数のメンバを含む請求項1に記載のシステム。
- 7前記1つまたは複数のタグは、無線周波数信号の送信および受信を行うマイクロデバイスである請求項1に記載のシステム。
- 81つまたは複数のオブジェクトに関するデータを格納し、取得し、および管理するための方法であって、 1つまたは複数のオブジェクトに1つまたは複数のタグを関連付けるステップと、 少なくとも1つの通信ネットワークを介して、1つまたは複数のコンポーネントから前記タグの少なくとも1つと通信するステップと、 前記複数のタグのうち、制御ソフトウェアと当該制御ソフトウェアを実行するように動作するプロセッサを有する少なくとも1つのタグが、前記少なくとも1つのタグに関連付けられた前記オブジェクトに関連するデータ、又は前記少なくとも1つのタグの動作に関するデータ、又はその両方のデータ、を送受信するように動作するステップと、を含み、 前記コンポーネントの少なくとも1つは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストの少なくとも1つを前記少なくとも1つのタグに送信する制御権限部を含み、 前記方法は、さらに、 前記プロセッサが、前記少なくとも1つのタグの動作に関するデータを処理し、前記制御権限部から前記クエリブロードキャストを受信し、前記少なくとも1つのタグに関連付けられた前記オブジェクトに関する前記データを前記制御権限部に送信し、前記イネーブルブロードキャストを前記制御権限部から受信し、他のタグからデータを受信するように前記少なくとも1つのタグを制御するように動作し、前記ディセーブルブロードキャストを前記制御権限部から受信し、前記少なくとも1つのタグが前記他のタグからのデータを受信することを無効にするように動作するステップを含む方法。
- 9前記関連付けられたオブジェクトに関する前 記デ ータは、前記関連付けられたオブジェクトと接触した人々の身元と、前記関連付けられたオブジェクトがさらされた少なくとも1つの環境条件の少なくとも1つの測定値と、前記オブジェクトの学業成績と、前記オブジェクトの運動成績と、前記オブジェクトの容体の少なくとも1つの測定値と、前記オブジェクトに関する真贋鑑定データと、前記オブジェクトの価格履歴と、前記オブジェクトの動きとから成るセットの1つまたは複数のメンバを含む請求項8に記載の方法。
- 10さらに、前記少なくとも1つのタグから前 記デ ータを受信するステップと、 前記少なくとも1つのタグからの 前 記デ ータを管理するステップと、を含む請求項8に記載の方法。
- 11前記制御 権限部 は、前記少なくとも1つのタグがデータを受信することができる前記1つまたは複数のコンポーネントの少なくとも1つを指定する請求項8に記載の方法。
- 12前記制御 権限部 は、前記少なくとも1つのタグが受信することを許可されている1つまたは複数のデータタイプを指定する請求項8に記載の方法。
- 13前記1つまたは複数のコンポーネントは、クライアントコンピュータ、データベース、サーバコンピュータ、入力ユーティリティ、センサ、およびタグから成るセットの1つまたは複数のメンバを含む請求項8に記載の方法。
- 141名または複数名の子供を管理するための方法であって、 1名または複数名の子供に1つまたは複数のタグを関連付けるステップであって、前記1つまたは複数のタグがプロセッサを有し、1つまたは複数のコンポーネントから、制御データと情報データとを受信するように動作し、前記プロセッサが、前記制御データに従って前記1つまたは複数のタグを制御するように前記制御データを処理し、前記1つまたは複数のタグが、前記制御データに従って、前記情報データまたは前記情報データの一部を送信するように動作する、ステップと、 前記1つまたは複数のタグに制御データおよび情報データを送信するステップと、 前記1つまたは複数のタグによって前記情報データを検知するステップであって、前記情報データは、前記1名または複数名の子供と接触した人々の身元、前記1名または複数名の子供がさらされた少なくとも1つの環境条件の少なくとも1つの測定値、前記1名または複数名の子供の学業成績、前記1名または複数名の子供の運動成績、前記1名または複数名の子供の容体の少なくとも1つの測定値の1つまたは複数を含む、ステップと、 前記制御データを処理し、少なくとも1つのタグが、別のタグから情報データを受信するか、特定された情報データを送信するか、所定タイプの送信データのみを受け付けるか、の何れかを実行するように制御するステップと、を含み、 前記制御データは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストを含み、 前記コンポーネントの少なくとも1つは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストの少なくとも1つを前記少なくとも1つのタグに送信する制御権限部を含み、 前記方法は、さらに、 前記プロセッサが、前記少なくとも1つのタグの動作に関するデータを処理し、前記制御権限部から前記クエリブロードキャストを受信し、前記少なくとも1つのタグに関連付けられた前記子供に関する前記データを前記制御権限部に送信し、前記イネーブルブロードキャストを前記制御権限部から受信し、他のタグからデータを受信するように前記少なくとも1つのタグを制御するように動作し、前記ディセーブルブロードキャストを前記制御権限部から受信し、前記少なくとも1つのタグが前記他のタグからのデータを受信することを無効にするように動作するステップを含む方法。
- 15前記制御データは、前記少なくとも1つのタグがデータを受信することができる前記1つまたは複数のタグの少なくとも1つを指定する請求項14に記載の方法。
- 16前記制御データは、前記少なくとも1つのタグが受信することを許可されている1つまたは複数のデータタイプを指定する請求項14に記載の方法。
- 171つまたは複数のオブジェクトを含む在庫を管理するための方法であって、 前記1つまたは複数のオブジェクトに1つまたは複数のタグを関連付けるステップであって、前記1つまたは複数のタグがプロセッサを有し、1つまたは複数のコンポーネントから、制御データと情報データとを受信するように動作し、前記プロセッサが、前記制御データに従って前記1つまたは複数のタグを制御するように前記制御データを処理し、前記1つまたは複数のタグが、前記制御データに従って、前記情報データまたは前記情報データの一部を送信するように動作する、ステップと、 前記1つまたは複数のタグに制御データおよび情報データを送信するステップと、 前記1つまたは複数のタグの中に前記情報データを受信するステップであって、前記情報データは、前記1つまたは複数のオブジェクトの位置、前記1つまたは複数のオブジェクトが、前記位置に存在していた時刻、前記1つまたは複数のオブジェクトを入手した、または手放した人々の身元、前記1つまたは複数のオブジェクトと接触した人々の身元、前記1つまたは複数のオブジェクトがさらされた少なくとも1つの環境条件の少なくとも1つの測定値、前記1つまたは複数のオブジェクトの重量、前記1つまたは複数のオブジェクトが、前記重量を有していた時刻、前記1つまたは複数のオブジェクトの寸法、および前記1つまたは複数のオブジェクトが、前記寸法を有していた時刻の1つまたは複数を含むステップと、 前記制御データを処理し、少なくとも1つのタグが、別のタグから情報データを受信するか、特定された情報データを送信するか、所定タイプの送信データのみを受け付けるか、の何れかを実行するように制御するステップと、を含み、 前記制御データは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストを含み、 前記コンポーネントの少なくとも1つは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストの少なくとも1つを前記少なくとも1つのタグに送信する制御権限部を含み、 前記方法は、さらに、 前記プロセッサが、前記少なくとも1つのタグの動作に関するデータを処理し、前記制御権限部から前記クエリブロードキャストを受信し、前記少なくとも1つのタグに関連付けられた前記オブジェクトに関する前記データを前記制御権限部に送信し、前記イネーブルブロードキャストを前記制御権限部から受信し、他のタグからデータを受信するように前記少なくとも1つのタグを制御するように動作し、前記ディセーブルブロードキャストを前記制御権限部から受信し、前記少なくとも1つのタグが前記他のタグからのデータを受信することを無効にするように動作するステップを含む方法。
- 18前記制御データは、前記1つまたは複数のタグが、データを受信することができる前記1つまたは複数のタグの少なくとも1つを指定する請求項17に記載の方法。
- 19前記制御データは、前記1つまたは複数のタグが受信することを許可されている1つまたは複数のデータタイプを指定する請求項17に記載の方法。
- 20さらに、前記少なくとも1つのタグから前記情報データを受信するステップと、 前記情報データを管理するステップと、を含む請求項17に記載の方法。
- 21前記制御データおよび情報を送信するステップは、クライアントコンピュータ、データベース、サーバコンピュータ、入力ユーティリティ、センサ、およびタグから成るセットの1つまたは複数のメンバを含む1つまたは複数のコンポーネントによって実行される請求項17に記載の方法。
- 22前記コンポーネントの前記少なくとも1つから少なくとも1つのクエリを送信して、前記少なくとも1つのタグに関連付けられた前記オブジェクトについての前記情報データの少なくとも一部分を受信するステップをさらに含む請求項21に記載の方法。
- 231つまたは複数のオブジェクトを含む在庫を管理するためのシステムであって、 前記1つまたは複数のオブジェクトに関連付けられた1つまたは複数のタグと、 前記1つまたは複数のタグに制御データおよび情報データを送信することが可能な1つまたは複数のコンポーネントと、 前記タグの少なくとも1つの中に含まれる、前記コンポーネントの少なくとも1つからの前記制御データおよび前記情報データを受信することが可能な少なくとも1つの受信機と、 前記制御データに従って、前記少なくとも1つのタグから前記情報データの少なくとも一部分を送信することが可能な少なくとも1つの送信機と、を有し、 前記情報データは、前記1つまたは複数のオブジェクトの位置、前記1つまたは複数のオブジェクトが、前記位置に存在していた時刻、前記1つまたは複数のオブジェクトを入手した、または手放した人々の身元、前記1つまたは複数のオブジェクトと接触した人々の身元、前記1つまたは複数のオブジェクトがさらされた少なくとも1つの環境条件の少なくとも1つの測定値、前記1つまたは複数のオブジェクトの重量、前記1つまたは複数のオブジェクトが、前記重量を有していた時刻、前記1つまたは複数のオブジェクトの寸法、および前記1つまたは複数のオブジェクトが、前記寸法を有していた時刻の1つまたは複数を含み、 前記コンポーネントの少なくとも1つは、クエリブロードキャスト、イネーブルブロードキャスト、およびディセーブルブロードキャストの少なくとも1つを前記少なくとも1つのタグに送信する制御権限部を含み、 前記複数のタグの少なくとも1つのタグは、前記制御データを実行するように動作するプロセッサを有し、 前記プロセッサは、前記少なくとも1つのタグの動作に関するデータを処理し、前記制御権限部から前記クエリブロードキャストを受信し、前記少なくとも1つのタグに関連付けられた前記オブジェクトに関する前記データを前記制御権限部に送信し、前記イネーブルブロードキャストを前記制御権限部から受信し、他のタグからデータを受信するように前記少なくとも1つのタグを制御するように動作し、前記ディセーブルブロードキャストを前記制御権限部から受信し、前記少なくとも1つのタグが前記他のタグからのデータを受信することを無効にするように動作する、システム。
- 24前記制御データは、前記1つまたは複数のタグが、データを受信することができる前記1つまたは複数のタグの少なくとも1つを指定する請求項23に記載のシステム。
- 25前記制御データは、前記1つまたは複数のタグが受信することを許可されている1つまたは複数のデータタイプを指定する請求項23に記載のシステム。
- 26前記コンポーネントは、クライアントコンピュータ、データベース、サーバコンピュータ、入力ユーティリティ、センサ、およびタグから成るセットの1つまたは複数のメンバを含む請求項23に記載のシステム。
- 27前記制御データは、前記少なくとも1つのタグに関連付けられた前記オブジェクトについての前記情報データの少なくとも一部分を受け取る少なくとも1つのクエリを含む請求項23に記載のシステム。
Independent claims27
75 paragraphs, as filed
The present invention generally relates to methods and systems for storing, retrieving, and managing data about tags associated with any type of object in any way. More specifically, the present invention manages writing data to those tags, reading data from those tags, and managing the data written to those tags and / or the data read from those tags. Do what you do.
The present invention stores, retrieves, and manages data about any type of tag associated with any type of object, physically or abstract, biological or inanimate, in any type of form. The methods and systems for doing so are involved. A tag is a device, any device that sends, receives, and / or stores data about whatever the device is monitoring or associated with, and is a tag. There are any type of satellite communication network, such as RFID (Radio Frequency Identification Device) tags, laser tags, cellular phones, devices that receive and transmit signals from television networks, and GPS (Global Positioning System). Includes many different types, such as, and others. The tag can be powered by any type of power source, such as DC power, AC power, solar, and so on. The identification device is described in "Electronic Identification & Recognition", the content of which is incorporated herein by reference. It is further explained in US Pat. No. 3,752,960, issued to Charles Walton, entitled "System." The types of objects that can be associated with tags include real estate, paintings, diamonds, jewelery, such as people, animals, plants, objects of any kind, homes, lands, condominiums, mobile homes, and townhouses. Expensive items such as watches and antiques, movable items such as automobiles, planes, military vehicles, bicycles, motorcycles, boats, ships, and more components, locations, environmental conditions, abstractions, concepts, phenomena, etc. Included, but not limited to. The association between a tag and an object can be of any type, including, but not limited to, one-to-many, many-to-one or one-to-one, physical, logical, and so on. Physical associations can include attaching and / or inserting tags to the associated object of the tag.
The present invention can be adapted to a wide variety of applications. For example, using the methods and systems of the present invention, authenticating expensive items, tracking any kind of object through manufacturing, supply chain, distribution, etc. to the sales floor and beyond. Manage inventory, track the movement of objects such as people, animals, plants, movable items, etc., get historical data such as price history from things such as expensive items and real estate Obtaining any type of health data from humans and animals, such as physical condition, treatment history, medication instructions, heart rate, pulse rate, body temperature, blood, oxygen, sugar, etc. for humans and animals, etc. It is possible to track any type of health condition, such as the amount of different substances in the body.
Many different benefits can arise from the various uses of the invention. For example, the use of the present invention may reduce the cost of identifying the value of things such as expensive items. This is because, for example, price history for the item, and other similar data, can be easily stored and retrieved from the associated tag for the item. With the availability of price history from tags associated with a home, as well as price history from other homes in the same area, the seller has little or no knowledge of the actual value of the home. It may prevent you from demanding an exorbitantly high amount of payment from a non-buyer. The use of the present invention may prevent the illegal replacement of expensive items with imitations. This is because the identification data from the associated tag of the item can be used to verify the authenticity of the item. The use of the present invention may prevent the owner of a vehicle from grabbing a damaged vehicle as an undamaged vehicle by an unsuspecting buyer. This is because the car accident history can be stored and retrieved from the car's associated tag. The use of the present invention may prevent the theft of military secrets. This is because it is possible to easily access the authorization information from the tags associated with a person to determine if the person should have access (right) to such a secret. The use of the present invention may avoid injuries or even deaths of athletes that may occur while the athlete is competing. This is because the athlete's heart rate, temperature, and other physical conditions can be easily monitored. For the same reason, coaches use the invention to make any player too tired to be. It is possible to quickly determine whether it is effective), and an athlete scout (recruiter) can use the present invention to determine which athlete can respond better to the severity of the competition. It is possible for an athlete trainer to use the present invention to tailor a training program to a particular athlete. By using the present invention, it is possible to facilitate the authenticity of evidence in court. This is because in court, the chain of custody can be easily obtained from the tag associated with the evidence. The use of the present invention further automates and simplifies inventory management.
Tags, and similar devices, are disclosed in other references, but all prior art references include a variety of applications, including authentication, tracking, medical surveillance, medical management, knowledge acquisition, and more. With respect to, it does not disclose the use of such tags in systems and methods for storing, retrieving, and managing data. In contrast, for example, US Pat. No. 6,440,096, US Pat. No. 5,358,514, US Pat. No. 5,193,540, US Pat. No. 6,107,102, and US Pat. No. 6,405,066 explain that microdevices are embedded in humans. There is. US Pat. No. 5,606,260, US Pat. No. 4,892,709, US Pat. No. 5,367,878, US Pat. No. 6,152,181, US Pat. No. 5,834,790, US Pat. No. 5,186,001, US Pat. No. 5,839,056, and US Pat. No. 5,144,298 Describes the use of a microdevice as a sensor or controller.
Therefore, there is a need for systems and methods for storing, retrieving, and managing data about any type of tag associated with any type of object in any type of form.
<p> The present invention provides systems and methods for storing, retrieving, and managing data for any type of tag associated with any type of object in any type of object for various applications. ..</p>
<p> In particular, certain aspects of the invention include A system for storing, retrieving, and managing data about one or more objects. With one or more tags associated with one or more objects, With one or more components communicating with at least one of the tags, At least one receiver for receiving control data and information data from at least one of the components in at least one of the tags, the information data being associated with the at least one tag. The receiver for the object and With at least one transmitter for transmitting at least a portion of the information data to at least one of the components according to the control data. Includes at least one communication network to facilitate the communication between the component and the tag. At least one of the components provides a system that sends at least one query to receive at least a portion of the information data about the object associated with the at least one tag.</p><p> A further aspect of the present invention is A method for storing, retrieving, and managing data about one or more objects. With the step of associating one or more tags with one or more objects, With the step of communicating with at least one of the tags from one or more components, A step of receiving control data and information data from at least one of the components in at least one of the tags, wherein the information data is about an object associated with the at least one tag. A step of transmitting at least a portion of the information data from the at least one tag to at least one of the components according to the control data. Provided to provide a system comprising sending at least one query from said at least one of said components and receiving at least a portion of said information data about said object associated with said at least one tag. is there.</p><p> A further aspect of the present invention is It s a way to manage a child, With the step of associating one or more tags with one or more children, The step of transmitting control data and information data to the one or more tags, and A step of receiving the information data in the one or more tags, the information data exposing the identities of people who have come into contact with one or more children, one or more children. At least one measurement of at least one environmental condition, academic performance of one or more children, exercise performance of one or more children, and at least one measurement of the condition of one or more children. Steps on one or more values, and The present invention provides a method including a step of transmitting at least a part of the information data from the at least one tag according to the control data.</p><p> The above and other aspects and features of the present invention, along with the accompanying drawings, will be more clearly understood from the following detailed description.</p>
The present invention stores data on any type of tag associated with any type of object (physical or abstract, living or inanimate) in any type of form for various applications. And provide a system and method for acquiring, and managing.
Although the present invention is described in the scope of several different applications, such as authenticating objects containing expensive items and evidence, and monitoring children by parents of children, the present invention describes objects of any kind. It can be applied to any application where the storage, retrieval, and management of data about the tags associated with is beneficial. Examples of their application are the exchange of objects such as real estate, goods, and services, the sick. ill), monitoring the vital signs of the elderly, and athletes, monitoring environmental conditions, traffic, and consumer behavior in various settings such as exercise training programs, parks, shopping centers, casinos, etc. Tracking the location of people such as prisoners, students, foreigners, military personnel, and workers in confidential areas, via manufacturing, supply chain, distribution, etc., to the sales floor, and beyond, inventory, etc. Tracking the location of any type of supplies, tracking the location of confidentially designated materials, manufacturing history, sales history, and repair history of supplies such as machines, automobiles, planes, trains, and more components. Tracking, monitoring the movement of people and objects such as vehicles, traffic, etc. on battlefields, highways, etc., monitoring the flow of oil and other liquids in pipelines, etc. Is included.
FIG. 1 is a block diagram 100 showing a main operation configuration of the present invention. The present invention relates to real estate such as people, animals, plants, objects of any kind, homes, land, condominiums, mobile homes, and townhouses, and expensive items such as paintings, diamonds, jewelry, watches, and antiques. Can be associated with any type of object, including vehicles such as cars, planes, military vehicles, bicycles, motorcycles, boats, ships, components, locations, environmental conditions, abstractions, concepts, phenomena, etc. , It is possible to include one or more tags 102. The association between the tag and the object can be of any type, including one-to-many, many-to-one, or one-to-one. Their associations can be physical, logical, or otherwise. The physical association can include attaching the tag to the associated object of the tag and / or inserting it within such an object. Logical associations can include information in the database, such as tables where the correspondence between one or more tags and one or more objects can be established by their identification numbers. It is possible.
Tag 102 can be one of a variety of different types, including RFID (Radio Frequency Identification Device) tags, laser tags, cellular phones, devices that receive and transmit signals from GPS (Global Positioning System), and more. Is. Tag 102 is DC power, AC power, solar power (solar) It can be powered by any kind of power source, such as power), etc. Each tag 102 can have the ability to receive data, store data, detect data, and / or transmit data. Data can be received and transmitted to other tags 102, sensors 104, computer 106, and database management system 110. The tag 102 can have the ability to detect data from the associated objects of the tag 102, the environment of the tag 102, and so on. Data detected from associated objects, such as a person or animal, can include medical data such as body temperature, oxygen content in blood, heart rate, and more. Data detected from the environment can include various gases, poisons, pollutants content, temperature, humidity, barometric pressure, chemicals, movement, light, sound, etc. in the air or water. is there.
The present invention 100 can further include a sensor 104. The sensor 104 can be of any type and can detect any type of data. The sensor 104 can be powered by any type of power source, such as AC power, DC power, solar power, and so on. The sensor 104 can include a thermometer, a motion detector, a GPS (Global Positioning System) device, a chemical sensor, and the like. Computer 106 provides a database management system 110 for arbitrarily storing and managing data associated with tag 102, including data transmitted to and / or retrieved from tag 102. It can be included. Data can be sent from computer 106 to tag 102 for storage within tag 102, and can also be sent from tag 102 to computer 106. The data acquired from the tag 102 can be stored and managed in the database management system 110.
The present invention can further include a communication network 114, which comprises a variety of different types of components and software that communicate different types of data between tags 102, sensors 104, computers 106, and others. It can be included. These components and software include modulators / demodulators (modems), satellites, frequency up and down frequency converters, including those for communication with satellites, audio / video encoders, routers. , Hubs, bridges, etc. can be included. In one embodiment, the communication network 114 can be a cellular telephone network. In another embodiment, the communication network 114 can be any type of satellite network, such as GPS. In another embodiment, the communication network can be a television network. In another embodiment, the communication network 114 can include the Internet. Communication is World Wide It can be reached on the Internet by one or more Internet applications, including the Web. The communication network 114 may be an intranet or an extranet. An intranet is a private network, typically a LAN (Local Area Network) or WAN (Wide Area Network), that enables the use of Internet-based applications in a secure private environment. An extranet is an intranet-type network that links multiple sites or multiple organizations using intranet-related technologies.
The World Wide Web is built on a protocol called HTTP (Hypertext Transfer Protocol). The computer 106 can include browser software 108 for requesting data entered by tags 102 and sensors 104 and / or data stored in the database management system 110. Requests for data from browser software 108 can be handled by server software 109. The server software 109 can find the requested data and send the data to the requesting browser software 108. Computer 106 can further include application server software 111, which can extend the capabilities of server software 109. In particular, the application server software 111 can preprocess the data page before it is sent to the requesting browser software 108.
In one embodiment, the application server software 111 is a ColdFusion application. Cold Fusion is described in Chapter 1, "The Macromedia Cold Fusion 5 Web Application Construction Kit," Ben Forta and Nate Weiss, Forth Edition (hereafter "Cold Fusion 5"), the contents of which are incorporated herein by reference. As specified, in World Wide web applications for creating dynamic page applications and interactive websites by combining standard HTML (Hypertext Markup Language) files with ColdFusion (Cold Fusion Markup Language) instructions. is there. HTML is a page markup language that allows you to create and lay out pages and forms. In one embodiment of the invention, Cold The Fusion application defines a fill-in form for data entry, including data that controls the behavior of tags 102 and sensors 104, and queries that ask for the data.
In one embodiment, the ColdFusion application 111 is used to retrieve or update the data in the database management system 110. Cold Fusion application 111 can access the database management system 110 through an interface called ODBC (Open Database Connectivity), which is incorporated herein by reference, ColdFusion 5, Chapter. As explained in 6, it is a standard API (application programming interface) for accessing information from different database systems and different formats.
In another embodiment, the data may be entered using a program written in a language that manipulates text, files, and information. An exemplary language is the PERL specified in "Programming Perl", Larry Ward and Randal L. Schwartz, O'Reilly & Associates, Inc., March 1992, the content of which is incorporated herein by reference. Is.
The database 110 may be a distributed database that can be stored among many computers 106 or a central database. Database 110 can be of any type, including relational or hierarchical databases. Databases and database management systems are described in Database System Concepts, Henry F. Korth, Abraham Silberschatz, McGraw-Hill 1986, Chapter 1, whose contents are incorporated herein by reference. The exemplary database 110 includes Microsoft SQL (Structured Query Language) Server, Microsoft Access 1.0, 2.0, and 7.0, Microsoft FoxPro 2.0, 2.5, and 2.6, Oracle 7.0, Borland Paradox 3.X and 4.X, Borland. Includes dBase III and dBase IV, as well as Microsoft Excel 3.0, 4.0, and 5.0.
In one embodiment, data is retrieved, inserted, updated, or deleted from database 110 using SQL (Structured Query Language). SQL is incorporated herein by reference, "SAMS Teach Yourself SQL", 2<sup>nd</sup> Explained in Edition, Ben Forta.
The present invention can include additional components that manage data retrieved from tags 102, sensors 104, and other locations. Those additional components can include exploration tools. In one embodiment, the search tool is Verity. The data can be organized into one or more collections. It is then possible to use Verity to index the collection and edit the metadata about the collection so that Verity can quickly explore the collection. Conceptually, the usefulness of Verity is when you are asked to index information about a collection, edit that information, and use that information to quickly explore the collection. Due to the ability of Verity to be able to. Search and query are conceptual operators such as STEM, WORD, and WILD CARD, neighbor operators such as NEAR and PHRASE, relational operators such as CONTAINS, MATCHES, STARTS, ENDS, and SUBSTRING, CASE, MANY, NOT, and ORDER. It can be specified using the Verity operator, including search modifiers such as, and score operators such as YES NO, COMPLEMENT, PRODUCT, and SUM. Search form pages and search result pages can be defined using HTML and Cold Fusion tags. Creating and exploring collections and displaying search results using Verity is incorporated herein by reference in ColdFusion 5, Chapter 5. It is explained in 36. The web browser software 108 can display a web page from the server software 109 that includes an entry form for data entry, an entry form for entering search conditions, and search result text data. The invention also uses an on-demand video-audio streaming server, such as RealServer, described in the RealServer Administration and Content Creation Guide, the content of which is incorporated herein by reference. And the audio and video data input by the sensor 104 can also be displayed.
In another embodiment, the search engine may be a commercial search engine such as Alta Vista, Google, Yahoo, or the like. The commercial search engine can be incorporated into the present invention using the ColdFusion tags described in ColdFusion 5, Chapter 36.
Before performing the search, the search engine queries as specified in Database System Concepts, Henry F. Korth, Abraham Silberschatz, McGraw-Hill 1986, Chapter 9, whose contents are incorporated herein by reference. Can be optimized.
FIG. 2 is a data flow diagram 200 showing the storage of data in the tag 102 associated with any type of object. A data flow diagram is a graph in which nodes are processes and arcs are data flows. "Object Oriented Modeling and Design," Rumbaugh, J., Prentice Hall, which is incorporated herein by reference. Inc. (1991), Chapter See 1. The data defines what type of data the tag 102 is allowed to receive and / or send, send the data to the tag 102, or receive the data from the tag 102. It can consist of control data that governs the behavior of tag 102, such as by identifying components that can (ie, other tags 102, computer 106, browser software 108, server software 109, sensors 104, etc.). Yes, it can consist of information to be stored within tag 102. At step 202, tag 102 can wait for data to be received. The process proceeds to step 204 when the data is received. In step 204, the tag 102 is capable of receiving data, which includes the computer 106, the browser software 108, the server software 109, the database 110, the sensor 104, another tag 102, the tag 102 itself, and so on. It can be transmitted from any type of component, including, but not limited to. At step 206, a check can be performed to determine if the received data is allowed to be stored in the tag 102. Step 206 can include checking if the source of the data has the authority to store the type of data received at tag 102.
Inspections are secured by any other type of security, including cryptography, art and science that keeps messages secure, intranets, VPNs (Virtual Private Networks), and more. It can be performed by a variety of different techniques, including but not limited to those that use the communication. Cryptography can be used herein for authentication, integrity, and / or non-repudiation. Authentication allows the recipient of a message to determine the source of the message. Consistency allows the recipient of the message to verify that the message has not been modified during transmission. Non-repudiation prevents the sender of a message from falsely denying that the sender actually sent the message.
In one embodiment, a symmetric algorithm is used. In a symmetric algorithm, the encryption key is calculated from the decryption key and vice versa. The key must remain secret so that the communication is kept secret. In another embodiment, a public key algorithm (also called an asymmetric algorithm) is used. In the public key algorithm, the decryption key cannot be calculated from the encryption key in a reasonable amount of time. The encryption key is public and is called the public key. The decryption key is left secret and is called the secret key. In another embodiment, digital signatures can be used. In digital signatures, the message is encrypted by the sender using the private key, which signs the message and is decrypted by the recipient using the public key, which verifies the signature. Will be done. Exemplary digital signature algorithms include RSA (Rivest-Shamir-Adelman) and DSA (Digital Signature Algorithm) proposed by NIST (National Institute of Standards and Technology). Cryptography, including symmetric algorithms, public key algorithms, and digital signatures, are described in "Applied Cryptography" by Bruce Schneier, Chapters 1, 2, 19, and 20, whose contents are incorporated herein by reference. There is.
In another embodiment, the inspection can be performed by some form of password verification.
If the inspection in step 206 indicates that the received data is allowed to be stored in tag 102, the process proceeds to step 208. At step 208, the data is stored in tag 102. After step 208, processing proceeds to step 202, where tag 102 waits for new data to be received. If the inspection in step 206 indicates that the received data is not allowed to be stored in tag 102, processing returns to step 202.
FIG. 3 is a data flow diagram 300 showing the transmission of data from the tag 102. At step 302, a check is performed to determine if the tag 102 should transmit the data without request, and if so, what type of data the tag 102 should transmit. This can be done by examining the control settings within tag 102. If the inspection in step 302 indicates that the tag 102 should transmit data, the process proceeds to step 304. At step 304, a check is performed to determine if data should be transmitted at that time. This check can be done by comparing the clock in tag 102 with a given time setting. If the inspection in step 304 indicates that the data should be transmitted, the process proceeds to step 308. If not, the process remains at step 304. At step 308, data is transmitted from tag 102. After step 308, processing returns to step 302.
At step 310, tag 102 waits for a request for data. Processing remains in step 310 until such a request is received, after which it proceeds to step 312. In step 312, tag 102 is capable of receiving a request, which includes, but is not limited to, client 106, server 108, database 110, sensor 104, another tag 102, and more. It can be sent from any type of component. At step 312, a check can be performed to determine if the received request is allowed to receive a response at tag 102. Step 312 can include checking whether the source of the request is authorized to receive the requested type of data. The inspection can be performed by a variety of different techniques, including techniques that use cryptography, as described in detail in the previous section. The inspection may be performed by some form of password verification as an alternative. If the inspection in step 312 indicates that the request is allowed to receive data in response, the process proceeds to step 314. At step 314, the requested data is sent to the source of the request. After step 314, processing proceeds to step 310, where tag 102 waits for the receipt of a new request. If the inspection in step 312 indicates that the request is not allowed to receive data in response, processing returns to step 310.
In one embodiment, communication between one or more of tags 102 and one or more of sensors 104 and server software 109 can be performed using WAP (Wireless Application Protocol). , WAP is described in ColdFusion 5, Chapter 34, whose content is incorporated by reference.
The present invention can have many different uses. For example, the present invention can be used by parents to monitor the activity of their children. The parent can associate the tag 102 with the child by any means, such as by physically attaching or embedding the tag 102 to the child. From browser software 108, or elsewhere, parents send control data to their child's tag 102, another tag 102 associated with a particular person, GPS (Global) that reveals the child's location throughout the day. Positioning To indicate that the tag 102 should receive data from a sensor 104 such as a System) satellite, or an environmental sensor 104 that reveals the content (ie, toxin) of air or water around the child. it can. The tag 102 attached to the child performs a process for storing data within the tag 102, as shown by the flow diagram of FIG. 2, in order to analyze and store the control information transmitted by the parent. At a later point, parents could send one or more queries from browser software 108, or elsewhere, to identify the people who came into contact with the child and from a teacher that the child might have received that day. You can get the score or notification of the test, the quality of the air or water around the child, and the movement of the child. The tag 102 associated with the child performs the process for sending data from the child tag 102, as shown by the flow diagram in Figure 3, in order to respond to the parent's query.
As another example, the child's tag sends additional control data from the browser software 108, or elsewhere, to the child's tag 102, and the data from tag 102 to database 110 on a regular basis. May be ordered to. At any time later, the parent can submit one or more queries to database 110 from browser software 108, or elsewhere, to find out the same information about the child.
FIG. 4a shows a sample entry form 400 that is completed by the parent in browser software 108, or elsewhere, to control the behavior of the child's tag 102. This form may include one or more of the following fields: That is, Authorized Components For Receipt Table 402, this field specifies the components (ie, tags, sensors, etc.) from which a child's tag can receive data from that component.
Authorized Data For Receipt Table 404, this field contains the types of data that the child's tag 102 can receive (ie, data that identifies people associated with the child's contact tag 102, exam scores, teacher notifications, etc. Specify environment data, location data, etc.).
Authorized Components For Transmission Table 406, this field specifies the components (ie, database 110, etc.) to which the child tag can transmit data.
Authorized Data For Transmission 408, this field specifies the type of data that the child tag 102 can transmit.
FIG. 4b shows a sample fill-in form 450 that is filled in by the parent in browser software 108, or elsewhere, and the data is retrieved from the child's tag 102 or from the database 110. This form may include one or more of the following fields: That is, Identification Query 452, this field requests identification of tagged objects, such as people and animals that come into contact with children.
Environmental Query 454, this field requests the content of water and air that the child has come into contact with.
Performance Query 456, this field requests data on a child's behavior, academic performance, and athletic performance.
The present invention can be used to identify objects such as expensive items, sports souvenirs, and evidence. The seller can associate the tag 102 with an expensive item, such as a diamond or painting, by any means, such as by physically attaching or embedding the tag 102 to the item. From browser software 108, or elsewhere, the seller sends control data to the object's tag 102 to identify the other tag 102, which identifies people associated with the other tag 102, revealing the location of the object throughout the day. GPS (Global Positioning) System) It can indicate that the tag 102 should accept data from a sensor 104 such as a satellite, or an environmental sensor 104 that reveals air or water inclusions (ie, toxins) around an object. Tag 102 on the object performs a process for storing data within tag 102, as shown by the flow diagram of FIG. 2, in order to analyze and store the control information sent by the seller. At a later point, the seller sends one or more queries from the browser software 108, or elsewhere, to identify the people who handled the object, the quality of the air and water around the object, the movement of the object, You can find out the chain of titles, the chain of ownership, and the identities of the manufacturers, retailers, and distributors of objects. The tag 102 associated with the object performs the process for sending data from the object's tag 102, as shown by the flow diagram in FIG. 3, in order to respond to the seller's query.
In another example, the object's tag is such that the browser software 108, or elsewhere, sends additional control data to the object's tag 102 and periodically sends data from the tag 102 to the database 110. You may order 102. At any time later, the seller can send one or more queries to database 110 from browser software 108, or elsewhere, to find out information about the object.
Another embodiment of the invention performs neighborhood tracking. In that embodiment, when a tag falls within the scope of another tag, an event can be recorded within the tag. Those recorded events can later be sent to the database. This embodiment can be commonly used to track an object that has entered the vicinity of another object. For example, this embodiment can be used to track people who have come into contact with or have entered the place where the child was. This embodiment can also be used to track the movement of objects relative to their location within a secure facility.
In one embodiment, the tag can include one or more of the following: That is, wireless transmitters, wireless receivers, memory, control software, processors, and clocks. The memory can include RAM and ROM. The control software can be stored in ROM. The processor can be of the type that consumes less power.
The tag can include one or more data structures, including a tag identifier, a tag identifier map, and a time field. The tag identifier can be a variable length string of up to 255 bytes and can be used to distinguish tags from each other. Tag identifier maps can map tag identifiers to public keys and counters. In one embodiment, the tag identifier map is implemented using a hash table. In another embodiment, the tag identifier is implemented using a binary search tree. The tag identifier map can be initialized using the public key of some tags, such as tags that are expected to be encountered and / or tags that are determined to be sensitive. Is. This scheme allows the tag to quickly discard messages from tags with invalid signatures. Entries in the tag identifier map can be discarded after the map is full. The entries are FIFO (first in, first out), LRU (least recently used). It can be destroyed in any order, such as used)), etc. The time field can be a 4-byte unsigned integer and can contain the current time in any form, such as GMT (Greenwich Mean Time).
FIG. 5 is a data flow diagram 500 showing the operation of one embodiment of the tag related to the neighborhood inspection. The tag waits for an interrupt in step 502. At step 504, the type of interrupt is determined. If the interrupt is a received interrupt, the process proceeds to step 506. In step 506, the protocol identifier of the received broadcast is identified. The protocol identifier can be of a different type, such as tag identifier broadcast, tag identifier map broadcast, and so on. Illustrative formats for tag identifier broadcasts, central authority broadcasts, and tag identifier map broadcasts are shown in Figures 6a, 6b, and 6c, respectively. Broadcasts can be encapsulated in radio broadcast packets at the network interface layer, with multi-byte values being big endian. It can be sent in endian) order. The signature can be an RSA signature. The signature in the tag identifier broadcast can be taken across the tag identifier and the current time field. The signature in the central authority broadcast can be taken over the current time field. Tag Identifier One or more of the fields in the map broadcast, excluding the protocol identifier, can be encrypted using a public key with central privileges. The signature on the tag identifier can be taken over one or more of the fields that follow the current time.
If the protocol identifier is the tag identifier broadcast, the process proceeds to step 508. At step 508, the tag identifier of the tag identifier broadcast is checked to determine if the identifier is valid. If the identifier is not valid, the broadcast is ignored and processing returns to step 502. If the identifier is valid, the process proceeds to step 510. At step 510, the time in the tag identifier broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 502. If it is within 1 minute, the process proceeds to step 512. In step 512, the tag identifier in the tag identifier broadcast is checked to determine if the identifier is present in the tag identifier map (ie, the tag is still encountered). If it does not exist, the process proceeds to step 514. At step 514, a new entry for that tag identifier is created in the tag identifier map, and the number of encounters for that entry is set to 1. Next, the process proceeds to step 502.
If it is determined in step 512 that the tag identifier exists in the tag identifier map, the process proceeds to step 516. At step 516, it is determined whether the tag identifier in the tag identifier broadcast has a public key. If it has a public key, the process proceeds to step 518. At step 518, the public key is used to verify the signature. If the signature verification in step 518 is unsuccessful, the broadcast is ignored and processing returns to step 502. If the signature verification in step 518 is successful, the process proceeds to step 520. At step 520, the number of encounters with that tag identifier is incremented in the tag identifier map.
If the protocol identifier is determined to be a central authority broadcast in step 506, the process proceeds to step 522. At step 522, the time in the central authority broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 502. If within 1 minute, the process proceeds to step 524. At step 524, the central authority public key is used to verify the signature in the central authority broadcast. If the signature verification is unsuccessful, the broadcast is ignored and processing returns to step 502. If the signature verification in step 524 is successful, the process proceeds to step 526. At step 526, the tag identifier map is encrypted using the central authority public key. At step 528, the encrypted tag identifier map is broadcast. The process then returns to step 502.
If it is determined in step 504 that the interrupt is a timer interrupt, the process proceeds to step 530. In one embodiment, timer interrupts occur every 15 seconds. At step 530, the signature is created using the tag's private key. At step 532, the signature, tag identifier, and current time are written to the tag identifier broadcast. At step 534, the tag identifier broadcast is broadcast. The process then returns to step 502.
The embodiment of FIG. 5 has several advantages. The signature makes it impossible to forge a real tag with a pre-registered tag. Repeated attacks are blocked by a time stamp.
The private key can be secure, the central authority can be in a secure location, and the tag can be tamper-resistant. is there. These options prevent one tag from denying contact with another. Replacement measures can be used to prevent attempts to flood the tag identifier map by broadcasting false tag identifiers. In another embodiment, the broadcast may be validated using a global public / private key pair.
Another embodiment of the invention sounds an alarm within a predetermined time if the tag goes outside the specific range of one or more other tags. In one embodiment, the range is a mutual transmission / reception range. In one embodiment, the predetermined time is 60 seconds. One tag can be physically attached to a sensitive object that must not leave the secure area. The other tag may be embedded in a secure, immobile location such as the floor or ceiling, or may be carried by authorized personnel. In one embodiment, the protocol enables (enables) and disables (disables) tags so that an object can be removed by an authorized party.
Use this embodiment to alert security staff about the movement of objects out of a secure facility, alert employees about theft of inventory from a warehouse, or a child who gets lost outside an area. In a secure facility for alerting parents or day-care providers, alerting individuals about the theft of motorcycles or theft of expensive objects from home, abandonment by guests You can alert your attendants, the escape of criminals from prison, or the escape of homes for criminals who are in custody at home.
In one embodiment, the tag can include one or more of the following: That is, wireless transmitters, wireless receivers, memory, control software, processors, clocks, and audible alarms. The memory can include RAM and ROM. The control software can be stored in ROM. The processor can be of the type that consumes less power.
The tag contains one or more data structures, including a tag identifier, a partner tag tag identifier, a private key for the tag, a public key for the partner tag, a public key for control privileges, an alarm counter, an enable flag, and a time field. It is possible. The tag identifier can be a variable length string of up to 255 bytes and can be used to distinguish tags from each other. The tag identifier of the partner tag can be a variable length character string of up to 255 bytes. The private and public keys can be 16 bytes. The alarm counter can be 4 bytes. The enable flag can be 4 bytes. The time field can be a 4-byte unsigned integer and can contain the current time in any form, such as GMT (Greenwich Mean Time).
FIG. 7 is a data flow diagram 700 showing the operation of one embodiment of the tag related to the out-of-range alarm. The tag waits for an interrupt in step 702. At step 704, the type of interrupt is identified. If the interrupt was a received interrupt, processing proceeds to step 706. At step 706, the protocol identifier of the received broadcast is identified. The protocol identifier can be of a different type, such as tag identifier broadcast, control privilege broadcast (including control privilege enable and control privilege disable), and so on. Illustrative formats for tag identifier broadcast, control privilege enable, and control privilege disable are shown in Figures 8a, 8b, and 8c, respectively. Broadcasts can be encapsulated in radio broadcast packets at the network interface layer, and multibyte values can be transmitted in big endian order. The signature in the tag identifier broadcast can be taken across the tag identifier and the current time field. The signature in the control broadcast can be taken over the current time field. The signature can be an RSA signature.
If the protocol identifier is the tag identifier broadcast, the process proceeds to step 708. At step 708, the tag identifier of the tag identifier broadcast is checked to determine if the identifier is valid. If the identifier is not valid, the broadcast is ignored and processing returns to step 702. If so, the process proceeds to step 710. At step 710, the time in the tag identifier broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 702. If within 1 minute, the process proceeds to step 712. At step 712, the public key of the partner tag can be used to verify the signature in the tag identifier broadcast. If the signature verification in step 712 is unsuccessful, the broadcast is ignored and processing returns to step 702. If the signature verification in step 712 is successful, the process proceeds to step 714. At step 714, the alarm counter is reset to 0.
If the protocol identifier is determined to be a control privilege enable broadcast in step 706, the process proceeds to step 716. At step 716, the time in the control privilege enable broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 702. If within 1 minute, the process proceeds to step 718. At step 718, the public key of the control privilege is used to verify the signature in the control privilege enable broadcast. If the signature verification is unsuccessful, the broadcast is ignored and processing returns to step 702. If the signature verification in step 718 is successful, the process proceeds to step 720. At step 720, the enable flag is set to 1. The process then returns to step 702.
If the protocol identifier is determined to be a control privilege disabled broadcast in step 706, the process proceeds to step 722. At step 722, the time in the control privilege disabled broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 702. If within 1 minute, the process proceeds to step 724. At step 724, the public key of the control privilege is used to verify the signature in the control privilege enable broadcast. If the signature verification is unsuccessful, the broadcast is ignored and processing returns to step 702. If the signature verification in step 724 is successful, the process proceeds to step 726. At step 726, the enable flag is set to 0. The process then returns to step 702.
If the interrupt is determined to be a timer interrupt in step 704, the process proceeds to step 728. In one embodiment, the timer interrupt occurs every 6 seconds. At step 728, the enable flag is added to the alarm counter. At step 730, the alarm counter is inspected to determine if the counter is over the limit. In one embodiment, the limit can be 10 seconds. If the alarm counter exceeds the limit, the process proceeds to step 732. At step 732, the tag sounds an alarm. The process then proceeds to step 702.
If it is determined in step 730 that the alarm counter is below the limit, the process proceeds to step 734. At step 734, the signature is created using the tag's private key. In one embodiment, the signature is taken over the tag identifier of the partner and the current time. At step 736, the signature, protocol identifier, partner tag identifier, and current time are written to the tag identifier broadcast. At step 738, the tag identifier broadcast is broadcast. The process then returns to step 702.
The embodiment of FIG. 7 has many advantages. The signature makes it impossible to alter a real tag with a fake partner tag. The signature also makes it impossible for fake controls to invalidate the tag. Repeated attacks are blocked by a time stamp. By destroying the tag, the alarm of the partner tag is sounded.
Another embodiment of the invention sounds an alarm when a tag falls within a particular range of one or more other tags. Each tag can hold a sensitive tag list of such other tags that causes the alarm for that tag to sound. In one embodiment, the range is a mutual transmission / reception range. One tag can be physically attached to a sensitive object that must not enter a secure area. The other tag may be incorporated in a secure, immobile location such as the floor or ceiling, or may be carried by authorized staff. This embodiment can include protocols for adding tags to and removing tags from the sensitive tag list.
Use this embodiment to alert security staff about the movement of objects such as dangerous or harmful objects into sensitive facilities, and to employees about inventory being carried near the exit of the warehouse. Alerting, alerting parents or childcare providers about a child's movement towards a dangerous area or designated person, alerting pedestrians approaching a hazardous area, to a hazardous condition It can alert motorcycle drivers approaching, alert security staff about visitors entering or approaching restricted areas, and more.
In one embodiment, the tag can include one or more of the following: That is, wireless transmitters, wireless receivers, memory, control software, processors, clocks, and audible alarms. The memory can include RAM and ROM. The control software can be stored in ROM. The processor can be of the type that consumes less power.
The tag can include one or more data structures, including a tag identifier, a private key for the tag, a public key for control, a tag identifier map, and a time field. The tag identifier can be a variable length string of up to 255 bytes and can be used to distinguish tags from each other. The private and public keys can be 16 bytes. The tag identifier map can map sensitive tag identifiers to public keys. The tag identifier map can be implemented by a hash table or a binary search tree. Entries in the tag identifier map can expire in the least-recently used order when the tag identifier map is full. The time field can be a 4-byte unsigned integer and can contain the current time in any form, such as GMT (Greenwich Mean Time).
FIG. 9 is a data flow diagram 900 showing the operation of one embodiment of the tag relating to the symmetric neighborhood alarm. The tag waits for an interrupt in step 902. At step 904, the type of interrupt is identified. If the interrupt was a received interrupt, processing proceeds to step 906. At step 906, the protocol identifier of the received broadcast is identified. The protocol identifier can be of a different type, such as tag identifier broadcast, control privilege addition tag broadcast, control privilege removal tag broadcast, and so on. Illustrative formats for tag identifier broadcasts, control privilege addition tag broadcasts, and control privilege removal tag broadcasts are shown in Figures 10a, 10b, and 10c, respectively. Broadcasts can be encapsulated in radio broadcast packets at the network interface layer, and multibyte values can be transmitted in big endian order. The signature can be an RSA signature. The signature in the tag identifier broadcast can be taken across the tag identifier and the current time field. The signature in the additional control tag broadcast can be taken across the target tag identifier, the sensitive tag identifier, the sensitive tag public key, and the current time field. The signature in the control removal tag broadcast can be taken across the target tag identifier, the sensitive tag identifier, and the current time field.
If the protocol identifier is the tag identifier broadcast, the process proceeds to step 908. At step 908, the tag identifier of the tag identifier broadcast is checked to determine if the identifier is in the tag's sensitive tag list. If the identifier is not in the sensitive tag list, the broadcast is ignored and processing returns to step 902. If the identifier is in the sensitive tag list, the process proceeds to step 910. At step 910, the time in the tag identifier broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 902. If within 1 minute, the process proceeds to step 912. At step 912, the signature in the tag identifier broadcast can be verified using the public key of the tag identifier in the tag identifier broadcast. If the signature verification in step 912 is unsuccessful, the broadcast is ignored and processing returns to step 902. If the signature verification in step 912 is successful, the process proceeds to step 914. At step 914, the alarm sounds.
If it is determined in step 906 that the protocol identifier is a control authority addition tag broadcast, the process proceeds to step 916. At step 916, the target tag identifier is checked to determine if the signal matches the tag identifier of the tag receiving the broadcast. If no match exists, the broadcast is ignored and processing returns to step 902. If a match exists, the process proceeds to step 918. At step 918, the time in the additional control tag broadcast is checked to determine if the time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 902. If within 1 minute, the process proceeds to step 920. At step 920, the public key of the control authority is used to verify the signature in the additional control authority tag broadcast. If the signature verification is unsuccessful, the broadcast is ignored and processing returns to step 902. If the signature verification in step 920 is successful, the process proceeds to step 922. At step 922, the sensitive tag identifier in the additional control tag broadcast and the public key for that identifier are stored in the tag identifier map. The process then returns to step 902.
If it is determined in step 906 that the protocol identifier is a control authority removal tag broadcast, the process proceeds to step 924. At step 924, the target tag identifier is checked to determine if it matches the tag identifier of the tag that receives the broadcast. If no match exists, the broadcast is ignored and processing returns to step 902. If a match exists, the process proceeds to step 926. At step 926, the time in the control delete tag broadcast is checked to determine if that time is within one minute of the current time. If not within 1 minute, the broadcast is ignored and processing returns to step 902. If within 1 minute, the process proceeds to step 928. At step 928, the public key of the control authority is used to verify the signature in the control authority removal tag broadcast. If the signature verification is unsuccessful, the broadcast is ignored and processing returns to step 902. If the signature verification in step 928 is successful, the process proceeds to step 930. At step 930, the sensitive tag identifier in the control permission removal tag broadcast and the public key of that identifier are removed from the tag identifier map. The process then returns to step 902.
If the interrupt is determined to be a timer interrupt in step 904, the process proceeds to step 932. In one embodiment, timer interrupts occur every 15 seconds. At step 932, the signature is created using the tag's private key. In one embodiment, the signature is taken over the tag identifier and the current time. At step 934, the signature, protocol identifier, tag identifier, and current time are written to the tag identifier broadcast. At step 936, the tag identifier broadcast is broadcast. The process then returns to step 902.
The embodiment of FIG. 9 has many advantages. Signing makes it impossible to alter a real tag with a fake sensitive tag. The signature also makes it impossible for fake controls to add or remove tags. Repeated attacks are blocked by a time stamp. The tag can be made tamper-proof to reduce the tag's vulnerability to physical destruction or removal.
Although the above invention has been described in relation to some preferred embodiments, the scope of the present invention is not limited to those embodiments. One of ordinary skill in the art can find variants of those preferred embodiments, also within the spirit of the invention, whose scope is defined by the appended claims.
<figref num="1">It is a block diagram which shows the main operation element of this invention.</figref><figref num="2">It is a data flow diagram which shows the storage of data in the tag 102 associated with an object of any kind.</figref><figref num="3">It is a data flow diagram which shows the transmission of data from a tag 102.</figref><figref num="4">FIG. 4a is a diagram showing a sample entry form 400 completed by the parent on the client computer 106 to control the behavior of the child tag 102. FIG. 4b shows a sample entry form 450 that is completed by the parent on the client computer 106 and the data is retrieved from the child tag 102 or from the database 110.</figref><figref num="5">FIG. 500 is a data flow diagram 500 showing the operation of one embodiment of the tag related to the neighborhood inspection.</figref><figref num="6">6a, 6b, and 6c are diagrams showing exemplary formats for tag identifier broadcasts, central authority broadcasts, and tag identifier map broadcasts, respectively.</figref><figref num="7">It is a data flow diagram which shows the operation of one Embodiment of the tag concerning the alarm outside the neighborhood range.</figref><figref num="8">8a, 8b, and 8c are diagrams showing exemplary formats for tag identifier broadcast, control privilege enable, and control privilege disable, respectively.</figref><figref num="9">It is a data flow diagram which shows the operation of one Embodiment of the tag concerning a symmetric neighborhood alarm.</figref><figref num="10">10a, 10b, and 10c are diagrams showing exemplary formats of tag identifier broadcast, control privilege addition tag broadcast, and control privilege removal tag broadcast, respectively.</figref>
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2003296415A | Cites | Japan |
| JP2000163527A | Cites | Japan |
| JP2003283391A | Cites | Japan |
| JP2003157457A | Cites | Japan |
| JP2002261969A | Cites | Japan |
| JP2002536726A | Cites | Japan |
| JP2003212348A | Cites | Japan |
| WO2003005295A1 | Cites | World Intellectual Property Organization (WIPO) |
| US20020070865A1 | Cites | United States of America |
| JP2003296667A | Cites | Japan |
65 members in 15 offices
Priority claims14
| Document | Office | Kind | Date |
|---|---|---|---|
| 51544903 | United States of America | P | |
| 51544903 | United States of America | P | |
| 60515449 | United States of America | – | |
| 10952789 | United States of America | – | |
| 95278904 | United States of America | A | |
| 95278904 | United States of America | A | |
| 2004035932 | United States of America | W | |
| 2004035932 | United States of America | W | |
| 2003515449 | – | – | – |
| 2004952789 | – | – | – |
| 2004035932 | – | – | – |
| US20030515449P | – | – | – |
| US20040952789 | – | – | – |
| WO2004US35932 | – | – | – |
Members65
| Document | Office | Kind | |
|---|---|---|---|
| US2005092823A1 | United States of America | A1 | |
| AU2004287169A1 | Australia | A1 | |
| CA2544217A1 | Canada | A1 | |
| WO2005045631A2 | World Intellectual Property Organization (WIPO) | A2 | |
| EP1690167A2 | European Patent Office (EPO) | A2 | |
| WO2005045631A3 | World Intellectual Property Organization (WIPO) | A3 | |
| BRPI0415994A | Brazil | A | |
| CN1906644A | China | A | |
| KR20070032265A | Republic of Korea | A | |
| JP2007515702A | Japan | A | |
| HK1098862A1 | Hong Kong, China | A1 | |
| ZA200603722B | South Africa | B | |
| US2007273518A1 | United States of America | A1 | |
| RU2006118688A | Russian Federation | A | |
| US7388488B2 | United States of America | B2 | |
| WO2008091576A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2008091576A3 | World Intellectual Property Organization (WIPO) | A3 | |
| US2008224857A1 | United States of America | A1 | |
| EP1690167A4 | European Patent Office (EPO) | A4 | |
| AU2004287169B2 | Australia | B2 | |
| RU2399948C2 | Russian Federation | C2 | |
| EP1690167B1 | European Patent Office (EPO) | B1 | |
| ATE502364T1 | Austria | T1 | |
| DE602004031866D1 | Germany | D1 | |
| JP2011100483A | Japan | A | |
| US7956742B2 | United States of America | B2 | |
| US2011279262A1 | United States of America | A1 | |
| CN1906644B | China | B | |
| US2012030241A1 | United States of America | A1 | |
| JP4875986B2This record | Japan | B2 | |
| KR101135221B1 | Republic of Korea | B1 | |
| US8314705B2 | United States of America | B2 | |
| US2012322428A1 | United States of America | A1 | |
| CA2544217C | Canada | C | |
| US2013103679A1 | United States of America | A1 | |
| IL175333A | Israel | A | |
| US8558668B2 | United States of America | B2 | |
| US2014040260A1 | United States of America | A1 | |
| JP5538206B2 | Japan | B2 | |
| US8952814B2 | United States of America | B2 | |
| US2015112784A1 | United States of America | A1 | |
| US2015169917A1 | United States of America | A1 | |
| US9177325B2 | United States of America | B2 | |
| US9218520B2 | United States of America | B2 | |
| US2016042379A1 | United States of America | A1 | |
| US2016110366A1 | United States of America | A1 | |
| US9460233B2 | United States of America | B2 | |
| US9460446B2 | United States of America | B2 | |
| US2017017818A1 | United States of America | A1 | |
| US2017018003A1 | United States of America | A1 | |
| IL208883A | Israel | A | |
| US9785810B2 | United States of America | B2 | |
| US9792624B2 | United States of America | B2 | |
| US9817870B2 | United States of America | B2 | |
| US2018032771A1 | United States of America | A1 | |
| US2018040022A1 | United States of America | A1 | |
| US2018067949A1 | United States of America | A1 | |
| BRPI0415994B1 | Brazil | B1 | |
| US10083460B2 | United States of America | B2 | |
| US10331920B2 | United States of America | B2 | |
| US10459930B2 | United States of America | B2 | |
| US2020073873A1 | United States of America | A1 | |
| US11100118B2 | United States of America | B2 | |
| US2021382906A1 | United States of America | A1 | |
| US2023325394A1 | United States of America | A1 |
27 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Renewal fee payment (event date is renewal date of database)FPAY | FPAY | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 4875986
- Publication, DOCDB
- 4875986
- Publication, EPODOC
- JP4875986B
- Application
- 2006538288
- Application, DOCDB
- 2006538288
- Application, EPODOC
- JP20060538288
Titles2
- Japanese
- タグに関するデータを格納し、取得し、および管理するための方法およびシステム
- English
- Methods and systems for storing, retrieving, and managing data about tags
Classification
- CPC, 9
- G06Q10/08
- G06F17/00
- G06K7/10366
- G08B13/2462
- G08B21/22
- G06F16/90
- G06F16/903
- G06F17/40
- G06K7/10257
- IPC, 5
- G06K17 00
- B65G61 00
- G06F
- G06F17 00
- G06Q10 00