CN117575761A

CN117575761A - Resource management method, device, computer equipment and storage medium

Info

Publication number: CN117575761A
Application number: CN202311545729.2A
Authority: CN
Inventors: 张梦醒; 梅坚
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2023-11-17
Filing date: 2023-11-17
Publication date: 2024-02-20

Abstract

The application relates to a resource management method, a device, computer equipment and a storage medium in the technical field of big data. The method comprises the following steps: receiving a service processing request; pushing an account grade processing interface under the condition that the service type is the account type; acquiring an object identifier, an account identifier and an account security level input through an account security level input sub-interface; updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier; determining a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level; and managing the resources of the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota amount acquired through the account quota input sub-interface. By adopting the method, the resource management can be accurately performed.

Description

Resource management method, device, computer equipment and storage medium

Technical Field

The present application relates to the field of big data technology, and in particular, to a resource management method, apparatus, computer device, storage medium, and computer program product.

Background

With the vigorous development of big data technology, the demand for managing resources is gradually increased, so that more resource management means are presented. The resource management may be a user who uses the resource or a process of using the resource by the user, which can support better service users.

At present, taking a bank as an example, a means of managing resources by the bank generally records information of a resource user, compares the resource required to be acquired by the user with a preset resource maximum transfer-out limit of the bank when the user needs to acquire the resources in the bank, and transfers the resource to the user if the resource required to be acquired by the user is smaller than the preset resource maximum transfer-out limit of the bank; if the resource required to be acquired by the user is larger than the maximum transfer-out limit of the preset resource of the bank, the resource cannot be transferred out.

However, the current resource management method or the conventional method has a problem of insufficient accuracy.

Disclosure of Invention

Based on this, it is necessary to provide an accurate resource management method, apparatus, computer device, computer readable storage medium and computer program product in view of the above technical problems.

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

receiving a service processing request, wherein the service processing request carries a service type;

pushing an account grade processing interface under the condition that the service type is an account type, wherein the account grade processing interface comprises an account security grade input sub-interface and an account quota input sub-interface;

acquiring an object identifier, an account identifier and an account security level input through the account security level input sub-interface;

updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, wherein the object identifier corresponds to at least one account identifier, and the pre-stored account security levels corresponding to the account identifiers corresponding to the object identifiers are the same or different;

determining a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, wherein the preset quota amount is used for checking the quota amount input by the account quota input sub-interface;

And carrying out resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota obtained through the account quota input sub-interface. In some embodiments, the account level processing interface further includes an account processing type sub-interface; the updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, includes:

and under the condition that the processing type selected by the account processing type sub-interface is a maintenance type, updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier.

In some embodiments, the account level processing interface further includes an account processing type sub-interface; the method further comprises the steps of:

inquiring a pre-stored account security level corresponding to the object identifier and the account identifier under the condition that the processing type selected by the account processing type sub-interface is an inquiring type;

Pushing an account processing type switching message if the searched pre-stored account security level is inconsistent with the account security level obtained through the account security level input sub-interface;

and under the condition that a first confirmation message corresponding to the account processing type switching message is acquired, switching the processing type selected by the account processing type sub-interface from the query type to the maintenance type.

In some embodiments, the method further comprises:

pushing an object grade processing interface under the condition that the service type is a user type, wherein the object grade processing interface comprises an object security grade input interface and an object processing type sub-interface;

when the processing type selected by the object processing type sub-interface is a maintenance type, acquiring an object identifier and an object security level input through the object security level input interface;

and updating the pre-stored object security level corresponding to the object identifier based on the object security level.

In some embodiments, the method further comprises:

inquiring a pre-stored object security level corresponding to the object identifier when the processing type selected by the object processing type sub-interface is an inquiring type;

If the pre-stored object security level is inconsistent with the object security level, pushing an object processing type switching message;

and under the condition that a second confirmation message corresponding to the object processing type switching message is acquired, switching the processing type selected by the object processing type sub-interface from the query type to the maintenance type.

In some embodiments, the method further comprises:

pushing a history grade inquiry selection interface;

acquiring an object identifier, an account identifier and a grade inquiry type selected through the history grade inquiry selection interface, and inquiring a history security grade corresponding to the object identifier, the account identifier and the grade inquiry type;

pushing the historical security level.

In some embodiments, the querying the historical security level corresponding to the object identification, account identification, and the level query type comprises:

querying a historical object security level corresponding to the object identifier and the object level query type under the condition that the level query type is an object level query type;

and querying a historical account security level corresponding to the object identifier, the account identifier and the account level query type under the condition that the level query type is the account level query type.

In some embodiments, the determining the preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier includes;

and determining a preset single-time limit amount and a preset single-day limit amount corresponding to the account limit input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, wherein the preset single-time limit amount is used for checking the single-time limit amount input by the account limit input sub-interface, and the preset single-day limit amount is used for checking the single-day limit amount input by the account limit input sub-interface.

In a second aspect, the present application further provides a resource management device, including:

the request acquisition module is used for receiving a service processing request, wherein the service processing request carries a service type;

the interface pushing module is used for pushing an account grade processing interface under the condition that the service type is an account type, wherein the account grade processing interface comprises an account security grade input sub-interface and an account quota input sub-interface;

the data acquisition module is used for acquiring the object identifier, the account identifier and the account security level input through the account security level input sub-interface;

The data processing module is used for updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, wherein the object identifier corresponds to at least one account identifier, and the pre-stored account security levels corresponding to the account identifiers corresponding to the object identifiers are the same or different;

the quota determining module is used for determining a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, wherein the preset quota amount is used for checking the quota amount input by the account quota input sub-interface;

and the resource management module is used for carrying out resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier and the quota amount acquired through the account quota input sub-interface.

In some embodiments, the account level processing interface further includes an account processing type sub-interface; the data processing module is further configured to update a pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier when the processing type selected by the account processing type sub-interface is a maintenance type.

In some embodiments, the account level processing interface further includes an account processing type sub-interface; the device also comprises a first query module, wherein the first query module is used for querying a pre-stored account security level corresponding to the object identifier and the account identifier when the processing type selected by the account processing type sub-interface is a query type; pushing an account processing type switching message if the searched pre-stored account security level is inconsistent with the account security level obtained through the account security level input sub-interface; and under the condition that a first confirmation message corresponding to the account processing type switching message is acquired, switching the processing type selected by the account processing type sub-interface from the query type to the maintenance type.

In some embodiments, the apparatus further includes an object level update module configured to push an object level processing interface, where the service type is a user type, the object level processing interface including an object security level input interface and an object processing type sub-interface; when the processing type selected by the object processing type sub-interface is a maintenance type, acquiring an object identifier and an object security level input through the object security level input interface; and updating the pre-stored object security level corresponding to the object identifier based on the object security level.

In some embodiments, the apparatus further includes a processing type switching module, where the processing type switching module is configured to query a pre-stored object security level corresponding to the object identifier when the processing type selected by the object processing type sub-interface is a query type; if the pre-stored object security level is inconsistent with the object security level, pushing an object processing type switching message; and under the condition that a second confirmation message corresponding to the object processing type switching message is acquired, switching the processing type selected by the object processing type sub-interface from the query type to the maintenance type.

In some embodiments, the apparatus further comprises a history rank query module for pushing a history rank query selection interface; acquiring an object identifier, an account identifier and a grade inquiry type selected through the history grade inquiry selection interface, and inquiring a history security grade corresponding to the object identifier, the account identifier and the grade inquiry type; pushing the historical security level.

In some embodiments, the history grade query module is further configured to query a history object security grade corresponding to the object identifier and the object grade query type if the grade query type is an object grade query type; and querying a historical account security level corresponding to the object identifier, the account identifier and the account level query type under the condition that the level query type is the account level query type.

In some embodiments, the quota determination module is further configured to determine, based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, a preset single quota amount corresponding to the account quota input sub-interface and a preset single daily quota amount, where the preset single quota amount is used to verify a single quota amount input by the account quota input sub-interface, and the preset single daily quota amount is used to verify a single daily quota amount input by the account quota input sub-interface.

In a third aspect, the present application also provides a computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:

and carrying out resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota obtained through the account quota input sub-interface. In a fourth aspect, the present application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:

and carrying out resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota obtained through the account quota input sub-interface. In a fifth aspect, the present application also provides a computer program product comprising a computer program which, when executed by a processor, performs the steps of:

and carrying out resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota obtained through the account quota input sub-interface.

The resource management method, the resource management device, the computer equipment, the storage medium and the computer program product receive a service processing request, wherein the service processing request carries a service type; pushing an account grade processing interface under the condition that the service type is the user type, wherein the account grade processing interface comprises an account security grade input sub-interface and an account quota input sub-interface; acquiring an object identifier, an account identifier and an account security level input through an account security level input sub-interface; updating the pre-stored account security levels corresponding to the object identifiers and the account identifiers based on the account security levels and the pre-stored object security levels corresponding to the pre-stored object identifiers, wherein the object identifiers correspond to at least one account identifier, and the corresponding pre-stored account security levels of the account identifiers corresponding to the object identifiers are the same or different; determining a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, wherein the preset quota amount is used for checking the quota amount input by the account quota input sub-interface; and managing the resources of the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota amount acquired through the account quota input sub-interface. In the whole process, because the object identifier corresponds to at least one account identifier, the pre-stored account security level corresponding to the object identifier and the account identifier can be accurately updated based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier; further, after updating the pre-stored account security level, the account preset limit amount can be determined according to the updated pre-stored account security level, and then accurate resource management is performed on the object identification from three dimensions of the preset object client security level, the updated pre-stored account security level and the limit amount.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the related art, the drawings that are required to be used in the embodiments or the related technical descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for a person having ordinary skill in the art.

FIG. 1 is an application environment diagram of a resource management method in one embodiment;

FIG. 2 is a flow diagram of a method of resource management in one embodiment;

FIG. 3 is a flow chart of a method of resource management in another embodiment;

FIG. 4 is a block diagram of a resource management device in one embodiment;

fig. 5 is an internal structural diagram of a computer device in one embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.

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.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use, and processing of the related data are required to meet the related regulations.

The resource management method provided by the embodiment of the application can be applied to an application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The user operates on the terminal 102, inputs or selects a required service type, the terminal 102 acquires the service type, generates a service processing request, and sends the service processing request to the server 104; the server 104 receives the service processing request and extracts the service type carried in the service processing request; pushing an account grade processing interface under the condition that the service type is an account type, wherein the account grade processing interface comprises an account security grade input sub-interface and an account quota input sub-interface; acquiring an object identifier, an account identifier and an account security level input through an account security level input sub-interface; updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, wherein the object identifier corresponds to at least one account identifier, and the pre-stored account security levels corresponding to the account identifiers corresponding to the object identifiers are the same or different; determining a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, wherein the preset quota amount is used for checking the quota amount input by the account quota input sub-interface; and managing the resources of the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota amount acquired through the account quota input sub-interface.

In other embodiments, the resource management method provided in the embodiments of the present application may also be applied to a terminal separately. The user operates on the terminal 102, inputs or selects a required service type, and the terminal 102 obtains a service processing request uploaded by the user, wherein the service processing request carries the service type; and processing the object identifier by adopting a resource management method based on the service processing request.

The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.

In some embodiments, as shown in fig. 2, a resource management method is provided, which is illustrated by using the method applied to the server 104 in fig. 1 as an example, and includes:

s100, receiving a service processing request.

Wherein the service processing request carries a service type.

Specifically, a user operates on a terminal, inputs or selects a required service type, the terminal acquires the service type, generates a service processing request, and sends the service processing request to a server; the server receives the service processing request and extracts the service type carried in the service processing request. Wherein the service type comprises an account type and a user type. The service type in the application is generally a security level type, that is, the account type refers to the security level type of the account corresponding to the user object, and the user type refers to the security level type of the user object.

Further, when the user performs an operation on the terminal and inputs or selects a desired service type, a service type processing interface is displayed on the terminal, and the service type processing interface includes a service type input interface or a service type selection interface. When the service type processing interface is a service type input interface, a user can directly input the service type to be input on the terminal; when the service type processing interface is a service type selection interface, the service type selection interface comprises a service type candidate sub-interface and a service type selection sub-interface, a plurality of selectable service types are displayed on the service type candidate sub-interface, a user can click a certain candidate service type in the service type candidate sub-interface on the terminal, the terminal receives a click request of the user and forwards the request to the server, and the server inquires the candidate service type corresponding to the click request of the user and pushes the candidate service type to the service type selection sub-interface in the terminal to be displayed for displaying to the user. Still further, the sub-interface may be characterized in terms of an input box or selection box, or the like.

S200, pushing an account grade processing interface under the condition that the service type is the account type.

The account level processing interface comprises an account security level input sub-interface and an account quota input sub-interface.

Specifically, when the user inputs or selects that the service type is the account type, the server pushes an account level processing interface to the terminal, where the account level processing interface is essentially a processing interface of the security level of the account, and the user can update the security level of the account in the processing interface of the security level of the account on the terminal. In addition, the account level processing interface also comprises a quota input sub-interface of the account, and a user can limit the quota of the subsequent resource processing of the account in the sub-interface.

S300, obtaining the object identification, the account identification and the account security level input through the account security level input sub-interface.

The object identifier refers to the identifier of the user, and the account identifier refers to the identifier of the account owned by the user; a user may register and use multiple accounts, and thus, one object identification corresponds to at least one account identification.

Specifically, the terminal may obtain the object identifier and the account identifier through various channels. If the user inputs the service type on the held terminal, the user can also input an account identifier, the terminal generates a service processing request based on the service type and the account identifier, the service processing request is uploaded to a server, the server extracts the account identifier in the service processing request, and the object name, the object identifier and the account name corresponding to the account identifier are inquired from a database; further, the server pushes the object name, the object number and the account name corresponding to the account identifier to the terminal, so that the terminal can display the object name, the object identifier and the account name corresponding to the account identifier to the user so as to confirm whether the object name, the object identifier and the account name corresponding to the account identifier are correct or not; wherein, the object identifier and the account identifier are generally characterized in the form of a numerical number in a standard format, and can also adopt a combination of numerals and letters; for another example, the user may input a service type at an interface in which an account has been logged in, and at this time, the terminal may directly acquire the account type and perform subsequent interaction with the server.

Furthermore, the server pushes the account level processing interface to the terminal, and the terminal can not only receive the input account identification, but also receive the account security level input by the user on the account level processing interface of the terminal. The account security level includes, but is not limited to, a digital level as the account security level, and the size of the digital indicates the security degree of the account security level, for example, the account security level may be set to be primary, secondary and tertiary, and the account security level is the largest when the account security level is tertiary. In addition, when the user inputs the account identifier, the service type and the account security level, if the user inputs errors, the user can click a reset button on the interface to reset the data.

S400, updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier.

The object identifiers correspond to at least one account identifier, and the pre-stored account security levels corresponding to the account identifiers corresponding to the object identifiers are the same or different.

Specifically, the database of the server stores the object identifier, the pre-stored object security level corresponding to the pre-stored object identifier, the pre-stored account identifier corresponding to the pre-stored object identifier, and the pre-stored account security level corresponding to the pre-stored object identifier and the pre-stored account identifier in advance. The server acquires the object identifier and the account identifier, and queries whether a pre-stored account identifier and a pre-stored object identifier which are consistent with the object identifier and the account identifier exist in a database; if so, inquiring the pre-stored account security level corresponding to the pre-stored account identifier and the pre-stored object identifier, and taking the pre-stored account security level corresponding to the object identifier and the account identifier. And because an object can have a plurality of accounts, the security level of the account is referred to by the security level of the object, so that the updating of the pre-stored account security level is based on the account security level input through the account security level input sub-interface and the pre-stored object security level corresponding to the pre-stored object identification.

S500, determining a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier.

The preset quota amount is used for checking the quota amount input by the account quota input sub-interface.

Specifically, on the basis of updating the pre-stored account security level corresponding to the object identifier and the account identifier, the amount of subsequent resource processing of the account can be limited. The method for limiting the amount of the subsequent resource processing of the account is carried out through an account amount input sub-interface pushed by the server before. The user can input the required set resource quota on the terminal, but the resource quota input by the user needs to be limited to a certain extent, namely the resource quota input by the user needs to be matched with the account security level. Therefore, after the server updates the pre-stored account security level corresponding to the object identifier and the account identifier, the server further determines the preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier. The resource quota input by the user on the terminal needs to be matched with the preset quota. In practical applications, the preset limit may be a range of amounts, such as 0-500000.

Further, taking the pre-stored account security level as an example, the pre-stored account security level is three-level, two-level and one-level according to the security degree order, and the server determines the preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, including: when the updated pre-stored account security level is three-level, the preset quota amount corresponding to the account quota input sub-interface can be 99999999999; when the updated pre-stored account security level is the second level, the preset quota amount corresponding to the account quota input sub-interface can be 0-500000, and the user can input any number from 0-500000 in the account quota input sub-interface; when the updated pre-stored account security level is the first level, the preset quota amount corresponding to the account quota input sub-interface may be 0. That is, the preset quota amount corresponding to the account quota input sub-interface is proportional to the security degree of the account security level.

Furthermore, the server can also check the quota input by the account quota input sub-interface according to the preset quota. If the quota input by the account quota input sub-interface is not matched with the preset quota, the server pushes a matching failure message, wherein the matching failure message comprises a matching failure reason and a preset quota prompt.

And S600, performing resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota amount acquired through the account quota input sub-interface.

Specifically, the server starts from three dimensions of a pre-stored object security level corresponding to the object identifier, an updated pre-stored account security level corresponding to the object identifier and the account identifier, and a quota amount obtained through an account quota input sub-interface, and performs subsequent resource management and control on the object identifier based on the multiple dimensions. For example, when a user wants to take out a certain amount of resources from the account a, the server can evaluate the account a of the user through the pre-stored object security level corresponding to the object identifier and the updated pre-stored account security level corresponding to the object identifier and the account identifier, and evaluate the certain amount of resources which the user wants to take out from the account a by adopting the quota obtained through the account quota input sub-interface, so as to judge whether the user can take out the certain amount of resources from the account a, so as to realize resource management on the user corresponding to the object identifier.

In the resource management method, in the whole process, because the object identifier corresponds to at least one account identifier, the pre-stored account security level corresponding to the object identifier and the account identifier can be accurately updated based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier; further, after updating the pre-stored account security level, the account preset limit amount can be determined according to the updated pre-stored account security level, and then accurate resource management is performed on the object identification from three dimensions of the preset object client security level, the updated pre-stored account security level and the limit amount.

In some embodiments, the account level processing interface further includes an account processing type sub-interface; updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, including:

Specifically, the account level processing interface further comprises an account processing type sub-interface, wherein the account processing type sub-interface comprises selection of a processing type, and the processing type comprises a maintenance type and a query type. Under the condition that the processing type is maintenance, the server can maintain and update the pre-stored account security level corresponding to the object identifier and the account identifier through the account security level input by the account security level input sub-interface. Further, since one object corresponds to at least one account, the security level of the account refers to the security level of the object, and thus, when updating the pre-stored account security level corresponding to the object identifier and the account identifier, the updating is performed based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier.

Further, in the case that the processing type is query, even if the account security level input through the account security level input sub-interface is obtained, the server cannot update the pre-stored account security level based on the input account security level and the pre-stored object security level corresponding to the pre-stored object identifier.

In this embodiment, the processing type selected by the account processing type sub-interface is limited, so that the functions of query and maintenance are separated, and the pre-stored account security level can be efficiently updated under the condition that the processing type is maintenance, so that the pre-stored account security level is prevented from being updated by mistake due to the fact that the account security level is input under the condition that only query is needed.

In some embodiments, as shown in FIG. 3, the account level processing interface also includes an account processing type sub-interface; the method further comprises the steps of:

and S700, inquiring the pre-stored account security level corresponding to the object identifier and the account identifier under the condition that the processing type selected by the account processing type sub-interface is the inquiring type.

Specifically, in the case where the processing type selected by the account processing type sub-interface is the query type, the server cannot implement the maintenance function. Further, in the case that the processing type selected by the account processing type sub-interface is the query type, the user clicks the submit button on the terminal, and the server can query the pre-stored account security level corresponding to the object identifier and the account identifier based on the obtained object identifier and the account identifier.

S800, pushing the account processing type switching message if the searched pre-stored account security level is inconsistent with the account security level obtained through the account security level input sub-interface.

Specifically, if the searched pre-stored account security level is inconsistent with the account security level obtained through the account security level input sub-interface, that is, the historically stored account security level is inconsistent with the current actual account security level, the pre-stored account security level needs to be maintained and updated. If maintenance is required, the processing type selected by the account processing type sub-interface needs to be switched to the maintenance type. At this time, the server pushes an account processing type switching message to the terminal. The terminal acquires the account processing type switching message and displays the account processing type switching message to the user so that the user can judge whether the processing type is to be switched or not, and therefore the pre-stored account security level is updated.

S900, switching the processing type selected by the account processing type sub-interface from the query type to the maintenance type under the condition that the first confirmation message corresponding to the account processing type switching message is acquired.

Specifically, if the user confirms that the processing type selected by the account processing type sub-interface is to be switched to the maintenance type, uploading a first confirmation message corresponding to the account processing type switching message to the terminal, and forwarding the first confirmation message to the server by the terminal. And under the condition that the server acquires the first confirmation message, switching the processing type selected by the account processing type sub-interface from the query type to the maintenance type. In addition, the user can update the processing type selected by the account processing type sub-interface by himself.

In this embodiment, under the condition that the processing type selected by the account processing type sub-interface is the query type, the pre-stored account security level corresponding to the object identifier and the account identifier is accurately queried, so as to accurately determine whether the pre-stored account security level at this time is consistent with the currently input account security level, and whether the processing type selected by the account processing type sub-interface needs to be switched from the query type to the maintenance type can be determined, so as to update the pre-stored account security level corresponding to the object identifier and the account identifier, thereby realizing more accurate resource management.

In some embodiments, in the case where the traffic type is an account type, pushing an account level processing interface, the account level processing interface including an account security level input sub-interface, an account quota input sub-interface, and an object processing type sub-interface. In the case that the processing type selected by the object processing type sub-interface is the query type, the account quota input sub-interface is set to a non-editable state; only in the case that the processing type selected by the object processing type sub-interface is the maintenance type, the quota amount of the account quota input sub-interface can be edited.

In some embodiments, the method further comprises:

pushing an object level processing interface under the condition that the service type is the user type; when the processing type selected by the object processing type sub-interface is a maintenance type, acquiring an object identifier and an object security level input through an object security level input interface; and updating the pre-stored object security level corresponding to the object identifier based on the object security level.

The object level processing interface comprises an object security level input interface and an object processing type sub-interface.

Specifically, in the case that the service type is the user type, processing of the object security level is performed at this time, so that the object security level input interface and the object processing type sub-interface are pushed. The object security level input interface is used for inputting the object security level, and the object processing type sub-interface comprises a query type and a maintenance type. When the processing type selected by the object processing type sub-interface is a maintenance type, the object security level pre-stored in the database can be updated based on the object security level input through the object security level input interface, i.e. the pre-stored object security level corresponding to the object identifier is updated to the object security level input through the object security level input interface.

Further, the object security level pre-stored in the database is associated with the pre-stored object identifier, so that the object security level pre-stored in the database is acquired based on the object identifier, that is, the server acquires the object identifier uploaded by the terminal, inquires whether the object identifier consistent with the object identifier uploaded by the terminal exists in the object identifier pre-stored in the database, and if so, acquires the pre-stored object security level corresponding to the object identifier.

Further, in the case that the processing type selected by the object processing type sub-interface is maintenance, the server may further push the evaluation basis selection sub-interface and other reasons to the terminal, so that the user may select or input the evaluation basis and other reasons at the terminal. The evaluation basis refers to an optional evaluation basis of the object security level input by the user through the object security level input sub-interface, for example, the optional evaluation basis includes: business conditions, transaction conditions, blacklist conditions, tax and other reasons, etc. The user can select the safety grade evaluation basis from the selectable evaluation basis in the evaluation basis selection sub-interface of the terminal, and if the evaluation basis selected by the user in the evaluation basis selection sub-interface is the evaluation basis except for other reasons, the server can maintain other reason input sub-interfaces in a non-editable state; if the evaluation basis selected by the user in the evaluation basis sub-interface is other reasons, the server updates other reasons input sub-interfaces into an editable state; in other words, the other reason input sub-interface defaults to be set gray and can not be edited, and only when the evaluation basis selected by the user in the evaluation basis selection sub-interface is the other reason, the other reason input sub-interface can be edited, and at this time, the user inputs the evaluation reason corresponding to the security level of the object in the other reason input sub-interface which can be edited by the terminal. In addition, if the user wants to re-select the process type, rating basis, or other reasons, the reset button on the interface may be clicked to reset the process type, rating basis, or other reasons.

In the embodiment, when the maintenance type is selected by pushing the two interfaces, the object security level is input through the object security level input interface, so that the updating efficiency of the pre-stored object security level corresponding to the object identifier is improved; and only when the processing type selected by the object processing type sub-interface is the maintenance type, the pre-stored object security level corresponding to the object identification can be updated, and the accuracy of updating operation can be improved.

In some embodiments, the method further comprises:

inquiring a pre-stored object security level corresponding to the object identifier when the processing type selected by the object processing type sub-interface is an inquiring type; if the pre-stored object security level is inconsistent with the object security level, pushing an object processing type switching message; and under the condition that a second confirmation message corresponding to the object processing type switching message is acquired, switching the processing type selected by the object processing type sub-interface from the query type to the maintenance type.

Specifically, when the processing type selected by the object processing type sub-interface is the query type, the user clicks a submit button in the object level processing interface, namely, the object security level query request can be uploaded to the server, and the object security level query request carries an object identifier; the server receives the object security level inquiry request, extracts the object identifier carried in the object security level inquiry request, and inquires the pre-stored object security level corresponding to the object identifier; if the inquired pre-stored object security level is inconsistent with the object security level input through the object security level input interface, the pre-stored object security level in the database is required to be updated, and at the moment, an object processing type switching message is required to be pushed to the terminal; the terminal displays the object processing type switching message to the user, the user confirms whether the processing type selected by the object processing type sub-interface needs to be switched, and if the user confirms that the processing type needs to be switched from the query type to the maintenance type, the second confirmation message is uploaded to the server; and the server switches the processing type selected by the object processing type sub-interface from the query type to the maintenance type under the condition that the second confirmation message is acquired. In addition, the user can update the processing type selected by the object processing type sub-interface by himself.

Further, in the case that the processing type selected by the object processing type sub-interface is a query, the server may push the evaluation-based selection sub-interface and the other reason input sub-interface to the terminal, but the evaluation-based selection sub-interface and the other reason input sub-interface are both in a non-editable state.

In this embodiment, under the condition that the processing type selected by the object processing type sub-interface is the query type, the pre-stored account security level corresponding to the object identifier is accurately queried, so as to accurately determine whether the pre-stored object security level at this time is consistent with the currently input object security level, and whether the processing type selected by the object processing type sub-interface needs to be switched from the query type to the maintenance type can be determined, so as to update the pre-stored account security level corresponding to the object identifier, thereby realizing more accurate resource management.

In some embodiments, the method further comprises:

pushing a history grade inquiry selection interface; acquiring an object identifier, an account identifier and a grade inquiry type selected through a history grade inquiry selection interface, and inquiring a history security grade corresponding to the object identifier, the account identifier and the grade inquiry type; pushing historical security levels.

Specifically, the server may further push a history grade query selection interface to the terminal to perform a query of a history security grade, where the history grade query selection interface includes a grade query type; the rank query types include an object rank query type and an account rank query type. The user inputs or selects account identification and grade inquiry type at the terminal, clicks an inquiry key to send the input data to the terminal, and the terminal forwards the input data to the server; the server can inquire the object identifier corresponding to the account identifier according to the account identifier forwarded by the terminal, and further inquire the historical security level corresponding to the object identifier, the account identifier and the level inquiry type according to the object identifier, the account identifier and the level inquiry type.

Further, the historical security level corresponding to the object identifier, the account identifier and the level query type queried by the server can be pushed to the terminal, and the terminal sequentially displays the historical security level in a table in the historical level query selection interface, wherein the displaying order can be ordered from late to early according to the update time. In addition, the server can also query the update date, assessment basis, other reasons, single quota, single daily quota, assessment person, assessment organization and identification and the like corresponding to the historical security level.

In practical application, if the account identifier and the rank query type input or selected by the user at the terminal need to be modified and the query key is not clicked yet, the reset key can be clicked to reset the account identifier and the rank query type.

In this embodiment, the history records can be queried by pushing the history grade query selection interface, so that the history security grade has a certain traceability, so that a certain processing needs to be performed on the history records later.

In some embodiments, querying the historical security level corresponding to the object identification, the account identification, and the level query type includes:

under the condition that the grade query type is an object grade query type, querying a historical object security grade corresponding to the object identification and the object grade query type; and querying the historical account security level corresponding to the object identification, the account identification and the account level query type under the condition that the level query type is the account level query type.

Specifically, in the case that the class query type is the object class query type, the server may query, through the object identifier, a historical object security class corresponding to the object identifier and the object class query type, and may query an update date, a rating basis, other reasons, a rating person, a rating mechanism, an identifier, and the like corresponding to the historical object security class; in the case that the class query type is an account class query type, the server may query the historical object security class corresponding to the object identifier, the account identifier and the object class query type through the object identifier, the account identifier, and may query the update date, the single quota, the single daily quota, the rater, the rating institution, the identifier and the like corresponding to the historical account security class.

In this embodiment, by querying the security level of the historical object and the security level of the historical account in different manners, the security level of the historical object and the security level of the historical account can be accurately distinguished, so as to implement classified query for the user.

In some embodiments, determining the preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier comprises;

and determining a preset single-time quota amount and a preset single-day quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier.

The method comprises the steps of presetting a single quota amount for checking the single quota amount input by an account quota input sub-interface, presetting a single daily quota amount for checking the single daily quota amount input by the account quota input sub-interface.

Specifically, in the application, the preset quota amount corresponding to the account quota input sub-interface can be set based on the updated pre-stored account security level corresponding to the object identifier and the account identifier. The preset quota amounts corresponding to the different pre-stored account security levels are different. And the preset quota amount in the application comprises a preset single quota amount and a preset single daily quota amount. The server pushes the account limit input sub-interface, namely the account single-stroke limit input sub-interface and the account single-day limit input sub-interface are pushed, the single-stroke limit amount input by the user in the account single-stroke limit input sub-interface needs to be matched with the single-stroke preset limit amount, and the single-day limit amount input in the account single-stroke and limit input sub-interface needs to be matched with the single and the preset limit amount.

Further, the user inputs the single quota amount in the account single quota input sub-interface of the terminal, the terminal forwards the single quota amount input by the user to the server, the server checks the single quota amount input by the user according to the preset single quota amount, and if the single quota amount input by the user is not matched with the preset single quota amount, the input failure message is pushed. If the single quota input by the user is matched with the preset single quota, pushing the input success message.

Furthermore, in the case that the service type is the account type, the server pushes a single day accumulated quota sub-interface corresponding to the account quota input sub-interface, and the single day accumulated quota sub-interface is in an uneditable state. Under the condition that the service type is switched from the account type to the user type, the accumulated quota sub-interface is hidden in a single day; the server obtains the object identifier and the account identifier, can inquire the single-day accumulated quota corresponding to the object identifier and the account identifier from the database, and sends the single-day accumulated quota corresponding to the object identifier and the account identifier to the terminal, and the single-day accumulated quota is displayed in a single-day accumulated quota sub-interface by the terminal.

In this embodiment, by determining the preset single quota amount and the preset single daily quota amount corresponding to the account quota input sub-interface, both the single quota and the single daily quota of the account can be limited, so that more accurate differential resource management is performed on two dimensions of single resource transfer and single daily resource transfer of a user.

In some embodiments, in the case that the service type is the object type, three aspects of querying the object security level, maintaining the object security level and querying the object security level history are added, and columns for evaluating the basis and other reasons can be added when the user performs resource management.

Under the condition that the service type is the account type, three aspects of inquiring the account security level, maintaining the account security level and inquiring the account security level history are added, so that the user can accurately inquire, maintain the account security level and inquiring history change records. And the setting of the account security level needs to be based on the setting of the object security level, the account security level does not record the rating basis, but the single quota amount and the single daily quota amount need to be set according to the account security level. When the resource management is carried out on the user in the follow-up, the resource transfer process of the user is controlled according to the set single quota and the single daily quota, and meanwhile, the accumulated quota of the single day is recorded.

In some embodiments, the application provides a resource management method, and data interaction among a server, a resource management interface on a terminal and a user three party is adopted to realize resource management.

Specifically, the resource management interface on the terminal includes an account identifier input box, an account name input box, an object identifier input box, an object name input box, a service type selection box, a query key and a first reset key, wherein the account name input box is in an editable state, and the account name input box, the object identifier input box and the object name input box are in non-editable states.

The user inputs an account identifier in a standard format on a resource management interface on the terminal, and the server inquires an account name, an object identifier and an object name corresponding to the account identifier based on the account identifier uploaded by the terminal and respectively and reversely displays the account name, the object identifier and the object name corresponding to the account identifier into a corresponding input box in the resource management interface.

When the user selects the service type as the account type in the service type selection frame, the server pushes an account grade processing page to the terminal; when the user selects the service type as the user type in the service type selection box, the server pushes the object class processing page to the terminal. If the user wants to reselect the service type or reenter the account identifier at this time, the user may click on the first reset button to reset the entered account identifier or selected service type. Further, at this time, the user may click on the query button, and the recorded information related to the historical security level is obtained.

Further, under the condition that the user selects the service type as the object type in the service type selection frame, the server pushes an object grade processing interface to the terminal, wherein the object grade processing interface comprises an object security grade input interface, an object processing type sub-interface, a rating basis selection frame, other reason input frames, a submitting button and a second reset button, the object processing type selection frame comprises a query type and a maintenance type, and the object processing type selection frame and the rating basis selection frame display text information of 'please select' in default. The user can select the object security level in the object security level selection frame, and when the account processing type selection frame is the query type, the user clicks the submit button to query the object security level corresponding to the object identifier; when the account processing type selection box is a maintenance type, the user can edit in the evaluation basis selection box and other reason input boxes, and after the editing is completed, the user clicks a submit button, so that the pre-stored object security level can be updated through the object security level selected in the object security level selection box.

Under the condition that a user selects a service type as an account type in a service type selection frame, pushing an account grade processing interface to a terminal by a server, wherein the account grade processing interface comprises an account processing type selection frame, an account security grade selection frame, an account single-stroke quota input frame, an account single-day accumulated quota input frame, a submitting button and a second reset button, the account processing type selection frame comprises a query type and a maintenance type, and the account processing type selection frame defaults to display text information of 'please select'; the user can select the account security level in the account security level selection frame, and when the account processing type selection frame is a query type, the user clicks a submit button to query the account security level corresponding to the object identifier and the account identifier; when the account processing type selection box is of a maintenance type, the user clicks the submit button, and the pre-stored account security level can be updated through the account security level selected in the account security level selection box and the pre-stored object security level.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a resource management device for realizing the above-mentioned resource management method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in one or more embodiments of the resource management device provided below may refer to the limitation of the resource management method hereinabove, and will not be repeated herein.

In some embodiments, as shown in fig. 4, there is provided a resource management apparatus comprising: a request acquisition module 100, an interface pushing module 200, a data acquisition module 300, a data processing module 400, a quota determination module 500, and a resource management module 600, wherein:

a request acquisition module 100, configured to receive a service processing request, where the service processing request carries a service type;

the interface pushing module 200 is configured to push an account level processing interface when the service type is an account type, where the account level processing interface includes an account security level input sub-interface and an account quota input sub-interface;

the data acquisition module 300 is configured to acquire an object identifier, an account identifier, and an account security level input through an account security level input sub-interface;

the data processing module 400 is configured to update a pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, where the object identifier corresponds to at least one account identifier, and the pre-stored account security levels corresponding to the account identifiers corresponding to the object identifier are the same or different;

the quota determining module 500 is configured to determine a preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, where the preset quota amount is used to verify the quota amount input by the account quota input sub-interface;

The resource management module 600 is configured to perform resource management on the object identifier based on the pre-stored object security level corresponding to the object identifier, the updated pre-stored account security level corresponding to the object identifier and the account identifier, and the quota obtained through the account quota input sub-interface.

In some embodiments, the account level processing interface further includes an account processing type sub-interface; the data processing module is further used for updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier under the condition that the processing type selected by the account processing type sub-interface is the maintenance type.

In some embodiments, the account level processing interface further includes an account processing type sub-interface; the device also comprises a first query module, wherein the first query module is used for querying a pre-stored account security level corresponding to the object identifier and the account identifier under the condition that the processing type selected by the account processing type sub-interface is a query type; pushing an account processing type switching message if the searched pre-stored account security level is inconsistent with the account security level obtained through the account security level input sub-interface; and under the condition that the first confirmation message corresponding to the account processing type switching message is acquired, switching the processing type selected by the account processing type sub-interface from the query type to the maintenance type.

In some embodiments, the apparatus further includes an object level update module, where the object level update module is configured to push an object level processing interface, where the object level processing interface includes an object security level input interface and an object processing type sub-interface, where the service type is a user type; when the processing type selected by the object processing type sub-interface is a maintenance type, acquiring an object identifier and an object security level input through an object security level input interface; and updating the pre-stored object security level corresponding to the object identifier based on the object security level.

In some embodiments, the apparatus further comprises a history rank query module for pushing the history rank query selection interface; acquiring an object identifier, an account identifier and a grade inquiry type selected through a history grade inquiry selection interface, and inquiring a history security grade corresponding to the object identifier, the account identifier and the grade inquiry type; pushing historical security levels.

In some embodiments, the history grade query module is further configured to query a history object security grade corresponding to the object identifier and the object grade query type if the grade query type is the object grade query type; and querying the historical account security level corresponding to the object identifier, the account identifier and the account level query type under the condition that the level query type is the account level query type.

In some embodiments, the quota determining module is further configured to determine, based on the updated pre-stored account security level corresponding to the object identifier and the account identifier, a preset single quota amount corresponding to the account quota input sub-interface and a preset single daily quota amount, where the preset single quota amount is used to verify the single quota amount input by the account quota input sub-interface, and the preset single daily quota amount is used to verify the single daily quota amount input by the account quota input sub-interface.

The respective modules in the above-described resource management apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In some embodiments, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing data such as object identification, account security level, object security level and the like. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a resource management method.

It will be appreciated by those skilled in the art that the structure shown in fig. 5 is merely a block diagram of some of the structures associated with the present application and is not limiting of the computer device to which the present application may be applied, and that a particular computer device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.

In some embodiments, there is also provided a computer device comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In some embodiments, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, carries out the steps of the method embodiments described above.

In some embodiments, a computer program product is provided, comprising a computer program which, when executed by a processor, implements the steps of the method embodiments described above.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the various embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magnetic random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (Phase Change Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in the form of a variety of forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), and the like. The databases referred to in the various embodiments provided herein may include at least one of relational databases and non-relational databases. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic units, quantum computing-based data processing logic units, etc., without being limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The above examples only represent a few embodiments of the present application, which are described in more detail and are not to be construed as limiting the scope of the present application. It should be noted that it would be apparent to those skilled in the art that various modifications and improvements could be made without departing from the spirit of the present application, which would be within the scope of the present application. Accordingly, the scope of protection of the present application shall be subject to the appended claims.

Claims

1. A method of resource management, the method comprising:

2. The method of claim 1, wherein the account level processing interface further comprises an account processing type sub-interface; the updating the pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier, includes:

3. The method of claim 1, wherein the account level processing interface further comprises an account processing type sub-interface; the method further comprises the steps of:

4. A method according to any one of claims 1 to 3, characterized in that the method further comprises:

5. The method according to claim 4, wherein the method further comprises:

6. The method according to claim 1, wherein the method further comprises:

Pushing a history grade inquiry selection interface;

pushing the historical security level.

7. The method of claim 6, wherein querying the historical security level corresponding to the object identification, account identification, and the level query type comprises:

8. The method of claim 1, 6 or 7, wherein determining the preset quota amount corresponding to the account quota input sub-interface based on the updated pre-stored account security level corresponding to the object identification and the account identification comprises;

9. A resource management apparatus, the apparatus comprising:

10. The apparatus of claim 9, wherein the account level processing interface further comprises an account processing type sub-interface; the data processing module is further configured to update a pre-stored account security level corresponding to the object identifier and the account identifier based on the account security level and the pre-stored object security level corresponding to the pre-stored object identifier when the processing type selected by the account processing type sub-interface is a maintenance type.

11. The apparatus of claim 9, wherein the account level processing interface further comprises an account processing type sub-interface; the device also comprises a first query module, wherein the first query module is used for querying a pre-stored account security level corresponding to the object identifier and the account identifier when the processing type selected by the account processing type sub-interface is a query type; pushing an account processing type switching message if the searched pre-stored account security level is inconsistent with the account security level obtained through the account security level input sub-interface; and under the condition that a first confirmation message corresponding to the account processing type switching message is acquired, switching the processing type selected by the account processing type sub-interface from the query type to the maintenance type.

12. The apparatus according to any one of claims 9 to 11, further comprising an object level update module configured to push an object level processing interface, where the service type is a user type, the object level processing interface including an object security level input interface and an object processing type sub-interface; when the processing type selected by the object processing type sub-interface is a maintenance type, acquiring an object identifier and an object security level input through the object security level input interface; and updating the pre-stored object security level corresponding to the object identifier based on the object security level.

13. The apparatus of claim 12, further comprising a process type switching module configured to query a pre-stored object security level corresponding to the object identification when the process type selected by the object process type sub-interface is a query type; if the pre-stored object security level is inconsistent with the object security level, pushing an object processing type switching message; and under the condition that a second confirmation message corresponding to the object processing type switching message is acquired, switching the processing type selected by the object processing type sub-interface from the query type to the maintenance type.

14. The apparatus of claim 9, further comprising a history rank query module for pushing a history rank query selection interface; acquiring an object identifier, an account identifier and a grade inquiry type selected through the history grade inquiry selection interface, and inquiring a history security grade corresponding to the object identifier, the account identifier and the grade inquiry type; pushing the historical security level.

15. The apparatus of claim 14, wherein the historical grade query module is further configured to query a historical object security grade corresponding to the object identification and the object grade query type if the grade query type is an object grade query type; and querying a historical account security level corresponding to the object identifier, the account identifier and the account level query type under the condition that the level query type is the account level query type.

16. The apparatus of claim 9, 14 or 15, wherein the quota determination module is further configured to determine, based on the updated pre-stored account security levels corresponding to the object identifier and the account identifier, a preset single quota amount corresponding to the account quota input sub-interface and a preset single daily quota amount, where the preset single quota amount is used to verify a single quota amount input by the account quota input sub-interface, and the preset single daily quota amount is used to verify a single daily quota amount input by the account quota input sub-interface.

17. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any one of claims 1 to 8 when the computer program is executed.

18. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 8.

19. A computer program product comprising a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method of any one of claims 1 to 8.