A method and system for displaying multi-form data linkage of over-the-counter derivatives

Abstract

The present invention provides a method and system for the linkage display of multi-form data of over-the-counter derivatives, provides the structural definition of element metadata, the structural definition of form data and the structural definition of form container, divides the three display areas of contract master data, structural data and underlying data for displaying and editing over-the-counter derivative contract data, and provides a method for generating a form display header for each area dynamically based on metadata and a processing method for formatting the display of form data. In addition, a linkage display processing method among the contract master data, structural data and underlying data is also provided.

Description

Technical Field

[0001] The present invention relates to a method and system for linkage display of multi-form data of over-the-counter derivatives, belonging to the technical field of form data processing. Background Art

[0002] In recent years, my country's over-the-counter derivatives market has developed rapidly, among which the development of business products such as interest rate swaps, over-the-counter options and income certificates is particularly prominent. The contract data of over-the-counter derivatives is an important means to record and track business progress.

[0003] Due to the complexity of OTC derivatives business types, the corresponding contract data structure becomes very complex. OTC derivatives contract data usually consists of three parts: contract master data, structure data and underlying data. Its complexity is mainly reflected in three points: First, the business type structure is complex. Taking OTC options as an example, there are usually 1-N types of option products in the OTC derivatives contract management system, and the elements of these products themselves are very different. Second, the hierarchical relationship is complex. In structured OTC derivatives, there is a 1:N correspondence between contract master data and structure data, and there is also a 1:N correspondence between structure data and underlying data. Third, the element fields are complex. In most scenarios, the contract master data, structure data and underlying data each contain dozens of element fields, and the element field types are complicated, including strings, integer values, floating-point values, JSON, date values, etc.

[0004] Due to the complexity of contract data, there are difficulties in system implementation, such as high development difficulty and long time cycle. Especially in the display of contract data, the addition of support for a new product structure often requires a lot of time and effort to solve problems such as data acquisition, processing, display and update. Therefore, it affects the development speed of new business types of over-the-counter derivatives to a certain extent. Summary of the invention

[0005] The purpose of the present invention is to overcome the deficiencies in the prior art and to provide a method and system for the linkage display of multi-form data of over-the-counter derivatives, which can automatically generate a query condition area based on a set of element metadata, allowing users to input query conditions by themselves to perform data queries, and can quickly realize the display and update requirements of form data.

[0006] To achieve the above object, the present invention is implemented by adopting the following technical solutions:

[0007] In a first aspect, the present invention provides a method for displaying multi-form data linkage of over-the-counter derivatives, comprising the following steps:

[0008] Generate an element metadata set; the element metadata set includes element metadata of contract master data, structure data and subject data;

[0009] Obtain the element metadata set, classify and sort it, and form the contract master data metadata set, structure data metadata set and target data metadata set;

[0010] Generate a set of table header columns based on the element metadata set after classification and sorting, and set editing properties for each column;

[0011] Generate a query condition area according to the element metadata data set, and obtain a query condition input by a user based on the query condition area;

[0012] Obtain form data according to the query conditions;

[0013] The form data is formatted according to the metadata format to form data to be displayed and the data to be displayed is output for display.

[0014] Furthermore, the method for generating the feature metadata dataset includes:

[0015] According to the structural characteristics of over-the-counter derivative products, the elements of the contract master data, structural data and underlying data are sorted out, and the corresponding element metadata is generated according to the data characteristics of each element to form an element metadata data set, which is stored in the element metadata data set database;

[0016] The element metadata is the self-descriptive information of each element in the form, including element category, display name, column identifier, display sequence, data type, whether it is a query condition, whether it is editable, and structure type attributes, where the column identifier is the unique identifier of the element metadata; the element category includes contract master data, structure data, and subject data;

[0017] The contract master data refers to a collection of identical elements in products of different structures; the contract master data uses the contract number as the unique identifier of the contract master data;

[0018] The structural data refers to a collection of unique elements in products of different structures; the structural data uses a transaction number as a unique identifier of the structural data; the structural data stores a contract number to indicate the subordinate relationship between the structural data and the contract master data;

[0019] The target data refers to the collection of target elements linked to products of different structures; the target data elements of different structural data are the same, and the target data includes transaction number, target code and transaction venue; the target code and transaction venue constitute the unique identification of the target data; the target data is used to indicate the subordinate relationship between the target data and the structural data.

[0020] Furthermore, the method of obtaining the feature metadata data set and performing sorting processing includes:

[0021] Obtain a feature metadata dataset from a feature metadata dataset database;

[0022] Classify the element metadata according to the element category, and store the element metadata of the contract master data, structure data and subject data in independent containers respectively;

[0023] The element metadata in each container is sorted in ascending order according to the display sequence of the element metadata to form a contract master data metadata set, a structural data metadata set and a target data metadata set.

[0024] Furthermore, the method of generating a form display header column set and setting editing properties for each column includes:

[0025] Traverse the contract master data metadata set, add the metadata display name to the list, form the contract master data header column set, and bind the metadata editability and data type attributes to the corresponding columns;

[0026] Traverse the structure data metadata set, add the display name of the metadata to the list, form a structure data header column set, bind the metadata editability and data type attributes to the corresponding columns, take out the element metadata named contract number from the contract master data metadata set, add its display name to the head of the structure data header column set, and mark this column as non-editable;

[0027] Traverse the target data metadata set, add the metadata display name to the list, form the target data header column set, bind the metadata editability and data type attributes to the corresponding columns, take out the element metadata named transaction number from the structure data metadata set, add its display name to the head of the target data header column set, and mark this column as non-editable;

[0028] After the contract main data header set, structure data header column set and subject data header column set are generated, they are filled into the corresponding parts of the form data display area for display.

[0029] Furthermore, the method for generating a query condition area according to the feature metadata set includes:

[0030] Traverse the contract main data metadata set, structure data metadata set and target data metadata set, and extract the metadata that meets the query condition TRUE;

[0031] Generate a corresponding input control according to the data type of the metadata extracted separately, where the input control refers to a component used by the user to manually enter data, and place the input control in the query condition area for the user to enter the query condition;

[0032] Furthermore, the method of obtaining form data according to the query condition includes:

[0033] According to the query conditions entered by the user in the query condition area, the query conditions are encapsulated into a predetermined message format;

[0034] Get form data according to a predetermined message format;

[0035] The form data is a two-dimensional data list, including column identifiers, element categories and structure types in element metadata, which is used to match the element metadata in the front-end application system and the element metadata set, so as to parse it and display it in the specified column; the basic format of the predetermined message format is in the form of a "key-value" pair, the key is the column identifier of the element metadata, and the value is the actual data of the form data column.

[0036] Furthermore, the method of formatting the form data according to the metadata format to form the data to be displayed includes:

[0037] Traverse the form data, extract a single row of data, traverse a single row of data, extract a single column of data, classify the column data according to the element category, and form a collection of contract master data, structure data and target data for a single row of data;

[0038] Processing contract master data: traverse the contract master data set of a single row of data, extract a single contract master data column, find metadata in the contract master data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and place the result in the contract master data set to be displayed after processing;

[0039] Processing structure data: traverse the structure data of a single row of data, extract a single structure data column, find the metadata in the structure data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and after processing, put the result into the hash table of structure data to be displayed according to the structure type of the column data; the hash table of structure data to be displayed uses the structure type as the key; after traversal, insert the hash table of structure data to be displayed into the tail of the contract master data set to be displayed;

[0040] Processing target data: traverse the target data of a single row of data, extract a single target data column, find the metadata in the target data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and after processing, put the result into the hash table of the target data to be displayed according to the transaction number of the column data; the hash table of the target data to be displayed uses the transaction number as the key; after traversal, find the structure data to be displayed with the same transaction number in the hash table of the structure data to be displayed, and insert the hash table of the target data to be displayed into the tail of the set of main contract data to be displayed;

[0041] After processing is completed, the contract master data set to be displayed is filled into the contract master data display area for display.

[0042] Furthermore, the data linkage display method also includes the linkage display processing of contract master data, structure data and subject data, including the following steps:

[0043] When the user selects a certain contract master data in the contract master data display area, the structure data hash table to be displayed is taken out from the tail of the contract master data, and a structure data list containing N different structure types is obtained according to the key in the hash table, and filled into the structure data display area in the lower left corner;

[0044] If the number of structure data lists N>1, the structure data of different structure types are displayed in tabs, and the title of each tab corresponds to the value of the structure type;

[0045] When the user selects a certain structure data in the structure data display area, the hash table of the target data to be displayed is taken out from the tail of the current contract main data, and the list of display target data is taken out according to the transaction number in the structure data, and filled into the target data in the lower right corner for display.

[0046] Furthermore, the data linkage display method also includes form data editing processing, including the following steps:

[0047] When the user edits the form data, including adding, deleting, and updating, the corresponding edit control is generated according to the data type in the feature metadata, and the display data is filled into the edit control;

[0048] After the user finishes editing, the updated value is obtained from the edit control and filled into the corresponding column of the form container.

[0049] Furthermore, the data linkage display method also includes form data persistence processing, including the following steps:

[0050] When the user edits the data in the form, the initial data and the latest data in the form container are compared, and the changed data is extracted to form a list of data to be sent; the list of data to be sent uses row data as basic elements, and the row data contains all column data, and each column data includes normal display data, column identifiers in element metadata, element categories, and structure types;

[0051] The list to be sent is transmitted in a predetermined message format, processed and saved in a database.

[0052] In a second aspect, the present invention provides an OTC derivatives multi-form data linkage display system, including a front-end application system and a back-end service system:

[0053] The foreground application system is used to obtain a set of element metadata from the background service system, parse the set of element metadata, and generate a form container; obtain multiple form data from the background service system, parse the multiple form data, parse and process the form data according to the attributes in the element metadata set, and then display it in the form container; at the same time, obtain the data added, deleted, and modified by the user in the form container, and send the changed data to the background service system for storage;

[0054] Backend service system: used to store feature metadata sets and provide query interfaces for the frontend application system to obtain feature metadata sets; store multi-form data and provide query and save interfaces for the frontend application system to obtain form data.

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

[0056] 1. The present invention provides a method for displaying multi-form data of over-the-counter derivatives in a linked manner. In a metadata-driven manner, it can dynamically display, add, delete, update and other common form functions of contract master data, structural data and underlying data in a form container, realize the linked display between contract master data and structural data, and realize the linked display between structural data and underlying data. At the same time, it can automatically generate a query condition area according to the element metadata set, allowing users to input query conditions by themselves to perform data query, thereby quickly realizing the display and update requirements of form data.

[0057] 2. The advantage of the present invention is that through the definition and combined use of element metadata, a method for displaying multi-form data linkage of over-the-counter derivatives is realized, and three display areas of contract master data, structure data and subject data are divided for displaying and editing over-the-counter derivatives data. The display header and data display format of each area are dynamically generated based on metadata. When encountering changes in requirements, such as adding or deleting fields, adjusting the display order of fields, etc., it is only necessary to modify the relevant attributes of the metadata in the metadata set. When encountering a completely new derivative product structure, it is only necessary to configure the corresponding metadata to quickly display and edit data in the foreground application system. The present invention avoids the function development that needs to be completed manually according to specific field definitions in the traditional development process, reduces repetitive coding work, shortens the system development cycle, and improves the quality of function delivery. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 It is a list diagram of element metadata attributes of a method for displaying multi-form data linkage of over-the-counter derivatives of the present invention;

[0059] Figure 2 It is a flow chart of a method for linkage display of multi-form data of over-the-counter derivatives according to the present invention;

[0060] Figure 3 A schematic diagram of a form container structure of a method for displaying multi-form data linkage of over-the-counter derivatives according to the present invention;

[0061] Figure 4 A schematic diagram of the form data structure of a method for displaying multi-form data linkage of over-the-counter derivatives according to the present invention;

[0062] Figure 5 A schematic diagram of the display area of ​​a method for linked display of multi-form data of over-the-counter derivatives according to the present invention. DETAILED DESCRIPTION

[0063] The present invention will be further described below in conjunction with the accompanying drawings. The following embodiments are only used to more clearly illustrate the technical solution of the present invention, and cannot be used to limit the protection scope of the present invention.

[0064] Embodiment 1:

[0065] In response to the technical problems encountered in the display and update of the above-mentioned over-the-counter derivatives contract data, this embodiment provides a method for the linkage display of multi-form data of over-the-counter derivatives. In a metadata-driven manner, it is possible to dynamically perform common form functions such as display, addition, deletion, and update of contract master data, structural data, and underlying data in the form container, thereby realizing the linkage display between contract master data and structural data, and the linkage display between structural data and underlying data. At the same time, it is possible to automatically generate a query condition area based on the element metadata set, allowing users to enter query conditions by themselves to perform data queries, thereby quickly realizing the display and update requirements of form data.

[0066] The specific method for displaying multi-form data linkage of over-the-counter derivatives includes the following steps:

[0067] Step 1: Generate an element metadata set. According to the structural characteristics of over-the-counter derivative products, sort out the elements of the contract master data, structure data and underlying data, and generate corresponding element metadata according to the data characteristics of each element to form an element metadata set, which is stored in the element metadata set database. The element metadata is the self-describing information of each element in the form, including element category (including three types: contract master data, structure data and underlying data), display name, column ID, display sequence, data type (including integer, floating point, string, date, Boolean, JSON and enumeration), whether it is a query condition, whether it is editable, structure type (only applicable to structure data) and other attributes. The column ID is the unique identifier of the element metadata and cannot be repeated. For the specific structure, see the attached. Figure 1 ;

[0068] Contract master data refers to a collection of identical elements in products of different structures. These elements constitute the common part of the contract. There is an element called contract number in the contract master data, which is the unique identifier of the contract data.

[0069] Structural data refers to a collection of unique elements in products of different structures. There is an element called transaction number in the structural data, which is the unique identifier of the structural data. In addition, the structural data stores the associated contract number, indicating which contract master data the structural data belongs to.

[0070] The underlying data refers to the collection of underlying elements in products of different structures. The underlying data elements of different structural data are the same. There is an element called the underlying code and an element called the trading venue in the underlying data, which together constitute the unique identifier of the underlying data. In addition, the underlying data stores the associated transaction number, indicating which structural data the underlying data belongs to.

[0071] Step 2: Obtain the element metadata data set and sort it. The front-end application system obtains the element metadata data set from the element metadata data set database, first classifies it according to the element category of the element metadata, stores the element metadata of the contract master data, structure data and subject data in independent containers, and sorts the element metadata in each container in ascending order according to the display sequence of the element metadata to form the contract master data metadata set, structure data metadata set and subject data metadata set;

[0072] Step 3: Generate a form display header column set and set editing properties for each column. Traverse the contract master data metadata set, add the display name of the metadata to the list, form a contract master data header column set, and bind the metadata editability and data type attributes to the corresponding columns; traverse the structure data metadata set, add the display name of the metadata to the list, form a structure data header column set, and bind the metadata editability and data type attributes to the corresponding columns, extract the element metadata named contract number from the contract master data metadata set, add its display name to the head of the structure data header column set, and mark this column as non-editable; traverse the target data metadata set, add the display name of the metadata to the list, form a target data header column set, and bind the metadata editability and data type attributes to the corresponding columns, extract the element metadata named transaction number from the structure data metadata set, add its display name to the head of the target data header column set, and mark this column as non-editable; after the contract master data header set, structure data header column set, and target data header column set are generated, fill them into the corresponding parts of the form data display area for display;

[0073] Step 4: Generate the query condition area layout. Traverse the contract master data metadata set, structure data metadata set and subject data metadata set, and extract the metadata for which the query condition is TRUE. According to the data type of the extracted metadata, generate the corresponding input control and place it in the query condition area for the user to enter the query condition; input control refers to the component that the user can manually enter data, which can be subdivided into text box, date selection component, value input box, etc. according to different data types;

[0074] Step 5: Get form data from the background service. According to the query conditions entered by the user in the query condition area, the foreground application system encapsulates the query conditions into a predetermined message format and sends it to the background service system, and obtains the form data from the background service system. The form data is a two-dimensional data list, and each element in the list is a row of data. A row of data consists of 1-N column data. In addition to the normal display data, the column data also contains the column identifier, element category and structure type in the element metadata, which are used for matching the foreground application system with the element metadata in the element metadata set, so as to parse it and display it in the specified column; the predetermined message format, its basic format is in the form of a "key-value" pair, the key is the column identifier of the element metadata, and the value is the actual data of the form data column. The predetermined message format realizes the transmission of multiple rows of form data through repeated "key-value" pairs;

[0075] Step 6: Format the form data according to the metadata to form the data to be displayed. The specific formatting process is as follows: traverse the form data, take out a single row of data, traverse a single row of data, take out a single column of data, classify the column data according to the element category, and form a single row of data contract master data, structure data and target data set. Processing contract master data: traverse the contract master data set of a single row of data, take out a single contract master data column, find metadata in the contract master data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and place the result in the contract master data set to be displayed after processing. Processing structure data: traverse the structure data of a single row of data, take out a single structure data column, find metadata in the structure data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and place the result in the structure data hash table to be displayed (with the structure type as the key and its value as a list) according to the structure type of the column data after processing. The purpose of the structure data hash table to be displayed is to meet the scenario where multiple structure data are attached to one contract master data. After traversal is completed, the structure data hash table to be displayed is inserted into the tail of the contract master data set to be displayed. Processing target data: traverse the target data of a single row of data, extract a single target data column, find the metadata in the target data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and after processing, put the result into the target data hash table to be displayed (with the transaction number as the key and its value as a list) according to the transaction number of the column data. The purpose of the target data hash table to be displayed is to meet the scenario of multiple target data hanging under one structure data. After traversal, the structure data to be displayed with the same transaction number in the hash table of the structure data to be displayed, and insert the target data hash table to be displayed into the tail of the contract master data set to be displayed. After processing, fill the contract master data set to be displayed into the contract master data display area for display.

[0076] Step 7: Linked display processing of contract master data, structure data and target data. When the user selects a certain contract master data in the contract master data display area, the hash table of structure data to be displayed is taken out from the tail of the contract master data, and according to the key in the hash table, a list of structure data containing N (N≧1) different structure types is obtained, and filled into the structure data display area in the lower left corner. If N>1, the structure data of different structure types are displayed in the form of tabs, and the title of each tab corresponds to the value of the structure type. When the user selects a certain structure data in the structure data display area, the hash table of target data to be displayed is taken out from the tail of the current contract master data, and the list of target data to be displayed is taken out according to the transaction number in the structure data, and filled into the target data in the lower right corner for display;

[0077] Step 8: Editing and processing form data. The processing process for contract master data, structure data and subject data is the same. When the user edits the form data, including adding, deleting and updating, the front-end application system generates the corresponding edit control according to the data type in the element metadata, and fills the display data into the edit control. After the user finishes editing, the front-end application system obtains the updated value from the edit control and fills it into the corresponding column of the form container;

[0078] Step 9: Persistence processing of form data. When the user edits the data in the form, the front-end application system compares the initial data and the latest data in the form container, extracts the changed data, and forms a list of data to be sent. The list of data to be sent uses row data as the basic element, and the row data contains all column data. In addition to the normal display data, each column data also contains the column identifier, element category and structure type in the element metadata. The list to be sent is sent to the back-end service system in a predetermined message format, and the back-end service system processes it and saves it to the database.

[0079] Figure 1 A list of element metadata attributes of a method for displaying multi-form data linkage of over-the-counter derivatives is shown. The composition of the element metadata includes: element category, display name, column identifier, display sequence, data type, structure type, whether it is editable, whether it is a query condition, whether to use thousands separators, minimum integer value, maximum integer value, minimum floating point value, maximum floating point value, enumeration list, and data precision.

[0080] Among them, the element category is used to distinguish the type of data, which includes three categories, namely contract master data, structure data and subject data. The display name is the display value used for the table header in the form container; the column identifier is the unique identifier of the element metadata, which cannot be repeated and is used to distinguish different element metadata in the element metadata set; the display sequence is the display position of the element metadata in the element metadata set, which cannot be repeated and is numbered from 0; the data type refers to the data type of the column in the element metadata set, including integer, floating point, string, date, Boolean, JSON and enumeration, which is used to control the formatting process when the data is displayed; whether it is editable is used to indicate the display of the element metadata in the form container. Whether the data in this column can be edited in the query condition; whether it is a query condition is used to control whether the column is included in the query condition interface when generating it; whether to use thousand separators is applicable to integer and floating-point data, and is used to control whether the value is formatted in accounting format when displayed, such as "1,000,000,000"; the maximum value of integer and the minimum value of integer are applicable to integer data, and are used to control the range of values ​​that users can enter when editing; similarly, the minimum value of floating point and the maximum value of floating point control the input range of floating point data; the data precision controls the decimal precision of floating point data when displayed in the target container; the enumeration list is applicable to string type, and is used to provide a drop-down box style value display, such as province.

[0081] Figure 2 A flow chart of a method for linkage display of multi-form data of over-the-counter derivatives of the present invention is shown. It can be seen from the steps therein that in the development process of the present invention, the main work will focus on the maintenance of element metadata, and functions such as interface layout generation, data access and update are automatically completed by the general data component, ensuring the consistency of implementation logic; for back-end personnel, they only need to follow the general data interface specification in the process of implementing the CRUD service of the data. The general data interface specification includes three interfaces of adding, deleting and updating, and its expression form is standardized, that is, the interfaces of all business function data are the same.

[0082] When business requirements change, such as adding or deleting fields, changing query conditions, adjusting the order of field display, etc., front-end developers only need to maintain the existing metadata without changing the front-end code. Even for the need to adjust the order of field display, after modifying the metadata, the hot layout of the front-end function interface can be realized. For back-end developers, they only need to change the internal implementation of the data service, and no modification at the interface level is involved.

[0083] Figure 3A schematic diagram of the form container structure of a method for displaying multi-form data linkage of over-the-counter derivatives of the present invention is shown. The form container consists of two parts: a query condition area and a form data display area. The query condition area generates corresponding input controls for user input based on whether it is a query condition and the data type in the element metadata set; the form data display area consists of three parts, the top is the contract main data display area, the lower left corner is the structure data display area, and the lower right corner is the target data display area, wherein the structure data display area supports the simultaneous display of data of multiple structure types, and is laid out in the form of tabs. The form header of the data display area comes from the element metadata set. The detailed process is shown in steps 2 and 3 above.

[0084] Figure 4 A schematic diagram of the form data structure of a method for linkage display of multi-form data of over-the-counter derivatives of the present invention is shown, wherein the form data is composed of 1-N row data, and the row data is composed of 1-N column data. Each column data contains four attributes, namely, display data, column identifier, element category, and structure type. After the original form data is processed in step six above, it is finally filled into the corresponding part of the form data display area for display.

[0085] The present embodiment is further described in detail below in conjunction with a specific over-the-counter options embodiment:

[0086] OTC options are a typical OTC derivative product. There are many types of OTC options. The common "automatic knock-in, knock-out" structure is used as an example. The main fields of the "automatic knock-in, knock-out" contract data include:

[0087] Table 1 Main fields of "Automatic knock-in and knock-out" contract data

[0088] Feature name Feature categories Contract Number Contract Master Data Customer Name Contract Master Data Product Name Contract Master Data Trading Currency Contract Master Data Transaction Description Contract Master Data Total options position Contract Master Data Initial nominal principal Contract Master Data Transaction completion date Contract Master Data Start date Contract Master Data Expiration Date Contract Master Data Duration Contract Master Data Front-end rate Contract Master Data Computing Agency Contract Master Data Transaction ID Structural data Structure Type Structural data Asset Class Structural data Position direction Structural data Valuation Model Structural data Beginning Price Structural data Option Direction Structural data Knock-out yield Structural data Knock out the observation day sequence Structural data Target Code Target data Name of the target Target data Trading venue Target data The size of the target Target data

[0089] According to step 1, first generate the element metadata set for the "automatic knock-in and knock-out" contract. The generated element metadata set is shown in the following table:

[0090] Table 2 Metadata set of data elements of “automatic knock-in and knock-out” contract

[0091] Column ID display name Feature categories Data Types Display Sequence Structure Type ..... TradeId Contract Number Contract Master Data String Autocall Clientname Customer Name Contract Master Data String Autocall Productname Product Name Contract Master Data String Autocall Currency Trading Currency Contract Master Data enumerate Autocall Description Transaction Description Contract Master Data String Autocall Cash Total options position Contract Master Data Floating point numbers Autocall NotionalMonney Initial nominal principal Contract Master Data Floating point numbers Autocall Tradedate Transaction completion date Contract Master Data date Autocall Startdate Start date Contract Master Data date Autocall Enddate Expiration Date Contract Master Data date Autocall Exists Duration Contract Master Data Integer Autocall Fee Front-end rate Contract Master Data Floating point numbers Autocall Company Computing Agency Contract Master Data String Autocall TradingLegID Transaction ID Structural data String Autocall StructureType Structure Type Structural data String Autocall AssetType Asset Class Structural data String Autocall CashType Position direction Structural data String Autocall AssessModel Valuation Model Structural data String Autocall InitialPrice Beginning Price Structural data Floating point numbers Autocall OptionType Option Direction Structural data String Autocall KnockoutFee Knock-out yield Structural data Floating point numbers Autocall KnockoutNo Knock out the observation day sequence Structural data String Autocall Underlying Target Code Target data String Autocall UnderlyingName Name of the target Target data String Autocall ExchangeCode Trading venue Target data String Autocall UnderlyingCategory The size of the target Target data String Autocall InitialPrice Beginning Price Structural data Floating point numbers Autocall OptionType Option Direction Structural data String Autocall KnockoutFee Knock-out yield Structural data Floating point numbers Autocall KnockoutNo Knock out the observation day sequence Structural data String Autocall Underlying Target Code Target data String Autocall UnderlyingName Name of the target Target data String Autocall ExchangeCode Trading venue Target data String Autocall UnderlyingCategory The size of the target Target data String Autocall

[0092] After processing in step 2 and step 3 of the present invention, the contract master data, structure data and subject data metadata sets are divided according to element categories, and a form display header is formed, wherein the form headers of the contract master data display area, the structure data display area and the subject data display area are respectively:

[0093] The table header of the contract master data display area includes: contract number, customer name, product name, transaction currency, transaction description, total option position, initial notional principal, transaction completion date, start date, expiration date, duration, front-end rate, and calculation agency;

[0094] The table header of the structure data display area: contract number, transaction number, structure type, asset category, position direction, valuation model, initial price, option direction, knock-out yield, and knock-out observation day sequence;

[0095] The form header of the target data display area includes: transaction number, target code, target name, transaction location, and target category.

[0096] Step 4 generates query conditions. According to whether it is a query condition attribute, in this example, only the contract number is used as the query condition, and the data type of the contract number is a string. Therefore, a text input box is generated in the query condition area for entering the contract number as the query condition. When the user enters the query condition in the query condition area and clicks the "Query" button, the query condition is first extracted and converted into a key-value pair, {"Tradeid":""}, and then sent to the background service system in the predetermined message format to apply for query form data. The encapsulated query condition format is shown below.

[0097] {

[0098] "ColumnCount":"1",

[0099] "ColumnData":[

[0100] {

[0101] "Column ID":"TradeId",

[0102] "value":""

[0103] }

[0104] }

[0105] When the backend receives the query conditions, it filters out the data that meets the conditions in the database, and then encapsulates the form data according to the predefined message format. After the front-end application system processes the form data through steps five and six, it fills the contract master data, structure data, and subject data into the corresponding display area for display. The result is as follows Figure 5 shown.

[0106] When adding new data, the user first fills in the data, and then the form container encapsulates the filled-in data according to the predetermined message format and sends it to the background service system. The background service system parses it according to the predefined message format, finds the corresponding column in the database according to the column identifier, generates data update SQL, and then updates the data. When deleting, the data to be deleted is also encapsulated according to the predetermined message format. After the background receives it, it generates data deletion SQL according to the element metadata name and deletes the data. When the user updates the data in the form container, the form container compares the original data with the current data, filters out the changed data, and then sends it to the background service system through the predefined message format. After the background service system parses the data, it generates update SQL to update and save the data.

[0107] Embodiment 2:

[0108] This embodiment provides an OTC derivatives multi-form data linkage display system, including a front-end application system and a back-end service system:

[0109] The foreground application system is used to obtain a set of element metadata from the background service system, parse the set of element metadata, and generate a form container; obtain multiple form data from the background service system, parse the multiple form data, parse and process the form data according to the attributes in the element metadata set, and then display it in the form container; at the same time, obtain the data added, deleted, and modified by the user in the form container, and send the changed data to the background service system for storage;

[0110] Backend service system: used to store feature metadata sets and provide query interfaces for the frontend application system to obtain feature metadata sets; store multi-form data and provide query and save interfaces for the frontend application system to obtain form data.

[0111] This system specifically includes the following modules:

[0112] Metadata set module: used to generate element metadata set; the element metadata set includes element metadata of contract master data, structure data and subject data;

[0113] Classification and sorting module: used to obtain the element metadata set, classify and sort it, and form the contract master data metadata set, structure data metadata set and target data metadata set;

[0114] Column editing module: used to generate a set of table header columns based on the element metadata set after classification and sorting, and set editing properties for each column;

[0115] Query condition module: used to generate a query condition area according to the element metadata set, and obtain the query condition input by the user based on the query condition area;

[0116] Form module: used to obtain form data according to the query conditions;

[0117] Output display module: used for formatting form data according to metadata format, forming data to be displayed and outputting and displaying the data to be displayed.

[0118] The system of this embodiment can be used to implement the method described in the first embodiment.

[0119] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0120] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0121] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0122] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0123] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the technical principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for displaying multi-form data linkage of over-the-counter derivatives, characterized in that: The following steps are involved: Generate an element metadata set; the element metadata set includes element metadata of contract master data, structure data and subject data; Obtain the element metadata set, classify and sort it, and form the contract master data metadata set, structure data metadata set and target data metadata set; Generate a set of table header columns based on the element metadata set after classification and sorting, and set editing properties for each column; Generate a query condition area according to the element metadata data set, and obtain a query condition input by a user based on the query condition area; Obtain form data according to the query conditions; Formatting the form data according to the metadata to form data to be displayed and outputting the data to be displayed; The data linkage display method also includes the linkage display processing of contract master data, structure data and subject data, including the following steps: When the user selects a certain contract master data in the contract master data display area, the structure data hash table to be displayed is taken out from the tail of the contract master data, and a structure data list containing N different structure types is obtained according to the key in the hash table, and filled into the structure data display area in the lower left corner; If the number of structure data lists N>1, the structure data of different structure types are displayed in tabs, and the title of each tab corresponds to the value of the structure type; When the user selects a certain structure data in the structure data display area, the hash table of the target data to be displayed is taken out from the tail of the current contract master data, and the list of display target data is taken out according to the transaction number in the structure data, and filled into the target data display area in the lower right corner for display; And / or, the data linkage display method further includes form data editing processing, including the following steps: When the user edits the form data, including adding, deleting, and updating, the corresponding edit control is generated according to the data type in the feature metadata, and the display data is filled into the edit control; After the user finishes editing, the updated value is obtained from the edit control and filled into the corresponding column of the form container.

2. The method for displaying multi-form data of over-the-counter derivatives according to claim 1, characterized in that: Methods for generating feature metadata datasets include: According to the structural characteristics of over-the-counter derivative products, the elements of the contract master data, structural data and underlying data are sorted out, and the corresponding element metadata is generated according to the data characteristics of each element to form an element metadata data set, which is stored in the element metadata data set database; The element metadata is the self-descriptive information of each element in the form, including element category, display name, column identifier, display sequence, data type, whether it is a query condition, whether it is editable, and structure type attributes, where the column identifier is the unique identifier of the element metadata; the element category includes contract master data, structure data, and subject data; The contract master data refers to a collection of identical elements in products of different structures; the contract master data uses the contract number as the unique identifier of the contract master data; The structural data refers to a collection of unique elements in products of different structures; the structural data uses a transaction number as a unique identifier of the structural data; the structural data stores a contract number to indicate the subordinate relationship between the structural data and the contract master data; The target data refers to the collection of target elements linked to products of different structures; the target data elements of different structural data are the same, and the target data includes transaction number, target code and transaction venue; the target code and transaction venue constitute the unique identification of the target data; the target data is used to indicate the subordinate relationship between the target data and the structural data.

3. The method for displaying multi-form data of over-the-counter derivatives according to claim 1, characterized in that: The methods for obtaining feature metadata data sets and performing classification and sorting processing include: Obtain a feature metadata dataset from a feature metadata dataset database; Classify the element metadata according to the element category, and store the element metadata of the contract master data, structure data and subject data in independent containers respectively; The element metadata in each independent container is sorted in ascending order according to the display sequence of the element metadata to form a contract main data metadata set, a structural data metadata set and a target data metadata set.

4. The method for displaying multi-form data of over-the-counter derivatives according to claim 1, characterized in that: The methods for generating a form display header column set and setting editing properties for each column include: Traverse the contract master data metadata set, add the metadata display name to the list, form the contract master data header column set, and bind the metadata editability and data type attributes to the corresponding columns; Traverse the structure data metadata set, add the display name of the metadata to the list, form a structure data header column set, bind the metadata editability and data type attributes to the corresponding columns, take out the element metadata named contract number from the contract master data metadata set, add its display name to the head of the structure data header column set, and mark this column as non-editable; Traverse the target data metadata set, add the metadata display name to the list, form the target data header column set, bind the metadata editability and data type attributes to the corresponding columns, take out the element metadata named transaction number from the structure data metadata set, add its display name to the head of the target data header column set, and mark this column as non-editable; After the contract main data table header set, structure data table header column set and subject data table header column set are generated, they are filled into the corresponding parts of the form data display area for display.

5. The method for displaying multi-form data linkage of over-the-counter derivatives according to claim 1, characterized in that: The methods for generating query condition areas based on feature metadata datasets include: Traverse the contract main data metadata set, structure data metadata set and target data metadata set, and extract the metadata whose query condition is TRUE separately; According to the data type of the metadata extracted separately, a corresponding input control is generated. The input control refers to a component used for the user to manually enter data. The input control is placed in the query condition area for the user to input query conditions.

6. The method for displaying multi-form data linkage of over-the-counter derivatives according to claim 5, characterized in that: Methods for obtaining form data based on query conditions include: According to the query conditions entered by the user in the query condition area, the query conditions are encapsulated into a predetermined message format; Get form data according to a predetermined message format; The form data is a two-dimensional data list, including column identifiers, element categories and structure types in element metadata, which is used to match the element metadata in the element metadata set, so as to parse it and display it in a specified column; the basic format of the predetermined message format is in the form of a key-value pair, the key is the column identifier of the element metadata, and the value is the actual data of the form data column.

7. The method for displaying multi-form data linkage of over-the-counter derivatives according to claim 1, characterized in that: Methods for formatting form data according to metadata to form data to be displayed include: Traverse the form data, extract a single row of data, traverse a single row of data, extract a single column of data, classify the column data according to the element category, and form a collection of contract master data, structure data and target data for a single row of data; Processing contract master data: traverse the contract master data set of a single row of data, extract a single contract master data column, find metadata in the contract master data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and place the result in the contract master data set to be displayed after processing; Processing structure data: traverse the structure data of a single row of data, extract a single structure data column, find metadata in the structure data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and after processing, put the result into the hash table of structure data to be displayed according to the structure type of the column data; the hash table of structure data to be displayed uses the structure type as the key; after traversal is completed, insert the hash table of structure data to be displayed into the tail of the contract master data set to be displayed; Process the target data: traverse the target data of a single row of data, extract a single target data column, find the metadata in the target data metadata set according to the column identifier in the data, process the data according to the data type of the metadata, and after processing, put the result into the hash table of the target data to be displayed according to the transaction number of the column data; the hash table of the target data to be displayed uses the transaction number as the key; after traversal, find the structure data to be displayed with the same transaction number in the hash table of the structure data to be displayed, and insert the hash table of the target data to be displayed into the tail of the set of main contract data to be displayed; After processing is completed, the contract master data set to be displayed is filled into the contract master data display area for display.

8. The method for displaying multi-form data linkage of over-the-counter derivatives according to claim 1, characterized in that: The data linkage display method also includes form data persistence processing, including the following steps: When the user edits the data in the form, the initial data and the latest data in the form container are compared, and the changed data is extracted to form a list of data to be sent; the list of data to be sent uses row data as basic elements, and the row data contains all column data, and each column data includes normal display data, column identifiers in element metadata, element categories, and structure types; The list to be sent is transmitted in a predetermined message format, processed and saved in a database.

9. An OTC derivatives multi-form data linkage display system, characterized in that: Used to execute the method as claimed in claim 1, including a foreground application system and a backend service system: The foreground application system is used to obtain a set of element metadata from the background service system, parse the set of element metadata, and generate a form container; Obtain form data from the backend service system and parse the form data. According to the attributes in the element metadata set, parse and process the form data and display it in the form container. At the same time, obtain the data added, deleted, and modified by the user in the form container, and send the changed data to the backend service system for storage; Backend service system: used to store feature metadata data sets and provide query interfaces for frontend application systems to obtain feature metadata data sets; Store form data and provide query and save interfaces for the front-end application system to obtain form data.

Images