EP3371977B1 - Method of associating locations with devices - Google Patents

Method of associating locations with devices Download PDF

Info

Publication number
EP3371977B1
EP3371977B1 EP16809565.1A EP16809565A EP3371977B1 EP 3371977 B1 EP3371977 B1 EP 3371977B1 EP 16809565 A EP16809565 A EP 16809565A EP 3371977 B1 EP3371977 B1 EP 3371977B1
Authority
EP
European Patent Office
Prior art keywords
sequencing
devices
lru
locations
identifier
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP16809565.1A
Other languages
German (de)
French (fr)
Other versions
EP3371977A2 (en
Inventor
Eric P. Moyer
Andreas ROCHAU
Christian Kissling
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Safran Passenger Innovations LLC
Original Assignee
Systems and Software Enterprises LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Systems and Software Enterprises LLC filed Critical Systems and Software Enterprises LLC
Priority claimed from PCT/US2016/060696 external-priority patent/WO2017079671A2/en
Publication of EP3371977A2 publication Critical patent/EP3371977A2/en
Application granted granted Critical
Publication of EP3371977B1 publication Critical patent/EP3371977B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/21Server components or server architectures
    • H04N21/214Specialised server platform, e.g. server located in an airplane, hotel, hospital
    • H04N21/2146Specialised server platform, e.g. server located in an airplane, hotel, hospital located in mass transportation means, e.g. aircraft, train or bus
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41Structure of client; Structure of client peripherals
    • H04N21/414Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
    • H04N21/41422Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance located in transportation means, e.g. personal vehicle

Definitions

  • the field of the invention is determination of wireless device locations.
  • IFE In-flight entertainment
  • Some systems include seat-back displays, others include overhead displays, with still others include some combination of the two.
  • Display units, whether overhead or seat-back, are typically installed at fixed locations on commercial aircraft. As technology advances, the need for wired communication between different display units becomes unnecessary, but in fully wireless IFE systems there is a need for a method of registering device locations for each display unit in the system.

Description

  • This application claims priority to U.S. Patent Application No. 15/344,352, filed November 4, 2016 , which claims the benefit of priority to U.S. Provisional Application No. 62/252,371, filed November 6, 2015 .
  • Field of the Invention
  • The field of the invention is determination of wireless device locations.
  • Background of the Invention
  • All publications identified herein are incorporated by reference to the same extent as if each individual publication or patent application were specifically and individually indicated to be incorporated by reference. Where a definition or use of a term in an incorporated reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein applies and the definition of that term in the reference does not apply.
  • In-flight entertainment (IFE) systems often have units that are specific to each seat on an aircraft. For example, some systems include seat-back displays, others include overhead displays, with still others include some combination of the two. Display units, whether overhead or seat-back, are typically installed at fixed locations on commercial aircraft. As technology advances, the need for wired communication between different display units becomes unnecessary, but in fully wireless IFE systems there is a need for a method of registering device locations for each display unit in the system.
  • In wired installations the physical locations of installed devices can be determined at run-time by analyzing the topology of the network connection between them. In wireless installations this is not possible; all wireless devices appear on the network as peers, so their physical location cannot be inferred from the network topology. The physical location of all wireless line replaceable units (LRU) must be known for accurate system status and fault reporting and to support targeted delivery of services based on aircraft cabin-class or location.
  • Thus, there is still a need for improved methods of associating locations with devices.
  • US 2006/0143660 discloses an aircraft in-flight entertainment system having a plurality of seat entertainment boxes (SEBs). Each SEB comprises a video display unit and a respective passenger control unit typically mounted in an armrest of a seat.
  • Summary of the Invention
  • In one aspect of the inventive subject matter, a method of determining locations of a set of devices that are associated with an inflight entertainment system, comprising the steps of: storing an electronic representation of a set of potential device locations in a server; and manually actuating a set of devices, by manually activating an input control on a user interface of each device in a sequence that is based on the electronic representation, wherein each device is wirelessly connected to the system; and automatically associating each device of the set of devices with a unique location of the set of potential device locations via a processor based on an order of actuation of each device and the electronic representation.
  • In some embodiments, the method additionally includes the step of determining device types. This can be accomplished by polling a wireless network to identify the set of devices connected to the wireless network.
  • The method can also include the step of interpreting a device identifier of a device using a portable electronic device, with the step of associating additionally including the task of associating each device with a unique location based on the interpreted device identifier. Polling the devices connected to the wireless network can also include the step of determining device types of each device connected to the wireless network.
  • In another aspect of the inventive subject matter, another method of determining locations of a set of devices that are associated with an in flight entertainment system is contemplated. The method includes the steps of: (1) storing an electronic representation of a set of potential device locations; (2) sequentially actuating each device of the set of devices in a predetermined sequencing order based on the electronic representation; and (3) associating each sequentially actuated device, based on the sequence that each device is actuated, with a unique location from the set of potential device locations.
  • In some embodiments, the method additionally includes the step of polling a wireless network for the in flight entertainment system to identify connected devices. The step of polling can additionally include the step of determining the device types of each device connected to the network.
  • In another aspect of the inventive subject matter, methods of determining locations of a set of devices that are associated with an in flight entertainment system are provided. Contemplated methods include the steps of: (1) storing a map having a set of potential device locations; (2) manually recording a device identifier associated with a device of the set of devices; and (3) associating the device, based on the manually recorded device identifier, with a unique location the set of potential device locations.
  • In some embodiments, the step of manually recording further includes using an electronic device to record the device identifier. Additionally or alternatively, the step of associating also includes using the electronic device to electronically associate the interpreted device identifier with the unique location. In some embodiments, the device identifier is a visual identifier (e.g., a barcode or a QR code) presented by an electronic display coupled with the device.
  • In some embodiments, the step of manually recording includes using an electronic device to interpret the device identifier via near field communication (NFC) protocol.
  • Brief Description of the Figures
    • Figure 1 shows a map of LRU locations.
    • Figure 2A shows a display device that can be used to perform sequencing, prior to conducting sequencing.
    • Figure 2B shows a display device that can be used to perform sequencing, after conducting sequencing.
    • Figure 3 shows an LRU displaying a barcode to facilitate sequencing.
    • Figure 4 shows a flow chart of a general sequencing method.
    • Figure 5 shows a flow chart of an indirect sequencing method.
    • Figure 6 shows a flow chart of a direct sequencing method.
    Detailed Description
  • In one aspect of the inventive subject matter, a method of determining wireless device locations that includes the performance of a manual maintenance operation in a manner that minimizes the time required to capture device locations, minimizes the possibility of operator error, supports configuration changes after initial installation (unit repair swaps, etc.), and provides verification that Line-Replaceable Units (LRUs) are properly associated with their physical location is contemplated. The term LRU can refer to seat-back display units, overhead display units, or any other unit implemented in an IFE (in-flight entertainment) system.
  • As used in this application, and unless the context dictates otherwise, the term "coupled to" is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms "coupled to" and "coupled with" are used synonymously.
  • It should be noted that any language directed to a computer should be read to include any suitable combination of computing devices, including servers, interfaces, systems, databases, agents, peers, engines, controllers, or other types of computing devices operating individually or collectively. One should appreciate the computing devices comprise a processor configured to execute software instructions stored on a tangible, non-transitory computer readable storage medium (e.g., hard drive, solid state drive, RAM, flash, ROM, etc.). The software instructions preferably configure the computing device to provide the roles, responsibilities, or other functionality as discussed below with respect to the disclosed apparatus. In especially preferred embodiments, the various servers, systems, databases, or interfaces exchange data using standardized protocols or algorithms, possibly based on HTTP, HTTPS, AES, public-private key exchanges, web service APIs, known financial transaction protocols, or other electronic information exchanging methods. Data exchanges preferably are conducted over a packet-switched network, the Internet, LAN, WAN, VPN, or other type of packet switched network.
  • The inventors contemplate two different types of sequencing: direct sequencing and indirect sequencing.
  • Various LRU types can be used in accordance with the inventive subject matter. In some embodiments, all of the LRUs are of the same type, but the inventors also contemplate that IFE systems can incorporate multiple different types of LRUs. Although the methods of the inventive subject matter can include a step of determining what LRU types are being used with the IFE system, the step is not required.
  • LRU types can be determined automatically or manually. For example, when LRUs are all connected to the IFE system wirelessly, the IFE system can wirelessly determine what LRUs are connected. Alternatively, a person can manually enter into the IFE system what LRUs are connected to the IFE system. LRUs can be identified by, for example, a MAC address, an IP address, a serial number, or any other unique or assigned identifier. Generally, direct sequencing will performed on a single LRU type at a time, though direct sequencing more than one type is possible as well.
  • Before direct sequencing begins, the nominal locations of all LRUs are known to the IFE system controller. Typically this information is stored in the IFE system controller's Aircraft Configuration Database (ACD). For example, for a given aircraft the System Controller would know how many LRUs (or, for example, an overhead display unit) are present in that aircraft's configuration and at which seat/row location those LRUs are installed. In other words, a map of an aircraft identifying locations for LRUs can be used to keep track of LRU locations. The map can be different depending on the type of aircraft and the IFE setup to be implemented.
  • Figure 1 shows a visual representation of a possible map 100 where LRUs are to be placed on seat backs, which are represented as seat locations 102. The map 100 can be displayed on, for example, a control panel or a portable electronic device.
  • The actual direct sequencing of the LRUs can be initiated as a maintenance operation. In some embodiments, it can be initiated from a crew panel, but in others it can be initiated at any connected LRU or other device connected to the IFE system's network.
  • Once initiated, direct sequencing is carried out by the completion of a number of steps. To complete the necessary steps, each LRU has a direct sequencing interface. Each LRU connected to the IFE system (i.e., in the "sequencing pool") preferably implements an input control which can recognize and report a "Sequencing Press Event" to the network. The input control is typically a button but could be implemented using a touch screen, a capacitive or resistive touch area, a virtual near-field data detector, an IR sensor, or the like. Figure 2A shows a touch screen 200 having an input 202 that registers a Sequencing Press Event.
  • Each LRU in the sequencing pool preferably also implements an output device which is detectable by the operator. The output device is typically a light but could be implemented as a video display, LCD, LED, near field data emitter, IR emitter, or similar. At a minimum the output device should be capable of indicating two states: sequenced and unsequenced. Additional information could be displayed to optimize direct sequencing time and error immunity.
  • In addition to an output device, a map of LRU locations can also include indicators that show when an LRU has been associated with a particular location. Figure 1 shows a visual representation of a possible map 100 where LRUs are to be placed on seat backs. Each seat location 102 on the map can also include an indicator 104, which shows when an LRU has been associated with a location 102 on the map 100.
  • At the start of direct sequencing, all of the LRUs are initialized to an unsequenced state. Then, during direct sequencing, all LRU's display a current state (e.g., unsequenced/sequenced) on their output device, which is depicted as a touch screen 200 in Figure 2A . To perform direct sequencing, an operator (e.g., a flight attendant) activates the input control on each LRU in the sequencing pool in a predetermined order (for example, left forward to aft, followed by right aft to forward). For example, Figure 2A depicts a touch screen 200 interface where an operator can press the "Press to Sequence" button 202 (the input control) to perform the direct sequencing operation. By activating the input control 202 on each LRU in the predetermined order, the IFE system registers each LRU via the IFE system's wireless network such that the location of each LRU is known to the IFE system by mapping each input signal to a location on the location map (e.g., the LRU map shown in Figure 1).
  • When an LRU's input control is activated, the IFE system controller associates the next available physical location identifier with that LRU in accordance with the predetermined sequencing order (which is determined by the nominal location map), and changes the state of that LRU from "unsequenced" to "sequenced." This change of state can be displayed on each LRU as in Figure 2B , which shows how Figure 2A would change after an operator pressed on the "Press to Sequence" button.
  • Once direct sequencing is completed, direct sequencing verification can be performed. Direct sequencing verification can be conducted by checking each LRU's output device to see a physical location identifier. In other words, if the direct sequencing operation is committed, then the mapping of LRUs to physical location identifiers determined by the direct sequencing operation is adopted by the IFE system. If the results are rejected, then direct sequencing must still be performed again before the IFE system can take LRU location into account.
  • Some LRUs do not have output devices capable of displaying a physical location identifier, and in those embodiments, all that can be seen is an indication of "sequenced" or "unsequenced" to verify whether the process was completed correctly. Displaying a physical location identifier aids in verifying that direct sequencing has been performed properly.
  • Indirect sequencing is a less automated form of sequencing. As mentioned above, indirect sequencing uses the manual observation, transcription, and reporting of arbitrary unique identifiers to determine the association between each LRU and its physical location. This differs from direct sequencing which is conducted by, for example, sequential button pressing on LRUs which are then automatically registered as existing in a predetermined location.
  • As with direct sequencing, various LRU types can be used. In some embodiments, all of the LRUs are of the same type, but the inventors also contemplate that IFE systems can incorporate multiple different types of LRUs. Although the methods of the inventive subject matter can include a step of determining what LRU types are being used with the IFE system, the step is not required.
  • LRU types can be determined automatically or manually. For example, when LRUs are all connected to the IFE system wirelessly, the IFE system can wirelessly determine what LRUs are connected. Alternatively, a person can manually enter into the IFE system what LRUs are connected to the IFE system. LRUs can be identified by, for example, a MAC address, an IP address, a serial number, or any other unique or assigned identifier. Generally, indirect sequencing will performed on a single LRU type at a time, though sequencing more than one type is possible as well.
  • Before indirect sequencing begins, the nominal locations of all LRUs should be known to the IFE system controller. Typically this information is stored in the IFE system controller's Aircraft Configuration Database (ACD). For example, for a given aircraft the System Controller would know how many LRUs (or, for example, an overhead display unit) are present in that aircraft's configuration and at which seat/row location those LRUs are installed. In other words, a map of an aircraft identifying locations for LRUs can be used to keep track of LRU locations. The map can be different depending on the type of aircraft and the IFE setup to be implemented.
  • The actual indirect sequencing of the LRUs can be initiated as a maintenance operation. In some embodiments, it can be initiated from a crew panel, but in others it can be initiated at any connected LRU or other device connected to the IFE system's network.
  • Each LRU in the sequencing pool preferably also implements an output device which is detectable by the operator. The output device is typically a light but could be implemented as a video display, LCD, LED, near field data emitter, IR emitter, or similar. At a minimum the output device should be capable of indicating two states: sequenced and unsequenced, and indicating a unique "sequencing identifier." Additional information could be displayed to optimize indirect sequencing time and error immunity.
  • At the start of indirect sequencing, all LRUs are issued a unique "sequencing identifier." During indirect sequencing, all LRUs display their sequence identifier (e.g., visually or electronically via Bluetooth, NFC, WiFi, or some other electronic or wireless communication protocol). Then, to perform indirect sequencing, the operator records the sequencing identifier of each LRU in association with the physical location identifier of that LRU (e.g., the nearest seat location). In some embodiments, the sequencing identifier is a visual identifier presented, for example, on an electronic display or as feature of the physical structure of the LRU (e.g., a sticker or a printed-on feature bearing a sequencing identifier). Examples of visual sequencing identifiers include one dimensional visual elements (e.g., line-style barcodes) or two dimensional visual elements (e.g., quick response (QR) codes). Alternatively or additionally, the sequencing identifier can be presented by the output device non-visually via, for example, near filed communication protocol (NFC), WiFi, Bluetooth, RFID, or any other wireless protocol known in the art.
  • The record can be made manually and then entered into the system (e.g., entered at the crew panel). In other embodiments, the record can be made in real-time on a wireless device or the like. For example, a crew member can have a portable electronic device that they can use to record the sequencing identifier into (or in some embodiments, the device can scan the sequencing identifier). When each sequencing identifier is recorded into that device, the location of the LRU associated with that sequencing identifier is then registered within the IFE system. This, in essence, assigns each LRU to each of the nominal locations already known to the IFE system.
  • Once indirect sequencing is completed, indirect sequencing verification can be performed. Indirect sequencing verification can be conducted by checking each LRU's output device to see a physical location identifier. In other words, if the indirect sequencing operation is committed, then the mapping of LRUs to physical location identifiers determined by the indirect sequencing operation is adopted by the IFE system. If the results are rejected, then indirect sequencing must still be performed again before the IFE system can take LRU location into account.
  • An example of an LRU that can be indirectly sequenced is shown in Figure 3 . The LRU 300 presents on its display a barcode 302. A person tasked with carrying out the indirect sequencing task would scan the barcode 302 corresponding to this LRU 300 in a predetermined order such that the location of the LRU 300 is determined according to the indirect sequencing procedure described above.
  • Some LRUs do not have output devices capable of displaying a physical location identifier, and in those embodiments, all that can be seen is an indication of "sequenced" or "unsequenced" to verify whether the process was completed correctly. Displaying a physical location identifier aids in verifying that indirect sequencing has been performed properly.
  • An example of a general sequencing method 400 is shown in Figure 4 . In the first step 402, an electronic representation of a set of potential device locations is stored in a server. In the second step 404, each device is automatically associated with a unique location via a processor by actuating the devices in a sequence that is based on the electronic representation, where each device is wirelessly connected to the system.
  • Outside of these method steps, three optional steps 406, 408, & 410 are contemplated. In optional step 406, device types are determined. In optional step 408, a device identifier of a device is interpreted using a portable electronic device, and the step of associating is modified to additionally associate each device with a unique location based on the interpreted device identifier. In optional step 410, a wireless network is polled to identify the set of devices connected to the wireless network.
  • An example of an indirect sequencing method 500 is shown in Figure 5 . In the first step 502, an electronic representation of a set of potential device locations is stored (e.g., to a server). In the next step 504, each device of the set of devices is sequentially actuated in a predetermined sequencing order based on the electronic representation. In the next step 506, each sequentially actuated device, based on the sequence that each device is actuated, is associated with a unique location from the set of potential device locations.
  • Two optional steps 508 and 510 can also be executed as a part of the method. In step 508, a wireless network is polled for the in flight entertainment system to identify connected devices. In step 510, device types of each device are determined.
  • An example of a direct sequencing method 600 is shown in Figure 6 . In the first step 602, an electronic representation of a set of potential device locations is stored (e.g., to a server). In the next step 604, each device identifier associated with a device is manually recorded. In the next step 606, the device, based on the manually recorded device identifier, is associated with a unique location the set of potential device locations. In the next step 608, the electronic device is used to electronically associate the interpreted device identifier with the unique location.
  • Two optional steps 610 and 612 can also be executed as a part of the method. In step 610, an electronic device (e.g., a mobile computing device like a cell phone) is used to interpret the device identifier via near field communication (NFC) protocol. In step 612, an electronic device is used to record the device identifier.
  • In some embodiments, the numbers expressing quantities of ingredients, properties such as concentration, reaction conditions, and so forth, used to describe and claim certain embodiments of the invention are to be understood as being modified in some instances by the term "about." Accordingly, in some embodiments, the numerical parameters set forth in the written description and attached claims are approximations that can vary depending upon the desired properties sought to be obtained by a particular embodiment. In some embodiments, the numerical parameters should be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of some embodiments of the invention are approximations, the numerical values set forth in the specific examples are reported as precisely as practicable. The numerical values presented in some embodiments of the invention may contain certain errors necessarily resulting from the standard deviation found in their respective testing measurements.
  • Unless the context dictates the contrary, all ranges set forth herein should be interpreted as being inclusive of their endpoints and open-ended ranges should be interpreted to include only commercially practical values. Similarly, all lists of values should be considered as inclusive of intermediate values unless the context indicates the contrary.
  • As used in the description herein and throughout the claims that follow, the meaning of "a," "an," and "the" includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise.
  • The recitation of ranges of values herein is merely intended to serve as a shorthand method of referring individually to each separate value falling within the range. Unless otherwise indicated herein, each individual value with a range is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g. "such as") provided with respect to certain embodiments herein is intended merely to better illuminate the invention and does not pose a limitation on the scope of the invention otherwise claimed. No language in the specification should be construed as indicating any non-claimed element essential to the practice of the invention.
  • Groupings of alternative elements or embodiments of the invention disclosed herein are not to be construed as limitations. Each group member can be referred to and claimed individually or in any combination with other members of the group or other elements found herein. One or more members of a group can be included in, or deleted from, a group for reasons of convenience and/or patentability. When any such inclusion or deletion occurs, the specification is herein deemed to contain the group as modified thus fulfilling the written description of all Markush groups used in the appended claims.
  • The scope of the invention is defined by the appended claims.

Claims (5)

  1. A method of determining locations of a set of devices that are associated with an in-flight entertainment system, comprising the steps of:
    storing an electronic representation of a set of potential device locations in a server (402, 502);
    manually actuating a set of devices, by manually activating an input control (202) on a user interface (200) of each device in a sequence that is based on the electronic representation, wherein each device is wirelessly connected to the system; and
    automatically associating each device of the set of devices with a unique location of the set of potential device locations via a processor based on an order of actuation of each device and the stored electronic representation (404, 506).
  2. The method of claim 1, further comprising the step of determining device types (406, 510).
  3. The method of claim 1, further comprising the step of interpreting a device identifier of a device of the set of devices using a portable electronic device, and wherein the step of associating further comprises associating each device with a unique location based on the interpreted device identifier (408).
  4. The method of claim 1, further comprising polling a wireless network for the in-flight entertainment system to identify devices of the set of devices that are connected to the wireless network (410, 508).
  5. The method of claim 4, wherein the step of polling further comprises determining device types of each device of the set of devices (510).
EP16809565.1A 2015-11-06 2016-11-04 Method of associating locations with devices Active EP3371977B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562252371P 2015-11-06 2015-11-06
PCT/US2016/060696 WO2017079671A2 (en) 2015-11-06 2016-11-04 Method of associating locations with devices

Publications (2)

Publication Number Publication Date
EP3371977A2 EP3371977A2 (en) 2018-09-12
EP3371977B1 true EP3371977B1 (en) 2020-01-01

Family

ID=63077612

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16809565.1A Active EP3371977B1 (en) 2015-11-06 2016-11-04 Method of associating locations with devices

Country Status (1)

Country Link
EP (1) EP3371977B1 (en)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP3371977A2 (en) 2018-09-12

Similar Documents

Publication Publication Date Title
US20210042014A1 (en) Vehicle diagnostic systems and methods
CN103246692B (en) System and method for maintenance and operation aircraft
US10097950B2 (en) Method of associating locations with devices
EP3531664A1 (en) Method, device, and server for unlocking air conditioning unit
CN104021442B (en) Label system and method is changed based on stroke
EP3583031B1 (en) Apparatus, systems, and methods for life vest identification, inspection, and maintenance
US11206520B2 (en) Method for line-replaceable unit identification, localization and status retrieval
DK2715677T3 (en) Diagnostic device for motor vehicles and diagnostic procedure
US9934629B2 (en) Vehicle maintenance system and method
US8732586B2 (en) Complex system function status diagnosis and presentation
JP2012256276A (en) Data center navigation system
CN107257925A (en) The system and method for showing gas concentration
WO2018215658A1 (en) A system for monitoring occupancy of a seat arranged in a transportation vehicle
JP2017041018A (en) Conveyance information gathering system
EP3371977B1 (en) Method of associating locations with devices
RU2767142C2 (en) Autonomous low-energy access indication system
US11138542B2 (en) Confirming field technician work based on photographic time and location device
JP6906793B2 (en) Labor management system and computer program
US20240086846A1 (en) Operation management system and operation management method
CN109545366B (en) Method and system for summarizing diagnostic analyzer related information
CN109447401A (en) Ground health control method, system and device based on adaptive resource allotment
JP2017142646A5 (en)
CN105844372A (en) Vehicle chain management mode system

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180430

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20190213

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602016027497

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04N0021214000

Ipc: H04W0004020000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/02 20180101AFI20190719BHEP

Ipc: H04N 21/214 20110101ALI20190719BHEP

Ipc: H04N 21/414 20110101ALI20190719BHEP

INTG Intention to grant announced

Effective date: 20190826

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1221344

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200115

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016027497

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200101

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200527

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200401

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200401

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200501

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200402

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016027497

Country of ref document: DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 602016027497

Country of ref document: DE

Representative=s name: VENNER SHIPLEY GERMANY LLP, DE

Ref country code: DE

Ref legal event code: R082

Ref document number: 602016027497

Country of ref document: DE

Representative=s name: VENNER SHIPLEY LLP, DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1221344

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200101

26N No opposition filed

Effective date: 20201002

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201104

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201130

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201104

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200101

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201130

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231019

Year of fee payment: 8

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231019

Year of fee payment: 8

Ref country code: DE

Payment date: 20231019

Year of fee payment: 8