Method for assisting user in purchasing train ticket

Abstract

The invention relates to a method for assisting a user in purchasing train tickets. A periodic ticket booking configuration page is provided for the user, the periodic ticket booking configuration page is used for configuring a periodic ticket booking scheme, and the periodic ticket booking scheme comprises periodic travel time and a departure place and a destination of periodic travel. And in response to an operation of the user on the periodic ticket booking configuration page, starting a periodic ticket booking function. Therefore, train tickets can be automatically purchased according to the periodic ticket booking scheme. Therefore, convenient services can be provided for users with periodic travel (commuting) requirements, frequent ticket buying operation is avoided, the operation burden of the users is reduced, and the ticket buying requirements of commuting crowds can be better met.

Description

Technical Field

[0001] The present disclosure relates to the field of transportation, and particularly to a method for assisting users in purchasing train tickets. Background Art

[0002] Through research on the train ticket purchasing population, it is found that although the commuting population accounts for a very small proportion of the overall user population, the order volume contributed by it is very objective. The proportion of the order volume contributed by the commuting population is much higher than the proportion of the user population. At the same time, it is also noted that the special needs of the commuting population in the existing ticket purchasing scenarios have not been fully met. For the commuting population, the process of frequent ticket purchasing is a bit cumbersome and is easily forgotten, which affects normal travel.

[0003] Therefore, there is still a need for a train ticket purchase assistance solution that can meet the special needs of the commuting population. Summary of the Invention

[0004] One technical problem to be solved by the present disclosure is to provide a solution for assisting users in purchasing train tickets, which can better meet the ticket purchasing needs of the commuting population.

[0005] According to the first aspect of the present disclosure, there is provided a method for assisting users in purchasing train tickets, including: providing a periodic ticket booking configuration page to the user, the periodic ticket booking configuration page being used to configure a periodic ticket booking plan, the periodic ticket booking plan including a periodic travel time and the departure and destination of the periodic travel; in response to an operation of the user on the periodic ticket booking configuration page, enabling the periodic ticket booking function; and automatically purchasing train tickets according to the periodic ticket booking plan.

[0006] Optionally, the method further includes: judging whether the user may have a need for periodic travel between fixed stations according to the user's historical ticket purchase order data; in the case of determining that the user may have a need for periodic travel between fixed stations, asking the user whether they have a need for periodic travel between fixed stations. Among them, in the case where the user confirms that they have a need for periodic travel between fixed stations, the step of providing a periodic ticket booking configuration page to the user is executed.

[0007] Optionally, the method further includes: determining the user's historical periodic travel information between fixed stations according to the multiple ticket purchase order data between fixed stations in the user's historical ticket purchase order data, the historical periodic travel information between fixed stations including the departure and destination of the historical periodic travel between fixed stations, and the periodic travel time; automatically configuring the departure and destination of the periodic travel and the periodic travel time on the periodic ticket booking configuration page according to the historical periodic travel information between fixed stations; receiving the user's modification of the departure and / or destination of the periodic travel, and / or receiving the user's modification of the periodic travel time.

[0008] Optionally, the periodic ticket booking scheme may further include the desired train trips.

[0009] Optionally, the historical periodic travel information between fixed stations may further include the historical train trips.

[0010] Optionally, the method further includes: providing at least one train trip option in the periodic ticket booking configuration page; receiving the user's selection and / or adjustment of the desired train trip.

[0011] Optionally, the train trip options include the train trips that the user may be expected to desire.

[0012] Optionally, the method further includes: providing an entry for the periodic ticket booking management page on the train ticket related page, and in response to the user clicking on the management page entry, providing the periodic ticket booking configuration page when the periodic ticket booking function is not enabled, providing the periodic ticket booking management page when the periodic ticket booking function is enabled, and providing the periodic ticket booking scheme and the ticket reservation status corresponding to the nearest future travel itinerary in the periodic ticket booking management page.

[0013] Optionally, the method further includes: when the periodic ticket booking function is enabled, providing status information indicating that the periodic ticket booking function is enabled in association with the entry for the periodic ticket booking management page provided on the train ticket related page.

[0014] Optionally, the method further includes: in response to the first activation of the periodic ticket booking function, providing a floating window in association with the entry for the periodic ticket booking management page provided on the train ticket related page to prompt the user for the location and / or access path and / or function usage instructions of the periodic ticket booking management page.

[0015] Optionally, the method further includes: providing an entry for the train trip settings page in the periodic ticket booking configuration page and / or the periodic ticket booking management page, and in response to the user clicking on the train trip settings page entry, providing the train trip settings page, and providing multiple train trip options for the user to select in the train trip settings page, and the number of train trip options provided in the train trip settings page is greater than the number of train trip options provided in the periodic ticket booking configuration page.

[0016] Optionally, the method further includes: when the periodic ticket booking function is enabled, providing at least part of the content of the periodic ticket booking scheme and the ticket reservation status corresponding to the nearest future travel itinerary on the train ticket related page.

[0017] Optionally, the method further includes: in response to successful ticket purchase, providing a ticket issuance success prompt and / or a booking prompt for the next travel itinerary to the user.

[0018] Optionally, the method further includes: providing an entrance to an order list page on a periodic ticket booking management page, in response to a user clicking on the entrance to the order list page, providing the order list page, and providing in the order list page the un-traveled itinerary orders and the traveled itinerary orders of the booked train tickets.

[0019] Optionally, the method further includes: on a periodic ticket booking configuration page, when the user has not selected a desired train number for travel, setting the activation button for requesting to activate the periodic ticket booking function to be non-clickable, and in response to the user selecting a desired train number for travel, switching the activation button for requesting to activate the periodic ticket booking function to be clickable.

[0020] Optionally, the method further includes: when the periodic ticket booking function has been activated, on the periodic ticket booking management page, providing a function deactivation button, in response to the user clicking on the function deactivation button, providing an interface for receiving an instruction from the user to temporarily and / or permanently deactivate the periodic ticket booking function, and making the function deactivation button non-clickable during the ticket purchasing process before performing an operation to complete payment and issue the ticket.

[0021] Optionally, the method further includes: receiving the user's selection of a preferred train number among multiple desired train numbers for travel and / or setting the priority of multiple desired train numbers for travel; in the case where there are insufficient remaining tickets for the preferred train number or the train number with a higher priority to issue the ticket, automatically switching to purchasing an alternative train number other than the preferred train number or a train number with a lower priority among the multiple desired train numbers for travel, and prompting the user that the alternative train number or the train number with a lower priority has been booked.

[0022] Optionally, providing a preferred train number selection control or a train number priority setting control on the train number setting page to receive the user's selection of a preferred train number among multiple desired train numbers for travel and / or setting the priority of multiple desired train numbers for travel, wherein multiple train numbers for travel options are provided on the train number setting page for the user to select, and the number of train numbers for travel options provided on the train number setting page is greater than the number of train numbers for travel options provided on the periodic ticket booking configuration page.

[0023] Optionally, the method further includes: not providing a preferred train number selection control or a train number priority setting control on the periodic ticket booking configuration page.

[0024] Optionally, the method further includes: in the case where the user selects multiple train numbers as preferred train numbers, purchasing the train tickets of any one of the multiple preferred train numbers with the same priority.

[0025] Optionally, the periodic travel includes a departure journey and a return journey, the departure places and destinations of the departure journey and the return journey are opposite to each other, and on the periodic ticket booking configuration page, respectively receiving the user's configuration of the travel times and the desired train numbers for travel of the departure journey and the return journey.

[0026] Optionally, the method further includes: when the remaining tickets of the desired train trip are in short supply, providing a reminder message of insufficient remaining tickets on the main page related to train tickets; in response to the user clicking on the reminder message of insufficient remaining tickets, providing a train trip setting page, and providing options of train trips for the user to choose that the user has not selected in the train trip setting page.

[0027] Optionally, the method further includes: providing an activation button for requesting to activate the periodic ticket booking function on the periodic ticket booking configuration page; in response to the user clicking on the activation button, providing an automatic payment setting page for the user. Wherein, in response to the user completing the automatic payment setting, the step of activating the periodic ticket booking function is executed.

[0028] Optionally, the method further includes at least one of the following: receiving an instruction from the user to configure the length of the period for periodic travel; receiving an instruction from the user to temporarily and / or permanently turn off the periodic ticket booking function; receiving an instruction from the user to configure the date to start executing the periodic ticket booking function; receiving an instruction from the user to configure the number of days in advance to purchase tickets; receiving an instruction from the user to configure the ticket booking plan for legal holidays; configuring the ticket booking plan for legal holidays according to a preset policy.

[0029] Optionally, the preset policy includes at least one of the following: not executing the periodic ticket booking function on legal holidays; prompting the user to choose whether to execute the periodic ticket booking function on legal holidays; only executing the outbound ticket booking of the periodic ticket booking function when the start date of the legal holiday coincides with Saturday; and / or only executing the return ticket booking of the periodic ticket booking function when the end date of the legal holiday coincides with Sunday.

[0030] Optionally, the method further includes: sending a trip reminder to the user via SMS and / or social platform, and providing a link to cancel the current trip in the trip reminder. In response to the user clicking on the link to cancel the current trip, or sending a request to cancel the current trip via text or voice: when the train tickets related to the current trip have not been purchased, turning off the automatic reservation of the train tickets related to the current trip and providing a link to reactivate the automatic reservation of the train tickets for the current trip; and / or when the train tickets related to the current trip have been purchased, providing a link to cancel the order of the train tickets related to the current trip. In response to the user clicking on the link to cancel the order of the train tickets related to the current trip, entering the order page, and providing a ticket refund control and / or a ticket change control for the purchased train tickets related to the current trip in the order page.

[0031] Optionally, the trip reminder is sent to the user at at least one of the following time nodes: the time when train tickets are about to be automatically purchased; the time when the ticket refund fee is about to change; before the trip; before legal holidays.

[0032] According to a second aspect of the present disclosure, there is provided a computing device, including: a processor; and a memory storing executable code thereon, which, when executed by the processor, causes the processor to execute the method as described in the first aspect above.

[0033] According to a third aspect of the present disclosure, there is provided a computer program product including executable code, which, when executed by a processor of an electronic device, causes the processor to execute the method as described in the first aspect above.

[0034] According to a fourth aspect of the present disclosure, there is provided a non-transitory machine-readable storage medium storing executable code thereon, which, when executed by a processor of an electronic device, causes the processor to execute the method as described in the first aspect above.

[0035] Thus, it is possible to provide convenient services for users with periodic travel (commuting) needs, avoid frequent ticket purchasing operations, reduce the operation burden of users, and better meet the ticket purchasing needs of commuters. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] By describing the exemplary embodiments of the present disclosure in more detail in conjunction with the accompanying drawings, the above and other objects, features, and advantages of the present disclosure will become more apparent, wherein, in the exemplary embodiments of the present disclosure, the same reference numerals generally represent the same components.

[0037] Figure 1 is a schematic flowchart of a method for assisting a user in purchasing a train ticket according to the present disclosure.

[0038] Figure 2 is a schematic flowchart of a process for determining whether a user has periodic travel needs according to an embodiment of the present disclosure.

[0039] Figure 3 Schematically shows an interface for asking a user whether they have periodic travel needs on a train ticket related page.

[0040] Figures 4A to 4C Schematically shows an interface for configuring a periodic ticket booking plan.

[0041] Figure 5A and 5B Schematically shows an interface for payment settings.

[0042] Figure 6A and 6B Schematically shows an interface presented after enabling the periodic ticket booking function.

[0043] Figures 7A to 7D Schematically shows an interface for managing a periodic ticket booking plan.

[0044] Figures 8A to 8C Schematically shows an interface presented in the case of insufficient remaining tickets.

[0045] Figures 9A to 9F Schematically shows an interface for adjusting a periodic ticket booking scheme.

[0046] Figures 10A to 10D Schematically shows an interface for sending reminder messages to users.

[0047] Figure 10E Schematically shows an interface for providing users with functions of refunding tickets or changing ticket endorsements.

[0048] Figure 11 Shows a schematic structural diagram of a computing device that can be used to implement the method for assisting users in purchasing train tickets according to an embodiment of the present invention. Detailed implementation manners

[0049] The preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0050] The travel needs of commuting people generally focus on commuting between two cities on weekdays and commuting home on weekends, and often have the characteristic of multiple periodic trips, such as departing on Friday and returning on Sunday every week.

[0051] Commuting users often face some troubles. For example, even during the off-peak period when the ticket sources are abundant, the process of frequently purchasing tickets every week is cumbersome and easily forgotten. Sometimes, after successfully purchasing a ticket for the outbound journey, one forgets to purchase a ticket for the return journey in a timely manner. In addition, during the peak period when the ticket sources are tight, one may be unable to grab a ticket because the ticket has not been booked in advance. Especially during holidays, the problem is more prominent when forgetting to set an alarm to grab a ticket.

[0052] To solve the above problems, the present disclosure proposes a solution for assisting users in purchasing train tickets, providing better services for commuting users with periodic travel needs, which can be called "commuting assistant" for example. Users are authorized, for example, by subscription, and the system can automatically and continuously book round-trip commuting train tickets between fixed stations (OD, origin and destination) with a fixed frequency for users to reduce the operation burden of users. In the solution of the embodiment, it is also possible to further ensure smooth travel for users during the peak period. Thus, the periodic travel needs of commuting people can be better met.

[0053] It should be noted that the method of the present application can be executed on the server side, or on the client running on the user's mobile terminal, or can also be executed through the cooperation of the server side and the client.

[0054] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions, and corresponding operation entrances are provided for the user to choose to authorize or refuse.

[0055]

General Concept

[0056] Figure 1 It is a schematic flowchart of a method for assisting a user to purchase a train ticket according to the present disclosure.

[0057] As Figure 1 shown, in step S110, a periodic ticket booking configuration page is provided to the user.

[0058] For example, the server side can generate a periodic ticket booking configuration page and provide it to the client to present the periodic ticket booking configuration page to the user on the client. In the context of the present disclosure, the operation of providing various pages (or floating windows or page entrances) can either refer to the process in which the server side generates relevant pages (or floating windows or page entrances) and provides them to the client and thus to the customer, or refer to the process in which the client presents the page (or floating window or page entrance) received from the server side or self-generated relevant pages (or floating windows or page entrances) to the user, or refer to the process in which the server side and the client cooperate to generate relevant pages (or floating windows or page entrances) and present them on the client to provide to the user.

[0059] The periodic ticket booking configuration page is used to configure a periodic ticket booking plan. The periodic ticket booking plan can include the periodic travel time and the departure and destination of the periodic travel.

[0060] In some embodiments, the user only needs to configure the periodic travel time and the departure and destination of the periodic travel, and the system can automatically adapt the corresponding train number range and select an appropriate train number from the corresponding train number range to purchase a train ticket.

[0061] In some embodiments, the periodic ticket booking plan can further include the expected train number for travel. In this way, the user can select the expected train number for travel from multiple optional train number options.

[0062] In addition, the trips with periodic travel can include the outbound trip and the return trip, and the departure and destination of the outbound trip and the return trip are opposite to each other. On the periodic ticket booking configuration page, the user can be received to configure the travel time and the expected train number for the outbound trip and the return trip respectively. Alternatively, the user can also configure only a single trip for the outbound trip or the return trip. In this way, even when only the travel time and the expected train number for the outbound trip and the return trip configured by the user are received on the periodic ticket booking configuration page, the following operation to enable the periodic ticket booking function can also be performed.

[0063] In step S120, in response to the user's operation on the periodic ticket booking configuration page, the periodic ticket booking function is enabled.

[0064] The way to enable the periodic ticket booking function can be similar to the way of subscribing to services in many applications (APPs) for example. Through the user's authorization, the corresponding train tickets can be automatically ordered, and the automatic payment of the relevant fees can be realized, so as to automatically complete the process of purchasing train tickets and issuing tickets.

[0065] Therefore, in step S130, train tickets can be automatically purchased according to the periodic ticket booking plan.

[0066]

Discovery of commuting needs

[0067] In some embodiments, it can be determined whether the user has a commuting need by analyzing the user's historical travel records.

[0068] Figure 2 It is a schematic flowchart of the process of determining whether the user has a periodic travel need according to an embodiment of the present disclosure.

[0069] As Figure 2 shown, before providing the periodic ticket booking configuration page to the user in step S110, in step S210, according to the user's historical ticket purchase order data, it can be determined whether the user may have a need for periodic travel between fixed stations.

[0070] For example, the number of trips of the user between fixed stations can be counted. In the case where the user himself / herself is the traveler and the number of times of purchasing tickets and traveling between fixed stations within one year is higher than a set threshold (for example, 8 times), it can be preliminarily determined that the user may have a need for periodic travel between fixed stations.

[0071] In step S220, in the case where it is determined that the user may have a need for periodic travel between fixed stations, the user can be further asked whether he / she has a need for periodic travel between fixed stations.

[0072] Here, for example, on the train ticket related page of the client APP running on the user's mobile terminal, the user can be asked in a simple and natural way whether he / she often commutes (periodically travels) between these two stations.

[0073] Figure 3 Schematically shows an interface that asks the user whether they have a need for periodic travel on the train ticket related page.

[0074] As Figure 3 shown, on the train ticket related page of the APP (such as the main train ticket related page or the train ticket home page), for example, below the search box, in the middle of the page, a query statement "Often commute between Hangzhou and Shanghai?" can be presented based on speculation. Below it, the basis for the above speculation can also be presented, such as "12 orders for this train number have been detected recently" (that is, it is found that the user has traveled between these fixed stations several times recently). Correspondingly, confirmation ("Yes") or denial ("No") buttons (or controls) can be provided.

[0075] After the user clicks the denial ("No") button, this query can be closed.

[0076] On the other hand, when the user clicks the confirmation button ("Yes") and confirms the need for periodic travel between fixed stations, the operation of step S110 to provide the user with a periodic ticket booking configuration page is executed.

[0077]

Automatic Configuration

[0078] The following further describes the process of configuring the periodic ticket booking plan in the periodic ticket booking configuration page with reference to Figures 4A to 4C the examples.

[0079] Figures 4A to 4C Schematically shows an interface for configuring the periodic ticket booking plan.

[0080] Among them, Figure 4A schematically shows the interface when entering the periodic ticket booking configuration page when the user has not yet enabled the periodic ticket booking function.

[0081] In order to reduce the user's operations, facilitate the user to configure the periodic ticket booking plan, and more quickly enable the periodic ticket booking function, some travel information can be automatically configured in the periodic ticket booking configuration page.

[0082] Specifically, based on the multiple ticket purchase order data between fixed stations in the user's historical ticket purchase order data, the user's historical periodic travel information between fixed stations can be determined. The historical periodic travel information between fixed stations can, for example, include the departure place and destination of the historical periodic travel between fixed stations, and the periodic travel time.

[0083] Based on the periodic travel information between historical fixed stations, the departure place, destination, and periodic travel time of periodic travel can be automatically configured on the periodic ticket booking configuration page.

[0084] For example, in Figure 4A the example shown, based on the user's travel history, the departure place and destination can be automatically configured as "Hangzhou East" and "Shanghai Hongqiao", and the periodic travel time as "Go on Friday - Return on Sunday". It should be understood that in the case of purchasing round-trip tickets, the departure place and destination of the return journey are opposite to those of the outbound journey.

[0085] Corresponding controls or modules can be provided on the periodic ticket booking configuration page, and the user can modify the departure place, destination, and periodic travel time. For example, the user can click on the display area of the departure place "Hangzhou East" to trigger the modification of the departure place, click on the display area of the destination "Shanghai Hongqiao" to trigger the modification of the destination, and click on the display area of the periodic travel time "Go on Friday - Return on Sunday" to trigger the modification of the periodic travel time. These display areas can be configured as controls or configurable modules to trigger the corresponding modifications in response to being clicked. Figure 4A The display area of the frequency (cycle length) of periodic travel "Weekly Commute" and the configuration display area of the holiday ticket booking plan "Book or Not on Holidays" are also shown, which can be used to adjust the travel frequency and holiday travel plan accordingly. This will be further described in detail below.

[0086] In this way, on the periodic ticket booking configuration page, the user's modifications to any one or more of the departure place, destination, and periodic travel time of periodic travel can be received.

[0087] If the historical periodic travel information between historical fixed stations analyzed based on the user's previous historical ticket purchase orders is accurate enough, the accurate departure place, destination, and periodic travel time can be automatically configured. The user only needs to check and confirm.

[0088] In the case where the cycle of periodic travel is one week, for example, the periodic travel time can be a fixed day (one-way) or two days (round-trip) in a week, such as Friday (go) and Sunday (return).

[0089] In the case where the cycle is 10 days or one month, the periodic travel time can be the fixed i-th day (one-way) or the i-th and j-th days (round-trip) in the cycle, where i and j are the sequential numbers of the dates in the cycle.

[0090] In addition, the periodic travel time can be further specified to a time period within a corresponding day or two days, such as morning, afternoon, evening, or some other specifically set time period. For example, the periodic departure time can be from 18:00 to 19:00 on Friday, and the periodic return time can be from 21:00 to 23:00 on Sunday evening. The time period information can also be automatically configured based on the analysis of historical periodic travel information at fixed stations.

[0091] In some embodiments, as long as the departure location, destination, and periodic travel time are configured, the user can be allowed to enable the periodic ticket booking function. The system can select an appropriate train number to automatically purchase tickets according to the configured departure location, destination, and periodic travel time. An "Enable Automatic Reservation" button for requesting to enable the periodic ticket booking function can be provided on the periodic ticket booking configuration page. In response to the user clicking this enable button, the operation of enabling the periodic ticket booking function can be triggered.

[0092] In some other embodiments, it can be required that the user configure at least one expected travel train number before allowing the user to enable the periodic ticket booking function.

[0093] For example, in Figure 4A 's example, on the periodic ticket booking configuration page, when the user has not selected an expected travel train number, the "Enable Automatic Reservation" button for requesting to enable the periodic ticket booking function is set to be unable to be clicked, for example, it is presented in a gray state and cannot be clicked to trigger the enabling of the periodic ticket booking function. In response to the user selecting an expected travel train number, the "Enable Automatic Reservation" button for requesting to enable the periodic ticket booking function is switched to be able to be clicked, for example, it exits the gray state.

[0094] In this way, the periodic ticket booking scheme can also include the expected travel train number. As Figure 4A shown, considering the page size, two travel train numbers can be provided for each of the departure and return trips, and the train number information can be briefly given.

[0095] The historical periodic travel information between fixed stations can also include historical travel train numbers. In this way, at least one travel train number option is provided on the periodic ticket booking configuration page, and the travel train number option includes the travel train numbers that are predicted to be expected by the user. This can facilitate the user to select the expected travel train number, reduce the operation difficulty, and thus more conveniently guide the user to enable the periodic ticket booking function.

[0096] Correspondingly, on the periodic ticket booking configuration page, the user's selection and / or adjustment of the expected travel train number can be received. For example, a selection control can be provided associated with each travel train number option, and the user clicks the corresponding selection control to select the travel train number option as the expected travel train number.

[0097] In order to conveniently implement an efficient function enabling operation with less space occupied and less user attention in the periodic ticket booking configuration page, only a few train trip options are displayed in the periodic ticket booking configuration page. For example, there is one or two train trip options for each of the outbound and return trips.

[0098] In addition, an entrance to the train trip setting page can be provided in the periodic ticket booking configuration page. For example, Figure 4A in

[0099] “More Options” clickable display areas are respectively associated with the outbound and return trips in

[0100] as the entrance to the train trip setting page.

[0101] Figure 4B An example of the train trip setting page is schematically shown.

[0102] As Figure 4B shown, in the train trip setting page, for the outbound trip, multiple (5) train trip options are provided for the user to select. The number of train trip options provided in the train trip setting page (5) is more than the number of train trip options provided in the periodic ticket booking configuration page (2).

[0103] In this way, the user can set more desired train trips in the train trip setting page.

[0104] Figure 4B A button “Set as Alternative Option” for confirming the setting of the desired train trips is shown at the bottom. In response to the user clicking this button, these desired train trips can be confirmed and the periodic ticket booking configuration page can be returned to.

[0105] In some embodiments, when multiple desired train trips are configured through the train trip setting page, the display text of the entrance to the train trip setting page can be modified from the original “More Options” to the information of the configured number of train trips. For example, in the case where 4 desired train trips are selected for the outbound trip as Figure 4B shown, the display text of the entrance to the train trip setting page associated with the outbound trip in the periodic ticket booking configuration page can be modified to “4 Options Selected”.

[0106]

Preferred or Priority

[0107] In the case where a user selects multiple desired train trips for a single journey, such as the outbound or return journey, the user can be allowed to select a preferred train trip or set priorities for the multiple selected desired train trips.

[0108] On the train trip setting page, a preferred train trip selection control or a train trip priority setting control can be provided to receive the user's selection of the preferred train trip among multiple desired train trips and / or the priority setting for multiple desired train trips.

[0109] For example, as Figure 4B shown, on the train trip setting page, a preferred train trip click control can be provided in association with each train trip option for the user to select the preferred train trip.

[0110] The setting of priorities can be achieved, for example, by adjusting the sorting order of the selected desired train trips or by adjusting the priority information displayed in association with the selected desired train trips.

[0111] In this way, the user's selection of the preferred train trip among multiple desired train trips and / or the priority setting for multiple desired train trips can be received.

[0112] In the case where there are insufficient remaining tickets for the preferred train trip or the train trip with a higher priority to issue tickets, it can be automatically switched to purchasing an alternative train trip other than the preferred train trip or a train trip with a lower priority among the multiple desired train trips, and the user is prompted that the alternative train trip or the train trip with a lower priority has been booked.

[0113] Optionally, on Figure 4A the periodic ticket booking configuration page shown, a preferred train trip selection control or a train trip priority setting control may not be provided. In this way, it can avoid distracting the user's attention and increasing the difficulty for the user to enable the periodic ticket booking function, thus helping the user to complete the enabling operation of the periodic ticket booking function as soon as possible.

[0114] In addition, the user can also be allowed to select multiple train trips as the preferred train trips. In the case where the user selects multiple train trips as the preferred train trips, train tickets for any one of the multiple preferred train trips can be purchased with the same priority.

[0115] Figure 4C An example interface is schematically shown where the user has selected the desired train trips for the outbound and return journeys.

[0116] In response to the user clicking the "Enable Automatic Booking" enable button for requesting to enable the periodic ticket booking function, the enabling operation of the periodic ticket booking function can be triggered.

[0117]

Payment

[0118] In the case where the previous user has already set up automatic payment, the periodic ticket booking function can be directly enabled.

[0119] In the case where the user has not yet set up automatic payment, the user can be guided to complete the automatic payment setting. In response to the user clicking the enable button, an automatic payment setting page is provided to the user. Here, the automatic payment setting can be similar to the subscription function provided in some applications. With the user's consent, the passwordless payment function is enabled.

[0120] Figure 5A and 5B Schematically shows the interface of the payment setting.

[0121] Among them, Figure 5A Schematically shows the automatic payment setting page.

[0122] Such as Figure 5A As shown, in the automatic payment setting page, service details can be described, including the periodic travel time, departure place, destination, and in some embodiments, the expected train number for travel (for example, only the preferred expected train number for travel can be included). Further, the user's payment account and the deduction method can also be set.

[0123] In addition, a link to the "Payment Authorization Service Agreement" can be provided for the user to view.

[0124] After the user clicks the payment method confirmation button "Agree to the agreement and activate", it can be transferred to the notification interface of successful activation, as Figure 5B shown. In Figure 5B , it is informed the user that the passwordless payment function has been activated, and it can further be informed that "the deduction information will be notified through messages. Please turn on the notification function in the settings" to remind the user to turn on the notification function permission of the application.

[0125] Thus, in response to the user completing the automatic payment setting, the periodic ticket booking function can be enabled.

[0126] In Figure 5B the display interface, in response to the user clicking the "Complete" button, it can return to the train ticket related page (such as the train ticket related main page or the train ticket home page).

[0127] Such as Figure 3 shown, a periodic ticket booking management page entry can be provided on the train ticket related page (such as the train ticket related main page or the train ticket home page), for example Figure 3 the "Commute Assistant" label in the middle below as shown.

[0128] In response to the user clicking the management page entry, in the case where the periodic ticket booking function has not been enabled, in response to the user clicking the management page entry, it can provide Figure 4AThe periodic ticket booking configuration page shown guides the user to configure a periodic ticket booking plan to enable the periodic ticket booking function.

[0129] On the other hand, when the periodic ticket booking function is enabled, in response to the user clicking on the management page entry, a periodic ticket booking management page can be provided, and the periodic ticket booking plan and the train ticket reservation status corresponding to the nearest upcoming trip can be provided on the periodic ticket booking management page. The periodic ticket booking configuration page and the periodic ticket booking management page can be based on the same framework, except that the train number information display area presents different contents. The periodic ticket booking configuration page presents travel train number options for the user to select, while the periodic ticket booking management page presents the selected desired travel train number and the reservation status. The periodic order management page will be described in further detail below with reference to Figures 7A to 7D Further details will be provided about the periodic order management page.

[0130] Figure 6A and 6B Schematically shows the interface presented after enabling the periodic ticket booking function.

[0131] In response to the first-time enabling of the periodic ticket booking function, after returning to the train ticket-related page (such as the train ticket-related main page or the train ticket home page), as Figure 6A shown, a floating window can be provided in association with the periodic ticket booking management page entry provided on the train ticket-related page to prompt the user about the location and / or access path and / or function usage instructions of the periodic ticket booking management page entry "Commute Assistant".

[0132] For example, as Figure 6A shown, a finger icon can be used to indicate the location of the periodic ticket booking management page entry "Commute Assistant". The access path of the periodic ticket booking management page entry "Commute Assistant" can also be described in text as "Go to the train ticket home page and click on Commute Assistant". Additionally, a function usage instruction link for the periodic ticket booking function, "How to manage your 'Commute Assistant'", can be provided. In response to the user clicking on this link, more comprehensive function usage instructions will be presented to the user.

[0133] In addition, an elimination button "I got it" can also be provided on this floating window. In response to the user clicking on the elimination button "I got it", this floating window can be eliminated, and the normal display of the train ticket-related page (such as the train ticket-related main page or the train ticket home page) can be restored.

[0134] As Figure 6B shown, when the periodic ticket booking function is enabled, status information "Enabled" indicating that the periodic ticket booking function has been enabled can be provided in association with the periodic ticket booking management page entry "Commute Assistant" provided on the train ticket-related page (such as the train ticket-related main page or the train ticket home page). In contrast, in Figure 3In the shown interface, there is a display of the status information "Enabled".

[0135] In addition, as Figure 6B shown, when the periodic ticket booking function is enabled, on the train ticket related pages (such as the main train ticket related page or the train ticket home page), for example, in the middle part of the page, that is Figure 3 in the position where the original interface shown asked whether there was a commuting need, at least part of the periodic ticket booking plan and the train ticket booking status corresponding to the upcoming nearest travel itinerary are provided, for example: "Going at 18:00 every Friday | Returning at 21:00 every Sunday, Automatically booking...>".

[0136]

Management Page

[0137] As described above, when the periodic ticket booking function is enabled, in response to the user clicking on the management page entry, a periodic ticket booking management page can be provided.

[0138] Figures 7A to 7D Schematically shows an interface for managing the periodic ticket booking plan through the periodic ticket booking management page.

[0139] Figure 7A Schematically shows the periodic order management page when the booking status is "Ticket booking in progress".

[0140] As Figure 7A shown, in the train number information display area of the periodic order management page, the train numbers and status "Ticket booking in progress" for the outbound and return trips being booked are displayed.

[0141] For the sake of simple interface display, for the outbound and return trips, only the information of one expected travel train number can be displayed respectively, for example, it can be the information of the preferred train number.

[0142] Similar to Figure 4A the shown periodic ticket booking configuration page, in Figure 7A the shown periodic ticket booking management page, an entry "More Plans" for the train number setting page can also be provided. In response to the user clicking on the entry "More Plans" for the train number setting page, a train number setting page as Figure 4B shown is provided. When the user clicks on the entry "More Plans" for the train number setting page associated with the outbound and / or return trips, they can enter Figure 4B the shown train number setting page, presenting the expected travel train numbers selected by the user, and multiple travel train number options can also be provided for the user to choose, and the user can further adjust the expected travel train numbers.

[0143] When the periodic ticket booking function is enabled, in the periodic ticket booking management page, a function off button can be provided. As Figure 7AAs shown, the button below the interface can display the current reservation status "Round-trip ticket automatic reservation in progress". This button can be used as a function close button. In response to the user clicking the function close button, an interface for receiving instructions for the user to temporarily and / or permanently close the periodic ticketing function is provided, so that the user can set to temporarily or permanently close the periodic ticketing function, which will be described in further detail below.

[0144] In response to successful ticket purchase, a ticket issuance success prompt and / or a next travel itinerary ticketing prompt can be provided to the user on the periodic ticketing management page. Additionally, a ticket issuance success prompt and / or a next travel itinerary ticketing prompt can also be provided on the train ticket related page (the train ticket related main page or the train ticket home page).

[0145] Figure 7B The periodic order management page at the time of successful ticket purchase is schematically shown.

[0146] As Figure 7B shown, the ticket information that has been ordered in the train number information display area. For example, in addition to being able to display information such as the train number, departure place, destination, departure time, arrival time, total travel time, etc., specific ticket information such as the carriage number, seat number, seat class, price, aisle / window seat, etc. can be further detailedly displayed.

[0147] Additionally, during the ticketing process when a ticket has just been booked and before the operation to complete the payment and issue the ticket, the function close button can be made unable to be clicked. As Figure 7B shown, the function close button can be made gray to indicate that it cannot be clicked.

[0148] The current reservation status "Ticket issuance successful" can be displayed on the function close button, and it can further prompt "After this order is completed, the system will reserve the next itinerary".

[0149] As described above, in the case where there are insufficient remaining tickets for the preferred train number or the train number with a higher priority and the ticket cannot be issued, it can be automatically switched to purchase an alternative train number or a train number with a lower priority other than the preferred train number among multiple desired travel train numbers. At this time, the user can be prompted that an alternative train number or a train number with a lower priority has been reserved. If the user is not satisfied with the alternative train number or the train number with a lower priority, they can enter the order page to handle ticket refund or ticket change.

[0150] Figure 7C The periodic order management page in the case of purchasing an alternative train number or a train number with a lower priority is schematically shown.

[0151] As Figure 7CAs shown, when the ticket for the preferred train G39 could not be purchased on the return journey, a ticket for G112 was reserved. Thus, in the train number information display area, in addition to displaying the information of the purchased ticket, a prompt message "There are no tickets available for the G39 18:00 - 18:54 option. Another alternative has been reserved for you" is further provided in association with the return journey.

[0152] As Figures 7A to 7C shown, on the periodic ticket booking management page, an entrance "Commuting Order" to the order list page can be provided. In response to the user clicking on the entrance "Commuting Order" to the order list page, an order list page is provided, as Figure 7D shown. In the order list page, uncompleted journey orders and completed journey orders of the reserved train tickets are provided.

[0153] Figure 7D An order list page of the periodic ticket booking management function is schematically shown.

[0154] As Figure 7D shown, which shows the information and status of the tickets reserved for upcoming round trips this week, and also shows the information and status of the tickets for upcoming trips next week.

[0155] In the order list page, an entrance "View Order" to the order page of the corresponding order is provided in association with each order. In response to the user clicking on the entrance "View Order" to the order page, the order page of the corresponding order can be provided, presenting the detailed information of the corresponding order specifically.

[0156]

Reminder of Insufficient Remaining Tickets during Peak Periods

[0157] Figures 8A to 8C An interface presented in the case of insufficient remaining tickets is schematically shown.

[0158] When the remaining tickets for the desired train on the expected travel date are in short supply, a reminder of insufficient remaining tickets can be provided on the main page related to train tickets. For example, when the user selects a relatively small number of desired trains (e.g., only one desired train), it may be difficult to purchase train tickets for the desired trains during peak travel periods. Even when trying to grab tickets or waiting for the 12306 system to release tickets again, it may still be difficult to purchase tickets. At this time, a reminder of insufficient remaining tickets can be sent to the user to prompt the user to take appropriate measures.

[0159] Figure 8A An interface for providing a reminder of insufficient remaining tickets on the train ticket related page is schematically shown.

[0160] As Figure 8A shown, corresponding to Figure 3 asking whether there is a commuting need, Figure 6BProvide a region in a predetermined state that can prompt "Insufficient remaining tickets". Additionally, the reminder message can be displayed in a prominent and eye-catching manner, such as being bold, highlighted, or colored, in order to attract the user's attention.

[0161] In response to the user clicking on the reminder message for insufficient remaining tickets, a train schedule setting page can be provided. As Figure 8B shown, in the train schedule setting page, options for train schedules that the user has not yet selected for the trip are provided for the user to choose from. The user can supplement the desired train schedule in the train schedule setting page to increase the probability of successful ticket purchase. Figure 8B The train schedule setting page can be the same as the Figure 4B train schedule setting page, which will not be elaborated here.

[0162] In this way, if the actually purchased ticket does not match the user's set preferred train schedule or high-priority train schedule, a prompt can be made in the periodic ticket booking management page, as Figure 8C shown. Figure 8C The prompt message can be the same as the Figure 7C prompt message, which will not be elaborated here.

[0163] Incidentally, Figure 7C shows the interface in the state where a ticket has just been snatched and the payment and ticket issuance procedures have not been completed (during the ticket purchase process). In this state, as Figure 7B shown, the following function close button cannot be clicked, and the function close button can be made gray to indicate that it cannot be clicked. While Figure 8C shows the interface in the state where the payment and ticket issuance procedures have been completed. In this state, as Figure 7A shown, the following function close button can be clicked. The function close button can display "Round-trip ticket automatic booking in progress". In response to the user clicking on the function close button, an interface for receiving instructions for the user to temporarily and / or permanently close the periodic ticket booking function is provided, so that the user can set to temporarily or permanently close the periodic ticket booking function, which will be further described in detail below.

[0164]

Ticket Booking Function Settings

[0165] The configuration of the periodic ticket booking plan can include, in addition to the aforementioned configuration of the departure location, destination, periodic travel time, and desired train schedule, the configuration of the travel frequency (cycle length), special plans for holidays, the function start date, etc.

[0166] Figures 9A to 9F Schematically shows some interfaces for adjusting the periodic ticket booking plan.

[0167] Figure 9ASchematically highlights the configuration entry in the periodic ticket booking configuration page that allows users to make further configurations.

[0168] Figure 9A Taking the periodic ticket booking configuration page as an example for display. It should be understood that in the case where the periodic ticket booking function has been enabled, the same configuration can also be made in the periodic ticket booking management page to further adjust the previously configured plan.

[0169] As Figure 9A shown, the departure location "Hangzhou East", the destination "Shanghai Hongqiao", the periodic travel time "Go on Friday - Return on Sunday", the commuting frequency (cycle length) "Commute weekly", and the special plan for holidays "Book or not on holidays" can all be modified or adjusted. In response to the user clicking on the corresponding display area, for example, a configuration interface for the corresponding item can be provided to modify or adjust the corresponding item. For example, a floating window can pop up below the interface as the configuration area for the corresponding item, and the floating window can provide the corresponding configuration options and confirmation and / or cancellation buttons.

[0170] In addition, it should be understood that an instruction for the user to configure the number of days to purchase tickets in advance can also be received to configure how many days in advance to start purchasing tickets. The current regular advance sale days for train tickets in the 12306 system is 15 days. The number of days to purchase tickets in advance can be set to the same as the number of days the 12306 system starts selling tickets in advance. Or, it can also be set to less than the number of days the 12306 system starts selling tickets in advance according to the user's needs. For example, the user may hope to have the opportunity to reconsider the travel plan a few days in advance before each trip, so may hope to start purchasing tickets only one week or three days in advance. In this way, corresponding configuration adjustments can be made to meet the user's needs.

[0171] Figure 9B Schematically shows the configuration interface for the periodic travel time.

[0172] In response to the user clicking on the periodic travel time "Go on Friday - Return on Sunday" in the periodic ticket booking configuration page or the periodic ticket booking management page as Figure 9A shown, the interface as Figure 9B shown can be provided.

[0173] As Figure 9B shown, multiple departure times, such as "Go on Thursday", "Go on Friday", "Go on Saturday", "Go on Sunday", etc., can be provided in the left column for the user to choose, and multiple return times, such as "Return on Saturday", "Return on Sunday", "Return on Monday", "Return on Tuesday", etc., can be provided in the right column for the user to choose.

[0174] The user can make selections respectively, and after selecting the round-trip time, click the "OK" button to complete the setting. The floating window can disappear accordingly, and the periodic travel time displayed in the corresponding area on the periodic ticket booking configuration page or the periodic ticket booking management page is adjusted accordingly.

[0175] Figure 9C Schematically shows the configuration interface of the periodic travel frequency.

[0176] In response to the user clicking on the "Weekly Commute" of the periodic travel frequency on the periodic ticket booking configuration page or the periodic ticket booking management page as shown in Figure 9A it can provide the interface shown in Figure 9C .

[0177] As shown in Figure 9C , multiple optional travel frequencies (the length of the period of periodic travel) can be provided, for example, "Daily Commute", "Weekly Commute", "Bi-Weekly Commute", "Tri-Weekly Commute", "Monthly Commute", etc. for the user to choose from, so as to receive the instruction from the user to configure the length of the period of periodic travel (travel frequency).

[0178] The user can make selections according to needs, and after selecting the travel frequency, click the "Confirm" button to complete the setting. Clicking the "Cancel" button can cancel the current modification or adjustment and retain the original configuration. After the user clicks the "Confirm" or "Cancel" button, the floating window can disappear accordingly, and the periodic travel frequency displayed in the corresponding area on the periodic ticket booking configuration page or the periodic ticket booking management page is adjusted accordingly.

[0179] Figure 9D Schematically shows the configuration interface for closing the periodic ticket booking function.

[0180] In response to the user clicking the function closing button (on which the booking status "Round-trip ticket automatic booking in progress" is displayed) on the periodic ticket booking management page as shown in Figure 7A or 8C, it can provide the interface shown in Figure 9D .

[0181] As shown in Figure 9D , multiple temporary closing scheme options and a permanent closing option can be provided, for example, "Temporarily close for 1 week", "Temporarily close for 1 week", "Temporarily close for 1 week", "Temporarily close for 1 week", "Temporarily close for 1 week", etc. for the user to choose from, so as to receive the instruction from the user to temporarily and / or permanently close the periodic ticket booking function.

[0182] Users can make selections according to their needs. After selecting the option to temporarily or permanently close the solution, click the "Confirm" button to complete the setting. Clicking the "Cancel" button can cancel the current modification or adjustment and retain the original configuration. After the user clicks the "Confirm" or "Cancel" button, the floating window can disappear accordingly, and the reservation status displayed in the corresponding area on the periodic ticket booking management page (such as the reservation status "Round-trip ticket automatic reservation in progress" on the function close button) is adjusted accordingly (such as adjusted to "Temporarily closed for 1 week").

[0183] Figure 9E Schematically shows a configuration interface for setting the date to start executing the periodic ticket booking function.

[0184] In response to the user clicking on the periodic ticket booking configuration page or the periodic ticket booking management page as shown in Figure 4A 、 4C 、7A to 7C or 8C on the periodic ticket booking start dates "Start on Friday, August 23" and "Start on Sunday, August 25" respectively associated with the outbound and return trips, the interface shown in Figure 9E can be provided.

[0185] As shown in Figure 9E , multiple optional start times for the outbound trip can be provided, such as "This week", "Next week (August 23)", "The week after next (August 30)", "September 6" (farther times can be directly represented by specific dates), etc. for the user to choose to receive the user's instruction to configure the date to start executing the periodic ticket booking function.

[0186] Users can make selections according to their needs. After selecting the date to start executing the periodic ticket booking function, click the "OK" button to complete the setting. After the user clicks the "OK" button, the floating window can disappear accordingly, and the date to start executing the periodic ticket booking function displayed in the corresponding area on the periodic ticket booking configuration page or the periodic ticket booking management page is adjusted accordingly.

[0187] Figure 9F Schematically shows a configuration interface for setting whether to execute the periodic ticket booking function on legal holidays.

[0188] In response to the user clicking on the commuting frequency "Commute weekly" on the periodic ticket booking configuration page or the periodic ticket booking management page as shown in Figure 9A , the interface shown in Figure 9F can be provided.

[0189] As shown in Figure 9F , the upcoming legal holidays and the dates before and after can be displayed in the floating window, for example, it can include the holiday itself and the dates of the adjusted working days and adjusted holiday days before and after. The user is to select whether to continue the periodic travel itinerary for this legal holiday and the corresponding adjusted working days and adjusted holiday days.

[0190] In the context of the present disclosure, the term "statutory holiday" does not include weekends. According to the "Regulations on National Annual Festivals and Memorial Days", the statutory holidays in China include New Year's Day, Spring Festival, Tomb-Sweeping Day, Labor Day, Dragon Boat Festival, Mid-Autumn Festival, National Day, etc., and these festivals are days when all citizens have holidays. Weekends, namely Saturday and Sunday, are rest days. Although they are sometimes used in combination with the rescheduled holidays, they do not belong to the category of statutory holidays themselves.

[0191] When it comes to statutory holidays, the time that needs to be considered by the user can include the statutory holidays themselves, the corresponding rescheduled holiday days, and the corresponding rescheduled working days. In the context of the present disclosure, the statutory holidays themselves, the corresponding rescheduled holiday days, and the corresponding rescheduled working days can be collectively referred to as the "period during statutory holidays".

[0192] For example, as Figure 9F shown, for the upcoming Mid-Autumn Festival and National Day, the corresponding national statutory holidays, rescheduled holiday days, and rescheduled working days can be respectively displayed, and configuration controls can be provided for the user to select, so as to receive the instruction from the user to configure the ticket booking plan for statutory holidays.

[0193] The user can make selections according to their needs, and after selecting whether to continue the periodic travel itinerary on the selected holiday, click the "OK" button to complete the setting. After the user clicks the "OK" button, the floating window can disappear accordingly.

[0194] In addition, the ticket booking plan for statutory holidays can also be configured according to a preset strategy, and the configured plan can be used as the default plan, and the user can make corresponding adjustments according to their actual needs.

[0195] The preset strategy can include at least one of the following: not executing the periodic ticket booking function during statutory holidays; prompting the user to select whether to execute the periodic ticket booking function during statutory holidays; only executing the outbound ticket booking of the periodic ticket booking function when the start date of the statutory holiday coincides with Saturday; only executing the return ticket booking of the periodic ticket booking function when the end date of the statutory holiday coincides with Sunday.

[0196] For example, when the preset strategy is not to book tickets during the default statutory holiday period, a selection control can be provided in association with the corresponding holiday. The user's selection of the selection control indicates that the periodic ticket booking function still needs to be executed during this holiday period, and the non-selection of the selection control indicates that the periodic ticket booking function does not need to be executed during this holiday period.

[0197]

Reminder

[0198] The periodic ticket booking function of the present disclosure needs to be executed for a long time. During the execution process, various information is often reminded to the user. In addition to providing reminder information on the client of the application running the ticketing assistance solution, various reminder information can also be sent to the user via SMS and / or social platforms.

[0199] Figures 10A to 10D An interface for sending reminder information to the user is schematically shown.

[0200] As Figure 10A shown, trip reminders can be sent to the user via SMS and / or social platforms. For example, it can remind "You plan to depart from Hangzhou East to Shanghai Hongqiao on September 13, 2024 (Friday) and return from Shanghai Hongqiao to Hangzhou East on September 15, 2024 (Sunday)". A commuting order link can also be provided. In response to the user clicking on the commuting order link, commuting order information can be presented to the user (for example, the order page of the client of the application running the ticketing assistance solution can be entered).

[0201] In addition, a link "Cancel Trip" to cancel the current trip can be provided in the trip reminder, or a reminder message for canceling the trip can be given, such as "If you have a temporary change and don't plan to travel, you can say 'Cancel Trip' to me, and the background will automatically cancel this commuting plan for you temporarily". The text "Cancel Trip" can be configured as a link to cancel the current trip.

[0202] When approaching a legal holiday, more reminder information can be provided. For example, as Figure 10B shown, in addition to the regular trip reminder, it can further remind and explain the possible conflict between the legal holiday and the periodic ticket booking plan configured by the user. For example, "Due to the approaching Mid-Autumn Festival, you need to work on September 16 (Saturday) due to the holiday adjustment, which conflicts with your travel arrangement". Further, a recent calendar can be provided, marking the legal holidays, adjusted holiday days, and adjusted working days, so that the user can make a decision.

[0203] In response to the user clicking on the link "Cancel Trip" to cancel the current trip in Figure 10A or the information reminder interface shown in Figure 10B, or sending a request to cancel the current trip through text or voice, such as "I want to cancel the trip", the corresponding operation to cancel the trip can be executed.

[0204] In the case where the train tickets related to the current trip have not been purchased yet, as Figure 10C shown, the automatic reservation of the train tickets related to the current trip can be directly closed. Correspondingly, a reminder message can be sent to the user: "The automatic reservation of this week's commuting trip order has been closed for you".

[0205] In addition, a link to restart the automatic reservation of train tickets for this trip can be provided, along with a prompt "You can click to restart".

[0206] In this way, the user can adjust the corresponding travel configuration, cancel this travel plan, and temporarily turn off the periodic ticket booking function without further operation in the client of the application running this ticket purchase assistance solution.

[0207] In addition, in the case where train tickets related to this trip have already been purchased, as Figure 10D shown, a link "Cancel the automatic reservation for this trip" to cancel the train ticket order related to this trip can be provided.

[0208] In response to the user clicking the link "Cancel the automatic reservation for this trip" to cancel the train ticket order related to this trip, the order page of the client of the application running this ticket purchase assistance solution can be entered, as Figure 10E shown. Figure 10E An interface providing the ticket refund or rescheduling function to the user is schematically shown.

[0209] In the order page, "Ticket refund" controls and / or "Rescheduling" controls for the purchased train tickets related to this trip can be provided. In response to the user clicking the "Ticket refund" control or the "Rescheduling" control, the user is guided to perform the corresponding operation.

[0210] It should be understood that when the user clicks the order page entry "View order" corresponding to a certain order in the Figure 7D shown order list page, the Figure 10E shown order page can also be provided, and the user can also manage the un-traveled orders, such as canceling the itinerary that has not been ticketed or performing ticket refund or rescheduling on the itinerary that has been ticketed.

[0211] Trip reminders can be sent to the user at multiple time nodes before the user travels.

[0212] For example, a trip reminder can be sent to the user at the time approaching the automatic purchase of train tickets, such as one day before the set date to start ordering train tickets (e.g., 15 days before the actual travel date), so that the user can pay attention to the trip before purchasing tickets and cancel the trip in time if needed.

[0213] For another example, a trip reminder can be sent to the user before traveling, such as one day before traveling and / or before the departure time on the day of traveling, so as to remind the user to travel in time and perform ticket refund or rescheduling in time if needed.

[0214] For another example, as mentioned above, a trip reminder can be sent to the user before legal holidays, so that the user can make corresponding trip adjustments according to the special circumstances of legal holidays.

[0215] For another example, a travel reminder can be sent to the user at the time when the refund fee is about to change, so as to minimize the refund fee in case the user needs to refund the ticket and reduce the user's economic loss.

[0216] Currently, the refund fee charging rules are as follows: if the ticket is refunded more than 8 days before departure, 5% of the ticket price will be charged; 30% if it is refunded 48 hours before departure; and 50% if it is refunded within 48 hours before departure. In this way, a travel reminder can be sent to the user, for example, on the 9th day before departure and on the 3rd day before departure, so that the user can refund the ticket in time if needed and avoid incurring a higher refund fee.

[0217] Through the auxiliary ticket purchase scheme according to the present disclosure, convenient services can be provided for users with periodic travel (commuting) needs, avoiding the operation of frequent ticket purchases, reducing the user's operation burden, and better meeting the ticket purchase needs of the commuting population. According to the method of the embodiment, it is possible to avoid delaying the journey due to the user forgetting to purchase a ticket, and it is also possible to reduce or even avoid the situation of difficult ticket purchase during the peak period when the ticket source is tight. Correspondingly, the auxiliary ticket purchase scheme of the present disclosure can provide a better experience for commuting users.

[0218] Figure 11 FIG. shows a schematic structural diagram of a computing device that can be used to implement the above method for assisting a user in purchasing a train ticket according to an embodiment of the present invention.

[0219] See Figure 11 , the computing device 1100 includes a memory 1110 and a processor 1120.

[0220] The processor 1120 can be a multi-core processor or can include multiple processors. In some embodiments, the processor 1120 can include a general-purpose main processor and one or more special coprocessors, such as a graphics processing unit (GPU), a digital signal processor (DSP), etc. In some embodiments, the processor 1120 can be implemented using custom circuits, such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0221] The memory 1110 may include various types of storage units, such as system memory, read-only memory (ROM), and permanent storage devices. Among them, the ROM may store static data or instructions required by the processor 1120 or other modules of the computer. The permanent storage device may be a readable and writable storage device. The permanent storage device may be a non-volatile storage device that does not lose the stored instructions and data even when the computer is powered off. In some embodiments, the permanent storage device employs a mass storage device (such as a magnetic or optical disk, flash memory) as the permanent storage device. In some other embodiments, the permanent storage device may be a removable storage device (such as a floppy disk, optical drive). The system memory may be a readable and writable storage device or a volatile readable and writable storage device, such as dynamic random access memory. The system memory may store some or all of the instructions and data required by the processor during operation. In addition, the memory 1110 may include any combination of computer-readable storage media, including various types of semiconductor storage chips (DRAM, SRAM, SDRAM, flash memory, programmable read-only memory), and magnetic disks and / or optical disks may also be employed. In some embodiments, the memory 1110 may include a removable storage device that is readable and / or writable, such as a compact disc (CD), read-only digital versatile disc (such as DVD-ROM, dual-layer DVD-ROM), read-only Blu-ray disc, super density disc, flash memory card (such as SD card, min SD card, Micro-SD card, etc.), magnetic floppy disk, and so on. The computer-readable storage media does not include carrier waves and instantaneous electronic signals transmitted wirelessly or by wire.

[0222] An executable code is stored on the memory 1110, and when the executable code is processed by the processor 1120, it can cause the processor 1120 to execute the method for assisting a user to purchase a train ticket described above.

[0223] The method for assisting a user to purchase a train ticket according to the present invention has been described in detail above with reference to the accompanying drawings.

[0224] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of the relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entrances are provided for the user to select authorization or rejection.

[0225] In addition, the method according to the present invention may also be implemented as a computer program or computer program product, which includes computer program code instructions for performing the above-described steps defined in the above method of the present invention.

[0226] Alternatively, the present invention can also be implemented as a non-transitory machine-readable storage medium (or computer-readable storage medium, or machine-readable storage medium) having executable code (or computer program, or computer instruction code) stored thereon, which when executed by a processor of an electronic device (or computing device, server, etc.), causes the processor to perform the various steps of the above-described method according to the present invention.

[0227] Those skilled in the art will also understand that the various exemplary logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both.

[0228] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, segment, or portion of code that contains one or more executable instructions for implementing the specified logical function. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur in a different order than noted in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or operations, or by a combination of dedicated hardware and computer instructions.

[0229] The various embodiments of the present invention have been described above. The above description is exemplary and not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The choice of terms used herein is intended to best explain the principles of the embodiments, the practical application, or the improvement of technologies in the market, or to enable other ordinary skilled persons in the art to understand the embodiments disclosed herein.

Claims

1. A method for assisting a user in purchasing a train ticket, comprising: Providing a periodic ticketing configuration page to the user, the periodic ticketing configuration page is used to configure a periodic ticketing plan, the periodic ticketing plan includes a periodic travel time and a departure place and a destination of the periodic travel; In response to the user's operation on the periodic ticket booking configuration page, the periodic ticket booking function is enabled; as well as Train tickets are automatically purchased according to the periodic booking scheme.

2. The method according to claim 1, further comprising: Based on the user's historical ticket purchase order data, determine whether the user may have a need for periodic travel between fixed stations; When it is determined that the user may have a need for periodic travel between fixed stations, the user is asked whether he has a need for periodic travel between fixed stations. Wherein, when the user confirms that there is a need for periodic travel between fixed sites, the step of providing the user with a periodic ticket booking configuration page is performed.

3. The method according to claim 2, further comprising: Determine the user's historical periodic travel information between fixed sites according to the multiple ticket purchase order data between fixed sites in the user's historical ticket purchase order data, wherein the historical periodic travel information between fixed sites includes the departure place and destination of the historical periodic travel between fixed sites, and the periodic travel time; According to the historical periodic travel information between fixed sites, the departure place and destination of the periodic travel, and the periodic travel time are automatically configured in the periodic ticketing configuration page; receiving a user's modification of a departure point and / or destination of a periodic trip, and / or receiving a user's modification of a periodic trip time, Wherein, the periodic ticketing plan also includes the expected travel train number, and the historical periodic travel information between fixed stations also includes the historical travel train number. The method also includes: providing at least one travel train number option in the periodic ticketing configuration page, and the travel train number option includes a predicted travel train number that the user may expect, and receiving the user's selection and / or adjustment of the expected travel train number.

4. The method according to claim 3, further comprising: Providing a periodic ticketing management page entrance on a train ticket related page, and in response to a user clicking on the management page entrance, providing the periodic ticketing configuration page if the periodic ticketing function is not enabled, and providing a periodic ticketing management page if the periodic ticketing function is enabled, and providing the periodic ticketing plan and the train ticket booking status corresponding to the most recent future travel itinerary on the periodic ticketing management page; and / or In the case where the periodic ticket booking function has been turned on, providing status information indicating that the periodic ticket booking function has been turned on in association with the periodic ticket booking management page entry provided on the train ticket related page; and / or In response to the first activation of the periodic ticket booking function, a floating window is provided in association with a periodic ticket booking management page entry provided on a train ticket related page to prompt the user with a location and / or access path and / or function usage instructions of the periodic ticket booking management page entry; and / or Providing a train number setting page entrance on the periodic ticketing configuration page and / or the periodic ticketing management page, and in response to a user clicking on the train number setting page entrance, providing a train number setting page, providing a plurality of travel train number options for the user to select in the train number setting page, the number of travel train number options provided in the train number setting page being greater than the number of travel train number options provided in the periodic ticketing configuration page; and / or When the periodic ticket booking function is enabled, providing at least part of the periodic ticket booking plan and the ticket booking status of the next most recent trip on the train ticket related page; and / or In response to a successful ticket purchase, providing the user with a successful ticket issuance reminder and / or a next trip ticket booking reminder; and / or Providing an order list page entrance on the periodic ticket booking management page, and in response to a user clicking on the order list page entrance, providing an order list page, wherein the order list page provides untraveled itinerary orders and traveled itinerary orders of the ordered train tickets; and / or On the periodic ticketing configuration page, when the user has not yet selected a desired travel train, the on button for requesting to enable the periodic ticketing function is set to be unclickable, and in response to the user selecting a desired travel train, the on button for requesting to enable the periodic ticketing function is switched to be clickable; and / or When the periodic ticketing function is turned on, a function closing button is provided in the periodic ticketing management page. In response to the user clicking the function closing button, an interface for receiving the user's instruction to temporarily and / or permanently close the periodic ticketing function is provided, and the function closing button cannot be clicked during the ticket purchasing process before the operation is performed to complete the payment and issue the ticket.

5. The method according to claim 3, further comprising: receiving a user's selection of a preferred train from among a plurality of desired trains and / or a priority setting for the plurality of desired trains; If the preferred train or a train with a higher priority has insufficient remaining tickets and cannot be issued, the system automatically switches to purchasing an alternative train or a train with a lower priority among the multiple desired travel trains other than the preferred train, and prompts the user that the alternative train or the train with a lower priority has been booked.

6. The method according to claim 5, wherein: Providing a preferred train selection control or a train priority setting control in the train setting page to receive a user's selection of a preferred train from a plurality of desired travel trains and / or a priority setting for the plurality of desired travel trains, wherein the train setting page provides a plurality of travel train options for the user to select, and the number of travel train options provided in the train setting page is greater than the number of travel train options provided in the periodic ticketing configuration page; and / or No preferred train selection control or train priority setting control is provided on the periodic ticketing configuration page; and / or If the user selects multiple trains as preferred trains, purchasing train tickets for any of the multiple preferred trains with the same priority; and / or The periodic trip includes an outbound trip and a return trip, the departure places and destinations of the outbound trip and the return trip are opposite to each other, and the user's configuration of the travel time and the expected travel number of the outbound trip and the return trip is received on the periodic ticketing configuration page.

7. The method according to claim 6, further comprising: If the remaining tickets for the train you want to travel are limited, a reminder message of insufficient remaining tickets will be provided on the main page of the train ticket; In response to the user clicking on the insufficient remaining ticket reminder information, the train number setting page is provided, and the travel train number options that the user has not selected yet are provided in the train number setting page for the user to select.

8. The method according to claim 1, further comprising: Providing an activation button for requesting to activate the periodic ticketing function on the periodic ticketing configuration page; In response to the user clicking the start button, providing the user with an automatic payment setting page, Wherein, in response to the user completing the automatic payment setting, the step of enabling the periodic ticket booking function is executed.

9. The method according to claim 1, further comprising at least one of the following: Receiving instructions from a user to configure the length of a periodic trip; Receive instructions from users to temporarily and / or permanently disable the recurring ticketing function; receiving an instruction from a user to configure a date for starting to execute the periodic ticket booking function; Receive instructions from users to configure the number of days in advance for ticket purchase; Receive instructions from users to configure ticket booking plans for statutory holidays; The statutory holiday booking plan is configured according to a preset strategy, wherein the preset strategy includes at least one of the following: the periodic booking function is not executed on statutory holidays; the user is prompted on statutory holidays to select whether to execute the periodic booking function; when the starting day of a statutory holiday coincides with a Saturday, only the outbound ticket booking of the periodic booking function is executed; and / or when the ending day of a statutory holiday coincides with a Sunday, only the return ticket booking of the periodic booking function is executed.

10. The method according to claim 1, further comprising: Send a trip reminder to the user via mobile phone text messages and / or social platforms, and provide a link to cancel the trip in the trip reminder. In response to the user clicking on the link to cancel the trip, or sending a request to cancel the trip via text or voice: If you have not purchased a ticket for this trip, turn off automatic booking for this trip and provide a link to re-enable automatic booking for this trip; and / or If the train tickets related to this trip have already been purchased, a link to cancel the train ticket order related to this trip is provided. In response to the user clicking on the link to cancel the train ticket order related to this trip, the user enters the order page, on which refund controls and / or change controls for the purchased train tickets related to this trip are provided.

11. The method according to claim 10, wherein: Send a trip reminder to the user at least one of the following time points: The time when train tickets will be purchased automatically; When the cancellation fee will change; Before traveling; Before statutory holidays.

12. A computer program product, comprising executable codes, which, when executed by a processor of an electronic device, cause the processor to perform the method according to any one of claims 1 to 11.

Images