A unified account management system based on customer center

Abstract

The present invention discloses a unified account management system based on customer center, which helps futures companies to transform towards intelligent digitalization, proposes process digitization, intelligent business handling, and automated handling solutions from channels to counter business, so as to reduce the burden on business personnel. Its technical solution is as follows: The system of the present invention proposes a system method centered on customers, with multiple types of accounts as the entry point, and focusing on account services: in the customer dimension, a unified account layer is established, and data uniqueness aggregation is completed by collecting customer public information, archival information and suitability information. On the basis of the unified account, the futures account layer, stock option account layer, fund account layer, securities account layer and user layer are expanded to achieve intelligent and digital management of various types of customer accounts. At the same time, the system provides a unified standardized open service interface to help the service system run through and the entrance is normalized.

Description

Technical Field

[0001] The present invention relates to an account system applied in the field of financial software, and in particular to a unified account management system based on a customer center. Background Art

[0002] In recent years, the domestic financial market has flourished, and the products of trading targets have been continuously enriched, showing a development trend of product expansion and opening up to the outside world. Futures companies have also begun to transform from traditional business services to new business operation models such as investment consulting, asset management and wealth management. Futures companies need to maintain existing customers while expanding new customers. Their strategic goals have changed from product-centric to customer-centric. In the era of big data and artificial intelligence, how to improve customer satisfaction, how to manage customers, and maximize the use of customer data resources and convert them into revenue have become major strategic goals for futures companies. Futures companies must combine their own advantages, establish strategic development goals, and build core competitiveness.

[0003] at the same time, Figure 1 shows the gap between service requirements and current operational status, as Figure 1 As shown in the figure, the business entrances of futures companies are scattered, different business systems coexist, and the same business is operated by multiple systems, resulting in many repeated operations and fragmented processes. In addition, customer data is scattered in different systems, lacking uniqueness and correctness, data is repeated and fragmented, and the degree of digitization and openness is insufficient.

[0004] In today's highly developed Internet era, driven by the Internet, big data, and artificial intelligence, the traditional business processing system can no longer meet the growing service requirements. The financial circle is in urgent need of reform, and futures companies are looking forward to digital transformation. As capital accounts are a necessary condition for on-site transactions, the market urgently needs intelligent account management systems.

[0005] Figure 2 It shows the operating platform currently used by futures companies. Futures companies have multiple systems coexisting, such as archive systems, suitability systems, anti-money laundering systems, futures counters, and stock options counters. Account information and customer data information coexist in multiple systems, information maintenance is inconsistent, and customer information is repeatedly entered in multiple places; it is not open enough. After the introduction of the unified account, archives, suitability, and business processing are all carried out in the unified account to ensure the uniqueness and strong consistency of information. In addition, the unified account connects to futures counters, stock options counters, seats, and peripheral systems through open interfaces / views, etc., providing a unified data entry and exit. Among them, the open interface will be forwarded after gateway authentication. Summary of the invention

[0006] A brief summary of one or more aspects is given below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its only purpose is to give some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0007] The purpose of the present invention is to solve the above problems and provide a unified account management system based on customer center to help futures companies transform towards intelligent digitalization, propose process digitization, intelligent business handling, and automated handling solutions from channels to counter business, thereby reducing the burden on business personnel.

[0008] The technical solution of the present invention is as follows: The present invention discloses a unified account management system, which adopts a microservice architecture to achieve decoupling between various subsystems in the system. The system includes an account service subsystem, a unified account opening service subsystem, and a cloud account opening service subsystem, wherein:

[0009] The account service subsystem includes the account service front end, account service back end, and data layer.

[0010] The account service front-end adopts a distributed architecture, develops front-end and back-end interaction interfaces based on the Http interface, and builds the user interface based on the vueelementui progressive framework.

[0011] The account service backend is encapsulated into the Wukong framework based on the open source Spring Boot framework. The account service adopts the Spring MVC architecture mode. Visual operations are performed on the data at the account service frontend. The Http request of the account service frontend is forwarded to the account service backend through the server's proxy forwarding configuration. The account service backend authenticates the request and transmits the authenticated request to the service layer. The service layer processes the business logic and performs data persistence operations on the processing results of the business logic at the data access layer. The heterogeneity between the database and the program is realized through object-relational mapping. The account service backend interacts with the unified account service subsystem through encapsulated internal services and interacts with the external open counter through the message bus.

[0012] Unified account opening service subsystem: Account service sends a report to the account opening interface of the unified account opening service. The account opening interface processes the request for reporting from the account service subsystem, interacts with the monitoring center and processes the business corresponding to the report request. At the same time, it operates on the data layer. The unified account opening service subsystem also processes the response data from the monitoring center and performs logical processing based on the response data.

[0013] The cloud account opening service subsystem is used to provide online personal account opening solutions.

[0014] According to an embodiment of the unified account management system of the present invention, the distributed architecture adopted by the account service front end is the cap-leo architecture, and the encapsulation of the Http protocol into the account protocol interface is completed by the cap-leo architecture based on the skylark architecture using Java reflection technology.

[0015] According to an embodiment of the unified account management system of the present invention, the cap-leo architecture also provides log service, message service, and transaction service.

[0016] According to an embodiment of the unified account management system of the present invention, the account service backend performs permission authentication on the request by developing a permission authentication microservice provided by the counter.

[0017] According to an embodiment of the unified account management system of the present invention, during the authorization authentication of the request by the account service backend, the request that fails the authentication is returned to the account service frontend, and the account service frontend redirects the request to the service login interface for login verification.

[0018] According to an embodiment of the unified account management system of the present invention, in the processing of the business logic of the service layer, data consistency is ensured through transactions, and the execution process is printed through the log section service.

[0019] According to an embodiment of the unified account management system of the present invention, the data access layer performs data persistence operations on the processing results of the business logic through the MyBatis framework. The data persistence operation adopts Oracle active-active and Redis cluster solutions in the data layer, and Oracle data adopts hot backup.

[0020] According to an embodiment of the unified account management system of the present invention, the account service backend also integrates multiple types of caches to improve the speed of request response.

[0021] According to an embodiment of the unified account management system of the present invention, the account service of the Spring MVC architecture mode is divided into a view layer, an access layer, a service layer, a data layer and middleware, wherein:

[0022] View layer, providing visual account service operations;

[0023] The access layer is developed using the Spring Boot framework and is configured with Gson serialization, operation permission control, data permission control, log aspect, and cache functions to provide consistent serialization processing, permission control, and cache for all requests from the view layer.

[0024] The service layer configures the functions of services, controllers, mappers, Mybatis, Redis, and logs. The service layer is used to perform business logic processing and data operations on single request data. A single request is distributed to the corresponding service or controller through the interface of the service layer. The service and controller process the corresponding business logic, and synchronize the data of the business logic processing results through the mapper;

[0025] The data layer is used to display the data storage media in the unified account service subsystem, where the data storage media include Oracle database, Redis cache, and file storage. The database is used to persistently store data information, Redis stores timeliness information including login tokens, and file storage is used to store archive file data;

[0026] The middleware uses the persistence layer framework Mybatis to manipulate the Oracle database, uses the Redis middleware to store time-effectiveness information, and uses the log aspect service to track the software execution process and store it in the log file and console.

[0027] According to an embodiment of the unified account management system of the present invention, the business handling process configured in the unified account opening service subsystem includes:

[0028] The unified account opening service subsystem connects to the monitoring center through the JnaCfmmcLibrary plug-in and logs in to report the user; after the initial reporting preparation is completed, it waits for the reporting request from the account service subsystem;

[0029] The account service subsystem requests reporting when handling business that needs to be reported. The account service subsystem calls the unified account opening service subsystem through internal services. The unified account opening service subsystem obtains data from the Oracle database based on the called parameters, generates an XML file to be reported based on the obtained data, and sends the XML file to the monitoring center;

[0030] The monitoring center feeds back the parsing result of the XML file. If the parsing fails, the reporting record is updated;

[0031] After processing the reported XML file, the monitoring center returns an XML response file. The unified account opening service subsystem parses the XML response file and performs persistent data updates.

[0032] According to one embodiment of the unified account management system of the present invention, the cloud account opening service subsystem adopts the SpringBoot / Spring MVC architecture, the data persistence storage adopts Oracle and Redis cluster solutions, the database is operated through the Mybatis framework, transaction control and log aspect services are provided, the service interface is called by request, and the service interface operates the database through the data access layer. The cloud account opening service subsystem also communicates with the account service subsystem through internal services.

[0033] According to an embodiment of the unified account management system of the present invention, the operation process of the cloud account opening service subsystem configuration includes:

[0034] The business request first passes through the central scheduler, which obtains the processor execution chain through the processor mapper;

[0035] The processor execution chain finds the processor controller corresponding to the business request through the processor adapter;

[0036] After receiving the business request, the processor controller first checks the input parameters. After the verification is passed, it calls the service interface to process the business request and performs persistence processing on the Oracle data through the data access layer. If the business request needs to be reported, the cloud account opening service subsystem calls the account service subsystem through the internal service interface, and the account service subsystem reports the business request.

[0037] Compared with the prior art, the present invention has the following beneficial effects: the present invention provides a unified account solution for normalizing customer data and automating service processes. A system approach centered on customers and taking multiple types of accounts as entry points, focusing on services: in the customer dimension, a unified account layer is established, and data uniqueness aggregation is completed by collecting customer public information, archival information and suitability information. On the basis of the unified account, the futures account layer, stock option account layer, fund account layer, securities account layer and user layer are expanded to achieve intelligent and digital management of various types of customer accounts. At the same time, the system provides a unified standardized open service interface to help the service system run through and the entrance be normalized.

[0038] Specifically, the innovations of the present invention are in the following aspects:

[0039] 1. Data center, unified view of customer information. The unified account is customer-centric, with multiple types of accounts as the entry point. It is an account management middle-end application centered on services, connecting futures accounts, stock options accounts, fund accounts and securities accounts, and providing one-stop account management services. At the same time, it integrates customer data to form a customer data middle-end to promote the digital transformation of futures companies.

[0040] 2. Automated and intelligent business processes. From channels to counter business, through process reengineering, the counter is connected, data is automatically acquired, automatically checked, and the process is automatically processed. The process configuration is simple to operate and has strong scalability, which reduces the labor cost of the enterprise and improves the efficiency of business handling.

[0041] 3. Unified authority control. The system of the present invention adopts a unified authority control method to centrally manage data authority and operation authority, solve the problem of inconsistent authority and multiple settings in various subsystems of futures companies, standardize authority management, ensure data security, and improve the processing efficiency of technical personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The above features and advantages of the present invention can be better understood after reading the detailed description of the embodiments of the present disclosure in conjunction with the following drawings. In the drawings, the components are not necessarily drawn to scale, and components with similar related properties or features may have the same or similar reference numerals.

[0043] Figure 1 Schematic diagram showing the contradiction between futures companies' service requirements and the current insufficient digital service provision capabilities.

[0044] Figure 2 A schematic diagram showing the comparison of futures companies' operating platforms before and after the introduction of unified accounts.

[0045] Figure 3 A schematic diagram of the system architecture of an account service subsystem of an embodiment of a unified account management system based on a customer center of the present invention is shown.

[0046] Figure 4 A schematic diagram of the system level of the account service subsystem of the customer-centric unified account management system of the present invention is shown.

[0047] Figure 5 A schematic diagram showing the functional design of the account service subsystem in the customer-centric unified account management system of the present invention.

[0048] Figure 6 A schematic diagram showing the data model hierarchy of unified account data in the account service subsystem of the customer-centric unified account management system of the present invention is shown.

[0049] Figure 7 A schematic diagram showing data authority control in an account service subsystem of a unified account management system based on a customer center of the present invention is shown.

[0050] Figure 8 A schematic diagram of business process configuration in an account service subsystem of a unified account management system based on a customer center of the present invention is shown.

[0051] Fig. 9 The present invention shows a schematic diagram of the process of three nodes (handling post, review post, and audit post) by taking the account opening application business as an example.

[0052] Fig.10 A schematic diagram showing the system architecture of a unified account opening service subsystem of a unified account management system based on a customer center of the present invention.

[0053] Fig.11 A schematic diagram showing the business processing sequence of the unified account opening service subsystem of the customer-centered unified account management system of the present invention.

[0054] Fig.12 A schematic diagram showing the system architecture of the cloud account opening service subsystem of the customer-centered unified account management system of the present invention is shown.

[0055] Fig.13 A schematic diagram showing the operation process of the cloud account opening service subsystem of the unified account management system based on the customer center of the present invention. DETAILED DESCRIPTION

[0056] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. Note that the aspects described below in conjunction with the accompanying drawings and specific embodiments are only exemplary and should not be construed as limiting the scope of protection of the present invention in any way.

[0057] The unified account management system of the present invention adopts a microservice architecture. The microservice architecture decouples the subsystems in the system by decomposing the functions into discrete services. In the microservice architecture, the unified account management system of the present invention is functionally decomposed into account services ( account_center ) subsystem, unified account opening service (open_account) subsystem and cloud account opening service (account_cloud) subsystem.

[0058] Figure 3 The structure of the account service subsystem of the unified account management system based on the customer center of the present invention is shown. Figure 3As shown, the account service subsystem adopts B / S architecture, which is divided into account service front-end, account service back-end and data layer. Account service provides log service, message service, transaction service, etc. The account service front-end uses the progressive framework JavaScript framework Vue.js to build the user interface, uses Element-UI (a desktop component library) and encapsulates it into the account common component FIP-UI (FipGridPage, FipButton, etc.) to achieve the adaptive layout of the front-end interface and enable the table to support advanced search. The overall project of the account service subsystem runs on Node.js, uses event-driven, non-blocking I / O model, and manages modules through NPM (Node Package Manager, Node.js package manager). The code is packaged by WebPack (WebPack is a front-end resource loading / packaging tool) packager and put into Linux Apache server for running.

[0059] The account service backend uses Java language. The account service backend is encapsulated into Wukong framework based on the Spring Boot framework of the open source solution. The account service subsystem is embodied in the Spring MVC (Model View Controller) architecture mode. The account service frontend performs view visualization operations on the data. The Http request of the account service frontend is forwarded to the account service backend through the proxy forwarding (Proxy Pass) configuration of LinuxApache. The account service backend performs authorization authentication on the request by integrating uum (uum is the authorization authentication microservice provided by the development counter). Requests that fail to pass the authentication will be returned to the account service frontend. The account service frontend redirects the request to the uapcm (uapcm is the login microservice provided by the external development counter) service login interface for login verification. Requests that pass the authentication will be transmitted to the service interface (Service API). The service interface processes the business logic, and then the MyBatis framework is used to persist the data of the processing results of the business logic in the Dao (Data Access Object) layer as the data access layer. The heterogeneity between the database and the program is solved through object relational mapping (Object Relational Mapping, referred to as ORM). In the processing of the service interface, data consistency is guaranteed through transactions, and the log aspect service LogAspect prints the execution process. The account service backend integrates spring cache, ehcache, shiro-cache, and data memory cache to improve request response speed. The data persistence operation uses Oracle dual-active and Redis cluster solutions in the data layer, and the Oracle database is set up for hot backup. At the same time, the account service backend also interacts with the unified account opening service through the encapsulated internal service (Internal Service) and interacts with the external open counter through the message bus.

[0060] Figure 4 The system level of the unified account management system based on the customer center of the present invention is shown. Figure 4 As shown in the figure, the account service using Spring MVC architecture mode is divided into view layer, access layer, service layer, data layer and middleware.

