US5699512A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Software analysis protection method for changing the software pattern on the memory of a user terminal
Assignee: NTT Inc
•
Filing: 1995-04-28
•
Granted: 1997-12-16
•
Expires: 2015-04-28
Abstract
Abstract A software analysis protection method capable of preventing an illegitimate use of a software reliably, by making a software analysis difficult without complicating or enciphering the software itself. Software parts dividing the software to be used at the user terminal are distributedly stored in the user terminal and the center, and the software parts stored in the center are transmitted to the user terminal and loaded into missing parts among the software parts stored in the user terminal on a memory so as to make the software operable at the user terminal. Then, the software as developed on the memory is operated at the user terminal. The software parts are down-loaded from the center to the user terminal such that an arranged pattern of the software as developed on the memory is changed at each time of a use of the software at the user terminal.
Inventors
- 👤 Kenji Moriyasu
- 👤 Atsusi Kanai
- 👤 Nobuhisa Miyake
- 👤 Atsusi Terauchi
- 👤 Hironobu Okuyama
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-10-28 05:52
CPC Classifications
G; G06; G06F; G06F21/00; G06F21/10; G06F21/12; G06F21/14
Claims Analysis
Total Claims: 21
Claim 1
Independent Claim
257 words
A software analysis protection method for protecting a software to be used at a user terminal from being analyzed at the user terminal in a system formed by a center and a plurality of user terminals connected with the center, comprising the steps of: distributedly storing software parts dividing the software to be used at the user terminal in the user terminal and the center; requesting the software parts stored in the center from the user terminal at each time of a use of the software at the user terminal; transmitting the software parts stored in the center to the user terminal in response to a request from the user terminal and loading the software parts transmitted from the center into missing parts among the software parts stored in the user terminal on a memory so as to make the software operable at the user terminal while changing an arranged pattern of the software as developed on the memory at each time of a use of the software at the user terminal; and operating the software as developed on the memory at the user terminals; wherein the software parts stores in the center include a plurality of sets of software parts with an identical function, and the center selects one set of software parts for a transmission from the center to the user terminal according to a random number, such that the arranged pattern of the software as developed on the memory is changed at each time of a use of the software at the user terminal.
Claim 2
Dependent Claim
257 words
A software analysis protection method for protecting a software to be used at a user terminal from being analyzed at the user terminal in a system formed by a center and a plurality of user terminals connected with the center, comprising the steps of: distributedly storing software parts dividing the software to be used at the user terminal in the user terminal and the center; requesting the software parts stored in the center from the user terminal at each time of a use of the software at the user terminal; transmitting the software parts stored in the center to the user terminal in response to a request from the user terminal and loading the software parts transmitted from the center into missing parts among the software parts stored in the user terminal on a memory so as to make the software operable at the user terminal while changing an arranged pattern of the software as developed on the memory at each time of a use of the software at the user terminal; and operating the software as developed on the memory at the user terminals; wherein the software parts stores in the center include a plurality of sets of software parts with an identical function, and the center selects one set of software parts for a transmission from the center to the user terminal according to a random number, such that the arranged pattern of the software as developed on the memory is changed at each time of a use of the software at the user terminal.
Claim 3
Dependent Claim
99 words
The software analysis protection method of claim 1, wherein the software parts stored in the center include more than one group of software parts for different functions of the software including a plurality of sets of software parts for each function of the software, and the center selects one set of software parts in one group of software parts for a transmission from the center to the user terminal according to one of the request from the user terminal or a judgment at the center, such that a function of the software operated at the user terminal is changed.
Claim 4
Dependent Claim
74 words
The software analysis protection method of claim 1, wherein the software parts stored in the center include a plurality of sets of software parts, the center selects one set of software parts for a transmission from the center to the user terminal, and the software becomes at least partially operable when said one set of software parts transmitted from the center are loaded into a corresponding set of the missing parts on the memory.
Claim 5
Dependent Claim
35 words
The software analysis protection method of claim 3, wherein the center sequentially transmits said plurality of sets of software parts in response to requests from the user terminal as an operation of the software progresses.
Claim 6
Dependent Claim
34 words
The software analysis protection method of claim 1, wherein the software parts loaded into the missing parts are cleared from the memory after a use of the software at the user terminal is finished.
Claim 7
Dependent Claim
46 words
The software analysis protection method of claim 1, wherein the software parts loaded into the missing parts are sequentially cleared from the memory during an operation of the software, as the software parts loaded into the missing parts become unnecessary for subsequent operation of the software.
Claim 8
Dependent Claim
35 words
The software analysis protection method of claim 1, wherein the software parts loaded into the missing parts are cleared from the memory by a command provided in the software parts stored in the user terminal.
Claim 9
Dependent Claim
40 words
The software analysis protection method of claim 1, wherein the software parts loaded into the missing parts are cleared from the memory by a command provided in the software parts stored in the center and loaded into the missing parts.
Claim 10
Dependent Claim
91 words
The software analysis protection method of claim 1, wherein each software part stored in the center has a known maximum number of times for use of said each software part and a count of number of times for actual use of said each software part, and said each software part which is loaded into the missing part is cleared from the memory whenever said count of number of times for actual use of said each software part reaches to said maximum number of times for use of said each software part.
Claim 11
Dependent Claim
26 words
The software analysis protection method of claim 1, wherein the software parts stored in the user terminal are a plurality of non-consecutive blocks in the software.
Claim 12
Dependent Claim
47 words
The software analysis protection method of claim 1, wherein the software parts stored in the center are a plurality of non-consecutive blocks in the software, and the non-consecutive blocks of the software parts stored in the center are transmitted in an non-sequential order among the non-consecutive blocks.
Claim 13
Dependent Claim
213 words
The software analysis protection method of claim 1, wherein each software part stored in the center has a first code at a prescribed address within said each software part, the first code having a function for returning a fixed value indicating that it is a software part stored in the center when said each software part is checked at the user terminal, each missing part on the memory in the user terminal has a second code at a prescribed address within said each missing part, the second code having a function for returning another fixed value indicating that it is a missing part when said each missing part is checked at the user, and the method further comprises the steps of: checking a value returned from the first code or the second code provided in each part of the software as developed on the memory while operating the software at the user terminal, so as to judge whether each part of the software is a software part loaded into a missing part or a remaining missing part; and interrupting an operation of the software whenever said another fixed value is returned from one part of the software as developed on the memory in a course of operating the software at the user terminal.
Claim 14
Dependent Claim
197 words
A software analysis protection method for protecting a software to be used at a user terminal from being analyzed at the user terminal in a system formed by a center and a plurality of user terminals connected with the center, comprising the steps of: distributedly storing software parts dividing the software to be used at the user terminal in the user terminal and the center; transmitting the software parts stored in the center to the user terminal and loading the software parts transmitted from the center into missing parts among the software parts stored in the user terminal on a memory so as to make the software operable at the user terminal; and operating the software as developed on the memory at the user terminal; wherein the software parts stored in the center include a plurality of sets of software parts with an identical function, and the center selects one set of software parts for a transmission from the center to the user terminal according to a random number, such that an arranged pattern of the software as developed on the memory is changed at each time of a use of the software at the user terminal.
Claim 15
Dependent Claim
197 words
A software analysis protection method for protecting a software to be used at a user terminal from being analyzed at the user terminal in a system formed by a center and a plurality of user terminals connected with the center, comprising the steps of: distributedly storing software parts dividing the software to be used at the user terminal in the user terminal and the center; transmitting the software parts stored in the center to the user terminal and loading the software parts transmitted from the center into missing parts among the software parts stored in the user terminal on a memory so as to make the software operable at the user terminal; and operating the software as developed on the memory at the user terminal; wherein the software parts stored in the center include a plurality of sets of software parts with an identical function, and the center selects one set of software parts for a transmission from the center to the user terminal according to a random number, such that an arranged pattern of the software as developed on the memory is changed at each time of a use of the software at the user terminal.
Claim 16
Dependent Claim
44 words
The software analysis protection method of claim 13, wherein the software parts stored in the center are transmitted to the user terminal in response to a request from the user terminal at each time of a use of the software at the user terminal.
Claim 17
Dependent Claim
26 words
The software analysis protection method of claim 13, wherein the software parts stored in the center are transmitted as a plurality of blocks in the software.
Claim 18
Dependent Claim
35 words
The software analysis protection method of claim 13, wherein an arranged pattern of the software as developed on the memory is changed at each time of a use of the software at the user terminal.
Claim 19
Dependent Claim
74 words
The software analysis protection method of claim 13, wherein the software parts stored in the center include a plurality of sets of software parts, the center selects one set of software parts for a transmission from the center to the user terminal, and the software becomes at least partially operable when said one set of software parts transmitted from the center are loaded into a corresponding set of the missing parts on the memory.
Claim 20
Dependent Claim
34 words
The software analysis protection method of claim 13, wherein the software parts loaded into the missing parts are cleared from the memory after a use of the software at the user terminal is finished.
Claim 21
Dependent Claim
46 words
The software analysis protection method of claim 13, wherein the software parts loaded into the missing parts are sequentially cleared from the memory during an operation of the software, as the software parts loaded into the missing parts become unnecessary for subsequent operation of the software.
References Cited (Backward Citations)
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2000-12-15 | 2001-06-16 | 2001-12-16 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2004-12-15 | 2005-06-16 | 2005-12-16 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2008-12-15 | 2009-06-16 | 2009-12-16 | $7700.00 | Window Closed / Lapsed |