TWM658447U - Trust business integrated system - Google Patents

Abstract

A trust business integrated system comprises a bank server, and the bank server is configured to receive trust business information of clients from variant trust institutions. The trust business integrated system further comprises an identity verification module, and the identity verification module connected to the bank server is configured to provide multiple trust data types for the clients to choose in the first step, to provide multiple identity types for the clients to choose in the second step, and to provide for the clients to verify their identities.

Description

Trust Business Integration System

The present disclosure relates to a trust business integration system, and in particular to a trust business integration system with different trust businesses and cross-unit data integration.

When customers conduct trust business in different banks or units, if they want to query the data records of different units, they need to use different platform systems or go to the bank in person. Data retrieval is inconvenient, time-consuming and laborious. In addition, data transmission between banks and other trust businesses also requires manpower and related administrative processes. Therefore, a trust business integration system is needed to solve the above problems.

This disclosure provides a trust business integration system. The data of each business unit is uploaded to the system, and different trust businesses and cross-unit data are integrated. When logging into the system according to different identities, all trust cases of domestic banks and construction management companies can be queried, which greatly increases convenience.

The embodiment of the present disclosure provides a trust business integration system, including a bank server configured to receive a plurality of trust business data from a client in a plurality of trust units. The trust business integration system also includes an identity verification module connected to the bank server and configured to provide the client with a choice of trust data type in the first step, provide the client with a choice of an identity category corresponding to the trust data type in the second step, and verify the client's identity in the third step.

In some embodiments, if the trust information type in the first step is a real estate sale price trust, the identity categories in the second step include buyers and sellers, land surveyors, brokerage firms, and construction management companies.

In some embodiments, if the trust information type in the first step is retirement trust, real estate trust, other money trust, securities trust, insurance trust, single parent orphan/disabled trust, public servant trust, and family asset trust, then the identity categories in the second step include settlor, trustee, beneficiary, designated guardian, and trust supervisor.

In some embodiments, if the trust data type in the first step is an employee benefit trust, the identity category in the second step includes company and employee.

In some embodiments, a login registration module is also included, which is connected to a bank server and configured to provide a customer registration account, wherein providing a customer registration account includes performing mobile phone verification.

In some embodiments, a storage unit is also included, which is connected to the bank server through the network and is configured to store the customer's trust business data in the trust unit.

In some embodiments, the bank server further includes a data management module configured to classify the trust business data of the customer in the trust unit into: a first trust data category, including real estate purchase and sale price trusts; a second trust data category, including retirement trusts, real estate trusts, other money trusts, securities trusts, insurance trusts, single-parent orphan/disabled trusts, public servant trusts, and family asset trusts; and a third trust data category, including employee welfare trusts.

In some embodiments, the identity verification module includes an operating interface in a display, wherein the operating interface is configured to display the trust data type in a first step; after the customer selects the trust data type, in a second step, display the identity category corresponding to the trust data type; and after the customer selects the identity category, in a third step, display the identity verification screen for identity verification.

In some embodiments, the trust business data of the customer in the trust unit includes bank trust data, deposit account data, balance and details.

In some embodiments, the bank server is further configured to receive trust business data from a client at a construction management company.

The following disclosure will be more fully described herein through drawings and references, and some exemplary embodiments are illustrated in the drawings. The disclosure may be implemented in different forms and should not be limited by the embodiments mentioned below. However, these embodiments are provided to help a more complete understanding of the content of the disclosure and to fully convey the scope of the disclosure to those skilled in the art. The same reference numerals will refer to similar elements throughout the text.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have their usual meanings, which are understood by those familiar with the field. Furthermore, the definitions of the above terms in commonly used dictionaries should be interpreted in the content of this specification as meanings consistent with the relevant fields of this disclosure. Unless otherwise clearly defined, these terms will not be interpreted as idealized or overly formal meanings.

The words “include,” “including,” “have,” and similar terms used herein specify the features, regions, integers, steps, operations, elements, and/or components described therein, but do not exclude the described or additional one or more other features, regions, integers, steps, operations, elements, components, and/or groups thereof.

Please refer to FIG. 1 for a schematic diagram of a trust business integration system 10 according to an embodiment of the present disclosure. As shown in FIG. 1 , the trust business integration system 10 includes a cloud database 100, a bank server 120, a data management module 125, an execution module 130, a login registration module 150, an identity verification module 160, a login query module 170, and a data retrieval module 180.

As shown in FIG. 1 , the cloud database 100 is connected to the bank server 120. In some embodiments, the cloud database 100 is a storage unit, and is connected to the bank server 120 via a network to access data. In some embodiments, the cloud database 100 can be an information access device, for example, a computer host, a memory device and/or a cloud storage space.

In some embodiments, the cloud database 100 may receive trust business data provided by the bank server 120. In some embodiments, the cloud database 100 may upload and store the received trust business data. In some embodiments, the trust business data includes the bank trust data, deposit account data, balance and details of the customer 140. In some embodiments, the trust business data also includes the customer 140's personal identity data and registration data.

In some embodiments, the bank server 120 may be a bank management system, which includes data transmission and receiving devices, such as computers, applications or other suitable devices. In some embodiments, taking the banking industry as an example, the bank server 120 is configured to perform data integration and management for the bank 105.

In some embodiments, the bank server 120 includes a data management module 125 and an execution module 130. In some embodiments, the bank 105 transmits data to the bank server 120, and performs data aggregation, analysis and management through the data management module 125 and the execution module 130. In some embodiments, the data management module 125 and the execution module 130 can perform maintenance management through an interface, wherein the interface can be a web page, an application or other suitable interface. In some embodiments, the data management module 125 can be a computer, an application or other suitable device. In some embodiments, the execution module 130 can be a computer, an application or other suitable device.

Referring to FIG. 1 , in some embodiments, the trust unit 110 and the construction management company 115 may provide the trust business data of the customer 140 to the bank 105. For example, the trust unit 110 and the construction management company 115 may provide the trust business of the customer 140 in different trust units, including deposit account data, balance and details, to the bank 105 for data integration and management. For example, the trust unit 110 may include different bank units. In more detail, the trust unit 110 includes at least two or more different trust units. Similarly, the construction management company 115 includes at least two or more different construction management companies.

Referring to FIG. 1 , the login registration module 150 can be connected to the bank server 120 for communication. In some embodiments, the communication connection between the login registration module 150 and the bank server 120 can be through the network. In some embodiments, the login registration module 150 can be a data receiving and transmitting device, such as a web page, application, software or other suitable interface. In some embodiments, the login registration module 150 can include peripheral input and output devices, such as a keyboard, mouse, touch panel or smart phone, and peripheral output devices such as a computer screen, display, touch panel, smart phone or other suitable operation interface.

In some embodiments, the customer 140 connects to the login registration module 150 through a web page, application or software to register, and fills in personal information in the interface, including setting the account as a personal ID number and password. In some embodiments, the personal information of the customer 140 includes an ID number, a set of passwords and a mobile phone number.

In some embodiments, the login and registration module 150 may transmit the personal data of the customer 140 to the bank server 120. In some embodiments, the bank server 120 may transmit the personal data of the customer 140 to the cloud database 100 for storage. In some embodiments, the personal data of the customer 140 will be integrated, analyzed and maintained by the bank 105 in the bank server 120.

Referring to FIG. 1 , the identity verification module 160 can be connected to the bank server 120 for communication. In some embodiments, the communication connection between the identity verification module 160 and the bank server 120 can be through a network. In some embodiments, the identity verification module 160 can be a data receiving, capturing and transmitting device, such as a computer, an application or other suitable device. In some embodiments, the identity verification module 160 can include peripheral input and output devices, such as a keyboard, a mouse, a touch panel or a smart phone, and peripheral output devices such as a computer screen, a display, a touch panel, a smart phone or other suitable operating interfaces. For example, the identity verification module 160 can be included in the operating interface of the display.

In some embodiments, after logging in and registering, the customer 140 needs to verify the identity through a mobile phone (i.e., verify the identity through a personal mobile phone number). In some embodiments, the customer 140 connects to the identity verification module 160 through a web page, application, or software to verify the identity, enters the personal mobile phone number in the identity verification interface, and enters the verification code received in the SMS into the identity verification interface. In some embodiments, the identity verification module 160 can perform identity verification after communicating with the bank server 120, and upload the customer 140 identity verification data and verification results to the bank server 120 and the cloud database 100.

