US 2022/0067191 A1 · PERMISSIONS - ENFORCED GRAPH DATABASE

Abstract

An internally-constructed permissions graph database enabling a user to construct and alter the graph database permissions within the graph database. Edge permissions define whether a one node can View, Edit, or Manage another node. A node can view another node if there is at least one edge path connecting the nodes having a “View” permission. Similarly, a node can “Edit” or “Manage” another node if there is at least one edge path connecting the nodes having allowing “Edit” and/or “Manage” permissions, respectively. If a contiguous path of permission edges does not exist from the “caller node” to the “requested node” to be acted upon, then permission to perform the desired action or operation on that node is not granted. Edges have permissions, and Nodes have properties. A “Caller Node” makes Requests upon and “Requested Node,” which are limited by edge permissions.

Claims22

Dependent claims

A method for facilitating permissions within a graph database so as to enable a user of the graph database to construct and alter the graph database based upon edge permissions within the graph database, the method comprising the steps of:

providing a graph database utilizing nodes and edges connecting the nodes in a computer system, wherein the nodes have properties and the edges have permissions;
providing a root node that has view, edit, manage edge permissions to all nodes in the graph database;
storing data information within the nodes;
defining a caller node, a source node, and a terminal node;
and
defining edge permissions to include view, edit, and manage, wherein the view edge permission enables a first node to view the properties of a second node, the edit edge permission enables the first node to edit the properties of the second node, and the manage edge permission enables a caller node to create an edge between a source node and a terminal node provided the caller node has the view edge permission to the source node and the manage edge permission to the terminal node.

3 more elements

providing a graph database utilizing nodes and edges connecting the nodes in a computer system, wherein the nodes have properties and the edges have permissions;
providing a root node that has view, edit, manage edge permissions to all nodes in the graph database;
storing data information within the nodes;
defining a caller node, a source node, and a terminal node;
defining edge permissions to include view, edit, and manage, wherein the view edge permission enables a first node to view the properties of a second node, the edit edge permission enables the first node to edit the properties of the second node, and the manage edge permission enables a caller node to create an edge between a source node and a terminal node provided the caller node has the view edge permission to the source node and the manage edge permission to the terminal node;
and
providing data stored within the second node to the first node in response to a data query from the first node to the second node wherein an edge between the first node and the second exists having a view permission.

4 more elements

Dependencies are inferred from the claim text.

Permissions - enforced graph database

Life of this patent

Permissions - enforced graph database

Life of this patent

Abstract

Claims22