CN102227147B

CN102227147B - Method and system used for corporately verifying international equipment identification

Info

Publication number: CN102227147B
Application number: CN201110165640.4A
Authority: CN
Inventors: 王兰睿; 庞国丽; 陈天; 刘兵
Original assignee: 王兰睿
Current assignee: BEIJING RUIGETE SOFTWARE TECHNOLOGY Co.,Ltd.
Priority date: 2011-06-20
Filing date: 2011-06-20
Publication date: 2013-08-21
Anticipated expiration: 2031-06-20
Also published as: CN102227147A

Abstract

The invention discloses a method, an equipment identity register EIR and a system which are used for corporately verifying an international equipment identification. The method comprises a pal member list is arranged in each EIR to record a list of EIR members which have a pal relation with the EIR; an original EIR identification is configured to the data record of the local mobile list of each EIR to mark the original EIR of the data record; in the execution of a rapid IMEI verification process, when direct changes happen to the local mobile equipment list of some EIR, the EIR synchronizes the direct changes into the local mobile equipment lists of all the members in the pal member list, wherein the direct changes comprise a record addition and/ or a record deletion. According to the invention, a plurality of EIRs possessing pal relations corporately completes the IMEI verification function, the efficacy time index of the IMEI verification result is improved based on fully utilizing the IMEI verification result, system resources are saved and construction costs of the equipment are reduced.

Description

A kind of method and system for collaborative verification International Mobile Station Equipment Identification

Technical field

The present invention relates to moving communicating field, relate in particular to a kind of method, equipment identity register and system for collaborative verification International Mobile Station Equipment Identification.

Background technology

In GSM, WCDMA and TD-SCDMA digital mobile cellular telecommunication net, can be by enabling IMEI (International Mobile station Equipment Identity, International Mobile Station Equipment Identification) verification scheme realizes the mobile device access to netwoks control of (Mobile Equipment is called for short ME).

Be set to prevention faulty equipment and stolen equipment access to mobile network owing to enable the purpose of IMEI verification at first, therefore when IMEI is carried out verification, with IMEI corresponding equipment state (Equipment Status, be called for short ES) be whether legal unique foundation of mobile device, namely usually at EIR(Equipment Identity Register, equipment identity register) in finish the IMEI verification according to equipment state.

Particularly, EIR comprises one or several database that is used for storage IMEI, mainly finishes identification to mobile device, monitors function such as locking.IMEI can be stored in three in white list, gray list and blacklist independently in the tabulation:

● preserve number section that all allow the device identification of use in the white list;

● preserve all in the blacklist by the device identification of locking;

● the not locking of equipment in the gray list, but by Network records (in order to add up and other purposes).

Equipment state refers to the store status of IMEI in EIR, is respectively: be put into white list, be put into gray list, be put on the blacklist and the unknown.

Its concrete checking procedure is as follows:

From MSC(Mobile-service Switch Center, mobile services switching centre)/SGSN(Serving GPRS Support Node, Serving GPRS Support Node) receives " Check IMEI " message, parse IMEI/TAC(Type Allocation Code, the model assigned code), inquiry is that indexed data table (white list, blacklist, gray list etc.) obtains corresponding with it ES with IMEI/TAC, and it is sent it back described MSC/SGSN as the IMEI check results; Wherein, be that the IMEI verification mode of index has realized the access to netwoks control based on the mobile device individual cell with IMEI; Be that the IMEI verification mode of index has then realized the access to netwoks control based on the mobile device model with TAC.

Obviously, above-mentioned IMEI verification scheme can't be taken precautions against IMEI itself by the bootlegging problem: if certain IMEI is legal, then bootlegging the mobile device of this IMEI can be considered to legal equally, and access to mobile network smoothly.

For the above-mentioned IMEI that can't take precautions against that exists in the IMEI verification scheme that solves in standard by the problem of bootlegging, prior art generally can be chosen in standard " Check IMEI " message increases parameter, as IMSI(International Mobile Subscriber Identity, IMSI International Mobile Subscriber Identity), MSISDN(Mobile Subscriber ISDN, mobile subscriber ISDN number) etc., to increase the accuracy of identification to mobile device.

Therefore after improving, EIR finishes the IMEI verification usually in the following way:

From " Check IMEI " message that MSC/SGSN receive to strengthen, parse the tlv triple＜IMEI of mobile device, IMSI, MSISDN〉or binary group information＜IMSI, IMEI〉etc. information; The data query table determines whether whether described IMEI be the legal user of described IMEI by the mobile subscriber of bootlegging and this IMSI or MSISDN representative; According to the identity validation result to described mobile device and user thereof, and the processing rules of the requirement of the validated user of described mobile device (as whether reporting the loss, whether break down etc.) and operator (as forbid or allow bootlegging equipment networking etc.), determine the equipment state that described mobile device is final, and it is sent it back described MSC/SGSN as the IMEI check results;

In above-mentioned IMEI verification mode, EIR equipment is employed to be the mobile device tabulation of expansion, namely adopts IMSI or MSISDN to indicate the validated user of described IMEI corresponding mobile device; If described IMEI is not by bootlegging or used by validated user, then with the equipment state in the mobile device tabulation as check results, and with serve as to control according to this mobile device being carried out access to netwoks; If described IMEI by bootlegging and used by the disabled user, then carries out access to netwoks control according to the rule of operator to this mobile device.

As can be seen, strengthen by above-mentioned " Check IMEI " message to standard, can make EIR possess the IMEI of strick precaution by the function of bootlegging; Even existed the mobile device (Gray Handset, i.e. so-called " mountain vallage machine ") that uses bootlegging IMEI in the network in a large number, still can enable the IMEI verifying function; Like this, by guiding " becoming a full member " process in advance, gradually reduce " mountain vallage machine " in the netting index amount, enable the IMEI verification to " mountain vallage machine " again, can eliminate IMEI to greatest extent by the bootlegging phenomenon, improve identifiability and the serviceability of mobile device.

When in relatively large network, enabling the IMEI verifying function, for solving EIR networking problem, generally can be equipped with CEIR(Central Equipment Identity Register, the central equipment marker register) equipment; CEIR is higher leveled EIR equipment, stores the IMEI central database, and this IMEI central database comprises the information of whole mobile devices in the mobile communications network; Concrete, this IMEI central database is distributed high-volume database, general storage IMEI and equipment state also can comprise other available information such as IMSI, MSISDN, the time of enabling first, the last time that occurs and once occurred at which MSC or SGSN etc. in network; CEIR equipment has been realized the centralized management of mobile device information, formed server/client relationship with EIR equipment, and the data exchanging function of CEIR equipment IMEI verification needs in satisfying net, also be responsible for the shared and exchange of the mobile device list (mainly being blacklist) between the different operators.

Thereby the idiographic flow of IMEI verification may further comprise the steps:

● MSC/SGSN sends " Check IMEI (IMEI) " message to EIR;

● EIR sends " Remote Check IMEI (IMEI) " message to CEIR, and this message is converted into remote inquiry to CEIR with the IMEI check request of this locality;

● CEIR utilizes inner sign verification unit that this mobile device is carried out verification, returns " Remote Check IMEI Ack (IMEI) " message to EIR;

● EIR returns " Check IMEI Ack (IMEI) " message to MSC/SGSN, and MSC/SGSN determines whether to allow this mobile device to carry out access to netwoks according to the check results of receiving.

But after introducing CEIR equipment, EIR equipment need be inquired about the distal end I MEI central database that is stored among the CEIR with lookup table mode in real time in checking procedure, so the response time of checking procedure is uncertain, have defectives such as construction cost height, inefficiency.

Inquire about a series of problems that distal end I MEI central database brings in the IMEI checking procedure in real time for solving, can introduce the method for quick verification IMEI, its know-why is: the EIR that carries out the IMEI verification is decomposed into ES with the IMEI verification and changes identification and ES renewal, in the single IMEI verification at specific mobile device, only carry out one of them stage; Be that EIR ES that identify, specific mobile device in certain IMEI verification changes and will upgrade in the IMEI verification at this specific mobile device next time.

For realizing above-mentioned quick verification IMEI method, data record in IMEI central database in the CEIR equipment and the tabulation of the mobile device in the EIR equipment generally all comprises tlv triple and the status information of equipment of mobile device, but every implication difference that data record is represented:

● in CEIR equipment, what the equipment state that data record represents to meet the mobile device of certain condition should be;

● in EIR equipment, data record is then annotated " instruction " that will carry out for EIR equipment, and the mobile device that is about to meet certain condition is set to desired equipment state.

The purpose of IMEI verification is to make MSC/VLR(Visit Location Register, Visited Location Registor) equipment state of mobile device and IMEI central database keep synchronously (when MSC carries out the mobile device access control and among the SGSN, the information of mobile device is kept among the VLR), and according to the access to netwoks control of equipment state realization to mobile device; The real process of this quick verification IMEI method is: send up-to-date tlv triple and status information of equipment to EIR and CEIR from VLR/SGSN; Described EIR checks whether the equipment state update instruction that is stored in the local mobile device tabulation is arranged, if have, then with the equipment state in the described update instruction as check results, equipment state is synchronous in realization VLR/SGSN and the IMEI central database, otherwise, keep the current device state constant; Whether should upgrade the equipment state of mobile device in VLR/SGSN by CEIR identification; If desired, then CEIR sends to EIR with update instruction, and is being handed down to VLR/SGSN in the IMEI verification at described mobile device by EIR next time.

In addition, in quick verification IMEI process, the equipment state update instruction that is stored in the local mobile device tabulation of EIR equipment can be deleted after execution, to reduce the length of local mobile device tabulation; In the checking procedure, the mobile device tabulation that EIR only need inquire about local storage can provide check results, and pending operational order negligible amounts in the tabulation, therefore can realize the purpose of quick verification.

Concrete, Fig. 1 shows the flow chart of the method for above-mentioned quick verification IMEI, may further comprise the steps:

Step S101, send " Extended Check IMEI " (IMEI check request of expansion) message by MSC/SGSN to EIR, this message has been added the current ES of mobile device in former " Check IMEI " (IMEI verification) message basis, preferably, can further include information such as IMSI and MSISDN; And information such as current ES have been stored among VLR or the SGSN, and MSC/SGSN can easily obtain;

Step S102, EIR receives and resolves " Extended Check IMEI " request message, inquire about local mobile device tabulation according to the mobile device identifying information in the analysis result, this this locality mobile device tabulation is used for record, and all are used for upgrading the instruction of mobile device status;

If should have the data record that is complementary with this mobile device in the mobile device tabulation of this locality, and then require final ES is set according to tabulation, otherwise keep current ES constant; If only relating to this mobile device, the described record that is complementary with this mobile device from local mobile device tabulation, deletes described record;

EIR with target ES(namely do not have when record of being complementary resolve the ES that obtains or have when being complementary record require set ES according to tabulation) send to MSC/SGSN as check results with the form of " Extended Check IMEI Ack " (IMEI verification response of expansion) message, MSC/SGSN determines whether to allow this mobile device to carry out access to netwoks according to the check results of receiving;

Step S103, EIR sends " Update ME Info Request " (mobile device information updating request) message to CEIR, sends IMEI, current ES and the possible information relevant with mobile device such as IMSI, MSISDN to CEIR;

Step S104, CEIR receives " Update ME Info Request " message, and the ES information in the message and the ES information in the IMEI central database are compared, and determines whether upgrade the ES of corresponding IMEI among the EIR; Do not upgrade if do not need, then send normal " Update ME Info Response " (the mobile device information updating response) message that receives of expression and give EIR, otherwise send " the Update ME Info Response " message that has comprised the instruction that is used for the tabulation of renewal EIR mobile device and give EIR, generally speaking, be the ES that will from the IMEI central database, inquire and to the identifying information of described mobile device as " the Update ME Info Response " message of encoding of the update instruction to described EIR;

Wherein, CEIR utilizes received information that the IMEI central database is upgraded, as receives the time of IMEI verification message, the source of IMEI verification message and possible IMSI, MSISDN etc.;

After this, EIR receives " Update ME Info Response " message, if comprised the instruction that is used for upgrading mobile device status in this message, then according to command request it newly-increasedly is a record in the described local mobile device tabulation.

As can be seen, in the method for quick verification IMEI, the variation of the equipment state that identifies will be deferred to when EIR carries out the IMEI verification to this mobile device next time upgrades corresponding delaying of the entry-into-force time of check results; Because the frequency of occurrences of IMEI verification trigger event higher (per hour can reach once as the frequency of occurrences of position update event when busy), increase to the delay of check results entry-into-force time generally within acceptable scope.

But, the result of the quick verification of above-mentioned IMEI only is stored among the EIR that carries out this time verification, leave the area of coverage of this EIR as the mobile subscriber after, the check results that before produces namely lost efficacy, namely after the mobile subscriber enters the area of coverage of another EIR, this another EIR need re-execute the operation that ES changes identification and ES renewal, and therefore, the entry-into-force time of check results will more prolong.

Less or mobile device is under the situation of high-speed moving state at the EIR area of coverage, and system will be more remarkable at the mis-behave of check results aspect the entry-into-force time.

And in present stage, the market demand to high performance-price ratio IMEI calibration technology is urgent day by day, can the development priority of IMEI calibration technology be to enhance product performance, reducing the construction costs, be to improve the key of the quick check system cost performance of IMEI and carry out substantial improvements to check results entry-into-force time index.

In sum, to the IMEI calibration technology in addition perfect, improve and have vast market prospect, also be very important.

Summary of the invention

For verification the possibility of result in the method that solves quick verification IMEI lost efficacy or was delayed the problem that comes into force, the invention discloses a kind of technical scheme for collaborative verification International Mobile Station Equipment Identification, realize the cooperation of a plurality of EIR in the mode of the quick check results of share I MEI.

To achieve these goals, the invention provides a kind of method for collaborative verification IMEI, comprise the execution following steps:

S1: partner member's tabulation is set in each EIR, is used for the EIR member list that record and described EIR have partnership;

The data record of tabulating for the local mobile device of each EIR arranges original EIR sign, is used for the original EIR of this data record of mark;

S2: in carrying out quick IMEI checking procedure, when the local mobile device tabulation of a certain EIR took place directly to change, described EIR was synchronized to described direct variation in the local mobile device tabulation of all members in its partner member's tabulation; Wherein, described direct variation comprises the newly-increased and/or record deletion of record;

Described record is newly-increased to be comprised: the IMEI check request that reports CEIR for described EIR with regard to a certain mobile device, when it receives when comprising the instruction of upgrading described mobile device status in feedback information that CEIR issues and the described feedback information, then according to command request it is increased newly and be a data record in the described local mobile device tabulation, and be that described data record is added original EIR sign, described EIR is labeled as the original EIR of described data record;

Described record deletion comprises: at described EIR after the data record in the tabulation of local mobile device is upgraded corresponding mobile device executing state based on it, if described data record only relates to current mobile device, then described EIR deletes described data record from its local mobile device tabulation.

Preferably, the step that described direct variation is synchronized in the local mobile device tabulation of all members in its partner member tabulation of EIR described in the described step S2 comprises:

Step S21: described EIR identifies described direct variation;

If newly-increased for record, all members send first synchronization request message in then tabulating to partner member;

If be record deletion, then determine according to the original EIR sign of described data record whether this equipment is the original EIR of described data record, be then in the partner member tabulation all members send first synchronization request message, otherwise only send first synchronization request message to the original EIR of the original EIR sign institute mark of described data record;

Wherein, carry the record newly-added information/record deletion information of described local mobile device tabulation in described first synchronization request message;

Step S22: the EIR that receives described first synchronization request message resolves and identifies described first synchronization request message;

If obtain the record newly-added information, then carry out the newly-increased operation of record of local mobile device tabulation: described record newly-added information is compiled as a data record in the local mobile device tabulation, and is transmit leg EIR by the original EIR of the described data record of original EIR identity marking;

If obtain record deletion information, then carry out the record deletion operation of local mobile device tabulation: the corresponding data record of deletion from local mobile device tabulation, and determine according to the original EIR sign of described data record whether this equipment is the original EIR of described data record, be then in partner member's tabulation all members except transmit leg EIR send second synchronization request message; Wherein, carry the record deletion information of described local mobile device tabulation in described second synchronization request message;

Step S23: after receiving the EIR parsing of described second synchronization request message and identifying described second synchronization request message, the corresponding data record of deletion from local mobile device tabulation.

Preferably, comprise that also the EIR that receives described the first/the second synchronization request message sends the first/the second synchronous response message to the transmit leg EIR of described the first/the second synchronization request message.

Preferably, also being included in when executive logging is newly-increased to be operated is that corresponding data record arranges life cycle, is used for these data of mark and is recorded in the deadline date that EIR preserves; When the life cycle of a certain data record finishes, the described data record of deletion from local mobile device tabulation.

To achieve these goals, the present invention also provides a kind of EIR for collaborative verification IMEI, and it comprises for the unit of realizing quick IMEI verification; Also comprise:

Partner member's tabulation is used for the EIR member list that record and described EIR have partnership;

Original EIR arranges module, is connected with described local mobile device tabulation for the unit of realizing quick IMEI verification, is used to the data record of described local mobile device tabulation that original EIR sign is set, and is used for the original EIR of this data record of mark;

Lock unit, with described original EIR module is set and is connected for the unit of realizing quick IMEI verification, described partner member tabulation with described, be used for when the local mobile device tabulation of carrying out EIR described in the quick IMEI checking procedure takes place directly to change, described direct variation be synchronized in the local mobile device tabulation of all members in described partner member's tabulation; Wherein, described direct variation comprises the newly-increased and/or record deletion of record;

Described record is newly-increased to be comprised: the IMEI check request that reports central equipment marker register CEIR for described EIR with regard to a certain mobile device, when it receives when comprising the instruction of upgrading described mobile device status in feedback information that CEIR issues and the described feedback information, then according to command request it is increased newly and be a data record in the described local mobile device tabulation, and be that described data record is added original EIR sign, described EIR is labeled as the original EIR of described data record;

Preferably, described lock unit comprises:

The first synchronization request module, tabulating with described partner member with the unit of the quick IMEI verification of described realization is connected, and is used for the described direct variation of identification;

Handle synchronously and the second synchronization request module, with original EIR module is set with described partner member's tabulation and is connected, be used for the synchronization request message that parsing and identification receive;

Wherein, the described synchronization request message that receives comprises first synchronization request message and second synchronization request message.

Preferably, described lock unit also comprises the sync response receiver module that is connected with and the processing synchronously and second synchronization request module of the described first synchronization request module respectively, and the sync response sending module that is connected with described synchronous processing and the second synchronization request module;

Described sync response sending module is used for receiving according to described synchronous processing and the second synchronization request module triggering of described the first/the second synchronization request message, sends the first/the second synchronous response message to the transmit leg EIR of described the first/the second synchronization request message;

Described sync response receiver module is used for receiving the first/the second synchronous response message, and feeds back to the described first synchronization request module and synchronous the processing and the second synchronization request module.

Preferably, comprise that also life cycle arranges module, be connected with described lock unit that being used for when the newly-increased operation of executive logging is that corresponding data record arranges life cycle, is used for these data of mark and is recorded in the deadline date that EIR preserves; When the life cycle of a certain data record finishes, the described data record of deletion from local mobile device tabulation.

To achieve these goals, the present invention also provides a kind of system for collaborative verification IMEI, comprise EIR and respectively with mutual MSC/ SGSN and the CEIR of described EIR, described EIR is above-mentioned EIR.

By technique scheme as can be seen, no matter a certain mobile device is to trigger IMEI verification next time in the EIR of a preceding IMEI verification or in the partner EIR of this EIR, takes place all can comprise the equipment state change information that a preceding IMEI verification has been done according to this mobile device in the local mobile device tabulation of EIR of IMEI verification next time; Therefore, the mobile device status change that can guarantee to identify in a preceding IMEI verification will be performed in described IMEI next time verification and put in place;

Therefore, by the improvement that the present invention carries out quick IMEI method of calibration, can take full advantage of the result of IMEI verification each time, improve the entry-into-force time index of IMEI check results, save system resource simultaneously and reduced the equipment construction cost.

Introduced the concept of a series of reduced forms in the summary of the invention part, this will further describe in the embodiment part.Content part of the present invention does not also mean that key feature and the essential features that will attempt to limit technical scheme required for protection, does not more mean that the protection range of attempting to determine technical scheme required for protection.

Below in conjunction with accompanying drawing, describe advantages and features of the invention in detail.

Description of drawings

Fig. 1 is the method flow diagram of quick verification IMEI in the prior art;

Fig. 2 A is the schematic flow sheet of the method for collaborative verification IMEI according to the present invention;

Fig. 2 B is the method for the collaborative verification IMEI according to the present invention, the schematic flow sheet of a preferred embodiment;

Fig. 3 is according to a specific embodiment of the present invention, related MSC/SGSN process chart;

Fig. 4 is according to a specific embodiment of the present invention, among the related EIR to the process chart of received IMEI check request;

Fig. 5 is according to a specific embodiment of the present invention, among the related EIR to the process chart of received synchronization request message;

Fig. 6 is according to a specific embodiment of the present invention, related CEIR process chart;

Fig. 7 is used for the system construction drawing of collaborative verification IMEI for according to a preferred embodiment of the present invention;

Fig. 8 is used for the structural representation of the EIR of collaborative verification IMEI in accordance with a preferred embodiment of the present invention.

Embodiment

In the following description, a large amount of concrete details have been provided in order to more thorough understanding of the invention is provided.Yet, it will be apparent to one skilled in the art that the present invention can need not one or more these details and implemented.In other example, for fear of obscuring with the present invention, be not described for technical characterictics more well known in the art.

Obviously, execution of the present invention is not limited to the specific details that those skilled in the art has the knack of.Preferred embodiment of the present invention is described in detail as follows, yet except these were described in detail, the present invention can also have other execution modes.

According to the present invention, provide a kind of method and system for collaborative verification International Mobile Station Equipment Identification IMEI.Know-why of the present invention is: if the mobile device in a certain EIR may roam into other the EIR area of coverage, then described other EIR is defined as the partner EIR of this EIR, namely described other EIR and this EIR has partnership; This EIR ES that identify, specific mobile device in certain IMEI verification changes and will be updated to synchronously among the partner EIR, thereby guarantees can be updated among the MSC/SGSN at described mobile device place in the IMEI verification at this specific mobile device next time; And after EIR was handled the ES variation of this specific mobile device, this processing can be synchronized among its partner EIR, to avoid repetitive operation equally.

According to above-mentioned know-why, the invention provides a kind of method for collaborative verification International Mobile Station Equipment Identification, shown in Fig. 2 A, may further comprise the steps:

S1: partner member's tabulation is set in each equipment identity register EIR, is used for the EIR member list that record and described EIR have partnership;

The data record of tabulating for the local mobile device of each EIR arranges original EIR sign, is used for the original EIR of this data record of mark, and namely this data record of mark is to trigger generation because carry out quick IMEI verification in which EIR at first; The setting of this original EIR sign can be carried out in the initialization procedure of local mobile device tabulation;

Described record deletion comprises: at described EIR after the data record in the tabulation of local mobile device is upgraded corresponding mobile device executing state based on it, if described data record only relates to current mobile device, then need not to continue to keep, described EIR is the described data record of deletion from its local mobile device tabulation.

As can be seen, because the present invention adopts the mode that local mobile device tabulation changes synchronously between partner EIR, the instruction of the recognition result of this verification and the required execution form with data record is updated in the local mobile device tabulation of described EIR and partner EIR thereof synchronously, the EIR(that can guarantee to carry out verification next time carries out one of the EIR of this IMEI verification or its partner EIR) local mobile device tabulation in comprised the data record that generates according to this verification recognition result, therefore no matter whether mobile device is roamed, all can be to using in its IMEI verification next time to the recognition result of its last IMEI verification.

That is, the data record that the present invention generates last IMEI verification recognition result is updated among described EIR and the partner EIR thereof synchronously, when described mobile device carries out IMEI verification next time, even described mobile device is roamed out the described EIR area of coverage and is entered the area of coverage that a gang of accompanies EIR, still can utilize the data in synchronization record that the equipment state of described mobile device is adjusted to the desired state of last verification, therefore, to continue to reside in the situation of former EIR identical for the entry-into-force time of this check results and described mobile device when can be implemented in described mobile device and roaming into the area of coverage of described partner EIR, improved the utilance of check results, and avoided causing delaying of check results entry-into-force time because of the mobile device roaming.

In addition, because data record (data record that namely only relates to the mobile device individual cell) can be deleted from EIR after use, and delete identical data record in the partner EIR equipment synchronously, can effectively control the length of the local mobile device tabulation of EIR equipment and partner EIR device storage thereof, reach and shorten the IMEI verification response time, and the purpose of reducining the construction costs.

Further, the step that EIR described in the described step S2 is synchronized to described direct variation in the local mobile device tabulation of all members in its partner member tabulation can take variety of way to be realized, all members send synchronization request message in for example being tabulated to partner member by the EIR that takes place directly to change, for example send synchronization request message by the EIR that takes place directly to change to CEIR, all members send synchronization request message etc. in being tabulated to corresponding partner member by CEIR again.

Certainly, the corrective measure that the check results that identifies in this verification is updated to synchronously partner EIR that the present invention takes can increase the exchanges data quantity between CEIR and EIR or EIR and partner EIR undoubtedly; But the data exchange process between the CEIR that increases and EIR or EIR and partner EIR is as long as finished before next verification takes place; In the real network environment, the occurrence frequency that mobile device is carried out the IMEI verification (period that traffic carrying capacity is the highest) when every day busy can reach per hour 1 ~ 2 time; And the general high speed interface that adopts Ethernet etc. between CEIR and EIR, EIR and partner EIR, so the disposal ability that above-mentioned exchanges data increases and data transfer load are acceptables.

But still there are some defectives in the such scheme:

If all members send synchronization request message in for example being tabulated to partner member by the EIR that takes place directly to change, then because the EIR of occurrence record deletion may not be the original EIR of this record, therefore, its can send to the synchronization request message of this record deletion all members own but not that the partner member of original EIR tabulates; This just may cause the partner member of a part of original EIR not receive the synchronization request message of this record deletion and keep corresponding data record always, perhaps a part of EIR that does not belong to original EIR partner member receives the synchronization request message of this record deletion and does not have exercisable object, causes the information redundancy in the local mobile device tabulation of unhelpful Signalling exchange and some EIR.

And carry out alternant way by CEIR, and still may there be above-mentioned defective, the EIR of directly variation and the signaling consumption between the CEIR take place but also increased.

Therefore, in order to simplify Signalling exchange as far as possible and to reduce information redundancy in the local mobile device tabulation of each EIR, the present invention is synchronized to described direct variation for EIR described in the described step S2 specific implementation that step in the local mobile device tabulation of all members in its partner member tabulation provides following optimization, comprising:

Step S21: the directly EIR of variation takes place in described EIR() the described direct variation of identification;

In a preferred embodiment, the EIR that receives described first synchronization request message can send first synchronous response message to the transmit leg EIR of described first synchronization request message, therefore in this step, the EIR that takes place directly to change is after waiting for and receiving whole first synchronous response message corresponding with first synchronization request message that sends, finish this device processes process and enter idle condition, directly changing next time or changing synchronously up to local mobile device tabulation;

In a preferred embodiment, the EIR that receives described the first/the second synchronization request message can send the first/the second synchronous response message to the transmit leg EIR of described the first/the second synchronization request message, therefore in this step, the EIR that receives described first synchronization request message can send first synchronous response message to the transmit leg EIR of described first synchronization request message, and after waiting for and receiving whole second synchronous response message corresponding with second synchronization request message that sends, finish this device processes process and enter idle condition, directly changing next time or changing synchronously up to its local mobile device tabulation;

Step S23: after receiving the EIR parsing of described second synchronization request message and identifying described second synchronization request message, the corresponding data record of deletion from local mobile device tabulation;

In a preferred embodiment, the EIR that receives described second synchronization request message can send second synchronous response message to the transmit leg EIR of described second synchronization request message, therefore in this step, the EIR that receives described second synchronization request message can send second synchronous response message to the transmit leg EIR of described second synchronization request message, finish this device processes process and enter idle condition, directly changing next time or changing synchronously up to its local mobile device tabulation.

As can be seen, adopt the synchronization scenario of above-mentioned optimization, make local mobile device tabulation the EIR of directly variation take place by identifying the direct variation that takes place, distinguished the processing of and record deletion newly-increased for record, thereby the synchronous process range that guarantees record deletion can be consistent with the newly-increased process range of original record, reduces signaling consumption as far as possible and avoid the information redundancy in the local mobile device tabulation among each EIR.

Further again, no matter whether adopt the synchronous implementation of above-mentioned optimization, can when the newly-increased operation of executive logging, be that corresponding data record arranges life cycle all, be used for these data of mark and be recorded in the deadline date that EIR preserves; When the life cycle of a certain data record finishes, the described data record of deletion from local mobile device tabulation; Deletion action after this deletion is upgraded corresponding mobile device executing state no thanks to, therefore the data record that finishes to delete because of life cycle does not constitute the direct variation of local mobile device tabulation.For arranging life cycle, data record can in local mobile device list initialization process, arrange, it is long that the arranging of this life cycle can avoid some unnecessary data to be recorded in the local mobile device tabulation RT, and then shorten the response time of IMEI verification.

Fig. 2 B shows the flow chart of method one preferred embodiment of above-mentioned collaborative verification IMEI.

Below in conjunction with exemplary parameter existing quick IMEI checkschema and collaborative checkschema provided by the invention are compared, so that the easier grasp of those skilled in the art characteristics of the present invention and advantage, but exemplary parameter is not the restriction to technical solution of the present invention.

Suppose that the mobile device parameter that certain IMEI verification relates to is as follows: IMEI is the 11111111111111(14 position, has deleted standby number SP); The IMSI of the SIM card of using in the described mobile device is that 222222222222222, MSISDN is 3333333333333; The current ES of the described mobile device of storing in MSC/SGSN is that 0(is put into white list); The target ES of the described mobile device of storing in the IMEI of CEIR central database is that 1(is put on the blacklist).

Existing quick IMEI checking procedure is as follows:

If at described MSC/VLR(or SGSN, present embodiment reports with MSC execution verification and is example, and MSC and VLR are integrated in one in the present embodiment) middle triggering IMEI verification, and " Extended Check IMEI " message is sent to the EIR(that possesses quick verifying function namely comprises EIR for the unit of realizing quick IMEI verification), comprised mobile device triplet information＜IMEI in described " Extended Check IMEI " message, IMSI, MSISDN〉and the current ES of mobile device; EIR receives " Extended Check IMEI " message, the mobile device triplet information that parses is＜11111111111111,222222222222222,3333333333333 〉, the current ES of mobile device is 0, the data record that is not complementary with described mobile device in the local mobile device tabulation of EIR, therefore, this verification sends to described MSC/VLR to current ES as check results and after being encoded to " Extended Check IMEI Ack " message, because check results is that 0(is put into white list), allow described mobile device to carry out access to netwoks;

EIR is with the mobile device triplet information＜IMEI that obtains in this verification, IMSI, MSISDN〉and current ES send to CEIR after being encoded to " Update ME Info Request " message; The triplet information that CEIR parses described mobile device is＜11111111111111,222222222222222,3333333333333〉and, current ES is 0; CEIR is with triplet information＜11111111111111,222222222222222,3333333333333〉the target ES that obtains described mobile device for search index IMEI central database is 1; Because current ES and target ES are inconsistent, CEIR generates and comprises quaternary group information＜IMEI, IMSI, MSISDN, ES〉update command, concrete quaternary group information is＜11111111111111,222222222222222,3333333333333,1 〉, being about to tlv triple is＜11111111111111,222222222222222,3333333333333〉the ES of mobile device be set to 1; CEIR is encoded by described update command and reception result sends to EIR for after " Update ME Info Response " message; EIR receives " Update ME Info Response " message, and with quaternary group information＜11111111111111,222222222222222 that parse, 3333333333333,1〉be compiled as a data record in the local mobile device tabulation;

If verification is next time still triggered by described MSC/VLR, then EIR receives new " Extended Check IMEI " message, and the mobile device triplet information that parses is＜11111111111111,222222222222222,3333333333333 〉, the current ES of mobile device is 0; With tlv triple＜11111111111111,222222222222222,3333333333333〉the local mobile device tabulation of inquiry, the ES that comprises in the data record that obtains to match is 1, therefore, need to revise the ES of mobile device, the ES in the described data record is sent to described MSC/VLR as check results and after being encoded to " Extended Check IMEI Ack " message, because check results is that 1(is put on the blacklist), refuse described mobile device and carry out access to netwoks; EIR deletion comprises quaternary group information＜11111111111111,222222222222222,3333333333333,1〉data record;

EIR is with mobile device triplet information＜IMEI, IMSI, MSISDN〉and current ES(be updated to 1 by above-mentioned checking procedure) send to CEIR after being encoded to " Update ME Info Request " message; The triplet information that CEIR parses described mobile device is＜11111111111111,222222222222222,3333333333333〉and, current ES is 1; CEIR is with triplet information＜11111111111111,222222222222222,3333333333333〉the target ES that obtains described mobile device for search index IMEI central database is 1; Because current ES is consistent with target ES, does not need the ES of mobile device is upgraded again; CEIR sends to EIR after reception result being encoded to " Update ME Info Response " message; EIR receives " Update ME Info Response " message authentication checking procedure and finishes;

If but verification next time triggers by new MSC/VLR, and " Extended Check IMEI " message is sent to new EIR; New EIR receives " Extended Check IMEI " message, the mobile device triplet information that parses is＜11111111111111,222222222222222,3333333333333 〉, the current ES of mobile device is 0, the data record that is not complementary with described mobile device in the local mobile device tabulation of new EIR, therefore, current ES is sent to described MSC/VLR as check results and after being encoded to " Extended Check IMEI Ack " message, because check results is that 0(is put into white list), allow described mobile device to carry out access to netwoks;

New EIR is with the mobile device triplet information＜IMEI that obtains, IMSI, MSISDN〉and current ES send to CEIR after being encoded to " Update ME Info Request " message; The triplet information that CEIR parses described mobile device is＜11111111111111,222222222222222,3333333333333〉and, current ES is 0; CEIR is with triplet information＜11111111111111,222222222222222,3333333333333〉the target ES that obtains described mobile device for search index IMEI central database is 1; Because current ES and target ES are inconsistent, CEIR generates and comprises quaternary group information＜IMEI, IMSI, MSISDN, ES〉update command, concrete quaternary group information is＜11111111111111,222222222222222,3333333333333,1 〉, being about to tlv triple is＜11111111111111,222222222222222,3333333333333〉the ES of mobile device be set to 1; CEIR is encoded by described update command and reception result sends to new EIR for after " Update ME Info Response " message; New EIR receives " Update ME Info Response " message, and with quaternary group information＜11111111111111,222222222222222 that parse, 3333333333333,1〉be compiled as a data record in the local mobile device tabulation.

From above-mentioned example process, if verification is next time triggered by new MSC/VLR in quick IMEI verification, and by new EIR reception " Extended Check IMEI " message, there is not the data record with described mobile device coupling in the local mobile device tabulation because of new EIR, verification next time fails to revise the state of described mobile device, and the entry-into-force time of this check results is delayed verification next time again.

By contrast, the method for collaborative verification IMEI provided by the invention is the improvement to quick IMEI verification, and the process of the collaborative verification IMEI after the improvement is as follows:

If in described MSC/VLR, trigger the IMEI verification, and with " Extended Check IMEI " message be sent to possess quick verifying function EIR(for example, EIR M), comprised mobile device triplet information＜IMEI in described " Extended Check IMEI " message, IMSI, MSISDN〉and the current ES of mobile device; EIR M receives " Extended Check IMEI " message, the mobile device triplet information that parses is＜11111111111111,222222222222222,3333333333333 〉, the current ES of mobile device is 0, the data record that is not complementary with described mobile device in the local mobile device tabulation of EIR M, therefore, this verification sends to described MSC/VLR to current ES as check results and after being encoded to " Extended Check IMEI Ack " message, because check results is that 0(is put into white list), allow described mobile device to carry out access to netwoks;

EIR M is with the mobile device triplet information＜IMEI that obtains in this verification, IMSI, MSISDN〉and current ES send to CEIR after being encoded to " Update ME Info Request " message; The triplet information that CEIR parses described mobile device is＜11111111111111,222222222222222,3333333333333〉and, current ES is 0; CEIR is with triplet information＜11111111111111,222222222222222,3333333333333〉the target ES that obtains described mobile device for search index IMEI central database is 1; Because current ES and target ES are inconsistent, CEIR generates and comprises quaternary group information＜IMEI, IMSI, MSISDN, ES〉update command, concrete quaternary group information is＜11111111111111,222222222222222,3333333333333,1 〉, being about to tlv triple is＜11111111111111,222222222222222,3333333333333〉the ES of mobile device be set to 1; CEIR is encoded by described update command and reception result sends to EIR M for after " Update ME Info Response " message; EIR M receives " Update ME Info Response " message, and with quaternary group information＜11111111111111 that parse, 222222222222222,3333333333333,1〉is compiled as a data record in the tabulation of local mobile device, and this EIR M is that described data record is added original EIR sign, this equipment (EIR M) is labeled as the original EIR of this quaternary group information data record;

EIR M sends " ME List Syn Request " message as synchronization request message to all members in its partner member's tabulation, should carry above-mentioned quaternary group information and record newly-added information in " ME List Syn Request " message, also alternative is carried original EIR sign; Partner EIR receives " ME List Syn Request " message, parse quaternary group information＜11111111111111,222222222222222,3333333333333,1〉and be identified as the record newly-added information, therefore it is compiled as a data record in the local mobile device tabulation, and can is original EIR according to the original EIR mark for marking EIR M that carries in this message; If do not carry original EIR sign in " ME List Syn Request " message, then according to realizing the mark of original EIR according to the transmit leg that is somebody's turn to do " ME List Syn Request " message;

Partner EIR sends " ME List Syn Response " message as synchronous response message to EIR M, and expression normally receives and finish renewal process;

If verification is next time still triggered by described MSC/VLR, then EIR M receives new " Extended Check IMEI " message, and the mobile device triplet information that parses is＜11111111111111,222222222222222,3333333333333 〉, the current ES of mobile device is 0; With tlv triple＜11111111111111,222222222222222,3333333333333〉the local mobile device tabulation of inquiry, the ES that comprises in the data record that obtains to match is 1, therefore, need to revise the ES of mobile device, the ES in the described data record is sent to described MSC/VLR as check results and after being encoded to " Extended Check IMEI Ack " message, because check results is that 1(is put on the blacklist), refuse described mobile device and carry out access to netwoks; EIR M deletion comprises quaternary group information＜11111111111111,222222222222222,3333333333333,1〉data record; This EIR M further identification oneself is original EIR, therefore EIR M is quaternary group information＜11111111111111,222222222222222,3333333333333,1〉is encoded to " ME List Syn Request " message as synchronization request message, should carry above-mentioned quaternary group information and record deletion information in " ME List Syn Request " message, and send to all members in its partner member's tabulation;

On the one hand, partner EIR receives " ME List Syn Request " message, parse quaternary group information＜11111111111111,222222222222222,3333333333333,1〉and be identified as record deletion information, therefore delete in the local mobile device tabulation and comprise quaternary group information＜11111111111111,222222222222222,3333333333333,1〉data record, and send " ME List Syn Response " message to EIR M and represent the normal synchronizing process that receives and finished; Next, partner EIR identification oneself is not the original EIR of this data record, therefore no longer continues operation;

On the other hand, EIR M is with mobile device triplet information＜IMEI, IMSI, MSISDN〉and current ES(be updated to 1 by above-mentioned checking procedure) send to CEIR after being encoded to " Update ME Info Request " message; The triplet information that CEIR parses described mobile device is＜11111111111111,222222222222222,3333333333333〉and, current ES is 1; CEIR is with triplet information＜11111111111111,222222222222222,3333333333333〉the target ES that obtains described mobile device for search index IMEI central database is 1; Because current ES is consistent with target ES, does not need the ES of mobile device is upgraded again; CEIR sends to EIR M after reception result being encoded to " Update ME Info Response " message; EIR M receives " Update ME Info Response " message authentication checking procedure and finishes;

Even verification is next time triggered by new MSC/VLR, and the partner EIR(that " Extended Check IMEI " message is sent to EIR M for example, EIR N); EIR N receives " Extended Check IMEI " message, the mobile device triplet information that parses is＜11111111111111,222222222222222,3333333333333 〉, the current ES of mobile device is 0, with tlv triple＜11111111111111,222222222222222,3333333333333〉the local mobile device tabulation of inquiry, the ES that comprises in the data record that obtains to match is 1, therefore, need to revise the ES of mobile device, ES in the described data record is sent to described MSC/VLR as check results and after being encoded to " Extended Check IMEI Ack " message, because check results is that 1(is put on the blacklist), refuse described mobile device and carry out access to netwoks; EIR N deletes the respective data record in the tabulation of local mobile device, and the original EIR that identifies this data record is EIR M, then sends the deletion action of " ME List Syn Request " message initiated respective data record to EIR M;

EIR M receives " ME List Syn Request " message, parse quaternary group information＜11111111111111,222222222222222,3333333333333,1〉and be identified as record deletion information, therefore delete in the local mobile device tabulation and comprise quaternary group information＜11111111111111,222222222222222,3333333333333,1〉data record, and send " ME List Syn Response " message to EIR N and represent the normal synchronizing process that receives and finished;

Next, on the one hand, EIR M identification oneself is the original EIR of this data record, then quaternary group information＜11111111111111,222222222222222,3333333333333,1〉and record deletion information send to its partner EIR except EIR N after being encoded to " ME List Syn Request " message; The partner EIR of EIR M receives " ME List Syn Request " message, parse quaternary group information＜11111111111111,222222222222222,3333333333333,1〉and be identified as record deletion information, therefore deletion comprises quaternary group information＜11111111111111 in the local mobile device tabulation separately, 222222222222222,3333333333333,1〉data record, and send " ME List Syn Response " message to EIR M and represent the normal synchronizing process that receives and finished; Next, partner EIR identification oneself is not the original EIR of this data record, therefore no longer continues operation;

On the other hand, EIR N is with mobile device triplet information＜IMEI, IMSI, MSISDN〉and current ES(be updated to 1 by above-mentioned checking procedure) send to CEIR after being encoded to " Update ME Info Request " message; The triplet information that CEIR parses described mobile device is＜11111111111111,222222222222222,3333333333333〉and, current ES is 1; CEIR is with triplet information＜11111111111111,222222222222222,3333333333333〉the target ES that obtains described mobile device for search index IMEI central database is 1; Because current ES is consistent with target ES, does not need the ES of mobile device is upgraded again; CEIR sends to EIR N after reception result being encoded to " Update ME Info Response " message; EIR N receives " Update ME Info Response " message authentication checking procedure and finishes.

From above-mentioned example process, improved quick IMEI method of calibration is namely worked in coordination with in the IMEI method of calibration, if verification is next time triggered by new MSC/VLR, and by partner EIR reception " Extended Check IMEI " message, comprised the data record with described mobile device coupling in the local mobile device tabulation because of partner EIR, verification next time will be carried out the update instruction of the ES that revises described mobile device, thereby avoid the entry-into-force time of this check results further to be delayed.

For the ease of the enforcement of technical staff to the technology of the present invention content, below respectively to the in addition exemplary description respectively of the concrete handling process of MSC, SGSN, EIR and CEIR equipment among the top embodiment.

With reference to figure 3, be the method for collaborative verification IMEI provided by the invention, the concrete handling process of related MSC/SGSN equipment:

Step S301 receives IMEI verification trigger event, as identification request, authentication ciphering etc.;

Step S302 checks whether to start the IMEI checking process, if do not need, and process ends then;

Step S303 obtains the IMEI relevant with this mobile device, ES and possible information such as IMSI, MSISDN;

Step S304, " Extended Check IMEI " message is set: " Check IMEI " message that IMEI is encoded to standard by the MAP_CHECK_IMEI primitive of 3GPP agreement regulation, ES and the equiprobable out of Memory of IMSI, MSISDN with the form coding of extensionContainer/ privateExtensionList/ extId in the extension container of MAP_CHECK_IMEI primitive, wherein, each extId can comprise maximum 16 2 byte integer, adopts the ASN.1 mode to encode;

Step S305 sends to EIR with " Extended Check IMEI " message;

Step S306 waits for " the Extended Check IMEI Ack " message that comes from EIR;

Step S307 receives and resolves " the Extended Check IMEI Ack " message that comes from EIR;

Step S308 determines whether to allow described mobile device to carry out access to netwoks according to the check results that parses from " Extended Check IMEI Ack " message.

With reference to figure 4, be the method for collaborative verification IMEI provided by the invention, (it is example that present embodiment is handled synchronously with the synchronization request of carrying out partner EIR one by one to related EIR equipment to the concrete handling process of received IMEI check request, but those skilled in the art can understand, and also can realize synchronization request to partner EIR simultaneously by mass-sending):

Step S401 receives " Extended Check IMEI " message from MSC/SGSN, and " the Extended Check IMEI " message that receives is decoded, and parses IMEI, ES and parameters such as the IMSI that may comprise, MSISDN;

Step S402 inquires about local mobile device tabulation according to the mobile device identifying information in the analysis result;

Step S403 if comprised the data record that is complementary with current mobile device in the tabulation of local mobile device, then needs to change the ES of current mobile device, changes step S405; Otherwise, execution in step S404;

Step S404 adopts the ES that parses from " Extended Check IMEI " message as check results, changes step S406;

Step S405 is according to the Query Result of local mobile device tabulation being determined final ES and as check results;

Step S406 is encoded to the check results that obtains the MSC/ SGSN that " Extended Check IMEI Ack " information and sending sends " Extended Check IMEI " message to the step S401;

Step S407 identifies these data that inquire and is recorded in whether continue use after this verification is finished, and namely whether this data record only relates to current mobile device; Be then, execution in step S408, otherwise change step S409 over to;

Step S408, the data record that deletion is mated from local mobile device tabulation;

Step S409 sends " Update ME Info Request " message to CEIR, has comprised IMEI, current ES and possible information such as IMSI, MSISDN in this message;

Step S410 waits for " the Update ME Info Response " message that comes from CEIR;

Step S411, reception comes from " the Update ME Info Response " message of CEIR and parses the whole parameters that comprise;

Step S412 if do not comprise the instruction that local mobile device tabulation is upgraded in " Update ME Info Response " message, does not namely need to upgrade local mobile device tabulation, then jumps to step S414; Otherwise need to upgrade local mobile device tabulation, enter step S413;

Step S413, the update instruction information editing who carries in described " Update ME Info Response " message is a data record in the described local mobile device tabulation, realization is to the once renewal of local mobile device tabulation, and identifies original EIR for this data record;

Step S414, whether identification exists partner EIR, if wherein described EIR does not have partner EIR, then process ends;

Step S415 is not if cause the direct variation of local mobile device tabulation, then process ends in this checking procedure;

Step S416 generates the synchronic command tabulation according to the change conditions in the local mobile device tabulation; For the newly-increased situation of record, need to mass-send synchronic command to all partner members, therefore, will be that target EIR and the synchronic command that carries newly-increased recorded information add in the synchronic command tabulation one by one with the member in partner member's tabulation; Situation for record deletion, if current EIR is the original EIR of required delete data record, then need to mass-send synchronic command to all partner members, being about to the member in partner member's tabulation is that target EIR and the synchronic command that carries deletion record information add in the synchronic command tabulation one by one, otherwise, only the original EIR to required delete data record sends synchronic command, and the original EIR that is about to required delete data record is that target EIR and the synchronic command that carries deletion record information add in the synchronic command tabulation;

Step S417 obtains a unenforced synchronic command and is encoded to " ME List Syn Request " message;

Step S418, desired target partner EIR sends " ME List Syn Request " message to synchronic command;

Step S419 waits for " the ME List Syn Response " message from target partner EIR;

Step S420 receives and resolves " ME List Syn Response " message from target partner EIR;

Step S421 is if success synchronously then changes step S423 over to;

Step S422 continues then to change step S418 over to, otherwise target EIR is labeled as synchronously but synchronization failure synchronously to target partner EIR if desired, and execution in step S423;

Step S423, the executed synchronic command of deletion from the synchronic command tabulation;

Step S424 if also have unenforced synchronic command, then changes step S417 over to, otherwise, process ends.

Wherein, " the ME List Syn Request " message among step S417 and the step S418 is described first synchronization request message, and " the ME List Syn Response " message among step S419 and the step S420 is described first synchronous response message.

It should be noted that above-mentioned steps is that example is described with the single-threaded processor environment, namely possible record deletion process and possible record increase the local mobile device tabulation that all stops afterwards more synchronous all the relevant EIR of row newly; If but the processor among the EIR is the concurrent processing device, the newly-increased caused simultaneous operation of record deletion and record can be carried out simultaneously, namely after step S408, just can begin to carry out the simultaneous operation (step S414 is to step S424) of record deletion, treat just can begin to record newly-increased simultaneous operation (step S414 is to step S424) after the step S413.

With reference to figure 5, be the method for collaborative verification IMEI provided by the invention, EIR equipment comes from partner EIR's to received " ME List Syn Request " handling process of message:

Step S501 receives and parsing " ME List Syn Request " message from partner EIR, obtains contained mobile device tabulation synchronic command information;

Step S502 if the synchronic command that obtains requires newly-increased data record, then changes step S503 over to, otherwise changes step S504 over to;

Step S503, will from " ME List Syn Request " information editing that parses the message is a record in the local mobile device tabulation, the original EIR of mark also changes step S514 over to;

Step S504, deletion from local mobile device tabulation " ME List Syn Request " the desired record of message;

Step S505, whether be the original EIR of institute delete data record, be then to change step S506 over to, otherwise change step S514 over to if identifying current EIR;

Step S506, with the partner member of this EIR tabulate as treat synchronous EIR tabulation and with the EIR of transmit leg EIR(forwarding step S501 described " ME List Syn Request " message) therefrom deletion;

Step S507 identifies and describedly treats that whether synchronous EIR tabulation has not synchronous as yet EIR, is then to change step S508 over to, otherwise changes step S514 over to;

Step S508, obtain one do not finish synchronous partner EIR as yet and from treat synchronous EIR tabulation with its deletion;

Step S509 sends " ME List Syn Request " message to the target partner EIR that obtains;

Step S510 waits for " the ME List Syn Response " message from target partner EIR;

Step S511 receives and resolves " ME List Syn Response " message from target partner EIR;

Step S512 if target partner EIR has finished synchronously (comprising that the synchronization failure number of times reaches peaked situation), then changes step S507 over to;

Step S513 proceeds subsynchronously if desired, then changes step S509 over to, otherwise changes step S507 over to;

Step S514 sends " ME List Syn Response " message to transmit leg EIR and represents normal the reception and process ends.

As can be seen, above-mentioned EIR equipment has been contained newly-increased synchronous, synchronous and synchronous as the deletion of non-original EIR as the deletion of original EIR to the handling process of received " ME List Syn Request " message that comes from partner EIR;

Wherein, deletion as non-original EIR may be triggered by two kinds of situations synchronously, a kind of situation is that " ME List Syn Request " message from local mobile device tabulation the directly original EIR of variation (record deletion) takes place, and another kind of situation is that " ME List Syn Request " message from local mobile device tabulation the original EIR that the synchronous recording deletion changes takes place; For clarity, the former message can be called first synchronization request message, the latter's message is called second synchronization request message, but this differentiation is not to mean two kinds of " ME List Syn Request " message what has distinguish technically, only be for being convenient to illustrative purposes, become first synchronization request message and " ME List Syn Request " message that the EIR of (record deletion or record are newly-increased) sends is taken place directly to change in local mobile device tabulation; In fact concerning " ME List Syn Request " message of above-mentioned two kinds of different addresses, the synchronous processing mode of deletion that non-original EIR takes is identical.

With reference to figure 6, be the method for collaborative verification IMEI provided by the invention, the concrete handling process in the CEIR equipment:

Step S601 receives and parsing " Update ME Info Request " message from EIR, therefrom obtains IMEI, current ES and possible information such as IMSI, MSISDN;

Step S602, inquiry IMEI central database obtains the IMEI relevant with this mobile device, ES and possible information such as IMSI, MSISDN;

Step S603 compares the information that comes from " Update ME Info Request " message and IMEI central database;

Step S604 judges whether that according to above-mentioned comparative result needs upgrade the mobile device tabulation of storing among the EIR, if do not need to upgrade, then change step S606 over to;

Step S605, according to pre-defined rule information extraction from described IMEI central database, and with it as update instruction; Above-mentioned pre-defined rule for example with TAC, IMEI,＜IMEI, IMSI 〉,＜IMEI, MSISDN 〉,＜IMEI, IMSI, MSISDN 〉,＜IMEI, ~ IMSI 〉,＜IMEI, ~ MSISDN〉be index, but be not limited to the said extracted mode;

Step S606, coding " Update ME info Response " message, coded object or the update instruction that obtains based on step S605, or based on the reception result to " Update ME Info Request " message of step S601;

Step S607 sends " Update ME Info Response " message to EIR;

Step S608, the information that utilization is extracted from " Update ME Info Request " message, as receive the time of IMEI verification message, the source of IMEI verification message and possible IMSI, MSISDN etc., record relevant with described IMEI in the IMEI central database is upgraded.

According to the present invention, a kind of system for collaborative verification IMEI also is provided, the general structure of system 700 comprises CEIR equipment 710, EIR equipment, MSC equipment and SGSN equipment as shown in Figure 7;

EIR equipment is generally a plurality of, adopts an EIR equipment 720, the

2nd EIR equipment

750 and 780 signals of the 3rd EIR equipment here, but and do not mean that in the actual conditions to be three EIR equipment; The one EIR equipment 720 has MSC equipment 730 under its command and SGSN equipment 740, the two EIR equipment 750 have MSC equipment 760 under its command and SGSN equipment 770, the three EIR equipment 780 have MSC equipment 790 and SGSN equipment 7A0 under its command;

The one EIR equipment 720, the 2nd EIR equipment 750 and the 3rd EIR equipment 780 are the EIR for collaborative verification IMEI provided by the present invention.Wherein, an EIR equipment 720 and the 2nd EIR equipment 750 is partner EIR each other, and the 2nd EIR equipment 750 and the 3rd EIR equipment 780 is partner EIR each other.

Partner member's tabulation is set in each equipment identity register EIR; And the data record that each equipment identity register EIR tabulates for local mobile device separately at initial phase arranges original EIR sign, and is preferable, and also the data record for local mobile device tabulation separately arranges life cycle.

Above-mentioned each EIR720,750 and 780 concrete structure and function are participated in the detailed description below in conjunction with accompanying drawing 8.

The present invention also provides the EIR that is used for collaborative verification IMEI, and the one preferred embodiment as shown in Figure 8;

EIR 800 for collaborative verification IMEI provided by the present invention comprises:

Be used for to realize the unit 810 of quick IMEI verification, should be used for realizing that the unit of quick IMEI verification was mutual with MSC equipment/SGSN equipment and CEIR equipment 710, be used for the quick IMEI verification of realization; And should be used for realizing that the unit 810 of quick IMEI verification comprised local mobile device tabulation 8101, and be used for record and be useful on the instruction of upgrading mobile device status;

Specifically, should be used for realizing that the unit 810 of quick IMEI verification was used for inquiring about local mobile device tabulation 8101 after the IMEI check request message that receives MSC equipment/SGSN equipment transmission;

If should have the data record that is complementary with this mobile device in this locality mobile device tabulation 8101, and then require final ES is set according to tabulation, otherwise keep current ES constant; If only relating to this mobile device, the described record that is complementary with this mobile device from local mobile device tabulation 8101, deletes described record;

The unit 810 that should be used for realize quick IMEI verification target ES(is not namely had to resolve the ES that obtains when being complementary record or have when being complementary record require set ES according to tabulation) send to MSC/SGSN as check results with the form of " Extended Check IMEI Ack " (IMEI verification response of expansion) message, thereby MSC/SGSN determines whether to allow this mobile device to carry out access to netwoks according to the check results of receiving;

Should be used for realize that the unit 810 of quick IMEI verification was corresponding sends " Update ME Info Request " message to CEIR equipment 710, IMEI, current ES(is not namely had to resolve the ES that obtains when being complementary record or have when being complementary record require set ES according to tabulation) and the possible information relevant with mobile device such as IMSI, MSISDN send CEIR equipment 710 to;

And, should be used for realizing that the unit 810 of quick IMEI verification received from CEIR equipment 710 " Update ME Info Response " message, if comprised the instruction that is used for upgrading mobile device status in this message, then according to command request it newly-increasedly is a record in the described local mobile device tabulation.

EIR 800 for collaborative verification IMEI provided by the present invention also comprises:

Partner member tabulates 820, the EIR member list that record and described EIR800 have partnership;

Original EIR arranges module 830, be connected with described local mobile device tabulation 8101 for the unit 810 of realizing quick IMEI verification, be used to the data record of described local mobile device tabulation 8101 that original EIR sign is set, the original EIR that is used for this data record of mark namely is used for this record of mark and triggers and generate because which EIR to carry out quick IMEI verification at first;

Lock unit 840,820 with described original EIR module 830 is set and is connected with described the tabulation for the unit 810, the described partner member that realize quick IMEI verification, be used for when the local mobile device tabulation 8101 of carrying out EIR described in the quick IMEI checking procedure takes place directly to change, described direct variation be synchronized to described partner member tabulate during all members' local mobile device is tabulated in 820; Wherein, described direct variation comprises the newly-increased and/or record deletion of record;

Described record is newly-increased to be comprised: be specially the unit 810 that this is used for realizing quick IMEI verification for described EIR 800() report the IMEI check request of CEIR 710 with regard to a certain mobile device, when it receives when comprising the instruction of upgrading described mobile device status in feedback information that CEIR 710 issues and the described feedback information, then according to command request it is increased newly and be a data record in the described local mobile device tabulation 8101, and by original EIR module 830 is set and adds original EIR sign for described data record, described EIR 800 is labeled as the original EIR of described data record;

Described record deletion comprises: be specially the unit 810 that this be used for to realize quick IMEI verification at described EIR 800() after the data record of local mobile device tabulation 8101 based on it upgrades corresponding mobile device executing state, if described data record only relates to current mobile device, then described EIR 800(is specially this unit 810 that is used for realizing quick IMEI verification) from the described data record of its local mobile device tabulation 8101 deletions;

