Patent Description:
Fluid streams often carry particulate material therein. In many instances, it is desirable to remove some or all of the particulate material from a fluid flow stream. For example, air intake streams to engines for motorized vehicles or power generation equipment, gas streams directed to gas turbines, and air streams to various combustion furnaces, often include particulate material therein. The particulate material, should it reach the internal workings of the various mechanisms involved, can cause substantial damage thereto. It is therefore desirable for such systems to remove the particulate material from the fluid flow upstream of the engine, turbine, furnace or other equipment involved.

A variety of air filter or gas filter arrangements have been developed for particulate removal. Beyond particulate removal, filtration systems can also be used as gas phase or liquid phase contaminant removal systems.

Many filtration systems include portions that are designed to be substantially permanent (such as filter housings) and portions that are designed to be replaced periodically to assure proper operation (such as filter elements that fit within filter housings).

Document <CIT> discloses a filter system with a wireless identification tag coupled to a replaceable filter element to identify the filter element.

Document <CIT> is directed to a filter device for a motor vehicle, comprising at least one gas filter element arranged in a corresponding housing and a sensor device for determining a parameter, which is the installation position of the filter element and time of installation of the filter element. The parameter is transferable to an evaluation unit for evaluating the parameter.

A method according to the invention of providing data to a filtration system is disclosed in any one of claims <NUM>-<NUM>.

A filtration system according to the invention is disclosed in any one of claims <NUM>-<NUM>.

This summary is an overview of some of the teachings of the present application and is not intended to be an exclusive or exhaustive treatment of the present subject matter. Further details are found in the detailed description and appended claims. Other aspects will be apparent to persons skilled in the art upon reading and understanding the following detailed description and viewing the drawings that form a part thereof, each of which is not to be taken in a limiting sense. The scope herein is defined by the appended claims and their legal equivalents.

Aspects may be more completely understood in connection with the following drawings, in which:.

While embodiments are susceptible to various modifications and alternative forms, specifics thereof have been shown by way of example and drawings, and will be described in detail. It should be understood, however, that the scope herein is not limited to the particular embodiments described. On the contrary, the intention is to cover modifications and alternatives falling within the scope as defined by the claims.

As described above, many filtration systems include a portion (such as a filter element) that must be replaced periodically to maintain a desired level of filtration performance. Other portions of the filtration system, such as the filter housing, are designed to be substantially permanent and remain in place after initial installation (either during initial system/vehicle assembly in an OEM scenario or after installation of an after-market kit).

In some cases, filtration systems (or other components separate from the filtration system such as a separate reader or computation device) can include one or more processing circuits and/or processors and may execute various operations including performing various calculations, including but not limited to, end-of-life (EOL) calculations, plugging calculations, and the like. Firmware or other types of stored electronic instructions and/or operating software can be used to direct the operations performed by the system.

If the filtration system can be connected to a data network then it can be possible to send instructions to the filtration systems remotely and/or send updates including updates to firmware, operating software, or the like. However, the filtration system may not be connected to a data network and/or it may be impossible to send instructions or updates to the filtration systems installed in the field over a data network. Further, in some scenarios the filtration system may be connected to a data network, but for various reasons data flow may be limited to one-way (e.g., machine to network). In yet other scenarios, there may be a network connection, but it may be unreliable or inconsistently available. In these cases, it can be extremely challenging to keep the system components updated with the latest firmware, operating software, etc..

In accordance with embodiments herein, certain types of data, such as firmware and/or other software updates, can be loaded onto replaceable filter elements (or other replaceable system components) and can be conveyed onto filtration systems that are installed in the field when a filter element or other replaceable element is installed. In this manner, firmware and other software updates can be provided to remote, field-installed systems despite there being no direct connection available to those remote, field-installed systems through a data network. This approach can solve a long-standing problem associated with providing updates to remote, field-installed systems that are not directly reachable through a data network such as the Internet or another type of data network.

As used herein, the term "firmware" shall refer to a specific class of computer software that provides the low-level control for the device's specific hardware. Firmware is generally held in non-volatile memory devices such as ROM, EPROM, or flash memory.

Referring now to <FIG>, a schematic view of a supply chain flow of replaceable filter elements <NUM>, <NUM> is shown in accordance with various embodiments herein. Specifically, in this view, the conveyance of filter elements from a manufacturing facility <NUM> onto a remote, field installed filtration system <NUM> is shown. Filter elements <NUM>, <NUM> are produced, in whole or in part, at the manufacturing facility <NUM>. The filter elements <NUM>, <NUM> can be of various types. In some embodiments, the filter elements can be a primary filter element <NUM> and a secondary or safety filter element <NUM>. In some embodiments, there may only be a single type of filter element that passes through the supply chain to enable replacement. The filter elements can be for used in air intake filtration systems, exhaust filtration systems, fuel filtration systems, oil/lubricant filtration systems, industrial air particulate filtration systems, air handling systems, or the like.

At or after the time of filter element manufacture, data can be loaded onto the filter elements <NUM>, <NUM>. For example, in some embodiments data can be loaded onto the filter elements at a manufacturing facility <NUM>. In some embodiments, data can be loaded onto a data storage element prior to filter element manufacture and then the data storage element can be integrated with the other filter element components during filter element manufacturing processes (e.g., an inventory of pre-programmed data storage elements could be maintained and then used during the manufacturing process). In other embodiments, a data storage element can be integrated with other filter element components during manufacturing first and then data can be loaded onto the data storage element later (e.g., an inventory of data storage elements that still require programming could be maintained). In some embodiments, data can be loaded onto the filter elements after they have left the manufacturing facility <NUM>, but are still within the supply chain. For example, in some embodiments, data can be loaded onto the filter elements at a distribution or transport facility. In still further embodiments, data can be loaded onto the filter elements at a customer facility before installation of the filter elements.

The filter elements can include data storage circuits/components thereon with which to receive and store the data. The data can be of various types, such as such as firmware and/or other software updates. In some embodiments, the filter elements <NUM>, <NUM> are ultimately installed in a filtration system <NUM> within a vehicle <NUM>. In this case, the filtration system <NUM> is a remote, field-installed system within a vehicle <NUM>. However, it will be appreciated that the remote field-installed system could also be within another type of environment besides a vehicle such as a remote plant or factory with an industrial air filtration system. The vehicle <NUM> can include an ECU (engine control unit) <NUM> and can, of course, also include many other components. In some embodiments, the ECU <NUM> and the filtration system <NUM> can exchange data. In some embodiments, the filtration system <NUM> can send data to the ECU <NUM> or receive data from the ECU <NUM> through a CAN bus system or other type of local data network. In other embodiments, however, the filtration system <NUM> and the ECU <NUM> are completely isolated from one another in terms of data exchange. In non-engine applications, a device equivalent to an ECU can be present, such as a master control system or other high-level system including a processor or other computing device and taking inputs from the overall system.

Referring now to <FIG>, a schematic cross-sectional view of a filtration system <NUM> with a primary filter element <NUM> and a secondary or safety filter element <NUM> installed therein in accordance with various embodiments herein. This serves as merely one example of a filtration system and many other types of filtration systems are contemplated herein. With reference to the primary filter element <NUM>, a filter body <NUM> and filter media <NUM> disposed within the filter body <NUM> can be included. However, it will be appreciated that the secondary or safety filter element <NUM>, as well as other filter elements can similarly include a filter body and filter media. The filtration system <NUM> can include a housing <NUM> comprising a fluid inlet <NUM> and a fluid outlet <NUM>, the housing defining an internal volume. A primary filter element <NUM> can be disposed within the internal volume of the housing <NUM> and can be configured to be removably disposed therein. The proximal end of the internal volume is configured to engage with a removable cover <NUM> that fits adjacent to the proximal end in order to seal off the proximal end of the housing from the flow of fluid there through. The removable cover <NUM> can engage the proximal end and remain attached thereto through various devices or structures including threads, friction-fit mechanisms, latches, buckles, snap-fit mechanisms, or the like.

A data storage element <NUM> can be associated with the secondary or safety filter element <NUM>. A data storage element <NUM> can also be associated with the primary filter element <NUM>. However, while not intending to be bound by theory, it is believed that in some embodiments the primary filter element <NUM> is replaced more often than the secondary or safety filter element <NUM>. As such, in some embodiments, to maximize opportunities to convey data while simultaneously reducing cost and overall complexity of the system, only the primary filter element <NUM> includes a data storage element <NUM> and not the secondary or safety filter element <NUM>. Alternatively, in some embodiments, a data storage element <NUM> associated with a secondary or safety filter element <NUM> stores a lesser amount of data, and/or a different kind of data, than that stored by a data storage element <NUM> associated with a primary filter element <NUM>.

