WO2002061699A1

WO2002061699A1 - A method for bill payment

Info

Publication number: WO2002061699A1
Application number: PCT/IE2001/000013
Authority: WO
Inventors: Shane Joseph Buckley
Original assignee: Fournir Limited
Priority date: 2001-02-01
Filing date: 2001-02-01
Publication date: 2002-08-08
Also published as: WO2002061699A8

Abstract

The invention allows a user or a client of a service provider operating a server to pay bills using a short messaging (SM) service. It is particularly adapted for use by user's to pay regular bills by sending an SMS to the service provider to instruct that the bill be paid. This is particularly adapted for use by mobile phones since each mobile phone has a caller line identifier (CLI) which itself is unique and therefore, identifies clearly where the instruction is coming from. Since, the system ensures that there is already set up, the suppliers that can be paid on behalf of a particular client, the risk of fraud is minimal. Further, the invention is directed towards the topping up of the charges of a mobile phone very conveniently where such a mobile phone operates on a pre-paid system. Once the system is set up, the server downloads an SM giving details of bills requiring payment and the user of the mobile phone simply sends back an SM instructed whether the bill is to be paid or not.

Description

"A method for bill payment"

Introduction

The present invention relates to methods for bill payment and for the secure payment for goods and services in a payment system operating in a communications network. Further, the invention relates to the construction of such a payment system.

Many people have regular bills which require payment, very often at monthly intervals, such as, for example, telephone, electricity, gas and other similar utilities.

Further, people often have other regular payments such as mortgage payments and loan payments, together with regular payments of varying amounts to particular suppliers of goods or services. All of these suppliers constitute, for the consumer,

^"regular bills which have to be paid on a regular basis. For many people, particularly those travelling or not in their home environment during working hours, the payment of such bills and services can be quite an onerous task. This becomes particularly the case, for example, if a person is travelling regularly and it is not necessarily convenient to pay, for example, credit card bills, while at the same time, the person does not want to ignore them. Ideally, for the consumer, there should be some way of paying a multitude of these bills automatically.

Another problem that often arises for the consumer is that he or she does not know whether they wish to pay the bill directly out of their bank account or to use some form of credit such as, for example, a credit card. Further, for the consumer, he or she may have a multitude of bills which vary over time such as, for example, certain heating bills could be relatively expensive over the winter months and minimal over the summer months. Thus, for the customer, it would be convenient to spread out all these bills over, for example, a twelve month period, by the payment of regular monetary amounts, while having each of the bills discharged as they became due, irrespective of their amount. At the same time they do not necessarily want to have the bills paid automatically. The customer could then effectively spread out the payments for all these goods and services over a twelve month period.

In this specification, the term "client" is used to identify the consumer using the service and method according to the present invention, which client is, strictly speaking, both a customer of the service provider in accordance with the invention, and a customer of the actual supplier of the goods and services. Additionally in certain instances the terms such as "client" and "client computer" are used synonymously to avoid undue complexity in the description. Further, the term "client communications device" in this specification, relates to any communications device, whether it be a PDA, or laptop with an integrated wireless communication system, or a mobile telephone with a unique call line identifier.

The present invention is directed towards providing a method of the payment of bills for goods and services in a simple and secure manner.

Statements of Invention

According to the present invention there is provided a method for bill payment in a payment system having a server including a short messaging (SM) service, supplier computers and client communications devices capable of receiving and sending short messages each having a unique call line identifier (CLI), the server, computers and communications devices all being connected in a communications network comprising the initial steps oft-

storing in the server details of the suppliers whose bills are to be received;

storing in the server a payment procedure for client bills including the client CLI; and

subsequently the steps are performed of:-

the supplier computer downloads a bill for a client to the server;

the server sends the bill in the form of bill SM to the client communications device;

the client communications device receives the SM in accordance with the SMS;

the client communications device retrieves the bill SM;

the client communications device sends an instruction in the form of a pay SM to the server;

the server validates the instruction;

the server carries out the payment procedure; and

the server, on successful completion of the payment procedure, sends a payment confirmation SM to the client communications device.

Ideally the server validates the pay SM by comparing the communications device CLI with the client CLI.

Preferably the client communications device downloads a PIN number with the pay SM for validation of the instruction.

Ideally on sending the pay SM, the pay SM includes the monetary amount of the payment.

Further on sending the pay SM, the pay SM includes the date on which payment is to be made.

Preferably the payment procedure established between the client and the supplier comprises more than one method of payment having a unique payment system identifier and in which, on the client communications device sending a pay SM, the client communications device additionally sends one of the unique payment system identifiers.

Ideally when the pay SM sent does not includes the unique payment system identifier, the server returns the pay SM to the client communications device with an SM requesting the unique payment system identifier.

Ideally the payment procedure comprises:-

the server contacts a credit card provider computer;

the server downloads the client credit card details and bill payment details to the credit card provider computer as payment instructions; and

on the credit card provider accepting the payment instructions, the confirmation SM is sent to the client communications device.

Further the payment procedure comprises:-

the server computer receiving direct debiting protocols from a client financial institution having a financial institution computer;

the server storing the direct debiting protocols;

on receiving a pay SM, the server computer carries out the direct debiting protocols with the financial institution computer; and

on the direct debit being accepted by the client financial institution, the confirmation SM is sent.

Further still the payment procedure further comprises budget procedure rules comprising:-

the client agrees a total budget for the payment of specified bills over an agreed time period;

the client agrees to make regular payments at regular time intervals during the agreed time period under the payment procedure; and during the agreed time period, the server computer pays the bill, on receiving the pay SM.

Ideally the bill SM includes at least the supplier and the monetary amount of the bill.

Preferably the bill SM includes the due date for payment.

Ideally the server, on receiving the bill from the supplier computer stores the bill details in a bills payable database until the bills is paid.

Preferably at regular intervals, the server searches the bills payable database and downloads a bill SM in respect of outstanding bills.

Ideally on receiving a bill query SM from the client communications device, the server searches the bills payable database and downloads one or more bill SMs as required to the client communications device.

Preferably on sending a payment confirmation SM to the client communications device, the payment confirmation SM details are stored in a bills paid database.

Ideally on receiving a payment query SM from the client communications device, the server computer searches the bill paid database and downloads one or more payment confirmation SMs to the client communications device.

Preferably the client communications device is a mobile phone operated on a prepaid credit basis and the method is used to top up the monetary amount available for use of the phone serve comprising the server sends a payment request as a bill SM when the monetary amount available for phone services falls below a preset limit.

In another embodiment there is provided a method for the secure payment for goods and services in a payments system having a server including a short messaging (SM) service supplier computers and a client communications device capable of receiving and sending short messages, the communications device having a unique call line identifier (CLI), the server having means to store supplier details whose bills are to be received for a specified customer and having means to store a payments procedure pre-agreed between the client and server operator including means to store the CLI as an authentication and authorisation code for carrying out the payments procedure, the method comprising the following steps:-

the supplier computer downloads a bill for a client to the server;

the server sends the bill in the form of a bill SM to the client communications device;

the client communications device receives the SM in accordance with the SMS;

the client communications device retrieves the bill SM;

the server validates the instruction;

the server carries out the payment procedure; and

It will be appreciated that the server may be only a bearer of information, which passes the CLI, a unique payment system identifier, instruction and amount to a third party to carry out the payment procedure.

Preferably the client communications device downloads a PIN number with the pay SM for validation of the instruction. Further, on sending the pay SM, the pay SM includes the monetary amount of the payment.

Further still on sending the pay SM, the pay SM includes the date on which payment is to be made.

Ideally the payment procedure established between the client and the supplier comprises more than one method of payment having a unique payment system identifier and in which, on the client communications device sending a pay SM, the client communications device additionally sends one of the unique payment system identifiers.

Preferably the pay SM sent does not includes the unique payment system identifier, the server returns the pay SM to the client communications device with an SM requesting the unique payment system identifier.

Ideally the payment procedure comprises:-

the server contacts a credit card provider computer;

Preferably the payment procedure comprises:-

the server storing the direct debiting protocols; on receiving a pay SM, the server computer carries out the direct debiting protocols with the financial institution computer; and

Further the payment procedure further comprises budget procedure rules comprising:-

the client agrees to make regular payments at regular time intervals during the agreed time period under the payment procedure; and

during the agreed time period, the server computer pays the bill, on receiving the pay SM.

Further the bill SM includes the due date for payment.

Preferably the server, on receiving the bill from the supplier computer stores the bill details in a bills payable database until the bill is paid.

Ideally at regular intervals, the server searches the bills payable database and downloads a bill SM in respect of outstanding bills.

Preferably on receiving a bill query SM from the client communications device, the server searches the bills payable database and downloads one or more bill SMs as required to the client communications device.

Ideally on sending a payment confirmation SM to the client communications device, the payment confirmation SM details are stored in a bills paid database. Further on receiving a payment query SM from the client communications device, the server computer searches the bill paid database and downloads one or more payment confirmation SMs to the client communications device.

Preferably the client communications device is a mobile one operated on a pre-paid credit basis and the method is used to top up the monetary amount available for use of the phone serve comprising the server sends a payment request as a bill SM when the monetary amount available for phone services falls below a preset limit.

In another embodiment of the present invention there is provided a payments system for the secure payment for goods and services comprising:-

a server;

a short messaging service computer;

supplier computers;

a client communications device for the delivery and reception of short messages, the communications device having a unique call line identifier (CLI);

a communications network (2) interconnecting the server (3), the short messaging service computer (4), supplier computers (5) and the client communications device (6) characterised in that the server (3) comprises:

means for carrying out the steps of the method carried out by the server (3) as claimed in any preceding claim.

Ideally the client communications device is a mobile phone.

In a further embodiment of the present invention there is provided a computer program comprising program instructions for causing a computer to carry out the invention.

Detailed Description of the Invention

The invention will be more clearly understood from the following description of some embodiments thereof, given by way of example only, with reference to the accompanying drawings, in which:-

Fig. 1 is a stylised layout of a payment system according to the invention, and

Figs. 2 to 5 are flowcharts showing the operation of the invention.

Referring to the drawings and initially to Fig. 1 thereof, there is illustrated a payment system for the secure payment for goods and services, indicated generally by the reference numeral 1, comprising a communications network 2 to which is connected a server 3, in turn connected to a short messaging service (SMS) 4 which would also be provided by another computer. There is also provided a plurality of supplier computers 5, together with a number of client communications devices 6 which, in this embodiment, are identified by mobile phones or a portable computer having a modem, all of which are identified by the reference numeral 6 and all have an ability to communicate and each has a unique call line identifier (CLI). A financial institution is identified by the reference numeral 7 and this could be, for example, a credit card provider, a client bank, an acquirer bank or indeed part of the server organisation.

Essentially, what the invention provides is an easy way for users or clients of the server operated by the service provider to pay multiple bills by using SMS. The server computer 3, hereinafter generally referred to as the server, may have its own dedicated SMS 4 or may indeed simply be connected to an SMSC (SMS Centre) provided by a third party. The invention is particularly adapted to mobile phones since almost all mobile phones now in use have a short messaging capability so that they can use a short messaging service.

Referring now to Fig. 2, there is shown how a client sets up the service or subscribes to it. In step 10, the client contacts the server. In step 11, the server downloads to the client a set-up form, which set-up form identifies the client's call line identifier (CLI), the service provider, that is to say, the server operator's account number, and the billing or payment procedure agreed between the client and the service company. This set-up process could happen through a customer service call centre or through a registration process for new set-ups. Optionally, when agreeing the procedure in step 12 for payment, the service company may also agree a further identifying or confirming PIN number with the client. In step 13, the server stores the payment procedure agreed with the client. In step 14, the server contacts suppliers to set up communications with the supplier computers so that the suppliers computers can subsequently download bills for payment to the server.

Various payment procedures may be adopted and indeed more than one payment route or method within the procedure may be agreed between the client and the service provider operating the server, as will be described hereinafter.

Now referring to Fig. 3, in step 15, the supplier downloads a bill to the server. The bill will be downloaded in such a way that the server can extract the necessary information from the bill to send a short message (SM) to the client communications device. In step 16, the server uses the SMS 4 to send an SM to the client communications device, which SM contains at least the supplier name and amount of the bill payable. The client is prompted to reply to the message with the word "pay" in the text field in order to settle the account. In this example the term "pay" is used, however any pre-determined term may be used between the two parties in order to settle the account. Ideally, it also includes the due date for payment. This short message constitutes a pay SM. Simultaneously, the server, in step 17, stores the bill details in a bills payable database. In step 18, the client communications device stores the SM and in step 19, the client communications device displays the bill SM and in step 20, the client communications device sends an instruction to the server to pay the bill by sending a pay SM. The pay SM may be a short message to pay all the bill or portion of the bill, as the case may be. It will be appreciated that steps 18, 19 and 20, while shown as three steps, may in fact all be carried out simultaneously. In other words, as the short message is delivered, the actual pay SM may be almost immediately returned. In step 21 , the server receives the pay SM and in step 22, the server authenticates the pay SM by checking the client CLI or CLI and password and in step 23, accepts the pay SM and in step 24, conducts the payment procedure and if the payment procedure is acceptable, in step 25, in accordance with the procedure, confirms to the supplier. Because there are so many procedures that could be adopted for payment, these are described later. However, essentially, the payment is confirmed in step 25 and in step 26, a payment confirmation SM is send to the client communications device. Simultaneously, in step 27, the bills payable database is updated with the fact that the bill has been paid and in step 28, also simultaneously, details of the payment of the bill is entered into a bills paid database.

When the server conducts the payment procedure and the payment is rejected, in step 29, the client is informed by an SMS and the instruction is rejected. In step 30, the bill SM is resent to the client.

It will be appreciated that after a certain length of time, bills become due and the due date for payment expires, in which case the server will send a reminder SM giving a further bill SM to the client communications device. Such reminders may be sent at regular intervals or indeed may not be sent. It depends entirely on the procedure agreed. It will be appreciated that suppliers would prefer the server to deliver such reminders and thus, the delivery of such reminders can be a source of revenue to the server who can agree with a supplier to search the bills payable database on a regular basis and send reminders to all of the suppliers, customers, that is to say, the service provider's clients who have not yet paid the supplier.

Referring to Fig. 5, there is illustrated some of the steps used in topping up the phone bill of a phone company's customer when that phone bill is operated on a "pay-as- you-go" basis. In step 40, the phone company contacts the server with an SMS stating that some preset minimum limit of expenditure remains on the mobile phone. In step 41, the server receives the SMS and in step 42, sends a bill SM to the mobile phone. This bill SM is, strictly speaking, not a bill, but a reminder that a payment should be made. In step 43, the mobile phone sends back a pay SM together with a PIN number. Some form of PIN or password may be needed for use for this operation because it is always possible that somebody unauthorised could have the use of somebody else's phone and put considerable charges on it. It will be appreciated that a customer can unsubscribe to the bill service if the customer wishes to do so. The remainder of the procedure is as before and they are ignored except that in step 44, the phone is topped up.

Various payment procedures are envisaged. For example, in general, the service provider operating the server, will pay the bills on behalf of the client. In this circumstance, the server will carry out various payment procedures. For example, the server could contact a credit card provider computer, the server would then download the client credit card details and bill payment details to the credit card provider computer as payment instructions, and on the credit card provider accepting the payment instructions, the confirmation SM is sent to the client communications device.

The payment instructions could be either payment instructions to the supplier or payment instructions to the service provider. Whichever way it is paid, all that is necessary is that once the credit card company has accepted the payment, then the confirmation SM can be sent to the client. Needless to say, a further payment procedure could comprise the server receiving direct debiting protocols from a financial institution of which the client is a customer, the financial institution having a financial institution computer. In such a case the server would store the direct debiting protocols and on receiving a pay SM the server computer would then carry out the direct debiting protocols with the financial institution computer and, on the direct debit being accepted by the financial institution, the confirmation SM is sent and subsequently, the service provider operating the server, pays the supplier. Alternatively, needless to say, the direct debiting procedure could, in fact, credit the supplier account directly and the money need not necessarily be routed through the service provider although, undoubtedly ideally for the service provider, the money should in fact be transmitted through the service provider.

There is a considerable opportunity to set up a payment procedure which comprises a budget procedure rules in addition to the normal payment procedure, which would comprise, for example, the client agreeing to a total budget for the payment of specified bills over an agreed period. Then, the client would agree to make regular payments at intervals during the time period under the designated payment procedure and during the time period, the server would pay the bills on receiving the pay SM or have the one automatic pay SM for the year and at the same time, this procedure would continue as long as the payments were received by the service provider.

Further, it is envisaged, as already explained, that the server, on receiving a bill from the supplier, can store the bill details in the bills payable database until the bill is paid. One of the advantages of this is that it allows both the server to search the bills payable database at regular intervals and download a bill SM in respect of outstanding bills. Further, it allows, by the use of a simple querying SM for the client communications device to request the server to search the bills payable database and download one or more bill SMs as required to the client communications device. Similarly, as explained already, in one embodiment of the invention, on sending a payment confirmation SM to the client communications device, the payment confirmation SM details are stored in a bills paid database. On the client querying a payment, the payment query SM from the client communications device will allow the server computer search the bill paid database and download one or more payment confirmation SMs to the client communication device.

It will be appreciated that when a client sends a pay SM, the client may additionally send a unique payment system identifier which has been already sent to the client informing the client that a bill payment is due. Further, if the pay SM does not include the unique payment system identifier the server returns the pay SM to the client requesting the unique payment system identifier. In this way the security is increased and payment procedure is made safer.

It will be appreciated that various aspects of the invention may be embodied on a computer that is running a program or program segments originating from a computer readable or usable medium, such medium including but not limited to magnetic storage media (.e.g. ROMs, floppy disks, hard disks, etc.), optically readable media (e.g. CD-ROMs, DVDs, etc.) and carrier waves (e.g., transmissions over the Internet). A functional program, code and code segments, sued to implement the present invention can be derived by a skilled computer programmer from the description of the invention contained herein. In the specification the terms "comprise, comprises, comprised and comprising" or any variation thereof and the terms "include, includes, included and including" or any variation thereof are considered to be totally interchangeable and they should all be afforded the widest possible interpretation and vice versa.

The invention is not limited to the embodiment hereinbefore described, but may be varied in both construction and detail within the scope of the claims.

Claims

1. A method for bill payment in a payment system having a server including a short messaging (SM) service, supplier computers and client communications devices capable of receiving and sending short messages each having a unique call line identifier (CLI), the server, computers and communications devices all being connected in a communications network comprising the initial steps of:-

storing in the server details of the suppliers whose bills are to be received;

subsequently the steps are performed of:-

the supplier computer downloads a bill for a client to the server;

the client communications device receives the SM in accordance with the SMS;

the client communications device retrieves the bill SM;

the server validates the instruction;

the server carries out the payment procedure; and the server, on successful completion of the payment procedure, sends a payment confirmation SM to the client communications device.

2. A method as claimed in claim 1 , in which the server validates the pay SM by comparing the communications device CLI with the client CLI.

3. , A method as claimed in claim 1 or 2, in which the client communications device downloads a PIN number with the pay SM for validation of the instruction.

4. A method as claimed in any preceding claim, in which, on sending the pay SM, the pay SM includes the monetary amount of the payment.

5. A method as claimed in any preceding claim, in which, on sending the pay SM, the pay SM includes the date on which payment is to be made.

6. A method as claimed in any preceding claim, in which the payment procedure established between the client and the supplier comprises more than one method of payment having a unique payment system identifier and in which, on the client communications device sending a pay SM, the client communications device additionally sends one of the unique payment system identifiers.

7. A method as claimed in claim 6, in which, when the pay SM sent does not includes the unique payment system identifier, the server returns the pay SM to the client communications device with an SM requesting the unique payment system identifier.

8. A method as claimed in any preceding claim, in which the payment procedure comprises:-

the server contacts a credit card provider computer;

9. A method as claimed in any preceding claim, in which the payment procedure comprises:-

the server storing the direct debiting protocols;

10. A method as claimed in any preceding claim, in which the payment procedure further comprises budget procedure rules comprising:-

11. A method as claimed in any preceding claim, in which the bill SM includes at least the supplier and the monetary amount of the bill.

12. A method as claimed in claim 11, in which the bill SM includes the due date for payment.

13. A method as claimed in any preceding claim, in which the server, on receiving the bill from the supplier computer stores the bill details in a bills payable database until the bills is paid.

14. A method as claimed in claim 13, in which at regular intervals, the server searches the bills payable database and downloads a bill SM in respect of outstanding bills.

15. A method as claimed in claim 13 or 14, in which, on receiving a bill query SM from the client communications device, the server searches the bills payable database and downloads one or more bill SMs as required to the client communications device.

16. A method as claimed in any preceding claim, in which, on sending a payment confirmation SM to the client communications device, the payment confirmation SM details are stored in a bills paid database.

17. A method as claimed in claim 16, in which, on receiving a payment query SM from the client communications device, the server computer searches the bill paid database and downloads one or more payment confirmation SMs to the client communications device.

