Persisted Enterprise Graph Queries for Dynamic Entity Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise graph queries are complex and difficult for users to enter and manage, especially when involving multiple relationships between actor and target object sets, and there is a need for a way to easily access and update query results without re-entering the original query.
Innovation Solution
A system that allows users to persist enterprise graph queries, enabling them to be saved and re-run across various devices and experiences, with user input instructing the search service to save and associate the query with an entity, allowing access to updated results without re-entering the query.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If enterprise graph queries are made complex to handle multiple relationships between actor and target object sets, then query capability and relationship coverage are improved, but user input difficulty and query management complexity increase
Solution Approach 1:
The patent stores historical query results and query definitions in a database, allowing users to access and re-execute previously run queries without re-entering them. This copying mechanism preserves the complex query structure while simplifying user interaction by enabling query retrieval and re-execution through simple interface actions.
Solution Approach 2:
The patent introduces an intermediary interface layer between the user and the complex graph query system. This interface provides simplified actions for querying, persisting, and re-executing queries, mediating between user simplicity needs and the underlying complex query processing requirements.
2Adaptability or versatility
If enterprise graph queries are made complex to handle multiple relationships between actor and target object sets, then query capability and relationship coverage are improved, but device and system complexity increase
Solution Approach 1:
The system stores query definitions and results in a database, creating persistent copies that can be retrieved and re-executed. This eliminates the need to manage complex query structures in memory or through repeated manual input, reducing system complexity while maintaining advanced query capabilities.
Solution Approach 2:
The patent performs preliminary actions by storing query definitions and results in advance in a database. This allows queries to be prepared, saved, and automatically re-executed later without requiring the system to reconstruct or re-manage the complex query logic at execution time.
3Reliability
If users re-enter enterprise graph queries to access updated results, then query result freshness is improved, but user time consumption and computational resource usage increase
Solution Approach 1:
The patent performs preliminary actions by storing query definitions in the database in advance. When users need updated results, the system retrieves the stored query definition and re-executes it automatically, eliminating the need for users to re-enter queries and reducing both user time consumption and computational overhead.
Solution Approach 2:
The system copies stored query definitions from the database and uses them to generate updated results. This copying mechanism allows rapid re-execution of complex queries without requiring users to re-input them, maintaining result freshness while minimizing user effort and system resource usage.
Data Source
AI summary
A computer search service can receive an enterprise graph query from a client computing device that is remote from the computer search service, with the enterprise graph query identifying an actor object set, a target object set, and a relationship between the actor object set and the target object set. The search service can return results of the enterprise graph query to the client device. The search service can receive from the client device an indication of user input instructing the search service to persist the enterprise graph query, with the indication of user input also instructing the search service to associate the persisted enterprise graph query with an entity. Moreover, in response to receiving the indication of user input, the search service can persist the enterprise graph query as well as associate the persisted enterprise graph query with the entity and/or enter a subscription entry for the query.