WO2002005189A1 - Transfert d'informations de voyage personnalisées - Google Patents

Transfert d'informations de voyage personnalisées Download PDF

Info

Publication number
WO2002005189A1
WO2002005189A1 PCT/US2001/021709 US0121709W WO0205189A1 WO 2002005189 A1 WO2002005189 A1 WO 2002005189A1 US 0121709 W US0121709 W US 0121709W WO 0205189 A1 WO0205189 A1 WO 0205189A1
Authority
WO
WIPO (PCT)
Prior art keywords
traveler
information
electronic receiver
travel
itinerary information
Prior art date
Application number
PCT/US2001/021709
Other languages
English (en)
Inventor
Eric Schorman
Original Assignee
Motorola, 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 Motorola, Inc. filed Critical Motorola, Inc.
Priority to AU2001280502A priority Critical patent/AU2001280502A1/en
Publication of WO2002005189A1 publication Critical patent/WO2002005189A1/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 pertains to personal travel information for a traveler and more particularly, the invention relates to a method and apparatus for distributing and receiving travel information for the traveler.
  • a system which will automatically transfer travel information regarding departure and arrival times, including gate information, to a traveler.
  • a system is required which will automatically transfer the same information to those aw.aiting the arrival of a traveler, or those scheduled to transport the traveler to/from the airport, for example.
  • FIG. 1 is a diagram illustrating a distribution of travel itinerary information, according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of an electronic mail message notifying a traveler of a scheduled itinerary and the corresponding gate and terminal information, according to an embodiment of the present invention.
  • FIG. 3 is a diagram illustrating an example of an electronic mail message notifying a traveler of an itinerary schedule change and the corresponding new gate and terminal information, according to an embodiment of the present invention.
  • FIG. 4 is a diagram illustrating an example of an electronic mail message notifying a secondary party of a traveler's itinerary and corresponding gate information, according to an embodiment of the present invention.
  • FIG. 5 is a flow chart illustrating a distribution of travel itinerary information, according to an embodiment of the present invention.
  • FIG. 1 is a diagram illustrating a method of delivering travel itinerary information, including, for example, gate and terminal information.
  • a travel server 100 stores information encompassing, for example, a traveler profile, an itinerary of a traveler 142, and airline schedules in a travel storage device 110. This information is transferred to/from travel storage device 110 via communication channel 104.
  • the traveler profile may include information regarding the traveler, such as, credit card information, seat preferences, meal preferences, phone numbers, pager addresses, and electronic mail addresses, for example.
  • Travel server 100 may be controlled by a travel agency 130; alternatively, travel server 100 may be controlled by other travel service providers, such as airlines (not illustrated), or train and bus providers (not illustrated), for example.
  • a traveler provider 120 may provide travel information via a communication channel 122 to travel server 100.
  • This travel information may include, for example, schedules of air flights, and may also indicate changes in a previous flight, terminal, and gate schedules.
  • the information stored by traveler server 100 has been indicated as including the traveler profile and/or itinerary information, it is not limited thereto and could store additional information.
  • traveler 142 will make reservations with a travel agency 130 via communication channel 144 such as the public switched telephone network or the internet. Accordingly, travel agency 130 will coordinate, via a communication channel 132, scheduling of traveler's itinerary (not illustrated) with travel server 100 and with schedules provided by travel provider 120. When an itinerary is finalized, traveler 142 will typically be notified through a computer communication channel 152, for example, via paging system 150 by travel server 100 of up-to-date flight information, including, for example, terminal and gate information, if available.
  • travel server 100 will typically be notified through a computer communication channel 152, for example, via paging system 150 by travel server 100 of up-to-date flight information, including, for example, terminal and gate information, if available.
  • Traveler 142 may manually request flight information by sending a request by a communication channel 144, such as a telephone, electronic mail, or web request, for example to travel agency 130 or directly to the travel server 100. Alternatively, traveler 142 may be automatically notified as follows. At a predetermined time before the scheduled flight-departure time, travel server 100 will automatically transfer to a traveler receiver 140, via paging system 150, the then up-to-date flight information, including, for example, gate information, if available.
  • a communication channel 144 such as a telephone, electronic mail, or web request
  • travel server 100 will automatically transfer to a traveler receiver 140, via paging system 150, the then up-to-date flight information, including, for example, gate information, if available.
  • traveler receiver 140 may be, for example, a personal digital assistant . (PDA), a cell telephony device, or a pager.
  • traveler receiver 140 may be a desktop computer or device with the capability of receiving electronic mail.
  • Traveler receiver 140 of traveler 142 should at least include communication receivers for receiving information directed to the traveler, such as by way of the traveler's electronic mail address or pager number, for example.
  • the aforementioned automatic notification feature would preferably include, for example, notification being performed by a computer in an automated manner.
  • travel server 100 might notify traveler 142 at one or two hours prior to the scheduled departure time the aforementioned up-to-date flight information, although different predetermined notification times could be requested by traveler 142.
  • Travel server 100 may then notify traveler 142 of up-to-date flight information, via an email or pager address, for example, which is stored as a part of the traveler profile. Traveler 142 may also be notified via a method other than electronic mail or pages.
  • the aforementioned computer communication channels 152 and 153 represent a transfer of computer understandable communications via a communication channel.
  • travel server 100 will notify traveler 142 automatically upon a change of, for example, departure time, terminal, or gate. Further, notifications to traveler 142 may be purged from paging system 150 and travel server 100 after the travel has commenced or been canceled, for example.
  • Secondary parties 160 may not need all the information needed by traveler 142, or may actually need additional information stored in the traveler profile.
  • Typical secondary parities 160 may include, but are not limited to, a spouse, boss, service companies, such as limousine or car rental companies, or even hotels.
  • travel server 100 automatically notifies secondary party 160, via communication channel 102, paging system 150 and computer communication channel 153, of pertinent information such as departure or arrival times, estimated arrival times, and corresponding gate information, for example.
  • pertinent information such as departure or arrival times, estimated arrival times, and corresponding gate information, for example.
  • traveler 142 may determine what additional information is necessary for each of the secondary parties 160.
  • secondary parties may also receive the aforementioned automatic predetermined time notifications and automatic scheduling change notifications. This allows for a traveler's boss or spouse, for example, or any other entity the traveler chooses, to be kept abreast of the traveler's travel plans and current status.
  • secondary parties 160 can include service companies for example, limousine companies, car rental companies, or hotels, for example, these secondary parties 160 can be kept updated of the arrival or departure of traveler 142.
  • a limousine company may decide, based on received itinerary information, when to arrive to take traveler 142 to the airport or when to pick up traveler 142 from the airport, and at which gate.
  • travel server 100 has access to the traveler profile, similarly notified hotels, for example, may make special accommodations, such as a preferred check-in or special meals.
  • a preferred type of car could be available at the car rental company upon arrival of traveler 142.
  • each secondary party could be kept abreast of potential delays or even cancellations.
  • preferred customer benefits for different service companies can be stored in the traveler profile so all potential appropriate benefits can be collated, properly accumulated, and potentially applied to the traveler's corresponding service company.
  • the different service companies additionally may be given traveler's electronic mail address, phone number, or the like, for direct communication with traveler 142.
  • traveler 142 may indicate in the traveler profile that certain notifications to certain secondary parties 160 may be permanently requested, or may only be requested for onetime events.
  • electronic mail or pager addresses, for example, of certain secondary parties may be stored in the traveler profile, or may be available, for example, through databases and lists available to travel server 100. Additional methods of communicating the travel information to the secondary parties may be available and may be indicated within the traveler profile.
  • FIG. 2 is a diagram illustrating an embodiment where traveler 142 receives an electronic message, through computer communication channel 152, from paging system 150 (as shown in FIG. 1).
  • the electronic mail message indicates the traveler's itinerary, including terminal and gate data.
  • FIG. 3 is a diagram illustrating an embodiment where the traveler receives an additional electronic message indicating an itinerary change and potential gate and terminal change information.
  • FIG. 4 is a diagram illustrating the aforementioned secondary party notification.
  • a secondary party 160 has been electronically mailed the traveler name, itinerary, terminal, and gate information.
  • the limousine would be able to promptly arrive to take traveler 142 to the airport, for example, or promptly arrive at the airport, for example, to take traveler 142 to additional destinations.
  • FIG. 5 is a flow chart illustrating a distribution of travel itinerary information, according to an embodiment of the present invention.
  • travel server 100 begins the notification process by collating travel schedules from travel provider 100 with the traveler profile and itinerary of traveler 142 in operation 300. From operation 300, the process moves to operation 305, where traveler 142 is notified at a predetermined time before the beginning time of the traveler's itinerary. From operation 305, the process moves to operation 310, where it is determined whether there are secondary parties 160 that should also be notified.
  • the process moves from operation 310 to operation 315, where traveler server 100 determines, based on the traveler profile, what information each secondary party 160 should receive.
  • the process moves to operation 320, where the secondary parties 160 are notified at a predetermined time that may differ from the predetermined time at 305. After notifying secondary parties 160 in operation 320, or if travel server 100 determines that there are no secondary parties, the process moves to operation 325 where it is determined whether there has been a change in the traveler's itinerary.
  • the process moves to operation 330, where the traveler is notified of the change. If the travel server 100 determines that there is no change in the traveler's itinerary, the process moves to operation 350, where travel server 100 determines whether the traveler's itinerary is complete. If travel server 100 in operation 350 determines that the traveler's itinerary is not complete, then the process moves to operation 325, where traveler server 100 determines whether there is a change in the traveler's itinerary.
  • the process moves to operation 335, where travel server 100 determines whether the traveler profile indicates that there are any secondary parties 160. If there are secondary parties that need to be notified, the process moves to operation 340, where traveler server 100 determines what information each secondary party 160 is to receive. From operation 340, the process moves to operation 345, where traveler server 100 notifies the secondary party 160 of information related to the change in traveler's itinerary. From operation 345, the process moves to operation 350, where travel server 100 determines whether the itinerary is complete.
  • the process moves to operation 325, where travel server 100 determines whether there are changes in the traveler's itinerary, otherwise the process moves to operation 355, where travel server 100 may purge the traveler's itinerary from travel server 100 operations and cease the notification process.
  • FIG. 3 The flow chart of FIG. 3 is merely one embodiment, thus there could be a multitude of potential processes that could be implemented by one of ordinary skill in the art to accomplish similar notification goals.
  • the communication channels 132, 122, 104, 102, 144 and computer communication channels 152 and 153, shown in FIG. 1 may employ, but are not limited thereto, a multitude of communication environments, including, for example, the Internet, wireless networks, local area networks, wide area networks, optical communication networks, telephonic networks, or the like.
  • notifications between paging system 150 of FIG. 1 have been disclosed as employing computer communication channels such as electronic mail or paging systems, many different methods of communication would be acceptable, including automated telephonic messaging, wireless telephone messaging, two-way paging, and the like.
  • FIG. 1 utilizes a travel agency
  • embodiments of the present invention may also be employed by transportation companies directly, such as an airline or railway companies, or the like. Further, it is envisioned that non-transportation companies may also implement the above-disclosed embodiments.

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)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé pour la remise d'information d'itinéraire de voyage. En l'occurrence, un serveur de voyages (100) conserve en mémoire un itinéraire d'un voyageur (142) ainsi que des horaires de transporteurs aériens dans une mémoire de voyages (110). On utilise un canal de communication (104) pour transférer cette information. Le serveur de voyages (100) peut être géré par une agence de voyage (130) ou tout autre fournisseur de services de voyages (120). En règle générale, c'est le voyageur (142) qui fait ses réservations auprès d'une agence de voyages (130) via le canal de communication (144). Il revient alors à l'agence de voyage (130) de coordonner le serveur de voyages (100) pour échéancer un itinéraire destiné au voyageur (142). Lorsque l'itinéraire est confirmé, le voyageur (142) reçoit notification, via un système de radiomessagerie (150), des informations mises à jour concernant le vol tel que le terminal et la porte.
PCT/US2001/021709 2000-07-11 2001-07-10 Transfert d'informations de voyage personnalisées WO2002005189A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001280502A AU2001280502A1 (en) 2000-07-11 2001-07-10 Transfer of personalized travel information

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US61392000A 2000-07-11 2000-07-11
US09/613,920 2000-07-11

Publications (1)

Publication Number Publication Date
WO2002005189A1 true WO2002005189A1 (fr) 2002-01-17

Family

ID=24459209

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/021709 WO2002005189A1 (fr) 2000-07-11 2001-07-10 Transfert d'informations de voyage personnalisées

Country Status (2)

Country Link
AU (1) AU2001280502A1 (fr)
WO (1) WO2002005189A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
WO2011042914A1 (fr) * 2009-10-09 2011-04-14 Prakash Rohra Chaîne de télévision destinée à fournir des informations relatives à des compagnies aériennes
US9916564B1 (en) 2009-01-27 2018-03-13 Robert A. Johns Computer-based systems and methods for collaborative travel planning

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5953706A (en) * 1996-10-21 1999-09-14 Orissa, Inc. Transportation network system
US6009408A (en) * 1996-04-01 1999-12-28 Electronic Data Systems Corporation Automated processing of travel related expenses
US6094640A (en) * 1993-06-08 2000-07-25 The Pugliese Company Electronic ticketing and reservation system and method
US6122620A (en) * 1997-02-20 2000-09-19 Sabre Inc. System for the radio transmission of real-time airline flight information

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6094640A (en) * 1993-06-08 2000-07-25 The Pugliese Company Electronic ticketing and reservation system and method
US6009408A (en) * 1996-04-01 1999-12-28 Electronic Data Systems Corporation Automated processing of travel related expenses
US5953706A (en) * 1996-10-21 1999-09-14 Orissa, Inc. Transportation network system
US6122620A (en) * 1997-02-20 2000-09-19 Sabre Inc. System for the radio transmission of real-time airline flight information

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
US9916564B1 (en) 2009-01-27 2018-03-13 Robert A. Johns Computer-based systems and methods for collaborative travel planning
WO2011042914A1 (fr) * 2009-10-09 2011-04-14 Prakash Rohra Chaîne de télévision destinée à fournir des informations relatives à des compagnies aériennes

Also Published As

Publication number Publication date
AU2001280502A1 (en) 2002-01-21

Similar Documents

Publication Publication Date Title
US8355936B2 (en) Managing a travel itinerary
US6496568B1 (en) Method and apparatus for providing automated notification to a customer of a real-time notification system
CN100358249C (zh) 通过无线网络传送内容的方法和系统以及该无线网络
US7792634B2 (en) Flight information reminder system and method
US6898569B1 (en) Method and apparatus for advanced scheduling and messaging system
CA2282294C (fr) Systeme pour reseau de transport
US5648900A (en) Method and apparatus for controlling and monitoring group travel related services
US20020178022A1 (en) Method and apparatus for message escalation by digital assistants
US20030078978A1 (en) Firmware portable messaging units utilizing proximate communications
US20130185394A1 (en) Providing Information to a Computing Device Based on Known Location and User Information
US20020115430A1 (en) Motion dispatch system
JP2004531829A (ja) ロケーションおよびリソースに基づくインテリジェント・キャッシングおよびネットワーク管理
US20040048604A1 (en) Advertisement services on mobile terminals
EP2282291A1 (fr) Système et procédé de gestion des informations d'utilisateur
US20150294237A1 (en) System and method for simultaneously displaying non-scheduled and scheduled air travel services for booking flights
CN101241612A (zh) 一种自助值机的方法及系统
US20020156854A1 (en) Electronic mail management method and management system
US20060258334A1 (en) Wireless paging system
US20130066659A1 (en) Travel arrangement service and methods of determining alternative routes
US7603281B1 (en) Method, computer program, and system for pushing flight information to passengers
US20130227040A1 (en) Method and system for sending messages
US20030009360A1 (en) System and process for providing better car service from car services companies
EP1096405A2 (fr) Système électronique sans fil pour l'assistance de voyage
WO2002005189A1 (fr) Transfert d'informations de voyage personnalisées
US20060047541A1 (en) Method and system for real-time booking by an electronic document

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

ENP Entry into the national phase

Country of ref document: RU

Kind code of ref document: A

Format of ref document f/p: F

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP