CN102136963B - Method and system for checking data consistency - Google Patents
Method and system for checking data consistency Download PDFInfo
- Publication number
- CN102136963B CN102136963B CN 201010527697 CN201010527697A CN102136963B CN 102136963 B CN102136963 B CN 102136963B CN 201010527697 CN201010527697 CN 201010527697 CN 201010527697 A CN201010527697 A CN 201010527697A CN 102136963 B CN102136963 B CN 102136963B
- Authority
- CN
- China
- Prior art keywords
- data
- static traffic
- traffic data
- user
- hlr
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a method for checking data consistency, comprising the following steps of: when a home location register (HLR) detects activity events, acquiring corresponding static service data according to a user identification associated with the activity events, and sending out the static service data, wherein the static service data includes user identifications; after a checking system receives the static service data, acquiring the corresponding static service data from a customer relationship management (CRM) system according to the user identifications, and comparing the static service data acquired from the CRM system with the static service data from the HLR; and when the static service data acquired from the CRM system and the static service data from the HLR are inconsistent, updating the static service data in the HLR according to the static service data acquired from the CRM system. The invention further provides a system for checking data consistency. Through the embodiment of the invention, the comparison range of the static service data is greatly shortened, and thus occupied resource and consumed time for the data consistency checking are reduced.
Description
Technical field
The present invention relates to network communications technology field, particularly a kind of data consistency method of calibration and system.
Background technology
The communication network that telecommunications operator is set up often comprises numerous communication equipments.For multiple consideration, user data (for example describing the business datum of user's subscription services) often has copy on a more than communication equipment.For avoiding occurring because of the inconsistent problems such as billing error that cause of the user data of storing on each communication equipment, telecom operators often need to carry out consistency desired result to the user data on each communication equipment.Along with riseing fast of number of users, the shared resource of data consistency verification gets more and more, and is consuming time also more and more longer, day by day threatens the normal delivery of communication service.
Summary of the invention
The embodiment of the present invention provides a kind of data consistency method of calibration and system, can reduce the duration of the shared resource of data consistency verification and consumption.
The embodiment of the present invention provides a kind of method of data consistency verification, comprise: attaching position register HLR is detecting when enlivening event, enliven the user ID that event is associated and obtain corresponding static traffic data according to described, and send described static traffic data, comprise described user ID in wherein said static traffic data;
Check system is after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
The embodiment of the present invention also provides a kind of data consistency check system, comprise: attaching position register HLR, be used for detecting when enlivening event, enliven the user ID that event is associated and obtain corresponding static traffic data according to described, and send described static traffic data, comprise described user ID in wherein said static traffic data;
Check system, be used for after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
Above technical scheme, need the user's of checking data scope to reduce the workload of verification by restriction, angelica location register (HLR, Home Location Register) detect when enlivening event, HLR just obtains corresponding static traffic data according to the user ID that this enlivens the time correlation connection, and sends described static traffic data.After checking system is received the described static traffic data that HLR sends, the described user ID of foundation is from CRM system (CRM, Customer Relationship Management) obtain static traffic data corresponding to this user ID in, the static traffic data that to obtain from CRM and comparing from the static traffic data of HLR, when both are inconsistent, with the static traffic data that CRM obtains, the static traffic data in HLR are upgraded.Check system in this programme only verification has the static traffic data corresponding to user of the event of enlivening.So greatly dwindle the scope of static traffic comparing, reduced the duration of the shared resource of data consistency verification and consumption with this.
Description of drawings
Fig. 1 is the flow chart according to the data consistency method of calibration of one embodiment of the invention;
Fig. 2 is the flow chart according to the data consistency method of calibration of another embodiment of the present invention;
Fig. 3 is the signaling diagram according to the data consistency method of calibration of one embodiment of the invention;
Fig. 4 is the structure chart according to the data consistency calibration equipment of one embodiment of the invention;
Fig. 5 is the structure chart according to the data consistency check system of one embodiment of the invention;
Fig. 6 is the structure chart according to the data consistency check system of another embodiment of the present invention.
Embodiment
At first the embodiment of the present invention is realized that a kind of method of data consistency verification describes, comprise: attaching position register HLR is detecting when enlivening event, enliven the user ID that event is associated and obtain corresponding static traffic data according to described, and send described static traffic data, comprise described user ID in wherein said static traffic data;
Check system is after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
Introduce in detail specific implementation of the present invention below in conjunction with accompanying drawing.
Referring to Fig. 1, this figure is embodiment one flow chart of data consistency method of calibration provided by the invention.
Embodiment of the method one:
S101:HLR is detecting when enlivening event, enlivens the user ID that event is associated and obtains corresponding static traffic data according to described, and send described static traffic data, comprises described user ID in wherein said static traffic data;
Specifically, when receiving from the registration request of VLR Visitor Location Register VLR or position updating request, described HLR assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described registration request or position updating request.Perhaps, when receiving the business change request, described HLR assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described business change request.
S102: check system is after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
Specifically, the static traffic data that described check system will obtain from CRM compare specifically with the static traffic data from HLR and comprise: described check system will merge from least one business work forms data HLR static traffic data, generates the business work forms data after merging; Described check system merges at least one business work forms data from the static traffic data that described CRM obtains, and generates the business work forms data after merging; Described check system will and compare from the business work forms data after the fusion of CRM from the business work forms data after the fusion of HLR.
In addition, described check system is data consistency system or service release system.
The data consistency method of calibration that the present embodiment provides needs the user's of checking data scope to reduce the workload of verification by restriction, when HLR detects when enlivening event, HLR just obtains corresponding static traffic data according to the user ID that this enlivens the time correlation connection, and sends described static traffic data.After checking system is received the described static traffic data that HLR sends, obtain static traffic data corresponding to this user ID according to described user ID from CRM, the static traffic data that to obtain from CRM and comparing from the static traffic data of HLR, when both are inconsistent, with the static traffic data that CRM obtains, the static traffic data in HLR are upgraded.Check system in this programme only verification has the static traffic data corresponding to user of the event of enlivening.So greatly dwindle the scope of static traffic comparing, reduced the duration of the shared resource of data consistency verification and consumption with this.
Embodiment of the method two:
Referring to Fig. 2, this figure is another embodiment flow chart of data consistency method of calibration provided by the invention.
In the present embodiment, HLR is receiving from VLR Visitor Location Register (VLR, when registration request Vsitor LocationRegister) or position updating request, HLR assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described registration request or position updating request.
Check system in the present embodiment is data consistency system or service release system.
After S201:HLR receives the user's that VLR sends registration request or position updating request, send described user's static traffic data to described VLR, copy simultaneously described static traffic data to data consistency system or service release system; Described user's registration request or position updating request are transmitted to described VLR by described user through base station controller (BSC, Base Station Controller).
S202: described HLR receives the check results that described data consistency system or service release system obtain after comparing to described static traffic data with from the user service data of CRM, when check results is data when inconsistent, revise described user's static traffic data take the user service data of described CRM as benchmark.
Also have a kind of situation to be, HLR is when the business change request of receiving the user, and HLR assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described business change request.
The method of the data consistency verification that the present embodiment provides only relatively HLR issue this part user (initiating more New Consumers of registration request or position) of VLR static traffic data or this part user of business change occur, do not have like this user that business is used not compare to judge whether data are consistent, therefore, the method has been dwindled the user's of comparison scope, can complete the verification of the user's who is using business at present data consistency within a short period of time.
Embodiment of the method three:
Referring to Fig. 3, this figure is the signaling diagram of the data consistency verification that provides of the embodiment of the present invention.
S1: the user sends registration request or position updating request to BSC.
To be the user send when new start registration request, and for example, the cellphone subscriber has bought SIM card when using first, sends registration request to BSC.
The user is checked through LAI in current residing location area (LAI, Location Area Identification) and SIM card when inconsistent, sends position updating request to BSC.
S2:BSC sends to VLR or mobile switching centre (MSC, Mobile Switch Center) with user's registration request or position updating request.
S3:VLR or MSC send to HLR with user's registration request or position updating request.
S4:HLR will send registration request or position more the static traffic data of New Consumers send to VLR.
S5:HLR will send to user's the static traffic data copy of VLR to data consistency system or service release system simultaneously.
Need to prove, when the static traffic Data Update was arranged in HLR, HLR sent to described VLR with the information of described static traffic Data Update, and the information that copies simultaneously described static traffic Data Update is to described data consistency system or service release system.
In the present embodiment, preferably, HLR utilizes MAP message that user's static traffic data are issued VLR and copy to data consistency system or service release system.
S6: the user's that data consistency system or service release system docking are received static traffic data are resolved, and are converted to available user service data.That is: the static traffic data that will obtain from CRM of described data consistency system or service release system also comprise before comparing with static traffic data from HLR: described check system will merge from least one business work forms data HLR static traffic data; At least one business work forms data from the static traffic data that described CRM obtains is merged.After this, above-mentioned comparison procedure is and will compares from the static traffic data of the fusion of HLR and static traffic data from the fusion of CRM.
Need to prove, this step of S6 can be to carry out any time after data consistency system or service release system receive user's static traffic data, does not specifically limit the time of its generation.
For example, RBT=1 represents that the user has opened the RBT business, and RBT=0 represents that the user does not open the RBT business.
S7: under normal circumstances, CRM, E-CARE or Interaction Voice Response (IVR, Interaction VoiceResponse) send the daily service request of user to data consistency system or service release system.
Need to prove, S7 and other steps do not have the sequencing relation, and S7 may occur in any time.
S8: data consistency system or service release system according to pre-defined rule to carrying out verification from the static traffic data of HLR with from the user service data of CRM.
Described pre-defined rule is user's critical data or comparison cycle.
For example CRM user's critical data is: user class comprises platinum, yellow gold, silver and common four ranks.
For example the rule of CRM user data consistence itself, namely compare the cycle, and certain user of nearest n month is carried out the data consistency verification.
Data consistency system or the service release system method to adopting S6 to describe from the processing of the user's of HLR static traffic data.
Data consistency system or the service release system mode to inquiring about CRM from the traditional active triggering of the user service data employing of CRM is used the webservice interface usually; The present embodiment preferred usage data consistency system or service release system existing business work forms data first merges.
Below in conjunction with object lesson, the method that business work forms data merges is introduced.
The implication of each letter representative of paper:
ADD3GSUB-Add 3G subscriber: the user who newly opens a 3G
MSISDN: phone number
IMSI: card number
CLIP-Call Line Identify Presentation: caller identification
CLIR-Call Line Identify Restriction: incoming call is prohibited aobvious
CFU-Call Forward Unconditional: Call Forwarding Unconditional
CFB-Call Forward Busy: divert when busy
VOICE: speech business
SMST-Short Message Service Terminate: short message receiving is conquered business
SMSO-Short Message Service Original: short message sends business
OPENIDD-Open International Direct Dial: open the international direct dial authority
IDD-International Direct Dial: international direct dial business
Numeral 1 expression need to be opened this business; Numeral 0 expression does not need to open this business.Such as CLIP=1 represents to open the caller identification business; CFU=0 represents not need to open the Call Forwarding Unconditional business.
Instruction 1:
ADD3GSUB:MSISDN=123456; CLIP=1; CLIR=1; CFU=0; CFB=1; VOICE=1; SMST=1; SMSO=1; Be an instruction of opening 3G subscription, need to open CLIP, CLIR, CFB, VOICE, SMST and SMSO business in this instruction, but do not need to open the CFU business.
Instruction 2:
OPENIDD:MSISDN=123456; IDD=1; Be an instruction of opening IDD, need to open the IDD business in this instruction.
Instruction 1 occurs in the user when opening an account, whenever (be user apply for time) after instruction 2 occurs in and opens an account.For the data consistency verification, data consistency system or service release system can produce a record at MSISDN or the IMSI for the user at ordinary times, and the user is merged in the business information of different time.
Although instruction 1 and instruction 2 occur in the different time, all belong to same phone number MSISDN=123456, so this user's business information is accumulated and is exactly: CLIP=1; CLIR=1; CFU=0; CFB=1; VOICE=1; SMST=1; SMSO=1; IDD=1.
Above business information with instruction 1 and instruction 2 merges and can complete at ordinary times, like this when doing the data consistency verification, just do not need again will before user's static traffic data of merging again with the HLR copy of the business information of N bar instruction compare.Because doing the business information fusion of instruction in comparison can lower efficiency again.
S9: if data consistency system or service release system's discovery check results are inconsistent for both data, send modify instruction to HLR, so that the user's of HLR modification self static traffic data are consistent with the user service data of CRM.
S10:HLR with the result feedback of data modification to data consistency system or service release system.
The method of the data consistency verification that the present embodiment provides, the user scope of data check is defined as the user who is really using at present, dwindled like this scope of data consistency verification, thereby reduce the visit capacity to HLR and CRM, therefore can alleviate the impact to the regular traffic of CRM or HLR.
Embodiment of the method four:
Data consistency method of calibration provided by the invention also increases on check system from the static traffic data of HLR with from the buffer memory of the static traffic data of CRM.When carrying out the data consistency verification afterwards, if be cached with the static traffic data that need check and correction in check system, need not to obtain the static traffic data from HLR and CRM again.
The embodiment of the present invention also provides a kind of data consistency calibration equipment.
Referring to Fig. 4, this figure is apparatus embodiments one structure chart that the embodiment of the present invention provides.
The data consistency calibration equipment that the present embodiment provides comprises: receiving element 401, transmitting element 402, copy cell 403, check results receiving element 404 and revise unit 405;
Described receiving element 401 is for the user's who receives VLR Visitor Location Register VLR transmission registration request or position updating request;
Described transmitting element 402 is used for to the described user's of described VLR transmission static traffic data; Described copy cell 403 simultaneously is used for copying described static traffic data to data consistency system or service release system; Described user's registration request or position updating request are transmitted to described VLR by described user through base station controller BSC;
Check results receiving element 404 is used for receiving the check results that obtains after described data consistency system or service release system compare to described static traffic data with from the user service data of CRM system CRM;
Described modification unit 405 when check results is data when inconsistent, is used for revising described user's static traffic data take the user service data of described CRM as benchmark.
The static traffic data that the data consistency calibration equipment that the present embodiment provides only needs to send the user who is using to VLR get final product, and the user who is using is for sending the user of registration request or position updating request.Dwindled like this scope of data consistency verification, be not with carrying out per family the data consistency verification to all in CRM, so also reduce the access to data consistency desired result equipment, thereby reduced the impact to the regular traffic of data consistency desired result equipment.
The data consistency calibration equipment that the embodiment of the present invention provides also comprises feedback unit 406, is used for revising unit amended user's static traffic data feedback to described data consistency system or service release system.
The embodiment of the present invention also provides a kind of data consistency check system.
Referring to Fig. 5, this figure is the structure chart of the data consistency check system that provides of the embodiment of the present invention.
The data consistency check system that the present embodiment provides comprises:
HLR501 is used for detecting when enlivening event, enlivens the user ID that event is associated and obtains corresponding static traffic data according to described, and send described static traffic data, comprises described user ID in wherein said static traffic data;
Specifically, described HLR501 is used for when receiving from the registration request of VLR Visitor Location Register VLR or position updating request, assert the event of enlivening that detects, described to enliven the user ID that event is associated be the user ID that is included in described registration request or position updating request.In addition, described HLR501 is used for when receiving the business change request, assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described business change request.
Check system 502, be used for after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM503, the static traffic data that to obtain from CRM503 compare with the static traffic data from HLR501,, according to the static traffic data of obtaining from CRM503, the described static traffic data described HLR501 are upgraded when inconsistent from the static traffic data of HLR501 in the static traffic data of obtaining from CRM503.
Specifically, described check system 502 is further used for:
To merge from least one business work forms data in HLR501 static traffic data, generate the business work forms data after merging; At least one business work forms data from the static traffic data that described CRM503 obtains is merged, generate the business work forms data after merging; To and compare from the business work forms data after the fusion of CRM503 from the business work forms data after the fusion of HLR501.
Specifically, described check system is data consistency system or service release system.
The data consistency check system that the present embodiment provides needs the user's of checking data scope to reduce the workload of verification by restriction, when HLR detects when enlivening event, HLR just obtains corresponding static traffic data according to the user ID that this enlivens the time correlation connection, and sends described static traffic data.After checking system is received the described static traffic data that HLR sends, obtain static traffic data corresponding to this user ID according to described user ID from CRM, the static traffic data that to obtain from CRM and comparing from the static traffic data of HLR, when both are inconsistent, with the static traffic data that CRM obtains, the static traffic data in HLR are upgraded.Check system in this programme only verification has the static traffic data corresponding to user of the event of enlivening.So greatly dwindle the scope of static traffic comparing, reduced the duration of the shared resource of data consistency verification and consumption with this.
Referring to Fig. 6, this figure is the schematic diagram of another kind of data consistency check system provided by the invention.
The data consistency check system that the present embodiment provides also comprises VLR601.
HLR501 is used for when receiving from the registration request of VLR Visitor Location Register VLR601 or position updating request, assert the event of enlivening that detects, described to enliven the user ID that event is associated be the user ID that is included in described registration request or position updating request.
Also have another kind of situation, HLR501 is used for when receiving the business change request, assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described business change request.In the present embodiment, regard as the event of enlivening when initiating registration request or position updating request with the user.
The static traffic data that described check system will obtain from CRM503 also are used for before comparing with the static traffic data from HLR501: will merge from least one business work forms data of HLR501 static traffic data;
At least one business work forms data from the static traffic data that described CRM503 obtains is merged.
VLR601 is used for and will sends to HLR501 from the user's of BSC registration request or position updating request.
Need to prove, user's registration request or position updating request are issued BSC by the user.
To be the user send when new start registration request, and for example, the cellphone subscriber has bought SIM card when using first, sends registration request to BSC.
The user is checked through LAI in current residing LAI and SIM card can send position updating request to BSC when inconsistent.
HLR501 is used for user's static traffic data are sent to VLR601, simultaneously user's static traffic data copy is given described data consistency system or service release system;
Described data consistency system or service release system are used for and will compare from the user service data of CRM503 and the static traffic data from the user of HLR501, if both are inconsistent, send modify instruction to HLR501;
HLR501 is used for revising local user's static traffic data according to described modify instruction as benchmark take the user service data of described CRM503.
Data consistency check system provided by the invention defines the user of data consistency verification, only the user who initiates registration request or position updating request is carried out the data consistency verification, has dwindled like this scope of data consistency verification.Also reduce simultaneously the access to HLR501, alleviated the impact to the HLR501 regular traffic.
CRM503 is used for the routine work request to HLR transmission user by described data consistency system or service release system.
HLR501 sends to the visiting home register by MAP message with user's static traffic data, gives described data consistency system or service release system by MAP message with user's static traffic data copy simultaneously.
The static traffic data that data consistency system or service release system 502 will obtain from CRM503 also are used for before comparing with the static traffic data from HLR501: will merge from least one business work forms data of HLR501 static traffic data;
At least one business work forms data from the static traffic data that described CRM503 obtains is merged.
Lower mask body is introduced the method for data fusion.
Data consistency system or service release system resolve the static traffic data from the user of HLR501, convert user service data to; To use from the user service data of VLR601 business work forms data first to merge, be merged into a user service data, then compare.
The present embodiment will be converted to available user service data from the user's of HLR501 static traffic data, to first merge from the user service data of VLR601, be merged into a user service data, then both compared, realize the verification of data consistency.
Need to prove, the data consistency check system that the embodiment of the present invention provides also increases on check system from the static traffic data of HLR with from the buffer memory of the static traffic data of CRM.When carrying out the data consistency verification afterwards, if be cached with the static traffic data that need check and correction in check system, need not to obtain the static traffic data from HLR and CRM again.
One of ordinary skill in the art will appreciate that all or part of step that realizes in the said method execution mode is to come the relevant hardware of instruction to complete by program, described program can be stored in computer read/write memory medium, this program can comprise the content of aforesaid each execution mode of communication means when carrying out.Here alleged storage medium, as: ROM/RAM, magnetic disc, CD etc.
In sum, the method of a kind of data consistency verification that the embodiment of the present invention provides, need the user's of checking data scope to reduce the workload of verification by restriction, when HLR detects when enlivening event, HLR just obtains corresponding static traffic data according to the user ID that this enlivens the time correlation connection, and sends described static traffic data.After checking system is received the described static traffic data that HLR sends, obtain static traffic data corresponding to this user ID according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM and comparing from the static traffic data of HLR, when both are inconsistent, with the static traffic data that CRM obtains, the static traffic data in HLR are upgraded.Check system in this programme only verification has the static traffic data corresponding to user of the event of enlivening.So greatly dwindle the scope of static traffic comparing, reduced the duration of the shared resource of data consistency verification and consumption with this.
One of ordinary skill in the art will appreciate that all or part of step that realizes in above-described embodiment method is to come the relevant hardware of instruction to complete by program, described program can be stored in a computer read/write memory medium, this program is when carrying out, comprise the steps: that attaching position register HLR is detecting when enlivening event, enliven the user ID that event is associated and obtain corresponding static traffic data according to described, and send described static traffic data, comprise described user ID in wherein said static traffic data;
Check system is after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
Claims (10)
1. a data consistency method of calibration, is characterized in that, comprises the following steps:
Attaching position register HLR is detecting when enlivening event, enlivens the user ID that event is associated and obtains corresponding static traffic data according to described, and send described static traffic data, comprises described user ID in wherein said static traffic data;
Check system is after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
2. the method for claim 1, it is characterized in that, when receiving from the registration request of VLR Visitor Location Register VLR or position updating request, described HLR assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described registration request or position updating request.
3. the method for claim 1, is characterized in that, when receiving the business change request, described HLR assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described business change request.
4. method as described in any one in claims 1 to 3, it is characterized in that, the static traffic data that described check system will obtain from CRM compare specifically with the static traffic data from HLR and comprise: described check system will merge from least one business work forms data HLR static traffic data, generates the business work forms data after merging;
Described check system merges at least one business work forms data from the static traffic data that described CRM obtains, and generates the business work forms data after merging;
Described check system will and compare from the business work forms data after the fusion of CRM from the business work forms data after the fusion of HLR.
5. method as claimed in claim 4, is characterized in that, described check system is data consistency system or service release system.
6. a data consistency check system, is characterized in that, comprising:
Attaching position register HLR is used for detecting when enlivening event, enlivens the user ID that event is associated and obtains corresponding static traffic data according to described, and send described static traffic data, comprises described user ID in wherein said static traffic data;
Check system, be used for after receiving described static traffic data, obtain corresponding static traffic data according to described user ID from CRM system CRM, the static traffic data that to obtain from CRM compare with the static traffic data from HLR,, according to the static traffic data of obtaining from CRM, the described static traffic data described HLR are upgraded when inconsistent from the static traffic data of HLR in the static traffic data of obtaining from CRM.
7. data consistency check system as claimed in claim 6, it is characterized in that, described HLR is used for when receiving from the registration request of VLR Visitor Location Register VLR or position updating request, assert the event of enlivening that detects, described to enliven the user ID that event is associated be the user ID that is included in described registration request or position updating request.
8. data consistency check system as claimed in claim 6, it is characterized in that, described HLR is used for when receiving the business change request, assert the event of enlivening that detects, and described to enliven the user ID that event is associated be the user ID that is included in described business change request.
9. data consistency check system as described in any one in claim 6 to 8, is characterized in that, described check system is further used for:
To merge from least one business work forms data in HLR static traffic data, generate the business work forms data after merging;
At least one business work forms data from the static traffic data that described CRM obtains is merged, generate the business work forms data after merging;
To and compare from the business work forms data after the fusion of CRM from the business work forms data after the fusion of HLR.
10. data consistency check system as claimed in claim 9, is characterized in that, described check system is data consistency system or service release system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010527697 CN102136963B (en) | 2010-10-27 | 2010-10-27 | Method and system for checking data consistency |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201010527697 CN102136963B (en) | 2010-10-27 | 2010-10-27 | Method and system for checking data consistency |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102136963A CN102136963A (en) | 2011-07-27 |
| CN102136963B true CN102136963B (en) | 2013-06-05 |
Family
ID=44296624
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201010527697 Expired - Fee Related CN102136963B (en) | 2010-10-27 | 2010-10-27 | Method and system for checking data consistency |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102136963B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103559330B (en) * | 2013-10-10 | 2017-04-12 | 上海华为技术有限公司 | Method and system for detecting data consistency |
| CN105813064B (en) * | 2014-12-31 | 2019-08-20 | 华为技术有限公司 | The processing method and network element of service release |
| CN108804464A (en) * | 2017-05-03 | 2018-11-13 | 中兴通讯股份有限公司 | Data consistency detection, device, distributed data base and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1083482A2 (en) * | 1999-09-09 | 2001-03-14 | Nec Corporation | Method of updating client's installed data in response to a user-triggered event |
| CN1399853A (en) * | 1999-08-24 | 2003-02-26 | 艾利森电话股份有限公司 | Methods and systems for handling subscriber data |
| CN1602083A (en) * | 2003-09-22 | 2005-03-30 | 华为技术有限公司 | Management method of honeycomb cluster client's data |
| CN101394666A (en) * | 2008-08-23 | 2009-03-25 | 华为技术有限公司 | Age indication and user data modifying method and apparatus |
-
2010
- 2010-10-27 CN CN 201010527697 patent/CN102136963B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1399853A (en) * | 1999-08-24 | 2003-02-26 | 艾利森电话股份有限公司 | Methods and systems for handling subscriber data |
| EP1083482A2 (en) * | 1999-09-09 | 2001-03-14 | Nec Corporation | Method of updating client's installed data in response to a user-triggered event |
| CN1602083A (en) * | 2003-09-22 | 2005-03-30 | 华为技术有限公司 | Management method of honeycomb cluster client's data |
| CN101394666A (en) * | 2008-08-23 | 2009-03-25 | 华为技术有限公司 | Age indication and user data modifying method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102136963A (en) | 2011-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10021561B2 (en) | Method and apparatus for setting up communication connection | |
| RU2602091C2 (en) | Multichannel communication terminal | |
| JP4676404B2 (en) | Distribution apparatus and program | |
| CN106851617B (en) | Virtual SIM card system and method for mobile terminal to use virtual SIM card | |
| JP4153488B2 (en) | Apparatus and method for storing subscriber data | |
| US7369839B2 (en) | Method and apparatus for determining individual or common mobile subscriber number in mobile network for handling multiple subscribers having the same calling line identity | |
| US20070207839A1 (en) | Network support for mobile special alerting | |
| CN102546989B (en) | The quick forwarding method of complex telephone traffic and system | |
| CN101754189A (en) | Method for realizing multiple-card-one-number service, device and system thereof | |
| CN102136963B (en) | Method and system for checking data consistency | |
| US8326273B2 (en) | System and method for playing a color ring back tone based on the called user's state presence information | |
| CN104581676A (en) | Communication system, mobile communication device, and method for switching user identification information | |
| CN102143447B (en) | SIMM (single IMSI (International Mobile Subscriber Identity) multiple MSISDN ((mobile station international subscriber directory number)) service processing method, SIMM service system and SIMM platform | |
| JP5620808B2 (en) | COMMUNICATION MANAGEMENT DEVICE, MOBILE DEVICE, COMMUNICATION SYSTEM, AND COMMUNICATION MANAGEMENT METHOD | |
| CN101374345B (en) | Method, apparatus and system for transferring wireless virtual private network VPN short number of calling subscriber | |
| Taskin | GSM MSC/VLR Unstructured Supplementary Service Data (USSD) Service | |
| JP2009232414A (en) | Mobile communication system, and subscriber identification code notice apparatus | |
| CN101047969B (en) | Method for channel call in mobile communication network | |
| CN103702302A (en) | Strong call interpolation method and device | |
| US20090080631A1 (en) | Method, apparatus and communication system for renting telephone number | |
| CN102131260B (en) | Method, device and system for implementing call anchoring service | |
| US12082080B2 (en) | Dynamic subscriber profile management | |
| CN100512501C (en) | Information notification method, system and device for mobile intelligent subscriber during international roaming | |
| KR101048269B1 (en) | Apparatus and method for providing a message service | |
| CN100473239C (en) | Dispatching control method based on short message |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130605 Termination date: 20141027 |
|
| EXPY | Termination of patent right or utility model |