A cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights

By constructing a unified ownership ontology model and a spatial topology conflict detection module, the problem of low efficiency in cross-database queries of real estate ownership, forest rights, and land contract management rights has been solved, and automatic conflict detection and synchronization have been achieved, improving data consistency and management efficiency.

CN123115166APending Publication Date: 2026-11-17GUIZHOU SIYOU SPACE TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611403986.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-10
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, data on real estate ownership, forest rights, and land contract management rights are stored in databases of different departments, resulting in low efficiency of cross-database queries, inability to automatically detect ownership conflicts, and a lack of cross-database linkage and synchronization mechanisms, leading to data inconsistency and management chaos.

Method used

A unified ownership ontology model is constructed by employing a multi-source data access module, a unified ownership ontology database construction module, a spatial topology conflict detection module, and a linkage change synchronization module. Conflicts are identified through spatial topology relationships, and automatic synchronization of ownership changes is achieved.

Benefits of technology

It enables unified management of cross-database ownership data, automatically detects and promptly handles conflicts, improves query efficiency and data consistency, supports ownership chain tracing and cross-database related views, and adapts to the management requirements of different regions and departments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123115166A_ABST
    Figure CN123115166A_ABST
Patent Text Reader

Abstract

This invention discloses a cross-database linkage governance and database construction system for real estate ownership, forest rights, and land contractual management rights, relating to the field of real estate registration and natural resource data governance technology. The system includes a multi-source data access module, a unified ownership ontology database construction module, a spatial topology conflict detection module, a linkage change synchronization module, an ownership association graph module, and a governance rule engine. The unified ownership ontology database construction module constructs a unified ontology model containing the three types of ownership and maps each source data to ontology concepts; the spatial topology conflict detection module calculates the topological relationships of cross-database ownership entities based on the spatial geometric coordinates of land parcels to identify ownership conflicts; the linkage change synchronization module monitors change events in each source database and triggers change verification and synchronization of associated databases based on ontology associations. This system can achieve unified database construction and cross-database linkage governance of the three types of ownership data, which is beneficial for automatically discovering ownership conflicts and ensuring cross-database data consistency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of real estate registration and natural resource data governance technology, and in particular to a cross-database linkage governance and database construction system for real estate rights, forest rights, and land contract management rights. Background Technology

[0002] Real estate registration is handled by the natural resources department, forest tenure management by the forestry department, and land contractual management right management by the agriculture and rural affairs department. These three types of ownership data are stored in their respective independent database systems, each using different data standards, coding rules, and spatial reference coordinate systems.

[0003] In practice, a single land parcel often involves multiple types of ownership rights. For example, a piece of forest land may simultaneously have forest land use rights (belonging to the category of real estate rights), timber ownership (belonging to the category of forest rights), and forest land contract management rights (belonging to the category of land contract management rights). Because these three types of data are scattered in the databases of different departments, when it is necessary to query the complete ownership status of a certain land parcel, staff need to log in to multiple business systems to manually query and compare, which is inefficient and prone to omissions.

[0004] A more prominent problem is the inability to automatically detect cross-database ownership conflicts. When different departments register ownership of the same land parcel in their respective business systems, the lack of an automatic cross-database verification mechanism can lead to conflicts such as inconsistent rights holders, overlapping rights periods, and overlapping ownership scopes. These conflicts are usually only discovered in subsequent ownership disputes or legal proceedings, by which time management chaos and damage to the rights holders' interests have already occurred.

[0005] Furthermore, there is a lack of cross-database synchronization mechanisms for ownership changes. When an ownership change occurs in one department's business system (such as the transfer of forest rights or adjustment of land contractual management rights), the associated ownership data in other departments' databases will not be automatically updated, requiring manual notification and modification. This asynchronous update mode easily leads to data inconsistencies between databases, and these inconsistencies may persist for a considerable period.

[0006] In existing technologies, some regions have attempted to achieve data exchange between departments through data sharing and exchange platforms. However, this approach typically employs a periodic batch export and import model, resulting in poor data timeliness. Furthermore, the exchanged data remains stored in their respective databases, failing to create a unified cross-database relational view. Some studies have also proposed establishing a unified real estate registration information platform. However, these platforms primarily focus on integrating real estate registration business processes and lack targeted technical solutions for cross-database collaborative governance of forest rights and land contractual management rights. In particular, existing technologies have not yet provided effective solutions for automatic conflict detection based on spatial topology and event-driven collaborative change synchronization. Summary of the Invention

[0007] This invention provides a cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights to solve the problems raised in the background technology.

[0008] To solve the above-mentioned technical problems, the present invention adopts the following technical solution: A cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights includes a multi-source data access module, a unified ownership ontology database construction module, a spatial topology conflict detection module, and a linkage change synchronization module. The multi-source data access module connects to the real estate registration database, forest rights management database, and land contractual management rights database, respectively, and is used to extract ownership data from each database. The unified ownership ontology database construction module connects to the multi-source data access module and is used to construct a unified ownership ontology model encompassing the three ownership concepts of real estate rights, forest rights, and land contractual management rights. It converts the ownership data extracted from each database into ontological ownership data according to field mapping relationships and stores it in the ontological ownership database. The spatial topology conflict detection module connects to the unified ownership ontology database construction module and is used to calculate the spatial topology relationships between ownership entities of different ownership types based on the spatial geometric coordinates of each ownership entity in the ontological ownership data. Based on the spatial topology relationship determination results, it identifies cross-database ownership conflicts and generates conflict records. The linkage change synchronization module is connected to the multi-source data access module and the unified ownership ontology database building module, respectively. It is used to monitor ownership change events in each source database, determine the affected related ownership entities based on the association relationship of the ownership entities involved in the change event in the unified ownership ontology model, initiate a change verification request to the corresponding source database, and update the status of the related ownership entities in the ontology database after the verification is passed.

[0009] In one implementation, the unified ownership ontology model includes ownership entity classes, right type classes, land parcel spatial classes, and right subject classes. Ownership entity classes and right type classes are connected through type attribution relationships; ownership entity classes and land parcel spatial classes are connected through spatial location relationships; and ownership entity classes and right subject classes are connected through right attribution relationships. Right type classes include subclasses for real estate rights, forest rights, and land contractual management rights, with corresponding right nature sub-nodes set under each subclass. The unified ownership ontology database construction module maps the right type field from the ownership data of each source database to the corresponding sub-node of the right type class, maps the right holder field to the right subject class, and maps the land parcel location or boundary coordinate field to the land parcel spatial class.

[0010] In one implementation, the spatial topology conflict detection module includes a coordinate unification unit, a topology calculation unit, and a conflict determination unit. The coordinate unification unit transforms the spatial geometric coordinates of the land parcels of each source database ownership entity to a unified spatial reference coordinate system. The topology calculation unit performs spatial overlay analysis on ownership entities of different ownership types after coordinate transformation, calculating the spatial topology relationships between pairs of ownership entities. These spatial topology relationships include disjoint, adjacent, intersecting, overlapping, contained, and contained. The conflict determination unit, when the spatial topology relationship between two ownership entities of different ownership types is intersecting, overlapping, contained, or contained, further compares the rights holder information and rights term information of the two ownership entities. When the rights holders are inconsistent and the rights terms overlap, it determines it as a cross-database ownership conflict and generates a conflict record containing the conflict type, the identifiers of the involved ownership entities, the spatial overlap range, and the conflict level.

[0011] In one implementation, the linkage change synchronization module includes an event listening unit, a correlation analysis unit, a change verification unit, and a synchronization execution unit. The event listening unit listens for ownership change events in each source database via a message queue. Ownership change events include the addition, modification, cancellation, and mortgaging of ownership entities. The correlation analysis unit queries the unified ownership ontology model for related ownership entities that have overlapping spatial locations or the same rights holder relationship, based on the ownership entity identifier in the change event. The change verification unit initiates a change verification request to the source database to which the related ownership entity belongs, verifying whether the change event affects the rights status of the related ownership entity. The synchronization execution unit, upon successful verification, updates the correlation status field of the related ownership entity in the ontology-based ownership database and sends a change synchronization notification to the corresponding source database.

[0012] In one implementation, the system further includes a property rights association graph module. This module is connected to the unified property rights ontology database module and is used to construct a cross-database property rights association graph using property rights entities in the ontological property rights data as nodes and spatial overlap relationships, identical rights holder relationships, rights inheritance relationships, and rights transfer relationships between property rights entities as edges. The module is also used to traverse paths along the relationship edges in the cross-database property rights association graph based on a specified property rights entity identifier, generating a property rights chain tracing result for that entity. This result includes the entity's historical change records, information on other associated property rights entities of different types, and the change trajectory of the rights holder.

[0013] In one implementation, the system further includes a governance rule engine. The governance rule engine is connected to both the spatial topology conflict detection module and the linkage change synchronization module, and is used to configure data quality rules, conflict resolution rules, and synchronization rules. Data quality rules include mandatory field validation rules, encoding format validation rules, and spatial coordinate validity validation rules. The governance rule engine performs quality checks on the ownership data extracted by the multi-source data access module according to the data quality rules and generates quality problem records. Conflict resolution rules include automatic conflict merging rules, conflict reporting rules, and conflict ignoring rules. The spatial topology conflict detection module classifies and handles identified cross-database ownership conflicts according to the conflict resolution rules. The linkage change synchronization module executes change synchronization operations according to the synchronization rules.

[0014] In one implementation, the multi-source data access module includes a full extraction unit, an incremental extraction unit, and a data cleaning unit. The full extraction unit extracts all historical ownership data from each source database in batches during the system initialization phase. The incremental extraction unit captures newly added or changed ownership data from each source database in real time using database change data capture technology. The data cleaning unit performs format standardization processing on the extracted ownership data, including deduplication and normalization of right holder names, verification of document type and document number formats, unification of right term and date formats, and conversion of land parcel code formats.

[0015] Therefore, the present invention has at least the following beneficial effects: First, this invention constructs a unified ownership ontology model that includes three types of ownership concepts: real estate ownership, forest rights, and land contractual management rights, through a unified ownership ontology database construction module. This maps ownership data scattered across different departments and standards into a unified ontology concept system, forming an ontology-based ownership database. This solves the problems of lacking a unified semantic model for multi-source heterogeneous ownership data and difficulty in directly linking cross-database data, providing a unified data foundation for cross-database queries and collaborative governance.

[0016] Secondly, the present invention uses a spatial topology conflict detection module to calculate the spatial topology relationship between ownership entities of different ownership types based on the spatial geometric coordinates of the land parcel, and combines the information of the right holder and the right term to determine the conflict. It can automatically discover conflict situations such as overlapping, intersecting, and inconsistent right holders across the same land parcel, which changes the existing technology that relies on manual comparison to discover conflicts and is conducive to improving the timeliness and comprehensiveness of conflict discovery.

[0017] Third, this invention constructs a cross-database ownership entity association graph through the ownership association graph module, supports path traversal along the relationship edges to generate ownership chain tracing results, and can provide complete ownership history information and cross-database association views for scenarios such as ownership dispute investigation, real estate registration review, and judicial inquiry.

[0018] Fourth, this invention enables the configurability of data quality rules, conflict resolution rules, and synchronization rules through a governance rule engine, allowing the system to adapt to the management requirements of different regions and departments, which is beneficial to improving the applicability and maintainability of the system.

[0019] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0020] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a schematic diagram of the overall system architecture of the present invention; Figure 2 A schematic diagram of the unified ownership ontology model structure; Figure 3 This is a schematic diagram of the spatial topology conflict detection process; Figure 4 This is a schematic diagram illustrating the synchronization timing of the linkage change. Figure 5 This is a schematic diagram of the cross-database ownership association structure; Figure 6 A diagram illustrating the configuration and execution process of the governance rules engine. Detailed Implementation

[0021] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0022] like Figure 1 As shown, the cross-database linkage governance and database construction system for real estate ownership, forest rights, and land contractual management rights provided in this embodiment includes a multi-source data access module, a unified ownership ontology database construction module, a spatial topology conflict detection module, a linkage change synchronization module, an ownership association graph module, and a governance rule engine. The modules interact with each other through standardized service interfaces. The system is deployed on a government cloud platform and connected to the source business systems of various departments via the government extranet.

[0023] The multi-source data access module connects to the real estate registration database, the forest tenure management database, and the land contract management right database, respectively. The real estate registration database is deployed in the natural resources authority and uses a relational database to store real estate registration data, including fields such as real estate unit number, right holder, certificate type, certificate number, right type, right nature, location, area, term of use, and registration time. Land parcel spatial data is stored in a spatial database, using polygonal geometric objects to represent the parcel boundaries. The forest tenure management database is deployed in the forestry authority and includes fields such as forest tenure certificate number, right holder, ID number, forest land ownership right holder, forest land use right holder, forest or timber ownership right holder, forest or timber use right holder, forest land area, main tree species, number of trees, forest type, forest land use period, and expiration date. The parcel boundaries are represented by spatial geometric data of small plot boundaries. The land contract management right database is deployed in the agricultural and rural affairs authorities and includes fields such as contract number, contracting party, contractor representative, contractor family members, contracted land code, land name, land area, land type, contract period, contracting method, and confirmation method. The scope of the contracted land is represented by a polygon formed by the coordinates of the boundary points.

[0024] The multi-source data access module includes a full extraction unit, an incremental extraction unit, and a data cleaning unit. The full extraction unit runs during system initialization, connecting to various source databases via JDBC and batch-reading all historical ownership data according to preset extraction SQL statements. For the real estate registration database, the extraction statements associate the main real estate registration table and the land parcel spatial table, extracting data in segments based on registration time to avoid excessive data volume in a single query. For the forest tenure management database, the extraction statements associate the forest tenure registration table and the small plot spatial table. For the land contract management right database, the extraction statements associate the contract table, the contractor table, and the contracted land parcel spatial table. The extraction progress is recorded during the full extraction process, and breakpoint resumption is supported.

[0025] The incremental extraction unit operates continuously during normal system operation, employing database change data capture technology to capture newly added or changed ownership data in each source database in real time. For databases supporting logical replication (such as PostgreSQL), change data is obtained by parsing the WAL log; for other databases, incremental data is obtained by creating change triggers in the source database or by periodically polling and updating the timestamp field. The captured incremental data is written to a message queue for consumption by downstream modules.

[0026] The data cleaning unit performs format standardization processing on the ownership data extracted in full volume and incrementally. The deduplication and standardization processing of obligee names includes: removing spaces in names, unifying full-width and half-width characters, and mapping and converting organization codes and unified social credit codes. The format verification of certificate types and certificate numbers includes: 18-digit verification of ID card numbers (including check digit verification), 9-digit verification of organization codes, and 18-digit verification of unified social credit codes. The unification of right term date formats includes: converting multiple formats such as "YYYY年MM月DD日", "YYYY-MM-DD" and "YYYYMMDD" uniformly into the ISO 8601 standard date format. The format conversion of parcel codes includes: uniformly mapping different coding rules used in each source database (such as 28-digit code of real estate unit number, forest right sub-compartment code, and contracted land parcel code) to the unique parcel identifier inside the system, and the mapping relationship is stored in the code mapping table.

[0027] As shown in Figure 2 , the unified ownership ontology database construction module constructs a unified ownership ontology model containing three types of ownership concepts: real estate ownership, forest right, and land contracted management right. The ontology model is defined using the OWL DL description language, and includes four core classes: ownership entity class, right type class, parcel space class, and right subject class.

[0028] The ownership entity class is the core class of the ontology model, representing each specific ownership registration record. The ownership entity class has data properties: ownership entity identifier (unique internal ID of the system), source database identifier (indicating whether the data comes from the real estate registration database, forest right management database, or land contracted management right database), source record number (original record number in the source database), registration time, cancellation time, and right status (valid, cancelled, mortgaged, sealed up). The ownership entity class and the right type class are connected through the object property "type affiliation", and each ownership entity belongs to one right type instance. The ownership entity class and the parcel space class are connected through the object property "spatial location", and each ownership entity corresponds to one parcel space instance. The ownership entity class and the right subject class are connected through the object property "right affiliation", and each ownership entity corresponds to one or more right subject instances (when the right is jointly owned by multiple obligees).

[0029] The rights type classification adopts a hierarchical structure. The top level is the rights type class, which is further divided into three first-level subclasses: real estate rights, forest rights, and land contractual management rights. The real estate rights subclass includes sub-nodes indicating the nature of the rights: state-owned construction land use rights, collective construction land use rights, homestead land use rights, land contractual management rights (registered with the natural resources department), forest land use rights, house ownership, and building ownership. The forest rights subclass includes sub-nodes indicating the nature of the rights: forest land ownership, forest land use rights, forest or timber ownership, and forest or timber use rights. The land contractual management rights subclass includes sub-nodes indicating the nature of the rights: family contractual management rights, contractual management rights obtained through bidding, auction, or public negotiation, and land management rights. Each rights type instance has the following data attributes: type code, type name, applicable legal basis, and registration department.

[0030] A land parcel spatial class represents the spatial extent of a land parcel corresponding to a property rights entity. A land parcel spatial class has the following data attributes: unique parcel identifier, parcel name, parcel area (square meters), spatial geometric object (a polygonal geometry represented in WKT format), coordinate system identifier, land category code, and land category name. Land parcel spatial classes are connected by spatial adjacency through object attribute spaces, and by inclusion through object attribute spaces, they connect parcels with an inclusive relationship (such as independent courtyards contained within a parcel).

[0031] The "Rights Subject" category represents the rights holder. This category is further divided into two subcategories: Natural Persons and Legal Persons or Unincorporated Organizations. The Natural Persons subcategory has the following data attributes: Name, ID Type, ID Number, Gender, Date of Birth, and Place of Residence. The Legal Persons or Unincorporated Organizations subcategory has the following data attributes: Name, ID Type (Unified Social Credit Code / Organization Code), ID Number, Legal Representative, and Registered Address. Rights Subjects are connected through the kinship attribute (used for family members of the contractor in land contract management rights) and through the representation attribute, connecting the contractor's representative with other family members.

[0032] The unified ownership ontology database module converts ownership data extracted from various source databases into ontological ownership data according to field mapping relationships. Field mapping relationships are defined through a mapping configuration file, with each source database corresponding to a set of mapping rules. Taking the real estate registration database as an example, the mapping rules include: the real estate registration number is mapped to the source record number of the ownership entity; the right type field value is mapped to the corresponding instance in the right type class; the right holder field is mapped to an instance of the right subject class, with deduplication matching performed using the document number; the location and boundary coordinates of the land parcel are mapped to an instance of the land parcel spatial class; and fields such as registration time and cancellation time are directly mapped to the corresponding data attributes of the ownership entity. During the mapping process, for cases where the same right subject appears in different source databases, entity alignment is performed using a combination of document type and document number, merging them into the same right subject instance. For cases where the same land parcel appears in different source databases, land parcel matching is performed through spatial geometric overlay analysis. When the spatial overlap area of ​​two land parcels exceeds a preset threshold (design target is 90%), they are determined to be the same land parcel and merged into the same land parcel spatial instance.

[0033] The transformed ontological ownership data is stored in an ontological ownership repository. This repository uses a graph database to store the classes, instances, and relationships of the ontology model, while employing a relational database to store detailed attribute data of ownership entities to support efficient conditional queries. The graph database and the relational database are linked through ownership entity identifiers.

[0034] like Figure 3 As shown, the spatial topology conflict detection module includes a coordinate unification unit, a topology calculation unit, and a conflict determination unit.

[0035] The coordinate unification unit transforms the spatial geometric coordinates of land parcels belonging to various source database entities to a unified spatial reference coordinate system. This embodiment uses the 2000 National Geodetic Coordinate System (CGCS2000) as the unified spatial reference. For land parcel data whose original coordinate system is the 1980 Xi'an Coordinate System, a seven-parameter Bursa model is used for coordinate transformation, with transformation parameters determined based on the surveying control point data of each region. For land parcel data whose original coordinate system is the 1954 Beijing Coordinate System, it is first transformed to the 1980 Xi'an Coordinate System and then to the 2000 National Geodetic Coordinate System. For land parcel data already using the 2000 National Geodetic Coordinate System, it can be used directly without transformation. During the coordinate transformation process, the original coordinate system identifier and transformation parameter version are recorded for subsequent traceability. The area of ​​the transformed spatial geometric data is recalculated and compared with the original area. When the area difference exceeds a preset threshold (design target is 1%), a coordinate transformation anomaly record is generated.