Optionally, comprise that also life cycle arranges module 850, be connected with local mobile device tabulation 8101 and the described lock unit 840 of the unit 810 of the quick IMEI verification of described realization, be used to the data record of described local mobile device tabulation 8101 that life cycle is set, be used for these data of mark and be recorded in the deadline date that described local mobile device tabulation 8101 is preserved; When the life cycle of a certain data record finishes, then from local mobile device tabulation 8101 with its deletion.

In order to reduce signaling consumption as far as possible and to avoid the information redundancy in the local mobile device tabulation among each EIR, the invention provides a preferred embodiment of lock unit 840, comprising:

The first synchronization request module 8401, tabulate with the unit 810 of the quick IMEI verification of described realization and partner member and 820 to be connected, be used for the direct variation of the described local mobile device tabulation 8101 of identification, if newly-increased for record, then tabulating to partner member, all members send first synchronization request message in 820; If be record deletion, then determine according to the original EIR sign of described data record whether this equipment is the original EIR of described data record, be to tabulate to partner member then that all members send first synchronization request message in 820, otherwise only send first synchronization request message to the original EIR of the original EIR sign institute mark of described data record; Wherein, carry the record newly-added information/record deletion information of described local mobile device tabulation in described first synchronization request message;

Handle synchronously and the second synchronization request module 8402, tabulate 820 with described partner member, life cycle arranges module 850 and with original EIR module 830 is set and is connected, is used for resolving and identifying the synchronization request message that receives,

If obtain the record newly-added information, then carry out the newly-increased operation of record of local mobile device tabulation 8101: described record newly-added information is compiled as a data record in the local mobile device tabulation, and triggering original EIR, the original EIR of module 830 by the described data record of original EIR identity marking is set is transmit leg EIR;

If obtain record deletion information, then carry out the record deletion operation of local mobile device tabulation 8101: the corresponding data record of deletion from local mobile device tabulation 8101, and determine according to the original EIR sign of described data record whether this equipment is the original EIR of described data record, be then to instruct described synchronization request module 8401 all members except transmit leg EIR in the partner member tabulation to send second synchronization request message, wherein, carry the record deletion information of described local mobile device tabulation in described second synchronization request message;

Wherein, the described synchronization request message that receives comprises first synchronization request message and second synchronization request message, that is to say that processing and the second synchronization request module, 8402 received synchronization request message may be first synchronization request message synchronously, also may be second synchronization request message;

It is to be noted, the first/the second synchronization request message that lock unit 840 receives is only distinguished for convenience of explanation, for EIR equipment, therefore this two kinds of synchronization request message and indistinction only need a synchronous processing module (namely handling synchronously and the second synchronization request module 8402) to get final product; Processing and the second synchronization request module 8402 are after receiving synchronization request message and resolving identification synchronously, if newly-increased then execution of record increases newly synchronously, if record deletion, then identify whether original EIR of this equipment, this situation of non-original EIR(means that received synchronization request message may be first synchronization request message, also may be second synchronization request message) then carry out deletion synchronously, be that this situation of original EIR(means that received synchronization request message must be first synchronization request message) then continue that all members except transmit leg EIR send second synchronization request message in partner member's tabulation in the back synchronously in deletion.

Preferable, described lock unit 840 also comprises the sync response receiver module 8403 that is connected with and the processing synchronously and second synchronization request module 8402 of the described first synchronization request module 8401 respectively, and the sync response sending module 8404 that is connected with described synchronous processing and the second synchronization request module 8402;

Described sync response sending module 8404 is used for receiving according to described synchronous processing and the second synchronization request module 8402 triggering of described the first/the second synchronization request message, sends the first/the second synchronous response message to the transmit leg EIR of described the first/the second synchronization request message;

Described sync response receiver module 8403 is used for receiving the first/the second synchronous response message, and feeds back to the described first synchronization request module 8401 and synchronous the processing and the second synchronization request module 8402, confirms that described synchronization request message is correctly received and handles.

Below in conjunction with EIR equipment 720,750 and 780 the characteristics of coming exemplary illustration EIR equipment provided by the present invention alternately, be example so that record deletion to have taken place:

The one EIR equipment 720 receives the IMEI check request and carries out the processing procedure from MSC equipment 730 or SGSN equipment 740, if (record deletion) takes place directly to change in its local mobile device tabulation, then identification described directly be changed to record deletion after, whether identify this equipment is the original EIR that treats delete data record;

In the present embodiment, suppose that an EIR equipment 720 is not the original EIR that treats delete data record, original EIR is the 2nd EIR equipment 750; Therefore, an EIR equipment 720 sends first synchronization request message to the 2nd EIR equipment 750, and finishes the current processing procedure of this equipment after receiving first synchronous response message;

The 2nd EIR equipment 750 receives first synchronization request message from an EIR equipment 720, then carries out desired record deletion operation; Subsequently, this equipment of identification by the original EIR of data record of requirement deletion, therefore send second synchronization request message to the 3rd EIR equipment 780, wait for and receive second synchronous response message, and to an EIR equipment 720 transmissions first synchronous response message, finish the current processing procedure of this equipment afterwards;

The 3rd EIR equipment 780 receives second synchronization request message from the 2nd EIR equipment 750, then carries out desired record deletion operation; Subsequently, identifying this equipment is not the original EIR of the data record of deletion that requires, and therefore finishes the current processing procedure of this equipment after sending second synchronous response message to the 2nd EIR equipment 750.

In sum, by technical scheme provided by the invention, result in IMEI verification each time all is updated among the partner EIR synchronously, and no matter next time verification is to occur among the EIR that carries out this verification in the partner EIR of described EIR, the instruction that the ES to mobile device that this verification generates upgrades all can be carried out by the EIR that carries out verification next time, the result of this verification can be fully utilized, and avoided owing to mobile device roams into outside the coverage of the EIR that carries out this verification this check results being lost efficacy, further avoid described mobile device is restarted the process of identification and renewal ES, avoided delaying of check results entry-into-force time;

And, only need store local mobile device tabulation in EIR equipment and the partner EIR equipment thereof, and a lot of data record that only relate to current mobile device in this tabulation can be deleted after using synchronously, so it is generally very short to tabulate, not only improve the speed of IMEI verification, also can avoid using the large data library software, thereby reach the purpose of reducining the construction costs.

The present invention is illustrated by above-described embodiment, but should be understood that, above-described embodiment just is used for for example and illustrative purposes, but not is intended to the present invention is limited in the described scope of embodiments.It will be appreciated by persons skilled in the art that in addition the present invention is not limited to above-described embodiment, can also make more kinds of variants and modifications according to instruction of the present invention, these variants and modifications all drop in the present invention's scope required for protection.Protection scope of the present invention is defined by the appended claims and equivalent scope thereof.

Claims

1. a method that is used for collaborative verification International Mobile Station Equipment Identification IMEI is characterized in that, may further comprise the steps:

2. method according to claim 1 is characterized in that, the step that EIR described in the described step S2 is synchronized to described direct variation in the local mobile device tabulation of all members in its partner member tabulation comprises:

Step S21: described EIR identifies described direct variation;

3. method according to claim 2 is characterized in that, comprises that also the EIR that receives described the first/the second synchronization request message sends the first/the second synchronous response message to the transmit leg EIR of described the first/the second synchronization request message.

4. according to the arbitrary described method of claim 1 to 3, it is characterized in that also being included in when executive logging is newly-increased to be operated is that corresponding data record arranges life cycle, is used for these data of mark and is recorded in the deadline date that EIR preserves; When the life cycle of a certain data record finishes, the described data record of deletion from local mobile device tabulation.

5. equipment identity register EIR who is used for collaborative verification International Mobile Station Equipment Identification IMEI, it comprises for the unit of realizing quick IMEI verification; It is characterized in that, also comprise:

6. EIR according to claim 5 is characterized in that, described lock unit comprises:

7. EIR according to claim 6, it is characterized in that, described lock unit also comprises the sync response receiver module that is connected with and the processing synchronously and second synchronization request module of the described first synchronization request module respectively, and the sync response sending module that is connected with described synchronous processing and the second synchronization request module;

8. according to the arbitrary described EIR of claim 5 to 7, it is characterized in that, comprise that also life cycle arranges module, be connected with described lock unit, being used for when the newly-increased operation of executive logging is that corresponding data record arranges life cycle, is used for these data of mark and is recorded in the deadline date that EIR preserves; When the life cycle of a certain data record finishes, the described data record of deletion from local mobile device tabulation.

9. system that is used for collaborative verification International Mobile Station Equipment Identification IMEI, comprise equipment identity register EIR and respectively with mutual mobile services switching centre MSC/ Serving GPRS Support Node SGSN and the central equipment marker register CEIR of described EIR, it is characterized in that described EIR is the arbitrary described EIR of claim 5-8.