An insurance template-based batch intelligent insurance system and method

Abstract

The application discloses an insurance template batch intelligent insurance system and method, and belongs to the technical field of insurance data processing. The method comprises the following steps: checking the received batch template insurance policies respectively; based on the template insurance policies that pass the check, constructing a multi-dimensional field mapping data set covering passenger identity information, travel data and insurance product elements; performing set analysis and mapping analysis filling on the constructed multi-dimensional field mapping data set to obtain batch standardized insurance information; based on the mapping relationship between the supplier and the insurance parameter, performing supplier identification and conversion on the batch standardized insurance information, and sending the batch converted "some" insurance policies to the corresponding suppliers respectively. The application realizes automatic identification and extraction of insurance parameter information from the template insurance policy; through the combination of "set analysis and mapping analysis filling" and "supplier identification and conversion", intelligent pre-filling and batch insurance of the insurance form are completed.

Description

Technical Field

[0001] This application belongs to the field of insurance data processing technology, and specifically relates to an insurance template-based batch intelligent insurance application system and method. Background Technology

[0002] The continuous development of the global air travel industry has driven the ongoing upgrading of the civil aviation service system, and air travel has become one of the main modes of long-distance travel for the public. Against this backdrop, passengers' demand for travel risk protection is becoming increasingly prominent, and the market penetration and user acceptance of travel insurance products are continuously improving. More and more consumers are incorporating insurance into their travel planning decisions to enhance their ability to cope with risks during their journey. However, the existing travel insurance application process suffers from significant efficiency bottlenecks in the information collection stage. Traditional application systems often use a linear form model, requiring users to fill in multiple fields such as name, identification information, flight number, travel date, and insurance period. This serial input method is not only cumbersome and time-consuming but also prone to inaccurate information due to human error, making it difficult to meet the high standards of timeliness and convenience required by current civil aviation services. Therefore, it is necessary to optimize the existing application process through technological means and build a more intelligent and efficient insurance application solution to improve user experience and business processing capabilities.

[0003] In the aviation tourism and travel management sector, group travel demand is experiencing rapid growth, particularly in scenarios such as corporate group travel, school study tours, large-scale conference and exhibition groups, and themed charter flights. The number of passengers involved in a single insurance policy often reaches dozens to hundreds. Traditional insurance distribution systems are typically designed based on a one-person, one-time data entry model. Agents must repeatedly enter basic data such as each passenger's name, ID number, date of birth, and flight information when processing group policies, and must also verify the insurance terms and coverage details one by one. This manual, one-by-one processing method is not only inefficient and physically demanding, but also highly susceptible to errors due to repetitive data entry and visual fatigue, affecting policy quality and customer experience. Faced with the continuous expansion of group insurance business, the market's demand for insurance systems with batch and automated processing capabilities is increasingly urgent. Insurance distribution systems urgently need to introduce technical solutions that support template import, intelligent verification, and batch processing to enable rapid uploading and identification of passenger information through standardized Excel or CSV files, coupled with real-time underwriting and feedback mechanisms. This will improve operational efficiency while ensuring data accuracy and business compliance. Summary of the Invention

[0004] To address the aforementioned issues, this application provides a templated, batch-based intelligent insurance application system and method.

[0005] The first objective of this application is to provide a template-based, batch, intelligent insurance application method, including: Verify each batch of received templated insurance policies; Based on the validated templated insurance policy, a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements is constructed. The constructed multi-dimensional field mapping dataset is parsed and populated with set parsing and mapping parsing to obtain batches of standardized insurance information; Based on the mapping relationship between suppliers and insurance parameters, standardized insurance information in batches is identified and transformed, and the transformed insurance policies are sent to the corresponding suppliers.

[0006] In a specific embodiment of this application, the step of verifying the received batch of templated insurance policies includes: Each batch of received templated insurance policies undergoes version verification. If the version verification fails, generate a policy version error message; Based on the successful validation of the templated policy format, the field content of the templated policy is validated.

[0007] In a specific embodiment of this application, the field content validation of the templated insurance policy includes: The integrity of the field structure, the existence of the fields, and the compliance of the format of the templated insurance policy are all verified simultaneously. If the verification fails, an error message is generated; Based on the successful verification, a determination is made as to whether the insurance application has been successfully submitted. Based on the result of whether the insurance application was successful or not, a business rejection message is generated; If the successful insurance application is deemed a successful outcome, then the templated policy passes the verification.

[0008] In a specific embodiment of this application, the determination of whether the insurance has been successfully purchased is made by comparing the departure time of the travel plan with the current time; The result of successfully obtaining insurance is: the time difference between the planned departure time and the current time is greater than or equal to the insurance validity threshold. The result of determining whether the insurance application is successful is: the time between the planned departure time and the current time is less than the insurance application time limit, or the planned departure time is earlier than the current time.

[0009] In a specific embodiment of this application, the construction of a multi-dimensional field mapping dataset covering passenger identity information, travel data, and insurance product elements based on a verified templated insurance policy includes: Based on the verified templated insurance policy, extract and construct a collection of passenger information. Based on the verified templated insurance policy, extract and construct a collection of travel information; By merging the passenger information set with the travel information set, a multi-dimensional field mapping dataset covering passenger identity information, travel data, and insurance product elements is obtained.

[0010] In a specific embodiment of this application, the step of extracting and constructing a passenger information set based on the verified templated insurance policy includes: In the templated insurance policy, the passenger group identifier is located and the number of passengers is determined. An independent subset of insurance data is constructed for each passenger. The passenger information collection contains the subset of insurance data of all passengers in the entire group. The construction of the aforementioned subset of insurance data includes: In the templated insurance policy, the passenger name field is extracted, and the passenger serial number is used as an index to establish a mapping relationship between the name and the insurance parameters; In the templated insurance policy, extract the passenger's document type, identify the document number, and construct a document combination mapping relationship identifier; In the templated insurance policy, extract the passenger's date of birth and establish a date of birth mapping identifier; Extract the passenger's gender from the templated insurance policy and establish a gender mapping relationship identifier; Extract passenger contact numbers from the templated insurance policy and establish a contact number mapping relationship identifier; In the templated insurance policy, extract the relationship field information between the policyholder and the insured, and establish the policyholder-insured mapping relationship identifier; In the templated insurance policy, extract the passenger ticket number field information and establish a passenger ticket number mapping relationship identifier.

[0011] In a specific embodiment of this application, if there is policyholder information corresponding to the current passenger in the templated insurance policy, then the construction of the policyholder data subset also includes the construction of the policyholder information data subset; If there is no policyholder information corresponding to the current passenger in the templated policy, then the current passenger will be used as the policyholder.

[0012] In a specific embodiment of this application, the step of extracting and constructing a travel information set based on the verified templated insurance policy includes: In the templated insurance policy, the travel time period is specified; Extract the vehicle number field from the travel time period and establish a mapping relationship with the insurance parameters; Extract the departure date data of the means of transportation from the location travel time period, map it to the insurance field, and convert the date data format to the destination date data format; Extract the planned departure time of transportation from the location travel time period and establish a departure time field mapping; From the location of the travel time period, the estimated arrival time of the means of transportation is analyzed, and an arrival time field mapping is established; Extract the departure city code from the location travel time period and establish a mapping relationship to the departure city; Extract destination codes from the location travel time period and establish a mapping relationship between arrival cities.

[0013] In a specific embodiment of this application, the step of performing set parsing and mapping parsing to populate the constructed multi-dimensional field mapping dataset to obtain batches of standardized insurance information includes: Perform set parsing on the constructed multi-dimensional field mapping dataset; Based on the matching relationship between the insurance parameters and the identifiers of the passenger information set and the travel information set, the fields obtained from the set parsing are filled to obtain a batch of standardized insurance information.

[0014] The second objective of this application is to provide a template-based batch intelligent insurance application system, including a template verification central module, an information recognition central module, an information filling central module, and an application submission central module; The template verification central module is used to verify the received batch of templated insurance policies respectively; The information identification central module is used to construct a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements based on the verified templated insurance policy; The information filling central module is used to perform set parsing and mapping parsing filling on the constructed multi-dimensional field mapping dataset to obtain batches of standardized insurance information; The insurance application submission central module is used to identify and convert batches of standardized insurance information based on the mapping relationship between suppliers and insurance parameters, and send the batch-converted "available" insurance policies to the corresponding suppliers.

[0015] In a specific embodiment of this application, the template verification hub module is further configured to send the verified templated policy information to the information recognition hub module. The information identification hub module is used to receive the templated policy information that has passed the verification, and also to send the constructed multi-dimensional field mapping dataset to the information filling hub module; The information filling central module is used to receive the constructed multi-dimensional field mapping dataset and also to send batches of standardized insurance information to the insurance submission central module. The insurance application submission central module is also used to receive batches of standardized insurance application information.

[0016] In a specific embodiment of this application, the template verification hub module is further configured to generate an error message or a service rejection message and send the error message or service rejection message to the user login terminal; The information filling central module includes a set parsing unit and a mapping parsing filling unit; The set parsing unit is used to perform set parsing on the constructed multi-dimensional field mapping dataset; The mapping parsing and filling unit is used to fill the structured fields obtained from the set parsing into the corresponding fields of the insurance application form based on the identification matching relationship between the insurance application parameters and the passenger information set and the travel information set, respectively, so as to obtain a batch of standardized insurance application information.

[0017] In a specific embodiment of this application, the insurance application submission central module includes a supply identification unit, an intelligent conversion unit, and an information sending unit; The supply identification unit is used to identify the supply of standardized insurance information in batches based on the mapping relationship between suppliers and insurance parameters. The intelligent conversion unit is used to convert the field parameters in the standardized insurance information into parameter information that conforms to the field format requirements of each supplier, based on the supplier's policy business requirements, so as to obtain a batch of "available" policies. The information sending unit is used to distribute the batch of "existing" insurance policies one by one and in sequence to the corresponding suppliers.

[0018] In a specific embodiment of this application, the insurance application submission central module is also used to receive the supplier's underwriting approval instruction; The insurance application submission central module is also used to generate and save an electronic insurance policy based on the underwriting approval instruction; The insurance application submission central module is also used to receive a response message containing an error code returned by the supplier if the underwriting fails. The insurance application submission central module is also used to generate modification suggestions based on the response report containing error codes, and send the modification suggestions to the user login terminal.

[0019] Compared with the prior art, this application has the following advantages: This application constructs a multi-dimensional field mapping dataset covering passenger identity information, travel data, and insurance product elements to automatically identify and extract insurance parameter information from templated insurance policies; and through the combination of "set parsing and mapping parsing filling" and "supply identification and transformation", it completes intelligent pre-filling of insurance forms and batch insurance applications.

[0020] The combination of "set parsing and mapping parsing population" and "supply identification and transformation" serves two main purposes: Order data containing multiple passengers is split into independent and complete insurance sub-requests based on the passenger dimension (achieved through "set parsing and mapping parsing population"). These independent and complete insurance sub-requests are then subjected to supply identification, and these sub-requests are distributed sequentially to the supplier's insurance interface (achieved through "supply identification and transformation"), realizing a refined "one order, one passenger" insurance model. This model ensures that each insurance request strictly meets the supplier's order quantity threshold requirements, fundamentally avoiding the risk of insurance failure due to exceeding the order insurance quantity limit.

[0021] Furthermore, in the step of "verifying the received batch of templated insurance policies", the data is formatted and logically verified at the field level to ensure its completeness and standardization; in the step of "supply identification and conversion", business rules and underwriting conditions are matched at the policy level to ensure that each policy meets the underwriting requirements of the insurer, thus realizing an integrated dual verification mechanism.

[0022] This application effectively overcomes the technical bottlenecks of low efficiency and high error rate inherent in traditional manual data entry methods, reshaping the insurance application experience, especially in group insurance scenarios. It frees insurance agents from tedious and repetitive transactional work, allowing them to enjoy intelligent "what you see is what you get" services. Furthermore, the system supports flexible configuration of mapping rules and parsing strategies based on the product characteristics of different insurance providers, possessing excellent business adaptability and scalability. This helps drive the upgrade of the civil aviation ancillary business system towards automation and precision, providing effective support for technological innovation and service model transformation in the entire aviation and travel insurance sector.

[0023] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

[0024] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 A flowchart of a templated batch intelligent insurance application method according to certain embodiments of this application is shown; Figure 2A framework diagram of a templated batch intelligent insurance application system according to certain embodiments of this application is shown. In the diagram: 10. Template verification central module; 20. Information recognition central module; 30. Information filling central module; 40. Submission central module. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0027] The terms used in this application are explained below: IATA The International Air Transport Association (IATA) is a large international organization comprised of airlines from around the world. Its predecessor was the International Association of Air Transport, founded in The Hague in 1919 and dissolved during World War II. Headquartered in Montreal, Canada, with its executive office in Geneva, IATA is more like an international coordinating organization of carriers (airlines) than the International Civil Aviation Organization (ICAO), which regulates aviation safety and navigation rules. It manages issues arising in civil aviation such as ticket prices and the transport of dangerous goods. Its main role is to coordinate and communicate intergovernmental policies and resolve practical operational problems through air transport companies.

[0028] GDS A Global Distribution System (GDS) is a large-scale computer information service system applied to civil aviation transportation and the entire tourism industry. Through GDS, travel sales organizations worldwide can obtain a wealth of travel-related information from airlines, hotels, car rental companies, and insurance companies in a timely manner, thereby providing customers with fast, convenient, and reliable services. China TravelSky is one such GDS service provider.

[0029] Travel insurance aggregation system Insurance Distribution Platform (IDP) is a platform that integrates, processes, and handles insurance product data provided by upstream and downstream insurance users. It serves as the interface, data, and services of the travel insurance platform software. Target customers are airline agents or application software, providing services for selling travel insurance products. Key functions include insurance inquiry, booking, cancellation, invoice issuance, and sales statistics.

[0030] software In software operations and maintenance (O&M) terminology, it refers to the sum of products maintained by the project team, or the general term for the overall product system, such as: travel insurance aggregation system.

[0031] Module In software operation and maintenance systems, this term refers to the components or subsystems of software, such as the insurance platform module and insurance interface module under the travel insurance aggregation system.

[0032] The agent is a distributor of airline tickets and insurance.

[0033] like Figure 1 As shown, a method for standardized batch intelligent insurance application according to certain embodiments of this application includes: S1. Verify each batch of templated insurance policies received; S2. Based on the verified templated insurance policy, construct a multi-dimensional field mapping dataset covering passenger identity information, travel data, and insurance product elements; S3. Perform set parsing and mapping parsing to populate the constructed multi-dimensional field mapping dataset to obtain batches of standardized insurance information; S4. Based on the mapping relationship between suppliers and insurance parameters, identify and convert batches of standardized insurance information, and send the converted insurance policies to the corresponding suppliers.

[0034] In some embodiments of this application, the templated insurance policy is designed for travelers' insurance needs and includes personal information, travel information, and insurance validity information. The acquisition of personal information, travel information, and insurance validity information is with the customer's consent and is kept confidential. The personal information includes policyholder information and insured information. The travel information includes transportation schedule information, departure point, and destination. The insurance validity information includes the insurance effective date and the insurance expiration date, with the time in the insurance effective date and the insurance expiration date accurate to the hour and minute. For example, if a passenger travels by air, their templated insurance policy is shown in Table 1.

[0035] Table 1

[0036] In some embodiments of this application, step S1 includes: S1-1. For each batch of received templated insurance policies, a version verification of the templated insurance policy is performed. The version verification adopts a two-factor authentication mechanism: detecting the extension of the templated insurance policy. For example, the valid extensions are xls and xlsx. Based on the preset attachment naming rules in the version configuration library, the name of the current templated insurance policy is further verified. The preset attachment naming rules are set by the travel management requirements themselves, and this application does not impose specific limitations on them. S1-2. Based on the failure of version verification, generate a policy version error message and send it to the customer login terminal to inform the user of the error in the templated policy, so that the user can make corrections according to the corresponding error message. The policy version error message includes file extension error and naming error. S1-3. Based on the successful validation of the templated policy format, validate the field content of the templated policy.

[0037] In some embodiments of this application, steps S1-3 include: S1-3-1. Simultaneously verify the integrity of the field structure, the existence of fields, and the compliance of the format of the templated insurance policy; The field structure integrity check is performed by checking the continuity of the sequence number of the travel time period (if the means of transportation is airplane, then it is flight segment; if it is train, then it is travel interval (or ticket segment or journey segment)) to ensure that the travel data is not broken or misaligned. The field existence verification is as follows: For the products purchased by users, based on the preset mandatory field policy, key fields such as name, flight number, date and time, and identification information are checked for non-emptiness. For example, itinerary products require the ticket number, departure and arrival city codes (the specific fields that need to be verified for existence depend on the supplier of the specific insurance product). Therefore, when purchasing this type of product, it is necessary to verify whether the aforementioned relevant field information in the attachment is not empty. The format compliance verification includes: verifying whether the date field conforms to the YYYYMMDD standard, whether the time field meets the HHMM format, and whether the document number length meets the corresponding document type specification requirements; S1-3-2. Based on the failure of the verification, an error message is generated. The content of the error message is generated according to the failed verification. For example, if the verification of the integrity of the field structure fails, an error in the integrity of the travel time period is generated so that the user can make corresponding modifications to the verification (field structure integrity, field existence and / or format compliance) according to the error message. S1-3-3. Based on the successful verification, determine whether the insurance application has been successfully submitted. S1-3-4. Based on the result of whether the insurance application was successful or not, generate a business rejection message; S1-3-5. If the successful insurance application is deemed a successful result, the templated policy passes the verification.

[0038] In some embodiments of this application, the determination of whether the insurance has been successfully purchased is made by comparing the departure time of the travel plan with the current time; The successful insurance application is determined as follows: the time difference between the planned departure time and the current time is greater than or equal to the insurance application validity threshold. The insurance application validity threshold is set according to the insurance application time rules of the corresponding insurance product, and this application does not specifically limit it. The result of determining whether the insurance application is successful is: the time between the planned departure time and the current time is less than the insurance application time limit, or the planned departure time is earlier than the current time.

[0039] In some embodiments of this application, step S2 includes: S2-1. Based on the verified templated insurance policy, extract and construct a collection of passenger information; S2-2. Based on the verified templated insurance policy, extract and construct a collection of travel information; S2-3. Merge the passenger information set with the travel information set to obtain a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements.

[0040] In some embodiments of this application, step S2-1 includes: In the templated insurance policy, the passenger group identifier is located and the number of passengers is determined. An independent subset of insurance data is constructed for each passenger. The passenger information collection contains the subset of insurance data of all passengers in the entire group. The construction of the aforementioned subset of insurance data includes: S2-1-A-1. In the templated insurance policy, extract the passenger name field, use the passenger serial number as an index, and establish a mapping relationship between the name and the insurance parameters; the insurance parameters are the insurance product number, and the insurance product number and insurance product elements such as the insurance effective date and insurance expiration date are structured data, with each insurance product number corresponding to a set of insurance product elements such as the insurance effective date and insurance expiration date; For example, the passenger name field code is: CN + passenger serial number. This field supports multi-byte character set encoding to ensure the complete storage of names of ethnic minorities and foreign passengers. S2-1-A-2. In the templated insurance policy, extract the passenger's document type, identify the document number, and construct a document combination mapping relationship identifier; For example, the passenger document type field code is: IDTYPE + passenger serial number; For example, the passenger identification number field code is: ID + passenger serial number; S2-1-A-3. Extract the passenger's date of birth from the templated policy and establish a date of birth mapping relationship identifier; For example, the passenger's date of birth field code is: BD + passenger serial number; S2-1-A-4. Extract the passenger's gender from the templated insurance policy and establish a gender mapping relationship identifier; For example, the passenger gender field code is: GE + passenger serial number; S2-1-A-5. Extract passenger contact numbers from the templated insurance policy and establish contact number mapping relationship identifiers; For example, the field code for passenger contact number is: TEL + passenger serial number. S2-1-A-6. In the templated insurance policy, extract the relationship field information between the policyholder and the insured, and establish the policyholder-insured mapping relationship identifier; For example, the field code for the relationship between the policyholder and the insured is: RE + passenger serial number. S2-1-A-7. Extract the passenger ticket number field information from the templated insurance policy and establish a passenger ticket number mapping relationship identifier; For example, the field code for passenger ticket number is: TK + passenger serial number.

[0041] Based on the structured processing from steps S2-1-A-1 to S2-1-A-7, a complete set of passenger information containing fields such as CN / IDTYPE / ID / BD / GE / TEL / RE / TK is generated, achieving a high-fidelity conversion from data in the templated policy to the standard insurance dataset. Each passenger subset is identified by a unique serial number, supporting batch insurance operations and subsequent data traceability.

[0042] In some embodiments of this application, if there is policyholder information corresponding to the current passenger in the templated insurance policy, the construction of the policyholder data subset also includes the construction of the policyholder information data subset; this situation applies to cases where the insured is a minor or an employee of an enterprise and the corresponding policyholder information needs to be recorded.

[0043] In some embodiments of this application, the steps for constructing the subset of policyholder information data are the same as steps S2-1-A-1 to S2-1-A-6, except that the extracted passenger is replaced with the policyholder. The corresponding mapping relationship identifiers include: the mapping relationship between name and insurance parameters, the mapping relationship identifier of document combination, the mapping relationship identifier of date of birth, the mapping relationship identifier of gender, the mapping relationship identifier of contact number, and the mapping relationship identifier between policyholder and insured. For example, the policyholder's name field code is: BCN + passenger serial number. This field supports multi-byte character set encoding to ensure the complete storage of names of ethnic minorities and foreign passengers. For example, the policyholder document type field code is: BIDTYPE + passenger serial number; For example, the policyholder identification number field code is: BID + passenger serial number; For example, the policyholder's date of birth field code is: BBD + passenger serial number; For example, the policyholder's gender field code is: BGE + passenger serial number; For example, the field code for the policyholder's contact number is: BTEL + passenger serial number; For example, the field code for the relationship between the policyholder and the insured is: BRE + Passenger Number.

[0044] Similarly, based on the above steps for constructing the policyholder information data subset, the policyholder information data subset with fields such as BCN / BIDTYPE / BID / BBD / BGE / BTEL / BRE is also stored in the passenger information collection.

[0045] In some embodiments of this application, if there is no policyholder information corresponding to the current passenger in the templated policy, the current passenger will be used as the policyholder.

[0046] In some embodiments of this application, step S2-2 includes: S2-2-1. Locate the travel time period in the templated insurance policy; S2-2-2 Extract the travel vehicle number field from the location travel time period and establish a mapping relationship with the insurance parameters; For example, the travel vehicle number field code is: FN; If the mode of transportation is an airplane, the mode of transportation number is the flight number, which uses IATA standard coding to ensure the uniformity of global flight identification; S2-2-3. Extract the departure date data of the means of transportation from the location travel time period, map it to the insurance field, and convert the date data format to the destination date data format; For example, the departure date field code is: DA; Date data is automatically converted to the YYYYMMDD standard format to comply with insurance industry data specifications; S2-2-4. Extract the planned departure time of the means of transportation from the location travel time period and establish a departure time field mapping; For example, the departure time slot code is: OT; Time data is accurate to the minute and stored in HHMM format; S2-2-5. From the location travel time period, analyze the estimated arrival time of the means of transportation and establish an arrival time field mapping; For example, the arrival time field code is: DT; Time data is synchronously converted to HHMM format to ensure the integrity of the timeline; S2-2-6. Extract the departure city code from the location travel time period and establish a mapping relationship to the departure city; For example, the departure city field code is: OC; If the mode of transportation is an airplane, the departure code is the three-letter code of the departure airport, and the three-letter code of the departure airport follows the IACO international standard and supports precise location of airports worldwide; S2-2-7. Extract destination codes from the location travel time period and establish a mapping relationship between arrival cities; For example, the arrival city field code is: DC; The encoding rules for the arrival city code are consistent with those for the departure city code, so as to form a closed-loop trip data chain.

[0047] In steps S2-3, since the passenger information or policyholder information in the passenger information dataset and the occurrence information in the travel dataset are all associated with the insurance parameters, the passenger information dataset and the travel dataset are merged to obtain a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements.

[0048] In some embodiments of this application, step S3 includes: S3-1. Perform set parsing on the constructed multi-dimensional field mapping dataset; S3-2. Based on the preset matching relationship between the insurance parameters and the identifiers of the passenger information set and the travel information set (the code mapping relationship set when constructing the set in step S-2), the structured fields obtained from the set parsing are filled into the corresponding fields of the insurance application form (as shown in Table 2 for example), resulting in batches of standardized insurance information. Each insurance product corresponds to one insurance application form.

[0049] Table 2

[0050] In Table 2, the third column provides explanations based on the specific means of transportation. Table 2 provides explanations for information corresponding to airplanes. If the means of transportation is railway, the explanations can be adjusted accordingly, such as changing the flight number to the train number. The ellipses in Table 2 represent insurance fields, mapping codes, and explanations containing policyholder information. This application does not impose specific limitations on insurance fields and mapping codes, as long as the uniqueness of the insurance fields, mapping codes, and the explanations is guaranteed.

[0051] In some embodiments of this application, step S4 includes: S4-1. Based on the mapping relationship between suppliers and insurance parameters, identify suppliers for batches of standardized insurance information; S4-2. Based on the supplier's policy business requirements, the field parameters in the standardized insurance information are transformed into parameter information that conforms to the field format requirements of each supplier, so as to obtain a batch of "available" policies.

[0052] In some embodiments of this application, step S4 further includes: The batch of "existing" insurance policies are distributed one by one and sequentially to the corresponding suppliers. This step innovatively adopts the "separate insurance" strategy to replace the traditional single order insurance model, so as to effectively avoid the maximum limit set by the supplier for the number of passengers in the order. For example, the distribution to the corresponding supplier is achieved through API (Application Programming Interface) communication protocols.

[0053] Specifically, steps S3-S4 serve the following purposes: Upon receiving the insurance request submitted by the user, the request parameters are first preprocessed and parsed. Order data containing multiple passengers is split into independent and complete insurance sub-requests based on the passenger dimension (achieved through step S3). These independent and complete insurance sub-requests are then identified by the supplier and distributed sequentially to the supplier's insurance interface (achieved through step S4), realizing a refined "one order, one passenger" insurance model. This model ensures that each insurance request strictly meets the supplier's order quantity threshold requirements, fundamentally avoiding the risk of insurance failure due to exceeding the order insurance quantity limit.

[0054] like Figure 2 As shown, an insurance template-based batch intelligent insurance application system according to certain embodiments of this application includes a template verification central module 10, an information recognition central module 20, an information filling central module 30, and an insurance application submission central module 40. The template verification central module 10 is used to verify the received batch of templated insurance policies respectively; The information recognition central module 20 is used to construct a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements based on the verified templated insurance policy; The information filling central module 30 is used to perform set parsing and mapping parsing filling on the constructed multi-dimensional field mapping dataset to obtain batches of standardized insurance information; The insurance application submission central module 40 is used to identify and convert batches of standardized insurance information based on the mapping relationship between suppliers and insurance parameters, and send the batch-converted "available" insurance policies to the corresponding suppliers.

[0055] In some embodiments of this application, the template verification hub module 10 is further configured to send the verified templated policy information to the information recognition hub module 20; The information recognition central module 20 is used to receive the templated insurance policy information that has passed the verification, and is also used to send the constructed multi-dimensional field mapping dataset to the information filling central module 30; The information filling central module 30 is used to receive the constructed multi-dimensional field mapping dataset and also to send batches of standardized insurance information to the insurance submission central module 40. The insurance application submission central module 40 is also used to receive batches of standardized insurance application information.

[0056] In some embodiments of this application, the template verification central module 10 includes an attachment verification unit and a text verification unit; The attachment verification unit is used to perform version verification on the received batch of templated insurance policies; it is also used to generate a policy version error message and send it to the customer login terminal if the version verification fails. The text verification unit is used to verify the field content of the templated insurance policy based on the passing of the templated insurance policy format verification.

[0057] In some embodiments of this application, the template verification hub module 10 is further configured to generate error messages or service rejection messages and send the error messages or service rejection messages to the user login terminal; In some embodiments of this application, the information filling central module 30 includes a set parsing unit and a mapping parsing filling unit; The set parsing unit is used to perform set parsing on the constructed multi-dimensional field mapping dataset; The mapping parsing and filling unit is used to fill the structured fields obtained from the set parsing into the corresponding fields of the insurance application form based on the preset matching relationship between the insurance fields and the mapping relationship identifier, so as to obtain a batch of standardized insurance information.

[0058] In some embodiments of this application, the insurance application submission central module includes a supply identification unit, an intelligent conversion unit, and an information sending unit; The supply identification unit is used to identify the supply of standardized insurance information in batches based on the mapping relationship between suppliers and insurance parameters. The intelligent conversion unit is used to convert the field parameters in the standardized insurance information into parameter information that conforms to the field format requirements of each supplier, based on the supplier's policy business requirements, so as to obtain a batch of "available" policies. The information sending unit is used to distribute the batch of "existing" insurance policies one by one and in sequence to the corresponding suppliers. The interface between the information sending unit and the supplier is connected via API protocol and rules.

[0059] In some embodiments of this application, the insurance application submission central module 40 is also used to receive an underwriting approval instruction from the supplier; The insurance application submission central module 40 is also used to generate and save an electronic insurance policy based on the underwriting approval instruction; The insurance application submission central module 40 is also used to receive a response message containing an error code returned by the supplier if the underwriting fails; The insurance application submission central module 40 is also used to generate modification suggestions based on the response report containing error codes, and send the modification suggestions to the user login terminal.

[0060] The system described in the above embodiment is installed in an Information Distribution Platform (IDP) for travel insurance aggregation. IDP is a travel insurance distribution system launched by China TravelSky (GDS) to serve domestic agents, providing them with insurance distribution services. The system integrates resources from multiple insurance providers and achieves insurance sales through automated system integration. It is also used to implement the aforementioned method for template-based batch intelligent insurance underwriting.

[0061] In this embodiment, the templated policy is shown in Table 1, and the specific operations of steps S1-S3 are shown in the example. In step S3, the constructed multi-dimensional field mapping dataset is parsed in the information population central module. Based on the matching relationship between the insurance parameters and the identifiers of the passenger information set and the travel information set, the parsed structured field data is automatically populated into the corresponding fields of the insurance application form, constructing a complete data model covering passenger basic information and flight itinerary information. This model consists of two main sets: The passenger basic information unit includes legal identity elements such as name, document type, document number, date of birth, and gender. The name field uses Unicode encoding and supports multiple language character sets; the document type covers various legal documents such as resident ID cards and passports; the document number is verified using a validation algorithm to ensure format compliance; and the date of birth is automatically converted to YYYYMMDD format according to national standards.

[0062] The flight itinerary information unit integrates key itinerary parameters such as ticket number, flight number, departure time, arrival time, departure airport code, and destination airport code. The flight number adopts the IATA standard coding format, the departure / arrival time is accurate to the minute, and the airport code follows the IACO standard, forming a standard data chain covering the entire flight lifecycle. In step S4, based on the supplier's policy business requirements obtained through deep parsing in the interface call between the information sending unit and the supplier, and the mapping relationship between the supplier and the insurance parameters, the field parameters in the standardized insurance information are transformed into parameter information that conforms to the field format requirements of each supplier. Examples are shown below: For the user document type field, the system has a built-in comprehensive and dynamically expandable mapping rule system that not only covers mainstream document types such as ID cards, passports, and military officer certificates, but also reserves flexible extension interfaces to handle emerging document types. In the adaptation phase, the system first accurately identifies the original code identifier of the document type in local data (e.g., "01" corresponds to an ID card), and then seamlessly converts it to the standardized code required by the supplier (e.g., "ID_CARD") according to the mapping rule library. For complex document types with multi-level classifications (e.g., passports are subdivided into official and private categories), a multi-level mapping logic is adopted to ensure that the conversion results are both accurate and strictly compliant.

[0063] For date and time related parameters, intelligent parsing and formatting technology is employed to automatically identify the date and time format in local data (such as "YYYY-MM-DD HH:mm:ss") and dynamically adjust it to the target format (such as "MM / DD / YYYY" or timestamp format) according to supplier requirements. Simultaneously, time zone conversion is supported to ensure data consistency in cross-time zone business scenarios.

[0064] Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for modularized, batch intelligent insurance application, characterized in that, include: Verify each batch of received templated insurance policies; Based on the validated templated insurance policy, a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements is constructed. The constructed multi-dimensional field mapping dataset is parsed and populated with set parsing and mapping parsing to obtain batches of standardized insurance information; Based on the mapping relationship between suppliers and insurance parameters, standardized insurance information in batches is identified and transformed, and the batch-transformed "available" insurance policies are sent to the corresponding suppliers.

2. The method for modularized batch intelligent insurance application according to claim 1, characterized in that, The step of verifying the received batch of templated insurance policies includes: Each batch of received templated insurance policies undergoes version verification. If the version verification fails, generate a policy version error message; Based on the successful validation of the templated policy format, the field content of the templated policy is validated.

3. The method for modularized batch intelligent insurance application according to claim 2, characterized in that, The field content validation of the templated insurance policy includes: The integrity of the field structure, the existence of the fields, and the compliance of the format of the templated insurance policy are all verified simultaneously. If the verification fails, an error message is generated; Based on the successful verification, a determination is made as to whether the insurance application has been successfully submitted. Based on the result of whether the insurance application was successful or not, a business rejection message is generated; If the successful insurance application is deemed a successful outcome, then the templated policy passes the verification.

4. The method for modularized batch intelligent insurance application according to claim 3, characterized in that, The determination of whether the insurance application was successful is made by comparing the planned departure time of the trip with the current time. The result of successfully obtaining insurance is: the time difference between the planned departure time and the current time is greater than or equal to the insurance validity threshold. The result of determining whether the insurance application is successful is: the time between the planned departure time and the current time is less than the insurance application time limit, or the planned departure time is earlier than the current time.

5. The method for modularized batch intelligent insurance application according to claim 1, characterized in that, Based on the verified templated insurance policy, a multi-dimensional field mapping dataset covering passenger identity information, travel data, and insurance product elements is constructed, including: Based on the verified templated insurance policy, extract and construct a collection of passenger information. Based on the verified templated insurance policy, extract and construct a collection of travel information; By merging the passenger information set with the travel information set, a multi-dimensional field mapping dataset covering passenger identity information, travel data, and insurance product elements is obtained.

6. The method for modularized batch intelligent insurance application according to claim 5, characterized in that, The step of extracting and constructing a passenger information set based on the verified templated insurance policy includes: In the templated insurance policy, the passenger group identifier is located and the number of passengers is determined. An independent subset of insurance data is constructed for each passenger. The passenger information collection contains the subset of insurance data of all passengers in the entire group. The construction of the aforementioned subset of insurance data includes: In the templated insurance policy, the passenger name field is extracted, and the passenger serial number is used as an index to establish a mapping relationship between the name and the insurance parameters; In the templated insurance policy, extract the passenger's document type, identify the document number, and construct a document combination mapping relationship identifier; In the templated insurance policy, extract the passenger's date of birth and establish a date of birth mapping identifier; Extract the passenger's gender from the templated insurance policy and establish a gender mapping relationship identifier; Extract passenger contact numbers from the templated insurance policy and establish a contact number mapping relationship identifier; In the templated insurance policy, extract the relationship field information between the policyholder and the insured, and establish the policyholder-insured mapping relationship identifier; In the templated insurance policy, extract the passenger ticket number field information and establish a passenger ticket number mapping relationship identifier.

7. The method for modularized batch intelligent insurance application according to claim 6, characterized in that, If there is policyholder information corresponding to the current passenger in the templated policy, then the construction of the policyholder data subset also includes the construction of the policyholder information data subset; If there is no policyholder information corresponding to the current passenger in the templated policy, then the current passenger will be used as the policyholder.

8. The method for modularized batch intelligent insurance application according to claim 5, characterized in that, The step of extracting and constructing a travel information set based on the verified templated insurance policy includes: In the templated insurance policy, the travel time period is specified; Extract the vehicle number field from the travel time period and establish a mapping relationship with the insurance parameters; Extract the departure date data of the means of transportation from the location travel time period, map it to the insurance field, and convert the date data format to the destination date data format; Extract the planned departure time of transportation from the location travel time period and establish a departure time field mapping; From the location of the travel time period, the estimated arrival time of the means of transportation is analyzed, and an arrival time field mapping is established; Extract the departure city code from the location travel time period and establish a mapping relationship to the departure city; Extract destination codes from the location travel time period and establish a mapping relationship between arrival cities.

9. A method for modularized batch intelligent insurance application according to any one of claims 1-8, characterized in that, The process of performing set parsing and mapping parsing to populate the constructed multi-dimensional field mapping dataset yields a batch of standardized insurance information, including: Perform set parsing on the constructed multi-dimensional field mapping dataset; Based on the matching relationship between the insurance parameters and the identifiers of the passenger information set and the travel information set, the fields obtained from the set parsing are filled to obtain a batch of standardized insurance information.

10. A template-based, batch intelligent insurance application system, characterized in that, It includes a template verification central module, an information recognition central module, an information filling central module, and an insurance application submission central module; The template verification central module is used to verify the received batch of templated insurance policies respectively; The information identification central module is used to construct a multi-dimensional field mapping dataset covering passenger identity information, travel data and insurance product elements based on the verified templated insurance policy; The information filling central module is used to perform set parsing and mapping parsing filling on the constructed multi-dimensional field mapping dataset to obtain batches of standardized insurance information; The insurance application submission central module is used to identify and convert batches of standardized insurance information based on the mapping relationship between suppliers and insurance parameters, and send the batch-converted "available" insurance policies to the corresponding suppliers.

11. The insurance template-based batch intelligent insurance application system according to claim 10, characterized in that, The template verification central module is also used to send the verified templated policy information to the information recognition central module. The information identification hub module is used to receive the templated policy information that has passed the verification, and also to send the constructed multi-dimensional field mapping dataset to the information filling hub module; The information filling central module is used to receive the constructed multi-dimensional field mapping dataset and also to send batches of standardized insurance information to the insurance submission central module. The insurance application submission central module is also used to receive batches of standardized insurance application information.

12. The insurance template-based batch intelligent insurance application system according to claim 10, characterized in that, The template verification central module is also used to generate error messages or service rejection messages and send them to the user login terminal. The information filling central module includes a set parsing unit and a mapping parsing filling unit; The set parsing unit is used to perform set parsing on the constructed multi-dimensional field mapping dataset; The mapping parsing and filling unit is used to fill the structured fields obtained from the set parsing into the corresponding fields of the insurance application form based on the identification matching relationship between the insurance application parameters and the passenger information set and the travel information set, respectively, so as to obtain a batch of standardized insurance application information.

13. The insurance template-based batch intelligent insurance application system according to claim 10, characterized in that, The insurance application submission central module includes a supply identification unit, an intelligent conversion unit, and an information sending unit; The supply identification unit is used to identify the supply of standardized insurance information in batches based on the mapping relationship between suppliers and insurance parameters. The intelligent conversion unit is used to convert the field parameters in the standardized insurance information into parameter information that conforms to the field format requirements of each supplier, based on the supplier's policy business requirements, so as to obtain a batch of "available" policies. The information sending unit is used to distribute the batch of "existing" insurance policies one by one and in sequence to the corresponding suppliers.

14. The insurance template-based batch intelligent insurance application system according to claim 10, characterized in that, The insurance application submission central module is also used to receive the supplier's underwriting approval instruction; The insurance application submission central module is also used to generate and save an electronic insurance policy based on the underwriting approval instruction; The insurance application submission central module is also used to receive a response message containing an error code returned by the supplier if the underwriting fails; The insurance application submission central module is also used to generate modification suggestions based on the response report containing error codes, and send the modification suggestions to the user login terminal.

Images