Method and system for prevention of piracy of a given software application via a communications network

• US 20060179486A1
• Filed: 12/19/2005
• Published: 08/10/2006
• Est. Priority Date: 06/14/2000
• Status: Abandoned Application

• Current Assignee: Reuben Bahar
• Original Assignee: Reuben Bahar
• Inventors: Bahar, Reuben
• Application Number:
  US11/311,964
• Publication Number:
  US 20060179486A1
• Time in Patent Office: Days
• US Class Current: 726/26
• CPC Class Codes: G06F 21/121 Restricting unauthorised execution of programs
• CPC Class Codes: G06T 2201/0064 for copy protection or copy management, e.g. CGMS, copy only once, one-time copy
• CPC Class Codes: H04L 2209/605 Copy protection

Abstract

A method and system for preventing piracy of a given software application which makes use of a communications network, such as the Internet. A given software application, when initially installed on a user system, is non-functional until activated by a remote service provider. The user must provide the remote service provider with user data, such as the user'"'"'s personal identity information and the unique software identification code relating to the specific software. User data is compared to archived data to determine if the user is a pirator of the software. If the user is not a pirator, then the remote service provider transmits service data, such as an activation code, to the user system. Once activated, the software becomes fully operational, and the user is allowed complete access to its functions.

Claims

1. A method of preventing piracy of a given software application comprising the steps of:

assigning a unique identification code to each authentic copy of such software application;

installing the software application in a data storage element on a user'"'"'s computer;

configuring the software application to require service data to activate at least part of its functionality;

requiring the user to communicate user data to a remote service provider, the user data being derived, at least in part, from the identifying data that identifies the user, and being derived, at least in part, from the unique identification code;

archiving identifying data received from a user for each unique identification code if no such identifying data has previously been archived for such unique identification code;

comparing received identifying data associated with a unique identification code with previously archived identifying data corresponding to the same unique identification code if such identifying data has previously been archived;

selectively transmitting service data to the user'"'"'s computer when no such identifying data has previously been archived for such unique identification code;

selectively transmitting service data to the user'"'"'s computer when the received identifying data is consistent with previously archived data for the same unique identification code; and

receiving the transmitted service data within the data storage element of the user'"'"'s computer to activate at least part of the functionality of the software application.

2. The method recited by claim 1 wherein said step of selectively transmitting service data to the user'"'"'s computer when the received identifying data is consistent with previously archived data for the same unique identification code includes the steps of:

a. determining the number of times that said service data has been requested; and

b. refusing transmission of said service data when the number of times that said service data has been requested exceeds a predetermined threshold.

3. The method recited by claim 1 including the steps of:

a. determining the number of times that received identifying data is not consistent with previously archived data for the same unique identification code; and

b. refusing transmission of said service data when the number of times that received identifying data is not consistent with previously archived data for the same unique identification code exceeds a predetermined threshold.

4. The method recited by claim 1 further including the step of archiving identifying data received from a user for each unique identification code subsequent to an initial archiving of identifying data pertaining to the same unique identification code.

5. The method recited by claim 1 wherein said received service data is stored within the data storage element of the user'"'"'s computer.

6. The method recited by claim 1 wherein said user data includes product information relating to said software application installed on the user'"'"'s computer.

7. The method recited by claim 1 wherein said service data is maintained in a data storage element of the remote service provider.

8. The method recited by claim 7 wherein said service data comprises at least one program code sequence that activates at least part of the functionality of said software application installed on the user'"'"'s computer.

9. The method recited by claim 7 wherein said service data includes at least one program code sequence that results in a promotional message that may be displayed to said user on the user'"'"'s computer.

10. The method recited by claim 1 wherein said service data is derived at least in part from said communicated user data.

11. The method recited by claim 1 wherein said service data is transferred by said remote service provider without human intervention and received by the user'"'"'s computer.

12. The method recited by claim 1 said service data is manually transferred from said remote service provider to the user'"'"'s computer.

13. The method recited by claim 1 wherein said service data is made available to the user from said remote service provider, the user being able to download said service data into said user'"'"'s computer.

14. The method recited by claim 1 wherein said software application includes a program code sequence that identifies said software application installed on the user'"'"'s computer, said software application additionally being responsive to a second program code sequence that activates at least part of the functionality of said software application, and which is transmitted to the user'"'"'s computer.

15. A method of preventing piracy of a given software application comprising the steps of:

assigning a unique identification code to each authentic copy of such software application;

installing the software application in a data storage element on a user'"'"'s computer;

configuring the software application to require service data to activate at least part of its functionality;

requiring the user to communicate user data to a service provider, the user data being derived, at least in part, from the identifying data that identifies the user, and being derived, at least in part, from the unique identification code;

archiving identifying data received from a user for each unique identification code if no such identifying data has previously been archived for such unique identification code;

comparing received identifying data associated with a unique identification code with previously archived identifying data corresponding to the same unique identification code if such identifying data has previously been archived, and if so, determining whether such previously archived data is consistent with newly-received identifying data for the same unique identification code.

16. The method recited by claim 15 further including the step of communicating service data to the user to activate at least part of the said software'"'"'s functionality.

17. The method recited by claim 16, wherein said communicated service data is stored within the data storage element of the user'"'"'s computer.

18. The method recited by claim 16 wherein said step of communicating service data to the user further includes the steps of:

a. determining the number of times that said service data has been requested; and

b. refusing transmission of said service data when the number of times that said service data has been requested exceeds a predetermined threshold.

19. The method recited by claim 15 further including the step of archiving identifying data received from a user for each unique identification code subsequent to an initial archiving of identifying data pertaining to the same unique identification code.

20. The method recited by claim 15 wherein said user data includes product information relating to said software application installed on the user'"'"'s computer.

21. The method recited by claim 16 wherein said service data is maintained in a data storage element of said service provider.

22. The method recited by claim 16 wherein said service data comprises at least one program code sequence that activates at least part of the functionality of said software application installed on the user'"'"'s computer.

23. The method recited by claim 16 wherein said service data includes at least one program code sequence that results in a promotional message that may be displayed to said user on the user'"'"'s computer.

24. The method recited by claim 16 wherein said service data is derived at least in part from said communicated user data.

25. The method recited by claim 16 wherein said service data is transferred by said service provider without human intervention and received by the user'"'"'s computer.

26. The method recited by claim 16 wherein said service data is manually transferred from said service provider to the user'"'"'s computer.

27. The method recited by claim 16 wherein said service data is made available to the user from said service provider, the user being able to download said service data into the user'"'"'s computer.

28. The method recited by claim 15 wherein said software application includes a program code sequence that identifies said software application installed on said data storage element of the user'"'"'s computer, said software application additionally being responsive to a second program code sequence that activates at least part of the functionality of said software application.

29. A method of preventing piracy of a given software application comprising the steps of:

assigning a unique identification code to each authentic copy of such software application;

installing the software application in a data storage element on a user'"'"'s computer;

configuring the software application to require service data to activate at least part of its functionality;

requiring the user to communicate user data to a service provider, the user data being derived, at least in part, from the identifying data that identifies the user, and being derived, at least in part, from the unique identification code;

comparing received identifying data associated with a unique identification code with previously archived identifying data corresponding to the same unique identification code if such identifying data has previously been archived;

selectively communicating service data to the user when the received identifying data is consistent with previously archived data for the same unique identification code; and

receiving the communicated service data wherein said service data is used to activate at least part of the functionality of the software.

30. The method recited by claim 29 wherein said step of selectively communicating service data to the user when the received identifying data is consistent with previously archived data for the same unique identification code includes the steps of:

a. determining the number of times that said service data has been requested; and

b. refusing communication of said service data when the number of times that said service data has been requested exceeds a predetermined threshold.

31. The method recited by claim 29 including the steps of:

a. determining the number of times that received identifying data is not consistent with previously archived data for the same unique identification code; and

b. refusing communication of said service data when the number of times that received identifying data is not consistent with previously archived data for the same unique identification code exceeds a predetermined threshold.

32. The method recited by claim 29 further including the step of archiving identifying data received from a user for each unique identification code.

33. The method recited by claim 29 wherein said received service data is stored within the data storage element of the user'"'"'s computer.

34. The method recited by claim 29 wherein said service data comprises at least one program code sequence that activates at least part of the functionality of said software application installed on said data storage element of the user'"'"'s computer.

35. A system for preventing piracy of a given software application, said software application having a unique identification code associated therewith, and said software application requiring service data to activate at least part of the functionality of said software application, said system comprising:

a user computer system on which a user desires to operate the software application, said user system being connected to a communications network to transmit user data and to receive said service data, said user data being derived at least in part from identifying data which identifies the user, and being derived at least in part from said unique identification code;

a remote service computer system connected to said communications network to receive user data transmitted over the communications network from the user computer system, said remote service computer system configured to performing the following steps;

archiving identifying data received from a user for each unique identification code if no such identifying data has previously been archived for such unique identification code;

comparing received identifying data associated with a unique identification code with previously archived identifying data corresponding to the same unique identification code if such identifying data has previously been archived;

selectively transmitting service data to the user'"'"'s computer system when no such identifying data has previously been archived for such unique identification code;

selectively transmitting service data to the user'"'"'s computer system when it is determined that the received identifying data is consistent with previously archived data for the same unique identification code.

36. The system as in claim 35 wherein said service data is maintained by said remote service computer system in a data storage element used to archive said service data.

37. The system as in claim 35 wherein said service data consists, at least in part, of an activation code sequence to activate at least part of the functionality of the software application.

38. The system as in claim 35 wherein said service data is transferred by said remote service computer system without human intervention and received by said user computer system.

39. The system as in claim 35 wherein said service data is manually transferred from said remote service computer system to said user computer system.

40. The system as in claim 35 wherein said service data is made available to said user from said remote service system, said user being able to download said service data into said user computer system.

41. The system as in claim 35 wherein said software application includes a program code sequence that identifies said software application stored on said user computer system, said software application additionally being responsive to a second program code sequence that activates at least part of the functionality of said software application.

42. The system as recited in claim 35 wherein said service data includes at least one program code sequence that results in a promotional message that may be displayed to said user on said user computer system.

43. The system as recited in claim 35 wherein said service data is received by the data storage element of the user computer system to activate at least part of the functionality of said software application.

44. A method of preventing piracy of a given software application comprising the steps of:

assigning a unique identification code to each authentic copy of such software application;

installing the software application in a data storage element on a user'"'"'s computer;

configuring the software application to require service data to activate at least part of its functionality;

requiring the user to communicate user data to a service provider, the user data being derived, at least in part, from the identifying data that identifies the user, and being derived, at least in part, from the unique identification code;

archiving identifying data received from a user for each unique identification code if no such identifying data has previously been archived for such unique identification code;

comparing received identifying data associated with a unique identification code with previously archived identifying data corresponding to the same unique identification code if such identifying data has previously been archived;

selectively communicating service data to the user when no such identifying data has previously been archived for such unique identification code;

selectively communicating service data to the user when the received identifying data is consistent with previously archived data for the same unique identification code.

45. The method recited by claim 44 wherein said service data is received by said user to activate at least part of the functionality of said software application.

46. The method recited by claim 44 wherein said service data comprises at least one program code sequence that activates at least part of the functionality of said software application installed on the user'"'"'s computer.

47. The method recited by claim 44 further including the step of archiving identifying data received from a user for each unique identification code subsequent to an initial archiving of identifying data pertaining to the same unique identification code.

48. The method recited by claim 44 wherein said step of selectively communicating service data to the user when the received identifying data is consistent with previously archived data for the same unique identification code includes the steps of:

a. determining the number of times that said service data has been requested; and

b. refusing communication of said service data when the number of times that said service data has been requested exceeds a predetermined threshold.

49. The method recited by claim 44 including the steps of:

a. determining the number of times that received identifying data is not consistent with previously archived data for the same unique identification code; and

b. refusing communication of said service data when the number of times that received identifying data is not consistent with previously archived data for the same unique identification code exceeds a predetermined threshold.

50. The method recited by claim 44 wherein said received service data is stored within the data storage element of the user'"'"'s computer.

51. The method recited by claim 44 wherein said user data includes product information relating to said software application installed on the user'"'"'s computer.

52. The method recited by claim 44 wherein said service data is maintained in a data storage element of the service provider.

53. The method recited by claim 44 wherein said service data includes at least one program code sequence that results in a promotional message that may be displayed to said user on the user'"'"'s computer.

54. The method recited by claim 44 wherein said service data is derived at least in part from said communicated user data.

55. The method recited by claim 44 wherein said software application includes a program code sequence that identifies said software application installed on the user'"'"'s computer, said software application additionally being responsive to a second program code sequence that activates at least part of the functionality of said software application.