CN105635340A - Method and system for intensively integrating power enterprise information system user and telephone user - Google Patents

Abstract

The invention discloses a method and a system for intensively integrating a power enterprise information system user and a telephone user; the method comprises the following steps: a directory system due to business change generates directory system information update and is pushed to a directory system user temporary library of an enterprise unified address book in real time, and a directory system user synchronizes a service to discover an update record, starts a synchronous update task, and synchronizes update information from the directory system to corresponding tables of an enterprise unified address book formal library according to a logic rule; multiple charging system user change information are respectively imported to a charging system user temporary library of the unified address book, and a charging system user synchronizes the service to discover the update record, starts the synchronous update task, and synchronizes the update information from a charging system to the corresponding tables of the enterprise unified address book formal library according to the logic rule. By integrating the information of the power enterprise information network system user and the communication network telephone user, the enterprise unified address book with complete user information, organizational structure information and telephone number information is established.

Description

The method and system of information system for power enterprise user and telephone subscriber's centralized integration

Technical field

The present invention relates to enterprise operation system user profile and the method and system of telephone subscriber's information centralized integration, be specifically related under electrical network provincial Utilities Electric Co. communication network telephone subscriber's information and the method and system of information network business system user centralized integration.

Background technology

At present, information network and communication network within each provincial Utilities Electric Co. of state's genus off the net are to separate, and by safety standard requirements, two networks can not connect in application layer. And in information network, dispose enterprise's a large number of services system, this partial service system user generally uses catalog system and is managed and safeguards; Same, communication network is mainly disposed the system relevant to telephone communication, telephone subscriber generally uses charge system and administers and maintains. Catalog system is called with user and main safeguards user profile, and including user group's structural information, user profile, organizational information are accurate; And charge system is with telephone number for main registration user profile and department information etc., telephone number and telephone position information are accurate. Along with IMS system phased deployment runs, the fusion work of information network and communication network has been achieved with progress, operation system demand based on this two parts user profile is also just arisen at the historic moment, but currently used two network users information still suffer from a lot of problem and difficulty:

(1) catalog system and charge system user profile integrity difference are big. Catalog system user profile is complete, organizational structure accurate, but telephone number and positional information thereof are accurate not as charge system. And charge system user profile is inaccurate, unit information is inaccurate, it does not have complete organizational structure, but telephone number is accurate.

(2) user's update mechanism is different with update content. Catalog system user profile is by office's unified management, and personnel change and are maintained in system in time, and user can revise personal information by door, and information updating mechanism is comparatively perfect, and content update is timely. And charge system only call log or variation just can more fresh information, and update primarily focus on phone and positional information thereof, user profile, organizational information update not in time.

(3) two systems do not have any interface and data exchange. Because two nets separate, not having any interface and data exchange channel between two systems, the valuable part of two parts user profile can not be excavated fully and be utilized.

(4) along with the deployment of IMS, two net fusions progressively realize, but IMS does not have enterprise's address book function, it is impossible to being undertaken integrated by two network users information, worker's user profile of enterprise remains disunity, is separated from each other.

In sum, in the urgent need to setting up a unified address book system, the phone information of centralized integration catalog system user profile and charge system, make full use of the Data renewal mechanism of existing catalog system and charge system, it is achieved electric power enterprise user communication records information completely, content is accurate, it is timely, readily available to update.

Summary of the invention

For solving the deficiency that prior art exists, the invention discloses a kind of method realizing catalog system and the concentration integration of charge system user data, by setting up unified enterprise customer's address book system, it is deployed in the server that IMS core net is special, communication information network and communication network is configured so that Information Network data connect enterprise by proprietary address with port and unify address book system by SBC gateway function. Setting up directory user temporary library between catalog system and unified address list, catalog system is immediately to catalogue temporary library propelling user information; Setting up user's fee temporary library between charge system and unified address list, user and telephone number information are pushed to user's fee temporary library by charge system.

For achieving the above object, the concrete scheme of the present invention is as follows:

The method of information system for power enterprise user and telephone subscriber's centralized integration, comprises the following steps:

Catalog system is because business variation produces catalog system information updating, unified in catalog system user's temporary library of address list by real time propelling movement to enterprise, catalog system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from catalog system is unified to enterprise in the respective table in the formal storehouse of address list;

Multiple charge system user's transition information are by the charge system user's temporary library being directed respectively into unified address list, charge system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from charge system is unified to enterprise in the respective table in the formal storehouse of address list;

Enterprise unifies in the formal storehouse of address list the in store centralized integration enterprise user information of catalog system user and charge system user profile, always initiates entrance for what operation system applied various communication channelss.

Further, information updating content synchronization to enterprise is unified in the formal table of address list by catalog system, concretely comprising the following steps of employing:

Step one: catalog system is by the user information pushing of renewal to the interim table of catalog system user, and interim table includes enterprise user information and the organizational information of catalog system;

Step 2: catalog system user's synchronous service constantly monitors the more fresh information of the interim table of catalog system user;

Step 3: catalog system user's synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set;

Step 4: catalog system user's synchronous service starts result set record is circulated process;

Step 5: take a directory user change record from result set, starts synchronization process;

Step 6: judge that this record is newly-increased amendment, or delete the renewal operation of type;

Step 7: if increasing or amendment operation, then perform newly-increased and modification process;

Step 8: if deletion action, then perform deletion action flow process;

Step 9: whether judged result collection has processed, and completes without process, then return step 5 and continue with;

Step 10: synchronization process of directory user synchronous service terminates.

Further, in step 7, if increasing or amendment operation, then performing newly-increased and modification process, newly-increased and modification process concretely comprises the following steps:

Step 7-1: inquire about enterprise unifies whether there is this user profile in the table of address list formal storehouse by idu;

Step 7-2: without this user profile, then as Adding User process;

Step 7-3: if unifying to inquire about in the table of address list formal storehouse there is this user profile in enterprise, then perform amendment operation;

Step 7-4: the newly-increased or amendment user record end of message.

Further, in step 7-2: without this user profile, then as Adding User process, the process step that Adds User is as follows:

Step 7-2-1: by telephone number from enterprise unifies to inquire about whether there is this user's fee information under same charge system the table of address list formal storehouse;

Step 7-2-2: without user's fee information, then directly unify one record of increase in the table of address list formal storehouse to enterprise;

Step 7-2-3: if there being user's fee information, it is judged that whether this user's fee record exists directory user information;

Step 7-2-4: if there being directory user information, then record and find there are other user profile using same phone number when Adding User information, and unify one record of increase in the table of address list formal storehouse to enterprise;

Step 7-2-5: without directory user information, then this user's fee information is merged with new directory user information.

Further, in step 7-3: if unifying to inquire about in the table of address list formal storehouse there is this user profile in enterprise, then performing amendment operation, it is as follows that amendment operation processes step:

Step 7-3-1: check whether that amendment enterprise unifies user department in the table of address list formal storehouse;

Step 7-3-2: if amendment user department, then judge whether across charge system;

Step 7-3-3: if across charge system, looks into user's fee telephone number in new charge system;

Step 7-3-4: if not across charge system, it may be judged whether amendment charge system telephone number;

Step 7-3-5: if amendment charging telephone number, then according to telephone number query user's fee, otherwise amendment enterprise unifies the user record information in the table of address list formal storehouse;

Step 7-3-6: inquire about user's fee result according to previous step, it may be judged whether have user's fee. Without user's fee, then amendment directory user information, has user's fee information else if, then continue to judge whether this user's fee has directory user information;

Step 7-3-7: if this user's fee record has directory user information, then illustrate to exist the user using same phone number, and record uses user's out of Memory of same phone number, and unifies one record of increase in the table of address list formal storehouse to enterprise;

Step 7-3-8: if enterprise unifies this user's fee record in the table of address list formal storehouse and do not have directory user information, then this user's fee information is merged with the directory user information to increase or to revise.

Further, information updating content synchronization to enterprise is unified in the formal table of address list by charge system, concretely comprising the following steps of employing:

Step A: the user profile of renewal is imported to the interim table of charge system user by charge system, and the interim table of charge system user includes the user profile of charge system, including telephone number information;

Step B: the more fresh information of the user's fee synchronous service periodic monitor interim table of catalog system user;

Step C: user's fee synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set;

Step D: synchronous service starts result set record is circulated process;

Step E: take a directory user change record from result set, starts synchronization process;

Step F: judge that this record is newly-increased amendment, or delete the renewal operation of type;

Step G: if increasing or amendment operation, then perform newly-increased and modification process;

Step H: if deletion action, then perform deletion action flow process;

Step I: whether judged result collection has processed, and completes without process, then return step E and continue with;

Step J: synchronization process of user's fee synchronous service terminates.

Further, in step G: if increasing or amendment operation, then perform newly-increased and modification process; The newly-increased modification process Detailed operating procedures of charge system user profile is as follows:

Step G-1: inquiry enterprise unifies whether to have in the table of address list formal storehouse this charging phone number user information;

Step G-2: without the user's fee information of this telephone number, then as newly-increased user's fee, to the newly-increased user's fee information of formal storehouse table;

Step G-3: if unifying to inquire about in the table of address list formal storehouse there is this user's fee information in enterprise, then amendment charging telephone number related information;

Step G-4: the newly-increased or amendment user's fee record end of message.

Further, in step H: if deletion action, then performing deletion action flow process, it is as follows that charge system user profile deletes flow process thin deletion action step:

Step H-1: unify this user's fee information, if there is no this user profile in the table of address list formal storehouse by charging telephone number query enterprise, then perform step H-5, otherwise continue following steps;

Step H-2: if there is this user's fee information, then check and count whether this record has directory user information, if there is no performs step H-4;

Step H-3: if this record has directory user information, then delete this record charging telephone number information, and this record be set to directory user deletion state, continue step H-5;

Step H-4: perform this record is set to deletion Status Flag;

Step H-5: terminate user's fee synchronization removal handling process.

The system of information system for power enterprise user and telephone subscriber's centralized integration, including:

Catalog system information updating synchronization module, catalog system is because business variation produces catalog system information updating, unified in catalog system user's temporary library of address list by real time propelling movement to enterprise, catalog system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from catalog system is unified to enterprise in the respective table in the formal storehouse of address list;

Charge system information updating synchronization module, multiple charge system user's transition information are by the charge system user's temporary library being directed respectively into unified address list, charge system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from charge system is unified to enterprise in the respective table in the formal storehouse of address list;

Enterprise unifies the formal storehouse of address list and integrates module, and enterprise unifies in the formal storehouse of address list the in store centralized integration enterprise user information of catalog system user and charge system user profile, always initiates entrance for what operation system applied various communication channelss.

Further, in catalog system information updating synchronization module, information updating content synchronization to enterprise is unified in the formal table of address list by catalog system, including:

Catalog system updates info push module, and catalog system is by the user information pushing of renewal to the interim table of catalog system user, and interim table includes enterprise user information and the organizational information of catalog system;

Catalog system user's synchronous service monitoring modular, catalog system user's synchronous service constantly monitors the more fresh information of the interim table of catalog system user;

Catalog system result set forms module, catalog system user's synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set;

Catalog system judge module, it is judged that this record is newly-increased amendment, or delete the renewal operation of type; If increasing or amendment operation, then enter newly-increased and modified module; If deletion action, then enter deletion action module;

Catalog system synchronous processing module, catalog system user's synchronous service starts result set record is circulated process; From result set, take a directory user change record, start synchronization process; Until having processed result set data.

Further, newly-increased and modified module is used for: inquire about enterprise unifies whether there is this user profile in the table of address list formal storehouse by idu; Without this user profile, then as Adding User process, enter the processing module that Adds User; If unifying address list formal storehouse table is inquired about there is this user profile in enterprise, then perform amendment operation; Increase newly or the amendment user record end of message.

Further, the processing module that Adds User for: by telephone number from enterprise unifies to inquire about whether there is this user's fee information under same charge system the table of address list formal storehouse;

Without user's fee information, then directly unify one record of increase in the table of address list formal storehouse to enterprise;

If there being user's fee information, it is judged that whether this user's fee record exists directory user information;

If there being directory user information, then record and find there are other user profile using same phone number when Adding User information, and unify one record of increase in the table of address list formal storehouse to enterprise;

Without directory user information, then this user's fee information is merged with new directory user information.

Further, amendment operation processing module is used for:

Check whether that amendment enterprise unifies user department in the table of address list formal storehouse;

If amendment user department, then judge whether across charge system;

If across charge system, look into user's fee telephone number in new charge system;

If not across charge system, it may be judged whether amendment charge system telephone number;

If amendment charging telephone number, then according to telephone number query user's fee, otherwise amendment enterprise unifies the user record information in the table of address list formal storehouse;

User's fee result is inquired about, it may be judged whether have user's fee according to previous step. Without user's fee, then amendment directory user information, has user's fee information else if, then continue to judge whether this user's fee has directory user information;

If this user's fee record has directory user information, then illustrating to exist the user using same phone number, record uses user's out of Memory of same phone number, and unifies one record of increase in the table of address list formal storehouse to enterprise;

If enterprise unifies this user's fee record in the table of address list formal storehouse does not have directory user information, then this user's fee information is merged with the directory user information to increase or to revise.

Further, charge system information updating synchronization module, information updating content synchronization to enterprise is unified, in the formal table of address list, to specifically include by charge system:

Charge system more fresh information imports module: the user profile of renewal is imported to the interim table of charge system user by charge system, and the interim table of charge system user includes the user profile of charge system, including telephone number information;

Charge system user's synchronous service monitoring modular, the more fresh information of the user's fee synchronous service periodic monitor interim table of catalog system user;

Charge system result set forms module: user's fee synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data;

Charge system judge module: judge that this record is newly-increased amendment, or delete the renewal operation of type; If increasing or amendment operation, then perform charge system and increase newly and modified module; If deletion action, then perform charge system deletion action module;

Charge system synchronous processing module: synchronous service starts result set record is circulated process; From result set, take a directory user change record, start synchronization process; Form result set; Until result set has processed.

Further, charge system is newly-increased is used for modified module:

Inquiry enterprise unifies whether to have in the table of address list formal storehouse this charging phone number user information;

Without the user's fee information of this telephone number, then as newly-increased user's fee, to the newly-increased user's fee information of formal storehouse table;

If unifying address list formal storehouse table is inquired about there is this user's fee information in enterprise, then amendment charging telephone number related information;

Increase newly or the amendment user's fee record end of message.

Further, charge system deletion action module is used for: unifies this user's fee information, if there is no this user profile in the table of address list formal storehouse by charging telephone number query enterprise, then terminates user's fee synchronization removal handling process;

If there is this user's fee information, then check and count whether this record has directory user information, if it does not exist, then perform this record is set to deletion Status Flag;

If this record has directory user information, then delete this record charging telephone number information, and this record is set to directory user deletion state, then terminate user's fee synchronization removal handling process.

Beneficial effects of the present invention:

(1) integration of Information Network System in Electric Power Enterprise user and communication network telephone subscriber's information, builds up user profile, organizational information, enterprise that telephone number information is complete unify address list.

(2) each information system user information in a communication network that solves separates, and user profile is imperfect, independently repeats Input. Making to unify address list construction information system based on enterprise in a communication network convenient easily, user's uniqueness, information integrity are more guaranteed.

(3) solve user profile telephone number information in information network update not in time, the imperfect problem of information. Make each operation system in information network can unify address list based on enterprise easily and increase the functions such as voice call, instant message, multimedia conferencing.

(4) particularly, when realize with wireless network convergence after, enterprise unifies address list can download to intelligent terminal easily, it is achieved unify the extension of intelligent terminal's business function based on address list user by enterprise.

In a word, unify address list by enterprise and realize Enterprise Staff user profile centralized integration, will progressively realize with worker's user-center, by various communication communication channelss, each operation system entrance integrated, carry out the new model of work in every and business.

Accompanying drawing explanation

Fig. 1: system structure composition schematic diagram;

Fig. 2: catalog system user profile synchronizes general flow chart;

Fig. 3: catalog system user profile increases modification process figure newly;

Fig. 4: catalog system user profile deletes flow chart;

Fig. 5: charge system user profile synchronizes general flow chart;

Fig. 6: charge system user profile increases modification process figure newly;

Fig. 7: charge system user profile deletes flow chart.

Detailed description of the invention:

Below in conjunction with accompanying drawing, the present invention is described in detail:

(1) system structure

As Fig. 1 system structure forms shown in schematic diagram, the embodiment of the present invention includes on system structure forms: enterprise unifies the formal storehouse of address list, catalog system user's temporary library, charge system temporary library, catalog system user's synchronous service, the several part of charge system user's synchronous service, additionally involves catalog system and one or more charge system. Flow to according to data message below and describe various piece logical relation:

1. from catalog system to enterprise, unify address book data processing procedure. Catalog system, because business variation produces catalog system information updating, is pushed to enterprise and is unified in catalog system user's temporary library of address list immediately, and this temporary library effect is exactly that the user profile accepted from catalog system updates. Catalog system user's synchronous service finds more new record, start synchronized update task, more fresh information logically regular and synchronized from catalog system is unified to enterprise in the respective table in the formal storehouse of address list (synchronizing flow process detailed step referring to follow-up system handling process part), catalog system user's synchronous service solves the user profile merging treatment Tong Bu come with already present charge system.

2. from charge system to enterprise, unify address book data processing procedure. According to electric power enterprise practical situation, there is multiple charge system situation, therefore multiple charge system user's transition information can by the charge system user's temporary library being directed respectively into unified address list, and this temporary library effect is exactly that the user profile accepted from multiple charge systems updates. Charge system user's synchronous service finds more new record, synchronized update task is started by charge system, more fresh information logically regular and synchronized from charge system is unified in the respective table in the formal storehouse of address list to enterprise, synchronize flow process detailed step referring to follow-up system handling process part, charge system user's synchronous service solve the user profile merging treatment Tong Bu come with already present catalog system.

3. enterprise unifies in the formal storehouse of address list the in store centralized integration enterprise user information of catalog system user and charge system user profile, and what can be used for that operation system applies various communication channelss (phone, note, instant message, mail, video, multimedia conferencing) always initiates entrance.

(2) system handling process

Know that how catalog system user profile and charge system user profile are synchronized, are incorporated into enterprise and unify in address list by the present invention to be described in more detail, be below divided into two parts to be respectively described catalog system user and synchronize flow process and charge system user synchronizes flow process.

1. catalog system synchronizes flow process

As Fig. 2-catalog system user profile synchronizes shown in general flow chart, how the description present invention will work as catalog system user profile (including organizational structure) updates in the formal table that synchronizing information unifies address list to enterprise. Specifically comprise the following steps that

Step 1: catalog system is by the user information pushing of renewal to the interim table of catalog system user, and interim table includes enterprise user information and the organizational information of catalog system.

Step 2: catalog system user's synchronous service constantly monitors the more fresh information of the interim table of catalog system user.

Step 3: catalog system user's synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set.

Step 4: catalog system user's synchronous service starts result set record is circulated process.

Step 5: take a directory user change record from result set, starts synchronization process.

Step 6: judge that this record is newly-increased amendment, or delete the renewal operation of type.

Step 7: if increasing or amendment operation, then perform newly-increased and modification process, and shown in the newly-increased modification process figure of newly-increased modification process such as Fig. 3 catalog system user profile, Detailed operating procedures is as follows:

Step 7-1: inquire about enterprise unifies whether there is this user profile in the table of address list formal storehouse by idu.

Step 7-2: without this user profile, then as Adding User process, the process step that Adds User is as follows:

Step 7-2-1: by telephone number from enterprise unifies to inquire about whether there is this user's fee information under same charge system the table of address list formal storehouse.

Step 7-2-2: without user's fee information, then directly unify one record of increase in the table of address list formal storehouse to enterprise.

Step 7-2-3: if there being user's fee information, it is judged that whether this user's fee record exists directory user information.

Step 7-2-4: if this user's fee record has directory user information, then illustrate to exist the user using same phone number, and record uses user's out of Memory of same phone number, and unifies one record of increase in the table of address list formal storehouse to enterprise.

Step 7-2-5: if enterprise unifies this user's fee record in the table of address list formal storehouse and do not have directory user information, then this user's fee information is merged with the directory user information to increase or to revise.

Step 7-3: if unifying to inquire about in the table of address list formal storehouse there is this user profile in enterprise, then perform amendment operation, and it is as follows that amendment operation processes step:

Step 7-3-1: check whether that amendment enterprise unifies user department in the table of address list formal storehouse.

Step 7-3-2: if amendment user department, then judge whether across charge system.

Step 7-3-3: if across charge system, looks into user's fee telephone number in new charge system.

Step 7-3-4: if not across charge system, it may be judged whether amendment charge system telephone number.

Step 7-3-5: if amendment charging telephone number, then according to telephone number query user's fee, otherwise amendment enterprise unifies the user record information in the table of address list formal storehouse.

Step 7-3-6: inquire about user's fee result according to previous step, it may be judged whether have user's fee. Without user's fee, then amendment directory user information, has user's fee information else if, then continue to judge whether this user's fee has directory user information.

Step 7-3-7: if there being other directory user information, then revise other modification information except charge number in this record, and record an amendment number failure record.

Step 7-3-8: without other directory user information, then a newly-increased former charge number record, and revise this record user profile and merge with new charge number record.

Step 7-4: the newly-increased or amendment user record end of message.

Step 8: if deletion action, then performing deletion action flow process, as Fig. 4-catalog system user profile is deleted shown in flow chart, detailed deletion action step is as follows:

Step 8-1: inquire about enterprise by idu and unify this user profile, if there is no this user profile in the table of address list formal storehouse, then perform step 8-5, otherwise continue following steps.

Step 8-2: if there is this user profile, then check and count whether this record has charging telephone number, if there is no performs step 8-4.

Step 8-3: if this record has charging telephone number, then delete this record directory user information, and this record be set to directory user deletion state, continue step 8-5.

Step 8-4: perform this record is set to deletion Status Flag.

Step 8-5: terminate directory user synchronization removal handling process.

Step 9: whether judged result collection has processed, and completes without process, then continue step 5.

Step 10: synchronization process of directory user synchronous service terminates.

2. charge system synchronizes flow process

As Fig. 5-charge system user profile synchronizes shown in general flow chart, describe how the present invention will update in the formal table that synchronizing information unifies address list to enterprise when charge system user profile. Specifically comprise the following steps that

Step 1: the user profile of renewal is imported to the interim table of charge system user by charge system, the interim table of charge system user includes the user profile (including telephone number information) of charge system.

Step 2: the more fresh information of the user's fee synchronous service periodic monitor interim table of catalog system user.

Step 3: user's fee synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set.

Step 4: synchronous service starts result set record is circulated process.

Step 5: take a directory user change record from result set, starts synchronization process.

Step 6: judge that this record is newly-increased amendment, or delete the renewal operation of type.

Step 7: if increasing or amendment operation, then perform newly-increased and modification process, and shown in the newly-increased modification process figure of newly-increased modification process such as Fig. 6 charge system user profile, Detailed operating procedures is as follows:

Step 7-1: inquiry enterprise unifies whether to have in the table of address list formal storehouse this charging phone number user information.

Step 7-2: without the user's fee information of this telephone number, then as newly-increased user's fee, to the newly-increased user's fee information of formal storehouse table.

Step 7-3: if unifying to inquire about in the table of address list formal storehouse there is this user's fee information in enterprise, then amendment charging telephone number related information.

Step 7-4: the newly-increased or amendment user's fee record end of message.

Step 8: if deletion action, then performing deletion action flow process, as Fig. 7-charge system user profile is deleted shown in flow chart, detailed deletion action step is as follows:

Step 8-1: unify this user's fee information, if there is no this user profile in the table of address list formal storehouse by charging telephone number query enterprise, then perform step 8-5, otherwise continue following steps.

Step 8-2: if there is this user's fee information, then check whether this record has directory user information, if there is no performs step 8-4.

Step 8-3: if this record has directory user information, then delete this record charging telephone number information, and this record be set to directory user deletion state, continue step 8-5.

Step 8-4: perform this record is set to deletion Status Flag.

Step 8-5: terminate user's fee synchronization removal handling process.

Step 9: whether judged result collection has processed, and completes without process, then continue step 5.

Step 10: synchronization process of user's fee synchronous service terminates.

The specific embodiment of the present invention is described in conjunction with accompanying drawing although above-mentioned; but not limiting the scope of the invention; one of ordinary skill in the art should be understood that; on the basis of technical scheme, those skilled in the art need not pay various amendments or deformation that creative work can make still within protection scope of the present invention.

Claims (10)

1. the method for information system for power enterprise user and telephone subscriber's centralized integration, is characterized in that, comprises the following steps:

Catalog system is because business variation produces catalog system information updating, unified in catalog system user's temporary library of address list by real time propelling movement to enterprise, catalog system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from catalog system is unified to enterprise in the respective table in the formal storehouse of address list;

Multiple charge system user's transition information are by the charge system user's temporary library being directed respectively into unified address list, charge system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from charge system is unified to enterprise in the respective table in the formal storehouse of address list;

Enterprise unifies in the formal storehouse of address list the in store centralized integration enterprise user information of catalog system user and charge system user profile, always initiates entrance for what operation system applied various communication channelss.

2. the method for information system for power enterprise user as claimed in claim 1 and telephone subscriber's centralized integration, is characterized in that, information updating content synchronization to enterprise is unified in the formal table of address list by catalog system, concretely comprising the following steps of employing:

Step one: catalog system is by the user information pushing of renewal to the interim table of catalog system user, and interim table includes enterprise user information and the organizational information of catalog system;

Step 2: catalog system user's synchronous service constantly monitors the more fresh information of the interim table of catalog system user;

Step 3: catalog system user's synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set;

Step 4: catalog system user's synchronous service starts result set record is circulated process;

Step 5: take a directory user change record from result set, starts synchronization process;

Step 6: judge that this record is newly-increased amendment, or delete the renewal operation of type;

Step 7: if increasing or amendment operation, then perform newly-increased and modification process;

Step 8: if deletion action, then perform deletion action flow process;

Step 9: whether judged result collection has processed, and completes without process, then return step 5 and continue with;

Step 10: synchronization process of directory user synchronous service terminates.

3. the method for information system for power enterprise user as claimed in claim 2 and telephone subscriber's centralized integration, is characterized in that, in step 7, if increasing or amendment operation, then performs newly-increased and modification process, and newly-increased and modification process concretely comprises the following steps:

Step 7-1: inquire about enterprise unifies whether there is this user profile in the table of address list formal storehouse by idu;

Step 7-2: without this user profile, then as Adding User process;

Step 7-3: if unifying to inquire about in the table of address list formal storehouse there is this user profile in enterprise, then perform amendment operation;

Step 7-4: the newly-increased or amendment user record end of message.

4. the method for information system for power enterprise user as claimed in claim 3 and telephone subscriber's centralized integration, is characterized in that, in step 7-2: without this user profile, then as Adding User process, the process step that Adds User is as follows:

Step 7-2-1: by telephone number from enterprise unifies to inquire about whether there is this user's fee information under same charge system the table of address list formal storehouse;

Step 7-2-2: without user's fee information, then directly unify one record of increase in the table of address list formal storehouse to enterprise;

Step 7-2-3: if there being user's fee information, it is judged that whether this user's fee record exists directory user information;

Step 7-2-4: if there being directory user information, then record and find there are other user profile using same phone number when Adding User information, and unify one record of increase in the table of address list formal storehouse to enterprise;

Step 7-2-5: without directory user information, then this user's fee information is merged with new directory user information.

5. the method for information system for power enterprise user as claimed in claim 3 and telephone subscriber's centralized integration, it is characterized in that, in step 7-3: if unifying to inquire about in the table of address list formal storehouse there is this user profile in enterprise, then performing amendment operation, it is as follows that amendment operation processes step:

Step 7-3-1: check whether that amendment enterprise unifies user department in the table of address list formal storehouse;

Step 7-3-2: if amendment user department, then judge whether across charge system;

Step 7-3-3: if across charge system, looks into user's fee telephone number in new charge system;

Step 7-3-4: if not across charge system, it may be judged whether amendment charge system telephone number;

Step 7-3-5: if amendment charging telephone number, then according to telephone number query user's fee, otherwise amendment enterprise unifies the user record information in the table of address list formal storehouse;

Step 7-3-6: inquire about user's fee result according to previous step, it may be judged whether have user's fee, without user's fee, then amendment directory user information, has user's fee information else if, then continue to judge whether this user's fee has directory user information;

Step 7-3-7: if this user's fee record has directory user information, then illustrate to exist the user using same phone number, and record uses user's out of Memory of same phone number, and unifies one record of increase in the table of address list formal storehouse to enterprise;

Step 7-3-8: if enterprise unifies this user's fee record in the table of address list formal storehouse and do not have directory user information, then this user's fee information is merged with the directory user information to increase or to revise.

6. the method for information system for power enterprise user as claimed in claim 1 and telephone subscriber's centralized integration, is characterized in that, information updating content synchronization to enterprise is unified in the formal table of address list by charge system, concretely comprising the following steps of employing:

Step A: the user profile of renewal is imported to the interim table of charge system user by charge system, and the interim table of charge system user includes the user profile of charge system, including telephone number information;

Step B: the more fresh information of the user's fee synchronous service periodic monitor interim table of catalog system user;

Step C: user's fee synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set;

Step D: synchronous service starts result set record is circulated process;

Step E: take a directory user change record from result set, starts synchronization process;

Step F: judge that this record is newly-increased amendment, or delete the renewal operation of type;

Step G: if increasing or amendment operation, then perform newly-increased and modification process;

Step H: if deletion action, then perform deletion action flow process;

Step I: whether judged result collection has processed, and completes without process, then return step E and continue with;

Step J: synchronization process of user's fee synchronous service terminates.

7. the method for information system for power enterprise user as claimed in claim 6 and telephone subscriber's centralized integration, is characterized in that, in step G: if increasing or amendment operation, then perform newly-increased and modification process; The newly-increased modification process Detailed operating procedures of charge system user profile is as follows:

Step G-1: inquiry enterprise unifies whether to have in the table of address list formal storehouse this charging phone number user information;

Step G-2: without the user's fee information of this telephone number, then as newly-increased user's fee, to the newly-increased user's fee information of formal storehouse table;

Step G-3: if unifying to inquire about in the table of address list formal storehouse there is this user's fee information in enterprise, then amendment charging telephone number related information;

Step G-4: the newly-increased or amendment user's fee record end of message.

8. the method for information system for power enterprise user as claimed in claim 6 and telephone subscriber's centralized integration, it is characterized in that, in step H: if deletion action, then performing deletion action flow process, it is as follows that charge system user profile deletes flow process thin deletion action step:

Step H-1: unify this user's fee information, if there is no this user profile in the table of address list formal storehouse by charging telephone number query enterprise, then perform step H-5, otherwise continue following steps;

Step H-2: if there is this user's fee information, then check and count whether this record has directory user information, if there is no performs step H-4;

Step H-3: if this record has directory user information, then delete this record charging telephone number information, and this record be set to directory user deletion state, continue step H-5;

Step H-4: perform this record is set to deletion Status Flag;

Step H-5: terminate user's fee synchronization removal handling process.

9. the system of information system for power enterprise user and telephone subscriber's centralized integration, is characterized in that, including:

Catalog system information updating synchronization module, catalog system is because business variation produces catalog system information updating, unified in catalog system user's temporary library of address list by real time propelling movement to enterprise, catalog system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from catalog system is unified to enterprise in the respective table in the formal storehouse of address list;

Charge system information updating synchronization module, multiple charge system user's transition information are by the charge system user's temporary library being directed respectively into unified address list, charge system user's synchronous service finds more new record, start synchronized update task, the more fresh information logically regular and synchronized from charge system is unified to enterprise in the respective table in the formal storehouse of address list;

Enterprise unifies the formal storehouse of address list and integrates module, and enterprise unifies in the formal storehouse of address list the in store centralized integration enterprise user information of catalog system user and charge system user profile, always initiates entrance for what operation system applied various communication channelss.

10. the system of information system for power enterprise user as claimed in claim 9 and telephone subscriber's centralized integration, it is characterized in that, in catalog system information updating synchronization module, information updating content synchronization to enterprise is unified in the formal table of address list by catalog system, including:

Catalog system updates info push module, and catalog system is by the user information pushing of renewal to the interim table of catalog system user, and interim table includes enterprise user information and the organizational information of catalog system;

Catalog system user's synchronous service monitoring modular, catalog system user's synchronous service constantly monitors the more fresh information of the interim table of catalog system user;

Catalog system result set forms module, catalog system user's synchronous service according to the upper subsynchronous dominant record time, inquire about from upper subsynchronous since change data, form result set;

Catalog system judge module, it is judged that this record is newly-increased amendment, or delete the renewal operation of type; If increasing or amendment operation, then enter newly-increased and modified module; If deletion action, then enter deletion action module;

Catalog system synchronous processing module, catalog system user's synchronous service starts result set record is circulated process; From result set, take a directory user change record, start synchronization process; Until having processed result set data.