Source: http://www.google.com/patents/US7988051?dq=6,202,008
Timestamp: 2014-03-15 03:07:33
Document Index: 681903797

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 10', 'art 2', 'art 2', 'Application No. 10']

Patent US7988051 - XML printer system with RFID capability - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsAn XML system is configured to print bar code labels, tags, tickets, cards, or other media, and/or encode RFID devices embedded in media, based upon an extensible markup language (XML) input data stream. The XML system includes a computer system operatively coupled to a network. The computer system further...http://www.google.com/patents/US7988051?utm_source=gb-gplus-sharePatent US7988051 - XML printer system with RFID capabilityAdvanced Patent SearchPublication numberUS7988051 B2Publication typeGrantApplication numberUS 12/551,953Publication dateAug 2, 2011Filing dateSep 1, 2009Priority dateDec 17, 2001Also published asUS7600685, US20060249566, US20090321513Publication number12551953, 551953, US 7988051 B2, US 7988051B2, US-B2-7988051, US7988051 B2, US7988051B2InventorsBruce AlleshouseOriginal AssigneeZIP Corp.Export CitationBiBTeX, EndNote, RefManPatent Citations (40), Non-Patent Citations (28), Referenced by (5), Classifications (11), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetXML printer system with RFID capabilityUS 7988051 B2Abstract An XML system is configured to print bar code labels, tags, tickets, cards, or other media, and/or encode RFID devices embedded in media, based upon an extensible markup language (XML) input data stream. The XML system includes a computer system operatively coupled to a network. The computer system further includes an XML processor configured to receive, parse, and process an XML input data stream and obtain schema identified in the XML data stream from a schema repository. The XML processor validates the XML data stream based upon the schema obtained. Also included is an XSLT processor configured to obtain a stylesheet identified in the XML data stream from a stylesheet repository. The XSLT processor transforms data in the XML input data stream into transformed XML data based upon the stylesheet obtained. Also, an XSLFO processor formats the transformed XML data into formatted XML data based upon XSLFO instructions contained in the stylesheet. A barcode rendering subsystem then receives the formatted XML data and generates a bit map representative of the bar code label. Alternatively, the system includes an XML processor configured to receive and process the XML input data stream, a ZPL processor configured to receive and process a format template, a variable data integrator configured to develop an association between the XML data contained in the XML input data stream and the format template, a formatting engine configured to format the associated XML data according to a format governed by the format template, and a barcode rendering engine configured to generate a printable representation of the bar code label, tag, ticket, card, other media, and/or generate encoding information for an RFID device.
27. The computer program product of claim 24, wherein the computer-readable program code instructions are further configured to direct a printer to print the printable representation.
28. A computer program product comprising at least one computer-readable storage medium having executable computer-readable program code instructions stored therein, the computer-readable program code instructions configured to:
wherein the computer-readable program code instructions are further configured to direct a printer to print the printable representation using a proprietary printer control language.
29. A computer program product comprising at least one computer-readable storage medium having executable computer-readable program code instructions stored therein, the computer-readable program code instructions configured to:
format XML data in an XML input data stream according to a format governed by a format template, the format template being configured to govern formatting of data in accordance with a printer control and formatting language or a proprietary programming language; and generate a printable representation based on the formatted XML data;
wherein the computer-readable program code instructions configured to generate the printable representation include being configured to process an in-stream foreign object.
30. A computer program product comprising at least one computer-readable storage medium having executable computer-readable program code instructions stored therein, the computer-readable program code instructions configured to:
generate a printable representation based on the formatted XML
wherein the computer-readable program code instructions configured to generate the printable representation include being configured to process an in-stream barcode-type object.
CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of, and claims of the benefit or priority from, U.S. application Ser. No. 10/505,982 filed Mar. 28, 2006, now U.S. Pat. No. 7,600,685 which is hereby incorporated by reference in its entirety. U.S. application Ser. No. 10/505,982 claims the benefit of priority from International Application No. PCT/US04/015499, having an International filing date of May 17, 2004, which is hereby incorporated by reference in its entirety, and claims the benefit of priority from, and is a continuation-in-part of, then co-pending U.S. application Ser. No. 10/332,604, filed Oct. 20, 2003, now issued as U.S. Pat. No. 7,025,268, which is hereby incorporated by reference in its entirety. U.S. Pat. No. 7,025,268 claims the benefit of priority from International Application No. PCT/US02/36322, having an International filing date of Nov. 13, 2002, which is hereby incorporated by reference in its entirety, and is a continuation-in-part of then co-pending U.S. application Ser. No. 10/197,014, filed Jul. 17, 2002, now issued as U.S. Pat. No. 6,540,142, which is hereby incorporated by reference in its entirety. U.S. Pat. No. 6,540,142 claims the benefit of priority from the following provisional applications: 1) provisional U.S. Application No. 60/345,389, filed Jan. 4, 2002, entitled XML Printer Technology, and 2) provisional U.S. Application No. 60/341,427, filed Dec. 17, 2001, entitled Bar Code Labeling Systems Having Machine Readable Standards. Provisional U.S. Application Nos. 60/345,389 and 60/341,427 are incorporated herein by reference in their entirety.
U.S. application Ser. No. 10/505,982 also claims the benefit of priority from and is a continuation-in-part of co-pending U.S. application Ser. No. 10/601,213, filed Jun. 20, 2003 entitled XML System, which is hereby incorporated by reference in its entirety. U.S. application Ser. No. 10/601,213 is a continuation-in-part of co-pending U.S. application Ser. No. 10/348,422, filed Jan. 21, 2003, now U.S. Pat. No. 6,655,593, entitled Native XML Printer, which is hereby incorporated by reference in its entirety. U.S. application Ser. No. 10/348,422 is a continuation of then pending U.S. application Ser. No. 10/197,014, now issued as U.S. Pat. No. 6,540,142.
FIELD OF THE INVENTION The present invention relates generally to a method and apparatus for printing media, such as tickets, tags, cards, barcode labels, sheet fed paper, continuous and fan-folded paper, plastic media, and for encoding RF (Radio Frequency) identification circuitry (RFID) that may be embedded in media, and more specifically in one embodiment, to an XML (Extensible Mark-up Language) printer that prints such printed media and/or encodes RFID devices based on an XML data stream using existing ZPL-based (Zebra Programming Language) format template.
Referring now to FIG. 1, a specific embodiment of a high-level hardware block diagram of an XML system 10 is shown generally. In the embodiment of FIGS. 1-6, the native or natural �language� of the system is XML, thus the XML system 10 may be referred to as a �native XML printer.� The XML system 10 includes a computer or processing system 12, which includes various hardware components, such as RAM 14, ROM 16, hard disk storage 18, cache memory 20, database storage 22, and the like (also referred to as �memory subsystem� 26), as is known in the art. The computer system 12 may include any suitable processing device 28, such as a computer, microprocessor, RISC processor (reduced instruction set computer), CISC processor (complex instruction set computer), mainframe computer, work station, single-chip computer, distributed processor, server, controller, micro-controller, discrete logic computer and the like, as is known in the art. For example, the processing device 28 may be an Intel Pentium� microprocessor, x86 compatible microprocessor, or equivalent device.
The computer system 12 may be further coupled to a printer system 50. The printer system 50 may include a media/paper control system 52, a printer driver 54 and a print head mechanism 56. Any suitable printer capable of printing barcode labels may be used, which may include various dot matrix, ink jet, laser and/or thermal printers. Of course, dot matrix printers are usually of lower quality and require closer monitoring of the label output. Preferably, the printer system 50 is a thermal transfer printer. Such suitable printers, for example, are available from Zebra Technologies Corporation of Vernon lills, Ill., and may include the Model Xi series barcode printers (XiIII+, 90XiIII+, 96XiIII+, 110XiIII+140XiIII+, 170XiIII+, 220XiIII+, etc.), the 2800 Series barcode printers, Model Z4M, Z6M, 105SL barcode printers, Model R4Mplus, R402, R-140 printer/encoders, and others. Any suitable barcode label printer may be used.
The software blocks illustrated in FIGS. 2-3 include an XML (extensible mark-up language) processor 70 (also referred to as the �XML parser�), an XSLT (extensible stylesheet language transformation) processor 74, an XSLFO (extensible stylesheet language formatting object) processor 78, a bit map/bar code/RFID rendering engine 80, the RFID transceiver 61 and the printer driver 54 (FIG. 1). Of course, the RFID transceiver 61 may be used in conjunction with printed labels, or may be used separately. The function and basic structure of the XML system 10 is unaffected by the inclusion or non-inclusion of the RFID transceiver.
The present XML system 10 utilizes an open format. In particular, the formatting requirements and the form of the barcode label or RFID transponder are all defined in the XML language. Moreover, not only is XML well defined and available for all to use, but non-programmers can understand the data and commands in an XML data stream or file (or hard copy) with minimal training.
The following is a brief overview of the operation of the various software components. First, note that the XML input data stream 90 includes text that identifies the name and location of other required XML documents or files. One such document is referred to as �XML schema� or �schema.� The schema is used to validate the XML input data stream, including the underlying value data. If validation is successful, a stylesheet is applied, as will be described below. The name and location of the stylesheet is also specified in the XML input data stream 90. Application of the stylesheet is handled by the XSLT processor 74, which under the direction of the stylesheet, may transform the underlying XML element names and/or underlying value data. Next, the data is processed by the XSLFO processor 78, which handles formatting and �layout� of the underlying value data, which may include, for example, formatting the underlying value data in accordance with, for example, font type, font size, color, and the like. Next, the underlying value data is processed by the bitmap/barcode/RFID rendering engine 80, which creates a bitmap 92 of the barcode label or the programming code sequence for the RFID transponder corresponding to the transformed and formatted data. The rendering engine 80 may utilize an �instream foreign object� residing in the stylesheet to direct creation of the bitmap. The bitmap 92 is then sent to the printer driver 54 (FIG. 1) for subsequent printing of the barcode label by the barcode printer or to the RFID transceiver 61 for encoding into the RFID transponder 62 (FIG. 1).
Code Segment 1 for an XML Input Data Steam 1 <?xml version=�1.0� encoding=�UTF-8�?>
5 xmlns:xsi=�http://www.w3.org/2001/XMLSchema-instance�
Code Segment 2 for XML Schema 1 <?xml version=�1.0� encoding=�UTF-8�?>
5 <xs:element name=�address� type=�xs:string�/>
10 <xs:element ref=�name�/>
25 <xs:element name=�name� type=�xs:string�/>
35 <xs:element name=�zip�>
Code Segment 3 for an XSLT Stylesheet 1 <?xml version=�1.0� encoding=�UTF-8� ?>
5 xmlns:bo=�http://www.zebra.com/2002/XSL/Barcode�>
10 <fo:simple-page-master master-name=�all-labels�>
15 <fo:flow flow-name=�xsl-region-body� font=�12pt
60 <xsl:value-of select=�.� />
Code Segment 4 for an XSLFO Instance Node Tree Representation 1 <?xml version=�1.0� encoding=�UTF-16� ?>
5 <fo:simple-page-master master-name=�all-labels�>
10 <fo:flow flow-name=�xsl-region-body� font=�12pt Times�>
30 <fo:block font=�bold 14pt Times� text-
<bo postnet interpretation-
50 <fo:block font=�bold 14pt Times� text-
55 align=�left�>10044</fo:block>
60 line=�none�>10044</bo:postnet>
The operation of the RFID transceiver may be according to international standards such as ISO/IEC or according to proprietary specifications from vendors such as Texas Instruments (Tag-it) or Phillips (I� Code). For example, operation may be governed by the International Organization for Standardization (ISO) specification 15693 for vicinity cards, or by ISO specification 14443 for proximity cards. ISO specification 15693 describes the physical characteristics, the radio frequency power and signal interface, and the anticollision and transmission protocol. The transmission protocol specification includes the requests and responses to read, write, and lock the transponder. Note that the ISO specification 15693 is a preferable applicable standard when RFID label tags are involved.
Preferably, the XML system 10 utilizes the �FOP� XSLFO processor 78 available from the Apache Software Foundation because this XSLFO processor may be configured to �call� a subroutine or other processing function when it encounters an instream foreign object that it is not capable of processing. In particular, this XSLFO processor 78 may be set to call the rendering engine software block 80 described herein, to handle the instream foreign object that it is not capable of processing.
Next, as shown in a block 160, if the node contains an instream foreign object representing a barcode or RFID transponder, which is not capable of being processed by the XSLFO processor 78, the rendering engine 80 checks to determine if the instream foreign object has a �namespace� specific to this XML system 10. For example, the rendering engine 80 may check to determine if the namespace associated with the instream foreign object corresponds to the �Zebra Technologies Corporation namespace.� The namespace notation is known in the art. This is shown in line 3 of the code segment 4 as �xmlns:bo=�http://www.zebra.com/2002/XSL/Barcode�>� Thus, as shown in the code segment 4, the namespace defined above is applied to any elements having a �bo� prefix. Such elements having a �bo� prefix are then only available for processing by the rendering engine 80, which �bo� prefix type elements correspond to a barcode-type instream foreign object. The XSLFO processor 78 will not �know� how to process such elements.
For linear barcodes, the bitmap is rendered by converting the text data to a series of dark and light bars whose relative widths conform to the industry specifications for the barcode symbology. The text data may have check characters added before encoding to allow verification of the barcode when it is read by a barcode scanner. The check characters may be required or may be optional depending upon the symbology. The bars may be grouped into modules of bars depending upon the requirements of the encoding of the symbology. The text data may be compressed during encoding depending upon the symbology. The bars may be preceded and/or followed by one or more �finder� bars as defined by the symbology specifications, which allow a scanner to locate the barcode data more easily. Other algorithms may be applied as needed for the proper encoding and proper physical dimensions required by the symbology. The height of the bars, the width of the narrow bar, the ratio of the wide bar to narrow bar, and other symbology specific parameters may be specified by attributes in the XML data. In addition, the barcode bitmap may be rotated (usually in ninety degree increments) as specified by attributes in the XML data.
Referring back to block 170, assuming that the instream foreign object has the appropriate namespace, if the instream foreign object is not a barcode type, then block 170 interprets the elements in the instream foreign object to determine if it is an RFID type. Just like any barcode type may be specified in the instream foreign object, as set forth above, any RFID transponder type may be specified in the instream foreign object as well, depending upon the application. The RFID transponder type is based upon known RFID standards. For example, the RFID type is not limited to an ISO 15693 type of RFID encoding, and may be, for example, a Tag-it or I� Code type of RFID encoding, and the like. The RFID type specifies the basic structure of the RFID data to be encoded, such as the data storage capacity, data addressing scheme, transmit frequency, receive frequency, proprietary features such as serial numbering and data locking, and the like. Each specific known RFID standard is concretely defined, as set forth above.
Code Segment 5�a ZPL Downloadable Template 1 {circumflex over ( )}XA
Thus, in this embodiment, the template shown in code segment 5 is stored in the hybrid XML printer system 300, and no real �work� is performed (i.e., a label is not yet printed). In summary, lines 7-11 define text fields and line 12 defines a bar code that are defined along with associations that will be correlated with actual XML data sent from the ERP system 88 at a later time, along with other parameters, as set forth above. The template of code segment 5 may define which fields are static and which fields are variable. The variable fields have a variable name (stored in the ^FD command), which may be later correlated or �associated� with data to be downloaded at a later time, which data corresponds to the printed label. Thus, in the hybrid embodiment of FIGS. 7-8, the �^FD� command (i.e., followed by �name�) determines the name of the variable that will be sent in the actual XML data that eventually follows the downloading of the template, rather than the actual data that will be printed on the barcode label.
Code Segment 6�Downloaded XML Data for Use with a ZPL Template 1 <?xml version=�1.0� encoding=�UTF-8�?>
The code segment 6 contains three groups of �label� data, as shown at lines 5-11, 12-18, and 19-25, respectively. Note that the three groups of �label� data appear to be similar to code segment 1, namely lines 8-14, 15-21, and 22-28 respectively, because both code segments refer to �Albert Einstein,� �Steven Hawking,� and �Richard Feynman,� respectively, and have associated fields for address, city, state, and zip code data. Accordingly, the data shown in code segment 6 corresponds to three individual labels to be printed. Note, however, that for each of the three labels to be printed, all of the addressee information is printed as text, but only the zip code field is printed as an actual barcode. This is because of the �ABZ� command defined in template of code segment 5, line 12.
Turning now to FIGS. 7 and 8, FIG. 7 shows a high-level functional block diagram of a specific embodiment of the hybrid XML printer system 300, while FIG. 8 illustrates a combined high-level software block diagram and data flow diagram of a specific embodiment of the hybrid XML printer system. The hybrid XML printer system 300 receives data from the enterprise resource planning (ERP) system 88, as described above with respect to the native XML printer system. The data may contain both XML components and ZPL components, such as XML data and/or the ZPL template data. The high level blocks of FIG. 7 illustrate use of a SAX processor 320, which is a type of XML processor. By way of background, a SAX processor (Simple API for XML) does not use the DOM processing model (Document Object Model) used by the XML processors described above with respect to the native XML printer system of FIGS. 2-6.
Various ZPL commands govern the processing and define the fields of the label, essentially establishing and defining the data to be printed. Printer control and other commands may be received at this stage of processing. When all of the format template has been downloaded, the ZPL processing block 322 encounters an �end of label� command (^XZ), which causes the format template to be saved. Note that the ^DF command with the corresponding identifier �E:SHPLABL.ZPL,� (shown at line 2 of code segment 5) indicates to the ZPL processing block 322 that the format template is preferably saved internally in the printer system on the �E:� device in a file named �shiplabl.zpl.� Of course, the format template need not be saved internally in the printer system and may be saved at any storage location, such as on a networked server or a remote location accessible through a communication network.
The ADF (Download Format) ZPL command indicates that the label format of which it is part is to be stored rather than immediately printed. The save actually takes place when the ^XZ is encountered which indicates that all template data has been received.
The SAX processing block 320 processes the XML syntax and determines various elements and attributes defined by the data input stream 340. In this embodiment upon receiving a �_FORMAT� attribute, the data input stream 340 is temporarily interrupted and input data comes from the format template stored in the printer system 300, and thus the ZPL commands embedded in the format template are interpreted by the ZPL processing block 322. Once the commands in the format template have been interpreted, the data input stream 340 again becomes the SAX processing block 320, which continues to process the XML data. Additional passes through the processing under control of the SAX processor 320 may cause various �events� to be initiated, as described above. For example, a �variable data SAX event� 376 may be initiated so that the various fields in the format template are populated with the corresponding or �associated� XML data being received. This is shown by the block labeled �Match XML variable with ZPL label format variable� 380. Essentially, the variables in the XML data input stream 340 are associated with the fields in the format template. For example, in this step, the XML variable, such as the actual XML data �Albert Einstein� (306 of FIG. 9) shown in code segment 6, is matched with the ZPL label format variable, such as the label variable �name� in the ZPL template of code segment 5.
When an �end of label element� event (</label>) is received, the label is complete and now may be printed. Control is then routed to a ZPL formatting engine processing 394, which causes the label to be printed. Preferably, the function of the ZPL formatting engine processing 394 includes the function of bitmap/barcode/RFID rendering. Thus, the block 394 will be referred to as the ZPL formatting engine. This combined function determines the bitmaps for each of the text, barcode, and other fields on the label, integrates the individual bitmaps with proper rotation and magnification into a single label bitmap 396, and sends the completed label bitmap to the print engine (or printer driver 54, FIG. 1) for physical rendering on media. As described above, the ZPL formatting engine processing 394 may be found in various commercially available ZPL printers, such as for example, in printers commercially available from Zebra Technologies Corporation of Vernon Hills, Ill., which may include the following printer models: XiIII+, 9XiIII+, 96XiIII+, 110XiIII+, 140XiIII+, 170XiIII+, 220XiIII+, Model Z4M, Z6M, 105SL Model R4Mplus, R402, R-140 printer/encoders, and any Model Xi series barcode printers.
Also, the RFID transceiver 61 may be operatively coupled to the ZPL formatting engine processing 394 to facilitate communication with the RFID transponder 62. The REID transceiver 61 and transponder 62 may be similar to or the same as the transceiver and transponder shown and described above with respect to the embodiments of FIGS. 1, 2, 6 and 7.
Turning now to code segment 7, the code segment shown immediately below entitled �code segment 7�a ZPL downloadable template with RFID and data logging commands� shows code segment 5 with certain RFID and data logging commands added. The added code will cause reads from and writes to the RFID tag, and logging of the RFID data to a host computer. Line numbering has been inserted for purposes of illustration only and is not part of the code.
Code Segment 7�a ZPL Downloadable Template with RFID and Data Logging Commands 1 {circumflex over ( )}XA
The inclusion of the read unique tag id (^RI) command on line 16 indicates that the tag id number is to be read from the tag and associated with an XML variable named �tagid,� as specified by the ^FD with a parameter of �tagid� on line 16. In addition, the data read from the tag is associated with field number 994 (^FN command with a parameter of 994). Since the text field on line 15 also has a field number of 994, the tag id which is read from the RFID tag will be printed as text on the label in location 188, 394.
To see how the data indicated in the format template of code segment 7 above is returned to a host computer, code segment 8 is shown immediately below, and is entitled �code segment 8�uploaded XML data.� Line numbering has been inserted for purposes of illustration only and is not part of the code.
Code Segment 8�Uploaded XML Data 1 <?xml version=�1.0� encoding=�UTF-8�?>
5 <variable name=�name�>Albert Einstein</variable>
10 <variable name=�tagid�>1248002001</variable>
15 <variable name=�city�>Los Angeles</variable>
20 <label>
25 <variable name=�zip�>10044</variable>
29 </root>
When the printer is requested to upload the log data, the printer forms an XML data stream similar to that shown in code segment 8. The data is very similar to the XML data sent to the printer in order to print the labels, but with some additions. A �root� element has been added so that data from more than one complete print job can be returned in the same XML stream. The name of the log file is specified in the _LOGFILE attribute shown on line 2. The data that was read from the RFID tag is included as �tagid� variables on lines 10, 18, and 26. When this data is received by a host computer, the host will know that the RFID tag with id of �1248002001� was used to identify the goods shipped to Albert Einstein. This data can be stored in a database on the host computer for later reference. Although this example is shown with the unique tag identifier, any data written to or read from the RFID tag could be reported to the host computer in a similar manner.
Specific embodiments of an XML system, including a native XML printer system and a hybrid XML printer system, according to the present invention have been described for the purpose of illustrating the manner in which the invention may be made and used. It should be understood that implementation of other variations and modifications of the invention and its various aspects will be apparent to those skilled in the art, and that the invention is not limited by the specific embodiments described. It is therefore contemplated to cover by the present invention any and all modifications, variations, or equivalents that fall within the true spirit and scope of the basic underlying principles disclosed and claimed herein. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5527407Dec 30, 1992Jun 18, 1996The Goodyear Tire & Rubber CompanyApparatus and method for marking a rubber article with a message readable by a light scanning deviceUS5860068Dec 4, 1997Jan 12, 1999Petabyte CorporationMethod and system for custom manufacture and delivery of a data productUS6154378Mar 23, 1999Nov 28, 2000Lockheed Martin CorporationPolyphase inverter with neutral-leg inductorUS6226675Oct 16, 1998May 1, 2001Commerce One, Inc.Participant server which process documents for commerce in trading partner networksUS6246326May 5, 1999Jun 12, 2001Intermec Ip Corp.Performance optimized smart label printerUS6289501Mar 31, 1999Sep 11, 2001Unisys Corp.Method for generating simple document type definitionsUS6305605Aug 9, 1999Oct 23, 2001John W. GoetzMultiple-casualty incident patient trackingUS6449620Mar 2, 2000Sep 10, 2002Nimble Technology, Inc.Method and apparatus for generating information pages using semi-structured data stored in a structured mannerUS6457883Jun 30, 2000Oct 1, 2002Silverbrook Research Pty LtdInteractive printer reward schemeUS6487566Oct 5, 1998Nov 26, 2002International Business Machines CorporationTransforming documents using pattern matching and a replacement languageUS6507856Jan 5, 1999Jan 14, 2003International Business Machines CorporationDynamic business process automation system using XML documentsUS6539422May 3, 1999Mar 25, 2003Intermec Ip Corp.Automatic data collection device having a network communications capabilityUS6540142Jul 17, 2002Apr 1, 2003Zih Corp.Native XML printerUS6568596Oct 2, 2000May 27, 2003Symbol Technologies, Inc.XML-based barcode scannerUS6600418Dec 12, 2000Jul 29, 20033M Innovative Properties CompanyObject tracking and management system and method using radio-frequency identification tagsUS6655593Jan 21, 2003Dec 2, 2003Zih Corp.Native XML printerUS6764009May 30, 2002Jul 20, 2004Lightwaves Systems, Inc.Method for tagged bar code data interchangeUS6793127 *Apr 4, 2001Sep 21, 2004Koninklijke Philips Electronics N.V.Internet enabled resource constrained terminal for processing tagsUS6908034Jun 20, 2003Jun 21, 2005Zih Corp.XML systemUS6925631Dec 8, 2000Aug 2, 2005Hewlett-Packard Development Company, L.P.Method, computer system and computer program product for processing extensible markup language streamsUS7025268Nov 13, 2002Apr 11, 2006Zih CorporationXML printer systemUS7126716Aug 18, 2000Oct 24, 2006Zih Corp.Printer for printing labels, tags or the likeUS7172122Dec 13, 2004Feb 6, 2007Zih Corp.XML systemUS7267279 *May 18, 2004Sep 11, 2007Tripletail Ventures, Inc.Method for tagged bar code data interchangeUS7339690Jun 20, 2002Mar 4, 2008Fargo Electronics, Inc.Identification card printer with client/serverUS7407102Feb 10, 2006Aug 5, 2008Zih Corp.XML printer systemUS7600685 *May 17, 2004Oct 13, 2009Zih Corp.XML printer system with RFID capabilityUS7630908May 1, 2000Dec 8, 2009John AmrienWireless electronic prescription scanning and management systemUS20020112224Jan 31, 2001Aug 15, 2002International Business Machines CorporationXML data loadingUS20030058469Sep 26, 2001Mar 27, 2003International Business Machines CorporationMethod and apparatus for printing XML directly using a formatting templateUS20030061947Oct 1, 2001Apr 3, 2003Hohberger Clive P.Method and apparatus for associating on demand certain selected media and value-adding elementsUS20030090712Jun 20, 2002May 15, 2003Lenz Gary A.Identification card printer with client/serverUS20060138227Feb 10, 2006Jun 29, 2006Zih Corp.XML printer systemUS20060249566May 17, 2004Nov 9, 2006Zih CorporationXml printer system with rfid capabilityJP2002103746A Title not availableTW578064B Title not availableWO2001006345A1Jul 12, 2000Jan 25, 2001Fargo Electronics IncIdentification card printer with client/serverWO2001030581A1Oct 27, 2000May 3, 2001Zebra Technologies CorpPrinter programming tool and methodWO2003052658A1Nov 13, 2002Jun 26, 2003Bruce N AlleshouseXml printer systemWO2005122057A1May 17, 2004Dec 22, 2005Zih CorpXml printer system with rfid capability* Cited by examinerNon-Patent CitationsReference11 page entitled Welcome-Toshiba TEC Corporation-Toshiba TEC Thermal Transfer Printer B-482: Vertual experienc (sic) (1999) Applicant submits that it was aware of the product more than one year prior to the filing of the above-identified patent application.21 page entitled Welcome�Toshiba TEC Corporation�Toshiba TEC Thermal Transfer Printer B-482: Vertual experienc (sic) (1999) Applicant submits that it was aware of the product more than one year prior to the filing of the above-identified patent application.32 pages entitled Toshiba TEC Corporation-Toshiba TEC introduces B-482 with the following invaluable network capability. (1999) Applicant submits that it was aware of the product more than one year prior to the filing of the above-identified patent application.42 pages entitled Toshiba TEC Corporation�Toshiba TEC introduces B-482 with the following invaluable network capability. (1999) Applicant submits that it was aware of the product more than one year prior to the filing of the above-identified patent application.5Anderegg, J. U.: "SVG and Image "Caching"-Page Fore-/Backgrounds-Transparency" FOP-DEV Mailing List Jan. 24, 2003, Downloaded at: http://mail-archives.apache.org/mod-mbox/xmlgraphics-fop-dev/200301.mbox%3cLEODKBFMBBGFAPEJNBCOEEAACHAA.hansuli.anderegg@bluewjn.ch%3e; Jul. 14, 2010; 3 sheets.6Anderegg, J. U.: "SVG and Image "Caching"�Page Fore-/Backgrounds�Transparency" FOP-DEV Mailing List Jan. 24, 2003, Downloaded at: http://mail-archives.apache.org/mod�mbox/xmlgraphics-fop-dev/200301.mbox%3cLEODKBFMBBGFAPEJNBCOEEAACHAA.hansuli.anderegg@bluewjn.ch%3e; Jul. 14, 2010; 3 sheets.7Application Development Trends Apr. 1999, XML The Last Silver Bullet, J. Vaughan (4 page magazine article).8Auto-ID Center Uses Physical Markup Language in Radio Frequency Identification (RFID) Tag Technology, Cover Pages, http://xml.coverpages.org/ni2001-11-21-c.html, created Nov. 21, 2001.9B�hm, Klemens; "On Extending the XML Engine with Query-Processing Capabilities"; Proceedings of the IEEE Advances in Digital Libraries; 2000; IEEE Computer Society Washington, DC, USA; May 2000; pp. 127-138.10Chicago Tribune, Dec. 4, 2000, New Computer Language to Streamline Business-to-Business e-commerce (1 page).11Extended Search Report for European Patent Application No. 10 18 3493 completed Mar. 18, 2011; 7 pages.12Infoworld, Sep. 4, 2000, www.infoworld.com, EDI-to-XML Conversions Getting. A Boost, Ephraim Schwartz (1 page magazine article).13International Business Machines Corporation, "A Process for Optimized Application of XSL Stylesheets for Use With Partially Static XML Data Streams", Research Disclosure, Mason Publications, whole document, Apr. 2000 , vol. 432, No. 179.14International Search Report-International Application No. PCT/US02/36322, dated Dec. 19, 2002.15International Search Report�International Application No. PCT/US02/36322, dated Dec. 19, 2002.16JetForm XFA-JetForm XML Forms Architecture XFA.ORG (17 page power point presentation). Applicant submits that it was aware of this document more than one year prior to the filing of the above-identified patent application.17JetForm XFA�JetForm XML Forms Architecture XFA.ORG (17 page power point presentation). Applicant submits that it was aware of this document more than one year prior to the filing of the above-identified patent application.18JetForm XML Forms Architecture XFA.COM file://D:\JetForm%20XML%20Forms% 20Architecture %20SFA-Com.htm (10 page website article). Applicant submits that it was aware of this document more than one year prior to the filing of the above-identified patent application.19JetForm XML Forms Architecture XFA.COM file://D:\JetForm%20XML%20Forms% 20Architecture %20SFA�Com.htm (10 page website article). Applicant submits that it was aware of this document more than one year prior to the filing of the above-identified patent application.20Kay M., "XSLT Part 2-How Does XSLIT Transform XML?", Internet Citation, http://web.archive.org/web/20011124080629/http://tutorials.beginners.co.uk/read/id/143, Nov. 24, 2001 (retrieved on May 25, 2004).21Kay M., "XSLT Part 2�How Does XSLIT Transform XML?", Internet Citation, http://web.archive.org/web/20011124080629/http://tutorials.beginners.co.uk/read/id/143, Nov. 24, 2001 (retrieved on May 25, 2004).22Office Action issued in U.S. Appl. No. 11/561,084; Mail Date: Aug. 3, 2010; 12 pages.23Office Action issued in U.S. Appl. No. 11/774,152; Mail Date: Aug. 4, 2010; 10 pages.24Sandstrom, A: "Announce: FOP 0.16 Release"XSL-List Mailing List Jan. 2, 2001; Downloaded at: URL:http://xml.coverpages.org/fop16-Ann.html; Jul. 14, 2010; 2 sheets.25Search Report for European Patent Application No. 10 18 4234 dated Jan. 21, 2011; 8 pages.26Toshiba TEC Corporation Bar Code Systems Engineering Dept., Web Printer XML Function, Sep. 20, 2000 (7 page power point presentation).27X Marks The Spot, Apr. 1999, D. Andrews, website article http://www.idsystems.com/reader/1999-04-infolink/xm110499.htm (3 page website article).28X Marks The Spot, Apr. 1999, D. Andrews, website article http://www.idsystems.com/reader/1999�04�infolink/xm110499.htm (3 page website article).Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8393540 *Jun 10, 2011Mar 12, 2013Zih Corp.XML printer system with RFID capabilityUS8459555May 6, 2011Jun 11, 2013Zih Corp.XML systemUS8544746Jun 14, 2011Oct 1, 2013Zih Corp.XML printer systemUS20110303752 *Jun 10, 2011Dec 15, 2011Zih Corp.Xml printer system with rfid capabilityWO2013152210A2 *Apr 4, 2013Oct 10, 2013Zih CorpComputer language translation filter* Cited by examinerClassifications U.S. Classification235/462.01, 235/462.09, 235/375, 235/462.15International ClassificationG06K7/10Cooperative ClassificationG06Q10/10, G06Q10/00, G06K1/121European ClassificationG06Q10/00, G06Q10/10, G06K1/12BLegal EventsDateCodeEventDescriptionMar 6, 2012CCCertificate of correctionRotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google