Air ticket change scheme pushing method and device, electronic equipment and storage medium

By obtaining user portraits and needs and generating personalized air ticket change solutions, the complex operation of air ticket change services in the existing technology is solved, efficient and automated change processes are realized, and user experience is improved.

CN119809762APending Publication Date: 2025-04-11TRAVELSKY TECHNOLOGY LIMITED
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202411883750.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-12-19
Publication Date
2025-04-11

AI Technical Summary

Technical Problem

In the prior art, air ticket change services rely on manual operations, resulting in complex operations, low efficiency, opaque information and poor user experience.

Method used

By obtaining the user portrait of the target user, determining user needs, generating personalized air ticket change plans, and sending them to the user's front-end equipment to realize an automated change process.

Benefits of technology

It improves the efficiency of air ticket changes, reduces user waiting time, simplifies operational processes, improves user experience, and reduces manual intervention.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119809762A_ABST
    Figure CN119809762A_ABST
Patent Text Reader

Abstract

The invention discloses an air ticket change scheme pushing method and device, electronic equipment and a storage medium, and the method comprises the steps: obtaining a target user portrait of a target user; determining a target user demand according to the target user portrait; generating a target air ticket changing scheme of the target user according to the demand of the target user; and sending the target air ticket change scheme to front-end equipment of the target user. The technical problem that in the prior art, air ticket changing scheme operation is too complex, and consequently user experience is poor is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of automation technology, and in particular to a method, device, electronic device and storage medium for pushing a ticket change plan. Background Art

[0002] In recent years, with the rapid development of the civil aviation industry, ticket change services have become an important part of the civil aviation industry. As a means of transportation with a high punctuality rate, people often consider the weather, wind speed, and flight punctuality of the destination when purchasing tickets. At the same time, by changing tickets before the flight departs, some costs can be saved and losses caused by flight delays and cancellations can be avoided. Before the plane takes off, due to various reasons such as weather, flight delays, personal emergencies, etc., users may choose to change tickets or cancel their trips. In most cases, users use manual operations such as telephone, official website, and dedicated customer service. This is inefficient, and the manual ticket change process is cumbersome, the change process information is not transparent, and the payment process is complicated.

[0003] The existing ticket change service mainly relies on manual operation and cannot realize automated change. The manual ticket change process is inefficient, the change process information is not transparent, the payment process is complicated, and the user experience is poor.

[0004] Currently, no corresponding solutions have been proposed for the above problems. Summary of the Invention

[0005] The embodiments of the present invention provide a method, device, electronic device and storage medium for pushing a ticket change plan, so as to at least solve the technical problem in the prior art that the ticket change plan operation is too complicated, resulting in a poor user experience.

[0006] According to one embodiment of the present invention, a method for pushing an air ticket change plan is provided, including: obtaining a target user portrait of a target user; determining the target user's needs based on the target user portrait; generating a target air ticket change plan for the target user based on the target user's needs; and sending the target air ticket change plan to the target user's front-end device.

[0007] Optionally, the method for pushing the ticket change plan also includes: obtaining target user information of the target user; and determining a target user portrait based on the target user information.

[0008] Optionally, the method for pushing the ticket change plan further includes: the target user information includes at least one of the following: user personal information, historical ticketing information and historical preference information.

[0009] Optionally, the method for pushing the ticket change plan also includes: obtaining initial user information of the target user; performing data preprocessing operations on the initial user information to obtain target user information, wherein the data preprocessing operations include at least some of the following operations: data cleaning, data deduplication and data normalization.

[0010] Optionally, the method for pushing the ticket change plan also includes: determining the target user type of the target user based on the target user portrait; obtaining target preference information corresponding to the target user type; and determining the target user needs based on the target preference information.

[0011] Optionally, the method for pushing the ticket change plan also includes: generating an initial ticket change plan for the target user based on the target user's needs, wherein the initial ticket change plan includes the changed flight information and the changed flight price; determining whether the changed flight is a saleable flight based on the changed flight information; and in response to the changed flight being a saleable flight, determining the initial ticket change plan as the target ticket change plan.

[0012] Optionally, the method for pushing the ticket change plan also includes: obtaining the initial flight price; calculating the price difference between the initial flight price and the changed flight price; and sending the price difference to the front-end device of the target user.

[0013] According to one embodiment of the present invention, a device for pushing an air ticket change plan is also provided, including: a first acquisition module, used to obtain a target user portrait of a target user; a determination module, used to determine the target user needs based on the target user portrait; a generation module, used to generate a target air ticket change plan for the target user based on the target user needs; a first sending module, used to send the target air ticket change plan to the front-end device of the target user.

[0014] Optionally, the first acquisition module includes: a first acquisition unit, used to obtain target user information of the target user; and a first determination unit, used to determine a target user portrait based on the target user information.

[0015] Optionally, the first acquisition module further includes: the target user information includes at least one of the following: user personal information, historical ticketing information and historical preference information.

[0016] Optionally, the first acquisition unit includes: an acquisition subunit, used to obtain the initial user information of the target user; an execution subunit, used to perform data preprocessing operations on the initial user information to obtain the target user information, wherein the data preprocessing operations include at least some of the following operations: data cleaning, data deduplication and data normalization.

[0017] Optionally, the determination module includes: a second determination unit, used to determine the target user type of the target user based on the target user portrait; a second acquisition unit, used to acquire target preference information corresponding to the target user type; and a third determination unit, used to determine the target user needs based on the target preference information.

[0018] Optionally, the generation module includes: a generation unit, used to generate an initial ticket change plan for the target user based on the target user's needs, wherein the initial ticket change plan includes the changed flight information and the changed flight price; a fourth determination unit, used to determine whether the changed flight is a saleable flight based on the changed flight information; and a fifth determination unit, used to determine the initial ticket change plan as the target ticket change plan in response to the changed flight being a saleable flight.

[0019] Optionally, the push device for the ticket change plan also includes: a second acquisition module for acquiring the initial flight price; a calculation module for calculating the price difference between the initial flight price and the changed flight price; and a second sending module for sending the price difference to the front-end device of the target user.

[0020] According to one embodiment of the present invention, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute any of the above-mentioned methods for pushing a ticket change plan.

[0021] According to one embodiment of the present invention, a computer-readable storage medium is further provided, wherein the computer-readable storage medium stores a computer program, wherein the computer program is configured to execute any of the above-mentioned methods for pushing a ticket change plan when running.

[0022] In an embodiment of the present invention, a target user portrait of a target user is obtained, and target user needs are determined based on the target user portrait, thereby achieving the purpose of generating a target ticket change plan for the target user based on the target user needs, and achieving the technical effect of sending the target ticket change plan to the front-end device of the target user, thereby solving the technical problem in the prior art that the ticket change plan operation is too complicated, resulting in a poor user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0024] Figure 1 This is a flow chart of a method for pushing a ticket change plan according to one embodiment of the present invention;

[0025] Figure 2This is a flow chart of a user operating a flight ticket change according to one embodiment of the present invention;

[0026] Figure 3 1 is a structural block diagram of a push device for a ticket change solution according to one embodiment of the present invention. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0028] It should be noted that the terms "first", "second", etc. in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] According to an embodiment of the present invention, an embodiment of a method for pushing a ticket change plan is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system containing at least one set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0030] The method embodiment can also be executed in an electronic device, a similar control device, or an electronic device that includes a memory and a processor. Taking an electronic device as an example, the electronic device may include one or more processors and a memory for storing data. Optionally, the electronic device may also include a communication device and a display device for communication functions. It will be understood by those skilled in the art that the above structural description is only illustrative and does not limit the structure of the above electronic device. For example, the electronic device may also include more or fewer components than those described in the above structural description, or have a configuration different from the above structural description.

[0031] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP) chip, a microcontroller unit (MCU), a field-programmable gate array (FPGA), a neural-network processing unit (NPU), a tensor processing unit (TPU), an artificial intelligence (AI) type processor, and the like. Among them, different processing units may be independent components or integrated into one or more processors. In some instances, the electronic device may also include one or more processors.

[0032] The memory can be used to store computer programs, such as a computer program corresponding to the method for pushing a ticket change solution in an embodiment of the present invention. The processor executes the computer program stored in the memory to implement the method for pushing a ticket change solution. The memory can include high-speed random access memory (RAM) and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory can further include memory remotely located from the processor, and these remote memories can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0033] The communication device is used to receive or send data via a grid. Specific examples of the aforementioned grid may include a wireless grid provided by a communication provider of the mobile terminal. In one example, the communication device includes a grid adapter (network interface controller, NIC), which can be connected to other grid devices via a base station to communicate with the Internet. In one example, the communication device can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly. In some embodiments of the present solution, the communication device is used to connect to mobile devices such as mobile phones and tablets, and can send instructions to the vehicle-mounted terminal via the mobile device.

[0034] The display device may be a touchscreen liquid crystal display (LCD) or a touch display (also referred to as a "touch screen" or "touch display"). The LCD may enable a user to interact with the user interface of the vehicle-mounted terminal. In some embodiments, the vehicle-mounted terminal may include a graphical user interface (GUI), and the user may interact with the GUI through finger contacts and / or gestures on the touch-sensitive surface. The human-computer interaction function may include a vehicle gear shifting function, and the executable instructions for executing the human-computer interaction function may be configured / stored in a computer program product or a readable storage medium executable by one or more processors.

[0035] Figure 1 FIG. 1 is a flow chart of a method for pushing a ticket change plan according to one embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0036] Step S102: Obtain a target user portrait of the target user.

[0037] Optionally, the execution subject of this embodiment is the ticket change plan push system. It should be noted that other electronic devices and processors can also serve as the execution subject, and no further limitation is given here.

[0038] Specifically, the ticket change plan push system also includes the following modules:

[0039] 1) User profiling module, which collects and analyzes user data to build user profiles. User data includes but is not limited to identity information, historical travel records, and preferences;

[0040] 2) Demand analysis module, connected to the user portrait module, analyzes the user's ticket change needs, including but not limited to changing time, destination, and cabin class;

[0041] 3) The recommendation model module is connected to the demand analysis module to generate a change plan that meets the needs based on user needs and flight information;

[0042] 4) The change processing module is connected to the recommendation model module. After the user selects a change plan, it automatically completes the change application processing, including connecting with the airline interface, order modification, and fee calculation;

[0043] 5) Payment optimization module, connected with the change processing module, optimizes the payment process in the payment change scenario and realizes automatic callback after payment is completed;

[0044] 6) Notification module, which is connected to the change processing module and the payment optimization module, notifies users of the change results through SMS, email, or APP push.

[0045] Specifically, the ticket change plan push system can significantly improve the efficiency of ticket changes and reduce user waiting time. It is suitable for online change service scenarios of airlines and ticketing platforms.

[0046] In the technical solution provided in the above step S102 of the present invention, in order to improve the convenience of users changing their air ticket plans, the present invention proposes an operation method for quickly changing air tickets. In order to implement the method, it is necessary to first construct a user profile of the target user who needs to change the air ticket.

[0047] Specifically, the user profiling module builds a profile of the target user based on their historical behavior data and preferences. By pre-building this profile, the ticket change solution push system can respond more quickly to user needs and provide more personalized services, making it suitable for scenarios with rich user behavior data.

[0048] Step S104: determining target user needs based on the target user portrait.

[0049] In the technical solution provided in the above step S104 of the present invention, the demand analysis module in the ticket change plan push system can further determine the user needs of the target user based on the constructed target user portrait.

[0050] Specifically, the demand analysis module can further analyze the target user's preferences based on user profiles, thereby deeply exploring their change needs and providing more precise change recommendations. This approach allows the ticket change proposal push system to better understand user needs, provide change options that better meet user expectations, and improve user satisfaction. This approach is suitable for change scenarios where users have specific preferences or needs.

[0051] Optionally, the change requirements of the target user include but are not limited to flight information such as the change time of the ticket, the ticket destination, and the cabin class.

[0052] Optionally, the demand analysis module may determine the user type of the target user based on the user portrait of the target user. For example, the user types may be divided into business travelers, leisure travelers, and high-frequency travelers.

[0053] Optionally, the demand analysis module can further determine the user needs of the target user based on the user type corresponding to the target user. For example, if the target user is a business traveler, it can be determined that the user needs of the target user may be to save time and arrive at the destination not too late, etc. Furthermore, the recommendation model module provides further ticket change plans based on the user needs of the above target user.

[0054] For example, if the user is a leisure traveler, the user's demand may be a cheaper air ticket or an earlier / later air ticket.

[0055] Step S106: Generate a target air ticket change plan for the target user according to the target user's needs.

[0056] In the technical solution provided in step S106 of the present invention, the demand analysis module can dynamically generate a change proposal based on the target user's needs and the real-time data of the current flight. This approach ensures the real-time and personalized nature of the recommended proposal and is suitable for scenarios requiring dynamic adjustment of the change proposal.

[0057] For example, if the target user is a business traveler, based on the target needs, a flight ticket with a time closer to the user's original flight ticket can be recommended to the user, and a flight ticket with a higher cabin class can also be recommended to the user.

[0058] For example, if the target user is a leisure traveler, relatively low-priced air tickets can be recommended to the user based on the corresponding target needs, and some red-eye flight tickets can also be recommended to the user.

[0059] Optionally, the recommendation model module, based on a machine learning algorithm, can update flight information in real time, ensuring the timeliness and accuracy of recommended solutions. This implementation ensures that the target flight change solutions recommended to the target user are up-to-date, avoiding change failures due to information lags, and is suitable for scenarios requiring real-time flight information updates.

[0060] Step S108: Send the target ticket change plan to the front-end device of the target user.

[0061] In the technical solution provided in the above step S108 of the present invention, the notification module may send the generated target ticket change plan of the target user to the front-end device of the target user to suggest the target user to adopt a suitable change plan.

[0062] Optionally, the ticket change notification system also has a pre-stored contact information feature to quickly notify users of change results. This approach ensures that users receive change information promptly and is suitable for all scenarios where user change notification is required.

[0063] From the above steps S102 to S108, it can be seen that in the present invention, if Figure 2 As shown, the target user portrait of the target user is obtained, and the target user needs are determined based on the target user portrait, thereby achieving the purpose of generating the target ticket change plan for the target user based on the target user needs, and achieving the technical effect of sending the target ticket change plan to the front-end device of the target user, thereby solving the technical problem in the prior art that the ticket change plan operation is too complicated, resulting in poor user experience.

[0064] This invention provides personalized, efficient, and accurate ticket change services by deeply analyzing user profiles and real-time flight information. Automated processing and payment optimization significantly enhance the user experience, reduce manual intervention, and lower operational complexity.

[0065] Furthermore, the ticket change solution push system can recommend relevant services and products based on predicted user behavior, further enhancing user satisfaction and system value. Pre-authorized payment processing and security considerations ensure a convenient and secure payment process, improving the efficiency and user trust of the ticket change service overall.

[0066] In practical applications, the aforementioned ticket change solution push system and method not only significantly improves change processing efficiency and reduces user wait time, but also increases user stickiness and enhances service quality through personalized recommendations. For airlines and ticketing platforms, this system and method effectively reduces customer service pressure and improves operational efficiency. By optimizing the payment process and ensuring payment security, it also enhances user trust in the platform and promotes its long-term development. For users, they can enjoy faster and more accurate change services and a more convenient payment experience, greatly improving travel convenience and satisfaction.

[0067] It's worth noting that, in practical applications, the system and method of this application have proven effective in improving change success rates, reducing user operation steps, and optimizing the payment process, thereby enhancing both service quality and user experience. Furthermore, through subsequent service and product combination recommendations, users can be provided with more travel options, further enhancing user satisfaction and the platform's market competitiveness.

[0068] The above method of this embodiment is further described in detail below.

[0069] As an optional implementation manner, obtaining a target user portrait of a target user includes: obtaining target user information of the target user; and determining a target user portrait according to the target user information.

[0070] In this embodiment, the user portrait module of the ticket change plan push system obtains the user portrait of the target user who needs to change the ticket, including the following steps: the user portrait module must first obtain the target user information of the target user, and then further construct the target user portrait based on the basic user information of the target user.

[0071] For example, based on the information provided by the user, the following user profile can be constructed:

[0072] 1. Name: xx

[0073] 2. Age: 25

[0074] 3. Gender: Female

[0075] 4. Occupation: Software Engineer

[0076] 5. Historical flight time preference: more flights are chosen during late night and early morning hours

[0077] 7. Historical flight seat preference: Window seats are chosen more often

[0078] 8. Historical airline preference: xx airline is chosen most often

[0079] Based on the above information, the user profile of this user is a young female software engineer. She likes to take xx Airlines flights late at night or early in the morning and prefers window seats.

[0080] As an optional implementation manner, the target user information includes at least one of the following: user personal information, historical ticketing information, and historical preference information.

[0081] In this embodiment, the target user information of the target user includes at least one of the following: basic personal information of the user, ticket information of the user's historical flights, and various preference information of the historical flights.

[0082] Optionally, after obtaining the historical flight ticket information in the above-mentioned target historical information, the time periods and airlines of the user's historical flights can be collected and screened to filter out the more concentrated time periods and airlines with more frequent flights in the user's historical flights, so as to determine the user's flight preferences.

[0083] Optionally, in addition to screening out the user's optimal preference, the ticket change plan push system also needs to determine the user's suboptimal preference, in case the user's optimal choice does not exist in the ticket plan that can be changed this time, the system can make recommendations based on the user's suboptimal preference.

[0084] As an optional implementation, obtaining target user information of a target user includes: obtaining initial user information of the target user; performing data preprocessing operations on the initial user information to obtain target user information, wherein the data preprocessing operations include at least some of the following operations: data cleaning, data deduplication, and data normalization.

[0085] In this embodiment, the ticket change plan push system obtains the target user information of the above-mentioned target user by the following steps: first, obtaining the initial user basic information of the target user, and then performing a data preprocessing operation on the above-mentioned unprocessed initial user information data to obtain the processed target user information, wherein the data preprocessing operation includes at least some of the following operations: data cleaning, data deduplication and data normalization.

[0086] Specifically, data preprocessing is an important step in data analysis, used to clean, transform, and prepare data for subsequent analysis. Data preprocessing includes the following main steps:

[0087] 1. Data cleaning: Detect and process erroneous values, missing values, and outliers in the data to ensure data quality.

[0088] 2. Data conversion: Standardize, normalize, discretize, and perform other processing on the data to ensure that the data is compared or calculated on the same scale.

[0089] 3. Data integration: Integrate data from multiple data sources into one data set to facilitate comprehensive analysis.

[0090] 4. Data reduction: Reduce the amount of data through aggregation, sampling and other methods to improve the efficiency of data processing and analysis.

[0091] 5. Feature selection: Select the most relevant and valuable features from the data to reduce model complexity and improve prediction accuracy.

[0092] 6. Data transformation: Transform data through methods such as feature extraction and dimensionality reduction to extract more useful information and reduce data dimensions.

[0093] Optionally, the purpose of data preprocessing is to make the data more suitable for machine learning and data mining analysis, thereby improving the accuracy and reliability of the analysis results.

[0094] For example, data preprocessing technology refers to a series of operations such as cleaning, conversion, and integration of data before data analysis and processing to ensure data accuracy and validity. Preprocessing is a very important step for one-click ticket changes. Its core technologies mainly include the following aspects:

[0095] 1) Data Preprocessing: Data preprocessing involves cleaning, deduplication, and normalizing raw data to improve data quality and enhance data analysis effectiveness. For one-click ticket changes, data preprocessing includes customer information, flight information, ticket type, price, and other information to facilitate subsequent business processing.

[0096] 2) Feature Selection: Feature selection is a crucial step in machine learning. It involves selecting features from raw data that are helpful for target prediction, thereby improving the model's prediction accuracy. In the one-click ticket change feature, feature selection can be performed based on factors such as a passenger's personal information and previous bookings, and recommendations can be made based on passenger needs and travel time.

[0097] 3) Data Modeling: Data modeling involves machine learning, where cleaned data is subjected to feature engineering and model training to create a model suitable for prediction. For one-click ticket changes, data modeling can be used to provide passengers with more intelligent upgrade recommendations based on classification, regression, or deep learning models.

[0098] 4) Model Optimization: Model optimization involves optimizing model parameters, feature selection, and algorithm selection after the model is established to improve model accuracy and prediction performance. For one-click ticket changes, model optimization can be performed based on factors such as the preferences, travel habits, and budgets of different passenger groups, providing more personalized recommendations.

[0099] As an optional implementation, determining target user needs based on the target user portrait includes: determining the target user type of the target user based on the target user portrait; obtaining target preference information corresponding to the target user type; and determining target user needs based on the target preference information.

[0100] In this embodiment, the ticket change plan push system determines the target user needs based on the target user portrait, including the following steps: the user portrait module can determine the user type of the target user based on the target user portrait, and further obtain the target preference information corresponding to the user type corresponding to the user, and determine the target user needs based on the target preference information.

[0101] Optionally, the demand analysis module may determine the user type of the target user based on the user portrait of the target user. Exemplarily, the user type may include but is not limited to business travelers, leisure travelers, and high-frequency travelers.

[0102] Optionally, the demand analysis module can further determine the user needs of the target user based on the user type corresponding to the target user. For example, if the target user is a business traveler, it can be determined that the user needs of the target user may be to save time and arrive at the destination not too late, etc. Furthermore, the recommendation model module provides further ticket change plans based on the user needs of the above target user.

[0103] For example, if the user is a leisure traveler, the user's demand may be a cheaper air ticket or an earlier / later air ticket.

[0104] As an optional implementation, generating a target ticket change plan for a target user based on the needs of the target user includes: generating an initial ticket change plan for the target user based on the needs of the target user, wherein the initial ticket change plan includes changed flight information and changed flight price; determining whether the changed flight is a saleable flight based on the changed flight information; and in response to the changed flight being a saleable flight, determining the initial ticket change plan as the target ticket change plan.

[0105] In this embodiment, the ticket change plan push system generates a target ticket change plan for a target user based on the target user's needs, including the following steps: a change processing module can generate an initial ticket change plan for the target user based on the target user's needs, wherein the initial ticket change plan includes the change flight information and the change flight price. After determining the optimal change plan for the user, the change processing module also needs to determine whether the flight of the optimal change plan is a saleable flight based on the real-time changed flight information. If it is determined that the optimal change flight is a saleable flight, the initial ticket change plan can be pushed to the user device as the target ticket change plan.

[0106] Specifically, the recommendation model module, powered by machine learning algorithms, updates flight information in real time, ensuring the timeliness and accuracy of recommended solutions. This approach ensures that recommended flight change solutions are up-to-date, preventing change failures due to information lags and is suitable for scenarios requiring real-time flight information updates.

[0107] Specifically, the change processing module automates change submission, fee calculation, and change confirmation. This approach significantly improves change processing efficiency, reduces manual intervention, and is suitable for scenarios requiring a high degree of automation.

[0108] Optionally, the ticket change solution push system also includes a follow-up recommendation mechanism for recommended services and product combinations. This mechanism can provide relevant service and product recommendations based on the user's predicted behavior after the ticket change. This approach can increase user stickiness and improve service quality, and is suitable for scenarios where follow-up recommendations are required.

[0109] As an optional implementation, the method further includes: obtaining an initial flight price; calculating a price difference between the initial flight price and the changed flight price; and sending the price difference to a front-end device of the target user.

[0110] In this embodiment, the above-mentioned method for pushing the ticket change plan also includes the following steps: the payment optimization module of the ticket change plan push system can first obtain the initial flight price, then calculate the difference between the initial flight price and the changed flight price, and send the above-mentioned price difference to the front-end device of the target user.

[0111] Specifically, the payment optimization module uses pre-authorized payment processing to simplify the payment change process. This method can simplify the payment process and improve the user experience, and is suitable for scenarios that require pre-authorized payment.

[0112] Optionally, the ticket change solution push system can integrate a payment interface to implement an internal payment process, including generating payment requests, monitoring payment status, and providing feedback on payment results. This approach ensures a smooth payment process and improves the user experience, making it suitable for scenarios requiring an internal payment process.

[0113] Through the description of the above embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus the necessary general hardware platform, or of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, or grid device, etc.) to execute the methods of various embodiments of the present invention.

[0114] This embodiment also provides a device for pushing a ticket change solution. This device is used to implement the above-mentioned embodiments and preferred implementations, and details already described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0115] Figure 3 is a structural block diagram of a push device 300 for a ticket change solution according to one embodiment of the present invention. Figure 3 As shown, the device includes: a first acquisition module 301, a determination module 302, a generation module 303 and a first sending module 304.

[0116] The first acquisition module 301 is used to obtain a target user portrait of a target user;

[0117] Determination module 302, for determining target user needs based on target user portraits;

[0118] Generating module 303, for generating a target ticket change plan for a target user according to the target user's needs;

[0119] The first sending module 304 is configured to send the target ticket change plan to the front-end device of the target user.

[0120] Optionally, the first acquisition module 301 includes: a first acquisition unit, configured to acquire target user information of a target user; and a first determination unit, configured to determine a target user portrait according to the target user information.

[0121] Optionally, the first acquisition module 301 further includes: the target user information includes at least one of the following: user personal information, historical ticketing information, and historical preference information.

[0122] Optionally, the first acquisition unit includes: an acquisition subunit, used to obtain the initial user information of the target user; an execution subunit, used to perform data preprocessing operations on the initial user information to obtain the target user information, wherein the data preprocessing operations include at least some of the following operations: data cleaning, data deduplication and data normalization.

[0123] Optionally, the determination module 302 includes: a second determination unit, used to determine the target user type of the target user based on the target user portrait; a second acquisition unit, used to obtain target preference information corresponding to the target user type; and a third determination unit, used to determine the target user needs based on the target preference information.

[0124] Optionally, the generation module 303 includes: a generation unit, used to generate an initial ticket change plan for the target user according to the target user's needs, wherein the initial ticket change plan includes the changed flight information and the changed flight price; a fourth determination unit, used to determine whether the changed flight is a saleable flight based on the changed flight information; and a fifth determination unit, used to determine the initial ticket change plan as the target ticket change plan in response to the changed flight being a saleable flight.

[0125] Optionally, the push device 300 for the ticket change plan also includes: a second acquisition module for acquiring the initial flight price; a calculation module for calculating the price difference between the initial flight price and the changed flight price; and a second sending module for sending the price difference to the front-end device of the target user.

[0126] An embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the above-mentioned method for pushing a ticket change plan.

[0127] Optionally, in this embodiment, the electronic device may be configured to store a computer program for performing the following steps:

[0128] Step S102, obtaining a target user portrait of the target user;

[0129] Step S104, determining target user needs based on the target user portrait;

[0130] Step S106, generating a target ticket change plan for the target user according to the target user's needs;

[0131] Step S108: Send the target ticket change plan to the front-end device of the target user.

[0132] Optionally, when executing the program, the processor further implements the following steps: obtaining target user information of the target user; and determining a target user portrait based on the target user information.

[0133] Optionally, when executing the program, the processor further implements the following steps: the target user information includes at least one of the following: user personal information, historical ticketing information, and historical preference information.

[0134] Optionally, when executing the program, the processor also implements the following steps: obtaining the initial user information of the target user; performing data preprocessing operations on the initial user information to obtain the target user information, wherein the data preprocessing operations include at least some of the following operations: data cleaning, data deduplication and data normalization.

[0135] Optionally, when executing the program, the processor further implements the following steps: determining the target user type of the target user based on the target user portrait; obtaining target preference information corresponding to the target user type; and determining the target user needs based on the target preference information.

[0136] Optionally, when executing the program, the processor further implements the following steps: generating an initial ticket change plan for the target user based on the target user's needs, wherein the initial ticket change plan includes the changed flight information and the changed flight price; determining whether the changed flight is a saleable flight based on the changed flight information; and in response to the changed flight being a saleable flight, determining the initial ticket change plan as the target ticket change plan.

[0137] Optionally, when executing the program, the processor further implements the following steps: obtaining the initial flight price; calculating the price difference between the initial flight price and the changed flight price; and sending the price difference to the front-end device of the target user.

[0138] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the above-mentioned substation environment analysis method when running on a computer or a processor.

[0139] Optionally, in this embodiment, the computer-readable storage medium may be configured to store a computer program for performing the following steps:

[0140] Step S102, obtaining a target user portrait of the target user;

[0141] Step S104, determining target user needs based on the target user portrait;

[0142] Step S106, generating a target ticket change plan for the target user according to the target user's needs;

[0143] Step S108: Send the target ticket change plan to the front-end device of the target user.

[0144] Optionally, the storage medium is configured to store program codes for executing the following steps: obtaining target user information of the target user; and determining a target user portrait based on the target user information.

[0145] Optionally, the storage medium is configured to store program codes for executing the following steps: the target user information includes at least one of the following: user personal information, historical ticketing information, and historical preference information.

[0146] Optionally, the storage medium is configured to store program code for executing the following steps: obtaining initial user information of the target user; performing data preprocessing operations on the initial user information to obtain target user information, wherein the data preprocessing operations include at least some of the following operations: data cleaning, data deduplication, and data normalization.

[0147] Optionally, the storage medium is configured to store program code for executing the following steps: determining a target user type of a target user based on a target user portrait; obtaining target preference information corresponding to the target user type; and determining target user needs based on the target preference information.

[0148] Optionally, the storage medium is configured to store program code for executing the following steps: generating an initial ticket change plan for the target user based on the target user's needs, wherein the initial ticket change plan includes the changed flight information and the changed flight price; determining whether the changed flight is a saleable flight based on the changed flight information; and in response to the changed flight being a saleable flight, determining the initial ticket change plan as the target ticket change plan.

[0149] Optionally, the storage medium is configured to store program codes for executing the following steps: obtaining an initial flight price; calculating a price difference between the initial flight price and the changed flight price; and sending the price difference to a front-end device of a target user.

[0150] Optionally, specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0151] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0152] In some embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0153] Units described as separate components may or may not be physically separate, and components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected to achieve the purpose of the present embodiment according to actual needs.

[0154] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0155] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server or grid device, etc.) to execute all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc., various media that can store program code.

[0156] The above are only preferred embodiments of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for pushing a ticket change plan, characterized in that: include: Obtain the target user portrait of the target user; Determine the target user's needs according to the target user portrait; Generate a target ticket change plan for the target user according to the target user's needs; The target air ticket change plan is sent to the front-end device of the target user.

2. The method for pushing a ticket change plan according to claim 1, characterized in that: Acquiring the target user portrait of the target user includes: Acquire target user information of the target user; The target user portrait is determined according to the target user information.

3. The method for pushing a ticket change plan according to claim 2, characterized in that: The target user information includes at least one of the following: user personal information, historical ticket information, and historical preference information.

4. The method for pushing a ticket change plan according to claim 2, characterized in that: Acquiring the target user information of the target user includes: Obtaining initial user information of the target user; A data preprocessing operation is performed on the initial user information to obtain the target user information, wherein the data preprocessing operation includes at least some of the following operations: data cleaning, data deduplication, and data normalization.

5. The method for pushing a ticket change plan according to claim 3, characterized in that: Determining the target user's needs according to the target user portrait includes: Determining a target user type of the target user according to the target user portrait; Obtaining target preference information corresponding to the target user type; The target user needs are determined based on the target preference information.

6. The method for pushing a ticket change plan according to claim 1, characterized in that: Generating the target ticket change plan for the target user according to the target user's needs includes: Generate an initial ticket change plan for the target user according to the target user's needs, wherein the initial ticket change plan includes changing flight information and changing flight prices; Determining whether the changed flight is a saleable flight based on the changed flight information; In response to the changed flight being the saleable flight, the initial ticket change plan is determined as the target ticket change plan.

7. The method for pushing a ticket change plan according to claim 6, characterized in that: The method further comprises: Get the initial flight price; Calculating the price difference between the initial flight price and the changed flight price; The price difference is sent to the front-end device of the target user.

8. A device for pushing a ticket change plan, characterized in that: include: A first acquisition module is used to acquire a target user portrait of a target user; A determination module, used to determine target user needs according to the target user portrait; A generating module, used for generating a target ticket change plan for the target user according to the target user's needs; The first sending module is used to send the target air ticket change plan to the front-end device of the target user.

9. An electronic device, comprising a memory and a processor, characterized in that: The memory stores a computer program, and the processor is configured to run the computer program to execute the method for pushing a ticket change plan as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method for pushing a ticket change plan as described in any one of claims 1 to 7 when running on a computer or a processor.

Citation Information

Patent Citations

  • Ticket buying recommendation method and device, electronic equipment and storage medium

    CN115797016A

  • Air ticket changing method and system, electronic equipment and storage medium

    CN116385091A