18. A method as claimed in any preceding claim, in which the client communications device is a mobile phone operated on a pre-paid credit basis and the method is used to top up the monetary amount available for use of the phone serve comprising the server sends a payment request as a bill SM when the monetary amount available for phone services falls below a preset limit.

19. A method for the secure payment for goods and services in a payments system having a server including a short messaging (SM) service supplier computers and a client communications device capable of receiving and sending short messages, the communications device having a unique call line identifier (CLI), the server having means to store supplier details whose bills are to be received for a specified customer and having means to store a payments procedure pre-agreed between the client and server operator including means to store the CLI as an authentication and authorisation code for carrying out the payments procedure, the method comprising the following steps:-

the supplier computer downloads a bill for a client to the server;

the client communications device receives the SM in accordance with the SMS;

the client communications device retrieves the bill SM;

the server validates the instruction;

the server carries out the payment procedure; and

20. A method as claimed in claim 19, in which the server validates the pay SM by comparing the communications device CLI with the client CLI.

21. A method as claimed in claim 19 or 20, in which the client communications device downloads a PIN number with the pay SM for validation of the instruction.

22. A method as claimed in any of claims 19 to 21, in which, on sending the pay 5 SM, the pay SM includes the monetary amount of the payment.

23. A method as claimed in any of claims 19 to 22, in which, on sending the pay SM, the pay SM includes the date on which payment is to be made.

0 24. A method as claimed in any of claims 19 to 23, in which the payment procedure established between the client and the supplier comprises more than one method of payment having a unique payment system identifier and in which, on the client communications device sending a pay SM, the client communications device additionally sends one of the unique payment system 5 identifiers.

25. A method as claimed in claim 24, in which, when the pay SM sent does not includes the unique payment system identifier, the server returns the pay SM to the client communications device with an SM requesting the unique o payment system identifier.

26. A method as claimed in any of claims 19 to 25, in which the payment procedure comprises:-

5 the server contacts a credit card provider computer;

the server downloads the client credit card details and bill payment details to the credit card provider computer as payment instructions; and 0 on the credit card provider accepting the payment instructions, the confirmation SM is sent to the client communications device.

27. A method as claimed in any of claims 19 to 26, in which the payment procedure comprises:-

the server storing the direct debiting protocols;

28. A method as claimed in any of claims 19 to 27, in which the payment procedure further comprises budget procedure rules comprising:-

29. A method as claimed in any of claims 19 to 28, in which the bill SM includes at least the supplier and the monetary amount of the bill.

30. A method as claimed in claim 29, in which the bill SM includes the due date for payment.

31. A method as claimed in any of claims 19 to 30, in which the server, on receiving the bill from the supplier computer stores the bill details in a bills payable database until the bills is paid.

32. A method as claimed in claim 31, in which at regular intervals, the server searches the bills payable database and downloads a bill SM in respect of outstanding bills.

33. A method as claimed in claim 31 or 32, in which, on receiving a bill query SM from the client communications device, the server searches the bills payable database and downloads one or more bill SMs as required to the client communications device.

34. A method as claimed in any of claims 19 to 33, in which, on sending a payment confirmation SM to the client communications device, the payment confirmation SM details are stored in a bills paid database.

35. A method as claimed in claim 34, in which, on receiving a payment query SM from the client communications device, the server computer searches the bill paid database and downloads one or more payment confirmation SMs to the client communications device.

36. A method as claimed in any of claims 19 to 35, in which the client communications device is a mobile one operated on a pre-paid credit basis and the method is used to top up the monetary amount available for use of the phone serve comprising the server sends a payment request as a bill SM when the monetary amount available for phone services falls below a preset limit.

37. A payments system for the secure payment for goods and services comprising:-

a server;

a short messaging service computer;

supplier computers; a client communications device for the delivery and reception of short messages, the communications device having a unique call line identifier (CLI);

38. A payments system as claimed in claim 37, in which the client communications device is a mobile phone.

39. A computer program comprising program instructions for causing a computer to perform the method of any of claims 1 to 36.

40. A computer program comprising program instructions which when loaded into a computer, constitute the means of claims 37 and 38.

41. A computer program as claimed in claim 39 or 40 embodied on a record medium.

42. A computer program as claimed in claim 39 or 40 stored in a computer memory.

43. A computer program as claimed in claim 39 or 40 embodied in a read only memory.

44. A computer program as claimed in claim 39 or 40 carried on an electrical signal carrier.