SDK use-restriction imposing device, use-restriction-imposed SDK developing system, and SDK use-restriction imposing method

1. An SDK use-restriction imposing device comprising:

a processor;

a user interface unit;

a source file of a use-restriction plug-in;

a use-restriction plug-in edit unit configured to set use restrictions to the source file on the basis of use-restriction information received via the user interface unit;

a build unit configured to compile the source file so as to generate an executable file of the use-restriction plug-in in response to a build instruction received via the user interface unit; and

a use-restriction plug-in generation unit configured to generate a use-restriction-imposed SDK including an original SDK and the executable file of the use-restriction plug-in in response to an output instruction received via the user interface unit, wherein the original SDK includes a plug-in core module configured to, upon start-up, query the use-restriction plug-in and continue or terminate execution in accordance with a response from the use-restriction plug-in.

2. The SDK use-restriction imposing device according to claim 1 , wherein the use-restriction information includes a use permission period counted from a start-of-use date.

3. The SDK use-restriction imposing device according to claim 2 , wherein:

when start-of-use information indicates a “before start-of-use” value, the use-restriction plug-in is configured to (i) determine a period that is obtained by adding the use permission period to a current date and set the result as a use deadline, (ii) set the start-of-use information to an “after start-of-use” value, and (iii) set use permission information to a “use permitted” value when the current date does not exceed the use deadline,

when the start-of-use information indicates the “after start-of-use” value, the use-restriction plug-in is configured to set the use permission information to the “use permitted” value when the current date does not exceed the use deadline, and

the use-restriction plug-in is configured to send the core module the use permission information as the response.

4. The SDK use-restriction imposing device according to claim 3 , wherein when the current date exceeds the use deadline, the use-restriction plug-in is configured to (i) set end-of-use information to an “after end-of-use” value and (ii) cause the core module to terminate the execution.

5. The SDK use-restriction imposing device according to claim 4 , wherein the start-of-use information and the end-of-use information are stored in a non-volatile storage unit outside of the core module and outside of the use-restriction plug-in.

6. The SDK use-restriction imposing device according to claim 1 , further comprising a key generation unit,

wherein the key generation unit is configured to generate a secret key and a public key.

7. The SDK use-restriction imposing device according to claim 6 , wherein the use-restriction plug-in generation unit is configured to encrypt a hash value of the executable file of the use-restriction plug-in with the secret key and generates a digital signature.

8. The SDK use-restriction imposing device according to claim 7 , wherein the use-restriction plug-in generation unit includes the digital signature and a public key token corresponding to the public key in an assembly manifest and generates a use-restriction plug-in assembly including the assembly manifest.

9. A use-restriction-imposed SDK developing system comprising:

a processor;

an original SDK development support device configured to support development of an original SDK; and

an SDK use-restriction imposing device,

wherein the SDK use-restriction imposing device includes:

a user interface unit;

a source file of a use-restriction plug-in;

a use-restriction plug-in edit unit configured to set use restrictions to the source file on the basis of use-restriction information received via the user interface unit;

a build unit configured to compile the source file so as to generate an executable file of the use-restriction plug-in in response to a build instruction received via the user interface unit; and

a use-restriction plug-in generation unit configured to generate a use-restriction-imposed SDK including an original SDK and the executable file of the use-restriction plug-in in response to an output instruction received via the user interface unit, and

wherein the original SDK includes a plug-in core module configured to, upon start-up, query the use-restriction plug-in and continue or terminate execution in accordance with a response from the use-restriction plug-in.

10. The use-restriction-imposed SDK developing system according to claim 9 , wherein the use-restriction information includes a use permission period counted from a start-of-use date.

11. The use-restriction-imposed SDK developing system according to claim 10 , wherein:

when start-of-use information indicates a “before start-of-use” value, the use-restriction plug-in is configured to (i) determine a period that is obtained by adding the use permission period to a current date and set the result as a use deadline, (ii) set the start-of-use information to an “after start-of-use” value, and (iii) set use permission information to a “use permitted” value when the current date does not exceed the use deadline,

when the start-of-use information indicates the “after start-of-use” value, the use-restriction plug-in is configured to set the use permission information to the “use permitted” value when the current date does not exceed the use deadline, and

the use-restriction plug-in is configured to send the core module the use permission information as the response.

12. The use-restriction-imposed SDK developing system according to claim 11 , wherein when the current date exceeds the use deadline, the use-restriction plug-in is configured to (i) set end-of-use information to an “after end-of-use” value and (ii) cause the core module to terminate the execution.

13. The use-restriction-imposed SDK developing system according to claim 12 , wherein the start-of-use information and the end-of-use information are stored in a non-volatile storage unit outside of the core module and outside of the use-restriction plug-in.

14. The use-restriction-imposed SDK developing system according to claim 9 , wherein the SDK use-restriction imposing device further includes a key generation unit, and

wherein the key generation unit is configured to generate a secret key and a public key.

15. The use-restriction-imposed SDK developing system according to claim 14 , wherein the use-restriction plug-in generation unit is configured to encrypt a hash value of the executable file of the use-restriction plug-in with the secret key and generates a digital signature.

16. A computer-implemented SDK use-restriction imposing method via an SDK use-restriction imposing device comprising:

setting use restrictions to a source file of a use-restriction plug-in on the basis of use-restriction information via a use-restriction plug-in edit unit;

compiling the source file and generating an executable file of the use-restriction plug-in via a build unit; and

generating a use-restriction-imposed SDK including an original SDK and the executable file of the use-restriction plug-in via a use-restriction plug-in generation unit, wherein the original SDK includes a plug-in core module configured to, upon start-up, query the use-restriction plug-in and continue or terminate execution in accordance with a response from the use-restriction plug-in.

17. The SDK use-restriction imposing method according to claim 16 ; further comprising:

generating a secret key and a public key via a key generation unit.

18. The SDK use-restriction imposing method according to claim 17 , further comprising:

encrypting a hash value of the executable file of the use-restriction plug-in with the secret key and generating a digital signature via the use-restriction plug-in generation unit.

19. The SDK use-restriction imposing method according to claim 18 , further comprising:

including the digital signature and a public key token corresponding to the public key in an assembly manifest and generating a use-restriction plug-in assembly including the assembly manifest via the use-restriction plug-in generation unit.