CN101527896B - Personal information management method and device - Google Patents
Personal information management method and device Download PDFInfo
- Publication number
- CN101527896B CN101527896B CN2009101323502A CN200910132350A CN101527896B CN 101527896 B CN101527896 B CN 101527896B CN 2009101323502 A CN2009101323502 A CN 2009101323502A CN 200910132350 A CN200910132350 A CN 200910132350A CN 101527896 B CN101527896 B CN 101527896B
- Authority
- CN
- China
- Prior art keywords
- user
- information
- contact person
- branch
- data
- 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
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a personal information management method. The method comprises the following steps: when receiving personal information input by a user, establishing a personal branch and storing the personal information in the personal branch; when receiving a message for releasing the personal information, establishing a main branch corresponding to the personal branch and storing an information entry needing to be released in the personal information in the main branch; and when receiving a request which is sent by a certain contact and is used for acquiring the personal information of the user, synchronizing the information entry which is stored in the main branch and needs to be released into a user branch established by the contact. The invention also discloses a personal information management device. The personal information management method and the device thereof can separate storage and release of the contact information; in addition, when the request of a certain contact is received, the data in the main branch is synchronized into the user branch of the contact, thus avoiding that the user receives information which is rejected to be updated.
Description
Technical field
The present invention relates to field of information management, particularly relate to a kind of PIM method and device.
Background technology
The address list people carry out the important means of information management, can write down contact person's various contact methods and information through address list.Today of popularizing in the Internet, this media of the Internet that passes through that People more and more is many is unified preservation information, thereby can under the situation that can connect the Internet, obtain up-to-date information whenever and wherever possible.Yet the associated person information in the address list is not to be constant, after associated person information changes, original information can't continue to keep and the contact person between the communication tie, therefore only can't satisfy people and keep the demand linked up through the record of the Internet memory communicating.
At present; The renewal that some technical schemes allow the user to issue personal information for example, can be uploaded address list to the synchronizing information server through client software is installed; The administration-management of going forward side by side reason, synchronous; Utilize this method, the user can upload onto the server the personal information of oneself, by server information is distributed to the user relevant with this contact person then.Yet in this technical scheme; In case the user is published to server with personal information; Server will be distributed to these personal information this user's contact person automatically; But its result often, and the certain user is reluctant that the content of upgrading is updated, or some do not hope that the interim personal information of issuing is published away and does not have approach to preserve.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of PIM method and device, can the storage and the issue of personal information be made a distinction, be convenient to realize more neatly management personal information.
For realizing above-mentioned purpose, the invention provides following scheme:
A kind of PIM method comprises:
When receiving its personal information of user's input, set up private branch, said personal information is kept in the said private branch;
When receiving the message of the said personal information of issue, set up the main split corresponding, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information with said private branch;
When receive that certain contact person sends obtain this userspersonal information's request the time, the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
Preferably, comprise the Back ground Information that key field is fixing in the said private branch, and key-value pair is by user-defined extend information;
Comprise the Back ground Information that key field is fixing in the said user branch, and key-value pair is by the self-defining self-defined information of contact person.
Preferably, also comprise:
Receive the grouping information of user to contact person in the address list, and user's appointment need be to contact person's information releasing clauses and subclauses of each group;
Also comprise when needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information:
With each group of this user's appointment and need the corresponding relation between the information releasing clauses and subclauses to be kept in the said main split;
With comprising in the said user branch that needs the information releasing clauses and subclauses to be synchronized to and to set up for this contact person:
Judge the group that this contact person is affiliated, need be synchronized in the user branch that sets up into this contact person to this group contact person information releasing clauses and subclauses.
Preferably, also comprise:
Data are upgraded when main split, and perhaps the user's branch data with certain contact person clashes, when perhaps the data of the modification carried out in off-line state of certain contact person and main split clash, with taking place to upgrade or the data entries of conflict is prompted to this contact person.
Preferably, also comprise:
When user's branch data of main split's data and certain contact person clashes, provide the data of main split and user branch to supply this contact person to select;
Confirm the final result of user's branch data according to the result of this contact person's selection.
Preferably, also comprise:
When the modification of carrying out in off-line state as certain contact person and the data of user branch clash; Judge whether main split's data exist with user's branch data and conflict; If exist, provide the amended data of this contact person, main split's data and user's branch data to supply this contact person to select; Otherwise, provide the data of amended data of this contact person and user branch to supply this contact person to select;
Confirm the final result of user's branch data according to the result of this contact person's selection.
Preferably, also comprise:
If the user uses the international identification code MSISDN of travelling carriage login system; Then this MSISDN is mapped to the unique virtual number of the account of an overall situation; And said virtual number of the account offered this user's contact person, preserve the mapping relations between this virtual number of the account and this user's the personal information;
When the user changes MSISDN, receive and make amendment and information releasing after the user uses former MSISDN login, upgrade this user's in the main split MSISDN information;
Receive certain contact person when obtaining the request of the current MSISDN information of this user through said virtual number of the account, with amended MSISDN information synchronization in the main split in this contact person's user branch.
A kind of personal information management device comprises:
Private branch when being used to receive its personal information of user's input, is set up in the first preservation unit, and said personal information is kept in the said private branch;
The second preservation unit is used for when receiving the message of the said personal information of issue, setting up the main split corresponding with said private branch, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information;
The information release unit, be used for when receive that certain contact person sends obtain this userspersonal information's request the time, the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
Preferably, comprise the Back ground Information that key field is fixing in the said private branch, and key-value pair is by user-defined extend information;
Comprise the Back ground Information that key field is fixing in the said user branch, and key-value pair is by the self-defining self-defined information of contact person.
Preferably, also comprise:
The authority information receiving element is used to receive the grouping information of user to contact person in the address list, and user's appointment need be to contact person's information releasing clauses and subclauses of each group;
The said second preservation unit also is used for each group of this user's appointment and needs the corresponding relation between the information releasing clauses and subclauses to be kept at said main split;
Said information release unit specifically is used to judge the group under this contact person, need be synchronized in the user branch that sets up into this contact person to this group contact person information releasing clauses and subclauses.
Preferably, also comprise:
Tip element; Be used for upgrading when main split's data; Perhaps the user's branch data with certain contact person clashes, when perhaps the data of the modification carried out in off-line state of certain contact person and main split clash, with taking place to upgrade or the data entries of conflict is prompted to this contact person.
Preferably, also comprise:
First data provide the unit, are used for when user's branch data of main split's data and certain contact person clashes, and provide the data of main split and user branch to supply this contact person to select;
The first status modifier unit is used for confirming according to the result that this contact person selects the final result of user's branch data.
Preferably, also comprise:
Second data provide the unit; When the modification that is used for carrying out in off-line state as certain contact person and the data of user branch clash; Judge whether main split's data exist with user's branch data and conflict; If exist, provide the amended data of this contact person, main split's data and user's branch data to supply this contact person to select; Otherwise, provide the data of amended data of this contact person and user branch to supply this contact person to select;
The second status modifier unit is used for confirming according to the result that this contact person selects the final result of user's branch data.
Preferably, also comprise:
Map unit; Use the international identification code MSISDN of travelling carriage login system if be used for the user; Then this MSISDN is mapped to the unique virtual number of the account of an overall situation; And said virtual number of the account offered this user's contact person, preserve the mapping relations between this virtual number of the account and this user's the personal information;
Main split's updating block is used for when the user changes MSISDN, receives to make amendment and information releasing after the user uses former MSISDN login, upgrades this user's in the main split MSISDN information;
Lock unit, when being used to receive certain contact person and obtaining the request of the current MSISDN information of this user through said virtual number of the account, with amended MSISDN information synchronization in the main split in this contact person's user branch.
According to specific embodiment provided by the invention, the invention discloses following technique effect:
First; The present invention can make a distinction the storage and the issue of personal information, therefore, does not want to issue if some information are users; Just can only in private branch, store; To need the information releasing clauses and subclauses to be stored in the main split simultaneously, when satisfying the demand that releases news, can also the user not thought that information releasing stores.In addition, when receiving certain contact person's request just with the data sync in the main split in this contact person's user branch, avoided the user to receive being reluctant updated information.
The second, the associated person information in the user branch is divided into Back ground Information, extend information and three parts of self-defined information, other information of some contact persons that the user hopes to write down can partly be described at self-defined information.
The 3rd, can allow the user that the contact person in the address list is divided into groups, and can disclosed data entries to the contact person in each group, therefore be convenient to associated person information is carried out privacy control.
The 4th, when the associated person information in the different branches clashes, can point out the data entries that clashes; Can also solve this data collision problem through the information in the multiple branch is provided.
The 5th, the user for using the cell-phone number login system can eliminate the inconvenience that brings when the user changes cell-phone number through cell-phone number and system virtualization number of the account are bound.
Description of drawings
Fig. 1 is the flow chart of the method that provides of the embodiment of the invention;
Fig. 2 is the sketch map that concerns between each branch of providing of the embodiment of the invention;
Fig. 3 is that the virtual number of the account of utilizing that the embodiment of the invention provides realizes the sketch map of cellphone changing number;
Fig. 4 is the schematic representation of apparatus that the embodiment of the invention provides.
Embodiment
For make above-mentioned purpose of the present invention, feature and advantage can be more obviously understandable, below in conjunction with accompanying drawing and embodiment the present invention done further detailed explanation.
Referring to Fig. 1, the PIM method that the embodiment of the invention provides may further comprise the steps:
S101: when receiving its personal information of user's input, set up private branch, said personal information is kept in the said private branch;
S102: when receiving the message of the said personal information of issue, set up the main split corresponding, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information with said private branch;
S103: when receive that certain contact person sends obtain this userspersonal information's request the time, the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
The embodiment of the invention is that unit organizes with the storage of user's personal information with every user; Each user's personal information is called a document; Document is made up of " key-value pair "; Wherein " key " is character string forms (like name, phone, E-mail address or the like), and " value " can be character string or binary data (i.e. " key " corresponding particular content).
Said branch is meant the copy of a personal information, the difference that allows to exist the reasons such as modification of information to produce between each copy.Between the different branches only the union operation through data influence each other, and submit to data in each branch can't influence the data of other branches.
At first; When logging in system by user and when filling in the personal information of oneself; For this user sets up a private branch at server end, be example with user A, just when user A imports the information (name of oneself, telephone number, E-mail address or the like) of oneself; For this user A sets up private branch, with the personal information storage of user A input in private branch.That is, private branch is used for the user and safeguards my information, and the external issue of information does not take place when the user upgrades personal information to this branch.Therefore, the user can be with oneself personal information storage in private branch, and does not worry that some does not think that external information releasing is published away.
When the user fills in personal information, can two kinds of selections be provided to the user, storage or issue, if the user selects storage, then direct personal information with the user is kept in the private branch.When the user selects to issue (any moment that can be after filling in personal information, and not necessarily after filling in completion, promptly select issue), server end can be set up a main split accordingly, and user's personal information is kept in the main split.That is to say that main split is used to preserve the outwards personal information of issue of user's needs.
Certainly, the user possibly only think externally to issue some clauses and subclauses in the personal information, and therefore, the user also can specify selectively can the information releasing clauses and subclauses, promptly can specify which data entries only to be used for storage, and which data entries can be published away.At this moment, still preserve all personal information of user in the private branch, these information only user are visible, and preserving in the main split can the information releasing clauses and subclauses, and the part that these data entries can personal information also can be the whole of personal information.Therefore, main split for the contact person be the equal of readable, can write, wherein, the data of write operation come from the information in the private branch, trigger when write operation can be released news by this choose of user.Certainly main split is read-only for other users beyond the user.It is thus clear that, introduce private branch and main split, can be so that the user can utilize private branch storage personal information; (can be optionally to issue) can release news again; Therefore, can storage and issue be made a distinction, be very easy to the management of user personal information.
Simultaneously; The embodiment of the invention is also set up user branch for each user who occurs user A among the contact person of address list; That is, if user A is the contact person of user B, then user B has the personal information of user A; And the personal information of user A is kept in the user branch, that is to say that user branch is used to preserve the contact person's of user B personal information.It is thus clear that owing in each user's the address list a plurality of contact persons are arranged generally, therefore, each user possibly have a plurality of user branch, is respectively applied for the personal information of preserving each contact person.For example, user A appears in the address list of user B, and promptly user A is the contact person of user B, and then the personal information of the user A of user B maintenance will be stored in the user branch.If user B need upgrade the personal information of user A, then can send request to server, after server receives request, can the information releasing clauses and subclauses be synchronized in the user branch of user B what preserve in the main split.
Wherein, the information in the user branch can be that user B imports voluntarily, promptly; Before user B obtains renewal; Possibly there are some information in the user branch, therefore, after getting access to data entries from main split; Need at first carry out the merging and the conflict of data and handle, and then give user B data passes.It is thus clear that, use user branch after, user B can preserve the own contact person's who safeguards personal information, is not needing need not to obtain renewal from main split under the synchronous situation, therefore, has avoided receiving some and oneself has been reluctant the information that receives.
It is thus clear that, for a user's personal information, can there be private branch, main split and user branch, can realize management more neatly like this to personal information, be convenient to satisfy from many aspects user's demand.
The embodiment of the invention can also solve many-sided problem on the basis of above-mentioned PIM method, at length introduce respectively below.
One, in the prior art; The user is in the personal information of filling in oneself or when writing down other people personal information, and the form that normally provides according to system is filled in, promptly; Usually key field is fixed; And in the space of key field back, insert corresponding value field (certainly, for user branch, these values also can be obtained from main split).But the user maybe be also needs outwards other information beyond the issue retainingf key field, and for example, the retainingf key field possibly have only name, mobile phone, home phone number, office telephone, and certain user possibly also need disclose information such as oneself msn address and blog address; In addition; Also having some users possibly have distich is that people's personal information is carried out self-defining demand; Promptly; Except the data entries that the contact person externally announces, the user often has the demand that associated person information is increased some self-defined clauses and subclauses, is used to describe other information of some contact persons that the user hopes to write down.For example, contact person's hobby, pet name or the like.
For this reason, the embodiment of the invention can be divided into the personal information in the private branch Back ground Information and extend information two parts, if the user is when filling in the personal information of oneself; Wherein, The key field of Back ground Information is fixed (being that system is given), embodies the most basic information of contact person, for example phone number, E-mail address, address etc.; These information are the common information of most contact persons, and generally all can be stored in the main split.Because key field fixes, thereby can merge the renewal to Back ground Information, and can find the conflict in the renewal, so Back ground Information is the data of participation multi-user collaborative in the address list through field is corresponding one by one from contact person and user.
Extend information is the individual additional information that the coupling family provides, for example, and blog address, game role name or the like.Extend information is submitted to only for the user, and its key-value pair is self-defined by the contact person.Thus it is clear that,, can make the user outwards to issue extra information and no longer be confined to Back ground Information through extend information.
Simultaneously, can contact person's personal information of preserving in the user branch be divided into three parts of Back ground Information self-defined information, the respective document data of storage are also by this division.Wherein, the key field of Back ground Information is fixed equally, and self-defined information is the extra side information that has user's interpolation of this associated person information, and its key-value pair is by User Defined.Thus it is clear that,, can make the user can write down some extraneous informations of contact person, and no longer be confined to Back ground Information, perhaps contact person's information releasing through self-defined information.
It is thus clear that Back ground Information and extend information can be kept in the private branch,, also can be kept in the main split if when the user needs outwards issue.But extend information can't actual storage and user branch, and can only from main split, obtain; And self-defined information only exist with user branch in.Certainly, the extend information that the user fills in might have identical part with the self-defined information that other artificial these users fill in, but this does not influence the realization of the embodiment of the invention.
Two, in the practical application, because everyone role in society is different, therefore, for the contact person of difference relation, the data entries that can announce may be different.For example, if certain contact person is the classmate of user A, then user A may announce comparatively detailed information such as its telephone number, address, blog address to this contact person; And if certain contact person is the play fellow of user A, then user A maybe only need be to its open own game role name, and other information all are privacies for this contact person, do not want it is disclosed.Therefore, the user possibly need which kind of information of control to be obtained by the contact person of which kind of relation when externally issuing contact details, promptly need consider the demand of privacy of user aspect.
For this reason, the embodiment of the invention can also allow the user that the contact person in the address list is divided into groups, and a contact person can belong to a plurality of groups.Grouping can embody the social relationships between All Contacts and the user, thereby can be as the authority granularity of privacy control, and each key-value pair can be related to arriving one or more groups.Userspersonal information's issue is the minimal data granularity with the key-value pair, and on the basis of this granularity, the user can freely determine the externally privacy policy of issue of different information, thereby reaches the maximization of flexibility.For example; Can increase the control of authority option in the back of each key-value pair, comprise the title of each group in the option, after the user has filled in a data entries; Which can in option, select to disclose this information to the contact person of group; Certainly, if the user does not make a choice, can be defaulted as this information can be open to whole contact persons.
Incidence relation between key-value pair and each group can be kept in the main split, promptly when key-value pair is published to main split as data entries, will preserve the authority information of each data entries simultaneously.When receive certain contact person obtain information request the time, can judge at first that this contact person belongs to that group, can be synchronized to this contact person's user branch then to the disclosed data entries of this group.Thereby guaranteed that only the contact person in having the group of access rights can obtain corresponding information bar destination data, played the effect of protection privacy of user effectively.
Three, the preamble merging of mentioning data with conflict, wherein, said data merge and are meant the merging of the data of two branches being carried out data according to the corresponding relation of each information canopy of the heavens.For example user branch and main split all have " Email " this data entries; After the last the merging; Address in two branches in the Email is user163.com, and main split takes place to upgrade and makes the address of Email become newuser163.com afterwards, at this moment; If the data of main split are merged to user branch, then the address of Email will become newuser163.com in the user branch.
Said conflict is meant that when merging the information of different branches, if all there is new renewal in the last each branch of back that merges, and the data updated content is inconsistent, then produces conflict.For example; All has " Email " this data entries in user branch and the main split; After the last the merging, the address in two branches in the Email is user163.com, and main split takes place to upgrade and makes the address of Email become newuser163.com afterwards; User branch has also taken place to upgrade and has made the address of Email become user126.com; At this moment, if main split is merged to user branch, thus then can be owing to renewal and the inconsistent generation conflict of data have all taken place in two branches.
The embodiment of the invention has also taken into full account the data collision problem, and the timely data that clash of user can be pointed out the data that clash on client end interface for ease, and concrete way can be:
When the information in address book clauses and subclauses exist renewal or conflict, can indicate at client end interface and upgrade or conflict situation.For example; Address list master interface is the tabulation of being made up of name of contact person; The background of each clauses and subclauses adopts color to indicate the state of this name corresponding contact information: when main split's data and user's branch data exist when conflict, use color to indicate the clauses and subclauses that generation conflicts at client end interface.The associated person information interface is the tabulation of being made up of the key-value pair clauses and subclauses, and the background of each clauses and subclauses adopts color to indicate the update inconsistency state of these clauses and subclauses.
Possesses the client (for example cell phone software etc.) of local storage capacity for some; On data mode, there is local this state of revising with respect to the client of no storage capacity (for example browser etc.); Be that the user can the personal information to the contact person make amendment under off-line state, and be kept at this locality.When the renewal existence of this locality modification and user branch conflicts, can indicate (using color etc.) equally at client end interface and produce the clauses and subclauses of conflict.That is to say; Revise when this locality takes place data for the client that possesses local storage capacity; And the user branch of far-end just exist simultaneously when upgrading can unlabeled data renewal, conflict situation; Certainly, as long as user branch and the renewal of main split do not exist and conflict then that local data is always up-to-date, there are not renewal or modification state for the client of no local storage capacity.
In addition; The embodiment of the invention also provides the solution of data collision problem; The user submits to data all to follow the first rule of afterwards submitting to of upgrading to private branch or user branch, and the user is first from long-range acquisition latest data, and solves contingent conflict; Guarantee to submit to before the data based on data are up-to-date versions, thereby guarantee that the data modification of submitting to the back to take place is the modification of user expectation.During concrete the realization, can be in the following manner:
When main split's data and user's branch data exist when conflicting, to the data that the user provides user branch and main split, select to use the final result of the data of one of them branch voluntarily as user branch by the user in client.Main split produces the reason of conflicting with user branch and comes from; The user has safeguarded contact person's Back ground Information voluntarily; And Back ground Information is committed to user branch preserves, and after this contact person has been published to main split with the modification of personal information and this modification is inconsistent to data with the corresponding key assignments in the user branch.When the user when user branch to upgrade; Need to merge earlier the modification of main split and user branch; As clash, then inform that through client end interface data collision takes place the user, and provide the data of user branch and main split to select finally to use which piece of data simultaneously by the user.
Same; For the client that possesses local storage capacity; When the renewal existence of this locality modification and user branch conflicts; To the user data of local data, user branch, three branches of main split are provided in client, select to use a copy of it data as final result and be reflected to user branch voluntarily by the user.Because client possesses storage capacity, so the user can revise data in client off-line, and is kept at client terminal local, thereby makes the client terminal local data become the modification state.When the user need carry out when user branch to upgrade and the local merging of revising, revise to exist inconsistently then clashing with Updating Information of obtaining when this locality, can inform that data collision takes place the user this moment through client end interface.
When solving this data collision; Need consider also whether user branch exists with main split and conflict, when user branch and main split do not exist when conflicting, can provide the local data of revising with user branch to supply the user to select; When user branch and main split also exist when conflicting; Then can local modification, user branch, main split's three piece of data be provided, select finally to use which piece of data by the user, and user's selection result is saved in the user branch to the user.
In order to understand the PIM method that the embodiment of the invention provides better, introduce through concrete example below.
Referring to Fig. 2, the figure shows the data format of the document of preserving in each branch, and the relation between each branch.As can be seen from the figure, the method that provides of the embodiment of the invention comprises following content:
1) personal information with oneself after user A logins is kept in the private branch, and private branch comprises a document data, and content is:
Name: A
Cell-phone number: 13900571987
Home phone number: 87876532
Office telephone: 87861322
Email：usera163.com
Address: XXX sub-district 1-1-1
Birthday: 1980-1-1
MSN number: useramsn.com
Blog address: usera.blog.163.com
2) user A issues personal information, and system sets up main split, can the information releasing clauses and subclauses be kept in the main split, and in this example, its information is identical with information in the private branch, and user A all issues the information that it is kept in the private branch.
3) have A in the contacts list of user B, thereby B creates out user branch with the information preservation of contact person A, its content is:
Name: A
Cell-phone number: 13900571987
Home phone number:
E-mail address: usera163.com
These contents have user B oneself editor.
4) user B obtains renewal from main split, and system carries out the information of A in the information of user A in the user branch and the main split related, thereby user branch content alteration is:
Name: A
Cell-phone number: 13900571987
Home phone number: 87876532
Office telephone: 87861322
Email：usera163.com
Address: XXX sub-district 1-1-1
Birthday: 1980-1-1
MSN number: useramsn.com
Blog address: usera.blog.163.com
User B need write down the more information about user A, in the user branch of user B, can comprise with the lower part:
1) Back ground Information of user A:
Name: A
Cell-phone number: 13900571987
Home phone number: 87876532
Office telephone: 87861322
Email：usera163.com
Address: XXX sub-district 1-1-1
Birthday: 1980-1-1
Back ground Information is present in each branch.That is, these information all exist in private branch, main split and user branch.
2) extend information of user A:
MSN number: useramsn.com
Blog address: usera.blog.163.com
The extend information that in each branch, is provided with only contact person can be write, and extend information exists only in main split and the private branch, and promptly these extend informations are the extra issues of contact person, only from main split's mapping, and unactual being stored in the user branch.
3) user B be user A more self-defined information:
Girl friend: willow six
Warcraft ID:moon
The pet name: mj
This self-defined information is that user B oneself adds, and therefore exists only in the user branch.
In order to carry out privacy control, can may further comprise the steps:
1) have contact person B, C, D in the contacts list of user A, wherein B, C belong to good friend's grouping of A;
2) user A is associated with good friend's grouping with the authority of home phone number, and other data entries are visible to everyone for what give tacit consent to;
3) user A selects the issue home phone number to main split, simultaneously the packet associated relation is updated to main split;
4) user B obtains renewal from main split, divide into groups because B belongs to the good friend, so B obtains the home phone number information of A.
5) user D asks lastest imformation to main split, and owing to D does not divide into groups the good friend, so D can't obtain the renewal of home phone number.
When Data Update or conflict take place, can the background that the updated information clauses and subclauses take place be denoted as blueness, the data entries that clashes is denoted as redness, concrete, can point out according to following method:
1) user B login system, the information of finding contact person A exist to be upgraded and not to have a conflict, then in the address list client end interface, the entry background of contact person A is made as blueness;
2) upgrade and when clashing when the information of finding contact person A exists, the background with the entry of contact person A in the address list client end interface is made as redness;
3) the associated person information interface of entering contact person A, the E-mail address conflict, the background of these clauses and subclauses is shown in red;
4) information of home phone number exist to upgrade then that the background of these clauses and subclauses is shown as blueness.
Suppose that user B has upgraded the E-mail address information of A through client, becomes us era126.com from original us era163.com; User A has issued E-mail address information to main split, becomes newusera163.com from original usera163.com; User B obtains renewal from system, and E-mail address usera126.com and the newusera163.com in the main split that take place in the user branch this moment clash, and when solving this data collision problem, concrete way is following:
1) return this conflicting information through client to user B, to B provide from the usera126.com of user branch with select from newusera163.com two piece of data of main split;
2) if B selects newusera163.com as final data, user branch recovers consistent with main split so;
3) if B selects usera126.com as final data, relative main split of user branch becomes the modification state so, and no longer is conflict situation.
In addition, suppose that user C uses the client maintenance address list on mobile phone, C has revised user A under off-line state E-mail address is usera188.com; User C connection is attend system and is obtained renewal, and the idea email address usera126.com that takes place this moment in the main split revises conflicting of usera188.com with this locality of user C, and for solving this data collision problem, concrete way is following:
1) to user C the usera188.com from this locality is provided through client, and this two piece of data of usera126.com of main split;
2) if C selects the usera126.com of main split as final data (E-mail address in the user branch is revised as usera126.com), this locality, user branch, main split get back to consistent state once more;
3), think local in system so, user branch is consistent and become the modification state with respect to main split, and no longer be conflict situation if C selects local usera188.com as final data (E-mail address in the user branch is revised as usera188.com).
In addition, also have such a case: some user use always the international identification code of travelling carriage (The Mobile Station ISDN number, MSISDN) login system (wherein; For this portable terminal of mobile phone, said MSISDN is the cell-phone number of saying usually, for convenience's sake; All be that example is described below) with the cell-phone number; In case but the user changes cell-phone number, can't normally sign in to system through cell-phone number, more can't get access to the information in each branch.For this reason, the embodiment of the invention has also provided corresponding solution, and is specific as follows:
If the user uses the cell-phone number login system all the time, then in system, cell-phone number is mapped to a virtual number of the account that the overall situation is unique.Virtual number of the account is transparent fully for the user, and no matter the user is to activate new number of the account with cell-phone number, or login system all only needs to use cell-phone number.Virtual number of the account produces when activating new number of the account, and binds with the cell-phone number that activates usefulness, and after this data file in each branch all can obtain through virtual number of the account retrieval in the system.
Like this; When cellphone changing number takes place in the user; The user can use former phone number login system, and upgrades the phone number in the Back ground Information, to main split's issue new digit information; This user's contact person still can find this user's information through this user's corresponding virtual number of the account, and obtains new phone number.
The sketch map that utilizes virtual number of the account to realize cellphone changing number has been shown among Fig. 3.As can be seen from the figure, concrete implementation method can comprise following content:
1) cell-phone number of supposing user A is 13900571987, and activates to system with this cell-phone number, and system is that it binds a virtual number of the account abcd1234567;
2) user B and A contact person each other in address list separately find the virtual number of the account of A after the B login system through the A cell-phone number, and system is the virtual number of the account of user B record contact person A and the mapping relations between contact person A information;
3) to have changed cell-phone number be 13800123456 to user A, and be the number of the account login system with former cell-phone number, upgrades its cell-phone number information, and information is published to main split;
4) user B signs in to system, and obtains the up-to-date information of user A according to the virtual number of the account of user A to system, and user B obtains the up-to-date cell-phone number information of user A from main split, accomplishes the renewal of associated person information.
Corresponding with the PIM method that the embodiment of the invention provides, the embodiment of the invention also provides a kind of personal information management device, and referring to Fig. 4, this device comprises with lower unit:
The first preservation unit U401 when being used to receive its personal information of user's input, sets up private branch, and said personal information is kept in the said private branch;
The second preservation unit U402 is used for when receiving the message of the said personal information of issue, setting up the main split corresponding with said private branch, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information;
Information release unit U403, be used for when receive that certain contact person sends obtain this userspersonal information's request the time, the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
During its personal information of user input, the first preservation unit U401 sets up private branch for this user's personal information, and said personal information is kept in the said private branch; If the user need issue its personal information; Then can send the issue request to system; When receiving the message of the said personal information of issue; The second preservation unit U402 sets up the main split corresponding with said private branch, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information; Data entries in the main split can be a full detail or the part in the private branch, and the user can select according to concrete needs.The information releasing clauses and subclauses that need that are kept in the main split can't send to this user's contact person immediately; But when receive that certain contact person sends obtain this userspersonal information's request the time, by information release unit U403 the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
In order to satisfy the demand that the user issues more information or writes down contact person's more information; The embodiment of the invention can be divided into the information in the private branch Back ground Information and extend information; Wherein the key field of Back ground Information is fixed, and value field can be filled in by the user accordingly; The key-value pair of extend information is by User Defined.The user can issue other information except that Back ground Information like this.
Simultaneously, can also the information in the user branch be divided into Back ground Information and self-defined information, Back ground Information is that key field is fixed equally, and value field can be filled in by the user accordingly; The key-value pair of self-defined information is by User Defined.The user can write down other any information the information that the contact person gets access to except that Back ground Information and from main split like this.
For the ease of the control of authority to the userspersonal information, this device can also comprise:
Authority information receiving element U404 is used to receive the grouping information of user to contact person in the address list, and user's appointment need be to contact person's information releasing clauses and subclauses of each group;
At this moment, the second preservation unit U402 also is used for each group of this user's appointment and needs the corresponding relation between the information releasing clauses and subclauses to be kept at said main split;
Information release unit U403 specifically is used to judge the group under this contact person, need be synchronized in the user branch that sets up into this contact person to this group contact person information releasing clauses and subclauses.
When the data of each branch clash, find this conflict and processing in time for the ease of the guiding user, this device can also comprise:
Tip element U405; Be used for upgrading when main split's data; Perhaps the user's branch data with certain contact person clashes, when perhaps the data of the modification carried out in off-line state of certain contact person and main split clash, with taking place to upgrade or the data entries of conflict is prompted to this contact person.
In addition, this embodiment of the invention can also help the user to solve the data collision problem, and at this moment, this device also comprises:
First data provide unit U406, are used for when user's branch data of main split's data and certain contact person clashes, and provide the data of main split and user branch to supply this contact person to select;
The first status modifier unit U406 is used for the state according to the results modification data of this contact person's selection.
Possesses the client of local storage capacity for some; The user can make amendment to data in off-line state, and these data will be kept at client terminal local, and can not preserve with the described arbitrary branch of the embodiment of the invention in; But; This modification also possibly cause the conflict of data, and the embodiment of the invention has also proposed solution to this, and this device also comprises:
Second data provide unit U407; When the modification that is used for carrying out in off-line state as certain contact person and the data of main split clash; Judge whether main split's data exist with user's branch data and conflict; If exist, provide the amended data of this contact person, main split's data and user's branch data to supply this contact person to select; Otherwise, provide the data of amended data of this contact person and user branch to supply this contact person to select;
The second status modifier unit U408 is used for the state according to the results modification data of this contact person's selection.
In practical application, some user can directly use cell-phone number to come login system, and in order to solve the problem that exists when this user changes cell-phone number, this device can also comprise:
Map unit U409; Use the cell-phone number login system if be used for the user; Then this cell-phone number is mapped to the unique virtual number of the account of an overall situation, and said virtual number of the account is offered this user's contact person, preserve the mapping relations between this virtual number of the account and this user's the personal information;
The updating block U410 of main split is used for when the user changes cell-phone number, receives to make amendment and information releasing after the user uses former cell-phone number login, upgrades this user's in the main split cell-phone number information;
Lock unit U411, when being used to receive certain contact person and obtaining the request of this user's current phone information through said virtual number of the account, with amended cell-phone number information synchronization in the main split in this contact person's user branch.
More than to a kind of PIM method provided by the present invention and device; Carried out detailed introduction; Used concrete example among this paper principle of the present invention and execution mode are set forth, the explanation of above embodiment just is used for helping to understand method of the present invention and core concept thereof; Simultaneously, for one of ordinary skill in the art, according to thought of the present invention, part all can change on embodiment and range of application.In sum, this description should not be construed as limitation of the present invention.
Claims (14)
1. a PIM method is characterized in that, comprising:
When receiving its personal information of user's input, set up private branch, said personal information is kept in the said private branch;
When receiving the message of the said personal information of issue, set up the main split corresponding, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information with said private branch;
When receive that certain contact person sends obtain this userspersonal information's request the time, the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
2. method according to claim 1 is characterized in that, comprises the Back ground Information that key field is fixing in the said private branch, and key-value pair is by user-defined extend information;
Comprise the Back ground Information that key field is fixing in the said user branch, and key-value pair is by the self-defining self-defined information of contact person.
3. method according to claim 1 is characterized in that, also comprises:
Receive the grouping information of user to contact person in the address list, and user's appointment need be to contact person's information releasing clauses and subclauses of each group;
Also comprise when needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information:
With each group of this user's appointment and need the corresponding relation between the information releasing clauses and subclauses to be kept in the said main split;
With comprising in the said user branch that needs the information releasing clauses and subclauses to be synchronized to and to set up for this contact person:
Judge the group that this contact person is affiliated, need be synchronized in the user branch that sets up into this contact person to this group contact person information releasing clauses and subclauses.
4. method according to claim 1 is characterized in that, also comprises:
Data are upgraded when main split, and perhaps the user's branch data with certain contact person clashes, when perhaps the data of the modification carried out in off-line state of certain contact person and main split clash, with taking place to upgrade or the data entries of conflict is prompted to this contact person.
5. method according to claim 1 is characterized in that, also comprises:
When user's branch data of main split's data and certain contact person clashes, provide the data of main split and user branch to supply this contact person to select;
Confirm the final result of user's branch data according to the result of this contact person's selection.
6. method according to claim 1 is characterized in that, also comprises:
When the modification of carrying out in off-line state as certain contact person and the data of user branch clash; Judge whether main split's data exist with user's branch data and conflict; If exist, provide the amended data of this contact person, main split's data and user's branch data to supply this contact person to select; Otherwise, provide the data of amended data of this contact person and user branch to supply this contact person to select;
Confirm the final result of user's branch data according to the result of this contact person's selection.
7. method according to claim 1 is characterized in that, also comprises:
If the user uses the international identification code MSISDN of travelling carriage login system; Then this MSISDN is mapped to the unique virtual number of the account of an overall situation; And said virtual number of the account offered this user's contact person, preserve the mapping relations between this virtual number of the account and this user's the personal information;
When the user changes MSISDN, receive and make amendment and information releasing after the user uses former MSISDN login, upgrade this user's in the main split MSISDN information;
Receive certain contact person when obtaining the request of the current MSISDN information of this user through said virtual number of the account, with amended MSISDN information synchronization in the main split in this contact person's user branch.
8. a personal information management device is characterized in that, comprising:
Private branch when being used to receive its personal information of user's input, is set up in the first preservation unit, and said personal information is kept in the said private branch;
The second preservation unit is used for when receiving the message of the said personal information of issue, setting up the main split corresponding with said private branch, with needing the information releasing clauses and subclauses to be kept in the said main split in the said personal information;
The information release unit, be used for when receive that certain contact person sends obtain this userspersonal information's request the time, the information releasing clauses and subclauses that need of preserving in the said main split are synchronized in the user branch that sets up into this contact person.
9. device according to claim 8 is characterized in that, comprises the Back ground Information that key field is fixing in the said private branch, and key-value pair is by user-defined extend information;
Comprise the Back ground Information that key field is fixing in the said user branch, and key-value pair is by the self-defining self-defined information of contact person.
10. device according to claim 8 is characterized in that, also comprises:
The authority information receiving element is used to receive the grouping information of user to contact person in the address list, and user's appointment need be to contact person's information releasing clauses and subclauses of each group;
The said second preservation unit also is used for each group of this user's appointment and needs the corresponding relation between the information releasing clauses and subclauses to be kept at said main split;
Said information release unit specifically is used to judge the group under this contact person, need be synchronized in the user branch that sets up into this contact person to this group contact person information releasing clauses and subclauses.
11. device according to claim 8 is characterized in that, also comprises:
Tip element; Be used for upgrading when main split's data; Perhaps the user's branch data with certain contact person clashes, when perhaps the data of the modification carried out in off-line state of certain contact person and main split clash, with taking place to upgrade or the data entries of conflict is prompted to this contact person.
12. device according to claim 8 is characterized in that, also comprises:
First data provide the unit, are used for when user's branch data of main split's data and certain contact person clashes, and provide the data of main split and user branch to supply this contact person to select;
The first status modifier unit is used for confirming according to the result that this contact person selects the final result of user's branch data.
13. device according to claim 8 is characterized in that, also comprises:
Second data provide the unit; When the modification that is used for carrying out in off-line state as certain contact person and the data of user branch clash; Judge whether main split's data exist with user's branch data and conflict; If exist, provide the amended data of this contact person, main split's data and user's branch data to supply this contact person to select; Otherwise, provide the data of amended data of this contact person and user branch to supply this contact person to select;
The second status modifier unit is used for confirming according to the result that this contact person selects the final result of user's branch data.
14. device according to claim 8 is characterized in that, also comprises:
Map unit; Use the international identification code MSISDN of travelling carriage login system if be used for the user; Then this MSISDN is mapped to the unique virtual number of the account of an overall situation; And said virtual number of the account offered this user's contact person, preserve the mapping relations between this virtual number of the account and this user's the personal information;
Main split's updating block is used for when the user changes MSISDN, receives to make amendment and information releasing after the user uses former MSISDN login, upgrades this user's in the main split MSISDN information;
Lock unit, when being used to receive certain contact person and obtaining the request of the current MSISDN information of this user through said virtual number of the account, with amended MSISDN information synchronization in the main split in this contact person's user branch.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101323502A CN101527896B (en) | 2009-03-30 | 2009-03-30 | Personal information management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101323502A CN101527896B (en) | 2009-03-30 | 2009-03-30 | Personal information management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101527896A CN101527896A (en) | 2009-09-09 |
| CN101527896B true CN101527896B (en) | 2012-02-29 |
Family
ID=41095545
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101323502A Active CN101527896B (en) | 2009-03-30 | 2009-03-30 | Personal information management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101527896B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101729672B (en) * | 2009-11-10 | 2013-01-16 | 中兴通讯股份有限公司 | Management method and system of multifunction mobile equipment |
| CN102469036A (en) * | 2010-11-02 | 2012-05-23 | 腾讯科技（深圳）有限公司 | Method and device for processing user information |
| CN102360461A (en) * | 2011-09-23 | 2012-02-22 | 纽海信息技术（上海）有限公司 | Personal address management system and method thereof |
| CN107071080B (en) * | 2011-10-20 | 2020-11-17 | 华为技术有限公司 | Method and system for maintaining contact information |
| KR101832394B1 (en) * | 2013-04-10 | 2018-02-26 | 삼성전자주식회사 | Terminal apparatus, server and contol method thereof |
| CN104270728A (en) * | 2014-09-16 | 2015-01-07 | 小米科技有限责任公司 | Information integration method and device |
| CN105872178A (en) * | 2016-06-06 | 2016-08-17 | 北京珠穆朗玛移动通信有限公司 | Contact person information sharing method and mobile terminal |
| CN106506511B (en) * | 2016-11-17 | 2019-08-23 | 京东方科技集团股份有限公司 | A kind of address list information processing method, device |
| US11165634B2 (en) * | 2018-04-02 | 2021-11-02 | Oracle International Corporation | Data replication conflict detection and resolution for a multi-tenant identity cloud service |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1558342A (en) * | 2004-01-16 | 2004-12-29 | 旭 张 | Method for realizing synchronous update of address book information utilizing public information network |
| CN101068156A (en) * | 2006-12-20 | 2007-11-07 | 腾讯科技（深圳）有限公司 | Conflict processing method and conflict processing server when data synchronization |
| CN101150629A (en) * | 2007-10-22 | 2008-03-26 | 孙国仲 | Contact book management system and method |
-
2009
- 2009-03-30 CN CN2009101323502A patent/CN101527896B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1558342A (en) * | 2004-01-16 | 2004-12-29 | 旭 张 | Method for realizing synchronous update of address book information utilizing public information network |
| CN101068156A (en) * | 2006-12-20 | 2007-11-07 | 腾讯科技（深圳）有限公司 | Conflict processing method and conflict processing server when data synchronization |
| CN101150629A (en) * | 2007-10-22 | 2008-03-26 | 孙国仲 | Contact book management system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101527896A (en) | 2009-09-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101527896B (en) | Personal information management method and device | |
| CN101645926B (en) | Operating method of mobile SNS communication system based on address book of mobile phone | |
| CN100334583C (en) | Smart card enabled mobile personal computing environment system | |
| US8719222B2 (en) | Synchronization and collaboration within peer-to-peer and client/server environments | |
| CN101080056B (en) | A management method and system of network browser collection folder of mobile terminal | |
| US8595380B2 (en) | Message bus based replication | |
| CN102279948A (en) | Contact information merger and duplicate resolution | |
| CN102088519A (en) | Address book management method and device | |
| CN104937906B (en) | Method for being communicated between multiple users with communication terminal via virtual communication space | |
| CN102769640B (en) | The update method of user profile, server and system | |
| CN104092770A (en) | Inner-enterprise address book management method and system based on cloud computing | |
| CN108563771B (en) | Block chain-based large file management system and method | |
| JP2008287407A (en) | Content distribution device and content distribution method | |
| CN101802808A (en) | Accessing device-hosted services from scripting and other programming environments | |
| CN103119911A (en) | System and method for synchronizing the profile of a user in social networks and the user's personal contact card (PCC) | |
| CN102833180A (en) | Method and system for sharing microblog messages | |
| CN101978353A (en) | Portable information terminal, character delivery method, and temporary character saving program product | |
| CN109871210A (en) | Web page element amending method, device, equipment and storage medium | |
| CN101861578A (en) | Network operating system | |
| CN105407044B (en) | A kind of implementation method of the cloud storage gateway system based on NFS | |
| CN112394932A (en) | Automatic browser webpage skin changing method and device | |
| CN102186163A (en) | Data synchronizing method of multi-account address book of smart phone | |
| CN104731833A (en) | Web layout method and device | |
| CN103078782A (en) | Friend note recommendation note implementation method and system | |
| CN101861576A (en) | Network operating system |
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 |