CN109146653B

CN109146653B - Distributed environment-based accounting daily cutting checking method and device

Info

Publication number: CN109146653B
Application number: CN201810736820.5A
Authority: CN
Inventors: 郭宏文; 刘浩
Original assignee: Nanjing Xingyun Digital Technology Co Ltd
Current assignee: Jiangsu Sushang Bank Co ltd
Priority date: 2018-07-06
Filing date: 2018-07-06
Publication date: 2022-11-22
Anticipated expiration: 2038-07-06
Also published as: CN109146653A

Abstract

The embodiment of the invention discloses a checking method and a checking device for daily account information based on a distributed environment, relates to the technical field of internet, and can be used for realizing centralization under the condition of distributed account processing, completely avoiding the problem of total score checking in a single-point mode, maximizing the post of accounting logic, avoiding the interference of internal management requirements on customer service, greatly improving the flexibility of accounting processing and reducing design concerns of a business processing part in a system. The invention includes: and after receiving the request message, capturing the date part of the current time of the service server as the currently requested accounting time (RTD), and when detecting that the RTD in the account table is inconsistent with the Time (TD) in the database record, performing time scrolling by taking the latest time in the time axis as the reference, and summarizing the account amount of the specified date to obtain the end balance of the specified date. The method is suitable for extracting and checking the accounting accuracy in a large concurrency scene.

Description

Distributed environment-based checking method and device for daily account switching

Technical Field

The invention relates to the technical field of internet, in particular to a method and a device for checking account daily-degree based on a distributed environment.

Background

With the development of internet technology, online financial services are gradually expanded, and at present, domestic banks and finance have basically realized digitization and networking. For the banking and financial industries, the effectiveness and accuracy of financial management are important, and particularly, the financial industry is different from the retail industry and needs to be in the end of the day and the month.

The current architecture is based primarily on the core banking system (corebanki ng), and the final day of the accounting is checked for total points and balance of loans. Among them, how to realize the retention of the day-cut point under the uninterrupted condition of 7 × 24 hours becomes a technical difficulty. In order to solve the problem, in the prior art, an accounting entry checking mechanism, that is, a balance snapshot mechanism, is mainly used for performing account checking. In this case, the daily cutting process is triggered by a mechanism, and all the accounting statements are submitted into a single record of the database, so that the banking industry refers to the largest user of the high-end server device, and a lot of money is spent each year to build the central computer room, and the hardware performance of the central computer room is reached to the greatest extent. And once a hacker attack is met, the whole bank system is often paralyzed.

Disclosure of Invention

The embodiment of the invention provides a checking method and a checking device for daily account switching based on a distributed environment, which can solve the problem of checking general scores in a decentralized and completely single-point mode under the condition of distributed account processing, enable accounting logic to be maximum and post-positioned, avoid the interference of internal management requirements on customer service, greatly improve the flexibility of accounting processing and reduce design concerns of a business processing part in a system.

In order to achieve the above object, the embodiment of the present invention does not adopt the conventional mechanism (the conventional centralized large computer room) that takes the date in the database table as the accounting time, and completely takes the application server time in each distributed node as the accounting time. The specific technical scheme is as follows:

after receiving the request message, capturing a date part of the current time of the service server as the currently requested accounting time (RTD), wherein the received request message is a distributed system, and the distributed system is composed of at least 2 service servers as nodes; recording the RTD and the time of Last Transaction (LTD) in each customer's account table;

when the RTD in the account table is detected to be inconsistent with the Time (TD) in the database record, performing time scrolling by taking the rearmost time in the time axis as a reference;

and summarizing account amount of the appointed date to obtain the end balance of the appointed date.

The checking method for the accounting daily switch based on the distributed environment provided by the embodiment of the invention solves the problem of consistency daily switch without a single-point storage mode, and greatly reduces the difficulty of deployment and application development. The problem that the accounting time is inconsistent with the customer perception time and the situation that the transaction is rejected in millisecond level in the traditional daily cutting mechanism is solved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the embodiments 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. 1a and fig. 1b are schematic diagrams of system architectures according to embodiments of the present invention;

FIG. 2 is a schematic flow chart of a method according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an embodiment of the present invention;

fig. 4 is a schematic diagram of an embodiment provided in the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the present invention will be described in further detail with reference to the accompanying drawings and specific embodiments. Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are exemplary only for explaining the present invention and are not construed as limiting the present invention. As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or coupled. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

The embodiment of the present invention may be specifically implemented in a system as shown in fig. 1a, wherein:

the analysis server may specifically be a separately made server device, such as: rack-mounted, blade, tower-type or cabinet-type server equipment, or hardware equipment with higher computing power such as workstations and large computers; or may be a server cluster consisting of a plurality of server devices.

And the database system runs the user account data and information and is used for storing and managing the user account data and information. The database system may be a single analysis server for managing and storing data, or may be a server cluster including a plurality of analysis servers. And operating a database corresponding to the analysis server on hardware equipment of the database system, and managing and storing the data of the analysis server. Specifically, a commonly used mesh Database (Network Database), a Relational Database (Relational Database), a tree Database (Hierarchical Database), an Object-oriented Database (Object-oriented Database), and a new generation big data system architecture may be adopted.

The analysis server may specifically also be integrated in a database system, such as: dividing part of analysis servers in a server cluster into front-end servers for interacting data with a user terminal, wherein the front-end servers can be called analysis servers; and another part of servers and most of storage devices (such as disk arrays, cache machines and the like) in the server cluster can be used as a background database to provide data access services for the front-end server, and the problem database is maintained on the background database.

Optionally, the system shown in fig. 1b may further include a user terminal, which may be specifically implemented as a single system, or integrated into various different business application systems, such as a smart phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), or a Personal Digital Assistant (PDA).

The embodiment of the invention provides a checking method for daily account switching based on a distributed environment, which can be specifically realized by an analysis server, and as shown in fig. 2, the checking method comprises the following steps:

s1, after receiving the request message, capturing the date part of the current time of the service server as the accounting time (RTD) of the current request.

The system comprises a distributed system and a plurality of service servers, wherein the distributed system is used for receiving request messages and consists of at least 2 service servers as nodes; recording the RTD and the time of Last Transaction (LTD) in each customer's account table

After receiving the request message, capturing the date part of the current time of the service server in the processing flow as the currently requested accounting time (RTD), and running through the whole processing process.

The accounting time described in this embodiment may be understood as the date part of the current time value of the machine, and the day-to-day process does not focus on the hour, minute and second, but only on which day.

The embodiment does not adopt the traditional mechanism (traditional centralized large machine room) which takes the date in the database table as the accounting time, and completely takes the service server time in each distributed node as the accounting time, so that the processing has at least two advantages, and the problems that the accounting time is inconsistent with the customer perception time and the traditional daily cutting mechanism has millisecond-level transaction rejection are solved.

And S2, when the RTD in the account table is detected to be inconsistent with the Time (TD) in the database record, performing time scrolling by taking the most backward time in the time axis as a reference.

When the account table is processed, the requested accounting date RTD and the accounting date in the database record should be kept consistent, and time scrolling is performed based on the most backward time in the time axis, that is, for the requested accounting date RTD, the accounting date TD of the account in the database record, the last accounting date LTD of the account, the balance a of the account, and the last balance LA of the account, specifically, the RTD and the TD are both kept consistent backward, and update is earlier. As shown in fig. 3, there are the following relationships and processes (where operator = > indicates that the value of the operator left parameter is put into the right parameter):

if the RTD = TD, updating A;

if RTD > TD, processing is performed: TD = > LTD, RTD = > TD, a = > LA, and update a; if RTD < TD, processing is carried out: TD = > RTD, and update a.

And S3, summarizing the account amount on the appointed date to obtain the end-of-term balance on the appointed date.

Specifically, at the end of the day, the accounting processing part of the system selects a date D, and notifies the business processing part to sum the total amount of the customer account on the day, so that the following relationships and processing exist for the current machine date RTD, the accounting time TD of the account, the time LTD of the last transaction of the account, the balance a of the account, and the last balance LA of the account:

when the specified date D is detected to be less than or equal to the RTD on any service server, judging that the processing is failed, otherwise:

if D = TD, participate in the summary of the end balance of the specified date with LA;

if D > TD, participate in the summary of the end balance on the specified date with A.

For example, as shown in fig. 4:

further, the accounting processing part of the system forms the last date balance after the last date entry stream of a certain subject is posted one by one, and the balance is equal to the sum of the obtained sum balances of all parts of the distributed system, so that the total score checking process is completed, that is, for a certain subject: initial balance plus Sigma current daily running detail =Sigmaaccount of all branch households under the project.

It should be noted that some terms mentioned in the present embodiment, such as: the term accounting time (RTD), the time of the Last Transaction (LTD), the time in the database record (TD), etc. are all terms in the field of accounting, and in some cases, these terms may be changed according to the needs, such as: the time in the database record, which may sometimes be referred to as the data record time, or the time of warehousing, etc., may be used by those skilled in the art as is commonly understood in the accounting arts.

For another example: at present, in the management of accounting data, a general ledger is usually established in a financial system, and a corresponding account is also established in a client system, so that dual-system accounting management is realized, for example: the account that each client establishes in the system is called an account division, which is also called an account table. On the data level, one instruction message for increasing and decreasing the general ledger is the content of the accounting entry. In step 1 of this embodiment, taking a date part of the current time of the service server as an accounting time (RTD) of the current request includes:

if the request message is detected to correspond to at least two accounts, determining a node where each account is located;

and acquiring the date part of the current time of the service server of each determined node, and capturing the earliest date part of the current time of the service server of each node as the RTD.

Further, when the request message corresponds to at least two accounts, there are two processing mechanisms:

the mechanism 1 is that accounting processing of each client account is only balanced with 'internal accounts';

mechanism 2: the business processing part can mark the request ID of each account operation, and the ID of multiple account operations triggered by the same request is the same, but the accounting time may be different. For a set of account operation across dates, transition entry processing is automatically added when the accounting engine processes the account operation.

Further, in step 2 of this embodiment, in the processing process, the account table is processed first, and then the accounting or event table is processed, and the accounting time of the related records in the account table and the accounting/event table must be consistent.

The embodiment of the invention also provides a checking device for daily account switching based on a distributed environment, which specifically comprises the following steps:

a receiving module: the system comprises a data acquisition module, a data acquisition module and a data processing module, wherein the data acquisition module is used for acquiring a date part of the current time of a business server as the accounting time (RTD) of the current request after receiving a request message;

a processing module: the time scrolling device is used for scrolling time based on the most backward time in the time axis when the RTD in the account table is detected to be inconsistent with the Time (TD) in the database record;

an output module: and the account amount of the appointed date is collected to obtain the end balance of the appointed date.

The processing module further comprises: time scrolling with respect to a later time in the time axis, comprising:

if the RTD = TD, updating A;

if RTD > TD, processing: TD = > LTD, RTD = > TD, a = > LA, and update a;

if RTD < TD, processing: TD = > RTD, and update a;

wherein a represents the balance of the account, LA represents the balance of the account on the last day, and the operator = > represents: the value of the operator left parameter is put into the right parameter.

The receiving module further comprises a date part of the current time of the service server as a current requested accounting time (RTD), including:

Further, the output module may further include a step of summarizing the account amount on the specified date, and the obtaining the end balance on the specified date includes:

if D = TD, participating in the summary of the end-of-term balance on the specified date with LA;

if D > TD, participate in the summary of the end-of-term balances on the specified date with A.

All the embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are also within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A checking method for accounting daily-time based on a distributed environment is characterized by comprising the following steps:

after receiving the request message, capturing the date part of the current time of the service server as the RTD of the current request, wherein the received request message is a distributed system which is composed of at least 2 service servers as nodes; recording the RTD and the time LTD of the last transaction in an account table of each customer;

when the RTD in the account table is detected to be inconsistent with the time TD in the database record, time rolling is carried out by taking the most backward time in the time shaft as the reference;

summarizing account amount on a specified date to obtain the term end balance on the specified date;

the time scrolling with reference to the most backward time in the time axis comprises the following steps:

if the RTD = TD, updating A;

if RTD > TD, processing: TD = > LTD, RTD = > TD, a = > LA, and update a;

if RTD < TD, processing is carried out: TD = > RTD, and update a;

2. The method of claim 1, wherein capturing a date part of a current time of a traffic server as an account time RTD of a current request comprises:

3. The method of claim 2, wherein aggregating account amounts for a specified date resulting in an end of term balance for the specified date comprises:

when the specified date D is detected to be less than or equal to the RTD on any service server, the judgment processing is failed, otherwise:

4. A reconciliation apparatus for accounting daily cutting based on a distributed environment, comprising:

a receiving module: the system comprises a service server, a RTD (credit date) server, a distributed system and a data processing system, wherein the RTD is used for capturing the date part of the current time of the service server as the current request after receiving a request message, and the distributed system is composed of at least 2 service servers as nodes; recording the RTD and the time LTD of the last transaction in an account table of each customer;

a processing module: when the RTD in the account table is detected to be inconsistent with the time TD in the database record, time rolling is carried out by taking the most backward time in the time axis as the standard;

an output module: the account amount used for summarizing the appointed date is obtained, and the term end balance of the appointed date is obtained;

the processing module further comprises:

if the RTD = TD, updating A;

if RTD > TD, processing is performed: TD = > LTD, RTD = > TD, a = > LA, and update a;

if RTD < TD, processing: TD = > RTD, and update a;

5. The apparatus of claim 4, wherein the receiving module further comprises:

6. The apparatus of claim 5, wherein the output module further comprises: