WO2022105666A1

WO2022105666A1 - Duplicate reservation identification method and apparatus

Info

Publication number: WO2022105666A1
Application number: PCT/CN2021/130027
Authority: WO
Inventors: 曾进进; 余真真; 林彤; 郜美华; 高宁宁; 王晓逸; 王汉博; 付英茂; 韩楠; 郭鑫
Original assignee: 中国民航信息网络股份有限公司
Priority date: 2020-11-19
Filing date: 2021-11-11
Publication date: 2022-05-27
Also published as: CN112214520A

Abstract

A duplicate reservation identification method and apparatus. Acquired PNR data (S101) is parsed, and passenger identity information and flight information are extracted from the PNR data (S102); and a cache database is searched for a passenger ID corresponding to the passenger identity information (S103). A cache database is introduced to store the current valid PNR data, and a passenger ID corresponding to passenger identity information is directly generated in the cache database when a passenger makes a reservation for the first time. When real-time PNR data is received, the PNR data is preferentially placed in the cache database before duplicate reservation identification, such that the passenger ID can correspond to all associated PNR data, and thus, a duplicate reservation can be identified by means of performing duplicate order comparison on all valid PNR data associated with the same passenger ID.

Description

Method and device for re-booking identification

This application claims the priority of the domestic application with the application number 202011302293.0 and the invention titled "A Method and Device for Recognizing Repeated Reservations", which was filed with the China Patent Office on November 19, 2020, the entire contents of which are incorporated into this application by reference middle.

technical field

The present invention relates to the technical field of airline ticket reservation, and more particularly, to a method and device for recognizing repeated seat reservations.

Background technique

On the same flight or route, it is often seen that a certain passenger has booked seats on the same flight or adjacent flights in different PNRs (Passenger Name Records), or has booked multiple same flights in the same PNR or A seat on an adjacent flight. Since the passenger's subjective willingness is to use one of the seats, double booking of seats will cause the airline to occupy empty seats, so that the airline cannot sell the empty seats to the passengers who really need it as soon as possible, resulting in low flight occupancy rate and making the airline company gains are lost.

In conclusion, how to provide a method for identifying repeated reservations has become a technical problem that those skilled in the art need to solve urgently.

SUMMARY OF THE INVENTION

In view of this, the present invention discloses a method and device for recognizing repeated reservations, so as to realize the recognition of repeated reservations.

A method for identifying duplicate reservations, comprising:

Acquire PNR data, the PNR data includes: PNR number;

Parse the PNR data, and extract the passenger identity information and flight information from the PNR data;

Find the passenger ID corresponding to the passenger identity information from the cache database, and the passenger ID is generated in the cache database when the passenger makes a reservation for the first time;

The PNR number is placed in the cache database, and is stored in the form of a corresponding relationship with the passenger ID, and the PNR data corresponding to the PNR number is stored in the cache database simultaneously;

extracting all valid target PNR data from the cache database based on the passenger ID and the associated PNR number;

According to the preset duplicate reservation identification rules, compare all the target PNR data with duplicate orders to determine whether the passenger has duplicate orders;

If so, the repeat order is saved in the master database.

A device for identifying repeated reservations, comprising:

an acquisition unit, configured to acquire PNR data, the PNR data includes: a PNR number;

a parsing unit for parsing the PNR data, and extracting passenger identity information and flight information from the PNR data;

a search unit, configured to find the passenger ID corresponding to the passenger identity information from the cache database, where the passenger ID is generated in the cache database when the passenger makes a reservation for the first time;

The first storage unit is used to put the PNR number in the cache database, and store it in the form of a corresponding relationship with the passenger ID, and store the PNR data corresponding to the PNR number in the cache. in the database;

an extraction unit for extracting all valid target PNR data from the cache database based on the passenger ID and the associated PNR number;

The duplicate order judgment unit is used to compare all the target PNR data with duplicate orders according to the preset duplicate reservation identification rules, and judge whether the passenger has duplicate orders;

The second storage unit is configured to save the repeated order in the main database when the repeated order determination unit determines yes.

