Electronic itinerary processing method, system, storage medium and device

Abstract

The application discloses an electronic itinerary processing method, system, storage medium and equipment, and belongs to the technical field of air transportation. The method comprises the following steps: receiving an electronic itinerary request from a front-end system; in response to the electronic itinerary request, acquiring electronic ticket data and insurance invoice information, constructing electronic itinerary data according to the electronic ticket data and the insurance invoice information; uploading the electronic itinerary data to a tax system for verification, and acquiring a verification result returned by the tax system; and generating a format file according to the electronic itinerary data that passes the verification. The electronic itinerary processing method simplifies user operation and improves convenience.

Description

Technical Field

[0001] This application belongs to the field of air transport technology, and in particular relates to electronic itinerary processing methods, systems, storage media and devices. Background Technology

[0002] In the digitalization of air transport services, electronic itineraries have undergone digital upgrades, becoming a core electronic voucher for passenger travel and corporate reimbursement. Their functionality is crucial for industry service upgrades and user experience enhancement. However, existing electronic itinerary technologies and application models still have many shortcomings, making it difficult to adapt to industry development needs and actual user demands.

[0003] Firstly, information integration is incomplete, resulting in missing information for users. Currently, the travel information system's ticketing system and insurance system are mostly independent architectures, and their data is not effectively interconnected. The QR code on the electronic itinerary ticket contains core itinerary identification information but is not linked to core insurance data such as the insurance premium invoice number and the insured amount. This prevents passengers from accessing insurance invoice information by scanning the QR code.

[0004] Secondly, inconsistencies in expense information hindered the reimbursement process. While the electronic itinerary included an insurance premium item, this expense information was not simultaneously included in the corresponding electronic invoice on the tax verification platform. This mismatch in amounts between the aforementioned documents conflicted with the compliance requirements for financial reimbursement, leading the finance department to refuse to accept related reimbursement applications, causing significant inconvenience to travelers and corporate users.

[0005] Third, there is data isolation across systems and a lack of a coordinated management mechanism. Because the data barriers between the travel information system's ticketing system and the insurance system have not been broken down, companies cannot use electronic itineraries to achieve joint verification and full-process traceability of passenger travel information and insurance information. This is not only detrimental to companies' precise optimization of service quality, but also makes it difficult to meet industry regulators' requirements for data traceability. Summary of the Invention

[0006] To address the aforementioned issues, this application provides an electronic itinerary processing method that simplifies user operations and improves convenience.

[0007] This application is achieved through the following technical solution: Receive electronic itinerary requests from the front-end system; In response to the electronic itinerary request, obtain electronic ticket data and insurance invoice information, and construct electronic itinerary data based on the electronic ticket data and insurance invoice information; Upload the electronic itinerary data to the tax system for verification, and obtain the verification result returned by the tax system; Generate a layout file based on the successfully verified electronic itinerary data.

[0008] Optional, The electronic itinerary request includes: Requests for issuing electronic itinerary receipts, requesting red-ink electronic itinerary receipts, requesting to query electronic itinerary receipts, and requesting to download electronic itinerary receipts.

[0009] Optional, The step of responding to the electronic itinerary request, obtaining electronic ticket data and insurance invoice information, and constructing electronic itinerary data based on the electronic ticket data and insurance invoice information includes: The system calls the TravelSky mainframe ticketing system to obtain electronic ticket data, which includes ticket sales data, insurance premium data, and ticket status. The system retrieves insurance invoice information based on premium data. Electronic itinerary data is generated based on the electronic ticket data and insurance invoice information.

[0010] Optional, The process of calling the insurance system to obtain insurance invoice information based on insurance premium data includes: Based on the electronic ticket data, the insurance system is accessed to query and retrieve insurance invoice information: If no insurance invoice information is found, the insurance system will be invoked to issue an insurance invoice and obtain the insurance invoice information.

[0011] Optional, Call the TravelSky mainframe ticketing system to mark the electronic tickets with issued electronic itineraries as invoices; and / or, Call the TravelSky mainframe ticketing system to remove the invoice printing mark from electronic tickets with red-inked electronic itineraries.

