CN101692641A - High effective HLR/AUC data daily auditing method - Google Patents
High effective HLR/AUC data daily auditing method Download PDFInfo
- Publication number
- CN101692641A CN101692641A CN200810219746A CN200810219746A CN101692641A CN 101692641 A CN101692641 A CN 101692641A CN 200810219746 A CN200810219746 A CN 200810219746A CN 200810219746 A CN200810219746 A CN 200810219746A CN 101692641 A CN101692641 A CN 101692641A
- Authority
- CN
- China
- Prior art keywords
- data
- hlr
- auc
- cycle
- boss
- 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.)
- Granted
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method for auditing HLR/AUC data daily. The method comprises the following steps: collecting instruction log file updated in an auditing period, updating stored HLR/AUC data in the system based on the updated instruction log file; analyzing the updated HLR/AUC data, collecting and analyzing work order execution data in BOSS in an auditing period to obtain the change of the data in HLR, AUC and BOSS in one auditing period; based on the change, obtaining junk authentication data and data difference list in AUC; performing existing network auditing to the junk authentication data and data difference list, and turning on a module to perform synchronization and store the synchronous result through the service of BOSS. The method of the invention can be used nearly without additional resources occupation to HLR/AUC, ensure the high effective data consistency checking of core network element HLR/AUC so that the normalization of data consistency auditing can be realized daily and save the precious resource in HLR/AUC.
Description
Technical field
The present invention relates to business support and core net, particularly, relate to a kind of HLR/AUC data daily auditing method.
Background technology
BOSS (business operation support system) is the main body network element of China Mobile's supporting network, is the support platform that China Mobile carries out client's service handling, service charging and customer data storage.The mobile subscriber carries out product subscription, service release and service payment of fees by BOSS to network and business platform, and commmunication company stores, uses service to charge to the user user data by BOSS.
HLR (attaching position register)/AUC (AUC) is mainly used in the network element of preserving the leading subscriber data in China Mobile's core net.HLR mainly preserves mobile subscriber business information, and related business comprises whole mobile traditional businesses and a large amount of mobile new business.AUC preserves the user's who moves authentication information.HLR/AUC is the core of mobile service operation, the resource of HLR/AUC equipment also is very valuable and limited, the swift and violent growth of the user of China Mobile at present, the resource of HLR/AUC equipment is under the prerequisite that ensures ordinary production and high customer satisfaction in the existing core net, and it is few to have more than needed.
User's business information all has management in BOSS, HLR, AUC, these are kept at business information coordinated on the different network elements and have finished China Mobile user's complete service is provided.
Yet, owing to cooperating reasons such as flow process imperfection, transfer of data fault, network element device catastrophic failure, business administration imperfection between each network element, inconsistent situation has appearred in the data that cause being kept in these network elements, the deposition in present network element because inconsistent situation appears in historical problem is arranged, also have because new inconsistent data every day that the new problem new situation is caused.These inconsistent data have caused serious problems such as customer complaint increase, customer satisfaction decline, commmunication company's losses of revenues, mobile network resource waste again.
Disclose the inconsistent monitoring process method of data between a kind of network element at one piece of application number in the Chinese patent application file of " 200710049384.6 ", in " the provincial business operation support system of China Mobile (BOSS) service technique standard (3.0.0) ", also the method has been made detailed description.
Described method comprises: require the network element data that is consistent from BOSS and other network element collections, again data corresponding in data and the BOSS are resolved, are compared the tabulation of generation difference, after data difference is carried out validation verification, in conjunction with synchronization rules generate synchrodata and be sent to BOSS and other network elements in carry out data simultaneous operation, data are consistent.The mode that described collection employing full dose collection and incremental crawler combine is from the network element image data; Described full dose collection requires network element to derive the data that all requirements are consistent; Described incremental crawler is at the data that require to be consistent, and only gathers the data that last acquisition time changes in the current acquisition time.
The inconsistent detection processing method of existing elements data is that a kind of universal method is not optimized at the actual conditions and the characteristics that move each network element, so the inconsistent testing of data is not accomplished optimum to the resource occupation of network element in the practical application.The core network element HLR/AUC that for example data consistency is most important in detecting, content is maximum, resource at its equipment is extremely valuable and limited, few characteristics more than needed under the prerequisite that ensures ordinary production and high customer satisfaction, there is following shortcoming in the existing inconsistent detection processing method of network element data:
During 1) from HLR/AUC collection incremental data, require HLR/AUC to derive the data that last acquisition time changes in the current acquisition time, and present most HLR/AUC equipment does not all provide such data to derive instrument, makes that this incremental data acquisition method can't promotion and implementation.
2) at gathering incremental data from HLR/AUC, the method that a kind of accommodation is arranged at present is the data that change in the current acquisition time according to last acquisition time among the BOSS, provide real-time query statement by HLR/AUC, in HLR/AUC, inquire about up-to-date data one by one and finish the comparison of follow-up data, but there are two problems the most serious in the method for this accommodation: the one, adopt this mode can't find in HLR/AUC, to take place variation and the inconsistent data that in BOSS, do not change; The 2nd, at single HLR/AUC get business change data volume about about 1000 among the BOSS present every day, all need in HLR/AUC, carry out the online query of one or many for carrying out these data of consistency detection, in general the data query instruction is a bigger instruction of consumption of natural resource among the HLR/AUC, therefore the system resource of HLR/AUC equipment is additionally taken is bigger to this method, What is more, when mobile sales promotion or other peak traffic occurring, get the business change data volume at single HLR/AUC among the BOSS and can become quite big every day, the business change of carrying out these flood tides will take a large amount of HLR/AUC device resources originally, and need to take a large amount of system resource and be used for real-time inquiry in order to carry out consistency detection, can cause HLR/AUC system resource problem more serious like this.
3) existing method be a kind of be the data mismatch detection method at center with BOSS, it mainly is to find that the data between BOSS and each network element are inconsistent, but do not consider the inconsistent situation of data between inner HLR of core network element and the AUC, and this inconsistent meeting causes AUC to go up a large amount of rubbish authorization data of generation, waste HLR/AUC and gone up valuable system resource, exist in a large number in the actual production of this situation, must be handled.
4) when HLR/AUC gathers the full dose data, require HLR/AUC to derive the data that all requirements are consistent, the provisional derivation of this total data has additionally increased the system resources consumption of HLR/AUC.During the derivation of total data, may lower HLR/AUC at some HLR/AUC, reduce and carry out efficient producing the response time of instruction, individual cases down in addition the equipment that can meet accident restart.And have indivedual HLR/AUC equipment not provide interim data to derive means, make this full dose collecting method to implement.
Therefore, the present invention wishes to propose a kind of method, be used for solving the detection efficiency problem of network element data consistency detection at core network element HLR/AUC, take and accomplish minimum finishing between HLR/AUC and the BOSS in the daily fast detecting of data consistency system resource to HLR/AUC, or even additionally do not take the system resource of HLR/AUC, also will remedy simultaneously and can't detect the inconsistent problem of handling between HLR and the AUC of data in the available data consistency detecting method, the data consistency that thoroughly solves between network element detects problem.
Summary of the invention
For this reason, the present invention proposes a kind of method of the HLR/AUC data being carried out daily auditing, comprise: check in the cycle at one, gather the instruction journal file that upgrades, and previous HLR/AUC data of preserving in the system are upgraded based on the instruction journal file of described renewal; Described one check end cycle after, described HLR/AUC data after upgrading are resolved, and BOSS checked that at described one worker in the cycle singly carries out data and gathers and resolve, to obtain data among described HLR, described AUC and the described BOSS in a described variation of checking in the cycle; In a described variation of checking in the cycle, obtain rubbish authorization data and data difference tabulation on the described AUC based on the data among described HLR, described AUC and the described BOSS; Described rubbish authorization data and described data difference tabulation carrying out existing network are verified, and undertaken synchronously and the preservation synchronized result by the service release module of described BOSS immediately.
The method according to this invention improved existing network element data consistency detecting method not high at the efficient that the data consistency of core network element HLR/AUC detects, HLR/AUC system resource is taken big, method exploitativeness and the not strong shortcoming of adaptability; improved the efficient that the core network element data consistency detects; almost there is not extra system resource to take to HLR/AUC; the feasible data consistency of HLR/AUC is checked really accomplished normalization, normalization; and exploitativeness of the present invention is strong, can adapt to nearly all HLR/AUC.
The present invention has replenished the data consistency between the HLR/AUC of core network element inside has been detected, and can find efficiently that AUC goes up a large amount of rubbish authentications that exist, and effectively protects and save valuable system resource on the HLR/AUC.
Among the present invention simultaneously, at first the daily Backup Data of HLR/AUC imports database, carry out at any time renewal by the instruction daily record of real-time collection then, so also effectively formed the backup library of HLR/AUC data, data in this backup library have only delay in 1～2 hour (rise time of depending on HLR instruction daily record) with the HLR/AUC data in producing, this database can provide the query function of HLR/AUC data to some to the less demanding system of real-time, as the statistical analysis of HLR/AUC user data, searching fast etc. of customer complaint HLR side reason, effective system queries pressure of having shunted HLR/AUC.
The method according to this invention is based on the mobile core network element data daily auditing of HLR/AUC log collection; HLR/AUC almost there is not extra resource occupation; it is efficient to have guaranteed that core network element HLR/AUC data consistency detects, and makes the data consistency to check can to accomplish daily normalization to be carried out.And the method according to this invention detects at the data consistency between the HLR/AUC of core network element inside, finds a large amount of rubbish authentications on the AUC, the method for the valuable system resource on protection and the saving HLR/AUC.
Description of drawings
Fig. 1 shows the system logic framework according to the HLR/AUC data auditing system of exemplary embodiment of the invention; And
Fig. 2 shows the HLR/AUC data daily auditing flow chart according to exemplary embodiment of the invention.
Embodiment
Below in conjunction with accompanying drawing, the present invention is done detailed elaboration.
Fig. 1 shows the system logic framework according to the HLR/AUC data auditing system of exemplary embodiment of the invention.Difference and traditional tri-level logic framework, HLR/AUC data auditing system adopts four layers of logical architecture based on Business Rule Engine, on the basis of traditional tri-level logic framework, introduced the business rule layer again, by flexible deployment, make the system flexibility of HLR/AUC data auditing system and extensibility reach a unprecedented height to business rule.
Wherein, data Layer is mainly used in preserves the relevant various data of HLR/AUC data auditing system, and these data comprise: the various initial data that collect from HLR/AUC and BOSS, check intermediate data, check and handle result data and system's running log.Wherein upgrade synchronously according to the HLR/AUC data that in time collect HLR instruction daily record in the audit system, can guarantee in the audit system the HLR/AUC data with produce in HLR/AUC data basically identical, between data delay have only 1～2 hour usually (rise time of depending on HLR instruction daily record), so the HLR/AUC data in the audit system can be to some to the less demanding system of real-time, as the statistical analysis of HLR/AUC user data, searching fast etc. of customer complaint HLR side reason, provide the query function of HLR/AUC data effective shunted the system queries pressure of HLR/AUC.
The business rule layer comprises Business Rule Engine and business rule base.Wherein main business rule all is stored in the business rule base, as HLR log collection rule, the single collection rule of BOSS worker, HLR daily record resolution rules, data comparison rules, data sync rule etc.The corn module of system is called execution by Business Rule Engine to the business rule that is kept in the business rule base, to realize the miscellaneous service function.Business rule can upgrade in online deployment, can not influence the normal operation of whole system, but by the newly-increased and upgrade-system smooth evolution to business rule, supports the data consistency of new network element and new business to detect processing.
Application layer comprises data acquisition, data preliminary treatment, data auditing, data check, the data sync five functional module of core, these functional modules all are by Business Rule Engine the corresponding service rule that is kept in the business rule base to be called execution, to realize its business function, so their configuration is very flexible.Data acquisition module is mainly finished functions such as the daily Backup Data collection of HLR, HLR instruction log collection, the data acquisition of BOSS full dose, the collection of BOSS worker's forms data.Data preprocessing module mainly be responsible for to the various data that collect resolve accordingly, verification and standardization.The data auditing module mainly is responsible for according to the data comparison rules data that each side participates in checking being compared, and generates the data difference tabulation.Data check module and data simultaneous module coordinated are finished the existing network of data difference tabulation are verified with synchronously.
Boundary layer has comprised man-machine interface and machine machine interface.Wherein man-machine interface mainly is the inquiry and the statement analysis of business rule configuration, system monitoring alarm, system management and data, and machine machine interface mainly is system acquisition interface and the sync cap of system acquisition interface and sync cap, audit system and the BOSS of audit system and HLR/AUC.
Fig. 2 shows the HLR/AUC data daily auditing flow chart according to exemplary embodiment of the invention.Below, be described in detail in conjunction with the daily auditing flow process of flow chart with reference to Fig. 2 HLR/AUC data auditing system.
1) data daily auditing of HLR/AUC was undertaken by the cycle, and this cycle can be 1 week, 1 day or several hours, and the minimum cycle of checking is that the instruction daily record of HLR/AUC forms cycle, normally 1 hour this cycle;
2) cycle of checking begin the back system can check constantly whether HLR present instruction journal file closes;
3) if the instruction journal file is not closed, then repeat 2～3 step, if closing of a file is then gathered this journal file;
4) according to the new instruction journal file that collects, the HLR/AUC data in the update system under preserving during the full dose data auditing last time make it keep up-to-date state;
5) if the not end of the current cycle of checking, then repeat 2～5 step, if the current end cycle of checking, then parsing is integrated in the HLR/AUC instruction daily record that collects before, and reject last one and check data in synchronization content in the cycle, obtain the data cases that HLR/AUC upward changes in this cycle;
6) current check end cycle in, finish BOSS gone up the collection that worker in this cycle singly carries out data, these workers are singly resolved, and reject last one and check data in synchronization content in the cycle, obtain that BOSS goes up the data cases of variation in this cycle;
7) data situation in should the cycle on HLR and the AUC is compared, and obtains the rubbish authorization data on the AUC, and the data situation on HLR/AUC and the BOSS in this cycle is compared obtains the data difference tabulation;
8) after to rubbish authorization data and the verification of data difference tabulation carrying out existing network, undertaken synchronously by the service release module of BOSS immediately, and preserve synchronized result;
9) new the checking the cycle of beginning repeats 1～9 step.
This HLR/AUC data daily auditing flow process does not almost have extra system resource to take to HLR/AUC, make this flow process can normalization, more frequent carrying out.
Above-mentioned execution mode is only for exemplary and nonrestrictive, and by reading this specification, those skilled in the art can make various modifications and variations to above-mentioned execution mode, and do not break away from the spirit and scope of the present invention.Protection scope of the present invention only is defined by the claims.
Claims (5)
1. one kind is carried out the method for daily auditing to the HLR/AUC data, comprising:
Check in the cycle at one, gather the instruction journal file that upgrades, and previous HLR/AUC data of preserving in the system are upgraded based on the instruction journal file of described renewal;
Described one check end cycle after, described HLR/AUC data after upgrading are resolved, and BOSS checked that at described one worker in the cycle singly carries out data and gathers and resolve, to obtain data among described HLR, described AUC and the described BOSS in a described variation of checking in the cycle;
In a described variation of checking in the cycle, obtain rubbish authorization data and data difference tabulation on the described AUC based on the data among described HLR, described AUC and the described BOSS;
Described rubbish authorization data and described data difference tabulation carrying out existing network are verified, and undertaken synchronously and the preservation synchronized result by the service release module of described BOSS immediately.
2. method according to claim 1, wherein, the step of gathering the instruction journal file that upgrades comprises:
Check continuously whether the described instruction journal file among the described HLR closes;
If described instruction journal file is closed, then described instruction journal file is gathered.
3. method according to claim 1, wherein, the described HLR/AUC data after upgrading are resolved and BOSS is checked that at described one the worker in the cycle singly carries out the step that data gather and resolve and comprises:
Described one check end cycle after, described one is resolved and rejected to described HLR/AUC data after upgrading check data in synchronization content in the cycle, to obtain data among described HLR and the described AUC in a described variation of checking in the cycle, simultaneously, the above one of described BOSS is checked that worker in the cycle singly carries out data and gathers and resolve, and reject described one and check data in synchronization content in the cycle, to obtain data on the described BOSS in a described variation of checking in the cycle.
4. method according to claim 1, wherein, described rubbish authorization data is the data on described HLR and the described AUC to be checked at described one that situation of change in the cycle is compared obtain.
5. method according to claim 1, wherein, the tabulation of described data difference checks that at described one the data on variation in the cycle and the described BOSS check at described one that variation in the cycle is compared and obtain with the data on described HLR and the described AUC.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102197466A CN101692641B (en) | 2008-12-08 | 2008-12-08 | High effective HLR/AUC data daily auditing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008102197466A CN101692641B (en) | 2008-12-08 | 2008-12-08 | High effective HLR/AUC data daily auditing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101692641A true CN101692641A (en) | 2010-04-07 |
| CN101692641B CN101692641B (en) | 2011-09-07 |
Family
ID=42081299
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008102197466A Active CN101692641B (en) | 2008-12-08 | 2008-12-08 | High effective HLR/AUC data daily auditing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101692641B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102098699A (en) * | 2010-12-22 | 2011-06-15 | 大唐软件技术股份有限公司 | Method and device for verifying user data in telecommunication system |
| CN102209335A (en) * | 2011-05-24 | 2011-10-05 | 四川奥诚科技有限责任公司 | Method and device for acquiring user data of multiple network element platforms |
| CN102340791A (en) * | 2010-07-21 | 2012-02-01 | ***通信集团福建有限公司 | System used for realizing data consistency and method thereof |
| CN102447798A (en) * | 2010-09-30 | 2012-05-09 | ***通信集团浙江有限公司 | Recharge-for-recovery method and device |
| CN102523620A (en) * | 2012-01-13 | 2012-06-27 | 四川奥诚科技有限责任公司 | Method, device and system for data synchronism |
| CN105933396A (en) * | 2016-04-14 | 2016-09-07 | 北京思特奇信息技术股份有限公司 | Method and system for realizing long flow by cooperating system interfaces of different channels |
-
2008
- 2008-12-08 CN CN2008102197466A patent/CN101692641B/en active Active
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102340791A (en) * | 2010-07-21 | 2012-02-01 | ***通信集团福建有限公司 | System used for realizing data consistency and method thereof |
| CN102447798A (en) * | 2010-09-30 | 2012-05-09 | ***通信集团浙江有限公司 | Recharge-for-recovery method and device |
| CN102447798B (en) * | 2010-09-30 | 2013-12-04 | ***通信集团浙江有限公司 | Recharge-for-recovery method and device |
| CN102098699A (en) * | 2010-12-22 | 2011-06-15 | 大唐软件技术股份有限公司 | Method and device for verifying user data in telecommunication system |
| CN102098699B (en) * | 2010-12-22 | 2013-08-14 | 大唐软件技术股份有限公司 | Method and device for verifying user data in telecommunication system |
| CN102209335A (en) * | 2011-05-24 | 2011-10-05 | 四川奥诚科技有限责任公司 | Method and device for acquiring user data of multiple network element platforms |
| CN102523620A (en) * | 2012-01-13 | 2012-06-27 | 四川奥诚科技有限责任公司 | Method, device and system for data synchronism |
| CN102523620B (en) * | 2012-01-13 | 2015-07-15 | 四川奥诚科技有限责任公司 | Method, device and system for data synchronism |
| CN105933396A (en) * | 2016-04-14 | 2016-09-07 | 北京思特奇信息技术股份有限公司 | Method and system for realizing long flow by cooperating system interfaces of different channels |
| CN105933396B (en) * | 2016-04-14 | 2018-11-13 | 北京思特奇信息技术股份有限公司 | A kind of each canalization interface of collaboration realizes the method and system of long flow |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101692641B (en) | 2011-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101692641B (en) | High effective HLR/AUC data daily auditing method | |
| CN103699580B (en) | Database synchronization method and device | |
| CN104199666B (en) | A kind of application program Dynamic Configuration and device | |
| CN110245078A (en) | A kind of method for testing pressure of software, device, storage medium and server | |
| CN101542478B (en) | Methods and apparatus for improving data warehouse performance | |
| CN110300963A (en) | Data management system in large-scale data repository | |
| CN107391649A (en) | A kind of system and method for lifting block chain query efficiency | |
| CN102638378B (en) | Mass storage system monitoring method integrating heterogeneous storage devices | |
| CN105933446A (en) | Service dual-active implementation method and system of big data platform | |
| CN107657052A (en) | A kind of data governing system based on metadata management | |
| CN100433650C (en) | Method and system for synchronizing network administration data in network optimizing system | |
| CN102521128B (en) | Software fault tolerance method facing cloud platform | |
| CN101436207A (en) | Data restoring and synchronizing method based on log snapshot | |
| CN109146653B (en) | Distributed environment-based accounting daily cutting checking method and device | |
| CN105512336A (en) | Method and device for mass data processing based on Hadoop | |
| CN108399199A (en) | A kind of collection of the application software running log based on Spark and service processing system and method | |
| CN102236672A (en) | Method and device for importing data | |
| CN101321207B (en) | Failure processing method of telecommunication customer service system database | |
| EP1938193A2 (en) | Revenue management system and method | |
| CN105913233A (en) | SDK processing method suitable for application client end payment | |
| CN104506348A (en) | Method for automatically discovering and configuring monitoring object | |
| CN110245145A (en) | Structure synchronization method and apparatus of the relevant database to Hadoop database | |
| CN109656999A (en) | Method of data synchronization, equipment, storage medium and the device of big data quantity | |
| CN109039710B (en) | Routing data auditing method, device, server and storage medium | |
| CN102902777A (en) | Cross data source inquiry device and cross data source inquiry method |
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 |