Abstract:
A programming device is provided that programs cards, such as payment cards, with data, such as personal data, using light transmitters and receivers. For example, an infrared transmitter may be provided to program personal data (e.g., a customer&#39;s credit card number) into a card wirelessly. In doing so, the card may be, for example, completely laminated such that there are no exposed electronic components on the exterior surface of the card and be programmed via light. The programming device may shield the programming components to block ambient light from interacting with those programming components during programming. A conveyor may be utilized to align multiple cards with a programming device to allow assembly-line style programming of the cards.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims the benefit of U.S. Provisional Patent Application No. 61/249,692, titled “Programming with Light for Powered Cards and Devices,” filed Oct. 8, 2009 and U.S. Provisional Patent Application No. 61/287,366, titled “Programming Protocols for Powered Cards and Devices,” filed Dec. 17, 2009, which are hereby incorporated by reference herein in their entirety. 
    
    
     BACKGROUND OF THE INVENTION 
     This invention relates to magnetic cards and devices and associated payment systems. 
     SUMMARY OF THE INVENTION 
     A card may include a dynamic magnetic communications device. Such a dynamic magnetic communications device may take the form of a magnetic encoder or a magnetic emulator. A magnetic encoder may change the information located on a magnetic medium such that a magnetic stripe reader may read changed magnetic information from the magnetic medium. A magnetic emulator may generate electromagnetic fields that directly communicate data to a magnetic stripe reader. Such a magnetic emulator may communicate data serially to a read-head of the magnetic stripe reader. 
     All, or substantially all, of the front as well as the back of a card may be a display (e.g., bi-stable, non bi-stable, LCD, LED, or electrochromic display). Electrodes of a display may be coupled to one or more capacitive touch sensors such that a display may be provided as a touch-screen display. Any type of touch-screen display may be utilized. Such touch-screen displays may be operable of determining multiple points of touch. Accordingly, a barcode may be displayed across all, or substantially all, of a surface of a card. In doing so, computer vision equipment such as barcode readers may be less susceptible to errors in reading a displayed barcode. 
     A card may include a number of output devices to output dynamic information. For example, a card may include one or more RFIDs or IC chips to communicate to one or more RFID readers or IC chip readers, respectively. A card may include devices to receive information. For example, an RFID and IC chip may both receive information and communicate information to an RFID and IC chip reader, respectively. A device for receiving wireless information signals may be provided. A light sensing device or sound sensing device may be utilized to receive information wirelessly. A card may include a central processor that communicates data through one or more output devices simultaneously (e.g., an RFID, IC chip, and a dynamic magnetic stripe communications device). The central processor may receive information from one or more input devices simultaneously (e.g., an RFID, IC chip, dynamic magnetic stripe devices, light sensing device, and a sound sensing device). A processor may be coupled to surface contacts such that the processor may perform the processing capabilities of, for example, an EMV chip. The processor may be laminated over and not exposed such that such a processor is not exposed on the surface of the card. 
     A card may include one or more light transmitters and light receivers. The light transmitters and receivers may be the same, or different, devices. A light transmitter may be able to transmit visible, infrared, or visible and infrared light. A light transmitter may be able to transmit additional types of light (e.g., ultraviolet light). A light receiver may be able to receive visible, infrared, or visible and infrared light. A light receiver may be able to receive additional types of light (e.g., ultraviolet light). A light transmitter may take the form of, for example, an LED. A light receiver may take the form of, for example, a photo-transistor, photo-diode, or photo-resistor. 
     A card may include a light transmitter (e.g., an infrared transmitter) about one end of a card and a light receiver (e.g., an infrared receiver) about the opposite end of a card. In doing so, the light transmitter and receiver may be located at a distance from one another (e.g., greater than half an inch, one inch, one and a half inch, two inches, or two and a half inches away from one another) such that the light receiver cannot pick up transmissions from the light transmitter. 
     For example, a light receiver may be located along about a top edge of a card at a particular distance from one side edge (e.g., 1.067 inches from one side edge). A light transmitter may also be located about the top edge at that same particular distance from the other side edge (e.g., 1.067 inches from the other side edge). Accordingly, a programming fixture may include a light transmitter spaced similarly from a light receiver such that the light receiver of the programming fixture may communicate with the light transmitter of the card and the light transmitter of the programming fixture may communicate with the light receiver of that same card. In this manner, cards may be moved through the programming fixture and stopped in front of the programming fixture for programming. A programming module may be included with multiple programming fixtures such that multiple programming fixtures may simultaneously program cards. 
     Multiple programming fixtures, for example, may be implemented along a portion of an assembly line. A transport mechanism (e.g., a conveyor belt) may be implemented to carry each card to one or more programming fixtures that may be implemented along an assembly line. In so doing, multiple cards may be carried in a forward and/or reverse direction to one or more programming fixtures of an assembly line. Each card may be programmed by one or more of the programming fixtures of an assembly line. 
     A personalization machine may include multiple modules (e.g., multiple programming modules) such that cards may be personalized utilizing the personalization machine. For example, a personalization machine may include one or more modules for embossing a card, modules for printing indicia on a card, modules for writing to a static magnetic stripe of a card, modules for reading from a static magnetic stripe of a card, modules for reading and/or writing information to an IC chip (e.g., EMV chip) of a card, modules for reading and/or writing information to a Radio-Frequency Identification Tag of a card, modules for laser engraving to a card, modules for flex-testing a card, modules for placing holograms onto a card, modules for placing protective coatings on a card, modules for optically reading physical information on a card (e.g., a credit card number), and modules for placing a material operable to receive an ink-based signature/mark on a card. The personalization machine may be able to communicate with a remote server to, for example, download information to be programmed into a card. The personalization machine may be able to communicate with a remote server to, for example, upload information confirming data programmed into a card. 
     A card may include a universal identification number. In this manner, multiple card accounts may be programmed into a card. A universal identification number may be supplied by a card (e.g., via a light transmitter) during programming to identify a universal card number. Such information may be communicated to a remote server, in which one or more multiple card account information (e.g., magnetic stripe data for multiple card accounts), may be communicated to the personalization machine and then communicated to a card via a light transmitter. The magnetic stripe data may be stored in a memory of a card during programming. 
     Application code may be pre-programmed into the card before programming by the personalization machine such that the application code is programmed when the magnetic stripe data is programmed into the card. Particular magnetic stripe data may then be emulated, for example, through a magnetic emulator located on a card in accordance with the previously programmed application code. Additional data may be stored during programming of magnetic stripe data. For example, information utilized by application code other than magnetic stripe data may be programmed. For example, a particular one or more security codes for a particular universal identification number may be programmed into a card. The remote server may keep track of the one or more security codes programmed into a particular card (e.g., using a universal identification number or a payment card account number such as a credit card number). 
     Numerous types of light may be utilized to program a card. For example, infrared light of a particular frequency may be utilized. All cards programmed by a particular module may be programmed, for example, utilizing the same frequency of infrared light. Alternatively, for example, different cards may be programmed utilizing different frequencies of light. In doing so, multiple cards may be programmed in close proximity to one another and different frequencies of communication for each card may protect against infrared cross-talk within the programming module. A card may include an identification number (e.g., a universal identification number or a payment card account number such as a credit card account number) that is optically read by a module of a personalization machine. 
     A remote database may store a pre-programmed infrared communications frequency for a card. Accordingly, the personalization machine may receive the frequency from the remote database. Accordingly, the card and an IR programming module of the personalization machine may each know the frequency of communication without, for example, the need to directly communicate with one another. 
     Multiple types of data may be communicated to a card. For example, one or more account numbers, expiration dates, user names, and other data (e.g., magnetic stripe track data) may be loaded into a card using communication ports on the card (e.g., IR transmitters and/or receivers). 
     A protocol is provided for infrared data communication between a programming device and an infrared client device such as a programmable card. The client device may be, for example, a one-time programmable low-power device. The protocol may exhibit a high tolerance for device-dependent operational frequency error, such that a low speed (e.g., 2.4 kbit/s) may be implemented at the infrared physical layer. A factory test feature may be provided such that a client device failure due to parts deviation may be detected during a manufacture production process. 
     The protocol may include a high security feature such that the communication port of a client device may be disconnected and the programming memory erased permanently after infrared communication. The communication process time may occur within one or more seconds (e.g., 1-2 seconds). 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The principles and advantages of the present invention can be more clearly understood from the following detailed description considered in conjunction with the following drawings, in which the same reference numerals denote the same structural elements throughout, and in which: 
         FIG. 1  is an illustration of cards constructed in accordance with the principles of the present invention; 
         FIG. 2  is an illustration of a card constructed in accordance with the principles of the present invention; 
         FIG. 3  is an illustration of a programming device constructed in accordance with the principles of the present invention; 
         FIG. 4  is an illustration of communications constructed in accordance with the principles of the present invention; 
         FIG. 5  is an illustration of an architecture constructed in accordance with the principles of the present invention; 
         FIG. 6  is an illustration of a radiant intensity constructed in accordance with the principles of the present invention; 
         FIG. 7  is an illustration of a card constructed in accordance with the principles of the present invention; 
         FIG. 8  is an illustration of a personalization system constructed in accordance with the principles of the present invention; 
         FIG. 9  is an illustration of communications constructed in accordance with the principles of the present invention; 
         FIG. 10  is an illustration of communications constructed in accordance with the principles of the present invention; 
         FIG. 11  is an illustration of communications constructed in accordance with the principles of the present invention; and 
         FIG. 12  is an illustration of process flow charts constructed in accordance with the principles of the present invention. 
     
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       FIG. 1  shows card  100  that may include, for example, a dynamic number that may be entirely, or partially, displayed via display  112 . A dynamic number may include a permanent portion such as, for example, permanent portion  111 . Permanent portion  111  may be printed as well as embossed or laser etched on card  100 . Multiple displays may be provided on a card. For example, display  113  may be utilized to display a dynamic code such as a dynamic security code. Display  125  may also be provided to display logos, barcodes, as well as multiple lines of information. A display may be a bi-stable display or non bi-stable display. Permanent information  120  may also be included and may include information such as information specific to a user (e.g., a user&#39;s name or username) or information specific to a card (e.g., a card issue date and/or a card expiration date). 
     Card  100  may include one or more buttons such as buttons  130 - 134 . Such buttons may be mechanical buttons, capacitive buttons, or a combination of mechanical and capacitive buttons. Card  100  may include button  199 . Button  199  may be used, for example, to place card  100  into a programming mode to receive programming (e.g., programming of a user&#39;s personal payment card data). A button (e.g., button  199 ) may be utilized in a variety of ways (e.g., to communicate information through a dynamic magnetic communications device indicative of a user&#39;s intent to purchase a particular product with points instead of credit). 
     Architecture  150  may be utilized with any card. Architecture  150  may include processor  120 . Processor  120  may have on-board memory for storing information (e.g., application code). Any number of components may communicate to processor  120  and/or receive communications from processor  120 . For example, one or more displays (e.g., display  140 ) may be coupled to processor  120 . Persons skilled in the art will appreciate that components may be placed between particular components and processor  120 . For example, a display driver circuit may be coupled between display  140  and processor  120 . 
     Memory  142  may be coupled to processor  120 . Memory  142  may include data that is unique to a particular card. For example, memory  142  may store discretionary data codes associated with buttons of card  150 . Such codes may be recognized by remote servers to effect particular actions. For example, a code may be stored on memory  142  that causes a non-merchant product to be purchased with points during a merchant transaction. Memory  142  may store loyalty information such as identifying information for a points account (e.g., a points account number) and associated information (e.g., a default preference on how points are earned during a purchase, such as 50% of a purchaser&#39;s points is given to the user and 50% of a purchaser&#39;s points is used to purchase lottery entries for a lottery that has at least one award of a particular number of points). 
     Memory  142  may be partially implemented as non-volatile memory. Accordingly, memory  142  may be pre-programmed with, for example, a programming protocol that may define how data (e.g. IR data) may be received by data input  153  and how data (e.g., IR data) may be transmitted by data output  154 . 
     Memory  142  may receive data as received from data input  153  (e.g., an IR receiver). For example, data may be received by memory  142  that may be indicative of a universal identification number associated with card  100 . Such a universal identification number may, for example, uniquely identify card  100 . Memory  142  may receive data via data input  153  that may represent a security code that may be associated with the universal identification number of card  100 . 
     Memory  142  may provide data, such as a universal identification number associated with card  100 , to data output  154 . Accordingly, data output  153  (e.g., an IR transmitter) may transmit such a universal identification number to, for example, a personalization machine. The personalization machine may relay the universal identification number to a remote server, which in turn, may respond with personalization data that may be associated with the universal identification number of card  100 . 
     Memory  142  may receive data from data input  153  (e.g., an IR receiver) that may be associated with a universal identification number of card  100 . For example, one or more account numbers, user names, discretionary data, and expiration dates may be stored within memory  142 . Such data may be provided by card  100 , for example, as one or more tracks of magnetic stripe data during a transaction (e.g., a purchase transaction). 
     Any number of reader communication devices may be included in architecture  150 . For example, IC chip  152  may be included to communicate information to an IC chip reader. IC chip  152  may be, for example, an EMV chip. As per another example, RFID  151  may be included to communicate information to an RFID reader. A magnetic stripe communications device may also be included to communicate information to a magnetic stripe reader. Such a magnetic stripe communications device may provide electromagnetic signals to a magnetic stripe reader. 
     Different electromagnetic signals may be communicated to a magnetic stripe reader to provide different tracks of data. For example, electromagnetic field generators  170 ,  180 , and  185  may be included to communicate separate tracks of information to a magnetic stripe reader. Such electromagnetic field generators may include a coil wrapped around one or more materials (e.g., a magnetic material and/or a non-magnetic material). 
     Each electromagnetic field generator may communicate information serially to a receiver of a magnetic stripe reader for a particular magnetic stripe track. Read-head detectors  171  and  172  may be utilized to sense the presence of a magnetic stripe reader (e.g., a read-head housing of a magnetic stripe reader). The sensed information may be communicated to processor  120  to cause processor  120  to communicate information serially from electromagnetic generators  170 ,  180 , and  185  to magnetic stripe track receivers in a read-head housing of a magnetic stripe reader. Accordingly, a magnetic stripe communications device may change the information communicated to a magnetic stripe reader at any time. 
     Processor  120  may, for example, communicate user-specific and card-specific information through RFID  151 , IC chip  152 , and electromagnetic generators  170 ,  180 , and  185  to card readers coupled to remote information processing servers (e.g., purchase authorization servers). Driving circuitry  141  may be utilized by processor  120 , for example, to control electromagnetic generators  170 ,  180 , and  185 . 
       FIG. 2  shows card  200 . Cards may include one or more infrared and/or visible light receivers and transmitters to communicate with one or more infrared and/or visible light transmitters and receivers, respectively, that may exist on programming fixtures of programming modules of a personalization machine. Card  200  may include, for example, receiver  202  and transmitter  203  that may be utilized to program card  200  via a personalization machine. 
     Receiver  202  and transmitter  203  may represent, for example, a non-contact, opto-isolated, bi-directional communications port. Such a communications port may, for example, transmit and receive at differing frequencies so as to reduce interference. For example, signals transmitted by transmitter  203  may be cross-coupled into receiver  202  if the peak wavelength sensitivity of receiver  202  is at or near the peak wavelength emission of transmitter  203 . Accordingly, receiver  202  may be implemented with a peak wavelength sensitivity (e.g., 870 nanometers) that may be sufficiently different from the peak wavelength emission (e.g., 940 nanometers) of transmitter  203 . Alternate interference reduction methods (e.g., half-duplex communication methods) may also be used. In so doing, a communications port may transmit and receive at the same frequency, but not at the same time so as to reduce interference. 
       FIG. 3  shows programming device  300 . Programming device  300  may include housing  301  with slit  302 . Slit  302  may be sized to receive all or a portion of a client device (e.g., a powered card). Indicators  303  and  304  may be provided to represent the direction programming ports are to be faced (e.g., infrared programming ports) when a client device is inserted into slit  302 . Communications cable  311  may be utilized to couple a device to programming device  300 . Such a device may be, for example, a computer that includes data to be programmed onto a client device. Cable  311  may include connector  310  (e.g., mini-USB) for connecting to the circuitry of programming device  300 . Cable  311  may include connector  312  (e.g., USB) for connecting to the circuitry of another device. 
     Initially, programming device  300  may send a sequence of clock pulses (e.g., ten clock pulses) to wake up a client device which may be in a low-power, deep-sleep mode. Once the client device is in communication range (e.g., an IR communication range), the client device may return a sequence of clock pulses to the programming device. Accordingly, the programming device may measure and determine the frequency difference between the clock signal generated by the programming device and the clock signal generated by the client device. 
     The programming device may verify that the client device&#39;s clock frequency is within a specification range. The programming device may send a set of personalization requests containing client&#39;s account information and/or other data to the client device based on the client device&#39;s clock frequency. 
     At the end of the personalization sequence, the programming device may send a “terminate” request to the client to terminate the personalization sequence. A “successful” personalization sequence response to the request may be sent by the client device to the programming device, which may constitute the minimum test requirement of the personalization sequence. 
     The personalization sequence may be time limited. Accordingly, a timeout may be experienced during the personalization sequence if a maximum time limit (e.g., 3-4 seconds) has transpired. A timeout may cause the client device to return to a low-power operational mode to conserve battery energy. 
     The command messages may be sequenced for maximum user account protection. Accordingly, strict sequencing rules may be applied, such that any sequencing error that may occur during the personalization sequence may cause the client device to return to a low-power operational mode to conserve battery energy and to terminate the personalization sequence. In so doing, any personalization data that may otherwise be transmitted to the client device may instead remain protected within the programming device in the event that an attempt is made to receive unauthorized personalization data from the programming device. 
     The physical layer of a communications protocol implemented by a programming device may use a pulse width modulation scheme. “Inter-byte” and “inter-message” idle timing may be implemented. The programming device may initiate all requests to the client device within a few seconds (e.g., 1-2 seconds). A delay (e.g., a 30 ms delay) may be implemented in between the exchange of message packets according to, for example, communication  430  of  FIG. 4 . 
     The data transmission of a programming device and a client device may use an infrared physical layer protocol. The baud rate may be, for example, approximately 2400 bps, 8-bit data with a start and a stop bit. The start bit may be “0” and the stop bit may be “1”. A “0” bit may be represented by a 3/16 th  bit width pulse and “1” bit may be represented by the lack of a pulse. An exemplary byte scheme is shown in communication  410  of  FIG. 4 . The order of the transmission may be LSB first, 8-bit data followed by a stop bit. A delay (e.g., approximately 5 ms delay) may be allowed between bytes. An idle period (e.g., approximately 30 ms idle time) may be inserted between messages. 
     The delays, for example, may allow the processor to identify the messages and to provide sufficient time to process the messages. Accordingly, for example, a communication sequence may cause an interrupt to occur in a processor that may be running on the client device and/or the programming device. Delays, therefore, may provide sufficient time to process the interrupt and to execute, for example, a programming sequence in response to the interrupt. 
     Infrared data reception, for example, may occur as follows. When a byte of data is transmitted from the programming device, a start bit may generate an interrupt in a processor running on the client device. 8-bit data may be shifted, for example, to a data register of the client device at a rate that may be in accordance with a baud rate of data transmission established between the programming device and the client device. A negative 3/16 bit pulse may correspond to a “0” bit, while a “1” bit may be represented by the lack of a pulse as shown in communication  420  of  FIG. 4 . 
     The message structure, for example, may be implemented as follows. Each message may be transmitted with a header (e.g., 0x80) followed by, for example, two bytes that may define a length of the message to follow the header. A 16-bit circular redundancy check (CRC) may be transmitted with the message packet. The CRC may not, for example, be considered as a part of message. It may not, for example, be included in the data length. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                   
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Defined Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Start of 
                 0x80 
               
               
                   
                   
                   
                 header 
                   
               
               
                   
                 2 
                 2 
                 Length (2 byte) 
                 N - Count of data bytes 
               
               
                   
                   
                   
                   
                 in the message 
               
               
                   
                 3 
                 N 
                 Message as defined 
                 Variables 
               
               
                   
                 4 
                 2 
                 CRC16 (2 byte) 
                 CRC for the above 
               
               
                   
                   
                   
                   
                 message 
               
               
                   
                   
               
             
          
         
       
     
     A 16-bit CRC, for example, may be used in the protocol. The CRC value may be generated and may be inserted into the transmission data packet (e.g., at the end of the transmission data packet). At the receiving end (e.g., at the client device) the CRC may be calculated with the corresponding message and compared with the CRC received from the transmitting end (e.g., the programming device). If a CRC error occurs during communication, the entire message may be ignored by the receiving end. Accordingly, the CRC error may be considered as a communication failure. In order to preserve data integrity and user security, the programming device may not retry to send the message. 
     Message character strings, for example, may include the following. 
     
       
         
               
             
               
               
               
             
           
               
                   
               
               
                 Message Character Strings 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                   
                 byte 
                 0x00 to 0xFF (hexadecimal), 0 to 255 
               
               
                   
                   
                 (unsigned), −128 to 127 (signed). Used 
               
               
                   
                   
                 typically for string lengths. 
               
               
                   
                 short 
                 2-byte integer value, 0x0000 to 0xFFFF 
               
               
                   
                   
                 (hexadecimal), 0~65535 (unsigned), −32768 to 
               
               
                   
                   
                 32767 (signed). 
               
               
                   
                 int 
                 4-byte integer value representing 0x00000000 to 
               
               
                   
                   
                 0xFFFFFFFF (hexadecimal), 0 to 4294967295 
               
               
                   
                   
                 (unsigned), −2147483648 to 2147483647 (signed) 
               
               
                   
                 long 
                 8-byte integer value representing 
               
               
                   
                   
                 0x0000000000000000 to 0xFFFFFFFFFFFFFFFF 
               
               
                   
                   
                 (hexadecimal), 0 to 2{circumflex over ( )}64-1 (unsigned), −2{circumflex over ( )}63 to 
               
               
                   
                   
                 2{circumflex over ( )}63-1 (signed). Used typically for absolute 
               
               
                   
                   
                 time and data. 
               
               
                   
                 double 
                 8-byte value in IEEE 754 64-bit double- 
               
               
                   
                   
                 precision binary floating-point format. 
               
               
                   
                   
               
             
          
         
       
     
     Byte ordering, for example, may occur as follows. The programming device and client device communication protocol, for example, may utilize big-endian byte ordering. Accordingly, for a 16-bit, 2-byte transmission, the most significant byte may have the lower address order. The lower address byte may be transmitted first. 
     Clock initialization, for example, may occur as follows. The clock initialization may be designed to wake the client device from a low-power (e.g., deep-sleep) mode of operation. Upon receiving a set of initial clock signals from the programming device, the client device may transmit a data sequence (e.g., 0x000000) to the programming device according to an internal clock rate of the client device. The clock signal may be measured by the programming device, for example, to determine the communication bit rate to be used during subsequent communication with the client device. The programming device may tolerate clock frequency errors and monitor and collect the data for future analysis. 
     A security password, for example, may be provided as follows. The programming device, for example, may transmit a security password to the client device once the communication rate is determined. The client device, for example, may only respond to communications from the programming device once the correct security password is received and verified by the client device. 
     The message specification, for example, may be provided as follows. A number of available messages may be provided, where each message may include the application control and user data information. A communication protocol may provide flexibility for implementation, such that it may not be necessary to implement all of the messages at one time. However, each message that may be sent by the programming device may, for example, require an acknowledgement response. Such an acknowledgement response, for example, may contain header information, message length, CRC and message type information. Failure to respond to a request, for example, may result in a communication error. Other requests (e.g., a password request), however, may not require a response. 
     A protocol implementation may include, for example, a security password request, a write device request, a read device request, and a terminate request. The terminate request, for example, may permanently disable communication to the client device. Other message types, for example, may include the following message types. 
     
       
         
               
               
             
               
               
             
           
               
                   
               
               
                 Message 
                   
               
               
                 Type 
                 Description 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 1 
                 Password 
               
               
                   
                 Security password sent to the client device 
               
               
                   
                 from the programming device for 
               
               
                   
                 communication validation. 
               
               
                 2 
                 Read Device 
               
               
                   
                 A request sent by the programming device to 
               
               
                   
                 the client device to obtain TRACK 1, TRACK 
               
               
                   
                 2, and/or TRACK 3 information contained 
               
               
                   
                 within the client device. 
               
               
                 3 
                 Read Device Response 
               
               
                   
                 A response sent by the client device to the 
               
               
                   
                 programming device containing TRACK 1, 
               
               
                   
                 TRACK 2, and/or TRACK 3 information. 
               
               
                 4 
                 Write Device 
               
               
                   
                 A request sent to the client device from 
               
               
                   
                 the programming device to write TRACK 1, 
               
               
                   
                 TRACK 2, and/or TRACK 3 information. 
               
               
                 5 
                 Write Device Response 
               
               
                   
                 A response from the client device to a 
               
               
                   
                 “Write Device” request from the programming 
               
               
                   
                 device. 
               
               
                 6 
                 Read Battery Information 
               
               
                   
                 A request sent from the programming device 
               
               
                   
                 to the client device to obtain battery 
               
               
                   
                 voltage/capacity information from the 
               
               
                   
                 client device. 
               
               
                 7 
                 Battery Information Response 
               
               
                   
                 A response from the client device to a 
               
               
                   
                 “Read Battery Information” request from the 
               
               
                   
                 programming device that contains battery 
               
               
                   
                 voltage and capacity information. 
               
               
                 8 
                 Read Memory 
               
               
                   
                 A request sent from the programming device 
               
               
                   
                 to the client device to fetch a memory 
               
               
                   
                 block from the client device. 
               
               
                 9 
                 Read Memory Response 
               
               
                   
                 A response from the client device to a 
               
               
                   
                 “Read Memory” request from the programming 
               
               
                   
                 device. 
               
               
                 10 
                 Write Memory 
               
               
                   
                 A request sent from the programming device 
               
               
                   
                 to the client device to update a block of 
               
               
                   
                 memory contained within the client device. 
               
               
                 11 
                 Write Memory Response 
               
               
                   
                 A response from the client device to a 
               
               
                   
                 “Write Memory” request from the programming 
               
               
                   
                 device. 
               
               
                 12 
                 Firmware Version 
               
               
                   
                 A request sent from the programming device 
               
               
                   
                 to the client device to obtain a firmware 
               
               
                   
                 version contained within the client device. 
               
               
                 13 
                 Firmware Version Response 
               
               
                   
                 A response from the client device to a 
               
               
                   
                 “Firmware Version” request from the 
               
               
                   
                 programming device. 
               
               
                 14 
                 Terminate 
               
               
                   
                 A request sent from the programming device 
               
               
                   
                 to the client device to terminate 
               
               
                   
                 communication operation. 
               
               
                 15 
                 Response to Terminate 
               
               
                   
                 A response from the client device to a 
               
               
                   
                 “Terminate” request from the programming 
               
               
                   
                 device. 
               
               
                   
               
             
          
         
       
     
     Message Type 1, for example, may be directed to the Password. The Password may be sent from the programming device to the client device to initiate communications between the programming device and the client device. This may be a security feature added to the protocol that may not require a response from the client device. 
     
       
         
               
               
               
               
             
           
               
                   
               
               
                   
                 # of 
                   
                 Defined 
               
               
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
               
             
             
               
                 1 
                 1 
                 Message Type 
                 0x01 
               
               
                 2 
                 1 
                 N - PASSWORD length (hex) 
                 N (hex) 
               
               
                 3 
                 N 
                 PASSWORD (N bytes in hex) 
                 TBD 
               
               
                   
               
             
          
         
       
     
     Message Type 2, for example, may be directed to the Read Device request that requests track information that may be contained within the client device. Item fields 2, 3, and/or 4 may specify the request for specific track data information. A value of “0” may be used to indicate that no track information is requested. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type 
                 0x02 
               
               
                   
                 2 
                 1 
                 Track 1 information 
                 Any value. 
               
               
                   
                   
                   
                   
                 0, no info. 
               
               
                   
                 3 
                 1 
                 Track 2 information 
                 Any value. 
               
               
                   
                   
                   
                   
                 0, no info. 
               
               
                   
                 4 
                 1 
                 Track 3 information 
                 Any value. 
               
               
                   
                   
                   
                   
                 0, no info. 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 3, for example, may be directed to the Read Device Response from the client device and may be used for read and write verification during personalization of the client device. The client device can provide a “0” in track string length field to indicate that track information is not provided. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type 
                 0x03 
               
               
                   
                 2 
                 1 
                 N - Track 1 character 
                 Any value. 
               
               
                   
                   
                   
                 string length (hex) 
                 0, no info. 
               
               
                   
                 3 
                 N 
                 Track 1 character string 
                 Any value. 
               
               
                   
                 4 
                 1 
                 M - Track 2 character 
                 Any value. 
               
               
                   
                   
                   
                 string length (hex) 
                 0, no info. 
               
               
                   
                 5 
                 M 
                 Track 2 character string 
                 Any value. 
               
               
                   
                 6 
                 1 
                 O - Track 3 character 
                 Any value. 
               
               
                   
                   
                   
                 string length (hex) 
                 0, no info. 
               
               
                   
                 7 
                 O 
                 Track 3 character string 
                 Any value. 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 4, for example, may be directed to the Write Device request. This request may be used to write personalization data (e.g., user information) to the client device tracks (e.g., write information to a memory of the card that communicates the information to a dynamic magnetic stripe communications device). Track 1, 2, and/or 3 character string information may be specified in separate item fields. 
     
       
         
               
               
               
               
             
           
               
                   
               
               
                   
                 # of 
                   
                 Defined 
               
               
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
               
             
             
               
                 1 
                 1 
                 Message Type 
                 0x04 
               
               
                 2 
                 1 
                 N - Track 1 Character 
                 Any value. 
               
               
                   
                   
                 String Length (hex) 
                   
               
               
                 3 
                 N 
                 Track 1 Character String 
                 Any value. 
               
               
                   
                   
                 (ASCII hex) 
                   
               
               
                 4 
                 1 
                 M - Track 2 Character 
                 Any value. 
               
               
                   
                   
                 String Length (hex) 
                   
               
               
                 5 
                 M 
                 Track 2 Character String 
                 Any value. 
               
               
                   
                   
                 (ASCII hex) 
                   
               
               
                 6 
                 1 
                 O - Track 3 Character 
                 Any value. 
               
               
                   
                   
                 String Length (hex) 
                   
               
               
                 7 
                 O 
                 Track 3 Character String 
                 Any value. 
               
               
                   
                   
                 (ASCII hex) 
               
               
                   
               
             
          
         
       
     
     Message Type 5, for example, may be directed to the Write Device Response and may be the client device response to Message Type 4. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 #of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type 
                 0x05 
               
               
                   
                 2 
                 1 
                 Track 1 String Character 
                 Length 
               
               
                   
                   
                   
                 Length Written (hex) 
                 written 
               
               
                   
                   
                   
                   
                 Track 1 
               
               
                   
                 3 
                 1 
                 Track 2 String Character 
                 Length 
               
               
                   
                   
                   
                 Length Written (hex) 
                 written 
               
               
                   
                   
                   
                   
                 Track 2 
               
               
                   
                 4 
                 1 
                 Track 3 String Character 
                 Length 
               
               
                   
                   
                   
                 Length Written (hex) 
                 written 
               
               
                   
                   
                   
                   
                 Track 3 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 6, for example, may be directed to a Read Battery Information request that may request battery information from the client device. An option field, for example, may define a battery type for which battery voltage and/or capacity information may be requested. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type 
                 0x06 
               
               
                   
                 2 
                 1 
                 Option 
                 0x00 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 7, for example, may be directed to a Battery Information Response that may include a 12-bit battery voltage value and a battery-type option field to indicate a battery type that may correspond to the battery voltage value. 
     
       
         
               
               
               
               
             
           
               
                   
               
               
                   
                 # of 
                   
                 Defined 
               
               
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
               
             
             
               
                 1 
                 1 
                 Message Type 
                 0x07 
               
               
                 2 
                 2 
                 Battery Voltage 12-bit A/D 
                 12-bit A/D 
               
               
                   
                   
                 Value (hex) 
                   
               
               
                 3 
                 1 
                 Option (battery type) 
                 0x00 
               
               
                   
               
             
          
         
       
     
     Message Type 8, for example, may be directed to a Read Memory request and may be the request sent by the programming device to the client device for specific memory blocks. The Read Memory request may be used for test purposes (e.g., to verify data previously written into a memory block of the client device). A Read Memory request for undesignated and/or unauthorized memory information may be denied. 
     
       
         
               
               
               
               
             
           
               
                   
               
               
                   
                 # of 
                   
                 Defined 
               
               
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
               
             
             
               
                 1 
                 1 
                 Message Type 
                 0x08 
               
               
                 2 
                 2 
                 N - Length of Memory to 
                   
               
               
                   
                   
                 Read (byte) 
                   
               
               
                 3 
                 2 
                 Address of Memory  
                 Address of 
               
               
                   
                   
                 (2 byte in hex) 
                 Memory 
               
               
                   
               
             
          
         
       
     
     Message Type 9, for example, may be directed to a Read Memory response, which may be designated for test verification purposes. For example, only information from a designated memory block, as defined by the client device, may be accessible. A return value of “0” may indicate that the Read Memory request is rejected. 
     
       
         
               
               
               
               
             
           
               
                   
               
               
                   
                 # of 
                   
                 Defined 
               
               
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
               
             
             
               
                 1 
                 1 
                 Message Type 
                 0x09 
               
               
                 2 
                 2 
                 N - Length of Memory Read 
                 0, info 
               
               
                   
                   
                   
                 request 
               
               
                   
                   
                   
                 rejected. 
               
               
                 3 
                 N 
                 N bytes of Memory 
                 Memory 
               
               
                   
                   
                 Contents (hex) 
                 contents 
               
               
                   
               
             
          
         
       
     
     Message Type 10, for example, may be directed to a Write Memory request, which may be a request to write a block of data to client device memory. The length and address may be specified in the request. The client card device may reject the Write Memory request to protect the client device memory area. 
     
       
         
               
               
               
               
             
           
               
                   
               
               
                   
                 # of 
                   
                 Defined 
               
               
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
               
             
             
               
                 1 
                 1 
                 Message Type 
                 0x0A 
               
               
                 2 
                 2 
                 N - Length of Memory to 
                   
               
               
                   
                   
                 Write (2 bytes) 
                   
               
               
                 3 
                 2 
                 Address of Memory  
                 Address of 
               
               
                   
                   
                 (2 bytes) 
                 Memory 
               
               
                   
               
             
          
         
       
     
     Message Type 11, for example, may be directed to a Write Memory Response. The client device may respond to the Write Memory request with the length of memory written, where a value of “0” may indicate that the request is rejected. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type (byte) 
                 0x0B 
               
               
                   
                 2 
                 2 
                 N - Length of Memory 
                 Length of 
               
               
                   
                   
                   
                 Written (2 bytes) 
                 memory 
               
               
                   
                   
                   
                   
                 written 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 12, for example, may be directed to a Firmware Version request, which may request the version of firmware currently being executed by the client device. The Firmware Version request may also request hardware information associated with the client device firmware. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type (byte) 
                 0x0C 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 13, for example, may be directed to a Firmware Version Response. The client device may respond, for example, with one byte of hexadecimal version code corresponding to its embedded firmware and hardware revision. The client device may respond, for example, with an application number that may define a specific type of client device. A status field may be provided, for example, that may indicate an operational status (e.g., battery capacity) of the client device. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type (byte) 
                 0x0D 
               
               
                   
                 2 
                 1 
                 Version Number (byte) 
                 Version 
               
               
                   
                   
                   
                   
                 Number 
               
               
                   
                 3 
                 1 
                 Application Number 
                 Any value 
               
               
                   
                 4 
                 1 
                 Status 
                 Any value 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 14, for example, may be directed to a Terminate request. The programming device may send a Terminate request to the client device, for example, to terminate the communication process. A Terminate request with option 0x00 may set the client device to a normal mode where no further programming of the client device is possible, but the client device is ready for commercial use. A Terminate request with option 0x01 may set the client device to test mode, whereby personalization data may be transmitted to the client device, but not stored within the client device. A terminate request with option 0x02 may set the client device to test mode, whereby personalization data may be stored within the client device and further programming of the client device may still be possible. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type (byte) 
                 0x0E 
               
               
                   
                 2 
                 1 
                 Option (0x00 hex, Normal) 
                 0x00, 0x01, 
               
               
                   
                   
                   
                   
                 0x02 
               
               
                   
                   
               
             
          
         
       
     
     Message Type 15, for example, may be directed to a Response to Terminate, which may be sent by the client device to the programming device before terminating the communication process. The option status byte may contain the terminating status information. For example, a hexadecimal byte of 0xFF may indicate an error termination. 
     
       
         
               
               
               
               
               
             
           
               
                   
                   
               
               
                   
                   
                 # of 
                   
                 Defined 
               
               
                   
                 Item 
                 Bytes 
                 Content 
                 Values 
               
               
                   
                   
               
             
             
               
                   
                 1 
                 1 
                 Message Type (byte) 
                 0x0E 
               
               
                   
                 2 
                 1 
                 Option (status) 
                 TBD 
               
               
                   
                   
               
             
          
         
       
     
       FIG. 5  shows architecture  500  of a programming device, which may include a communications port (e.g., USB port  502 ), a communications transceiver (e.g., USB transceiver  504 ), test port  508 , MCU  506 , a transmitter (e.g., IR transmitter  510 ), and a receiver (e.g., IR receiver  512 ). 
     The optical characteristics, for example, of programming device  500  may be as follows. The transmission and/or reception range of programming device  500  may include a relatively short range of distance (e.g., a few centimeters or less than an inch). For example, the reception and transmission range may be approximately less than 10 cm (e.g., approximately 5 mm). 
     The IR transmitter/IR receiver of the card device may be aligned with the corresponding IR receiver/IR transmitter of the programming device for optimized communication. The IR receivers of the client device and the programming device may be sensitive to ambient light. Accordingly, a sealed environment may be provided to substantially block ambient light from potentially interfering with IR communications between the client device and the programming device. Interference may be reduced, for example, by establishing half-duplex communications between a client device and a programming device. 
     Interference may be further reduced, for example, by establishing a wavelength sensitivity of the IR receiver that is different than a peak wavelength as transmitted by the IR transmitter. The wavelength sensitivity of the IR receiver may be selected to, for example, 870 nm+/−10 nm. Other parameters that may be exhibited by an IR receiver of a client device and/or a programming device may be as follows. 
     
       
         
               
               
               
               
               
             
               
               
               
               
               
             
           
               
                   
               
               
                 Receiver Parameter 
                 Min. 
                 Typ. 
                 Max. 
                 Unit 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 Irradiance in angular range 
                   
                 110 
                   
                 mW/cm 2   
               
               
                 SIR mode 
                   
                   
                   
                   
               
               
                 Peak Wavelength 
                 860 
                 870 
                 890 
                 nm 
               
               
                 Spectral Radiation Bandwidth 
                   
                 45 
                   
                 nm 
               
               
                 Leading edge jitter 
                   
                 50 
                   
                 ns 
               
               
                 Latency 
                   
                 500 
                   
                 us 
               
               
                 Rise/Fall Time 
                   
                 15 
                   
                 us 
               
               
                 Link Distance 
                   
                 10 
                   
                 mm 
               
               
                   
               
             
          
         
       
     
       FIG. 6  shows radiant intensity graph  600 , which may be exhibited by an IR transmitter of a client device and/or a programming device. For example, the radiated power of an IR transmitter may be 100 mW per steradian at, for example, 0 degree transmission angle  602 . A peak wavelength of, for example, 940 nm may be utilized by the IR transmitter so that the peak wavelength may be sufficiently different from the peak wavelength sensitivity (e.g., 870 nm) of the IR receiver. Other parameters that may be exhibited by an IR transmitter of a client device and/or a programming device may be as follows. 
     
       
         
               
               
               
               
               
             
               
               
               
               
               
             
           
               
                   
               
               
                 Transmitter Parameter 
                 Min. 
                 Typ. 
                 Max. 
                 Unit 
               
               
                   
               
             
             
               
                   
               
             
          
           
               
                 Radiated Power 
                   
                 100 
                   
                 mW/sr 
               
               
                 Peak Wavelength 
                   
                 940 
                   
                 nm 
               
               
                 Half Angle 
                   
                 15 
                   
                 Deg 
               
               
                 Optical output pulse duration 
                   
                 80 
                   
                 us 
               
               
                 (2.4 kbit/s) 
                   
                   
                   
                   
               
               
                 Rise/Fall Time 
                   
                 15 
                   
                 us 
               
               
                   
               
             
          
         
       
     
       FIG. 7  shows card  700 . Card  700  may include an embedded computer consisting of a computing core, embedded memory, and a low-power infrared transceiver, which may include, for example, IR receiver  702  and IR transmitter  704 . Card  700  may be programmed (e.g., personalized) by using a bidirectional communication protocol that may program the embedded memory inside card  700  via IR receiver  702  and IR transmitter  704 . 
     Once card  700  has been programmed successfully, the infrared transceiver on the card may be permanently disabled for the remainder of the card&#39;s life. Prior to personalization, card  700  may reside in a “wait” state, such that card  700  may be sensitive to all types of light (e.g., infrared light). Accordingly, card  700  may be provided in a dark container and introduced to light only during personalization of card  700 . 
     The IR reactive components (e.g., IR receiver  702  and IR transmitter  704 ) may be accessible through any surface of card  700 . Accordingly, personalization of card  700  may be accomplished through alignment of IR transmitter  704  to a corresponding IR receiver of a programming device and alignment of IR receiver  702  and a corresponding IR transmitter of a programming device. For example, light pipes may be used to align the IR reactive components of card  700  and the corresponding IR reactive components of a programming device. 
       FIG. 8  shows programming system  800 . Programming system  800  may include programming device  806 , conveyor  812 , cards  808 , IR device  814 , IR transmitter  802 , and IR receiver  804 . Programming system  800  may be used, for example, for high-volume programming scenarios, whereby several hundreds of cards  808  may be personalized daily by a single programming device  806  in conjunction with a single IR device  814 . Persons skilled in the art will appreciate that multiple programming systems  800  working in parallel may be capable of personalizing several tens to several hundreds of thousands of cards  808  per day. 
     Programming device  806  may include an application programming interface (API) that may be executing within a computing platform of programming device  806 . The computing platform may, for example, be executing a high-level windows application that may be used to interface with IR device  814 . Accordingly, cards  808  having no user account information may nevertheless be programmed with user account information so as to personalize cards  816  for commercial use. Persons skilled in the art will appreciate that multiple IR devices  814  may be controlled by a single programming device  806  to, for example, further increase a number of cards that may be personalized on a daily basis. 
     Bidirectional interface  810  may represent a communications medium (e.g., a USB communications medium) whereby card personalization information may be exchanged between programming device  806  and IR device  814 . IR device  814  may perform a transceiver operation, whereby communications received from programming device may be converted, for example, to corresponding IR signals and communications received from card  816  may be converted, for example, to USB signals. 
     Personalization data that may be used to personalize card  816  may be derived from media that may be localized to programming device  806 . For example, personalization data may be extracted from a computer readable medium, such as a CD or DVD, by programming device  806  and subsequently programmed into card  816  via IR device  814 . Alternately, personalization data may be extracted from a remote server  820  via a network (e.g., the internet) by programming device  806  and subsequently programmed into card  816  via IR device  814 . 
     Cards  808  may be removably attached to conveyer  812 . Conveyer  812  may be actuated, for example, such that cards  808  may be sequentially brought within a programming distance of IR device  814 . For example, infrared components  802  and  804  on IR device  814  may be closely aligned within 5 mm or less (e.g., within approximately 1.0 mm) of the corresponding components on card  816  via operation of conveyer  812 . IR device  814  may utilize sensor  822 , which may determine whether IR components of card  816  are properly aligned with the corresponding IR components of IR device  814 . Persons skilled in the art will appreciate that conveyer  812  may be actuated in both a forward and reverse direction to bring cards  808  within a programming distance of IR device  814 . 
     The IR receiver on card  816  may be configured, for example, to have a peak wavelength sensitivity of 870 nm. Therefore, corresponding IR transmitter  802  on IR device  814  may be provided so as to closely match the IR receiver specifications of card  816 . 
     The IR transmitter on card  816  may be configured, for example, to have a peak wavelength emission at approximately 940 nanometers. Therefore, corresponding IR receiver  804  of IR device may be provided so as to closely match the IR transmitter specifications of card  816 . 
     A low-level, IR communication schema may be used in the personalization of cards  808 . The schema, for example, may be an asynchronous, bidirectional, serial communication method. Communication may occur, for example, at a rate of approximately 2400 bps with no parity error checking, 1 start bit, and 1 stop bit (2400-N-8-1). The start bit, for example, may be zero (0) and the stop bit, for example, may be one (1). 
     Bit encoding using infrared pulses may be implemented with a common 18% ( 3/16 th ) duty cycle pulse width scheme as shown in  FIG. 9 .  FIG. 9  shows an example of a transmitted zero (0) bit where the IR pulse width is 78 microseconds (μS) and the entire bit time is 416.7 μS.  FIG. 10  shows an example of a typical byte frame that may utilize the pulse width scheme of  FIG. 9 . 
     After initial manufacturing, cards  808  may be placed into a low-power, deep-sleep condition. To wake card  816 , for example, programming device  806  may send a series of clock pulses (e.g.,  10 ) at a particular rate (e.g., a rate of 600 bits per second) using a 78.1 us infrared pulse encoding scheme. For example, the clock pulses have a bit width, or period, of 1.7 ms and a corresponding infrared pulse width of 78.1 us. 
     After the initialization sequence (e.g., ten clock pulses) are sent by programming device  806 , card  816  may wake up and provide a response (e.g., three bytes of 0x00 at a baud rate of approximately 2400 bps). Since card  816  may not be able to accurately produce a specific baud rate, programming device  806  may nevertheless use the response from card  816  to measure the baud rate produced by card  816 . Accordingly, programming device  806  may make any timing adjustments that may be necessary to substantially match the baud rate produced by card  816  so as to improve subsequent communications with card  816 . 
       FIG. 11  shows an initialization sequence and a response to the initialization sequence. A programming device may transmit initialization sequence  1102  to a client device. In so doing, a client device may be awakened from a low-power (e.g., sleep) mode of operation. For example, the initialization sequence may be provided to input ports of a processor of the client device, which may cause an interrupt to occur within the processor to transition the client device into a normal mode of operation. Once active, the client device may respond with response  1104 . If the client device does not respond with response  1104  within a timeout period (e.g., 100 mS), the programming device may resend initialization sequence  1102 . 
     The programming device may receive response  1104  from the client device. In so doing, the programming device may ascertain a communication rate (e.g., transmission clock timing) that may be used by the client device to transmit response  1104 . The programming device may adjust its communication timing to be compatible with the timing characteristics of the client device and the transfer of personalization data (e.g., messages) may commence. 
     Upon receipt of a message, the client device may evaluate the validity of the message. A client device may also evaluate a CRC that may be transmitted with the message. If the message validity and CRC are evaluated favorably, the client device may accept the message and may acknowledge receipt of the message. If either of the message or CRC are evaluated unfavorably, the client device may not respond at all. 
     If the programming device receives an acknowledgment from the client device, the programming device may proceed to send additional messages. However, if after a timeout period (e.g., 30 ms) the client device has not yet responded, the programming device may assume that a communication error has occurred and may not attempt resending messages to the client device. 
     The programming device may try to resend any unacknowledged message. If after a resend, the client device still has not acknowledged, the programming device may report an error condition and the client device may be marked as a suspected defect. 
     Data exchanged between a programming device and a client device may observe communication timeout rules. Inter-Byte timeouts may be tolerated, such that a maximum delay (e.g., 5 mS) between consecutive bytes in a message may be permitted. If more than a maximum timeout delay elapses between consecutively transmitted bytes, a client device may assume an error condition has occurred and return to a low-power (e.g., sleep) condition. In so doing, no data may be saved within the client device and the entire personalization session may be ignored. 
     Inter-Message timeouts may be tolerated, such that a maximum delay (e.g., 30 mS) between consecutive messages during a personalization sequence may be permitted. If more than a maximum timeout delay elapses between messages, the client device may assume an error condition has occurred and return to a low-power (e.g., sleep) condition. In so doing, no data may be saved within the client device and the entire personalization session may be ignored. 
       FIG. 12  shows sequences  1210  through  1240 . Sequence  1210  may include, for example, transmitting an initialization sequence from a programming device to a client device (e.g., as in step  1211 ), transmitting a response sequence from a client device to a programming device (e.g., as in step  1212 ), adjusting communication timing of the programming device based upon the response sequence transmitted by the client device (e.g., as in step  1213 ), and commencing a personalization sequence of the client device (e.g., as in step  1214 ). 
     Sequence  1220  may include, for example, loading multiple client devices onto one or more conveyors (e.g., as in step  1221 ), moving the conveyor to align each client device with a corresponding programming device (e.g., as in step  1222 ), detecting a proper alignment of each client device with a respective programming device (e.g., as in step  1223 ), and commencing a personalization sequence of the client device (e.g., as in step  1224 ). 
     Sequence  1230  may include, for example, commencing a personalization sequence of a client device (e.g., as in step  1231 ), transmitting a byte of a personalization message from a programming device to a client device (e.g., as in step  1232 ), setting a timeout delay to receive an acknowledgment from the client device (e.g., as in step  1233 ), waiting for the acknowledgment from the client device (e.g., as in step  1234 ), and terminating the personalization session if the acknowledgment is not received from the client device before the timeout delay expires. 
     Sequence  1240  may include, for example, commencing a personalization sequence of a client device (e.g., as in step  1241 ), transmitting a personalization message from a programming device to a client device (e.g., as in step  1242 ), setting a timeout delay to receive an acknowledgment from the client device (e.g., as in step  1243 ), waiting for the acknowledgment from the client device (e.g., as in step  1244 ), and terminating the personalization session if the acknowledgment is not received from the client device before the timeout delay expires. 
     Persons skilled in the art will appreciate that the present invention is not limited to only the embodiments described. Instead, the present invention more generally involves dynamic information. Persons skilled in the art will also appreciate that the apparatus of the present invention may be implemented in other ways then those described herein. All such modifications are within the scope of the present invention, which is limited only by the claims that follow.