[0012] Optional, If the electronic itinerary request received from the front-end system is a request to issue an electronic itinerary: In response to the request to issue an electronic itinerary, electronic ticket data is obtained from the TravelSky mainframe ticketing system; Based on the electronic ticket data, the insurance system is accessed to query and retrieve insurance invoice information: If the insurance system returns insurance invoice information, then the electronic ticket data and insurance invoice information are integrated to generate electronic itinerary data; If no insurance invoice information is found, the insurance system will be called to issue an insurance invoice and obtain the insurance invoice information. The electronic ticket data and insurance invoice information will be integrated to generate electronic itinerary data. Upload the electronic itinerary data to the tax system for verification; after successful verification, generate an electronic itinerary template file containing insurance invoice information.

[0013] Optional, If the electronic itinerary request received from the front-end system is a red-ink electronic itinerary request: Based on the electronic itinerary information that needs to be red-resolved carried in the request for red-resolved electronic itinerary, the status of the electronic ticket invoice is obtained from the TravelSky host ticket system and it is verified whether red-resolved is possible; Select Red-ink Reversal Data: If only red-ink reversal of electronic travel itineraries is required, the electronic travel itinerary data to be red-inked will be constructed and uploaded to the tax system; if red-ink reversal of insurance and electronic travel itineraries is required at the same time, the insurance system's red-ink reversal of insurance invoice information will be retrieved, the electronic travel itinerary data to be red-inked will be constructed, and uploaded to the tax system. Verify the red-inking result. If the red-inking is successful, generate a layout file for delivery.

[0014] This application also provides an electronic itinerary processing system for implementing the aforementioned method, the system comprising: The request receiving module is used to receive electronic itinerary requests from the front-end system; The itinerary processing module is used to respond to the electronic itinerary request, obtain electronic ticket data and insurance invoice information, and construct electronic itinerary data based on the electronic ticket data and insurance invoice information; The tax verification module is used to upload the electronic itinerary data to the tax system for verification and obtain the verification result returned by the tax system. The layout file generation module is used to generate layout files based on successfully verified electronic itinerary data.

[0015] This application also provides a computer-readable storage medium storing one or more programs that, when executed, can implement the aforementioned electronic itinerary processing method.

[0016] This application also provides a device, including a processor, a communication interface, a computer-readable storage medium, and a communication bus; wherein the processor, the communication interface, and the computer-readable storage medium communicate with each other through the communication bus; The processor is used to execute programs stored in a computer-readable storage medium.

[0017] Compared with the prior art, this application has the following advantages: 1. The electronic itinerary processing method proposed in this application constructs electronic itinerary data based on electronic ticket data and insurance invoice information, and verifies it through the tax system. It directly integrates insurance invoice information into the QR code of the electronic itinerary containing insurance, thereby achieving deep integration of itinerary data and insurance data. This solves the problem in the prior art where the electronic itinerary lists insurance expenses but the corresponding electronic invoice on the tax verification platform does not include these expenses, improving operability and convenience, and making implementation easier.

[0018] 2. By integrating core data such as insurance premium invoice number and insured amount into the electronic itinerary QR code and ticket, users can scan the code to query electronic ticket invoice and insurance invoice information, simplifying the user operation process and improving the travel service experience.

[0019] 3. By unifying the display standards of electronic itinerary receipts and tax inspection platforms for expense information, insurance expenses can be accurately matched in invoices, resolving the bottleneck of mismatched amounts during reimbursement and meeting financial compliance requirements.

[0020] 4. By building a cross-system data linkage management system, we help enterprises achieve linkage verification of itinerary and insurance information and full-process traceability, providing data support for service optimization and adapting to the digital upgrade and refined management needs of the air transport industry.

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

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

[0023] Figure 1 A flowchart illustrating the electronic itinerary processing method is shown; Figure 2 This application illustrates a schematic diagram of the process for issuing electronic travel itineraries according to an embodiment of the present application. Figure 3 A schematic diagram of the red-ink electronic travel record process according to an embodiment of this application is shown; Figure 4 A schematic block diagram of the electronic itinerary processing system is shown. Figure 5 This paper illustrates a schematic diagram of the interaction between the electronic itinerary processing system and an external system according to an embodiment of this application. Figure 6 A functional schematic diagram of the electronic itinerary processing system according to an embodiment of this application is shown; Figure 7 This is a schematic diagram of the structure of a device according to an embodiment of this application. Detailed Implementation

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