As can be seen from the above technical solutions, the present invention discloses a method and a device for re-booking identification, which analyzes the acquired PNR data, extracts the passenger identity information and flight information from the PNR data, and finds the relevant passengers from the cache database. The passenger ID corresponding to the identity information, the passenger ID is generated in the cache database when the passenger makes a reservation for the first time, the PNR number is placed in the cache database, and stored in the form of a corresponding relationship with the passenger ID, while the PNR number is stored in the cache database. The corresponding PNR data is stored in the cache database. Based on the passenger ID and the associated PNR number, all valid target PNR data are extracted from the cache database, and all target PNR data are repeated according to the preset repeated reservation identification rules. Orders are compared and the determined duplicate orders are saved in the main database. The present invention introduces a cache database to save the current valid PNR data, and directly generates the passenger ID corresponding to the passenger identity information in the cache database when the passenger makes a reservation for the first time. Prior to the reservation identification, the PNR data is preferentially placed in the cache database, so that the passenger ID can correspond to all the associated PNR data, so that all valid PNR data associated with the same passenger ID can be compared with repeated orders. Identification of duplicate reservations.

Description of drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent when taken in conjunction with the accompanying drawings and with reference to the following detailed description. 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 the originals and elements are not necessarily drawn to scale.

1 is a flowchart of a method for re-booking identification disclosed in an embodiment of the present invention;

FIG. 2 is a processing process of a repeated reservation identification system disclosed in an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a repeated reservation identification device disclosed in an embodiment of the present invention.

Detailed ways

The processing method of the repeated reservation identification in the prior art is: the repeated reservation identification system receives the PNR (Passenger Name Record, passenger reservation record) booked by various reservation channels in real time or regularly, and the repeated reservation identification system is based on the passenger information. Repeated reservation identification is performed by querying the database to find out whether the same passenger has repeated reservations or suspected repeated reservations within a certain range.

From the point of view of system architecture, in order to improve the throughput capacity of the repeated reservation identification system, the current repeated reservation identification system generally adopts a distributed parallel processing architecture. The distributed architecture has many advantages such as reliability, scalability, resource sharing, flexibility, high speed, and high performance, but there are also certain problems. In the process of identifying duplicate orders, the order data of the same passenger in the database needs to be queried and compared with the PNR pushed to the system in real time. In some cases, the system receives two or more PNRs of the same passenger almost simultaneously, such as: PNR1 and PNR2. Since the system adopts distributed parallel processing, these orders are allocated to different machines for simultaneous processing. When machine 1 is processing PNR1, PNR2 cannot be queried in the database, and it is impossible to identify whether PNR2 is duplicated with PNR1. Similarly, when the machine 2 is processing the PNR2, the information of the PNR1 cannot be queried in the database, so it is impossible to identify whether the PNR1 is repeated with the PNR2. In this scenario, if PNR1 and PNR2 are duplicate orders, the system will not be able to obtain the correct duplicate reservation identification result. From this, it can be concluded that there is a loophole in the identification of instantaneously high concurrent repeated orders by the distributed parallel repeated reservation identification system, which may cause the system to fail to fully identify the repeated order data.

In view of the above problems, a possible solution is to use the traditional serial calculation method for processing, that is, when two or more PNRs are received at the same time, PNR1 is preferentially processed, PNR2 waits, and then processed after PNR1 is processed. PNR2. Although this solution can guarantee the integrity of the duplicate order identification business, it also greatly reduces the processing speed of the system and loses the advantages of the high throughput capability of the parallel processing architecture.

Based on this, the embodiment of the present invention discloses a method and device for re-booking identification, which analyzes the acquired PNR data, extracts the passenger identity information and flight information from the PNR data, and finds the relevant passenger identity information from the cache database. The corresponding passenger ID, the passenger ID is generated in the cache database when the passenger makes a reservation for the first time, and the PNR number is placed in the cache database and stored in the form of a corresponding relationship with the passenger ID. The PNR data is stored in the cache database. Based on the passenger ID and the associated PNR number, all valid target PNR data are extracted from the cache database. According to the preset repeated reservation identification rules, all the target PNR data are compared for repeated orders. Yes, and save the identified duplicate orders in the master database. The present invention introduces a cache database to save the current valid PNR data, and directly generates the passenger ID corresponding to the passenger identity information in the cache database when the passenger makes a reservation for the first time. Prior to the reservation identification, the PNR data is preferentially placed in the cache database, so that the passenger ID can correspond to all the associated PNR data, so that all valid PNR data associated with the same passenger ID can be compared with repeated orders. Identification of duplicate reservations.

In addition, the present invention directly generates the passenger ID corresponding to the passenger identity information in the cache database, so that the passenger ID can correspond to all the associated PNR data, effectively avoiding the inability to identify the same data in the traditional solution due to the use of distributed parallel processing. The problem of multiple PNRs for passengers to identify duplicate reservations. Moreover, compared with the main database, the cache database can greatly improve the read and write efficiency, and can shorten the read and write operations to the millisecond level.

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 should 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 the purpose of A more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes, and are not intended to limit the protection scope of the present disclosure.

As used herein, the term "including" and variations thereof are open-ended inclusions, ie, "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 of other terms will be given in the description below.

It should be noted that concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or interdependence.

Referring to FIG. 1 , a flowchart of a method for identifying repeated reservations disclosed in an embodiment of the present invention includes:

Step S101, obtaining PNR data;

Specifically, in practical applications, the PNR data of the airline can be obtained from the China Civil Aviation Information System, and the PNR data includes: the PNR number.

PNR is the passenger reservation record, which is the abbreviation of Passenger Name Record. It reflects the passenger's voyage, the number of seats occupied by the flight, and passenger information, and is applicable to the civil aviation reservation system.

Step S102, parse the PNR data, and extract the passenger identity information and flight information from the PNR data;

The passenger identity information may include: passenger name, ID number, passport number, frequent flyer card number, and the like.

The flight information may include: flight reservation information, flight origin, flight destination, flight number, departure date and arrival date, and the like.

Step S103, finding the passenger ID corresponding to the passenger identity information from the cache database;

The passenger ID is generated in the cache database when the passenger makes a reservation for the first time.

In practical applications, passengers may use any one or more of ID number, passport number and frequent flyer card number for each seat reservation, so it is necessary to identify the passenger identity.

In order to facilitate subsequent repeated identification of multiple orders of the same passenger, the present invention generates a passenger ID for each passenger in the cache database to uniquely identify each passenger.

It should be noted:

A) When the passenger ID corresponding to the passenger identification information is not found in the cache database, a passenger ID corresponding to the passenger identification information is generated in the cache database.

B) If multiple passenger IDs corresponding to the passenger identity information are found in the cache database, the multiple passenger IDs need to be merged to ensure that passengers with multiple documents have only one unique passenger ID.

Example 1: Combining passenger IDs of different ID cards

Processing order 1 (English name + ID card 1): Get the real English name + encrypted ID number 1 key, query the cache database, no results are stored in the cache database, with the real English name + encrypted ID number 1 as the key, the passenger ID1 is the value;

Processing order 2 (English name + ID card 2): Get the real English name + encrypted ID number 2 key, query the cache database, no results are stored in the cache database, with the real English name + encrypted ID number 2 as the key, the passenger ID2 is the value;

Processing order 3 (English name + ID number 1 + ID number 2): Get the real English name + encrypted ID number 1 key and the real English name + encrypted passport number 2 key to circulate the certificate type, query the cache database, and find this Two key data exists, and there are two different passenger ID values, randomly use the passenger ID value of order 1 or order 2 as the final passenger ID (such as ID1), update the passenger ID value of order 1 and order 2, and aggregate become the same person.

Example 2: Combining the passenger ID of the ID card and the passport

Processing order 1 (English name + ID card): Get the real English name + encrypted ID number key, query the cache database, no result is stored in the cache database, take the real English name + encrypted ID number as the key, and passenger ID1 as the value ;

Processing order 2 (English name + passport): Get the real English name + encrypted passport number key, query the cache database, no result is stored in the cache database, take the real English name + encrypted passport number as the key, and passenger ID2 as the value;

Processing order 3 (English name + ID card + passport): Obtain the real English name + encrypted ID number key and the real English name + encrypted passport number key, cycle the certificate type, query the cache database, and find that these two key name data exist , and there are two different passenger ID values, randomly use the passenger ID value of order 1 or order 2 as the final passenger ID (such as ID1), update the passenger ID value of order 1 and order 2 (both ID1), and aggregate them into the same person.

In practical applications, the present invention can determine whether the passenger is the first reservation by judging whether the passenger ID corresponding to the passenger identity information is stored in the cache database, and if not, it is determined that the passenger has not made a reservation before. Generate a new passenger ID in the cache database; if it is, it is determined that the passenger is not the first reservation, and when the passenger rebooks, if there are multiple documents, it is determined to merge the passenger ID, otherwise the previously generated passenger ID is directly used. Passenger ID is sufficient.

It should be noted that this step is a key step to solve the loopholes existing in the distributed parallel repeated reservation identification system for instantaneously high concurrent repeated order identification. Assuming that the cache database is not introduced, if the repeated reservation recognition system receives two PNRs of the same passenger at a very short time interval (such as 1ms), they are PNR1 and PNR2 respectively. Since the system adopts distributed parallel processing, these orders will be It is assigned to different machines for simultaneous processing. When machine 1 is processing PNR1, PNR2 cannot be queried in the database, and it is impossible to identify whether PNR2 is duplicated with PNR1. Similarly, when the machine 2 is processing the PNR2, the information of the PNR1 cannot be queried in the database, so it is impossible to identify whether the PNR1 is repeated with the PNR2.

Therefore, the present invention introduces a cache database, in which the currently valid PNR data can be stored, and by directly generating a unique passenger ID corresponding to the passenger identity information in the cache database, the passenger ID can be established with all associated PNR data. At the same time, a corresponding relationship is also established between the PNR data and all passenger IDs, which effectively avoids the problem of inability to identify multiple PNRs of the same passenger in the traditional scheme due to the use of distributed parallel processing. Moreover, compared with the main database, the cache database can greatly improve the read and write efficiency, and can shorten the read and write operations to the millisecond level.

Step S104, put the PNR number in the cache database, and store it in the form of a corresponding relationship with the passenger ID, and store the PNR data corresponding to the PNR number in the cache database simultaneously;

Specifically, when a passenger makes a reservation for the first time, a passenger ID corresponding to the passenger identity information is first generated in the cache database, and then the acquired PNR data and the PNR number are stored in the cache database.

When it is not the first time that the passenger makes a reservation, the obtained PNR data together with the PNR number are directly stored in the cache database.

Step S105, based on the passenger ID and the associated PNR number, extract all valid target PNR data from the cache database;

It should be noted that, in the cache database, one passenger ID corresponds to all associated PNR data.

The valid target PNR data in this embodiment refers to the order data that has not been cancelled.

Step S106, according to the preset duplicate reservation identification rules, compare all the target PNR data with duplicate orders, and determine whether the passenger has duplicate orders, and if so, go to step S107;

Among them, the duplicate orders determined according to the preset duplicate reservation identification rules meet the conditions: (1) the passenger name and ID are the same; (2) the flight origin or the flight arrival place (airport) is the same; (3) the time meets the following requirements The duplicate PNR data of (the class, flight number and booking responsibility group in the duplicate PNR data can be different), as follows:

A. When the flight segment is a domestic flight segment (the country corresponding to the departure airport and the arrival airport is CN), the departure or arrival airport is the same, and the departure time of the two flight segments is within the first preset time range. part;

B. When the flight segment is an international flight segment (at least one of the countries corresponding to the departure airport and the arrival airport is not CN), the departure or arrival airports are the same, and the departure time of the two flight segments is considered to be within the second preset time range. is a repeating segment.

Specifically, (1) the criteria for judging whether the passenger's name and the identity ID are the same are: the passenger's name is duplicated and the identity ID is duplicated.

1) The basis for judging the duplication of passenger names is that the English names are the same.

For example, see Table 1 for details. It is assumed that the duplicate reservation identification system receives two PNRs, which are PNR1 and PNR2 respectively.

Table 1

2) The basis for judging the duplication of IDs is that the two passengers use the same ID card, passport or frequent flyer card.

The meaning of the same passenger is: the system will maintain the information of the passenger's English name, ID type and ID content. The same passenger can have multiple document information. If a passenger has the same English name and the same identity ID, they will be assigned the same passenger ID. If the same passenger appears in the same PNR with different identities, then these identities will also be assigned the same passenger ID. For example, if a passenger has entered the ID number and passport number in the same PNR, if the subsequent change of passenger uses the ID number and passport number to book a PNR, it will also be confirmed as the same passenger.

Among them, the types of identity ID type analysis are as follows:

************<FOID>**************************************** *

Use SSR FOID to enter passenger identification information

Instruction format:

SSR FOID AIRLINE-CODE HK/document code and number/Pn

Note: 1) The certificate code has NI ID card, PP passport;

2) Each passenger can only enter one FOID identity information. If you enter the wrong information, you must delete it and enter it again. That is, the PNR of multiple people must specify the information, which passenger belongs to, and the PNR of single person can not specify.

Example:

SSR FOID CA HK/NI110108200306016012/P1

SSR FOID CA HK/PP112233/P2

************<PSPT>**************************************** *

Entering Passenger Passport Information Using SSR PSPT

Instruction format:

SSR PSPT AIRLINE-CODE HK1/passport number/nationality/passenger birthday/passenger surname/passenger name/gender and baby ID/holder ID/Pn

Notice:

1 Gender and baby identification include: M for MALE, F for FEMALE; MI for boy, FI for girl.

2 Each passenger can only enter one passport information. That is, the PNR of multiple people must specify which passenger the information belongs to, and the PNR of a single person may not specify.

3. Only need to enter the passenger's surname and passenger's name in the following two situations: A. When the passenger's name in the PNR is different from the passenger's name in the passport; B. Enter the passport information for the baby.

Example:

Enter the passport information for a Chinese boy (male baby) TEST/NAME born on April 20, 2002, the passport number is 1234567890123456, and the passport holder is the first passenger in the PNR.

SSR PSPT CA HK1/1234567890123456/CN/20APR02/TEST/NAME

/MI/H/P1

Enter the passport information for a Chinese male born on April 20, 1970, the passport number is 123456789, and this person is the first passenger in the PNR.

SSR PSPT CA HK1/123456789/CN/20APR70///M/P1

********<API usage format>******************************

background:

The United States requires airlines to begin adopting PAXLST based on the UNEDIFACT standard on October 4, 2005. Canada began to use on November 1, 2005. Compared with the current API information, the information added to the US PAXLST includes: country of residence, US address (except for US citizens or US resident cards), passport expiration date, Canada PAXLST increase Information: country of residence, passport expiration date. PAXLST usually only requires one type of valid document information, at most no more than two, passport information is preferred, and each passenger including infants must hold at least one valid document.

*DOCS

Instruction format:

SSR: DOCS Airline Code Action-Code1 Document Type / Issuing Country / Document Number / Nationality / Date of Birth / Gender / Document Validity Period

/SURNAME(last name)/FIRST-NAME(first name)/MID-NAME(middle name)/holder

Logo H/P1

Example:

SSR: DOCS CA HK1P/CHN/143810297/CHN/24APR67/M/23APR02

ZHANG/DALONG/P1

illustrate:

Document Type: P Passport Issuing Country: CHN

Passport number: 143810297 Nationality: CH

Date of Birth: 24APR67 Gender: M

Certificate validity: 23APR02

Surname: ZHANG Name: DALONG

Note: only focus on the P type of the DOCS type

************<FQTV>************************************ *

Entering frequent flyer information using SSR FQTV

Instruction format:

SSR FQTV AIRLINE-CODE HK/document code and number/Pn

Note: 1 The document code is the prefix of the airline, such as CA, LH, etc. (This requirement supports the non-Air China alliance card number entered by Air China.).

2 The frequent flyer number must be a real and valid number.

Example:

SSR FQTV CA HK/CA101599260/P1

Examples of suspected duplicate passengers (when the passenger names are the same and the identity information has the following situations):

Example 1 (Table 2) - same ID number:

Table 2

PNR1中的旅客Passengers in PNR1	NI：11012340098900233NI: 11012340098900233
PNR2中的旅客Passengers in PNR2	NI：11012340098900233NI: 11012340098900233

Example 2 (table 3) - same passport number:

table 3

PNR1中的旅客Passengers in PNR1	PP：25782769PP: 25782769
PNR2中的旅客Passengers in PNR2	PP：25782769PP: 25782769

Example 3 (Table 4) - Same frequent flyer card number:

Table 4

PNR1中的旅客Passengers in PNR1	CA：101599260CA: 101599260
PNR2中的旅客Passengers in PNR2	CA：101599260CA: 101599260

Example 4 (Table 5) - The ID number is the same as the frequent flyer card number:

table 5

PNR1中的旅客Passengers in PNR1	NI：11012340098900233、CA：101599260NI: 11012340098900233, CA: 101599260
PNR2中的旅客Passengers in PNR2	NI：11012340098900233NI: 11012340098900233
PNR3中的旅客Passengers in PNR3	CA：101599260CA: 101599260

It should be noted that when judging whether a passenger is booking a seat for the first time, the judgment is mainly based on the identity information of the passenger. Since the passenger names in the PNR data may have a wide variety of name suffixes, such as MR, MS, VIP, etc., before judging whether the name is repeated, the name suffix needs to be stripped in order to obtain an accurate name. Whether the passenger's name is repeated. When the passenger ID corresponding to the passenger's identity information is found from the cache database, according to the passenger's name stripped from the name suffix and the ID number, passport number or frequent flyer card number used for this booking, etc. Whether the passenger ID of the passenger identification information exists.

Among them, the passenger identity information includes: any one of the ID number, passport number or frequent flyer card number used for this reservation, and the passenger's name with the name suffix stripped.

3) Stripping the name suffix

Strip the suffix in the following form and store it in the database table in two fields: name (after stripping) and suffix (after stripping). In the duplicate order result data, duplication between names with suffix and suffix, duplication between names without suffix and without suffix, duplication between names with suffix and without suffix can be identified.

There are mainly the following types of recognizable name suffixes, which support configuration:

MR/MS/CHD/MRS/MISS/MSTR/SD/STU/DL/DR/MDM/INF/SC/V/LBR/VVIP/IN/DE/INS/DIPL/CBBG/EXST/MASTER/SEA/EM/ MIS/GM/EMI/

STCR/JC/WCHR/WCHS/WCHC/VIP/MAAS/INAD/DEPA/DEPU/DEAF/CHILD/CIP/BLND/MAS/YP/MADAM/AS/LEGL/PETC/SP/VF

Strip slashes and spaces from names.

Example 1: zhang/san, it is stored as zhangsan.

Example 2: zhang san, it is stored as zhangsan.

Example 3: HAN/WAI LEEA, it is stored as HANWAILEEA.

Example 4: VANASS/LEONAD JOHA MR, it is stored as VANASSLEONADJOHA.

(2) Judgment criteria for the same (or repeating segment) of the flight origin or arrival place (airport) are as follows:

1) The flight segment is a valid flight segment;

2) The conditions for similar flight segments are that the departure city or the arrival city is the same, and if the departure city is the same, the departure time is relatively short, and if the arrival city is the same, the arrival time is relatively short.

It should be noted that, for the description of suspected duplicate matching, see Table 6.

Table 6

It should also be noted that when detecting whether there are other duplicate flight segments, the present invention supports the scope control of whether to enable full detection within the alliance. For example, FM and MU are the same alliance, and the flight segments with duplicate reservations within the alliance can be identified.

It should be noted that, in order to protect the privacy data of passengers, the document information (ID number, passport number and frequent flyer card number) in the PNR order is encrypted, and the encryption method can be SM4. For the specific encryption process, reference may be made to the existing mature solution, which will not be repeated here.

Step S107, save the repeated order in the main database.

Among them, after the repeated orders are saved in the main database, they can be used for subsequent query or cleaning functions. Specifically, the automatic cleaning module reads duplicate orders from the main database, and after cleaning the duplicate orders, the cleaning results are kept in the main database.

It should be noted that the processing process of the repeated reservation identification system disclosed in the present invention can be referred to as shown in FIG. 2 , wherein PNR1 and PNR2 are only an example. In practical applications, the number of PNRs obtained by the repeated reservation identification system is the corresponding in the application.

To sum up, the present invention discloses a method for re-booking identification, which analyzes the acquired PNR data, extracts the passenger identity information and flight information from the PNR data, and finds the passenger corresponding to the passenger identity information from the cache database. ID, the passenger ID is generated in the cache database when the passenger makes a reservation for the first time, the PNR number is placed in the cache database, and stored in the form of a corresponding relationship with the passenger ID, and the PNR data corresponding to the PNR number is stored at the same time. In the cache database, based on the passenger ID and the associated PNR number, all valid target PNR data are extracted from the cache database, and all target PNR data are compared according to the preset repeated reservation identification rules for repeated orders, and Save identified duplicate orders in the master database. The present invention introduces a cache database to save the current valid PNR data, and directly generates the passenger ID corresponding to the passenger identity information in the cache database when the passenger makes a reservation for the first time. Prior to the reservation identification, the PNR data is preferentially placed in the cache database, so that the passenger ID can correspond to all the associated PNR data, so that all valid PNR data associated with the same passenger ID can be compared with repeated orders. Identification of duplicate reservations.

It should be noted that the flowcharts and block diagrams in the accompanying drawings 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 that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks 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 is also noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented in dedicated hardware-based systems that perform the specified functions or operations , or can be implemented in a combination of dedicated hardware and computer instructions.

Computer program code for performing operations of the present disclosure may be written in one or more programming languages, including but not limited to object-oriented programming languages—such as Java, Smalltalk, C++, and This includes conventional procedural programming languages - such as the "C" 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 kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (eg, using an Internet service provider via Internet connection).

Corresponding to the above method embodiments, the present invention also discloses a repeated reservation identification device.

Referring to FIG. 3 , a schematic structural diagram of a device for identifying repeated reservations disclosed in an embodiment of the present invention includes:

an obtaining unit 201, configured to obtain PNR data, the PNR data includes: a PNR number;

a parsing unit 202 for parsing the PNR data, and extracting passenger identity information and flight information from the PNR data;

Searching unit 203, configured to find the passenger ID corresponding to the passenger identity information from the cache database, where the passenger ID is generated in the cache database when the passenger makes a reservation for the first time;

In practical applications, passengers may use any one or more of ID number, passport number and frequent flyer card number for each seat reservation, so it is necessary to identify the passenger's identity.

It should be noted:

Therefore, the repeated reservation identification device may further include: a generating unit, for the first storage unit 204 to put the PNR number into the cache database, and store it in the form of a corresponding relationship with the passenger ID, and at the same time store the PNR number in the cache database. Before the PNR data corresponding to the PNR number is stored in the cache database, when the passenger ID corresponding to the passenger identity information is not found in the cache database, a data corresponding to the passenger is generated from the cache database. The identity information corresponds to the passenger ID.

B) If multiple passenger IDs corresponding to the passenger identity information are found in the cache database, the multiple passenger IDs need to be merged to ensure that passengers with multiple certificates have only one unique passenger ID.

Example 1: Combining passenger IDs of different ID cards

Example 2: Combining the passenger ID of the ID card and the passport

The first storage unit 204 is used to put the PNR number in the cache database, and store it in the form of a corresponding relationship with the passenger ID, and store the PNR data corresponding to the PNR number in the cached in the database;

When the passenger is not making the first reservation, the obtained PNR data together with the PNR number are directly stored in the cache database.

Extraction unit 205, for extracting all valid target PNR data from the cache database based on the passenger ID and the associated PNR number;

The duplicate order judgment unit 206 is configured to compare all the target PNR data with duplicate orders according to the preset duplicate reservation identification rules, and judge whether the passenger has duplicate orders;

The second storage unit 207 is configured to save the repeated order in the main database when the repeated order determination unit determines yes.

In summary, the present invention discloses a repeated reservation identification device, which analyzes the acquired PNR data, extracts the passenger identity information and flight information from the PNR data, and finds the passenger corresponding to the passenger identity information from the cache database. ID, the passenger ID is generated in the cache database when the passenger makes a reservation for the first time, the PNR number is placed in the cache database, and stored in the form of a corresponding relationship with the passenger ID, and the PNR data corresponding to the PNR number is stored at the same time. In the cache database, based on the passenger ID and the associated PNR number, all valid target PNR data are extracted from the cache database, and all target PNR data are compared according to the preset repeated reservation identification rules for repeated orders, and Save identified duplicate orders in the master database. The present invention introduces a cache database to save the current valid PNR data, and directly generates the passenger ID corresponding to the passenger identity information in the cache database when the passenger makes a reservation for the first time. Prior to the reservation identification, the PNR data is preferentially placed in the cache database, so that the passenger ID can correspond to all the associated PNR data, so that all valid PNR data associated with the same passenger ID can be compared with repeated orders. Identification of duplicate reservations.

In the above-mentioned embodiment, when performing name repetition judgment, the repeated reservation identification device may further include:

The name repetition judgment unit is used to strip the suffix of the passenger's name, and judge whether the passenger's name after the suffix stripped is repeated.

The units involved in the embodiments of the present disclosure may be implemented in a software manner, and may also be implemented in a hardware manner. Wherein, the name of the unit does not constitute a limitation of the unit itself under certain circumstances, for example, the first acquisition unit can also be described as "a unit that acquires 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 Chips (SOCs), Complex Programmable Logical Devices (CPLDs) and more.

It should be particularly noted that, for the specific working principles of each component in the apparatus embodiment, please refer to the corresponding part of the method embodiment, which will not be repeated here.

Finally, it should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other.

The above description of the disclosed embodiments enables any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

A method for identifying repeated reservations, comprising:

Acquire PNR data, the PNR data includes: PNR number;

Parse the PNR data, and extract the passenger identity information and flight information from the PNR data;

Find the passenger ID corresponding to the passenger identity information from the cache database, and the passenger ID is generated in the cache database when the passenger makes a reservation for the first time;

Put the PNR number in the cache database, and store it in the form of a corresponding relationship with the passenger ID, and store the PNR data corresponding to the PNR number in the cache database simultaneously;

extracting all valid target PNR data from the cache database based on the passenger ID and the associated PNR number;

According to the preset duplicate reservation identification rules, compare all the target PNR data with duplicate orders to determine whether the passenger has duplicate orders;

If so, the repeat order is saved in the master database.
The method for identifying repeated reservations according to claim 1, wherein the PNR number is stored in the cache database in the form of a corresponding relationship with the passenger ID, and the PNR number is stored at the same time. Before storing the corresponding PNR data in the cache database, it also includes:

When the passenger ID corresponding to the passenger identity information is not found in the cache database, a passenger ID corresponding to the passenger identity information is generated from the cache database.
The method for identifying repeated reservations according to claim 1, wherein the repeated order determined according to the preset repeated reservation identification rule satisfies the conditions:

The passenger's name and ID are the same;

The origin of the flight or the place of arrival of the flight is the same;

Repeated PNR data whose time meets the following requirements:

A. When the flight segment is a domestic flight segment, the departure or arrival airport is the same, and the departure time of the two flight segments is within the first preset time range, it is considered as a duplicate flight segment;

B. When the flight segment is an international flight segment, the departure or arrival airport is the same, and the departure time of the two flight segments is within the second preset time range, it is considered as a duplicate flight segment.
The method for identifying repeated reservations according to claim 3, wherein the criterion for determining whether the passenger name and the identity ID are the same is: the passenger name is repeated and the identity ID is repeated;

The basis for judging that the passenger's name is repeated is: the English name is the same;

The basis for judging that the IDs are duplicated is that the two passengers use the same ID card, passport or frequent flyer card.
The method for identifying repeated reservations according to claim 4, wherein the process of judging that the passenger's name is repeated comprises:

The suffix is stripped from the passenger's name, and it is judged whether the passenger's name after the suffix stripping is repeated.
The method for identifying repeated reservations according to claim 5, wherein the passenger identity information includes: any one of the ID number, passport number or frequent flyer card number used for the current reservation, and the name suffix stripped Passenger Name.
The method for re-booking identification according to claim 3, wherein the criteria for determining that the flight originating place or the flight arriving place are the same are: the flight segment is a valid flight segment; the conditions for similar flight segments are the departure city or the arrival location. The cities are the same, and if the departure city is the same, the departure time is relatively close, and if the arrival city is the same, the arrival time is relatively close.
A device for identifying repeated reservations, comprising:

an acquisition unit, configured to acquire PNR data, the PNR data includes: a PNR number;

a parsing unit for parsing the PNR data, and extracting passenger identity information and flight information from the PNR data;

a search unit, configured to find the passenger ID corresponding to the passenger identity information from the cache database, where the passenger ID is generated in the cache database when the passenger makes a reservation for the first time;

The first storage unit is used to put the PNR number in the cache database, and store it in the form of a corresponding relationship with the passenger ID, and store the PNR data corresponding to the PNR number in the cache. in the database;

an extraction unit for extracting all valid target PNR data from the cache database based on the passenger ID and the associated PNR number;

The duplicate order judgment unit is used to compare all the target PNR data with duplicate orders according to the preset duplicate reservation identification rules, and judge whether the passenger has duplicate orders;

The second storage unit is configured to save the repeated order in the main database when the repeated order judgment unit judges yes.
The repeated reservation identification device according to claim 8, further comprising:

A generating unit, for the first storage unit to put the PNR number in the cache database, and store it in the form of a corresponding relationship with the passenger ID, and store the PNR data corresponding to the PNR number at the same time Before reaching the cache database, when no passenger ID corresponding to the passenger identity information is found in the cache database, a passenger ID corresponding to the passenger identity information is generated from the cache database.
The repeated reservation identification device according to claim 8, wherein the repeated order determined according to the preset repeated reservation identification rule satisfies the conditions:

The passenger's name and ID are the same;

The origin of the flight or the place of arrival of the flight is the same;

Repeated PNR data whose time meets the following requirements:

A. When the flight segment is a domestic flight segment, the departure or arrival airport is the same, and the departure time of the two flight segments is within the first preset time range, it is considered as a duplicate flight segment;

B. When the flight segment is an international flight segment, the departure or arrival airport is the same, and the departure time of the two flight segments is within the second preset time range, it is considered as a duplicate flight segment.
The repeated reservation identification device according to claim 10, wherein the criterion for determining whether the passenger name and the identity ID are the same is: the passenger name is repeated and the identity ID is repeated;

The basis for judging that the passenger's name is repeated is: the English name is the same;

The basis for judging that the IDs are duplicated is that the two passengers use the same ID card, passport or frequent flyer card.
The repeated reservation identification device according to claim 11, characterized in that, further comprising:

The name repetition judgment unit is used to strip the suffix of the passenger's name, and judge whether the passenger's name after the suffix stripped is repeated.
The device for re-booking identification according to claim 12, wherein the passenger identity information includes: any one of an ID number, a passport number or a frequent flyer card number used for the current reservation, and a stripped name suffix. Passenger Name.
The device for re-booking identification according to claim 10, wherein the criteria for determining that the flight departure place or the flight arrival place are the same are: the flight segment is a valid flight segment; the condition for similar flight segments is the departure city or the arrival location. The cities are the same, and if the departure city is the same, the departure time is relatively close, and if the arrival city is the same, the arrival time is relatively close.