Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/24—Querying
  • G06F16/248—Presentation of query results
• • 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
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/24—Querying
  • G06F16/245—Query processing
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
  • G06F16/24—Querying
  • G06F16/245—Query processing
  • G06F16/2457—Query processing with adaptation to user needs
  • G06F16/24575—Query processing with adaptation to user needs using context
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
  • G06F16/953—Querying, e.g. by the use of web search engines
  • G06F16/9535—Search customisation based on user profiles and personalisation

Definitions

• a user can use various websites to plan their trips. Conventionally, a user browses a website corresponding to a particular provider (for example a specific airline) or a web-based travel site that provides access to several different providers. Once the user has identified a travel itinerary, he can typically purchase the itinerary directly from the website.
• a provider for example a specific airline
• a web-based travel site that provides access to several different providers.
• This application describes technologies relating to the search for information.
• an aspect of the subject described in the present application may be implemented in methods that include the steps of receiving a search request in a search interface; determine that the search query is a query associated with flights; and in response to determining that the search query is a flight associated query, and without additional user input, providing a flight search interface including a plurality of search dimensions and a plurality of flight search results, each dimension being associated with a flight search attribute and each dimension having an associated value, one or more dimension values corresponding to values retrieved from the search query, and the plurality of flight search results being filtered according to the values of dimension.
• Other embodiments of this aspect include corresponding systems, apparatus, and computer programs stored on computer storage devices, each configured to perform process operations.
• One or more of the plurality of dimensions may be associated with default values.
• the step of determining that the search request received is a request associated with flights may be based on the processing of the received search request.
• One or more of the values associated with the dimensions may be adjusted according to the user input.
• the method may further include the step of receiving the user input adjusting one of the default values; and automatically update the flight search results in response to the user input.
• Determining that the search query is a request associated with flights may include identifying one or more keywords associated with flight search requests.
• the flight search results are updated automatically in response to additional user input modifying one or more dimension values.
• the method may further include the steps of: providing a link to one or more third party booking sites in response to the user selecting one or more flight search results.
• the flight search interface may include a portion of dimensions and a portion of flight search results.
• the dimension portion can include an interactive map and the user can change an origin or destination value by an entry on a map.
• the size portion may include a scattergram of flights displaying flights relative to a pair of dimensions.
• the method may further include the steps of receiving a user input modifying a marker position associated with one or more of the dimension pairs in the diffusiogram; and updating the flight search results according to the flights in the region of the diffusiogram demarcated by the user input.
• a first dimension of the pair may be a price, and a second dimension of the pair may be a duration.
• the method may further include the steps of receiving a user input selecting a particular flight search result; and in response to the selection, presenting one or more associated return flight search results.
• the step of presenting one or more associated return flight search results may include displaying the associated return flight search result (s) online under the selected flight search result.
• a user selection of a search result from Flights and a return flight search result can identify a selected route.
• the plurality of dimensions may include an automatically calculated maximum duration limit and an automatically calculated maximum price limit.
• the maximum duration limit and the maximum price limit can be updated automatically in response to additional user input modifying one or more dimension values.
• the method may further include the step of presenting a user interface element, which, when selected by a user, results in the display of additional search results.
• the method may further include, in response to a user input selecting the user interface element, the step of adjusting at least one of the maximum duration limit and the maximum price limit, the results of supplementary research meeting the maximum duration and adjusted price limits.
• another aspect of the subject described in the present application can be implemented by methods which include the steps of providing a flight search interface including a plurality of search dimensions, each dimension being associated with a search attribute. search flights and a value of each dimension that can be configured by a user, the flight search interface comprising a portion of dimensions and a portion of flight search results, the dimension portion having a diffusiogram of flights displaying flights in relation to a pair of dimensions; receiving a user input specifying one or more dimension values; and provide flight search results that are filtered based on dimension values.
• Other embodiments of this aspect include corresponding computer systems, apparatus, and programs stored on computer storage devices, each configured to perform process operations.
• the flight search results may be updated automatically in response to additional user input modifying one or more dimension values.
• the method may further include the step of providing a link to one or more third party booking sites in response to the user's selection of one or more flight search results.
• the method may further include the step of replacing, in the size portion, the flight diffusogram portion with an interactive map in response to a user input selecting a user interface element associated with the interactive map, the user who can change an original or destination value by an entry on a map in the interactive map.
• the method may further include the steps of receiving a user input modifying a marker position associated with one or more of the dimension pairs in the diffusiogram; and updating the flight search results according to the flights in the region of the diffusiogram demarcated by the user input.
• a first dimension of the pair can be a price and a second dimension of the pair can be a duration.
• the method may further include the steps of receiving a user input selecting a particular flight search result; and in response to the selection, presenting one or more associated return flight search results.
• the step of presenting one or more associated return flight search results may include displaying the associated return flight search result (s) online under the selected flight search result.
• a user selection of a flight search result and a return flight search result can identify a selected route.
• the plurality of dimensions may include an automatically calculated maximum duration limit and an automatically calculated maximum price limit.
• the maximum duration limit and the maximum price limit can be updated automatically in response to additional user input modifying one or more dimension values.
• the method may further include the step of presenting a user interface element, which, when selected by a user, results in the display of additional search results.
• the method may further include, in response to a user input selecting the user interface element, the step of adjusting at least one of the maximum duration limit and the maximum price limit, the results of research additional limits to the maximum duration and adjusted prices.
• Flight searches can be performed by extracting search dimensions from a user-submitted query, allowing for expressive queries.
• the search results can be dynamically updated in response to changes by the user of dimensions providing quick updates of refined search.
• Default filtering can also narrow down the results by eliminating duplicate code shares and hiding options that are unlikely to be selected by users.
• the maximum duration and price limits for search results can be calculated automatically so that a manageable number of search results are initially presented.
• the maximum duration and price limits can be automatically adjusted in response to dimensional changes by the user, so that a modification by the user does not result in the display of unreasonable excessive numbers of results. research. Users can easily change the duration and price limits, for example to see additional search results that are not displayed or to see a smaller number of results.
• Users can interactively use a trip calendar and an associated trip graph to provide travel flexibility to easily view prices for flights of different lengths and different departure and arrival dates. . Users can interactively use a map to easily identify potential destinations from a specified origin location, and to easily determine which of these potential destinations are accessible given the dimension values currently specified. Users can use a scattergram interactively to easily visualize price and flight duration options that meet the currently specified dimension values, as well as price and duration options. flights that do not meet one or more of the dimension values. The flight options can be presented in a dense and easily navigable form, for example a single row of data per flight. In addition, using a hierarchical presentation of round-trip travel itineraries that includes one-way flights and then deploys online to illustrate return flights, reduces the number of results a user must consider when making decisions. of flights.
• Figure 1 is a flowchart an example of a process for finding flights.
• Figure 2 illustrates an example of a flight search interface.
• Figure 3 illustrates an example of a flight search interface that includes a portion of search results.
• Figure 4 illustrates an example of a flight search interface that includes filtered search results.
• Figure 5 illustrates an example of a flight search interface that includes a flight schedule.
• Figure 6 illustrates an example of a flight search interface that includes a scattergram of flights.
• Figure 7 illustrates an example of a flight search interface that includes a scattergram of flights.
• Figure 8 illustrates a portion of an exemplary flight search interface that includes return flights.
• Figure 9 illustrates a portion of an exemplary flight search interface that includes a reservation link.
• Figure 10 illustrates a portion of an exemplary flight search interface that includes a synthesis row.
• Figure 11 illustrates an example of a flight search interface that includes a result adding element.
• Figure 12 illustrates an example of a flight search interface that includes a result adding element.
• Figure 13 illustrates an example of a flight search interface that includes a link to the cheapest flights.
• a flight search interface is provided in response to user input in a search interface.
• a search query of a user can be identified as a request associated with flights or a user can select a flight option in the search interface.
• the user can use the flight search interface to explore route options.
• a route, in particular a flight itinerary is a collection of one or more flight segments that the user can purchase.
• a route identified by the flight search interface can be transmitted to a booking site for purchase.
• a flight segment is a nonstop flight.
• a user can choose multiple segments to go from his origin to his destination.
• the origin is the city or airport from which the user begins his journey.
• the destination is a city in which the user stops, but does not constitute a transition point between segments.
• a route through multiple cities can have multiple destinations.
• a journey between places of origin and destination is a journey.
• a return ticket contains two trips, one in each direction.
• Each path can include multiple segments.
• a trip for a user from San Francisco to Tel Aviv may include a first segment from San Francisco to Los Angeles and a second segment from Los Angeles to Tel Aviv.
• the flight search interface presents flight information based on a plurality of different dimensions. Each dimension can be filtered to provide routes that contain particular dimension values. A user can explore flights using a map presented in the flight search interface, which allows the user to see initial information for a number of different destinations from a specified origin.
• the flight search results are presented in the flight search interface.
• These flight search results can be updated dynamically as the user edits the dimension values.
• a time and price spread diagram shows all the flights corresponding to certain criteria. The user can adjust position markers to restrict the results to a particular range of durations and flight prices. The research results presented are updated in response to adjustments. Once a user has selected a particular route, the user can select a link to a third party provider to complete the transaction.
• Fig. 1 is a flowchart of an exemplary process 100 for finding flights.
• the process 100 will be described in connection with a system including one or more computing devices that implement the process 100.
• the system receives a search query associated with flights.
• the user can enter the search query in a search field or search interface.
• the search query can be processed to determine whether the search query is a query associated with a flight, or not.
• keywords in the query or particular query sentences can be used to identify the search query as a query associated with flights. Examples of keywords may include "flights", as well as city names or airport codes (eg "SFO” for San Francisco International Airport).
• the terms "to”, or "since” connecting cities or airport codes may indicate a request associated with flights, for example "flights from SFO to LHR".
• the search request associated with received flights optionally triggers a response box module (for example a module OneBox) for flight search.
• the system provides the flight search response box with the search results obtained in response to the request.
• Response box modules display information specially formatted when triggered in response to particular types of requests (eg movies, weather, or music). For example, if the user's query refers to weather conditions in a particular location, the answer box may include a weather forecast in the location in question.
• a response box has a category that belongs to a predefined category group and is formatted according to a category-specific template.
• a response box may also be associated with a code that defines how the contents of the response box are obtained. The code can be, for example, scripts or code identifying a main server from which the content is received.
• the flight search response box may include summary flight information responding to the request, for example a typical or minimum price, a number of flights and their duration, airlines serving the route in question, as well as destinations. third parties from whom a flight may be purchased.
• the system provides a flight search interface in response to user input.
• the response box in which a response box is presented, includes a user-selectable link to enter the flight search interface.
• the search results page may include a selectable flights tab (for example, tabs in a search interface for subject-specific searches, such as images, news, books, purchases, blogs). .
• a selection by the user of the flights tab triggers the presentation of the flight search interface.
• the system automatically presents, i.e. without further user input after the request is submitted. search interface, flight search interface without providing intermediate search results.
• the flight search interface presented may be automatically filled with information extracted from the flight search request. For example, if the received request is "flights from SFO to LH R", the request can be interpreted as having an "origin: SFO” and a "destination: LHR". This origin and destination can be prefilled in the flight search interface, ie displayed in the flight search interface without additional user input when the interface is initially presented to the user. . As a variant, the request "flights from SFO" pre-fills only the origin.
• a query includes multiple dimensions that are parsed to fill in certain corresponding dimension values allowing the user to enter more expressive queries, for example "nonstop flights from ZRH to somewhere ⁇ 4h of flight , departing on Friday after 6pm and returning on Sunday after 7pm.
• the flight search interface presented may include flight search results that satisfy the dimension values extracted from the flight search request. For example, for the query "flights from SFO to LHR", in addition to pre-filling origin and destination, the flight search interface can be pre-filled with flight search results that identify flights. whose origin is SFO and the destination LHR.
• the flight search results may also satisfy one or more default values, or other dimensions, and may be automatically updated in response to a user input adjusting one or more of the dimension values.
• the flight search interface includes other dimensions having values that can be modified by the user. These changes can be used to identify filtered results to dimension values.
• Dimensions are properties of a flight itinerary. Dimensions include, for example, the origin and destination of a flight, dates and times of departure and arrival, airlines, flight numbers, flight time, duration of travel, connecting airports, classes of services, number of stops, and luggage fees.
• some dimensions are initially hidden in the flight search interface. These dimensions may be presented, for example, in response to a user input requesting the display of additional dimensions.
• the dimensions are grouped according to particular criteria. For example, primary dimensions may include an origin, a destination, a departure date, a return date, a maximum price, and a maximum duration.
• the primary dimensions may be presented together in a particular location of the flight search interface. For example, the primary dimensions may be prominently positioned in the flight search interface as being most likely changed by users to filter the flight search results.
• Secondary dimensions may include airlines, airline groups (eg OneWorld, SkyTeam, and Star Alliance), stops, connecting airports, departure times, and return times.
• these secondary dimensions may be positioned in a location of the flight search interface different from that of the modified primary dimensions. most frequently.
• the system can use default values for one or more dimensions.
• the default values are chosen so as to restrict the set of results.
• dimensions can be filtered based on default values for maximum price or duration dimensions (for example, users will not likely select a flight option that is longer than a specified amount of time relative to the duration of other flight options).
• the default connections may be limited because users will probably not select a flight path with more than two segments.
• the default values are used to eliminate code-share flights to avoid duplication of search results.
• FIG. 2 illustrates an exemplary flight search interface 200.
• the flight search interface 200 comprises a search request entry field 202 and a portion of dimensions 204.
• the dimension portion 204 comprises primary dimensions 212, secondary dimensions 214, and a card 216.
• the card 216 may be used to specify the original and destination dimensions.
• the origin and destination can be entered directly into an origin field 206 and a destination field 208, respectively.
• the origin has been specified as "San Francisco (SFO)."
• the original field 206 has been pre-filled because the user interface 200 has been provided in response to receiving a search query requesting information about flights from San Francisco, or more specifically, the San Francisco International Airport, whose airport code is SFO.
• the search request received may have been "flights from SFO", or "flights from San Francisco”.
• a user may have entered the origin directly into the original field 206.
• the user may have selected a flight tab, for example flight tab 216, on a search engine interface. , which will have resulted in obtaining the flight search interface 200 without a pre-filled origin or destination information.
• a drop-down box is presented, which contains popular destinations 210.
• the drop-down box is superimposed on the interface.
• the presentation of the drop-down box may be triggered by a user input selecting the destination field 208.
• the presentation of the drop-down box may be triggered when a user fills the entry of origin in the field of origin 206.
• Popular destinations 210 may be specific to the specified origin location.
• popular destinations may be the destinations with the most non-stop flights from the place of origin, the places that most frequently correspond to the destination of itineraries purchased from the place of origin, or the most more frequently included in the same flight request as the place of origin.
• the drop-down box displays additional information to assist the user in selecting a correct location.
• the drop-down box may offer suggestions for potential destination entries that correspond to the user's entry.
• the drop-down box may include the names of airports that are near the location entered by the user, as well as the distance from each airport to that location. The user can then select one or more of the presented airports to specify the destination.
• the drop-down box may display a suggestion “Boston, MA”, or “Boston, MA, Logan International Airport”.
• the drop-down box may display one or more airport names and the distance from the address at the airport, eg "La Guardia International Airport, 22 miles", and "John F. Kennedy International Airport, 30 miles”.
• Other primary dimensions 212 include departure and return dates, price, and duration.
• the user can enter specific dates in respective start and return fields.
• the selection of the field may trigger the presentation of a calendar (for example overlay on the interface), allowing the user to select a specific date.
• the user also specifies a time or time slot for departure and return.
• the price dimension may allow direct entry by the user or a selection of maximum / minimum price ranges, from drop-down menus, for example.
• the price and duration can be edited using a flight scattergram as described below with reference to Figures 3 to 4.
• the map 216 includes particular destination indicators 218, shown in the map 216 as dots.
• the points are displayed as an option with an associated prize, the associated prize showing the price of a trip from the city of the currently selected place to the destination (for example a specified minimum price).
• the currently entered values for the origin and the destination can be indicated in the map 216, for example with particular markers.
• the origin may be indicated with a marker 220 indicating a start.
• destinations 218 are major destinations, for example cities with populations above a certain threshold or cities that are identified as tourist attractions.
• the destinations 218 correspond to popular destinations from the selected place of origin, for example the destinations which correspond to the destination of most flights departing from the selected origin or the cities which appear on the more frequently in the same flight search request as the selected origin.
• Destinations shown on the map can be changed in response to user input.
• the particular destinations illustrated on the map can also be modified, for example to show popular destinations from the specified new place of origin instead of the specified place of origin. old place of origin.
• a user may use the map interactively to increase or decrease the magnification level.
• the particular destinations illustrated on the map can be modified. For example, in response to a user zooming in on the map, that is, the map will no longer show in a smaller region of the United States, smaller or less popular destinations currently not displayed will then be shown on the map. Conversely, in response to user input zooming out of the map, to display multiple continents, smaller destinations within the United States may no longer be displayed, and popular destinations in others. continents can be added.
• the map 216 can be used to explore potential destinations. For example, if only a place of origin is specified, the user can select a destination directly inside the map 216, for which corresponding flight search results 208 can be displayed in a portion of search results. of the interface. For example, selecting a particular point on the map 216 can automatically fill in the destination field, which can then be used to generate corresponding search results. Further, in some circumstances, the user input to the destination input field 208 may cause a change in the magnification degree of the card 216 to allow the user to actually select a destination.
• the map can then either automatically or in response to a user input selecting a flag of card 230, be adjusted to show only cities or airports in the destination.
• An entry at a higher level of granularity that a city could be, for example, a state (eg California or Florida), a country (eg Japan or Spain), or a region (eg San Francisco Bay Area, or the Middle East).
• a state eg California or Florida
• a country eg Japan or Spain
• a region eg San Francisco Bay Area, or the Middle East.
• information about the destination is presented (e.g., as a tooltip or pop-up).
• This information can include a destination name or other destination information.
• a selected destination may also result in the presentation of additional destination information in the map 216.
• This information may include, for example, a description of the destination city, images, weather conditions, time slots. , and the distance from the airport to the city.
• the functionality of the above map has been described in terms of displaying potential destinations for travel from a particular origin, in some embodiments, if the user specifies a destination without specifying origin , the user can use the map 216 interactively to select an origin.
• the map 216 may include potential origins having flights to the specified destination.
• Secondary dimensions 214 include a number of different dimensions and options for specifying values or ranges of dimension values.
• the number of stops can be selected as indifferent, 0, 1, or 2, or more.
• a dimension Airline allows the user to specify an airline, selected groups of airlines, or specific individual airlines.
• the selection of "specific airlines " results in the presentation of an expanded list, for example in secondary dimensions 214 or in a pop-up or superimposed list (for example with checkboxes for each airline).
• Other secondary dimensions 214 may also be customized, such as connection locations, and departure and return times.
• each secondary dimension 214 has the largest possible value by default.
• the selected value can be indicated visually. For example, in the flight search interface 200, the values selected for the secondary dimensions 214 are displayed in bold type.
• FIG. 3 is an example of a flight search interface 300 which includes a portion of search results 314.
• a destination location "Boston" has been specified, for example by the interaction of the user with a card 316 or by direct user input in a destination input field 302.
• the card 316 includes an original marker 306 and a destination marker 308.
• the original markers and destination are connected on the map by a line segment and are visually distinct so as to indicate that one represents the origin and the other represents the destination of a potential trip.
• a user can select a different origin or destination, for example, by selecting one of the destinations indicated by a point on the map 316.
• the portion of search results 314 includes a list of search results 316 that can be classified and satisfies the specified dimensions.
• the search results 316 can be classified according to various ranking criteria 318.
• the portion of search results 306 includes columns that can be classified, including departure times, duration, arrival times, the airline, the connections, and the price of the round trip.
• the search results 316 include the corresponding information, if any. For example, direct flights have no connections.
• Each search result among the search results 316 may be presented as a single row of information.
• the information for each flight represented by one of the search results may provide limited information that allows a user to make a decision about the flight while also allowing easy navigation through the different flight options.
• a particular flight option shown in search results 316 may be limited to departure time, arrival time, airline, connections, and price, while not displaying other information that is less useful when searching for flights, for example the flight number.
• a maximum price limit 310 and a maximum time limit 312 are automatically calculated and displayed.
• Each of the search results 316 meets the requirements of the maximum price and duration limits.
• the maximum price and duration limits can be calculated, for example, so as to ensure that a manageable number of search results potentially attractive to the user will be displayed. If a user modifies a dimension by the flight interface 300, the maximum price and duration limits can be automatically recalculated and the new limit values will be displayed.
• the automatic calculation of price and duration limits may initially lead to the lack of display of some airlines or the cheapest flight possible.
• the interface 300 may include elements that allow a user to view these omitted flights. These elements will be described in more detail below with reference to FIGS. 12 to 16.
• the system receives a user input modifying the dimensions.
• Some dimensions may include fields from which the user can enter values directly.
• the origin and destination fields can allow users to directly type a city, country, or airport code.
• Other dimensions may be represented by drop-down menus or selected options.
• a number of stops can be selected from a set of displayed options (eg 0 stop, 1 stop, or 2+ stops).
• Other dimensions may include multiple input forms.
• the entry of a travel date can be a direct entry or can trigger the display of a calendar in which the user can select a particular date.
• the user input modifying dimensions is provided by an additional graphical representation.
• modification dimensions may be presented using a map representation, an aired map of flights shown, a travel schedule, or a portion of the graph associated with the travel schedule.
• the system provides filtered results.
• some flights are filtered according to the values of each dimension.
• the results provided can be presented as a list in the flight search interface.
• only departing flights are initially displayed. These flights can be categorized according to different criteria that can be selected by the user. For example, flights may be listed initially based on departure time, but may be categorized, for example, by arrival time, airline, connections, and return trip price (if return flight is selected).
• the user can make other changes to one or more dimensions.
• Search results are updated based on changes.
• the results can be filtered and presented dynamically as the user changes the dimension values.
• the flight search results can be identified by a search system that identifies potential flight routes in response to a submitted request. Dimension values can serve as restrictions or additional components of the query.
• the search system may use the information received from the flight search interface to identify appropriate flight search results. Specific flight information may be sought, for example, on the basis of schedule and rate regulation information provided by the airlines, and, in some embodiments, by one or more intermediaries.
• FIG. 4 is an example of a flight search interface 400 which includes filtered search results 412.
• a user has changed the value of a stop number dimension 402 to indicate that the user is only interested in non-stop flights.
• the maximum price limit 408 and the minimum price limit 410 have been changed automatically.
• the appearance of particular places identified by points on a map 404 has been changed to indicate that there is no flight to that destination satisfying the new dimension values, i.e. to the new value of the stop number dimension and the new values of the maximum price and duration limits. For example, since no direct flight could be identified between San Francisco and Omaha, lasting less than 8 hours, the appearance of point 406 representing Omaha was modified to make this point visually distinct from other points representing Places where direct flights from San Francisco, lasting less than 8 hours, are available (eg an empty circle for unavailable destinations, and a filled point for available destinations).
• modified search results 412 are displayed, which satisfy the modified dimension values. In other words, only search results that represent direct flights from San Francisco to Boston are displayed.
• the interface 400 also includes a calendar user interface element 414 and a diffusogram user interface element 416.
• a travel calendar may be displayed for example in place of the map 404, to allow a user to easily adjust the size values of the departure date and the return date.
• a diffusogram can be displayed, for example in place of the card 404, to allow the user to easily adjust the values of the maximum price and duration limits.
• a map user interface element may be displayed instead of the user interface element associated with the broadcast or travel calendar.
• a map may be displayed, for example in place of the broadcast or travel calendar.
• Fig. 5 is an example of a flight search interface 500 that includes a travel calendar 502.
• the travel calendar portion 502 includes a calendar portion 504 and an associated graph portion 506.
• the calendar portion 504 displays a range of travel dates that includes the specified departure and return dates.
• the calendar portion 504 may include a date box for each day in a two-month date range, which includes the selected departure and return dates.
• the trip defined by the departure and return dates that is, the trip starting on the departure date and ending on the return date, is indicated in calendar portion 504 by a highlighted portion. 508.
• the user can interact with the highlighted portion, for example by moving it to different dates in the calendar portion or by increasing or decreasing the length of the highlighted portion to change the departure and return dates.
• Chart 506 displays, for each day in the range, a trip starting on that date and having a duration equal to the duration the trip defined by the departure and return dates. If the user changes the duration of the trip, for example by interacting with the highlighted portion 508 to change the departure or return date, the prices displayed in the portion of graph 506 will be adjusted to indicate prices for trips with a duration equal to the new duration.
• the calendar portion 504 and the graph portion 506 a user is able to easily identify the impact of planning his trip based on different dates in the date ranges.
• the flight search results 510 are changed to show only flight search results that satisfy the specified new dimensions.
• FIG. 6 is an example of a flight search interface 600 which includes a flight dispatcher 602.
• the flight dispatcher 602 provides a visual representation of the airspace according to the price and the duration (for example indicated on respective axes of the flight distribution diagram 602).
• Each point in flight schedule 602 corresponds to a flight that meets the dimensions of the flight search interface 600.
• flights from San Francisco to Cincinnati on September 18th flights from San Francisco to Cincinnati on September 18th.
• Additional visual cues may be provided in Flight Diagram 602, to indicate split flights at a particular intersection between price and duration, for example, increased dot density or color changes.
• the flight broadcast 602 includes control bars 606 and 608.
• the control bar 606 allows a user to change the maximum price.
• the control bar 608 allows the user to modify a maximum duration.
• the control bar 606 is set at a maximum price of $ 744 and the control bar 608 is set to a maximum duration of 7 hours and 12 minutes.
• Flights in the 602 flight program in zone 604 formed by the positions of the two control rods correspond to flights that meet the price and duration limits.
• this area includes visual indications that demarcate the selected area of the full flight diffusogram 602, for example by using a border outline or shading.
• the search results 610 present flights from San Francisco to Cincinnati that satisfy the dimension values including the defined area of the diffusiogram 602. Thus, for example, while a user can visually identify flights in the diffusiogram 602 that exceed their range. Price and duration criteria, these flights do not appear in the search results 610. However, the control bars 606 and 608 can be moved to include additional flights or fewer flights in the search results 610.
• FIG. 7 is an example of a flight search interface 700 including a scattergram of flights 702.
• Flight scattergram 702 also provides here a visual representation of the airspace as a function of price and duration.
• a user has modified a value of one dimension of the number of stops 712.
• some points in an area 704 formed by the control rods 706 and 708 correspond to flights that no longer satisfy the dimensions of the search interface 700.
• the aspect of the points has been modified so that the points in area 704 that correspond to flights that satisfy each dimension are visually distinct from points in zone 704 that do not correspond to flights that satisfy each dimension.
• points that correspond to flights that do not satisfy each dimension are not filled on the diffusogram 702, even if they belong to the area 704.
• control bar 706 to adjust the maximum price is set at a maximum price of $ 745 and the control bar 708 to adjust the maximum duration is set to a maximum duration of 9 hours .
• the positions of the control bars 706 and 708 may have been automatically updated in response to the user input changing the value of the number of stops, i.e. because new maximum values for the price and duration were calculated automatically as described above with reference to FIG.
• the search results 710 present flights from San Francisco to Boston that satisfy the dimension values including the defined area 704 and the newly modified size of the number of stops 712.
• the search results 710 are updated as the The user modifies the positions of the control bars 706 and 708. For example, if the user increases one or more of the maximum duration or the maximum price, more flights will be able to satisfy the criteria, for example if the movement of the control bars includes another point or other points in the broadcast program 702. The search results 710 are therefore updated to include the additional flights. Similarly, if the user decreases one or more of the maximum duration and the maximum price, fewer flights will meet the criteria. The search results 710 are updated to include the smaller number of flights that satisfy the filtered dimensions.
• the updating of the search results 710 can be performed dynamically after each modification of the diffusogram 702 or another dimension.
• the entry relative to a dimension triggers the updated results.
• a specified wait time without any further user input triggers the updated results (eg 3 seconds without receiving other dimension changes).
• a user is able to select a point in the broadcast.
• the appearance of the search result in the search results 710 which corresponds to the same flight as the selected point can be modified, for example the displayed search result can be highlighted, to indicate that the search result corresponds on the same flight as the selected point.
• the system receives a route selection by the user.
• the user first selects a forward path from the presented results.
• the system then provides one or more second paths (e.g., a return trip) based on the selected one-way trip.
• the second path may be presented as a pop-up or overlay on the search interface to distinguish the second path from the search results of the forward path.
• the user can then select a second particular path. In some routes passing through several cities, additional journeys can then be selected in a similar manner.
• the selected routes constitute a route.
• the system directs the user to a selected reservation site.
• a given route may be provided together with one or more links to reservation sites.
• Each reference to a particular booking site may include the corresponding price for the route.
• the user can select a particular booking site.
• the system then directs the user to a corresponding reservation site (for example a web page corresponding to the particular selection).
• the system then transmits the selected route to the booking site.
• the user can then complete the purchase of the itinerary by the booking site.
• Figure 8 is a portion of an exemplary flight search interface 800 which includes return flights.
• the example illustrated shows a portion of the search results 802 of the flight search interface 804.
• Other portions for example those discussed above with reference to FIGS. 2 to 7, may be displayed above or below below the 802 search results portion of the 800 flight search interface.
• the 802 Search Results Portion has 804 search results that show flights from San Francisco to Cincinnati.
• the user has selected a particular flight search result 806.
• the user can select a particular flight from the search results 804 using an input device (eg, a mouse or touch screen input). ).
• the selection of the particular flight search result 806 has given rise to the return flight search results 812.
• an overlay is generated for the return flights over the outbound flights.
• the return flight search results 812 are deployed online such that forward flights remaining below the selected one are moved downward so as not to be obscured by the return flights results. Thus, the user can still see all identified search results 804 for the outbound options.
• the return flight search results 812 include search results that satisfy the associated dimensions. Each result may include the same information as for outward flights, including flight departure times, duration, arrival times, airline, connections, if any, and the cost of the round trip for the pair consisting of the selected outgoing flight 806 and a given return flight. A cheaper round trip price may also be identified in the return flight search results 812.
• FIG. 9 illustrates a portion of an exemplary flight search interface 900 which includes a reservation link 912.
• the illustrated example illustrates a portion of the search results 902 of the flight search interface 900.
• D Other portions, for example those discussed above with reference to Figures 2 to 7, may be displayed above or below the search result portion 902 in the flight search interface 900.
• the 902 search results portion includes 904 search results that show flights from San Francisco to Cincinnati.
• a user can select a one-way flight and then a return flight to create a route 910.
• the user has selected a particular one-way flight search result 906.
• the user also selected a return flight search result 908 from the return flight search results that have been presented in response to the user's selection of the outward search result 906, for example the return flight search results 812 of FIG.
• a unique third-party booking site for example a web-based travel site or the airline's website operating the flights constituting the itinerary, is identified for purchase of the itinerary. selected.
• links to multiple reservation sites may be presented in response to the user's selection of the reservation link 912 together with the corresponding rates for the itinerary for each booking site. , respectively.
• a reservation site link may be an advertisement, for example a reservation provider may purchase the rights to present a link to the reservation provider's website as a booking link for particular itineraries.
• a reservation site link includes a promotional offer. For example, an airline air miles bonus, or a discount when the reservation is associated with a hotel reservation or rental car. The booking provider may purchase the promotion advertising right within the booking link.
• the user's selection of the arrow indicator 914 may trigger a presentation of a user interface element, for example a drop-down box, which allows the user to specify additional dimensions, for example the number passengers, before continuing to book a fare.
• Promotional offers may also be displayed in the UI element instead of, or in addition to, additional dimensions.
• a new search is performed to confirm the price and availability of the selected route.
• a new request can be issued to check if the price and availability of the selected route have not changed with some booking sites that have been identified for the purchase of the selected route. This way, a user can be informed of price changes or availability of their selected route before they start the booking process.
• FIG. 10 illustrates a portion of an exemplary flight search interface 1000 that includes a synthesis row 1010.
• the illustrated example shows a portion of the search results 1002 of the flight search interface 1000.
• D ' other portions for example those discussed above with reference to Figures 2 to 7, may be displayed above or below the search result portion 1002 in the flight search interface 1000.
• Other portions may include portions to specify primary or secondary dimensions and maximum price and duration limits.
• the search result portion 1002 includes search results 1004 that satisfy each specified dimension and the maximum price and duration limits.
• the search result portion 1002 also includes a summary row 1010 which indicates that although flights from additional airlines are available and meet the specified dimensions, they are not currently displayed, for example because each flight of these companies exceeds either the currently specified maximum price limit or the currently specified maximum time limit.
• the summary row 1002 also indicates a minimum price for flights from these airlines (for example flights start at $ 490).
• a summary row can be displayed in a search results portion of a flight search interface when the currently selected maximum price and duration limits have resulted in the exclusion of flight search results that might be of interest. for the user in view of the displayed flight search results.
• the summary row may be displayed when the currently selected maximum price and duration limits have resulted in the exclusion of the cheapest flight that meets the specified dimensions.
• the summary row may be displayed when the currently selected maximum price and duration limits have resulted in the exclusion of all flights of a particular airline, even if flights of that airline that satisfy each dimension have been identified.
• the summary row is only displayed when the currently selected maximum price and duration limits have been calculated automatically, i.e. they have not been adjusted by the user.
• the summary row may be displayed regardless of whether at least one of the limits has been specified by the user.
• the user can select the synthesis portion 1010, for example with a cursor of an input device or with a key input.
• the price and duration limits may be varied, for example, adjusted to numbers large enough for all search results satisfying the dimensions to be displayed.
• FIG. 11 is an example of a flight search interface 1100 which includes a result adding element 1 1 10.
• the flight search interface 1 100 includes a search request entry field 1 102, a portion of dimensions 1,104, and a portion of search results 1,106.
• the portion of dimensions 1,104 includes primary dimensions 1 to 12 and secondary dimensions 1 to 14.
• Primary dimensions include a maximum price limit 1 1 16 and a maximum duration limit 1 1 18. The maximum price and duration limits have been calculated automatically, for example on the basis of the values of the primary dimensions and the other secondary dimensions.
• the portion of search results 1,106 includes search results 1,120 that satisfy each of the primary dimensions 1 1 12 and each of the secondary dimensions 1 1 14.
• the search result portion 1 106 also includes the element of addition of results 1 1 10 and text indicating that additional flight search results displayed in response to a user selection of the 1 1 10 result adding element will exceed at least one of the maximum limit 1 1 16 and the maximum duration limit 1 1 18.
• the maximum price limit and the maximum be automatically adjusted so that ten additional results that satisfy each of the primary dimensions and each of the secondary dimensions including the newly calculated maximum price and duration limits are kets.
• a selection of the results adding element 1 1 10 results in the display of ten results In some embodiments, the selection may result in the display of a different number, for example five, fifteen, or twenty, additional results.
• Fig. 12 is an example of a flight search interface 1200 that includes a result adding element 1210.
• the flight search interface 1200 includes a search query entry field 1202, a 1204-dimensional portion. , and a portion of search results 1206.
• Dimensional portion 1204 includes primary dimensions 1212 and secondary dimensions 1214.
• Primary dimensions include a maximum price limit 1216 and a maximum duration limit 1218.
• the maximum price limit 1216 was calculated automatically. However, the maximum time limit of 1218 has been specified by a user. For example, the user may have changed an automatically calculated value of the duration limit by entering an entry in the maximum duration limit field 1218 or by interacting with the arrow indicators associated with the maximum duration limit field 1218 .
• the search result portion 1206 includes search results 1220 that satisfy each of the primary dimensions 1212 and each of the secondary dimensions 1214.
• the search result portion 1206 also includes the result adding element 1210 and a text indicating that additional flight search results displayed in response to a user's selection of the result adding element 1210 will exceed the maximum price limit 1216. Since the maximum duration limit 1218 has been specified by the user instead of being calculated automatically, the maximum duration limit 1218 will remain unchanged.
• the maximum price limit may be automatically modified, i.e., increased, to a sum that results in the display. ten additional results that satisfy each of the primary dimensions and each of the secondary dimensions including the newly calculated maximum price limit.
• the selection may result in the display of a different specified number, for example five, fifteen, or twenty, additional results.
• Additional search results can be added, for example in order of price so that the ten cheapest search results (or other specified number) that satisfy each of the primary and secondary dimensions and which are not already displayed, are added to the results search engine 1220.
• FIG. 13 illustrates an example of a flight search interface 1300 including a link to a least expensive flight 1310.
• the flight search interface 1300 includes a search request entry field 1302, a portion of dimensions 1304. , and a portion of search results 1306.
• the size portion 1304 includes primary dimensions 1312 and secondary dimensions 1314. Secondary dimensions include a maximum price limit 1316 and a maximum duration limit 1318. The maximum price and of duration have been calculated automatically.
• the search result portion 1306 includes search results 1320 that satisfy each of the primary dimensions 1312 and each of the secondary dimensions 1314.
• the search result portion 1306 also includes the link to a least expensive flight 1310 and a text indicating that the cheapest flight has a duration that exceeds the maximum time limit 1318.
• the link to the cheapest flight 1310 and the associated text are displayed only when the cheapest flight does not meet the maximum time limit 1318. In some embodiments, the link to the cheapest flight 1310 and the associated text are displayed only when the cheapest flight does not meet the maximum duration limit 1318 and the maximum duration limit has been calculated. automatically instead of being specified by a user.
• the time limit is changed so that the cheapest flight meets the time limit and is therefore displayed in the search results 1320.
• the price limit may also be changed, for example, the price limit may be lowered to ensure that a manageable number of search results are displayed after the increase in the time limit.
• a computer storage medium may be, or may be included in, a computer readable storage device, a computer readable storage substrate, an arrangement or a random access or serial access memory device, or a combination of one or many of them.
• a computer storage medium may be a source or destination of computer program instructions encoded in an artificially generated propagated signal.
• the computer storage medium may also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices).
• the operations described in this application may be implemented as operations performed by a data processing apparatus on data stored on one or more computer readable storage devices or received from other sources.
• data processing apparatus includes all types of data processing apparatus, devices, and machines, including, for example, a programmable processor, a computer, a system on a chip, a plurality, or combinations, of these.
• the apparatus may include a specific logic circuit, for example an FPGA (gate network programmable in situ) or an ASIC (application-specific integrated circuit).
• the apparatus may also include, in addition to the hardware, code that creates a runtime environment for the computer program in question, such as code that constitutes processor firmware, a protocol stack, a system a database management system, an operating system, a multiplatform runtime environment, a virtual machine, or a combination of one or more of them.
• the apparatus and the execution environment can realize various different computing model infrastructures, such as web services, distributed computing infrastructures, and grid computing infrastructures.
• a computer program (also called program, software, software application, script, or code) may be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and may be deployed in any form, including an independent program, or in the form of a module, component, subroutine, object, or other unit suitable for use in a computing environment.
• a computer program may, but need not, correspond to a file in a file system.
• a program can be stored in a portion of a file that contains other programs or data (for example one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in files multiple coordinated (eg files that store one or more modules, subroutines, or portions of code).
• a computer program can be deployed to run on a computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communications network.
• Suitable processors for executing a computer program include, by way of example, both general purpose and special purpose microprocessors, and any other processor or processors of any type of digital computer. In general, a processor will receive instructions and data from a ROM or RAM or both.
• the essential elements of a computer are a processor for performing actions according to instructions and one or more memory devices for storing instructions and data.
• a computer will also include, or will be operably coupled to receive data from, or to transfer data to, one or more mass memory devices for storing data, for example magnetic, magneto-optical, or disk disks. optics.
• mass memory devices for storing data, for example magnetic, magneto-optical, or disk disks. optics.
• a computer does not need to have all these devices.
• a computer can be incorporated into another device, for example a mobile phone, a personal digital assistant (PDA), a portable audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (for example a universal serial bus Flashdrive unit (USB)) to name a few.
• Suitable devices for storing instructions and computer program data include all forms of nonvolatile memory, media devices and memory, including for example semiconductor memory devices, e.g.
• EPROMs electrically erasable programmable read-only memory
• EEPROMs electrically erasable read-only memory
• flash memory devices magnetic disks, for example internal hard disks or removable diskettes; magneto-optical disks; and CD-ROMs and DVD-ROMs.
• the processor and the memory may be supplemented by, or incorporated into, special logic circuits.
• a computer having a display device, for example a CRT (cathode ray tube) computer screen. or LCD (liquid crystal display), to display information for the user, and a keyboard and a pointing device, for example a mouse or a trackball, allowing the user to make entries into the computer.
• a display device for example a CRT (cathode ray tube) computer screen. or LCD (liquid crystal display), to display information for the user, and a keyboard and a pointing device, for example a mouse or a trackball, allowing the user to make entries into the computer.
• a display device for example a CRT (cathode ray tube) computer screen. or LCD (liquid crystal display)
• keyboard and a pointing device for example a mouse or a trackball
• Other types of devices can be used to also provide interaction with a user; for example a response provided to the user may have some form of sensory response, for example a visual response, an auditory response, or a tactile response; and user input may be received
• Embodiments of the subject described in the present application may be implemented in a computer system which includes a back-end component, for example in the form of a data server, or which includes a middleware component, for example an application server, or which includes a front-end component, for example a client computer that has a graphical user interface or web browser that allows a user to interact with an implementation of the subject described in this application, or any combination of one or several of said back-end, middleware, or front-end components.
• the system components may be interconnected by any form or any digital data communication medium, for example a communications network. Examples of communication networks include a local area network ("LAN”) and a wide area network (“WAN”), an inter-network (eg the Internet), and peer-to-peer networks (eg peer-to-peer networks). ad hoc).
• the computer system can include clients and servers.
• a client and a server are generally remote from each other and typically interact by a communication network.
• the relationship between the client and the server occurs through computer programs running on the respective computers and having a client-server relationship with each other.
• a server transmits data (e.g. an HTML page) to a client device (e.g., to display data and to receive user input from a user communicating with the user device).
• the data generated at the client device level may be received from the client device by the server.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Databases & Information Systems (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• Data Mining & Analysis (AREA)
• Business, Economics & Management (AREA)
• Computational Linguistics (AREA)
• Tourism & Hospitality (AREA)
• Entrepreneurship & Innovation (AREA)
• Strategic Management (AREA)
• General Business, Economics & Management (AREA)
• Quality & Reliability (AREA)
• Operations Research (AREA)
• Marketing (AREA)
• Human Resources & Organizations (AREA)
• Economics (AREA)
• Development Economics (AREA)
• User Interface Of Digital Computer (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=45755370

Family Applications (1)

Country Status (3)

Families Citing this family (38)

Citations (1)

Family Cites Families (40)

• 2012
  • 2012-01-12 US US13/979,638 patent/US9684690B2/en active Active
  • 2012-01-12 WO PCT/FR2012/050084 patent/WO2012095613A1/fr active Application Filing
  • 2012-01-12 EP EP12705329.6A patent/EP2663951A1/de not_active Ceased
• 2017
  • 2017-05-25 US US15/604,899 patent/US20170293665A1/en not_active Abandoned

Patent Citations (1)

Also Published As

Similar Documents

Legal Events