CN112288565A

CN112288565A - System, method and device for executing service

Info

Publication number: CN112288565A
Application number: CN202011086114.4A
Authority: CN
Inventors: 孙宇; 林浩; 王冬; 戴明燃; 金谋青; 汤晨辉; 高国强; 纪明林; 严明; 刘运飞
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2020-10-12
Filing date: 2020-10-12
Publication date: 2021-01-29

Abstract

The specification discloses a system, a method and a device for executing service, wherein a service resource limit and an allocation rule are determined according to a service information contract subsystem carried in a first service request, a limit allocation subsystem determines the remaining limit of the service resource limit according to service information, an allocation result is determined according to the service resource limit, an account subsystem determines a target scene account according to the service information and records account change, and when a fulfillment condition is met, a fulfillment subsystem determines resource repayment information and sends prompt information to a user according to the resource repayment information to prompt the user to execute the resource repayment service. The credit services of different types can use the system to execute the business, so that different departments of the same organization do not need to execute the business through respective special systems, and the operation cost of financial institutions is reduced.

Description

System, method and device for executing service

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a system, a method, and an apparatus for executing a service.

Background

At present, as society progresses and markets further develop, credit services provided by the financial industry are not limited to traditional credit services such as credit cards, but various types of credit services are gradually provided for users. Such as credit credits, mini credits, etc.

In the prior art, because the electronic industry starts relatively late, the system used in the financial institution is generally constructed based on the product model of the traditional credit card service, as shown in fig. 1. Fig. 1 is a schematic diagram of a conventional credit card product model, wherein the product model includes five parts, namely, an organization, a product, an account, a customer, and a product certificate. The connecting lines among the parts represent the interactive relationship existing among the parts of the product model when the business is executed. For example, the connection line between the product certificate and the account indicates that when the service is executed, the product certificate needs to be determined by the subsystem corresponding to the product certificate and sent to the subsystem corresponding to the account, and then the subsystem corresponding to the account determines the account corresponding to the product certificate so as to continue to execute the service.

Therefore, during system development, development of subsystems or code modules in each system and configuration of information transmission can be carried out according to each part and interaction in the product model.

As described above, while the credit service is continuously developed, the product model of the conventional credit card service obviously cannot meet the requirement of the new credit service, and therefore, the product model required by the new credit service is determined to construct a system for executing the new credit service by modifying or adding subsystems on the basis of the product model of the credit card service.

However, since different types of credit services are typically provided by different departments in a financial institution, and different product models exist for different credit services. However, because the internal subsystems of the systems constructed based on different product models are not completely consistent, different systems are incompatible, so that a corresponding system needs to be constructed for each type of credit service in a financial institution, and the operating cost of the financial institution is high.

Based on the above problems, the present application provides a new service execution system, method and device.

Disclosure of Invention

The present specification provides a system and a storage medium for performing a service, which partially solve the above-mentioned problems occurring in the prior art.

The embodiment of the specification adopts the following technical scheme:

the present specification provides a system for executing a service, the system comprising: contract subsystem, account subsystem, resource limit distribution subsystem, the subsystem of performing contract, wherein:

the contract subsystem is used for determining a service resource limit and an allocation rule according to service information carried in a first service request when the first service request initiated by a user is received, and sending the service information, the service resource limit and the allocation rule to the limit allocation subsystem and the account subsystem, wherein the service information at least comprises scene information, an identifier of a service contract and the service resource limit requested by the user.

And the limit distribution subsystem is used for determining a service resource limit according to the service information, distributing the remaining limit according to at least one of the service resource limit and the distribution rule when the service resource limit is not greater than the remaining limit of the service resource limit, and sending a distribution result to the account subsystem.

And the account subsystem is used for determining a target scene account from all scene accounts contained in a contract account corresponding to the identifier of the service contract according to the service information, and recording account change in the determined target scene account according to the distribution result.

The fulfillment subsystem is configured to, for each fulfillment account, when the fulfillment account meets fulfillment conditions, obtain, from the account subsystem, a contract account and account change of a scene account under a management account corresponding to the fulfillment account, determine resource repayment information according to the account change, and send prompt information to the user according to the resource repayment information, where the prompt information is used to prompt the user to execute a resource repayment service.

Wherein the fulfillment account is an account corresponding to the management account determined by the fulfillment subsystem according to the service contract; and the management account is the corresponding management account determined by the service contract and is the account subsystem.

Optionally, the contract subsystem is further configured to, before receiving the first service request initiated by the user, create a service contract and determine resource quota information according to the received second service request initiated by the user, send the service contract to the account subsystem and the performing subsystem, and send the resource quota information to the quota allocation subsystem.

The account subsystem is further configured to create a contract account corresponding to the service contract according to the received service contract, and determine a management account corresponding to the service contract, where the management account includes at least one contract account.

And the fulfillment subsystem is used for determining a fulfillment account corresponding to the service contract according to the received service contract and establishing a corresponding relation of a management account corresponding to the service contract.

And the limit distribution subsystem determines the user resource limit corresponding to the user and the service resource limit corresponding to the service contract according to the received limit information.

Optionally, the contract subsystem is further configured to determine a product credential according to the received second service request initiated by the user, and determine an association relationship between the product credential and the service contract, the management account, and the fulfillment account.

Optionally, the contract subsystem is configured to determine a product certificate from service information carried in a first service request initiated by the user, determine an identifier of the service contract according to the product certificate, determine an allocation rule according to a service contract corresponding to the identifier of the service contract, and determine a service resource limit according to the determined service contract and a resource quota value included in the service contract information.

The account subsystem is used for determining a contract account according to an identifier of a service contract in the service information, judging whether a scene account corresponding to the scene information exists in the scene accounts contained in the contract account, if so, taking the scene account corresponding to the scene information as a target scene account, and if not, creating the scene account corresponding to the scene information as the scene account contained in the contract account; the context account is determined by at least one of a type of a service contract, a type of a resource, and a type of other implementers of the first service request.

