CN102088519A - Address book management method and device - Google Patents

Address book management method and device Download PDF

Info

Publication number
CN102088519A
CN102088519A CN2009102423029A CN200910242302A CN102088519A CN 102088519 A CN102088519 A CN 102088519A CN 2009102423029 A CN2009102423029 A CN 2009102423029A CN 200910242302 A CN200910242302 A CN 200910242302A CN 102088519 A CN102088519 A CN 102088519A
Authority
CN
China
Prior art keywords
user
communication
list
address list
subclauses
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.)
Pending
Application number
CN2009102423029A
Other languages
Chinese (zh)
Inventor
王波
金剑
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to CN2009102423029A priority Critical patent/CN102088519A/en
Publication of CN102088519A publication Critical patent/CN102088519A/en
Pending legal-status Critical Current

Links

Abstract

The invention discloses an address book management method and an address book management device. An address book of a user is stored on a network side and takes a user identifier which is bound with a mobile communication number of the user as an index; the communication book of each user comprises the communication information of the user and a contact person list of the user; and the list is used for storing user identifiers of contact persons. The method comprises the following steps of: when the network side receives a request for changing communication information from a first user, acquiring a first user identifier which is bound with the mobile communication number of the first user according to the mobile communication number and a first user address book which takes the first user identifier as an index and changing the communication information of the first user in the first user address book according to the request; and acquiring the address book which comprises the first user identifier and the user identifier serving as the index of the address book in the contact person list from each address book and transmitting the communication information of the first user in the first user address book to a mobile terminal which corresponds to the mobile communication number bound with the acquired user identifier.

Description

Book management method and device thereof
Technical field
The present invention relates to the data service technology of the communications field, relate in particular to a kind of book management method and device thereof.
Background technology
The traditional form of individual address shows as paper, this book or the cards folder of record communication information, the present then address list of widely-used electronic form.Preserve various liaison methods, communication number, contact person's basic condition information of each contact person etc. in the individual address, even more complicated multimedia messagess such as picture.Several contact persons' information aggregation is got up, and actual is the database of other people communication information of a personal record.Although different format standards is arranged, individual address does not break away from the pattern of centralized stores substantially, is created voluntarily and is safeguarded by the address list user.The carrier of person-to-person communication address book stored and application are then varied, as, PDA(Personal Digital Assistant), PC (PC), landline telephone, mobile phone, SIM/USIM card (Subscriber Identity Module), cyberspace etc. are wherein used the most general with the address list on the mobile phone (being mobile phone).
Lose for avoiding the address list content-data, there are many technological means to help to realize the backup and the recovery of individual address at present, its basic principle all copies nothing more than the data that portion is identical with individual subscriber address list content and separates storage, for example is stored in SIM card, PC disk or cyberspace.If individual subscriber address list contents lost or damage can recover out by the data that have other places in advance.
Existing individual address technical scheme all shows as the user and sets up and safeguard a cover contact data, several contact persons' lengthy and tedious communication information unification is managed voluntarily by the user, when number of contacts is considerable, the required memory capacity of address book backup increases severely thereupon, and recovery synchronously also expends the more time.In addition, during the communication information change of contact person's reality, respective contacts information in necessary its address list of time update of user, its backup of passive renewal simultaneously, otherwise can cause this contact person's communication information to lose efficacy.
Though existing individual address administrative skill has realized the foundation, storage, backup of address list, management maintenance function such as synchronous substantially, but still extensively adopt by individual centralized stores and safeguard the mode of many people communication information voluntarily.The a large amount of memory spaces of this Technology Need are dealt with a considerable number of contact person's communication data, create and safeguard that these data are very difficult.
Summary of the invention
Embodiments of the invention provide a kind of book management method and device thereof, in order to solve the problem of the big and data maintenance difficulty of network storage amount that existing address list management technology exists.
The technical scheme that embodiments of the invention provide comprises:
A kind of book management method, wherein, network side storing has user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
When network side receives after first user changes the request of he or she's communication information, according to first user's who carries in the described request mobile communication number obtain with first user ID of its binding and with first user ID be first user communication record of index, and change the communication information of user in this first user communication record according to described request; Then, from each address list, obtain the address list that includes first user ID in the contacts list and the user ID of this address list of index, and after getting access to user ID, the pairing portable terminal of mobile communication number of the user ID binding that the communication information of user in first user communication record is sent to and gets access to.
A kind of address list management server comprises:
The address list memory module, be used to store user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
When network side receives after first user changes the request of he or she's communication information, according to first user's who carries in the described request mobile communication number obtain with first user ID of its binding and with first user ID be first user communication record of index, and change the communication information of user in this first user communication record according to described request; Then, from each address list, obtain the address list that includes first user ID in the contacts list and the user ID of this address list of index, and after getting access to user ID, the pairing portable terminal of mobile communication number of the user ID binding that the communication information of user in first user communication record is sent to and gets access to.
In the above embodiment of the present invention, because in the record of the user communication of network side storing, store the linking relationship that the user points to the contact person with the contacts list form, and need not be each its contact person's of user storage corresponding communication information, saved network storage space like this.On the other hand, when first user changes the communication information of oneself, point to its contact person's annexation by this user in each user communication record, find out the user who first user is added to the contact person, and send first user's communication information to the user who finds out, contact person's address list of end side so that it upgrades in time, thus realized the interlock of network side and end side address list, reduced the address list maintenance difficulties.
A kind of book management method, wherein, network side storing has user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
When network side receives after first user obtains the request of its address list, obtain with first user ID of its binding and be first user communication record of index with first user ID according to first user's who carries in the described request mobile communication number; Then, according to the user ID in the contacts list of first user communication record obtain with described user ID be index address list, and the communication information of user in the address list that gets access to is sent to first user's mobile communication number corresponding mobile terminal.
A kind of address book server comprises:
The address list memory module, be used to store user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
Communication information change processing module, be used for receiving after first user changes the request of he or she's communication information, according to first user's who carries in the described request mobile communication number obtain with first user ID of its binding and with first user ID be first user communication record of index, and change the communication information of user in this first user communication record according to described request; Then, from each address list, obtain the address list that includes first user ID in the contacts list and the user ID of the described address list of index, and after getting access to described user ID, the pairing portable terminal of mobile communication number of the user ID binding that the communication information of user in first user communication record is sent to and gets access to.
In the above embodiment of the present invention, because in the record of the user communication of network side storing, store the linking relationship that the user points to the contact person with the contacts list form, and need not be each its contact person's of user storage corresponding communication information, saved network storage space like this.On the other hand, when first its address list of user's acquisition request, point to its contact person's annexation by this user in the record of first user communication, find out first user's contact person's address list, and the communication information of contact person in these contact persons' the address list sent first user, thereby realized the interlock of network side and end side address list.
Description of drawings
Fig. 1 is the structural representation of the contact book management system that embodiments of the invention provided;
Fig. 2 a, Fig. 2 b, Fig. 2 c and Fig. 2 d are respectively user communication record data structure schematic diagram in the embodiment of the invention;
Fig. 3 is the schematic flow sheet of the establishment address list that embodiments of the invention provided;
Fig. 4 is one of schematic flow sheet that adds the contact person for the user that embodiments of the invention provided;
Fig. 5 for embodiments of the invention provided for the user add the contact person schematic flow sheet two;
Fig. 6 upgrades the schematic flow sheet of self files on each of customers for user that embodiments of the invention provided;
The user that Fig. 7 provides for embodiments of the invention deletes contact person's schematic flow sheet;
Fig. 8 is the schematic flow sheet of its address list of user's download that embodiments of the invention provided;
The structural representation of the address list management server that Fig. 9 a and Fig. 9 b provide for embodiments of the invention.
Embodiment
Problem at the prior art existence, the invention provides a kind of address list management technology, can each user's the individual address that be stored in network side is interconnected by this technical scheme, association link by between a user communication record and the record of other user communications realizes this user's complete address list function.Each user only need administer and maintain my address list, and a indexed links of pointing to other users of management maintenance gets final product again in addition.Like this, server only keeps its individual address for each user, and a point to this user and be set at contact person's indexed links data, thereby can greatly save network storage space.
Described address list management technical scheme may be implemented as a kind of book management method, also may be implemented as a kind of communication management server, perhaps a kind of communication management system; And, may be implemented as hardware, also may be implemented as software, perhaps be implemented as the combination of software and hardware.
Below in conjunction with accompanying drawing technical solution of the present invention is described in detail.
Fig. 1 shows the structural representation of the contact book management system that one embodiment of the present of invention provide.As shown in the figure, this contact book management system mainly comprises communication terminal 10, address list management server 20 (hereinafter to be referred as server 20) and is used for the database 30 that memory communicating is recorded data.Communication terminal 10 can be mobile communication terminal 12 or compunication terminal 14, and mobile communication terminal 12 can be that mobile phone, PDA or other have the Wireless Telecom Equipment of communication capacity.In another embodiment of communications management system of the present invention, server 20 and database 30 close and are located at together.
Can be between mobile communication terminal 12 and the server 20 by mobile communications network (as GSM, be global system for mobile communications) carry out information interaction, can carry out information interaction by the INTERNET network between compunication terminal 14 and the server 20, the address book data in the addressable and process database 30 of server 20.
Store contact person's address list of user in mobile communication terminal 12 or the compunication terminal 14, mainly comprise each contact person's files on each of customers in contact person's address list, comprise various communication clauses and subclauses in the files on each of customers, as name, phone number; Store all registered users' of contact book management system address list in the database 30, comprise user's files on each of customers in each user's the address list, and this user points to the linking relationship (hereinafter to be referred as contact person's link) of its contact person's files on each of customers.
On communication terminal 12 or the computer communicating terminal 14 the contact book management system client software is installed, the contact book management system server software is installed in the server 20.Server software provides the access path of WEB mode or provides other and the special-purpose interactive mode of client software.Client software can or be independent of original address list management software with original address list management software collaboration on the terminal, carries out alternately with server end.The client software of communication management system can cooperate with server software, and to finish the various management functions of address list, these management functions can comprise:
The user can safeguard the contact person's address list on it by portable terminal 12 or the terminal 14 that the communication management system client is installed, and comprising increases contact person, deletion contact person, and the user can also upload onto the server 20 with contact person's modification information; Server 20 can change the contact person's link in the address list of this user in the situation maintenance data base 30 according to the contact person of client upload;
The user can also be by portable terminal 12 or the terminal 14 that the communication management system client is installed, and request server 20 upgrades this user's files on each of customers; The user's that server 20 can be uploaded according to terminal files on each of customers modification information, user's files on each of customers in this user's the address list in the new database 30 more, and can be to this renewal of other user notifications that this user are added to the contact person, the contact person's address list so that these users upgrade in time on its terminal;
The user can also ask to recover or download this user's address list to server 20 by portable terminal 12 or the terminal 14 that the communication management system client is installed; Server 20 can obtain this user's All Contacts's files on each of customers, and send to this user place terminal according to the contact person's linking relationship of this user of record in the database 30; User place terminal can the receiving management server contact person's archives of 20 these users that send, and form contact person's address list on this terminal.
The existing way of contact person's address list of end side and storage format can be based on prior aries, and be relatively independent with the address list of network side (management server or database), just as the local address list of user terminal for the daily use of user.
Each registered user at contact book management system, server 20 distributes unique user communication record account for it, the address list account carries out unique identification by the user ID (user ID) that contact book management system distributes, and be index with the user ID, in database 30, distribute corresponding memory space as the address list memory space, be used to store this user's files on each of customers, contact person's linking relationship.User ID is unique related with user's a mobile communication number (as phone number).User ID is with the authentication that can realize its address list memory space of user capture for the password of user's distribution.
In the memory space of user communication record, the files on each of customers storage area can be divided into two zones, and one is the zone of being created and being safeguarded by user oneself, is called the user management district; One is the zone of being created and being safeguarded by server 20, is called the system management district, and the files on each of customers in the system management district normally writes when other people are added to the contact person with this address list account's user.The user can not visit the data in its system management district, and the data in system management district are invisible for this user.
The user management district stores every communication clauses and subclauses of user, address name, main the cell-phone number phone number of user ID binding (promptly with), other various phone number, E-mail address, MSN ID, address, date of birth, work unit or the like can be comprised, void item can also be kept in addition for user's expanded definition.Each communication clauses and subclauses can be provided with the open authority to the contact person, and the user can set and revise the open authority of every communication clauses and subclauses for its each contact person.If it is open that certain communication clauses and subclauses is set to certain contact person, then these communication clauses and subclauses to this contact person as seen, and after the change of this communication entry contents, but server 20 can to the user who these communication clauses and subclauses is had read right (be these users as seen) to these communication clauses and subclauses initiatively circular upgrade.Contact book management system can be provided with the open authority (this user ID tabulation can be described as permissions list) of each communication clauses and subclauses to the contact person by the mode that the user ID tabulation is set for each communication clauses and subclauses, record contact person's user ID (this user ID is the user ID that contact book management system distributes) in the permissions list, the communication clauses and subclauses for the user in its permissions list as seen.When initial, permissions list can be made as sky, it is invisible to any contact person user promptly to give tacit consent to all communication clauses and subclauses, and authority that can also the communication clauses and subclauses is set to All Contacts user all visible or all invisible.
The system management district stores the communication clauses and subclauses of limited given number, address name, main the cell-phone number phone number of user ID binding (promptly with), other various phone number, E-mail address etc. can be comprised, void item can also be kept in addition for user's expanded definition.Wherein, the main cell-phone number in main cell-phone number and the user management district is consistent, and is unique foundation that other users are made as this user the contact person.With the user management district, each communication clauses and subclauses all is provided with the open authority to other users, and can the open authority of each communication clauses and subclauses to other users be set by the mode that the user ID tabulation is set for each communication clauses and subclauses.Each communication clauses and subclauses can be given tacit consent to the user's opening that the user with this address list account is added to the contact person.If when having a plurality of users that same address list account's user is added to the contact person, the communication entry contents that writes in the system management district of this address list is identical, then do not repeat to write, if the content difference that writes at a plurality of users of communication clauses and subclauses then is considered as writing new communication clauses and subclauses and treats.If certain the communication clauses and subclauses correspondence in the system management district with no longer including Any user ID in the identification list, show these communication clauses and subclauses no longer as seen to Any user, then system can empty these communication clauses and subclauses.
Contact person's linking relationship of user shows directly which user the active user is made as the contact person of oneself.Contact person's linking relationship reality has just been stored contact person's user ID, can show as the identification of contacts tabulation, and the user ID in the tabulation is to user and invisible.When the user is added to the contact person with other certain users, server 20 just adds this contact person automatically in its identification of contacts tabulation user ID.By contact person's user ID, server 20 can read open this user's of giving of contact person various communication clauses and subclauses.
For the more convenient data structure of understanding the user communication record of network side, Fig. 2 a shows the data structure of certain user communication record of storage in the database 30.From Fig. 2 a as can be seen, the user of this Alice by name, its user ID is ID.A, ID.A and this user's main cell-phone number 138*****001 binding; The name of Alice and main cell-phone number to its All Contacts all as seen, the phone number of Alice and email address only to user ID be ID.B and ID.C the contact person as seen, the address of Alice is all invisible to anyone; It is the user of ID.B and ID.C that user ID is arranged among the contact person of Alice.The main cell-phone number in user management district and system management district is identical in the address list.
Below in conjunction with system construction drawing shown in Figure 1 and address book data structure shown in Figure 2, describe the address list management flow process of the embodiment of the invention in detail.
Referring to Fig. 3, the contact book management system that provides for one embodiment of the present of invention is the schematic flow sheet of user at network side establishment address list.For clarity sake, this flow process with Bill by name, phone number be the user of 138*****002 to ask to create address list be that example is described, this flow process mainly comprises following content:
Step 301, Bill initiate the request of establishment address list by the place terminal to server, wherein carry this user's phone number 138*****002;
In this step, Bill can be by the place terminal with the address list management interface that WEB mode or other mode access servers provide, and submits to server fill in information such as phone number, name by this interface after, and address list is created in request.
Step 302, server judge whether to have the corresponding address list of submitting to this user of phone number, if having, then execution in step 306; Otherwise execution in step 303;
Because the user communication that server is created record comes index by user ID, and therefore user ID and subscriber phone number binding, can judge whether to exist corresponding address list by user's cell-phone number.
Step 303, server are this user's distributing user ID, as ID.B, divide to be equipped with this user ID as the indexed data space, this data space can show as a user data table in the database, is the user and creates one with the address book data table of user ID as sign.Server can also be set initial challenge for this user ID, when being used for this user communication record of follow-up maintenance the user who sends maintenance request is carried out authentication.
The phone number that step 304, server are submitted Bill to write new establishment the address book data table the user management district main communication number bar now, this cell-phone number can also be write this address book data table the system management district corresponding communication bar now.If also carry other communication entry data in the request to create that Bill submits to, as address name, address etc., then server can these communication clauses and subclauses writes in the user management district corresponding communication bar now, the address book data structure of Bill after establishment is finished can be shown in Fig. 2 b, wherein, the open authority of the acquiescence of each communication clauses and subclauses is all invisible to the All Contacts of Bill in the user management district.
After step 305, server were created and finished the address list of Bill, Bill became the registered user of contact book management system.Server can be further sends SMS message to the mobile phone of correspondence according to the phone number of Bill, informs that address list creates successfully, and is that Bill distributes under the situation of password at server, and the password that distributes is carried on the mobile phone that short message sends to Bill.
Step 306, server return the notice of creating failure, and can further point out failure cause.
In the above-mentioned flow process, server is after the request of the establishment address list that receives the Bill submission, can also be further send SMS message or the message of other types to corresponding mobile terminal according to the phone number that carries in the request to create of submitting to, to reaffirm whether create address list, and after the affirmation message that obtains returning, carry out the creation operation of address list again.
Referring to Fig. 4, the contact book management system that provides for one embodiment of the present of invention adds contact person's schematic flow sheet for the registered user.For clarity sake, it serves as that the artificial example of contact is described that this flow process is added user Alice with user Bill request, and this flow process mainly comprises following content:
Step 401, Bill use the password logon server into its distribution by the place terminal;
Step 402, at server after authentication is passed through to Bill according to password, Bill is sent in the request of adding contact person Alice in its address list by the place terminal to server, wherein carry the phone number 138*****001 of the contact person Alice that will add, and the phone number 138*****002 of Bill;
In this step, the address list management interface that the user can provide with WEB mode or other mode access servers by the place terminal, and submit to server fill in contact persons' such as contact person's phone number information by this interface after, request is added the user of this phone number as its contact person.
Step 403, server are ID.B according to the user ID that the phone number 138*****002 of Bill finds binding;
Step 404, server are ID.A according to the user ID that the cell-phone number 138*****001 of Alice finds binding, and it is in the identification of contacts tabulation of address list (being the address list of Bill) of index that ID.A is added to ID.B;
Step 405, Bill are provided with open authority to Alice by the place terminal for each communication clauses and subclauses, and the result will be set submit to server;
In this step, the address list management interface that the user can provide with WEB mode or other mode access servers by the place terminal, and whether open contact person for this communication clauses and subclauses setting one by one to new interpolation by this interface.
Step 406, server add ID.A according to the open authority that the user is provided with in the permissions list of corresponding communication clauses and subclauses correspondence.Wherein, open if certain communication clauses and subclauses is set to this contact person, the user ID of adding this contact person in the user ID tabulation of this communication clauses and subclauses correspondence then shows that these communication clauses and subclauses to the contact person of this new interpolation as seen.The address book data structure of the user Bill of this moment can be shown in Fig. 2 c.
Step 407, server find corresponding address list according to the user ID ID.A of Alice, obtaining with ID.A is communication clauses and subclauses open to ID.B in the user management district in the address list of index, and it is given Bill or send to corresponding mobile terminal according to the cell-phone number of Bill by the address list management interface display, so that make its local contact person's address list of mobile terminal to update.
In this step, in determining the address list of ID.A during for the communication clauses and subclauses of the open authority of ID.B, server comprehensively in the address list of ID.A in user management district and the system management district authority of every communication clauses and subclauses be provided with to determine.Concrete, can be: if Alice is not added to the contact person with Bill, then can be unpromising in the user management district in the address list of ID.A the communication project of the open authority of ID.B, only determine whether as seen this moment ID.B according to the open authority of the communication clauses and subclauses in the system management district in the address list of ID.A; If Alice is added to the contact person with Bill, then server is with all show or send to the user of ID.B correspondence in user management district and the system management district to the open communication clauses and subclauses of ID.B, if the communication clauses and subclauses of the same name in two zones simultaneously as seen, then be as the criterion with this communication entry contents of user management district.
Step 405 in the above flow process~407 are optional.
Referring to Fig. 5, the contact book management system that provides for one embodiment of the present of invention adds contact person's schematic flow sheet for the registered user.For clarity sake, it is that 138*****003, the user who is called Emma are that the contact person is described that this flow process is added phone number with user Bill request, and this flow process mainly comprises following content:
Step 501, Bill use the password logon server into its distribution by the place terminal;
Step 502, at server after authentication is passed through to Bill according to password, Bill is sent in the request of adding contact person Emma in its address list by the place terminal to server, wherein carry the phone number 138*****003 of the contact person Emma that will add, and the phone number 138*****002 of Bill;
Step 503, server find the ID.B of binding according to phone number 138*****002, but do not search the user ID of binding according to phone number 138*****003;
Step 504, owing to do not find user ID with the contact person that will add binding, show that then this contact person does not also have the address list of correspondence, server is at first created address list for this contact person.
In this step, server distributes respective user ID:ID.E according to phone number 138*****003, and for its branch is equipped with the address list memory space that ID.E is an index, and the system management district in this memory space adds this contact person's phone number 138*****003.If discovering server also carries other information of contact person in the request of adding the contact person,, then other information of this contact person are written as in the system management district in the address list memory space that this contact person creates corresponding communication bar now as name.Wherein, this clauses and subclauses that write in system management district acquiescence to Bill as seen.At this moment, the user communication record of creating for Emma can be shown in Fig. 2 d.
Step 505, server be for after this contact person created address list, sends SMS message to it according to this contact person's phone number, and notice has been created address list for it, and waits for this user's activation.
Because being its active request, do not create the address list of Emma, but by other people (herein for Bill) when it is added to the contact person for its establishment, therefore this address list is current is unactivated state, only after Emma activates, as ask to add after the User Profile information, just can be activated and be that it distributes password.
Step 506, server add ID.E in the identification of contacts tabulation of address list (promptly being the address book data table of index with ID.B) of user Bill;
Step 507, Bill are provided with open authority to user Emma by the place terminal for each communication clauses and subclauses of this user, and the result will be set submit to server; The open authority that server is provided with according to the user, the user ID of in the permissions list of corresponding communication clauses and subclauses correspondence, adding Emma.
Step 508, server are given the communication clauses and subclauses of the open ID.B of giving in the address list of ID.E correspondence the user or are sent to corresponding mobile terminal according to the cell-phone number of Bill by the address list management interface display, so that make its local contact person's address list of mobile terminal to update.
Step 505 in the above flow process~508 are optional.
In the above-mentioned flow process, server is before creating address list for Emma, whether the cell-phone number that also can at first verify Emma is effective, and be verified as under the effective situation, cell-phone number according to Bill confirms whether to add this contact person to the corresponding mobile terminal transmission, and is obtaining creating address list for this contact person again after the affirmation.
Referring to Fig. 6, the registered user of the contact book management system that provides for one embodiment of the present of invention upgrades the flow process of the files on each of customers of himself.For clarity sake, this flow process with the cell-phone number be the user of 138*****001, Alice by name to ask to upgrade its files on each of customers be that example is described, this flow process mainly comprises following content:
Step 601, Alice use the password logon server into its distribution by the place terminal;
Step 602, after server passes through this subscriber authentication according to password, Alice sends the request of the files on each of customers that upgrades me by the place terminal to server, wherein carries its cell-phone number 138*****001, and the subscriber profile data after upgrading;
Except that user ID, other communication clauses and subclauses in the files on each of customers all allow the user to upgrade, as, name, address etc., and open authority.
The phone number that step 603, server are submitted to according to Alice finds the ID.A of binding, index corresponding address book data table with ID.A, then, according to the subscriber profile data of carrying in the update request, upgrade corresponding communication bar subscriber profile data now in this address book data table user management district, can also upgrade the permissions list under the respective entries according to the open authority of upgrading;
Step 604, server travel through the identification of contacts tabulation in each user communication record tables of data, find out the address book data table comprising ID.A.Comprise ID.A if be in the identification of contacts tabulation of address book data table of index with ID.B, then server obtains the phone number 138*****002 that binds with ID.B, then the open communication entry contents of ID.B of giving in the address list of Alice is sent to the 138*****002 corresponding mobile terminal, the contact person's address list so that this portable terminal upgrades in time on the terminal.
In this step, in determining the address list of ID.A during for the communication clauses and subclauses of the open authority of ID.B, server comprehensively in the address list of ID.A in user management district and the system management district authority of every communication clauses and subclauses be provided with to determine.
Especially, if the user revises the main communication handset number with the ID binding, for example cell-phone number A is revised as cell-phone number B, server can at first search for cell-phone number B whether set up corresponding address list, if do not have, then send SMS message and wait user answer in finite time to the pairing mobile phone of cell-phone number B, after the user replys affirmation, make amended main communication handset number avalidation, server can revise correspondingly also in the user data space in the system management district mainly that the communication handset number is cell-phone number B; If cell-phone number B has established address list, if the user ID of binding with cell-phone number B is user ID B, then whether whois lookup has the user that user ID B is made as the contact person, if have, then all user ID B that find are replaced with user ID A (being the user ID of cell-phone number A binding), then every entry contents and authority in the system management district in the address list of this user ID B are merged to the system management district of user ID A, delete user ID B at last and discharge its data space.
Referring to Fig. 7, the registered user of the contact book management system that provides for one embodiment of the present of invention deletes contact person's schematic flow sheet in contact person's address list of its network side, and this flow process mainly comprises following content:
Step 701, user use the password logon server into its distribution by the place terminal;
Step 702, after server passes through this subscriber authentication according to password, this user sends deletion contact person's request by the place terminal to server, wherein carries this user's main phone number and the contact person's that will delete main phone number;
Step 703, server find the user ID of binding according to the phone number of initiating requesting users, index corresponding address book data table with this user ID, then, the deletion user ID corresponding from the identification of contacts tabulation of this address book data table with the contact person's that will delete main phone number;
In the user list of each communication clauses and subclauses correspondence, the user ID deletion with this contact person keeps the user list of each communication clauses and subclauses correspondence in the system management district constant in step 704, the user management zone of server from this address book data table.
Referring to Fig. 8, the registered user of the contact book management system that provides for one embodiment of the present of invention downloads the schematic flow sheet of its address list from the network side request, and this flow process mainly comprises following content:
Step 801, user use the password logon server into its distribution by the place terminal;
Step 802, after server passes through this subscriber authentication according to password, this user sends the request that its address list is downloaded in request by the place terminal to server, wherein carries this user's main phone number;
After step 803, server find the user ID of binding according to this phone number, index corresponding address book data table by this user ID;
Step 804, server travel through the user ID in the identification of contacts tabulation in this user communication record tables of data, for each user ID that traverses, server indexes corresponding address book data table by this user ID, with the files on each of customers in this address book data table, the open authority of initiating requesting users is sent to this user then by it.
Step 805, user receive user communication record data by the place terminal, and form the contact person's address list on this terminal.
In order further to save the memory space of network side address list, in the another embodiment of the present invention, management server can be after the operation of finishing the deletion contact person, perhaps according to setting-up time or cycle, check the address list memory space of each user ID correspondence, be sky if find the user management district of certain user's address list memory space, and current without any the user with this user as the contact person, promptly, this user ID does not appear in contact person's lists of links of Any user, then management server thinks that this user ID and corresponding address list memory space thereof lost efficacy, and deletes this user ID and discharge corresponding address list memory space.
Based on identical technical conceive, embodiments of the invention also provide a kind of address list management server.
Shown in Fig. 9 a, the address list management server that one embodiment of the present of invention provide can comprise:
Address list memory module 901, be used to store user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding; Its address book data structure can be shown in Fig. 2 a;
Communication information change processing module 902, be used for receiving after first user changes the request of he or she's communication information, according to first user's who carries in the described request mobile communication number obtain with first user ID of its binding and with first user ID be first user communication record of index, and change the communication information of user in this first user communication record according to described request; Then, from each address list, obtain the address list that includes first user ID in the contacts list and the user ID of the described address list of index, and after getting access to described user ID, the pairing portable terminal of mobile communication number of the user ID binding that the communication information of user in first user communication record is sent to and gets access to.Its communication information change implementation procedure can be with reference to flow process shown in Figure 6.
If in the address list of address list memory module 901 storage, each the communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, be used to store user ID with this user's contact person's mobile communication number binding;
Then communication information change processing module 902 is further used for, for each address list that includes first user ID in the contacts list, after getting access to the user ID of this address list of index, permissions list according to each communication clauses and subclauses correspondence in the communication information of user in the record of first user communication, obtain the pairing communication clauses and subclauses of the permissions list that includes described user ID, and the content of the communication clauses and subclauses that get access to is sent.
If in the address list of address list memory module 901 storages, the zone of storage user communication information comprises user management district and system management district in each user's the address list; Communication clauses and subclauses in the system management district are write at the communication information that other users are provided when this user is added to the contact person by network side, comprise the person's of writing user ID in the pairing permissions list of communication clauses and subclauses that writes at least;
User's communication information in first user communication record of being changed of communication information change processing module 902 then is meant first user's who stores in the user management district in the record of first user communication communication information; Communication information change processing module 902 is further used for, permissions list according to each communication clauses and subclauses correspondence in system management district and the user management district in the record of first user communication, obtain the pairing communication clauses and subclauses of the permissions list that wherein includes described user ID, wherein, for identical communication clauses and subclauses in system management district and the user management district, be as the criterion with the communication clauses and subclauses in the user management district.
Above-mentioned address book server can also comprise:
The contact person changes processing module 903, be used for receiving after first user adds contact person's request, obtain with first user ID of its binding and be first user communication record of index according to first user's who carries in the described request mobile communication number with first user ID, obtain user ID with its binding according to the contact person's who carries in the described request mobile communication number, and after the user ID that gets access to its binding, the user ID that gets access to is added in the contacts list of first user communication record.
Above-mentioned address book server can also comprise: address list creation module 905 is used for creating the user communication record and stores address list memory module 901 into.
When the contact person changes processing module 903 and fails to get access to user ID with its binding according to the contact person's who carries in according to described request mobile communication number, notify described address list creation module to create address list, and after address list is finished in establishment, the user ID of the address list of this establishment of index is added in the contacts list of first user communication record; Address list creation module 905 changes the notice of processing module 903 according to the contact person, generates the user ID with described contact person's mobile communication number binding, and creating with this user ID is the address list of index.
When changing processing module 903, the contact person receives after first user deletes contact person's request, obtain first user ID with its binding according to first user's who carries in the described request mobile communication number, find corresponding first user communication record according to first user ID; Obtain user ID with its binding according to the contact person's who carries in the described request mobile communication number, and will the deletion from the identification of contacts tabulation to the record of first user communication of this user ID.
Can also comprise in the above-mentioned address book server:
Cleaning module 904, be used for regularly searching the user ID whether contacts list that is not present in current all user communication records is arranged, if find such user ID, and my communication information in the address list of this user ID correspondence is empty, then delete this user ID, and discharge the memory space of the address list of this user ID correspondence.
Shown in Fig. 9 b, the address list management server that an alternative embodiment of the invention provides can comprise:
Address list memory module 910, be used to store user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
Synchronous processing module 912, be used for receiving after first user obtains the request of its address list, obtain with first user ID of its binding and be first user communication record of index with first user ID according to first user's who carries in the described request mobile communication number; Then, according to the user ID in the contacts list of first user communication record obtain with described user ID be index address list, and the communication information of user in the address list that gets access to is sent to first user's mobile communication number corresponding mobile terminal.
If in the address list of address list memory module 910 storage, each the communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, be used to store user ID with this user's contact person's mobile communication number binding;
Then synchronous processing module 912 is for each address list that gets access to according to the user ID in the contacts list of first user communication record, permissions list according to each communication clauses and subclauses correspondence in user's wherein the communication information, obtain the pairing communication clauses and subclauses of the permissions list that includes first user ID, and the content of the communication clauses and subclauses that get access to is sent.
Also can further comprise the corresponding function module in the address book server shown in Fig. 9 a in the above-mentioned address book server.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.

Claims (24)

1. book management method, it is characterized in that, network side storing has user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
When network side receives after first user changes the request of he or she's communication information, according to first user's who carries in the described request mobile communication number obtain with first user ID of its binding and with first user ID be first user communication record of index, and change the communication information of user in this first user communication record according to described request; Then, from each address list, obtain the address list that includes first user ID in the contacts list and the user ID of this address list of index, and after getting access to user ID, the pairing portable terminal of mobile communication number of the user ID binding that the communication information of user in first user communication record is sent to and gets access to.
2. the method for claim 1 is characterized in that, each the communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, is used to store the user ID with this user's contact person's mobile communication number binding;
Send the communication information of user in the record of first user communication, be specially:
For each address list that includes first user ID in the contacts list, after getting access to the user ID of this address list of index, permissions list according to each communication clauses and subclauses correspondence in the communication information of user in the record of first user communication, obtain the pairing communication clauses and subclauses of the permissions list that includes described user ID, and the content of the communication clauses and subclauses that get access to is sent.
3. method as claimed in claim 2, it is characterized in that, also carry the information of change of the permissions list of communication clauses and subclauses correspondence in the described request, change the communication information of user in the record of first user communication according to described request, also comprise:, change the permissions list of corresponding communication clauses and subclauses correspondence in described first user communication record according to the modification information of the permissions list of the communication clauses and subclauses correspondence of carrying in the described request;
Obtain the permissions list of the pairing communication clauses and subclauses of the permissions list that includes described user ID time institute foundation, be meant according to described request permissions list after changing.
4. as claim 2 or 3 described methods, it is characterized in that the zone of storage user communication information comprises user management district and system management district in each user's the address list; Communication clauses and subclauses in the system management district are write at the communication information that other users are provided when this user is added to the contact person by network side, comprise the person's of writing user ID in the pairing permissions list of communication clauses and subclauses that writes at least;
User's communication information in the record of first user communication that changed is meant first user's who stores in the user management district in the record of first user communication communication information;
Obtain the pairing communication clauses and subclauses of the permissions list that includes described user ID, be specially: according to the permissions list of each communication clauses and subclauses correspondence in system management district and the user management district in the record of first user communication, obtain the pairing communication clauses and subclauses of the permissions list that wherein includes described user ID, wherein, for identical communication clauses and subclauses in system management district and the user management district, be as the criterion with the communication clauses and subclauses in the user management district.
5. the method for claim 1 is characterized in that, network side receive first user change the request of user's communication information after, obtain the user ID of binding before, also carry out authentication, and checking by after obtain the user ID of binding.
6. the method for claim 1 is characterized in that, also comprises:
When network side receives after first user adds contact person's request, obtain with first user ID of its binding and be first user communication record of index according to first user's who carries in the described request mobile communication number with first user ID, obtain user ID with its binding according to the contact person's who carries in the described request mobile communication number, and after the user ID that gets access to its binding, the user ID that gets access to is added in the contacts list of first user communication record.
7. method as claimed in claim 6 is characterized in that, if fail to get access to user ID with its binding according to the contact person's who carries in the described request mobile communication number, then also comprises:
Generate the user ID with described contact person's mobile communication number binding, creating with this user ID is the address list of index, with adding in the contacts list that first user communication records with sign of generating.
8. method as claimed in claim 7 is characterized in that, the zone of storage user communication information comprises user management district and system management district in the address list of being created;
After creating described address list, also comprise:
Described contact person's mobile communication number is write the system management district of the address list of establishment, and in the permissions list of this mobile communication number clauses and subclauses correspondence, add first user ID;
The state of this address list is made as unactivated state,, requires the user to activate the request of address list to the corresponding mobile terminal transmission according to described contact person's mobile communication number; After receiving the response that described portable terminal returns, the mobile communication number of this portable terminal is write the user management district of this address list, and this address list is set to state of activation.
9. method as claimed in claim 6, it is characterized in that, after described user ID being added in the contacts list of first user communication record, also comprise: for the visible authority that its each communication clauses and subclauses are provided with, described contact person's user ID is added in the permissions list of corresponding communication clauses and subclauses correspondence in first address list for described contact person according to first user.
10. the method for claim 1 is characterized in that, also comprises:
When network side receives after first user deletes contact person's request, obtain with first user ID of its binding and be first user communication record of index according to first user's who carries in the described request mobile communication number with first user ID, obtain user ID with its binding according to the contact person's who carries in the described request mobile communication number, and with the user ID that gets access to from deletion to the identification of contacts tabulation of first user communication record.
11. method as claimed in claim 10 is characterized in that, each the communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, is used to store the user ID with this user's contact person's mobile communication number binding;
Described contact person's user ID after the deletion, is also comprised from the contacts list to the record of first user communication: described contact person's user ID is included from the record of first user communication in the permissions list of this user ID and delete.
12. the method for claim 1 is characterized in that, also comprises:
Network side is regularly searched the user ID that whether has in the contacts list that is not present in current all user communication records, if find such user ID, and with the user's communication information in the address list of this user ID index is sky, then delete this user ID, and discharge the memory space of the address list of this user ID correspondence.
13. book management method, it is characterized in that, network side storing has user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
When network side receives after first user obtains the request of its address list, obtain with first user ID of its binding and be first user communication record of index with first user ID according to first user's who carries in the described request mobile communication number; Then, obtaining with described user ID according to the user ID in the contacts list of first user communication record is the address list of index, and the communication information of user in the address list that gets access to is sent to first user's mobile communication number corresponding mobile terminal.
14. method as claimed in claim 13 is characterized in that, each the communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, is used to store the user ID with this user's contact person's mobile communication number binding;
Send the communication information of user in the address list, be specially:
For each address list that gets access to according to the user ID in the contacts list of first user communication record, permissions list according to each communication clauses and subclauses correspondence in user's wherein the communication information, obtain the pairing communication clauses and subclauses of the permissions list that includes first user ID, and the content of the communication clauses and subclauses that get access to is sent.
15. method as claimed in claim 13 is characterized in that, the zone of storage user communication information comprises user management district and system management district in each user's the address list; Communication clauses and subclauses in the system management district are write at the communication information that other users are provided when this user is added to the contact person by network side, comprise the person's of writing user ID in the pairing permissions list of communication clauses and subclauses that writes at least;
Obtain the pairing communication clauses and subclauses of the permissions list that includes first user ID, be specially: according to the permissions list of each communication clauses and subclauses correspondence in system management district and the user management district, the pairing communication clauses and subclauses of permissions list that wherein include first user ID, wherein, for identical communication clauses and subclauses in system management district and the user management district, be as the criterion with the communication clauses and subclauses in the user management district.
16. an address list management server is characterized in that, comprising:
The address list memory module, be used to store user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
Communication information change processing module, be used for receiving after first user changes the request of he or she's communication information, according to first user's who carries in the described request mobile communication number obtain with first user ID of its binding and with first user ID be first user communication record of index, and change the communication information of user in this first user communication record according to described request; Then, from each address list, obtain the address list that includes first user ID in the contacts list and the user ID of this address list of index, and after getting access to user ID, the pairing portable terminal of mobile communication number of the user ID binding that the communication information of user in first user communication record is sent to and gets access to.
17. address list management server as claimed in claim 16 is characterized in that,
In the address list of storing in the described address list memory module, each the communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, is used to store the user ID with this user's contact person's mobile communication number binding;
Described communication information change processing module is further used for, for each address list that includes first user ID in the contacts list, after getting access to the user ID of this address list of index, permissions list according to each communication clauses and subclauses correspondence in the communication information of user in the record of first user communication, obtain the pairing communication clauses and subclauses of the permissions list that includes described user ID, and the content of the communication clauses and subclauses that get access to is sent.
18. address list management server as claimed in claim 17 is characterized in that,
In the address list of storing in the described address list memory module, the zone of storage user communication information comprises user management district and system management district in each user's the address list; Communication clauses and subclauses in the system management district are write at the communication information that other users are provided when this user is added to the contact person by network side, comprise the person's of writing user ID in the pairing permissions list of communication clauses and subclauses that writes at least;
Described communication information changes the communication information of user in first user communication record that processing module changed, is meant first user's who stores in the user management district in the record of first user communication communication information;
Described communication information change processing module is further used for, permissions list according to each communication clauses and subclauses correspondence in system management district and the user management district in the record of first user communication, obtain the pairing communication clauses and subclauses of the permissions list that wherein includes described user ID, wherein, for identical communication clauses and subclauses in system management district and the user management district, be as the criterion with the communication clauses and subclauses in the user management district.
19. address book server as claimed in claim 16 is characterized in that, also comprises:
The contact person changes processing module, be used for receiving after first user adds contact person's request, obtain with first user ID of its binding and be first user communication record of index according to first user's who carries in the described request mobile communication number with first user ID, obtain user ID with its binding according to the contact person's who carries in the described request mobile communication number, and after the user ID that gets access to its binding, the user ID that gets access to is added in the contacts list of first user communication record.
20. address book server as claimed in claim 19 is characterized in that, also comprises the address list creation module;
Described contact person changes processing module and is further used for, when the contact person's who carries in according to described request mobile communication number fails to get access to user ID with its binding, notify described address list creation module to create address list, and after address list is finished in establishment, the user ID of the address list of this establishment of index is added in the contacts list of first user communication record;
Described address list creation module is used for changing according to described contact person the notice of processing module, generates the user ID with described contact person's mobile communication number binding, and creating with this user ID is the address list of index.
21. address book server as claimed in claim 19, it is characterized in that, described contact person changes processing module and is further used for, receiving after first user deletes contact person's request, obtaining with first user ID of its binding and be first user communication record of index with first user ID according to first user's who carries in the described request mobile communication number; Obtain user ID with its binding according to the contact person's who carries in the described request mobile communication number, and with this user ID from deletion to the identification of contacts tabulation of first user communication record.
22. address book server as claimed in claim 16 is characterized in that, also comprises:
The cleaning module, be used for regularly searching the user ID whether contacts list that is not present in current all user communication records is arranged, if find such user ID, and my communication information in the address list of this user ID correspondence is empty, then delete this user ID, and discharge the memory space of the address list of this user ID correspondence.
23. an address book server is characterized in that, comprising:
The address list memory module, be used to store user's address list, the user ID that described address list is bound with the mobile communication number of user under this address list is an index, each user's address list comprises user's communication information and this user's contacts list, and described contacts list is used to store the user ID with this user's contact person's mobile communication number binding;
Synchronous processing module, be used for receiving after first user obtains the request of its address list, obtain with first user ID of its binding and be first user communication record of index with first user ID according to first user's who carries in the described request mobile communication number; Then, according to the user ID in the contacts list of first user communication record obtain with described user ID be index address list, and the communication information of user in the address list that gets access to is sent to first user's mobile communication number corresponding mobile terminal.
24. address book server as claimed in claim 23, it is characterized in that, in the address list of described address list memory module storage, each communication clauses and subclauses correspondence in each user he or she's the communication information is provided with permissions list, is used to store the user ID with this user's contact person's mobile communication number binding;
Described synchronous processing module is further used for, for each address list that gets access to according to the user ID in the contacts list of first user communication record, permissions list according to each communication clauses and subclauses correspondence in user's wherein the communication information, obtain the pairing communication clauses and subclauses of the permissions list that includes first user ID, and the content of the communication clauses and subclauses that get access to is sent.
CN2009102423029A 2009-12-08 2009-12-08 Address book management method and device Pending CN102088519A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2009102423029A CN102088519A (en) 2009-12-08 2009-12-08 Address book management method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2009102423029A CN102088519A (en) 2009-12-08 2009-12-08 Address book management method and device

Publications (1)

Publication Number Publication Date
CN102088519A true CN102088519A (en) 2011-06-08

Family

ID=44100123

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2009102423029A Pending CN102088519A (en) 2009-12-08 2009-12-08 Address book management method and device

Country Status (1)

Country Link
CN (1) CN102088519A (en)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102438214A (en) * 2011-09-14 2012-05-02 武汉飞众科技有限公司 Method for self-maintaining mobile phone communication record of contact
CN102497483A (en) * 2011-11-30 2012-06-13 中国联合网络通信集团有限公司 Address book management method of multimedia public phone system, apparatuses and multimedia public phone system
CN102594918A (en) * 2012-03-19 2012-07-18 中兴通讯股份有限公司 Address book realization method and system for terminal, and terminal
CN102882851A (en) * 2012-09-03 2013-01-16 东莞宇龙通信科技有限公司 Generating method of address book and server
CN102882953A (en) * 2012-09-18 2013-01-16 李建成 Communication number synchronization method and system
CN102917035A (en) * 2012-09-27 2013-02-06 东莞宇龙通信科技有限公司 Address book updating method and system
CN102968430A (en) * 2011-09-01 2013-03-13 三星电子株式会社 Method and apparatus for automatically generating and managing groups in address book
CN102984213A (en) * 2012-11-08 2013-03-20 北京小米科技有限责任公司 Information sharing method, device and system
CN103095829A (en) * 2013-01-15 2013-05-08 上海交通大学 Network contact list system achieving version management and authority management
CN103139761A (en) * 2013-01-17 2013-06-05 北京奇虎科技有限公司 Information real-time show method and mobile communication terminal
CN103281192A (en) * 2013-05-31 2013-09-04 腾讯科技(深圳)有限公司 Method, device and system for retrieving data
CN103338148A (en) * 2013-06-28 2013-10-02 北京小米科技有限责任公司 Address book updating methods and address book updating device
CN103338304A (en) * 2013-06-18 2013-10-02 李健 Scheme for synchronously updating user electronic communication contact details in mobile terminal
CN103369062A (en) * 2012-04-11 2013-10-23 丁瑞彭 Contact-person information management arithmetic, method and system based on inter-address-book relations
CN104065673A (en) * 2013-03-18 2014-09-24 中国移动通信集团福建有限公司 Method and device used for synchronizing mail list to server
CN104468318A (en) * 2013-09-18 2015-03-25 腾讯科技(北京)有限公司 Method and server for recovering reverse relationship chain in network communication
CN104573010A (en) * 2015-01-08 2015-04-29 笨鸟软件科技(北京)有限公司 Information processing method and system
CN104601829A (en) * 2013-11-13 2015-05-06 腾讯科技(深圳)有限公司 Notification method and device of communication number
CN104869561A (en) * 2014-02-24 2015-08-26 中国移动通信集团山西有限公司 Contacts updating method, client and contacts management platform
CN104980329A (en) * 2014-04-04 2015-10-14 中国移动通信集团公司 Address book management method address book management device and mobile agent server
CN105306346A (en) * 2015-10-14 2016-02-03 深圳市金立通信设备有限公司 Information change notification method and terminal
CN105554293A (en) * 2015-12-24 2016-05-04 深圳市金立通信设备有限公司 Information sharing method and terminal
CN107493323A (en) * 2017-07-31 2017-12-19 四川长虹电器股份有限公司 A kind of system and method for smart mobile phone synchronization contact person
CN109981694A (en) * 2017-12-27 2019-07-05 中国移动通信集团公司 A kind of synchronous method, server and terminal

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5315705A (en) * 1991-02-25 1994-05-24 Hitachi, Ltd. Communication address management system
CN1713674A (en) * 2004-06-25 2005-12-28 华为技术有限公司 Telephone book system, updating and calling method for telephone book of mobile terminal telephone book
CN201142742Y (en) * 2007-10-22 2008-10-29 孙国仲 Address book management system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5315705A (en) * 1991-02-25 1994-05-24 Hitachi, Ltd. Communication address management system
CN1713674A (en) * 2004-06-25 2005-12-28 华为技术有限公司 Telephone book system, updating and calling method for telephone book of mobile terminal telephone book
CN201142742Y (en) * 2007-10-22 2008-10-29 孙国仲 Address book management system

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102968430A (en) * 2011-09-01 2013-03-13 三星电子株式会社 Method and apparatus for automatically generating and managing groups in address book
CN102968430B (en) * 2011-09-01 2017-05-24 三星电子株式会社 Method and apparatus for automatically generating and managing groups in address book
CN102438214A (en) * 2011-09-14 2012-05-02 武汉飞众科技有限公司 Method for self-maintaining mobile phone communication record of contact
CN102497483A (en) * 2011-11-30 2012-06-13 中国联合网络通信集团有限公司 Address book management method of multimedia public phone system, apparatuses and multimedia public phone system
CN102594918A (en) * 2012-03-19 2012-07-18 中兴通讯股份有限公司 Address book realization method and system for terminal, and terminal
CN102594918B (en) * 2012-03-19 2018-07-24 中兴通讯股份有限公司 A kind of method, terminal and system that terminal contact is realized
CN103369062A (en) * 2012-04-11 2013-10-23 丁瑞彭 Contact-person information management arithmetic, method and system based on inter-address-book relations
CN102882851B (en) * 2012-09-03 2016-06-08 东莞宇龙通信科技有限公司 The generation method of address list and server
CN102882851A (en) * 2012-09-03 2013-01-16 东莞宇龙通信科技有限公司 Generating method of address book and server
CN102882953A (en) * 2012-09-18 2013-01-16 李建成 Communication number synchronization method and system
CN102917035A (en) * 2012-09-27 2013-02-06 东莞宇龙通信科技有限公司 Address book updating method and system
CN102984213A (en) * 2012-11-08 2013-03-20 北京小米科技有限责任公司 Information sharing method, device and system
CN102984213B (en) * 2012-11-08 2016-07-06 小米科技有限责任公司 A kind of method of information sharing, Apparatus and system
CN103095829B (en) * 2013-01-15 2015-09-23 上海交通大学 Realize the network contact list system of version management and rights management
CN103095829A (en) * 2013-01-15 2013-05-08 上海交通大学 Network contact list system achieving version management and authority management
CN103139761A (en) * 2013-01-17 2013-06-05 北京奇虎科技有限公司 Information real-time show method and mobile communication terminal
CN103139761B (en) * 2013-01-17 2017-11-14 北京奇虎科技有限公司 The method and communication terminal of a kind of information real-time show
CN104065673A (en) * 2013-03-18 2014-09-24 中国移动通信集团福建有限公司 Method and device used for synchronizing mail list to server
CN104065673B (en) * 2013-03-18 2017-11-03 中国移动通信集团福建有限公司 A kind of implementation method and device by address list synchronization to server
CN103281192A (en) * 2013-05-31 2013-09-04 腾讯科技(深圳)有限公司 Method, device and system for retrieving data
CN103281192B (en) * 2013-05-31 2015-07-15 腾讯科技(深圳)有限公司 Method, device and system for retrieving data
CN103338304A (en) * 2013-06-18 2013-10-02 李健 Scheme for synchronously updating user electronic communication contact details in mobile terminal
CN103338148B (en) * 2013-06-28 2018-11-23 小米科技有限责任公司 The update method and device of address list
CN103338148A (en) * 2013-06-28 2013-10-02 北京小米科技有限责任公司 Address book updating methods and address book updating device
WO2014206146A1 (en) * 2013-06-28 2014-12-31 小米科技有限责任公司 Address book update method and apparatus
CN104468318A (en) * 2013-09-18 2015-03-25 腾讯科技(北京)有限公司 Method and server for recovering reverse relationship chain in network communication
CN104468318B (en) * 2013-09-18 2019-03-26 腾讯科技(北京)有限公司 The method and server of inverse relationship chain are recycled in network communication
CN104601829A (en) * 2013-11-13 2015-05-06 腾讯科技(深圳)有限公司 Notification method and device of communication number
CN104869561A (en) * 2014-02-24 2015-08-26 中国移动通信集团山西有限公司 Contacts updating method, client and contacts management platform
CN104980329A (en) * 2014-04-04 2015-10-14 中国移动通信集团公司 Address book management method address book management device and mobile agent server
CN104573010A (en) * 2015-01-08 2015-04-29 笨鸟软件科技(北京)有限公司 Information processing method and system
CN104573010B (en) * 2015-01-08 2018-05-01 笨鸟软件科技(北京)有限公司 A kind of information processing method and system
CN105306346A (en) * 2015-10-14 2016-02-03 深圳市金立通信设备有限公司 Information change notification method and terminal
CN105306346B (en) * 2015-10-14 2019-07-12 深圳市金立通信设备有限公司 A kind of notification method and terminal of information change
CN105554293A (en) * 2015-12-24 2016-05-04 深圳市金立通信设备有限公司 Information sharing method and terminal
CN107493323A (en) * 2017-07-31 2017-12-19 四川长虹电器股份有限公司 A kind of system and method for smart mobile phone synchronization contact person
CN109981694A (en) * 2017-12-27 2019-07-05 中国移动通信集团公司 A kind of synchronous method, server and terminal

Similar Documents

Publication Publication Date Title
CN102088519A (en) Address book management method and device
CN1656468B (en) Method, apparatus and system for synchronizing data storage modes in different data memories
CN101622837B (en) Sharing of media using contact data
CN103595730A (en) Ciphertext cloud storage method and system
CN102281324B (en) Method for remote authorized management on menu items of mobile communication terminal system
KR20110052356A (en) Method for providing contact merging service in portable terminal
CN107861686B (en) File storage method, server and computer readable storage medium
AU2010337430B2 (en) System and method for a global directory service
CN102576425A (en) Information update system
CN103067478A (en) Method, device and system for transmitting contact person information
CN102082818A (en) Method and system for storing and managing graphical data and structured data based on cloud storage
CN104092770A (en) Inner-enterprise address book management method and system based on cloud computing
CN103119911A (en) System and method for synchronizing the profile of a user in social networks and the user's personal contact card (PCC)
CN102421091A (en) Address book updating method and system
CN101330657A (en) Address list system and implementing method thereof
CN102685101A (en) Proxy communications on a social network
CN107391758A (en) Database switching method, device and equipment
CN101730085B (en) Address book data synchronizing method and system
CN101510895A (en) System and method for managing mobile address book based on internet
CN104615662A (en) Data processing method and device and terminal device
CN1818902A (en) Synchronizing server and device data using device data schema
CN103095891A (en) Method, device and terminal of quickly inputting information of business card
CN102711034A (en) Information synchronization method based on personal information management system, device and communication terminal
CN102469457A (en) Communication system and synchronization and maintenance method of address list information
CN101686542B (en) Method, system and device for informing removal

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20110608