WO2012065405A1

WO2012065405A1 - Method and system for judging legal terminal

Info

Publication number: WO2012065405A1
Application number: PCT/CN2011/073478
Authority: WO
Inventors: 高淑美
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-11-18
Filing date: 2011-04-28
Publication date: 2012-05-24
Also published as: CN102014388A; CN102014388B

Abstract

A method and system for judging a legal terminal are provided by the present invention. The method includes: a Mobile Switching Center (MSC) receives a COUNT value from a terminal; the MSC compares a COUNT value saved in an authentication entity with the received COUNT value of the terminal to determine whether they are consistent, wherein, the COUNT value saved in the MSC is the COUNT value of the legal terminal; in the case that the consistent is determined, the terminal is judged to be a legal terminal, or else the terminal is judged to be a cloned terminal. The solution of the present invention can differentiate the legal terminal from the all cloned terminal in a communications network, and avoid the cloned terminal embezzling network resource and cross-talk resulted from the embezzlement, and therefore the rights and interests of the legal terminal are protected effectively.

Description

TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a method and system for determining a legal terminal. BACKGROUND OF THE INVENTION With the rapid development of the mobile communication field, some illegal terminals gradually appear in mobile communication networks, and they clone some information of real user terminals, such as international mobile identification codes.

(International Mobile Subscriber Identity, IMSI for short) and other information, trying to access the mobile communication network to steal network resources, we call this type of terminal a clone terminal or an illegal terminal. The current mobile communication networks all have their own set of security mechanisms to prevent such illegal terminals from using network resources to initiate various services. In CDMA 2000 networks, the core network uses electronic serial numbers (ESNs) and The Secret Subscriber Authentication Key (A-key) is used to authenticate the terminal. If the ESN or A-key is inconsistent, the core network will refuse to clone the service applied by the terminal.

CN101203031 illustrates a method for preventing an illegal terminal from being legally used in a case where the same terminal and the cloned terminal IMSI have different ESNs. The method is limited to the solution when the legal terminal and the clone terminal IMSI 4 are the same, the ESN or the A-key are different. So forty pairs of cloned terminals, although we have some way to solve some problems by locking the cloned terminal, but for the completely cloned terminal (the user information of the cloned terminal and the legal terminal are the same, such as IMSI, ESN, A-key All are the same). Under the existing authentication mechanism of the communication network, it is impossible to distinguish between a legitimate terminal and a clone terminal. In this way, the clone terminal steals the network resources and infringes the rights of the legitimate terminal, and the legitimate terminal also pays for the clone terminal. Moreover, when the legal terminal is called, if the legal terminal and the clone terminal are within a certain range, the cloned terminal will be paged to a high probability and enter the call state at the same time, and the clone terminal can also hear the call content of the legitimate terminal. , "cross talk" appeared, and the privacy rights of legitimate terminals were seriously violated. SUMMARY OF THE INVENTION The present invention provides a method and system for determining a legal terminal to solve the above problems. According to an aspect of the present invention, a method for determining a legal terminal is provided, which is applied to a mobile communication network, including: the mobile interaction center MSC receives a COUNT value from the terminal; and the MSC stores the COUNT value in the authentication entity. Comparing with the received COUNT value of the terminal, determining whether the COUNT value is the COUNT value of the legal terminal; if the determination is consistent, determining that the terminal is a legitimate terminal; otherwise, determining that the terminal is a clone terminal. Before the MSC receives the COUNT value from the terminal, the method further includes: the legal terminal responds to the parameter update process initiated by the core network, updates the COUNT value of the legal terminal, and saves; the MSC updates the COUNT value stored in the authentication entity to a legal terminal update. After the COUNT value.

The MSC receiving the COUNT value from the terminal includes: The base station BS receives the COUNT value from the terminal and transmits it to the MSC; the MSC receives the COUNT value of the terminal from the BS. The legal terminal responds to the parameter update process initiated by the core network, and the COUNT value of the updated legal terminal includes: the BS receives the MSC parameter update request message and sends the parameter update command message to the legal terminal; the legal terminal receives the parameter update command message of the BS, and the legal terminal The COUNT value is updated and a parameter update confirmation command message is sent to the BS; the MSC updates the COUNT value stored in the authentication entity to the COUNT value after the legal terminal is updated: the BS sends a parameter update confirmation message to the MSC; the MSC receives the parameter update. After confirming the message, the COUNT value stored in the authentication entity of the MSC is updated to the COUNT value of the authentication parameter after the terminal is updated. The method further includes: receiving, by the BS, a paging request from the MSC, where the paging request carries the COUNT value after the terminal is updated; and the BS stores the COUNT value saved by the BS and the COUNT value carried in the paging response message fed back by the terminal. For comparison, if it is consistent, it is determined that the terminal is a legitimate terminal; otherwise, the terminal is determined to be a clone terminal, and the paging response message is discarded. The method further includes: the terminal comparing the updated COUNT value carried in the received channel assignment message with the COUNT value of the terminal to determine whether the consistency is consistent; if consistent, processing the channel assignment message to enter the traffic channel, otherwise, discarding the channel assignment Information, refusal to enter the traffic channel. According to another aspect of the present invention, a system for determining a legal terminal is provided. The determining system includes: a terminal and a mobile interaction center MSC, where the MSC includes: a first receiving module, setting In order to receive the COUNT value from the terminal, the first determining module is configured to compare the COUNT value stored in the authentication entity with the COUNT value of the received terminal to determine whether the identity is consistent, wherein the MSC is saved in the authentication entity. The COUNT value is the COUNT value of the legal terminal; the first judging module determines that the terminal is a legitimate terminal if the determination is consistent, otherwise, the terminal is determined to be a clone terminal. The terminal includes: a first update module, configured to respond to a parameter update process initiated by the core network, update the COUNT value of the terminal, and save the COUNT value; the MSC further includes: a second update module, configured to save the MSC value in the authentication entity The updated COUNT value for the first update module. The system further includes: a base station BS; the BS includes: a second receiving module, configured to receive a COUNT value from the terminal, and send the COUNT value to the MSC; the first receiving module is further configured to receive the COUNT value of the terminal from the second receiving module . The second receiving module is further configured to receive and save a paging request from the MSC, where the paging request carries the updated COUNT value of the terminal; the BS further includes: a second determining module, configured to set the COUNT value saved by the BS The COUNT value carried in the paging response message fed back by the terminal is compared. If they are consistent, the terminal is determined to be a legitimate terminal; otherwise, the terminal is determined to be a clone terminal, and the paging response message is discarded. The terminal further includes: a third determining module, configured to compare the updated COUNT value carried in the received channel assignment message with the COUNT value of the terminal to determine whether the agreement is consistent; if consistent, process the channel assignment message to enter the traffic channel Otherwise, the channel assignment information is discarded and the traffic channel is denied. The invention uses the COUNT field in the authentication information to distinguish between a legitimate terminal and a clone terminal. The related art can solve the problem that the completely cloned terminal and the legal terminal cannot be distinguished in the communication network, the cloning terminal steals the network resource and the crosstalk problem caused thereby, thereby effectively protecting the rights of the legitimate terminal. Other features and advantages of the invention will be set forth in the description which follows, and The objectives and other advantages of the invention will be realized and attained by the <RTI BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a flow chart of a method for determining a legal terminal according to an embodiment of the present invention; FIG. 2 is a flow chart showing parameter updating according to a preferred embodiment of the present invention; FIG. 3 is a schematic diagram of a parameter update according to a preferred embodiment of the present invention; The cloning terminal first returns the paging response, and the authentication center authentication fails to pass the flowchart of the call failure. FIG. 4 is a schematic flowchart of the BS determining whether the paging response is a clone terminal according to the preferred embodiment of the present invention; In the preferred embodiment of the present invention, when the legal terminal and the clone terminal are in the same area,

FIG. 6 is a schematic flowchart of a method for solving a "crosstalk" problem occurring in the embodiment shown in FIG. 5. FIG. 7 is a structural block diagram of a system for determining a legal terminal in the embodiment of the present invention; 8 is a schematic structural diagram of a determination system of a legal terminal in a preferred embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. It should be noted that, in the following embodiments, both the base station BS and the mobile interaction center MSC need to be authenticated. In this way, the terminal will have an authentication parameter in the access message. FIG. 1 is a flowchart of a method for determining a legal terminal according to an embodiment of the present invention. The method is applied to the mobile communication network. As shown in FIG. 1, the method includes: Step S102: The mobile interaction center MSC receives the COUNT value from the terminal. In a preferred implementation process, the MSC receiving the COUNT value from the terminal includes: the base station BS receiving the COUNT value from the terminal and transmitting the COUNT value to the MSC; and the MSC receiving the COUNT value of the terminal from the BS. Step S104: The MSC compares the COUNT value stored in the authentication entity with the COUNT value of the received terminal to determine whether the MSC value is COUNT. The COUNT value stored in the authentication entity is COUNT of the legal terminal. Values; Step S106, if the determination is consistent, it is determined that the terminal is a legitimate terminal, otherwise, the terminal is determined to be a clone terminal. As can be seen from the above embodiment, the present invention uses the COUNT field in the authentication information to distinguish between a legitimate terminal and a clone terminal. The related art can solve the problem that the completely cloned terminal and the legal terminal cannot be distinguished in the communication network, the cloning terminal steals the network resource and the crosstalk problem caused thereby, thereby effectively protecting the rights of the legitimate terminal. Preferably, before performing step S102, the following processing may also be included:

(1) The legal terminal responds to the parameter update process initiated by the core network, and updates the COUNT value of the legal terminal and saves it; in the preferred implementation process, the legal terminal responds to the parameter update process initiated by the core network, and updates the COUNT value of the terminal to include The BS receives the MSC parameter update request message and sends a parameter update command message to the terminal; the terminal receives the parameter update command message of the BS, updates the COUNT value of the terminal, and sends a parameter update confirmation command message to the BS. (2) The MSC updates the COUNT value stored in the authentication entity to the updated COUNT value of the legal terminal. In the preferred implementation process, the MSC updating the COUNT value stored in the authentication entity to the COUNT value after the terminal is updated includes: the BS sending a parameter update confirmation message to the MSC; after receiving the parameter update confirmation message, the MSC receives the parameter update confirmation message. And updating the COUNT value of the foregoing MSC to the COUNT value of the foregoing authentication parameter after the terminal is updated. The above preferred embodiment is described in detail below with reference to an example: Embodiment 1 The updated value of the COUNT value of the legal terminal is 1 (0 before the update), the COUNT value of the clone terminal is 0, and the COUNT value recorded by the authentication center is the updated COUNT value of the legal terminal. Both the BS and the MSC are required to be authenticated. In this way, the terminal will have an authentication parameter in the access message. After the caller is successfully established, the core network initiates a parameter update process, and the purpose is that the terminal can update the COUNT value of the authentication parameter. By default, the COUNT value saved by all terminals is 0. When the terminal receives the Parameter Update Order message, the above-mentioned legal terminal will update the COUNT and save the new COUNT value. When the call is accessed, The updated COUNT value is brought to the BS in the authentication parameter, and is transparently transmitted by the BS to the MSC.

The COUNT value update process of the above embodiment is further described below in conjunction with FIG. 2 is a flowchart of parameter update according to a preferred embodiment of the present invention. As shown in FIG. 2: Step S202, the MSC sends a Parameter Update Request message to the BS, and starts a timer T3220. Step S204, the BS sends parameters. The parameter update order message is sent to the terminal MS (Mobile Station); step S206, the legal terminal MS updates the COUNT value, and sends a parameter update confirmation order message to the BS; step S208, the BS sends the parameter update. The Parameter Update Confirm message is sent to the MSC. After receiving the message, the MSC updates the COUNT value in the authentication entity and stops the timer T3220. The update process of the foregoing embodiment only actively updates the COUNT for the calling party, and does not actively update the COUNT for the called party, which can reduce the frequency of updating the COUNT, and avoid the situation that the COUNT is updated when the cloned terminal and the legitimate terminal are in the crosstalk. Of course, the above update process can also perform COUNT update on the first call after the legitimate terminal is turned on, and does not perform COUNT update at other times, which can reduce the number of COUNT updates and improve system efficiency. The above authentication center (MSC) keeps the legal terminal authentication parameters updated in the authentication entity.

COUNT value, and use COUNT value for authentication calculation: Because the COUNT value of the legal terminal is updated during the above update process, the authentication parameter COUNT value of the legal terminal and the clone terminal is different, and the authentication center (MSC) saves COUNT value is the COUNT value of the legal terminal, so when the authentication center (MSC) performs authentication, in addition to using IMSI, ESN, A-KEY In addition to the number of authentication, the COUNT parameter is used for authentication. If the COUNT value is different, the description is to clone the terminal and reject the call. The foregoing method embodiment includes the first embodiment, which can basically solve the "crosstalk" problem of the clone terminal and the legal terminal. However, in the following case, the call may also fail: the core network initiates a paging request, when the above legal terminal and When the cloned terminal is within the scope of this paging, the BS will send a paging request message to both the legal terminal and the clone terminal. If the cloned terminal first returns the paging response, the core network will call the call because the COUNT authentication fails. Reject, even if the legitimate terminal returns the paging response later, the call still fails. In order to facilitate understanding of the above-mentioned cloned terminal first paging response, the authentication center fails to pass the call and causes the call to fail, which will be described below with reference to FIG. 3, it is assumed that MS_1 is a cloning terminal, and MS_2 is a legal terminal. As shown in FIG. 3, the following mainly includes the following processing: Step S302: The MSC sends a paging request (Pageing Request) message to the BS; Step S304, the cloning terminal MS_1 is in the present Within the secondary paging range, the BS sends a paging message (General Page) to MS_1; step S306, assuming that the legitimate terminal MS_2 is within the current paging range, B S sends a paging message to the MS_2 (General Page); Step S308, the cloning terminal MS_1 first returns a Paging Response message to the BS, and the COUNT parameter value in the message is 0. After receiving the paging response message, the BS receives the paging response message. Sending a paging response message (Paging Response) to the MSC, the COUNT parameter value in the message is 0; Step S310, the MSC receives the paging response message (Paging Response), and the authentication center (MSC) performs COUNT authentication, The COUNT value of the Paging Response message is inconsistent with the COUNT value saved by the authentication center, the authentication fails, and the current call fails; Step S312, the legitimate terminal MS_2 returns a paging response message to the BS, and the paging response message is The COUNT value of the band is 1. However, since the call has been released at this time, the paging response message of the legal terminal is invalid at this time. To solve the problem of the embodiment shown in FIG. 3, preferably, the above method may further include the following deal with:

The BS receives and stores a paging request from the MSC, where the paging request carries the updated COUNT value of the terminal; the COUNT value saved by the BS and the COUNT carried in the paging response message fed back by the terminal The values are compared. If they are consistent, the terminal is determined to be a legitimate terminal; otherwise, the terminal is determined to be a clone terminal, and the paging response message is discarded. In order to better understand the above preferred embodiments, the following description will be made in conjunction with the second embodiment. In the embodiment, the COUNT field is added to the paging request message, and when the core network sends the paging message, the COUNT value of the recorded legal terminal is sent to the BS through the paging message, and the BS records the paging message. COUNT value, when the BS receives the paging response, compares the COUNT value of the authentication parameter in the paging response message with the COUNT value of the paging request message authentication parameter, and if the COUNT value does not match, it indicates that the paging is returned by the clone terminal. In response to the message, the BS directly discards the paging response message and does not process it. If the COUNT value is consistent, the processing continues according to the normal paging response procedure. This can prevent the cloning terminal from responding first and causing the paging failure. In order to better understand the above process, it will be described in detail below with reference to FIG. 4; FIG. 4 shows: Step S402, the MSC sends a paging request to the BS, and the paging request (Paging Request) carries the COUNT parameter, the BS record book. The COUNT value of the secondary paging request is 1; Step S404, the cloning terminal MS_1 is within the current paging range, and the BS sends a General Page message to the MS_1; Step S406, assuming that the legal terminal MS_2 is within the current paging range, the BS gives MS_2 send

General Page message; Step S408, the clone terminal MS_1 first returns a paging response message to the BS, and the COUNT value in the Page Response message is 0. The BS determines that the COUNT value of the paging response is inconsistent with the COUNT value of the paging request, and considers that it is the paging response of the cloned terminal back, discarding the paging response message; Step S410, the legitimate terminal MS_2 returns a paging response message to the BS, The COUNT value in the message is 1. The BS determines that the COUNT value of the paging response is consistent with the COUNT value of the paging request, and is considered to be a paging response of the legitimate terminal back. In step S412, the BS sends a paging response message to the MSC. When the authentication center performs COUNT authentication, the COUNT value of the comparison Page Response message is consistent with the COUNT value saved by the authentication center, and the authentication is passed to continue the processing of the call flow. In the case where the cloned terminal and the legal terminal are in the same cell, the above solution cannot be solved. After the terminal sends the paging response message to the BS, the timer is set to wait for the channel assignment message. Therefore, in the above example, even if the BS discards the paging response message of the cloned terminal, only the paging response message of the legitimate terminal is processed, but the clone terminal is And the legitimate terminal is waiting for the channel assignment message, so the gram Both the terminal and the legitimate terminal receive the channel assignment message sent by the BS. Both the clone terminal and the legitimate terminal enter the traffic channel. At this time, the "crosstalk" phenomenon may occur. In order to better understand the above-mentioned "crosstalk" process, the above process will be described in detail below with reference to FIG. 5. The embodiment shown in FIG. 5 needs to perform all the steps of the embodiment shown in FIG. 4 in the specific implementation. As shown in FIG. 5, the method mainly includes the following processing: Step S502: The MSC sends a channel assignment request ( Assignment Request) message to the BS. Step S504, the BS sends a channel assignment message to the cell that the legal terminal MS_2 accesses and the non-access message that supports the access handover or supports the access probe handover; Step S506: After the legal terminal MS_2 receives the channel assignment message, enters the service. Channel S508, if the clone terminal MS_1 and the legal terminal MS_2 are in the same 'j, zone, because the clone terminal MS_1 sends a paging response message to the BS in step S408, the clone terminal MS_1 also sets a channel assignment message such as a timer. The channel assignment message may also be received by the clone terminal MS_1; in step S510, the clone terminal MS_1 receives the channel assignment message and enters the service letter. In order to solve the "crosstalk" problem of the embodiment shown in FIG. 5, the method may further include: the terminal is to receive the updated information carried in the received channel assignment message. The COUNT value is compared with the COUNT value of the terminal to determine whether they are consistent; if they are consistent, the channel assignment message is processed to enter the traffic channel, otherwise the channel assignment information is discarded, and the access to the traffic channel is denied. To better understand the above preferred solution The following is described in conjunction with the third embodiment. Embodiment 3 This embodiment is implemented by modifying an air interface protocol, and needs to be added in the channel assignment message.

