Catastrophe insurance loss redistribution module and method for realizing loss redistribution

Abstract

The present invention mainly relates to a catastrophe insurance loss redistribution module and a method for realizing loss redistribution. First, a plurality of risk source nodes participating in the merger and a plurality of first contract nodes to be associated with the risk source nodes participating in the merger are created; at least one split component is created and associated with at least one first contract node, and the split component is configured to: define the risk source nodes participating in the merger and the risk destination nodes after the split; associate each risk destination node after the split with a second contract node associated with a certain risk source node or certain risk source nodes; on this basis, a method for realizing catastrophe insurance loss redistribution in reinsurance business based on the catastrophe insurance loss redistribution module is also proposed. The present invention can realize the function of merging the loss results of multiple risks and the function of redistributing the mixed losses of catastrophe insurance.

Description

Technical Field

[0001] The present invention relates to the field of reinsurance business, and in particular to a catastrophe insurance loss redistribution module and a method for realizing loss redistribution. Background Art

[0002] When reinsurers underwrite risks for direct insurers, they usually provide specific contractual terms for the risks ceded by the direct insurers. Therefore, each catastrophe underwriting business in reinsurance business is generally composed of catastrophe risks and underwriting contracts. The risks accepted by this business have different sources and forms. The risks (Risk) in the business can be given in the form of an event model (ELT), or an event occurrence table (YLT) can be further generated based on the event model. All event information is recorded in the form of an array, and the data at the corresponding position of each array constitutes a YLT data, which records in detail the loss value caused by a catastrophe event at a certain time.

[0003] In some business situations, before calculating several risks according to the underwriting contract, it is necessary to first know the total losses of several risks. After each of them is calculated according to the relevant terms of the contract, the loss result after the contract calculation will be generated. Therefore, the total loss before entering the contract and the calculated total loss after entering the contract have a one-to-one corresponding YLT data. In some business situations, the loss result after entering the contract needs to be split back into the losses calculated according to the contract for different risks. The above-mentioned losses calculated according to the contract for different risks may also be used as the reinsurance business of other reinsurance companies to sign reinsurance contracts.

[0004] At present, the reinsurance field needs a system that can calculate losses for different business situations, especially catastrophic business losses, which requires the redistribution of losses through well-designed tools and algorithms. So far, there is no computing system or computer program product in the industry that can fully meet this demand. Summary of the invention

[0005] In view of the technical problems in the art, the present invention relates, on one hand, to a method for creating a catastrophe insurance loss redistribution module, comprising the following steps:

[0006] Creating a number of risk source nodes participating in the merger and a number of first contract nodes to be associated with the risk source nodes;

[0007] At least one split component is created and associated with at least one first contract node, the split component being configured to:

[0008] Define the risk source nodes involved in the merger and the risk destination nodes after the split;

[0009] Each of the risk destination nodes is associated with a second contract node associated with a certain risk source node or certain risk source nodes.

[0010] The present invention also relates to a method for realizing catastrophe insurance loss redistribution in reinsurance business based on a catastrophe insurance loss redistribution module, comprising the following steps:

[0011] According to the underwriting relationship between the risks and contracts involved in the current reinsurance business, the corresponding catastrophe insurance loss redistribution module is introduced;

[0012] Configure a YLT data table for each risk source node participating in the merger, wherein the YLT data table includes an occurrence time list TR, an event identifier list EID, a risk type list RID, and a loss value list Loss;

[0013] Merge the YLT data tables of all risk source nodes involved in the merger to obtain a mixed YLT data table;

[0014] The mixed YLT data table is processed by the first contract node to obtain a calculated mixed YLT data table;

[0015] The calculated mixed YLT data table is processed through a number of risk destination nodes to obtain a split YLT data table for each risk destination node;

[0016] The split YLT data table is calculated through the second contract node to obtain the split YLT data table.

[0017] The present invention also relates to a computer program product, comprising a computer program / instruction, which implements the steps of the method proposed by the present invention when the computer program / instruction is executed by a processor.

[0018] The present invention also relates to a computing system for realizing the redistribution of catastrophe insurance losses in reinsurance business. The computing system implements the steps of the method proposed by the present invention when running.

[0019] Aiming at different business situations in the field of reinsurance, the present invention proposes a complete technical solution, including a catastrophe business loss calculation system and related tools and algorithms, which can not only realize the function of merging the loss results of multiple risks, but also realize the function of redistributing the mixed losses of catastrophe insurance. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 , one The structural model diagram of some catastrophe insurance loss redistribution modules;

[0021] Figure 2 , one Flow charts of a method for realizing catastrophe insurance loss redistribution in reinsurance business based on a catastrophe insurance loss redistribution module;

[0022] Figure 3 , one Reinsurance business structure diagram in some implementation methods;

[0023] Figure 4 , business structure diagram after using approximate business construction method.

[0024] The Chinese nouns corresponding to the English nouns in the attached figure are: Risk, contract, Loss, SourceSplitter redistribution functional component, SourceNode participating in the merging node, and DestinationNode the final node of the split. DETAILED DESCRIPTION

[0025] Some embodiments involve Figure 1 A catastrophe insurance loss redistribution module is provided, and a method for creating such a module includes the following steps:

[0026] Create a number of risk source nodes participating in the merger and a number of first contract nodes to be associated with the risk source nodes participating in the merger;

[0027] At least one split component is created and associated with at least one first contract node, the split component being configured to:

[0028] Define the risk source nodes involved in the merger and the risk destination nodes after the split;

[0029] Each split risk destination node is associated with a second contract node associated with a certain risk source node or certain risk source nodes.

[0030] Here, the term "module" generally includes any collection of executable codes and data that can be loaded into memory and run, which can be a component of a large program instruction and can include components and / or nodes.

[0031] Some embodiments involve processes such as Figure 2 The method for realizing catastrophe insurance loss redistribution in reinsurance business based on the catastrophe insurance loss redistribution module shown includes the following steps:

[0032] According to the underwriting relationship between the risks and contracts involved in the current reinsurance business, the corresponding catastrophe insurance loss redistribution module is introduced;

[0033] Configure the YLT data table for each risk source node involved in the merger. The YLT data table includes the occurrence time list TR, event identification list EID, risk type list RID, and loss value list Loss;

[0034] Merge the YLT data tables of all risk source nodes involved in the merger to obtain a mixed YLT data table;

[0035] The mixed YLT data table is processed by the first contract node to obtain a calculated mixed YLT data table;

[0036] Calculate the mixed YLT data table through several risk destination nodes to obtain the split YLT data table of each risk destination node;

[0037] The split YLT data table is calculated and split through the second contract node to obtain the split YLT data table.

[0038] Among them, YLT is the actual occurrence table of events generated by event simulation based on ELT. Assuming that the occurrence of events within 100,000 years is simulated, the actual occurrence of events after random simulation is shown in Table 1:

[0039] Table 1. Actual occurrence YLT

[0040]

[0041] Some embodiments involve obtaining a hybrid YLT data table, specifically comprising the following steps:

[0042] Create the first index Index1 and the second index Index2;

[0043] Sort the YLT data table YLT1 of the first risk source node and the YLT data table YLT2 of the second risk source node involved in the merger in order of occurrence time from small to large, to obtain sorting YLT1 and sorting YLT2;

[0044] Compare the occurrence time of sorted YLT1 with the occurrence time of sorted YLT2 in sequence, and record the YLT data corresponding to the smaller occurrence time value as the current mixed YLT data, traversing sorted YLT1 and sorted YLT2;

[0045] Traverse Index1 and record the current index value as Index1_i and its order i. At the same time: record the i-th value in the occurrence time list TR1 of sorted YLT1 as the Index1_i occurrence time value of the mixed YLT data table, record the i-th value in the event identification list EID1 of sorted YLT1 as the Index1_i event identification value of the mixed YLT data table, and record the i-th value in the loss value list Loss1 of sorted YLT1 as the Index1_i loss value in the mixed YLT data table;

