Method and system for copy-tracking distributed software featuring tokens containing a key field and a usage field

• US 6,070,171 A
• Filed: 05/15/1998
• Issued: 05/30/2000
• Est. Priority Date: 05/15/1998
• Status: Expired due to Fees

• Current Assignee: Micromind Incorporated, Palantir Software Incorporated
• Original Assignee: Micromind Incorporated, Palantir Software Incorporated
• Inventors: Snyder, J. Gary, Brooks, Peter P., Bliss, Steven
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): TRINH, WILLIAM B
• Application Number:
  US09/079,381
• Time in Patent Office: 746 Days
• Field of Search: 707/203, 705/55, 705/59
• US Class Current: 1/1
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: G06F 21/16 Program or content traceability, e.g. by watermarking
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

The present invention provides a central computer site on a computer network for detecting authorized or unauthorized duplication of software on computers connected to such a network. The computers on the network may be continually connected, like computers on a Local Area Network, or intermittently connected, like computers on the Internet. Every time a user of the distributed software attempts to execute that software, a connection to the central computer site on the network is made, and a previously-created information token is presented by the user'"'"'s software to the central site. The central site evaluates that token, and possibly issues a new token to be kept by the user for the next transaction. These transactions need no human intervention, and may take place without the software user'"'"'s knowledge. At the same time, the central site may provide or withhold permission for the user to execute the distributed software. Using this information token, the central site can detect when a user uses a copy not made at the factory and track the execution of any such software copies. The central site need not know the identity of those using the software, nor the identities of the computers on which the software is executed.

Claims

1. A method of copy-tracking distributed software programs over a computer network after the programs are distributed to users comprising the steps of:

(a) encoding a plurality of a distributable computer-readable media with (1) a Software Payload to be tracked, (2) a Tracker Client program and (3) a Current Token readable by the Tracker Client program and including a Key field and a Usage field;

(b) installing a Tracker Server program on a central computer in the network, the Tracker Server program including a database for storing Current Tokens received from the Tracker Client programs;

(c) selectively installing the encoded media on respective user computers that are connectable to the network;

(d) operating each one of the user computers to execute the Tracker Client program on the encoded medium installed thereon to access the Tracker Server program on the central computer via computer-to-computer communications over the network;

(e) the user computer of step (d) executing the Tracker Client program to read the Current Token on the encoded medium installed thereon and to send the Current Token to the Tracker Server program;

(f) the central computer executing the Tracker Server program to validate the Current Token of step (e);

if the Current Token is invalid the Tracker Server program is executed to request a re-send or to inform the Tracker Client program to prevent access to the Software Payload;

(g) if the Tracker Server program validates the Current Token in step (f) and the Usage field is set to zero to indicate that the Tracker Client program is initially communicating with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (2) to store at least the Key of the new Current Token in the Tracker Server database, (3) to set the Usage field to one, and (4) to indicate to the Tracker Client program to permit execution of the Software Payload;

or

(h) if the Tracker Server program validates the Current Token in step (f) and the Usage field is set to greater than zero to indicate that the Tracker Client program has previously communicated with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to determine whether the Key in the Key field matches a Key in the Tracker Server database, and if there is a match, (2) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (3) to store at least the Key of the new Current Token in the Tracker Server database, (4) to increment the Usage field by one, and (5) to indicate to the Tracker Client program to permit execution of the Software Payload; and

if in (1) above the Key in the Key field does not match a Key in the Tracker Server database, optionally informing the Tracker Client program to prevent access to the Software Payload; and

(i) repeating steps (d) to (h) for the other user computers.

2. The method of claim 1 wherein in step (h) the Tracker Server program instructs the Tracker Client program to prevent access to the Software Payload whenever the Key in the Current Token does not match a Key in the Tracker Server database, and the Tracker Client program is executed by the user computer to prevent such access.

3. The method of claim 1 further comprising the user computer executing the Software Payload whenever the Tracker Client program receives an indication from the Tracker Server program to permit execution of the Software Payload.

4. The method of claim 1 wherein in step (h) a copy the Tracker Client program is detected when a Key in the Key field does not match a Key in the Tracker Server database, and wherein the Tracker Server program increments a database for recording a current number of copies detected for the respective Current Token.

5. The method of claim 1, wherein the Keys are each unique characters formed of randomly generated numbers and/or letters.

6. The method of claim 1 wherein initially the Current Token of each distributable medium includes a Base Serial Number field with a Base Serial Number therein and an empty Key field;

when the Tracker Client program first communicates the Current Token to the Tracker Server program, the Tracker Server program searches the Tracker Server database to confirm that the Base Serial Number has not been previously received, and the Tracker Server program creates a unique Key and places the Key in the Key field of the Current Token to form the new Current Token;

the Tracker Server program also stores the new Current Token including the Base Serial Number and the created Key; and

thereafter when the Tracker Server program receives a Current Token with a Base Serial Number and Key that match the stored Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client along with permission to execute the Software Payload.

7. The method of claim 1 wherein the Current Token of each distributable medium includes a Base Serial Number and a Key, and wherein if the Tracker Server program receives a Current Token having a Base Serial Number and a Key from a Tracker Client, and the Key does not match the Key associated with the Base Serial Number stored in the Tracker Server database, then an unauthorized copy has been detected, and optionally the Tracker Server program sends the Tracker Client program an instruction refusing permission to execute the Software Payload.

8. The method of claim 7 wherein the Tracker Server program sends the Tracker Client program an instruction refusing permission to execute the Software Payload.

9. The method of claim 1 wherein initially the Current Token of each distributable computer-readable medium includes as the unique component an empty Base Serial Number field and an empty Key field;

when the Tracker Client program first communicates the Current Token to the Tracker Server program, the Tracker Server program recognizes the empty Base Serial Number field and the empty Key field and advances to step (g) wherein the Tracker Server program places a distinctive Base Serial Number in the Base Serial Number field and creates a unique Key and placing the unique Key in the Key field of the Current Token to form the new Current Token, and the new Current Token is returned to the Tracker Client program with permission to execute the Software Payload;

the Tracker Server program also stores the new Current Token including the distinctive Base Serial Number and the created Key in the Tracker Server database; and

thereafter whenever the Tracker Server program receives a Current Token with a Serial Number and a Key that match the stored distinctive Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client program along with permission to execute the Software Payload.

10. The method of claim 1 wherein in step (a) the Current Token further includes a Base Serial Number in an unchangeable Base Serial Number field.

11. The method of claim 1 wherein the distributable computer-readable media are manufactured by a strict duplication method which makes only identical copies in batches with all copies in each batch having a common batch Base Serial Number, and wherein initially the Current Token of each distributable medium in the batch includes a Base Serial Number field with the common Base Serial Number therein and an empty Key field;

when the Tracker Client program first communicates the Current Token of each one of the distributable computer-readable media to the Tracker Server program, the Tracker Server program searches the Tracker Server database to confirm that the common Base Serial Number is authorized, and the Tracker Server program changes the component of the Current Token by creating a unique Key and placing the Key in the Key field of the Current Token to form the new Current Token;

the Tracker Server program also stores the new Current Token including the common Base Serial Number and the created Key; and

thereafter when the Tracker Server program receives a Current Token with a Base Serial Number and Key that match the stored common Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client along with permission to execute the Software Payload.

12. The method of claim 1 wherein the Current Token comprises a plurality of fields including Key, Copy and Usage represented by:

space="preserve" listing-type="equation">Key;

00-Copy;

0-Usage;

0

in which;

the Usage field tracks the number of times the Tracker Client program is used,

the Key is formed of unique characters created by the Tracker Server program for the Current Token and is also stored in the Tracker Server database, and functions to validate uses of the Current Token subsequent to the first time the Tracker Client program and Tracker Server program communicate, wherein if the Tracker Client program presents an invalid Key to the Tracker Server program (i) the Tracker Server program will reject the invalid Key and inform the Tracker Client program to disallow usage of the Software Payload if the Tracker Server program is programmed for unauthorized copy-rejection, or (ii) the Copy field is used to count the number of unauthorized copies if the Tracker Server program is programmed to permit access to the Software Payload by an unauthorized copy; and

the Copy field is initially set by the Tracker Server program, and contains the number of unauthorized copies known by the Tracker Server program if the Tracker Server program permits use of unauthorized copies.

13. The method of claim 12 wherein the Current Token further includes a Base Serial Number which comprises a plurality of fields including Customer number, Batch number, Sequence number and Check digits represented by:

space="preserve" listing-type="equation">customer;

W-batch;

X-sequence;

Y-check;

Z;

wherein W, X, Y and Z are numbers; and

wherein abbreviations and compression are optionally used.

14. The method of claim 1 wherein the Software Payload is a software program and/or electronic data.

15. The method of claim 1 wherein a list of authorized Base Serial Numbers is stored in the Tracker Server database, and wherein the Base Serial Number of each incoming Current Token is compared with this list and if not found therein the Current Token is considered invalid.

16. A system for copy-tracking distributed software programs over a computer network after the programs are distributed to users comprising:

a plurality of a distributable computer-readable media encoded with (1) a Software Payload to be tracked, (2) a Tracker Client program and (3) a Current Token readable by the Tracker Client program and including a Key field and a Usage field;

a central computer in the network, the central computer having installed thereon a Tracker Server program including a database for storing Current Tokens received from the Tracker Client programs;

a plurality of user computers connectable to the network, each one of the user computers having operatively associated therewith one of the encoded computer-readable media;

a plurality of means each including one of the user computers for executing the Tracker Client program on the encoded medium operatively associated therewith;

(a) to access the Tracker Server program on the central computer via computer-to-computer communications over the network;

(b) to read the Current Token on the encoded medium operatively associated therewith and to send the Current Token to the Tracker Server program; and

(c) to execute the Software Payload whenever the Tracker Client program receives an indication from the Tracker Server program to permit execution of the Software Payload; and

means including the central computer for executing the Tracker Server program;

(d) to validate each Current Token sent thereto; and

if the Current Token is invalid the Tracker Server program is executed to request a re-send or to inform the Tracker Client program to prevent access to the Software Payload;

(e) if the Tracker Server program validates the Current Token in step (d) and the Usage field is set to zero to indicate that the Tracker Client program is initially communicating with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (2) to store at least the Key of the new Current Token in the Tracker Server database, (3) to set the Usage field to one, and (4) to indicate to the Tracker Client program to permit execution of the Software Payload;

or

(f) if the Tracker Server program validates the Current Token in step (d) and the Usage field is set to greater than zero to indicate that the Tracker Client program has previously communicated with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to determine whether the Key in the Key field matches a Key in the Tracker Server database, and if there is a match, (2) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (3) to store at least the Key of the new Current Token in the Tracker Server database, (4) to increment the Usage field by one, and (5) to indicate to the Tracker Client program to permit execution of the Software Payload; and

if in (1) above the Key in the Key field does not match a Key in the Tracker Server database, optionally informing the Tracker Client program to prevent access to the Software Payload.

17. The system of claim 16 wherein initially the Current Token of each distributable medium includes a Base Serial Number field with a Base Serial Number therein and an empty Key field;

when the Tracker Client program first communicates the Current Token to the Tracker Server program, the central computer executes the Tracker Server program to search the Tracker Server database to confirm that the Base Serial Number has not been previously received, and the Tracker Server program creates a unique Key and places the Key in the Key field of the Current Token to form the new Current Token;

the Tracker Server program also stores the new Current Token including the Base Serial Number and the created Key in the Tracker Server database; and

thereafter when the Tracker Server program receives a Current Token with a Base Serial Number and Key that match the stored Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client along with permission to execute the Software Payload;

or

thereafter when the Tracker Server program receives a Current Token having a Base Serial Number and a Key from a Tracker Client, and the Key does not match the Key associated with the Base Serial Number stored in the Tracker Server database, then an unauthorized copy has been detected, and optionally the Tracker Server program sends the Tracker Client program an instruction refusing permission to execute the Software Payload.

18. A computer-readable medium for use in a system for copy-tracking distributed software programs over a computer network after the programs are distributed to users comprising:

the computer-readable medium having encoded thereon (i) a Software Payload to be tracked, (ii) a Tracker Client program and (iii) a Current Token readable by the Tracker Client program, said Current Token including a key field and a usage field;

the Tracker Client program being computer executable to interact with a remote Tracker Server program executable by a central computer on the network for copy-tracking the distributed medium, the Tracker Server program maintaining a database of Current Tokens received from the Tracker Client (TC) program and other TC programs that are executable by computers on the network, the database being used for validating Current Tokens received from the TC programs;

the computer-readable media being encoded with the following computer executable Tracker Client program instructions;

(a) to access the Tracker Server program on the central computer via computer-to-computer communications over the network;

(b) to read the Current Token on the computer-readable medium and to send the Current Token to the Tracker Server program;

(c) when the Tracker Server program validates the Current Token for execution of the Software Payload, to store a new Current Token received from the Tracker Server program for use when the Tracker Client program next accesses the Tracker Server program, the new Current Token including a new Key in the Key field and an incremental increase in the Usage field; and

(d) to execute the Software Payload whenever the Tracker Client program receives an authorization from the Tracker Server program for execution of the Software Payload, or to deny access to the Software Payload whenever the Tracker Client program receives an instruction from the Tracker Server program refusing permission to execute the Software Payload.

19. The computer-readable medium of claim 18 wherein initially the Current Token of each distributable medium includes a Base Serial Number field with a Base Serial Number therein.

20. A method of copy-tracking distributed Software Payloads over a computer network after the Software Payloads are distributed to users comprising the steps of:

(a) selectively distributing a plurality of Software Payloads encoded with a Tracker Client program and a Current Token readable by the Tracker Client program and including a Key field and a Usage field;

(b) installing a Tracker Server program on a central computer in the network, the Tracker Server program including a database for storing Current Tokens received from the Tracker Client programs;

(c) installing the distributed Software Payloads on respective user computers that are connectable to the network;

(d) operating each one of the user computers to execute the Tracker Client program on the distributed Software Payload installed thereon to access the Tracker Server program on the central computer via computer-to-computer communications over the network;

(e) the user computer of step (d) executing the Tracker Client program to read the Current Token on the distributed Software Payload installed thereon and to send the Current Token to the Tracker Server program;

(f) the central computer executing the Tracker Server program to validate the Current Token of step (e);

if the Current Token is invalid the Tracker Server program is executed to request a re-send or to inform the Tracker Client program to prevent access to the Software Payload;

(g) if the Tracker Server program validates the Current Token in step (f) and the Usage field is set to zero to indicate that the Tracker Client program is initially communicating with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (2) to store at least the Key of the new Current Token in the Tracker Server database, (3) to set the Usage field to one, and (4) to indicate to the Tracker Client program to permit execution of the Software Payload;

or

(h) if the Tracker Server program validates the Current Token in step (f) and the Usage field is set to greater than zero to indicate that the Tracker Client program has previously communicated with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to determine whether the Key in the Key field matches a Key in the Tracker Server database, and if there is a match, (2) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (3) to store at least the Key of the new Current Token in the Tracker Server database, (4) to increment the Usage field by one, and (5) to indicate to the Tracker Client program to permit execution of the Software Payload; and

if in (1) above the Key in the Key field does not match a Key in the Tracker Server database, optionally informing the Tracker Client program to prevent access to the Software Payload; and

(i) repeating steps (d) to (h) for the other user computers.

21. The method of claim 20 wherein the Software Payloads are electronically-deliverable.

22. The method of claim 21 wherein in step (h) the Tracker Server program instructs the Tracker Client program to prevent access to the Software Payload whenever the Key in the Current Token does not match a Key in the Tracker Server database, and the Tracker Client program is executed by the user computer to prevent such access.

23. The method of claim 21 further comprising the user computer executing the Software Payload whenever the Tracker Client program receives an indication from the Tracker Server program to permit execution of the Software Payload.

24. The method of claim 21 wherein in step (h) a copy the Tracker Client program is detected when a Key in the Key field does not match a Key in the Tracker Server database, and wherein the Tracker Server program increments a database for recording a current number of copies detected for the respective Current Token.

25. The method of claim 21, wherein the Keys are each unique characters formed of randomly generated numbers and/or letters.

26. The method of claim 21 wherein initially the Current Token of each electronically-distributable Software Payload includes a Base Serial Number field with a Base Serial Number therein and an empty Key field;

when the Tracker Client program first communicates the Current Token to the Tracker Server program, the Tracker Server program searches the Tracker Server database to confirm that the Base Serial Number has not been previously received, and the Tracker Server program creates a unique Key and places the Key in the Key field of the Current Token to form the new Current Token;

the Tracker Server program also stores the new Current Token including the Base Serial Number and the created Key; and

thereafter when the Tracker Server program receives a Current Token with a Base Serial Number and Key that match the stored Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client along with permission to execute the Software Payload.

27. The method of claim 21 wherein the Current Token of each electronically-distributable Software Payload includes a Base Serial Number and a Key, and wherein if the Tracker Server program receives a Current Token having a Base Serial Number and a Key from a Tracker Client, and the Key does not match the Key associated with the Base Serial Number stored in the Tracker Server database, then an unauthorized copy has been detected, and optionally the Tracker Server program sends the Tracker Client program an instruction refusing permission to execute the Software Payload.

28. The method of claim 27 wherein the Tracker Server program sends the Tracker Client program an instruction refusing permission to execute the Software Payload.

29. The method of claim 21 wherein initially the Current Token of each electronically-distributable Software Payload includes as the unique component an empty Base Serial Number field and an empty Key field;

when the Tracker Client program first communicates the Current Token to the Tracker Server program, the Tracker Server program recognizes the empty Base Serial Number field and the empty Key field and advances to step (g) wherein the Tracker Server program places a distinctive Base Serial Number in the Base Serial Number field and creates a unique Key and placing the unique Key in the Key field of the Current Token to form the new Current Token, and the new Current Token is returned to the Tracker Client program with permission to execute the Software Payload;

the Tracker Server program also stores the new Current Token including the distinctive Base Serial Number and the created Key in the Tracker Server database; and

thereafter whenever the Tracker Server program receives a Current Token with a Serial Number and a Key that match the stored distinctive Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client program along with permission to execute the Software Payload.

30. The method of claim 21 wherein in step (a) the Current Token further includes a Base Serial Number in an unchangeable Base Serial Number field.

31. The method of claim 21 wherein the the electronically-deliverable Software Payloads along with the Tracker Client program and Current Token are created by a strict duplication method which makes only identical copies in batches with all copies in each batch having a common batch Base Serial Number, and wherein initially the Current Token of each electronically-deliverable software in the batch includes a Base Serial Number field with the common Base Serial Number therein and an empty Key field;

when the Tracker Client program first communicates the Current Token of each one of the distributable computer-readable media to the Tracker Server program, the Tracker Server program searches the Tracker Server database to confirm that the common Base Serial Number is authorized, and the Tracker Server program changes the component of the Current Token by creating a unique Key and placing the Key in the Key field of the Current Token to form the new Current Token;

the Tracker Server program also stores the new Current Token including the common Base Serial Number and the created Key; and

thereafter when the Tracker Server program receives a Current Token with a Base Serial Number and Key that match the stored common Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client along with permission to execute the Software Payload.

32. The method of claim 21 wherein the Current Token comprises a plurality of fields including Key, Copy and Usage represented by:

space="preserve" listing-type="equation">Key;

00-Copy;

0-Usage;

0

in which;

the Usage field tracks the number of times the Tracker Client program is used,

the Key is formed of unique characters created by the Tracker Server program for the Current Token and is also stored in the Tracker Server database, and functions to validate uses of the Current Token subsequent to the first time the Tracker Client program and Tracker Server program communicate, wherein if the Tracker Client program presents an invalid Key to the Tracker Server program (i) the Tracker Server program will reject the invalid Key and inform the Tracker Client program to disallow usage of the Software Payload if the Tracker Server program is programmed for unauthorized copy-rejection, or (ii) the Copy field is used to count the number of unauthorized copies if the Tracker Server program is programmed to permit access to the Software Payload by an unauthorized copy; and

the Copy field is initially set by the Tracker Server program, and contains the number of unauthorized copies known by the Tracker Server program if the Tracker Server program permits use of unauthorized copies.

33. The method of claim 32 wherein the Current Token further includes a Base Serial Number which comprises a plurality of fields including Customer number, Batch number, Sequence number and Check digits represented by:

space="preserve" listing-type="equation">customer;

W-batch;

X-sequence;

Y-check;

Z;

wherein W, X, Y and Z are numbers; and

wherein abbreviations and compression are optionally used.

34. The method of claim 21 wherein the Software Payload is a software program and/or electronic data.

35. The method of claim 21 wherein a list of authorized Base Serial Numbers is stored in the Tracker Server database, and wherein the Base Serial Number of each incoming Current Token is compared with this list and if not found therein the Current Token is considered invalid.

36. A system for copy-tracking distributed software programs over a computer network after the programs are distributed to users comprising:

a plurality of electronically-distributable Software Payloads encoded with a Tracker Client program and a Current Token readable by the Tracker Client program and including a Key field and a Usage field;

a central computer in the network, the central computer having installed thereon a Tracker Server program including a database for storing Current Tokens received from the Tracker Client programs;

a plurality of user computers connectable to the network, each one of the user computers having operatively associated therewith one of the encoded computer-readable media;

a plurality of means each including one of the user computers for executing the Tracker Client program on the encoded medium operatively associated therewith;

(a) to access the Tracker Server program on the central computer via computer-to-computer communications over the network;

(b) to read the Current Token on the encoded medium operatively associated therewith and to send the Current Token to the Tracker Server program; and

(c) to execute the Software Payload whenever the Tracker Client program receives an indication from the Tracker Server program to permit execution of the Software Payload; and

means including the central computer for executing the Tracker Server program;

(d) to validate each Current Token sent thereto; and

if the Current Token is invalid the Tracker Server program is executed to request a re-send or to inform the Tracker Client program to prevent access to the Software Payload;

(e) if the Tracker Server program validates the Current Token in step (d) and the Usage field is set to zero to indicate that the Tracker Client program is initially communicating with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (2) to store at least the Key of the new Current Token in the Tracker Server database, (3) to set the Usage field to one, and (4) to indicate to the Tracker Client program to permit execution of the Software Payload;

or

(f) if the Tracker Server program validates the Current Token in step (d) and the Usage field is set to greater than zero to indicate that the Tracker Client program has previously communicated with the Tracker Server program, the Tracker Server program is executed by the central computer (1) to determine whether the Key in the Key field matches a Key in the Tracker Server database, and if there is a match, (2) to return a new Current Token with a new Key in the Key field to the Tracker Client program for use when the Tracker Client program next accesses the Tracker Server program, (3) to store at least the Key of the new Current Token in the Tracker Server database, (4) to increment the Usage field by one, and (5) to indicate to the Tracker Client program to permit execution of the Software Payload; and

if in (1) above the Key in the Key field does not match a Key in the Tracker Server database, optionally informing the Tracker Client program to prevent access to the Software Payload.

37. The system of claim 36 wherein initially the Current Token of each electronically-distributable Software Payload includes a Base Serial Number field with a Base Serial Number therein and an empty Key field;

when the Tracker Client program first communicates the Current Token to the Tracker Server program, the central computer executes the Tracker Server program to search the Tracker Server database to confirm that the Base Serial Number has not been previously received, and the Tracker Server program creates a unique Key and places the Key in the Key field of the Current Token to form the new Current Token;

the Tracker Server program also stores the new Current Token including the Base Serial Number and the created Key in the Tracker Server database; and

thereafter when the Tracker Server program receives a Current Token with a Base Serial Number and Key that match the stored Base Serial Number and the created Key, the Tracker Server program creates a new Key and stores the new key in the Tracker Server database, and returns a new Current Token with the new Key to the Tracker Client along with permission to execute the Software Payload;

or

thereafter when the Tracker Server program receives a Current Token having a Base Serial Number and a Key from a Tracker Client, and the Key does not match the Key associated with the Base Serial Number stored in the Tracker Server database, then an unauthorized copy has been detected, and optionally the Tracker Server program sends the Tracker Client program an instruction refusing permission to execute the Software Payload.

38. A electronically-distributable Software Payload for use in a system for copy-tracking electronically-distributable Software Payloads over a computer network after the programs are distributed to users comprising:

the electronically-distributable Software Payload having encoded thereon (i) a Software Payload to be tracked, (ii) a Tracker Client program and (iii) a Current Token readable by the Tracker Client program, said Current Token including a key field and a usage field;

the Tracker Client program being computer executable to interact with a remote Tracker Server program executable by a central computer on the network for copy-tracking the distributed medium, the Tracker Server program maintaining a database of Current Tokens received from the Tracker Client (TC) program and other TC programs that are executable by computers on the network, the database being used for validating Current Tokens received from the TC programs;

the electronically-distributable Software Payload being encoded with the following computer executable Tracker Client program instructions;

(a) to access the Tracker Server program on the central computer via computer-to-computer communications over the network;

(b) to read the Current Token on the computer-readable medium and to send the Current Token to the Tracker Server program;

(c) when the Tracker Server program validates the Current Token for execution of the electronically-distributable Software Payload, to store a new Current Token received from the Tracker Server program for use when the Tracker Client program next accesses the Tracker Server program, the new Current Token including a new Key in the Key field and an incremental increase in the Usage field; and

(d) to execute the electronically-distributable Software Payload whenever the Tracker Client program receives an authorization from the Tracker Server program for execution of the Software Payload, or to deny access to the Software Payload whenever the Tracker Client program receives an instruction from the Tracker Server program refusing permission to execute the Software Payload.

39. The electronically-distributable software Payload of claim 38 wherein initially the Current Token of each electronically-distributable Software Payload includes a Base Serial Number field with a Base Serial Number therein.