CN114155089A

CN114155089A - Bill management method, device and equipment

Info

Publication number: CN114155089A
Application number: CN202111503551.6A
Authority: CN
Inventors: 张忠友
Original assignee: Shanghai Pinshun Information Technology Co ltd
Current assignee: Shanghai Pinshun Information Technology Co ltd
Priority date: 2021-12-09
Filing date: 2021-12-09
Publication date: 2022-03-08

Abstract

The application discloses a bill management method, device and equipment. After determining each entity related to the bill field, setting bill services corresponding to each bill based on each entity; so that different billing services can be set for different bill types of respective banks, financial companies, and billing rules of respective bills. A user interface layer for providing interface service to the outside can be set based on the set bill service and the external business system; so that various banks and financial companies can access different billing services through different service interfaces according to different business systems. The problem that financial data calculation is complex and errors are prone to occur due to different services of various banks and financial companies is effectively solved. In addition, a data access layer can be arranged on the basis of the bill service and the externally configured database so as to be connected with the externally configured database to realize the functions of acquiring data and persisting data, and the management efficiency of the bill data is effectively improved.

Description

Bill management method, device and equipment

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method, an apparatus, and a device for managing bills.

Background

With the rapid development of the mobile internet and the popularization of smart phones, the living needs of users are also changing. As the life habits of users are slowly changed from physical store consumption to online shopping, the payment means of the users are also changed from traditional cash payment to convenient mobile payment. The mobile payment is a novel payment system formed by effectively combining the internet, terminal equipment and a financial institution, wherein the mobile client uses electronic products such as a mobile phone to carry out electronic money payment. The mobile payment in the internet era breaks the limit of the traditional payment to time and space, so that the user can carry out payment activities anytime and anywhere. The traditional payment is mainly cash payment, and needs face-to-face payment between a user and a merchant, so that the payment time and place are greatly limited; the mobile payment is mainly based on mobile phone payment, and a user can use a mobile phone to carry out payment activities at any time and any place without the limitation of time and space. In addition, various mobile payment means such as a face brush and a fingerprint brush are available.

Mobile payment has facilitated the cooperation of many consumer platforms with banks and financial companies while providing payment convenience to users. To better provide a convenient mobile payment experience for the user. Each large consumption platform often performs combined service with multiple banks and financial companies to jointly manage various bill data generated by consumption behaviors of users. The business of each bank and financial company is different, the bill types and the bill charging rules of each bank and financial company are different, the repayment mode is flexible, and the fund allocation mode is diversified. This makes it cumbersome and difficult to manage the individual billing data generated by the consumer's consumption behavior.

In order to ensure the normal operation between the consumption platform and each bank and financial company, a method for efficiently managing user accounts and bill data of various channels is urgently needed; the method is used for solving the problem that the efficiency of jointly managing user accounts and bill data of various channels by using each consumption platform, each bank and each financial company is low.

Disclosure of Invention

In view of the above, the present application provides a bill management method, apparatus, and device, which are used to solve the problem that the efficiency of jointly managing user accounts and bill data of various channels by each consumption platform and each bank and financial company is low.

A method of bill management, comprising:

determining various entities involved in the billing field;

setting bill services corresponding to various bills based on various entities related to the bill field;

setting a user interface layer for providing an interface service to the outside based on the billing service and an external business system;

a data access layer is provided based on the billing service and the externally configured database for use in connecting the externally configured database to obtain data and persistent data.

Preferably, each entity involved in the billing field includes:

the interest fee penalty, the basic bill, the charging bill, the equal-amount principal bill, the synchronous bill for the fund elimination, the stage bill and the coupon.

Preferably, the billing service includes:

the billing service, the bill service after payment, the bill service after repayment and the bill service after payment again.

Preferably, the user interface layer includes:

HTTP service interface, OSP service interface.

Preferably, the setting up a data access layer based on the billing service and the externally configured database includes:

determining the type of the externally configured database;

setting an interface of a data access layer based on the type of billing service and the database type.

Preferably, the data access layer includes:

mysql database interface, Oracle database interface, Redis database interface.

Preferably, the method further comprises:

after the instruction of the bill service which the user requests to access is obtained, calling an interface corresponding to the bill service which the user requests to access to provide the corresponding bill service for the user;

and calling an interface of a data access layer according to the type of the data generated by providing the bill service for the user, and persisting the data generated by providing the bill service for the user to a database corresponding to the type of the data generated by providing the bill service for the user.

Preferably, before the setting of the user interface layer for providing the interface service to the outside based on the billing service and the external business system, the method further includes:

and setting bill service corresponding to the business requirement of the user according to the business requirement of the user.

A bill management apparatus comprising:

the entity determining unit is used for determining each entity related to the bill field;

the bill service setting unit is used for setting bill services corresponding to various bills based on various entities related to the bill field;

a user interface layer setting unit for setting a user interface layer for providing an interface service to the outside based on the billing service and an external service system;

and the data access layer setting unit is used for setting a data access layer based on the billing service and the externally configured database so as to be used for connecting the externally configured database to acquire data and persistent data.

A bill management device comprising a memory and a processor;

the memory is used for storing programs;

the processor is configured to execute the program to implement the steps of the bill management method as described above.

A readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the bill management method as introduced above.

According to the technical scheme, the bill management method can set bill services corresponding to various bills based on various entities related to the bill field after the entities related to the bill field are confirmed; so that different billing services can be set for different bill types of respective banks, financial companies, and billing rules of respective bills. After the billing service corresponding to each bill is set, a user interface layer for providing an interface service to the outside may be set based on the billing service and an external business system; so that various banks and financial companies can access different billing services through different service interfaces according to different business systems. The problem that data management is complex due to different services of various banks and financial companies is effectively solved. In addition, a data access layer can be arranged on the basis of the bill service and an externally configured database, so that the data access layer can be connected with the externally configured database to realize the functions of acquiring data and persisting data. The bill service system and the database are managed independently, and the data access layer is arranged for interaction between the bill service system and the database, so that the management of bill data is effectively improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

Fig. 1 is a flowchart of a method for implementing bill management according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a bill management device according to an example of the present application;

fig. 3 is a block diagram of a hardware structure of a bill management device according to an embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

With the rapid development of mobile internet and the popularization of smart phones, more and more users are used to mobile payment. The mobile payment may generate various types of billing data, such as a basic billing bill generated by the consumption behavior of the user, billing data generated by the consumption of the virtual asset by the user using a coupon, and the like. In addition, in order to stimulate the consumption of users and promote the economic development, the mobile payment also promotes a business of early consumption. And each consumption platform combines each bank and financial company to provide loan service for the common user, and better provides service for the consumption behavior of the user. Thus, the mobile payment also generates loan-type and payment-type billing data. As each consumption platform, bank and finance company has own loan business rules. The different loan-type bills that are generated are also varied. The diversification of the business also brings huge challenges to bill management of various consumption platforms, banks and financial companies.

Therefore, there is a need for a bill management method for solving the problem of better and collective management of various business bill data by each consuming platform, bank or financial company.

In order to solve the problem, the application provides a bill management method which can be used for solving the problem that the efficiency of managing user accounts and bill data of various channels by combining each consumption platform with each bank and each financial company is low.

The method can be applied to any equipment capable of realizing bill management, and optionally, the equipment capable of realizing bill management can be a terminal with data processing capability, such as a tablet personal computer, a mobile phone, a digital television and the like.

The following describes a flow of a bill management method according to an embodiment of the present application with reference to fig. 1, where the flow may include the following steps:

step S101, determining each entity related to the billing field.

In particular, billing rules generated by different banks and financial companies for different consumption behaviors of different consumers are different. Different consumer behaviors of different consumers on different consumption platforms can generate bills in different fields. Therefore, in order to better manage bills in different bill areas, various entities involved in different bill areas can be determined based on consumption behaviors of different consumers so as to be used for setting different bill services for different consumption behaviors of different consumers. Wherein, each entity related to each bill field has a unique ID and can be persisted; each entity may be determined from the real billing business object.

For example, according to the commonly used financial services, it can be confirmed that the entity related to the billing field related to the commonly used financial services can be set as a plurality of entities such as local interest penalty, basic bill, charging bill, equal-amount principal bill, synchronous consumption bill, installment bill, coupon, and the like.

Wherein the meaning of each entity is set as follows:

1. this benefit penalizes the stagnation: the operations for principal and interest fee penalty are based on the loan request of the finance company, the consumption platform and the bank, the bill generated by the user based on the repayment behavior generated by the loan, and the principal and interest fee penalty.

2. Basic billing: may be provided as an abstract class, may be a data structure and associated abstract behavior used to define the bill generated by the user.

3. Billing: the method can be set into an abstract class, can inherit the attribute of the basic bill, faces bills of different charging types of consumption platforms, banks and financial companies, and adopts a template method to design different charging bills.

4. Equal amount of the bill: the attribute of the charging bill can be inherited, and the bill service in the equal-amount principal charging mode is provided.

5. Waiting for the amount of the original bill: the attribute of the charging bill can be inherited, and the bill service in the equal-amount and intrinsic-information charging mode is provided.

6. And (4) synchronous bill for eliminating money: the method can inherit the attribute of the basic bill, and reserve an expansion interface in an SPI interface mode for synchronous bill service based on a consumption platform and a financial company so as to adapt to bill logics of different cash companies. The SPI is a set of Interface provided by Java for realizing by third party or expanding Service, which can make caller use to start frame expansion and replacing component according to actual use requirement to achieve the aim of local Service realization.

7. And (4) staging billing: the stage-oriented billing entity is the minimum granularity of the bill, and can combine the benefit penalty entity and the basic billing entity to complete the related billing service.

8. And (4) coupon: may be the finest level structure of the bill for each channel, relating to the age of the bill, may be used to calculate the channel bill.

And S102, setting bill services corresponding to various bills based on various entities related to the bill field.

Specifically, different bills are determined based on different entities and corresponding charging rules, and thus, after respective entities related to a bill field are confirmed, bill services corresponding to the various bills can be set based on the respective entities related to the bill field, so that different service interfaces can be set according to the different bill services.

For example, based on the determined entities involved in the billing field, the billing service corresponding to each bill may be set as: the billing service, the bill service after payment, the bill service after repayment and the bill service after payment again.

Wherein, each billing service can be set as follows:

charging service: can be responsible for the billing logic of bills, and the billing service can have the function of high extension to adapt to the billing rules of different banks, consumption platforms and financial companies.

Bill service after deposit: the method can serve the paying link in the transaction process and can be responsible for bill generation processing, the paid bill service can play a role of a coordinator, and related bill service requests can be packaged to directly operate bill core field objects to complete the paid bill service.

Bill service after repayment: the method can serve the repayment link in the transaction flow, can be responsible for processing bill payment account, can play a role of a coordinator like the bill service after payment, and can also encapsulate a related bill service request to directly operate a bill core field object to complete the bill service after payment.

Bill service after reimbursement: the method can serve the reimbursement link in the transaction process, can be responsible for the original bill cancellation processing and the new bill generation processing, can play a role of a coordinator like the bill service after reimbursement and the bill service after repayment, and can encapsulate a related bill service request to directly operate a bill core field object to complete the bill service after reimbursement.

And step S103, setting a user interface layer for providing interface service to the outside based on the bill service and the external business system.

In particular, different billing services correspond to different businesses. Accordingly, after the billing service corresponding to each bill is set based on each entity related to the billing field, a user interface layer for providing an interface service to the outside can be set based on the billing service and an external business system. So that different banks, financial companies and consumption platforms request to access different billing services according to their respective business requirements.

For example, according to the common service attributes, an HTTP service interface and an OSP service interface may be set at the user interface layer for different services, so as to provide interface services to the outside. The osp (open Service platform) is an open Service platform, is a set of distributed Service framework, and mainly aims to provide a core remote invocation mechanism and a basic Service management function for Service.

And step S104, setting a data access layer based on the billing service and the externally configured database so as to be used for connecting the externally configured database to acquire data and persistent data.

Specifically, after various billing services are set, a user interface layer for providing an interface service to the outside may be set based on the billing services and an external business system. A data access layer can also be arranged on the basis of the bill service and an externally configured database, so that the data access layer can be used for connecting the externally configured database to acquire data and persistent data to better provide better service for different businesses.

According to the technical scheme, the bill management method can set different bill services for different bill types of banks and financial companies and the charging rules of bills. Setting a user interface layer for providing an interface service to the outside based on the billing service and an external business system; the system can be used for various banks and financial companies to access different billing services through different service interfaces according to different business systems. The problem that data management is complex due to different services of various banks and financial companies is effectively solved. In addition, a data access layer can be arranged on the basis of the bill service and an externally configured database, so that the data access layer can be connected with the externally configured database to realize the functions of acquiring data and persisting data. The bill service system and the database are managed independently, and the data access layer is arranged for interaction between the bill service system and the database, so that the management of bill data is effectively improved.

In the embodiment of the present application, a process of setting a data access layer based on the billing service and the external database in the step S104 is described. The process may include the following steps:

in step S1, the type of externally configured database is determined.

Specifically, generally, for the security and stability of data, a user manages a database separate setting server, and different users may use different types of databases. Therefore, before setting up the data access layer, the type of data configured outside the system may be determined, so as to set up different access interfaces according to different database types.

For example, the externally configured data type may be a Mysql database, a Redis database, a mock database, a test database, or a production database.

And step S2, setting an interface of a data access layer based on the type of the billing service and the type of the database.

Specifically, after determining the type of a database configured outside the system, an interface of a data access layer may be set based on the type of the billing service and the database type. For use in connecting externally deployed databases to obtain data and persistent data.

For example, the interface of the data access layer can be set to be a Mysql database interface, an Oracle database interface, and a Redis database interface according to the database type.

According to the technical scheme, the external database can be applied, and the data access layer is arranged to connect the external database to acquire the data and the persistent data, so that the decoupling of the application and the external database is realized, the safety and the stability of the data are improved, and the efficiency of data management is also improved.

After the bill management system is set according to the technical scheme introduced in the above embodiment, the embodiment of the application may further provide corresponding bill service according to the access request of the user, so as to complete bill management.

The process of providing the corresponding billing service according to the access request of the user may include the following steps:

step S1, after obtaining the instruction of the billing service requested to be accessed by the user, calling the interface corresponding to the billing service requested to be accessed by the user to provide the corresponding billing service for the user.

And step S2, calling an interface of a data access layer according to the type of the data generated by the bill service provided for the user, and making the data generated by the bill service provided for the user persistent to a database corresponding to the type of the data generated by the bill service provided for the user.

According to the technical scheme, after the instruction of the bill service which the user requests to access is obtained, the corresponding service interface can be called according to the bill service, so that the corresponding bill service is provided for the user. In addition, the type of the data generated by providing the bill service for the user can be called, an interface of a data access layer is called, and the data generated by providing the bill service for the user is persisted to a database corresponding to the type of the data generated by providing the bill service for the user.

In consideration of the diversity of business in the practical application process, some billing services related to business requirements of users need to be set so as to better provide the billing services for the users. Therefore, in addition to the above, in step S103, before setting the user interface layer for providing the interface service to the outside based on the billing service and the external business system, a process of setting the billing service corresponding to the business requirement of the user according to the business requirement of the user may be added. So that users with different business requirements can be provided with corresponding billing services. The experience of the user is improved.

Next, several common bill calculation methods will be described in detail.

The first method comprises the following steps: calculation method for equal-amount principal deposit paying

1. Inputting data: the core information such as the principal of loan fund, the term, the borrowing time, the (fixed) repayment date and the like, and other information such as the borrowing serial number (internal and external), the billing product code, the billing version and the like are input.

2. Outputting data: and outputting the details of the bill per period according to the period, the period number, the bill starting date, the bill ending date (the last repayment date), the balance fund of the period, the interest of the period, the balance fee of the period and other information such as the internal debit note number (application number), the channel debit note number (channel return, corresponding to the internal debit note number), the current version number of the charging rule and the like.

3. The calculation method of the equal-amount principal deposit paying can comprise the following steps:

1) calculating the mode of each period principal of the staged payment: dividing the total principal by the period number, and reserving two decimal points for the result;

2) the interest to be paid for each period is equal to the total principal remaining in the bill from the beginning of the period multiplied by the daily interest rate and multiplied by (end date of the bill-start date of the bill).

Second, equal-amount principal repayment calculation method

1. Inputting data: entering billing data for each period, remaining principal, remaining outstanding interest equal to cumulative confirmed interest minus paid (difference indicates confirmed remaining interest), remaining penalty, remaining commission, remaining user commission, billing start date, billing end date (last payment date), last time the bill was paid (date), period.

2. Determining the payment details of the customer: including determining the time of payment, principal, interest, penalty, commission, reduced or exempt commission, and whether or not to make future purchases. And other information such as repayment serial number (internal, external), payment serial number (internal, external), billing product code, billing version, etc.

3. Outputting data:

outputting the change value of the bill according to the time: the number of the current period, the amount of money returned by the current period, the interest returned by the current period, the newly confirmed interest returned by the current period, and the planned interest in the future of the current period.

Besides, some basic conventions can be set according to business requirements, for example, the following conventions can be set:

1) repayment needs to be guaranteed: the principal returns the principal and interest (commission) returns interest;

2) the amount of each repayment is distributed, and a first period, a second period, a.

3) The special case is combined payment, and the payment in each period needs to be distributed according to the priority of channels.

In addition, the output of repayment includes real repayment principal, real repayment interest and new repayment interest information of each period. In particular, the gold should remain unchanged.

Third, equal-amount principal repayment calculation method

For each independent calculation, the variables are defined as follows:

current repayment time: tx;

repayment principal for the user: CU;

paying interest by the user: LU;

the remaining principal of the current period before repayment: CB;

the remaining principal of the current period after payment: CA;

remaining not interest (confirmed remaining not interest): LB, cumulative confirmed interest for the period-interest for the period has been paid;

date of start of this session: t1;

date of the end of this period: t2;

date of the last repayment of the period: t3(T3 ≦ Tx must be satisfied);

the remaining principal from the beginning of the session (i.e., the principal before the session is removed) before repayment: c1;

the remaining principal from the beginning of the session (i.e., the principal before the session is removed) after the payment: c2;

the daily interest rate: DR;

repayment fund for the time: CR (output);

repayment interest for the time in the period: LR (output);

newly confirmed interest on this repayment at this stage: add (output);

planned interest in this phase next future: plan (export);

based on the above defined variables, the equal-amount principal payment calculation method may include the steps of:

(1) the CR/CA of each phase is calculated by the following algorithm:

CR algorithm:

1) inputting a CU, and creating a temporary variable CX which is equal to the CU;

2) iterating each period of bill, sequentially subtracting CB, if CX-CB is greater than 0, then CR is CB, CX is CX-CB, CA is 0, and iterating continuously; otherwise CR ═ CX, CA ═ CB-CX, CX ═ 0, and the iteration ends.

(2) Based on the CB obtained in (1), C1 was estimated based on the CB, C2 was estimated based on CA (available as a first step), and Add and Plan for each phase were calculated as follows:

note: C1/C2 requires iteration of all relevant staged CB/CA calculations, Add depends on C1, Plan depends on C2.

1) If Tx < T1, indicating a future phase ahead, Add is 0, Plan is DR (T2-T1) C2;

2) if T1 < Tx < T2, it indicates advance payment or due payment after entering the period (if Tx T2, it is special case);

judging whether T3 exists or not, if T3 exists, and T3 is less than T1, Add is DR (Tx-T1) C1, Plan is DR (T2-Tx) C2; t1 ≦ T3(T3 only ≦ T2, not ≦ T2), Add ≦ DR (Tx-T3) × C1, Plan ≦ DR (T2-Tx) C2; if T3 is not present, Add-DR (Tx-T1) -C1, Plan-DR (T2-Tx) C2; in a special case, if Tx — T2, Plan is 0.

3) If T2 < Tx < ═ T2+3 (grace period), the payment in the grace period is indicated;

judging whether T3 exists or not, if T3 exists and T3 < T1, adding to DR (T2-T1) C1, and Plan is 0; and T1 ≦ T3 ≦ T2, Add ≦ DR (T2-T3) × C1, Plan ≦ 0; and T3> T2, Add is 0, Plan is 0; if T3 is not present, Add is DR (T2-T1) C1, Plan is 0.

4) If Tx > T2+3, it indicates a overdue payment,

judging whether T3 exists or not, if T3 exists, T3 is less than T1, Add is DR (T2-T1) C1, Plan is 0; and T1 ≦ T3 ≦ T2, Add ≦ DR (T2-T3) × C1, Plan ≦ 0; and T2 < T3 ≦ T2+3 (grace period), Add 0, Plan 0; if T3 is not present, Add is DR (T2-T1) C1, Plan is 0.

After the calculation of the cost of all the periods is completed, a logic needs to be supplemented:

if the principal is over in a certain period, the principal is indicated to be cleared (a multi-period scene of payment in advance), the interest continuously generated at the time is recorded into the next period, if the next period is also clearing, the next period is continuously iterated to the back, and so on, and correspondingly, the interest in the period is directly cleared.

3. After the Add is obtained, the LR for each phase is calculated as follows:

LR algorithm:

1) inputting LU, and creating a temporary variable LX ═ LU;

2) iterating each period of the bill, and sequentially subtracting LB' (-LB + Add); if LX-LB ' >0, LR ═ LB ', LX ═ LX-LB ', and iteration continues; otherwise, LR equals LX, LX equals 0, and the iteration ends.

Fourth, equal cost calculation method

The equal-amount principal and interest repayment method refers to a loan repayment method, which means that the same amount of loan (including principal and interest) is repayed every month in a repayment period.

The calculation of the equal-amount original payment can comprise the following parts:

1. conversion of interest rate:

(1) monthly-rate is the annual rate divided by 12;

(2) the daily rate is the annual rate divided by 360;

2. the standard calculation formula may include several calculation methods as follows

(1) The formula for calculating the total repayment amount of the equal amount interest in each period is as follows: assuming that the total loan amount is A, the monthly rate is beta, the loan term number is k, and the total repayment amount (principal + interest) in each period is x, then:

after the first payment, the total amount owed Q1 ═ a (1+ β) -x;

after the second payment, the total amount owed, Q2 ═ Q1 ═ a ═ (1+ β) -x ] (1+ β) -x ═ a ^2- [1+ (1+ β) ] × x;

after the third payment, the total amount owed is Q3 ═ Q2 ^2- [1+ (1+ β) ]. times x } (1+ β) -x ═ A ^ 1+ β) + (1+ β) ^3- [1+ (1+ β) + (1+ β) ^2 ]. times x;

it follows that after the k-th payment, the total amount owed Qk is Qk-1 (1+ β) -x ═ a ═ 1+. k- [1+.. + (1+ β) ^ k- [1+. 2) + (1+ β) ^ k-1) ] ×;

because the loan is finished after the k-th repayment, Qk is 0, namely A (1+ beta) k- { [ (1+ beta) k-1 ]/beta }. x is 0, so that the total repayment amount x of equal amount per period is A (1+ beta) k/[ (1+ beta) k-1], which is the total amount of the repayment required per period.

(2) Formula for calculating equal-amount original interest and interest paid at each period

Wherein, interest calculation is divided into two types:

1) the interest is calculated according to the day, namely the interest is calculated according to the remaining total principal of the current period and the number of the rest days of the current period and the daily interest rate;

2) the interest is calculated according to the month, namely the interest is the monthly rate of the residual total cost;

(3) formula for calculating equal amount and interest money repayment fund in each period

With the total amount x of the repayment in each period and the interest calculation mode, the calculation of the repayment principal in each period is simpler. Taking monthly interest as an example, assuming that the nth payment principal is Pn, then:

the first stage requires gold P1 ═ x-a ═ β;

the second phase requires that the gold P2 ═ x- (a-P1) ═ β ═ x- { a- [ x-a ═ β ] } ═ x-a ═ β + (x-a ═ β) ═ P1+ P1 ═ P1 ═ P (1+ β);

the third period is that the gold P3 ═ x- (A-P1-P2) ═ β ═ x- { A-P1-P1 ═ 1+ β } ═ β ═ x-A ^ β + P1 ^ β + P1 ^ 1+ β ^ P1 ^ 1+ β ^ 2;

it can be demonstrated by mathematical induction: the nth stage needs to be the Pn ═ P1 ^ (1+ beta) ^ (n-1).

The following description starts with the bill management device provided in the embodiment of the present application, and the bill management device described below and the bill management method described above may be referred to correspondingly.

Referring to fig. 2, fig. 2 is a schematic structural diagram of a bill management device disclosed in the embodiment of the present application.

As shown in fig. 2, the account management apparatus may include:

an entity determining unit 101, configured to determine each entity related to the billing field;

a billing service setting unit 102, configured to set billing services corresponding to various bills based on various entities related to the billing field;

a user interface layer setting unit 103 for setting a user interface layer for providing an interface service to the outside based on the billing service and the external service system;

a data access layer setting unit 104, configured to set a data access layer based on the billing service and the externally configured database, so as to be used to connect the externally configured database to obtain the data and the persistent data.

The device of the embodiment of the application can set different bill services for different bill types of various banks and financial companies and charging rules of various bills. Setting a user interface layer for providing an interface service to the outside based on the billing service and an external business system; the system can be used for various banks and financial companies to access different billing services through different service interfaces according to different business systems. The problem that data management is complex due to different services of various banks and financial companies is effectively solved. In addition, a data access layer can be arranged on the basis of the bill service and an externally configured database, so that the data access layer can be connected with the externally configured database to realize the functions of acquiring data and persisting data. The bill service system and the database are managed independently, and the data access layer is arranged for interaction between the bill service system and the database, so that the management of bill data is effectively improved.

Further optionally, the bill management apparatus may further include:

the bill service interface calling unit is used for calling an interface corresponding to the bill service which the user requests to access to provide the corresponding bill service for the user after acquiring the instruction of the bill service which the user requests to access;

and the data access layer interface calling unit is used for calling the interface of the data access layer according to the type of the data generated by providing the bill service for the user, and persisting the data generated by providing the bill service for the user to a database corresponding to the type of the data generated by providing the bill service for the user.

Further optionally, the bill management apparatus may further include:

and the setting unit is used for setting bill service corresponding to the business requirement of the user according to the business requirement of the user.

The specific processing flow of each unit included in the bill management apparatus may refer to the related description of the foregoing method, and is not described herein again.

The bill management device provided by the embodiment of the application can be applied to bill management equipment, such as a terminal: mobile phones, computers, etc. Alternatively, fig. 3 shows a block diagram of a hardware structure of the bill management device, and referring to fig. 3, the hardware structure of the bill management device may include: at least one processor 1, at least one communication interface 2, at least one memory 3 and at least one communication bus 4.

In the embodiment of the present application, the number of the processor 1, the communication interface 2, the memory 3, and the communication bus 4 is at least one, and the processor 1, the communication interface 2, and the memory 3 complete mutual communication through the communication bus 4.

The processor 1 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement embodiments of the present invention, etc.;

the memory 3 may include a high-speed RAM memory, and may further include a non-volatile memory (non-volatile memory) or the like, such as at least one disk memory;

wherein the memory stores a program and the processor can call the program stored in the memory, the program for: and realizing each processing flow in the terminal bill management scheme.

Embodiments of the present application further provide a readable storage medium, where the storage medium may store a program adapted to be executed by a processor, where the program is configured to: and realizing each processing flow of the terminal in the bill management scheme.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, 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 identical elements in a process, method, article, or apparatus that comprises the element.

The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. The various embodiments may be combined with each other. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of bill management, comprising:

determining various entities involved in the billing field;

2. The bill management method according to claim 1, wherein each entity involved in the bill field comprises:

3. The bill management method according to claim 1, wherein the bill service comprises:

4. The bill management method according to claim 1, wherein the user interface layer comprises:

HTTP service interface, OSP service interface.

5. The billing management method of claim 1, wherein the setting up a data access layer based on the billing service and an externally configured database comprises:

determining the type of the externally configured database;

6. The bill management method according to claim 1, wherein the data access layer comprises:

mysql database interface, Oracle database interface, Redis database interface.

7. The bill management method according to claim 1, wherein the method further comprises:

8. The bill management method according to any one of claims 1 to 7, wherein before the setting of the user interface layer for providing the interface service to the outside based on the bill service and the external business system, the method further comprises:

9. A bill management apparatus, comprising:

10. A bill management device comprising a memory and a processor;

the memory is used for storing programs;

the processor, executing the program, performs the steps of the bill management method as claimed in any one of claims 1 to 8.