KR20000038662A - Method for detecting equipment duplication by using count in case of adopting smart card in mobile communication - Google Patents

Abstract

1. TECHNICAL FIELD OF THE INVENTION

The present invention relates to a terminal duplication detection method using a call history count when adopting a smart card in a mobile communication.

2. The technical problem to be solved by the invention

An object of the present invention is to provide a terminal duplication detection method for detecting terminal duplication using a call history count when a smart card is adopted in a mobile communication.

3. Summary of the Solution of the Invention

The present invention includes storing terminal identification information (ESN), setting a call history count (COUNT) to a predetermined value, receiving a random number, and transmitting an authentication response generation request message; Generating an authentication response as an input of a hash function to the subscriber identification information MIN stored by the card, a random number from the terminal, and an ESN, and transmitting the generated authentication response to the terminal; Transmitting an authentication request message including an MIN and an authentication response of the card and an ESN, a COUNT value, and a random number stored in the terminal; And confirming the relationship between the MIN and the ESN, the authentication request type, and transmitting an authentication response, and confirming the authentication response and transmitting a COUNT value increasing command to the card.

4. Important uses of the invention

The present invention is used to detect terminal duplication in mobile communication.

Description

Terminal duplication detection method using call history count when adopting smart card in mobile communication

The present invention relates to a method for detecting terminal duplication using a call history count when a smart card is adopted in a mobile communication, and a computer-readable recording medium having recorded thereon a program for realizing the same.

Mobile communication has a serious illegal use of services due to the characteristics of wireless. In particular, the most frequent security breach in mobile communication is due to terminal duplication. Terminal replication refers to extracting legitimate subscriber identification information and injecting it into another terminal for use. To block this abuse, the IS-41C, a specification for North American digital cellular systems, uses authentication. Authentication is a method in which a mobile communication network confirms that both a terminal and a mobile communication network have the same key (A-key) and algorithm, and that the service is a legitimate subscriber.

1 is an explanatory diagram of a terminal authentication in a conventional mobile communication network.

As shown in the figure, the subscriber station 1-1 and the public mobile communication network 1-2 have the same subscriber authentication secret keys A-key 1-3 and A- immediately after joining, before the authentication procedure is performed. The key '(1-4) is distributed and stored in a secure and secure manner, and the same temporary secret key, SSD (1-5) and SSD' (1) through a shared secret data (SSD) update procedure. -6) Save.

After that, when the terminal 1-1 connects to the public mobile communication network 1-2, an authentication response is performed using the random number 1-7, the SSD, and other parameters sent by the mobile communication network 1-2. (AUTHR: AUTHentication Response) is generated and sent to the mobile communication network (1-2) (1-8). The mobile communication network 1-2 calculates an authentication response through the same generation process using the corresponding terminal-related information stored therein and checks whether it is the same as the authentication response sent by the terminal. At this time, it is checked whether the parameters COUNT, which are the parameters related to the call history sent by the terminal, are equal to each other compared with COUNT stored in the mobile communication network. In the two comparison processes, if the calculation results of the terminal and the mobile communication network are the same, authentication is successful.

In the IS-41C certification, if the certification is successful, a series of services are provided. If the certification fails, a series of management procedures determined by the network operator are performed to select the cause of the certification failure. Reasons for authentication failure in IS-41C certification include AUTHR mismatch and COUNT mismatch.

2 is a flowchart of a conventional terminal duplication detection method.

As shown in the figure, when a mobile communication network receives an authentication request from a terminal in a standby state (2-1) to provide a service (2-2), it is determined whether the authentication parameters match (2-3). If there is a match, the authentication success is notified (2-4) .If the authentication parameters do not match, the authentication response (AUTHR) mismatch or call history count (COUNT) mismatch is checked (2-5). The process is performed (2-6), and if the call history count mismatch, the call history count mismatch process is performed (2-7).

Ideal mobile communication provides subscribers with both personal and terminal mobility. Terminal mobility is a service that can be provided to an individual by carrying a specific terminal and moving to any area. Personal mobility is the ability for unique individuals to identify and provide services from any device in any region. Currently, North American mobile standards do not, but GSM, the European standard, uses smart cards. have.

A smart card is a device equipped with a processing unit and a memory, and physically complies with the ISO-7816 standard. In mobile communication, smart cards are used to secure key distribution for security, and smart cards are used to provide personal mobility. IS-41 and IS-95 systems do not use smart cards, but are being considered for their advantages.

When a smart card is used, a problem arises in which of parameters stored in an existing terminal are stored in the smart card and which is stored in the terminal. The parameter used to perform the authentication function may lose the original purpose of the parameter depending on whether it is stored in the smart card or the terminal. In particular, COUNT, the call history count, seems to be lost because the use of smart cards reduces the possibility of illegal terminal duplication, which was originally intended. However, even if smart card duplication is technically impossible, duplication of terminals is still possible. If the terminal can be duplicated, a terminal identification number (ESN) can be obtained, and the service can be provided using another smart card. However, at this time, it may be regarded as not interested because the charging is made from the operator's point of view, but the terminal replication is a major concern from the terminal manufacturer's point of view or the terminal loaner formed later. Therefore, detecting terminal duplication is also an important issue when using smart cards. In order to manage a terminal separately from a smart card, the European GSM uses a terminal identification device (EIR).

Therefore, conventional smart card operation method exists in GSM in Europe, but this does not take into account the call history count has a problem that can not be applied to the terminal duplication detection using the call history count when the smart card is adopted.

Therefore, the present invention has been made to solve the above problems, the terminal duplication detection method for detecting terminal duplication using the call history count when the smart card is adopted in the mobile communication and a program for realizing the program to read the computer The purpose is to provide a recording medium that can be used.

1 is an explanatory diagram of terminal authentication in a conventional mobile communication network.

2 is a flowchart of a conventional terminal duplication detection method.

3 to 5 are flowcharts illustrating an exemplary embodiment of a terminal duplication detection method using a call history count when a smart card is adopted according to the present invention.

6 to 8 are flowcharts illustrating an embodiment of a terminal duplication detection method using a call history count when a smart card is adopted according to the present invention.

9 is an explanatory diagram of a subscriber profile in an authentication center applied to the present invention.

10 and 11 are flowcharts of a third embodiment of a method for detecting a terminal duplication using a call history count when adopting a smart card according to the present invention.

12 and 13 are flowcharts illustrating a fact example of a method for detecting a terminal duplication using a call history count when a smart card is adopted according to the present invention.

* Explanation of symbols for the main parts of the drawings

301, 601: smart card 302, 602: terminal

303, 603: Certification Center

In accordance with another aspect of the present invention, a terminal duplication detection method applied to a mobile communication network includes a terminal storing terminal identification information, setting a call history count to a predetermined value, and receiving a random number from an authentication center. A first step of transmitting an authentication response generation request message together with the terminal identification information; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information, shared secret data stored in the smart card, and a random number and terminal identification information from the terminal, and the authentication response and subscriber generated by the smart card. Transmitting identification information to the terminal in response to an authentication response generation request; Transmitting, by the terminal, an authentication request message including subscriber identification information and authentication response from the smart card, terminal identification information, call history count value, and random number stored therein to the authentication center; And when the authentication center confirms the relationship between the subscriber identification information and the terminal identification information, confirms the authentication request type, and transmits the authentication response to the terminal, the terminal confirms the authentication response and instructs the smart card to increase the call history count value. The fourth step of transmitting.

In addition, the present invention is a mobile communication network having a large processor, the terminal stores the terminal identification information, set the call history count to a predetermined value, and receives a random number from the authentication center to the smart card with the terminal identification information authentication response A first function of sending a creation request message; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information, shared secret data stored in the smart card, and a random number and terminal identification information from the terminal, and the authentication response and subscriber generated by the smart card. A second function of transmitting identification information to the terminal in response to an authentication response generation request; A third function of sending, by the terminal, an authentication request message including subscriber identification information and authentication response from the smart card, terminal identification information, call history count value and random number stored therein to the authentication center; And when the authentication center confirms the relationship between the subscriber identification information and the terminal identification information, confirms the authentication request type, and transmits the authentication response to the terminal, the terminal confirms the authentication response and instructs the smart card to increase the call history count value. A computer readable recording medium having recorded thereon a program for realizing a fourth function of transmitting the data is provided.

In addition, the present invention is a terminal duplication detection method applied to a mobile communication network, the terminal stores the terminal identification information, set the call history count to a predetermined value, the authentication response generation request command including the call history count and the terminal identification information Transmitting a smart card to a smart card; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information and shared secret data stored in the smart card, call history count and terminal identification information from the terminal, and the generated authentication response and subscriber identification information. Transmitting a message to the terminal in response to an authentication response generation request; And when the terminal transmits an authentication request message including subscriber identification information and authentication response from the smart card and terminal identification information and call history count value stored therein to the authentication center, the authentication center generates an authentication response. And a third step of checking an authentication request type to increase a call history count value and sending an authentication response to the terminal.

In addition, the present invention provides a smart card to a mobile communication network having a high-capacity processor, the terminal stores the terminal identification information, set the call history count to a predetermined value, the authentication response generation request command including the call history count and terminal identification information A first function of transmitting to; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information and shared secret data stored in the smart card, call history count and terminal identification information from the terminal, and the generated authentication response and subscriber identification information. A second function of transmitting a message to the terminal in response to an authentication response generation request; And when the terminal transmits an authentication request message including subscriber identification information and authentication response from the smart card and terminal identification information and call history count value stored therein to the authentication center, the authentication center generates an authentication response. The present invention provides a computer-readable recording medium having recorded thereon a program for realizing a third function of confirming an authentication request type, increasing a call history count value, and transmitting an authentication response to the terminal.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

3 to 5 are flowcharts illustrating an embodiment of a method for detecting a terminal duplication using a call history count when adopting a smart card according to the present invention.

First, the smart card stores a subscriber identification number (MIN), a subscriber secret key (A-key), shared secret data (SSD: shared secret data), a hash function (authentication algorithm), and a call history count (COUNT). It is the same as the smart card used by GSM except COUNT.

3 shows a process in which authentication is performed between the smart card 301, the terminal 302, and the network (authentication center) 303 when the smart card is adopted in the system conforming to IS-41C and IS-95.

As shown in the figure, when the smart card 301 contacts the terminal 302 (3-1) and power is supplied to the terminal 302 (3-2), the terminal device (including the smart card and the terminal) ) Starts the operation.

Thereafter, the terminal 302 receives the random number (RAND) 3-3 provided by the network and transmits an authentication response generation request command with its ESN to the smart card 301 (3-4). 301 generates an authentication response (AUTHR) from the SSD generated using the stored A-key, MIN, A-key, RAND and ESN sent by the terminal as input of the hash function (3-5).

Thereafter, the smart card transmits the generated AUTHR and the COUNT, MIN and RAND stored therein to the terminal in response to the authentication response generation request (3-6), and the terminal includes the MIN, ESN, AUTHR and COUNT values. Send an authentication request message to the network (3-7).

4 shows a process in which a network (authentication center) receives and processes an authentication request message.

As shown in the figure, the authentication center receives an authentication request message from the terminal (4-1) and generates an authentication response (AUTHR) with MIN, ESN, SSD and RAND as input (4-2), It is determined whether AUTHR and AUTHR generated by the authentication center match (403), and if it matches, it is checked whether the COUNT stored in the terminal and the COUNT from the terminal match (4-4). Card Detach "(4-5), if the authentication request type is not" Card Detech ", the subscriber's own COUNT value is increased to '1' (4-6), and the authentication success and COUNT value An authentication response message indicating an increase of '1' is transmitted to the terminal (4-7).

On the other hand, if the AUTHR matching check (4-3) fails, the AUTHR discrepancy processing procedure is performed (4-8), and if it fails in the COUNT matching check (4-4), the COUNT mismatch processing procedure is performed (4- 9), an authentication response message indicating the authentication failure is transmitted to the terminal (4-7).

In addition, even when the smart card falls into the terminal, in order to perform authentication, in addition to the call origination, call forwarding, and location registration previously defined as the authentication request type, an authentication request type of "card detach" is defined. If the authentication request type is "card detachment", the COUNT value does not increase and terminates immediately because there is no terminal to receive the authentication response message.

5 is a flowchart illustrating a process of a terminal transmitting an authentication request message.

As shown in the figure, the authentication request message is transmitted to the authentication center (5-1), and the terminal checks whether the authentication request type of the transmitted message is "Card Detach" (5-2). If the type is "Card Detach", it ends without waiting for a response from the authentication center. If the type of authentication request is not "Card Detach", it waits for a response from the authentication center (5-3).

After receiving a response from the authentication center (5-4), it checks whether the authentication is successful (5-5), and if the authentication is successful, sends a command to increase the COUNT value '1' to the smart card (5-6). If it fails, exit.

3 to 5 show that when the smart card is adopted, the COUNT has a smart card duplication detection function, and the terminal only serves as a smart card reader. In practice, however, a smart card cannot be duplicated, and a device capable of copying is a terminal. If it is possible to obtain the subscriber identifier in the wireless section and store it in the smart card to provide the service, it can be said that COUNT is responsible for the smart card duplication detection function, but this is practically impossible, so the problem in adopting the smart card is the terminal replication to be. Therefore, storing COUNTs on a smart card is a common approach, but it's not an efficient way.

6 to 8 are flowcharts illustrating a method of detecting a terminal duplication using a call history count when a smart card is adopted according to the present invention, and FIG. 6 is a COUNT when a smart card is adopted in a system conforming to IS-41C and IS-95. When a value is stored in the terminal, the authentication is performed between the smart card, the terminal, and the network (authentication center).

As shown in the figure, when the ESN is stored in the terminal, the COUNT value is set to '0' (6-1), the smart card contacts the terminal (6-2) and the power is supplied to the terminal (6- 3) The terminal device (including the smart card and the terminal) starts operation.

Subsequently, the terminal receives a random number (RAND) 6-4 provided by the authentication center and transmits an authentication response generation request command with its ESN to the smart card (6-5), and stores the smart card A-. An authentication response (AUTHR) is generated by inputting a hash function using an SSD, a RAND, and an ESN generated by a key, a MIN, and an A-key (6-6).

Subsequently, the AUTHR and MIN generated by the smart card are transmitted to the terminal in response to the authentication response generation request (6-7), and the terminal stores the MIN and AUTHR from the smart card, and the ESN, COUNT, and RAND stored by the terminal. The authentication request message containing the value is sent to the authentication center (6-8).

7 illustrates a process in which the authentication center receives and processes an authentication request message.

As shown in the figure, the authentication center receives an authentication request message from the terminal (7-1) and generates an authentication response (AUTHR) with MIN, ESN, SSD and RAND as input (7-2), Determine whether AUTHR and AUTHR generated by the authentication center match (7-3). If they match, check whether the COUNT stored by the user and the COUNT from the terminal match (7-4). Check if this is a "Card Detach" (7-5), if the authentication request type is not "Card Detach", increase the COUNT value of the subscriber he owns by '1' (7-6) In response to the successful authentication and an increase in the COUNT value '1', an authentication response message is transmitted to the terminal (7-7).

On the other hand, if the AUTHR match check (7-3) fails, perform the AUTHR discrepancy process (7-8), and if the UT match check (7-4) fails, perform the COUNT mismatch handle (7-9). After that, it sends an authentication response message indicating the authentication failure to the terminal (7-7) and ends. If the authentication request type is "card removal", the COUNT value in the subscriber profile held by the authentication center is reset to '0' (7-10).

8 is a flowchart illustrating a process of a terminal transmitting an authentication request message.

As shown in the figure, the terminal transmits the authentication request message to the authentication center (8-1), and checks whether the authentication request type of the transmitted message is "Card Detach" (8-2). If the request type is "Card Detach", it does not wait for a response from the authentication center, resets the COUNT value stored in the terminal to '0' (8-7), and the authentication request type is "Card Detach". If not, wait for a response from the authentication center (8-3).

After receiving a response from the authentication center (8-4), it is determined whether the authentication is successful (8-5). If the authentication is successful, a command to increase the COUNT value '1' is sent to the smart card (8-6), and authentication fails. To exit.

In IS-41C, COUNT is a value indicating the number of times a terminal performs authentication. Strictly speaking, it is a value that can be incremented by '1' at any time when a network operator is specified, that is, when authentication is performed, such as call origination, call reception, or location registration, and the minimum value of the modular-64 counter is 0 and maximum. The value is 2 ⁶⁴ -1. That is, the count simply indicates the number of times the terminal performs authentication separately from the use of the A-key or SSD, which is a secret key.

When the COUNT is used in FIGS. 6 to 8, the cycle of the COUNT is the time until the smart card is inserted into the terminal and used and then separated. However, in this case, if the subscriber profile in the authentication center is configured with the MIN as a base, the terminal can be duplicated and used as long as it is not duplicated up to the smart card, and the fact of the terminal duplication itself cannot be detected. The only advantage is that it can be used without changing the existing system. At this time, if it is possible to determine that the same ESN is used for different MINs, it is possible to detect terminal duplication. Therefore, the subscriber profile stored in the authentication center should be divided into parts directly related to the subscriber and parts related to the terminal.

9 is an explanatory diagram of a subscriber profile in an authentication center applied to the present invention.

As shown in the figure, subscriber profile 9-1 is composed of MIN 9-2 and A-key 9-3, and terminal profile 9-4 is composed of ESN 9-5 and COUNT. It consists of (9-6).

When a subscriber requests location registration or authentication with MIN and ESN, the authentication center uses two profiles to construct one subscriber profile 9-7 currently in service. If the mobile communication network manages the subscriber profile and stores the COUNT value of the MIN in use when removing the card from the terminal in both the authentication center and the terminal, the COUNT can be used perfectly as a means of detecting the duplication of the terminal.

10 and 11 are flowcharts illustrating an example of a method for detecting a duplication of a terminal using a call history count when adopting a smart card according to the present invention.

FIG. 10 illustrates a process in which the authentication center receives the authentication request message in FIG. 6.

As shown in the figure, the authentication center receives an authentication request message from the terminal (10-1) and checks whether there is a relationship between the MIN and the ESN (10-2). Identify the card as inserted into a new terminal, form a relationship between MIN and ESN (10-3), and if there is a relationship between MIN and ESN, generate authentication response (AUTHR) with MIN, ESN and SSD as input (10-4)

Subsequently, it is determined whether the AUTHR from the terminal and the AUTHR generated by the authentication center match (10-5), and if it matches, it is checked whether the COUNT stored in the terminal and the COUNT from the terminal match (10-6). If there is a match, it is checked whether the authentication request type is "Card Detach" (10-7). If the authentication request type is not "Card Detach", the COUNT value of the subscribers owned is increased to '1'. (10-8), an authentication response message indicating an increase in the COUNT value '1' with authentication success is transmitted to the terminal (10-9).

On the other hand, if the AUTHR matching check (10-5) fails, the AUTHR discrepancy processing (10-10) procedure is performed. If the COUNT matching check (10-6) fails, the COUNT discrepancy processing (10-11) procedure is performed. After that, an authentication response message indicating the authentication failure is transmitted to the terminal (10-9). If the authentication request type is "card detachment", the relationship between the MIN and the ESN is released (10-12).

11 is a flowchart illustrating a process of a terminal transmitting an authentication request message in FIG. 6.

As shown in the figure, the terminal transmits an authentication authentication request message (11-1), and checks whether the authentication request type of the transmitted message is "Card Detach" (11-2), and then "card removal ( Card Detach) "without waiting for a response from the authentication center, and stores the current COUNT value of the terminal in an area that cannot be erased, such as ESN (11-3), and if not" Card Detach ", the response from the authentication center is returned. Wait (11-4)

Thereafter, when the terminal receives a response from the authentication center (11-5), it determines whether the authentication is successful (11-6), and if the authentication is successful, transmits a COUNT value '1' increasing command to the smart card (11-7), Exit if authentication fails.

Since smart card duplication is virtually impossible and AUTHR inconsistency is less likely to occur due to terminal duplication, if COUNT is used as input to a hash function without using RAND, AUTHR inconsistency will become COUNT inconsistency. There is no need to compare and COUNT twice. This method can be applied to both the case of resetting the COUNT value to '0' when the smart card is removed from the terminal and the case of storing the COUNT value.

12 and 13 are flowcharts illustrating a method of detecting a terminal duplication using a call history count when a smart card is adopted according to the present invention. FIG. 12 is a hash function input of a COUNT without providing RAND in a network (authentication center). In the case of using, as shown in Figure 6 when using the COUNT, the authentication process between the smart card, the terminal and the network (represented by the authentication center) is shown.

As shown in the figure, the terminal stores the ESN, sets the COUNT value to '0' (12-1), the smart card contacts the terminal (12-2), and power is supplied to the terminal (12-2). -3) The terminal device (including the smart card and the terminal) starts operation.

Thereafter, the terminal transmits an authentication response generation request command including the COUNT and the ESN stored by the terminal to the smart card (12-4), and generates using the A-key, MIN, and A-key stored in the smart card. The SSD, the COUNT and the ESN from the terminal generate an authentication response (AUTHR) as the input of the hash function (12-5).

Subsequently, the AUTHR and MIN generated by the smart card are transmitted to the terminal in response to the authentication response generation request (12-6), and the terminal includes the MIN and AUTHR from the smart card and the ESN and COUNT values stored by the terminal. The authentication request message is sent to the authentication center (12-7).

13 illustrates a process in which the authentication center receives and processes an authentication request message.

As shown in the figure, the authentication center receives an authentication request message from the terminal (13-1) and generates an authentication response (AUTHR) by inputting MIN, ESN, SSD and COUNT (13-2), It is judged whether the AUTHR and the AUTHR generated by the authentication center match (13-3), and if it matches, it is checked whether the authentication request type is "Card Detach" (13-4), and the authentication request type is "card detach ( Card Detach) ", the subscriber's own COUNT value is increased by 1 (13-5), and the authentication response message indicating the successful authentication and the COUNT value '1' is transmitted to the terminal (13-6).

On the other hand, if the AUTHR coincidence check 13-3 fails, it performs the AUTHR mismatch process 13-7 and sends an authentication response message indicating the authentication failure to the terminal (13-6). If the authentication request type is "Card Detach", the COUNT value in the subscriber profile held by the authentication center is reset to '0' (13-8).

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains, and the above-described embodiments and accompanying It is not limited to the drawing.

In the present invention as described above, when the smart card is adopted in the mobile communication, the call history count can be stored in the terminal and the terminal duplication can be easily detected by improving the operation method, and the call history count is used as the input of the hash function for authentication. The comparison operation of the center can be reduced, and the smart card is adopted in the mobile communication system using IS-41C and IS-95, so that the authentication function can be efficiently performed.

Claims (7)

In the terminal duplication detection method applied to a mobile communication network, A first step of the terminal storing the terminal identification information, setting the call history count to a predetermined value, receiving a random number from the authentication center, and transmitting an authentication response generation request message together with the terminal identification information to the smart card; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information, shared secret data stored in the smart card, and a random number and terminal identification information from the terminal, and the authentication response and subscriber generated by the smart card. Transmitting identification information to the terminal in response to an authentication response generation request; Transmitting, by the terminal, an authentication request message including subscriber identification information and authentication response from the smart card, terminal identification information, call history count value, and random number stored therein to the authentication center; And When the authentication center confirms the relationship between the subscriber identification information and the terminal identification information, and confirms the authentication request type and transmits the authentication response to the terminal, the terminal checks the authentication response and sends a command to increase the call history count value to the smart card. 4th step of transmitting Terminal replication detection method using a call history count when adopting a smart card comprising a. The method of claim 1, The third step, A fifth step of the terminal transmitting an authentication request message including subscriber identification information and authentication response from the smart card, terminal identification information, call history count value and random number stored therein to the authentication center; And A sixth step of checking, by the terminal, whether the authentication request type is "Card Detach"; A seventh step of storing the call history count value or resetting the call history count value to a predetermined value if the authentication request type is "Card Detach" as a result of the sixth step inspection; And An eighth step of waiting for an authentication response from the authentication center if the authentication request type is not "Card Detach" as a result of the sixth step inspection; Terminal replication detection method using a call history count when adopting a smart card comprising a. The method according to claim 1 or 2, The fourth step, A ninth step of the authentication center receiving an authentication request message from the terminal to confirm whether a relationship between the subscriber identification information and the terminal identification information exists; A tenth step of forming a relationship between the subscriber identification information and the terminal identification information if the relationship does not exist, and generating an authentication response by inputting the subscriber identification information, the terminal identification information, and the shared secret data; An eleventh step of generating an authentication response by inputting subscriber identification information, terminal identification information, and shared secret data if a relationship exists as a result of the ninth step; A twelfth step of checking, by the authentication center, whether the authentication response from the terminal and the authentication response generated by the authentication center match, and checking whether the authentication request type is "Card Detach"; A thirteenth step of releasing the subscriber identification information and the terminal identification information if the authentication request type is "Card Detach" as a result of the inspection in the twelfth step; A fourteenth step of increasing a call history count value of a subscriber owned by the subscriber if the authentication request type is not "Card Detach" as a result of the check in the twelfth step, and transmitting an authentication response to the terminal; And A fifteenth step in which the terminal checks the authentication response from the authentication center and transmits a call history count value increasing command to the smart card; Terminal replication detection method using a call history count when adopting a smart card comprising a. In a mobile communication network with a large processor, A first function of storing, by the terminal, terminal identification information, setting a call history count to a predetermined value, receiving a random number from the authentication center, and sending an authentication response generation request message with the terminal identification information to the smart card; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information, shared secret data stored in the smart card, and a random number and terminal identification information from the terminal, and the authentication response and subscriber generated by the smart card. A second function of transmitting identification information to the terminal in response to an authentication response generation request; A third function of sending, by the terminal, an authentication request message including subscriber identification information and authentication response from the smart card, terminal identification information, call history count value and random number stored therein to the authentication center; And When the authentication center confirms the relationship between the subscriber identification information and the terminal identification information, and confirms the authentication request type and transmits the authentication response to the terminal, the terminal checks the authentication response and sends a command to increase the call history count value to the smart card. 4th function to transmit A computer-readable recording medium having recorded thereon a program for realizing this. In the terminal duplication detection method applied to a mobile communication network, A first step of the terminal storing the terminal identification information, setting the call history count to a predetermined value, and transmitting an authentication response generation request command including the call history count and the terminal identification information to the smart card; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information and shared secret data stored in the smart card, call history count and terminal identification information from the terminal, and the generated authentication response and subscriber identification information. Transmitting a message to the terminal in response to an authentication response generation request; And When the terminal transmits an authentication request message including the subscriber identification information and the authentication response from the smart card and the terminal identification information and the call history count value stored therein, the authentication center generates an authentication response. A third step of checking an authentication request type to increase a call history count value and transmitting an authentication response to the terminal; Terminal replication detection method using a call history count when adopting a smart card comprising a. The method of claim 5, The third step, Transmitting, by the terminal, an authentication request message including subscriber identification information and authentication response from the smart card and terminal identification information and call history count value stored therein to the authentication center; The authentication center receives an authentication request message from the terminal and generates an authentication response by inputting subscriber identification information, terminal identification information, shared secret data, and call history count, and generated by the authentication center and the authentication response from the terminal. A fifth step of checking whether the authenticated response is matched; A sixth step of performing an authentication response disagreement process and transmitting an authentication response message indicating an authentication failure to the terminal, if there is a mismatch as a result of the checking of the fifth step; A seventh step of checking whether the authentication request type is "Card Detach" if the result of the fifth step is confirmed; As a result of the check in the seventh step, if the authentication request type is not "Card Detach", the call history count value of the subscriber owned is increased, and the authentication response message indicating the successful authentication and the call history count value is recalled. An eighth step of transmitting to the terminal; And A ninth step of resetting the call history count in the subscriber profile held by the authentication center to a predetermined value if the authentication request type is "Card Detach". Terminal replication detection method using a call history count when adopting a smart card comprising a. In a mobile communication network with a large processor, A first function of storing, by the terminal, terminal identification information, setting the call history count to a predetermined value, and transmitting an authentication response generation request command including the call history count and the terminal identification information to the smart card; An authentication response is generated by inputting a hash function to a subscriber secret key, subscriber identification information and shared secret data stored in the smart card, call history count and terminal identification information from the terminal, and the generated authentication response and subscriber identification information. A second function of transmitting a message to the terminal in response to an authentication response generation request; And When the terminal transmits an authentication request message including subscriber identification information and authentication response from the smart card and terminal identification information and call history count value stored therein, the authentication center generates an authentication response. A third function of checking an authentication request type to increase a call history count value and transmitting an authentication response to the terminal; A computer-readable recording medium having recorded thereon a program for realizing this.