NZ553606A

NZ553606A - User interface for travel booking system

Info

Publication number: NZ553606A
Application number: NZ55360607A
Authority: NZ
Inventors: Young Ly; Jonathan Ackerman; Benjamin William King; Rahul Bhambhra; Andrew Edward Lewis; Ian David Shores
Original assignee: Air New Zealand Ltd
Priority date: 2007-03-02
Filing date: 2007-03-02
Publication date: 2009-07-31
Also published as: WO2008108666A1

Abstract

A user interface for a travel booking system is disclosed, the user interface enabling a user to query possible journey destinations and comprises: an icon that can be manipulated into a plurality of states, each state corresponding to a price requirement, a window adapted to display a map comprising possible journey destinations. Upon manipulating the icon into a state, the window is adapted to display a map and possible journey destinations on the map with respective journey prices meeting the price requirement corresponding to the icon state. A travel booking system for booking journey tickets is disclosed which comprises: a computer with a user interface as described above and a database in communication with the computer. The database contains information on journey destinations and journey prices, and the computer is adapted to receive information on one or more of the possible journey destinations from the database. The possible journeys relate to journey destinations with respective journey prices meeting the price requirement selected by a user, and the computer is adapted to display a map and the possible journey destinations on the map in the user interface.

Description

<div class="application article clearfix" id="description"> 5536p6 NEW ZEALAND PATENTS ACT, 1953 No: 553606 Date: 2 March 2007 COMPLETE SPECIFICATION USER INTERFACE We, AIR NEW ZEALAND LIMITED, 185 Fanshawe Street, Auckland, New Zealand, do hereby declare the invention for which we pray that a patent may be granted to us, and the method by which it is to be performed, to be particularly described in and by the following statement: Intellectual Property Office of N.Z. 2 9 FEB 2008 d c r p i \/ F D 5536^6 FIELD OF THE INVENTION The present invention relates to a method, user interface and system for use in conjunction with a travel booking system. BACKGROUND TO THE INVENTION Travel booking engines or systems are well known. They enable customers to self-book tickets for travel on a travel service, such as a bus, train or airline service. For example, the airline industry uses booking systems to enable customers to self-book airline rickets over the internet or other network. Customers can comprise retail customers and also wholesale or trade customers. A system enables a customer to enter details such as the desired origin, destination, and preferred dates of travel. The booking system then provides information on available flights that meet their requirements. The customer can then select one or more of the available options and proceed with booking tickets for the travel. Typically, the customer will access the booking system over the internet, although customers could access the system by other means, such as kiosks, dedicated terminals or the like. Existing travel booking systems are based on the premise that the user knows their desired origin, destination and a date or range of dates on which they wish to travel. SUMMARY OF THE INVENTION It is the object of the present invention to provide price as a desired parameter for selecting possible journeys. In one aspect the present invention may be said to consist in a user interface for a travel booking system, the user interface enabling a user to query possible journey destinations and comprising: an icon that can be manipulated into a plurality of states, each state corresponding to a price requirement, a window adapted display a map comprising possible journey destinations, wherein upon manipulating the icon into a state, the window is adapted to display a map and possible journey destinations on the map with respective journey prices meeting the price requirement corresponding to the icon state. Preferably, the price requirement corresponds to a journey price. Alternatively, the price requirement corresponds to a range of journey prices. More preferably, the price requirement corresponds to a maximum desired journey price or range of journey prices that a customer wishes to pay for a journey ticket to go to a journey destination. Preferably, if the icon is manipulated between states corresponding to different price requirements, the map in the window will zoom in and out in a corresponding manner for each state 5536^)6 to display a sufficient portion of the map to display the journey destinations with journey prices meeting the corresponding price requirement for that state. Preferably, a journey price meets the price requirement if it is less than or equal to the price requirement. Preferably, the journey is an available airplane flight and a journey price is the retail cost of a ticket for that available airplane flight. Preferably, the user interface further comprises an origin input that enables a user to input the desired journey origin. Preferably, the user interface further comprises a user input that enables the user to input a time period in which they wish to travel. Preferably, the window is adapted to display a map of one or more countries containing the journey origin and the journey destinations with respective journey prices meeting the price requirement corresponding to the icon state. The window also displays graphics indicating the possible journey origin/destinations combinations on the map, and other relevant information such as price, data/time availability and the like. More preferably, the window displays a line linking each possible journey origin/destination combination on the map. Preferably, if the user selects the displayed graphics corresponding to a possible origin/destination combination, further information relating to that possible origin/destination combination is displayed. Preferably, the further information relates to real-time data. Preferably, information on price of journey tickets on multiple dates is provided in graph form. Preferably, the prices forming part of the information are based on fare data and availability data that have been combined to produce a retail available price. More preferably, the user interface further comprises a means to allow the user to select a journey destination, and a booking screen for booking journey tickets will be displayed comprising information relating to the selected journey destination. Preferably, the user interface further comprises one or more icons each relating to a region or regions of the displayed map. When an icon is selected by a user, the window displays a map zoomed in or out to display the region or regions relating to the selected icon. In another aspect the present invention may be said to consist in a method for providing a user with possible journey destinations comprising the steps of: receiving user input via an icon, displaying the icon in one or more states based on the user input, each state corresponding to a price requirement, displaying a map and possible journey destinations on the map, the possible journey destinations having respective journey prices meeting the price requirement corresponding to the icon state. 553606 - 4 - 10 15 20 25 30 Preferably, displaying a map and journey destinations on the map comprises zooming the map in and out corresponding to the state of the displayed icon, wherein: i) the displayed map zooms out when the state of the icon corresponds to a price requirement associated with journey destinations spread over a larger geographical area, and ii) the displayed map zooms in when the state of the icon corresponds to a price requirement associated with journey destinations spread over a smaller geographical area. Preferably, the price requirement corresponds to a journey price. Alternatively, the price requirement corresponds to a range of journey prices. More preferably, the price requirement corresponds to a maximum desired journey price or range of journey prices that a customer wishes to pay for a journey ticket to go to a journey destination. Preferably, the journey is an available airplane flight and a journey price is the retail cost of a ticket for that available airplane flight. Preferably, a journey price meets the price requirement if it is less than or equal to the price requirement. Preferably, the method further comprises receiving user input specifying a journey origin. Preferably, the method further comprises displaying graphics indicating the possible journey origin/destinations combinations on the map, and other relevant information such as price, data/time availability and/or a line linking each possible journey origin/destination combination on the map. Preferably, the method further comprises receiving input identifying a possible origin/destination combination displayed on the map, and displaying further information relating to the identified possible origin/destination combination. More preferably, the method further comprises receiving input indicating a booking request, and displaying a booking screen for booking journey tickets comprising information relating to the selected journey destination. Preferably, the method further comprises displaying one or more icons each relating to a region or regions of the displayed map, receiving input identifying an icon, and displaying a map zoomed in or out to display the region or regions relating to the identified icon. A travel booking system for booking journey tickets comprising: a computer with a user interface, the user interface comprising an icon that can be manipulated by a user to select a price requirement, a database in communication with the computer, the database containing information on journey destinations and journey prices, wherein the computer is adapted to receive information on one or more of the possible journey destinations from the database, wherein the one or more of the possible journeys relate to and 553606 -5- journey destinations with respective journey prices meeting the price requirement selected by a user, and wherein the computer is adapted to display a map and the one or more possible journey destinations on the map in the user interface. In another aspect the present invention may be said to consist in a user interface for a travel booking system, the user interface enabling a user to find possible airplane flight destinations: an icon that can be manipulated into a plurality of positions, each position corresponding to maximum desired airplane ticket retail price, an origin input adapted to allow a user to input a desired origin for an airplane flight, a window adapted display a map comprising possible airplane flight destinations, wherein upon manipulating the icon into a state, the window is adapted to display a map comprising airplane flight destinations with respective airplane ticket retail prices equal to or less than the maximum desired airplane ticket retail price corresponding to the state, and wherein upon manipulating the icon into another state with a corresponding maximum desired airplane ticket retail price, the window displays a zoomed-out version of the map that comprises airplane flight destinations with respective airplane ticket retail prices equal to or less than the higher maximum desired airplane ticket retail price corresponding to the state, and wherein upon manipulating the icon into another state with a lower corresponding maximum desired airplane ticket retail price, the window displays a zoomed-in version of the map that comprises less airplane flight destinations with respective airplane ticket retail prices equal to or less than the higher maximum desired airplane ticket retail price corresponding to the state. In this specification where reference has been made to patent specifications, other external documents, or other sources of information, this is generally for the purpose of providing a context for discussing the features of the invention. Unless specifically stated otherwise, reference to such external documents is not to be construed as an admission that such documents, or such sources of information, in any jurisdiction, are prior art, or form part of the common general knowledge in the art The term "comprising" as used in this specification means "consisting at least in part of. Related terms such as "comprise" and "comprised" are to be interpreted in the same manner. To those skilled in the art to which the invention relates, many changes in construction and widely differing embodiments and applications of the invention will suggest themselves without departing from the scope of the invention as defined in the appended claims. The disclosures and the descriptions herein are purely illustrative and are not intended to be in any sense limiting. BRIEF DESCRIPTION OF THE DRAWINGS 553606 6 Preferred embodiments of the invention will be described with reference to the drawings, of which: Figure 1 is a block diagram indicating the typical form of a travel booking system adapted to provide price requirement searching, 5 Figure 2 is a flow chart of a method for obtaining journey destination options based on a user selected price requirement, Figure 3 is a screen shot of a user interface with an origin input facility, Figure 4 is a screen shot of a user interface showing a price requirement selector and a window adapted to display a map with possible journey destinations, 10 Figure 5 is a screen shot showing a first selected price requirement and a displayed map comprising journey destinations meeting the price requirement, Figure 6a is a screen shot showing a second, higher, selected price requirement and a displayed map showing additional regions comprising further journey destinations meeting the price requirement, 15 Figure 6b is a screen shot in which a region selector has been selected by a user, Figure 6c is a screen shot in which a zoomed-in map is displayed in the window comprising the selected region in Figure 6b, Figure 7a is a screen shot of a user interface showing a third, yet higher, selected price requirement and a displayed map showing additional regions comprising further journey destinations 20 meeting the price requirement, Figures 7b, 7c and 7d are screen shots showing further information for journey tickets of a selected journey destination, and Figure 8 is a screen shot of a booking interface. 25 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention provides a user interface, system and/or method that enables a customer to view available journey destinations with journey prices that meet the customer's price requirement. Typically, the price requirement will be a maximum price that the customer wants to pay for a journey. This enables a customer to choose a journey destination based on their available 30 budget, whereby they are provided with various journey destination options based on the price requirement they specify. The preferred embodiments of the present invention will be described in relation to plane travel, but it will appreciated that the invention could be readily applied to the services offered by providers in other travel industries, such as train, ferry or bus travel. In each case, the invention 35 provides a means by which a customer can be provided with journey destination options based on 553606 -7- their available budget. The customer can then choose to purchase or book tickets on the service that will take them to that destination (and where appropriate, back to the origin). It will be appreciated that the user interface, method and system according to a preferred embodiment of the invention could be an integral part of a newly developed or an existing travel 5 booking system, or alternatively be provided separately and retrospectively integrated with or used in conjunction with an existing travel booking system. Alternatively, the invention could be provided independently from a booking travel system. In this case, the invention would provide travel or journey options that could be booked via another means. However, it will be appreciated in a preferred embodiment the invention will comprise, be integrated with or otherwise be used in 10 conjunction with a travel booking system as this facilitates more efficient booking of desired travel. In general terms, a preferred embodiment of the invention provides a user interface with an icon that can be moved into a range of positions or states. Each of these positions or states corresponds to a price requirement (e.g. a desired maximum price that the user wishes to spend on travel). As the icon is moved between the various states, the user interface also displays a map 15 containing journey destinations that have a journey price that meet the price requirement indicated by the price requirement icon. Generally, the price requirement will be that the journey price is equal to or less than the price indicated by the icon state. It will be appreciated, however, that the price requirement could relate to some other relationship between the price indicated by the icon state, and journey prices. For example, the price requirement might be that the journey destinations 20 must have a journey price that is equal to the price requirement. As the positional state of the icon changes under user control, this will alter the selected price requirement and consequently alter the journey destinations with journey prices that meet the price requirement. For example, as the price requirement increases, it is likely that additional journey destinations, and journey destinations to more remote destinations, will become available for 25 that price requirement Therefore, as the price requirement increases, the map may "zoom-out" to show additional geographical regions that capture the additional journey destinations to more remote regions. Likewise, as the icon is moved to lower a price requirement, it is likely that less destinations, or destinations to only closer regions will be available for that price requirement. In this case, the map will be "zoomed-in" to show a smaller geographical region that more closely 30 relates to the journey destinations available for that price requirement. The price requirement can relate to return or one-way prices. In this specification, the term "journey destination" relates to a destination that can be reached by the mode of travel on offer by the travel service provider implementing the invention. For example, in the case of airline flight, this will relate to a city to which the airline flies. The term 35 "journey origin" relates to the starting point of a desired journey by a customer. These will generally relate to cities or other geographical regions. The term "journey ticket" relates to a ticket or similar 553606 -8- that can be purchased to permit travel on the offered travel service. In the case of an airline travel service, the journey ticket will be an airline ticket. The term "journey price" relates to the price (such as retail price) for a customer to buy a journey ticket to travel to the journey destination using the mode of travel offered by the travel service provider. For example, in the case of an airline 5 booking system, the journey price would relate to the price the customer pays for an airline ticket for a seat on a plane flying to a particular journey destination. It will be appreciated that the terms used have a range of similarly used terms in the industry, and the use of the terms here should be considered to cover any alternatively terminology used in the travel industry that means the same. A preferred embodiment of the invention will be described in detail with reference to the 10 Figures. Figure 1 shows a travel booking system 5 in generic schematic form. The general manner in which a travel booking system operates will be known to those skilled in the art. The general system 5 shown in Figure 1, however, is adapted to implement the present invention. In this case, the invention is implemented by integrating a graphical user interface or GUI 6 with an existing travel booking system 5. The system 5 comprises a booking system server 1, which is maintained by 15 the travel service or an agent, which is in communication with a travel database 2. The travel database 2 contains travel data or information on available journey tickets corresponding to journey destinations, along with other relevant information such as dates of availability, prices and the like. Details stored on the travel database 2 will be known to those skilled in the art. Customers can access the booking system server 1 over the internet 3 via a computer 4. The computer 4 has the 20 user interface 6 that enables the user to enter various data indicating their requirements for travel. Upon receiving travel requirement information via the interface 6, the computer 4 provides it to the booking system server 1 via the internet 3. The booking system server 1 queries the database 2 to retrieve travel data relating to available journey tickets for journey destinations that meet the customer entered requirements. The travel data (comprising available seats on the travel 25 service, along with journey destinations, price, date availability and the like) is then provided by the booking system server 1 to the customer via the internet 3 and the user interface 6. The travel data might specify several travel options. The customer can then select the desired options and a booking is made by the booking system server. The use of the user interface 6, which provides for price requirement searching will be 30 described in more detail with reference to the flow diagram in Figure 2 and the screens shots in Figures 3 to 7c. First, the computer displays a user interface 51, step 20, with a user input means 50 by which a user can input their desired journey origin. The user input means 50 in this case is a drop down menu showing a range of journey origins (Auckland, Christchurch, Dunedin, Hamilton and Wellington in New Zealand). However, it will be appreciated that the user input means 50 35 could be any other suitable user interface, such as a window, data entry field or the like. The user then selects their desired journey origin, step 21, using the user input means 50. The desired journey 5536j36 origin will typically be (although not necessarily) the user's home city or town. In this case, the city of Wellington is chosen as the journey origin. This input is received, step 22, by the computer 4 running the user interface. Next, as shown in Figure 4, the computer refreshes the user interface to display a price 5 requirement icon 52, step 23. Preferably, the icon is a slider that can slide between a range of positions or states between a minimum currency value, such as $0, to a maximum currency value, for example, $8000. Each icon state relates to a currency value, which corresponds to a price requirement for a journey price. The slider 52 or the user interface adjacent the icon might comprise indicia e.g. 52a, 52b indicating the currency value relating to each or some positions or states of the 10 icon. Multiple indicia could be provided. Further, the icon 52 itself might display the present currency value relating to the position or state the icon 52 is in. The user can input their desired price requirement by using a mouse or other device to control the position of the icon slider 52, and place it in a position or state corresponding to their desired price requirement. It will be appreciated that the icon 52 for setting the price requirement could take any suitable form. For example, as an 15 alternative, the price requirement icon could be a dial. The user interface also displays a map 53, step 23, comprising journey destinations meeting the price requirement. In the default case, when the price requirement icon set at $0, a default map is shown with no journey destinations indicated thereon, such as shown in Figure 4. Next, the user then selects their price requirement, step 24, using the price requirement icon 20 52. In the preferred embodiment, the price requirement will be the desired maximum price that a user wishes to pay for a journey ticket. Therefore, journey prices meeting that price requirement will be those that are equal to or less than the value of the currency value indicated by the price requirement icon 52. As noted above, the price requirement could specify some other relationship between a journey price and the selected price requirement. 25 As shown in Figure 5, the user in this case has selected a price requirement of $99 by moving the slider 52 accordingly. The icon 52 shows the selected currency value corresponding to the position of the icon, namely $99. In the general case, as the price requirement icon 52 is moved between positions from $0 to $8000 an indication of the selected currency value at any particular position is shown on the icon 52. A user is able to slide the icon 52 to any desired position relating 30 to their desired maximum price (i.e. price requirement). At step 24, the user could also enter a preferred flight period, using drop down menu 49. The user interface 6 and computer 4 receive this user input, step 25, and communicate with the travel database 2 over a communications network 3 to identify journey destinations with journey prices that meet the price requirement, step 26. In identifying such journey destinations, there is 35 also at least one seat available for purchase on a flight to that destination, the journey price relating to the purchase price of a ticket for one of those available seats. That is, in the preferred 5536C36 embodiment, the database will only return travel data for journey destinations that have available journey tickets. In this case, the journey destinations are cities with airports that are serviced by the airline . The database 2 will return travel data identifying the journey destinations meeting the price requirement, and also other pertinent information such as the date/time availability of journeys, the price of a journey ticket, special conditions and the like. The computer then operates, step 27, the user interface 51 to update a window 54 with a map 53 that contains the journey destinations 45a that have been identified. Further, the window 53 is updated to display graphics indicating the journey destinations on the map, preferably by way of travel lines 45b extending from the journey origin 45c to the various available journey destinations 45a. Journey destination names or other identifying indicia could also be provided on the map 53. The user interface 51 is also updated to show relevant information 46 relating to journey tickets, which can include information such as flight retail price, date/time availability of the flights, and other information. This information is based on the travel data obtained from the travel database 2. In this case, the journey destination and journey ticket information 46 is provided on the left hand side of the user interface 50. As can be seen, in this case, there are journey tickets available for the journey destinations Tauranga, Gisborne, Westport, Hamilton and Rotorua, which are all in New Zealand. Each destination is indicated by a line 45b on the map 53, and the price 46 of each available flight is also shown, along with the date of availability 46 and whether the price includes one way or return journey tickets 46. It will be appreciated that the journey and ticket information 46 could be provided in another form, such as on the map itself 53. Preferably, the information 46 is based on real-time data. Preferably, the prices forming part of the information 46 are based on fare data and availability data that have been combined to produce a retail available price. The user interface 51 also indicates the origin 47 in this case Wellington, New Zealand in a suitable graphical means, such as a text field. A drop down menu, or other suitable user input means 48 is provided such that the origin can be changed if required. Another user input means 49 is provided, which could be a drop down menu or other input means, that enables the customer to select a date or a range of dates or periods of time in which they wish to travel. In this case, the journey destinations that are shown on the map are restricted to those with available journey tickets for flights that are to be taken within the next five months. Other time periods, such as 1 week, 1 month, 1 year or the like could be selectable by the user. After the map has been displayed with journey destinations, step 27, the user can view the journey destinations 45a meeting the selected price requirement, step 28. At this point, the interface awaits for any further changes to the price requirement icon 52 made by the user. If a change is made, step 29, the input is received, step 22, and the steps 23 to 28 are reiterated. Referring to Figure 6a, in this case the screen shot shows that the customer has moved the price requirement icon 52 to a maximum desired price of $331, step 24. The user interface 6 and 553^6 computer 4 receive this input, step 25, and retrieve journey destinations with journey prices meeting the price requirement, step 26, from the travel database 2, as described previously. In this case, because the price requirement is higher ($331), a larger number of journey destinations have available journey tickets that meet the price requirement, in addition, many of these destinations are also further a field, including journey destinations in Australia, Norfolk Island and Tonga. The map 53 is redisplayed, step 27, or zoomed-out to show a larger geographical area that captures all the journey destinations with journey prices that meet the $331 price requirement. The travel information relating to journey tickets for the journey destinations is updated 46. This includes journey information for Sydney, Melbourne and Brisbane in Australia, Norfolk Island and also Tonga. The journey information area 46 on the user interface 51 also comprises a slider or other icon 55 that enables scrolling of the area to show additional information or further journey destinations 45a that cannot be displayed. In a preferred embodiment of the invention, it should be noted that as the price requirement icon 52 is moved between various positions, the map that is displayed is zoomed in and out as appropriate to display a sufficient geographical area that captures all the journey destinations that have journey prices meeting the price requirement. Generally, as the price requirement icon is moved to positions with higher price requirements, the number of available journey destinations will increase, and will generally comprise destinations that are further a field from the origin. As such, the map 53 that is displayed will be zoomed-out to capture all the journey destinations as the icon is positioned to increase the price requirement. In contrast, as the price requirement icon is moved through a range of positions to a lower price requirement, it is likely that the journey destinations will be closer to the origin 45c. Therefore, the displayed map 53 will be zoomed-in to cover just the geographical area covering the journey destinations with journey prices meeting the lower price requirement. Preferably, the zooming in and out will be dynamically linked to the position of the price requirement. That is, as the price requirement icon is moved, the map will dynamically zoom in and out accordingly. As can be seen in Figure 6a, the user interface 51 also displays (as part of step 27) region icons 56 relating to regions that may be displayed on the map 53. By clicking on one of the region icons 56, step 30, the computer 4 will receive the input 31 and will redisplay the map 53, step 32. The map 53 will be redisplayed to zoom-in on the regions selected, displaying more detail of the journey destinations 45a that are available in that region for the selected price requirement. For example, referring to Figure 6b, in this case the user has selected the Australian region icon 56, and referring to Figure 6c, the map is redisplayed to show a zoomed-in version of Australia, showing more detail of journey destinations at Brisbane, Sydney and Melbourne. The journey information 46 area is updated to show just the journey information 46 relating to the zoomed-in region. In addition, journey information 57 is also shown graphically on the map 53. 553^6 Figure 7a shows a further screen where the price requirement icon 52 has been moved, step 24, to a position relating to a price requirement of $2540. This increases the number of journey destinations 45a with available journey tickets meeting the journey price requirement. In this case journey destinations exist in North America and Asia. The journey information portion of the 5 screen displays journey information 46 for Vancouver, Las Vegas and San Francisco, Los Angeles in the US, and Ho Chi Minh City in Vietnam. Further travel information can be viewed by controlling the scroll slider 55. A larger number of region icons 56 are now displayed corresponding to the regions that are displayed in the zoomed-out map 51. It would be possible to view in further detail any one of the regions by clicking on the appropriate regional icon 56, step 30, such that the map 10 displayed, step 32, is a zoomed-in version of that selected region. Referring to Figure 7b, it is possible to obtain further information on any one of the journey destinations 45a by manoeuvring a cursor or other pointing device over the journey destination, or the line 45b linking the journey destination with the journey origin 45c, step 33. Upon doing so, the computer receives the input, step 34, and retrieves further travel data relating to the journey 15 destination, step 35. This might be travel data that was previously retrieved and stored locally on the computer 4, or alternatively, the further travel data could be retrieved via the booking system server 1. The travel data comprises information such as available journey tickets to the destination, availability times/dates, price and the like. Referring to Figure 7c, the computer 4 then displays the further travel data, step 36, in the 20 user interface 6. The information is preferably displayed in a window 60. In this case, further details have been provided for the Las Vegas journey, including the flight date availability and the flight price. Further, the window 60 provides the option to view other flights for the journey destination on other dates. Upon doing so, a graph is displayed in another window 61 (as shown in Figure 7c) that indicates other available flights to Las Vegas, the dates of availability and the lowest available 25 fare. This graph 61 shows a breakdown of the flight availability and cost for the next six months (or other time period that is selected by the user). Referring to Figure 7d, the user can zoom-in on the particular region by clicking on the "US West Coast" region icon 56. Once the information is displayed in windows 60, 61, the user views the information, step 37. At that point, step 38 they can select another journey destination to view information, step 33, 30 or they can select the one of the available journey tickets, step 39, for booking. The user interface 51 provides a suitable user input means for indicating that the user wants to book a particular journey ticket, such as an icon, or by selecting the "view flights" link in windows 60 or 61. The computer 4 receives input, step 40, indicating this selection, and then displays a booking screen 80, step 41 as shown in Figure 8. The booking screen is the existing booking screen of the system 5. 35 The screen is populated with journey ticket details 81 of the user selected journey ticket, such as flight date/time, flight number, price, number of passengers and the like. Other information could 553606 -13- also be provided. The user can then enter other details that are necessary, such as payment details, personal details and the like, and then confirm the booking (e.g. by clicking the "GO" icon 82), step 42. The computer 4 receives this input, step 43 and the carries out the operations required to actually book the journey ticket for the user, step 44. This comprises communicating with the 5 booking system server 1, the booking system server then carrying out the steps to book the flight, in a manner that will be known to those skilled in the art. It should be noted that the method described in relation to Figure 2 shows the general steps, and it should not be considered that all the steps have to be carried out in the order described. The user has the option to change any of the inputs (price requirement, origin, time period, journey 10 ticket selection) at any time and generally in alternative orders. The flow chart merely shows the usual order in which the selections would be made. Further, the selection of the origin 47 and/or time period 49 for available flights is optional. It is possible for these to be set as a default, without user input. For example, the computer 4 might decide on the user's location and use this as the default origin. The time period 49 might be set as a 15 default. The preferred embodiment could be extended to cover not just journey tickets for journey destinations, but also other add-ons, such as accommodation, transfers, car hire, activities and the like. Options could be provided that have costs that meet the price requirement. These could be displayed independently, based on an additional price requirement icon for add-ons. Alternatively, 20 they could be displayed based on the primary price requirement icon, wherein the total package of journey tickets plus add-ons must meet the price requirement. It will be appreciated that the interface could be configured to display destinations where the return journey price meets the price requirement. Alternatively, it could display destinations where the one-way price meets the price requirement. </div>

