WO1997030404A1 - Systeme de transfert de donnees des progiciels de gestion de transactions des compagnies aeriennes - Google Patents

Systeme de transfert de donnees des progiciels de gestion de transactions des compagnies aeriennes Download PDF

Info

Publication number
WO1997030404A1
WO1997030404A1 PCT/US1996/018463 US9618463W WO9730404A1 WO 1997030404 A1 WO1997030404 A1 WO 1997030404A1 US 9618463 W US9618463 W US 9618463W WO 9730404 A1 WO9730404 A1 WO 9730404A1
Authority
WO
WIPO (PCT)
Prior art keywords
input data
computer
server computer
data
data structures
Prior art date
Application number
PCT/US1996/018463
Other languages
English (en)
Inventor
Farid Mehovic
Original Assignee
The Sabre Group, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by The Sabre Group, Inc. filed Critical The Sabre Group, Inc.
Priority to AU30806/97A priority Critical patent/AU3080697A/en
Priority to EP96946375A priority patent/EP0832464A1/fr
Priority to EA199700372A priority patent/EA199700372A1/ru
Publication of WO1997030404A1 publication Critical patent/WO1997030404A1/fr

Links

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

Definitions

  • This invention relates in general, to electronic data manipulation, and in particular to, a system and method for propagating, retrieving and using airline computerized reservation system Transaction Processing Facility data propagated to a relational database platform thus enabling the execution of relational database functions using the propagated Transaction Processing Facility data.
  • TPF Transaction Processing Facility
  • TPF based data repository The intrinsic value of any airline reservation system's TPF based data repository is that it represents an inventory of information that is maintained in as current a manner as possible. Such information is typically referred to as real-time information. Unlike information governed by a Relational Database Management System (RDBMS), currently TPF based CRS resident information may only be accessed and utilized by applications managed through the limited purpose TPF control program. Consequently, though a TPF based CRS maintains huge volumes of real-time data resources, it is woefully deficient in its ability to present these resources in a timely and effective manner for use by non-TPF based applications.
  • RDBMS Relational Database Management System
  • non-TPF applications require data stored within an airline TPF based CRS environment
  • data could be (1) copied into the non-TPF environment via a batch processing scenario, or (2) retrieved from the TPF basec CRS via on-line communication channels.
  • option (1) becomes unfeasible due to processing delays and data accuracy impact, associated with host processor and storage device overhead.
  • Option (2) becomes equally unacceptable due to communications delay - most particularly when the application requires reference to more than a single element of real-time data.
  • Option (2) bears the further significant detriment of requiring extensive modification to applications within the airline TPF based CRS environment to facilitate presentation of such data.
  • the present invention provides the framework within which TPF based CRS data is propagated to a RDBMS for subsequent retrieval and use in a transparent manner by the end user.
  • the present invention provides a comprehensive system and methodology to automate the migration of data structures from an airline TPF based CRS processing environment and, in particular, the American Airlines' SABRE TPF based CRS environment to a relational database management system (RDBMS) for transparent retrieval and use by the end user.
  • RDBMS relational database management system
  • the invention thus provides a unique solution to a long standing data processing dilemma - how to propagate real-time airline TPF based CRS data quickly, directly, and transparently, from the airline TPF based CRS processing environment to any relational database management system (RDBMS) supported by Structured Query Language (SQL) command processing for use by the end user.
  • SQL Structured Query Language
  • the invention can be viewed as consisting of the following elements:
  • FIGURE 1 is a schematic representation of the airline TPF based CRS data propagation system
  • FIGURE 2 is a logic flow chart of the airline TPF based CRS data propagation selection process
  • FIGURE 3 is a logic flow chart of the function management process
  • FIGURE 4 is a schematic representation of communicably linked remote hardware components attendant to the airline TPF based CRS propagation system
  • FIGURE 5 is a schematic representation of communicably linked hardware components attendant to the airline TPF based CRS propagation system with the function management means residing exclusively within the functional server computer;
  • FIGURE 6 is a schematic representation of communicably linked hardware components attendant to the airline TPF based CRS propagation system with the function management means residing exclusively within the target relational database management system computer;
  • FIGURE 7 is a schematic representation of communicably linked hardware components attendant to the airline TPF based CRS propagation with the function management means residing in both the functional server computer and target relational database management system computer.
  • FIGURE 8 is a schematic representation of communicably linked hardware components illustrating the retrieval and use of the propagated TPF data.
  • FIGURE 9 is a detailed schematic representation of internal processing conducted by the Functional Server as it relates to the retrieval, translation, and use of the TPF propagated data by an end-user.
  • the system for propagating airline TPF based CRS data and, in particular, American Airlines SABRE TPF based CRS data to a relational database platform and enabling the execution of relational database applications using the TPF data is generally designated as 10 is shown in Figure 1.
  • the airline computerized reservation system transaction processing facility 12, ("TPF based CRS") of the present invention is a series of mainframe computers such as an IBM ES 3090 coupled together in a centralized processing complex to form the heart of American Airlines' SABRE CRS.
  • a user terminal 14 is communicably connected to the TPF based CRS 12. The user terminal 14 thus serves to interface with applications executing under TPF based CRS control and may be configured as either a dedicated terminal or a personal computer.
  • a functional server 16 is communicably linked to the CRS TPF 12.
  • the functional server 16 is a software concept and as such, may be one or more computers.
  • Propagated data 18 from the TPF based CRS 12 is propagated in real-time to the functional server 16.
  • a database server 20 receives Structure Query Language ("SQL") statements 22 generated by the functional server 16.
  • SQL Structure Query Language
  • the database server 20, like the functional server, is a software concept and may be supported and resident upon one or more computers.
  • the database server 20 may operate in any open relational database environment, for example, DB2, Oracle, Ingres, Informix or Sybase.
  • the database server 20 interprets the SQL statements 22 and performs the desired SQL functions against a relational database 24.
  • the relational database 24 may be one or more digitized storage devices attached to one or more computers in a relational database processing environment.
  • the operating system for the database server 20 may be Unix or an equivalent system.
  • the database server 20 may execute upon , for example, SMP (symmetric multi-processors) such as IBM's RISC System/600 Models J30.or R30, or a MPP (massively parallel processors), such as IBM's SP2.
  • the functional server 16 hosts relational database input translation applications which act upon propagated data 18 from the TPF based CRS 12.
  • a personal computer (“PC") client 26 uses the data from the relational database and database server 20 to transparently execute non-TPF based CRS applications using the propagated data 18 from the TPF based CRS 12.
  • a logic flow chart of the data propagation selection process 28 resident on the TPF based CRS 12 is shown in Figure 2.
  • the process comprises a series of steps for data propagation that occur immediately after the TPF based CRS 12 updates the data or at definable intervals of time, in which case data updates are saved in a log until the next propagation event.
  • Step 30 an application program processing request from an end-user or PC client is received by the TPF based CRS 12.
  • the application program processing request is dispatched by the TPF based CRS 12 in step 32 which passes control to the application program.
  • the application program performs routine processing in step 34.
  • step 36 the system determines whether a TPF based CRS 12 data update is indicated.
  • step 38 determines whether a miscellaneous function management processing is indicated in step 38. If no miscellaneous function management processing is indicated, the routine application program processing is completed in step 40. Control is returned to the TPF based CRS 12 operating system in step 42. If a TPF based CRS 12 data update is indicated in step 36, data is sent to a function management process in step 44. In step 46 function management processing is completed. Step 48 returns to routine application program processing. Routine application program processing is completed in step 40. Control is returned to the TPF based CRS 12 operating system in step 42. If miscellaneous function management processing is indicated in step 38, a miscellaneous function management processing request passes data to the function management process in step 50.
  • step 46 function management processing is completed.
  • Step 48 returns to routine application program processing.
  • Routine application program processing is completed in step 40.
  • Control is returned to the TPF based CRS 12 operating system in step 42.
  • a logic flow chart of the function management process 52 is shown in Figure 3.
  • a request for function management service is received in step 54.
  • a determination of whether the request for function management service is a propagation request is made in step 56. If there is a propagation request, the propagation data is parsed in step 58. SQL statements are created in step 60. The parsed propagation data and the SQL statements are sent to update the target relational database management system in step 62.
  • Step 64 determines whether the update of the target relational database management system was successful.
  • step 66 If the update of the target relational database management system was not successful a reply message of resend is sent in step 66.
  • the function management process 52 then waits for a new request for service in step 68. If the update of the target relational database management system was successful a reply message of success is sent in step 70. The function management process 52 then waits for a new request for service in step 68. If there is not a propagation request in step 56, a determination of whether the request for function management service is a function request is made in step 72. If there is a function request, the function command and data are parsed in step 74. SQL statements are created in step 76. The SQL statements containing relevant parsed function data are sent to search/update the target relational database management system in step 78.
  • Step 80 determines whether the search/update of the target relational database management system was successful. If the search/update of the target relational database management system was not successful a reply message of error is sent in step 82. The function management process 52 then waits for a new request for service in step 68. If the search/update of the target relational database management system was successful in step 80, a reply message of the results is sent in step 84. The function management process 52 then waits for a new request for service in step 68.
  • step 86 a determination of whether a default action has been defined is made in step 86. If there is no default action defined, a reply message of error is sent in step 88. The function management process 52 then waits for a new request for service in step 68. If there is a default action defined in step 86, the default action is performed in step 90. A reply message of success or error is sent in step 92. The function management process 52 then waits for a new request for service in step 68.
  • FIG. 4 A schematic representation of communicably linked remote hardware components and propagation software attendant to the TPF based CRS propagation system of Figure 1 is presented in Figure 4.
  • the TPF based CRS 12 is communicably linked to an input device 94 of the user terminal 14.
  • the input device 94 may be a keyboard, a mouse, a touch screen or other suitable input means, including resident software modules such as TPF based CRS elapsed interval initiated activity.
  • the input device 94 of the user terminal 14 is used to create an input data structure 96 which is sent to the TPF based CRS system 12.
  • a data propagation selection means 98 as described in reference to Figure 2 is resident within the TPF based CRS 12.
  • the data propagation selection means 98 is in communication with the functional server 16 and the database server 20.
  • the database server 20 has RDBMS operating software loaded for operation of the database server 20.
  • the database server 20 has an data output means 100 in communication therewith.
  • the data output means may be a computer monitor, a printer, a fax machine or other suitable device.
  • PC clients 26 and data storage means 24 are communicably linked to the database server 20.
  • FIG. 5 A schematic representation of communicably linked remote hardware components and function management software attendant to the TPF based CRS propagation system of Figure 1 is presented in Figure 5.
  • the propagated data 18 from the TPF based CRS 12 is received by a function management means 102 residing exclusively within the functional server 16.
  • the function management means 102 receives requests and creates SQL statements which are sent to the database server 20 as described in reference to Figure 3.
  • the propagated data 18 from the TPF based CRS 12 is received by a function management means 102 residing exclusively within the database server 20.
  • the function management means 102 receives requests and creates SQL statements as described in reference to Figure 3.
  • the propagated data 18 from the TPF based CRS 12 is received by a function management means 102 residing within both the functional server 16 and the database server 20.
  • the function management means 102 receives requests and creates SQL statements as described in reference to Figure 3.
  • FIG 8 there is representative schematic of how the TPF based CRS data 12 is retrieved and used from the relational database 24.
  • SABRE end-users 104 may access the relational database 24 either through a VAX front- end 106 or through the functional server 16 and then subsequently communicate with the relational database 24. Alternatively, the end-user 104 may communicate first through the VAX front-end 106, second through the TPF 12 and then subsequently to the functional server 16.
  • other non-SABRE users 108 may either access the functional server 16 and then communicate with the relational database 24 or directly with the relational database system. Access to the functional server by SABRE and non-SABRE users may also be performed by voice recognition software that activates the RDBMS software 24 merely by use of voice commands.
  • One of the primary advantages of the present invention is the ability of the SABRE end-user 104 to access the TPF based CRS data 12 after propagation to a relational database management system 24 using already known language structure commands and without the need to upgrade, buy or purchase any additional hardware or software.
  • the SABRE end-user 104 thus, has the ability to utilize the previously TPF based CRS data 12 now existing on the relational database 24, as though the data was still residing on the mainframes.
  • This feature provides the end-users 104 and 108 with the flexibility and adaptability to retrieve and use propagated TPF based CRS data now residing on relational database 24, as if remained resident on the TPF Host CRS (12) at all times.
  • FIG. 9 therein is disclosed in more detail the ability of the end-users 104 and 108 to input commands 110 which may be SABRE commands, English commands, SQL language or any other type of input queries.
  • the input commands 110 are received by the receiver 112 of the functional server 16.
  • the receiver 112 passes the commands that are in non-SQL language through the translator 114 which converts it into the structured query language (SQL) and then through the sender 116 that produces an output 118 which is compatible with the relational database server 20.
  • the output 118 is then used by the relational database 24 in the execution of any relational database server applications.
  • the present invention for a system for propagating TPF based CRS data to a relational database platform and enabling the execution of relational database applications using the TPF based CRS data is now described in reference to the propagation, function management and use by an end-user of an American Airlines' SABRE CRS Passenger Name Record (“PNR”) .
  • PNR American Airlines' SABRE CRS Passenger Name Record
  • the original PNR is stored on the TPF based CRS 12.
  • the PNR as TPF based CRS data, is a mix of textual and parametric data, stored as a text object.
  • the PNR is entered into the TPF based CRS it is propagated to a functional server and subsequently stored in a relational database.
  • the information is stored in four logical entities or tables in the relational database which are: Reservation, Segment, Passenger, and Ticket.
  • Table Reservation contains the actual PNRs.
  • the PNRs are stored as Table Reservation Attribute PNRs, as specified in Table 1 below.
  • Attribute PNR Status specifies whether the PNR is in error, and if so, what type of error it is (N for no- error, C for data corrupted error, T for data corrupted error with PNR truncated, E for other types of error) .
  • Attribute PNR Locator, Purge Date, and PCC contain parameters specified in the PNR itself.
  • PNR Locator is the unique PNR code used by travel agents and customers to quickly locate the PNR.
  • Attribute Purge Date is the date the PNR was scheduled to be purged from the CRS system.
  • PCC stands for Pseudo-City-Code, the location code of the agency which booked the reservation.
  • Archive Date specifies the date the PNR was archived, i.e., stored in this table.
  • PNR Number is the unique identifier for the PNR when stored in the archive.
  • Table Segment contains flight segments stored in the original PNR on the special segment lines, as specified in Table
  • Each flight segment consists of Airline Code and
  • Flight segments can be canceled or still active. Attribute Segment Status represents whether the flight segment is still active. Attribute Segment Status represents whether the flight segment is still active (OK) or canceled. If canceled, it shows the reason for cancellation, such as AS, SC, or XS.
  • the PNR Number specifies which PNR a particular flight segment (a row of the Segment table) is associated with. There can be several flight segments per PNR.
  • Attribute Segment Number specifies the segment number within the
  • PNR The combination of PNR Number and Segment Number attributes is unique.
  • Table Passenger contains passengers for which reservations are booked, as specified in Table 3 below. This information is stored on special lines within the original PNRs. Each line contains the common last name of one or more passengers, or the name of the organization for which the reservation is made. This name is stored in attribute Name. Attribute Passenger Type indicates whether the passenger is a person or persons (P) or an organization (B, C, or I) . Attribute Passenger Count specifies how many actual individuals are represented by this PNR line (by this Passenger table row) . The PNR Number specifies which PNR
  • SUBSTITUTESHEET(RULE2Q) a particular passenger (a row of the Passenger table) is associated with. There can be several passengers per PNR. Attribute Passenger Number specifies the passenger number within the PNR. The combination of PNR Number and Passenger Number attributes is unique.
  • Table Ticket contains tickets booked for all reservations, as specified in Table 4 below. This information is stored on special lines within the original PNRs. Each line contains the ticket number and ticket type. Attribute Ticket Number is an array of digits. The first three digits represent airline code, and the rest represent the unique ticket number within the airline. The entire ticket number, however, is treated here as one single array of digits. Ticket Number is unique. Attribute Ticket Type can have several values, as specified in the original PNR, such as AT, CY, EG, TC, TCN, TK, T-TK. The PNR Number specifies which PNR a particular ticket (a row of the Ticket table) is associated with. There can be several tickets per PNR.
  • Table 4 Table Ticket
  • Each of the tables Segment, Passenger, and Ticket is related to the Reservation table, because rows in those three tables correspond to specific reservations in the Reservation
  • SUBSTITUTESHEET(RULE28) table For example, one reservation contains zero or more flight segments while one flight segment can be associated with only one reservation.
  • This Reservation-to-Segment relationship is of type one-to-many. One reservation contains one or more passengers (in the sense described above) but one passenger can be associated with only one reservation.
  • This Reservation-to- Passenger relationship is of type one-to-many. One reservation contains zero or more tickets while one ticket can be associated with only one reservation.
  • This Reservation-to-Ticket relationship is also of type one-to-many.
  • the parsed PNRs as described above are sent from the functional server computer to the database server with appended SQL statements.
  • the SQL define the logical database schema, i.e. the four tables. Below, the SQL statements are represented by the terms Character, Date, Number, and String, where String represents an array of characters and stores text.
  • the last one or two lines of every definition specifies the primary key and possibly a foreign key for each table.
  • the primary key is attribute PNR Number.
  • the primary key is the combination of attributes PNR Number and Segment Number.
  • the primary key is the combination of attributes PNR Number and Passenger Number.
  • the primary key is attribute Ticket Number.
  • Tables Segment, Passenger, and Table each contain one foreign key (the last line of the definitions of those tables) .
  • the foreign key for each of the three tables is PNR Number. This is defined by specifying what table the foreign key references (each references table Reservation) .
  • Tables Segment, Passenger, and Table each contain one foreign key (the last line of the definitions of those tables) .
  • the foreign key for each of the three tables is PNR Number. This is defined by specifying what table the foreign key references (each references table Reservation) .
  • the SQL statement below finds reservations with specified reservation locator number. The term prefixed by a colon specifies an input variable, so PNR locator is used as input value. Note that PNR status is also returned so that we know whether the reservation is in error or not. The name of the first passenger is returned as well so that the end user can have more information when deciding what PNR to actually retrieve.
  • PNRLocator : PNRLocator
  • the end user may search for PNRs knowing the Ticket Number.
  • the SQL statement below finds reservations containing specified ticket number.
  • the statement joins tables Reservation, Ticket, and Passenger by equating the PNR Number attribute in all three tables. Ticket number is used as input value.
  • the end user may also search for PNRs knowing the Airline, Flight, Name, and Dates.
  • the SQL statement below finds reservations given passenger name, airline, departure and arrival city codes, and departure date(s) .
  • the statement joins tables Reservation, Segment, and Passenger by equating the PNR Number attribute in all .three tables. Airline code, flight number, name, begin date, and end date are used as in put values. Note that the name input value is pattern matched (by using the keyword Like) and not exactly equated. This is done so that even just partial names could be supplied to the search statement. Both Name and Departure Date attributes are also returned, to give the end user more information when making decision which PNR to actually retrieve.
  • the end user may search for PNRs knowing the airline, airports, name, and dates.
  • the SQL statement below finds reservations given passenger name, airline and flight number, and departure date(s) .
  • the statement joins tables
  • Airline code, departure city code, arrival city code, name, begin date, and end date are used as input values.
  • AirlineCode :AirlineCode
  • the end user may retrieve PNRs using the PNR number.
  • the statement below displays reservation selected from a list of reservations. PNR number is used as input value.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un système et un procédé de transfert, vers une plate-forme de base de données relationnelle, des données issues du progiciel de gestion de transactions (10) du système informatisé de réservation d'une compagnie aérienne. Le principe de ce système et de ce procédé consiste à mettre en oeuvre: un ordinateur source pour le traitement des transactions (12) d'un système informatisé de réservation, lequel ordinateur origine est en communication avec un fichier de données de sortie; une structure de données d'entrée; un ordinateur intervenant comme serveur fonctionnel (16); et un ordinateur cible hébergeant le système de gestion de base de données relationnelle. L'ordinateur cible hébergeant le système de gestion de base de données relationnelle est en communication, non seulement avec l'ordinateur intervenant comme serveur fonctionnel (16), mais aussi avec une base de données de sortie. Un dispositif de sélection (18) de transfert de données qui réside dans l'ordinateur utilisé comme serveur fonctionnel (16), est également en communication, non seulement avec l'ordinateur intervenant comme serveur fonctionnel (16), mais aussi avec l'ordinateur cible hébergeant le système de gestion de base de données relationnelle. Un module de gestion de fonctions, qui réside dans l'ordinateur intervenant comme serveur fonctionnel (16), est, quant à lui, en communication, non seulement avec l'ordinateur source utilisé pour le traitement des transactions (12), mais également avec l'ordinateur hébergeant le système de gestion de base de données relationnelle.
PCT/US1996/018463 1996-01-18 1996-11-15 Systeme de transfert de donnees des progiciels de gestion de transactions des compagnies aeriennes WO1997030404A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU30806/97A AU3080697A (en) 1996-01-18 1996-11-15 System for propagating airline tpf data
EP96946375A EP0832464A1 (fr) 1996-01-18 1996-11-15 Systeme de transfert de donnees des progiciels de gestion de transactions des compagnies aeriennes
EA199700372A EA199700372A1 (ru) 1996-01-18 1996-11-15 Система распространения данных средства обработки входных сообщений авиалинии

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US58843696A 1996-01-18 1996-01-18
US08/588,436 1996-01-18

Publications (1)

Publication Number Publication Date
WO1997030404A1 true WO1997030404A1 (fr) 1997-08-21

Family

ID=24353841

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1996/018463 WO1997030404A1 (fr) 1996-01-18 1996-11-15 Systeme de transfert de donnees des progiciels de gestion de transactions des compagnies aeriennes

Country Status (5)

Country Link
EP (1) EP0832464A1 (fr)
AU (1) AU3080697A (fr)
CA (1) CA2220126A1 (fr)
EA (1) EA199700372A1 (fr)
WO (1) WO1997030404A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002007001A2 (fr) * 2000-07-17 2002-01-24 Sabre Inc. Systeme, procede, et article fabrique destines a propager des donnees basees sur un systeme de traitement interactif et a fournir les donnees propagees a divers clients
EP1258823A2 (fr) * 2001-05-15 2002-11-20 NTT DoCoMo, Inc. Appareil, procédé, programme et support d'enregistrement d'information de vol lisible par ordinateur
WO2003014881A2 (fr) * 2001-08-09 2003-02-20 Saturn Internet Reservation Systems, Inc. Systeme de reservation sur internet de transport terrestre
EP1344141A1 (fr) * 2000-11-03 2003-09-17 Galileo International, Inc. Procede et systeme de suivi de selections d'un consommateur dans un reseau d'ordinateurs
US6714945B1 (en) 1995-11-17 2004-03-30 Sabre Inc. System, method, and article of manufacture for propagating transaction processing facility based data and for providing the propagated data to a variety of clients
US7668744B2 (en) 2003-07-31 2010-02-23 The Boeing Company Method and system for conducting fleet operations

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4875155A (en) * 1985-06-28 1989-10-17 International Business Machines Corporation Peripheral subsystem having read/write cache with record access
US5201046A (en) * 1990-06-22 1993-04-06 Xidak, Inc. Relational database management system and method for storing, retrieving and modifying directed graph data structures
US5225990A (en) * 1991-03-26 1993-07-06 Brals Limited Apparatus and methods for baggage reconciliation and location
US5253166A (en) * 1991-03-29 1993-10-12 Disc Corporation Pre-ticket travel reservation record keeping system
US5537533A (en) * 1994-08-11 1996-07-16 Miralink Corporation System and method for remote mirroring of digital data from a primary network server to a remote network server
US5560005A (en) * 1994-02-25 1996-09-24 Actamed Corp. Methods and systems for object-based relational distributed databases

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4875155A (en) * 1985-06-28 1989-10-17 International Business Machines Corporation Peripheral subsystem having read/write cache with record access
US5201046A (en) * 1990-06-22 1993-04-06 Xidak, Inc. Relational database management system and method for storing, retrieving and modifying directed graph data structures
US5225990A (en) * 1991-03-26 1993-07-06 Brals Limited Apparatus and methods for baggage reconciliation and location
US5253166A (en) * 1991-03-29 1993-10-12 Disc Corporation Pre-ticket travel reservation record keeping system
US5560005A (en) * 1994-02-25 1996-09-24 Actamed Corp. Methods and systems for object-based relational distributed databases
US5537533A (en) * 1994-08-11 1996-07-16 Miralink Corporation System and method for remote mirroring of digital data from a primary network server to a remote network server

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6714945B1 (en) 1995-11-17 2004-03-30 Sabre Inc. System, method, and article of manufacture for propagating transaction processing facility based data and for providing the propagated data to a variety of clients
WO2002007001A2 (fr) * 2000-07-17 2002-01-24 Sabre Inc. Systeme, procede, et article fabrique destines a propager des donnees basees sur un systeme de traitement interactif et a fournir les donnees propagees a divers clients
WO2002007001A3 (fr) * 2000-07-17 2003-04-24 Sabre Inc Systeme, procede, et article fabrique destines a propager des donnees basees sur un systeme de traitement interactif et a fournir les donnees propagees a divers clients
EP1344141A1 (fr) * 2000-11-03 2003-09-17 Galileo International, Inc. Procede et systeme de suivi de selections d'un consommateur dans un reseau d'ordinateurs
EP1344141A4 (fr) * 2000-11-03 2007-01-24 Galileo International Inc Procede et systeme de suivi de selections d'un consommateur dans un reseau d'ordinateurs
EP1258823A2 (fr) * 2001-05-15 2002-11-20 NTT DoCoMo, Inc. Appareil, procédé, programme et support d'enregistrement d'information de vol lisible par ordinateur
EP1258823A3 (fr) * 2001-05-15 2003-07-16 NTT DoCoMo, Inc. Appareil, procédé, programme et support d'enregistrement d'information de vol lisible par ordinateur
WO2003014881A2 (fr) * 2001-08-09 2003-02-20 Saturn Internet Reservation Systems, Inc. Systeme de reservation sur internet de transport terrestre
WO2003014881A3 (fr) * 2001-08-09 2003-12-04 Saturn Internet Reservation Sy Systeme de reservation sur internet de transport terrestre
US7668744B2 (en) 2003-07-31 2010-02-23 The Boeing Company Method and system for conducting fleet operations

Also Published As

Publication number Publication date
AU3080697A (en) 1997-09-02
EA199700372A1 (ru) 1998-06-25
CA2220126A1 (fr) 1997-08-21
EP0832464A1 (fr) 1998-04-01

Similar Documents

Publication Publication Date Title
US6122642A (en) System for propagating, retrieving and using transaction processing facility airline computerized reservation system data on a relational database processing platform
US7007275B1 (en) Method and apparatus for automatic execution of concatenated methods across multiple heterogeneous data sources
US6151624A (en) Navigating network resources based on metadata
US6856992B2 (en) Methods and apparatus for real-time business visibility using persistent schema-less data storage
US6651142B1 (en) Method and apparatus for processing data using multi-tier caching
US6374241B1 (en) Data merging techniques
US7562093B2 (en) Method for creating a stored query
US7788253B2 (en) Global anchor text processing
US7047242B1 (en) Weighted term ranking for on-line query tool
US6714945B1 (en) System, method, and article of manufacture for propagating transaction processing facility based data and for providing the propagated data to a variety of clients
US20020078015A1 (en) Database system with methodogy providing faster n-ary nested loop joins
US20050203940A1 (en) Database System with Methodology for Automated Determination and Selection of Optimal Indexes
WO1996023266A1 (fr) Systeme permettant a un utilisateur individuel d'effectuer des interrogations
US6374270B1 (en) Corporate disclosure and repository system utilizing inference synthesis as applied to a database
EP2264664A1 (fr) Échange d'actifs marketing
US20040083422A1 (en) System and method for automatically generating patent analysis reports
CN116034349A (zh) 列式分析存储格式的半结构化数据的概率文本索引
US8275661B1 (en) Targeted banner advertisements
US7559048B1 (en) System and method for managing objects between projects
US20040039755A1 (en) Metadata relationships
US7225202B2 (en) Method and apparatus for generating query and response statements at runtime from generic requests
EP0832464A1 (fr) Systeme de transfert de donnees des progiciels de gestion de transactions des compagnies aeriennes
US11645274B2 (en) Minimizing group generation in computer systems with limited computing resources
US7010539B1 (en) System and method for schema method
US20030204500A1 (en) Process and apparatus for automatic retrieval from a database and for automatic enhancement of such database

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AU CA JP SG US AM AZ BY KG KZ MD RU TJ TM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FI FR GB GR IE IT LU MC NL PT SE

WWE Wipo information: entry into national phase

Ref document number: 1996946375

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2220126

Country of ref document: CA

Ref document number: 2220126

Country of ref document: CA

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 199700372

Country of ref document: EA

WWP Wipo information: published in national office

Ref document number: 1996946375

Country of ref document: EP

NENP Non-entry into the national phase

Ref document number: 97529329

Country of ref document: JP

WWW Wipo information: withdrawn in national office

Ref document number: 1996946375

Country of ref document: EP