File system management with user-definable functional attributes stored in a token action log

• US 20040064434A1
• Filed: 05/22/2003
• Published: 04/01/2004
• Est. Priority Date: 09/30/2002
• Status: Active Grant

• Current Assignee: Scott E. Sampson
• Original Assignee: Scott E. Sampson
• Inventors: Sampson, Scott E.
• Granted Patent: US 6,804,687 B2
• Time in Patent Office: Days
• US Class Current: 707/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/389 Keeping log of transactions for guaranteeing non-repudiation of a transaction
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A file system or other system that manages information entities includes a subsystem to store one or more tokens, as well as a token action log to associate each token with a customizable set of one or more actions, where each token is to trigger the associated set of one or more actions in response to accompanying a file-system/information entity that experiences an event. The file system also includes a token log manager, which initiates the appropriate actions corresponding to file-system entities that experience an event.

Claims

1. A method comprising:

storing one or more tokens within a file system;

associating each token with one or more customizable sets of one or more actions in a token action log, wherein each token is to trigger the associated set of one or more actions in response to accompanying a file-system entity that experiences an event designated for those one or more actions;

associating specific tokens with specific file-system entities.

2. The method of claim 1, wherein the file-system is a system that stores an organized of information entities.

3. The method of claim 1, wherein the file-system entities are one or more of files, directories, links to files, links to directories, data structures, data structure elements, images, video data, audio data, messages, and message attachments.

4. The method of claim 1, wherein storing one or more tokens includes receiving a configuration from a system operator of a specific token.

5. The method of claim 4, wherein storing one or more tokens includes receiving a configuration from a system operator of a configuration of a second specific token.

6. The method of claim 1, wherein storing one or more tokes includes receiving the configuration of the one or more tokens from an external source.

7. The method of claim 1, wherein storing one or more tokes includes one or more of recording the token in system memory, recording the token on a system storage device, and recording the token on an external device.

8. The method of claim 1, wherein the event is selected from the set consisting of deleting the file-system entity, opening the file-system entity, copying the file-system entity, printing the file-system entity, receiving the file-system entity over a network connection, sending the file-system entity over a network connection, backing up the file-system entity, moving the file-system entity, executing the file-system entity, creating the file-system entity, modifying the file-system entity, and associating a token with the file-system entity.

9. The method of claim 1, further comprising:

associating one or more time dependent alarms with one or more tokens and one or more token actions as recorded in the token action log.

10. The method of claim 9, wherein the event comprises passing a designated time as indicated by one or more alarms associated with one or more tokens.

11. The method of claim 1, wherein the token action log is stored in the file system.

12. The method of claim 1, wherein the one or more tokens are stored in the file system, and wherein the token action log is stored outside of the file system.

13. The method of claim 1, wherein the token action log is affiliated with a given user of the file system.

14. The method of claim 1, wherein the token action log is affiliated with a given group of users of the file system.

15. The method of claim 1, wherein specific entries in the token action log are affiliated with a given user of the file system.

16. The method of claim 1, wherein specific entries in the token action log are affiliated with a given group of users of the file system.

17. The method of claim 1, wherein associating specific tokens to specific entities within the file system comprises including one or more tokens in a set of extended attributes pertaining to specific file system entities.

18. The method of claim 1, wherein associating specific tokens to specific file-system entities comprises recording the token in meta-information which is stored with the file-system entities.

19. The method of claim 1, wherein associating specific tokens to specific file-system entities comprises recording in a data structure which tokens are considered associated to specific entities within the file system.

20. The method of claim 1, further comprising:

detecting an event involving a file-system entity associated with a specific token previously stored within the file system;

searching the token action log for a set of one or more actions associated with the specific token; and

executing the set of one or more actions.

21. The method of claim 20, wherein the file-system entity is accompanied by a second specific token previously stored within the file system, the method further comprising:

searching the token action log for a second set of one or more actions associated with the second specific token; and

executing the second set of one or more actions.

22. The method of claim 1, further comprising:

detecting an event that pertains to a specific token previously recorded in the token action log;

identifying entities within the file system that are associated with the specific token pertaining to the detected event;

searching the token action log for a set of one or more actions associated with the specific token; and

executing the set of one or more actions for each of the identified files-system entities.

23. The method of claim 1, wherein at least one action includes conditional logic.

24. The method of claim 1, wherein the specific token is accompanied by a set of parameters, and wherein executing the set of one or more actions comprises calling a function with the set of parameters.

25. The method of claim 20, wherein the specific token is associated with one or more conditions for use, and wherein searching the token action log includes verifying that the one or more conditions for use are satisfied.

26. The method of claim 1, wherein at least one token is associated with an indication of an intended purpose for the at least one token.

27. The method of claim 1, wherein associating the one or more tokens to specific file-system entities comprises associating multiple tokens with different purposes to two or more file-system entities.

