CN116645096A

CN116645096A - Resource processing method and device, electronic equipment and storage medium

Info

Publication number: CN116645096A
Application number: CN202310636786.5A
Authority: CN
Inventors: 陈壮; 于东东; 邢利菲
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2023-05-31
Filing date: 2023-05-31
Publication date: 2023-08-25

Abstract

The application provides a resource processing method, a device, electronic equipment and a storage medium, which can be used in the fields of financial cloud and online processing analysis. The method comprises the following steps: receiving a resource processing request, wherein the resource processing request comprises source account information, target account information and transaction data; determining a target account level of the resource processing request according to the source account information of the resource processing request; acquiring account resource data corresponding to at least one effective account in the target account level; and dividing target resources corresponding to the transaction data into target accounts corresponding to the target account information according to the account resource data. The method of the application improves the resource management efficiency.

Description

Resource processing method and device, electronic equipment and storage medium

Technical Field

The present application relates to the fields of financial cloud, online processing analysis, and the like, and in particular, to a resource processing method, a device, an electronic apparatus, and a storage medium.

Background

In recent years, with the rapid development of computer technology, account transactions realized through computer networks have been more and more frequent. In particular, the group-type customers have more complex funds transactions, more types of funds transactions, and higher complexity for account management. For example, processing requirements for various accounts, such as issuing, proxy payment, direct payment, limit payment, etc., are collected. And the group clients have more accounts and higher account management difficulty. Currently, manual account management is generally adopted to manage the accounts of clients, so that the account management efficiency is low.

Disclosure of Invention

The application provides a resource processing method, a device, electronic equipment and a storage medium, which are used for solving the problem of low account management efficiency.

In a first aspect, the present application provides a resource processing method, including:

receiving a resource processing request, wherein the resource processing request comprises source account information, target account information and transaction data;

determining a target account level corresponding to the source account information according to the source account information of the resource processing request;

acquiring account resource data corresponding to at least one effective account in the target account level;

and dividing target resources corresponding to the transaction data into target accounts corresponding to the target account information according to the account resource data.

In a second aspect, the present application provides a resource processing apparatus comprising:

a request receiving unit, configured to receive a resource processing request, where the resource processing request includes source account information, target account information, and transaction data;

the level determining unit is used for determining a target account level of the resource processing request according to the source account information of the resource processing request;

the data acquisition unit is used for acquiring account resource data corresponding to at least one effective account in the target account level;

And the resource dividing unit is used for dividing the target resources corresponding to the transaction data into target accounts corresponding to the target account information according to the account resource data.

In a third aspect, the present application provides an electronic device comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method as described in the first aspect and the various possibilities of the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, are adapted to carry out the method of the first aspect and the various possibilities of the first aspect.

In a fifth aspect, the application provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of the first aspect and the various possible methods involved in the first aspect.

The proposal provided by the application can receive the resource processing request, and the resource processing request can comprise source account information, target account information and transaction data. The target account level corresponding to the source account information can be determined through the source account information. The target account level may correspond to at least one valid account, and further account resource data of the at least one valid account corresponding to the target account level may be used to divide a target resource corresponding to the transaction data into a target account corresponding to the target account information according to the account resource data. At least one effective account in the target account level is uniformly managed by the target account level corresponding to the source account information, so that account resource data in the target account level is subjected to resource division, namely the accounts are effectively classified by the account level, resources in the level can be uniformly managed by the account level, the resource management efficiency of clients with more accounts is improved, and meanwhile, resources can be safely divided by the level account, so that the resource management efficiency and the safety of the accounts of the clients are improved.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is an application system architecture diagram of a resource processing method according to an embodiment of the present application;

FIG. 2 is a flowchart of an embodiment of a resource processing method according to an embodiment of the present application;

FIG. 3 is an exemplary diagram of an account level division provided by an embodiment of the present application;

fig. 4 is an application example diagram of a resource processing method according to an embodiment of the present application;

FIG. 5 is a schematic diagram illustrating a configuration of an embodiment of a resource processing device according to an embodiment of the present application;

fig. 6 is a block diagram of an electronic device for implementing a resource processing method according to an embodiment of the present application.

Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or fully authorized by each party, and the collection, use and processing of the related data need to comply with related laws and regulations and standards, and provide corresponding operation entries for the user to select authorization or rejection.

The resource processing method, the device, the electronic equipment and the storage medium can be used in the fields of financial cloud, online processing analysis and the like, and can also be used in any field except the fields of financial cloud, online processing analysis and the like.

In the related art, group clients generally have a plurality of accounts, and the group clients have various account transaction requirements. For example, the method has the account transaction scenes such as real-time collection issuing, timing collection issuing, direct payment, proxy payment and the like. However, in practical applications, the account structure of the group client is complex, and the transaction objects facing each account are different. Thus, for account security, the transaction objects of the account may generally be monitored. However, the security monitoring is performed by using the transaction object of the account, and the monitoring mode cannot control the flow direction of resources, the existing account transaction monitoring mode is simpler, the flow direction of the account cannot be solved, and early warning of the account transaction cannot be timely solved.

In the present application, a resource processing request may be received, and the resource processing request may include source account information and target account information, and transaction data. The target account level corresponding to the source account information can be determined through the source account information. The target account level may correspond to at least one valid account, and further account resource data of the at least one valid account corresponding to the target account level may be used to divide a target resource corresponding to the transaction data into a target account corresponding to the target account information according to the account resource data. At least one effective account in the target account level is uniformly managed by the target account level corresponding to the source account information, so that account resource data in the target account level is subjected to resource division, namely the accounts are effectively classified by the account level, resources in the level can be uniformly managed by the account level, the resource management efficiency of clients with more accounts is improved, and meanwhile, resources can be safely divided by the level account, so that the resource management efficiency and the safety of the accounts of the clients are improved.

The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

As shown in fig. 1, an application system architecture diagram of a resource processing method according to an embodiment of the present application is shown. The system architecture may include a server 1, a client 2, and a client 3, where the server 1 and the client 2, 3 may establish a communication connection, respectively. Client 2 may be the account manager of the source account information and client 3 may be the account manager of the target account. The server 1 may configure the resource processing method provided by the embodiment of the present application.

Wherein the client 2 may detect a resource handling request initiated by the account manager. The resource processing request may include source account information, target account information, and transaction data, and is transmitted to the server 1.

The server 1 may receive a resource processing request transmitted by the client 2. In addition, at least one account level may be configured in the server 1, where each account level is associated with at least one valid account, and each valid account may have resource data corresponding thereto. The server 1 may execute the resource processing method provided by the embodiment of the present application based on the at least one account level, and divide the target resource corresponding to the transaction data into the target account corresponding to the target account information, so as to implement efficient and safe allocation of the resource. After that, the client 3 may display the updated information of the target account and the updated resource data, for example, "you receive a 1000 yuan transfer, your account balance is 26189".

As shown in fig. 2, a flowchart of an embodiment of a resource processing method according to an embodiment of the present application may be configured as a resource processing device. The resource processing means may be located in the electronic device. The resource processing method may include:

step 201: a resource processing request is received, the resource processing request including source account information, target account information, and transaction data.

The execution body of the embodiment may be an electronic device, and the electronic device may be a server, a cloud server, a computer, a super personal computer, a mobile terminal, or the like, which is not limited in this embodiment.

Alternatively, the resource processing request may be sent by the client to the electronic device. The client may correspond to a resource provider, which may be, for example, a manager of the source account. The resource processing request may refer to a communication request generated by the account manager in response to a client-triggered account transaction operation. The resource processing request may carry relevant request information, such as source account information, target account information, transaction data, and the like.

Alternatively, the resource processing request may be generated by a request triggering module of the electronic device. The request triggering module may detect, for example, request information entered by a user for a display screen or input device, which may include, for example, source account information, target account information, and transaction data.

Illustratively, the resource handling request may be, for example: http requests, socket requests, etc., the resource processing requests may be transmitted to the electronic device through various channels or signals.

The source account information may refer to an account number or account identification of the provider of the resource. The target account information refers to an account number or account identification of the resource receiver. The transaction data may be data entered by an account manager corresponding to the detection source account information. Wherein the source account information, the target account information, and the transaction data may be obtained by the resource provider input. The method specifically comprises the steps that the electronic equipment or the client detects source account information, target account information and transaction data input by a resource provider.

Wherein the resource processing request may include at least one, and the at least one resource processing request may be transmitted by the at least one client. Specifically, the electronic device may receive at least one resource processing request, and process the at least one resource processing request in synchronization through steps 202-204, respectively, to complete the division of resources.

