KR101390677B1 - Method of managing copies of embedded software, and computer-readable recording medium with copy-management program for the same - Google Patents

Abstract

The present invention relates to a technology for managing replication of embedded software. More particularly, the present invention relates to a technology for managing the number of copies of software (embedded software) mounted on an embedded device and preventing illegal copying and use of these embedded software. According to the present invention, illegal duplication and use can be prevented by managing the number of duplication of the embedded software installed in the embedded terminal and allowing duplication only by a preset limit value, and by managing the number of duplication of the embedded software, It is not necessary to change the hardware configuration of the embedded terminal in order to apply the replication management technology according to the present invention and thus the manufacturing process can be used as it is. According to the present invention, there is an advantage that security is very strong by forming a copy management structure by utilizing a personal identification module (for example, a SIM card) in which an illegal modification is extremely difficult.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention [0001] The present invention relates to a method and apparatus for managing a copy of embedded software, and a copy management program for the same. 2. Description of the Related Art [0002]

The present invention relates to a technology for managing replication of embedded software. More particularly, the present invention relates to a technology for managing the number of copies of software (embedded software) mounted on an embedded device and preventing illegal copying and use of these embedded software.

With the development of the technology, most of the electronic devices are conventionally equipped with a microprocessor, an operating system for driving these microprocessors, and application software for performing various service operations. An operating system and application software for driving a microprocessor mounted on an electronic device are called 'embedded software', and devices incorporating such embedded software are called 'embedded terminals'.

These embedded terminals are used in various places and there are many kinds of them. For example, there are a variety of terminal devices including televisions, computers, refrigerators, air conditioners, PMPs, MP3 players, personal digital assistants (PDA), smart phones, smart pads, set- Is used in a great many fields such as airplanes and satellites.

Meanwhile, the embedded software installed in the embedded terminal is provided in a binary form. Embedded software, which is provided in binary form, can be installed and run on hardware of similar platforms without any restrictions. Software developers who supply embedded software should make royalties a business model. For efficient royalties, it is important to manage the duplication of embedded software and to know the number of copies.

Accordingly, in the related technology field, there is a desperate need for a technology that can reliably manage the reproduction of the embedded software.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and it is an object of the present invention to provide a technique for managing replication of embedded software. More specifically, it is an object of the present invention to provide a technology for managing the number of times of copying of software (embedded software) mounted on an embedded device and for preventing unauthorized copying and use of these embedded software.

A method for managing a copy of embedded software according to the present invention includes: a first step in which an embedded terminal executes a copy management process for a specific embedded software; A second step in which the embedded terminal identifies previously stored certificates and hardware specific information; A third step of the embedded terminal checking whether a pre-stored certificate for the embedded software is valid; A fourth step of allowing the embedded terminal to validate the certificate if the pre-stored certificate exists as a result of the checking, and if the verification of the certificate is successful, ending the copy management process while allowing the embedded software; A fifth step of, if the pre-stored certificate does not exist as a result of the checking, requesting a certificate while the embedded terminal provides hardware-specific information to the personal identification module; If the personal identification module newly generates and provides a certificate based on hardware specific information at a preset copying limit value limit, the embedded terminal receives and stores the generated new certificate, and terminates the copy management process while allowing the embedded software step; And a seventh step of the embedded terminal terminating the replication management process while failing the embedded software if the personal identification module reaches the copy threshold value and provides the certificate generation rejection.

At this time, the method for managing replication of embedded software according to the present invention is characterized in that the signature generation device, which is executed before the first step, includes signature basic information including at least one of a version of embedded software, ; The signature generation device generating a signature using the signature base information; Wherein the signature generating device obtains a key combination of a public key and a private key; Providing a signature and a public key to an embedded terminal; And providing the signature generation device with a copy limit value and a private key to the personal identification module.

In a fourth step of the present invention, the embedded terminal decrypts the certificate with the public key to verify whether the certificate is generated or not, (B) comparing the hardware specific information reflected in the certificate with the hardware specific information identified in the second step, and verifying whether the certificate is generated for the embedded terminal; And if the verification in the forty-first step and the verification in the forty-second step are successful, the embedded terminal permits the embedded software and terminates the copy management process.

The sixth step of the present invention may further include the steps of: checking whether the personal identification module checks the copy threshold value to check whether additional copy is permitted; Generating a certificate based on the hardware-specific information provided by the personal identification module when additional checking is permitted as a result of the checking; The personal identification module reflecting the new generation of the certificate in the management of the copy threshold value; Encrypting the newly generated certificate by the personal identification module with the private key and providing the encrypted certificate to the embedded terminal; Receiving and storing a newly generated certificate by the embedded terminal; Verifying the newly generated certificate with the public key of the embedded terminal and verifying whether the certificate is generated with respect to the embedded terminal by comparing the hardware unique information reflected in the certificate with the hardware unique information identified in the second step; And terminating the copy management process while permitting the embedded terminal to allow the embedded software when all of the verification is successful.

In addition, the present invention provides a method of managing a certificate, comprising the steps of: maintaining a certificate generation history corresponding to a new certificate generated in the sixth step, and providing a certificate generation history to the certificate reissue server; An eighth step in which the certificate reissue server collects a certificate generation history by the personal identification module; A ninth step of requesting reissue of the certificate while providing hardware specific information to the certificate reissue server upon detecting deletion or corruption of the stored certificate by the embedded terminal; A step 10 in which the certificate reissue server inquires of the certificate generation history about the hardware specific information provided by the certificate reissue server; And if the inquiry result is successful, the certificate reissue server reissues the certificate based on the hardware specific information and provides the reissued certificate to the embedded terminal.

In addition, in the fifth step of the present invention, the embedded terminal further provides a signature to the personal identification module. When the personal identification module, which is executed between the fifth and sixth steps, receives the signature, the embedded terminal checks an error of the signature, And if the error is detected, rejecting the certificate generation and terminating the copy management process while the embedded terminal fails the embedded software. The hardware specific information may include at least one of a modem chip serial number, a memory serial number, a Bluetooth medium access control (MAC) address, a WIFI MAC address, and an International Mobile Terminal Identification Number (IMEI) of the embedded terminal .

Meanwhile, a computer readable recording medium according to the present invention records a duplication management program for executing a duplication management method of the above-described embedded software.

According to the present invention, there is an advantage that illegal duplication and use can be prevented by managing the number of duplication of the embedded software installed in the embedded terminal and allowing duplication only by a preset threshold value.

Also, according to the present invention, there is an advantage that the royalty collection of the embedded software can be ensured by managing the copying frequency of the embedded software installed in the embedded terminal.

Also, since the hardware configuration of the embedded terminal does not need to be changed in order to apply the replication management technology according to the present invention, the manufacturing process can be used as it is, which is advantageous in that the manufacturer does not need to add the cost.

According to the present invention, there is an advantage that security is very strong by forming a copy management structure by utilizing a personal identification module (for example, a SIM card) in which an illegal modification is extremely difficult.

1 is a view for explaining a concept of a copy protection system according to the present invention,
2 is an internal block diagram of a signature generating apparatus according to the present invention,
3 is a flowchart illustrating the generation of security environment data for preventing copying of embedded software in the signature generation apparatus according to the present invention,
4 is a diagram illustrating internal block configurations and interrelationships between an embedded terminal and an individual identification module according to the present invention;
5 is a flowchart showing a security management process performed in an embedded terminal and a personal identification module according to the present invention;
FIG. 6 is a flowchart illustrating a certificate reissue process performed in an embedded terminal and a reissue server according to the present invention. FIG.

Hereinafter, the present invention will be described in detail with reference to the drawings.

1, a copy protection system according to the present invention includes a signature generation device 10, an embedded terminal 20, A personal identification module 30, and a certificate reissue server 40. [

The signature generating apparatus 10 may be configured as a personal computer, and a dedicated terminal may be used according to an embodiment. The signature generating apparatus 10 generates a signature to be mounted on the embedded terminal 20 and generates a public key for use in communication between the embedded terminal 20 and the personal identification module 30 and a certificate, ), And sets the copy limit value which is the maximum copy tolerance value of the embedded software. The signature generation device 10 provides a signature and a public key to the embedded terminal 20 and a private key and a copy threshold value to the personal identification module 30. [

The embedded terminal 20 can be implemented in the form of various terminal devices including a smart phone, which is an electronic device equipped with embedded software in which copy management according to the present invention is carried out. A certificate manager for managing embedded software is installed in the embedded terminal 20. The certificate manager checks whether a valid certificate is stored for installation and operation of the embedded software and if not, It is requested and provided. At this time, management of the number of times of copying of the embedded software is realized by the personal identification module 30.

A concrete operation of the embedded terminal 20 and a certificate manager installed in the embedded terminal 20 according to the present invention will be described later in detail with reference to the drawings. 1, a smart phone is exemplified as the embedded terminal 20, but any embedded terminal capable of having the personal identification module 30 in addition to the smart phone may be used. Hereinafter, for convenience of description, the embedded terminal 20 will be described as a smart phone.

The personal identification module 30 may be implemented as a card module implemented by an integrated circuit (IC), which is a SIM card called a Subscriber Identification Module, for managing replication of embedded software according to the present invention . In addition, a Universal Subscriber Identity Module (USIM) used in the GSM system may be used.

The personal identification module 30 according to the present invention is provided with a private key and a copy limit value from the signature generation device 10 in order to manage copying of the embedded software. Generates a certificate that can be used exclusively for the embedded terminal 20 using the information, and provides the generated certificate to the embedded terminal 20 again. At this time, the personal identification module 30 controls the number of generated certificates so as not to exceed the copying limit value of the embedded software. The personal identification module 30 encrypts the certificate with the private key, and provides the certificate to the embedded terminal 20.

The certificate reissue server 40 reissues the certificate to the embedded terminal 20. After the embedded terminal 20 receives the certificate for the first time from the personal identification module 30 and installs and sells the software, when the user performs various kinds of repair processes such as repair service of the after-use service of the embedded terminal 20, device breakage, The certificate can be deleted or corrupted due to the cause. If there is no certificate, the software can not operate. Therefore, the certificate must be regenerated and provided to the embedded terminal 20. At this time, a certificate is generated for the embedded terminal 20 in the hands of the general user through the personal identification module 30 Since it is difficult or undesirable in reality, it is provided to the network through the certificate reissue server 40. [

That is, the certificate reissue server 40 generates a certificate through the personal identification module 30 and reissues the certificate only for the provided embedded terminal 20. The certificate reissue server 40 collects the certificate generation history through the collection of the personal identification module 30 and receives the certificate reissue request from the embedded terminal 20 to inquire the certificate generation history and determine whether to reissue the certificate.

When the personal identification module 30 generates the certificate for the first time and provides the generated certificate to the embedded terminal 20 in relation to the method of collecting the certificate generation history, the embedded terminal 20 provides the certificate generation information to the certificate reissue server 40 . However, it is safer that the personal identification module 30 manages the certificate creation history internally and provides it to the certificate reissue server 40.

2 is an internal block diagram of a signature generation apparatus 10 for implementing a replication management technique according to the present invention. 2, a signature generating apparatus 10 according to the present invention includes a user UI unit 101, a control unit 103, a signature generating unit 105, an external device interface unit 107, a graphics processing unit 109 ).

The user UI unit 101 is a component for receiving an operation input from a user, which is composed of a mouse, a keyboard, a touch screen, a touch pen, and the like. The graphic processing unit 109 receives an operation process To a monitor as a still image or a moving image.

1, the external device interface unit 107 performs an interface between data transmitted and received by the signature generation device 10 via the network with the embedded terminal 20 and the personal identification device 30. [ The external device interface unit 107 may also interface with other external devices.

The signature generation unit 105 can be implemented in the form of a software module on various recording media. The signature generation unit 105 is a component that provides data defining a security environment for implementing the replication management technology according to the present invention. The signature generation unit 105 generates a signature 105a and a public key 105b and a copy threshold value 105c and a private key 105d. The signature generation unit 10 generates a signature 105a, a public key 105b, And provides the copy threshold value 105c and the private key 105d to the certificate generation unit 305 of the personal identification device 30. [

First, the signature 105a is used for a consistency check or the like in the certificate management unit 205 and the certificate generation unit 305 to be described later. For example, the signature 105a includes a version of the embedded software module, a distribution target manufacturer and a product model, (Digital signature) value obtained by collecting data such as the digital signature 105c. The public key 105b and the private key 105d are security related key combinations used for communication (encryption / decryption) related to certificate transmission / reception between the embedded terminal 20 and the personal identification device 30. [ Finally, the copy threshold value 105c is a value relating to the maximum number of copies (replications) allowed for the embedded software in question.

3 is a control flowchart for generating and transmitting security environment data for preventing duplication of embedded software in the signature generation apparatus 10 for implementing the replication management technology according to the present invention.

First, the signature generating apparatus 10 proceeds to step S200 to acquire basic information for generating a signature. The signature basic information can include information stored in advance in association with the embedded software and information input by the operator through the user UI unit 101. For example, the version of the embedded software, the manufacturer and model of the distribution target, the copy threshold value 105c ) Can be considered.

In order to achieve the object of the present invention, the copy limit value 105c is already set in advance for the embedded software. The copy threshold value 105c is the maximum copy tolerance value to be limited by one personal identification module 30, and is appropriately set by the software developer.

The signature generating apparatus 10 generates the signature 105a using these signature basic information in step S202. A concrete method of generating a digital signature from various basic information is a well-known technology in the security-related field, and a description thereof will be omitted in this specification.

In step S204, the signature generation apparatus 10 acquires a key combination composed of the public key 105b and the private key 105d. Here, the public key 105b and the private key 105d may utilize a key combination provided by an external key management authority or may be generated by itself. However, the present invention does not specifically limit the type of the key combination .

The signature generating apparatus 10 provides the signature 105a and the public key 105b to the embedded terminal 20 in step S206 and transmits the copy threshold value 105c and the private key 105d to the embedded terminal 20 in step S208. To the module (30). In the present invention, steps S206 and S208 may be performed simultaneously or may be reversed.

The signature 105a and the public key 105b are provided to the embedded terminal 20 and the copy threshold 105c and the private key 105d are provided to the personal identification module 30 according to the present invention Management of copy management (i.e., copying) for embedded software is performed. The detailed procedure will be described later with reference to FIGS. 4 and 5. FIG.

4 is a diagram illustrating internal block configurations and interrelationships of the embedded terminal 20 and the individual identification module 30 according to the present invention. 4, the embedded terminal 20 to which the present invention is applied includes a touch input unit 201, a terminal control unit 203, a certificate management unit 205, a display unit 207, a hardware information management unit 209, The personal identification module 30 includes a certificate generation unit 305, a terminal connection unit 313, and a generation history storage unit 314. The certificate generation unit 305 generates a certificate,

First, the internal configuration of the embedded terminal 20 will be described.

The touch input unit 201 detects a touch operation of the user, converts the touch operation into a user input signal, and provides the user input signal to the terminal control unit 203.

The terminal control unit 203 performs a general control operation related to the terminal device, and performs operations necessary for installation, authentication, operation, and copy management of the embedded software according to the present invention. This will be described in more detail with reference to the flow chart of FIG.

The certificate managing unit 205 manages various data necessary for the operation of the embedded terminal 20. Specifically, the signature managing unit 205 receives and manages the signature 105a and the public key 105b from the signature generating unit 10. [

The display unit 207 is configured in the form of an LCD or an LED and displays the state of the embedded terminal 20 in a process necessary for the operation of the embedded terminal 20 and a standby state under the control of the terminal control unit 203.

The hardware information management unit 209 is a component for managing hardware specific information of the embedded terminal 20. The hardware information management unit 209 includes a modem chip serial number, a memory serial number, a Bluetooth media access control (MAC) address, a WIFI A MAC address, and an International Mobile Equipment Identity (IMEI). The hardware information management unit 209 provides the hardware specific information to the terminal control unit 203 and the certificate management unit 205.

The terminal storage unit 211 is a component that provides a storage space for the embedded terminal 20 and provides a space for storing the signature 105a and the public key 105b in connection with the present invention, Stores the certificate provided by the identification module 30, and provides the certificate to the certificate management unit 205 when necessary.

The identification module connection unit 213 interfaces data transmitted and received between the personal identification module 30 and the terminal control unit 203. The data transmitted and received between the terminal control unit 203 and the individual identification module 30 may be certificate information according to the present invention, response information corresponding to a certificate request and a copy request, and the like. A more detailed description thereof will be made with reference to the flowcharts to be described later.

Next, the internal configuration of the personal identification module 30 will be described.

The certificate generation unit 305 is a component that generates and provides a certificate in response to a request of the embedded terminal 20. [ The certificate generating unit 305 first checks the copy threshold value before generating the certificate to determine whether to further permit copying (copy) with respect to the embedded software, and if the copy is permitted to the maximum allowed If copying (replication) is no longer allowed, the certificate creation is denied. On the other hand, if it is acceptable, the certificate generating unit 305 generates the certificate reflecting the hardware specific information of the embedded terminal 20 and provides the generated certificate to the embedded terminal 20. At this time, it is preferable to encrypt and transmit it with the private key 105d.

The terminal connection unit 313 performs various data transmission and reception between the embedded terminal 20 and the personal identification module 30 as a component for interfacing with the identification module connection unit 213 of the above-

The generation history storage unit 314 stores the certificate generation history generated by the personal identification module 30 and provided to the embedded terminal 20. The certificate generation history stores information that identifies the embedded terminal 20, that is, hardware specific information of the embedded terminal 20 together. The certificate generation history is provided to the certificate reissue server 40 and utilized for determining whether to reissue the certificate, which will be described later in detail with reference to FIG.

5 is a flowchart illustrating a replication management process performed in the embedded terminal 20 and the personal identification module 30 according to the present invention. The process of FIG. 5 may be executed when the embedded software is run, copied, or installed in the embedded terminal 20, and may be performed when the embedded terminal 20 is booted after the embedded software is installed have. The present invention is not limited to the point in time at which the copy management process of the embedded software is executed but will be described on the basis of execution of the copy management process when the embedded software is executed in the embedded terminal 20.

First, when the embedded software is activated in the embedded terminal 20, the terminal control unit 203 of the embedded terminal 20 identifies whether the stored certificate exists in the terminal storage unit 211 through the certificate management unit 205 in step S300 , And identifies the hardware specific information through the hardware information management unit (209). The hardware specific information includes information such as a modem chip serial number, a memory serial number, a Bluetooth medium access control (MAC) address, a WIFI MAC address, an international mobile terminal identification number (IMEI) And may be included in the hardware specific information if they indicate the inherent attributes of the embedded terminal 20.

Then, the certificate management unit 205 of the embedded terminal 20 checks whether there is a valid certificate in the embedded terminal 20 for the embedded software that is attempted to run in step S302. If there is a valid certificate, the terminal control unit 203 of the embedded terminal 20 proceeds to step S330, and if there is no valid certificate, the terminal control unit 203 proceeds to step S304. In this case, the 'valid certificate' in step S302 means that there is no problem of data breaking when the field format such as the certificate header is checked as a certificate usable for the embedded software, and there is no reason for disqualification such as the expiration of the validity period.

First, if there is no valid certificate in the embedded terminal 20, the embedded terminal 20 requests the personal identification module 30 to issue a certificate for driving the embedded software in step S304. At this time, the embedded terminal 20 provides the signature 105a and the hardware specific information to the personal identification module 30, thereby ensuring the integrity of the copy management system, and at the same time, generating a certificate for the embedded terminal 20 do.

Upon receipt of the certificate request, the personal identification module 30 first checks whether there is an error in the signature 105a received from the embedded terminal 20 in step S306. If there is an error in the signature 105a, the flow advances to step S320 to reject the certificate creation for the embedded terminal 20, and the embedded terminal 20 displays an error in step S322 and terminates.

On the other hand, if there is no error in the signature 105a as a result of the check, the process proceeds to step S308 to check the copy threshold value. That is, the copying threshold value 105c, which is the maximum copy permission value, is set for the embedded software, which is set by the signature generating apparatus 10 and managed by the certificate generating unit 305 of the personal identification module 30 . The personal identification module 30 checks the copy threshold value 105c to determine whether it should allow additional copying (copying) with respect to the embedded software. If the maximum copy tolerance value has been reached, the personal identification module 30 proceeds to step S320 The embedded terminal 20 rejects the certificate creation for the embedded terminal 20, and the embedded terminal 20 displays an error in step S322 and terminates the process.

On the other hand, if the maximum copy tolerance value is not reached (the copy limit value is equal to 0), the personal identification module 30 generates a certificate using the hardware unique information of the embedded terminal 20 in step S310, 105d to encrypt the certificate. When the certificate is generated as described above, the personal identification module 30 stores the certificate generation history for the generated certificate in step S312.

The personal identification module 30 then reduces the copy threshold value 105c and provides a certificate to the embedded terminal 20 in step S314.

As to the management of the copy threshold value 105c, it is reduced by one for each generated certificate for the embedded software, and when the value becomes 0, the copy limit value is reached and it is treated as being no longer permitted. For example, assuming that the copy threshold value 105c is determined as 300, the copy threshold value 105c is decremented by 1 until it reaches 0 each time the certificate is provided according to the request of the embedded terminal 20. [ Thus, all 300 certificates can be generated.

In the above description, it is assumed that a method of reducing the copy threshold value 105c by one is used. In another implementation, it may be implemented by checking whether the copy threshold value 105c is the same value as the copy threshold value 105c, without increasing the copy threshold value 105c, but increasing the number of separately provided copy counters by one. That is, in the present invention, it should be noted that either of the methods of reducing the copy threshold value 105c or putting the copy counter may be used.

When the certificate is transmitted from the personal identification module 30, the terminal control unit 203 of the embedded terminal 20 receives the certificate through the identification module connection unit 213 and stores the received certificate in the terminal storage unit 211 in step S316.

If the valid certificate is confirmed in step S302 or the certificate is provided in step S316, the embedded terminal 20 proceeds to step S330 to verify the certificate. That is, it is determined whether there is a problem by decrypting the certificate using the public key 105b, and the hardware specific information reflected in the certificate is compared with the hardware specific information provided by the hardware information management unit 209, (20). ≪ / RTI >

As a result of the verification, if the verification in step S330 fails, the embedded terminal 20 proceeds to step S322 and displays an error and terminates the process. In this case, it is generally considered that the certificate is transferred from another terminal device.

On the other hand, if the verification in step S330 is successful, the embedded terminal 20 proceeds to step S334 and normally operates the embedded software.

According to the above process, in order to drive specific embedded software in the embedded terminal 20, a certificate generated for the embedded terminal 20 must be provided inside. If there is no certificate, the certificate is received from the personal identification module 30. At this time, since the copy limit value 105c is managed by decrementing the copy limit value 105c one by one, copying of the embedded software is performed within the maximum copy tolerance value set by the signature generation device 10 Replication) can be controlled.

In addition, when the personal identification module 30 generates a certificate reflecting the hardware specific information of the embedded terminal 20 and the embedded terminal 20 checks whether the hardware unique information matches when verifying the certificate, It is also possible to effectively prevent copying and use of the device.

When manufacturing the embedded terminal 20 using the personal identification module 30 having the copy threshold value 105c, the number of embedded terminals that can be manufactured per individual identification module 30 is limited, The user can easily grasp the usage of the embedded software.

6 is a flowchart illustrating a certificate reissue process performed in the embedded terminal 20 and the certificate reissue server 40 according to the present invention. When the certificate is deleted or damaged, the embedded terminal 20 requests the certificate reissue server 40 to reissue the certificate. When the certificate reissue server 40 confirms the history of issuing the certificate through the personal identification module 30 Reissue the certificate.

First, the certificate reissue server 40 collects the generation history of the certificate (S400). The certificate generation history is managed by the personal identification module 30 as described above with reference to FIG. 4 and FIG. 5, and is transmitted to the certificate reissue server 40. However, it should be understood that other types of implementations are also possible.

After step S400, the embedded terminal 20 detects deletion or corruption of the stored certificate, and requests the certificate reissue server 40 to reissue the certificate. At this time, the embedded terminal 20 transmits the signature 105a and the hardware specific information together with the certificate re-issuance request message. The signature 105a is for verifying that the certificate re-issuance request is a normal message according to the present invention. The hardware specific information is used for verifying that the embedded terminal 20 has a history of normally generating the certificate through the personal identification module 30 .

Upon receiving the certificate reissue request, the certificate reissue server 40 checks whether there is an error in the signature 105a in step S404. If there is an error in the signature 105a, it is determined that there is a problem, and the process proceeds to step S414 to reject the certificate re-issuance and ends.

On the other hand, if there is no error in the signature 105a, the process proceeds to step S406, where the certificate reissue server 40 inquires of the certificate creation history about the hardware specific information. The certificate reissue server 40 determines whether the embedded terminal 20 requesting the reissue of the certificate has a history of normally generating the certificate through the personal identification module 30.

Then, the certificate reissue server 40 examines the result of inquiring the certificate generation history in step S408. If the query fails, it is determined that there is no certificate generation history through the individual identification module 30, And the certificate re-issuance is denied.

On the contrary, if the inquiry is successful, it is determined that the embedded terminal 20 has a history of normally generating the certificate through the personal identification module 30, and accordingly, in step S410, the certificate re- And transmits the re-issued certificate to the embedded terminal 20 by encrypting the re-issued certificate with the private key 105d. At this time, the re-issued certificate may be configured in the same format as that of the certificate originally generated by the individual identification module 30, or may be configured in a different format so as to identify the re-issued certificate.

Finally, in step S412, the embedded terminal 20 receives the re-issued certificate and stores it in the terminal storage unit 211. [

Meanwhile, in the present invention, the personal identification module 30 can generate a certificate the number of times corresponding to a specific copy threshold value (e.g., 100), and the embedded terminal 20 can only generate a personal identification module 30) is required. The personal identification module 30 is inserted into a plurality of terminal devices in the manufacturing process of the embedded terminal 20 and intervenes only in the certificate generation process, and is removed. In the process, the certificate generation history is stored and provided to the certificate reissue server 40. The embedded terminal 20 receives the certificate from the personal identification module 30 for the first time, and receives the re-issued certificate from the certificate re-issuance server 40 when it is required to receive the certificate again due to deletion or corruption of the certificate.

However, the technical idea of the present invention is not limited to the above-described first embodiment, but may be implemented in different ways. For example, in the second embodiment, the personal identification module 30 may be configured to generate only one certificate, and the certificate reissue server 40 may be inserted into the individual identification module 30 so as to be integrally formed. However, the inventor of the present invention has determined that the first embodiment is a more preferable method than the second embodiment in consideration of the production efficiency and the production cost of the embedded terminal 20 and the personal identification module 30, .

The present invention can also be embodied in the form of computer readable code on a computer readable recording medium. At this time, the computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored.

Examples of the computer-readable recording medium include a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage, and the like, and may be implemented in the form of a carrier wave . The computer-readable recording medium can also be stored and executed by a computer-readable code in a distributed manner on a networked computer system. And functional programs, codes, and code segments for implementing the present invention can be easily deduced by programmers skilled in the art to which the present invention belongs.

As described above, the embodiments of the present invention have been disclosed in the present specification and drawings, and although specific terms have been used, they have been used only in a general sense to easily describe the technical contents of the present invention and to facilitate understanding of the invention. And is not intended to limit the scope of the invention. It will be apparent to those skilled in the art that other modifications based on the technical idea of the present invention are possible in addition to the embodiments disclosed herein.

10: Signature Generator
20: embedded terminal
30: Personal identification module
40: Certificate reissue server
101: User UI section
103:
105: Signature generator
107: External device interface unit
109: Graphics processor
201: Touch input unit
203:
205: certificate management unit
207:
209: hardware information management unit
211:
213: Identification module connection
305: Certificate generating unit
313:
314: Creation history storage unit

Claims (9)

A first step of the embedded terminal executing a duplication management process for the specific embedded software;
A second step in which the embedded terminal identifies previously stored certificates and hardware specific information;
A third step of the embedded terminal checking whether a pre-stored certificate for the embedded software is valid;
A fourth step of, if the pre-stored certificate is valid as a result of the checking, if the embedded terminal verifies the certificate and if the verification of the certificate succeeds, then the embedded software is permitted and the copy management process is terminated;
A fifth step of, if the pre-stored certificate does not exist as a result of the checking, requesting a certificate while the embedded terminal provides the hardware specific information to the personal identification module;
Wherein the personal identification module newly generates and provides a certificate based on the hardware specific information at a predetermined copying limit value limit so that the embedded terminal can receive and store the generated new certificate and perform the copy management process while allowing the embedded software A sixth step of terminating the process;
A seventh step of the embedded terminal terminating the copy management process while failing to process the embedded software when the personal identification module reaches the copy threshold and provides a certificate generation rejection;
The method comprising the steps of:
The method according to claim 1,
A second step of executing,
The signature generation device acquiring signature base information including at least one of a version of the embedded software, a distribution target manufacturer and a product model, and a copy threshold value;
The signature generation device generating a signature using the signature basis information;
The signature generation device obtaining a key combination of a public key and a private key;
The signature generation device providing the signature and the public key to the embedded terminal;
The signature generation device providing the copy threshold and the private key to the person identification module;
The method comprising the steps of:
The method of claim 2,
In the fourth step,
(41) the embedded terminal decrypts the certificate with the public key and verifies whether or not an error has occurred;
Comparing the hardware specific information reflected in the certificate with the hardware specific information identified in the second step and verifying whether the certificate is generated for the embedded terminal;
43. The method of claim 43, wherein if the verification of step 41 and the verification of step 42 are successful, the embedded terminal permits the embedded software and ends the replication management process.
And a copy management program for managing the copy of the embedded software.
The method of claim 3,
In the sixth step,
The personal identification module checking the copy threshold to check whether additional copying is allowed;
Generating a certificate based on the provided hardware-specific information when the check result indicates that additional copying is permitted;
The personal identification module reflecting the new generation of the certificate in the management of the copy threshold value;
Encrypting the newly generated certificate with the private key and providing the newly generated certificate to the embedded terminal;
Receiving and storing the newly generated certificate by the embedded terminal;
The embedded terminal verifies the newly generated certificate with the public key and verifies whether the certificate is generated for the embedded terminal by comparing the hardware unique information reflected in the certificate with the hardware unique information identified in the second step ;
Ending the copy management process while permitting the embedded terminal to allow the embedded software if the verification is successful;
And a copy management program for managing the copy of the embedded software.
The method of claim 4,
An eighth step of the certificate reissue server collecting the certificate generation history by the personal identification module;
A ninth step of requesting reissue of the certificate while providing the hardware specific information to the certificate reissue server upon detecting deletion or corruption of the certificate newly created and stored in the sixth step;
A step 10 in which the certificate reissue server inquires of the certificate generation history about the provided hardware specific information;
If the inquiry result is successful, the certificate reissue server reissues the certificate based on the hardware specific information and provides the reissued certificate to the embedded terminal;
The method comprising the steps of:
The method of claim 5,
The method of claim 1,
Each time a new certificate is generated in the sixth step, the personal identification module maintains a certificate generation history corresponding to the new certificate and provides the certificate generation history to the certificate reissue server;
The method comprising the steps of:
The method of claim 6,
In the fifth step, the embedded terminal further provides the signature to the personal identification module,
And a fourth step of executing, between the fifth step and the sixth step,
When the personal identification module receives the signature, it checks an error of the signature. If an error is detected as a result, the embedded terminal rejects the certificate generation, and the embedded terminal terminates the replication management process while failing the embedded software step;
The method comprising the steps of:
The method of claim 7,
The hardware specific information may include at least one of a modem serial number, a memory serial number, a Bluetooth media access control (MAC) address, a WIFI MAC address, and an International Mobile Terminal Identification Number (IMEI) of the embedded terminal Wherein the method comprises the steps of:
A computer-readable recording medium storing a replication management program for executing a replication management method of embedded software according to any one of claims 1 to 8.

Images