Financial asset dynamic expansion method and device, medium and product
By building a dynamic expansion framework for financial assets, the configuration files and bridge modes are used to solve the problem of high repetitive development and maintenance costs in the asset management system, and the dynamic expansion and stability of financial assets are achieved.
Patent Information
- Application Number
- CN202510409325.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-02
- Publication Date
- 2025-07-29
AI Technical Summary
When handling financial assets, existing asset management systems have problems such as overlapping functions of the same/similar behavior, high maintenance costs and error-prone, making it difficult to effectively avoid duplicate development.
By defining asset configuration files and asset operation configuration files, a dynamic expansion framework for financial assets is built, and a bridge model is used to transfer asset operation behavior to the same name method of the asset execution interface to achieve dynamic expansion of financial assets.
Effectively avoid duplicate development, reduce development and maintenance costs, improve the structural stability and expansion of the system, and adapt to the access to new financial varieties and the extension of functions of existing varieties.
Smart Images

Figure CN120387894A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of asset management, and particularly to a method, device, medium and product for dynamically expanding financial assets. Background Art
[0002] Financial assets include standardized assets and non-standardized assets. Standardized assets include fixed-income securities such as bonds and asset-backed securities issued in accordance with the law. All other debt assets are non-standardized assets, except for deposits (including large-denomination certificates of deposit) and assets formed by bond reverse repurchase, inter-bank lending, etc.
[0003] These assets have both the same / similar behaviors, such as contract signing and approval, fund disbursement and approval, and also have many personalized behaviors, such as principal and interest repayment of credit assets, investment behaviors of wealth management assets, etc. Existing asset management systems lack refinement of the same / similar behaviors, and have disadvantages such as overlapping functions of the same / similar behaviors, high maintenance costs and easy errors. Summary of the Invention
[0004] The purpose of this application is to provide a method, device, medium and product for dynamically expanding financial assets, which can effectively avoid duplicate development and reduce development and maintenance costs.
[0005] To achieve the above purpose, this application provides the following solutions:
[0006] In the first aspect, this application provides a method for dynamically expanding financial assets. The method for dynamically expanding financial assets is applied to an asset management system, and the method for dynamically expanding financial assets includes:
[0007] Define an asset configuration file; the asset configuration file includes: the reading path of the asset operation configuration file and a literal definition list of various assets;
[0008] Define an asset operation configuration file; the asset operation configuration file includes: a mapping relationship list between various assets and asset operation behaviors;
[0009] Initialize an asset object and an asset operation object according to the asset configuration file and the asset operation configuration file, and transfer the asset operation behavior to the homonymous method of the asset execution interface through the bridge pattern to obtain a financial asset dynamic expansion framework;
[0010] The asset management system performs dynamic expansion of financial assets based on the financial asset dynamic expansion framework.
[0011] Optionally, initializing an asset object and an asset operation object according to the asset configuration file and the asset operation configuration file, and transferring the asset operation behavior to the homonymous method of the asset execution interface through the bridge pattern to obtain a financial asset dynamic expansion framework includes:
[0012] Read and parse the asset allocation file, and construct an asset proxy class and an asset execution interface according to the asset allocation file; the asset proxy class is used to create asset objects; the asset execution interface is used to create asset operation objects; the asset operation objects include: an abstract asset operation object and a specific asset operation object;
[0013] Read and parse the asset operation configuration file, and construct an abstract asset operation object and a specific asset operation object according to the asset operation configuration file; the specific asset operation objects include: all asset variety operation objects and specific asset variety operation objects; the specific asset variety operation objects inherit from the all asset variety operation objects; the all asset variety operation objects inherit from the abstract asset operation object;
[0014] Transfer the asset operation behavior to the method with the same name in the asset execution interface through the bridge pattern to obtain a financial asset dynamic extension framework.
[0015] Optionally, reading and parsing the asset allocation file, and constructing an asset proxy class and an asset execution interface according to the asset allocation file, including:
[0016] Read and parse the asset allocation file using a first parsing program;
[0017] Create an asset scheduling center in memory according to the asset allocation file; the asset scheduling center includes at least one asset context, and the asset context includes the asset proxy class and the asset execution interface.
[0018] Optionally, reading and parsing the asset operation configuration file, and constructing an abstract asset operation object and a specific asset operation object according to the asset operation configuration file, including:
[0019] Read and parse the asset operation configuration file using a second parsing program;
[0020] Construct an abstract asset operation object and a specific asset operation object according to the asset operation configuration file.
[0021] Optionally, transfer the asset operation behavior to the method with the same name in the asset execution interface through the bridge pattern to obtain a financial asset dynamic extension framework, including:
[0022] Aggregate the abstract asset operation object with the asset template class, and transfer the asset operation behavior to the method with the same name in the asset execution interface through the bridge pattern to obtain a financial asset dynamic extension framework.
[0023] Optionally, the asset management system performs dynamic extension of financial assets based on the financial asset dynamic extension framework, including:
[0024] In the asset management system, specific asset operation behaviors are initiated by specific assets;
[0025] Based on the financial asset dynamic extension framework, the specific asset operation behaviors of specific assets are bridged to the homonymous methods of the asset execution interface through injection;
[0026] According to the Java polymorphism principle, the homonymous methods of the asset execution interface are sunk to the homonymous methods of the subclass;
[0027] Identify whether the homonymous method of the subclass is a reusable key method;
[0028] If it is a reusable key method, then call or reuse the homonymous method of the parent class;
[0029] If it is not a reusable key method, then rewrite and call the homonymous method of the subclass.
[0030] Optionally, based on the financial asset dynamic extension framework, the specific asset operation behaviors of specific assets are bridged to the homonymous methods of the asset execution interface through injection, including:
[0031] Execute the homonymous method of the asset template class according to the specific asset operation behaviors of specific assets to obtain the asset execution interface;
[0032] The asset template class bridges the specific asset operation behaviors of specific assets to the homonymous methods of the asset execution interface through injection.
[0033] In a second aspect, the present application provides a computer device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor executes the computer program to implement the financial asset dynamic extension method.
[0034] In a third aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the financial asset dynamic extension method is implemented.
[0035] In a fourth aspect, the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, the financial asset dynamic extension method is implemented.
[0036] According to the specific embodiments provided by the present application, the following technical effects are disclosed in the present application:
[0037] The present application provides a method, device, medium and product for dynamic expansion of financial assets. The method includes: defining an asset allocation profile; defining an asset operation configuration profile; initializing asset objects and asset operation objects according to the asset allocation profile and the asset operation configuration profile, and transferring asset operation behaviors to the same-name methods of the asset execution interface through the bridge mode to obtain a financial asset dynamic expansion framework; and the asset management system performs dynamic expansion of financial assets based on the financial asset dynamic expansion framework. By constructing a financial asset dynamic expansion framework, the present application conducts hierarchical design for the same / similar behaviors and personalized behaviors of financial assets, which can effectively avoid duplicate development and reduce the development and maintenance costs. Whether new financial products are connected or the functions of existing financial products are extended, it has the characteristics of stable structure and easy expansion. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings required for use in the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.
[0039] Figure 1 It is a flowchart of the financial asset dynamic expansion method provided by the present application;
[0040] Figure 2 It is a general diagram of the financial asset dynamic expansion framework provided by the present application;
[0041] Figure 3 It is a flowchart of the initialization of asset objects provided by the present application;
[0042] Figure 4 It is a flowchart of the initialization of asset operation objects provided by the present application;
[0043] Figure 5 It is an example diagram of the implementation of asset operation behaviors provided by the present application;
[0044] Figure 6 It is a timing diagram of the method call for contract signing of open-ended fund assets provided by the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0045] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, rather than all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.
[0046] The present application provides a method, device, medium and product for dynamically expanding financial assets. Through the hierarchical design of the same / similar behaviors and personalized behaviors of financial assets, it can effectively avoid duplicate development and reduce the development and maintenance costs. Whether new financial products are connected or the functions of existing financial products are extended, it has the characteristics of stable structure and easy expansion.
[0047] To make the above objects, features and advantages of the present application more obvious and understandable, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0048] In an exemplary embodiment, the present application provides a method for dynamically expanding financial assets. The method for dynamically expanding financial assets is applied to an asset management system. In the embodiments of the present application, as Figure 1 and Figure 2 shown, the method includes the following steps 1 to 4.
[0049] Step 1: Define an asset configuration file. The asset configuration file includes: the reading path of the asset operation configuration file and the literal definition list of various assets.
[0050] Define the asset configuration file assetConfig.xml. This file is the total entry of the configuration information, including the literal definition list of various assets and the reading path of the asset operation configuration file assetOperaConfig.xml. The configuration example of the asset configuration file assetConfig.xml is as follows, where the tag <assetopera>The configured path is for reading the asset operation configuration file assetOperaConfig.xml, the tag <asset>Defines a literal definition list of various assets, including literal interface names and corresponding implementation objects.
[0051] Label <iface>Interface definitions representing each asset. Taking bond assets as an example, see Table 1 below.
[0052] Table 1 Interface Definition Table for Bond Assets
[0053]
[0054]
[0055] Label <impl>The interface implementation classes representing each asset. Taking bond assets as an example, it is shown in Table 2.
[0056] Table 2 Interface Implementation Class Table for Bond Assets
[0057]
[0058] A configuration example of the asset allocation file is shown in Table 3.
[0059] Table 3 Configuration Example Table of the Asset Allocation File Table
[0060]
[0061]
[0062] Step 2: Define the asset operation configuration file. The asset operation configuration file includes: a list of mapping relationships between various assets and asset operation behaviors.
[0063] Define the asset operation configuration file assetOperaConfig.xml. A configuration example of the asset operation configuration file assetOperaConfig.xml is shown in Table 4, where the tag <asset>The configured asset types are those defined in the aforementioned assetConfig.xml file, label <assetopera>Configured are the asset operation behaviors that the current asset variety can have, where the attribute <type>For contract represents contract operation behavior, attributes <type>For "money", it represents the behavior of capital operation, and the attribute <type>For invest, it represents the investment operation behavior.
[0064] Table 4 Configuration Example Table of Asset Operation Configuration File
[0065]
[0066]
[0067] Step 3: Initialize the asset object and the asset operation object according to the asset configuration file and the asset operation configuration file, and transfer the asset operation behavior to the method with the same name in the asset execution interface through the bridge mode to obtain the financial asset dynamic extension framework.
[0068] Step 3 specifically includes: reading and parsing the asset configuration file, and constructing an asset proxy class and an asset execution interface according to the asset configuration file; the asset proxy class is used to create an asset object; the asset execution interface is used to create an asset operation object; the asset operation object includes: an abstract asset operation object and a specific asset operation object; reading and parsing the asset operation configuration file, and constructing an abstract asset operation object and a specific asset operation object according to the asset operation configuration file; the specific asset operation object includes: all asset type operation objects (such as Figure 5 the contract asset operation object in) and specific asset type operation objects (such as Figure 5 the credit contract asset operation object and the wealth management contract asset operation object in); the specific asset type operation object inherits the all asset type operation object; the all asset type operation object inherits the abstract asset operation object; transfer the asset operation behavior to the method with the same name in the asset execution interface through the bridge mode to obtain the financial asset dynamic extension framework.
[0069] Specifically, reading and parsing the asset configuration file, and constructing an asset proxy class and an asset execution interface according to the asset configuration file, includes: using the first parsing program (i.e., the parsing program XmlAssetManagerBuilder) to read and parse the asset configuration file; according to the asset configuration file, creating an asset scheduling center in the memory; the asset scheduling center includes at least one asset context, and the asset context includes the asset proxy class and the asset execution interface.
[0070] Such as Figure 3 As shown in the figure, when the system is initialized, the parsing program XmlAssetManagerBuilder reads in the asset configuration file assetConfig.xml. First, the system creates an asset scheduling center AssetManager in memory. This asset scheduling center AssetManager contains one or more asset contexts AssetContext. An asset context AssetContext includes an asset proxy class AssetProxy (constructed from the asset configuration file assetConfig.xml) and an asset execution interface AssetOperaExecutor (constructed from the asset operation configuration file assetOperaConfig.xml). The asset proxy class AssetProxy is a unified proxy implementation class for each asset object. It is created based on the asset configuration file assetConfig.xml and is responsible for dynamically creating various asset objects at runtime to achieve the enhancement or extension of asset objects. The asset execution interface AssetOperaExecutor creates various asset operation objects according to the asset operation configuration file assetOperaConfig.xml, such as loan asset operation objects, wealth management asset operation objects, etc., and uniformly defines various asset operation behaviors, such as contract signing, investment application, loan disbursement, etc.
[0071] Specifically, read and parse the asset operation configuration file, and construct abstract asset operation objects and specific asset operation objects according to the asset operation configuration file, including: using the second parsing program (i.e., the parsing program AssetOperaConfigParser) to read and parse the asset operation configuration file; constructing abstract asset operation objects and specific asset operation objects according to the asset operation configuration file.
[0072] As Figure 4 shown in the figure, when the system is initialized, the parsing program AssetOperaConfigParser reads the configuration file into memory, and uses the AssetOperaClientBuilder class to construct abstract asset operation objects and specific asset operation objects. The asset operation configuration file assetOperaConfig.xml defines the corresponding relationship between assets and asset operation behaviors. Each asset can be freely combined with various asset operations. After being used in conjunction with the aforementioned asset configuration file assetConfig.xml, independent and dynamic expansion can be achieved both from the perspective of assets and from the perspective of asset operations. For example, contract signing behavior and investment application behavior can be defined for bond assets, contract signing behavior and fund loan disbursement behavior can be defined for credit assets, contract signing behavior and investment application behavior can be defined for wealth management assets, or loan disbursement behavior and other necessary additional asset behaviors can be defined for bond assets and wealth management assets.
[0073] After the above steps are completed, the AbstractAssetOpera of the abstract asset operation object and the AssetTemplate class are aggregated. When the front-end user (operator) performs a certain asset operation behavior on a certain asset, this method is transferred to the method with the same name in the AbstractAssetExecutor interface through the bridge pattern. Taking the contract approval and saving as an example, when executing the contract approval and saving method of a certain asset, the system will execute the contract approval and saving method executeContractApprovalSave of the AssetTemplate. In this method, the AssetOperaExecutor interface of the asset is first obtained, and then the contract approval method executeContractApprovalSave of the asset execution interface is called. This can decouple the asset from the asset operation behavior.
[0074] An example of the code for the asset template class to bridge the asset execution interface is shown in Table 5.
[0075] Table 5 Example code table for the asset template class to bridge the asset execution interface
[0076]
[0077]
[0078] An example of the code for the asset execution interface is shown in Table 6.
[0079] Table 6 Example code table for the asset execution interface
[0080]
[0081] Step 4: The asset management system performs dynamic expansion of financial assets based on the financial asset dynamic expansion framework.
[0082] The above Steps 1 to 3 are the basic framework for the dynamic expansion of financial assets. The asset management system performs dynamic expansion of financial assets based on the financial asset dynamic expansion framework, including: in the asset management system, a specific asset initiates a specific asset operation behavior; based on the financial asset dynamic expansion framework, the specific asset operation behavior of the specific asset is bridged to the method with the same name in the asset execution interface through the injection method; according to the Java polymorphism principle, the method with the same name in the asset execution interface is sunk to the method with the same name in the subclass; identify whether the method with the same name in the subclass is a reusable key method; if it is a reusable key method, then call or reuse the method with the same name in the parent class; if it is not a reusable key method, then rewrite and call the method with the same name in the subclass.
[0083] Among them, based on the dynamic extension framework of financial assets, the specific asset operation behavior of a specific asset is bridged to the method with the same name in the asset execution interface through injection, including: executing the method with the same name in the asset template class according to the specific asset operation behavior of the specific asset to obtain the asset execution interface; the asset template class bridges the specific asset operation behavior of the specific asset to the method with the same name in the asset execution interface through injection.
[0084] At the implementation level, a specific asset, such as the credit asset object CreditContractAsset, needs to initiate a specific asset operation behavior, such as contract signing executeContractSign(), as Figure 5 shown.
[0085] If it is a method that is fixed and applicable to the operation contracts of all asset types, such as the contract signing initialization method doContractSignInit(), then it is defined in the contract asset operation object ContractAssetOpera and is called an atomic method.
[0086] If the method reused at the abstract asset operation object AbstractAssetOpera level may also be overridden at the specific asset contract operation object level, then the method defined in the abstract asset operation object AbstractAssetOpera is a template method, such as the contract signing other method doContractSignOther(), and the method defined in the specific asset contract operation object is called a hook method, such as the contract signing other method doContractSignOther() of the credit contract asset operation object CreditContractAssetOpera.
[0087] If the method reused at the contract asset operation object ContractAssetOpera level may also be overridden at the specific asset contract operation object level, then the method defined in the contract asset operation object ContractAssetOpera is also a template method, such as the contract signing save method doContractSignSave(), and the method defined in the specific asset contract operation object is also called a hook method, such as the contract signing save method doContractSignSave() of the credit contract asset operation object Cr
[0088] editContractAssetOpera.
[0089] The purpose of the above design is to make full use of the Java polymorphism principle, identify key reusable methods, reduce the cost of dynamic extension, and improve the efficiency of dynamic extension.
[0090] Take the executeContractSign method as an example of contract signing. executeContractSign consists of three steps: contract signing initialization, contract signing saving, and other contract signing operations. The contract signing initialization doContractSignInit is applicable to all types of asset contracts, without the need for splitting or sinking to subclasses. It is a fixed and unchanging atomic method that is directly called by subclasses. The contract signing saving doContractSignSave() may have different elements and rules for the contract signing of the credit contract asset operation object CreditContractAssetOpera and the wealth management contract asset operation object FinContractAssetOpera, or it may have the same elements and rules. In the former case, the contract signing saving method doContractSignSave can be overridden in their respective classes, and at this time, the contract signing saving method doContractSignSave becomes a typical hook method. In the latter case, the contract signing saving method of the parent class doContractSignSave can be directly called, which can greatly improve the readability, reusability, and maintainability of the code.
[0091] The following provides a complete usage case of the financial asset dynamic extension framework.
[0092] Suppose that now a certain asset management system needs to connect to a new type of financial asset: open-ended funds, and needs to implement the contract signing for open-ended funds. Then the operating logic of the system is as Figure 6 shown.
[0093] 1. Add a definition in the asset configuration file assetConfig.xml. See Table 7.
[0094] Table 7 New Definition Table of Asset Configuration File
[0095]
[0096] 2. Add a definition in the asset operation configuration file assetOperaConfig.xml. See Table 8.
[0097] Table 8 New Definition Table of Asset Operation Configuration File
[0098]
[0099] 3. After the asset management system starts, the asset proxy class AssetProxy initializes the open-ended fund asset instance.
[0100] 4. When an operator triggers a contract signing application via the open-ended fund asset instance FundAsset, it first triggers the contract signing application method executeContractSign() of the parent class of the open-ended fund asset instance, i.e., the asset template class AssetTemplate, and then the asset template class AssetTemplate bridges to the contract signing application method executeContractSign() of the same name in the asset execution interface AssetOperaExecutor through injection.
[0101] 5. According to the Java polymorphism principle, the contract signing method of the asset execution interface AssetOperaExecutor sinks to the contract signing application method executeContractSign() of the open-ended fund contract asset operation object class FundContractAssetOpera.
[0102] 6. The contract signing application method executeContractSign() of the open-ended fund contract asset operation object class FundContractAssetOpera consists of three parts, namely the contract signing initialization sub-method doContractSignInit(), the contract signing save sub-method doContractSignSave(), and the contract signing other sub-method doContractSignOther().
[0103] 7. The contract signing initialization sub-method doContractSignInit() is applicable to assets of all varieties and directly calls this method in the contract asset operation object class ContractAssetOpera.
[0104] 8. For the contract signing save sub-method doContractSignSave(), if there are personalized differences in the logic of the contract signing save method doContractSignSave() of the open-ended fund contract asset operation object class FundContractAssetOpera, the system automatically calls the contract signing save method doContractSignSave() of the open-ended fund contract asset operation object class FundContractAssetOpera; otherwise, the system will automatically call (re-use) the contract signing save method doContractSignSave() in the contract asset operation object class ContractAssetOpera.
[0105] 9. The other sub - method for contract signing, doContractSignOther(). If there are personalized differences in the logic of the other contract - signing method doContractSignOther() of the FundContractAssetOpera class, which is the operation object class of the open - ended fund contract assets, the system automatically calls the other contract - signing method doContractSignOther() of the FundContractAssetOpera class. Otherwise, the system will automatically call (re - use) the other contract - signing method doContractSignOther() in the AbstractAssetOpera class, which is the abstract asset operation object class.
[0106] This application has the following advantages:
[0107] 1. By using a configuration file to define financial product types, it is possible to dynamically add or delete product types, achieving the separation of interfaces and implementations, and increasing the flexibility and scalability of the system.
[0108] 2. Using the dynamic proxy mechanism to call the asset management applications of various financial product types, unifying the method call entry, reducing the intrusion into business code, and effectively reducing the complexity of business objects.
[0109] 3. Through the template design pattern, abstracting specific asset behaviors to form a high - level abstraction layer, and then defining templates for each specific asset behavior, improving the reuse rate of asset behaviors and accelerating the speed of deploying new assets and operation behaviors.
[0110] In an exemplary embodiment, the present application also provides a computer device, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above - mentioned method embodiments are implemented.
[0111] In an exemplary embodiment, the present application also provides a computer - readable storage medium storing a computer program, and when the computer program is executed by a processor, the steps in the above - mentioned method embodiments are implemented.
[0112] In an exemplary embodiment, the present application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, the steps in the above - mentioned method embodiments are implemented.
[0113] In this application, all actions of obtaining signals, information, or data are carried out on the premise of complying with the corresponding data protection regulations and policies of the country where the location is located and obtaining the authorization given by the owner of the corresponding device. It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant laws and regulations.
[0114] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memories can include read-only memory (ROM), magnetic tapes, floppy disks, flash memories, optical memories, high-density embedded non-volatile memories, resistive random access memories (ReRAM), magnetoresistive random access memories (MRAM), ferroelectric random access memories (FRAM), phase change memories (PCM), graphene memories, etc. Volatile memories can include random access memory (RAM) or external cache memories, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.
[0115] The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logics, data processing logics based on quantum computing, etc., without limitation.
[0116] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.
[0117] In this article, specific examples are used to elaborate on the principles and implementation manners of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation to the present application.< / type> < / type> < / type> < / assetopera> < / asset> < / impl> < / iface> < / asset> < / assetopera>
Claims
1. A method for dynamically expanding financial assets, characterized in that The financial asset dynamic expansion method is applied to an asset management system, and the financial asset dynamic expansion method includes: Defining an asset allocation file; the asset allocation file includes: the reading path of the asset operation configuration file and a literal definition list of various assets; Defining an asset operation configuration file; the asset operation configuration file includes: a mapping relationship list between various assets and asset operation behaviors; Initializing an asset object and an asset operation object according to the asset allocation file and the asset operation configuration file, and transferring the asset operation behavior to the homonymous method of the asset execution interface through the bridge mode to obtain a financial asset dynamic expansion framework; The asset management system performs dynamic expansion of financial assets based on the financial asset dynamic expansion framework.
2. The dynamic expansion method of financial assets according to claim 1, wherein Initializing an asset object and an asset operation object according to the asset allocation file and the asset operation configuration file, and transferring the asset operation behavior to the homonymous method of the asset execution interface through the bridge mode to obtain a financial asset dynamic expansion framework, including: Reading and parsing the asset allocation file, and constructing an asset proxy class and an asset execution interface according to the asset allocation file; the asset proxy class is used to create an asset object; the asset execution interface is used to create an asset operation object; the asset operation object includes: an abstract asset operation object and a specific asset operation object; Reading and parsing the asset operation configuration file, and constructing an abstract asset operation object and a specific asset operation object according to the asset operation configuration file; the specific asset operation object includes: an all-asset-variety operation object and a specific-asset-variety operation object; the specific-asset-variety operation object inherits the all-asset-variety operation object; the all-asset-variety operation object inherits the abstract asset operation object; Transferring the asset operation behavior to the homonymous method of the asset execution interface through the bridge mode to obtain a financial asset dynamic expansion framework.
3. The financial asset dynamic expansion method according to claim 2, wherein Reading and parsing the asset allocation file, and constructing an asset proxy class and an asset execution interface according to the asset allocation file, including: Reading and parsing the asset allocation file by using a first parsing program; Creating an asset scheduling center in memory according to the asset allocation file; the asset scheduling center includes at least one asset context, and the asset context includes the asset proxy class and the asset execution interface.
4. The financial asset dynamic expansion method according to claim 2, characterized in that Reading and parsing the asset operation configuration file, and constructing an abstract asset operation object and a specific asset operation object according to the asset operation configuration file, including: Reading and parsing the asset operation configuration file by using a second parsing program; Constructing an abstract asset operation object and a specific asset operation object according to the asset operation configuration file.
5. The financial asset dynamic expansion method according to claim 2, wherein Transferring the asset operation behavior to the homonymous method of the asset execution interface through the bridge mode to obtain a financial asset dynamic expansion framework, including: Aggregating the abstract asset operation object with the asset template class, and transferring the asset operation behavior to the homonymous method of the asset execution interface through the bridge mode to obtain a financial asset dynamic expansion framework.
6. The dynamic expansion method of financial assets according to claim 1, wherein The asset management system performs dynamic expansion of financial assets based on the financial asset dynamic expansion framework, including: In the asset management system, a specific asset initiates a specific asset operation behavior; Based on the dynamic extension framework of financial assets, the specific asset operation behavior of a specific asset is bridged to the homonymous method of the asset execution interface through injection; According to the Java polymorphism principle, the homonymous method of the asset execution interface is sunk to the homonymous method of the subclass; Identify whether the homonymous method of the subclass is a reusable key method; If it is a reusable key method, call or reuse the homonymous method of the parent class; If it is not a reusable key method, rewrite and call the homonymous method of the subclass.
7. The financial asset dynamic expansion method according to claim 6, wherein Based on the dynamic extension framework of financial assets, the specific asset operation behavior of a specific asset is bridged to the homonymous method of the asset execution interface through injection, including: Execute the homonymous method of the asset template class according to the specific asset operation behavior of the specific asset to obtain the asset execution interface; The specific asset operation behavior of the specific asset is bridged to the homonymous method of the asset execution interface by the asset template class through injection.
8. A computer device, comprising: A memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to implement the financial asset dynamic extension method according to any one of claims 1-7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the financial asset dynamic extension method according to any one of claims 1-7.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the financial asset dynamic extension method according to any one of claims 1-7.