WO2012106982A1 - Method and system for quick verification of international mobile station equipment identity - Google Patents

Abstract

Disclosed is a method for quick verification of the International Mobile station Equipment Identity (IMEI). The method comprises: an equipment identity register (EIR) receiving an IMEI verification request message carrying at least the IMEI and current equipment status (ES) information; querying a local mobile equipment list, and if the specified mobile equipment exists, taking the ES in the list as the verification result, otherwise, taking the current ES as the verification result; sending the information contained in the IMEI verification request message to a central EIR (CEIR), to update the database and the mobile equipment list in the EIR; and applying the update result for a next verification. Also disclosed is a system for IMEI quick verification, an EIR and a CEIR. The present invention is capable of implementing fast verification of the IMEI, while saving system resources and reducing equipment construction costs.

Description

 Method and system for quickly verifying international mobile device identification Technical field

The present invention relates to the field of mobile communications, and in particular, to a method, system, device identification register device, and central device identification register device for quickly verifying an international mobile device identity.

Background technique

 In GSM, WCDMA and TD-SCDMA digital cellular mobile communication networks, IMEI (International Mobile Station Equipment Identity, International Mobile Equipment Identity) An individual unit that uniquely identifies a mobile device. Therefore, it can be implemented based on ME (Mobile Equipment) by enabling IMEI verification mechanism. , mobile device) model or single unit network access control, such as preventing theft, failure and other illegal devices access to the network.

 IMEI consists of 15 digits, all numbers are binary coded 0 to 9 The decimal number, the number above this range is invalid. According to the 3GPP protocol, the specific configuration is TAC-SNR-SP, where: TAC (Type Allocation Code, The model allocation code is 8 digits; the SNR (Serial Number) is 6 digits, and the same type of mobile device does not have two identical SNR numbers; SP (Spare, alternate number) is 1 digit, set to 0 when transmitting via mobile station, and IMEI stored in mobile station is usually supplemented 1 The bit number is used as a check digit to prevent human error.

 IMEISV (International Mobile station Equipment Identity and Software Version Number, International Mobile Device ID and Software Version Number) A total of 16 digits, which was increased by IMEI The SVN (Software Version Number) is composed of two digits. The specific configuration is TAC-SNR-SVN.

 EIR ( Equipment Identity Register) It contains one or several databases for storing IMEI, and mainly performs functions such as identification of mobile devices, monitoring and blocking. IMEI can be stored in three separate lists of whitelists, greylisters, and blacklists:

 ● The number range of all allowed device IDs is saved in the whitelist;

 ● All blocked device IDs are saved in the blacklist.

 ● Devices in the graylist are not blocked but are recorded by the network (for statistical and other purposes).

 ES (Equipment Status) is IMEI at EIR The storage status in the list is: whitelisted, grayed out, blacklisted, and unknown. EIR can be based on administrators and CEIR (Central Equipment The Identity Register, Central Device Identification Register) requires updating the stored IMEI and ES. Common EIR implementation techniques, generally for ES Implicit storage is used, that is, a whitelist, a graylist, a blacklist, and the like are respectively set, and the status of the IMEI is determined according to whether IMEI appears in a certain data table. In some cases, an IMEI It may appear in different lists at the same time, resulting in ambiguity in the results of the query.

 IMSI (International Mobile Subscriber Identity) , International Mobile User Identity) uniquely identifies a mobile user with a total of 15 digits, by MCC (Mobile Country Code), MNC ( Mobile Network Code, Mobile Network Code) and MSIN (Mobile Subscriber Identification Number) , mobile user identification number). In some known application technologies, IMSI has been used to improve EIR functionality.

 In addition to IMSI separation, IMEI can be performed when any access attempt is made by the mobile station. Verify, or in accordance with the mobile communication operator's security policy, perform IMEI verification when dedicated resources are available in an established call. When the response returned from EIR is received as 'blacklisted' or When 'not whitelisted', the network should prohibit any access attempts or ongoing calls and give the user an 'illegal terminal' The prompt, this is equivalent to authentication failure, therefore, all calls and location updates are forbidden and only emergency calls can be completed.

 In addition, the IMEI verification mechanism has also been used for IMS (IP Multimedia Subsystem, IP multimedia subsystem) and other devices in the access management.

 EIR can be based on MSC (Mobile-service Switch Center, Mobile Service Switching Center) ) / SGSN (Serving GPRS Support Node), verify IMEI and its status, and inform the result MSC/SGSN.

 Whitelists should use IMEI, blacklists and graylists can also use IMEISV. The type of IMEI can be unknown. The MSC/SGSN can be configured to block unknown devices.

 The interface between the MSC and the EIR is the F interface, which is responsible for exchanging data between the MSC and the EIR. F Interface signaling uses the MAP protocol. The EIR completes the verification of the IMEI status of the mobile terminal in the circuit domain through the F interface. During the evolution of the core network, the MSC splits into an MSC server ( MSC Server) and MGW (Media GateWay, Mobile Media Gateway) two network elements. The F interface is inherited by the MSC server. Unless otherwise stated, the F The interface will include an interface between the EIR and the MSC and the MSC server, and the MSC device also includes the MSC server device.

 The interface between the SGSN and the EIR is the Gf interface, which is responsible for exchanging data between the SGSN and the EIR. Gf Interface signaling uses the MAP protocol. The EIR completes the verification of the IMEI status of the mobile terminal in the packet domain through the Gf interface.

 Specifically, the request and verification process of the IMEI is as shown in FIG. 1, and includes the following steps:

 Step S101, the MSC/SGSN sends to the MS (Mobile Station, mobile station) 'Identity Request (Identity Type)' message;

 Step S102, the MS responds with 'Identity Response (Mobile Identity ) ' ;

 Step S103, if the MSC/SGSN decides to verify the IMEI by EIR, it sends to the EIR. 'Check IMEI(IMEI)' message, otherwise, end the process;

 Step S104, EIR returns a 'Check IMEI Ack (IMEI)' message, The MSC/SGSN determines whether the mobile device is allowed to access the network according to the received verification result.

 Specifically, the authentication encryption and IMEI verification process is as shown in FIG. 2, and includes the following steps:

 Step S201, the MSC/SGSN sends an 'Authentication and Ciphering Request' message containing the IMEISV parameter;

 Step S202, MS responds to 'Authentication and Ciphering Response' ;

 Step S203: If the MSC/SGSN decides to verify the IMEI by EIR, it sends to the EIR. 'Check IMEI(IMEI)' message, otherwise, end the process;

 Step S204, EIR returns a message of 'Check IMEI Ack (IMEI)', The MSC/SGSN determines whether the mobile device is allowed to access the network according to the received verification result.

 The data exchange function between MSC/SGSN and EIR in the above IMEI check process is performed by 3GPP TS. The MAP_CHECK_IMEI primitive defined in 29.002 is completed. The MAP_CHECK_IMEI primitive carries multiple mobile-related parameters, such as the call number (Invoke) ID), IMEI, IMEISV, requested device information, device status, BMUEF (Bit Map of UE Faults , user equipment fault bitmap), user error information, and provider error information.

 The MAP_CHECK_IMEI primitives are defined as shown in Table 1 (R4 and previous versions) and Table 2 (R5). And later versions); among them, the following symbols are classified as parameters: M means that the parameter content is mandatory, O means the parameter content is the service provider option, C means the condition parameter, and, ( = ) appended to the preceding token, indicating that the parameter takes the same value as the one shown on the left:

 Table 1: MAP_CHECK_IMEI primitives specified in R4 and previous versions

 Table 2: MAP_CHECK_IMEI primitives specified in R5 and later

 The specific encoding method of the MAP_CHECK_IMEI primitive is in accordance with the 3GPP protocol TS 29.002 The different versions are as follows:

 (1) R4 and previous versions

 checkIMEI OPERATION

 ARGUMENT

 Imei OCTET STRING ( SIZE( 8 ) )

 RESULT

 equipmentStatus ENUMERATED {

 whiteListed ( 0 ),

 blackListed ( 1 ),

 greyListed ( 2 ) }

 ERRORS {

 -- systemFailure -- localValue : 34,

 -- dataMissing -- localValue : 35,

 -- unknownEquipment -- localValue : 7}

 ::= localValue : 43

 ( 2 ) R5 and R6

 checkIMEI OPERATION ::= {

 ARGUMENT SEQUENCE {

 Imei OCTET STRING ( SIZE( 8 ) ),

 requestedEquipmentInfo BIT STRING {

 equipmentStatus (0),

 Bmuef (1 )} ( SIZE( 2 .. 8 ) ),

 extensionContainer SEQUENCE {

 privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF

 SEQUENCE {

 extId MAP-EXTENSION .&extensionId ( {

 ,

 ...} ) ,

 extType MAP-EXTENSION .&ExtensionType ( {

 ,

 ...} { @extId } ) OPTIONAL} OPTIONAL,

 pcs-Extensions [1] IMPLICIT SEQUENCE {

 ... } OPTIONAL,

 ... } OPTIONAL,

 ... }

 RESULT SEQUENCE {

 equipmentStatus ENUMERATED {

 whiteListed ( 0 ),

 blackListed ( 1 ),

 greyListed ( 2 ) } OPTIONAL,

 Bmuef SEQUENCE {

 uesbi-IuA [0] IMPLICIT BIT STRING ( SIZE( 1 .. 128 ) ) OPTIONAL,

 uesbi-IuB [1] IMPLICIT BIT STRING ( SIZE( 1 .. 128 ) ) OPTIONAL,

 ... } OPTIONAL,

 extensionContainer [0] IMPLICIT SEQUENCE {

 privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF

 SEQUENCE {

 extId MAP-EXTENSION .&extensionId ( {

 ,

 ...} ) ,

 extType MAP-EXTENSION .&ExtensionType ( {

 ,

 ...} { @extId } ) OPTIONAL} OPTIONAL,

 pcs-Extensions [1] IMPLICIT SEQUENCE {

 ... } OPTIONAL,

 ... } OPTIONAL,

 ... }

 ERRORS {

 systemFailure |

 dataMissing |

 unknownEquipment }

 CODE local : 43

 }

 (3) R7 and later versions

checkIMEI OPERATION :: = {

 ARGUMENT

 CheckIMEI-Arg

 RESULT

 CheckIMEI-Res

 ERRORS {

 systemFailure |

 dataMissing |

 unknownEquipment}

 CODE local:43 }

 among them,

CheckIMEI-Arg ::= SEQUENCE {

 Imei IMEI,

 requestedEquipmentInfo RequestedEquipmentInfo,

 extensionContainer ExtensionContainer OPTIONAL,

 ...}

CheckIMEI-Res ::= SEQUENCE {

 equipmentStatus EquipmentStatus OPTIONAL,

 Bmuef UESBI-Iu OPTIONAL,

 extensionContainer [0] ExtensionContainer OPTIONAL,

 ...}

RequestedEquipmentInfo ::= BIT STRING {

 equipmentStatus (0),

 Bmuef (1)} (SIZE (2..8))

 -- exception handling: reception of unknown bit Assignments in the

 -- RequestedEquipmentInfo data type shall be Discarded by the receiver

UESBI-Iu ::= SEQUENCE {

 uesbi-IuA [0] UESBI-IuA OPTIONAL,

 uesbi-IuB [1] UESBI-IuB OPTIONAL,

 ...}

UESBI-IuA ::= BIT STRING (SIZE(1..128))

 -- See 3GPP TS 25.413

UESBI-IuB ::= BIT STRING (SIZE(1..128))

 -- See 3GPP TS 25.413

EquipmentStatus ::= ENUMERATED {

 whiteListed (0),

 blackListed (1),

 greyListed (2)}

 extensionContainer SEQUENCE {

 privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF

 SEQUENCE {

 extId MAP-EXTENSION .&extensionId ( {

 ,

 ...} ) ,

 extType MAP-EXTENSION .&ExtensionType ( {

 ,

 ...} { @extId } ) OPTIONAL} OPTIONAL,

 pcs-Extensions [1] IMPLICIT SEQUENCE {

 ... } OPTIONAL,

 ... } OPTIONAL}

 By comparing the definitions and encoding methods of the MAP_CHECK_IMEI primitives in the above versions of the 3GPP protocol, it is known: The most basic content of the MAP_CHECK_IMEI primitive specified by R4 and previous versions, that is, the request message parameter contains IMEI, and the response message parameter contains ES; R5 and R6. On the previous version, the structure and content of the MAP_CHECK_IMEI encoding method have been greatly improved. One main feature is to add an extension container (Extension Container). Parameters, which can carry user-defined information, so the standard 'Check IMEI' message can be extended according to user requirements; R7 and later versions are not yet available for R5 and R6 Make further improvements.

 It can be seen that since the purpose of initially verifying the IMEI is set to prevent the faulty device and the stolen device from accessing the mobile network, it is in R4. When the IMEI is verified in the previous version, the ES corresponding to the IMEI is the only basis for the validity of the mobile device. That is, the EIR usually performs the IMEI check as follows:

 ● Receive 'Check IMEI' message from MSC/SGSN, parse out IMEI, query with IMEI Obtaining an ES corresponding to the indexed mobile device list and sending it back to the MSC/SGSN as an IMEI check result;

 ● Receive 'Check IMEI' message from MSC/SGSN, parse out IMEI and extract TAC from it Querying the list of mobile devices indexed by TAC to obtain the corresponding ES, and sending it back to the MSC/SGSN as an IMEI check result;

 The IMEI-based IMEI verification method implements network access control based on mobile device ME individual units. The TEI-indexed IMEI check method implements network access control based on the mobile device ME model.

 Obviously, the above IM4 verification mechanism of R4 and previous versions cannot prevent IMEI from being illegally copied: if an IMEI If it is legal, the mobile device that illegally copied the IMEI will also be considered legal and can access the mobile network smoothly.

 Especially in 3G In the future mobile communication networks, the dependence of mobile services on mobile devices is becoming more and more obvious. The identification of mobile devices has become a basic condition in the promotion process of many new mobile services. IMEI It is the only way to identify mobile devices, but due to the existence of illegal copying problems, a large number of mobile devices are difficult to be accurately identified, which will inevitably affect the development of new mobile services. Therefore, enable IMEI The verification function increases the recognizability of mobile devices and becomes an inevitable trend in the development of mobile communication networks. It is also the most direct and effective management method for regulating the mobile terminal industry chain, or the basic requirement for enhancing the security of mobile users.

 Therefore, in order to solve the above-mentioned unavoidable IMEI in the standard IMEI check mechanism Illegal replication problems, generally choose to add parameters in the standard 'Check IMEI' message, such as IMSI, MSISDN (Mobile Subscriber ISDN) , mobile user ISDN number), etc., to increase the accuracy of the IMEI identification process.

 Based on the above improvements, EIR usually completes the IMEI check as follows:

 ● Receive enhanced 'Check IMEI' messages from MSC/SGSN and parse out IMEI and IMSI Querying the mobile device list to determine whether the IMEI has been illegally copied and whether the mobile user represented by the IMSI is the IMEI a legitimate user; based on the identity of the mobile device and its user, and the requirements of the legitimate user of the mobile device (such as whether it is reported, whether it is faulty, etc.) and the operator's processing procedures (such as prohibited or Allow illegal copying of devices into the network, etc.) to determine the final ES and send it back to the MSC/SGSN as an IMEI check result;

 ● Receive enhanced 'Check IMEI' messages from the MSC/SGSN and parse out IMEI, MSISDN; querying the mobile device list to determine whether the IMEI has been illegally copied and whether the mobile user represented by the MSISDN is the IMEI a legitimate user; based on the identity of the mobile device and its user, and the requirements of the legitimate user of the mobile device (such as whether it is reported, whether it is faulty, etc.) and the operator's processing procedures (such as prohibited or Allow illegal copying of devices into the network, etc.) to determine the final ES and send it back to the MSC/SGSN as an IMEI check result.

 In the above two IMEI verification methods, the EIR device uses an extended list of mobile devices, that is, using IMSI or The MSISDN identifies the legitimate user of the mobile device corresponding to the IMEI. If the IMEI is not illegally copied or is being used by a legitimate user, the ES in the mobile device list will be As a result of the verification, and based on the network access control of the mobile device. If the IMEI If it has been illegally copied and is being used by an illegal user, the mobile device is controlled by the following methods according to the management rules of the carrier:

 Strictly prohibited: All mobile devices identified by the IMEI are prohibited from accessing the mobile network unless they are being used by legitimate users;

 Partial Prohibition: Prohibition of use by the specific user indicated by IMSI or MSISDN with the IMEI Access the mobile network for the identified mobile device

 Temporarily prohibited: Network access control for mobile devices using IMEI that have been illegally copied is not yet available.

 It can be seen that IMSI and MSISDN are added by enhancing the standard 'Check IMEI' message. After the parameters, EIR can prevent the IMEI from being illegally copied. Even if there are a large number of mobile devices that use illegal copying of IMEI in the network (the so-called 'cottage machine', Gray Handset) can still enable IMEI verification. By first guiding the 'turning positive' process, gradually reduce the number of 'cottage machines' in the network, and then enable EIR for IMEI Verification can minimize the illegal copying of IMEI and improve the recognizability and serviceability of mobile devices.

 After introducing IMSI, MSISDN, etc. as auxiliary parameters, the problem of IMEI being illegally copied can be theoretically solved and will be enabled. The impact of the IMEI verification function on the mobile terminal industry and mobile users is minimized. Although the common technical solutions for introducing auxiliary parameters mostly use non-standard technologies, there is still a gap with large-scale commercialization, but it cannot continue to hinder the activation. IMEI check function.

 EIR needs to be resolved when IMEI verification is enabled in a larger network Networking problem. This is due to the limitation of signaling processing capability, single EIR The capacity of devices is generally tens of thousands to hundreds of thousands of mobile users, and the number of mobile users may range from millions to hundreds of millions, especially mobile users and mobile devices can automatically roam in the network of one or more operators: network Any mobile device inside may appear in any one Among the check queues of EIR devices. Therefore, a single EIR device obviously cannot meet the capacity requirements of a larger network. It is necessary to have multiple EIR devices combined to provide support in a larger network. IMEI The transaction processing capabilities required for the verification function.

 To solve the networking problem of EIR devices, CEIR devices are generally introduced in larger networks. CEIR is a higher level The EIR device stores an IMEI central database that includes information on all mobile devices in the mobile communication network. The IMEI central database is a distributed mass database, generally including IMEI and ES. Other available information includes IMSI, MSISDN, the time of first activation in the network, the time of the most recent occurrence, and which MSC or SGSN was present. CEIR The device implements centralized management of mobile device information and forms a server/client relationship with the EIR device.

 After the CEIR device is equipped, the specific process of IMEI verification is shown in Figure 3, including the following steps:

 Step S301, the MSC/SGSN sends a 'Check IMEI (IMEI)' to the EIR. Message

 Step S302, EIR sends 'Remote Check IMEI (IMEI)' to CEIR a message that translates the local IMEI verification request into a remote query to CEIR;

 Step S303, the CEIR uses the internal identity verification unit to verify the mobile device, and returns to the EIR. 'Remote Check IMEI Ack (IMEI)' message;

 Step S304, EIR returns a message of 'Check IMEI Ack (IMEI)', The MSC/SGSN determines whether the mobile device is allowed to access the network according to the received verification result.

 It can be seen that the CEIR device solves the networking problem of the EIR device and can adapt to the construction needs of mobile communication networks of various sizes. CEIR In addition to the data exchange function required for IMEI verification in the network, the device is also responsible for the sharing and exchange of mobile device lists (mainly blacklists) between different operators.

 According to the above description, it can be seen that the current stage IMEI The feasibility of the verification technology has been solved; however, in the specific implementation process, the following defects still exist:

 First, cost defects:

 The number of mobile users in a large mobile communication network often reaches tens of millions or even hundreds of millions, enabling IMEI The real-time verification function will consume a lot of system processing power, which will eventually lead to a sharp increase in construction costs.

 In particular, in large mobile communication networks, due to the need to rely on CEIR To achieve networked retrieval, the verification process often introduces remote queries, and the application of large distributed databases becomes an inevitable choice.

 Real-time query and superposition of large databases, that is, real-time query of large databases (especially distributed databases), taking up too much network resources, directly pushing up The cost of the IMEI verification system.

 Second, the response time is uncertain:

 After the introduction of the CEIR device, a major problem occurred was that it took too long to determine the status of the mobile device and could not be determined, IMEI The response time of the verify operation is highly volatile; since the valid number of IMEI is up to 14 digits, and IMEI The central database stores a large amount of content and can be extended. In the actual storage process, it is difficult to store by address in a mapping manner, which is generally implemented by means of a data table. Therefore, the query algorithm of the database ultimately determines the IMEI. Time response characteristics of the check: The time of the commonly used data table search algorithm is proportional to NlogN (N is the length of the data table, at IMEI The number of users in the central database); the time taken to query the data table each time is uncertain. The use of caching technology in EIR can improve system performance, but the practical effect is limited and the system complexity is increased.

 Third, inefficiency:

 The essence of the IMEI check is to make the VLR (Visitor) upon receiving a trigger request for a particular mobile device. Location Register, visit location register) / current state of the mobile device stored in the /SGSN with IMEI The target state of the mobile device stored in the central database is consistent; in a network where there is no CEIR device, the IMEI central database is equivalent to the list of devices stored in the EIR device. Common IMEI In the verification technology, the target state of the mobile device is generally queried from the IMEI central database by means of a lookup table, and the current state stored in the VLR/SGSN is updated in the form of a verification result.

Because most mobile devices fully meet the network access requirements during the use of mobile devices, they will not pose a serious threat to the performance of the wireless access network. From the perspective of network operation, only some mobile devices that have been identified as prohibited by professional testing organizations should be blacklisted. From an information security perspective, mobile devices will be blacklisted primarily for theft. If the target of the stolen device is set to find and return the owner, the stolen device should not be blacklisted, but the tracking function should be enabled. From a management perspective, it is unreasonable to blacklist a large number of mobile devices. Therefore, updates to the current state of most mobile devices in the network are not necessary.

 At the same time, due to the long period of change of the state of the mobile device caused by the failure, theft, and replacement, the statistical report of the 3GSM Alliance shows that Between 2003 and 2008, global GSM mobile phone users switched to a new mobile phone every 25 months on average, and the location update that currently triggers IMEI verification can reach 1 to 2 every day. The user can also switch on and off 1 or 2 times a day. Obviously, an update to the current state of the mobile device when the state of the mobile device has not changed is not necessary.

 It can be seen that frequent updates to the status of a large number of mobile devices are the main reasons for the inefficiency of common IMEI verification techniques.

 In summary, IMEI verification is irreplaceable for maintaining the security and identifiability of mobile devices, while existing IMEI The high cost, low efficiency and low cost performance of the verification technology and the response time problem are the key factors hindering the enabling of the IMEI check function, so at this stage, IMEI The development of calibration technology focuses on improving product performance and reducing construction costs. From the perspective of curbing the gray list device based on 'cottage machine' and improving the security and recognizability of mobile devices, it is cost-effective IMEI The market demand for verification technology is becoming more and more urgent, and research on IMEI fast verification technology has also become the focus of EIR applications. Therefore, for IMEI It is also necessary to improve the calibration technology with broad market prospects.

Summary of the invention

 It is an object of the present invention to provide a method and system for quickly verifying an international mobile device identity IMEI. In 3GPP The common IMEI verification method has been improved within the framework of the protocol to improve the time response metrics of the verification and reduce the usage of large database software, thereby reducing the construction cost of equipment such as EIR.

 In order to achieve the above object, the present invention provides a method for quickly verifying IMEI, comprising the following steps:

 Step 1: The EIR receives the IMEI for the MSC/SGSN for a mobile device. After verifying the request message, querying whether there is a data record matching the mobile device in the local mobile device list, and returning the ES determined according to the data record as a check result to the MSC/SGSN And deleting the data record from the local mobile device list if the data record only relates to the mobile device; otherwise returning directly to the current ES as the check result in the IMEI check request message MSC/SGSN; wherein the IMEI check request message carries at least the IMEI of the mobile device and the current ES;

 Step 2: The EIR to CEIR Transmitting a mobile device information update request message; wherein the mobile device information update request message carries information extracted from the IMEI check request message;

 Step 3: The CEIR sends the ES and the IMEI carried in the mobile device information update request message. The ES of the corresponding mobile device stored in the central database is compared; if not, the EIR is Returning a first mobile device information update response message carrying information extracted from the IMEI central database according to a predetermined rule; if consistent, or also to the EIR Returning a second mobile device information update response message, the second mobile device information update response message indicating normal reception of the mobile device information update request message;

 Step four: EIR After receiving the first mobile device information update response message, it is edited as a data record in the local mobile device list.

 In order to achieve the above object, the present invention also provides a system for quickly verifying IMEI, an EIR device, and a CEIR. Equipment.

 The system for quickly verifying IMEI includes EIR and MSC/ interacting with the EIR respectively SGSN and CEIR:

 The MSC/SGSN is configured to send an IMEI for the mobile device to the EIR Verifying the request message, wherein the IMEI check request message carries at least the IMEI of the mobile device and the current ES; and, receives and according to the EIR Returning a verification result, performing network access control on the mobile device;

 The EIR is configured to receive the IMEI sent by the MSC/SGSN Checking the request message, querying whether there is a data record matching the mobile device in the local mobile device list, and returning the device status ES determined according to the data record as a check result to the MSC/SGSN, and if the data record relates only to the mobile device, deleting the data record from the local mobile device list; otherwise directly verifying the current ES in the request message with the IMEI Returning to the MSC/SGSN as a check result; transmitting a mobile device information update request message to the CEIR, wherein the mobile device information update request message carries the IMEI from the And verifying the information extracted in the request message; and receiving the first mobile device information update response message returned by the CEIR, editing it as a data record in the local mobile device list; or receiving the The second mobile device information update response message returned by the CEIR;

 The CEIR is configured to receive the EIR The transmitted mobile device information update request message and the ES carried in the mobile device information update request message and the ES of the corresponding mobile device stored in the IMEI central database Comparing; if not, returning a first mobile device information update response message to the EIR, the first mobile device information update response message carrying the IMEI according to a predetermined rule Information extracted in the central database; if consistent, or returning a second mobile device information update response message to the EIR, the second mobile device information update response message indicates The normal reception of the mobile device information update request message.

 The EIR device for quickly verifying the IMEI includes:

 a verification request receiving unit, configured to receive an IMEI verification request message from the MSC/SGSN; wherein The IMEI check request message carries at least one IMEI of the mobile device and the current ES;

 a verification request decoding unit, configured to decode information carried in the IMEI verification request message;

 A list of local mobile devices that hold records received from CEIR;

 a mobile device list management unit, configured to manage the local mobile device list;

An identifier checking unit is connected to the check request decoding unit, configured to query whether there is a data record in the local mobile device list that matches the mobile device information decoded by the check request decoding unit, and The ES in the data record is used as a check result, and if the data record only relates to the mobile device, triggering the mobile device list management unit to delete the data record; otherwise directly decoding the current ES As a result of the verification;

 a verification response coding unit, coupled to the identity verification unit, for encoding the verification result into the IMEI verification response message;

 a verification response sending unit, configured to send the IMEI check response message to the MSC/SGSN;

a mobile device information update request encoding unit, coupled to the verification request decoding unit, configured to encode the information decoded by the verification request decoding unit into a mobile device information update request message;

 a mobile device information update request sending unit, configured to send the mobile device information update request message to the CEIR;

 a mobile device information update response receiving unit for using the CEIR Receiving a first mobile device information update response message, or further receiving a second mobile device information update response message; the first mobile device information update response message carrying the IMEI according to a predetermined rule The information extracted in the central database, the second mobile device information update response message indicating normal reception of the mobile device information update request message;

a mobile device information update response decoding unit, configured to decode the first or second mobile device information update response message, if the first mobile device information update response message is triggered, trigger the mobile device list management unit to edit the mobile device for A piece of data record in the list of local mobile devices.

 The CEIR device for quickly verifying the IMEI includes:

 Mobile device information update request receiving unit for receiving from EIR Mobile device information update request message, wherein the mobile device information update request message carries at least one IMEI of the mobile device and the current ES;

 a mobile device information update request decoding unit, configured to decode information carried in the mobile device information update request message;

 IMEI central database for storage of mobile device information;

 An IMEI central database management unit for providing a human machine interface to manage the IMEI Mobile device information stored in the central database;

 An update processing unit, coupled to the mobile device information update request decoding unit, the IMEI central database, for Querying, in the IMEI central database, the ES of the mobile terminal, and sending it to the mobile device list remote management unit together with the ES decoded in the mobile device information update request message; Updating information related to the mobile terminal in the IMEI central database according to the mobile device information update request message;

 a mobile device list remote management unit, coupled to the update processing unit, for receiving two ESs from the update processing unit Compare; if not, extract information from the IMEI central database according to predetermined rules And triggering the mobile device information update response coding unit; if consistent, or directly triggering the mobile device information update response coding unit;

 a mobile device information update response encoding unit, configured to trigger according to the mobile device list remote management unit, if the presence Generating the first mobile device information update response message according to the information extracted from the IMEI central database according to a predetermined rule; otherwise, or generating a second mobile device information update response message; The first mobile device information update response message carries information extracted from the IMEI central database according to a predetermined rule, and the second mobile device information update response message indicates Normal reception of the mobile device information update request message;

 a mobile device information update response sending unit for using the EIR Sending the first or second mobile device information update response message for subsequent verification use.

 The technical solution provided by the present invention uses the received mobile device information for the next IMEI check , avoiding real-time remote query during the verification process, effectively improving the time response index, achieving the purpose of quickly verifying IMEI and reducing construction costs; Only the mobile device whose previous device status changed is updated, which saves system resources; and the description of the local mobile device list in the EIR device is deleted immediately after use, which not only further improves IMEI The speed of verification can also avoid the use of large database software, thus achieving the purpose of reducing construction costs.

A series of simplified forms of concepts are introduced in the Summary of the Invention section, which will be described in further detail in the Detailed Description section. The summary is not intended to limit the key features and essential technical features of the claimed invention, and is not intended to limit the scope of protection of the claimed embodiments.

 Advantages and features of the present invention are described in detail below with reference to the accompanying drawings.

DRAWINGS

 Figure 1 is a flow chart of IMEI request and verification;

 Figure 2 is a flow chart of authentication encryption and IMEI verification;

 Figure 3 is a flow chart of IMEI verification by CEIR;

 4 is a flowchart of quickly verifying an international mobile device identifier in an embodiment of the present invention;

 FIG. 5 is a flowchart of processing an MSC according to an embodiment of the present invention;

 6 is a flowchart of processing of an SGSN in an embodiment of the present invention;

 7 is a flow chart of EIR processing in an embodiment of the present invention;

 8 is a flowchart of CEIR processing in an embodiment of the present invention;

 9 is a general structural diagram of a system in an embodiment of the present invention;

 10 is a system structural diagram of an MSC/SGSN in an embodiment of the present invention;

 11 is a system structural diagram of an EIR in an embodiment of the present invention;

 Figure 12 is a system configuration diagram of CEIR in the embodiment of the present invention.

detailed description

In the following description, numerous specific details are set forth in the However, it will be apparent to those skilled in the art that the present invention may be practiced without one or more of these details. In other instances, some of the technical features well known in the art have not been described in order to avoid confusion with the present invention.

It is apparent that the practice of the present invention is not limited to the specific details familiar to those skilled in the art. The preferred embodiments of the present invention are described in detail below, but the present invention may have other embodiments in addition to the detailed description.

 In accordance with the present invention, a method of quickly verifying an international mobile device identity is provided. The technical principle of the present invention is: performing IMEI verification EIR decomposes the IMEI check into ES change identification and ES update. In a single IMEI check for a specific mobile device, only one of the phases is performed; that is, EIR is at a certain time. The ES change for a particular mobile device identified in the IMEI check will be updated in the next IMEI check for that particular mobile device.

 According to the above technical principle, the present invention provides a method for quickly verifying an international mobile device identity, comprising the following steps:

 Step 1: The EIR receives the IMEI for the MSC/SGSN for a mobile device. After verifying the request message, querying whether there is a data record matching the mobile device in the local mobile device list, and returning the ES determined according to the data record as a check result to the MSC/SGSN And deleting the data record from the local mobile device list if the data record only relates to the mobile device; otherwise returning directly to the current ES as the check result in the IMEI check request message MSC/SGSN; wherein the IMEI check request message carries at least the IMEI of the mobile device and the current ES, and preferably, further includes IMSI and MSISDN Information such as will be described below;

 Step 2: EIR to CEIR Sending a mobile device information update request message; wherein the mobile device information update request message carries information extracted from the IMEI check request message, including the IMEI of the mobile device and the current ES , preferably, also includes information such as IMSI and MSISDN;

 Step 3: The CEIR sends the ES and the IMEI carried in the mobile device information update request message. The ES of the corresponding mobile device stored in the central database is compared; if not, the EIR is Returning a first mobile device information update response message carrying information extracted from the IMEI central database according to a predetermined rule; if consistent, or also to the EIR Returning to the second mobile device information update response message, the second mobile device information update response message indicating normal reception of the mobile device information update request message; Returning the second mobile device information update response message is not a necessary step, and a person skilled in the art may return no information or periodically return information indicating normal reception according to actual needs, since it does not substantially affect the technical solution of the present invention. This will not be repeated here;

 Step four: EIR After receiving the first mobile device information update response message, edit it as a data record in the local mobile device list; of course, those skilled in the art can understand that if EIR Receiving the returned second mobile device information update response message, no action is required.

It can be seen that, because the present invention adopts the method of first identifying and re-updating, the identification result of the current check is used for the next check to replace the recognition result of the current check in the prior art for the current check. So every IMEI In the verification, there is no need to wait for the response of the CEIR, but it can immediately return a verification result to the MSN/SGSN, so the response time is determined and immediate, which substantially shortens the verification process and improves the verification efficiency;

 And, the present invention uses the identification result of the current verification for the next verification, so that the EIR has a comfortable time (ie, two IMEIs). Verifying the time between requests) to query CEIR's IMEI central database, thus reducing the performance requirements for EIR equipment and CEIR equipment in terms of processing speed and reducing construction costs;

 At the same time, the present invention adopts the method of identifying and updating again, and only updates the mobile device whose ES changes, avoiding the existing IMEI. A large number of repeated and unnecessary updates to the ES of the mobile device in the verification technology, saving system resources;

 In addition, since most data records (ie data records involving only individual units of mobile devices) are available from EIR after use Deleted, so the local mobile device list stored by the EIR device in the present invention is generally in a state close to the empty table; on the one hand, this makes the MSC/SGSN from the EIR in the IMEI check process of the present invention. The time interval between the device receiving the verification request and the verification response is relatively fixed and far lower than the existing IMEI verification technology, further improving the speed of the IMEI check; on the other hand, making the EIR The list of local mobile devices stored by the device is generally short, which avoids the use of large database software, thereby reducing the construction cost;

 Of course, the improvement measures taken by the present invention to update the ES change identified in the verification at the next verification will undoubtedly result in The delay in the effective time of the IMEI check. However, in the actual network environment, the frequency of IMEI verification for mobile devices is high, and it can reach 1~2 per hour during busy hours (the period with the highest traffic volume). At the same time, the ES change cycle for mobile devices often reaches months or longer. Considering IMEI The uncertainty of the triggering event (such as user boot, location update, etc.) itself is checked, and the delay caused by the above improvement measures at the effective time of the verification result is generally acceptable.

The above technical solutions are further refined and optimized in combination with the exemplary parameters, so that those skilled in the art can more easily grasp the features and advantages of the present invention, but the exemplary parameters are not limited to the technical solutions of the present invention.

 In one embodiment, as an optimization of the method provided by the present invention, as previously described, in IMEI The verification request message and the mobile device information update response message may further carry the IMSI and/or MSISDN of the mobile device to implement blocking of the illegal mobile terminal that copies the IMEI;

 In particular, the prior art passes on IMSI and / or MSISDN The first check to exclude the cottage, get the first check result and then enable EIR for IMEI Verification, that is, there are two verification wait problems, not only the response time is greatly prolonged, but also the system resources are occupied more seriously, and the cost of the IMEI check is further pushed up;

 The present invention is capable of verifying IMSI and / or MSISDN with IMEI The verification synchronization is performed, and the present invention provides a corresponding technical solution, wherein the information extracted from the IMEI central database according to a predetermined rule in the third step may include:

 The information extracted by TAC is at least the ES under the corresponding index;

 The information extracted by IMEI is at least the ES under the corresponding index;

 The information extracted by <IMEI, IMSI> is at least the ES under the corresponding index;

 The information extracted by <IMEI, MSISDN> is at least the ES under the corresponding index. ;

 Information extracted with <IMEI, IMSI, MSISDN> as an index, including at least ES under the corresponding index;

 Information extracted with <IMEI , ~IMSI> as an index: or

 Information extracted with <IMEI , ~MSISDN> as the index;

 According to which kind or which rules are used for information extraction, CEIR The maintainers (generally network operators) are controlled according to actual needs. In fact, CEIR's IMEI central database is also managed by the maintainer;

 Therefore, in general, step 3 also includes the IMEI. The central database updates the information related to the mobile terminal according to the mobile device information update request message, for example, using information extracted from the mobile device information update request message, such as receiving an IMEI Verifying the time of the message, the source of the IMEI check message, and possibly the IMSI, MSISDN, etc., updating the corresponding records in the IMEI central database related to the IMEI;

 For example, there may be a mobile device information update request message at IMEI. If the possibility of corresponding mobile device is not found in the central database, the maintainer can be notified by prompt or other means, and the maintainer adds data information and determines the corresponding ES.

Based on the above embodiments, those skilled in the art can understand that since the information carried in the first mobile device information update response message in step 3 will be edited as a data record, the next IMEI for the mobile device Checking, so in the next round of IMEI check, it is queried whether there is a data record matching the mobile device in the local mobile device list, and the device status determined according to the data record is ES. The step of returning to the MSC/SGSN as a result of the verification may include:

 Querying the list of local mobile devices;

 On the one hand, if there is TAC, IMEI, <IMEI on the mobile device, IMSI>, <IMEI, MSISDN> or <IMEI, IMSI, MSISDN> for indexed data records And returning the ES in the data record to the MSC/SGSN as a check result; specifically, the following may be included:

 (1) If there is a data record indexed by the mobile device's TAC, ie at IMEI If the TAC of the mobile device involved in the verification process is the same as the index value of this record, the ES in this record is used as the verification result; thus, network access control based on the ME model can be implemented;

 (2) If there is a data record indexed by the IMEI of the mobile device, ie if IMEI If the IMEI of the mobile device involved in the verification process is the same as the index value of this record, the ES in this record is used as the verification result; thus, based on a single ME The network access control of the individual unit can be deleted after use; the goal is to verify the mobile device whose IMEI has not been illegally copied;

 (3) If there is a data record indexed by <IMEI, IMSI> of the mobile device That is, if the IMEI and IMSI of the mobile device involved in the IMEI verification process are the same as the index value of this record, the ES in this record is used as the verification result; thus, based on a single ME The network access control of individual units can be deleted after use; the target is a mobile device whose IMEI may have been illegally copied, and its current user can be a legitimate mobile user or a specific illegal mobile user (via IMSI) Marked), so that the IMSI checksum can be synchronized with the IMEI check;

 (4) If there is an <IMEI with the mobile device, MSISDN > For the data record of the index, ie if the IMEI and MSISDN of the mobile device involved in the IMEI verification process are the same as the index value of this record, the ES in this record will be As a result of the verification; thus, network access control based on a single ME individual unit can be realized, and can be deleted after use; the target is IMEI A mobile device that may have been illegally copied, whose current user can be a legitimate mobile user or a specific illegal mobile user (marked by MSISDN), so that the MSISDN checksum and IMEI can be performed. Verify the synchronization;

 (5) If there is an <IMEI, IMSI, MSISDN with the mobile device> For the data record of the index, ie if the IMEI, IMSI and MSISDN of the mobile device involved in the IMEI verification process are the same as the index value of this record, the ES in this record will be As a result of the verification; thus, network access control based on a single ME individual unit can be realized, and can be deleted after use; the target is IMEI Mobile devices that may have been illegally copied, whose current users are legitimate mobile users or specific illegal mobile users (as indicated by IMSI and MSISDN), thus enabling IMSI and The verification of the MSISDN is performed synchronously with the IMEI check;

 On the other hand, if there is <IMEI, ~IMSI> with the mobile device or <IMEI, ~MSISDN> is the data record of the index, ie there is such a data record, indexing the IMEI of the data record with the IMEI of the mobile device The same, but the IMSI or MSISDN indexing the data record is different from the IMSI or MSISDN of the mobile device; then it is identified whether there is an ES in the data record, and then The ES in the data record is returned to the MSC/SGSN as a check result, otherwise it is blacklisted as a check result and returned to the MSC/SGSN. Specific can include the following:

 (6) If there is a data record indexed by <IMEI, ~IMSI> of the mobile device, That is, if the IMEI of the mobile device involved in the IMEI verification process is the same as the IMEI value in the record index but the IMSI value is different from the IMSI value in the record index, if there is an ES in the record , the ES in the record is used as the check result, otherwise, it is blacklisted as the check result; thus, network access control based on multiple ME individual units can be realized; the target is IMEI The mobile device that may have been illegally copied but the current user is not a legitimate mobile user (marked as a legitimate user by IMSI), so that the IMSI checksum can be synchronized with the IMEI check.

 (7) If there is an <IMEI with the mobile device, ~ MSISDN > For the indexed data record, the IMEI of the mobile device involved in the IMEI check process is the same as the IMEI value in the record index but the MSISDN and the MSISDN in the record index If the value is different, if the ES exists in the record, the ES in the record is used as the check result. Otherwise, the blacklist status is used as the check result; thus, based on multiple MEs Network access control for individual units; the goal is that the IMEI may have been illegally copied and the current user is not a legitimate mobile user (marked by the MSISDN as a legitimate user, not a) mobile device, and thus The IMSI checksum is synchronized with the MSISDN checksum;

 Those skilled in the art can understand that when CEIR When the maintainer receives multiple replication reports for a legitimate mobile device, the information of the legitimate mobile device can be set in the IMEI according to the above rules (6)(7). In the central database, the identification and processing of multiple illegal mobile users is realized; thus, the IMEI and the corresponding information are respectively set for each cottage, which can effectively reduce the workload of the CEIR maintainer;

 It can also be seen from the above cases (1) to (7) that when the IMEI check request message carries only the mobile device For IMEI and current device status ES, (1) and (2) apply; when the IMEI check request message carries IMSI and / or MSISDN information, it can be applied accordingly ( 1)~(7), wherein (3)~(7) can realize synchronous verification for the cottage machine; and, (1), (6) and (7), that is, TAC, <IMEI, ~IMSI>, <IMEI, ~MSISDN> The data records for the index involve individual units of multiple mobile devices, and should not be EIR after completing the verification of the target device. Removed from the list of local mobile devices.

 And the foregoing technical solution may divide the local mobile device list in the EIR into multiple sub-tables for storage and management according to the index type; Of course, the above cases (1)-(7) are only examples, and those skilled in the art can also perform verification of other mobile terminal information synchronously; but in any case, since there is no MSC/SGSN Waiting for the problem of verifying information, so it will not cause an increase in response time, and there will be no resource occupation and cost increase caused by multiple information interactions.

 Further, those skilled in the art can understand that in the present invention, EIR The list of local mobile devices stored by the device is no longer a whitelist, graylist, blacklist, or unknown device list in the traditional sense, but a list of instructions for updating the current ES of the mobile device, that is, EIR from CEIR. The received management command for the mobile device can be further understood as a certain mobile device that meets the preset rule as an ES directly specified in the command or an ES that can be determined according to the command. , for example, being whitelisted, grayed out, blacklisted, and unknown, etc.;

 Further, those skilled in the art can apply the prior art to the technical solution of the present invention, for example, MSC/SGSN Performing network access control on the mobile device according to the received verification result, that is, determining whether to allow the mobile device to access the network according to the received verification result;

 However, in some cases, in order to adapt to the characteristics of the present invention, it is necessary to appropriately adjust the prior art, for example:

 Those skilled in the art will of course understand that MSC/SGSN Upon receiving a trigger message such as a mobile device boot or location update, the information is obtained and encoded to generate an IMEI check request message and sent to the EIR; however, since the present invention encodes the current ES together to the IMEI In the verification request message, even the IMEI check request message may include information such as IMSI and MSISDN, so the MSC/SGSN Adaptation adjustment is also required in the encoding process; specifically, the IMEI verification request message is generated according to the 3GPP protocol standard, and the ES can be directly directly carried only when the current ES information is carried. The information is encoded into the extended container parameters that meet the 3GPP protocol standard. When IMSI, MSISDN, etc. are added, IMSI and MSISDN can be added. The information is encoded together into an extended container parameter that satisfies the 3GPP protocol standard;

 Similarly, the EIR needs to decode the received IMEI check request message before performing a local mobile device list query. The codec operation of the check result between the EIR and the MSC/SGSN and the codec operation in the interaction between the EIR and the CEIR are also omitted here.

The present invention is exemplarily described in the following by means of specific embodiments, so that those skilled in the art can more clearly understand the process of the method provided by the present invention, but by way of example and not limitation.

 After the MSC/SGSN receives the trigger message of the IMEI check, the standard message specified in the 3GPP protocol Add the current ES of the mobile device to the 'Check IMEI' message, or further increase the parameters such as IMSI and MSISDN to expand to 'Extended Check The IMEI' message is sent to the EIR; the EIR receives the 'Extended Check IMEI' After the message, query the locally stored list of mobile devices. If there is a data record matching the device, the ES determined according to the data record is used as a check result, otherwise the current ES is As a result of the check, the check result is then encoded as an 'Extended Check IMEI Ack' message to the MSC/SGSN; MSC/SGSN Determine whether to allow the mobile device to access the network according to the received verification result; EIR will include the IMEI, ES included in the received 'Extended Check IMEI' message And possible parameters such as IMSI and MSISDN are sent to CEIR in the form of 'Update ME Info Request' message; CEIR will receive the ES Compare with the ES of the corresponding mobile device stored in the IMEI central database to determine whether to update the list of mobile devices stored in the EIR, and if necessary to update the update instructions to 'Update ME Info Response' message and sent to EIR; EIR receives 'Update ME Info Response' Messages and updates to the list of local mobile devices; the maintainer of the CEIR updates the IMEI central database with the received information, such as the time of receiving the IMEI check message, IMEI Verify the source of the message and possible IMSI, MSISDN, etc.

 4 shows a flow chart of a method provided by the present invention according to the above embodiment, comprising the following steps:

 Step S401, the MSC/SGSN sends an 'Extended Check to the EIR. IMEI' request message, which is attached to the current ES of the mobile device based on the original 'Check IMEI' message. Preferably, it may further include IMSI and MSISDN. Information such as the current ES is stored in the VLR ( Visit Location Register) or SGSN, MSC/SGSN Can be easily obtained;

 Step S402, the EIR queries the local mobile device list, If there is a data record matching the mobile device in the local mobile device list, the final ES is set according to the list requirement, otherwise the current ES is kept unchanged, and the EIR takes the obtained ES as the verification result. The 'Extended Check IMEI Ack' message is sent to the MSC/SGSN, MSC/SGSN Determining whether the mobile device is allowed to access the network according to the received verification result;

 Step S403, EIR sends 'Update ME Info Request' to CEIR Message, transmitting IMEI, current ES and possible IMSI, MSISDN and other mobile device related information to CEIR;

 Step S404, CEIR receives 'Update ME Info Request' Message and compare the ES information in the message with the ES information in the IMEI central database to determine if the corresponding IMEI ES in the EIR should be updated If an update is not required, send an 'Update ME Info Response' message indicating normal reception to the EIR and end the process, otherwise the send contains the EIR for update The 'Update ME Info Response' message of the instruction in the mobile device list is given to EIR. In general, it is the ES that will be queried from the IMEI central database. And the identification information for the mobile device is encoded as a mobile device information update response message 'Update ME Info Response' as an update command to the EIR.

 As a further refinement, the following examples are respectively for MSC, SGSN, EIR and CEIR in the above embodiments. The specific processing flow of the device is described separately.

 Refer to Figure 5 for the specific processing flow in the MSC device:

 Step S501, receiving an IMEI check trigger event, such as an identification request, an authentication encryption, or the like;

 Step S502, checking whether the IMEI verification process is started, and if not, ending the process;

 Step S503, acquiring IMEI, ES, and possible IMSI, MSISDN related to the mobile device. Information

 Step S504, setting an 'Extended Check IMEI' message: according to the 3GPP protocol The MAP_CHECK_IMEI primitive encodes IMEI as a standard 'Check IMEI' message, with possible additional information such as ES and IMSI, MSISDN, etc. The form of extensionContainer/ privateExtensionList/extId is encoded into MAP_CHECK_IMEI In the extension container of the primitive, where each extId can include up to 16 2-byte integers, encoded in ASN.1 mode;

 Step S505, sending an 'Extended Check IMEI' message to the EIR;

 Step S506, waiting for 'Extended Check IMEI Ack' from EIR Message

 Step S507, receiving 'Extended Check IMEI Ack' from EIR Message

 Step S508, according to 'Extended Check IMEI Ack' The check result in the message determines whether the mobile device is allowed to access the network.

 Refer to Figure 6 for the specific processing flow in the SGSN device:

 Step S601, receiving an IMEI check trigger event, such as an identification request, an authentication encryption, or the like;

 Step S602, checking whether the IMEI verification process is started, and if not, ending the process;

 Step S603, acquiring IMEI, ES, and possible IMSI, MSISDN related to the mobile device. Information

 Step S604, setting an 'Extended Check IMEI' message: according to the 3GPP protocol The MAP_CHECK_IMEI primitive encodes IMEI as a standard 'Check IMEI' message, with possible additional information such as ES and IMSI, MSISDN, etc. The form of extensionContainer/ privateExtensionList/extId is encoded into MAP_CHECK_IMEI In the extension container of the primitive, where each extId can include up to 16 2-byte integers, encoded in ASN.1 mode;

 Step S605, sending an 'Extended Check IMEI' message to the EIR;

 Step S606, waiting for 'Extended Check IMEI Ack' from EIR Message

 Step S607, receiving an 'Extended Check IMEI Ack' from the EIR Message

 Step S608, according to 'Extended Check IMEI Ack' The check result in the message determines whether the mobile device is allowed to access the network.

 Refer to Figure 7 for the specific processing flow in the EIR device:

 Step S701, receiving an 'Extended Check IMEI' message;

 Step S702, decoding the received 'Extended Check IMEI' message, parsing out IMEI, ES and possible parameters such as IMSI and MSISDN;

 Step S703, querying a local mobile device list;

 Step S704 If the local mobile device list contains the data record that matches the current mobile device, the ES of the current mobile device needs to be changed, and the process goes to step S706;

 Step S705, using the ES parsed from the 'Extended Check IMEI' message As a result of the verification, the process proceeds to step S707;

 Step S706: Determine a final ES according to a query result of the local mobile device list, and use the verification result as a check result.

 Step S707, encoding the verification result as 'Extended Check IMEI Ack' Sending a message to the MSC/SGSN;

 Step S708, sending 'Update ME Info Request' to the CEIR Message, which contains information such as IMEI, current ES, and possible IMSI, MSISDN;

 Step S709, waiting for 'Update ME Info Response' from CEIR Message

 Step S710, receiving 'Update ME Info Response' from CEIR Message

 Step S711, from 'Update ME Info Response' Parse out all the parameters contained in the message;

 Step S712, if 'Update ME Info Response' The message does not include an instruction to update the local mobile device list, and the process ends.

 Step S713, if 'Update ME Info Response' The message contains an instruction to update the local mobile device list, then the 'Update ME Info Response' The information carried in the message is edited as a data record in the local mobile device list, and an update to the local mobile device list is implemented;

 It should be noted that the above steps are described based on the EIR IMEI verification process for a mobile device, when EIR At the same time, when IMEI check is performed for multiple mobile devices, the 'Update ME Info Request' message will carry information of multiple mobile devices, and 'Update ME The Info Response' message may also include update instructions for multiple mobile devices, in which case multiple data records in the local mobile device list will be edited simultaneously.

 Refer to Figure 8 for the specific processing flow in the CEIR device:

 Step S801, receiving an 'Update ME Info Request' message from the EIR;

 Step S802, parsing the 'Update ME Info Request' message, obtaining IMEI, current ES and possible IMSI, MSISDN and other information;

 Step S803, querying the IMEI central database to obtain IMEI, ES and possible related to the mobile device Information such as IMSI and MSISDN;

 Step S804, the message from the 'Update ME Info Request' and the IMEI The ES of the central database is compared;

 Step S805, judging whether it is necessary to update the EIR according to the comparison result. The list of mobile devices stored in the file, if no update is required, then proceeds to step S807;

 Step S806, according to a predetermined rule from the IMEI Extract the information from the central database and use it as an update command. For the above-mentioned predetermined rules, please refer to the above information extraction method, for example, TAC, IMEI, <IMEI, IMSI>, <IMEI, MSISDN>, <IMEI, IMSI, MSISDN>, <IMEI, ~IMSI>, <IMEI, ~MSISDN> is an index, but is not limited to the above extraction method;

 Step S807, encoding 'Update ME info Response' The message, the encoding object is either an update instruction obtained based on step S806, or a result of receiving the 'Update ME Info Request' message based on step S805;

 Step S808, sending an 'Update ME Info Response' message to the EIR.

 In addition, it also includes the update steps of the IMEI central database, ie from 'Update ME Info Information extracted from the Request' message, such as the time when the IMEI check message was received, the source of the IMEI check message, and possible IMSI, MSISDN, etc., to IMEI The records related to the IMEI in the central database are updated (not shown).

 According to the present invention, there is also provided a system for quickly verifying IMEI, and the overall structure of system 900 is as shown in FIG. Included are CEIR device 910, EIR device 920, MSC device 930, and SGSN device 940. The quick check is performed by a specific embodiment below. The IMEI system 900 describes:

 MSC device 930 or SGSN device 940 receives IMEI for a mobile device After the triggered trigger message, the mobile device's current ES and possible IMSI, MSISDN and other information are extendedContainer/ The privateExtensionList/extId method extends the standard 'Check IMEI' message and the resulting 'Extended Check' The IMEI' message is sent to the EIR device 920; the EIR device 920 parses the IMEI of the mobile device from the 'Extended Check IMEI' message , current ES and possible IMSI, MSISDN And parameterizing, and querying the locally stored list of mobile devices; if there is no data record matching the mobile device in the local mobile device list, for example, there is no IMEI with the mobile device For the indexed record, the current ES of the mobile device is used as a check result; otherwise, the ES determined according to the corresponding data record of the local mobile device list is used as a check result; on the one hand, the above check result is passed An 'Extended Check IMEI Ack' message is sent to the MSC device 930 or SGSN device 940; on the other hand, If the data record of the local mobile device list relates to only a single device, ie, the mobile device that requests the IMEI check, the data record is deleted; and the EIR device 920 will IMEI The current ES and possible IMSI, MSISDN and other information are encoded as 'Update ME Info Request' message and sent to the CEIR device 910; The CEIR device 910 parses out the IMEI, the current ES, and the possible IMSI, MSISDN from the 'Update ME Info Request' message. And other parameters; the CEIR device 910 obtains IMEI, ES and possible IMSI, MSISDN and other information corresponding to the mobile device from the IMEI central database query; The CEIR device 910 pairs the ESs contained in the received 'Update ME Info Request' message with the ESs queried from the IMEI central database. For comparison, if they are inconsistent, the mobile device list in the EIR device 920 needs to be updated, and the information extracted from the IMEI central database according to the predetermined rule is used as the update command and the pair. The result of receiving the 'Update ME Info Request' message is encoded into the 'Update ME Info Response' message and sent to the EIR device. 920, otherwise, the result of receiving the 'Update ME Info Request' message is encoded into 'Update ME info Response' The message is sent to the EIR device 920;

 The information extracted by the CEIR device 910 from the IMEI central database according to a predetermined rule may include:

 The information extracted by TAC is at least the ES under the corresponding index;

 The information extracted by IMEI is at least the ES under the corresponding index;

 The information extracted by <IMEI, IMSI> is at least the ES under the corresponding index;

 The information extracted by <IMEI, MSISDN> is at least the ES under the corresponding index. ;

 Information extracted with <IMEI, IMSI, MSISDN> as an index, including at least ES under the corresponding index;

 Information extracted with <IMEI , ~IMSI> as an index: or

 Information extracted with <IMEI , ~MSISDN> as the index;

 And the ES recorded in the EIR local mobile device list and stored in the IMEI central database of the CEIR ES includes: whitelisted, graylisted, blacklisted, and unknown; in particular, the EIR local mobile device list remains close to the empty table for most of the time, thus ensuring The interval between the 'Extended Check IMEI' message and the 'Update ME Info Request' message is relatively fixed and much lower than other common IMEIs. Calibration technique

 At the same time, due to the introduction of IMSI and MSISDN data, it is possible to synchronize IMEI for illegal replication. Identification of mobile devices.

 The system 900 for quickly verifying the IMEI is described below by way of a specific embodiment. The detailed description is intended to be illustrative, and not restrictive.

 As shown in FIG. 10, the MSC device 9930/SGSN device 940 further includes: a data acquisition unit. 1001, verification request encoding unit 1002, verification request transmitting unit 1003, verification response receiving unit 1004, verification response decoding unit 1005, and network access control unit The data obtaining unit 1001 is configured to acquire information about an IMEI, a current ES, and a possible IMSI, MSISDN, and the like of the corresponding mobile device; the verification request coding unit 1002, used to encode the ES and possible IMSI, MSISDN and the like together with the IMEI into the IMEI check request message, and the specific coding mode is preferably according to 3GPP. The protocol standard encodes the obtained information into an IMEI check request message; the check request sending unit 1003 is configured to send the IMEI check request message to the EIR device 920. The check response receiving unit 1004 is configured to receive an IMEI check response message carrying the check result from the EIR device 920; the check response decoding unit 1005 is configured to The verification result is decoded in the IMEI check response message; the network access control unit 1006 is configured to perform network access control on the mobile device according to the check result.

 As shown in FIG. 11, the EIR device 920 further includes: a verification request receiving unit 1101. a verification request decoding unit 1102, a local mobile device list 1103, a mobile device list management unit 1104, an identity verification unit 1105, and a verification response coding unit 1106 a verification response sending unit 1107, a mobile device information update request encoding unit 1108, a mobile device information update request transmitting unit 1109, and a mobile device information update response receiving unit 1110 And a mobile device information update response decoding unit 1111; the verification request receiving unit 1101 is configured to receive an IMEI from the MSC device 930/SGSN device 940 a verification request decoding unit 1102, configured to decode information carried in the IMEI verification request message, such as IMEI, current ES, and possible IMSI, Information such as MSISDN; the local mobile device list 1103 for storing records received from the CEIR device 910; the mobile device list management unit 1104 For managing the local mobile device list, the identifier verification unit 1105 is connected to the verification request decoding unit 1102, and is used to query whether the local mobile device list exists. The data record matching the mobile device is an ES determined according to the data record as a check result, and if the data record only relates to the mobile device, triggering the mobile device list management unit 1104 Deleting the data record; otherwise, directly using the decoded current ES as a check result, simply speaking, according to the current ES carried in the IMEI check request message As a check result, the check response coding unit 1106 is connected to the identifier check unit 1105, and is configured to encode the check result into the IMEI check response message; the check response sending unit 1107, configured to send the IMEI check response message to the original MSC device 930 or the SGSN device 940; the mobile device information update request coding unit 1108, And connected to the verification request decoding unit 1102, for decoding information that the verification request decoding unit 1102 decodes, such as IMEI, current ES, and possible IMSI, Mobile device information such as MSISDN is encoded into an 'Update ME Info Request' message; the mobile device information update request sending unit 1109 is configured to An 'Update ME Info Request' message is sent to the CEIR device 910; the mobile device information update response receiving unit 1110 is used to slave the CEIR device 910 receives an 'Update ME Info Response' message, and the 'Update ME Info Response' message carries a representation of CEIR The information that the device 910 receives the result of the 'Update ME Info Request' message may also carry an update instruction to the local mobile device list. The mobile device information update response decoding unit 1111 is configured to parse the information carried by the 'Update ME Info Response' message, If the update command for the local mobile device list is carried, the mobile device list management unit 1104 is triggered to edit it as the data record in the local mobile device list 1103;

 The query verification unit 1105 querying the local mobile device list specifically includes:

 The identity verification unit 1105 queries the local mobile device list 1103;

 If there is TAC, IMEI, <IMEI, IMSI> of the mobile device, <IMEI, MSISDN> or <IMEI, IMSI, MSISDN> is the indexed data record, then the ES in the data record As a result of the verification, the verification response encoding unit 1106 is triggered;

 If there is <IMEI, ~IMSI> or <IMEI on the mobile device, ~MSISDN> is the data record of the index, that is, there is such a data record, the IMEI indexing the data record is the same as the IMEI of the mobile device, but the data record is indexed The IMSI or MSISDN is different from the IMSI or MSISDN of the mobile device; then it is identified whether there is an ES in the data record, and the ES in the data record is The verification response encoding unit 1106 is triggered as a result of the verification, otherwise the verification response encoding unit 1106 is triggered by being blacklisted as a verification result.

 As shown in FIG. 12, the CEIR device 910 further includes: a mobile device information update request receiving unit 1201. , mobile device information update request decoding unit 1202, update processing unit 1203, IMEI central database 1204, IMEI central database management unit 1205, Mobile device list remote management unit 1206, mobile device information update response encoding unit 1207 and mobile device information update response transmitting unit 1208; mobile device information update request receiving unit 1201, configured to receive an 'Update ME Info Request' message from the EIR device 920; the mobile device information update request decoding unit 1202 For parsing the IMEI, the current ES, and the possible IMSI, MSISDN, and the like from the 'Update ME Info Request' message; The IMEI central database 1204 is used for storage of mobile device information. Specifically, all mobile device information in the CEIR device 910 is stored in the IMEI central database 1203. The IMEI central database 1204 may be a distributed mass database as in the prior art; the IMEI central database management unit 1205, provided with CEIR Maintainer's human-machine interface, enabling maintainers to store mobile device information (IMEI, ES, and possibly IMSI, MSISDN) stored in the IMEI Central Database 1204 And managing; the update processing unit 1203 is connected to the mobile device information update request decoding unit 1202, the IMEI central database 1204, for using the IMEI The central database 1204 queries the ES of the mobile terminal and sends it to the mobile device list remote management unit 1206 along with the ES decoded in the mobile device information update request message. And updating information related to the mobile terminal in the IMEI central database 1204 according to the mobile device information update request message, such as the time when the IMEI check message is received, IMEI Verifying the source of the message and possible IMSI, MSISDN, etc.; the mobile device list remote management unit 1206, connected to the update processing unit 1203, for Compare the two ESs received from the update processing unit 1203, specifically, the ES from the IMEI Central Database 1204 and from the 'Update ME The ES decoded in the Info Request' message, if not consistent, extracts information from the IMEI central database as an update command according to a predetermined rule. And triggering the mobile device information update response coding unit, if consistent, may directly trigger the mobile device information update response coding unit or not take an operation; the mobile device information update response coding unit 1207 is configured to The 'Update ME Info Response' message is encoded according to the trigger of the mobile device list remote management unit 1206, the 'Update ME Info The Response' message may include an update command, or may only include information indicating that the CEIR device 910 normally receives, of course, even if the same mobile terminal is carrying the update command, The 'Update ME Info Response' message can also carry the CEIR device 910 at the same time. The normally received information does not conflict with each other, and the corresponding coding rule may be determined by a person skilled in the art according to actual needs; the mobile device information update response sending unit 1208 is configured to send the EIR device to the EIR device. 920 sends an 'Update ME Info Response' message, the 'Update ME Info Response' message carries the pair 'Update The ME Info Request' message is received and/or an update command to the local mobile device list 1103 in the EIR device 920.

 In addition, the present invention also provides an EIR device and CEIR for quickly verifying IMEI. For the specific structure and working mode of the device, refer to the corresponding part in the system for quickly verifying the IMEI, and details are not described here.

 In summary, according to the technical solution provided by the present invention, there is no need to wait for CEIR in each IMEI check. Response, and can immediately return a verification result to the MSN/SGSN and use the received mobile device information for the next IMEI check, ie at IMEI Real-time remote query is avoided during the verification process, which enables quick verification of IMEI functions and reduces construction costs.

 And, only the mobile devices whose previous device status changes are updated, avoiding the existing IMEI verification technology for mobile devices. Large, repetitive and unnecessary updates by ES save system resources; EIR Only the local mobile device list needs to be stored in the device, and many of the lists only involve the current mobile terminal's data record can be deleted after use, so the list is generally short, not only further improving IMEI The speed of verification can also avoid the use of large database software, thus achieving the purpose of reducing construction costs.

The present invention has been described by the above-described embodiments, but it should be understood that the above-described embodiments are only for the purpose of illustration and description. Further, those skilled in the art can understand that the present invention is not limited to the above embodiments, and various modifications and changes can be made according to the teachings of the present invention. These modifications and modifications are all claimed in the present invention. Within the scope. The scope of the invention is defined by the appended claims and their equivalents.

Claims (1)

What is claimed is: 1. A method for quickly verifying an international mobile device identity, the method comprising the steps of: Step 1: Device Identification Register EIR Received Mobile Service Switching Center MSC/Service GPRS Support Node SGSN International mobile device identity IMEI for a mobile device After verifying the request message, querying whether there is a data record matching the mobile device in the local mobile device list, and returning the device status ES determined according to the data record as a check result to the MSC/SGSN, and if the data record relates only to the mobile device, deleting the data record from the local mobile device list; otherwise directly verifying the current ES in the request message with the IMEI Returning to the MSC/SGSN as a result of the verification; wherein the IMEI check request message carries at least the IMEI of the mobile device and the current ES; Step 2: The EIR to the central device identification register CEIR Transmitting a mobile device information update request message; wherein the mobile device information update request message carries information extracted from the IMEI check request message; Step 3: The CEIR stores the ES carried in the mobile device information update request message with the corresponding mobile device stored in the IMEI central database. The ES compares; if not, returns a first mobile device information update response message to the EIR, the first mobile device information update response message carrying the IMEI according to a predetermined rule Information extracted in the central database; if consistent, or returning a second mobile device information update response message to the EIR, the second mobile device information update response message indicates Normal reception of the mobile device information update request message; Step four: EIR After receiving the first mobile device information update response message, it is edited as a data record in the local mobile device list. The method according to claim 1, wherein the IMEI check request message further carries an international mobile subscriber identity of the mobile device. IMSI and / or mobile subscriber IDSN number MSISDN. The method according to claim 1, wherein the step 3 is performed from the IMEI according to a predetermined rule. The information extracted in the central database includes: The information extracted by TAC is at least the ES under the corresponding index; The information extracted by IMEI is at least the ES under the corresponding index; The information extracted by <IMEI , IMSI > is at least ES under the corresponding index ; The information extracted by <IMEI, MSISDN> is at least the ES under the corresponding index. ; The information extracted by <IMEI, IMSI, MSISDN> is at least the ES under the corresponding index. ; Information extracted with <IMEI , ~IMSI> as an index: or Information extracted with <IMEI , ~MSISDN> as the index. 4, according to claim 3 The method is characterized in that, in step 1, it is queried whether there is a data record matching the mobile device in the local mobile device list, and the device status determined according to the data record is ES. The step of returning to the MSC/SGSN as a check result specifically includes: Querying the list of local mobile devices; If there is TAC, IMEI, <IMEI, IMSI>, <IMEI on the mobile device, MSISDN> or <IMEI, IMSI, MSISDN> is the data record of the index, and the ES in the data record is returned as the check result to the MSC/SGSN ; If there is <IMEI, ~ IMSI > or <IMEI, ~MSISDN> on the mobile device For the indexed data record, ie there is such a data record, the IMEI indexing the data record is the same as the IMEI of the mobile device, but indexing the IMSI or MSISDN of the data record Different from the IMSI or MSISDN of the mobile device; identifying whether an ES exists in the data record, and returning the ES in the data record as a check result to the MSC/SGSN, otherwise returned to the MSC/SGSN with the blacklist status as a check result. The method according to any one of claims 1 to 4, wherein the ES and the CEIR are recorded in the EIR local mobile device list. ESs stored in the IMEI Central Database include: whitelisted, graylisted, blacklisted, and unknown. The method according to any one of claims 1-4, wherein before the step 1, the method further comprises: the MSC/SGSN Upon receiving the mobile device trigger message, the IMEI check request message is generated and sent to the EIR according to the 3GPP protocol standard. The method according to any one of claims 1 to 4, further comprising: after the step one, the MSC/SGSN Performing network access control on the mobile device according to the received verification result. The method according to any one of claims 1 to 4, wherein the step 3 further comprises updating the request according to the mobile device information update request message. The steps in the IMEI central database for information about the mobile terminal. 9. A system for quickly verifying an identity of an international mobile device, comprising a device identification register EIR and a mobile services switching center respectively interacting with the EIR MSC/Service GPRS Support Node SGSN and Central Device Identification Register CEIR, which are characterized by: The MSC/SGSN is configured to send an International Mobile Equipment Identity IMEI Check Request message for the mobile device to the EIR, where The IMEI check request message carries at least the IMEI of the mobile device and the current device status ES; and, receives and according to the EIR Returning a verification result, performing network access control on the mobile device; The EIR is configured to receive the IMEI sent by the MSC/SGSN Checking the request message, querying whether there is a data record matching the mobile device in the local mobile device list, and returning the device status ES determined according to the data record as a check result to the MSC/SGSN, and if the data record relates only to the mobile device, deleting the data record from the local mobile device list; otherwise directly verifying the current ES in the request message with the IMEI Returning to the MSC/SGSN as a check result; transmitting a mobile device information update request message to the CEIR, wherein the mobile device information update request message carries the IMEI from the And verifying the information extracted in the request message; and receiving the first mobile device information update response message returned by the CEIR, editing it as a data record in the local mobile device list; or receiving the The second mobile device information update response message returned by the CEIR; The CEI R is configured to receive a mobile device information update request message sent by the EIR, and send the ES carried in the mobile device information update request message with The ESs of the corresponding mobile devices stored in the IMEI central database are compared; if not, the first mobile device information update response message is returned to the EIR. The first mobile device information update response message carries information extracted from the IMEI central database according to a predetermined rule; if consistent, or also to the EIR Returning to the second mobile device information update response message, the second mobile device information update response message indicating normal reception of the mobile device information update request message. 10. The system of claim 9 wherein: The IMEI check request message also carries an international mobile subscriber identity IMSI and/or a mobile subscriber IDSN number of the mobile device MSISDN. 11. The system of claim 9 wherein: said CEIR is from said IMEI in accordance with a predetermined rule The information extracted in the central database includes: The information extracted by TAC is at least the ES under the corresponding index; The information extracted by IMEI is at least the ES under the corresponding index; The information extracted by <IMEI, IMSI> is at least the ES under the corresponding index; The information extracted by <IMEI, MSISDN> is at least the ES under the corresponding index. ; The information extracted by <IMEI, IMSI, MSISDN> is at least the ES under the corresponding index. ; Information extracted with <IMEI , ~IMSI> as an index: or Information extracted with <IMEI , ~MSISDN> as the index. The system according to any one of claims 9-11, wherein: said ES and said said EIR local mobile device list ESs stored in CEIR's IMEI Central Database include: whitelisted, graylisted, blacklisted, and unknown. The system according to any one of claims 9-11, characterized in that: MSC/SGSN Further includes: a data obtaining unit, configured to acquire at least an IMEI of the mobile device and a current ES, or obtain an IMSI and/or of the mobile device MSISDN ; a verification request encoding unit, configured to encode the obtained information into an IMEI verification request message; a verification request sending unit, configured to send the IMEI check request message to the EIR; a verification response receiving unit, configured to receive, from the EIR, an IMEI verification response message carrying a verification result; a check response decoding unit, configured to decode the check result from the IMEI check response message; And a network access control unit, configured to perform network access control on the mobile device according to the verification result. 14. The system according to claim 13, wherein: said verification request coding unit comprises a 3GPP protocol standard module for The 3GPP protocol standard encodes the obtained information into an IMEI check request message. The system according to any one of claims 9-11, wherein the EIR further comprises: a verification request receiving unit, configured to receive an IMEI verification request message from the MSC/SGSN; a verification request decoding unit, configured to decode information carried in the IMEI verification request message; a list of local mobile devices for storing records received from the CEIR; a mobile device list management unit, configured to manage the local mobile device list; Identification unit And connecting to the check request decoding unit, configured to query, in the local mobile device list, whether there is a data record that matches the mobile device information decoded by the check request decoding unit, and then according to the data Recorded ES as a check result, and if the data record only relates to the mobile device, triggering the mobile device list management unit to delete the data record; otherwise, directly using the decoded current ES as a check result ; a verification response coding unit, coupled to the identity verification unit, for encoding the verification result into the IMEI verification response message; a verification response sending unit, configured to send the IMEI check response message to the MSC/SGSN; a mobile device information update request encoding unit, coupled to the verification request decoding unit, configured to encode the information decoded by the verification request decoding unit into a mobile device information update request message; a mobile device information update request sending unit, configured to send the mobile device information update request message to the CEIR; a mobile device information update response receiving unit for using the CEIR Receiving the first mobile device information update response message, or receiving the second mobile device information update response message; a mobile device information update response decoding unit, configured to decode the first or second mobile device information update response message, if the first mobile device information update response message is triggered, trigger the mobile device list management unit to edit the mobile device for A piece of data record in the list of local mobile devices. 16. The system of claim 15 wherein said identification verification unit Querying the list of local mobile devices specifically includes: The identity verification unit queries the local mobile device list; If there is TAC, IMEI, <IMEI, IMSI>, <IMEI on the mobile device, MSISDN> or <IMEI, IMSI, MSISDN> is an indexed data record, and the ES in the data record is used as a check result, and the Verify response coding unit; If there is <IMEI, ~IMSI> or <IMEI, ~MSISDN> with the mobile device For the indexed data record, ie there is such a data record, the IMEI indexing the data record is the same as the IMEI of the mobile device, but indexing the IMSI or MSISDN of the data record Different from the IMSI or MSISDN of the mobile device; identifying whether an ES exists in the data record, and then using the ES in the data record as a check result and triggering the The response response coding unit is checked, otherwise the verification response coding unit is triggered by being blacklisted as a check result. The system according to any one of claims 9-11, wherein the CEIR further comprises: a mobile device information update request receiving unit, configured to receive a mobile device information update request message from the EIR; a mobile device information update request decoding unit, configured to decode information carried in the mobile device information update request message; IMEI central database for storage of mobile device information; IMEI central database management unit for providing a human machine interface to manage the IMEI Mobile device information stored in the central database; An update processing unit, coupled to the mobile device information update request decoding unit, the IMEI central database, for using the IMEI Querying, in the central database, the ES of the mobile terminal, and sending it to the mobile device list remote management unit together with the ES decoded in the mobile device information update request message; Updating information related to the mobile terminal in the IMEI central database according to the mobile device information update request message; a mobile device list remote management unit coupled to the update processing unit for receiving two ESs from the update processing unit Compare; if not, extract information from the IMEI central database according to predetermined rules And triggering the mobile device information update response coding unit; if consistent, or directly triggering the mobile device information update response coding unit; The mobile device information update response encoding unit is configured to trigger from the IMEI according to the predetermined rule according to the trigger of the mobile device list remote management unit Generating the information in the central database to generate the first mobile device information update response message; otherwise, or generating a second mobile device information update response message; And a mobile device information update response sending unit, configured to send the first or second mobile device information update response message to the EIR. 18. A device identification register device EIR for quickly verifying an identity of an international mobile device, comprising: a verification request receiving unit for receiving an IMEI from the mobile services switching center MSC/serving GPRS support node SGSN Verifying the request message; wherein the IMEI check request message carries at least one mobile device's international mobile device identity IMEI and the current device state ES; a verification request decoding unit, configured to decode information carried in the IMEI verification request message; a list of local mobile devices for storing records received from the central device identification register device CEIR; a mobile device list management unit, configured to manage the local mobile device list; An identifier checking unit is connected to the check request decoding unit, configured to query whether there is a data record in the local mobile device list that matches the mobile device information decoded by the check request decoding unit, and The ES in the data record is used as a check result, and if the data record only relates to the mobile device, triggering the mobile device list management unit to delete the data record; otherwise directly decoding the current ES As a result of the verification; a verification response coding unit, coupled to the identity verification unit, for encoding the verification result into the IMEI verification response message; a verification response sending unit, configured to send the IMEI check response message to the MSC/SGSN; a mobile device information update request encoding unit, coupled to the verification request decoding unit, configured to encode the information decoded by the verification request decoding unit into a mobile device information update request message; a mobile device information update request sending unit, configured to send the mobile device information update request message to the CEIR; a mobile device information update response receiving unit for using the CEIR Receiving a first mobile device information update response message, or further receiving a second mobile device information update response message; the first mobile device information update response message carrying the IMEI according to a predetermined rule The information extracted in the central database, the second mobile device information update response message indicating normal reception of the mobile device information update request message; a mobile device information update response decoding unit, configured to decode the first or second mobile device information update response message, if the first mobile device information update response message is triggered, trigger the mobile device list management unit to edit the mobile device for A piece of data record in the list of local mobile devices. 19. The EIR according to claim 18, wherein said IMEI The verification request message also carries the international mobile subscriber identity IMSI and/or the mobile subscriber IDSN number MSISDN of the mobile device. 20. The EIR of claim 18, wherein said said IMEI is in accordance with a predetermined rule The information extracted in the central database includes: The information extracted by TAC is at least the ES under the corresponding index; The information extracted by IMEI is at least the ES under the corresponding index; The information extracted by <IMEI, IMSI> is at least the ES under the corresponding index; The information extracted by <IMEI, MSISDN> is at least the ES under the corresponding index. ; The information extracted by <IMEI, IMSI, MSISDN> is at least the ES under the corresponding index. ; Information extracted with <IMEI , ~IMSI> as an index: or Information extracted with <IMEI , ~MSISDN> as the index. 21 . The EIR according to claim 20, wherein the identifier verification unit Querying the list of local mobile devices specifically includes: The identity verification unit queries the local mobile device list; If there is TAC, IMEI, <IMEI, IMSI>, <IMEI on the mobile device, MSISDN> or <IMEI, IMSI, MSISDN> is an indexed data record, and the ES in the data record is used as a check result, and the Verify response coding unit; If there is <IMEI, ~IMSI> or <IMEI, ~MSISDN> with the mobile device For the indexed data record, ie there is such a data record, the IMEI indexing the data record is the same as the IMEI of the mobile device, but indexing the IMSI or MSISDN of the data record Different from the IMSI or MSISDN of the mobile device; identifying whether an ES exists in the data record, and then using the ES in the data record as a check result and triggering the The response response coding unit is checked, otherwise the verification response coding unit is triggered by being blacklisted as a check result. The EIR according to any one of claims 18 to 21, wherein the ES and the described in the local mobile device list ESs stored in CEIR's IMEI Central Database include: whitelisted, graylisted, blacklisted, and unknown. 23. A central device identification register device CEIR for quickly verifying an identity of an international mobile device, comprising: a mobile device information update request receiving unit for receiving an EIR from the device identification register Mobile device information update request message, wherein the mobile device information update request message carries at least one mobile device's international mobile device identity IMEI and current device status ES ; a mobile device information update request decoding unit, configured to decode information carried in the mobile device information update request message; IMEI central database for storage of mobile device information; An IMEI central database management unit, configured to provide a human machine interface to manage mobile device information stored by the IMEI central database; An update processing unit, connected to the mobile device information update request decoding unit and the IMEI central database, for obtaining an ES of the mobile terminal from the IMEI central database And transmitting to the mobile device list remote management unit together with the ES decoded in the mobile device information update request message; and updating the IMEI according to the mobile device information update request message Information related to the mobile terminal in the central database; a mobile device list remote management unit, connected to the update processing unit, for comparing two ESs received from the update processing unit; If they are inconsistent, extract information from the IMEI central database according to predetermined rules And triggering the mobile device information update response coding unit; if consistent, or directly triggering the mobile device information update response coding unit; a mobile device information update response encoding unit, configured to trigger from the IMEI according to the mobile device list remote management unit according to a predetermined rule Generating the information in the central database to generate a first mobile device information update response message; otherwise, or generating a second mobile device information update response message; the first mobile device information update response message Carrying information extracted from the IMEI central database according to a predetermined rule, the second mobile device information update response message indicating Normal reception of the mobile device information update request message; a mobile device information update response sending unit for using the EIR Sending the first or second mobile device information update response message for subsequent verification use. The CEIR according to claim 23, wherein said mobile device information update request message It also carries the international mobile subscriber identity IMSI and/or the mobile subscriber IDSN number MSISDN of the mobile device. The CEIR according to claim 23, wherein the mobile device list remote management unit is from the IMEI according to a predetermined rule. The information extracted in the central database includes: The information extracted by TAC is at least the ES under the corresponding index; The information extracted by IMEI is at least the ES under the corresponding index; The information extracted by <IMEI, IMSI> is at least the ES under the corresponding index; The information extracted by <IMEI, MSISDN> is at least the ES under the corresponding index. ; The information extracted by <IMEI, IMSI, MSISDN> is at least the ES under the corresponding index. ; Information extracted with <IMEI , ~IMSI> as an index: or Information extracted with <IMEI , ~MSISDN> as the index. The CEIR according to any one of claims 23-25, wherein the ES stored in the IMEI central database These include: being whitelisted, grayed out, blacklisted, and unknown.

Images