MXPA06004775A - A method and system for storing, retrieving, and managing data for tags - Google Patents

Abstract

This invention relates generally to a method and system forstoring, retrieving, and managing data for tags that are associated in some manner to any type of object. More particularly, the present invention writes data to these tags, reads data from these tags, and manages data that is written to and/or read from these tags.

Description

METHOD AND SYSTEM FOR STORING, RECOVERING AND HANDLING DATA FOR LABELS FIELD OF THE INVENTION This invention relates, in general, to a method and system for storing, retrieving and handling data for labels that are associated in some way with any type of object. More particularly, the present invention writes data to these labels, reads data from labels, and handles data that. are written in, and / or read data from, these labels.

BACKGROUND This invention consists of a method and system for storing, retrieving and handling data for any type of label or identifier that is associated in any way with any type of object, physical or abstract, animate or inanimate. A label is any device that sends, receives and / or stores data about anything that it is monitoring or associated with; It includes many different types, such as radio frequency identification device (RFID) tags, laser tags, cell phones, receiving devices and transmit signals from television networks, any type of satellite communication network, such as the Global Positioning System (GPS), et. A label can be powered by any type of power source, such as a DC power source, AC power source, solar power, etc. Identification devices are further described in US Patent No. 3,752,960 to Charles Walton, entitled, Electronic Identification and Recognition System "the content of which is incorporated herein by reference." The types of objects that may be associated with the labels they can be, but are not limited to, people, animals, plants, things of any kind, real properties such as houses, land, condominiums, mobile homes, unifamily homes, valuables such as paintings, diamonds, jewelry, watches and antiques, articles mobiles such as automobiles, airplanes, military vehicles, bicycles, motorcycles, boats, boats, components of these, locations, environmental conditions, abstractions, concepts, phenomena, etc. The associations between labels and objects can be of any type including, but not limited to a, one to many, many to one or one to one, physical, logical, etc. Physical associations can consist of Click on adding and / or inserting the tag to its associated objects.

The present invention is adapted to a wide variety of uses. For example, the method and system of the present invention can be used to authenticate valuable items, to manage inventories, such as tracking objects of any kind during manufacturing, supply chain, distribution, etc., to the point of sale and more. there, to track the movements of objects such as people, animals, plants, mobile items, etc., to retrieve historical data, such as the price history of things such as valuable items and real properties, to recover any type of health data , such as medical conditions, treatment history, medication instructions, etc., of people and animals, to track any type of health conditions, such as heart rate, pulse rate, temperature, the amount of different things in the blood like oxygen, sugar, etc., for people and animals.

Many different benefits may arise from the various uses of the present invention. For example, its use can lower costs to determine the value of a thing as a valuable item, because, for example, price history and other similar data for the item, it can be easily stored and recover from its associated label. The availability of the price history of a label associated with a house, as well as other houses in the same neighborhood, can prevent the seller from charging an excessively high value to a buyer with little or no knowledge of the current value of the house. The use of the present invention can prevent the fraudulent substitution of a counterfeit for an article of value because the identification data of the label associated with the article can be used to verify the authenticity of the article. The use of the present invention can prevent a vehicle owner from passing a damaged car as one without damage to a confident buyer, because the accident history of the vehicle can be stored and retrieved from the label associated with the vehicle. The use of the present invention can prevent the theft of military secrets because the authorized information can be easily accessed from the label associated with a person to determine whether the person should have access to said secrets. The use of the present invention can prevent injury or even death to athletes, which can occur while performing some exercise due to their heart rate, temperature, and other medical conditions that can be easily monitored.

For similar reasons, a coach can use the present invention to quickly determine which players are too fatigued to be effective; An athletic recruiter can use the present invention to determine which players are better able to carry out competition rigors; and athletic trainers can use the present invention to adapt training programs to individual athletes. The use of the present invention can facilitate the authentication of evidence in the evidence because the chain of custody can be easily retrieved from the labels associated with the evidence.

Labels and similar devices have been described in other references, but no prior art reference describes the use of such labels in a system and method for storing, retrieving and handling data for a variety of applications including authentication, tracking, monitoring of health care, health care management, knowledge acquisition, etc. On the contrary, for example, US Patents No. 6,440,096, 5,358,514, ,193,540, 6,107,102 and 6,405,066 describe the implantation of microdevices in people. U.S. Patent Nos. 5,606,260, 4,892,709, ,367,878, 6,152,181, 5,834,790, 5,186,001, 5,839,056 and 5,144,298 describe the use of microdevices as sensors or controllers.

Accordingly, there is a need for a system and method for storing, retrieving and handling data for any type of label associated in any way to any type of object.

COMPENDIUM OF THE INVENTION The invention provides a system and method for storing, retrieving and handling data for any type of label associated in any type of way to any type of object for a variety of applications.

In particular, an aspect of the present invention is to present a system for storing, retrieving and handling data for one or more objects, comprising: one or more tags associated with one or more objects; one or more components communicating with at least one of said labels; at least one receiver to receive control data and information data from at least one of the components in at least one of the labels, in where the information data is about the object associated with at least one tag; 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; and at least one communication network to facilitate communication between the components and the labels; wherein at least one of the components transmits at least one query to receive at least a portion of the information data about the object associated with at least one tag.

It is also another aspect of the present invention to present a method for storing, retrieving and handling data of one or more objects comprising the steps of: associating one or more tags with one or more objects; communicate with at least one of the labels from one or more components; receiving control data and information data from at least one of the components within at least one of the tags, wherein the information data is about the object that is associated with at least one tag; transmitting at least a portion of the information data from at least one label to at least one of the components according to the control data; and transmitting from at least one of the components at least one query to receive at least a portion of the information data about the object associated with at least one tag.

It is also another aspect of the present invention to present a method for managing a child, comprising the steps of: associating one or more labels with one or more children; transmit control data and information data to one or more labels; receiving the information data within one or more labels, the information data is about one or more of the following: the identification of the people who come into contact with one or more children; at least one measure of an environmental condition to which one or more children were exposed; the academic performance of one or more children, the athletic performance of one or more children, at least one measurement of medical conditions of one or more children; Y transmitting at least a portion of the information data from at least one tag according to the control data.

BRIEF DESCRIPTION OF THE DRAWINGS These and other aspects and features of the invention will be understood more clearly from the following detailed description, together with the accompanying drawings and drawings, wherein: Figure 1 is a block diagram showing the main operating elements of the invention.

Figure 2 is a flow chart describing the storage of data to labels 102 that are associated with any type of object.

Figure 3 is a flow chart describing the transmission of data from labels 102.

Figure 4a shows a fill sample from 400 completed by a parent on a client computer 106 to control the operation of the child's label 102.

Figure 4b shows a fill example from 450 completed by a parent on a client computer 106 to retrieve data from the child's label 102 or from a database 110.

Figure 5 is a data flow diagram 500 illustrating the operation of a modality of a tag for proximity verification.

Figures 6a, 6b and 6c show examples of formats of the issuance of the label identifier, the issuance of the central authority and the issuance of the identifier map of the label, respectively.

Figure 7 is a data flow diagram showing the operation of a modality of a label for an out-of-proximity alarm.

Figures 8a, 8b and 8c show exemplary formats of the issuance of the label identifier, the enabling of the control authority and the deactivation of the control authority, respectively.

Figure 9 is a data flow diagram illustrating the operation of a modality of a label for a symmetric proximity alarm.

Figures 10a, 10b and 10c show exemplary formats of the issuance of the label identifier, the issuance of the label that adds the control authority and the issuance of. the label that deletes the control authority, respectively.

DETAILED DESCRIPTION OF THE PREFERRED MODALITY The invention provides a system and method for storing, retrieving and handling data for any type of label associated in any way with any type of object (physical or abstract, animate or inanimate) for a variety of applications.

While the present invention will be explained within the context of various different applications such as the authentication of objects including valuable items and evidence, and the monitoring of children by their parents, the present invention can be applied to any application that benefits from storage, data recovery and handling for labels associated with any type of object. These applications include the change of objects such as real property, goods and services, monitoring of vital signs of the sick, elderly and athletes, athletic training programs, monitoring of environmental conditions, traffic and consumer behavior in various scenarios such as amusement parks, shopping centers , casinos, tracking the location of people, such as prisoners, students, foreigners, military personnel and workers in classified areas, tracking the location of goods of any kind, such as inventory for manufacturing, the supply chain, distribution, etc., to the point of sale and beyond, the tracking of the location of classified material, tracking of manufacturing history, sale and repair of goods, such as machinery, automobiles, airplanes, trains and their components, monitoring of the movement of people and things as vehicles, traffic, etc., in places such as a battlefield, fast track, etc., oil flow monitoring or other Fluids in the pipes, et cetera.

Figure 1 is a block diagram 100 showing the main functional elements of the invention. The invention may include one or more labels 102 that may be associated with objects of any kind such as people, animals, plants, things of any kind,ties such as houses, land, condominiums, mobile homes and unifamily houses, valuables such as paintings, diamonds, jewelry, watches and antiques, vehicles such as automobiles, airplanes, military vehicles, bicycles, motorcycles, boats, component ships, locations, environmental conditions, abstractions, concepts, phenomena, etc. The associations between labels and objects can be of any type including one to many, many to one or one to one. These associations can be physical, logical, etc. Physical associations can include adding and / or inserting the label ao in its associated object. Logical associations can include information in a database such as a table that can map between one or more labels and one or more objects by your identification numbers.

Labels 102 can be one of a variety of different types including Radio Frequency Identification Device (RFID) tags, laser tags, cell phones, devices that receive and transmit signals from a Global Positioning System (GPS) etc. Labels 102 can work by any type of source of energy as a source of CD energy, an AC power source, solar energy, etc. Each tag 102 must have the ability to receive data, store data, detect data and / or transmit data. The data may be received and transmitted to other tags 102, sensors 104, computers 106, and database management systems 110. TAG_102_may have the capability to detect data of its associated object, its environment, etc. The data detected from an associated object such as a person or animal can include medical data such as temperature, oxygen content in the blood, heart rate, etc. The detected environmental data may include the content of various gases, poisons and contaminants in air or water, temperature, humidity, barometric pressure, chemicals, movement, light, sound, and so on.

The present invention 100 may further include sensors 104. Sensors 104 may be of any type can detect any type of data. The sensors 104 can be operated by any type of power source such as an AC power source, CD power source, solar power, etc. Sensors 104 may be thermometers, motion sensors, Global Positioning System devices (GPS, Global Positioning System), chemical sensors, etc. The computers 106 may be database management systems 110 for storing and handling data associated with labels 102 in any form such as data transmitted to, and / or retrieved from, the labels 102. The data may be transmitted to the labels 102 from computers 106 for, storage within labels 102, and can be transmitted from labels 102 to computers 106. Data retrieved from labels 102 can be stored and operated in database management systems 110.

The present invention may further include a communication network 114, which may have a variety of different types of components and software to communicate different types of data between the tags 102 the sensors 104, computers 106, etc. These components and software may include a modulator / demodulator (modems), satellites, up and down frequency converters such as those used for communications with satellites, sound or video encoders, routers, hubs or hubs, bridges, etc. . In one embodiment, the communication network 114 may be a cellular telephone network. In other mode, the communication network 114 may be of 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 may be the Internet. Communication can be achieved on the Internet by one or more of the internet applications, including the World Wide Web (WWW, World Wide Web, in Spanish). The communication network 114 may be an intranet or an extranet. An intranet is a private network with a local area network (LAN) or a wide area network (WAN) that allows the use of Internet-based applications in secure and private environments. Extranet and intranet type networks that link multiple sites or organizations using Intranet related technologies.

The World Wide Web is built on a protocol called Hypertext Transfer Protocol (HTTP, Hypertext Transport Protocol). Computers 106 may include a software or browser program 108 for requesting data output by tags 104 and sensors 102, and / or data stored in a database management system 110. Requests for data from browser software 108 may managed by server software 109. Server software 109 can locate the requested data and can transmit them to the requesting browser software 108. The computers 106 may further include an application server software 111, which may extend the capabilities of the server software 109. In particular, the application server software 111 may pre -Process a data page before sending it to the requesting browser software 108.

In one embodiment, the application server software 11 is a Cold Fusion application. Cold Fusion is a World Wide Web application for creating dynamic web pages and interactive Web sites by combining standard Hypertext Markup Language (HTML) files with Cold Fusion Label Language instructions (CFML, Cold Fusion Markup Language), as specified in "The Kit for Building Web Applications with Macromedia Cold Fusion 5"(The Macromedia Cold Fusion 5 Web Application Construction Kit), by Ben Forta and Nate Welss, Fourth Edition, (hereinafter," Cold Fusion 5"), Chapter 1, the contents of which are incorporated in this As a reference, HTML is a language of page labels that allows the creation and design of pages and forms. invention, a Cold Fusion application defines filling forms for data entry including data to control the operation of labels 102 and sensors 104 and queries for data.

In one embodiment, a Cold Fusion 111 application is used to retrieve and update data in the database management system 110. The Cold Fusion 111 application can access the database administration system 110 through an interface called Open It was Connectivity (ODBC), which is a standard Application Programming Interface (API) for accessing information from different database systems and different formats, as explained in ColdFusion 5, Chapter 6, contents of which are incorporated herein by reference.

In an alternative mode, the data can be entered using a program written in a language that manipulates text, files and information. An example language is PERL as specified in "Programming Perl" (Programming Perl), by Larry Ward and Randal L. Schwartz, O'Reilly & Associates, Inc., March 1992, the contents of which are incorporated herein by reference.

The database 110 can be a distributed database, which can be stored between many computers 106 or can be a central database. The database 110 can be of any type, including a relational database or a hierarchical database. The databases and systems for the administration of databases are described in Database System Concepts, by Henry F. Korth, Abraham Silberschatz, MaGraw-Hill 1986, Chapter 1, the contents of which are incorporated in the present as a reference. Examples of 110 databases include: Microsoft Structured Query Language (SQL) 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 dBase III and dBase IV, and Microsoft Excel 3.0, 4.0 and 5.0.

In one embodiment, the data is retrieved, inserted, updated or deleted from the database 110 using Structured Query Language (SQL). SQL is described in "SAMS Teach Yourself SQL", 2nd edition, by Ben Forta, the contents of which are incorporated herein by reference.

The present invention may include additional components for handling the data received from tags 102, sensors 104 and any other. These additional components may include a search tool. In one modality, the search tool is Verity. The data can be organized within one or more collections. Verity can then be used to catalog the collection and compile metadata about the collection to enable it to search the collection quickly. Conceptually, Verity's utility is attributed to its ability to catalog and compile information about the collection and use this information to quickly search the collection when asked to do so. Searches and queries can be specified using Verity operators including concept operators such as STEM, WORD, and WILDCARD, proximity operators such as NEAR and PHRASE, relationship operators such as CONTAINS, MATCHES, STARTS, ENDS, and SUBSTRING, search modifiers such as CASE, MANY, NOT and ORDER and scoring operators such as YES NO, COMPLEMENT, PRODUCT, and SUM. Search forms and search results pages can be defined using HTML with Cold Fusion tags. The creation and search of collections, and the presentation of search results using Verity is described in ColdFusion 5, Chapter 36, the contents of which are incorporated herein by reference. The browser software of the web 108 can display the web pages from the server software 109 including the filling form for data entry, the filling form for entering search criteria and the text data of the results of the search. The present invention can also display audio and video data entered by tags 102 and sensors 104 using an on-demand video and audio streaming server, such as RealServer as explained in "Real Server AD Administration and Content Creation Guide", the contents of the which are incorporated herein by reference.

In another mode, the search engine can be a commercial search engine such as Alta Vista, Google, Yahoo, etc. A commercial search engine may be integrated within the present invention using Cold Fusion tags as explained in ColfFusion 5, Chapter 36.

Before performing the search, the search engine optimizes queries as specified in Datbase System Concepts, by Henry F. Korth, Abraham Silbarshatz, McGraw-Hill 1986, Chapter 9, the content of which is incorporated herein by reference.

Figure 2 is a flowchart 200 describing the storage of the data to labels 102 that are associated with any type of object. A data flow diagram is a graph whose nodes are processed and whose arcs are data streams. See Object Oriented Modeling and Design, by Rumbaugh, J., Prentice Hall, Inc. (1991) Chapter 1, the content of which is incorporated herein by reference. The data may consist of control data that govern the operation of the tag 102 as the definition of what types of data the tag 102 is to receive and / or transmit, the identification of those components (ie, other tags 102, computers) 106, browser software 108, server software 109, sensors 104, etc.) that can transmit data to, or receive data from, tag 102, and may consist of information for storage within tag 102. In step 202 , the tag 102 can wait for the reception of data. The control proceeds to step 204 where the data is received. In step 204, the tag 102 can receive data, which could be transmitted from any type of components including, but not limited to, a computer 106, browser software 108, server software 109, a database 110, a sensor 104, another label 102, itself, etc. In step 206, an inspection can be made to determine whether the received data is authorized to be stored in the tag 102. Step 206 may include inspecting whether the data source has the authority to store the type of data that was received in the data. the label 102.

Inspection can be done through a variety of different techniques including, but not limited to, those that use cryptography, the art and science of keeping messages secure, and any other type of communication source such as an intranet, a virtual private network (VPN), etc. Cryptography can be used in the present invention for authentication, integrity and / or non-repudiation. Authentication allows the recipient of a message to find out its origin. Integrity allows the recipient of a message to verify that the message has not been modified in the transmission. Non-repudiation prevents the sender of the message from falsely denying that he actually sent the message.

In one modality, a symmetric algorithm is used. With symmetric algorithms, the encryption key can be calculated from the decoding key and vice versa. The key must remain secret to maintain the secrecy of communication. In another modality, a public key algorithm (also called an asymmetric algorithm) is used. With a public key algorithm, the decoding key can not be calculated from the encryption key in a reasonable amount of time. The encryption key is made public and is called the public key. The decoding key is kept secret and is called a private key. In another modality, digital signatures can be used. A sender encrypts a message with a private key, by means of digital signatures, thus signing the message and the recipient decodes it with a public key. Exemplary digital signature algorithms include Rivest-Shamir-Adelman (RSA) and Digital Signature Algorithm (DSA), Digital Signature Algorithm, proposed by the National Institute of Standards and Technology (NIST). Cryptography, including symmetric algorithms, public key algorithms and digital signatures are described in "Applied Cryptography" by Bruce Schneier, Chapters 1, 2, 19 and 20, the contents of which are incorporated herein by reference.

In another mode, verification can be done by some form of password verification.

If the verification step 206 indicates that the received data is authorized to be stored in the tag 102, then the control proceeds to step 208. In step 208, the data is stored in the tag 102. After step 208, the control proceeds to step 202, where the tag 102 waits for the reception of new data. If in step 206 the verification indicates that the received data is not authorized to be stored in the tag 102, then the control returns to step 202.

Figure 3 is a data flow diagram 300 describing the transmission of label data 102. In step 302, a check is made to determine whether the label 102 should transmit data without the request, if so, what type of data should transmit. This should be done by checking the control preferences within the tag 102. If in step 302 the check indicates that the tag 102 should transmit data, the control proceeds to step 304.

In step 304, a check is made to determine if the data should be transmitted at that time. This verification can be done by comparing a clock on the label 102 with a predetermined time setting. If in step 304 the verification indicates that the data should be transmitted, the control proceeds to step 308. Otherwise, the control continues in step 304. In step 308, the data is transmitted from label 102. After step 308, control returns to step 302.

In step 310, the tag 102 waits for a data request. The control remains in step 310 until said request is received after proceeding to step 312. In step 312, the tag 102 may receive the request, which may be transmitted from any type of component that may be, but not limited to. a, a client 106, a server 108, a database 110, a sensor 104, another label 102, etc. At step 312, a check can be made to determine whether or not to approve the received request to receive a response on the tag 102. Step 312 can include verifying whether the source of the request has the authority to receive the data type. that are requested. Verification can be done through a variety of different techniques that include those that use cryptography, as explained in detail above. Verification can be done alternatively through some form of password verification. If the verification in step 312 indicates that the request is authorized to receive data in response, the control proceeds to step 314. In step 314, the requested data is transmitted to the source of the request. After step 314, the control proceeds to step 310, where the tag 102 waits for the receipt of a new request. If the verification in step 312 indicates that the request is not authorized to receive data in response, the control returns to step 310.

In one embodiment, communication between one or more of the tags 102 and one or more of the sensors 104 with the server software 109 can be performed using a Wireless Application Protocol (WAP), which is described in ColdFusion 5 , Chapter 34, the contents of which are incorporated herein by reference.

The present invention may have different uses. For example, it can be used by parents to monitor their children's activities. A parent can associate a Label 102 to your child by any means such as physically attaching or implanting the 102 label on the child. From a browser software 108 or elsewhere, a parent may transmit control data to his child's label 102 to indicate that the label 102 should accept data from other labels 102 associated with particular people, sensors 104 such as the system of global positioning (GPS) satellites identifying the location of children through the day or environmental sensors 104 identifying the content of the air or water (ie, toxins) to which the child is exposed. The label 102 in the child executes the process for storing data on labels 102 illustrated by the flow chart of Figure 2, for the purpose of analyzing and storing the control information sent by the parent. At a later time, the parent can transmit one or more queries from the browser software 108 or any other to find out the identity of the people who come into contact with the child, to retrieve test scores or notes from a teacher, that the child could have received that day, the quality of the air and water to which the child was exposed and the child's movements. The label 102 associated with the child executes the process of transmitting data from the child's label 102, illustrated by the flow chart of Figure 3 for the purpose of responding to the father's query.

The parent may, in the alternative, transmit additional control data to the child's label 102 from the browser software 108 or from any other instructing the child's labels to transmit data periodically from the label 102 to a database 110. In any subsequent time, the parent may transmit one or more queries from the browser software 108 or any other to a database 110 to learn the same information about the child.

Figure 4a shows a filling example from 100 completed by a parent in the browser software 108 or in any other to control the operation of the child's label 102. The filling form may contain one or more of the following fields: Authorized Components for Reception Table 402: This field specifies the components (ie labels, sensors, etc.) from which the child's label can receive data.

Authorized Data for Reception Table 404: This field specifies the types of data (ie, the data identifying the people associated with the labels 102 with which the child comes into contact, punctuation tests, teacher notes, data from the medium environment, location data, etc.) that the child's label 102 can receive.

Authorized Components for Transmission Table 406: This field specifies the components (ie, database 110, etc.) to which the child's card can transmit data.Authorized Data for Transmission 408: This field specifies the types of data that the child's label 102 can transmit.

Figure 4b shows an example of the filling form 450 completed by a parent in a browser software 108 or any other to receive data from the child's label 102 or from a database 110. The filling form may contain one or More of the following fields: Identification Consultation 452: This field requires identification of tagged objects such as people and animals that come into contact with the child.

Environmental Consultation 454: This field requests the content of water and air with which the child has contact.

Performance Consultation 456: This field requests data on the child's behavior, academic performance and athletic performance.

The present invention can be used to authenticate objects such as valuables, sports belongings, and evidences. A vendor may associate a tag 102 with an article of value such as a diamond or paint by any of these means such as physically adding or implanting the tag 102 on the item. From the browser software 108 or any other, a vendor can transmit control data to the tag of the object 102 to indicate that the tag 102 should accept data from other tags 102 identifying the people associated with the other tags 102, sensors 104 such as global positioning system (GPS) satellites identifying the locations of the object through the day or sensors of the environment 104 identifying the content of air or water (ie, toxins) to which the object is exposed. The label 102 in the object executes the process for storing data in the labels 102 illustrated by the flow chart of Figure 2 for the purpose of analyzing and storing the control information sent by the vendor. In a subsequent time, the seller can transmit one or more queries from the browser software 108 or any other to find out the identity of the people who have handled the object, the quality of the air and the water to which the object was exposed, the movements of the object, the title of the chain, the chain of possession and the identity of the object's manufacturers, retailers and distributors. The label 102 associated with the object executes the process for transmitting data from the label of the object 102 illustrated by the flow chart of Figure 3 for the purpose of responding to the query of the vendor.

The vendor may alternatively transmit additional control data to the tag of the object 102 from the software or browser program 108 or either side instructing the tag 102 of the object to periodically transmit data from the tag 102 to a base of data 110. At any subsequent time, the seller may transmit, one or more queries from the browser program 108 or any side to the database 110 to learn about the information about the object.

Another embodiment of the invention performs proximity scanning. In this mode, an event can be recorded within a tag when it comes within a range of another tag. These events recorded later can be sent to a database. This mode can generally be used to track objects that have come in proximity to another object. For example, this mode can be used to track people who have had contact with a child or places where the child has been. This mode can also be used to track the movement of objects with respect to locations within a secure installation.

In one embodiment, the tags may contain one or more of the following: a radio transmitter, a radio receiver, a memory, a software control, a processor and a clock. The memory can include a RAM and a ROM. The control software can be stored in * the ROM. The processor can be of a type that consumes less energy.

The tags may contain 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 more than 255 bytes and can be used to distinguish tags from one another. The tag identifier map can draw a map from a tag identifier to a public key and a counter. In one embodiment, the tag identifier map is implemented with a check table. In another mode, the tag identifier is implemented with a binary search tree. The tag identifier map can be initialized with the public keys of certain tags such as those that are expected to be found and / or those that are determined to be sensitive. This scheme allows labels to discard messages quickly from labels with invalid signatures. Entries in the tag identifier map can be discarded after the map becomes full. The entries can be discarded in any order as first entry-first exit (PIPO, first-in-first-out), least recently used (LRU, least recently used), etc. The time field can be an unsigned integer of four bytes and can contain the current time in any form such as Greenwich mean time (GMT, Greenwich Mean Time).

Figure 5 is a data flow diagram 500 illustrating the operation of a modality of a tag for proximity verification. The tag waits for an interruption in step 502. In step 504, the type of interrupt is determined. If the interruption is a received interrupt, the control proceeds to step 506. In step 506, the identifier of the received broadcast protocol is determined. The identifier of the protocol can be of different types such as an emission of the identification of the label, an emission of the map of the identifier of the label, etc. Exemplary formats of the label identification emission, the issuance of the central authority and the emission of the identifier map of the label are shown in Figures 6a, 6b and 6c respectively. The emission can be encapsulated in a wireless emission packet in the network interface layer and multiple byte values can be transmitted in the order of the highest weight byte stored in the lowest memory address and the lowest weight byte in the address higher .. Signatures can be RSA signatures. The signature of the issuance of the label identifier can take on the identifier of label and the current time fields. The issuer signature of the central authority can take the current time field. One or more of the fields excluding the identifier of the protocol of the issuance of the tag identifier map may be coded with the public key of the central authority. The signature of the tag identifier can take one or more of the fields following the current time.

If the identifier of the protocol is emitter of the identifier of the tag, the control proceeds to step 508. In step 508, the identifier of the tag of the issuance of the identifier of the tag is verified to determine if it is valid. If it is not valid, the transmission is ignored and the control returns to step 502. If it is valid, the control proceeds to step 510. In step 510, the time at which the label identifier is issued is verified to determine if it is within one minute of the current time. If it is not, then the transmission is ignored and the control returns to step 502. If it is, then the control proceeds to step 512. In step 512, the identifier of the label in the issuance of the label identifier is verified for determine if it is present in the tag identifier map (that is, it has been previously found through the label). If not, the control proceeds to step 514. In step 514, a new entry is created for the tag identifier in the label identifier map, and the number of encounters for that entry is reset to one. The control then proceeds to step 502.

If the identifier of the tag is determined to be present in the tag identifier map in step 512, then the control proceeds to step 516. In step 516, it is determined whether the identifier of the tag in the issuing identifier of the tag has a public key. If so, then the control goes to step 518. In step 518, the public key is used to verify the signature. If the verification of the signature in step 518 is not successful, then the transmission is ignored and the control returns to step 502. If the verification of the signature in step 518 is successful, then the control proceeds to step 520. In the step 520, the number of encounters for the identifier of the label on the tag identifier map is increased.

If the identifier of the protocol is determined to be a transmitter of the central authority in step 506, then the control proceeds to step 522. In step 522, the time in the issuer of the central authority is checked to determine if it is within one minute of the current time. If not, then the transmission is ignored and the control returns to step 502. If so, the control proceeds to step 524. In step 524 the public authority key is used to verify the signature on the issuer of the central authority. If the verification of the signature is not successful, then the transmission is ignored and the control returns to step 502. If the verification of the signature in step 524 is successful, then the control proceeds to step 526. In step 526, the The identifier map of the tag is encoded with the public key of the central authority. In step 528, the identifier map of the label is transmitted. The control then returns to step 502.

If the switch is determined to be a timer switch in step 504, the control proceeds to step 530. In one embodiment, the timer switch occurs every 15 seconds. In step 530, the signature is created using the private key of the tag. In step 532, the signature, the tag identifier and the current time are written to the sender of the tag identifier. In step 534, the emission of the identifier of the label. The control then returns to step 502.

The embodiment of Figure 5 has several advantages. The signature makes it unfeasible for any pre-registered label to falsify a real label. Repeat attacks are blocked by the time stamp.

Private keys can be secured; the central authority may be in a secure location; and the labels can be tamper proof. These options prevent a tag from denying contact with another tag. A replacement strategy can be used to prevent attempts to overflow the tag identifier map by issuing false identifiers from the tag. In another mode, a global public / private key pair can be used to authenticate the broadcasts.

In another embodiment of the invention, an alarm sounds within a predetermined time if the label goes out in a particular range of one or more other labels. In one mode, the range is a common transmission / reception range. In one mode, the default time is sixty seconds. A label can be attached physically to a sensitive object that should not leave a safe area. The other tag may be constructed within a secure, immovable location such as a floor or roof or may be carried by authorized personnel. In one modality, a protocol allows and disables labels so that objections can be removed by authorized parties.

This mode can be used to alert security personnel of a movement of objects outside a secure facility, to alert employees of inventory theft in a warehouse, to alert a parent of the day care provider to a child who is Apart from a certain area, to alert a person of the theft of a vehicle engine, or of theft of valuables from a house, to alert an escort in a safe installation of abandonment by a guest, to alert the authorities of the escape of a criminal from the prison or from a house for those criminals under house arrest, etc.

In one embodiment, the tags may contain one or more of the following: a radio transmitter, a radio receiver, a memory, a control software, a processor, a clock and an audible alarm. The memory can include a RAM and a ROM. The control software can be stored in the ROM. The processor can be of a type that consumes less energy.

Labels may contain one or more data structures including a label identifier, a label identifier of a companion label, a private key for the label, a public key for the companion label, a public key of a control authority , an alarm counter, a flag enabled and a time field. The tag identifier can be a variable length string of more than 255 bytes and can be used to distinguish one tag from another. The tag identifier of the companion tag can be a variable length string of more than 255 bytes. Public and private keys can be 16 bytes. The alarm counter can be four bytes. The flag enabled can be four bytes. The time field can be four bytes not assigned integer and can contain the current time in any way such as Greenwich Mean Time (GMT).

Figure 7 is a data flow diagram 700 illustrating the operation of a mode of a label for an out of proximity alarm. The tag waits for a switch in step 702. In step 704, the type of switch is determined. If the switch is a received switch, the control proceeds to step 706. In step 706, the protocol identifier of the received broadcast is determined. The identifier protocol may be of different types such as a sender of the tag identifier, an issuer of the controlling authority (including a permitted control authority and an unused control authority), etc. The example formats of the issuance of the label identifier, the permitted control authority and the unused control authority are shown in Figures 8a, 8b and 8c respectively. Emissions can be encapsulated in wireless broadcast packets in a network interface layer and multi-byte values can be transmitted in a big endian order (the highest weight byte is stored in the lowest memory address and the lowest byte weight in the highest direction.). The signature of the issuance of the label identifier can take the identifier of the label in current time fields. The issuer signature of the controlling authority can take the current time field. The signatures can be RSA signatures.

If the identifier of the protocol is an issuance of the tag identifier, the control proceeds to step 708. In step 708, the identifier of the tag of the issuance of the tag identifier is verified to determine if it is valid. If it is not valid, the emission is ignored and the control returns to step 702. If it is valid, the control proceeds to step 720. In step 710, the time at which the label identifier is issued is verified to determine if it is within one minute of the current time. If not, then the emission is ignored and the control returns to step 702. If so, the control proceeds to step 712. In step 712, the public key of a companion label can be used to verify the signature of the issuance of the label identifier. If the verification of the signature in step 712 is not successful, then the emission is ignored and the control returns to step 702. If the verification of the signature in step 712 is successful, then the control proceeds to step 714. In the Step 714, the alarm counter is reset.

If the protocol identifier is determined as an emission enabled by the control authority in step 706, then the control proceeds to step 716. In step 716, the time in the emission allowed by the authority Control is checked to determine if it is within one minute of the current time. If not, then the emission is ignored and control returns to step 702. If so, the control proceeds to step 718. In step 718, the public key of the control authority is used to verify the signature in the emission that enables the control authority. If the verification of the signature is not successful, then the transmission is ignored and the control returns to step 702. If the verification of the signature in step 718 is successful, then the control proceeds to step 720. In step 720, the flag enabled is set to one. Then control returns to step 702.

If it is determined that the protocol identifier is a disabling emission of the control authority in step 706, then the control proceeds to step 722. In step 722, the time in the disabling issuer of the control authority is verified to determine if it is within the minute of the current time. If not, then the emission is ignored and the control returns to step 702. If so, the control proceeds to step 724. In step 724, the public key of the control authority is used to verify the signature in the enabling emission. of the control authority. If the verification of the signature is not successful, then the emission and control are ignored return to step 702. If the verification of the signature in step 724 is successful, then the control proceeds to step 726. In step 726, the flag enabled is set to zero. Then control returns to step 702.

If the switch is determined to be a timer switch in step 704, the control proceeds to step 728. In one embodiment, the timer switch occurs every six seconds. In step 728, the enabled flag is added to the alarm counter. In step 730 the alarm counter is checked to determine if it is greater than a limit. In one mode, the limit can be 10 seconds. If the alarm counter is greater than the limit, the control proceeds to step 732. In step 732, the label sounds an alarm. The control proceeds to step 702.

If the alarm counter is determined to be less than or equal to the limit in step 730, the control proceeds to step 734. In step 734, a signature is created using the private key of the tag. In one modality, the signature takes the identifier of a companion's label and the current time. In step 736, the signature, the identifier of the protocol, the identifier of the label of a partner, and the current time are written to the issuer of the tag identifier. In step 738, the issuance of the tag identifier is transmitted. Then control returns to step 702.

The embodiment of Figure 7 has a variety of advantages. The signature makes it unfeasible for a fake companion label to falsify a real label. The signature also becomes unviable for a fake control authority to invalidate a label. Replay attacks are blocked by the time stamp. Destroying a label sounds the alarm of a companion tag.

Another embodiment of the invention sounds an alarm if a label comes within a particular range of one or more labels. Each label can contain a list of sensitive labels of other labels that cause its alarm to the sound. In one mode, the range is a transmitter / receiver range. A label can be physically attached to a sensitive object that should not enter a secure area. The other tag can be constructed within an immovable, secure location such as a floor or roof or can be carried by authorized personnel. This mode can include a protocol to add tags to and delete tags from the sensitive tag list.

This mode can be used to alert security personnel of the movement of objects such as dangerous or harmful objects within a sensitive facility, to alert employees of inventory being taken near the exit of a store, to alert a parent or child care provider of a child's movement to a dangerous area or designated persons, to warn a pedestrian who approaches a dangerous area, to warn a driver of a motor vehicle who is approaching dangerous conditions, to alert security personnel to visitors who enter or approach restricted areas, etc.

In one embodiment, the labels may contain one or more of the following: a radio transmitter, a radio receiver, a memory, a control software, a processor, a clock and an audible alarm. The memory can include a RAM and a ROM. The control software can be stored in the ROM. The processor can be of a type that consumes less energy.

Tags can contain one or more data structures including a tag identifier, a private key for the tag, a public key of a tag control authority, a map of the tag identifier, and a time field. The identifier of the tag can be a variable length string of more than 255 bytes and can be used to distinguish tags from one another. Public and private keys can be 16 bytes. The tag identifier map can map the identifier of the tag sensitive to a public key. The identifier map of the tag can be implemented by a check table or a binary search tree. Entries in the tag identifier map may expire in a lower order of use recently if the identifier map of the tag is full. The time field can be an unsigned four-byte integer and can contain the current time in any form such as Greenwich Mean Time (GMT).

Figure 9 is a flow diagram 900 illustrating the function of a modality of a label for a symmetric proximity alarm. The tag waits for a switch in step 902. In step 904, the type of switch is determined. If the switch is a received switch, the control proceeds to step 906. In step 906, the identifier of the protocol is determined of the received emission. The identifier of the protocol may be of different types such as a sender of the tag identifier, an added tag issuer of control authority, a sender of the tag deleted from the control authority, etc. Exemplary formats of the issuance of the label identifier, the issuer of the added label of the control authority and the emitter of the deleted label of the control authority are shown in Figures 10a, 10b and 10c respectively. Emissions can be encapsulated in a wireless broadcast packet in the network interface layer and multi-byte values can be transmitted in an order in which the highest weight byte is stored in the lowest memory address and the byte of lower weight in the highest direction .. Signatures can be RSA signatures. The signature on the issuance of the label identifier can take the identifier of the label and current time fields. The signature on the issuer of the added label of the control authority can take the identifier of the target label, the identifier of the sensitive label, the public key of the sensitive label and the current time field. The signature on the issuer of the deleted label of the control authority can take the identifier of the label target, the identifier of the sensitive label and the current time field.

If the identifier of the protocol is a sender of the identifier of the tag, the control proceeds to step 908. In step 908, the identifier of the tag of the issuance of the identifier of the tag is checked to determine whether it is in the list of tags. labels of sensitive labels. If it is not in the list of sensitive labels, the emission is ignored and the control returns to step 902. If it is in the list of sensitive labels, the control proceeds to step 910. In step 910, the time when the identifier is issued The label is checked to determine if it is within one minute of the current time. If it is not, then the emission is ignored and the control returns to step 902. If it is, then the control proceeds to step 912. In step 912, the public key of the tag identifier in the issuance of the identifier of the The tag can be used to verify the signature on the issuance of the tag identifier, if the verification of the signature in step 912 is not successful, then the issuance is ignored and the control returns to step 902. If the signature verification in step 912 it is successful, then the control proceeds to step 914. In step 914, the alarm sounds.

If the identifier of the protocol is determined to be an emitter of the added label of the control authority in step 906, then the control proceeds to step 916. In step 916, the identifier of the target label of the label is verified to determine if it corresponds to the identifier of the label of the label that receives the emission. If it does not correspond, the emission is ignored and control returns to step 902. If there is a match, the control proceeds to step 918. In step 918, the time in the sender of the added label of the control authority is verified to determine if it is within the minute of the current time. If it is not, then the emission is ignored and the control returns to step 902. If it is within one minute, the control proceeds to step 920. In step 920, the public key of the control authority is used to verify the signature on the issuer of the added label of the control authority. If the verification of the signature is not successful, then the emission is ignored and the control returns to step 902. If the verification of the signature in step 920 is successful, then the control proceeds to step 922. In step 922, the The identifier of the sensitive label in the issuer of the added label of the control authority and its public key are stored in the identifier map of the label. The control then returns to step 902.

If it is determined that the protocol identifier is an emission of the deleted label from the control authority in step 906, then the control proceeds to step 924. In step 924, the identifier of the target label is verified to determine if it matches the identifier of the label of the label receiving the emission. If there is no match, the broadcast is ignored and control returns to step 902. If there is a match, the control proceeds to step 926. In step 926, the time at which the deleted label is issued from the control authority is check to determine if it is within one minute of the current time. If not, then the emission is ignored and the control returns to step 902. If it is within one minute, the control proceeds to step 928. In step 928, the public key of the control authority is used to verify the signature in the issuer of the deleted label of the control authority. If the verification of the signature is not successful, then the emission is ignored and the control returns to step 902. If the verification of the signature in step 928 is successful, the control proceeds to step 930. In step 930, the identifier of the sensitive label in the sender of the deleted label of the control authority and its public key are removed from the tag identifier map. The control then returns to step 902.

If the switch is determined to be a timer switch in step 904, the control proceeds to step 932. In one embodiment, the timer switch occurs every 15 seconds. In step 932, a signature is created using the public key of the tag. In one modality, the signature takes the identifier of the label and the current time. In step 934, the signature, the protocol identifier, the tag identifier, and the current time are written in the issuance of the tag identifier. In step 936, the issuance of the tag identifier is transmitted. Then control returns to step 902.

The embodiment of Figure 9 has a number of advantages. The signature makes it unfeasible for a false sensitive label to falsify a real label. The signature also makes it unfeasible for a fake control authority to add or delete a label. The repetitions are blocked by the time stamp. Labels can be made resistant to hardening to decrease their vulnerability to physical destruction or elimination.

While the aforementioned invention has been described with reference to certain preferred embodiments, the scope of the present invention is not limited to these modalities. One skilled in the art may find variations of these preferred embodiments, which, however, fall within the spirit of the present invention, the scope of which is defined by the claims set forth below.

Claims (52)

1. A system for storing, retrieving and handling data of one or more objects comprising: one or more tags associated with one or more objects; one or more components communicating with at least one of said labels; at least one receiver for receiving control data and information data from at least one of the components within at least one of the labels wherein the information data is about the object that is associated with at least one tag; 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; and at least one of the components transmits at least one query to receive at least a portion of the information data about the object associated with at least one tag.

2. The system for storing, retrieving and handling data of one or more objects as in claim 1, wherein the information data for the associated object they comprise one or more members of the set consisting of: identification of people who come in contact with the associated object, at least one measure of at least one environmental condition to which the associated object was exposed, the academic performance of said object, the athletic performance of said object, at least a measurement of the medical conditions of the object, the authentication of data of the object, the price history of the object, and the movement of the object.

3. The system for storing, retrieving and handling data of one or more objects as in claim 1, wherein one or more components comprises: At least one database to receive information data from at least one label to handle the information data .

4. The system for storing, retrieving and handling data of one or more objects as in claim 1, wherein the control data specifies at least one or more components from which at least one tag receives data.

5. The system for storing, retrieving and handling data of one or more objects as in claim 1, in where the control data specifies one or more types of data that at least one label is authorized to receive.

6. The system for storing, retrieving and handling data of one or more objects as in claim 1, wherein one or more components comprise one or more members of a set consisting of a client computer, a database, a server computer, an input utility and a sensor.

7. The system for storing, retrieving and handling data of one or more objects as in claim 1, wherein one or more labels are micro devices that transmit and receive radio frequency signals.

8. A method for storing, retrieving and handling data of one or more objects comprising the steps of: associating one or more tags with one or more objects; Communicate with at least one of the labels from one or more components; receive control data and information data from at least one of the components within at least one of the labels where the data of information are about the object that is associated with a label; transmitting at least a portion of the information data from at least one label to at least one of the components according to the control data; and transmitting from 'at least one of the components a query to receive a portion of the information data about the object associated with at least one tag.

9. The method for storing, retrieving and handling data of one or more objects as in claim 8, wherein the information data for the associated object comprises one or more members of a set consisting of: the identification of people who come in contact with the associated object, at least a measure of an environmental condition to which the associated object was exposed, the academic performance of the object, the athletic performance of the object, at least a measure of the medical conditions of that object, the authentication of data for the object, the price history of the object, and the movement of the object.

10. The method for storing, retrieving and handling data of one or more objects as in claim 8 further comprises the steps of: receiving information data from at least one tag; and handle said information data.

11. The method for storing, retrieving and handling data of one or more objects as in claim 8, wherein the control data specifies at least one of one or more components from which at least one tag can receive data.

12. The method for storing, retrieving and handling data of one or more objects as in claim 8, wherein the control data specifies one or more types of data that at least one tag is authorized to receive.

13. The method for storing, retrieving and handling data of one or more objects as in claim 8, wherein one or more components comprise one or more members of a set consisting of a client computer, a database, a server computer, an input utility, a sensor and a label.

14. The method of managing one or more children comprising the steps of: associating one or more labels with one or more children; transmit control data and information data to one or more labels; to receive the information data within one or more labels, the information data comprise one or more of the following: the identification of the people who come in contact with one or more children; at least one measure of an environmental condition to which one or more children were exposed, the academic performance of one or more children, the athletic performance of one or more children, when I receive a medical condition measurement, of one or more children; and transmitting at least a portion of said information data from one or more labels in accordance with the control data.

15. The method for handling one or more children as in claim 14, wherein the control data specifies at least one of one or more tags from which at least one tag can receive data.

16. The method for handling one or more children as in claim 14, wherein the control data specify one or more types of data that at least one label is authorized to receive.

1 . The method for verifying the proximity of one or more labels comprising the steps of: receiving a message of a first type; read an identification of a label that sends said messages from the message; and increase a number of encounters to read the identifiers of the label.

18. The method for verifying the proximity of one or more labels as in claim 17, further comprises the step of storing said number of encounters in a data structure of a first type.

19. The method for verifying the proximity of one or more labels as in claim 18, further comprises the step of creating an entry for said identifier of the tag retrieved in the data structure if the identifier of the retrieved tag is not ready within the data structure of said first type.

20. The method for verifying the proximity of one or more labels as in claim 18, and n where the step Storage is performed only if a signature of the identifier of the tag read in the message of the first type is verified.

21. The method for verifying the proximity of one or more labels as in claim 18, wherein the increment step is only performed if a time in said message of the first type is within a redetermined period of time.

22. The method for verifying the proximity of one or more labels as in claim 21, wherein the predetermined time period is not more than one minute from a current time.

23. The method for verifying the proximity of one or more tags in claim 8, further comprises the step of transmitting said data structure of the first type upon receipt of a message of a second type.

24. The method for verifying the proximity of one or more labels as in claim 23, wherein the transmission step is performed only if a signature in said message of a second type is verified.

25. The method of verifying the proximity of one or more tags as in claim 23, further comprises the step of encrypting the data structure of the first type.

26. The method for verifying the proximity of one or more labels as in claim 17, further comprises the steps of: receiving a time switch; create a message of said first type; and send said message of the first type.

27. The method for verifying the proximity of one or more labels as in claim 17, wherein the first type message comprises one or more of the following: a signature of a label that is sent said message, an identifier of a label that is send to that message, and a current time.

28. The method to generate an alarm when one or more labels fall outside of a proximity, comprising the steps of: receive a message of a first type; read an identifier of a label when the message is sent from the message; Y reset the alarm counter for the read identifier.

29. The method for generating an alarm as in claim 28, wherein the reset step is performed only if a signature of said identifier of the tag read in the message of the first type is verified.

30. The method for generating an alarm as in claim 28, wherein the reset step is performed only if a time in the message of said first type is within a predetermined period of time.

31. The method for generating an alarm as in claim 30, wherein the predetermined time period is not more than one minute for a current time.

32. The method for generating an alarm as in claim 28, further comprises the steps of; receive a timer switch; increase an alarm counter; Y sound an alarm if the alarm counter is greater than the predetermined limit.

33. The method for generating an alarm as in claim 32, wherein the increment step and the voicing step are performed only when the switch reception is allowed by the label.

34. The method for generating an alarm when one or more tags fall within a proximity, comprises the steps of: receiving a message of a first type; read an identifier of a label that sends said message of the first type; and sound an alarm if the reading identifier is not in a list of sensitive labels.

35. The method for generating an alarm as in claim 34, wherein the step of sounding an alarm is performed only if a signature in the message of the first type is verified.

36. The method for generating an alarm as in claim 34, wherein said step of sounding a alarm is only carried out if a time in said message of the first type is within a predetermined period.

37. The method for generating an alarm as in claim 36, wherein the predetermined period is not more than one minute for a current time.

38. The method for generating an alarm as in claim 34 further comprises the steps of: receiving a message of a second type; read a label identifier from the message of the second type; and add the tag identifier to the list of sensitive tags.

39. The method for generating an alarm as in claim 38, wherein the step of adding is performed only if a signature in the message of the second type is verified.

40. The method for generating an alarm as in claim 34 further comprises the steps of: receiving a message of a third type; read an identifier of the label from the message of the third type; Y Remove the tag identifier from the list of sensitive tags.

41. The method for generating an alarm as in claim 40, wherein the step of removing is performed only if a signature in the message of said third type is verified.

42. The method for managing the inventory including one or more objects, comprises the steps of: associating one or more labels with one or more objects; transmit control data and information data to one or more labels; receiving the information data within one or more labels, the information data comprises one of the following: a location of one or more objects, a time in which one or more objects was in the location, the identity of the people who took or released possession of one or more objects, the identity of the people who came into contact with one or more objects, at least a measure of at least one environmental condition to which one or more objects was exposed, a weight of one or more objects, the time in which one or more objects had the weight, dimensions of one or more objects, and a time in which one or more objects had the dimensions; Y transmit at least a portion of the information data from at least one label according to the control data.

43. The method for handling the inventory including one or more objects as in claim 42, wherein the control data specifies at least one of one or more tags from which one or more tags can receive data.

44. The method for handling the inventory that includes one or more objects as in claim 42, wherein the control data specifies one or more types of data that one or more tags is authorized to receive.

45. The method for handling inventory that includes one or more objects as in claim 42, further comprises the steps of: receiving said information data from at least one tag; and handle the information data.

46. The method for handling the inventory including one or more objects as in claim 42, wherein the step of transmitting control and information data is performed by one or more components, the components comprise one or more members of the set consisting of a client computer, database, a server computer, an input utility, a sensor and a label.

47. The method for handling inventory that includes one or more objects as in claim 46, further comprises the step of: transmitting from at least one of the components at least one query to receive a portion of said information data about the object associated with when minus a label

48. The system for managing inventory that includes one or more objects comprising the steps of: one or more labels associated with one or more objects; one or more components transmitting control data and information data to one or more labels; at least one receiver for receiving control data and information data from at least one of the components within one of the labels wherein the information data comprises one or more of the following: a location of one or more objects, a time in which one or more objects was in the location, the identity of the people who took or released the possession of one or more objects, the identification of the people who came in contact with one or more objects, at least one measure of an environmental condition to which one or more objects was exposed, a weight of one or more objects, a time in which one or more objects had the weight, dimensions of one or more objects, and a time in which one or more objects had the dimensions; and at least one transmitter for transmitting a portion of the information data from at least one tag according to the control data.

49. The system for managing inventory that includes one or more objects as in claim 48, wherein the control data specifies at least one of one or more tags from which one or more tags can receive data.

50. The system for managing inventory that includes one or more objects as in claim 48, wherein the control data specifies one or more types of data that one or more labels are authorized to receive.

51. The system for managing inventory that includes one or more objects as in claim 48, wherein the Components comprise one or more members of the set consisting of a client computer, a database, a server computer, an input utility, a sensor and a label.

52. The system for managing inventory that includes one or more objects as in claim 48, wherein the control data comprises at least one query to receive at least a portion of said information data about the object associated with at least one tag.