CN102469144B - 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
- CN102469144B CN102469144B CN201010551068.0A CN201010551068A CN102469144B CN 102469144 B CN102469144 B CN 102469144B CN 201010551068 A CN201010551068 A CN 201010551068A CN 102469144 B CN102469144 B CN 102469144B
- Authority
- CN
- China
- Prior art keywords
- address book
- data
- book 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.)
- Active
Links
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 inter-system data synchronization technology, refer to a kind of method and the unification address list plateform system that realize multiple system communication record data fusion especially.
Background technology
Along with the application of communication assistant's class and the development of personal hand-held terminal, what individual address data grows was many are considered to is distributed in each isolated terminal (as: mobile phone, PDA etc.) and application (as: mailbox, office system etc.), thus define a large amount of separately independent, cannot the data silo of intercommunication.Simultaneously dissimilar, save a part respectively for the application of different user group personal address book, as saved the enterprise address book (colleague) of enterprise staff for the office system of enterprise, the application such as personal assistant, PIM then saves the personal address book of individual.The data of too disperseing cause great inconvenience for user uses during each address list related application, and each application and terminal room cannot complete data syn-chronization simultaneously, also result in the address book data that user cannot grasp oneself completely.
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 its primary limitation is:
It is all data syn-chronization work in order to complete between hand-held mobile terminal and PC (PC) or Internet service that these two kinds of technology existing are mainly applied, only can realize man-to-man data syn-chronization, cannot carry out synchronous to the data between multiple application and merge.
Both sides in the synchronizing process initiated by SyncML and ActiveSync are relations of client and server, and data are as the criterion with one party, and when being used for data syn-chronization between application system, are difficult to assuring data security.
SyncML and ActiveSync all requires to follow unified specific directory form, and the data exceeding this form cannot complete synchronously.But the address book data form of current existing extensive application cannot be converted to the consolidation form of its regulation completely.
Summary of the invention
In view of this, the object of the invention is to propose a kind of method and the unification address list plateform system that realize multiple system communication record data fusion, effectively can merge the individual address data stored in each application system and user terminal, realize the integration of individual address and enterprise's address list.
Based on above-mentioned purpose a kind of method realizing multiple system communication record data fusion provided by the invention, comprising:
The unified address list plateform system preserving unified address list is set;
Be kept in different account number tables to the personal account number in address book data respectively from enterprise account number, the corresponding relation of personal account number and enterprise's account number is kept in relation table;
After the address book data of unified address list plateform system reception operation system transmission reports request, judge that this reports the address book data in request whether consistent with the existing address book data in this locality, if unanimously, then process ends; If inconsistent, then according to reporting the address book data in request to upgrade existing address book data, the address book data after upgrading is issued to other operation systems.
Optionally, contact person's Back ground Information corresponding for account number is stored in the horizontal table of a database by the method, the details of address book contact is kept in the vertical table of another database;
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specifies the corresponding relation between each operation system data field and the attribute-name unifying address list.
Optionally, if the described address book data of the method report request to ask for newly-increased or delete existing address book data, then unified address list plateform system directly performs corresponding operation to existing address book data;
If described address book data report request to ask for modify to existing address book data, the address book data in request and existing address book data then this is reported to carry out field merging, preserve the data after merging, carry out conflict control process to what cannot merge.
Optionally, described in the method, field merging treatment process, comprises the steps:
Step 601, for the field f of in address book data, judge that whether this field f in current uplink communication record data is identical with field f corresponding in the address book data of current preservation in unified address list plateform system, i.e. whether CurVer.f=NewVer.f, if so, then directly step 603 is entered; Otherwise enter step 602;
Step 602, judges that whether described field f in current up address book data is identical with the field f in old version corresponding in unified address list plateform system, i.e. whether CurVer.f=HisVer.f, if so, then enters step 603; Otherwise, enter step 604;
Step 603, does not upgrade the data in unified address list plateform system, is as the criterion, NewVer.f is revised as CurVer.f, then directly enter step 607 with CurVer.f;
Step 604, judges that whether the f field f in the address book data version of current preservation in unified address list plateform system is identical with the f field in old version, i.e. whether CurVer.f=HisVer.f, if so, then enters step 605; Otherwise, enter step 606;
Step 605, is as the criterion with the f field in current uplink communication record data to the f field of data in unified address list plateform system, upgrades, namely retain NewVer.f value constant, enter step 607;
Step 606, mark the up existence conflict of this field f, trailer field merges flow process;
Step 607, judges whether the field of not carrying out merging treatment in addition, if so, then returns step 601 and perform above step to next field, otherwise trailer field merges flow process;
Described conflict control processing procedure, comprises the steps:
Step 701, according to the content of each field in Measures compare NewVer, CurVer and HisVer three record of step 601-607, carries out field merging;
Step 702, if field merges produce conflict, then generate conflict record: keep the colophon on synchronization server constant, NewVer is converted to newly-increased contact person operation, a newly-increased contact person record, its shared field is set to unshared, and generates a conflict notification record and a descending Notification Record for it;
Step 703, if field merges do not find that field contents is changed, without the need to upgrading;
Step 704, if field merges find field contents change, but does not produce conflict, then merge and obtain a final contact person record and be updated to current record, 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, synchronously according to business demand process conflict record, can complete the conflict control that address book data is synchronous.
Optionally, whether the process consistent with existing address book data comprises to judge this to report the address book data in request described in the method: 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 so, be then judged to be unanimously; Otherwise, continue to judge that this reports the version number of the address book data of request whether identical with the version number of address book data in current unified address list plateform system, if so, be then judged to be consistent, otherwise be judged to be inconsistent.
Optionally, described in the method, the process that the address book data after renewal is issued to other operation systems comprises by unified address list plateform system: described unified address list plateform system sends the descending notice of address book data to other operation systems; The service server receiving this descending notice calls downstream interface and obtains from unified address list plateform system the address book data upgraded; Service server upgrades local address book data and version number, calls downstream feedback interface, update process result is sent to described unified address list plateform system; Described unified address list plateform system sends synchronization notice to all operation systems.
Optionally, described in the method, unified address list plateform system comprises after the address book data after renewal is issued to other operation systems further: after operation system completes address book data renewal, reports request that the address book data of renewal is reported to unified address list plateform system by address book data.
Based on above-mentioned purpose, a kind of unified address list plateform system realizing multiple system communication record data fusion provided by the invention, comprising:
Interface adaptation unit, is coupled with each operation system for providing;
Data storage cell, for preserving address book data, being kept in different account number tables to the personal account number in address book data respectively from enterprise account number, being kept in relation table by the corresponding relation of personal account number and enterprise's account number;
Application management unit, after reporting request at the address book data being received operation system transmission by described interface adaptation unit, is judged that this reports the address book data in request whether consistent with the existing address book data in this locality, if unanimously, does not then deal with; If inconsistent, then according to reporting the address book data in request to upgrade existing address book data, the address book data after upgrading is issued to other operation systems by interface adaptation unit.
Optionally, in data storage cell described in this system, contact person's Back ground Information corresponding for account number is stored in the horizontal table of a database, the details of address book contact is kept in the vertical table of another database;
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specifies the corresponding relation between each operation system data field and the attribute-name unifying address list.
Optionally, if the described address book data of this system report request to ask for newly-increased or delete existing address book data, then described application management unit directly performs corresponding operation to existing address book data;
If described address book data report request to ask for modify to existing address book data, then this reports the address book data in request and existing address book data to carry out field merging by described application management unit, preserve the data after merging, carry out conflict control process to what cannot merge.
Optionally, also comprise in application management unit described in this system:
Safety control module, for being encrypted by SSL, ensures the safety of data communication;
Address list management module, for the address list data in management maintenance Unified Communication record platform, detects the reliability of data, ensures availability of data;
User relationship management module, for the belonging relation between maintain individual user and enterprise customer, makes personal user can by the enterprise address book data of interface polls owned enterprise;
Application management module, for managing each operation system of access Unified Communication record platform, guarantees that each operation system synchronously and can only revise oneself data.
Optionally, described in this system, operation system comprises application system and mobile terminal, and described interface adaptation unit is communicated by SyncML protocol realization with between mobile terminal; Described interface adaptation unit realizes communicating by adaptive synchronicity interface protocol with between application system.
Optionally, comprise multiple node be made up of described data storage cell and application management unit within the system, address book data dispersion is stored in different data storage cells;
Described interface adaptation unit comprises Distributor and interface server, after the address book data that interface server reception operation system sends reports request, send to Distributor, after Distributor carries out secondary route by hash algorithm, the application management unit being sent to corresponding node processes.
As can be seen from above, the method and system realizing multiple system communication record data fusion provided by the invention, by building unified address list plateform system, for each application platform provide corresponding data-interface mode realize each application between data fusion and data syn-chronization, form the total solution of the functions such as the reading of a set of collection address list, maintenance, optimization.By adopting the data model of flexible and expansion and efficiently variable interface communications protocol, effectively merge the individual address data stored in each application system and user's handheld terminal, realize the integration of individual address and enterprise's address list, make user in all terminals and application system, obtain unified data and experience.
Specifically possess following advantage and effect:
1) the synchronous of address book data between multiple application system can be realized, make the user of each application system can obtain unified data and experience.
2) can merge the individual address data of user and enterprise's address book data, make user in same interface, oneself individual and enterprise's address list can be accessed simultaneously.
3) by adopting extendible data model, data between different application systems can be effectively integrated and synchronous.
4) by adopting easily extensible and tailorable sync cap agreement, the compatible difference of each application system data model, ensure that all application systems submit the fail safe of data to, also drastically reduce the area volume of transmitted data simultaneously, improve system response time.
5) transaction capabilities of unified address list plateform system is ensured by distributed structure/architecture.
Accompanying drawing explanation
Fig. 1 is embodiment of the present invention Account Data storage organization schematic diagram;
Fig. 2 is embodiment of the present invention contacts data store structural representation;
Fig. 3 is the schematic flow sheet that the embodiment of the present invention realizes multiple system communication record data fusion method;
Fig. 4 is that the embodiment of the present invention unifies address list plateform system structural representation;
Fig. 5 is that the embodiment of the present invention unifies address list plateform system deployment architecture schematic diagram;
Fig. 6 is the schematic flow sheet of embodiment of the present invention field merging treatment process;
Fig. 7 is the schematic flow sheet of embodiment of the present invention conflict control processing procedure.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly understand, below in conjunction with specific embodiment, and with reference to accompanying drawing, the present invention is described in more detail.
A kind of method realizing multiple system communication record data fusion provided by the invention, mainly comprises:
The unified address list plateform system preserving unified address list is set;
Be kept in different account number tables to the personal account number in address book data respectively from enterprise account number, the corresponding relation of personal account number and enterprise's account number is kept in relation table;
After the address book data of unified address list plateform system reception operation system transmission reports request, judge that this reports the address book data in request whether consistent with the existing address book data in this locality, if unanimously, then process ends; If inconsistent, then according to reporting the address book data in request to upgrade existing address book data, the address book data after upgrading is issued to other operation systems.
As an embodiment, described address book data can be divided into Account Data and contact data, can be indexed the contact data of each contact person by Account Data.
As an embodiment, contact person's Back ground Information corresponding for account number is stored in the horizontal table of a database, the details of address book contact is kept in the vertical table of another database;
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specifies the corresponding relation between each operation system data field and the attribute-name unifying address list.
In the flow process of data syn-chronization:
As an embodiment, if described address book data report request to ask for newly-increased or delete existing address book data, then unified address list plateform system directly performs corresponding operation to existing address book data;
If described address book data report request to ask for modify to existing address book data, the address book data in request and existing address book data then this is reported to carry out field merging, preserve the data after merging, carry out conflict control process to what cannot merge.
As an embodiment, describedly judge this to report the address book data in request whether the process consistent with existing address book data comprises: 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 so, be then judged to be unanimously; Otherwise, continue to judge that this reports the version number of the address book data of request whether identical with the version number of address book data in current unified address list plateform system, if so, be then judged to be consistent, otherwise be judged to be inconsistent.
As an embodiment, the process that the address book data after renewal is issued to other operation systems comprises by described unified address list plateform system: described unified address list plateform system sends the descending notice of address book data to other operation systems; The service server receiving this descending notice calls downstream interface and obtains from unified address list plateform system the address book data upgraded; Service server upgrades local address book data and version number, calls downstream feedback interface, update process result is sent to described unified address list plateform system; Described unified address list plateform system sends synchronization notice to all operation systems.
As an embodiment, described unified address list plateform system comprises after the address book data after renewal is issued to other operation systems further: after operation system completes address book data renewal, reports request that the address book data of renewal is reported to unified address list plateform system by address book data.
Wherein, described operation system both can be the application system of enterprise customer etc., and also can be the equipment such as the mobile terminal of individual, described interface adaptation unit be communicated by SyncML protocol realization with between mobile terminal; Described interface adaptation unit realizes communicating by adaptive synchronicity interface protocol with between application system.
Shown in Figure 1, for preserving the example of the account number table of Account Data.
In this embodiment, Account Data is deposited in a 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 relation of the personal account number in personal account number's table and the enterprise's account number in enterprise's account number table is deposited in an other database table, for the incidence relation of corresponding individual with enterprise.
By associating with enterprise account number individual, the data between dissimilar application can being merged, making personal user all can have access to oneself corporate communication record and individual address when using application arbitrarily simultaneously.
Shown in Figure 2, for preserving the example of the contact data table of contact data.
In this embodiment, in order to compatibility has and the address list form of in the future each application and terminal, the present embodiment have employed extendible data model.The Back ground Information of contact person in address list (comprises contact person's essential information as name, sex, birthday etc., and system information as contact person ID, affiliated account number, share arrange) be stored in a horizontal table of database, contact details (as the information such as address, phone) 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 horizontal table of database of above-mentioned generation and database are indulged table and are jointly constituted the contact list shown in Fig. 2.
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specify the corresponding relation between the attribute-name (Prop Name) that each application system data field and Unified Communication are recorded, the attribute with general character (all existing in multiple application system) is synchronous between each application system, and individuation data (be all in certain application system and exist) then only has other application system to carry out synchronously.Because attribute list can constantly be expanded, therefore can meet the difference of all application systems in contact data model, thus solve the excessive synchronous difficulty caused of data model difference between each application system.
Contact list can be indexed, by contact list and then contact attribute table can be indexed by account number table.In addition, search for convenience, Account Data table also can store some user-dependent data, the personal information such as name, sex of such as user.
In order to ensure Synchronization Control data, can in the following way as an embodiment:
The data structure of address book contact record, for preserving current contact person record information.Comprise the transversary representing contact person's essential information, which includes a record version number field, field name is defined as Version; The System Number of this record of record last update, field name is defined as LastUpdateAppId; One represents the identification field recording and whether share between multisystem, is designated as shared.This structure further comprises the telescopic vertical structure representing contact person's contact details, extend information.
The data structure of address book contact historical record, for preserving the information of a version on a contact person record.Comprise the some fields representing contact associated information; A record version number field, field name is defined as Version.
The data structure of descending Notification Record, needs descending address book data record for preserving operation system.
Data synchronization interface agreement:
Because the data model of each application system is all not identical, therefore present invention employs easily extensible and tailorable sync cap agreement.Interface can adopt the modes such as JSON or XML to realize, and below discusses for JSON+HTTP.The data submitted to are a JSON data block, wherein contain 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-1715:36:00 ", " source_user_id ": 133xxxxxxx, " desc ": " ", " updatetime ": " 2009-08-1715: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 " } { " prop_name ": 18, " desc ": " personal preference ", " prop_content ": " film " }] }], " itemsize ": 1, " appid ": " 1 " } }
This request application system that to be appid be " 1 " is submitted to, object is as " 133xxxxxxx " this account number increases the contact person of by name " Zhang San ", and this person's Work Telephone be " 0203863xxxx " mobile phone be " 131xxxxxxxx " personal preference is " film ".Unified Communication record can increase this contact person for " 133xxxxxxx " this account number in a database, simultaneously can by other application systems of the message notice of this contact person.
If the application system that appid is " 2 " does not preserve the personal preference of user, but save the home phone number of user, then this request becomes: { " cmd ": " Member_UL ", " parameter ": { " itemlist ": [{ " birthday ": " 2009-08-1715:36:00 ", " source_user_id ": 133xxxxxxx, " desc ": " ", " updatetime ": " 2009-08-1715: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 " } { " prop_name ": 5, " desc ": " home phone number ", " prop_content ": " 0208822xxxx " }] }], " itemsize ": 1, " appid ": " 2 " } }
When revising contact data, application system only submits the data of this application systematic conservation to, by content system sky being deleted the data of certain attribute, the application system being 1 as appid submits to one to revise request: { " cmd ": " Member_UL ", " parameter ": { " itemlist ": [{ " birthday ": " 2009-08-1715:36:00 ", " source_user_id ": 133xxxxxxx, " desc ": " ", " updatetime ": " 2009-08-1715:36:21 ", " version ": 0, " fn ": " Zhang San ", " optype ": 2, " source_id ": 1, " prop ": [{ " prop_name ": 1, " desc ": " Work Telephone 1 ", " prop_content ": " 0203554xxxx " }, { " prop_name ": 18, " desc ": " personal preference ", " prop_content ": " " }] }], " itemsize ": 1, " appid ": " 1 " } }
The result of the generation of this request is, Unified Communication record can revise the data of " Zhang San " this contact person, Work Telephone 1 is changed into " 0203554xxxx ", delete the data of personal preference, but appid is the mobile telephone data of the operation system submission of 1 before can not revising, the home phone number data that appid is the operation system submission of 2 also can not be revised.
By easily extensible and tailorable interface protocol, can the difference of each application system data model compatible, ensure that all application systems submit the fail safe of data to, also drastically reduce the area volume of transmitted data simultaneously, improve system response time.
In the flow process of data syn-chronization:
Shown in Figure 3, describe address list synchronization handling process in detail with an embodiment.This flow process can be divided into data uplink, data downstream and downstream feedback three sub-processes, specifically comprises following steps:
The version defining current up address book data is NewVer, and the version of the current preservation of unified address list platform is CurVer, and old version is HisVer.A version before being CurVer as HisVer described in an embodiment.
Step 301, operation system sends address book data according to upstream Interface agreement to unified address list plateform system and reports request, and the operation system numbering initiating request is designated as appid.
Step 302, operation system transmits the version number of address book data and the Current communications record data needing to upgrade to unified address list plateform system.
Step 303, the promoter that unified address list plateform system judges current request upstream data whether with last time more new data operation system identical, i.e. whether appid=CurVer.LastUpdateAppId, if the promoter of current upstream data and last time more new data be same operation system, then process ends; Otherwise enter step 304.
Step 304, unified address list plateform system judges that whether the upstream data version number of current request is identical with the address book data version number of the current preservation in this locality, i.e. NewVer version number=CurVer version number, if identical, then process ends; Otherwise enter step 305.
Step 305, unified address list plateform system directly presses newly-increased, delete processing for newly-increased, the deletion action of each contact person record in upstream data; For the retouching operation of contact person record, then unified address list plateform system compares each field of three versions NewVer, CurVer, HisVer, attempts carrying out field merging, preserves the data after merging.For the record that cannot merge, carry out conflict control process.
Step 306, current version CurVer is first saved as HisVer by unified address list plateform system, afterwards NewVer is saved as current version CurVer, and version number increases 1, and generates a descending Notification Record respectively for numbering the operation system being not equal to appid.
Step 307, operation system calls downstream interface, initiates data downstream request, unifies from this address book data that address list plateform system obtains needs.
Step 308, the address book data got is updated to local certificate by operation system, and the version number of local address book data is added the version number of 1 renewal local address book data.
Step 309, operation system initiates downstream feedback request, feeds back to unified address list plateform system the result of each lower line item.
Step 310, unified address list plateform system, according to the descending Notification Record preserved, initiates synchronization notice to needing the operation system of carrying out data downstream.
As an embodiment, this step is after unified address list plateform system waits for all synchronously completing of local all address book datas, and the unified descending Notification Record of each bar by generation in step 306 is issued to the operation system needing to carry out data downstream.
Step 311, receives the operation system of synchronization notice, sends address book data report request to carry out data syn-chronization by step 301-310 and unified address list plateform system to unified address list plateform system.
Can guarantee that operation system keeps synchronous with the address book data in unified address list plateform system by step 311.
In above-mentioned steps 305, described field merging treatment process, shown in Figure 6, comprise the steps:
Step 601, for the field f of in address book data, judge that whether this field f in current uplink communication record data is identical with field f corresponding in the address book data of current preservation in unified address list plateform system, i.e. whether CurVer.f=NewVer.f, if so, then directly step 603 is entered; Otherwise enter step 602.
Step 602, judges that whether described field f in current up address book data is identical with the field f in old version corresponding in unified address list plateform system, i.e. whether CurVer.f=HisVer.f, if so, then enters step 603; Otherwise, enter step 604.
Step 603, does not upgrade the data in unified address list plateform system, is as the criterion, NewVer.f is revised as CurVer.f, then directly enter step 607 with CurVer.f.
Step 604, judges that whether the f field f in the address book data version of current preservation in unified address list plateform system is identical with the f field in old version, i.e. whether CurVer.f=HisVer.f, if so, then enters step 605; Otherwise, enter step 606.
Step 605, is as the criterion with the f field in current uplink communication record data to the f field of data in unified address list plateform system, upgrades, namely retain NewVer.f value constant, enter step 607.
Step 606, mark the up existence conflict of this field f, trailer field merges flow process.
Step 607, judges whether the field of not carrying out merging treatment in addition, if so, then returns step 601 and perform above step to next field, otherwise trailer field merges flow process.
In above-mentioned steps 305, described conflict control processing procedure, shown in Figure 7, comprise the steps:
Step 701, according to the content of each field in Measures compare NewVer, CurVer and HisVer three record of step 601-607, carries out field merging, specifically can be shown in Figure 6.
Step 702, judges field merges whether produce conflict, if field merges produce conflict, enters step 703, otherwise enter step 704.
Step 703, generate conflict record, keep the colophon on synchronization server constant, current NewVer is converted to newly-increased contact person and preserves (wherein this current NewVer refers to after step 601-607 process), a newly-increased contact person record, its shared field is set to unshared, and generates a conflict notification record and a descending Notification Record for it.Conflict sends to synchronous side by synchronization server when being recorded in data downstream, synchronously according to business demand process conflict record, can complete the conflict control that address book data is synchronous.
Wherein, after above-mentioned steps 604 can being connected on as this step of embodiment 702.
Step 704, judges whether field contents has change, if field merges do not find that field contents is changed, without the need to upgrading.
Step 705, if field merges find field contents change, but does not produce conflict, then merge and obtain a final contact person record and be updated to current record, the version of this record increases 1 on original basis.
In another aspect of this invention, additionally provide a kind of unified address list plateform system realizing multiple system communication record data fusion, shown in Figure 4, comprising:
Interface adaptation unit, is coupled with each operation system for providing;
Data storage cell, for preserving address book data, being kept in different account number tables to the personal account number in address book data respectively from enterprise account number, being kept in relation table by the corresponding relation of personal account number and enterprise's account number;
Application management unit, after reporting request at the address book data being received operation system transmission by described interface adaptation unit, is judged that this reports the address book data in request whether consistent with the existing address book data in this locality, if unanimously, does not then deal with; If inconsistent, then according to reporting the address book data in request to upgrade existing address book data, the address book data after upgrading is issued to other operation systems by interface adaptation unit.
As an embodiment, in described data storage cell, contact person's Back ground Information corresponding for account number is stored in the horizontal table of a database, the details of address book contact is kept in the vertical table of another database;
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specifies the corresponding relation between each operation system data field and the attribute-name unifying address list.
As an embodiment, if described address book data report request to ask for newly-increased or delete existing address book data, then described application management unit directly performs corresponding operation to existing address book data;
If described address book data report request to ask for modify to existing address book data, then this reports the address book data in request and existing address book data to carry out field merging by described application management unit, preserve the data after merging, carry out conflict control process to what cannot merge.
As an embodiment, also comprise in described application management unit:
Safety control module, is encrypted by SSL, ensures the safety of data communication.
Address list management module, the address list data in management maintenance Unified Communication record platform, detect the reliability of data, ensure availability of data.
User relationship management module, the belonging relation between maintain individual user and enterprise customer, makes personal user can by the enterprise address book data of interface polls owned enterprise.
Application management module, each operation system of management access Unified Communication record platform, guarantees that each operation system synchronously and can only revise oneself data.
As an embodiment, described operation system comprises operation system and mobile terminal, and described interface adaptation unit is communicated by SyncML protocol realization with between mobile terminal; Described interface adaptation unit realizes communicating by adaptive synchronicity interface protocol with between application system.
In order to the address book data realized between terminal and application is synchronous, the present embodiment to unify in address list plateform system based on SyncML protocol construction terminal contact sync cap.Communication protocol between mobile terminal and terminal contact service interface is the SyncML agreement of standard.Thus ensure that the data syn-chronization between terminal and each application system.
Unified address list plateform system has concentrated the data of all address list related application, forms a unified address book data storehouse.Data scale estimation is as follows:
Calculate by 5,000,000 personal users and 100,000 enterprise customers, average each individual has 50 address list records, and an enterprise has 500 address list records, then unified address list total amount of data reaches:
500 × 50+10 × 500,=30,000 ten thousand
30% to calculate with address list year turnover rate, busy 8 hours, then average process request each second:
(3 × 108 × 30%)/365/8/3600 ≈ 8.6
In view of unified address list plateform system needs the address book data and the large batch of data operation request of each application system that process magnanimity, unified address list plateform system ensures transaction capabilities by using distributed structure/architecture.
Shown in Figure 5, for this reason, unify, in address list plateform system, described data storage cell and application management unit are consisted of a node at this, whole system can form Node 0 by multiple node, Node 1 ... Node n, address book data dispersion is stored in the data storage cell of different node, preferably can be evenly distributed in a node.
Described interface adaptation unit comprises Distributor (Dispatcher) and interface server (Interface Server), after the address book data that interface server reception operation system sends reports request, send to Distributor, after Distributor carries out secondary route by hash algorithm, the application management unit being sent to corresponding node processes.
Unified address list plateform system scale smoothly can be expanded by the mode of continuous expanding node, thus ensure that disposal ability and the capacity of system.
In unified address list plateform system, all services, data all ensure the example of existence more than 2 parts, ask in Multi-instance, to carry out load balancing, after any one example breaks down, request can be routed automatically on normal example by system, thus ensure that the High Availabitity characteristic of system.
By adopting full-text search engine, ensure that high-performance and the high flexibility of inquiry transaction.
Such as: China Telecom economizes and built unified address list plateform system according to this programme, Data distribution8 is on 6 nodes, each node uses a pair (2) Service Instance, data keep two copies in this pair Service Instance, dispose 2 Requests routing servers (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 personal communication assistant platform and the enterprise telephone exchange platform address book data of this province, complete associating of personal address book data and enterprise's address book data, have enterprise customer more than 50,000 family, personal user is more than 6,000,000 families, and incorporating contact book of mobile phone service ability, the unified address book data provided from terminal to application for user is experienced.
Unified address list plateform system is integrated the address book data of the application systems such as 189 mailboxes, sky wing live and comprehensive office, and carries out adaptation to more handheld terminal, to providing the Directory service of fusion for more user.
It should be noted that the present invention can realize in the combination of software and/or software and hardware, such as, 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 memory and to be performed by processor, to realize above-mentioned functions.Like this, process of the present invention (comprising the data structure be associated) can be stored on computer-readable medium or carrier wave, such as RAM memory, Magnetic driving or optical drive or disk etc.
Those of ordinary skill in the field are to be understood that: the foregoing is only specific embodiments of the invention; be not limited to the present invention; within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (13)
1. realize a method for multiple system communication record data fusion, it is characterized in that, comprising:
The unified address list plateform system preserving unified address list is set;
Be kept in different account number tables to the personal account number in address book data respectively from enterprise account number, the corresponding relation of personal account number and enterprise's account number is kept in relation table; Wherein, described address book data can be divided into Account Data and contact data, can be indexed the contact data of each contact person by Account Data;
After the address book data of unified address list plateform system reception operation system transmission reports request, judge that this reports the address book data in request whether consistent with the existing address book data in this locality, if unanimously, then process ends; If inconsistent, then according to reporting the address book data in request to upgrade existing address book data, the address book data after upgrading is issued to other operation systems.
2. method according to claim 1, is characterized in that, is stored in by contact person's Back ground Information corresponding for account number in the horizontal table of a database, the details of address book contact is kept in the vertical table of another database;
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specifies the corresponding relation between each operation system data field and the attribute-name unifying address list.
3. method according to claim 1, is characterized in that, if described address book data report request to ask for newly-increased or delete existing address book data, then unified address list plateform system directly performs corresponding operation to existing address book data;
If described address book data report request to ask for modify to existing address book data, the address book data in request and existing address book data then this is reported to carry out field merging, preserve the data after merging, carry out conflict control process to what cannot merge.
4. method according to claim 3, is characterized in that, described field merging treatment process, comprises the steps:
Step 601, for the field f of in address book data, judge that whether this field f in current uplink communication record data is identical with field f corresponding in the address book data of current preservation in unified address list plateform system, i.e. whether CurVer.f=NewVer.f, if so, then directly step 603 is entered; Otherwise enter step 602;
Step 602, judges that whether described field f in current up address book data is identical with the field f in old version corresponding in unified address list plateform system, i.e. whether CurVer.f=HisVer.f, if so, then enters step 603; Otherwise, enter step 604;
Step 603, does not upgrade the data in unified address list plateform system, is as the criterion, NewVer.f is revised as CurVer.f, then directly enter step 607 with CurVer.f;
Step 604, judges that whether the f field f in the address book data version of current preservation in unified address list plateform system is identical with the f field in old version, i.e. whether CurVer.f=HisVer.f, if so, then enters step 605; Otherwise, enter step 606;
Step 605, is as the criterion with the f field in current uplink communication record data to the f field of data in unified address list plateform system, upgrades, namely retain NewVer.f value constant, enter step 607;
Step 606, mark the up existence conflict of this field f, trailer field merges flow process;
Step 607, judges whether the field of not carrying out merging treatment in addition, if so, then returns step 601 and perform above step to next field, otherwise trailer field merges flow process;
Described conflict control processing procedure, comprises the steps:
Step 701, according to the content of each field in Measures compare NewVer, CurVer and HisVer three record of step 601-607, carries out field merging;
Step 702, if field merges produce conflict, then generate conflict record: keep the colophon on synchronization server constant, NewVer is converted to newly-increased contact person operation, a newly-increased contact person record, its shared field is set to unshared, and generates a conflict notification record and a descending Notification Record for it;
Step 703, if field merges do not find that field contents is changed, without the need to upgrading;
Step 704, if field merges find field contents change, but does not produce conflict, then merge and obtain a final contact person record and be updated to current record, 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, synchronously according to business demand process conflict record, can complete the conflict control that address book data is synchronous.
5. method according to claim 1, it is characterized in that, describedly judge this to report the address book data in request whether the process consistent with existing address book data comprises: 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 so, be then judged to be unanimously; Otherwise, continue to judge that this reports the version number of the address book data of request whether identical with the version number of address book data in current unified address list plateform system, if so, be then judged to be consistent, 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 renewal is issued to other operation systems comprises by described unified address list plateform system: described unified address list plateform system sends the descending notice of address book data to other operation systems; The service server receiving this descending notice calls downstream interface and obtains from unified address list plateform system the address book data upgraded; Service server upgrades local address book data and version number, calls downstream feedback interface, update process result is sent to described unified address list plateform system; Described unified address list plateform system sends synchronization notice to all operation systems.
7. method according to claim 1 or 5, it is characterized in that, described unified address list plateform system comprises after the address book data after renewal is issued to other operation systems further: after operation system completes address book data renewal, reports request that the address book data of renewal is reported to unified address list plateform system by address book data.
8. realize a unified address list plateform system for multiple system communication record data fusion, it is characterized in that, comprising:
Interface adaptation unit, is coupled with each operation system for providing;
Data storage cell, for preserving address book data, being kept in different account number tables to the personal account number in address book data respectively from enterprise account number, being kept in relation table by the corresponding relation of personal account number and enterprise's account number; Wherein, described address book data can be divided into Account Data and contact data, can be indexed the contact data of each contact person by Account Data;
Application management unit, after reporting request at the address book data being received operation system transmission by described interface adaptation unit, is judged that this reports the address book data in request whether consistent with the existing address book data in this locality, if unanimously, does not then deal with; If inconsistent, then according to reporting the address book data in request to upgrade existing address book data, the address book data after upgrading is issued to other operation systems by interface adaptation unit.
9. system according to claim 8, is characterized in that, in described data storage cell, is stored in by contact person's Back ground Information corresponding for account number in the horizontal table of a database, the details of address book contact is kept in the vertical table of another database;
Contact attribute leaves in contact attribute table, by formulating the unified specification of attribute, specifies the corresponding relation between each operation system data field and the attribute-name unifying address list.
10. system according to claim 8, is characterized in that, if described address book data report request to ask for newly-increased or delete existing address book data, then described application management unit directly performs corresponding operation to existing address book data;
If described address book data report request to ask for modify to existing address book data, then this reports the address book data in request and existing address book data to carry out field merging by described application management unit, preserve the data after merging, carry out conflict control process to what cannot merge.
11. systems according to claim 8, is characterized in that, also comprise in described application management unit:
Safety control module, for being encrypted by SSL, ensures the safety of data communication;
Address list management module, unifies the address book data in address list platform for management maintenance, detects the reliability of data, ensures availability of data;
User relationship management module, for the belonging relation between maintain individual user and enterprise customer, makes personal user can by enterprise's address book data of interface polls owned enterprise;
Application management module, for managing each operation system of the unified address list platform of access, guarantees that each operation system synchronously and can only revise oneself data.
12. systems according to claim 8, is characterized in that, described operation system comprises application system and mobile terminal, and described interface adaptation unit is communicated by SyncML protocol realization with between mobile terminal; Described interface adaptation unit realizes communicating by adaptive synchronicity interface protocol with between application system.
13. systems according to claim 8, is characterized in that, comprise multiple node be made up of described data storage cell and application management unit within the system, and address book data dispersion is stored in different data storage cells;
Described interface adaptation unit comprises Distributor and interface server, after the address book data that interface server reception operation system sends reports request, send to Distributor, after Distributor carries out secondary route by hash algorithm, the application management unit being sent to corresponding node processes.
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 CN102469144A (en) | 2012-05-23 |
| CN102469144B true 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) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103037061B (en) * | 2012-12-10 | 2016-02-10 | 东莞宇龙通信科技有限公司 | A kind of method of associated person information process and terminal |
| 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 |
| CN104980329B (en) * | 2014-04-04 | 2019-03-26 | 中国移动通信集团公司 | Book management method and device, Mobile Agent Server |
| CN105187289A (en) * | 2014-06-23 | 2015-12-23 | 中兴通讯股份有限公司 | Group synchronization method and voice mailbox and office system employing above method |
| CN104270524A (en) * | 2014-09-28 | 2015-01-07 | 酷派软件技术（深圳）有限公司 | Information processing method and device |
| CN112152910A (en) * | 2015-02-16 | 2020-12-29 | 钉钉控股（开曼）有限公司 | Communication 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 |
| 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 |
| CN107451280B (en) * | 2017-08-07 | 2020-08-11 | 北京星选科技有限公司 | Data communication method and device and electronic equipment |
| 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 |
| CN112887474B (en) * | 2019-11-13 | 2022-09-20 | 腾讯科技（深圳）有限公司 | Address book management method, server and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8478837B2 (en) * | 2004-01-28 | 2013-07-02 | Microsoft Corporation | Offline global address list |
-
2010
- 2010-11-19 CN CN201010551068.0A patent/CN102469144B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102469144A (en) | 2012-05-23 |
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 | |
| US7738503B2 (en) | Multi-way, peer-to-peer synchronization | |
| US8024290B2 (en) | Data synchronization and device handling | |
| CN100552679C (en) | Regular text data is imported the method for database | |
| CN101207580B (en) | System and method for adding and deleting linkman synchronously by instant communication platform and business platform | |
| US20070100856A1 (en) | Account consolidation | |
| US20050071195A1 (en) | System and method of synchronizing data sets across distributed systems | |
| US10122665B2 (en) | Distributed synchronization data in a message management service | |
| CN101155018B (en) | Data synchronization method and its implementing device and system | |
| US20090233591A1 (en) | Data synchronization method between mobile terminal and server | |
| CN106407214A (en) | Distributed storage method and system | |
| US7840528B2 (en) | System and method for integrating continuous synchronization on a host handheld device | |
| CN102769640B (en) | The update method of user profile, server and system | |
| WO2010006497A1 (en) | Address list system and implementation method thereof | |
| CN101674263A (en) | Transmission method, transmission system, transmission device and receiving device of large data object | |
| CN103607418B (en) | Large-scale data segmenting system based on cloud service data characteristics and dividing method | |
| US20100325556A1 (en) | Method and device for modifying a personal data repository in a network | |
| CN103297448B (en) | The fusion method of private cloud storage and system | |
| CA2522477C (en) | System and method for integrating continuous synchronization on a host handheld device | |
| CN105915636A (en) | Contact person information synchronization method and apparatus thereof | |
| CN101610225B (en) | Method, system and device for synchronous processing | |
| CN101312436A (en) | Notes mail box migrating system and method | |
| CN103532827A (en) | System and method for realizing address book function by extending XMPP (Extensible Messaging and Presence Protocol) | |
| KR100998296B1 (en) | System and method for displaying account or device specific characteristics |
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 |