TWM530997U - Financial system and financial server - Google Patents

Abstract

A financial system is disclosed. Financial system includes a first server and a second server. First server includes a plurality of first financial contracts. Second server includes a plurality of second financial contracts, which are synchronous backups of the plurality of the first financial contracts. When the first server receives a write-in request about one of the first financial contracts, a lock module of the second server locks a corresponding one of the second financial contracts to refuse another write-in request. When the first server completes the write-in of the one of the first financial contracts, a synchronous module of the second server synchronizes the corresponding one of the second financial contracts with the complete written-in one of the first financial contracts. After synchronization completes, an unlock module of the second server unlocks the corresponding one of the second financial contracts.

Description

Financial servo system and financial server

The present disclosure relates to a servo system, and more particularly to a financial servo system.

In the traditional database dual-center architecture, the second center is mostly used for backup purposes. In order to maximize the benefits of the dual-center architecture, companies or users will want to use each database for decentralized operations. In order to achieve this goal, the system is bound to synchronize the data base at any time to reduce the gap between the data of each database. However, there is often a time lag between the synchronization processes, which will result in unequal information in each database. The application of the database dual-center architecture to financial transactions, the gap in the data in each database may cause financial losses for enterprises or customers.

The disclosure discloses a financial servo system that can be used to write and store a plurality of financial transaction contracts, such as life insurance, policy loans, policy claims, survival payments, policy changes, financial futures, and the like. The financial servo system disclosed in the disclosure can avoid each server There is a problem with information that is not equal.

In an embodiment of the disclosure, the financial servo system includes a first server and a second server. The first server includes a first storage module, a first locking module, a first synchronization module, and a first unlocking module, wherein the first storage module stores a plurality of first financial contracts. The second server includes a second storage module, a second locking module, a second synchronization module, and a second unlocking module, wherein the second storage module stores a plurality of copies synchronized with the first financial contract of the plurality of pens Pen second financial contract. The second synchronization module is connected to the first synchronization module. When the first server receives a write request for one of the first financial contracts, the second lock module locks one of the corresponding second financial contracts to reject another write request. When the first server completes writing the first financial contract, the second synchronization module synchronizes one of the corresponding second financial contracts with the first financial contract after the writing is completed. When the synchronization is completed, the second unlocking module unlocks one of the corresponding second financial contracts.

A financial server is proposed in one of the technical aspects of the disclosure. The financial server includes a storage module, a locking module, a synchronization module, and an unlocking module. The storage module stores a plurality of second financial contracts. The second financial contract is used to synchronously back up the plurality of first financial contracts on another server. When one of the first financial contracts receives a write request, the locking module locks one of the second financial contracts corresponding to the first financial contract to reject another write request. When the first financial contract is written, the synchronization module synchronizes the corresponding second financial contract with the first financial contract after the completion of writing. When the synchronization is completed, the unlocking module unlocks the second financial contract.

100‧‧‧Financial Servo System

110a‧‧‧First server

110b‧‧‧Second server

120a, 120b‧‧‧ input interface

130a, 130b‧‧‧ storage module

140a, 140b‧‧‧Locking module

150a, 150b‧‧‧ unlocking module

160a, 160b‧‧‧ Synchronous Module

300, 400, 500‧‧‧ flow chart

S310, S320, S330, S340‧‧‧ steps

S410, S420, S430, S440‧‧ steps

P510, P520, P530, P540, P550, P560‧‧‧ Process

A1~An, B1~Bn‧‧‧ financial contract

Figure 1 is a diagram of a financial servo system architecture in accordance with one embodiment of the disclosed document.

FIG. 2 is a schematic diagram of data stored in a storage module of a financial servo system according to an embodiment of the disclosure.

Figure 3 is a flow chart showing the operation of a financial server in one embodiment of the present disclosure.

Figure 4 is a flow chart showing the operation of a financial server in one embodiment of the present disclosure.

Figure 5 is a flow chart showing the operation of the financial servo system in the case of an abnormality in one embodiment of the disclosed document.

