RFID system with packetized data storage in a mobile environment: methods, systems and program products

Abstract

An RFID system includes transponders transmitting or receiving packetized data in standard form in lieu of custom format for applications executable in a mobile device or network. Tag data may be packetized in any of several standard formats. Each format includes a layer to identify packet format. In one embodiment, a tag contains a standard UDP header with a checksum and payload data. The application opens a socket to listen to UDP connections. The device transmits a RF signal activating tags which transmit UDP packets to a RFID reader in the device. The packets are passed to an IP stack which strips away the UDP header and validity of the checksum verified. If verified, the device transmits the payload to an application running in the device or a network, otherwise, the IP stack notifies the tag the transmission failed and requests re-transmissions which are repeated until a successful transmission occurs.

Description

BACKGROUND OF INVENTION

[0002] 1. Field of Invention

[0003] This invention relates to automatic identification systems, methods and program products. More particularly, the invention relates to an RFID system with packetized data storage in a mobile environment: methods, systems and program products.

[0004] 2. Description of Prior Art

[0005] Mobile communication devices, typically cell phones, laptops and other portable devices are active with cellular wireless or short-range wireless systems. Cellular systems require service areas to be arranged into cells, which have their own transmitter and receiver base stations. In each cell a group of frequencies are used by the mobile devices for communication with other devices and external networks via the base station. Cellular systems have ranges in the order of kilometers. The frequency bands and other parameters for cellular systems are described in the text “Cellular Radio Principles and Design”, by R. C. V. Macario, published by McGraw-Hill, NY, N.Y., 1993 (ISBN: 0-07-044301-7) at page 210.

[0006] Short-range wireless systems operating with mobile communication devices operate in the unlicensed portion of the radio spectrum, usually either in a 2.4 GHz Industrial, Scientific, and Medical (ISM) Band or the 5.0 GHz Unlicensed-National Information Infrastructure (UINII) Band, and have a typical range of one hundred meters or less. Short-range wireless systems can be combined with systems wired to the Internet to provide communication over long distances via an access point. A description of short-range wireless systems is described in the text, “802.11 Wireless Networks as the Definitive Guide”, by Matthew S. Gast, published by O'Reilly, Associates, Inc. Sebastopol, Calif. (ISBN: 0-596-001883-5), 2002, Chapter II.

[0007] Short-range wireless communications systems find use in automatic identification systems (AIS). Radio Frequency Identification (RFID) systems are one embodiment of AIS which find use in short-range wireless communication system. The typical RFID system includes a RFID reader and a RFID transponder linked together by a radio frequency generated by the reader. The transponder is attached or coupled to an item for identification purposes. RFID systems are described in the text “RFID Handbook—Radio-Frequency Identification Fundamentals and Applications” by K. Finkenzeller, published by John Wiley & Sons LTD, New York, N.Y. (ISBN 0-471-98851 0) 1999, pages 6-7, and fully incorporated herein by reference.

[0008] In one embodiment, the reader may be incorporated into a mobile device which communicates with the RFID transponder via a radio frequency signal. The reader sends out a RF signal that “wakes up” the RFID transponder. The transponder may be active or passive. In response to the RF signal, the transponder transmits a data signal back to the reader via a RF frequency signal. The transponder or “tag” includes a memory and is incorporated into an item. The tag stores data descriptive of the item for identification purposes. An exemplary tag information block is described in related application, Ser. No. ______, filed ______, supra, beginning at page 24, line 18, and shown in FIG. 5. The memory may be random access or read only or erasable read only memory and the like. Data is stored in the memory in a customized data structure and format, according to the requirements of an application executable in the mobile devices or in an external network. Most RFID applications define an entire vertical structure from the format of the bits of the RFID tag to the top-level application behavior. Each time a new application is created, the data structure and format of the tag must be customized to meet the requirements of the new application. Re-creating the data structure and format for new applications is expensive and time consuming. Moreover, the customized data structure and format limits processing of the tag data for the application executing in the mobile device and can impede off-loading the tag data to other external data processing system. What is needed in the art is a RFID system in a mobile environment having a data structure and format for tag information which facilitates (a) creating new applications or changes to existing applications executable in the mobile device or another environment with minimum effort; (b) reading or writing tag data between the tag and the mobile device or an external network, and (c) allowing external applications to be transferred to the RFID environment with no or little modification.

[0009] Prior art related to the present invention includes the following:

