CN115439224A

CN115439224A - Interest counting method, system and equipment for large-volume deposit list

Info

Publication number: CN115439224A
Application number: CN202211122927.3A
Authority: CN
Inventors: 魏广; 邹帮山; 严彪; 李成功; 孙健淞; 刘晓林; 顾倍铭; 胡文龙; 田晓林
Original assignee: Bank Of Jilin Co ltd
Current assignee: Bank Of Jilin Co ltd
Priority date: 2022-09-15
Filing date: 2022-09-15
Publication date: 2022-12-06
Anticipated expiration: 2042-09-15
Also published as: CN115439224B

Abstract

The present disclosure relates to financial technologies, and in particular, to a method, a system, and a device for charging a large deposit receipt. The method comprises the steps that a deposit receipt subsystem receives an interest counting request of a user terminal; the deposit receipt subsystem carries out first interest processing on the due expenditure interest-collecting request to obtain a first interest result; converting the information-collecting request in advance and then sending the converted information-collecting request to a core subsystem; the core subsystem carries out second interest processing on the converted advanced interest-bearing request to obtain a second interest result, and the second interest result is fed back to the deposit receipt subsystem; and the order storing subsystem sends the first interest counting result or the second interest counting result to the user terminal according to the interest counting request of the user terminal. By utilizing the embodiment of the text, the compatibility of the new subsystem and the old subsystem is realized, the functional decoupling is realized, and the condition that the data is not uniform possibly caused by the same service calculation of the two subsystems is avoided.

Description

Interest counting method, system and equipment for large-volume deposit list

Technical Field

The present disclosure relates to financial technologies, and in particular, to a method, a system, and a device for charging a large deposit receipt.

Background

In recent years, with the acceleration of market reformation of interest rate, the independent pricing capacity of financial institutions is remarkably improved, a deposit pricing pattern with ordered layering and differentiated competition is basically formed, and meanwhile, the rapid development of the same-industry deposit receipt market lays a solid foundation for the promotion of enterprise and individual large-volume deposit receipts.

In the prior art, as the business development of the Xiaozhong bank needs a long time process, the large deposit receipt system and the core system are both separately developed, the problems of coupling of the functions of the core system and the large deposit receipt system and even data inconsistency often occur, the large deposit receipt system and the core system need to be completely upgraded and updated again to solve the problems, and the time cost and the development cost are high.

How to solve the problem that the information function of the large-volume deposit receipt system and the core system is divided again with the lowest cost in the prior art, namely, the large-volume deposit receipt system and the core system are decoupled on the premise of changing as little as possible is urgent to solve.

Disclosure of Invention

To solve the problems in the prior art, embodiments herein provide an interest-bearing method, system and device for a large-volume deposit receipt, which can adapt to a newly-added core subsystem with as few changes as possible on the basis of an original deposit receipt subsystem, and decouple the entire system.

Embodiments herein provide a method for interest-bearing on a large inventory, comprising,

the deposit receipt subsystem receives an interest counting request of a user terminal, wherein the interest counting request comprises an expired interest counting request or an advanced interest counting request of a large deposit receipt;

the deposit receipt subsystem carries out first interest processing on the due expenditure interest-bearing request to obtain a first interest result; converting the information-collecting request in advance and then sending the converted information-collecting request to a core subsystem;

the core subsystem carries out second interest bearing processing on the converted information-drawing-in-advance request to obtain a second interest bearing result, and the second interest bearing result is fed back to the deposit receipt subsystem;

and the deposit sub-system sends the first message result or the second message result to the user terminal according to the message request of the user terminal.

As an aspect of embodiments herein, the receipt of the interest bearing request by the deposit subsystem further comprises,

the deposit receipt subsystem receives an information counting request of a user terminal through a message bus;

matching the URL of the received interest request with a mapping table, and analyzing whether the interest request is an expired interest-drawing request or an advanced interest-drawing request;

if the interest collection request is due, first interest processing is carried out through a first interest unit of the deposit receipt subsystem;

if the information is taken out in advance, and the information is converted and sent to the core subsystem.

As another aspect of embodiments herein, the URL of the interest request is http:// message bus Domain name service Port/custom URL/.

