Deployment System, Method, Terminal Device and Medium for Cloud Collection

Abstract

The present invention discloses a cloud-based debt collection deployment system, method, terminal device, and computer-readable storage medium. The cloud-based debt collection deployment system includes: a cloud-based debt collection subsystem for batch-pushing preset outsourced order files to a cloud-based debt collection database within the cloud-based debt collection subsystem; and a debt collection business subsystem connected to the cloud-based debt collection subsystem. The cloud-based debt collection business subsystem is configured to receive debt collection operation requests, obtain outsourced order files from the cloud-based debt collection database based on the collection operation requests, perform debt collection operations based on the outsourced order files, obtain operation results, and simultaneously push the operation results to a local debt collection database within the cloud-based debt collection subsystem. The present invention can improve the efficiency of debt collection operations based on outsourced order files.

Description

Technical Field

[0001] The present invention relates to the field of big data processing, and in particular to a cloud-based debt collection deployment system, method, terminal device, and computer-readable storage medium. Background Art

[0002] In existing technology, overdue case information is typically integrated into data reports based on internal bank policy decisions. These reports are then synchronized with internal systems via files, all deployed within the bank. However, outsourced collection agencies must submit lists offline to in-bank personnel. These personnel then complete the application process, apply for an account number and a dynamic token, and return the information to the outsourced collection agency. The outsourced collection agency then logs into the bank's internal system, downloads the overdue case files, and imports them into its own system for collection operations.

[0003] Therefore, the existing collection methods for overdue bank cases have the following problems:

[0004] 1. After outsourced debt collection agencies download overdue case files by logging into the bank's internal system, it is unknown what the outsourced debt collection agencies use this sensitive information for, posing a risk of sensitive data leakage;

[0005] 2. When the bank's internal systems interact with outsourced collection agencies, there is a risk of data being attacked and intercepted, which in turn may affect the bank's internal systems.

[0006] 3. When outsourced collection agencies access the bank's system, they must go through the bank's application and approval process. This process is cumbersome and lengthy, and is not suitable for scenarios where large numbers of external users access the system or where personnel mobility is high.

[0007] In summary, the existing collection methods for overdue cases cannot guarantee the security of internal bank data, and the collection efficiency is low. Summary of the Invention

[0008] The main purpose of the present invention is to provide a cloud-based debt collection deployment system, method, terminal device and computer-readable storage medium, aiming to improve the efficiency of outsourced debt collection operations based on outsourced order files.

[0009] To achieve the above objectives, the present invention provides a cloud-based debt collection deployment system, which includes:

[0010] A cloud collection subsystem, which is used to push preset outsourcing order files in batches to a cloud collection database in the cloud collection subsystem;

[0011] The collection business subsystem is connected to the cloud collection subsystem. The cloud collection business subsystem is used to receive collection operation requests, and obtain the outsourced release file in the cloud collection database according to the collection operation request, perform collection operations based on the outsourced release file to obtain operation results, and push the operation results to the local collection database in the cloud collection subsystem.

[0012] Optionally, the cloud collection subsystem includes:

[0013] A local module, which is used to push preset outsourcing order files in batches;

[0014] A cloud module is connected to the local module, and is used to receive the outsourcing release files pushed in batches by the local module, and push the outsourcing release files to the cloud collection database in the cloud collection subsystem.

[0015] Optionally, the cloud-based debt collection deployment system further includes:

[0016] A user management subsystem is connected to the cloud collection subsystem and the collection business subsystem respectively. The user management subsystem is used to manage the outsourced collection agencies connected to the cloud collection deployment system. The user management subsystem includes: an agency management module, a user management module and a permission management module.

[0017] To achieve the above-mentioned object, the present invention further provides a cloud-based debt collection deployment method, which is applied to the cloud-based debt collection deployment system. The cloud-based debt collection deployment method includes:

[0018] Pushing the preset outsourcing order files in batches to the cloud collection database in the cloud collection subsystem;

[0019] Receive a collection operation request, and obtain the outsourced release file in the cloud collection database according to the collection operation request, perform a collection operation based on the outsourced release file to obtain an operation result, and push the operation result to the local collection database in the cloud collection subsystem.

[0020] Optionally, the cloud collection subsystem includes: a local module and a cloud module, wherein the local module further includes: a local big data processing unit and a local front-end unit, and the cloud module includes: a cloud big data processing unit and a cloud front-end unit;

[0021] The step of pushing the preset outsourcing order file to the cloud collection database in the cloud collection subsystem includes:

[0022] Push the preset outsourcing order file to the local big data processing unit, split and unpack the outsourcing order file in the local big data processing unit based on the preset UEDS suite, and push the split and unpacked outsourcing order file to the local front-end unit;

[0023] Push the outsourcing order file in the local front-end unit to the cloud front-end unit, and parse the outsourcing order file in the cloud front-end unit according to the UEDS suite;

[0024] The parsed outsourcing order file is pushed to the cloud-based big data processing unit, and the outsourcing order file in the cloud-based big data processing unit is pushed to the cloud-based collection database.

[0025] Optionally, the step of pushing the operation result to the local collection database in the cloud collection subsystem includes:

[0026] In this way, the operation results are pushed from the cloud collection database in the cloud collection subsystem to the local collection database in the cloud collection subsystem through the cloud front-end unit and the local front-end unit.

[0027] Optionally, the step of receiving a collection request includes:

[0028] Receive collection requests based on HTTPS and IP whitelist.

[0029] Optionally, before the step of pushing the preset outsourcing order file to the cloud collection database in the cloud collection subsystem, the method further includes:

[0030] The outsourcing release file is obtained by batch extracting collection data from the local collection database in the cloud collection subsystem based on the local big data processing unit.

[0031] To achieve the above-mentioned purpose, the present invention also provides a terminal device, which includes: a memory, a processor, and a cloud-based debt collection deployment program stored on the memory and runnable on the processor. When the cloud-based debt collection deployment program is executed by the processor, the steps of the cloud-based debt collection deployment method described above are implemented.

[0032] In addition, to achieve the above-mentioned purpose, the present invention also proposes a computer-readable storage medium, on which a cloud-based debt collection deployment program is stored. When the cloud-based debt collection deployment program is executed by a processor, the steps of the cloud-based debt collection deployment method as described above are implemented.

[0033] In addition, to achieve the above-mentioned purpose, the present invention also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the steps of the above-mentioned cloud-based debt collection deployment method.

[0034] The present invention provides a cloud-based debt collection deployment system, method, terminal device, computer-readable storage medium, and computer program product. The cloud-based debt collection deployment system includes: a cloud-based debt collection subsystem, which is used to push preset outsourced order files in batches to a cloud-based debt collection database in the cloud-based debt collection subsystem; a debt collection business subsystem, which is connected to the cloud-based debt collection subsystem. The cloud-based debt collection business subsystem is used to receive a debt collection operation request, and obtain the outsourced order files in the cloud-based debt collection database according to the debt collection operation request, perform a debt collection operation based on the outsourced order files to obtain an operation result, and push the operation result to a local debt collection database in the cloud-based debt collection subsystem.

[0035] Compared to the prior art, where an outsourced collection agency downloads outsourced release documents from the bank's internal system and then performs collection operations based on the downloaded outsourced release documents, the present invention constructs a cloud-based collection deployment system that includes a cloud collection subsystem, a collection business subsystem, and a user management subsystem. This deployment system solution utilizes the latest frameworks and interactive components, providing a functionally robust system while meeting the outsourced collection agency's basic requirements for an interactive experience. Outsourced collection agencies can directly access a large number of outsourced release documents from the cloud-based collection database through the cloud-based collection business subsystem and perform collection operations directly in the cloud. This invention effectively prevents the risk of sensitive data leakage caused by exporting, while also improving the efficiency of synchronizing collection data from within the bank to the cloud, meeting the needs of outsourced collection agency personnel to be able to work as soon as they arrive at work. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 This is a functional module diagram of an embodiment of a cloud-based debt collection deployment system of the present invention;

[0037] Figure 2 This is a schematic diagram of cloud deployment functions involved in an embodiment of a cloud-based debt collection deployment system of the present invention;

[0038] Figure 3 This is a flow chart of an embodiment of a method for deploying cloud-based debt collection according to the present invention;

[0039] Figure 4 This is a schematic diagram of the in-bank-cloud data synchronization process involved in an embodiment of a cloud-based debt collection deployment method of the present invention;

[0040] Figure 5A schematic diagram of a data synchronization time optimization path involved in an embodiment of a cloud-based debt collection deployment method of the present invention;

[0041] Figure 6 This is a schematic diagram of the structure of the hardware operating environment involved in the embodiment of the present invention.

[0042] The purpose, features and advantages of the present invention will be further described with reference to the accompanying drawings and in conjunction with the embodiments. DETAILED DESCRIPTION

[0043] It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0044] like Figure 1 The functional module diagram of an embodiment of the cloud-based debt collection deployment system of the present invention is shown in FIG. In an embodiment of the cloud-based debt collection deployment system of the present invention, the cloud-based debt collection deployment system of the present invention includes:

[0045] A cloud collection subsystem, which is used to push a preset outsourcing order file to a cloud collection database in the cloud collection subsystem;

[0046] The collection business subsystem is connected to the cloud collection subsystem. The cloud collection business subsystem is used to receive collection operation requests, and obtain the outsourced release file in the cloud collection database according to the collection operation request, perform collection operations based on the outsourced release file to obtain operation results, and push the operation results to the local collection database in the cloud collection subsystem.

[0047] When the terminal device deploys the collection system in the cloud, the cloud collection subsystem, collection business subsystem and user management subsystem are deployed respectively. The cloud collection subsystem is used to batch synchronize the bank's local outsourced release documents for overdue cases to the cloud collection database. Then, users of external institutions can directly perform related collection operations on the outsourced release documents in the cloud collection database in the cloud collection business subsystem.

[0048] It should be noted that, in this embodiment, Figure 2As shown in the cloud deployment functional diagram, the cloud-based debt collection deployment system includes a cloud-based debt collection subsystem and a debt collection business subsystem. The debt collection business subsystem includes a configuration center module, a homepage information display module, an operations center module, a job center module, and a statistics center module. The cloud-based debt collection deployment system offers outstanding advantages in terms of data security, information security, and timeliness. Regarding data security, the business information displayed in the debt collection business subsystem is only viewable by connected external organizations. Role-based permission control restricts access to the cloud system to organizational personnel. Regarding sensitive information, viewing and related operations are permitted only within the debt collection business subsystem. Exporting sensitive information is prohibited, and each backend view is recorded, effectively preventing the risk of sensitive data leakage due to export. Regarding information security, the cloud-based debt collection deployment system encrypts information transmission via HTTPS combined with IP whitelisting. A professional security team hardens the system, effectively blocking some hacker attacks. There are different response options for hacker attacks. In the worst-case scenario, if the cloud-based collection deployment system is compromised, the separation of the cloud deployment system from internal bank systems will not affect the operation of other systems. Regarding timeliness, the cloud-based collection subsystem establishes a data synchronization path from the bank to the cloud. Through backend optimization methods such as batch optimization and the integration of standardized solutions with the UDES and BDP suites, the efficiency of data synchronization from the bank to the cloud is greatly improved, effectively promoting timeliness optimization. For example, the cloud-based collection subsystem in this embodiment can synchronize 50 million data items from the local collection database to the cloud-based collection database in approximately 30 to 40 minutes.

[0049] In a feasible embodiment, the cloud collection subsystem includes:

[0050] A local module, which is used to push preset outsourcing order files in batches;

[0051] A cloud module is connected to the local module, and is used to receive the outsourcing release files pushed in batches by the local module, and push the outsourcing release files to the cloud collection database in the cloud collection subsystem.

[0052] The cloud collection subsystem includes local modules and cloud modules. Through the synergy of local modules and cloud modules, a large number of outsourced release documents within the bank can be quickly and efficiently pushed into the cloud collection database in the cloud, so that users can obtain the required outsourced release documents from the cloud collection database to perform collection operations and obtain collection results, and return the collection results to the local collection database in the cloud collection subsystem, so that business personnel within the bank can make timely processing of the data.

[0053] It should be noted that in this embodiment, the terminal device quickly synchronizes and pushes a large number of outsourced order files in the bank's local collection database to the cloud collection database through the cloud collection subsystem, realizing efficient in-bank-cloud data synchronization, thereby improving the efficiency of collection operations.

[0054] In a feasible embodiment, the cloud-based debt collection deployment system further includes:

[0055] A user management subsystem is connected to the cloud collection subsystem and the collection business subsystem respectively. The user management subsystem is used to manage external organizations connected to the cloud collection deployment system. The user management subsystem includes: an organization management module, a user management module and a permission management module.

[0056] In addition to the cloud collection subsystem and the collection business subsystem, the cloud collection deployment system also includes a user management subsystem. The user management subsystem manages the institutions and users connected to the cloud collection deployment system, and also manages the permissions of each institution and user. It can assign corresponding permissions to users based on actual business scenarios to limit user operations.

[0057] It should be noted that in this embodiment, in order to meet the scenario of large-scale user access from external organizations, a user management system (PUM) is developed separately for external organizations and deployed on the cloud. External organizations can create organizations and user personnel according to their actual conditions for flexible use, effectively reducing the access costs of external organizations.

[0058] In this embodiment, when a terminal device deploys a collection system in the cloud, a cloud collection subsystem, a collection business subsystem, and a user management subsystem are deployed. The cloud collection subsystem is used to batch synchronize the bank's local outsourced release documents for overdue cases to the cloud collection database. Users of external institutions can then directly perform relevant collection operations on the outsourced release documents in the cloud collection database in the cloud collection business subsystem. The cloud collection subsystem includes local modules and cloud modules. Through the synergistic effect of the local modules and the cloud modules, a large number of outsourced release documents within the bank can be quickly and efficiently pushed to the cloud collection database in the cloud. This allows users to obtain the required outsourced release documents from the cloud collection database to perform collection operations and obtain collection results. The collection results are then returned to the local collection database in the cloud collection subsystem, allowing business personnel within the bank to make timely data processing. In addition to the cloud collection subsystem and the collection business subsystem, the cloud collection deployment system also includes a user management subsystem. The user management subsystem manages the institutions and users connected to the cloud collection deployment system, and also manages the permissions of each institution and user. It can assign corresponding permissions to users based on actual business scenarios to limit user operations.

[0059] Compared to the prior art where an outsourced collection agency downloads outsourced release files from the bank's internal system and then performs collection operations based on the downloaded outsourced release files, the present invention constructs a cloud-based collection deployment system that includes a cloud collection subsystem, a collection business subsystem, and a user management subsystem. This deployment system solution utilizes the latest framework and interactive components, providing a fully functional system while meeting the outsourced collection agency's basic demands for an interactive experience. Outsourced collection agencies can directly access a large number of outsourced release files from the cloud collection database within the cloud collection subsystem through the cloud-based collection business subsystem, perform collection operations directly in the cloud, and, if the cloud-based collection deployment system is hacked, will not affect the operation of other systems within the bank. This effectively prevents the risk of data leakage caused by the export of sensitive data, while improving the efficiency of data synchronization from within the bank to the cloud, meeting the needs of outsourced collection agency staff to be able to work as soon as they arrive at work.

[0060] Furthermore, based on the various embodiments of the above-mentioned cloud-based debt collection deployment system, various embodiments of the cloud-based debt collection deployment method of the present invention are proposed. The cloud-based debt collection deployment method of the present invention is applied to the above-mentioned cloud-based debt collection deployment system.

[0061] Please refer to Figure 3 , Figure 3 This is a flow chart of the first embodiment of the cloud-based debt collection deployment method of the present invention.

[0062] In this embodiment, an embodiment of a deployment method for cloud-based debt collection is provided. It should be noted that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than here.

[0063] Step S10: Pushing the preset outsourcing order files in batches to the cloud collection database in the cloud collection subsystem;

[0064] The terminal device pre-processes the overdue case information for internal bank strategy decisions and integrates it to obtain a large number of outsourced release documents, and then pushes a large number of these outsourced release documents from the local collection database within the bank to the cloud collection database in the cloud collection subsystem, so that users of the outsourced collection agency can obtain the outsourced release documents in the cloud collection database through the collection business subsystem to perform outsourced collection operations for the outsourced release documents. Among them, the strategy decision can include adopting corresponding collection methods according to the degree of overdueness of the customer.

[0065] Specifically, for example, Figure 4 As shown in the diagram of the in-bank-cloud data synchronization process, the terminal device pushes a large number of outsourced order files in batches to the local BDP (Big Data Platform, big data processing system), and then pushes the outsourced order files in the local BDP in batches to the local CAP (front-end system, used to provide a file interaction channel between the bank's internal system and external systems). The outsourced order files in the local CAP are then pushed in batches to the cloud CAP. The outsourced order files in the cloud CAP are then pushed in batches to the outsourced collection batch application on the cloud via SFTP. The outsourced order files in the outsourced collection batch application are then parsed and pushed to the cloud BDP. Finally, the outsourced order files in the cloud BDP are pushed in batches to the cloud database (CCSM DB). Figure 4 The new collection WEB service is the collection business subsystem in the cloud-based collection deployment system of the present invention, that is, it provides an accessible and operable front end for the connected outsourced collection agencies to implement outsourced collection operations.

[0066] It should be noted that in this embodiment, the terminal device pushes the outsourced release order files in batches from the bank's local collection database to the cloud collection database through BDP and CAP, thereby realizing rapid synchronization of collection data from the bank to the cloud.

[0067] Furthermore, the cloud-based debt collection deployment method of the present invention further includes:

[0068] Step S20: Receive a collection operation request, and obtain the outsourced release file in the cloud collection database according to the collection operation request, perform a collection operation based on the outsourced release file to obtain an operation result, and push the operation result to the local collection database in the cloud collection subsystem.

[0069] The terminal device receives the collection operation request through the collection business subsystem, and obtains the outsourced release file corresponding to the collection operation request from the cloud collection database, and then performs the corresponding collection operation based on the outsourced release file in the collection business subsystem in the cloud collection deployment system, and obtains the collection result. In order to enable the business personnel within the bank to obtain the collection result in a timely manner, the terminal device also needs to return the collection result to the local collection database, and the business personnel within the bank will obtain the corresponding collection data from the local collection database.

[0070] Specifically, for example, Figure 4 As shown in the diagram of the in-bank-cloud data synchronization process, after the outsourced collection agency's staff completes the outsourced collection work in the cloud, the terminal device will obtain the work results based on the collection business subsystem. These work results may include collection records, audio recordings, and videos. The work results are then processed and pushed from the cloud database to the cloud BDP. The work results in the cloud BDP are then pushed to the cloud CAP. The work results in the cloud CAP are then pushed to the local CAP via SFTP. The work results in the local CAP are then pushed to the local BDP. Finally, the work results in the local BDP are pushed to the local collection database. The bank's staff will then retrieve the required data from this local collection database for business processing.

[0071] It should be noted that in this embodiment, after the business personnel of the outsourced collection agency complete the outsourced collection operation through the collection business subsystem and obtain the collection results, they directly push the operation results back to the bank's local collection database through the cloud collection subsystem, thereby improving the efficiency of pushing the collection data from the cloud back to the bank, and improving the processing efficiency of the bank's internal business.

[0072] Furthermore, in the above step S10, “pushing the preset outsourcing order file to the cloud collection database in the cloud collection subsystem” may include:

[0073] Step S101: Push the preset outsourcing order file to the local big data processing unit, split and unpack the outsourcing order file in the local big data processing unit based on the preset UEDS, and push the split and unpacked outsourcing order file to the local front-end unit;

[0074] It should be noted that, in this embodiment, the cloud collection subsystem includes: a local module and a cloud module, wherein the local module also includes: a local BDP (big data processing unit) and a CAP (local front-end unit), and the cloud module includes: a cloud BDP and a cloud CAP.

[0075] Specifically, for example, Figure 5 As shown in the diagram of the data synchronization time optimization path, the terminal device extracts the outsourced order files from the local collection database to the local BDP through Sqoop, and then uses UEDS to split and unpack a large number of outsourced order files in the local BDP to obtain a large number of outsourced order files. At this time, the outsourced order files are smaller and easier to transmit than the outsourced order files before splitting and unpacking. The large number of outsourced order files obtained by splitting and unpacking are pushed to the local CAP.

[0076] Step S102: Push the outsourcing order file in the local front-end unit to the cloud front-end unit, and parse the outsourcing order file in the cloud front-end unit according to the UEDS suite;

[0077] In step S103, the parsed outsourcing order file is pushed to the cloud-based big data processing unit, and the outsourcing order file in the cloud-based big data processing unit is pushed to the cloud-based collection database.

[0078] After the terminal device obtains a large number of outsourced release files after splitting and unpacking through the local CAP, it will further push the large number of outsourced release files in the local CAP to the cloud CAP, and directly perform multi-threaded parallel analysis on the large number of outsourced release files in the cloud CAP through the UEDS suite in the cloud BDP, and then push the outsourced release files after multi-threaded parallel analysis to the cloud BDP, and push the outsourced release files in the cloud BDP to the cloud collection database through sqoop.

[0079] It should be noted that in this embodiment, an in-bank-cloud data synchronization channel is established, and a large number of outsourced order files are split and unpacked by integrating UDES and BDP suites. Then, a large number of outsourced order files after splitting and unpacking are batch-stored through multi-threaded parallel processing, which optimizes the synchronization efficiency of collection data from the bank to the cloud and improves data synchronization efficiency.

[0080] Furthermore, in the above step S20, “pushing the operation result to the local collection database in the cloud collection subsystem” may include:

[0081] In step S201, the operation result is pushed from the cloud collection database in the cloud collection subsystem to the local collection database in the cloud collection subsystem through the cloud front-end unit and the local front-end unit.

[0082] It should be noted that in this embodiment, the local front-end unit (CAP) and the cloud front-end unit (CAP) serve as data transfer stations from the bank to the cloud, that is, from the local to the cloud, providing a file interaction channel between the bank system and the external system.

[0083] After the terminal device obtains the operation results based on the collection business subsystem, it pushes the operation results from the cloud database to the cloud BDP, and then pushes the operation results in the cloud BDP to the cloud CAP, and then pushes the operation results in the cloud CAP to the local CAP through SFTP, and then pushes the operation results in the local CAP to the local BDP, and then pushes the operation results in the local BDP to the local collection database.

[0084] It should be noted that in this embodiment, the terminal device will transmit the obtained operation results from the cloud collection database back to the local collection database, so that the bank's business personnel can perform related business processing based on the outsourced collection operation results, thereby improving the processing efficiency of the bank's business.

[0085] In this embodiment, the terminal device pre-processes overdue case information for internal bank policy decisions and integrates it to obtain a large number of outsourced release documents. These documents are then pushed from the bank's local collection database to the cloud collection database in the cloud collection subsystem. This allows users of outsourced collection agencies to access the outsourced release documents in the cloud collection database through the collection business subsystem and perform outsourced collection operations based on these documents. The terminal device receives a collection operation request through the collection business subsystem and retrieves the outsourced release document corresponding to the collection operation request from the cloud collection database. Based on the outsourced release document, the collection business subsystem in the cloud collection deployment system performs the corresponding collection operation and obtains the collection results. To enable bank staff to obtain the collection results in a timely manner, the terminal device also needs to return the collection results to the local collection database, from which bank staff can retrieve the corresponding collection data.

[0086] Compared with the prior art in which the business personnel of the outsourced collection agency directly download the relevant outsourced release files from the bank's internal business system to carry out collection operations, the present invention splits and unpacks a large number of outsourced release files about overdue case information and pushes them in batches to the collection system on the cloud, so that the business personnel of the outsourced collection agency can directly carry out the corresponding collection operations in the cloud system. On the one hand, the present invention greatly improves the efficiency of pushing collection data from local synchronization to the cloud, meeting the needs of the business personnel of the outsourced collection agency to start work as soon as they get to work. On the other hand, it effectively prevents the risk of data leakage caused by the export of sensitive data, and improves the security and stability of the bank's internal system.

[0087] Furthermore, based on the first embodiment of the deployment method of cloud-based debt collection of the present invention, a second embodiment of the deployment method of cloud-based debt collection of the present invention is proposed.

[0088] The main difference between this embodiment and the first embodiment is that in step S20, "receiving a collection request" may include:

[0089] Step S202: Receive a collection request based on HTTPS combined with an IP whitelist.

[0090] The terminal device receives the collection operation request triggered by the outsourced collection agency through the pre-deployed collection business subsystem, and obtains the corresponding outsourced collection file according to the collection operation request to perform the outsourced collection operation. In addition, the terminal device encrypts and transmits the collection data through HTTPS combined with the IP whitelist. The IP whitelist includes outsourced collection agencies that have a cooperative relationship with the bank. That is, the terminal device needs to pre-verify whether the connected outsourced collection agency is on the IP whitelist. Only after the verification is passed will the corresponding business personnel of the outsourced collection agency be allowed to obtain the outsourced release file and perform the corresponding outsourced collection operation on the cloud.

[0091] It should be noted that, in this embodiment, by combining HTTPS with IP whitelist, it is possible to provide better access speed and efficiency while taking security into consideration.

[0092] Furthermore, before the above step S10 of "pushing the preset outsourcing order files in batches to the cloud collection database in the cloud collection subsystem", the following steps are also included:

[0093] Step S30: Based on the local big data processing unit, the collection data is batch-extracted from the local collection database in the cloud collection subsystem to obtain the outsourced release file.

[0094] It should be noted that, in this embodiment, Figure 4The diagram below shows the in-bank-cloud data synchronization process. The collection batch subsystem is used to update the data stored in the local collection database based on account information. Furthermore, the terminal device extracts the collection data stored in the local collection database through the local BDP, generating a large number of outsourced release documents in batches.

[0095] In this embodiment, the terminal device encrypts and transmits collection data via HTTPS combined with an IP whitelist. The IP whitelist includes outsourced collection agencies that have a cooperative relationship with the bank. This means that the terminal device must pre-verify whether the outsourced collection agency is on the IP whitelist. Only after verification is the corresponding business personnel of the outsourced collection agency allowed to obtain the outsourced release document and perform the corresponding outsourced collection operations in the cloud. This invention improves the access speed of the cloud-based collection system and the efficiency of outsourced collection operations while maintaining security.

[0096] Further, if Figure 6 As shown, Figure 6 It is a schematic diagram of the device structure of the hardware operating environment involved in the embodiment of the present invention.

[0097] It should be noted that the terminal device in the embodiment of the present invention can be a terminal device for implementing real-time and efficient cloud-based debt collection deployment, and the terminal device can specifically be a smart phone, a personal computer, a server, etc.

[0098] like Figure 6 As shown, the device may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0099] Those skilled in the art will understand that Figure 6 The device structure shown in the figure does not constitute a limitation of the device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0100] like Figure 6As shown, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a cloud-based debt collection deployment program. The operating system is a program that manages and controls the hardware and software resources of the device, and supports the operation of the cloud-based debt collection deployment program and other software or programs. Figure 1 In the device shown, the user interface 1003 is mainly used to communicate data with the client; the network interface 1004 is mainly used to establish a communication connection with the server; and the processor 1001 can be used to call the cloud collection deployment program stored in the memory 1005 and perform the following operations:

[0101] Pushing the preset outsourcing order files in batches to the cloud collection database in the cloud collection subsystem;

[0102] Receive a collection operation request, and obtain the outsourced release file in the cloud collection database according to the collection operation request, perform a collection operation based on the outsourced release file to obtain an operation result, and push the operation result to the local collection database in the cloud collection subsystem.

[0103] Furthermore, the cloud collection subsystem includes: a local module and a cloud module, wherein the local module further includes: a local big data processing unit and a local front-end unit, and the cloud module includes: a cloud big data processing unit and a cloud front-end unit;

[0104] The processor 1001 may also be configured to call a cloud-based debt collection deployment program stored in the memory 1005 and perform the following operations:

[0105] Push the preset outsourcing order file to the local big data processing unit, split and unpack the outsourcing order file in the local big data processing unit based on the preset UEDS suite, and push the split and unpacked outsourcing order file to the local front-end unit;

[0106] Push the outsourcing order file in the local front-end unit to the cloud front-end unit, and parse the outsourcing order file in the cloud front-end unit according to the UEDS suite;

[0107] The parsed outsourcing order file is pushed to the cloud-based big data processing unit, and the outsourcing order file in the cloud-based big data processing unit is pushed to the cloud-based collection database.

[0108] Furthermore, the processor 1001 may also be configured to call a cloud-based debt collection deployment program stored in the memory 1005 and perform the following operations:

[0109] In this way, the operation results are pushed from the cloud collection database in the cloud collection subsystem to the local collection database in the cloud collection subsystem through the cloud front-end unit and the local front-end unit.

[0110] Furthermore, the processor 1001 may also be configured to call a cloud-based debt collection deployment program stored in the memory 1005 and perform the following operations:

[0111] Receive collection requests based on HTTPS and IP whitelist.

[0112] Furthermore, before the step of pushing the preset outsourcing order file to the cloud collection database in the cloud collection subsystem, the processor 1001 may also be configured to call a cloud collection deployment program stored in the memory 1005 and perform the following operations:

[0113] The outsourcing release file is obtained by batch extracting collection data from the local collection database in the cloud collection subsystem based on the local big data processing unit.

[0114] In addition, an embodiment of the present invention further proposes a computer-readable storage medium, on which a cloud-based debt collection deployment program is stored. When the cloud-based debt collection deployment program is executed by a processor, the steps of the cloud-based debt collection deployment method described above are implemented.

[0115] The various embodiments of the computer-readable storage medium of the present invention can refer to the various embodiments of the deployment method of the cloud-based debt collection of the present invention, and will not be repeated here.

[0116] In addition, an embodiment of the present invention also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the cloud-based collection deployment method as described in any embodiment of the above cloud-based collection deployment method.

[0117] The specific embodiments of the computer program product of the present invention are basically the same as the embodiments of the above-mentioned cloud-based debt collection deployment method, and will not be described in detail here.

[0118] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

[0119] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0120] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better embodiment. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), including a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0121] The above are only preferred embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention description and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A cloud-based debt collection deployment system, characterized in that: The cloud-based debt collection deployment system includes: A cloud collection subsystem, which is used to push preset outsourcing order files in batches to a cloud collection database in the cloud collection subsystem; The cloud collection subsystem includes: A local module, which is used to push preset outsourcing order files in batches, and further includes a local big data processing unit and a local front-end unit; A cloud module, connected to the local module, configured to receive batches of outsourced order files pushed by the local module and push the outsourced order files to the cloud collection database in the cloud collection subsystem. The cloud module also includes a cloud-based big data processing unit and a cloud-based front-end unit. The local module is further configured to push the preset outsourcing order file to the local big data processing unit, and split and unpack the outsourcing order file in the local big data processing unit based on the preset UEDS suite, and push the split and unpacked outsourcing order file to the local front-end unit; Push the outsourcing order file in the local front-end unit to the cloud front-end unit, and parse the outsourcing order file in the cloud front-end unit according to the UEDS suite; Pushing the parsed outsourcing order file to the cloud-based big data processing unit, and pushing the outsourcing order file in the cloud-based big data processing unit to the cloud-based debt collection database; A collection business subsystem, connected to the cloud collection subsystem, configured to receive collection operation requests, obtain an outsourced order file from the cloud collection database based on the collection operation request, perform a collection operation based on the outsourced order file to obtain an operation result, and simultaneously push the operation result to the local collection database in the cloud collection subsystem; The collection business subsystem is further configured to push the operation results from the cloud collection database in the cloud collection subsystem to the local collection database in the cloud collection subsystem through the cloud front-end unit and the local front-end unit.

2. The cloud-based debt collection deployment system according to claim 1, characterized in that: The cloud-based debt collection deployment system further includes: A user management subsystem is connected to the cloud collection subsystem and the collection business subsystem respectively. The user management subsystem is used to manage the outsourced collection agencies connected to the cloud collection deployment system. The user management subsystem includes: an agency management module, a user management module and a permission management module.

3. A cloud-based debt collection deployment method, characterized in that: The cloud-based debt collection deployment method is applied to the cloud-based debt collection deployment system according to any one of claims 1 to 2, and the cloud-based debt collection deployment method includes: Pushing the preset outsourcing order files in batches to the cloud collection database in the cloud collection subsystem; The step of pushing the preset outsourcing order file to the cloud collection database in the cloud collection subsystem includes: Push the preset outsourcing order file to the local big data processing unit, split and unpack the outsourcing order file in the local big data processing unit based on the preset UEDS suite, and push the split and unpacked outsourcing order file to the local front-end unit; Push the outsourcing order file in the local front-end unit to the cloud front-end unit, and parse the outsourcing order file in the cloud front-end unit according to the UEDS suite; Pushing the parsed outsourcing order file to the cloud-based big data processing unit, and pushing the outsourcing order file in the cloud-based big data processing unit to the cloud-based debt collection database; Receive a collection operation request, and obtain the outsourced release file in the cloud collection database according to the collection operation request, perform a collection operation based on the outsourced release file to obtain an operation result, and simultaneously push the operation result to the local collection database in the cloud collection subsystem; The step of pushing the operation result to the local collection database in the cloud collection subsystem includes: In this way, the operation results are pushed from the cloud collection database in the cloud collection subsystem to the local collection database in the cloud collection subsystem through the cloud front-end unit and the local front-end unit.

4. The cloud-based debt collection deployment method according to claim 3, characterized in that: The step of receiving a collection operation request includes: Receive collection requests based on HTTPS and IP whitelist.

5. The cloud-based debt collection deployment method according to claim 3, characterized in that: Before the step of pushing the preset outsourcing order file to the cloud collection database in the cloud collection subsystem, the method further includes: The outsourcing release file is obtained by batch extracting collection data from the local collection database in the cloud collection subsystem based on the local big data processing unit.

6. A terminal device, characterized in that: The terminal device includes a memory, a processor, and a cloud-based debt collection deployment program stored in the memory and executable on the processor. When the cloud-based debt collection deployment program is executed by the processor, the steps of the cloud-based debt collection deployment method as described in any one of claims 3 to 5 are implemented.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a cloud-based debt collection deployment program, and when the cloud-based debt collection deployment program is executed by the processor, the steps of the cloud-based debt collection deployment method as described in any one of claims 3 to 5 are implemented.

Images