[0046] Traverse Index2 and record the current index value as Index2_j and its order j. At the same time: record the j-th value in the occurrence time list TR2 of sorted YLT2 as the Index2_j occurrence time value of the mixed YLT data table, record the j-th value in the event identification list EID2 of sorted YLT2 as the Index2_j event identification value of the mixed YLT data table, and record the j-th value in the loss value list Loss2 of sorted YLT2 as the Index2_j loss value in the mixed YLT data table.

[0047] Preferably, if the occurrence time of the sorted YLT1 is equal to the occurrence time of the sorted YLT2, the risk type of the sorted YLT1 is compared with the risk type of the sorted YLT2, and the YLT data corresponding to the smaller value of the risk type is recorded as the current mixed YLT data;

[0048] Preferably, if the risk type of the sorted YLT1 is the same as the risk type of the sorted YLT2, the event identifier of the sorted YLT1 is compared with the event identifier of the sorted YLT2, and the YLT data corresponding to the smaller value of the risk identifier is recorded as the current mixed YLT data;

[0049] Preferably, if the event identifier of the sequence YLT1 is the same as the event identifier of the sequence YLT2, the YLT data corresponding to the sequence YLT1 and / or the sequence YLT2 are recorded as the current mixed YLT data.

[0050] Some embodiments also involve obtaining a split YLT data table, which specifically includes the following steps:

[0051] Starting from calculating the first data in the mixed YLT data table, the YLT data table of the first risk destination node, and the mixed YLT data table, according to the following formula, traverse and calculate the mixed YLT data table, the YLT data table of the first risk destination node, and the mixed YLT data table to obtain the loss value of the split YLT data table:

[0052] ResultLoss[m]=AllocSource Loss[m]×Loss1[n] / SourceAggLoss[m]

[0053] Among them, AllocSourceLoss[m] is the mth loss value calculated in the hybrid YLT data table, Loss1[n] is the nth loss value in the YLT data table of the first risk destination node, SourceAggLoss[m] is the mth loss value in the hybrid YLT data table, and ResultLoss[m] is the mth loss value in the YLT data table of the first risk destination node.

[0054] Some embodiments further involve the following steps:

[0055] Starting from the first data of the calculation hybrid YLT data table and the YLT data table of the first risk destination node, traverse the calculation hybrid YLT data table and the YLT data table of the first risk destination node, and compare the mth occurrence time of the calculation hybrid YLT data table and the nth occurrence time of the YLT data table of the first risk destination node in sequence;

[0056] If the mth occurrence time calculated in the hybrid YLT data table is less than the nth occurrence time in the YLT data table of the first risk destination node, then the m+1th occurrence time in the hybrid YLT data table is considered;

[0057] If the mth occurrence time calculated in the hybrid YLT data table is greater than the nth occurrence time in the YLT data table of the first risk destination node, the n+1th occurrence time in the YLT data table of the first risk destination node is considered;

[0058] If the mth occurrence time in the calculated hybrid YLT data table is equal to the nth occurrence time in the YLT data table of the first risk destination node, then compare the mth risk type in the calculated hybrid YLT data table with the nth risk type in the YLT data table of the first risk destination node;

[0059] If the mth risk category in the calculated hybrid YLT data table is less than the nth risk category in the YLT data table of the first risk destination node, then the m+1th risk category in the calculated hybrid YLT data table is considered;

[0060] If the mth risk type in the calculated mixed YLT data table is greater than the nth risk type in the YLT data table of the first risk destination node, then the n+1th risk type in the YLT data table of the first risk destination node is considered;

[0061] If the m-th risk category in the calculated mixed YLT data table is equal to the n-th risk category in the YLT data table of the first risk destination node, then compare the m-th event identifier in the calculated mixed YLT data table with the n-th event identifier in the YLT data table of the first risk destination node;

[0062] If the mth event identifier of the calculated hybrid YLT data table is less than the nth event identifier in the YLT data table of the first risk destination node, then the m+1th event identifier of the calculated hybrid YLT data table is considered;

[0063] If the mth event identifier in the calculated hybrid YLT data table is greater than the nth event identifier in the YLT data table of the first risk destination node, then the n+1th event identifier in the YLT data table of the first risk destination node is considered;

[0064] If the m-th event identifier in the calculated hybrid YLT data table is equal to the n-th event identifier in the YLT data table of the first risk destination node, then add the n-th occurrence time, the n-th risk type, and the n-th event identifier in the calculated hybrid YLT data table to the split YLT data table.

[0065] Some more specific implementation manners will detail the technical solutions of the following two methods, namely the loss merging method and the hybrid loss redistribution method:

[0066] Suppose it is necessary to merge the losses of Risk1 and Risk2. The loss result of each Risk consists of four list results, namely the risk type list, the event occurrence time list, the event loss list, and the event EventId list. Suppose the risk type list in the loss result of Risk1 is RID1, the occurrence time list is TR1, the event EventId list is EID1, and the loss list is Loss1. The risk type list in the loss result of Risk2 is RID2, the occurrence time list is TR2, the event EventId list is EID2, and the loss list is Loss2. To calculate the merged result of the two risk loss results, two index lists, namely index1 and index2, are required to record which data item in the merged result each result in the loss result of Risk1 corresponds to, and which data item in the merged result each result in the loss result of Risk2 corresponds to. The merged result also consists of four list results, called TR, RID, Loss, and EID respectively. The specific merging steps are as follows:

[0067] 1. Sort the loss results of Risk1 and Risk2 in ascending order according to the event occurrence time list;

[0068] 2. Traverse the loss results of Risk1 and Risk2. The traversal indexes are count1 and count2 respectively, and the index of the merged result is count. At this time, count, count1, and count2 are all 0;

[0069] 3. Compare the loss results of Risk1 and Risk2. First, compare the event occurrence times in the loss results.

[0070] 1) If TR1[count1]<TR2[count2], then add the loss result of Risk1 to the merged result, that is

[0071] TR[count] = TR1[count1], RID[count] = RIS1[count1], EID[count] = EID1[count1],

[0072] At the same time, record the data position of this piece of data in Risk1 in the merged result, that is

[0073] index1[count1] = count, count1 is incremented by one, and count is incremented by one;

[0074] 2) If TR1[count1] > TR2[count2], then add the loss result of Risk2 to the merged result, that is

[0075] TR[count] = TR2[count2], RID[count] = RIS2[count2], EID[count] = EID2[count2],

[0076] At the same time, record the data position of this piece of data in Risk2 in the merged result, that is index2[count2] = count, count2 is incremented by one, and count is incremented by one;

[0077] 4. If TR1[count1] = TR2[count2], then compare the risk types in the loss results.

[0078] 1) If RID1[count1] < RID2[count2], then add the loss result of Risk1 to the merged result, that is

[0079] TR[count] = TR1[count1], RID[count] = RIS1[count1], EID[count] = EID1[count1],

[0080] At the same time, record the data position of this piece of data in Risk1 in the merged result, that is

[0081] index1[count1] = count, count1 is incremented by one, and count is incremented by one;

[0082] 2) If RID1[count1] > RID2[count2], then add the loss result of Risk2 to the merged result, that is

[0083] TR[count] = TR2[count2], RID[count] = RIS2[count2], EID[count] = EID2[count2],

[0084] At the same time, record the data position of this piece of data in Risk2 in the merged result, that is

[0085] index2[count2] = count, count2 is incremented by one, and count is incremented by one;

[0086] 5. If RID1[count1] = RID2[count2], then compare the EventId of the events in the loss results.

[0087] 1) If EID1[count1] < EID2[count2], then add the loss result of Risk1 to the merged result, that is

[0088] TR[count] = TR1[count1],

[0089] RID[count] = RIS1[count1],

[0090] EID[count] = EID1[count1],

[0091] At the same time, record the data position of this piece of data in Risk1 in the merged result, that is

[0092] index1[count1] = count,

[0093] count1 is incremented by one, and count is incremented by one;

[0094] 2) If EID1[count1] > EID2[count2], then add the loss result of Risk2 to the merged result, that is

[0095] TR[count] = TR2[count2],

[0096] RID[count] = RIS2[count2],

[0097] EID[count] = EID2[count2],

[0098] At the same time, record the data position of this piece of data in Risk2 in the merged result, that is index2[count2] = count, count2 is incremented by one, and count is incremented by one;

[0099] 6. If EID1[count1] = EID2[count2], then add the loss results of both Risk1 and Risk2 to the merged result, that is

[0100] TR[count]=TR1[count1],

[0101] RID[count]=RIS1[count1],

[0102] EID[count]=EID1[count1],

[0103] At the same time, the data position of the data in Risk1 and Risk2 in the merged result is recorded, that is,

[0104] index1[count1]=count,index2[count2]=count,

[0105] count1 plus one, count2 plus one, count plus one;

[0106] 7. Traverse index1, for each index i in index1 and the corresponding value index1[i]:

[0107] TR[index1[i]]=TR1[i],

[0108] EID[index1[i]]=EID1[i],

[0109] Loss[index1[i]] = Loss1[i];

[0110] 8. Traverse index2, for each index i in index2 and the corresponding value index2[i]:

[0111] TR[index2[i]]=TR2[i],

[0112] EID[index2[i]]=EID2[i],

[0113] Loss[index2[i]]=Loss[index2[i]]+Loss2[i];

[0114] Some specific implementation methods propose a redistribution function component SourceSplitter, which is a component equal to Risk and Contract. When building reinsurance business, SourceSplitter can be connected under Contract. In the parameters of SourceSplitter, fill in the nodes involved in the merger, called SourceNode, and the final nodes of the split, called DestinationNode. For example, the above business splits Risk1 and Risk2 from the combined loss results of Risk1, Risk2 and Risk3 after contract calculation. After using SourceSplitter component, the above business structure is as follows Figure 3 shown.

[0115] After the system designs the SourceSplitter component, the system needs to use reasonable algorithm steps to split the combined loss. The above business structure will be used as an example to introduce the redistribution method of mixed losses. The specific method steps are as follows:

[0116] 1. To separate the combined loss of Risk1 and Risk2 from the mixed loss, first separate the losses of Risk1 and Risk2, then combine the loss results of Risk1 and Risk2 according to the above loss combination method to obtain the combined loss result of Risk1 and Risk2. The method for splitting the loss result of Risk1 is the same as that for Risk2, so the method for splitting the loss of Risk1 is described below;

[0117] 2. Assume that in this business structure, the loss result YLT of the calculated mixed loss of the contract has been obtained. YLT includes four list results, namely the risk type list AllocSourceRID, the event occurrence time list AllocSourceTR, the event loss list AllocSourceLoss, and the EventId list AllocSourceEID of the event. The combined loss result of Risk1, Risk2, and Risk3, that is, the combined loss of SourceNode, also contains four list results, namely the risk type list SourceAggRID, the event occurrence time list SourceAggTR, the event loss list SourceAggLoss, and the EventId list SourceAggEID of the event. The loss result of Risk1 also contains four list results, namely the risk type list RID1, the event occurrence time list TR1, the event loss list Loss1, and the EventId list EID1 of the event. Assume that the four result lists included in the split loss result are ResultRID, ResultTR, ResultLoss, and ResultEID;

[0118] 3. Obtain the length Risk1LossLength of the loss result data of Risk1;

[0119] 4. Traverse the loss result YLT of the calculated mixed loss of the contract, set the traversal index as i, and at the same time traverse the loss result YLT of Risk1, set the traversal index as j. At this time, both i and j are 0;

[0120] 5. First, compare AllocSourceTR[i] and TR1[j]. If AllocSourceTR[i] < TR[j], then i++. If AllocSourceTR[i] > TR[j], then j++. If AllocSourceTR[i] = TR[j], then compare AllocSourceRID[i] and RID1[j]. If AllocSourceRID[i] < RID1[j], then i++;

