According to one aspect, systems and processes for managing stored genomic sequencing data are provided. In exemplary process, a trigger related to a call review event is detected, where at least one portion of a denormalized data structure is accessed based on the detected trigger. In response the accessing, the at least one portion of the denormalized data structure is transformed into a normalized data structure. A user request associated with the at least one portion of the denormalized data structure is received. The normalized data structure is accessed in response to the user request, and information contained within the normalized data structure is then displayed on a display screen.

Aspects of the invention include assessing, by a management layer executing on a first processor, a query from a client application requesting data from a server. The assessing occurs prior to the query being executed by a provider. The assessing includes extracting, by the management layer, characteristics of the query. The management layer compares the extracted query characteristics with a policy defined by the provider. Based at least in part on results of the comparing, it is determined by the management layer whether the query is permitted to be executed by the provider at the server. The management layer initiates execution of the query at the server in response to determining that the query is permitted to be executed. The management layer prevents execution of the query at the server in response to determining that the query is not permitted to be executed.

A network device includes a standing query instance (SQI) and a database. The SQI is programmed to generate an output stored in a low resource storage table of a database. The database is programmed to monitor a storage capacity of the low resource storage table based on at least, in part, the output stored in the low resource storage table; determine, based on the monitoring, when the storage capacity reaches a predetermined amount; and disable an upstream element in response to the determination.

Techniques to interpret and resolve natural language queries that contain conditions are presented. The domains, intents, and slots for the condition portion and the action portion may be identified. The identified domain, intents, and slots may be delivered to another device or application for further processing.

New methods to represent variables as parts of the classical truth table lead to complete evaluation methods that generate a compiled, efficient version of logical expressions.

The new methods are suitable for use in, e.g., relational database applications in which both, efficient query times as well as logical completeness and consistency are required in the context of general constraint treatments.

Input/output operations remain linear in the length of the input character strings regardless of the complexity of the logical theory.

A new processing method of formulas is described as the basis for the efficiency increase.

In order to find a specific truth-value, pattern trees are used representing the extension of the logical theory.

Exemplary methods, apparatuses, and systems receive a command to overwrite or delete data stored within an allocated portion of a file system. In response to the command, an entry is added to a first data structure. A write command is received. The portion of the file system added to the first data structure is formatted for reallocation. In performance of the write command, the portion of the file system is reallocated. Portions of the file system are allocated from a second data structure when the second data structure includes a sufficient amount of space to satisfy the write command and from the first data structure when the second data structure does not include a sufficient amount of space. The second data structure includes free portions of the file system that have been formatted for allocation. The first data structure includes free portions that have yet to be formatted.

Databases may enforce foreign key constraints for efficient materialized view updates. A materialized view may be created for a database. Updates to the database may be received and performed according to a foreign key constraint enforced with respect to the updates. An update to the materialized view may be performed to make the materialized view consistent with the updates to the database. Performance of a join operation to update the materialized view that would return a result violating the foreign key constraint may be excluded from the update to the materialized view.

A system includes a processor and a memory storing multiple records in a key-value data structure and processor executable instructions for managing access to records in the key-value data structure. The instructions are executable to perform operations including managing a shared atomic epoch counter and thread epoch counters, determining a maximal safe epoch as a function of the shared atomic epoch counter and the thread epoch counters, maintaining a drain list of trigger actions, and triggering the trigger actions in the drain list as a function of an update of the shared atomic epoch counter and the maximal safe epoch.

A method for distributing content to a mobile communication device includes: storing a plurality of content profiles, wherein each content profile includes at least a content data file and associated trigger data; receiving an activity notification, wherein the activity notification includes at least trigger data associated with activity data corresponding to a wearable computing device interfaced with the mobile communication device; identifying one or more content profiles based on the included associated trigger data and the trigger data included in the activity notification; generating a data signal superimposed with at least the content data file included in the identified one or more content profiles; and electronically transmitting the generated data signal to the mobile communication device.

Disclosed is an intelligent remote monitoring method for fire-fighting, including: S1, pre-loading a protocol parsing configuration file in JSON format; S2, acquiring fire-fighting status information and operation status information of fire-fighting IoT equipment to obtain a data frame of a binary protocol; S3, parsing the data frame according to the configuration file to obtain a JSON data object, and pushing the parsed data of the fire-fighting IoT equipment to a routing layer through data push technology including kafka technology and storing in a fire-fighting database; S4: presetting different application modules according to different application services, and determining a routing direction of the data of the fire-fighting IoT equipment according to rules including a device type and a device status, and routing the data of the corresponding fire-fighting IoT equipment to the corresponding application module through the routing layer for triggering processing of events including alarms and faults, so as to realize remote monitoring of fire-fighting.