Step 202: and determining a target account level corresponding to the source account information according to the source account information of the resource processing request.

The target account level may be an account level at which the source account information is located.

Optionally, at least one account level may be set, and the plurality of accounts of the customer may be divided into at least one account level, each account level may be associated with a respective account, and the account associated with each account level may include at least one.

Alternatively, the plurality of accounts may be randomly divided into at least one account level, respectively, to obtain at least one account corresponding to each account level, respectively.

Step 202 may specifically be matching the source account information with a corresponding target account level from at least one account level.

Step 203: and acquiring account resource data corresponding to at least one effective account positioned in the target account level.

Optionally, at least one active account within the target account level may be managed uniformly. The account resource data may be data obtained by weighted summation of respective resource data of at least one active account within the target account level.

The account levels and the accounts of the account levels can be stored in a database in an associated mode, and at least one account corresponding to the account levels can be queried from the database to obtain the accounts corresponding to the account levels. And determining at least one valid account located within the target account level from the accounts associated with each account level.

Step 204: and dividing the target resources corresponding to the transaction data into target accounts corresponding to the target account information according to the account resource data.

Optionally, step 204 may include: and determining target resources corresponding to the transaction data from the resources corresponding to the account resource data, and dividing the target resources into target accounts corresponding to the target account information.

Illustratively, the resources may include storage space resources, financial resources, various types of data resources, etc., and the specific type of resources in this embodiment is not limited. The financial resource may refer to funds, the resource data may refer to a funds amount, and at this time, the transaction data may be a transaction amount, and funds corresponding to the transaction amount may be divided into target accounts.

Optionally, the account resource data may be resource data corresponding to at least one valid account. Dividing the target resource corresponding to the transaction data into the target account corresponding to the target account information may include: a source account of the target resource may be determined from the at least one valid account, and the target resource corresponding to the transaction data is divided from the resource data corresponding to the source account into target accounts of the target account information. The source account of the target resource may be an account corresponding to the source account information. If the resource data of the account corresponding to the source account information is smaller than the transaction data, a newly added source account can be determined from other effective accounts of the target account level, the resource data of the account corresponding to the source account information is used as part of the transaction data, and the resource data of the newly added source account is used as the rest of the transaction data. The remaining transaction data may be transaction data remaining in the transaction data except for the above-described partial transaction data. For example, assuming that the transaction data is 100 ten thousand, and the resource data in the a account corresponding to the source account information is 80 ten thousand, the B account may be selected from the target account level as the newly added source account, and 20 ten thousand may be determined from the B account as the remaining transaction data.

For example, account resource data may be used as a source of partitioning of resources.

As an alternative embodiment, step 204 may include:

judging whether the transaction data meets the transaction condition according to the account resource data;

if yes, dividing target resources corresponding to the transaction data in the account resource data into target accounts corresponding to the target account information;

if not, outputting transaction early warning prompt information which is used for prompting that the transaction data of the source account information exceeds the preset transaction condition.

Optionally, the transaction early warning prompt information may be information in the form of a short message, an instant communication message, an early warning page, an email, or the like, and in this embodiment, the specific information type of the transaction early warning prompt information is not limited too.

Optionally, the dividing the target resource into the target account corresponding to the target account information may specifically refer to adding the target resource into the original resource of the target account corresponding to the target account information, that is, the resource formed by the sum of the original resource and the target resource of the target account may be the new resource of the target account. The transaction condition may mean that a data difference between the transaction data and the account resource data is less than the pre-alarm resource data.

In this embodiment, it may be determined whether the transaction data satisfies the transaction condition through the account resource data. By confirming the transaction conditions, the account resource data can be effectively divided and used.

Further, optionally, determining whether the transaction data meets the transaction condition according to the account resource data may include:

calculating the data difference between account resource data and transaction data;

judging whether the transaction data meets the transaction condition according to the data difference;

optionally, the method further comprises:

if the data difference is smaller than or equal to the early warning resource data, determining that the transaction data does not meet the transaction condition;

if the data difference is larger than the early warning resource data, determining that the transaction data meets the transaction condition.

The early warning resource data can be a preset transaction limit value, can be set according to the use requirement, and can be specifically set by a resource provider or a resource manager.

Further, different account levels may set different early warning resource data. Illustratively, the higher the account level, the larger the early warning resource data may be, and the lower the account level, the smaller the early warning resource data may be. In this design, the early warning resource data may be early warning resource data corresponding to the target account level. For example, the base level may be set to 1000 ten thousand, the PCP (Precedence Constraint Posting, priority constraint posting) level may be set to 100 ten thousand, the VNP level may be set to 20 ten thousand, and the BDP level may be set to 5 ten thousand. Of course, in practical application, the early warning resource data may also be set randomly or according to historical experience, and the specific value of the early warning resource data in this embodiment is not limited too.

In this embodiment, the data difference between the account resource data and the transaction data may be calculated, and the data difference is used as a basis for determining whether the transaction data meets the transaction condition, so as to balance the resource requirement and the resource supply for the data difference, so as to confirm whether the transaction data meets the transaction condition accurately, and improve the accuracy of triggering the transaction condition.

As yet another alternative embodiment, determining the target account level of the resource processing request according to the source account information of the resource processing request may include:

at least one account level is obtained, the account level is used for associating at least one account, and the at least one account level forms a tree structure according to the level size and the association.

Determining a target account corresponding to source account information of the resource processing request according to at least one account associated with each account level;

a first account level associated with the target account is determined as the target account level.

Alternatively, the target account corresponding to the source account information may refer to a source account, that is, a target account having the same query account information as the source account information, that is, a source account.

The at least one account level may include a plurality and the different account levels may have account associations therebetween. For example, any account may be associated with an account presence at its next level of accounts. Assuming that the B account is a sub-account of the a account, there is an association between the B account and the a account.

In this embodiment, at least one account level and at least one account associated with each account level may be acquired first, so as to achieve acquisition of a target account corresponding to source account information, and further determine that a first account level associated with the target account is the target account level. The inquiry of the target account of the source account information can be realized through the corresponding relation between the account and the account level, so that the association of the account level is realized, and the inquiry efficiency and accuracy of the account level are improved.

Illustratively, account-level correspondence may be achieved by account matching.

As an embodiment, the method may further comprise:

determining an account to be classified of a target client and at least one account level;

respectively carrying out level matching processing on the account to be classified and at least one account level to obtain a second account level matched with the account to be classified;

and dividing the accounts to be classified into the corresponding second account levels so as to determine at least one account corresponding to each account level.

Alternatively, the account levels of at least one account level may be different and there may be a relationship of inclusion to inclusion. That is, one account level may be considered a child account level of the other account level, or may be considered a parent account level of the other account level. At least one account level within the account levels may include accounts belonging to the account level, may include accounts belonging to sub-account levels of the account level, and may include accounts of sub-account levels of each sub-account level until the last account level. That is, for any account level, all account levels below that account level may each account make up at least one account for that account level.

For ease of understanding, an exemplary diagram of account level division is shown in FIG. 3. Assuming that the plurality of accounts are A, B, C, D, E and F, respectively, and assuming that there are three account levels, the levels from high to low may be a PCP level, a VNP level, and a BDP level, respectively. Wherein the accounts of the PCP level comprise accounts A and B, the VNP level comprise accounts C and D, and the BDP comprises accounts E and F.

The child account level of the PCP level may be a parent account level of the VNP level and the BDP level. The VNP level may be either a child account level of the PCP level or a parent account level of the BDP level. While the BDP level is a sub-account level of the VNP level. The hierarchical relationship of the accounts at each level may be used as a premise for the acquisition of at least one account at each account level.

In this embodiment, for an account to be classified and at least one account level, the account to be classified may be matched to a second account level from at least one account level, so that the second account level is used as an account level of the account to be classified, and rapid and accurate division of the account level of the account to be classified is achieved, so that at least one account corresponding to each level of account level is managed by the classification, so that each account is divided according to different account levels, which is convenient for managing each level of account, improves account management efficiency, and more efficient management and monitoring of flow of account resources in the level.

Further, optionally, performing level matching processing on the account to be classified and at least one account level respectively to obtain a second account level matched with the account to be classified, including:

determining the level attribute corresponding to at least one account level respectively;

and carrying out attribute matching on the to-be-classified account and the level attribute corresponding to at least one account level respectively so as to obtain a second account level successfully matched with the to-be-classified account attribute.

Alternatively, the level attribute may refer to level features or content, which may be represented by any information type such as keywords, images, voice signals, feature vectors, and the like, and may also be represented by attribute identification. An account attribute may refer to a characteristic or content of an account. The account attribute of the account to be classified and the level attribute of the account level are expressed in the same way, for example, the account attribute and the level attribute can be feature vectors or keywords. Performing attribute matching on the to-be-classified account and the level attribute corresponding to the at least one account level respectively can comprise performing attribute similarity calculation on the account attribute of the to-be-classified account and the level attribute of the at least one account level respectively to obtain attribute similarity of the to-be-classified account corresponding to the at least one account level respectively. And then, selecting the account level with the highest similarity from the attribute similarities corresponding to at least one account level respectively according to the accounts to be classified as a second account level.

In this embodiment, when matching the corresponding second account level for the account to be classified, matching may be performed according to the level attribute corresponding to each level of account level and the account to be classified, and the account level is divided according to the attribute of the account when matching the account to be classified to the second account level with similar attribute. By attribute can make

determining a user level corresponding to an account owner of an account to be classified;

a second account level is selected from the at least one account level that matches the user level based on the user level of the account owner.

Optionally, in practical application, the group client may be built into an organization architecture, where the organization architecture may include multiple layers, each layer may correspond to a corresponding manager, and different managers, that is, users, may set different user levels. The higher the user level, the higher its corresponding account level, and the lower the user level, the lower its corresponding account level. The user-level setting can realize the effective management of the accounts to be classified, and improve the management efficiency and the effectiveness of the accounts.

In this embodiment, an account level corresponding to an account owner of an account to be classified may be determined, and a second account level matched with the user level may be determined according to the user level of the account owner. The user level of the account owner is taken as the acquisition basis of the account level, so that the second account level is more matched with the user level of the account owner, and accurate level positioning can be realized.

Further, on the basis of any one of the foregoing embodiments, determining the target account level of the resource processing request according to the source account information of the resource processing request may include:

and if the current time is detected to meet the time transaction condition, determining a target account level of the resource processing request according to the source account information of the resource processing request.

The time transaction condition can be that the current time reaches a certain transaction time, namely, the resource processing request is processed in a specific time in a targeted manner, so that the centralized processing of the resource processing request is realized, and the processing efficiency and accuracy of the resource processing request are improved.

In this embodiment, the time transaction condition is set to use whether the current time meets the time transaction condition as a processing premise of the resource processing request, so that the processing of the resource processing request is executed in a certain time, the resource processing request is processed in a centralized manner, and the processing efficiency of the resource processing request can be improved. Meanwhile, the centralized processing of the resource processing requests can realize the one-by-one processing of the resource processing requests, and the loss or omission of the resource processing requests can be avoided.

Further, optionally, the method further comprises:

determining a transaction frequency and a previous historical transaction time;

determining target transaction time according to the transaction frequency and the historical transaction time;

if the current time is detected to reach the target transaction time, determining that the current time meets the time transaction condition.

Where transaction frequency may refer to an account processing frequency that may be used to determine the interval between two adjacent processing resource processing requests. The transaction frequency may be set according to transaction habits or transaction requirements. For example, more transaction requirements may set a higher transaction frequency, less transaction requirements may set a lower transaction frequency.

In this embodiment, when the processing constraint is performed on the resource processing request through the time transaction condition, the historical transaction time and the transaction frequency may be specifically used to determine the target transaction time, and the target transaction time is used as the time transaction condition, so as to implement effective application of the time transaction condition, and further perform efficient and centralized processing on the resource processing request, so as to implement efficient management on the resource.

Further, based on any one of the above embodiments, obtaining account resource data corresponding to at least one valid account located in the target account level includes:

Determining at least one valid account within the target account level;

generating account inquiry requests for at least one effective account respectively, and sending the account inquiry requests of each effective account to corresponding account management equipment, wherein the account inquiry requests instruct the account management equipment to inquire the resource data of the corresponding effective account;

receiving resource data respectively corresponding to at least one effective account sent by each account management device;

and adding and summing the resource data corresponding to at least one effective account respectively to obtain account resource data.

At least one valid account may be included within the target account level. The account manager may be different for any two active accounts. The electronic device to which the account manager corresponds may be referred to as an account management device. The resource data of each effective account can be inquired and obtained through the account management equipment of each effective account.

In practical applications, the account management device corresponding to at least one valid account may be a node in one or more distributed clusters. The distributed cluster may be a server cluster. Any one of the distributed clusters may be associated with one or more active accounts. Different distributed clusters may be different resource managers, e.g., a distributed cluster may correspond to a bank manager.

In this embodiment, at least one effective account of the target account level may be determined first to generate an account query request of each effective account, and resource data of each effective account may be queried pertinently through the account query request of each effective account to obtain resource data corresponding to at least one effective account respectively, so as to implement quick and accurate query of the account.

Further, on the basis of any of the above embodiments, the determining step of the at least one valid account within the target account level may include:

determining a target account level and sub-account levels belonging to the target account level in at least one account level;

acquiring an effective account associated with a target account level and an effective account associated with each sub-account level corresponding to the target account level;

and determining the valid account associated with the target account level as at least one valid account in the target account level.

Each sub-account level of the target account level may include a sub-account level of the target account level and a sub-account level of the sub-account level, even sub-account levels of each level sub-account level, up to the last level sub-account level.

Taking the account of fig. 3 as an example, assuming that the source account is B, the PCP level is the target account level, and the VNP level below the PCP level and the sub-account level-BDP level of the VNP level may be sub-account levels of the PCP level, so that the accounts C and D, and the accounts E and F combine to form at least one valid account within the target account level.

In this embodiment, the target account level and each sub-account level belonging to the target account level in at least one account level may be determined, so as to obtain at least one effective account in the target account level, implement the same management of a plurality of effective accounts by using the account level, share resources in the accounts, and implement efficient management of account resources.

For easy understanding, as shown in fig. 4, an application example diagram of a resource processing method provided by the present application is referred to fig. 4. In practical applications, the client 41 may face the resource provider and display an information input page, and may detect source account information, target account information, and transaction data input by the user through the information input page 401. And generating a resource processing request from the source account information, the target account information, and the transaction data. The resource processing request may then be sent to the electronic device 42.

Wherein the electronic device 42 may receive a resource handling request sent by the client 41. And determining a target account level from the at least one account level based on the source account information of the resource processing request. At least one account level may refer to the account level shown in fig. 3. By acquiring account resource data corresponding to at least one effective account in the target account level, for example, the source account is D, if the corresponding target account level is VNP, the account C of the same VNP group and the account of the sub-account level thereof, and the account E and the account F included in the BDP account level are both effective accounts, that is, the account C, D, E, F is taken as at least one effective account. Account resource data for at least one active account, such as account balance 403 for account CDEF, may be determined. If the account balance is higher than the transaction data of the resource processing request, the target resource corresponding to the transaction data can be divided into target accounts corresponding to the target account information, for example, the transaction data is 1000 yuan, the original balance of the target account is 2000 yuan, and the account balance of the responding target account is updated to 3000 yuan. And updating the account balance of the target account, and displaying the updated account balance. For example, the client 43 corresponding to the target account may display "your account balance is 3000 yuan".

As shown in fig. 5, a schematic structural diagram of an embodiment of a resource processing device according to an embodiment of the present application, where the resource processing device 500 may include the following units:

the request receiving unit 501: for receiving a resource processing request including source account information, target account information, and transaction data.

The level determination unit 502: and the target account level corresponding to the source account information is determined according to the source account information of the resource processing request.

A data acquisition unit 503: the method is used for acquiring account resource data corresponding to at least one effective account located in the target account level.

Data dividing unit 504: and dividing the target resources corresponding to the transaction data into target accounts corresponding to the target account information according to the account resource data.

As one embodiment, the data dividing unit may include:

and the account judging module is used for judging whether the transaction data meets the transaction condition according to the account resource data.

And the first processing module is used for dividing the target resources corresponding to the transaction data in the account resource data into target accounts corresponding to the target account information if yes.

And the second processing module is used for outputting transaction early warning prompt information if not, wherein the transaction early warning prompt information is used for prompting that the transaction data of the source account information exceeds the preset transaction condition.

As yet another embodiment, the account judgment module may include:

the difference calculation sub-module is used for calculating the data difference between the account resource data and the transaction data;

the difference judging sub-module is used for judging whether the transaction data meets the transaction condition according to the data difference;

the apparatus further comprises:

and the first determining unit is used for determining that the transaction data does not meet the transaction condition if the data difference is smaller than or equal to the early warning resource data.

And the second determining unit is used for determining that the transaction data meets the transaction condition if the data difference is larger than the early warning resource data.

As still another embodiment, the level determining unit may include:

the system comprises a level acquisition module, a level generation module and a level generation module, wherein the level acquisition module is used for acquiring at least one account level, the account level is used for associating at least one account, and the at least one account level forms a tree structure according to the level size and the association;

the account association module is used for determining a target account corresponding to source account information of the resource processing request according to at least one account associated with each account level;

and the target determining module is used for determining the first account level associated with the target account as the target account level.

As yet another embodiment, further comprising:

And the first determining unit is used for determining the account to be classified of the target client and at least one account level.

The first matching unit is used for respectively carrying out level matching processing on the account to be classified and at least one account level to obtain a second account level matched with the account to be classified.

And the account dividing unit is used for dividing the accounts to be classified into the corresponding second account levels so as to determine at least one account corresponding to each account level.

As still another embodiment, the first matching unit may include:

the attribute determining module is used for determining the level attribute corresponding to at least one account level respectively;

and the attribute matching module is used for carrying out attribute matching on the to-be-classified account and the level attribute corresponding to at least one account level respectively so as to obtain a second account level successfully matched with the to-be-classified account attribute.

As still another embodiment, the first matching unit may include:

the level determining module is used for determining the user level corresponding to the account owner of the account to be classified;

and the level matching module is used for selecting a second account level matched with the user level from at least one account level according to the user level of the account owner.

As still another embodiment, the level determining unit includes:

and the time management module is used for detecting that the current time meets the time transaction condition and determining the target account level of the resource processing request according to the source account information of the resource processing request.

As yet another embodiment, further comprising:

a history determining unit for determining a transaction frequency and a previous history transaction time;

a time determining unit for determining a target transaction time according to the transaction frequency and the historical transaction time;

and the detection triggering unit is used for determining that the current time meets the time transaction condition if the current time is detected to reach the target transaction time.

As still another embodiment, the data acquisition unit may include:

an account determination module for determining at least one valid account within the target account level;

the account inquiry module is used for generating an account inquiry request according to at least one effective account, sending the account inquiry request to the account management equipment, and indicating the account management equipment to inquire the resource data corresponding to the at least one effective account respectively;

the resource receiving module is used for receiving resource data corresponding to at least one effective account sent by the account management equipment;

And the resource adding module is used for adding and summing the resource data corresponding to at least one effective account respectively to obtain account resource data.

As yet another embodiment, it may further include:

the level inquiry unit is used for determining the target account level and each sub-account level belonging to the target account level in at least one account level;

the account acquisition unit is used for acquiring the account associated with the target account level and the effective account associated with each sub-account level corresponding to the target account level;

and the account determining unit is used for determining the account associated with the target account level and the valid account associated with each sub-account level as at least one valid account in the target account level.

Fig. 6 is a block diagram of an electronic device, which may be a mobile phone, computer, digital broadcast terminal, messaging device, game console, tablet device, medical device, exercise device, personal digital assistant, or the like, in accordance with an exemplary embodiment.

The apparatus 600 may include one or more of the following components: a processing component 602, a memory 604, a power component 606, a multimedia component 608, an audio component 610, an input/output (I/O) interface 612, a sensor component 614, and a communication component 616.

The processing component 602 generally controls overall operation of the apparatus 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or part of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 may include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.

The memory 604 is configured to store various types of data to support operations at the apparatus 600. Examples of such data include instructions for any application or method operating on the apparatus 600, contact data, phonebook data, messages, pictures, videos, and the like. The memory 604 may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

The power supply component 606 provides power to the various components of the device 600. The power supply components 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 600.

The multimedia component 608 includes a screen between the device 600 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation. In some embodiments, the multimedia component 608 includes a front camera and/or a rear camera. The front camera and/or the rear camera may receive external multimedia data when the apparatus 600 is in an operational mode, such as a photographing mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may be further stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.

The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be a keyboard, click wheel, buttons, etc. These buttons may include, but are not limited to: homepage button, volume button, start button, and lock button.

The sensor assembly 614 includes one or more sensors for providing status determination of various aspects of the apparatus 600. For example, the sensor assembly 614 may detect the on/off state of the device 600, the relative positioning of the assemblies, such as the display and keypad of the device 600, the sensor assembly 614 may also detect the change in position of the device 600 or one of the assemblies of the device 600, the presence or absence of user contact with the device 600, the orientation or acceleration/deceleration of the device 600, and the change in temperature of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscopic sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 616 is configured to facilitate communication between the apparatus 600 and other devices in a wired or wireless manner. The device 600 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In one exemplary embodiment, the communication component 616 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 616 further includes a Near Field Communication (NFC) module to facilitate short range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic elements for executing the methods described above.

In an exemplary embodiment, a non-transitory computer-readable storage medium is also provided, such as memory 604, including instructions executable by processor 620 of apparatus 600 to perform the above-described method. For example, the non-transitory computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

The present application provides an electronic device including: a processor, a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes the computer-executable instructions stored in the memory to implement a method as possible in any of the embodiments described above. The present application provides a computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out a method as possible in any of the embodiments. The storage medium may be, for example, the memory 604 of the embodiment shown in fig. 6.

The present application provides a computer program product comprising a computer program which, when executed by a processor, implements a method as possible in any of the embodiments.

Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.

Claims

1. A method of resource processing, comprising:

2. The method of claim 1, wherein the dividing the target resource corresponding to the transaction data into the target account corresponding to the target account information according to the account resource data comprises:

judging whether the transaction data meets transaction conditions according to the account resource data;

3. The method of claim 2, wherein determining whether the transaction data satisfies a transaction condition based on the account resource data comprises:

calculating the data difference between the account resource data and the transaction data;

and judging whether the transaction data meets the transaction condition according to the data difference.

4. The method of claim 1, wherein determining the target account level of the resource processing request based on the source account information of the resource processing request comprises:

acquiring at least one account level, wherein the account level is used for associating at least one account, and at least one account level forms a tree structure according to the level size and the association;

determining a target account corresponding to the source account information of the resource processing request according to at least one account associated with each account level;

Determining a first account level associated with the target account as the target account level.

5. The method of any one of claims 1-4, further comprising:

6. The method according to claim 5, wherein the performing the level matching process on the account to be classified and at least one of the account levels to obtain a second account level matched with the account to be classified includes:

determining at least one level attribute corresponding to the account level respectively;

and carrying out attribute matching on the account to be classified and at least one level attribute corresponding to the account level respectively so as to obtain a second account level successfully matched with the account attribute to be classified.

7. The method according to claim 5, wherein the performing the level matching process on the account to be classified and at least one of the account levels to obtain a second account level matched with the account to be classified includes:

Determining a user level corresponding to an account owner of the account to be classified;

and selecting a second account level matched with the user level from at least one account level according to the user level of the account owner.

8. The method of claim 1, wherein determining the target account level of the resource processing request based on the source account information of the resource processing request comprises:

9. The method as recited in claim 8, further comprising:

determining a transaction frequency and a previous historical transaction time;

determining a target transaction time according to the transaction frequency and the historical transaction time;

and if the current time is detected to reach the target transaction time, determining that the current time meets a time transaction condition.

10. The method of claim 1, wherein the obtaining account resource data corresponding to at least one valid account located within the target account level comprises:

Determining at least one valid account within the target account level;

generating an account query request according to at least one effective account, and sending the account query request to account management equipment, wherein the account query request indicates the account management equipment to query resource data corresponding to at least one effective account respectively;

receiving resource data respectively corresponding to at least one effective account sent by the account management equipment;

and adding and summing the resource data corresponding to at least one effective account respectively to obtain the account resource data.

11. The method of claim 1, wherein the step of determining at least one valid account within the target account level comprises:

determining the target account level and each sub-account level belonging to the target account level in at least one account level;

acquiring an account associated with the target account level and an effective account associated with each sub-account level corresponding to the target account level;

and determining the account associated with the target account level and the valid account associated with each sub-account level as at least one valid account in the target account level.

12. A resource processing apparatus, comprising:

13. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;

the memory stores computer-executable instructions;

the processor executes computer-executable instructions stored in the memory to implement the method of any one of claims 1 to 11.

14. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are adapted to carry out the method of any one of claims 1 to 11.