One or both of the data storage elements <NUM>, <NUM> can communicate, either through a wired or wireless data connection, with a filter housing associated reader device <NUM>. Alternatively, or in addition, one or both of the data storage elements <NUM>, <NUM> can communicate, either through a wired or wireless data connection, with a separate reader device <NUM>. The separate reader device <NUM> can be part of a vehicle or other equipment structure or can be off-vehicle or completely separate from other equipment structures.

It will be appreciated that filtration systems herein can take on many different shapes and configurations. Referring now to <FIG>, a schematic cross-sectional view is shown of a filtration system <NUM> with a primary filter element <NUM> and a secondary filter element <NUM> installed therein in accordance with various embodiments herein. The filtration system <NUM> can include a housing <NUM> comprising a fluid inlet <NUM> and a fluid outlet <NUM>. The housing can define an internal volume <NUM>. The primary filter element <NUM> can be disposed within the internal volume <NUM> of the housing <NUM> and can be configured to be removably disposed therein. The secondary filter element <NUM> can be disposed within the internal volume <NUM> of the housing <NUM> and can also be configured to be removably disposed therein. In this embodiment, the primary filter element <NUM> can be removed with or without also removing the secondary filter element <NUM>.

The proximal end of the internal volume <NUM> is configured to engage with a cover <NUM> that fits adjacent to the proximal end <NUM> in order to seal off the proximal end of the housing from the flow of fluid there through.

A first data storage element <NUM> can be associated with, such as disposed on or in, the primary filter element <NUM> and a second data storage element <NUM> can be associated with, such as disposed on or in, the secondary filter element <NUM>. One or both of the data storage elements <NUM>, <NUM> can communicate, either through a wired or wireless data connection, with a filter housing associated reader <NUM>. Alternatively, or in addition, one or both of the data storage elements <NUM>, <NUM> can communicate, either through a wired or wireless data connection, with a separate reader device <NUM>.

Referring now to <FIG>, a schematic view is shown of data storage hardware and data types in accordance with various embodiments herein. In various embodiments, an electronic circuit or electronic component <NUM> can be used to store data <NUM>. Various types of memory storage can be used, including dynamic RAM (D-RAM), read only memory (ROM), static RAM (S-RAM), disk storage, flash memory, EPROM. battery-backed RAM such as S-RAM or D-RAM and any other type of digital data storage component. In some embodiments, the electronic circuit or electronic component includes non-volatile memory and/or volatile memory. In some embodiments, the electronic circuit or electronic component can include transistors interconnected so as to provide positive feedback operating as latches or flip flops, providing for circuits that have two or more metastable states, and remain in one of these states until changed by an external input. Memory storage can be based on such flip-flop containing circuits. Memory storage can also be based on the storage of charge in a capacitor or on other principles.

In some embodiments, the electronic circuit or electronic component <NUM> storing data can be in electronic communication with other components such as a communication circuit, and antenna, a power source (such as a battery), or the like.

The data <NUM> stored by the electronic circuit or electronic component <NUM> can be of various types <NUM> including, but not limited to filter element intrinsic data <NUM>, operational program data <NUM>, and extrinsic data <NUM>.

By way of example, in some embodiments, the data <NUM> can include filter element intrinsic data <NUM>. Examples of filter element intrinsic data <NUM> can include, but are not limited to, a manufacturing date; a filter element ID; a filter element model ID; a filter element manufacturer ID; a filter element manufacturing plant ID; and a filter element performance characteristic. Filter element performance characteristics can include, but are not limited to, filter element capacity information, filter element terminal pressure drop associated with model ID, filter element loading curves, filter element loading coefficients, typical fuel consumption rate for a machine associated with the filter element model ID, fuel usage penalty factor for increased filter element pressure drop for a machine associate with the filter element model ID. In various embodiments, the filter element intrinsic data <NUM> can be in the form of ASCII, hexadecimal, octal, decimal, binary, HTML, or other character or symbol codes stored electronically. In various embodiments, the filter element intrinsic data <NUM> is not in the form of compiled code. In some embodiments, filter element intrinsic data <NUM> can be encrypted at rest on the filter element.

In some embodiments, the data <NUM> can include operational program data <NUM>. Examples of operational program data <NUM> can include, but are not limited to, an algorithm definition, an operating software update, and a firmware update. In some embodiments, an algorithm definition can include at least one of an end-of-life (EOL) prediction algorithm definition, a regeneration event recommendation algorithm definition, and a filtration performance algorithm definition. In various embodiments, the operational program data can be compiled code, compiled code modules, one or more compiled code libraries, binary code libraries, object code, assembly code, and/or machine code or the like. In some embodiments, operational program data <NUM> can be encrypted at rest on the filter element.

In some embodiments, the operating software update can be a reader device operating software update or an operating software update for a device other than a reader device. In some embodiments, the firmware update can be a reader device firmware update or a firmware update for a device other than a reader device.

In some embodiments, the data <NUM> can include extrinsic data <NUM>. Extrinsic data can be important for calculating economically optimal filter clement change/replacement times/intervals. Examples of extrinsic data <NUM> can include, but are not limited to, fuel cost per unit of fluid measure, fuel formulation data. environmental emissions regulation data, date of extrinsic data revision, cost of filter element, labor cost to change filter element associated with filter element model ID, etc. In various embodiments, the extrinsic data <NUM> can be in the form of ASCII, hexadecimal, octal, decimal, binary, HTML, or other character or symbol codes stored electronically. In various embodiments, the extrinsic data <NUM> is not in the form of compiled code. In some embodiments, extrinsic data <NUM> can be encrypted at rest on the filter element.

Further examples of the types of data that can be conveyed in accordance with embodiments herein are shown with respect to Table <NUM> below.

In various embodiments, data carried by filter elements or portions thereof can be encrypted and/or digitally signed to secure the data and/or provide authentication as to the source of the data. Referring now to <FIG>, a schematic view is shown of a flow of filter elements in accordance with various embodiments herein.

At a manufacturing facility <NUM>, or at another point during distribution, data can be loaded onto a data storage element of a filter element. In some embodiments, the data can be digitally signed using a manufacturer-specific private key <NUM> (part of a standard public/private key architecture or PKI - public key infrastructure). By applying a digital signature with a manufacturer-specific private key <NUM>, later on the public key <NUM> for that manufacturer can be used to verify that the data carried by the filter element is authentic and did, in fact, come from the manufacturer or the holder of the private key.

Alternatively, or in addition to digitally signing the data, the data can be encrypted using a manufacturer specific public key. In this way, only a device holding the manufacturer specific private key (forming a pair with the public key used for encryption - separate from the key pair used for digitally signing) can be used to decrypt the data.

The filter elements <NUM>, <NUM> can be installed in a filter housing <NUM>. After installation, a public key of the manufacturer can be used to verify the digital signature applied at the manufacturing facility <NUM>. Alternatively, or in addition, a private key of the manufacturer can be used to decrypt the data content stored by the data storage element. A private key of the manufacturer can be stored with the filter housing <NUM> and/or a reader device at the time the filter housing <NUM> or reader device is manufactured or at the time the filter housing <NUM> or the reader device is installed on vehicle, machine, in a plant location, etc. The public key of the manufacturer can also be stored with the filter housing <NUM> and/or reader device. In some embodiments, the public key of the manufacturer can be passed along to the filter housing <NUM> or reader device by being carried with a filter element.

Circuitry associated with filter elements herein can include various specific electronic components in order to execute operations as described herein. Similarly, circuitry associated with reader devices herein (either as associated with a filter housing or other filter structure or as located separately from a filter housing or other filter structure) can include various specific electronic components in order to execute operations as described herein. Referring now to <FIG>. a schematic view of components of a system is shown in accordance with various embodiments herein.

Components associated with a data storage element <NUM> can include one or more of an antenna <NUM>, a power supply circuit <NUM> (which can include one or more of a battery, a capacitor, a power-receiver such as a wireless power receiver), a control circuit <NUM> (which can include a processor, a microcontroller, an ASIC, or the like), a memory storage circuit <NUM> (which can include volatile or non-volatile electronic memory), a communication circuit <NUM>, and a cryptographic circuit <NUM> (which can include a specialized cryptographic processor and/or data associated with cryptographic functions). In some embodiments herein, a wireless power receiver can include an LC circuit. In some embodiments, the wireless power receiver can include an RF power receiver. In some embodiments, one or more components of a power supply circuit, such as a wireless power receiver, can be disposed on or in the filter body.

It will be appreciated that in some embodiments a specific data storage element <NUM> may not include all of the components shown and described with respect to <FIG>. In addition, in some embodiments data storage element <NUM> may include additional components beyond what is shown and described with respect to <FIG>.

Components associated with a reader device <NUM> can include one or more of an antenna <NUM>, a power supply circuit <NUM> (which can include one or more of a battery, a capacitor, or a power-receiver), a control circuit <NUM> (which can include a processor, a microcontroller, an ASIC, or the like), a memory storage circuit <NUM> (which can include volatile or non-volatile memory), a communication circuit <NUM>, a cryptographic circuit <NUM> (which can include a specialized cryptographic processor and/or data associated with cryptographic functions), a clock circuit <NUM>, and a location circuit <NUM>.

In some embodiments, communication between components of a system can be conducted wirelessly. However, in other embodiments, communication between components of a system can be conducted through a wired connection. Referring now to <FIG>, a schematic view is shown of components of a system in accordance with various embodiments herein.

Components associated with a data storage element <NUM> can include one or more of a control circuit <NUM> (which can include a processor, a microcontroller, an ASIC, or the like), a memory storage circuit <NUM> (which can include volatile or non-volatile electronic memory), a communication circuit <NUM>, and a cryptographic circuit <NUM> (which can include a specialized cryptographic processor and/or data associated with cryptographic functions). Power can be provided from a power supply <NUM> that is external to the data storage element (and could be from a vehicle or another source). The data storage element <NUM> can be connected to the power supply via electrical contacts <NUM>. As represented in <FIG>, the power supply <NUM> is a DC power source, but AC power sources are also contemplated herein. It will be appreciated that in some embodiments a specific data storage element <NUM> may not include all of the components shown and described with respect to <FIG>. In addition, in some embodiments data storage element <NUM> may include additional components beyond what is shown and described with respect to <FIG>.

Components associated with a reader device <NUM> can include one or more of a control circuit <NUM> (which can include a processor, a microcontroller, an ASIC, or the like), a memory storage circuit <NUM> (which can include volatile or non-volatile memory), a communication circuit <NUM>, a cryptographic circuit <NUM> (which can include a specialized cryptographic processor and/or data associated with cryptographic functions), a clock circuit <NUM>, and a location circuit <NUM>. Power can be provided from a power supply <NUM> that is external to the data storage element (and could be from a vehicle or another source). The reader device <NUM> can be connected to the data storage element <NUM> (such as when the filter element is installed in a filter housing) via wires <NUM>.

Various methods are included herein. In some embodiments, a method of providing data to a filtration system in the field is included. The method can include storing operational program data on a filter element, the filter element comprising a filter body; a filter media disposed within the filter body; and a data storage element associated with the filter element. The method can further include installing the filter element within a filter housing. The filter housing can define an interior volume. The filter element can be configured to fit within the interior volume of the filter housing. The method can further include passing the operational program data onto a reader device.

Referring now to <FIG>. a diagram is shown of a method in accordance with various embodiments herein. The method can include an operation including a handshake protocol <NUM>. The method can also include an operation including an authentication protocol <NUM>.

The method can also include operations of passing data from a data storage element associated with a filter element to a reader device (associated with the filter housing or remotely located). In some embodiments, data can be passed in a particular order. By way of example, data that is directly needed for operation of the filtration system, if any, can be transferred first. For example, filter element intrinsic data such as that described above can be transferred <NUM> first in some embodiments. In some embodiments, extrinsic data can be transferred <NUM> next. In some embodiments, operational program data can be transferred <NUM> last.

In some embodiments, reader devices herein can prompt the filter element and/or the data storage element thereon when certain types of data are desired. In some embodiments, certain types of data are automatically provided by the data storage element while other types of data are only provided after receiving a specific prompt for the same. For example, in some embodiments operational program data may only be provided after the filter element receives a specific prompt from a reader device and/or only after the reader device is properly authenticated. Referring now to <FIG>, a diagram is shown of a method in accordance with various embodiments herein. The method can include an operation including a handshake protocol <NUM>. The method can also include an operation including an authentication protocol <NUM>.

The method can also include an operation of passing filter element intrinsic data <NUM> from a data storage element associated with a filter element to a reader device (associated with the filter housing or remotely located). The method can also include an operation of passing extrinsic data <NUM> from a data storage element associated with a filter element to a reader device (associated with the filter housing or remotely located). The method can also include an operation of waiting for a further request from the reader device <NUM>. Assuming such a request is received, the method can also include an operation of passing operational program data <NUM> from a data storage element associated with a filter element to a reader device (associated with the filter housing or remotely located).

The transfer of data from the filter element onto a reader device can be impacted by the outcome of the authentication protocol <NUM>. In some embodiments, if the authentication protocol <NUM> fails, then no data is transferred. However, in some embodiments, some data can be transferred even if the authentication protocol <NUM> fails. For example, filter element intrinsic data <NUM> is provided regardless of whether proper authentication resulted from the authentication protocol <NUM>, but other types of data are held back if the authentication protocol <NUM> fails. In some embodiments, the system can enter a default or baseline operating mode if the authentication protocol <NUM> fails. In some embodiments, the default or baseline operation mode can include the filtration system sending a signal on to other components that it has entered a default or baseline operation mode. In some embodiments, the default or baseline operation mode can include the use of algorithms that are more conservative (e.g., predicting an earlier end-of-life for the filter element and/or shorter servicing intervals) than would be applied if the authentication protocol <NUM> terminated successfully.

In various embodiments, the transfer and/or use of certain types of data, such as operational program data can be contingent based on other data such as dates of revisions and/or version information. For example, information such as a date or version of a carried piece of operational program data such as a software or firmware update can be evaluated before or after transferring the operational program data. In this manner, if the reader device (or other device that would be updated using the operational program data carried) has already received the update or is already operating with a more recent version of the operational program data then the operational program data may not be transferred.

Alternatively, if data that is outdated or otherwise obsolete is transferred, then it may simply be discarded if the reader device (or other device that would be updated using the operational program data carried) has already received the update or is already operating with a more recent version of the operational program data.

Similarly, information such as a date of extrinsic data revision can be evaluated before the extrinsic data in question is actually put to use in calculations. If the extrinsic data revision date is not sufficiently recent or if the currently relied upon extrinsic data has a more recent revision date, then the system can reject the extrinsic data carried by the filter element and rely upon previously obtained extrinsic data and/or default extrinsic data values.

Data can also be evaluated and excluded or included based on additional factors. By way of example, various types of data herein, and particularly extrinsic data can be specific for geography (for example, country and/or region). As such, data herein, such as extrinsic data can be marked with one or more countries and/or regions of validity. This can be evaluated by one or more components of the system based on the current location and/or stored location of the filtration system and/or reader device. If the extrinsic data is not valid based on a country and/or region determination, then the system can reject the extrinsic data carried by the filter element and rely upon previously obtained extrinsic data and/or default extrinsic data values. In some embodiments, multiple versions of data can be carried by a filter element. For example, multiple versions of one or more types of extrinsic data can be carried by a filter element wherein the multiple versions correspond to multiple countries and/or regions. In some embodiments, the system and/or reader device can evaluate the versions and select the correct version and discard the rest. In some embodiments, a country and/or region can be provided to the filter element by the system and/or reader device and then the filter element only transfers the correct version to the system and/or reader device.

In some embodiments, evaluation of a date relating to data carried by a filter element can include comparing the date to a date value provided by an ECU or a date value maintained by a clock circuit that forms part of the filtration system or with which the filtration system conununicates. If the comparison reveals that the date of the data carried by the filter element exceeds a threshold value (such as greater than <NUM>. <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. or <NUM> days old), then the system can initiate one or more of terminating any further transfer of data, discarding the transferred data, reverting operation to a default or baseline mode, or the like.

It will be appreciated that while many embodiments herein are directed to filtration systems and associated filter elements, aspects herein can also be used in conjunction with systems other than filtration systems. For example, embodiments herein can include disposable elements that include a data storage element and move through a supply chain and can be installed within a system in the field to deliver a data payload to the system in the field. Such systems can include those relying upon disposable/consumable elements and can specifically include, but are not limited to, consumer appliances, industrial systems, power systems, and the like. Specific disposable/consumable elements can include batteries, tool blades, physical consumables, and the like.

Claim 1:
A method of providing data to a filtration system in the field comprising:
storing data on a filter element, the filter element comprising
- a filter body (<NUM>);
- a filter media (<NUM>) disposed within the filter body (<NUM>); and
- a data storage element (<NUM>, <NUM>) associated with the filter element for storing said data;
installing the filter element within a filter housing (<NUM>), the filter housing (<NUM>) defining an interior volume, the filter element configured to fit within the interior volume of the filter housing (<NUM>); and
passing the data onto a reader device (<NUM>, <NUM>), characterized in that the data include prioritized and non-prioritized data and wherein the prioritized data are transferred first to the reader device (<NUM>, <NUM>).