Patent Description:
According to an aspect of the present invention, there is provided a monitoring device as claimed in claim <NUM> According to an other aspect of the present invention, there is provided a system for monitoring loading of cargo in a transport vehicle, according to claim <NUM>.

Other aspects of the present invention are provided in dependant claims <NUM> to <NUM>.

In the following description, like reference numbers are used to identify like elements. Furthermore, the drawings are intended to illustrate major features of exemplary embodiments in a diagrammatic manner. The drawings are not intended to depict every feature of actual embodiments nor relative dimensions of the depicted elements, and are not drawn to scale.

The present invention is not limited in any way to the illustrated embodiments. Instead, the illustrated embodiments described below are merely examples of the invention. Therefore, the structural and functional details disclosed herein are not to be construed as limiting the claims. The disclosure merely provides bases for the claims and representative examples that enable one skilled in the art to make and use the claimed inventions. Furthermore, the terms and phrases used herein are intended to provide a comprehensible description of the invention without being limiting.

As used herein, the term "or" refers an inclusive "or" rather than an exclusive "or. " In addition, the articles "a" and "an" as used in the specification and claims mean "one or more" unless specified otherwise or clear from the context to refer the singular form.

The terms "module," "manager," and "unit" refer to hardware, software, or firmware, or a combination thereof.

The instant specification describes an example system of tape agent platforms (also referred to herein as "tape agents") that can be used to implement a low-cost wireless network infrastructure for performing monitoring, tracking, and other logistic functions relating to, for example, parcels, persons, tools, equipment and other physical assets and objects. The tape nodes discussed herein include the features described in <CIT>, titled "Fabricating Multifunction Adhesive Product for Ubiquitous Realtime Tracking", and <CIT>, titled "Wireless Communications and Transducer Based Event Detection Platform"; each of the aforementioned patent and patent application publication are incorporated by reference in their entireties as if fully set forth herein. The example system includes a set of four different types of tape nodes that have different respective functionalities and different respective cover markings that visually distinguish the different tape agent types from one another. Other systems may include fewer than three or more than three different types of tape nodes. In one non-limiting example, the covers of the different tape agent types are marked with different colors (e.g., white, green, and black). In the illustrated examples, the different tape agent types also are distinguishable from one another by their respective wireless communications capabilities and their respective sensing capabilities. The colors discussed above are examples only, any different color, or any combination of colors may be used, for any different categories of tape nodes.

<FIG> is a cross-sectional side view of one example first type (e.g., white) of tape node <NUM> formed as a segment of a flexible adhesive tape product. The first type of tape node <NUM> includes an adhesive layer <NUM>, an optional flexible substrate <NUM> (e.g., a polymer layer), and an optional adhesive layer <NUM> on the bottom surface of the flexible substrate <NUM>. If the bottom adhesive layer <NUM> is present, a release liner (not shown) may be (removably) adhered to the bottom surface of the adhesive layer <NUM>. In some examples, the adhesive layer <NUM> includes an adhesive (e.g., an acrylic foam adhesive) that has a high bond strength that is sufficient to prevent removal of the first type of tape node <NUM> from a surface on which the adhesive layer <NUM> is adhered without destroying the physical or mechanical integrity of the first type of tape node <NUM> and/or one or more of its constituent components. In some examples, the optional flexible substrate <NUM> is implemented as a prefabricated adhesive tape that includes the adhesive layers <NUM>, <NUM> and the optional release liner. In other examples, the adhesive layers <NUM>, <NUM> are applied to the top and bottom surfaces of the flexible substrate <NUM> during the fabrication of the adhesive tape platform. The adhesive layer <NUM> bonds the flexible substrate <NUM> to a bottom surface of a flexible circuit <NUM>, that includes one or more wiring layers (not shown) that connect the processor <NUM>, a low power wireless communication interface <NUM> (e.g., a Zigbee, Bluetooth® Low Energy (BLE) interface, or other low power communication interface), a clock and/or a timer circuit <NUM>, transducing and/or energy harvesting component(s) <NUM> (if present), the memory <NUM>, and other components in a device layer <NUM> to each other and to the energy storage device <NUM> and, thereby, enable the transducing, tracking and other functionalities of the first type of tape node <NUM>. The memory <NUM> may store a device identifier (ID) <NUM> that uniquely identifies the tape node <NUM>, and software <NUM> that includes machine-readable instructions that are executable by the processor <NUM> to cause the processor to implement functionality described herein. The low power wireless communication interface <NUM> typically includes an antenna and a wireless circuit.

<FIG> shows a cross-sectional side view of a portion of an example second type (e.g., green) of tape node <NUM> formed as a segment of a flexible adhesive tape product. The second type of tape node <NUM> is similar to the first type of tape node <NUM> shown in <FIG>, but differs by the inclusion of a medium power communication interface <NUM>' (e.g., a LoRa interface) in addition to the low power communications interface <NUM>' that is present in the first type of tape node <NUM>. The medium power communication interface <NUM>' has longer communication range than the low power communication interface <NUM>'. In some examples, one or more other components of the second type of tape node <NUM> differ from components of the first type of tape node <NUM> in functionality or capacity (e.g., larger power source).

<FIG> shows a cross-sectional side view of a portion of an example third type (e.g., black) of tape node <NUM> formed as a segment of a flexible adhesive tape product. The third type of tape node <NUM> is similar to the second type of tape node <NUM> of <FIG>, but differs by further including a high-power communications interface <NUM>" (e.g., a cellular interface; e.g., GSM/GPRS). The high-power communication range of the high-power communications interface <NUM>" provides global coverage to available infrastructure (e.g. the cellular network). In certain embodiments, one or more other components of the third type of tape node <NUM> differ from those of the second type of tape node <NUM> in functionality or capacity (e.g., larger energy source).

<FIG> shows a cross-sectional side view of a portion of an example fourth type (e.g., black) of tape node <NUM> formed as a segment of a flexible adhesive tape product. The fourth type of tape node <NUM> is similar to the third type of tape node <NUM> but differs by further including an Automatic Dependent Surveillance - Broadcast (ADS-B) out receiver <NUM>‴ for receiving ADS-B out signals from aircraft, other vehicles, items, and objects. For example, each ADS-B out signal defines a current location (e.g., based on GNSS determined coordinates) of an identified transport vehicle (e.g., an aircraft).

<FIG> show examples in which the cover <NUM>, <NUM>', <NUM>", <NUM>‴ (e.g., a flexible layer) of the flexible adhesive tape platform includes one or more interfacial regions <NUM>, <NUM>', <NUM>", <NUM>‴ positioned over one or more of the transducers <NUM>, <NUM>', <NUM>", <NUM>‴. In examples, one or more of the interfacial regions <NUM>, <NUM>', <NUM>", <NUM>‴ have features, properties, compositions, dimensions, and/or characteristics that are designed to improve the operating performance of the platform for specific applications. In some examples, the flexible adhesive tape platform includes multiple interfacial regions <NUM>, <NUM>', <NUM>", <NUM>‴ over respective transducers <NUM>, <NUM>', <NUM>", <NUM>"', which may be the same or different depending on the target applications. Example interfacial regions include an opening, an optically transparent window, and/or a membrane located in the interfacial regions <NUM>, <NUM>', <NUM>", <NUM>‴ of the cover <NUM>, <NUM>', <NUM>", <NUM>‴ that is positioned over the one or more transducers and/or energy harvesting components <NUM>. Additional details regarding the structure and operation of example interfacial regions <NUM>, <NUM>', <NUM>", <NUM>‴ are described in <CIT>, and <CIT>, each of which are incorporated herein by reference in their entireties as if fully set forth.

In some examples, a flexible polymer layer <NUM>, <NUM>', <NUM>", <NUM>"' encapsulates the device layer <NUM> and thereby reduces the risk of damage that may result from the intrusion of contaminants and/or liquids (e.g., water) into the device layer <NUM>, <NUM>', <NUM>", <NUM>"'. The flexible polymer layer <NUM>, <NUM>', <NUM>", <NUM>‴ also planarizes the device layer <NUM>. This facilitates optional stacking of additional layers on the device layer <NUM>, <NUM>', <NUM>", <NUM>‴ and also distributes forces generated in, on, or across the tape nodes <NUM>, <NUM>, <NUM> so as to reduce potentially damaging asymmetric stresses that might be caused by the application of bending, torqueing, pressing, or other forces that may be applied to the tape nodes <NUM>, <NUM>, <NUM> during use. In the illustrated example, a cover <NUM>, <NUM>', <NUM>", <NUM>‴ is bonded to the planarizing flexible polymer layer <NUM>, <NUM>', <NUM>", <NUM>‴ by an adhesive layer (not shown).

The cover <NUM>, <NUM>', <NUM>', 90ʺʺ and the flexible substrate <NUM> may have the same or different compositions depending on the intended application. In some examples, one or both of the cover <NUM>, <NUM>', <NUM>", <NUM>‴ and the flexible substrate <NUM>, <NUM>', <NUM>", <NUM>‴ include flexible film layers and/or paper substrates, where the film layers may have reflective surfaces or reflective surface coatings. Example compositions for the flexible film layers include polymer films, such as polyester, polyimide, polyethylene terephthalate (PET), and other plastics. The optional adhesive layer on the bottom surface of the cover <NUM>, <NUM>', <NUM>", <NUM>‴ and the adhesive layers <NUM>, <NUM>', <NUM>", <NUM>, <NUM>', <NUM>", <NUM>‴ on the top and bottom surfaces of the flexible substrate <NUM>, <NUM>', <NUM>" typically include a pressure-sensitive adhesive (e.g., a silicon-based adhesive). In some examples, the adhesive layers are applied to the cover <NUM> and the flexible substrate <NUM>, <NUM>', <NUM>", <NUM>‴ during manufacture of the adhesive tape platform (e.g., during a roll-to-roll or sheet-to-sheet fabrication process). In other examples, the cover <NUM>, <NUM>', <NUM>" may be implemented by a prefabricated single-sided pressure-sensitive adhesive tape and the flexible substrate <NUM> may be implemented by a prefabricated double-sided pressure-sensitive adhesive tape; both kinds of tape may be readily incorporated into a roll-to-roll or sheet-to-sheet fabrication process. In some examples, the flexible substrate <NUM>, <NUM>', <NUM>", <NUM>‴ is composed of a flexible epoxy (e.g., silicone).

In some examples, the energy storage device <NUM>, <NUM>', <NUM>', <NUM>"" is a flexible battery that includes a printed electrochemical cell, which includes a planar arrangement of an anode and a cathode and battery contact pads. In some examples, the flexible battery may include lithium-ion cells or nickel-cadmium electro-chemical cells. The flexible battery typically is formed by a process that includes printing or laminating the electro-chemical cells on a flexible substrate (e.g., a polymer film layer). In some examples, other components may be integrated on the same substrate as the flexible battery. For example, the low power wireless communication interface <NUM>, <NUM>', <NUM>", <NUM>‴ and/or the processor(s) <NUM>, <NUM>', <NUM>", <NUM>‴ may be integrated on the flexible battery substrate. In some examples, one or more of such components also (e.g., the flexible antennas and the flexible interconnect circuits) may be printed on the flexible battery substrate.

Tape nodes <NUM>, <NUM>, <NUM>, and <NUM> may establish communication with the same type of tape node, and with other types of tape node. For example, a first tape node may broadcast advertisement packets in accordance with a particular wireless communication protocol such that they may be received by other tape nodes. When a second tape node receives one of the advertisement packets, the second tape node may transmit a scan link request. In response to the scan link request, the first tape node may establish a communication link with the second tape node (e.g., by allocating a data channel).

<FIG> is a schematic diagram illustrating one example system <NUM> for monitoring loading of assets in logistic containers <NUM> (e.g., cargo) onto a transport vehicle <NUM>. In the example of <FIG>, the transport vehicle <NUM> is an aircraft; however, transport vehicle <NUM> may represent other types of transportation including ground vehicles, trucks, trains, water vehicles, ships, air vehicles, and any other vehicle used to transport freight or cargo. The logistic container <NUM> may represent any type of asset (e.g., object(s), item(s), cargo, etc.), or container thereof, being transported. For example, logistic container <NUM> may represent one or more of a package, a parcel, a box, and a unit load device.

The transport vehicle <NUM> includes a cargo hold <NUM> into which the logistic containers <NUM> are loaded by a cargo loader <NUM>, such as a conveyer device for example, through an access port (e.g., a door or hatch). Each logistic container <NUM> has at least one wireless tracking tag <NUM>, which may be implemented as one of the first, second, third and fourth types of tape node <NUM>, <NUM>, <NUM>, and <NUM> of <FIG>, and <FIG>, respectively, and may take the form of a tag, tape, and/or label. For purpose of illustration, wireless tracking tag <NUM> is assumed to represent tape node <NUM> of <FIG>. <FIG> is an enlarged view of the cargo hold <NUM>, the cargo loader <NUM>, the logistic containers <NUM>, the wireless tracking tags <NUM>, and the wireless monitoring device <NUM>. <FIG> are best viewed together with the following description.

The wireless tracking tag <NUM> is a digital computing device that includes energy storage <NUM> (e.g., a battery), processor <NUM>, memory <NUM> that includes software <NUM> (e.g., machine-readable instructions) and a tracking identifier <NUM> that uniquely identifies the wireless tracking tag <NUM>, and a wireless communications interface <NUM>.

The system <NUM> also includes a server <NUM>, such as a cloud based computer server that is remote from the wireless monitoring device <NUM>, that communicates with the wireless monitoring device <NUM> over a wireless network <NUM> (e.g., a local WAN, the Internet, etc.). Server <NUM> may represent the example computer apparatus <NUM> shown in <FIG>. The server <NUM> may include a manifest <NUM> that may be represented as a table (e.g., stored as data <NUM> of memory <NUM>) or a list that defines, for each logistic contains scheduled to be conveyed to the cargo hold <NUM> of the transport vehicle <NUM> and fitted with at least one wireless tracking tag <NUM>, the corresponding tracking identifier of the at least one wireless tracking tag <NUM>.

The wireless monitoring device <NUM> is a digital computing device. In certain embodiments, wireless monitoring device <NUM> may be implemented as one of the first, second, third and fourth types of tape node <NUM>, <NUM>, <NUM>, and <NUM> of <FIG>, and <FIG>, respectively, and may take the form of a tag, tape, and/or label. However, wireless monitoring device <NUM> may take other forms and be based on other similar devices without departing from the scope hereof. For purpose of illustration, wireless monitoring device <NUM> is assumed to represent the third type of tape node <NUM> of <FIG> and includes energy storage <NUM>" (e.g., a battery), processor <NUM>", memory <NUM>" that includes software <NUM>" (e.g., machine-readable instructions) and monitoring device identifier <NUM>" that uniquely identifies the wireless monitoring device <NUM>, and one or more wireless communications interfaces <NUM>",<NUM>", and <NUM>".

In one example of operation, the wireless monitoring device <NUM> may determine its current location and send it to the server <NUM>. In response, the server <NUM> may determine a closest transport vehicle <NUM> to the wireless monitoring device <NUM>, and then send one or both of a unique universal identifier (UUID) of the transport vehicle <NUM> (e.g., a unique International Civil Aviation Organization address that uniquely identifies the aircraft), and the manifest <NUM>. The wireless monitoring device <NUM> may receive, via the network <NUM>, the UUID and/or the manifest <NUM> from the server <NUM> and store the UUID and/or the manifest <NUM> in its memory, such that the wireless monitoring device <NUM> is configured with the manifest <NUM> prior to loading of the logistic containers <NUM> into the cargo hold <NUM>.

In certain embodiments, where the wireless monitoring device <NUM> is positioned within a cargo hold <NUM> of the transport vehicle <NUM>, the wireless monitoring device <NUM> may broadcast a beacon signal, at intervals, that includes the UUID of the transport vehicle, such that any wireless tracking tags <NUM> within the cargo hold <NUM> may determine whether they are on the correct transport vehicle. For example, at least one wireless tracking tag <NUM> may be preconfigured with the UUID of the transport vehicle that it is intended to travel on, and may thereby determine whether it is on the correct transport vehicle by comparing the UUID received in the beacon signal to the UUID stored in its memory, generating an alert when the UUIDs do not match.

<FIG> is a flowchart illustrating one example method <NUM> for installing and operating at least part of the system <NUM> of <FIG>. Block <NUM> and <NUM> of method <NUM> are implemented within the wireless monitoring device <NUM>, for example. Wireless tracking tags <NUM> are attached to respective ones of logistic containers <NUM> intended for transport by the transport vehicle (<FIG>, block <NUM>). In one example of block <NUM>, one wireless tracking tag <NUM> is attached to each logistic container <NUM> prior to loading the logistic containers <NUM> into the cargo hold <NUM>. In another example of block <NUM>, one wireless tracking tag <NUM> is attached to one logistic container <NUM> of a group of logistic containers (e.g., not all logistic containers ha a wireless tracking tag) prior to loading the logistic containers <NUM> into the cargo hold <NUM>. In another example of block <NUM>, the wireless tracking tags <NUM> are distributed randomly among the logistic containers <NUM> prior to loading the logistic containers <NUM> into the cargo hold <NUM>.

The wireless monitoring device <NUM> is affixed to a structural, non-moving portion, of the cargo loader <NUM> (<FIG>, block <NUM>). In one example of block <NUM>, the wireless monitoring device <NUM> is attached to a non-moving portion of the cargo loader <NUM> that is proximate the path of the logistic containers <NUM> as they are being loaded into the cargo hold <NUM>.

In one example of operation, the wireless monitoring device <NUM> communicates with each of the wireless tracking tags <NUM> as it is loaded into the cargo hold <NUM> and receives the corresponding tracking identifier <NUM> of the wireless tracking tag <NUM> (<FIG>, block <NUM>). The wireless monitoring device <NUM> identifies discrepancies between the tracking identifiers received from the wireless tracking tags <NUM> attached to the logistic containers <NUM> being conveyed to the cargo hold <NUM> of the transport vehicle <NUM> and the tracking identifiers listed in the manifest <NUM> to determine discrepancies between the cargo expected to be loaded and the cargo actually loaded (<FIG>, block <NUM>). In one example, where the manifest <NUM> lists tracking identifier "T24" as expected to be loaded into cargo hold <NUM>, and, when loading is complete, the tracking identifier "T24" was not received by the wireless monitoring device <NUM>, the wireless monitoring device <NUM> determines that the logistic container <NUM> corresponding to the wireless tracking tag <NUM> with the tracking identifier "T24" was not loaded and is therefore a discrepancy. In another example, where the manifest <NUM> does not list tracking identifier "T87" as expected to be loaded into cargo hold <NUM>, and, when the wireless monitoring device <NUM> receives the tracking identifier "T87" from one wireless tracking tag <NUM> as it is conveyed into the cargo hold <NUM>, the wireless monitoring device <NUM> determines that the logistic container <NUM> corresponding to the wireless tracking tag <NUM> with the tracking identifier "T87" was loaded in error and is therefore a discrepancy.

In some embodiments, a distance of a wireless tracking tag <NUM> relative to the wireless monitoring device <NUM> is estimated based on a signal strength of a communication link (e.g., a Bluetooth communication connection) between the wireless monitoring device <NUM> and the wireless tracking tag <NUM>. In the example of <FIG>, as the asset <NUM> with the wireless tracking tag <NUM> is conveyed into the cargo hold <NUM>, the signal strength of wireless signals received via the communication link between the wireless tracking tag <NUM> and the wireless monitoring device <NUM> reduces. Accordingly, the system <NUM> (e.g., the wireless monitoring device <NUM>) determines that the asset <NUM> with the attached wireless tracking tag <NUM> is being conveyed to the cargo hold <NUM> based on the known location of the wireless monitoring device <NUM> and the trend of the signal strength over time. In another example, the system <NUM> (e.g., one of the wireless monitoring device <NUM> and the wireless tracking tag <NUM> attached to the asset <NUM>) may determine that an error or deviation in the loading of the asset <NUM> with the attached wireless tracking tag <NUM> has occurred when the signal strength abruptly decreases or abruptly increases. An abrupt increase or decrease may be different based on the given application, but those of skill in the art understand that "abrupt" is defined by a change over a predefined threshold that is representative of the asset <NUM> not being conveyed into the cargo hold. The system <NUM> (e.g., one of the wireless monitoring device <NUM>, the wireless tracking tag <NUM>, another tape node forming the system <NUM>, or some combination thereof) may initiate an alert when the error or deviation is detected. For example, the wireless monitoring device <NUM> may detect an abrupt increase in the signal strength indicative of the asset <NUM> falling off the cargo loader <NUM> and landing in a location closer to the wireless monitoring device <NUM> than its previous position on the cargo loader <NUM>. The wireless monitoring device <NUM> may broadcast an alert to other nodes forming the system <NUM> (e.g., another wireless tracking tag <NUM>, another wireless monitoring device <NUM>, a client device, a smartphone or device of a human operator, and/or the server <NUM>). In some embodiments, the wireless monitoring device <NUM> broadcasts an audio alert to notify any nearby human operators.

<FIG> is a flowchart illustrating one example method <NUM> installing and operating at least part of the system <NUM> of <FIG>. Blocks <NUM> and <NUM> of method <NUM> are implemented in wireless monitoring device <NUM>, for example. A wireless monitoring device is affixed to a structural portion (e.g., a stationary portion, non-moving portion, such as the ceiling, wall, door frame, etc.) of a cargo hold of a transport vehicle (<FIG>, block <NUM>). In one example of block <NUM>, wireless monitoring device <NUM> is attached to an internal ceiling of the cargo hold <NUM>. In another example of block <NUM>, wireless monitoring device <NUM> is attached to a door post of the cargo hold <NUM>. The wireless monitoring device <NUM> may be an embodiment of a tape node, for example, one of tape nodes <NUM>, <NUM>, <NUM>, <NUM> shown in <FIG>, according to some embodiments.

Wireless tracking tags <NUM> are attached to respective logistic containers <NUM> intended for transport by a transport vehicle <NUM> (<FIG>, block <NUM>). In one example of block <NUM>, one wireless tracking tag <NUM> is attached to each logistic container <NUM> prior to loading the logistic containers <NUM> into the cargo hold <NUM>. In another example of block <NUM>, one wireless tracking tag <NUM> is attached to one logistic container <NUM> of a group of logistic containers (e.g., not all logistic containers ha a wireless tracking tag) prior to loading the logistic containers <NUM> into the cargo hold <NUM>. In another example of block <NUM>, the wireless tracking tags <NUM> are distributed randomly among the logistic containers <NUM> prior to loading the logistic containers <NUM> into the cargo hold <NUM>.

In operation, the wireless monitoring device <NUM> communicates with each of the wireless tracking tags <NUM> as it is loaded into the cargo hold <NUM> and received the corresponding tracking identifier of the wireless tracking tag <NUM> (<FIG>, block <NUM>). The wireless monitoring device <NUM> identifies discrepancies between the tracking identifiers received from the wireless tracking tags <NUM> attached to the logistic containers <NUM> being conveyed to the cargo hold <NUM> of the transport vehicle <NUM> and the tracking identifiers listed in the manifest <NUM> to determine discrepancies between the cargo expected to be loaded and the cargo actually loaded (<FIG>, block <NUM>). In one example, where the manifest <NUM> lists tracking identifier "T24" as expected to be loaded into cargo hold <NUM>, and, when loading is complete, the tracking identifier "T24" was not received by the wireless monitoring device <NUM>, the wireless monitoring device <NUM> determines that the logistic container <NUM> corresponding to the wireless tracking tag <NUM> with the tracking identifier "T24" was not loaded and is therefore a discrepancy. In another example, where the manifest <NUM> does not list tracking identifier "T87" as expected to be loaded into cargo hold <NUM>, and, when the wireless monitoring device <NUM> receives the tracking identifier "T87" from one wireless tracking tag <NUM> as it is conveyed into the cargo hold <NUM>, the wireless monitoring device <NUM> determines that the logistic container <NUM> corresponding to the wireless tracking tag <NUM> with the tracking identifier "T87" was loaded in error and is therefore a discrepancy.

<FIG> is a flowchart illustrating one example method <NUM> for monitoring a shipment that uses a plurality of logistic containers <NUM> that are being transported in a cargo hold <NUM> of a transport vehicle <NUM>. Method <NUM> is implemented in at least one wireless tracking tag <NUM>, for example. Method <NUM> may also be implemented by more than one wireless tracking tag, using distributed processing, for example. Method <NUM> may also be implemented by the wireless monitoring device <NUM>, such as when the wireless monitoring device <NUM> is within the cargo hold <NUM>.

In one example scenario, wireless tracking tags <NUM> are used by the transportation company to track logistic containers <NUM>. In another example scenario, wireless tracking tags <NUM> are used by the company making a shipment and may be attached to each package in the company's shipment. For each scenario, operation of the wireless tracking tags <NUM> is similar, and is described below in detail. In this example, the wireless tracking tag <NUM> performing method <NUM> is referred to as the first wireless tracking tag <NUM> to distinguish it from other wireless tracking tags for clarity of description; however, any of the wireless tracking tags <NUM> conveyed into the cargo hold <NUM> may perform the method <NUM>, and thus the method <NUM> may be performed by multiple wireless tracking tags <NUM>, at different times and/or concurrently. Each wireless tracking tag <NUM> attached to logistic containers <NUM> being shipped together, or attached to packages being shipped together, may be configured with a threshold number that defines the total number of wireless tracking tags <NUM> used for that collective shipment, and may also be configured with a date and time that defines a scheduled event of interest, such as a time related to the departure of the transport vehicle <NUM> (e.g., <NUM> minutes before the scheduled departure time). Advantageously, each wireless tracking tag <NUM> may perform method <NUM> to determine when to trigger an alarm. In certain embodiments, each wireless tracking tag <NUM> attached to assets of a collective shipment may be configured with a group manifest that identifies each of the wireless tracking tags in the collective shipment. Particularly, one or more of the wireless tracking tags <NUM> may then determine when any one, or more, of the wireless tracking tags <NUM> in the group manifest cannot be contacted, indicating that the corresponding asset may be missing.

The first wireless tracking tag <NUM> may identify a logistic container load event by determining that it has been loaded into the cargo hold <NUM> of the transport vehicle <NUM>. For example, based upon interrogation by wireless monitoring device <NUM>, the first wireless tracking tag <NUM> may determine that is has been conveyed into the cargo hold <NUM>. In response to the logistic container load event, the first wireless tracking tag <NUM> may indicate its presence by transmitting, at intervals, a wireless signal (e.g., a broadcast advertisement packet) that includes authentication data (<FIG>, block <NUM>). In certain embodiments, the wireless tracking tag <NUM> may use a different wireless protocol (e.g., a short-range protocol, such as Bluetooth). Other wireless tracking tags <NUM> (or the wireless monitoring device <NUM>) that are within wireless communication range of the first wireless tracking tag <NUM> may respond to receiving the wireless signal, when the authentication data is validated, by transmitting a scan link request to establish communication with the first wireless tracking tag <NUM>, over a data channel for example. The authentication data may be determined as valid only when it matches authentication data preloaded into the other wireless tracking tag. When the wireless tracking tag <NUM> receiving the wireless signal cannot validate the authentication data, the wireless tracking tag <NUM> does not respond to the wireless signal. Advantageously, the authentication data may be selected to group the wireless tracking tags <NUM> according to the cargo being shipped, where the same authentication data is used by wireless tracking tags <NUM> of the same shipment. The first wireless tracking tag <NUM> may receive the tracking identifier of the other wireless tracking tag <NUM>. (<FIG>, block <NUM>).

The first wireless tracking tag <NUM> repeats the transmission, at intervals, of the wireless signal with authentication data, to establish communications connections with other wireless tracking tags <NUM> that are within wireless range, and to receive their corresponding tracking identifiers (<FIG>, block <NUM>).

In certain embodiments, each of the wireless tracking tags <NUM> transmits, at intervals, a wireless signal including its unique identifier and the authentication data. The first wireless tracking tag <NUM> tracks the different unique identifiers received in these wireless signals with validated authentication data to determine ones of the wireless signals that correspond to the same collective shipment. Over time, the first wireless tracking tag <NUM> learns the unique identifiers of the other wireless tracking tags <NUM> in proximity and may thereby determine, based on the group manifest, whether any assets of the collective shipment are missing.

When the first wireless tracking tag <NUM> determines that fewer than the threshold number of different wireless tracking tags have responded to the wireless signal at the scheduled event, the first wireless tracking tag <NUM> triggers an alarm (<FIG>, block <NUM>). In certain embodiments, the first wireless tracking tag <NUM> may detect when a particular one of the wireless tracking tags identified in the group manifest has not responded. In some embodiments, the wireless tracking tag <NUM> stores program instructions to trigger an alarm if the total number of other wires tags that accept the authentication credentials is less than the threshold number before the scheduled event occurs.

<FIG> is a diagrammatic view illustrating the use of one or more ADS-B out signals <NUM> to determine a current position of a logistic container <NUM>. In this embodiment, a wireless tracking tag <NUM> is attached to the logistic container <NUM> and represents the fourth type of tape node <NUM> of <FIG>. In this example, the logistic container <NUM> is being loaded into a cargo hold <NUM> of an aircraft <NUM>. Three ADS-B out signals <NUM>(<NUM>)-(<NUM>) are transmitted by three different aircraft <NUM>, <NUM>, <NUM>, respectively, each of which may be on the ground or in the air. Each of the ADS-B out signals <NUM>(<NUM>)-(<NUM>) includes a current Global Navigation Satellite System (GNSS) determined location (e.g., geographic coordinates, height, etc.) and a unique identifier (e.g., a unique International Civil Aviation Organization address that uniquely identifies the aircraft), thereby defining a location of, and identifying, each of the corresponding aircraft <NUM>, <NUM>, <NUM>. In the example of <FIG>, the wireless tracking tag <NUM> receives three different ADS-B out signals <NUM>(<NUM>)-(<NUM>) determining a current position (location) of the logistic container <NUM>.

<FIG> is a flowchart illustrating one example method <NUM> for determining the current position of the logistic container <NUM> of <FIG> by triangulating the received ADS-B out signals <NUM> and selecting one of the ADS-B out signals <NUM> that corresponds to the aircraft carrying the logistic container <NUM>. Method <NUM> is implemented by the wireless tracking tag <NUM> affixed to the logistic container <NUM> for example. The wireless tracking tag <NUM> receives ADS-B out signals <NUM> transmitted by different aircraft, each signal defining a respective location and unique identifier (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> receives ADS-B out signal <NUM>(<NUM>) transmitted by aircraft <NUM>, receives ADS-B out signal <NUM>(<NUM>) transmitted by aircraft <NUM>, and receives ADS-B out signal <NUM>(<NUM>) transmitted by aircraft <NUM>. A respective signal strength value is determined by the wireless tracking tag <NUM> for each of the ADS-B out signals <NUM> received (<FIG>, block <NUM>). In one example of block <NUM>, ADS-B out receiver <NUM>‴ of the wireless tracking tag <NUM> determines a received signal strength indicator (RSSI) of the ADS-B out signal <NUM> as the signal is received. In other embodiments, the signal strength value for the ADS-B out signal <NUM> is determined by other components of the wireless tracking tag <NUM>.

The wireless tracking tag <NUM> triangulates its current location based on both the corresponding signal strength values of each received ADS-B out signal <NUM> and the corresponding location included in the ADS-B out signal (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> determines its current locations by triangulation using the signal strength values and locations of each aircraft <NUM>, <NUM>, and <NUM> determined from ADS-B out signals <NUM>(<NUM>)-(<NUM>), respectively. The wireless tracking tag <NUM> selects the ADS-B out signal <NUM> containing the location that is nearest to the determined location of the wireless tracking tag <NUM> (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> determines that the ADS-B out signal <NUM>(<NUM>) includes the location that is nearest to the triangulated current location of the wireless tracking tag <NUM>. Associate the location of the logistic container <NUM> with the location included in the selected ADS-B out signal (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> uses the location received in ADS-B out signal <NUM>(<NUM>) as the location of the logistic container <NUM>.

<FIG> is a flowchart illustrating one example method <NUM> for determining the current position of the logistic container <NUM> of <FIG> by selecting a one of the ADS-B out signals <NUM> that corresponds to the aircraft carrying the logistic container <NUM>. Method <NUM> is implemented by the wireless tracking tag <NUM> affixed to the logistic container <NUM> for example. The wireless tracking tag <NUM> receives ADS-B out signals <NUM> transmitted by different aircraft, each signal defining a respective location and unique identifier (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> receives ADS-B out signal <NUM>(<NUM>) transmitted by aircraft <NUM>, receives ADS-B out signal <NUM>(<NUM>) transmitted by aircraft <NUM>, and receives ADS-B out signal <NUM>(<NUM>) transmitted by aircraft <NUM>. A respective signal strength value is determined by the wireless tracking tag <NUM> for each of the ADS-B out signals <NUM> received (<FIG>, block <NUM>). The ADS-B out signal with the highest signal strength value is selected (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> selects the ADS-B out signal <NUM>(<NUM>) as having the strongest RSSI value, as compared to RSSI values for ADS-B out signals <NUM>(<NUM>) and <NUM>(<NUM>). Associate the location of the logistic container <NUM> with the location included in the selected ADS-B out signal (<FIG>, block <NUM>). In one example of block <NUM>, the wireless tracking tag <NUM> determines that the logistic container <NUM> (and thus the wireless tracking tag <NUM>) is being transported by the aircraft <NUM> and uses the location received in ADS-B out signal <NUM>(<NUM>) as the location of the logistic container <NUM>.

As described above, the wireless tracking tag <NUM> may triangulate its location from three different ADS-B out signals. The determines location thereby defines the location of the asset to which the wireless tracking tag <NUM> is attached. Prior to loading of the asset onto an aircraft, the determined location of the wireless tracking tag <NUM> may indicate when the asset is not near the aircraft designated for transporting the asset. For example, where the assets is designated for transport by transport vehicle <NUM> (<FIG>), which is currently being loaded, and the determined location of the corresponding wireless tracking tag <NUM> indicates that the assets is no near to the aircraft, the system <NUM> may generate an alert. Advantageously, the use of triangulation may locate the asset (wireless tracking tag <NUM>) prior to loading onto the aircraft which may identify incorrect loading before it occurs. In another example, the use of triangulation may define a location of the asset within the aircraft after loading. For example, the triangulated location may indicate which part of the plane, relative to the cockpit (or some other central location), the asset is in. In another example, the triangulated location may indicate that the asset is outside of the transportation vehicle <NUM>, which is about to depart, the wireless tracking tag <NUM> may cause system <NUM> to generate an alert indicating that the asset has not been loaded as expected. Further, if the location of the asset is determined (by the wireless tracking tag <NUM>) to be at the airport still, but the location of the transport vehicle expected to carry the asset has left the airport, system <NUM> may determine that the asset missed its flight.

Advantageously, the use of triangulation with the ADS-B out signals provides an additional metric to use of ADS-B out signal tracking of aircraft for improved tracking of assets and for identifying transportation anomalies.

<FIG> shows an example embodiment of computer apparatus that may be used to implement one or more of the computing systems (e.g., server <NUM> of <FIG>) described in this specification. The computer apparatus <NUM> includes a processing unit <NUM>, a system memory <NUM>, and a system bus <NUM> that couples the processing unit <NUM> to the various components of the computer apparatus <NUM>. The processing unit <NUM> may include one or more data processors, each of which may be in the form of any one of various commercially available computer processors. The system memory <NUM> includes one or more computer-readable media that typically are associated with a software application addressing space that defines the addresses that are available to software applications. The system memory <NUM> may include a read only memory (ROM) that stores a basic input/output system (BIOS) that contains start-up routines for the computer apparatus <NUM>, and a random-access memory (RAM). The system bus <NUM> may be a memory bus, a peripheral bus or a local bus, and may be compatible with any of a variety of bus protocols, including PCI, VESA, Microchannel, ISA, and EISA. The computer apparatus <NUM> also includes a persistent storage memory <NUM> (e.g., a hard drive, a floppy drive, a CD ROM drive, magnetic tape drives, flash memory devices, and digital video disks) that is connected to the system bus <NUM> and contains one or more computer-readable media disks that provide non-volatile or persistent storage for data, data structures and computer-executable instructions.

A user may interact (e.g., input commands or data) with the computer apparatus <NUM> using one or more input devices <NUM> (e.g. one or more keyboards, computer mice, microphones, cameras, joysticks, physical motion sensors, and touch pads). Information may be presented through a graphical user interface (GUI) that is presented to the user on a display monitor <NUM>, which is controlled by a display controller <NUM>. The computer apparatus <NUM> also may include other input/output hardware (e.g., peripheral output devices, such as speakers and a printer). The computer apparatus <NUM> connects to other network nodes through a network adapter <NUM> (also referred to as a "network interface card" or NIC).

A number of program modules may be stored in the system memory <NUM>, including application programming interfaces <NUM> (APIs), an operating system (OS) <NUM> (e.g., the Windows® operating system available from Microsoft Corporation of Redmond, Washington U. ), software applications <NUM> including one or more software applications programming the computer apparatus <NUM> to perform one or more of the steps, tasks, operations, or processes of the hierarchical classification systems described herein, drivers <NUM> (e.g., a GUI driver), network transport protocols <NUM>, and data <NUM> (e.g., input data, output data, program data, a registry, and configuration settings).

Examples of the subject matter described herein, including the disclosed systems, methods, processes, functional operations, and logic flows, can be implemented in data processing apparatus (e.g., computer hardware and digital electronic circuitry) operable to perform functions by operating on input and generating output. Examples of the subject matter described herein also can be tangibly embodied in software or firmware, as one or more sets of computer instructions encoded on one or more tangible non-transitory carrier media (e.g., a machine-readable storage device, substrate, or sequential access memory device) for execution by data processing apparatus.

The details of specific implementations described herein may be specific to particular embodiments of particular inventions and should not be construed as limitations on the scope of any claimed invention. For example, features that are described in connection with separate embodiments may also be incorporated into a single embodiment, and features that are described in connection with a single embodiment may also be implemented in multiple separate embodiments. In addition, the disclosure of steps, tasks, operations, or processes being performed in a particular order does not necessarily require that those steps, tasks, operations, or processes be performed in the particular order; instead, in some cases, one or more of the disclosed steps, tasks, operations, and processes may be performed in a different order or in accordance with a multi-tasking schedule or in parallel.

Claim 1:
A monitoring device (<NUM>) positioned to monitor a cargo hold (<NUM>) of a transport vehicle (<NUM>), comprising:
an RF transceiver implementing a first wireless communication protocol;
a processor; and
memory storing machine-readable instructions that, when executed by the processor, cause the processor to:
transmit a location of the monitoring device to a server (<NUM>) of a tracking system including the monitoring device;
receive, in response, an identifier of the transport vehicle (<NUM>) nearest to the wireless monitoring device (<NUM>);
receive a wireless signal containing a tracking identifier from a wireless tracking tag (<NUM>) attached to a logistic container (<NUM>) being conveyed into the cargo hold (<NUM>) of the transport vehicle (<NUM>);
determine a signal strength of the wireless signal; and
transmit an alert to a network service when the signal strength indicates that the wireless tracking tag (<NUM>) was not successfully loaded into the cargo hold (<NUM>) of the transport vehicle (<NUM>).