Claims

<div class="application article clearfix printTableText" id="claims"> WHAT WE CLAIM IS: 553606 - 14-

1. A user interface for a travel booking system, the user interface enabling a user to query possible journey destinations and comprising: 5 an icon that can be manipulated into a plurality of states, each state corresponding to a price requirement, a window adapted to display a map comprising possible journey destinations, wherein upon manipulating the icon into a state, the window is adapted to display a map and possible journey destinations on the map with respective journey prices meeting the price 10 requirement corresponding to the icon state.

2. A user interface according to claim 1 wherein the price requirement corresponds to a journey price or range of journey prices. 15

3. A user interface according to claim 2 wherein the price requirement corresponds to a maximum desired journey price or range of journey prices that a customer wishes to pay for a journey ticket to go to a journey destination.

4. A user interface according to claim 1 wherein when the icon is manipulated between states 20 corresponding to different price requirements, the map in the window will zoom in and out in a corresponding manner for each state to display a sufficient portion of the map to display the journey destinations with journey prices meeting the corresponding price requirement for that state.

5. A user interface according to claim 4 wherein a journey price meets the price requirement if 25 it is less than or equal to the price requirement.

6. A user interface according to claim 5 wherein the journey is an available airplane flight and a journey price is the retail cost of a ticket for that available airplane flight. 30

7. A user interface according to claim 6 wherein the user interface further comprises an origin input that enables a user to input the desired journey origin.

8. A user interface according to claim 7 wherein the user interface further comprises a user input that enables the user to input a time period in which they wish to travel. 35 553606 - 15-

9. A user interface according to claim 8 wherein the window is adapted to display a map of one or more countries containing the journey origin and the journey destinations with respective journey prices meeting the price requirement corresponding to the icon state. 5

10. A user interface according to claim 9 wherein the window also displays graphics indicating the possible journey origin/destinations combinations on the map, and other relevant information such as price, data/time availability.

11. A user interface according to claim 10 wherein the window displays a line linking each 10 possible journey origin/destination combination on the map.

12. A user interface according to claim 11 wherein if the user selects the displayed graphics corresponding to a possible origin/destination combination, further information relating to that possible origin/destination combination is displayed. 15

13. A user interface according to claim 12 wherein the further information relates to real-time data.

14. A user interface according to claim 13 wherein the information on price of jovirney tickets 20 on multiple dates is provided in graph form.

15. A user interface according to claim 14 wherein the prices forming part of the information are based on fare data and availability data that have been combined to produce a retail available price. 25

16. A user interface according to claim 14 wherein the user interface further comprises a selector to allow the user to select a journey destination, and a booking screen for booking journey tickets the booking screen comprising information relating to the selected journey destination. 30

17. A user interface according to claim 16 wherein the user interface further comprises one or more icons each relating to a region or regions of the displayed map and wherein when an icon is selected by a user, the window displays a map zoomed in or out to display the region or regions relating to the selected icon. 35

18. A method for providing a user with possible journey destinations comprising the steps of: receiving user input via an icon, 5536|5g displaying the icon in one or more states based on the user input, each state corresponding to a price requirement, displaying a map and possible journey destinations on the map, the possible journey destinations having respective journey prices meeting the price requirement corresponding to the 5 icon state.

19. A method according to claim 18 wherein displaying a map and journey destinations on the map comprises zooming the map in and out corresponding to the state of the displayed icon, wherein: 10 l) the displayed map zooms out when the state of the icon corresponds to a price requirement associated with journey destinations spread over a larger geographical area, and ii) the displayed map zooms in when the state of the icon corresponds to a price requirement associated with journey destinations spread over a smaller geographical area. 15

20. A method according to claim 19 wherein the price requirement corresponds to a journey price or a range of journey prices.

21. A method according to claim 20 wherein the price requirement corresponds to a maximum desired journey price or range of journey prices that a customer wishes to pay for a journey ticket to 20 go to a journey destination.

22. A method according to claim 21 wherein the journey is an available airplane flight and a journey price is the retail cost of a ticket for that available airplane flight. 25