Optionally, the fulfillment subsystem is configured to determine a management account corresponding to the fulfillment account, and send an acquisition request carrying an identifier of the management account to the account subsystem.

And the account subsystem is used for determining the management account according to the identification carried by the acquisition request, determining the record of account change of each scene account according to each scene account in each contract account contained in the management account, and returning the determined record of account change to the fulfillment subsystem.

And the fulfillment subsystem is used for determining a current fulfillment bill according to the received record of the account change.

Optionally, the performing subsystem is configured to, for each performing period, determine a performing order corresponding to the performing period when there are still unreleased resources in the performing period, and determine resource repayment information according to the determined performing order corresponding to each performing period.

Optionally, the allocation rule includes a first allocation rule and a second allocation rule. The quota allocation subsystem is used for continuously allocating the remaining quota after the service resource quota allocation according to the first allocation rule; and sending the allocation result to the account subsystem.

And the quota allocation subsystem is used for allocating the remaining quota according to the second allocation rule and sending the allocation result to the account subsystem when the time point included by the second allocation rule is reached or a settlement request which is sent by the user and meets the second allocation rule is received.

The present specification provides a method of performing a service, comprising:

receiving a first service request initiated by a user, and determining a service resource line and an allocation rule according to service information carried in the first service request, wherein the service information at least comprises scene information, an identifier of a service contract and the service resource line requested by the user.

And determining a service resource limit according to the service information, and when the service resource limit is not greater than the remaining limit of the service resource limit, allocating the remaining limit according to at least one of the service resource limit and the allocation rule, and determining an allocation result.

And according to the service information, determining a target scene account from all scene accounts contained in a contract account corresponding to the identifier of the service contract, and recording account change in the determined target scene account according to the distribution result.

For each fulfillment account, when the fulfillment account meets fulfillment conditions, acquiring a contract account and account variation of a scene account under a management account corresponding to the fulfillment account, determining resource repayment information according to the account variation, and sending prompt information to the user according to the resource repayment information, where the prompt information is used to prompt the user to execute a resource repayment service, the fulfillment account is an account corresponding to the management account determined according to the service contract, and the management account is a corresponding management account determined according to the service contract.

The present specification provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the system for performing a service described above.

The technical scheme adopted by the specification can achieve the following beneficial effects:

in the service-oriented system provided by the present specification, different subsystems are established functionally, the service is completed through interaction between the different subsystems after receiving the service request, and the system provided by the present application can be completely compatible for different credit services.

Firstly, according to service information in a first service request initiated by a user, determining a service resource limit and an allocation rule, determining a remaining limit of the service resource limit and a remaining limit of the service resource limit according to the service information, allocating the remaining limit of the service resource limit according to the service resource limit and the allocation rule, determining an allocation result, recording account change according to the allocation result, and when a fulfillment condition is met, determining resource repayment information through the account change so as to enable a user to execute a resource repayment service. Therefore, the system can be compatible with different types of credit services, when new services are generated, a new system does not need to be built, and the operation cost and the system maintenance cost of an organization are reduced.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

FIG. 1 is a schematic diagram of a conventional credit card product model;

fig. 2 is a schematic structural diagram of a system for executing a service according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of an account structure provided by embodiments of the present description;

fig. 4 is a schematic flowchart of a system for executing a service according to an embodiment of the present disclosure;

fig. 5 is a flowchart illustrating a method for executing a service according to an embodiment of the present disclosure;

fig. 6 is a flowchart illustrating a method for executing a service according to an embodiment of the present disclosure.

Fig. 7 is a schematic diagram of an electronic device corresponding to fig. 5 provided in an embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present disclosure more apparent, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person skilled in the art without making any inventive step based on the embodiments in the description belong to the protection scope of the present application.

In the prior art, different types of credit services provided by financial institutions use different systems, and the different systems are not compatible with each other, mainly because the systems used by the credit services of all types are improved based on the traditional credit card product model. The differences of different types of credit services in terms of service objects, provided service contents, rights and interests, repayment rules and the like also cause that when the credit card product model is improved, the improvement directions are not completely the same, so that systems used by different credit services cannot be compatible with each other.

The system which can be improved based on the traditional credit card product model and used by different credit services is based on the following steps: for example, the different credit services are provided by the institution, and then receive additional reimbursement resources to meet the user's demand for financial services.

Since the financial service industry is developing, various credit services are gradually developed, and therefore systems required by different credit services are also independently developed, which is also a reason for incompatibility among different systems at present, and as the credit services mature at present, different credit services have a converged demand, for example, different credit services are no longer provided by different departments of a financial institution, but are managed in a unified manner, and a plurality of credit services are provided by the same department. Therefore, when the existing systems for various credit services are incompatible and unable to communicate with each other, a system for performing services that can solve the needs of different credit services is needed.

Based on this, the application provides a new system for executing business, so that the same system can be compatible with different types of credit services, and the operation cost of financial institutions is further reduced.

Fig. 2 is a system for executing a service according to an embodiment of the present application, where the system includes: the system comprises a contract subsystem, an amount distribution subsystem, an account subsystem and a performance subsystem.

From a software perspective, in one or more embodiments provided in the present specification, each subsystem in the system is code that can run on a server, and the functions of each subsystem are implemented by running the code of each subsystem. In addition, in this specification, codes of different subsystems are independent from each other, each subsystem may communicate or transmit data with other subsystems through a preset data interface, and iterative update and testing of codes may be performed on each subsystem separately through the independent subsystems.

From a hardware perspective, in one or more embodiments provided in the present specification, the subsystems may run on different servers respectively, or may run on the same server. Moreover, when each subsystem runs on a different server, for each subsystem, the server running the subsystem may be a single server, or multiple servers, such as a distributed server, which is not limited in this specification and may be specifically set as needed. Of course, since the operating pressures of different subsystems may be different, the servers for operating the systems may also be configured according to the operating pressures of the different subsystems. For example, a distributed server comprising a plurality of servers may be configured to operate the contract subsystem and a single server may be configured to operate the performance subsystem, assuming that the contract subsystem operates at a much greater pressure than the performance subsystem. Or, the performing subsystem and other subsystems are configured to run on the same server, and so on.

In one or more embodiments provided in this specification, an example in which the system for executing the service provides the enterprise network disk leasing service and the system for executing the service provides the credit service is taken as an example.

The contract subsystem in the system is used for receiving a first service request, wherein in an enterprise network disk leasing service scene, the first service request is a network disk leasing service request initiated by a user, and in a credit service scene, the first service request is a credit service request initiated by the user. And, the first service request may also carry service information. The service information at least comprises scene information, an identifier of a service contract and a service resource limit requested by the user. In the enterprise network disk leasing service scene, the service resource limit is the network disk space which needs to be leased by the user, and in the credit service scene, the service resource limit is the amount of money which needs to be lent by the user. The contract subsystem can determine the service resource limit according to the service information after receiving the first service request, wherein the service resource limit is the resource limit required by the user to initiate the first service request. And the contract subsystem can also determine the service contract of the user from the prestored service contracts according to the identification of the service contract in the service information so as to determine the distribution rule according to the determined service contract. Finally, the contract subsystem can send the determined service information, the service resource limit and the allocation rule to the limit allocation subsystem and the account subsystem, so that the limit allocation subsystem and the account subsystem continue to execute the service corresponding to the first service request.

The content of the service contract may include the service type, the distribution rule, the obligation of performing the contract that should be exhausted, the contract of the punishment measure that does not perform the contract in time, the service resource limit corresponding to the service, and so on. In the enterprise network disk leasing scenario, the service types generally include: document storage service, audio storage service, and image storage service, in a credit service scenario, the service types generally include: credit payment service, credit service and payment service, of course, which specific service types can be further subdivided or set according to needs, and this specification does not limit. The allocation rule refers to a rule of resources that a user needs to provide when using a business service, for example, taking an enterprise network disk renting a service scenario as an example, the allocation rule may include a rule of paying back resources by the user, such as how many times the user pays back the resources, interest that needs to be paid for each time of paying back, and the like, and may further include a network disk space that the user needs to occupy when using the service, and taking a credit service scenario as an example, the allocation rule may include a rule of paying back resources by the user, such as how many times the user pays back, interest that needs to be paid for each time of paying back, and the like, and may further include resources that the user needs to pay for using the service, such as a commission fee, a service fee, and the allocation rule is often referred to as a.

The system comprises a line distribution subsystem used for receiving the business information, the service resource line and the distribution rule sent by the contract subsystem. Then, the remaining amount of the service resource amount corresponding to the service contract can be determined according to the received identifier of the service contract in the service information, then, the service resource amount sent by the received contract subsystem is compared with the remaining amount of the service resource amount, when the service resource amount is not greater than the remaining amount of the service resource amount, the remaining amount of the service resource amount is distributed and a distribution result is generated according to at least one of the service resource amount and a distribution rule sent by the received contract subsystem, and the generated distribution result is sent to the account subsystem, so that the account subsystem continues to execute the service corresponding to the first service request according to the distribution result. When the service resource limit is larger than the remaining limit of the service resource limit, determining the allocation result of allocation failure and returning to the contract subsystem and the account subsystem to enable the contract subsystem and the account subsystem to determine that the service fails, at this time, the contract subsystem can send prompt information to the user, the prompt information is used for prompting the user that the service request fails, and the account subsystem can determine to stop executing the service corresponding to the first service request.

The account subsystem in the system is used for receiving first service information sent by the contract subsystem and a distribution result sent by the quota distribution subsystem, and the account subsystem can determine a contract account corresponding to the identification of the service contract according to the identification of the service contract in the received service information sent by the contract subsystem, and then determine a target scene account from each scene account contained in the contract account according to the scene information in the service information. Wherein, the account type in the account subsystem may include: the management account, the contract account and the scene account are created in advance by the account subsystem according to each business contract, and the scene account can be determined as required after business information is received. Specifically, the context account may be determined according to context information included in the service information, and the context information may include: at least one of a type of a service contract, a type of a resource, and a type of other executing party of the first service request. Taking enterprise network disk lease service as an example, the types of the service contract may include: backup network disk service contract, synchronous network disk service contract and the like, the resource type can be a file type, such as a document file, an audio file and the like, and the types of other executing parties can comprise a partner, a team member and the like. For example, the types of business contracts include: the resource type can be currency, and the types of other executing parties can be determined according to the information of the operating field, the geographic position, whether the executing parties are linked and the like of the executing parties. Of course, what contents the scene information specifically includes may be set as required, and this specification does not limit.

In addition, in this specification, the account subsystem may further record account changes in the determined target scene account according to the received allocation result sent by the quota allocation subsystem.

Specifically, in one or more embodiments provided in this specification, an account subsystem stores a pre-created management account and a contract account, where the management account is an account for managing multiple contract accounts of the same user, and is used to uniformly manage and display information such as resources in multiple contract accounts owned by the user and leased resources of the user. The contract account is an account corresponding to the business contract and is used for uniformly managing and displaying all resources of the user under a certain business contract and the condition that the user rents the resources. The scene accounts are basic units for managing resources owned by the users and rented resources of the users by the account subsystem, the scene accounts are of various types, document scene accounts, audio scene accounts and the like can exist in enterprise network disk renting scenes, and consumption scene accounts, cash-taking scene accounts and the like can exist in credit service scenes. A user may have multiple management accounts in the same organization, and a management account may contain multiple contract accounts. In addition, contract accounts under the same management account can perform together, and business contracts corresponding to the contract accounts which can perform together can be the same in distribution rule or the same only in order-making day, which is not limited in the application. Multiple scenario accounts may be included under one contract account.

In the enterprise network disk leasing scene, an enterprise may have multiple management accounts, each management account may include multiple contract accounts, a contract account is an account provided by the enterprise for employees to use the network disk leasing service, the enterprise may divide the contract accounts of employees in different departments according to the departments, and the contract accounts included in the management accounts are configured and managed by the same management account, or may also be configured according to the working age, the position, and the like of the employees, and the description is not limited. The enterprise can efficiently determine the network disk leasing conditions of different employees through the management account, and pay back the network disk resources through the fulfillment account according to the management account.

Fig. 3 is a schematic diagram of an account structure provided in an embodiment of the present specification, and it can be seen that a certain user corresponds to a plurality of management accounts, each management account includes at least one contract account, and each contract account may include at least one scenario account.

The fulfillment subsystem in the system is configured to send, for each fulfillment account, a request for acquiring an account change record to the account subsystem when the fulfillment account satisfies fulfillment conditions, where the request carries an identifier of a management account.

And the account subsystem is also used for determining the account change records in all contract accounts contained in the management account according to the received request for acquiring the account record sent by the fulfillment subsystem after receiving the request sent by the fulfillment subsystem, and sending the determined account change records to the fulfillment subsystem.

The fulfillment subsystem is further configured to determine resource reimbursement information according to the account change record after receiving the account change record. And the performing subsystem can also send prompt information to the user according to the resource repayment information so as to prompt the user to execute the resource repayment service. The performing account is an account which is predetermined by the performing subsystem according to the service contract and corresponds to the management account.

Based on the system for performing business shown in fig. 2, the present specification proposes a system that is compatible with different types of enterprise network disk rental services. In the prior art, because the backup network disk service and the synchronous network disk service are different in the provided service content, rights and interests, repayment rules and the like, for example, for the same user in the same organization, the amount of the backup network disk service is often much higher than that of the synchronous network disk service, the required bandwidth of the backup network disk service is often much smaller than that of the synchronous network disk service, and in addition, the charging standard of the backup network disk service is also different from that of the synchronous network disk service, so a system constructed by taking the backup network disk as a product model cannot support the synchronous network disk service, but the backup network disk service and the synchronous network disk service have the same point in the service using process, for example, the service resource amount needs to be obtained based on the first service information, and when the requested service resource amount is less than the remaining amount of the service resource, the remaining amount of the service resource amount is allocated according to the service resource amount, and accounting is performed. The system for executing the business is provided based on the same point of the different types of enterprise network disk leasing services, so that the business can be executed by using the same system aiming at the different types of enterprise network disk leasing services. Furthermore, different enterprise network disk renting services provided by different departments of the same organization can be executed by using the same system at the same time, so that the operation cost of the enterprise network disk organization is reduced. Or if different parts of the same organization respectively use the system to provide credit service, the problem of system incompatibility can be avoided when departments are combined, so that the departments in the organization can be flexibly adjusted.

Based on the system for executing business shown in fig. 2, the present specification proposes a system compatible with different types of credit services, by comparing credit cards, credit credits, and mini credits, the same points and different points of different credit services are obtained, and then common points of different credit services are extracted, so as to construct the system model described above. In the prior art, the credit service is different from the credit card service in terms of service content, rights and interests, repayment rules and the like, for example, the credit limit is often much higher than the credit card for the same user in the same institution, the loan term and application threshold of the credit are also higher, and the charging standard of the credit is also different from the credit card service, so that the system built by taking the credit card as a product model cannot support the credit service, and the charging standard of the credit cannot be applied to a model with no interest in credit card stages. However, the credit loan service and the credit card service have the same point in the process of using the service, for example, it is necessary to obtain the service resource amount based on the first service information, and when the requested service resource amount is smaller than the remaining amount of the service resource amount, the remaining amount of the service resource amount is allocated according to the service resource amount and the account is taken. The system for executing the business is provided based on the same point of different types of credit services, so that the business can be executed by using the same system aiming at different credit services. Furthermore, different credit services provided by different departments of the same organization can be simultaneously executed by using the same system, so that the operation cost of the financial institution is reduced. Or if different parts of the same organization respectively use the system to provide credit service, the problem of system incompatibility can be avoided when departments are combined, so that the departments in the organization can be flexibly adjusted.

In the current credit service system constructed based on the credit card product model, because the infrastructure of the credit card product model cannot be got rid of, each subsystem in the system may need to support the realization of multiple functions, for example, the account subsystem needs to realize functions such as interest-bearing charging allocation amount, and from the software perspective, the multiple different functions cannot be split, that is, there is no decoupling between codes. Therefore, when a developer performs system maintenance or function adjustment, a large amount of codes need to be adjusted and tested, which increases the difficulty of maintenance and development. The same points of various credit services are extracted, different subsystems are constructed to realize a certain function, the system is split functionally, the workload of maintaining and developing the system is reduced, the developing and maintaining efficiency is improved, and the technical problem of the system of different credit services constructed based on a credit card product model at present is solved.

In addition, in one or more embodiments provided herein, the contract subsystem may store the content of business contracts for various users. The user is an object such as a natural person or a legal person who initiates a service through the system for executing the service. The business contract of the user is determined and stored by the contract subsystem according to a second business request initiated by the user in advance, and the following description of the process of determining the business contract according to the second business request is provided in the specification.

Based on the system shown in fig. 2, the present specification provides a flow diagram of the system for executing the service to execute the service, as shown in fig. 4.

S100: the contract subsystem may be configured to receive a first service request initiated by a user during execution of a service. The user may send the first service request to the contract subsystem through a Terminal, where the Terminal may be a mobile phone, a tablet computer, a personal computer, an automatic teller machine, a Point Of sale Terminal (POS), and the like, and this specification does not limit this. Of course, since the user may initiate the service in multiple ways at present, what way the first service request in this specification is specifically sent to the contract subsystem is not limited in this specification, as long as the contract subsystem is provided with a corresponding entry in advance, so that the user may initiate the first service request through the entry.

When receiving the first service request, the contract subsystem may determine service data required for executing the service according to the service information carried in the first service request. Specifically, for example, when the enterprise network disk rental service is executed, at least the type of the network disk service used by the user (e.g., synchronous network disk service, backup network disk, etc.), the service resource quota applied by the user, the type of the service available to the user (e.g., document storage service, picture storage service, etc.), and the allocation rule of the resource that the user needs to occupy additionally when using the service, etc. are determined. Taking the provision of credit services as an example, at least the type of credit service used by the user (e.g., credit card service, credit loan service, etc.), the amount of service resources requested by the user, the type of service available to the user (e.g., credit payment service, credit service, etc.), and the allocation rules of resources that the user needs to occupy in using the service. Of course, the service data required by different services may not be completely the same, and the specification does not limit which service data may be specifically included, and may be set as required.

S101: further, in the process that the contract subsystem determines the service data required by the execution of the service according to the service information carried in the first service request, the contract subsystem can determine the service resource limit according to the first service information, also can determine the service contract of the user from the pre-stored service contracts according to the first service information, then determine the type and the distribution rule of the service available to the user according to the determined service contract, and when the type of the service available to the user includes the service type requested by the first service request, send the service resource limit corresponding to the first service request, the first service information and the distribution rule to the limit distribution subsystem, and send the first service information to the account subsystem. When the type of the service available to the user does not include the service type requested by the first service request, the contract subsystem is further configured to determine a prompt message and return the prompt message to the user, so as to prompt the user that the service corresponding to the first service request cannot be executed.

In one or more embodiments provided in this specification, the quota allocation subsystem stores a user resource quota corresponding to each user, a service resource quota corresponding to each service contract, and a scene resource quota. The scene resource limit corresponding to each service contract may be determined according to the content of the service contract, that is, the content of the service contract may further include: and (4) a scene resource limit.

In addition, in this specification, the resource limit of the user is the maximum resource amount that can be used by the user, and is obtained by the institution by evaluating the credit ability and performance ability of the user, where the credit ability may be an individual credit for the user, or may be a credit score of the user at the institution, the credit score is related to the overdue level of the user at the institution, and the performance ability may be obtained from the resource owned by the user, or may be obtained from the resource amount available to the user every month, and this application is not limited thereto. The service resource limit is the maximum resource amount that can be used by the user when using the service, and is defined by the contract when generating the contract, and the scene resource limit is the scene resource limit corresponding to each scene included in the service contract. In addition, for different users, service contracts corresponding to the same type of service are not completely the same, and similarly, scene quota and the like are not necessarily the same.

S102: in the process of executing the service, the quota allocation subsystem can be used for receiving the first service information, the service resource quota and the allocation rule sent by the contract subsystem. When receiving the first service information, the service resource limit and the allocation rule sent by the contract subsystem, the limit allocation subsystem can determine the service resource limit corresponding to the service according to the first service information, then determine the corresponding scene resource limit according to the scene information contained in the service information, and further determine the remaining limit of the scene resource limit.

Specifically, when the service resource limit is not greater than the remaining limit of the scene resource limit, the contract subsystem allocates the remaining limit of the scene resource limit according to the service resource limit requested by the user, and generates a successful allocation result.

In addition, in this specification, the quota allocation subsystem may also allocate the remaining quota of the scene resource quota according to an allocation rule, and generate an allocation result. The allocation rule refers to a rule of resources that a user needs to provide when using a business service, for example, taking an enterprise network disk renting service scene as an example, the allocation rule may include a rule of a user paying a network disk space, such as how many times the user pays and an interest that needs to be paid each time the user pays, may also include resources that the user needs to pay when using the service, such as a commission fee, a service fee, and the like, taking a credit service scene as an example, the allocation rule may include a rule of a user paying resources, such as how many times the user pays and an interest that needs to be paid each time the user pays, and may also include resources that the user needs to pay when using the service, such as a commission fee, a service fee, and the like. The allocation rules may include a variety of allocation rules, such as for example, for commission fees, interest, etc. After determining that the allocation of the service resource quota is successful, the quota allocation subsystem can determine the remaining quota of the scene resource quota to allocate according to at least one allocation rule, and generate an allocation result of successful allocation.

Further, the allocation rule may include a first allocation rule and a second allocation rule, for example, in the case of a credit service, the first allocation rule may include a charging rule, the quota allocation subsystem may allocate the scene resource quota after the allocation of the service resource quota according to the first allocation rule, the second allocation rule may include an interest-bearing rule, and when an interest bearing condition (e.g., an interest bearing day is reached or a user interest bearing request is received), the quota allocation subsystem allocates the remaining quota according to the second allocation rule.

When the service resource limit is larger than the remaining limit of the scene resource limit, the limit distribution subsystem can determine the distribution result of the distribution failure.

After the quota allocation subsystem determines the allocation result, the determined allocation result can be sent to the account subsystem.

Of course, if the allocation result is that the allocation fails, the quota allocation subsystem may determine not to execute the service, and therefore, the allocation result of the allocation failure may also be returned to the contract subsystem, so that the contract subsystem may determine that the service fails. The contract subsystem may send a prompt to the user, where the prompt is used to prompt the user that the service request fails, and the account subsystem may determine to stop executing the service corresponding to the first service request.

