CN111708849A - Data management method, device, equipment and storage medium - Google Patents

Data management method, device, equipment and storage medium Download PDF

Info

Publication number
CN111708849A
CN111708849A CN202010559232.6A CN202010559232A CN111708849A CN 111708849 A CN111708849 A CN 111708849A CN 202010559232 A CN202010559232 A CN 202010559232A CN 111708849 A CN111708849 A CN 111708849A
Authority
CN
China
Prior art keywords
quota
credit
limit
user
node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010559232.6A
Other languages
Chinese (zh)
Inventor
吴岘辉
陈龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Tongbang Zhuoyi Technology Co ltd
Original Assignee
Beijing Tongbang Zhuoyi Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Tongbang Zhuoyi Technology Co ltd filed Critical Beijing Tongbang Zhuoyi Technology Co ltd
Priority to CN202010559232.6A priority Critical patent/CN111708849A/en
Publication of CN111708849A publication Critical patent/CN111708849A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28Databases characterised by their database models, e.g. relational or object models
    • G06F16/283Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03Credit; Loans; Processing thereof

Abstract

The embodiment of the invention provides a data management method, a device, equipment and a storage medium, wherein the method comprises the following steps: if a first quota related service request triggered by a user is received, determining quota system configuration information corresponding to the user; constructing a credit data tree structure corresponding to the user according to the credit system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer; and managing the related business of the quota corresponding to the user according to the quota data tree structure. Because the limit data tree structure is adopted to manage the limit data in the user limit system, the limit data tree structure can manage the data in a layered and top-down manner, so that the limit data management with various dimensionalities can be realized, the data management is complete enough, and the data can be managed efficiently and accurately.

Description

Data management method, device, equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a data management method, a data management device, data management equipment and a storage medium.
Background
With the rapid development of computer technology and information technology, data generated by industrial application is explosively increased, and the data needs to be managed efficiently and safely.
Illustratively, in the field of network loan, the responsibility of the credit line center is to maintain the credit line system of the client, and provide the functions of initializing, freezing, unfreezing, occupying, recovering, invalidating, increasing and decreasing the credit line data.
In the existing management method for the data of the quota system, the quota data is simply divided into the dimensionality of the total quota of the client and the dimensionality of the product of the client to manage the quota data, so that the dimensionality of quota data management is single, the management is not comprehensive enough, and the data cannot be efficiently and accurately managed.
Disclosure of Invention
Embodiments of the present invention provide a data management method, an apparatus, a device, and a storage medium, which solve the technical problems in the prior art that the data management for the quota has a single dimension, the management is not comprehensive enough, and the data cannot be efficiently and accurately managed.
In a first aspect, an embodiment of the present invention provides a data management method, including:
if a first quota related service request triggered by a user is received, determining quota system configuration information corresponding to the user; establishing a quota data tree structure corresponding to the user according to the quota system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer; and managing the related business of the quota corresponding to the user according to the quota data tree structure.
In a second aspect, an embodiment of the present invention provides a data management apparatus, including:
the system comprises a configuration information determining module, a first limit system configuration module and a second limit system configuration module, wherein the configuration information determining module is used for determining limit system configuration information corresponding to a user if a first limit related service request triggered by the user is received; the tree structure construction module is used for constructing a credit data tree structure corresponding to the user according to the credit system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer; and the data management module is used for managing the related business of the quota corresponding to the user according to the quota data tree structure.
In a third aspect, an embodiment of the present invention provides an electronic device, including: a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any of the first aspects.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, the computer program being executed by a processor to implement the method according to any one of the first aspect.
The embodiment of the invention provides a data management method, a device, equipment and a storage medium, wherein if a first quota related service request triggered by a user is received, quota system configuration information corresponding to the user is determined; constructing a credit data tree structure corresponding to the user according to the credit system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer; and managing the related business of the quota corresponding to the user according to the quota data tree structure. Because the limit data tree structure is adopted to manage the limit data in the user limit system, the limit data tree structure can manage the data in a layered and top-down manner, so that the limit data management with various dimensionalities can be realized, the data management is complete enough, and the data can be managed efficiently and accurately.
It should be understood that what is described in the summary above is not intended to limit key or critical features of embodiments of the invention, nor is it intended to limit the scope of the invention. Other features of the present invention will become apparent from the following description.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a flowchart of a data management method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating a structure of a credit tree according to an embodiment of the present invention;
fig. 3 is a flowchart of a data management method according to a second embodiment of the present invention;
fig. 4 is a flowchart of step 201 in the data management method according to the second embodiment of the present invention;
FIG. 5 is a diagram illustrating a first usage state of a template configuration interface according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating a second usage state of a template configuration interface according to an embodiment of the present invention;
FIG. 7 is a schematic illustration of a first product configuration interface in an embodiment of the invention;
FIG. 8 is a schematic illustration of a second product configuration interface in an embodiment of the invention;
FIG. 9 is a schematic illustration of a third product configuration interface in an embodiment of the invention;
FIG. 10 is a flowchart illustrating step 204 of a data management method according to a second embodiment of the present invention;
fig. 11 is a first flowchart of step 2043 of the data management method according to the second embodiment of the present invention;
FIG. 12 is a second flowchart of step 2043 of the data management method according to the second embodiment of the present invention;
fig. 13 is a schematic structural diagram of a data management apparatus according to a third embodiment of the present invention;
fig. 14 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present invention are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present invention. It should be understood that the drawings and the embodiments of the present invention are illustrative only and are not intended to limit the scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, and in the above-described drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
For clear understanding of the technical solutions of the present application, the terms involved are explained first:
the credit data tree structure is abbreviated as: the quota tree, after modeling the quota system by adopting the tree structure, is called the image of the quota system, in the following embodiment, for the convenience of description, the quota tree is used to represent the quota data tree structure.
Quota nodes: the specific node in the quota tree can be associated with the father node and the child node according to the position of the quota node in the quota tree.
And (3) a quota tree root node: the special quota node is positioned at the topmost layer of the quota tree, only the child node is associated, and no parent node is arranged.
Limit tree leaf node: the special quota node is positioned at the bottommost layer of the quota tree, has no child node, and only can be associated with the parent node.
Credit remaining amount: the remaining value after the frozen quota and the occupied quota are subtracted from the credit quota.
The quota cycle attribute is as follows: the attribute of whether the credit line of the client can be reused or not.
The embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
Example one
Fig. 1 is a flowchart of a data management method according to an embodiment of the present invention, and as shown in fig. 1, an execution subject of the embodiment is a data management device. The data management apparatus may be integrated in an electronic device, and the data management method provided in this embodiment includes the following steps.
Step 101, if a first quota related service request triggered by a user is received, determining quota system configuration information corresponding to the user.
The first quota related service request is a request for triggering and constructing a quota data tree structure corresponding to the user. Such as may be a trusted application request.
In this embodiment, the user is a client that operates a client corresponding to the data management method in the electronic device or a client that transacts a business related to the quota via a web page.
In this embodiment, the user may trigger the first quota related service request by operating a client or an operation interface of a web page corresponding to the data management method in the electronic device. And after triggering the first quota related service request, determining quota system configuration information corresponding to the user.
Wherein, the configuration information of the quota system comprises configuration information for constructing a quota tree corresponding to the user. The quota tree comprises: the multilayer credit node can comprise: root node, middle layer limit node, and leaf node. Therefore, the quota system configuration information may specifically include: general quota template information, attribute information of leaf quota nodes, additional quota information and the like.
In this embodiment, the general quota template information may be quota template information that is pre-configured and shared by all users before the user opens the first quota related service, and the quota template information may include: the parent-child relationship of each layer of quota nodes in the quota data tree structure and the quota calculation strategy of non-leaf quota nodes.
In this embodiment, the leaf credit node is a credit node corresponding to a specific product, so the attribute information of the leaf node may include: currency type, whether the currency type can be recycled, whether the currency type is independent of the credit line tree and the like.
In this embodiment, the additional credit information of the leaf credit node may include: limit value of credit line, line recovery mode, and associated configuration information of product and product line node.
Step 102, establishing a credit data tree structure corresponding to a user according to credit system configuration information; the credit data tree structure comprises a plurality of layers of credit nodes, and each layer of credit node except the leaf credit node represents a management dimension node of a corresponding layer.
In this embodiment, the credit tree corresponding to the user is constructed according to the credit system configuration information. The constructed limit tree comprises multilayer limit nodes, and the multilayer limit nodes comprise: root node, middle layer limit node, and leaf node. It is possible to represent the management dimension node of the corresponding hierarchy with each level credit node except the leaf credit node.
Illustratively, as shown in fig. 2, the credit tree has 4 credit nodes, except for the lowest layer where the leaf credit node is located, each layer on the upper layer of the leaf credit node represents one management dimension, that is, three credit management nodes. The first layer only has one root limit node which is fixed as the comprehensive limit management dimension of the user and represents the comprehensive limit information of the user. The second layer represents the loan product type management dimensionality and can be divided into two sub-classes of credit loan lines and mortgage loan lines, wherein one sub-class is represented by a line node. The third layer represents the partner type management dimension and can be divided into two sub-categories of self-supporting product quota and non-self-supporting product quota.
As shown in fig. 2, the client has line information under four products of the product A, B, C, D, and the four product line information are respectively hung on four bottommost leaf line nodes of the line tree.
And 103, managing the related business of the quota corresponding to the user according to the quota data tree structure.
In this embodiment, since each layer of credit nodes except leaf nodes represents management dimension nodes of a corresponding layer, the credit tree can be used to manage the credit related services of the user according to the subsequent transaction of the specific credit related services of the user.
For example, when a user performs a loan transaction, the credit line tree can be used to adjust the credit line, the frozen line and the occupied line of each layer of line node. When the user generates a payment service, the related quota can be adjusted through the quota tree.
In the data management method provided by this embodiment, if a first quota-related service request triggered by a user is received, quota system configuration information corresponding to the user is determined; constructing a credit data tree structure corresponding to the user according to the credit system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer; and managing the related business of the quota corresponding to the user according to the quota data tree structure. Because the limit data tree structure is adopted to manage the limit data in the user limit system, the limit data tree structure can manage the data in a layered and top-down manner, so that the limit data management with various dimensionalities can be realized, the data management is complete enough, and the data can be managed efficiently and accurately.
Example two
Fig. 3 is a flowchart of a data management method according to a second embodiment of the present invention, and as shown in fig. 3, the data management method according to the present embodiment is further detailed in steps 101 to 103 on the basis of the data management method according to the first embodiment of the present invention, and the data management method according to the present embodiment includes the following steps.
Step 201, if a first quota related service request triggered by a user is received, determining quota system configuration information corresponding to the user.
The first quota related service request may be a credit application request.
As an alternative implementation, as shown in fig. 4, in this embodiment, step 201 includes the following steps:
step 2011, obtaining the universal quota template information configured through the template configuration interface, where the universal quota template information includes: the parent-child relationship of each layer of quota nodes in the quota data tree structure and the quota calculation strategy of non-leaf quota nodes.
In this embodiment, before the user transacts the credit related service, the manager may configure the universal credit template information through the template configuration interface, where the universal credit template configuration information is the credit template information shared by all users.
Wherein, general quota template information includes: the parent-child relationship of each layer of quota nodes in the quota data tree structure and the quota calculation strategy of non-leaf quota nodes. So exemplarily, as shown in fig. 5, the control of structure editing and the control of node rule editing are in the template configuration interface. If the current hierarchy is the first hierarchy, the first-layer quota node is a root node and only one root node can be maintained, so that quota nodes cannot be added in the hierarchy content editing interface. If the current level is not the first level, a limit node can be added, after clicking and storing, the node can appear in the left template configuration interface, and editing or deleting operation can be carried out on each limit node. Through the configuration of the limit tree structure, the hierarchy of the limit tree can be set, namely the limit system control dimension and the sub-number of each control dimension, specifically expressed as the limit node number of each layer.
After the structure is edited and the node rule editing control is clicked, illustratively, as shown in fig. 6, the generated initial quota tree appears on the template configuration interface, the editing node rule interface is displayed on the right side, and the administrator can set the node rule, that is, the quota calculation policy of the non-leaf quota node, through editing.
Wherein, because the basic attribute of the quota of each quota node comprises: the credit limit, the frozen limit and the occupied limit are arranged in the limit calculation strategy of the non-leaf limit node configured in the template configuration interface, the credit limit of the non-leaf limit node is generated according to the limit calculation strategy and the credit limits of all the sub-nodes, and the specific limit calculation strategy comprises the strategies of summation, big calculation, small calculation and the like. Or an irrelevant strategy can be set, if the strategy is the irrelevant strategy, the credit line of the current non-leaf line node can be generated by the line-related wind control strategy model and is irrelevant to the credit line of the child node. Similarly, the frozen quota and the occupied quota can also be generated by summing according to the frozen quota and the occupied quota of all the child nodes, if the quota node is a leaf node, the credit quota is default to zero, and meanwhile, the credit quota is not involved in the calculation of the credit quota of the parent quota node. The frozen quota and the occupied quota are also defaulted to zero, but participate in the generation of the frozen quota and the occupied quota of the parent node.
In this embodiment, by configuring the line calculation policy of the non-leaf line node, the calculation policies of the credit line, the frozen line, and the occupied line in each non-leaf node can be configured.
It can be understood that, when the general quota template information configured on the template configuration interface is configured, the configuration can be performed before the user opens the quota related service, or after the user opens the quota related service, the parent-child relationship of each quota node in the quota tree in the general quota template information and the quota calculation strategy of the non-leaf quota node can be changed in real time according to the actual service quota risk change, so as to achieve the purpose of adjusting the general quota template information in time.
Step 2012, obtaining attribute information of the product corresponding to the leaf amount node configured through the first product configuration interface or the second product configuration interface.
In this embodiment, the leaf credit node is a credit node of a specific product, so that the leaf credit node may be affiliated to the credit tree or not, but may be managed separately as an independent credit node according to the credit-related service requirement.
If the leaf limit node is attached to the limit tree, the attribute information of the product corresponding to the leaf limit node can be configured through the first product configuration interface. As shown in fig. 7, in the first product configuration interface, the administrator may configure the attribute information of the product corresponding to the leaf credit node by inputting or selecting.
If the leaf limit node is not affiliated to the limit tree, the attribute information of the product corresponding to the leaf limit node can be configured through the second product configuration interface. As shown in fig. 8, in the second product configuration interface, the administrator may configure the attribute information of the product corresponding to the leaf credit node by inputting or selecting.
Wherein, the attribute information of the product corresponding to the leaf quota node may include: currency type, whether the money can be recycled, whether the money is hung on a limit tree and the like.
And 2013, acquiring additional quota information of the product corresponding to the leaf quota node configured through the third product configuration interface.
In this embodiment, as shown in fig. 9, in the third product configuration interface, the administrator may configure the additional credit information of the product corresponding to the leaf credit node by inputting or selecting.
Wherein, the additional amount information may include: the upper limit of the credit limit of the product, the limit recovery mode, the association configuration of the product and the leaf limit node and the like. The association configuration of the products and the leaf limit nodes can be associated by selecting the product names corresponding to the leaf limit nodes.
It should be noted that, in order to ensure that the credit tree structure of the credit system is clear, the leaf credit nodes and the products are in one-to-one correspondence, that is, one product can only be associated with one leaf credit node, and one leaf credit node can only be associated with one product.
It can be understood that when configuring the attribute information and the additional limit information of the leaf limit node, after completing the configuration of the general template information, the attribute information and the additional limit information of the product corresponding to different leaf limit nodes can be configured, so as to achieve the purpose of flexibly configuring the leaf limit node.
Step 202, generating an initial quota data tree structure according to the parent-child relationship of each quota node.
Step 203, configuring the non-leaf limit nodes in the initial limit data tree structure according to the limit calculation strategy of the non-leaf limit nodes, and configuring the leaf limit nodes according to the attribute information and the additional limit information of the leaf limit nodes to generate a limit data tree structure.
Specifically, in this embodiment, the parent-child relationship of each level of the credit node in the credit tree configured in the general credit template information is obtained, so as to generate the initial credit tree displayed in the template configuration interface as shown in fig. 6. And then obtaining the configured quota calculation strategy of the non-leaf quota node so as to configure the non-leaf quota node in the initial quota data tree structure. And finally, acquiring the attribute information and the additional limit information of the configured leaf limit nodes so as to configure the leaf limit nodes. After the configuration of each quota node is completed, the generated quota tree can manage the multidimensional quota data.
In the data management method provided by this embodiment, when constructing the quota tree, an initial quota data tree structure is generated according to the parent-child relationship of each quota node; the non-leaf limit nodes in the initial limit data tree structure are configured according to the limit calculation strategy of the non-leaf limit nodes, the leaf limit nodes are configured according to the attribute information and the additional limit information of the leaf limit nodes to generate the limit data tree structure, data in a limit system can be managed in a limit tree mode in a layered and top-down mode, and therefore limit data management of multiple dimensions can be achieved, data management is comprehensive enough, and data can be managed efficiently and accurately.
Step 204, managing the related business of the quota corresponding to the user according to the quota data tree structure.
Optionally, as an optional implementation manner, in this embodiment, step 204 includes the following step 2041.
Step 2041, if the first amount-related service request is a credit granting application request, determining whether the user is a credit granting user; if the user is a credit user, initializing the basic attribute of the quota on the quota tree; the basic attributes of the quota include: credit line, frozen line and occupied line.
Specifically, in this embodiment, before the user transacts the loan service or the repayment service, the user needs to perform a credit granting application, so that the first credit line related service request triggered by the user is received first may be a credit granting application request. After receiving the credit application request, carrying out risk assessment on the credit condition of the user according to the credit tree corresponding to the user, and if the user is determined to be the credit user, carrying out basic attribute initialization on the credit tree. The credit line is generated according to the line-related wind control strategy model when the user applies for credit, and the frozen line and the occupied line can be initialized to be zero.
As an alternative implementation, as shown in fig. 10, in this embodiment, step 204 includes the following steps 2042 and 2043.
Step 2042, receiving the service request related to the second quota triggered by the user.
Specifically, in this embodiment, after the user is a credit granting user, the user may trigger a second amount-related service request, which may be a loan application request and a repayment application request.
Step 2043, the basic quota attributes of each quota node are adjusted according to the second quota related service request.
As an alternative embodiment, as shown in FIG. 11, step 2043 includes steps 2043 a-2043 d.
Step 2043a, obtain credit remaining amount.
Specifically, in this embodiment, if the loan application is the first loan application after the user is determined to be the credit granting user, the credit remaining amount is the credit amount initialized for the amount tree. And storing the credit remaining amount into the amount tree after completing the loan each time, and further acquiring the credit remaining amount. When the credit surplus limit is stored in the limit tree, the related limit nodes all store the corresponding credit surplus limit.
Step 2043b, determine if the credit remaining amount is greater than the loan application amount, if yes, go to step 2043c, otherwise go to step 2043 d.
Specifically, in this embodiment, when receiving the credit application request, the credit application request includes a loan application amount, and it is checked from a leaf amount node layer by layer according to the loan application amount whether the credit remaining amount of the relevant amount node is greater than the loan application amount, and only when the credit remaining amounts of all the amount nodes can be greater than or equal to the loan application amount, it is determined that the credit remaining amount is greater than or equal to the loan application amount.
And 2043c, adjusting the frozen quota and the occupied quota corresponding to each quota node in the quota data tree structure from bottom to top according to the loan application quota.
Specifically, in this embodiment, if it is determined that the credit remaining amount is greater than the loan application amount, the corresponding amount value is frozen in each layer of amount node in the amount data tree structure from bottom to top according to the loan application amount after the loan is issued, that is, the frozen amount is adjusted. When the user loan is successfully issued, the corresponding amount is unfrozen according to the loan application amount, and the corresponding amount is immediately occupied, namely the frozen amount and the occupied amount are adjusted.
Step 2043d, the user is denied a loan application.
Specifically, in this embodiment, since the credit remaining amount is less than the loan application amount, the user is not qualified to loan in the corresponding loan application amount, so that the user is denied the loan application, for example, a prompt message indicating that the loan application amount is too high may be displayed on the interface.
The data management method provided by the embodiment can effectively and reasonably manage the loan service of the user because the limit tree is reasonably configured in advance when the loan service of the user is managed.
As an alternative embodiment, as shown in fig. 12, step 2043 includes steps 2043 e-2043 g.
Step 2043e, the loan cycle attribute corresponding to the loan amount node in the line data tree structure is obtained.
In this embodiment, the corresponding leaf limit node is determined according to the product of the loan application, and then the loan cycle attribute corresponding to the loan limit node is determined according to the configuration information of the leaf limit node.
The loan cycle attribute may be a cycle attribute or a non-cycle attribute.
Step 2043f, if the loan cycle attribute is a cycle attribute, adjusting the occupied amount according to the repayment application amount.
And 2043g, if the loan cycle attribute is a non-cycle attribute, keeping the occupied amount unchanged according to the repayment application amount.
Specifically, in this embodiment, after the loan is successfully delivered to the user, the credit line corresponding to the loan application line is occupied, that is, the occupied line is increased, and the available credit line is decreased. If the loan cycle attribute is the cycle attribute, the corresponding occupancy amount can be recovered after the payment of the user, and the user can generate the loan again. If the loan cycle attribute is a non-cycle attribute, the corresponding occupation amount is not recovered after the user repays the loan, namely, the corresponding occupation amount is kept unchanged. The occupied amount can only increase continuously when the loan application amount increases, and when the credit line granted by the user is used up, the loan cannot occur again.
In the data management method provided by the embodiment, when the repayment service of the user is managed, the loan cycle attribute is reasonably configured in advance, so that the repayment service can be effectively and reasonably managed according to the loan cycle attribute.
It can be understood that the service request related to the second quota may also be an increase request, a decrease request, and the like, which is not limited in this embodiment.
As an alternative implementation, as shown in fig. 3, in this embodiment, after step 204, the following steps are further included:
step 205, receiving a service display request triggered by a user.
Specifically, in this embodiment, a service display control may be set in the interface, and the user triggers the service display request by clicking the service display control.
And step 206, displaying the credit data tree structure in a tree connection mode according to the service display request.
In this embodiment, after the user clicks the service display control to trigger the service display request, the service is displayed in the form of a quota tree, as shown in fig. 2.
Step 207, receiving a statistical request for a quota node triggered by a user.
Specifically, in this embodiment, in the interface, a control may be set on each credit node, and the user triggers a statistical request for the credit node by clicking the credit node that needs to be subjected to credit statistics.
Step 208, responding to the statistical request, and displaying the quota statistical information of the quota node.
Specifically, in this embodiment, in response to the statistics request, the quota statistics information of the quota node may be displayed in the form of a window or an interface.
In the data management method provided by this embodiment, a service display request triggered by a user is received; displaying a credit data tree structure in a tree connection mode according to the service display request; receiving a statistical request for a certain quota node triggered by a user; and responding to the counting request, and displaying the quota counting information of the quota node. Visual display and different levels and dimensionality of the quota data can be achieved, the quota data can be managed visually, and user experience is improved.
EXAMPLE III
Fig. 13 is a schematic structural diagram of a data management apparatus according to a third embodiment of the present invention, and as shown in fig. 13, a data management apparatus 1300 according to the present embodiment includes: a configuration information determining module 1301, a tree structure constructing module 1302 and a data management module 1303.
The configuration information determining module 1301 is configured to determine, if a first quota related service request triggered by a user is received, quota system configuration information corresponding to the user. A tree structure building module 1302, configured to build a credit data tree structure corresponding to the user according to the credit system configuration information; the credit data tree structure comprises a plurality of layers of credit nodes, and each layer of credit node except the leaf credit node represents a management dimension node of a corresponding layer. And the data management module 1303 is used for managing the business related to the quota corresponding to the user according to the quota data tree structure.
The data management apparatus provided in this embodiment may execute the technical solution of the method embodiment shown in fig. 1, and the implementation principle and the technical effect are similar, which are not described herein again.
Further, the data management apparatus provided in this embodiment further includes: and a data display module.
Optionally, the quota system configuration information corresponding to the user includes: general quota template information, attribute information of leaf quota nodes and additional quota information;
the configuration information determining module 1301 is specifically configured to:
acquiring general quota template information configured through a template configuration interface, wherein the general quota template information comprises: the parent-child relationship of each layer of quota nodes in the quota data tree structure and the quota calculation strategy of non-leaf quota nodes; acquiring attribute information of a product corresponding to a leaf credit node configured through a first product configuration interface or a second product configuration interface; and acquiring additional quota information of the product corresponding to the leaf quota node configured through the third product configuration interface.
Optionally, the tree structure building module 1302 is specifically configured to:
generating an initial quota data tree structure according to the parent-child relationship of each quota node; and configuring the non-leaf limit nodes in the initial limit data tree structure according to the limit calculation strategy of the non-leaf limit nodes, and configuring the leaf limit nodes according to the attribute information and the additional limit information of the leaf limit nodes to generate a limit data tree structure.
Optionally, the data management module 1303 is specifically configured to:
if the first limit related service request is a credit granting application request, judging whether the user is a credit granting user; if the user is a credit user, initializing the basic attribute of the quota on the quota tree; the basic attributes of the quota include: credit line, frozen line and occupied line.
Optionally, the data management module 1303 is specifically configured to:
receiving a second quota related service request triggered by a user; and adjusting the basic quota attributes of each quota node according to the second quota related service request.
Optionally, the service request related to the second amount is a loan application request, where the loan application request includes: applying for the credit;
the data management module 1303, when adjusting the basic quota attributes of the quota nodes of each tier according to the second quota related service request, is specifically configured to:
obtaining a credit remaining amount; judging whether the credit remaining amount is larger than the loan application amount; and if the credit remaining amount is determined to be larger than or equal to the loan application amount, adjusting the frozen amount and the occupied amount corresponding to each layer of amount node in the amount data tree structure from bottom to top according to the loan application amount.
Optionally, the service request related to the second amount is a repayment application request, where the repayment application request includes: repayment application limit;
the data management module 1303, when adjusting the basic quota attributes of the quota nodes of each tier according to the second quota related service request, is specifically configured to:
obtaining loan cycle attributes corresponding to loan amount nodes in an amount data tree structure; if the loan cycle attribute is the cycle attribute, adjusting the occupation amount according to the repayment application amount; if the loan cycle attribute is a non-cycle attribute, keeping the occupation amount unchanged according to the repayment application amount.
Optionally, the data display module is specifically configured to:
receiving a service display request triggered by a user; displaying a credit data tree structure in a tree connection mode according to the service display request; receiving a statistical request for a certain quota node triggered by a user; and responding to the counting request, and displaying the quota counting information of the quota node.
The data management apparatus provided in this embodiment may execute the technical solutions of the method embodiments shown in fig. 3 to 4 and fig. 10 to 12, and the implementation principles and technical effects thereof are similar and will not be described herein again.
Example four
Fig. 14 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention, and as shown in fig. 14, an electronic device 1400 according to a fourth embodiment of the present invention includes: memory 1401, processor 1402, and computer programs.
Wherein the computer program is stored in the memory 1401 and configured to be executed by the processor 1402 to implement the data management method provided by any one of the embodiments of the present invention. The related descriptions and effects corresponding to the steps in the drawings can be correspondingly understood, and redundant description is not repeated here.
In this embodiment, the memory 1401 and the processor 1402 are connected by a bus.
EXAMPLE five
Fifth embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the data management method provided in any embodiment of the present invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware form, and can also be realized in a form of hardware and a software functional module.
Program code for implementing the methods of the present invention may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present invention, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
Further, while operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (18)

1. A method for managing data, comprising:
if a first quota related service request triggered by a user is received, determining quota system configuration information corresponding to the user;
establishing a quota data tree structure corresponding to the user according to the quota system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer;
and managing the related business of the quota corresponding to the user according to the quota data tree structure.
2. The method of claim 1, wherein the credit system configuration information corresponding to the user comprises: general quota template information, attribute information of leaf quota nodes and additional quota information;
the determining of the quota system configuration information corresponding to the user includes:
acquiring general quota template information configured through a template configuration interface, wherein the general quota template information comprises: the parent-child relationship of each layer of quota nodes in the quota data tree structure and the quota calculation strategy of non-leaf quota nodes;
acquiring attribute information of a product corresponding to a leaf credit node configured through a first product configuration interface or a second product configuration interface;
and acquiring additional quota information of the product corresponding to the leaf quota node configured through the third product configuration interface.
3. The method of claim 2, wherein the constructing of the credit data tree structure corresponding to the user according to the credit system configuration information comprises:
generating an initial quota data tree structure according to the parent-child relationship of each quota node;
and configuring the non-leaf limit nodes in the initial limit data tree structure according to the limit calculation strategy of the non-leaf limit nodes, and configuring the leaf limit nodes according to the attribute information and the additional limit information of the leaf limit nodes to generate the limit data tree structure.
4. The method as claimed in any one of claims 1-3, wherein the managing the credit-related service corresponding to the user according to the credit data tree structure comprises:
if the first limit related service request is a credit granting application request, judging whether the user is a credit granting user;
if the user is a credit user, initializing the basic attribute of the quota on the quota tree; the basic attributes of the quota include: credit line, frozen line and occupied line.
5. The method of claim 4, wherein the managing the related credit services corresponding to the subscriber according to the credit data tree structure comprises:
receiving a second quota related service request triggered by the user;
and adjusting the basic quota attributes of each quota node according to the second quota related service request.
6. The method of claim 5, wherein the second credit-related business request is a loan application request, and the loan application request comprises: applying for the credit;
the adjusting the basic quota attributes of each quota node according to the second quota related service request comprises:
obtaining a credit remaining amount;
judging whether the credit remaining amount is larger than the loan application amount;
and if the credit remaining amount is determined to be larger than or equal to the loan application amount, adjusting the frozen amount and the occupied amount corresponding to each layer of amount node in the amount data tree structure from bottom to top according to the loan application amount.
7. The method of claim 5, wherein the second credit-related service request is a payment application request, and the payment application request comprises: repayment application limit;
the adjusting the basic quota attributes of each quota node according to the second quota related service request comprises:
obtaining loan cycle attributes corresponding to loan amount nodes in an amount data tree structure;
if the loan cycle attribute is a cycle attribute, adjusting an occupation amount according to the repayment application amount;
if the loan cycle attribute is a non-cycle attribute, keeping the occupied amount unchanged according to the repayment application amount.
8. The method according to any one of claims 1-3, further comprising:
receiving a service display request triggered by the user;
displaying the credit data tree structure in a tree connection mode according to the service display request;
receiving a statistical request for a certain quota node triggered by the user;
and responding to the counting request, and displaying the quota counting information of the quota node.
9. A data management apparatus, comprising:
the system comprises a configuration information determining module, a first limit system configuration module and a second limit system configuration module, wherein the configuration information determining module is used for determining limit system configuration information corresponding to a user if a first limit related service request triggered by the user is received;
the tree structure construction module is used for constructing a credit data tree structure corresponding to the user according to the credit system configuration information; the limit data tree structure comprises a plurality of layers of limit nodes, and each layer of limit node except the leaf limit node represents a management dimension node of a corresponding layer;
and the data management module is used for managing the related business of the quota corresponding to the user according to the quota data tree structure.
10. The apparatus of claim 9, wherein the credit system configuration information corresponding to the user comprises: general quota template information, attribute information of leaf quota nodes and additional quota information;
the configuration information determining module is specifically configured to:
acquiring general quota template information configured through a template configuration interface, wherein the general quota template information comprises: the parent-child relationship of each layer of quota nodes in the quota data tree structure and the quota calculation strategy of non-leaf quota nodes; acquiring attribute information of a product corresponding to a leaf credit node configured through a first product configuration interface or a second product configuration interface; and acquiring additional quota information of the product corresponding to the leaf quota node configured through the third product configuration interface.
11. The apparatus according to claim 10, wherein the tree structure building module is specifically configured to:
generating an initial quota data tree structure according to the parent-child relationship of each quota node; and configuring the non-leaf limit nodes in the initial limit data tree structure according to the limit calculation strategy of the non-leaf limit nodes, and configuring the leaf limit nodes according to the attribute information and the additional limit information of the leaf limit nodes to generate the limit data tree structure.
12. The apparatus according to any one of claims 9 to 10, wherein the data management module is specifically configured to:
if the first limit related service request is a credit granting application request, judging whether the user is a credit granting user; if the user is a credit user, initializing the basic attribute of the quota on the quota tree; the basic attributes of the quota include: credit line, frozen line and occupied line.
13. The apparatus of claim 12, wherein the data management module is specifically configured to:
receiving a second quota related service request triggered by the user; and adjusting the basic quota attributes of each quota node according to the second quota related service request.
14. The apparatus of claim 13, wherein the second credit-related transaction request is a loan application request, and the loan application request comprises: applying for the credit;
the data management module is specifically configured to, when adjusting the basic quota attributes of each quota node according to the second quota-related service request:
obtaining a credit remaining amount; judging whether the credit remaining amount is larger than the loan application amount; and if the credit remaining amount is determined to be larger than or equal to the loan application amount, adjusting the frozen amount and the occupied amount corresponding to each layer of amount node in the amount data tree structure from bottom to top according to the loan application amount.
15. The apparatus of claim 13, wherein the second credit-related service request is a payment application request, and the payment application request comprises: repayment application limit;
the data management module is specifically configured to, when adjusting the basic quota attributes of each quota node according to the second quota-related service request:
obtaining loan cycle attributes corresponding to loan amount nodes in an amount data tree structure; if the loan cycle attribute is a cycle attribute, adjusting an occupation amount according to the repayment application amount; if the loan cycle attribute is a non-cycle attribute, keeping the occupied amount unchanged according to the repayment application amount.
16. The apparatus of any one of claims 9-11, further comprising: the data display module is specifically used for:
receiving a service display request triggered by the user; displaying the credit data tree structure in a tree connection mode according to the service display request; receiving a statistical request for a certain quota node triggered by the user; and responding to the counting request, and displaying the quota counting information of the quota node.
17. An electronic device, comprising:
a memory, a processor, and a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any one of claims 1-8.
18. A computer-readable storage medium, on which a computer program is stored, which computer program is executable by a processor to implement the method according to any one of claims 1-8.
CN202010559232.6A 2020-06-18 2020-06-18 Data management method, device, equipment and storage medium Pending CN111708849A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010559232.6A CN111708849A (en) 2020-06-18 2020-06-18 Data management method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010559232.6A CN111708849A (en) 2020-06-18 2020-06-18 Data management method, device, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN111708849A true CN111708849A (en) 2020-09-25

