Background technology
Personal information management (Personal Information Management, being called for short PIM) business is meant that the client is consistent the information in the portable terminal (address list, schedule etc.) with wireless or wired mode and computer or mobile network's server, and can inquire about and the business of management information with multiple terminal, multiple access means.
The content of PIM is address list, schedule, memo pad or the like normally.The PIM management of mobile phone users in the past is based on this machine or PC and the irrelevant behavior of network, continuous growth along with the rate of changing planes of portable terminal, being necessary provides PIM operation system in mobile network's side, the end user can backup on the server of network side by the pim data of air traffic channel with oneself, or obtain the PIM information synchronization to portable terminal from the server of network side, finally reach the synchronous purpose of personal information of portable terminal, the webserver and PC.
The user can use the PIM service by multiple connected mode WEB/WAP, the personal information of leading subscriber, and can realize the consistency of portable terminal, personal computer and mobile network's personal information.The up-downgoing that realizes individual card information unified mutually between portable terminal and PC, the mobile network, schedule is synchronous.The user can realize that by PC the PIM operation system of visiting the mobile network based on the WEB mode realizes self-data management.
The technology that also has a kind of information interaction in the prior art, i.e. mobile community.By mobile community, the user is the restriction of spanning network, place, time really, carries out interaction whenever and wherever possible.Mobile community comprises a plurality of sub-communities, for example, and various blog community, instant messaging community, game community, friend-making community or the like.In mobile community, the user need register the personal information information of oneself, comprises company, post, contact method or the like.Mobile platform is provided unique number for the user is unified, promptly Digital ID (calling digital ID in the following text) is used for authentication identification mobile subscriber, and the user can have identical or different user name in each sub-community.A phone number can only be bound a digital ID, and forms mapping relations by digital ID and user in the user name of each sub-community.
Appearance along with mobile community, user's the digital id information and the clauses and subclauses of community users name have been added in the PIM address list, be illustrated in figure 1 as a kind of PIM information representation intention, index key is user's digital ID and a Mobile Directory Number, and contact details also are included in the user name of each sub-community except comprising information such as common name, company, phone.In existing another kind of PIM information table, Vcard essential information with the user, the information such as name, company, phone that is the user is as the first collection information, and will provide the access entrance of second-level message in the PIM information table in the extend informations such as user name of each sub-community as second-level message.
For the convenience of using, the subscriber's meter of mobile community also adopts identical setting with PIM address list information table, and information such as the sub-community-specific information such as the pet name, buddy list of user in each sub-community only is stored in the sub-community service server.Shown in Fig. 2 a and Fig. 2 b, be respectively the subscriber's meter schematic diagram of game community and blog community, be index key with sub-community users name and digital ID, it stores the specific information in the sub-community down.
Though existing P IM is professional and mobile community manages for the userspersonal information and the intercommunication of information provides great convenience, but still have some defectives: when the user in the PIM address list, added the digital ID of contact person's mobile community, after the information such as community users name, the user wishes and can also become the good friend with this contact person in mobile community very much, but, in the prior art, the not intercommunication on business of PIM service system and mobile community service system, the user still needs to log on again good friend's management of mobile community, carry out manual interpolation and handle, cause the inconvenience of use.
Embodiment
As shown in Figure 3,, comprise the terminal A that user A uses, the terminal B that user B uses, PIM operation system, and mobile community operation system for using operation system schematic diagram of the present invention.Terminal can be portable terminal or fixed terminal, as terminal equipments such as PC, when terminal is portable terminal, can communicate by letter with PIM operation system and mobile community operation system by mobile communications network, when terminal is fixed terminal, can communicate by letter with PIM operation system and mobile community operation system by the Internet.PIM operation system and mobile community operation system are by network interconnection.This mobile community operation system can be blog community, instant messaging community, game community, arbitrary sub-community operation systems such as friend-making community.
User B is the contact person of user A, when user B is the user of a certain sub-community, if user A has inputed the user name of user B in community in address list, then the PIM client of terminal can be provided with correlated identities for user B, and display reminding user A is added to user B the corresponding sub-good friend's of community information.User A can realize user B is added to the sub-good friend of community directly by selecting this prompt options.
As shown in Figure 4, be friendly-synchronizing management method for network community flow chart of the present invention, terminal detect prompt options selected after, carry out following steps:
Step 1, terminal A send to the PIM operation system and add good friend's request message; The user totem information of the user B that carries the user totem information of terminal A in this interpolation good friend request message and will add; User totem information can be digital ID or sub-community users name.
Step 2, PIM operation system are transmitted to the mobile community operation system and are added good friend's request message.
Step 3, mobile community operation system are added user B in the buddy list of user A according to the user totem information of terminal A and the user totem information of user B, change message to PIM operation system return information, and return interpolation good friend processing of request result to terminal A.
In some cases, user terminal may not preserved address list information, for example, the user is using a new portable terminal, and user's use for convenience provides the option that adds the good friend by PIM in sub-community, after this option is selected, trigger the flow process of adding the good friend by PIM.As shown in Figure 5, be friendly-synchronizing management method for network community embodiment one flow chart of the present invention, comprise:
Step 101, terminal A land the mobile community operation system by WAP or WEB mode, detect by the PIM operation system add good friend's the option of request message selected after, send the request message that adds the good friend by the PIM operation system to this mobile community operation system; Carry the user totem information of terminal A in this request message; User totem information can be digital ID or sub-community users name.
Step 102, mobile community operation system are transmitted this adds the good friend by the PIM operation system request message to the PIM operation system.
Step 103, PIM operation system send address book data according to the user totem information of terminal A to terminal A; After terminal A receives address book data, be shown to the user, select the good friend who adds for the user.
Step 104, terminal A send to the PIM operation system and add good friend's request message; The user totem information of the user B that carries the user totem information of terminal A in this interpolation good friend request message and will add.
Step 105, PIM operation system are transmitted to the mobile community operation system and are added good friend's request message.
Step 106, mobile community operation system are added user B in the buddy list of user A according to the user totem information of terminal A and the user totem information of user B, change message to PIM operation system return information, and return interpolation good friend processing of request result to terminal A.
Before adding the good friend, the mobile community service system can inquire whether user B agrees that user A is added to the good friend with it, under the situation that user B agrees, adds operation again, if disagree with, then returns the prompt for successful information of not adding to user A.As shown in Figure 6, be friendly-synchronizing management method for network community embodiment two flow charts of the present invention:
Step 201, terminal A send to the PIM operation system and add good friend's request message; The user totem information of the user B that carries the user totem information of terminal A in this interpolation good friend request message and will add; User totem information can be digital ID or sub-community users name.
Step 202, PIM operation system are transmitted to the mobile community operation system and are added good friend's request message.
Step 203, mobile community operation system send interpolation good friend prompting message according to the user totem information of user B to terminal B.
Whether step 204, mobile community operation system receive the interpolation good friend acknowledge message that terminal B returns at the appointed time, if, execution in step 205, otherwise, execution in step 206.
Step 205, mobile community operation system are added user B in the buddy list of user A according to the user totem information of terminal A and the user totem information of user B, change message to PIM operation system return information, and return interpolation good friend processing of request result to terminal A.
Step 206, mobile community operation system are returned the prompt for successful information of not adding to user A.
After user B is added to the good friend of user A, can inquire further also whether user B needs user A is added to the good friend, after user B agrees, carry out and add operation: user A is added in the buddy list of user B according to the user totem information of terminal A and the user totem information of user B.
When user A interpolation user B is the good friend, user A may not be the user of corresponding sub-community, the mobile community operation system can be according to the user totem information of terminal A, whether inquiring user A is community users, if, then can carry out follow-up interpolation good friend's operation, otherwise, this mobile community operation system sends the information that adds community to terminal A, adhere to community at user A, be after the mobile community operation system is received the adding community acknowledge message that terminal A returns, carry out the operation of adding the good friend again.
In using another kind of operation system of the present invention, the mobile community operation system comprises total service server and subservice server, as shown in Figure 7.The subscriber's meter of storing in wherein total service server is consistent with the PIM information table, with digital ID and Mobile Directory Number is index key, it is storing contact information down, comprises information such as common name, company, phone, also is included in the user name identification information of each sub-community.The sub-community users table of each subservice server is with digital ID and sub-community users index key by name, and it is the pet name and the information such as buddy list of storage user in corresponding sub-community down.In the PIM address list, provide the function choosing-item that certain user is added to all good friends of community.
As shown in Figure 8, for network good friend synchronization management method embodiment three flow charts of the present invention, comprise the steps:
Step 301, terminal A send to the PIM operation system and add good friend's request message; The user totem information of the user B that carries the user totem information of terminal A in this interpolation good friend request message and will add; User totem information can be digital ID or telephone number.
Step 302, PIM operation system are transmitted to total service server and are added good friend's request message.
Step 303, total service server add good friend's request message to the subservice server forwards.
When user totem information is telephone number,, and be sent to the subservice server with adding good friend's request message Zong service server is converted into digital ID according to the record in the subscriber's meter.
Step 304, subservice server add user B in the buddy list of user A to according to the user totem information of terminal A and the user totem information of user B.
Step 305, subservice server are to total service server return information change result;
Step 306, total service server generate information-change message and result according to the information-change result that each subservice server returns, and are sent to PIM operation system and terminal A respectively.
Each subservice server also can directly return information-change message and interpolation good friend processing of request result to PIM operation system and terminal A respectively.If but adopt this scheme, and each subservice server all will send information respectively, and traffic is than many greatly by the unified transmission of total service server.
In embodiment three, also can add inquiry user B and whether agree that user A is added to good friend's step with it, and, can allow user B select to allow it is added to the good friend of which community.Concrete steps are similar to the correlation step among the embodiment two, do not repeat them here.
Because the user of user A and the not all community of user B possibility, therefore, when total service server is asked to subservice server forwards interpolation good friend, can selectively send, dual mode can be arranged: a kind of sub-community that to be total service server added according to the user totem information inquiring user A of terminal A, and send to corresponding subservice server and to add good friend's request message; The another kind community that to be total service server added according to the user totem information inquiring user B of user B, and send to corresponding subservice server and to add good friend's request message.
Under first kind of mode, user B may not be the user of certain a little community, in this case, still can't directly user B be added to the good friend of user A.Can be before each the subservice server that adds to user A sends interpolation good friend request by total service server, judge that earlier whether user B is the user of all sub-communities of user A adding, if, then send and add good friend's solicited message to corresponding subservice server, otherwise, determine its Mobile Directory Number according to the user totem information of user B, send the information that adds corresponding sub-community to terminal B, if user B adheres to corresponding sub-community, be that total service server is received the sub-community of the adding acknowledge message that terminal B returns, then send and add good friend's request message to corresponding subservice server.The operation of judging also can be carried out by the subservice server, after the subservice server is received and is added good friend's request, judge whether user B is the user of sub-community, if, then carry out the operation of adding the good friend, otherwise, send the information that adds corresponding sub-community according to the user totem information of user B to terminal B, after receiving the sub-community of the adding acknowledge message that second terminal is returned, carry out the operation of adding the good friend.
Under the second way, user A may not be the user of corresponding sub-community.Can be before each the subservice server that adds to user B sends interpolation good friend request by total service server, judge the user of the sub-community whether user A adds for user B, if, then send and add good friend's solicited message to corresponding subservice server, otherwise, send the information that adds corresponding sub-community to terminal A, after receiving the sub-community of the adding acknowledge message that terminal A returns, send interpolation good friend request message to corresponding subservice server.Perhaps, the subservice server is after receiving that adding the good friend asks, judge whether first user is the user of sub-community, if, carry out the operation of adding the good friend, otherwise, send the information that adds corresponding sub-community to terminal A, after receiving the sub-community of the adding acknowledge message that terminal A returns, carry out the operation of adding the good friend.
Comprise in the mobile community operation system under the situation of total service server and subservice server, also can when landing a certain sub-community, add the good friend by PIM.As shown in Figure 9, network good friend synchronization management method embodiment four flow charts for of the present invention comprise the steps:
Step 401, terminal A land the subservice server by WAP or WEB mode, and send the request message that adds the good friend by the PIM operation system to this subservice server; Carry the user totem information of terminal A in this request message; User totem information can be digital ID or sub-community users name.
Step 402, subservice server are transmitted this adds the good friend by the PIM operation system request message to the PIM operation system.
Step 403, PIM operation system send address book data according to the user totem information of terminal A to terminal A; After terminal A receives address book data, be shown to the user, select the good friend who adds for the user.
Step 404, terminal A send the request message that user B is added to all good friends of community to the PIM operation system; Carry the user totem information of terminal A and the user totem information of user B in this request message.
Step 405, PIM operation system are transmitted to total service server and are added good friend's request message.
Step 406, total service server are searched subscriber's meter according to the user ID of user B, determine the sub-community that user B is added, and send interpolation good friend request to each sub-community that user B adds;
Step 407, receive the sub-community service affair device that adds good friend's request and judge whether user A is the user of this sub-community, if execution in step 410; Otherwise, execution in step 408.
Step 408, subservice server send the information that adds corresponding sub-community to terminal A.
After whether step 409, subservice server receive the sub-community of the adding acknowledge message that terminal A returns at the appointed time, if, execution in step 410, otherwise, execution in step 411.
Step 410, subservice server add user B in the buddy list of user A to, and return the information-change result who shows interpolation good friend success, execution in step 412 to total service server.
Step 411, subservice server finish this and add good friend's operation, and return the information-change result who shows interpolation good friend failure to total service server.
Step 412, total service server generate information-change message and result according to the information-change result that each subservice server returns, and are sent to PIM operation system and terminal A respectively.
By present embodiment, the user can be added to this sub-community users the good friend of all communities when landing a certain sub-community.
Should be noted that at last: above embodiment is only in order to illustrate that technical scheme of the present invention is not intended to limit; Although with reference to preferred embodiment the present invention is had been described in detail, those of ordinary skill in the field should be appreciated that still and can make amendment or the part technical characterictic is equal to replacement the specific embodiment of the present invention; And not breaking away from the spirit of technical solution of the present invention, it all should be encompassed in the middle of the technical scheme scope that the present invention asks for protection.