Civil aviation electronic ticket system and ticket management method, and storage medium and program product

Abstract

The present disclosure relates to the technical field of ticket management, and in particular, to a civil aviation electronic ticket system and ticket management method, and a storage medium and a program product. The system comprises: a ticket number acquisition interface, a quota consumption module and a ticket number consumption module, wherein the ticket number acquisition interface is configured to: upon receiving a ticket number application instruction sent by a sales office, update, by means of the quota consumption module and the ticket number consumption module, quota data and ticket number data of the sales office, and allocate a blank ticket number to the sales office. During a distribution process by the civil aviation electronic ticket system provided by the present disclosure, conventional ticket number segments are abandoned and replaced with quotas represented by numbers, and pre-allocation of ticket numbers is changed to on-demand allocation of ticket numbers, thereby simplifying the distribution process, and achieving number segment sharing; in addition, there is no need for level-by-level recovery of the ticket number segments, thereby facilitating the recovery of the number segments.

Description

Civil aviation electronic ticketing system, ticket management methods, storage media and program products Technical Field

[0001] This disclosure relates to the field of ticket management technology, and in particular to a civil aviation electronic ticket system, ticket management method, storage medium and program product. Background Technology

[0002] The tickets used in the civil aviation industry include air tickets and miscellaneous fare slips. Before being sold and used, these tickets are called blank tickets. The management of blank tickets is an important part of civil aviation ticket sales management. Before sales, blank tickets are issued to sales units. During sales, the tickets are filled out and issued to passengers; they serve as proof of consumption for passengers in subsequent service delivery processes.

[0003] The blank ticket management system comprises three main functions: organization management, ticket pool management, and ticket number management. An airline may have multiple branches, and each branch may have multiple offices. Only airline administrators, branch administrators, and office administrators have access to the ticket pool. If the user hierarchy is four-tiered, a sales unit wanting to sell electronic miscellaneous expense bills needs its upper-level office administrator to allocate usable ticket number ranges. The upper-level office administrator then applies for usable ticket number ranges from its upper-level branch administrator, who in turn applies to its upper-level airline administrator. When multiple sales units apply for sales, their respective offices need to know if their ticket pool's ticket number ranges meet the sales unit's needs. Branch administrators need to know the ranges and usage of ticket numbers already allocated by their upper-level administrators, as well as the ranges of ticket numbers they can distribute to lower-level administrators. Airline administrators need to know the usage of their own ticket ranges after they are added to the database, the number ranges already allocated to lower-level administrators, and the ranges of ticket numbers applied for by lower-level administrators. This is used to determine which ticket number ranges can be entered into the inventory, issued, and distributed to sales units. When multiple sales units find that they cannot sell their tickets, all their superiors must calculate, confirm, and allocate the number ranges; this one-to-many relationship means that sales units need to patiently wait for the allocation to be completed.

[0004] Currently, there are existing systems for electronic ticket number distribution, but the main problems with the existing systems and technical solutions are: blank tickets are pre-allocated based on number segments, which leads to the following two main problems: (1) The distribution process is cumbersome. During the distribution process, large number segments need to be split into multiple smaller number segments and distributed level by level, making the management process complicated. (2) Recycling is difficult: Recycling is also carried out according to number segments, which is very difficult. Business reasons for recycling include business changes or ticket number segments expiring and being rotated. Summary of the Invention

[0005] This disclosure aims to at least partially solve one of the technical problems in the aforementioned technologies, and to this end proposes a civil aviation electronic ticketing system, comprising:

[0006] The system includes a ticket number retrieval interface, a quota consumption module, and a ticket number consumption module; among them,

[0007] The ticket retrieval interface is configured as follows:

[0008] Upon receiving a ticket number application instruction from a sales unit, the quota consumption module and ticket number consumption module update the quota data and ticket number data of the sales unit and allocate blank ticket numbers to the sales unit.

[0009] Furthermore, the parameters corresponding to the quota data include: sales unit code, ticket type, allocated quota and consumed quota; the parameters corresponding to the ticket number data include: starting ticket number, capacity, remaining quantity and ticket type; the ticket type is divided into domestic tickets and international tickets.

[0010] Furthermore, the quota data is stored in the quota database, and the ticket number data is stored in the ticket number database.

[0011] Furthermore, the system also includes a quota management module, configured to process quota data stored in the quota database in response to user quota management commands.

[0012] Furthermore, the ticket number consumption module assigns ticket numbers to the sales module, and the method executed includes:

[0013] Search the ticket number database for blank ticket number segments;

[0014] Based on the start and end ticket numbers of the blank ticket number segment, determine whether the blank ticket number segment meets the ticket number quantity requirements of the sales module. If not, repeat the above method. If yes, allocate the blank ticket number segment to the sales module.

[0015] Record the allocation results of the blank ticket number segment.

[0016] Furthermore, the system also includes a ticket number management module, configured to process ticket number data stored in the ticket number database in response to user ticket number management commands.

[0017] Furthermore, the ticket number management module is also configured to reclaim allocated ticket number segments, and the method of execution includes: marking the target ticket number segment to be reclaimed as an unavailable ticket number segment.

[0018] This disclosure also proposes a civil aviation electronic ticket management method based on the aforementioned civil aviation electronic ticket system, including:

[0019] Using the ticket retrieval interface, execute the following method:

[0020] Upon receiving a ticket number application instruction from a sales unit, the quota consumption module and ticket number consumption module update the quota data and ticket number data of the sales unit and allocate blank ticket numbers to the sales unit.

[0021] This disclosure also proposes a computer-readable storage medium storing a computer program or instructions, which, when executed by a processor, are at least used to implement the above-described civil aviation electronic ticket management method.

[0022] This disclosure also proposes a computer program product stored in a computer-readable storage medium, which, when executed by a processor, is used to at least implement the above-described civil aviation electronic ticket management method.

[0023] Compared with the prior art, the beneficial effects of this disclosure are:

[0024] (1) The civil aviation electronic ticketing system disclosed herein abandons the traditional ticket number segments in the distribution process and instead uses quotas represented by numbers. Pre-allocation of ticket numbers has been changed to on-demand allocation. The entire distribution process does not involve the splitting of number segments. Obtaining pre-allocated number segments from each sales unit has been changed to obtaining quota numbers; the actual allocation of ticket numbers is delayed until ticket numbers are retrieved at the time of sale; within the ticket number retrieval process, quota consumption and ticket number consumption occur.

[0025] (2) The civil aviation electronic ticketing system disclosed herein has changed from pre-allocated ticket numbers to on-demand ticket number allocation, and different sales units share all number segments, overcoming the defect that the existing pre-allocated ticket number management model cannot share ticket numbers.

[0026] (3) The civil aviation electronic ticketing system disclosed herein can directly mark the corresponding number segment as reclaimed in the ticket number database when reclaiming number segments. It does not require reclaiming previously allocated ticket number segments from the sales unit level by level, which simplifies the operation.

[0027] Other features and advantages of this disclosure will be set forth in the following description, and will be apparent in part from the description, or may be learned by practicing the disclosure. The objects and other advantages of this disclosure may be realized and obtained by means of the structures particularly pointed out in the written description and the accompanying drawings. The technical solutions of this disclosure will be further described below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0028] The accompanying drawings are provided to further illustrate the present disclosure and form part of the specification. They are used together with the embodiments of the present disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings:

[0029] Figure 1 is a schematic diagram of the civil aviation electronic ticketing system given in the embodiment;

[0030] Figure 2 is a schematic diagram of the electronic device given in the embodiment;

[0031] Figure 3 is a schematic diagram of a computer-readable storage medium provided in the embodiment. Detailed Implementation

[0032] The present disclosure will be described below with reference to the accompanying drawings. The preferred embodiments described herein are for illustration and explanation only and are not intended to limit the present disclosure.

[0033] This disclosure proposes a civil aviation electronic ticketing system, including:

[0034] The system includes a ticket number retrieval interface, a quota consumption module, and a ticket number consumption module; among them,

[0035] The ticket retrieval interface is configured as follows:

[0036] Upon receiving a ticket number application instruction from a sales unit, the quota consumption module and ticket number consumption module update the quota data and ticket number data of the sales unit and allocate blank ticket numbers to the sales unit.

[0037] Furthermore, the quota data, and the corresponding parameters, include: sales unit code, ticket type, allocated quota and consumed quota; the ticket number data, and the corresponding parameters include: starting ticket number, capacity, remaining quantity and ticket type; ticket types are divided into domestic tickets and international tickets.

[0038] Furthermore, the quota data is stored in the quota database, and the ticket number data is stored in the ticket number database.

[0039] According to some embodiments of this disclosure, the sales unit code refers to the unique identifier of the sales unit, and blank tickets need to be distinguished between international and domestic, that is, the ticket types are divided into domestic tickets and international tickets. The allocated quota refers to the total cumulative quota of tickets allocated to the sales unit, and the consumed quota refers to the total cumulative quota of tickets consumed by the sales unit.

[0040] According to other embodiments of this disclosure, the quota data table is shown in Table 1:

[0041] Table 1

[0042] For sales unit codes, for example, PEK001 represents the ticket management agency in the North China region, PEK111 represents a sales unit under the management of PEK001, and PEK112 represents another sales unit under the management of PEK001.

[0043] Taking PEK001 as an example, initially, the administrator increased the quota for PEK001 in the North China region by 3000 domestic tickets. The quota data table is shown in Table 2.

[0044] Table 2

[0045] According to some other embodiments of this disclosure, the ticket number data table includes: a blank number segment data table and a ticket number actual destination table, as shown in Table 3:

[0046] Table 3

[0047] For example, an airline releases blank tickets: domestic tickets, starting with ticket number 4320000001, 50,000 tickets; international tickets, starting with ticket number 4340000001, 10,000 tickets. This yields the blank ticket number data table shown in Table 4.

[0048] The actual destination of the tickets is shown in Table 5:

[0049] Table 5

[0050] According to some embodiments of this disclosure, the civil aviation electronic ticketing system includes: several sales modules (sales systems of sales units) and a ticketing module. The ticketing module includes: a ticket number consumption module, a ticket number database, a ticket number retrieval interface, a quota consumption module, and a quota database. The sales system realizes quota consumption by calling the ticket number retrieval interface. The quota consumption module is used to process corresponding instructions, calculate the quota data corresponding to the sales system, and update the quota database. The ticket number data module is used to process corresponding instructions, calculate the ticket number data corresponding to the sales system, and update the ticket number database.

[0051] Furthermore, the system also includes a quota management module, configured to process quota data stored in the quota database in response to user quota management commands.

[0052] According to some embodiments of this disclosure, the ticket module also includes a quota management module, which is used to receive quota management instructions sent by the administrator, process the corresponding quota data according to the quota management instructions, and update the quota database.

[0053] According to other embodiments of this disclosure, quota management includes:

[0054] Increased amount and decreased amount. The steps for increasing the amount are as follows:

[0055] S101. According to the amount data parameter values (such as the sales unit code and the type of ticket), check whether there is corresponding amount data in the amount data table (stored in the amount database). If so, go to S102 and update the found amount data;

[0056] S102. Let quota_new = quota + quota_add, where quota_new represents the new amount, quota_add represents the increased amount of the amount, and quota represents the allocated amount;

[0057] S103. Update the allocated amount field of the amount record to quota_new;

[0058] S104. Judge whether the amount data is updated successfully and output the judgment result;

[0059] S105. Update the amount record for this sales unit. The amount record <sales unit code, type, allocated amount, consumed amount> = <office, type, quota_add, 0>;

[0060] S106. Judge whether the amount record is updated successfully and output the judgment result.

[0061] The steps for decreasing the amount are as follows:

[0062] S201. According to the amount data parameter values, check whether there is corresponding amount data in the amount data table. If so, go to S202, otherwise report an error;

[0063] S202. Judge whether quota - consumed < quota_remove holds. If so, report an error indicating that the current remaining amount of the sales unit is not enough for this amount reduction. Otherwise, calculate the new amount quota_new = quota - quota_remove; Here, consumed represents the consumed amount, and quota_remove represents the amount to be reduced;

[0064] S203. Update the allocated amount field of the amount record to quota_new;

[0065] S204. Judge whether the amount data is updated successfully and output the judgment result.

[0066] According to some embodiments of this disclosure, PEK001 in the North China region (current allocated quota: domestic tickets, 3000 tickets) increases its quota by 500 domestic tickets to its subordinate sales unit PEK113 (current allocated quota: domestic tickets, 0 tickets). This involves the consumption of quota for PEK001 and the increase of quota for PEK113. The corresponding quota data table is recorded as shown in Table 6:

[0067] Table 6

[0068] According to some embodiments of this disclosure, the sales system applies to the ticket module for a specified number of ticket numbers by calling the ticket number retrieval interface. At this time, the ticket number consumption module allocates ticket numbers to the corresponding sales module according to the received ticket number application instruction and updates the ticket number database to record the ticket numbers actually allocated by the sales system.

[0069] According to other embodiments of this disclosure, the process for credit limit consumption is as follows:

[0070] S301. Based on the input credit limit data parameter value, check if the corresponding credit limit data exists in the credit limit data table. If it does, proceed to S302; otherwise, report an error.

[0071] S302. Determine if remain ≥ want is true. If not, report an error indicating that the credit limit consumption failed (the remaining credit limit for the current sales unit is less than the amount consumed this time); if yes, calculate the new value of the consumed credit limit: consumed_new = consumed + want; where want represents the amount consumed this time, remain = quota - consumed, quota represents the allocated credit limit, consumed represents the consumed credit limit, and consumed_new represents the new value of the consumed credit limit.

[0072] S303. Update the credit limit record for this sales unit, that is, set the consumption credit limit for this sales unit in the credit limit data table to consumed_new;

[0073] S304. Determine whether the quota data has been updated successfully and output the result.

[0074] Furthermore, the ticket consumption module assigns ticket numbers to the sales module, and the methods executed include:

[0075] Search the ticket number database for blank ticket number segments;

[0076] Based on the start and end ticket numbers of the blank ticket number segment, determine whether the blank ticket number segment meets the ticket number requirements of the sales module. If not, repeat the above method; if yes, allocate the blank ticket number segment to the sales module.

[0077] Record the allocation results for blank ticket number segments.

[0078] According to some embodiments of the present disclosure, the process of ticket number consumption (ticket number allocation) is as follows:

[0079] S401. Read the blank number segment table according to the input quota data parameter value (such as ticket type), and locate a certain blank number segment;

[0080] S402. Determine whether the capacity of the located blank number segment meets the requirements (the capacity of the blank number segment is greater than the ticket number demand). If so, enter S403; otherwise, return to S401 until the capacity of the blank number segment meets the requirements. If it still does not meet the requirements after traversing the blank number segment table, an error is reported;

[0081] S403. Allocate some ticket numbers in this blank number segment to the corresponding sales unit, and update the actual destination table of ticket numbers and the remaining quantity of this blank number segment at the same time.

[0082] Furthermore, the system further includes: a ticket number management module, configured to: respond to a user's ticket number management instruction and process the ticket number data stored in the ticket number database.

[0083] According to some embodiments of the present disclosure, as shown in FIG. 1, the civil aviation electronic ticket system provided by the present disclosure includes: at least one sales system (the above-mentioned sales module), a ticket number acquisition interface, a quota consumption module, a quota database, a quota management module, a ticket number consumption module, a ticket number database, and a ticket number management module. The user can process the ticket number data stored in the ticket number database through the ticket number management module. For the functions of other modules, please refer to the above.

[0084] According to some embodiments of the present disclosure, ticket number management includes putting in number segments, and the steps are as follows:

[0085] S501. Construct a blank number segment record, where ticket type = type, from = grant_from, cap = grant_count, free = grant_count, where grant_from represents the starting ticket number to be put in, and grant_count represents the quantity to be put in;

[0086] S502. Write this blank number segment record into the blank number segment table;

[0087] S503. Judge whether the writing is successful and output the writing result.

[0088] According to some other embodiments of the present disclosure, PEK113 is sold, 3 tickets are sold, and when preparing to issue tickets, the ticket number acquisition interface is called. The ticket number acquisition interface internally calls quota consumption and ticket number consumption in sequence, and finally returns <4320000>001, 3>.

[0089] The data table corresponding to the above process is as follows:

[0090] Table 7

[0091] Table 7 is a credit limit data table, reflecting the credit limit consumption situation.

[0092] Table 8

[0093] Table 8 is a data table of ticket numbers, reflecting the changes in ticket numbers.

[0094] Table 9

[0095] Table 9 shows the actual destination of the tickets, reflecting the allocation of the tickets.

[0096] Furthermore, the ticket number management module is also configured to reclaim allocated ticket number segments, and the method to be executed includes: marking the target ticket number segment to be reclaimed as an unavailable ticket number segment.

[0097] According to some embodiments of this disclosure, ticket number management includes recycling number segments, marking the number segments to be recycled as blank ticket number segments, and counting the number of recycled ticket numbers. The steps for counting the number of recycled ticket numbers are as follows:

[0098] S601. Let `revoked = 0`, traverse the blank number segment table, and for each blank number segment record, calculate its intersection with the number segment to be reclaimed, i.e.<stock_from+cap-free,stock_from+cap> and<revoke_from,revoke_to> intersection<join_from,join_to> ;stock_from represents the starting ticket number corresponding to the target blank number segment record, stock_to represents the ending ticket number corresponding to the target blank number segment record, cap represents the capacity corresponding to the target blank number segment record, and free represents the remaining quantity corresponding to the target blank number segment record; revoke_from represents the starting ticket number of the number segment to be reclaimed, and revoke_to represents the ending ticket number of the number segment to be reclaimed; join_from represents the starting ticket number of the intersection, and join_to represents the ending ticket number of the intersection.

[0099] S602. Calculate the quantity recovered this time: num = join_to - join_from + 1;

[0100] S603. Set the remaining capacity of the target blank number segment record to 0, revoked = revoked + num, and return to S601 until the blank number segment table is traversed. Output the revoked at the end of the traversal, which is the number of successfully revoked.

[0101] According to other embodiments of this disclosure, after a period of sales, YY Airlines decided to discontinue the domestic number segments: 4320000001-4320050000; and to activate the new domestic number segments 4321000001-4321999999, initially releasing 20,000 tickets. The operation method is as follows: first release the new number segments, then withdraw the old number segments. The corresponding changes in the ticket number data table are as follows:

[0102] Table 10

[0103] This operation allows you to deactivate the old number segment and activate the new number segment.

[0104] Based on the same technical concept, this disclosure also proposes a civil aviation electronic ticket management method based on the above-mentioned civil aviation electronic ticket system, including:

[0105] Using the ticket retrieval interface, execute the following method:

[0106] After receiving the ticket number application instruction from the sales unit, the quota consumption module and ticket number consumption module update the quota data and ticket number data of the sales unit and assign blank ticket numbers to the sales unit.

[0107] As shown in Figure 2, this disclosure provides an electronic device, which includes a memory and a processor. The memory stores computer programs or instructions. When the computer programs or instructions are executed by the processor, they are used to implement at least the above-mentioned civil aviation electronic ticket management method.

[0108] As shown in Figure 3, this disclosure also proposes a computer-readable storage medium storing a computer program or instructions, which, when executed by a processor, are used to implement at least the above-described civil aviation electronic ticket management method.

[0109] This disclosure also proposes a computer program product stored in a computer-readable storage medium, which, when executed by a processor, is used to implement at least the above-described civil aviation electronic ticket management method.

[0110] The electronic ticketing system and ticket management method disclosed herein have the following advantages:

[0111] (1) Simplified distribution process: In the distribution process, the traditional ticket number range was abandoned and replaced with a quota represented by numbers. Ticket numbers were changed from pre-allocated to on-demand allocation. The entire distribution process does not involve the splitting of number ranges. Obtaining a pre-allocated number range from each sales unit is changed to obtaining a quota number; the actual allocation of ticket numbers is delayed until the ticket numbers are obtained at the time of sale; within the process of obtaining ticket numbers, quota consumption and ticket number consumption are carried out.

[0112] (2) Facilitates the sharing of ticket numbers: All number segments can be shared between different sales units; overcoming the shortcomings of the existing pre-allocated ticket number management model that cannot share ticket numbers.

[0113] (3) Convenient recycling: When recycling number segments, the corresponding number segments can be marked as recycled directly in the ticket number database, without having to recycle the ticket number segments allocated from the sales unit level by level.

[0114] It is obvious that those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.

Claims

1. A civil aviation electronic ticket management system, characterized in that, include: The system includes a ticket number retrieval interface, a quota consumption module, and a ticket number consumption module; among them, The ticket retrieval interface is configured as follows: Upon receiving a ticket number application instruction from a sales unit, the quota consumption module and ticket number consumption module update the quota data and ticket number data of the sales unit and allocate blank ticket numbers to the sales unit.

2. The system of claim 1, wherein, The quota data includes the following parameters: sales unit code, ticket type, allocated quota and consumed quota; the ticket number data includes the following parameters: starting ticket number, capacity, remaining quantity and ticket type; the ticket type is divided into domestic tickets and international tickets.

3. The system of claim 1, wherein, The quota data is stored in the quota database, and the ticket number data is stored in the ticket number database.

4. The system of claim 3, wherein, The system further includes a quota management module, configured to process quota data stored in the quota database in response to user quota management commands.

5. The system of claim 3, wherein, The ticket number consumption module assigns ticket numbers to the sales module, and the methods executed include: Search the ticket number database for blank ticket number segments; Based on the start and end ticket numbers of the blank ticket number segment, determine whether the blank ticket number segment meets the ticket number quantity requirements of the sales module. If not, repeat the above method. If yes, allocate the blank ticket number segment to the sales module. Record the allocation results of the blank ticket number segment.

6. The system of claim 3, wherein, The system further includes a ticket number management module, configured to process ticket number data stored in the ticket number database in response to user ticket number management commands.

7. The system of any of claims 1-6, wherein, The ticket number management module is also configured to reclaim allocated ticket number segments, and the method of execution includes: marking the target ticket number segment to be reclaimed as an unavailable ticket number segment.

8. A method for managing the electronic ticket of civil aviation according to any one of claims 1 to 7, characterized in that, include: Using the ticket retrieval interface, execute the following method: Upon receiving a ticket number application instruction from a sales unit, the quota consumption module and ticket number consumption module update the quota data and ticket number data of the sales unit and allocate blank ticket numbers to the sales unit.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions, which, when executed by a processor, are at least used to implement the method of claim 8.

10. A computer program product stored in a computer readable storage medium, characterized in that, When the computer program product is executed by a processor, it is used to implement at least the method of claim 8.

Images