In the COUNT field, the COUNT value of the legal terminal is filled in the channel assignment when the call is established. After receiving the channel assignment, the terminal compares the COUNT value in the message with the COUNT value saved by itself, and does not process the channel assignment message when the COUNT value is inconsistent, COUNT value The channel assignment message is processed only when it is consistent. Specifically, as shown in FIG. 6, it should be noted that, in this embodiment, the steps of the foregoing embodiment of FIG. 4 before the step S502 and the step S502 before the step S502 are performed before the specific implementation. Specifically, the specific implementation includes: Step S602: The BS sends a channel assignment message to the cell that is accessed by the legal terminal MS_2 and the non-access message that supports the access handover or supports the access probe handover, where the message carries the COUNT value of the legal terminal MS_2. Step S604, the legal terminal MS_2 After receiving the channel assignment message, determining that the COUNT value in the channel assignment message is consistent with the COUNT value saved by the terminal, processing the channel assignment message, and entering the traffic channel; step S606, if the clone terminal MS_1 and the legitimate terminal MS_2 are in the same 'area, because the clone terminal The MS_1 sends a paging response message to the BS in step d, and the clone terminal MS_1 also sets a channel assignment message such as a timer. Therefore, the channel assignment message may also be received by the clone terminal MS_1, and the channel assignment message carries the COUNT value of the legal terminal MS_2; after receiving the channel assignment message, the clone terminal MS_1 determines the COUNT value in the channel assignment message and the COUNT saved by the terminal. The values are inconsistent and the channel assignment message is discarded. Therefore, the clone terminal MS_1 does not enter the traffic channel, and there is no "crosstalk" between the clone terminal MS_1 and the legitimate terminal MS_2. FIG. 7 is a structural block diagram of the determination system of the legal terminal of the embodiment of the invention. As shown in FIG. The determining system includes: a terminal 70 and a mobile interaction center MSC 72, wherein the MSC 72 includes: a first receiving module 722 configured to receive a COUNT value from the terminal 70; and a first determining module 724 configured to: The COUNT value stored in the authentication entity is compared with the received COUNT value of the terminal 70 to determine whether the COUNT value is the COUNT value of the legal terminal. The first determining module determines In the case of the same, it is determined that the terminal 70 is a legitimate terminal, otherwise, the terminal 70 is determined to be a clone terminal. Preferably, as shown in FIG. 8, the terminal 70 includes: a first update module 702, configured to respond to the core network. The parameter update process updates the COUNT value of the terminal 70 and saves the foregoing; the MSC 72 further includes: a second update module 726, configured to The COUNT value of the MSC 72 stored in the authentication entity is updated to the COUNT value of the first update module 702. Preferably, as shown in FIG. 8, the system further includes: a base station BS74, where the BS 74 includes: a second receiving module 742, configured to receive the COUNT value from the terminal 70, and send it to The MSC 72; the first receiving module 722 is further configured to receive the COUNT value of the terminal from the second receiving module 742. The second receiving module 742 is further configured to receive and save a paging request from the MSC 72, where the paging request carries the updated COUNT value of the terminal 70; preferably, as shown in FIG. 8, the BS74 The method further includes: a second determining module 744, configured to compare the COUNT value saved by the BS 74 with the COUNT value carried in the paging response message fed back by the terminal 70, and if yes, determine that the terminal 70 is a legal terminal; otherwise, determine The terminal is a clone terminal, and the paging response message is discarded. Preferably, as shown in FIG. 8, the terminal 70 may further include: a third determining module 704, configured to compare the updated COUNT value carried in the received channel assignment message with the COUNT value of the terminal 70, Determining whether they are consistent; if they are consistent, the above channel assignment message is processed, and the traffic channel is entered, otherwise the channel assignment information is discarded, and the access to the service channel is denied. It should be noted that, in the specific application, the foregoing method may perform other methods of authentication. For example, in the related art, the terminal is authenticated by using the ESN or the A-key, and then the foregoing use authentication of the foregoing embodiment of the present invention is performed. The COUNT value of the parameter is authenticated, so that the embodiment of the present invention is more applicable. It should be noted that the above authentication entities include: Mobile Switching Center emulation (MSCe), Home Location Register (HLR), where shared secret and secret data (Shared Secret Data) , referred to as SSD for short) can be shared in the above MSCe, not shared in the above HLR. It should be noted that the preferred working manners of the related modules in the foregoing system may be specifically described in the foregoing method embodiments, and details are not described herein again. In summary, the present invention utilizes the COUNT field in the authentication information to distinguish between a legitimate terminal and a clone terminal. The invention solves the adverse effects of the cloned terminal on the legitimate terminal caused by the inability to distinguish the completely cloned terminal and the legal terminal in the communication network, such as the cloning terminal stealing network resources and the crosstalk problem caused thereby, thereby effectively protecting the legal terminal Rights. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. Perform the steps shown or described, or They are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

A method for determining a legal terminal, applied to a mobile communication network, comprising:

The mobile interaction center MSC receives the COUNT value from the terminal;

The MSC compares the COUNT value stored in the authentication entity with the received COUNT value of the terminal to determine whether the COUNT value is the legal terminal. The COUNT value; in the case of determining consistency, the terminal is determined to be a legitimate terminal, otherwise, the terminal is determined to be a clone terminal.

2. The method according to claim 1, wherein before the MSC receives the COUNT value from the terminal, the method further includes:

The legal terminal responds to the parameter update process initiated by the core network, and updates the COUNT value of the legal terminal and saves the value;

The MSC updates the COUNT value stored in the authentication entity to the updated COUNT value of the legal terminal.

The method according to claim 1 or 2, wherein the MSC receiving the COUNT value from the terminal comprises:

The base station BS receives the COUNT value from the terminal and sends it to the MSC; the MSC receives the COUNT value from the terminal of the BS.

4. The method according to claim 2, wherein

The legal terminal responds to the parameter update process initiated by the core network, and updating the COUNT value of the legal terminal includes:

Receiving, by the BS, the MSC parameter update request message, and sending a parameter update command message to the legal terminal;

The legal terminal receives the parameter update instruction message of the BS, updates the COUNT value of the legal terminal, and sends a parameter update confirmation instruction message to the BS; the MSC updates the COUNT value stored in the authentication entity. The updated COUNT value for the legal terminal includes: Sending, by the BS, a parameter update confirmation message to the MSC;

After receiving the parameter update confirmation message, the MSC updates the COUNT value stored in the authentication entity to the COUNT value of the authentication parameter after the terminal is updated. The method according to claim 4, wherein the method further comprises:

The BS receives and stores a paging request from the MSC, where the paging request carries the updated COUNT value of the terminal;

The BS compares the saved COUNT value with the COUNT value carried in the paging response message fed back by the terminal, and if yes, determines that the terminal is a legal terminal; otherwise, determines that the terminal is a clone terminal, and discards The page response message. The method according to claim 4, wherein the method further comprises:

The terminal will receive the updated channel carried in the received channel assignment message

The COUNT value is compared with the COUNT value of the terminal to determine whether they are consistent;

If they are consistent, the channel assignment message is processed, entering the traffic channel, otherwise the channel assignment information is discarded and the access to the traffic channel is denied. A system for determining a legal terminal, the determining system includes: a terminal and a mobile interaction center MSC, where the MSC includes:

a first receiving module, configured to receive a COUNT value from the terminal; a first determining module, configured to save the COUNT value of the MSC in the authentication entity and the received COUNT value of the terminal The COUNT value stored in the authentication entity is the COUNT value of the legal terminal;

The first determining module determines that the terminal is a legal terminal if the determination is consistent, otherwise, determines that the terminal is a clone terminal. The system according to claim 7, wherein

The terminal includes: a first update module, configured to respond to a parameter update process initiated by the core network, update a COUNT value of the terminal, and save the COUNT value;

The MSC further includes: a second update module, configured to update the COUNT value stored in the authentication entity by the MSC to the updated COUNT value of the first update module.

The system according to claim 7, wherein the system further comprises: a base station BS;

The BS includes: a second receiving module, configured to receive a COUNT value from the terminal, and send the COUNT value to the MSC;

The first receiving module is further configured to receive a COUNT value of the terminal from the second receiving module.

10. The system according to claim 9, wherein

The second receiving module is further configured to receive and save a paging request from the MSC, where the paging request carries the updated COUNT value of the terminal; the BS further includes: a module, configured to compare the COUNT value saved by the BS with a COUNT value carried in a paging response message fed back by the terminal, and if yes, determine that the terminal is a legal terminal; otherwise, determine that the terminal is a clone terminal. , discard the paging response message.

The system of claim 7, wherein the terminal further comprises:

The third determining module is configured to compare the updated COUNT value carried in the received channel assignment message with the COUNT value of the terminal to determine whether the consistency is consistent; if they are consistent, process the channel assignment message, and enter Traffic channel, otherwise discarding channel assignment information, denying access to the traffic channel.