Open main menu

Search request router

Router is a plugin of the Air tickets component of the Websky system.

Contents

Purpose

The search request router is used to automate the selection of requisite packages for a search based on search request parameters. The agency can set up an advantageous search scheme for you:

  • search in different GDS in several zones,
  • issue more diverse fares at minimal expenses for search transactions.

You can bind requisite packages to a certain geography, for example, so that the searches of GDS Sirena Travel would only be carried out for domestic Russian flights.

Principle of Operation

Search request router is a combination of rules that distributes search requests to different requisite packages.

Search request routing - a function of selecting suitable requisite packages for search.

Search request router - a set of routing rules.

Routing rule - requisite package and a set of conditions under which a search request will be executed in the specified requisite package.

  • Routing rule condition - a set of parameters and specified values.
  • Condition parameter - a sign by which the search request will be checked during routing.
  • Condition value - one or several specific parameter objects for comparison with the search request: specific continents, countries, airports, etc. If several values are specified, they are considered as alternative in the condition.

In general, one request corresponds to several suitable requisites.

The router compares the specified parameters of a search request with the rules of search request routing and defines suitable rules:

  • If suitable rules are found, the system sends parallel requests to all suitable packages and performs a search by the requisites specified in them.
  • If no suitable rules are found, the system will generate a message that the results are not found.

For the router to select a rule, the all parameters of the search query must match the all conditions of the rule.

Routing in Websky and Nemo Connect

Routing is configured via one of two plugins:

It is recommended to use the router in Websky Nemo Connect because it supports a more flexible mechanism for setting up rules for selecting packages and has more parameters for setting conditions in routing rules. For example, it allows you to create separate rules for different users, search and meta search APIs, and rules are created directly for packages of Websky Nemo Connect requisites without using Websky 1 requisite packages.

Attention! When using Websky Nemo Connect router, geographical restrictions of Websky 1 packages do not work.

Examples of search request routing rules

Rules Search parameters Result
Search for flights from France to Russia in Galileo
Search for flights from France to Austria in Sabre
Flight from Paris to Moscow Search will be performed in Galileo's flight requisites package

For the "Round-trip" flights, the requisites packages are selected as follows:

Rules Search parameters Result
Search for flights from France to Russia in Galileo Moscow-Paris-Moscow Search will be performed in Galileo's flight requisites package
Search for flights from Russia to France in Galileo Paris-Moscow The search will not be performed, as there are no suitable requisite packages.

For the Complex routes, the requisites package is selected if the parameters of each flight segment in the search request correspond to the routing rule for the given package:

Rules Search parameters Result
Search for flights from France or Moscow to Italy or Ukraine in Galileo Moscow - Paris - Milan Search will be performed in Galileo's flight requisites package
Search for flights from France or Moscow to Italy or Ukraine in Galileo Moscow - Paris - St. Petersburg The search will not be performed, as there are no suitable requisite packages.

Attention! If a package with non-working requisites is selected for search, the user will receive a message: "No matching requisites found. Check the settings".

See also