Patent Description:
Checking tire pressure is an important part of the maintenance of a vehicle. Tire pressures should be maintained at predetermined pressures to ensure that a tire performs as intended by the manufacturer. <CIT> discloses a computer-implemented method of aircraft tire maintenance including the steps of receiving data of a plurality of pressure and temperature measurements, each of the plurality of pressure and temperature measurements having an associated time stamp; determining stable points in the plurality of pressure and temperature measurements; and using the stable points for determining tire maintenance. <CIT> discloses a turnkey maintenance of a customer's aircraft fleet managed by a single management service provider (MSP) controlling integrated maintenance and materials services from a central operations site. <CIT> discloses a method of determining a status of a tyre monitoring device is disclosed. The tyre monitoring device includes a counter initiated on a first use of the tyre monitoring device on a wheel and the method includes: determining a current value of the counter; determining a status of the tyre monitoring device based on the current value of the counter; and providing an indication based on the determined status. <CIT> discloses a handheld interrogation device including a controller configured to generate a power signal. The controller is also configured to determine tire pressure data based on a signal received from a tire pressure sensor. <CIT> discloses a system for sensing tire parameters in the remote monitoring and management of a fleet of autonomous vehicles.

A first aspect of the present invention provides an aircraft tire monitoring system comprising: a processor; and a data carrier comprising machine readable instructions that, when executed, cause the processor to perform operations based on a plurality of sets of values indicative of tire parameters of aircraft tires, each set of values corresponding to an aircraft comprising a plurality of the aircraft tires, the operations comprising: determining a remedial action associated with each set of values; determining a priority associated with the determined remedial actions; generating, based on the determined remedial actions, a list of aircraft, the list of aircraft ranked based on the determined priority of remedial action; and causing a display device to display the list of aircraft, such that aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action.

By displaying the list of aircraft such that aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action, those aircraft for which higher priority remedial actions are required may be more easily identified, which may facilitate ongoing maintenance procedures for the identified aircraft.

Optionally, the instructions, when executed, cause the processor to perform actions comprising causing the display device to display, for each aircraft in the list, the corresponding set of values.

Optionally, the tire parameters comprise tire pressures of associated aircraft tires, and the instructions, when executed, cause the processor to perform operations comprising causing the display device to display, for each aircraft in the list, an associated reference pressure for the corresponding aircraft tires.

Optionally, the instructions, when executed, cause the processor to perform actions comprising causing the display device to display, based on the determined priority of the remedial action, a visual indicium for each remedial action, the visual indicium configured to take one of at least a first state and a second state based on the determined priority.

Optionally the visual indicium comprises a binary visual indicium configured to take one of the first state and the second state based on the determined priority.

Optionally, the instructions, when executed, cause the processor to perform actions comprising causing the display device to display, for each aircraft in the list and associated aircraft tires, a status message based on the determined remedial actions.

Optionally, the instructions, when executed, cause the processor to perform actions comprising determining, based on the plurality of sets of values, a further remedial action for each of the aircraft tires and/or tire monitoring devices associated with each of the aircraft tires.

Optionally, the instructions, when executed, cause the processor to perform actions comprising determining, based on a status of the tire monitoring devices, corresponding further remedial actions.

Optionally the instructions, when executed, cause the processor to perform actions comprising: determining a further priority associated with each of the determined further remedial actions; and causing the display device to display, based on the determined further priorities, a further visual indicium for each aircraft tire, the further visual indicium configured to take one of at least a first state and a second state depending on the determined further priority.

Optionally the further visual indicium comprises a further binary visual indicium configured to take one of the first state and the second state.

Optionally, the determined further remedial actions comprise one or more of checking the tire monitoring device, and replacing the tire monitoring device.

Optionally, the instructions, when executed, cause the processor to perform operations comprising: generating, based on the determined further remedial actions, the list of aircraft; and causing the display device to display the list of aircraft, such that at least one of: aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action, and aircraft with a higher number of determined further remedial actions are shown higher up the list on the display than aircraft with a lower number of determined further remedial actions.

Optionally, the instructions, when executed, cause the processor to perform operations comprising: generating, based on a type of the determined further remedial actions, the list of aircraft, each type of determined further remedial action having an associated priority; and causing the display device to display the list of aircraft, such that at least one of: aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action, aircraft with a higher number of determined further remedial actions are shown higher up the list on the display than aircraft with a lower number of determined further remedial actions, and aircraft with a greater number of relatively higher priority determined further remedial actions are shown higher up the list on the display than aircraft with a lower number of relatively lower priority determined further remedial actions.

Optionally, the instructions, when executed, cause the processor to perform actions comprising: causing the display device to display the list such that each entry of the list is expandable to display further detail associated with the corresponding set of values, the further detail comprising one or more of a visual gauge indicator associated with the corresponding tire parameter, a location associated with the corresponding tire parameter, a tire parameter profile based on historical tire parameter readings for a given tire, and a message log comprising messages associated with status messages for the associated aircraft tires.

Optionally, the instructions, when executed, cause the processor to perform actions comprising: causing the display device to display the list of aircraft on a first display pane; causing the display device to display, for each entry in the list of aircraft, a link to a respective second display pane; and causing the display device to display, on each respective second display pane, further detail associated with the corresponding set of values, the further detail comprising one or more of a visual gauge indicator associated with the corresponding tire parameter, a location associated with the corresponding tire parameter, a tire parameter profile based on historical tire parameter readings for a given tire, and a message log comprising messages associated with status messages for the associated aircraft tires.

