CN112883029A

Movatterモバイル変換

Info

Publication number: CN112883029A
Application number: CN202110180887.7A
Authority: CN
Inventors: 麻陈飞; 卢旖旎; 王文育; 陈思骏
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-02-07
Filing date: 2021-02-07
Publication date: 2021-06-01
Anticipated expiration: 2041-02-07
Also published as: CN112883029B

Abstract

Translated fromChinese

本公开提供了一种针对不动产登记中心的业务处理方法，金融领域或其他领域，该方法包括：响应于已确定服务申请的种类和拟针对服务申请进行业务办理的不动产登记中心，获取业务办理入口提供的第一业务数据，其中第一业务数据包括不动产登记中心针对服务申请进行业务办理所需的数据；基于服务申请的种类，将第一业务数据转换成符合不动产登记中心的业务办理要求的第二业务数据；以及将第二业务数据转发至与不动产登记中心对接的分行系统，使得分行系统基于第二业务数据向不动产登记中心提交服务申请。本公开还提供了一种针对不动产登记中心的业务处理装置、一种电子设备、一种计算机可读存储介质以及一种计算机程序产品。

The present disclosure provides a business processing method for a real estate registration center, in the financial field or other fields, the method includes: in response to the type of the service application being determined and the real estate registration center that intends to perform business processing for the service application, obtaining a business processing entry The provided first business data, wherein the first business data includes the data required by the real estate registration center to process the service application; based on the type of the service application, the first business data is converted into the first business data that meets the business processing requirements of the real estate registration center. Second business data; and forwarding the second business data to the branch system connected with the real estate registration center, so that the branch system submits a service application to the real estate registration center based on the second business data. The present disclosure also provides a business processing apparatus for a real estate registration center, an electronic device, a computer-readable storage medium, and a computer program product.

Description

Service processing method and device for real estate registration center

Technical Field

The present disclosure relates to the financial field or other fields, and in particular, to a method and an apparatus for processing a transaction for a real estate registration center, an electronic device, a computer-readable storage medium, and a computer program product.

Background

In the related art, when a user transacts a mortgage registration service, the user usually needs to go to a local real estate registration center together with local bank staff for offline transaction; or the local branch system uploads the relevant information for mortgage registration to be transacted online according to the business transaction requirement put forward by the local real estate registration center.

In carrying out the inventive concepts of the present disclosure, the inventors discovered: the real estate registration center usually takes the city level as a unit, and policy and regulations in various regions have certain differences, so that the difference exists in the information required to be provided when the real estate registration centers transact business in different places. And the interface standard and the transmitted data required by the real estate registration center at different places are different. Therefore, when the branches in different areas are in butt joint with the local real estate registration center, the branches need to develop a system capable of meeting the service application requirements of the local real estate registration center by themselves, so that the development pressure of the branches is increased, and the branches are not beneficial to the head office to uniformly manage the branches.

Disclosure of Invention

In view of the above, the present disclosure provides a method and an apparatus for processing a service for a real estate registration center, an electronic device, a computer-readable storage medium, and a computer program product.

One aspect of the present disclosure provides a service processing method for a real estate registration center, including: responding to the determined type of the service application and a real estate registration center which is planned to conduct business transaction aiming at the service application, and acquiring first business data provided by a business transaction entrance, wherein the first business data comprises data required by the real estate registration center for conducting business transaction aiming at the service application; converting the first business data into second business data which accords with the business transaction requirements of the real estate registration center based on the type of the service application; and forwarding the second service data to a branch system in butt joint with the real estate registration center, so that the branch system submits a service application to the real estate registration center based on the second service data.

Optionally, the converting the first business data into second business data meeting the business transaction requirement of the real estate registration center based on the type of the service application includes: extracting at least one standardized field contained in the first service data; converting each standardized field in the at least one standardized field into a corresponding basic field based on a mapping relation between a standardized field pre-configured for the type of the service application and a basic field used by a service interface provided by the real estate registration center to obtain at least one basic field; and obtaining the second service data based on the at least one basic field.

Optionally, the mapping relationship includes at least one of the following: the mapping relation of the field name dimension, the mapping relation of the data type dimension and the mapping relation of the field length dimension.

Optionally, the obtaining the second service data based on the at least one basic field includes: extracting at least one first field which does not need to be combined and configured and at least two second fields which need to be combined and configured from the at least one basic field based on an interface document configured for the service interface and/or based on a basic field combination relation pre-configured by the interface document; configuring the at least two second fields into at least one set type field according to the basic field combination relationship; and obtaining the second service data based on the at least one first field and the at least one set type field.

Optionally, obtaining second service data based on the at least one first field and the at least one set type field includes: configuring the at least one first field and the at least one set type field into interface data according to a field packaging relation based on the interface document and/or a field packaging relation configured in advance based on the interface document; and using the interface data as the second service data.

Optionally, the set type field includes at least one subset type field.

Optionally, the method further comprises: acquiring a transaction result forwarded by the branch system and returned by the real estate registration center; extracting fields needing to be stored in the business transaction entries from the transaction results; and converting the fields into standardized fields meeting the storage requirements of the business handling portal.

Optionally, the service application includes at least one of the following: mortgage registration service application, mortgage withdrawal registration service application, and escort status query service application.

Another aspect of the present disclosure provides a business processing apparatus for a real estate registration center, including: a data obtaining module, configured to obtain first service data provided by a service transaction entrance in response to a determined type of a service application and a real estate registration center that is intended to perform service transaction for the service application, where the first service data includes data required by the real estate registration center to perform service transaction for the service application; a data conversion module, configured to convert the first business data into second business data meeting a business transaction requirement of the real estate registration center based on the type of the service application; and a data forwarding module, configured to forward the second service data to a branch system docked with the real estate registration center, so that the branch system submits a service application to the real estate registration center based on the second service data.

Another aspect of the present disclosure provides an electronic device including: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the methods of embodiments of the present disclosure.

Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, implement the method of embodiments of the present disclosure.

Another aspect of the disclosure provides a computer program product comprising a computer program which, when executed by a processor, implements the above method according to an embodiment of the disclosure.

According to the embodiment of the disclosure, under the condition that the service application type and the real estate registration center to be docked are determined, the first business data used by the service applying the service application type can be obtained, the first business data is converted into the second business data required by the real estate registration center to be docked for handling the service application, and the docked branch system forwards the second business data to the real estate registration center to be docked for business handling, so that the standardized data (such as the first business data) used in the head office system can be converted into the personalized data (such as the second business data) meeting the requirements of the real estate registration center at different places. The scheme does not need to be separately developed and researched by each branch to meet the service application requirement of the local real estate registration center, and the research and development pressure and the research and development resource investment of each branch can be reduced. Meanwhile, the data conversion can be carried out similarly aiming at the handling results fed back by the real estate registration centers of all the places, so that the business of all the places can be managed uniformly by the head office.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIG. 1 schematically illustrates a system architecture suitable for applying the business processing method and apparatus for a real estate registration center in accordance with an embodiment of the present disclosure;

FIG. 2 schematically illustrates an application scenario suitable for applying the business processing method and apparatus for a real estate registration center according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of a business process method for a real estate registration center according to an embodiment of the present disclosure;

fig. 4 schematically shows a flow chart for converting first traffic data into second traffic data according to an embodiment of the present disclosure;

FIG. 5A is a diagram that schematically illustrates a mapping between standardized fields and basic fields, in accordance with an embodiment of the present disclosure;

FIG. 5B is a diagram that schematically illustrates another mapping between standardized fields and basic fields, in accordance with an embodiment of the present disclosure;

FIG. 6 schematically illustrates a flow chart for obtaining second traffic data based on a first field and a set type field, according to an embodiment of the disclosure;

FIG. 7 schematically illustrates a diagram of combining into a set-type field using base fields, according to an embodiment of the disclosure;

FIG. 8 schematically illustrates a field encapsulation according to an embodiment of the disclosure;

FIG. 9 schematically illustrates a flow diagram of another business process method for a real estate registration center according to an embodiment of the present disclosure;

FIG. 10 schematically illustrates a block diagram of a business processing apparatus for a real estate registration center according to an embodiment of the present disclosure; and

FIG. 11 schematically shows a block diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

The embodiment of the disclosure provides a business processing method for a real estate registration center and a device capable of applying the method. The method comprises the following steps: responding to the determined type of the service application and a real estate registration center which is planned to conduct service handling aiming at the service application, and acquiring first service data provided by a service handling entrance, wherein the first service data comprises data required by the real estate registration center for conducting service handling aiming at the service application; converting the first business data into second business data meeting business handling requirements of a real estate registration center based on the type of the service application; and forwarding the second business data to a branch system which is in butt joint with the real estate registration center, so that the branch system submits a service application to the real estate registration center based on the second business data.

Fig. 1 schematically illustrates a system architecture suitable for applying the business processing method and apparatus for a real estate registration center according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in FIG. 1, asystem architecture 100 according to this embodiment may include acredit system 101, acomponent library 102, abranch system 103, and a realestate registration center 104. Data transmission is performed between thecredit system 101 and thecomponent library 102, between thecomponent library 102 and thebranch system 103, between thebranch system 103 and the realestate registration center 104 through a network, and the like. The network can include various connection types, such as wired and/or wireless communication links, among others.

Thecredit system 101, as a head office system, may be used as a unified portal for applying for transactions such as mortgage registration to a local real estate registration center through different regional branches, which may provide a user interface for entering or collecting the first transaction data described above. For example, a user may access thecredit system 101 through a predetermined client to select a service application category and a real estate registration center to be docked. Thecredit system 101 may obtain first business data entered by the user after selecting the real estate registration center and the service application category to be docked. Additionally, thecredit system 101 may also return the business transaction results to the client for the user to view confirmation.

The mapping relationship between the standardized fields and the personalized basic fields, the combination relationship between the basic fields and the basic fields, and the encapsulation relationship between the basic fields and/or the set type fields can be configured in advance in thecomponent library 102. Thecomponent repository 102 converts the first business data obtained from thecredit system 101 into the second business data using the relationship described above. Wherein the second business data comprises data meeting the requirement that the real estate registration center to be docked transacts the selected service application type.

Thebranch system 103 may be a local feature system of a bank, and is used to provide network transmission, identity authentication, and other guarantees required for interfacing with a local real estate registration center.

The realestate registration center 104 is used to provide services such as online mortgage registration, and warranty status inquiry.

For example, when a user needs to transact a mortgage registration service, thecredit system 101 may be accessed by the client and the realestate registration center 104 and the service application type (including service types such as mortgage registration, and warranty status inquiry) to be docked are selected by thecredit system 101. Thecredit system 101 may provide thecomponent repository 102 with the first business data required by the realestate registration center 104 to be docked and the service application category according to the user selected realestate registration center 104 to be docked and the service application category. Thecomponent library 102 may convert the acquired first data into second service data required by the realestate registration center 104 to be docked, and send the converted second service data to thebranch system 103, so as to be forwarded to the local realestate registration center 104 by thebranch system 103.

Thecomponent library 102 may also convert the transaction results sent by thebranch system 103 into transaction results that meet the storage requirements of thecredit system 101 and send the converted transaction results to thecredit system 101 for storage.

It should be understood that the number of credit systems, component libraries, branch systems, and real estate registration centers in FIG. 1 are merely illustrative. There may be any number of credit systems, component libraries, branch systems, and real estate registration centers, as desired for implementation.

Fig. 2 schematically illustrates an application scenario suitable for applying the service processing method and apparatus for a real estate registration center according to an embodiment of the present disclosure.

As shown in FIG. 2, in thisapplication scenario 200, assume that user A accesses the credit system through a client, such as some APP. And selects the real estate registration center to be docked in the credit system as the a real estate registration center and the service application category as the mortgage registration service, for example, as shown in theuser interface 201 in fig. 2.

In response to the user a selecting the real estate registration center and the service application category, the credit system may provide the component repository with first business data provided by the user a applying for a mortgage registration service with the a real estate registration center.

And after acquiring the first service data, the component library converts the first service data into second service data, and sends the second service data obtained after conversion to a branch system butted with the A real estate registration center. After the branch system obtains the second service data, submitting a mortgage registration service application to the A real estate registration center and forwarding the second service data.

After the A real estate registration center finishes the transaction of the mortgage registration service application service, the transaction result is forwarded to the branch system. And the branch system receives the transaction result and forwards the transaction result to the component library. The component library receives the transaction result, analyzes the transaction result, converts the transaction result into a field name and a data type which meet the storage requirement of the credit system, and forwards the analyzed data to the credit system. The credit system receives and stores the data and returns the transaction results to user a for viewing and confirmation by user a, for example, as shown inuser interface 202 in fig. 2.

FIG. 3 schematically shows a flow chart of a business processing method for a real estate registration center according to an embodiment of the present disclosure. As shown in fig. 3, the method may include operations S310 to S330.

Operation S310, in response to the determined type of the service application and the real estate registration center that is intended to perform service transaction for the service application, acquiring first service data provided by the service transaction portal, where the first service data includes data required by the real estate registration center to perform service transaction for the service application.

According to the embodiment of the disclosure, a user can access a business transaction entrance (such as a credit system) through a client to select the type of a service application, such as the business types of mortgage registration, deregistration, escort status inquiry and the like. The user may also select a real estate registration center to be docked via the business transaction portal.

According to the embodiment of the disclosure, in response to the type of the service application selected by the user and the real estate registration center for transacting the selected service application, the business transaction portal acquires the first business data input by the user for the type of the service application and the real estate registration center to be docked, and provides the first business data to the component library. The field name, the data type and the field length of each field in the first service data all meet the storage requirement of the service transaction entry.

According to an embodiment of the present disclosure, the component library acquiring the first service data provided by the service transaction portal may include the following:

in one case, the component repository may successfully obtain the first business data provided by the business transaction portal. In this case, further, the component library may be further configured to successfully convert the acquired first service data into the second service data. Or the component library cannot convert the acquired first service data into the second service data, for example, a field with an empty field value exists in fields extracted from the first service data. In another case, the component repository may not be able to successfully obtain the first business data provided by the business transaction portal. For example, the first service data provided by the service transaction portal cannot be transmitted to the component repository due to a network error.

Operation S320 is to convert the first business data into second business data meeting a business transaction requirement of the real estate registration center based on the type of the service application.

According to an embodiment of the present disclosure, the service application may include a transacted service application, a revoked service application, a query service application, and the like.

Different service application types require different data to be provided by the user. For example, mortgage registration requires information on the transactor or the transacted object; transacting revocation of mortgage registrations requires providing information on the revoked objects, the current status of the revoked objects, transactor information, etc. In addition, the data required to be provided by the same service application type is different in different real estate registration centers. For example, when a user transacts the mortgage registration service in the real estate registration center a, the identity information of the user, the information of the object to be mortgage and the information of the bank account number of the user need to be provided. The user transacts the mortgage registration service in the B real estate registration center, for example, only the identity information of the user and the information of the objects to be mortgage need to be provided.

Further, in different real estate registration centers, fields which are required by the same service application type and represent the same meaning may also be different in corresponding field name and field type. For example, following the above example, the user provides a field representing "date of birth" via the business transaction portal, for example, the field name of the field: date of birth, data type is Double type. And a field representing "date of birth" in the a real estate registration center, the field name of which may be: birth time, the data type may be Float type. And a field representing "date of birth" in B real estate registration center, whose field name may be: at birth time, the data type may be a Double type.

In addition, even though fields having the same meaning have the same field name and data type in different real estate registration centers, the length of the field may be different.

Operation S330 is to forward the second service data to the branch system docked with the real estate registration center, so that the branch system submits a service application to the real estate registration center based on the second service data.

According to embodiments of the present disclosure, a real estate registration center at a different location interfaces with a branch system at that location. And sending the converted second service data to a branch system butted with a real estate registration center to be butted through a component library. And then the second service data is sent to a real estate registration center to be butted through the branch system for processing.

According to the embodiment of the disclosure, under the condition that the service application type and the real estate registration center to be docked are determined, first business data input by a user aiming at the determined service application type and the real estate registration center to be docked can be obtained, the first business data are converted into second business data required by the real estate registration center to be docked for handling the service application, and the docked branch system forwards the second business data to the real estate registration center to be docked for business handling, so that standardized data (such as the first business data) used in the head office system can be converted into personalized data (such as the second business data) meeting requirements of the real estate registration center in different places. The scheme does not need to be separately developed and researched by each branch to meet the service application requirement of the local real estate registration center, and the research and development pressure and the research and development resource investment of each branch can be reduced. Meanwhile, the data conversion can be carried out similarly aiming at the handling results fed back by the real estate registration centers of all the places, so that the business of all the places can be managed uniformly by the head office.

Fig. 4 schematically shows a flow chart for converting first traffic data into second traffic data according to an embodiment of the present disclosure. As shown in fig. 4, the method may include operations S410 to S430.

Operation S410 extracts at least one standardized field included in the first service data.

According to an embodiment of the present disclosure, it is assumed that service data input by a user at a service transaction portal, such as a credit system, is standard service data. It should be understood that the standardized service data includes at least one standardized field each including a standardized field name, a standardized data type, and a standardized field length. For example, in the business transaction portal, business data related to "date of birth of the transactor" is acquired, and the data is standard business data. And at least one standardized field is extracted from it, a field representing "date of birth" can be extracted, and the field name of this field can be, for example: the birth date is a standard field name of a field indicating "birth date", and the data type of the field is, for example, a Double type, and is a standard data type of a field indicating "birth date".

