Browse Prior Art Database

Automatic Time-Based Purging of Code on a Mobile Device

IP.com Disclosure Number: IPCOM000130503D
Publication Date: 2005-Oct-25
Document File: 2 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

Mobile devices generally have limited space available for applications and data. As applications become more sophisticated and complex they inevitably take up more and more space, thus reducing the amount of space available for other applications and data. In addition, the more feature-rich an application is, the more likely it is that the application contains features that are not desirable to all users. Even if an application contains features that are not desirable to a user, the user is unable to eliminate the undesirable features from the device and free up valuable space that could be used for additional applications and data. In addition, users of mobile devices are responsible for manually removing code from the device when they no longer need it or in order to free up space for other applications or data storage. There is no automatic mechanism available that would allow code (features, entire applications, etc.) to be removed automatically after a period of time if they have not been used or when space is needed for more data storage. The invention keeps track of the user's usage of applications and features within those application in order to determine when components were last accessed by the user and how often they have been accessed. This allows the device to make intelligent decisions regarding the removal of these components. Using this information, the system can inform the user when features or applications have become stale due to lack of use and give the user the option of removing the components or leaving them on the system. If the user elects to remove a component, it is purged from the device automatically. The user would be able to specify parameters for this automatic purging, such as the length of time before a component is considered stale, whether or not to prompt the user before purging, etc. It might also make sense to mark certain feature or applications as mandatory so that they cannot expire or be deleted. The expiration feature may also be controlled by IT policy. When coupled with a wireless install on first use mechanism this forms a powerful mechanism for the automatic management of code on a mobile device. For example, if the user doesn't use the Global Address Lookup feature in Address Book, it could be removed from the device freeing up valuable space for data or other applications. This system can also be used when the device is running low on space for data storage. When this occurs, the system can determine which application or features have been infrequently used and provide the user with the option of purging old data or stale components. Again, the user would be able to configure various aspects of this mechanism. With this invention, the user no longer has to worry about keeping track of which applications or features they use and manually purging stale components. The system takes care of the entire process automatically. The mobile device already takes care of purging stale messages and calendar appointments after a certain time frame has elapsed or when additional data storage space is required. This invention takes this philosophy to the next level.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 52% of the total text.

AUTOMATIC TIME-BASED CODE PURGING

Automatic Time-Based Purging of Code on a

Mobile

Device

Disclosed Anonymously

Mobile devices generally have limited space available for applications and data. As applications become more sophisticated and complex they inevitably take up more and more space, thus reducing the amount of space available for other applications and data. In addition, the more feature-rich an application is, the more likely it is that the application contains features that are not desirable to all users. Even if an application contains features that are not desirable to a user, the user is unable to eliminate the undesirable features from the device and free up valuable space that could be used for additional applications and data.

In addition, users of mobile devices are responsible for manually removing code from the device when they no longer need it or in order to free up space for other applications or data storage. There is no automatic mechanism available that would allow code (features, entire applications, etc.) to be removed automatically after a period of time if they have not been used or when space is needed for more data storage.

The invention keeps track of the user's usage of applications and features within those application in order to determine when components were last accessed by the user and how often they have been accessed. This allows the device to make intelligent decisions regarding the removal of these components.

Using this information, the system can inform the user when features or applications have become stale due to lack of use and give the user the option of removing the components or leaving them on the system. If the user elects...