Patent classifications
G06F16/288
System and method for identifying at least one association of entity
A system and method for identifying at least one association of an entity. The system includes a processing module and a database arrangement communicably coupled to processing module. The processing module is operable to receive an input comprising data related to the entity; acquire web content related to the received input from a plurality of data sources; filter the acquired web content to obtain information relating to the entity; identify probable associations of the entity from the information relating to the entity using an ontology; determine for each of the probable associations, at least one of: a recency attribute, a frequency attribute, a proximity attribute, a semantics attribute; determine a probability score for each of the probable associations of the entity; and identify the at least one association of the entity from the probable associations, wherein the at least one association corresponds to a highest probability score.
Data processing method, apparatus, and system
A data processing method, apparatus, and system, where the method includes: receiving a data insertion request sent by service software, where the data insertion request includes a data record, and the data record includes an object type identifier, a field value, a field identifier, and an object instance identifier; generating a field index based on the object type identifier, the field value, and the object instance identifier; generating a relationship index based on the object type identifier; writing the data record to a database; and caching an index record and an operation for the index record into a cache apparatus, where the index record includes the relationship index and the field index. Using the foregoing solution, high-performance data processing of a flat-wide table is implemented.
Method and system for retrieving and displaying data from an entity network database
A computer-implemented method of retrieving and displaying data from an entity network database (130) comprising a plurality of entities and a plurality of relationships between the entities is provided. The method comprises receiving a selection of a plurality of anchor entities of the entity network database; retrieving a plurality of connector entities of the entity network database, each connector entity disposed on a path in the entity network database extending between at least two of the anchor entities; determining a relevance score for each of the connector entities, the relevance score reflecting the relevance of each connector entity to the anchor entities; and displaying the connector entities within a shape defined by the anchor entities, wherein the distance of each connector entity from the anchor entities is based on the relevance score of the connector entity.
Data investigation and visualization system
Data investigations are performed by querying a plurality of data sources. A system receives an investigation input and queries a plurality of data sources in accordance with the received input. The system receives, in response to the querying, response data from the plurality of data sources, and generates and stores a data structure representing relationships between the first investigation input and the first response data. The data structure may be in the form of a knowledge graph. The system may generate and display a visualization of the data structure. The system may generate and store a record of investigation steps used to generate the data structure, such that the investigation steps may be applied in future instances, for example using different inputs, to generate new data structures.
Unique ID generation for sensors
Systems, methods, and computer-readable media are provided for generating a unique ID for a sensor in a network. Once the sensor is installed on a component of the network, the sensor can send attributes of the sensor to a control server of the network. The attributes of the sensor can include at least one unique identifier of the sensor or the host component of the sensor. The control server can determine a hash value using a one-way hash function and a secret key, send the hash value to the sensor, and designate the hash value as a sensor ID of the sensor. In response to receiving the sensor ID, the sensor can incorporate the sensor ID in subsequent communication messages. Other components of the network can verify the validity of the sensor using a hash of the at least one unique identifier of the sensor and the secret key.
Systems and methods for using entity/relationship model data to enhance user interface engine
A user interface for allowing a user to create a chart, the user interface comprising: an entity type selection area for allowing a user to select a type of entity; an explorer for displaying an entity-relationship schema associated with the selected entity type and allowing a user to navigate the schema via one or more relationship paths; a list area for displaying one or more available fields of an entity associated with a relationship path selected from the explorer; and a target area for displaying a list of bindable data targets and allowing a user to assign one or more of the available fields to the bindable data targets to create a chart.
Methods and apparatus for visualizing entity instance relationships in a database
A method, apparatus, and non-transitory computer-readable storage medium for generating and presenting information identifying relationships between entity instances in a database that has a plurality of entity structures.
Free world replication protocol for key-value store
The “free world replication protocol” makes use of client computing resources, wherein the clients are not part of the replicated key-value store, but instead reside in the “free world” outside of the dedicated resources of the nodes of the replicated key-value store. In the free world replication protocol, only a single “write” client is authorized to modify the key-value store at any time but any number of clients may be authorized to read data from the key-value store. The write client sends its transactions to multiple nodes in the replicated key-value store. As a result, the latency between the transaction being sent from the client and the transaction being received by the multiple nodes is reduced. A consensus protocol, driven by a master node, is used to periodically ensure consistency, but the data transactions themselves do not make use of a master node.
System and method for managing relationships by identifying relevant content and generating correspondence based thereon
Systems and methods for managing contacts and generating communications with relevant content are disclosed herein. In an embodiment, a system for generating correspondence with one or more contact includes a central server with at least a processor and a memory. The central server is configured to communicate with a user terminal and a plurality of content sources. The processor is configured to execute instructions stored on the memory to cause the central server to: (i) determine at least one keyword relevant to at least one contact based on at least one contact input entered using the user terminal; (ii) use the at least one keyword to identify relevant content from the plurality of content sources; (iii) calculate at least one value for the relevant content; and (iv) generate a suggested communication to be displayed for the user on the user terminal when the at least one value meets a threshold.
Automatic creation of schema annotation files for converting natural language queries to structured query language
Methods, systems and computer readable media are provided for automatically creating a semantic model of a relational database for processing natural language queries. A computing device automatically extracts relational database metadata. The computing device prompts a user to enter textual labels for columns of the extracted metadata. The computing device automatically generates a schema annotation file based upon the relational database metadata and the textual labels for the columns. A natural language query is processed for the relational database using the schema annotation file.