Language selection

Search

Patent 2314098 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent Application: (11) CA 2314098
(54) English Title: PAYMENT SYSTEM AND METHOD USING TOKENS
(54) French Title: SYSTEME ET PROCEDE DE PAIEMENT AU MOYEN DE JETONS
Status: Deemed Abandoned and Beyond the Period of Reinstatement - Pending Response to Notice of Disregarded Communication
Bibliographic Data
(51) International Patent Classification (IPC):
  • G06Q 20/06 (2012.01)
(72) Inventors :
  • BARKAN, MORDHAI (Israel)
(73) Owners :
  • IMS SOFTWARE SERVICES, LTD.
(71) Applicants :
  • IMS SOFTWARE SERVICES, LTD. (United States of America)
(74) Agent: MCMILLAN LLP
(74) Associate agent:
(45) Issued:
(86) PCT Filing Date: 1998-11-19
(87) Open to Public Inspection: 1999-06-03
Examination requested: 2003-07-09
Availability of licence: N/A
Dedicated to the Public: N/A
(25) Language of filing: English

Patent Cooperation Treaty (PCT): Yes
(86) PCT Filing Number: PCT/IL1998/000563
(87) International Publication Number: IL1998000563
(85) National Entry: 2000-07-07

(30) Application Priority Data:
Application No. Country/Territory Date
122263 (Israel) 1997-11-20

Abstracts

English Abstract


The system and method for collecting payments for services on the internet
according to the figure. A user is provided with electronic tokens or stamps,
against a payment by a third party. When a service is requested by the user, a
token monitoring unit (14) determines if enough tokens are available to pay
for the service, if so, the service is performed. The status of the tokens
used is then changed to "used" in the third party's token database. This
trusted third party's tokens are used as a unit of exchange.


French Abstract

Système et procédé servant à encaisser des paiements correspondant à des services sur Internet (selon la figure). L'utilisateur est pourvu de jetons ou de timbres électroniques émis pour paiement par un tiers. Quand un service est demandé par l'utilisateur, une unité de contrôle de jetons (14) détermine si suffisamment de jetons sont disponibles pour payer ce service et, si c'est le cas, le service est accordé. L'état des jetons utilisés est ensuite modifié en "utilisé" dans la base de données de jetons du tiers. On utilise les jetons de ce tiers de confiance en tant que valeur d'échange.

Claims

Note: Claims are shown in the official language in which they were submitted.


43
Claims
What is claimed is:
1. A method of payment using tokens issued by a third party, during a
transaction between a first and second party, and where the third party
does not take part in the transaction, comprising the following steps:
a. A transaction management unit, pertaining to the software of the
first party, receives from a user there a request to perform a service
for which payment with tokens is required;
b. The management unit checks whether there are yet unused tokens
available in the system, that is tokens whose status is "ready" as
opposed to "used" or "canceled".
If an unused token was found, go to step (c);
If there are no available tokens, then indicate to the user that the
service cannot be performed because of lack of tokens, then END;
c. The management unit requests and/or retrieves information on an
available (unused as yet) token from a database or storage unit
pertaining to the software of the first party.
The status of the token which was retrieved is automatically changed in
the database, and will thereafter be designated as "used" or
"canceled";

44
d. During a subsequent transaction with the second party, the
management unit sends information relating to the token now used and
canceled to the second party, through a communication channel.
2. The method of payment according to claim 1, wherein after step (d)
the first user further sends to the second user information relating to
previous token or tokens used by the first user.
3. The method of payment according to claim 1, wherein after step (d)
the first user further sends to the second user information relating to
the use of token or tokens by other parties, as reported to the
first party during previous transactions.
4. The method of payment according to claim 1, wherein the second user
receives information relating to the use of tokens by other parties, and
discards the oldest information to limit the total information stored therein.
5. A method for monitoring the proper use of tokens during a transaction
between a first and second party, where a third party has issued the
tokens to the first party but does not take part in the transaction,
comprising the following steps:
a. The first party sends to the second party a report including
information relating to the token used and canceled by the first party
for that transaction;

45
b. The second party maintains a database of previous reports
relating to tokens used in the past, and the report received in
step (a) is added to the database;
c. The second party compares the information received in step (a)
with previous reports for the same first party;
d. If the comparison detects a violation of the rules for the use of
tokens, then the second party stores that information and/or displays a
violation report and/or reports that to the tokens issuer, and/or sends
a note to the first party of such token.
6. The method for monitoring the proper use of tokens according to
claim 5, wherein in step (b) the second party maintains a database of
previous reports relating to tokens used in the past by the first party.
7. The method for monitoring the proper use of tokens according to
claim 5, wherein in step (b) the second party maintains a database of
previous reports relating to tokens used in the past by a plurality of
other parties or users.
8. The method for monitoring the proper use of tokens according to
claim 5, wherein in step (b) the database of previous reports is being
updated to include the latest reports, and the oldest reports are
deleted therefrom.

46
9. The method for monitoring the proper use of tokens according to
claim 5, wherein in step (d) one of the rules for use of tokens is that
no token is allowed to be used twice.
10. The method for monitoring the proper use of tokens according to
claim 5, wherein in step (d) one of the rules for use of tokens is that
the serial number of successive tokens should be in ascending order.
11. The method for monitoring the proper use of tokens according to
claim 5, wherein in step (d) one of the rules for use of tokens is that
the serial number of issued tokens should correspond to a document or
permit issued by the third party.
12. A system for managing and monitoring the use of tokens during
transactions between a first and a second party, comprising:
a. a transactions management unit using tokens, wherein the unit is
activated when a local user requires to perform a service for which
payment using tokens is required, to activate tokens stored in a tokens
database;
b. a tokens database which includes information on tokens acquired
from the third party, and wherein each token presented to the management
unit to be used is then designated as "used" or "canceled" to prevent
the use of the same token in subsequent transactions;

47
c. a tokens use monitoring unit, to verify the correct use of tokens
by other parties who connect to the local system;
d. a database of tokens reports, including information on acquired
tokens which are available for performing the service for fee, and
wherein each token includes status indicating means, which change from
"ready" to "used" or "canceled" after a token is used;
e. a communication channel to other users.
13. The managing and monitoring system according to claim 12, wherein
a software package to implement the managing and monitoring system is
installed in the facilities of the first and second party and of any
party which may take part in transactions using tokens.
14. The managing and monitoring system according to claim 12, wherein
the transactions management unit will perform the required service only
if there are available tokens, that is tokens which are not "canceled"
or "used", in the database of tokens reports.
15. The managing and monitoring system according to claim 12, wherein
the communication channel may include a telephone line and/or a wireless
link or a connection to Internet or other means for performing a digital
communication session with other users.

48
16. A method for issuing tokens and for the subsequent use of tokens
during a transaction between a first and second party, wherein a third
party, which has issued the tokens to the first party, does not take
part in the transaction, comprising the following steps:
a. The first user calls the third party, asking for a specific
number (K) of tokens;
b. The third party prepares a digital document, allowing the first
party to generate K tokens, and wherein the digital document is signed
or encrypted with the private key of the third party, and further the
document is delivered to the first party;
c. To perform a paid transaction, the software of the first party
checks whether a token can be issued, according to the digital document.
If positive, a counter of used tokens is incremented, and a token is
prepared with a serial number which is the successor of the last token
generated, all within the serial numbers according to the digital
document. Go to step (d);
If all the tokens were already generated according to the digital
document issued in step (a), then no token is now generated, and the
user is informed accordingly "no more tokens available". END.
17. The method for issuing tokens according to claim 16, wherein in step (d)
the first party sends the token prepared in step (c) together with the
digital document prepared instep (a) to the second party, as proof of
payment for the present transaction.

Description

Note: Descriptions are shown in the official language in which they were submitted.


CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
Payment System and Method Using Tokens
Technical Field
This invention concerns systems and methods for collecting payments in a
distributed digital communications environment. The invention relates in
particular
to large networks and the Internet.
Background Art
In the present distributed digital communication systems, service providers
may
find it difficult to collect a fee for services performed.
Moreover, it may be desirable for users to have an instrument for paying for
various
services or products available in the net.
At present, it is not possible for service/product providers to get paid for
service
where the provider does not take part in every transaction.
Prior art systems and methods may not be suitable to answer this need
Thus, a service provide may possibly devise a software package with an
integral module which accounts for the use of the software, so that the
service provider may charge the user accordingly. Thus, for example, a
provider of a registered E-mail service may be paid for services provided.
A weak point in such a software is that it is too easy to neutralize the
accounting
module, to render it inoperable, so that the user may use the software for
free.

CA 02314098 2000-07-07
WO 99!27475 PGT/IL98/00563
2
And, if one user does not have the required technical skills for that, he/she
may be
sure that a hacker somewhere across the globe already did it, and that a
"cracked/broken" version of the software is available on the Internet. Thus, a
hacker or unauthorized person may spread worldwide a software package to
attack
the legitimate software. This may result in a large scale misuse of the
software,
while avoiding the required payment.
At present, it is impossible to detect such an attack on one's software or to
prevent
it. It is impossible to detect illegitimate use of the software, that is use
of "cracked"
software which denies the software owner their legitimate profits.
In the present business climate, with users of the software spread across the
globe,
it is very difficult or impossible to enforce a policy or to survey
transactions
performed.
Another approach to the fee collecting problem may be to channel all
transactions
through the service provider's facility. The service provider then has control
on any
and all transactions being performed, and can enforce a payment policy as
desired
This would require a tremendous investment by the service provider, to set up
huge
service centers worldwide, capable of concurrently serving many users. Thus,
this
approach may not be practical. It is therefore not desirable that the service
provider
take part in any and ali transactions between users.
Still another payment method may include the user using his/her credit card to
pay
in real time for any transaction.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/Ob563
3
The disadvantage of this method is that the credit card number may be
compromised, since the Internet and similar links are not secure. If an
unauthorized person intercepts the credit card information, this may be
used in fraudulent transactions. The card owner may find it difficult to
prove a specific transaction was not authorized, or even to detect some
of the unauthorized charges.
At present, a person paying with his/her credit card over the Internet may be
exposed to large losses. Thus, payment over a distributed net is difficult.
Still more difficult is collecting fees for transactions between two parties,
where the
service provider is a third party and is not a party to the actual
transactions.
For example, a provider of walkie-talkie devices or wireless sets cannot
collect a
fee from each call, since the communication is direct between users, without
the
manufacturer's mediation.
Another example is the use of a software for premium services relating
to E-mail. It may be advantageous both to manufacturer and user to
charge per use, not a global fee for the software. But how to account
for use of the software? The manufacturer may even not be aware of the
existence of the user, who may have obtained the software from a third party.
Still another problem with prior art systems is the use of "digital
cash". Prior art systems involve the issuance of "digital cash" which
include a credit for a fixed amount of money, signed by the "cash" issuer.

CA 02314098 2000-07-07
wo ~m4~s rc~rnL9s~ooss~
4
A possible problem is that these documents can be copied, so
each can be used in multiple transactions. To prevent that, the issuer
maintains a center which approves in real time each "cash" to be used.
This is an immense task, to participate in every business transaction
worldwide, more so when one considers the small amounts involved.
At present, there apparently are no methods which may enable a third
party to collect a fee from transactions between two parties over a
distributed network, where the third party takes no part in the actual
transactions between the two parties.
It is an objective of the present invention to provide for a system and method
of
payment using tokens, with means for overcoming the abovedetailed
deficiencies.
Disclosure of Invention
It is an object of the present invention to provide a system and method for
collecting payments or paying for a service or product in a distributed
digital
communications environment, especially suitable for large networks and the
Internet.
This object is achieved by a method of payment using tokens as disclosed in
claim 1.

CA 02314098 2000-07-07
wo ~rm4~s rcrnlr~oos~
In accordance with the invention, the object is basically accomplished
using a method of payment including the steps of (a) A transaction management
unit receives from a user there a request to perform a service for which
payment
with tokens is required; (b) The management unit checks whether there are yet
unused tokens available in the system. if an unused token was found, go to
step (c); If there are no available tokens, then the service cannot be
performed,
END; (c) The management unit requests information on an available token and
changes its status to "canceled"; (d) During the subsequent transaction with
the
second party, the management unit sends information relating to the token now
used and canceled to the second party.
The invention allows a third party to collect a fee from a transaction between
two
parties, even though the third party does not participate in transactions
between the
two parties.
According to one aspect of the present invention, a user is provided
with electronic tokens or stamps, against a payment. The user, while
using the service performed by the service provider, destroys a token or
stamp as payment for that service. After several uses of the service,
the tokens are all "used" or "destroyed" , so the user has to buy new
tokens for future use of the service.
Moreover, the method may be used to pay for various available services
or products.
According to a second aspect of the present invention, the user is
required to make public or present proof that he/she indeed did
destroy the tokens as required.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
6
Thus, a party to a transaction and the public in general can monitor the
legitimacy
of the use of tokens by a specific user. Thus, a large number of possible
monitoring
persons may verify a large number of the service or software, to ensure there
are
no illegitimate transactions, or at least that the number of these
illegitimate
transaction will not grow to large numbers.
According to a third aspect of the present invention, the system and
method performs an automatic process of presenting proof of destroying
the tokens, and of checking that the other party presented a legitimate
proof as well. Thus, during normal transactions between users, users
will check each other with respect to the performance of payments as
required, without requiring a deliberate effort on the part of the
users. Furthermore, the software package will include means for
automatically displaying and reporting any detected lack of payment or
lack of report of tokens being destroyed as required.
According to still another aspect of the present invention, the system
and method include means for diffusing the information on the use of
tokens among many users, to allow high visibility of each user's proper
conduct.
Another important aspect of the use of tokens is to pay to a second
party for a service or product. Whereas the tokens provider will
eventually pay to the second party, there is no need that the tokens
provider approve in real time each and every transaction.

