SYSTEM AND METHOD FOR SELF-EXPIRING DATA CONTENT

Abstract

A system and method for supporting self-expiring data content. In accordance with an embodiment, a data record can be associated with a future expiration date and/or time, which can be specified as either an absolute date or time, or a relative date or time. When the expiration date and/or time is reached, the data record and its associated data are automatically deleted from the system. Depending on the particular implementation, the deletion can be automatic or provide some form of confirmation or acknowledgement. In accordance with an embodiment, a user inputting the data can control the record's expiration date, such that data is only retained in the system for as long as the user reasonably expects the data to be useful to them. For example, in a mobile phone contacts implementation, a user can attach an expiration date to a particular contacts data record, and that record will only remain in their mobile phone for that desired period of time.

Description

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

FIELD OF INVENTION

Embodiments of the invention are generally related to data processing, and are particularly related to a system and method for supporting self-expiring data content.

BACKGROUND

As computer systems have become increasingly powerful and found utility in almost every aspect of modern life, a consequence of such growth is that the amount of data stored worldwide has similarly grown at an almost exponential rate. Databases must be continuously expanded to accommodate new data. Some of this data, such as brief personal messages, news stories, consumer transactions and advertisements, has value only contemporaneously, for a short period of time. Storing such data over the long-term provides negligible value, but in many instances storing the data, even if it means having to provide additional storage, is an easier task than trying to filter out unimportant information. This means that over time, many databases become bloated with unwanted, stale, and often inconsistent data. This is the general area that embodiments of the present invention are intended to address.

SUMMARY

Disclosed herein is a system and method for supporting self-expiring data content. In accordance with an embodiment, a data record can be associated with a future expiration date and/or time, which can be specified as either an absolute date or time, or a relative date or time. When the expiration date and/or time is reached, the data record and its associated data are automatically deleted from the system. Depending on the particular implementation, the deletion can be automatic or provide some form of confirmation or acknowledgement. In accordance with an embodiment, a user inputting the data can control the record's expiration date, such that data is only retained in the system for as long as the user reasonably expects the data to be useful to them. For example, in a mobile phone contacts implementation, a user can attach an expiration date to a particular contacts data record, and that record will only remain in their mobile phone for that desired period of time.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a system for supporting self-expiring data content, in accordance with an embodiment.

FIG. 2 shows a system for supporting self-expiring data content, in accordance with an alternative embodiment.

FIG. 3 shows a system for supporting self-expiring data content, in accordance with an alternative embodiment.

FIG. 4 illustrates the use of absolute record expiration date/times, in accordance with an embodiment.

FIG. 5 illustrates the use of relative record expiration date/times, in accordance with an embodiment.

FIG. 6 shows a flowchart of a method for supporting self-expiring data content, in accordance with an embodiment.

DETAILED DESCRIPTION

Disclosed herein is a system and method for supporting self-expiring data content. In accordance with an embodiment, a data record can be associated with a future expiration date and/or time, which can be specified as either an absolute date or time, or a relative date or time. When the expiration date and/or time is reached, the data record and its associated data are automatically deleted from the system. Depending on the particular implementation, the deletion can be automatic or provide some form of confirmation or acknowledgement. In accordance with an embodiment, a user inputting the data can control the record's expiration date, such that data is only retained in the system for as long as the user reasonably expects the data to be useful to them. For example, in a mobile phone contacts implementation, a user can attach an expiration date to a particular contacts data record, and that record will only remain in their mobile phone for that desired period of time.

Although generally described herein in the context of a database, with data records therein, the techniques described herein can be similarly used with other types of system and data storage, for example an enterprise email system with stored email messages, a web-based advertising system with stored advertisements, or a mobile device with stored contact information. The techniques are intended to be usable with storing any form of data storage system, and any form of data or information for which self-expiration of that data or information is desirable.

FIG. 1 shows a system for supporting self-expiring data content, in accordance with an embodiment. As shown in FIG. 1, the system 10 can include a database 16 or other form of data storage, within which database each data record A 22 can include a data portion 24 and an expiration date portion 26.

In accordance with an embodiment, whenever a new record is added to the database, say manually by a user, or automatically by a computer process, or as any other form of data input 30, the data 32 in the data input can be used to populate the data portion 36 of the record (e.g. record b 34), while any optionally specified expiration date 33 in the data input can be used to populate the expiration date portion 38 of the record. Depending on the particular implementation, if an expiration date is not specified as part of the data input, the system can automatically determine and associate a default expiration date with the record, prior to storing the record in the database; or in some implementations set no expiration date with that particular record.

As further shown in FIG. 1, over time, the system (either via the operating system, the database logic itself, or using a record-expiring process) periodically checks 40 each of its database records' expiration dates, to determine whether that record has expired. Time can be measured based on an actual clock value, or on another time-dependent count. At any particular system time 41, if the system determines that a particular record has reached its expiration date, i.e. has expired, then that record is deleted from the system. In accordance with an embodiment, record expiration dates can also be pushed to a stack, and popped off as system time progresses, to indicate that the corresponding record should be deleted.

Depending on the particular implementation, a confirmation-to-delete and/or acknowledgement-of-deletion message 42 can be communicated to the user or computer process to inform them the record will be/has been deleted; otherwise the deletion of expired records is essentially silent.

In accordance with various embodiments, instead of periodically checking each of the database records' expiration dates, to determine whether that record has expired, the system can use alternative methods to determine and delete expired records. For example, FIG. 2 shows a system for supporting self-expiring data content, in accordance with an alternative embodiment, wherein a deletion list 43 or similar set of information is maintained regarding records to-be-deleted and their expiration dates 44. As records to-be-deleted are added to the database, the deletion list is updated accordingly 45. As time progresses, the system can look to entries in the list for those records due to be expired, and delete 46 the record accordingly.

FIG. 3 shows a system for supporting self-expiring data content, in accordance with an alternative embodiment. As shown in FIG. 3, instead of deleting records one-by-one, in accordance with an embodiment, a periodic checking, deletion list, or other deletion mechanism 55, such as but not limited to the examples described above, can be used to determine groups of records to-be-deleted 50, 52, 54, and delete those in bulk, or as a group. In accordance with other embodiments other features can be employed, for example by considering a deletion buffer time during which the record is temporarily moved to a trash area, prior to being permanently deleted at some later point. The above are intended to be examples of various embodiments, and others may be developed within the spirit and scope of the invention.

In accordance with some implementations, it may be desirable to store each record with an absolute record expiration date/time, which indicates a particular point in time at which that record is considered expired and should be deleted. FIG. 4 illustrates the use of absolute record expiration date/times 60, in accordance with an embodiment. As shown in FIG. 4, depending on the particular implementation, an absolute expiration date can be again either specified as part of the data input 62, or the system can automatically determine and associate an absolute expiration date with the record, prior to storing the record in the database. Each data record C 63 can include a data portion 64 and an absolute expiration date portion 66. At any particular system time, if the system determines that the system time is greater than that particular record's absolute expiration date, then the system determines that record has expired and is deleted 68 from the system

In accordance with other implementations, it may be desirable to store each record with a relative record expiration date/time, which does not indicate a particular point in time at which that record is considered expired and should be deleted, but rather a desired lifetime that record should be allowed to persist within the system (such as a number of days, weeks, or years). FIG. 5 illustrates the use of relative record expiration date/times 70, in accordance with an embodiment. As shown in FIG. 5, depending on the particular implementation, an absolute expiration date can be again either specified as part of the data input 72, or the system can automatically determine and associate an absolute expiration date with the record, prior to storing the record in the database. Each data record D 73 can include a data portion 74, a record creation date portion 75, and a relative expiration date portion 76. At any particular system time, if the system determines that the system time, less the creation time, (i.e. the age of the record) is greater than that particular record's relative expiration date, then that record has expired and is deleted 78 from the system.

FIG. 6 shows a flowchart of a method for supporting self-expiring data content, in accordance with an embodiment. As shown in FIG. 6, in step 80, the system receives input of data to be stored in database, together with any optional user-specified expiration date. In step 82, the data input is stored as a record with an appropriate expiration date (specified as either an absolute or a relative date/time). In step 84, the system checks (e.g. using periodic checking, deletion list, or other mechanism) within the database and compares record expiration dates (e.g., by comparing system time with absolute expiration dates; or record ages with relative expiration dates). In step 86, any expired records and their associated data are automatically deleted when their expiration date is reached and determined by the system.

Example Use Cases

In accordance with an embodiment, a user inputting the data can control the record's expiration date, such that data is only retained in the system for as long as the user reasonably expects the data to be useful to them. For example, in a mobile phone contacts implementation, a user can attach an expiration date to a particular contacts data record, and that record will only remain in their mobile phone for that desired period of time. This type of use case can be useful, e.g. while vacationing, so that contacts required only during that vacation period (hotel concierge contacts, restaurant or museum contacts) are automatically deleted following the vacation. Additional use cases can be developed.

The present invention may be conveniently implemented using one or more conventional general purpose or specialized digital computers or microprocessors programmed according to the teachings of the present disclosure. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.

In some embodiments, the present invention includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.

The foregoing description of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalence.

Claims

1. A system for supporting self-expiring data content, comprising:

a database or other form of data storage, for storing a plurality of data records, wherein each data record includes a data portion and an expiration date portion;

wherein, whenever a new record is added to the database, as a data input, the data in the data input is used to populate the data portion of the record, while any optionally specified expiration date in the data input is used to populate the expiration date portion of the record; and

wherein, over time, the system periodically checks each of its database records' expiration dates, to determine whether that record has expired, and wherein at any particular system time, if the system determines that a particular record has reached its expiration date, then that record is deleted from the system.

2. The system of claim 1, wherein each record has an absolute record expiration date/time.

3. The system of claim 1, wherein each record has a relative record expiration date/time.

4. The system of claim 1, wherein if an expiration date is not specified as part of the data input, the system can automatically determine and associate a default expiration date with the record, prior to storing the record in the database, or set no expiration date with that particular record.

5. The system of claim 1, wherein the system is used within a mobile phone implementation, wherein a user can attach an expiration date to a particular data record, and that record will only remain in their mobile phone for that desired period of time.

6. A computer-based method of supporting self-expiring data content, comprising the steps of:

providing a database or other form of data storage, for storing a plurality of data records, wherein each data record includes a data portion and an expiration date portion;

whenever a new record is added to the database, as a data input, using the data in the data input to populate the data portion of the record, while any optionally specified expiration date in the data input is used to populate the expiration date portion of the record; and

periodically checking each of its database records' expiration dates, to determine whether that record has expired, and wherein at any particular system time, if it is determined that a particular record has reached its expiration date, then deleting that record.

7. The method of claim 6, wherein each record has an absolute record expiration date/time.

8. The method of claim 6, wherein each record has a relative record expiration date/time.

9. The method of claim 6, wherein if an expiration date is not specified as part of the data input, the system can automatically determine and associate a default expiration date with the record, prior to storing the record in the database, or set no expiration date with that particular record.

10. The method of claim 6, wherein the system is used within a mobile phone implementation, wherein a user can attach an expiration date to a particular data record, and that record will only remain in their mobile phone for that desired period of time.

11. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

providing a database or other form of data storage, for storing a plurality of data records, wherein each data record includes a data portion and an expiration date portion;

whenever a new record is added to the database, as a data input, using the data in the data input to populate the data portion of the record, while any optionally specified expiration date in the data input is used to populate the expiration date portion of the record; and

periodically checking each of its database records' expiration dates, to determine whether that record has expired, and wherein at any particular system time, if it is determined that a particular record has reached its expiration date, then deleting that record.

12. The non-transitory computer readable medium of claim 11, wherein each record has an absolute record expiration date/time.

13. The non-transitory computer readable medium of claim 11, wherein each record has a relative record expiration date/time.

14. The non-transitory computer readable medium of claim 11, wherein if an expiration date is not specified as part of the data input, the system can automatically determine and associate a default expiration date with the record, prior to storing the record in the database, or set no expiration date with that particular record.

15. The non-transitory computer readable medium of claim 11, wherein the system is used within a mobile phone implementation, wherein a user can attach an expiration date to a particular data record, and that record will only remain in their mobile phone for that desired period of time.