Specifically, for example, when the enterprise network disk leasing service is provided, the quota allocation subsystem may determine the type of the enterprise network disk leasing service used by the user according to the received first service information, for example: synchronous network disk service and backup network disk service. Further, a scene resource limit and a remaining limit of the scene resource limit may be determined in the determined enterprise network disk leasing service type used by the user according to the scene information, for example: and comparing the service resource limit requested by the user with the remaining limit of the scene resource limit. When the service resource limit is not larger than the remaining limit of the scene resource limit, the contract subsystem distributes the remaining limit of the scene resource limit according to the service resource limit requested by the user and generates a distribution result. For example, the credit line allocation subsystem may determine the credit service type used by the user according to the received first service information, for example: credit card service, mini-loan service. Further, a scene resource limit and a remaining limit of the scene resource limit may be determined in the determined credit service type used by the user according to the scene information, for example: the credit card is compared with the service resource limit requested by the user and the surplus limit of the scene resource limit. When the service resource limit is not larger than the remaining limit of the scene resource limit, the contract subsystem distributes the remaining limit of the scene resource limit according to the service resource limit requested by the user and generates a distribution result. And the quota allocation subsystem allocates the remaining quota of the scene resource quota according to at least one allocation rule and generates an allocation result. The allocation rule may be related to the service resource amount or unrelated to the service resource amount. For example, according to a preset proportion, determining the resource limit allocated when the remaining limit of the scene resource limit is allocated according to the allocation rule according to the service resource limit. If the preset proportion is 5% and the service resource quota is 100, the resource quota which needs to be deducted from the remaining quota of the scene resource quota according to the allocation rule is 5. Or, when the remaining amount of the scene resource amount is allocated according to the allocation rule according to the preset resource amount, if the preset resource amount is 10, the resource amount deducted from the remaining amount of the scene resource amount is 10 no matter how many the service resource amount is.

S103: and after the distribution result is generated, the quota distribution subsystem also sends the distribution result to an account subsystem for account change and recording.

S104: the account subsystem can receive the distribution result sent by the limit distribution subsystem, and when the distribution result is successful, the account subsystem can determine a target scene account and record account change in the target scene account according to the distribution result and the service information sent by the contract subsystem. When the allocation fails, the account subsystem may determine to stop executing the service corresponding to the first service request.

In the process of executing the service, the account subsystem can be used for receiving the first service information sent by the contract subsystem and the distribution result sent by the quota distribution subsystem. When receiving the first service information sent by the contract subsystem and the allocation result sent by the limit allocation subsystem, the account subsystem can determine a contract account under a management account corresponding to the user according to the received service contract identifier on the service information sent by the contract subsystem, determine a target scene account under the contract account according to the scene information carried by the first service information, and record account change in the determined target scene account according to the allocation result sent by the limit allocation subsystem. In addition, the account change may be recorded only in the target scene account, or may be recorded in both the contract account and the target scene account, which is not limited in the present application.

The fulfillment subsystem is configured to, for each fulfillment account, obtain, from the account subsystem, a contract account and account change of the scene account under the management account corresponding to the fulfillment account when the fulfillment account meets fulfillment conditions, determine resource reimbursement information according to the account change, and send, to the user, prompt information according to the resource reimbursement information, where the prompt information is used to prompt the user to execute a resource reimbursement service.

And the performing account is an account which is determined by the performing subsystem according to the service contract and corresponds to the management account. The management account is an account subsystem and is a corresponding management account determined according to the service contract.

In this embodiment of the application, when the fulfillment subsystem receives a fulfillment request initiated by a user, a fulfillment account corresponding to an identifier of a management account may be determined according to the identifier of the management account carried in the fulfillment request, and it is determined that the fulfillment account satisfies fulfillment conditions. That is, the fulfillment subsystem may determine, based on the received fulfillment request, a fulfillment account that satisfies fulfillment conditions.

Alternatively, since the service contract of the general user includes a performance condition, such as an order-closing date and the like, the performance date identifies the time when the service contract performs, and the performance account is the account corresponding to the management account determined by the performance subsystem according to the service contract, the performance condition (such as the order-closing date) of the service contract corresponding to each performance account may also be stored in the performance subsystem. Then, the performing subsystem may further determine, for each performing account, whether the performing account satisfies the performing conditions according to the performing conditions of the stored service contract. Of course, the above process is only described by taking the fulfillment condition as an example on the conclusion date, and the fulfillment condition included in the service contract may be set according to needs, for example, after the resource amount used by the user reaches a certain value, the number of times of using the service by the user reaches a certain number, and the like, which is not limited in the present application.

In addition, since the performing account may correspond to a plurality of contract accounts, and account changes of the contract account and the scenario account under the management account corresponding to the performing account need to be acquired by the account subsystem according to the performing conditions, the contract accounts corresponding to each performing account need to be able to perform together, that is, there is no conflict between the performing conditions agreed in the service contracts of the contract accounts corresponding to the same performing account.

S105: the fulfillment subsystem is configured to send, for each fulfillment account, a request for obtaining an account change record to the account subsystem when the fulfillment account satisfies fulfillment conditions, where the request carries an identifier of a management account.

S106: and the account subsystem is also used for determining the account change records in all contract accounts contained in the management account according to the received request for acquiring the account record sent by the fulfillment subsystem after receiving the request sent by the fulfillment subsystem, and sending the determined account change records to the fulfillment subsystem.

S107: the fulfillment subsystem is further configured to generate a fulfillment form according to the account change record after receiving the account change record, determine resource reimbursement information according to the fulfillment form, and update an overdue level according to the fulfillment form.

S108: and the fulfillment subsystem can also send prompt information to the user according to the resource repayment information to prompt the user to execute the resource repayment service, wherein the overdue level is negatively related to the credit capability of the user, namely the higher the overdue level is, the lower the credit capability of the user is.

Further, for each performance period, if there are still unreleased resources in the performance period, the performance subsystem determines the performance order corresponding to the performance period, and determines the resource reimbursement information according to the determined performance order corresponding to each performance period.

