© 2026 Zoe. All rights reserved.
Zoe is a legal information platform. Always consult the Federal Register of Legislation for authoritative text.
[2001] FCA 445
Federal Court of Australia
2001-07-01
Heerey J
Original judgment source is linked above.
Welcome Real-Time SA v Catuity Inc [2001] FCA 445 PATENTS - patent for process and device for operation of smart cards in connection with traders' loyalty programs - claim for infringement and cross-claim for revocation - construction - "Behaviour file", "coupon" - whether infringement - whether definite steps to use infringing system before priority date - whether manner of manufacture - whether lacking in novelty - whether obvious - whether useful - whether lacking in clarity - sufficiency or description - fair basis WORDS AND PHRASES - "Behaviour file" "coupon" Patents Act 1990 (Cth) ss 7, 13(1), 18(1)(a), 40(2)(a), 40(3), 119(1)(b) Patents Act 1977 (Imp) s 64 Statute of Monopolies 1623 (Imp) s 6 Constitution of the United States Art 1, s 8, cl 8 Flexible Steel Lacing Company v Beltreco Ltd (2000) 49 IPR 331 at [70]-[81] followed Rhone-Poulenc Agrochimie SA v UIM Chemical Services Pty Ltd (1986) 12 FCR 477 at 496 applied CCOM Pty Ltd v Jiejing Pty Ltd (1993) 27 IPR 577 at 627 followed Helitune Ltd v Stewart Hughes Ltd [1991] FSR 171 mentioned Lubrizol Corporation v Esso Petroleum Ltd [1998] RPC 727 mentioned Dyno Nobel Asia Pacific Ltd v Orica Australia Pty Ltd (1999) 99 FCR 151 at [222] mentioned Rolls Royce Ltd's Application [1963] RPC 251 mentioned Re Brown (1899) 5 ALR 81 mentioned Commissioner of Patents v Lee (1913) 16 CLR 138 mentioned Nielson v Minister for Public Works (NSW) (1914) 18 CLR 423 mentioned Re Kelvin & Hughes Ltd's Application (1954) 71 RPC 103 mentioned Rogers v Commissioner of Patents (1910) 10 CLR 701 mentioned ESP's Application (1945) 62 RPC 87 mentioned W's Application (1914) 31 RPC 141 mentioned International Business Machines Corporation v Commissioner of Patents (1991) 33 FCR 218 followed CCOM Pty Ltd v Jiejing Pty Ltd (1994) 51 FCR 260 applied Commissioner of Patents v Microcell Ltd (1959) 102 CLR 232 at 249 distinguished National Research Development Corporation v Commissioner of Patents (1959) 102 CLR 252 applied Joos v Commissioner of Patents (1972) 126 CLR 611 at 616 mentioned Crane v Price (1842) 3 Man & G 580, 134 ER 239 mentioned Re GEC's Application (1942) 60 RPC 1 mentioned Re Cementation Co Ltd's Application (1945) 62 RPC 151 mentioned Rantzen's Case (1946) 64 RPC 63 mentioned Burroughs Corp Application [1974] RPC 147 at 161 mentioned International Business Machines Corporation's Application [1980] FSR 564 mentioned State Street Bank & Trust Co v Signature Financial Group 149 F 3d 1368 (1998) discussed Meyers Taylor Pty Ltd v Vicarr Industries Ltd (1977) 137 CLR 228 at 235 applied Flour Oxidising Co Ltd v Carr Atco Ltd (1908) 25 RPC 428 at 457 mentioned General Tyre & Rubber Co v Firestone Tyre & Rubber Co Ltd [1972] RPC 457 at 485-6 mentioned Minnesota Mining and Manufacturing Co v Beiersdorf (Australia) Ltd (1980) 144 CLR 253 at 293 applied Aktiebolaget Hassle v Alphapharm Pty Ltd (2000) AIPC 91-636 at [69] applied Sach v Hartford Electric Co 47 F 2d 743 (1931) at 748 mentioned Fawcett v Homan (1896) 13 RPC 398 at 405 applied Upper Hunter County District Council v Australian Chilling & Freezing Co Ltd (1968) 118 CLR 429 applied Kimberley-Clark Australia Pty Ltd v Araco Trading International Pty Ltd (2001) 177 ALR 460 at [25] applied Universal Oil Products Co v Monsanto Co (1972) 46 ALJR 658 at 661 applied Décor Corporation Pty Ltd v Dart Industries Inc (1988) 13 IPR 385 at 393, 400 applied Pearce v Paul Kingston Pty Ltd (1992) 23 IPR 303 at 307-308 applied Rehm Pty Ltd v Websters Security Systems (International) Pty Ltd (1988) 11 IPR 281 at 302-305 applied WELCOME REAL-TIME S.A. v CATUITY INC & ORS V 526 OF 2000 HEEREY J 17 MAY 2001 MELBOURNE
THE COURT ORDERS THAT:
I INTRODUCTION 3 II CONSTRUCTION 4
I INTRODUCTION 1 The applicant Welcome Real-Time SA is the proprietor of Australian patent no. 712925 (the Patent). The invention disclosed is for a process and device for the operation of smart cards in connection with traders' loyalty programs. Smart cards are cards which contain a microprocessor or chip with the capacity for receiving and storing information. With loyalty programs a trader promotes goods or services by offering rewards based on prior transactions, for example according to the value of goods or services previously acquired or the frequency of such transactions. Rewards may take the form of a price discount or a free supply of goods or services. 2 The priority date of the Patent is 22 January 1996. Its terms are an English translation of an earlier patent granted in France. 3 The applicant claims the respondents have infringed the Patent by the operation of their CiT/Transcard system from August 1996. 4 The respondents say that on the proper construction of the claims of the Patent their system does not infringe. In the alternative, they rely on the defence under s 119(1)(b) of the Patents Act 1990 (Cth) (the Act) in that immediately before the priority date they had taken definite steps to use the process the subject of the Patent. 5 The respondents have also cross-claimed seeking revocation of the Patent. They say that the invention the subject of the Patent is not a matter of manufacture: s 18(1)(a) of the Act. They say further that it is generally inconvenient within the meaning of s 6 of the Statute of Monopolies, lacks novelty and is obvious. They rely also on lack of utility, lack of clarity, insufficiency of description and want of fair basis.
The field of the invention 6 Loyalty programs have been a feature of retail trading for many years. It is an incentive for a customer to deal with a particular trader if, after a specified number or value of transactions, a free benefit will be received. Earlier examples included Green Shield stamps. The customer received a stamp at the time of purchase, collected a prescribed number of stamps, sent them to a central location and received a gift. Another example began in the early 1980s when airlines in the United States, and shortly afterwards in Australia, introduced frequent flyer programs. A passenger flying for a certain mileage became entitled to a specified free fare. 7 The operation of such programs involved cost and inefficiency. Typically, information about customers' entitlements had to be sent to some central repository and maintained in a retrievable form. Evidence of entitlement had to be sent by post or some other means to the customer who would in turn have to send off a claim for a benefit. The trader would then have to check the entitlement and forward the reward. All this was a cost. Moreover, documents evidencing entitlement might be lost or fraudulently duplicated. 8 With the advent of smart cards it became apparent that some of these problems could be overcome. If the information relating to the customer's entitlement could be stored on the card and read at a point of sale (POS) terminal, benefits to which the customer became entitled could be provided immediately at the retail outlet. 9 But, easier said than done. The more particular problems encountered in applying smart card technology to loyalty programs can be illustrated by the development of the invention the subject of the Patent by its inventors M Aneace Haddad and M Bernard Chevalier. In 1995 the applicant's parent company High Co S.A. became a shareholder in Carte Jeunes SA, a company that operates the Carte Jeunes card on behalf of the French Ministry of Youth and Sports. The card is intended to encourage merchants to provide discounts to young people in France. Initially the Carte Jeunes card was a "flash card", that is to say a card which is simply shown to a participant merchant to obtain a discount. The Ministry decided to investigate the conversion of the Carte Jeunes card to a chip card. 10 By 1995 most loyalty programs were based on a "scheme-wide currency" which centred on there being a single points counter for the accumulation of points within a customer data base. In some of these programs, such as airline frequent flyer programs, cards were not electronic; the card contained a customer identification number which was typed into a terminal when the customer checked in. Other versions had a card with a magnetic stripe which dispatched information concerning a processed transaction to a central data base where the points balance for each customer resided. Account statements would be sent to each customer by mail indicating the points balance and information on rewards obtainable. These centrally processed scheme-wide currency programs (whether or not involving electronic cards) were relatively straightforward as there was usually just one points counter and all participating merchants' transactions sent points to the same counter. 11 In 1995 Shell in the United Kingdom and Takashimaya in Singapore introduced scheme-wide currency programs based on chip cards which removed the need to send statements or redeem awards by mail. 12 High Co's work with Carte Jeunes, starting in 1995, progressed through a number of stages. First there was a system based on scheme-wide Carte Jeunes "currency" in which the customers' points counter resided in the card's chip as well as on a central data base. All participating merchants would give points in the form of Carte Jeunes "currency" which was exchangeable for payment at any participating merchant. The balance of the "currency" was contained in the card and could be provided at each transaction, thus obviating the need for statements or reward request forms. However, the Bank of France considered that the proposed Carte Jeunes "currency" was too like real money and could compete with cash in the French economy. Apart from that problem, investigations revealed it was going to be difficult to persuade many small traders to participate in universal point schemes. Unless all invested in electronic payment terminals it could not be stated that points could be redeemed at any Carte Jeunes merchant. 13 A second stage was a proposal that universal points could be redeemed only at participating cinemas. However this proposal was not implemented because Carte Jeunes considered a currency valid only at cinemas was of limited benefit to card holders. 14 These examples illustrate the difficulty in developing a system which linked together many diverse traders with different technical infrastructures and promotional methods. Since a universal scheme-wide currency proved impractical, attention turned to exploring systems operated by single chains where points accumulated within the chain did not mingle with points accumulated elsewhere and where specific rewards could be provided for specific merchants or groups of merchants. To implement multiple distinct merchant programs on a single chip card, the inventors became aware that the chip card based system needed to be capable of using multiple counters within the chip, each counter dedicated to an individual merchant or chain of merchants. 15 The world's leading supplier of chip card technology was the French company Gemplus. Gemplus proposed to Carte Jeunes a chip card with several points counters. However, the problem remained that with multiple loyalty programs, if a chip card was intended to function with loyalty programs A and B, the card would have to be produced with loyalty programs A and B predefined within the chip's data memory. Each program operator would have to ensure that they used only the memory space which had been assigned to them. This allocation could not later be amended. A customer's chip card would carry all available loyalty programs regardless of whether or not the customer participated in all of them. With the then available technology there was a limit of about ten programs which could be loaded to pre-assigned memory locations for merchants. The inventors recognised that such types of chip card would not be able to provide a system which could be implemented in an environment consisting of potentially thousands of different merchants running their own distinct loyalty programs. 16 The next proposal made by Gemplus to Carte Jeunes was to create co-branded chip cards for local merchants. For example, a chain of cinemas in Paris would issue their own Carte Jeunes cards with their name on it and their dedicated loyalty program memory zoned within the chip. Merchants who did not have nationwide outlets would be limited to those co-branded cards. However, that would effectively limit the merchants' loyalty program only to those cards with the merchants' co-branded cards. Most merchants wanted to provide loyalty rewards to all Carte Jeunes card holders in their geographic area. 17 The inventors' thinking at the time as to these practical limitations was that the POS terminal of a particular merchant would have to be configured to read and write to a single memory zone or file with a specific address with which it had been predefined. For example, merchant A's terminal would be programmed to always function with memory zone A in the chip. Thus the number of merchants which could participate in the loyalty system was limited. 18 The solution arrived at by the inventors, which is said to be the invention of the Patent, is to "dynamically" store each merchant's loyalty program in a separate record of a file called the Behaviour file. The merchant's loyalty program is added to the Behaviour file by the POS terminal the first time the card holder uses the card at that merchant's store. Behaviour information and a points counter for merchants that the card holder never visits are never added to the chip card. There is not a pre-allocated memory slot for such non-visited merchants. Any chip card can still have only just a few points counters but the first points counter of any one card would be allocated to one merchant, while the same points counter on another card could be allocated to another merchant. The approach of the invention was to allow chip cards with a small memory capacity to be used across thousands of merchants each operating their own proprietary loyalty program. M Haddad knew of no other system before the priority date of the Patent that dynamically supported a plurality of different merchants each operating a different loyalty program within the chip card's memory, and each program being added only to those cards actually participating in the loyalty program. This was because all the previous systems lacked a Behaviour file indicating which merchant loyalty programs the customer was involved in, within a much larger pool of merchant loyalty programs available on the same chip card network.
Principles 19 The case law on the approach to be taken by a court in the construction of patents has recently been comprehensively reviewed by Hely J in Flexible Steel Lacing Company v Beltreco Ltd (2000) 49 IPR 331 at [70] to [81]. I incorporate by reference and adopt the whole of that passage in these reasons. 20 It is accepted that all the expressions the subject of construction disputes in the present case are ordinary English words and not terms of art. 21 All that needs be added is the perhaps trite observation that the alleged infringement is to be ignored when construing the patent. Although the forensic contest will throw up the particular construction issues to be resolved, a patent must, as the saying goes, be construed as if the infringer had never been born.
The Patent 22 The Patent commences with a brief summary of the invention. It notes that the invention finds "a particularly important though non-exclusive application in the field of the processing of loyalty cards, presented by customers at the time of payment at a trader's". Thus with the invention "… it is possible to alter a trade offer on the basis of the a posteriori behaviour of the card holder, thus making it possible to grant him specific benefits in a customised and immediate manner, and which may moreover be recorded on the card." 23 I take the expression "alter a trade offer" to refer to alteration of an offer made to the public at large. For example, if a trader offers an item for $100, a loyalty program may stipulate that a cardholder who has already purchased items to the value of $500 may obtain the item for a 15 per cent discount. 24 The drawbacks of existing mail-based systems are noted, such as delays and limited reliability caused by loss of coupons and changes of address. But, according to the invention, the trader will be able to "recognise a customer on the basis of the frequency with which he calls in and the size of his spending. It will then be possible to grant him a specified definite benefit automatically and instantaneously." 25 The specification then sets out a statement of the method of the invention and advantageous embodiments which together are reflected in claim 1. It also sets out a statement of the device of the invention and advantageous embodiments which together are reflected in the device of claim 6. 26 It is said that advantageous embodiments of the method include the following provisions: " - the algorithmic processing includes a step of incrementing or decrementing the Points file by a pre-specified number of points; - the coupon is only printed if the number of points contained in the Points file is greater than a specified value; - the coupon is only printed and/or the Points file is only incremented or decremented if the Member file corresponds to specified criteria; - the Points file is incremented more or less depending on the amount of the purchase or payment operation; - the Points file is incremented more or less depending on frequency and/or on the nature of first, second or xth visit by the cardholder over a period of time of specified duration. - information corresponding to the operation is entered into a memory of a payment terminal located on the premises of said trader, said entered information is compared with information stored in storage means and relating to prespecified series of operations, and the results of these comparisons are processed in order to print a coupon and/or write to the Points file. It is thus possible to undertake promotional operations which are limited in time and pertain to a collection of traders belonging to the same network." 27 A "non-limiting" example of the invention is provided, with reference to drawings (figures 1, 2 and 3). 28 The manufacturers of suitable POS terminals and chip cards are identified. It is stated that the cards can be bank cards, personal credit cards or loyalty cards. 29 Embodiments of the Member file, the Behaviour file and the Points file according to the invention are then described "by way of example": Member file 18 Read code: Free Update code: RCode01 Field Format Width Card number 999999999 9 Type Alpha 2 Version 99 2 Present applications Y / N 9 Month/year of customization (manufacture) yymm 4 Month/year of 1st use yymm 4 Month/year of expiry yymm 4 Reserved Alpha 46
Behaviour file 21 Read code: Free Update code: Rcode12 Field Format Width Max number of traders 99 2 Number of traders recorded 99 2 Reserved Alpha 16
Field Format Width Traders (up to the No. of traders rec.): Trader code 99999 5 Business code Alpha 1 Date of first visit yymmdd 6 Date of last visit yymmdd 6 Number of visits this month 99 2 Spend this month 99999 5 Number of visits this year 999 3 Spend this year 999999 6 Total number of visits 999 3 Total spend 999999 6
Points file 22 (points counter) Balance read key : Free Debit key: Rkdebl Credit key: Rkcredl PIN (for access to the debit): Rcode13 30 After some description of encryption procedures, an example is provided of the device of figure 2. The particular program involves the grant of a discount based on the number of "operations" (presumably transactions) performed by the card holder within the month. It is said: "The invention thus enables the card holder to obtain two types of benefit separately or simultaneously:
card (4) with a chip (5), at a trader's, in which the contents of the memory (14) of the chip card are read and a coupon (12) is or is not printed on the basis of the information arising from the contents of said memory, 10
[b] characterized in that, with the memory of the chip card including [c] a first identification file (18), termed the Member file, identifying the card-holding customer, a [d] second accounting file (22), termed the Points file, [e] and a third file (21), termed the Behaviour file, relating to the behaviour of the card holder towards the user trader 15
or traders, [f] a specified algorithmic processing is performed [g] depen- dent, on the one hand, on the date of the operation and, [h] on the other hand, on the information contained in said 20
files, including the Behaviour file, [i] the algorithmic processing including a step of incrementing or decrementing the Point [sic] file by a predetermined number of points [j] depending on the frequency and/or the nature of first, second or xth visit by the card holder over a time period of specified 25
duration, [k] the coupon is printed only if the number of points contained in the Points file is greater than a specified value [l] then data is written to the Points file, 30
[m] new information is written to the Behaviour file, [n] and said coupon is or is not printed on the basis of the result of said algorithmic processing.
Claims 2 to 5 are variation of the method of claim 1. Claim 6 is a device claim similar in terms to claim 1. Claim 7 is a variation of claim 6. The claims other than claim 1 were not the subject of substantial dispute.
Behaviour file 35 It was not disputed that a file in this context means a collection of records or data or information stored for use by a computer. A file, whether a computer file or an ordinary physical file, usually contains records which have some commonality or relationship with each other, such as correspondence with a particular person or documents concerning a particular topic. 36 "Behaviour" in this context means "… observable actions; treatment shown to or towards another or others" (New Shorter Oxford Dictionary). In the Patent the behaviour with which the Behaviour file is concerned is that of the card holder "towards the user trader or traders" (claim 1 line 14). So in this context the behaviour of the card holder could include such conduct as visiting the premises of the trader or traders and, if so, how often, or spending money there and, if so, how much. 37 But, and at this point the parties diverge, what is the minimum information that a file must contain before it is a Behaviour file within the meaning of claim 1? The respondents contend that behaviour refers to more than just the presence of a trade code (or loyalty program ID) and is concerned with recency and frequency of dealings. They say that recency and frequency and monetary amount (RFM) are part of the concept of the Behaviour file. 38 The applicant argues that the trader code is the minimum field necessary. It is not necessary that the Behaviour file of the claims should have all of the data fields in the table of the example ([30] above) (i.e. date of first visit, date of last visit, number of visits this month etc). 39 In my opinion, the applicant's contention is to be preferred, for the following reasons. 40 The content of each of the three files referred to in claim 1 is identified in the claim: the content of the Member file is something identifying the cardholding customer; the content of the Points file is something counted; and the content of the Behaviour file is, as stated, something relating to the behaviour of the cardholder towards the user trader or traders. It is evident therefore that the Behaviour file and the Points file cannot be the same thing and that the Behaviour file must have something in it which does not include accumulated points. If there be any doubt as to this, the specification makes it clear that the Points file contains a points counter (claim 1 line 4) and the Behaviour file does not. 41 The algorithmic processing referred to in the claim is dependent, amongst other things, on information in the Behaviour file. Integers [h] and [m], in contrast to integer [l], use the terms "information" and "new information" rather than the term "data". Accordingly, upon first use of a card at a trader's premises (when there is no trader code in the Behaviour file) the Behaviour file contains the information that this customer has not previously attended this trader. This information arises from the absence of a trader code in the Behaviour file. The non-existence of a fact (for example, it is not raining today) is properly to be characterised as information. The processing proceeds to add new information, being the trader's trader code, to the Behaviour file. The algorithmic processing is dependent on that information. 42 Moreover, as the applicant submitted, there is no reason why the area set aside and structured for a Behaviour file (as in the example in the Patent) should not be regarded as a Behaviour file whether or not data is recorded in it. Physical files may exist in the sense of a folder being appropriated to a subject, labelled and structured (for example, by alphabetic tabs) before any documents are inserted. An electronic file is essentially the same in this regard. 43 The language "relating to the behaviour of the card holder towards the user trader or traders" is quite general. Information that on a given date a card holder has visited a trader for the first time tells us something about the behaviour of that card holder towards that trader. Applying the principles of construction discussed in Flexible Steel, I see no reason to read down or qualify that meaning. 44 The respondents argued that the reference to the singular "trader" suggested that "behaviour" is referring to something more than the identification of a trader. The short answer is that information that a card holder has visited a (singular) trader for the first time does convey more than the identification of that trader, namely that that card holder has visited that trader for the first time. 45 There is nothing in integers [i] to [j] (lines 20-25) which militates against the applicant's interpretation of "Behaviour file". The requirement of the claim that the algorithmic processing should include a step of incrementing or decrementing the points file depending on the frequency and/or the nature of the first, second or xth visit by the card holder over a time period of specified duration means no more than that the points file is incremented or decremented depending on the number of visits made to the trader, or the nature of such visits to the trader, during the currency of the program. "Frequency" in this context refers to the number of times something occurs during the currency of a program and not to the number of times something occurs during a particular time interval during the currency of a program. Accordingly, these lines of the claim refer to the function of the Points file, which may accumulate points in a variety of ways during the currency of a program, not to the Behaviour file. It is wrong to say that "nature" cannot mean "amount" in an appropriate case because "amount" is referred to in claim 3. On the contrary, the dependency of claim 3 on claim 1 suggests that "nature" does include "amount" and the purpose of claim 3 is simply to narrow the broader claim 1.
Coupon 46 The issue here is whether "coupon" is (i) a document which represents entitlement, that is to say a "store of value", or (ii) whether it is something in the nature of a voucher evidencing a transaction. The former meaning is the respondents' case and the latter the applicant's. 47 I have no doubt that whatever be the meaning, in the context of the Patent an actual document or piece of paper is intended. This follows from the reference to the coupon being printed and the representation of what is obviously a document in 12 in figure 1. 48 "Coupon" derives from the French verb couper (to cut). It appears from the Oxford English Dictionary that the term was first used in the 1820s in relation to securities issued to bearer where a ticket or certificate could be detached when an interest payment or dividend became due and presented as evidencing entitlement to payment thereof. 49 In 1864 Thomas Cook introduced the system whereby tourists prepaid a single fixed sum for travel and hotel expenses. Instead of paying money, the tourist would give up a coupon at the appropriate stage of the tour. In the First and Second World Wars coupons became familiar in connection with rationing schemes. Coupons were issued by government authorities and had to be produced when certain foodstuffs, petrol and other rationed goods were purchased. In that historical context, "coupon" corresponds with meaning 2a in the OED, viz: "A form, ticket, part of a printed advertisement, etc, entitling the holder to a gift or discount, etc, or designed to be filled up by an intending user or purchaser and forwarded to the advertiser for information, goods, etc." 50 If the term is viewed in isolation, there is much to be said for the meaning propounded by the respondents. However, I do not think claim 1 is speaking of a coupon in that sense. The function of the piece of paper is to notify trader and customer of immediate entitlement of the latter to a benefit. Data and new information are written to the Points file and Behaviour file respectively (claim 1 lines 29 and 30). This is most obvious in the case of a discount. The coupon functions as a manifestation of an existing entitlement recorded in the card. Read as a whole, claim 1 is not concerned with producing a coupon of the Thomas Cook type, which is intended to be presented at some later time as payment for goods or services rendered, and the loss whereof will mean the former holder does not receive the benefit.
Member file 51 The respondents' argument is that "identifying the card-holding customer" (claim 1 line 11) means that there must be data on the card which identifies the person who is the holder of the card, as distinct from merely identifying the card itself, for which a unique number would be sufficient. 52 But the function of the Member file is to identify the person holding the card during a purchase or payment operation. This does not require the owner be identified. What is happening is the rewarding of the user of the card. This has nothing to do with ownership.
Points file 53 The respondents' case on construction of "Behaviour file" depended in part on the proposition that the claim required one Points file with one counter used for all programs. It was said that, on the applicant's construction of the Behaviour file of the claim, the examples ([30] above) could not be performed with a single counter. Conversely, the invention would achieve all its objectives without multiple counters if it had a Behaviour file in the sense contended for by the respondents. 54 I accept the applicant's argument that in integer [d] there is no reason why the claim need refer to more than one points counter. The claim is concerned with a method of processing coded information during a purchase or payment operation at a (i.e. one) trader's. It is thus concerned with an operation conducted at a single trader's premises. While it is clear that the card might (and ordinarily would) contain a number of programs relating to a number of traders, there is no reason why claim 1 should be concerned with more than the counter relevant to that particular trader. 55 Moreover, the examples contemplate a points counter for each of the traders mentioned.
The respondents' system 56 For present purposes the corporate structure of the respondent companies, and the changes which have occurred in that structure from time to time, are not relevant. It will be convenient simply to refer to "the respondents". 57 In March 1995 the respondents launched their Wizard/Transcard system, which provided for electronic purse (e-purse) payments, ticketing and loyalty and incentive programs on a contactless smart card. An e-purse is an electronic substitute for cash; a pre-paid card is used by the card holder to make payments for goods and services until the stored value is used up. In the Wizard/Transcard system the card could then be "reloaded" by the cardholder paying cash to a Transcard agent who would then "load" the equivalent value on to the card by means of a transaction on the terminal. A contactless smart card is one with a computer chip and antenna which can be activated by a magnetic field generated by a terminal reader so as to communicate and conduct transactions. 58 From April 1995 the Wizard/Transcard system was trialed on Westbus buses in the western suburbs of Sydney, in Cabcharge taxis and a number of small retailers in Western Sydney offering e-purse payment, and ticketing. On the Westbus buses there was a loyalty program offering one free trip after every ten. A portion of the memory area on the cards would be used to store a record of points. Each time the card holder purchased a ticket an extra point would be recorded. Each time the points counter reached eleven, the ticket machine was programmed to provide a free ticket and not to deduct money from the e-purse. The points counter would then be set back to zero. 59 The Wizard/Transcard trial proved to be successful. Users made a number of suggestions. The respondents in August 1996 launched an upgraded system called CiT/Transcard. In an affidavit sworn on 3 August 2000 Mr Anthony Garton, the respondents' Software Development Manager, described this upgraded system as follows: "21. The CiT Transcard system offered essentially the same functions as the Wizard/Transcard system it replaced. However, with the change over to CiT Transcard, we improved the system. These improvements included the development of a common device to read the cards (called a validator), increasing the security of the system, and changing the way we managed the space on the card to make it more efficient. 22. The CiT Transcard system was now able to store any combination of electronic purses, loyalty programs and tickets and thereby better use the limited space in the card memory. We defined a range of program IDs and data formats for each program type (EP, loyalty, tickets). We standardised on 16 byte "blocks" for each program entry in the program area as this matched the memory addressing architecture of the contactless card we were using. This new design allowed us to store up to 36 programs of any type on a card. The actual location and number of programs on a specific card would now depend entirely on how the card was used not by some arbitrary space allocation. This card layout is still used by the Catuity system today." 60 The respondents produced later improvements - the CAT system (late 1997/early 1998) and the Catuity system (December 1999/early 2000). However, it is the CiT/Transcard system (hereafter "the respondents' system") which gives rise to the infringement issues in the present case. It will be necessary to consider it in a little more detail. The following description comes largely from the evidence of Mr Ben-Meir. 61 The respondents' system stores application data (including customer loyalty programs) on the chip card by means of a specific organisation of the chip card memory. The memory in the chip card is divided into three separate areas, each having a specific role with respect to the use of memory on the chip card. The three areas are described by the respondents as follows: "(a) Chip static area (the Static Area); (b) Application index area (the Index Area); and (c) Application data area (the Application Area)." 62 The Static Area contains (among other things) pointers that tell a terminal or validator where to find the start of the Index Area and the start of the Application Area. The Static Area also stores the identification number of the card. The Static Area includes the first block of the first sector of the card's memory, which includes the chip card's serial number (the Card Serial number) incorporated into the card at the time of manufacture. This serial number ensures that reading and writing operations remain confined to a single card during a single transaction. The "Card External ID" is a further identification number in the Static Area which can be assigned by the card issuer and can also perform the role of identifying a chip card and card holder data within the system. This number is used for printing on receipts. 63 The Index Area provides an index to the location of applications (the Applications) that are stored in the Application Area of the card. Applications can be loyalty programs, e-purses or ticketing programs. The Index stores a unique reference number that identifies each Application (the Application ID). The Index Area acts as an index in that the memory location of an Application in the Application Area is implied by the position of the corresponding Application ID within the Index Area. An Application ID that identifies a loyalty program is termed a Loyalty Program ID. The memory in the Application Area is addressed by the Index Area in 16 byte blocks. Each of these 16 byte blocks is represented by a location in the Index Area, that is to say Application IDs are arranged in the Index Area in such a way that the position of an Application ID within the Index Area indicates the position of the corresponding 16 byte block in the Application Area. For example, the first record in the Index Area will store the Application ID for the Application that is stored in the first 16 byte block of the Application Area, and so forth. 64 The Index Area of the respondents' system was described in their Power Point slides shown at a presentation attended by Mr Ben-Meir in these terms: "• Dynamic, reusable indexed use of storage • No fixed position of application data on the card • Flexible use of storage depending on card usage • No pre-allocation of space". This functionality was also described by Mr Garton at par 22 of his affidavit (see [59] above). 65 In Mr Ben-Meir's view, which I accept, the Index Area performs the role of a file that accumulates the Application ID for each Application as and when it is loaded onto the customer's chip card by a card terminal or validator at a trader's. Because the Index Area contains a store of the Loyalty Program IDs for the loyalty programs in which a card holder is participating, the Index Area of a chip card is a store of the particular card holder's chosen relationship with one or more traders that operate loyalty programs through the respondents' system. When the customer engages in his or her first transaction with a trader offering a loyalty program, the Loyalty Program ID for that new loyalty program is loaded into the Index Area and the loyalty program Application itself is loaded into the Application Area of the card. 66 As old loyalty programs expire they may be removed from the Index Area and the chip card memory may be reused. The Index Area on any particular chip card operating in the respondents' system will therefore be a catalogue of current loyalty programs stored on the chip card as a consequence of the customer's choices in relation to a trader or traders operating loyalty programs through the system. The indexing function of the Index Area plays an essential role in accessing data that is stored for loyalty programs in the Application Area. Data in the Index Area is used to reference loyalty program data every time that loyalty program data is updated in the operation of the system. 67 The Application Area contains data for each loyalty program stored on the chip card. Data fields for each of the following pieces of information for each loyalty program are as set out in the respondents' PowerPoint slides. (i) Application expiry date: This is the date at which the loyalty program on the card expires and the memory space allocated to that program can be reused for the storage of data for another program. (ii) Country: This is a code for the country in which the loyalty program is running. The field makes it possible for Application IDs to be allocated on a country by country basis where the respondents' system operates in more than one country. (iii) FIP detail: "FIP" is used in the respondents' documents to refer to Frequency Incentive Programs which are equivalent to the loyalty programs. (iv) Counter 1 and Counter 2: Counter 1 is used to store units or points accrued by a customer towards rewards offered in a loyalty program. Points are accrued according to the loyalty program rules depending on the cardholder's spending or frequency of visits. 68 The Index Area and Application Area are used as described above for storing data on the chip card and for reading and writing data to and from the chip card for the operation of loyalty programs. The data processing operations by which card holders accumulate points towards rewards, and by which rewards are granted, are performed on POS terminals which read data from the chip card and write updated data to the chip card. 69 Loyalty programs operated through the respondents' system are created on a centralised computer called the "host" and transmitted to the relevant POS terminal or terminals in the form of "parameter files". The software that operates the loyalty programs is of a standard kind and the particular characteristics of each loyalty program are generated by the parameter files downloaded to the POS terminal(s) for the operation of the software. Changes can be made to the rules of loyalty programs simply by sending new parameter files from the host to the terminal. 70 Reward entitlements are displayed on a screen visible to both trader and cardholder and receipts are printed. 71 The respondents' PowerPoint presentation states: "• In CiT/Transcard onwards the following rewards are supported: Fixed value discount (eg ($10), Percentage discount (eg 10%) or message only (eg 'Give Free Coke'). • For discount rewards the discount amount is automatically applied to the current transaction. • For message only rewards, message on screen and receipt used to prompt the operator to offer the free good or service. • If goods/service reward is not accepted reward is lost. • All rewards are given at the time of transaction. The consumer does not have the choice which reward to redeem or when."
Principles 72 A patent is infringed if a person exploits the patented invention without permission of the patentee: s 13(1) of the Act. It is admitted by the respondents that should the operation of the respondents' system (and later systems) involve the claimed methods or devices there will have been infringement. 73 For infringement to occur each and every essential integer of the claim must be taken by the infringer and incorporated into his own product or process: Rhone-Poulenc Agrochimie SA v UIM Chemical Services Pty Ltd (1986) 12 FCR 477 at 496.
Infringement issues 74 The respondents' case is that some of the essential integers of claim 1 are not found in their system. They say: (i) as to integer [e], the respondents' Index Area is not a Behaviour file; (ii) alternatively, the Index Area is not used in the way required by the other integers; (iii) as to integer [c], the respondents' system does not have a Member file; (iv) as to integers [a], [k] and [n], the respondents' system does not print a coupon. 75 Implicit in the respondents' conduct of their case is that all other integers of the claim of the Patent are present in their system.
Behaviour file 76 In cross-examination Mr Ben-Meir accepted that the only basis for saying that the respondents' system contained a Behaviour file was that it had an index containing the trader codes that related to each of the programs stored in it at any one time. But he pointed out that the presence of a trader code did tell something about the card holder's behaviour towards that trader, namely that the card holder had chosen to deal at least once with that trader. And, over a series of transactions, the Index area of each card accumulates a series of loyalty program IDs that reflect the card holder's choice of particular traders, this being a sub-set of traders within a potentially much larger set of traders with available loyalty programs. 77 I do not accept the respondents' argument that information of this sort is trivial or commercially useless. 78 It is true that in the respondents' system there is no writing to the equivalent of the Behaviour file after the first visit to the particular trader. The system simply adds points depending on the program, such as one point per bus ride or one point per dollar spent. It does not store complicated data such as date of last visit or number of visits this month. Accordingly, much stress was put on the fact (in itself not disputed) that, on the applicant's case, the respondents' system only infringed on the first day it is used at each of a number of traders or with respect to their individual programs. 79 However, I do not see how this fact prevents infringement taking place. The respondents obviously see the capacity to add new programs as an important part of their system. Their PowerPoint presentation promotes a number of features, including "• Programs automatically added to card by terminal when used • Multiple programs can exist on a card or terminal." 80 So in this regard the respondents' system necessarily operates in a way that infringes an essential integer of claim 1. It does not matter that once a trader's program has been loaded subsequent use of that program will not infringe. If an infringer's device or process adopts all integers of the claim of the patent, it is not to the point that some embodiments of the patent provides benefits which the infringer's device or process does not.
Other integers 81 The respondents argued that integers [f], [g] and [h] meant that the calculations which lead to the various results (incrementing or decrementing points, printing coupon etc) depend on various items of information, including date of operation and information in the Behaviour file, things that are not present in the respondents' system. 82 But it is enough that the processing of integer [f] be dependent upon, among other things, the date of the operation. It is not necessary that the date of the operation be "used in" calculation of points. 83 It is to be noted that the respondents' PowerPoint presentation, when dealing with POS terminal parameters, refers to "Accumulation Start Date The date and time when the terminal will start accumulating points. Accumulation End Date/Time The date and time when the terminal will stop accumulating points." 84 The operation of a loyalty program defined by these parameters requires that the date of the operation, that is, a purchase or payment operation by a card holder, be compared to the Accumulation Start Date and to the Accumulation End Date to determine whether the system will proceed to accumulate points for that card holder for that transaction. Therefore, the date of the operation is used in the specified algorithmic processing. 85 The foregoing analysis assumes a construction of the integers [f], [g] and [h] advanced by the applicant, namely that the integers do not necessarily require the date in question to be stored on the card itself - they can be stored in the POS terminal. In my opinion, that construction is correct. 86 The respondents argued that in integers [i] and [j] the words "over a time period of specific duration" related to the frequency of visits and nature of visit. On the first use of the respondents' card at a trader's - the only case said to infringe - the time period of specified duration cannot have begun. Frequency and/or nature can only be calculated over a period of time, not on the first occasion. 87 However, I see no reason why the period of specified duration would not apply to the beginning and end date of a loyalty program or, in the respondents' terms, the Accumulation Start Date and Accumulation End Date.
Member file 88 It was submitted that the respondents' system does not have a Member file. For the reasons already discussed ([51] - [52] above) I think that in the claims of the Patent there is a file which identifies the card holder. In the respondents' system there is the Static Area ([62] above) which identifies the holder. Both systems operate on programs which relate to an identified card. Ownership rights are irrelevant.
Coupon 89 Once the construction issue is resolved in favour of the applicant, the respondents must fail on this issue.
Conclusion 90 I find the respondents' system has infringed the claims of the Patent.
VI GENERAL INCONVENIENCE 131 The respondents argued that the Patent was, within the meaning of the Statute of Monopolies, generally inconvenient as it placed a restraint on traders in developing and operating loyalty and incentive schemes which were "a commonplace way of doing business and had been so for many years in both the real and on line worlds". It was said that the applicant was seeking to monopolise a series of known integers for the purpose of a particular kind of loyalty scheme and was thereby preventing other traders from seeking to use those integers or the same composition of them in their own customer loyalty schemes. 132 But if an invention otherwise satisfies the requirement of s 18 it can hardly be a complaint that others in the relevant field will be restricted in their trade because they cannot lawfully infringe the patent. The whole purpose of patent law is the granting of monopoly.
Prior art 133 In their cross-claim the respondents alleged no less than 56 items of prior art as anticipations of the Patent. Thankfully by the time of the hearing they relied on only three: (i) PCT patent application no WO95/21428 in the name of Card One Development Company. (ii) European patent application no 0253240 in the name of Omron Tateisi Electronics Co. (iii) Public disclosure of the Wizard/Transcard system in Sydney in television broadcasts on 13 March and 16 August 1995 and a promotion at Darling Harbour in May 1995.
Principles 134 It was common ground that the reverse infringement test was applicable. One assumes the patent to be valid and asks whether the prior art in question would infringe it: Meyers Taylor Pty Ltd v Vicarr Industries Ltd (1977) 137 CLR 228 at 235. Where the prior art consists of a document only, the disclosure must give the reader "clear and unmistakable directions to do what the patentee claims to have omitted", Flour Oxidising Co Ltd v Carr Atco Ltd (1908) 25 RPC 428 at 457. As was metaphorically put in General Tyre & Rubber Co v Firestone Tyre & Rubber Co Ltd [1972] RPC 457 at 485-6: "A sign post, however clear, upon the road to the patentee's invention will not suffice. The prior inventor must be clearly shown to have planted his flag at the precise destination before the patentee."
Card One 135 This patent disclosed a smart card based method for amassing incentive credits (points) which can be redeemed to give a discount. 136 But according to the evidence of Mr Ben-Meir, which I accept, the invention in Card One represents a different approach to the operation of loyalty programs to that claimed in the Patent. The Patent claims an invention that makes its data processing dependent on the Behaviour file that stores information about card holder behaviour relating to a trader or traders and provides the invention with the capability of operating multiple loyalty programs in a trader specific manner using data on the same card. The invention in the Card One patent is an alternative approach in which transactions carried out with any of the relevant providers result in accumulation of a shared "incentive credit" which may be redeemed with any of the providers. Since the invention is essentially based on this mode of preparation, it is necessary to redistribute the cost of providing rewards, as between traders, using the centralised record keeping facility for recording record posting and account reconciliation. In Mr Ben-Meir's view the disclosure in Card One leads the reader, in important respects, away from what is claimed in the Patent.
Omron 137 Omron described a system that enables a loyalty program to be operated at a store. Points are accumulated according to the value of the purchases by a card holder at that store. Mr Ben-Meir points out that there is no description of the object of having a card holder use any card with more than one store. Unlike the invention claimed in the Patent, there is no description of a Behaviour file upon which the algorithmic processing is dependent and to which new information is written.
Wizard/Transcard 138 Wizard/Transcard did not have a file that stored data relating to which traders the card holder had transacted business with for use in operating loyalty programs. Instead there was a fixed use of memory space on the chip card such that a POS terminal would access a predetermined slot of the chip card's memory that contained the data belonging to the loyalty program operated with that terminal. The fixed memory location for each loyalty program meant that the number of loyalty programs that could be run within the system as a whole was limited to the number of loyalty programs that could be stored on each card. Indeed it was the respondents' modification of Wizard/Transcard by the introduction of the "index" which resulted in application data no longer having a fixed position on the chip card. But this happened after the priority date of the Patent and founds the applicant's claim for infringement.
x clarity 164 Section 40(3) of the Act provides that the claim or claims of a specification must be "clear and succinct". 165 The respondents' first argument runs along these lines. The inventor (M Haddad) and the applicant's experts have sworn that they read terms in the specification in a way which was "radically different" from the construction advanced by the respondents. So if the respondents' construction is accepted, the fact that skilled addressees make a mistake means that the terms are ambiguous. Even if a court itself is able to resolve an ambiguity (and in the respondents' favour), the fact remains that skilled addressees cannot. 166 This is akin to shooting two birds with one barrel. The respondents have their construction accepted, and so win on infringement, but because their construction is problematic (albeit correct) the court finds lack of clarity, so the respondents win on revocation. 167 When a court construes any document there are usually two (or more) possible meanings. Were this not so, a construction issue would not have arisen in the first place. In Upper Hunter County District Council v Australian Chilling and Freezing Co Ltd (1968) 118 CLR 429 Barwick CJ (with the agreement of McTiernan, Kitto and Windeyer JJ) said (at 436-437): "But a contract of which there can be more than one possible meaning or which when construed can produce in its application more than one result is not therefore void for uncertainty. As long as it is capable of a meaning, it will ultimately bear that meaning which the courts, or in an appropriate case, an arbitrator, decides is its proper construction: and the court or arbitrator will decide its application. The question becomes one of construction, of ascertaining the intention of the parties, and of applying it. Lord Tomlin's words in this connexion in Hillas & Co. Ltd. v. Arcos Ltd. (1932) 147 LT 503 at 512 ought to be kept in mind. So long as the language employed by the parties, to use Lord Wright's words in Scammell (G.) & Nephew Ltd. v. Ouston [1941] AC 251 is not 'so obscure and so incapable of any definite or precise meaning that the Court is unable to attribute to the parties any particular contractual intention', the contract cannot be held to be void or uncertain or meaningless. In the search for that intention, no narrow or pedantic approach is warranted, particularly in the case of commercial arrangements. Thus will uncertainty of meaning, as distinct from absence of meaning or of intention, be resolved." 168 This statement of principle is equally applicable to the construction of a patent specification. 169 The respondents then argued that if the applicant's construction is adopted certain terms are lacking in clarity, notably "coupon", "Behaviour file" and "behaviour", "a coupon is or is not printed on the basis of the information arising from the contents of the said memory", "a specified algorithmic processing", "the nature of the first, second or xth visit", "the coupon is printed only if the number of points contained in the Points file is greater than the specified value "when read in conjunction with" and the said coupon is or is not printed on the basis of the result of the said algorithmic processing" and "new information is written to the Behaviour file … on the basis of the result of the said algorithmic processing". 170 The short answer to this is that neither Dr Brookes nor Dr Clarke nor any other witness called by the respondents said that they could not make something fall in with the claims of the specification. The evidence of M Haddad was that his own programmers needed no more than a draft of the patent specification to make the functional system of the patent. The only witness called by the respondent who had practical experience of systems of this nature, Mr Garton, did not claim to be unable to read the Patent.
XI DESCRIPTION 171 Section 40(2)(a) of the Act requires the specification to describe the invention fully, including the best method known to the applicant of performing it. The requirement is that the skilled addressee, assisted by the common general knowledge in the relevant art, would be able to produce something within each claim: Kimberley-Clark Australia Pty Ltd v Arico Trading International Pty Ltd (2001) 177 ALR 460 at [25]. This is a question of fact: Universal Oil Products Co v Monsanto Co (1972) 46 ALJR 658 at 661. 172 It is said that this lack of proper description is to be found first in the absence of any description of the dynamic use of memory, asserted to be central to the invention. 173 For the reasons already mentioned ([146] above) characterisation of the inventive step is something different from the instructions to the skilled addressee. 174 Secondly, it is said that there is no description of any coupons in the sense contended for by the applicant. As already mentioned, none of the respondents' experts said that it was not possible to make something fall within the claims of the Patent on the basis of the specification and M Haddad's programmers needed no more than a draft of the Patent specification to make the functional system of the Patent. Mr Garton did not suggest he could not make something fall within the claims of the Patent. 175 Thirdly, the respondents said there was in the absence of any description of "coupon" as construed by the applicant. I think I can only say that this is obvious from the specification.
XII FAIR BASIS 176 The claim or claims must be clear and succinct and fairly based on the matter described in the specification: s 40(3) 177 Most of the allegations of fair basing alleged in the cross-claim were abandoned. The one persisted in was that there was no real and reasonably clear disclosure in the specification of the following: (i) That a "coupon" includes a mere receipt, record or acknowledgment of a transaction, so that the coupon is not required to give rise to an entitlement. (ii) That a "coupon" includes a mere printing of a message on a POS screen. (iii) That "printed" includes a message on a POS screen. (iv) That a "Behaviour file" includes the number of merchant files stored on the smart card. (v) That a "Behaviour file" includes merchant programs sorted on the smart card with files identifying the location where each merchant program is stored in the memory of the card. (vi) That a "Behaviour file" includes storing a new Points file for each new trader. 178 In my opinion this is no more than an attempt to confine the claims precisely to the preferred embodiment: Décor Corporation Pty Ltd v Dart Industries Inc (1988) 13 IPR 385 at 393, 400: Pearce v Paul Kingston Pty Ltd (1992) 23 IPR 303 at 307-308 and Rehm Pty Ltd v Websters Security Systems (International) Pty Ltd (1988) 11 IPR 281 at 302-305.
XIII ORDERS 179 I find for the applicant on the claim and the cross-claim. There will be a direction that the applicant within seven days file and serve minutes of proposed orders to give effect to these reasons. Further hearing will be adjourned to a date to be fixed. I certify that the preceding one hundred and seventy-nine (179) numbered paragraphs are a true copy of the Reasons for Judgment herein of the Honourable Justice Heerey.
Counsel for the Applicant: R C Macaw QC and A J Ryan
Solicitor for the Applicant: Arthur Robinson and Hedderwicks
Counsel for the Respondents: D K Catterns QC, C D Golvan and S Ricketson
Solicitor for the Respondents: Baldwin Shelston Waters Law
Date of Hearing: 6, 7, 8 and 9 March, 2, 3 and 9 April 2001
Welcome Real-Time SA
Catuity Inc
(2000) 49 IPR 331
(1986) 12 FCR 477
(1993) 27 IPR 577
(1999) 99 FCR 151
(1899) 5 ALR 81
(1913) 16 CLR 138
(1914) 18 CLR 423
(1910) 10 CLR 701
(1991) 33 FCR 218
(1994) 51 FCR 260
(1959) 102 CLR 232
(1959) 102 CLR 252
(1972) 126 CLR 611
(1977) 137 CLR 228
(1980) 144 CLR 253
(1968) 118 CLR 429
(2001) 177 ALR 460
(1972) 46 ALJR 658
(1988) 13 IPR 385
(1992) 23 IPR 303
(1988) 11 IPR 281