CN110599372A - Method, device and system for managing house ticket data - Google Patents
Method, device and system for managing house ticket data Download PDFInfo
- Publication number
- CN110599372A CN110599372A CN201910743658.4A CN201910743658A CN110599372A CN 110599372 A CN110599372 A CN 110599372A CN 201910743658 A CN201910743658 A CN 201910743658A CN 110599372 A CN110599372 A CN 110599372A
- Authority
- CN
- China
- Prior art keywords
- data
- house
- ticket
- registration
- appointment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000012790 confirmation Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 7
- 230000001360 synchronised effect Effects 0.000 claims description 3
- 238000007726 management method Methods 0.000 abstract description 63
- 238000013523 data management Methods 0.000 abstract description 19
- 230000008859 change Effects 0.000 abstract description 10
- 230000002596 correlated effect Effects 0.000 abstract description 8
- 230000000875 corresponding effect Effects 0.000 description 30
- 238000010586 diagram Methods 0.000 description 14
- 238000013480 data collection Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 238000012550 audit Methods 0.000 description 3
- 230000006399 behavior Effects 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 239000000370 acceptor Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000012776 electronic material Substances 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 238000007789 sealing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/18—Legal services
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Tourism & Hospitality (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Marketing (AREA)
- Human Resources & Organizations (AREA)
- Primary Health Care (AREA)
- Strategic Management (AREA)
- General Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Economics (AREA)
- Health & Medical Sciences (AREA)
- Technology Law (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention is suitable for the field of information management and provides a method, a device and a system for managing house ticket data, wherein the method comprises the following steps: acquiring house appointment data through a first data interface, wherein the appointment data comprise an appointment number and an appointment date; acquiring house registration data through a second data interface, wherein the registration data comprises a ticket number and a registration date; and adding the appointment data and the registration data to a management time axis of the house ticket data for association based on the appointment date and the sequence of the registration date, and storing the management time axis in a shared database. The house appointed data and the house registration data are correlated, the appointed number is used as a starting point, the ticket number is used as an end point, the follow-up registration state change is conveniently tracked and managed in real time, the uniqueness of owner information can be confirmed without manually inquiring in a large quantity, and the house data management efficiency is improved.
Description
Technical Field
The invention relates to the field of data management, in particular to a method, a device and a system for managing house ticket data.
Background
The house right certificate can also be called as a house property right certificate or a house ownership certificate, and is a unique legal certificate for protecting the house owner, and protecting the house owner, namely, the house right person legally owns the house right and plays the right of possession, use, income and punishment of the house. The existing house property trading is divided into two parts, namely a house property trading part and a house property registering part which are respectively responsible for two management departments, the house property trading is filing confirmation facing market behaviors, the house property registering is administrative registration facing government authority, and the two parts of data have precedence relationship, namely the data of house property trading is required to be generated, so that the house property registering can be carried out. In the process, paper archive management is mostly adopted, when filing is carried out, corresponding related materials are usually put into the same file bag for storage, after multiple transactions of the same property occur, when the uniqueness of the owner information of the current property needs to be confirmed, a large amount of archive data needs to be inquired to determine the uniqueness of the owner information, and the uniqueness cannot be confirmed quickly and in real time. Therefore, the existing house data has a problem of low management efficiency.
Disclosure of Invention
The embodiment of the invention provides a method, a device and a system for managing house ticket data, and aims to solve the problem of low management efficiency of existing house data.
The embodiment of the present invention is implemented as follows, and in a first aspect, the present invention provides a method for managing house ticket data, where the method includes the following steps:
acquiring house appointment data through a first data interface, wherein the appointment data comprise an appointment number and an appointment date;
acquiring house registration data through a second data interface, wherein the registration data comprises a ticket number and a registration date;
and adding the appointment data and the registration data to a management time axis of the house ticket data for association based on the appointment date and the sequence of the registration date, and storing the management time axis in a shared database.
Still further, the method further comprises:
acquiring house request data of a third party, wherein the request data comprises request content and request date;
and adding the request data into the management time shaft according to the request date.
Still further, prior to the step of obtaining premise appointment data, the method comprises:
inquiring a corresponding management time axis according to the serial number of the ticket to be agreed, and judging whether the right state of the serial number of the ticket to be agreed is a limited right state or not;
and if the right state of the to-be-agreed ticket number is not the limited right state, acquiring the house agreement data based on the to-be-agreed ticket number.
Still further, the method further comprises:
and if the right state of the ticket number to be agreed is the limited right state, sending a prompt that the right state is the limited right state.
Still further, the method further comprises:
polling the shared database regularly for data update;
if the data updating exists, the updating data in the shared database is pulled through the message queue, and the pulled updating data is synchronized to the intermediate database;
and carrying out information push on the updated data based on the data of the intermediate database.
Further, the step of storing the management timeline in a shared database specifically includes:
acquiring the house appointment data and house registration data associated on the management time axis;
forming mirror image view data by the house appointment data and the house registration data which are related on the management time axis;
storing the mirror view data in the shared database.
In a second aspect, the present invention also provides an apparatus for managing house ticket data, the apparatus comprising:
the first acquisition module is used for acquiring the house appointment data through a first data interface, wherein the appointment data comprise an appointment number and an appointment date;
the second acquisition module is used for acquiring house registration data through a second data interface, and the registration data comprises a ticket number and a registration date;
and the association sharing module is used for adding the appointed data and the registration data to a management time axis of the house ticket data for association based on the appointed date and the sequence of the registration date, and storing the management time axis in a shared database.
Still further, the apparatus comprises:
the third acquisition module is used for acquiring house request data of a third party, and the request data comprises request content and request date;
and the adding module is used for adding the request data into the management time shaft according to the request date.
Still further, the apparatus further comprises:
the judging module is used for inquiring the corresponding management time shaft according to the serial number of the ticket to be agreed and judging whether the right state of the serial number of the ticket to be agreed is the limited right state or not;
and the confirmation module is used for obtaining the house appointment data based on the to-be-appointed ticket number if the right state of the to-be-appointed ticket number is not the limited right state.
Still further, the apparatus further comprises:
and the prompting module is used for sending out a prompt that the right state is the limited right state if the right state of the ticket number to be agreed is the limited right state.
Still further, the apparatus further comprises:
the polling module is used for polling the shared database at regular time to determine whether data updating exists;
the pulling module is used for pulling the update data in the shared database through the message queue if the data update exists, and synchronizing the pulled update data to the intermediate database;
and the pushing module is used for pushing the information of the updated data based on the data of the intermediate database.
Further, the association sharing module specifically includes:
an acquisition unit configured to acquire the house appointment data and the house registration data associated with each other on the management time axis;
the processing unit is used for forming the house appointment data and the house registration data which are related on the management time axis into mirror image view data;
and the storage unit is used for storing the mirror image view data in the shared database.
In a third aspect, the present invention further provides a system for managing house ticket data, including:
the system comprises at least two data acquisition devices, a data processing device and a data processing device, wherein the data acquisition devices are respectively used for generating house appointment data and house registration data; and
a management apparatus for house ticket data according to any one of the embodiments of the present invention.
Still further, the system further comprises:
and the third-party data acquisition device is used for generating the house request data.
In the embodiment of the invention, the house appointed data and the house registration data are correlated, the appointed number is used as the starting point, the ticket number is used as the terminal point, and a life cycle of the house ticket is formed, so that the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is conveniently tracked and managed in real time, the uniqueness of owner information can be confirmed without manually inquiring a large amount, and the house data management efficiency is improved.
Drawings
Fig. 1 is a schematic flow chart of a method for managing house ticket data according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of another house ticket data management method according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating another method for managing property ticket data according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating another method for managing property ticket data according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating another method for managing property ticket data according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating step 103 of FIG. 1 according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a management apparatus for house ticket data according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of a management apparatus for house ticket data according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of another house ticket data management apparatus according to an embodiment of the present invention;
fig. 10 is a schematic structural view of another house ticket data management apparatus according to an embodiment of the present invention;
fig. 11 is a schematic structural view of another house ticket data management apparatus according to an embodiment of the present invention;
FIG. 12 is a schematic diagram of a structure of the generating module 703 in FIG. 7 according to an embodiment of the present invention;
fig. 13 is a schematic structural diagram of a system for managing house ticket data according to an embodiment of the present invention;
fig. 14 is a schematic configuration diagram of another house ticket data management system according to the embodiment of the present invention;
fig. 15 is a schematic configuration diagram of another house ticket data management system according to the embodiment of the present invention;
fig. 16 is a flowchart node diagram of a method for managing house ticket data according to an embodiment of the present invention;
fig. 17 is a schematic structural diagram of another house ticket data management system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The existing paper archive management is mostly adopted, when the paper archive management is used for filing, corresponding related materials are usually put into the same file bag for storage, after the same house is traded for many times, when the uniqueness of the owner information of the current house needs to be confirmed, a large amount of archive data needs to be inquired to determine the uniqueness of the owner information, the quick and real-time confirmation cannot be carried out, and the management efficiency is low. The invention relates the house appointed data and the house registration data, takes the appointed number as the starting point and the ticket number as the terminal point to form a life cycle of the house ticket, ensures the relevance, uniqueness and authenticity of the house in the transaction registration, is convenient for tracking and managing the subsequent registration state change in real time, can confirm the uniqueness of the house owner information without manually inquiring in a large quantity, and improves the efficiency of house data management.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions.
The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
Example one
Referring to fig. 1, fig. 1 is a schematic flowchart of a method for managing house ticket data according to an embodiment of the present invention, where as shown in fig. 1, the method includes the following steps:
s101, acquiring house appointment data through a first data interface, wherein the appointment data comprise an appointment number and an appointment date.
The first data interface may be an internet interface, a local area network interface, or the like, and the first data interface may respond to a request of a user and obtain data to be requested from a corresponding database. For example, the house appointment data is stored in a transaction database of a house transaction node, the first data interface may be an interface accessed to the transaction database, and may be a common interface or a dedicated interface, the common interface may use an account to perform login access, the dedicated interface may perform login access after binding an IP address, and perform access using a specific IP address, the transaction database may be a cloud database or a local database, and meanwhile, the transaction database may be understood as a complete database or a storage area dedicated to transaction data storage in the complete database. The house appointment data can be generated by a house transaction node, and can be a house buying and selling contract, a house leasing contract (in the case that a house is leased to others), and the like, and can be in a paper or electronic form; embodiments of the present invention are directed to house buying and selling contracts. The contract number may be a contract number, and the contract number has uniqueness, and the contract number is generated by the house transaction node. The appointed date refers to the appointed time between the house giving node and the house accepting node, namely the date of signing the house buying and selling contract. The user can use the appointment number to make a request to the corresponding database so as to obtain the corresponding house appointment data. Of course, in a possible embodiment, the identity of the appointed person (the emissary person or the transferee) may also be used to make a request to the corresponding database to obtain the corresponding house appointment data; in addition, the house data, such as house address, can be used to make a request to the corresponding database to obtain the corresponding house appointment data.
And S102, acquiring house registration data through a second data interface, wherein the registration data comprises a ticket number and a registration date.
The second data interface may be an internet interface, a local area network interface, or the like, and the second data interface may respond to a request of a user and obtain data to be requested from a corresponding database. For example, the house registration data is stored in a registration database of the house registration node, the first data interface may be an interface accessed to the registration database, and may be a common interface or a dedicated interface, the common interface may perform login access using an account, the dedicated interface may perform login access after binding an IP address, and perform access using a specific IP address, the registration database may be a cloud database or a local database, and meanwhile, the registration database may be understood as a complete database or a storage area dedicated to storage of the registration data in the complete database. The house registration data may be a house property ticket (real property ticket), a land use ticket, or the like. The aforementioned ticket number may be generated by the house registration node, and the aforementioned ticket number may be a house property ticket number, which has uniqueness, and which is generated by the house registration node. The registration date mentioned above refers to the time when the house-assigned node is registered at the house registration node, that is, the date of house registration. The user can make a request to the corresponding database using the ticket number to obtain the corresponding house registration data. Of course, in a possible embodiment, the identity of the transferee may also be used to make a request to the corresponding database to obtain the corresponding house registration data; in addition, house data, such as house addresses, may also be used to request from the corresponding database to obtain corresponding house registration data.
And S103, adding the appointment data and the registration data to a management time axis of the house ticket data for association based on the appointment date and the sequence of the registration date, and storing the management time axis in a shared database.
The appointment date and the registration date may be obtained in steps S101 and S102, the appointment data and the registration data are added to the management time axis of the house ticket data to be associated with each other, and it is understood that the appointment data and the registration data are sorted by time, the management time axis of the house ticket data may be a time axis formed for the house itself, that is, a set of houses corresponds to only one management time axis, in this case, a life cycle of a plurality of house tickets may exist on the management time axis, and the life cycle of the house ticket refers to one house ticket time formed by starting with an appointment number (contract number) and ending with a ticket number. Of course, in a possible embodiment, the time axis of the house ticket data may also be a time axis formed for the house ticket, for example, one ticket number corresponds to one management time axis, and when the ticket number is changed, a management time axis of a parent is generated to manage new ticket data. Through the time axis, the uniqueness of the information of the house owner can be visually determined, and a large amount of query work and time are not needed. The shared database may be a local shared database separately set, or may be a cloud database separately set. In a possible embodiment, the shared database may be the same database as the transaction database or the registration database, for example, three storage areas of transaction data, registration data and shared data are separately opened up in one database for storing three kinds of data respectively.
In the embodiment, the house appointment data and the house registration data are correlated, the appointment number is used as the starting point, the ticket number is used as the ending point, a life cycle of the house ticket is formed, the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is convenient to track and manage in real time, the uniqueness of the house owner information can be confirmed through the life cycle of the nearest house ticket on the time axis, the uniqueness of the owner information can be confirmed without manual massive inquiry, and therefore the house data management efficiency is improved.
Example two
On the basis of the first embodiment, referring to fig. 2, fig. 2 is a schematic flow chart of the second embodiment, and the method for managing the house ticket data further includes the following steps:
s201, house request data of a third party is obtained, and the request data comprises request content and request date.
S202, adding the request data into the management time shaft according to the request date.
The house request data of the third party may be based on a third party request under a new ticket, for example, based on a bank finance request or a judicial department request under the new ticket, for example, based on purchasing house loan under the new ticket, a bank finance department initiates a request for completing the mortgage registration of real property, or based on the subsequent behavior of being restricted, checked and the like by the police judicial law, the police judicial department initiates a request for completing the related registration of real property. The request data is added to the management time axis according to the request date to form a new time axis node, and when a user inquires, the house request data of a third party can be inquired. Of course, it should be appreciated that the management timeline will be updated into the shared database after the third party house request data is added. The registration of the third party premises request described above may be done in the premises registration node to produce corresponding third party premises request data.
In the embodiment, the house appointment data and the house registration data are correlated, the appointment number is used as the starting point, the ticket number is used as the ending point, a life cycle of the house ticket is formed, the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is convenient to track and manage in real time, the uniqueness of the house owner information can be confirmed through the life cycle of the nearest house ticket on the time axis, the uniqueness of the owner information can be confirmed without manual massive inquiry, and therefore the house data management efficiency is improved. In addition, the house request data of a third party is added on the management time axis, and the change of the subsequent registration state of the house under the right can be tracked in real time based on the ticket number, so that the house transaction risk is avoided, and the house circulation safety is guaranteed.
EXAMPLE III
Referring to fig. 3 on the basis of the second embodiment, fig. 3 is a schematic flow chart of the method of the third embodiment, before step S101, the method for managing the house ticket data further includes:
s301, inquiring a corresponding management time axis according to the serial number of the ticket to be agreed, and judging whether the right state of the serial number of the ticket to be agreed is a limited right state.
S302, if the right state of the to-be-agreed ticket number is not the limited right state, acquiring the house agreement data based on the to-be-agreed ticket number.
The above mentioned to-be-agreed ticket number refers to the ticket number corresponding to the transferee node, that is, the house property ticket number that can be understood as the transferee. In one possible embodiment, the corresponding management timeline may be generated by the transferor at a previous registration activity, for example, when the transferor registers the house after a transaction with the property developer. If the corresponding management time axis cannot be inquired, the corresponding archive provided by the acquirer can be prompted so as to be convenient for manual examination and verification, and thus the right of the acquirer to the acquirer corresponding to the acquirer node is guaranteed. The right state can be a normal right state and a restricted right state, and the normal right state indicates that the property right of the house is normal and clear, and the house can enter the market for circulation, can be traded and the like. The restricted right state includes a state in which mortgage, freezing, transaction restriction, sealing, etc. affect the entry of the property right into the market. If the right state of the to-be-agreed ticket number is not the limited right state, the to-be-agreed ticket number is a normal right state, the to-be-agreed ticket number can enter the market for circulation and can be traded to the assignee, and the like, at the moment, the host and the assignee can be prompted to sign a house buying and selling contract, so that house agreement data (namely the house buying and selling contract) can be generated and the house buying and selling contract can be signed in modes of face signing, network signing and the like.
In the embodiment, the house appointment data and the house registration data are correlated, the appointment number is used as the starting point, the ticket number is used as the ending point, a life cycle of the house ticket is formed, the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is convenient to track and manage in real time, the uniqueness of the house owner information can be confirmed through the life cycle of the nearest house ticket on the time axis, the uniqueness of the owner information can be confirmed without manual massive inquiry, and therefore the house data management efficiency is improved. In addition, before acquiring the house appointed data, the original property right condition of the house is confirmed through the management time axis, so that the rights and interests of the assigned nodes can be guaranteed, and the house is safer in the circulation process.
Example four
Referring to fig. 4 on the basis of the third embodiment, fig. 4 is a schematic flow chart of a method according to the fourth embodiment, and as shown in fig. 4, the method for managing house ticket data further includes:
s401, if the right state of the ticket number to be agreed is the limited right state, a prompt that the right state is the limited right state is sent out.
In a possible embodiment, if the right status of the pending right number is a restricted right status, it indicates that the pending right number is a restricted right status, for example, the house may also process a bank mortgage status, or is applied for a frozen status by a judicial department, or is applied for a restricted transaction by the judicial department, or is checked by the judicial department, and the property right of the house is unclear, and these statuses may affect the interest of the assignee after purchasing the house, and at this time, the issuer may be prompted, for example, to prompt: the method comprises the steps of generating premise appointment data (namely house buying and selling contracts) by 'the situation that the inquired house property has a mortgage and does not allow trading before the mortgage is released', and signing in modes of surface signing, net signing and the like.
In the embodiment, the house appointment data and the house registration data are correlated, the appointment number is used as the starting point, the ticket number is used as the ending point, a life cycle of the house ticket is formed, the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is convenient to track and manage in real time, the uniqueness of the house owner information can be confirmed through the life cycle of the nearest house ticket on the time axis, the uniqueness of the owner information can be confirmed without manual massive inquiry, and therefore the house data management efficiency is improved. In addition, before acquiring the house appointed data, the original property right condition of the house is confirmed through the management time axis, so that the rights and interests of the appointed nodes can be guaranteed, the house transaction risk is avoided, and the house circulation safety is guaranteed.
EXAMPLE five
On the basis of any of the above embodiments, please refer to fig. 5, fig. 5 is a schematic flow chart of a fifth method according to the embodiment, and as shown in fig. 5, the managing of the house ticket data further includes:
s501, regularly polling whether the shared database has data updating.
And S502, if data updating exists, pulling the updating data in the shared database through the message queue, and synchronizing the pulled updating data to the intermediate database.
And S503, carrying out information push on the updated data based on the data of the intermediate database.
The above-mentioned timed polling may be understood as a timed inquiry, and the above-mentioned data update may be the addition of the life cycle of the new house ticket, or the addition of data requested by a third party, etc., which is added to the management timeline. The message queue described above is used to pull multiple update data in the shared database. The intermediate database may be used to store the pulled update data, and in a possible embodiment, the intermediate database may be understood as an external shared database, that is, a shared database opened to the public, and in this case, the shared database may be understood as an internal shared database, that is, a shared database opened only to the house transaction node and the house registration node. The information that can be pulled in the shared database is non-private information such as a house property certificate number, house provenance basic information, and the like. The information pushing objects can be house supervision nodes, transaction service nodes and the like. In a possible embodiment, the premises supervision node may also make a data request to the internal shared database through the data interface.
In the embodiment, the house appointment data and the house registration data are correlated, the appointment number is used as the starting point, the ticket number is used as the ending point, a life cycle of the house ticket is formed, the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is convenient to track and manage in real time, the uniqueness of the house owner information can be confirmed through the life cycle of the nearest house ticket on the time axis, the uniqueness of the owner information can be confirmed without manual massive inquiry, and therefore the house data management efficiency is improved. In addition, the house right certificate data can be updated timely by regularly polling the shared database, regularly pulling and pushing the updated data in the shared database, and the house data management efficiency is further improved.
EXAMPLE six
On the basis of any of the above embodiments, please refer to fig. 6, fig. 6 is a schematic flow chart of a method according to a sixth embodiment, and as shown in fig. 6, the step 103 further includes:
s601, acquiring house appointment data and house registration data related to a management time axis.
And S602, forming mirror image view data by the house appointment data and the house registration data which are related on the management time axis.
And S603, storing the mirror image view data in a shared database.
After managing the related house appointment data and house registration data on the time axis, storing the corresponding data in the shared database in a mirror view mode, wherein the mirror view can be a container-based clone mirror or a snapshot. Thus, if data in the shared database is to be modified, the original storage address where the mirror image view is located needs to be found. Data in the shared database is prevented from being modified.
In the embodiment, the house appointment data and the house registration data are correlated, the appointment number is used as the starting point, the ticket number is used as the ending point, a life cycle of the house ticket is formed, the correlation, uniqueness and authenticity of the house in transaction registration are ensured, the follow-up registration state change is convenient to track and manage in real time, the uniqueness of the house owner information can be confirmed through the life cycle of the nearest house ticket on the time axis, the uniqueness of the owner information can be confirmed without manual massive inquiry, and therefore the house data management efficiency is improved. In addition, the mirror image view of the house ticket data is stored in the shared database, so that the condition that the data in the shared database is modified can be avoided, and the safety of the house ticket data is ensured.
It should be noted that the management method of the house ticket data provided by the foregoing embodiments is applied to electronic devices that can manage house ticket data for inquiry, such as electronic devices of a transaction supervision node and a house registration node, and the electronic devices may be a computer terminal, a mobile phone terminal, a server terminal, and the like.
EXAMPLE seven
Referring to fig. 7, fig. 7 is a schematic structural diagram of a management apparatus for house ticket data according to an embodiment of the present invention, and as shown in fig. 7, an apparatus 700 includes:
a first obtaining module 701, configured to obtain, through a first data interface, premise appointment data, where the appointment data includes an appointment number and an appointment date;
a second obtaining module 702, configured to obtain, through a second data interface, house registration data, where the registration data includes a ticket number and a registration date;
and the association sharing module 703 is configured to add the appointment data and the registration data to a management time axis of the house ticket data for association based on the appointment date and the order of the registration date, and store the management time axis in a shared database.
Further, as shown in fig. 8, the apparatus 700 further includes:
a third obtaining module 704, configured to obtain house request data of a third party, where the house request data includes request content and a request date;
an adding module 705, configured to add the request data to the management timeline according to the request date.
Further, as shown in fig. 9, the apparatus 700 further includes:
the judging module 706 is configured to query a corresponding management time axis according to the ticket number to be agreed, and judge whether the right state of the ticket number to be agreed is a restricted right state;
a confirming module 707, configured to obtain the house appointment data based on the ticket number to be appointed if the right status of the ticket number to be appointed is not the limited right status.
Further, as shown in fig. 10, the apparatus 700 further includes:
the prompting module 708 is configured to send a prompt that the right status is the limited right status if the right status of the ticket number to be agreed is the limited right status.
Further, as shown in fig. 11, the apparatus 700 further includes:
a polling module 709, configured to poll the shared database at regular time to determine whether there is a data update;
a pulling module 710, configured to pull, if there is a data update, the update data in the shared database through a message queue, and synchronize the pulled update data to an intermediate database;
the pushing module 711 is configured to perform information pushing on the update data based on the data in the middle database.
Further, as shown in fig. 12, the association sharing module 703 specifically includes:
an obtaining unit 7031, configured to obtain the house appointment data and the house registration data associated on the management time axis;
a processing unit 7032, configured to form mirror view data from the house appointment data and the house registration data associated on the management time axis;
a storage unit 7033, configured to store the mirror view data in the shared database.
Example eight
In order to solve the above technical problem, an embodiment of the present application further provides a management system for house ticket data. Referring to fig. 13, fig. 13 is a block diagram of a management system for house ticket data according to the present embodiment. The management system 130 of the house ticket data includes:
at least two data acquisition devices 131, 132 for generating premise appointment data and premise registration data, respectively; and a management apparatus 700 for house ticket data according to any one of the above embodiments.
The management device may be a computer terminal, a mobile phone terminal, a server terminal, etc. disposed at the supervisory node.
The data collection devices 131 and 132 may be house appointment data collection devices and house registration data collection devices, the house appointment data collection devices may be deployed at house transaction nodes, and the house registration data collection devices may be deployed at house registration nodes.
Further, as shown in fig. 14, the management system of the house ticket data further includes:
and the third-party data acquisition device 133 is used for generating the house request data.
Further, referring to fig. 15 specifically, fig. 15 is a block diagram of a structure of a management system for optional house ticket data according to this embodiment. The management system of the house ticket data comprises:
a service extranet 1501, a service intranet 1502, a government network 1503, and an intranet 1504. The house appointment data acquisition device can be deployed in a business extranet 1501 or a business intranet 1502, the house login data acquisition device can be deployed in a government affair net 1503 or an intranet 1504, the business extranet 1501 comprises a house property trading service platform 15011 used for providing house property trading service, and social public, developers, brokerages and the like can access the house property trading service platform 15011 through the internet to initiate house trading requests. A firewall + VPN15012 is provided between the house property transaction service platform 15011 and the internet to secure information of the house property transaction service platform 15011. The business intranet 1502 includes a database interaction mechanism 15021 and a house property transaction supervision platform 15022, after the house property transaction service platform 15011 generates a transaction request, the transaction request is sent to the house property transaction supervision platform 15022 through the database interaction mechanism 15021, and a house property auditor audits on the house property transaction supervision platform 15022, and corresponding appointment data are generated after the audit is passed. A firewall 15023 is disposed between the service intranet 1502 and the service extranet 1501 to ensure the information security of the service intranet 1502. The government affair network 1503 includes a real estate one-window acceptance platform 15031 and a data interface 15032, and can acquire appointment data from the business intranet 1502 through the data interface 15032, and real estate acceptors perform acceptance operations on the appointment data on the real estate one-window acceptance platform 15031. A firewall 15033 is disposed between the government affair network 1503 and the service intranet 1502 to ensure the security of the government affair network 1503. The intranet 1504 includes a real estate registration platform 15041, an intermediate interactive library 15042, and synchronization software 15043, the real estate registration platform 1504 obtains appointment data and registration data from the business intranet 1502 and the government affairs net 1503 through a data interface 15032, respectively, a real estate auditor performs auditing on the real estate registration platform 15041 to complete registration, and the synchronization software 15043 associates the appointment data and the registration data in the intermediate interactive library 15042. A gatekeeper 15044 is provided between the government affair net 1503 and the intranet 1504 to further ensure the information security of the intranet.
Further, as shown in fig. 16, fig. 16 is a schematic flow node diagram of the management method of the house ticket data in this embodiment, and includes the following steps:
s1, signing a buying and selling contract between a house transferor and a house transferee, and forming a contract number by a house property transaction service platform.
And S2, the signed buying and selling contract is filed and confirmed on a real estate transaction supervision platform by a real estate transaction department.
And S3, submitting the confirmed filed contract by the buyer and the seller in a real estate one-window acceptance platform of the registration department.
And S4, the real estate one-window acceptance platform acquires the electronic information of the contract through the contract number shared by the trading department and feeds back the acceptance state to the trading department.
And S5, the real estate registration platform in the registration department acquires the information of the real estate one-window acceptance platform, audits and finishes the user registration, and sends a new ticket to the transferee.
And S6, simultaneously, the real estate registration platform can share the latest right information of the house to a trading department to form association.
And S7, if a subsequent house mortgage loan is made under the new right, the bank financial department initiates and completes the real estate mortgage registration and forms the association.
And S8, if the subsequent behavior of the new ticket is limited and checked by the introduction of the police law, finishing the relevant registration procedures in real estate and forming association.
And S9, the latest registered ownership state information related to the mortgage, the seal check, the limitation and other rights is shared by the registration department to the transaction department.
And S10, if the new right certificate needs to be given out, house source confirmation is carried out in a trading department, the latest condition is checked, if no trading limit exists, a new trading contract can be signed, and a secondary trading process is carried out.
The above-mentioned nodes may be nodes deploying computer terminals, mobile phone terminals, server terminals, etc.
Further, as shown in fig. 17, fig. 17 is a schematic structural diagram of another alternative house ticket data management system according to this embodiment. The system 1700 for managing optional property ticket data includes:
the transaction service platform 1701, the transaction supervision platform 1702, the real estate acceptance platform 1703, the data sharing platform 1704, the real estate registration platform 1705, the registration database 1706, the pre-shared library 1707, the intermediate database 1708, the data synchronization software 1709 and the data interface 1710. The transaction service platform 1701 performs information interaction with the transaction supervision platform 1702, the data sharing platform 1704 is respectively connected with the transaction supervision platform 1702 and the real estate acceptance platform 1703 through the data interface 1710 to acquire or send corresponding data, the real estate acceptance platform 1703 performs information interaction with the real estate registration platform 1705, the real estate registration platform 1705 stores the formed data into the registration database 1706, the data in the registration database forms a mirror image view to be stored into the front-mounted shared library, the data synchronization software performs data polling on the front-mounted shared library through the middle database regularly by acquiring log information of the middle database so as to pull updated data in the front-mounted shared library into the middle database, and the data synchronization software notifies the middle database to perform information pushing to the transaction supervision platform.
Specifically, the transaction service platform 1701 performs the following functions:
house source checking function: and whether the right state of the house under the name can be traded or not is confirmed through the ticket number and the information of the obligee.
Signing a trading contract: and (4) collecting the contract information, uploading the electronic material, forming a contract number and submitting the contract number to a transaction supervision platform to complete a subsequent filing process.
Transaction monitor platform 1702 performs the following functions:
and (3) contract record confirmation: and (4) verifying and confirming contract information signed by the buyer and the seller and main information of the house and the person, forming a confirmation list after filing and confirming, and covering an electronic signature to form an effective contract result.
The data sharing interface 1710 performs the following functions:
contract information result interface: the real estate is provided with an interface for acquiring the corresponding contract information when the real estate is registered.
Accept registration information interface: and pushing the interface of the relevant acceptance information after the real estate acceptance platform service is completed.
The data synchronization software 1709 sweeps the following functions:
the synchronous operation of the view mirror image data shared by the real estate front server in the intranet mainly comprises the following steps:
data pull service: and polling the latest shared information regularly, and pulling the latest shared information to the intermediate library through the message queue.
Data push service: and the timing service confirms the service state and pushes the finished information to the transaction supervision platform.
It is to be understood that the above-described embodiments are merely illustrative of some, but not restrictive, of the broad invention, and that the appended drawings illustrate preferred embodiments of the invention and do not limit the scope of the invention. This application is capable of embodiments in many different forms and is provided for the purpose of enabling a thorough understanding of the disclosure of the application. Although the present application has been described in detail with reference to the foregoing embodiments, it will be apparent to one skilled in the art that the present application may be practiced without modification or with equivalents of some of the features described in the foregoing embodiments. All equivalent structures made by using the contents of the specification and the drawings of the present application are directly or indirectly applied to other related technical fields and are within the protection scope of the present application.
Claims (14)
1. A method for managing property ticket data, the method comprising the steps of:
acquiring house appointment data through a first data interface, wherein the appointment data comprise an appointment number and an appointment date;
acquiring house registration data through a second data interface, wherein the registration data comprises a ticket number and a registration date;
and adding the appointment data and the registration data to a management time axis of the house ticket data for association based on the appointment date and the sequence of the registration date, and storing the management time axis in a shared database.
2. The method of managing premise ticket data of claim 1, further comprising:
acquiring house request data of a third party, wherein the request data comprises request content and request date;
and adding the request data into the management time shaft according to the request date.
3. The method of managing premise ticket data of claim 1 wherein prior to said step of obtaining premise appointment data, said method comprises:
inquiring a corresponding management time axis according to the serial number of the ticket to be agreed, and judging whether the right state of the serial number of the ticket to be agreed is a limited right state or not;
and if the right state of the to-be-agreed ticket number is not the limited right state, acquiring the house agreement data based on the to-be-agreed ticket number.
4. The method of managing premise ticket data of claim 3, further comprising:
and if the right state of the ticket number to be agreed is the limited right state, sending a prompt that the right state is the limited right state.
5. The method of managing premise ticket data of claim 1, further comprising:
polling the shared database regularly for data update;
if the data updating exists, the updating data in the shared database is pulled through the message queue, and the pulled updating data is synchronized to the intermediate database;
and carrying out information push on the updated data based on the data of the intermediate database.
6. The method for managing property ticket data of any one of claims 1-5, wherein said step of storing said management timeline in a shared database specifically comprises:
acquiring the house appointment data and house registration data associated on the management time axis;
forming mirror image view data by the house appointment data and the house registration data which are related on the management time axis;
storing the mirror view data in the shared database.
7. An apparatus for managing house ticket data, the apparatus comprising:
the first acquisition module is used for acquiring the house appointment data through a first data interface, wherein the appointment data comprise an appointment number and an appointment date;
the second acquisition module is used for acquiring house registration data through a second data interface, and the registration data comprises a ticket number and a registration date;
and the association sharing module is used for adding the appointed data and the registration data to a management time axis of the house ticket data for association based on the appointed date and the sequence of the registration date, and storing the management time axis in a shared database.
8. The apparatus for managing house ticket data of claim 7, wherein said apparatus comprises:
the third acquisition module is used for acquiring house request data of a third party, and the request data comprises request content and request date;
and the adding module is used for adding the request data into the management time shaft according to the request date.
9. The apparatus for managing premise ticket data as claimed in claim 7, wherein said apparatus further comprises:
the judging module is used for inquiring the corresponding management time shaft according to the serial number of the ticket to be agreed and judging whether the right state of the serial number of the ticket to be agreed is the limited right state or not;
and the confirmation module is used for obtaining the house appointment data based on the to-be-appointed ticket number if the right state of the to-be-appointed ticket number is not the limited right state.
10. The apparatus for managing property ticket data of claim 9, wherein said apparatus further comprises:
and the prompting module is used for sending out a prompt that the right state is the limited right state if the right state of the ticket number to be agreed is the limited right state.
11. The apparatus for managing premise ticket data as claimed in claim 7, wherein said apparatus further comprises:
the polling module is used for polling the shared database at regular time to determine whether data updating exists;
the pulling module is used for pulling the update data in the shared database through the message queue if the data update exists, and synchronizing the pulled update data to the intermediate database;
and the pushing module is used for pushing the information of the updated data based on the data of the intermediate database.
12. The apparatus for managing property ticket data according to any of claims 6-11, wherein the association sharing module comprises:
an acquisition unit configured to acquire the house appointment data and the house registration data associated with each other on the management time axis;
the processing unit is used for forming the house appointment data and the house registration data which are related on the management time axis into mirror image view data;
and the storage unit is used for storing the mirror image view data in the shared database.
13. A system for managing property ticket data, comprising:
the system comprises at least two data acquisition devices, a data processing device and a data processing device, wherein the data acquisition devices are respectively used for generating house appointment data and house registration data; and
a management apparatus of house ticket data as claimed in any one of claims 7-12.
14. The system for managing property ticket data of claim 14, further comprising:
and the third-party data acquisition device is used for generating the house request data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910743658.4A CN110599372A (en) | 2019-08-13 | 2019-08-13 | Method, device and system for managing house ticket data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910743658.4A CN110599372A (en) | 2019-08-13 | 2019-08-13 | Method, device and system for managing house ticket data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110599372A true CN110599372A (en) | 2019-12-20 |
Family
ID=68854034
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910743658.4A Pending CN110599372A (en) | 2019-08-13 | 2019-08-13 | Method, device and system for managing house ticket data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110599372A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117371767A (en) * | 2023-12-07 | 2024-01-09 | 中国光大银行股份有限公司 | Deposit processing method and device |
| CN117556463A (en) * | 2023-11-14 | 2024-02-13 | 青岛仁科信息技术有限公司 | House property right management method, medium and system based on blockchain technology |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105139302A (en) * | 2015-08-31 | 2015-12-09 | 丁澄天 | House restriction registration management system for on-line real-estate integrated information management for real-estate services |
| CN105303280A (en) * | 2014-06-19 | 2016-02-03 | 林淑贞 | Method and system for managing real estate information by using house calendar |
| CN109493196A (en) * | 2018-12-29 | 2019-03-19 | 杭州趣链科技有限公司 | A kind of real estate based on block chain deposits card and method of commerce |
| CN110009179A (en) * | 2019-01-22 | 2019-07-12 | 苏州智数信息科技有限公司 | A kind of management system and its method of real estate platform |
-
2019
- 2019-08-13 CN CN201910743658.4A patent/CN110599372A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105303280A (en) * | 2014-06-19 | 2016-02-03 | 林淑贞 | Method and system for managing real estate information by using house calendar |
| CN105139302A (en) * | 2015-08-31 | 2015-12-09 | 丁澄天 | House restriction registration management system for on-line real-estate integrated information management for real-estate services |
| CN109493196A (en) * | 2018-12-29 | 2019-03-19 | 杭州趣链科技有限公司 | A kind of real estate based on block chain deposits card and method of commerce |
| CN110009179A (en) * | 2019-01-22 | 2019-07-12 | 苏州智数信息科技有限公司 | A kind of management system and its method of real estate platform |
Non-Patent Citations (2)
| Title |
|---|
| 丁磊: "面向不动产统一登记的南京市六合区房地历史数据整合方法研究", 《中国优秀硕士学位论文全文数据库经济与管理科学辑》 * |
| 刘雅慧: "不动产统一登记数据同步更新方法研究", 《中国优秀硕士学位论文全文数据库基础科学辑》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117556463A (en) * | 2023-11-14 | 2024-02-13 | 青岛仁科信息技术有限公司 | House property right management method, medium and system based on blockchain technology |
| CN117371767A (en) * | 2023-12-07 | 2024-01-09 | 中国光大银行股份有限公司 | Deposit processing method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230198971A1 (en) | Resource transfer setup and verification | |
| US11909881B2 (en) | Digital asset management | |
| CA2849152C (en) | System and method for creating, vaulting, transferring, and controlling transferable electronic records with unique ownership | |
| US20190130394A1 (en) | Systems and Methods to Validate Transactions For Inclusion in Electronic Blockchains | |
| CN109190331B (en) | Space flight measurement and control network data transaction method based on block chain | |
| CN110728494B (en) | Real estate business handling method, real property information system and device | |
| CN107636662A (en) | Web content certification | |
| US8307218B2 (en) | System and method for creating, vaulting, transferring and controlling transferable electronic records with unique ownership | |
| US20150095243A1 (en) | Online-id-handling computer system and method | |
| DE102019200533A1 (en) | Methods and Devices for Detecting Denial-of-Service Attacks in Secure Interaction | |
| CN111414434B (en) | Block chain-based data transaction management network, transaction device and storage medium | |
| US20230142659A1 (en) | System and method for registering share of asset of which owner cannot be specified or ownership does not exist | |
| CN111612452A (en) | Intellectual property management system and method based on block chain | |
| WO2020155204A1 (en) | Blockchain-based domain name transaction method and apparatus | |
| CN111784128A (en) | Asset information processing method and system based on block chain | |
| CN111897770A (en) | Method and system for initiating litigation request | |
| CN110599372A (en) | Method, device and system for managing house ticket data | |
| CN114303129A (en) | Document authentication method and system | |
| KR20210120249A (en) | Transaction methods and systems that utilize based of block-chain technology to trade creative assets such as works of art using smart contracts and to track them to implement creator's resale royalty Right in a transparent and fair manner | |
| CN111833193A (en) | System and method for providing patent ownership insurance with centralized and distributed data structures | |
| RU2801890C2 (en) | Access control system for metadata of intellectual property objects | |
| CN113807845B (en) | Real estate transaction system based on blockchain and implementation method thereof | |
| CN111563814B (en) | Information processing method, device, system and electronic equipment | |
| CN114697114B (en) | Data processing method, device, electronic equipment and medium | |
| CN117455487A (en) | Block chain-based data processing method, device, equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191220 |