[0010] A. U.S. Pat. No. 6,398,105B2 entitled “Automatic Data Collection Device That Intelligently Switches Data Based On Data Type”, issued Jun. 4, 2002 discloses intelligently routing data received from an automatic data collection (“ADC”) device in an ADC device platform based on its type. A data routing mechanism operates on the data-receiving side of an ADC data server. After identifying the characteristics of the input data, the data routing mechanism determines the destination for the data based on the characteristics then routes the data to the selected destination. For some types of data, the selected destination may be an intermediate destination where the data undergoes additional processing before being transmitted to another location, while for other types of data the selected destination may be the application that ultimately processes the data. For example, the data routing mechanism may receive a set of input data, analyze the data to determine that the data is voice data, and then route the data to a speech recognition module that processes voice data. ADC devices accommodated by the system include bar code readers, speech recognition systems, RF tag readers, resonator readers, and two-dimensional symbol readers optical character recognition (“OCR”) systems. The invention finds application within a network of ADC device platforms that receive requests for input data from both local and remote applications. Data may be communicated to remote users using any data protocol, including the Transmission Control Protocol (“TCP”), the User Datagram/Internet Protocol (“UDP/IP”) or the User Datagram Plus Protocol (“UDP+”).

[0011] B. U.S. Pat. No. 6,150,921 entitled “Article Tracking System”, issued Nov. 21, 2000 discloses tracking mobile tags. Cell controllers with multiple antenna modules generate a carrier signal which is received by the tags. Tags shift the frequency of the carrier signal, modulate an identification code onto it, and transmit the resulting tag signal at randomized intervals. The antennas receive and process the response, and determine the presence of the tags by proximity and triangulation. Distance of a tag from an antenna is calculated by measuring the round trip signal time. The cell controllers send data from the antenna to a host computer. The host computer collects the data and resolves them into positional estimates. Data are archived in a data warehouse, such as an SQL Server. The tag datagram may contain a header to enable the cell controller to detect the tag's presence, an identifier preamble, which may be implemented, for example, as a validity check such as a cyclic redundancy check (CRC), the tag's UID and optional data sections, which can include data from within the tag.

[0012] C. U.S. Pat. No. 6,448,979 entitled “Printed medium activated interactive communication of multimedia inormation, including advertising” discloses communicating multimedia information using a scanner for machine-readable code containing a link information corresponding to a provider information depicted on the printed medium. A user interface obtains user input information corresponding to the provider information. A communications bridge sends the link information and the user input information via the network. A receiver in communication with the scanner, capable of receiving the link information and user input information, and further capable of receiving and playing a multimedia information sequence. A portal server in communication with the scanner via the network capable of selecting a multimedia information sequence corresponding to the link information and the user input information.

[0013] None of the prior art discloses or suggests an RFID system in a mobile environment which satisfies the needs of the art for creating new application with minimum effort by using a packetized and preferably standardized data structure and format which facilitates reading and writing data to a tag and enables external application data to be communicated within the RFID environment.

SUMMARY OF THE INVENTION

[0014] An RFID system includes transponders or tags or data carriers having stored packetized data in a standard form in lieu of custom format which facilitates data transfer to/from the tags and access to extended applications running in a device, typically a mobile device or a network. The tag data may be packetized in any of several formats including standardized and globally addressable formats such as e.g. UDP, IPv4, IPv6, and the like, alone or in combination. This allows even more complicated protocols known in the art such as HTTP, HTTPU, etc, to be layered on top of the basic formats such as UDP, IPv4, IPv6, etc. Each format includes a layer to identify the packet format in the tag. In one embodiment, a tag contains UDP packets including a standard UDP header with a checksum and payload data. An application in the device opens a socket to listen to UDP connections. The device transmits a RF signal for activating tags within the coverage of the device. In response, the tag transmits IP packets to a RFID reader in the device, which strips the RFID header, and passes the packets to an IP stack in the device. The IP header is stripped away by the IP stack and the validity of the checksum verified. If verified, the device transmits the payload, which can be an UDP, TCP, or ICMP packet, to the application running in the device, which can send and receive data to/from the tag. Otherwise, the IP stack notifies the tag the transmission failed and requests a re-transmission from the tag which is repeated until a successful transmission occurs or the IP stack drops the packet if re-transmission is unsuccessful after a number of tries or sends a message to the application of the packet failure. In another embodiment, an UDP packet is used instead of an IP packet. The RFID reader in the device reads the packet, and removes the RFID headers, which are used to recognize the payload as an UDP packet. The payload is then transferred to the IP stack, which then delivers the payload to an application running in the device. In another embodiment, a UIDP packet is wrapped within an IP packet for transfer to an application external to the device. An application in the device opens a socket to listen to UDP connections. In response to a device activation signal, tags within the coverage of the device transmit packets to the reader, which passes them to an IP stack in the device. The IP stack parses the IP header; checks the packet destination and verifies the checksum validity. If verified, the packet is passed to the destination address which may be external to the device or passed to an application in the device if a loopback address is contained in the header, otherwise the re-transmission process described in the previous embodiment is conducted. In still another embodiment, data packets in UDP, IP format are transmitted to and stored in the tag from an application running in the device or a network. The RFID reader, which in this case can also function as a writer device, then adds the proper header data for packet recognition before putting the payload on the tag.