The embodiments are described in detail below with reference to the drawings, but the specific embodiments described are only used to explain the present invention, and are not intended to limit the present invention, and the description of structural operations is not intended to limit the order of execution thereof. The device that is recombined by the components and produces equal devices is the scope covered by the novel disclosure.

Please refer to FIG. 1 , which illustrates the architecture of a financial servo system 100 in one embodiment of the disclosed document. The financial servo system 100 includes a first server 110a and a second server 110b. The first server 110a has an input interface 120a, a storage module 130a, a locking module 140a, an unlocking module 150a, and a synchronization module 160a, and the second server 110b has an input interface 120b. The storage module 130b, the locking module 140b, the unlocking module 150b, and the synchronization module 160b. The synchronization module 160a is connected to the synchronization module 160b to perform bidirectional transmission of data between the first server 110a and the second server 110b.

Please refer to FIG. 2 together. FIG. 2 is a schematic diagram showing the data stored in the storage modules 130a and 130b in the financial servo system 100 of FIG. The storage module 130a of the first server 110a of the financial server system 100 stores a plurality of financial contracts A1~An, and the storage module 130b of the second server 110b stores the corresponding storage modules 130a. A plurality of financial contracts B1~Bn that are stored in a synchronized financial contract A1~An.

In an embodiment of the present disclosure, when the user inputs a write request for a financial contract in the storage module 130a (for example, a request for access or change of the contract content) on the input interface 120a of the first server 110a. At this time, the first server 110a will transmit a notification that the first server 110a has received the write request to the second server 110b. After the second server 110b receives the notification, the locking module 140b locks the corresponding financial contract in the storage module 130b to reject the input corresponding to the input interface 120b of the second server 110b. A write request for a financial contract.

Next, the first server 110a starts processing the write process. When the writing is completed, the first server 110a will send a notification that the writing has been completed to the second server 110b. After the second server 110b receives the notification that the writing has been completed, the synchronization module 160b starts to synchronize the corresponding financial contract in the storage module 130b with the financial contract written in the storage module 130a. After the synchronous backup is completed, the unlocking module 150b of the second server 110b The corresponding financial contract in the storage module 130b is unlocked. After unlocking, the second server 110b will resume accepting write requests for this corresponding financial contract.

For example, when the input interface 120a of the first server 110a receives a write request for the financial contract A1, the first server 110a will notify the second server 110b. When the second server 110b receives the notification, the locking module 140b locks the financial contract B1 corresponding to the financial contract A1 in the storage module 130b. At this time, if a user wants to write the financial contract B1 to the second server 110b, the second server 110b will reject the write request. Then, when the second server 110b receives the notification that the writing of the financial contract A1 has been completed, the synchronization module 160b synchronizes the financial contract B1 with the financial contract A1 after the writing is completed. The unlocking module 150b will unlock the financial contract B1 after the synchronization is completed. At this time, the user can start writing to the financial contract B1 at the second server 110b.

In addition, when the input interface 120a of the first server 110a receives a write request for one of the financial contracts A1~An, the locking module 140a may also lock one of the financial contracts to reject the input interface. 120a enters another write request for one of the financial contracts. When the writing is completed, the unlocking module 150a unlocks one of the financial contracts. After that, the user can enter another write request for one of the financial contracts again.

It should be noted that the user can also request and execute the writing of one of the financial contracts B1~Bn at the input interface 120b of the second server 110b. At this time, the first server 110a will financial contract A1~An The financial contract corresponding to one of the financial contracts is locked, and the data is synchronized and unlocked after the writing is completed. That is, the first server 110a and the second server 110b are all servers that can work simultaneously or support each other. In conjunction with the disclosure document, the above-mentioned lock mechanism is disclosed, and a dual-center system without information gap can be realized.

