320 results about "Retention period" patented technology

A privacy impact assessment is performed to determine and implement privacy requirements for any information resource that uses personal information. Data may be collected and analyzed regarding the information resource and the personal information, and applicable laws, regulations, and policies may be considered to determine privacy requirements. Such requirements may include, for example, access controls, information retention periods, systems requirements, and risk assessments.

A privacy impact assessment is performed to determine and implement privacy requirements for any information resource that uses personal information. Data may be collected and analyzed regarding the information resource and the personal information, and applicable laws, regulations, and policies may be considered to determine privacy requirements. Such requirements may include, for example, access controls, information retention periods, systems requirements, and risk assessments.

This invention provides a specified retention date within a data set that is locked against deletion or modification within a WORM storage implementation. This retention date scheme does not utilize any proprietary application program interfaces (APIs) or protocols, but rather, employs native functionality within conventional file (or other data containers, data sets or block-based logical unit numbers) properties available in commonly used operating systems. In an illustrative embodiment, the retention date / time is calculated by querying the file's last-modified time prior to commit, adding the retention period to this value and thereby deriving a retention date after which the file can be released from WORM. Prior to commit, the computed retention date is stored in the file's “last access time” property / attribute field, or another metadata field that remains permanently associated with the file and that, in being used for retention date, does not interfere with file management in a WORM state. Since this field is not utilized in a WORM context, it can be adapted to store this date. Once stored, the retention date in this field is locked against modification. Where extension (never reduction) of a retention period is desired, the last access time field be updated, wherein the new retention period is added to the existing last access time value to derive a new, later retention date for the file. Upon expiry of the retention date, the system allows deletion of the expired WORM file / data set.

Provided are a method, system, and program for receiving a request to remove a record. A determination is made as to whether a state associated with the record includes at least one hold state and whether the state associated with the record includes at least a retention period that has not expired. The request to remove the record is denied in response to determining that the state associated with the record includes at least one of at least one hold state and one retention period that has not expired.

Methods and apparatus are described for collecting and storing large volumes of time series data. For example, such data may comprise metrics gathered from one or more large-scale computing clusters over time. Data are gathered from resources which define aspects of interest in the clusters, such as nodes serving web traffic. The time series data are aggregated into sampling intervals, which measure data points from a resource at successive periods of time. These data points are organized in a database according to the resource and sampling interval. Profiles may also be used to further organize data by the types of metrics gathered. Data are kept in the database during a retention period, after which they may be purged. Each sampling interval may define a different retention period, allowing operating records to stretch far back in time while respecting storage constraints.

Provided are a method, system, and program for receiving a request to remove a record. A determination is made as to whether a state associated with the record includes at least one hold state and whether the state associated with the record includes at least a retention period that has not expired. The request to remove the record is denied in response to determining that the state associated with the record includes at least one of at least one hold state and one retention period that has not expired.

Techniques for adjusting the frequency of data backups and initiating event-driven backups in a storage system are disclosed herein. In one embodiment, a self-adjusting backup frequency, known as a “Change Rate Objective,” is defined to conduct or delay backups for one or more volumes in the storage system on the basis of an associated policy value. The Change Rate Objective may be tied to one or more business or data activity events, such as the amount and type of data changes since a last backup. The storage system may also be tailored to conduct or delay full or incremental backups on the basis of a Change Rate Objective that measures whether a full or incremental or differential backup is more appropriate. Various data or system failures, or data or business events may also be used to adjust the retention periods of continuous data protection (CDP) data and delay a rollup of CDP data.

When sending electronic mail, a user of a mobile phone can add predetermined conditions (or data) to the electronic mail. When the mobile phone receives electronic mail with the conditions added thereto, the received electronic mail can be displayed and deleted according to the aforementioned conditions. The receiver of the electronic mail cannot freely dispose of the received electronic mail. The added conditions are, for example, display date and time, display period, number of displays, retention period.

