WO2011150765A1 - Synchronization method of contacts information - Google Patents

Abstract

The embodiments of the present invention provide synchronization methods of contacts information. One of the synchronization methods of contacts information includes the following steps: a terminal performs synchronization of personal information of contacts with a server (101), the terminal sends a group upload request message to the server, the group upload request message includes group information of the contacts, according to which, the server performs storing in group to the stored personal information of the contacts (102).

Description

 Contact information synchronization method

The present application claims priority to Chinese Patent Application No. 201010515611.1, the entire disclosure of which is hereby incorporated by reference. TECHNICAL FIELD Embodiments of the present invention relate to communication technologies, and in particular, to a method for synchronizing contact information. Background technique

 During the communication service of the user through the terminal, the personal information of the contact can be stored in the terminal. In order to prevent the user from losing the personal information of the contact due to damage to the terminal, loss of the terminal or replacement of the terminal, the terminal may upload the personal information of the contact stored by the terminal to the server, so that the server stores the personal information of the contact, thereby making the server The user can download the personal information of the contact stored by the server from the server through another terminal.

 The existing terminal or server may further store the group information of the contact according to the setting of the user, and store the personal information of the contact in groups. However, the terminal cannot upload the group information of the contact stored by the terminal to the server, and cannot download the group information of the contact stored by the server from the server, thereby failing to accurately synchronize the contact information between the terminal and the server, thereby reducing the contact. The accuracy of human information synchronization. Summary of the invention

Embodiments of the present invention provide a method for synchronizing contact information, which is used to implement a terminal and a server. Accurate synchronization of contact information between contacts, improving the accuracy of contact information synchronization.

 The embodiment of the invention provides a method for synchronizing contact information, including:

 The terminal and the server synchronize the personal information of the contact;

 Sending, by the terminal, a packet upload request message to the server, where the packet upload request message includes packet information of the contact, so that the server searches the stored contact according to the grouping information of the contact Personal information is stored in groups.

 An embodiment of the present invention provides another method for synchronizing contact information, including:

 The terminal and the server synchronize the personal information of the contact;

 Sending, by the terminal, a packet download request message to the server;

 Receiving, by the terminal, a packet download response message returned by the server, where the packet download response message includes group information of a contact;

 The terminal stores the stored personal information of the contact according to the grouping information of the contact.

 The embodiment of the invention provides another method for synchronizing contact information, including:

 The terminal and the server synchronize the personal information of the contact;

 Sending, by the terminal, an add command based on an Open Mobile Alliance data synchronization protocol to the server, where the add command includes packet information of a contact, so that the server stores the location according to the grouping information of the contact The personal information of the contact is stored in a group; or the server sends an add command based on the Open Mobile Alliance data synchronization protocol to the terminal, where the add command includes group information of the contact, so that the terminal according to the The grouping information of the contact is stored, and the stored personal information of the contact is stored in groups.

According to the foregoing technical solution, the embodiment of the present invention sends a connection to the server through the terminal. The packet of the grouping information of the person uploads the request message, so that the server can store the personal information of the stored contact according to the grouping information of the contact, thereby realizing the synchronization of the grouping information of the contact of the terminal to the server, thereby The terminal-to-server contact information (personal information of the contact and the grouping information of the contact) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved; or the grouping of the grouping information including the contact from the server is received by the terminal. Downloading the response message, so that the terminal can store the personal information of the stored contact according to the grouping information of the contact, and realize the synchronization of the packet information of the server-to-terminal contact, thereby making the server-to-terminal contact The person information (personal information of the contact person and the grouping information of the contact person) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved; or the terminal sends an increase command including the grouping information of the contact to the server, thereby enabling the server to The grouping information of the contact, storing the personal information of the stored contact in groups, realizing the synchronization of the grouping information of the terminal-to-server contact, thereby making the terminal-to-server contact information (contact person's personal information and contact) The grouping information of the person can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved; or the server sends an increase command including the grouping information of the contact to the terminal, so that the terminal can store the information according to the grouping information of the contact. The personal information of the contact is stored in a group, and the grouping information of the contact of the server to the terminal is synchronized, so that the contact information of the server to the terminal (the personal information of the contact and the grouping information of the contact) can be accurately synchronized and improved. The accuracy of the synchronization of the contact information; or an increase command including the name of the group of the contact sequentially sent to the opposite end, and an increase command including the member identification information corresponding to the group name and the personal information of the contact, thereby The opposite end can Said personal information storage identification information and said contact members to the group name with the group corresponding to the above-described contacts are established, the terminal to achieve The server or server-to-terminal contact information (contact's personal information and contact grouping information) can be accurately synchronized, improving the accuracy of contact information synchronization. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. The drawings are some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work.

 1 is a schematic flow chart of a method for synchronizing contact information according to Embodiment 1 of the present invention;

 2 is a schematic flow chart of a method for synchronizing contact information according to Embodiment 2 of the present invention;

 FIG. 3 is a schematic flowchart of another method for synchronizing contact information according to Embodiment 3 of the present invention; FIG.

 4 is a schematic flowchart of another method for synchronizing contact information according to Embodiment 4 of the present invention;

 FIG. 5 is a schematic flowchart of still another method for synchronizing contact information according to Embodiment 5 of the present invention; FIG.

 FIG. 6 is a schematic flowchart of still another method for synchronizing contact information according to Embodiment 6 of the present invention; FIG.

 FIG. 7 is a schematic structural diagram of a terminal according to Embodiment 7 of the present invention;

FIG. 8 is a schematic structural diagram of a server according to Embodiment 8 of the present invention; FIG. FIG. 9 is a schematic structural diagram of another terminal according to Embodiment 9 of the present invention; FIG.

 FIG. 10 is a schematic structural diagram of another server according to Embodiment 10 of the present invention; FIG.

 FIG. 1 is a schematic structural diagram of still another terminal according to Embodiment 11 of the present invention;

 FIG. 12 is a schematic structural diagram of still another server according to Embodiment 12 of the present invention; FIG. 13 is a schematic structural diagram of still another terminal according to Embodiment 13 of the present invention;

 14 is a schematic structural diagram of still another server according to Embodiment 14 of the present invention; FIG. 15 is a schematic structural diagram of still another terminal according to Embodiment 15 of the present invention;

 FIG. 16 is a schematic structural diagram of a server according to Embodiment 16 of the present invention; FIG. 17 is a schematic structural diagram of a terminal according to Embodiment 17 of the present invention;

 FIG. 18 is a schematic structural diagram of still another server according to Embodiment 18 of the present invention. detailed description

 The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

 FIG. 1 is a schematic flowchart of a method for synchronizing contact information according to Embodiment 1 of the present invention. This embodiment is applicable to a scenario in which a terminal-to-server one-way synchronization is performed. As shown in FIG. 1, the method for synchronizing contact information in this embodiment may include the following steps:

 Step 101: The terminal and the server synchronize the personal information of the contact;

The terminal and the server can synchronize the personal information of the contact, and refer to the terminal in the prior art. A method for uploading personal information of a contact to a server to implement one-way synchronization from the terminal to the server, which is not described here.

 Step 102: The terminal sends a packet upload request message to the server, where the packet upload request message includes packet information of the contact, so that the server stores the personal information of the contact according to the group information of the contact. Perform group storage.

 The grouping information of the contact may include a group name and member identification information corresponding to the group name. The member identification information may be a Locally Unique Identifier (LUID) of the terminal.

 In this embodiment, the terminal sends a packet upload request message including the grouping information of the contact to the server, so that the server can store the personal information of the stored contact according to the grouping information of the contact, and implement the terminal. The synchronization of the grouping information of the contacts to the server enables the terminal-to-server contact information (personal information of the contact and the grouping information of the contacts) to be accurately synchronized, improving the accuracy of the synchronization of the contact information.

 FIG. 2 is a schematic flowchart of a method for synchronizing contact information according to Embodiment 2 of the present invention. This embodiment is applicable to a scenario in which a terminal-to-server one-way synchronization is performed. As shown in FIG. 2, the method for synchronizing contact information in this embodiment may include the following steps:

 Step 201: The terminal and the server synchronize the personal information of the contact;

 For the synchronization of the personal information of the contact between the terminal and the server, refer to the method for uploading the personal information of the contact to the server by the terminal in the prior art, and the one-way synchronization of the terminal to the server is implemented, and details are not described herein again.

Step 202: The terminal sends a packet upload request message to the server, where the packet upload request message includes group information of the contact; The grouping information of the contact may include a group name and member identification information corresponding to the group name. The member identification information may be a Locally Unique Identifier (LUID) of the terminal.

 Specifically, the hypertext transfer protocol (HTTP) header of the foregoing packet upload request message needs to upload an x-ds-data-type extension field, an x-ds-oper-type extension field, and an x-up- The calling-line-id field, where the value of the x-ds-data-type extension field is grp (contact grouping), for example: x-ds-data-type: grp, x-ds-oper-type extension field The value can be up (upload), for example: x-ds-oper-type: up , the value of the x-up-calling-line-id field is the user name of the terminal ( user id ), for example: x-up -calling-line-id: 139111 1111 1. Specifically, the content of the foregoing packet upload request message can be seen in Table 1.

 Table 1 Contents of the packet upload request message

Cred Type 1 String 认证类 认证的类型， 包括 MD5 型 认证、 SHA-1、 SHA-256 等。

Cred Type 1 String Type of authentication type, including MD5 type authentication, SHA-1, SHA-256, and so on.

 Cred Format 1 String Authentication format The format of the authentication information, including b64, binary, and so on.

 Cred Data 1 String Authentication Number The data used for authentication.

 According to

 UpDataReq MsgID 1 String Messages Each session is incremented from 1.

 number

 UpDataReq MaxMsgSize 1 String Terminal length The length of the message before compression, the most held: Bytes.

 Big news

 Length

 UpDataReq DevID 1 String Terminal Set An IMEI backup identification number information that is filled in as a terminal to uniquely identify an end device.

 UpDataReq DataType 1 String Data class The data type carried by this message.

 Type grp: contact grouping

 UpDataReq IsFinal 1 String Fl Sending a knot Contact packet data upload end flag Bundle flag.

 End: y

Not ended: n UpDataReq Grp One-to-one contact terminal has 0 to more group grouping information locally.

 Grp N 1 String Contact Contact group name not allowed Group name Duplicate.

 Weigh

 Grp M 1 String Contacts A contact can belong to multiple groups.

 Bay contact group member with terminal local LUID representation, multiple

LUIDs are separated by ",", for example:

1001, 1002, 1003, 1004 » Note: If it is a null group, the value is null.

 Step 203: The server performs group storage on the stored personal information of the contact according to the grouping information of the contact.

Further, in this step, the server may further perform authentication on the received packet upload request message, and after the authentication is passed, store the stored personal information of the contact. Specifically, the foregoing authentication process is as follows: When the terminal sends the packet upload request message, the terminal includes the authentication information in the packet upload request message, where the authentication information may include an authentication format, an authentication type, and authentication data, and the terminal may be based on the terminal. The algorithm specified by the user name, password, authentication random number (Nonce), and authentication type (Type field, for example: MD5 authentication), generates the specified identification Authentication data (Data field, for example: a string) of the format (Format field, for example: b64). After receiving the packet upload request message, the server may obtain the user name of the terminal in the x-up-calling-line-id field of the HTTP header, and corresponding to the user name of the terminal and the user name stored by the terminal according to the user name of the terminal. The password, the authentication random number, and the authentication type (Type field) included in the packet upload request packet, and the authentication data of the specified authentication format (Format field) included in the packet upload request packet is generated, and the server generates the authentication generated by itself. The data is compared with the authentication data (Data field) included in the packet upload request message. If the two fields are the same, the authentication succeeds, otherwise the authentication fails. The server may indicate the result of this authentication in the packet upload response message returned to the terminal.

 Step 204: The server returns a packet upload response message to the terminal.

 Specifically, the content of the foregoing packet upload response message can be seen in Table 2.

 Table 2 Contents of the packet upload response message

UpDataRes Cred 0 认 证 鉴权认证信息。

UpDataRes Cred 0 Authentication authentication information.

 1 from,

 1

 Cred Type String Type of authentication, including MD5 authentication type, SHA-SHA-256, etc.

Cred Format 1 String The format of the authentication information, including the format b64, binary, etc.

 Cred Data 1 String Authentication Data used for authentication.

 Data

 UpDataRes RespURI 0 String Continued Fill in the first response message.

 1 Destination address URI address of the subsequent request message of the URI terminal.

 DnDataRes IsSessionEnd 1 String Fl Session End of session flag.

 End of the end: y

 Flag not closed: n

UpDataRes Status 1 Status report processing result of the terminal uploading data to the terminal. Status Code String F3 Returns 401 - Authentication failed.

 Code 400 - Request message format error

 (Fields such as Msgld isFinal, DataType, MaxMsg Size, Type, Code are not filled in the specification format).

 510 - Server data operation failed.

 900 - User data sync latching (if the user is using another terminal to operate).

 000 - successful.

 999 - Partially successful.

NOTE: When returning 000, it means complete success, the operation can continue; when it returns 999, it means partial success, you need to check the Fail field for details; when returning other error codes, it means that this session fails and needs to be closed. Status Fail String Failure to fill in when the part is successful.

 Information Format: Contact group name # three digit error code, 10# three digit error code, where "#," and "," are separators. For example, classmate #400, colleague #400.

 400 - The data format is incorrect.

 420 - Server storage space is insufficient.

 Note: If the server returns a 420 error code, it indicates that the server has insufficient storage space and the server will end the session. That is, when there is a 420 error code in the response message, the value of the IsSessionEnd tag must be y.

 500 - Server internal error. 510 - Server database operation failed.

The detailed process of the embodiment of the present invention will be described below by way of a specific embodiment. For example: After the synchronization of the personal information of the contact between the terminal and the server is completed, when the terminal is ready to send the group information of the contact stored by the terminal to the server, the terminal may send the following to the server: Packet upload request message:

 POST http://pim. monternet. com/yjb/sync

 X-ds-data-type: grp

 X-ds-oper-type: up

<?xml version:" 1.0" encoding="UTF-8"?>

 <UpDataReq><! - Upload contact grouping ->

 <SessionID>K/SessionID>

 <MsgID>K/MsgID>

 <Cred>

 <Type xmlns= ' sync ml: metinf >syncml: auth-md5</Type> <Format xmlns= ' syncml: metinf >b64</Format>

<Data>Zz6EivR3yeaaENcRN61pAQ==</Data>

 </Cred>

 <MaxMsgSize> 100000</MaxMsgSize> <!--Maximum message length supported by the terminal, length of message before compression, unit: Byte 〉

 <DevID>IMEI: 1234567890123456</DevID> <! -- Terminal Equipment Identification ->

<DataType>grp</DataType> <!~grp: Contact grouping ->

 <Grp> <!—Contact Grouping—>

 <N>Classmate <^> <!--Contact Group Name ->

 <M>10001, 10002, 10003, 10004</M><—Contact group members, used between LUIDs

"," Separation -> </Grp>

 <Grp> <!—Contact Grouping—>

 <N>Colleague <^> <! -- Contact group name ->

 <M>20001 , 10002, 10003 , 20004</M> <—contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N> football team </N> <!--contact group name->

 <M>20001, 10002,30003,40004</M> <—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N>Warcraft </N> <!--Contact Group Name ->

 <M></M><—empty group, no member LUID-->

 </Grp>

 <IsFinal>n</IsFinal> <!-- indicates that the data has not been completely sent yet ->

 </UpDataReq>

 The server receives the packet upload request packet, and authenticates the packet upload request packet. After the authentication is passed, the stored personal information of the contact is stored in a packet, and the following packet upload response message is returned to the terminal:

 <?xml version:" 1.0" encoding="UTF-8"?>

<UpDataRes> <SessionID>K/SessionID>

 <MsgID>K/MsgID>

 <Cred>

 <Type xmlns= ' sync ml: metinf >syncml: auth-md5</Type> <Format xmlns= ' syncml: metinf >b64</Format>

<Data>adggjtrtryeaa356ssrtnrr==</Data>

 </Cred>

 <Is S e s s ionEnd>n</Is S e s s ionEnd> <!--session end flag: y-end, n-not ended->

 <Status>

 <Code>999</Code> <!—Response to the result, 401 - Authentication failed, 000 - Success, 999 - Partially successful 〉

 <Fail> Classmate #400, Colleague #400</Fail> <!--Failure data, contact group name # three digits Error code, contact group name # three digit error code, where # and are separators. 400 - Data format error, 420 - insufficient server storage space 〉

 </Status>

 <RespURI>http://10.0.0.1 :80/yjb/sync?sid=1400MjAwODA5MjctMDIyN TE4LTU0MS0yMTEuMTM4LjE4NC4yMDE</RespURI> 〈! - Terminal subsequent request The destination URI address of the message, where sid is the current session ID assigned by the server, and the load balancer distributes the message according to the server module ID (such as 1400) in the sid.

 </UpDataRes>

Receiving, by the terminal, the packet upload response message, and performing the packet upload response message After the authentication is passed, the packet information of the remaining contacts stored in the terminal is continuously sent to the server, and the terminal may send the following packet upload request message to the server:

 POST

 Http://10.0.0.1 :80/yjb/sync/?sid=1400MjAwODA5MjctMDIyNTE4LTU0 MS0yMTEuMTM4LjE4NC4yMDE

 X-ds-data-type: grp

 X-ds-oper-type: up

<?xml version:" 1.0" encoding="UTF-8"?>

 <UpDataReq><! - Upload contact grouping ->

 <SessionID>K/SessionID>

 <MsgID>2</MsgID>

 <MaxMsgSize> 100000</MaxMsgSize> <!--Maximum message length supported by the terminal, length of message before compression, unit: Byte 〉

 <DevID>IMEI: 1234567890123456</DevID> <! -- Terminal Equipment Identification ->

<DataType>grp</DataType> <! ― gr : contact group -->

 <Grp> <!—Contact Grouping—>

 <N>Family </N> <!--Contact Group Name ->

 <M>50001,50002,50003,50004</M><—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

<Grp><!—ContactGrouping—> <N>^f^</N><!—Contact Group Name—〉

 <M>60001,60002,60003,60004</M> <—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N>Fetion friend < 〉 <!--Contact group name ->

 <M>70001,70002,70003,70004</M><—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <IsFinal>y</IsFinal> <!- indicates that the data has been completely sent -->

 </UpDataReq>

 The server receives the packet upload request packet and performs authentication (simplely according to the session identifier included in the packet, which is similar to the prior art, and is not described here). After the authentication is passed, the storage is performed. The personal information of the remaining contacts is stored in a packet, and the following packet upload response message is returned to the terminal:

 <?xml version:" 1.0" encoding="UTF-8"?>

 <UpDataRes>

 <SessionID>K/SessionID>

 <MsgID>2</MsgID>

 <Is S e s s ionEnd>y</Is S e s s ionEnd> <!--session end flag: y-end, n-not ended->

<Status> <Code>000</Code><!—Response results, 000 - success, 999 - partial success ->

</Status>

 </UpDataRes>

 It should be noted that, in this embodiment, in the same session, for the first message of both parties, authentication authentication information, that is, a <0^3> field, is required, and the receiver authenticates the sender. In the message after the authentication is passed, the two parties only need to send the session identifier, that is, the <8688101 10> field, and the receiver can simply authenticate the sender. Because this session is authenticated, subsequent messages from both parties in this session are trustworthy.

 Further, the user or the service provider can also initiate synchronization of the group information of the contact from the server side by logging in to the portal (Web Portal). Specifically, the server may send a notification message to the terminal to notify the terminal to initiate synchronization with the server for the group information of the contact, and the notification message needs to include the synchronization identifier of the group information of the contact. The terminal may send a packet upload request message to the server according to the received notification message, and synchronize the group information of the contact. The foregoing notification message may be carried by a short message, a Wireless Application Protocol (WAP) Push message, or the like.

Further, in this embodiment, when the terminal updates the group information of the contact (including adding, deleting, and modifying), the terminal may send the group information of all contacts after the terminal update to the server by using the packet upload request message. (member name information corresponding to the group name and the group name), and storing the personal information of the contact stored by the user according to the grouping information of the contact from the terminal, for example: if the terminal updates the group name and/or the group name corresponding to the group name Member identification information, you can send a packet message containing the contact after the update to the server. The packet uploading request message of the information, the server also updates the member identification information corresponding to the group name and/or the group name in the personal information of the contact stored by the server. Specifically, the server can synchronize the grouping information of the contact by maintaining a Change Log. This modification record table is a record that maintains the modification of the grouping information of the contacts by the server since the last synchronization. The server compares the grouping information of the contact stored by the server with the grouping information of the contact sent by the terminal, and can obtain the grouping information of the contact updated by the terminal. The server can obtain the group information of the contact that is updated by itself from its own modification record table (ie, Change Log). According to the obtained grouping information of the contact updated by the terminal and the server, the server can perform a corresponding synchronization operation.

 Optionally, after the terminal and the server perform synchronization of the contact information (personal information of the contact and the group information of the contact), if the terminal updates the group information of the contact, the terminal may be in the grouping from the server. The upload request message includes the grouping information of the updated contact and the identification information of the range of the grouping information for identifying the contact in the message, and the identifier information may identify the grouping information of the contact in the message as the total contact. Grouping information of a person or grouping information of an updated contact.

 It should be noted that: if the update on the terminal conflicts with the update on the server, the server may perform a judgment according to the conflict processing policy configured by the server, and determine whether the update of the terminal is correct or the update of the server itself. Synchronize. For example: The terminal deletes a packet, and the server modifies the packet by modifying the packet name. If the server determines that the update is based on the terminal, the server deletes the packet.

Further, in the embodiment of the present invention, the terminal may further send an active cancellation notification message, which is used to cancel the grouping information of the uploading contact, and specifically, cancel the HTTP message of the notification text. The control parameter "X-DS-Abort-Sync" needs to be added to the header. If the user cancels the synchronization through the terminal, the parameter is carried and the parameter value is "True", and the message body is empty; otherwise, this parameter is not carried. E.g:

 POST

 Http://10.0.0.1 :80/yjb/sync?sid=1400MjAwODA5MjctMDIyNTE4LTU0M S0yMTEuMTM4LjE4NC4yMDE

 X-DS-Abort-Sync: True

 It should be noted that: When the server encounters the following abnormal conditions, the server will directly return an HTTP 400 error and will not return a response message. After receiving the HTTP 400 error, the terminal will terminate the operation and prompt the user with the failure information. Abnormal conditions can include, but are not limited to, the following:

 The WAP gateway IP address through which the request packet passes is illegal;

 The related parameters in the HTTP header of the request packet do not exist or are illegal.

 The request message corresponds to the session expiration or does not exist;

 The request packet stream resolution failed.

 In this embodiment, the terminal sends a packet upload request message including the grouping information of the contact to the server, so that the server can store the personal information of the stored contact according to the grouping information of the contact, and implement the terminal. The synchronization of the grouping information of the contacts to the server enables the terminal-to-server contact information (personal information of the contact and the grouping information of the contacts) to be accurately synchronized, improving the accuracy of the synchronization of the contact information.

FIG. 3 is a schematic flowchart of another method for synchronizing contact information according to Embodiment 3 of the present invention. This embodiment is applicable to a scenario in which a server-to-terminal one-way synchronization is performed. As shown in Figure 3, this The method for synchronizing contact information of an embodiment may include the following steps:

 Step 301: The terminal and the server synchronize the personal information of the contact;

 For the synchronization of the personal information of the contact between the terminal and the server, refer to the method for downloading the personal information of the contact from the server by the terminal in the prior art, and the one-way synchronization between the server and the terminal is implemented, and details are not described herein.

 Step 302: The terminal sends a packet download request message to the server.

 Step 303: The terminal receives the packet download response message returned by the server, where the packet download response message includes packet information of the contact;

 Step 304: The terminal stores the stored personal information of the contact according to the grouping information of the contact.

 The grouping information of the contact may include a group name and member identification information corresponding to the group name. The member identification information may be a Locally Unique Identifier (LUID) of the terminal.

 In this embodiment, the terminal receives the packet download response message from the server that includes the packet information of the contact, so that the terminal can store the personal information of the stored contact according to the grouping information of the contact, thereby realizing The synchronization of the grouping information of the server-to-terminal contact enables the server-to-terminal contact information (personal information of the contact and the grouping information of the contact) to be accurately synchronized, improving the accuracy of the synchronization of the contact information.

 FIG. 4 is a schematic flowchart of another method for synchronizing contact information according to Embodiment 4 of the present invention. This embodiment is applicable to a scenario in which a server-to-terminal one-way synchronization is performed. As shown in FIG. 4, the method for synchronizing contact information in this embodiment may include the following steps:

Step 401: The terminal and the server synchronize the personal information of the contact; For the synchronization of the personal information of the contact between the terminal and the server, refer to the method for downloading the personal information of the contact from the server by the terminal in the prior art, and the one-way synchronization between the server and the terminal is implemented, and details are not described herein again.

 Step 402: The terminal sends a packet download request message to the server.

 Specifically, the hypertext transfer protocol (HTTP) header of the foregoing packet download request message needs to upload an x-ds-data-type extension field, an x-ds-oper-type extension field, and an x-up- The calling-line-id field, where the value of the x-ds-data-type extension field is grp (contact grouping), for example: x-ds-data-type: grp, x-ds-oper-type extension field The value can be dn (download), for example: x-ds-oper-type: dn, the value of the x-up-calling-line-id field is the user name of the terminal ( user id ), for example: x-up -calling-line-id: 139111 1111 1. Specifically, the content of the foregoing packet download request message can be seen in Table 3.

 Table 3 Contents of the packet download request message

DnDataReq MsgID 1 String 报文编号 消息标识， 每次会话 中， 消息标识从 1开 始递增。

DnDataReq MsgID 1 String Message number message ID, the message ID is incremented from 1 in each session.

 DnDataReq Cred 0..1 —— —— Authentication Information Authentication and authentication information.

Cred Type 1 String Authentication Type The type of authentication, including

 MD5 authentication, SHA-1, SHA-256, etc.

 Cred Format 1 String - Authentication format The format of the authentication information, including b64, binary, etc.

Cred Data 1 String - Authentication data Data used for authentication.

DnDataReq MsgID 1 String - Message number Each session is incremented from 1 onwards.

 DnDataReq MaxMsgSize 1 String Terminal support The length of the message before compression, the maximum unit of elimination: Byte.

 Interest length

 DnDataReq DevID 1 String Terminal device Generally filled in as the terminal's identification IMEI number information, used to uniquely identify a terminal device.

 DnDataReq DataType 1 String Data Type The type of data carried by this message.

Grp: Contact grouping.

Status Fail String Error message Fill in when the part is successful.

 Format: Contact group name #三位错误码, contact group name #三位 Error code, where #和, is the separator. Such as classmate #400, colleague #400.

 400 - Data format error. 420 - The terminal storage space is insufficient.

 Note: If the terminal returns 420 error code, it means that the terminal has insufficient storage space. The server needs to end the session. That is, when there is 420 error code in the terminal request message, the server must set the value of the IsSessionEnd tag in the next response message. y.

Step 403: The server returns a packet download response message to the terminal, where the packet download response message includes packet information of the contact. The grouping information of the contact may include a group name and member identification information corresponding to the group name. The member identification information may be a Locally Unique Identifier (LUID) of the terminal.

 Further, in this step, the server may further authenticate the received packet download request message, and after the authentication is passed, return a packet download response message to the terminal.

 For details, refer to the related description in the foregoing Embodiment 2 of the present invention, and the details are not described herein again.

 Specifically, the content of the foregoing packet download response message can be seen in Table 4.

 Table 4 Contents of the group download response message

Cred Type 1 String 认证类 认证的类型， 包括 MD5 型 认证、 SHA-1、 SHA-256 等。

Cred Type 1 String Type of authentication type, including MD5 type authentication, SHA-1, SHA-256, and so on.

 Cred Format 1 String Authentication format The format of the authentication information, including b64, binary, and so on.

 Cred Data 1 String Authentication Number The data used for authentication.

 According to

 DnDataRes MsgID 1 String Messages Each session is incremented from 1.

 number

 DnDataRes RespURI ? String Follow-up Please fill in the target message in the first response message.

 The target URI address of the subsequent request message of the URI terminal.

 DnDataRes IsFinal 1 String Fl Sending a knot Contact group data download end flag Bundle flag.

 End: y

 Not ended: n

 DnDataRes IsSessionEn 1 String Session End Session End Flag.

 d 1 bundle sign end: y

 Not ended: n

DnDataRes Status 1 The status of the processing of the message uploaded by the terminal to the terminal. Status Code String F3 401 - Authentication failed.

 400 - Request message format error

(Fields such as Msgld isFinal, DataType, MaxMsg Size, Type, Code are not filled in the specification format).

510 - Server data operation failed.

 900 - User data sync latching (if the user is using another terminal to operate).

 000 - successful.

 999 - Partially successful.

NOTE: When returning 000, it means complete success, the operation can continue; when it returns 999, it means partial success, you need to check the Fail field for detailed information; when returning other error codes, it means that this session fails and needs to be closed. Status Fail ? String Failure letter is filled in when the part is successful.

 From, format: ID# three-digit error code, ID#

 Three-digit error code, where " #,, and ", " are separators. For example, 1001#400,1002#400„ 400 - Data format error.

 500 - Server internal error.

 510 - Server database operation failed.

 DnDataRes Grp One Contact There are 0 or more contacts on the server. Grouping information.

 Grp N 1 String Contact Contact group name not allowed Group name Duplicate.

 Weigh

 Grp M 1 String Contact A contact can belong to multiple groups.

The shell contact group members are represented by the terminal local LUID, and the multiple LUIDs are separated by ",", for example: 1001, 1002, 1003, 1004. Step 404: The terminal stores the stored personal information of the contact according to the grouping information of the contact. Further, in this step, the terminal may further perform authentication on the received packet download response message, and after the authentication is passed, store the stored personal information of the contact.

 Specifically, the authentication method of the terminal is similar to the authentication method of the server, and the authentication process is also referred to the related description in the second embodiment of the present invention, and details are not described herein again.

 The detailed process of the embodiment of the present invention will be described below by way of a specific embodiment. For example: After the synchronization of the personal information of the contact between the terminal and the server is completed, when the terminal prepares to download the group information of the contact stored by the server from the server, the terminal may send the following packet download request message to the server:

 POST http://pim. monternet. com/yjb/sync

 X-ds-data-type: grp

 X-ds-oper-type: dn

<?xml version:" 1.0" encoding="UTF-8"?>

 <DnDataReq> <!--Download contact grouping ->

 <SessionID>2</SessionID>

 <MsgID>K/MsgID>

 <Cred>

 <Type xmlns= ' sync ml: metinf >syncml: auth-md5</Type> <Format xmlns= ' syncml: metinf >b64</Format>

<Data> aklj ahlg; kfdaj; oiduao d==</Data>

 </Cred>

<MaxMsgSize>100000</MaxMsgSize><!--The maximum message length supported by the terminal, Length of message before compression, unit: Byte>

 <DevID>IMEI: 1234567890123456</DevID> <! - Terminal device identification --> <DataType>grp</DataType> <! ― gr : contact group -->

 </DnDataReq>

 The server receives the packet download request packet, and authenticates the packet download request packet. After the authentication is passed, the following group download response message is returned to the terminal:

 <DnDataRes> <!--Download contact grouping ->

 <SessionID>2</SessionID>

 <MsgID>K/MsgID>

 <IsSessionEnd>n</IsSessionEnd> <!--session end flag: y-end, n-not ended->

 <Cred>

 <Type xmlns= ' sync ml: metinf >syncml: auth-md5</Type> <Format xmlns= ' syncml: metinf >b64</Format>

<Data>aakljagiuoiaeuaiojdg;ajg=</Data>

 </Cred>

 <Status>

 <Code>000</Code> <!—Response to the result, 401 - Authentication failed, 000 - Success, 999 - Partially successful 〉

 </Status>

<RespURI>http://10.0.0.1 :80/yjb/sync?sid=1400MjAwODA5MjctMDIyN TE4LTU0MS0yMTEuMTM4LjE4NC4yMDE</RespURI><! -- Terminal follow-up request The destination URI address of the message, where sid is the current session ID assigned by the server, and the load balancer distributes the message according to the server module ID (such as 1400) in the sid.

 <Grp> <!—Contact Grouping—>

 <N>Classmate <^> <!--Contact Group Name ->

 <M>10001, 10002, 10003, 10004</M><—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N>Colleague <^> <! -- Contact group name ->

 <M>20001 , 10002, 10003 , 20004</M> <—contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N> football team </N> <!--contact group name->

 <M>20001, 10002,30003,40004</M> <—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N>Warcraft </N> <!--Contact Group Name ->

 <M></M> <- Empty group, no members LUID- ->

 </Grp>

<IsFinal>n</IsFinal><!-- indicates that the data has not been completely sent yet -> </DnDataRes>

 The terminal receives the packet download response message, and authenticates the packet download response message. After the authentication is passed, the stored personal information of the contact is stored in groups, and the group information of the currently downloaded contact is returned to the server. Processing the result, and continuing to prepare to download the group information of the remaining contacts stored by the server from the server, and the terminal may send the following group download request message to the server:

 POST

 Http://10.0.0.1 :80/yjb/sync/?sid=1400MjAwODA5MjctMDIyNTE4LTU0 MS0yMTEuMTM4LjE4NC4yMDE

 X-ds-data-type: grp

 X-ds-oper-type: dn

<?xml version:" 1.0" encoding="UTF-8"?>

 <DnDataReq> <!--Download contact grouping ->

 <SessionID>2</SessionID>

 <MsgID>2</MsgID>

 <MaxMsgSize> 100000</MaxMsgSize> <!--Maximum message length supported by the terminal, length of message before compression, unit: Byte 〉

 <DevID>IMEI: 1234567890123456</DevID> <! -- Terminal device identification —> <DataType>grp</DataType> <! ― gr : contact group -->

 <Status>

<Code>999</Code><!—Response to the result, 401 - Authentication failed, 000 - Success, 999 - Partial success>

 <Fail> Classmate #400, Colleague #400</Fail> <!--Failure data, contact group name # three digits Error code, contact group name # three digit error code, where # and are separators. 400 - data format error, 420 - insufficient terminal storage space 〉

 </Status>

 </DnDataReq>

 The server receives the packet download request packet, and performs the authentication on the packet download request packet. The authentication may be performed according to the session identifier included in the packet, which is similar to the prior art, and is not described here. After the right is passed, the following group download response message is returned to the terminal:

<DnDataRes> <!--Download contact grouping ->

 <SessionID>2</SessionID>

 <MsgID>2</MsgID>

 <IsSessionEnd>n</IsSessionEnd> <!--session end flag: y-end, n-not ended->

 <Status>

 <Code>000</Code> <!—Response to the result, 401 - Authentication failed, 000 - Success, 999 - Partially successful 〉

 </Status>

 <Grp> <!—Contact Grouping—>

 <N>Family </N> <!--Contact Group Name ->

 <M>50001,50002,50003,50004</M> <—Contact group members, used between LUIDs

"," Separation -> </Grp>

 <Grp> <!—Contact Grouping—>

 <Ν> <ίΝ> <!--Contact group name ->

 <Μ>60001,60002,60003,60004</Μ> <—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <Grp> <!—Contact Grouping—>

 <N>Fetion friend < 〉 <!--Contact group name ->

 <M>70001,70002,70003,70004</M><—Contact group members, used between LUIDs

"," Separation ->

 </Grp>

 <IsFinal>n</IsFinal> <!-- indicates that the data has not been completely sent yet ->

 </DnDataRes>

 The terminal receives the packet download response message, and authenticates the packet download response message (simplely according to the session identifier included in the packet, which is similar to the prior art, and is not described here). After the right is passed, the stored personal information of the remaining contacts is stored in groups, the processing result of the group information of the currently downloaded remaining contacts is returned to the server, and the group information of the remaining contacts stored by the server is continuously prepared to be downloaded from the server, the terminal The following packet download request message can be sent to the server:

 POST

Http://10.0.0.1 :80/yjb/sync/?sid=1400MjAwODA5MjctMDIyNTE4LTU0 MS0yMTEuMTM4LjE4NC4yMDE X-ds-data-type: grp

 X-ds-oper-type: dn

<?xml version:" 1.0" encoding="UTF-8"?>

 <DnDataReq> <!--Download contact grouping ->

 <SessionID>2</SessionID>

 <MsgID>3</MsgID>

 <MaxMsgSize> 100000</MaxMsgSize> <!--Maximum message length supported by the terminal, length of message before compression, unit: Byte 〉

 <DevID>IMEI: 1234567890123456</DevID><!—Terminal Device Identification—> <DataType>grp</DataType> <! ― gr : contact group -->

 <Status>

 <Code>000</Code> <!—Response to the result, 401 - Authentication failed, 000 - Success, 999 - Partially successful 〉

 </Status>

 </DnDataReq>

 The server receives the packet download request packet, and performs the authentication on the packet download request packet. The authentication may be performed according to the session identifier included in the packet, which is similar to the prior art, and is not described here. After the right is passed, the following group download response message is returned to the terminal:

<?xml version:" 1.0" encoding="UTF-8"?>

 <DnDataRes> <!--Download contact grouping ->

<SessionID>2</SessionID> <MsgID>3</MsgID>

 <Grp> <!—Contact Grouping—>

 <N>MSN Friends </N> <!—Contact Group Name—>

 <M>80001,80002,80003</M> <—Contact group members, separated by LUD with ",,, -->

 </Grp>

 <IsFinal>y</IsFinal> <!—Indicates that the data has all been sent—>

 <Is S e s s ionEnd>y</I s S e s s ionEnd> <!--session end flag: y - end, n - not ended -->

 <Status>

 <Code>000</Code> <!—Response to the result, 401 - Authentication failed, 000 - Success, 999 - Partially successful 〉

 </Status>

 </DnDataRes>

 It should be noted that, in the embodiment of the present invention, in the same session, for the first message of both parties, authentication authentication information, that is, a <0^ field, is required, and the receiver authenticates the sender. After the authentication is passed, the two parties only need to send the session identifier, that is, the <8688101 10> field, and the receiver can simply authenticate the sender. Because this session is authenticated, subsequent messages from both parties in this session are trustworthy.

Further, the user or the service provider can also initiate synchronization of the group information of the contact from the server side by logging in to the portal (Web Portal). Specifically, the server may send a notification message to the terminal, to notify the terminal to initiate a grouping message with the server for the contact. Synchronization of the information, the notification message needs to include the synchronization identifier of the group information of the contact. The terminal may send a packet download request message to the server according to the received notification message, and synchronize the group information of the contact. The notification message may be carried by a short message, a Wireless Application Protocol (WAP) push message, or the like.

Further, in this embodiment, when the server updates the group information of the contact (including adding, deleting, and modifying), the server may send the group of all contacts after the server terminal is updated to the terminal by using the group download response message. Information (group name and member identification information corresponding to the group name), and personal information of the contact stored by itself is stored according to the grouping information of the contact from the server, for example: if the server updates the group name and/or the group name corresponding The member identification information may send a notification message to the terminal to notify the terminal to initiate synchronization of the group information of the contact with the server. The terminal may send a packet download request message to the server, so that the server may send a packet download response message including the group information of the contact after the update to the terminal, and the terminal also correspondingly in the personal information of the contact stored by the terminal. Update the member identification information corresponding to the group name and/or the group name. Specifically, the terminal can implement grouping information of the synchronization contact by maintaining a change log (Change Log). This modification record table is a record for maintaining the modification of the grouping information of the contacts by the terminal terminal since the last synchronization. The terminal compares the grouping information of the contact stored by the terminal with the grouping information of the contact sent by the server, and can obtain the grouping information of the contact updated by the server. The terminal can learn the grouping information of the contact that is updated by itself from its own modification record table (ie, Change Log). According to the obtained grouping information of the contact updated by the terminal and the server, the terminal can perform a corresponding synchronization operation. Optionally, after the terminal and the server perform synchronization of the contact information (personal information of the contact and the group information of the contact), if the server updates the group information of the contact, the server may be in the grouping from the terminal. The download response message includes the grouping information of the updated contact and the identification information of the range of the grouping information for identifying the contact in the message, and the identifier information may identify the grouping information of the contact in the message as the total contact. Grouping information of a person or grouping information of an updated contact.

 It should be noted that: if the update on the terminal conflicts with the update on the server, the terminal may perform a judgment according to the conflict processing policy configured by the terminal, and determine whether the update of the server is correct or the update of the terminal itself. Synchronize. For example, the server deletes a packet, and the terminal modifies the packet by modifying the packet name. If the terminal determines that the update is based on the server, the terminal deletes the packet.

 Further, in the embodiment of the present invention, the terminal may further send an active cancellation notification message, which is used to cancel the grouping information of the downloaded contact. Specifically, the HTTP message header of the active cancellation of the notification message needs to add a control parameter "X-DS- Abort-Sync". If the user cancels the synchronization through the terminal, the parameter is carried and the parameter value is "True", and the message body is empty; otherwise, this parameter is not carried. E.g:

 POST

 Http://10.0.0.1 :80/yjb/sync?sid=1400MjAwODA5MjctMDIyNTE4LTU0M S0yMTEuMTM4LjE4NC4yMDE

 X-DS -Abort- Sync: True

It should be noted that: When the server encounters the following abnormal conditions, the server will directly return an HTTP 400 error, and will not return a response message. After receiving the HTTP 400 error, the terminal will Terminate this operation and prompt the user for the failure message. Abnormal conditions can include, but are not limited to, the following:

 The WAP gateway IP address through which the request packet passes is illegal;

 The related parameters in the HTTP header of the request packet do not exist or are illegal.

 The request message corresponds to the session expiration or does not exist;

 The request packet stream resolution failed.

 In this embodiment, the terminal receives the packet download response message from the server that includes the packet information of the contact, so that the terminal can store the personal information of the stored contact according to the grouping information of the contact, thereby realizing The synchronization of the grouping information of the server-to-terminal contact enables the server-to-terminal contact information (personal information of the contact and the grouping information of the contact) to be accurately synchronized, improving the accuracy of the synchronization of the contact information.

 It should be noted that: the synchronization of the group information of the contacts involved in the first embodiment and the second embodiment of the present invention can be regarded as “one-way synchronization from the terminal to the server”, for example: data backup, only the upload operation is required. The server can directly overlay the group information uploaded by the terminal to the group information stored by the server. The synchronization of the grouping information of the contacts involved in the third and fourth embodiments of the present invention can be regarded as "one-way synchronization from the server to the terminal", for example: data recovery, only the download operation is required, and at this time, the terminal can The group information downloaded by the server directly covers the group information stored by the terminal.

Further, the above-mentioned first and second embodiments of the present invention can further implement the "one-way synchronization of the server to the terminal", so that the two-way synchronization between the terminal and the server can be realized. For the specific implementation method, refer to the third and fourth embodiments of the present invention. The related content in the content is not described herein again; the third and fourth embodiments of the present invention further implement "one-way synchronization from the terminal to the server". For details, refer to the related content in the first and second embodiments of the present invention, and details are not described herein again.

 It should be noted that after the terminal performs the upload operation, the server needs to compare the information of the two parties one by one to identify whether the terminal needs to be notified to perform the download operation; or after the terminal performs the download operation, the terminal needs to perform information on both parties. One by one comparison to identify whether an upload operation needs to be performed.

 Therefore, the above-mentioned first to fourth embodiments of the present invention can implement "two-way synchronization between the terminal and the server", that is, synchronization of group information of contacts between the terminal and the server can be realized, thereby making contact information between the terminal and the server (contact The personal information of the person and the grouping information of the contact) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

 FIG. 5 is a schematic flowchart of a method for synchronizing contact information according to Embodiment 5 of the present invention. As shown in FIG. 5, the method for synchronizing contact information in this embodiment may include the following steps: Step 501: Terminal and server Synchronize the personal information of the contact;

 For the synchronization of the personal information of the contact between the terminal and the server, refer to the method for uploading the personal information of the contact to the server by the terminal in the prior art, to implement one-way synchronization from the terminal to the server, or to refer to the downloading from the server by the terminal in the prior art. The method of personal information of the contact person realizes one-way synchronization from the server to the terminal, and details are not described herein again.

Step 502: The terminal sends an Add (Add) command based on an Open Mobile Alliance (OMA)-based Data Synchronization (DS) protocol to the server, where the add command includes packet information of the contact, So that the server stores the stored personal information of the contact according to the grouping information of the contact; or The server sends an Add (Add) command based on the Data Synchronization (DS) protocol of the Open Mobile Alliance (OMA) to the terminal, where the added command includes the grouping information of the contact, so that the foregoing The terminal stores the stored personal information of the contact according to the grouping information of the contact.

 The grouping information of the contact may include a group name and member identification information corresponding to the group name. The member identification information may be a Locally Unique Identifier (LUID) of the terminal.

 In this embodiment, the terminal sends an add command including the group information of the contact to the server, so that the server can store the personal information of the stored contact according to the group information of the contact, and implement the terminal to the server. The synchronization of the contact information of the contact, so that the contact information of the terminal to the server (the personal information of the contact and the group information of the contact) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved; or the server sends the information to the terminal. An increase command of the grouping information of the contact is included, so that the terminal can store the personal information of the stored contact according to the grouping information of the contact, thereby realizing the synchronization of the grouping information of the server-to-terminal contact, thereby The server-to-terminal contact information (contact's personal information and contact grouping information) can be accurately synchronized, improving the accuracy of contact information synchronization.

This embodiment uses the existing Open Mobile Alliance (OMA) Synchronization Markup Language (SyncML) Data Synchronization (DS) protocol command to implement contact information. Accurate synchronization, specifically by using different message headers for synchronizing the personal information of the contact and synchronizing the grouping information of the contact, so the receiving party can distinguish the ones that are synchronized The person information, or the group information group information of the contact. Specifically, the form in which the above-mentioned increase command includes the group information of the contact may include, but is not limited to, the following forms:

 A. The add command can include the grouping information of the contact through the existing field;

 Specifically, the <^^1>/<16> field may be used to indicate that the data is grouping information of the contact, and the <Item>/<Source> field is used to carry the group name, using <^0>/<0 1> Field to carry member identification information. E.g:

 <Add> ; Add group members

 <CmdID>12345</CmdID> ; Command ID

<Cred> ; Certification information

 <Meta>

 <Type xmlns= ' syncml: metinf >syncml: auth-md5</Type>

 <Format xmlns= ' syncml: metinf >b64</Format>

 </Meta>

 <Data>Zz6EivR3yeaaENcRN61pAQ==</Data>

 </Cred>

 <Meta> ; Description of the data

 <Format xmlns= ' syncml: metinf >chr</Format>

 <Type xmlns=' syncml: metinf >text/x-group</Type> ; indicates that it is a group letter

</Meta>

 <Item>

<Source><LocURI>.^i^</LocURI></Source> Group Name <Data> 10003 , 10004</Data>; members of the group

</Item>

 </Add>

 B. Add a command to include the grouping information of the contact through the newly added field.

 Specifically, a <0卬> field may be added to indicate that the data is the grouping information of the contact, the <N> field is used to carry the group name, and the <^1> field is used to carry the member identification information. E.g:

 <Add> ; Add group members

 <Grp> ; indicates that the operation is on the group

 <N>Friends </N> ; Group name

<M>10003, 10004</M> ; Add group members with their IDs 10003 and 10004 respectively, other members are unchanged

 </Grp>

 </Add>

 Further, in this embodiment, when the terminal updates the group information of the contact (including adding, deleting, and modifying), the terminal may send an increase command, a delete command, and a modification according to the OMA-based DS protocol to the server. Replace ) command so that the server can perform the corresponding synchronization operation.

Further, after the server compares the grouping information of the contact sent by the terminal by the add command, the delete command, and the replace command, the server identifies that the contact information of the contact needs to be sent to the terminal (because the terminal contacts the contact The grouping information is updated.) The grouping information of the contact is sent to the terminal by adding a command, a delete command, and a replace command. In this way, the contact group of the contact can be realized between the terminal and the server. The interest is synchronized.

 Further, in this embodiment, when the server updates the group information of the contact (including adding, deleting, and modifying), the OMA-based DS protocol may be sent to the terminal by adding, deleting, and modifying the The <Replace> command, so that the terminal can perform the corresponding synchronization operation.

 Further, after the terminal compares the grouping information of the contact sent by the server by the add command, the delete command, and the replace command, the terminal identifies the group information that needs to be sent to the server (because the terminal contacts the contact The grouping information is updated.) The grouping information of the contact is sent to the server by adding a command, a delete command, and a replace command. In this way, the grouping information of the contacts can be synchronized between the terminal and the server.

 The detailed process of the embodiment of the present invention will be described below by way of several specific embodiments. For example: Add a new grouping information (may be empty), add the command can be as follows:

 <Add> ; Add a new group

 <Grp> ; indicates that the operation is on the group

 <N>Classmate </N> ; the name of the parent group where the new group is located

 <Grp>

 <N>University classmates <^> ; new group to be added

<M>10003, 10004</M> ; group member of the new group, can be empty </Grp>

 </Grp>

</Add> Or add a command can also be as follows:

 <Add> ; Power port grouping

 <Meta> Description of the data

 <Format xmlns= ' syncml: metinf >chr</Format>

 <Type xmlns= ' sync ml: metinf >text/x -group</Type> ; indicates grouping information </Meta>

 <Item>

； 增力口 "大学 同学" 的分组

; Grouping of "Liu University Students"

 <Data> 10003 , 10004</Data>; group member of the new group, can be empty

 </Item>

</Add>

 Modifying a member of a group to modify the member identification information in the group information, the modification command can be: ^ shown below:

 <Replace> ; Tampering with group members

 <Grp> ; indicates that the operation is on the group

 <N>Friends </N> Group Name

 <M>10003, 10004</M> ; The modification is a modification of the entire group member. After the modification, the group has only these two members.

 </Grp>

 </Replace>

Modify the name of a group to modify the group name in the group information, and the modification command can be as Shown below:

 <Replace> ; modify the group name

 <Grp> ; indicates that the operation is on the group

 <N>Friends </N> ; the old name of the group

 <NewName>Good friend </NewName> ; new name for grouping

 </Grp>

 </Replace>

 It should be noted that the modification of the packet can be divided into two cases: one is that the packet to be modified must exist, otherwise the modification fails; the other is that the modified packet is created if it does not exist. In order to avoid the ambiguity of the command, the terminal and the server must agree on one in advance.

 Deleting a member of a group deletes the member identification information in the group information, and the delete command can be: ^

 <Delete> ; delete group members

 <Grp> ; indicates that the operation is on the group

 <N>Friends </N> ; Group name

 <M>10003, 10004</M> ; delete members from the group

</Grp>

 </Delete>

 Deleting a group (including group name and member) means deleting the group name and member identification information in the group information. The delete command can be as follows:

 <Delete> ; delete group

<Grp>; indicates that the operation is on the group <N>Friends</N>; Group name

 </Grp>

 </Delete>

 Further, in this embodiment, the grouping information of the contact may also be queried, and may be implemented by using an OMA-based DS protocol (Get) command. The command to query a group may be as follows:

 <Get> ; query for group members

 <Grp> ; indicates that the operation is on the group

 <N>Friends </N> ; Group name

 </Grp>

 </Get>

 The receiver returns a list of member identification information for the packet, using the Results command. <Results> ; returns group members

 <Grp> ; indicates that the operation is on the group

 <N>Friends </N> ; Group name

 <M>10003, 10004</M> ; delete members from the group

 </Grp>

 </Results>

 Further, in this embodiment, the grouping information of the contact may also be queried, and may be implemented by using an OMA-based DS protocol (Get) command, and the query for querying all the packets (equivalent download) may be as follows:

<Get>; query for grouping information for all contacts <Grp>; indicates that the operation is on the group

 <N>J</N> ; indicates the root directory, that is, the grouping information of all contacts

</Grp>

 </Get>

 In this embodiment, the terminal may also send a delete command to the server to delete the group information of all contacts on the server, and then send an add command to the server to add group information of all contacts on the server (equivalent upload). . The delete command can be as follows:

 <Delete> ; delete group information for all contacts

 <Grp> ; indicates that the operation is on the group

 <N>J</N> ; indicates the root directory, that is, all group information

</Grp>

 </Delete>

 Note: The group name is "./", which means that it is the root directory, that is, the operation for all groupings.

 It should be noted that: for the addition of the grouping information of all the contacts, an empty group may be added first, and then the members are added to the respective groups. For details, refer to the description of the previous commands, and details are not described herein.

 Further, in this embodiment, if only one packet is deleted, but its members are not deleted, but become members of the ungrouped. In order to distinguish from existing commands, a separate parameter ( </DelGrp> field) is required to indicate, for example:

 <Delete> ; delete group A

 </DelGrp> ; indicates that only the group is deleted

<Meta>; Description of the data <Format xmlns= ' sync ml: metinf >chr</Format>

 <Type xmlns= ' sync ml: metinf >text/x -group</Type> ; indicates yes grouping information

 </Meta>

 <Item>

 <Source><LocURI>JA</LocURI></Source> ;

 </Item>

 </Delete>

 Further, in this embodiment, if a contact is transferred from the A packet to the B packet, two operations need to be included: first delete the contact from the A packet, and then add the contact to the B packet:

 <Delete> ; delete members of group A

<Meta> ; Description of the data

 <Format xmlns='syncml:metinf >chr</Format>

 <Type xmlns= ' syncml: metinf >text/x -group</Type> ; indicates yes grouping information

 </Meta>

 <Item>

 <Source><LocURI>JA</LocURI></Source> ; <Data>1001 </Data>

 </Item>

</Delete> <Add>; Add member to group B

<Meta> Description of the data

 <Format xmlns= ' syncml: metinf >chr</Format>

是分组信息 <Type xmlns='syncml:metinf >text/x-group</Type>

Is group information

 </Meta>

 <Item>

 <Source><LocURI>./B</LocURI></Source> ;

 <Data>1001 </Data>

 </Item>

 </Add>

 It should be noted that if you need to synchronize the group information of the contact, add the <Sync> command outside the command; if you do not synchronize, only manage, you do not need to add the <Sync> command. For example: For querying group information, you do not need to synchronize, you do not need to add the <Sync> command.

 Further, in this embodiment, the searching and filtering of the grouping information of the contact may be further implemented. Specifically, a search (Search) command and a Filter (Filter) command based on the OMA-based DS protocol can be utilized. In the search command, filter command, you can use the "GrpName" keyword to indicate the group name, and the "Group" keyword to indicate a group.

 For example: For a search for the group name "Friend", the search command can look like this:

 <Search>

<Source><LocURI>Jbrucel/emp_tabl.db</LocURI></Source> <Meta>

 <Type xmlns= ' syncml: metinf >application/s ql</Type>

 </Meta>

 <Data>SELECT EQ * WHERE "GrpName" EQ "Friend"</Data> </Search>

 For the filtering of the group "business", the filtering command can be as follows:

 <Filter>

 <Record>

 <Item>

 <Meta><Type>syncml:filtertype-cgi</Type></Meta> <Data>GROUP&iCON;business </Data>

 </Item>

 </Record>

 </Filter>

 It should be noted that: the contact group name of the contact cannot be duplicated, and for the same group, the server name and the client group name must be the same, which can satisfy most of the actual scenarios, and can reduce the local unique identifier and global uniqueness for the packet. The mapping process between the identifiers.

 Further, the packets can be nested, ie there can be sub-packets below the packets. The operation of the sub-packet is similar to the operation of the grouping, and will not be described here.

For example: A group and two subgroups below it can be structured as follows: <Grp> <N>Classmates</N;>

 <Grp>

 <N>University classmates <^>

 <M>1001,1002</N>

 </Grp>

 <Grp>

 <N>Secondary classmates < 〉

 <M>1003,1004</N>

 </Grp>

 </Grp>

 That is to say, if the group is nested inside another group, it means that it is a sub-group, for example, "college classmate" is in the "classmate", that is, sub-grouping; if the grouping is juxtaposed to another group, it means that it is juxtaposed. Grouping, for example: "University classmates" and "high school classmates" are juxtaposed, and are grouped in parallel.

 These structures can be used in commands such as <Add>, <Replace>, <Delete>, etc., similar to non-nested groups.

 In this embodiment, the personal information of the contact person and the group information of the contact are in a synchronized order. That is: If the terminal adds several contacts locally, and adds them to the A group. During the synchronization process, the personal information of the newly added contacts of the terminal needs to be added to the server to save and establish a mapping relationship through the <^1⁄2^11> command, and the terminal synchronizes the group information of the contact to the server to implement the server. Synchronization of contact information between.

FIG. 6 is a flowchart showing still another method for synchronizing contact information according to Embodiment 6 of the present invention; The method for synchronizing the contact information in this embodiment may include the following steps: Step 601: The terminal sends a first increase command to the server, where the first increase command includes a group name of the contact, so that the foregoing The server establishes a packet corresponding to the group name; or the server sends a first adding command to the terminal, where the first adding command includes a group name of the contact, so that the terminal establishes a packet corresponding to the group name;

 Step 602: The terminal sends a second increase command to the server, where the second increase command includes member identifier information corresponding to the group name and personal information of the contact, so that the server sends the member identifier information and the contact information. Personal information is stored in the above group; or

 The server sends a second increase command to the terminal, where the second increase command includes member identification information corresponding to the group name and personal information of the contact, so that the terminal stores the member identification information and the personal information of the contact. Go to the above grouping.

 The member identification information may be a Locally Unique Identifier (LUID) of the terminal.

 In this embodiment, the adding command of the packet name including the contact, and the adding command including the member identification information corresponding to the grouping name and the personal information of the contact, which are sequentially sent to the opposite end, enable the opposite end to The member identification information and the personal information of the above contact are stored in the established group corresponding to the group name of the contact, and the terminal-to-server or server-to-terminal contact information is realized (personal information of the contact and grouping of the contact) Information) Accurate synchronization, improving the accuracy of contact information synchronization.

In this embodiment, the grouping information of the contact is treated as a special data element, for example: Folder. Each group is a Folder. Hierarchical relationship between Folders Level to indicate. For example: JDataStore/Contact/Grp_A indicates A group; JDataStore/Contact/Grp_B indicates B group; JDataStore/Contact/Grp_B/l 0011 indicates 1001 1 contacts under B group. You only need to agree on a special identifier to indicate that it is a group, for example using the Grp_ prefix. Similarly, when synchronizing, you can also use the <^^1> element to indicate that this data element is a group.

 The operation of grouped data elements and groups can be done very well by reusing existing DS protocols. Specifically, the above-mentioned increase command includes the group name of the contact or the member identification information corresponding to the group name and the form of the personal information of the contact, which may include, but are not limited to, the following forms:

 A. The add command may include the group name of the contact or the member identification information corresponding to the group name and the personal information of the contact through the existing field;

 Specifically, when the grouping information of the contact is operated, the <Item>/<Meta>/<Type> field may be used to indicate that the information is the grouping information of the contact, and the <^11:>/<80111^;> field is used. To carry the group name, use the <:^11:>/<0&1&;> field to carry the member identification information. When operating the contact's personal information, use the <Item>/<Meta>/<Type> field to indicate that the information is the contact's personal information, and use the <^0>/<0 1> field to carry the contact's personal. information.

 B. The add command may include the group name of the contact or the member identification information corresponding to the group name and the personal information of the contact through the added field.