[0061] The view layer provides visual account service operations, which can be used for customer information query, account information query, opening unified account, opening futures account, suitability assessment and other operations. The view layer uses Vue to build the user interface, and encapsulates it into the account general component FIP-UI (FipGridPage, FipButton, etc.) based on the component Element-UI to achieve the adaptive layout of the front-end interface, and the table supports advanced search. The entire project runs on Node.js, using an event-driven, non-blocking I / O model, and manages modules packages through the NPM tool. The code is packaged into static resources using WebPack and put into the Apache server for running.

[0062] The access layer is developed using the spring-boot framework, which mainly includes Gson serialization, operation permission control, data permission control, log aspect, cache and other functions. It is mainly used to provide consistent serialization processing, permission control and caching for all requests of the view layer.

[0063] The service layer includes service, controller, mapper, Mybatis (an open source project of Apache, a persistence layer framework), Redis (a data structure server), log, etc. The main function of the service layer is to perform business logic processing and data operations on single request data. The request is distributed to the corresponding service or controller through the service interface (ServiceAPI). The service and controller perform corresponding business logic processing. Based on the business logic processing results, the mapper performs data synchronization on these data operations.

[0064] The data layer shows the data storage media in the unified account service. The unified account mainly uses three storage media: Oracle database, Redis cache, and file storage (File). The database is used to persist table data information, Redis stores time-sensitive information such as login tokens (Token), and files are used to store data such as archive files. The above three storage media are used together.

[0065] In addition, the present invention also adopts many middlewares to efficiently and flexibly develop the account system, adopts the persistence layer framework Mybatis to flexibly manipulate the Oracle database, uses Redis middleware to store timeliness information, and uses LogAspect log aspect service to track the software execution process and store it in log files and consoles.

[0066] Figures 2 to 4 It explains the account service subsystem of the unified account management system at the level of specific technical implementation. Figure 5This section explains the functional design of the account service subsystem. The functions of the account service subsystem include: open interface, basic data configuration, customer information management, customer business information management, account management, archive business, appropriate business and authority control.

[0067] Basic data configuration further includes: company management, file management, department management, questionnaire management, process management, employee management, business configuration management, and account opening parameter management.

[0068] Customer information management further includes: customer management and bank account management.

[0069] Customer business information management further includes: single customer inquiry, customer questionnaire management, and customer file inquiry.

[0070] Account management further includes: futures layer, stock options layer, fund layer, and securities layer.

[0071] Permission control includes data permissions and operation permissions.

[0072] In the above-mentioned account management, the unified account management system is customer-centric for unified account data, designs a customer-level basic customer model, and highly refines customer account public information data. Figure 6 As shown, an asset account layer is set under the customer layer for storing various types of account-side information such as futures asset accounts, stock option accounts, fund accounts, securities accounts, etc., and a system account layer for user-side information is set under the futures asset accounts.

[0073] In the above Figure 5 The open interface shown provides a standardized restful interface for external systems to use. The external system first logs in through the gateway (Femas_Gateway), obtains a token, and then authenticates through the gateway. The gateway adds user information to the request header and forwards the updated Http request to the open interface of the account service. The open interface processes the logic corresponding to the Http request, performs Oracle persistence operations on the data, and returns the processing results of the Http request to the external system.

[0074] In terms of process management, we configure business processes for opening unified accounts, opening futures accounts, etc., and circulate them according to the configured business processes. Figure 8As shown: The business configuration unit will perform process configuration, file configuration, suitability configuration, and form configuration. The process configuration is mainly used to configure business flow nodes and node permissions. The file configuration and suitability configuration are used to configure the file information and suitability information required for business processing. The form configures the flow form for business processing. At the same time, the business configuration unit also provides matching control and status control, and performs targeted personalized matching control and status control as well as business flow according to different customer information (region, type, risk registration). When entering the business processing portal on the home page, the configuration information in the business configuration unit is matched according to the customer information (region, type, risk registration), and the files and questionnaires are collected according to the matched configuration information, and the business flow is carried out according to the process.

[0075] Fig. 9 The figure shows a flow diagram of the business process of three nodes (handling post, review post, and audit post) using the account opening application business as an example. Fig. 9 As shown in the figure, the handling post collects account opening information and submits an account opening application. After the review post logs into the system, there will be a pending review to review the completeness and appropriateness of the account opening application materials. If the review fails, it will be sent back to the handling post. After the review passes, the account opening process will flow to the review post. If the review fails, it will be sent back to the review post. If the review passes, the transaction code submission and other subsequent operations will be carried out. The account service provides a temporary storage function to save the information in the business flow process in a temporary table. Data persistence is implemented only after the review post passes the review.

[0076] Figure 3 The implementation scheme of the operation permissions of the access layer shown in is as follows: menu permission control and button permission control are realized by connecting with the microservice uum (uum is the permission control microservice provided by the development counter).

[0077] Figure 3The data permissions of the access layer shown in the figure are implemented as follows: Currently, the unified account controls data permissions in four ways: a) Associating operators with organizational structures: If an operator is associated with an organizational structure, the operator can obtain customer data permissions under the customer's department equal to the organizational structure node; b) Associating operators with a single customer: If an operator is directly associated with a single customer, the operator can directly obtain the customer's data permissions; c) Operators and customers join customer relationship groups. If an operator and a customer are in the same customer relationship group, the operator can obtain the customer's data permissions. It can be many-to-many, that is, multiple operators correspond to multiple customers; d) Encrypted customers are managed separately: If a customer is an encrypted customer and an operator is associated with the encrypted customer, the operator can obtain the encrypted customer's data permissions. The account service front end provides a permission setting page, which can set user department permissions, account permissions, customer permissions, and set encrypted customers. The account service back end performs data control on the business query SQL according to the set permissions. The process is as follows Figure 7 As shown: The unified account service subsystem provides business services, data permission services, and query services. The basic services include basic query services, query table parameter splicing, import and export, and other basic services, providing dynamic SQL parameter query, data import and export and other basic functions. The data permission service includes permission business data cache, operators, permission rule logic unit, and permission SQL splicer. The front-end data query request first passes through the business service to obtain the business service SQL and operator. The data permission service obtains the data permission list corresponding to the operator and inputs the permission list into the permission rule logic unit for permission calculation. The SQL splicer splices the original SQL with the permission list to form an SQL with data permission control. Executing this SQL can obtain the data within the operator's permission range.

[0078] The functions to be completed by the unified account opening service subsystem are as follows: the unified account includes the application of transaction code business, the cancellation of transaction code business, the modification of identity information business, the modification of general information business, the exchange account opening report, the exchange account cancellation report, the supplementary report of standard information business, the lifting of position opening restrictions business, the transaction authority report business, the account dormancy business and the activation of dormant account business, etc. These business operations need to be reported to the monitoring center and further processed according to the information returned by the monitoring center. The unified account opening service subsystem is used to process these business reports to the monitoring center and receive the information returned by the monitoring center.

[0079] The architecture of the unified account opening service subsystem is as follows Fig.10As shown in the figure. The unified account opening service subsystem adopts the Spring Boot architecture. The account service subsystem sends reports to the account opening interface (Open Account API) of the unified account opening service subsystem. The account opening interface processes the request for application reporting by the account service subsystem, interacts with the monitoring center through the JnaCfmmcLibrary plug-in provided by the monitoring center and processes the reported business. At the same time, Mybatis is used to operate Oracle data. The unified account opening service subsystem also needs to process the response data of the monitoring center and perform logical processing based on the response data.

[0080] Fig.11 The figure shows the business processing sequence of the unified account opening service subsystem. Fig.11 As shown, the business processing procedures of the unified account opening service subsystem are as follows.

[0081] The unified account opening service subsystem first connects to the monitoring center reporting program through the JnaCfmmcLibrary plug-in and logs in as a reporting user. After the initial reporting preparation is completed, it waits for the account service subsystem to report. When handling a business that needs to be reported, the account service subsystem requests reporting. The account service subsystem calls the unified account opening service subsystem through the internal service. The unified account opening service subsystem obtains data from the Oracle database based on the calling parameters, generates an xml file to be reported based on the acquired data, and sends the xml file to the monitoring center. The monitoring center first feeds back the parsing result of the xml file, and updates the reporting record if the parsing fails. After processing the reported xml file, the monitoring center returns an xml response file. The unified account opening service subsystem parses the xml response file and updates the data persistently.