The present invention includes embodiments of systems and methods for increasing the operational efficiency and extending the estimated operational lifetime of a flash memory storage device (and its component flash memory chips, LUNs and blocks of flash memory) by monitoring the health of the device and its components and, in response, adaptively tuning the operating parameters of flash memory chips during their operational lifetime, as well as employing other less extreme preventive measures in the interim, via an interface that avoids the need for direct access to the test modes of the flash memory chips. In an offline characterization phase, “test chips” from a batch of recently manufactured flash memory chips are used to simulate various usage scenarios and measure the performance effects of writing and attempting to recover (read) test patterns written with different sets of operating parameters over time (simulating desired retention periods).

A method for storing content on a storage system wherein the content is defined an associated retention period. The retention period prescribes a fixed amount of time that the content will be stored without the possibility of deletion. After the retention period expires, the content and all metadata associated with the content can be deleted from the storage system.

Memory devices and / or methods of managing memory data errors are provided. A memory device detects and corrects an error bit of data read from a plurality of memory cells, and identifies a memory cell storing the detected error bit. The memory device assigns a verification voltage to each of the plurality of first memory cells, the assigned verification voltage corresponding to the corrected bit for the identified memory cell, the assigned verification voltage corresponding to the read data for the remaining memory cells. The memory device readjusts the data stored in the plurality of memory cells using the assigned verification voltage. Through this, it is possible to increase a retention period of the data of the memory device.

A records management system and method includes a file plan that has one or more segments associated with compliance data. Data stored in these segments of the file plan have a mandatory minimum retention period during which they cannot be modified or deleted. Additionally, the information about the mandatory minimum retention period may not be altered or removed.

Disclosed are a method, system, program and data structure for implementing a records retention policy by storing selected files for designated lengths of time and then deleting them only when that time has passed. Embodiments of the invention perform this function in an efficient database-free manner. Embodiments of the invention can perform this function by utilizing existing storage directory tree functionality provided by any computer operating system organized under a retention directory coupled with a mechanism for preventing unauthorized deletions of files designated for retention. Expiration of retained files may be managed through directory structure using directory names corresponding to expiration dates determined from identified retention periods for retained files. Files may be further protected from erasure by a kernel mode process which prevents erasure of any files contained in the retention directory.

Embodiments of the present invention relate to methods and apparatuses serving to provide assurance that healthcare providers will receive payment for services rendered. In one embodiment, a payment card (or other portable consumer device) provides an extended authorization hold period (for example up to 21 days). This hold period allows the healthcare provider to request authorization for payment from the patient's credit, debit, FSA, HRA, or HSA payment card, submit the insurance claim, and then upon receipt of a health insurance carrier's Explanation of Benefits (EOB) within the hold period, submit for settlement only that amount actually due from the patient. In accordance with an alternative embodiment, pending receipt of the EOB from the insurer, the healthcare provider flags a transaction in a point-of-sale (POS) terminal device or server for storage and delayed submittal over an electronic payment network. Embodiments in accordance with the present invention are particularly applicable to payment of claims in healthcare plans following adjudication by a payer.

One embodiment is a method and apparatus for modifying retention periods in a storage system, in which previously defined retention periods for units of data may be reduced. In another embodiment, the retention period of a unit of data may be modified in response to the occurrence of an event by renewing previously defined retention periods until the occurrence of the event is detected. If the occurrence of the event is detected, a retention period associated with that event may be established for the unit of data. In yet another embodiment, retention classes are used to define retention periods for units of data so that the retention period of a unit of data may be modified without modifying the unit of data itself. In a further embodiment, a request to the storage system to reduce a retention period includes authentication information that the storage system may use to verify the request.

This invention provides a specified retention date within a data set that is locked against deletion or modification within a WORM storage implementation. This retention date scheme does not utilize any proprietary application program interfaces (APIs) or protocols, but rather, employs native functionality within conventional file (or other data containers, data sets or block-based logical unit numbers) properties available in commonly used operating systems. In an illustrative embodiment, the retention date / time is calculated by querying the file's last-modified time prior to commit, adding the retention period to this value and thereby deriving a retention date after which the file can be released from WORM. Prior to commit, the computed retention date is stored in the file's “last access time” property / attribute field, or another metadata field that remains permanently associated with the file and that, in being used for retention date, does not interfere with file management in a WORM state. Since this field is not utilized in a WORM context, it can be adapted to store this date. Once stored, the retention date in this field is locked against modification. Where extension (never reduction) of a retention period is desired, the last access time field be updated, wherein the new retention period is added to the existing last access time value to derive a new, later retention date for the file. Upon expiry of the retention date, the system allows deletion of the expired WORM file / data set.

Disclosed are embodiments of a system and method for establishing and managing document retention policy in a distributed computing environment. One embodiment comprises the steps of loading documents into a database as individual components or items; establishing a custodian for each document instance; categorizing its content into a plurality of categories; assigning retention periods to the content by category; and continuously monitoring retention policies according to the assigned retention periods. Any database capable of storing de-duplicated data can be adapted to implement embodiments of the invention. One embodiment utilizes codified algorithms to cross-match one or more retention policies with each document instance in the system based on the role of the custodian held at the time the instance was created and retained and / or the content or category of the content to which the document refers. If multiple policies apply, the retention period is set to the furthest in the future.

A method of removing metadata from a database in a multimode replication system includes establishing a metadata retention period for nodes in the system as well as associating changes with nodes on the system. The system responds to an expiration of the retention period for any one node by analyzing the associated changes and nodes and determining if the change affects data shared with other nodes. If the data is shared with other nodes then the expired retention period node metadata is removed from the system. If the expired metadata retention period node does not share the changes with other nodes, the metadata is not removed. This allows any unique changes to still be entered into the database without adversely affecting other nodes.

A background scheduler is provided that utilizes low-level communications (e.g., communications with a generic or controller-specific solid state, non-volatile memory driver) to control locking, reading, rewriting and unlocking of pages of data in the non-volatile memory. Such low-level communications cause data to be rewritten to the non-volatile memory independent of the file system in an effort to avoid data loss prior to an estimated data retention period.

The present invention performs appropriate archive management using a device that allows random access. An archive managing part 1B reads out files stored in an on-line volume 5A at a timing determined by the respective file type, and stores these files in a specified volume among archive volumes 5B1 and 5B2. A retention term is designated for each set of file data, and respective retention terms are also set for the respective volumes 5B1 and 5B2. The file data is stored in a volume having a retention term that matches the retention term of the file data. The respective volumes 5B1 and 5B2 are set in a device that allows random access such as a hard disk or the like. The areas in which data is written into the respective volumes 5B1 and 5B2 are managed as write prohibited areas by means of pointers P. As a result, the respective volumes 5B1 and 5B2 are used as a so-called WORM device.

A policy-based retention manager provides protection and management of files in a WORM file volume. The protection of the files is accomplished by the manager establishing a volume retention period for securely storing the files within the WORM file volume on a WORM media (e.g., a WORM disk media) based on a file retention end date of each file within the WORM file volume, and securely storing the WORM file volume on the WORM media during the volume retention period. The management of the files is accomplished by the manager establishing a volume reclamation period for reclaiming unexpired files within the WORM file volume prior to an expiration of the volume retention period, and reclaiming each unexpired file within the WORM file volume from the WORM media during the volume reclamation period.

Methods, apparatus, and computer program products are disclosed for managing data retention in a database operated by a database management system (‘DBMS’) that include creating, in metadata of the database, a retention policy for data of the database, and enforcing the retention policy by the DBMS. Managing data retention in a database operated by a DBMS may also include adding to the command set a retention command capable of creating the retention policy for data of the database, and creating the retention policy by the retention command. Managing data retention in a database operated by a DBMS may also include adding the retention measurement column to a table of the database. Managing data retention in a database operated by a DBMS may also include periodically enforcing the retention policy according to the retention periods.

The invention discloses a method for protecting user terminal comprising following step: network side successfully accesses to network at user terminal and assigns a false name to the user terminal; the network side receives the user terminal using the false name as information for marking user identity. The invention also discloses a method for protecting user terminal privacy comprising following steps: when the user terminal successfully access at user terminal, the user terminal receives temporary identity mark sent by network side and retention period of the identity mark; the user terminal receives request for reporting permanent identity mark sent by the network side; the user terminal judges if reporting response to permanent identity mark. The invention also discloses a system and device for protecting privacy of user terminal. The invention can effectively avoids attacker to take advantage of identity request information for acquiring permanent identity mark of user terminal, thereby protects privacy of user terminal.

The invention relates to a fish paste and a preparation method. The fish paste is characterized by comprising main raw materials and auxiliary raw materials, wherein the main raw materials comprise fish filet, lard oil, corn starch, fresh eggs and water, and the auxiliary raw materials comprise refined salt, a natural aromatic condiment, sodium glutamine, sorbitol and vegetable protein. The fish paste is prepared by the special processes of stewing, sterilizing and caking. The fish paste has the characteristics of high protein content, low fat content, long retention period, delicate quality, smooth and soft mouth feel, good toughness after being sliced into a flaky shape and convenient eating, can be preserved for 5 months at ordinary temperature, can be eaten in a cooking way, a swilling way, a stewing way, a cold way or a hot way and is a delicious food which is suitable for all the people, and the quality of the fish paste can be preserved for 4 months at ordinary temperature.

One embodiment is directed to the deletion of content units from a storage system. When a content unit is deleted, a reflection may be created and stored on the storage system. The reflection identifies the deleted content unit and may include additional information, such as a portion of the content of the content unit and audit information regarding the deletion of the content unit.

The invention discloses an ecological restoration structured approach for an unstable earth and rockfill side slope, comprising the following steps: reinforcing a slope with iron threaded anchor rods and galvanized wire meshes; then restoring by a wet type spraying and sowing technique; further reducing loss soil loss tolerance of a sowing layer by the pore retaining effect of a three-dimensional vegetation network; constructing surface runoff retaining ditches and reinforcing walls at the joint of naked abrupt slopes and undamaged massifs to prevent the fall of the slope crest; constructing a collecting basin at the slope base to collect slope runoff and massif predominant current. The approach disclosed by the invention effectively realizes effective fixation of a plant matrix of the unstable earth and rockfill side slope, so that a restored vegetation layer can be formed in a short period of time and is not easy to be damaged; meanwhile as water power retention period increases, adaptability is good, the restored matrix does not run off easily.

An electric power steering device provides an appropriate power assist from the motor even when torque sensors have failed and the steering torque is no longer detected. If an error is detected in a torque sensor, the motor is driven based on the rotor rotation angle detected by a resolver and assist characteristics. When the absolute value of the rotor turning angle velocity calculated based on the rotor rotation angle falls to or below a prescribed value, a process is started for reducing the current driving the motor, and if the state in which the absolute value of the rotor turning angle velocity has fallen to or below the prescribed value continues over a prescribed length of time, the process for reducing the current is interrupted and, because an assist current was flowing at said time of interruption, an appropriate power assist can be given during a steering retention period.

A wide area distributed storage system checks for erasion of WORM (Write-Once Read-Many) files. A first management server (100a) acquires from second disk equipment (200b) a storage location of a file which corresponds to the file stored on first disk equipment (200a), of which a storage period has expired, and queries a management server (100b) about a storage period of the file whose storage location has been acquired. The queried file management server refers to a file table and indicates existence or non-existence of the file on the second disk equipment and whether the storage period of the file has expired or not. The system avoids unintended deletion of files by querying a plurality of file management servers about whether a file with an expired retention period should be set as a deletable object.

A method and system is provided for configurable articulation of criteria for period archival, deletion, or movement of data from one data storage system to another. A consistent method for executing programs which manage specific data uses criteria articulated to identify sets of data and the rules associated with the data entities being process by the programs. Data entities may have different controlling rules and policies such as required by different countries, companies, or contractual arrangements. Data entities are associated with rules and policies that define durations for storage, frequency of archival, retention periods, or the like. As a result a consistent process may be achieved that captures an organization's retention policy and that be administered over a variety of application systems.