CN114091714A - Passenger ticket filling control method and device - Google Patents
Passenger ticket filling control method and device Download PDFInfo
- Publication number
- CN114091714A CN114091714A CN202210063930.6A CN202210063930A CN114091714A CN 114091714 A CN114091714 A CN 114091714A CN 202210063930 A CN202210063930 A CN 202210063930A CN 114091714 A CN114091714 A CN 114091714A
- Authority
- CN
- China
- Prior art keywords
- rule
- ticket
- request
- module
- filling
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 101
- 230000007246 mechanism Effects 0.000 claims description 31
- 238000006243 chemical reaction Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 description 53
- 238000007726 management method Methods 0.000 description 31
- 239000003795 chemical substances by application Substances 0.000 description 21
- 238000012545 processing Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 10
- 238000004590 computer program Methods 0.000 description 8
- 230000003287 optical effect Effects 0.000 description 6
- 230000003993 interaction Effects 0.000 description 4
- 238000012550 audit Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/02—Reservations, e.g. for tickets, services or events
-
- G06Q50/40—
Abstract
The application discloses a method and a device for controlling ticket filling. In the technical scheme of the application, the rule matching module receives a passenger ticket filling request provided by the interface module; the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set; and the rule matching module sends a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set. According to the method and the device, the ticket filling request provided by the interface module is received through the rule matching module, and the ticket filling request is matched, so that the ticket filling operation is effectively controlled, and the service management loophole caused by invalid ticket filling control in the air ticket sales flow is avoided.
Description
Technical Field
The application relates to the technical field of data processing, in particular to a passenger ticket filling control method and device.
Background
In the prior art, the complete air ticket selling process comprises the following steps: flight reservation and ticket filling are carried out, and the management and control appeal of an airline company to a sales organization needs to be covered in the two links.
In a flight booking link, a computer booking system has a so-called blacklist function, supports an airline company to set a blacklist in a sales terminal rule form, and is used for punishing an illegal sales agent and controlling the business of the illegal sales agent.
However, in the passenger ticket filling-out link, for the illegal sales agent, the computer booking system limits the flight booking operation but cannot limit the passenger ticket filling-out operation, so that the sales agents can be matched in different links, and the sales agent who should limit the passenger ticket filling-out authority still participates in completing the air ticket sales process. For example, the sales agent with limited operation of the flight booking link is responsible for completing the operation of the passenger ticket filling link, and the sales agent with unlimited operation of the flight booking link is responsible for completing the operation of the flight booking link. Therefore, the effective business control of the sales agent is not achieved in the passenger ticket filling link, so that management loopholes in business occur.
Disclosure of Invention
Based on the above problems, the application provides a passenger ticket filling control method and device, so as to solve the problem of service management loopholes caused by the fact that the passenger ticket filling operation is not controlled.
The embodiment of the application discloses the following technical scheme:
in a first aspect, the present application provides a method for controlling ticket filling, comprising:
the rule matching module receives a passenger ticket filling request provided by the interface module;
the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set;
and the rule matching module sends a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set.
In a second aspect, the present application provides a ticket refill control apparatus comprising: a rule matching module and an interface module;
the rule matching module is used for receiving a passenger ticket filling request provided by the interface module;
the rule matching module is also used for carrying out rule matching on the passenger ticket filling request and the passenger ticket filling limiting rule in the rule set;
the rule matching module is also used for sending a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set;
the interface module is used for receiving the control signal which is sent by the rule matching module and indicates permission or prohibition.
Compared with the prior art, the method has the following beneficial effects:
in the technical scheme of the application, a rule matching module is used for receiving a ticket filling request provided by an interface module, the rule matching module carries out rule matching on the ticket filling request and a ticket filling limiting rule in a rule set, and if the ticket filling request is successfully matched with any ticket filling limiting rule in the rule set, the rule matching module sends a control signal for indicating prohibition to the interface module; if the ticket fill request matches successfully with all of the ticket fill restriction rules in the rule set, the rule matching module sends a control signal to the interface module indicating permission. Therefore, the ticket filling-out request provided by the interface module is received by the rule matching module and matched, so that the ticket filling-out operation is effectively controlled, and the service management loophole caused by invalid ticket filling-out control in the air ticket selling process is avoided.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
FIG. 1 is a flowchart of a method for controlling ticket filling according to an embodiment of the present disclosure;
FIG. 2 is a schematic connection diagram of a plurality of modules in a ticket filling control method according to an embodiment of the present application;
FIG. 3 is an interactive signaling diagram of a plurality of modules in a ticket filling control method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an architecture of a ticket filling control device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
First, meanings of terms that may be referred to in the present specification are described.
Computer Reservation System (CRS): computer Reservation System (CRS) refers to a computer system that provides flight schedule time, space availability information, fare and related service information, and supports flight booking or ticket filling through the system.
Air ticket selling process: a complete air ticket selling process comprises the following steps: flight reservation and passenger ticket filling.
And (3) ticket filling: in a computer reservation system, the operation of generating an electronic ticket based on a reservation record for a traveler.
And (3) changing the passenger ticket: in a computer booking system, the operation of changing one electronic ticket (old ticket) to another electronic ticket (new ticket).
E-ticket: an electronic record is provided to the traveler that serves as a shipping voucher. By means of the electronic ticket, the passenger can handle the procedure of taking the airplane and take the flight, and the purpose of going out is achieved.
The data items of the E-ticket include: ticket number, sales organization, passenger name, passenger identity document information, flight segment, ticket connection state and other data.
Flight booking: the process of reserving the seat of the flight and generating the reservation record for the passenger according to the will of the passenger in the online air ticket selling system by the personnel of the air ticket selling mechanism or the air ticket selling mechanism.
And (3) predetermined recording: after the flight reservation is successful, an electronic record is generated at the computer reservation system.
The data items of the predetermined record include: passenger name, passenger identity card information, flight legs, freight rate information, sales organization, etc.
And (3) passenger ticket filling control: airlines, based on their administrative intents, prohibit ticket fill operations for certain reservation records in a computer reservation system for certain sales organizations.
Sales agent: obtain the authorization of the airline company and provide the ticket sale service enterprises/institutions for passengers. The sales agent may perform flight booking, ticket filling, etc. operations in the computer booking system.
Agent for filling passenger ticket: the sales agents for both the flight booking and ticket filling links may not be the same. Therefore, the ticket fill agent is used to refer specifically to a sales agent who performs a ticket fill operation.
Method embodiment
Referring to fig. 1, it is a flowchart of a method for controlling ticket filling according to an embodiment of the present application.
As shown in fig. 1, the method for controlling ticket filling provided in this embodiment includes:
step 101: the rule matching module receives the ticket filling request provided by the interface module.
In the embodiment of the application, the interface module receives an original ticket filling control request sent by a computer booking system, then the interface module sends the ticket filling request to the rule matching module, and finally the rule matching module is responsible for receiving the ticket filling request from the interface module.
Step 102: and the rule matching module is used for carrying out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set.
Note that the ticket issuing agency information includes a predetermined system code, office number, pc number, iata number, city, country, and region. It will be appreciated that the ticket filling authority information uniquely characterizes the ticket filling authority. If the ticket fill mechanism information in the request is consistent with the ticket fill mechanism information in the rule, it indicates that the mechanism is restricted from ticket fill in the rule. It can be understood that the rule matching module compares the received regularized ticket filling request with each rule in the rule set cached in the module one by one. The integral matching process of the execution rule is that if the rule is matched with the audit module, the rule matching module outputs a prohibition signal to the interface module, and the interface module sends a log record to the audit module; if not, continuing to match the next rule until all the rules are not matched, outputting an allowing signal to the interface module by the rule matching module, and sending a log record to the auditing module by the interface module.
TABLE 1 structural schematic table of single ticket fill-in restriction rules
As shown in table 1, the matching process for a single rule is as follows:
(1) comparing the current actual date and time with the effective date and the expiration date in the ticket filling limit rule:
if the rule does not fall into the interval, the result is that the rule is not matched, the matching process is ended, and if the rule falls into the interval, the following matching process is continued.
(2) Comparing the ticket filling mechanism in the normalized ticket filling request with the ticket filling mechanism in the ticket filling limit rule: specifically, the information of the passenger ticket filling mechanism is compared;
(3) Comparing the reservation record in the normalized ticket filling request with the reservation record in the ticket filling restriction rule:
If the above matching processes are all consistent, the result is a match, and the ticket fill operation of the sales agent is restricted. It should be noted that, the three comparison and matching processes of comparing the current actual date and time with the effective date and the ineffective date intervals in the ticket fill-up restriction rule, comparing the ticket fill-up mechanism in the normalized ticket fill-up request with the ticket fill-up mechanism in the ticket fill-up restriction rule, and comparing the predetermined record in the normalized ticket fill-up request with the predetermined record in the ticket fill-up restriction rule can be arbitrarily matched, only considering the problem of execution efficiency in this embodiment, so the above steps are adopted for matching.
Step 103: and the rule matching module sends a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set.
According to the step 102, the rule matching module may send a control signal indicating permission or prohibition to the interface module according to a matching result of the ticket fill-in request and the ticket fill-in restriction rule in the rule set, and it is understood that if the ticket fill-in request is successfully matched with any ticket fill-in restriction rule in the rule set, the rule matching module sends a control signal indicating prohibition to the interface module; if the ticket fill request matches successfully with all of the ticket fill restriction rules in the rule set, the rule matching module sends a control signal to the interface module indicating permission.
The above is a method for controlling ticket filling provided by the embodiment of the application. The method utilizes a rule matching module to receive a passenger ticket filling request provided by an interface module; the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set; and the rule matching module sends a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set. According to the method and the device, the ticket filling request provided by the interface module is received through the rule matching module, and the ticket filling request is matched, so that the ticket filling operation is effectively controlled, and the service management loophole caused by invalid ticket filling control in the air ticket sales flow is avoided. In practical application, since the computer booking system does not perform service control on the sales agent performing the ticket filling operation, there may be a service leak that the sales agent performing the service control performs flight booking and performs ticket filling on the sales agent performing the service control. To better fulfill the complete management intent of the airline, the following description is made in conjunction with the embodiments and the accompanying drawings.
Referring to fig. 2, the figure is a schematic connection diagram of a plurality of modules in the passenger ticket filling control method according to the embodiment of the present application.
In the method provided in the embodiment of the present application, as shown in table 2, the rule management module provides a human-computer interaction interface and a rule change notification, and a rule administrator performs management operations such as adding, deleting, modifying, and checking rules through the human-computer interaction interface provided by the rule management module, and after any change occurs to a rule, the module sends a rule update notification to the rule matching module.
TABLE 2 complete structure of a ticket fill restriction rule
It can be understood that, as shown in table 3, in an example, the rule administrator may add, on the rule management interface on the human-computer interaction page, rules such as restricting HSY888 ticket filling out jinghu lines, restricting european agent ticket filling out china national air channels, and the like, specifically, the sales agent (HSY 888) has an illegal operation, the airline punishments the illegal operation, and prohibits part of ticket filling out behavior, and the corresponding restriction rule is ticket filling out agency information: office number: HSY 888; and (3) predetermined recording: flight: Beijing-Shanghai route, cabin space: KLMNQ, etc. low-price discount cabin, flight date: all dates, penalty period: from 9/1/2021 to 12/31/2021. In another example, airlines temporarily prohibit all agents in europe from filling in e-tickets containing china's home leg in order to reduce their commission expenditure because of the commission rate differences. The corresponding restriction rule is the information of the passenger ticket filling mechanism: the area is as follows: europe; and (3) predetermined recording: flight: china domestic flight segment, flight date: 1/10/2021 to 7/10/2021, cabin space: all, penalty period: 9/1/2021 to 10/4/2021.
TABLE 3 schematic representation of two restriction rules
In the method provided in the embodiment of the present application, the rule matching module is responsible for implementing a ticket fill-out control decision, and specifically, receives a normalized ticket fill-out request and outputs a control signal, where as shown in table 4, a complete structure of a normalized ticket fill-out request includes ticket fill-out mechanism information and reservation records, the ticket fill-out mechanism information includes a reservation system code, an office number, a pc number, an iata number, a city, and a country, and the reservation records include a flight number, a slot, a flight date, a departure airport, an arrival airport, a departure time, an arrival time, a departure city, an arrival city, a departure country, and an arrival country. The control signal is divided into a prohibition signal and a permission signal, the calculation process of the control signal is to match the ticket filling request with the ticket filling restriction rule set, and if the matching is found, the prohibition signal is output; if no match is found, a permission signal is output.
It should be noted that, the ticket used in the matching process fills the restriction rule set, which is a rule set cached in the module, and the rule set is obtained and updated by the rule matching module, after receiving the rule update notification, the rule matching module performs a rule query on the rule storage module, and the queried rule set is cached in the module, thereby avoiding frequent access to the storage module.
TABLE 4A complete structure for regularizing ticket fill-out requests
In the method provided by the embodiment of the application, the interface module is responsible for butting a computer booking system, providing an interface function and receiving an original ticket filling control request sent by the computer booking system, and after carrying out regularization processing, obtaining a regularized ticket filling request and submitting the regularized ticket filling request to the rule matching module; and the system is responsible for receiving the response of the rule matching module and forwarding the response to the computer booking system, wherein as shown in table 5, the complete structure of an original ticket filling control request comprises ticket filling mechanism information and a reservation record, the ticket filling mechanism information comprises a reservation system code, an office number, a pc number, an iata number and a city, and the reservation record comprises a flight number, a cabin position, a flight date, a departure airport, an arrival airport, a departure time and an arrival time.
TABLE 5 complete structural schematic table of original ticket fill-in control request
The interface module carries out regularization processing on the original ticket filling control request, and can be understood that the interface module firstly processes the ticket filling mechanism information of the original ticket filling control request, for example, a city is taken as a keyword, and a basic data city table is inquired to obtain a country; then processing a predetermined record of the original ticket opening control request, for example, taking the departure airport as a keyword, and inquiring a basic data airport table to obtain a departure city; inquiring a basic data city table by taking the starting city as a keyword to obtain a starting country; inquiring a basic data airport table by taking an arrival airport as a keyword to obtain an arrival city; inquiring a basic data city table by taking the arriving city as a keyword to obtain the arriving country; and finally, obtaining a regularized ticket filling request after the processing.
In the method provided by the embodiment of the application, the auditing module is responsible for receiving the log records and storing the log records. Each log record includes a request for ticket fill control and control signals for post-audit verification.
In the method provided in the embodiment of the present application, the rule storage module is responsible for storing all the ticket fill-in restriction rules, and supports addition, deletion, modification, and check of the ticket fill-in restriction rules, where as shown in table 6, a complete structure of one ticket fill-in restriction rule in the rule storage module includes a ticket fill-in mechanism, a reservation record, and a rule validity period, information of the ticket fill-in mechanism includes a reservation system code, an office number, a pc number, an iata number, a city, a country, and an area, the reservation record includes a flight number, a slot, a flight date, a departure airport, an arrival airport, a departure time, an arrival time, a departure city and an arrival city, a departure country, an arrival country, a departure area, and an arrival area, the rule validity period includes a validity date and a expiration date, and it is required to say that management information of the rule can also be checked in the rule storage module.
TABLE 6 complete structural schematic table of ticket fill restriction rules in rule storage module
Referring to fig. 3, the figure is an interactive signaling diagram of a plurality of modules in the passenger ticket filling control method according to the embodiment of the present application.
As shown in fig. 3, the method includes:
the rule matching module updates the rules, and can be understood that a rule administrator adds, deletes, modifies and the like the rules through a human-computer interaction interface of the rule management module, the rule storage module receives the adding, deleting and modifying operations of the ticket filling limit rules, the ticket filling limit rules are persistently stored in the rule storage module for later use, the rule storage module returns the information of successful storage, the rule management module sends a rule updating notice to the rule matching module after receiving the information of successful storage, the rule matching module sends a query request to the rule storage module after receiving the rule updating notice, the rule storage module returns the rule query results which contain all the currently effective rules, the rule matching module receives the rule query results and caches the query results in the rule storage module, for later use.
Processing a ticket filling control request, wherein the interface module receives an original ticket filling control request sent by a computer booking system, the interface module performs regularization processing on the received original ticket filling control request to obtain a regularized ticket filling request, the interface module sends the regularization request to a rule matching module, the rule matching module performs rule matching on the ticket filling request and a rule set cached in the module, and if the result is matching, a prohibition signal is output; if the result is not matched, a permission signal is output, the interface module receives a signal sent by the rule matching module, the interface module forwards the received signal to the computer booking system, the interface module sends a log to the auditing module, the content of the log comprises a ticket filling control request received by the interface module and a control signal sent by the interface module, and the auditing module stores the log after receiving the log for later use.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information. Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
Based on the method for controlling the ticket filling, the application also provides a device for controlling the ticket filling. The following description is made with reference to the embodiments and the accompanying drawings.
Device embodiment
Referring to fig. 4, it is a schematic diagram of an architecture of a ticket filling control device according to an embodiment of the present application.
As shown in fig. 4, the apparatus includes a rule matching module 401, an interface module 402:
the rule matching module is used for receiving a passenger ticket filling request provided by the interface module;
the rule matching module is also used for carrying out rule matching on the passenger ticket filling request and the passenger ticket filling limiting rule in the rule set;
the rule matching module is also used for sending a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set;
and the interface module is used for receiving the control signal which is sent by the rule matching module and indicates permission or prohibition.
With the device, the ticket filling request provided by the interface module is received by using the rule matching module, and the ticket filling request is matched, so that the ticket filling is controlled.
Optionally, the rule matching module 401 specifically includes:
a first sending unit, configured to, when the ticket fill-in request is successfully matched with any ticket fill-in restriction rule in the rule set, send a control signal indicating prohibition to the interface module by the rule matching module;
a second sending unit, configured to, when the ticket fill-in request fails to match all ticket fill-in restriction rules in the rule set, send a control signal indicating permission to the interface module by the rule matching module;
the passenger ticket filling request and the passenger ticket filling limiting rule comprise passenger ticket filling mechanism information and a preset record; the ticket fill restriction rule further comprises: a rule validity period;
a first determining unit, configured to determine that the ticket fill-out request and the ticket fill-out restriction rule are successfully matched when the current date is within the rule validity period, the ticket fill-out request and the ticket fill-out mechanism information in the ticket fill-out restriction rule are successfully matched, and the ticket fill-out request and the reservation record in the ticket fill-out restriction rule are successfully matched;
a second determining unit, configured to determine that the ticket fill-out request and the ticket fill-out restriction rule fail to match when the current date is not within the rule validity period, or the ticket fill-out request fails to match ticket fill-in mechanism information in the ticket fill-out restriction rule, or the ticket fill-out request fails to match a predetermined record in the ticket fill-out restriction rule.
Optionally, the interface module 402 specifically includes: the device comprises a request receiving unit, an information regularization unit, a forwarding unit and a log generation unit;
the request receiving unit is used for receiving an original ticket filling control request provided by the computer booking system;
the information regularization unit is used for regularizing the information in the original ticket filling control request according to a preset information conversion relation to obtain the ticket filling request;
the forwarding unit is used for forwarding the control signal to a computer booking system;
the log generating unit is used for generating a log according to the passenger ticket filling request and the control signal;
the device further comprises: and the auditing module is used for receiving the log sent by the interface module.
The architecture of a ticket filling control device comprising an auditing module, a rule storage module and a rule management module is described with reference to fig. 2. As shown in fig. 2, the apparatus may include: the rule matching module and the interface module can also comprise a rule management module, an auditing module and a rule storage module:
the rule management module is used for responding to user operation and managing the ticket filling limit rule;
the rule management module is further configured to send a rule update notification message to the rule matching module according to the information that the storage is successful;
the rule storage module is used for receiving a management instruction of the rule management module, storing rules in the rule storage module, and sending information of successful storage to the rule management module after the storage is finished;
the rule storage module is further configured to return a rule set query result of the updated rule set to the rule matching module according to the rule set query request;
and the auditing module is used for receiving the log sent by the interface module.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
Referring now to fig. 5, shown is a schematic diagram of an electronic device 600 suitable for use in implementing embodiments of the disclosed apparatus. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 5, the electronic device 600 may include a processing means (e.g., a central processing unit, a graphic processing unit, etc.) 601, i.e., a ticket fill control means described in the above embodiments, which may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage device 606 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 606 including, for example, magnetic tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 5 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
The embodiment of the application is based on the method and the device introduced in the foregoing text, and accordingly, a computer-readable storage medium is also provided.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a passenger ticket filling request provided by an interface module;
carrying out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set;
and sending a control signal indicating permission or prohibition to the interface module according to a matching result of the ticket filling request and the ticket filling limiting rule in the rule set.
Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a passenger ticket filling request provided by an interface module;
carrying out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set;
and sending a control signal indicating permission or prohibition to the interface module according to a matching result of the ticket filling request and the ticket filling limiting rule in the rule set.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
Based on the method, the device and the storage medium provided by the foregoing embodiments, correspondingly, the present application also provides a computer program product.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such embodiments, the computer program may be downloaded and installed from a network through the communication device 609, or installed from the storage device 606, or installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
According to one or more embodiments of the present disclosure, there is provided a ticket fill control method, the method including:
the rule matching module receives a passenger ticket filling request provided by the interface module;
the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set;
and the rule matching module sends a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set.
Optionally, the rule matching module sends a control signal indicating permission or prohibition to the interface module according to a matching result between the ticket filling request and the ticket filling restriction rule in the rule set, where the control signal includes:
when the ticket filling request is successfully matched with any ticket filling limiting rule in the rule set, the rule matching module sends a control signal indicating prohibition to the interface module;
when the ticket filling request fails to match all the ticket filling limiting rules in the rule set, the rule matching module sends a control signal indicating permission to the interface module.
Optionally, the ticket filling request and the ticket filling restriction rule both include ticket filling mechanism information and a reservation record; the ticket fill restriction rule further comprises: a rule validity period;
the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set, and the rule matching module comprises the following steps:
when the current date is within the validity period of the rule, the ticket filling request is successfully matched with the ticket filling mechanism information in the ticket filling limiting rule, and the ticket filling request is successfully matched with the predetermined record in the ticket filling limiting rule, the ticket filling request and the ticket filling limiting rule are successfully matched;
and when the current date is not within the validity period of the rule, or the matching of the ticket filling request and the ticket filling mechanism information in the ticket filling limiting rule fails, or the matching of the ticket filling request and the predetermined record in the ticket filling limiting rule fails, determining that the matching of the ticket filling request and the ticket filling limiting rule fails.
Optionally, before the rule matching module receives a ticket filling request provided by the interface module, the method further includes:
the interface module receives an original ticket filling control request provided by a computer booking system;
and the interface module normalizes the information in the original ticket filling control request according to a preset information conversion relation to obtain the ticket filling request.
Optionally, the method further comprises:
and the interface module forwards the control signal to a computer booking system.
Optionally, the method further comprises:
the interface module generates a log according to the passenger ticket filling request and the control signal;
and the interface module sends the log to an auditing module.
Optionally, the method further comprises:
the rule management module responds to user operation and manages the ticket filling limit rule;
the rule storage module receives a management instruction of the rule management module, stores the rule in the rule storage module, and sends information of successful storage to the rule management module after the storage is finished;
the rule management module sends a rule updating notification message to the rule matching module according to the information of successful storage;
the rule matching module sends a rule set query request to the rule storage module according to the rule updating notification message;
the rule storage module returns a rule set query result of the updated rule set to the rule matching module according to the rule set query request;
the rule matching module caches the updated rule set inside the rule matching module.
According to one or more embodiments of the present disclosure, there is provided a ticket fill control apparatus including: a rule matching module and an interface module;
the rule matching module is used for receiving a passenger ticket filling request provided by the interface module;
the rule matching module is also used for carrying out rule matching on the passenger ticket filling request and the passenger ticket filling limiting rule in the rule set;
the rule matching module is also used for sending a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set;
the interface module is used for receiving the control signal which is sent by the rule matching module and indicates permission or prohibition.
Optionally, the rule matching module specifically includes:
a first sending unit, configured to, when the ticket fill-in request is successfully matched with any ticket fill-in restriction rule in the rule set, send a control signal indicating prohibition to the interface module by the rule matching module;
and the second sending unit is used for sending a control signal indicating permission to the interface module by the rule matching module when the ticket filling request fails to be matched with all the ticket filling limiting rules in the rule set.
Optionally, the ticket filling request and the ticket filling restriction rule both include ticket filling mechanism information and a reservation record; the ticket fill restriction rule further comprises: a rule validity period;
the rule matching module specifically comprises:
a first determining unit, configured to determine that the ticket fill-out request and the ticket fill-out restriction rule are successfully matched when the current date is within the rule validity period, the ticket fill-out request and the ticket fill-out mechanism information in the ticket fill-out restriction rule are successfully matched, and the ticket fill-out request and the reservation record in the ticket fill-out restriction rule are successfully matched;
a second determining unit, configured to determine that the ticket fill-out request and the ticket fill-out restriction rule fail to match when the current date is not within the rule validity period, or the ticket fill-out request fails to match ticket fill-in mechanism information in the ticket fill-out restriction rule, or the ticket fill-out request fails to match a predetermined record in the ticket fill-out restriction rule.
Optionally, the interface module further includes a request receiving unit and an information regularization unit;
the request receiving unit is used for receiving an original ticket filling control request provided by the computer booking system;
and the information regularization unit is used for regularizing the information in the original ticket filling control request according to a preset information conversion relation to obtain the ticket filling request.
Optionally, the interface module further includes a forwarding unit; the forwarding unit is used for forwarding the control signal to a computer booking system.
Optionally, the interface module further includes a log generating unit, and the log generating unit is configured to generate a log according to the ticket filling request and the control signal;
the device further comprises: and the auditing module is used for receiving the log sent by the interface module.
Optionally, the apparatus further comprises: the rule management module and the rule storage module;
the rule management module is used for responding to user operation and managing the ticket filling limit rule;
the rule storage module is used for receiving a management instruction of the rule management module, storing rules in the rule storage module, and sending information of successful storage to the rule management module after the storage is finished;
the rule management module is further configured to send a rule update notification message to the rule matching module according to the information that the storage is successful;
the rule matching module is further used for sending a rule set query request to the rule storage module according to the rule update notification message;
the rule storage module is further configured to return a rule set query result of the updated rule set to the rule matching module according to the rule set query request;
the rule matching module is further configured to cache the updated rule set in the rule matching module.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Claims (14)
1. A passenger ticket opening control method is characterized by comprising the following steps:
the rule matching module receives a passenger ticket filling request provided by the interface module;
the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set;
and the rule matching module sends a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set.
2. The method of claim 1, wherein the rule matching module sends a control signal indicating permission or prohibition to the interface module according to a matching result of the ticket fill request with a ticket fill restriction rule in the rule set, comprising:
when the ticket filling request is successfully matched with any ticket filling limiting rule in the rule set, the rule matching module sends a control signal indicating prohibition to the interface module;
when the ticket filling request fails to match all the ticket filling limiting rules in the rule set, the rule matching module sends a control signal indicating permission to the interface module.
3. The method of claim 1 wherein said ticket fill request and said ticket fill restriction rules each comprise ticket fill authority information and a reservation record; the ticket fill restriction rule further comprises: a rule validity period;
the rule matching module carries out rule matching on the ticket filling request and the ticket filling limiting rule in the rule set, and the rule matching module comprises the following steps:
when the current date is within the validity period of the rule, the ticket filling request is successfully matched with the ticket filling mechanism information in the ticket filling limiting rule, and the ticket filling request is successfully matched with the predetermined record in the ticket filling limiting rule, the ticket filling request and the ticket filling limiting rule are successfully matched;
and when the current date is not within the validity period of the rule, or the matching of the ticket filling request and the ticket filling mechanism information in the ticket filling limiting rule fails, or the matching of the ticket filling request and the predetermined record in the ticket filling limiting rule fails, determining that the matching of the ticket filling request and the ticket filling limiting rule fails.
4. A method according to any of claims 1-3, wherein before the rule matching module receives a ticket fill request provided by an interface module, the method further comprises:
the interface module receives an original ticket filling control request provided by a computer booking system;
and the interface module normalizes the information in the original ticket filling control request according to a preset information conversion relation to obtain the ticket filling request.
5. The method according to any one of claims 1-3, further comprising:
and the interface module forwards the control signal to a computer booking system.
6. The method according to any one of claims 1-3, further comprising:
the interface module generates a log according to the passenger ticket filling request and the control signal;
and the interface module sends the log to an auditing module.
7. The method according to any one of claims 1-3, further comprising:
the rule management module responds to user operation and manages the ticket filling limit rule;
the rule storage module receives a management instruction of the rule management module, stores the rule in the rule storage module, and sends information of successful storage to the rule management module after the storage is finished;
the rule management module sends a rule updating notification message to the rule matching module according to the information of successful storage;
the rule matching module sends a rule set query request to the rule storage module according to the rule updating notification message;
the rule storage module returns a rule set query result of the updated rule set to the rule matching module according to the rule set query request;
the rule matching module caches the updated rule set inside the rule matching module.
8. A ticket refill control device, comprising: a rule matching module and an interface module;
the rule matching module is used for receiving a passenger ticket filling request provided by the interface module;
the rule matching module is also used for carrying out rule matching on the passenger ticket filling request and the passenger ticket filling limiting rule in the rule set;
the rule matching module is also used for sending a control signal indicating permission or prohibition to the interface module according to the matching result of the ticket filling request and the ticket filling limiting rule in the rule set;
the interface module is used for receiving the control signal which is sent by the rule matching module and indicates permission or prohibition.
9. The apparatus according to claim 8, wherein the rule matching module specifically includes:
a first sending unit, configured to, when the ticket fill-in request is successfully matched with any ticket fill-in restriction rule in the rule set, send a control signal indicating prohibition to the interface module by the rule matching module;
and the second sending unit is used for sending a control signal indicating permission to the interface module by the rule matching module when the ticket filling request fails to be matched with all the ticket filling limiting rules in the rule set.
10. The apparatus of claim 8 wherein said ticket fill request and said ticket fill restriction rules each comprise ticket fill authority information and a reservation record; the ticket fill restriction rule further comprises: a rule validity period;
the rule matching module specifically comprises:
a first determining unit, configured to determine that the ticket fill-out request and the ticket fill-out restriction rule are successfully matched when the current date is within the rule validity period, the ticket fill-out request and the ticket fill-out mechanism information in the ticket fill-out restriction rule are successfully matched, and the ticket fill-out request and the reservation record in the ticket fill-out restriction rule are successfully matched;
a second determining unit, configured to determine that the ticket fill-out request and the ticket fill-out restriction rule fail to match when the current date is not within the rule validity period, or the ticket fill-out request fails to match ticket fill-in mechanism information in the ticket fill-out restriction rule, or the ticket fill-out request fails to match a predetermined record in the ticket fill-out restriction rule.
11. The apparatus according to any one of claims 8-10, wherein the interface module further comprises a request receiving unit and an information regularization unit;
the request receiving unit is used for receiving an original ticket filling control request provided by the computer booking system;
and the information regularization unit is used for regularizing the information in the original ticket filling control request according to a preset information conversion relation to obtain the ticket filling request.
12. The apparatus according to any of claims 8-10, wherein the interface module further comprises a forwarding unit; the forwarding unit is used for forwarding the control signal to a computer booking system.
13. The apparatus according to any one of claims 8-10, wherein the interface module further comprises a log generation unit for generating a log according to the ticket filling request and the control signal;
the device further comprises: and the auditing module is used for receiving the log sent by the interface module.
14. The apparatus according to any one of claims 8-10, further comprising: the rule management module and the rule storage module;
the rule management module is used for responding to user operation and managing the ticket filling limit rule;
the rule storage module is used for receiving a management instruction of the rule management module, storing rules in the rule storage module, and sending information of successful storage to the rule management module after the storage is finished;
the rule management module is further configured to send a rule update notification message to the rule matching module according to the information that the storage is successful;
the rule matching module is further used for sending a rule set query request to the rule storage module according to the rule update notification message;
the rule storage module is further configured to return a rule set query result of the updated rule set to the rule matching module according to the rule set query request;
the rule matching module is further configured to cache the updated rule set in the rule matching module.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210063930.6A CN114091714A (en) | 2022-01-20 | 2022-01-20 | Passenger ticket filling control method and device |
| PCT/CN2022/087623 WO2023137890A1 (en) | 2022-01-20 | 2022-04-19 | Passenger ticket filling control method and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210063930.6A CN114091714A (en) | 2022-01-20 | 2022-01-20 | Passenger ticket filling control method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114091714A true CN114091714A (en) | 2022-02-25 |
Family
ID=80308931
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210063930.6A Pending CN114091714A (en) | 2022-01-20 | 2022-01-20 | Passenger ticket filling control method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114091714A (en) |
| WO (1) | WO2023137890A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023137890A1 (en) * | 2022-01-20 | 2023-07-27 | 中国民航信息网络股份有限公司 | Passenger ticket filling control method and apparatus |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030158811A1 (en) * | 2001-07-18 | 2003-08-21 | Ventanex | System and method for rules based electronic funds transaction processing |
| CN108305134A (en) * | 2017-01-13 | 2018-07-20 | 阿里巴巴集团控股有限公司 | A kind of safety detection method, equipment and the system of air ticket order |
| CN109949140A (en) * | 2017-12-18 | 2019-06-28 | 航天信息股份有限公司 | The method and device that generation draws a bill |
| US20200387976A1 (en) * | 2019-06-06 | 2020-12-10 | Salus Finance, LLC | System and Method for Consolidation, Reconciliation and Payment Management |
| CN113590683A (en) * | 2021-07-22 | 2021-11-02 | 福建博思软件股份有限公司 | Multi-dimensional electronic bill suspicious ticket comprehensive monitoring and analyzing method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180218438A1 (en) * | 2017-02-01 | 2018-08-02 | Oracle International Corporation | System and method for database querying and matching at parent item level |
| CN112016981A (en) * | 2020-07-23 | 2020-12-01 | 南京领行科技股份有限公司 | Electronic invoice issuing method and device, electronic equipment and readable storage medium |
| CN112966845A (en) * | 2021-03-10 | 2021-06-15 | 中国民航信息网络股份有限公司 | Method and device for selling airline ticket, storage medium and electronic equipment |
| CN114091714A (en) * | 2022-01-20 | 2022-02-25 | 中国民航信息网络股份有限公司 | Passenger ticket filling control method and device |
-
2022
- 2022-01-20 CN CN202210063930.6A patent/CN114091714A/en active Pending
- 2022-04-19 WO PCT/CN2022/087623 patent/WO2023137890A1/en unknown
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030158811A1 (en) * | 2001-07-18 | 2003-08-21 | Ventanex | System and method for rules based electronic funds transaction processing |
| CN108305134A (en) * | 2017-01-13 | 2018-07-20 | 阿里巴巴集团控股有限公司 | A kind of safety detection method, equipment and the system of air ticket order |
| CN109949140A (en) * | 2017-12-18 | 2019-06-28 | 航天信息股份有限公司 | The method and device that generation draws a bill |
| US20200387976A1 (en) * | 2019-06-06 | 2020-12-10 | Salus Finance, LLC | System and Method for Consolidation, Reconciliation and Payment Management |
| CN113590683A (en) * | 2021-07-22 | 2021-11-02 | 福建博思软件股份有限公司 | Multi-dimensional electronic bill suspicious ticket comprehensive monitoring and analyzing method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023137890A1 (en) * | 2022-01-20 | 2023-07-27 | 中国民航信息网络股份有限公司 | Passenger ticket filling control method and apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023137890A1 (en) | 2023-07-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10984349B2 (en) | Travel advisory notifications | |
| US8229853B2 (en) | Dynamic itinerary-driven profiling for preventing unauthorized card transactions | |
| US20070143154A1 (en) | System and method for managing customer-based availability for a transportation carrier | |
| EP3002714A1 (en) | Ticketing system with integrated personalized data | |
| TWI679862B (en) | Method and device for processing text information | |
| US20160055431A1 (en) | System and method for generating itineraries and weather forecast displays | |
| US20180357732A1 (en) | Automatic space exchange opportunity response systems and methods | |
| US20200258010A1 (en) | Systems and methods for multi-destination travel planning using calendar entries | |
| CN114091714A (en) | Passenger ticket filling control method and device | |
| CN111104413A (en) | System and method for updating a shared database using blockchain techniques | |
| WO2021109306A1 (en) | Method and device for use in information processing, and computer storage medium | |
| Islam et al. | Use of ubiquitous real‐time bus passenger information | |
| US20180365599A1 (en) | Updating an entire itinerary based on modifying a single travel reservation | |
| WO2022166271A1 (en) | Airline passenger ticket management method and apparatus, computer-readable storage medium and program product | |
| CN113487338A (en) | Ticket refunding processing method and system, electronic equipment and storage medium | |
| US20160155139A1 (en) | Interacting with a database storing discounts | |
| KR20050062003A (en) | Method and apparatus for providing mobile passenger ticket service by mobile handset | |
| CN115099852A (en) | Freight rate authorization management method, device, equipment and storage medium | |
| KR102392273B1 (en) | System for providing freight information and method thereof | |
| CN113298621B (en) | Processing method of civil aviation retail order and related equipment | |
| JP7474544B1 (en) | Information processing system, information processing method, and program | |
| JP7440155B1 (en) | Programs, methods, and information processing systems | |
| Waghmare et al. | QR code based Railway e-Ticket | |
| CN115907789A (en) | Luggage quota sharing method and device, electronic equipment and storage medium | |
| US20220398507A1 (en) | Information processing device, information processing system, and information processing method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220225 |