Family

ID=72541133

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010559232.6A Pending CN111708849A (en) 2020-06-18 2020-06-18 Data management method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111708849A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111967984A (en) * 2020-10-22 2020-11-20 北京江融信科技有限公司 Method and system for dynamically managing credit limit based on relational tree
CN112365345A (en) * 2021-01-14 2021-02-12 北京江融信科技有限公司 DAG-based dynamic control method and system for multi-type credit line
CN113159920A (en) * 2021-04-23 2021-07-23 上海数禾信息科技有限公司 Credit limit management method, system, electronic equipment and storage medium
CN114240641A (en) * 2022-02-24 2022-03-25 北京锐融天下科技股份有限公司 Credit transfer method and system
CN116057168A (en) * 2020-09-30 2023-05-02 株式会社岛津制作所 Data processing system, data processing method, and computer program for executing data processing method using information processing apparatus

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101145264A (en) * 2007-11-06 2008-03-19 中国工商银行股份有限公司 Business affairs bank card processing system and method
CN104331830A (en) * 2014-11-07 2015-02-04 山东中创软件工程股份有限公司 Construction method and platform of limit managing system
CN107679983A (en) * 2017-10-20 2018-02-09 京北方信息技术股份有限公司 Amount tree constructing method and device, amount take route inspection method and apparatus
CN109670686A (en) * 2018-12-05 2019-04-23 泰康保险集团股份有限公司 Construct method, equipment and the business process management system of operation flow template
CN109767129A (en) * 2019-01-15 2019-05-17 蔷薇智慧科技有限公司 A kind of line of credit control method and device
CN110490459A (en) * 2019-08-21 2019-11-22 中国工商银行股份有限公司 A kind of protocol managerial approach and device

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101145264A (en) * 2007-11-06 2008-03-19 中国工商银行股份有限公司 Business affairs bank card processing system and method
CN104331830A (en) * 2014-11-07 2015-02-04 山东中创软件工程股份有限公司 Construction method and platform of limit managing system
CN107679983A (en) * 2017-10-20 2018-02-09 京北方信息技术股份有限公司 Amount tree constructing method and device, amount take route inspection method and apparatus
CN109670686A (en) * 2018-12-05 2019-04-23 泰康保险集团股份有限公司 Construct method, equipment and the business process management system of operation flow template
CN109767129A (en) * 2019-01-15 2019-05-17 蔷薇智慧科技有限公司 A kind of line of credit control method and device
CN110490459A (en) * 2019-08-21 2019-11-22 中国工商银行股份有限公司 A kind of protocol managerial approach and device

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116057168A (en) * 2020-09-30 2023-05-02 株式会社岛津制作所 Data processing system, data processing method, and computer program for executing data processing method using information processing apparatus
CN111967984A (en) * 2020-10-22 2020-11-20 北京江融信科技有限公司 Method and system for dynamically managing credit limit based on relational tree
CN111967984B (en) * 2020-10-22 2021-02-02 北京江融信科技有限公司 Method and system for dynamically managing credit limit based on relational tree
CN112365345A (en) * 2021-01-14 2021-02-12 北京江融信科技有限公司 DAG-based dynamic control method and system for multi-type credit line
CN112365345B (en) * 2021-01-14 2021-04-13 北京江融信科技有限公司 DAG-based dynamic control method and system for multi-type credit line
CN113159920A (en) * 2021-04-23 2021-07-23 上海数禾信息科技有限公司 Credit limit management method, system, electronic equipment and storage medium
CN114240641A (en) * 2022-02-24 2022-03-25 北京锐融天下科技股份有限公司 Credit transfer method and system
CN114240641B (en) * 2022-02-24 2022-05-20 北京锐融天下科技股份有限公司 Credit transfer method and system

Similar Documents

Publication Publication Date Title
CN111708849A (en) Data management method, device, equipment and storage medium
US11074098B2 (en) Systems and methods for java virtual machine management
KR102211374B1 (en) Method and device for outputting risk information and constructing risk information
CN104796270B (en) Recommend the method and device of suspect assembly in being diagnosed in the problem of cloud application
US20120311523A1 (en) Dependency-based impact analysis using multidimensional models of software offerings
US20140365662A1 (en) Configuring cloud resources
US9201702B2 (en) Integrated cloud data center management
US20090112919A1 (en) Method and system to model and create a virtual private datacenter
CN111694615B (en) Method, device, equipment and storage medium for data configuration
CN112651826B (en) Credit line management and control system, method and readable storage medium
CN110490459A (en) A kind of protocol managerial approach and device
US11836228B2 (en) Graphical user interface and console management, modeling, and analysis system
EP2705424A1 (en) Revenue-based impact analysis using multidimensional models of software offerings
CN108717657A (en) Capital lease system and method based on block chain
CN112861059A (en) Visual component generation method and device, computer equipment and readable storage medium
US20220335525A1 (en) Event management and validation platform using a recursive hierarchic blockchain
US20220108391A1 (en) Systems and methods for utilizing project information for adjusting a credit offer
CN109241110A (en) Order management method and system, electronic equipment, storage medium
CN115640457A (en) Information management method, apparatus, device, medium, and program product
CN111708782A (en) Data structure construction method, device, equipment and storage medium
CN105190568B (en) User-defined pond
CN106897337A (en) The acquisition methods and device of Internet resources, the acquisition methods of finance product
CN107818002A (en) The management method and device of a kind of Command Line Interface
US11922491B1 (en) Generating dynamic base limit value user interface elements determined from a base limit value model
US20130055090A1 (en) Bundling configuration items into a composite configuration item

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination