National debt transaction system based on micro-service architecture

Abstract

The invention discloses a national debt transaction system based on a micro-service architecture. The transaction system comprises a bond information management module, a customer information management module, a transaction processing module and a batch task management module, the bond information management module is used for realizing full life cycle management of bonds; the customer information management module is used for managing customer information; the transaction processing module is used for processing various types of bond transactions; and the batch task management module is used for realizing management of timed tasks by adopting Control-M as a task scheduling tool. Management personnel can perform analysis based on the real-time data, dynamically adjust the national debt sales strategy, optimize resource configuration, ensure the transaction success rate and the market response speed, and solve the problem that the decision is lack of real-time data support.

Description

Technical Field

[0001] The present invention relates to the field of treasury bond business systems, and in particular to a treasury bond trading system based on a microservice architecture. Background Art

[0002] The current treasury bond business is integrated into the core business system as a submodule of the core business system and is developed using the RPG language. The syntax of this development language is relatively old and lacks rich advanced programming features. It also has high requirements for developers and requires a deep understanding of the AS / 400 hardware architecture, operating system features, and various resource management mechanisms. During the development process, developers need to carefully consider how to optimize the code to make full use of limited resources, such as memory, processor time, etc. They need to find appropriate algorithms and data structures to improve program performance and avoid resource exhaustion or slow operation. At the same time, this development method has difficulties in integrating with external systems, and its scalability is also limited, and it cannot respond to today's agile development methods in a timely manner.

[0003] The disadvantages of the prior art are as follows:

[0004] 1) Monolithic architecture, limited scalability. With the development and innovation of the treasury bond market, business needs are constantly changing and increasing. Some existing systems may not fully consider future scalability when they are designed, making it difficult to quickly adapt to new business models and products. For example, when a new type of treasury bond is launched or a new trading method is introduced, the system may not be able to support it directly, requiring large-scale transformation or even redevelopment, which affects the efficiency of business advancement.

[0005] 2) Manual bond management is inefficient, which is a significant problem of manual bond management. Processing large amounts of bond data, executing transactions, monitoring market dynamics, and conducting risk management tasks all require a lot of time and manpower, which not only increases operating costs, but may also result in missed market opportunities or inability to respond to risks in a timely manner due to insufficient processing speed.

[0006] 3) Data accuracy and consistency issues. Since the treasury bond business involves multiple participants and complex processes, errors or inconsistencies are prone to occur when data flows between different systems and links. For example, there may be differences between the transaction data in the trading system and the registration data in the custody system, which may be caused by loss during data transmission, repeated entry, or clock asynchrony between systems. This will affect the accurate recording of investors' rights and interests and the fairness of the market, and also bring difficulties to supervision.

[0007] 4) Transaction delays. During the peak period of treasury bond trading, especially when there are large-scale tender issuances or when the market fluctuates violently, the trading system may face greater pressure, resulting in delays in the processing and response of trading instructions. For example, investors' buy and sell orders cannot be executed in time, and they may miss the best trading opportunity, affecting market liquidity and investors' trading experience.

[0008] 5) The interface is not friendly enough. The operation interface design of some treasury bond business systems is relatively complex, not intuitive and user-friendly. For some non-professional investors or new users in the market, the learning and use costs are high. The system often provides relatively general services and cannot meet the personalized needs of different users. For example, different investors have different focuses and investment strategies for treasury bond information, but it is difficult for the system to provide customized information push and investment advice services based on the specific circumstances of users, which affects users' grasp of the market and the accuracy of investment decisions.

[0009] 6) System security and stability issues. As an important infrastructure of the financial market, the security and stability of the treasury bond business system are of vital importance. However, some existing systems are deficient in security protection and fault tolerance mechanisms and are vulnerable to hacker attacks, virus intrusions or system failures. Once a security incident or system crash occurs, it may lead to the loss of a large amount of bond data, transaction interruption or theft of funds, causing huge losses to investors and the market.

[0010] 7) Lack of intelligent and automated support. With the continuous development of financial technology, intelligence and automation have become important trends in the financial industry. However, some treasury bond business systems are still lagging behind in this regard, lacking intelligent data analysis, risk warning, and automated trading functions. This results in investors and financial institutions having to manually perform a lot of tedious operations and judgments when handling treasury bond business, which is not only inefficient but also prone to errors. At the same time, the lack of intelligent support also limits the potential for innovation and development of treasury bond business. Summary of the invention

[0011] In view of the above problems, the present invention is proposed to provide a treasury bond trading system based on a microservice architecture that overcomes the above problems or at least partially solves the above problems.

[0012] According to one aspect of the present invention, a treasury bond trading system based on a microservice architecture is provided, the trading system comprising: a bond information management module, a customer information management module, a transaction processing module and a batch task management module;

[0013] The bond information management module is used to implement the full life cycle management of bonds;

[0014] The customer information management module is used to manage customer information;

[0015] The transaction processing module is used to process various types of bond transactions;

[0016] The batch task management module is used to use Control-M as a task scheduling tool to achieve the management of scheduled tasks.

[0017] Optionally, the bond information management module is used to implement the full life cycle management of bonds and includes:

[0018] Bond issuance, quota allocation, business parameter maintenance, quota application qualification review, quota allocation, system status synchronization and book-entry bond quotation.

[0019] Optionally, the customer information management module is used to manage customer information and specifically includes:

[0020] It supports the opening of custody accounts, collection and replacement of custody books, upgrade of custody accounts, reporting loss and unblocking, freezing, payment suspension, account cancellation, information modification and password management.

[0021] Optionally, the transaction processing module is used to process various types of bond transactions and specifically includes:

[0022] Subscription, trading, early redemption, maturity redemption, fund freezing, non-transaction transfer, custody transfer and related inquiry services.

[0023] Optionally, the batch task management module is used to use Control-M as a task scheduling tool and specifically includes: end-of-day tasks and daytime scheduled tasks.

[0024] Optionally, the end-of-day tasks specifically include:

[0025] Automatically execute date switching to promote system status flow;

[0026] Automatically complete end-of-day processing and generate various business reports for management reference.

[0027] Optionally, the daytime scheduled tasks specifically include:

[0028] The system regularly monitors the bond data information issued by the Central Clearing Company to achieve fully automatic bond registration, quota allocation, and business parameter maintenance;

[0029] Daytime batch tasks, handling various businesses at agreed time;

[0030] Execute timed task flow compensation to ensure that all transaction processes are fully executed.

[0031] Optionally, the various types of business specifically include: sales data reporting, reconciliation data acquisition and synchronization of business outlets information.

[0032] The present invention provides a treasury bond trading system based on a microservice architecture, the trading system comprising: a bond information management module, a customer information management module, a transaction processing module and a batch task management module; the bond information management module is used to realize the full life cycle management of bonds; the customer information management module is used to manage customer information; the transaction processing module is used to process various types of bond transactions; the batch task management module is used to use Control-M as a task scheduling tool to realize the management of scheduled tasks. Managers can analyze based on real-time data, dynamically adjust treasury bond sales strategies, optimize resource allocation, ensure transaction success rate and market response speed, and solve the problem of lack of real-time data support for decision-making.

[0033] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.

[0035] Figure 1 A block diagram of a treasury bond trading system based on a microservice architecture provided by an embodiment of the present invention;

[0036] Figure 2 A flowchart of the purchase of book-entry treasury bonds provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0037] The exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to enable a more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

[0038] The terms "comprises" and "having" and any variations thereof in the description embodiments, claims and drawings of the present invention are intended to cover non-exclusive inclusions, for example, including a series of steps or units.

[0039] The technical solution of the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0040] A treasury bond trading system based on microservice architecture uses the Spring Cloud framework to build a microservice architecture. The overall architecture includes the following:

[0041] Registration Center: Use Nacos to provide service registration and discovery functions.

[0042] Configuration Center: Nacos is also used to achieve centralized management and dynamic refresh of configurations.

[0043] API Gateway: Use Spring Cloud Gateway, which is responsible for routing forwarding and request filtering.

[0044] DMZ Gateway: Establish a springboot application to interact with the central clearing company in real time and complete data reporting.

[0045] Distributed cache: Use Redis sentinel mode to provide highly available data caching services.

[0046] Distributed file processing: Use a combination of Oriental Connect and file DN to achieve distributed storage and processing of files.

[0047] Scheduled task scheduling: Use Control-M to schedule and control tasks.

[0048] Monitoring: Prometheus is used for data collection, and Grafana is used for data visualization.

[0049] Log collection and analysis: Use ELK Stack (Elasticsearch, Logstash, Kibana) to collect, store and analyze logs.

[0050] Front-end technology

[0051] Front-end framework: Vue.js, for building responsive and efficient user interfaces.

[0052] Backend Technology

[0053] Backend framework: Spring Boot, which provides the ability to quickly develop server-side applications.

[0054] Database Tier

[0055] Relational database: OceanBase, a high-performance database that supports large-scale data processing.

[0056] Non-relational database: Redis, used for caching and message storage.

[0057] Middleware layer

[0058] Logging: LogBack, for recording application logs.

[0059] Message queue: Kafka, for processing high-throughput real-time data streams.

[0060] Security

[0061] Security protocol: HTTPS and SSL / TLS certificates to ensure data transmission security.

[0062] Encryption technology: National encryption standards and signature server verification ensure data security and privacy.

[0063] Deployment and Operation

[0064] CI / CD tools: Jenkins and TFS, supporting continuous integration and continuous deployment.

[0065] Containerization technologies: Docker and Kubernetes, which improve the portability and scalability of applications.

[0066] Monitoring and logging

[0067] Monitoring tools: Prometheus and Grafana, used to monitor system performance in real time.

[0068] Log management: Elasticsearch, Logstash, and Kibana (ELK Stack) for collecting, storing, and analyzing log data.

[0069] Business services divided by bond type

[0070] This system has designed multiple independent service modules for different types of treasury bonds - electronic treasury bonds, book-entry treasury bonds and voucher treasury bonds, including functions such as bond management, customer management, transaction management and batch management. These service modules are deployed on different service nodes to ensure low coupling between services and improve the flexibility and scalability of the system. By dynamically adjusting the number of Pod nodes in the container cloud environment to optimize resource allocation, both service quality and effective use of server resources can be guaranteed.

[0071] like Figure 1 As shown, a treasury bond trading system based on microservice architecture includes:

[0072] The bond information management module realizes the full life cycle management of bonds, including bond issuance, quota allocation, business parameter maintenance, quota application qualification review, quota allocation, system status synchronization, book-entry bond quotation and other functions.

[0073] The customer information management module supports the opening of custody accounts, collection and replacement of custody books, custody account upgrades, reporting loss and unblocking, freezing, payment suspension, account cancellation, information modification, password management and other related functions.

[0074] The transaction processing module can handle various types of bond transactions, such as subscription, sale, early redemption, maturity redemption, fund freezing, non-transaction transfer, custody transfer and related query services.

[0075] The batch task management module uses Control-M as a task scheduling tool to implement the management of scheduled tasks.

[0076] End-of-day tasks include: automatically executing date switching to promote system status flow; automatically completing end-of-day processing and generating various business reports for management reference.

[0077] Daily scheduled tasks include: the system regularly monitors the bond data information issued by the Central Clearing Company to achieve fully automatic bond registration, quota allocation, and business parameter maintenance.

[0078] Daily batch tasks include completing various business processes at the agreed time, such as sales data reporting, reconciliation data acquisition, synchronization of business outlets information, etc.

[0079] Execute timed task flow compensation to ensure that all transaction processes are fully executed.

[0080] Business critical processes such as Figure 2 As shown:

[0081] Book-entry Treasury bond subscription purchase process;

[0082] Book-entry Treasury bond subscription purchase operation process

[0083] Verify business hours, bond information and account information

[0084] Before the transaction begins, the system will first verify whether it is within the time period allowed for trading, and confirm the validity of the selected bonds and relevant information of the customer account.

[0085] Reducing bond quotas

[0086] If the verification is correct, the corresponding number of bonds will be reduced from the available quota to reserve the purchase quota.

[0087] Freeze customer account funds

[0088] In order to ensure that the deduction amount is sufficient after the transaction is successful, the system will temporarily freeze the funds in the customer's account used for this purchase.

[0089] Send a third-party request to subscribe

[0090] The system will send a purchase request to the external trading partner to complete the purchase operation.

[0091] Processing return results

[0092] Depending on the response from the external trading system, the system will further process:

[0093] (1) Three-party failure

[0094] - If the external transaction fails, the system needs to do the following:

[0095] -Restore previously cut bond quotas.

[0096] - Unfreeze the funds in customer accounts.

[0097] (2) Three-party success

[0098] -If the external transaction is successful, the system needs to do the following:

[0099] -Insert transaction record into transaction details.

[0100] - Unfreeze the customer's account funds and carry out accounting processing.

[0101] (3) Over-the-counter transactions and re-registration of passbooks

[0102] -For over the counter transactions, it is also necessary to update the customer's passbook record after the transaction is successful.

[0103] Treasury bond result processing failed

[0104] If any abnormal situation occurs during the processing and the result processing fails, you need to do the following:

[0105] Send an alarm email to the designated mailbox to notify relevant personnel in time.

[0106] Submit the failed transaction to the Control-M task scheduling system and wait for the subsequent retry mechanism.

[0107] Through the above process, the security and accuracy of treasury bond subscription purchase operations can be ensured, while at the same time, various abnormal situations that may arise can be effectively dealt with to ensure that the user experience is not affected.

[0108] like Figure 1 As shown in the figure, the deployment architecture of the national debt business system is briefly described.

[0109] 1. Three-party system

[0110] Function: The three-party system provides basic business support for treasury bonds, including but not limited to treasury bond issuance, trading, redemption and other business functions.

[0111] Interaction: Communicate with the DMZ area of ​​the treasury project through a standardized interface to ensure the security and reliability of data transmission.

[0112] 2.DMZ area

[0113] Function: The DMZ area is an isolated area used to connect external systems (third-party systems) with the internal network environment.

[0114] composition:

[0115] Gateway: As the core component of the DMZ zone, the gateway is responsible for processing all data flows entering the internal network, implementing firewall rules, performing SSL / TLS offloading functions, and performing basic authentication.

[0116] Security protection: Implement strict security policies, including but not limited to IP address filtering, port scan detection, malware protection and other measures.

[0117] 3. Open Zone Network

[0118] Function: The open zone network is part of the internal network and is responsible for processing the core logic and services of the treasury bond business.

[0119] composition:

[0120] CTM task scheduling system: responsible for the scheduled task scheduling in the treasury bond business process, including periodic tasks such as maturity reminders and interest payments.

[0121] F5 load balancer: used to distribute requests from the DMZ area to the backend server cluster to ensure high availability and performance of the service.

[0122] Cryptographic verification module: performs encryption and decryption operations to ensure confidentiality and integrity during data transmission.

[0123] Treasury bond business related services:

[0124] Containerized deployment: Use Kubernetes (K8S) for containerized deployment to improve the portability and scalability of services.

[0125] Elastic scaling: Automatically adjust the number of service instances according to business needs to ensure high performance and high availability.

[0126] Microservice architecture: Certificate bond nodes, book-entry bond nodes and electronic bond nodes, each business node runs as an independent microservice for easy maintenance and upgrade.

[0127] Data processing: Real-time processing and analysis of treasury bond business data to support decision-making and risk assessment.

[0128] 4. Internal core system

[0129] Support functions: The internal core system is responsible for the accounting and user information management of treasury bond business.

[0130] 5. Data storage layer

[0131] Function: The data storage layer is responsible for storing key data and user information of treasury bond business.

[0132] composition:

[0133] Database: Stores business data and user information using a relational database

[0134] Redis cache: As a cache system, it is used to improve data access speed and reduce database pressure.

[0135] Beneficial effects: Provide an efficient, safe and reliable platform for processing treasury bond business. By dividing the system into multiple layers, effective isolation of external systems and efficient collaboration of internal systems are achieved. The layered design not only improves the security of the system, but also enhances the system's reliability.

[0136] The above specific implementation methods further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A treasury bond trading system based on microservice architecture, characterized in that: The trading system includes: a bond information management module, a customer information management module, a transaction processing module and a batch task management module; The bond information management module is used to implement the full life cycle management of bonds; The customer information management module is used to manage customer information; The transaction processing module is used to process various types of bond transactions; The batch task management module is used to use Control-M as a task scheduling tool to achieve the management of scheduled tasks.

2. According to claim 1, a treasury bond trading system based on microservice architecture is characterized in that: The bond information management module is used to implement the full life cycle management of bonds and includes: Bond issuance, quota allocation, business parameter maintenance, quota application qualification review, quota allocation, system status synchronization and book-entry bond quotation.

3. According to claim 1, a treasury bond trading system based on microservice architecture is characterized in that: The customer information management module is used to manage customer information and specifically includes: It supports the opening of custody accounts, collection and replacement of custody books, custody account upgrades, reporting loss and unblocking, freezing, payment suspension, account cancellation, information modification and password management.

4. According to claim 1, a treasury bond trading system based on microservice architecture is characterized in that: The transaction processing module is used to process various types of bond transactions and specifically includes: Subscription, trading, early redemption, maturity redemption, fund freezing, non-transaction transfer, custody transfer and related inquiry services.

5. According to claim 1, a treasury bond trading system based on microservice architecture is characterized in that: The batch task management module is used to use Control-M as a task scheduling tool and specifically includes: end-of-day tasks and daytime scheduled tasks.

6. According to claim 5, a treasury bond trading system based on microservice architecture is characterized in that: The end-of-day tasks specifically include: Automatically execute date switching to promote system status flow; Automatically complete end-of-day processing and generate various business reports for management reference.

7. According to claim 5, a treasury bond trading system based on microservice architecture is characterized in that: The daytime scheduled tasks specifically include: The system regularly monitors the bond data information issued by the Central Clearing Company to achieve fully automatic bond registration, quota allocation, and business parameter maintenance; Daytime batch tasks, handling various businesses at agreed time; Execute timed task flow compensation to ensure that all transaction processes are fully executed.

8. According to claim 7, a treasury bond trading system based on microservice architecture is characterized in that: The various types of business specifically include: sales data reporting, reconciliation data acquisition and synchronization of business outlets information.

Images