Banking business protocol unified management method and system

Abstract

The invention discloses a banking business protocol unified management method and system, and belongs to the field of computers. The method comprises the following steps: acquiring a protocol signing request; the protocol request comprises a protocol type and protocol element information; converting the protocol element information of the corresponding protocol signing request into protocol model information according to the protocol type; the protocol model information comprises protocol master information and protocol proprietary information; and registering the protocol master information and the protocol proprietary information. According to the method, a factory mode and a basic object inheritance mode in a software design mode are utilized. Isolation and process unification are carried out on the classification and classification registration processes of the protocol information. When a plurality of projects are implemented, only the differentiated implementation of newly added protocol types needs to be concerned. And the existing protocol signing is not influenced. And the stability of the system function is improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and system for unified management of banking business agreements. Background Art

[0002] In the business processing scenarios of banks, contractual agreements are important documents with legal clauses. Based on different business scenarios, natural persons need to sign clear contractual agreements with different business lines or service departments of banks for certain services or products, user protection and agreed rights and obligations of both parties. However, due to the continuous enrichment of banking service content, there are often many signed agreements. And they are constantly increasing. From a technical perspective, unified management of these agreements is becoming more and more important. In actual use scenarios, due to the limitations of technical planning, the technology usually used is to provide independent agreement signing management processing for different agreement management. Different agreement management information data is separated or isolated, and unified management cannot be achieved. When a new type of agreement is signed, it is necessary to redefine the model for the new agreement and carry out technical development to achieve management requirements. The implementation process often consumes manpower and time, and cannot quickly respond to business development requirements. At the same time, due to the separation and inconsistency of management information, it is difficult to achieve a unified agreement management view with traditional practices. Summary of the invention

[0003] The purpose of the present invention is to provide a unified management method and system for banking business protocols, which clearly defines the parameters of protocol types. By abstracting the protocol model at the protocol registration level, a unified protocol standard model is formed. On the basis of the standard model, the management process is further unified. After adding a new protocol type, it is only necessary to define a new protocol-specific model and develop the registration of protocol-specific information without affecting the management process of the existing protocol.

[0004] In order to solve the above technical problems, the present invention provides a unified management method for banking business agreements, comprising the following steps:

[0005] Obtaining an agreement signing request; the agreement signing request includes an agreement type and agreement element information;

[0006] According to the protocol type, the protocol element information of the corresponding protocol signing request is converted into protocol model information; the protocol model information includes protocol main information and protocol specific information;

[0007] Register the protocol master information and protocol specific information.

[0008] Preferably, according to the protocol type, converting the protocol element information of the corresponding protocol signing request into the protocol model information specifically includes the following steps:

[0009] Get the common information model;

[0010] Obtaining the main agreement information from the agreement element information of the agreement signing request through the common information model;

[0011] Determine the unique business information model based on the protocol type;

[0012] The protocol-specific information is obtained from the protocol element information of the protocol signing request through the unique business information model.

[0013] Preferably, the general information model is used to uniformly define uniform feature information common to all protocol types;

[0014] The unique service information model is used to separately define the difference information between different protocol types.

[0015] Preferably, the unified characteristic information includes a description or explanation of the agreement, the effective start date of the agreement, the validity period of the agreement, the current status of the agreement, the signing date of the agreement, the signing agency of the agreement, the signing channel, and the signing operator or teller.

[0016] Preferably, the difference information includes a text message agreement, a financial management agreement and an agreed transfer agreement.

[0017] Preferably, before registering the protocol master information and the protocol specific information, the following steps are also included:

[0018] Conduct a legality check on the main and supplementary information of the agreement. Once the check is passed, register the main information and proprietary information of the agreement.

[0019] Preferably, registering the protocol master information and the protocol specific information specifically includes the following steps:

[0020] The protocol master information and protocol specific information are registered separately.

[0021] Preferably, the method further comprises the following steps:

[0022] After adding a new protocol type, define a corresponding protocol-specific model for the new protocol type.

[0023] Compared with the prior art, the present invention has the following beneficial effects:

[0024] The present invention utilizes the factory mode in software design mode and the basic object inheritance mode. The classification of protocol information and the process of classification registration are isolated and unified. When implementing multiple projects, only the differentiated implementation of the newly added protocol types needs to be paid attention to. There is no impact on the signing of existing agreements. The stability of system functions is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The specific implementation modes of the present invention are further described in detail below with reference to the accompanying drawings.

[0026] Figure 1 It is a flow chart of a unified management method of banking business agreements of the present invention. DETAILED DESCRIPTION

[0027] Many specific details are set forth in the following description to facilitate a full understanding of the present invention. However, the present invention can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present invention, so the present invention is not limited to the specific implementation disclosed below.

[0028] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0029] It should be understood that although the terms first, second, etc. may be used to describe various information in one or more embodiments of this specification, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0030] The present invention is further described in detail below in conjunction with the accompanying drawings:

[0031] The present invention provides a unified management method for banking business agreements, comprising the following steps:

[0032] Obtaining an agreement signing request; the agreement signing request includes an agreement type and agreement element information;

[0033] According to the protocol type, the protocol element information of the corresponding protocol signing request is converted into protocol model information; the protocol model information includes protocol main information and protocol specific information;

[0034] Register the protocol master information and protocol specific information.

[0035] Preferably, according to the protocol type, converting the protocol element information of the corresponding protocol signing request into the protocol model information specifically includes the following steps:

[0036] Get the common information model;

[0037] Obtaining the main agreement information from the agreement element information of the agreement signing request through the common information model;

[0038] Determine the unique business information model based on the protocol type;

[0039] The protocol-specific information is obtained from the protocol element information of the protocol signing request through the unique business information model.

[0040] Preferably, the general information model is used to uniformly define uniform feature information common to all protocol types;

[0041] The unique service information model is used to separately define the difference information between different protocol types.

[0042] Preferably, the unified characteristic information includes a description or explanation of the agreement, the effective start date of the agreement, the validity period of the agreement, the current status of the agreement, the signing date of the agreement, the signing agency of the agreement, the signing channel, and the signing operator or teller.

[0043] Preferably, the difference information includes a text message agreement, a financial management agreement and an agreed transfer agreement.

[0044] Preferably, before registering the protocol master information and the protocol specific information, the following steps are also included:

[0045] Conduct a legality check on the main and supplementary information of the agreement. Once the check is passed, register the main information and proprietary information of the agreement.

[0046] Preferably, registering the protocol master information and the protocol specific information specifically includes the following steps:

[0047] The protocol master information and protocol specific information are registered separately.

[0048] Preferably, the method further comprises the following steps:

[0049] After adding a new protocol type, define a corresponding protocol-specific model for the new protocol type.

[0050] The present invention provides a unified protocol management mechanism to help practitioners achieve unified management of the protocol information life cycle, and unified visualization management of protocol information is the main starting point and goal of this technical patent. The present invention conducts a unified analysis of the information characteristics of the protocol information, extracts the common elements of all protocol information, and performs unified model definition and encapsulation to achieve standardized management of basic protocol information. At the same time, with the help of technical means, it provides a classification definition of protocol-specific information to meet the embodiment and management of differentiated information of all protocols. In addition to the unified management of protocol information, how to quickly respond to new protocol requirements is also a technical purpose of the present invention. The idea of ​​factory mode + isolation implementation is adopted to classify and process protocol information, uniformly manage basic information, and implement differentiated implementation of classified protocol information, which realizes the classification isolation of each protocol and the unification of unified protocol processing flow.

[0051] In order to better illustrate the technical effect of the present invention, the present invention provides the following specific embodiments to illustrate the above technical process:

[0052] Example 1: A unified management method for banking business agreements, such as Figure 1 As shown, the following steps are included:

[0053] S101: receiving various agreement signing requests, where the agreement request includes agreement type and agreement element information;

[0054] S102: converting the sent protocol into a corresponding protocol model according to the protocol type, where the protocol model includes protocol main information and protocol specific information;

[0055] S103: Perform necessary legality checks on the converted protocol master information and protocol proprietary information;

[0056] S104: After the check is passed, the main information of the agreement is registered;

[0057] S105: Register the protocol-specific information to complete the management registration of this protocol type;

[0058] The main feature of the present invention is to use the object inheritance pattern in object-oriented design and the factory method pattern in the design pattern in object-oriented design.

[0059] At the business parameter level, all protocols are clearly defined with protocol type numbers. Each protocol number represents an actual protocol scenario in system processing.

[0060] In terms of business models, for each type of agreement, all agreement attributes are classified and summarized to form basic agreement information and differentiated agreement information. The agreement management within the bank is defined according to a unified standard. Basic agreement information is able to be separated from the specific content of the agreement type itself and has unified characteristics, such as: clear agreement type, agreement description or instructions, agreement effective start date, agreement validity period, agreement current status, agreement signing date, agreement signing agency, signing channel, signing operator or teller, etc.; these basic agreement information are uniformly defined to form a general agreement information model. Differential information of different agreements, such as SMS agreement, financial management agreement or agreed transfer agreement, each has unique agreement content. These agreement-specific information are defined separately at the model level of each agreement type to form a unique business information model of each agreement. The complete information model of different agreements is reflected by the inheritance of the agreement general information model by the agreement-specific business information model.

[0061] With the help of model splitting, all the information of all protocols is uniformly encapsulated and defined to form a general information model. Define the protocol models for the differentiated information of different protocols such as SMS and financial management protocols. General information model + unique business information model of each protocol = complete protocol information. When splitting the entity model, the main protocol + sub-protocol model can also be used to reflect the complete protocol information.

[0062] After the model definition is completed, a unified definition is also made for the management process of the agreement. The management cycle of an agreement includes the signing of the agreement, the modification of the agreement, and the termination of the agreement. All agreements take effect after they are signed, and may be modified during the effective period. The legal constraints of both parties to the agreement are lifted after the agreement is terminated. Therefore, the management process of the agreement is also uniformly packaged in the present invention. A unified protocol registration mode is provided. The problem of unified registration of protocol information between different protocols is realized. When adding a new protocol, you only need to focus on the development and implementation of differentiated content within the protocol. Standardized and unified processing is achieved at the protocol registration level.

[0063] In the several embodiments provided by the present invention, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules, modules or units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units, modules or components can be combined or integrated into another device, or some features can be ignored or not executed.

[0064] The units may or may not be physically separated, and the components displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0065] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0066] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part, and / or installed from a removable medium. When the computer program is executed by the central processing unit (CPU), the above-mentioned functions defined in the method of the present invention are executed. It should be noted that the above-mentioned computer-readable medium of the present invention can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, a system, device or device of an electrical, magnetic, optical, electromagnetic, infrared segment, or semiconductor, or any combination of the above.

[0067] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0068] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed by the present invention should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for unified management of banking business agreements, characterized in that: The following steps are involved: Obtaining an agreement signing request; the agreement signing request includes an agreement type and agreement element information; According to the agreement type, the agreement element information of the corresponding agreement signing request is converted into agreement model information; The protocol model information includes protocol main information and protocol specific information; Register the protocol master information and protocol specific information.

2. The unified management method of banking business agreements according to claim 1, characterized in that: According to the agreement type, the agreement element information of the corresponding agreement signing request is converted into the agreement model information, which specifically includes the following steps: Get the common information model; Obtaining the main agreement information from the agreement element information of the agreement signing request through the common information model; Determine the unique business information model based on the protocol type; The protocol-specific information is obtained from the protocol element information of the protocol signing request through the unique business information model.

3. The unified management method of banking business agreements according to claim 2, characterized in that: The general information model is used to uniformly define the uniform characteristic information possessed by all protocol types.

4. The method for unified management of banking business agreements according to claim 3, characterized in that: The unique service information model is used to separately define the difference information between different protocol types.

5. The method for unified management of banking service agreements according to claim 4, characterized in that: The unified characteristic information includes a description or explanation of the agreement, the effective start date of the agreement, the validity period of the agreement, the current status of the agreement, the signing date of the agreement, the signing agency of the agreement, the signing channel, and the signing operator or teller.

6. The method for unified management of banking business agreements according to claim 5, characterized in that: The difference information includes SMS agreement, financial management agreement and agreed transfer agreement.

7. The unified management method of banking business agreements according to claim 6, characterized in that: Before registering the protocol master information and protocol specific information, the following steps are also included: Conduct a legality check on the main and supplementary information of the agreement. Once the check is passed, register the main information and proprietary information of the agreement.

8. The unified management method of banking business agreements according to claim 7, characterized in that: The registration of the main information and the proprietary information of the agreement includes the following steps: The protocol master information and protocol specific information are registered separately.

9. The unified management method of banking business agreements according to claim 8, characterized in that: The following steps are also included: After adding a new protocol type, define a corresponding protocol-specific model for the new protocol type.

10. A unified management system for banking business agreements, used to implement the unified management method for banking business agreements as claimed in any one of claims 1 to 9, characterized in that: include: An acquisition module is used to obtain an agreement signing request; The protocol request includes protocol type and protocol element information; A conversion module, used to convert the protocol element information of the corresponding protocol signing request into protocol model information according to the protocol type; The protocol model information includes protocol main information and protocol specific information; The registration module is used to register the protocol main information and protocol specific information.

Images