CN111260477B - Writing and reading method and processing system for product object data information - Google Patents
Writing and reading method and processing system for product object data information Download PDFInfo
- Publication number
- CN111260477B CN111260477B CN201911215524.1A CN201911215524A CN111260477B CN 111260477 B CN111260477 B CN 111260477B CN 201911215524 A CN201911215524 A CN 201911215524A CN 111260477 B CN111260477 B CN 111260477B
- Authority
- CN
- China
- Prior art keywords
- product
- code
- model
- definition
- layer table
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/06—Asset management; Financial planning or analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Technology Law (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Human Resources & Organizations (AREA)
- Operations Research (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the application provides a writing and reading method and a processing system of data information of a product object, wherein the writing method comprises the following steps: establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; receiving first data information for a product object; extracting product code and model configuration data of a product object from the first data information; the model configuration data comprises service attribute field parameters; and writing the product codes and the business attribute field parameters into a product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table. Through the embodiment of the application, unified management of insurance product definition is realized, the line speed of insurance product definition is improved, and all insurance products can be flexibly defined.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a method and a processing system for writing and reading data information of a product object.
Background
Insurance products are a complex of tangible and intangible services offered by insurance companies for the marketplace. Insurance products in a narrow sense refer to financial instruments created by an insurance company that can be selected by customers to conduct transactions in the insurance market.
Along with the rapid development of the Internet, competitive pressures among insurance companies comprise slow online of insurance products, disordered codes, difficult operation bottleneck test, incapability of reusing cases for building test cases for each special product, difficult development, individual treatment of the products, insurance premium division of main and auxiliary insurance, insurance premium algorithm and special package verification, no independence in special treatment of the products, various products, universal insurance, serious illness insurance, red insurance, accidental insurance and the like, and numerous combinations and packages.
Disclosure of Invention
In view of the above, a method and a processing system for writing, reading data information of a product object are proposed to overcome or at least partially solve the above problems, comprising:
a method of writing product object data information, the method comprising:
establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
Receiving first data information for a product object;
extracting product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
and writing the product codes and the business attribute field parameters into a preset product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table.
Optionally, the step of writing the product code and the service attribute field parameter into the preset product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table includes:
determining a product model code corresponding to the product object from the data information of the product object;
determining a basic model code corresponding to the product model code from the product model layer table;
determining an object definition code corresponding to the basic model code from the product model definition layer table, and establishing a corresponding relation between the object definition code and the product code;
determining a field code corresponding to the object definition code from the product object definition layer table;
And writing the service attribute field parameters into the data table fields corresponding to the field codes in the preset product object data table.
Optionally, the basic model code includes a fixed model code and a dynamic model code, the service attribute field parameter includes a fixed service attribute field parameter and a dynamic service attribute field parameter, the fixed service attribute field parameter corresponds to the fixed model code, and the dynamic service attribute field parameter corresponds to the dynamic model code.
Optionally, the product model code corresponds to a product type of the product object, and the base model code corresponds to an item type of the product type.
Optionally, the product object is a product object for insurance business, and the product type includes any one or more of the following:
life risk type, red risk type, universal risk type, throw continuous risk type;
the transaction types include any one or more of the following:
policy definition matters, risk definition matters, responsibility definition matters, and claim record definition matters.
Optionally, the policy definition item, the risk definition item, and the base model code corresponding to the responsibility definition item are fixed model codes, and the base model code corresponding to the claim record definition item is dynamic model codes.
A method of reading product object data information, the method comprising:
establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
receiving a data information reading request for a product object; wherein the data information reading request comprises a product code corresponding to the product object;
searching a service attribute field parameter corresponding to the product code from a preset product object data table;
and generating second data information corresponding to the service attribute field parameters and publishing the second data information.
A processing system for product object data information, the system comprising writing means and reading means:
the writing device includes:
the first model table establishing module is used for establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
The first data information receiving module is used for receiving first data information aiming at the product object;
the extraction module is used for extracting the product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
the writing module is used for combining the product model definition layer table, the product model layer table and the product object definition layer table and writing the product codes and the service attribute field parameters into the product object data table;
the reading device includes:
the information receiving module is used for receiving a data information reading request aiming at a product object; wherein the data information reading request comprises a product code corresponding to the product object;
the searching module is used for searching the service attribute field parameters corresponding to the product codes from a preset product object data table;
and the reading module is used for generating and issuing second data information corresponding to the service attribute field parameters.
An electronic device comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, which computer program, when being executed by the processor, carries out the steps of the method of writing and reading product object data information as described above.
A computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of a method of writing and reading product object data information as described above. The embodiment of the application has the following advantages:
in the embodiment of the application, the product code and the model configuration data of the product object are extracted from the first data information by establishing the product model definition layer table, the product model layer table, the product object definition layer table and the product object data table, and the service attribute field parameters can be written into the product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table, so that unified management of insurance product definition is realized, the online speed of insurance product definition is improved, and all insurance products can be flexibly defined.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the description of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1 is a diagram of a model definition of product object data information according to one embodiment of the present application;
FIG. 2 is a model correspondence diagram of product object data information according to one embodiment of the present application;
FIG. 3 is a flowchart of a method for writing product object data information according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a method for reading data information of a product object according to an embodiment of the present application;
fig. 5 is a block diagram of a processing system for product object data information according to an embodiment of the present application.
Detailed Description
In order that the above-recited objects, features and advantages of the present application will become more readily apparent, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. It will be apparent that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
With the rapid development of the internet, competition pressure among insurance companies is increasing, and there are two main pressures, namely, pressure inside the company and pressure outside the company.
External pressure is mainly from traditional competitors, and in particular, market competition is increasingly strong, and market participants develop omnibearing competition in the fields of products, channels, operation, investment, customer service and the like.
External pressure comes from new participants, and in particular, internet companies are becoming new participants in industry with their own strong user portal control and take the initiative of internet channels.
External pressure also comes from new technologies, in particular, consumers are getting more initiative as new technologies (e.g., mobile interconnect, big data, etc.) continue to mature.
The internal pressure is mainly reflected in that products are slow to be online and run, product codes are chaotic, operation is bottleneck, testing is difficult, testing cases need to be built for each special product, the cases cannot be reused, testing data can be manually created, product development is difficult, individual processing of the products, insurance premium division of main insurance and auxiliary insurance, insurance premium algorithm and package special verification are difficult, special processing of the products is not independent, the types of the products are various, universal insurance, serious disease insurance, red insurance, accidental insurance and the like are combined, and packages are numerous.
To cope with the pressures of the two aspects, this can be achieved by three product models: an easy-to-secure product model, a middle-family soft product model, and an IBM product model.
The easy-to-protect product model is characterized in that a classification mode is used for modeling, then a large amount of stored processes and java codes are used for calculation and rule processing, and a foreground definition interface is provided; the method has the advantages that 1) the calculation is java code and storage process, the processing speed is relatively high, and 2) the service user can configure the product: if the type is supported by the system, the configuration can be carried out by a fine calculation or an operator; the disadvantage is (1) poor expansibility; (2) complex definition; (3) the refined data table is too large.
The middle-family soft product model is characterized in that (1) a model of a plane is compared, (2) a database table and SQL sentences are used for defining products, rules and calculation; the method has the advantages that (1) the configuration is simple, the expandability is strong, and (2) the product which can be rapidly configured is developed: the development is simpler, and (3) the data table is designed to be independent of each product, so that the data size is small; the disadvantage is mainly a performance problem.
The IBM product model is characterized in that (1) tree-type classification mode modeling is used, (2) the model is defined only and does not comprise implementation, and the IBM product model has the advantages that (1) a reference model and a modeling tool are provided, (2) the definition capability is strong, the expansion capability is strong, and the defects that (1) the model is difficult to land are overcome; (2) national conditions, enterprises, finances, and supervision differences.
Specifically, during the product on-line process, product data may be stored as follows:
three tables, MAPP (product table), MRISK (seed risk table), MDUTY (responsibility table) are stored in the database.
The data for the three tables are as follows:
MAPP (product table):
ID: water flow number
Productid: product coding
PRODUCTNAME: product name
Valid ate: expiration date
FLAG: whether or not to avoid claims
| ID | PRODUCTID | PRODUCTNAME | VALIDATE | FLAG |
| 1 | P000001 | Taikang and ease life accident risk | 1Y | 1 |
MRISK (risk table):
ID: water flow number
RISKID: dangerous seed code
RISKNAME: dangerous seed name
Productid: product coding
PREM: premium for premium
MDUTY (responsibility table):
ID: water flow number
DUTYID: responsibility encoding
DUTYNAME: name of responsibility
Productid: product coding
RISKID: dangerous seed code
PREM: premium for premium
| ID | DUTYID | DUTYNAME | PRODUCTID | RISKID | PREM |
| 1 | D000001 | Accidental injury of aircraft | P000001 | R000001 | 5 |
| 2 | D000002 | Other accidental injuries | P000001 | R000001 | 5 |
| 3 | D000003 | Accident of airplane | P000001 | R000002 | 10 |
| 4 | D000004 | Other unexpected statues | P000001 | R000002 | 10 |
When the program acquires the data information, the database acquisition information needs to be directly read, and if additional information needs to be added, the table structure needs to be modified.
Referring to fig. 1, a model definition diagram of product object data information provided in an embodiment of the present application is shown, where a product may be defined into two layers, namely a product layer and a model layer, and specifically, the product layer may be further divided into an object definition layer and an object layer, and the model layer may be divided into a model definition layer and a model layer.
The model definition layer is responsible for defining the type of the product and the overall structure thereof, and can be stored through a model definition layer table, wherein the model layer is related to data in the model table, can be stored through a product model layer table, the object definition layer can be used for defining field attributes of sub-models in the model definition layer, can be stored through a product object definition layer table related to product definition, the object layer can be related to data of the object definition layer, and the object definition layer and the object layer are related to each other and can be stored through a product object data table. .
Referring to fig. 2, a model correspondence diagram of product object data information provided in an embodiment of the present application is shown, where a model definition layer is responsible for defining types of products and their overall structures, and for example, all products may be divided into four types: life insurance product model, red-division product model, universal insurance product model and continuous insurance product model.
The model layer defines information of sub-models corresponding to the product model, as shown in fig. 2, and for the life insurance product model, the model corresponds to two types of models, namely a fixed model and a dynamic model, wherein the fixed model comprises three sub-models which can be respectively: insurance definition model, risk definition model, responsibility definition model. The dynamic model comprises a special model corresponding to the life insurance product, and can be specifically defined for the claim records, and all the product models can be defined by adding the dynamic model into the fixed model.
Referring to fig. 3, a flowchart of a method for writing product object data information according to an embodiment of the present application is shown, which specifically may include the following steps:
step 301, building a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
before writing the product object data information, a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table can be established;
the product model definition layer table can be shown in the following table and can be used for storing the corresponding relation between the product model codes and the basic model codes;
| ID | basic model coding | Basic model name |
| 1 | MB0001 | Policy definition model |
| 2 | MB0002 | Dangerous seed definition model |
| 3 | MB0003 | Responsibility definition model |
| 4 | MB0004 | Definition record model for claims |
The product model layer table can be shown in the following table and can be used for storing the corresponding relation between the product model codes and the basic model codes;
| ID | product model coding | Insurance model name | Type(s) | Basic model coding |
| 1 | MM0001 | Life insurance product model | Fixed model | MB0001 |
| 2 | MM0001 | Life insurance product model | Fixed model | MB0002 |
| 3 | MM0001 | Life insurance product model | Fixed model | MB0003 |
| 4 | MM0001 | Life insurance product model | Dynamic model | MB0004 |
The product object definition layer table may be used to store the correspondence between object definition codes and field codes as shown in the following table:
the product object data table may be used to store the correspondence between field codes and service attribute field parameters as shown in the following table:
step 302, receiving first data information for a product object;
the first data information is specific content contained in the product object, for example, a name of the product, an explanation of the product or a use method of the product.
Before the product is specifically written, the first data information of the product object may be received first, and in the actual receiving process, the first data information of the product object sent by the external client may be received, or the first data information of the product object stored in the receiving and storing device may be directly read, or the first data information of the product object may be received in other manners.
In an embodiment of the present application, the product object is a product object for an insurance service, and the product type includes any one or more of the following:
life risk type, red risk type, universal risk type, throw continuous risk type;
the event types include any one or more of the following:
policy definition matters, risk definition matters, responsibility definition matters, and claim record definition matters.
In an embodiment of the present application, the basic model codes corresponding to the policy definition items, the risk definition items, and the liability definition items are fixed model codes, and the basic model codes corresponding to the claim record definition items are dynamic model codes.
Step 303, extracting product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
wherein the product code may be unique code information for each product, with only one product code for each product.
In practical application, the model configuration data is specific data information of the product, and may include a name of the product, an explanation of the product or a usage method of the product, where one model configuration data corresponds to one product code.
The service attribute field parameters are parameters which are specifically filled in during storage.
The product code may be located in a first data byte of the model configuration data, after receiving the first data information of the product object, the data packet corresponding to the model configuration data may be extracted first, and then the model configuration data and the data of the corresponding first data byte are separated, that is, the product code and the model configuration data of the product object are extracted, where the model configuration data includes the service attribute field parameters.
In an embodiment of the present application, the service attribute field parameters include a fixed service attribute field parameter and a dynamic service attribute field parameter, where the fixed service attribute field parameter corresponds to a fixed model code, and the dynamic service attribute field parameter corresponds to a dynamic model code.
Step 304, writing the product codes and the service attribute field parameters into a preset product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table.
The preset product object data table is a preset data table and is used for storing all data information of the product.
After the product code and model configuration data of the product object are extracted, a product model definition layer table, a product model layer table and a product object definition layer table are combined to obtain a space corresponding to the product code and corresponding service attribute field parameters, and then the product code and the corresponding service attribute field parameters are written into the corresponding space.
As an embodiment, writing the product code and the service attribute field parameters into the preset product object data table further comprises the following sub-steps:
s11, determining a product model code corresponding to the product object from the data information of the product object;
wherein the product model code is a code corresponding to a product model, which may be composed of a plurality of small models, one for each product, and one for each product model.
The product model code may be included in the data information of the product object by a single data packet, and after the data information of the product object is received, the data packet corresponding to the product model code may be extracted from the data information of the product object, and the data packet corresponding to the product model code may be parsed to determine the product model code corresponding to the product object.
In an embodiment of the present application, the product model code corresponds to a product type of the product object, and the base model code corresponds to a transaction type of the product type.
S12, determining a basic model code corresponding to the product model code from a product model layer table;
wherein the base model is a small model that constitutes the product model, which may include a plurality of small model structures.
The basic model codes are codes corresponding to the basic model, and the basic model codes are in one-to-one correspondence with the basic model codes.
The base model code corresponding to the product model code may be determined in a stored model correspondence table, for example, as shown in the following table:
| ID | insurance model code | Insurance model name | Type(s) | Corresponding code |
| 1 | MM0001 | Life insurance product model | Fixed model | MB0001 |
| 2 | MM0001 | Life insurance product model | Fixed model | MB0002 |
| 3 | MM0001 | Life insurance product model | Fixed model | MB0003 |
| 4 | MM0001 | Life insurance product model | Dynamic model | MB0004 |
In a specific implementation, a product model layer table is obtained first, the content of the product model layer table is identified, then, from the product model layer table, a product model code corresponding to a product object is determined, and a basic model code corresponding to the product model code is obtained, for example, as shown in the table above, if the product model code is identified as MM0001, then, the basic model codes corresponding to the product model code are determined as MB0001, MB0002, MB0003 and MB0004.
In an embodiment of the present application, the base model coding includes fixed model coding and dynamic model coding.
S13, determining an object definition code corresponding to the basic model code from a product model definition layer table, and establishing a corresponding relation between the object definition code and the product code;
Wherein the object definition code is a code corresponding to the small model structure.
In a specific implementation, a product model definition layer table is firstly obtained, the content of the product model definition layer table is identified, then a basic model code corresponding to the product model code is determined from the product model definition layer table, specifically, a basic model name corresponding to the basic model code can be obtained in a model basic table, and after the basic model name is obtained, an object definition code can be determined in an object structure definition table through the object definition name and the model code.
S14, determining field codes corresponding to the object definition codes from the product object definition layer table;
wherein a field code may correspond to a piece of content of the product information.
In a specific implementation, a product object definition layer table is acquired first, the content of the product object definition layer table is identified, then an object definition code is determined from the product object definition layer table, and specifically, a field code corresponding to the object definition code can be acquired in the object data definition table.
And S15, writing the parameters of the service attribute field into the data table field corresponding to the field code in the data table of the product object.
After determining the field code corresponding to the object definition code, the service attribute field parameter may be written into the data table field corresponding to the field code.
In the embodiment of the application, first data information aiming at a product object is received by establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; and extracting product code and model configuration data of the product object from the first data information, wherein the model configuration data comprises service attribute field parameters, and writing the product code and the service attribute field parameters into the product object data table in combination with the product model definition layer table, the product model layer table and the product object definition layer table, so that the line speed of insurance product definition is improved, unified management of insurance product definition is realized, and all insurance products can be flexibly defined.
Referring to fig. 4, a flowchart illustrating steps of a method for reading product object data information according to an embodiment of the present application may specifically include the following steps:
step 401, building a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
Step 402, receiving a data information reading request for a product object; wherein the data information reading request comprises a product code corresponding to the product object;
receiving a data information reading request for a product object, for example, a product query request of a customer; the data information reading request includes a product code corresponding to the product object, for example, a policy underwriting of the client includes a product number in the policy underwriting, and the product number is used to refer to a specific product.
Step 403, searching the service attribute field parameters corresponding to the product codes from a preset product object data table;
searching a product code in a preset product object data table, and searching a service attribute field corresponding to the product code.
And step 404, generating second data information corresponding to the service attribute field parameters and publishing.
Wherein the second data information is product information stored in the product object data table corresponding to the business attribute field parameter.
And after the service attribute field corresponding to the product code is found in the preset product object data table, extracting the second data information corresponding to the service attribute field, and sending the second data information to the client.
In the embodiment of the application, first data information aiming at a product object is received by establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; and extracting product code and model configuration data of the product object from the first data information, wherein the model configuration data comprises service attribute field parameters, and writing the product code and the service attribute field parameters into the product object data table in combination with the product model definition layer table, the product model layer table and the product object definition layer table, so that the line speed of insurance product definition is improved, unified management of insurance product definition is realized, and all insurance products can be flexibly defined.
Referring to fig. 5, there is shown a block diagram of a processing system for product object data information according to an embodiment of the present application, the system includes a writing device 510 and a reading device 520:
the writing device 510 may include the following modules:
a first model table establishing module 511, configured to establish a product model definition layer table, a product model layer table, a product object definition layer table, and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
A first data information receiving module 512 for receiving first data information for a product object;
an extracting module 513, configured to extract product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
a writing module 514, configured to combine the product model definition layer table, the product model layer table, and the product object definition layer table, and write the product code and the service attribute field parameter into the product object data table.
In an embodiment of the present application, the writing module 514 further includes the following sub-modules:
the product model code confirming sub-module is used for determining a product model code corresponding to the product object from the data information of the product object;
a basic model code confirmation sub-module, configured to determine, from the product model layer table, a basic model code corresponding to the product model code;
a product code corresponding sub-module, configured to determine an object definition code corresponding to the basic model code from the product model definition layer table, and establish a corresponding relationship between the object definition code and the product code;
A field code corresponding sub-module, configured to determine, from the product object definition layer table, a field code corresponding to the object definition code;
and the business attribute field parameter writing sub-module is used for writing the business attribute field parameter into a data table field corresponding to the field code in the product object data table.
In an embodiment of the present application, the basic model code includes a fixed model code and a dynamic model code, the service attribute field parameter includes a fixed service attribute field parameter and a dynamic service attribute field parameter, the fixed service attribute field parameter corresponds to the fixed model code, and the dynamic service attribute field parameter corresponds to the dynamic model code.
In an embodiment of the present application, the product model code corresponds to a product type of the product object, and the base model code corresponds to an item type of the product type.
In an embodiment of the present application, the product object is a product object for insurance business, and the product type includes any one or more of the following:
life risk type, red risk type, universal risk type, throw continuous risk type;
The transaction types include any one or more of the following:
policy definition matters, risk definition matters, responsibility definition matters, and claim record definition matters.
In an embodiment of the present application, the policy definition item, the risk definition item, and the base model code corresponding to the responsibility definition item are fixed model codes, and the base model code corresponding to the claim record definition item is dynamic model codes.
The reading device 520 may include the following modules:
an information receiving module 521 for receiving a data information reading request for a product object; wherein the data information reading request comprises a product code corresponding to the product object;
a searching module 522, configured to search, from a preset product object data table, a service attribute field parameter corresponding to the product code;
and the reading module 523 is configured to generate and issue second data information corresponding to the service attribute field parameter.
In the embodiment of the application, a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table are established; receiving first data information aiming at a product object, extracting product code and model configuration data of the product object from the first data information, wherein the model configuration data comprises service attribute field parameters, and writing the product code and the service attribute field parameters into a product object data table by combining a product model definition layer table, a product model layer table and a product object definition layer table, so that the online speed of insurance product definition is improved, unified management of insurance product definition is realized, and all insurance products can be flexibly defined.
For the system embodiments of the present application, the description is relatively simple, as it is substantially similar to the method embodiments, and reference should be made to the description of the method embodiments for relevant points.
An embodiment of the present application further provides an electronic device, which may include a processor, a memory, and a computer program stored on the memory and capable of running on the processor, where the computer program is executed by the processor to implement the steps of a method for writing and reading product object data information as described above.
An embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps of a method for writing and reading product object data information as described above.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
It will be apparent to those skilled in the art that embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present embodiments have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the present application.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.
The foregoing has described in detail the method and system for writing and reading data information of a product object, and specific examples are applied to illustrate the principles and embodiments of the present application, and the above examples are only used to help understand the method and core idea of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (9)
1. A method of writing product object data information, the method comprising:
establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
Receiving first data information for a product object;
extracting product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
writing the product codes and the business attribute field parameters into the product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table;
wherein the step of writing the product code and the business attribute field parameters into the product object data table by combining the product model definition layer table, the product model layer table and the product object definition layer table comprises the following steps:
determining a product model code corresponding to the product object from the data information of the product object;
determining a basic model code corresponding to the product model code from the product model layer table;
determining an object definition code corresponding to the basic model code from the product model definition layer table, and establishing a corresponding relation between the object definition code and the product code;
determining a field code corresponding to the object definition code from the product object definition layer table;
And writing the service attribute field parameters into the data table fields corresponding to the field codes in the product object data table.
2. The method of claim 1, wherein the base model code comprises a fixed model code and a dynamic model code, wherein the business attribute field parameters comprise a fixed business attribute field parameter and a dynamic business attribute field parameter, wherein the fixed business attribute field parameter corresponds to the fixed model code, and wherein the dynamic business attribute field parameter corresponds to the dynamic model code.
3. The method of claim 1, wherein the product model code corresponds to a product type of the product object, and wherein the base model code corresponds to an item type of the product type.
4. A method according to claim 3, wherein the product object is a product object for an insurance service, the product type comprising any one or more of the following:
life risk type, red risk type, universal risk type, throw continuous risk type;
the transaction types include any one or more of the following:
policy definition matters, risk definition matters, responsibility definition matters, and claim record definition matters.
5. The method of claim 4, wherein the base model code for the policy definition item, the risk definition item, and the liability definition item is a fixed model code and the base model code for the claims records definition item is a dynamic model code.
6. A method of reading product object data information, the method comprising:
establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
receiving a data information reading request for a product object; wherein the data information reading request comprises a product code corresponding to the product object;
searching a service attribute field parameter corresponding to the product code from a preset product object data table;
Generating second data information corresponding to the service attribute field parameters and publishing the second data information;
wherein the product object data table is generated by:
receiving first data information for a product object;
extracting product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
determining a product model code corresponding to the product object from the data information of the product object;
determining a basic model code corresponding to the product model code from the product model layer table;
determining an object definition code corresponding to the basic model code from the product model definition layer table, and establishing a corresponding relation between the object definition code and the product code;
determining a field code corresponding to the object definition code from the product object definition layer table;
and writing the service attribute field parameters into the data table fields corresponding to the field codes in the product object data table.
7. A system for processing product object data information, the system comprising writing means and reading means:
The writing device includes:
the first model table establishing module is used for establishing a product model definition layer table, a product model layer table, a product object definition layer table and a product object data table; the product model layer table is used for storing the corresponding relation between the product model code and the basic model code, the product model definition layer table is used for storing the corresponding relation between the basic model code and the object definition code, the product object definition layer table is used for storing the corresponding relation between the object definition code and the field code, and the product object data table is used for storing the corresponding relation between the field code and the service attribute field parameter;
the first data information receiving module is used for receiving first data information aiming at the product object;
the extraction module is used for extracting the product code and model configuration data of the product object from the first data information; wherein the model configuration data includes business attribute field parameters;
the writing module is used for combining the product model definition layer table, the product model layer table and the product object definition layer table and writing the product codes and the service attribute field parameters into the product object data table;
The writing module further comprises the following sub-modules:
the product model code confirming sub-module is used for determining a product model code corresponding to the product object from the data information of the product object;
a basic model code confirmation sub-module, configured to determine, from the product model layer table, a basic model code corresponding to the product model code;
a product code corresponding sub-module, configured to determine an object definition code corresponding to the basic model code from the product model definition layer table, and establish a corresponding relationship between the object definition code and the product code;
a field code corresponding sub-module, configured to determine, from the product object definition layer table, a field code corresponding to the object definition code;
a service attribute field parameter writing sub-module, configured to write, in the product object data table, the service attribute field parameter into a data table field corresponding to the field code;
the reading device includes:
the information receiving module is used for receiving a data information reading request aiming at a product object; wherein the data information reading request comprises a product code corresponding to the product object;
The searching module is used for searching the service attribute field parameters corresponding to the product codes from a preset product object data table;
and the reading module is used for generating and issuing second data information corresponding to the service attribute field parameters.
8. An electronic device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program implementing the steps of a method of writing and reading product object data information according to any one of claims 1 to 6 when executed by the processor.
9. A computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, carries out the steps of a method of writing and reading product object data information according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911215524.1A CN111260477B (en) | 2019-12-02 | 2019-12-02 | Writing and reading method and processing system for product object data information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911215524.1A CN111260477B (en) | 2019-12-02 | 2019-12-02 | Writing and reading method and processing system for product object data information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111260477A CN111260477A (en) | 2020-06-09 |
| CN111260477B true CN111260477B (en) | 2023-07-25 |
Family
ID=70948536
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911215524.1A Active CN111260477B (en) | 2019-12-02 | 2019-12-02 | Writing and reading method and processing system for product object data information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111260477B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105303287A (en) * | 2014-05-30 | 2016-02-03 | 艾玛迪斯简易股份公司 | A method and a system for managing a record data structure |
| JP2016170469A (en) * | 2015-03-11 | 2016-09-23 | ニッセイ情報テクノロジー株式会社 | Insurance application system, insurance application method and program |
| CN108257013A (en) * | 2016-12-28 | 2018-07-06 | 平安科技（深圳）有限公司 | Insurance products define method and device |
| CN109445759A (en) * | 2018-09-28 | 2019-03-08 | 中国平安人寿保险股份有限公司 | Generation method, device, computer equipment and the storage medium of insurance products |
| CN109460527A (en) * | 2018-09-25 | 2019-03-12 | 中国平安人寿保险股份有限公司 | Product data configuration method, device, computer equipment and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070214020A1 (en) * | 2003-03-18 | 2007-09-13 | Balaji Srinivasan | Modeling of insurance product data |
| US20120053964A1 (en) * | 2010-08-30 | 2012-03-01 | Williams Sarah A | Systems and methods for online insurance financial planning |
| US20150178851A1 (en) * | 2013-12-19 | 2015-06-25 | Guidewire Software, Inc. | Insurance product model relationships |
-
2019
- 2019-12-02 CN CN201911215524.1A patent/CN111260477B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105303287A (en) * | 2014-05-30 | 2016-02-03 | 艾玛迪斯简易股份公司 | A method and a system for managing a record data structure |
| JP2016170469A (en) * | 2015-03-11 | 2016-09-23 | ニッセイ情報テクノロジー株式会社 | Insurance application system, insurance application method and program |
| CN108257013A (en) * | 2016-12-28 | 2018-07-06 | 平安科技（深圳）有限公司 | Insurance products define method and device |
| CN109460527A (en) * | 2018-09-25 | 2019-03-12 | 中国平安人寿保险股份有限公司 | Product data configuration method, device, computer equipment and storage medium |
| CN109445759A (en) * | 2018-09-28 | 2019-03-08 | 中国平安人寿保险股份有限公司 | Generation method, device, computer equipment and the storage medium of insurance products |
Non-Patent Citations (1)
| Title |
|---|
| 崔新友 ; 杨柳 ; 雷磊 ; .保险业数据仓库的设计.科技信息.2010,(19),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111260477A (en) | 2020-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10713654B2 (en) | Enterprise blockchains and transactional systems | |
| US10339038B1 (en) | Method and system for generating production data pattern driven test data | |
| CN103620601B (en) | Joining tables in a mapreduce procedure | |
| CN107123047B (en) | Data acquisition system based on bond transaction and data acquisition method thereof | |
| EP3168758A1 (en) | Data storage method, query method and device | |
| CN106326248A (en) | A storage method and device for data of databases | |
| CN104765745B (en) | Loading data in database are carried out with the method and system of logic checking | |
| CN112115152B (en) | Data increment updating and inquiring method and device, electronic equipment and storage medium | |
| US9600602B2 (en) | Combined deterministic and probabilistic matching for data management | |
| CN111597177A (en) | Data governance method for improving data quality | |
| CN110704486B (en) | Data processing method, device, system, storage medium and server | |
| US10248668B2 (en) | Mapping database structure to software | |
| CN110941488A (en) | Task processing method, device, equipment and storage medium | |
| CN113468160A (en) | Data management method and device and electronic equipment | |
| CN112699142A (en) | Cold and hot data processing method and device, electronic equipment and storage medium | |
| CN111260477B (en) | Writing and reading method and processing system for product object data information | |
| CN114398562B (en) | Shop data management method, device, equipment and storage medium | |
| CN115908062A (en) | Intellectual property full-period management system | |
| CN110941952A (en) | Method and device for perfecting audit analysis model | |
| CN115329395A (en) | Database data processing method, device, system, equipment and storage medium | |
| CN114691768A (en) | Data processing method, accounting system and related equipment | |
| CN109783559A (en) | Acquisition methods, device, electronic equipment and the storage medium of house prosperity transaction data | |
| CN114036174B (en) | Data updating method, device, equipment and storage medium | |
| CN111783152B (en) | Method and system for generating tamper-proof abstract of accounting based on decision tree | |
| CN114912818B (en) | Asset index analysis method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |