WO2020077836A1 - 业务数据管理方法、装置、设备及计算机可读存储介质 - Google Patents

业务数据管理方法、装置、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2020077836A1
WO2020077836A1 PCT/CN2018/123363 CN2018123363W WO2020077836A1 WO 2020077836 A1 WO2020077836 A1 WO 2020077836A1 CN 2018123363 W CN2018123363 W CN 2018123363W WO 2020077836 A1 WO2020077836 A1 WO 2020077836A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
business data
business
abnormal
service
Prior art date
Application number
PCT/CN2018/123363
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 WO2020077836A1 publication Critical patent/WO2020077836A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • This application mainly relates to the field of financial technology, specifically, to a business data management method, device, equipment, and computer-readable storage medium.
  • the asset package includes multiple pieces of business data, and each piece of business data corresponds to arrears information of a debtor; financial institutions will Asset packages obtained from third-party institutions are transmitted to the system of financial institutions for management in the form of business data.
  • financial institutions have imperfect management of business data and do not distinguish the quality of business data. They may introduce business data with greater risks or lack of information to financial institutions, which may cause risks to financial institutions.
  • manual identification and screening and return operations are required, and the degree of automation of management is low, which increases labor costs and low operation efficiency.
  • the main purpose of this application is to provide a business data management method, device, equipment and computer-readable storage medium, aiming to solve the imperfect management of business data in the prior art, which is likely to cause risks to financial institutions and the degree of automation of management Low problem.
  • the present application provides a business data management method, which is applied to a business data management system.
  • the business data management system includes a transaction channel subsystem, an accounting subsystem, and an asset management subsystem.
  • the business data management method includes The following steps:
  • An abnormal data packet is generated from each of the abnormal business data, and when a return request for the abnormal data packet is received, a return operation is performed on the abnormal data packet.
  • the present application also proposes a business data management device, the business data management device includes:
  • the verification module is used to read each business data corresponding to the import request when receiving the import request, and verify each business data to generate normal business data with successful verification and failed verification Abnormal business data;
  • a splitting module used for importing each of the normal business data, splitting each of the normal business data according to the data type, correspondingly generating business sub-data, and classifying and storing each of the business sub-data;
  • a return and exchange model is used to generate abnormal data packets for each of the abnormal service data, and upon receiving a return and exchange request for the abnormal data packets, perform a return and exchange operation on the abnormal data packets.
  • the present application also proposes a business data management device.
  • the business data management device includes: a memory, a processor, a communication bus, and business data management readable instructions stored on the memory;
  • the communication bus is used to implement connection communication between the processor and the memory
  • the processor is used to execute the business data management readable instructions to implement the following steps:
  • An abnormal data packet is generated from each of the abnormal business data, and when a return request for the abnormal data packet is received, a return operation is performed on the abnormal data packet.
  • the present application also provides a computer-readable storage medium that stores one or more programs, and the one or more programs may be used by one or more processors Implementation for:
  • An abnormal data packet is generated from each of the abnormal business data, and when a return request for the abnormal data packet is received, a return operation is performed on the abnormal data packet.
  • the business data before receiving the business data import request, the business data is verified before the business data is imported, and the business data is divided into normal business data with successful verification and failed verification Abnormal business data; where normal business data is business data whose quality meets the needs of financial institutions, and abnormal business data is business data whose quality cannot meet the needs of financial institutions; import normal business data, and import each normal business data Split into business sub-data according to the data type, and classify and store each business sub-data to ensure the quality of the imported business data and avoid the risk of financial institutions; for each abnormal business data, an abnormal data package is generated and received When it comes to the return request for abnormal data packets, the abnormal data packets are returned and exchanged; each abnormal business data is identified by verification, and the overall return is performed in the form of abnormal data packets, avoiding manual identification and screening, Increased the degree of automated management of business data .
  • FIG. 1 is a schematic flowchart of a first embodiment of a business data management method of this application
  • FIG. 2 is a schematic diagram of functional modules of the first embodiment of the business data management device of the present application.
  • FIG. 3 is a schematic diagram of a device structure of a hardware operating environment involved in the method of an embodiment of the present application.
  • This application provides a business data management method.
  • FIG. 1 is a schematic flowchart of a first embodiment of a business data management method of this application.
  • the business data management method includes:
  • Step S10 when receiving the import request, read each business data corresponding to the import request, and verify each business data to generate normal business data with successful verification and abnormal business data with failed verification ;
  • the business data management method of this application is applied to a server in a financial institution, and is suitable for managing business data derived from an asset package through the server; where the asset package is the information of arrears purchased by a financial institution from a third-party institution, each owed
  • the payment information exists in the asset package in the form of an EXCEL file.
  • One line in the EXCEL file corresponds to one piece of arrearage information; each piece of arrearage information includes at least the name of the owed party, ID card number, contact phone number, type of arrearage, and arrearage Data such as the amount and duration of arrears characterize the information that each arrears have.
  • the asset package includes a variety of multiple pieces of business data, and each piece of business data corresponds to a piece of arrears.
  • the financial institution's server is connected with an information display entry device.
  • the display interface of the display entry device is provided with a virtual button for importing business data; when there is a demand for importing business data in the asset package, the virtual button is triggered. Use the triggered operation of the virtual button as an import request for business data.
  • the steps for verifying each business data include:
  • Step S11 judging whether the required items in the service data are null values one by one, and if the required items in the service data are null values, it is determined that the verification of the service data fails;
  • each business data is essentially the various pieces of arrears information in the form of asset package EXCEL, and each piece of arrears information includes multiple data; when verifying, first verify the requested import Whether the various business data exist in the form of EXCEL files. If it exists in the form of an EXCEL file, it is further checked whether the required items in each business data are empty. If it does not exist in the form of an EXCEL file, it is determined that the asset package is unqualified and no subsequent business data verification is performed. The required items are necessary information for collection of arrears, such as the contact number of the owed party and the amount owed.
  • any mandatory item in the business data is empty, it means that the lack of information necessary to collect the arrears may cause the financial institution to fail to collect the arrears normally, and the missing required item Of the business data is judged to have failed verification.
  • it can also verify whether the format of each business data meets the requirements, that is, the format of the business data corresponds to the format of the corresponding type of the arrearage information, such as the number corresponding to the telephone number or date is digital data; pass this required item
  • business data format verification to ensure the integrity of information and format accuracy of imported business data.
  • Step S12 if the required item in the service data is not null, it is detected whether the service data has information existing in a preset blacklist;
  • Step S13 if the service data has information existing in the blacklist, it is determined that the service data verification fails, and if the service data does not have information existing in the blacklist, the service data is determined The verification is successful.
  • the business data When it is judged by comparison that the business data has information that exists in the blacklist, it means that the business data has historical risk information. If it is imported, it may cause risks to financial institutions; thus, the business data is judged to have failed verification, It cannot import the business data. When it is judged that the business data does not have information existing in the blacklist, it means that the business data does not have historical risk information, and it is judged as a verification failure to facilitate the import operation.
  • the successful identifier is assigned, and the business data that fails the verification is assigned a failed identifier; after all the business data corresponding to the import request are verified, the one with the successful identifier All business data form a collection to generate normal business data; and all business data with a failure identifier are also collected to generate abnormal business data; to import normal business data and return abnormal business data.
  • Step S20 importing each of the normal business data, splitting each of the normal business data according to the data type, correspondingly generating business sub-data, and classifying and storing each of the business sub-data;
  • normal business data belongs to safe and reliable business data, it needs to be imported into financial institutions.
  • the business data exists in the form of rows in the EXCEL of the asset package, and the normal business data correspondingly exists in the form of rows in the EXCEL file.
  • the units of behavior in the EXCEL file are read each time. Take a line of content in the EXCEL file for import until all lines in the EXCEL file are imported.
  • each normal business data is assigned as an identifier number to form the difference between each normal business data, such as the first normal business data number 0001, the second Business data number 0002 etc.
  • each normal business data includes various types of arrears such as the name of the owed party, ID number, contact phone number, type of arrears, amount of arrears, etc.
  • each normal business data is split according to the data type, and the same type of debtor information is collected together to generate business subdata and store it.
  • the ID number of the owed party in each normal business data is split and collected together to form the business sub-data of the identity information.
  • Various types of business subdata are also stored in the form of EXCEL tables, and an EXCEL table corresponds to a type of debtor information, that is, a type of business subdata.
  • Each EXCEL table formed by splitting and collecting contains various The same information for the owed party.
  • add a number that characterizes the business data from which each split information is derived, such as the above number 0001 for the source For the ID number in the normal business data, add the number 0001 to the ID number to characterize its source, and distinguish it from other ID numbers in the identity information table.
  • Step S30 Generate an abnormal data packet from each of the abnormal service data, and perform a return operation on the abnormal data packet when receiving a return request for the abnormal data packet.
  • the abnormal business data is data with incomplete information or risks, if such abnormal business data is imported into a financial institution, it is not possible to collect debts or bring risks to the financial institution.
  • Business data is returned or exchanged.
  • an abnormal data packet is generated from each abnormal business data, and a virtual button for return is set on the display interface; when a financial institution has a demand for the return of the abnormal data packet, the virtual button for return is triggered, and the triggered operation is used as abnormal data
  • the return and exchange request of the packet when the return and exchange request is received, the abnormal data packet is returned and exchanged.
  • the return includes two types of refund operations for abnormal data packets and replacement of abnormal data packets with new data packets. Before returning, you need to determine the specific type of return; specifically, after receiving a return request for the abnormal data packet At this time, the steps to return the abnormal data packet include:
  • Step S31 when receiving a return request for the abnormal data packet, read the return identifier carried in the return request, and determine the return type of the return request according to the return identifier;
  • the staff of the financial institution first selects the required exchange type, and adds the selected exchange type to the exchange request in the form of a exchange identifier.
  • the server receives the return request for the abnormal data packet, it reads the return identifier carried in the return request, and the return identifier determines the return type of the return request, that is, the return type for the abnormal service data.
  • Step S32 when the return type is the first type, the refund amount is determined according to the transaction amount corresponding to each of the business data, the number of each of the business data and the number of each of the abnormal business data, and Performing a return operation on the asset package to be returned according to the refund amount;
  • the return type of the refund is regarded as the first type.
  • the return type is determined to be the first type based on the return identifier in the return request, that is, the refund is made for abnormal business data
  • the corresponding data of the business data is read.
  • Transaction amount the amount of each business data and the amount of abnormal business data. Because the business data is the arrearage information that exists in the asset package, and the asset package is purchased by the amount institution from a third-party institution, the financial cost of purchasing the asset package is the amount spent on each business data, and this amount is used as the The transaction amount corresponding to the business data.
  • the amount of arrearage information included in the asset package is the number of business data, that is, the number of rows of business data included in the EXCEL table; and the number of abnormal business data is the number of business data that failed verification in the business data.
  • the refund amount is related to the ratio of the amount of abnormal business data to the amount of business data, and can be calculated and generated by a preset formula; specifically, according to the transaction amount corresponding to each business data, the amount of each business data, and the abnormal business data
  • the number of steps to determine the refund amount includes:
  • the preset formula is:
  • y represents the refund amount
  • m represents the transaction amount
  • n1 represents the number of each abnormal business data
  • n2 represents the number of each business data.
  • the read transaction amount, the amount of each business data, and the amount of abnormal business data are respectively input into a preset formula, replacing m, n1, and n2, and the refund amount is calculated.
  • the abnormal data package can be returned and exchanged, and the abnormal business data in the abnormal data package can be returned to the source of the business data, and the refund amount returned by the source can be received to complete the abnormal data.
  • Step S33 When the return type is the second type, the abnormal data packet is transmitted to the source of the service data, and new service data returned by the source is received.
  • the abnormal data packet is replaced with the return type of the new data packet as the second type.
  • the abnormal service data is replaced with other new service data
  • the amount of abnormal business data in the abnormal data package is the amount of business data that needs to be returned, and the abnormal business data therein is the business data itself that needs to be returned.
  • the abnormal data packet is transmitted to the source of the business data as a whole, that is, the abnormal business data is returned to the source, and the new business data transmitted by the source is received; the total arrearage and The total amount of arrears represented in the abnormal data package is the same, so as to perform equivalent replacement and complete the return and exchange of abnormal business data in the abnormal data package.
  • the business data before receiving the business data import request, the business data is verified before the business data is imported, and the business data is divided into normal business data with successful verification and failed verification Abnormal business data; where normal business data is business data whose quality meets the needs of financial institutions, and abnormal business data is business data whose quality cannot meet the needs of financial institutions; import normal business data, and import each normal business data Split into business sub-data according to the data type, and classify and store each business sub-data to ensure the quality of the imported business data and avoid the risk of financial institutions; for each abnormal business data, an abnormal data package is generated and received When it comes to the return request for abnormal data packets, the abnormal data packets are returned and exchanged; each abnormal business data is identified by verification, and the overall return is performed in the form of abnormal data packets, avoiding manual identification and screening, Increased the degree of automated management of business data
  • the step of classifying and storing each of the business sub-data includes:
  • Step S40 when receiving a query request for the service data, read the query identifier of the query request, and determine each service data to be queried in the service sub-data according to the query identifier;
  • a query input box and a query virtual button are set on the display interface; the requester who has the query requirement inputs the information to be queried into the input box as keywords, and clicks the query virtual button to trigger the query request.
  • the keyword sent together with the query request is read, and the keyword is used as the query identifier.
  • the keyword can be an ID number.
  • the number corresponding to the ID number After receiving the ID number as the query identifier, query the number corresponding to the ID number; the number can represent the normal business data from which the ID number originates.
  • the other information split in the data carries the number; then all the information carrying the number can be queried by the number.
  • This numbered information is the information derived from the normal business data after the split, which is the demand side.
  • the information to be queried is determined as each to-be-queried business data in the business sub-data.
  • Step S50 Transmit each of the service data to be queried to a preset template, generate query information, and output and display the query information.
  • a preset template is preset; the preset template is a visual display template, and different locations display different Data; for example, the upper left corner of the template is used to display the name data of the owed party, and the upper right corner is used to display the ID number of the owed party. Transmit the business data obtained by the query to the preset template, and replace the content of the template.
  • the replaced preset template is the query information; the query information is output and displayed so that the query requester can view it.
  • the step of classifying and storing each of the business sub-data includes:
  • Step S60 when receiving the update request, read the update identifier carried in the update request;
  • the arrears party needs to repay the arrearage amount in the corresponding arrearage information.
  • the owed party repays the amount owed
  • the owed party's corresponding arrearage information in the arrearage information changes, that is, the information in the normal business data changes and needs to be updated.
  • the financial institution ’s server is in communication with an accounting system for calculating the amount of arrears, and the accounting system calculates the amount of the arrears repaid by the arrears; after the completion of the accounting, it sends updates to the server to normal business data Update request.
  • the update identifier When receiving the update request, read the update identifier carried in the update request, the update identifier is actually the number carried in the calculated amount of arrears, and represents the normal business from which the calculated amount of arrears originates Data, so as to determine the normal service data to be updated according to the update identifier.
  • Step S70 Determine the service sub-data to be updated in the service sub-data according to the update identifier, and update the normal service data corresponding to the service sub-data to be updated to target service data.
  • the service sub-data obtained by splitting the normal service data also carry the number;
  • the update identifier is compared with the number carried by each service sub-data to determine the number consistent with the update identifier.
  • the service sub-data with the consistent number is the service sub-data to be updated in each service sub-data to be updated.
  • the business sub-data to be updated is split from the normal business data that has been verified successfully, and the normal business data from which the business sub-data to be updated is derived is updated to the target business data; each sub-data to be updated is updated to form Target business data.
  • the content of the update is determined by the amount owed by the owed party.
  • the principal in the updated business subdata is to be updated; and when the interest in the owed amount is repaid , The interest in the update business sub-data is to be updated; and when the handling fee in the amount of arrears is paid, the handling fee in the update business sub-data is to be updated; at the same time, the repayment time of the owed party is updated to characterize The latest repayment time; after each sub-data to be updated is updated, all business sub-data with the same number as the business sub-data to be updated will generate target business data to complete the update of normal business data.
  • this embodiment is also provided with a reduction and exemption mechanism, which is to reduce the amount owed by the owed party when the owed party repays the amount owed to a certain extent, that is, preset the conditions for reduction and exemption, in order to encourage the owed Party's repayment.
  • a reduction and exemption mechanism which is to reduce the amount owed by the owed party when the owed party repays the amount owed to a certain extent, that is, preset the conditions for reduction and exemption, in order to encourage the owed Party's repayment.
  • the step of updating the normal service data corresponding to the service sub-data to be updated to the target service data includes:
  • Step S80 Compare the normal business data with the target business data to generate a comparison result, and compare the comparison result with a preset relief condition to determine whether the comparison result meets the preset relief condition;
  • the amount owed in the target business data is reduced relative to the amount owed in the normal business data; where the amount owed in the target business data
  • the remaining amount after the repayment of the owed amount, and the amount owed in the normal business data is the entire amount of the initial owed amount of the debtor; subtract the amount owed between the two, and use the result of the subtraction and the normal.
  • the amounts owed in the business data are compared, and the result of the ratio obtained is the ratio of the amount owed by the owed party.
  • the preset reduction and exemption conditions are: when the amount of arrears reached reaches 90% of the arrears, the remaining 10% can be fully reduced, or partially reduced, or extended the repayment time; and normal business data and target business data
  • the comparison result of the comparison is 80%. Compared with the preset exemption conditions, it can be seen that the preset exemption conditions have not been met and the exemption cannot be made.
  • Step S90 If the comparison result meets the preset reduction and exemption condition, output prompt information to the business party corresponding to the target business data.
  • the amount owed by the owed party can be reduced or exempted; thus, a prompt message is output to the business party corresponding to the target business data.
  • the business party corresponding to the target business data is actually the owed party corresponding to the target business data; output reminder information to the owed party to inform that its remaining arrears amount meets the preset reduction and exemption conditions, and the reduction can be carried out;
  • the business data corresponds to the repayment of the owed party, and speeds up the collection of the amount owed in the target business data.
  • the present application provides a business data management device.
  • the business data management device includes:
  • the verification module 10 is configured to read each business data corresponding to the import request when receiving the import request, and verify each business data to generate normal business data with successful verification and verification failure Abnormal business data;
  • the splitting module 20 is configured to import each of the normal business data, split the normal business data according to the data type, generate business sub-data corresponding to the classification, and store the business sub-data in categories;
  • the return model 30 is used to generate abnormal data packets for each of the abnormal service data, and when receiving a return request for the abnormal data packets, perform a return operation on the abnormal data packets.
  • the verification module 10 before receiving the business data import request, before the business data is imported, the verification module 10 first verifies the business data, and divides the business data into normal business data and a successful verification. Failed to verify abnormal business data; where normal business data is business data with quality that meets the needs of financial institutions, and abnormal business data is business data with quality that does not meet the needs of financial institutions; split module 20 imports each normal business data, And split the imported normal business data into business sub-data according to the data type, and classify and store each business sub-data to ensure the quality of the imported business data and avoid the risk of financial institutions; and for each abnormal business data An abnormal data packet is generated, and the return model 30 performs a return operation on the abnormal data packet when receiving a return request for the abnormal data packet; it identifies each abnormal business data by means of verification and takes the form of an abnormal data packet Carry out an overall return, avoiding manual identification and screening, High degree of automated management of business data.
  • each virtual function module of the above-mentioned business data management device is stored in the memory 1005 of the business data management device shown in FIG. 3, and when the processor 1001 executes business data management readable instructions, the modules of the embodiments shown in FIG. 2 are implemented.
  • non-volatile computer-readable storage medium may be a read-only memory, a magnetic disk, or an optical disk.
  • FIG. 3 is a schematic structural diagram of a device in a hardware operating environment involved in a method according to an embodiment of the present application.
  • the business data management device in the embodiment of the present application may be a PC (personal computer) or a terminal device such as a smart phone, tablet computer, e-book reader, and portable computer.
  • the service data management device may include: a processor 1001, such as a CPU (Central Processing Unit, central processing unit), a memory 1005, and a communication bus 1002.
  • the communication bus 1002 is used to implement connection communication between the processor 1001 and the memory 1005.
  • the memory 1005 may be a high-speed RAM (random access memory) or a stable memory (non-volatile memory), such as a disk memory.
  • the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
  • the service data management device may further include a user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi (Wireless Fidelity, wireless broadband) module, and so on.
  • the user interface may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface may also include a standard wired interface and a wireless interface.
  • the network interface may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).
  • the structure of the business data management device shown in FIG. 3 does not constitute a limitation on the business data management device, and may include more or fewer components than the illustration, or a combination of certain components, or different Parts layout.
  • the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, and business data management readable instructions.
  • the operating system is a program that manages and controls the hardware and software resources of the business data management device, and supports the operation of business data management readable instructions and other software and / or programs.
  • the network communication module is used to implement communication between various components within the memory 1005 and other hardware and software in the service data management device.
  • the processor 1001 is configured to execute business data management readable instructions stored in the memory 1005 to implement the steps in the above embodiments of the business data management method.
  • the present application provides a computer-readable storage medium that stores one or more programs, and the one or more programs may also be executed by one or more processors to implement the foregoing The steps in each embodiment of the business data management method.
  • the methods in the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware, but in many cases the former is better Implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or a part that contributes to the existing technology, and the computer software product is stored in a computer-readable storage medium (such as The ROM / RAM, magnetic disk, and optical disk include several instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the embodiments of the present application.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Technology Law (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请公开一种业务数据管理方法、装置、设备及计算机可读存储介质,所述方法包括:当接收到导入请求时,读取与导入请求对应的各业务数据,并对各业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;对各正常业务数据进行导入,并对各正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各业务子数据进行分类存储;将各异常业务数据生成异常数据包,在接收到对异常数据包的退换请求时,对异常数据包进行退换操作。本方案通过校验的方式识别正常业务数据和异常业务数据,并对正常业务数据导入管理,而对异常业务数据退换,确保了所导入业务数据的质量,避免了人工的辨别筛选,提高了业务数据的自动化管理程度。

Description

业务数据管理方法、装置、设备及计算机可读存储介质
本申请要求于2018年10月16日提交中国专利局、申请号为201811206000.1、发明名称为“业务数据管理方法、装置、设备及计算机可读存储介质”的中国专利申请的优先权,其全部内容通过引用结合在申请中。
技术领域
本申请主要涉及金融技术领域,具体地说,涉及一种业务数据管理方法、装置、设备及计算机可读存储介质。
背景技术
随着技术的发展,金融机构在运营过程中,所涉及到的资产包越来越多,资产包中包括多条业务数据,每条业务数据对应一个欠款方的欠款信息;金融机构将从第三方机构获取而来的资产包,按照业务数据的形式传输到金融机构的系统进行管理。目前金融机构对于业务数据的管理不完善,没有对业务数据的质量进行区分,可能将风险性较大或信息缺失的业务数据引进到金融机构,而引起金融机构的风险;同时因没有区分质量,对于质量差的业务数据,需要人工辨别筛选并进行退换操作,管理的自动化程度低,增加了人力成本且操作效率低。
发明内容
本申请的主要目的是提供一种业务数据管理方法、装置、设备及计算机可读存储介质,旨在解决现有技术中对业务数据的管理不完善,容易引起金融机构风险,且管理的自动化程度低的问题。
为实现上述目的,本申请提供一种业务数据管理方法,应用于业务数据管理系统,所述业务数据管理系统包括交易通道子系统、核算子系统和资产管理子系统,所述业务数据管理方法包括以下步骤:
当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
此外,为实现上述目的,本申请还提出一种业务数据管理装置,所述业务数据管理装置包括:
校验模块,用于当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
拆分模块,用于对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
退换模型,用于将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
此外,为实现上述目的,本申请还提出一种业务数据管理设备,所述业务数据管理设备包括:存储器、处理器、通信总线以及存储在所述存储器上的业务数据管理可读指令;
所述通信总线用于实现处理器和存储器之间的连接通信;
所述处理器用于执行所述业务数据管理可读指令,以实现以下步骤:
当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所 述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
此外,为实现上述目的,本申请还提供一种计算机可读存储介质,所述计算机可读存储介质存储有一个或者一个以上程序,所述一个或者一个以上程序可被一个或者一个以上的处理器执行以用于:
当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
本实施例的业务数据管理方法,在接收到对业务数据的导入请求,将业务数据导入之前,先对业务数据进行校验,将业务数据划分为校验成功的正常业务数据和校验失败的异常业务数据;其中正常业务数据为质量满足金融机构需求的业务数据,而异常业务数据为质量不能满足金融机构需求的业务数据;对各个正常业务数据进行导入操作,并将导入的各个正常业务数据按照数据类型进行拆分为业务子数据,对该各个业务子数据进行分类存储,确保所导入业务数据的质量,避免了金融机构的风险;而对于各个异常业务数据则生成异常数据包,在接收到对异常数据包的退换请求时,则对异常数据包进行退换操作;对各异常业务数据 通过校验的方式进行识别,并以异常数据包的形式进行整体退换,避免了人工的辨别筛选,提高了业务数据的自动化管理程度。
附图说明
图1是本申请的业务数据管理方法第一实施例的流程示意图;
图2是本申请的业务数据管理装置第一实施例的功能模块示意图;
图3是本申请实施例方法涉及的硬件运行环境的设备结构示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请提供一种业务数据管理方法。
请参照图1,图1为本申请业务数据管理方法第一实施例的流程示意图。在本实施例中,所述业务数据管理方法包括:
步骤S10,当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
本申请的业务数据管理方法应用于金融机构中的服务器,适用于通过服务器对来源于资产包中的业务数据进行管理;其中资产包为金融机构向第三方机构所购买的欠款信息,各欠款信息以EXCEL文件的形式存在于资产包中,EXCEL文件中的一行对应一条欠款信息;每条欠款信息中至少包括欠款方名称、身份证号码、联系电话、欠款类型、欠款金额、欠款时长等数据,表征每条欠款所具有的各项信息。将一条欠款信息作为一项业务数据,资产包中包括各种各样的多项业务数据,每项业务数据均与一条欠款对应。金融机构的服务器连接有信息显示录入设备,该显示录入设备的显示界面上设置有用于业务数据导入的虚拟按键;当有对资产包中业务数据的导入需求时,触发该虚拟按键。将该虚拟按键的触发 操作作为业务数据的导入请求,当接收到该导入请求时,则对与该导入请求所针对的各项业务数据进行校验,以确保所请求导入的各项业务数据的安全性以及信息完整性;将经校验确定为符合安全性和信息完整性要求的各业务数据作为校验成功的正常业务数据,而将不符合安全性或者信息完整性要求的各业务数据作为校验失败的异常业务数据。具体地,对各业务数据进行校验的步骤包括:
步骤S11,逐一判断所述业务数据中的必填项是否为空值,若所述业务数据中的必填项为空值,则判定所述业务数据校验失败;
可理解地,因各项业务数据其实质为以资产包的EXCEL形式所存在的各条欠款信息,且每条欠款信息均包括多个数据;在校验时,先校验所请求导入的各业务数据是否以EXCEL文件形式存在。若以EXCEL文件形式存在,则进一步校验每项业务数据中的必填项是否为空值;若不以EXCEL文件形式存在,则判定资产包不合格,不进行后续的业务数据校验。其中必填项为对欠款进行催收所必要的信息,如欠款方联系电话、欠款金额等。当检测出业务数据中存在任意一项必填项为空值时,则说明缺少对欠款进行催收所必要的信息,可能导致金融机构无法对欠款进行正常催收,而将该缺少必填项的业务数据判定为校验失败。此外还可以校验各项业务数据的格式是否均满足要求,即业务数据的格式与欠款信息对应类型的格式对应,如联系电话或者日期所对应的格式为数字型数据;通过该必填项和业务数据格式的校验,来确保所导入业务数据的信息完整性和格式的准确性。
步骤S12,若所述业务数据中的必填项不为空值,则检测所述业务数据中是否具有存在于预设黑名单中的信息;
进一步地,当判断出业务数据中的必填项均不为空值时,则说明业务数据 中用于催收欠款的各项必要信息均完整;但考虑到业务数据中可能存在表征该业务数据存在风险的信息,如业务数据中欠款方身份证号码存在于黑名单中,表明该欠款方在金融机构中具有历史的风险信息;若将与该欠款方对应的业务数据导入到金融机构可能引起金融机构风险。为了避免因导入业务数据而给金融机构带来风险,预先将金融机构中历史确定为风险的数据形成预设黑名单,在检测出业务数据的信息完整后,进一步将业务数据和该预设黑名单中的所有数据对比,判断业务数据中是否具有存在于预设黑名单中的信息,以确保所导入业务数据的安全性。
步骤S13,若所述业务数据中具有存在于黑名单中的信息,则判定所述业务数据校验失败,若所述业务数据中不具有存在于黑名单中的信息,则判定所述业务数据校验成功。
当经对比判断出业务数据中具有存在于黑名单中的信息,则说明该业务数据具有历史的风险信息,若将其导入可能引起金融机构的风险;从而将该业务数据判定为校验失败,而不能对该业务数据进行导入操作。而当判断出业务数据中不具有存在于黑名单中的信息,则说明该业务数据不具有历史的风险信息,则将其判定为校验失败,以便于进行导入操作。对于校验过程中校验成功的业务数据分配成功标识符,而校验失败的业务数据分配失败标识符;在与导入请求对应的所有业务数据均校验完成后,将其中具有成功标识符的所有业务数据形成集合,生成正常业务数据;而将其中具有失败标识符的所有业务数据也形成集合,生成异常业务数据;以对正常业务数据进行导入,而对异常业务数据进行退换。
步骤S20,对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存 储;
进一步地,因正常业务数据属于安全可靠的业务数据,需要将其导入到金融机构。而业务数据在资产包的EXCEL中以行的形式存在,正常业务数据相应的以行的形式存在于EXCEL文件中,在对正常业务数据进行导入时,以EXCEL文件中的行为单位,每次读取EXCEL文件中的一行内容进行导入,直到EXCEL文件中的所有行内容均导入完成。为了对导入的各项正常业务数据进行区分,对各项正常业务数据分配作为标识符的编号,形成各项正常业务数据之间的差异性,如第一项正常业务数据编号0001,第二项业务数据编号0002等。此外,因每项正常业务数据包括诸如欠款方名称、身份证号码、联系电话、欠款类型、欠款金额等多种类型的欠款方信息,在对正常业务数据导入完成后,需要对此各种类型的欠款方信息进行拆分;将各正常业务数据依据数据类型进行拆分,将类型相同的欠款方信息集合到一起,生成业务子数据并进行存储。如将各项正常业务数据中的欠款方身份证号拆分,并集合到一起所形成身份信息的业务子数据。各种类型的业务子数据也以EXCEL表的形式进行存储,且一个EXCEL表对应一类欠款方信息,即一类业务子数据,各个经拆分并集合而形成的EXCEL表中包含了各个欠款方的同一信息。为了在各个欠款方,即各项业务数据之间进行区分,而在各个EXCEL表之间进行关联,为各个拆分的信息添加表征其所来源的业务数据的编号,如对于来源上述编号0001正常业务数据中的身份证号码,为该身份证号码添加编号0001,以表征其来源,和身份信息表中的其他身份证号码形成区别。
步骤S30,将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
更进一步地,因异常业务数据属于信息不完整或者存在风险的数据,若将 该类异常业务数据导入到金融机构,不能对欠款进行催收或者给金融机构带来风险,从而需要将该类异常业务数据进行退换操作。具体地,将各异常业务数据生成异常数据包,在显示界面上设置有退换虚拟按键;当金融机构有对异常数据包的退换需求时,触发该退换虚拟按键,将该触发操作作为对异常数据包的退换请求;当接收到该退换请求时,则对该异常数据包进行退换操作。其中退换包括对异常数据包进行退款操作和将异常数据包更换为新数据包两个类型,在退换操作前需要先确定具体的退换类型;具体地,在接收到对异常数据包的退换请求时,对异常数据包进行退换操作的步骤包括:
步骤S31,当接收到对所述异常数据包的退换请求时,读取所述退换请求中所携带的退换标识符,并根据所述退换标识符确定所述退换请求的退换类型;
可理解地,金融机构工作人员在触发退换虚拟按键,发起退换请求前,先选择所需要的退换类型,将该选择的退换类型以退换标识符的形式添加到退换请求中。当服务器接收到对异常数据包的退换请求时,读取退换请求中所携带的退换标识符,并由该退换标识符确定退换请求的退换类型,即对异常业务数据的退换类型。
步骤S32,当所述退换类型为第一类型时,则根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及各所述异常业务数据的数量,确定退款金额,并根据所述退款金额对所述待退换资产包进行退换操作;
本实施例中将退款的退换类型作为第一类型,当由退换请求中的退换标识符判定退换类型为第一类型,即针对异常业务数据进行退款时,则读取与业务数据对应的交易金额,各业务数据的数量以及异常业务数据的数量。因业务数据为存在于资产包中的欠款信息,而资产包由金额机构向第三方机构所购买,购买资 产包所花费的金融即为购买各个业务数据所花费的金额,将该金额作为与业务数据对应的交易金额。同时资产包中所包括的欠款信息数量即为业务数据的数量,即EXCEL表中所包括业务数据的行数;而异常业务数据的数量为业务数据中验证失败的业务数据数量。由该交易金额,并结合业务数据的数量和异常业务数据的数量,可确定退款金额。该退款金额与异常业务数据的数量在业务数据数量之间的占比相关,可由预设公式计算生成;具体地,根据与各业务数据对应的交易金额、各业务数据的数量以及异常业务数据的数量,确定退款金额的步骤包括:
将所述交易金额、各所述业务数据的数量以及各所述异常业务数据的数量传输到预设公式中,根据所述预设公式,生成退款金额;
所述预设公式为:
Figure PCTCN2018123363-appb-000001
其中,y表示退款金额、m表示交易金额、n1表示各所述异常业务数据的数量、n2各所述业务数据的数量。
即,将读取的交易金额、各业务数据的数量以及异常业务数据的数量分别输入到预设公式中,替换其中的m、n1、n2,计算得出退款金额。在确定退款金额后,则可对异常数据包进行退换操作,将异常数据包中的各项异常业务数据退回到业务数据的来源方,并接收该来源方退回的退款金额,完成异常数据包的退换。
步骤S33,当所述退换类型为第二类型时,则将所述异常数据包传输到所述业务数据的来源方,并接收所述来源方返回的新业务数据。
更进一步地,将异常数据包更换为新数据包的退换类型作为第二类型,当由退换请求中的退换标识符判定退换请求的类型为第二类型,即将异常业务数据更换为其他新业务数据时,则异常数据包中异常业务数据的数量即为所需要退换 的业务数据数量,且其中的异常业务数据为所需要退换的业务数据本身。从而将异常数据包作为整体传输到业务数据的来源方,即将异常业务数据退回到来源方,并接收该来源方传输的新业务数据;其中传输的新业务数据中所表征的总欠款金额和异常数据包中所表征的总欠款金额相同,以进行等价更换,完成异常数据包中异常业务数据的退换。
本实施例的业务数据管理方法,在接收到对业务数据的导入请求,将业务数据导入之前,先对业务数据进行校验,将业务数据划分为校验成功的正常业务数据和校验失败的异常业务数据;其中正常业务数据为质量满足金融机构需求的业务数据,而异常业务数据为质量不能满足金融机构需求的业务数据;对各个正常业务数据进行导入操作,并将导入的各个正常业务数据按照数据类型进行拆分为业务子数据,对该各个业务子数据进行分类存储,确保所导入业务数据的质量,避免了金融机构的风险;而对于各个异常业务数据则生成异常数据包,在接收到对异常数据包的退换请求时,则对异常数据包进行退换操作;对各异常业务数据通过校验的方式进行识别,并以异常数据包的形式进行整体退换,避免了人工的辨别筛选,提高了业务数据的自动化管理程度。
进一步地,在本申请业务数据管理方法另一实施例中,所述将各所述业务子数据进行分类存储的步骤之后包括:
步骤S40,当接收到对所述业务数据的查询请求时,读取所述查询请求的查询标识符,并根据所述查询标识符,确定所述业务子数据中的各待查询业务数据;
可理解地,资产包中的业务数据量众多,在对业务数据管理过程中存在对其中任意业务数据查询的需求,如金融机构工作人员查询某项业务数据中欠款方的还款情况,或者欠款方查询其自身的欠款情况等。针对查询需求,在显示界面 上设置有查询输入框和查询虚拟按键;有查询需求的需求方将需要查询的信息作为关键词输入到输入框,并点击查询虚拟按键,以触发查询请求。当接收到该对业务数据的查询请求时,读取与查询请求一并发送的关键词,将该关键词作为查询标识符。该关键词可以为身份证号,在接收到作为查询标识符的身份证号后,查询与该身份证号对应的编号;该编号可表征该身份证号所来源的正常业务数据,该正常业务数据中所拆分的其他信息均携带有该编号;进而由编号可查询到所有携带有该编号的信息,此带有编号的信息为来源于正常业务数据经拆分的信息,为需求方所需要查询的信息,而将其确定为业务子数据中的各待查询业务数据。
步骤S50,将各所述待查询业务数据传输到预设模板中,生成查询信息,并将所述查询信息输出显示。
进一步地,因经查询得到的待查询业务数据以分散的单个数据存在,为了将各个待查询业务数据呈现,预先设置有预设模板;该预设模板为可视化的展示模板,不同的位置显示不同的数据;如模板中的左上角用于显示欠款方的名称数据,而右上角用于显示欠款方的身份证号等。将查询得到的各个待查询业务数据传输到该预设模板中,替换其中的模板内容,经替换后的预设模板即为查询信息;将该查询信息输出显示,以便查询需求方进行查看。
进一步地,在本申请业务数据管理方法另一实施例中,所述将各所述业务子数据进行分类存储的步骤之后包括:
步骤S60,当接收到更新请求时,读取所述更新请求中所携带的更新标识符;
可理解地,对于导入的表征欠款信息的正常业务数据,欠款方需要对与其对应欠款信息中的欠款金额进行偿还。在欠款方对其所欠金额进行偿还后,该欠款方对应欠款信息中的欠款金额发生变化,即正常业务数据中的信息发生变化, 需要进行更新。具体地,本金融机构的服务器与用于核算欠款金额的核算系统通信连接,核算系统对欠款方所偿还的欠款金额进行核算;在核算完成后,向服务器发送对正常业务数据进行更新的更新请求。当接收到该更新请求时,读取更新请求中所携带的更新标识符,该更新标识符其实质为核算的欠款金额中所携带的编号,表征该核算的欠款金额所来源的正常业务数据,以便于根据该更新标识符确定所需要更新的正常业务数据。
步骤S70,根据所述更新标识符确定所述业务子数据中的待更新业务子数据,将与所述待更新业务子数据对应的所述正常业务数据更新为目标业务数据。
进一步地,在读取到更新请求中所携带的更新标识符后,因更新标识符为正常业务数据的编号,正常业务数据拆分所得到的业务子数据也均携带有该编号;从而将该更新标识符和各个业务子数据所携带编号进行对比,确定与该更新标识符一致的编号,该具有该一致编号的业务子数据即为各业务子数据中需要更新的待更新业务子数据。该待更新业务子数据由经校验成功的正常业务数据拆分而来,而将待更新业务子数据所来源的正常业务数据更新为目标业务数据;即将各个待更新业务子数据进行更新,形成目标业务数据。其中更新的内容由欠款方偿还的欠款金额确定,当欠款方偿还欠款金额中的本金,则对待更新业务子数据中的本金进行更新;而当偿还欠款金额中的利息,则对待更新业务子数据中的利息进行更新;而当偿还欠款金额中的手续费,则对待更新业务子数据中的手续费进行更新;同时对欠款方的偿还时间进行更新,以表征最新的还款时间;在各个待更新业务子数据均更新完成后,则将具有与待更新业务子数据相同编号的所有业务子数据生成目标业务数据,完成对正常业务数据的更新。
更进一步地,本实施例还设置有减免机制,减免机制为当欠款方对欠款金 额偿还达到一定程度,即预设减免条件时,对欠款方的欠款进行减免,以激励欠款方的还款。为了确定是否可对欠款方的欠款进行减免,在欠款方对其欠款金额进行偿还后,需要确定欠款方所偿还的欠款金额是否满足预设减免条件。具体地,将与待更新业务子数据对应的正常业务数据更新为目标业务数据的步骤之后包括:
步骤S80,将所述正常业务数据和所述目标业务数据对比,生成对比结果,并将所述对比结果和预设减免条件对比,判断所述对比结果是否满足所述预设减免条件;
进一步地,在将正常业务数据更新为目标业务数据之后,目标业务数据中的欠款金额相对于正常业务数据中的欠款金额减少;其中目标业务数据中的欠款金额为欠款人对其所欠款项偿还后的剩余金额,而正常业务数据中的欠款金额为欠款人初始所欠款项的全部金额;将两者之间的欠款金额进行相减,并用相减的结果和正常业务数据中的欠款金额做比值,得到的比值结果为欠款方所偿还欠款金额的比值。将该所偿还欠款金额的比值作为正常业务数据和目标业务数据对比所生成的对比结果,进而将该对比结果和预设减免条件进行对比,判断欠款方所偿还的欠款金额是否达到预设减免条件。如设定的预设减免条件为:当所偿还的欠款金额达到欠款金额的90%,剩余的10%可全部减免,或者部分减免,或者延长还款时间;而正常业务数据和目标业务数据对比的对比结果为80%,其和预设减免条件对比,可知没有达到预设减免条件,而不能进行减免。
步骤S90,若所述对比结果满足所述预设减免条件,则向所述目标业务数据对应业务方输出提示信息。
当将对比结果和预设减免条件进行对比,判断出对比结果满足预设减免条 件时,则说明可对欠款方的欠款金额进行减免;从而向目标业务数据对应业务方输出提示信息,该目标业务数据对应的业务方其实质为与目标业务数据对应的欠款方;向欠款方输出提示信息,以告知其剩余的欠款金额满足预设减免条件,可进行减免;以促进与目标业务数据对应欠款方的还款,提高对目标业务数据中欠款金额的催收速度。
此外,请参照图2,本申请提供一种业务数据管理装置,在本申请业务数据管理装置第一实施例中,所述业务数据管理装置包括:
校验模块10,用于当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
拆分模块20,用于对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
退换模型30,用于将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
本实施例的业务数据管理装置,在接收到对业务数据的导入请求,将业务数据导入之前,校验模块10先对业务数据进行校验,将业务数据划分为校验成功的正常业务数据和校验失败的异常业务数据;其中正常业务数据为质量满足金融机构需求的业务数据,而异常业务数据为质量不能满足金融机构需求的业务数据;拆分模块20对各个正常业务数据进行导入操作,并将导入的各个正常业务数据按照数据类型进行拆分为业务子数据,对该各个业务子数据进行分类存储,确保所导入业务数据的质量,避免了金融机构的风险;而对于各个异常业务数据则生成 异常数据包,退换模型30在接收到对异常数据包的退换请求时,则对异常数据包进行退换操作;对各异常业务数据通过校验的方式进行识别,并以异常数据包的形式进行整体退换,避免了人工的辨别筛选,提高了业务数据的自动化管理程度。
其中,上述业务数据管理装置的各虚拟功能模块存储于图3所示业务数据管理设备的存储器1005中,处理器1001执行业务数据管理可读指令时,实现图2所示实施例中各个模块的功能。
需要说明的是,本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成,也可以通过计算机可读指令控制相关的硬件完成,所述的可读指令可以存储于一种非易失性计算机可读存储介质中,上述提到的非易失性可读存储介质可以是只读存储器,磁盘或光盘等。
参照图3,图3是本申请实施例方法涉及的硬件运行环境的设备结构示意图。
本申请实施例业务数据管理设备可以是PC(personal computer,个人计算机),也可以是智能手机、平板电脑、电子书阅读器、便携计算机等终端设备。
如图3所示,该业务数据管理设备可以包括:处理器1001,例如CPU(Central Processing Unit,中央处理器),存储器1005,通信总线1002。其中,通信总线1002用于实现处理器1001和存储器1005之间的连接通信。存储器1005可以是高速RAM(random access memory,随机存取存储器),也可以是稳定的存储器(non-volatile memory),例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地,该业务数据管理设备还可以包括用户接口、网络接口、摄像头、RF(Radio Frequency,射频)电路,传感器、音频电路、WiFi(Wireless Fidelity,无线宽带)模块等等。用户接口可以包括显示屏(Display)、输入单元比如键盘(Keyboard),可选用户接口还可以包括标准的有线接口、无线接口。网络接口可选的可以包括标准的有线接口、无线接口(如WI-FI接口)。
本领域技术人员可以理解,图3中示出的业务数据管理设备结构并不构成对 业务数据管理设备的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
如图3所示,作为一种计算机可读存储介质的存储器1005中可以包括操作系统、网络通信模块以及业务数据管理可读指令。操作系统是管理和控制业务数据管理设备硬件和软件资源的程序,支持业务数据管理可读指令以及其它软件和/或程序的运行。网络通信模块用于实现存储器1005内部各组件之间的通信,以及与业务数据管理设备中其它硬件和软件之间通信。
在图3所示的业务数据管理设备中,处理器1001用于执行存储器1005中存储的业务数据管理可读指令,实现上述业务数据管理方法各实施例中的步骤。
本申请提供了一种计算机可读存储介质,所述计算机可读存储介质存储有一个或者一个以上程序,所述一个或者一个以上程序还可被一个或者一个以上的处理器执行以用于实现上述业务数据管理方法各实施例中的步骤。
还需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在如上所述的一个计算机可读存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本申请各个实施例所述的方法。
以上所述仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是在本申请的构思下,利用本申请说明书及附图内容所作的等效结构变换,或直接/间接运用在其他相关的技术领域均包括在本申请的专利保护范围内。

Claims (20)

  1. 一种业务数据管理方法,其特征在于,所述业务数据管理方法包括以下步骤:
    当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
    对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
    将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
  2. 如权利要求1所述的业务数据管理方法,其特征在于,所述对各所述业务数据进行校验的步骤包括:
    逐一判断所述业务数据中的必填项是否为空值,若所述业务数据中的必填项为空值,则判定所述业务数据校验失败;
    若所述业务数据中的必填项不为空值,则检测所述业务数据中是否具有存在于预设黑名单中的信息;
    若所述业务数据中具有存在于黑名单中的信息,则判定所述业务数据校验失败,若所述业务数据中不具有存在于黑名单中的信息,则判定所述业务数据校验成功。
  3. 如权利要求1所述的业务数据管理方法,其特征在于,所述在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作的步骤包括:
    当接收到对所述异常数据包的退换请求时,读取所述退换请求中所携带的 退换标识符,并根据所述退换标识符确定所述退换请求的退换类型;
    当所述退换类型为第一类型时,则根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及各所述异常业务数据的数量,确定退款金额,并根据所述退款金额对所述异常数据包进行退换操作;
    当所述退换类型为第二类型时,则将所述异常数据包传输到所述业务数据的来源方,并接收所述来源方返回的新业务数据。
  4. 如权利要求3所述的业务数据管理方法,其特征在于,所述根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及所述异常业务数据的数量,确定退款金额的步骤包括:
    将所述交易金额、各所述业务数据的数量以及各所述异常业务数据的数量传输到预设公式中,根据所述预设公式,生成退款金额;
    所述预设公式为:
    Figure PCTCN2018123363-appb-100001
    其中,y表示退款金额、m表示交易金额、n1表示各所述异常业务数据的数量、n2各所述业务数据的数量。
  5. 如权利要求1所述的业务数据管理方法,其特征在于,所述将各所述业务子数据进行分类存储的步骤之后包括:
    当接收到对所述业务数据的查询请求时,读取所述查询请求的查询标识符,并根据所述查询标识符,确定所述业务子数据中的各待查询业务数据;
    将各所述待查询业务数据传输到预设模板中,生成查询信息,并将所述查询信息输出显示。
  6. 如权利要求1所述的业务数据管理方法,其特征在于,所述将各所述业务子数据进行分类存储的步骤之后包括:
    当接收到更新请求时,读取所述更新请求中所携带的更新标识符;
    根据所述更新标识符确定所述业务子数据中的待更新业务子数据,将与所述待更新业务子数据对应的所述正常业务数据更新为目标业务数据。
  7. 如权利要求6所述的业务数据管理方法,其特征在于,所述将与所述待更新业务子数据对应的所述正常业务数据更新为目标业务数据的步骤之后包括:
    将所述正常业务数据和所述目标业务数据对比,生成对比结果,并将所述对比结果和预设减免条件对比,判断所述对比结果是否满足所述预设减免条件;
    若所述对比结果满足所述预设减免条件,则向所述目标业务数据对应业务方输出提示信息。
  8. 一种业务数据管理装置,其特征在于,所述业务数据管理装置包括:
    校验模块,用于当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
    拆分模块,用于对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
    退换模型,用于将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
  9. 一种业务数据管理设备,其特征在于,所述业务数据管理设备包括:存储器、处理器、通信总线以及存储在所述存储器上的业务数据管理可读指令;
    所述通信总线用于实现处理器和存储器之间的连接通信;
    所述处理器用于执行所述业务数据管理可读指令,以实现以下步骤:
    当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
    对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
    将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
  10. 如权利要求9所述的业务数据管理设备,其特征在于,所述对各所述业务数据进行校验的步骤包括:
    逐一判断所述业务数据中的必填项是否为空值,若所述业务数据中的必填项为空值,则判定所述业务数据校验失败;
    若所述业务数据中的必填项不为空值,则检测所述业务数据中是否具有存在于预设黑名单中的信息;
    若所述业务数据中具有存在于黑名单中的信息,则判定所述业务数据校验失败,若所述业务数据中不具有存在于黑名单中的信息,则判定所述业务数据校验成功。
  11. 如权利要求9所述的业务数据管理设备,其特征在于,所述在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作的步骤包括:
    当接收到对所述异常数据包的退换请求时,读取所述退换请求中所携带的退换标识符,并根据所述退换标识符确定所述退换请求的退换类型;
    当所述退换类型为第一类型时,则根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及各所述异常业务数据的数量,确定退款金额,并根据所述退款金额对所述异常数据包进行退换操作;
    当所述退换类型为第二类型时,则将所述异常数据包传输到所述业务数据的来源方,并接收所述来源方返回的新业务数据。
  12. 如权利要求11所述的业务数据管理设备,其特征在于,所述根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及所述异常业务数据的数量,确定退款金额的步骤包括:
    将所述交易金额、各所述业务数据的数量以及各所述异常业务数据的数量传输到预设公式中,根据所述预设公式,生成退款金额;
    所述预设公式为:
    Figure PCTCN2018123363-appb-100002
    其中,y表示退款金额、m表示交易金额、n1表示各所述异常业务数据的数量、n2各所述业务数据的数量。
  13. 如权利要求9所述的业务数据管理设备,其特征在于,所述将各所述业务子数据进行分类存储的步骤之后,所述处理器用于执行所述业务数据管理可读指令,以实现以下步骤:
    当接收到对所述业务数据的查询请求时,读取所述查询请求的查询标识符,并根据所述查询标识符,确定所述业务子数据中的各待查询业务数据;
    将各所述待查询业务数据传输到预设模板中,生成查询信息,并将所述查询信息输出显示。
  14. 如权利要求9所述的业务数据管理设备,其特征在于,所述将各所述业务子数据进行分类存储的步骤之后,所述处理器用于执行所述业务数据管理可读指令,以实现以下步骤:
    当接收到更新请求时,读取所述更新请求中所携带的更新标识符;
    根据所述更新标识符确定所述业务子数据中的待更新业务子数据,将与所 述待更新业务子数据对应的所述正常业务数据更新为目标业务数据。
  15. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有业务数据管理可读指令,所述业务数据管理可读指令被处理器执行,实现以下步骤:
    当接收到导入请求时,读取与所述导入请求对应的各业务数据,并对各所述业务数据进行校验,生成校验成功的正常业务数据和校验失败的异常业务数据;
    对各所述正常业务数据进行导入,并对各所述正常业务数据依据数据类型进行拆分,对应分类生成业务子数据,将各所述业务子数据进行分类存储;
    将各所述异常业务数据生成异常数据包,在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作。
  16. 如权利要求15所述的计算机可读存储介质,其特征在于,所述对各所述业务数据进行校验的步骤包括:
    逐一判断所述业务数据中的必填项是否为空值,若所述业务数据中的必填项为空值,则判定所述业务数据校验失败;
    若所述业务数据中的必填项不为空值,则检测所述业务数据中是否具有存在于预设黑名单中的信息;
    若所述业务数据中具有存在于黑名单中的信息,则判定所述业务数据校验失败,若所述业务数据中不具有存在于黑名单中的信息,则判定所述业务数据校验成功。
  17. 如权利要求15所述的计算机可读存储介质,其特征在于,所述在接收到对所述异常数据包的退换请求时,对所述异常数据包进行退换操作的步骤包括:
    当接收到对所述异常数据包的退换请求时,读取所述退换请求中所携带的 退换标识符,并根据所述退换标识符确定所述退换请求的退换类型;
    当所述退换类型为第一类型时,则根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及各所述异常业务数据的数量,确定退款金额,并根据所述退款金额对所述异常数据包进行退换操作;
    当所述退换类型为第二类型时,则将所述异常数据包传输到所述业务数据的来源方,并接收所述来源方返回的新业务数据。
  18. 如权利要求16所述的计算机可读存储介质,其特征在于,所述根据与各所述业务数据对应的交易金额、各所述业务数据的数量以及所述异常业务数据的数量,确定退款金额的步骤包括:
    将所述交易金额、各所述业务数据的数量以及各所述异常业务数据的数量传输到预设公式中,根据所述预设公式,生成退款金额;
    所述预设公式为:
    Figure PCTCN2018123363-appb-100003
    其中,y表示退款金额、m表示交易金额、n1表示各所述异常业务数据的数量、n2各所述业务数据的数量。
  19. 如权利要求15所述的计算机可读存储介质,其特征在于,所述将各所述业务子数据进行分类存储的步骤之后,所述业务数据管理可读指令被处理器执行,实现以下步骤:
    当接收到对所述业务数据的查询请求时,读取所述查询请求的查询标识符,并根据所述查询标识符,确定所述业务子数据中的各待查询业务数据;
    将各所述待查询业务数据传输到预设模板中,生成查询信息,并将所述查询信息输出显示。
  20. 如权利要求15所述的计算机可读存储介质,其特征在于,所述将各所 述业务子数据进行分类存储的步骤之后,所述业务数据管理可读指令被处理器执行,实现以下步骤:
    当接收到更新请求时,读取所述更新请求中所携带的更新标识符;
    根据所述更新标识符确定所述业务子数据中的待更新业务子数据,将与所述待更新业务子数据对应的所述正常业务数据更新为目标业务数据。
PCT/CN2018/123363 2018-10-16 2018-12-25 业务数据管理方法、装置、设备及计算机可读存储介质 WO2020077836A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811206000.1A CN109582668A (zh) 2018-10-16 2018-10-16 业务数据管理方法、装置、设备及计算机可读存储介质
CN201811206000.1 2018-10-16

Publications (1)

Publication Number Publication Date
WO2020077836A1 true WO2020077836A1 (zh) 2020-04-23

Family

ID=65920551

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123363 WO2020077836A1 (zh) 2018-10-16 2018-12-25 业务数据管理方法、装置、设备及计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN109582668A (zh)
WO (1) WO2020077836A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113301115A (zh) * 2020-07-29 2021-08-24 钱秀英 一种对各通信设备之间传输数据时信息采集系统
CN112037000B (zh) * 2020-09-02 2023-09-22 中国银行股份有限公司 一种业务处理方法、装置及系统
CN112560097B (zh) * 2020-12-22 2022-09-30 广州技象科技有限公司 一种电力业务数据的存储管理方法及装置
CN112967143A (zh) * 2021-04-30 2021-06-15 平安普惠企业管理有限公司 债权数据处理方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106254045A (zh) * 2016-08-09 2016-12-21 中国银行股份有限公司 一种数据校验方法及装置
CN106846144A (zh) * 2017-01-08 2017-06-13 世纪禾光科技发展(北京)有限公司 Mt940报文在银企直连中应用的方法及系统
WO2017105882A1 (en) * 2015-12-17 2017-06-22 SpringAhead, Inc. Dynamic data normalitzation and duplicate analysis

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100961725B1 (ko) * 2005-10-28 2010-06-10 동양시스템즈 주식회사 확정기여형 퇴직연금 운영방법 및 시스템
CN103870274A (zh) * 2014-03-14 2014-06-18 浪潮集团山东通用软件有限公司 一种基于webservice技术下实现异构系统间数据交互的可视化开发组件
CN104503914A (zh) * 2014-12-29 2015-04-08 浪潮(北京)电子信息产业有限公司 一种信息诊断方法及系统
CN107547606B (zh) * 2016-06-29 2021-01-26 中兴通讯股份有限公司 数据处理方法、集群管理器、资源管理器、数据处理系统
CN108228635A (zh) * 2016-12-19 2018-06-29 北京奇虎科技有限公司 财务数据的导入方法、装置及财务系统
CN107992535A (zh) * 2017-11-23 2018-05-04 上海斐讯数据通信技术有限公司 文件快速寻址装置、方法、系统及计算机可读存储介质
CN108595597A (zh) * 2018-04-19 2018-09-28 平安科技(深圳)有限公司 数据导入方法、装置、计算机设备和存储介质

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017105882A1 (en) * 2015-12-17 2017-06-22 SpringAhead, Inc. Dynamic data normalitzation and duplicate analysis
CN106254045A (zh) * 2016-08-09 2016-12-21 中国银行股份有限公司 一种数据校验方法及装置
CN106846144A (zh) * 2017-01-08 2017-06-13 世纪禾光科技发展(北京)有限公司 Mt940报文在银企直连中应用的方法及系统

Also Published As

Publication number Publication date
CN109582668A (zh) 2019-04-05

Similar Documents

Publication Publication Date Title
WO2020077836A1 (zh) 业务数据管理方法、装置、设备及计算机可读存储介质
US10867304B2 (en) Account type detection for fraud risk
CN110782240B (zh) 业务数据处理方法、装置、计算机设备和存储介质
EP3859644B1 (en) Block chain-based data check system and method, computing device, and storage medium
US11151566B2 (en) Authentication and fraud prevention in provisioning a mobile wallet
WO2017028630A1 (zh) 一种验证方法及服务器
CN110458562B (zh) 票据报销方法、装置和设备及计算机存储介质
US20150220933A1 (en) Methods and systems for making secure online payments
CN111444209B (zh) 一种基于区块链的数据处理方法、装置、设备及介质
CN109636564A (zh) 用于风控的信息核实方法、装置、设备及存储介质
US20130282583A1 (en) Fraud detection system rule profile interaction
CN113034274A (zh) 一种基于区块链的供应链金融服务系统、方法及终端设备
CN111429057A (zh) 一种数字仓单管理方法和装置
US20140089023A1 (en) Method and system for distributing data stream
WO2020233402A1 (zh) 应付账款订单校验方法、装置、设备及存储介质
TW202009771A (zh) 基於區塊鏈存證的識別證據真實性的方法及裝置
CN110851298A (zh) 异常分析及处理方法、电子装置及存储介质
CN115344888A (zh) 数据访问方法、装置、电子设备及存储介质
CN109634950A (zh) 业务数据管理方法、装置、设备及计算机可读存储介质
CN108550017B (zh) 基于saas平台的消费金融核心系统
CN112965986A (zh) 业务一致性处理方法、装置、设备及存储介质
WO2021223657A1 (zh) 数据交互
CN113822660A (zh) 数据处理的方法、装置、电子设备及介质
US10216830B2 (en) Multicomputer processing of client device request data using centralized event orchestrator and link discovery engine
EP3631731A1 (en) System for pushing transactional data

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: 18937196

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 06/08/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 18937196

Country of ref document: EP

Kind code of ref document: A1