Hierarchical database monitoring

There is a need for more effective and efficient hierarchical database monitoring. This need can be addressed by, for example, solutions for performing/executing hierarchical database monitoring in an effective and efficient manner. In one example, a method includes identifying related hierarchical entities for each hierarchical entity; identifying an entity tracking data object for each hierarchical entity; updating the entity tracking data objects; generating a database monitoring data object based at least in part on the updated entity tracking data objects; and performing monitoring of the hierarchical database based at least in part on the database monitoring data object.

BACKGROUND

Various embodiments of the present invention address technical challenges related to performing hierarchical database monitoring. Because of the complexity of the data models utilized by hierarchical databases, monitoring such hierarchical databases presents unique reliability and efficiency challenges. Various embodiments of the present address the shortcomings of existing hierarchical database monitoring systems and disclose various techniques for efficiently and reliably performing hierarchical database monitoring.

BRIEF SUMMARY

In general, embodiments of the present invention provide methods, apparatus, systems, computing devices, computing entities, and/or the like for performing/executing hierarchical database monitoring. Certain embodiments utilize systems, methods, and computer program products that perform/execute hierarchical database monitoring using one or more of entity tracking data objects, entity invalidation statuses, invalidation iteration identifiers, creation iteration identifier, replicating invalidations, and non-replicating invalidations.

In accordance with one aspect, a method is provided. In one embodiment, the method comprises: for each hierarchical entity of the plurality of hierarchical entities, identifying one or more related hierarchical entities of the plurality of hierarchical entities, wherein the one or more related hierarchical entities comprise the corresponding hierarchical entity and any hierarchical entities of the plurality of hierarchical entities that depend from the corresponding hierarchical entity; for each hierarchical entity of the plurality of hierarchical entities, identifying an entity tracking data object of a plurality of entity tracking data objects, wherein the entity tracking data object comprises an entity invalidation status for the corresponding hierarchical entity; for each hierarchical entity of the plurality of hierarchical entities whose entity invalidation status indicates a valid entity status, updating the plurality of entity tracking data objects by: (a) determining, based at least in part on the entity-related data, an entity invalidation condition associated with the corresponding hierarchical entity, (b) determining whether the entity invalidation condition associated with the corresponding hierarchical entity indicates an invalid entity condition or a modified entity condition, (c) responsive to determining that the entity invalidation condition associated with the corresponding hierarchical entity indicates the invalid entity condition, performing a non-replicating invalidation of the corresponding hierarchical entity, wherein performing the non-replicating invalidation of the corresponding hierarchical entity comprises updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, and (d) responsive to determining that the entity invalidation condition associated with the corresponding hierarchical entity indicates the modified entity condition, performing a replicating invalidation of the corresponding hierarchical entity, wherein performing the replicating invalidation of the corresponding hierarchical entity comprises updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, generating a modified entity tracking data object for the corresponding hierarchical entity, and generating a replicated tracking data object for each related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity other than the corresponding hierarchical entity; and subsequent to updating the plurality of entity tracking data objects: (a) generating the database monitoring data object based at least in part on the plurality of entity tracking data objects, and (b) performing monitoring of the hierarchical database based at least in part on the database monitoring data object.

In accordance with another aspect, a computer program product is provided. The computer program product may comprise at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising executable portions configured to: for each hierarchical entity of the plurality of hierarchical entities, identify one or more related hierarchical entities of the plurality of hierarchical entities, wherein the one or more related hierarchical entities comprise the corresponding hierarchical entity and any hierarchical entities of the plurality of hierarchical entities that depend from the corresponding hierarchical entity; for each hierarchical entity of the plurality of hierarchical entities, identify an entity tracking data object of a plurality of entity tracking data objects, wherein the entity tracking data object comprises an entity invalidation status for the corresponding hierarchical entity; for each hierarchical entity of the plurality of hierarchical entities whose entity invalidation status indicates a valid entity status, update the plurality of entity tracking data objects by: (a) determining, based at least in part on the entity-related data, an entity invalidation condition associated with the corresponding hierarchical entity, (b) determining whether the entity invalidation condition associated with the corresponding hierarchical entity indicates an invalid entity condition or a modified entity condition, (c) responsive to determining that the entity invalidation condition associated with the corresponding hierarchical entity indicates the invalid entity condition, performing a non-replicating invalidation of the corresponding hierarchical entity, wherein performing the non-replicating invalidation of the corresponding hierarchical entity comprises updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, and (d) responsive to determining that the entity invalidation condition associated with the corresponding hierarchical entity indicates the modified entity condition, performing a replicating invalidation of the corresponding hierarchical entity, wherein performing the replicating invalidation of the corresponding hierarchical entity comprises updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, generating a modified entity tracking data object for the corresponding hierarchical entity, and generating a replicated tracking data object for each related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity other than the corresponding hierarchical entity; and subsequent to updating the plurality of entity tracking data objects: (a) generate the database monitoring data object based at least in part on the plurality of entity tracking data objects, and (b) perform monitoring of the hierarchical database based at least in part on the database monitoring data object.

In accordance with yet another aspect, an apparatus comprising at least one processor and at least one memory including computer program code is provided. In one embodiment, the at least one memory and the computer program code may be configured to, with the processor, cause the apparatus to: for each hierarchical entity of the plurality of hierarchical entities, identify one or more related hierarchical entities of the plurality of hierarchical entities, wherein the one or more related hierarchical entities comprise the corresponding hierarchical entity and any hierarchical entities of the plurality of hierarchical entities that depend from the corresponding hierarchical entity; for each hierarchical entity of the plurality of hierarchical entities, identify an entity tracking data object of a plurality of entity tracking data objects, wherein the entity tracking data object comprises an entity invalidation status for the corresponding hierarchical entity; for each hierarchical entity of the plurality of hierarchical entities whose entity invalidation status indicates a valid entity status, update the plurality of entity tracking data objects by: (a) determining, based at least in part on the entity-related data, an entity invalidation condition associated with the corresponding hierarchical entity, (b) determining whether the entity invalidation condition associated with the corresponding hierarchical entity indicates an invalid entity condition or a modified entity condition, (c) responsive to determining that the entity invalidation condition associated with the corresponding hierarchical entity indicates the invalid entity condition, performing a non-replicating invalidation of the corresponding hierarchical entity, wherein performing the non-replicating invalidation of the corresponding hierarchical entity comprises updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, and (d) responsive to determining that the entity invalidation condition associated with the corresponding hierarchical entity indicates the modified entity condition, performing a replicating invalidation of the corresponding hierarchical entity, wherein performing the replicating invalidation of the corresponding hierarchical entity comprises updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, generating a modified entity tracking data object for the corresponding hierarchical entity, and generating a replicated tracking data object for each related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity other than the corresponding hierarchical entity; and subsequent to updating the plurality of entity tracking data objects: (a) generate the database monitoring data object based at least in part on the plurality of entity tracking data objects, and (b) perform monitoring of the hierarchical database based at least in part on the database monitoring data object.

DETAILED DESCRIPTION

Various embodiments of the present invention address technical challenges related to monitoring hierarchical databases. In a hierarchical database, data entities are related to each other with hierarchical relationships, often very complex and multi-layered hierarchical relationships. Because of their complex semantic structure, hierarchical databases present unique problems for efficient and effective database monitoring. For example, in a hierarchical database, any invalidation or modification of a particular hierarchical entity may have effects on some but not all of the hierarchical entities that have defined hierarchical relationships with the corresponding hierarchical entity. As a result, many existing hierarchical database monitoring solutions will resort to one of two approaches to address the challenges associated with efficient and effective monitoring of various hierarchical databases: performing multiple monitoring iterations to generate each monitoring report or limiting propagation of invalidation or modification of particular hierarchical entities across their corresponding hierarchical relationships. The former approach is inefficient while the latter approach fails to perform reliable monitoring metrics under various runtime conditions.

Various embodiments of the present invention introduce techniques for performing monitoring of a hierarchical database in a manner that, during a single iteration, can propagate invalidations or modifications across hierarchical relationships characterizing a hierarchical database. For example, in some embodiments, a proposed system determines, based at least in part on entity-related data associated with a hierarchical database, an entity invalidation condition associated with each hierarchical entity. Responsive to determining that the entity invalidation condition associated with a hierarchical entity indicates an invalid entity condition, the proposed system updates each entity tracking data object for a dependent hierarchical entity associated with the corresponding hierarchical entity to invalidate the dependent hierarchical entity. However, responsive to determining that the entity invalidation condition associated with a hierarchical entity a the modified entity condition, the proposed system updates each entity tracking data object for a dependent hierarchical entity associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, generates a modified entity tracking data object for the corresponding hierarchical entity, and generates a replicated tracking data object for each dependent hierarchical entity associated with the corresponding hierarchical entity other than the corresponding hierarchical entity. In this way, the proposed system can ensure effective hierarchical propagation of invalidations and modifications while preventing a monitoring iteration repeat need scenario.

By utilizing the noted techniques and similar techniques described herein, various embodiments of the present invention provide techniques for efficiently and reliably performing database monitoring in a hierarchical database. The noted techniques accommodate the unique needs and complexities of hierarchical databases and make important contributions to reducing time complexity of hierarchical database monitoring routines in highly-complex databases, such as hierarchical databases. Importantly, by reducing time complexity of hierarchical database monitoring, the described techniques allow for retroactive entity tracking in hierarchical databases, a task that requires performing entity tracking across various temporal units during a single monitoring iteration. Accordingly, various embodiments of the present invention address technical challenges related to improving effectiveness and efficiency of hierarchical database monitoring solutions and substantially improve the effectiveness and efficiency of existing hierarchical database monitoring frameworks.

II. COMPUTER PROGRAM PRODUCTS, METHODS, AND COMPUTING ENTITIES

As should be appreciated, various embodiments of the present invention may also be implemented as methods, apparatus, systems, computing devices, computing entities, and/or the like. As such, embodiments of the present invention may take the form of an apparatus, system, computing device, computing entity, and/or the like executing instructions stored on a computer-readable storage medium to perform certain steps or operations. Thus, embodiments of the present invention may also take the form of an entirely hardware embodiment, an entirely computer program product embodiment, and/or an embodiment that comprises combination of computer program products and hardware performing certain steps or operations. Embodiments of the present invention are described below with reference to block diagrams and flowchart illustrations. Thus, it should be understood that each block of the block diagrams and flowchart illustrations may be implemented in the form of a computer program product, an entirely hardware embodiment, a combination of hardware and computer program products, and/or apparatus, systems, computing devices, computing entities, and/or the like carrying out instructions, operations, steps, and similar words used interchangeably (e.g., the executable instructions, instructions for execution, program code, and/or the like) on a computer-readable storage medium for execution. For example, retrieval, loading, and execution of code may be performed sequentially such that one instruction is retrieved, loaded, and executed at a time. In some exemplary embodiments, retrieval, loading, and/or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and/or executed together. Thus, such embodiments can produce specifically-configured machines performing the steps or operations specified in the block diagrams and flowchart illustrations. Accordingly, the block diagrams and flowchart illustrations support various combinations of embodiments for performing the specified instructions, operations, or steps.

III. EXEMPLARY SYSTEM ARCHITECTURE

FIG. 1is a schematic diagram of an example architecture100for performing/executing hierarchical database monitoring. The architecture100includes a hierarchical database system101configured to store one or more hierarchical databases, receive database monitoring requests for monitoring the hierarchical databases, generate database monitoring data objects for the hierarchical databases in response to the received database monitoring requests, provide the generated database monitoring data objects to particular external computing entities102(e.g., monitoring authority computing entities), and/or automatically set configuration parameters for the hierarchical databases. For example, the hierarchical database system101may be configured to maintain a member information database for a health insurance provider institution, perform database monitoring of the member information database to generate membership accounting reports for the health insurance provider institution, and provide the membership accounting reports to one or more financial institution computing entities.

In some embodiments, hierarchical database system101may communicate with at least one of the external computing entities102using one or more communication networks. Examples of communication networks include any wired or wireless communication network including, for example, a wired or wireless local area network (LAN), personal area network (PAN), metropolitan area network (MAN), wide area network (WAN), or the like, as well as any hardware, software and/or firmware required to implement it (such as, e.g., network routers, and/or the like).

The hierarchical database system101may include a hierarchical database computing entity106and a storage subsystem108. The hierarchical database computing entity106may be configured to receive database monitoring requests for monitoring the hierarchical databases, generate database monitoring data objects for the hierarchical databases in response to the received database monitoring requests, provide the generated database monitoring data objects to particular external computing entities102(e.g., monitoring authority computing entities), and/or automatically set configuration parameters for the hierarchical databases.

The storage subsystem108may be configured to store data associated with the hierarchical databases maintained by the hierarchical database system101. The storage subsystem108may further be configured to store configuration data associated with the hierarchical database system101, such as configuration data associated with the hierarchical databases maintained by the hierarchical database system101and/or configuration data associated with the operation of the hierarchical database computing entity106.

The storage subsystem108may include one or more storage units, such as multiple distributed storage units that are connected through a computer network. Each storage unit in the storage subsystem108may store at least one of one or more data assets and/or one or more data about the computed properties of one or more data assets. Moreover, each storage unit in the storage subsystem108may include one or more non-volatile storage or memory media including but not limited to hard disks, ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RANI, Millipede memory, racetrack memory, and/or the like.

Exemplary Hierarchical Database Computing Entity

As indicated, in one embodiment, the hierarchical database computing entity106may also include one or more communications interfaces220for communicating with various computing entities, such as by communicating data, content, information, and/or similar terms used herein interchangeably that can be transmitted, received, operated on, processed, displayed, stored, and/or the like.

In one embodiment, the hierarchical database computing entity106may further include or be in communication with non-volatile media (also referred to as non-volatile storage, memory, memory storage, memory circuitry and/or similar terms used herein interchangeably). In one embodiment, the non-volatile storage or memory may include one or more non-volatile storage or memory media210, including but not limited to hard disks, ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, NVRAM, MRAM, RRAM, SONOS, FJG RAM, Millipede memory, racetrack memory, and/or the like. As will be recognized, the non-volatile storage or memory media may store databases, database instances, database management systems, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like. The term database, database instance, database management system, and/or similar terms used herein interchangeably may refer to a collection of records or data that is stored in a computer-readable storage medium using one or more database models, such as a hierarchical database model, network model, relational model, entity-relationship model, object model, document model, semantic model, graph model, and/or the like.

Exemplary External Computing Entity

FIG. 3provides an illustrative schematic representative of an external computing entity102that can be used in conjunction with embodiments of the present invention. In general, the terms device, system, computing entity, entity, and/or similar words used herein interchangeably may refer to, for example, one or more computers, computing entities, desktops, mobile phones, tablets, phablets, notebooks, laptops, distributed systems, kiosks, input terminals, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and/or any combination of devices or entities adapted to perform the functions, operations, and/or processes described herein. External computing entities102can be operated by various parties. As shown inFIG. 3, the external computing entity102can include an antenna312, a transmitter304(e.g., radio), a receiver306(e.g., radio), and a processing element308(e.g., CPLDs, microprocessors, multi-core processors, coprocessing entities, ASIPs, microcontrollers, and/or controllers) that provides signals to and receives signals from the transmitter304and receiver306, correspondingly.

The signals provided to and received from the transmitter304and the receiver306, correspondingly, may include signaling information/data in accordance with air interface standards of applicable wireless systems. In this regard, the external computing entity102may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the external computing entity102may operate in accordance with any of a number of wireless communication standards and protocols, such as those described above with regard to the hierarchical database computing entity106. In a particular embodiment, the external computing entity102may operate in accordance with multiple wireless communication standards and protocols, such as UMTS, CDMA2000, 1×RTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, UWB, IR, NFC, Bluetooth, USB, and/or the like. Similarly, the external computing entity102may operate in accordance with multiple wired communication standards and protocols, such as those described above with regard to the hierarchical database computing entity106via a network interface320.

Via these communication standards and protocols, the external computing entity102can communicate with various other entities using concepts such as Unstructured Supplementary Service Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MIMS), Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber Identity Module Dialer (SIM dialer). The external computing entity102can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including executable instructions, applications, program modules), and operating system.

The external computing entity102may also comprise a user interface (that can include a display316coupled to a processing element308) and/or a user input interface (coupled to a processing element308). For example, the user interface may be a user application, browser, user interface, and/or similar words used herein interchangeably executing on and/or accessible via the external computing entity102to interact with and/or cause display of information/data from the hierarchical database computing entity106, as described herein. The user input interface can comprise any of a number of devices or interfaces allowing the external computing entity102to receive data, such as a keypad318(hard or soft), a touch display, voice/speech or motion interfaces, or other input device. In embodiments including a keypad318, the keypad318can include (or cause display of) the conventional numeric (0-9) and related keys (#, *), and other keys used for operating the external computing entity102and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface can be used, for example, to activate or deactivate certain functions, such as screen savers and/or sleep modes.

In another embodiment, the external computing entity102may include one or more components or functionality that are the same or similar to those of the hierarchical database computing entity106, as described in greater detail above. As will be recognized, these architectures and descriptions are provided for exemplary purposes only and are not limiting to the various embodiments.

IV. EXEMPLARY SYSTEM OPERATIONS

Various embodiments of the present invention introduce techniques for performing monitoring of a hierarchical database in a manner that, during a single iteration, can propagate invalidations or modifications across hierarchical relationships characterizing a hierarchical database. For example, in some embodiments, a proposed system determines, based at least in part on entity-related data associated with a hierarchical database, an entity invalidation condition associated with each hierarchical entity. Responsive to determining that the entity invalidation condition associated with a hierarchical entity indicates an invalid entity condition, the proposed system updates each entity tracking data object for a dependent hierarchical entity associated with the corresponding hierarchical entity to invalidate the dependent hierarchical entity. However, responsive to determining that the entity invalidation condition associated with a hierarchical entity a the modified entity condition, the proposed system updates each entity tracking data object for a dependent hierarchical entity associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, generates a modified entity tracking data object for the corresponding hierarchical entity, and generates a replicated tracking data object for each dependent hierarchical entity associated with the corresponding hierarchical entity other than the corresponding hierarchical entity. In this way, the proposed system can ensure effective hierarchical propagation of invalidations and modifications while preventing a monitoring iteration repeat need scenario.

By utilizing the noted techniques and similar techniques described herein, various embodiments of the present invention provide techniques for efficiently and reliably performing database monitoring in a hierarchical database. The noted techniques accommodate the unique needs and complexities of hierarchical databases and make important contributions to reducing time complexity of hierarchical database monitoring routines in highly-complex databases, such as hierarchical databases. Importantly, by reducing time complexity of hierarchical database monitoring, the described techniques allow for retroactive entity tracking in hierarchical databases, a task that requires performing entity tracking across various temporal units during a single monitoring iteration. Accordingly, various embodiments of the present invention address technical challenges related to improving effectiveness and efficiency of hierarchical database monitoring solutions and substantially improve the effectiveness and efficiency of existing hierarchical database monitoring frameworks.

A. Hierarchical Database Monitoring

FIG. 4is a flowchart diagram of an example process400for performing database monitoring with respect to a hierarchical database. Via the various steps/operations of process400, the hierarchical database computing entity106can perform effective and efficient adjustments to entity states for various hierarchical entities in a hierarchical database in a manner that reliably addresses hierarchical relationships between the various hierarchical entities in the hierarchical database.

At step/operation401, the hierarchical database computing entity106identifies one or more related hierarchical entities for each hierarchical entity associated with the hierarchical database. The related entities for a particular hierarchical entity may include the corresponding hierarchical entity itself and any hierarchical entities associated with the hierarchical database that depend from the corresponding hierarchical entity. In some embodiments, the hierarchical database is configured to maintain entity-related data associated with a plurality of hierarchical entities, where the plurality of hierarchical entities may be related to each other by a hierarchical structure that defines one or more hierarchical relationships. The hierarchical database computing entity106may utilize the noted hierarchical structure to determine the related hierarchical entities for each particular hierarchical entity associated with the hierarchical database. In some embodiments, the hierarchical database is a membership information database, and at least some of plurality of hierarchical entities are associated with one or more member profiles associated with the membership information database.

For example, given a hierarchical database associated with the hierarchical entities HE1-HE6 where hierarchical entities HE2-HE3 directly depend from the hierarchical entity HE1, hierarchical entity HE4 depends from the hierarchical entity HE2, hierarchical entity HE5 depends from the hierarchical entity HE4, and hierarchical entity HE6 depends from the hierarchical entity HE3, the related hierarchical entities for each of the hierarchical entities HE1-HE6 may include: for the hierarchical entity HE1, hierarchical entities HE1-HE6; for the hierarchical entity HE2, hierarchical entities HE2 and HE4-HE5; for the hierarchical entity HE3, hierarchical entities HE3 and HE6; for the hierarchical entity HE4, hierarchical entities HE4-HE5; for the hierarchical entity HE5, the hierarchical entity HE5 itself; and for the hierarchical entity HE6, the hierarchical entity HE6 itself. In some embodiments, a hierarchical entity A is deemed to be related to a hierarchical entity B if changes in at least one aspect of the status of hierarchical entity B may affect the status of the hierarchical entity A. For example, in the described example, an invalidation of the hierarchical entity HE1 may necessitate the invalidation of all of the hierarchical entities HE2-HE5.

An operational example of a hierarchical database data model500for a hierarchical database is depicted inFIG. 5. As depicted inFIG. 5, the hierarchical database data model500includes four hierarchical levels501-504, where each hierarchical level501-504is associated with one or more hierarchical entity types, and further where each hierarchical entity type is associated with one or more attribute types. For example, the hierarchical level501is a highest hierarchical level that is associated with a “Member Group Contract Plan Option” hierarchical entity type. As another example, the hierarchical level502is a second-highest hierarchical level that is associated with a “Benefit Plan” hierarchical entity type. As yet another example, the hierarchical level503is a third-highest hierarchical level that is associated with a “Membership” hierarchical entity type. As a further example, the hierarchical level504is a fourth-highest hierarchical level that is associated with a “Member Count” hierarchical entity type, a “Subscriber Count” hierarchical entity type, and a “Surviving Spouse Count” hierarchical entity type.

In some embodiments, each hierarchical entity of the plurality of hierarchical entities is associated with an entity designation of a plurality of entity designations and a temporal unit designation of a plurality of temporal unit designations (e.g., a month of a predefined number of months, such as 48 months). For example, a first hierarchical entity may be associated with monitoring attributes for a first group plan during a first month and a second hierarchical entity may be associated with monitoring attributes for the first group plan during a second month. Associating hierarchical entities with temporal unit designations may enable retroactive reporting of changes to entity states in prior temporal units even when such changes were not properly captured during monitoring iterations associated with the prior temporal units. For example, given a change in a membership state for a particular member for October that only gets reflected in entity-related data by November, the hierarchical database computing entity106can reflect the change in the November monitoring report but for the appropriate entity associated with the particular member and the month of October. In this way, the hierarchical database computing entity106can both record that the change has occurred in October but that it has first been reflected in monitoring reports as of the November report. In some embodiments, each temporal unit may be associated with two or more monitoring iterations. For example, two database monitoring data objects may be generated during each month.

At step/operation402, the hierarchical database computing entity106identifies a plurality of entity tracking data objects for the hierarchical entities associated with the hierarchical database. In some embodiments, the hierarchical database computing entity106identifies an entity tracking data object for each hierarchical entity associated with the hierarchical database. In some embodiments, the entity tracking data object for a hierarchical entity is a data object that indicates one or more properties of the hierarchical entity, such as an entity invalidation status for the hierarchical entity, an invalidation iteration identifier for the hierarchical entity, a creation iteration identifier for the hierarchical entity, and one or more entity attributes for the hierarchical entity.

In some embodiments, the entity invalidation status for a hierarchical entity indicates whether the hierarchical entity is deemed valid at a time associated with performing monitoring of the hierarchical database (e.g., at current a monitoring iteration during which a current database monitoring data object is generated). In some embodiments, the invalidation iteration identifier for the hierarchical entity indicates a monitoring iteration during which the hierarchical entity is first designated as being invalid. In some embodiments, the creation iteration identifier for the hierarchical entity indicates a monitoring iteration during which the hierarchical entity is first created. In some embodiments, an entity attribute for the hierarchical entity indicates data defining the hierarchical entity. In some embodiments, the entity tracking data object for a hierarchical entity further indicates one or more hierarchical relationships of the hierarchical entity with other hierarchical entities associated with the hierarchical database.

An operational example of entity tracking data objects601-606for six hierarchical entities is depicted in the entity tracking data object file600ofFIG. 6. As depicted in the entity tracking data object file600ofFIG. 6, the entity tracking data objects601-605are each associated with a group of attributes. For example, the entity tracking data object601which corresponds to a “Member Group Contract Plan Option” hierarchical entity type in the hierarchical database data model500ofFIG. 5is associated with various associated entity attributes such as customerPurchaseIdentifier and customerPurchaseEffectiveDate. As another example, the entity tracking data object602which corresponds to a “Benefit Plan” hierarchical entity type in the hierarchical database data model500ofFIG. 5is associated with various associated entity attributes such as productIdentifier and productTypeCode. As a yet another example, the entity tracking data object603which corresponds to a “Membership” hierarchical entity type in the hierarchical database data model500ofFIG. 5is associated with various associated entity attributes such as medicareEntitlementTypeCode and subscriberResidentStateCode. As a further example, the entity tracking data objects604-606which correspond to “Subscriber Count,” “Member Count,” and “Surviving Spouse Count” hierarchical entity types respectively in the hierarchical database data model500ofFIG. 5are each associated with a count entity attribute.

At step/operation403, the hierarchical database computing entity106updates the plurality of entity tracking data objects for the hierarchical entities associated with the hierarchical database by analyzing entity-related data associated with each hierarchical entity of the hierarchical entities associated with the hierarchical database. In some embodiments, the hierarchical database computing entity106determines whether any of the entity tracking data objects in the plurality of entity tracking data objects for the hierarchical entities associated with the hierarchical database should be modified (e.g., set to an invalid entity status) and/or whether any new entity tracking data objects should be added to the plurality of entity tracking data objects for the hierarchical entities associated with the hierarchical database. In some embodiments, the hierarchical database computing entity106performs the noted determination based at least in part on entity-related data stored with respect to the hierarchical entities in the hierarchical database. For example, the hierarchical database computing entity106may determine that the invalidation status for a member entity type should be set to indicate an invalid entity status responsive to determining that the member has left a particular member group contract plan option.

In some embodiments, subsequent to determining that any of the entity tracking data objects in the plurality of entity tracking data objects associated with the hierarchical database should be modified and/or whether any new entity tracking data objects should be added to the plurality of entity tracking data objects associated with the hierarchical database, the hierarchical database computing entity106updates the plurality of entity tracking data objects associated with the hierarchical database in accordance with the noted preceding determinations. In some embodiments, updating the plurality of entity tracking data objects comprises analyzing each of the plurality of hierarchical entities starting from a highest hierarchical level to a lowest hierarchical level.

In some embodiments, step/operation403may be performed in relation to a particular hierarchical entity in accordance with the various steps/operations depicted inFIG. 7. The process depicted inFIG. 7begins at step/operation701when the hierarchical database computing entity106determines an entity invalidation condition for the corresponding hierarchical entity. The entity invalidation condition for the corresponding hierarchical entity indicates whether the entity tracking data object for the hierarchical entity should be set to indicate an invalid status. In some embodiments, the plurality of hierarchical entities for the hierarchical database are associated with a current monitoring iteration of a plurality of monitoring iterations, the plurality of monitoring iterations is associated with a temporal order which defines a precedent monitoring iteration for the current monitoring iteration, and the invalidation condition for each hierarchical entity of the plurality of hierarchical entities is determined based at least in part on whether the entity-related data indicate one or more entity condition updates for the hierarchical entity between the precedent monitoring iteration and the current monitoring iteration.

In some embodiments, the hierarchical database computing entity106determines the invalidation condition for the corresponding hierarchical entity based at least in part on entity-related data associated with the corresponding hierarchical entity and maintained in the hierarchical database. For example, the entity-related data associated with the hierarchical entity may indicate occurrence of at least one of an invalidating event (e.g., a cancellation event) or an attribute modification event (e.g., a plan adjustment event) with respect to the corresponding hierarchical entity which in turn may trigger setting the entity invalidation condition for the corresponding hierarchical entity accordingly.

At step/operation702, the hierarchical database computing entity106determines whether the entity invalidation condition for the corresponding hierarchical entity indicates an invalid entity condition, a modified entity condition, or a valid entity condition. In some embodiments, the entity invalidation condition for the corresponding hierarchical entity may indicate an invalid entity condition, a modified entity condition, or a valid entity condition. The noted invalidation conditions are described in greater detail below with reference to steps/operations703-705.

At step/operation703, responsive to determining that the entity invalidation condition for the corresponding hierarchical entity indicates an invalid entity condition, the hierarchical database computing entity106performs a non-replicating invalidation of the corresponding hierarchical entity, wherein performing the non-replicating invalidation of the corresponding hierarchical entity may include updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity. In some embodiments, the entity tracking data object for a hierarchical entity of the plurality of hierarchical entities comprises an invalidation iteration identifier for the hierarchical entity. In some embodiments, performing the non-replicating invalidation of a hierarchical entity of the plurality of hierarchical entities comprises modifying the invalidation iteration identifier for the hierarchical entity to indicate a current monitoring iteration.

In some embodiments, an invalid entity condition indicates that the hierarchical entity has been nullified and/or cancelled. For example, the invalid entity condition for a hierarchical entity having a member entity type may indicate that a member has deceased and/or has left a group plan. In some embodiments, to accommodate the invalid invalidation condition for a hierarchical entity, the hierarchical database computing entity106invalidates the entity tracking data object for both the invalidated hierarchical entity and any hierarchical entities that depend from the hierarchical entity without replacing any of the noted invalidated hierarchical entities. In some embodiments, to invalidate an entity tracking data object, the hierarchical database computing entity106sets the invalidation status of the entity tracking data object to indicate an invalidation status and/or sets an invalidation iteration identifier of the entity tracking data object to indicate a current monitoring iteration.

At step/operation704, responsive to determining that the entity invalidation condition for the corresponding hierarchical entity indicates a modified entity condition, the hierarchical database computing entity106performs a replicating invalidation of the corresponding hierarchical entity, wherein performing the replicating invalidation of the corresponding hierarchical entity may include updating each entity tracking data object for a related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity to invalidate the related hierarchical entity, generating a modified entity tracking data object for the corresponding hierarchical entity, and generating a replicated tracking data object for each related hierarchical entity of the one or more related hierarchical entities associated with the corresponding hierarchical entity other than the corresponding hierarchical entity.

In some embodiments, a modified entity condition indicates that at least one entity attribute associated with the entity has been modified and/or changed. For example, the modified entity condition for a member entity type may indicate that a member has changed her deductible range selection. In some embodiments, to accommodate the modified invalidation condition for a hierarchical entity, the hierarchical database computing entity106invalidates the entity tracking data object for both the invalidated hierarchical entity and any hierarchical entities that depend from the hierarchical entity but generates new entity tracking data objects to replace the invalidated entity tracking data objects, where the new tracking data object for the corresponding hierarchical entity has modified attributes.

In some embodiments, to invalidate an entity tracking data object, the hierarchical database computing entity106sets the invalidation status of the entity tracking data object to indicate an invalidation status. In some embodiments, to invalidate an entity tracking data object, the hierarchical database computing entity106sets an invalidation iteration identifier of the entity tracking data object to indicate a current monitoring iteration. In some embodiments, to generate a new entity tracking data object, the hierarchical database computing entity106generates data associated with the new entity tracking data object (e.g., in accordance with one or more attribute modification requests associated with the modified entity condition) and/or sets a creation iteration identifier of the entity tracking data object to indicate a current monitoring iteration.

In some embodiments, the entity tracking data object for a hierarchical entity of the plurality of hierarchical entities comprises one or more entity attributes for the hierarchical entity. In some of those embodiments, generating the modified entity tracking data object for a hierarchical entity of the plurality of hierarchical entities comprises generating an entity tracking data object based at least in part on the hierarchical entity and one or more modifications to the one or more entity attributes for the hierarchical entity in accordance with the modified entity condition. In some embodiments, the entity tracking data object for a hierarchical entity of the plurality of hierarchical entities comprises a creation iteration identifier for the hierarchical entity. In some of those embodiments, performing the replicating invalidation of a hierarchical entity of the plurality of hierarchical entities comprises generating the modified entity tracking data object for the hierarchical entity to indicate a current monitoring iteration in the creation iteration identifier for the hierarchical entity.

At step/operation705, responsive to determining that the entity invalidation condition for the corresponding hierarchical entity indicates a valid entity condition, the hierarchical database computing entity106does not invalidate the entity tracking data object associated with the hierarchical entity. In some embodiments, a valid entity condition indicates that neither the hierarchical entity has been nullified and/or cancelled nor at least one entity attribute associated with the entity has been modified and/or changed. Accordingly, responsive to determining that the entity invalidation condition for the corresponding hierarchical entity indicates a valid entity condition as defined herein, the hierarchical database computing entity106does not need to perform any invalidations of entity tracking data objects or any generation of new entity tracking data objects.

Returning toFIG. 4, at step/operation404, the hierarchical database computing entity106generates a database monitoring data object based at least in part on the plurality of entity tracking data objects. In some embodiments, subsequent to updating the plurality of entity tracking data objects associated with the hierarchical database, the hierarchical database computing entity106utilizes the updated plurality of entity tracking data objects to generate the database monitoring data object, which may be a database object that includes each of the updated plurality of entity tracking data objects. In some embodiments, the database monitoring data object may be a latest iteration of a monitoring report associated with the hierarchical database that can be compared with prior and subsequent monitoring reports associated with the hierarchical database.

At step/operation405, the hierarchical database computing entity106performs monitoring of the hierarchical database based at least in part on the database monitoring data object. In some embodiments, performing monitoring of the hierarchical database based at least in part on the database monitoring data object includes setting one or more database configuration parameters for the hierarchical database based at least in part on the database monitoring data object (e.g., based at least in part on comparing the database monitoring data object and other database monitoring data objects associated with other monitoring iterations). In some embodiments, performing monitoring of the hierarchical database based at least in part on the database monitoring data object includes performing one or more load balancing operations for the hierarchical database based at least in part on the database monitoring data object (e.g., based at least in part on comparing the database monitoring data object and other database monitoring data objects associated with other monitoring iterations).

In some embodiments, performing monitoring of the hierarchical database based at least in part on the database monitoring data object includes generating a monitoring report for the hierarchical database based at least in part on the database monitoring data object and transmitting the monitoring report to a monitoring authority computing device (e.g., a financial institution server). In some embodiments, performing monitoring of the hierarchical database based at least in part on the database monitoring data object includes generating a maintenance recommendation for the hierarchical database based at least in part on the database monitoring data object and transmitting the maintenance recommendation a monitoring authority computing device (e.g., a financial institution server).

B. Generating Entity Tracking Reports

FIG. 8is a flowchart diagram of an example process800for generating an entity tracking report for a hierarchical database during a current monitoring iteration. Via the various steps/operations of process800, the hierarchical database computing entity106can generate entity tracking reports for various hierarchical entities in a hierarchical in an effective and efficient manner.

The process800begins at step/operation801when the hierarchical database computing entity106creates a new reporting iteration. At step/operation802, the hierarchical database computing entity106retrieves a list of hierarchical entities. At step/operation803, for each new hierarchical entity, the hierarchical database computing entity106generates a new entity tracking data object for the new hierarchical entity, where the new entity tracking data object includes a creation iteration identifier that indicates the current monitoring iteration. At step/operation804, for each hierarchical entity whose invalidation condition indicates a need for invalidating the entity, the hierarchical database computing entity106invalidates the corresponding hierarchical entity and all its dependent hierarchical entities. At step/operation805, for each hierarchical entity whose invalidation condition does not indicate a need for invalidating the entity but whose condition indicates a need for adding new dependent hierarchical entities for the corresponding hierarchical entity, the hierarchical database computing entity106adds new entity tracking data objects for the new dependent hierarchical entities for the corresponding hierarchical entity.

FIG. 9is a flowchart diagram of an example process900for generating a membership accounting report for a membership information database. Via the various steps/operations of process900, the hierarchical database computing entity106can perform membership accounting in an effective and efficient manner. While various embodiments of the process900are described with reference to a health insurance member insurance information database, a person of ordinary skill in the art will recognize that the disclosed techniques can be utilized for any membership insurance database storing data associated with other membership contexts. In some embodiments, the hierarchical database computing entity106repeats the steps/operations902-905described below for each temporal unit associated with a current monitoring iteration (e.g., each month for a period of 48 months prior to a time associated with the current monitoring iteration).

The process900begins at step/operation901when the hierarchical database computing entity106creates a new monitoring report iteration identified by a unique identifier R. In some embodiments, the hierarchical database computing entity106then retrieves a list of member group contract plan options for the current month M that have not previous been reported. At step/operation902, for each new member group contract plan option valid for M, the hierarchical database computing entity106adds the member group contract plan option as a child of the current iteration of the report. In some embodiments, the hierarchical database computing entity106sets iteration identifier for each child is set to R.

In some embodiments, the hierarchical database computing entity106then retrieves a list of member group contract plan options previously reported for M. At step/operation903, for each previously reported plan option, if any of the attributes of the member group contract plan option have changed, or if the member group contract plan option is no longer valid, the hierarchical database computing entity106invalidates the member group contract plan option, setting the invalidation iteration identifier to R. The purpose of this invalidation identifier may to create the audit trail between each report iteration's plan option instance, forming a chain between instances of a given plan option. This will invalidate all associated benefit plan and membership child records, traversing according to the process flow. The membership counts associated to the membership are reversed with −1 counts for the previously reported +1 counts. In some embodiments, if the invalidation was due to an attribute change, the hierarchical database computing entity106generates new member group contract plan option structure, storing the iteration identifier R as the iteration in which the plan option instance was created.

At step/operation904, if a plan option was not invalidated due to becoming invalid or an attribute change, the hierarchical database computing entity106traverses structure to the benefit plan level for each benefit plan previously reported under the plan option. In some embodiments, for each benefit plan, if any of the attributes of the benefit plan have changed, or if the benefit plan is no longer valid, the hierarchical database computing entity106invalidates the benefit plan, setting the invalidation iteration identifier to R. The purpose of this invalidation identifier is to create the audit trail between each report iteration's benefit plan instance, forming a chain between instances of a given plan option. This will invalidate all associated membership child records, traversing according to the process flow. The membership counts associated to the membership are reversed with −1 counts for the previously reported +1 counts. Please note the plan option for the previously reported iteration maintains validity. In some embodiments, if the invalidation was due to an attribute change, the hierarchical database computing entity106generates a new member benefit plan structure, storing the iteration identifier R as the iteration in which the benefit plan instance was created.

At step/operation905, if the plan option was not invalidated due to becoming invalid or an attribute change, the hierarchical database computing entity106traverses the structure to the membership level for each member previously reported under the plan option. In some embodiments, for each member, if any of the attributes of the member have changed, or if the member is no longer valid, the hierarchical database computing entity106invalidates the member, setting the invalidation iteration identifier to R. The purpose of this invalidation identifier is to create the audit trail between each report iteration's member instance, forming a chain between instances of a member. The membership counts associated to the member are reversed with −1 counts for the previously reported +1 counts. Please note that the plan option for the previously reported iteration maintains validity, as does the previously reported benefit plan, maintaining those chains, while attaching the new member. In some embodiments, if the invalidation was due to an attribute change, the hierarchical database computing entity106generates a new member, storing the iteration identifier R as the iteration in which the member instance was created.