CN102136963B - Method and system for checking data consistency - Google Patents

Abstract

The present invention provides a data consistency checking method, comprising the following steps: when the home location register (HLR) detects an active event, it acquires corresponding static service data according to the user identification associated with the active event, and sends out the static service data, wherein the static service data is The business data contains the user ID; after the verification system receives the static business data, it obtains the corresponding static business data from the customer relationship management system CRM according to the user ID, and compares the static business data obtained from the CRM with the static business data from the HLR In comparison, when the static service data obtained from the CRM is inconsistent with the static service data from the HLR, the static service data in the HLR is updated according to the static service data obtained from the CRM. The invention also provides a data consistency checking system. The range of static business data comparison in the embodiment of the present invention is used to reduce the resources occupied and the time consumed by data consistency verification.

Description

Method and system for checking data consistency

technical field

The invention relates to the technical field of network communication, in particular to a data consistency checking method and system.

Background technique

The communication network established by the telecom operator often includes many communication devices. Due to various considerations, user data (such as service data describing user-subscribed services) often have copies stored on more than one communication device. In order to avoid problems such as billing errors caused by inconsistent user data stored on each communication device, telecom operators often need to perform a consistency check on the user data on each communication device. With the rapid increase in the number of users, data consistency verification takes up more and more resources and takes longer and longer, which increasingly threatens the normal delivery of communication services.

Contents of the invention

Embodiments of the present invention provide a method and system for verifying data consistency, which can reduce resources occupied and time consumed by data consistency verification.

An embodiment of the present invention provides a data consistency verification method, including: when the home location register (HLR) detects an active event, obtains the corresponding static service data according to the user identification associated with the active event, and sends the static service data. Service data, wherein the static service data includes the user identifier;

After the verification system receives the static service data, it obtains the corresponding static service data from the customer relationship management system CRM according to the user identification, compares the static service data obtained from the CRM with the static service data from the HLR, and then When the static service data obtained from the CRM is inconsistent with the static service data from the HLR, the static service data in the HLR is updated according to the static service data obtained from the CRM.

The embodiment of the present invention also provides a data consistency verification system, including: a home location register HLR, used to obtain corresponding static service data according to the user identification associated with the active event when an active event is detected, and send The static service data, wherein the static service data includes the user identifier;

The verification system is used to obtain the corresponding static service data from the customer relationship management system CRM according to the user identification after receiving the static service data, and compare the static service data obtained from the CRM with the static service data from the HLR In comparison, when the static service data obtained from the CRM is inconsistent with the static service data from the HLR, the static service data in the HLR is updated according to the static service data obtained from the CRM.

The above technical solution reduces the workload of verification by limiting the range of users who need to verify data. When the Home Location Register (HLR, Home Location Register) detects an active event, the HLR will only use the user identification associated with the active time. Obtain corresponding static service data, and send the static service data. After the inspection system receives the static business data sent by the HLR, it obtains the static business data corresponding to the user ID from the customer relationship management system (CRM, Customer Relationship Management) according to the user ID, and the static business data obtained from the CRM Compared with the static service data from the HLR, when the two are inconsistent, the static service data in the HLR is updated with the static service data acquired by the CRM. The verification system in this solution only verifies the static business data corresponding to users with active events. This greatly reduces the scope of static business data comparison, thereby reducing the resources and time consumed by data consistency verification.

Description of drawings

Fig. 1 is a flowchart of a data consistency checking method according to an embodiment of the present invention;

Fig. 2 is a flowchart of a data consistency checking method according to another embodiment of the present invention;

FIG. 3 is a signaling diagram of a data consistency checking method according to an embodiment of the present invention;

Fig. 4 is a structural diagram of a data consistency checking device according to an embodiment of the present invention;

Fig. 5 is a structural diagram of a data consistency checking system according to an embodiment of the present invention;

Fig. 6 is a structural diagram of a data consistency checking system according to another embodiment of the present invention.

Detailed ways

First, a method for implementing a data consistency check in the embodiment of the present invention is described, including: when the home location register HLR detects an active event, obtains the corresponding static service data according to the user identification associated with the active event, and sends The static service data, wherein the static service data includes the user identifier;

After the verification system receives the static service data, it obtains the corresponding static service data from the customer relationship management system CRM according to the user identification, compares the static service data obtained from the CRM with the static service data from the HLR, and then When the static service data obtained from the CRM is inconsistent with the static service data from the HLR, the static service data in the HLR is updated according to the static service data obtained from the CRM.