Specifically, when the group information of the contact is operated, the <Grp> field may be used to indicate that the information is the group information of the contact, and the <Grp>/<N> field is used to carry the group name, and <Grp>/<M is used. The 〉 field carries the member identification information. When working with a contact’s personal information, Use the <Item>/<Meta>/<Type> field to indicate that the information is the personal information of the contact, and use the <^11>/<0 1> field to carry the personal information of the contact.

 Specifically, the grouping information of the contact can be treated as a special data element, such as a Folder. Each group is a Folder. The hierarchical relationship between Folders is indicated by the hierarchy of the directory. For example: JDataStore/Contact/Grp_A is indicated as A group; JDataStore/Contact/Grp_B is indicated as B group; JDataStore/Contact/Grp_B/l 0011 indicates 1001 1 contact under group B. You only need to agree on a special identifier to indicate that it is a group, for example: Use the Grp_ prefix. Similarly, when synchronizing, you can also use the <^^1> element to indicate that this data element is a group. When the receiver receives the Grp_ prefix, or receives <Meta>/<Type> to indicate a packet, the corresponding data is processed as a packet. The operation of grouped data elements and groups can be done very well by reusing the commands of the existing OMA SyncML DS protocol.

 The detailed process of the embodiment of the present invention will be described below by way of several specific embodiments. First, add an empty grouping. Add the command as follows:

 <Add> ; Add B group

 <Meta> ; Description of the data

<Format xmlns= ' sync ml: metinf >chr</Format>

 <Type xmlns='syncml:metinf >text/x-folder</Type> ; indicates yes grouping information

 </Meta>

 <Item>

<Source> <LocURI>JDataStore/Contacts/Grp_B</LocURI>

 </Source> ; Group B

 <Data> - description of the group - </Data>

 </Item>

 </Add>

 Further add the corresponding members to the above added packets. The add command can be as follows: <Add> ; Add member contacts to B group

 <Meta> ; Description of the data

 <Format xmlns= ' syncml: metinf >chr</Format>

 <Type xmlns= ' syncml: metinf >text/x- vCard</Type> ; indicates contact information

 </Meta>

 <Item>

 <Source>

 <LocURI>JDataStore/Contacts/Grp_B/ 1001 1 </LocURI>

 </Source>

 <Data> - Contact vCard information ― </Data>

 </Item>

 </Add>

 The commands for other modification commands, delete commands, and acquisition commands are similar.

Modify a group and its member information, that is, the personal information of the contact. The modification command can be as follows: s/Du Oss-oosId ssnoiAV

/ //3⁄4/ ΐ ΐ 00 ΐos <53⁄4Ίaa:23⁄4ll><>0&suolo. .l </Source>

 <Data> - Contact vCard information ― </Data>

 </Item>

 </Update>

 The delete command to delete a group can be as follows:

 <Delete> ; Delete B group

 <Meta> ; Description of the data

<Format xmlns= ' sync ml: metinf >chr</Format>

 <Type xmlns='syncml:metinf >text/x-folder</Type> ; indicates yes grouping information

 </Meta>

 <Item>

 <Source>

 <LocURI>JDataStore/Contacts/Grp_B</LocURI>

 </Source> ; Group B

 </Item>

 </Delete>

 Further, in this embodiment, the grouping information of the contact may also be queried, and may be implemented by using a Get command. The command to query the grouping information of a group may be as follows:

 <Get> ; Get information about group B

<Meta> Description of the data <Format xmlns= ' sync ml: metinf >chr</Format>

 <Type xmlns='syncml:metinf >text/x-folder</Type> ; indicates yes grouping information

 </Meta>

 <Item>

 <Source>

 <LocURI>JDataStore/Contacts/Grp_B</LocURI>

 </Source> ; Group B

 </Item>

 </Get>

 In this embodiment, the personal information of the contact person and the group information of the contact are not synchronized. That is: If the terminal adds several contacts locally, and adds them to the A group. During the synchronization process, the personal information of the newly added contacts of the terminal does not need to be added to the server for storage and the mapping relationship is established by the <^1⁄2 11611:> command. As long as the terminal synchronizes the group name of the contact to the server, the server establishes a correspondence. The grouping, the terminal then synchronizes the corresponding member identification information and the contact's personal information to the server, in order to synchronize the contact information with the server.

 It should be noted that, in this embodiment, the contact information actually includes information in two formats, one is a personal information of a contact in a vCard format, and one is a group information of a contact in a Folder format. In terminal and server implementations, you can choose to store the data in either of these formats, or store them together.

It should be noted that: for the foregoing method embodiments, for the sake of simple description, The description is a series of combinations of actions, but those skilled in the art will appreciate that the present invention is not limited by the described order of the acts, as some steps may be performed in other sequences or concurrently in accordance with the present invention. In addition, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

 In the above embodiments, the descriptions of the various embodiments are different, and the details are not described in detail in an embodiment, and the related descriptions of other embodiments can be referred to.

 FIG. 7 is a schematic structural diagram of a terminal according to Embodiment 7 of the present invention. As shown in FIG. 7, the terminal in this embodiment may include a personal information synchronization module 71 and a packet information synchronization module 72. The personal information synchronization module 71 synchronizes the personal information of the contact with the server, and the packet information synchronization module 72 sends a packet upload request message to the server, where the packet upload request message includes the group information of the contact, so that the The server stores the stored personal information of the contact according to the grouping information of the contact.

 The functions of the terminal in the first embodiment and the second embodiment of the present invention can be implemented by the terminal provided by the embodiment of the present invention.

 In this embodiment, the packet information synchronization module sends a packet upload request message including the packet information of the contact to the server, so that the server can store the personal information of the stored contact according to the group information of the contact. The synchronization of the group information of the terminal-to-server contact is realized, so that the terminal-to-server contact information (personal information of the contact and the grouping information of the contact) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

FIG. 8 is a schematic structural diagram of a server according to Embodiment 8 of the present invention. As shown in FIG. 8, the server in this embodiment may include a personal information synchronization module 81 and a packet information synchronization module 82. The personal information synchronization module 81 synchronizes the personal information of the contact with the terminal, and the group information synchronization module 82 compares the group information of the contact included in the packet upload request message from the terminal to the stored personal person of the contact. Information is stored in groups.

 The functions of the server in the first embodiment and the second embodiment of the present invention can be implemented by the server provided by the embodiment of the present invention.

 In this embodiment, the packet information synchronization module receives the packet upload request message from the terminal that includes the packet information of the contact, so that the stored personal information of the contact is stored in groups according to the group information of the contact. The synchronization of the group information of the terminal-to-server contact is realized, so that the terminal-to-server contact information (personal information of the contact and the grouping information of the contact) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

 FIG. 9 is a schematic structural diagram of another terminal according to Embodiment 9 of the present invention. As shown in FIG. 9, the terminal in this embodiment may include a personal information synchronization module 91 and a packet information synchronization module 92. The personal information synchronization module 91 synchronizes the personal information of the contact with the server, and the packet information synchronization module 92 sends a packet download request message to the server, and receives a packet download response message returned by the server, and the packet download response message. The text includes grouping information of the contact, and the stored personal information of the contact is stored in groups according to the grouping information of the contact.

 The functions of the terminals in the third and fourth embodiments of the present invention can be implemented by the terminal provided by the embodiment of the present invention.

In this embodiment, the packet information response module receives the packet download response message from the server including the packet information of the contact, thereby enabling the group information according to the contact, The personal information of the stored contacts is stored in groups, and the grouping information of the contacts of the server to the terminal is synchronized, so that the contact information of the server to the terminal (the personal information of the contact and the grouping information of the contact) can be accurately Synchronization improves the accuracy of contact information synchronization.

 FIG. 10 is a schematic structural diagram of another server according to Embodiment 10 of the present invention. As shown in FIG. 10, the server in this embodiment may include a personal information synchronization module 1001 and a packet information synchronization module 1002. The personal information synchronization module 1001 synchronizes the personal information of the contact with the terminal, and the packet information synchronization module 1002 returns a packet download response message to the terminal according to the packet download request message from the terminal, and the packet download response message. The grouping information of the contact is included in the terminal, so that the terminal stores the stored personal information of the contact according to the grouping information of the contact.

 The functions of the servers in the third and fourth embodiments of the present invention can be implemented by the server provided by the embodiment of the present invention.

 In this embodiment, the packet information synchronization module sends a packet download response message including the packet information of the contact to the terminal, so that the terminal can store the personal information of the stored contact according to the group information of the contact. The synchronization of the grouping information of the server-to-terminal contact is realized, so that the server-to-terminal contact information (personal information of the contact and the grouping information of the contact) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

FIG. 11 is a schematic structural diagram of still another terminal according to Embodiment 11 of the present invention. As shown in FIG. 11, the terminal in this embodiment may include a personal information synchronization module 1101 and a packet information synchronization module 1102. The personal information synchronization module 1101 and the server perform personal information of the contact person. Synchronization, the packet information synchronization module 1 102 sends an increase command to the server, where the increase command includes group information of the contact, so that the server groups the stored personal information of the contact according to the group information of the contact. storage.

 The functions of the terminal in the fifth embodiment of the present invention can be implemented by the terminal provided by the embodiment of the present invention.

 In this embodiment, the group information synchronization module sends an increase command including the group information of the contact to the server, so that the server can store the personal information of the stored contact according to the group information of the contact, thereby realizing the terminal. The synchronization of the grouping information of the contacts to the server enables the terminal-to-server contact information (personal information of the contact and the grouping information of the contacts) to be accurately synchronized, improving the accuracy of the synchronization of the contact information.

 FIG. 12 is a schematic structural diagram of still another server according to Embodiment 12 of the present invention. As shown in FIG. 12, the server in this embodiment may include a personal information synchronization module 1201 and a packet information synchronization module 1202. The personal information synchronization module 1201 synchronizes the personal information of the contact with the terminal, and the group information synchronization module 1202 groups the stored personal information of the contact according to the group information of the contacts included in the increase command from the terminal. storage.

 The functions of the server in the fifth embodiment of the present invention can be implemented by the server provided by the embodiment of the present invention.

In this embodiment, the group information synchronization module receives an increase command of the packet information of the contact from the terminal, so that the stored personal information of the contact is stored in groups according to the group information of the contact, thereby realizing the terminal. The synchronization of the grouping information of the contacts to the server enables the terminal-to-server contact information (personal information of the contact and the grouping information of the contacts) to be accurately synchronized, improving the accuracy of the synchronization of the contact information. FIG. 13 is a schematic structural diagram of still another terminal according to Embodiment 13 of the present invention. As shown in FIG. 13, the terminal in this embodiment may include a personal information synchronization module 1301 and a packet information synchronization module 1302. The personal information synchronization module 1301 synchronizes the personal information of the contact with the server, and the group information synchronization module 1302 groups the stored personal information of the contact according to the group information of the contacts included in the increase command from the server. storage.

 The functions of the terminal in the fifth embodiment of the present invention can be implemented by the terminal provided by the embodiment of the present invention.

 In this embodiment, the group information synchronization module receives an increase command of the packet information of the contact from the server, so that the personal information of the stored contact is group-stored according to the group information of the contact, and the server is implemented. The synchronization of the grouping information of the contacts to the terminal enables the server-to-terminal contact information (personal information of the contact and the grouping information of the contacts) to be accurately synchronized, improving the accuracy of the synchronization of the contact information.

 FIG. 14 is a schematic structural diagram of still another server according to Embodiment 14 of the present invention. As shown in FIG. 14, the server in this embodiment may include a personal information synchronization module 1401 and a packet information synchronization module 1402. The personal information synchronization module 1401 synchronizes the personal information of the contact with the terminal, and the packet information synchronization module 1402 sends an increase command to the terminal, where the increase command includes the group information of the contact, so that the terminal is based on the contact. The group information stores the stored personal information of the above contacts in groups.

 The functions of the server in the fifth embodiment of the present invention can be implemented by the server provided by the embodiment of the present invention.

In this embodiment, the group information synchronization module sends an add command including the group information of the contact to the terminal, so that the terminal can store the information according to the group information of the contact. The personal information of the contact is stored in a group, and the grouping information of the contact of the server to the terminal is synchronized, so that the contact information of the server to the terminal (the personal information of the contact and the grouping information of the contact) can be accurately synchronized and improved. The accuracy of contact information synchronization.

 FIG. 15 is a schematic structural diagram of a terminal according to Embodiment 15 of the present invention. As shown in FIG. 15, the terminal in this embodiment may include a first synchronization module 1501 and a second synchronization module 1502. The first synchronization module 1501 sends a first increase command to the server, where the first increase command includes the group name of the contact, so that the server establishes the packet corresponding to the group name, and the second synchronization module 1502 sends the second message to the server. And adding the command, the second adding command includes the member identification information corresponding to the group name and the personal information of the contact, so that the server stores the member identification information and the personal information of the contact in the group.

 The functions of the terminal in the foregoing embodiment of the present invention can be implemented by the terminal provided by the embodiment of the present invention.

 In this embodiment, the first synchronization module sends an increase command including the group name of the contact to the server, and the second synchronization module sends an increase command to the server that includes the member identification information corresponding to the group name and the personal information of the contact. So that the server can store the above-mentioned member identification information and the personal information of the contact mentioned above into the established group corresponding to the group name of the contact, and realize the terminal-to-server contact information (personal information and contact of the contact person) The grouping information of the person can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

FIG. 16 is a schematic structural diagram of a server according to Embodiment 16 of the present invention. As shown in FIG. 16, the server in this embodiment may include a first synchronization module 1601 and a second synchronization module 1602. The first synchronization module 1601 is configured according to the association included in the first increase command from the terminal. The group name of the person, the group corresponding to the group name is established, and the second synchronization module 1602 associates the member according to the member identification information corresponding to the group name and the personal information of the contact included in the second addition command from the terminal. The identification information and the personal information of the above contact are stored in the above group.

 The functions of the server in the sixth embodiment of the present invention can be implemented by the server provided by the embodiment of the present invention.

 In this embodiment, the first synchronization module receives an increase command of the packet name of the contact from the terminal, so that the server can establish a packet corresponding to the packet name of the contact, and receive the second synchronization module from the terminal. An increase command including the member identification information corresponding to the group name and the personal information of the contact, so that the server can store the member identification information and the personal information of the contact in the established group, and implement the terminal-to-server connection. The person information (personal information of the contact person and the grouping information of the contact person) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

 FIG. 17 is a schematic structural diagram of a terminal according to Embodiment 17 of the present invention. As shown in FIG. 17, the terminal in this embodiment may include a first synchronization module 1701 and a second synchronization module 1702. The first synchronization module 1701 establishes a packet corresponding to the group name according to the group name of the contact included in the first addition command from the server, and the second synchronization module 1702 according to the second update command included in the server from the server. The member identification information corresponding to the group name and the personal information of the contact store the member identification information and the personal information of the contact person in the group.

The functions of the terminal in the foregoing embodiment of the present invention can be implemented by the terminal provided by the embodiment of the present invention. In this embodiment, the first synchronization module receives an increase command of the packet name of the contact from the server, so that the terminal can establish a packet corresponding to the packet name of the contact, and receive the second synchronization module from the server. An increase command including the member identification information corresponding to the group name and the personal information of the contact, so that the terminal can store the member identification information and the personal information of the contact in the established group, thereby implementing server-to-terminal contact The person information (personal information of the contact person and the grouping information of the contact person) can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved.

 FIG. 18 is a schematic structural diagram of still another server according to Embodiment 18 of the present invention, as shown in FIG.

As shown in FIG. 18, the server of this embodiment may include a first synchronization module 1801 and a second synchronization module 1802. The first synchronization module 1801 sends a first increase command to the terminal, where the first increase command includes a packet name of the contact, so that the terminal establishes a packet corresponding to the packet name, and the second synchronization module 1802 sends a second message to the terminal. And adding the command, the second adding command includes the member identification information corresponding to the group name and the personal information of the contact, so that the terminal stores the member identification information and the personal information of the contact in the group.

 The functions of the server in the sixth embodiment of the present invention can be implemented by the server provided by the embodiment of the present invention.

In this embodiment, the first synchronization module sends an increase command including the group name of the contact to the terminal, and the second synchronization module sends an increase command to the terminal that includes the member identification information corresponding to the group name and the personal information of the contact. So that the terminal can store the member identification information and the personal information of the contact to the established group corresponding to the group name of the contact, and implement the server-to-terminal contact information (personal information and contact of the contact). The grouping information of the person can be accurately synchronized, and the accuracy of the synchronization of the contact information is improved. A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

 It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Claim  A method for synchronizing contact information, comprising:  The terminal and the server synchronize the personal information of the contact;  Sending, by the terminal, a packet upload request message to the server, where the packet upload request message includes packet information of the contact, so that the server searches the stored contact according to the grouping information of the contact Personal information is stored in groups.  The method according to claim 1, wherein the grouping information of the contact includes a group name and member identification information corresponding to the group name.  The method according to claim 2, wherein after the terminal and the server synchronize the personal information of the contact, the terminal further includes:  The server sends a notification message to the terminal, where the notification message includes a synchronization identifier of the group information of the contact, to notify the terminal to initiate synchronization of the group information of the contact with the server.  The method according to claim 1, 2 or 3, wherein after the terminal sends a packet upload request message to the server, the method further includes:  The terminal sends an active cancellation notification message to the server to cancel the group information of the uploaded contact.  5. A method for synchronizing contact information, comprising:  The terminal and the server synchronize the personal information of the contact;  Sending, by the terminal, a packet download request message to the server; Receiving, by the terminal, a packet download response message returned by the server, where the packet downloading should be The message contains the group information of the contact;  The terminal stores the stored personal information of the contact according to the grouping information of the contact.  The method according to claim 5, wherein the group information of the contact includes a group name and member identification information corresponding to the group name.  The method according to claim 6, wherein after the terminal and the server synchronize the personal information of the contact, the terminal further includes:  The server sends a notification message to the terminal, where the notification message includes a synchronization identifier of the group information of the contact, to notify the terminal to initiate synchronization of the group information of the contact with the server.  The method according to claim 5, 6 or 7, wherein, after the terminal sends the packet download request message to the server, the method further includes:  The terminal sends an active cancellation notification message to the server to cancel the group information of the downloaded contact.  9. A method for synchronizing contact information, comprising:  The terminal and the server synchronize the personal information of the contact; Sending, by the terminal, an add command based on an Open Mobile Alliance data synchronization protocol to the server, where the add command includes packet information of a contact, so that the server stores the location according to the grouping information of the contact The personal information of the contact is stored in a group; or the server sends an add command based on the Open Mobile Alliance data synchronization protocol to the terminal, where the add command includes group information of the contact, so that the terminal according to the Narration The grouping information of the person is stored in groups for storing the personal information of the contact.  10. The method according to claim 9, wherein the group information of the contact includes a group name and member identification information corresponding to the group name.  The method according to claim 10, wherein the server stores the stored personal information of the contact according to the grouping information of the contact, or the terminal according to the contact The grouping information of the person, after storing the stored personal information of the contact, further includes:  Sending, by the terminal, an update command based on an Open Mobile Alliance data synchronization protocol to the server, where the update command includes a packet name and/or member identification information, so that the server is configured according to a group name included in the update command. And/or the member identification information re-storing the personal information of the contact related to the group name and/or the member identification information; or  Sending, by the server, an update command based on an Open Mobile Alliance data synchronization protocol to the terminal, where the update command includes a packet name and/or member identification information, so that the terminal according to the group name included in the update command And/or the member identification information re-stores the personal information of the contact related to the group name and/or the member identification information.  12. The method according to claim 11, wherein the update command comprises an add command, a delete command or a modify command.  The method according to claim 10, wherein the server stores the stored personal information of the contact according to the grouping information of the contact, or the terminal according to the contact The grouping information of the person, after storing the stored personal information of the contact, further includes: The terminal sends the data synchronization protocol based on the Open Mobile Alliance to the server a command/search command, where the acquisition command/search command includes a group name;  Receiving, by the terminal, a result command returned by the server, where the result command includes member identification information corresponding to the group name; or  Sending, by the server, an acquisition command/search command based on an Open Mobile Alliance data synchronization protocol to the terminal, where the acquisition command/search command includes a group name;  The server receives a result command returned by the terminal, where the result command includes member identification information corresponding to the group name.