[0015] An aspect of the invention is a RFID system storing packetized data in transponders or data carriers or tags in standardized formats in lieu of custom format.

[0016] Another aspect is a data carrier in a RFID system storing packetized data in UDP/IP formats and combinations thereof with or without fully or partly compressed or shortened or omitted headers.

[0017] Another aspect is a mobile terminal and method in RFID system transmitting activation signals to tags within the signal coverage area and sending and receiving packetized data to/from the tags.

[0018] Another aspect is a mobile terminal and method in a RFID system including a reader in the terminal capturing and transmitting packetized data from/to a tag.

[0019] Another aspect is a mobile terminal and method in a RFID system including a communication protocol stack transmitting and receiving packetized data between a tag and an application running in the terminal or a network.

[0020] Another aspect is a mobile terminal and method in a RFID system including an Internet protocol stack routing packetized tag datagrams from tags to/from destinations identified in the tag datagrams

[0021] Another aspect is a mobile terminal and method in an RFID system decompressing or expanding headers in a tag datagram.

[0022] Another aspect is an RFID system and method including a mobile terminal coupled to a transponder for activating the transponder to send and receive packetized data in UDP/IP format and communicating with a network to read the packetized data for an application running in the network or in the terminal.

DESCRIPTION OF THE DRAWINGS

[0023] The invention will be further understood from the following detailed description of a preferred embodiment, taken in conjunction with an appended drawing, in which:

[0024] FIG. 1 is a representation of an RFID system including a mobile device containing a reader linked to a transponder and an external network and incorporating the principles of the present invention;

[0025] FIG. 2A is a representation of a datagram structure with a User Datagram Protocol (UDP) packet header in the tag of FIG. 1

[0026] FIG. 2B is a representation of a datagram structure with a compressed User Datagram Protocol (UDP) header in the tag of FIG. 1;

[0027] FIG. 3 is a representation of a datagram structure for a combined Internet Protocol Version 4 (Ipv4) packet header and a UDP header in the tag of FIG. 1;

[0028] FIG. 4 is a flow diagram of the mobile device of FIG. 1 processing a UDP packet in the tag of FIG. 2A;

[0029] FIG. 5 is a flow diagram of the mobile device of FIG. 1 processing an IP/IUDP packet in the tag of FIG. 3,

[0030] FIG. 6 is a flow diagram of the mobile device writing data to the tag of FIG. 1.

DESCRIPTION OF PREFERRED EMBODIMENT

[0031] FIG. 1 discloses an RFID system 100 including a mobile device 102 containing an RFID reader 104 linked by a RF frequency to a transponder or tag 106. The mobile device is also linked to an external network 108 including a terminal 110, typically a server. The network 108 can be the Internet, an Intranet, a mobile phone network, a PSTN, a PBX or the like. The device 102 includes antennas 112 for receiving network or cellular transmissions and short-range transmissions. The antennas are coupled to a short-range transceiver 114; a network transceiver 116 and an input/output (I/O) circuit 118. A processing unit (CPU) 120 services the transceivers 114, 116; the I/O circuit 118 and is coupled to a display 122. A keyboard (not shown) enables a user to input instructions and/or data to the processor and responds to commands displayed in the display 122. The processor interacts with a storage unit typically a Read Only Memory (ROM) 126 and a Random Access Memory(RAM) 128. The ROM 126 stores applications executable with the tag 106 and the server 110. The RAM includes software for operating the RFID system. An operating system 130, typically a Microsoft Windows Version controls the operation of the device 102. A reader application 132 enables the device to interact with the reader in reading and writing data from/to the tag 106. A routing application 134 is responsive to Internet Protocols 136 or an IP stack 138.

[0032] The IP stack is organized in four conceptual layers where each layer takes responsibility for handling communications with adjacent layers other devices and networks. At the lowest level of the stack, a network interface layer 140 receives and transmits datagrams from/to the RFID reader 104, to be described hereinafter and interfaces with an Internet layer 142. The Internet layer delivers the datagrams to the routing application 134 which decides whether the datagram should be processed locally or forwarded to an appropriate network interface for transmission. If the destination address id is a multicast address (such as e.g. 255.255.255.255) the datagram may be routed to a personal area network, but not outside a gateway. The datagram may thus be transmitted to e.g. a number of nearby Bluetooth devices. A transport layer 144 interfaces with the Internet layer. The transport layer sends or receives data for applications stored in the mobile device or in the external network. An application layer 146 interacts with the transport layer to send or receive data. The application program passes data in the required form to the transport layer for delivery. Data passes up and down the different IP layers according to the data source. Data received from a local application stored in the storage unit 126 or the Internet 108 passes the data down the transport, Internet and network interface layers to the tag 106 via the reader 104. Data passes up the IP stack 138 from the RF tag 106 via the reader 104 to the application stored in the mobile device 102, or an application in the external network. Further details on the functions and operation of the IP stack are described in the text “Internet Working With TCP/IP” by Douglas E. Corner, published by Prentices Hall, Upper Saddle River, N.J. 07458 (ISBN 0-13-216987-8) (v.1), 1995, pages 165-167.

[0033] The reader 104 contains a high frequency interface 148 consisting of a receiver and transmitter with an antenna (all not shown). The interface may have two separate data paths for reading 150 and writing 152 from/to the tag 106. A control unit 154, directed by a microprocessor 156, communicates with the application 134 via CPU 120 in the execution of commands and controls communications with the tag. Further details describing the reader are described in the text “RFID Handbook”, supra, Chapter 11.

[0034] Any type of tag may be used in the present invention. RFID tags can be either active or passive. Active tags require an internal battery or another type of power source and are often read/write tags. Passive tags do not require a dedicated power source, but rather obtain operating power generated from RF signals provided by a reader. Tags may come in a variety of shapes and sizes, but are generally based on a custom-designed silicon integrated circuit. Any transponder/tag may be used in connection with the present invention, and the tag type, size, etc., depends on the particular environment and identification purpose.

[0035] Before further describing the tag, a brief description of RFID technology is believed appropriate. RFID technology utilizes electromagnetic or electrostatic coupling in the radio frequency (RF) portion of the electromagnetic spectrum. The reader 104 is miniaturized and includes an interface network layer. Readers are described in the text “RFID Handbook”, supra, at Chapter 11. The reader includes an antenna (not shown) for transmitting a RF signal that activates the transponder or tag 106. When the tag is activated, it transmits information back to the reader 104. In the case of a passive tag, the tag may be energized by a time-varying electromagnetic RF wave generated by the reader. When the RF field passes through the antenna coil associated with the tag, a voltage is generated across the coil. This voltage is ultimately used to power the tag and make possible the tag's return transmission of information to the reader, sometimes referred to as back-scattering. The reader passes the information to the IP stack for delivery to the application in the device or to an application in the external network. A processor is coupled to the memory and to the reader. The processor is configured to invoke at least the application and to provide the content to the local application as directed by the reader application.

[0036] Now turning to the tag 106, a high frequency interface 158 is linked to an address unit 160 for reading and writing data from/to a memory 162, typically a ROM or EEPROM or the like. The high frequency unit serves as the interface with the reader 104 and may transmit a signal when within the RF zone of the reader. The interface demodulates the reader signals for processing in the address logic unit 160. The address/logic unit 160 controls all reading and writing processes on the tag via a state machine (not shown). Further details on the operation of the tag are described in the text “RFID Handbook”, supra pages 171-177.

