WO2019056769A1 - 基于关联交易数据处理的优化方法、装置和计算机设备 - Google Patents

基于关联交易数据处理的优化方法、装置和计算机设备 Download PDF

Info

Publication number
WO2019056769A1
WO2019056769A1 PCT/CN2018/086272 CN2018086272W WO2019056769A1 WO 2019056769 A1 WO2019056769 A1 WO 2019056769A1 CN 2018086272 W CN2018086272 W CN 2018086272W WO 2019056769 A1 WO2019056769 A1 WO 2019056769A1
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
source
target
data
database
Prior art date
Application number
PCT/CN2018/086272
Other languages
English (en)
French (fr)
Inventor
卿松
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019056769A1 publication Critical patent/WO2019056769A1/zh
Priority to PH12019501066A priority Critical patent/PH12019501066A1/en

Links

Images

Classifications

    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • 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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • the present application relates to an optimization method, apparatus and computer device based on associated transaction data processing.
  • a related party transaction is a transaction between related parties.
  • One of the related parties may control or have a significant influence on the financial and business strategy of the other party.
  • One of the related parties may also be the company directly or indirectly controlling the other party.
  • an insurance company usually has a parent company, a branch company, a subsidiary company, a holding company, and a shareholding company.
  • a number of subsidiaries, holding companies and shareholding companies within the insurance company can be related parties and then carry out related party transactions.
  • a connected transaction is a transaction that often occurs in the operation of an insurance company and is prone to unfair results.
  • eligible connected transactions need to be disclosed or reported to the regulatory authorities. Before a related party transaction is disclosed or reported, it needs to be approved within the insurance company.
  • each institution in an insurance company usually aggregates the related transactions on a monthly or quarterly basis, and reports the related transactions that need to be disclosed or reported to the parent company, and the parent company performs internal approval on it. .
  • the internal approval work is complicated, but also the approval time is prolonged, resulting in a decline in the efficiency of the examination and approval. Therefore, how to effectively improve the internal approval efficiency of connected transactions has become a technical problem that needs to be solved.
  • an optimization method, apparatus, computer device, and storage medium based on associated transaction data processing are provided.
  • An optimization method based on data processing of associated transactions including:
  • association list uploaded by a plurality of terminals, where the association list includes an organization name of the organization and a related party corresponding to the institution;
  • An optimization device based on associated transaction data processing comprising:
  • a communication module configured to receive an association list uploaded by multiple terminals, where the association list includes an organization name of the organization and a related party corresponding to the institution;
  • a synchronization module configured to acquire, according to the organization name, a source database name corresponding to the organization, and synchronize the service data of the multiple source databases to the target database in real time according to the multiple source database names;
  • An extracting module configured to extract corresponding related transactions by using the related party corresponding to the organization name and the service data in the target database
  • a simplification module configured to query, according to the extracted transaction parties, whether there is a corresponding first preset file, and when the first preset file is queried, calculate a remaining credit corresponding to the first preset file; Obtaining the transaction amount corresponding to the related transaction, and if the transaction amount is less than or equal to the remaining amount, recording the related transaction as a related transaction for simplifying the approval process.
  • a computer device comprising a memory and one or more processors having stored therein computer readable instructions, the computer readable instructions being executable by the processor to cause the one or more processors to execute The following steps:
  • association list uploaded by a plurality of terminals, where the association list includes an organization name of the organization and a related party corresponding to the institution;
  • One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:
  • association list uploaded by a plurality of terminals, where the association list includes an organization name of the organization and a related party corresponding to the institution;
  • FIG. 1 is an application scenario diagram of an optimization method based on associated transaction data processing in accordance with one or more embodiments
  • FIG. 2 is a flow diagram of an optimization method based on associated transaction data processing in accordance with one or more embodiments
  • FIG. 3 is a block diagram of an optimization device based on associated transaction data processing in accordance with one or more embodiments
  • FIG. 4 is a block diagram of a computer device in accordance with one or more embodiments.
  • the present application provides an optimization method based on associated transaction data processing, which can be applied to an application environment as shown in FIG. 1.
  • the first terminal 102 is in communication connection with the server 104 via a network.
  • the second terminal 106 is in communication connection with the server 104 via a network.
  • a plurality of organizations may upload an association list to the server 104 through the first terminal 102, respectively.
  • the association list includes the name of the organization and a number of related parties associated with the institution.
  • Each organization has corresponding business data.
  • the business data of each organization is stored in the corresponding source database.
  • the source database can be deployed on the server 104.
  • a target database is also deployed on the server 104.
  • the server 104 can obtain the source database name corresponding to the organization name according to the organization name.
  • the server 104 Synchronize business data from multiple source databases to the target database in real time based on multiple source database names.
  • the server 104 extracts the corresponding related transaction in the target database by using the related party and business data corresponding to the organization name.
  • the server 104 queries whether the corresponding first preset file exists according to the two sides of the transaction of the extracted related transaction.
  • the server 104 calculates the remaining credit corresponding to the first preset file.
  • the server 104 compares the transaction amount of the associated transaction with the remaining amount, and if the transaction amount is less than or equal to the remaining amount, records the related transaction as an associated transaction that simplifies the approval process.
  • the server 104 obtains the simplified approval process, and sends the related transaction to the second terminal for approval according to the simplified approval process.
  • an optimization method based on the associated transaction data processing is provided.
  • the method is applied to the server in FIG. 1 as an example, and specifically includes the following steps:
  • Step 202 Receive an association list uploaded by multiple terminals, where the association list includes an organization name of the organization and a related party corresponding to the organization.
  • Step 204 Acquire a source database name corresponding to the organization according to the organization name, and synchronize the service data of the multiple source databases to the target database in real time according to the multiple source database names.
  • Step 206 Extract corresponding transaction in the target database by using the related party and the business data corresponding to the organization name.
  • Step 208 The two parties in the transaction according to the extracted associated transaction query whether there is a corresponding first preset file. When the first preset file is queried, the remaining credit corresponding to the first preset file is calculated.
  • Step 210 Acquire a transaction amount corresponding to the related transaction. If the transaction amount is less than or equal to the remaining amount, record the related transaction as a related transaction that simplifies the approval process.
  • the parent company of an insurance company may be referred to as institutions.
  • Institutions can be related to each other and conduct related party transactions. Institutions can also interact with external companies to conduct related party transactions.
  • the organization may upload an association list to the server of the parent company of the insurance company through the terminal (which may be the first terminal in FIG. 1).
  • the association list includes the name of the organization and a number of related parties associated with the institution.
  • Each organization has corresponding business data, and business data includes transaction data and financial data.
  • Transaction data can be data generated by an institution's transactions with other institutions or other companies, such as the party, the transaction identifier, and the transaction amount.
  • the transaction identifier may be the contract name of the transaction or the contract number of the transaction.
  • Financial data includes the amount of assets of an organization, such as the amount of audited net assets, the total amount of assets at the end of the previous quarter, and the amount of net assets.
  • the business data of each organization is stored in the corresponding source database.
  • the source database can be deployed on the parent company's server or on the organization's own server.
  • the servers of each organization can establish a connection with the server of the parent company.
  • One or more source data tables are stored in the source database.
  • the organization's business data can be stored in a source data table or in multiple source data tables.
  • the transaction data and financial data can be stored in different data tables.
  • Business data from different organizations can be stored in different source databases. Understandably, business data of some different organizations can also be stored in the same source database.
  • Each source database has a corresponding source database name. Multiple source database names and corresponding organization names are recorded in the server.
  • the target database is pre-created on the server, and the target database also has the corresponding target database name.
  • a target data table is created in the target database.
  • the server can obtain the source database name corresponding to each organization according to the organization name.
  • the server can obtain the source data table in the source database according to the original database name.
  • the server reads the business data in the source data table.
  • the server can synchronize the read business data to the target database in real time.
  • the server can perform real-time synchronization operations on the business data in multiple source databases at the same time, or perform real-time synchronization operations on the business data in each source database.
  • the server extracts the corresponding related transaction in the target database by using the related party and business data corresponding to the organization name. Specifically, the server reads the service data in the target database, and obtains the corresponding transaction party according to the organization name. If the transaction party is the related party corresponding to the organization name, the server records the service data as the service data corresponding to the associated transaction. The server can add tags for associated transactions to the business data, thereby extracting multiple associated transactions. Since the business data in the target database is obtained from real-time synchronization from multiple source databases, the related transactions can be extracted in time, so that the related transactions are internally approved. In this embodiment, the related transactions are no longer counted on a monthly or quarterly basis, thereby avoiding the problem that the internal approval time is extended due to the submission of the approval of the related transaction.
  • the server queries whether the corresponding first preset file exists according to the two sides of the transaction of the extracted related transaction.
  • the first preset file may be a motion file or an announcement file or the like. If the corresponding first preset file is queried, the server acquires the total transaction amount in the first preset file.
  • the server queries the corresponding historical related transaction according to the transaction parties of the related transaction, obtains the transaction amount in the historical related transaction, and calculates the accumulated transaction amount according to the transaction amount of the historical related transaction.
  • the server uses the total transaction amount in the first preset file minus the accumulated transaction amount to obtain the corresponding remaining amount. If the server does not query the historical related transaction corresponding to both parties of the transaction, the total transaction amount in the first preset file can be regarded as the aforementioned remaining amount.
  • the server obtains the transaction amount of the related transaction, compares the transaction amount with the remaining amount, and records the related transaction as the related transaction of the simplified approval process if the transaction amount is less than or equal to the remaining amount.
  • the original approval process for an associated transaction is: executive director approval and board approval.
  • the related party transaction is recorded as a related transaction that simplifies the process approval, the corresponding approval process is: executive director approval.
  • the board of directors has been reduced, which has effectively improved the efficiency of examination and approval.
  • the real-time synchronization operation of the service data in the source database corresponding to the plurality of organization names can synchronize the service data of the plurality of organizations to the target database in real time. Therefore, it is possible to extract related transactions in time in the target database for the business data of all organizations, and avoid the problem that the related transactions are collectively submitted for internal approval and the approval time is extended. If the related transaction has a corresponding first preset file, and the transaction amount of the related transaction is less than the remaining amount corresponding to the first preset file, the approval process of the related transaction may be simplified, and the internal approval link of the related transaction is reduced. This effectively improves the internal approval efficiency of connected transactions.
  • steps in the flowchart of FIG. 2 are sequentially displayed as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIG. 2 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, the execution of these sub-steps or stages The order is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of the other steps.
  • the association list further includes a supervision department corresponding to the organization name; after the step of extracting the corresponding related transaction by using the related party and the business data corresponding to the organization name in the target database, the method further includes: obtaining the calculation corresponding to the supervision department Rules; use the business data corresponding to the associated transaction and the calculation rules corresponding to the regulatory department to extract significant related transactions in the connected transaction.
  • the association list may include, in addition to the organization name, a plurality of related parties associated with the institution, the supervision department of the institution, and the like.
  • An organization can have multiple regulatory agencies. Different agencies can have different regulatory authorities.
  • the server obtains the supervision department corresponding to the organization name according to the transaction list, and obtains corresponding calculation rules according to the supervision department. Among them, the calculation rules include calculation rules for major related transactions.
  • the server calculates the business data corresponding to the related transaction by using the calculation rule of the major related transaction, and obtains the corresponding calculation result. If the calculation result indicates that the related transaction belongs to a major related transaction, the server records the corresponding business data as the business data corresponding to the major related transaction.
  • the server can add tags for significant associated transactions to business data. This extracts one or more significant related transactions.
  • the server obtains the calculation rules of each related department for major related transactions, and the calculation rules of different supervisory departments are different, and the business data required for calculation may also be different.
  • the server uses the calculation rule of the major related party transaction of the regulatory department to calculate the business data corresponding to the related party transaction corresponding to the institution name one by one. If the calculation result indicates that the related party transaction belongs to a major related party transaction required by multiple regulatory departments, the server separately Mark the corresponding regulatory authorities for major related party transactions.
  • the corresponding calculation rule is that the transaction amount (abbreviated as AB) of the related transaction is greater than 30000000, and the transaction amount (AB) and the latest audited net asset amount of the group company ( The ratio abbreviated as AD) is greater than 5%.
  • the above calculation rule can be expressed by the following formula: AB>30000000 and AB/
  • the server marks the related party transaction as a significant related party transaction reported by the upstate.
  • the corresponding calculation rule is that the transaction amount (AB) of the related transaction is greater than 30000000, or the transaction amount (AB) and the latest audited net asset amount (abbreviated as IE).
  • the ratio is greater than 1%, or the transaction amount (AB) plus the cumulative amount of associated transactions with the same related party (abbreviated as IC) divided by the most recent audited net asset amount (IE) ratio greater than 5% .
  • the above calculation rule can be expressed by the following formula: AB>30000000; or AB/IE>1%; or (AB+IC)/IE>5%.
  • the supervisory department corresponding to the name of the institution includes the Shanghai Stock Exchange and the China Insurance Regulatory Commission
  • the business data corresponding to the associated transaction corresponding to the name of the institution is calculated by using the calculation rules of the Shanghai Stock Exchange and the calculation rule distribution of the China Insurance Regulatory Commission. If the calculation result satisfies both the calculation rules of the Shanghai Stock Exchange and the calculation rules of the China Insurance Regulatory Commission, the server marks the related party transaction as a significant related party transaction reported by the Shanghai Stock Exchange and a significant related party transaction reported to the China Insurance Regulatory Commission.
  • Significant related party transactions should be reported to the corresponding regulatory authorities so that the regulatory authorities can supervise them. Internal approval is also required before major related recommendations are reported.
  • the server can further identify whether the major related party transaction is a connected transaction that simplifies the approval process, in order to facilitate internal approval of significant related party transactions in accordance with the simplified approval process.
  • the method further includes: acquiring a second preset file corresponding to the major associated transaction, where the second preset file includes a preset service type and an upper limit; and acquiring a service type of the major related transaction and a transaction amount;
  • the business type is the default business type and the transaction amount is less than the upper limit
  • the major related transaction is recorded as the related transaction that simplifies the approval process.
  • the server queries whether there is a corresponding second preset file according to the major associated transaction.
  • the second preset file may be a framework protocol or the like.
  • the second preset file includes a preset service type and an upper limit corresponding to a major related transaction.
  • the default business type can be a loan or a loan.
  • the server queries the counterparty of the major related party transaction for the existence of historical related transactions. If there is a historical associated transaction, the server calculates the cumulative transaction amount for the historical associated transaction. The server uses the upper limit minus the cumulative transaction amount to obtain the available amount. If the server does not query the historical related transaction corresponding to the two parties of the transaction, the upper limit in the second preset file can be regarded as the aforementioned available credit.
  • the server compares the transaction amount of the major related transaction with the available amount. If the transaction amount of the major related transaction is less than or equal to the available amount, the server records the significant related transaction as the related transaction of the simplified approval process. For example, a major related party transaction that should be reported to the China Insurance Regulatory Commission may be exempted from the approval of the board of directors and reported to the China Insurance Regulatory Commission after being recorded as a related transaction that simplifies the approval process. This has improved the internal approval efficiency of this major connected transaction.
  • the target database stores a target data table, where the target data table includes a supervision field corresponding to the supervision department; and the step of synchronizing the service data of the multiple source databases to the target database according to the multiple source database names in real time includes: : Listening to write operations of multiple source databases according to source data names; when listening to service data corresponding to the supervised fields is written to the source database, triggering synchronous operation of the source data to the target data; by synchronizing operations in the source database Read the business data corresponding to the supervision field; write the read business data to the target data table in the target database in real time.
  • the service data of each organization may be separately stored in the data table of the corresponding source database.
  • the source data table may include multiple fields of business data, that is, multiple fields of transaction data and financial data.
  • the fields corresponding to the transaction data include the transaction identifier, the transaction type, the transaction amount, the counterparty, and the transaction time.
  • the fields corresponding to the financial data include audited net assets, accumulated amounts, and net capital. Multiple fields of the transaction data and multiple fields of the financial data may be set in the same source data table, or may be set in different source data tables.
  • a target data table is pre-created in the target database.
  • Multiple governance fields are included in the target data table.
  • the regulatory field can be set according to regulatory requirements of the regulatory body. Different regulatory authorities may have different regulatory fields. Understandably, the regulatory authorities may be the same, and the corresponding regulatory fields may be the same.
  • the name of the supervised field can be the same or the same for the field names of the business data.
  • the server obtains the source database name corresponding to the organization name.
  • the server invocation script listens for writes to multiple source databases based on the source database name.
  • the service data corresponding to the supervision field is detected to be written to the source database, the synchronization operation of the source database to the target database is triggered.
  • the server call thread uses the supervision field to generate SQL statements.
  • the server reads the service data of the corresponding field in the source data table of the source database through the SQL statement.
  • the server writes the read business data in real time to the target data table of the target database. Since the server only extracts the corresponding field in the source data table and writes the target data table when performing the synchronization operation, and does not need to perform the whole table extraction on the source data table to write to the target database, the data read operation and the write operation are saved. When it is effective, the efficiency of data synchronization is effectively improved.
  • the server calls multiple threads respectively, and uses the SQL statement to concurrently execute the operation of reading the source data table in the source database.
  • the server writes the business data read from multiple source data tables in real time to the target data table of the target database.
  • the multi-threaded concurrent synchronization operation further improves the efficiency of data synchronization between multiple source databases to target data.
  • the server may perform full synchronization of the service data corresponding to the supervision field during the first synchronization operation, and the server may perform the service corresponding to the supervision field during the second synchronization operation and the subsequent synchronization operation.
  • the data is incrementally synchronized.
  • the step of synchronizing the service data of the plurality of source databases to the target database according to the plurality of source database names comprises: reading the source log files in the plurality of source databases in real time according to the source database name, and the source log file records Business data; write the source log file to the target database; use the multiple source log files in the target database to generate the corresponding target log file; use the target log file to extract the corresponding business data.
  • the corresponding log file is recorded in the write operation and the read operation of the service data in the source database.
  • Log files recorded in the source database can also be referred to as source log files.
  • the log file records the read and write operations of the business data, including the read and write operations of the transaction data and financial data.
  • the server call thread reads source log files in multiple source databases in real time, and writes the read source log files to the target database.
  • the server uses the multiple source log files in the target database to generate the target log files.
  • a target data table is pre-created in the target database.
  • Multiple governance fields are included in the target data table.
  • the regulatory field can be set according to regulatory requirements of the regulatory body. Different regulatory authorities may have different regulatory fields. Understandably, the regulatory authorities may be the same, and the corresponding regulatory fields may be the same.
  • the name of the supervised field can be the same or the same for the field names of the business data.
  • the server parses the target log file and obtains the parsed log file.
  • the server extracts the corresponding service data in the parsed log file by using the name of the supervision field, and writes the extracted service data into the target data table according to the supervision field.
  • the source log files can effectively reflect the read and write status of data in the source database.
  • the business data written in the source database can be known.
  • the business data written in the plurality of source databases can be obtained. Since the source log file is usually smaller than the source data table, synchronizing the source log file requires less time than synchronizing the source data table, thereby improving the efficiency of data synchronization.
  • the server can perform full synchronization of the source log files during the first synchronization operation, and the server can incrementally synchronize the source log files during the second synchronization operation and subsequent synchronization operations.
  • the present application also provides an optimization apparatus based on associated transaction data processing.
  • the apparatus includes a communication module 302, a synchronization module 304, an extraction module 306, and a simplification module 308, each of which may be implemented in software, hardware, or a combination thereof. among them:
  • the communication module 302 is configured to receive an association list uploaded by multiple terminals, where the association list includes an organization name of the organization and an associated party corresponding to the organization.
  • the synchronization module 304 is configured to obtain a source database name corresponding to the organization according to the organization name, and synchronize the service data of the multiple source databases to the target database in real time according to the multiple source database names.
  • the extracting module 306 is configured to extract corresponding related transactions in the target database by using related parties and business data corresponding to the organization name.
  • the simplification module 308 is configured to query, according to the extracted transaction parties, whether there is a corresponding first preset file, and when the first preset file is queried, calculate a remaining credit corresponding to the first preset file; The corresponding transaction amount, if the transaction amount is less than or equal to the remaining amount, the related transaction is recorded as a related transaction that simplifies the approval process.
  • the association list further includes a supervision department corresponding to the organization name; the extraction module 306 is further configured to obtain a calculation rule corresponding to the supervision department; and use the business data corresponding to the association transaction and the calculation rule corresponding to the supervision department in the related transaction. Extract significant related party transactions.
  • the simplification module 308 is further configured to obtain a second preset file corresponding to the major associated transaction, where the second preset file includes a preset service type and an upper limit degree; and the service type of the major related transaction and the transaction amount; When the business type is the default business type and the transaction amount is less than the upper limit, the major related transaction is recorded as the related transaction that simplifies the approval process.
  • a target data table is stored in the target database, and the target data table includes a supervision field corresponding to the supervision department; the synchronization module 304 is further configured to monitor the write operations of the multiple source databases according to the source data name; When the service data corresponding to the supervision field is detected and written to the source database, the synchronization operation of the source data to the target data is triggered; the service data corresponding to the supervision field is read in the source database by the synchronization operation; and the read service data is real-time. Write to the target data table in the target database.
  • the synchronization module 304 is further configured to read source log files in multiple source databases in real time according to the source database name, the source log files record business data, write the source log files to the target database, and in the target database.
  • the corresponding target log file is generated by using multiple source log files; the corresponding business data is extracted by using the target log file.
  • Each of the above-described modules in the optimization device based on the associated transaction data processing may be implemented in whole or in part by software, hardware, and combinations thereof.
  • Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.
  • a computer device for example, the computer device can be a server.
  • the computer device includes a processor, a memory, and a network interface connected by a system bus.
  • the processor of the computer device is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium and an internal memory.
  • the non-volatile storage medium of the computer device stores an operating system and computer readable instructions.
  • the non-volatile storage medium can be a non-transitory computer readable storage medium.
  • the internal memory of the computer device provides an environment for the operation of an operating system and computer readable instructions in a non-volatile storage medium.
  • the network interface of the computer device is used to communicate with an external terminal via a network connection.
  • the computer readable instructions are executed by the processor to implement an optimization method based on associated transaction data processing.
  • the computer device can be a standalone server or a cluster server. It will be understood by those skilled in the art that the structure shown in FIG. 4 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied.
  • the specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
  • a computer apparatus comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by the processor, cause The one or more processors perform the steps in the various method embodiments described above.
  • one or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, causing one or more processors The steps in the various method embodiments described above are performed.
  • the readable storage medium which when executed, may include the flow of an embodiment of the methods as described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Tourism & Hospitality (AREA)
  • Data Mining & Analysis (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Finance (AREA)
  • Game Theory and Decision Science (AREA)
  • Computing Systems (AREA)
  • Technology Law (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种基于关联交易数据处理的优化方法，包括：接收多个终端上传的关联清单，关联清单中包括了机构的机构名称及与机构对应的关联方；根据机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；在目标数据库中利用机构名称对应的关联方和业务数据提取相应的关联交易；根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到第一预设文件时，计算第一预设文件对应的剩余额度；获取关联交易对应的交易金额，若交易金额小于或等于剩余额度，则将关联交易记录为简化审批流程的关联交易。

Description

基于关联交易数据处理的优化方法、装置和计算机设备
本申请要求于2017年9月25日提交中国专利局，申请号为2017108749572，申请名称为“基于关联交易数据处理的优化方法、装置和计算机设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及一种基于关联交易数据处理的优化方法、装置和计算机设备。
背景技术
关联交易是关联方之间的交易。关联方中的一方可以对另一方的财务和经营策略进行控制或者有重大影响。关联方中的一方还可以是公司直接或间接控股另一方等。以保险公司为例，通常会下设母公司、分公司、子公司、控股公司以及参股公司等机构。保险公司内部的多家子公司、控股公司以及参股公司等可以互为关联方，继而进行关联交易。关联交易是保险公司运作中经常出现的、又易于发生不公平结果的交易。为了规范关联交易行为，有效防范经营风险，符合条件的关联交易需要进行披露或上报至监管部门。关联交易被披露或上报之前，需要在保险公司内部进行审批。
在传统的方式中，保险公司中的各家机构通常是按月或按季度等对关联交易分别进行汇总统计，将需要披露或上报的关联交易上报给母公司，由母公司对其执行内部审批。通常走完一项关联交易的审批流程需要耗费几天时间，面对大量的关联交易，不仅造成内部审批的工作繁多，也会延长审批耗时，导致审批效率下降。因此，如何有效提高关联交易的内部审批效率成为目前需要解决的一个技术问题。
发明内容
根据本申请公开的各种实施例，提供一种基于关联交易数据处理的优化方法、装置、计算机设备和存储介质。
一种基于关联交易数据处理的优化方法，包括：
接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
根据所述机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；
在所述目标数据库中利用所述机构对应的关联方和所述业务数据提取相应的关联交易；
根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；及
获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
一种基于关联交易数据处理的优化装置，包括：
通信模块，用于接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
同步模块，用于根据所述机构名称获取与机构对应的源数据库名称，根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库；
提取模块，用于在所述目标数据库中利用所述机构名称对应的关联方和所述业务数据提取相应的关联交易；及
简化模块，用于根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
一种计算机设备，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：
接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
根据所述机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；
在所述目标数据库中利用所述机构对应的关联方和所述业务数据提取相应的关联交易；
根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；及
获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
根据所述机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；
在所述目标数据库中利用所述机构对应的关联方和所述业务数据提取相应的关联交易；
根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；及
获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
本申请的一个或多个实施例的细节在下面的附图和描述中提出。本申请的其它特征和优点将从说明书、附图以及权利要求书变得明显。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为根据一个或多个实施例中基于关联交易数据处理的优化方法的应用场景图；
图2为根据一个或多个实施例中基于关联交易数据处理的优化方法的流程图；
图3为根据一个或多个实施例中基于关联交易数据处理的优化装置的框图；
图4为根据一个或多个实施例中计算机设备的框图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请提供基于关联交易数据处理的优化方法，可以应用于如图1所示的应用环境中。第一终端102通过网络与服务器104进行通信连接。第二终端106通过网络与服务器104进行通信连接。多个机构可以通过第一终端102分别向服务器104上传关联清单。关联清单中包括了机构名称以及与该机构具有关联关系的多个关联方等。每个机构都具有相应的业务数据。各个机构的业务数据存入相应的源数据库中。源数据库可以部署在服务器104上。服务器104上还部署了目标数据库。服务器104根据机构名称可以获取与机构名称对应的源数据库名称。根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库。服务器104在目标数据库中利用机构名称对应的关联方和业务数据提取相应的关联交易。服务器104根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件。服务器104计算该第一预设 文件对应的剩余额度。服务器104将关联交易的交易金额与剩余额度进行比较，如果交易金额小于或等于剩余额度，则将该关联交易记录为简化审批流程的关联交易。服务器104获取简化后的审批流程，根据简化后的审批流程将该关联交易发送至第二终端进行审批。
在一个实施例中，如图2所示，提供了一种基于关联交易数据处理的优化方法，以该方法应用于图1中的服务器为例进行说明，具体包括以下步骤：
步骤202，接收多个终端上传的关联清单，关联清单中包括了机构的机构名称及与机构对应的关联方。
步骤204，根据机构名称获取与机构对应的源数据库名称，根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库。
步骤206，在目标数据库中利用机构名称对应的关联方和业务数据提取相应的关联交易。
步骤208，根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到第一预设文件时，计算第一预设文件对应的剩余额度。
步骤210，获取关联交易对应的交易金额，若交易金额小于或等于剩余额度，则将关联交易记录为简化审批流程的关联交易。
保险公司的母公司以及下设的分公司、子公司、控股公司以及参股公司等可以称为机构。机构之间可以互为关联方，进行关联交易。机构还可以与外部企业互为关联方，进行关联交易。机构可以通过终端(可以是图1中的第一终端)向保险公司母公司的服务器上传关联清单。关联清单中包括了机构名称以及与该机构具有关联关系的多个关联方等。
每个机构都具有相应的业务数据，业务数据包括交易数据和财务数据等。交易数据可以是机构与其他机构或其他企业进行交易所产生的数据，例如，交易方、交易标识和交易金额等。其中，交易标识可以是交易的合同名称或交易的合同号等。财务数据包括机构的多种资产金额，例如，经审计净资产金额、上季度末总资产金额和净资产金额等。各个机构的业务数据存入相应的源数据库中。源数据库可以部署在母公司的服务器上，也可以部署在机构 自己的服务器上。各机构的服务器可以与母公司的服务器建立连接。源数据库中存有一个或多个源数据表。机构的业务数据可以存入一个源数据表中，也可以存入多个源数据表中。当机构的业务数据存入多个数据表时，交易数据和财务数据可以分别存入不同的数据表。不同机构的业务数据可以存入不同的源数据库。可以理解的，部分不同机构的业务数据也可以存入同一个源数据库中。
每个源数据库都具有相应的源数据库名称。服务器中记录了多个源数据库名称以及对应的机构名称。服务器上预先创建了目标数据库，目标数据库也具有相应的目标数据库名称。目标数据库中创建了目标数据表。服务器根据机构名称可以获取各个机构对应的源数据库名称。服务器根据原数据库名称可以获取源数据库内的源数据表。服务器读取源数据表中的业务数据。服务器可以将读取到的业务数据实时同步至目标数据库中。服务器可以将多个源数据库中的业务数据同时进行实时同步操作，也可以分别对每个源数据库中的业务数据进行实时同步操作。
服务器在目标数据库中利用机构名称对应的关联方和业务数据提取相应的关联交易。具体的，服务器在目标数据库中读取业务数据，根据机构名称获取对应的交易方，若交易方为该机构名称对应的关联方，则服务器将业务数据记录为关联交易对应的业务数据。服务器可以为业务数据添加关联交易的标签，由此提取出多个关联交易。由于目标数据库中的业务数据是从多个源数据库中实时同步得到的，从而能够及时提取出关联交易，使得关联交易进行内部审批。本实施例中不再按月或按季度等对关联交易进行统计，避免了关联交易集中提交审批导致内部审批时间延长的问题。
服务器根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件。第一预设文件可以是议案文件或公告文件等。如果查询到相应的第一预设文件，服务器获取第一预设文件中的交易总额。服务器根据该关联交易的交易双方查询对应的历史关联交易，获取历史关联交易中的交易金额，根据历史关联交易的交易金额计算累积交易金额。服务器利用第一预设文件中 的交易总额减去累积交易金额得到相应的剩余额度。如果服务器未查询到该交易双方对应的历史关联交易，则第一预设文件中的交易总额即可视为前述的剩余额度。
服务器获取该关联交易的交易金额，将该交易金额与剩余额度进行比较，如果交易金额小于或等于剩余额度，则将该关联交易记录为简化审批流程的关联交易。例如，某关联交易原来的审批流程为：执行董事审批以及董事会审批。当该关联交易被记录为简化流程审批的关联交易时，所对应的审批流程为：执行董事审批。减少了董事会审批的环节，由此有效提高了审批效率。
通过及时提取关联交易，在提取出关联交易后及时进行内部审批，能够避免大量的关联交易在一个时间段内被集中上报审批而导致审批实际延长的问题。而且部分关联交易的内部审批流程进行了简化，能够有效减少审批耗时。这也促使未做审批流程简化的关联交易的审批进度能够加快。从而能够整体上提高关联交易的内部审批效率。
本实施例中，通过对多个机构名称对应的源数据库内的业务数据进行实时同步操作，可以将多个机构的业务数据实时同步至目标数据库。由此能够在目标数据库中对所有机构的业务数据及时提取出关联交易，避免了关联交易被集中提交内部审批导致审批时间延长的问题。如果关联交易具有对应的第一预设文件，且关联交易的交易金额小于第一预设文件对应的剩余额度，则本次关联交易的审批流程可以进行简化，减少关联交易的内部审批环节。由此有效提高了关联交易的内部审批效率。
应该理解的是，虽然图2的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替 地执行。
在一个实施例中，关联清单中还包括机构名称对应的监管部门；在目标数据库中利用机构名称对应的关联方和业务数据提取相应的关联交易的步骤之后，还包括：获取监管部门对应的计算规则；利用关联交易对应的业务数据和监管部门对应的计算规则在关联交易中提取重大关联交易。
关联清单中除了包括机构名称、与该机构具有关联关系的多个关联方之外，还可以包括该机构的监管部门等。一个机构可以有多个监管部门。不同的机构可以有不同的监管部门。服务器根据交易清单获取机构名称对应的监管部门，根据监管部门获取相应的计算规则。其中，计算规则中包括重大关联交易的计算规则。服务器利用重大关联交易的计算规则对关联交易对应的业务数据进行计算，得到对应的计算结果。如果计算结果表示，该关联交易属于重大关联交易，则服务器将相应的业务数据记录为重大关联交易对应的业务数据。服务器可以为业务数据添加重大关联交易的标签。由此提取出一个或多个重大关联交易。
当关联清单中的机构名称对应多个监管部门时，服务器获取每个监管部门对重大关联交易的计算规则，不同监管部门的计算规则不同，计算所需的业务数据也可以不同。服务器利用监管部门的重大关联交易的计算规则对该机构名称对应的关联交易对应的业务数据逐一进行计算，若计算结果表示该关联交易属于多个监管部门所需监管的重大关联交易，则服务器分别对重大关联交易对应监管部门进行标记。
例如，当机构名称对应的监管部门为上交所时，对应的计算规则为关联交易的交易金额(简写为AB)大于30000000，且该交易金额(AB)与集团公司最近一期经审计净资产金额(简写为AD)的比值大于5％。上述计算规则可以用如下公式来表达：AB>30000000且AB/|AD|>5％。当关联交易满足该计算规则时，服务器将该关联交易标记为向上交所上报的重大关联交易。
例如，当机构名称对应的监管部门为保监会时，对应的计算规则为关联交易的交易金额(AB)大于30000000，或者该交易金额(AB)与最近一期 经审核净资产金额(简写为IE)的比值大于1％，或者该交易金额(AB)加上与同一关联方的关联交易的累积金额(简写为IC)的和除以最近一期经审核净资产金额(IE)的比值大于5％。上述计算规则可以用如下公式来表达：AB>30000000；或者AB/IE>1％；或者(AB+IC)/IE>5％。当关联交易满足该计算规则时，服务器将该关联交易标记为向保监会上报的重大关联交易。
如果机构名称对应的监管部门包括上交所和保监会，则将该机构名称对应的关联交易对应的业务数据利用上交所的计算规则和保监会的计算规则分布进行计算。如果计算结果既满足上交所的计算规则，又满足保监会的计算规则，则服务器将该关联交易标记为向上交所上报的重大关联交易以及向保监会上报的重大关联交易。如果计算结果只满足上交所的计算规则，而不满足保监会的计算规则，表示相应的重大关联交易只需要上报至上交所，而不必上报至保监会。服务器只将该关联交易标记为向上交所上报的重大关联交易。
重大关联交易应当向对应的监管部门进行报备，以便于监管部门对其进行监管。在重大关联建议进行报备之前，同样需要进行内部审批。服务器还可以进一步识别重大关联交易是否为简化审批流程的关联交易，以便于根据简化后的审批流程对重大关联交易进行内部审批。
在其中一个实施例中，该方法还包括：获取重大关联交易对应的第二预设文件，第二预设文件包括预设的业务类型和上限额度；获取重大关联交易的业务类型以及交易金额；当业务类型为预设的业务类型且交易金额小于上限额度时，将重大关联交易记录为简化审批流程的关联交易。
服务器根据重大关联交易查询是否存在对应的第二预设文件。例如，第二预设文件可以是框架协议等。第二预设文件中包括了重大关联交易对应的预设的业务类型和上限额度等。例如，预设的业务类型可以是拆借或贷款等。服务器根据重大关联交易的交易方查询是否存在历史关联交易。如果存在历史关联交易，则服务器计算历史关联交易的累积交易金额。服务器利用该上限额度减去累积交易金额得到可用额度。如果服务器未查询到该交易双方对 应的历史关联交易，则第二预设文件中的上限额度即可视为前述的可用额度。服务器将重大关联交易的交易金额与该可用额度进行比较，若重大关联交易的交易金额小于或等于该可用额度，则服务器将该重大关联交易记录为简化审批流程的关联交易。例如，原本应当向保监会报备的某重大关联交易，在记录为简化审批流程的关联交易之后，可用豁免董事会审批和向保监会报备，只提交执行董事审批即可。由此提高了该重大关联交易的内部审批效率。
在一个实施例中，目标数据库中存储有目标数据表，目标数据表中包括与监管部门对应的监管字段；根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库的步骤包括：根据源数据名称对多个源数据库的写操作进行监听；当监听到与监管字段对应的业务数据被写入源数据库时，触发源数据向目标数据的同步操作；通过同步操作在源数据库中读取监管字段对应的业务数据；将读取到的业务数据实时写入至目标数据库中的目标数据表。
本实施例中，各个机构的业务数据可以分别存入相应的源数据库的数据表中。源数据表中可以包括业务数据的多个字段，即交易数据和财务数据的多个字段。例如，交易数据对应的字段包括交易标识、交易类型、交易金额、交易方和交易时间等。财务数据对应的字段包括审计净资产、累积金额和资本净额等。交易数据的多个字段与财务数据的多个字段可以被设置于同一个源数据表中，也可以被设置于不同的源数据表中。
目标数据库中预先创建了目标数据表。目标数据表中包括多个监管字段。监管字段可以是根据监管部门的监管要求来设定的。监管部门不同，所对应的监管字段也可以不同。可以理解的，监管部门不同，所对应的监管字段也可以是相同的。监管字段的名称可以业务数据的字段名称全部相同或部分相同。
服务器获取机构名称对应的源数据库名称。服务器调用脚本根据源数据库名称对多个源数据库的写操作进行监听。当监听到与监管字段对应的业务数据被写入源数据库时，触发该源数据库向目标数据库的同步操作。
服务器调用线程利用监管字段生成SQL语句。当源数据库向目标数据库的同步操作被触发时，服务器通过SQL语句在该源数据库的源数据表中读取相应字段的业务数据。服务器将读取到的业务数据实时写入至目标数据库的目标数据表中。由于在执行同步操作时，服务器只提取了源数据表中的相应字段写入目标数据表，而不需要对源数据表进行整表提取写入目标数据库，节省了数据读操作以及写操作的耗时，有效提高了数据同步的效率。
当多个源数据库向目标数据库的同步操作被触发时，服务器分别调用多个线程，利用SQL语句在源数据库中并发执行读取源数据表的操作。服务器将从多个源数据表中读取到的业务数据实时写入至目标数据库的目标数据表中。通过多线程的并发同步操作，进一步提高了多个源数据库向目标数据进行数据同步的效率。
为了进一步提高数据同步的效率，服务器在进行第一次同步操作时可以对监管字段对应的业务数据进行全量同步，在第二次同步操作以及后续的同步操作时，服务器可以对监管字段对应的业务数据进行增量同步。
在一个实施例中，根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库的步骤包括：根据源数据库名称实时读取多个源数据库中的源日志文件，源日志文件记录了业务数据；将源日志文件写入目标数据库；在目标数据库中利用多个源日志文件生成相应的目标日志文件；利用目标日志文件提取相应的业务数据。
本实施例中，源数据库中对业务数据的写操作和读操作会记录相应的日志文件。源数据库中记录的日志文件也可以称为源日志文件。日志文件中记录了对业务数据的读操作和写操作，包括对交易数据和财务数据的读操作和写操作等。服务器调用线程实时读取多个源数据库内的源日志文件，将读取到的源日志文件写入目标数据库。服务器在目标数据库中利用多个源日志文件生成目标日志文件。
目标数据库中预先创建了目标数据表。目标数据表中包括多个监管字段。监管字段可以是根据监管部门的监管要求来设定的。监管部门不同，所对应 的监管字段也可以不同。可以理解的，监管部门不同，所对应的监管字段也可以是相同的。监管字段的名称可以业务数据的字段名称全部相同或部分相同。
服务器对目标日志文件进行解析，得到解析后的日志文件。服务器利用监管字段的名称在解析后的日志文件中提取相应的业务数据，将提取到的业务数据对照监管字段写入目标数据表中。
由于源日志文件是实时记录的，因此源日志文件能够有效反映源数据库内的数据读写状况。根据源日志文件中记录的被写入的业务数据，可以得知源数据库中写入的业务数据。由此对多个源日志文件进行同步之后，能够得到多个源数据库中写入的业务数据。由于源日志文件通常比源数据表小，因此对源日志文件进行同步操作比对源数据表的同步操作所需的耗时要少，由此能够提高数据同步的效率。
为了进一步提高数据同步的效率，服务器在进行第一次同步操作时可以对源日志文件进行全量同步，在第二次同步操作以及后续的同步操作时，服务器可以对源日志文件进行增量同步。
如图3所示，本申请还提供了一种基于关联交易数据处理的优化装置。在一个实施例中，该装置包括：通信模块302、同步模块304、提取模块306和简化模块308，每个模块可以通过软件、硬件或其组合来实现。其中：
通信模块302，用于接收多个终端上传的关联清单，关联清单中关联清单中包括了机构的机构名称及与机构对应的关联方。
同步模块304，用于根据机构名称获取与机构对应的源数据库名称，根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库。
提取模块306，用于在目标数据库中利用机构名称对应的关联方和业务数据提取相应的关联交易。
简化模块308，用于根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到第一预设文件时，计算第一预设文件对应的剩余额度；获取关联交易对应的交易金额，若交易金额小于或等于剩余额度， 则将关联交易记录为简化审批流程的关联交易。
在一个实施例中，关联清单中还包括机构名称对应的监管部门；提取模块306还用于获取监管部门对应的计算规则；利用关联交易对应的业务数据和监管部门对应的计算规则在关联交易中提取重大关联交易。
在一个实施例中，简化模块308还用于获取重大关联交易对应的第二预设文件，第二预设文件包括预设的业务类型和上限额度；获取重大关联交易的业务类型以及交易金额；当业务类型为预设的业务类型且交易金额小于上限额度时，将重大关联交易记录为简化审批流程的关联交易。
在一个实施例中，目标数据库中存储有目标数据表，目标数据表中包括与监管部门对应的监管字段；同步模块304还用于根据源数据名称对多个源数据库的写操作进行监听；当监听到与监管字段对应的业务数据被写入源数据库时，触发源数据向目标数据的同步操作；通过同步操作在源数据库中读取监管字段对应的业务数据；将读取到的业务数据实时写入至目标数据库中的目标数据表。
在一个实施例中，同步模块304还用于根据源数据库名称实时读取多个源数据库中的源日志文件，源日志文件记录了业务数据；将源日志文件写入目标数据库；在目标数据库中利用多个源日志文件生成相应的目标日志文件；利用目标日志文件提取相应的业务数据。
关于基于关联交易数据处理的优化装置的具体限定可以参见上文中对于基于关联交易数据处理的优化方法的限定，在此不再赘述。上述基于关联交易数据处理的优化装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，提供了一种计算机设备，例如该计算机设备可以是服务器。如图4所示，该计算机设备包括通过系统总线连接的处理器、存储器和网络接口。其中，该计算机设备的处理器用于提供计算和控制能力。该计 算机设备的存储器包括非易失性存储介质、内存储器。该计算机设备的非易失性存储介质存储有操作系统和和计算机可读指令。非易失性存储介质可以是非易失性计算机可读存储介质。该计算机设备的内存储器为非易失性存储介质中的操作系统和计算机可读指令的运行提供环境。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机可读指令被处理器执行时以实现一种基于关联交易数据处理的优化方法。该计算机设备可以是独立服务器，也可以是集群服务器。本领域技术人员可以理解，图4中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，提供了一种计算机设备，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行上述各个方法实施例中的步骤。
在一个实施例中，提供了一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行上述各个方法实施例中的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机可读指令来指令相关的硬件来完成，所述的计算机可读指令可存储于一非易失性计算机可读取存储介质中，该计算机可读指令在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本 领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (20)

  1. 一种基于关联交易数据处理的优化方法，包括：
    接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
    根据所述机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；
    在所述目标数据库中利用所述机构对应的关联方和所述业务数据提取相应的关联交易；
    根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；及
    获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
  2. 根据权利要求1所述的方法，其特征在于，所述关联清单中还包括机构名称对应的监管部门；在所述目标数据库中利用所述机构名称对应的关联方和所述业务数据提取相应的关联交易的步骤之后，还包括：
    获取所述监管部门对应的计算规则；及
    利用所述关联交易对应的业务数据和所述监管部门对应的计算规则在所述关联交易中提取重大关联交易。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    获取所述重大关联交易对应的第二预设文件，所述第二预设文件包括预设的业务类型和上限额度；
    获取所述重大关联交易的业务类型以及交易金额；及
    当所述业务类型为所述预设的业务类型且所述交易金额小于所述上限额度时，将所述重大关联交易记录为简化审批流程的关联交易。
  4. 根据权利要求1所述的方法，其特征在于，所述目标数据库中存储有目标数据表，所述目标数据表中包括与监管部门对应的监管字段；所述根据源数据库名称将源数据库的业务数据实时同步至目标数据库的步骤包括：
    根据源数据名称对多个源数据库的写操作进行监听；
    当监听到与所述监管字段对应的业务数据被写入源数据库时，触发源数据向目标数据的同步操作；
    通过所述同步操作在源数据库中读取所述监管字段对应的业务数据；及
    将读取到的业务数据实时写入至目标数据库中的目标数据表。
  5. 根据权利要求1所述的方法，其特征在于，所述根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库的步骤包括：
    根据源数据库名称实时读取多个源数据库中的源日志文件，所述源日志文件记录了业务数据；
    将所述源日志文件写入目标数据库；在所述目标数据库中利用多个源日志文件生成相应的目标日志文件；及
    利用所述目标日志文件提取相应的业务数据。
  6. 一种基于关联交易数据处理的优化装置，包括：
    通信模块，用于接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
    同步模块，用于根据所述机构名称获取与机构对应的源数据库名称，根据多个源数据库名称将多个源数据库的业务数据实时同步至目标数据库；
    提取模块，用于在所述目标数据库中利用所述机构名称对应的关联方和所述业务数据提取相应的关联交易；及
    简化模块，用于根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
  7. 根据权利要求6所述的装置，其特征在于，所述目标数据库中存储有目标数据表，所述目标数据表中包括与监管部门对应的监管字段；所述同步模块还用于根据源数据名称对多个源数据库的写操作进行监听；当监听到与所述监管字段对应的业务数据被写入源数据库时，触发源数据向目标数据的 同步操作；通过所述同步操作在源数据库中读取所述监管字段对应的业务数据；及将读取到的业务数据实时写入至目标数据库中的目标数据表。
  8. 根据权利要求6所述的装置，其特征在于，所述同步模块还用于根据源数据库名称实时读取多个源数据库中的源日志文件，所述源日志文件记录了业务数据；将所述源日志文件写入目标数据库；在所述目标数据库中利用多个源日志文件生成相应的目标日志文件；及利用所述目标日志文件提取相应的业务数据。
  9. 根据权利要求6所述的装置，其特征在于，所述关联清单中还包括机构名称对应的监管部门；所述提取模块还用于获取监管部门对应的计算规则；及利用所述关联交易对应的业务数据和所述监管部门对应的计算规则在所述关联交易中提取重大关联交易。
  10. 根据权利要求9所述的装置，其特征在于，所述简化模块还用于获取所述重大关联交易对应的第二预设文件，所述第二预设文件包括预设的业务类型和上限额度；获取所述重大关联交易的业务类型以及交易金额；当所述业务类型为预设的业务类型且交易金额小于上限额度时，将所述重大关联交易记录为简化审批流程的关联交易。
  11. 一种计算机设备，包括存储器和一个或多个处理器，所述存储器中储存有计算机可读指令，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器执行以下步骤：
    接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
    根据所述机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；
    在所述目标数据库中利用所述机构对应的关联方和所述业务数据提取相应的关联交易；
    根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；及
    获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
  12. 根据权利要求11所述的计算机设备，其特征在于，所述关联清单中还包括机构名称对应的监管部门；所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器还执行以下步骤：
    获取所述监管部门对应的计算规则；及
    利用所述关联交易对应的业务数据和所述监管部门对应的计算规则在所述关联交易中提取重大关联交易。
  13. 根据权利要求12所述的计算机设备，其特征在于，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器还执行以下步骤：
    获取所述重大关联交易对应的第二预设文件，所述第二预设文件包括预设的业务类型和上限额度；
    获取所述重大关联交易的业务类型以及交易金额；及
    当所述业务类型为所述预设的业务类型且所述交易金额小于所述上限额度时，将所述重大关联交易记录为简化审批流程的关联交易。
  14. 根据权利要求11所述的计算机设备，其特征在于，所述目标数据库中存储有目标数据表，所述目标数据表中包括与监管部门对应的监管字段；所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器还执行以下步骤：
    根据源数据名称对多个源数据库的写操作进行监听；
    当监听到与所述监管字段对应的业务数据被写入源数据库时，触发源数据向目标数据的同步操作；
    通过所述同步操作在源数据库中读取所述监管字段对应的业务数据；及
    将读取到的业务数据实时写入至目标数据库中的目标数据表。
  15. 根据权利要求11所述的计算机设备，其特征在于，所述计算机可读指令被所述处理器执行时，使得所述一个或多个处理器还执行以下步骤：
    根据源数据库名称实时读取多个源数据库中的源日志文件，所述源日志 文件记录了业务数据；
    将所述源日志文件写入目标数据库；在所述目标数据库中利用多个源日志文件生成相应的目标日志文件；及
    利用所述目标日志文件提取相应的业务数据。
  16. 一个或多个存储有计算机可读指令的非易失性计算机可读存储介质，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器执行以下步骤：
    接收多个终端上传的关联清单，所述关联清单中包括了机构的机构名称及与所述机构对应的关联方；
    根据所述机构名称获取与机构对应的源数据库名称，根据源数据库名称将源数据库的业务数据实时同步至目标数据库；
    在所述目标数据库中利用所述机构对应的关联方和所述业务数据提取相应的关联交易；
    根据提取出的关联交易的交易双方查询是否存在对应的第一预设文件，当查询到所述第一预设文件时，计算所述第一预设文件对应的剩余额度；及
    获取所述关联交易对应的交易金额，若所述交易金额小于或等于所述剩余额度，则将所述关联交易记录为简化审批流程的关联交易。
  17. 根据权利要求16所述的存储介质，其特征在于，所述关联清单中还包括机构名称对应的监管部门；计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    获取所述监管部门对应的计算规则；及
    利用所述关联交易对应的业务数据和所述监管部门对应的计算规则在所述关联交易中提取重大关联交易。
  18. 根据权利要求17所述的存储介质，其特征在于，所述关联清单中还包括机构名称对应的监管部门；计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    获取所述重大关联交易对应的第二预设文件，所述第二预设文件包括预 设的业务类型和上限额度；
    获取所述重大关联交易的业务类型以及交易金额；及
    当所述业务类型为所述预设的业务类型且所述交易金额小于所述上限额度时，将所述重大关联交易记录为简化审批流程的关联交易。
  19. 根据权利要求16所述的存储介质，其特征在于，所述关联清单中还包括机构名称对应的监管部门；所述目标数据库中存储有目标数据表，所述目标数据表中包括与监管部门对应的监管字段；计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    根据源数据名称对多个源数据库的写操作进行监听；
    当监听到与所述监管字段对应的业务数据被写入源数据库时，触发源数据向目标数据的同步操作；
    通过所述同步操作在源数据库中读取所述监管字段对应的业务数据；及
    将读取到的业务数据实时写入至目标数据库中的目标数据表。
  20. 根据权利要求16所述的存储介质，其特征在于，计算机可读指令被一个或多个处理器执行时，使得一个或多个处理器还执行以下步骤：
    根据源数据库名称实时读取多个源数据库中的源日志文件，所述源日志文件记录了业务数据；
    将所述源日志文件写入目标数据库；在所述目标数据库中利用多个源日志文件生成相应的目标日志文件；及
    利用所述目标日志文件提取相应的业务数据。
PCT/CN2018/086272 2017-05-12 2018-05-10 基于关联交易数据处理的优化方法、装置和计算机设备 WO2019056769A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PH12019501066A PH12019501066A1 (en) 2017-05-12 2019-05-14 Method and device for in-vehicle payment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710874957.2A CN107798417B (zh) 2017-09-25 2017-09-25 基于关联交易数据处理的优化方法、装置和计算机设备
CN201710874957.2 2017-09-25

Publications (1)

Publication Number Publication Date
WO2019056769A1 true WO2019056769A1 (zh) 2019-03-28

Family

ID=61532327

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/086272 WO2019056769A1 (zh) 2017-05-12 2018-05-10 基于关联交易数据处理的优化方法、装置和计算机设备

Country Status (2)

Country Link
CN (1) CN107798417B (zh)
WO (1) WO2019056769A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107798417B (zh) * 2017-09-25 2019-06-14 平安科技（深圳）有限公司 基于关联交易数据处理的优化方法、装置和计算机设备
CN112990871A (zh) * 2021-03-16 2021-06-18 金蝶软件（中国）有限公司 一种单据处理方法及相关设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101976419A (zh) * 2010-10-19 2011-02-16 中国工商银行股份有限公司 交易数据的风险监控处理方法和系统
CN103020782A (zh) * 2012-12-25 2013-04-03 远光软件股份有限公司 内部关联交易业务的自动识别和提取方法及系统
US20160283584A1 (en) * 2015-03-26 2016-09-29 Ca, Inc. Grouping of Database Objects
CN106980636A (zh) * 2016-07-22 2017-07-25 平安科技（深圳）有限公司 保单数据处理方法和装置
CN107798417A (zh) * 2017-09-25 2018-03-13 平安科技（深圳）有限公司 基于关联交易数据处理的优化方法、装置和计算机设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006251957A (ja) * 2005-03-09 2006-09-21 Oki Electric Ind Co Ltd 事務リスクモニタリングシステム及び管理サーバ
CN103530767A (zh) * 2013-09-10 2014-01-22 潘之凯 一种用于计量量收费系统的信息安全方法
CN104103009A (zh) * 2014-05-16 2014-10-15 张岩 一种基于信用报告的数据库的构建方法
CN105321044A (zh) * 2015-11-04 2016-02-10 国家计算机网络与信息安全管理中心 项目审批系统
CN106557592A (zh) * 2016-12-02 2017-04-05 中铁程科技有限责任公司 数据同步方法、装置及服务器集群
CN106970934A (zh) * 2017-01-16 2017-07-21 平安银行股份有限公司 交易处理控制方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101976419A (zh) * 2010-10-19 2011-02-16 中国工商银行股份有限公司 交易数据的风险监控处理方法和系统
CN103020782A (zh) * 2012-12-25 2013-04-03 远光软件股份有限公司 内部关联交易业务的自动识别和提取方法及系统
US20160283584A1 (en) * 2015-03-26 2016-09-29 Ca, Inc. Grouping of Database Objects
CN106980636A (zh) * 2016-07-22 2017-07-25 平安科技（深圳）有限公司 保单数据处理方法和装置
CN107798417A (zh) * 2017-09-25 2018-03-13 平安科技（深圳）有限公司 基于关联交易数据处理的优化方法、装置和计算机设备

Also Published As

Publication number Publication date
CN107798417A (zh) 2018-03-13
CN107798417B (zh) 2019-06-14

Similar Documents

Publication Publication Date Title
CN108536761B (zh) 报表数据查询方法及服务器
WO2019056789A1 (zh) 关联交易的识别方法、装置、计算机设备和存储介质
US10715331B2 (en) Method and system for providing validated, auditable, and immutable inputs to a smart contract
WO2019056770A1 (zh) 基于关联交易的数据处理方法、装置和计算机设备
CN110489313B (zh) 基于区块链的操作日志记录方法、装置及存储介质
CN106649828B (zh) 一种数据查询方法及系统
US20210287298A1 (en) Actuarial processing method and device
WO2019134340A1 (zh) 薪资计算方法、应用服务器及计算机可读存储介质
WO2020000720A1 (zh) 服务器、报文处理方法、程序和计算机可读存储介质
CN105791178B (zh) 报文组装方法及装置
KR102529038B1 (ko) 리소스 관리 및 제어 방법 및 장치, 디바이스 및 저장매체
WO2019041748A1 (zh) 一种保单数据处理方法、装置、电子设备及介质
CN104657808A (zh) 能够实现企业资金数据实时查询和管理的系统及方法
WO2019056769A1 (zh) 基于关联交易数据处理的优化方法、装置和计算机设备
WO2019214014A1 (zh) 网销产品管理方法、装置、终端设备及存储介质
CN109299913A (zh) 员工薪资方案生成方法及装置
CN108182204A (zh) 基于房产交易多维度数据的数据查询的处理方法及装置
CN110008180A (zh) 财务数据记录方法、装置、计算机设备和存储介质
US20170163565A1 (en) System for analysis of resource usage and availability
CN111275436A (zh) 一种处理信息的方法及终端
CN112148762A (zh) 一种实时数据流的统计方法和装置
CN110858199A (zh) 一种单据数据分布式计算的方法和装置
US20140188706A1 (en) Correctable pre-payment for database services
JP2020514907A (ja) プロセス定義およびプロセス実行トラッキングのためのユーザインターフェイスおよびランタイム環境
CN110727677B (zh) 数据仓库内表格的血缘关系追溯的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18858022

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 22/09/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18858022

Country of ref document: EP

Kind code of ref document: A1