[0082] The cloud account opening service subsystem provides online personal account opening solutions, including verifying customer identity, obtaining SMS verification code, verifying SMS verification code, obtaining account status, querying customer information, querying the latest customer suitability information, obtaining capital account, investor minimum risk level, opening an account, adding a transaction code, data modification-ID card validity period modification, data modification-mobile phone number, data modification-other information, saving suitability assessment results, ID card validity period, querying exchange information where the account has been successfully opened, obtaining bank and futures account information, and saving bank and futures account information, a total of 18 interfaces.

[0083] Fig.12 The system architecture of the cloud account opening service subsystem is shown in FIG. Fig.12As shown in the figure, the cloud account opening service subsystem adopts Spring Boot / Spring MVC architecture, and the data persistence storage adopts Oracle and Redis cluster solutions. The database is operated through the Mybatis framework. At the same time, the system provides transaction control and log aspect services. The request calls the service interface (Service API), and the service interface operates the database through the Dao layer to process data. At the same time, the cloud account opening service subsystem also communicates with the account service subsystem through the internal service (Internal Service).

[0084] Fig.13 The operation process of the cloud account opening service subsystem is shown in FIG. Fig.13 As shown in the figure, online personal accounts conduct account opening and suitability business through the API SDK or webpage provided by the monitoring center, and the business backend accesses the cloud account opening service subsystem through Http request to process the corresponding account opening and suitability business. The specific process of the request is as follows: the request first passes through the central dispatcher (Dispatch Servlet), the central dispatcher obtains the processor execution chain through the processor mapper (Handle Mapping), the processor execution chain finds the processor controller (Controller) corresponding to the request through the processor adapter (Handle Adapter), after the processor controller receives the request, it first checks the input parameters, and after the check passes, calls the service interface (Service API) to process the request, and performs persistence processing on Oracle data through the Dao layer. If the requested business needs to be reported, the cloud account opening service subsystem calls the account service subsystem through the internal service (Internal Service) API, and the account service subsystem reports the requested business.

[0085] Although the above methods are illustrated and described as a series of actions for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but understandable to those skilled in the art.

[0086] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the present invention.

[0087] The various illustrative logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration.

[0088] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0089] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented as a computer program product in software, each function may be stored on a computer-readable medium or transmitted through the computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically, while disc reproduces data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0090] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A unified account management system based on a customer center, characterized in that: The microservice architecture is used to achieve decoupling between the various subsystems in the system. The system includes the account service subsystem, the unified account opening service subsystem, and the cloud account opening service subsystem, among which: The account service subsystem includes the account service front end, account service back end, and data layer. The account service front-end adopts a distributed architecture, develops front-end and back-end interaction interfaces based on the Http interface, and builds the user interface based on the VueElementUI progressive framework; The account service backend is encapsulated into the Wukong framework based on the open source Spring Boot framework. The account service adopts the Spring MVC architecture mode. Visual operations are performed on the data at the account service frontend. The Http request of the account service frontend is forwarded to the account service backend through the server's proxy forwarding configuration. The account service backend authenticates the request and transmits the authenticated request to the service layer. The service layer processes the business logic and performs data persistence operations on the processing results of the business logic at the data access layer. The heterogeneity between the database and the program is realized through object-relational mapping. The account service backend interacts with the unified account service subsystem through encapsulated internal services and interacts with the external open counter through the message bus. Unified account opening service subsystem: the account service sends a request to the monitoring center to the internal call interface of the unified account opening service. The internal call interface processes the request submitted by the account service subsystem, interacts with the monitoring center, generates corresponding XML files for different businesses, and sends them to the monitoring center. At the same time, it operates on the data layer. The unified account opening service subsystem also processes the response data from the monitoring center and performs logical processing based on the response data. The cloud account opening service subsystem is used to provide online individual account opening solutions; Among them, the account service of Spring MVC architecture mode is divided into view layer, access layer, service layer, data layer and middleware, among which: View layer, providing visual account service operations; The access layer is developed using the Spring Boot framework and is configured with Gson serialization, operation permission control, data permission control, log aspect, and cache functions to provide consistent serialization processing, permission control, and cache for all requests from the view layer. The service layer configures the functions of services, controllers, mappers, Mybatis, Redis, and logs. The service layer is used to perform business logic processing and data operations on single request data. A single request is distributed to the corresponding service or controller through the interface of the service layer. The service and controller process the corresponding business logic, and synchronize the data of the business logic processing results through the mapper; The data layer is used to display the data storage media in the unified account service subsystem, where the data storage media include Oracle database, Redis cache, and file storage. The database is used to persistently store data information, Redis stores timeliness information including login tokens, and file storage is used to store archive file data; The middleware uses the persistence layer framework Mybatis to manipulate the Oracle database, uses the Redis middleware to store time-effectiveness information, and uses the log aspect service to track the software execution process and store it in the log file and console.

2. The unified account management system according to claim 1, characterized in that: The distributed architecture used by the account service front end is the cap-leo architecture. Encapsulating the Http protocol into the account protocol interface is accomplished by the cap-leo architecture based on the Skylark architecture using Java reflection technology.

3. The unified account management system according to claim 2, characterized in that: The cap-leo architecture also provides log services, message services, and transaction services.

4. The unified account management system according to claim 1, characterized in that: The account service backend performs authorization authentication on requests by developing the authorization authentication microservice of the counter system.

5. The unified account management system according to claim 4, characterized in that: The account service backend performs authorization authentication on the request. Requests that fail authentication are returned to the account service frontend, which redirects the request to the service login interface for login verification.

6. The unified account management system according to claim 5, characterized in that: In the processing of business logic in the service layer, data consistency is ensured through transactions, and the execution process is printed through the log section service.

7. The unified account management system according to claim 6, characterized in that: The data access layer uses the MyBatis framework to persist the results of business logic processing. The data persistence operation uses Oracle active-active and Redis cluster solutions in the data layer, and Oracle data uses hot backup.

8. The unified account management system according to claim 7, characterized in that: The account service backend also integrates multiple types of caches to improve the speed of request response.

9. The unified account management system according to claim 8, characterized in that: The business handling procedures configured in the unified account opening service subsystem include: The unified account opening service subsystem connects to the monitoring center through the JnaCfmmcLibrary plug-in and logs in to report the user; after the initial reporting preparation is completed, it waits for the reporting request from the account service subsystem; The account service subsystem requests reporting when handling business that needs to be reported. The account service subsystem calls the unified account opening service subsystem through internal services. The unified account opening service subsystem obtains data from the Oracle database based on the called parameters, generates an XML file to be reported based on the obtained data, and sends the XML file to the monitoring center; The monitoring center feeds back the parsing result of the XML file. If the parsing fails, the reporting record is updated; After processing the reported XML file, the monitoring center returns an XML response file. The unified account opening service subsystem parses the XML response file and performs persistent data updates.

10. The unified account management system according to claim 9, characterized in that: The cloud account opening service subsystem adopts the Spring Boot / Spring MVC architecture, and uses Oracle and Redis cluster solutions for data persistence storage. It operates the database through the Mybatis framework, provides transaction control and log aspect services, and requests to call the service interface. The service interface operates the database through the data access layer. The cloud account opening service subsystem also communicates with the account service subsystem through internal services.

11. The unified account management system according to claim 10, characterized in that: The operation process of the cloud account opening service subsystem configuration includes: The business request first passes through the central scheduler, which obtains the processor execution chain through the processor mapper; The processor execution chain finds the processor controller corresponding to the business request through the processor adapter; After receiving the business request, the processor controller first checks the input parameters. After the verification is passed, it calls the service interface to process the business request and performs persistence processing on the Oracle data through the data access layer. If the business request needs to be reported, the cloud account opening service subsystem calls the account service subsystem through the internal service interface, and the account service subsystem reports the business request.

Images