Patent Application
20180229862
The field of the invention is apparatus, systems, and methods for facilitating life vest inspection and maintenance.
The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
Life vests are typically installed under or near each seat of an aircraft to ensure there is at least one life vest for each passenger on board. Before boarding, crew members typically inspect to verify that a life vest is stowed under or near each seat and has not been stolen or otherwise removed. During routine maintenance, each life vest may be removed to check the expiration date; however, these inspections can be labor intensive and costly.
In an effort to increase the efficiency of life vest inspections, U.S. patent application Ser. No. 11/694,564 to Bartz et al. discloses the use of radio frequency identification (“RFID”) technology and a user interface, which displays inspection information on a screen. RFID tags are installed in/on life vests or their packaging. An airline employee may then move within an aircraft and interrogate the RFID tags row-by-row using an RFID reader. A display shows visual indicia of at least a portion of the aircraft where a life vest is expected to be found. The visual indicia are updated with information read from the RFID tags, such as whether one or more life vests have expired, are about to expire, or are not present. However, Bartz's methods still require an airline employee to move about the cabin to interrogate RFID tags, which have the disadvantages mentioned above. In addition, RFID tags typically require power, increasing the cost of each RFID tag. Ayyagari et al. describe similar methods and systems in U.S. Pat. No. 7,589,636.
U.S. Pat. No. 9,162,776 to Shore et al. describes an aircraft monitoring system in which items, including oxygen generators and life vests are equipped with RFID tags. RFID interrogators are adapted to determine an issue with respect to any of the RFID equipped items and may be integrated into pre-existing systems. Typically, during pre-flight procedures, a flight attendant or other employee walks through the aircraft and uses a RFID interrogator to determine whether any of the RFID equipped items requires service, repair, replacement and/or maintenance. However, Shore's methods still share many or all of the disadvantages described above.
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.
Thus, there is still a need for life vest inspection apparatuses, systems, and methods that (1) save time for life vest inspections before passenger boarding, (2) are inexpensive, (3) do not require powering the component installed on the life vest, and (4) do not require an inspector to go to multiple locations within the cabin.
The inventive subject matter provides apparatus, systems and methods in which an automated inspection system identifies whether a life vest is present in its proper location (e.g., under a passenger seat), whether the life vest has expired, and/or whether the life vest has been altered or tampered with. Although the below discussion references aircraft, it is contemplated that the system could be used in other vehicles, such as boats, busses, and trains, for example. Furthermore, although life vests are described, the same system could be used with other articles that require constant or periodic monitoring of their location and/or status.
Contemplated life vest inspection systems include near-field communication (“NFC”) readers installed where life vests are stowed. Typically, life vests are stowed under each passenger seat, although in some classes of service or for other reasons, life vests may be stowed in a specified compartment or in one or more overhead bins. Each NFC reader is positioned so that it can communicate with passive NFC tags installed in life vests or their packaging. In some embodiments, each NFC tag can correspond to a single NFC reader; however, in other embodiments, it is contemplated that a single NFC reader may be within a range to read two or more NFC tags due to proximity. Because NFC readers typically have a maximum range of about 4 inches (10 centimeters), the NFC tag of each properly stowed life vest should be within the range of at least one NFC reader. In some embodiments, the numbers expressing quantities, properties, 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.
The NFC reader is preferably connected, either wired or wirelessly, to an embedded cabin management system, such as an in-flight entertainment (“IFE”) system. 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.
The cabin management system may provide power to the NFC reader. Additionally, the cabin management system preferably provides the seat number(s) associated with each NFC reader and/or NFC tag. Optionally, the cabin management system may provide a system time to the life vest inspection system.
Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.
Throughout the following discussion, numerous references will be made regarding servers, services, interfaces, portals, platforms, or other systems formed from computing devices. It should be appreciated that the use of such terms is deemed to represent one or more computing devices having at least one processor configured to execute software instructions stored on a computer readable tangible, non-transitory medium. For example, a server can include one or more computers operating as a web server, database server, or other type of computer server in a manner to fulfill described roles, responsibilities, or functions.
The following discussion provides many example embodiments of the inventive subject matter. Although each embodiment represents a single combination of inventive elements, the inventive subject matter is considered to include all possible combinations of the disclosed elements. Thus if one embodiment comprises elements A, B, and C, and a second embodiment comprises elements B and D, then the inventive subject matter is also considered to include other remaining combinations of A, B, C, or D, even if not explicitly disclosed.
The following description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.
When a system time is available, the system may display and/or record what time the status was last updated, and the time when a life vest indicator changes, for example. In one embodiment, the system could cause a message or alarm to sound when a life vest is removed during a flight. Such messages or alerts may prompt a flight attendant to inspect the life vest and assist in making sure that it is properly replaced. The system may also automatically provide the passenger with instructions how to replace the life vest via the IFE system. In another example, the system can record the time when a life vest is removed and from which seat. If the life vest is not replaced, the airline may charge the passenger sitting in that seat for the missing life vest or initiate an investigation.
In some embodiments, a person can initiate an inspection, and the time of the inspection may be saved with the inspection results. The person can then replace a life vest when the display shows that one or more life vests have gone missing or expired.
Display 110 has a user interface showing a representation of a portion of the airplane cabin, and representations for each of the seats in rows 9-11, labeled in columns A-F. Seats 11A, 11B and 11C are illustrated to the right.
In this embodiment, and as shown in
NFC readers 130 are coupled to the IFE system 140 via path 145, which may be physical (wired) or wireless. Coupling the cabin management system to each NFC reader 130 allows for information to be transmitted from the NFC reader 130 to the cabin management system. The cabin management system also provides power to the NFC readers 130.
In
Because there is no life vest under seat 11B, NFC reader 130 does not detect any NFC tag. An indicator for each life vest is illustrated in display 110 in
The graphical user interface on the display 110 of the cabin management system may additionally or alternatively show the whole cabin or other portions thereof, such as grouping first class, business class, and economy on different screens. In another embodiment, groupings of between 1 and 25 rows, preferably 3-6 rows will be visible at one time, and crew members can scroll through the rows. It is also contemplated that the interface can immediately display a list or graphical view of any missing life vests. 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. In cases where it is desirable to view additional details about the information collected by the NFC readers, the crew member may zoom-in to view 1, 2, 3, 4, or more seats at a time, depending on the amount of information provided for each seat and the size of the display.
With respect to the life vest indicators, a green indicator could indicate that the life vest has not been tampered with and is not expired. A yellow indicator may signify that the NFC tag for a life vest was at least temporarily out of the range of the NFC reader, indicating that the life vest has been removed and replaced, and perhaps tampered with. Thus, a yellow indicator may indicate that a crew member should inspect the corresponding life vest. Additionally or alternatively, a yellow life vest indicator could signify that the life vest will expire soon, such as in one day, one week, or one month. An indicator could also flag that a life vest should be replaced at the next scheduled maintenance inspection, because it will expire before the subsequent scheduled maintenance inspection. In addition to indicating that a life vest is missing, a red indicator may signify that the life vest has expired and needs to be replaced. It should be appreciated that use of other indicators or symbols (e.g., checks and crosses, 0s and 1s, present and absent, or other alphanumeric words/codes) are consistent with the inventive subject matter.
In some embodiments, the NFC readers can be triggered or activated from the cabin management system, such as the central computer of an IFE system. It may also be desirable for the NFC reader to be triggered automatically when the NFC tag on a life vest comes within the range of the NFC reader. After the NFC reader is initially triggered, a crew member may perform an inspection by viewing the graphical user interface to review the life vest indicators from the NFC readers. The crew member may optionally, use the graphical user interface to command the NFC readers to read data from the NFC tags before such an inspection. In another embodiment, the NFC readers continuously or semi-continuously attempt to take readings from the NFC tags within their range, or at defined points of flight (e.g., during the flight attendant checks that occur prior to landing, for example). Readings may also be taken at regular intervals, such as every 10, 15, 20, 30, 45, or 60 minutes. The life vest inspection system may also provide real-time indicators, notification and/or warnings when an indicator changes.
For example, the notification or warning could be a reminder that one life vest of the plurality of life vests will expire within a certain time period, such as one day, one week, or one month. The time could also be set, so an inspector or maintenance technician is instructed to replace life vests at the next maintenance inspection, before the life vests expire.
In another example, the inspection system provides an audio notification in real-time when one life vest indicator of the plurality of life vest indicators changes. This would allow crew members to investigate when a life vest is removed from its stowage location by a passenger, preventing theft and/or to make sure the life vest is not tampered with and is properly replaced. When a life vest expires, it is contemplated that the inspection system could issue an audio or other notice, so a crew member can replace the life vest immediately.
In another embodiment, the graphical user interface displays life vest indicators in a list or table with other information about the each life vest. For example, tables may include seat numbers and installation statuses, expiration dates, expiration statuses, and/or a tamper status. A system time may optionally be displayed as well.
In another aspect of the inventive subject matter, a method of inspecting life vests comprises obtaining a plurality of life vest indicators using a plurality of NFC readers. The plurality of NFC readers reads the plurality of life vest indicators from a plurality of NFC tags on a plurality of life vests or life vest packages. Next, the plurality of life vest indicators is transmitted to a cabin management system. A seat number is assigned to each life vest indicator. A user interface may be depicted on a display of the cabin management system that depicts a schematic representation of at least a part of the cabin. The schematic representation further show the life vest indicators that correspond to each seat number for the part of the cabin displayed. The system then updates the display to show an updated status indicator.
As explained above, the life vest indicators comprise at least one of an installation status, an expiration status, and a tamper status. Methods of inspecting life vests may further comprise a step of triggering the NFC readers from the cabin management system, before the step of obtaining a plurality of life vest indicators. Additionally, or alternatively, the triggering step may be performed automatically when installing a life vest having an NFC tag associated with it or its packaging.
All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context.
As used herein, 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.
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.
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.
It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the spirit of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms “comprises” and “comprising” should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C . . . and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.
This application claims priority to U.S. provisional application Ser. No. 62/458,908 filed on Feb. 14, 2017. This and all other referenced extrinsic materials are incorporated herein by reference in their entirety. Where a definition or use of a term in a reference that is incorporated by reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein is deemed to be controlling.
| Number | Date | Country | |
|---|---|---|---|
| 62458908 | Feb 2017 | US |
