CN102469144A - Method and system for realizing multisystem address-book data fusion - Google Patents
Method and system for realizing multisystem address-book data fusion Download PDFInfo
- Publication number
- CN102469144A CN102469144A CN2010105510680A CN201010551068A CN102469144A CN 102469144 A CN102469144 A CN 102469144A CN 2010105510680 A CN2010105510680 A CN 2010105510680A CN 201010551068 A CN201010551068 A CN 201010551068A CN 102469144 A CN102469144 A CN 102469144A
- Authority
- CN
- China
- Prior art keywords
- address book
- book data
- data
- address
- field
- 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
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and system for realizing multisystem address-book data fusion. The method comprises the following steps of: setting a uniform address-book platform system which is used for storing a uniform address-book; respectively storing personal accounts and enterprise accounts in address-book data into different account lists, and storing a corresponding relation between the personal accounts and the enterprise accounts in a relation list; and after receiving an address-book data report request which is sent from a business system by the uniform address-book platform system, judging whether the address-book data in the report request is consistent with local existing address-book data or not; if so, finishing a flow; otherwise, updating the existing address-book data according to the address-book data in the report request, and sending the updated address-book data to the other business systems. According to the invention, individual address-book data stored in various application systems and user terminals can be effectively fused, so as to realize the integration of a personal address book and an enterprise address book.
Description
Technical field
The present invention relates to the inter-system data simultaneous techniques, be meant a plurality of system communication record data fusion method of a kind of realization and unified address list plateform system especially.
Background technology
Development along with communication assistant class application and personal hand-held terminal; The individual address data are increasing to be considered to be distributed to each isolated terminal (as: mobile phone, PDA etc.) and to use in (as: mailbox, office system etc.), thereby has formed a large amount of independent separately, data silo that can't intercommunication.A part of personal address book has been preserved in application simultaneously dissimilar, that be directed against the different user crowd respectively; As preserved the enterprise address book (colleague) of enterprise staff to the office system of enterprise, individual personal address book has then been preserved in application such as personal assistant, PIM.The data of too disperseing have caused great inconvenience when using each address list related application for the user, each application simultaneously and terminal room can't be accomplished data sync, have also caused user's address book data of oneself on top of.
At present, the ripe general address list synchronization technology of industry mainly contains two kinds: SyncML (Synchronization Markup Language) and ActiveSync.These two kinds of address list synchronization technology are formulated by Open Mobile Alliance and Microsoft respectively, and it mainly limits to and is:
Existing these two kinds of main application of technology all are in order to accomplish the data sync work between hand-held mobile terminal and PC (PC) or the Internet service, only to realize man-to-man data sync, can't carrying out synchronously and fusion the data between a plurality of application.
Both sides in the synchronizing process of initiating through SyncML and ActiveSync are relations of client and server, and data are as the criterion with a certain side, and when being used between application system data sync, are difficult to guaranteeing data security property.
SyncML and ActiveSync all require to follow unified specific directory form, and the data that exceed this form can't be accomplished synchronously.But the address book data form of present existing extensive application can't convert the consolidation form of its regulation fully into.
Summary of the invention
In view of this; The objective of the invention is to propose a plurality of system communication record data fusion method of a kind of realization and unified address list plateform system; Can each application system of effective fusion and user terminal in the individual address data of storing, realize the integration of individual address and enterprise's address list.
Based on a plurality of system communication record of above-mentioned purpose a kind of realization provided by the invention data fusion method, comprising:
The unified address list plateform system of unified address list is preserved in setting;
Personal account number in the address book data is kept at respectively in the different account number tables with the enterprise account number, the corresponding relation of personal account number and enterprise's account number is kept in the relation table;
After the address book data that unified address list plateform system reception operation system is sent reports request, judge that this reports the address book data in the request whether consistent with the existing address book data in this locality, if unanimity, then process ends; If inconsistent, then, the address book data after upgrading is issued to other operation systems according to reporting the address book data in the request to upgrade existing address book data.
Optional, this method contact person's Back ground Information that account number is corresponding is stored in the horizontal table of a database, and the details of address book contact are kept in the vertical table of another database;
Contact attribute leaves in the contact attribute table, through formulating the unified specification of attribute, stipulates the corresponding relation between the attribute-name of each operation system data field and unified address list.
Optional, if the said address book data of this method reports the newly-increased or existing address book data of deletion that is that request asks, then unified address list plateform system is directly carried out corresponding operation to existing address book data;
If said address book data report that request asks for existing address book data is made amendment; Then report address book data and existing address book data in the request to carry out the field merging this; Preserve the data after merging, to the control and treatment of conflicting that can't merge.
Optional, the said field of this method merges processing procedure, comprises the steps:
Described conflict control and treatment process comprises the steps:
Optional; This method is said judges this reports the address book data in the request whether to comprise with the consistent process of existing address book data: unified address list plateform system judges that sending address book data reports the operation system of request whether identical with the operation system of asking last time to upgrade; If then be judged to be unanimity; Otherwise whether the version number of address book data is identical in the version number that continues to judge the address book data that this reports request and the current unified address list plateform system, if then be judged to be unanimity, otherwise be judged to be inconsistent.
Optional, the process that the address book data after the said unified address list plateform system of this method will upgrade is issued to other operation systems comprises: said unified address list plateform system sends the descending notice of address book data to other operation systems; The service server of receiving this descending notice calls downstream interface and obtains the address book data of renewal from unified address list plateform system; Service server upgrades local address book data and version number, calls the downstream feedback interface, and the update processing result is sent to said unified address list plateform system; Said unified address list plateform system sends synchronization notice to all operation systems.
Optional; After being issued to other operation systems, address book data after the said unified address list plateform system of this method will upgrade further comprises: after operation system is accomplished the address book data renewal, report request that the address book data that upgrades is reported to unified address list plateform system through address book data.
Based on above-mentioned purpose, a kind of unified address list plateform system of realizing a plurality of system communication record data fusion provided by the invention comprises:
The interface adaptation unit is used to provide and each operation system coupling;
Data storage cell is used to preserve address book data, and the personal account number in the address book data is kept at respectively in the different account number tables with the enterprise account number, and the corresponding relation of personal account number and enterprise's account number is kept in the relation table;
The application management unit is used for after the address book data that receives the operation system transmission through said interface adaptation unit reports request, judges that this reports the address book data in the request whether consistent with the existing address book data in this locality, if consistent, does not then deal with; If inconsistent, then, the address book data after upgrading is issued to other operation systems through the interface adaptation unit according to reporting the address book data in the request to upgrade existing address book data.
Optional, in the said data storage cell of this system, contact person's Back ground Information that account number is corresponding is stored in the horizontal table of a database, and the details of address book contact are kept in the vertical table of another database;
Contact attribute leaves in the contact attribute table, through formulating the unified specification of attribute, stipulates the corresponding relation between the attribute-name of each operation system data field and unified address list.
Optional, if the said address book data of this system reports the newly-increased or existing address book data of deletion that is that request asks, corresponding operation is directly carried out to existing address book data in then said application management unit;
If said address book data report that request asks for existing address book data is made amendment; Then said application management unit reports address book data and existing address book data in the request to carry out the field merging this; Preserve the data after merging, to the control and treatment of conflicting that can't merge.
Optional, this system also comprises in the said application management unit:
Safety control module is used for encrypting through SSL, ensures the safety of data communication;
The address list management module is used for management maintenance and unifies the address list data in the address list platform, detects the reliability of data, guarantees availability of data;
The customer relationship administration module is used for the affiliated relation between maintain individual user and the enterprise customer, makes that the personal user can be through the enterprise address book data of interface inquiry owned enterprise;
Application management module is used to manage each operation system that inserts unified address list platform, guarantees that each operation system can only be synchronously and the data of modification oneself.
Optional, the said operation system of this system comprises application system and portable terminal, realizes communicating by letter through the SyncML agreement between said interface adaptation unit and the portable terminal; Realize communicating by letter through self adaptation sync cap agreement between said interface adaptation unit and the application system.
Optional, in this system, comprising a plurality of nodes of forming by said data storage cell and application management unit, address book data disperses to be stored in the different data storage cells;
Comprise Distributor and interface server in the said interface adaptation unit; After the address book data that interface server reception operation system is sent reports request; Send to Distributor; After Distributor carried out the secondary route through hash algorithm, the application management unit that sends to corresponding node was handled.
Saidly can find out from top; A plurality of system communication record data fusion method of realization provided by the invention and system; Through making up unified address list plateform system; Realize each data fusion and data sync between using for each application platform provides corresponding data-interface mode, form functional integrity solutions such as a cover collection address list reads, safeguards, optimization.Through adopting flexibly and expanded data model and efficient variable interface communications protocol; Merge the individual address data of storing in each application system and the user's handheld terminal effectively; Realize the integration of individual address and enterprise's address list, make the user in all terminals and application system, obtain unified data and experience.
Specifically possess following advantage and effect:
1) can realize address book data between a plurality of application systems synchronously, make the user of each application system can access unified data and experience.
2) can user's individual address data and enterprise's address book data be merged, make the user can in same interface, visit own individual and enterprise's address list simultaneously.
3), make between different application systems data to effectively integrate and synchronously through adopting extendible data model.
4) can expand and tailorable sync cap agreement through adopting, the compatible difference of each application system data model has guaranteed that all application systems submit safety of data to, has also reduced volume of transmitted data significantly simultaneously, has improved system response time.
5) guarantee the transaction capabilities of unified address list plateform system through distributed structure/architecture.
Description of drawings
Fig. 1 is an embodiment of the invention Account Data storage organization sketch map;
Fig. 2 is an embodiment of the invention contacts data store structural representation;
Fig. 3 realizes the schematic flow sheet of a plurality of system communication record data fusion methods for the embodiment of the invention;
Fig. 4 unifies address list plateform system structural representation for the embodiment of the invention;
Fig. 5 unifies address list plateform system deployment architecture sketch map for the embodiment of the invention;
Fig. 6 merges the schematic flow sheet of processing procedure for embodiment of the invention field;
Fig. 7 is the schematic flow sheet of embodiment of the invention conflict control and treatment process.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, below in conjunction with specific embodiment, and with reference to accompanying drawing, to further explain of the present invention.
The a plurality of system communication record of a kind of realization provided by the invention data fusion method mainly comprises:
The unified address list plateform system of unified address list is preserved in setting;
Personal account number in the address book data is kept at respectively in the different account number tables with the enterprise account number, the corresponding relation of personal account number and enterprise's account number is kept in the relation table;
After the address book data that unified address list plateform system reception operation system is sent reports request, judge that this reports the address book data in the request whether consistent with the existing address book data in this locality, if unanimity, then process ends; If inconsistent, then, the address book data after upgrading is issued to other operation systems according to reporting the address book data in the request to upgrade existing address book data.
As an embodiment, said address book data can be divided into Account Data and contact data, can index each contact person's contact data through Account Data.
As an embodiment, contact person's Back ground Information that account number is corresponding is stored in the horizontal table of a database, and the details of address book contact are kept in the vertical table of another database;
Contact attribute leaves in the contact attribute table, through formulating the unified specification of attribute, stipulates the corresponding relation between the attribute-name of each operation system data field and unified address list.
In the flow process of data sync:
As an embodiment, if said address book data reports the newly-increased or existing address book data of deletion that is that request asks, then unified address list plateform system is directly carried out corresponding operation to existing address book data;
If said address book data report that request asks for existing address book data is made amendment; Then report address book data and existing address book data in the request to carry out the field merging this; Preserve the data after merging, to the control and treatment of conflicting that can't merge.
As an embodiment; Saidly judge that this reports the address book data in the request whether to comprise with the consistent process of existing address book data: unified address list plateform system judges that whether identical with the operation system that last time, request was upgraded send address book data reports the operation system of request; If then be judged to be unanimity; Otherwise whether the version number of address book data is identical in the version number that continues to judge the address book data that this reports request and the current unified address list plateform system, if then be judged to be unanimity, otherwise be judged to be inconsistent.
As an embodiment, the process that the address book data after said unified address list plateform system will upgrade is issued to other operation systems comprises: said unified address list plateform system sends the descending notice of address book data to other operation systems; The service server of receiving this descending notice calls downstream interface and obtains the address book data of renewal from unified address list plateform system; Service server upgrades local address book data and version number, calls the downstream feedback interface, and the update processing result is sent to said unified address list plateform system; Said unified address list plateform system sends synchronization notice to all operation systems.
As an embodiment; After being issued to other operation systems, address book data after said unified address list plateform system will upgrade further comprises: after operation system is accomplished the address book data renewal, report request that the address book data that upgrades is reported to unified address list plateform system through address book data.
Wherein, said operation system both can be enterprise customer's etc. a application system, also can be individual's equipment such as portable terminal, communicated by letter through the realization of SyncML agreement between said interface adaptation unit and the portable terminal; Realize communicating by letter through self adaptation sync cap agreement between said interface adaptation unit and the application system.
Referring to shown in Figure 1, be the example of the account number table of preserving Account Data.
In this embodiment, Account Data leaves in the database with horizontal sheet form, and personal account number and enterprise's account number submeter are deposited, and forms personal account number's table and enterprise's account number table.The personal account number in personal account number's table and the relation of the enterprise's account number in enterprise's account number table are deposited in the other database table, are used for the incidence relation of corresponding individual and enterprise.
Related through individual and enterprise account number are carried out, can the data between the dissimilar application be merged, make the personal user when using application arbitrarily, all can have access to oneself corporate communication record and individual address simultaneously.
Referring to shown in Figure 2, be the example of the contact data table of preserving contact data.
In this embodiment, reach the address list form at each application in the future and terminal for compatibility is existing, present embodiment has adopted extendible data model.Contact person's Back ground Information (comprises contact person's essential information such as name, sex, birthday etc. in the address list; And system information such as contact person ID, affiliated account number, share be provided with etc.) be stored in the horizontal table of database, contact details (like information such as address, phones) leaves in the vertical table of an other database.Personal account number's contact data and enterprise's account number contact data submeter are deposited.The vertical table of horizontal table of the database of above-mentioned generation and database has been formed contact list shown in Figure 2 jointly.
Contact attribute leaves in the contact attribute table; Through formulating the unified specification of attribute; Stipulate the corresponding relation between the attribute-name (Prop Name) of each application system data field and unified address list; Attribute with general character (in a plurality of application systems, all existing) is synchronous between each application system, and individuation data (be all in certain application system and exist) then has only other application system to carry out synchronously.Because attribute list can constantly be expanded, therefore can satisfy the difference of all application systems aspect the contact data model, thereby solve the excessive synchronous difficulty that causes of data model difference between each application system.
Can index contact list through the account number table, through contact list and then can index the contact attribute table.In addition, for easy-to-look-up, the Account Data table also can be stored some user-dependent data, such as personal informations such as user's name, sexes.
In order to guarantee the Synchronization Control data, can adopt following mode as an embodiment:
Address book contact data recorded structure is used to preserve current contact person record information.The transversary that comprises expression contact person essential information, comprising a record version number field, field name is defined as Version; System's numbering that the last update of a record should be write down, field name is defined as LastUpdateAppId; The identification field whether the expression record is shared between multisystem is designated as shared.This structure has also comprised the telescopic vertical structure of representing contact person's contact details, extend information.
The data structure of address book contact historical record, the information that is used to preserve a version on the contact person record.Comprise some fields of representing contact associated information; A record version number field, field name is defined as Version.
The data structure of descending Notification Record is used to preserve the descending address book data record of operation system needs.
The Data synchronization interface agreement:
Because the data model of each application system is all inequality, so the present invention has adopted and can expand and tailorable sync cap agreement.Interface can adopt modes such as JSON or XML to realize, below discussing with JSON+HTTP is example.The data of submitting to are a JSON data block, have wherein comprised operation requests type, operating data etc.Following data block is complete newly-increased contact person's request: { " cmd ": " Member_UL ", " parameter ": { " itemlist ": [{ " birthday ": " 2009-08-17 15:36:00 ", " source_user_id ": 133xxxxxxx, " desc ": " "; " updatetime ": " 2009-08-17 15:36:21 ", " version ": 0, " fn ": " Zhang San "; " optype ": 1, " source_id ": 1, " prop ": [{ " prop_name ": 1; " desc ": " Work Telephone 1 ", " prop_content ": " 0203863xxxx " }, { " prop_name ": 8; " desc ": " mobile phone 1 ", " prop_content ": " 131xxxxxxxx " } and " prop_name ": 18, " desc ": " personal preference "; " prop_content ": " film " }] }], " itemsize ": 1, " appid ": " 1 " }
This request is the application system submission of " 1 " for appid; Purpose is to increase into " 133xxxxxxx " this account number the contact person of " Zhang San " by name, and this person's Work Telephone is that " 0203863xxxx " mobile phone is " film " for " 131xxxxxxxx " personal preference.Unified address list can be that " 133xxxxxxx " this account number increases this contact person in database, can notify other application systems with this contact person's information simultaneously.
If appid does not preserve user's personal preference for the application system of " 2 ", but has preserved user's home phone number, then this request becomes: { " cmd ": " Member_UL "; " parameter ": { " itemlist ": [{ " birthday ": " 2009-08-17 15:36:00 ", " source_user_id ": 133xxxxxxx, " desc ": " "; " updatetime ": " 2009-08-17 15:36:21 ", " version ": 0, " fn ": " Zhang San "; " optype ": 1, " source_id ": 1, " prop ": [{ " prop_name ": 1; " desc ": " Work Telephone 1 ", " prop_content ": " 0203863xxxx " }, { " prop_name ": 8; " desc ": " mobile phone 1 ", " prop_content ": " 131xxxxxxxx " } and " prop_name ": 5, " desc ": " home phone number "; " prop_content ": " 0208822xxxx " }] }], " itemsize ": 1, " appid ": " 2 " }
When revising contact data, application system is only submitted the data that should preserve with system to, through the data that content system sky is deleted certain attribute, is that 1 application system submits to one to revise request like appid: { " cmd ": " Member_UL "; " parameter ": { " itemlist ": [{ " birthday ": " 2009-08-17 15:36:00 ", " source_user_id ": 133xxxxxxx, " desc ": " ", " updatetime ": " 2009-08-17 15:36:21 "; " version ": 0, " fn ": " Zhang San ", " optype ": 2; " source_id ": 1, " prop ": [" prop_name ": 1, " desc ": " Work Telephone 1 "; " prop_content ": " 0203554xxxx " }, and " prop_name ": 18, " desc ": " personal preference "; " prop_content ": " " }] }], " itemsize ": 1, " appid ": " 1 " }
The result of the generation of this request is; Unified address list can be revised " Zhang San " this contact person's data; Change Work Telephone 1 into " 0203554xxxx "; Deletion personal preference's data, but appid is not the mobile phone data that 1 operation system is submitted to before can not revising can not revised appid yet and be the home phone number data that 2 operation system is submitted to.
Through can expanding and tailorable interface protocol, difference that can compatible each application system data model has guaranteed that all application systems submit safety of data to, has also reduced volume of transmitted data significantly simultaneously, has improved system response time.
In the flow process of data sync:
Referring to shown in Figure 3, describe the address list synchronization handling process in detail with an embodiment.This flow process can be divided into data uplink, data downstream and three sub-flow processs of downstream feedback, specifically comprises following steps:
The version that defines current up address book data is NewVer, and the version of unified address list platform current saved is CurVer, and old version is HisVer.As a said HisVer of embodiment is a CurVer version before.
As an embodiment, this step is that the unified descending Notification Record of each bar with generation in the step 306 is issued to the operation system that need carry out data downstream after all completion synchronously of local all address book datas of unified address list plateform system wait.
Step 311 receives the operation system of synchronization notice, sends address book data to unified address list plateform system and reports and ask set by step that 301-310 carries out data sync with unified address list plateform system.
Can guarantee that through step 311 operation system is synchronous with the address book data maintenance in the unified address list plateform system.
In the above-mentioned steps 305, described field merges processing procedure, referring to shown in Figure 6, comprises the steps:
Step 602 judges whether the field f in the corresponding historical version is identical in said field f and the unified address list plateform system in the current up address book data, i.e. CurVer.f=HisVer.f whether is if then get into step 603; Otherwise, get into step 604.
Step 603 is not upgraded the data in the unified address list plateform system, is as the criterion with CurVer.f, and NewVer.f is revised as CurVer.f, directly gets into step 607 then.
Step 604 judges whether the f field f in the address book data version of current saved in the unified address list plateform system is identical with f field in the old version, i.e. CurVer.f=HisVer.f whether is if then get into step 605; Otherwise, get into step 606.
Step 607 judges whether not merge in addition the field of processing, if then return step 601 pair next field and carry out above step, otherwise trailer field merges flow process.
In the above-mentioned steps 305, described conflict control and treatment process referring to shown in Figure 7, comprises the steps:
Step 701 according to the content of each field in method comparison NewVer, CurVer and three records of HisVer of step 601-607, is carried out field and is merged, specifically can be referring to shown in Figure 6.
Step 702 judges field merges whether produce conflict, if field merges the generation conflict then gets into step 703, otherwise gets into step 704.
Wherein, can be connected on after the above-mentioned steps 604 as this step of embodiment 702.
Step 704 judges whether field contents has change, does not find the field contents change if field merges, and need not to upgrade.
Step 705 is found the field contents change if field merges, but does not produce conflict, then merges to obtain a final contact person record and be updated to current record, and the version of this record increases 1 on original basis.
In another aspect of this invention, a kind of unified address list plateform system of realizing a plurality of system communication record data fusion is provided also,, has comprised referring to shown in Figure 4:
The interface adaptation unit is used to provide and each operation system coupling;
Data storage cell is used to preserve address book data, and the personal account number in the address book data is kept at respectively in the different account number tables with the enterprise account number, and the corresponding relation of personal account number and enterprise's account number is kept in the relation table;
The application management unit is used for after the address book data that receives the operation system transmission through said interface adaptation unit reports request, judges that this reports the address book data in the request whether consistent with the existing address book data in this locality, if consistent, does not then deal with; If inconsistent, then, the address book data after upgrading is issued to other operation systems through the interface adaptation unit according to reporting the address book data in the request to upgrade existing address book data.
As an embodiment, in the said data storage cell, contact person's Back ground Information that account number is corresponding is stored in the horizontal table of a database, and the details of address book contact are kept in the vertical table of another database;
Contact attribute leaves in the contact attribute table, through formulating the unified specification of attribute, stipulates the corresponding relation between the attribute-name of each operation system data field and unified address list.
As an embodiment, if said address book data reports the newly-increased or existing address book data of deletion that is that request asks, corresponding operation is directly carried out to existing address book data in then said application management unit;
If said address book data report that request asks for existing address book data is made amendment; Then said application management unit reports address book data and existing address book data in the request to carry out the field merging this; Preserve the data after merging, to the control and treatment of conflicting that can't merge.
As an embodiment, said application management also comprises in the unit:
Safety control module is encrypted through SSL, ensures the safety of data communication.
Address list management module, management maintenance are unified the address list data in the address list platform, detect the reliability of data, guarantee availability of data.
The customer relationship administration module, the affiliated relation between maintain individual user and the enterprise customer makes that the personal user can be through the enterprise address book data of interface inquiry owned enterprise.
Application management module, management inserts each operation system of unified address list platform, guarantees that each operation system can only be synchronously and the data of modification oneself.
As an embodiment, said operation system comprises operation system and portable terminal, realizes communicating by letter through the SyncML agreement between said interface adaptation unit and the portable terminal; Realize communicating by letter through self adaptation sync cap agreement between said interface adaptation unit and the application system.
For realize the terminal and use between address book data synchronous, present embodiment in unified address list plateform system based on the SyncML protocol construction terminal contact sync cap.Communication protocol between portable terminal and the terminal contact service interface is the SyncML agreement of standard.Thereby guaranteed the data sync between terminal and each application system.
Unified address list plateform system has been concentrated the data of all address list related application, forms a unified address book data storehouse.Data scale is estimated as follows:
Calculate by 5,000,000 personal users and 100,000 enterprise customers, on average each individual has 50 address list records, and an enterprise has 500 address list records, and then unified address list total amount of data reaches:
Ten thousand of 500 * 50+10 * 500=30000
With address list year turnover rate 30% calculate, when busy 8 hours, handle request then average each second:
8.6 of (3 * 108 * 30%)/365/8/3600 ≈
Seeing that unified address list plateform system need be handled the address book data and the large batch of data operation request of each application system of magnanimity, unified address list plateform system guarantees transaction capabilities through using distributed structure/architecture.
Referring to shown in Figure 5; For this reason; Unify in the address list plateform system said data storage cell and application management unit to be consisted of a node at this, whole system can be formed Node 0 by a plurality of nodes, and Node 1 ... Node n; Address book data is disperseed to be stored in the data storage cell of different nodes, preferably can be evenly distributed in the node.
Comprise Distributor (Dispatcher) and interface server (Interface Server) in the said interface adaptation unit; After the address book data that interface server reception operation system is sent reports request; Send to Distributor; After Distributor carried out the secondary route through hash algorithm, the application management unit that sends to corresponding node was handled.
Unified address list plateform system scale can smoothly be expanded through the mode of continuous expanding node, thereby has guaranteed the disposal ability and the capacity of system.
In the unified address list plateform system; All services, data all guarantee to exist the instance more than 2 parts, and load balancing is carried out in request in a plurality of instances, after any instance breaks down; System can be routed automatically to request on the normal instance, thereby has guaranteed the high available characteristic of system.
Through adopting the full-text search engine, guaranteed the high-performance and the high flexibility of inquiry transaction.
For example: China Telecom economizes and has built unified address list plateform system according to this programme; Data are distributed on 6 nodes; Each node uses a pair of (2) Service Instance, and data keep two copies in this a pair of Service Instance, disposes 2 request Distributors (Dispatcher) and 2 interface service (Interface Server) 16 Service Instances altogether simultaneously; Be distributed on 4 PC server hosts, form a complete Distributed Application.
Unified address list plateform system has merged the personal communication assistant platform and the enterprise telephone exchange platform address book data of this province; Accomplished the related of personal address book data and enterprise address book data; Had family surplus the enterprise customer 50,000; The personal user surpasses 6,000,000 families, and has integrated the contact book of mobile phone service ability, experiences for the user provides from the terminal to the unified address book data of using.
Unified address list plateform system is integrated the address book data of application systems such as 189 mailboxes, day wing live and comprehensive office, and more handheld terminal is carried out adaptive, in the hope of the address list service of fusion is provided for more user.
Should be noted that the present invention can realize in the combination of software and/or software and hardware, for example use application-specific integrated circuit (ASIC) (ASIC), all-purpose computer or other hardware equivalents to realize.In one embodiment, module or process can be loaded in the memory and by processor and carry out, to realize above-mentioned functions.Like this, process of the present invention (comprising the data structure that is associated) can be stored on computer-readable medium or the carrier wave, for example RAM memory, magnetic driving or optical drive or disk or the like.
The those of ordinary skill in affiliated field is to be understood that: the above is merely specific embodiment of the present invention; Be not limited to the present invention; All within spirit of the present invention and principle, any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (13)
1. realize a plurality of system communication record data fusion method for one kind, it is characterized in that, comprising:
The unified address list plateform system of unified address list is preserved in setting;
Personal account number in the address book data is kept at respectively in the different account number tables with the enterprise account number, the corresponding relation of personal account number and enterprise's account number is kept in the relation table;
After the address book data that unified address list plateform system reception operation system is sent reports request, judge that this reports the address book data in the request whether consistent with the existing address book data in this locality, if unanimity, then process ends; If inconsistent, then, the address book data after upgrading is issued to other operation systems according to reporting the address book data in the request to upgrade existing address book data.
2. method according to claim 1 is characterized in that, contact person's Back ground Information that account number is corresponding is stored in the horizontal table of a database, and the details of address book contact are kept in the vertical table of another database;
Contact attribute leaves in the contact attribute table, through formulating the unified specification of attribute, stipulates the corresponding relation between the attribute-name of each operation system data field and unified address list.
3. method according to claim 1 is characterized in that, if said address book data reports the newly-increased or existing address book data of deletion that is that request asks, then unified address list plateform system is directly carried out corresponding operation to existing address book data;
If said address book data report that request asks for existing address book data is made amendment; Then report address book data and existing address book data in the request to carry out the field merging this; Preserve the data after merging, to the control and treatment of conflicting that can't merge.
4. method according to claim 3 is characterized in that, said field merges processing procedure, comprises the steps:
Step 601; For a field f in the address book data; Judge in the current uplink communication record data this field f with unify the address list plateform system in the address book data of current saved corresponding field f whether identical; I.e. CurVer.f=NewVer.f whether is if then directly get into step 603; Otherwise get into step 602;
Step 602 judges whether the field f in the corresponding historical version is identical in said field f and the unified address list plateform system in the current up address book data, i.e. CurVer.f=HisVer.f whether is if then get into step 603; Otherwise, get into step 604;
Step 603 is not upgraded the data in the unified address list plateform system, is as the criterion with CurVer.f, and NewVer.f is revised as CurVer.f, directly gets into step 607 then;
Step 604 judges whether the f field f in the address book data version of current saved in the unified address list plateform system is identical with f field in the old version, i.e. CurVer.f=HisVer.f whether is if then get into step 605; Otherwise, get into step 606;
Step 605, the f field that the f field of data in the unified address list plateform system is recorded in the data with current uplink communication is as the criterion, and upgrades, and it is constant promptly to keep the NewVer.f value, gets into step 607;
Step 606, the up existence conflict of this field of mark f, trailer field merges flow process;
Step 607 judges whether not merge in addition the field of processing, if then return step 601 pair next field and carry out above step, otherwise trailer field merges flow process;
Described conflict control and treatment process comprises the steps:
Step 701 according to the content of each field in method comparison NewVer, CurVer and three records of HisVer of step 601-607, is carried out field and is merged;
Step 702; If merging, field produces conflict; Then generate the conflict record: keep the colophon on the synchronization server constant, convert NewVer into newly-increased contact person's operation, newly-increased contact person record; Its shared field is set to non-sharing, and generates a conflict notification record and a descending Notification Record for it;
Step 703 is not found the field contents change if field merges, and need not to upgrade;
Step 704 is found the field contents change if field merges, but does not produce conflict, then merges to obtain a final contact person record and be updated to current record, and the version of this record increases 1 on original basis;
Step 705 sends to synchronous side by synchronization server when conflict is recorded in data downstream, can handle the conflict record according to business demand synchronously, accomplishes the synchronous conflict control of address book data.
5. method according to claim 1; It is characterized in that; Saidly judge that this reports the address book data in the request whether to comprise with the consistent process of existing address book data: unified address list plateform system judges that whether identical with the operation system that last time, request was upgraded send address book data reports the operation system of request; If then be judged to be unanimity; Otherwise whether the version number of address book data is identical in the version number that continues to judge the address book data that this reports request and the current unified address list plateform system, if then be judged to be unanimity, otherwise be judged to be inconsistent.
6. method according to claim 1; It is characterized in that the process that the address book data after said unified address list plateform system will upgrade is issued to other operation systems comprises: said unified address list plateform system sends the descending notice of address book data to other operation systems; The service server of receiving this descending notice calls downstream interface and obtains the address book data of renewal from unified address list plateform system; Service server upgrades local address book data and version number, calls the downstream feedback interface, and the update processing result is sent to said unified address list plateform system; Said unified address list plateform system sends synchronization notice to all operation systems.
7. according to claim 1 or 5 described methods; It is characterized in that; After being issued to other operation systems, address book data after said unified address list plateform system will upgrade further comprises: after operation system is accomplished the address book data renewal, report request that the address book data that upgrades is reported to unified address list plateform system through address book data.
8. a unified address list plateform system of realizing a plurality of system communication record data fusion is characterized in that, comprising:
The interface adaptation unit is used to provide and each operation system coupling;
Data storage cell is used to preserve address book data, and the personal account number in the address book data is kept at respectively in the different account number tables with the enterprise account number, and the corresponding relation of personal account number and enterprise's account number is kept in the relation table;
The application management unit is used for after the address book data that receives the operation system transmission through said interface adaptation unit reports request, judges that this reports the address book data in the request whether consistent with the existing address book data in this locality, if consistent, does not then deal with; If inconsistent, then, the address book data after upgrading is issued to other operation systems through the interface adaptation unit according to reporting the address book data in the request to upgrade existing address book data.
9. system according to claim 8 is characterized in that, in the said data storage cell, contact person's Back ground Information that account number is corresponding is stored in the horizontal table of a database, and the details of address book contact are kept in the vertical table of another database;
Contact attribute leaves in the contact attribute table, through formulating the unified specification of attribute, stipulates the corresponding relation between the attribute-name of each operation system data field and unified address list.
10. system according to claim 8 is characterized in that, if said address book data reports the newly-increased or existing address book data of deletion that is that request asks, corresponding operation is directly carried out to existing address book data in then said application management unit;
If said address book data report that request asks for existing address book data is made amendment; Then said application management unit reports address book data and existing address book data in the request to carry out the field merging this; Preserve the data after merging, to the control and treatment of conflicting that can't merge.
11. system according to claim 8 is characterized in that, said application management also comprises in the unit:
Safety control module is used for encrypting through SSL, ensures the safety of data communication;
The address list management module is used for management maintenance and unifies the address list data in the address list platform, detects the reliability of data, guarantees availability of data;
The customer relationship administration module is used for the affiliated relation between maintain individual user and the enterprise customer, makes that the personal user can be through the enterprise address book data of interface inquiry owned enterprise;
Application management module is used to manage each operation system that inserts unified address list platform, guarantees that each operation system can only be synchronously and the data of modification oneself.
12. system according to claim 8 is characterized in that, said operation system comprises application system and portable terminal, realizes communicating by letter through the SyncML agreement between said interface adaptation unit and the portable terminal; Realize communicating by letter through self adaptation sync cap agreement between said interface adaptation unit and the application system.
13. system according to claim 8 is characterized in that, in this system, comprises a plurality of nodes of being made up of said data storage cell and application management unit, address book data disperses to be stored in the different data storage cells;
Comprise Distributor and interface server in the said interface adaptation unit; After the address book data that interface server reception operation system is sent reports request; Send to Distributor; After Distributor carried out the secondary route through hash algorithm, the application management unit that sends to corresponding node was handled.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010551068.0A CN102469144B (en) | 2010-11-19 | 2010-11-19 | Method and system for realizing multisystem address-book data fusion |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010551068.0A CN102469144B (en) | 2010-11-19 | 2010-11-19 | Method and system for realizing multisystem address-book data fusion |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102469144A true CN102469144A (en) | 2012-05-23 |
| CN102469144B CN102469144B (en) | 2015-02-18 |
Family
ID=46072307
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010551068.0A Active CN102469144B (en) | 2010-11-19 | 2010-11-19 | Method and system for realizing multisystem address-book data fusion |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102469144B (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103037061A (en) * | 2012-12-10 | 2013-04-10 | 东莞宇龙通信科技有限公司 | Method and terminal of contact person information process |
| CN103475712A (en) * | 2013-09-10 | 2013-12-25 | 北京思特奇信息技术股份有限公司 | Method and system for realizing automatic correlation of multiple enterprises and multiple contact lists based on cloud computation |
| CN103501337A (en) * | 2013-09-29 | 2014-01-08 | 方正国际软件有限公司 | Multi-grade data node updating and synchronizing system and method |
| CN104270524A (en) * | 2014-09-28 | 2015-01-07 | 酷派软件技术（深圳）有限公司 | Information processing method and device |
| CN104683586A (en) * | 2015-03-09 | 2015-06-03 | 深圳酷派技术有限公司 | Method and terminal for information display |
| CN104980329A (en) * | 2014-04-04 | 2015-10-14 | 中国移动通信集团公司 | Address book management method address book management device and mobile agent server |
| CN105187289A (en) * | 2014-06-23 | 2015-12-23 | 中兴通讯股份有限公司 | Group synchronization method and voice mailbox and office system employing above method |
| CN105872168A (en) * | 2015-11-09 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Address list update method and device |
| CN106776062A (en) * | 2016-11-29 | 2017-05-31 | 北京元心科技有限公司 | Multi-system contact person attribute information synchronization method and device |
| CN107451280A (en) * | 2017-08-07 | 2017-12-08 | 北京小度信息科技有限公司 | Data get through method, apparatus and electronic equipment |
| CN107547683A (en) * | 2017-08-10 | 2018-01-05 | 青岛海信移动通信技术股份有限公司 | Data processing method and device |
| CN107852358A (en) * | 2016-06-12 | 2018-03-27 | 华为技术有限公司 | A kind of method and apparatus that content is forwarded between different application |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| CN111083038A (en) * | 2019-10-23 | 2020-04-28 | 上海盈联电信科技有限公司 | Enterprise management online instant messaging system and method |
| CN112152904A (en) * | 2015-02-16 | 2020-12-29 | 钉钉控股（开曼）有限公司 | Network interaction method |
| CN112887474A (en) * | 2019-11-13 | 2021-06-01 | 腾讯科技（深圳）有限公司 | Address book management method, server and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050164651A1 (en) * | 2004-01-28 | 2005-07-28 | Microsoft Corporation | Offline global address list |
| CN101437221A (en) * | 2008-12-18 | 2009-05-20 | 中国移动通信集团浙江有限公司 | Method for processing mobile number book data based on OMA SyncML protocol |
| CN101588375A (en) * | 2009-05-21 | 2009-11-25 | 中国电信股份有限公司 | Address book processing system and method thereof |
| CN101730085A (en) * | 2009-11-18 | 2010-06-09 | 中国电信股份有限公司 | Address book data synchronizing method and system |
-
2010
- 2010-11-19 CN CN201010551068.0A patent/CN102469144B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050164651A1 (en) * | 2004-01-28 | 2005-07-28 | Microsoft Corporation | Offline global address list |
| CN101437221A (en) * | 2008-12-18 | 2009-05-20 | 中国移动通信集团浙江有限公司 | Method for processing mobile number book data based on OMA SyncML protocol |
| CN101588375A (en) * | 2009-05-21 | 2009-11-25 | 中国电信股份有限公司 | Address book processing system and method thereof |
| CN101730085A (en) * | 2009-11-18 | 2010-06-09 | 中国电信股份有限公司 | Address book data synchronizing method and system |
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103037061A (en) * | 2012-12-10 | 2013-04-10 | 东莞宇龙通信科技有限公司 | Method and terminal of contact person information process |
| CN103475712A (en) * | 2013-09-10 | 2013-12-25 | 北京思特奇信息技术股份有限公司 | Method and system for realizing automatic correlation of multiple enterprises and multiple contact lists based on cloud computation |
| CN103475712B (en) * | 2013-09-10 | 2016-05-11 | 北京思特奇信息技术股份有限公司 | Realize the method and system of many address lists of multiple enterprises auto-associating based on cloud computing |
| CN103501337B (en) * | 2013-09-29 | 2017-05-10 | 北大医疗信息技术有限公司 | Multi-grade data node updating and synchronizing system and method |
| CN103501337A (en) * | 2013-09-29 | 2014-01-08 | 方正国际软件有限公司 | Multi-grade data node updating and synchronizing system and method |
| CN104980329B (en) * | 2014-04-04 | 2019-03-26 | 中国移动通信集团公司 | Book management method and device, Mobile Agent Server |
| CN104980329A (en) * | 2014-04-04 | 2015-10-14 | 中国移动通信集团公司 | Address book management method address book management device and mobile agent server |
| CN105187289A (en) * | 2014-06-23 | 2015-12-23 | 中兴通讯股份有限公司 | Group synchronization method and voice mailbox and office system employing above method |
| WO2015196529A1 (en) * | 2014-06-23 | 2015-12-30 | 中兴通讯股份有限公司 | Group synchronization method, and voice mailbox and office system applying the method |
| CN104270524A (en) * | 2014-09-28 | 2015-01-07 | 酷派软件技术（深圳）有限公司 | Information processing method and device |
| CN112152904B (en) * | 2015-02-16 | 2022-12-09 | 钉钉控股（开曼）有限公司 | Network interaction method |
| CN112152904A (en) * | 2015-02-16 | 2020-12-29 | 钉钉控股（开曼）有限公司 | Network interaction method |
| CN104683586A (en) * | 2015-03-09 | 2015-06-03 | 深圳酷派技术有限公司 | Method and terminal for information display |
| CN105872168A (en) * | 2015-11-09 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Address list update method and device |
| CN107852358A (en) * | 2016-06-12 | 2018-03-27 | 华为技术有限公司 | A kind of method and apparatus that content is forwarded between different application |
| US11438298B2 (en) | 2016-06-12 | 2022-09-06 | Huawei Technologies Co., Ltd. | Method and apparatus for forwarding content between different application programs |
| CN106776062B (en) * | 2016-11-29 | 2020-12-01 | 北京元心科技有限公司 | Multi-system contact person attribute information synchronization method and device |
| CN106776062A (en) * | 2016-11-29 | 2017-05-31 | 北京元心科技有限公司 | Multi-system contact person attribute information synchronization method and device |
| CN107451280B (en) * | 2017-08-07 | 2020-08-11 | 北京星选科技有限公司 | Data communication method and device and electronic equipment |
| CN107451280A (en) * | 2017-08-07 | 2017-12-08 | 北京小度信息科技有限公司 | Data get through method, apparatus and electronic equipment |
| CN107547683A (en) * | 2017-08-10 | 2018-01-05 | 青岛海信移动通信技术股份有限公司 | Data processing method and device |
| CN107547683B (en) * | 2017-08-10 | 2021-04-30 | 青岛海信移动通信技术股份有限公司 | Data processing method and device |
| CN111083038A (en) * | 2019-10-23 | 2020-04-28 | 上海盈联电信科技有限公司 | Enterprise management online instant messaging system and method |
| CN110769061B (en) * | 2019-10-24 | 2021-02-26 | 华为技术有限公司 | Data synchronization method and equipment |
| CN110769061A (en) * | 2019-10-24 | 2020-02-07 | 华为技术有限公司 | Data synchronization method and equipment |
| US12045247B2 (en) | 2019-10-24 | 2024-07-23 | Huawei Technologies Co., Ltd. | Data synchronization method and device |
| CN112887474A (en) * | 2019-11-13 | 2021-06-01 | 腾讯科技（深圳）有限公司 | Address book management method, server and computer readable storage medium |
| CN112887474B (en) * | 2019-11-13 | 2022-09-20 | 腾讯科技（深圳）有限公司 | Address book management method, server and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102469144B (en) | 2015-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102469144B (en) | Method and system for realizing multisystem address-book data fusion | |
| CN100538699C (en) | Utilize mobile communication equipment integrated content automatically from multiple information stores | |
| CN101448212B (en) | Apparatus and methods for operation of wireless server | |
| CN100552679C (en) | Regular text data is imported the method for database | |
| US8620366B2 (en) | Data synchronization method between mobile terminal and server | |
| WO2007047140A1 (en) | Account consolidation | |
| CN101588262A (en) | Remote management of mobile wireless devices | |
| CN101155018B (en) | Data synchronization method and its implementing device and system | |
| CN103533023B (en) | Cloud service application cluster based on cloud service feature synchronizes system and synchronous method | |
| CN102769640B (en) | The update method of user profile, server and system | |
| CN103607418B (en) | Large-scale data segmenting system based on cloud service data characteristics and dividing method | |
| WO2010006497A1 (en) | Address list system and implementation method thereof | |
| EP2533461B1 (en) | Method and system for managing service group | |
| CN102421091A (en) | Address book updating method and system | |
| US20060101082A1 (en) | System and method for integrating continuous synchronization on a host handheld device | |
| CN108416567A (en) | One kind being based on full-range multi-functional synergetic office work method and device | |
| CN110727738A (en) | Global routing system based on data fragmentation, electronic equipment and storage medium | |
| CN102186163A (en) | Data synchronizing method of multi-account address book of smart phone | |
| KR20130042792A (en) | A total business surpporting system and a method therefor | |
| US20100325556A1 (en) | Method and device for modifying a personal data repository in a network | |
| CA2522477C (en) | System and method for integrating continuous synchronization on a host handheld device | |
| CN101312436B (en) | Notes mail box migrating system and method | |
| JP2002373101A (en) | Inter-directory cooperative method | |
| WO2012162939A1 (en) | Method for providing contact information based on verification information | |
| US8068820B1 (en) | Systems and methods for providing data to mobile stations |
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 |