Patent Application
20140019417
This application claims the priority under 35 U.S.C. §119(a) to Korean Application Serial No. 10-2012-0075798, which was filed in the Korean Intellectual Property Office on Jul. 11, 2012, the entire content of which is hereby incorporated by reference.
1. Field of the Invention
The present disclosure relates generally to a method and apparatus for managing personal information in a communication system that provides a Converged Address Book (CAB) service.
2. Description of the Related Art
A Converged Address Book (CAB) service that is a general single network-based address book service stores a single network address in a network, and improves an experience of a user and a function associated with the stored single network address book. In particular, various devices that may be manipulated by a user can access the single network address book regardless of a time and a place, and the synchronization is performed for this.
When restoration of a document where a change occurs due to modification, deletion, addition, and the like with respect to personal information used by a user is required, a communication system that provides the CAB service requires a method that enables the user to readily restore the document.
Accordingly, an aspect of the present disclosure is to provide a user with an effective method and an apparatus for managing personal information by including a current version information value of a personal information XML (eXtensible markup language) document and information associated with a number of times of restoration in a request in a case of requesting restoration of the personal information XML document.
In accordance with another aspect of the present disclosure, a method of managing personal information in a communication system that provides a Converged Address Book (CAB) service is provided. The method includes: generating, by a CAB user, a restoration request for restoring a personal document, which includes a document recognition value of a personal document stored in the CAB, current version information of the personal document, and property information instructing restoration of the personal document to a previous version of the current version; transmitting, by the CAB user, the restoration request to a server that manages the CAB through an arbitrary device; and receiving, by the CAB user, a response indicating that the personal document is restored to the previous version of the current version from the server through the arbitrary device.
In accordance with another aspect of the present disclosure, a method of managing personal information in a communication system that provides a CAB service is provided. The method includes: receiving, from a CAB user, a restoration request for restoring a personal document that is stored in the CAB in advance; obtaining, from the restoration request, a document recognition value of the personal document, current version information of the personal document, and property information instructing restoration of the personal document to a previous version of the current version, and restoring the personal document to the previous version of the current version to correspond to the property information; and informing the CAB user of a response indicating a restoration result through an arbitrary device.
In accordance with another aspect of the present disclosure, an apparatus for managing personal information in a communication system that provides a CAB service is provided. The apparatus includes: a message generating unit to generate a restoration request for restoring a personal document, which includes a document recognition value of the personal document stored in the CAB, a current version of the personal document, property information instructing restoration of the personal document to a previous version of the current version, in response to an input by a CAB user; a transmitting unit to transmit the restoration request to a server that manages the CAB through an arbitrary device by the CAB user; and a receiving unit to receive, from the server, a response indicating that the personal document is restored to the previous version of the current version.
In accordance with another aspect of the present disclosure, an apparatus for managing personal information in a communication system that provides a CAB service is provided. The apparatus includes: a receiving unit to receive, from a CAB user, a restoration request for restoring a personal document that is stored in the CAB in advance; a controller to obtain, from the restoration request, a document recognition value of the personal document, current version information of the personal document, and property information instructing restoration of the personal document to the previous version of the current version, and restoring the personal document to the previous version of the current version to correspond to the property information; and a transmitting unit to inform the CAB user of a response indicating a restoration result through an arbitrary device.
According to the embodiments of the disclosure invention, when restoration of a personal information eXtensible markup language (XML) document which needs restoration is requested in a communication system that provides a Converged Address Book (CAB) service, a request including a current version information value of the personal information XML document and information associated with a number of times of restoration is transferred, and a server that receives the request restores the personal information XML document based on the current version information value and the information associated with the number of times of restoration and thus, there is no need of a procedure in which a user obtains the corresponding personal information XML document so as to determine a previous version of the personal information XML document, and there is no need to perform restoration a predetermined number of times. Accordingly, a method that may enable the user to effectively manage personal information may be provided.
The above and other aspects, features, and advantages of the present disclosure will be more apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:
Hereinafter, operation principles of exemplary embodiments of the present disclosure will be described in detail with reference to accompanying drawings. In the following description, the same elements will be designated by the same reference numerals although they are shown in different drawings. Further, in the following description of the present disclosure, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present disclosure rather unclear. Then, terms described later are defined in consideration of the functions of the present disclosure, but may vary according to the intention or convention of a user or operator. Therefore, its definition will be made based on the overall contents of this specification.
Referring to
The CAB client 100 communicates with the CAB server 105 through a terminal, authenticates a CAB user, synchronizes contact information, that is, personal profile information (Personal Contact Card (PCC)) and a converged address book stored in a network storage unit, and transmits, to the CAB server 105, demands made by the CAB user for, for example, address subscription, address searching, address sharing, interacting with an existing address book, managing user preference, or the like.
The CAB server 105 is a main network component in a CAB structure, and processes requests of the CAB user received from the CAB client 100. A main function of the CAB server 105 includes CAB client mutual authentication, storing a CAB address, synchronizing address information, and receiving an update of address information from the address subscription function and reflecting the same. Also, the CAB server 105 is a network component that reflects address subscription/sharing/translating and user preference/policy and the like, and includes an address subscription function that receives a number of a CAB user preference XML document and a request for subscription of a CAB user from a CAB user preference App. Usage, an address sharing function that applies personal preferences of data obtained through the address subscription and reflects the same to an address book, maintains subscription status information, and shares a PCC or a converged address book, and an interworking function that is associated with an existing address book system or exposures an interface to an external enabler, and the like. In addition, as an application usage (App. Usage) associated with the CAB enabler, an XDM server that manages data of a user includes a CAB AB App. Usage 112 that stores a converged address book and contact status, a CAB user Pref App. Usage 116 that manages preferences of a user, a CAB FH (Feature Handler) App. Usage 118 that manages a CAB service request/response, and a CAP PCC App. Usage 114 that stores PCC information. In addition to the above, an XDMC for accessing various App. Usage functions, a Session Initiation Protocol/Internet Protocol (SIP/IP) Core Network for message-routing with entities of an external domain, and a PUSH enabler for transferring notification messages of non-SIP terminals, and the like are included.
In particular, referring to
1. Address Book Synchronization
First, in a case of the address book synchronization function, 1) when a CAB user modifies a local address stored in a corresponding terminal, the CAB client 100 transmits modified information to the CAB server 105 through a CAB-1 (SyncML) interface. Then, 2) an address book (AB) synchronization function 105-1 provided by the CAB server 105 reflects the modification of the local address book to the CAB AB App/Usage 112 corresponding to an XML document management server, through an XDM Agent 105-5. In this example, when formats between the CAB client 100 and the CAB AB App. Usage 112 are different from each other, translation occurs and thus, the translation into different formats may cause a loss of data.
2. Contact Subscription
In a case of the contact subscription function, 1) the CAB client 100 sends an XML Configuration Access Protocol (XCAP) request for contact subscription to the CAB User Pref App. Usage 116. 2) The CAB User Pref App. Usage 116 that receives the XCAP request adds, to a contact subscription list, a contact address obtained from the XCAP request. 3) The CAB User Pref App. Usage 116 informs a contact subscription function 105-6 of the CAB server 105, of a change of a document of the contact subscription list caused by the adding operation. 4) The contact subscription function 105-6 directly sends a contact subscription request for a PCC of a receiver from the contact subscription list to a domain of a reception side, directly or through a subscription proxy. 5) The CAB PCC App Usage 116 that receives the contact subscription request determines access permission and user preferences with respect to the contact subscription request, and informs a receiver of a subscription result. 5) Also, in a case of an environment that does not support an SIP, a corresponding terminal and an enabler use an XDM Document Command Protocol (XDCP) and thus, the CAB client 100 may execute subscription to a corresponding address.
3. Contact Sharing
In a case of a contact sharing function, 1) the CAB client 100 sends an XCAP request for sharing a contact, to a CAB FH App. Usage 118. 2) Then, the CAB FH App. Usage 118 adds a contact address obtained from the XCAP request and a reference of data to be shared to a CAB feature Handler. 3) The CAB FH App. Usage 118 informs a contact share function 105-3 of the CAB server 105, of a change of a document caused by adding the contact address obtained from the XCAP request and the reference of the data to be shared. 4) The contact share function 1053-3 recognizes a contact status of a CAB AB App. Usage of the receiver based on the address of the receiver. 4-1) When the receiver is a CAB user, the contact share function 105-3 generates a contact sharing request, and transmits the contact sharing request to a desired server, for example, the CAB AB App. Usage 112 or the CAB PCC App. Usage 114, through an XDM Agent. A corresponding App. Usage that receives the contact sharing request sends the data to be shared to the receiver based on an XDM forward mechanism. 4-2) When the receiver is not a CAB user, the contact share function 105-3 receives data from, for example, the CAB AB App. Usage 112 or the CAB PCC App. Usage 114, transfers the received data to a CAB interworking function 105-4, requests format translation of the data into a legacy format, and sends the same to the receiver through a messaging enabler which is not illustrated in the drawings.
4. Contact Search
In a case of a contact search function, 1) the CAB client 100 sends a contact search request for its AB or PCC or an AB or a PCC of a different domain by passing through an aggregation proxy 115/search proxy 120 of an XDM enabler. 2) Then, the contact search request is routed to a corresponding App. Usage by the search proxy 115, and the corresponding App. Usage transfers a search result to the CAB client 100. 3) Also, the CAB client 100 changes the contact search request into an external search request through the interworking function 105-4 in a case of an external directory search, sends the external search request to an external directory, changes an external search result received through the interworking function 105-4 again into a standard XML search result, and transfers the standard XML search result to the CAB client 100.
5. Fetch an External Address Book from a Non-CAB System
In a case of the function, 1) the CAB client 100 sends an XCAP request for an importance of non-CAB data to the CAB FH App. Usage 118. 2) The CAB FH App. Usage 118 adds information obtained from the XCAP request, for example, a non-CAB source, a credential, and a scheduled interval, to a CAB feature Handler. 3) The CAB FH App. Usage 118 informs the interworking function 105-4 of the CAB server 105, of a change of a document caused by the adding operation to the CAB feature Handler. 4) The interworking function 105-4 obtains information associated with non-CAB address book data and stores the information in the CAB AB App. Usage 112 based on a CAB user preference, and instructs the CAB client 100 to start AB synchronization.
One of the methods proposed for restoring personal information provided based on a CAB service is to transfer a personal information restoring request to a CAB XDM server based on a modification history information document so as to change a corresponding document into a previous version.
Referring to
In operation 225, a CAB user who obtains the modification history information document through the CAB client block 200 may determine a document version information value (E-tag) for restoring the document to a previous version, based on the modification history information document. In operation 230, the CAB client block 200 transfers an XDCP restoration request including the previous document version information value (E-tag) to the CAB PCC Application Usage block 205. In operation 235, the CAB PCC Application Usage block 205 restores the modification history information document to the previous version corresponding to the previous document version information value. In operation 240, the CAB PCC Application Usage block 205 transmits the response message (200 OK) to the CAB client block 200.
As described above, when restoration of personal information is requested based on a modification history information document, the following problems may exist. Particularly, a cumbersome process for obtaining a PCC modification history document is required to obtain a previous document version information value. Also, the CAB user has inconvenience in that the CAB user needs to select a directly previous document version information value from a PCC modification history document. When the CAB user desires to determine a previous document version a few times, the CAB user needs to obtain a number of PCC modification history documents corresponding to a number of times of determination, which is inefficient.
Due to the above problems, a CAB enabler requires a method that enables a CAB user to more effectively restore (Undo) personal information such as changes (modification, addition, and deletion) applied in a PCC.
Therefore, the disclosure defines a personal information restoration request to include a current version information value of a personal information XML document and information associated with a number of times of restoration. A method that may enable a user to effectively manage personal information may be provided by providing a method in which a server restores a document of a previous version in response to the personal information restoration request as defined above.
In particular, according to an embodiment of the present disclosure, there is provided a data transceiving method and system that may provide a high-speed communication service without a waste of resources, power, or memory in a communication system that supports a variety of types of communication services. Also, a data transceiving method and system for providing a CAB service to a user may be provided in the communication system.
In particular, embodiments of the present disclosure assume a case of restoring (undo) PCC information stored in a storage unit in a CAB system to a directly previous version of a current version. In this case, a personal information restoration request, including a current version information value of a personal information eXtensible markup language (XML) document corresponding to the PCC information and information associated with the number of times of restoration, is transmitted to a CAB PCC App. Usage in a CAB XDM server. The CAB PCC App. Usage block restores the personal information XML document of the current version to a document of a previous version of the current version information value obtained through the received personal information restoration request, a few times corresponding to the information associated with the number of times of restoration. A modification history information document of the personal information XML document before restoration is deleted, and a document of the restored previous version is stored. Subsequently, the document of the restored previous version is provided to a user as a result value of the restoration request and thus, an effective personal information managing method may be provided to a CAB user. Hereinafter, descriptions of embodiments of the present disclosure may be applied to the communication system described in
Hereinafter, a first embodiment of the present disclosure provides a new personal information restoration method (XDCP Undo) that includes a current version information value of a personal information XML document that is to be restored based on a method of restoring a personal information document to a directly previous version, and information associated with a number of times of restoration.
Referring to
Referring to
In particular, an ‘<current-etag>’ element indicates a current version information value of a personal information XML document of a user. A ‘<number-of-undo>’ element indicates information associated with a number of times of restoration of a personal information XML document required by a CAB user. The ‘<number-of-undo>’ element is an optional value, and when the element is not included in a corresponding <undo> element, restoration of a personal information XML document one time is regarded as a default value. A maximum number of times of restoration may be managed based on a policy of a service provider.
In operation 320, the CAB PCC App. Usage block 305 that receives the XDCP Undo as defined above performs the following procedure based on a document recognition value (XCAP Uniform Resource Indication (URI)), current-E-tag, and number-of-undo obtained from the XDCP Undo. First, the CAB PCC App. Usage block 305 checks a validity of <current-etag>, and although not illustrated, transfers an error message (HTTP 409 “Conflict”) to the CAB client block 300 when it is invalid.
The CAB PCC App. Usage block 305 restores the personal information XML document to a previous version of the current-E-tag, a few times corresponding to number-of-undo. Although not illustrated, the CAB PCC App. Usage block 305 deletes a modification history document of the personal information XML document from PCC history documents stored in the PCC history document block 315. In operation 325, the CAB PCC App. Usage block 305 transfers, to the CAB Client block 300, an XDCP response indicating a result of the restoration.
Hereinafter, a second embodiment of the present disclosure provides a modified personal information restoration method (XDCP Restore) that includes a current version information value of a personal information XML document that is to be restored based on a method of restoring a personal information document to a directly previous version, and information associated with a number of times of restoration. In a case of the second embodiment of the present disclosure, the method may enable restoration to a previous version and restoration to a predetermined version designated by a user.
Referring to
In particular, a ‘type’ property is a value indicating a property of an <restore> element. Here, ‘undo’ that requests restoration of a personal information document to a directly previous version and ‘restore’ that requests restoration of a document to a predetermined version selected by a user may be defined. A <back-to-etag>’ element includes an information value of a document version when the user requests restoration of a document to a predetermined version selected by the user. In this example, according to the second embodiment of the present disclosure, the ‘type’ property is ‘undo’ and thus, ‘<back-to-etag>’ having a property of the <restore> element may not be included. That is, the <back-to-etag> element is an optional element. A ‘<current-etag>’ element indicates a current version information value of a personal information XML document of the user. A ‘<number-of-undo>’ element is an optional element, and indicates information associated with a number of times of restoration desired by the user. The ‘<number-of-undo>’ element is an optional value, and restoration one time is regarded as a default value when it is not included in a corresponding <undo> element. A maximum number of times of restoration may be managed by a policy of a service provider.
In operation 525, the CAB PCC App. Usage block 505 that receives the XDCP Restore request as defined above may perform the following procedure based on a document recognition value (XCAP URI), type information, <current-etag>, and <number-of-undo> obtained from the XDCP Restore request. For example, in
When it is determined that the property of ‘type’ is ‘undo’ from the XDCP Restore request, the CAB PCC App. Usage block 505 restores the personal information XML document to a previous version of the current-E-tag, a few times corresponding to <number-of-undo>. Although not illustrated, the CAB PCC App. Usage block 505 deletes a modification history document of the personal information XML document from PCC history documents stored in the PCC history document block 515. In operation 530, the CAB PCC App. Usage block 505 transfers, to the CAB Client block 500, an XDCP response indicating a result of the restoration.
Although the embodiments of the present disclosure provide a restoration method of restoring, to a previous version of a current version, a personal information XML document in which an error occurs from among personal information XML documents stored in a CAB system, the XDCP Undo and the modified XDCP Restore defined in the embodiments of the present disclosure may be equivalently applied to an XML document managing system.
Referring to
The controller 705 performs a control so that the message generating unit 715 generates a personal information restoration request message including a current version information value of a personal information XML document to be restored and information associated with a number of times of restoration according to an embodiment of the present disclosure. In particular, the message generating unit 715 generates XDCP Undo including <undo> elements or an XDCP Restore including <restore> elements as defined in
Although specific exemplary embodiments have been described in the detailed description of the present disclosure, various modifications may be made without departing from the scope of the present disclosure. Thus, the scope of the present disclosure shall not be determined merely based on the described exemplary embodiments and rather determined based on the accompanying claims and the equivalents thereto.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2012-0075798 | Jul 2012 | KR | national |
