Ticket issuance system and method thereof

Abstract

The present invention relates to a ticket issuance system and a method thereof, and more specifically, to a ticket issuance system for rehandling an issued ticket, comprising a database unit including ticket information and payment information, and a control unit that receives a request for rehandling of said ticket, transmits a request for cancellation of said ticket to an external platform, and rehandles said ticket based on the cancellation result of said external platform, wherein the control unit rehandles said ticket based on the date of the request for rehandling of said ticket and the date of issuance of said ticket.

Description

Technology Field

[0001] The present invention relates to a ticket issuance system and a method thereof, and more specifically, to a ticket issuance system and a method thereof that enables inquiry and re-handling of tickets purchased on an external platform at a station counter terminal. Background Technology

[0002] Mobile train ticket sales services are provided using smartphone applications. Through this application, customers wishing to use the train can reserve their desired seats by selecting the date, time, and number of passengers. Furthermore, if a reservation needs to be refunded, the ticket can be easily returned by selecting the relevant ticket and canceling the payment via the application. Additionally, in situations where the application is unavailable, the seat can be checked and re-handled through terminals at station ticket counters.

[0003] However, currently, customers who purchased tickets through external platforms other than the application cannot use services such as ticket lookup, reissuance, travel changes, or refunds at station counters due to payment encryption and security concerns. Consequently, there is the inconvenience of having to access the website where the ticket was purchased directly to cancel or change it. Prior art literature

[0004] Korean Registered Patent Publication No. 10-2272817 ("Device and method for providing ticket sales service," date of publication May 6, 2021) The problem to be solved

[0005] The present invention has been devised to solve the problems described above. The purpose of the ticket issuance system and method according to the present invention is to provide a ticket issuance system and method that can improve the convenience of using trains by enabling ticket purchases made on an external platform to be viewed and rehandled at a station counter terminal. means of solving the problem

[0006] A ticket issuance system and method according to various embodiments of the present invention for solving the problems described above are a ticket issuance system for rehandling an issued ticket, wherein the ticket issuance system for rehandling an issued ticket comprises a database unit including ticket information and payment information, and a control unit that receives a request for rehandling of the ticket, transmits a request for cancellation of the ticket to an external platform, and rehandles the ticket based on the cancellation result of the external platform, wherein the control unit rehandles the ticket based on the date of the request for rehandling of the ticket and the date of issuance of the ticket.

[0007] In addition, the control unit is characterized by, upon receiving a request for re-handling on the day of issuance of the ticket, sharing ticket lookup information including ticket information and payment information contained in the database unit, and, based on the cancellation result of the external platform, transmitting the corresponding ticket lookup result from the database unit to the external platform, and transmitting a payment cancellation request signal to the external platform so that the external platform transmits a payment cancellation request to the card company server according to the ticket lookup result.

[0008] In addition, the control unit shares ticket lookup information including ticket information and payment information included in the database unit, and based on the cancellation result of the external platform, transmits the lookup result of the corresponding ticket from the database unit to the external platform, and transmits a payment cancellation request signal to the external server so that the external server transmits a payment cancellation request to the card company server.

[0009] In addition, the search result of the above ticket is characterized by including ticket information including at least one of a return number, itinerary, number of people, the amount of the above ticket, and a discount.

[0010] In addition, the inquiry result of the above ticket is characterized by providing partial cancellation information in cases where the full cancellation is not possible.

[0011] In addition, a ticket issuance system for re-handling tickets issued on an external platform is characterized by including a database unit containing information on reserved tickets and payment information, and a control unit that, when the issuance of the reserved ticket fails in response to a request for issuance from the external platform, transmits ticket issuance information containing details of the ticket issuance failure to the external platform, thereby controlling the external platform to transmit a network cancellation request signal to a card company server.

[0012] In addition, a method for rehandling a ticket issuance system that rehandles a ticket issued on an external platform, including a database unit, wherein a control unit comprises the steps of: (a) receiving a request for rehandling of the ticket; and (b) transmitting a request for cancellation of the ticket to the external platform and rehandling the ticket based on the cancellation result of the external platform, wherein the control unit rehandles the ticket based on the date of the request for rehandling of the ticket and the date of issuance of the ticket.

[0013] Additionally, when a request for re-handling is received on the day of issuance of the above ticket, the above step (b) is characterized by sharing ticket inquiry information including ticket information and payment information contained in the database unit, and, based on the cancellation result of the external platform, transmitting the corresponding ticket inquiry result from the database unit to the external platform, and transmitting a payment cancellation request signal to the external platform so that the external platform transmits a payment cancellation request to the card company server according to the ticket inquiry result.

[0014] Additionally, when a request for re-handling is received after the issuance date of the above ticket, the above step (b) shares ticket lookup information including ticket information and payment information contained in the database unit, and based on the cancellation result of the external platform, transmits the corresponding ticket lookup result from the database unit to the external platform, and transmits a payment cancellation request signal to the external server so that the external server transmits a payment cancellation request to the card company server.

[0015] In addition, the search result of the above ticket is characterized by including ticket information including at least one of a return number, itinerary, number of people, the amount of the above ticket, and a discount.

[0016] In addition, the inquiry result of the above ticket is characterized by providing partial cancellation information in cases where the full cancellation is not possible. Effects of the invention

[0017] According to the ticket issuance system and method of the present invention as described above, tickets purchased not only through an application but also through an external platform providing ticket purchasing services can be conveniently rehandled, such as by canceling or changing them at a station counter or on the train, thereby improving the convenience of train usage for customers. Brief explanation of the drawing

[0018] FIG. 1 is a flowchart illustrating a conventional method of booking and paying for tickets through an external platform, and FIG. 2 is a flowchart illustrating a conventional method of returning a ticket issued through an external platform on the day of issuance, and FIG. 3 is a flowchart illustrating a conventional method of returning a ticket issued through an external platform after the ticketing date, and FIG. 4 is a schematic diagram illustrating a ticket issuance system according to an embodiment of the present invention, and FIG. 5 is a flowchart illustrating a method for returning a ticket issued through a ticket issuance system on the day of issuance according to an embodiment of the present invention, and FIG. 6 is a flowchart illustrating a method for returning a ticket issued through a ticket issuance system after the ticket issuance date according to another embodiment of the present invention. FIG. 7 is a flowchart illustrating a method for canceling a ticketing error in case of a ticketing error according to another embodiment of the present invention. Specific details for implementing the invention

[0019] In order to explain the present invention, the operational advantages of the present invention, and the objectives achieved by the implementation of the present invention, preferred embodiments of the present invention are illustrated below and examined with reference thereto.

[0020] First, the terms used in this application are used merely to describe specific embodiments and are not intended to limit the invention; singular expressions may include plural expressions unless the context clearly indicates otherwise. Furthermore, in this application, terms such as "comprising" or "having" are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0021] In describing the present invention, if it is determined that a detailed description of related known components or functions may obscure the essence of the invention, such detailed description is omitted.

[0022] Figure 1 is a flowchart illustrating a conventional method of booking and paying for tickets through an external platform.

[0023] Referring to Fig. 1, I will explain the method by which tickets are reserved and paid for through a conventional external platform and ticket issuance system.

[0024] First, a request for a remaining seat lookup (S10) can be made to the ticket issuance system (conventional) to issue a ticket from a conventional external platform. When requesting a remaining seat lookup, the request can be made based on the boarding date, train type, departure station, arrival station, seat attributes, required number of seats, etc. Additionally, the ticket issuance system stores train information and remaining seats, and in response to the request for a remaining seat lookup from the external platform, it can provide information to the external platform including the train number, departure station, arrival time, arrival station, arrival time, and remaining seats by carriage (S20). Subsequently, a ticket reservation request can be received from the external platform (S30). At this time, the reservation request information may include a name, contact information, itinerary information, passenger information, discount information, etc. Additionally, in response to this, the ticket reservation result may be provided to the external platform (S40), and the ticket reservation result may include a PNR number, itinerary information, seat, fare, fee, and discount information. At the same time, the ticket issuance system (10) can store the corresponding reservation information.

[0025] After reserving a ticket in the manner described above, the external platform requests credit payment approval from the card company server and receives the card approval result. At this time, the credit payment approval request may include a merchant code, card number (OTC), payment amount, and installment period. Additionally, the card approval result may include the approval date, approval number, and payment amount.

[0026] Subsequently, the ticket issuance system receives a ticket issuance request from an external platform (S50) and provides the ticket issuance result to the external platform. Specifically, upon receiving the ticket issuance request, the system receives reservation information (PNR number) and payment information (card number, approval date, approval number, payment amount), stores the received payment information, and provides the ticket issuance result (S60) based on the stored ticket information. Specifically, the ticket issuance result may include a ticket return number.

[0027] Figure 2 is a flowchart illustrating a conventional method of returning a ticket issued through an external platform on the day of issuance.

[0028] With reference to Fig. 2, I will explain the operation of the external platform and the ticket issuance system when processing the return of a ticket at a conventional external platform.

[0029] First, the ticket issuance system holds ticket information and payment information for the issued ticket. At this time, when a ticket lookup request is received (S10) from an external platform based on the return number of the ticket to be returned, the ticket lookup result can be transmitted (S20) based on the previously stored ticket information and payment information. At this time, the ticket lookup result may include ticket information and return amount information. Specifically, the ticket information may include the return number, itinerary, number of passengers, ticket amount, and discount information, and the return amount information may include the total return amount based on the previously stored payment information, the return amount by payment method, the return fee, etc.

[0030] Subsequently, the ticket issuance system may receive a ticket refund request from an external platform (S30) and provide a ticket refund result accordingly (S40). At this time, the ticket refund request may include a refund number, a refund amount, and a refund fee.

[0031] Accordingly, based on the ticket return request and result, the external platform may request the card company server to cancel the card authorization and receive the result of the card authorization cancellation from the said card company server.

[0032] FIG. 3 is a flowchart illustrating a method for returning a ticket issued through an external platform after the conventional ticketing date.

[0033] If a ticket is returned through the external platform where it was issued after the date of issuance, it may be as follows.

[0034] First, the ticket issuance system holds ticket information and payment information for the issued ticket. At this time, when a ticket lookup request is received (S10) from an external platform based on the return number of the ticket to be returned, the ticket lookup result can be transmitted (S20) based on the previously stored ticket information and payment information. Specifically, the ticket lookup result may include ticket information and return amount information. More specifically, the ticket information may include the return number, itinerary, number of passengers, ticket amount, and discount information, and the return amount information may include the total return amount based on the previously stored payment information, the return amount by payment method, the return fee, etc.

[0035] Subsequently, the ticket issuance system may receive a ticket refund request from an external platform (S30) and provide a ticket refund result accordingly (S40). At this time, the ticket refund request may include a refund number, a refund amount, and a refund fee.

[0036] Accordingly, the ticket issuance system can provide ticket return information, which is refund information for card settlement, to a separate business management system (S50). With this, the business management system can purchase card cancellations from the card company server and receive the cancellation purchase result. Specifically, it can transmit a purchase cancellation file to the card company server and receive a purchase cancellation result file from the card company server.

[0037] FIG. 4 is a schematic diagram illustrating a ticket issuance system according to an embodiment of the present invention.

[0038] A ticket issuance system (1000) for rehandling issued tickets according to one embodiment of the present invention includes a database unit (100) and a control unit (200).

[0039] The database unit (100) includes information on the issued ticket and payment information. At this time, the ticket information may include a return number, itinerary, number of passengers, ticket amount, discount information, ticket status, etc. Meanwhile, when providing ticket information, if it is not a full cancellation, partial cancellation information may be provided.

[0040] The control unit (200) receives a request to rehandle an issued ticket and can transmit a request to cancel the ticket to an external platform (20). Additionally, it can rehandle the ticket based on the ticket cancellation result received from the external platform (20).

[0041] Specifically, the control unit (200) can rehandle the ticket based on the date of the request for rehandling of the ticket (hereinafter, the ticket refers to all issued tickets) and the date of issuance of the ticket.

[0042] More specifically, if a request for re-handling is received on the day of ticket issuance, it constitutes a cancellation of approval; however, if a request for re-handling is received after the date of issuance, it may constitute a cancellation of purchase. Therefore, I will explain these two cases in detail.

[0043] [Example 1] Case of cancellation of approval

[0044] When the control unit (200) receives a request for re-handling, i.e., a request for cancellation of approval, on the day of ticket issuance, it may transmit a ticket cancellation request to an external platform (20). At this time, ticket inquiry information including ticket information and payment information contained in the database unit (100) can be shared with the external platform (20), and subsequently, based on the cancellation result of the external platform (20), the database unit (100) may provide the inquiry result of the corresponding ticket to the external platform (20). Additionally, based on the inquiry result of the corresponding ticket from the database unit (100), a payment cancellation request signal may be transmitted to the external platform (20) so that the external platform (20) transmits a payment cancellation request to the card company server. Accordingly, the external platform that received the ticket cancellation request may request the card company server to cancel the card approval and may receive the card approval cancellation result from the card company server.

[0045] [Example 2] Case of purchase cancellation

[0046] When the control unit (200) receives a request for re-handling, i.e., a request for cancellation of purchase, after the ticket issuance date, it may transmit the ticket cancellation request to the external platform (20). At this time, ticket inquiry information including ticket information and payment information contained in the database unit (100) can be shared with the external platform (20), and subsequently, based on the cancellation result of the external platform (20), the inquiry result of the corresponding ticket from the database unit (100) can be provided to the external platform (20). Additionally, a payment cancellation request may be transmitted to the external server so that the external server transmits a payment cancellation request to the card company server. Specifically, ticket return information (approval number, cancellation amount), which is refund information for card settlement, may be transmitted. By doing so, the external server can purchase the card cancellation from the card company server and receive the cancellation purchase result. Specifically, it can transmit the purchase cancellation file to the card company server and receive the purchase cancellation result file from the card company server. Meanwhile, an external platform (20) that receives the ticket inquiry result can send card cancellation information including the ticket cancellation details to the payment server for customers who check the cancellation details through a separate payment server.

[0047] A ticket issuance system (1000) for rehandling tickets issued on an external platform (20) according to another embodiment of the present invention includes a database unit (100) and a control unit (200).

[0048] The database section (100) includes information on reserved tickets and payment information. At this time, the ticket information may include a return number, itinerary, number of passengers, ticket amount, discount information, ticket status, etc.

[0049] The control unit (200) can provide the external platform (20) with ticket issuance information including details of the ticket issuance failure when the issuance of a ticket requested by the external platform (20) fails. By doing so, the external platform (20) can be controlled to transmit a network cancellation request signal to the card company server. Specifically, when the external platform (20) requests network cancellation from the card company server, it may request network cancellation for the previous approval details and may include the card number, approval date, approval number, approval amount, etc. Upon receiving this, the card company server can transmit the network cancellation result to the external platform (20).

[0050] Thus, customers purchasing tickets can conveniently purchase them at an external platform (20), and can conveniently cancel or change tickets purchased through the external platform (20) at a station counter equipped with the ticket issuance system (1000) of the present invention and on the train, making train use more convenient.

[0051] Hereinafter, a rehandling method of the ticket issuance system (1000) according to the present invention will be explained through FIGS. 5 to 7.

[0052] FIGS. 5 and 6 are flowcharts illustrating a method for returning a ticket issued through a ticket issuance system according to the present invention.

[0053] As illustrated in FIGS. 5 and 6, a rehandling method of a ticket issuance system (1000) that rehandles a ticket issued from an external platform (20), including a database unit (100) according to an embodiment of the present invention, comprises the steps of: a control unit (200) receiving a request to rehandle a ticket (S100); and (b) transmitting a request to cancel a ticket to an external platform (20) and rehandling the ticket based on the cancellation result of the external platform (20).

[0054] Specifically, the ticket lookup results may include the return number, itinerary, number of passengers, ticket price, discount information, and ticket status. Meanwhile, when providing ticket information, partial cancellation information may also be provided in cases where the cancellation is not full.

[0055] At this time, the control unit (200) can rehandle the ticket based on the date of the request for rehandling of the ticket (hereinafter, the ticket refers to all issued tickets) and the date of issuance of the ticket.

[0056] [Example 1] Case of cancellation of approval

[0057] As illustrated in FIG. 5, when the control unit (200) receives a request for re-handling, i.e., a request for cancellation of approval, on the day of ticket issuance, it may transmit a ticket cancellation request (S100) to an external platform (20). At this time, ticket inquiry information including ticket information and payment information included in the database unit (100) can be shared with the external platform (20). Subsequently, a ticket cancellation result is received from the external platform (20) (S200), and based on the received ticket cancellation result, a corresponding ticket inquiry result from the database unit (100) can be provided to the external platform (20) (S300). Subsequently, based on the corresponding ticket inquiry result from the database unit (100), a payment cancellation request signal can be transmitted to the external platform (20) so that the external platform (20) transmits a payment cancellation request to the card company server. Accordingly, the external platform that received the ticket cancellation request may request a card approval cancellation from the card company server and may receive a card approval cancellation result from the card company server.

[0058] [Example 2] Case of purchase cancellation

[0059] As illustrated in FIG. 6, when the control unit (200) receives a request for re-handling, i.e., a request for cancellation of purchase, after the ticket issuance date, it may transmit a ticket cancellation request (S100) to an external platform (20). At this time, ticket inquiry information including ticket information and payment information contained in the database unit (100) can be shared with the external platform (20). Subsequently, a ticket cancellation result is received from the external platform (20) (S200), and based on the received ticket cancellation result, a corresponding ticket inquiry result from the database unit (100) can be provided to the external platform (20) (S300). Additionally, a payment cancellation request can be transmitted to the external server (S400) so that the external server transmits a payment cancellation request to the card company server. Specifically, ticket return information (approval number, cancellation amount), which is refund information for card settlement, can be transmitted. By doing so, the external server can purchase the card cancellation from the card company server and receive the cancellation purchase result. Specifically, a purchase cancellation file is transmitted to a card company server, and a purchase cancellation result file can be received from the card company server. Meanwhile, an external platform (20) that receives the ticket inquiry result can transmit card cancellation information containing the ticket cancellation details to the payment server for a customer who checks the cancellation details through a separate payment server.

[0060] In the case of network cancellation, as illustrated in FIG. 7, the control unit (200) may request a ticket reservation (S100) from an external platform (20). Accordingly, the ticket issuance system (1000) may transmit the ticket reservation result to the external platform (20) (S200). Subsequently, the system receives a request for the issuance of the reserved ticket from the external platform (20) (S300), and if the issuance of the ticket fails, it may provide the ticket issuance information containing the details of the ticket issuance failure to the external platform (20) (S400). By doing so, the system can control the external platform (20) to transmit a network cancellation request signal to the card company server. Specifically, when the external platform (20) requests network cancellation to the card company server, it may request network cancellation for the previous approval details and may include the card number, approval date, approval number, approval amount, etc. Upon receiving this, the card company server may transmit the network cancellation result to the external platform (20).

[0061] Thus, customers purchasing tickets can conveniently purchase them at an external platform (20), and can conveniently cancel or change tickets purchased through the external platform (20) at a station counter equipped with the ticket issuance system (1000) of the present invention and on the train, making train use more convenient.

[0062] Although preferred embodiments of the present invention have been described above, the present invention is not limited to the specific embodiments described above. That is, those skilled in the art to which the present invention pertains can make numerous changes and modifications to the present invention without departing from the spirit and scope of the appended claims, and all such appropriate changes and modifications should be deemed to fall within the scope of the present invention as equivalents. Explanation of the symbols

[0063] 10 : Ticket issuance system (conventional) 20 : External platform 1000 : Ticket issuance system 100 : Database section 200 : Control unit API: Application Programming Interface

Claims

Claim 1 In a ticket issuance system for re-handling issued tickets, a database unit including ticket information and payment information; and a control unit that receives a request for re-handling of the above ticket, transmits a request for cancellation of the ticket to an external platform, and re-handles the above ticket based on the cancellation result of the external platform; wherein the control unit re-handles the above ticket based on the date of the request for re-handling of the above ticket and the date of issuance of the above ticket, does not communicate directly with the card company server, and when the request for re-handling is received on the day of issuance of the above ticket, shares ticket lookup information including the ticket information and payment information contained in the database unit, and based on the cancellation result of the external platform, transmits the corresponding lookup result of the above ticket from the database unit to the external platform, and transmits a payment cancellation request signal to the external platform so that the external platform transmits a payment cancellation request to the card company server according to the lookup result of the above ticket, and when the request for re-handling is received after the date of issuance of the above ticket, shares ticket lookup information including the ticket information and payment information contained in the database unit, and based on the cancellation result of the external platform, transmits the corresponding lookup result of the above ticket from the database unit to the external platform, and the external server makes a payment to the card company server A ticket issuance system characterized by transmitting a payment cancellation request signal to the external server to transmit a cancellation request. Claim 2 delete Claim 3 delete Claim 4 A ticket issuance system according to claim 1, characterized in that the inquiry result of the ticket includes ticket information including at least one of a return number, journey, number of people, the amount of the ticket, and a discount. Claim 5 A ticket issuance system characterized in that, in the case of the inquiry result of the above ticket in paragraph 4, if the full cancellation is not possible, it provides partial cancellation information. Claim 6 A ticket issuance system for re-handling tickets issued from an external platform, comprising: a database unit including information on reserved tickets and payment information; and a control unit that, when the issuance of the reserved ticket fails in response to a request for issuance of the ticket from the external platform, transmits ticket issuance information including details of the ticket issuance failure to the external platform, thereby controlling the external platform to transmit a network cancellation request signal to a card company server. Claim 7 A method for rehandling a ticket issuance system that rehandles a ticket issued on an external platform, including a database unit, wherein the control unit comprises: (a) receiving a request for rehandling of the ticket; and (b) transmitting a request for cancellation of the ticket to the external platform and rehandling the ticket based on the cancellation result of the external platform; wherein the control unit rehandles the ticket based on the date of the request for rehandling of the ticket and the date of issuance of the ticket, and does not communicate directly with a card company server, and when the request for rehandling is received on the day of issuance of the ticket, the step (b) shares ticket inquiry information including ticket information and payment information contained in the database unit, and transmits the corresponding inquiry result of the ticket from the database unit to the external platform based on the cancellation result of the external platform, and transmits a payment cancellation request signal to the external platform so that the external platform transmits a payment cancellation request to the card company server according to the inquiry result of the ticket, and when the request for rehandling is received after the date of issuance of the ticket, the step (b) is a method for rehandling a ticket issuance system, characterized by sharing ticket inquiry information including ticket information and payment information included in the database unit, and transmitting the inquiry result of the corresponding ticket from the database unit to the external platform based on the cancellation result of the external platform, and transmitting a payment cancellation request signal to the external server so that the external server transmits a payment cancellation request to the card company server. Claim 8 delete Claim 9 delete Claim 10 A method for rehandling a ticket issuance system according to claim 7, wherein the inquiry result of the ticket includes ticket information comprising at least one of a return number, journey, number of people, amount of the ticket, and discount. Claim 11 A method for rehandling a ticket issuance system characterized in that, in the case of the inquiry result of the above ticket in paragraph 10, if the full cancellation is not a cancellation, the result provides partial cancellation information.

Images