US 8,024,260 B1Grant
Method for transmitting a code
Issue Date:2011-09-20
•24 Claims
•2 Drawing Sheets
Abstract
The present invention relates to a method for transmitting a code to a user in which the user transmits his or her financial account identifier information to a code allocation unit 3, the code allocation unit 3 transfers an amount of money to the financial institution 5 specified by the user and/or transfers an amount of money from the financial institution 5 specified by the user, thereby submitting the account identifier information and the code to be transmitted as additional information with this transfer and/or this debit, and the financial institution 5 forwards a receipt for the transfer and/or debit together with the additional information to the user.
Metadata
Assignee
- PayPal Inc.
Inventors
- Christian Hogl
- Josef Gundel
Application Information
Application Number:US 10/018,237
Filing Date:2000-06-09
Priority Date:1999-06-10
Art Unit:3695
Classifications
IPC:
G06Q40/00
Patent Drawings (2 sheets)
Description
[0001] The present invention relates to a method for transmitting a code to a user.
[0002] Traditionally, companies, offering services or selling goods are used to issuing personal codes to users who intend to buy or use the goods or services in order to facilitate identification of the users with the company. Furthermore, financial institutions, for example, are used to issuing personal identification numbers (PINs) to their customers to enable them to withdraw money from ATMs, conduct financial transactions, standing orders or use other services through a computer. Whenever a user initiates the first contact to such a company there is the problem of transmitting the personal code to him or her securely with minimal expense. Traditionally, personal codes will be handed over personally or sent by mail. Although both transmission methods are relatively secure, the expense associated with it is relatively high. It is either necessary to prepare a special tamper-proof letter, thereby ensuring that no third party can get information about the code without opening the letter, or the user has to show up in person with a company representative and submit a means of identification, for example his passport, in order to have his or her identity checked. Furthermore, companies, especially those offering online services, are used to transmitting personal codes via e-mail. Although this transmission method is very simple, it is also very insecure.
[0003] Once a personal code has been transmitted to a user, there is the additional problem of how to conduct future payment transactions with the user when he or she is buying or using the company's goods or services. The so-called direct debit method has been proven to be especially advantageous for conducting payment transactions. With this method, the user agrees in advance to have amounts of money transferred from his or her bank corresponding to the goods or services bought or used, thereby eliminating the need to explicitly confirm every single transaction in the future. With this method, the company submits the user's financial account identifier and the amount to be transferred to the user's financial institution. This can be especially simply effected by an electronic storage media, for example a diskette, or by an online remote data connection. The financial institution verifies the financial account identifier information and, after positive verification, transfers the respective amount of money from the user's account to the company's account. For the company conducting this direct debit method, there is the problem of guaranteeing that all data submitted to the financial institution are correct. For example, if the financial account identifier information cannot be assigned to a valid bank account, the financial institution will reject the transaction and levy relatively high charges to the company. Consequently, with new users, there is the added problem of verifying financial account identifier information along with transmitting personal codes in order to prevent problems with future payment transactions. Such a verification is very expensive and difficult, especially for a company that neither has personal contact with a new user nor, for example, any means of physically checking his or her credit card or ATM card at least shortly. Consequently, companies are used to omitting verification of financial account identifier information provided by new users, thereby disadvantageously incurring the risk of fraud and invalid transactions.
[0004] It is therefore the object of the present invention to provide a method for transmitting a code to a user which is secure, causes minimal expense and, therefore, costs associated with the transmission, and additionally provides a means for verifying financial account identifier information provided by the user.
[0005] This object is accomplished by the method according to claim 1, whereby advantageous modifications can be seen from the dependent claims.
[0006] According to the invention, the user transmits his or her financial account identifier information to a code allocation unit. Said code allocation unit transfers an amount of money to the financial institution specified by the user and/or transfers an amount of money from the financial institution specified by the user, thereby submitting the account identifier information and the code to be transmitted as additional information with this transfer and/or this debit. After having executed the transfer and/or the debit, the financial institution forwards a receipt for the transfer and/or debit together with the additional information to the user.
[0007] Advantageously, the invention provides a very secure transmission method. The secrecy of the transmission channel is guaranteed by the financial institution, as transaction details of the transfer or debit will not be divulged to any person outside a select group of confidential staff and, furthermore, only the legitimate user has access to his or her transfer or debit transaction receipts.
[0008] Furthermore, the method according to the invention provides a proof that the code has been transmitted to the account specified by the financial account identifier information through the additional information with the transfer or debit. The financial institution thus acts as an independent third party confirming the transaction. Consequently, the user will later not be able to repudiate having received the code. Thus, the transmission method according to the invention is almost equivalent to a registered letter, but less expensive and causes less effort.
[0009] In an advantageous embodiment of the invention, a verification unit of the financial institution, prior to executing the transfer and/or debit verifies the transfer and/or debit, data submitted by the allocation unit as to whether they can be assigned to a valid financial account of the user. In the case of a positive verification, the financial institution executes the transfer and/or debit initiated by the allocation unit. This measure ensures that the transfer and/or debit will not be executed unless there is a valid account of the user with the financial institution. For example, if his or her account is temporarily closed or non-existent, an invalid transaction can be avoided. Consequently, the method according to the invention obviates the need for separately verifying financial account identifier information or incurring future costs associated with invalid direct debit transactions.
[0010] Advantageously, in the case the verification of the financial account identifier information is negative, the verification unit of the financial institution transmits this result to the code allocation unit. In the code allocation unit, it can thus be decided whether to refrain from issuing a personal code to the user but rather contact him or her through another communication channel, if necessary.
[0011] Advantageously, the user furthermore submits identification data to the code allocation unit. These identification data are being submitted together with the account identifier information when initiating the transfer and/or debit. The verification unit verifies the identification data in combination with the account identifier information. Thus, not only the principal validity of the account identifier information can be verified, but also whether the account identifier information matches the specified user.
[0012] The transmission of the identification data and/or financial account identifier information of the user, the money transfer and/or debit and/or the transmission of the transfer or debit transaction receipt can advantageously be effected by a remote data connection. This can facilitate the method according to the invention very much. Furthermore, by using a remote data connection, the code can very quickly be transmitted to the user. The remote data connection can, for example, be effected through a computer network and/or an automatic telephone interface, for example an interactive voice response system.
[0013] In an advantageous embodiment of the method according to the invention, the code consists of at least two partial codes, whereby one code is being transmitted by the method according to the invention as an additional information with the transfer and/or debit and another partial code is being transmitted to the user by an alternate transmission method. This embodiment has the advantage that a third party, even in the case of getting access to the code transmitted by the method according to the invention, is being prevented from using it fraudulently, because the resulting code effectively used later consists of the at least two partial codes. Even if the other partial code is being transmitted by a relatively insecure method, such as the internet or the telephone, the probability of a third party getting access to both partial codes is very low. This embodiment thus provides a very secure code transmission method.
[0014] Advantageously, the identification data transmitted by the user to the allocation unit comprise at least the user's full name. Furthermore, the financial account identifier information transmitted by the user to the code allocation unit comprises at least the bank account number or credit card number and/or the name or bank code number of the financial institution or the credit card company.
[0015] Furthermore, the financial institution can also forward a transfer or debit transaction receipt to the allocation unit. Thus, through the receipts of the financial institution, not only the user, but also the party operating the code allocation unit will be advantageously provided with a means of proving the code transmission. This embodiment of the method according to the invention is almost equivalent to a registered letter with delivery confirmation, avoiding the drawbacks associated with sending letters.
[0016] Embodiments of the method according to the invention will be described in detail with references to the enclosed FIGURE.
[0017] The FIGURE schematically depicts a system for conducting the method according to the invention.
[0018] Reference number 1 refers to an input unit of a user intending to obtain a code from a company, for example, in order to use the company's services. The input unit can, for example, be a computer or a telephone system. The company features a code allocation unit 3. This code allocation unit 3 can, for example, be the company's central computer or a system of connected single computers. The code to be allocated can be any information submitted to a user in order to enable him to identify himself or herself to any party. The code can be a permanent personal access code such as a PIN. Furthermore, the code can be a one-time code such as a TAN (transaction number).
[0019] The user's input unit 1 and the company's allocation unit 3 are connected by some form of remote data connection 2. The remote data connection can, for example, be a computer network such as the internet or an automatic telephone interface such as an interactive voice response system. The user transmits his or her financial account identifier information through the input unit 1 via the remote data connection 2 to the code allocation unit 3. In this context, the term “financial account identifier information” refers to any collection of data that allow to establish some form of financial transaction with the user. The term “financial institution” generally refers to an entity through which financial transactions can be conducted. Obviously, the term also comprises a network of single institutions, for example the user's bank, the company's bank and for example, the ACH (Automated Clearing House). The financial transactions can thus be effected, for example, through an account with a financial institution, such as a bank or savings bank, or a credit card account. The financial account identifier information provided by the user comprises of his or her bank account number or credit card number and the name or bank code number of his or her financial institution or credit card company.
[0020] The code allocation unit 3 then transfers an amount of money to the financial institution specified by the user, thereby submitting the financial account identifier information and, if necessary, the user's identification data. After the new user's data have been transmitted, the money transfer can be effected automatically. Furthermore, the code to be transmitted is being transmitted as additional information with this transfer. The term “additional information” refers to any information transmitted in association with the money transfer. This information can be transmitted in unencrypted or encrypted form, additionally to the money transfer data or contained therein.
[0021] Such transmissions can, for example, be effected in the following ways: with a money transfer to a financial institution, a payment reference can be specified. This payment reference can indicate the code to be transmitted. Advantageously, a very small amount of money, for example EUR 1.00 is being transferred. Furthermore, the code to be transmitted can be contained within the amount of money to be transferred. For example, if the code 1498 is to be transmitted, an amount of EUR 14.98 could be transferred. The amount transferred can later be billed as an expense to the user. The money transfer can be effected through a remote data connection 4 between the code allocation unit 3 and the financial institution 5.
[0022] The financial institution 5 advantageously features a verification unit which verifies the money transfer data received from the code allocation unit as to whether they can be assigned to a valid financial account of the user. For example, it is being verified whether the account number exists and, if applicable, whether it exists for the specified user. In the case of a positive validation, the financial institution 5 executes the money transfer initiated by the allocation unit 3 and credits the respective amount of money to the users account. A receipt for the money transfer together with the additional information is being transmitted to the user via another connection 6, which can also be a remote data connection 6 such as a computer network or an automatic telephone interface. Furthermore, it is possible to forward the receipt to the user by an account balance statement printer.
[0023] Additionally, the financial institution 5 can also forward a receipt for the money transfer to the allocation unit 3 in order to provide the party operating the code allocation 3 unit with a means of proving the code transmission.
[0024] The method according to the invention provides an especially simple way of transmitting a personal code to a new user. All the user has to know is how to extract the code from the additional information associated with the money transfer. This can be communicated by the company issuing the code or by another party, for example over the internet in a public forum.
[0025] Simultaneously with the transmission, it is verified that the financial account identifier information is correctly specified by the user, because only by doing so will he or she be able to receive the money transfer. This is especially important for future payment transactions between the user and the company offering services or selling goods. Furthermore, the user will receive his or her code very quickly, as the time needed for the transmission depends only on the time needed for the money transfer by the financial institution 5.
[0026] It is being remarked that the term “remote data connection” not only refers to an online connection, but also to offline connections, as long as some form of data transfer between the respective units is effected. For example, it could also be possible to ship data storage media.
[0027] If the verification unit of the financial institution 5 yields a verification result indicating that the account identifier information submitted is invalid, the financial institution 5 does not carry out the money transfer. Advantageously, this result is being transmitted to the verification and allocation unit via a remote data connection 4. In this case, it can thus be decided in the code allocation unit whether to initiate another contact to the user 1, for example through the remote data connection 2, or whether to refrain from issuing a personal code to the respective user.
[0028] In another embodiment of the method according to the invention, the code to be used later by the new user consists of two or more partial codes. For example, the first partial code represents the first four digits of the effective code and the second partial code represents the last four digits. The effective code could, for example, also be generated by multiplying the two partial codes or by applying some other computation known to the user. One partial code is being transmitted to the user using the method according to the invention and the other partial code or a plurality of other partial codes by an alternate transmission method that may be not so secure. For example, the second partial code can be sent over a computer network such as the internet to the user.
[0029] This embodiment of the method provides an increased level of security, because an unauthorized person, even when getting access to the partial code transmitted by the method according to the invention, still has no information about the resulting code effectively used later. The probability of that person getting access to both or all partial codes is very low.
[0030] In another embodiment of the invention, the code transmission will be effected by a debit rather than a transfer of a small amount of money from the financial institution specified by the new user. With this debit as well, the account identifier information and as additional information the code to be transmitted are specified. The method used in this embodiment of the invention corresponds to the method described above, whereby in each case a debit rather than a transfer is executed.
[0031] Furthermore, both a transfer and a debit of the same amount of money can be executed simultaneously. Although this method slightly increases the expense, however, it will have a neutral effect on the new user's account balance.
Claims
The invention claimed is:
1. A method comprising:
receiving financial account identifier information of a user at a code allocation unit;
generating an access code for the user, the access code being to identify the user to a business entity; and
from the code allocation unit, effecting a value transfer utilizing the financial account identifier information and the access code, the access code being reflected in an amount of value associated with the value transfer so as to be transmitted to the user together with a receipt for the value transfer.
2. The method of claim 1, wherein the value transfer is a money withdrawal transaction.
3. The method of claim 1, wherein the generated access code is equal to the amount of money associated with the value transfer.
4. The method according to claim 1, wherein the value transfer is a money deposit transaction.
5. The method according to claim 1, wherein the effecting of the value transfer is by a remote data connection.
6. The method according to claim 1, wherein the access code is to be transmitted to the user by one or more of a remote data connection and an account balance statement printer.
7. The method according to claim 6, wherein the remote data connection is a computer network or an automated telephone interface.
8. The method according to claim 1, wherein:
the access code comprises at least two partial codes; and
a first partial code from the at least two partial codes is to be transmitted to the user together with the receipt for the value transfer and a second partial code from the at least two partial codes is to be transmitted by an alternative method to the user.
9. The method according to claim 1, further comprising receiving the identification data of the user at the code allocation unit.
10. The method according to claim 1, wherein the financial account identifier information comprises at least one of a group including:
data associated with a bank account number; and
data associated with a credit card number of the user.
11. The method according to claim 1, further comprising receiving the receipt for the value transfer at the allocation unit.
12. A machine-readable medium having instruction data to cause a machine to:
receive financial account identifier information of a user;
generate an access code for the user, the access code being to identify the user to a business entity; and
effect a value transfer utilizing the financial account identifier information and the access code, the access code being reflected in an amount of value associated with the value transfer so as to be transmitted to the user together with a receipt for the value transfer.
13. The machine-readable medium of claim 12, wherein the value transfer is a money withdrawal transaction.
14. The machine-readable medium of claim 12, wherein the access code is reflected in an amount of money associated with the value transfer.
15. The machine-readable medium according to claim 12, wherein the value transfer is a money deposit.
16. The machine-readable medium according to claim 12, wherein the code allocation unit is to effect the value transfer by a remote data connection.
17. The machine-readable medium according to claim 12, wherein the access code is to be transmitted to the user by one or more of a remote data connection and an account balance statement printer.
18. The machine-readable medium according to claim 17, wherein the remote data connection is a computer network or an automated telephone interface.
19. The machine-readable medium according to claim 12, wherein:
the access code comprises at least two partial codes; and
a first partial code from the at least two partial codes is to be transmitted to the user together with the receipt for the value transfer and a second partial code from the at least two partial codes is to be transmitted by an alternative method to the user.
20. The machine-readable medium according to claim 12, wherein the code allocation unit is to receive identification data of the user.
21. The machine-readable medium according to claim 12, wherein the financial account identifier information comprises at least one of a group including:
data associated with a bank account number; and
data associated with a credit card number of the user.
22. The machine-readable medium according to claim 12, wherein the code allocation unit is to receive the receipt for the value transfer.
23. A method comprising:
receiving financial account identifier information of a user at a code allocation unit;
from the code allocation unit effecting a money transfer transaction utilizing the financial account identifier information;
generating an access code for the user utilizing an amount of money associated with the money transfer transaction, the access code being to identify the user to a business entity; and
submitting the access code to be transmitted to the user together with a receipt for the money transfer transaction.
24. A system comprising:
a receiver to receive financial account identifier information of a user;
a generator to generate an access code for the user, the access code being to identify the user to a business entity; and
a transfer module to effect a value transfer utilizing the financial account identifier information and the access code, the access code being reflected in an amount of value associated with the value transfer so as to be transmitted to the user together with a receipt for the value transfer.
Patent Citations (59)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3823308(A) | 1974-07-01 | Goldberg | Applicant |
| US3852571(A) | 1974-12-01 | Hall et al. | Applicant |
| US3896266(A) | 1975-07-01 | Waterbury | Applicant |
| US4471216(A) | 1984-09-01 | Herve | Applicant |
| US5053606(A) | 1991-10-01 | Kimizu | Applicant |
| US5416306(A) | 1995-05-01 | Imahata | Applicant |
| US5532464(A) | 1996-07-01 | Josephson et al. | Applicant |
| US5679938(A) | 1997-10-01 | Templeton et al. | Applicant |
| US5708422(A) | 1998-01-01 | Blonder et al. | Applicant |
| US5750972(A) | 1998-05-01 | Botvin | Applicant |
| US5770843(A) | 1998-06-01 | Rose et al. | Applicant |
| US5778178(A) | 1998-07-01 | Arunachalum | Applicant |
| US5793028(A) | 1998-08-01 | Wagener et al. | Applicant |
| US5870456(A) | 1999-02-01 | Rogers | Applicant |
| US5877482(A) | 1999-03-01 | Reilly | Examiner |
| US5883810(A) | 1999-03-01 | Franklin et al. | Applicant |
| US5903878(A) | 1999-05-01 | Talati et al. | Applicant |
| US5907801(A) | 1999-05-01 | Albert et al. | Applicant |
| US5907832(A) | 1999-05-01 | Pieterse et al. | Applicant |
| US5963917(A) | 1999-10-01 | Ogram | Applicant |
| US5987500(A) | 1999-11-01 | Arunachalam | Applicant |
| US6029150(A) | 2000-02-01 | Kravitz | Applicant |
| US6052675(A) | 2000-04-01 | Checchio | Applicant |
| US6212556(B1) | 2001-04-01 | Arunachalam | Applicant |
| US6226624(B1) | 2001-05-01 | Watson et al. | Applicant |
| US6497359(B1) | 2002-12-01 | Chihara | Applicant |
| US6836765(B1) | 2004-12-01 | Sussman | Applicant |
| US7430537(B2) | 2008-09-01 | Templeton et al. | Applicant |
| US2002/0077837(A1) | 2002-06-01 | Krueger et al. | Applicant |
| US2008/0312998(A1) | 2008-12-01 | Templeton et al. | Applicant |
| AU199928111(B2) | 2000-02-01 | Applicant | |
| AU200197079(B2) | 2002-06-01 | Applicant | |
| DE4425271(A1) | 1996-01-01 | Applicant | |
| DE4425271(A1) | 1996-01-01 | Applicant | |
| DE19628045(A1) | 1998-01-01 | Applicant | |
| DE19628045(A1) | 1998-01-01 | Applicant | |
| DE19634418(A1) | 1998-03-01 | Applicant | |
| DE19634418(A1) | 1998-03-01 | Applicant | |
| DE10022973(A1) | 2001-02-01 | Applicant | |
| DE19926472 | 2001-11-01 | Applicant | |
| EP519843 | 1992-12-01 | Applicant | |
| EP527639 | 1993-02-01 | Applicant | |
| EP216521 | 1993-11-01 | Applicant | |
| EP400911 | 1993-11-01 | Applicant | |
| EP848360 | 1998-06-01 | Applicant | |
| JP2004519748(A) | 2004-07-01 | Applicant | |
| JP2008257747(A) | 2008-10-01 | Applicant | |
| JP2010124604 | 2010-06-01 | Applicant | |
| WO-9506294 | 1995-03-01 | Applicant | |
| WO-9516971 | 1995-06-01 | Applicant | |
| WO96/38813 | 1996-12-01 | Examiner | |
| WO97/10560 | 1997-03-01 | Examiner | |
| WO-9713228(A1) | 1997-04-01 | Applicant | |
| WO99/08242 | 1999-02-01 | Applicant | |
| WO-9923622 | 1999-05-01 | Applicant | |
| WO-9966436(A1) | 1999-12-01 | Applicant | |
| WO-0077754(A1) | 2000-12-01 | Applicant | |
| WO-0205224 | 2002-01-01 | Applicant | |
| WO-0205224(A3) | 2002-01-01 | Applicant |
Non-Patent Literature (58)
- “International Search Report”, PCT/US01/21725, (Aug. 29, 2002).Applicant
- “U.S. Appl. No. 09/901,954, Notice of Allowance mailed Jun. 19, 2008”, 10 pgs.Applicant
- “U.S. Appl. No. 09/901,954 Advisory Action mailed Mar. 3, 2006”, 3 pgs.Applicant
- “U.S. Appl. No. 09/901,954 Non Final Office Action mailed Jan. 21, 2005”, 10 pgs.Applicant
- “U.S. Appl. No. 09/901,954 Non Final Office Action mailed Feb. 13, 2007”, 11 pgs.Applicant
- “U.S. Appl. No. 09/901,954 Response filed Mar. 14, 2006 to Advisory Action mailed Mar. 3, 2006”, 3 pgs.Applicant
- “U.S. Appl. No. 09/901,954 Response filed Dec. 19, 2005 to Non Final Office Action mailed Jan. 21, 2005”, 11 pgs.Applicant
- Automated Clearing House Rules, “A Complete Guide to Rules and Regulations Governing the ACH Netowrk”, The National Automated Clearing House Assocation, Herndon VA., (1999), OR 4, OR 10, OG 19, OG 46-48.Applicant
- Automated Clearing House Rules, “A Complete Guide to Rules and Regulations Governing the ACH Network”, The National Automed Clearing House Assocation, Herndon VA., (1999).Applicant
- Horne, Doak D., “Letter from Gowling Lafleur Henderson LLP to Park, Vaughan and Fleming LLP, Jul. 21, 2004”.Applicant
- Oregon Department of Revenue, “ACH Debit Electronic Funds Transfer: Program Guide”, [Online]. Retrieved from the Internet: <URL:http://www.dor.state.or.us/19forms/206-029.pdf>, (Feb. 1999).Applicant
- Telstra Corporation Limited, “Statment of Grounds of Opposition and Particulars Relating to Each Ground In the Matter of Opposition ot Australian Patent Application No. 2001271968 in the name of PayPal, Inc. Dated Sep. 17, 2007”.Applicant
- “U.S. Appl. No. 09/901,954, Advisory Action mailed Sep. 6, 2007”, 3 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Appeal Brief filed May 11, 2006”, 30 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Examiner Interview Summary mailed Jan. 21, 2005”, 3 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Examiner Interview Summary mailed Feb. 5, 2008”, 2 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Final Office Action mailed Jul. 10, 2007”, 11 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Non Final Office Action mailed Dec. 19, 2007”, 10 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Response filed Jan. 18, 2008 to Non Final Office Action mailed Dec. 19, 2007”, 11 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Response filed Jan. 26, 2006 to Final Office Action mailed Dec. 19, 2005”, 18 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Response filed Feb. 28, 2005 to Non Final Office Action mailed Jan. 21, 2005”, 15 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Response filed Mar. 27, 2007 to Non Final Office Action mailed Feb. 13, 2007”, 19 pgs.Applicant
- “U.S. Appl. No. 09/901,954, Response filed Aug. 20, 2007 to Final Office Action mailed Jul. 10, 2007”, 20 pgs.Applicant
- “Australian Application No. 2008203005, Examiner's First Report on Patentability mailed Oct. 29, 2008”, 4 pgs.Applicant
- “Australian Application Serial No. 2001271968, Amended Statement of Grounds of Opposition and Particulars Related to Each Ground mailed Feb. 11, 2008”, 11 pgs.Applicant
- “Australian Application Serial No. 2001271968, Letter from Examiner mailed Nov. 19, 2007”, 2 pgs.Applicant
- “Australian Application Serial No. 2001271968, Letter to Examiner Dec. 17, 2007”, 1 pgs.Applicant
- “Australian Application Serial No. 2001271968, Letter to examiner mailed Oct. 15, 2007”, 2 pgs.Applicant
- “Australian Application Serial No. 2001271968, Notice of Acceptance mailed Mar. 2, 2007”, 3 pgs.Applicant
- “Australian Application Serial No. 2001271968, Notice of Opposition mailed Jun. 15, 2007”, 1 pgs.Applicant
- “Australian Application Serial No. 2001271968, Office Action mailed Nov. 15, 2005”, 2 pgs.Applicant
- “Australian Application Serial No. 2001271968, Office Action mailed Nov. 21, 2006”, 2 pgs.Applicant
- “Australian Application Serial No. 2001271968, Response filed Jan. 11, 2007 to Office Action mailed Nov. 21, 2006”, 23 pgs.Applicant
- “Australian Application Serial No. 2001271968, Response filed Jan. 25, 2008 to Statement of Grounds and Particulars mailed Jan. 10, 2008”, 2 pgs.Applicant
- “Australian Application Serial No. 2001271968, Response filed Oct. 12, 2006 to Office Action mailed Nov. 15, 2005”, 20 pgs.Applicant
- “Australian Application Serial No. 2001271968, Statement of Grounds of Opposition and Particulars Relating to Each Ground mailed Sep. 17, 2007”, 8 pgs.Applicant
- “Australian Application Serial No. 2001271968, Supplemental Response filed Oct. 25, 2006 to Office Action mailed Nov. 15, 2005”, 17 pgs.Applicant
- “Australian Application Serial No. 2008203005, Response filed Aug. 10, 2009 to Office Action mailed Oct. 29, 2008”, 2 pgs.Applicant
- “Canadian Application Serial No. 2,412,184, Response filed Feb. 29, 2008 to Office Action mailed Aug. 31, 2007”, 21 pgs.Applicant
- “Canadian Application Serial No. 2,412,184, Office Action mailed Jan. 3, 2007”, 5 pgs.Applicant
- “Canadian Application Serial No. 2,412,184, Office Action mailed Aug. 31, 2007”, 5 pgs.Applicant
- “Canadian Application Serial No. 2,412,184, Response filed May 30, 2007 to Office Action mailed Jan. 3, 2007”, 16 pgs.Applicant
- “European Application Serial No. 00942046.4-2221, Office Action mailed Apr. 30, 2007”, w/translation, 6 pgs.Applicant
- “European Application Serial No. 00942046.4-2221, Response filed Oct. 31, 2007 to Office Action mailed Apr. 30, 2007”, 10 pgs.Applicant
- “European Application Serial No. 00942046.4-2221, Summons to Attend Oral Proceedings mailed Mar. 3, 2010”, 3 pgs.Applicant
- “European Application Serial No. 00942046.4-2221, Written Statements Filed Nov. 30, 2010”, 31 pgs.Applicant
- “European Application Serial No. 01951030.4, Office Action mailed Jan. 20, 2006”, 15 pgs.Applicant
- “European Application Serial No. 01951030.4, Response filed Mar. 30, 2006 to Office Action mailed Jan. 20, 2006”, 9 pgs.Applicant
- “European Application Serial No. 01951030.4, Summons to Attend Oral Proceedings mailed Jul. 21, 2008”, 7 pgs.Applicant
- “European Application Serial No. 10158849.9, Extended European Office Action mailed Jun. 18, 2010”, 7 pgs.Applicant
- “European Application Serial No. 10158849.9, Response filed Jan. 20, 2011 to EP Search Report mailed Jun. 18, 2010”, 4 pgs.Applicant
- “International Application Serial No. PCT/EP00/05359, International Search Report mailed Nov. 16, 2000”, 2 pgs.Applicant
- “International Application Serial No. PCT/US01/21725, International Preliminary Examination Report mailed Dec. 10, 2004”, 5 pgs.Applicant
- “International Application Serial No. PCT/US01/21725, International Search Report mailed Aug. 22, 2002”, 3 pgs.Applicant
- “International Application Serial No. PCT/US01/21725, Written Opinion mailed Aug. 24, 2004”, 4 pgs.Applicant
- “Japanese Application Serial No. 2002-508754, Preliminary Amendment mailed Jul. 2, 2008”, 14 pgs.Applicant
- “Japanese Application Serial No. 2002-508754, Office Action mailed May 30, 2011”, 7 pgs.Applicant
- “Japanese Application Serial No. 2008-173992, Office Action mailed May 18, 2011”, 3 pgs.Applicant