28. The method of claim 1, wherein associating the one or more tokens to specific entities comprises associating multiple tokens with different purposes to one file-system entity.

29. The method of claim 1, further comprising:

associating two or more actions in the token action log to different specific events.

30. The method of claim 1, wherein at least one action in the token action log includes a reference to one or more standard action sets.

31. A system comprising:

a token action log to associate each token with a customizable set of one or more actions in a token action log, wherein each token is to trigger the associated set of one or more actions in response to accompanying a file-system entity that experiences an event; and

a token distributor to attach tokens to specific entities within the file system.

32. The system of claim 31, wherein the event is selected from the set consisting of deleting the file-system entity, opening the file-system entity, copying the file-system entity, printing the file-system entity, emailing the file-system entity, backing up the file-system entity, moving the file-system entity, executing the file-system entity, creating the file-system entity, modifying the file-system entity, and associating a token with the file-system entity.

33. The system of claim 31, wherein the event comprises passing a designated time.

34. The system of claim 31, further comprising:

a subsystem to detect a file-system entity experiencing an event, which file-system entity is accompanied by a specific token previously stored in the token action log;

a lookup module to search the token action log for a set of one or more actions associated with the specific token; and

an action manager to execute the set of one or more actions.

35. The system of claim 34, wherein the file-system entity is accompanied by a second specific token previously stored within the file system, and wherein the lookup module is to search the token action log for a second set of one or more actions associated with the second specific token;

and wherein the action manager is to execute the second set of one or more actions.

36. The system of claim 31, further comprising:

a subsystem to detect a file-system entity experiencing an event, which file-system entity is accompanied by a specific token previously stored within the file system;

a lookup module to search the token action log for a set of one or more time-lagged actions associated with the specific token; and

an alarm event manager to initiate the actions after the designated time lag.

37. The system of claim 31, further comprising:

a subsystem to detect an event pertaining to one or more tokens recorded in the token action log;

a search module to identify file-system entities associated with the one or more tokens;

38. The system of claim 37, further comprising:

a processing module to process the identified file-system entities according to actions recorded in the token action log corresponding to the one or more tokens.

39. The system of claim 31, wherein each token corresponds to a group of file-system entities.

40. The system of claim 34, wherein the detection subsystem, in response to encountering a file-system entity without a token, associates the file-system entity with a designated token.

41. The system of claim 31, further comprising:

a subsystem to detect a file-system entity experiencing an event, which file-system entity is not accompanied by a token previously stored in the token action log;

a lookup module to search the token action log for a set of one or more actions associated with file-system entities that are not accompanied by a token; and

an action manager to execute the set of one or more actions.

42. The system of claim 34, wherein an action executed by the action manager is to attach one or more tokens to one or more entities already in the file system.

43. The system of claim 34, wherein at least one action is selected from the group consisting of tagging the file-system entity with an identifier, deleting the file-system entity, moving the file-system entity, activating a device, sending a file to a designated recipient, sending the file-system entity to a designated recipient, audibly alerting an operator of the file system, visually alerting an operator of the file system, extracting information from the file-system entity, modifying the token action log, generating a new token, executing a program, and setting an option in a program acting on the file system entity.

44. The system of claim 34, wherein at least one action includes conditional logic.

45. The system of claim 34, wherein the specific token is accompanied by a set of parameters, and wherein the action manager is to execute the set of one or more actions by calling a function with the set of parameters.

46. The system of claim 34, wherein the specific token is associated with conditions for use, and wherein the file system is to perform one or more operations in response to the conditions for use being satisfied.

47. The system of claim 31, further comprising:

recording in a searchable data structure which tokens have been assigned to which entities within the file system.

48. The system of claim 47, further comprising:

identifying within the searchable data structure the entities that have a specified token assigned to them.

49. The system of claim 48, further comprising:

presenting the identified entities to the file system operator.

50. The system of claim 48, further comprising:

performing a specific set of one or more actions on the identified file system entities.

51. A file-system apparatus comprising:

means for storing one or more tokens within a file system;

means for associating each token with a customizable set of one or more actions in a token action log, wherein each token is to trigger the associated set of one or more actions in response to accompanying a file-system entity that experiences an event,

means for associating specific tokens to specific entities within the file system.

means for detecting an event involving a file-system entity accompanied by a specific token previously stored within the file system;

means for searching the token action log for a set of one or more actions associated with the specific token; and

means for executing the set of one or more actions.

52. A computer program product comprising program code for performing a method, the method comprising:

storing one or more tokens within a file system;

associating each token with a customizable set of one or more actions in a token action log, wherein each token is to trigger the associated set of one or more actions in response to accompanying a file-system entity that experiences an event,

associating specific tokens to specific entities within the file system.

detecting an event involving a file-system entity accompanied by a specific token previously stored within the file system;

searching the token action log for a set of one or more actions associated with the specific token; and

executing the set of one or more actions.