The specific implementation of the present invention will be described in detail below in conjunction with the accompanying drawings.

Referring to FIG. 1 , this figure is a flow chart of Embodiment 1 of the data consistency checking method provided by the present invention.

Method embodiment one:

S101: When the HLR detects an active event, obtains corresponding static service data according to the user ID associated with the active event, and sends the static service data, wherein the static service data includes the user ID;

Specifically, when receiving a registration request or a location update request from the visitor location register VLR, the HLR determines that an active event has been detected, and the user identification associated with the active event is included in the registration request or location update request. User ID in . Or, when receiving the service change request, the HLR determines that an active event has been detected, and the user ID associated with the active event is the user ID included in the service change request.

S102: After the verification system receives the static service data, it obtains the corresponding static service data from the CRM according to the user ID, compares the static service data obtained from the CRM with the static service data from the HLR, and obtains the static service data from the CRM When the obtained static service data is inconsistent with the static service data from the HLR, the static service data in the HLR is updated according to the static service data obtained from the CRM.

Specifically, the verification system comparing the static business data obtained from the CRM with the static business data from the HLR specifically includes: the verification system fuses at least one piece of business work order data from the static business data of the HLR , generating fused business work order data; the verification system will fuse at least one piece of business work order data in the static business data obtained from the CRM to generate fused business work order data; the verification system will The fused business ticket data from the HLR is compared with the fused business ticket data from the CRM.

In addition, the verification system is a data consistency system or a service provisioning system.

The data consistency verification method provided in this embodiment reduces the workload of verification by limiting the range of users who need to verify data. When HLR detects an active event, HLR obtains the corresponding user ID according to the active time. static business data and send out the static business data. After the inspection system receives the static service data sent by the HLR, it obtains the static service data corresponding to the user identifier from the CRM according to the user identifier, and compares the static service data obtained from the CRM with the static service data from the HLR, When the two are inconsistent, the static service data in the HLR is updated with the static service data acquired by the CRM. The verification system in this solution only verifies the static business data corresponding to users with active events. This greatly reduces the scope of static business data comparison, thereby reducing the resources and time consumed by data consistency verification.

Method embodiment two:

Referring to FIG. 2 , this figure is a flow chart of another embodiment of the data consistency checking method provided by the present invention.

In this embodiment, when the HLR receives a registration request or a location update request from a visitor location register (VLR, Vsitor LocationRegister), the HLR determines that an active event has been detected, and the user identification associated with the active event is included in the The user ID in a registration request or a location update request.

The verification system in this embodiment is a data consistency system or a service provisioning system.

S201: After the HLR receives the user's registration request or location update request sent by the VLR, it sends the user's static service data to the VLR, and at the same time copies the static service data to a data consistency system or a service provisioning system; The user's registration request or location update request is forwarded to the VLR by the user through a base station controller (BSC, Base Station Controller).

S202: The HLR receives the verification result obtained by the data consistency system or the service provisioning system after comparing the static service data with the user service data from the CRM, and when the verification result is inconsistent with the data, the The user service data of the CRM is used as a reference to modify the static service data of the user.

In another case, when the HLR receives the user's service change request, the HLR determines that an active event has been detected, and the user ID associated with the active event is the user ID included in the service change request.

The data consistency verification method provided by this embodiment only compares the users whose static service data is sent by the HLR to the VLR (users who initiate registration requests or location updates) or users whose services change. No comparison will be performed to determine whether the data is consistent. Therefore, this method narrows down the range of users to be compared, and can complete the verification of the data consistency of users who are currently using the service in a relatively short period of time.

Method embodiment three:

Referring to FIG. 3 , the figure is a signaling diagram of the data consistency check provided by the embodiment of the present invention.

S1: The user sends a registration request or a location update request to the BSC.

The registration request is sent by the user when the phone is turned on again. For example, when the mobile phone user buys a SIM card and uses it for the first time, the registration request is sent to the BSC.

When the user checks that the current location area identification (LAI, Location Area Identification) is inconsistent with the LAI in the SIM card, the user sends a location update request to the BSC.

S2: The BSC sends the user's registration request or location update request to the VLR or Mobile Switching Center (MSC, Mobile Switch Center).

S3: The VLR or MSC sends the user's registration request or location update request to the HLR.

S4: The HLR sends the static service data of the user who sends the registration request or the location update to the VLR.

S5: At the same time, the HLR copies the static service data of the user sent to the VLR to the data consistency system or the service provisioning system.

It should be noted that when there is a static service data update in the HLR, the HLR sends the updated information of the static service data to the VLR, and copies the updated information of the static service data to the data consistency system or service Activate the system.

In this embodiment, preferably, the HLR uses the MAP message to send the user's static service data to the VLR and copy it to the data consistency system or the service provisioning system.

S6: The data consistency system or service provisioning system analyzes the received static service data of the user and converts it into usable user service data. That is: before the data consistency system or the service activation system compares the static service data obtained from the CRM with the static service data from the HLR, it also includes: the checking system compares at least one service item from the HLR static service data Fusing single data; fusing at least one piece of business work order data in the static business data obtained from the CRM. Thereafter, the above comparison process is to compare the fused static service data from the HLR with the fused static service data from the CRM.

It should be noted that the step S6 can be performed at any time after the data consistency system or the service provisioning system receives the user's static service data, and the time of its occurrence is not specifically limited.

For example, RBT=1 indicates that the user has subscribed to the RBT service, and RBT=0 indicates that the user has not subscribed to the RBT service.

S7: Under normal circumstances, CRM, E-CARE or Interaction Voice Response (IVR, Interaction Voice Response) sends the user's daily business requests to the data consistency system or service provisioning system.

It should be noted that there is no sequential relationship between S7 and other steps, and S7 may occur at any time.

S8: The data consistency system or the service provisioning system verifies the static service data from the HLR and the user service data from the CRM according to predetermined rules.

The predetermined rule is user key data or comparison period.

For example, the key data of a CRM user is: user level, including four levels of platinum, gold, silver and common.

For example, the rules of CRM user data consistency itself, that is, the comparison period, performs data consistency verification on a certain user in the last n months.

The data consistency system or service provisioning system uses the method described in S6 to process the user's static service data from the HLR.

The data consistency system or the service provisioning system adopts the traditional method of actively triggering and querying the CRM for the user business data from the CRM, usually using the webservice interface; this embodiment preferably uses the existing business work order data of the data consistency system or the service provisioning system Fusion first.

The method for merging business work order data will be introduced below in combination with specific examples.

First introduce the meaning of each letter:

ADD3GSUB-Add 3G subscriber: open a new 3G subscriber

MSISDN: mobile phone number

IMSI: card number

CLIP-Call Line Identify Presentation: Caller ID

CLIR-Call Line Identify Restriction: Incoming calls are banned

CFU-Call Forward Unconditional: forward unconditionally

CFB-Call Forward Busy: forward busy

VOICE: voice service

SMST-Short Message Service Terminate: Short message receiving service

SMSO-Short Message Service Original: short message sending service

OPENIDD-Open International Direct Dial: Open international direct dial authority

IDD-International Direct Dial: International Direct Dial Service

The number 1 means that the service needs to be opened; the number 0 means that the service does not need to be opened. For example, CLIP=1 indicates that the caller ID service needs to be activated; CFU=0 indicates that the unconditional forwarding service does not need to be activated.

Command 1:

ADD3GSUB: MSISDN＝123456; CLIP＝1; CLIR＝1; CFU＝0; CFB＝1; VOICE＝1; , CLIR, CFB, VOICE, SMST, and SMSO services, but the CFU service does not need to be activated.

Command 2:

OPENIDD: MSISDN=123456; IDD=1; is an instruction to open IDD, and IDD service needs to be opened in this instruction.

Instruction 1 occurs when the user opens an account, and instruction 2 occurs at any time after account opening (that is, when the user applies). For data consistency verification, the data consistency system or service provisioning system can generate a record for the user's MSISDN or IMSI at ordinary times, and integrate the user's business information at different times.

Although instruction 1 and instruction 2 occurred at different times, they both belong to the same mobile phone number MSISDN=123456, so the accumulated business information of this user is: CLIP=1; CLIR=1; CFU=0; CFB=1; VOICE =1; SMST=1; SMSO=1; IDD=1.

The above-mentioned business information fusion of command 1 and command 2 can be completed at ordinary times, so that when doing data consistency verification, there is no need to integrate the business information of the previous N commands and then statically copy the user information with the HLR Compare business data. Because the business information fusion of instructions is performed during the comparison, which will reduce efficiency.

S9: If the data consistency system or the service provisioning system finds that the two data are inconsistent in the verification result, it sends a modification instruction to the HLR, so that the HLR modifies its own user's static service data to be consistent with the CRM's user service data.

