Resource recovery amount determination method and device, equipment, medium and program product
By independently processing user transaction data in database table entities and partitions, data asynchronousness and processing efficiency problems in resource recovery calculation are solved, efficient and accurate resource recovery calculation is achieved, and flexible expansion of data sources is supported.
Patent Information
- Application Number
- CN202411332872.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-24
- Publication Date
- 2025-01-10
AI Technical Summary
In the calculation of resource recovery amount, the processing timeliness is reduced due to the increase in data asynchronousness and data volume, and different data sources influence each other, affecting the calculation accuracy and efficiency.
By determining the target database table entity and partition according to the resource type and the correspondence between the service organization in multiple preset database table entities, and independently storing and processing user transaction data, real-time calculation and accuracy of resource recovery amount are achieved.
It improves the real-time and accuracy of data processing, reduces the mutual influence between different data sources, ensures that the calculation of resource recovery amount is accurate and efficient, and has good scalability and flexibility.
Smart Images
Figure CN119293089A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of big data technology, and in particular, relates to a method, device, equipment, medium and program product for determining resource recovery amount. Background Art
[0002] With the diversification of resource services, users can apply for resource lending services from service agencies across different resource types (such as credit cards, consumer loans, mortgages, small and micro loans, etc.).
[0003] In the relevant technology, it is necessary to wait until the user transaction data of each resource type and each service agency are complete before loading the user transaction data, and then summarize the daily transaction data by customer dimension, calculate the daily resource recovery amount, and finally calculate the recovery-related indicators by customer dimension. Since the relevant technology needs to wait until all data are collected before starting the data loading and processing process, there are the following problems: the repayment data of each channel and each branch does not arrive synchronously, which seriously reduces the timeliness of data processing; with the continuous increase in the number of financial product fields and branches connected, the data processing volume increases sharply and the processing speed gradually slows down; if the repayment data of a certain product field cannot arrive in time or has quality problems, it will affect each other and may have an adverse impact on the data processing of other fields or branches.
[0004] In view of the above problems, there is an urgent need to develop a more efficient, flexible and reliable resource recovery amount determination process. Summary of the invention
[0005] The embodiments of the present application provide a method, apparatus, device, medium and program product for determining a resource recovery amount, which can provide a more efficient, flexible and reliable resource recovery amount determination process, can adapt to the asynchrony of data arrival, improve the real-time and accuracy of data processing, and reduce the mutual influence between different data sources, thereby ensuring that the calculation of resource recovery amount is more accurate and efficient.
[0006] In a first aspect, an embodiment of the present application provides a method for determining a resource recovery amount, comprising:
[0007] In the case of receiving user transaction data corresponding to the target resource type and the target service agency, determining the target database table entity corresponding to the target resource type among a plurality of preset database table entities according to the correspondence between the preset resource type and the database table entity, wherein the user transaction data includes sub-transaction data of different users;
[0008] Among the multiple partitions of the target database table entity, determine the target partition corresponding to the target service organization according to the preset correspondence relationship between the service organization and the partition of the database table entity;
[0009] Store the user transaction data in the target partition of the target database table entity;
[0010] Obtain sub-transaction data of a target user in a target partition of a target database table entity;
[0011] Based on the sub-transaction data of the target user, determine the resource recovery amount corresponding to the target user.
[0012] In a possible embodiment of the first aspect, the target resource type is any one of multiple resource types, and the target service agency is any one of multiple service agencies.
[0013] In a possible embodiment of the first aspect, determining a resource recovery amount corresponding to the target user based on the sub-transaction data of the target user includes:
[0014] Get the updated status of the resource recovery amount corresponding to the target user;
[0015] When the update state is in the updating state, the waiting update state is changed from the updating state to the non-updating state;
[0016] When the update status changes from the updating status to the non-updating status, the resource recovery amount corresponding to the target user is determined based on the sub-transaction data of the target user, and the update status is modified to the updating status.
[0017] In a possible embodiment of the first aspect, the present invention further includes:
[0018] When the update status is not in the updating state, the resource recovery amount corresponding to the target user is determined based on the sub-transaction data of the target user, and the update status is modified to the updating state.
[0019] In a possible embodiment of the first aspect, the present invention further includes:
[0020] After the resource recovery amount corresponding to the target user is determined, the update status is changed to a non-updating status.
[0021] In a possible embodiment of the first aspect, the present invention further includes:
[0022] When the resource recovery amount corresponding to the target user is determined by the user transaction data corresponding to each resource type and each service agency, the usage status of the resource recovery amount corresponding to the target user is updated to an available status.
[0023] Based on the same inventive concept, in a second aspect, an embodiment of the present application further provides a device for determining a resource recovery amount, comprising:
[0024] A determination module, configured to determine, upon receiving user transaction data corresponding to a target resource type and a target service agency, a target database table entity corresponding to the target resource type from among a plurality of preset database table entities according to a correspondence between preset resource types and database table entities, wherein the user transaction data includes sub-transaction data of different users;
[0025] The determination module is further used to determine the target partition corresponding to the target service agency among the multiple partitions of the target database table entity according to the preset correspondence relationship between the service agency and the partition of the database table entity;
[0026] A storage module, used for storing user transaction data in a target partition of a target database table entity;
[0027] An acquisition module, used for acquiring sub-transaction data of a target user in a target partition of a target database table entity;
[0028] The determination module is also used to determine the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user.
[0029] Based on the same inventive concept, in the third aspect, an embodiment of the present application also provides a device for determining a resource recovery amount, the device comprising a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the method for determining the resource recovery amount in the first aspect, or any embodiment of the first aspect, is implemented.
[0030] Based on the same inventive concept, in the fourth aspect, an embodiment of the present application further provides a computer storage medium, on which computer program instructions are stored. When the computer program instructions are executed by a processor, the method for determining the resource recovery amount in the first aspect or any embodiment of the first aspect is implemented.
[0031] Based on the same inventive concept, in the fifth aspect, an embodiment of the present application also provides a computer program product. When the instructions in the computer program product are executed by the processor of the device, the device can execute the method for determining the resource recovery amount in the first aspect, or any embodiment of the first aspect.
[0032] The resource recovery amount determination method, apparatus, device, medium and program product of the embodiments of the present application, the method determines the target database table entity corresponding to the target resource type in multiple preset database table entities according to the correspondence between the preset resource type and the database table entity when receiving the user transaction data corresponding to the target service agency in the target resource type, wherein the user transaction data includes sub-transaction data of different users, and then determines the target partition corresponding to the target service agency in multiple partitions of the target database table entity according to the correspondence between the preset service agency and the partition of the database table entity, and then the user transaction data can be stored in the target partition of the target database table entity, and then the sub-transaction data of the target user is obtained in the target partition of the target database table entity; based on the sub-transaction data of the target user, the resource recovery amount corresponding to the target user is determined. When the user transaction data corresponding to a service agency of a certain resource type arrives, it can be loaded and calculated immediately without waiting for data from other service agencies or resource types. This can adapt to the asynchrony of data arrival. This independent processing mechanism for user transaction data effectively reduces the mutual influence between user transaction data, ensures the accuracy and reliability of the calculation of resource recovery amount, and has good scalability. When new resource types or service agencies are added, it is only necessary to simply expand the corresponding tables or partitions, which is more flexible. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] Other features, objects and advantages of the present application will become more apparent by reading the following detailed description of non-limiting embodiments with reference to the accompanying drawings, in which the same or similar reference numerals represent the same or similar features and the accompanying drawings are not drawn to scale.
[0034] Figure 1 It is a flow chart of a method for determining resource recovery amount provided in an embodiment of the present application;
[0035] Figure 2 It is another flow chart of the method for determining the resource recovery amount provided in the embodiment of the present application;
[0036] Figure 3 It is another flow chart of the method for determining the resource recovery amount provided in the embodiment of the present application;
[0037] Figure 4 It is another flow chart of the method for determining the resource recovery amount provided in the embodiment of the present application;
[0038] Figure 5 It is a structural schematic diagram of a device for determining a resource recovery amount provided in an embodiment of the present application;
[0039] Figure 6It is a structural schematic diagram of a device for determining a resource recovery amount provided in an embodiment of the present application. DETAILED DESCRIPTION
[0040] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only configured to explain the present application and are not configured to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is only to provide a better understanding of the present application by illustrating the examples of the present application.
[0041] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "include..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0042] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0043] It is obvious to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit or scope of the present application. Therefore, the present application is intended to cover modifications and changes of the present application that fall within the scope of the corresponding claims (technical solutions for protection) and their equivalents. It should be noted that the implementation methods provided in the embodiments of the present application can be combined with each other without contradiction.
[0044] It should be noted that the acquisition, storage, use and processing of data in the embodiments of the present application are in compliance with the relevant provisions of national laws and regulations.
[0045] It should also be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.
[0046] Before describing the technical solutions provided by the embodiments of the present application, in order to facilitate the understanding of the embodiments of the present application, the present application first specifically describes the problems existing in the related art:
[0047] With the diversification of resource services, users can apply for resource lending services from service agencies across different resource types (such as credit cards, consumer loans, mortgages, small and micro loans, etc.).
[0048] In the related technologies, it is necessary to wait until the user transaction data of each resource type and each service agency are complete before loading the user transaction data, and then summarize the daily transaction data by customer dimension, calculate the daily resource recovery amount, and finally calculate the recovery-related indicators by customer dimension. Since the related technologies need to wait until all data are complete before starting the data loading and processing process, there are the following problems: the repayment data of each channel and each branch do not arrive synchronously, which seriously reduces the timeliness of data processing; with the continuous increase in the number of financial product fields and branches connected, the data processing volume increases sharply and the processing speed gradually slows down; if the repayment data of a certain product field cannot arrive in time or has quality problems, it will affect each other and may have an adverse effect on the data processing of other fields or branches. In view of the above problems, it is urgent to develop a more efficient, flexible and reliable resource recovery amount determination process.
[0049] Based on this, the embodiments of the present application provide a method, device, equipment, medium and program product for determining the resource recovery amount, which can provide a more efficient, flexible and reliable resource recovery amount determination process, can adapt to the asynchrony of data arrival, improve the real-time and accuracy of data processing, and at the same time reduce the mutual influence between different data sources, ensuring that the calculation of resource recovery amount is more accurate and efficient.
[0050] The method for determining the resource recovery amount provided in the embodiment of the present application is described in detail below with reference to the accompanying drawings.
[0051] Figure 1 : is a flow chart of a method for determining resource recovery amount provided in an embodiment of the present application, such as Figure 1 As shown, the method may include steps S110 to S150.
[0052] S110, when receiving user transaction data corresponding to the target resource type and the target service agency, determine the target database table entity corresponding to the target resource type among multiple preset database table entities according to the correspondence between the preset resource type and the database table entity, wherein the user transaction data includes sub-transaction data of different users.
[0053] The target resource type represents the type of resource, that is, the field to which the service belongs. For example, in the financial field, the target resource type can be one of the resource types such as credit card, consumer loan, mortgage, small and micro quick loan, etc.
[0054] The target service organization is an organization or institution that provides specific services or data and is the source of user transaction data. In financial services, it can be a bank, securities company or payment platform; in the e-commerce field, it can be an online retailer or e-commerce platform.
[0055] User transaction data is data records generated when different users conduct transactions on resources of the target resource type at the target service agency, wherein the data records generated when each user conducts transactions at the target service agency can be referred to as sub-transaction data.
[0056] The target database table entity is a database table entity used to store the target resource type.
[0057] Specifically, upon receiving user transaction data of a target resource type and a target service agency, the system selects a target database table entity corresponding to the target resource type from a plurality of preset database tables according to a preset correspondence between resource types and database table entities.
[0058] S120: Determine, among the multiple partitions of the target database table entity, a target partition corresponding to the target service organization according to a preset correspondence relationship between the service organization and the partitions of the database table entity.
[0059] Partitions are independent storage areas that are further subdivided within a database table entity. Through partitions, data in a database table can be stored in different physical locations or storage units according to a certain logic (such as service agencies). For example, different partitions of a target database table entity are used to store user transaction data from different service agencies.
[0060] The correspondence between the preset service agencies and the partitions of the database table entity defines how the data of different service agencies should be allocated to the partitions of the database table entity, which can improve the efficiency and flexibility of data access.
[0061] Specifically, in the target database table entity, the system will automatically identify and locate the specific partition that the target service agency should use, namely the target partition, based on the pre-set correspondence between the service agency and the table partition, to ensure that data from different service agencies can be effectively isolated and independently managed.
[0062] S130, storing the user transaction data in a target partition of a target database table entity.
[0063] Specifically, the system can accurately locate a specific partition in the target database table entity, namely the target partition, based on the preset correspondence, and then store the collected user transaction data safely and orderly in the target partition to ensure clear data classification and efficient management, and facilitate subsequent data analysis, query and other operations, thereby ensuring accurate classification and effective management of data.
[0064] S140, obtaining sub-transaction data of a target user in a target partition of a target database table entity.
[0065] Specifically, after determining the target database table entity and its corresponding target partition, the system can further retrieve and obtain the sub-transaction data of the specific target user in the target partition.
[0066] S150, determining the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user.
[0067] Specifically, by analyzing the sub-transaction data generated when the target user trades resources of the target resource type in a specific service agency, the system can calculate the user's resource recovery amount. This independent processing mechanism for user transaction data effectively reduces the mutual influence between user transaction data and ensures the accuracy and reliability of the calculation of resource recovery amount.
[0068] According to the method for determining the resource recovery amount provided by the embodiment of the present application, when receiving the user transaction data corresponding to the target service agency in the target resource type, in a plurality of preset database table entities, according to the correspondence between the preset resource type and the database table entity, the target database table entity corresponding to the target resource type is determined, wherein the user transaction data includes sub-transaction data of different users, and then in a plurality of partitions of the target database table entity, according to the correspondence between the preset service agency and the partition of the database table entity, the target partition corresponding to the target service agency is determined, and then the user transaction data can be stored in the target partition of the target database table entity, and then the sub-transaction data of the target user is obtained in the target partition of the target database table entity; based on the sub-transaction data of the target user, the resource recovery amount corresponding to the target user is determined. When the user transaction data corresponding to a service agency of a certain resource type arrives, it can be loaded and calculated immediately without waiting for the data of other service agencies or resource types, and can adapt to the asynchrony of data arrival. This independent processing mechanism of user transaction data effectively reduces the mutual influence between user transaction data, ensures the accuracy and reliability of the calculation of resource recovery amount, and has good scalability. When a new resource type or service agency is added, it only needs to simply expand the corresponding table or partition, which is more flexible.
[0069] In some embodiments, the target resource type is any one of a plurality of resource types, and the target service agency is any one of a plurality of service agencies.
[0070] In the embodiment of the present application, the target resource type can be any one of multiple resource types, and the target service agency can be any one of multiple service agencies, so the system can support multiple resource types and service agencies, and the data of each service agency is processed independently, so when the data corresponding to any resource type and service agency arrives, the system can immediately load and calculate without waiting for the data of other service agencies. This adaptability ensures that the system can efficiently process asynchronously arriving data streams.
[0071] Figure 2 This is another flow chart of the method for determining the resource recovery amount provided in the embodiment of the present application.
[0072] In some embodiments, Figure 2 As shown, step S150 determines the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user, and may include steps S151 to S153.
[0073] S151, obtaining the update status of the resource recovery amount corresponding to the target user.
[0074] The update status is a concept that indicates the current processing status of the resource recovery amount corresponding to the target user. It reflects whether the system is updating the user's resource recovery amount. It can include the updating status and the non-updating status.
[0075] For example, the target user may be a co-debt user, and the final determination of the resource recovery amount of the co-debt user needs to be calculated based on the sub-transaction data of the co-debt user trading resources of different resource types in different service agencies. For example, on the Tth day, the co-debt user has n sub-transaction data, and the final resource recovery amount of the co-debt user needs to be calculated based on the n sub-transaction data.
[0076] The updating state means that the system is currently updating the resource recovery amount of the target user. In this state, it means that the system is recalculating the resource recovery amount.
[0077] The non-updating state is the opposite of the "updating state", which means that the system is not currently updating the resource recovery amount of the target user. This usually means that the update operation has been completed, the resource recovery amount has been updated to the latest state, or there is no update operation required.
[0078] Specifically, the latest update status of the user's current resource recovery amount is queried and obtained, including the updating status and the non-updating status.
[0079] S152: When the update status is the updating status, wait for the update status to change from the updating status to the non-updating status.
[0080] Specifically, when the resource recovery amount corresponding to the target user is in the updating state, the system will suspend the current further operations related to the user's resource recovery amount and enter a waiting state. This waiting state will continue until the system detects that the user's resource recovery amount update operation has been completed, that is, the update state changes from the updating state to the non-updating state. At this time, the system will continue to perform subsequent operations or processing related to the user's resource recovery amount. This process ensures that the system can maintain the accuracy and consistency of data when processing the user's resource recovery amount.
[0081] S153, when the update status changes from the updating status to the non-updating status, the resource recovery amount corresponding to the target user is determined based on the sub-transaction data of the target user, and the update status is modified to the updating status.
[0082] Specifically, once it is detected that the target user's resource recovery amount update status has changed from "updating status" to "not updating status", it means that the previous update operation has been completed. At this time, the system will immediately continue to calculate the user's resource recovery amount based on the user's sub-transaction data. While calculating, the update status will be modified to "updating status", which is equivalent to locking the user's resource recovery amount.
[0083] In an embodiment of the present application, when processing a co-debt user with multiple sub-transaction data, first check whether the resource recovery amount of the target user is being updated (i.e., in the updating state). If it is in the updating state, it will wait for the update to be completed. Once the update is completed (the updating state is changed to the non-updating state), the resource recovery amount can continue to be calculated based on the user's sub-transaction data, and the update state can be temporarily changed back to the updating state during this process to lock the calculation process of the resource recovery amount, ensure the accuracy and consistency of the data, prevent conflicts in the update of the resource recovery amount, and efficiently and accurately determine the resource recovery amount of the co-debt user.
[0084] Figure 3 This is another flow chart of the method for determining the resource recovery amount provided in the embodiment of the present application.
[0085] In some embodiments, Figure 3 As shown, step S154 is also included.
[0086] S154, when the update status is not in the updating status, determine the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user, and modify the update status to the updating status.
[0087] Specifically, when the system detects that the target user's resource recovery amount is not currently in the updating process (i.e., the update status is not in the updating state), there is no need to wait, and the resource recovery amount can be calculated immediately based on the user's sub-transaction data. At the same time, in order to mark that the calculation process has started and prevent interference from other concurrent operations, the update status can be modified to the updating state, thereby locking the user's resource recovery amount until the update operation is completed. The embodiment of the present application ensures the accuracy of the resource recovery amount calculation and the consistency of the system processing.
[0088] Figure 4 This is another flow chart of the method for determining the resource recovery amount provided in the embodiment of the present application.
[0089] In some embodiments, Figure 4 As shown, the method for determining the resource recovery amount also includes step S160.
[0090] S160: After determining that the resource recovery amount corresponding to the target user is completed, the update status is changed to a non-updating status.
[0091] Specifically, after determining the resource recovery amount corresponding to the target user, the update status can be changed to a non-updating status, which is actually "unlocking" the resource recovery amount of the user, indicating that the current update operation has been completed and the system no longer locks the resource recovery amount of the user. The embodiment of the present application can ensure the consistency and accuracy of the user's resource recovery amount.
[0092] In some embodiments, you can continue to see Figure 4 , the method for determining the resource recovery amount also includes step S170.
[0093] S170, when the resource recovery amount corresponding to the target user is determined by the user transaction data corresponding to each resource type and each service agency, the usage status of the resource recovery amount corresponding to the target user is updated to an available status.
[0094] The usage status is a status indicator used to identify whether the resource recovery amount can be used by other systems at present. The usage status is "available", which means that the final resource recovery amount of the co-debt user has been successfully calculated.
[0095] Specifically, after the target user's final corresponding resource recovery amount is calculated based on the target user's sub-transaction data under different resource types and different service agencies, the use status of the target user's resource recovery amount can be marked as "available", which means that the resource recovery amount is ready and other systems can query and use this part of the resources. The embodiment of the present application ensures the immediate availability of the information of the resource recovery amount corresponding to the target user, for example, it can be displayed on the front end of the service agency or the user's device, which can improve the user experience and the smoothness of system operation.
[0096] In an example, resource types include credit cards, consumer loans, and mortgages, and service agencies i include service agencies 1 to 37, as shown in Table 1.
[0097] The transaction file of service agency i in Table 1 stores the user transaction records of service agency i, including sub-transaction records of different users.
[0098] Table 1
[0099]
[0100] After the data of the transaction file (user transaction record) of any resource field and any service agency in Table 1 arrives, the transaction file is loaded into the data table partition where the service agency of the resource field is located, and then Spark SQL is used to perform abnormal data cleaning on the processed data and calculate the resource recovery amount of the target user.
[0101] Until the transaction file data of all service agencies of all resource types of the target user is processed, the resource recovery amount of the target user can be marked as available.
[0102] During the entire process, resource types and service agencies are independent of each other and do not affect each other.
[0103] In the embodiment of the present application, when a branch flow file (user transaction data of a service agency) of a certain product field (resource type) arrives, it can be loaded and calculated immediately without waiting for data from other branches (other service agencies) or other product fields (other resource types), and can adapt to the asynchrony of data arrival. This independent processing mechanism for user transaction data effectively reduces the mutual influence between user transaction data, ensures the accuracy and reliability of the calculation of resource recovery amount, and has good scalability. When new resource types or service agencies are added, it is only necessary to simply expand the corresponding tables or partitions, which is more flexible.
[0104] In one example, Spark's fault-tolerant mechanism (generating a copy of the stream file) can be used to ensure that even in the event of partial node failure (the main stream file is lost), data processing can still remain consistent and stable based on the stream file copy, thereby ensuring business continuity and data integrity.
[0105] Based on the same inventive concept, the embodiment of the present application also provides a device for determining resource recovery amount, such as Figure 5 As shown, the device 500 may include a determination module 510 , a storage module 520 and an acquisition module 530 .
[0106] The determination module 510 is used to determine the target database table entity corresponding to the target resource type according to the preset correspondence between the resource type and the database table entity among a plurality of preset database table entities when receiving the user transaction data corresponding to the target resource type and the target service organization, wherein the user transaction data includes sub-transaction data of different users;
[0107] The determination module 510 is further used to determine the target partition corresponding to the target service organization among the multiple partitions of the target database table entity according to the preset correspondence relationship between the service organization and the partition of the database table entity;
[0108] Storage module 520, used to store user transaction data into a target partition of a target database table entity;
[0109] An acquisition module 530 is used to acquire sub-transaction data of a target user in a target partition of a target database table entity;
[0110] The determination module 510 is further used to determine the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user.
[0111] According to the resource recovery amount determination device provided by the embodiment of the present application, when receiving the user transaction data corresponding to the target service agency in the target resource type, in multiple preset database table entities, according to the correspondence relationship between the preset resource type and the database table entity, the target database table entity corresponding to the target resource type is determined, wherein the user transaction data includes sub-transaction data of different users, and then in multiple partitions of the target database table entity, according to the correspondence relationship between the preset service agency and the partition of the database table entity, the target partition corresponding to the target service agency is determined, and then the user transaction data can be stored in the target partition of the target database table entity, and then the sub-transaction data of the target user is obtained in the target partition of the target database table entity; based on the sub-transaction data of the target user, the resource recovery amount corresponding to the target user is determined. When the user transaction data corresponding to a service agency of a certain resource type arrives, it can be loaded and calculated immediately without waiting for the data of other service agencies or resource types, and can adapt to the asynchrony of data arrival. This independent processing mechanism of user transaction data effectively reduces the mutual influence between user transaction data, ensures the accuracy and reliability of resource recovery amount calculation, and has good scalability. When a new resource type or service agency is added, it only needs to simply expand the corresponding table or partition, which is more flexible.
[0112] In some embodiments, the target resource type is any one of a plurality of resource types, and the target service agency is any one of a plurality of service agencies.
[0113] In some embodiments, the determination module is used to determine the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user, and can be specifically used to:
[0114] Get the updated status of the resource recovery amount corresponding to the target user;
[0115] When the update state is in the updating state, the waiting update state is changed from the updating state to the non-updating state;
[0116] When the update status changes from the updating status to the non-updating status, the resource recovery amount corresponding to the target user is determined based on the sub-transaction data of the target user, and the update status is modified to the updating status.
[0117] In some embodiments, the apparatus further comprises:
[0118] The determination module is also used to determine the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user when the update status is not in the updating status, and to modify the update status to the updating status.
[0119] In a possible embodiment of the first aspect, the device further includes a modification module:
[0120] The modification module is used to modify the update status to a non-updating status after determining that the resource recovery amount corresponding to the target user is completed.
[0121] In some embodiments, the apparatus further comprises an update module:
[0122] The updating module is used to update the usage status of the resource recovery amount corresponding to the target user to an available status when the resource recovery amount corresponding to the target user is determined by the user transaction data corresponding to each resource type and each service agency.
[0123] Each module in the resource recovery amount determination device provided in the embodiment of the present application can realize Figures 1 to 4 The functions of each step of the provided method for determining the resource recovery amount and its ability to achieve the corresponding technical effects are described briefly and will not be repeated here.
[0124] Figure 6 A schematic diagram of the hardware structure of a device for determining a resource recovery amount provided in an embodiment of the present application is shown.
[0125] The resource recovery amount determination device may include a processor 601 and a memory 602 storing computer program instructions.
[0126] Specifically, the processor 601 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.
[0127] The memory 602 may include a large capacity memory for data or instructions. For example, but not limitation, the memory 602 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 602 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 602 may be inside or outside the determining device of the resource recovery amount. In a specific embodiment, the memory 602 is a non-volatile solid-state memory.
[0128] The memory may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of the present disclosure.
[0129] The processor 601 reads and executes the computer program instructions stored in the memory 602 to implement any one of the resource recovery amount determination methods in the above embodiments.
[0130] In one example, the resource recovery amount determination device may further include a communication interface 603 and a bus 604. Figure 6 As shown, the processor 601, the memory 602, and the communication interface 603 are connected via a bus 604 and communicate with each other.
[0131] The communication interface 603 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.
[0132] The bus 604 includes hardware, software, or both, coupling the components of the resource recovery amount determination device to each other. For example, but not limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an InfiniBand interconnect, a Linear Predictive Coding (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (Peripheral Component Interconnect-X, PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VESA Local Bus, VLB) bus, or other suitable buses or a combination of two or more of these. Where appropriate, the bus 604 may include one or more buses. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.
[0133] The device can execute the resource recovery amount determination method in the embodiment of the present application based on each unit / component in the resource recovery amount determination device, thereby realizing the combination of Figures 1 to 4 Describes the method for determining resource recovery amounts.
[0134] In addition, in combination with the method for determining the resource recovery amount in the above embodiment, the embodiment of the present application can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by the processor, any one of the methods for determining the resource recovery amount in the above embodiment is implemented.
[0135] The present application also provides a computer program product. When the instructions in the computer program product are executed by a processor of an electronic device, the electronic device executes each process of any one of the above-mentioned resource recovery amount determination method embodiments.
[0136] It should be clear that the present application is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present application is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present application.
[0137] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), appropriate firmware, plug-in, function card, etc. When implemented in software, the elements of the present application are programs or code segments used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or communication link by a data signal carried in a carrier. "Machine-readable medium" may include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (Read-Only Memory, ROM), flash memory, erasable read-only memory (Erasable Read Only Memory, EROM), floppy disks, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical discs, hard disks, optical fiber media, radio frequency (Radio Frequency, RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.
[0138] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiment, or in a different order from the embodiment, or several steps can be performed simultaneously.
[0139] Aspects of the present disclosure are described above with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field programmable logic circuit. It can also be understood that each box in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can also be implemented by dedicated hardware that performs a specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions.
[0140] The above are only specific implementation methods of the present application. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present application is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the protection scope of this application.
Claims
1. A method for determining resource recovery amount, characterized in that: include: In the case of receiving user transaction data corresponding to a target resource type and a target service agency, determining a target database table entity corresponding to the target resource type among a plurality of preset database table entities according to a preset correspondence between resource types and database table entities, wherein the user transaction data includes sub-transaction data of different users; Among the multiple partitions of the target database table entity, determine the target partition corresponding to the target service organization according to the preset correspondence relationship between the service organization and the partition of the database table entity; storing the user transaction data in the target partition of the target database table entity; In the target partition of the target database table entity, obtaining sub-transaction data of a target user; Based on the sub-transaction data of the target user, determine the resource recovery amount corresponding to the target user.
2. The method according to claim 1, characterized in that The target resource type is any one of a plurality of resource types, and the target service agency is any one of a plurality of service agencies.
3. The method according to claim 1, characterized in that The determining, based on the sub-transaction data of the target user, a resource recovery amount corresponding to the target user includes: Obtaining the update status of the resource recovery amount corresponding to the target user; When the update state is in the updating state, waiting for the update state to change from the updating state to the non-updating state; When the update state changes from the updating state to the non-updating state, the resource recovery amount corresponding to the target user is determined based on the sub-transaction data of the target user, and the update state is modified to the updating state.
4. The method according to claim 3, characterized in that Also includes: When the update status is a non-updating status, the resource recovery amount corresponding to the target user is determined based on the sub-transaction data of the target user, and the update status is modified to an updating status.
5. The method according to claim 3, characterized in that: Also includes: After the determination of the resource recovery amount corresponding to the target user is completed, the update state is modified to a non-updating state.
6. The method according to any one of claims 1 to 5, characterized in that: Also includes: In the case where the resource recovery amount corresponding to the target user is determined by user transaction data corresponding to each resource type and each service agency, the usage status of the resource recovery amount corresponding to the target user is updated to an available status.
7. A device for determining resource recovery amount, characterized in that: include: A determination module, configured to, upon receiving user transaction data corresponding to a target resource type and a target service agency, determine a target database table entity corresponding to the target resource type from among a plurality of preset database table entities according to a correspondence between preset resource types and database table entities, wherein the user transaction data includes sub-transaction data of different users; The determination module is further used to determine the target partition corresponding to the target service organization among the multiple partitions of the target database table entity according to the preset correspondence relationship between the service organization and the partition of the database table entity; A storage module, used for storing the user transaction data in the target partition of the target database table entity; An acquisition module, used for acquiring sub-transaction data of a target user in the target partition of the target database table entity; The determination module is further used to determine the resource recovery amount corresponding to the target user based on the sub-transaction data of the target user.
8. A device for determining resource recovery amount, characterized in that: The device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the method for determining the resource recovery amount according to any one of claims 1 to 6 is implemented.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method for determining the resource recovery amount according to any one of claims 1 to 6 is implemented.
10. A computer program product, characterized in that When the instructions in the computer program product are executed by a processor of a device, the device is enabled to execute the method for determining a resource recovery amount as described in any one of claims 1 to 6.