In one embodiment of the present disclosure, the operational flow of the dual-center architecture can be as shown in FIGS. 3 and 4, respectively. FIG. 3 is a flow chart 300 showing the operation of the first server 110a in one embodiment of the disclosed document. In step S310, the first server 110a may generate a first timestamp T1 indicating the start of writing of the financial contract when receiving a write request for one of the financial contracts (for example, one of A1~An). And transmitting the first time stamp T1 to the second server 110b. In step S320, one of the financial contracts will be locked to reject another write request. In step S330, when the writing to the financial contract is completed in the first server 110a, the first server 110a generates a second time stamp T2 indicating that the writing is completed, and transmits the second time stamp T2 to the second servo. The device 110b. In step S340, one of the financial contracts is unlocked.

FIG. 4 is a flow chart 400 showing the operation of the second server 110b in one embodiment of the disclosed document. In step S410, after receiving the first time stamp T1 from the first server 110a, the second server 110b writes the corresponding financial contract of one of the financial contracts requested by the first server 110a (for example, B1~ The corresponding one of Bn is locked. In step S420, after receiving the second time stamp T2 from the first server 110a, the second server 110b writes the corresponding financial contract with the first server 110a. The completed financial contract is synchronized. Next, in step S430, when the synchronization is completed, the second server 110b will generate a third time stamp T3 indicating that the synchronization is completed. In step S440, the second server 110b unlocks the corresponding financial contract that is synchronized.

In order to make the explanation clearer, the following is an example in which the first server 110a receives a write request for the financial contract A1. Please refer to the following table 1: In the table, T1, T2, and T3 are sequentially referred to as a first timestamp, a second timestamp, and a third timestamp, and the character "o" indicates the existence of a timestamp. When there is no time stamp in the first server 110a and the second server 110b, both the first server 110a and the second server 110b can accept write requests for any financial contract. When the first server 110a receives the write request for the financial contract A1, the first time stamp T1 is generated. When the first time stamp T1 indicating that the write request of the financial contract A1 is received exists, the first server 110a will reject another write request for the financial contract A1. At the same time, the second server 110b is also unable to accept a write request for the financial contract B1 (corresponding to A1).

When indicating the second time for the completion of the writing of the financial contract A1 After the interstitial stamp T2 is generated, the first server 110a can begin receiving another write request for the financial contract A1. However, since the financial contract B1 in the second server 110b has not been synchronized with the newly written financial contract A1, the write request for the financial contract B1 cannot be accepted. After the synchronization is completed, the third time stamp T3 will be generated, and the second server 110b may start receiving the write request for the financial contract B1.

Briefly, for the first server 110a that receives the write request for a financial contract, as long as the first timestamp T1 and the second timestamp T2 exist, it can continue to receive another write for the same financial contract. Into the request. For the second server 110b, the write request for the corresponding financial contract can continue to be received only when the first timestamp T1, the second timestamp T2, and the third timestamp T3 are present.

In one aspect of the disclosure, the financial servo system 100 may further include a third server or more servers to perform larger-scale distributed operations at the same time. For example, when the first server receives the write request for the financial contract, the second server, the third server or the remaining servers lock their respective corresponding financial contracts, and the first servo After the completion of the writing of the financial contract, the financial contract corresponding to the first server is synchronized with the financial contract of the first server. That is to say, the content of the disclosure is not limited to two servers, and the number of servers can be increased according to actual needs.

In another technical aspect of the disclosure document, when an abnormality occurs in a server in the financial servo system, the operation mechanism of the financial servo system is disclosed herein. Referring to FIG. 5, FIG. 5 illustrates an embodiment of the disclosed document. The operational flow diagram 500 of the financial servo system 100 in the event of an anomaly. For example, the financial servo system 100 includes a first server 110a and a second server 110b. Here, the failure or abnormality of the second server 110b will be described as an example. In process P510, the second server 110b fails or is abnormal. In process P520, the financial servo system 100 locks the financial contracts B1~Bn in the second server 110b and directs further write or access operations to the first server 110a so that the service can continue uninterrupted.

In process P530, the failure or abnormality of the second server 110b is eliminated or repaired. In process P540, after the fault or abnormality is eliminated, the financial servo system 100 will determine whether the first server 110a has a write operation for the financial contract during the failure or abnormality of the second server 110b. If there is no write operation during the failure or abnormality of the second server 110b, the second server 110b can accept a new write request (process P560). If a write operation occurs in the first server 110a during the failure or abnormality of the second server 110b, the process is directed to the process P550, and the corresponding financial contract in the second server 110b is performed with the first server 110a. The synchronization of the financial contract after being written. When the synchronization is complete, the second server 110b can proceed to process P560 to begin accepting new write requests to resume normal dual center system operation.

Although the embodiments of the present invention have been disclosed as above, it is not intended to limit the present invention. Any one skilled in the art can make some modifications and retouchings without departing from the spirit and scope of the present invention. The scope is defined as defined in the scope of the patent application.

100‧‧‧Financial Servo System

110a‧‧‧First server

110b‧‧‧Second server

120a, 120b‧‧‧ input interface

130a, 130b‧‧‧ storage module

140a, 140b‧‧‧Locking module

150a, 150b‧‧‧ unlocking module

160a, 160b‧‧‧ Synchronous Module

Claims (10)

A financial servo system includes: a first server, a first storage module, a first locking module, a first synchronization module, and a first unlocking module, wherein the first storage module stores a first financial contract; a second server comprising a second storage module, a second locking module, a second synchronization module, and a second unlocking module, the second storage module Storing a plurality of second financial contracts synchronized with the first financial contract of the plurality of pens, wherein the second synchronization module is connected to the first synchronization module; wherein when the first server receives a pair of first When a write request of the financial contract is made, the second locking module locks one of the corresponding second financial contracts to reject another write request; wherein when the first server completes one of the first When the financial contract is written, the second synchronization module synchronizes one of the corresponding second financial contracts with the one of the first financial contracts after the writing is completed; and wherein the corresponding one of the second financial contracts When the financial contract is synchronized, Two modules to unlock the corresponding financial contract in which the sum of the second unlocked. The financial servo system of claim 1, wherein when the first server receives the write request for one of the first financial contracts, a first time stamp is generated, and the second locking module responds to the The first timestamp locks one of the corresponding second financial contracts to reject another write request. The financial server system of claim 1, wherein when the first server completes writing the first financial contract, a second time stamp is generated, and the second synchronization module responds to the second time. The stamp synchronizes one of the corresponding second financial contracts with the one of the first financial contracts after the completion of the writing. The financial server system of claim 1, wherein when the corresponding one of the second financial contracts is synchronized, a third time stamp is generated, and the second unlocking module responds to the third time stamp corresponding to the third time stamp. One of the second financial contracts is unlocked. The financial servo system of claim 1, wherein the first locking module locks one of the first financial contracts when the first server receives the writing request for one of the first financial contracts To reject another write request. The financial server system of claim 5, wherein the first unlocking module unlocks one of the first financial contracts when the first server completes writing the one of the first financial contracts. The financial servo system of claim 1, wherein when the second server is abnormal, the second locking module locks the plurality of second financial contracts to reject any write request. The financial servo system of claim 7, wherein the second synchronization module is connected according to the connection after the second server recovers from the abnormality The one or more first financial contracts written during the abnormal period synchronize the second financial contract corresponding to the one or more first financial contracts with the one or more first financial contracts that are written. A financial server includes: a storage module, the storage module stores a plurality of second financial contracts, and the second financial contract is used for synchronously backing up a plurality of first financial contracts on another server; The lock module, when one of the first financial contracts receives a write request, the lock module locks one of the second financial contracts corresponding to one of the first financial contracts to reject another write request; a synchronization module, when the first financial contract is written, the synchronization module synchronizes one of the second financial contracts with the one of the first financial contracts after the completion of writing; and an unlocking module When the second financial contract is completed synchronously, the unlocking module unlocks one of the second financial contracts. The financial server of claim 9, wherein when the another server receives the write request for the first financial contract, the first time stamp is generated, and the locking module responds to the first The timestamp locks one of the second financial contracts to reject another write request.