S10: The HLR feeds back the result of the data modification to the data consistency system or the service provisioning system.

The method for data consistency verification provided by this embodiment limits the scope of users of data verification to the users who are actually using it at present, which reduces the scope of data consistency verification, thereby reducing the amount of visits to HLR and CRM. Therefore, the impact on normal business of CRM or HLR can be alleviated.

Method embodiment four:

The data consistency verification method provided by the present invention also increases the cache of the static service data from the HLR and the static service data from the CRM on the verification system. When performing data consistency verification in the future, if there is static service data that needs to be checked in the cache of the verification system, there is no need to obtain static service data from the HLR and CRM.

The embodiment of the present invention also provides a data consistency checking device.

Referring to FIG. 4 , this figure is a structural diagram of the device embodiment 1 provided by the embodiment of the present invention.

The data consistency verification device provided in this embodiment includes: a receiving unit 401, a sending unit 402, a copying unit 403, a verification result receiving unit 404, and a modifying unit 405;

The receiving unit 401 is configured to receive a user's registration request or location update request sent by the visitor location register VLR;

The sending unit 402 is used to send the user's static service data to the VLR; at the same time, the copy unit 403 is used to copy the static service data to a data consistency system or a service opening system; the user's A registration request or a location update request is forwarded by the user to the VLR via the base station controller BSC;

A verification result receiving unit 404, configured to receive a verification result obtained after the data consistency system or the service provisioning system compares the static business data with the user business data from the customer relationship management system CRM;

The modifying unit 405 is configured to modify the user's static service data based on the CRM user's service data when the verification result is that the data is inconsistent.

The data consistency checking device provided in this embodiment only needs to send the static service data of the user in use to the VLR, and the user in use is the user sending a registration request or a location update request. This narrows the scope of data consistency verification, not all users in CRM perform data consistency verification, which also reduces access to data consistency verification devices, thereby reducing the need for data consistency verification devices impact on normal business.

The data consistency verification device provided by the embodiment of the present invention further includes a feedback unit 406, configured to feed back the static service data of the user modified by the modification unit to the data consistency system or the service provisioning system.

The embodiment of the invention also provides a data consistency checking system.

Referring to FIG. 5 , this figure is a structural diagram of a data consistency checking system provided by an embodiment of the present invention.

The data consistency verification system provided in this embodiment includes:

The HLR501 is configured to obtain corresponding static service data according to the user ID associated with the active event when an active event is detected, and send the static service data, wherein the static service data includes the user ID;

Specifically, the HLR501 is used to determine that an active event is detected when receiving a registration request or a location update request from the visitor location register VLR, and the user identification associated with the active event is included in the registration request or the location update request. The user ID in the update request. In addition, the HLR501 is configured to determine that an active event has been detected when receiving a service change request, and the user ID associated with the active event is the user ID included in the service change request.

The verification system 502 is configured to obtain the corresponding static service data from the CRM503 according to the user ID after receiving the static service data, compare the static service data obtained from the CRM503 with the static service data from the HLR501, and then When the static service data obtained from the CRM503 is inconsistent with the static service data from the HLR501, the static service data in the HLR501 is updated according to the static service data obtained from the CRM503.

Specifically, the checking system 502 is further used for:

Fusing at least one piece of business work order data from the static business data of HLR501 to generate fused business work order data; fusing at least one piece of business work order data from the static business data obtained from the CRM503 to generate fused Business work order data; compare the fused business work order data from HLR501 with the fused business work order data from CRM503.

Specifically, the verification system is a data consistency system or a service provisioning system.

The data consistency verification system provided in this embodiment reduces the workload of verification by limiting the range of users who need to verify data. When HLR detects an active event, HLR obtains the corresponding user ID according to the active time. static business data and send out the static business data. After the inspection system receives the static service data sent by the HLR, it obtains the static service data corresponding to the user identifier from the CRM according to the user identifier, and compares the static service data obtained from the CRM with the static service data from the HLR, When the two are inconsistent, the static service data in the HLR is updated with the static service data acquired by the CRM. The verification system in this solution only verifies the static business data corresponding to users with active events. This greatly reduces the scope of static business data comparison, thereby reducing the resources and time consumed by data consistency verification.

Referring to FIG. 6 , this figure is a schematic diagram of another data consistency checking system provided by the present invention.

The data consistency checking system provided in this embodiment also includes a VLR601.

HLR501 is used for when receiving registration request or location update request from visiting location register VLR601, determine to detect active event, the user identification associated with described active event is the user identification included in described registration request or location update request .