[0036] The topology calculation unit performs spatial overlay analysis on ownership entities of different ownership types after coordinate transformation. To improve computational efficiency, the topology calculation unit first uses a spatial index (such as an R-tree index) to index the land parcel spatial data. Then, based on the spatial index, it filters out ownership entity pairs whose spatial extents may intersect. Finally, it performs precise spatial topological relationship calculations on the filtered entity pairs. The determination of spatial topological relationships follows the dimension-extended nine-intersection model (DE-9IM), calculating the relationship type between pairs of ownership entities, including: disjoint (two land parcels have no intersection), adjacent (two land parcels only touch at the boundary and have no internal intersection), intersecting (two land parcels have internal intersection but do not contain each other), overlapping (two land parcels have similar areas and have a large internal intersection), containing (one land parcel's spatial extent completely contains another land parcel), and being contained (the reverse of the containment relationship). The topology calculation unit only performs calculations on ownership entity pairs of different ownership types (i.e., between real estate ownership entities and forest ownership entities, between real estate ownership entities and land contract management right ownership entities, and between forest ownership entities and land contract management right ownership entities). Ownership entity pairs within the same ownership type are not subject to cross-database conflict detection (conflicts within the same database are handled by each source business system).

[0037] The conflict determination unit further determines conflicts between ownership entity pairs that have spatial intersections, as output by the topology calculation unit. When the spatial topological relationship between two ownership entities of different ownership types is intersecting, overlapping, containing, or being contained, the conflict determination unit further compares the rights holder information and rights term information of the two ownership entities. Rights holder information comparison is performed through instance identifiers of rights holder classes. When the sets of rights holder instances of the two ownership entities are completely identical (i.e., the rights holders are completely the same), they are determined to be identical rights holders. In this case, even if the spatial scope overlaps, it does not constitute a conflict (multiple ownership types belonging to the same rights holder, such as the same rights holder simultaneously possessing forest land use rights and forest ownership). When the sets of rights holder instances of the two ownership entities are not completely identical, they are determined to be inconsistent rights holders. Rights term information comparison is performed by comparing the start date and end date of the rights of the two ownership entities. When there is a temporal intersection between the two rights terms (i.e., the rights period of one ownership overlaps with the rights period of another ownership), it is determined that the rights terms have an intersection. When the rights holders are inconsistent and the rights terms have an intersection, the conflict determination unit determines it to be a cross-database ownership conflict.

[0038] Conflict records include the following fields: Conflict Identifier (system-unique ID), Conflict Type (categorized into overlapping conflicts, cross conflicts, and containment conflicts based on spatial topology), Identifier 1 of Involved Ownership Entities, Identifier 2 of Involved Ownership Entities, Spatial Overlap Range (geometric overlapping area represented in WKT format), Spatial Overlap Area (square meters), Description of Differences Between Rights Holders, Intersection Range of Rights Term, Conflict Level (categorized into high, medium, and low levels based on the overlap area ratio and the degree of difference between rights holders), Detection Time, Handling Status (not handled, handling, handled), and Handling Result. The conflict level determination rules are as follows: when the spatial overlap area exceeds 50% of the smaller parcel area and the rights holders are completely different, it is determined to be a high-level conflict; when the overlap area ratio is between 20% and 50%, it is determined to be a medium-level conflict; and when the overlap area ratio is below 20%, it is determined to be a low-level conflict. These ratio thresholds are design targets and can be adjusted through the governance rule engine in practical applications.

[0039] like Figure 4 As shown, the linkage change synchronization module includes an event listening unit, a correlation analysis unit, a change verification unit, and a synchronization execution unit.

[0040] The event monitoring unit listens for ownership change events in each source database via a message queue. For source databases that support change data capture, the event monitoring unit directly consumes the change data written to the message queue by the incremental extraction unit and parses out the ownership change events. For source databases that do not support change data capture, the event monitoring unit obtains change events through an audit table. Ownership change events include: addition of ownership entities (registration of a new ownership record), modification (modification of certain fields in the ownership record, such as change of right holder, change of right term, change of land parcel scope), cancellation (ownership record is cancelled or revoked), mortgage (ownership record is mortgaged), and seizure (ownership record is judicially seized). Each change event includes: event identifier, source database identifier, source record number, change type, change time, list of changed fields, value before change, value after change, and operator information.

[0041] The association analysis unit queries other ownership entities with related relationships in the unified ownership ontology model based on the ownership entity identifier in the change event. The query for association relationships is based on object attributes in the ontology model, mainly including the following types of associations: First, overlapping spatial locations, i.e., other ownership entities of other ownership types that have spatial intersection with the spatial scope of the changed ownership entity, obtained by querying spatial adjacency and spatial inclusion relationships of the land parcel class and historical conflict records from the spatial topology conflict detection module; Second, identical rights holder relationships, i.e., other ownership entities that share the same rights holder instance with the changed ownership entity, obtained by querying the rights ownership relationship of the rights holder class in reverse; Third, relationship edges in the ownership association graph, i.e., cross-database association relationships constructed through the ownership association graph module, including rights inheritance relationships and rights transfer relationships. The association analysis unit groups the queried related ownership entities by association type and calculates the association strength (spatial overlap area ratio, degree of rights holder overlap, etc.) between each related ownership entity and the change event, sorting them in descending order of association strength.

[0042] The change verification unit initiates a change verification request to the source database of the associated ownership entity. The request is sent to the corresponding department's business system via a standardized web service interface. The request includes: detailed information about the change event, the identifier and current status of the associated ownership entity, and the specific items to be verified. The verification items vary depending on the change type: when the change type is a change of rights holder, it verifies whether the rights holder of the associated ownership entity needs to be changed simultaneously; when the change type is a change of land parcel scope, it verifies whether the land parcel scope of the associated ownership entity is affected and whether it needs to be re-verified; when the change type is a change of rights term, it verifies whether the rights term of the associated ownership entity needs to be adjusted accordingly; when the change type is cancellation, it verifies whether the associated ownership entity is still valid and whether it needs to be cancelled in conjunction with other entities. Upon receiving the verification request, the corresponding source database's business system reviews it using business personnel or automated verification rules and returns the verification result. The result includes: whether synchronization is required, the specific content to be synchronized, the synchronization deadline, and the reviewer's information.

[0043] Upon receiving a successful verification response, the synchronization execution unit performs a synchronization operation. This operation comprises two levels: First, updating the association status field of related ownership entities in the ontological ownership database. The association status field identifies the association status of the ownership entity with other ownership entities, including: whether cross-database association exists, a list of related ownership entity identifiers, the time of the most recent association change, and the consistency status of the association data (consistent, pending synchronization, synchronized, synchronization failed). When an ownership entity involved in a change event changes, the synchronization execution unit updates the consistency status of the association data of all related ownership entities to synchronized and records the synchronization time and a summary of the synchronization content. Second, sending a change synchronization notification to the corresponding source database. The synchronization notification is sent to the business system of the source database to which the related ownership entity belongs via a message queue or web service interface. The notification content includes: a summary of the change event, the identifier of the related ownership entity, and the suggested synchronization operation content. After receiving the notification, the business personnel in the source database determine whether corresponding modifications need to be made in the source database.

[0044] like Figure 5 As shown, the ownership association graph module uses ownership entities in the ontological ownership data as nodes and the relationships between ownership entities as edges to construct a cross-database ownership association graph.

[0045] The nodes in the graph are instances of ownership entities. Each node carries basic attribute information of the ownership entity, including ownership entity identifier, right type, right holder name, land parcel name, land parcel area, right term, right status, and source database identifier. Nodes are divided into three categories according to right type, each distinguished by different visual identifiers (real estate ownership node, forest rights node, and land contract management right node) to intuitively display the cross-database relationship structure when the graph is visualized.

[0046] The edges in the graph represent the relationships between ownership entities, including the following categories: First, spatial overlap edges connect ownership entities of different ownership types whose land parcels overlap spatially; the weight of the edge is the proportion of the overlapping area to the smaller parcel area. Second, edges representing entities sharing the same right holder connect ownership entities; the weight of the edge is the proportion of the number of entities sharing the same right holder. Third, edges representing inheritance relationships connect ownership entities with inheritance relationships (e.g., ownership acquired by a new right holder after the death of the original right holder); the direction of the edge is from the original ownership entity to the inherited ownership entity. Fourth, edges representing transfer relationships connect ownership entities with transfer relationships (e.g., forest tenure transfer, land contract management right transfer); the direction of the edge is from the transferring ownership entity to the receiving ownership entity. Each edge carries attributes such as relationship type, relationship establishment time, relationship source (automatic detection / manual annotation), and relationship confidence level.

[0047] The ownership association graph module uses a graph database to store graph data and supports incremental updates. When a new ownership entity is added to the ontological ownership database, the graph module automatically creates a new node and automatically establishes spatial overlap edges and rights-shared edge edges based on spatial overlap analysis and rights-subject matching results. When an ownership entity changes or is cancelled, the graph module updates the node attributes accordingly and re-evaluates the affected edges. Rights inheritance edges and rights transfer edges are mainly established through manual annotation or automatic extraction from the transfer registration records in the source database.

[0048] The ownership association graph module provides ownership chain tracing functionality. When a user inputs a specified ownership entity identifier, the graph module traverses the path along the relationship edges in the cross-database ownership association graph. The traversal uses a breadth-first search algorithm, starting from the specified node and expanding outwards along all types of relationship edges. The traversal depth is configurable (the design target is 3 layers by default). During the traversal, all nodes and edges visited are recorded, generating ownership chain tracing results. The tracing results contain two parts: First, information on other related ownership entities, listing real estate rights, forest rights, and land contract management rights entities that are directly or indirectly related to the specified entity, including basic information and relationship types of each entity; Second, the change trajectory of the rights holders, showing the changes in the rights holders involved in the ownership over time through historical association records of the rights holder class. The tracing results can be displayed in a graph visualization format, with nodes and edges arranged in chronological order. Users can interactively view detailed information for each node and edge.

[0049] like Figure 6 As shown, the governance rule engine is used to configure and execute various rules related to data governance. The governance rule engine adopts a rule-driven architecture, separating rules from execution logic. Rules are managed through a visual configuration interface or rule definition files, allowing governance strategies to be adjusted without modifying system code.

[0050] Data quality rules are used to verify the quality of ownership data extracted by the multi-source data access module. These rules include: mandatory field verification rules, which define a list of fields that must be filled in for each ownership type (e.g., for real estate ownership, the real estate unit number, right holder, right type, location, area, and term of use must be filled in). A quality problem record is generated when any of the mandatory fields in the extracted data are empty. Encoding format verification rules define the format requirements for various codes (e.g., 28-digit code for real estate unit number, 18-digit ID card number, and 18-digit alphanumeric combination for unified social credit code). A quality problem record is generated and an attempt is made to automatically correct the encoding format when it does not meet the requirements (e.g., increasing the ID card number from 15 digits to 18 digits). Spatial coordinate validity verification rules define the validity requirements for the spatial geometric data of the land parcel (e.g., polygons must be closed, the number of coordinate points must be no less than 3, the area must be greater than 0, and the coordinate values ​​must be within the administrative region). A quality problem record is generated when the spatial data is invalid. The execution result of the data quality rules generates a quality problem record, which includes a problem identifier, ownership entity identifier, problem type, problem field, problem description, severity level (fatal / serious / moderate / warning), and handling status. Quality issues are recorded and sent to data governance personnel for review and correction. The corrected data is then re-entered into the ontology database creation process.

[0051] Conflict resolution rules are used to classify and handle cross-database ownership conflicts identified by the spatial topology conflict detection module. These rules include: automatic conflict merging rules, defining the conditions under which the system can automatically merge conflicts (e.g., when two ownership entities are actually the same person but are judged as different entities due to name spelling differences, and the spatial overlap exceeds 95%, the system automatically aligns the ownership entities and merges the conflict records); conflict reporting rules, defining the conditions under which conflicts need to be reported to higher-level management departments or cross-departmental coordination mechanisms (e.g., high-level conflicts, complex conflicts involving multiple rights holders, conflicts that cannot be resolved by automatic rules); and conflict ignoring rules, defining the conditions under which conflicts can be marked as ignored (e.g., verified as legitimate ownership overlap, overlap within the allowable error range, conflicts resolved through other means). The execution of these conflict resolution rules is linked to the spatial topology conflict detection module. Upon detecting a conflict, the module automatically matches the applicable resolution rules and executes the corresponding actions. Conflicts that cannot be automatically resolved enter the manual resolution process, where they are investigated and handled by the cross-departmental ownership dispute coordination agency.

[0052] Synchronization rules are used to control the synchronization behavior of the linkage change synchronization module.

[0053] The governance rules engine provides rule version management functionality, generating a new rule version each time a rule is modified.

[0054] In this embodiment, the operation flow of each module of the system is as follows: During the system initialization phase, the full extraction unit of the multi-source data access module extracts all historical ownership data in batches from the three source databases. After standardization processing by the data cleaning unit, the data is sent to the unified ownership ontology database construction module. The unified ownership ontology database construction module converts the data into ontological ownership data according to the field mapping relationship, performs entity alignment of rights subjects and spatial matching of land parcels, and stores it in the ontological ownership database. The spatial topology conflict detection module performs spatial topology calculation and conflict determination on all cross-database ownership entity pairs in the ontological ownership database and generates initial conflict records. The ownership association map module constructs an initial cross-database ownership association map based on the ontological ownership data and conflict records.

[0055] During normal system operation, the incremental extraction unit of the multi-source data access module captures changed data from each source database in real time. After data cleaning, the data is sent to the unified ownership ontology database creation module to update the ontological ownership database. The event listening unit of the linkage change synchronization module captures change events, the association analysis unit queries related ownership entities, the change verification unit initiates a verification request to the corresponding source database, and the synchronization execution unit updates the ontological ownership database and sends a synchronization notification after the verification is passed. The spatial topology conflict detection module performs incremental conflict detection on newly added or changed ownership entities and updates conflict records. The ownership association graph module incrementally updates graph nodes and edges. The governance rule engine performs data quality verification, conflict handling, and synchronization control according to the configured rules in each of the above stages.

[0056] The present invention and its embodiments have been described above. This description is not restrictive, and practical applications are not limited thereto. In conclusion, if those skilled in the art, inspired by this description, design similar structures and embodiments without departing from the spirit of the invention, such designs should fall within the scope of protection of this invention.

Claims

1. A cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights, characterized in that, It includes a multi-source data access module, a unified ownership ontology database construction module, a spatial topology conflict detection module, and a linkage change synchronization module; The multi-source data access module is connected to the real estate registration database, the forest tenure management database, and the land contract management right database respectively, and is used to extract ownership data from each source database; The unified ownership ontology database construction module is connected to the multi-source data access module and is used to construct a unified ownership ontology model that includes three types of ownership concepts: real estate ownership, forest rights and land contract management rights. The ownership data extracted from each source database is converted into ontological ownership data according to the field mapping relationship and stored in the ontological ownership database. The spatial topology conflict detection module is connected to the unified ownership ontology database module. It is used to calculate the spatial topology relationship between ownership entities of different ownership types based on the spatial geometric coordinates of each ownership entity in the ontology ownership data, identify cross-database ownership conflicts based on the spatial topology relationship determination results, and generate conflict records. The linkage change synchronization module is connected to the multi-source data access module and the unified ownership ontology database building module, respectively. It is used to monitor ownership change events of each source database, determine the affected related ownership entities based on the association relationship of the ownership entities involved in the change event in the unified ownership ontology model, initiate a change verification request to the corresponding source database, and update the status of the related ownership entities in the ontology ownership database after the verification is passed.

2. The cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights as described in claim 1, characterized in that, The unified ownership ontology model includes ownership entity class, right type class, land parcel space class and right subject class. The ownership entity class and right type class are connected through type affiliation relationship. The ownership entity class and land parcel space class are connected through spatial location relationship. The ownership entity class and right subject class are connected through right affiliation relationship. The rights type class includes real estate rights subclass, forest rights subclass, and land contract management rights subclass, with corresponding rights nature sub-nodes set under each subclass; The unified ownership ontology database module maps the right type field in the ownership data of each source database to the corresponding child node of the right type class, maps the right holder field to the right subject class, and maps the land parcel location or boundary coordinate field to the land parcel spatial class.

3. The cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights as described in claim 1, characterized in that, The spatial topology conflict detection module includes a coordinate unification unit, a topology calculation unit, and a conflict determination unit. The coordinate unification unit is used to transform the spatial geometric coordinates of the land parcels of each source database ownership entity to a unified spatial reference coordinate system; The topology calculation unit is used to perform spatial overlay analysis on ownership entities of different ownership types after coordinate transformation, and to calculate the spatial topology relationship between pairs of ownership entities. The spatial topology relationship includes disjoint, connected, intersecting, overlapping, containing, and being contained. The conflict determination unit is used to further compare the rights holder information and rights term information of the two rights holder entities when the spatial topological relationship between the two rights holder entities is intersecting, overlapping, containing or being contained. When the rights holders are inconsistent and the rights terms overlap, it is determined to be a cross-database rights holder conflict and a conflict record containing the conflict type, the identity of the rights holder entity involved, the spatial overlap range and the conflict level is generated.

4. The cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights as described in claim 1, characterized in that, The linkage change synchronization module includes an event monitoring unit, a correlation analysis unit, a change verification unit, and a synchronization execution unit; The event listening unit is used to listen for ownership change events of each source database through a message queue. The ownership change events include the addition, modification, cancellation and mortgaging of ownership entities. The association analysis unit is used to query related ownership entities in the unified ownership ontology model based on the ownership entity identifier in the change event, which have overlapping spatial location relationships or the same rights subject relationship with the ownership entity. The change verification unit is used to initiate a change verification request to the source database to which the associated ownership entity belongs, and to verify whether the change event affects the rights status of the associated ownership entity. The synchronization execution unit is used to update the association status field of the associated ownership entity in the ontological ownership library after the verification is passed, and send a change synchronization notification to the corresponding source library.

5. The cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights as described in claim 1, characterized in that, It also includes a property rights association graph module, which is connected to the unified property rights ontology database module. It is used to construct a cross-database property rights association graph with the property rights entities in the ontological property rights data as nodes and the spatial overlap relationship, the same right subject relationship, the right inheritance relationship and the right transfer relationship between the property rights entities as edges. The ownership association graph module is also used to traverse the path along the relationship edge in the cross-database ownership association graph according to the specified ownership entity identifier, and generate the ownership chain tracing result of the ownership entity. The ownership chain tracing result includes the historical change record of the ownership entity, information of other related ownership types of ownership entities, and the change trajectory of the right holder.

6. The cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights as described in claim 1, characterized in that, It also includes a governance rule engine, which is connected to the spatial topology conflict detection module and the linkage change synchronization module, respectively, and is used to configure data quality rules, conflict handling rules and synchronization rules. The data quality rules include mandatory field validation rules, encoding format validation rules, and spatial coordinate validity validation rules. The governance rule engine performs quality validation on the ownership data extracted by the multi-source data access module according to the data quality rules and generates quality problem records. The conflict handling rules include automatic conflict merging rules, conflict reporting rules, and conflict ignoring rules. The spatial topology conflict detection module classifies and handles the identified cross-database ownership conflicts according to the conflict handling rules. The linkage change synchronization module performs change synchronization operations according to the synchronization rules.

7. The cross-database linkage governance and database construction system for real estate rights, forest rights, and land contractual management rights as described in claim 1, characterized in that, The multi-source data access module includes a full extraction unit, an incremental extraction unit, and a data cleaning unit; The full extraction unit is used to extract all historical ownership data from each source database in batches during the system initialization phase. The incremental extraction unit is used to capture newly added or changed ownership data in each source database in real time through database change data capture technology. The data cleaning unit is used to standardize the extracted ownership data, including deduplication and standardization of right holder names, verification of document type and document number formats, unification of right term and date formats, and conversion of land parcel code formats.

8. A method for cross-database coordinated management and database construction of real estate rights, forest rights, and land contractual management rights, characterized in that, Includes the following steps: S1. Extract ownership data from the real estate registration database, forest tenure management database, and land contract management right database respectively; S2. Construct a unified ownership ontology model that includes three types of ownership concepts: real estate ownership, forest rights, and land contract management rights. Convert the extracted ownership data from each source database into ontology-based ownership data according to the field mapping relationship and store it in the ontology-based ownership database. S3. Based on the spatial geometric coordinates of each ownership entity in the ontological ownership data, calculate the spatial topological relationship between ownership entities of different ownership types, identify cross-database ownership conflicts based on the spatial topological relationship determination results, and generate conflict records. S4. Monitor ownership change events of each source library, determine the affected related ownership entities based on the association relationship of the ownership entities involved in the change event in the unified ownership ontology model, initiate a change verification request to the corresponding source library, and update the status of the related ownership entities in the ontology ownership library after the verification is passed.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the cross-database linkage governance and database construction method for real estate rights, forest rights, and land contractual management rights as described in claim 8.