[0037] Data is stored in the ROM/EEPROM 162 in packetized form as datagrams, which usually contain only a few hundred bytes of data and carry a header identification that enables network hardware to know how to send the data to a specified destination. In one embodiment of the invention, a User Data Protocol (UDP) packet is structured to include a header 164 and payload data 166. In another embodiment, Internet Protocol (IP) packet is structured to include an IP header 168 and the payload data 166. Both the UDP and IP headers comprise a field to define the data structure type followed by standardized header and payload. In this way, UDP or IP packets may be stored directly on the tag. Depending on the application, data may be read from the tag or written to the tag.

[0038] In FIG. 2A, a UDP packet according to the invention includes a format field 202, a standard UDP header comprising a Source Port ID field 204, a Destination Port ID field 206, packet length field 208, a checksum 210, followed by the payload data 212. The format field comprises bytes 0 and 1 and includes a code, e.g., 0xB58A to define that the packet is a UDP packet. The format field comprises 16-bits. The first byte of the format field is the code, e.g., 0xB58A. The second byte defines the format of the packet. Bytes 2 . . . 10 are standard UDP header fields and bytes from byte 11 are payload data. However, due to the limited storing capacity of the tag, the header of the data packet, e.g., UDP or IP header may be compressed limiting the overhead in the data packet. The compression means that some fields of the standard packet header are omitted or are shorter than standardized fields or are combined together. Another aspect regarding compression of the data carried by the tag is that when additional header fields are added, the data to be transmitted with the RFID signal may end up to a situation, where the RFID tag is not capable of transmitting all the stored data, especially when the tag is of the passive type, with the energy generated by the interrogation signal. Therefore, the excess data needs to be reduced by compressing and reducing the overhead. In the case of receiving data from the tag, the compressed and/or omitted header fields of the received data packet may be decompressed in the mobile device by adding the omitted fields to the header or inflating the fields to comply with the standard format. In a decompression process, data stored in the mobile device may be used. Such data may comprise, for example, one or more lookup tables for compressed fields or data which is received and stored in the mobile device or inputted by the user. Fields of the type such as “length” or “checksum” may be computed by the processor of the mobile device and added to the respective fields. After decompression the forwarded data packets comply with the standard packet formasts, such as IP or UDP. In case of receiving data from the application and writing it to the tag, the same technology may be applied in the opposite way. In this case, standard IP or UDP packets are compressed and the resulting optimized packet is written to the tag. The known header compression techniques may be applied as described, for example, in “RFC 1144, RFC 2507,” etc.

[0039] FIG. 2B describes an example of an RFID tag data structure 220 according to one embodiment of the invention in compressed UDP header format, comprising a format field 202′, a destination port ID field 204′, and a payload data 212′. The field source port ID”, “length”, and “checksum” are omitted from the tag data. When the data packet is received in the mobile device, the format field content instructs the processor that the omitted fields are to be defined and/or computed and the header is appended with the fields created by the processor. To show that the format field of FIG. 2B is different from FIG. 2A, the format field content can be coded, e.g., 0XB58B.

[0040] FIG. 3 describes a datagram structure 300 for Internet Protocol, version 4 (IPv4). A format field 302 is coded, e.g., 0XB5B7 defining the packet format to be IPv.4 compliant. Bytes 2 . . . 25 are standard IP header fields and bytes 26 . . . 33 are UDP header fields. Payload data follows byte 33. A version field 304 defines the header format. An Internet Header Length (IHL) field 306 describes the length of the header. A type of service field 308 describes the quality of Internet service to be applied to the packet. A total Length field 312 describes the length of the packet. An Identification field 314 includes an identifier which uniquely identifies fragments of the datagram. The flag field 316, fragmentation field 318 and a fragment off-set field 320 control fragmentation and reassembly of the datagram. The low order 2-bits of the flag field controls fragmentation of the datagram. A Fragmentation field 318 defines the fragment size for fragmenting the datagram. A fragment off-set field 320 specifies the offset in the original datagram in units of 8 octets, starting at offset 0. A time to live field 322 defines how long in seconds the datagram is allowed to remain in the Internet system. A Protocol field 324 defines which high level protocol was used to create the message being carried in the datagram. The header checksum field 326 insures the integrity of header values. A source address field 328 and destination address field 330 contain 32-bit IP addresses of the datagram sender and intended recipient. An options field 332 comprising three bytes is included primarily for network testing and/or debugging. A padding field 334 is used to insure that the IP header ends and data begins on a 32-bit boundary. The padding is composed of zeros. A Source Port ID field 333, destination port ID field 338, Length field 340 and checksum 342 correspond to the UDP fields described in FIG. 2A. Payload data 344 follows the UDP header. Further details of the datagram in IP version 4 format are described in the text “Internet Working With TCP/IP”, supra, at pages 91-101.

[0041] The data packet itself may be compressed using a compression algorithm such as e.g. Lempel-Ziv or GZIP algorithm. If the headers are compressed as well, the data in the format field then may be chosen so that it reflects and informs the type of compression.

[0042] FIG. 4 taken in conjunction with FIG. 1 describes a process 400, in steps, for reading from the tag a datagram packet having a UDP header, shown in FIG. 2A, as follows:

[0043] Step 1: An application in the device 102 opens a socket to listen to UDP connections.

[0044] Step 2: The RFID reader included in or connected to the mobile device reads a datagram packet from the tag which is picked up by a directional coupler and transferred to the receiver input of the reader.

[0045] Step 3: The datagram packet is passed to the IP stack of the mobile device for processing.

[0046] Step 4: The IP stack strips away the UDP headers and checks the UDP checksum against the packet contents. If the checksum is not valid, the following steps are taken:

[0047] Step 4(a): The IP stack notifies the RFID reader that the transmission has failed and requests a re-read.

[0048] Step 4(b): If the re-read should fail, then re-reading is attempted a few times (defined by the user/developer or compiler times options). If the retransmission is successful, the process proceeds to Step 5.

[0049] Step 4(c): If no reading attempt succeeds, the IP stack can either drop the packet silently, or send a message to the user application designed to deal with RFID reader failures.

[0050] Step 5: The IP stack passes the payload data to the application listening to the UDP socket.

[0051] Step 6: The application then interprets the data and acts accordingly.

[0052] FIG. 5 describes a process 500, in steps, for receiving data from a tag including an IP header, shown in FIG. 3, as follows.

[0053] Step 1: An application in the mobile device opens a socket to listen to IP, TCP or UDP connections.

[0054] Step 2: The RFID reader in the device or connected to it reads the data from the tag via the reader's antenna. The signal is transferred to the input of the reader.

[0055] Step 3: The data packet is passed to the IP stack in the device for implementation.

[0056] Step 4: The IP stack processes the IP header and checks the destination of the packet.

[0057] Step 5: The IP header checksum is checked and if the checksum fails, a retry process is repeated as described at steps 4(a), 4(b), and 4(c) in the process 400,.

[0058] Step 6: If the destination is the device itself (denoted by using a looped-back address in the IP header), the IP stack will strip away the IP header and continue to pass the payload to the application listening on the UDP or TCP socket.

[0059] Step 7: If the destination is not the device, the IP packet will be routed accordingly.

[0060] FIG. 6 describes a process 600, in steps, for writing data to the tag from an application in the mobile device or an application in the network, as follows:

[0061] Step 1: An application opens a socket to locate a UDP/IP tag for writing purposes.

[0062] Step 2: The RFID reader transmits a RF signal to locate a tag having an erasable read-only memory or the like.

[0063] Step 3: The tag transmits a signal to the reader including a datagram describing the data content of the tag.

[0064] Step 4: The reader processor determines if the tag is writeable, and, if so, alerts the application program executable in the mobile device or the network to prepare to transmit the data after the reader completes a handshake with the tag.

[0065] Step 5: If the tag is not writeable, the reader disregards the tag signal and searches for another tag that is writeable.

[0066] Step 6: The application program transrmits the data to the reader for retransmission to the tag. The reader appends the RFID header information.

[0067] Step 7: The tag receives the application data and stores the data which may include over-writing the erasable read-only memory with the application data.

[0068] Step 8: Upon completion of data transmission and storage, the tag transmits an acknowledgment signal to the application via the reader and IP stack.

[0069] While the RFID system in a mobile environment has been described in terms of a preferred embodiment, various changes can be made therein without departing from the spirit and scope of the invention, as defined in the appended claims, in which:

Claims

1. A transponder for an RFID system, comprising: a) a substrate including RF receiving and transmitting means; b) data storage means storing packetized data in data formats transportable in the Internet; and c) identifying code in the format identifying the data format.

2. The transponder of claim 1 further comprising: d) signal means responsive to an activation signal for transmitting or receiving and storing packetized data.

3. The transponder of claim 2 wherein the data formats are UDP and IP, alone or in combination.

4. The transponder of claim 2 wherein the packetized data is at least partly compressed.

5. A mobile device in a RFID system, comprising: a) signal apparatus transmitting activation signals and sending/receiving packetized datagrams transportable in the Internet to/from at least one transponder; b) a communication protocol stack processing and routing packetized datagrams within the device or to a network; c) stored programs operating the device in the RFID system and implementing communications with a network; and d) reading apparatus processing packetized datagrams from a transponder.

6. The mobile device of claim 5 further comprising: e) at least one application stored in the device and responsive to the packetized data.

7. The mobile device of claim 5 wherein the packetized datagram is in UDP or IP or combined UDP/IP format including a header with at least partly compressed or shortened or omitted fields.

8. The mobile device of claim 6 further comprising: f) header processing means decompressing or expanding or providing omitted fields in the datagram.

9. The mobile device of claim 8 further comprising: g) parsing means processing datagrams for transmission to the network.

10. The mobile device of claim 7, wherein the packetized datagrams are at least partly compressed.

11. A RFID system, comprising: a) a transponder containing packetized datagrams in data formats transportable in the network and responsive to activation signal; b) a mobile terminal generating the activation signals and sending/receiving the packetized datagrams to/from the transponder; c) a communication protocol stack stored in the mobile terminal processing and routing the datagrams; d) a network linked to the terminal receiving and transmitting the packetized datagrams; and e) a reader in the terminal processing the packetized datagrams transmitted from the transponder.

12. The RFID system of claim 11 wherein the reader is located in the network.

13. The RFID system of claim 11 wherein the communication protocol stack checks a checksum in the packetized datagram against the packet contents and notifies the reader the transmission has failed if the checksum is not valid.

14. The RFID system of claim 13 wherein the communication protocol stack requests a re-transmission from the transponder if the checksum is not valid.

15. The RFID system of claim 13 wherein the communication protocol stack drops the packetized datagram or notifies an application running in the terminal if the re-transmission is unsuccessful.

16. The RFID system of claim 13 wherein the communication protocol stack transmits the packetized datagram to an application running in the terminal or to an application running in the network.

17. The RFID system of claim 13 wherein the communication protocol stack parses a header in the packetized datagram and routes the packetized datagram to a destination identified in the header if a checksum in the packetized datagram is valid.

18. The RFID system of claim 13, wherein the packetized datagrams are at least partly compressed.

19. A method for routing packetized data between a data carrier and destination address comprising: a) receiving and sending a data packet from and to the data carrier; b) identifying a format of the data packet; c) processing the data packet according to the identified format; and d) routing the processed data packet to a destination address.

20. The method according to claim 19, wherein the data packet comprises an identification data, a header data and a payload data.

21. The method according to claim 19 wherein the data packet without identification data is transportable in the Internet.

22. The method according to claim 19, wherein the data carrier is an RFID tag.

23. The method according to claim 19, wherein the destination address is an internet address (IP address) or an IP protocol port or both.

24. The method according to claim 20, wherein the header data is UDP header data.

25. The method according to claim 20, wherein the header data is at least partly in compressed form.

26. The method according to claim 25, wherein the processing comprises decompressing the received header data.

27. The method according to claim 20 wherein the payload data is at least partly in compressed form.

28. The method according to claim 20 wherein the payload data is in uncompressed form.

29. The method according to claim 20 wherein the header data is standard IP protocol packet header data.

30. The method according to claim 19 wherein the routed packets can be directed to a network or an application within the device.

31. The method according to claim 19, wherein the network can be an external network (e.g. the Internet) or a local network (such as a personal area network, or a local area network).

32. A method for writing a packetized data to a data carrier, where the data carrier is an RFID tag.

33. A system for routing packetized data comprising: a) at least one data carrier having at least one data packet embedded therein; b) a data receiving (reading) device or data sending (writing) device for receiving or sending the at least one embedded data packet from the said at least one data carrier; c) a data routing device connectable to the data receiving device for routing the received data packet to a destination address; An application receiving the routed data packet.

34. A system of claim 33, wherein the at least one data packet is at least partly compressed.

35. A system of claim 33, wherein the at least one data packet is transportable in the Internet.

36. A medium, executable in a computer system, for routing packetized data between a data carrier and destination address, the medium comprising: a) program code for receiving and sending a data packet from and to the data carrier; b) program code for identifying a format of the data packet; c) program code for processing the data packet according to the identified format; and d) program code for routing the processed data packet to a destination address.