CA 02314098 2000-07-07
wo ~srn~4~s Pcrn~~oos63
Moreover, the invention discloses an effective method for dissemination
of tokens to users. The special structure and operation of a
large-scale, distributed payment system impose special requirements,
including inter alia the need to effectively distribute tokens to a huge
number of users of these tokens, and to keep track of them all.
Further objects, advantages and other features of the present invention will
become obvious to those skilled in the art upon reading the disclosure set
forth
hereinafter.
Briei Description of Drawings
Fig. 1 illustrates the structure of a system for presenting reports on tokens
to other
users, and for monitoring other's reports.
Fig. 2 details the structure of a token information management and storage
database.
Fig. 3 illustrates the structure of a report detailing the use of tokens.
Fig. 4 illustrates the use of reports on tokens in transactions between
various users,
with Figs. 4(A), 4(B) and 4(C) illustrating three possible consecutive
transactions.
Fig. 5 illustrates another embodiment of the structure of a report detailing
the use
of tokens.

CA 02314098 2000-07-07
wo ~m4~s pc~r~L9arooss~
s
Fig. 6 illustrates a structure of a tokens use report, with means for token
use
diffusion among users.
Modes for Carrying out the Invention
A preferred embodiment of the present invention will now be described by
way of example and with reference to the accompanying drawings.
Referring to Fig. 1, a system for presenting reports on tokens to other users
and for
monitoring other's reports may include the following parts:
1. a transactions management unit 11, using tokens. The unit 11 is
activated when the user requires to perform a service for which payment
using tokens is required. For example, such a service may include a
special type of E-mail or an encryption procedure or other service
provided, on the Internet or elsewhere.
2. a tokens database 12, which includes information on tokens acquired
from the service provider, which is usually also the tokens issuer.
Unit 11 reads tokens from the database 12 each time there is a
requirement to use the service and pay with tokens. Only if there are
tokens available, will the service be performed. If the service is
performed, then the database 12 is instructed to "cancel" the token,
that is to indicate that the token was used.

CA 02314098 2000-07-07
WO 99/Z7475 PCT/IL98/00563
9
Thus, database 12 serves as a storage for tokens, keeping both used and
available tokens and additional information related to these tokens.
3. tokens use monitoring unit 13, to verify the correct use of tokens by
other parties who connect to the system as shown.
4. a database of tokens reports 14, including information on acquired
tokens available for performing the service for fee. Each token also
includes status indicating means, which change from "ready" to "used" or
"canceled" after a token is used.
5. a communication channel to other users 15. Channel 15 may include a
telephone line and/or a wireless link or a connection to Internet or
other means for pertorming a digital communication session with other
users.
Tokens may be used as payment means for a wide variety of services, for
example including but not limited to registered E-mail, legal E-mail,
permits generation and management, certificates generation and
management.
Tokens may also be used to pay for products in commercial transactions
over the Internet.
To achieve these goals, the system detailed in Fig. 1 may be used,
together with methods to be detailed below.

CA 02314098 2000-07-07
wo ~n~4~s pcrnL~oos~
Method 1 for providing~aid services
A method for providing service with tokens used as payment means may
include the following steps:
a. Transaction management unit 11 receives from the local user a
request to perform a service for which payment with tokens is required
b. Unit 11 checks whether there are yet unused tokens available in the
system, that is in tokens database 12, that is tokens whose status
is "ready" as opposed to uused" or "canceled".
If an unused token was found, go to step (c);
If there are no available tokens, then indicate to the user that the
service cannot be performed because of lack of tokens, then END.
If there are no available tokens, then indicate to the user that the
service cannot be performed because of lack of tokens, then END.
c. Unit 11 requests and/or retrieves information on an available (unused
as yet) token from the database or storage unit 12. The status of the
token which was retrieved will be automatically changed in the database
12, and will thereafter be designated as "used" or "canceled".
d. During the subsequent transaction with another party, unit 11 sends
information relating to the used token to that other party, through
channel 15.

CA 02314098 2000-07-07
wo ~m4~s rc~rnlr9aroos~
11
Method 2 for monitoring faro er use of tokens
A method for monitoring proper use of tokens by other users may include the
following steps:
a. Tokens use monitoring unit 13 receives reports from other users,
indicating their use of tokens and cancellation of tokens in each
transaction.
b. Unit 13 transfers the received reports to a database of tokens
reports 14, which including information on use of tokens by other users.
Preferably, latest information on tokens is store, and oldest
information is discarded.
c. Unit 13 requests and/or retrieves information on previous reports
from the same user from database 14.
d. Unit 13 processes reports on the use of tokens by the other user,
comparing according to predefined criteria.
e. If a criterion was violated, that is the reports indicate a fraud or
inappropriate use of tokens, then unit 13 stores that information in
database 14 and/or displays a violation report and/or reports that to
the tokens issuer, and/or sends a note to the user of such token.

CA 02314098 2000-07-07
wo ~m4~s PcrnL9sroos6s
12
Thus, the structure and operation of the system detailed above allows
for secure payment over a distributed network. There is no need that the
tokens provider take part in each and every transaction, since two
parties can do business and report use of tokens directly. Thus there
is no requirement that a huge center be organized, to approve each
transaction.
Moreover, the abovedetailed system and method allow a third party (the
tokens issuer) to collect a fee from a transaction between two parties,
even though that third party does not participate in transactions
between the two parties.
For example, with a walkie-talkie/ wireless sets provider, the provider
can now collect a fee per call, using tokens. Tokens may be loaded into
the wireless set and their use accounted for as detailed above,
including a report to the other party for verification purposes.
Using this invention, wireless sets like citizen band systems can now be
sold at a discount or even distributed for free, like cellular sets.
Until now, that was not possible since, whereas cellular sets connect
through a center and bring a fee to the manufacturer each time the set
is used, wireless sets are used directly between users and a fee policy
could not be enforced.
Another example - now a software package for premium services
relating to E-mail may be freely distributed, and the provider may get
paid as the package is used.

CA 02314098 2000-07-07
WO 99/27475 PGT/IL98/00563
13
Although the package is used directly between users, without the intervention
of
the software provider, the use of tokens as per the present invention ensures
that
the software provider will be paid for the service.
The invention may be advantageously used to pay for services on a
network, especially for services required irregularly, where the user
desires to pay per use.
For example, a user may desire to connect to a database. The prevalent
method of payment now in use is a subscription for a fixed period, so
that during that period the user is permitted unlimited access to the
database, or a given amount of time. This may not be a satisfactory
solution, since there are so many databases and other services now
available, that a user may desire to use just a short time in each of
them. But it may not be economical to subscribe to all of them, and to
pay for a long time in each, where the user expects not to fully utilize
all that time.
The use of tokens according to the present invention solves the problem
since now the user is free to select each of the services which accept
these tokens, and pay only as per actual use.
Other examples of resources in a net may be hardcopy printers belonging
to a third party. A user may use the printer and pay with tokens,
according to the volume of use, or the number of pages printed.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
14
Another example would be for network computers. A new concept in
computers relates to a system where each user will have just a simple,
low cost computer, and will use software resources available in the net.
For a commercially viable system, there should be a payment for the use
of these resources.
Resources may include advanced word processors, database systems, super
fast signal processors and much more. There are so many resources
available, and so many users. There is the difficult problem of paying
for the use of these resources, and for accounting for actual use of
each resource by each user.
All these problems are solved with the tokens according to the present
invention, as detailed above. The provider of the services may offer the
services through many outlets. Separately, the provider sells tokens for
the use of these resources. Then the provider does not have to take part
in every transaction, but the tokens will be used and new tokens will
have to be bought by users, as detailed above.
The abovedetailed applications refer to payments to a third party for
services rendered.
Another important application of tokens is to actually pay to a second
party for a service or product. According to implementation, tokens may each
represent a fixed amount of money or time of use of resource, or a specific
number
of calls using a resource.

CA 02314098 2000-07-07
WO 99!27475 PGT/IL98/00563
A token may represent a prepaid amount of money, or a credit to that specific
amount.
An example involves not the Internet, but a local net, like a net
in a business center. Many firms may have offices in the center, and
they all may occasionally use services provided by other firms there,
like printing or copying or data archiving or CD-ROM programming or
ordering products like office supplies.
All the firms, customers and service providers, are connected through
the local communication net. Services are ordered through the net, and
payment is made with tokens according to the present invention.
Another example is in motels where a counter is activated for the use of
electricity or gas. The counter is coin operated, and the guest pays in
advance for a specific amount of the service to be used.
Here, tokens are used to actually pay to a second party for a service or
product. Unlike prior systems, here there is no need that the tokens
provider approve in real time each and every transaction.
Thus, no huge centers are required to support all the transactions in the
world.
Some amount of fraud is expected, but fraud has a good chance of being
detected
and may possibly be traceable to source. This is achieved with a relatively
low cost
center, that is a center which does not take part in every transaction and
does not
have to respond in real time.

CA 02314098 2000-07-07
wo ~m4~s rc~.~L~oos63
16
No system is completely secure, as intruders may intertere with the
authorization
process itself, may break the encryption codes or may devise other methods. In
a
commercial enterprise, what matters is the level of security versus the cost
to
achieve it.
If a statistically reasonable security is achieved at reasonable cost, that
may be
satisfactory; losses may be further reduced with insurance. This is a
practical
solution to security over the net.
Thus, an acceptable business solution can be achieved.
Fig. 2 details the structure of a token information management and
storage database.
This is one embodiment of information stored in the tokens database 12
(see Fig. 1 ) .
Database 12 may include token identification part 21 , which includes
(not shown) token unique serial number and optional additional
information, all signed or encrypted with the private key of the service
provider and/or the tokens issuer.
The optional information may include the value of a token, if several
products/services are available. Thus, the present invention is not
limited to use/payment with one service provider. Tokens may be
presented to various providers of services or products.
If token is presented to a third party, that party may require payment
from the tokens issuer, so in effect the issuer performs the actual
payment between users.

CA 02314098 2000-07-07
WO 99/27475 PCTIIL98/00563
17
A token status part 22, indicates whether the token was already used or
not. If not - it is ready and available for the next use
A date of use 23, available only for used tokens. Allows subsequent
monitoring of transactions and adequate use of tokens.
A time of use 24, only used for used tokens. Allows more precise
monitoring of the use of tokens, since many tokens may be used daily and
a finer time resolution may be required. In the example, time is given
in hours.minutes. A more precise indication may be used, for example
down to seconds and even parts of a second. The exact time is less
important, than the relative timing of consecutive reports from any
specific user.
Tokens are preferably arranged in chronological order of use, with last
used token placed first in the list, as shown. Unused tokens are
preferably arranged in chronological order with earliest token first.
This structure allows for more efficient, faster processing by recipient.
In the example shown, the tokens T-100, T-101 and T-102 were already
used, as indicated in the status part 22 and the date of use 23 and time 24.
Tokens T-103 to T-111, T-903 and T-903 are ready to use.
Tokens T-100 to T-111 may have been issued at a specific date, with
tokens T-903 and T-903 issued at a later date. Hence the different
serial number and the relative location in the table.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
18
Fig. 3 illustrates the structure of a report detailing the use of tokens.
This is sent to another user during a transaction therebetween which
requires that User-1 will "spend" or "use" or "lose" a token.
The report is sent so as to show the other party that indeed payment was
performed for the transaction.
This report enables the second party to verify that indeed User-1 had a
token available prior to the transaction, and did destroy that token
during the transaction, as required.
As detailed there, the logical parts of the report in column 31, with an
example of
possible specific values assigned to these parts in column 32
User of service ID 331 contains the name or nickname or other
information to identify the user who pays with tokens. The name should
be understood or traceable by the service provider and/or tokens issuer,
since they are the ultimate party who monitors the use of their tokens.
In this example, a nickname "User-1 " is reported.
Tokens are preferably arranged in chronological order of use, with the
last used token (the token used in the present transaction) being placed first
in
the list, as shown.
The report may otherwise indicate which token was used last, and the
order of use of previous tokens. This information is helpful to allow
monitoring for correct use of tokens, as detailed below.

CA 02314098 2000-07-07
wo ~n~4~s rrrnL~oos63
19
There may be a limit on the number of used tokens reported, to keep the
communications effective. Then - only the last tokens) may be
transmitted to other users, for example one or five or ten or 100 for
example. Here, only three previous tokens are shown, however the actual
number of tokens may be much larger.
The date of use 332 indicates the date of use of the service, that is the
day when a specific token (to be detailed as well) was destroyed or
canceled. In the example, the date is 10.26.97.
The time of use 333 is the time when the token was canceled, here 19.55 .
In one embodiment of the invention, a common time may be used by all the
users in the system, for example Greenwich time.
In another embodiment, each user presents his/her local time. Since
time of various reports is compared separately for each user, there is
no need to compare time reports among different users, so there is no
need for a uniform time base.
In other words, consecutive reports from any user may be checked to
ensure that the time and date reported therein are in chronological
order. It is not allowed to prevent a report, and to send it at a later
date - this may be indicative of fraudulent activity. The time
relationship among reports from different users, however, may not
include significant information indicative of possible fraud, and in any
case are much more difficult to verify.

CA 02314098 2000-07-07
wo ~n~4~s rcr~L9s~oos~
The token ID 334 indicates the specific token which was used in the present
transaction, in this example the value was T-103. Token ID 334 may
include (not shown) an unique serial number, together with the signature
of the tokens issuer. The signature may use the private key of the
issuer. Alternatively, an unique combination of serial code and date may
be used. In still another embodiment, a digital code indicative of time
of issue may be used.
Additional optional information may include the details of the buyer of
that token (to whom it was sold), an expiry date and/or other
information. All the information may be signed by the tokens provider
Previous token ID 335 indicates the token which was used in a previous
transaction by User-1, that is the last token used before token T-103.
In the example, this was token T-102.
A report including this information allows the other party to the
transaction to verify that the tokens reported to be used are changing
with time, that is that User-1 updates his/her tokens database and
presents each time a different token, thus User-1 pays for the
transaction with tokens, as required.
The date of use 336 may be useful for monitoring the use of tokens, here
its value is 10.22.97 .
The time of use 337 allows a more precise comparison and evaluation of
reports, here it was 14.50 .

CA 02314098 2000-07-07
WO 99/Z7475 PCT/IL98/00563
21
A. plurality of previously used tokens is preferable since it increases
the chance that the other party has in their database a related report,
and can detect discrepancies if the use of tokens was not proper.
In the example illustrated, previous token ID 338 is T-101, and its date
of use 339 is 10.22.97 . Time of use 340 is 13.15.
Still a previous token used ID 341 was, in this example, T-100.
The date of use 342 was 10.22.97, and the time of use 343 was 11.05 .
The signature of user 344 is proof that User-1 sent that report. It may
include a hash or CRC of the abovementioned information, encrypted with
the private key of User-1.
Using the information in the report as detailed in Fig. 3, a tokens use
monitoring unit 13 (See Fig. 1) at another user's facility may monitor
the transaction for proper use of tokens. The monitoring unit 13 uses
information in a database of tokens reports 14 attached thereto.
An implemeritation of a monitoring routine is illustrated as Method 13
below. The method is automatically performed by computer means (not
shown) at another user's facility.

CA 02314098 2000-07-07
WO 99/Z7475 PCT/IL98/00563
22
Method 3 for monitoring use of tokens
A second user, upon receiving a tokens use report, can evaluate the
report to determine whether improper use of tokens has been made by
User-1, by performing the following steps:
a. The token ID, date and time of all tokens reported are compared, to
ensure that they are different. That is, there are no two tokens with
identical ID, and there are no two tokens which were used at exactly the
same date and time.
If two identical tokens or identical time/date was found - then a
discrepancy was detected, go to step (z) (store, display and/or report
misuse of tokens ).
b. The date and time of all tokens reported are compared, to verify
whether they are in chronological order, with the last token used
located first in the list.
If they are not in order - then a discrepancy was detected, go to step
(z) (store, display and/or report misuse of tokens ).
c. Each token in the report is compared with tokens stored in the
database of tokens reports 14 (see Fig. 1 ) , for User-1.
If a token with the same ID was detected, but with a different time/date, or a
token
with an identical time/date but with a different token ID was found in the
database,
then a discrepancy was detected, go to step (z).

CA 02314098 2000-07-07
wo 99n~4~s rcrnL9sroos~
23
d. The time span of the tokens in the report is evaluated, that is the
time between the first used token and the last used token.
If a token report was found in the database, whose time is within the
above time span but for which there is no corresponding token report in
the report, then a token report is missing, thus a discrepancy was
detected, go to step (z).
e. Conclusion: no discrepancy was found. END.
z. Conclusion: a discrepancy was detected. Store details of present
transaction, display to user and/or report misuse of tokens . END.
The above method is efficient in a statistical sense. It cannot
guarantee that absolutely no one will misuse the system, however misuse
on a large scale has a good chance of being detected. Thus, it is not
necessary that each user store huge databases with reports of past use
of tokens. Even with modest databases, a user who frequently misuses the
system has a good chance of being detected doing so.
The method can thus effectively prevent large scale fraud and avoidance
of payments due.
Fig. 4 illustrates the use of reports on tokens in transactions between
various users.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
24
As illustrated in Fig. 4(A), a first user 1 (User-1 ) may connect to
various other users. It is assumed in the example that first user 1 is
the party who has to pay with tokens for the transactions as detailed.
An identical method is used when user 1 is addressed by another party,
and that other party then sends a report instead.
A first user 1 connects through communication channel 15 to a second
user 18 (User-2 in the example).
A tokens use report 3 is sent from first user 1 to the second user 18.
Report 3 includes details on token T-104 (the presently used token) as
well as previously used tokens T-103, T-102, T-101 and T-100.
Actually a report 3 may be more detailed, to include for example
information as detailed in Fig. 3 above.
This is apparently a legitimate transaction with legitimate past
transactions, since all the tokens are different and in consecutive order.
A subsequent transaction is illustrated in Fig. 4(B). Here, the first
user 1 (User-1 ) connects to a third user 19 (User-51 ), through
communication channel 152. The communication channels may be different,
or the same channel may be used.
A tokens use report 38 is sent from first user 1 to third user 19.
Report 38 is an updated version of report 3 above, to indicate token
T-105 as the presently used token. Token T-104 now belongs to the
previously used tokens list, together with T-103, T-102 and T-101.

CA 02314098 2000-07-07
WO 99/17475 PGT1IL98/00563
Assuming that the reports are limited to four previous tokens, then
token T-100 (the oldest) is now removed from the report. The list may
include many more tokens, however it should preferably be limited
anyway, to prevent waste of communication time and of storage space.
Thus, a limit will be reached eventually, and then the oldest tokens
will be removed from subsequently transmitted reports.
A later transaction is illustrated in Fig. 4(C). Here, for example,
the first user 1 (User-1 ) connects again to the second user 18 (User-2).
A communication channel 152 may be used, maybe a channel different than
that used in the previous transaction illustrated in Fig 4(A).
A tokens use report 39 is sent from first user 1 to second user 18.
Again the report 39 is an updated version of report 38, to indicate
token T-106 as the presently used token. Tokens T-105, T-104 now belong
to the previously used tokens list, together with T-103 and T-102. Token
T-101 (the oldest) is now being removed from the report 39.
The reports 3 and 39 associated with the transactions with second user
18 now allow the second user 18 to compare the reports to verify whether
the first user 1 is using tokens properly, as detailed in Method 4
below.

CA 02314098 2000-07-07
wo ~ma~s
26
IlAethod 4 for monitoring the use of tokens
A user 18, upon receiving two subsequent token use reports 3, 39 from a
first user 1, may evaluate the reports to determine whether improper use
of tokens was made, by pertorming the following steps:
a. The tokens used in the two reports 3, 39 are compared to ensure they
are different (that is, the token ID is different).
If the same token is used in different transactions - then a discrepancy
was detected, go to step (z) (store, display and/or report misuse of tokens ).
In the example as shown, report 3 indicates that token T-104 was used
whereas later report 39 indicates the use of token T-105. Therefore,
there appear to be no discrepancy in this respect
b. The date and time of the tokens used in the two reports are
compared, to verify whether they are in chronological order .
If the later report 39 has the same date/time as the earlier report 3,
or if the later report 39 has an earlier date/time than the earlier
report 3 - then a discrepancy was detected, go to step (z) (store,
display and/or report misuse of tokens ).
In the example as shown, the date and time was not detailed in
reports 3, 38 and 39. The method should be applied taking in
consideration the presented of such information in one or other form, as
illustrated and described with reference to Fig. 3 above.

CA 02314098 2000-07-07
wo ~m47s pcTn~9sroos~
27
c. Each token in one report 39 is compared with the tokens stored in the
other report 3. If there is an overlap between the tokens, then the
tokens should appear in the same order, with none missing, otherwise a
discrepancy is declared.
For example, if report 39 details used tokens as T-107, T-106, T-105,
T-103 and T-102, whereas report 3 indicated tokens T-104, T-103, T-102,
T-101 and T-100, then a discrepancy was tound - in the later report 39
the use of token T-104 between T-103 and T-105 is missing.
It was probably erased to allow fraudulent later reuse of that token
if a discrepancy was detected, then go to step (z).
d. Conclusion: no discrepancy was found. END.
z. Conclusion: a discrepancy was detected. Store details of present
transaction, display to user and/or report misuse of tokens . END.
Again, the method is efficient in a statistical sense. However, by comparing
two or
more reports from the same user, a higher probability of detecting fraud by
the first
user 1 is achieved.
Fig. 5 illustrates another embodiment of the structure of a report detailing
the use
of tokens, with means for transferring information on use of tokens between
users.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
28
The logical parts of the report in column 31, with an example of
possible specific values assigned to these parts in column 32.
The report here differs from that illustrated in Fig. 3 in that now the
sender signs each token used, separately. Thus, the report includes
User of service ID 331 contains the name or nickname or other
information to identify the user who pays with tokens.
Again, tokens are preferably arranged in chronological order of use,
with the last used token placed first in the list, as shown.
Date of use 332 indicates the date of use of the service, that is the
day when a specific token (to be detailed as well) was destroyed or
canceled. In the example, the date is 10.26.97.
Time of use 333 is the time when the token was canceled, here 19.55 .
Token ID 334 indicates the specific token which was used in the present
transaction, in this example the value was T-103.
Signature-3 346 is the signature of the sender (User-1 ) on the last
token used, that is T-103 and related information. In the example, its
value is 3597711.
This is the difference from the report in Fig. 3 - now each token
reported is also separately signed by the sending party, that is the
user who paid with that token and prepared the report shown.

CA 02314098 2000-07-07
wo ~m4~s PcrnL9s~oos~
29
Similarly, other tokens in the report are each signed with Signature-2 (347),
Signature-1 (348) and Signature-0 (349) respectively.
This structure allows the recipient to distribute part of the token
information to other users, so as to diffuse the information relating to
the use of tokens. This allows each user to store information on the use
of tokens from various users in their respective database of tokens
reports 14, and to subsequently compare the information with other
reports from other users or from a user directly reporting to them on
the use of tokens.
This is automatically implemented in the tokens use monitoring unit 13, see
Fig. 1.
Fig. 6 illustrates a structure of a tokens use report, with means for
diffusion of
reports about token use among other users.
Again, the logical parts of the report are illustrated in column 31, with an
example
of possible specific values assigned to these parts included in column 32.
The report includes two parts, a report on own use of tokens 41 and a
report on other's use of tokens 42
The report 41 includes information on last tokens used by the present
sender, as detailed in Fig. 5 above and the related description. It
includes an indication of the user of service ID 331, with the name or
nickname or other information to identify the sender.

CA 02314098 2000-07-07
wo ~ma~s ~.aL~goos~
Date of use 332 indicates the date of use of the service, that is when the
token 334
was canceled.
Time of use 333 is the time when the token 334 was canceled.
Token ID 334 indicates the specific token which was used in the present
transaction.
Signature-3 346 is the signature of the sender (User-1 ) on the last token
used.
Similarly, report 41 further includes information on previously used
tokens as illustrated in Figs. 6 and 5.
A report on others' use of tokens 42 is a collection of token reports
from various user, as sent by other users when they connected to the
present sender and reported their use of tokens.
Thus, in the present example, user of service ID 421 refers to an user
designated as User-5, who had previously reported the use of a token on
the Date of use 422, that is the date when the token 424 was canceled
in the User-5 tokens database.
Time of use 423 is the time when the token 424 was canceled.
Token ID 424 indicates the specific token which was then used.
Signature-37 425 is the signature of the sender (User-5) on the report
relating to the use of that token, T-788 used.
Similarly, report 42 further includes information on other users' use of
tokens, like User-19 illustrated there.

CA 02314098 2000-07-07
WO 99/Z7475 PGT/IL98/00563
31
Each such token report is extracted from a report from another user, in
the form as illustrated in Fig. 5. Thus, if the sender signs for each
token reported, then each token can be included by recipient in his/her
reports to other users.
Thus, a report regarding the use of a token becomes highly visible,
since it may be communicated to many other users.
The advantage of the method is that the public becomes the watchdog over
the proper use of the tokens.
The process is automatic, thus fast and effective, and does not require
an effort on the part of the user.
Since the reports on the use of tokens may be further transferred to
other users, there is no indication of the parties to a specific
transaction, at a given time. Thus, the privacy of the transactions is
preserved, while allowing the monitoring of the use of tokens by many
users.
When a user communicates with the token issuer entity, they can transfer the
various reports stored in that user's storage. The tokens issuer can then
perform
further tests and comparisons based on that information and additional
information
from other users, to detect illegitimate use of tokens.

CA 02314098 2000-07-07
WO 99IZ7475 PCT/IL98/00563
32
Method 5 for dissemination of information relating to use of tokens
a. unit 11 requests and/or retrieves information on an available (unused
as yet) token from the database or storage unit 12, as well as
information on previously used tokens;
b. unit 11 prepares a first part of a token use report, including
information on the last token used as well as previous tokens used by
the present user;
c. tokens use monitoring unit 13 request and/or retrieves from unit 14
reports on the use of tokens by other users, and transfers these reports
to unit 11;
d. unit 11 prepares a second part of a token use report, including
information on the use of tokens by other users;
e. a report including the first part prepared in step (b) and a second
part prepared in step (d) is sent to another user during a paid
transaction.
In another embodiment of the invention, the second part of the report in step
(d)
may be performed by unit 13, then sent to unit 11 or directly to the other
user.

CA 02314098 2000-07-07
wo ~n~a~s ~c~r~~9s~oos~3
33
In still another embodiment, information relating to violation of token
use rules by others is always included in the token use report. Thus the
information on violations or fraud is diffused throughout the system,
until it reaches the tokens issuer or other party with enforcing
capabilities.
JlAethod 6 for verification of the use of tokens
a. Tokens use monitoring unit 13 receives reports from other users, indicating
their
use of tokens, as well as information on the use of tokens by others;
b. Unit 13 transfers the received reports to a database of tokens reports 14;
c. Unit 13 organizes the information in database 14 according to chronological
order and separately for each user;
d. For each user, the reports on the use of tokens are processed as detailed
in the
following steps, to detect conflicts or inconsistencies;
e. The token ID, date and time of all tokens reported are compared, to
ensure that they are different. That is, there are no two tokens with
identical lD, and there are no two tokens which were used at exactly the
same date and time.
If two identical tokens or identical time/date was found - then a discrepancy
was
detected, go to step (z) (store, display and/or report misuse of tokens ).

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
34
f. The date and time of all tokens reported are compared, to verify whether
they are
in chronological order, with the last token used located first in the list.
If they are not in order - then a discrepancy was detected, go to step
(z) (store, display and/or report misuse of tokens ).
g. Each token in the report is compared with tokens stored in the database of
tokens reports 14 (see Fig. 1 ) , for User-1.
If a token with the same ID was detected, but with a different time/date, or a
token
with an identical time/date but with a different token ID was found in the
database,
then a discrepancy was detected, go to step (z).
h. The time span of the tokens in the report is evaluated, that is the
time between the first used token and the last used token.
If a token report was found in the database, whose time is within the
above time span but for which there is no corresponding token report in
the report, then a token report is missing, thus a discrepancy was
detected, go to step (z).
i. Conclusion: no discrepancy was found. END.
z. Conclusion: a discrepancy was detected. Store details of present
transaction, display to user and/or report misuse of tokens . END.

CA 02314098 2000-07-07
WO 99/Z7475 PCT/IL98/00563
Moreover, the present invention discloses an effective method for
dissemination of tokens to users. One possible method is to create a
file "token° , to include an indication of the value of the token,
signed or encrypted with the private key of the tokens provider.
Each token may represent a fixed amount of money or time of use of
resource, or a specific number of calls using a resource, as the need be.
A disadvantage of the above method is that, for huge amounts of tokens
distributed to many users, it may be difficult for the tokens issuer to
keep track of them all, to prevent duplicates and to detect fraud.
Thus the tokens issuer may become a bottleneck in the digital commerce.
The above special requirements stem from the structure and operation of
a large-scale, distributed payment system.
A possible method to effectively distribute tokens to a huge
number of users and to keep track of them all is not to actually create
and distribute the tokens, but for the tokens issuer to give permits to
each user, to generate the tokens themselves, as detailed in Method 7.
Method 7 for tokens creation by users
a. User calls tokens issuer, and asks for a specific number (K) of
tokens. User pays for the tokens or uses credit, as per the business
arrangement between user and tokens issuer;

CA 02314098 2000-07-07
wo ~m4~s rc~.n~~oos~
36
b. Token issuer prepares a digital document, allowing the user to
generate K tokens, with specific parameters. These may include the value
of each token, and the serial number of the first and last token.
For example, the digital information in the document may effectively say:
"User-73 is hereby allowed to issue 100 tokens at value $10 each, with
serial numbers 240 to 339. Date issued: October 15, 1997. Valid for 6 months."
The above digital document is signed or encrypted with the private key
of the tokens issuer, and delivered to the user. Actually, the document
is delivered to a software package at the user's facility, a software
which is responsible for tokens issuing and accounting for, that is
unit 11, see Fig. 1;
c. To perform a paid transaction, the user software (unit 11 } checks
whether a token can be issued, according to the permit/digital document.
If positive, a counter of used tokens is incremented, and a token
prepared with a serial number which is the successor of the last token
generated, all within the serial numbers according to the digital document.
For example, a token may effectively include the following:
"Token No. 256, value $10, generated by User-73, according to permit
from Issuer-9" . The token is signed or encrypted with the private key
of User-73.

CA 02314098 2000-07-07
WO 99/Z7475 PCT/IL98/00563
37
If encrypted, then an indication to identify User-73 should be left en
clair, to allow decryption of the message. Go to step (d).
If all the tokens were already generated according to the digital
document issued in step (a), then no token is generated, and the
user is informed accordingly "no more tokens available". END.
d. Send the token prepared in step (c) together with the digital
document prepared in (a) to the other party, as proof of payment for the
present transaction. END.
A measure of safety is achieved in the above method, since the user
issuing these tokens may have to sign with his/her private key, so that
each token is traceable to source, and if there is suspicion of
fraudulent use, then a user may be held accountable.
On the other hand, this very possibility may prevent users from misusing
the tokens in the first place, thus achieving the desired safety.
Thus, the safety in this method is achieved not in a centralized system
with the center having "dictatorial" powers and intervening in each
transaction, but a distributed system "democratic" , where users
participate in enforcing the tokens and payment policy, and in checking
that other users do the same.
In another embodiment of invention illustrated in Method 7, a user will not
report to others about the use of tokens, however the system assigns to each
token a serial number, with number in ascending order.

CA 02314098 2000-07-07
WO 99/17475 PCT/IL98/00563
38
A recipient of a token may compare the serial number of the presently received
token with the serial number of a previous token or previous tokens. If the
serial
numbers are not all different from each other and in ascending order, this is
an
indication of tokens misuse. A tokens misuse is thus displayed for others to
see. The method is detailed below as Method 8.
Method 8 for tokens creation byr users
a. User calls tokens issuer, and asks for a specific number (K) of
tokens. User pays for the tokens or uses credit, as per the business
arrangement between user and tokens issuer;
b. Token issuer prepares a digital document, allowing the user to
generate K tokens, with specific parameters. These may include the value
of each token, and the serial number of the first and last token.
For example, the digital information in the document may effectively say:
"User-73 is hereby allowed to issue 100 tokens at value $10 each, with
serial numbers 240 to 339. Date issued: October 15, 1997. Valid for
6 months."
The above digital document is signed or encrypted with the private key
of the tokens issuer;

CA 02314098 2000-07-07
wo ~m4~s rcrnL9sroos63
39
c. To perform a paid transaction, the user software (unit 11 ) checks
whether a token can be issued, according to the permit/digital document.
If positive, a counter of used tokens is incremented, and a token
is prepared with a serial number which equals the previous serial number
plus a fixed increment (for example, the previous number plus 1 ), where
all the serial numbers are within the serial numbers according to the
digital document.
For example, a token may effectively include the following:
"Token No. 256, value $10, generated by User-73, according to permit
from Issuer-9" . The token is signed or encrypted with the private key
of User-73. Go to step (d) .
If a!I the tokens were already generated according to the digital
document issued in step (a), then no token is generated, and the
user is informed accordingly "no more tokens available". END.
d. Send the token prepared in step (c) together with the digital
document prepared in (a) to the other party, as proof of payment for the
present transaction. END.
In the above method, there is no need to indicate the date and time, since
the serial number of tokens may be used to detect misuse of tokens.
Various embodiments of the present invention will become apparent to
persons skilled in the art upon reading the present disclosure.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL98/00563
For example, the order of implementation of the steps in the above
methods may be interchanged, while still performing the basic function
detailed therein.
It is possible to use tokens of various value, where the value of each
token is embedded in the token ID as created by the token issuer.
This allows the user to pay various amounts for different services or
products, as the need be. This is equivalent to the use of different
money bills, each having a different value.
In this case, as the tokens are arranged in the order of their issue,
the tokens may also be arranged in the order of their value.
Alternately, several separate sections may be used in tokens database
12, each section including only tokens of a specific value.
To pay varying amounts of money, the methods may be updated to permit the use
of a plurality of tokens at one time/date. Such an activity will then be
considered as
valid.
The recipient has the ability to verify that the tokens are valid, by
performing a hash
or CRC, then decrypting the hash or CRC in the token with the known, public
key of
the tokens issuer, and comparing results. If the results do not correspond,
then the
tokens are false.

CA 02314098 2000-07-07
WO 99/27475 PCT/IL9$/00563
41
The recipient also has the ability to verify the signature of the
reports sending party, again by verifying the signature of that party as
detailed above: pertorm a hash or CRC, then decrypt the hash or CRC in
the report with the known, public key of the other user issuer, and compare
results.
If the results do not correspond, then the other user is an impostor.
Throughout the present disclosure, signature by a party involves the
computation of a hash or CRC of a piece of information, and encryption
of the hash or CRC with the private key of the sender.
A token may include additional information, for example a picture and/or
graphics and/or an audio message. Thus a digital token may resemble an
ordinary coin, by having a value attached thereto as well as additional
information.
A token may be used as letterhead or paper for a firm. The firm assigns
tokens to employees, who can use these tokens in official letters, for
example in E-mail messages. The token becomes the letterhead of the company
in this electronic paper application. The company may authorize employees to
use a token in each E-mail message sent in the course of their work.
Thus, the token is used as digital paper, to "write" messages thereon.
The tokens need not be prepaid by the user. It is possible to include
advertising in the token, with the firm benefiting from the advertising
paying for the use of tokens. This approach may be better suited for the
Internet environment, where services are generally free. Other methods to
replace direct payment by the user may be used.

CA 02314098 2000-07-07
wo ~m4~s ~cr~L9sioos,~
42
The advertising may be implemented in the additional information in the token,
which may include pictures, graphics, audio and/or other information.
It will be recognized that the foregoing is but one example of an apparatus
and
method within the scope of the present invention and that various
modifications will
occur to those skilled in the art upon reading the disclosure set forth
hereinbefore.

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Inactive: IPC expired 2023-01-01
Application Not Reinstated by Deadline 2016-08-19
Inactive: Dead - No reply to s.30(2) Rules requisition 2016-08-19
Deemed Abandoned - Failure to Respond to Maintenance Fee Notice 2015-11-19
Inactive: Abandoned - No reply to s.30(2) Rules requisition 2015-08-19
Inactive: S.30(2) Rules - Examiner requisition 2015-02-19
Inactive: Report - QC passed 2015-02-12
Inactive: IPC removed 2014-11-12
Inactive: First IPC assigned 2014-11-12
Inactive: IPC assigned 2014-10-30
Inactive: IPC assigned 2014-10-30
Amendment Received - Voluntary Amendment 2014-06-19
Inactive: S.30(2) Rules - Examiner requisition 2013-12-20
Inactive: Report - No QC 2013-12-12
Small Entity Declaration Request Received 2013-11-18
Small Entity Declaration Determined Compliant 2013-11-18
Maintenance Request Received 2013-11-18
Letter Sent 2013-10-17
Amendment Received - Voluntary Amendment 2012-04-18
Inactive: IPC expired 2012-01-01
Inactive: IPC expired 2012-01-01
Inactive: IPC removed 2011-12-31
Inactive: IPC removed 2011-12-31
Inactive: S.30(2) Rules - Examiner requisition 2011-10-18
Inactive: IPC deactivated 2011-07-29
Amendment Received - Voluntary Amendment 2009-08-12
Inactive: S.30(2) Rules - Examiner requisition 2009-02-13
Amendment Received - Voluntary Amendment 2007-01-23
Inactive: S.30(2) Rules - Examiner requisition 2006-07-25
Inactive: First IPC derived 2006-03-12
Inactive: IPC from MCD 2006-03-12
Inactive: IPC from MCD 2006-03-12
Inactive: IPC from MCD 2006-03-12
Letter Sent 2005-12-16
Reinstatement Request Received 2005-12-08
Reinstatement Requirements Deemed Compliant for All Abandonment Reasons 2005-12-08
Amendment Received - Voluntary Amendment 2005-12-08
Inactive: Office letter 2005-09-22
Inactive: Abandoned - No reply to s.30(2) Rules requisition 2005-08-29
Extension of Time for Taking Action Request Received 2005-08-26
Inactive: S.30(2) Rules - Examiner requisition 2005-02-28
Letter Sent 2003-08-27
All Requirements for Examination Determined Compliant 2003-07-09
Request for Examination Requirements Determined Compliant 2003-07-09
Request for Examination Received 2003-07-09
Revocation of Agent Requirements Determined Compliant 2002-11-26
Inactive: Office letter 2002-11-26
Inactive: Office letter 2002-11-26
Appointment of Agent Requirements Determined Compliant 2002-11-26
Revocation of Agent Request 2002-11-15
Appointment of Agent Request 2002-11-15
Inactive: Cover page published 2000-09-06
Inactive: First IPC assigned 2000-09-03
Letter Sent 2000-08-21
Inactive: Notice - National entry - No RFE 2000-08-21
Application Received - PCT 2000-08-18
Application Published (Open to Public Inspection) 1999-06-03

Abandonment History

Abandonment Date Reason Reinstatement Date
2015-11-19
2005-12-08

Maintenance Fee

The last payment was received on 2014-11-13

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Patent fees are adjusted on the 1st of January every year. The amounts above are the current amounts if received by December 31 of the current year.
Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
IMS SOFTWARE SERVICES, LTD.
Past Owners on Record
MORDHAI BARKAN
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Representative drawing 2000-09-05 1 5
Description 2000-07-06 42 1,248
Claims 2000-07-06 6 180
Drawings 2000-07-06 6 94
Abstract 2000-07-06 1 47
Description 2005-12-07 42 1,244
Claims 2005-12-07 5 173
Claims 2009-08-11 9 407
Claims 2012-04-17 5 211
Claims 2014-06-18 5 204
Notice of National Entry 2000-08-20 1 193
Courtesy - Certificate of registration (related document(s)) 2000-08-20 1 120
Reminder - Request for Examination 2003-07-21 1 112
Acknowledgement of Request for Examination 2003-08-26 1 173
Courtesy - Abandonment Letter (R30(2)) 2005-11-06 1 167
Notice of Reinstatement 2005-12-15 1 171
Courtesy - Abandonment Letter (R30(2)) 2015-10-13 1 163
Courtesy - Abandonment Letter (Maintenance Fee) 2015-12-30 1 172
Fees 2011-10-18 1 156
Fees 2012-10-24 1 156
PCT 2000-07-06 3 105
Correspondence 2002-11-14 3 79
Correspondence 2002-11-25 1 12
Correspondence 2002-11-25 1 19
Fees 2003-07-08 1 36
Fees 2001-09-10 1 36
Fees 2004-10-04 1 35
Correspondence 2005-08-25 1 41
Correspondence 2005-09-21 1 15
Fees 2005-08-25 1 33
Fees 2006-10-09 1 34
Fees 2007-11-08 1 37
Fees 2008-11-11 1 38
Fees 2009-11-04 1 40
Fees 2010-10-24 1 200
Fees 2013-11-17 1 48
Correspondence 2013-11-17 2 66