Patent Grant
7093767
The present invention generally relates to transaction devices, and more particularly, to a system and method for fabricating a Radio Frequency operable transaction device which may be included in any form factor.
As such, recent years has seen the development of transaction cards, such as credit cards, debit cards, smart cards, pre-paid cards, and the like, as a popular substitute for cash or personal checks. Initial transaction cards were typically restricted to select restaurants and hotels and were often limited to an exclusive class of individuals. The initial cards were difficult to store during long periods of extended use, since the initial cards were constructed of a soft easily alterable paper. As such, transaction card manufacturers began forming transaction cards from more durable material such as plastic.
With the advent of plastic credit cards, the use of transaction cards has rapidly increased world-wide. Transaction cards are now more readily available to the average consumer. The average consumer often prefers the transaction cards over traditional currency since the transaction card may be easily replaced by the card issuer if the user loses or misplaces the card or the card is stolen.
Transaction cards typically allow a consumer to pay for goods and services without the need to constantly possess cash. Alternatively, if a consumer needs cash, transaction cards allow access to funds through an automatic teller machine (ATM). Transaction cards also reduce the exposure to the risk of cash loss through theft and reduce the need for currency exchanges when traveling to various foreign countries. Due to the advantages of transaction cards, hundreds of millions of cards are now produced and issued annually.
The vast number of cards produced demands international standards for card dimensions (e.g., length, width, thickness, shape). For example, the International Standardization Organization (“ISO”) standardizes a transaction card's dimensions under standard ISO/IEC 7812, a standard which is accepted by all transaction card manufacturers industry wide. As such, the machines used to manufacture transaction cards vary little from one transaction card manufacture to another, in order that each manufacturer conforms to the industry standard.
As the number of transaction cards issued increases, so do the security issues surrounding transaction card transactions. Security concerns such as, fraudulent charges, credits, merchant settlement, and reimbursements, etc., have increased due to the increasing use of transaction cards. As a consequence, the transaction card industry started to develop more sophisticated transaction cards which allowed for the reading, transmission, and authorization of transaction card data, while lessening the elevating security concerns.
For example, many transaction card manufacturers are providing alternative transaction devices capable of being used in place of traditional transaction cards. Initially, the replacement transaction devices where manufactured in the form of smart cards, which were capable of transferring user information without the user every having to lose physical control of the device. Thus, smart cards enhance the security of the transactions by virtually eliminating the need for the user to hand the card over to a merchant salesperson for transaction completion.
While the advent of smart cards helped to alleviate some of the security issues surrounding transaction devices, smart cards did little to address fraud issues associated with a lost or stolen transaction card. This is true because the smart cards where manufactured with the same size dimensions as traditional transaction cards and, therefore, the user did little more to secure the smart card against loss than the user did to secure a traditional credit card, for example. More particularly, while the identical size dimensions between the traditional transaction card and the smart card has the cost advantage associated with permitting a card manufacturer to manufacture smart cards on traditional transaction card fabrication machinery, the disadvantage is that the smart card was still subject to similar theft and fraud concerns as a traditional card since smart card users typically would lose or misplace the smart card with similar frequency as with a traditional transaction card.
Thus, to alleviate the fraud cost associated with a lost or stolen transaction device, transaction card providers are searching for suitable technology which would permit a transaction to be completed without the cardholder having to relinquish control of the card, and which would provide increased means of securing the transaction device. One such technology is radio frequency identification (RFID) technology.
Like barcode and voice data entry, RFID is a contactless information acquisition technology. RFID systems are wireless, and are usually extremely effective in hostile environments where conventional acquisition methods fail.
In general, RFID technology permits a card manufacturer to provide for a dimensionally smaller transaction device than a smart card or traditional transaction card. RFID technology, therefore, is better suited for securing against loss or theft. For example, the RFID technology may be embodied in a form factor attachable to the account holder's person or to an often used (or often handled) personal article, such as a key chain, fob or tag. The RFID transaction device may be attached to the personal article in an unobtrusive manner because of its smaller size. As such, the user has increased security against loss or theft, since the user handles the personal article frequently, permitting the user to repeatedly be reminded that the card is present.
One of the more visible transaction device which uses RFID technology is found in the introduction of Exxon/Mobil's Speedpass® and Shell's EasyPay® products, which are attachable to a user's key chain. These products use RFID transponders placed in a fob or tag of irregular shape which enables automatic identification of the user when the fob is presented at a Point of Sale (POS) device. Fob identification data is typically passed to a third party server database, where the identification data is referenced to a customer (e.g., user) credit or debit account for completion of a transaction.
By providing a RFID transaction device (e.g., fob) as described above, transaction account providers are able to attract account users in increasing numbers. The account users often prefer account providers which offer the RFID transaction device option because of the convenience of use and the security using a RF transaction fob provides. As such, because of the increased popularity and benefits associated with RFID transaction devices, many banking and financing institutions, department stores, petroleum companies and other organizations have developed their own RFID transaction devices for use by the organization's consumers.
It is, therefore, an object of the present invention to provide a RFID operable transaction device manufacturing system and method which requires little retrofitting of conventional transaction card manufacturing and personalization machinery.
In one embodiment, the present invention relates to a process for producing a RFID operable transaction device, having any one or more features, such as a holographic foil, integrated circuit chip, silver magnetic stripe with text on the magnetic stripe, opacity gradient, perforations included in the transparent device body for forming an outline of a shape, and an “active thru” date on the front of the device.
In one aspect, the RFID transaction device of the present invention may use RFID technology to initiate and complete financial transactions. In that regard, the transaction device may include one or more RFID transponders and antennas in the device body, which are typically included during the transaction device fabrication. The system in which the RFID transaction device may be used may include a RFID reader operable to provide a RF interrogation signal for powering the transaction device transponder system, receiving a transponder system RF signal including transponder system account data, and providing transponder system account data relative to the transponder system RF signal although, the transaction device may include its own internal power source. The RFID reader may include an RFID protocol/sequence controller in communication with one or more interrogators for providing an interrogation signal to a transponder of the transaction device, a RFID authentication circuit for authenticating the signal received from the transponder, and a serial or parallel interface for interfacing with a point of interaction device.
The RFID reader may be configured to send a standing RFID recognition signal which may be continuously or intermittently transmitted from the RFID reader via radio frequency (or electromagnetic) propagation. In one instance, the transaction device may be placed within proximity to the RFID reader such that the RFID recognition signal may interrogate the device and initialize device identification or authorization procedures.
In another aspect of the invention, a transaction device is provided which may be issued to a user in a transaction device transporter wherein the user may remove the transaction device from the transporter for use with any form factor. In one exemplary transaction device manufacturing method, a plurality of transporter and transaction device (called “transaction device combination” herein) is manufactured simultaneously on a single sheet using conventional manufacturing machinery. Each of the plurality of transaction device combinations is manufactured as a removable subpart the sheet of the plurality of transaction device combinations, wherein each combination may be an independent operable RFID payment device, which is ISO/7810-1985 compliant in size. As such, the transaction device combination may be manufactured, stamped, and/or cut using conventional manufacturing equipment.
The transaction device transporter, including the removable transaction device, are manufactured with at least one border of the transaction device transporter directly adjacent a border of the next adjacent transporter, forming a sheet of conjoined transaction device transporters. Preferably, the sheet of transporters is manufactured including RFID operable transaction devices. More preferably, the sheet is manufactured with RFID operable transaction devices including conventional RFID data transmission circuitry.
Once the sheet of transaction device combinations is manufactured, the sheet may then be fed through a stamping device for imprinting an outline of the transaction device (e.g.,
The sheet may then be cut along the borders of the transaction device transporter into conventional transaction card dimensions, such as, for example, the ISO/IEC 7812 standardized card dimensions noted above. Preferably, the sheet is cut such that the transaction card shaped transaction device combination resulting from the cutting process includes the removable transaction device. The resulting transaction device combination may then be delivered to a transaction device user, who may remove (“punch-out”) the removable transaction device from the transaction device transporter by, for example, applying minimal physical force along lines (e.g., alignment lines) defining the shape of the transaction device imprinted on the transporter. Once removed, the RFID transaction device may be used to complete a RF transaction since the transaction device includes the RFID module. Further, the outline of the imprinting may serve to define the shape of the transaction device. The transaction device manufacturer may predetermine the shape of the transaction device and imprint the predetermined shape in the transporter.
In another embodiment, the transaction device may not be removed from the transporter. Instead, the transaction device combination may be left intact. The combination may be used to complete a RFID transaction since the RFID module is included in the transaction device (which is included in the transaction device combination). In this way, the transaction device combination may be used in similar manner as a conventional RFID transaction device to complete a transaction. That is, a user may position the transaction device combination in proximity to a RFID reader. The RFID module may then provide transaction device account information (e.g., account number, user identifier, device identifier) to the reader, which may forward the information to a merchant system or POS for transaction completion.
Alternatively, the transaction device combination may be equipped with a traditional magnetic stripe, which is ordinarily ISO/IEC 7800, et al., compliant. The magnetic stripe may include user account information which may be provided to a conventional magnetic stripe reader for completing a transaction using traditional magnetic stripe data processing methods. Thus, the user may use the transporter and RFID transaction device in similar manner as a traditional credit card or debit card, and the like.
In another exemplary embodiment, the transaction card body is cut and the transaction device outline is imprinted simultaneously. In this instance, the card manufacturer may utilize a cutting machine configured to imprint an outline of the removable transaction device when the cutting of the transporter is performed. In this way, only one machine action is necessary to cut the transporter body and imprint the removable transaction device outline.
In yet another exemplary embodiment, the transaction device includes the RFID module completely contained within the transaction device outline formed by the imprinting action. The transaction device may be formed or shaped using any desired outline. For example, a suitable outline such as an irregularly shaped key fob outline may be pressed (e.g., imprinted) within the perimeter of each of the plurality of transaction device transporters. The transaction device outline may be pressed or imprinted into the transporter such that the RFID module is contained within the transaction device outline. The transaction device may then be “punched out” of (“removed from”) the transporter by placing minimal physical force at the transaction device outline, such that the resulting RFID transaction device is shaped in the transaction device outline provided.
In yet another exemplary embodiment of the invention, the transaction device manufacturer may manufacture a transaction device sheet including the RFID module wherein the sheet may be cut in the traditional credit card ISO/IEC 7800 et al. compliant shapes and the transaction device is cut in any shape as desired for a RFID transaction device (e.g., teardrop fob shaped). In this way, a transaction device manufacturer may form both transaction cards and irregularly shaped RFID transaction devices on the same sheet simply by designating the proper design or shape to be made.
In still another aspect, the invention includes a means for securing the transaction device to a user's person or to a user's frequently used personal apparatus. For example, in one particular embodiment, the outline of the transaction device may be shaped to include an opening or aperture for securing the transaction device to, for example, a chain, key ring, ring, watch, rope, or the like. The key ring or chain, for example, may be inserted through the opening to secure the payment device to the chain or key ring to guard against the payment device being easily lost or stolen.
In another exemplary embodiment, the RFID module may be removed from the transaction device for use in completing a transaction independently of the transaction device or the transporter. The outline of the module may additionally be pressed inside a transaction device outline as well, although not required. In this instance, an outline of the RFID module may be imprinted on the transaction device transporter wherein the module is positioned inside the transporter outline. The RFID module outline may be imprinted or pressed into the transporter at sufficient depth to permit the module to be easily removed, in similar manner as discussed with the transaction device. The module may be removed from the transporter using any of the methods described herein.
Once removed, the module may be secured using an independent portable carrier. The portable carrier may be configured to encase a portion of the module and lock the module in place. The carrier, including the module, may include an aperture for securing the carrier to a key ring or chain, as described above. The carrier may be affixed to, or included in, any form factor (e.g., wrist watch, pocket watch, money clip, wrist watch band, cellular phone, etc.). Alternatively, the carrier may be secured in any form factor using any suitable securing means. The desired form factor may include an opening for accepting the module and for securely fixing the module to the form factor. The desired form factor may include means for securing the module alongside or adjacent to the form factor body.
Additional features and advantages of the present invention are described in, and will be apparent from, the detailed description of the present exemplary embodiments and from the drawings.
A more complete understanding of the present invention may be derived by referring to the detailed description and claims when considered in connection with the Figures, where like reference numbers refer to similar elements throughout the Figures, and:
The present invention may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. Such functional blocks may be realized by any number of hardware and/or software components configured to perform to specified functions. For example, the present invention may employ various integrated circuit components (e.g., memory elements, processing elements, logic elements, look-up cables, and the like), which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, Java, COBOL, assembler, PERL, extensible markup language (XML), JavaCard and MULTOS with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and the like. For a basic introduction on cryptography, review a text written by Bruce Schneier entitled “Applied Cryptography: Protocols, Algorithms, and Source Code in C,” published by John Wiley & Sons (second edition, 1996), herein incorporated by reference.
In addition, many applications of the present invention could be formulated. The exemplary network disclosed herein may include any system for exchanging data or transacting business, such as the internet, an intranet, an extranet, WAN, LAN, satellite communications, and/or the like. It is noted that the network may be implemented as other types of networks, such as an interactive television network (ITN).
Although the point of interaction device is described herein with respect to a merchant point of sale (POS) device, the invention is not to be so limited. Indeed, a merchant POS device is used herein by way of example, and the point of interaction device may be any device capable of receiving device account data. In this regard, the POS may be any point of interaction device or transaction device acceptance device enabling the user to complete a transaction using an RF responsive transponder.
The RFID reader 104 may be configured to communicate using a RFID internal antenna 108. Alternatively, RFID reader 104 may include an external antenna 106 where the external antenna 106 may be made remote to the RFID reader 104 using a suitable cable and/or data link. RFID reader 104 may be further in communication with a transaction completion system (e.g., merchant system 130) via a data link. In one exemplary embodiment the transaction completion system may include POS device 110 in communication with a RFID reader 104 (via a data link), and a customer interface 118 in communication with the POS device 110. The POS 110 may be in further communication with an account issuer system (not shown) via a network 112 which may be provided the account number and any transaction identifying information (e.g., time, duty, cost of transaction, item negotiated) for transaction completion.
The terms “Internet” or “network” as used herein, may refer to the Internet, any replacement, competitor or successor to the Internet, or any public or private internetwork, intranet or extranet that is based upon open or proprietary protocols. Specific information related to the protocols, standards, and application software utilized in connection with the Internet may not be discussed herein. For further information regarding such details, see, for example, Dilip Naik, “Internet Standards and Protocols” (1998); “Java 2 Complete”, various authors, (Sybex 1999); Deborah Ray and Eric Ray, “Mastering HTML 4.0” (1997); Loshin, “TCP/IP Clearly Explained” (1997). All of these texts are hereby incorporated by reference.
By being in “communication,” what is described may be that a signal may travel to/from one component of the invention to another. The components may be directly connected to each other or may be connected through one or more other devices or components. The various coupling components for the devices can include but are not limited to the Internet, a wireless network, a conventional wire cable, an optical cable or connection through air, water, or any other medium that conducts signals, and any other coupling device or medium.
Where required, the system user may interact with the system to complete a transaction via any input device or user interface 118, such as, a keypad, keyboard, mouse, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®, Blueberry®), cellular phone and/or the like. Similarly, the invention could be used in conjunction with any type of personal computer, network computer, work station, minicomputer, mainframe, or the like running any operating system such as any version of Windows, Windows NT, Windows 2000, Windows 98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris or the like. Moreover, although the invention may frequently be described as being implemented with TCP/IP communications protocol, it should be understood that the invention could also be implemented using SNA, IPX, Appletalk, IPte, NetBIOS, OSI or any number of communications protocols. Moreover, the system contemplates the use, sale, or distribution of any goods, services or information over any network having similar functionality described herein.
A variety of conventional communications media and protocols may be used for the data links. For example, data links may be an Internet Service Provider (ISP) configured to facilitate communications over a local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Lines (DSL), or any wireless communication media. In addition, the merchant system 130 including the POS device 110 and host network 112 may reside on a local area network which interfaces to a remote network (not shown) for remote authorization of an intended transaction. The merchant system 130 may communicate with the remote network via a leased line, such as a T1, D3 line, or the like. In addition, the merchant system 130, including the POS 110 and host network 112, may reside on a local area network, which interfaces with a remote network (not shown) for remote transaction authorization. Such communications lines are described in a variety of texts, such as, “Understanding Data Communications,” by Gilbert Held, which is incorporated herein by reference.
A transaction device account identifier or account number, as used herein, may include any identifier for a transaction device which may be correlated to a user transaction account (e.g., credit, charge debit, checking, savings, reward, loyalty, or the like) maintained by a transaction account provider (e.g., payment authorization center). A typical transaction account identifier (e.g., account number) may be correlated to a credit or debit account, loyalty account, or rewards account maintained and serviced by such entities as American Express, Visa and/or MasterCard or the like.
In general, the transaction devices 102 which use the above RF transmission process may take any form. The RFID circuitry 20 may be included in RFID transaction device 12 for use in completing a RFID transaction and the transaction device 102 may take any form as desired. To facilitate understanding of this invention,
The RFID transaction device 102 (described more fully below) may come in many different shapes. Because a typical card manufacturer may provide both traditional credit card shaped transaction cards and irregularly shaped RFID transaction devices, the manufacturer must have proper machinery for cutting sheets of the devices into the appropriate device size. The present invention provides a system and method for forming the irregularly shaped transaction devices, which utilizes conventional dimensional standards for transaction cards (e.g., credit cards, smart cards, etc.) irrespective of the RFID transaction device shape. This, in turn, allows the manufacturer to manufacture irregularly shaped transaction devices using conventional card manufacturing machinery, with little retrofitting. The invention allows for a manufacturer to use coextensive transaction card and RFID transaction device manufacturing processes which produce both transaction devices simultaneously or individually. The process is termed coextensive since identical material layers and/or circuitry may be used whether the card manufacture desires to cut transaction cards or RFID transaction devices.
Manufacturers of transaction cards 1 take advantage of mass production techniques when manufacturing transaction cards. Instead of producing the cards 1 individually, the cards 1 are produced en masse in sheets 200 which are then cut into the appropriate individual size.
Sheet 200 may be prepared using any conventional method of manufacturing a sheet of multiple transaction devices 1. The present invention modifies conventional methods by including perforation, impressing and RFID circuitry as discussed below. The following description is an exemplary method of manufacturing sheet 200 according to the invention. The description is offered to facilitate a understanding of the invention and not by way of limitation.
In the exemplary embodiment shown, sheet 200 may be formed using multiple material layers.
The fabrication of the individual card sheets 200 may include either direct layout (9 layers) of film or the use of a sub-assembly (5 layers). An exemplary sub-assembly layer 21 may consist of 5 layers of film with room temperature tack adhesive applied over thermoset and thermoplastic adhesives. The resulting cards comprise (from the card front towards the card back) 2.0 mil outer laminate (PVC, polyvinylchloride) including having a holographic foil, embossed surface, chip and other indicia on its surface, 9.0 mil printed PVC core with print side out (card front), 2.0 mil PVC adhesive, 1.7 mil PET GS (extrusion coated polyethyleneterephthalate—gluable/stampable) manufactured by D&K (525 Crossen, Elk Grove Village, Ill. 60007), 2.0 mil PET IR blocking film, 1.7 mil PET GS, 2.0 mil PET adhesive, 9.0 mil printed PVC core with the print side out (card back), and 2.0 mil outer back laminate with a signature panel, applied magnetic stripe and other indicia. Optimally, the PET IR blocking film is fabricated in the middle of the layers to balance the card and minimize warping of the resulting card product.
After eventually combining the sheets, by preferably adhering the front layer 10 on top of the back sheet 12, the total thickness of the transaction card 1, including the subassembly sheet 21, is about 0.032 in. (32 mil.), which is within the ISO thickness standard for smart cards. in one embodiment, the subassembly sheet 21 may be formed including RFID circuitry 20, which may be of sufficient thickness to maintain the smart card standard thickness. Alternatively, the RFID circuitry 20 may be embedded in the sheet 12 or card 1 via a suitable conventional milling process. Because the RFID circuitry 20 (called “RFID module 20” herein) may eventually embedded into the surface of the substrate or the subassembly 21 as described more fully below, the module 20 does not affect the thickness of the overall card 1. Moreover, the about 3′×4′ sheets include predefined alignment markings which define the boundaries of the individual cards 1 to be cut from the sheet. Each exemplary sheet yields over 50 transaction cards (typically 56 cards), wherein each card 1 is within the ISO card size standard, namely about 2″×3.5″.
In an exemplary embodiment, certain compounds are printed over the surface of sheets 10 and 12. The compounds may be printed in accordance with accepted ISO standards. One skilled in the art will appreciate that the printing of the text 30 and logo 50, and optically recognizable ink may be applied to any surface of card 1 such as, for example, the front 10 face (front material layer 10), the rear 12 face (rear material layer 12), the inside or outside surface of either face, between the two sheets of base material and/or a combination thereof. Moreover, any suitable printing, scoring, imprinting, marking or like method is within the scope of the present invention.
The text 30 and logo 50 are printed on the outside surface of each material layer 10, 12 by a known printing process, such as an offset printing process, which provides a thinner ink coverage, but clearer text. More particularly, with respect to offset printing, the artwork is duplicated onto a metal plate and the metal plate is placed onto an offset press printing machine which can print up to four colors during a single run. The offset printed text may include, for example, a corporate name, a copyright/trademark/patent notice, a batch code number, an “active thru” date, contact telephone numbers, legal statements and/or the like. The exemplary offset text may be printed in 4 DBC in opaque white ink or a special mix of Pantone Cool Gray 11 called UV AMX Gray. In one exemplary embodiment, the offset printed text is printed directly on the RFID module 20, such that the text is visible on the module 20 through casual inspection.
A laminate material layer 15 is applied to the back layer 12 of card 1. In one preferred embodiment, the laminate layer 15 includes rows of ISO compliant magnetic stripes 40, wherein each magnetic stripe 40 corresponds to an individual card 1. The magnetic stripe 40 may extend along one length of the card 1 and is applied to the back surface 12. The magnetic stripe 40 may be any width, length, shape, and placed on any location on card 1. In an exemplary embodiment, the magnetic stripe 40 is applied to the outer laminate layer 15 using a tape layer machine which bonds the cold peel magnetic stripe 40 to the outer laminate 15 when it is in a rolled position (not shown). The laminate 15 roll with a rolling hot die and at suitable pressure. The roll is then cut into layers 10, 12 before the card layers are assembled.
After the desired printing is complete and the magnetic stripe applied, the front 10 and back 12 material layers are placed together, and the layers are preferably adhered together by any suitable adhering process, such as a suitable adhesive. One skilled in the art will appreciate that, instead of printing on two material layers and combining the two material layers, a single plastic material layer can be used, wherein the single material layer is printed on one side, then the same material layer is re-sent through the printer for printing on the opposite side.
In the present invention, after adhering the layers together, a layer of lamination (not shown), approximately the same dimensions as the plastic sheets, namely 3′×4′, may be applied over the front 10 and back 12 of card 1. After the laminate is applied over the front 10 and back 12 of the combined plastic material layers, card 1 layers are suitably compressed at a suitable pressure and heated at about 300 degrees, at a pressure of between 90–700 psi, with a suitable dwell time to create a single card 1 device. The aforementioned card fabrication can be completed by, for example, Oberthur Card Systems, 15 James Hance Court, Exton, Pa.
In an exemplary embodiment, the card layers 10 and 12 are fused together in a lamination process using heat and pressure. During the hot press phase, the press is heated to about 300 F. degrees and the pressure builds to about 1000 psi and holds for about 90 seconds. The pressure then ramps up to about 350 psi over an about 30-second period and holds for 16 minutes at the same temperature, namely 300 F. degrees. The sheet 200 is then transferred to a cold press which is at about 57 F. degrees. The pressure builds to about 400 psi and is held for about 16 minutes as chilled water of about 57 F. degrees is circulated in the plates. The cold press then unloads the sheet 200.
In one exemplary manufacturing embodiment, the cards 1 may include internal circuitry for use in completing contactless transactions. For example, card 1 may include a RFID module 20 included in the card body and preferably may be included in subassembly sheet 21. The RFID module 20 is preferably positioned substantially central to the card body but may be positioned at any desired location therein. The RFID module 20 may be included interposed between front surface material layer 10 and back surface material layer 20 during fabrication of the sheet 200. Specifically, the module 20 may be included interposed between at least two layers of the subassembly sheet 20. Alternatively, after lamination, the RFID module 20 may be included within an individual card 1 within a space created by milling the card body and providing room for the insertion of the RFID module 20. As such, upon including the RFID module 20, sheet 200 will comprise a plurality of RFID operable transaction cards 1 wherein each transaction card 1 includes a RFID module 20. Traditional methods for including RFID module 20 in transaction devices 1 are well known, and are intended to be within the scope of the invention.
RFID module 20 may include an antenna 204 for receiving an interrogation signal from RFID reader 104 via antenna 108 (or alternatively, via external antenna 106). Module antenna 204 may be in communication with a transponder 214. In one exemplary embodiment, transponder 214 may be a 13.56 MHz transponder compliant with the ISO/IEC 14443 standard, and antenna 204 may be of the 13 MHz variety. The transponder 214 may be in communication with a transponder compatible modulator/demodulator 206 configured to receive the signal from transponder 214 and configured to modulate the signal into a format readable by any later connected circuitry. Further, modulator/demodulator 206 may be configured to format (e.g., demodulate) a signal received from the later connected circuitry in a format compatible with transponder 214 for transmitting to RFID reader 104 via antenna 204. For example, where transponder 114 is of the 13.56 MHz variety, modulator/demodulator 206 may be ISO/IEC 14443-2 compliant.
Modulator/demodulator 206 may be coupled to a protocol/sequence controller 208 for facilitating control of the authentication of the signal provided by RFID reader 104, and for facilitating control of the sending of the module 20 account number. In this regard, protocol/sequence controller 208 may be any suitable digital or logic driven circuitry capable of facilitating determination of the sequence of operation for the module 20 inner-circuitry. For example, protocol/sequence controller 208 may be configured to determine whether the signal provided by the RFID reader 104 is authenticated, and thereby providing to the RFID reader 104 the account number stored on module 20.
To authenticate the signal, the protocol/sequence controller 208 may be further in communication with authentication circuitry 210 for facilitating authentication of the signal provided by RFID reader 104. Authentication circuitry may be further in communication with a nonvolatile secure memory database 212. Secure memory database 212 may be any suitable elementary file system such as that defined by ISO/IEC 7816-4 or any other elementary file system allowing a lookup of data to be interpreted by the application on the chip. Database 212 may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Common database products that may be used to implement the databases include DB2 by IBM (White Plains, N.Y.), any of the database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or MSSQL by Microsoft Corporation (Redmond, Wash.), or any other database product. Database 212 may be organized in any suitable manner, including as data tables or lookup tables. Association of certain data may be accomplished through any data association technique known and practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in each of the manufacturer and retailer data tables. A “key field” partitions the database according to the high-level class of objects defined by the key field. For example, a certain class may be designated as a key field in both the first data table and the second data table, and the two data cables may then be merged on the basis of the class data in the key field. In this embodiment, the data corresponding to the key field in each of the merged data tables is preferably the same. However, data tables having similar, though not identical, data in the key fields may also be merged by using AGREP, for example.
The data received from the reader 104 or the database 212 may be used by protocol/sequence controller 208 for data analysis and used for management and control purposes, as well as security purposes. Authentication circuitry 216 may authenticate the signal provided by RFID reader 104 by association of the RFID signal to authentication keys stored on database 212. Authentication circuitry 216 may be in further communication with an encryption circuitry 216 which may encrypt or decrypt the reader 104 signal or the data (e.g., account number, user identifier, device identifier, etc.) returned from database 212 prior to transmitting the data. Encryption circuitry 216 may use keys stored on database 212 to perform encryption and/or decryption of signals sent to or from the RFID reader 104.
In addition, protocol/sequence controller 208 may be in communication with a database 212 for storing at least one of a module 20 account data, a unique module 20 identification code, user identification code, or transaction device identifier. Protocol/sequence controller 208 may be configured to retrieve the account number from database 212 as desired. Database 212 may be of the same configuration as database 212 described above. The account data and/or unique device identification code stored on database 212 may be encrypted prior to storage. Thus, where protocol/sequence controller 208 retrieves the account data, and or unique transaction device identifier, or the like, from database 212, the data may be encrypted by the encryption circuit 216 when being provided to RFID reader 104. Further, the data stored on database 212 may include, for example, an unencrypted unique module 20 identification code, a user identification ISO/IEC, Track 1 and 2 data, as well as specific application applets. The data may additionally be stored in the database 212 in Track 1/Track 2 format and may also be in Track 1/Track 2 format when provided to the reader 104.
In an exemplary operation, the module 20, is placed in proximity to reader 104 when the user wishes to conduct a transaction. The user simply waves the module 20 at a certain distance from the RF-based reader 104 until the reader 104 acknowledges that the information contained in the RFID module 20 has been received. The RF-based reader 104 then utilizes at least a portion of the information provided by module 20 (such as, a user's account number associated with the transaction device) to complete the transaction. The reader 104 may receive the account information from the module 20 and verify the account information authenticity prior to forwarding the account information to merchant system 130. Alternatively, the reader 104 may forward the account information to a merchant system 130 (via the merchant system POS 110) which may provide the account information to a transaction device issuer system (via network 112) for transaction completion. The merchant system 130 forwards the account information to an account issuer system, which may complete the transaction under issuer defined business as usual protocol Exemplary transaction completion methods and transaction device components are disclosed in the commonly owned U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002, incorporated herein in its entirety.
With reference to
In an exemplary embodiment, the laminated sheet 200 of 56 transaction device transporters 1 (including the RFID module) are suitably cut in half on a guillotine device, resulting in two half-sheets of 28 transporters 1 and module 20 combinations. The half-sheets may be loaded onto any conventional card punch machine which aligns the sheets to a die (x and y axes) using predetermined alignment marks 202 visible to the optics of the machine. The half-sheets are then fed under a punch to punch out the desired transporter device 1 and module 20 (called “transaction device combination”) shape. Particularly, a fixed distance feed is followed by another optic sensor search to stop the feed at the preprinted alignment mark, then the machine punches a row of four transaction device combinations out at one time, each punch being made along a preprinted alignment mark 202.
The preprinted alignment marks 202 indicate the perimeter boundaries of each transaction device transporter 1 to be cut from sheet 200. To separate each transaction device combination from the other, the cuts may typically be made along the preprinted alignment marks 202. In general, the preprinted alignment marks 202 are included in the sheet 200 as the writing is being added to the device material layers 10, 12. A typical sheet 200 may yield over 50 transaction device combinations (typically 56). In general, the shape of the transporter 1 is kept consistent by using a cutting apparatus having a preformed cutting dye formed in the desired shape. For example, the cutting dye may be formed in any shape, such as, for example, a traditional credit card shape as shown in Figure Alternatively, the shape is cut by using, for example, a laser or other cutting apparatus guided by any suitable preprinted alignment marks 202. The resulting individual transaction device combination may then be distributed for immediate activation and use.
Conventional methods of fabricating, manufacturing and cutting transaction devices, such as, credit cards, smart cards, RFID key fobs are well known. As such, one skilled in the art will understand the machinery and processes for fabricating, manufacturing, and/or cutting as they are included in the scope of this invention. Indeed, in the interest of brevity, conventional methods of fabricating, manufacturing and cutting transaction devices will not be discussed in detail herein. For instruction on manufacturing and fabricating a typical transaction card, see U.S. patent application Ser. No. 10/092,681, entitled “TRANSACTION CARD,” filed Mar. 7, 2002, and incorporated herein in its entirety.
While the foregoing describes an exemplary embodiment for the fabrication of transaction device combination, one skilled in the art will appreciate that any suitable method for incorporating text 30, logos 50, a magnetic stripe 40, a signature field, holographic foil 15 onto a substrate in accordance with accepted 160 standards, is within the scope of the present invention. Moreover, the holographic foil, RFID module 20, logo 50, magnetic stripe 40, signature field or any other compound may be included on the transporter 1 by any suitable means such as, for example, heat, pressure, adhesive, grooved and/or any combination thereof. In accordance with one embodiment, the text 30, logo 50, magnetic stripe 40, or holographic foil 15 may additionally be included in one surface use of the module 20 on a portion easily viewable by casual inspection.
As noted, various card manufacturers are producing RFID transaction devices that are irregularly shaped. As such, the irregular shaped transaction devices are typically cut using a cutting dye, or other method discussed above, which is designed to cut a sheet 200 into the desired transaction device shape. Consequently, manufacturers must often retrofit their machinery to cut the irregular shape. Returning now to
In accordance with one aspect of the invention, a credit card manufacturer may provide an irregularly shaped RFID transaction device 102 using a manufacturing process that is coextensive with the manufacturing process used for traditional transaction card 1 shapes. That is, the transaction devices 102 and transporters 1 may be manufactured, cut, perforated, or impressed without need to manufacture the devices independently of the transporter 1.
To assist in punching out or removing the transaction device 102, the RFID transaction device 102 preprinted alignment marks 502 may be pressed into the body of transporter 1 defined by preprinted alignment marks 202. As noted, the transporter 1 may be formed with one or more material layers, such as, for example, front layer 10, and back layer 12. The pressing action may result in indentations, or perforations being impressed into or through one or more layers of the multilayer transaction device. However, the perforations or indentations may not traverse completely through the card body. Instead, the perforations or indentations are impressed at such sufficient depth to permit the transaction device 102 to be removed from the transporter 1 with the application of minimal physical force. Thus, the perforations or indentations are typically provided along the transaction device 102 preprinted alignment marks 502 to facilitate the removal of the transaction device 102 from the transporter body. In one exemplary embodiment, the perforations and indentations, which may be used to form the outline of the transaction device 102, may also be arranged to form an outline of a shape, a picture, a security enhancing visage, or the like as desired by the manufacturer or system user. Suitable methods for providing perforations are disclosed in U.S. patent application Ser. No. 10/288,945, entitled “PERFORATED TRANSACTION CARD,” filed Nov. 6, 2002, incorporated herein by reference in its entirety.
In accordance with one exemplary embodiment of the present invention, the transaction device 102 outline (lines 502) is impressed within the outline of the transporter 1 drawn by alignment marks 202. For example, the preprinted sheet 200 of transaction device combinations is provided with the transporter 1 alignment marks 202 preprinted on the combination's front or rear surface 10, 12, and the transaction device outline 502 (“alignment marks 502”) is impressed within the alignment marks 502 (step 804).
Once the impression of the transaction device 102 is made in the transporter 1, the transaction device manufacturer may remove the transaction device 102 from the transporter 1 and provide the transaction device 102 to an end user. In one exemplary embodiment, the transaction device 102 is removed from the transporter 1 by the manufacturer (step 808) prior to providing the transaction device 102 to a user for device activation and device usage (step 810). In this way, the transaction device 102 may be provided to a user independent of the transporter 1. The user may use the transaction device 102 to complete a transaction by placing the transaction device 102 in proximity to the reader 104 as described above (step 830).
In an alternate embodiment of the invention, the RFID transaction device 102 is not removed by the manufacturer, but instead the RFID transaction device 102 is removed from the transporter 1 by the end user (step 812). For example, a transaction device provider may provide a user with the transaction device combination, including the transporter 1, and the transaction device 102, which includes RF module 20 (step 814). The user may then decide whether to remove the transaction device 102 from the transporter 1, which may be removed at the user's leisure (step 816). Should the user remove the transaction device 102, the user may additionally decide whether to remove module 20 (step 818). The user may remove the transaction device 102 to complete a transaction independent of the transporter 1 (step 830). The user may remove the transaction device 102 from transporter 1 by applying minimal physical force at the transaction device outline 502. The transaction device 102 may be removed manually or by cutting, tearing, or the like, (step 820). The user may use the transaction device 102 by placing the transaction device 102 in proximity to reader 104, as described above (step 830). The RFID module 20 may then provide transaction device account information to a RFID reader 104 for transaction completion.
The transaction device 102 may include an aperture 503, which may be formed by pressing the shape of the aperture 503 in the transporter 1 along alignment lines 502, perforating the transaction device 102 shape in the transporter 1 using any conventional machinery or method as described above. The aperture 503 may then be punched out or removed, wherein the portion of the transporter 1 within the aperture 503 is removed leaving an opening therein. The transaction device 102 may then be secured to a user's person or often used personal article by inserting one end of a tether-like means (not shown) through aperture 503 and securing the other end of the tether-like means to a transaction device 102 user person or often used personal article (e.g., keychain, fob chain, key ring, string, strap, belt, rope, etc.) which is ordinarily easily portable (step 820). The user may then use the transaction device 102 in similar manner as discussed above (step 830).
In another exemplary embodiment of the invention, user or transaction device manufacturer may remove the RFID module 20 from the transporter 1 to enable use of the module 20 to complete a transaction independent of any other portion of the transporter 1 or the transaction device 102 (step 822). In this instance, the transaction device issuer may configure the stamping machinery to preprint alignment marks which closely mimic the shape of the module 20. As shown in
In one exemplary embodiment, the user may use the module 20 with any portable form factor configured to secure the module 20 during transaction completion (step 824). Preferably, the form factor is embodied in an article frequently used by the module user. For example, the module 20 may be secured to any portable apparatus which may be manually transported by the module 20 user, and which may be used to facilitate manually presenting the module 20 to a RFID reader 104 for transaction completion. A suitable portable apparatus may include means for securing the module 20 to the apparatus.
In yet another exemplary embodiment, as shown in
For example, in the embodiment shown, carrier 400 is of similar shape as the module 20 depicted in
Carrier 400 may further include an aperture 412 in at least one end of the door 404, 406. The aperture 412 may be used in similar manner as with aperture 503 of
Alternatively, the carrier may be secured to the apparatus, such as cell phone 300 using any suitable attachment method. For example, the carrier 400 including the module 20 may be fastened to the cell phone 300 using any attachment means, such as for example, screws, rivets, bonding compound, glue or especially made fastening construction operable to hold the carrier 400 in physical communication with the cell phone 1402. For example, one suitable attachment method may be the fastener described in U.S. Pat. No. 6,669,263, entitled “Attachment Device,” which issued Dec. 30, 2003, to Asai, and U.S. Pat. No. 6,643,076, entitled “Attachment Device,” which issued Nov. 4, 2003, to Montage, hereby incorporated by reference.
Returning now to
The transporter 1 may be configured with a magnetic stripe 40 using any conventional method for attaching magnetic stripes as is commonly known. The magnetic stripe 40 may be compliant to International Standard Setting Organization standards for the shape, location and the format of the data stored and retrieved from the magnetic stripe 40. The magnetic stripe 40 may be configured to include account data (e.g., account, user, or transaction device identifier, code or number) stored thereon in Track 1/Track 2 ISO magnetic stripe standard format. As such, the magnetic stripe 40 may be configured to be readable by any conventional magnetic stripe reader as is found in the art. Consequently, the user may use the transaction device combination 600 in similar manner as a traditional credit, debit, DDA, prepaid card, an the like. For example, the user may present the transaction device combination 600 to a magnetic stripe reader, which may retrieve the magnetic stripe 40 data and forward the data to an account issuer for transaction completion. Conventional methods for completing a transaction are well known and will not be repeated for brevity.
In one conventional construction of transaction device combination 600, the magnetic stripe 40 may be such that a portion of the alignment lines 502, including the impressed outline of the transaction device 102 may intersect the magnetic stripe 40, as shown in
The preceding detailed description of exemplary embodiments of the invention makes reference to the accompanying drawings, which show the exemplary embodiment by way of illustration. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the invention. Thus, the preceding detailed description is presented for purposes of illustration only and not of limitation, and the scope of the invention is defined solely by the appended claims and their legal equivalents when properly read in light of the preceding description. For example, the steps recited in any of the method or process claims may be executed in any order and are not limited to the order presented. In addition, although the present description illustrates the invention as embodied in a card, key fob, or cellular phone, the invention is not so limited. That is, the present invention contemplates the incorporation of the inventive technology into a form factor presentable by hand.
This invention is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002 (which itself claims priority to U.S. Provisional Patent Application No. 60/304,216, filed Jul. 10, 2001). This invention is also a continuation-in-part of and claims priority to U.S. patent application Ser. No. 10/340,352, entitled “SYSTEM AND METHOD FOR INCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Jan. 10, 2003 (which itself claims priority to U.S. Provisional Patent Application No. 60/396,577, filed Jul. 16, 2002). This invention is also a continuation-in-part of U.S. patent application Ser. No. 10/394,914, entitled “TRANSACTION CARD,” filed Mar. 21, 2003 (which itself claims priority to U.S. Provisional Patent Application No. 60/153,112, filed Sep. 7, 1999, U.S. Provisional Patent Application No. 60/167,405, filed Nov. 24, 1999, and to U.S. Provisional Patent Application No. 60/171,689, filed Dec. 21, 1999), and is also a continuation-in-part of U.S. Patent Application No. 10/302,658, entitled “TRANSACTION CARD WITH DUAL IC CHIPS,” filed Nov. 22, 2002 now abandoned, both of which claim priority to U.S. patent application Ser. No. 10/092,681, entitled “TRANSACTION CARD,” filed Mar. 7, 2002 (which itself claims priority to U.S. Provisional Patent Application No. 60/153,112, filed Sep. 7, 1999, U.S. Provisional Patent Application No. 60/160,519, filed Oct. 20, 1999, U.S. Provisional Patent Application No. 60/167,405, filed Nov. 24, 1999, and to U.S. Provisional Patent Application No. 60/171,689, filed Dec. 21, 1999), which claims priority to U.S. patent application Ser. No. 10/062,106, entitled “TRANSACTION CARD,” filed Jan. 31, 2002, the entire contents of which are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| D061466 | Foltz | Sep 1922 | S |
| 3536894 | Travioli | Oct 1970 | A |
| 3573731 | Schwend | Apr 1971 | A |
| 3725647 | Retzky | Apr 1973 | A |
| 3763356 | Berler | Oct 1973 | A |
| 3829662 | Furahashi | Aug 1974 | A |
| 3838252 | Hynes et al. | Sep 1974 | A |
| 3873813 | Lahr et al. | Mar 1975 | A |
| 3894756 | Ward | Jul 1975 | A |
| 3955295 | Mayer | May 1976 | A |
| 4044231 | Beck et al. | Aug 1977 | A |
| 4058839 | Darjany | Nov 1977 | A |
| 4119361 | Greenaway | Oct 1978 | A |
| 4202491 | Suzuki | May 1980 | A |
| 4303904 | Chasek | Dec 1981 | A |
| 4361757 | Ehrat | Nov 1982 | A |
| D270546 | Malmberg | Sep 1983 | S |
| 4436991 | Albert et al. | Mar 1984 | A |
| 4475308 | Heise et al. | Oct 1984 | A |
| 4504084 | Jauch | Mar 1985 | A |
| D280214 | Opel | Aug 1985 | S |
| 4538059 | Rudland | Aug 1985 | A |
| 4547002 | Colgate, Jr. | Oct 1985 | A |
| 4563024 | Blyth | Jan 1986 | A |
| 4583766 | Wessel | Apr 1986 | A |
| 4593936 | Opel | Jun 1986 | A |
| 4597814 | Colgate, Jr. | Jul 1986 | A |
| 4639765 | d'Hont | Jan 1987 | A |
| 4641017 | Lopata | Feb 1987 | A |
| 4672021 | Blumel et al. | Jun 1987 | A |
| 4684795 | Colgate, Jr. | Aug 1987 | A |
| 4692394 | Drexler | Sep 1987 | A |
| 4694148 | Diekemper et al. | Sep 1987 | A |
| 4697073 | Hara | Sep 1987 | A |
| 4711690 | Haghiri-Tehrani | Dec 1987 | A |
| 4739328 | Koelle et al. | Apr 1988 | A |
| 4779898 | Berning et al. | Oct 1988 | A |
| 4794142 | Alberts et al. | Dec 1988 | A |
| 4795894 | Sugimoto et al. | Jan 1989 | A |
| 4852911 | Hoppe | Aug 1989 | A |
| 4863819 | Drexler et al. | Sep 1989 | A |
| 4889366 | Fabbiani | Dec 1989 | A |
| D310386 | Michels et al. | Sep 1990 | S |
| 4961142 | Elliott et al. | Oct 1990 | A |
| 5010243 | Fukushima et al. | Apr 1991 | A |
| 5023782 | Lutz et al. | Jun 1991 | A |
| 5053774 | Schuermann et al. | Oct 1991 | A |
| 5099226 | Andrews | Mar 1992 | A |
| 5101200 | Swett | Mar 1992 | A |
| 5106125 | Antes | Apr 1992 | A |
| 5111033 | Fujita et al. | May 1992 | A |
| 5142383 | Mallik | Aug 1992 | A |
| 5197140 | Balmer | Mar 1993 | A |
| 5212777 | Gove et al. | May 1993 | A |
| 5217844 | Fukushima et al. | Jun 1993 | A |
| 5221838 | Gutman et al. | Jun 1993 | A |
| 5222282 | Sukonnik et al. | Jun 1993 | A |
| 5226989 | Sukonnik | Jul 1993 | A |
| 5234624 | Bauer et al. | Aug 1993 | A |
| 5239654 | Ing-Simmons et al. | Aug 1993 | A |
| 5247304 | d'Hont | Sep 1993 | A |
| 5251937 | Ojster | Oct 1993 | A |
| 5256473 | Kotani et al. | Oct 1993 | A |
| 5272326 | Fujita et al. | Dec 1993 | A |
| 5274392 | d'Hont | Dec 1993 | A |
| 5285100 | Byatt | Feb 1994 | A |
| 5300764 | Hoshino et al. | Apr 1994 | A |
| 5304789 | Lob et al. | Apr 1994 | A |
| 5305002 | Holodak et al. | Apr 1994 | A |
| 5329617 | Asal | Jul 1994 | A |
| 5331138 | Saroya | Jul 1994 | A |
| 5339447 | Balmer | Aug 1994 | A |
| 5349357 | Schurmann et al. | Sep 1994 | A |
| 5351052 | d'Hont et al. | Sep 1994 | A |
| 5351142 | Cueli | Sep 1994 | A |
| 5355411 | MacDonald | Oct 1994 | A |
| 5371896 | Gove et al. | Dec 1994 | A |
| 5373303 | d'Hont | Dec 1994 | A |
| 5383687 | Suess et al. | Jan 1995 | A |
| 5407893 | Koshizuka et al. | Apr 1995 | A |
| 5408243 | d'Hont | Apr 1995 | A |
| 5410142 | Tsuboi et al. | Apr 1995 | A |
| 5410649 | Gove | Apr 1995 | A |
| 5428363 | d'Hont et al. | Jun 1995 | A |
| 5453747 | d'Hont et al. | Sep 1995 | A |
| 5471592 | Gove et al. | Nov 1995 | A |
| 5485510 | Colbert | Jan 1996 | A |
| 5488376 | Hurta et al. | Jan 1996 | A |
| 5489411 | Jha et al. | Feb 1996 | A |
| 5489908 | Orthmann et al. | Feb 1996 | A |
| 5490079 | Sharpe et al. | Feb 1996 | A |
| 5491483 | d'Hont | Feb 1996 | A |
| 5491484 | Schuermann | Feb 1996 | A |
| 5491715 | Flaxl | Feb 1996 | A |
| 5493312 | Knebelkamp | Feb 1996 | A |
| 5497121 | d'Hont | Mar 1996 | A |
| 5500651 | Schuermann | Mar 1996 | A |
| 5513525 | Schurmann | May 1996 | A |
| 5514860 | Berson | May 1996 | A |
| 5516153 | Kaule | May 1996 | A |
| 5518810 | Nishihara et al. | May 1996 | A |
| 5519381 | Marsh et al. | May 1996 | A |
| 5522083 | Gove et al. | May 1996 | A |
| 5525992 | Froschermeier | Jun 1996 | A |
| 5525994 | Hurta et al. | Jun 1996 | A |
| 5530232 | Taylor | Jun 1996 | A |
| 5541604 | Meier | Jul 1996 | A |
| 5543798 | Schuermann | Aug 1996 | A |
| 5544246 | Mandelbaum et al. | Aug 1996 | A |
| 5548291 | Meier et al. | Aug 1996 | A |
| 5550536 | Flaxl | Aug 1996 | A |
| 5550548 | Schuermann | Aug 1996 | A |
| 5552789 | Schuermann | Sep 1996 | A |
| 5557279 | d'Hont | Sep 1996 | A |
| 5557516 | Hogan | Sep 1996 | A |
| 5561430 | Knebelkamp | Oct 1996 | A |
| 5563582 | d'Hont | Oct 1996 | A |
| 5569187 | Kaiser | Oct 1996 | A |
| 5572226 | Tuttle | Nov 1996 | A |
| 5577109 | Stimson et al. | Nov 1996 | A |
| 5581630 | Bonneau, Jr. | Dec 1996 | A |
| 5592150 | d'Hont | Jan 1997 | A |
| 5592405 | Gove et al. | Jan 1997 | A |
| 5594233 | Kenneth et al. | Jan 1997 | A |
| 5594448 | d'Hont | Jan 1997 | A |
| 5597534 | Kaiser | Jan 1997 | A |
| 5600175 | Orthmann | Feb 1997 | A |
| 5602538 | Orthmann et al. | Feb 1997 | A |
| 5602919 | Hurta et al. | Feb 1997 | A |
| 5604342 | Fujioka | Feb 1997 | A |
| 5606520 | Gove et al. | Feb 1997 | A |
| 5606594 | Register et al. | Feb 1997 | A |
| 5607522 | McDonnell | Mar 1997 | A |
| 5608203 | Finkelstein et al. | Mar 1997 | A |
| 5608406 | Eberth et al. | Mar 1997 | A |
| 5608778 | Partridge, III | Mar 1997 | A |
| 5613146 | Gove et al. | Mar 1997 | A |
| 5619207 | d'Hont | Apr 1997 | A |
| 5621396 | Flaxl | Apr 1997 | A |
| 5621411 | Hagl et al. | Apr 1997 | A |
| 5621412 | Sharpe et al. | Apr 1997 | A |
| 5625366 | d'Hont | Apr 1997 | A |
| 5625370 | d'Hont | Apr 1997 | A |
| 5625695 | M'Raihi et al. | Apr 1997 | A |
| 5629981 | Nerlikar | May 1997 | A |
| 5638080 | Orthmann et al. | Jun 1997 | A |
| 5640002 | Ruppert et al. | Jun 1997 | A |
| 5646607 | Schurmann et al. | Jul 1997 | A |
| 5657388 | Weiss | Aug 1997 | A |
| 5660319 | Falcone et al. | Aug 1997 | A |
| 5673106 | Thompson | Sep 1997 | A |
| D384971 | Kawan | Oct 1997 | S |
| 5675342 | Sharpe | Oct 1997 | A |
| 5686920 | Hurta et al. | Nov 1997 | A |
| 5691731 | vanErven | Nov 1997 | A |
| 5692132 | Hogan | Nov 1997 | A |
| 5696913 | Gove et al. | Dec 1997 | A |
| 5697649 | Dames et al. | Dec 1997 | A |
| 5698837 | Furuta | Dec 1997 | A |
| 5699528 | Hogan | Dec 1997 | A |
| 5700037 | Keller | Dec 1997 | A |
| 5701127 | Sharpe | Dec 1997 | A |
| 5704046 | Hogan | Dec 1997 | A |
| 5705798 | Tarbox | Jan 1998 | A |
| 5720500 | Okazaki et al. | Feb 1998 | A |
| 5721781 | Deo et al. | Feb 1998 | A |
| 5729053 | Orthmann | Mar 1998 | A |
| 5729236 | Flaxl | Mar 1998 | A |
| 5731957 | Brennan | Mar 1998 | A |
| 5732579 | d'Hont et al. | Mar 1998 | A |
| 5748137 | d'Hont | May 1998 | A |
| 5748737 | Daggar | May 1998 | A |
| 5758195 | Balmer | May 1998 | A |
| 5761306 | Lewis | Jun 1998 | A |
| 5761493 | Blakeley et al. | Jun 1998 | A |
| 5768609 | Gove et al. | Jun 1998 | A |
| 5769457 | Warther | Jun 1998 | A |
| 5774882 | Keen et al. | Jun 1998 | A |
| 5777903 | Piosenka | Jul 1998 | A |
| 5778067 | Jones et al. | Jul 1998 | A |
| 5785680 | Niezink et al. | Jul 1998 | A |
| 5786587 | Colgate, Jr. | Jul 1998 | A |
| 5789733 | Jachimowicz et al. | Aug 1998 | A |
| 5792337 | Padovani et al. | Aug 1998 | A |
| 5793324 | Aslanidis et al. | Aug 1998 | A |
| 5794095 | Thompson | Aug 1998 | A |
| 5797060 | Thompson | Aug 1998 | A |
| 5797085 | Beuk et al. | Aug 1998 | A |
| 5797133 | Jones et al. | Aug 1998 | A |
| 5798709 | Flaxl | Aug 1998 | A |
| 5808758 | Solmsdorf | Sep 1998 | A |
| 5809142 | Hurta et al. | Sep 1998 | A |
| 5809288 | Balmer | Sep 1998 | A |
| 5809633 | Mundigl et al. | Sep 1998 | A |
| 5825007 | Jesadanont | Oct 1998 | A |
| 5825302 | Stafford | Oct 1998 | A |
| 5826077 | Blakeley et al. | Oct 1998 | A |
| 5828044 | Jun et al. | Oct 1998 | A |
| 5834756 | Gutman et al. | Nov 1998 | A |
| 5841364 | Hagl et al. | Nov 1998 | A |
| 5842088 | Thompson | Nov 1998 | A |
| 5844218 | Kawan et al. | Dec 1998 | A |
| 5844230 | Lalonde | Dec 1998 | A |
| 5845267 | Ronen | Dec 1998 | A |
| 5851149 | Xidos et al. | Dec 1998 | A |
| 5854891 | Postlewaite et al. | Dec 1998 | A |
| 5856048 | Tahara et al. | Jan 1999 | A |
| 5857709 | Chock | Jan 1999 | A |
| 5858006 | Van der AA et al. | Jan 1999 | A |
| 5859779 | Giordano et al. | Jan 1999 | A |
| 5864323 | Berthon | Jan 1999 | A |
| 5867100 | d'Hont | Feb 1999 | A |
| 5870031 | Kaiser et al. | Feb 1999 | A |
| 5870915 | d'Hont | Feb 1999 | A |
| D406861 | Leedy, Jr. | Mar 1999 | S |
| 5878215 | Kling et al. | Mar 1999 | A |
| 5878403 | DeFrancesco et al. | Mar 1999 | A |
| 5880675 | Trautner | Mar 1999 | A |
| 5881272 | Balmer | Mar 1999 | A |
| 5886333 | Miyake | Mar 1999 | A |
| 5887266 | Heinonen et al. | Mar 1999 | A |
| 5890137 | Koreeda | Mar 1999 | A |
| D408054 | Leedy, Jr. | Apr 1999 | S |
| 5898783 | Rohrbach | Apr 1999 | A |
| 5900954 | Katz et al. | May 1999 | A |
| 5903830 | Joao et al. | May 1999 | A |
| 5905798 | Nerlikar et al. | May 1999 | A |
| 5912678 | Saxena et al. | Jun 1999 | A |
| 5920628 | Indeck et al. | Jul 1999 | A |
| 5928788 | Riedl | Jul 1999 | A |
| 5929801 | Aslanidis et al. | Jul 1999 | A |
| 5931917 | Nguyen et al. | Aug 1999 | A |
| 5932870 | Berson | Aug 1999 | A |
| 5933624 | Balmer | Aug 1999 | A |
| 5943624 | Fox et al. | Aug 1999 | A |
| 5948116 | Aslanidis et al. | Sep 1999 | A |
| 5953512 | Cai et al. | Sep 1999 | A |
| 5955717 | Vanstone | Sep 1999 | A |
| 5955969 | d'Hont | Sep 1999 | A |
| 5956024 | Strickland et al. | Sep 1999 | A |
| 5963924 | Williams et al. | Oct 1999 | A |
| 5970148 | Meier | Oct 1999 | A |
| 5971276 | Sano et al. | Oct 1999 | A |
| RE36365 | Levine et al. | Nov 1999 | E |
| 5978348 | Tamura | Nov 1999 | A |
| 5978840 | Nguyen et al. | Nov 1999 | A |
| 5983208 | Haller | Nov 1999 | A |
| 5987140 | Rowney et al. | Nov 1999 | A |
| 5987155 | Dunn et al. | Nov 1999 | A |
| 5987498 | Athing et al. | Nov 1999 | A |
| 5989950 | Wu | Nov 1999 | A |
| 5991608 | Leyten | Nov 1999 | A |
| 5991750 | Watson | Nov 1999 | A |
| 5996076 | Rowney et al. | Nov 1999 | A |
| 6002438 | Hocevar et al. | Dec 1999 | A |
| 6002767 | Kramer | Dec 1999 | A |
| 6003014 | Lee et al. | Dec 1999 | A |
| 6005942 | Chan et al. | Dec 1999 | A |
| 6006216 | Griffin et al. | Dec 1999 | A |
| 6012049 | Kawan | Jan 2000 | A |
| 6014645 | Cunningham | Jan 2000 | A |
| 6018717 | Lee et al. | Jan 2000 | A |
| 6024286 | Bradley et al. | Feb 2000 | A |
| 6029149 | Dykstra et al. | Feb 2000 | A |
| 6038584 | Balmer | Mar 2000 | A |
| 6047888 | Dethloff | Apr 2000 | A |
| 6052675 | Checchio | Apr 2000 | A |
| 6064320 | d'Hont et al. | May 2000 | A |
| 6070003 | Gove et al. | May 2000 | A |
| 6072870 | Nguyen et al. | Jun 2000 | A |
| 6073840 | Marion | Jun 2000 | A |
| 6078888 | Johnson, Jr. | Jun 2000 | A |
| RE36788 | Mansvelt et al. | Jul 2000 | E |
| 6088686 | Walker et al. | Jul 2000 | A |
| 6092057 | Zimmerman et al. | Jul 2000 | A |
| 6101174 | Langston | Aug 2000 | A |
| 6102162 | Teicher | Aug 2000 | A |
| 6102672 | Woollenweber et al. | Aug 2000 | A |
| 6105008 | Davis et al. | Aug 2000 | A |
| 6105013 | Curry et al. | Aug 2000 | A |
| 6105865 | Hardesty | Aug 2000 | A |
| 6109525 | Blomqvist et al. | Aug 2000 | A |
| 6112152 | Tuttle | Aug 2000 | A |
| 6115360 | Quay et al. | Sep 2000 | A |
| 6116423 | Troxtell, Jr. et al. | Sep 2000 | A |
| 6116505 | Withrow | Sep 2000 | A |
| 6118189 | Flaxl | Sep 2000 | A |
| 6121544 | Petsinger | Sep 2000 | A |
| 6123223 | Watkins | Sep 2000 | A |
| 6129274 | Suzuki | Oct 2000 | A |
| 6133834 | Eberth et al. | Oct 2000 | A |
| 6138913 | Cyr et al. | Oct 2000 | A |
| 6141651 | Riley et al. | Oct 2000 | A |
| 6155168 | Sakamoto | Dec 2000 | A |
| 6167236 | Kaiser et al. | Dec 2000 | A |
| 6177860 | Cromer et al. | Jan 2001 | B1 |
| 6179205 | Sloan | Jan 2001 | B1 |
| 6179206 | Matsumori | Jan 2001 | B1 |
| 6188994 | Egendorf | Feb 2001 | B1 |
| 6192255 | Lewis et al. | Feb 2001 | B1 |
| 6196465 | Awano | Mar 2001 | B1 |
| 6198728 | Hulyalkar et al. | Mar 2001 | B1 |
| 6198875 | Edenson et al. | Mar 2001 | B1 |
| 6202927 | Bashan et al. | Mar 2001 | B1 |
| 6205151 | Quay et al. | Mar 2001 | B1 |
| 6206293 | Gutman et al. | Mar 2001 | B1 |
| 6215437 | Schurmann et al. | Apr 2001 | B1 |
| 6216219 | Cai et al. | Apr 2001 | B1 |
| 6219439 | Burger | Apr 2001 | B1 |
| D442627 | Webb et al. | May 2001 | S |
| D442629 | Webb et al. | May 2001 | S |
| 6223984 | Renner et al. | May 2001 | B1 |
| 6226382 | M'Raihi et al. | May 2001 | B1 |
| 6230270 | Laczko, Sr. | May 2001 | B1 |
| 6232917 | Baumer et al. | May 2001 | B1 |
| 6233683 | Chan et al. | May 2001 | B1 |
| 6237848 | Everett | May 2001 | B1 |
| 6239675 | Flaxl | May 2001 | B1 |
| 6240187 | Lewis | May 2001 | B1 |
| 6248314 | Nakashimada et al. | Jun 2001 | B1 |
| 6255031 | Yao et al. | Jul 2001 | B1 |
| 6257486 | Teicher et al. | Jul 2001 | B1 |
| 6259769 | Page | Jul 2001 | B1 |
| 6260026 | Tomida et al. | Jul 2001 | B1 |
| 6260088 | Gove et al. | Jul 2001 | B1 |
| 6264106 | Bridgelall | Jul 2001 | B1 |
| 6266754 | Laczko, Sr. et al. | Jul 2001 | B1 |
| 6273335 | Sloan | Aug 2001 | B1 |
| 6277232 | Wang et al. | Aug 2001 | B1 |
| 6282522 | Davis et al. | Aug 2001 | B1 |
| D447515 | Faenza, Jr. et al. | Sep 2001 | S |
| 6286763 | Reynolds et al. | Sep 2001 | B1 |
| 6289324 | Kawan | Sep 2001 | B1 |
| 6290137 | Kiekhaefer | Sep 2001 | B1 |
| 6296188 | Kiekhaefer | Oct 2001 | B1 |
| 6315193 | Hogan | Nov 2001 | B1 |
| 6317721 | Hurta et al. | Nov 2001 | B1 |
| 6318636 | Reynolds et al. | Nov 2001 | B1 |
| 6323566 | Meier | Nov 2001 | B1 |
| 6325285 | Baratelli | Dec 2001 | B1 |
| 6326934 | Kinzie | Dec 2001 | B1 |
| 6342844 | Rozin | Jan 2002 | B1 |
| 6364208 | Stanford et al. | Apr 2002 | B1 |
| 6367011 | Lee et al. | Apr 2002 | B1 |
| 6374245 | Park | Apr 2002 | B1 |
| 6377034 | Ivanov | Apr 2002 | B1 |
| 6388533 | Swoboda | May 2002 | B1 |
| 6390375 | Kayanakis | May 2002 | B1 |
| 6400272 | Holtzman et al. | Jun 2002 | B1 |
| 6402028 | Graham, Jr. et al. | Jun 2002 | B1 |
| 6411611 | van der Tuijn | Jun 2002 | B1 |
| 6415978 | McAllister | Jul 2002 | B1 |
| 6422464 | Terranova | Jul 2002 | B1 |
| 6424029 | Giesler | Jul 2002 | B1 |
| 6442532 | Kawan | Aug 2002 | B1 |
| 6457996 | Shih | Oct 2002 | B1 |
| 6466804 | Pecen et al. | Oct 2002 | B1 |
| 6471127 | Pentz et al. | Oct 2002 | B1 |
| 6473500 | Risafi et al. | Oct 2002 | B1 |
| 6480100 | Frieden et al. | Nov 2002 | B1 |
| 6480101 | Kelly et al. | Nov 2002 | B1 |
| 6481621 | Herrendoerfer et al. | Nov 2002 | B1 |
| 6481632 | Wentker et al. | Nov 2002 | B1 |
| 6484937 | Devaux et al. | Nov 2002 | B1 |
| 6490443 | Freeny, Jr. | Dec 2002 | B1 |
| 6491229 | Berney | Dec 2002 | B1 |
| 6494380 | Jarosz | Dec 2002 | B1 |
| 6507762 | Amro et al. | Jan 2003 | B1 |
| 6510983 | Horowitz et al. | Jan 2003 | B1 |
| 6510998 | Stanford et al. | Jan 2003 | B1 |
| 6513015 | Ogasawara | Jan 2003 | B1 |
| 6529880 | McKeen et al. | Mar 2003 | B1 |
| 6535726 | Johnson | Mar 2003 | B1 |
| 6546373 | Cerra | Apr 2003 | B1 |
| 6547133 | DeVries, Jr. et al. | Apr 2003 | B1 |
| 6549912 | Chen | Apr 2003 | B1 |
| 6560581 | Fox et al. | May 2003 | B1 |
| 6577229 | Bonneau et al. | Jun 2003 | B1 |
| 6578768 | Binder et al. | Jun 2003 | B1 |
| 6581839 | Lasch et al. | Jun 2003 | B1 |
| 6588660 | Buescher et al. | Jul 2003 | B1 |
| 6589119 | Orus et al. | Jul 2003 | B1 |
| 6608995 | Kawasaki et al. | Aug 2003 | B1 |
| 6609655 | Harrell | Aug 2003 | B1 |
| 6626356 | Davenport et al. | Sep 2003 | B1 |
| 6628961 | Ho et al. | Sep 2003 | B1 |
| 6650887 | McGregor et al. | Nov 2003 | B1 |
| 6665405 | Lenstra | Dec 2003 | B1 |
| 6674786 | Nakamura et al. | Jan 2004 | B1 |
| 6679427 | Kuroiwa | Jan 2004 | B1 |
| 6684269 | Wagner | Jan 2004 | B1 |
| 6687714 | Kogen et al. | Feb 2004 | B1 |
| 6690930 | Dupre | Feb 2004 | B1 |
| 6693513 | Tuttle | Feb 2004 | B1 |
| 6705530 | Kiekhaefer | Mar 2004 | B1 |
| 6711262 | Watanen | Mar 2004 | B1 |
| 6732936 | Kiekhaefer | May 2004 | B1 |
| 6742120 | Markakis et al. | May 2004 | B1 |
| 6760581 | Dutta | Jul 2004 | B1 |
| 6789012 | Childs et al. | Sep 2004 | B1 |
| 20010013542 | Horowitz et al. | Aug 2001 | A1 |
| 20010024157 | Hansmann et al. | Sep 2001 | A1 |
| 20010034565 | Leatherman | Oct 2001 | A1 |
| 20010039617 | Buhrlen et al. | Nov 2001 | A1 |
| 20020011519 | Shults | Jan 2002 | A1 |
| 20020028704 | Bloomfield et al. | Mar 2002 | A1 |
| 20020035548 | Hogan et al. | Mar 2002 | A1 |
| 20020052839 | Takatori | May 2002 | A1 |
| 20020062284 | Kawan | May 2002 | A1 |
| 20020074398 | Lancos et al. | Jun 2002 | A1 |
| 20020077837 | Krueger et al. | Jun 2002 | A1 |
| 20020077895 | Howell | Jun 2002 | A1 |
| 20020077992 | Tobin | Jun 2002 | A1 |
| 20020079367 | Montani | Jun 2002 | A1 |
| 20020092914 | Pentz et al. | Jul 2002 | A1 |
| 20020095343 | Barton et al. | Jul 2002 | A1 |
| 20020095389 | Gaines | Jul 2002 | A1 |
| 20020095587 | Doyle et al. | Jul 2002 | A1 |
| 20020097144 | Collins et al. | Jul 2002 | A1 |
| 20020107007 | Gerson | Aug 2002 | A1 |
| 20020107742 | Magill | Aug 2002 | A1 |
| 20020109580 | Shreve et al. | Aug 2002 | A1 |
| 20020111210 | Luciano, Jr. et al. | Aug 2002 | A1 |
| 20020113082 | Leatherman et al. | Aug 2002 | A1 |
| 20020116274 | Hind et al. | Aug 2002 | A1 |
| 20020120584 | Hogan et al. | Aug 2002 | A1 |
| 20020126010 | Trimble et al. | Sep 2002 | A1 |
| 20020131567 | Maginas | Sep 2002 | A1 |
| 20020138438 | Bardwell | Sep 2002 | A1 |
| 20020140542 | Prokoski et al. | Oct 2002 | A1 |
| 20020145043 | Challa et al. | Oct 2002 | A1 |
| 20020147913 | Lun Yip | Oct 2002 | A1 |
| 20020148892 | Bardwell | Oct 2002 | A1 |
| 20020152123 | Giordano et al. | Oct 2002 | A1 |
| 20020166891 | Stoutenburg et al. | Nov 2002 | A1 |
| 20020176522 | Fan | Nov 2002 | A1 |
| 20020178063 | Gravelle et al. | Nov 2002 | A1 |
| 20020178369 | Black | Nov 2002 | A1 |
| 20020185543 | Pentz et al. | Dec 2002 | A1 |
| 20020188501 | Lefkowith | Dec 2002 | A1 |
| 20020190125 | Stockhammer | Dec 2002 | A1 |
| 20020194303 | Stuila et al. | Dec 2002 | A1 |
| 20020194503 | Faith et al. | Dec 2002 | A1 |
| 20020196963 | Bardwell | Dec 2002 | A1 |
| 20030009382 | D'Arbelott et al. | Jan 2003 | A1 |
| 20030014307 | Heng | Jan 2003 | A1 |
| 20030014357 | Chrisekos et al. | Jan 2003 | A1 |
| 20030014891 | Nelms et al. | Jan 2003 | A1 |
| 20030018532 | Dudek et al. | Jan 2003 | A1 |
| 20030025600 | Blanchard | Feb 2003 | A1 |
| 20030046228 | Berney | Mar 2003 | A1 |
| 20030057278 | Wong | Mar 2003 | A1 |
| 20030069828 | Blazey et al. | Apr 2003 | A1 |
| 20030069846 | Marcon | Apr 2003 | A1 |
| 20030120554 | Hogan et al. | Jun 2003 | A1 |
| 20030121969 | Wankmueller | Jul 2003 | A1 |
| 20030132284 | Reynolds et al. | Jul 2003 | A1 |
| 20030140228 | Binder | Jul 2003 | A1 |
| 20030163699 | Pailles et al. | Aug 2003 | A1 |
| 20030167207 | Berardi et al. | Sep 2003 | A1 |
| 20030177347 | Schneier et al. | Sep 2003 | A1 |
| 20030183689 | Swift et al. | Oct 2003 | A1 |
| 20030183699 | Masui | Oct 2003 | A1 |
| 20030187786 | Swift et al. | Oct 2003 | A1 |
| 20030187787 | Freund | Oct 2003 | A1 |
| 20030187790 | Swift et al. | Oct 2003 | A1 |
| 20030187796 | Swift et al. | Oct 2003 | A1 |
| 20030195842 | Reece | Oct 2003 | A1 |
| 20030195843 | Matsuda et al. | Oct 2003 | A1 |
| 20030200184 | Dominguez et al. | Oct 2003 | A1 |
| 20030218066 | Fernandes et al. | Nov 2003 | A1 |
| 20030220876 | Burger et al. | Nov 2003 | A1 |
| 20030222153 | Pentz et al. | Dec 2003 | A1 |
| 20030225623 | Wankmueller | Dec 2003 | A1 |
| 20030225713 | Atkinson et al. | Dec 2003 | A1 |
| 20030227550 | Manico et al. | Dec 2003 | A1 |
| 20030233334 | Smith | Dec 2003 | A1 |
| 20040010462 | Moon et al. | Jan 2004 | A1 |
| 20040015451 | Sahota et al. | Jan 2004 | A1 |
| 20040029569 | Khan et al. | Feb 2004 | A1 |
| 20040039860 | Mills et al. | Feb 2004 | A1 |
| 20040139021 | Reed et al. | Jul 2004 | A1 |
| Number | Date | Country |
|---|---|---|
| 689070 | Aug 1997 | CH |
| 689680 | Aug 1999 | CH |
| 2847756 | May 1980 | DE |
| 0181770 | May 1986 | EP |
| 0343829 | Nov 1989 | EP |
| 0354817 | Feb 1990 | EP |
| 0 358 525 | Mar 1990 | EP |
| 0368570 | May 1990 | EP |
| 0388090 | Sep 1990 | EP |
| 0 424 726 | Oct 1990 | EP |
| 0403134 | Dec 1990 | EP |
| 0411602 | Feb 1991 | EP |
| 0473998 | Mar 1992 | EP |
| 0481388 | Apr 1992 | EP |
| 0531605 | Mar 1993 | EP |
| 0552047 | Jul 1993 | EP |
| 0560318 | Sep 1993 | EP |
| 0568185 | Nov 1993 | EP |
| 0657297 | Jun 1995 | EP |
| 0721850 | Jul 1996 | EP |
| 0780839 | Jun 1997 | EP |
| 0789316 | Aug 1997 | EP |
| 0866420 | Sep 1998 | EP |
| 0894620 | Feb 1999 | EP |
| 0916519 | May 1999 | EP |
| 0 933 717 | Aug 1999 | EP |
| 0 956 818 | Nov 1999 | EP |
| 0 959 440 | Nov 1999 | EP |
| 0 984 404 | Mar 2000 | EP |
| 1 016 947 | Jul 2000 | EP |
| 1 039 403 | Sep 2000 | EP |
| 1 104 909 | Jun 2001 | EP |
| 1 113 387 | Jul 2001 | EP |
| 1199684 | Apr 2002 | EP |
| 1 251 450 | Oct 2002 | EP |
| 1371254 | Oct 1974 | GB |
| 2108906 | May 1985 | GB |
| 2240948 | Aug 1991 | GB |
| 2347537 | Sep 2000 | GB |
| 62-264999 | Nov 1987 | JP |
| 63-071794 | Apr 1988 | JP |
| 63-098689 | Apr 1988 | JP |
| 63-072721 | May 1988 | JP |
| 63-175987 | Jul 1988 | JP |
| 64-4934 | Jan 1989 | JP |
| 64-087395 | Mar 1989 | JP |
| 64-087396 | Mar 1989 | JP |
| 64-087397 | Mar 1989 | JP |
| 62-43774 | Feb 1990 | JP |
| 02-130737 | May 1990 | JP |
| 02-252149 | Oct 1990 | JP |
| 03-290780 | Dec 1991 | JP |
| 04-303692 | Oct 1992 | JP |
| 05-069689 | Mar 1993 | JP |
| 05-254283 | Oct 1993 | JP |
| 06-183187 | Jul 1994 | JP |
| 06-191137 | Jul 1994 | JP |
| 06-234287 | Aug 1994 | JP |
| 07-173358 | Jul 1995 | JP |
| 07-205569 | Aug 1995 | JP |
| 09-52240 | Feb 1997 | JP |
| 09-274640 | Oct 1997 | JP |
| 10-129161 | May 1998 | JP |
| 11-227367 | Aug 1999 | JP |
| 2000-11109 | Jan 2000 | JP |
| 2000015288 | Jan 2000 | JP |
| 2000-40181 | Feb 2000 | JP |
| 200067312 | Mar 2000 | JP |
| 2000-177229 | Jun 2000 | JP |
| 2000207641 | Jul 2000 | JP |
| 2001-504406 | Apr 2001 | JP |
| 2001283122 | Oct 2001 | JP |
| 2001-315475 | Nov 2001 | JP |
| 2002-274087 | Sep 2002 | JP |
| WO 8100776 | Mar 1981 | WO |
| WO 8903760 | May 1989 | WO |
| WO 9008661 | Aug 1990 | WO |
| WO 9216913 | Oct 1992 | WO |
| WO 9532919 | Dec 1995 | WO |
| WO 9618972 | Jun 1996 | WO |
| WO 9903057 | Jan 1999 | WO |
| WO 9914055 | Mar 1999 | WO |
| WO 9947983 | Sep 1999 | WO |
| WO 0115098 | Mar 2001 | WO |
| WO 0143095 | Jun 2001 | WO |
| WO 0172224 | Oct 2001 | WO |
| WO 0177856 | Oct 2001 | WO |
| WO 0180473 | Oct 2001 | WO |
| WO 0186535 | Nov 2001 | WO |
| WO 0190962 | Nov 2001 | WO |
| WO 0195243 | Dec 2001 | WO |
| WO 0201484 | Jan 2002 | WO |
| WO 0213134 | Feb 2002 | WO |
| WO 02063545 | Aug 2002 | WO |
| WO 02065246 | Aug 2002 | WO |
| WO 02065404 | Aug 2002 | WO |
| WO 02069221 | Sep 2002 | WO |
| WO 02073512 | Sep 2002 | WO |
| WO 02086665 | Oct 2002 | WO |
| WO 02091281 | Nov 2002 | WO |
| WO 02097575 | Dec 2002 | WO |
| WO 02101670 | Dec 2002 | WO |
| WO 03007623 | Jan 2003 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20040256469 A1 | Dec 2004 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60396577 | Jul 2002 | US | |
| 60304216 | Jul 2001 | US | |
| 60171689 | Dec 1999 | US | |
| 60167405 | Nov 1999 | US | |
| 60153112 | Sep 1999 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10394914 | Mar 2003 | US |
| Child | 10708549 | US | |
| Parent | 10340352 | Jan 2003 | US |
| Child | 10394914 | US | |
| Parent | 10192488 | Jul 2002 | US |
| Child | 10340352 | US |
