Platform management of integrated access of public and privately-accessible datasets utilizing federated query generation and query schema rewriting optimization
US-2017364539-A1 · Dec 21, 2017 · US
US10657282B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10657282-B2 |
| Application number | US-201916268783-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 6, 2019 |
| Priority date | Feb 27, 2017 |
| Publication date | May 19, 2020 |
| Grant date | May 19, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Controlling access to nodes in a relational graph at query time by using an approximate membership query (AMQ) filter and ordered queries based on historic grants or denials of access according to security context enables a more efficient querying of the relational graph while preserving access controls. Security contexts that grant or deny access to a node are stored in an associated AMQ filter and are queried according to the subject's security context in an order based on the frequency at which the security contexts have previously granted or denied access to nodes in the relational graph.
Opening claim text (preview).
We claim: 1. A method for controlling access to one or more nodes in a relational graph, comprising: receiving a graph query including a subject security context; determining whether a node in the relational graph denies access to the node, the determining including determining at least one of (a) whether a deny Approximate Membership Query (AMQ) filter denies access to the node, or (b) whether a query deny list denies access to the node; and denying access to the node if it is determined that the node denies the access. 2. The method of claim 1 , further comprising permitting access to the node if it is determined that the node does not deny the access. 3. The method of claim 1 , further comprising: determining whether the node in the relational graph permits access to the node, the determining including determining at least one of (a) whether a permit Approximate Membership Query (AMQ) filter permits access to the node, or (b) whether a query permit list permits access to the node; and permitting access to the node if it is determined that node permits the access. 4. The method of claim 3 , further comprising denying access to the node if it is determined that the node does not permit the access. 5. The method of claim 3 , whether determining whether the permit Approximate Membership Query (AMQ) filter permits access to the node includes querying the permit AMQ filter with the subject security context, the permit AMQ filter including security contexts that grant access to the node as permitting members. 6. The method of claim 3 , wherein determining whether the query permit list permits access to the node includes querying the permit list with the subject security context, the permit list including security contexts that grant access to the node. 7. The method of claim 1 , wherein determining whether the deny Approximate Membership Query (AMQ) filter denies access to the node includes querying the deny Approximate Membership Query (AMQ) filter with the subject security context, the deny AMQ filter including security contexts that deny access to the node as denying members. 8. The method of claim 1 , wherein determining whether the query deny list denies access to the node includes querying the deny list with the subject security context, the deny list including security contexts that deny access to the node. 9. A method for controlling access to nodes in a relational graph, comprising: identifying frequencies at which security contexts are used to grant or deny access to the nodes in the relational graph; sorting permit lists and deny lists based on the identified frequencies; receiving a graph query on the relational graph; obtaining one or more security contexts for a subject; and ordering the security contexts for the subject, based on the identified frequencies. 10. The method of claim 9 , wherein the frequencies are identified via one of a count-min sketch or a counting Bloom filter. 11. The method of claim 9 , wherein the frequencies are identified on a periodic basis or in response to a user command. 12. The method of claim 9 , wherein in the sorting, more frequently observed security contexts are placed ahead of less frequently observed security contexts. 13. The method of claim 9 , wherein the graph query includes at least one security context for the subject, and the obtaining is based on the at least one security context for the subject. 14. The method of claim 9 , wherein the ordering sets a query order by which security contexts are tested against at least one of an Approximate Membership Query (AMQ) filter or a list. 15. A system for controlling access to one or more nodes in a relational graph, comprising: a memory storing a program; and a computer processor operating under control of the program to: receive a graph query including a subject security context, determine whether a node in the relational graph denies access to the node, by determining at least one of (a) whether a deny Approximate Membership Query (AMQ) filter denies access to the node, or (b) whether a query deny list denies access to the node, and deny access to the node if it is determined that the node denies the access. 16. The system of claim 15 , further comprising: a user interface coupled to the computer processor, the user interface providing user-input commands to the computer processor for controlling the computer processor. 17. The system of claim 15 , wherein the computer processor also is controllable by the program to permit access to the node if it is determined that the node does not deny the access. 18. The system of claim 15 , wherein the computer processor also is controllable by the program to determine whether the node in the relational graph permits access to the node, by determining at least one of (a) whether a permit Approximate Membership Query (AMQ) filter permits access to the node, or (b) whether a query permit list permits access to the node. 19. The system of claim 18 , wherein the computer processor also operates under control of the program to deny access to the node if it is determined that the node does not permit the access. 20. The system of claim 15 , wherein, in determining whether the deny Approximate Membership Query (AMQ) filter denies access to the node, the computer processor operates under control of the program to query the deny Approximate Membership Query (AMQ) filter with the subject security context, the deny AMQ filter including security contexts that deny access to the node as denying members.
Protecting access to data via a platform, e.g. using keys or access control rules · CPC title
Search customisation based on user profiles and personalisation · CPC title
Graphs; Linked lists (G06F16/9027 takes precedence) · CPC title
where protection concerns the structure of data, e.g. records, types, queries · CPC title
to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.