[0121] If AllocSourceRID[i] > RID1[j], then j++;

[0122] If AllocSourceRID[i] = RID1[j], then compare AllocSourceEID[i] and EID1[j]. If AllocSourceEID[i] < EID1[j], then i++;

[0123] If AllocSourceEID[i]>EID1[j], then j++,

[0124] If AllocSourceEID[i] = EID1[j], then you need to add results to ResultRID, ResultTR, ResultLoss, and ResultEID. Add AllocSourceTR[i] to ResultTR, add AllocSourceRID[i] to ResultRID, add AllocSourceEID[i] to ResultEID, and the data added to ResultLoss is calculated using the following formula:

[0125] ResultLoss[index]=AllocSourceLoss[i]×Loss1[j] / SourceAggLoss[i]

[0126] 6. After traversing the loss result YLT of the mixed loss after the contract calculation and the loss result YLT of Risk1, ResultRID, ResultTR, ResultLoss and ResultEID are the post-contract loss result YLT of Risk1 split out of the mixed loss.

[0127] Compared with other existing implementation methods, some implementation methods can more accurately handle mixed loss redistribution services. Because other implementation methods cannot accurately represent this type of service, they are all approximate. Assuming that after using the approximate service construction method, the service structure is as follows Figure 4 As shown, when using this structure, the operator needs to build multiple identical Contract1s to connect with different Risks, which brings inconvenience to the construction of the business structure. At the same time, the calculation results of this construction method may also be inaccurate. For example, Risk1 and Risk2 both have a catastrophic event in the first year. The event in Risk1 occurs earlier, and the event in Risk2 occurs later. In this case, the loss value of the catastrophic events in the two risks will be calculated after entering the contract. However, if the compound effect number in the Contract1 clause is 0, that is, the contract only bears the loss compensation of one catastrophic event in a year, then the event of Risk1 will enter the contract for loss calculation, while the catastrophic event of Risk2 will not enter the contract for loss calculation because it occurs later. Therefore, after the mixed loss redistribution, the event in Risk1 has a corresponding loss, but the event in Risk2 has no corresponding loss, which is obviously different from the result of the approximate structure.

[0128] Some embodiments of the present invention further relate to a computer program product, comprising a computer program / instruction, which implements the steps of the method proposed in the present invention when the computer program / instruction is executed by a processor.

[0129] Some embodiments of the present invention also relate to a computing system for realizing the redistribution of catastrophe insurance losses in reinsurance business, and the computing system implements the method proposed by the present invention when running.

[0130] The implementation and functional operation of the subject matter described in this specification can be implemented in the following: digital electronic circuits, tangibly implemented computer software or firmware, computer hardware, including the structures disclosed in this specification and their structural equivalents, or a combination of more than one of the above. The implementation of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions encoded on one or more tangible non-transitory program carriers, for being executed by a data processing device or controlling the operation of a data processing device. Computer programs (which may also be referred to or described as programs, software, software applications, modules, software modules, scripts or codes) can be written in any form of programming language, including compiled languages ​​or interpreted languages ​​or declarative languages ​​or procedural languages, and computer programs can be expanded in any form, including as independent programs or as modules, components, subroutines or other units suitable for use in a computing environment. Computer programs may, but do not necessarily, correspond to files in a file system. Programs may be stored in a portion of a file that stores other programs or data, for example, one or more scripts stored in the following: in a markup language document; in a single file dedicated to a related program; or in multiple collaborative files, for example, files storing one or more modules, subroutines or code portions. A computer program can be deployed to be executed on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0131] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output.

[0132] Computers suitable for executing computer programs include and may be based, illustratively, on general-purpose microprocessors or special-purpose microprocessors or both of the above processors, or any other kind of central processing unit. Typically, the central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The main elements of a computer are a central processing unit for running or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include or be operably coupled to receive data from or transfer data to a large-capacity storage device for storing data, or both, the large-capacity storage device being, for example, a magnetic disk, a magneto-optical disk, or an optical disk. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices.

[0133] The embodiments of the subject matter described in this specification can be implemented in a computing system, which includes a back-end component such as a data server, or includes an intermediate component such as an application server, or includes a front-end component such as a client computer, and the client computer has a graphical user interface or a web browser, and a user can interact with the implementation of the subject matter described in this specification through a graphical user interface or a web browser, or the computer system includes any combination of one or more such back-end components, intermediate components, or front-end components. The components in the system can be interconnected by digital data communication of any form or medium such as a communication network. Examples of communication networks include local area networks ("LANs") and wide area networks ("WANs"), for example, the Internet.

[0134] A system for implementing catastrophe insurance loss redistribution calculation in reinsurance business may include a client and a server. The client and the server are usually remote from each other and usually interact through a communication network. The relationship between the client and the server is generated by computer programs running on respective computers and having a client-server relationship between each other.

[0135] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any invention or the scope of what can be claimed, but rather as illustrations of features that can concretize specific embodiments of specific inventions. Specific features described in this specification in the context of independent embodiments can also be implemented in combination with a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented independently in multiple embodiments, or in any suitable sub-combination. In addition, although the features can be described above as a combination effect and even initially required, one or more features from the required combination can be removed from the combination in some cases, and the required combination can be turned to a sub-combination or a variation of the sub-combination.

Claims

1. A method for creating a catastrophe insurance loss redistribution module, characterized in that: The following steps are involved: Creating a number of risk source nodes participating in the merger and a number of first contract nodes to be associated with the risk source nodes; At least one split component is created and associated with at least one first contract node, the split component being configured to: Define the risk source nodes involved in the merger and the risk destination nodes after the split; Associating each of the risk destination nodes with a second contract node associated with a risk source node or some risk source nodes; The following steps are also included: According to the underwriting relationship between the risks and contracts involved in the current reinsurance business, the corresponding catastrophe insurance loss redistribution module is introduced; Configure a YLT data table for each risk source node participating in the merger, wherein the YLT data table includes an occurrence time list TR, an event identifier list EID, a risk type list RID, and a loss value list Loss; The YLT data tables of all risk source nodes involved in the merger are merged to obtain a mixed YLT data table; the mixed YLT data table is processed by the first contract node to obtain a calculated mixed YLT data table; the calculated mixed YLT data table is processed by a number of risk destination nodes to obtain a split YLT data table for each risk destination node; The split YLT data table is calculated through the second contract node to obtain the split YLT data table; The acquisition of the mixed YLT data table specifically includes the following steps: Create the first index Index1 and the second index Index2; Sort the YLT data table YLT1 of the first risk source node and the YLT data table YLT2 of the second risk source node involved in the merger in order of occurrence time from small to large, to obtain sorting YLT1 and sorting YLT2; Compare the occurrence time of the sorted YLT1 with the occurrence time of the sorted YLT2 in sequence, and record the YLT data corresponding to the smaller occurrence time value as the current mixed YLT data, traversing the sorted YLT1 and the sorted YLT2; Traverse the Index1, and record the current index value as Index1_i and its order i, and at the same time: record the i-th value in the occurrence time list TR1 of the sorted YLT1 as the Index1_i occurrence time value of the mixed YLT data table, record the i-th value in the event identification list EID1 of the sorted YLT1 as the Index1_i event identification value of the mixed YLT data table, and record the i-th value in the loss value list Loss1 of the sorted YLT1 as the Index1_i loss value in the mixed YLT data table; Traverse the Index2, and record the current index value as Index2_j and its order j. At the same time: record the j-th value in the occurrence time list TR2 of the sorted YLT2 as the Index2_j occurrence time value of the mixed YLT data table, record the j-th value in the event identification list EID2 of the sorted YLT2 as the Index2_j event identification value of the mixed YLT data table, and record the j-th value in the loss value list Loss2 of the sorted YLT2 as the Index2_j loss value in the mixed YLT data table.

2. The method according to claim 1, characterized in that The following steps are also included: If the occurrence time of the sorted YLT1 is equal to the occurrence time of the sorted YLT2, compare the risk type of the sorted YLT1 with the risk type of the sorted YLT2, and record the YLT data corresponding to the smaller value of the risk type as the current mixed YLT data.

3. The method according to claim 2, characterized in that The following steps are also included: If the risk type of the sorted YLT1 is the same as the risk type of the sorted YLT2, compare the event identifier of the sorted YLT1 with the event identifier of the sorted YLT2, and record the YLT data corresponding to the smaller value of the risk identifier as the current mixed YLT data.

4. The method according to claim 3, characterized in that The following steps are also included: If the event identifier of the sequence YLT1 is the same as the event identifier of the sequence YLT2, the YLT data corresponding to the sequence YLT1 and / or the sequence YLT2 is recorded as the current mixed YLT data.

5. The method according to claim 4, characterized in that The split YLT data table is specifically obtained by the following steps: Starting from the calculated mixed YLT data table, the YLT data table of the first risk destination node and the first data in the mixed YLT data table, the calculated mixed YLT data table, the YLT data table of the first risk destination node and the mixed YLT data table are traversed according to the following formula to obtain the loss value of the split YLT data table: ResultLoss[m]=AllocSource Loss[m]×Loss1[n] / SourceAggLoss[m] Among them, AllocSourceLoss[m] is the mth loss value calculated in the hybrid YLT data table, Loss1[n] is the nth loss value in the YLT data table of the first risk destination node, SourceAggLoss[m] is the mth loss value in the hybrid YLT data table, and ResultLoss[m] is the mth loss value in the YLT data table of the first risk destination node.

6. The method according to claim 5, characterized in that The following steps are also included: Starting from the first data of the calculated hybrid YLT data table and the YLT data table of the first risk destination node, traverse the calculated hybrid YLT data table and the YLT data table of the first risk destination node, and compare the mth occurrence time of the calculated hybrid YLT data table and the nth occurrence time of the YLT data table of the first risk destination node in sequence; If the mth occurrence time in the calculated hybrid YLT data table is less than the nth occurrence time in the YLT data table of the first risk destination node, then the m+1th occurrence time in the calculated hybrid YLT data table is considered; If the mth occurrence time in the calculated hybrid YLT data table is greater than the nth occurrence time in the YLT data table of the first risk destination node, then the n+1th occurrence time in the YLT data table of the first risk destination node is considered; If the mth occurrence time in the calculated hybrid YLT data table is equal to the nth occurrence time in the YLT data table of the first risk destination node, then compare the mth risk type in the calculated hybrid YLT data table with the nth risk type in the YLT data table of the first risk destination node; If the mth risk category in the calculated hybrid YLT data table is less than the nth risk category in the YLT data table of the first risk destination node, then the m+1th risk category in the calculated hybrid YLT data table is considered; If the mth risk type in the calculated mixed YLT data table is greater than the nth risk type in the YLT data table of the first risk destination node, then the n+1th risk type in the YLT data table of the first risk destination node is considered; If the m-th risk category in the calculated mixed YLT data table is equal to the n-th risk category in the YLT data table of the first risk destination node, then compare the m-th event identifier in the calculated mixed YLT data table with the n-th event identifier in the YLT data table of the first risk destination node; If the mth event identifier in the calculated hybrid YLT data table is less than the nth event identifier in the YLT data table of the first risk destination node, then the m+1th event identifier in the calculated hybrid YLT data table is considered; If the mth event identifier in the calculated mixed YLT data table is greater than the nth event identifier in the YLT data table of the first risk destination node, then the n+1th event identifier in the YLT data table of the first risk destination node is considered; If the mth event identifier of the calculated hybrid YLT data table is equal to the nth event identifier in the YLT data table of the first risk destination node, the nth occurrence time, nth risk type and nth event identifier of the calculated hybrid YLT data table are added to the split YLT data table.

7. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method of claims 1-6 are implemented.

8. A computing system for realizing the redistribution of catastrophe insurance losses in reinsurance business, characterized in that: The computing system implements the method of claims 1-6 when running.

Images