Operation S420 is performed to convert each standardized field of the at least one standardized field into a corresponding basic field based on a mapping relationship between the standardized field pre-configured for the type of the service application and a basic field used by a service interface provided by the real estate registration center, so as to obtain the at least one basic field.

According to embodiments of the present disclosure, the basic fields used by the real estate registration center interface differ from place to place. Therefore, to forward the first service data to the real estate registration center to be docked, the standardized fields in the first service data need to be converted into basic fields that can be used by the real estate registration center interface.

According to the embodiment of the disclosure, the standardized fields in the first service data can be converted into corresponding basic fields according to the mapping relationship between the standardized fields and the basic fields which are stored in advance. For example, the standardized fields in the first service data may be converted into basic fields that can be used by the service interface of the a city real estate registration center according to a mapping relationship between the standardized fields stored in advance and the basic fields used by the service interface provided by the a city real estate registration center.

For example, a field representing "date of birth" is obtained from a business transaction portal, and the field name of the field may be: date of birth, the data type may be a Double type. Then the standardized field name for the field representing "date of birth" may be considered to be: birth date, standardized data type is Double type. Correspondingly, in the basic field used by the service interface provided by the city a real estate registration center, a field indicating "date of birth" may be given by the field name: birth time, the data type may be Float type. Then the two have a mapping relationship.

Operation S430 obtains second service data based on the at least one basic field.

According to an embodiment of the present disclosure, the converted at least one base field is combined into second service data, wherein the second service data can be used by a service interface of a corresponding real estate registration center.

Further, the converted at least one basic field is returned to the business transaction portal for user confirmation, e.g., whether the field value of each basic field is accurate, etc. The method can also comprise returning the field which fails to be converted to the business transaction entrance, and defining the field value of the field which fails to be converted to be null. So that the user can maintain the fields for which the conversion failed, for example, to refill the corresponding information.

In the case where the base field containing the field with the conversion failure is returned to the business transaction portal, the component repository may verify that the data resubmitted by the business transaction portal meets the requirements of the real estate registry to be docked. And after the verification is passed, forwarding the data to the corresponding branch system. And under the condition that the verification fails, converting the resubmitted data into second service data and forwarding the second service data to the corresponding branch system.

According to the embodiment of the disclosure, the standardized field in the first service data is converted into the basic field according to the mapping relation between the standardized field and the basic field, and the second service data is obtained from the basic field obtained after the conversion. The conversion of the first service data can be made uniform. Meanwhile, the second service data obtained after conversion can meet the requirement of the real estate registration center to be docked.

According to an embodiment of the present disclosure, the mapping relationship includes at least one of the following: the mapping relation of the field name dimension, the mapping relation of the data type dimension and the mapping relation of the field length dimension.

Fig. 5A schematically illustrates a mapping relationship between a standardized field and a basic field according to an embodiment of the disclosure.

FIG. 5A is a mapping between standardized fields and the base fields used by A real estate registry. As shown in the field numbered 001, the standardized name is name 1, type 1, length 1, and the field is name 1 ', type 1 ', length 1 ' in the basic field used by the a real estate registration center. Then, according to the mapping relationship, the standardized field with name 1, type 1 and length 1 in the first service data may be converted into the basic field with name 1 ', type 1 and length 1'.

Fig. 5B schematically illustrates another mapping relationship between standardized fields and basic fields according to an embodiment of the disclosure.

FIG. 5B is a mapping between standardized fields and the base fields used by the B real estate registry. As can be seen from fig. 5A and 5B, the basic fields used by the same service application in different real estate registration centers are different.

According to an embodiment of the present disclosure, fields representing the same meaning have different field names, data types, and field lengths in different real estate registration centers. For example, a field representing "contract amount", which in city a may be a debt amount (field name) of Float type (data type); and in city B is the debit contract amount (field name) for Double type (data type). Further, the business process portal may be a contract amount (field name) of Double type (data type).

Fig. 6 schematically shows a flowchart for obtaining second traffic data based on the first field and the set type field according to an embodiment of the present disclosure. As shown in fig. 6, the method may include operations S610 to S630.

Operation S610 is to extract, from the at least one basic field, at least one first field that does not need to be configured in a combined manner and at least two second fields that need to be configured in a combined manner, based on an interface document configured for the service interface and/or based on a basic field combination relationship pre-configured by the interface document.

According to the embodiment of the disclosure, basic field combination relations used by service interfaces provided by different real estate registration centers can be configured and stored in advance. And extracting the first field and the second field according to the stored basic field combination relation. Or the first field and the second field can be extracted according to the basic field combination relation in the interface document configured for the service interface.

The basic field combination may include basic fields related to the same service application category. For example, in a mortgage service application, basic fields such as mortgage obligee, mortgage certification number, credit amount, mortgage method, credit fulfillment time, mortgage order, etc. need to be provided. These base fields can be configured as a basic field combination associated with a mortgage service application.

In addition, the basic field combination may also include the order between the basic fields in the basic field combination relationship. For example, assume that the basic field combinations associated with a mortgage service application include basic fields of mortgage obligee, mortgage certification number, credit amount, mortgage method, credit fulfillment time, mortgage order. When a mortgage right service application is transacted, according to the requirement of a real estate registration center, mortgage obligee information, a mortgage certification number, a mortgage mode, debt fulfillment time, a credit amount and a mortgage order need to be provided in sequence. Therefore, when configuring a basic field combination for a mortgage service application of the real estate registration center, the basic fields may be configured in the basic field combination, and the order of the basic fields may be configured in the basic field combination.

Operation S620 configures the at least two second fields into at least one set type field according to the basic field combination relationship.

According to an embodiment of the present disclosure, the at least two second fields may be configured into at least one set type field according to a basic field combination relationship. And a new field name may also be defined for the set type field.

Operation S630 obtains second traffic data based on the at least one first field and the at least one set type field.

According to the embodiment of the disclosure, according to the real estate registration center to be docked, the first field and the set type field are sequenced according to the relation between the basic fields and the set type field in the service data required by the determined service application type, so as to obtain the second service data.

According to the embodiment of the present disclosure, the same first field and the same set type field are ordered differently, resulting in different second service data combined. For example, the set type field and two first fields are respectively the service application time and the service application place, and the set type field includes the information of the mortgage owner, the mortgage certification number and the mortgage mode. And the three fields have six different orderings, which results in different obtained second service data. Therefore, according to the real estate registration center to be docked, the first field and the set type field need to be sorted according to the relationship between the basic fields and the set type field in the service data required by the determined service application type, so as to obtain the second service data that can be used by the real estate registration center.

FIG. 7 schematically illustrates a diagram of combining into a set type field using base fields, according to an embodiment of the disclosure.

As shown in fig. 7, the base fields numbered 001 and 002 may be combined in order of the numbers from smaller to larger to form a set type field numbered 01, and the set type field may be named name 1'. For example, the base fields 003 and 004 may be combined in descending order of numbers to form aset type field 02, and the set type field may be named as name 2'.

According to an embodiment of the present disclosure, obtaining the second service data based on the at least one first field and the at least one set type field may include: configuring at least one first field and at least one set type field into interface data according to a field packaging relation based on an interface document and/or a field packaging relation pre-configured based on the interface document; and taking the interface data as second service data.

According to an embodiment of the present disclosure, the interface data may be composed of at least one first field and at least one set type field in a field encapsulation relationship that is pre-configured according to an interface document provided by a real estate registry to be docked. Or the interface data is formed by at least one first field and at least one set type field based on the field packaging relation in the interface document provided by the real estate registration center. The field encapsulation relationship may include an ordering relationship between the base field and the collection type field.

According to the embodiment of the disclosure, the technical means of forming the interface data by combining the basic field and the set type word according to the encapsulation relation is adopted. The relationship between each basic field and the set type field may be pre-stored so that the first service data may be converted into the second service data according to the relationship between each basic field and the set type field, thereby simplifying the conversion process.

Fig. 8 schematically illustrates a schematic diagram of field encapsulation according to an embodiment of the disclosure.

The preconfigured field encapsulation relationship based on the interface document may be represented in fig. 8. As can be seen from the figure, the encapsulation relationship can not only indicate which basic fields and set type fields form the encapsulation relationship, but also indicate the sequential relationship between each basic field and set type field. As shown in fig. 8, the encapsulation relationship is composed of a set type field named name 2 and two basic fields named name 1 and name 3, respectively. Meanwhile, the three fields are sorted according to the sequence that the basic field of the name 1 is at the first position, the collection type field of the name 2 is at the second position, and the basic field of the name 3 is at the third position, and finally the encapsulation relation is obtained.

According to an embodiment of the present disclosure, the set type field includes at least one sub-set type field.

According to an embodiment of the present disclosure, a subset type field may also be included in one set type field. For example, some set type field (which may be named "mortgage service") includes basic fields of mortgage obligee, mortgage certification number, amount of debt, mortgage method, time of debt fulfillment, and mortgage order. The basic field of the mortgage owner may include the date of birth of the mortgage owner, the age of the mortgage owner, the current address of the mortgage owner, and the identity card of the mortgage owner. Thus, the mortgage owner can be a collection type field, including the base fields of the mortgage owner's birth date, the mortgage owner's age, the current address of the mortgage owner, and the identity of the mortgage owner. Furthermore, the sub-set type field of "mortgage owner" is included in the set type field of "mortgage service".

Through the embodiment of the disclosure, the set type field may further include a sub-set type field, and through a relationship between the set type field and the sub-set type field, the set type field may be configured layer by layer, and the basic fields are combined to form the second service data according to the set type field. The conversion process of the second service data can be simplified.

FIG. 9 schematically shows a flowchart of another business processing method for a real estate registration center according to an embodiment of the present disclosure. As shown in fig. 9, the method may further include operations S910 to S930, in addition to operations S310 to S330 in fig. 3:

operation S910, obtaining the transaction result returned by the real estate registration center forwarded by the branch system.

According to the embodiment of the disclosure, each branch system submits a service application to the real estate registration center to be docked and forwards the second service data. And after the real estate registration center finishes the service transaction, forwarding the service transaction result to the real estate registration center. And the real estate registration center forwards the service transaction result to the component library.

Operation S920, extracting a field to be stored in the service transaction entry from the transaction result.

According to the embodiment of the disclosure, the component library extracts the field required to be stored in the business transaction entry from the acquired business transaction result, so that the condition when the service application is transacted can be known through the extracted information when needed.

Operation S930, convert the field into a standardized field that meets the business transaction portal storage requirements.

According to the embodiment of the disclosure, as the technical means of extracting the second service data to be stored from the transaction result data and converting the second service data into the standardized fields is adopted, the fields to be stored in the service transaction entries can be converted into the standardized fields meeting the storage requirements of the service transaction entries, so that the service transaction entries can be uniformly managed and stored. Meanwhile, when the service application is transacted through the service transaction entrance next time, the converted standardized field can be used as first service data to be provided for the component library.

According to an embodiment of the present disclosure, the service application includes at least one of the following: mortgage registration service application, mortgage withdrawal registration service application, and escort status query service application.

FIG. 10 schematically shows a block diagram of a business processing apparatus for a real estate registration center according to an embodiment of the present disclosure.

As shown in fig. 10, theprocessing device 1000 applied to data backup includes adata acquisition module 1001, a firstdata conversion module 1002, and adata forwarding module 1003. The processing device may perform the method described above with reference to the method embodiment, which is not described in detail herein.

Specifically, thedata obtaining module 1001 is configured to obtain, in response to a determined type of a service application and a real estate registration center that is intended to perform service transaction for the service application, first service data provided by a service transaction portal, where the first service data includes data required by the real estate registration center to perform service transaction for the service application; a firstdata conversion module 1002, configured to convert, based on the type of the service application, the first business data into second business data meeting a business transaction requirement of the real estate registration center; and adata forwarding module 1003, configured to forward the second service data to a branch system docked with the real estate registration center, so that the branch system submits a service application to the real estate registration center based on the second service data.

According to an embodiment of the present disclosure, the first data conversion module includes: an extraction submodule, configured to extract at least one standardized field included in the first service data; a conversion sub-module, configured to convert each standardized field in the at least one standardized field into a corresponding basic field based on a mapping relationship between a standardized field preconfigured for a type of the service application and a basic field used by a service interface provided by the real estate registration center, so as to obtain at least one basic field; and an obtaining submodule configured to obtain the second service data based on the at least one basic field.

According to an embodiment of the present disclosure, the converting sub-module converts each of the at least one standardized field into a corresponding basic field through a mapping relationship, where the mapping relationship includes at least one of: the mapping relation of the field name dimension, the mapping relation of the data type dimension and the mapping relation of the field length dimension.

According to an embodiment of the present disclosure, the obtaining sub-module includes: an extracting unit, configured to extract, from the at least one basic field, at least one first field that does not need to be configured in a combined manner and at least two second fields that need to be configured in a combined manner, based on an interface document configured for the service interface and/or based on a basic field combination relationship pre-configured for the interface document; a configuration unit, configured to configure the at least two second fields into at least one set type field according to the basic field combination relationship; and an obtaining unit, configured to obtain the second service data based on the at least one first field and the at least one set type field.

According to an embodiment of the present disclosure, the obtaining unit includes: the packaging subunit is used for configuring the at least one first field and the at least one set type field into interface data according to the field packaging relationship based on the interface document and/or the field packaging relationship configured in advance based on the interface document; and a determining subunit, configured to use the interface data as the second service data.

According to an embodiment of the present disclosure, the encapsulating subunit configures, based on the interface document and/or based on a field encapsulation relationship preconfigured in the interface document, the at least one first field and the at least one set type field into interface data according to the field encapsulation relationship, where the set type field includes at least one subset type field.

According to an embodiment of the present disclosure, the processing apparatus further includes: the data return module is used for acquiring a transaction result forwarded by the branch system and returned by the real estate registration center; a data storage module for extracting the field required to be stored in the business transaction entrance from the transaction result; and the second data conversion module is used for converting the fields into standardized fields meeting the storage requirements of the business handling entrance.

According to an embodiment of the disclosure, the data obtaining module obtains first business data provided by a business transaction entrance in response to the determined type of the service application and a real estate registration center which is intended to perform business transaction for the service application, wherein the type of the service application includes at least one of: mortgage registration service application, mortgage withdrawal registration service application, and escort status query service application.

It should be noted that the embodiments of the apparatus portion and the method portion are similar to each other, and the achieved technical effects are also similar to each other, which are not described herein again.

Any number of modules, sub-modules, units, sub-units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, and sub-units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and firmware implementations. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the disclosure may be at least partially implemented as a computer program module, which when executed may perform the corresponding functions.

For example, any plurality of thedata obtaining module 1001, the firstdata conversion module 1002, and thedata forwarding module 1003 may be combined and implemented in one module, or any one of the modules may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of thedata obtaining module 1001, the firstdata converting module 1002, and thedata forwarding module 1003 may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware, and firmware, or implemented by a suitable combination of any several of them. Alternatively, at least one of thedata obtaining module 1001, the firstdata conversion module 1002 and thedata forwarding module 1003 may be at least partially implemented as a computer program module, which when executed, may perform a corresponding function.

FIG. 11 schematically shows a block diagram of an electronic device according to an embodiment of the disclosure. The electronic device shown in fig. 11 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 11,electronic device 1100 includes aprocessor 1110, a computer-readable storage medium 1120. Theelectronic device 1100 may perform a method according to an embodiment of the disclosure.

In particular,processor 1110 may include, for example, a general purpose microprocessor, an instruction set processor and/or related chip set and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), and/or the like. Theprocessor 1110 may also include onboard memory for caching purposes.Processor 1110 may be a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the disclosure.

Computer-readable storage medium 1120, for example, may be a non-volatile computer-readable storage medium, specific examples including, but not limited to: magnetic storage devices, such as magnetic tape or Hard Disk Drives (HDDs); optical storage devices, such as compact disks (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and so on.

The computer-readable storage medium 1120 may include acomputer program 1121, and thecomputer program 1121 may include code/computer-executable instructions that, when executed by theprocessor 1110, cause theprocessor 1110 to perform a method according to an embodiment of the present disclosure, or any variation thereof.

Thecomputer programs 1121 can be configured to have, for example, computer program code including computer program modules. For example, in an example embodiment, code incomputer program 1121 may include one or more program modules, including, for example, 10121A, modules 1121B, … …. It should be noted that the division and number of modules are not fixed, and those skilled in the art may use suitable program modules or program module combinations according to actual situations, so that theprocessor 1110 may execute the method according to the embodiment of the present disclosure or any variation thereof when the program modules are executed by theprocessor 1110.

According to an embodiment of the present disclosure, at least one of thedata obtaining module 1001, the firstdata converting module 1002, and thedata forwarding module 1003 may be implemented as a computer program module described with reference to fig. 11, which, when executed by theprocessor 1110, may implement the corresponding operations described above.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

It will be understood by those skilled in the art that while the present disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. Accordingly, the scope of the present disclosure should not be limited to the above-described embodiments, but should be defined not only by the appended claims, but also by equivalents thereof.