[0025] See appendix Figure 1 The electronic itinerary processing method of this application includes: S1. Receive electronic itinerary request from the front-end system; The electronic itinerary request includes: Requests for issuing electronic itinerary receipts, requesting red-ink electronic itinerary receipts, requesting to query electronic itinerary receipts, and requesting to download electronic itinerary receipts.

[0026] S2. Respond to the electronic itinerary request, obtain electronic ticket data and insurance invoice information, and construct electronic itinerary data based on the electronic ticket data and insurance invoice information; This involves calling the TravelSky mainframe ticketing system to obtain electronic ticket data, which includes ticket sales data, insurance premium data, and ticket status. The system retrieves insurance invoice information based on premium data. Electronic itinerary data is generated based on the electronic ticket data and insurance invoice information; This includes retrieving insurance invoice information from the insurance system based on electronic ticket data: If no insurance invoice information is found, the insurance system will be invoked to issue an insurance invoice and obtain the insurance invoice information.

[0027] S3. Upload the electronic itinerary data to the tax system for verification, and obtain the verification result returned by the tax system; S4. Generate a layout file based on the successfully verified electronic itinerary data.

[0028] This includes calling the TravelSky mainframe ticketing system to mark electronic tickets with issued electronic itineraries as invoices; and / or, Call the TravelSky mainframe ticketing system to remove the invoice printing mark from electronic tickets with red-inked electronic itineraries.

[0029] The process of issuing an electronic itinerary includes: If the electronic itinerary request received from the front-end system is a request to issue an electronic itinerary: In response to the request to issue an electronic itinerary, electronic ticket data is obtained from the TravelSky mainframe ticketing system; Based on the electronic ticket data, the insurance system is accessed to query and retrieve insurance invoice information: If the insurance system returns insurance invoice information, then the electronic ticket data and insurance invoice information are integrated to generate electronic itinerary data; If no insurance invoice information is found, the insurance system will be called to issue an insurance invoice and obtain the insurance invoice information. The electronic ticket data and insurance invoice information will be integrated to generate electronic itinerary data. If the insurance invoice fails to be issued, the reason for the failure will be returned. Upload the electronic itinerary data to the tax system for verification; after successful verification, generate an electronic itinerary template file containing insurance invoice information.

[0030] The process of creating a red-ink electronic itinerary includes: If the electronic itinerary request received from the front-end system is a red-ink electronic itinerary request: Based on the electronic itinerary information that needs to be red-resolved carried in the request for red-resolved electronic itinerary, the status of the electronic ticket invoice is obtained from the TravelSky host ticket system and it is verified whether red-resolved is possible; Select Red-ink Reversal Data: If only red-ink reversal of electronic travel itineraries is required, the electronic travel itinerary data to be red-inked will be constructed and uploaded to the tax system; if red-ink reversal of insurance and electronic travel itineraries is required at the same time, the insurance system's red-ink reversal of insurance invoice information will be retrieved, the electronic travel itinerary data to be red-inked will be constructed, and uploaded to the tax system. Verify the red-inking result. If the red-inking is successful, generate a layout file for delivery.

[0031] The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0032] The electronic itinerary processing method of this embodiment can be used to process the following electronic itinerary requests: Requests for issuing electronic itinerary receipts, requesting red-ink electronic itinerary receipts, requesting to query electronic itinerary receipts, and requesting to download electronic itinerary receipts.

[0033] 1. Issue electronic itinerary receipts.

[0034] In this embodiment, after all the travel has been completed, the passenger can obtain an electronic itinerary through the electronic itinerary processing method of this application embodiment, including: Receive a request to issue an electronic itinerary from the front-end system; In response to a request to issue an electronic itinerary, retrieve electronic ticket data from the TravelSky mainframe ticketing system; Based on the electronic ticket data, the insurance system is accessed to query and retrieve insurance invoice information: If the insurance system returns insurance invoice information, then the electronic ticket data and insurance invoice information are integrated to generate electronic itinerary data; If no insurance invoice information is found, the insurance system will be called to issue an insurance invoice and obtain the insurance invoice information. The electronic ticket data and insurance invoice information will be integrated to generate electronic itinerary data. If the insurance invoice fails to be issued, the reason for the failure will be returned. The electronic itinerary data is uploaded to the tax system for verification; after successful verification, an electronic itinerary document containing insurance invoice information (QR code containing insurance invoice information) is generated and delivered to the passenger. Call the TravelSky mainframe ticketing system to mark the invoice printing mark on the electronic tickets for which electronic itinerary slips have been issued.

[0035] 2. Red-ink electronic itinerary.

[0036] In this embodiment, after a passenger has obtained an electronic itinerary containing insurance information, if there is an error in the purchaser's information that prevents reimbursement, the airline and the agent can use the front-end system to initiate a red-ink cancellation application. The red-ink cancellation method for electronic itineraries in this embodiment includes: The system receives a request to redeem an electronic travel itinerary, which carries the information of the electronic travel itinerary that needs to be redeemed. Based on the request for red-inking electronic itinerary, retrieve the electronic ticket invoice status from the TravelSky mainframe ticketing system and verify whether red-inking is possible; Select Red Reversal Data: You can choose to reverse only the electronic itinerary or reverse both the insurance and electronic itinerary simultaneously. If you only reverse the electronic itinerary, the system will create the electronic itinerary data to be reversed and upload it to the tax system. If you reverse both the insurance and electronic itinerary simultaneously, the system will retrieve the insurance invoice information from the insurance system, create the electronic itinerary data to be reversed, upload it to the tax system, and check whether the electronic itinerary has been successfully reversed. After the red-inking process is successful, a formatted document is generated and delivered to the enterprise or individual, and the electronic ticket invoice printing indicator is removed.

[0037] In this embodiment, the electronic itinerary information includes: the electronic itinerary number and its corresponding electronic ticket number, email address, and other information.

[0038] 3. Download the successfully issued electronic itinerary template file.

[0039] In this embodiment, to facilitate passengers through airlines and travel agencies, after the electronic itinerary is successfully issued, the OFD or PDF version of the issued electronic itinerary can be downloaded upon customer request for delivery to passengers, including: The system receives a request to download an electronic itinerary, the request carrying the electronic itinerary information to be downloaded. Based on the recorded information from the electronic itinerary data, the layout generation service is invoked to generate a layout file and then returned.

[0040] 4. Check electronic itinerary.

[0041] In this embodiment, electronic travel itineraries can be queried according to customer requests: The system receives requests to query electronic travel itineraries from the front-end system. Based on the sales agency or electronic ticket number, it can apply to query historical information of electronic travel itineraries successfully issued on a specified date, read the database, and return a collection of information, which includes insurance invoice information and corresponding download links. The data is output in reverse chronological order of issuance time.

[0042] The following are specific embodiments of the electronic itinerary processing method of this application for processing the issuance, red-inking, querying, and downloading of electronic itineraries.

[0043] Figure 2 This is a schematic diagram illustrating the process of issuing an electronic itinerary in accordance with an embodiment of this application. In this embodiment, the specific process of issuing an electronic itinerary includes: Step 1: Verify Authorization. Upon receiving a request to issue an electronic itinerary for an electronic ticket with insurance, an authorization verification mechanism is implemented based on the sales agency. Step 2: Read electronic ticket sales data: Call the TravelSky mainframe ticketing system to read electronic ticket sales data (including passenger information, itinerary information, ticket price, and insurance premium); Step 3: Verify the status of the electronic ticket: Request that all flight segments on the electronic ticket have been completed, at least one flight segment has been used, and no other invoices have been issued; Step 4: Obtain insurance invoice information: Initiate a request to the insurance system to obtain the insurance invoice number and verify the insurance premium using the electronic ticket + insurance premium + purchaser's name + unified social credit code; Step 5: Insurance Invoice Information Result Inquiry: The insurance system asynchronously returns the ticket number, insurance premium amount, insurance premium invoice number, and insurance invoice download link; Step 6: Constructing Electronic Itinerary Receipts: Based on the electronic itinerary receipt numbering rules, assign unique electronic itinerary receipt invoice numbers to the electronic itinerary receipt invoices to be issued; simultaneously, construct electronic itinerary receipt data based on the obtained electronic ticket sales data, insurance invoice information, purchaser information, and seller information, and encode the insurance invoice information into the QR code data; Step 7: Tag the electronic ticket: Call the TravelSky mainframe ticketing system to mark the electronic ticket with an invoice printing identifier to prevent duplicate issuance; Step 8: Upload Invoice: Call the tax system interface to upload the electronic itinerary data; Step 9: Invoice Upload Result Inquiry: After the invoice is successfully uploaded, after 10 seconds to 10 minutes, use the "Acceptance Serial Number" returned by the invoice upload to call the tax system interface to check whether the electronic itinerary has been successfully received; Step 10: Cancel Labeling: If the invoice upload fails, call the TravelSky mainframe ticketing system to delete the electronic ticket printing label; Step 11: Generate format files: Generate electronic itinerary form OFD and PDF format files according to the requirements of the "Electronic Itinerary Form Format Information" document issued by the relevant management department; Step 12: Generate and send email: If the front-end request passed an email address, the generated layout file and insurance invoice link will be sent to the passenger via email.

[0044] Figure 3 This is a schematic diagram of the red-ink electronic itinerary flow chart according to an embodiment of this application. In this embodiment, the red-ink electronic itinerary includes: Step 13, Verify Permissions: Upon receiving a request for red-ink reversal of an electronic ticket containing insurance, a red-ink reversal permission verification mechanism is implemented based on the sales agency. Step 14: Obtain the electronic ticket invoice status: Call the TravelSky host ticketing system to obtain the electronic ticket invoice status and verify whether the current electronic ticket can be cancelled. Step 15: Request Red Invoice Reversal Information: Users can choose whether to initiate a red invoice reversal operation at the same time. If they choose yes, a red invoice reversal request will be sent to the insurance system using the insurance invoice number. If they choose no, this step will be skipped, and the following process will continue. Step 16: Constructing Electronic Itinerary Receipts: According to the electronic itinerary receipt numbering rules, assign unique electronic itinerary receipt invoice numbers to the electronic itinerary receipt invoices to be cancelled; based on the obtained electronic ticket sales data and insurance invoice information, construct the electronic itinerary receipt data and encode the insurance invoice information into the QR code data; Step 17: Upload the electronic travel itinerary data that needs to be reversed: Call the tax system interface to upload the electronic travel itinerary data that needs to be reversed; Step 18, Red Reversal Result Inquiry: Call the tax system interface to check whether the electronic itinerary was successfully reversed; Step 19: Generate format files: Generate electronic itinerary form OFD and PDF format files according to the invoice interface data specifications; Step 20: Perform Enterprise Delivery: If the purchasing enterprise is on the enterprise delivery list, generate delivery information and put it into the message queue in real time; the data in the message queue includes: electronic ticket number, electronic itinerary number / original electronic itinerary number (red ticket), invoicing status (normal / red cancellation), taxpayer identification number, enterprise name, issuance time (YYYY-MM-DD HH:MM:SS), sales outlet code, sales unit, international / domestic, government procurement verification number, ticket price (excluding tax), fuel surcharge (excluding tax), civil aviation development fund, other taxes and fees, VAT rate, tax amount, total, insurance premium, OFD version file, and PDF version file; Step 21: Perform personal delivery: If the front-end request includes an email address, the generated layout file will be sent to the passenger via email. Step 22: Cancel the label: After the invoice is successfully reversed, call the TravelSky host ticketing system to delete the electronic ticket printing label.

[0045] In this embodiment, the specific process of downloading the electronic itinerary includes: Step 23: Verify the download request: After receiving the request to download the electronic itinerary for the electronic ticket including insurance, query the electronic itinerary data and verify whether the current user has permission to download the electronic itinerary; Step 24: Generate layout files: Based on the electronic itinerary data, call the layout service to generate OFD and PDF layout files, and the QR code contains insurance invoice information; Step 25: Return the download results: Return the generated layout file and insurance invoice link to the front-end system.

[0046] In this embodiment, the specific process of querying and downloading electronic itinerary receipts includes: Step 26: Query the electronic itinerary of this sales agency: Enter the sales agency or the issuance date; call the electronic itinerary history query module to read the issuance database. If the read fails, the reason for the failure will be returned; if the read succeeds, the content returned will be a collection of information, with the data output in reverse order of issuance date. The query results include: invoice number, invoice status, domestic / international identification, passenger name, valid ID number, electronic ticket number, itinerary information (departure and arrival, carrier, flight number, seat class, departure date, etc.), fare information (fare, fuel surcharge, VAT rate, VAT amount, civil aviation development fund, other taxes and fees, total), purchaser company information (company name, company tax number), delivery email, issuance date, the ID of the person who made the reservation, sales agency information (sales agency number, company name), insurance premium, and the download link for the corresponding insurance invoice. Step 27: Query electronic itinerary by electronic ticket number (this airline): Enter the electronic ticket number or issuance date; call the electronic itinerary history query module to read the issuance database. If the read fails, the reason for the failure will be returned; if the read succeeds, the content returned will be a collection of information, with the data output in reverse order of issuance date; the query results include: invoice number, ticket status, domestic / international identification, passenger name, valid ID number, electronic ticket number, itinerary information (departure and arrival, carrier, flight number, seat class, departure date, etc.), fare information (fare, fuel surcharge, VAT rate, VAT amount, civil aviation development fund, other taxes and fees, total), purchaser company information (company name, company tax number), delivery email, issuance date, the ID of the person who made the reservation, sales agency information (sales agency number, company name), insurance premium, and the download link for the corresponding insurance invoice.

[0047] See appendix Figure 4 This application also provides an electronic itinerary processing system, including: The request receiving module is used to receive electronic itinerary requests from the front-end system; The itinerary processing module is used to respond to the electronic itinerary request, obtain electronic ticket data and insurance invoice information, and construct electronic itinerary data based on the electronic ticket data and insurance invoice information; The tax verification module is used to upload the electronic itinerary data to the tax system for verification and obtain the verification result returned by the tax system. The layout file generation module is used to generate layout files based on successfully verified electronic itinerary data.

[0048] like Figure 5 As shown, the electronic itinerary processing system of this application embodiment interacts with external front-end systems, travel information host ticketing systems, insurance systems, and tax systems to realize the issuance and red-inking of electronic itineraries containing insurance information, and delivers the issued or red-inked electronic itineraries to the requesting party, while providing download and query functions.

[0049] Front-end system: Used to trigger requests for issuing / reversing / downloading / querying electronic itineraries containing insurance information. The front-end system can be a B2B or B2C web front-end, APP, general sales front-end, etc.

[0050] TravelSky Mainframe Ticketing System: Used to provide electronic ticket data, including ticket sales data, insurance premium data, and ticket status (including invoice printing status), as well as to mark / cancel mark electronic tickets with issued / repeated electronic itineraries.

[0051] Insurance system: Used to query / generate / reverse insurance invoice information based on insurance premium data, and provide it to the electronic itinerary issuance system.

[0052] The tax system is used to achieve real-time data interaction with the electronic itinerary issuance system, verify the authenticity and accuracy of electronic itinerary data, and ensure the efficiency of tax collection and administration.

[0053] like Figure 6 As shown, the electronic itinerary processing system of this application embodiment provides the following functions: Issuance Function: Passengers can use the front-end system to apply for / renew electronic itinerary receipts including insurance; Red-card cancellation function: Processes business logic based on request operations, interacts with external systems to issue / cancel red-cards, and delivers them to passengers; Download function: Passengers or companies can download electronic itinerary templates and insurance invoices anytime, anywhere from the front-end system; Query function: Passengers or businesses can query electronic itinerary data and insurance invoice download links by sales agency or electronic ticket number.

[0054] Furthermore, embodiments of this application also provide an electronic itinerary processing device, comprising: The request receiving module receives electronic itinerary requests from the front-end system. The itinerary processing module responds to the electronic itinerary request, obtains electronic ticket data and insurance invoice information, and constructs electronic itinerary data based on the electronic ticket data and insurance invoice information; The tax verification module uploads the electronic itinerary data to the tax system for verification and obtains the verification result returned by the tax system. The layout file generation module generates layout files based on the successfully verified electronic itinerary data.

[0055] Based on the same concept, this application also provides a computer-readable storage medium storing one or more programs that, when executed, can implement the aforementioned electronic itinerary method.

[0056] like Figure 7 As shown in the illustration, this application also provides a device including a processor, a communication interface, a memory, and a communication bus. The processor, communication interface, and memory communicate with each other via the communication bus.

[0057] The memory is a computer-readable storage medium used to store one or more programs.

[0058] The processor is configured to execute a program stored in a computer-readable storage medium.

[0059] The computer-readable storage medium may be included in the device / apparatus described in the above embodiments; or it may exist independently and not assembled into the device / apparatus.

[0060] 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 processing electronic travel itineraries, characterized in that, include: Receive electronic itinerary requests from the front-end system; In response to the electronic itinerary request, obtain electronic ticket data and insurance invoice information, and construct electronic itinerary data based on the electronic ticket data and insurance invoice information; Upload the electronic itinerary data to the tax system for verification, and obtain the verification result returned by the tax system; Generate a layout file based on the successfully verified electronic itinerary data.

2. The method according to claim 1, characterized in that, The electronic itinerary request includes: Requests for issuing electronic itinerary receipts, requesting red-ink electronic itinerary receipts, requesting to query electronic itinerary receipts, and requesting to download electronic itinerary receipts.

3. The method according to claim 1, characterized in that, The step of responding to the electronic itinerary request, obtaining electronic ticket data and insurance invoice information, and constructing electronic itinerary data based on the electronic ticket data and insurance invoice information includes: The system calls the TravelSky mainframe ticketing system to obtain electronic ticket data, which includes ticket sales data, insurance premium data, and ticket status. The system retrieves insurance invoice information based on premium data. Electronic itinerary data is generated based on the electronic ticket data and insurance invoice information.

4. The method according to claim 3, characterized in that, The process of calling the insurance system to obtain insurance invoice information based on insurance premium data includes: Based on the electronic ticket data, the insurance system is accessed to query and retrieve insurance invoice information: If no insurance invoice information is found, the insurance system will be invoked to issue an insurance invoice and obtain the insurance invoice information.

5. The method according to any one of claims 2, characterized in that, Also includes: Call the TravelSky mainframe ticketing system to mark the electronic tickets with issued electronic itineraries with an invoice printing indicator; And / or, Call the TravelSky mainframe ticketing system to remove the invoice printing mark from electronic tickets with red-inked electronic itineraries.

6. The method according to any one of claims 2, characterized in that, Also includes: If the electronic itinerary request received from the front-end system is a request to issue an electronic itinerary: In response to the request to issue an electronic itinerary, electronic ticket data is obtained from the TravelSky mainframe ticketing system; Based on the electronic ticket data, the insurance system is accessed to query and retrieve insurance invoice information: If the insurance system returns insurance invoice information, then the electronic ticket data and insurance invoice information are integrated to generate electronic itinerary data; If no insurance invoice information is found, the insurance system will be called to issue an insurance invoice and obtain the insurance invoice information. The electronic ticket data and insurance invoice information will be integrated to generate electronic itinerary data. Upload the electronic itinerary data to the tax system for verification; After successful verification, an electronic itinerary document containing insurance invoice information will be generated.

7. The method according to any one of claims 2, characterized in that, Also includes: If the electronic itinerary request received from the front-end system is a red-ink electronic itinerary request: Based on the electronic itinerary information that needs to be red-resolved carried in the request for red-resolved electronic itinerary, the status of the electronic ticket invoice is obtained from the TravelSky host ticket system and it is verified whether red-resolved is possible; Select Red-ink Reversal Data: If only red-ink reversal of electronic travel itineraries is required, the electronic travel itinerary data to be red-inked will be constructed and uploaded to the tax system; if red-ink reversal of insurance and electronic travel itineraries is required at the same time, the insurance system's red-ink reversal of insurance invoice information will be retrieved, the electronic travel itinerary data to be red-inked will be constructed, and uploaded to the tax system. Verify the red-inking result. If the red-inking is successful, generate a layout file for delivery.

8. An electronic itinerary processing system, characterized in that, The system includes: The request receiving module is used to receive electronic itinerary requests from the front-end system; The itinerary processing module is used to respond to the electronic itinerary request, obtain electronic ticket data and insurance invoice information, and construct electronic itinerary data based on the electronic ticket data and insurance invoice information; The tax verification module is used to upload the electronic itinerary data to the tax system for verification and obtain the verification result returned by the tax system. The layout file generation module is used to generate layout files based on successfully verified electronic itinerary data.

9. A computer-readable storage medium storing one or more programs, characterized in that, When one or more of these programs are executed, the electronic itinerary processing method according to any one of claims 1-7 can be implemented.

10. An electronic device, comprising a processor, a communication interface, a computer-readable storage medium as described in claim 9, and a communication bus; wherein, The processor, communication interface, and computer-readable storage medium communicate electronically with each other via a communication bus; characterized in that, The processor is used to execute programs stored in a computer-readable storage medium.

Images