Apparatus, System, and Method for Responsibility-Based Data Management
AssigneeCard Access, Inc.
InventorsJames A. Stout, Howard B. Gee
Life of this patent
Estimating the term…
Loading patent…
AssigneeCard Access, Inc.
InventorsJames A. Stout, Howard B. Gee
Estimating the term…
An apparatus, system, and method are disclosed for responsibility-based data management. In one embodiment, the method may include the steps of: (i) receiving, from a network participant, a request to access an information set; (ii) setting a permission indicator in response to a determination that the network participant is associated with a group dissemination attribute that authorizes the network participant to access the information set; (iii) modifying the permission indicator in response to a determination that an exception rule modifies the group dissemination attribute; (iv) setting the permission indicator in response to a determination that the network participant is associated with a system position attribute that authorizes the network participant to access the information set; and (v) providing access to the information set in response to a determination that the permission indicator authorizes the network participant to access the information set.
A method comprising:
A method comprising:
An apparatus comprising:
An apparatus comprising:
A system comprising:
A computer program product comprising a computer-readable medium having computer-readable instructions executable to perform operations comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
Backward citations are indexed for grants only.
Protecting access to data via a platform, e.g. using keys or access control rules: to a system of files or objects, e.g. local or distributed file…
Computing and data processing
Term end not estimated
This invention relates to data management and more particularly relates to an apparatus, system, and method for responsibility-based data management.
Groups or organizations of people working to achieve a common purpose or goal often face challenges with regard to adequate communication and sharing of information, responsibility delegation and tracking, and coordination of activities. In particular, data management may be one difficulty facing such groups and organizations.
Typical data management systems often require costly hardware acquisition and setup costs. As with most data management systems, data security may be a primary concern. Additional costs will often be incurred to employ a system administrator. Traditionally, a system administrator is an Information Technology (IT) professional that is trained to manage the data management system.
The following drawings form part of the present specification and are included to further demonstrate certain aspects of the present invention. The invention may be better understood by reference to one or more of these drawings in combination with the detailed description of specific embodiments presented herein.
FIG. 1 is a schematic block diagram of one embodiment of a system for responsibility-based data management;
FIGS. 2A-2B are schematic block diagrams illustrating alternative embodiments of a system for responsibility-based data management;
The invention and the various features and advantageous details are explained more fully with reference to the nonlimiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known starting materials, processing techniques, components, and equipment are omitted so as not to unnecessarily obscure the invention in detail. It should be understood, however, that the detailed description and the specific examples, while indicating embodiments of the invention, are given by way of illustration only and not by way of limitation. Various substitutions, modifications, additions, and/or rearrangements within the spirit and/or scope of the underlying inventive concept will become apparent to those skilled in the art from this disclosure.
Many of the functional units described in this specification have been labeled as modules in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.