CN110751519B - Automatic change method and device for team passenger tickets - Google Patents
Automatic change method and device for team passenger tickets Download PDFInfo
- Publication number
- CN110751519B CN110751519B CN201910999130.3A CN201910999130A CN110751519B CN 110751519 B CN110751519 B CN 110751519B CN 201910999130 A CN201910999130 A CN 201910999130A CN 110751519 B CN110751519 B CN 110751519B
- Authority
- CN
- China
- Prior art keywords
- ticket
- change
- information
- team
- original
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000012508 change request Methods 0.000 claims abstract description 87
- 238000012790 confirmation Methods 0.000 claims abstract description 50
- 238000012795 verification Methods 0.000 claims description 3
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000004364 calculation method Methods 0.000 description 2
- 238000004088 simulation Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/40—Business processes related to the transportation industry
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S10/00—Systems supporting electrical power generation, transmission or distribution
- Y04S10/50—Systems or methods supporting the power network operation or management, involving a certain degree of interaction with the load-side end user applications
Landscapes
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Primary Health Care (AREA)
- Tourism & Hospitality (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for automatically changing a team ticket, which can obtain a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises an identifier of an original ticket of the user; obtaining original ticket information and new ticket information according to the identifier of the original ticket; obtaining a restriction condition corresponding to the first team ticket; determining whether the change request of the passenger tickets of the team meets all the limiting conditions; when the change request of the team passenger ticket meets all the limiting conditions, obtaining a change difference; sending a change confirmation message to the user side equipment, wherein the change confirmation message carries a change difference; and after the confirmation feedback of the user on the change confirmation message is obtained, changing the original ticket information according to the new ticket information to obtain a change result. The invention adopts the technical means of automatically changing the passenger tickets of the team, and improves the efficiency of changing the passenger tickets of the team.
Description
Technical Field
The invention relates to the field of ticket service, in particular to an automatic change method and device for a team passenger ticket.
Background
With the development of the transportation industry of each country, the ticketing service corresponding to the transportation industry is continuously updated and optimized, wherein the passenger ticket change is an important service in the ticketing service.
At present, the change of a single ticket can be automatically changed, the change of a group ticket is still changed in a manual mode, and the current operation flow of manually changing the group ticket comprises the following steps: manually checking original ticket information of a user needing to be changed in the group tickets and limiting conditions corresponding to the original ticket information one by one, manually comparing the new ticket information with the limiting conditions one by one, manually judging whether the new ticket information meets the limiting conditions, if the judgment result is allowable, calculating the difference of the ticket amounts before and after the change, reminding the user to charge and refund the difference, and manually changing the original ticket information according to the new ticket information after the charge and refund are finished until the change is finished. Therefore, the efficiency of manual change operation on the group tickets is low at present.
In order to solve the problem of low efficiency of manual modification of group tickets, a method for improving the efficiency of modification of group tickets is urgently needed.
Disclosure of Invention
In view of the above problems, the present invention provides a method and an apparatus for automatically changing a team ticket, which overcomes or at least partially solves the above problems, and the technical solution is as follows:
a method of automatic change of a team ticket, the method comprising:
obtaining a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises an identifier of an original ticket of the user;
obtaining original ticket information and new ticket information according to the identifier of the original ticket;
obtaining a restriction condition corresponding to the first team ticket;
determining whether the team ticket change request satisfies each of the restrictions;
when the change request of the team passenger ticket meets each limiting condition, obtaining a change difference;
sending a change confirmation message to user side equipment, wherein the change confirmation message carries the change difference;
and after the confirmation feedback of the user to the change confirmation message is obtained, changing the original ticket information according to the new ticket information to obtain a change result.
Optionally, the obtaining of the original ticket information and the new ticket information according to the identifier of the original ticket includes:
obtaining original ticket information corresponding to the identifier of the original ticket in a ticket sale database according to the identifier of the original ticket;
and obtaining new passenger ticket information corresponding to the identifier of the original passenger ticket in the passenger booking record according to the identifier of the original passenger ticket.
Optionally, the obtaining a restriction condition corresponding to the first team ticket includes:
and simulating and recalculating the original ticket price according to the original ticket information to obtain a limiting condition corresponding to the original ticket price.
Optionally, the limiting conditions include: a first change condition of the number of persons and/or a second change condition of the number of persons,
the first change number condition is as follows: the number of the users requesting to change is the same as the number of the users included in the first team ticket, or the number of the users not requesting to change is not lower than the minimum group number of people, wherein the number of the users requesting to change is the number of the users corresponding to each piece of ticket change information carried by the team ticket change request, and the number of the users not requesting to change is: the number of users included in the first team ticket minus the number of users requesting a change in the number of users;
the second change number condition is as follows: requesting to change the number of the users to be the same as the number of the users included in the first team passenger ticket; or the number of unchanged users and the number of users requesting to be changed are not lower than the minimum group number.
Optionally, when the change request of the team tickets meets each of the limiting conditions, obtaining a change allowance includes:
and when the change request of the team passenger tickets meets all the limiting conditions, calculating the sum of the new passenger tickets and the difference between the new passenger tickets and the old passenger tickets according to the information of the new passenger tickets.
An automatic change device for a team ticket, comprising: a change request obtaining unit, a ticket information obtaining unit, a limit condition obtaining unit, a change request verifying unit, a change balance obtaining unit, a ticket information changing unit, and a change result obtaining unit,
the change request obtaining unit is used for obtaining a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises an identifier of an original ticket of the user;
the ticket information obtaining unit is used for obtaining original ticket information and new ticket information according to the identifier of the original ticket;
the limiting condition obtaining unit is used for obtaining a limiting condition corresponding to the first team passenger ticket;
the change request verification unit is used for determining whether the team ticket change request meets all the limiting conditions;
the change balance obtaining unit is used for obtaining a change balance when the change request of the passenger tickets of the team meets each limiting condition;
the passenger ticket information changing unit is used for sending a change confirmation message to the user side equipment, wherein the change confirmation message carries the change balance;
and the change result obtaining unit is used for changing the original ticket information according to the new ticket information after obtaining the confirmation feedback of the user on the change confirmation message, and obtaining a change result.
Optionally, the ticket information obtaining unit is specifically configured to obtain, in a ticket sales database, original ticket information corresponding to the identifier of the original ticket according to the identifier of the original ticket;
the ticket information obtaining unit is specifically configured to obtain new ticket information corresponding to the identifier of the original ticket in a passenger booking record according to the identifier of the original ticket.
Optionally, the restriction condition obtaining unit is specifically configured to perform simulated recalculation on the original ticket price according to the original ticket information, and obtain a restriction condition corresponding to the original ticket price.
Optionally, the limiting conditions include: a first change condition of the number of persons and/or a second change condition of the number of persons,
the first change number condition is as follows: the number of the users requesting to change is the same as the number of the users included in the first team ticket, or the number of the users not requesting to change is not lower than the minimum group number of people, wherein the number of the users requesting to change is the number of the users corresponding to each piece of ticket change information carried by the team ticket change request, and the number of the users not requesting to change is: the number of users included in the first team ticket minus the number of users requesting a change in the number of users;
the second change number condition is as follows: requesting to change the number of the users to be the same as the number of the users included in the first team passenger ticket; or the number of the unchanged users and the number of the users requesting to change are not lower than the minimum group number.
Optionally, the change balance obtaining unit is specifically configured to calculate the amount of the new passenger ticket and the balance between the new passenger ticket and the old passenger ticket according to the new passenger ticket information when the change request of the team passenger ticket satisfies the limiting conditions.
By means of the technical scheme, the method and the device for automatically changing the team tickets can obtain a team ticket change request for changing the first team tickets, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises the original ticket identification of the users; obtaining original ticket information and new ticket information according to the identifier of the original ticket; obtaining a restriction condition corresponding to the first team ticket; determining whether the team ticket change request satisfies each of the restrictions; when the change request of the team passenger ticket meets each limiting condition, obtaining a change difference; sending a change confirmation message to user side equipment, wherein the change confirmation message carries the change difference; and after the confirmation feedback of the user to the change confirmation message is obtained, changing the original ticket information according to the new ticket information to obtain a change result. The invention adopts the technical means of verifying whether the change request of the team ticket meets the limiting condition in an automatic mode, overcomes the technical problem of low efficiency of manual change of the team ticket, and further improves the efficiency of the change of the team ticket.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a flow chart of a method for automatically changing a team ticket according to an embodiment of the present invention;
FIG. 2 is a flow diagram illustrating another method for automatic change of a team ticket according to an embodiment of the invention;
FIG. 3 is a flow diagram illustrating another method for automatic change of a team ticket according to an embodiment of the invention;
FIG. 4 is a flow diagram illustrating another method for automatic change of team tickets according to an embodiment of the invention;
fig. 5 is a schematic structural diagram of an automatic change device for a team ticket according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As shown in fig. 1, an automatic change method for a team ticket provided in an embodiment of the present invention may include:
s100, obtaining a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises an identifier of an original ticket of the user.
Specifically, the first team ticket may be a team ticket purchased by a team comprising at least two users. It will be appreciated that prior to making the change to the first team ticket, the destination, travel date, flight number, bin level, etc. information for each user in the first team ticket is consistent. The embodiment may obtain a team ticket change request sent by a first device to change a first team ticket, where the first device may be a device for each airline to process tickets. A team ticket change request to change a first team ticket carries ticket change information for at least two users. It will be appreciated that making changes to the first team ticket may include a whole team change and a split team change. The whole group is changed into the first team ticket, and the group is removed and changed into the first team ticket. Because two people can form a group, the change request of the ticket of the team in the group splitting change carries the ticket change information of at least two users.
The ticket change information may include: change cabin space information, change travel date information, change flight information, and the like. In this embodiment, the ticket change information carried by the team ticket change request may be the same. For example, the change request of the team ticket carries the ticket change information of the user a and the user B, and the ticket change information of the user a is as follows: if the cabin space is changed to be a business cabin, the passenger ticket change information of the user B is also as follows: and changing the cabin position into a business cabin.
In this embodiment, the original ticket identification of the user may be the ticket number of the original ticket. It will be appreciated that the user's original ticket identification may also be other uniquely identifiable information in the original ticket.
S200, obtaining the original ticket information and the new ticket information according to the identification of the original ticket.
It can be understood that, in this embodiment, after the first team ticket is generated, the ticket information of all users in the first team ticket is stored in the database with the identifier of the original ticket as the uniquely identifiable information, so that the embodiment can obtain the original ticket information and the new ticket information corresponding to the identifier of the original ticket in the database storing the original ticket information and the new ticket information according to the identifier of the original ticket. The database may be communicatively coupled to the first device. The original ticket information may include information of an original destination, an original travel date, an original flight number, an original cabin level, and the like of the user, and the new ticket information may be ticket information obtained by modifying the original ticket information according to the ticket change information.
In particular, the database may be a ticket sales database. As shown in fig. 2, in another method for automatically changing a team ticket according to an embodiment of the present invention, step S200 may include:
s210, obtaining original passenger ticket information corresponding to the original passenger ticket identification in a passenger ticket sales database according to the original passenger ticket identification.
According to the embodiment, the original ticket information corresponding to the original ticket identification can be obtained in the ticket sale database according to the original ticket identification of the user included in the ticket change information carried by the team ticket change request.
S220, obtaining new passenger ticket information corresponding to the original passenger ticket identification in the passenger booking record according to the original passenger ticket identification.
According to the embodiment, new ticket information corresponding to the original ticket identification can be obtained in the passenger booking record according to the original ticket identification of the user included in the ticket change information carried by the team ticket change request.
The passenger reservation record includes information such as the user's passenger name, destination, travel date, flight number, class level, etc. It will be appreciated that for a team ticket, the passenger reservation record includes information such as the passenger's name, destination, travel date, flight number, class level, etc. for all users in the team ticket. Before the user needs to change the ticket, the information that the user needs to change in the passenger booking record may be updated, for example, after the slot in the passenger booking record is changed, the new ticket information after the slot is changed is obtained in the passenger booking record according to the identifier of the original ticket in this embodiment. The passenger booking record may be stored in a preset storage medium, and in this embodiment, new ticket information corresponding to the identifier of the original ticket may be obtained by querying the storage medium according to the identifier of the original ticket.
And S300, obtaining the limiting conditions corresponding to the first team passenger ticket.
Optionally, as shown in fig. 3, in another method for automatically changing a team ticket according to an embodiment of the present invention, step S300 may include:
s310, simulating and recalculating the original ticket price according to the original ticket information, and obtaining the limiting conditions corresponding to the original ticket price.
The embodiment can specify the ticket date of the original ticket in the original ticket information and simulate the recalculation of the ticket price of the original ticket. Simulated recalculation of original ticket fare may also specify one or more of travel, flight, travel date, and slot including original ticket for simulated recalculation. The embodiment can obtain the limiting conditions corresponding to the original passenger ticket after the simulation recalculation.
Optionally, the limiting conditions include: the first condition of the number of persons to be changed and/or the second condition of the number of persons to be changed.
The first change number condition is as follows: the number of the users requesting to change is the same as the number of the users included in the first team ticket, or the number of the users not requesting to change is not lower than the minimum group number of people, wherein the number of the users requesting to change is the number of the users corresponding to each piece of ticket change information carried by the team ticket change request, and the number of the users not requesting to change is: the first team ticket includes the number of users minus the number of users requesting the change.
And when the number of the users requesting to change is the same as the number of the users included in the first team ticket, the first team ticket is explained to be changed in a whole group. When the whole group is changed, the passenger ticket change information of each user carried by the passenger ticket change request of the team is the same. For example, all users in the first team ticket change the travel date start time from 2019 on 4-month-15 to 2019 on 4-month-17.
And when the first change number condition is that the number of the unchanged users is not less than the minimum group number, the first team passenger ticket is explained to be changed by group removal. When the group is removed and changed, the passenger ticket change information carried by the passenger ticket change request of the team can be the same. For example, the change request of the team ticket carries the ticket change information of two users, and the new ticket information in the ticket change information of the two users changes the class of the slot from the economy class to the business class.
It should be noted that, in the embodiment of the present invention, after obtaining the number of users included in the first team ticket and the number of users requesting to change, the number of unchanged users determined by subtracting the number of users requesting to change from the number of users included in the first team ticket. For example, if the obtained first team ticket includes 8 users and the number of users requesting change is 7, the determined number of unchanged users is 1. The minimum group number of people in the embodiment of the invention can be set according to actual requirements. The minimum cluster population may be set to a fixed value.
The second change number condition is as follows: requesting to change the number of the users to be the same as the number of the users included in the first team passenger ticket; or the number of the unchanged users and the number of the users requesting to change are not lower than the minimum group number.
Wherein, when the second number of changed persons condition is: the condition that the number of the users required to be changed is equal to the number of the users included in the first team ticket and the first change number is as follows: the principle that the number of the users requesting to change is the same as the number of the users included in the first team ticket is the same, please refer to the above description, which is not described herein again.
And when the second change passenger number condition is that the number of the unchanged users and the number of the users requesting to change are not lower than the minimum group number, the first group of passenger tickets are explained to be changed by group splitting. The number of unchanged users and the number of users requesting to change are not less than the minimum group number. For example, when the minimum clustering population of the second change population condition is 3, the second change population condition is satisfied if the number of unchanged users is 4 and the number of requested users is 3, and the second change population condition is not satisfied if the number of unchanged users is 2 and the number of requested users is 3.
The limitation conditions in this embodiment may further include a modification range condition (category 31).
Specifically, the change range condition may be that the ticket change information carried by the team ticket change request is all located within the information change range corresponding to the first team ticket. Specifically, the ticket change information of each user is located within a changeable range in the changeable information type corresponding to the first team ticket. The changeable information type includes one or more of destination, travel date, flight number, class of space, etc., and the information type of changing the original ticket information according to the ticket change information needs to be within the changeable information type, for example, assuming that the changeable information type is date and space, if the information type of changing the original ticket information in the ticket change information is travel date and/or space, the ticket change information is located in the changeable information type corresponding to the first team ticket, and if the information type of changing the original ticket information in the ticket change information is destination, the ticket change information is not located in the changeable information type corresponding to the first team ticket.
It will be appreciated that although the ticket change information is located in the changeable information type corresponding to the first team ticket, the ticket change information still needs to be located within the changeable range in the changeable information type. For example, if the type of the changeable information is a travel date, and the ticket change information is such that the start date of the travel date in the original ticket information is changed from day 10 of 5 months to day 15 of 5 months, but no flight with the same flight number as that in the original ticket information exists on day 15 of 5 months, the ticket change information is not within the changeable range in the changeable information type corresponding to the first team ticket. Similarly, the type of the changeable information is a travel date, the ticket change information is that the starting date of the travel date in the original ticket information is changed from 5/10 to 5/15, but the seat of the flight with the same flight number as that in the original ticket information on 5/15 is sold out, and the ticket change information is not in the changeable range in the changeable information type corresponding to the first group of tickets. It is understood that the change range condition has a plurality of cases, and this embodiment does not exemplify the case where the ticket change information is not located in the changeable range in the changeable information type corresponding to the first team ticket.
S400, determining whether the team ticket change request meets each limiting condition.
S500, obtaining a change difference when the change request of the team passenger ticket meets each limiting condition.
Specifically, as shown in fig. 4, in another method for automatically changing a team ticket according to an embodiment of the present invention, step S500 may include:
s510, when the team ticket change request meets the limiting conditions, calculating the sum of the new ticket and the difference between the new ticket and the old ticket according to the new ticket information.
The embodiment can calculate the amount of the new ticket according to the destination, the travel date, the flight number, the class level and other information in the new ticket information. For example, the new ticket information is the ticket information for changing the economy class in the original ticket information into the business class according to the changed slot information in the ticket change information. And if the other prices are not changed, the price of the economy class is 1000 Yuan, and the price of the business class is 2000 Yuan, the difference between the old and the new passenger tickets is 1000 Yuan.
S600, sending a change confirmation message to user side equipment, wherein the change confirmation message carries the change allowance.
The embodiment can send a change confirmation message to the user side device after the calculation of the sum of the new ticket and the difference between the new ticket and the old ticket. The change allowance carried in the change confirmation message may include: new and old ticket balance, tax balance, commission, and total charge or total refund amount. The change confirmation message may further include: the destination, travel date, flight number, class level, etc. of the unchanged user and the new ticket information requesting to change the user in the first team's ticket.
S700, after the confirmation feedback of the user to the change confirmation message is obtained, the original ticket information is changed according to the new ticket information, and a change result is obtained.
The confirmation feedback may carry a message that the charge and return processing is completed, and after the confirmation feedback is received, the present embodiment may determine that the charge and return processing is completed by the user.
The embodiment may send the change result to the user side device for display.
The method for automatically changing the team tickets provided by the embodiment can obtain a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises an identifier of an original ticket of the user; obtaining original ticket information and new ticket information according to the identifier of the original ticket; obtaining a restriction condition corresponding to the first team ticket; determining whether the team ticket change request satisfies each of the restrictions; when the change request of the team passenger ticket meets each limiting condition, obtaining a change difference; sending a change confirmation message to user side equipment, wherein the change confirmation message carries the change difference; and after the confirmation feedback of the user on the change confirmation message is obtained, changing the original passenger ticket information according to the new passenger ticket information to obtain a change result. The technical means of verifying whether the change request of the team tickets meets the limiting conditions in an automatic mode is adopted, the technical problem that manual change of the team tickets is low in efficiency is solved, and then the efficiency of the change of the team tickets is improved.
Corresponding to the above method embodiment, this embodiment further provides an automatic change device for a team ticket, which has a structure as shown in fig. 5 and may include: a change request obtaining unit 100, a ticket information obtaining unit 200, a restriction condition obtaining unit 300, a change request verifying unit 400, a change balance obtaining unit 500, a ticket information changing unit 600, and a change result obtaining unit 700.
The change request obtaining unit 100 is configured to obtain a team ticket change request for changing a first team ticket, where the team ticket change request carries ticket change information of at least two users, and the ticket change information includes an identifier of an original ticket of the user.
Specifically, the first team ticket may be a team ticket purchased by a team comprising at least two users. It will be appreciated that prior to making the change to the first team ticket, the destination, travel date, flight number, bin level, etc. information for each user in the first team ticket is consistent. The embodiment may obtain a team ticket change request sent by a first device to change a first team ticket, where the first device may be a device for each airline to process tickets. The team ticket change request for changing the first team ticket carries ticket change information for at least two users. It will be appreciated that making changes to the first team ticket may include a whole team change and a split team change. The whole group is changed into the first team ticket, and the group is removed and changed into the first team ticket. Because the group can be formed by two persons, the change request of the ticket of the team in the group-splitting change carries the change information of the ticket of at least two users.
The ticket change information may include: change cabin space information, change travel date information, change flight information, and the like. In this embodiment, the ticket change information carried by the team ticket change request may be the same.
In this embodiment, the original ticket identifier of the user may be a ticket number of the original ticket. It will be appreciated that the user's original ticket identification may also be other uniquely identifiable information in the original ticket.
The ticket information obtaining unit 200 is configured to obtain the original ticket information and the new ticket information according to the identifier of the original ticket.
It can be understood that, in this embodiment, after the first team ticket is generated, the ticket information of all users in the first team ticket is stored in the database with the identifier of the original ticket as the uniquely identifiable information, so that the embodiment can obtain the original ticket information and the new ticket information corresponding to the identifier of the original ticket in the database storing the original ticket information and the new ticket information according to the identifier of the original ticket. The database may be communicatively coupled to the first device. The original ticket information may include information of an original destination, an original travel date, an original flight number, an original cabin level, and the like of the user, and the new ticket information may be ticket information obtained by modifying the original ticket information according to the ticket change information.
In particular, the database may be a ticket sales database. Optionally, the ticket information obtaining unit 200 is specifically configured to obtain, in a ticket sales database, original ticket information corresponding to the identifier of the original ticket according to the identifier of the original ticket.
According to the embodiment, the original ticket information corresponding to the original ticket identification can be obtained in the ticket sale database according to the original ticket identification of the user included in the ticket change information carried by the team ticket change request.
The ticket information obtaining unit 200 is specifically configured to obtain, in a passenger booking record, new ticket information corresponding to the identifier of the original ticket according to the identifier of the original ticket.
According to the embodiment, new ticket information corresponding to the original ticket identification can be obtained in the passenger booking record according to the original ticket identification of the user included in the ticket change information carried by the team ticket change request.
The passenger reservation record includes information such as the user's passenger name, destination, travel date, flight number, class level, etc. It will be appreciated that for a team ticket, the passenger reservation record includes information such as the passenger's name, destination, travel date, flight number, class level, etc. for all users in the team ticket. Before the user needs to change the ticket, the information that the user needs to change in the passenger booking record may be updated, for example, after the slot in the passenger booking record is changed, the new ticket information after the slot is changed is obtained in the passenger booking record according to the identifier of the original ticket in this embodiment. The passenger booking record can be stored in a preset storage medium, and the embodiment can inquire and obtain new passenger ticket information corresponding to the identifier of the original passenger ticket in the storage medium according to the identifier of the original passenger ticket.
The constraint condition obtaining unit 300 is configured to obtain a constraint condition corresponding to the first team ticket.
Optionally, the limitation condition obtaining unit 300 is specifically configured to perform simulated recalculation on the original ticket price according to the original ticket information, and obtain the limitation condition corresponding to the original ticket price.
The embodiment can specify the ticket date of the original ticket in the original ticket information and simulate the recalculation of the ticket price of the original ticket. Simulated recalculation of original ticket fare may also specify one or more of travel, flight, travel date, and slot including original ticket for simulated recalculation. The embodiment can obtain the limiting conditions corresponding to the original passenger ticket after the simulation recalculation.
Optionally, the limiting conditions include: the first condition of the number of persons to be changed and/or the second condition of the number of persons to be changed.
The first change number condition is as follows: the number of the users requesting to change is the same as the number of the users included in the first team ticket, or the number of the users not requesting to change is not lower than the minimum group number of people, wherein the number of the users requesting to change is the number of the users corresponding to each piece of ticket change information carried by the team ticket change request, and the number of the users not requesting to change is: the first team ticket includes the number of users minus the number of users requested to change.
The second change number condition is as follows: requesting to change the number of the users to be the same as the number of the users included in the first team passenger ticket; or the number of the unchanged users and the number of the users requesting to change are not lower than the minimum group number.
The limitation conditions in this embodiment may further include a modification range condition (category 31).
Specifically, the change range condition may be that the ticket change information carried by the team ticket change request is all located within the information change range corresponding to the first team ticket. Specifically, the ticket change information of each user is located within a changeable range in the changeable information type corresponding to the first team ticket. The changeable information type includes one or more of destination, travel date, flight number, class of space, etc., and the information type of changing the original ticket information according to the ticket change information needs to be within the changeable information type, for example, assuming that the changeable information type is date and space, if the information type of changing the original ticket information in the ticket change information is travel date and/or space, the ticket change information is located in the changeable information type corresponding to the first team ticket, and if the information type of changing the original ticket information in the ticket change information is destination, the ticket change information is not located in the changeable information type corresponding to the first team ticket.
It will be appreciated that although the ticket change information is located in the changeable information type corresponding to the first team ticket, the ticket change information still needs to be within the changeable range in the changeable information type. For example, if the type of the changeable information is a travel date, and the ticket change information is such that the start date of the travel date in the original ticket information is changed from day 10 of 5 months to day 15 of 5 months, but no flight with the same flight number as that in the original ticket information exists on day 15 of 5 months, the ticket change information is not within the changeable range in the changeable information type corresponding to the first team ticket. Similarly, the type of the changeable information is a travel date, the ticket change information is that the starting date of the travel date in the original ticket information is changed from 5/10 to 5/15, but the seat of the flight with the same flight number as that in the original ticket information on 5/15 is sold out, and the ticket change information is not in the changeable range in the changeable information type corresponding to the first group of tickets. It is understood that the change range condition has a plurality of cases, and this embodiment does not exemplify the case where the ticket change information is not located in the changeable range in the changeable information type corresponding to the first team ticket.
The change request verification unit 400 is configured to determine whether the team ticket change request satisfies each of the limiting conditions.
The change balance obtaining unit 500 is configured to obtain a change balance when the change request of the team ticket satisfies each of the limiting conditions.
Optionally, the change balance obtaining unit 500 is specifically configured to calculate the amount of the new ticket and the difference between the new ticket and the old ticket according to the new ticket information when the change request of the team ticket meets the limiting conditions.
The embodiment can calculate the amount of the new ticket according to the destination, the travel date, the flight number, the class level and other information in the new ticket information.
The ticket information changing unit 600 is configured to send a change confirmation message to the user side device, where the change confirmation message carries the change balance.
The embodiment can send a change confirmation message to the user side device after the calculation of the sum of the new ticket and the difference between the new ticket and the old ticket. The change allowance carried in the change confirmation message may include: new and old ticket differences, tax differences, commission fees, and total charge or refund amounts. The change confirmation message may further include: and the destination, the travel date, the flight number, the cabin level and other information of the unchanged users and the new ticket information of the users requiring to be changed in the first team ticket.
The change result obtaining unit 700 is configured to, after obtaining the confirmation feedback of the user on the change confirmation message, change the original ticket information according to the new ticket information, and obtain a change result.
The confirmation feedback may carry a message that the charge and return processing is completed, and after the confirmation feedback is received, the present embodiment may determine that the charge and return processing is completed by the user.
The embodiment may send the change result to the user side device for display.
The automatic change device for the team tickets provided by the embodiment can obtain a team ticket change request for changing the first team tickets, wherein the team ticket change request carries ticket change information of at least two users, and the ticket change information comprises an identifier of an original ticket of the user; obtaining original ticket information and new ticket information according to the identifier of the original ticket; obtaining a restriction condition corresponding to the first team ticket; determining whether the team ticket change request satisfies each of the restrictions; when the change request of the team passenger ticket meets each limiting condition, obtaining a change difference; sending a change confirmation message to user side equipment, wherein the change confirmation message carries the change difference; and after the confirmation feedback of the user to the change confirmation message is obtained, changing the original ticket information according to the new ticket information to obtain a change result. The technical means of verifying whether the change request of the team tickets meets the limiting conditions in an automatic mode is adopted, the technical problem that manual change of the team tickets is low in efficiency is solved, and then the efficiency of the change of the team tickets is improved.
In this application, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a," "8230," "8230," or "comprising" does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (6)
1. A method for automatic change of a team ticket, the method comprising:
obtaining a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, the ticket change information comprises an identification of an original ticket of the user, change space information, change travel date information and change flight information, and the change of the first team ticket comprises whole group change and group removal change;
obtaining original passenger ticket information and new passenger ticket information according to the identification of the original passenger ticket;
simulating and recalculating the original ticket price according to the original ticket information to obtain a limiting condition corresponding to the original ticket price, wherein the simulated and recalculated original ticket price specifies one or more of the travel, flight, travel date and space of the original ticket to perform simulated recalculation;
determining whether the team ticket change request satisfies each of the restrictions;
when the change request of the team passenger ticket meets each limiting condition, obtaining a change difference;
sending a change confirmation message to the user side equipment, wherein the change confirmation message carries the change difference, destination, travel date, flight number and space level information of the unchanged users in the first team of tickets and new ticket information of the users requesting to be changed, and the change difference comprises: new and old ticket difference, tax difference, commission and total charge or total refund amount;
after the confirmation feedback of the user to the change confirmation message is obtained, the original ticket information is changed according to the new ticket information, and a change result is obtained;
wherein,
the limiting conditions include: a first change condition of the number of persons and/or a second change condition of the number of persons;
the first change number condition is as follows: the number of the users requesting to change is the same as the number of the users included in the first team ticket, or the number of the users not requesting to change is not lower than the minimum group number of people, wherein the number of the users requesting to change is the number of the users corresponding to each piece of ticket change information carried by the team ticket change request, and the number of the users not requesting to change is: the number of users included in the first team ticket minus the number of users requesting a change in the number of users;
the second change number condition is as follows: requesting to change the number of the users to be the same as the number of the users included in the first team passenger ticket; or the number of the unchanged users and the number of the users requesting to change are not lower than the minimum group number.
2. The method of claim 1, wherein obtaining the original ticket information and the new ticket information based on the identification of the original ticket comprises:
obtaining original ticket information corresponding to the identifier of the original ticket in a ticket sale database according to the identifier of the original ticket;
and obtaining new passenger ticket information corresponding to the identifier of the original passenger ticket in the passenger booking record according to the identifier of the original passenger ticket.
3. The method of claim 1, wherein obtaining a change differential when the team ticket change request satisfies each of the constraints comprises:
and when the change request of the team passenger ticket meets the limiting conditions, calculating the sum of the new passenger ticket and the difference between the new passenger ticket and the old passenger ticket according to the information of the new passenger ticket.
4. An automatic change device of a team ticket, comprising: a change request obtaining unit, a ticket information obtaining unit, a limit condition obtaining unit, a change request verifying unit, a change balance obtaining unit, a ticket information changing unit, and a change result obtaining unit,
the change request obtaining unit is used for obtaining a team ticket change request for changing a first team ticket, wherein the team ticket change request carries ticket change information of at least two users, the ticket change information comprises an identifier of an original ticket of the user, change cabin position information, change travel date information and change flight information, and the change of the first team ticket comprises whole group change and group-dismantling change;
the ticket information obtaining unit is used for obtaining original ticket information and new ticket information according to the identifier of the original ticket;
the limiting condition obtaining unit is used for obtaining a limiting condition corresponding to the first team passenger ticket;
the change request verification unit is used for determining whether the team ticket change request meets the limiting conditions;
the change balance obtaining unit is configured to obtain a change balance, destination, travel date, flight number, and class level information of new ticket information of an unchanged user and a requested user in the first team ticket when the team ticket change request satisfies each of the limiting conditions, where the change balance includes: new and old ticket difference, tax difference, commission and total charge or total refund amount;
the passenger ticket information changing unit is used for sending a change confirmation message to the user side equipment, wherein the change confirmation message carries the change difference;
the change result obtaining unit is used for changing the original ticket information according to the new ticket information after obtaining the confirmation feedback of the user on the change confirmation message, and obtaining a change result;
the limiting condition obtaining unit is specifically configured to simulate recalculation of an original ticket fare according to the original ticket information to obtain a limiting condition corresponding to the original ticket fare, where the simulated recalculation of the original ticket fare specifies one or more of a travel, a flight, a travel date, and a slot of the original ticket to perform simulated recalculation;
the limiting conditions include: a first change condition of the number of persons and/or a second change condition of the number of persons;
the first change number condition is as follows: the number of the users requesting to change is the same as the number of the users included in the first team ticket, or the number of the users not requesting to change is not lower than the minimum group number of people, wherein the number of the users requesting to change is the number of the users corresponding to each piece of ticket change information carried by the team ticket change request, and the number of the users not requesting to change is: the number of users included in the first team ticket minus the number of users requesting a change in the number of users;
the second change number condition is as follows: requesting to change the number of the users to be the same as the number of the users included in the first team passenger ticket; or the number of the unchanged users and the number of the users requesting to change are not lower than the minimum group number.
5. The apparatus according to claim 4, wherein the ticket information obtaining unit is specifically configured to obtain, in a ticket sales database, original ticket information corresponding to the identifier of the original ticket according to the identifier of the original ticket;
the ticket information obtaining unit is specifically configured to obtain new ticket information corresponding to the identifier of the original ticket in a passenger booking record according to the identifier of the original ticket.
6. The apparatus of claim 4, wherein the change balance obtaining unit is configured to calculate the new ticket amount and the new and old ticket differences according to the new ticket information when the team ticket change request satisfies the respective limiting conditions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910999130.3A CN110751519B (en) | 2019-10-21 | 2019-10-21 | Automatic change method and device for team passenger tickets |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910999130.3A CN110751519B (en) | 2019-10-21 | 2019-10-21 | Automatic change method and device for team passenger tickets |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110751519A CN110751519A (en) | 2020-02-04 |
| CN110751519B true CN110751519B (en) | 2023-03-24 |
Family
ID=69278991
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910999130.3A Active CN110751519B (en) | 2019-10-21 | 2019-10-21 | Automatic change method and device for team passenger tickets |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110751519B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111784399B (en) * | 2020-06-30 | 2024-09-13 | 中国民航信息网络股份有限公司 | System and method for calculating price of returning and modifying label |
| JP7497246B2 (en) | 2020-08-19 | 2024-06-10 | 東日本旅客鉄道株式会社 | Information processing program, information processing method, and server device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0981799A (en) * | 1995-09-18 | 1997-03-28 | Toshiba Corp | Ticket processor |
| JPH1125195A (en) * | 1997-07-07 | 1999-01-29 | Toshiba Corp | Seat management system |
| JP2014232398A (en) * | 2013-05-29 | 2014-12-11 | 株式会社日立製作所 | Ticket system and boarding method |
| CN105354689A (en) * | 2015-12-20 | 2016-02-24 | 北京民航信息科技有限公司 | Computer system based civil aviation team management method and system |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07325939A (en) * | 1994-05-31 | 1995-12-12 | Toshiba Corp | Group passenger ticket processing device |
| US8195486B2 (en) * | 2006-11-15 | 2012-06-05 | Amadeus S.A.S | Airline ticket change constrainer |
| CN105528642A (en) * | 2015-12-20 | 2016-04-27 | 北京民航信息科技有限公司 | Group air ticket transaction method and system based on computer system |
| CN105654182A (en) * | 2015-12-28 | 2016-06-08 | 中国民航信息网络股份有限公司 | System and method for performing automatic time limit management and seat clearing on passenger team |
| CN105760990A (en) * | 2016-02-04 | 2016-07-13 | 中国民航信息网络股份有限公司 | Passenger ticket changing system and method |
| CN107426333A (en) * | 2017-08-10 | 2017-12-01 | 中国民航信息网络股份有限公司 | Self-service move back changes label method of servicing and system |
| CN109034974A (en) * | 2018-07-25 | 2018-12-18 | 海南好拼网络科技有限公司 | Air ticket purchasing system based on the network platform |
| CN109102364A (en) * | 2018-08-06 | 2018-12-28 | 海南好拼网络科技有限公司 | Air ticket supply management system and air ticket supplies management method based on the network platform |
-
2019
- 2019-10-21 CN CN201910999130.3A patent/CN110751519B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0981799A (en) * | 1995-09-18 | 1997-03-28 | Toshiba Corp | Ticket processor |
| JPH1125195A (en) * | 1997-07-07 | 1999-01-29 | Toshiba Corp | Seat management system |
| JP2014232398A (en) * | 2013-05-29 | 2014-12-11 | 株式会社日立製作所 | Ticket system and boarding method |
| CN105354689A (en) * | 2015-12-20 | 2016-02-24 | 北京民航信息科技有限公司 | Computer system based civil aviation team management method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110751519A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230334545A1 (en) | Systems and methods for creating 3d objects | |
| US10922708B2 (en) | Method and system for avoidance of parking violations | |
| RU2754066C2 (en) | Method and system for customized on-demand services | |
| US9997071B2 (en) | Method and system for avoidance of parking violations | |
| JP3991811B2 (en) | Inventory control system and inventory control method | |
| KR102291049B1 (en) | Vehicle managing method linked with car repair station using smart device | |
| CN110751519B (en) | Automatic change method and device for team passenger tickets | |
| CN105631630A (en) | Passenger order data processing method and device | |
| KR102317543B1 (en) | Inventory sharing method through tire inventory management | |
| US20140288981A1 (en) | Methods and systems for travel-based interactions | |
| JP2022183315A (en) | Sales activity management system by portable terminal, control method for sales activity management system by portable terminal, program for sales activity management system by portable terminal, and recording medium | |
| CN107771340B (en) | Customized service providing system and method for traveler | |
| US20060026014A1 (en) | Methods, systems and computer program products for performing subsequent transactions for prior purchases | |
| US20120150575A1 (en) | Quotation system and method | |
| TW202203100A (en) | Used secondary battery reuse system | |
| CN113379084A (en) | Air ticket time-changing method and air ticket time-changing device | |
| US20140279268A1 (en) | Methods and systems for alternative trip comparisons and/or queue-based interactions | |
| KR20220092306A (en) | Method for providing subscription economy based rental price comparison service | |
| JP2018205876A (en) | Damaged car assessment system | |
| CN111797329B (en) | Travel information processing method and device | |
| JP2003242329A (en) | Computer system for optimizing vehicle specification so as to fit customer need and method thereof | |
| KR20190057954A (en) | Vehicle management system based on Big Data | |
| US20060149636A1 (en) | Method and system for directing the sourcing of a part or component from a secondary supplier | |
| US20150294236A1 (en) | Electronic miscellaneous document handling in response to voluntary modifications of ancillary services | |
| JP2022184159A (en) | Information processing system, information processing method, information processing device, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |