CN111539869B - Ticket requesting method and device and computer readable storage medium - Google Patents

Ticket requesting method and device and computer readable storage medium Download PDF

Info

Publication number
CN111539869B
CN111539869B CN201911226413.0A CN201911226413A CN111539869B CN 111539869 B CN111539869 B CN 111539869B CN 201911226413 A CN201911226413 A CN 201911226413A CN 111539869 B CN111539869 B CN 111539869B
Authority
CN
China
Prior art keywords
ticket
request
visa
change
station
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
Application number
CN201911226413.0A
Other languages
Chinese (zh)
Other versions
CN111539869A (en
Inventor
李凤华
谢绒娜
耿魁
史国振
董秀则
金伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BEIJING ELECTRONIC SCIENCE AND TECHNOLOGY INSTITUTE
Institute of Information Engineering of CAS
Original Assignee
BEIJING ELECTRONIC SCIENCE AND TECHNOLOGY INSTITUTE
Institute of Information Engineering of CAS
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by BEIJING ELECTRONIC SCIENCE AND TECHNOLOGY INSTITUTE, Institute of Information Engineering of CAS filed Critical BEIJING ELECTRONIC SCIENCE AND TECHNOLOGY INSTITUTE
Priority to CN201911226413.0A priority Critical patent/CN111539869B/en
Publication of CN111539869A publication Critical patent/CN111539869A/en
Application granted granted Critical
Publication of CN111539869B publication Critical patent/CN111539869B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40Business processes related to the transportation industry
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • G06Q10/0631Resource planning, allocation, distributing or scheduling for enterprises or organisations

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Educational Administration (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the invention discloses a ticket requesting method, terminal equipment and a computer readable storage medium, which comprise the following steps: when a first preset condition is met, a first request is generated, and the generated first request is sent to a ticket processing device or a ticket processing system; or generating a first request, and when a second preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system; or when the first preset condition is met, generating a first request, and when the third preset condition is met, sending the first request generated this time to a ticket processing device or a ticket processing system. The embodiment of the invention effectively resists the phenomenon of ticket rewinding and vending through ticket robbing software or different terminal equipment by limiting the generation and the sending of ticket purchase requests, ticket change requests and ticket visa requests, thereby improving the rationality of ticket resource allocation.

Description

Ticket requesting method and device and computer readable storage medium
Technical Field
Embodiments of the present invention relate to, but are not limited to, computer technology, and in particular, to a ticket requesting method and apparatus, and a computer readable storage medium.
Background
With the development of high-speed rail and passenger transport, great convenience is brought to the trip of people, people buy tickets through a plurality of different channels such as 12306 websites, mobile phone clients, telephones, self-service machines and the like, and the situation that one ticket is difficult in the past is gradually changed. However, in the current train and car running systems, the following problems still exist:
1) Every time a passenger flow peak appears in holidays, tickets are still a scarce social resource, various ticket robbing systems are inoculated to generate, so that the resources are not reasonably distributed, and meanwhile, bad phenomena such as ticket pouring and vending exist.
2) The passengers cannot timely understand the state of the vehicle. For example, if a shutdown, a change line, or the like occurs before a departure, a passenger needs to log in a message issued by an official authority to know the situation, and the situation of missing the message is easy to cause. For another example, in the running process of the vehicle, passengers and passengers receiving the vehicle cannot know the running state of the vehicle in time, and if the conditions such as late time occur, the passengers and the passengers receiving the vehicle cannot change the journey and the plan in time, so that time and property losses are caused.
3) And adding a random number into the first request, so that replay attack on the ticket processing device or system is effectively prevented.
In summary, how to reasonably allocate and utilize ticket resources and improve the utilization rate of the transportation system is an urgent problem to be solved in the ticket operation system.
Disclosure of Invention
The embodiment of the invention provides a ticket requesting method and device and a computer readable storage medium, which can improve the rationality of ticket resource allocation.
The embodiment of the invention provides a ticket request method, which comprises the following steps:
when a first preset condition is met, a first request is generated, and the generated first request is sent to a ticket processing device or a ticket processing system;
or generating a first request, and when a second preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system;
or when the first preset condition is met, generating a first request, and when the third preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system;
wherein the first request includes any one of: ticket purchase request, ticket change request, ticket visa request;
the first preset condition comprises:
the time interval between the current time and the first timestamp in the first request generated last time is greater than or equal to a first preset threshold value;
the second preset condition or the third preset condition includes any combination of one or more of the following:
The time interval between the first time stamp in the first request generated at this time and the first time stamp in the first request generated last time is larger than or equal to a first preset threshold value;
the time interval between the current time and the time of the last transmitted first request is greater than or equal to a first preset threshold;
the number of tickets in the first request generated at this time is smaller than or equal to a second preset threshold value.
In an embodiment of the present invention, the method further includes:
receiving ticket processing results of a ticket processing device or a ticket processing system;
or, receiving the status or the unprocessed result of the ticket corresponding to the first request of the ticket processing device or the ticket processing system, and determining whether to continue to send the first request according to the status or the unprocessed result of the ticket corresponding to the first request.
In the embodiment of the present invention, when the first request is a ticket purchase request, the ticket processing result includes any combination of one or more of the following:
ticket processing result identifier, terminal equipment identifier, first request identifier, passenger identity information, ticket number, ticket identifier, number of cars, origin station, destination station, boarding station, alighting station, transfer station, vehicle type, ticket type, date of taking bus, ticket number, whether processing is successful or not, ticket processing result verification code;
When the first request is a ticket change request, the ticket processing result includes any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the change, the origin before the change, the destination before the change, the transfer before the change, the upper station before the change, the lower station before the change, the type of the vehicle before the change, the type of the ticket before the change, the date of the train before the change, the number of tickets after the change, the origin after the change, the destination after the change, the upper station after the change, the lower station after the change, the transfer after the change, the type of the vehicle after the change, the type of the ticket after the change, the date of the train after the change, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code;
when the first request is a ticket visa request, the ticket processing result includes any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the visa, the starting station before the visa, the terminal station before the visa, the upper station before the visa, the lower station before the visa, the transfer station before the visa, the type of the vehicle before the visa, the type of the ticket before the visa, the date of taking the ticket before the visa, the number of tickets after the visa, the starting station after the visa, the terminal station after the visa, the upper station after the visa, the lower station after the visa, the transfer station after the visa, the type of the vehicle after the visa, the type of the ticket after the visa, the date of taking the visa, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code.
In an embodiment of the present invention, the status of the ticket includes any combination of one or more of the following:
ticket identifier, ticket vending status, passenger loading and unloading status, vehicle running status, ticket true and false status, financial reimbursement status;
wherein the sales status of the ticket includes any combination of one or more of the following:
whether sold, paid, changed, number of changed, visa, printed, complemented, and refunded;
the passenger getting on/off status includes any combination of one or more of the following:
whether it has been inbound, whether it has been boarding, whether it has been disembarked, whether it has been outbound;
the operating state of the vehicle includes any combination of one or more of the following:
whether the train is launched, whether the train arrives at a boarding station, whether the train arrives at a disembarking station, whether the train is stopped, whether the train is rerouted, whether the train is late, and whether the train is normally operated;
the financial reimbursement status includes any combination of one or more of:
whether the transaction is reimbursed, whether the transaction is credited or not, and whether the transaction is filed or not;
the true and false states of the ticket include: whether the ticket is valid.
In an embodiment of the present invention, the method further includes:
And receiving a second request of the ticket processing device or the ticket processing system, paying, generating a payment result and sending the payment result to the ticket processing device or the ticket processing system.
In an embodiment of the present invention, when the first request is a ticket purchase request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a train number, a starting station, a terminal station, a boarding station, a disembarking station, a transfer station, a vehicle type, a ticket type, a riding date, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code;
when the first request is a ticket change request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, passenger identity information, a train number before a change, a starting station before a change, a terminal station before a change, a transfer station before a change, an upper station before a change, a lower station before a change, a train type before a change, a train ticket type before a change, a riding date before a change, a train number after a change, a starting station after a change, a terminal station after a change, an upper station after a change, a lower station after a change, a transfer station after a change, a train type after a change, a train ticket type after a change, a riding date after a change, a train ticket number, a first request content verification code, a first time stamp, a random number and a first request verification code;
When the first request is a ticket visa request, the first request includes any combination of one or more of:
the method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a number of vehicles before a visa, an originating station before a visa, a terminal station before a visa, a boarding station before a visa, a alighting station before a visa, a transfer station before a visa, a vehicle type before a visa, a ticket type before a visa, a date of taking a vehicle before a visa, a number of vehicles after a visa, an originating station after a visa, a terminal station after a visa, a boarding station after a visa, a alighting station after a visa, a transfer station after a visa, a vehicle type after a visa, a ticket type after a visa, a date of taking a vehicle after a visa, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code.
The embodiment of the invention provides a terminal device, which comprises a processor and a computer readable storage medium, wherein instructions are stored in the computer readable storage medium, and when the instructions are executed by the processor, any ticket requesting method is realized.
An embodiment of the present invention proposes a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the steps of any of the ticket requesting methods described above.
The embodiment of the invention comprises the following steps: when a first preset condition is met, a first request is generated, and the generated first request is sent to a ticket processing device or a ticket processing system; or generating a first request, and when a second preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system; or when the first preset condition is met, generating a first request, and when the third preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system; wherein the first request includes any one of: ticket purchase request, ticket change request, ticket visa request; the first preset condition comprises: the time interval between the current time and the first timestamp in the first request generated last time is greater than or equal to a first preset threshold value; the second preset condition or the third preset condition includes any combination of one or more of the following: the time interval between the first time stamp in the first request generated at this time and the first time stamp in the first request generated last time is larger than or equal to a first preset threshold value; the time interval between the current time and the time of the last transmitted first request is greater than or equal to a first preset threshold; the number of tickets in the first request generated at this time is smaller than or equal to a second preset threshold value. The embodiment of the invention effectively resists the phenomenon of ticket rewinding and vending through ticket robbing software or different terminal equipment by limiting the generation and the sending of ticket purchase requests, ticket change requests and ticket visa requests, thereby improving the rationality of ticket resource allocation.
Additional features and advantages of embodiments of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of embodiments of the invention. The objectives and other advantages of embodiments of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the technical solution of the embodiments of the present invention, and are incorporated in and constitute a part of this specification, illustrate and explain the technical solution of the embodiments of the present invention, and not to limit the technical solution of the embodiments of the present invention.
FIG. 1 is a flow chart of a ticket requesting method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a terminal device according to another embodiment of the present invention.
Detailed Description
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that, without conflict, the embodiments of the present invention and features of the embodiments may be arbitrarily combined with each other.
The steps illustrated in the flowchart of the figures may be performed in a computer system, such as a set of computer-executable instructions. Also, while a logical order is depicted in the flowchart, in some cases, the steps depicted or described may be performed in a different order than presented herein.
The embodiment of the invention describes that passengers or ticket sellers purchase, refund, supplement, change, visa, print, reimbursement, check-in and archive tickets (which can be airplane tickets, bus tickets, train tickets and the like) through terminal equipment, and the ticket requesting method comprises the following steps:
step 100, when a first preset condition is met, a first request is generated, and the generated first request is sent to a ticket processing device or a ticket processing system; or generating a first request, and when a second preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system; or when the first preset condition is met, generating a first request, and when the third preset condition is met, sending the first request generated this time to a ticket processing device or a ticket processing system.
In another embodiment of the present invention, the first request is not generated when the first preset condition is not satisfied; or generating a first request, and when the second preset condition is not met, not sending the first request generated at this time to a ticket processing device or a ticket processing system; or when the first preset condition is met, generating a first request, and when the third preset condition is not met, not sending the generated first request to a ticket processing device or a ticket processing system.
In an embodiment of the present invention, the first preset condition includes:
the time interval between the current time and the first timestamp in the first request generated last time is greater than or equal to a first preset threshold value;
the second preset condition or the third preset condition includes any combination of one or more of the following:
the time interval between the first time stamp in the first request generated at this time and the first time stamp in the first request generated last time is larger than or equal to a first preset threshold value;
the time interval between the current time and the time of the last transmitted first request is greater than or equal to a first preset threshold;
the number of tickets in the first request generated at this time is smaller than or equal to a second preset threshold value.
In an exemplary embodiment, the terminal device may be a mobile terminal (e.g., a mobile phone, etc.), a computer, or other intelligent device.
In one illustrative example, the first request may be any one of the following: ticket purchase request, ticket change request, ticket visa request, ticket refund request, ticket complement request, ticket print request, ticket reimbursement request, ticket check-in request, ticket archiving request.
In another illustrative example, when the first request is any one of the following: when a ticket purchase request, a ticket change request and a ticket visa request are required to be judged, whether a first preset condition, a second preset condition and a third preset condition are met or not is judged, whether a first request is generated or not is determined, and whether the first request is sent to a ticket processing device or a ticket processing system or not is determined.
When the first request is any one of the following: when the ticket refund request, the ticket complement request, the ticket print request, the ticket reimbursement request, the ticket accounting request and the ticket archiving request are met, the first request is directly generated without judging whether the first preset condition, the second preset condition and the third preset condition are met, and the first request is sent to the ticket processing device or the ticket processing system.
In one illustrative example, when the first request is a ticket purchase request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a train number, a starting station, a terminal station, a boarding station, a disembarking station, a transfer station, a vehicle type, a ticket type, a riding date, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code.
When the first request is a ticket change request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, passenger identity information, a train number before a change, a starting station before a change, a terminal station before a change, a transfer station before a change, an upper station before a change, a lower station before a change, a train type before a change, a train ticket type before a change, a train date before a change, a train number after a change, a starting station after a change, a terminal station after a change, an upper station after a change, a lower station after a change, a transfer station after a change, a train type after a change, a train ticket type after a change, a train date after a change, a train ticket number, a first request content verification code, a first time stamp, a random number and a first request verification code.
When the first request is a ticket visa request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a number of vehicles before a visa, an originating station before a visa, a terminal station before a visa, a boarding station before a visa, a alighting station before a visa, a transfer station before a visa, a vehicle type before a visa, a ticket type before a visa, a date of taking a vehicle before a visa, a number of vehicles after a visa, an originating station after a visa, a terminal station after a visa, a boarding station after a visa, a alighting station after a visa, a transfer station after a visa, a vehicle type after a visa, a ticket type after a visa, a date of taking a vehicle after a visa, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code.
When the first request is any one of a ticket refund request, a ticket replacement request, a ticket print request, a ticket reimbursement request, a ticket entry request, a ticket archiving request, the first request includes any combination of one or more of the following:
the first request identifier, the terminal equipment identifier, the driver identity information, the number of vehicles, the starting station, the terminal station, the boarding station, the alighting station, the transfer station, the vehicle type, the ticket type, the riding date, the ticket number, the random number and the first request verification code.
Wherein the first request identifier is a unique identifier for describing the first request, and may be a number, a character, any combination of a number and a character;
wherein, the terminal equipment identifier refers to a unique identifier for describing the terminal equipment generating the first request, and can be any combination of numbers, characters, numbers and characters;
wherein the vehicle type is a type used to describe a vehicle, including, but not limited to, including: airplane, train, car, subway, high-speed rail, inter-city, motor car, direct, express, quick, slow car, coach, bus, taxi, express car, special car, subway;
wherein the ticket type is used for describing the corresponding vehicle type, the identity type of the passengers and the type of the seats of the ticket, and comprises, but is not limited to, any combination of the following: airplane tickets, bus tickets, train tickets, subway tickets, rental tickets, bus tickets, general tickets, student tickets, child tickets, non-ticket, general tickets, coupons, business seats, first class seats, second class seats, soft seats, hard seats, soft seats, dynamic seats, no seats, first class seats, economy class seats, business class seats;
wherein, the first timestamp refers to the time when the terminal equipment generates the first request;
The first request verification code is used for verifying the authenticity and/or the integrity of the first request, and a first algorithm can be adopted to calculate the first information to obtain the first request verification code.
Wherein the first algorithm may be any combination of one or more of the following algorithms: digital signature, digest algorithm, hash message authentication code (HMAC, hash-based Message Authentication Code), encryption authentication algorithm, bar code algorithm, two-dimensional code algorithm. Of course, other algorithms are possible, and the embodiment of the present invention is not limited thereto.
Wherein when the first request is a ticket purchase request, the first information may be any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a train number, a starting station, a terminal station, a boarding station, a alighting station, a transfer station, a vehicle type, a ticket type, a riding date, a ticket number, a first request content verification code, a first time stamp and a random number.
Such as: information included in the first request is represented by M1, information such as a first request identifier, a terminal device identifier, driver identity information, a number of vehicles, an originating station, a destination station, a boarding station, a disembarking station, a transfer station, a vehicle type, a ticket type, a riding date, a ticket number, a first request content verification code, a first timestamp and the like are represented by M11, a key is a shared key between the terminal device and a ticketing unit, and in order to ensure authenticity and/or integrity of the first request, a message authentication code M12 of the first request is generated by adopting a message authentication code algorithm HMAC, namely the first request verification code, m12=hmac (key, M11), m1=m11||m12.
Or the first request is signed by a signature algorithm, for example, the private key of the terminal device is sk1, m13=signature (sk 1, M11), m1=m11||m13. The signature algorithm may be any signature algorithm, such as SM2, ECC, RSA, etc., and all are within the protection scope of the embodiments of the present invention.
Which algorithm is specifically adopted to generate the first request verification code is not particularly limited, and the embodiment of the invention is within the protection scope of the embodiment of the invention.
When the first request is a ticket change request, the first information may be any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, passenger identity information, a train number before a change, a starting station before a change, a terminal station before a change, an upper station before a change, a lower station before a change, a transfer station before a change, a train type before a change, a train ticket type before a change, a train date before a change, a train number after a change, a starting station after a change, a terminal station after a change, an upper station after a change, a lower station after a change, a transfer station after a change, a train type after a change, a train ticket type after a change, a train date after a change, a train ticket number, a first request content verification code, a first time stamp and a random number.
When the first request is a ticket visa request, the first information may be any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a number of vehicles before a visa, an originating station before a visa, a terminal station before a visa, a boarding station before a visa, a alighting station before a visa, a transfer station before a visa, a vehicle type before a visa, a ticket type before a visa, a date of taking a vehicle before a visa, a number of vehicles after a visa, an originating station after a visa, a terminal station after a visa, a boarding station after a visa, a alighting station after a visa, a transfer station after a visa, a vehicle type after a visa, a ticket type after a visa, a date of taking a vehicle after a visa, a ticket number, a first request content verification code, a first timestamp and a random number.
When the first request is any one of a ticket refund request, a ticket replacement request, a ticket print request, a ticket reimbursement request, a ticket entry request, and a ticket archiving request, the first information may be any combination of one or more of the following information:
the first request identifier, the terminal equipment identifier, the passenger identity information, the number of cars, the starting station, the terminal station, the boarding station, the alighting station, the transfer station, the vehicle type, the ticket type, the date of boarding, the ticket number and the random number.
The first request content verification code is used for verifying the authenticity and/or integrity of the first request content, and the second information can be calculated by adopting a second algorithm to obtain the first request content verification code.
Wherein the second algorithm may be any combination of one or more of the following algorithms: digital signature, digest algorithm, HMAC, encryption authentication algorithm, bar code algorithm, two-dimensional code algorithm. Of course, other algorithms are possible, and the embodiment of the present invention is not limited thereto.
Wherein when the first request is a ticket purchase request, the second information may be any combination of one or more of the following:
the method comprises the steps of passenger identity information, number of cars, starting station, terminal station, boarding station, alighting station, transfer station, vehicle type, ticket type, date of taking bus and ticket number.
Such as: the second information is denoted by M2, the first request content verification code is denoted by M3, and the first request content is signed by a signature algorithm, for example, the private key of the terminal device is sk1, m3=signature (sk 1, M2). The signature algorithm may be any signature algorithm, such as SM2, ECC, RSA, etc., and all are within the protection scope of the embodiments of the present invention. And adding a first request content verification code into the first request for a subsequent ticketing unit to limit the same first request content to be submitted for multiple times through different terminal devices, so as to prevent the phenomena of ticket robbing, ticket brushing, ticket rewinding and the like through a plurality of terminal devices.
When the first request is a ticket change request, the second information may be any combination of one or more of the following:
the method comprises the steps of passenger identity information, a train number before a sign change, a starting station before the sign change, a terminal station before the sign change, an upper station before the sign change, a lower station before the sign change, a transfer station before the sign change, a train type before the sign change, a train ticket type before the sign change, a train date before the sign change, a train number after the sign change, the starting station after the sign change, the terminal station after the sign change, the upper station after the sign change, the lower station after the sign change, the transfer station after the sign change, the train type after the sign change, the train date after the sign change and the train ticket number.
When the first request is a ticket visa request, the second information may be any combination of one or more of the following:
the method comprises the steps of passenger identity information, a number of vehicles before visa, an originating station before visa, a terminal station before visa, a loading station before visa, a unloading station before visa, a transfer station before visa, a vehicle type before visa, a ticket type before visa, a date of taking a vehicle before visa, a number of vehicles after visa, an originating station after visa, a terminal station after visa, a loading station after visa, a unloading station after visa, a transfer station after visa, a vehicle type after visa, a ticket type after visa, a date of taking a vehicle after visa, and a ticket number.
The first time stamp is added in the first request, and the first request can only be generated and submitted once in a specified time period for the same terminal equipment, so that the phenomena of ticket robbing, ticket pouring, ticket vending and the like of ticket robbing software are prevented.
For example: the terminal device T generates a ticket purchase request R1 at time T1 and sends it to the ticket processing apparatus or system, and then plans to generate another ticket purchase request R2 again at time T2, sets the minimum time interval between two ticket purchase requests to tmin, and if (T2-T1) < tmin, the terminal device T will not generate a ticket purchase request R2, or the ticket purchase request R2 will not be processed according to the invalidation, or the generated ticket purchase request will be delayed to T3 (T3-T1) > tmin, and then sends the generated ticket purchase request R2 to the ticket processing apparatus or system.
For example: the terminal device T generates a ticket purchase request R1 at time T1 and sends the ticket purchase request R1 to a ticket processing device or a ticket processing system at time T1', then plans to generate another ticket purchase request R2 at time T2, sets the minimum time interval between two ticket purchase requests to be tmin, and sends the generated ticket purchase request R2 to the ticket processing device or the ticket processing system only when the generated ticket purchase request is delayed to T3 (T3-T1 ') < tmin if (T2-T1 ') < tmin).
The number of tickets is increased in the first request, and the maximum number of tickets purchased at one time is limited. Such as: and setting the maximum number of purchased tickets to be 6, and if the number of purchased tickets is greater than 6, invalidating the ticket purchasing request.
In the embodiment of the invention, a ticket processing device or a ticket processing system receives a first request, processes the ticket corresponding to the first request, and returns a ticket processing result; when the ticket corresponding to the first request cannot be processed, returning the state of the ticket corresponding to the first request or the result of the processing incapability. In particular, the method comprises the steps of,
when the first request is a ticket purchase request, ticket purchase is performed;
or when the first request is a ticket change request, performing the ticket change;
or when the first request is a ticket visa request, ticket visa is carried out;
or when the first request is a ticket refund request, ticket refund processing is carried out;
or when the first request is a ticket printing request, ticket printing processing is carried out;
or when the first request is a ticket reimbursement request, ticket reimbursement processing is carried out;
or when the first request is a ticket accounting request, ticket accounting processing is carried out;
Or when the first request is a ticket archiving request, ticket archiving processing is performed.
And when the first request is a ticket complement request, directly purchasing the ticket.
In another embodiment of the present invention, the method further comprises:
step 101, receiving ticket processing results of a ticket processing device or a ticket processing system; or, receiving the status or the unprocessed result of the ticket corresponding to the first request from the ticket processing device or the ticket processing system, determining whether to continue to send the first request according to the status or the unprocessed result of the ticket corresponding to the first request, and when determining to continue to send the first request, continuing to execute step 100; when it is determined that the first request is not to be continuously transmitted, the present flow is ended.
In one illustrative example, when the first request is any one of a ticket purchase request, a ticket refund request, a ticket replacement request, a ticket print request, a ticket reimbursement request, a ticket posting request, a ticket archiving request, the ticket processing results include any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the ticket number, the ticket identifier, the number of cars, the originating station, the terminating station, the boarding station, the alighting station, the transfer station, the type of the car, the type of the ticket, the date of taking the car, the ticket number, whether the processing is successful or not and the ticket processing result verification code.
When the first request is a ticket change request, the ticket processing results include any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the change, the starting station before the change, the terminal station before the change, the transfer station before the change, the boarding station before the change, the alighting station before the change, the type of the vehicle before the change, the type of the ticket before the change, the date of taking the ticket before the change, the number of tickets after the change, the starting station after the change, the terminal station after the change, the boarding station after the change, the alighting station after the change, the transfer station after the change, the type of the vehicle after the change, the type of the ticket after the change, the date of taking the ticket after the change, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code.
When the first request is a ticket visa request, the ticket processing results include any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the visa, the starting station before the visa, the terminal station before the visa, the upper station before the visa, the lower station before the visa, the transfer station before the visa, the type of the vehicle before the visa, the type of the ticket before the visa, the date of taking the ticket before the visa, the number of tickets after the visa, the starting station after the visa, the terminal station after the visa, the upper station after the visa, the lower station after the visa, the transfer station after the visa, the type of the vehicle after the visa, the type of the ticket after the visa, the date of taking the visa, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code.
The ticket processing result verification code is used for verifying the authenticity and/or the integrity of the processing result, and a third algorithm can be adopted to calculate third information to obtain the ticket processing result verification code.
Wherein the third algorithm may be any combination of one or more of the following algorithms: digital signature, digest algorithm, HMAC, encryption authentication algorithm, bar code algorithm, two-dimensional code algorithm.
Wherein, when the first request is any one of a ticket purchase request, a ticket refund request, a ticket replacement request, a ticket print request, a ticket reimbursement request, a ticket posting request, and a ticket archiving request, the third information may be any combination of one or more of the following information: the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the ticket number, the ticket identifier, the number of cars, the originating station, the terminating station, the boarding station, the alighting station, the transfer station, the type of the car, the type of the ticket, the date of taking the car and whether the processing is successful or not.
When the first request is a ticket change request, the third information may be any combination of one or more of the following: the ticket processing method comprises the steps of ticket processing result identifiers, terminal equipment identifiers, first request identifiers, passenger identity information, ticket numbers, ticket identifiers, train numbers before the ticket is changed, starting stations before the ticket is changed, terminal stations before the ticket is changed, transfer stations before the ticket is changed, boarding stations before the ticket is changed, alighting stations before the ticket is changed, vehicle types before the ticket is changed, train numbers before the ticket is changed, starting stations after the ticket is changed, terminal stations after the ticket is changed, boarding stations after the ticket is changed, alighting stations after the ticket is changed, transfer stations after the ticket is changed, train types after the ticket is changed, train dates after the ticket is changed, and whether processing is successful or not.
When the first request is a ticket visa request, the third information may be any combination of one or more of the following: the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the visa, the starting station before the visa, the terminal station before the visa, the transfer station before the visa, the boarding station before the visa, the alighting station before the visa, the vehicle type before the visa, the ticket type before the visa, the date of taking the ticket before the visa, the number of tickets after the visa, the starting station after the visa, the terminal station after the visa, the boarding station after the visa, the alighting station after the visa, the transfer station after the visa, the vehicle type after the visa, the ticket type after the visa, the date of taking the visa and whether the processing is successful or not.
In one illustrative example, the result of failure to process refers to the reason for failure to process.
When the first request is a ticket purchase request, the results that cannot be processed include any combination of one or more of the following: whether the number of tickets sold as unsold tickets in the selling state of the tickets is smaller than the number of tickets required to be purchased, the tickets are not in the selling period, the vehicles are stopped, the vehicles are rerouted, and the tickets existing by the passengers collide with the purchased tickets;
When the first request is a ticket change request, the results that cannot be processed include any combination of one or more of the following: the method is characterized in that the method does not accord with the change rule, whether the number of tickets sold as unsold in the sale state of the tickets after the change is smaller than the number of tickets required to be changed, the tickets after the change are not in the sale period, the vehicles after the change are stopped, the vehicles after the change are changed to the route, and passengers have tickets and the tickets after the change collide;
when the first request is a ticket visa request, the results that cannot be processed include any combination of one or more of the following: the method is characterized in that the method does not accord with the visa rule, whether the number of tickets sold as unsold tickets in the sale state of the tickets after the visa is smaller than the number of tickets for requesting to change, the tickets after the visa are not in the sale period, the vehicles after the visa are stopped, the vehicles after the visa are changed to the route, and the passengers have tickets which collide with the tickets after the visa;
when the first request is a refund request, the results that cannot be processed include: the vehicle has arrived at the departure station;
when the first request is a print request, the results that cannot be processed include: the ticket is printed;
when the first request is a reimbursement request, the results that cannot be processed include: the ticket is reimbursed;
When the first request is an posting request, the results that cannot be processed include any combination of one or more of the following: the ticket is not reimbursed and the ticket is checked in;
when the first request is an archive request, the results that cannot be processed include any combination of one or more of the following: the tickets are not reimbursed, the tickets are not checked in, and the tickets are filed.
In an embodiment of the present invention, the status of the ticket includes any combination of one or more of the following:
ticket identifier, ticket vending status, passenger loading and unloading status, vehicle running status, ticket authenticity status, financial reimbursement status.
The ticket identifier is used for describing the unique identifier of the ticket, and can be any combination of numbers, character strings, two-dimensional codes and bar codes, and the corresponding state of the ticket can be queried later according to the ticket identifier.
The ticket is placed in an initial state by a ticket handling device or ticket handling system during a pre-sale period prior to sale.
Wherein the sales status of the ticket includes any combination of one or more of the following:
whether sold, paid, changed, number of changed, visa, printed, complemented, and refunded.
During the pre-sale period prior to the ticket sale, the sales status of the ticket includes any combination of one or more of the following:
the number of times of unsold, unpaid, unmodified, modified is 0, unsigned, unprinted, unrepensated.
Wherein the passenger getting on/off status includes any combination of one or more of the following:
whether it is inbound, whether it is getting on, whether it is getting off, whether it is outbound.
The boarding and disembarking status of the passenger prior to the ticket sale includes any combination of one or more of the following:
not entering, not getting on, not getting off.
Wherein the operating state of the vehicle comprises any combination of one or more of the following:
whether the train has been launched, whether the train has arrived at a boarding station, whether the train has arrived at a disembarking station, whether the train is stopped, whether the train is rerouted, whether the train is late, and whether the train is operating normally.
The running state of the vehicle is determined based on the actual running state of the vehicle.
Wherein the financial reimbursement status includes any combination of one or more of:
whether reimbursed, whether credited, and whether archived.
Prior to ticket sale, the financial reimbursement status includes any combination of one or more of the following:
unreliability, unreliability.
The true and false states of the ticket include: whether the ticket is valid.
The true and false states of the ticket are determined according to actual conditions.
In one exemplary example, when the first request is a ticket purchase request, the ticket corresponding to the first request refers to whether or not a ticket in a sales state of the ticket has been sold as an unsold ticket in the ticket corresponding to any combination of one or more of a number of cars, a start station, a terminal station, an upper station, a lower station, a transfer station, a vehicle type, a ticket type, and a riding date included in the first request. For example, when the first request includes the number of passes, the ticket corresponding to the first request refers to whether the ticket is sold as an unsold ticket or not in the sales status of the ticket among the tickets of the number of passes included in the first request.
When the first request is a ticket change request, the ticket corresponding to the first request refers to the ticket which needs to be changed.
When the first request is a ticket visa request, the ticket corresponding to the first request refers to the ticket requiring visa.
When the first request is a ticket refund request, the ticket corresponding to the first request refers to the refunded ticket.
When the first request is a ticket replacement request, the ticket corresponding to the first request refers to the replaced ticket.
When the first request is a ticket print request, the ticket corresponding to the first request refers to the printed ticket.
When the first request is a ticket reimbursement request, the ticket corresponding to the first request refers to the reimbursed ticket.
When the first request is a ticket posting request, the ticket corresponding to the first request refers to the posted ticket.
When the first request is a ticket archiving request, the ticket corresponding to the first request refers to the archived ticket.
In another embodiment of the present invention, when the first request is any one of a ticket purchase request, a ticket change request, a ticket visa request, a ticket complement request, the method further comprises: and receiving a second request of the ticket processing device or the ticket processing system, paying, generating a payment result and sending the payment result to the ticket processing device or the ticket processing system.
In one illustrative example, the second request is determined to be authentic and/or complete, making a payment; in another illustrative example, payment is made directly.
In one illustrative example, the authenticity and/or integrity of the second request is verified in a manner corresponding to generating a second request verification code.
In one illustrative example, payment may be made by any combination of one or more of the following: weChat, payment treasury, online banking, cash. The mode of ticket payment and refund is not limited by the embodiment of the invention;
In one illustrative example, the payment results include any combination of one or more of the following: a payment result identifier, a terminal device identifier, a first request identifier, a ticket number, a ticket identifier, a payment method, a payment or collection medium identifier, a payment amount, whether the payment is successful or not, and a payment result verification code.
In an exemplary embodiment, the payment result verification code is used to verify the authenticity and/or integrity of the payment result, and a fourth algorithm may be used to calculate the fourth information to obtain the payment or refund result verification code.
Wherein the fourth algorithm may be any combination of one or more of the following algorithms: digital signature, digest algorithm, HMAC, encryption authentication algorithm, bar code algorithm, two-dimensional code algorithm;
wherein the fourth information may be any combination of one or more of the following: a payment result identifier, a terminal device identifier, a first request identifier, a ticket number, a ticket identifier, a payment method, a payment or collection media identifier, a payment amount, whether the payment or refund was successful.
The embodiment of the invention effectively resists the phenomenon of ticket rewinding and vending through ticket robbing software or different terminal equipment by limiting the generation and the sending of ticket purchase requests, ticket change requests and ticket visa requests, thereby improving the rationality of ticket resource allocation. And adding a random number into the first request, so as to effectively prevent replay attack.
Another embodiment of the present invention provides a terminal device, including a processor and a computer readable storage medium, where instructions are stored, and when the instructions are executed by the processor, implement any of the above ticket requesting methods.
Another embodiment of the present invention provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of any of the ticket requesting methods described above.
Referring to fig. 2, another embodiment of the present invention proposes a terminal device, including:
a first request generating module 201, configured to generate a first request when a first preset condition is satisfied;
alternatively, a first request is generated;
a first request sending module 202, configured to send a first request generated at this time to a ticket processing device or a ticket processing system;
or when the second preset condition is met, the first request generated at this time is sent to a ticket processing device or a ticket processing system;
or when the third preset condition is met, the first request generated at this time is sent to a ticket processing device or a ticket processing system;
wherein the first request includes any one of: ticket purchase request, ticket change request, ticket visa request;
The first preset condition comprises:
the time interval between the current time and the first timestamp in the first request generated last time is greater than or equal to a first preset threshold value;
the second preset condition or the third preset condition includes any combination of one or more of the following:
the time interval between the first time stamp in the first request generated at this time and the first time stamp in the first request generated last time is larger than or equal to a first preset threshold value;
the time interval between the current time and the time of the last transmitted first request is greater than or equal to a first preset threshold;
the number of tickets in the first request generated at this time is smaller than or equal to a second preset threshold value.
In another embodiment of the present invention, the terminal device further includes:
a receiving module 203, configured to receive a ticket processing result of the ticket processing device or the ticket processing system;
or receiving the state of the ticket corresponding to the first request or the result of incapability of processing of the ticket processing device or the ticket processing system;
the first request sending module 202 is further configured to: whether to continue sending the first request is determined according to the status of the ticket corresponding to the first request or the result that cannot be processed.
Wherein when the first request is a ticket purchase request, the ticket processing result includes any combination of one or more of:
ticket processing result identifier, terminal equipment identifier, first request identifier, passenger identity information, ticket number, ticket identifier, number of cars, origin station, destination station, boarding station, alighting station, transfer station, vehicle type, ticket type, date of taking bus, ticket number, whether processing is successful or not, ticket processing result verification code;
when the first request is a ticket change request, the ticket processing result includes any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the change, the origin before the change, the destination before the change, the transfer before the change, the upper station before the change, the lower station before the change, the type of the vehicle before the change, the type of the ticket before the change, the date of the train before the change, the number of tickets after the change, the origin after the change, the destination after the change, the upper station after the change, the lower station after the change, the transfer after the change, the type of the vehicle after the change, the type of the ticket after the change, the date of the train after the change, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code;
When the first request is a ticket visa request, the ticket processing result includes any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the visa, the starting station before the visa, the terminal station before the visa, the upper station before the visa, the lower station before the visa, the transfer station before the visa, the type of the vehicle before the visa, the type of the ticket before the visa, the date of taking the ticket before the visa, the number of tickets after the visa, the starting station after the visa, the terminal station after the visa, the upper station after the visa, the lower station after the visa, the transfer station after the visa, the type of the vehicle after the visa, the type of the ticket after the visa, the date of taking the visa, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code.
Wherein the status of the ticket includes any combination of one or more of the following:
ticket identifier, ticket vending status, passenger loading and unloading status, vehicle running status, ticket true and false status, financial reimbursement status;
wherein the sales status of the ticket includes any combination of one or more of the following:
Whether sold, paid, changed, number of changed, visa, printed, complemented, and refunded;
the passenger getting on/off status includes any combination of one or more of the following:
whether it has been inbound, whether it has been boarding, whether it has been disembarked, whether it has been outbound;
the operating state of the vehicle includes any combination of one or more of the following:
whether the train is launched, whether the train arrives at a boarding station, whether the train arrives at a disembarking station, whether the train is stopped, whether the train is rerouted, whether the train is late, and whether the train is normally operated;
the financial reimbursement status includes any combination of one or more of:
whether the transaction is reimbursed, whether the transaction is credited or not, and whether the transaction is filed or not;
the true and false states of the ticket include: whether the ticket is valid.
In another embodiment of the present invention, the terminal device further includes:
and the receiving module 203 is configured to receive a second request from the ticket processing device or the ticket processing system, pay, generate a payment result, and send the payment result to the ticket processing device or the ticket processing system.
Wherein when the first request is a ticket purchase request, the first request includes any combination of one or more of:
The method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a train number, a starting station, a terminal station, a boarding station, a disembarking station, a transfer station, a vehicle type, a ticket type, a riding date, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code;
when the first request is a ticket change request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, passenger identity information, a train number before a change, a starting station before a change, a terminal station before a change, a transfer station before a change, an upper station before a change, a lower station before a change, a train type before a change, a train ticket type before a change, a riding date before a change, a train number after a change, a starting station after a change, a terminal station after a change, an upper station after a change, a lower station after a change, a transfer station after a change, a train type after a change, a train ticket type after a change, a riding date after a change, a train ticket number, a first request content verification code, a random number, a first time stamp and a first request verification code;
when the first request is a ticket visa request, the first request includes any combination of one or more of:
The method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a number of vehicles before a visa, an originating station before a visa, a terminal station before a visa, a boarding station before a visa, a alighting station before a visa, a transfer station before a visa, a vehicle type before a visa, a ticket type before a visa, a date of taking a vehicle before a visa, a number of vehicles after a visa, an originating station after a visa, a terminal station after a visa, a boarding station after a visa, a alighting station after a visa, a transfer station after a visa, a vehicle type after a visa, a ticket type after a visa, a date of taking a vehicle after a visa, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code.
The specific implementation process of the terminal device is the same as that of the ticket processing method in the foregoing embodiment, and will not be described herein again.
Those of ordinary skill in the art will appreciate that all or some of the steps, systems, functional modules/units in the apparatus, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between the functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed cooperatively by several physical components. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
Although the embodiments of the present invention are described above, the embodiments are merely used for facilitating understanding of the embodiments of the present invention, and are not intended to limit the embodiments of the present invention. Any person skilled in the art can make any modification and variation in form and detail without departing from the spirit and scope of the embodiments of the invention, but the scope of the embodiments of the invention is defined by the appended claims.

Claims (8)

1. A ticket requesting method comprising:
when a first preset condition is met, a first request is generated, and the generated first request is sent to a ticket processing device or a ticket processing system;
or generating a first request, and when a second preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system;
or when the first preset condition is met, generating a first request, and when the third preset condition is met, sending the first request generated at this time to a ticket processing device or a ticket processing system;
wherein the first request includes any one of: ticket purchase request, ticket change request, ticket visa request;
The first preset condition comprises:
the time interval between the current time and the first timestamp in the first request generated last time is greater than or equal to a first preset threshold value;
the second preset condition or the third preset condition includes any combination of one or more of the following:
the time interval between the first time stamp in the first request generated at this time and the first time stamp in the first request generated last time is larger than or equal to a first preset threshold value;
the time interval between the current time and the time of the last transmitted first request is greater than or equal to a first preset threshold;
the number of tickets in the first request generated at this time is smaller than or equal to a second preset threshold value.
2. The method according to claim 1, characterized in that the method further comprises:
receiving ticket processing results of a ticket processing device or a ticket processing system;
or, receiving the status or the unprocessed result of the ticket corresponding to the first request of the ticket processing device or the ticket processing system, and determining whether to continue to send the first request according to the status or the unprocessed result of the ticket corresponding to the first request.
3. The method of claim 2, wherein when the first request is a ticket purchase request, the ticket processing results include any combination of one or more of:
Ticket processing result identifier, terminal equipment identifier, first request identifier, passenger identity information, ticket number, ticket identifier, number of cars, origin station, destination station, boarding station, alighting station, transfer station, vehicle type, ticket type, date of taking bus, ticket number, whether processing is successful or not, ticket processing result verification code;
when the first request is a ticket change request, the ticket processing result includes any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the change, the origin before the change, the destination before the change, the transfer before the change, the upper station before the change, the lower station before the change, the type of the vehicle before the change, the type of the ticket before the change, the date of the train before the change, the number of tickets after the change, the origin after the change, the destination after the change, the upper station after the change, the lower station after the change, the transfer after the change, the type of the vehicle after the change, the type of the ticket after the change, the date of the train after the change, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code;
When the first request is a ticket visa request, the ticket processing result includes any combination of one or more of the following:
the ticket processing result identifier, the terminal equipment identifier, the first request identifier, the passenger identity information, the number of tickets, the ticket identifier, the number of tickets before the visa, the starting station before the visa, the terminal station before the visa, the upper station before the visa, the lower station before the visa, the transfer station before the visa, the type of the vehicle before the visa, the type of the ticket before the visa, the date of taking the ticket before the visa, the number of tickets after the visa, the starting station after the visa, the terminal station after the visa, the upper station after the visa, the lower station after the visa, the transfer station after the visa, the type of the vehicle after the visa, the type of the ticket after the visa, the date of taking the visa, the number of tickets, whether the processing is successful or not, and the ticket processing result verification code.
4. The method of claim 2, wherein the status of the ticket comprises any combination of one or more of:
the ticket selling state, the passenger getting on/off state, the running state of the vehicle, the ticket true and false state and the financial reimbursement state;
wherein the sales status of the ticket includes any combination of one or more of the following:
Whether sold, paid, changed, number of changed, visa, printed, complemented, and refunded;
the passenger getting on/off status includes any combination of one or more of the following:
whether it has been inbound, whether it has been boarding, whether it has been disembarked, whether it has been outbound;
the operating state of the vehicle includes any combination of one or more of the following:
whether the train is launched, whether the train arrives at a boarding station, whether the train arrives at a disembarking station, whether the train is stopped, whether the train is rerouted, whether the train is late, and whether the train is normally operated;
the financial reimbursement status includes any combination of one or more of:
whether the transaction is reimbursed, whether the transaction is credited or not, and whether the transaction is filed or not;
the true and false states of the ticket include: whether the ticket is valid.
5. The method according to claim 1, characterized in that the method further comprises:
and receiving a second request of the ticket processing device or the ticket processing system, paying, generating a payment result and sending the payment result to the ticket processing device or the ticket processing system.
6. The method of any one of claims 1-5, wherein when the first request is a ticket purchase request, the first request comprises any combination of one or more of:
The method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a train number, a starting station, a terminal station, a boarding station, a disembarking station, a transfer station, a vehicle type, a ticket type, a riding date, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code;
when the first request is a ticket change request, the first request includes any combination of one or more of the following:
the method comprises the steps of a first request identifier, a terminal equipment identifier, passenger identity information, a train number before a change, a starting station before a change, a terminal station before a change, a transfer station before a change, an upper station before a change, a lower station before a change, a train type before a change, a train ticket type before a change, a riding date before a change, a train number after a change, a starting station after a change, a terminal station after a change, an upper station after a change, a lower station after a change, a transfer station after a change, a train type after a change, a train ticket type after a change, a riding date after a change, a train ticket number, a first request content verification code, a random number, a first time stamp and a first request verification code;
when the first request is a ticket visa request, the first request includes any combination of one or more of:
The method comprises the steps of a first request identifier, a terminal equipment identifier, driver identity information, a number of vehicles before a visa, an originating station before a visa, a terminal station before a visa, a boarding station before a visa, a alighting station before a visa, a transfer station before a visa, a vehicle type before a visa, a ticket type before a visa, a date of taking a vehicle before a visa, a number of vehicles after a visa, an originating station after a visa, a terminal station after a visa, a boarding station after a visa, a alighting station after a visa, a transfer station after a visa, a vehicle type after a visa, a ticket type after a visa, a date of taking a vehicle after a visa, a ticket number, a first request content verification code, a first timestamp, a random number and a first request verification code.
7. A terminal device comprising a processor and a computer readable storage medium having instructions stored therein, which when executed by the processor, implement the ticket requesting method of any one of claims 1 to 6.
8. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the ticket requesting method according to any of claims 1 to 6.
CN201911226413.0A 2019-12-04 2019-12-04 Ticket requesting method and device and computer readable storage medium Active CN111539869B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911226413.0A CN111539869B (en) 2019-12-04 2019-12-04 Ticket requesting method and device and computer readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911226413.0A CN111539869B (en) 2019-12-04 2019-12-04 Ticket requesting method and device and computer readable storage medium

Publications (2)

Publication Number Publication Date
CN111539869A CN111539869A (en) 2020-08-14
CN111539869B true CN111539869B (en) 2023-07-07

Family

ID=71978472

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911226413.0A Active CN111539869B (en) 2019-12-04 2019-12-04 Ticket requesting method and device and computer readable storage medium

Country Status (1)

Country Link
CN (1) CN111539869B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112418981A (en) * 2020-11-19 2021-02-26 杨晨鹏 Big data-based automatic ticket signing and returning system for wrong vehicle
CN113724409A (en) * 2021-07-23 2021-11-30 中国铁道科学研究院集团有限公司电子计算技术研究所 Ticket change method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103258351A (en) * 2012-02-15 2013-08-21 国民技术股份有限公司 Real-name system ticket purchasing method and real-name system ticketing system
CN103714487A (en) * 2013-12-19 2014-04-09 广东粤铁科技有限公司 Ticket system and ticket-buying and ticket-checking method thereof for rail transit
EP2924661A1 (en) * 2014-03-25 2015-09-30 Movincom Servizi S.p.A. Method for managing issue of an electronic ticket and corresponding system
CN106503823A (en) * 2016-11-14 2017-03-15 北京北纬通信科技股份有限公司 The anti-method and system for accounting for seat ticket booking are carried out based on the network platform

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3552637B2 (en) * 1993-03-15 2004-08-11 株式会社日立製作所 Reserved seat ticket inspection system
TWI512658B (en) * 2013-12-27 2015-12-11 To Link Inc A method for processing the ticket booking request signal
CN104268196B (en) * 2014-09-22 2018-10-30 广东粤铁科技有限公司 A kind of ticket library of ticketing system and its update method
CN105959392A (en) * 2016-06-14 2016-09-21 乐视控股(北京)有限公司 Page view control method and device
CN109657763A (en) * 2017-10-10 2019-04-19 方正国际软件(北京)有限公司 A kind of application method of electronic ticket and electronic ticket
CN110060124A (en) * 2019-04-10 2019-07-26 北京三快在线科技有限公司 Order processing method, apparatus, storage medium and electronic equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103258351A (en) * 2012-02-15 2013-08-21 国民技术股份有限公司 Real-name system ticket purchasing method and real-name system ticketing system
CN103714487A (en) * 2013-12-19 2014-04-09 广东粤铁科技有限公司 Ticket system and ticket-buying and ticket-checking method thereof for rail transit
EP2924661A1 (en) * 2014-03-25 2015-09-30 Movincom Servizi S.p.A. Method for managing issue of an electronic ticket and corresponding system
CN106503823A (en) * 2016-11-14 2017-03-15 北京北纬通信科技股份有限公司 The anti-method and system for accounting for seat ticket booking are carried out based on the network platform

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Smart E-Ticketing System for Public Transport Bus;Sanam Kazi;《 2018 International Conference on Smart City and Emerging Technology (ICSCET)》;全文 *
退改签票据审核质量和工作效率的思考;秦兆芳;;纳税(18);全文 *

Also Published As

Publication number Publication date
CN111539869A (en) 2020-08-14

Similar Documents

Publication Publication Date Title
CN109003058B (en) Method, device, system, equipment and storage medium for generating electronic payment certificate
CN108510276B (en) Data processing method, device and system
CN110838047B (en) Network taxi driver credit management method and device, server and storage medium
WO2019165669A1 (en) Method for preventing bank card fraud, apparatus, computer device and storage medium
CN111539869B (en) Ticket requesting method and device and computer readable storage medium
CN101706933A (en) Method and background system for realizing joint account service operation
CN110751448B (en) Block chain based sign-off return method, device, equipment and readable storage medium
CN110866755A (en) Processing method, equipment and medium for bill data
CN111199461B (en) Unmanned vehicle passenger carrying method based on blockchain and unmanned vehicle
CN104867040A (en) Generation method and systems for taxi electronic invoices
CN111125778A (en) Copyright transaction information processing method and device
CN107527265A (en) A kind of check-out method
CN112002023A (en) Electronic ticket generating method, ticket checking method, electronic device and storage medium
CN110059943A (en) A kind of method, apparatus dispatched buses, equipment and storage medium
CN109657763A (en) A kind of application method of electronic ticket and electronic ticket
CN114792228A (en) Business handling method, device, equipment and medium
CN111598502A (en) Block chain-based waybill processing method, system, equipment and storage medium
CN111539703B (en) Payment exception handling method and system
CN111612564B (en) Ticket processing method and device and computer readable storage medium
CN104036416A (en) Personal identity card ticket-purchasing management system
JP6368261B2 (en) Authentication system and authentication method
CN105095974A (en) Ticket allocation method and apparatus
CN115205038A (en) Block chain cross-chain financial method, device, terminal and storage medium
CN109559107B (en) Shared vehicle settlement exception handling method, vehicle, server, device and system
CN110798320B (en) Vehicle information sharing method and device and vehicle-mounted equipment

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