WO2020248883A1 - 一种催收方法、***及装置 - Google Patents

一种催收方法、***及装置 Download PDF

Info

Publication number
WO2020248883A1
WO2020248883A1 PCT/CN2020/094238 CN2020094238W WO2020248883A1 WO 2020248883 A1 WO2020248883 A1 WO 2020248883A1 CN 2020094238 W CN2020094238 W CN 2020094238W WO 2020248883 A1 WO2020248883 A1 WO 2020248883A1
Authority
WO
WIPO (PCT)
Prior art keywords
collected
collection
user
users
operator
Prior art date
Application number
PCT/CN2020/094238
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 WO2020248883A1 publication Critical patent/WO2020248883A1/zh

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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • 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/03—Credit; Loans; Processing thereof

Definitions

  • the present invention relates to the technical field of financial technology (Fintech), in particular to a collection method, system and device.
  • the manual collection method is a commonly used collection method. For example, if 50 users (such as small and micro enterprises) apply for a small and micro enterprise loan from the bank and have not repaid the loan overdue, the manual collection method can be used manually Set the collection dialing method corresponding to these 50 users (for example, it can include the number of collection calls, introduction language, speech, etc.), and then the operator can dial the collection call to these 50 users according to the manual collection dialing method set by the operator. In this way, more manual intervention is usually required, which may make the collection efficiency lower; for example, for small and micro enterprises A among 50 small and micro enterprises, the manual collection method needs to be based on the small and micro enterprises.
  • the loan information of A, the historical loan situation of small and micro enterprise A, and the credit of small and micro enterprise A determine the level of risk of small and micro enterprise A's repayment; further, if small and micro enterprise A is determined to be a high-risk enterprise in repayment, then You can choose more stringent words to collect collection on the small and micro enterprise A. If it is determined that the small and micro enterprise A is a low-risk enterprise for repayment, you can choose a more moderate method to collect the small and micro enterprise A. In the above process, the process of manual analysis usually takes a long time, and errors may occur, resulting in low collection efficiency and accuracy.
  • the embodiments of the present invention provide a collection method, system and device to improve the efficiency and accuracy of collection.
  • an embodiment of the present invention provides a collection collection method, the method including:
  • the collection status of one or more users to be collected is described, and the collection mode corresponding to the one or more users to be collected is determined according to the collection status of the one or more users, and then the one or more users are sent to the operator Multiple collection methods corresponding to the users to be collected, so that the operator can collect collection from the one or more users to be collected according to the collection methods corresponding to the one or more users to be collected; wherein, the one or more The collection manner corresponding to the user to be collected is used to indicate the manner of collecting the one or more users to be collected.
  • the collection status of one or more users to be collected is used to determine the corresponding collection method of one or more users to be collected, without manual intervention, the corresponding collection dialing method of each user to be collected can be automatically obtained, thereby improving The efficiency and accuracy of the collection; and by decoupling the collection method from the business system, the collection method in the above design can be applied to multiple business systems, without the need to determine the collection method corresponding to the user to be collected for a single business system , Which can make the application range of the collection method wider.
  • the method further includes: receiving the collection results of the one or more users to be collected from the operator, and updating the office according to the collection results of the one or more users to be collected.
  • the collection status of the one or more users to be collected stored in the preset database; further, for the first user to be collected among the one or more users to be collected, according to the first user to be collected
  • the collection status determines whether the first user to be collected is to be collected a second time; if it is determined that the first user to be collected is to be collected a second time, then the first user to be collected is determined according to the collection result of the first user to be collected
  • the second collection method corresponding to the user to be collected, and the second collection method corresponding to the first user to be collected is sent to the operator, so that the operator can send to the operator according to the second collection method corresponding to the first user to be collected
  • the first user to be collected performs a second collection.
  • the collection status corresponding to one or more users to be collected can be determined, that is, the effect achieved by the current collection of one or more users to be collected ( For example, the collection method has been successfully conveyed, the user to be collected has confirmed the repayment period, the user to be collected does not answer the call, the user to be collected hangs up, etc.), so that the subsequent execution can be determined according to the corresponding collection status of one or more users to be collected
  • This kind of collection process that is to say, the above design can quickly plan the follow-up collection method by receiving the collection result of the operator in real time, thereby improving the collection efficiency.
  • the determining whether to perform a second collection of the first user to be collected according to the collection status of the first user to be collected includes: when the collection status of the first user to be collected is When committing to repay within a preset time limit, if the first user to be collected fails to repay the loan on time within the preset time limit, it is determined that the first user to be collected will be collected twice; If the collection user repays the payment on time within the preset time limit, it is determined not to perform a second collection for the first user to be collected.
  • the collection status of the first collection determines whether the user to be collected will perform the second collection, it is possible to avoid the harassment caused by the second collection of the user to be collected when the user to be collected promises to repay, and to improve the waiting collection User experience; and, by real-time monitoring of the repayment period promised by the user to be collected, the user can be collected in time when the user to be collected breaks the promise, so that the evasive behavior of the user to be collected can be avoided and the efficiency of the collection can be improved.
  • the sending the collection method corresponding to the one or more users to be collected to the operator includes: dividing the one or more users to be collected into the first type of users to be collected and the first type Two types of users to be collected, the risk value of the first type of users to be collected is greater than the risk value of the second type of users to be collected; further, the information of the first type of users to be collected is sent to the first operator , And send the information of the second type of users to be collected to the second operator.
  • the collection phone number dialed by a Unicom operator to a user to be collected can be displayed as a local number.
  • the higher-risk user to be collected will have extreme Dadi may answer calls from China Unicom operators, so that the transfer rate of the collection method is higher, and the collection effect of collection to high-risk users is improved.
  • the method further includes: signing the collection result of the one or more users to be collected through the one or more service systems and the operator, and signing all the results after the signature.
  • the collection results of one or more users to be collected are stored on the blockchain.
  • the one or more users to be collected are selected from at least one user who has transactions with the one or more business systems based on the information of the at least one user; if the user If it is an enterprise, the collection status of the user includes any one or more of the following: the information of the corporate legal person, the loan and repayment information of the holding fixed legal person in the enterprise, the loan and repayment information of the enterprise, and the basic business of the enterprise information.
  • an embodiment of the present invention provides a collection system, where the collection system includes at least one business system, a collection unit and an operator connected to the at least one business system;
  • the at least one business system is configured to determine one or more users to be collected from at least one user who has a transaction relationship with the at least one business system, and send the identification of the one or more users to be collected to Collection device;
  • the collection unit is configured to receive the identification of one or more users to be collected from the at least one business system, and to determine the one or more users to be collected according to the collection status of the one or more users.
  • the corresponding collection method; the collection method corresponding to the one or more users to be collected is used to indicate the method of collecting the one or more users to be collected; and, to send the one or more users to be collected to the operator.
  • the operator is configured to collect collection from the one or more users to be collected according to the collection manner corresponding to the one or more users to be collected.
  • the operator is further configured to: send the collection result of the first user to be collected after collecting the first user to be collected according to the collection method corresponding to the first user to be collected To a collection unit; the collection unit is further configured to: receive the collection result of the first user to be collected from the operator, and update the preset database according to the collection result of the first user to be collected The collection status of the first user to be collected; if it is determined that the first user to be collected is to be collected twice, the second user to be collected is determined according to the collection result of the first user to be collected And send the second collection method corresponding to the first user to be collected to the operator; the operator is also used to: send the second collection method corresponding to the first user to be collected to the first The user to be collected performs a second collection.
  • an embodiment of the present invention provides a collection collection device, the device includes:
  • a transceiver module configured to receive a collection list sent by at least one business system, the collection list including one or more identities of users to be collected;
  • An obtaining module configured to obtain the collection status of the one or more users to be collected that matches the identification of the one or more users to be collected from a preset database
  • the processing module is configured to determine the collection mode corresponding to the one or more users to be collected according to the collection status of the one or more users to be collected; the collection mode corresponding to the one or more users to be collected is used to indicate The manner in which the one or more users to be collected perform collection;
  • the transceiver module is further configured to send to the operator the collection manner corresponding to the one or more users to be collected, so that the operator sends the collection method corresponding to the one or more users to be collected to the one Or multiple users to be collected for collection.
  • the transceiver module is further configured to: receive the collection result of the one or more users to be collected from the operator, and according to the collection result of the one or more users to be collected Update the collection status of the one or more users to be collected stored in the preset database; the processing module is further configured to: for the first user to be collected among the one or more users to be collected, according to The collection status of the first user to be collected determines whether the first user to be collected is to be collected a second time; if it is determined that the first user to be collected is to be collected a second time, then according to the first user to be collected The collection result determines the second collection method corresponding to the first user to be collected, and sends the second collection method corresponding to the first user to be collected to the operator, so that the operator can follow the first user to be collected The corresponding secondary collection method performs secondary collection to the first user to be collected.
  • the processing module is specifically configured to: when the collection status of the first user to be collected is promised to repay within a preset time limit, if the first user to be collected is in the preset If the payment is not repaid on time within the time limit, it is determined that the first user to be collected will be collected a second time; if the first user to be collected is repaid on time within the preset time limit, it is determined not to be collected The user performs a second collection.
  • the transceiver module is specifically configured to: divide the one or more users to be collected into a first type of users to be collected and a second type of users to be collected, and the first type of users to be collected The risk value of is greater than the risk value of the second type of users to be collected; further, the information of the first type of users to be collected is sent to the first operator, and the information of the second type of users to be collected is sent To the second operator.
  • the processing module is further configured to: use the one or more business systems and the operator to sign the collection results of the one or more users to be collected, and to sign The collection results of the one or more users to be collected are stored on the blockchain.
  • the one or more users to be collected are selected from at least one user who has transactions with the one or more business systems based on the information of the at least one user; if the user If it is an enterprise, the user’s information includes any one or more of the following: corporate information of the corporate legal person, loan and repayment information of the holding fixed legal person in the enterprise, loan and repayment information of the enterprise, and basic business information of the enterprise .
  • a computer-readable storage medium provided by an embodiment of the present invention includes instructions, which when run on a computer, cause the computer to execute the collection collection method as described in any of the first or second aspects.
  • a computer program product provided by an embodiment of the present invention, when it runs on a computer, causes the computer to execute the collection collection method described in any one of the first or second aspects.
  • FIG. 1 is a schematic diagram of a system architecture of a collection system provided by an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a process corresponding to a collection method provided by an embodiment of the present invention
  • 3a is a schematic diagram of a system architecture of a server cluster system provided by an embodiment of the present invention.
  • 3b is a schematic diagram of the system architecture of another server cluster system provided by an embodiment of the present invention.
  • Figure 4 is a schematic structural diagram of a collection device provided by an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present invention.
  • Fig. 6 is a schematic structural diagram of a back-end device provided by an embodiment of the present invention.
  • Fintech refers to a new innovative technology brought to the financial field after the integration of information technology into the financial field.
  • the financial system can be improved by using advanced information technology to assist in financial operations, transaction execution and financial system improvements. Processing efficiency, business scale, and can reduce costs and financial risks.
  • the field of financial technology usually involves a large amount of data, such as loan data of the credit department, card purchase data of the sales department, maintenance data of the operation and maintenance department, etc. How to use technology to extract financial data from the large amount of data The characteristics required by the field have always been the goal pursued by the financial technology field.
  • the credit database of the credit department can store tens of thousands or even hundreds of thousands of historical loan data.
  • the staff of the credit department can usually analyze these historical loan data according to a preset cycle (such as one day, one week, one month), if a certain piece of loan data is found to exceed the time limit, or a certain piece of loan data is found If the credit data is about to expire and the user has not repaid, the user corresponding to the credit data can be collected.
  • a preset cycle such as one day, one week, one month
  • a collection method can be designed for each product.
  • a collection method a 1 coupled with the small and micro loan products can be designed.
  • the collection method a 1 can include Some characteristics of small and micro loan products, so that the collection method a 1 can be used for collection of small and micro loan companies; accordingly, for individual industrial and commercial loan products, another collection method a 2 coupled with individual industrial and commercial loan products is designed,
  • the collection method a 2 can include some characteristics of individual industrial and commercial loan products, so the collection method a 2 can be used to collect collections for self-employed individuals who loan individual industrial and commercial loans. Take collection method a 1 as an example.
  • the collection method a 1 can be used to analyze and determine which users of all loan small and micro loan products need to be collected. Collection, so as to organize the users who need to be collected into a collection list, and send the collection list to the operator; in this way, the operator can call the collection calls to the users to be collected in the collection list in turn. Since the collection method a 1 is a collection method coupled with small and micro loan products, when the operator makes a collection call, it can collect collection from each user to be collected in the following collection method: "Users of small and micro loans***, Hello, since your loan is about to expire (or has expired), please make repayment as soon as possible.”
  • the collection method needs to be coupled with the product, which will cause different products corresponding to different business systems to be unable to reuse the collection method of another product, resulting in poor portability of the collection method, and virtually increasing the development collection The cost of the method.
  • the embodiment of the present invention provides a collection method for improving the efficiency and accuracy of collection.
  • Figure 1 is a schematic diagram of the system architecture of a collection system provided by an embodiment of the present invention.
  • the system may include at least one business system (such as the business system 101, the business system 102, and the business system shown in Figure 1). 103).
  • the collection unit 200 and the operator 300 connected to at least one business system.
  • at least one business system may be connected to the collection unit 200 in a wired manner, or may also be connected to the collection unit 200 in a wireless manner, which is not specifically limited.
  • At least one business system can refer to at least one business group in the credit department.
  • Each business group in the at least one business group can develop one or more loan products, and can manage the cost of the credit department. Transactions related to one or more loan products developed by the business group.
  • the business system 101 develops a small and micro loan product
  • users 1 to 100 apply to the credit department and successfully obtain a small and micro loan product
  • the business system 101 can combine the loan information and basic information of users 1 to 100
  • Information and credit information are stored in the small and micro loan database set up in the business system 101, so that the repayment behaviors of users 1 to 100 can be recorded based on the small and micro loan database, such as the repayment period of users 1 to 100, Historical repayment on time rate, credit evaluation, etc.
  • the business system 101 develops small and micro loan products
  • the business system 102 develops individual industrial and commercial loan products
  • the business system 103 develops private enterprise loan products
  • the business system 101 to the business system 103 can collect collections separately Of small and micro loan product users, individual industrial and commercial loan product users, and private enterprise loan product users are sent to the collection unit 200.
  • the collection unit 200 can determine the collection method of the user of the small and micro loan product according to the current collection status of the user of the small and micro loan product, and determine the collection method of the individual industrial and commercial loan product user according to the current collection status of the individual industrial and commercial loan product user.
  • the current collection status of the loan product user determines the collection method of the private enterprise loan product user; for example, if a small and micro loan product user has repaid, there is no need to collect collection from the small and micro loan product user. If a certain small and micro loan is determined If the product user has reached the repayment period and has low credit, he can use stricter tactics to collect the small and micro loan product user.
  • the collection unit 200 may send the collection method of small and micro loan product users, the collection method of individual industrial and commercial loan product users, and the collection method (including contact information) of private enterprise loan product users to the operator, so that the operator can send the payment to the small Users of micro-loan products, users of individual industrial and commercial loan products, and users of private-owned enterprise loan products respectively dial collection calls to realize business system 101, business system 102, and business system 103 for small and micro loan products, individual industrial and commercial loan products, and private enterprise loan products. management.
  • the following describes the collection method provided by the embodiment of the present invention by taking collection from the user of the small and micro loan product managed by the business system 101 as an example. Understandably, the process of collecting collection from users of other loan products managed by other business systems can be referred to This method is implemented, and the details are not repeated here.
  • FIG. 2 is a schematic diagram of a process corresponding to a collection method provided by an embodiment of the present invention, and the method includes:
  • Step 201 The business system 101 determines one or more users to be collected.
  • the business department 101 can store the user’s data in the small and micro loan database while approving the loan to the user. It can be used to store data of users who have made small and micro loans to the business department 101 but have not yet repaid.
  • the user’s data can include the user’s basic information, loan information, credit information, etc.
  • the basic information can include the user’s name, ID number, contact information, home address, email address, etc.
  • the loan information can include the user’s loan amount, The length of the loan, the repayment method, etc., the credit information may include the user's historical loan information, other business systems (such as the business system 102 and/or the business system 103) evaluation information on the user, and so on.
  • Table 1 is a schematic table of a possible small and micro loan database provided by an embodiment of the present invention.
  • Table 1 Schematic representation of a possible small and micro loan database
  • the basic information and credit information of multiple users can be stored in the small and micro loan database.
  • the name of user A 3 can be Wang Wu, and the ID number can be X 3 .
  • Historical credit can be good; correspondingly, the loan amount and repayment date of multiple users can also be stored in the small and micro loan database.
  • the loan amount of user A 3 can be 10 million, and the repayment date can be 2019.06.
  • Table 1 is only an exemplary simple description. The information listed is only for the convenience of explaining the plan, and does not constitute a limitation on the plan. Understandably, the small and micro loan database can also include Other information, such as the gender and age of the user, are not specifically limited.
  • the business system 101 can obtain all the users who have loaned the small and micro loan products stored in the small and micro loan database, for each of all users, if it is determined that the current date has exceeded or reached the loan term of the user If the user has not repaid, it can be determined that the user is a user to be collected; if it is determined that the current date is approaching the user’s loan term and the user has not repaid, it can be determined based on the user’s loan amount, credit information, etc. Whether the user is to be collected.
  • the business system 101 can select the user A 1 whose repayment period is less than the current date and the repayment period equal to the repayment period of users A 1 to A 3 in the small and micro loan database a 2 date the current user's collection to be as user; in the repayment period for a 3, business system 101 may credit a 3, the repayment period, the amount of loans obtained to assess user a 3 from the current date two days of the user by analyzing the user's Repayment risk.
  • the lower the user’s credit the closer the repayment period, and the higher the loan amount, the higher the user’s repayment risk; as shown in Table 1, since user A 3 has a larger loan amount, The repayment period is close to the current date and the credit is average. Therefore, the credit department can also regard user A 3 as a user to be collected.
  • the business system 101 can base on the personal information of the legal person of the small and micro enterprise, the loan and repayment information of the holding fixed legal person in the enterprise, the loan and repayment information of the enterprise, the basic business information of the enterprise, etc. Comprehensively determine the repayment risk value of small and micro enterprises.
  • the legal person's bank information can include the legal person's residence address, mail address, ethnicity, education, emergency contact and relationship, mobile phone number, home number, office number, bank tied to the card, and the risk obtained by pre-loan analysis and evaluation of the legal person Level, etc.; for example, the risk level of a legal person can be evaluated based on the legal person’s 12-period loan repayment, promised repayment, broken promise, historical collection calls, and the nature of the company. For example, if a high-risk event occurs in the industry in which the company is located at the current date, the risk level of the legal person will also increase accordingly.
  • the loan and repayment information of the holding fixed legal person in the enterprise may include the number of loans of the shareholder in the credit department, the amount of the loan, the time of the loan, the corresponding repayment situation, and the data of the running account.
  • the loan and repayment information of the company can include the length of the company's debt, the amount owed, the total number of repayment periods, the number of deferred periods, whether there is active repayment experience, the age of the account, whether it is the first payment, and the first payment Whether it is overdue, the latest normal repayment date, loan limit value and risk level, etc.
  • the basic business information of an enterprise may include the name of the enterprise, its address, the nature of the enterprise, and the position of the legal person.
  • the existing technology usually only evaluates the risk value of the enterprise's repayment based on the enterprise information.
  • the shareholders, legal persons, etc. in the enterprise will also have an impact on the enterprise's repayment, which will lead to the repayment based on the enterprise information evaluation.
  • the risk value of the loan is not accurate; in the embodiment of the present invention, the risk value of the enterprise's repayment is obtained through comprehensive evaluation using enterprise information, enterprise legal person information, and enterprise shareholder information, which can make the company's profile more perfect and the repayment risk value more accurate, thereby Can improve the accuracy of collection.
  • the business system 101 can determine that the users A 1 to A 3 are three users to be collected.
  • step 202 the business system 101 sends the identification of one or more users to be collected to the collection unit 200.
  • the business system 101 may send the identities of the users A 1 to A 3 to the collection unit 200.
  • the identification of user A 1 can refer to the contact information of user A 1 , or it can refer to the ID number of user A 1 , or it can also refer to the contact information and ID number of user A 1
  • the specific combination is not limited.
  • step 203 the collection unit 200 determines collection modes corresponding to one or more users to be collected respectively.
  • a preset database may be set in the collection unit 200. If the current date is 2019.06.01, the preset database may store the collection status of historical users to be collected before 2019.06.01; where The collection status may include whether the collection is successful for the historical collection user, the promised repayment period of the historical collection user who is not successful in the collection, the latest collection stage for the historical collection user who is not successful, etc.
  • the collection unit 200 can query the preset database to obtain the collection status of users A 1 ⁇ user A 3 .
  • the collection status of user A 1 stored in the preset database can be obtained; if the preset database is If there is no target user whose ID matches the ID of user A 1 , then user A 1 information can be obtained (for example, by interacting with the business system 101, or directly accessing the small and micro loan database), and user A 1 can be added to In the preset database, the collection status of the user A 1 may be uncollected successfully.
  • the collection unit 200 may determine the user collection mode A 1 ⁇ A 3 respectively corresponding to the user according to the state collection user A 1 ⁇ A 3 of the user; wherein the collection mode may include collection call greeting, then surgery, contact Information, transfer method, repayment method consultation, transfer manual code method, etc. For example, if the collection has been performed on user A 1 but the collection has not been successful, and user A 1 promised to repay 2019.06.30 when the last collection call was made, the collection method corresponding to user A 1 can be "2019.06.01 ⁇ No collection call will be made between 2019.06.30.
  • a collection call will be made, and the call will be executed according to the method of breaking promises and strict words"; if the user A 2 has been collected and user a 2 has been completed in the same day payment collection, and can update the preset information database and small micro-credit loans a 2 database users, such as user a 2 can be removed from the default database and can update the small micro-credit loans Database user A 2 ’s historical loan status and credit information; if the collection call has not been performed on user A 3 , the collection method corresponding to user A 3 can be "2019.06.01, the first collection call to user A 3 , and according to the more moderate To execute the collection call".
  • the collection mode corresponding to one or more users to be collected is determined by the collection status of one or more users to be collected, without manual intervention, and the collection dialing method corresponding to each user to be collected can be automatically obtained.
  • the collection method in the above design can be applied to multiple business systems, without the need to determine the corresponding collection of the user to be collected for a single business system In this way, the application range of the collection method can be wider.
  • step 203 The hardware implementation process corresponding to step 203 is described below by taking a server cluster system as an example.
  • FIG. 3a is a schematic diagram of the system architecture of a server cluster system provided by an embodiment of the present invention.
  • the server cluster system may include at least one server, such as server 301, server 302, server 303, and server 304. Wherein, any two servers in the at least one server may be connected, for example, the connection may be realized in a wired manner, or the connection may also be realized in a wireless manner, which is not specifically limited.
  • the collection unit 200 can access the small and micro loan database and download 500 from the small and micro loan database after obtaining the identification of one or more users to be collected (for example, 500 users to be collected) sent by the business system 101 Data of a user to be collected. After the download is complete, the collection unit 200 can compare the data of the 500 users to be collected with the data of the historical collection users in the preset database, and can add users to be collected that do not exist in the preset database to the preset database. Then, the target users to be collected (for example, 1000) that need to be collected are determined from the preset database. Further, the collection unit 200 may divide the data of 100 target users to be collected to obtain multiple subtasks, such as 5 subtasks.
  • the collection unit 200 may divide the data of 100 target users to be collected to obtain multiple subtasks, such as 5 subtasks.
  • the first subtask includes the data of 300 target users to be collected
  • the second The subtasks include the data of 200 target users to be collected
  • the third subtask includes the data of 100 target users to be collected
  • the fourth subtask includes the data of 200 target users to be collected
  • the fifth subtask includes 200 Data of users to be collected by one target.
  • the collection unit 200 may send the first to fifth subtasks to the server cluster system.
  • the server cluster system receives the first to fifth subtasks, it can allocate the first to fifth subtasks to any one or any number of servers 301 to 304 according to the first preset allocation mechanism Server, so that the first to fifth subtasks can be processed by the server cluster system.
  • the first preset distribution mechanism may be a distribution mechanism set by a person skilled in the art based on experience, or may also be a distribution mechanism set by a user according to actual conditions, which is not specifically limited.
  • Table 2 is a schematic table of a first preset allocation mechanism provided by an embodiment of the present invention.
  • Table 2 Schematic of a first preset allocation mechanism
  • Target server (0, 50) Server 301 (50, 120) Server 301, Server 303 (120, 200] Server 302, server 303 (200, 500) Server 302, server 303, server 304 (500, 700] Server 301 ⁇ Server 304
  • the first preset allocation mechanism can include the correspondence between the data volume of the subtask and the target server. If it is determined that the data volume of a subtask is less than or equal to 50M, the subtask can be allocated to the server 301 for processing; if it is determined that the data volume of a subtask is greater than 50M and less than or equal to 120M, the subtask can be allocated to the server 301 and server 303 for processing; if it is determined that the data volume of a subtask is greater than 120M and less than Or equal to 200M, the subtask can be allocated to the server 302 and server 303 for processing; if it is determined that the data volume of a certain subtask is greater than 200M and less than or equal to 500M, the subtask can be allocated to the server 302 and server 303 Processing with the server 304; if it is determined that the data volume of a certain subtask is greater than 500M and less than or equal to 700M, the subtask can be allocated to the servers 301 to 304 for processing.
  • the target server includes multiple target servers, after the multiple target servers complete the processing of their respective subtasks, the processing results of the subtasks corresponding to the multiple target servers can be obtained, and the processing results of the subtasks corresponding to the server cluster system can be combined. result.
  • the preset allocation mechanism allocates the first subtask to any one or more of the servers 302 to 304.
  • the second preset allocation mechanism may be an allocation mechanism set by a person skilled in the art based on experience, or may also be an allocation mechanism set by a user according to actual conditions, and the details are not limited.
  • the execution process of the second preset allocation mechanism can be implemented according to the execution process of the first allocation mechanism, which will not be repeated here.
  • first preset allocation mechanism and the second preset allocation mechanism shown in FIG. 3a can be allocated artificially. For example, if the server cluster system receives the first to fifth subtasks To process the request, the first to fifth subtasks can be assigned to the corresponding target server artificially.
  • FIG 3b is a schematic diagram of the system architecture of another server cluster system provided by an embodiment of the present invention.
  • the server cluster system may include at least one server (server 305, server 306, and server as shown in Figure 3b). 307 and server 308) and a central server 310 that manages at least one server.
  • the central server 310 may be connected to each of the at least one server, so as to realize communication with each server.
  • the collection unit 200 may send the first to fifth subtasks to the central server 310.
  • the central server 310 may store a preset distribution mechanism (such as a first preset distribution mechanism and a second preset distribution mechanism).
  • the central server 310 may communicate with each other through a wired method (such as a network cable or optical fiber). Servers 305 to 308 are connected. In this way, if the central server 310 receives the processing request of the first to fifth subtasks, it can determine the first to fifth subtasks according to the data volume of the first to fifth subtasks and the preset allocation mechanism.
  • the subtasks respectively correspond to the target server; for example, if it is determined that the target server corresponding to the first subtask is the server 305, the central server 310 can send the first subtask to the server 305 via a network cable or optical fiber, and can receive the server via a network cable or optical fiber 305 Process the processing result obtained by the first subtask.
  • the central server 310 detects that the server 305 fails in the process of processing the first subtask, it can determine the backup server (such as server 306 and server 307) corresponding to the server 305 according to the preset allocation mechanism, and the central server 310
  • the first subtask currently processed by the server 305 may be sent to the server 306 and the server 307.
  • the central server 310 may be connected to the servers 305 to 308 in a wireless manner (such as microwave communication, satellite communication). In this way, the central server 310 may transmit the first subtask to the server by sending a signal with a preset frequency. 305, and may receive a signal with a preset frequency that includes the processing result of the first subtask sent by the server 305.
  • a wireless manner such as microwave communication, satellite communication
  • the server 305 can determine whether the current date is a special date (such as a holiday or weekend). If the current date is a special date, it indicates that 300 target users are to be collected Is taking a break, so, the server 305 can set the collection method of 300 target users to be collected as "no collection”; accordingly, if the current date is not a special date, it means that the 300 target users to be collected are working normally. In this way, the server 305 can Set the collection method of 300 target users to be collected as "collection". Setting different collection methods by date can better meet the needs of users and improve user experience.
  • a special date such as a holiday or weekend
  • the collection method can also be verified according to the collection status.
  • the server 305 can query 300 target users to be collected through the preset database whether they made a promise in the historical collection call, if a certain target user to be collected is in the history If you make a promise during the collection call, you can get the repayment date promised by the target user to be collected, and you can update the collection method of the target user to be collected as "Do not make a collection call within the preset repayment date, and repay in the preset When the date arrives but the payment is not repaid, the promise-breaking and strict collection call will be made"; if a target to be collected user has not made a promise in the historical collection call, and the collection status is "the key word was not heard during the historical collection call ", you can update the collection method of the target user to be collected to "make a collection call"; if a
  • the collection status of the target user to be collected is determined based on the collection result of the target user to be collected sent by the operator 300 to the collection unit 200. This process is described in step 206 to step 208, and will not be repeated here. .
  • the collection list can include the contact information and collection methods corresponding to 1000 target users to be collected.
  • step 204 the collection unit 200 sends the collection mode corresponding to one or more users to be collected to the operator.
  • the collection unit 200 may divide one or more users to be collected into a first type of users to be collected and a second type of users to be collected; wherein the risk value of the first type of users to be collected may be greater than The risk value of the second type of users to be collected, where the risk value may be the risk value described in step 201.
  • the collection unit 200 can set the target collection user whose repayment risk value is greater than or equal to 0.5 among 1,000 target users to be collected as the first type of user to be collected, and can set the repayment risk value of the 1,000 target users to be collected to be less than 0.5
  • the target collection user of is regarded as the second type of user to be collected; in this way, the first type of user to be collected has a higher repayment risk value and need to be paid attention to, and the second type of user to be collected has a lower repayment risk value and can be relatively less concerned point.
  • the collection unit 200 may send the information of the first type of users to be collected to the first operator, and may send the information of the second type of users to be collected to the second operator.
  • the first operator can be a Unicom operator
  • the second operator can be a telecommunications operator; since the collection call made by the Unicom operator to the user to be collected can be displayed as a local number, in this way, the risky first
  • the second type of users to be collected is assigned to the Unicom operator, so that the higher-risk users to be collected have a great possibility of answering the phone of the Unicom operator, so that the transfer rate of the collected information is higher, and the collection of the high-risk users is increased. Collection effect.
  • the collection unit 200 may send the collection modes corresponding to the users A 1 to A 3 to the collection unit 200 in the form of a file.
  • the collection methods corresponding to a larger number of users to be collected occupy a large amount of data. Therefore, the users to be collected are corresponded by using files.
  • the collection method is sent to the operator, which can save bandwidth and reduce system resources.
  • a preset bridge structure may be set between the collection unit 200 and the operator 300, and the preset bridge structure can convert the message sent by the collection unit 200 into a message that the operator 300 can parse. Text type.
  • the preset bridge structure can store the message sending mode, message canceling mode, new message mode, query message mode, and message receiving mode; in this way, if the default bridge type results in the message received If it is determined that the message is sent to the Unicom operator, then the message can be converted into a message type that the Unicom operator can parse. If it is determined that the message is a message sent to the telecom operator, then The message can be converted into a message type that the telecom operator can parse.
  • the conversion of different message types can be realized, so that the message can be decoupled from the operator, and the purpose of sending different types of messages to different operators is realized, and the collection is improved. Flexibility.
  • step 205 the operator 300 urges one or more users to be collected.
  • the operator 300 can perform fault tolerance processing in advance; for example, for any target user to be collected among the 1000 target users to be collected, the operator 300 can determine whether the contact information of the target user to be collected is correct, such as whether the contact information is an empty number, whether it has been shut down for a long time, whether the number is incomplete, and so on.
  • a collection call can be made to the target user to be collected; if it is determined that the contact information of the target user to be collected is incorrect, the contact information of the target user to be collected can be sent to the wrong information To the collection unit 200, or the correct contact information of the target user to be collected can be queried from other data sources.
  • the operator 300 can perform collection calls on the target users to be collected.
  • the operator 300 can perform collection on the 1000 target users to be collected in turn after fault tolerance processing is completed for the 1000 target users to be collected.
  • the operator 300 can perform a collection call for the target user to be collected after the fault tolerance processing for a target user to be collected is completed; in other examples, the operator 300 can also use other The method is to make a collection call to the target user to be collected, and the specific is not limited.
  • the call trajectory of the operator 300 for the call to the target user to be collected may include the first to eighth phases, and the first to eighth phases may be the dialing phase, the greeting phase, and the contact determination respectively.
  • the operator 300 can record the collection track of the target user to be collected. For example, if the collection call is not connected, the target user to be collected
  • the collection trajectory of T can be 0; if you only dial to any of the first to third phases (such as the second phase), it means that the target user to be collected has not heard the key information, and the target user T to be collected
  • the trajectory of this collection can be the second phase; if you dial to any of the fourth to eighth phases (such as the sixth phase), it means that the target user to be collected promises to repay, and the target user T to be collected this time
  • the collection trajectory can be a promise.
  • step 206 the operator 300 sends the collection result of the first user to be collected to the collection unit 200.
  • the operator 300 can send the collection result of the target user to be collected to the collection unit 200 in real time, that is, every time the collection of a target user to be collected is completed, the collection result of the target user to be collected can be sent Give the collection unit 200.
  • the collection status corresponding to one or more users to be collected can be determined, that is, the effect achieved by the current collection of one or more users to be collected (For example, the collection information has been successfully transmitted, the user to be collected has confirmed the repayment period, the user to be collected does not answer the phone, the user to be collected hangs up, etc.), so that the subsequent execution can be determined according to the corresponding collection status of one or more users to be collected What kind of collection process; that is, the embodiment of the present invention can quickly plan the subsequent collection method by receiving the collection result of the operator in real time, thereby improving the collection efficiency.
  • the operator 300 can send the collection trajectory of the target user T to be collected to the collection unit 200, that is, can send the call to the collection unit 200 during this collection call. .
  • Step 207 The collection unit 200 updates the collection status of the first user to be collected according to the collection result of the first user to be collected.
  • the collection unit 200 can receive the collection track of the target user T to be collected from the operator 300. If the collection call is not connected, the collection unit 200 can update the collection status of the target user T to be collected in the preset database to "The latest collection call was unsuccessful"; if the phase of the collection call is any of the first to third phases, the collection unit 200 may update the collection status of the target user T to be collected in the preset database to "the latest Call the target user T to be collected and did not hear the key information"; if the phase of the call is any of the fourth to eighth phases (such as the sixth phase), the collection unit 200 can set the target waiting in the preset database The collection status of the collection user T is updated to "the latest collection call the target pending collection user T has committed to repayment".
  • the collection unit 200 can update the optimal collection trajectory stored in the preset database according to the historical collection trajectory and this collection trajectory.
  • the collection trajectory in turn is regarded as the optimal collection trajectory.
  • the dialing phase of the historical collection trajectory is the first phase
  • the dialing phase of the collection trajectory is the sixth phase
  • the optimal trajectory can be the current collection trajectory
  • the collection status of the target user T to be collected can be updated to " In the optimal collection trajectory, the target user T to be collected has promised to repay.”
  • Step 208 Determine whether to perform a second collection for the first user to be collected according to the collection status of the first user to be collected.
  • the target user T to be collected it can be determined whether the target user T to be collected is to be collected twice; if the target user T to be collected is determined to be collected twice, then the target user to be collected can be collected according to the target user T.
  • the collection result of T determines the secondary collection mode corresponding to the target user T to be collected, and step 209a can be executed. If it is determined that the target user T to be collected is not to be collected again, step 209b can be executed.
  • the target user T to be collected can be dialed again; if the status of the collection call corresponding to the target user T to be collected "The collection call in the optimal collection trajectory is connected, but the optimal call trajectory only involves any of the dialing phase, the greeting phase, and the contact determination phase.”
  • This means that the target user T to be collected has not heard the key Information, you can re-dial the target user T to be collected; if the status of the collection call corresponding to the target user T to be collected is "The collection call is connected in the optimal collection trajectory, and the optimal call trajectory involves the fourth stage ⁇
  • the eighth stage means that the target user T to be collected has already listened to the key information, and there is no need to dial the target user T to be collected.
  • the target user T to be collected can be Do not call the target user T to be collected for collection within the promised repayment date; when the promised repayment date of the target user T to be collected is approaching (for example, two days apart), if the target user T to be collected has already repaid, there is no need to call the target The user T to be collected calls for collection.
  • the target user T to be collected does not repay, he can call the target user T to be collected, and the method of the collection call can be "keep promises and gentle words"; in the target user T to be collected After the promised repayment date is reached, if the target user T to be collected has already repaid, there is no need to call the target user T to be collected, and if the target user T to be collected has not repaid, you can call the target user T to be collected , And the way to call for collection can be "breaking promises, stern words" and so on.
  • Step 209a Send the second collection mode corresponding to the first user to be collected to the operator 300.
  • the collection unit 200 may send the operator 300 a secondary collection method corresponding to the target user T to be collected.
  • the operator 300 may perform a secondary collection to the target user T to be collected according to the secondary collection method corresponding to the target user T to be collected.
  • the result of the second collection can be sent to the collection unit 200 in real time; the collection unit 200 can update the target user T to be collected in the preset database according to the result of the second collection.
  • the collection status of the target user T to be collected can be used to determine whether the target user T to be collected should be collected three times; if the target user T to be collected needs to be collected three times, the collection unit 200 can execute step 209a, If the target user T to be collected does not need to be collected three times, the collection unit 200 may execute step 209b.
  • the collection status of the first collection determines whether the user to be collected will perform the second collection, it is possible to avoid the harassment caused by the second collection of the user to be collected when the user to be collected promises to repay, and improves The experience of collecting users; and, by real-time monitoring of the repayment period promised by users to be collected, the users can be collected in time when the users to be collected break their promises, thereby avoiding the evasive behavior of users to be collected and improving the efficiency of collection.
  • Step 209b Send the collection result of the first user to be collected to the business system 101.
  • the collection unit 200 may set the target to be collected
  • the collection result of the user T is sent to the business system 101, so that the business system 101 updates the loan status of the target user T to be collected in the small and micro loan database to "paid".
  • the collection unit 200 may send the collection result of the target user T to be collected to the service system 101, so that the service system 101 makes a collection call to the target user T to be collected in other ways.
  • the business system 101 can also update the loan information of the target user T to be collected in the small and micro-loan loan database according to the collection result of the target user T to be collected. For example, it can update the number of commitment periods of the target user T to be collected for the most recent 12 periods, break The number of promised periods, the call phase corresponding to each period, etc. In this way, the business system 101 can use the data in the small and micro loan database updated in real time to determine the users to be collected, thereby ensuring the real-time and accuracy of the collection.
  • step 210 the collection result of the first user to be collected is stored in the blockchain, and the consensus between the first business system 101 and the operator 300 is reached.
  • the collection unit 200 may also store the historical collection trajectory and the best collection trajectory corresponding to the 1000 target collection users in the blockchain after collecting the 1,000 target collection users.
  • the collection unit 200, the business system 101 and the operator 300 can be controlled in advance to join the blockchain, and after the collection unit 200, the business system 101 and the operator 300 become nodes in the blockchain, they can be used through the collection unit 200
  • the historical collection trajectory and the best collection trajectory corresponding to 1000 target collection users generate transaction information, and send the transaction information to the public network in the blockchain.
  • the business system 101 and the operator 300 can obtain transaction information from the public network, and can sign the transaction information after verifying that the transaction information is correct, so that if the collection unit 200, the business system 101, and the operator 300 verify the transaction If the information reaches a consensus, the transaction information can be stored in the blockchain.
  • legal and trusted collection data can be stored through the blockchain, and in the subsequent When needed, the collection data is obtained through the blockchain, so as to avoid the evasion of repayment by the user to be collected and/or the illegal behavior of the lender, while protecting the interests of the user to be collected and the lender.
  • a collection list sent by at least one business system is received, and the collection list includes the identification of one or more users to be collected; further, the collection list is obtained from a preset database.
  • the collection status of the one or more users to be collected that matches the ID of the user to be collected, and the collection mode corresponding to the one or more users to be collected is determined according to the collection status of the one or more users to be collected, and then Send to the operator the collection method corresponding to the one or more users to be collected, so that the operator can collect the one or more users to be collected according to the collection method corresponding to the one or more users to be collected
  • the collection manner corresponding to the one or more users to be collected is used to indicate the manner of collection to the one or more users to be collected.
  • the collection mode corresponding to one or more users to be collected is determined by the collection status of one or more users to be collected, without manual intervention, and the collection dialing method corresponding to each user to be collected can be automatically obtained.
  • the collection method in the embodiment of the present invention can be applied to multiple business systems without determining the corresponding user to be collected for a single business system
  • the collection method can make the application range of the collection method wider.
  • an embodiment of the present invention also provides a processing device based on distributed batch processing, and the specific content of the device can be implemented with reference to the foregoing method.
  • Fig. 4 is a collection device provided by an embodiment of the present invention.
  • the device includes:
  • the transceiver module 401 is configured to receive a collection list sent by at least one business system, where the collection list includes one or more identities of users to be collected;
  • the obtaining module 402 is configured to obtain the collection status of the one or more users to be collected that matches the identification of the one or more users to be collected from a preset database;
  • the processing module 403 is configured to determine the respective collection methods corresponding to the one or more users to be collected according to the collection status of the one or more users to be collected; the collection methods corresponding to the one or more users to be collected are used to indicate The manner of collecting the one or more users to be collected;
  • the transceiving module 401 is further configured to send the collection method corresponding to the one or more users to be collected to the operator, so that the operator sends the collection method corresponding to the one or more users to be collected to the operator One or more users to be collected perform collection.
  • the transceiver module 401 is further configured to: receive the collection result of the one or more users to be collected from the operator, and update the collection result according to the collection result of the one or more users to be collected. Preset the collection status of the one or more users to be collected stored in the database;
  • the processing module 403 is further configured to: for the first user to be collected among the one or more users to be collected, determine whether to perform the payment on the first user to be collected according to the collection status of the first user to be collected Second collection; if it is determined that the first user to be collected will be collected twice, the second collection method corresponding to the first user to be collected is determined according to the collection result of the first user to be collected, and the operator Sending the second collection manner corresponding to the first user to be collected so that the operator performs a second collection to the first user to be collected according to the second collection manner corresponding to the first user to be collected.
  • processing module 403 is specifically configured to:
  • the collection status of the first to-be-collected user is promised to repay within a preset time limit
  • the first-to-be-collected user fails to repay on time within the preset time limit, it is determined that the first to-be collected
  • the user performs a second collection; if the first user to be collected repays on time within the preset time limit, it is determined not to perform the second collection of the first user to be collected.
  • the transceiver module 401 is specifically configured to:
  • processing module 403 is further configured to:
  • the one or more users to be collected are obtained by screening based on the information of the at least one user from at least one user who has transactions with the one or more business systems;
  • the user information includes any one or more of the following:
  • a collection list sent by at least one business system is received, and the collection list includes one or more identities of users to be collected; further, it is obtained from a preset database
  • the collection status of the one or more users to be collected that matches the identification of the one or more users to be collected, and the one or more users to be collected are determined according to the collection status of the one or more users to be collected Respectively corresponding to the collection method, and then send the collection method corresponding to the one or more users to be collected to the operator, so that the operator can send to the one or more collection methods corresponding to the one or more users to be collected Multiple users to be collected perform collection; wherein, the collection manner corresponding to the one or more users to be collected is used to indicate the manner of collection to the one or more users to be collected.
  • the collection mode corresponding to one or more users to be collected is determined by the collection status of one or more users to be collected, without manual intervention, and the collection dialing method corresponding to each user to be collected can be automatically obtained.
  • the collection method in the embodiment of the present invention can be applied to multiple business systems without determining the corresponding user to be collected for a single business system
  • the collection method can make the application range of the collection method wider.
  • an embodiment of the present invention also provides a computer-readable storage medium, including instructions, which when run on a computer, cause the computer to execute the distributed batch-based The processing method of the processing system.
  • the embodiments of the present invention also provide a computer program product, which when it runs on a computer, causes the computer to execute the processing method based on any one of FIG. 2 or FIG. 2 based on the distributed batch processing system .
  • an embodiment of the present invention provides a terminal device. As shown in FIG. 5, it includes at least one processor 1101 and a memory 1102 connected to the at least one processor.
  • the embodiment of the present invention does not limit the processor.
  • the specific connection medium between 1101 and the memory 1102, the connection between the processor 1101 and the memory 1102 in FIG. 5 is taken as an example.
  • the bus can be divided into address bus, data bus, control bus, etc.
  • the memory 1102 stores instructions that can be executed by at least one processor 1101, and the at least one processor 1101 can execute the steps included in the aforementioned collection method by executing the instructions stored in the memory 1102.
  • the processor 1101 is the control center of the terminal device, which can use various interfaces and lines to connect various parts of the terminal device, and realize data by running or executing instructions stored in the memory 1102 and calling data stored in the memory 1102. deal with.
  • the processor 1101 may include one or more processing units, and the processor 1101 may integrate an application processor and a modem processor.
  • the application processor mainly processes an operating system, a user interface, and an application program.
  • the adjustment processor mainly processes instructions issued by operation and maintenance personnel. It is understandable that the foregoing modem processor may not be integrated into the processor 1101.
  • the processor 1101 and the memory 1102 may be implemented on the same chip, and in some embodiments, they may also be implemented on separate chips.
  • the processor 1101 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic devices, discrete gates or transistors Logic devices and discrete hardware components can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiment of the collection method may be directly embodied as executed and completed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory 1102 can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules.
  • the memory 1102 may include at least one type of storage medium, for example, it may include flash memory, hard disk, multimedia card, card-type memory, random access memory (Random Access Memory, RAM), static random access memory (Static Random Access Memory, SRAM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic memory, disk , CD, etc.
  • the memory 1102 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 1102 in the embodiment of the present invention may also be a circuit or any other device capable of realizing a storage function, for storing program instructions and/or data.
  • the embodiment of the present invention provides a back-end device, as shown in FIG. 6, including at least one processor 1201 and a memory 1202 connected to the at least one processor.
  • the embodiment of the present invention does not limit the processing
  • the specific connection medium between the processor 1201 and the memory 1202 the connection between the processor 1201 and the memory 1202 in FIG. 6 is taken as an example.
  • the bus can be divided into address bus, data bus, control bus, etc.
  • the memory 1202 stores instructions that can be executed by at least one processor 1201, and at least one processor 1201 can execute the steps included in the aforementioned collection method by executing the instructions stored in the memory 1202.
  • the processor 1201 is the control center of the back-end equipment, which can use various interfaces and lines to connect to various parts of the back-end equipment, and by running or executing instructions stored in the memory 1202 and calling data stored in the memory 1202, Realize data processing.
  • the processor 1201 may include one or more processing units, and the processor 1201 may integrate an application processor and a modem processor, where the application processor mainly processes operating systems, application programs, etc., and the modem processor Mainly analyze the received instructions and analyze the received results. It can be understood that the foregoing modem processor may not be integrated into the processor 1201.
  • the processor 1201 and the memory 1202 may be implemented on the same chip, and in some embodiments, they may also be implemented on separate chips.
  • the processor 1201 may be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array or other programmable logic devices, discrete gates or transistors Logic devices and discrete hardware components can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention.
  • the general-purpose processor may be a microprocessor or any conventional processor. The steps of the combined collection method can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the memory 1202 as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules.
  • the memory 1202 may include at least one type of storage medium, for example, may include flash memory, hard disk, multimedia card, card-type memory, random access memory (Random Access Memory, RAM), static random access memory (Static Random Access Memory, SRAM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic memory, disk , CD, etc.
  • the memory 1202 is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.
  • the memory 1202 in the embodiment of the present invention may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.

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)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种催收方法、***及装置，其中方法包括：接收至少一个业务***发送的一个或多个待催收用户的标识，并从预设数据库中获取与一个或多个待催收用户的标识匹配的一个或多个待催收用户的催收状态，进而根据一个或多个催收用户的催收状态确定一个或多个待催收用户对应的催收方式，并通过运营商按照催收方式向一个或多个待催收用户进行催收。该方法通过一个或多个催收用户的催收状态确定一个或多个待催收用户分别对应的催收方式，可以无需人工干预，自动得到每个待催收用户对应的催收拨打方式，从而可以提高催收的效率和准确性。

Description

一种催收方法、***及装置
相关申请的交叉引用
本申请要求在2019年06月11日提交中国专利局、申请号为201910501225.8、申请名称为“一种催收方法、***及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及金融科技(Fintech)技术领域，尤其涉及一种催收方法、***及装置。
背景技术
随着计算机技术的发展，越来越多的技术应用在金融领域，传统金融行业也正在逐步向金融科技(Fintech)转变，然而，由于金融行业的安全性、实时性要求，使得金融科技领域对技术提出了更高的要求。以银行为例，银行中通常会涉及到多种类型的信贷业务，比如小微企业贷、控股企业贷、个体工商贷等；一般来说，若到达还款日期而用户还未还款，或者未到还款日期但用户按期还款的风险值较高，则银行可以向用户进行催收，如此，即可以提醒用户按时还款，又可以获取用户的还款意愿，从而确定针对于该用户的后续催收计划。
人工催收方式是现有较为常用的一种催收方式，举例来说，若50用户(比如小微企业)向银行申请了小微企业贷且超期未还款，则人工催收方式下可以通过人工的方式设置这50名用户对应的催收拨打方式(比如可以包括催收拨打的次数、介绍语、话术等)，进而可以通过运营商按照人工设置的催收拨打方式向这50名用户拨打催收电话。采用该种方式，通常需要较多的人工干预，从而可能使得催收的效率较低；举例来说，针对于50个小微企业中的小微企业A，人工催收方式下均需要根据小微企业A的借款信息、小微企业A的历史借款情况、小微企业A的信用等确定小微企业A还款的风险值高低；进一步地，若确定小微企业A为还款高风险企业，则可以选择较为严厉的话术对小微企业A进行催收，若确定小微企业A为还款低风险企业，则可以选择较为温和的话术对小微企业A进行催收。在上述过程中，人工分析的过程通常需要耗费较长的时间，且可能会出现失误，从而使得催收的效率和准确性均较低。
综上，目前亟需一种催收方法，用以提高催收的效率和准确性。
发明内容
本发明实施例提供一种催收方法、***及装置，用以提高催收的效率和准确性。
第一方面，本发明实施例提供的一种催收方法，所述方法包括：
接收至少一个业务***发送的催收名单，所述催收名单中包括一个或多个待催收用户的标识；进一步地，从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态，并根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式，进而向运营商发送所述一个或多个待催收用 户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收；其中，所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式。
在上述设计中，通过一个或多个催收用户的催收状态确定一个或多个待催收用户分别对应的催收方式，可以无需人工干预，自动得到每个待催收用户对应的催收拨打方式，从而可以提高催收的效率和准确性；且，通过将催收方法与业务***解耦，可以使得上述设计中的催收方法应用于多种业务***，而无需针对于单一的业务***确定待催收用户对应的催收方式，从而可以使得催收方法的应用范围更为广泛。
在一种可能的设计中，所述方法还包括：接收所述运营商发送的所述一个或多个待催收用户的催收结果，并根据所述一个或多个待催收用户的催收结果更新所述预设数据库中存储的所述一个或多个待催收用户的催收状态；进一步地，针对于所述一个或多个待催收用户中的第一待催收用户，根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式，以使所述运营商按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
在上述设计中，通过实时获取一个或多个待催收用户的催收结果，可以确定一个或多个待催收用户对应的催收状态，即目前对一个或多个待催收用户进行催收所达到的效果(比如已成功转达催收方式、待催收用户已确认还款期限、待催收用户未接听电话、待催收用户挂断电话等)，从而可以根据一个或多个待催收用户对应的催收状态决定后续执行何种催收过程；也就是说，上述设计通过实时接收运营商的催收结果，可以快速规划后续的催收方式，从而可以提高催收的效率。
在一种可能的设计中，所述根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收，包括：在所述第一待催收用户的催收状态为承诺预设期限内还款时，若所述第一待催收用户在所述预设期限内未按时还款，则确定对所述第一待催收用户进行二次催收；若所述第一待催收用户在所述预设期限内按时还款，则确定不对所述第一待催收用户进行二次催收。
在上述设计中，通过使用第一次催收的催收状态确定是否对待催收用户执行第二次催收，可以避免待催收用户承诺还款时对待催收用户进行二次催收所造成的骚扰行为，提高待催收用户的体验；且，通过实时监控待催收用户承诺的还款期限，可以在待催收用户打破承诺时及时向待催收用户进行催收，从而可以避免待催收用户的逃避行为，提高催收的效率。
在一种可能的设计中，所述向运营商发送所述一个或多个待催收用户对应的催收方式，包括：将所述一个或多个待催收用户划分为第一类型待催收用户和第二类型待催收用户，所述第一类型待催收用户的风险值大于所述第二类型待催收用户的风险值；进一步地，将所述第一类型待催收用户的信息发送给第一运营商，并将所述第二类型待催收用户的信息发送给第二运营商。
在上述设计中，通过对风险等级不同的待催收用户设置不同的运营商进行催收，可以使得向风险较高的待催收用户和风险较低的待催收用户进行催收均能得到较好的催收效果；举例来说，联通运营商在向待催收用户拨打的催收电话可以显示为本地号码，如此， 若将风险较高的待催收用户分配给联通运营商，则风险较高的待催收用户具有极大地可能性会接听联通运营商的电话，从而使得催收方式的转达率较高，提高向高风险用户进行催收的催收效果。
在一种可能的设计中，所述方法还包括：通过所述一个或多个业务***和所述运营商对所述一个或多个待催收用户的催收结果进行签名，并将签名后的所述一个或多个待催收用户的催收结果存储在区块链上。
在上述设计中，通过将至少一个业务***和运营商签名的一个或多个待催收用户的催收结果存储在区块链中，可以通过区块链存储合法且受信任的催收数据，从而可以在后续需要时通过区块链获取催收数据，避免待催收用户逃避还款的行为和/或提供贷款方的违法行为，同时保护待催收用户和提供贷款方的利益。
在一种可能的设计中，所述一个或多个待催收用户为从与所述一个或多个业务***交易的至少一个用户中根据所述至少一个用户的信息筛选得到的；若所述用户为企业，则所述用户的催收状态包括以下任意一项或任意多项：企业法人的人行信息、企业中控股固定法人的借还款信息、企业的借还款信息、所述企业的基础工商信息。
现有技术通常仅基于企业信息对企业还款的风险值进行评估，然而，企业中的股东、法人等也会对企业还款产生影响，从而使得基于企业信息评估得到的还款风险值不准确；在上述设计中，通过使用企业信息、企业法人信息、企业股东信息综合评估得到企业还款的风险值，可以使得企业的画像较为完善，还款风险值较为准确，从而可以提高催收的准确性。
第二方面，本发明实施例提供的一种催收***，所述催收***包括至少一个业务***，与所述至少一个业务***连接的催收单元和运营商；
所述至少一个业务***，用于分别从与所述至少一个业务***具有交易关系的至少一个用户中确定一个或多个待催收用户，并将所述一个或多个待催收用户的标识发送给催收装置；
所述催收单元，用于接收所述至少一个业务***发送的一个或多个待催收用户的标识，并根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式；所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式；以及，向运营商发送所述一个或多个待催收用户对应的催收方式；
所述运营商，用于按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收。
在一种可能的设计中，所述运营商还用于：根据第一待催收用户对应的催收方式向所述第一待催收用户进行催收后，将所述第一待催收用户的催收结果发送给催收单元；所述催收单元还用于：接收所述运营商发送的所述第一待催收用户的催收结果，并根据所述第一待催收用户的催收结果更新所述预设数据库中存储的所述第一待催收用户的催收状态；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式；所述运营商还用于：按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
第三方面，本发明实施例提供的一种催收装置，所述装置包括：
收发模块，用于接收至少一个业务***发送的催收名单，所述催收名单中包括一个或 多个待催收用户的标识；
获取模块，用于从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态；
处理模块，用于根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式；所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式；
所述收发模块，还用于向运营商发送所述一个或多个待催收用户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收。
在一种可能的设计中，所述收发模块还用于：接收所述运营商发送的所述一个或多个待催收用户的催收结果，并根据所述一个或多个待催收用户的催收结果更新所述预设数据库中存储的所述一个或多个待催收用户的催收状态；所述处理模块还用于：针对于所述一个或多个待催收用户中的第一待催收用户，根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式，以使所述运营商按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
在一种可能的设计中，所述处理模块具体用于：在所述第一待催收用户的催收状态为承诺预设期限内还款时，若所述第一待催收用户在所述预设期限内未按时还款，则确定对所述第一待催收用户进行二次催收；若所述第一待催收用户在所述预设期限内按时还款，则确定不对所述第一待催收用户进行二次催收。
在一种可能的设计中，所述收发模块具体用于：将所述一个或多个待催收用户划分为第一类型待催收用户和第二类型待催收用户，所述第一类型待催收用户的风险值大于所述第二类型待催收用户的风险值；进一步地，将所述第一类型待催收用户的信息发送给第一运营商，并将所述第二类型待催收用户的信息发送给第二运营商。
在一种可能的设计中，所述处理模块还用于：通过所述一个或多个业务***和所述运营商对所述一个或多个待催收用户的催收结果进行签名，并将签名后的所述一个或多个待催收用户的催收结果存储在区块链上。
在一种可能的设计中，所述一个或多个待催收用户为从与所述一个或多个业务***交易的至少一个用户中根据所述至少一个用户的信息筛选得到的；若所述用户为企业，则所述用户的信息包括以下任意一项或任意多项：企业法人的人行信息、企业中控股固定法人的借还款信息、企业的借还款信息、所述企业的基础工商信息。
第四方面，本发明实施例提供的一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如上述第一或第二方面任一所述的催收方法。
第五方面，本发明实施例提供的一种计算机程序产品，当其在计算机上运行时，使得计算机执行如上述第一或第二方面任一所述的催收方法。
本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的 附图作简要介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例提供的一种催收***的***架构示意图；
图2为本发明实施例提供的一种催收方法对应的流程示意图；
图3a为本发明实施例提供的一种服务器集群***的***架构示意图；
图3b为本发明实施例提供的另一种服务器集群***的***架构示意图；
图4为本发明实施例提供的一种催收装置的结构示意图；
图5为本发明实施例提供的一种终端设备的结构示意图；
图6为本发明实施例提供的一种后端设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明作进一步地详细描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。
金融科技(Fintech)是指将信息技术融入金融领域后，为金融领域带来的一种新的创新科技，通过使用先进的信息技术辅助实现金融作业、交易执行以及金融***改进，可以提升金融***的处理效率、业务规模，并可以降低成本和金融风险。一般来说，金融科技领域通常会涉及到大量的数据，比如信贷部门的贷款数据、销售部门的购卡数据、运维部门的维修数据等，如何采用科技的手段从大量的数据中挖掘出金融领域所需要的特征，一直是金融科技领域追求的目标。
以银行中的信贷部门为例，信贷部门的业务量通常是非常巨大的，比如，信贷部门的信贷数据库中可以存储着上万条甚至数十万条的历史贷款数据。在这种情况下，信贷部门的工作人员通常可以按照预设周期(比如一天、一个周、一个月)对这些历史贷款数据进行分析，若发现存在某一条贷款数据超过时限要求，或者发现某一条信贷数据快要到期而用户还未还款，则可以向该条信贷数据对应的用户进行催收。然而，由于历史贷款数据的数据量非常大，导致待催款的用户较多，因此，采用何种方式对大量的待催款用户进行催收并保证得到较好的催收效果，一直是金融科技领域需要解决的一个问题。
在一种可能的实现方式中，可以针对于每个产品设计一种催收方法，比如，对于小微贷产品设计一种与小微贷产品耦合的催收方法a 1，催收方法a 1中可以包括小微贷产品的一些特性，从而催收方法a 1可以用于对于贷款小微贷的企业进行催收；相应地，对于个体工商贷产品设计另一种与个体工商贷产品耦合的催收方法a 2，催收方法a 2中可以包括个体工商贷产品的一些特性，从而催收方法a 2可以用于对于贷款个体工商贷的个体户进行催收。以催收方法a 1为例，一般来说，当需要向贷款小微贷产品的待催收用户进行催收时，可以通过催收方法a 1来分析确定所有贷款小微贷产品的用户中哪些用户需要进行催收，从而将需要进行催收的待催收用户整理成催收名单，并将催收名单发送给运营商；如此，运营商可以依次向催收名单中的待催收用户拨打催收电话。由于催收方法a 1为与小微贷产品耦合的催收方法，从而运营商在拨打催收电话时，可以如下的催收方式向每个待催收用户进行催收：“贷款小微贷的用户***，您好，由于您的贷款快要到期(或已到期)，请您尽快进 行还款”。
在上述实现方式中，催收方法需要与产品进行耦合，这会导致不同业务***对应的不同产品无法复用另一产品的催收方法，造成催收方法的可移植性较差，无形中增加了开发催收方法的成本。
基于此，本发明实施例提供了一种催收方法，用于提高催收的效率和准确性。
图1为本发明实施例提供的一种催收***的***架构示意图，如图1所示，该***可以包括至少一个业务***(比如图1所示意出的业务***101、业务***102和业务***103)、与至少一个业务***连接的催收单元200和运营商300。其中，至少一个业务***可以通过有线方式与催收单元200连接，或者也可以通过无线方式与催收单元200连接，具体不作限定。
以信贷部门为例，至少一个业务***可以是指信贷部门中的至少一个业务组，至少一个业务组中的每个业务组可以开发一种或多种贷款产品，并可以管理信贷部门中与本业务组开发的一种或多种贷款产品相关的交易。举例来说，业务***101开发了小微贷产品，则若用户1～用户100向信贷部门申请并成功贷款了小微贷产品，则业务***101可以将用户1～用户100的贷款信息、基本信息和信用信息等存储在业务***101内部设置的小微贷贷款数据库中，从而可以基于小微贷贷款数据库记录用户1～用户100的还款行为，比如用户1～用户100的还款期限、历史还款准时率、信用评价等。
若业务***101开发了小微贷产品，业务***102开发了个体工商贷产品，业务***103开发了私营企业贷产品，则在具体实施中，业务***101～业务***103可以分别将需要进行催收的小微贷产品用户、个体工商贷产品用户和私营企业贷产品用户发送给催收单元200。相应地，催收单元200可以根据小微贷产品用户当前的催收状态确定小微贷产品用户的催收方式，根据个体工商贷产品用户当前的催收状态确定个体工商贷产品用户的催收方式，根据私营企业贷产品用户当前的催收状态确定私营企业贷产品用户的催收方式；比如，若某一小微贷产品用户已还款，则无需向该小微贷产品用户进行催收，若确定某一小微贷产品用户已到还款期限而信用较低，则可以采用较为严厉的话术向该小微贷产品用户进行催收。进一步地，催收单元200可以将小微贷产品用户的催收方式、个体工商贷产品用户的催收方式和私营企业贷产品用户的催收方式(包括联系信息)发送给运营商，以使运营商向小微贷产品用户、个体工商贷产品用户和私营企业贷产品用户分别拨打催收电话，实现业务***101、业务***102和业务***103分别对小微贷产品、个体工商贷产品和私营企业贷产品的管理。
下面以向业务***101管理的贷款小微贷产品的用户进行催收为例描述本发明实施例提供的催收方法，可以理解地，向其它业务***管理的贷款其它产品的用户进行催收的过程可以参照该方法进行实现，具体不再赘述。
基于图1所示意的催收***的***架构，图2为本发明实施例提供的一种催收方法对应的流程示意图，该方法包括：
步骤201，业务***101确定一个或多个待催收用户。
本发明实施例中，若用户向业务部门101申请小微贷产品，则业务部门101可以在向该用户批准贷款的同时将该用户的数据存储在小微贷贷款数据库中，小微贷贷款数据库可以用于存储向业务部门101进行小微贷贷款但暂未还款的用户的数据。其中，用户的数据可以包括用户的基本信息、贷款信息、信用信息等，基本信息可以包括用户的姓名、身份证 号码、联系方式、家庭住址、邮箱地址等，贷款信息可以包括用户贷款的金额、贷款的时长、还款方式等，信用信息可以包括用户的历史贷款信息、其它业务***(比如业务***102和/或业务***103)对用户的评价信息等。
表1为本发明实施例提供的一种可能的小微贷贷款数据库的示意表。
表1：一种可能的小微贷贷款数据库的示意
用户 姓名 身份证号 历史信用 还款期限 贷款金额
用户A 1 张三 X 1 优 2019.06.01 300万
用户A 2 李四 X 2 低 2019.05.39 15万
用户A 3 王五 X 3 良 2019.06.03 1000万
如表1所示，小微贷贷款数据库中可以存储有多个用户的基本信息和信用信息，以用户A 3为例，用户A 3的姓名可以为王五，身份证号可以为X 3，历史信用可以为良；相应地，小微贷贷款数据库中还可以存储有多个用户贷款的金额和还款日期，比如，用户A 3贷款的金额可以为1000万，还款日期可以为2019.06.03。
需要说明的是，表1仅是一种示例性的简单说明，其所列举的信息仅是为了便于说明方案，并不构成对方案的限定，可以理解地，小微贷贷款数据库中也可以包括其它信息，比如用户的性别、年龄等，具体不作限定。
具体实施中，业务***101可以获取小微贷贷款数据库中存储的贷款了小微贷产品的所有用户，针对于所有用户中的每一个用户，若确定当前日期已超过或到达该用户的贷款期限而该用户还未还款，则可以确定该用户为一个待催收用户；若确定当前日期临近该用户的贷款期限而该用户还未还款，则可以根据该用户的贷款金额、信用信息等确定该用户是否为待催收用户。比如，若当前日期为2019.06.01，则业务***101可以根据小微贷贷款数据库中用户A 1～用户A 3的还款期限，选择还款期限小于当前日期的用户A 1和还款期限等于当前日期的用户A 2作为待催收用户；针对于还款期限距离当前日期2天的用户A 3，业务***101可以通过分析用户A 3的信用、还款期限、贷款金额评估得到用户A 3的还款风险，一般来说，用户的信用越低、还款期限越近、贷款金额越高，则用户的还款风险越高；根据表1所示，由于用户A 3的贷款金额较大，还款期限与当前日期相差较近，且信用一般，因此，信贷部门也可以将用户A 3作为一个待催收用户。
在一个示例中，当用户为小微企业时，业务***101可以根据小微企业法人的人行信息、企业中控股固定法人的借还款信息、企业的借还款信息、企业的基础工商信息等综合确定小微企业的还款风险值。其中，法人的人行信息可以包括法人的居住地地址、邮件地址、民族、学历、紧急联系人以及关系、手机号码、家庭号码、办公号码、绑卡银行以及对法人进行贷前分析评估得到的风险等级等；举例来说，法人的风险等级可以基于法人在信贷部门的12期内的借款还款情况、承诺还款情况、打破承诺情况、历史催收拨打情况、企业性质等评估得到法人的风险等级，比如，若当前日期时企业所在的行业出现高风险事件，则法人的风险等级也会相应提高。企业中控股固定法人的借还款信息可以包括股东在信贷部门中的贷款次数、贷款金额、贷款时间、相应地还款情况、流水账数据等。企业的借还款信息可以包括企业欠款的时长、欠款金额、还款总期数、延期的期数、是否存在主动还款经历、账户年龄、是否为还款首期、还款首期是否逾期、最近正常还款日期、贷款额度值和风险等级等。企业的基础工商信息可以包括企业名称、企业地址、企业性质、法 人职务等。
一般来说，现有技术通常仅基于企业信息对企业还款的风险值进行评估，然而，企业中的股东、法人等也会对企业还款产生影响，这会导致基于企业信息评估得到的还款风险值不准确；本发明实施例中，通过使用企业信息、企业法人信息、企业股东信息综合评估得到企业还款的风险值，可以使得企业的画像较为完善，还款风险值较为准确，从而可以提高催收的准确性。
通过上述评估方式，业务***101可以确定用户A 1～用户A 3分别为3个待催收用户。
步骤202，业务***101将一个或多个待催收用户的标识发送给催收单元200。
此处，业务***101可以将用户A 1～用户A 3的标识发送给催收单元200。以用户A 1为例，用户A 1的标识可以是指用户A 1的联系方式，或者也可以是指用户A 1的身份证号码，或者还可以是指用户A 1的联系方式与身份证号码的组合，具体不作限定。
步骤203，催收单元200确定一个或多个待催收用户分别对应的催收方式。
在一种可能的实现方式中，催收单元200中可以设置有预设数据库，若当前日期为2019.06.01，则预设数据库中可以存储有2019.06.01之前的历史待催收用户的催收状态；其中，催收状态可以包括历史待催收用户是否催收成功、催收未成功的历史催收用户的承诺还款期限、对催收未成功的历史催收用户最近一次催收的阶段等。
相应地，催收单元200在接收到业务***101发送的用户A 1～用户A 3的标识后，可以查询预设数据库，获取用户A 1～用户A 3的催收状态。具体地说，以用户A 1为例，若预设数据库中存在标识与用户A 1的标识匹配的目标用户，则可以获取预设数据库中存储的用户A 1的催收状态；若预设数据库中不存在标识与用户A 1的标识匹配的目标用户，则可以获取用户A 1的信息(比如通过与业务***101交互获取，或者直接访问小微贷贷款数据库)，并可以将用户A 1添加在预设数据库中，用户A 1的催收状态可以为未催收成功。
进一步地，催收单元200可以根据用户A 1～用户A 3的催收状态确定用户A 1～用户A 3分别对应的催收方式；其中，催收方式可以包括进行催收拨打的问候语、话术、联系人信息、转达方式、还款方式咨询、转接人工码方式等。举例来说，若已对用户A 1执行过催收但未催收成功，且用户A 1在最近一次催收拨打时承诺2019.06.30还款，则用户A 1对应的催收方式可以为“2019.06.01～2019.06.30之间不进行催收拨打，若2019.06.30时还未还款，则进行催收拨打，且根据打破承诺的方式以及严厉的话术执行催收拨打”；若已对用户A 2执行过催收且用户A 2已在催收当天完成还款，且可以更新预设数据库和小微贷贷款数据库中用户A 2的信息，比如可以将用户A 2从预设数据库中删除，并可以更新小微贷贷款数据库用户A 2的历史贷款情况和信用信息；若未对用户A 3执行过催收拨打，则用户A 3对应的催收方式可以为“2019.06.01对用户A 3进行首次催收拨打，且根据较为温和的方式执行催收拨打”。
本发明实施例中，通过一个或多个催收用户的催收状态确定一个或多个待催收用户分别对应的催收方式，可以无需人工干预，自动得到每个待催收用户对应的催收拨打方式，从而可以提高催收的效率和准确性；且，通过将催收方法与业务***解耦，可以使得上述设计中的催收方法应用于多种业务***，而无需针对于单一的业务***确定待催收用户对应的催收方式，从而可以使得催收方法的应用范围更为广泛。
下面以服务器集群***为例描述步骤203对应的硬件实现过程。
图3a为本发明实施例提供的一种服务器集群***的***架构示意图，如图3a所示，服务器集群***中可以包括至少一个服务器，比如服务器301、服务器302、服务器303和服 务器304。其中，至少一个服务器中的任意两个服务器之间可以连接，比如可以通过有线方式实现连接，或者也可以通过无线方式实现连接，具体不作限定。
具体实施中，催收单元200在获取到业务***101发送的一个或多个待催收用户(比如500个待催收用户)的标识后，可以访问小微贷贷款数据库，从小微贷贷款数据库中下载500个待催收用户的数据。当下载完成后，催收单元200可以对比这500个待催收用户的数据和预设数据库中的历史催收用户的数据，并可以将预设数据库中不存在的待催收用户添加到预设数据库中，进而从预设数据库中确定出需要进行催收的目标待催收用户(比如1000个)。进一步地，催收单元200可以对100个目标待催收用户的数据进行分片，得到多个子任务，比如划分得到5个子任务，第一个子任务中包括300个目标待催收用户的数据、第二个子任务中包括200个目标待催收用户的数据，第三个子任务中包括100个目标待催收用户的数据、第四个子任务中包括200个目标待催收用户的数据，第五个子任务中包括200个目标待催收用户的数据。
进一步地，在分片成功后，催收单元200可以将第一～第五子任务发送给服务器集群***。相应地，若服务器集群***接收到第一～第五子任务，则可以按照第一预设分配机制将第一～第五子任务分配给服务器301～服务器304中的任意一个服务器或任意多个服务器，以使第一～第五子任务可以被服务器集群***所处理。其中，第一预设分配机制可以为本领域技术人员根据经验设置的分配机制，或者也可以为用户根据实际情况设置的分配机制，具体不作限定。在一个示例中，表2为本发明实施例提供的一种第一预设分配机制的示意表。
表2：一种第一预设分配机制的示意
子任务的数据量(M) 目标服务器
(0，50] 服务器301
(50，120] 服务器301、服务器303
(120，200] 服务器302、服务器303
(200，500] 服务器302、服务器303、服务器304
(500，700] 服务器301～服务器304
如表2所示，第一预设分配机制中可以包括子任务的数据量与目标服务器的对应关系，若确定某一子任务的数据量小于或等于50M，则可以将该子任务分配给服务器301进行处理；若确定某一子任务的数据量大于50M且小于或等于120M，则可以将该子任务分配给服务器301和服务器303进行处理；若确定某一子任务的数据量大于120M且小于或等于200M，则可以将该子任务分配给服务器302和服务器303进行处理；若确定某一子任务的数据量大于200M且小于或等于500M，则可以将该子任务分配给服务器302、服务器303和服务器304进行处理；若确定某一子任务的数据量大于500M且小于或等于700M，则可以将该子任务分配给服务器301～服务器304进行处理。相应地，若目标服务器包括多个，则可以在多个目标服务器完成各自子任务的处理后，获取多个目标服务器分别对应的子任务的处理结果，合并得到服务器集群***对应的子任务的处理结果。
进一步地，以服务器301处理第一子任务为例，若在服务器301处理第一子任务的过程中，由于服务器301发生故障而导致第一子任务无法继续被处理，此时，可以按照第二预设分配机制将第一子任务分配给服务器302～服务器304中的任意一个或任意多个服务器。 其中，第二预设分配机制可以为本领域技术人员根据经验设置的分配机制，或者也可以为用户根据实际情况设置的分配机制，具体不作限定。本发明实施例中，第二预设分配机制的执行过程可以按照第一分配机制的执行过程进行实现，此处不再赘述。
需要说明的是，图3a所示意的第一预设分配机制和第二预设分配机制可以是通过人为来实现分配的，比如，若服务器集群***接收到第一子任务～第五子任务的处理请求，则可以通过人为的方式将第一子任务～第五子任务分配给对应的目标服务器。
图3b为本发明实施例提供的另一种服务器集群***的***架构示意图，如图3b所示，服务器集群***中可以包括至少一个服务器(如图3b所示意出的服务器305、服务器306、服务器307和服务器308)和管理至少一个服务器的中心服务器310。其中，中心服务器310可以与至少一个服务器中的每个服务器连接，从而实现与每个服务器的通信。
具体实施中，催收单元200若成功将任务划分为第一～第五子任务，则可以将第一～第五子任务发送给中心服务器310。相应地，中心服务器310中可以存储有预设分配机制(比如第一预设分配机制和第二预设分配机制)，在一个示例中，中心服务器310可以通过有线方式(比如网线、光纤)与服务器305～服务器308连接，如此，中心服务器310若接收到第一～第五子任务的处理请求，则可以根据第一～第五子任务的数据量和预设分配机制确定第一～第五子任务分别对应的目标服务器；比如若确定第一子任务对应的目标服务器为服务器305，则中心服务器310可以通过网线或光纤将第一子任务发送给服务器305，并可以通过网线或光纤接收服务器305处理第一子任务得到的处理结果。相应地，若中心服务器310检测到服务器305在处理第一子任务的过程中发生故障，则可以根据预设分配机制确定服务器305对应的备用服务器(比如服务器306和服务器307)，则中心服务器310可以将服务器305当前处理的第一子任务发送给服务器306和服务器307。在另一个示例中，中心服务器310可以通过无线方式(比如微波通信、卫星通信)与服务器305～服务器308连接，如此，中心服务器310可以通过发送预设频率的信号将第一子任务传输给服务器305，并可以接收服务器305发送的包括第一子任务的处理结果的预设频率的信号。
本发明实施例中，以服务器305执行第一子任务的过程为例，服务器305可以确定当前日期是否为特殊日期(比如节假日、周末)，若当前日期为特殊日期，说明300个目标待催收用户正在休息，如此，服务器305可以设置300个目标待催收用户的催收方式为“不进行催收”；相应地，若当前日期并非特殊日期，说明300个目标待催收用户正常工作，如此，服务器305可以设置300个目标待催收用户的催收方式为“进行催收”。通过日期设置不同的催收方式，可以更加满足用户的需要，提高用户的体验。
本发明实施例中，在确定目标待催收用户的催收方式后，还可以根据催收状态对催收方式进行校验。仍以服务器305执行第一子任务的过程为例，具体实施中，服务器305可以通过预设数据库查询300个目标待催收用户是否在历史催收拨打中作出承诺，若某一目标待催收用户在历史催收拨打中作出承诺，则可以获取该目标待催收用户承诺的还款日期，并可以更新该目标待催收用户的催收方式为“在预设还款日期内不进行催收拨打，在预设还款日期到达而未还款时进行打破承诺且话术严厉的催收拨打”；若某一目标待催收用户在历史催收拨打中未作出承诺，且其催收状态为“历史催收拨打时未听到关键词”，则可以更新该目标待催收用户的催收方式为“进行催收拨打”；若某一目标待催收用户在历史催收拨打中未作出承诺，且其催收状态为“历史催收拨打时已听到关键词”，则可以更新该目标待催收用户的催收方式为“在短时间内不再进行催收拨打”。
需要说明的是，目标待催收用户的催收状态为根据运营商300向催收单元200发送的目标待催收用户的催收结果确定的，该过程在步骤206～步骤208中进行描述，此处不再赘述。
通过图3a或图3b中的处理过程，若服务器集群***中的一个或多个服务器分别设置好了1000个目标待催收用户的催收方式，进一步地，可以将这1000个目标待催收用户进行合并，得到催收清单；其中，催收清单中可以包括1000个目标待催收用户对应的联系方式和催收方式。
步骤204，催收单元200将一个或多个待催收用户分别对应的催收方式发送给运营商。
在一种可能的实现方式中，催收单元200可以将一个或多个待催收用户划分为第一类型待催收用户和第二类型待催收用户；其中，第一类型待催收用户的风险值可以大于第二类型待催收用户的风险值，此处的风险值可以为步骤201中描述的风险值。比如，催收单元200可以将1000个目标待催收用户中还款风险值大于或等于0.5的目标催收用户作为第一类型待催收用户，并可以将1000个目标待催收用户中还款风险值小于0.5的目标催收用户作为第二类型待催收用户；如此，第一类型待催收用户的还款风险值较高，需要重点关注，第二类型待催收用户的还款风险值较低，关注可以相对少点。
进一步地，催收单元200可以将第一类型待催收用户的信息发送给第一运营商，并可以将第二类型待催收用户的信息发送给第二运营商。其中，第一运营商可以为联通运营商，第二运营商可以为电信运营商；由于联通运营商在向待催收用户拨打的催收电话可以显示为本地号码，如此，通过将风险较高的第二类型待催收用户分配给联通运营商，使得风险较高的待催收用户具有极大地可能性会接听联通运营商的电话，从而使得催收信息的转达率较高，提高向高风险用户进行催收的催收效果。
本发明实施例中，通过对风险等级不同的待催收用户设置不同的运营商进行催收，可以使得向风险较高的待催收用户和风险较低的待催收用户进行催收均能得到较好的催收效果。
在一个示例中，催收单元200可以以文件的形式将用户A 1～用户A 3分别对应的催收方式发送给催收单元200。如此，由于第一次确定待催收用户时待催收用户可能较多，从而导致数量较多的待催收用户对应的催收方式占用较多的数据量，因此，通过使用文件的方式将待催收用户对应的催收方式发送给运营商，可以节省带宽、减少***资源。
在一种可能的实现方式中，催收单元200和运营商300之间可以设置有一个预设桥结构，该预设桥结构可以将催收单元200发送的报文转换为运营商300可以解析的报文类型。相应地，预设桥结构中可以存储有报文发送方式、报文取消方式、新增报文方式、查询报文方式和接收报文方式；如此，若预设桥类结果接收到报文后，若确定该报文为发送给联通运营商的报文，则可以将该报文转换为联通运营商可以解析的报文类型，若确定该报文为发送给电信运营商的报文，则可以将该报文转换为电信运营商可以解析的报文类型。
本发明实施例中，通过设置预设桥结构，可以实现对不同报文类型的转换，从而可以将报文与运营商解耦，实现向不同运营商发送不同类型的报文的目的，提高催收的灵活性。
步骤205，运营商300向一个或多个待催收用户进行催收。
具体实施中，运营商300在接收到1000个目标待催收用户的联系方式后，可以预先进行容错处理；举例来说，针对于1000个目标待催收用户中的任一目标待催收用户，运营商300可以判断该目标待催收用户的联系方式是否正确，比如联系方式是否为空号、是否停机许久、是否号码不全等。若确定目标待催收用户的联系方式正确，则可以对该目标待催 收用户进行催收拨打；若确定目标待催收用户的联系方式不正确，则可以将该目标待催收用户的联系方式错误的信息发送给催收单元200，或者也可以从其它数据源中查询该目标待催收用户的正确联系方式。
运营商300对目标待催收用户进行催收拨打的方式可以有多种，在一个示例中，运营商300可以在对1000个目标待催收用户容错处理完成后，依次对1000个目标待催收用户执行催收拨打；在另一个示例中，运营商300可以在对某一个目标待催收用户容错处理完成后，即对该目标待催收用户执行催收拨打；在其它的示例中，运营商300还可以采用其他的方式对目标待催收用户进行催收拨打，具体不作限定。
在一种可能的实现方式中，运营商300对目标待催收用户进行催收拨打的拨打轨迹可以包括第一～第八阶段，第一～第八阶段分别可以为拨号阶段、问候阶段、联系人确定阶段、贷款信息传达阶段、还款确认阶段、承诺还款阶段、了解还款方式阶段、转接人工码阶段。其中，若拨打到第一阶段～第三阶段，则对应目标待催收用户未听到关键信息，若拨打到第四阶段～第八阶段，则对应目标待催收用户已听到关键信息。
以运营商300对目标待催收用户T进行催收拨打为例，具体实施中，运营商300可以记录对目标待催收用户进行催收拨打的催收轨迹，比如若催收拨打未接通，则目标待催收用户T的此次催收轨迹可以为0；若仅拨打到第一～第三阶段中的任一阶段(比如第二阶段)，则说明目标待催收用户还未听到关键信息，目标待催收用户T的此次催收轨迹可以为第二阶段；若拨打到第四～第八阶段中的任一阶段(比如第六阶段)，则说明目标待催收用户承诺还款，目标待催收用户T的此次催收轨迹可以为作出承诺。
步骤206，运营商300将第一待催收用户的催收结果发送给催收单元200。
具体实施中，运营商300可以通过实时的方式将目标待催收用户的催收结果发送给催收单元200，即每次对一个目标待催收用户催收完成，则可以将该目标待催收用户的催收结果发送给催收单元200。
本发明实施例中，通过实时获取一个或多个待催收用户的催收结果，可以确定一个或多个待催收用户对应的催收状态，即目前对一个或多个待催收用户进行催收所达到的效果(比如已成功转达催收信息、待催收用户已确认还款期限、待催收用户未接听电话、待催收用户挂断电话等)，从而可以根据一个或多个待催收用户对应的催收状态决定后续执行何种催收过程；也就是说，本发明实施例通过实时接收运营商的催收结果，可以快速规划后续的催收方式，从而可以提高催收的效率。
以目标待催收用户T为例，运营商300可以将目标待催收用户T此次的催收轨迹发送给催收单元200，即可以将此次催收拨打的过程中所拨打到的阶段发送给催收单元200。
步骤207，催收单元200根据第一待催收用户的催收结果更新第一待催收用户的催收状态。
具体实施中，催收单元200可以接收运营商300发送的目标待催收用户T的催收轨迹，若催收拨打未接通，则催收单元200可以将预设数据库中目标待催收用户T的催收状态更新为“最新一次催收拨打未成功”；若催收拨打的阶段为第一～第三阶段中的任一阶段，则催收单元200可以将预设数据库中目标待催收用户T的催收状态更新为“最新一次催收拨打目标待催收用户T未听到关键信息”；若催收拨打的阶段为第四～第八阶段中的任一阶段(比如第六阶段)，则催收单元200可以将预设数据库中目标待催收用户T的催收状态更新为“最新一次催收拨打目标待催收用户T已承诺还款”。
进一步地，催收单元200可以根据历史催收轨迹和此次催收轨迹更新预设数据库中存储的最优催收轨迹，在一个示例中，可以将历史收轨迹和此次催收轨迹中拨打阶段最靠后的依次催收轨迹作为最优催收轨迹。比如，历史催收轨迹的拨打阶段为第一阶段，而此次催收轨迹的拨打阶段为第六阶段，而最优轨迹可以为此次催收轨迹，且目标待催收用户T的催收状态可以更新为“最优催收轨迹中目标待催收用户T已承诺还款”。
步骤208，根据第一待催收用户的催收状态确定是否对第一待催收用户进行二次催收。
本发明实施例中，可以根据目标待催收用户T的催收状态，确定是否对目标待催收用户T进行二次催收；若确定对目标待催收用户T进行二次催收，则可以根据目标待催收用户T的催收结果确定目标待催收用户T对应的二次催收方式，并可以执行步骤209a，若确定对目标待催收用户T不进行二次催收，则可以执行步骤209b。
举例来说，若目标待催收用户T对应的催收拨打的状态为“催收拨打一直未接通”，则可以对目标待催收用户T重新拨打一次；若目标待催收用户T对应的催收拨打的状态为“最优催收轨迹中催收拨打已接通，但最优拨打轨迹仅涉及到拨号阶段、问候阶段、联系人确定阶段中的任意多项”，则说明目标待催收用户T还未听到关键信息，则可以对目标待催收用户T进行重新拨打；若目标待催收用户T对应的催收拨打的状态为“最优催收轨迹中催收拨打已接通，且最优拨打轨迹涉及到第四阶段～第八阶段”，则说明目标待催收用户T已收听到关键信息，已无需对目标待催收用户T进行重新拨打。
在一个示例中，若目标待催收用户T对应的催收拨打的状态为“最优催收轨迹中催收拨打已接通，且最优拨打轨迹涉及到第六阶段”，则可以在目标待催收用户T承诺的还款日期内不向目标待催收用户T催收拨打；在目标待催收用户T承诺的还款日期临近(比如间隔两天)，若目标待催收用户T已还款，则可以无需向目标待催收用户T催收拨打，若目标待催收用户T未还款，则可以向目标待催收用户T催收拨打，且催收拨打的方式可以为“保持承诺、温和话术”；在目标待催收用户T承诺的还款日期到达后，若目标待催收用户T已还款，则可以无需向目标待催收用户T催收拨打，若目标待催收用户T未还款，则可以向目标待催收用户T催收拨打，且催收拨打的方式可以为“打破承诺、严厉话术”等。
步骤209a，将第一待催收用户对应的二次催收方式发送给运营商300。
若确定向目标待催收用户T进行催收拨打，则催收单元200可以向运营商300发送目标待催收用户T对应的二次催收方式。相应地，运营商300可以按照目标待催收用户T对应的二次催收方式向目标待催收用户进行二次催收。
相应地，运营商300向目标待催收用户T进行二次催收后，可以将二次催收结果实时发送给催收单元200；催收单元200可以根据二次催收结果更新预设数据库中目标待催收用户T对应的催收状态，并可以根据目标待催收用户T对应的催收状态确定是否对目标待催收用户T进行三次催收；若需要对目标待催收用户T进行三次催收，则催收单元200可以执行步骤209a，若无需对目标待催收用户T进行三次催收，则催收单元200可以执行步骤209b。
本发明实施例中，通过使用第一次催收的催收状态确定是否对待催收用户执行第二次催收，可以避免待催收用户承诺还款时对待催收用户进行二次催收所造成的骚扰行为，提高待催收用户的体验；且，通过实时监控待催收用户承诺的还款期限，可以在待催收用户打破承诺时及时向待催收用户进行催收，从而可以避免待催收用户的逃避行为，提高催收的效率。
步骤209b，将第一待催收用户的催收结果发送给业务***101。
在一个示例中，当催收单元200确定对目标待催收用户的催收结果已达到最好的预期效果(比如目标待催收用户T已按照承诺期限还款，)时，催收单元200可以将目标待催收用户T的催收结果发送给业务***101，以使业务***101将小微贷款数据库中目标待催收用户T的贷款状态更新为“已还款”。在另一个示例中，当催收单元200确定对目标待催收用户的催收结果已达到最坏的预期效果(比如目标待催收用户T已多次承诺还款，但始终未还款；或者目标待催收用户T多次不接听催收电话)时，催收单元200可以将目标待催收用户T的催收结果发送给业务***101，以使业务***101通过其它方式向目标待催收用户T进行催收拨打。
相应地，业务***101还可以根据目标待催收用户T的催收结果更新小微贷贷款数据库中目标待催收用户T的贷款信息，比如可以更新目标待催收用户T最近12期的承诺期数、打破承诺的期数、每期对应的拨打阶段等。如此，在业务***101可以使用实时更新的小微贷贷款数据库中的数据确定待催收用户，从而保证催收的实时性和准确性。
步骤210，将第一待催收用户的催收结果存储到区块链中，并通过第一业务***101和运营商300共识。
在一种可能的实现方式中，催收单元200还可以在对1000个目标催收用户进行催收后，将1000个目标催收用户对应的历史催收轨迹和最佳催收轨迹存储在区块链中。具体地说，可以预先控制催收单元200、业务***101和运营商300加入区块链，并在催收单元200、业务***101和运营商300成为区块链中的节点后，通过催收单元200使用1000个目标催收用户对应的历史催收轨迹和最佳催收轨迹生成交易信息，并将交易信息发送到区块链中的公共网络上。如此，业务***101和运营商300可以从公共网络中获取交易信息，并可以在认证该交易信息正确后，对该交易信息进行签名，从而若催收单元200、业务***101和运营商300对交易信息达成共识，则该交易信息可以存储在区块链中。
本发明实施例中，通过将至少一个业务***和运营商签名的一个或多个待催收用户的催收结果存储在区块链中，可以通过区块链存储合法且受信任的催收数据，在后续需要时通过区块链获取催收数据，从而避免待催收用户逃避还款的行为和/或提供贷款方的违法行为，同时保护待催收用户和提供贷款方的利益。
本发明的上述实施例中，接收至少一个业务***发送的催收名单，所述催收名单中包括一个或多个待催收用户的标识；进一步地，从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态，并根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式，进而向运营商发送所述一个或多个待催收用户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收；其中，所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式。本发明实施例中，通过一个或多个催收用户的催收状态确定一个或多个待催收用户分别对应的催收方式，可以无需人工干预，自动得到每个待催收用户对应的催收拨打方式，从而可以提高催收的效率和准确性；且，通过将催收方法与业务***解耦，可以使得本发明实施例中的催收方法应用于多种业务***，而无需针对于单一的业务***确定待催收用户对应的催收方式，从而可以使得催收方法的应用范围更为广泛。
针对上述方法流程，本发明实施例还提供一种基于分布式批量处理的处理装置，该装置的具体内容可以参照上述方法实施。
图4为本发明实施例提供的一种催收装置，该装置包括：
收发模块401，用于接收至少一个业务***发送的催收名单，所述催收名单中包括一个或多个待催收用户的标识；
获取模块402，用于从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态；
处理模块403，用于根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式；所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式；
所述收发模块401，还用于向运营商发送所述一个或多个待催收用户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收。
可选地，所述收发模块401还用于：接收所述运营商发送的所述一个或多个待催收用户的催收结果，并根据所述一个或多个待催收用户的催收结果更新所述预设数据库中存储的所述一个或多个待催收用户的催收状态；
所述处理模块403还用于：针对于所述一个或多个待催收用户中的第一待催收用户，根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式，以使所述运营商按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
可选地，所述处理模块403具体用于：
在所述第一待催收用户的催收状态为承诺预设期限内还款时，若所述第一待催收用户在所述预设期限内未按时还款，则确定对所述第一待催收用户进行二次催收；若所述第一待催收用户在所述预设期限内按时还款，则确定不对所述第一待催收用户进行二次催收。
可选地，所述收发模块401具体用于：
将所述一个或多个待催收用户划分为第一类型待催收用户和第二类型待催收用户，所述第一类型待催收用户的风险值大于所述第二类型待催收用户的风险值；
将所述第一类型待催收用户的信息发送给第一运营商，并将所述第二类型待催收用户的信息发送给第二运营商。
可选地，所述处理模块403还用于：
通过所述一个或多个业务***和所述运营商对所述一个或多个待催收用户的催收结果进行签名，并将签名后的所述一个或多个待催收用户的催收结果存储在区块链上。
可选地，所述一个或多个待催收用户为从与所述一个或多个业务***交易的至少一个用户中根据所述至少一个用户的信息筛选得到的；
若所述用户为企业，则所述用户的信息包括以下任意一项或任意多项：
企业法人的人行信息、企业中控股固定法人的借还款信息、企业的借还款信息、所述企业的基础工商信息。
从上述内容可以看出：本发明的上述实施例中，接收至少一个业务***发送的催收名单，所述催收名单中包括一个或多个待催收用户的标识；进一步地，从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态，并根 据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式，进而向运营商发送所述一个或多个待催收用户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收；其中，所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式。本发明实施例中，通过一个或多个催收用户的催收状态确定一个或多个待催收用户分别对应的催收方式，可以无需人工干预，自动得到每个待催收用户对应的催收拨打方式，从而可以提高催收的效率和准确性；且，通过将催收方法与业务***解耦，可以使得本发明实施例中的催收方法应用于多种业务***，而无需针对于单一的业务***确定待催收用户对应的催收方式，从而可以使得催收方法的应用范围更为广泛。
基于同一发明构思，本发明实施例还提供了一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如图2或图2任一项所述的基于分布式批量处理***的处理方法。
基于同一发明构思，本发明实施例还提供了一种计算机程序产品，当其在计算机上运行时，使得计算机执行如图2或图2任一项所述的基于分布式批量处理***的处理方法。
基于相同的技术构思，本发明实施例提供了一种终端设备，如图5所示，包括至少一个处理器1101，以及与至少一个处理器连接的存储器1102，本发明实施例中不限定处理器1101与存储器1102之间的具体连接介质，图5中处理器1101和存储器1102之间通过总线连接为例。总线可以分为地址总线、数据总线、控制总线等。
在本发明实施例中，存储器1102存储有可被至少一个处理器1101执行的指令，至少一个处理器1101通过执行存储器1102存储的指令，可以执行前述的催收方法中所包括的步骤。
其中，处理器1101是终端设备的控制中心，可以利用各种接口和线路连接终端设备的各个部分，通过运行或执行存储在存储器1102内的指令以及调用存储在存储器1102内的数据，从而实现数据处理。可选的，处理器1101可包括一个或多个处理单元，处理器1101可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作***、用户界面和应用程序等，调制解调处理器主要处理运维人员下发的指令。可以理解的是，上述调制解调处理器也可以不集成到处理器1101中。在一些实施例中，处理器1101和存储器1102可以在同一芯片上实现，在一些实施例中，它们也可以在独立的芯片上分别实现。
处理器1101可以是通用处理器，例如中央处理器(CPU)、数字信号处理器、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本发明实施例中公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合催收方法的实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器1102作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块。存储器1102可以包括至少一种类型的存储介质，例如可以包括闪存、硬盘、多媒体卡、卡型存储器、随机访问存储器(Random Access Memory，RAM)、静态随机访问存储器(Static Random Access Memory，SRAM)、可编程只读存储器(Programmable Read Only Memory，PROM)、只读存储器(Read Only Memory，ROM)、带电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory， EEPROM)、磁性存储器、磁盘、光盘等等。存储器1102是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本发明实施例中的存储器1102还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
基于相同的技术构思，本发明实施例提供了一种后端设备，如图6所示，包括至少一个处理器1201，以及与至少一个处理器连接的存储器1202，本发明实施例中不限定处理器1201与存储器1202之间的具体连接介质，图6中处理器1201和存储器1202之间通过总线连接为例。总线可以分为地址总线、数据总线、控制总线等。
在本发明实施例中，存储器1202存储有可被至少一个处理器1201执行的指令，至少一个处理器1201通过执行存储器1202存储的指令，可以执行前述的催收方法中所包括的步骤。
其中，处理器1201是后端设备的控制中心，可以利用各种接口和线路连接后端设备的各个部分，通过运行或执行存储在存储器1202内的指令以及调用存储在存储器1202内的数据，从而实现数据处理。可选的，处理器1201可包括一个或多个处理单元，处理器1201可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作***、应用程序等，调制解调处理器主要对接收到的指令进行解析以及对接收到的结果进行解析。可以理解的是，上述调制解调处理器也可以不集成到处理器1201中。在一些实施例中，处理器1201和存储器1202可以在同一芯片上实现，在一些实施例中，它们也可以在独立的芯片上分别实现。
处理器1201可以是通用处理器，例如中央处理器(CPU)、数字信号处理器、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本发明实施例中公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合催收方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器1202作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块。存储器1202可以包括至少一种类型的存储介质，例如可以包括闪存、硬盘、多媒体卡、卡型存储器、随机访问存储器(Random Access Memory，RAM)、静态随机访问存储器(Static Random Access Memory，SRAM)、可编程只读存储器(Programmable Read Only Memory，PROM)、只读存储器(Read Only Memory，ROM)、带电可擦除可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、磁性存储器、磁盘、光盘等等。存储器1202是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本发明实施例中的存储器1202还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
显然，本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (16)

  1. 一种催收方法，其特征在于，所述方法包括：
    接收至少一个业务***发送的催收名单，所述催收名单中包括一个或多个待催收用户的标识；
    从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态，并根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式；所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式；
    向运营商发送所述一个或多个待催收用户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    接收所述运营商发送的所述一个或多个待催收用户的催收结果，并根据所述一个或多个待催收用户的催收结果更新所述预设数据库中存储的所述一个或多个待催收用户的催收状态；
    针对于所述一个或多个待催收用户中的第一待催收用户，根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式，以使所述运营商按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收，包括：
    在所述第一待催收用户的催收状态为承诺预设期限内还款时，若所述第一待催收用户在所述预设期限内未按时还款，则确定对所述第一待催收用户进行二次催收；若所述第一待催收用户在所述预设期限内按时还款，则确定不对所述第一待催收用户进行二次催收。
  4. 根据权利要求1所述的方法，其特征在于，所述向运营商发送所述一个或多个待催收用户对应的催收方式，包括：
    将所述一个或多个待催收用户划分为第一类型待催收用户和第二类型待催收用户，所述第一类型待催收用户的风险值大于所述第二类型待催收用户的风险值；
    将所述第一类型待催收用户的信息发送给第一运营商，并将所述第二类型待催收用户的信息发送给第二运营商。
  5. 根据权利要求2至4中任一项所述的方法，其特征在于，所述方法还包括：
    通过所述一个或多个业务***和所述运营商对所述一个或多个待催收用户的催收结果进行签名，并将签名后的所述一个或多个待催收用户的催收结果存储在区块链上。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述一个或多个待催收用户为从与所述一个或多个业务***交易的至少一个用户中根据所述至少一个用户的信息筛选得到的；
    若所述用户为企业，则所述用户的信息包括以下任意一项或任意多项：
    企业法人的人行信息、企业中控股固定法人的借还款信息、企业的借还款信息、所述企业的基础工商信息。
  7. 一种催收***，其特征在于，所述催收***包括至少一个业务***，与所述至少 一个业务***连接的催收单元和运营商；
    所述至少一个业务***，用于分别从与所述至少一个业务***具有交易关系的至少一个用户中确定一个或多个待催收用户，并将所述一个或多个待催收用户的标识发送给催收装置；
    所述催收单元，用于接收所述至少一个业务***发送的一个或多个待催收用户的标识，并根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式；所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式；以及，向运营商发送所述一个或多个待催收用户对应的催收方式；
    所述运营商，用于按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收。
  8. 根据权利要求7所述的***，其特征在于，所述运营商还用于：根据第一待催收用户对应的催收方式向所述第一待催收用户进行催收后，将所述第一待催收用户的催收结果发送给催收单元；
    所述催收单元还用于：接收所述运营商发送的所述第一待催收用户的催收结果，并根据所述第一待催收用户的催收结果更新所述预设数据库中存储的所述第一待催收用户的催收状态；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式；
    所述运营商还用于：按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
  9. 一种催收装置，其特征在于，所述装置包括：
    收发模块，用于接收至少一个业务***发送的催收名单，所述催收名单中包括一个或多个待催收用户的标识；
    获取模块，用于从预设数据库中获取与所述一个或多个待催收用户的标识匹配的所述一个或多个待催收用户的催收状态；
    处理模块，用于根据所述一个或多个催收用户的催收状态确定所述一个或多个待催收用户分别对应的催收方式；所述一个或多个待催收用户对应的催收方式用于指示向所述一个或多个待催收用户进行催收的方式；
    所述收发模块，还用于向运营商发送所述一个或多个待催收用户对应的催收方式，以使所述运营商按照所述一个或多个待催收用户对应的催收方式向所述一个或多个待催收用户进行催收。
  10. 根据权利要求9所述的装置，其特征在于，所述收发模块还用于：接收所述运营商发送的所述一个或多个待催收用户的催收结果，并根据所述一个或多个待催收用户的催收结果更新所述预设数据库中存储的所述一个或多个待催收用户的催收状态；
    所述处理模块还用于：针对于所述一个或多个待催收用户中的第一待催收用户，根据所述第一待催收用户的催收状态确定是否对所述第一待催收用户进行二次催收；若确定对所述第一待催收用户进行二次催收，则根据所述第一待催收用户的催收结果确定所述第一待催收用户对应的二次催收方式，并向运营商发送所述第一待催收用户对应的二次催收方式，以使所述运营商按照所述第一待催收用户对应的二次催收方式向所述第一待催收用户进行二次催收。
  11. 根据权利要求10所述的装置，其特征在于，所述处理模块具体用于：
    在所述第一待催收用户的催收状态为承诺预设期限内还款时，若所述第一待催收用户在所述预设期限内未按时还款，则确定对所述第一待催收用户进行二次催收；若所述第一待催收用户在所述预设期限内按时还款，则确定不对所述第一待催收用户进行二次催收。
  12. 根据权利要求9所述的装置，其特征在于，所述收发模块具体用于：
    将所述一个或多个待催收用户划分为第一类型待催收用户和第二类型待催收用户，所述第一类型待催收用户的风险值大于所述第二类型待催收用户的风险值；
    将所述第一类型待催收用户的信息发送给第一运营商，并将所述第二类型待催收用户的信息发送给第二运营商。
  13. 根据权利要求10至12中任一项所述的装置，其特征在于，所述处理模块还用于：
    通过所述一个或多个业务***和所述运营商对所述一个或多个待催收用户的催收结果进行签名，并将签名后的所述一个或多个待催收用户的催收结果存储在区块链上。
  14. 根据权利要求9至12中任一项所述的装置，其特征在于，所述一个或多个待催收用户为从与所述一个或多个业务***交易的至少一个用户中根据所述至少一个用户的信息筛选得到的；
    若所述用户为企业，则所述用户的信息包括以下任意一项或任意多项：
    企业法人的人行信息、企业中控股固定法人的借还款信息、企业的借还款信息、所述企业的基础工商信息。
  15. 一种计算机可读存储介质，其特征在于，包括指令，当其在计算机的处理器上运行时，使得计算机的处理器执行如权利要求1至6任一项所述的方法。
  16. 一种计算机程序产品，其特征在于，当其在计算机上运行时，使得计算机执行如权利要求1至6任一项所述的方法。
PCT/CN2020/094238 2019-06-11 2020-06-03 一种催收方法、***及装置 WO2020248883A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910501225.8 2019-06-11
CN201910501225.8A CN110288464A (zh) 2019-06-11 2019-06-11 一种催收方法、***及装置

Publications (1)

Publication Number Publication Date
WO2020248883A1 true WO2020248883A1 (zh) 2020-12-17

Family

ID=68003767

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094238 WO2020248883A1 (zh) 2019-06-11 2020-06-03 一种催收方法、***及装置

Country Status (2)

Country Link
CN (1) CN110288464A (zh)
WO (1) WO2020248883A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112967131A (zh) * 2021-03-24 2021-06-15 中国工商银行股份有限公司 贷款催收方案推送方法及装置
CN113724066A (zh) * 2021-08-31 2021-11-30 平安普惠企业管理有限公司 基于语义分析的权益分配方法、装置、设备及存储介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110288464A (zh) * 2019-06-11 2019-09-27 深圳前海微众银行股份有限公司 一种催收方法、***及装置
CN110796430A (zh) * 2019-10-08 2020-02-14 中国建设银行股份有限公司 一种逾期交易数据处理方法和装置
CN112988721A (zh) * 2019-12-18 2021-06-18 马上消费金融股份有限公司 交互数据清洗、自动控制方法及其设备、存储装置
CN113744039A (zh) * 2020-05-27 2021-12-03 马上消费金融股份有限公司 催收管理方法、平台及通信设备
CN113284497A (zh) * 2020-12-31 2021-08-20 一汽资本控股有限公司 一种向客户进行催收的方法、装置以及智能催收***
CN113065948A (zh) * 2021-03-22 2021-07-02 广东贤能数字科技有限公司 一种基于人工智能的催收分期方法、装置、设备及介质
CN116341879B (zh) * 2023-05-26 2024-05-31 杭州度言软件有限公司 一种逾期资产清收智能分案方法与***

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107240013A (zh) * 2017-04-19 2017-10-10 中国建设银行股份有限公司 一种***催收还款的方法和装置
CN108090826A (zh) * 2017-11-13 2018-05-29 平安科技（深圳）有限公司 一种电话催收方法及终端设备
CN109559220A (zh) * 2018-11-16 2019-04-02 深圳前海微众银行股份有限公司 催收管理方法、设备及计算机可读存储介质
CN109859032A (zh) * 2019-01-22 2019-06-07 深圳壹账通智能科技有限公司 基于智能语音的账款催收方法、装置、设备和存储介质
CN110288464A (zh) * 2019-06-11 2019-09-27 深圳前海微众银行股份有限公司 一种催收方法、***及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107240013A (zh) * 2017-04-19 2017-10-10 中国建设银行股份有限公司 一种***催收还款的方法和装置
CN108090826A (zh) * 2017-11-13 2018-05-29 平安科技（深圳）有限公司 一种电话催收方法及终端设备
CN109559220A (zh) * 2018-11-16 2019-04-02 深圳前海微众银行股份有限公司 催收管理方法、设备及计算机可读存储介质
CN109859032A (zh) * 2019-01-22 2019-06-07 深圳壹账通智能科技有限公司 基于智能语音的账款催收方法、装置、设备和存储介质
CN110288464A (zh) * 2019-06-11 2019-09-27 深圳前海微众银行股份有限公司 一种催收方法、***及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112967131A (zh) * 2021-03-24 2021-06-15 中国工商银行股份有限公司 贷款催收方案推送方法及装置
CN113724066A (zh) * 2021-08-31 2021-11-30 平安普惠企业管理有限公司 基于语义分析的权益分配方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN110288464A (zh) 2019-09-27

Similar Documents

Publication Publication Date Title
WO2020248883A1 (zh) 一种催收方法、***及装置
US11399029B2 (en) Database platform for realtime updating of user data from third party sources
CN110197315B (zh) 风险评估方法、装置及其存储介质
JP2019522275A (ja) 電子抵当権仲介及び監視
US20080109314A1 (en) Method and apparatus for determining a customer's likelihood of reusing a financial account
CN107038645B (zh) 业务处理方法、装置及***和服务器
CN113034274A (zh) 一种基于区块链的供应链金融服务***、方法及终端设备
CN110197426B (zh) 一种信用评分模型的建立方法、装置及可读存储介质
US20120215681A1 (en) System and method for providing pre-qualified and guaranteed financial products
CN113887971A (zh) 企业基于大数据的个人征信查询方法、装置及电子设备
CN111210109A (zh) 基于关联用户预测用户风险的方法、装置和电子设备
CN107172311B (zh) 业务评估方法及终端设备
CN110610290A (zh) 间联商户风险管控方法及其***
CN111429125B (zh) 账户管理方法、装置、存储介质及电子设备
CN114723455A (zh) 业务处理方法、装置、电子设备和存储介质
CN113421157A (zh) 借款方案的确定方法、装置、设备和存储介质
CN108449518A (zh) 保险契约回访方法和装置
WO2022204779A1 (en) Predicting future events of predetermined duration using adaptively trained artificial-intelligence processes
CN110602336A (zh) 基于区块链的呼叫中心管理方法及***
KR20240094217A (ko) 분산 조회 방식의 스크래핑 서비스 시스템과 방법 및 이를 위한 컴퓨터 프로그램
US20200334598A1 (en) Automated summary system computer server associated with a risk relationship attribute value review
CN114881770A (zh) 基于区块链的交易数据处理方法、装置和服务器
CN116720823A (zh) 审批任务处理方法、装置、电子设备和存储介质
CN113191881A (zh) 基于区块链的金融业务监管数据处理方法、装置及***
CN115795426A (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: 20822313

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20822313

Country of ref document: EP

Kind code of ref document: A1