This application is a continuation of U.S. patent application Ser. No. 10/244,044 filed Sep. 13, 2002, now U.S. Pat. No. 6,837,425 B2, entitled COMPACT PROTOCOL AND SOLUTION FOR SUBSTANTIALLY OFFLINE MESSAGING BETWEEN PORTABLE CONSUMER DEVICE AND BASE DEVICE which is hereby incorporated by reference, as if set forth in full in this document, for all purposes.
The present invention generally relates to communications between a portable device and a base device. More specifically, the present invention relates to a method and system for providing storage and display of transactional messages using message codes communicated from a portable device to a base device.
With the continuing demand for using information to provide enhanced consumer experience, base devices and portable devices may be leveraged to provide a personalized experience for a consumer during a purchase transaction at a merchant. For example, a loyalty program may be provided where consumers are awarded incentives for shopping at certain merchants that participate in the loyalty program. As part of the loyalty program, merchants can use portable devices, such as smartcards, and/or base devices, such as point-of-sale (POS) devices, to keep track of the activities of various consumers and accordingly offer targeted advertising and sale offers to such consumers. As a result, the use of a loyalty program is a powerful tool that may increase consumer loyalty by giving consumers added incentive to continue shopping at merchants participating in the loyalty program.
The effectiveness of the loyalty program may be affected by the ability to communicate with the consumer during the transaction. Thus, in order to more fully increase the effectiveness of the loyalty program, information relating to a consumer's participation in the loyalty program needs to be communicated to the consumer in a fast and efficient manner, preferably, at the point-of-sale. Typically, such information is conveyed to a consumer in the form of messages displayed via a base device. Since the duration of a point-of-sale transaction is relatively short and a consumer typically does not want to wait for a message about a loyalty transaction for an extended period of time, messages intended for the consumer involved in a loyalty transaction need to be rapidly created and provided to the consumer. The longer it takes to create a message, the greater the chances that the consumer may want to skip or discontinue participating in a loyalty program due to the wait time.
Some solutions have been proposed to create messages for display to consumers participating in loyalty programs in an expedited manner. Typical solutions involve, for example, providing consumers with generic messages that were set by software or other mechanisms. These generic messages are generally fixed/predefined and cannot be vared. Also, the messages are not directly linked to the activities of a specific consumer. Consequently, these messages are not very effective because they are not personalized for the consumer and thus are not particularly informative with respect to the consumer's specific status in the loyalty program. Additionally, if messages are composed using various databases residing on different servers distributed throughout the Internet, the time to compose messages increases, which further decreases the value of providing messages to consumers.
Furthermore, if messages are provided at all, the messages are typically derived from content stored in the base device because storage space and data access may be limited on the smartcard or portable device. Accordingly, existing messaging methods are relatively inflexible and do not fully use the advantages of providing a loyalty program.
Hence, it would be desirable to provide a system that is capable of providing messages to a consumer in an efficient and expedited manner during a purchase transaction, thereby allowing loyalty transaction information to be displayed at the point-of-sale.
In one embodiment of the present invention, a method for providing messaging between a portable device and base device is provided. The method includes communicating one or more message codes maintained in the portable device to the base device. The base device then composes a message for a user of the portable device using a dictionary of message codes. The message codes have corresponding message values, which are used to generate the message for the one or more message codes. The generated message is then provided to the user.
In one embodiment, a system for generating a message for a user of a portable device is provided. The system comprises: a base device configured to receive one or more message codes from the portable device; a dictionary having a plurality of message codes associated with the base device, wherein the plurality of message codes correspond to a plurality of message words; a composer configured to compose the message from the received one or more message codes using corresponding message words from the dictionary; and an interface device configured to provide the composed message to the user.
In another embodiment, a method for composing a message at a base device for a user of a portable device using a dictionary of message codes is provided. The message codes having corresponding message values. The method comprises: receiving one or more message codes at the base device from the portable device; generating the message from the received one or more message codes using corresponding message values from the dictionary; and providing the generated message to the user.
Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to accompanying drawings, like reference numbers indicate identical or functionally similar elements.
The present invention in the form of one or more exemplary embodiments will now be described.
Portable device 102 is a device that interfaces with base device 104. For example, portable device 102 may be a smartcard, cellular phone, personal digital assistant (PDA), pager, credit card, ATM card, digital tablet, security badge, access badge, and the like. Information, such as a message code string, is included on portable device 102 and may be read from portable device 102 or communicated to base device 104. Examples of information including message code strings will be described below.
Base device 104 is a device that interacts with portable device 102. Examples of base devices 104 include a point-of-sale (POS) device, cellular phone, PDA, computer, handheld specialized readers (e.g., smartcard key tabs), set-top boxes connected to a TV, kiosks, security system, access system, and the like. Base device 104 is configured to communicate with portable device 102 and more specifically to receive a message code string from portable device 102.
Base device 104 and portable device 102 may interact directly with one another. For example, portable device 102 and base device 104 may directly communicate through a direct connection. In this example, if portable device 102 is a smartcard and base device 104 is a POS device, the smartcard may be directly inserted into the POS device. Alternatively, portable device 102 and base device 104 may communicate through a communication medium, such as a contactless connection, wireless connection, wireline connection, the Internet, etc. Further, the communication may be through an intermediate computing or networking device that facilitates the communication. For example, a smartcard may communicate with a mobile-commerce server via a cell phone. In this case, a smartcard may be inserted into the cellular phone with the cellular phone communicating with the mobile-commerce server through a wireless or infrared (IR) connection. Additionally, a smartcard may be inserted into a PDA with the PDA communicating with the mobile-commerce server. It should be noted that the communication methods described above are for illustration purposes only and that a person of ordinary skill in the art will appreciate other methods that can be used to achieve communications between portable device 102 and base device 104. In one embodiment, communications between portable device 102 and base device 104 may be performed offline. In one embodiment, offline is where messaging is performed between portable device 102 and base device 104 where base device 104 is not connected to a network, such as the Internet.
It should also be noted that a device may alternately play the role of portable device 102 or base device 104 depending on the application under which the device is being used. For example, a cellular phone may function as base device 104 to receive or interface with a smartcard via a contact reader, the smartcard being the portable device 102 in this application; subsequently, the same cellular phone may function as portable device 102 to interface with a POS device via an RF, infrared, and/or bluetooth interface, the POS device being the base device 104 in this second application.
Dictionary database 106 may include one or more dictionaries, for example, dictionaries 124a,b. Each dictionary 124a,b is a database of message codes and their corresponding values or meanings. Dictionary database 106 may be embedded in base device 104. Also, dictionary database 106 may be separate from base device 104 and accessible through a communication medium. For example, dictionary database 106 may be localized in relation to base device 104 and accessible through a network, such as a local area network (LAN), wide area network (WAN), wireless network, wireline network, the Internet, and the like. Also, parts of dictionaries 124a,b may be distributed among different devices. For example, part of dictionary 124a may be located in base device 104 and part in dictionary database 106.
In one exemplary embodiment, each dictionary 124a,b may be organized in data structures of message codes/words and their respective meanings. Additionally, multiple dictionaries may be accessible to base device 104 and different versions of dictionaries may be used by base device 104. As will be further described below, one or more of the dictionaries 124a,b in the dictionary database 106 may be selected to allow a message to be composed or generated from a number of message codes.
Composer 108 may be software, embedded software, dedicated hardware, or any combination thereof, that analyzes message codes and generates a message by retrieving the appropriate values related to the message codes from dictionary 124a. For illustrative purposes herein, only one dictionary 124a is used to generate the message. Based on the disclosure and teachings provided herein, it will be clear to a person of ordinary skill in the art that more than one dictionary may be used to generate a message from the message codes. Composer 108 may be embedded in base device 104 or be accessible to base device 104. Once the message has been composed from the message codes by composer 108, composer 108 forwards the message to interface device 110. It should be noted that composer 108 may further use information from other sources or databases (not shown) to help compose or generate messages from message codes.
Interface device 110 receives the generated message from composer 108 and provides the message to a user of portable device 102. For example, interface device 110 may display the message, print the message, or announce the message audibly. If the message is audibly announced, a sound, tone, voice, or the like may be used. Additionally, any combination of methods for providing the message to the user may be used. For example, a sound and a displayed message may be used. Interface device 110 may also be part of base device 104 or be separate from base device 104 but coupled with base device 104. Examples of interface device 110 are a display screen, computer, printer, speaker, PDA, or any other device capable of providing a message to a user.
As mentioned above, message codes are included in portable device 102. In one exemplary embodiment, the message codes are strings of character and/or symbols. Referring to
The message codes may correspond to message words that serve different functions. There are different categories of message words. For example, message words may be classified as constant message words, variable message words, administrative message words, and action message words.
Constant message words are message words that are constant. For example, constant message words are words, sentences, colors, graphics, or sound sequences, such as, message code “255”=“congratulations, you are now participating in”; message code “A10F”=“three_standard_rings”; or message code “A75F”=“{HTML TAG}<TITLE>”. The message value “congratulations, you are now are participating in” represents a constant string of words or a sentence. The message value “three_standard_rings” may indicate a constant sound sequence of three rings, and the message value “{HTML TAG}<TITLE>” may indicate displaying an HTML TAG of TITLE.
Variable message words refer to message words that may vary. For example, variable message words may provide a reference to information computed during the transaction or unique information specific to portable device 102. For instance, message code “ABB0”=“remaining_value_on_electronic_purse”; message code “1234”=“account_number_used_during the_transaction”; or message code “DDDD”=“current_date”, where the message value “remaining_value_on_electronic urse” may indicate the remaining value on an electronic account related to portable device 102; the message value “account_number_used_during_the_transaction” may refer to the account number of the user of portable device 102 that is being used during the transaction; and the message value “current_date” refers to a variable that includes the value of the current date.
An administrative message word is a message word that is used to affect the analysis of the message codes. For example, administrative message words may indicate the bit or byte length of message words, a command to interpret the message codes with a basic or enhanced dictionary 106, a code to identify which type of base device 104 (e.g., POS, PC, phone, PDA, hand-held specialized readers) the message is applicable to, a code to identify interface device 110 (display, printer) for which the message code string applies, or a version of dictionary 106 that should be used with message code string 112.
Each dictionary 124a,b may include fields for different modes, such as a standard mode and an enhanced mode. In one exemplary embodiment, an administrative message code may be used to designate the selection of a particular mode depending on certain predetermined factors. For example, a standard mode may be used for a graphical display and an enhanced mode may be used for a printed message. Also, each dictionary 124a,b may include a default, or implicit mode which is to be used by the composer in absence of an administrative word identifying the selection of a particular mode.
Action message words are used to direct base device 104 to take corresponding actions as part of the transaction. Examples of action message words include message code “XYZ”=“print_receipt_only”; message code “9999”=“log_message_on_base_device_for_delayed_reporting_to_service_host”; or message code “ABCD” = “update_message_string_in_card”. The message value “print_receipt_only” may indicate the action of only printing a receipt using interface device 110, the message value “log_message_on_base_device_for_delayed_reporting_to_service_host” indicates the action of logging the message on base device 104 for subsequent reporting, and the message value “update_message_code_string_in_card” may indicate the action of sending an updated message code string to portable device 102 to replace message code string 112.
Data contained in portable device 102 may not be for the exclusive use of generating consumer messages. In one exemplary embodiment, data used by portable device 102 for purposes other than messaging may also be read by or transmitted to base device 104 and used for composing a message. For example, device information such as an application's ID (AID) in a smartcard may be a code string “A0 00 00 00 98 10 10 04” that is typically used to identify that specific smartcard application; this particular code string may also be used to cause the generation of the message “Visa Smart Loyalty Application Version 4” when read by or transmitted to base device 104. Optionally, information may be entered via base device 104 and used as part of the composed message. For example, transactional information for a purchase, such as total purchase price, may be entered via based device 104 and included in the message displayed to the user.
Message codes may be stored in a binary form, hexadecimal form, or any other standardized format that is interpretable by base device 104 and/or composer 108. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know how to use different formats to store the message codes depending on the system design and requirements.
In one exemplary embodiment, some of the message codes are not uniformly predefined and fixed across all dictionaries 124, but rather are specifically identified by a dictionary associated with a particular base device 104. In other words, the same message code does not necessarily have the same meaning in different dictionaries 124a,b. Accordingly, a message code stored in portable device 102 may have different meanings in different base devices 104 depending on the associated dictionary 124a for each base device 104. For example, a message code “1234” equals “congratulations, you have been entered into our loyal consumer program and now have:” when base device 104 is a POS device, and the same message code may be interpreted as “loyal consumer points:” when base device 104 is a cellular phone with a small display.
Dictionary database 106 may also include multiple versions of a dictionary 124a,b. For example, base device 104 may be associated with multiple interface devices 110 where different versions of dictionaries are used for the different interfaces. If a display and a printer are available, different messages may be provided to a user through the different interfaces. Thus, composer 108 may compose a message from a message code string “32 50 15 FF 0A” as “Welcome to the Smart Shopping Network” on a printer interface device 110 and as a logo on a Point-of-sale display interface device 110. In another example, different versions of dictionary 124a,b may include versions with different languages. In one exemplary embodiment, administrative message codes may be used to identify an appropriate dictionary version. By using different versions of dictionaries, different messages may be created for different interface devices while maintaining the same message code at the same time, and thus simplifying data storage on the portable device.
In one example, the following message codes may be translated differently based on base device 104 and/or interface device 110, or a version of dictionary 124. Table 1 illustrates an embodiment of this example.
Additionally, dictionaries 124a,b in the dictionary database 106 may be updated at any time. For example, message codes and/or message values may be changed and new message codes and/or message values may be added. Updates may be provided periodically to dictionary database 106 in a number of ways, for example, by a de-localized service management host or server or other computing device used for the management of the dictionary database 106. Furthermore, updates may be performed on an automated, pre-scheduled basis or in an ad hoc manner.
In addition, message code string 112 may be changed in portable device 102 and new message code string may be added to portable device 102. Message code string may be changed or added during communications between portable device 102 and base device 104. For example, once message code string 112 is composed into a message and the message is provided to the user of portable device 102, base device 104 may update message code string 112 in portable device 102 for use in future transactions or data exchanges. For example, if a user of portable device 102 has conducted a transaction, information relating to that transaction will be included in message code string 112 as updated in portable device 102.
In step 200, portable device 102 couples to base device 104. As mentioned above, portable device 102 may couple directly to base device 104, through a communication medium, through an intermediate computing or networking device, etc.
In step 202, portable device 102 communicates a message code string 112 to base device 104. For example, as shown in
In step 204, base device 104 receives message code string 112. In step 206, composer 108 then analyzes the message codes in message code string 112 using dictionary-124a. In analyzing the message codes, composer 108 may determine based on an administrative message code which one or more of the dictionaries 124a in dictionary database 106 are to be used and using the appropriate dictionary(ies) 124 retrieve the corresponding applicable message code values.
In step 208, composer 108 generates a message from message code string 112. Assuming table 118 is used as dictionary 124a, the message generated from the corresponding message codes is “Smart loyalty program: 3 of 5 visits to XYZ store. Earn $10 off your 6th purchase.” This assumes that the message code FF corresponds to the variable of three.
At step 210, the message is then provided to interface device 110 for communication to a user of portable device 102. For example, the message may be printed, displayed, or audibly communicated to the user through interface device 110.
In step 212, an updated message code string 116 may be provided to portable device 102. Updated message code string 116 may correspond to a message for any future communications between portable device 102 and base device 104. An updated message code string 116 may be appropriate due to the recent activity or transaction conducted by the user of portable device. The message corresponding to the updated message code string 116 may also be forwarded to interface device 110 for display to the user.
One example using an exemplary embodiment of the present invention will now be described. A user is shopping in a first store and has a portable device 102. While browsing at the first store, the user wants to find out the latest account information relating to the user's loyalty program at the first store. To find that latest account information, the user couples portable device 102 to base device 104. Consequently, message code string 112 is communicated to base device 104 and a message is composed from the message code string 112 using composer 108 and dictionary 124a. The message corresponding to the message code string 112 is displayed on interface device 110 for viewing by the user. For example, the message may say “200 additional points will earn you a special offer”.
Subsequently, the user decides to make a purchase at the first store. The purchase is worth two hundred (200) points. Once again, the user couples portable device 102 to base device 104 to complete the purchase. Portable device 102 and base device 104 then communicate with each other. During their communication, base device 104 sends an updated message code string 116 to portable device 102. At the same time, a message corresponding to updated message code string 116 is displayed on a screen connected to base device 104. Based on the purchase that the user just concluded, the message may include loyalty transaction information indicating that the user has just received a certain number of reward points for the purchase; the message may further include a marketing message informing the user that the reward points are valid toward special offers at a second store. For example, the message may say “your purchase just earned you 200 points and qualifies you for a special offer which may be redeemed at a second store”. Additionally, a receipt may also be printed from a printer. The receipt may includes information relating to the loyalty program printed in a different format than that shown on the screen connected to base device 104.
The user then goes to a mall where the second store is located. The user may double check the message that corresponds to updated message code string 116 using base device 104. Base devices 104 may be located throughout the mall. The user then proceeds to the second store after reading the message and connects with base device 104 located in the second store to find out about the special offer. Information relating to the special offer is specific to the second store and is made available through base devices 104 located throughout the second store.
The user then proceeds to make a purchase and at checkout, again couples portable device 102 to base device 104 located at the second store. Updated message code string 116 is again composed into a message by composer 108 using dictionary 124. Based on the purchase information, the composed message indicates that the user has earned a number of points on this purchase and that the special offer has been extended for a certain time period. Information relating to the purchase and the extended time period is then encoded and sent in another updated message code string 116 to portable device 102.
After leaving the second store, the user forgets how long the extended time period is for the special offer. The user can couple portable device 102 to base device 104, such as, a PC reader located at the user's home to quickly access that information on portable device 102 without having to connect to the Internet. The foregoing is merely an illustration of one of many applications that may utilize the present invention. A person of ordinary skill in the art will know of other applications in which the present invention can be deployed.
Furthermore, based on the disclosure and teachings provided herein, it will be clear to a person of ordinary skill in the art that many advantages are provided by various exemplary embodiments of the present invention. For example, messages for a consumer involved in a loyalty transaction using loyalty information pertinent to the transaction and the consumer may be rapidly created and provided to the consumer. A message code is included in a portable device in a very compact form, which keeps memory requirements minimal and communication times fast. Additionally, the use of the logically organized composition data structure for a dictionary 124 ensures rapid composition of messages from message codes. Also, various types of message words may be used depending on different kinds of transactions and different kinds of interface devices. Thus, by relying on the content of a specific dictionary 124 associated with a particular base device 104 to determine the semantic value of the message codes, flexibility is introduced between different portable devices 102, base devices 104, and interface devices 110.
The above description is illustrative but not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
Number | Name | Date | Kind |
---|---|---|---|
4559497 | Farrugia | Dec 1985 | A |
4701518 | Osborn et al. | Oct 1987 | A |
4743732 | Alpatiev et al. | May 1988 | A |
4849942 | Farrugia | Jul 1989 | A |
4851654 | Nitta | Jul 1989 | A |
5007026 | Gaultier et al. | Apr 1991 | A |
5063508 | Yamada et al. | Nov 1991 | A |
5131039 | Chaum | Jul 1992 | A |
5138580 | Farrugia et al. | Aug 1992 | A |
5267123 | Boothroyd et al. | Nov 1993 | A |
5276736 | Chaum | Jan 1994 | A |
5347632 | Filepp et al. | Sep 1994 | A |
5369261 | Shamir | Nov 1994 | A |
D367410 | Hortnagl | Feb 1996 | S |
D367594 | Hortnagl | Mar 1996 | S |
5496417 | Farrugia et al. | Mar 1996 | A |
5542430 | Farrugia et al. | Aug 1996 | A |
5568555 | Shamir | Oct 1996 | A |
5594910 | Filepp et al. | Jan 1997 | A |
5625791 | Farrugia et al. | Apr 1997 | A |
5629980 | Stefik et al. | May 1997 | A |
5634012 | Stefik et al. | May 1997 | A |
5638443 | Stefik et al. | Jun 1997 | A |
5671698 | Farrugia | Sep 1997 | A |
5680353 | Gaultier et al. | Oct 1997 | A |
5713488 | Farrugia | Feb 1998 | A |
5715403 | Stefik | Feb 1998 | A |
5734719 | Tsevdos et al. | Mar 1998 | A |
5758072 | Filepp et al. | May 1998 | A |
5796967 | Filepp et al. | Aug 1998 | A |
5812668 | Weber | Sep 1998 | A |
5813318 | Zanin et al. | Sep 1998 | A |
5815657 | Williams et al. | Sep 1998 | A |
5828848 | MacCormack et al. | Oct 1998 | A |
5844218 | Kawan et al. | Dec 1998 | A |
5850446 | Berger et al. | Dec 1998 | A |
5867494 | Krishnaswamy et al. | Feb 1999 | A |
5867495 | Elliott et al. | Feb 1999 | A |
5875305 | Winter et al. | Feb 1999 | A |
5889863 | Weber | Mar 1999 | A |
5895073 | Moore | Apr 1999 | A |
5931917 | Nguyen et al. | Aug 1999 | A |
5943241 | Nichols et al. | Aug 1999 | A |
5943424 | Berger et al. | Aug 1999 | A |
5963924 | Williams et al. | Oct 1999 | A |
5971925 | Hossack et al. | Oct 1999 | A |
5974235 | Nunally et al. | Oct 1999 | A |
5978840 | Nguyen et al. | Nov 1999 | A |
5983208 | Haller et al. | Nov 1999 | A |
5987132 | Rowney | Nov 1999 | A |
5996076 | Rowney et al. | Nov 1999 | A |
5999525 | Krishnaswamy et al. | Dec 1999 | A |
6002767 | Kramer | Dec 1999 | A |
6012049 | Kawan | Jan 2000 | A |
6014634 | Scroggie et al. | Jan 2000 | A |
6016484 | Williams et al. | Jan 2000 | A |
6026379 | Haller et al. | Feb 2000 | A |
6038492 | Nichols et al. | Mar 2000 | A |
D423147 | Farrugia | Apr 2000 | S |
6061660 | Eggleston et al. | May 2000 | A |
6061665 | Bahreman | May 2000 | A |
6061791 | Moreau | May 2000 | A |
6070147 | Harms et al. | May 2000 | A |
6072781 | Feeney et al. | Jun 2000 | A |
6072870 | Nguyen et al. | Jun 2000 | A |
6078888 | Johnson, Jr. | Jun 2000 | A |
6119105 | Williams | Sep 2000 | A |
6119933 | Wong et al. | Sep 2000 | A |
6163772 | Kramer et al. | Dec 2000 | A |
D436489 | Farrugia | Jan 2001 | S |
6178409 | Weber et al. | Jan 2001 | B1 |
6182123 | Filepp et al. | Jan 2001 | B1 |
6185307 | Johnson, Jr. | Feb 2001 | B1 |
6185766 | Farrugia | Feb 2001 | B1 |
6195661 | Filepp et al. | Feb 2001 | B1 |
6199100 | Filepp et al. | Mar 2001 | B1 |
6199762 | Hohle | Mar 2001 | B1 |
6213879 | Niizuma et al. | Apr 2001 | B1 |
6217165 | Silverbrook | Apr 2001 | B1 |
D442748 | Farrugia | May 2001 | S |
6229621 | Kulakowski et al. | May 2001 | B1 |
6236971 | Stefik et al. | May 2001 | B1 |
D444271 | Farrugia | Jun 2001 | S |
6246778 | Moore | Jun 2001 | B1 |
6253027 | Weber et al. | Jun 2001 | B1 |
6275852 | Filepp et al. | Aug 2001 | B1 |
6289324 | Kawan | Sep 2001 | B1 |
6304915 | Nguyen et al. | Oct 2001 | B1 |
6315200 | Silverbrook et al. | Nov 2001 | B1 |
6317192 | Silverbrook et al. | Nov 2001 | B1 |
6324525 | Kramer et al. | Nov 2001 | B1 |
6324603 | Niizuma et al. | Nov 2001 | B1 |
6332463 | Farrugia et al. | Dec 2001 | B1 |
6335927 | Elliott et al. | Jan 2002 | B1 |
6338105 | Niizuma et al. | Jan 2002 | B1 |
6351688 | Nichols et al. | Feb 2002 | B1 |
6356715 | Silverbrook | Mar 2002 | B1 |
6356794 | Perin, Jr. et al. | Mar 2002 | B1 |
6362868 | Silverbrook | Mar 2002 | B1 |
6362869 | Silverbrook | Mar 2002 | B1 |
6363154 | Peyravian et al. | Mar 2002 | B1 |
6363363 | Haller et al. | Mar 2002 | B1 |
6367474 | Berthon-Jones et al. | Apr 2002 | B1 |
6373950 | Rowney | Apr 2002 | B1 |
6837425 | Gauthier et al. | Jan 2005 | B1 |
20010005831 | Lewin et al. | Jun 2001 | A1 |
20010011247 | O'Flaherty et al. | Aug 2001 | A1 |
20010049620 | Blasko | Dec 2001 | A1 |
20020008147 | Coiton et al. | Jan 2002 | A1 |
20020026575 | Wheeler et al. | Feb 2002 | A1 |
20020132613 | Leung et al. | Sep 2002 | A1 |
Number | Date | Country | |
---|---|---|---|
20050121506 A1 | Jun 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10244044 | Sep 2002 | US |
Child | 10990289 | US |