In addition, in one or more embodiments provided herein, the contract subsystem is further configured to receive a second service request before receiving the first service request, where the second service request is a user-initiated request to create a service contract. Moreover, the second service request may carry service information, and the service information carried in the second service request is used to determine the content of the service contract, so that the service information is not exactly the same as the service information carried in the first service request. Wherein, the service information carried in the second service request at least includes: the method includes that identity information and subscription information of a user are used for determining specific content of a service contract requested by the user, and the subscription information may include, for example, an enterprise network disk leasing scene and a credit service: business resource limits, billing days, allocation rules, etc.

After receiving a second service request initiated by the user, the contract subsystem determines and records user identity information from service information carried by the second service request, creates a service contract according to subscription information in the second service request, and stores the user identity information and the service contract in a correlation manner.

After creating the business contract, the contract subsystem may also send the business contract to the account subsystem, the fulfillment subsystem, and the line allocation subsystem.

In addition, the contract subsystem can also determine the user resource limit corresponding to the user according to the user identity information, determine the service resource limit corresponding to the service and the scene resource limit corresponding to each scene contained in the service according to the content of the service contract, and send the determined user resource limit information, the service resource limit information and the scene resource limit information to the limit distribution subsystem. Taking the example of providing the enterprise network disk leasing service, the user sends a second service request to the contract subsystem, the contract subsystem creates a service contract according to second service information carried in the second service request, establishes an association relationship between user identity information and the service contract, and sends the service contract to the account subsystem, the performing subsystem and the limit distribution subsystem. And the contract subsystem can determine the total network disk space information corresponding to the enterprise according to the enterprise information, determine the total network disk space information corresponding to the individual and the network disk space information corresponding to each service which can be included when the individual uses according to the business contract, and send the determined total network disk space information corresponding to the enterprise, the total network disk space information corresponding to the individual and the network disk space information corresponding to each service which can be included when the individual uses to the limit distribution subsystem. Taking the provision of credit service as an example, the user sends a second service request to the contract subsystem, the contract subsystem creates a service contract according to second service information carried in the second service request, establishes an association relationship between the user identity information and the service contract, and sends the service contract to the account subsystem, the performing subsystem and the quota allocation subsystem. And the contract subsystem can determine the user resource limit corresponding to the user according to the personal information, determine the service resource limit corresponding to the credit service and the scene resource limit corresponding to each scene under the service contract according to the service contract, and send the determined user resource limit, the service resource limit and the scene resource limit to the limit distribution subsystem.

After receiving the service contract sent by the contract subsystem, the account subsystem can create a contract account corresponding to the service contract according to the service contract sent by the contract subsystem, determine a management account to which the contract account belongs, and send the management account information to the performing subsystem. Wherein, the management account at least should include the contract account corresponding to the service contract.

Taking the example of providing enterprise network disk leasing service, different departments can correspond to different management accounts, and members of the departments correspond to contract accounts. For example, a user may have multiple administrative accounts with different credit services corresponding to contract accounts.

The fulfillment subsystem may be configured to receive a service contract sent by the contract subsystem and management account information sent by the account subsystem, determine a fulfillment account corresponding to the service contract according to the service contract sent by the contract subsystem, determine a management account corresponding to the service contract according to the management account information sent by the account subsystem, and establish an association relationship between the fulfillment account and the management account.

The line distribution subsystem can be used for receiving the service information, the user resource line information, the service resource line information and the scene resource line information sent by the contract subsystem, after receiving the service information, the user resource line information, the service resource line information and the scene resource line information, the line distribution subsystem can determine a user resource line corresponding to a service contract according to the service information, the user resource line information, the service resource line information and the scene resource line information, and the service resource line corresponding to the service contract and the scene resource line corresponding to each scene included in the service contract.

Further, after the business contract is created, the contract subsystem is further configured to determine a product credential from the business contract and associate the product credential with the user identity information, the business contract, the management account, and the fulfillment account. The product certificate is a medium for identifying the user by the mechanism when the user uses the service, and may be a medium of a real entity, a virtual account, or the like, which is not limited in the present application.

In addition, the identity of the business contract can also be determined by the product voucher.

Based on the system for executing the service shown in fig. 2, the present specification further provides a flow diagram for executing the service, as shown in fig. 5.

Fig. 5 is a method for executing a service according to an embodiment of the present application, which specifically includes the following steps:

s200: receiving a first service request initiated by a user, and determining a service resource limit and an allocation rule according to service information carried in the first service request, wherein the service information at least comprises scene information, an identifier of a service contract and the service resource limit requested by the user.

S202: determining the service resource limit according to the service information, and when the service resource limit is not larger than the remaining limit of the service resource limit, allocating the remaining limit according to at least one of the service resource limit and the allocation rule, and determining the allocation result.

S204: and according to the service information, determining a target scene account from all scene accounts contained in a contract account corresponding to the identifier of the service contract, and recording account change in the determined target scene account according to the distribution result.

S206: for each performing account, when the performing account meets performing conditions, acquiring a contract account and account variation of a scene account under a management account corresponding to the performing account, determining resource repayment information according to the account variation, and sending prompt information to the user according to the resource repayment information, wherein the prompt information is used for prompting the user to execute resource repayment business, the performing account is an account corresponding to the management account determined according to the business contract, and the management account is a corresponding management account determined according to the business contract.

The process of executing the service may be specifically executed by the system shown in fig. 2, and different steps may be executed by subsystems in the system that are responsible for different functions, and the process of specifically executing the service may refer to the description of the process of executing the service by each subsystem in the system, which is not described again in this specification.

In the system shown in fig. 2 in this specification, before receiving the first service request, the contract subsystem may further receive a second service request, as shown in fig. 6, so that the contract subsystem, the account subsystem, the limit allocation subsystem, and the performing subsystem in the system may determine a basis for executing the service shown in fig. 5, that is, the contract subsystem determines a service contract and determines resource limit information, the account subsystem creates a contract account corresponding to the service contract and determines a management account corresponding to the service contract, the performing subsystem establishes a correspondence relationship between the management account corresponding to the service contract, and the limit allocation subsystem determines a user resource limit corresponding to the user and a service resource limit corresponding to the service contract.

