Content management system and method for portable device

• US 20070288485A1
• Filed: 04/24/2007
• Published: 12/13/2007
• Est. Priority Date: 05/18/2006
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Kim, Joon Oo, Oh, Yun Je, Kim, Chul Seung, Bae, Young Kyu, Shin, Ho Chul
• Granted Patent: US 8,234,247 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/16 File or folder operations, e.g. details of user interfaces specifically adapted to file systems
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs

Abstract

The present invention relates to a content management system and method of content management on a portable device. The content management system of the present invention includes a storage unit which stores at least one content file, a content list manager which creates a content list of contents files satisfying at least one monitoring condition and manages the content list on the basis of events occurring in the storage unit, and a monitoring unit which monitors the events occurring in the storage unit and transmits information on the events to the content list manager.

Claims

1. A content management system comprising:

a storage unit which stores at least one content file;

a content list manager which creates a content list of v files satisfying at least one monitoring condition and manages the content list on the basis of events occurring in the storage unit; and

a monitoring unit which monitors the events occurring in the storage unit and transmits information on the events to the content list manager.

2. The content management system of claim 1, wherein the content list manager transmits a monitoring command having the monitoring condition to the monitoring unit, and the monitoring unit starts monitoring the events in response to the monitoring command.

3. The content management system of claim 2, wherein the monitoring unit includes:

an agent, which interfaces between the content list manager and the monitoring unit, to receive the monitoring command from the content list manager and transmit the information on the events to the content list manager; and

a monitoring command executer which monitors the events in accordance with the monitoring command received from the agent and transmits a monitoring result to the agent.

4. The content management system of claim 2, wherein the monitoring condition includes at least one of a file extension for distinguishing types of contents and a file path.

5. The content management system of claim 4, wherein the monitoring unit determines whether the event is an addition or deletion event of a content file of which file extension belongs to the monitoring condition, when the monitoring condition is the file extension.

6. The content management system of claim 4, wherein the monitoring unit determines whether the event is an addition or deletion event of a content file of which file path belongs to the monitoring condition, when the monitoring condition is the file path.

7. The content management system of claim 6, wherein the addition event stores the content file satisfying the monitoring condition into the storage unit.

8. The content management system of claim 7, wherein the addition event copies the content file satisfying the monitoring condition and further stores the content file with a different file name.

9. The content management system of claim 6, wherein the deletion event moves the content file satisfying the file path to another file path.

10. The content management system of claim 1, wherein the event includes a content identifier, a file path, and an event identifier of the content file to which the event occurs.

11. The content management system of claim 10, wherein the contents list manager requests detailed information on the content file to the monitoring unit on the basis of the event and updates the content list on the basis of the detailed information received from the monitoring unit.

12. A content management method comprising the steps of:

registering at least one monitoring condition;

creating a content list of content files satisfying the monitoring condition;

receiving an event generated when status of the content file storage is changed; and

updating the content list on the basis of the event.

13. The content management method of claim 12, wherein the monitoring condition includes at least one of a file extension and a file path of the content file.

14. The content management method of claim 12, wherein the event includes a content identifier, a file path, and an event identifier of the content file to which occurs.

15. The content management method of claim 12, wherein the step of receiving the event further comprises the steps of:

transferring a monitoring command including the monitoring condition; and

receiving the event in response to the monitoring occurrence information.

16. The content management method of claim 15, wherein the step of receiving event further comprises the step of:

determining whether the event is an addition or deletion event of a content file of which file extension belongs to the monitoring condition, when the monitoring condition is the file extension.

17. The content management method of claim 15, wherein the step of receiving the event comprises the step of:

determining whether the event is an addition or deletion event of a content file of which file path belongs to the monitoring condition, when the monitoring condition is the file path.

18. The content management method of claim 17, wherein the addition event stores the content file satisfying the monitoring condition into the storage unit.

19. The content management method of claim 18, wherein the addition event copies the content file satisfying the monitoring condition and stores the content file with a different file name.

20. The content management method of claim 17, wherein the deletion event moves the content file satisfying the file path to another file path.

21. The content management method of claim 12, wherein the event includes a content identifier, a file path, and an event identifier of the content file to which the event occurs.