As another aspect of the embodiments herein, the deposit receipt subsystem performs a first interest processing on the due withdrawal interest request, and obtaining a first interest result further comprises,

and the deposit receipt subsystem performs first interest processing on the due expenditure interest request according to the interest data of the service product corresponding to the due expenditure interest request to obtain principal and interest data corresponding to the service product.

In another aspect of the embodiments herein, translating the early fetch interest request to send to the core subsystem further comprises,

and converting the URL of the interest calculation request sent by the user terminal into http:// core network management domain name: service port/core service URL/.

and adding a deposit receipt date, a flow receipt number and a timestamp into the head of a message formed by the advance interest-bearing request.

There is also provided in an embodiment herein an interest bearing system for a large volume inventory, comprising,

the system comprises a user terminal and a server, wherein the user terminal is used for sending an interest counting request, and the interest counting request comprises an expired interest collection request or an advanced interest collection request of a large deposit list;

the deposit receipt subsystem is used for carrying out first interest processing on the due expenditure interest request to obtain a first interest result; converting the information-collecting request in advance and then sending the converted information-collecting request to a core subsystem;

the core subsystem is used for carrying out second interest processing on the converted advanced interest-bearing request to obtain a second interest-bearing result, and feeding the second interest-bearing result back to the deposit receipt subsystem;

and the deposit subsystem is also used for sending the first information result or the second information result to the user terminal according to the information counting request of the user terminal.

As an aspect of the embodiments herein, further comprising a message bus for receiving an interest bearing request of the user terminal;

the deposit receipt subsystem further comprises a matching unit, a first information unit and a conversion unit;

the matching unit is used for matching the URL of the received interest request with a mapping table and analyzing whether the interest request is an expired interest-collecting request or an advanced interest-collecting request;

the first interest unit is used for carrying out first interest processing through an interest module of the deposit sub-system;

the conversion unit is used for converting the information-collecting request in advance and then sending the converted information-collecting request to the core subsystem;

the core subsystem further comprises a second interest unit, which is used for carrying out second interest processing on the converted advance interest-drawing request to obtain a second interest result.

Embodiments herein also provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above-mentioned method when executing the computer program.

Embodiments herein also provide a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the above-described method.

By utilizing the embodiment of the invention, the account requests of the large-volume deposit receipt are divided into two types, namely an expiration charging request and an advanced charging request, the expiration charging request is subjected to the account processing in the original deposit receipt subsystem, the advanced charging request is placed in the newly added core subsystem to be subjected to the account processing, and the parameters required by the account processing of the core subsystem can be transmitted to the core subsystem from the deposit receipt subsystem through the change of interfaces of the two subsystems, so that the compatibility of the old subsystem and the new subsystem is realized, the functional decoupling is realized, and the condition that the data are not uniform possibly caused by the same service calculation of the two subsystems is avoided.

Drawings

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

FIG. 1 is a schematic diagram of a large inventory information system according to an embodiment of the present disclosure;

FIG. 2 is a flow chart illustrating a method for interest bearing on a large inventory according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram illustrating an example of an interest-counting system for a large deposit list according to an embodiment of the present disclosure;

FIG. 4 is a flow chart illustrating a method for interest bearing on a grand inventory according to an embodiment of the present disclosure;

fig. 5 illustrates a computer device provided in an embodiment herein.

[ description of reference ]

101. A user terminal;

102. a deposit subsystem;

103. a core subsystem;

301. a user terminal;

302. a deposit subsystem;

3021. a matching unit;

3022. a first interest unit;

3023. a conversion unit;

3024. an acquisition unit;

3025. a calculation unit;

303. a core subsystem;

3031. a second messaging unit;

502. a computer device;

504. a processor;

506. a memory;

508. a drive mechanism;

510. an input/output module;

512. an input device;

514. an output device;

516. a presentation device;

518. a graphical user interface;

520. a network interface;

522. a communication link;

524. a communication bus.

Detailed Description

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

Fig. 1 is a schematic structural diagram of a large deposit receipt information system according to an embodiment of the present invention, where the diagram includes a user terminal 101, a deposit receipt subsystem 102, and a core subsystem 103, and it is described that the deposit receipt subsystem 102 analyzes an information request initiated by the user terminal 101, recognizes that the information request is an expired deposit receipt information request or an advance deposit receipt information request of a large deposit receipt, and processes the information request locally if the expired deposit receipt information request is, and sends the information request to the core subsystem 103 for processing if the advance deposit receipt information request is. Because the framework of the system is always developed along with the development of the service when the system is developed, when the service of banks in some regions is transited from a single large deposit receipt to a comprehensive service, the large deposit receipt is processed by the original deposit receipt subsystem 102, and a relatively small deposit receipt in the comprehensive service is processed by the core subsystem, under the condition that the original deposit receipt subsystem 102 is changed as little as possible, the work of paying out the interest in advance is delivered to the core subsystem 103 for processing, so that the calculation resources of the core subsystem 103 for the account of the live deposit receipt and the small deposit receipt can be fully utilized, and the problem that the result of the interest is not uniform when the deposit receipt subsystem 102 and the core subsystem 103 respectively calculate the task of paying out the interest in advance is solved.

In the embodiment of the present disclosure, the change to the deposit receipt subsystem 102 is to add middleware, distinguish the interest requests, and convert the command format, data requirement items, etc. of the deposit receipt subsystem 102 and the core subsystem 103, so as to implement communication and service processing between different subsystems, and save the high cost of redeveloping the deposit receipt subsystem 102 and the core subsystem 103.

Fig. 2 is a flowchart of an information method of a large deposit receipt according to an embodiment of the present disclosure, and in this diagram, it is described that the information system processes an expired interest-bearing request or an advanced interest-bearing request of a large deposit receipt differently by determining a type of the interest-bearing request in the deposit receipt subsystem, processes the advanced interest-bearing request through the core subsystem, multiplexes existing functions in the core subsystem, and maintains a service processing logic of the original deposit receipt subsystem as much as possible. The method specifically comprises the following steps:

step 201, the deposit receipt subsystem receives an interest bearing request of a user terminal, wherein the interest bearing request comprises an expired interest bearing request or an advanced interest bearing request of a large deposit receipt;

step 202, the deposit receipt subsystem carries out first interest processing on the due interest-drawing interest request to obtain a first interest result, or converts the prior interest-drawing interest request and then sends the converted prior interest-drawing interest request to a core subsystem;

step 203, the core subsystem performs second interest processing on the converted advance interest-drawing request to obtain a second interest result, and feeds the second interest result back to the deposit receipt subsystem;

and step 204, the deposit receipt subsystem sends the first information result or the second information result to the user terminal according to the information counting request of the user terminal.

As an embodiment herein, the receipt of the interest request of the user terminal by the deposit receipt subsystem further comprises the receipt of the interest request of the user terminal by the deposit receipt subsystem through a message bus;

matching the URL of the received interest request with a mapping table, and analyzing whether the interest request is an expired interest-collecting request or an advanced interest-collecting request;

and if the information is taken out in advance, converting the information taking out in advance and then sending the converted information to the core subsystem.

In this embodiment, when a local bank expands from a large deposit receipt service with a single service to more banking services with the expansion of the service, an original deposit receipt subsystem is no longer suitable for various integrated services, a core subsystem needs to be established to process the integrated services, such as the services of live deposit, and the like, and the interest-bearing standards and algorithms of different services are different, such as various interest-bearing ways of large deposit receipts, service types of paying principal money with interest being paid due regularly, service types of paying principal money with due money in advance, and various service types of paying principal money with due money in advance, while the live deposit service may be a daily interest-bearing service type, a daily interest-bearing mode service type with holidays removed, and interest-bearing mode service types with different interest rates according to holidays. Because the core subsystem and the original deposit-form subsystem developed later may have differences in data types (differences in data accuracy and the like) and different service types may have different interest-bearing modes, two subsystems are adopted for bearing the same service type respectively, different interest-bearing results may be generated, and data inconsistency is caused, thereby affecting the data hidden danger of the whole system. In the embodiment of the text, the due charging business type and the advanced charging business type of the large deposit receipt are respectively arranged in the deposit receipt subsystem and the core subsystem for processing, the special charging mode of the deposit receipt subsystem for the large deposit receipt is utilized for processing the specific business type, the core subsystem is utilized for carrying out the same charging processing as the comprehensive business on the specific business type of the large deposit receipt, so that the original deposit receipt subsystem and the newly added core subsystem are decoupled, and the charging results of the deposit receipt subsystem and the core subsystem are consistent.

In the above steps, a component unit for judging the interest-keeping request is added in the original deposit receipt subsystem, after the interest-keeping request of the user terminal is obtained from the message bus, the processing subsystem corresponding to the service type in the interest-keeping request is found according to the URL in the interest-keeping request and the mapping table, the basis for decoupling the deposit receipt subsystem and the core subsystem is recorded in the mapping table, which service types need to be sent to the core subsystem for interest-keeping processing, and which service types need to be left in the deposit receipt subsystem for interest-keeping processing. The original deposit receipt subsystem can be combined with a newly developed core subsystem by slightly modifying the original deposit receipt subsystem, the processing capacity of a specific service type of the deposit receipt subsystem is reserved, and the problem of non-uniform data among the subsystems is avoided.

As one embodiment herein, the URL of the interest request is http:// message bus domain name service port/custom URL/.

In this embodiment, the user-defined URL/the service type required to be performed by the user terminal is designated, each different service type has a corresponding user-defined URL, after the user-defined URL is matched with the mapping table, whether the interest request is an expiration interest-drawing request or an advance interest-drawing request is judged, and if the interest request is an expiration interest-drawing request, a first interest processing is performed through a first interest unit of the deposit receipt subsystem; and if the information is the information-collecting request in advance, converting the information-collecting request in advance and then sending the converted information-collecting request to the core subsystem.

As an embodiment herein, the deposit receipt subsystem performs a first message processing on the interest due drawing request, and the obtaining a first message result further comprises,

In this embodiment, the deposit receipt subsystem confirms the business product according to the product type in the due payment interest request, for example, the business product is a 1-year-old large deposit, the interest rate is XX, the interest payment is a quarterly payment, according to the comparison between the time of interest request and the time of deposit receipt, if the difference between the time of interest request and the time of the last due payment interest request reaches the time of 1 quarter, the deposit interest of the quarter can be calculated by using the interest rate, and the calculated deposit interest is sent to the account of the user. Because the appointed interest rule of each business product is possibly inconsistent, the interest processing of the interest due payment request is possibly inconsistent, and the interest processing is carried out on the interest due payment request of the user according to the interest data such as principal, interest rate and the like of the user's large deposit list, so that the interest data which the user should obtain is obtained.

In other embodiments, the time of interest payment may be monthly, quarterly, or semi-annually, or other time period payment, and the bank responds to the user's request for an expiration payment based on the result of the interest processing.

As an embodiment herein, converting the early fetch interest request to be sent to the core subsystem further comprises,

In this embodiment, the URL of the interest bearing request is http:// message bus domain name: service port/custom URL/, the middleware in the policy storage subsystem converts the URL of the interest bearing request in advance into a URL of the core subsystem, and the http:// core network management domain name: service port/core service URL/, which may be converted into http:// 127.0.0.1/module name/service type/custom URL according to the service, where 127.0.0.1 is the core network management domain name and 9060 is the service port, and the converted URL of the interest bearing request in advance may further include information such as the module name and the service type for processing the request.

Because the message processing of the core subsystem is different from the message processing of the deposit receipt subsystem, the required parameters are different, some of the parameters may be obtained in the core subsystem, or some of the parameters may need to be transmitted to the core subsystem by the deposit receipt subsystem for the message processing, and therefore, the message request message for early drawing the message after the conversion of the deposit receipt subsystem also includes some additional parameters. The format of the message of the information-collecting and charging request in advance mainly comprises two parts, namely sysHead and body, wherein the json format is used, the sysHead is a message header and comprises parameters which are transmitted to a core subsystem for information-collecting processing, and the body is a message data body and comprises parameters which are used by an original memory subsystem for information-collecting and charging request in advance, such as:

{

"sysHead":{

"authUserId": authorized user ",

"tranDate": "transaction date",

"seqNo": global water number ",

"subseqNo" means "substream number",

"trancode" means "transaction module",

"sourceBranch No": channel agency number ",

"messageCode": transaction code ",

apruserid: check user,

"progrmId": user software version ",

"brandhicld": the "agency number",

"userId": user ID ",

"aprflag": check flag ",

"sourceType": channel type ",

"userLang": user language ",

"authFlag": authorization flag ",

"tranTimestamp" and "timestamp",

"messageType": request type ",

service code "

},

"body":{

"prodType": product type ",

"term, number",

"termType" means "shelf life type Y-year, M-month, D-day",

"clientNo" client number, I am client unique identification ",

"baseAcctNo": account/card number ",

"realRate": execute interest rate ",

}

in the above embodiment, the sysHead message header includes various parameters conforming to the data format of the core subsystem, including, for example, a transaction date tranDate, an authorized user ID authuserld, a global flow number seqNo, a sub-flow number (the sub-flow number is changed when the message is forwarded between different systems), subSeqNo, a user software version programind, an audit user ID idaprpuserld, a user ID userld, a timestamp tranTimestamp, a service code serviceCode, where the main parameters include a transaction date, a flow order number (including a global flow number and a sub-flow number), and a timestamp.

When the message of the advance interest-bearing request is generated, in addition to adding the above parameters to the header of the message, the method also includes conversion of the data format of the parameters, for example, the timestamp data format of the deposit receipt subsystem is: the format of the timestamp data in the core subsystem is as follows: year/month/day/time/minute/second, and may further include converting a parameter of the data format in the inventory subsystem into a short integer into a long integer in the core subsystem.

The message data body comprises parameters required by the original deposit receipt subsystem for carrying out the advanced payment interest request interest processing, for example, the parameters comprise a product type prodType, a deposit term type termType, a client number clientNo, an account number baseAcctNo and an execution interest rate realRate, and the core subsystem can calculate the product life interest corresponding to the advanced payment interest request according to the parameters.

Since all the parameters required for the information processing in the original deposit receipt subsystem are local, the result can be directly calculated when various information processing is performed, for example, an advance information collection request or an expiration information collection request, but after the core subsystem is added to process other comprehensive services, the original functions in the deposit receipt subsystem need to be split and handed to the core subsystem for information processing, but the core subsystem may not store the parameters for calculating the advance information collection request of the large deposit receipt, and therefore the parameters need to be transmitted to the core subsystem, so that the core subsystem can complete the information processing of the advance information collection request. Therefore, the system structure shown in fig. 1 can be realized, the original deposit receipt subsystem and the core subsystem developed later are divided, the function of the original deposit receipt subsystem is divided to the core subsystem for processing, the core subsystem is combined aiming at the life time and rest processing function of other comprehensive services, and the problem of non-uniform data results caused by respectively carrying out rest processing on the two subsystems is solved.

As an embodiment herein, when the interest request is an advance interest-getting request, the deposit receipt subsystem sends the advance interest-getting request to a core subsystem for performing a current time interest-getting process, and receives a current time interest-getting result returned by the core subsystem;

the deposit receipt subsystem acquires the periodic drawing interest information of the large deposit receipt, and calculates the current interest result and the periodic drawing interest information to obtain an interest result;

and feeding back the interest counting result to the user terminal.

In this embodiment, the interest support policy for the advance interest support request of the large deposit receipt is periodic support, for example, once in half a year, if the user initiates the advance interest support request after obtaining the periodic support interest once in half a year, the advance interest support request needs to be sent to the core subsystem for live interest calculation, after calculating to obtain the interest of the large deposit receipt calculated by using the live interest rate, the interest during the period from the day of the effective large deposit receipt to the day of initiating the advance interest support request is obtained by subtracting the obtained periodic support interest from the live interest of the large deposit receipt, and the final interest support result is obtained and fed back to the user terminal. That is, the core subsystem is used to perform the lifetime interest-counting processing on other integrated services, such as the zero deposit transaction service and the lifetime deposit service, the lifetime interest-counting processing function of the core subsystem is used to perform the lifetime interest-counting calculation on the large deposit list which needs to be paid in advance, and the interest-counting calculation work on the large deposit list which is paid in advance is completed through the information of the periodic interest-counting of the large deposit list recorded in the deposit list subsystem, the same lifetime interest-counting work is only performed on the core subsystem, the expiration-counting work of the large deposit list is calculated by the deposit list subsystem, so that the function division of the whole system is realized, each subsystem is decoupled, the original deposit list subsystem can be docked with the core subsystem with less modification, and the problem that the same interest-counting processing is completed by two subsystems respectively, and the data is not unified is avoided.

Fig. 3 is a schematic diagram of a specific structure of an account system of a large deposit receipt according to an embodiment of the present disclosure, in which a core subsystem is added on the basis of an original deposit receipt subsystem to complete the account work of the large deposit receipt, the deposit receipt subsystem and the core subsystem may be implemented by a computer or a computer cluster, functions of the deposit receipt subsystem and the core subsystem may be implemented by software or a chip having corresponding functions, the system specifically includes a user terminal 301, a deposit receipt subsystem 302, and a core subsystem 303, the deposit receipt subsystem 302 further includes a matching unit 3021, a first account unit 3022, and a conversion unit 3023, the core subsystem 303 further includes a second account unit 3031,

the user terminal 301 is configured to send an interest bearing request, where the interest bearing request includes an expired interest bearing request or an advanced interest bearing request of a large deposit list;

the deposit receipt subsystem 302 is configured to perform a first interest processing on the due withdrawal interest request to obtain a first interest result; converting the information-collecting request in advance and then sending the converted information-collecting request to a core subsystem;

the matching unit 3021 is configured to match the URL of the received interest request with a mapping table, and analyze whether the interest request is an expired interest-bearing request or an advanced interest-bearing request;

the first interest unit 3022 is configured to perform a first interest processing through an interest module of the deposit receipt subsystem;

the conversion unit 3023 is configured to convert the advance interest-bearing request and send the converted advance interest-bearing request to the core subsystem;

the core subsystem 303 is configured to perform second interest processing on the converted advance interest-bearing request to obtain a second interest-bearing result, and feed the second interest-bearing result back to the deposit receipt subsystem;

the second interest unit 3031 is configured to perform second interest processing on the converted advance interest-collecting interest-calculating request to obtain a second interest result;

the deposit receipt subsystem 302 is further configured to send the first or second interest result to the user terminal 301 according to the interest bearing request of the user terminal.

The matching unit 3021 and the conversion unit 3023 may constitute a middleware, and the middleware may obtain an interest bearing request initiated by the user terminal 301 sent on the message bus, leave the interest bearing request due in the local processing, perform the grand deposit list interest bearing processing through the first interest bearing unit 3022 in the original deposit list subsystem 302, convert the interest bearing request in advance, and send the converted interest bearing request to the core subsystem 303 for the lifetime interest bearing processing.

As an embodiment herein, the deposit receipt subsystem 302 may be further configured to obtain the periodic interest information of the large deposit receipt, and calculate the current interest result received from the core subsystem and the periodic interest information to obtain an interest result; and feeding back the interest result to the user terminal.

In this embodiment, the deposit receipt subsystem 302 may further include an acquiring unit 3024 and a calculating unit 3025, the acquiring unit 3024 is configured to acquire the periodic drawing interest information of the volume deposit receipt, and the calculating unit 3025 is configured to calculate the expiration result received from the core subsystem and the periodic drawing interest information to obtain the interest result. The regular interest information is that the large deposit receipt partially draws the interest according to a certain time range, but not that the interest is drawn at one time after the large deposit receipt is due, and the drawn partial interest can be different along with different large deposit receipt products, and is not limited herein. When the user has paid part of the interest regularly, the user defaults to lift the advance interest-paying request, the interest rate of the large deposit receipt is changed into the current interest rate, the advance interest-paying request of the large deposit receipt is sent to the core subsystem for calculating the current interest rate, the amount of money that the user has paid regularly is subtracted from the current interest-paying result, and the rest part is the interest result corresponding to the advance interest-paying request of the user.

The account settlement subsystem 302 performs account settlement processing on the due information collection request without performing on-time account settlement processing on the early information collection request, the core subsystem performs on-time account settlement processing on the early information collection request, the two subsystems do not process the same account request, so that different calculation results cannot be generated, data unification among the subsystems is ensured, and the account settlement subsystem calculates the obtained on-time account result by using the core subsystem and the obtained on-time information collection information to obtain an interest result which the user should obtain.

Fig. 4 is a flowchart of an information method for a large deposit receipt according to an embodiment of the present disclosure, where a flow of completing large deposit receipt information among a user terminal, a message bus, a deposit receipt subsystem, and a core subsystem is described in this diagram, and specifically includes:

step 401, the user terminal initiates an interest-bearing request.

In this step, the interest bearing request may include an expiration interest bearing request of a large volume inventory or an early interest bearing request, where a URL of the interest bearing request is HTTP:// message bus domain name: service port/custom URL/, and the interest bearing request includes a plurality of parameters for interest bearing calculation, in this example, it is described that the user terminal sends an HTTP request, and the interest bearing request may be in a json format or an xml format, where the json format is:

{

"prod_type":"",

"term":"",

"term_type":"",

"client_no":"",

"base_acct_no":"",

"real_rate":""

}

if the interest bearing request is in xml format:

<？xml version＝"1.0"encoding＝"UTF-8"？>

where the interpretation of the fields is the product type prodType, the expiration of the product type term, the expiration type termType, the client number clientNo, the account number baseacctt no, the execution interest rate realRate.

At step 402, a message queue of interest requests is formed on a message bus.

In this step, the message bus may be a first-in first-out message queue.

In step 403, the deposit receipt subsystem obtains an information request on the message bus.

In step 404, the matching unit parses the interest bearing request and matches the interest bearing request with the mapping table.

In this step, matching is performed according to the custom URL of the interest request and the mapping table, and it is obtained that the interest request is an expired interest-getting request or an advanced interest-getting request.

Step 405, if the interest request is an advance interest-collecting request, converting the advance interest-collecting request.

In this step, when the interest request is a request for getting the interest in advance, the parameters required by the interest need to be converted by the conversion unit and then sent to the core subsystem. For example, if the parameter in the deposit receipt subsystem is long integer data and the parameter in the core subsystem is floating point data, the conversion rule of the parameter needs to be recorded in the mapping table, and the data type of the parameter obtained in the deposit receipt subsystem is converted into the data type supported by the core subsystem through the conversion unit. In addition, the conversion unit adds parameters required by the core subsystem for carrying out the information counting processing into the head of the information counting request message which is taken in advance, and the parameters do not exist in the core subsystem.

Step 406, if the interest request is an expired interest collection request, sending the expired interest collection request to the first interest unit.

In this step, the first interest unit belongs to a function module of the original deposit receipt subsystem and is used for carrying out interest processing on the expired large deposit receipt by combining with the product interest rule of the deposit receipt subsystem.

Step 407, the first interest bearing unit calculates the interest bearing request due to expenditure to obtain the interest bearing result of the large volume deposit receipt.

In this step, the first interest unit calls parameters in the deposit receipt subsystem to calculate the due interest-drawing request of the large deposit receipt, and performs interest-drawing processing by combining with the interest-drawing rules of the product, such as interest rate, drawing rules, principal and other associated factors of interest, to obtain an interest-drawing result.

And step 408, after receiving the converted information-collecting-in-advance request, the core subsystem calls a second information-collecting unit to carry out information-collecting processing.

In this step, the core subsystem calls a second interest unit to perform the daily interest-bearing processing on the advance-drawing interest-bearing request, and calculates the daily interest-bearing result according to the date difference between the deposit date and the time stamp of the large-volume deposit list and the daily interest rate.

And step 409, feeding back the result of the alive period interest counting to the deposit receipt subsystem.

In this step, the deposit receipt subsystem receives the expiration result and converts the data format of the expiration result into the data format supported by the deposit receipt subsystem.

Step 410, the obtaining unit in the deposit receipt subsystem obtains the interest information regularly drawn by the large deposit receipt, and the calculating unit is used for calculating the difference between the current interest information and the interest information regularly drawn to obtain the interest information.

In this step, according to the interest-bearing rules of different large deposit receipt products, different large deposit receipt products have their own unique interest-bearing rules, for example, paying corresponding interest to the user on a specific date, so the current interest-bearing result calculated by the core subsystem is not the final interest of the user, the user's already-paid periodic interest needs to be deducted from the current interest-bearing result, and the rest is the user's interest-bearing result. If the interest counting result is a negative value, namely the accumulated interest paid by the large deposit list regularly exceeds the current interest paid by the user in advance, the interest counting result of the user's interest compensation difference value is generated.

In step 411, the inventory subsystem sends the message result to the message bus.

In step 412, the message bus sends the message result to the user terminal.

In this step, the user terminal presents the interest result of the advanced interest-bearing request, if the user still holds the advanced interest-bearing request, the difference between the drawn interest and the current interest-bearing result needs to be compensated, then the deposit slip subsystem will transfer the user's principal into the account appointed by the user or return to the original account of the large deposit slip, or transfer the balance of the interest which is larger than the drawn interest and the principal into the account appointed by the user or return to the original account of the large deposit slip. And if the user cancels the advance interest-collecting request, ending the advance interest-collecting request.

As shown in fig. 5, a computer device provided in an embodiment of the present invention is shown, and a device of the inventory subsystem or the core subsystem in the embodiment of the present invention may be a computer device in the embodiment of the present invention, and performs the above-described method in the present invention. The computer device 502 may include one or more processors 504, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 502 may also include any memory 506 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 506 may include any one or combination of the following: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 502. In one case, when the processor 504 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 502 can perform any of the operations of the associated instructions. The computer device 502 also includes one or more drive mechanisms 508, such as a hard disk drive mechanism, an optical disk drive mechanism, or the like, for interacting with any of the memories.

Computer device 502 may also include an input/output module 510 (I/O) for receiving various inputs (via input device 512) and for providing various outputs (via output device 514). One particular output mechanism may include a presentation device 516 and an associated Graphical User Interface (GUI) 518. In other embodiments, input/output module 510 (I/O), input device 512, and output device 514 may not be included, but merely as a single computer device in a network. Computer device 502 can also include one or more network interfaces 520 for exchanging data with other devices via one or more communication links 522. One or more communication buses 524 couple the above-described components together.

Communication link 522 may be implemented in any manner, such as through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. Communication link 522 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

Embodiments herein also provide computer readable instructions, wherein a program thereof causes a processor to perform a method as described above when the instructions are executed by the processor.

It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.

It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.

In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The principles and embodiments of the present disclosure are explained in detail by using specific embodiments, and the above description of the embodiments is only used to help understanding the method and its core idea; meanwhile, for a person skilled in the art, according to the idea of the present disclosure, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present disclosure should not be construed as a limitation to the present disclosure.

Claims

1. An interest-bearing method of a large-volume deposit list is characterized by comprising the following steps,

the core subsystem carries out second interest processing on the converted advanced interest-bearing request to obtain a second interest-bearing result, and the second interest-bearing result is fed back to the deposit receipt subsystem;

2. The method of claim 1, wherein the step of receiving an interest request from the subscriber terminal by the deposit receipt subsystem further comprises,

3. The method of claim 2, wherein the URL of the interest request is http:// MessageBusDomains/custom URL/.

4. The method of claim 2, wherein the deposit sub-system performs a first interest-bearing process on the interest-bearing request, and further comprises obtaining a first interest-bearing result,

5. The method of claim 3, wherein transforming the prepaid billing request to the core subsystem further comprises,

6. The method of claim 5, wherein transforming the prepaid billing request to the core subsystem further comprises,

and adding a transaction date, a serial number and a timestamp into the header of a message formed by the advance interest-bearing request.

7. An interest system of a large-volume deposit list is characterized by comprising,

the core subsystem is used for carrying out second interest bearing processing on the converted information-drawing-in-advance request to obtain a second interest bearing result, and feeding the second interest bearing result back to the deposit receipt subsystem;

8. An interest system for a large inventory according to claim 7, further comprising a message bus for receiving an interest request from said user terminal;

the deposit subsystem further comprises a matching unit, a first interest unit and a conversion unit;

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of the preceding claims 1-6 when executing the computer program.

10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, is adapted to carry out the method of any of the preceding claims 1-6.