23. A method according to claim 22 wherein a journey price meets the price requirement if it is less than or equal to the price requirement.

24. A method according to claim 23 wherein the method further comprises receiving user input specifying a journey origin.

25. A method according to claim 24 wherein the method further comprises displaying graphics indicating the possible journey origin/destinations combinations on the map, and other relevant information such as price, data/time availability and/or a line linking each possible journey origin/destination combination on the map. 30 553(|Qj3

26. A method according to claim 25 wherein the method further comprises receiving input identifying a possible origin/destination combination displayed on the map, and displaying further information relating to the identified possible origin/destination combination. 5

27. A method according to claim 26 wherein the method further comprises receiving input indicating a booking request, and displaying a booking screen for booking journey tickets comprising information relating to the selected journey destination.

28. A method according to claim 27 wherein the method further comprises displaying one or 10 more icons each relating to a region or regions of the displayed map, receiving input identifying an icon, and displaying a map zoomed in or out to display the region or regions relating, to the identified icon.

29. A travel booking system for booking journey tickets comprising: 15 a computer with a user interface, the user interface comprising an icon that can be manipulated by a user to select a price requirement, and a database in communication with the computer, the database containing information on journey destinations and journey prices, 20 wherein the computer is adapted to receive information on one or more of the possible journey destinations from the database, wherein the one or more of the possible journeys relate to journey destinations with respective journey prices meeting the price requirement selected by a user, and wherein the computer is adapted to display a map and the one or more possible journey 25 destinations on the map in the user interface.

30. A user interface for a travel booking system, the user interface enabling a user to find possible airplane flight destinations: an icon that can be manipulated into a plurality of positions, each position corresponding to 30 maximum desired airplane ticket retail price, an origin input adapted to allow a user to input a desired origin for an airplane flight, a window adapted display a map comprising possible airplane flight destinations, wherein upon manipulating the icon into a state, the window is adapted to display a map comprising airplane flight destinations with respective airplane ticket retail prices equal to or less 35 than the maximum desired airplane ticket retail price corresponding to the state, and 553606 - 18- wherein upon manipulating the icon into another state with a corresponding maximum desired airplane ticket retail price, the window displays a zoomed-out version of the map that comprises airplane flight destinations with respective airplane ticket retail prices equal to or less than the higher maximum desired airplane ticket retail price corresponding to the state, and 5 wherein upon manipulating the icon into another state with a lower corresponding maximum desired airplane ticket retail price, the window displays a zoomed-in version of the map that comprises less airplane flight destinations with respective airplane ticket retail prices equal to or less than the higher maximum desired airplane ticket retail price corresponding to the state. DATED THIS 3 DAY OP AJ par^ .^ PER . AGENTS FOR TH^sAFPLICANT Intellectual Property A Office of N.Z. 1 29 FIB 2008 received </div>