Air travel insurance automatic application method and system based on PNR original text intelligent analysis

Abstract

This application discloses an automated travel insurance application method and device based on intelligent parsing of PNR original text, belonging to the field of computer technology. The method includes: receiving PNR original text data submitted by a user, determining the document type and version, and verifying the PNR original text data based on the determined document type and version; parsing the verified PNR original text data according to the meaning of the PNR original text fields, mapping the parsed PNR original text data to a custom mapping code, generating a standardized insurance application dataset; matching the standardized insurance application dataset to the insurance application fields based on the correspondence between the custom mapping code and the insurance application fields, filling the application page, and displaying it in an editable visual interface. This method uses a custom mapping code to map passenger identity and flight information to the standardized fields required by the insurance application form, achieving structured automatic filling of insurance information.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and specifically relates to an automated insurance application method and system for travel insurance based on intelligent parsing of PNR original text. Background Technology

[0002] With the booming development of the global aviation and tourism industry and the continuous upgrading of civil aviation services, air travel has increasingly become the preferred mode of long-distance transportation for the public. Against this backdrop, passengers' awareness of risk protection has significantly increased, and the penetration rate of travel insurance products has been rising year by year. More and more consumers are proactively purchasing travel insurance products when booking tickets to add professional protection for their trips. However, in the current travel insurance application process, there is a significant efficiency bottleneck in the insured information collection stage—due to the need to fully fill in multi-dimensional information such as name, ID number, flight number, and insurance period, the traditional linear information collection model severely restricts the efficiency of the insurance service, urgently requiring technological innovation to optimize the service experience. Summary of the Invention

[0003] To address the aforementioned issues, this application provides an automated travel insurance application method and device based on intelligent parsing of PNR original text, which can achieve automated pre-filling of application forms.

[0004] This application provides an automated travel insurance underwriting method based on intelligent parsing of PNR original text, including: Receive PNR original data submitted by users, determine the document type and version, and verify the PNR original data based on the determined document type and version; Based on the meaning of the fields in the original PNR data, the validated original PNR data is parsed and mapped to a custom mapping code to generate a standardized insurance dataset. Based on the correspondence between the custom mapping code and the insurance field, the standardized insurance dataset is matched to the insurance field, populated into the insurance page, and displayed in an editable form in the visual interface; The confirmed insurance information is assembled into a request message containing structured insurance data and sent to the insurance provider's system.

[0005] Furthermore, based on the meaning of the PNR original data fields, the PNR original data that passed the validation is parsed, including: Based on the meaning of the fields in the PNR original data, the passenger group identifier is located and the number of passengers is determined from the verified PNR original data. A passenger number is assigned to each passenger, and the passenger information of each passenger is extracted to obtain a collection of passenger information, which includes: name, document type, document number, date of birth, gender and ticket number. Based on the meaning of the fields in the original PNR data, the first segment number is located from the verified original PNR data. Using this first segment number as the data anchor, a complete set of flight information is extracted. The flight information includes: flight number, departure date, departure time, arrival time, departure airport code, and arrival airport code.

[0006] Furthermore, the custom mapping codes include: CN + passenger number, ID + passenger number, PP + passenger number, BD + passenger number, GE + passenger number, TK + passenger number, FN, DA + OT, DA + DT, OC, and DC. Among them, CN represents the passenger name, ID represents the ID card, PP represents the passport, BD represents the date of birth, GE represents the gender, TK represents the ticket number, FN represents the flight number, DA + OT represents the departure time, DA + DT represents the arrival time, OC represents the departure city three-letter code, and DC represents the arrival city three-letter code.

[0007] Furthermore, based on the correspondence between custom mapping codes and insurance fields, the standardized insurance dataset is matched to the insurance fields, populated into the insurance application page, and displayed in an editable form on the visual interface, including: Based on the correspondence between the custom mapping code and the insurance fields, the standardized insurance dataset is automatically populated into the insurance fields using a two-way verification mechanism. The data is then populated onto the insurance application page and displayed in an editable form on the visual interface. The two-way verification mechanism includes: semantic consistency verification of the target fields in the standardized insurance dataset and the visual insurance application interface, and format verification of the populated results.

[0008] Furthermore, document type and version determination is performed, and the PNR original data is verified based on the determined document type and version, including: Detect the document type identifier in the PNR original data to determine the document type version; The identified document type identifier is verified against the version configuration library, which contains document type, field length and verification rules; The system performs structural integrity checks and flight status checks in sequence. The structural integrity checks include checks on the continuity of flight segment numbers, the existence of fields, and the compliance of formats. The flight status checks include checking whether the difference between the current system time and the scheduled flight departure time is lower than the preset insurance validity threshold.

[0009] Furthermore, based on the correspondence between the custom mapping code and the insurance fields, the standardized insurance dataset is automatically populated and matched to the insurance fields using a two-way verification mechanism, populated onto the insurance application page, and displayed in an editable form on the visual interface, including: Based on the correspondence between the custom mapping code and the insurance fields, the standardized insurance dataset is automatically filled into the insurance fields using dynamic form generation technology based on a two-way verification mechanism. The data is then filled into the insurance page and displayed in an editable form on the visual interface.

[0010] Furthermore, the confirmed insurance information is assembled into a request message containing structured insurance data and sent to the insurance provider's system, including: Obtain the underwriting results from the insurance provider's system; If the underwriting is approved, an electronic policy will be generated and the data will be archived. If the underwriting fails, a response message containing an error code will be returned, and actionable correction suggestions will be displayed on the front-end page.

[0011] This application also provides an electronic device, including: Memory, which stores execution instructions; and The processor executes the execution instructions stored in memory, causing the processor to perform any of the methods described above.

[0012] This application also provides a readable storage medium storing executable instructions, which are executed by a processor to implement the above-described method.

[0013] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0014] Compared with the prior art, this application has the following advantages: 1. Significantly Improved Insurance Application Efficiency: Breaking away from the traditional linear model of manual, item-by-item data entry, this technology parses key fields such as passenger identity and flight information from the original PNR data structure. Through custom mapping code, it maps passenger identity and flight information to the standardized fields required in the insurance application form, achieving structured and automatic filling of insurance information. This technology eliminates repetitive data entry steps, significantly improving the efficiency of agents' insurance application operations and providing a revolutionary efficiency upgrade solution for travel insurance services.

[0015] 2. Ensuring the accuracy of insurance information: Breaking away from the traditional manual data entry model, this technology accurately identifies key information such as passenger identity and flight status in the original PNR (Passenger Notice), achieving synchronization between insurance information and ticket booking data. Using the original PNR as the sole data source, this technology ensures the accuracy of information entry, effectively eliminating the risk of information deviation caused by manual operation, and building a reliable data quality assurance system for travel insurance services.

[0016] 3. Diversified application of information: Deeply explore the value of PNR original data and build an intelligent connection hub for the core civil aviation system and the ancillary service ecosystem.

[0017] 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

[0018] 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.

[0019] Figure 1 The diagram illustrates the module interface and functions of the PNR identification insurance technology according to an embodiment of this application. Figure 2 A flowchart of an automated travel insurance underwriting method based on PNR original text intelligent parsing, according to an embodiment of this application, is shown. Detailed Implementation

[0020] In the globalized civil aviation operation system, the completion of a passenger's ticket booking triggers a multi-source data integration mechanism, automatically generating a structured PNR (Passenger Name Record) data record conforming to IATA standards. This record serves as a digital mirror of the passenger's itinerary, comprehensively storing the legal requirements for identity verification (including document type, number, and issuance information), multi-channel contact information, and itinerary parameters accurate to the flight segment level. Notably, all core elements required for travel insurance product application forms, including the insured's identification, flight status information, and scope of insurance liability, are fully integrated into the PNR data structure. By constructing an intelligent parsing engine to perform structured parsing of the PNR, automated pre-filling of insurance information is achieved. This not only eliminates repetitive data entry but also establishes a data consistency verification mechanism, effectively mitigating the risks of errors and omissions caused by manual operations, injecting intelligent transformation momentum into the civil aviation service chain.

[0021] To overcome the efficiency bottlenecks of traditional insurance application processes, this invention proposes an automated insurance application solution based on intelligent parsing of PNR original text. This technology deeply mines the PNR original text data structure, constructs multi-dimensional field mapping relationships, accurately locates and extracts key elements such as passenger identity and flight information, and achieves automated pre-filling of the insurance application form. This solution significantly shortens the insurance application process time, greatly improves the accuracy of information matching, and establishes a dual verification mechanism to ensure data integrity. It not only reshapes the travel insurance service process but also provides ticket and insurance distributors and other agents with a "what you see is what you get" intelligent and convenient operating experience, driving the evolution of the civil aviation service support chain towards automation and precision.

[0022] 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.

[0023] Figure 1 This diagram illustrates the module interface and functions of a PNR (Proof-of-Receipt) identification insurance application technology according to an embodiment of this disclosure, including: a text verification module, a text recognition module, an information filling module, and an insurance application submission module, wherein: The original text verification module is used to determine the authenticity of the original PNR format submitted by the user, and further verify the compliance and validity of the data source; The original text recognition module is used to receive the verified PNR original text data, and after recognizing and parsing the relevant field information according to the preset PNR field definition to form an order dataset, it sends it to the information filling module. The order dataset includes the parsed passenger basic information and itinerary information. The information population module is used to populate the relevant fields of the insurance application information using the order dataset to obtain the fully populated insurance application information; the fully populated insurance application information is then sent to the insurance application submission module. The insurance application submission module is used to transmit relevant information to the upstream to complete the insurance application process.

[0024] Specifically, the original text verification module includes the following functional modules: Structural integrity check: Verifies whether the overall structure of the PNR message is complete; Field Existence Validation: Verify that the key fields required for insurance application exist; Format compliance verification: Verify whether the format of each field conforms to industry standards; Specifically, the original text recognition module includes the following functional modules: Passenger Information Aggregation: Identifying and aggregating passenger information from the PNR; Flight Information Aggregator: Identifying and aggregating flight information from PNR; Specifically, the information population module includes the following functional modules: Passenger Basic Information Unit: Organize passenger information into standardized basic information units required for insurance application; Flight Itinerary Information Unit: Organize flight information into standardized itinerary information units required for insurance application; Specifically, the insurance application submission module includes the following functional modules: Integrity check: Verify whether the insurance application information to be submitted is complete; Supplier verification: Connect with insured suppliers to complete the compliance verification on the supplier side.

[0025] The following is combined Figure 2 The overall process of the automated travel insurance underwriting method based on PNR original text intelligent parsing of the present invention is described, specifically including the following steps: Step 201: The original document verification module receives the PNR original document data submitted by the user, performs document type and version identification, and verifies the PNR original document data based on the identified document type.

[0026] The above checks include: structural integrity check, field existence check, format compliance check, and flight status check.

[0027] Because the PNR original information entered by users is different, there may be situations such as missing information or expired flights during the entry process. Therefore, this step 1 integrates the standard PNR format and identifies the document type by recognizing the PNR original information entered by the user, so as to further determine the structural integrity of the PNR original data and the validity of the flight by the departure time.

[0028] After a user submits the PNR (Passenger No. 1) original data, the system initiates a document type version recognition process to determine the document type version of the input PNR original data. This stage employs a two-factor authentication mechanism: first, it detects the document type identifier (FOID / DOCS) in the PNR original data, and then performs a secondary verification by comparing it with the background version configuration database. Currently, the system supports two major document type versions: ID card (FOID identifier) ​​and passport (DOCS identifier). The version configuration database contains metadata information such as document type, field length, and verification rules. Cross-validation is performed using document number encoding rules and passenger type codes to ensure the accuracy of version recognition.

[0029] After confirming the document type and version, the original PNR data is subjected to structural integrity verification, specifically the following three-level verification system: (1) Continuity check of flight segment numbers: Check the continuity of flight segment numbers to ensure that the itinerary data is not broken or misaligned.

[0030] (2) Field Existence Validation: Perform non-empty validation on key fields such as name, PNR location code, flight number, city three-letter code, date and time field, document information, ticket number, etc.

[0031] (3) Format compliance verification: Verify whether the date field conforms to the YYYYMMDD standard, whether the time field meets the HHMM format, and whether the document number length conforms to the corresponding document type specification.

[0032] If the structural integrity check fails, an error message "PNR format error, parsing terminated" will be generated, and a detailed error log will be returned to guide the user in correcting the data.

[0033] If the integrity verification passes, the time service module is invoked to compare the scheduled flight departure time with the current system time. If the flight has already taken off or is about to take off (the time difference is less than the insurance validity threshold), a "Flight status abnormal, unable to apply for insurance" business rejection message is generated; if the time verification passes, the subsequent processing steps are executed: data mapping and insurance parameter assembly operations are performed.

[0034] In step 201, the original text verification module is used to determine the authenticity of the PNR original text format entered by the user and to verify the compliance and validity of the data source.

[0035] Step 202: Parse the validated PNR original text according to the meaning of the PNR original text data fields, map the parsed PNR original text data to the custom mapping code, and generate a standardized insurance dataset.

[0036] The parsed PNR original data includes passenger information and flight information.

[0037] Based on the verified PNR (Passenger Notice) original text, passenger basic information and flight information are extracted through field recognition. The parsed passenger basic information and flight information are then mapped to custom mapping codes. These custom mapping codes are then mapped to the standardized fields required in the insurance application form. Passenger basic information mainly involves passenger name, document type, document number, and ticket number; flight information mainly involves flight number, departure time, arrival time, departure airport code, and arrival airport code. A standardized dataset is then formed.

[0038] The parsing and mapping of passenger information involves: parsing the original PNR data structure, locating the passenger group identifier and determining the number of passengers, assigning a unique passenger serial number to each passenger, and using the passenger serial number as an index to map the name, ID information, and ticket number to a custom mapping code; mapping the passenger information for each passenger to obtain a subset of the insurance data for each passenger, ultimately forming a complete set of insurance data containing information for all passengers in the group. The specific process is as follows: 1) Passenger name mapping Extract passenger names and use the passenger serial number as an index to map the name to a custom mapping code (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.

[0039] 2) Document information mapping A differentiated parsing strategy is implemented based on the document information format (FOID / DOCS) in the original PNR data: FOID Layout Processing: When a FOID layout is detected, the document type is automatically identified as a People's Republic of China Resident Identity Card. Perform the following operations: Extract the ID number and map it to a custom mapping code ID + passenger serial number; The birth date data is extracted from the 7th to 14th digits of the ID card and mapped to a custom mapping code BD + passenger number; applying the national standard GB11643-1999, the gender is determined based on the parity of the 17th digit and mapped to a custom mapping code GE + passenger number.

[0040] DOCS Layout Processing: When a DOCS layout is encountered, the document type is automatically identified as a passport. Perform the following operations: Extract passport number data and map it to a custom mapping code PP+passenger serial number; Extract the date of birth data from the second digit of the passport information and map it to a custom mapping code BD + passenger serial number; Parse the last character of the birth date to identify the gender, and map it to a custom mapping code GE + passenger number.

[0041] 3) Ticket number information mapping The location ticket number information field (PNR statement identifier: TKNE) extracts the electronic ticket number and maps it to a custom mapping code TK + passenger serial number. This field uses an airline industry standard ticket number format verification algorithm to ensure data validity.

[0042] Through the above structured processing, a complete set of passenger information containing fields such as CN / ID / BD / GE / PP / TK is generated, achieving a high-fidelity conversion from PNR raw data to the insurance standard dataset. Each passenger subset is identified by a unique serial number, supporting batch insurance operations and subsequent data traceability.

[0043] The parsing and mapping of flight information is as follows: Based on the meaning of the fields in the original PNR data, the first segment number is located from the verified original PNR data, and the complete set of flight information is extracted using the first segment number as the data anchor point. It should be noted that the first flight segment number mentioned above is used as a data anchor point to link the complete information of this flight itinerary.

[0044] Specifically, flight information parsing and mapping consists of the following six core steps: 1) Flight Number Extraction: Extract the flight number field from the first segment number located and map it to a custom mapping code FN. The flight number uses IATA standard encoding to ensure the uniformity of global flight identification.

[0045] 2) Departure Date Parsing: Extract flight departure date data from the first flight segment and map it to a custom mapping code DA. Date data is automatically converted to the YYYYMMDD standard format, conforming to insurance industry data specifications.

[0046] 3) Departure Time Parsing: Parse the scheduled departure time of the flight from the first flight segment and map it to a custom mapping code OT. Time data is accurate to the minute and stored in HHMM format.

[0047] 4) Arrival Time Parsing: Parse the estimated arrival time of the flight from the last flight segment and map it to a custom mapping code DT. Time data is synchronously converted to HHMM format to ensure the integrity of the timeline.

[0048] 5) Departure Airport Code Extraction: Extract the three-letter code of the departure airport from the first flight segment and map it to a custom mapping code (OC). The code conforms to the IACO international standard and supports precise location of airports worldwide.

[0049] 6) Arrival Airport Code Extraction: Extract the three-letter code of the arrival airport from the last flight segment and map it to a custom mapping code (DC). The code system is consistent with the departure city, forming a closed-loop itinerary data chain.

[0050] Through the above six core steps mapping mechanism, the structured transformation from PNR original data to insurance standard dataset is completed, generating a flight information collection containing six major elements: FN / DA / OT / DT / OC / DC, providing complete data support for automated insurance application.

[0051] In summary, the above process is as follows: the verified PNR original text is structured and parsed to locate the passenger group identifier and the first segment number. Based on the passenger group identifier, the total number of passengers is determined and a unique passenger number is assigned to each passenger. The first segment number is used as the core anchor point for extracting flight information. Extract passenger information and execute custom mapping code mapping: Identify the format identifier of passenger documents to determine document type, adopt corresponding field extraction and derivation rules for different document types, automatically obtain or derive name, document number, date of birth, and gender information, simultaneously extract the corresponding electronic ticket number and perform format verification, map it to the custom mapping code, and generate a standardized passenger information collection by associating the above information with the passenger serial number; Extract flight information and perform custom mapping code mapping: Associate complete itinerary information with the core anchor point, extract flight number, departure date, departure time, arrival time, departure airport code, and arrival airport code, map them to custom mapping code, perform format standardization conversion and industry standard verification according to insurance industry data specifications, and generate a standardized flight information collection; Finally, the passenger information set and the flight information set are combined to form a structured dataset that can be directly imported into the insurance system.

[0052] Step 203: Based on the predefined correspondence between custom mapping codes and insurance fields, match passenger information sets and flight information sets to insurance fields, populate them into the insurance application page, and display them in an editable form on the visual interface.

[0053] After constructing passenger information sets and flight information sets, the passenger information sets and flight information sets are matched to the insurance fields based on the predefined correspondence between custom mapping codes and insurance fields. Dynamic form generation technology is used to automatically fill in the fields on the insurance application page, directly mapping core information such as passenger name, ID number, and flight number to the insurance application interface.

[0054] Construct a one-to-one correspondence between the custom mapping code and the insurance fields (i.e., field mapping relationship), and integrate the extracted field information based on this mapping relationship. Meanwhile, a visual interface is used to display information in plain text, ensuring that key information is presented in a clear and readable manner. This allows users to perform secondary verification, forming a closed-loop operation flow of "data parsing - automatic filling - manual confirmation," which ensures both efficiency and information accuracy.

[0055] Specifically, based on the field mapping rules established by the intelligent recognition engine as shown in Table (1), the parsed structured data can be automatically filled into the corresponding insurance fields of the insurance application form, thus constructing a complete data model covering passenger basic information and flight itinerary information. This data model is divided into two core units: (1) Passenger basic information unit includes legal identity elements such as name, document type, document number, date of birth, and gender.

[0056] (2) The flight itinerary information unit integrates key itinerary parameters such as flight number, departure time, arrival time, departure airport three-letter code and destination airport three-letter code.

[0057] In addition, a dual verification mechanism is used to ensure data integrity: first, field-level format verification is performed, then business logic verification is implemented (such as the takeoff time being earlier than the landing time), and finally a standardized dataset that meets the requirements of the insurance business is generated.

[0058] Table 1 summarizes the relationship between insurance fields and custom mapping codes as follows:

[0059] Step 204: Assemble the confirmed insurance information into a request message containing structured insurance data and send it to the insurance provider system.

[0060] Based on standardized insurance application information generated by an intelligent parsing engine, the system synchronizes structured data to the insurance provider's system via an encrypted transmission channel. This transmission process adheres to industry security standards, ensuring the integrity and confidentiality of the data during transmission. After receiving the standardized insurance application information, the insurance provider can quickly process underwriting and automatically generate policy documents based on preset rules.

[0061] Based on the insurance parameter specifications of the upstream business system, a strict information completeness verification procedure is executed. When a required field (such as the insured's name, ID number, flight number, etc.) is detected to be missing, an interactive prompt message "Required field not filled, please complete and submit" is immediately generated, blocking the process and guiding the user to complete the information. If all required fields pass verification, the system will automatically assemble a request message containing structured insurance data and transmit it upstream through a secure channel.

[0062] On the supplier side, insurance applications undergo multiple layers of verification: First, the business rules engine performs a compliance check, verifying whether the insurance parameters comply with preset rules such as product terms, sales area, and coverage limits; if the verification passes, the policy generation process is triggered, returning a successful insurance confirmation message containing the policy number; if the parameter verification fails (such as applying for insurance beyond the age limit, or the flight date exceeding the insurance validity period), a response message containing error codes is generated, detailing the violation fields and reasons, forming a complete risk control closed loop of "front-end verification - transmission encryption - back-end verification".

[0063] Based on the same inventive concept as the above disclosure, this disclosure also provides an electronic device. The electronic device of this disclosure includes at least one processor and at least one memory electrically connected to the processor. The memory is electrically connected to the processor, wherein the memory stores instructions executable by the at least one processor. These instructions are executed by the at least one processor to enable the at least one processor to perform the method described above. It should be noted that the electrical connection between the above-mentioned units does not necessarily mean the connection between lines. The indirect connection method can be applied to the embodiments of this disclosure as long as it achieves the purpose of this disclosure.

[0064] Based on the same inventive concept, this disclosure also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the above-described method.

[0065] Based on the same inventive concept, this disclosure also provides a computer program product that implements the above-described method when executed by a processor.

[0066] 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 automated travel insurance underwriting based on intelligent parsing of PNR original text, characterized in that, include: Receive PNR original data submitted by users, determine the document type and version, and verify the PNR original data based on the determined document type and version; Based on the meaning of the fields in the original PNR data, the validated original PNR data is parsed and mapped to a custom mapping code to generate a standardized insurance dataset. Based on the correspondence between the custom mapping code and the insurance field, the standardized insurance dataset is matched to the insurance field, populated into the insurance page, and displayed in an editable form in the visual interface; The confirmed insurance information is assembled into a request message containing structured insurance data and sent to the insurance provider's system.

2. The method according to claim 1, characterized in that, Based on the meaning of the PNR raw data fields, the PNR raw data that passed the validation is parsed, including: Based on the meaning of the fields in the PNR original data, the passenger group identifier is located and the number of passengers is determined from the verified PNR original data. A passenger number is assigned to each passenger, and the passenger information of each passenger is extracted to obtain a collection of passenger information, which includes: name, document type, document number, date of birth, gender and ticket number. Based on the meaning of the fields in the original PNR data, the first segment number is located from the verified original PNR data. Using this first segment number as the data anchor, a complete set of flight information is extracted. The flight information includes: flight number, departure date, departure time, arrival time, departure airport code, and arrival airport code.

3. The method according to claim 1, characterized in that, Custom mapping codes include: CN + passenger number, ID + passenger number, PP + passenger number, BD + passenger number, GE + passenger number, TK + passenger number, FN, DA + OT, DA + DT, OC, and DC. Among them, CN represents the passenger name, ID represents the ID card, PP represents the passport, BD represents the date of birth, GE represents the gender, TK represents the ticket number, FN represents the flight number, DA + OT represents the departure time, DA + DT represents the arrival time, OC represents the departure city three-letter code, and DC represents the arrival city three-letter code.

4. The method according to claim 1, characterized in that, Based on the correspondence between custom mapping codes and insurance fields, the standardized insurance dataset is matched to the insurance fields, populated into the insurance application page, and displayed in an editable visual interface, including: Based on the correspondence between the custom mapping code and the insurance fields, the standardized insurance dataset is automatically populated into the insurance fields using a two-way verification mechanism. The data is then populated onto the insurance application page and displayed in an editable form on the visual interface. The two-way verification mechanism includes: semantic consistency verification of the target fields in the standardized insurance dataset and the visual insurance application interface, and format verification of the populated results.

5. The method according to any one of claims 1-4, characterized in that, Perform document type and version identification, and verify the PNR original data based on the identified document type and version, including: Detect the document type identifier in the PNR original data to determine the document type version; The identified document type identifier is verified against the version configuration library, which contains document type, field length and verification rules; The system performs structural integrity checks and flight status checks in sequence. The structural integrity checks include checks on the continuity of flight segment numbers, the existence of fields, and the compliance of formats. The flight status checks include checking whether the difference between the current system time and the scheduled flight departure time is lower than the preset insurance validity threshold.

6. The method according to claim 4, characterized in that, Based on the correspondence between custom mapping codes and insurance fields, the standardized insurance dataset is automatically populated and matched to the insurance fields using a two-way validation mechanism. This population is then displayed on the insurance application page in an editable visual interface, including: Based on the correspondence between the custom mapping code and the insurance fields, the standardized insurance dataset is automatically filled into the insurance fields using dynamic form generation technology based on a two-way verification mechanism. The data is then filled into the insurance page and displayed in an editable form on the visual interface.

7. The method according to claim 1, characterized in that, The confirmed insurance information is assembled into a request message containing structured insurance data and sent to the insurance provider's system, including: Obtain the underwriting results from the insurance provider's system; If the underwriting is approved, an electronic policy will be generated and the data will be archived. If the underwriting fails, a response message containing an error code will be returned, and actionable correction suggestions will be displayed on the front-end page.

8. An electronic device, characterized in that, include: The memory stores execution instructions; as well as A processor that executes execution instructions stored in the memory, causing the processor to perform the method of any one of claims 1 to 7.

9. A readable storage medium, characterized in that, The readable storage medium stores execution instructions, which, when executed by a processor, are used to implement the method of any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 7.

Images