Referring to FIG. 1 , the login query module 170 can be connected to the data retrieval module 180 for communication. In some embodiments, the communication between the login query module 170 and the data retrieval module 180 can be through a network. In some embodiments, the login query module 170 can be a data receiving, capturing and transmitting device, such as a computer, application, software or other suitable device. In some embodiments, the login query module 170 can include peripheral input and output devices, such as a keyboard, mouse, touch panel or smart phone, and peripheral output devices such as a computer screen, display, touch panel, smart phone or other suitable operating interface.

Referring to FIG. 1 , the data retrieval module 180 is connected to the bank server 120. In some embodiments, the connection between the data retrieval module 180 and the bank server 120 can be through a network. In some embodiments, the data retrieval module 180 can be a data acquisition device, for example, a computer, an application or software. In some embodiments, the data retrieval module 180 can acquire trust business data provided by the bank server 120. In some embodiments, the data retrieval module 180 can display the trust business data provided by the bank server 120 in the interface through the login query module 170.

In some embodiments, after the identity of the customer 140 is verified, the login query module 170 and the data retrieval module 180 are connected to the bank server 120 through the network. In some embodiments, the login query module 170 and the data retrieval module 180 are configured to provide the customer 140 with an interface for querying trust business data.

It should be understood that in the scope of the patent application, the description involving "communication connection" can generally refer to one component indirectly communicating with another component through other components by wire and/or wireless, or one component being physically connected to another component without going through other components.

Please refer to FIG. 2, which is a flowchart of the operation of the trust business integration system according to the embodiment of the present disclosure. In more detail, FIG. 2 provides an operation method M1 for operating the trust business integration system 10 of FIG. 1. The method M1 includes an operation S101, uploading data. The method M1 also includes an operation S102, the customer registers his identity. The method M1 also includes an operation S103, logging into the system. The method M1 also includes an operation S104, querying data.

Please refer to Figure 1 and Figure 2. The bank 105 can upload the received trust business data to the bank server 120 and store it in the cloud database 100. In some embodiments, the trust unit 110 can be more than two and different banks. In some embodiments, the construction management company 115 can be more than two and different construction management companies. In some embodiments, the bank 105 can receive the trust business data provided by the trust unit 110 and the construction management company 115.

In some embodiments, the client 140 connects to the login registration module 150 through a web page, application or software to register, and fills in personal information and sets a password in the interface. In some embodiments, after logging in and registering, the client 140 uses a personal mobile phone number for identity verification.

In some embodiments, the client 140 can select the trust data type, identity and identity verification according to the steps in the operation interface displayed by the identity verification module 160. In some embodiments, after the identity verification is confirmed, the client 140 can query the trust business data in the subsequent login interface.

In some embodiments, the trust business data includes real estate purchase and sale trust, retirement trust, real estate trust, other money trust, securities trust, insurance trust, single parent orphan/disabled trust, public servant trust, family asset trust, and employee welfare trust. In some embodiments, the data management module 125 is configured to divide the trust business data into three categories. In some embodiments, trust business data is divided into three categories. The first category is real estate purchase and sale price trusts, the second category is retirement trusts, real estate trusts, other money trusts, securities trusts, insurance trusts, single-parent orphan/disabled trusts, public servant trusts, and family asset trusts; the third category is employee benefit trusts.

In some embodiments, the client 140 can select different trust data categories, where the trust data is divided into three categories. In some embodiments, the first trust data category is real estate purchase price trust. In some embodiments, the second trust business category is retirement trust, real estate trust, other money trust, securities trust, insurance trust, single parent orphan/disabled trust, public servant trust, family asset trust. In some embodiments, the third trust business category is employee welfare trust.

In some embodiments, after the customer 140 selects the first trust business category in the interface, he can then query different identities. In some embodiments, after the customer 140 selects the first trust business category, the identities that can be selected include buyers and sellers, land surveyors, brokerages, and construction management companies.

In some embodiments, after the customer 140 selects the second trust business category in the interface, he can query different identities. In some embodiments, after the customer 140 selects the second trust business category, the selectable identities include the principal, the trustee, the beneficiary, the designated guardian, and the trust supervisor.

In some embodiments, after the customer 140 selects the third trust business category in the interface, he can query for different identities. In some embodiments, after the customer 140 selects the third trust business category, the identities that can be selected include company and employee.

In some embodiments, after the customer 140 selects the trust data type, the interface displays the identity category corresponding to the trust data type. In some embodiments, after the customer 140 selects the identity category, the identity verification screen is displayed in the interface. In some embodiments, after the customer 140 fills in the personal identity and completes the identity verification, the trust business data query can be performed.

In some embodiments, after the identity information of the client 140 is verified, the client 140 can query the trust business information in the interface through the login query module 170 and the data retrieval module 180. In some embodiments, the client 140 can query the trust business information in the interface including the account balance, transaction details, transaction time and entrustment handling progress.

In some embodiments, the bank 105 may query the trust business data of the customer 140 through the bank server 120 and the data retrieval module 180.

The foregoing description is only provided to illustrate and describe the exemplary embodiments of the present disclosure, and is not intended to limit the precise form of the novel invention disclosed by the present disclosure. The above teachings may be modified or varied.

The embodiments selected and described are used to explain the content of the present disclosure and their practical applications to inspire other technical personnel in the field to utilize the present disclosure and various embodiments, and to make various modifications to meet the expected specific use. Alternative embodiments will be obvious to technical personnel in the field to which the present disclosure belongs without departing from the spirit and scope of the present disclosure. Therefore, the scope of the present disclosure is determined according to the scope of the attached new patent application, rather than being limited by the above specification and the exemplary embodiments described therein.

10: Trust business integration system 100: Cloud database 105: Bank 110: Trust unit 115: Construction management company 120: Bank server 125: Data management module 130: Execution module 140: Customer 150: Login registration module 160: Identity verification module 170: Login query module 180: Data retrieval module M1: Method S101: Operation S102: Operation S103: Operation S104: Operation

The drawings illustrate one or more embodiments of the present disclosure and are used together with the written description to explain the principles of the present disclosure. In all drawings, the same drawing marks are used as much as possible to refer to similar or identical elements of the embodiments, wherein: FIG. 1 is a schematic diagram of a trust business integration system according to an embodiment of the present disclosure. FIG. 2 is an operation flow chart of a trust business integration system according to an embodiment of the present disclosure.

10: Trust business integration system

100: Cloud database

105: Bank

110: Trust unit

115: Construction management company

120: Bank server

125: Data management module

130: Execution module

140: Customer

150: Login and registration module

160: Identity verification module

170: Login query module

180:Data retrieval module

Claims (10)

A trust business integration system comprises: A bank server configured to receive a plurality of trust business data from a client in a plurality of trust units; and An identity verification module connected to the bank server and configured to: In a first step, provide the client with a choice of a trust data type; In a second step, provide the client with a choice of an identity category corresponding to the trust data type; and In a third step, perform an identity verification on the client. The trust business integration system as described in claim 1, wherein if the trust data type in the first step is a real estate sale price trust, the identity category in the second step includes buyers and sellers, land surveyors, brokerage firms, and construction management companies. The trust business integration system as described in claim 1, wherein if the trust data type in the first step is retirement trust, real estate trust, other money trust, securities trust, insurance trust, single parent orphan/disabled trust, public servant trust, and family asset trust, then the identity category in the second step includes settlor, trustee, beneficiary, designated guardian, and trust supervisor. A trust business integration system as described in claim 1, wherein if the trust data type in the first step is an employee benefit trust, the identity category in the second step includes a company and an employee. The trust business integration system as described in claim 1 further includes a login registration module connected to the bank server and configured to provide the customer with an account registration, wherein providing the customer with the account registration includes performing a mobile phone verification. The trust business integration system as described in claim 1 further comprises a storage unit connected to the bank server via a network and configured to store the trust business data of the customer in the trust units. The trust business integration system as described in claim 1, wherein the bank server further includes a data management module configured to classify the trust business data of the client in the trust units into: A first trust data category, including real estate purchase and sale price trusts; A second trust data category, including retirement trusts, real estate trusts, other money trusts, securities trusts, insurance trusts, single-parent orphan/disabled trusts, public servant trusts, and family asset trusts; and A third trust data category, including employee welfare trusts. A trust business integration system as described in claim 1, wherein the identity verification module includes an operation interface in a display, wherein the operation interface is configured to: In the first step, display the trust data type; After the customer selects the trust data type, in the second step, display the identity category corresponding to the trust data type; and After the customer selects the identity category, in the third step, display an identity verification screen for performing the identity verification. The trust business integration system as described in claim 1, wherein the trust business data of the client in the trust units includes bank trust data, deposit account data, balance and details. The trust business integration system as described in claim 1, wherein the bank server is further configured to receive trust business data from the client in a construction management company.

Images