In another case, the HLR 501 is configured to determine that an active event has been detected when receiving a service change request, and the user ID associated with the active event is the user ID included in the service change request. In this embodiment, when a user initiates a registration request or a location update request, it is regarded as an active event.

Before the verification system compares the static business data obtained from CRM503 with the static business data from HLR501, it is also used to: fuse at least one business work order data from HLR501 static business data;

Fusing at least one piece of business work order data among the static business data acquired from the CRM503.

VLR601 is used to send the user's registration request or location update request from the BSC to HLR501.

It should be noted that the user's registration request or location update request is sent to the BSC by the user.

The registration request is sent by the user when the phone is turned on again. For example, when the mobile phone user buys a SIM card and uses it for the first time, the registration request is sent to the BSC.

When the user checks that the current LAI is inconsistent with the LAI in the SIM card, the user will send a location update request to the BSC.

HLR501 is used to send the user's static service data to VLR601, and simultaneously copy the user's static service data to the data consistency system or service provisioning system;

The data consistency system or service activation system is used to compare the user service data from the CRM503 with the static service data of the user from the HLR501, and if the two are inconsistent, send a modification instruction to the HLR501;

The HLR501 is configured to modify the static service data of the local user based on the user service data of the CRM503 according to the modification instruction.

The data consistency verification system provided by the present invention limits users for data consistency verification, and only performs data consistency verification for users who initiate registration requests or location update requests, thus reducing the scope of data consistency verification. At the same time, the visit to HLR501 is also reduced, and the impact on normal business of HLR501 is alleviated.

CRM503 is configured to send the user's daily service request to the HLR through the data consistency system or the service provisioning system.

The HLR501 sends the user's static service data to the visiting home register through the MAP message, and at the same time copies the user's static service data to the data consistency system or the service provisioning system through the MAP message.

Before the data consistency system or service provisioning system 502 compares the static business data obtained from the CRM503 with the static business data from the HLR501, it is also used to: fuse at least one business work order data from the static business data of the HLR501;

Fusing at least one piece of business work order data among the static business data acquired from the CRM503.

The method of data fusion is described in detail below.

The data consistency system or service provisioning system analyzes the static service data of users from HLR501 and converts them into user service data; first fuses the user service data from VLR601 with service work order data and merges them into one piece of user service data, and then Compare.

In this embodiment, the static service data of users from HLR501 is converted into usable user service data, and the user service data from VLR601 are first fused into one piece of user service data, and then compared to achieve data consistency verification.

It should be noted that the data consistency verification system provided by the embodiment of the present invention also adds caches for the static service data from the HLR and the static service data from the CRM to the verification system. When performing data consistency verification in the future, if there is static service data that needs to be checked in the cache of the verification system, there is no need to obtain static service data from the HLR and CRM.

Those of ordinary skill in the art can understand that all or part of the steps in the implementation of the above method can be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium, and the program can be executed when executed. , may include the contents of the foregoing communication method implementations. The storage medium referred to here, such as: ROM/RAM, magnetic disk, optical disk, etc.

In summary, the method for verifying data consistency provided by the embodiments of the present invention reduces the workload of verification by limiting the range of users who need to verify data. When the HLR detects an active event, the HLR will Obtain the corresponding static service data according to the user identification associated with the active time, and issue the static service data. After the inspection system receives the static service data sent by the HLR, it obtains the static service data corresponding to the user identifier from the customer relationship management system CRM according to the user identifier, and combines the static service data obtained from the CRM with the static service data from the HLR The data is compared, and when the two are inconsistent, the static service data in the HLR is updated with the static service data acquired by the CRM. The verification system in this solution only verifies the static business data corresponding to users with active events. This greatly reduces the scope of static business data comparison, thereby reducing the resources and time consumed by data consistency verification.

Those of ordinary skill in the art can understand that all or part of the steps in the method of the above-mentioned embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, and the program can be executed during execution When detecting an active event, the home location register HLR obtains corresponding static service data according to the user identification associated with the active event, and sends the static service data, wherein the static service data includes Said User ID;

After the verification system receives the static service data, it obtains the corresponding static service data from the customer relationship management system CRM according to the user identification, compares the static service data obtained from the CRM with the static service data from the HLR, and then When the static service data obtained from the CRM is inconsistent with the static service data from the HLR, the static service data in the HLR is updated according to the static service data obtained from the 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.

Images