Optionally, the instructions, when executed, cause the processor to perform actions comprising causing the display device to display, based on status messages for associated aircraft tires, an expandable message log comprising messages associated with status messages for the associated aircraft tires.

Optionally, the messages comprise determined further remedial actions.

Optionally, the remedial action comprises reinflation of one or more tires associated with the aircraft, and the priority of the reinflation is determined based on a time to reinflation.

Optionally, the system comprises a memory configured to store the plurality of sets of values, and the instructions, when executed, cause the processor to perform operations comprising obtaining the plurality of sets of values from the memory to determine the remedial actions.

A second aspect of the present invention provides a computer-implemented method comprising: obtaining a plurality of sets of values indicative of tire parameters of aircraft tires, each set of values corresponding to an aircraft comprising a plurality of the aircraft tires; determining a remedial action associated with each set of values; determining a priority associated with the determined remedial actions; generating, based on the determined remedial actions, a list of aircraft, the list of aircraft ranked based on the determined priority of remedial action; and displaying the list of aircraft, on a display device, such that aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action.

Optionally, the method comprises displaying, on the display device and for each aircraft in the list, the corresponding set of values.

Optionally, the tire parameters comprise tire pressures of associated aircraft tires, and the method comprises displaying, on the display device and for each aircraft in the list, an associated reference pressure for the corresponding aircraft tires.

Optionally, the method comprises: displaying, on the display device and for each aircraft in the list and associated aircraft tires, a status message based on the determined further remedial actions.

Optionally, the method comprises: determining, based on a status of tire monitoring devices associated with the plurality of aircraft tires, corresponding further remedial actions; determining a further priority associated with each of the determined further remedial actions; generating, based on the determined further remedial actions, the list of aircraft; and displaying, on the display device, the list of aircraft, such that at least one of aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action, and aircraft with a higher number of determined further remedial actions are shown higher up the list on the display than aircraft with a lower number of determined further remedial actions.

Optional features of aspects of the present invention may be equally applied to other aspects of the invention, where appropriate.

An aircraft tire monitoring device <NUM> in accordance with the present invention is illustrated schematically in <FIG>, in the form of a tire pressure monitoring device. The tire monitoring device <NUM> is configured for mounting on a wheel, for example by a mechanical connection to an opening on the wheel providing access to the tire. The tire monitoring device <NUM> includes a processor <NUM>, a wireless communication interface <NUM>, an indicator <NUM>, a power supply <NUM>, a pressure sensor <NUM>, a temperature sensor <NUM>, a first storage <NUM> and a second storage <NUM>.

Processor <NUM> may be any suitable processing device including a microprocessor with one or more processing cores. In use, processor <NUM> coordinates and controls the other components and may be operative to read and/or write computer program instructions and data from/to the storage <NUM>, <NUM>. The processor <NUM> may be optimized for low power operation or have at least one processing core optimized for low power operation in some examples.

Wireless communication interface <NUM> is connected to the processor <NUM> and is used to both transmit and received data from the other devices of the tire pressure sensor system. In this example, the wireless communication interface <NUM> includes two transceivers, <NUM>, <NUM> which both use different wireless technology. A first transceiver <NUM> is provided for relatively long-range communication, up to about <NUM> or about <NUM>. For example, the first transceiver <NUM> may use a communication standard suitable for mobile devices, such as IEEE <NUM>. <NUM>, IEEE <NUM>. <NUM>, IEEE <NUM> (Wi-Fi) on either the <NUM> or <NUM> Industrial Scientific and Medical (ISM) bands or a Wireless Avionics Intra-Communications (WAIC) standard. The first transceiver <NUM> also includes an encryption module for encrypting sent data and decrypting received data, for example according to the Advanced Encryption Standard (AES) utilizing pre-shared keys. A second transceiver <NUM> is provided for relatively short-range communications. For example, the second transceiver <NUM> may use a standard according to IEEE <NUM>, such as IEEE <NUM>. <NUM>, RFID or Near Field Communication (NFC). The second transceiver <NUM> may operate over a range of less than <NUM>, less than <NUM>, less than <NUM>, less than <NUM>, less than <NUM>, less than <NUM>, less than <NUM>, less than <NUM> or requiring contact between devices. Like the first transceiver <NUM>, the second transceiver <NUM> also includes an encryption module for encrypting sent data and decrypting received data.

In some examples, a single wireless transceiver may be provided in the wireless communication interface <NUM>. In that case the single transceiver may use relatively short range or relatively long range communication, or adjust the range (such as by controlling transmit power) as required.

Indicator <NUM> is connected to the processor <NUM> and controlled by the processor <NUM> to provide indications to a user of the tire monitoring device <NUM>. In this example the indicator <NUM> is an LED, but in other examples the indicator is another form of light, a display, such as an LCD or e-ink display, or any other form of visual indication. In other examples, the indicator <NUM> is an audible indicator, such as a buzzer, beeper, speaker or any other sound generating component. In further examples, the indicator <NUM> can comprise both audible and visual indication components. The indicator <NUM> provides at least first and second indications, for example a first colour and a second colour of emitted light. Further indications can also be provided, such as solid or flashing light. The tire monitoring device <NUM> has a housing (not shown) and the indicator <NUM> can provide an indication outside the housing, for example the LED may be mounted external to the housing or visible through the housing, or sound may be able to be emitted from within the housing.

The power supply <NUM> provides power to the elements of the tire monitoring device <NUM>. The power supply <NUM> may be a battery, such as Lithium battery. In this example, the power supply <NUM> is a Lithium battery with power sufficient to run the sensor in normal operation for about <NUM> to <NUM> years. In other examples the power supply <NUM> may comprise a power harvesting system, for example harvesting vibration and/or electromagnetic radiation to charge a capacitor or battery which is then used to power the device.

The pressure sensor <NUM> is connected to processor <NUM> and may be any suitable sensor for measuring pressure, for example a capacitive sensor. Similarly, the temperature sensor <NUM> is connected to processor <NUM> and may be any suitable sensor for measuring temperature, such as thermocouple. The temperature sensor <NUM> may be arranged to measure the temperature of the wheel or the temperature of the gas inside the tire directly. Where the temperature sensor <NUM> measures the temperature of the wheel, this can be processed to determine the temperature of the gas in the tire. For example, an algorithm or look-up table may be used.

The connection of the pressure sensor <NUM> and temperature sensor <NUM> to the processor <NUM> may be digital, providing a digital representation of the measured pressure and/or temperature from an Analogue to Digital Convertor (ADC) in the sensor itself, or analogue, in which case the processor may include an ADC to sample the received signal. Including both a pressure sensor <NUM> and a temperature sensor <NUM> may be useful to determine a temperature compensated pressure value. Although this example includes a pressure sensor <NUM> and a temperature sensor <NUM>, other examples may include only a pressure sensor, or may include further sensors.

This example includes two storage elements <NUM> and <NUM>, which can individually or collectively be referred to as local memory of the aircraft tire monitoring device <NUM>. Storage <NUM> is non-volatile rewritable storage in this example, such as flash memory which can retain data without requiring applied power. Other examples may include volatile storage, which is kept powered by the power supply, or combinations of read-only and rewritable storage. Storage <NUM> is connected to the processor <NUM> and used to store both computer program instructions for execution by the processor and data, such as data from the pressure sensor <NUM> or received over the wireless communication interface <NUM>. In some examples, storage <NUM> may store a history of pressure and/or temperature readings sensed by the pressure sensor <NUM> and the temperature sensor <NUM>. For example, the previous ten days readings may be stored, with the newest data replacing the oldest once the storage is full.

Storage <NUM> is secure storage to which write and/or read access is restricted, for example only accessible to certain processes running on processor <NUM>. Configuration data, such as wireless encryption keys can be stored in storage <NUM>. In other examples, a single storage may be provided, or storage <NUM> and <NUM> may be provided in a single physical device with a logical partitioning between storage <NUM> and storage <NUM>.

<FIG> shows a schematic representation of a remote device <NUM> for use in conjunction with the tire monitoring device <NUM> of <FIG>. The remote device <NUM> includes a processor <NUM>, a display <NUM>, an input system <NUM>, a power supply <NUM>, a wireless communication interface <NUM>, a storage <NUM> and wired communication interface <NUM>. In this example the remote device <NUM> is a mobile device, such as a cellular phone or a tablet computer.

The processor <NUM> is any suitable processing device, for example a multipurpose microprocessor, system-on-chip, or system in package, which may include one or more processing cores. Processor <NUM> is connected to the display <NUM>, such an LCD, OLED or e-ink display to display information to a user of the remote device <NUM>.

Input system <NUM> includes a touch screen interface in this example, allowing a user to interact with the remote device <NUM> by touching user interface elements on the screen. The input system <NUM> may include one or more buttons in addition to the touch screen, as well as other input devices, such as a microphone for speech recognition and a camera for image input. Other examples may not include a touch screen interface.

The remote device is powered by power supply <NUM>, which is a rechargeable lithium-ion battery in this example. Other examples may use alternative power supplies, such as other battery technologies, mains power, or energy harvesting, such as solar power.

A wireless interface <NUM> is included for the remote device <NUM> to communicate with other devices, such as the tire monitoring device <NUM>. In this example, a single wireless interface <NUM> is provided which is configured to communicate with the tire monitoring device <NUM>. For example, a relatively long range wireless communication technology can be used, such as one conforming to IEEE <NUM>. <NUM>, IEEE <NUM>. <NUM> or IEEE <NUM>. This allows the remote device <NUM> to interact with the tire monitoring device <NUM> from a relatively long range.

In other examples, the remote device <NUM> may be provided with multiple wireless communication interfaces or transceivers, operating with different wireless technologies, such as at least two of IEEE <NUM>. <NUM>, IEEE <NUM>. <NUM>, IEEE <NUM> (Wi-Fi), WAIC, RFID and NFC. For example, the remote device <NUM> may have two transceivers with one having a longer communication range than the other.

Storage <NUM> includes a non-volatile element, such as flash memory, and a volatile element, such as RAM. The non-volatile element is used to store operating system software and application software. In this example, the remote device <NUM> runs standard operating system software and is loaded with application software to interact with the tire monitoring device <NUM>. In order to restrict access to the tire monitoring device <NUM>, the application software may be provided from a secure source and not available to the general public, and/or require credentials to be entered before operating.

Wired communication interface <NUM> is provided for connection to a computing system. The wired communication interface <NUM> can be for example, a serial data connection, such as Universal Serial Bus (USB), a parallel data connection or a network connection, such as Ethernet. The wired communication interface <NUM> may allow the remote device <NUM> to communicate values and/or other status information read from the tire monitoring device <NUM> to a computing system, for example to store long term trends and assist fleet management. Alternatively, or additionally, wired communication interface <NUM> may be used for communication with the computing system. In some examples, the remote device <NUM> may not include a wireless communication interface.

<FIG> shows a schematic representation of a tire pressure sensor network <NUM> comprising a plurality of tire monitoring devices <NUM> installed in an aircraft <NUM>. The aircraft <NUM> comprises main landing gear <NUM> and nose landing gear <NUM>. The aircraft <NUM> may be used in conjunction with any of the methods described herein. Tire monitoring devices <NUM> are installed on each wheel of the main landing gear <NUM> and nose landing gear <NUM>.

In an example, the tire monitoring devices <NUM> are also in communication with a cockpit system to provide tire pressure information to the pilots on the flight deck. In these examples, the flight deck console may also function as a remote device.

<FIG> shows a flow chart of a tire pressure check process that can be used with the tire pressure sensor network <NUM> of <FIG>. First, at block <NUM>, a user launches the tire monitoring control application on the remote device <NUM>. During initialization of the application, a check is made that the wireless communication interface <NUM> for communication with the tire monitoring devices <NUM> is active on the remote device <NUM> and the user is prompted to activate if it is not active.

Next, at block <NUM>, the remote device <NUM> scans for tire monitoring devices <NUM> in range. For example, the remote device <NUM> may send out a probe over the wireless communication interface <NUM>. At the same time, the tire monitoring devices <NUM> are periodically waking and listening for the probe of the remote device, and/or periodically waking and broadcasting respective identification signals, which include aircraft identifiers, such as a tail identifier of an aircraft to which the tire monitoring device <NUM> is attached.

The scanning may comprise establishing direct, point-to-point contact with each tire monitoring device <NUM>, or contact through the network <NUM> of tire monitoring devices <NUM>, for example through an access point, a master device, or any device in a mesh network.

Depending on the communication range and location, tire monitoring devices associated with more than one aircraft may be detected. For example, several aircraft may be in the same hanger in range of the remote device <NUM>. At block <NUM>, input is received of a selected identifier.

Next, at block <NUM>, a request or command is sent to the tire monitoring devices <NUM> corresponding to the selected identifier to cause them to connect to the remote device <NUM>, for example so that they can receive a request from the remote device <NUM> to carry out a tire pressure check.

Throughout the process of <FIG>, communication between the remote device <NUM> and the tire monitoring devices <NUM> may be secure, for example encrypted by a network key. The network key for the communication with the remote device may be different from the network key used for communication between the sensor devices to enhance the security of the system.

Security may be increased by using a wireless communication technology with a limited transmission distance when exchanging secure keys, for example <NUM> (Wi-Fi) standards may allow transmission over a distance of <NUM> or further in clear space. This alone may be sufficient to provide increased security because physical proximity is required to intercept communications. In some examples, security may be increased by reducing transmission power when encryption keys are transmitted compared to transmission of the encrypted data itself, requiring closer proximity for the initial key exchange process.

A tire performance monitoring system <NUM> that utilises a number of tire pressure sensor networks <NUM> is illustrated schematically in <FIG>, and comprises a plurality of tire pressure sensor networks <NUM> formed of respective pluralities of tire monitoring devices <NUM>, the remote device <NUM>, a remote memory <NUM>, and a remote computing device <NUM>.

The remote memory <NUM> is disposed remotely from the tire pressure sensor networks <NUM>, and hence the plurality of aircraft tire monitoring devices <NUM>, and the remote device <NUM>, and comprises any memory device capable of storing data associated with the tire pressure sensor networks <NUM>. In some examples the remote memory <NUM> can comprise a database or the like, for example hosted on a server remote from the tire pressure sensor networks <NUM>, and hence the plurality of aircraft tire monitoring devices <NUM>, and the remote device <NUM>. Although illustrated separately in <FIG>, it will be appreciated that in some examples the remote memory <NUM> can comprise part of the remote computing device <NUM>. Similarly, whilst one memory is illustrated, it will be appreciated that in practice the memory may comprise multiple memory devices, for example distributed across physical and/or virtual locations.

The remote computing device <NUM> is disposed remotely from the tire pressure sensor networks <NUM>, and hence the plurality of aircraft tire monitoring devices <NUM>, and the remote device <NUM>. The remote computing device <NUM> comprises a processor <NUM>, a display device <NUM> and a memory <NUM>. Whilst illustrated as a single processor <NUM>, the remote computing device <NUM> may comprise more than one processor in practice, and similarly the system can additionally or alternatively comprise a plurality of remote computing devices <NUM> such as a server farm. The display device <NUM> can comprise a screen capable of displaying a graphical user interface to a user of the remote computing device <NUM>, as will be discussed in more detail hereafter. The memory <NUM> can comprise any suitable memory device, and stores instructions that, when executed, control the processor <NUM> to perform various actions.

The tire performance monitoring system <NUM> can be utilised to process and/or analyse data obtained from the tire pressure sensor networks <NUM> to provide further detail about aircraft tire performance characteristics of the tires of each of the aircraft <NUM>.

In particular, for a given aircraft <NUM> each of the respective aircraft tire monitoring devices <NUM> is configured to wake-up every <NUM> minutes to measure pressure and temperature values using the respective pressure sensor <NUM> and temperature sensor <NUM>. Such measured pressure and temperature values are stored in the respective first storage <NUM> of the aircraft tire monitoring device <NUM>, i.e. in local memory of the aircraft tire monitoring device <NUM>. When a tire pressure check is performed, for example once the aircraft tire monitoring devices <NUM> are connected to the remote device <NUM> following an appropriate request or command <NUM> in accordance with the method <NUM> described above, the remote device <NUM> obtains the measured pressure and temperature values from the first storage <NUM> of the respective aircraft tire monitoring devices <NUM>.

The remote device <NUM> sends the measured pressure and temperature values, or appropriate values derived from the measured pressure and temperature values, to be stored in the remote memory <NUM>. Such stored values are retrieved by the remote computing device <NUM>, and are processed by the processor <NUM> of the remote computing device <NUM>. This process occurs for each of the aircraft <NUM>, for example for a fleet of aircraft operated by an operator, with the remote computing device <NUM>, and in particular the display device <NUM>, utilised to communicate information about the fleet of aircraft to the operator.

It will be appreciated that, whilst processing and provision of large amounts of data to an operator may be desirable, such large amounts of data may be unwieldy and provide little value to an operator in practice.

A method <NUM> in accordance with the present invention is illustrated schematically in the flow diagram of <FIG>. The method <NUM> comprises obtaining <NUM> a plurality of sets of values indicative of tire parameters of aircraft tires, each set of values corresponding to an aircraft comprising a plurality of the aircraft tires. The method <NUM> comprises determining <NUM> a remedial action associated with each set of values, and determining <NUM> a priority associated with the determined remedial actions. The method <NUM> comprises <NUM> generating, based on the determined remedial actions, a list of aircraft, the list of aircraft ranked based on the determined priority of remedial action. The method <NUM> includes <NUM> displaying the list of aircraft, on a display device, such that aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action.

By displaying the list of aircraft such that aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action, a user or operator of the aircraft tire monitoring system may be more easily able to identify those aircraft for which higher priority remedial actions are required, which may facilitate ongoing maintenance procedures for the identified aircraft. This may be an improvement over, for example, user interface systems where aircraft are displayed with remedial actions in a non-ordered fashion or ordered without considering any remedial actions.

In the context of the tire performance monitoring system <NUM>, the processor <NUM> of the remote computing device <NUM> obtains the sets of pressure and temperature values for each aircraft <NUM> from the remote memory <NUM>, for example where a user desires to interrogate such values, and processes the sets of values to determine a time to reinflation of tires for the given aircraft <NUM>. Such time to reinflation is an example of a remedial action. The processor <NUM> assigns a priority level to each aircraft <NUM> based on the determined time to reinflation. For example, those aircraft <NUM> comprising a relatively shorter time to reinflation are assigned a higher priority than those aircraft <NUM> comprising a relatively longer time to reinflation. The processor <NUM> then automatically generates a list of aircraft <NUM> based on the determined times to reinflation and associated priorities, with those aircraft <NUM> having a relatively higher priority located further up the list than those aircraft <NUM> having a relatively lower priority. The processor <NUM> then automatically causes the list to be displayed on the display device <NUM>, for example with the processor <NUM> causing running of an application that presents a graphical user interface on the display device <NUM>.

A first display pane <NUM> of such a graphical user interface is illustrated schematically in <FIG>. The first display pane <NUM> comprises a list <NUM> of aircraft <NUM>, having first <NUM> and second <NUM> entries. Here the first entry <NUM> is illustrated with exemplary text content, whilst the second entry <NUM> is illustrated using corresponding reference numerals for clarity. It will be appreciated that in practice the list can comprise many more entries, which may not all be displayed at once. For example, with the first display pane <NUM> scrollable in a downward direction of <FIG> to display further entries in the list <NUM>, and/or navigable to transition between two or more pages of results. The list <NUM> may generated automatically in response to a request, such as by following the method of <FIG>. The list <NUM> may also be maintained ready for display in response to a request. In both cases, the processor <NUM> can also update the list <NUM>, for example by moving the position of an aircraft <NUM> within the list <NUM> where an updated priority of remedial action, and/or a new aircraft <NUM>, is determined. New and/or updated data may be determined by polling the remote memory, for example.

As well as the list <NUM>, the first display pane <NUM> comprises a search bar <NUM>, an aircraft tail ID filter <NUM>, a status filter <NUM>, and an expansion toggle <NUM>.

The search bar <NUM> can, for example, enable searching by aircraft tail ID number, or indeed searching based on any number of other categories. The aircraft tail ID filter <NUM> comprises a list of aircraft tail ID numbers, each with an associated check box that can be ticked/filled or unticked/unfilled to cause display of, or removal of, the associated aircraft from the list <NUM>. As depicted in <FIG>, all check boxes in the aircraft tail ID filter <NUM> are filled so all aircraft are displayed. Similarly, the status filter <NUM> comprises a list of statuses corresponding to statuses of tire monitoring devices <NUM> of aircraft <NUM> in the list <NUM>, each with an associated check box that can be ticked/filled or unticked/unfilled to cause display of, or removal of, the associated aircraft from the list <NUM>. As depicted in <FIG>, all check boxes in the status filter <NUM> are filled so aircraft of all status are displayed. The expansion toggle <NUM> can cause all entries <NUM>, <NUM> in the list <NUM> to be expanded in a manner that will be discussed in more detail below.

Each of the first <NUM> and second <NUM> entries on the list <NUM> comprises the same displayed information, with each entry <NUM>,<NUM> comprising a time to reinflate display region <NUM>, a value and status display region <NUM>, a reference pressure display region <NUM>, a message icon <NUM>, a show/hide detail icon <NUM>, a detailed view icon <NUM>, and an update status display region <NUM>.

The time to reinflate display region <NUM> displays a "Time to Reinflate X Days" message, with X an integer value that is illustrated as <NUM> days for the first entry <NUM> in the list <NUM>. In <FIG>, the text in the time to reinflate display region of the second entry <NUM> on the list <NUM> is not shown but is <NUM> days in this example. As indicated above, the list <NUM> is ordered based on the time to reinflate status for each aircraft <NUM>, e.g. with the processor <NUM> arranging the aircraft <NUM> in the list <NUM> based on their determined priority of time to reinflation. The time to reinflate display region <NUM> has an associated visual indicium <NUM> in the form of a coloured box that surrounds the "Time to Reinflate X Days" message. Here the visual indicium <NUM> is a binary visual indicium, in that it can be either in a red state or a green state depending on the determined priority of the time to reinflate, although visual indicia with a greater number of states, for example three states (red, amber, green), and/or different colours are also envisaged. Red is illustrated in the figures with dotted shading, whilst green is indicated in the figures with line shading. Here a high priority remedial action is the "Time to Reinflate <NUM> Days" message of the first entry <NUM> of the list <NUM>, which has an associated visual indicium <NUM> in the form of a red border surrounding the message. A lower priority remedial action can be a "Time to Reinflate <NUM> Days" message for the second entry <NUM> of the list <NUM>, which has an associated visual indicium <NUM> in the form of a green border surrounding the message.

The value and status display region <NUM> displays values and statuses associated with each tire, i.e. with each aircraft tire monitoring device <NUM>, of an aircraft <NUM>. As illustrated in <FIG>, values and status for each of a left nose landing gear NL, a right nose landing gear NR, and first through fourth main landing gears ML1-<NUM>, are displayed in the value and status display region <NUM>. Here the values displayed for each aircraft tire monitoring device <NUM> comprise a most recent pressure reading, e.g. a most recent psi value, measured by the aircraft tire monitoring device <NUM>. The psi value may be the value as measured or expressed at a reference temperature using data from the temperature sensor.

The status messages for a given aircraft tire monitoring device <NUM> can comprise one of a pre-determined list of status messages. Status messages can include, for example, an OK message indicating that the pressure value is above a reference pressure value with no remedial action required, a FAULT message indicating that a pressure reading is not obtainable and that remedial action is required, and a SERVICE message indicating that the pressure value is below the reference pressure value with remedial action required. Remedial actions in this case can include, for example, any of checking or servicing an aircraft tire monitoring device <NUM> and replacing an aircraft tire monitoring device <NUM>.

A visual indicium <NUM> is provided for each value and status combination, with such visual indicia taking the form of a coloured ring that surrounds the corresponding value and status message. Here the visual indicium <NUM> is a binary visual indicium, in that it can be either in a red state or a green state depending on a determined priority of the status or a remedial action associated with the status, although visual indicia with a greater number of states, for example three states (red, amber, green), are also envisaged. Here a high priority status/remedial action include the FAULT or SERVICE status of the first entry <NUM> of the list <NUM>, which have an associated visual indicium <NUM> in the form of a red ring surrounding the message. A lower priority status/remedial action includes the OK statuses of the first entry <NUM> of the list <NUM>, which have an associated visual indicium <NUM> in the form of a green ring surrounding the message.

In some examples, the statuses/associated remedial actions can be utilised as secondary determiners for ordering of the list <NUM>. For example, aircraft <NUM> with a relatively higher number of remedial actions such as checking or replacing the aircraft tire monitoring device can be included further up the list than those aircraft with a relatively lower number of remedial actions. Similarly, aircraft <NUM> with a relatively higher number of higher priority remedial actions such as checking or replacing the aircraft tire monitoring device can be included further up the list than those aircraft with a relatively lower number of higher priority remedial actions.

The reference pressure display region <NUM> displays reference pressure values for the tires of the given aircraft <NUM>. As illustrated in <FIG>, for each of the first <NUM> and second <NUM> entries on the list message of "Reference Pressure (Nose - 178psi, Main - 200psi) is displayed in the reference pressure display region <NUM>. Reference pressures may be stored in association with the retrieved data and provided by the tire monitoring devices <NUM> along with the data when it is provided from the internal memory <NUM>. Alternatively, reference pressures may be stored in association with an aircraft tail ID and/or an aircraft model and retrieved separately.

The update status display region <NUM> displays a time and date at which the list entry was last updated.

The message icon <NUM> comprises a selectable icon, which is itself displayed with a status that indicates whether or not there are any messages to be displayed by selecting the selectable icon. For example, for the second entry <NUM> of the list <NUM> may have a status of "No Messages" indicated with the selectable icon also shown in green colouring. User selection of the message icon <NUM> for the second entry <NUM> of the list <NUM> will not result in any further action.

For the first entry <NUM> of the list <NUM>, a status of "Message" is indicated with the selectable icon also shown in red colouring, although other examples may use other colours than red. User selection of the message icon <NUM> for the first entry <NUM> of the list <NUM> results in a pop-up box <NUM> being displayed on the first display pane <NUM>, as shown schematically in <FIG>, where like reference numerals are used for the sake of clarity.

The pop-up box <NUM> displays further detailed messages associated with each of the tires and/or aircraft tire monitoring devices <NUM> for the given aircraft <NUM>. The messages are shown in <FIG> grouped by wheel group, although in other examples the messages may be ordered by a priority of the corresponding status message, for example with those messages corresponding to higher priority status messages displayed closer to the top of the pop-up box <NUM>. As illustrated in <FIG> and <FIG>, the left nose landing gear NL has a value of <NUM> psi and a status message of OK. The corresponding message on the pop-up box <NUM> reads "NL - OK", but also provides the further detailed message "Low battery, replace sensor at next wheel change". Display of battery status in such a manner may avoid cluttering of the first display pane <NUM> with information deemed to be of relatively low priority.

As illustrated in <FIG> and <FIG>, the right nose landing gear NR has a value of XX psi and a status message of FAULT. The corresponding message on the pop-up box <NUM> reads "NR - FAULT", but also provides the further detailed message "Sensor fault - No pressure data". This can prompt an operator to ensure that operation of the aircraft tire monitoring device <NUM> is checked to determine the fault and whether further remedial action is required.

As illustrated in <FIG> and <FIG>, the main landing gear ML1 has a value of <NUM> psi and a status message of SERVICE. The corresponding message on the pop-up box <NUM> reads "ML1 - SERVICE", but also provides the further detailed message "Service tire". This may indicate that remedial action, e.g. reinflation of the tire, is required.

As illustrated in <FIG> and <FIG>, the main landing gear ML2 has a value of <NUM> psi and a status message of OK. The corresponding message on the pop-up box <NUM> reads "ML2 - OK", but also provides the further detailed message "Low battery, replace sensor at next wheel change".

As illustrated in <FIG> and <FIG>, the main landing gear ML3 has a value of <NUM> psi and a status message of SERVICE. The corresponding message on the pop-up box <NUM> reads "ML3 - SERVICE", but also provides the further detailed message "Service tire". This may indicate that remedial action, e.g. reinflation of the tire, is required. In some examples, such a low pressure value may indicate that replacement of the tire, or indeed an associated tire on the same wheel axle, is required.

As illustrated in <FIG> and <FIG>, the main landing gear ML4 has a value of <NUM> psi and a status message of OK. The corresponding message on the pop-up box <NUM> reads "ML4 - OK", but also provides the further detailed message "Low battery, replace sensor at next wheel change".

As can be seen in <FIG>, the pop-up box <NUM> may use a respective indentation for each status. For example, in <FIG>, first, second, and third indentations are associated with the "OK", "FAULT" and "SERVICE" status, respectively. This may facilitate identification of higher priority actions among the wheels of an aircraft.

In some examples, the message or status message can comprise a hyperlink that takes an operator to an associated remedial action. For example, such a hyperlink may take a user to an electronic version of an aircraft maintenance manual (AMM), which may include airworthiness instructions for the aircraft <NUM>. In other examples, the status message may simply direct a user to look-up a relevant section of an AMM.

Whilst particular statuses and messages have been discussed above, it will be appreciated that further statuses and/or more detailed messages are also envisaged as appropriate.

The show/hide detail icon <NUM> comprises a selectable icon that, when selected by a user, causes expansion of the given entry <NUM>,<NUM> of the list <NUM> to show further detail associated with the entry <NUM>,<NUM>.

Exemplary such further detail for the first entry <NUM> of the list <NUM> is illustrated schematically in <FIG>. Here the expanded list entry <NUM> comprises a pressure and temperature display region <NUM>, a location information display region <NUM> and a data profile display region <NUM>.

The pressure and temperature display region <NUM> displays pressure and temperature values to a user via corresponding pressure <NUM> and temperature <NUM> gauges. Such gauges can comprise visual indicia that provide information including any of upper and lower limits for values, reference pressure or temperature values, and current pressure or temperature values. Such visual indicia can be colour coded to correspond to the status messages for a given aircraft tire monitoring device <NUM> in a manner similar to that previously discussed in respect of the visual indicum <NUM>.

The location information display region <NUM> displays location information corresponding to a location at which the pressure and temperature values displayed in the pressure and temperature display region <NUM> were measured. As illustrated in <FIG>, the location information comprises a map indicating location at which the measurements took place and/or were provided by the tire monitoring device for storage in the remote memory. It will be appreciated that further detail regarding the location, including for example any of an airport name associated with the location, location coordinates, date and time, can be displayed in the location information display region <NUM>.

The data profile display region <NUM> displays a snapshot of pressure and temperature profiles utilising measured pressure and temperature values around the time at which the tire pressure check that resulted in the values displayed in the pressure and temperature display region <NUM> was performed. Here the profile takes the form of a graph illustrating pressure and temperature values over time for each of the wheels of the given aircraft <NUM>. In some examples the snapshot can be static or fixed, whereas in other examples the snapshot can be interactive, for example enabling a user to filter by any of date, time, wheel, pressure, and temperature.

Referring back to <FIG>, the detailed view icon <NUM> comprises a selectable icon that, when selected, causes display of a second display pane <NUM>, with the second display pane <NUM> illustrated schematically in <FIG>. It will be appreciated that there is a different second display pane <NUM> for each aircraft <NUM> in the list <NUM>.

The second display pane comprises a plurality of selectable tabs <NUM>, and a display region <NUM> located adjacent to the plurality of selectable tabs <NUM>.

The plurality of selectable tabs <NUM> comprises an "overall data" tab <NUM>, a "temperature and pressure info" tab <NUM>, a "temperature and pressure profile" tab <NUM>, a "local airport information" tab <NUM>, and a "message information" tab <NUM>. Other tabs are also envisaged, and different tabs can be provided dependent on aircraft operator requirements. Further exemplary tabs include a wheel tracking tab, a tire tracking tab, and a tire health tab. Some examples may allow customisation of the displayed tabs, for example by a settings screen.

Selection of the overall data tab <NUM> causes the most recent pressure and temperature values, along with the location at which such values were measured, to be displayed in the display region <NUM>. This can take the form of the information displayed in the pressure and temperature display region <NUM> and the location information display region <NUM> illustrated schematically in <FIG>. Other information that can be displayed on the overall data tab <NUM> includes, for example, whether an update for an application running on the remote device <NUM> is available, whether one or more remote devices <NUM> utilised by an operator requires updating, and reminders regarding maintenance of the remote device <NUM>.

Selection of the temperature and pressure info tab <NUM> causes the most recent pressure and temperature values to be displayed in the display region <NUM>. The most recent pressure and temperature values can be displayed using gauges similar to those depicted in the pressure and temperature display region <NUM> of <FIG>.

Selection of the temperature and pressure profile tab <NUM> causes display of temperature and pressure profiles, in the form of graphs, in the display region <NUM>. This is illustrated schematically in <FIG>, where like reference numerals are used for the sake of clarity. Here separate graphs are provided for nose landing gear NL and NR of the aircraft <NUM> and for main landing gear ML1-<NUM> of the aircraft <NUM>. The graphs illustrate pressure and temperature profiles for tires of the aircraft <NUM> over a prior <NUM> day period. The graphs may be interactive to enable filtering of data, alteration of timescales, exporting of data, and any other appropriate functionality.

Selection of the local airport information tab <NUM> causes display of recent location information corresponding to the last <NUM> tire pressure checks, for example tire pressure checks made by maintenance personnel using the remote device <NUM>, in the display region <NUM>. This is illustrated schematically in <FIG>, where like reference numerals are used for the sake of clarity. Here a list of the last <NUM> airports at which tire pressure checks were performed is displayed, alongside date and time information, in the format XX/YY/ZZ and AA:BB, as to when the pressure and temperature measurements were made at that airport, with each entry on the list clickable to cause the geographic location of the airport to be displayed on a map. Airport names are not illustrated in <FIG>, as in some examples such data may not be readily available from the information obtained from the aircraft tire monitoring devices <NUM> or remote device <NUM>, whereas location coordinates may be. However, in other examples airport name data may be determined and displayed based on obtained location coordinates, for example. More than <NUM> airports may be displayed in some examples, for example with the list of airports being scrollable. In some examples, the list of airports may be ordered with those corresponding to most recent tire pressure checks first, although other orderings are also envisaged.

Display of such historic location data may enable a user to identify if and when particular issues are occurring at particular airports, thereby enabling a user to take appropriate remedial action. In some examples, further detail may be included in the list of airports, or by selecting an entry in the list of airports. For example, events such as remedial actions, including tire inflation may be displayed. Additionally or alternatively, information such as the corresponding pressure and temperature values for the tire pressure check made at that particular airport may be displayed.

Selection of the message information tab <NUM> causes message history for the given aircraft <NUM> to be displayed in the display region <NUM>. This is illustrated schematically in <FIG>, where like reference numerals are used for the sake of clarity. Here message history is displayed in the form of a list, with the list ordered by date and time, such that most recent messages are shown first. It will be appreciated that examples are envisaged where message data may be ordered differently, for example by using filters or the like. In some examples the most recent messages can be indicated to a user, for example via use of highlighting or the like.

In the list of message history, date and time information are provided for each entry, alongside the relevant status message and any more detailed remarks. For example, the list of message history can comprise a modified, e.g. extended, version of the further detailed messages displayed using the pop-up box <NUM> discussed previously. A coloured visual indicium is provided alongside each status message for ease of identifying status messages associated with determined remedial actions. A user may investigate the message history to, for example, identify recurring issues and trends.

The first <NUM> and second <NUM> display panes discussed above may facilitate ongoing maintenance of tires and/or aircraft tire monitoring devices <NUM> for a fleet of aircraft <NUM> operated by an operator. By displaying the list <NUM> of aircraft <NUM> such that aircraft <NUM> with a relatively higher priority remedial action are shown higher up the list <NUM> on the display device <NUM> than aircraft <NUM> with a relatively lower priority remedial action, a user of the aircraft tire monitoring system <NUM> may be more easily able to identify those aircraft <NUM> for which higher priority remedial actions are required, which may facilitate ongoing maintenance procedures for the identified aircraft <NUM>. The processor <NUM> ranking and sorting the positions of the aircraft <NUM> in the list <NUM>, with such a list <NUM> then automatically being displayed to the user, may be an improvement over, for example, user interface systems where aircraft are displayed with remedial actions in a non-ordered fashion or sorted without considering remedial actions.

By displaying both measured pressure values and reference pressure values in an entry for the list <NUM>, a user may be easily able to identify high and/or low pressures through simple visual comparison of data, thereby facilitating determination of an appropriate maintenance action to be taken. Use of coloured visual indicia, for example binary visual indicia, may facilitate determination of an appropriate maintenance action and provide a simple visual flag to a user. Display of status messages for a given aircraft can again facilitate determination of an appropriate maintenance action and provide a simple visual flag to a user. By providing expandable list entries and/or by providing selectable icons to take a user to a further display pane, and initial display pane can be kept visibly clear and can reduce an amount of time taken for a user to digest information and determine an appropriate maintenance action.

Maintenance actions as discussed herein can comprise one or more of causing a maintenance procedure to be performed, performing a maintenance procedure, and checking that a maintenance procedure has already been performed.

Claim 1:
An aircraft tire monitoring system (<NUM>) comprising:
a processor (<NUM>); and
a data carrier (<NUM>) comprising machine readable instructions that, when executed, cause the processor to perform operations based on a plurality of sets of values indicative of tire parameters of aircraft tires, each set of values corresponding to an aircraft (<NUM>) comprising a plurality of the aircraft tires, the operations comprising:
determining (<NUM>) a remedial action associated with each set of values; the system being characterized in that the operations further comprise:
determining (<NUM>) a priority associated with the determined remedial actions;
generating (<NUM>), based on the determined remedial actions, a list (<NUM>) of aircraft, the list of aircraft ranked based on the determined priority of remedial action; and
causing (<NUM>) a display device (<NUM>) to display the list of aircraft, such that aircraft with a relatively higher priority remedial action are shown higher up the list on the display than aircraft with a relatively lower priority remedial action.