Fig. 6 is a method for executing a service according to an embodiment of the present application, which specifically includes the following steps:

s300: before receiving a first service request initiated by the user, creating a service contract and determining resource limit information according to a second service request initiated by the user.

S302: and according to the service contract, creating a contract account corresponding to the service contract, and determining a management account corresponding to the service contract, wherein the management account at least comprises one contract account.

S304: and determining a performing account corresponding to the service contract according to the service contract, and establishing a corresponding relation of a management account corresponding to the service contract.

S306: and determining the user resource limit corresponding to the user and the service resource limit corresponding to the service contract according to the limit information.

The present specification further provides a computer-readable storage medium, which stores a computer program, where the computer program can be used to execute the system for executing the service provided in fig. 2.

Based on the method for executing the service shown in fig. 5, the embodiment of the present specification further provides a schematic structural diagram of the electronic device shown in fig. 7. As shown in fig. 7, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, but may also include hardware required for other services. The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs the computer program to implement the method for executing the service shown in fig. 5.

Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.

Claims

1. A system for performing a service, the system comprising: contract subsystem, account subsystem, limit distribution subsystem, the subsystem of performing contract, wherein:

the contract subsystem is used for determining a service resource limit and an allocation rule according to service information carried in a first service request when the first service request initiated by a user is received, sending the service information, the service resource limit and the allocation rule to the limit allocation subsystem, and sending the service information to the account subsystem, wherein the service information at least comprises scene information, an identifier of a service contract and the service resource limit requested by the user;

the limit distribution subsystem is used for determining a service resource limit according to the service information, distributing the remaining limit according to at least one of the service resource limit and the distribution rule when the service resource limit is not larger than the remaining limit of the service resource limit, and sending a distribution result to the account subsystem;

the account subsystem is used for determining a target scene account from all scene accounts contained in a contract account corresponding to the identification of the service contract according to the service information, and recording account change in the determined target scene account according to the distribution result;

the fulfillment subsystem is configured to, for each fulfillment account, when the fulfillment account meets fulfillment conditions, obtain, from the account subsystem, a contract account and account change of a scene account under a management account corresponding to the fulfillment account, determine resource repayment information according to the account change, and send prompt information to the user according to the resource repayment information, where the prompt information is used to prompt the user to execute a resource repayment service;

the fulfillment account is an account corresponding to the management account determined by the fulfillment subsystem according to the service contract, and the management account is the account subsystem and a corresponding management account determined by the service contract.

2. The system of claim 1, wherein the contract subsystem is further configured to create a service contract and determine resource quota information according to a received second service request initiated by the user before receiving the first service request initiated by the user, and send the service contract to the account subsystem and the performing subsystem, and send the resource quota information to the quota allocation subsystem;

the account subsystem is further configured to create a contract account corresponding to the service contract according to the received service contract, and determine a management account corresponding to the service contract, where the management account includes at least one contract account;

the fulfillment subsystem is used for determining a fulfillment account corresponding to the service contract according to the received service contract and establishing a corresponding relation of a management account corresponding to the service contract;

3. The system of claim 2, wherein the contract subsystem is further configured to determine a product voucher based on the received second service request initiated by the user, and to determine an association of the product voucher with the service contract, the management account, and the fulfillment account.

4. The system according to claim 3, wherein the contract subsystem is configured to determine a product certificate from service information carried in a first service request initiated by the user, determine an identifier of the service contract according to the product certificate, determine an allocation rule according to a service contract corresponding to the identifier of the service contract, and determine a service resource limit according to the determined service contract and a resource limit value included in the service information.

5. The system according to claim 1, wherein the account subsystem is configured to determine a contract account according to an identifier of a service contract in the service information, determine whether a scenario account corresponding to the scenario information exists in scenario accounts included in the contract account, if so, take the scenario account corresponding to the scenario information as a target scenario account, and if not, create the scenario account corresponding to the scenario information as the scenario account included in the contract account; the context account is determined by at least one of a type of a service contract, a type of a resource, and a type of other implementers of the first service request.

6. The system of claim 1, wherein the fulfillment subsystem is configured to determine a management account corresponding to a fulfillment account, and send an acquisition request carrying an identifier of the management account to an account subsystem;

the account subsystem is used for determining the management account according to the identification carried by the acquisition request, determining the record of account change of each scene account according to each scene account in each contract account contained in the management account, and returning the determined record of account change to the fulfillment subsystem;

7. The system of claim 6, wherein the fulfillment subsystem is configured to, for each fulfillment period for which unreleased resources still exist, determine a fulfillment form corresponding to the fulfillment period, and determine resource reimbursement information according to the determined fulfillment form corresponding to each fulfillment period.

8. The system for performing transactions according to claim 1, wherein said allocation rules include a first allocation rule and a second allocation rule;

the quota allocation subsystem is used for continuously allocating the remaining quota after the service resource quota allocation according to the first allocation rule; sending the distribution result to the account subsystem;

9. A method of performing a service, comprising:

receiving a first service request initiated by a user, and determining a service resource line and an allocation rule according to service information carried in the first service request, wherein the service information at least comprises scene information, an identifier of a service contract and the service resource line requested by the user;

determining a service resource limit according to the service information, and when the service resource limit is not larger than the remaining limit of the service resource limit, allocating the remaining limit according to at least one of the service resource limit and the allocation rule, and determining an allocation result;

according to the service information, determining a target scene account from all scene accounts contained in a contract account corresponding to the identifier of the service contract, and recording account change in the determined target scene account according to the distribution result;

10. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when being executed by a processor, carries out the method of claim 9.