METHOD AND APPARATUS FOR SYNCHRONIZING FEED INFORMATION

• US 20080228945A1
• Filed: 09/10/2007
• Published: 09/18/2008
• Est. Priority Date: 03/12/2007
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: RYU, Won-ho, YOON, Seok-Hyun, RYU, Sung-ho
• Granted Patent: US 8,539,037 B2
• Time in Patent Office: Days
• US Class Current: 709/248
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A method and apparatus for synchronizing feed information are provided. A podcasting client includes a synchronization-processing unit which synchronizes first feed information acquired from a connected device with pre-stored second feed information, and a communication interface which transmits feed information of content that is podcast based on the synchronized feed information to the connected device.

Claims

1. A podcasting client comprising:

a synchronization-processing unit which synchronizes first feed information acquired from a connected device with second feed information; and

a communication interface which transmits feed information of content that is podcast based on the synchronized first feed information to the connected device.

2. The podcasting client of claim 1, wherein each of the first feed information and the second feed information comprise at least one of a time when a change of the feed information is generated, a cause of a change of the feed information, a changed item, and a change order number that indicates an order of change.

3. The podcasting client of claim 2, wherein the changed item comprises at least one of channel addition, channel deletion, feed collection, feed deletion, and feed reading.

4. The podcasting client of claim 1, wherein the synchronization-processing unit performs synchronization based on the first feed information and the second feed information if a first anchor including resultant information of synchronization of the connected device coincides with a second anchor including resultant information of synchronization of the podcasting client.

5. The podcasting client of claim 4, wherein the first anchor includes at least one of an identifier of the podcasting client, a change order number of a feed change log processed during a previous synchronization with the connected device among feed-change logs included in the first feed information, and a change order number of a feed change log processed during the previous synchronization with the connected device among the feed change logs included in the second feed information.

6. The podcasting client of claim 4, wherein the second anchor includes at least one of an identifier of the connected device, a change order number of a feed change log processed during a previous synchronization with the connected device among feed-change logs included in the first feed information, and a change order number of a feed change log finally processed during the previous synchronization with the connected device among feed-change logs included in the second feed information.

7. The podcasting client of claim 4, wherein the synchronization-processing unit aligns the first feed information and the second feed information based on a time when a change is generated, and performs synchronization work in an order with respect to the aligned feed information.

8. The podcasting client of claim 1, wherein the synchronization-processing unit copies the second feed information into the connected device if a first anchor including resultant information of synchronization of the connected device does not coincide with a second anchor including resultant information of synchronization of the podcasting client.

9. The podcasting client of claim 1, wherein the synchronization-processing unit generates an anchor that includes resultant information of synchronization of the first feed information and the second feed information, and stores the generated anchor in the connected device.

10. A device comprising:

a feed-change-log-management unit which generates a first feed change log in which a change of first feed information is recorded; and

a communication interface which receives from a podcasting client an anchor that includes resultant information of synchronization performed based on the first feed change log and a second feed change log in which a change of second feed information of the connected podcasting client is recorded.

11. The device of claim 10, wherein the anchor is identical to an anchor stored in the podcasting client.

12. A method of synchronizing feed information, the method comprising:

synchronizing, with second feed information, first feed information acquired from a connected device; and

transmitting, to the connected device, feed information of content that is podcast based on the synchronized first feed information.

13. The method of claim 12, wherein each of the first feed information and the second feed information comprise at least one of a time when a change of the feed information is generated, a cause of change, a changed item, and a change order number that indicates an order of change.

14. The method of claim 13, wherein the changed item comprises at least one of channel addition, channel deletion, feed collection, feed deletion, and feed reading.

15. The method of claim 12, wherein the synchronizing comprises performing synchronization based on the first feed information and the second feed information if a first anchor including resultant information of synchronization of the connected device side coincides with a second anchor.

16. The method of claim 15, wherein the first anchor includes at least one of an identifier of a podcasting client that participates in a previous synchronization with the connected device, a change order number of a feed change log processed during a previous synchronization with the device among feed-change log included in the first feed information, and a change order number of a feed change log processed during the previous synchronization with the device among feed-change log included in the second feed information.

17. The method of claim 15, wherein the second anchor includes at least one of an identifier of the connected device, a change order number of a feed change log processed during a previous synchronization with the connected device among feed-change log included in the first feed information, and a change order number of a feed change log processed during the previous synchronization with the connected device among feed-change log included in the second feed information.

18. The method of claim 15, wherein the synchronizing comprises:

aligning the first feed information and the second feed information based on a time when a change is generated; and

performing a synchronization work in an order with respect to the aligned feed information.

19. The method of claim 12, wherein the synchronizing comprises copying the second feed information to the connected device if a first anchor including resultant information of synchronization of the connected device does not coincide with a second anchor.

20. The method of claim 12, wherein the synchronizing comprises:

generating an anchor that includes resultant information of synchronization of the first feed information and the second feed information; and

storing the generated anchor in the connected device.

21. A method of synchronizing feed information, the method comprising:

generating a first feed change log in which a change of first feed information is recorded; and

storing an anchor that includes resultant information of synchronization performed based on the first feed change log and a second feed change log in which a change of second feed information of a connected podcasting client is recorded.

22. The method of claim 21, wherein the anchor is identical to an anchor stored in the podcasting client.