KR20090042124A - Procedure for managing data synchronization under multiple devices environment - Google Patents

Abstract

A procedure for managing the data synchronization under the multiple devices environment is provided to perform the synchronization between the network-based storage server and the terminal which is not registered in the corresponding system. A terminal(14) which is not registered in the corresponding system communicates with a CPM communication server(20) in order to perform the registration procedure(S101). The CPM communication server check the state of terminal which requests the registration(S102). If the terminal is not synchronized, the CPM communication server produces the synchronization alerting message(S103). The generated synchronization alerting message is transmitted to the terminal(S104). The terminal receives the synchronization alerting message and connects to a network-based storage server(30), and performs the data synchronization with the network-based storage server(S105).

Description

Process for managing data synchronization under multiple devices environment

The present invention relates to data synchronization between a terminal and a network-based storage server, and more particularly, to a procedure for managing data synchronization between one or more terminals and a network-based storage server in a multi-terminal environment.

IP Multimedia Subsystem (IMS) is attracting attention as a core information and communication technology for providing new multimedia services in Internet Protocol (IP) based next generation communication environment. IMS is a set of nodes that provide various multimedia services and perform call control in the environment of mobile communication network, and integrates IP network and mobile communication environment. Accordingly, the IMS facilitates interoperation between the terminal and the IP network, thereby making it possible to provide multimedia services such as IP-based voice, audio, video, and data using the mobile communication terminal.

One of the signaling protocols that can be used in the IMS network is Session Initiation Protocol (SIP). SIP is an application layer call control protocol for creating, modifying and terminating an IP-based multimedia service session between a user terminal or between a user terminal and an entity having an IP address.

Among the various services provided through the IMS network, the CPM service is an existing multimedia communication service such as a short messaging service (SMS), a multimedia messaging service (MMS), an email service ( E-mail service, Instant Messaging & Presence Service (IMPS), etc. are integrated and provided under the IP base. Unlike conventional multimedia communication services provided only through limited networks and terminals, CPM enables unified services regardless of the type or number of terminals, media type, network type, and service type.

As such, the CPM service supports a multiple devices environment that allows multiple terminals to simultaneously use one address address. The CPM service stores and manages data such as messages and media objects based on the network so that an integrated service can be provided regardless of the type of terminal or access network and type of service. Etc., to enable this. The message & media storage function of the CPM system is a functional object for managing data stored in a message and media storage server on a network. The message & media storage function can be used to retrieve, store, and It performs functions such as deleting and creating and uploading a message or media object to a storage server.

However, in a system for managing a message and the like based on a network-based storage server in a multi-terminal environment such as a CPM service, it is necessary to implement data synchronization between each of the plurality of terminals and the network-based storage server. A related art related to data synchronization between a terminal and a network-based storage server is Request For Comments (RFC) 4455. However, RFC4549 relates to a synchronization procedure for disconnected Internet Messaging Access Protocol (IMAP) 4 clients. It only defines a procedure related to one-to-one synchronization between a terminal and a server.

There is a certain limitation in applying the procedure defined in RFC4549 to the data synchronization management procedure in a system supporting a multi-terminal environment such as a CPM service. This is because the procedure according to RFC4549, which prescribes one-to-one synchronization between a terminal and a server, does not consider data synchronization for a plurality of terminals sharing one address at all. In particular, in a multi-terminal environment, a change occurs in a storage state of data, etc. by one of a plurality of terminals sharing an address, or some terminals of the plurality of terminals are subscribed to a CPM service. However, it may not be registered in the CPM system. Existing data synchronization management procedures such as RFC4549 do not consider the characteristics of the multi-terminal environment at all.

Accordingly, an object of the present invention is to provide a data synchronization management procedure capable of synchronizing between a plurality of terminals and a network-based storage server in a system supporting a multi-terminal environment such as a CPM service.

Another problem to be solved by the present invention is data synchronization that can achieve synchronization between a terminal and a network-based storage server that are subscribed to the service but not registered in the system in a system supporting a multi-terminal environment such as a CPM service. To provide management procedures.

Another problem to be solved by the present invention, even in the system supporting a multi-terminal environment such as a CPM service, even if registered in the system does not participate in the change of the network-based storage server is not synchronized with the network-based storage server It is to provide a data synchronization management procedure for efficiently synchronizing a terminal with the network-based storage server.

One embodiment of the present invention for solving the above problems is a procedure for managing data synchronization in a multi-terminal environment using a CPM chat server, the registration procedure for the first terminal in response to a request of the first terminal And if it is determined that the first terminal is not synchronized based on the synchronization management information, generate a synchronization notification message for notifying that data synchronization is necessary, and wherein the first terminal is a network-based storage server. And transmitting the synchronization notification message to the first terminal so as to access to perform a data synchronization procedure.

Another embodiment of the present invention for solving the above problems is a procedure for managing data synchronization in a multi-terminal environment using a network-based storage server, the integrated notification message for notifying that the first terminal has registered an integrated IP Receiving from a messaging dialog server and generating a synchronization notification message to inform the first terminal that data synchronization is necessary when it is determined that the first terminal is not synchronized based on the synchronization management information, and transmitting to the first terminal. And communicating with the first terminal to perform a data synchronization procedure.

According to an aspect of the embodiments, the synchronization management information may be composed of variable data for managing data synchronization of one or more terminals sharing and using an integrated IP messaging address for the first terminal. In this case, the synchronization management information may include subscription terminal ID information consisting of a list of the one or more terminals, and synchronization status information for showing whether each of the one or more terminals is in data synchronization with the network-based storage server. Can be. The synchronization management information may further include at least one of registration state information indicating whether each of the one or more terminals is registered and user preference setting information indicating a user's preference for each of the one or more terminals. It may include.

According to another aspect of the embodiments, when the stored data of the integrated IP messaging address is updated or notified from the network based storage server, the CPM conversation server or network based storing the synchronization management information. The storage server may reset all of the synchronization state information of the synchronization management information for each of the one or more terminals to a 'unsynchronized state'.

According to an embodiment of the present invention, data synchronization between a plurality of terminals and a network-based storage server may be efficiently performed in a system supporting a multi-terminal environment such as a CPM system. In particular, when a terminal subscribed to a CPM service but not registered in the CPM system registers in the CPM system or there is an update of a network-based storage server, synchronization between the terminal and the network-based storage server is effectively performed. Can be achieved with

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

Embodiments of the present invention may be applied to a system including a network-based storage server and also having a multi-terminal environment. An example of such a system is a CPM system, hereinafter, an embodiment of the present invention will be described using the CPM system as an example. However, embodiments of the present invention should not be limited to being applied only to a CPM system, and may be equally applicable to a system including a network-based storage server and supporting a multi-terminal environment.

In a system supporting a multi-terminal environment to which an embodiment of the present invention is applied, for example, a CPM system, a plurality of CPM clients subscribed to a CPM service may share and use a single CPM address. However, each of the plurality of CPM clients does not always need to be registered in the CPM system, and some CPM clients (eg, terminals powered off) may not be registered in the CPM system at a specific time point.

CPM systems typically have a CPM Conversation Server, a Message & Media Storage, a Converged Address Book, a CPM User Preferences, and an Interworking Function. ), And a CPM client. Here, the message and media storage server is a network-based storage server included in the CPM system. A description of the architecture of the CPM system, the functions of each of the elements constituting the CPM system, and the interface between the components is described in OMA-AD-CPM-V1_0-20071004-D, which is one of the standard documents of the Open Mobile Alliance (OMA). And since it is described in more detail in OMA-RD-CPM-V1_0-20070927-D, a detailed description thereof will be omitted here. In the present specification, only the contents necessary for describing the embodiments of the present invention will be briefly described, and the portions not described herein may be applied to the standardized documents cited above.

1 is a block diagram illustrating some components of a CPM system for explaining a procedure for managing synchronization between a plurality of terminals and a network-based storage server in a multi-terminal environment according to an embodiment of the present invention. Referring to FIG. 1, the CPM system includes a plurality of terminals 12 and 14, a CPM Conversation Server 20, and a network-based storage server 30. do.

The terminals 12 and 14 are devices for connecting to a mobile communication network and communicating with a functional entity on a network such as another terminal or an IMS network, and the name thereof is not particularly limited. For example, the terminals 12 and 14 may be a device, a user equipment in a universal mobile telecommunication system (UMTS), a global system for mobile communication (GSM), or an inter standard-95 (IS-95). It may be called a mobile station (MS), etc., but is not limited thereto.

Among the terminals 12 and 14 illustrated in FIG. 1, the first terminal 12 is devices registered in the CPM system in order to use the CPM service (hereinafter, referred to as a 'registration terminal'). On the other hand, the second terminal 14 are devices that are subscribed to the CPM service but are not registered in the CPM system (hereinafter, referred to as 'unregistered terminal'). The unregistered terminal may be, for example, a device that is currently powered off, or a device registered in the IMS system but not registered in the CPM system.

The terminals 12 and 14 basically include a controller, a CPM client, and a transceiver. The controller is an entity for controlling the operation of functional entities (eg, a CPM client, a user interface (UI), a transceiver, etc.) inside the terminals 12 and 14. The transceiver is an entity for allowing the terminals 12 and 14 to transmit and receive various signals through the mobile communication network.

The CPM client is a functional entity for interacting with other components of the CPM system, such as the CPM chat server 20 or the network-based storage server 30, etc. to allow the user to initiate and access the CPM service. The CPM client is responsible for generating and receiving SIP requests and responses, and can use the related functions provided by IMS Core (not shown). In addition, the CPM client performs client-side CPM service logic related functions, such as generating and receiving CPM messages, and CPM session processing related functions.

The CPM dialog server 20 performs core CPM server functions for realizing all communication in the CPM service, user preferences and service provider policies, and the like for session and media control and message processing between the home network and the CPM network. Provides functions The CPM Conversation Server logically controls CPM and user specific functions such as CPM Participating Function, CPM Conversation History Function, and CPM Deferred Messaging Function. It includes a common controlling function such as a function (CPM Controlling Function). Here, user specific functions are provided for the user involved in initiating and terminating the request, and when the CPM chat server provides common control functionality, it typically terminates the incoming request and distributes the request to multiple recipients or communicates with the group. Can handle

Among these, the CPM participation function controls sessions and media and processes messages according to service capabilities, user preferences, service provider policies, and the like. For example, the CPM Participation feature registers a CPM client for users, manages and handles the initiation, modification, and termination of CPM sessions with CPM clients that register or request registration, and the service provider's policies or users in the CPM session. Apply your preference.

In addition, according to an aspect of the present embodiment, the CPM conversation server 20 may perform a function for data synchronization management for each of the plurality of terminals 12 and 14. For example, the CPM conversation server 20 stores 'synchronization management information' for each CPM address (CPM service user) separately, and when the unregistered terminal 14 newly registers or the network-based storage server 30. When data synchronization is required for the registration terminal 12 due to changes or updates of stored messages and / or media, data synchronization may be managed using the stored synchronization management information. Functions for data synchronization management for the terminals 12 and 14 may be performed by the CPM participation function PF of the CPM conversation server 20, for example, but is not limited thereto.

The synchronization management information includes information including information necessary for data synchronization management for one or more CPM subscriber stations 12 and 14 sharing the same CPM address. In more detail, the synchronization management information uses subscribed device ID information indicating a list of terminals 12 and 14 that are subscribed to the CPM service, that is, a list of CPM clients, and the like, by using the corresponding CPM address. Synchronization Status information indicating whether each of the CPM clients are synchronized at the present time may be included.

The synchronization management information may further include registration status information indicating whether each of the subscribing terminals is registered in the CPM system and / or user preferences setting information in each of the subscribing terminals. have. The registration status information is for determining whether the terminals 12 and 14 are in a registration state at this time, and the user preference setting information is option information individually set by the user for the terminals 12 and 14, for example. In this case, the message may be information indicating a user's choice about whether to send a notification message or the like when there is an update of the message and the media storage server 30.

According to an embodiment of the present invention, the synchronization management information may be managed as follows as dynamic data. For example, whenever the corresponding address of the network-based storage server 30 is updated due to reception of a message or deletion of a stored message, the synchronization state information of the terminals 12 and 14 are not all synchronized. Can be reset collectively. When a synchronization procedure is performed between a CPM client of a specific terminal and a network-based storage server according to an embodiment of the present invention described below, the synchronization status information may be changed to indicate a synchronized state with respect to the corresponding terminal.

Such synchronization management information may be a variable data table, for example, a synchronization management table (SMT). In this case, the synchronization management table may be composed of the following fields. However, fields to be described later are exemplary, and a field for containing other information may be further added.

Subscribed device ID field

Synchronization status field

Registration status field

User preferences setting field

The network-based storage server 30 is a functional entity for storing and managing messages and media on a network. This network-based storage server 30 may be connected directly or indirectly by other components of the system, such as the terminals 12, 14 and the CPM conversation server 20. The network-based storage server 30 performs a synchronization procedure by communicating with the registration terminal 12 when there is a change or update of stored messages and media related information, or the unregistered terminal 14 registers with the CPM system. In this case, it is possible to perform a synchronization procedure by communicating with these terminals 14.

In addition, according to another aspect of the present embodiment, the network-based storage server 30 other than the CPM dialog server 20 stores the synchronization management information (SMT) for each of the plurality of terminals (12, 14) synchronization management procedure You can also do In this case, the synchronization management information does not need to be separately stored in the CPM conversation server 20, and the synchronization management information, for example, the synchronization management table SMT, is stored in the network-based storage server 30 so that the terminals 12 and 14 are stored. It is used for the synchronization management of).

Next, a synchronization management procedure according to an embodiment of the present invention in the aforementioned CPM system will be described.

First embodiment

2 is a message flow diagram illustrating a synchronization management procedure according to the first embodiment of the present invention. The first embodiment of the present invention is a synchronization management procedure for an unregistered terminal (for example, the terminal of reference numeral 14 of FIG. 1) subscribed to the CPM service but not registered in the CPM system in a multi-terminal environment. For example, the SMT is stored in the participation function PF of the CPM conversation server 20 instead of the network-based storage server 30.

Referring to FIG. 2, first, a terminal 14 which is not registered in the CPM system performs a registration procedure for registering with the CPM system by communicating with the CPM conversation server 20 (S101). The registration procedure of this step is the same as a normal registration procedure in the CPM system, and there is no particular limitation in the manner. For example, the terminal 14 may perform a registration procedure using the SIP REGISTER request method. According to this, the terminal 14 transmits a SIP REGISTER message, which is a registration request message, to the CPM chat server 20, and the CPM chat server 20 responds to the received SIP REGISTER message with a consent message or an acknowledgment message (for example, SIP 200OK message) is transmitted to the terminal 14. 3A shows an example of the format of the SIP REGISTER message that the terminal 14 sends to the CPM chat server 20.

After the registration procedure for the terminal 14 is completed or after receiving a registration request message from the terminal 14, the participation function PF of the CPM conversation server 20 is currently synchronized with the terminal 14 requesting registration. It is checked whether or not the state is (S102). Checking for synchronization may use synchronization management information stored in the CPM conversation server 20, for example, SMT. That is, the CPM chat server 20 may examine the synchronization status field of the SMT to determine whether the terminal 14 requesting registration is synchronized or not.

Subsequently, when it is determined in step S102 that the terminal 14 is not synchronized, the CPM conversation server 20 generates a notification message for notifying the fact, for example, a synchronization notification message (Synchronization Notification Message). S103) and transmits the generated synchronization notification message to the terminal 14 (S104). However, the generation and transmission of the synchronization notification message (S103 and S104) may be determined based on the setting state of the user preference setting field for each terminal in the SMT. For example, when the user preference setting field of the SMT for the terminal 14 is set to allow reception of a notification message such as a synchronization notification message, the steps S103 and S104 are performed, but the reception is set to the reception rejection. In this case, steps S103 and S104 can be omitted.

The synchronization notification message may be a message using a SIP request method, for example, a SIP SIP MESSAGE message or a SIP NOTIFY message. 3B is a diagram illustrating an example of a format for a SIP MESSAGE message as an example of such a SIP request method. Referring to FIG. 3B, the SIP MESSAGE message includes 'Synchronization required' as information indicating that synchronization is required, but the present embodiment is not limited thereto.

Subsequently, the terminal 14 receiving the synchronization notification message accesses the network-based storage server 30 and transmits and receives a predetermined signal to perform data synchronization with the network-based storage server 30 (S105). The terminal 14 may access the network-based storage server 30 using, for example, source address information or the like included in the received synchronization notification message or using previously acquired information. According to the embodiment of the present invention, the data synchronization procedure performed between the terminal 14 and the network-based storage server 30 is not particularly limited. For example, the data synchronization procedure S105 may be performed using any one of the following methods ① to ③ or may be performed according to a new data synchronization protocol instead of a known synchronization procedure.

① Follow the synchronization protocol specified in RFC4551 or RFC4549 and draft-ietf-lemonade-profile-bis-05, the synchronization protocol for IMAP4 clients.

② How to use the OMA Data Synchronization (DS) Enabler.

A method of establishing a session (eg, a SIP session) between the terminal 14 and the network-based storage server 30 and synchronizing by sending and receiving predetermined signaling through the session. In this case, the terminal 14 sends a session invitation message (eg, SIP Invite message) to the network-based storage server 30, and the network-based storage server 30 confirms or acknowledges the received session invitation message. By sending a message (eg, a SIP 200 OK message), a SIP session can be established between the terminal 14 and the network-based storage server 30.

Next, after the synchronization procedure between the terminal 14 and the network-based storage server 30 is completed, the network-based storage server 30 generates a notification message, for example, a result notification message to inform the completion of the synchronization CPM conversation server Transfer to step 20 (S106). This step is for updating the synchronization status information for the terminal 14 of the SMT in the CPM dialog server 20 that stores the synchronization management information (eg, SMT). The result notification message may be a SIP request method, for example a SIP MESSAGE message, or may be sent to the CPM conversation server 20 using a SIP NOTIFY message. 3C illustrates a SIP MESSAGE message as an example of the result notification message. Referring to FIG. 3C, information 'Synchronization completed' is included as information for informing that the synchronization is completed successfully, but the present embodiment is not limited thereto.

The CPM conversation server 20 receiving the result notification message updates the stored synchronization management information (eg, SMT) (S107). For example, when receiving a result notification message including information indicating that the synchronization has been successfully completed, the CPM conversation server 20 may store the synchronization management information stored in the synchronization status field of the SMT, for example, the terminal 14. Change to the synchronized state.

As described above, according to the first embodiment of the present invention, the participation function PF of the CPM chat server 20, for example, the CPM chat server 20, stores the synchronization management information SMT. When the unregistered terminal 14 is registered in the CPM system, the participation function PF determines whether the terminal 14 is synchronized using the SMT. As a result of the determination, if it is determined that synchronization is not necessary, the synchronization procedure is performed between the terminal 14 and the network-based storage server 30. If the synchronization is successfully completed, the participation function PF stores the synchronization. The SMT is updated to indicate that the terminal 14 is synchronized.

Second embodiment

3 is a message flow diagram illustrating a synchronization management procedure according to a second embodiment of the present invention. The second embodiment of the present invention is also the first method described above in that it is a synchronization management procedure for an unregistered terminal (for example, the terminal of reference numeral 14 of FIG. 1) subscribed to the CPM service in the multi-terminal environment but not registered in the CPM system. Although the same as the embodiment, the synchronization management table SMT, which is the synchronization management information, is stored in the network-based storage server 30 instead of the CPM conversation server 20, which is different from the first embodiment described above. The following description will focus on differences from the first embodiment described above.

Referring to FIG. 4, first, the terminal 14 which is not registered in the CPM system performs a registration procedure for registering with the CPM system by communicating with the CPM conversation server 20 (S201). The registration procedure of this step is also the same as a normal registration procedure in the CPM system, and there is no particular limitation in the manner. For example, the terminal 14 may perform a registration procedure using the SIP REGISTER request method. According to this, the terminal 14 transmits a SIP REGISTER message, which is a registration request message, to the CPM chat server 20, and the CPM chat server 20 responds to the received SIP REGISTER message with a consent message or an acknowledgment message (for example, SIP 200OK message) is transmitted to the terminal 14. 5A shows an example of the format of the SIP REGISTER message that the terminal 14 sends to the CPM chat server 20.

When the registration procedure for the terminal 14 is completed or when a registration request message is received from the terminal 14, the CPM conversation server 20 may notify the user of the registration of the terminal 14, for example, a registration notification message. Notification Message) is transmitted to the network-based storage server 30 (S202). This informs the network-based storage server 30 of the registration of the terminal 14 and checks the synchronization state of the terminal 14 using the synchronization management information (SMT) stored in the network-based storage server 30. will be.

The registration notification message may be a message using a SIP request method, for example, a SIP SIP MESSAGE message or a SIP NOTIFY message. 5B is a diagram illustrating an example of a format for a SIP MESSAGE message as an example of such a SIP request method. Referring to FIG. 5B, the SIP MESSAGE message includes 'CPM user01-10 has just registered' as information indicating that the terminal 14 is registered. However, the present embodiment is not limited thereto.

The network-based storage server 30 that receives the registration notification message checks whether the terminal 14 that has registered with the CPM system is currently in a synchronized state (S203). Checking for synchronization may use synchronization management information stored in the network-based storage server 30, for example, SMT.

Subsequently, when it is determined in step S203 that the terminal 14 is not synchronized, the network-based storage server 30 generates a notification message for informing the fact, for example, a synchronization notification message (S204). The synchronized notification message is transmitted to the terminal 14 (S205). However, the generation and transmission of the synchronization notification message (S204 and S205) may be determined based on the setting state of the user preference setting field for each terminal in the SMT.

The synchronization notification message may be a message using a SIP request method, for example, a SIP SIP MESSAGE message or a SIP NOTIFY message. 5C is a diagram illustrating an example of a format for a SIP MESSAGE message as an example of such a SIP request method. Referring to FIG. 5C, the SIP MESSAGE message includes 'Synchronization required' as information indicating that synchronization is required, but the present embodiment is not limited thereto.

Subsequently, the terminal 14, which has received the synchronization notification message, connects to the network-based storage server 30 and exchanges predetermined signaling with the network-based storage server 30, similarly to step S105 of the first embodiment. Data synchronization is performed (S205). After the synchronization procedure is completed between the terminal 14 and the network-based storage server 30, the network-based storage server 30 updates stored synchronization management information (eg, SMT) (S206). As a result, the stored synchronization management information, for example, the synchronization status field of the SMT, is displayed as being synchronized with the terminal 14.

As described above, according to the second embodiment of the present invention, the network-based storage server 30 stores the synchronization management information SMT. When the unregistered terminal 14 is registered in the CPM system, the CPM conversation server 20 notifies the network-based storage server 30 of the fact, and the network-based storage server 30 uses the SMT stored in the terminal. It is determined whether 14 is synchronized. As a result of the determination, if it is determined that synchronization is not necessary, a synchronization procedure is performed between the terminal 14 and the network-based storage server 30. When the synchronization is completed, the network-based storage server 30 stores the synchronization. The SMT is updated to indicate that the terminal 14 is synchronized.

Third embodiment

6 is a message flow diagram illustrating a synchronization management procedure according to a third embodiment of the present invention. The third embodiment of the present invention is a registered terminal registered with the CPM service when there is a change or update in the data state stored in the network-based storage server in a multi-terminal environment (for example, the terminal of reference numeral 12 of FIG. 1). This is different from the above-described first and second embodiments in that the synchronization management procedure for. The third embodiment is the first embodiment described above in that the synchronization management table SMT, which is synchronization management information, is stored in the participation function PF of the CPM conversation server 20 instead of the network-based storage server 30. Same as the embodiment. The third embodiment will be described below centering on the difference from the first embodiment described above.

Referring to FIG. 6, when there is an update of stored data for a given CPM address, the network-based storage server 30 firstly sends a notification message for notifying that the data of the predetermined CPM address has been updated, for example, an update notification message. (Update Notification Message) is generated and transmitted to the CPM chat server 20 (S301). According to the embodiment of the present invention, there is no limitation as to why the network-based storage server 30 is updated. For example, a network-based storage server by communication between any one terminal among registered terminals (eg, a terminal indicated by '1' among terminals included in reference numeral 12 in FIG. 1) and a network-based storage server 30. This may include a case where a change occurs in the data state of 30 or a message received from a third terminal having a corresponding CPM address as a destination.

The update notification message may be a message using a SIP request method, for example, a SIP SIP MESSAGE message or a SIP NOTIFY message. 7A illustrates an example of a format for a SIP MESSAGE message as an example of such a SIP request method. Referring to FIG. 7A, the SIP MESSAGE message includes 'Storage has been updated' as information indicating that the network-based storage server 30 has been updated. However, the present embodiment is not limited thereto.

The CPM conversation server, for example, the participation function PF, which has received the update notification message, resets all the synchronization status fields of the stored synchronization management information SMT to a state of 'not synchronized' (S302). This step is equally applied regardless of whether the terminals included in the synchronization management information SMT are the terminals 12 registered in the CPM system or the terminals 14 not registered.

Subsequently, the CPM conversation server 20 generates a notification message for notifying that the terminal 12 is not synchronized for the terminal 12 registered in the CPM system, for example, a synchronization notification message (S303), and then generates the generated synchronization notification. The message is transmitted to the terminal 12 (S304). However, the generation and transmission of the synchronization notification message (S303 and S304) may be determined based on the setting state of the user preference setting field for each terminal in the SMT.

The synchronization notification message may be a message using a SIP request method, for example, a SIP SIP MESSAGE message or a SIP NOTIFY message. 7B is a diagram illustrating an example of a format for a SIP MESSAGE message as an example of such a SIP request method. Referring to FIG. 7B, the SIP MESSAGE message includes 'Synchronization required' as information indicating that synchronization is required, but the present embodiment is not limited thereto.

Subsequently, the terminal 12 receiving the synchronization notification message accesses the network-based storage server 30 and transmits and receives a predetermined signal to perform data synchronization with the network-based storage server 30 (S305). For example, the terminal 12 may access the network-based storage server 30 by using source address information or the like included in the received synchronization notification message or using previously acquired information. According to the embodiment of the present invention, the data synchronization procedure performed between the terminal 12 and the network-based storage server 30 is not particularly limited.

Next, after the synchronization procedure is completed between the terminal 12 and the network-based storage server 30, the network-based storage server 30 generates a notification message for informing the result of the synchronization procedure, for example, a result notification message to generate a CPM conversation. The server 20 transmits the data to the server 20 (S306). This step is for updating the synchronization status information for the terminal 12 of the SMT in the CPM dialog server 20 that stores the synchronization management information (eg, SMT). The result notification message may be a SIP request method, for example a SIP MESSAGE message, or may be sent to the CPM conversation server 20 using a SIP NOTIFY message. 7C is a diagram illustrating a SIP MESSAGE message as an example of the result notification message. Referring to FIG. 7C, information 'Synchronization completed' is included as information for informing that the synchronization has been completed successfully, but the present embodiment is not limited thereto.

After receiving the result notification message indicating that the synchronization has been successfully completed, the CPM conversation server 20 updates the stored synchronization management information (eg, SMT) (S307). As a result, the stored synchronization management information, for example, the synchronization status field of the SMT, is displayed as being synchronized with the terminal 12.

As described above, according to the third embodiment of the present invention, the participation function PF of the CPM chat server 20, for example, the CPM chat server 20, stores the synchronization management information SMT. If a change in the data state occurs due to an update of the network-based storage server 30, the participation function PF resets the synchronization state field of the SMT for all terminals 12 and 14 to be 'unsynchronized state'. do. In addition, the registered terminal 12 is notified of the fact that the synchronization procedure between the terminal 12 and the network-based storage server 30 is in progress, and if the synchronization is successfully completed, the participation function (PF) stores the stored SMT It updates and shows that the terminal 12 is synchronized.

Fourth embodiment

8 is a message flow diagram illustrating a synchronization management procedure according to a fourth embodiment of the present invention. A fourth embodiment of the present invention is a registered terminal registered in the CPM service when there is a change or update in the data state stored in a network-based storage server in a multi-terminal environment (for example, the terminal of reference numeral 12 of FIG. 1). This is different from the first and second embodiments described above in that it is a synchronization management procedure with respect to the third embodiment. The fourth embodiment is the same as the second embodiment described above in that the synchronization management table SMT, which is synchronization management information, is stored in the network-based storage server 30 instead of the CPM conversation server 20. The fourth embodiment will be described below centering on the differences from the above-described second and third embodiments.

Referring to FIG. 8, when there is an update of stored data with respect to a predetermined CPM address, the network-based storage server 30 does not synchronize all of the synchronization status fields of the stored synchronization management information SMT. Reset to the state of 'S401. This step is equally applied regardless of whether the terminals included in the synchronization management information SMT are the terminals 12 registered in the CPM system or the terminals 14 not registered.

In addition, the network-based storage server 20 generates a notification message for notifying that the synchronization is not performed for the terminal 12 registered in the CPM system, for example, a synchronization notification message (S402), and generates a synchronization notification message. To transmit to the terminal 12 (S403). The synchronization notification message may not be transmitted to the terminal 14 which is not currently registered in the CPM system. The generation and transmission of the synchronization notification message (S402 and S403) with respect to the registration terminal 12 may be determined based on the setting state of the user preference setting field for each terminal in the SMT. .

The synchronization notification message may be a message using a SIP request method, for example, a SIP SIP MESSAGE message or a SIP NOTIFY message. 9 shows an example of a format for a SIP MESSAGE message as an example of such a SIP request method. Referring to FIG. 9, the SIP MESSAGE message includes 'Synchronization required' as information indicating that synchronization is required, but the present embodiment is not limited thereto.

Subsequently, the terminal 12 receiving the synchronization notification message accesses the network-based storage server 30 and transmits and receives a predetermined signal to perform data synchronization with the network-based storage server 30 (S404). According to the embodiment of the present invention, the data synchronization procedure performed between the terminal 12 and the network-based storage server 30 is not particularly limited.

Next, after the data synchronization procedure between the terminal 12 and the network-based storage server 30 is completed, the network-based storage server 30 updates the stored synchronization management information (eg, SMT) (S405). As a result, the stored synchronization management information, for example, the synchronization status field of the SMT, is displayed as being synchronized with the terminal 12.

As described above, according to the fourth embodiment of the present invention, the network-based storage server 30 stores the synchronization management information SMT. If a change in the data state occurs due to an update of the network-based storage server 30, the network-based storage server 30 sets the synchronization state field of the SMT for all terminals 12 and 14 to 'unsynchronized state'. Reset to. In addition, the registered terminal 12 is notified of the fact that the synchronization procedure between the terminal 12 and the network-based storage server 30 proceeds, and when the synchronization is completed, the network-based storage server 30 stores the stored SMT It updates and shows that the terminal 12 is synchronized.

The embodiments of the present invention described in detail above are merely illustrative of the technical idea of the present invention, and should not be construed as limiting the technical idea of the present invention by the embodiments. The protection scope of the present invention is specified by the claims of the present invention described later.

1 is a block diagram illustrating some components of a CPM system for explaining a procedure for managing synchronization between a plurality of terminals and a network-based storage server in a multi-terminal environment according to an embodiment of the present invention.

2 is a message flow diagram illustrating a synchronization management procedure according to the first embodiment of the present invention.

3A shows an example of a format of a registration request message transmitted from a terminal to a CPM chat server according to the first embodiment of the present invention.

3B shows an example of a format of a synchronization notification message transmitted from a CPM chat server to a terminal according to the first embodiment of the present invention.

Figure 3c shows an example of the format of the result notification message sent by the network-based storage server to the CPM chat server according to the first embodiment of the present invention.

4 is a message flow diagram illustrating a synchronization management procedure according to a second embodiment of the present invention.

5A illustrates an example of a format of a registration request message transmitted from a terminal to a CPM chat server according to a second embodiment of the present invention.

5B shows an example of a format of a registration notification message that a CPM chat server sends to a network-based storage server according to a second embodiment of the present invention.

5C shows an example of a format of a synchronization notification message transmitted from a network-based storage server to a terminal according to the second embodiment of the present invention.

6 is a message flow diagram illustrating a synchronization management procedure according to a third embodiment of the present invention.

7A illustrates an example of a format of an update notification message that a network-based storage server sends to a CPM chat server according to a third embodiment of the present invention.

7B illustrates an example of a format of a synchronization notification message transmitted from a CPM chat server to a terminal according to the third embodiment of the present invention.

7C shows an example of a format of a result notification message sent by a network-based storage server to a CPM conversation server according to a third embodiment of the present invention.

8 is a message flow diagram illustrating a synchronization management procedure according to a fourth embodiment of the present invention.

9 illustrates an example of a format of a synchronization notification message transmitted from a network-based storage server to a terminal according to the fourth embodiment of the present invention.

Claims (10)

In response to a request from the first terminal, performing a registration procedure for the first terminal, If it is determined that the first terminal is not synchronized based on the synchronization management information, generate a synchronization notification message for notifying that data synchronization is necessary, and And transmitting the synchronization notification message to the first terminal so that the first terminal accesses a network-based storage server to perform a data synchronization procedure. The synchronization management method of claim 1, wherein the synchronization management information comprises variable data for managing data synchronization of one or more terminals sharing and using an integrated IP messaging address for the first terminal. How to manage. The method of claim 2, wherein the synchronization management information is Subscriber terminal ID information consisting of a list of the one or more terminals, And synchronization status information for showing whether each of the one or more terminals is in data synchronization with the network-based storage server. The method of claim 3, wherein the synchronization management information is And at least one of registration status information for indicating whether each of the one or more terminals is registered and user preference setting information for indicating a user's preference for each of the one or more terminals. Method of managing synchronization in a multi-terminal environment. The method of claim 3, wherein when the network-based storage server is informed that the stored data of the integrated IP messaging address has been updated, all of the synchronization state information for each of the one or more terminals is 'unsynchronized'. The synchronization management method in a multi-terminal environment, characterized in that for resetting. The method of claim 1, Receive a notification message for notifying the completion result of the synchronization for the first terminal from the network-based storage server, And updating the synchronization management information based on the received notification message. Receiving a registration notification message from the integrated IP messaging conversation server for notifying that the first terminal has registered; If it is determined that the first terminal is not synchronized based on the synchronization management information, generate a synchronization notification message for notifying that the data synchronization is necessary, and transmit the same to the first terminal; and A method of managing data synchronization in a multi-terminal environment comprising communicating with the first terminal to perform a data synchronization procedure. The synchronization management method of claim 7, wherein the synchronization management information comprises variable data for managing data synchronization of one or more terminals sharing and using an integrated IP messaging address for the first terminal. How to manage. The multi-terminal environment of claim 7, wherein when the stored data of the integrated IP messaging address is updated, all of the synchronization state information for each of the one or more terminals is reset to an 'unsynchronized state'. How to manage synchronization in. The method of claim 7, wherein And updating the synchronization management information based on a synchronization completion procedure with the first terminal.

Images