Method for detecting environmental anomalies and initiating enhanced automatic response

Abstract

An improved system detects environmental anomalies in a shipping container and initiates mediation responses through generated hierarchical alarm notifications. The system includes a sensor-based ID node associated with a package within a container, and a command node mounted to the container in communication with the ID node and an external transceiver on a vehicle that shifts the container. The command node is programmed to detect sensor data from the ID node; comparing the sensor data with a wrapping environment threshold in the context data related to each ID node; detecting an environmental anomaly when the comparison indicates that the environmental condition of the at least one parcel exceeds its environmental threshold; responsively generating hierarchical alarm notifications identifying mediation recipients and mediation actions, and establishing a mediation response priority based on the comparison; and transmitting the hierarchical alert notification to the transceiver unit to initiate a mediation response associated with the mediation action.

Description

[0001] Priority application

[0002] This application hereby claims priority to the relevant U.S. provisional patent application number 62 / 735,075 entitled "Improved Systems, Apparatus, and Methods for Detecting an Environmental Anomaly and Initiating an Enhanced Automatic Response Using Elements of a Wireless Node Network". Technical Field

[0003] This disclosure generally relates to systems, apparatus, and methods in the field of detecting environmental anomalies on containers and responsively initiating improved mediation responses. In particular, this disclosure relates to various aspects involving systems, apparatus, and methods for improving environmental anomaly detection, associated enhanced hierarchical alarms as part of a mediation response, and the use of one or more elements of an adaptive, context-aware wireless node network to initiate hierarchical type mediation responses to such environmental anomalies. Background Technology

[0004] The transport of goods, objects, or materials (whether the goods, objects, or materials are packaged in packaging materials or shipped without packaging materials, and are uniformly and generally referred to herein as "parcels") is an important part of commerce. In some cases, the types of goods transported may involve those that are corrosive, flammable, combustible (e.g., easily ignitable), or contain components that may inherently pose a hazard when transported. For example, the transport and shipment of certain types of batteries (e.g., lithium-based batteries or lithium-ion batteries) may confuse the risk of adverse environmental conditions such as fire, explosion, chemical spills, or radiation leaks.

[0005] Common monitoring technologies used to monitor the condition of items being transported within shipping containers can involve sensors located far from the container. Such monitoring technologies are located, and may be located, too far away, which can cause lags or undesirable delays in detecting any type of environmental anomaly associated with items being loaded or simply maintained within the shipping container (e.g., unit loading equipment (ULD) type containers, intermodal shipping containers, palletized containers for carrying one or more parcels, storage facilities that can temporarily maintain parcels as non-mobile shipping containers, etc.). Such environmental anomalies may involve extremely hot and corrosive conditions that can spread rapidly. Therefore, any delay in detecting such environmental anomalies is inherently risky, and adverse environmental conditions can rapidly intensify and spread, causing damage to parcels, containers, other parcels within containers, other nearby containers, the transport vehicle carrying the container, and potentially injury and loss of life to those operating the transport vehicle or manipulating the shipping container. Furthermore, assessing the risks arising from such environmental anomalies and any delays in implementing remediation plans to address them also increases the undesirable severity of any environmental anomaly and its ability to rapidly intensify and spread, thereby causing rapid damage to parcels, containers, other parcels within containers, other nearby containers, the transport vehicles carrying the containers, and potentially causing injury and loss of life to those operating the transport vehicles or manipulating the containers.

[0006] Therefore, those skilled in the art will understand that the ability to quickly detect any environmental anomalies is important when transporting certain types of goods, objects, and materials, as time is of the essence. This is especially true when transporting packages (e.g., goods, objects, materials) on aircraft, where the presence of any environmental anomaly can be catastrophic, resulting in loss of property and life due to any delay in detecting such anomalies, and any resulting delay in initiating or responding to or mediating actions to resolve the detected anomaly.

[0007] To meet these requirements, a wide variety of systems, devices, and methods are needed to improve and enhance the detection of environmental anomalies—particularly on shipping containers with one or more packages—and to improve how to respond to such detected environmental anomalies. Therefore, there remains a need for improved systems, devices, and methods that can provide broader and more robust detection of environmental anomalies in a more timely and integrated manner than previously thought possible, along with the automated generation of hierarchical alarms and the adaptive initiation of one or more mediation responses. Summary of the Invention

[0008] In the following description, certain aspects and embodiments will become apparent. It should be understood that these aspects and embodiments, in their broadest sense, can be practiced without one or more features of these aspects and embodiments. It should be understood that these aspects and embodiments are merely exemplary.

[0009] One aspect of this disclosure proposes an improved monitoring system for detecting environmental anomalies within a shipping container maintaining parcels and for reporting tiered alarm notifications related to the environmental anomalies to an external transceiver unit associated with the transport vehicle transporting the shipping container. Generally, the system includes multiple ID nodes housed within the shipping container and a command node installed on the shipping container. Each of the ID nodes is associated with a corresponding parcel maintained within the shipping container, and each ID node includes at least one ID node processing unit (e.g., a processor), an ID node memory coupled to the processing unit, environmental sensors, and a wireless transceiver operatively coupled to the ID node processing unit. The ID node memory maintains at least ID node monitoring program code that programmatically adapts the ID node to an ID node beyond a general-purpose computer. The environmental sensors of the ID node are configured to generate sensor data related to the environmental conditions of the corresponding parcel associated with that ID node. When the ID node processing unit executes the ID node monitoring program code, the wireless transceiver (whether implemented in hardware, a combination of hardware and software, or as a software-defined radio (SDR)) is configured to access sensor data generated by the environmental sensors and broadcast the sensor data in response to report commands from the ID node processing unit.

[0010] The system's command node includes at least a command node processing unit, a command node memory coupled to the command node processing unit, and two communication interfaces (each communication interface can be implemented in hardware, a combination of hardware and software, or as an SDR). The command node's memory maintains command node container management program code and context data associated with each of the ID nodes, wherein the context data includes at least a plurality of environmental threshold conditions corresponding to each of the packages. A first communication interface is operatively coupled to the command node processing unit and configured to communicate with each ID node using a first wireless communication format compatible with the wireless transceiver on each ID node. A second communication interface is operatively coupled to the command node processing unit and configured to communicate with an external transceiver unit associated with the transport vehicle using a second wireless communication format.

[0011] Accordingly, the command node processing unit is programmatically configured, when executing the command node container management program code, to operate using a first communication interface to detect sensor data broadcast from ID nodes; compare the detected sensor data from each ID node with the corresponding context data associated with each ID node; detect an environmental anomaly in the shipping container when the comparison of the detected sensor data with the context data indicates that the environmental conditions of at least one package exceed its corresponding environmental threshold condition; in response to the detection of the environmental anomaly, generate a hierarchical alarm notification related to the environmental anomaly in the shipping container (wherein the hierarchical alarm notification identifies the target mediation recipient, identifies the target mediation action, and establishes a mediation response priority based on the comparison of the received sensor data with the context data); and cause a second communication interface to transmit the hierarchical alarm notification to an external transceiver unit to initiate a mediation response related to the target mediation action. Accordingly, the hierarchical alarm notification does not merely report the detected anomaly, but actively and interactively instructs the external transceiver to take a specific mediation response related to the content identified by the command node as a target mediation action.

[0012] In another aspect of this disclosure, an improved method is described for monitoring shipping containers and responding to environmental anomalies using a wireless node network, the wireless node network having at least a plurality of ID nodes disposed within the shipping container and a command node installed on and associated with the shipping container. Each ID node has at least one environmental sensor and is associated with a corresponding one of a plurality of parcels maintained within the shipping container, and wherein the command node is operable to communicate with each ID node and an external transceiver unit associated with a transport vehicle. The method begins by generating sensor data from the environmental sensor on each ID node, the sensor data relating to the environmental conditions of the corresponding parcel associated with each ID node when the parcel resides within the shipping container. Next, the method causes each ID node to broadcast the generated sensor data. The method continues in such a manner that the command node detects the sensor data broadcast from the ID nodes and compares the detected sensor data from each ID node with locally maintained context data associated with each ID node. Such context data includes at least a plurality of environmental threshold conditions, respectively corresponding to the parcels. The method then continues as follows: when a comparison of detected sensor data with corresponding context data indicates that environmental conditions in at least one package exceed their corresponding environmental threshold conditions, the command node detects an environmental anomaly in the shipping container. In response to the detected environmental anomaly, the command node then generates a hierarchical alarm notification related to the environmental anomaly in the shipping container, wherein the hierarchical alarm notification identifies the target mediation receiver, identifies the target mediation action, and establishes a mediation response priority based on a comparison of the received sensor data with the context data. The method then causes the command node to transmit the hierarchical alarm notification to the transceiver unit to initiate a mediation response related to the target mediation action (instead of simply reporting the detected environmental anomaly).

[0013] In another aspect of this disclosure, a more detailed system is described for detecting, automatically reporting, and proactively responding to environmental anomalies in a shipping container on a transport vehicle, wherein the shipping container maintains parcels being transported on the vehicle. Generally, the system has multiple ID sensor nodes disposed within the shipping container, a command node mounted to the shipping container, and a transport vehicle transceiver mounted on the transport vehicle. Each ID sensor node is associated with a corresponding parcel maintained within the shipping container, and each ID sensor node has an ID sensor node processing unit (e.g., a processor, such as a microprocessor, microcontroller, or other programmable logic circuit), an ID sensor node memory coupled to the ID sensor node processing unit (which maintains at least ID sensor node monitoring program code), at least one environmental sensor, and a wireless transceiver. The environmental sensor of the ID sensor node is configured to generate sensor data relating to the environmental conditions of the corresponding parcel associated with a particular ID sensor node. The wireless transceiver of the ID sensor node (whether implemented in hardware, a combination of hardware and software, or as a software-defined radio (SDR)) is coupled to the ID sensor node processing unit and configured to access sensor data generated by one or more of the node's environmental sensors while the ID sensor node processing unit executes the ID sensor node monitoring program code, and to broadcast the sensor data in response to report commands from the ID sensor node processing unit.

[0014] The system's command node has at least a command node processing unit, memory coupled to its processor, and at least two wireless communication interfaces (each interface can be implemented in hardware, a combination of hardware and software, or as an SDR). The command node's memory maintains at least command node container management program code (which, when executed, programmatically adapts and specifically configures the command node for unique and unconventional operations) and context data associated with each ID sensor node. The context data includes environmental threshold conditions corresponding to each package. A first communication interface is coupled to the command node processing unit and configured to communicate with each ID sensor node using a first wireless communication format compatible with the wireless transceiver on each ID sensor node. A second communication interface is also coupled to the command node processing unit and configured to communicate via a second wireless communication format.

[0015] The transport vehicle transceiver on the vehicle communicates with the second communication interface of the command node and has at least a display interface and a fire suppression system interface.

[0016] The command node processing unit is programmatically configured to, when executing the command node container management program code, operate to use a first communication interface to detect sensor data broadcast from ID sensor nodes; compare the detected sensor data from each ID sensor node with context data associated with each ID sensor node; detect an environmental anomaly in the shipping container when the comparison of the detected sensor data with the context data indicates that the environmental conditions of at least one package exceed its corresponding environmental threshold condition; in response to the detection of the environmental anomaly, generate a hierarchical alarm notification related to the environmental anomaly in the shipping container (wherein the hierarchical alarm notification identifies the target mediation recipient, identifies the target mediation action, and establishes a mediation response priority based on the comparison of the received sensor data with the context data); and cause a second communication interface to transmit the hierarchical alarm notification to the transport vehicle transceiver to initiate a mediation response related to the target mediation action.

[0017] In response to receiving a hierarchical alarm notification from the command node, the transport vehicle transceiver is operable to automatically generate a mediation message as a mediation response, wherein such a mediation message reflects the target mediation action (e.g., triggering a fire suppression system to initiate via its first fire suppression system interface) and the priority of the mediation response, and provides the mediation message to the target mediation recipient.

[0018] Each of these aspects respectively realizes an improvement in the technology for monitoring and detecting environmental anomalies, and how to respond more robustly and quickly to any such detected environmental anomalies. Additional advantages of this and other aspects of the disclosed embodiments and examples will be set forth in part in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. It is to be understood that both the foregoing general description and the following detailed description are merely exemplary and illustrative for the purposes of the claimed invention, and are not restrictive. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several embodiments according to one or more principles of the invention and, together with the specification, serve to explain one or more principles of the invention. In the drawings,

[0020] Figure 1 This is a diagram illustrating an exemplary wireless node network according to an embodiment of the present invention;

[0021] Figure 2 This is a more detailed illustration of an exemplary wireless node network according to embodiments of the present invention;

[0022] Figure 3 This is a more detailed illustration of an exemplary ID node device according to an embodiment of the present invention;

[0023] Figure 4This is a more detailed illustration of an exemplary master node device according to an embodiment of the present invention;

[0024] Figure 5 This is a more detailed illustration of an exemplary server according to an embodiment of the present invention;

[0025] Figure 6 This is a diagram illustrating the structure or format of an exemplary advertisement data packet according to an embodiment of the present invention;

[0026] Figure 7 This is a diagram illustrating sample content of an exemplary notification data group according to an embodiment of the present invention;

[0027] Figure 8 This is a state diagram illustrating the exemplary states of an exemplary node in a wireless node network according to an embodiment of the present invention, and the transitions between states as part of an operation;

[0028] Figure 9 This is a diagram illustrating exemplary components of a wireless node network during an exemplary master node to ID node association according to an embodiment of the present invention;

[0029] Figure 10 This is a diagram illustrating exemplary components of a wireless node network during an exemplary ID-to-ID node association according to an embodiment of the present invention;

[0030] Figure 11 This is a diagram illustrating exemplary components of a wireless node network during an exemplary ID-to-master node query according to an embodiment of the present invention;

[0031] Figure 12 This is a diagram illustrating exemplary components of a wireless node network during an exemplary alarm notification mode according to an embodiment of the present invention;

[0032] Figure 13 This is an illustration of an exemplary location determination using master node announcements according to an embodiment of the present invention;

[0033] Figure 14 This is a diagram illustrating an exemplary location determination using ID node announcements according to an embodiment of the present invention;

[0034] Figure 15 This is a diagram illustrating an exemplary position determined by triangulation according to an embodiment of the present invention;

[0035] Figure 16 This is a diagram illustrating an exemplary position determination by chain triangulation according to an embodiment of the present invention;

[0036] Figure 17This is a flowchart illustrating an exemplary method for locating nodes in a wireless node network based on signal patterns and characteristics observed over a time period, according to an embodiment of the present invention.

[0037] Figure 18 This is a flowchart illustrating an exemplary method for determining location by varying the power characteristics of nodes in a wireless node network according to an embodiment of the present invention.

[0038] Figure 19 This is a flowchart illustrating an exemplary method for determining location using associations of one or more nodes in a wireless node network according to an embodiment of the present invention;

[0039] Figure 20 This is a flowchart illustrating another exemplary method for determining location using associations of one or more nodes in a wireless node network according to an embodiment of the present invention;

[0040] Figure 21 This is a flowchart illustrating yet another exemplary method for determining location using associations of one or more nodes in a wireless node network according to an embodiment of the present invention;

[0041] Figure 22 This is a flowchart illustrating an exemplary method for determining the location of a first node in a wireless node network based on context data according to an embodiment of the present invention;

[0042] Figure 23 This is a flowchart illustrating an exemplary method for determining the location of one of a plurality of nodes in a wireless node network having a server using chain triangulation according to an embodiment of the present invention.

[0043] Figure 24A This is a diagram of an exemplary wireless node network according to an embodiment of the present invention, which is used to detect environmental anomalies using command nodes and ID nodes placed inside a shipping container.

[0044] Figure 24B This is a diagram of another exemplary wireless node network according to an embodiment of the present invention, which is used to detect environmental anomalies using command nodes and ID nodes associated with packages placed inside shipping containers.

[0045] Figure 24C This is a diagram of another exemplary wireless node network according to an embodiment of the present invention, which is used to detect environmental anomalies using command nodes and geographically dispersed ID nodes within shipping containers.

[0046] Figure 25AThis is an illustration of multiple shipping containers in the form of exemplary ULD containers, such as those loaded into an aircraft cargo warehouse, according to an embodiment of the present invention.

[0047] Figure 25B This is an illustration of multiple exemplary containers in the cargo warehouse of an aircraft according to an embodiment of the present invention, the aircraft having an onboard exemplary fire suppression system that is selectively and responsively deployed as part of a mediating response to detected environmental anomalies;

[0048] Figure 25C This is a diagram illustrating further exemplary external transceivers disposed in various control compartments of an exemplary aircraft transport vehicle according to an embodiment of the present invention;

[0049] Figure 26 This is a more detailed illustration of an exemplary command node device according to an embodiment of the present invention;

[0050] Figure 27 This is a flowchart illustrating an exemplary method for monitoring environmental anomalies of a shipping container using a wireless node network according to an embodiment of the present invention, wherein the wireless node network uses sensor data from ID nodes associated with the package and environmental threshold conditions of the package;

[0051] Figure 28 This is a flowchart illustrating an exemplary method for monitoring environmental anomalies in a shipping container using a wireless node network according to an embodiment of the present invention. The wireless node network uses sensor data from ID nodes that are placed inside the shipping container but are not associated with a specific package but are associated with environmental threshold conditions of ID nodes.

[0052] Figure 29 This is a flowchart illustrating an exemplary method for monitoring environmental anomalies in a shipping container using a wireless node network according to an embodiment of the present invention. The wireless node network uses ID node sensor data from ID nodes that are placed inside the shipping container but are not typically associated with a specific package but are associated with environmental threshold conditions of ID nodes, as well as command node sensor data from command nodes installed in the shipping container.

[0053] Figure 30 This is a flowchart illustrating an exemplary method according to an embodiment of the present invention, which is used to monitor environmental anomalies of a shipping container using a wireless node network based on unexpected communications from ID nodes placed inside the shipping container.

[0054] Figure 31This is a diagram of another exemplary wireless node network according to an embodiment of the present invention, which is used to detect environmental anomalies using command nodes associated with shipping containers transported on a transport vehicle and ID nodes inside and outside the shipping containers on the transport vehicle, wherein each of the ID nodes is associated with a package.

[0055] Figures 32A-32C These are a series of illustrations of an exemplary airborne fire suppression system according to embodiments of the present invention, which can be activated and deployed on a transport vehicle to initiate mediation actions in response to detected environmental anomalies related to a shipping container being transported on the transport vehicle.

[0056] Figure 33 This is a diagram of yet another exemplary wireless node network according to an embodiment of the present invention, which is used to detect environmental anomalies using command nodes associated with shipping containers transported on a transport vehicle and ID nodes inside and outside the shipping containers on the transport vehicle, wherein the ID nodes are not specifically associated with packages.

[0057] Figure 34 This is a diagram of yet another exemplary wireless node network according to an embodiment of the present invention, which is used to detect environmental anomalies using command nodes associated with shipping containers transported on a transport vehicle and ID nodes inside and outside the shipping containers on the transport vehicle, wherein the ID nodes in the network are a combination of packaged and non-packaged ID nodes inside and outside the shipping containers.

[0058] Figure 35 This is a flowchart illustrating an exemplary method according to an embodiment of the present invention, which is used to monitor environmental anomalies related to a shipping container using a wireless node network, the wireless node network having at least a command node associated with the shipping container and ID nodes inside and outside the shipping container, wherein the ID nodes are not specifically associated with a package.

[0059] Figure 36 This is a flowchart illustrating an exemplary method according to an embodiment of the present invention. The exemplary method is used to monitor environmental anomalies related to a shipping container using a wireless node network, the wireless node network having at least a command node associated with the shipping container, ID nodes inside and outside the shipping container, an airborne fire suppression system, and an external transceiver.

[0060] Figures 37A-37BThis is an illustration of an exemplary shipping container according to an embodiment of the present invention, which utilizes an exemplary wireless node network to detect environmental anomalies associated with the shipping container using command nodes installed on the shipping container and ID nodes selectively assigned within the shipping container.

[0061] Figures 38A-38B This is an illustration of an exemplary shipping container according to an embodiment of the present invention, which utilizes an exemplary wireless node network to detect environmental anomalies associated with the shipping container using command nodes installed in the shipping container and ID nodes selectively reassigned within the shipping container when the contents of the shipping container change.

[0062] Figure 39 This is a flowchart illustrating an exemplary method according to an embodiment of the present invention, which is used to monitor environmental anomalies of a shipping container using a command node installed to a shipping container and a selection of ID nodes from a plurality of ID nodes located at different positions within the shipping container.

[0063] Figure 40 This is an illustration of an exemplary external transceiver according to an embodiment of the present invention. The external transceiver can be activated and deployed on a transport vehicle to initiate mediation actions in response to detected environmental anomalies related to a shipping container being transported on the transport vehicle.

[0064] Figures 41A-41D This is an illustration of an exemplary enhanced shipping container according to an embodiment of the present invention, which uses selectively assigned ID nodes to transport parcels and self-monitors environmental anomalies;

[0065] Figures 42A-42C This is an illustration of an exemplary shipping container according to an embodiment of the present invention. The shipping container utilizes an exemplary wireless node network to use a set of monitoring beacons, consisting of command nodes installed on the shipping container and ID nodes selectively assigned within the shipping container, to detect environmental anomalies associated with the shipping container. The monitoring beacons include dedicated bridging nodes for remotely monitoring the beacons.

[0066] Figure 43 This is a flowchart illustrating an exemplary method for adaptively monitoring environmental anomalies using a set of monitoring beacons according to an embodiment of the present invention, wherein the set of monitoring beacons includes a dedicated bridging node for remotely monitoring the beacons;

[0067] Figure 44 This is an illustration of an exemplary enhanced shipping container according to an embodiment of the present invention, which uses sensor-based ID nodes to transport packages and self-monitor for environmental anomalies;

[0068] Figures 45A-45BThis is a diagram of an exemplary adaptive wireless node network system according to an embodiment of the present invention, which uses a master command node and designated survivor command nodes to monitor environmental anomalies in shipping containers.

[0069] Figures 46A-46B This is a diagram of an exemplary adaptive wireless node network system according to an embodiment of the present invention, which uses a master command node and multiple priority-based survivor command nodes to monitor environmental anomalies in shipping containers.

[0070] Figure 47 This is a flowchart illustrating an exemplary method for adaptively monitoring environmental anomalies of shipping containers using a master command node and designated survivor command nodes according to an embodiment of the present invention;

[0071] Figures 48A-48C This is a diagram of an exemplary dynamic monitoring system according to an embodiment of the present invention. The dynamic monitoring system uses a wireless ID node, a command node as a master monitor, and an external master node to identify and respond to environmental anomalies related to the shipping container. The external master node is operable to temporarily act as a master monitor in response to the environmental anomaly.

[0072] Figures 49A-49B This is a diagram illustrating the master monitor switching within an exemplary dynamic monitoring system according to an embodiment of the present invention. The dynamic monitoring system is used to identify and respond to environmental anomalies related to the shipment of containers using a wireless ID node, a command node acting as the master monitor, and an external master node, which is operable to temporarily act as the master monitor in response to the environmental anomalies.

[0073] Figures 50A-50C These are a series of diagrams of another exemplary airborne fire suppression system according to an embodiment of the present invention, which has an integrated master node and is activated and deployed on a transport vehicle for monitoring environmental anomalies and initiating mediation actions in response to detected environmental anomalies related to shipping containers being transported on the transport vehicle.

[0074] Figure 51 This is a diagram illustrating an exemplary airborne fire suppression system according to an embodiment of the present invention. The airborne fire suppression system has an integrated master node coupled to an exemplary shipping container sensor, which can be deployed as part of the fire suppression system to provide further monitoring and assessment of environmental anomalies related to the shipping container.

[0075] Figure 52This is a diagram illustrating yet another exemplary airborne fire suppression system according to an embodiment of the present invention, which has a pressurized fire extinguishing material container and a controlled release nozzle that can be actuated to deliver fire extinguishing material to a shipping container monitored by a master node enabled fire suppression system.

[0076] Figures 53A-53D These are a series of illustrations of exemplary deployable shipping containers according to embodiments of the present invention;

[0077] Figure 54 This is an illustration of an exemplary shipping container according to an embodiment of the present invention, which is reinforced with an exemplary fire suppression panel implemented within or as part of a wall of the container.

[0078] Figure 55 This is an illustration of an exemplary shipping container according to an embodiment of the present invention, which is reinforced by an alternative exemplary fire suppression panel attached to one wall of the shipping container;

[0079] Figures 56A-56D The illustrations are a series of diagrams relating to the details and operation of an enhanced shipping container according to an embodiment of the present invention, the enhanced shipping container having at least one fire extinguishing panel, and as in an improved system for coordinated reconciliation actions in response to identified environmental anomalies associated with the shipping container.

[0080] Figure 57 This is a diagram illustrating an exemplary node-enabled battery system with integrated environmental monitoring and reporting functions according to an embodiment of the present invention;

[0081] Figure 58 This is a diagram illustrating an exemplary node-enabled packaging system for a battery with integrated environmental detection and reporting functions according to an embodiment of the present invention;

[0082] Figure 59 This is a diagram illustrating an exemplary improved system according to an embodiment of the present invention, the improved system being used to coordinate and mediate actions in response to identified environmental anomalies associated with a shipping container for transporting at least one node-enabled battery system and at least one node-enabled parcel system for the battery.

[0083] Figure 60A This is a diagram illustrating an exemplary multi-node enabled package system for transporting multiple batteries, with integrated environmental detection and reporting functions according to an embodiment of the present invention.

[0084] Figure 60B This is a diagram illustrating an exemplary multi-node enabled parcel system and parcel master node for transporting multiple batteries, having integrated environmental detection and reporting functions according to an embodiment of the present invention.

[0085] Figure 61 This is a diagram illustrating an exemplary improved system according to an embodiment of the present invention for coordinating and resolving actions in response to identified environmental anomalies associated with a shipping container, the exemplary node-enabled battery system for shipping container transportation, the exemplary node-enabled parcel system for batteries, and the exemplary multi-node-enabled parcel system for transporting multiple batteries.

[0086] Figure 62 This is a diagram illustrating an exemplary system for initiating a tiered mediation response to battery-related environmental anomalies, involving a node-enabled battery device, at least one secondary sensor-based ID node, and a command node, according to an embodiment of the present invention.

[0087] Figure 63 This is a diagram illustrating an exemplary system for initiating a tiered mediation response to battery-related environmental anomalies, comprising multiple node-enabled battery devices, at least one secondary sensor-based ID node, and a command node, according to an embodiment of the present invention.

[0088] Figure 64 This is a diagram illustrating an exemplary system for initiating a tiered mediation response to battery-related environmental anomalies, involving a node-enabled battery device and a command node deployed with multiple environmental sensors, according to an embodiment of the present invention.

[0089] Figure 65 This is a diagram illustrating an exemplary enhanced system for detecting and verifying environmental anomalies within an improved shipping container having a master command node and a secondary command node, according to an embodiment of the present invention.

[0090] Figure 66 This is a flowchart illustrating an exemplary enhanced method according to an embodiment of the present invention, which is used to detect and verify environmental anomalies related to the shipping container using a first command node installed on the shipping container, a second command node installed on the shipping container, and multiple sensor-based ID nodes placed at different locations inside the shipping container.

[0091] Figure 67 This is a diagram illustrating an exemplary system for securely monitoring environmental anomalies of a shipping container using elements of a wireless node network according to an embodiment of the present invention. The elements of the wireless node network interact with an external transceiver associated with a transport vehicle, which has at least a temporary storage location for the shipping container.

[0092] Figure 68 This is a flowchart illustrating an exemplary method for securely monitoring environmental anomalies of a shipping container based on an ID node of a verified sensor used as a trusted sensor, according to an embodiment of the present invention.

[0093] Figure 69 This is a flowchart illustrating an exemplary method for securely monitoring environmental anomalies in a shipping container based on verified sensor data used as trusted sensor data, according to an embodiment of the present invention.

[0094] Figure 70 This is a diagram illustrating an exemplary node-enhanced detection blanket according to an embodiment of the present invention, shown in perspective within a cross-sectional view of a shipping container;

[0095] Figure 71 This is a diagram illustrating an exemplary system according to an embodiment of the present invention, which uses multiple types of node-enabled detection blankets below and above the package to enhance the detection of environmental anomalies associated with packages maintained in shipping containers;

[0096] Figure 72 This is a diagram illustrating an exemplary rigid type node-enabled detection blanket according to an embodiment of the present invention;

[0097] Figure 73 This is a diagram illustrating an exemplary node-enabled detection blanket having multiple panels according to an embodiment of the present invention;

[0098] Figure 74 This is a diagram illustrating an exemplary flexible webbing type node-enabled detection blanket according to an embodiment of the present invention;

[0099] Figure 75 This is a diagram illustrating another exemplary system according to an embodiment of the present invention, which is used to enhance the detection of environmental anomalies associated with packages maintained in shipping containers by using a plurality of node-enabled detection blankets arranged relative to different wrapping layers.

[0100] Figures 76A-76C These are a series of diagrams illustrating an exemplary shipping container with an exemplary base pallet according to an embodiment of the present invention, the base pallet having an exemplary node-enabled detection blanket attached to the base pallet, along with additional features that can be deployed as part of the exemplary node-enabled detection blanket.

[0101] Figure 77 This is a flowchart illustrating an exemplary adaptive method according to an embodiment of the present invention. The exemplary adaptive method is used to refine the monitoring of environmental anomalies of shipping containers by using a wireless node network when a command node detects environmental anomalies.

[0102] Figure 78This is a diagram illustrating an exemplary system for detecting environmental anomalies related to parcels transported within a shipping container on a transport vehicle having an external transceiver, according to an embodiment of the present invention. The system includes an exemplary parcel command node.

[0103] Figures 79A-79C This is an illustration of an exemplary system for detecting environmental anomalies related to a parcel being transported within a shipping container on a transport vehicle having an external transceiver, according to an embodiment of the present invention. The system includes an exemplary parcel command node that interacts with and works together with an exemplary shipping container command node. Detailed Implementation

[0104] Reference will now be made in detail to exemplary embodiments. Where possible, the same reference numerals are used in the drawings and description to refer to the same or similar parts.

[0105] Generally, various embodiments of context-aware hierarchical wireless node networks are described below. These hierarchical wireless node networks can be managed, operated, and applied as part of exemplary systems, apparatuses, and methods involving the detection of environmental anomalies, based on the principles set forth herein. Generally, exemplary embodiments of wireless node networks may include various interconnected devices. For example, one or more lower-level devices or nodes (e.g., sensorless ID nodes or sensor-based ID nodes) may exist, relying on short-range communication with intermediate-level devices or nodes (e.g., self-localizing master nodes or command nodes that may not have onboard self-localization circuitry). These intermediate-level devices or nodes are operable to communicate with higher-level devices (e.g., transceivers located externally to a shipping container as part of a transport vehicle) via different communication paths, while lower-level and intermediate-level nodes cannot communicate directly with higher-level devices. In some embodiments of the network, higher-level devices (e.g., remote control centers or remote servers) may communicate with one or more higher-level devices (e.g., external transceivers on transport vehicles).

[0106] Those skilled in the art will appreciate that such a hierarchical structure of different functional communication network components (commonly referred to as network devices) can be characterized as a node network. Those skilled in the art will appreciate that in some embodiments, a wireless node network may include external transceivers and / or remote servers as well as different wireless nodes, despite the fact that the external transceivers and / or remote servers may not be dedicated wireless components. In other embodiments, the network may include similar types of wireless nodes or different types of wireless nodes.

[0107] Furthermore, those skilled in the art will appreciate that each embodiment described herein implements improvements to a particular technique, such as enhancing and improving how quickly and automatically environmental anomalies are detected, and providing enhanced methods for initiating automatic mediation responses to detected environmental anomalies. These enhanced methods help avoid damage to property being shipped, vehicles transporting such property, and facilitate the use of adaptive, context-aware wireless node networks of node elements to avoid loss of life due to such environmental anomalies. Each embodiment describes a particular application of technique to one or more nodes operating in such a wireless node network, wherein said particular application of technique improves or otherwise enhances such a technical field as explained and supported by the following disclosure.

[0108] Those skilled in the art will understand from the following detailed description that nodes can be associated with or located near items, objects, or materials (uniformly and generally referred to herein as "packages"), and can be used to identify and locate packages, detect surrounding environmental conditions near nodes and / or packages, be dynamically programmed during network operation, and load and unload packages during individual transport or within shipping containers (such as ULD type containers). Various embodiments of wireless node networks, exemplary methods for monitoring and managing components of wireless node networks, exemplary methods for better determining the location of components of wireless node networks, and applications of wireless node networks for enhancing logistics operations that rely on wireless node networks, which can improve the detection of environmental anomalies, provide enhanced hierarchical alerts as part of a remedial response to detected anomalies, induce or initiate hierarchical remedial responses to such environmental anomalies, and perform such remedial responses in a targeted, selective, and rapid manner to improve the security of transporting any such packages.

[0109] Wireless node network

[0110] Figure 1 The illustration shows a basic diagram of an exemplary wireless node network according to an embodiment of the present invention. Figure 1 The exemplary network shown includes a server 100 connected to network 105, which is also operatively connected to different network components, such as master node 110a, and indirectly connected to ID node 120a via master node 110a. Master node 110a is typically connected via short-range wireless communication (e.g., The master node 110a typically connects to the server 100 via long-range wireless communication (e.g., cellular) and / or mid-range wireless communication (e.g., wireless LAN or Wi-Fi). The ID node 120a is typically a low-cost device that can be easily placed in a package, integrated as part of the packaging, or otherwise associated with an item to be tracked and located, such as package 130, a person, or an object (e.g., a vehicle). Figure 1 As shown, ID nodes typically communicate directly with the master node but not directly with the server, while the master node communicates directly with the server and, individually and directly with other nodes (such as ID nodes or another master node). Additional exemplary wireless node networks may include additional nodes (such as master node types called command nodes, and further network elements called external transceivers associated with delivery vehicles). The ability to deploy a node hierarchy within an exemplary wireless node network to efficiently and cost-effectively distribute tasks and functions at different levels facilitates a wide variety of adaptive localization, tracking, management, monitoring, detection, reporting, and mediation response applications using such node networks, as discussed in more detail below.

[0111] Generally, as part of maintaining the location of tracking ID node 120a (and associated items), the lower-cost, lower-complexity ID node 120a is managed by the higher-complexity master node 110a and server 100, thereby providing intelligent, robust, and broad visibility into the location and status of ID node 120a. In a typical embodiment, ID node 120a is initially associated with an item (e.g., package 130, person, or object). As ID node 120a moves with the item, it becomes associated with master node 110a, and server 100 uses this information for updates. Further movement of ID node 120a and the item can cause ID node 120a to be unassociated from master node 110a and transferred, becoming associated with another master node (not shown), after which server 100 is updated again. Thus, as an item physically moves from one location to another, server 100 typically operates to coordinate and manage information associated with ID node 120a. Further details of the architecture and functionality of exemplary ID node and master node embodiments are referenced below. Figure 3 and Figure 4 For a more detailed description, please refer to the exemplary server 100 below. Figure 5 To provide a more detailed description.

[0112] Although server 100 is shown connected via network 105, those skilled in the art will appreciate that, depending on implementation details and desired communication paths, server 100 may have [other features]. Figure 1 More direct or dedicated connections to other components illustrated in the diagram (such as master node 110a). Furthermore, those skilled in the art will appreciate that the exemplary server can be connected to a database ( Figure 1 The information set (not shown) may contain multiple databases maintained on multiple server platforms or network storage servers in other embodiments. Furthermore, those skilled in the art will appreciate that the database can be implemented using cloud technology, which essentially provides networked storage of the information set that can be directly accessed by devices such as master node 110a.

[0113] Network 105 may be a general data communication network involving multiple communication networks or paths. Those skilled in the art will appreciate that such an exemplary network or path can be implemented using hardwired structures (e.g., LANs, WANs, telecommunication lines, telecommunication support structures, and telecommunication processing equipment, etc.), wireless structures (e.g., antennas, receivers, modems, routers, repeaters, etc.), and / or combinations of both, depending on the implementation of server 100 and... in this embodiment of the invention. Figure 1 The desired implementation of a network in which other components are interconnected, as shown.

[0114] Master node 110a and ID node 120a are node types. Nodes are typically devices or apparatuses used as part of a component network to perform one or more tasks. Node embodiments may have unique identifiers, such as Media Access Control (MAC) addresses or addresses assigned to hardware radios, such as Internet Protocol 6 (IPv6) identifiers. In some embodiments, a node's unique identifier may be associated with a shipping identifier (e.g., a shipping tracking number in one example), or it may itself be a shipping tracking reference.

[0115] ID nodes, such as ID node 120a, are typically low-cost active wireless devices. In one embodiment, an exemplary ID node is a transceiver-based processing or logic unit having a short-range radio with variable RF characteristics (e.g., programmable RF output power range, programmable receiver sensitivity), memory accessible by the processing unit, timers operatively coupled to the processing unit, and a power source (e.g., a battery) to power the ID node's circuitry. For example, the physical implementation of the exemplary ID node can be small and therefore can be integrated into packages, tags, containers, or other types of objects. In some implementations of the ID node, the node is rechargeable, while other implementations do not allow recharging of the ID node's power source. In other implementations, the ID node is environmentally self-contained or hermetically sealed to enable robust and reliable operation under a variety of harsh environmental conditions.

[0116] A master node, such as master node 110a, typically acts as a smart bridge between ID node 120a and server 100. Therefore, a master node is generally more complex than an ID node. In one example embodiment, an exemplary master node is a device having: a processing or logic unit, a short-range radio (which may have variable RF characteristics) for communicating with other nodes (ID nodes and other master nodes), a medium-range and / or long-range radio for communicating with server 100, memory accessible by the processing unit, a timer operatively coupled to the processing unit, and a power source (e.g., a battery or wired power connection) for powering the circuitry of the master node. An exemplary master node, such as master node 110a, may be located in a known fixed location, or alternatively, may be a mobile unit with dedicated location-finding circuitry (e.g., GPS circuitry) to allow the master node to determine its own location.

[0117] Although Figure 1 The illustrated embodiment shows only a single master node and a single ID node; however, those skilled in the art will appreciate that a wireless network consistent with embodiments of the present invention can include a wide array of similar or different master nodes, each communicating with server 100 and / or other master nodes, as well as a variety of similar or different ID nodes. Therefore, Figure 1 The exemplary network shown is a basic embodiment, while Figure 2 The exemplary network shown is a more detailed exemplary wireless node network according to another embodiment of the present invention.

[0118] Now for reference Figure 2 Another exemplary wireless node network, including server 100 and network 105, is shown. Here, master nodes 110a, 110b, and 110c are deployed and connected to network 105 (and, by means of those corresponding connections, to server 100) and to each other. ID nodes 120a, 120b, and 120e are shown as connectable or operable to communicate with various master nodes via different paths. However, Figure 2 The ID nodes 120c and 120d shown are connected to ID node 120b, but not to any master node. This could be, for example, if ID nodes 120b, 120c, and 120d are associated with different items (e.g., packages) within a larger container 210 (or grouped together on a pallet). In such an example, only ID node 120b can remain within wireless communication range of any master node. This could be due, for example, to the location of the different ID nodes relative to the nearest master node within the container, unfavorable RF shielding caused by the container, unfavorable RF shielding caused by the packaging of the items, or unfavorable RF shielding caused by other nearby materials that interfere with radio transmission (e.g., several metal items wrapped between the ID node and any master node outside the container). Therefore, in Figure 2 In the illustrated configuration of the exemplary network shown in the figure, ID nodes 120c and 120d may be outside the range of the master node, but still have a valid communication path to the master node through ID node 120b.

[0119] In fact, in one example, ID node 120b could actually be the master node before being placed inside container 210. However, when it is placed inside container 210, the changed RF environment may interfere with the master node’s ability to locate itself via location signals (e.g., GPS signals) and cause the master node to temporarily operate as an ID node while still providing communication and data sharing with other ID nodes in container 210.

[0120] User access devices 200 and 205 are also... Figure 2 The diagram illustrates the ability to connect to network 105, the master node, and the ID node. Typically, user access devices 200 and 205 allow users to interact with one or more components of the exemplary wireless node network. In various embodiments, user access devices 200 and 205 can use desktop computers, laptop computers, tablet devices (such as Apple...) Touchscreen tablet devices), personal area network devices (such as...) Devices), smartphones (such as Apple) ), smart wearable devices (such as Samsung Galaxy Gear) TM Smartwatch or Google Glass TM This can be implemented as a wearable smart optical device or other such device capable of communicating with server 100 via network 105 (through wired or wireless communication paths to the master node and ID node). Therefore, an exemplary user access device can be a mobile type device designed for easy movement (such as a tablet or smartphone) or a non-mobile type device designed for operation from a fixed location (such as a desktop computer).

[0121] like Figure 2 As shown, user access devices 200 and 205 are coupled to and communicate with network 105, but each of them can also communicate in a more direct manner (e.g., via near field communication (NFC)). They communicate with each other or with other network components via wireless connections, Wi-Fi networks, dedicated wired connections, or other communication paths.

[0122] In one example, a user access device such as device 200 or 205 can facilitate the association of an ID node (such as ID node 120a) with the package's tracking number at the start of the shipment process, coordinate with server 100 to check the status and / or location of the package and associated ID nodes during transit, and, where possible, retrieve data from the master node or ID node associated with the shipped package. Therefore, those skilled in the art will appreciate that user access devices such as devices 200 and 205 are essentially interactive communication platforms through which users can initiate the shipment of items, track items, determine the status and location of items, and retrieve information about items.

[0123] Exemplary user access devices such as devices 200 or 205 may include sufficient hardware and code (e.g., applications or one or more other program code segments) to operate as a master node or ID node in various embodiments, as discussed in more detail below. For example, device 200 may be implemented as a mobile smartphone and functionally operate as an exemplary ID node that broadcasts announcement packets to other ID nodes or master nodes for association and data sharing with such nodes. In another example, device 200 is implemented as a mobile smartphone and may operate as an exemplary master node that communicates and associates with ID nodes and other master nodes as described herein, and communicates with server 100. Therefore, those skilled in the art will appreciate that Figure 3 Exemplary ID nodes and Figure 4 The exemplary master nodes and their corresponding parts, code, and program modules can be implemented using appropriately programmed user access devices, such as device 200 or 205. Therefore, the following... Figure 3 Exemplary ID nodes and Figure 4 The description of the exemplary master node in the text will apply to user access devices that operate as ID nodes or master nodes, respectively.

[0124] ID Node

[0125] Figure 3This is a more detailed illustration of an exemplary ID node device according to embodiments of the present invention, wherein the components of the ID node device are shown housed within an ID node housing for accommodating such a device. Generally, the node housing is used to house the components of the ID node and may be made of environmentally resistant materials to withstand harsh environments caused by, for example, temperature, pressure, chemical leaks, and / or radiation leaks. However, in some embodiments, the ID node housing may be a purposefully selected environmentally sensitive material that decomposes upon exposure to specific harsh environmental conditions (e.g., decomposing upon exposure to a predetermined threshold temperature corresponding to a threshold condition indicating an environmental anomaly). For example, the ID node housing may be made of a temperature-sensitive material that can expose one or more major components of the ID node (e.g., its processor, battery, memory, wireless transceiver) when the ID node is deployed in a very high temperature environment. Furthermore, the ID node housing may use a temperature-sensitive material with a high melting point, such that a failure of an ID node with this type of housing can indicate secondary environmental conditions at a predetermined threshold temperature above the temperature corresponding to the threshold condition indicating an environmental anomaly. Therefore, the type of material used for a particular ID node housing can be selectively chosen as part of a device and system for monitoring, detecting, and responding to environmental anomalies.

[0126] As previously described, one embodiment of an ID node includes a transceiver-based processing or logic unit (processor) having a short-range radio with variable RF characteristics (e.g., programmable RF output power range, programmable receiver sensitivity), memory accessible by the processing unit, timers operatively coupled to the processing unit, and a power supply (e.g., a battery) to provide power to the circuitry of the ID node. Reference now... Figure 3 In a more detailed embodiment, exemplary ID node 120a is shown as including a processing or logic unit 300 coupled to a variable power short-range communication interface 375, a memory storage device 315, volatile memory 320, a timer 370, and a battery 355. Those skilled in the art will appreciate that the processing unit 300 is logic such as a low-power microcontroller, which typically performs calculations on data and executes operational and application code, as well as other program modules or sections thereof, within ID node 120a. Accordingly, exemplary processing unit 300 operates as a transceiver-based processing core of ID node 120a.

[0127] Those skilled in the art will also appreciate that the exemplary ID node 120a is a hardware-based component that can be implemented using a single processor or logic unit (such as unit 300). In one embodiment, as required by a particular application, processing unit 300 may utilize... The processing unit 300 is implemented using an 8051 CPU core and associated peripheral circuitry. Less complex microcontrollers or discrete circuits can be used to implement the processing unit 300, as well as more complex and sophisticated microprocessors. Additionally, the exemplary processing unit 300 can be integrated into a single-chip transceiver that serves as the core of the ID node 120a.

[0128] The variable-power short-range communication interface 375 of ID node 120a is typically a programmable radio and an omnidirectional antenna coupled to processing unit 300. In other embodiments, interface 375 may use antennas with different antenna profiles when directivity may be desired. Those skilled in the art will appreciate that the short-range communication interface 375 can be implemented using hardware, a combination of hardware and software, and as a software-defined radio (SDR). Examples of the variable-power short-range communication interface 375 may include methods for operatively coupling a device to a specific short-range communication path (e.g., Other interface hardware or software components (not shown) for a low-power (BLE) connection path (communication at 2.4 GHz).

[0129] In one embodiment, various RF characteristics of the radio transceiver, such as RF output power and / or RF receiver sensitivity, can be dynamically and programmatically varied under the control of processing unit 300. In other embodiments, further RF characteristics of the radio transceiver, such as frequency, duty cycle, timing, modulation scheme, spread spectrum frequency hopping, etc., can be programmatically varied as needed, depending on the desired implementation and intended use of ID node 120a, to flexibly adjust the RF output signal. As will be explained in more detail below, some embodiments may use a broadcast profile with parameters that can be programmatically varied or adjusted. In other words, embodiments of ID node 120a (or any other ID node) may have programmatically adjustable RF characteristics (such as adjustable RF output signal power, adjustable RF receiver sensitivity, the ability to switch to different frequencies or bands, etc.).

[0130] In any of the embodiments described herein, communication interface 375 can be implemented as a transceiver-based communication interface with both short-range and long-range communication capabilities (i.e., it can be used as both a first and a second communication interface, as described in the various embodiments herein). This type of wider-range communication interface 375 can be implemented using LPWAN (Low Power Wide Area Network) connectivity such as LTE 5G, LTE-M, and NB-IoT (Narrowband Internet of Things). LPWAN, often also referred to as Low Power Wide Area (LPWA) networks or Low Power Only (LPN) networks, is a type of wide area network wireless communication format that allows extended-range, low-bandwidth communication for power-sensitive applications such as devices utilizing battery-powered equipment (e.g., ID nodes, mobile master nodes, container nodes, and command nodes). Exemplary types of LPWANs may include Ultra Narrowband (UNB) technology from Sigfox, Random Phase Multiple Access (RPMA) technology from Ingenu, and other Long Range WAN protocols (LoRaWAN) technologies promoted by LoRa Alliance companies (e.g., IBM, Microchip, Cisco, Semtech, Singtel, KPN, Bouygues Telecom). LTE-M is a communication technology that allows node-based devices (such as sensor-based ID nodes or command nodes) to connect directly to Long Term Evolution (4G) cellular networks without gateways and reliance on batteries. NB-IoT is a low-power communication technology that applies a narrowband approach to cellular IoT (Internet of Things) communications, allowing the use of a portion of the GSM spectrum bandwidth in the unused 200kHz band.

[0131] The battery 355 of ID node 120a is a type of power source typically used to power the circuitry implementing ID node 120a. In one embodiment, battery 355 may be a rechargeable power source. In other embodiments, battery 355 may be a non-rechargeable power source intended for disposal after use. In some embodiments of the ID node, the power source may involve alternative energy generation, such as solar cells.

[0132] The timer 370 for ID node 120a typically provides one or more timing circuits for use in applications such as time delay, pulse generation, and oscillator. In embodiments where ID node 120a saves power by entering a sleep or hibernation state within a predetermined time period (as part of an overall power-saving technique), the timer 370 auxiliary processing unit 300 manages the timing operations. Additionally, embodiments may allow ID nodes to share data to synchronize different nodes relative to the timer 370 and a common timing reference between the node and the server.

[0133] Embodiments may implement ID node 120a to optionally include a basic user interface (UI) 305 that indicates status and allows basic interactions such as start / stop. In one embodiment, UI 305 may be implemented using status lights such as multi-mode LEDs. Different colors of the lights may indicate different states or modes of ID node 120a (e.g., announcement mode (broadcast), scan mode (listen), current power status, battery level status, associated status, errors, or sensed conditions such as exceeding a temperature threshold, exceeding a humidity threshold, etc.). Other embodiments of the ID node may implement UI 305 in a more sophisticated manner using a graphical display or the like, where such status or mode information and one or more prompts may be displayed.

[0134] In a further embodiment, an exemplary status light used as part of UI 305 as an ID node can also indicate the shipping status. More specifically, the exemplary shipping status can include the status of the shipped item or the status of the item's current shipping journey from its origin to its destination.

[0135] Embodiments may also implement ID node 120a to optionally include one or more sensors 360. In some embodiments, an ID node implemented using one or more sensors 360 may be referred to as a sensor node or a sensor-based ID node. Examples of sensors 360 may include one or more environmental sensors (e.g., pressure, motion, light, temperature, humidity, chemical, radiation, magnetic field, altitude, attitude, orientation, acceleration, etc.) and dedicated location sensors (e.g., GPS sensors, IR sensors, proximity sensors, etc.). Those skilled in the art will appreciate that additional types of sensors measuring other characteristics are conceivable as sensors 360. Additionally, those skilled in the art will understand that sensor nodes or sensor-based ID nodes may include additional procedural features to manage the detection, collection, storage, sharing, and publication of captured sensor data.

[0136] Embodiments may further implement ID node 120a to optionally include one or more magnetic switches 365. Magnetic switches 365, such as reed switches, typically respond to an applied magnetic field to close or open an electrical path or connection. In other words, magnetic switches 365 are actuated by the presence or removal of a magnetic field. As discussed in the embodiments described in more detail below, various applications may relate to the operation of ID node 120a having magnetic switches 365.

[0137] and Figure 3 Consistent with the embodiments shown, exemplary ID node 120a can be based on Texas Instruments CC2540. This is implemented using a low-power (BLE) system-on-chip, which includes various peripherals (e.g., timer circuitry, USB, USART, general-purpose I / O pins, IR interface circuitry, DMA circuitry) to operate as an ID node and, if necessary, interface with different possible sensors and other circuits that make up the ID node (e.g., additional logic chips, relays, magnetic switches).

[0138] In additional embodiments, those skilled in the art will appreciate that similar functionality in the ID node can be implemented in other types of hardware. For example, the ID node 110a can be implemented using specially optimized hardware (e.g., a specific application-specific integrated circuit (ASIC) with the same operational control and functionality as the node control and management code described below, discrete logic, or a combination of hardware and firmware—depending on ID node requirements such as power, processing speed, level of RF characteristic adjustability, number of memory storage units coupled to one or more processors, cost, space, etc.).

[0139] As noted above, ID node 120a includes memory accessible by processing unit 300. Memory storage device 315 and volatile memory 320 are each operatively coupled to processing unit 300. Both memory components provide programming and data elements used by processing unit 300. Figure 3In the illustrated embodiment, memory storage device 315 maintains a wide variety of program code (e.g., node control and management code 325) and other data elements (e.g., profile data 330, security data 335, associated data 340, shared data 345, and sensor data 350, etc.). Memory storage device 315 is a tangible, non-transient computer-readable medium on which information (e.g., executable code / modules, node data, sensor measurements, etc.) can be retained in a non-volatile and non-transient manner. Examples of such memory storage device 315 may include hard disk drives, ROM, flash memory, or other media structures that allow for long-term non-volatile storage of information. Conversely, volatile memory 320 is typically a random access memory (RAM) structure used by processing unit 300 during operation of ID node 120a. When ID node 120a is powered on, volatile memory 320 may be filled with operating programs (such as node control and management code 325) or specific program modules that facilitate specific operations of ID node 120a. Furthermore, during the operation of ID node 120a, volatile memory 320 may also include certain data (e.g., profile data 330, security data 335, associated data 340, shared data 345, sensor data 350, etc.), which is generated when ID node 120a executes instructions such as programming or loading from memory storage device 315. However, those skilled in the art will understand that this is not... Figure 3 All data elements shown in the diagram must appear simultaneously in both memory storage device 315 and volatile memory 320.

[0140] Node control and management code

[0141] Typically, embodiments of node control and management code 325 are collections of software features implemented as programming functions or program modules that typically control the behavior of nodes such as ID node 120a. In embodiments, the functionality of code 325 can generally be similar to that implemented in different types of nodes such as master nodes, ID nodes, and sensor nodes. However, those skilled in the art will appreciate that while some operating principles are similar across such nodes, other embodiments may implement functionality in a degree of specialization or in a different manner depending on the desired application and use of the node. In other words, node control and management code 325 may also include further program code dedicated to the ID node functionality described in the embodiments using ID nodes, which are described in more detail below. Accordingly, the collection of code executing on ID nodes such as ID node 120a (or any other implementation of ID nodes as described herein) is used to programmatically configure the ID node beyond general-purpose processing devices so that, via such program code, the ID node is specifically adapted to operate in unconventional ways—either individually utilizing the specific functionality described herein or as part of a system.

[0142] In a typical embodiment, exemplary node control and management code 325 may typically include several programming functions or program modules, including (1) a node announcement and query (scan) logic manager (also referred to herein as a node communication manager), which manages how and when nodes communicate; (2) an information control and exchange manager, which manages whether and how nodes can exchange information; (3) a node power manager, which manages aspects of power consumption and RF output signal power and / or receiver sensitivity for variable short-range communication; and (4) an association manager, which focuses on how the node associates with other nodes. The following is a description of various embodiments of these basic program modules used by the node.

[0143] Node Communication Manager - Announcements and Scans

[0144] In an exemplary embodiment, the node announcement and query (scan) logic manager governs how and when a node should announce (transmit) its address or query (scan) the addresses of neighboring nodes. Announcements are typically accomplished using messages, which may contain different information in their various parts (e.g., headers, fields, tags, etc.). The message can be a single packet or multiple packets.

[0145] In an exemplary embodiment, the "announcement" mode (as opposed to the "query" or "scan" modes) is the default mode for ID nodes and enables nodes to broadcast or transmit messages containing their address and relevant metadata about the node. For example, in one embodiment, exemplary metadata may include information such as the node's RF output power level, reference designation, status flag, battery level, and manufacturer's name.

[0146] Figure 6 This is a diagram illustrating the structure or format of an exemplary notification data packet according to a general embodiment of the present invention. Referring now... Figure 6 The diagram illustrates the structure of an exemplary announcement data packet 600 broadcast as a signal or message from an ID node (such as ID node 120a). Packet 600 appears at increasingly detailed levels, illustrating exemplary metadata and the format of maintaining different types of metadata in different parts of the packet. Depending on the application deployed on the ID node, different embodiments may include different types of metadata.

[0147] Figure 7 This is a diagram illustrating sample content of an exemplary notification data packet according to an embodiment of the present invention. Referring now... Figure 7 The exemplary notification data packet 700 is illustrated to have exemplary metadata, which includes sample information such as the node's RF output power level (e.g., "TX power level"), reference labels (e.g., "'FDX ID' (short ASCII name)"), status flags (e.g., "status flag value (indicating 'request for confirmation')"), battery level (e.g., "battery level value (indicating 73% charge)"), and manufacturer name (e.g., "company identifier (FedEx, currently undefined)"). In one embodiment, those skilled in the art will appreciate that reference labels may be omitted or obscured for security purposes.

[0148] In one embodiment, an exemplary notification data packet may include an RF output power level, as described above. Figure 7 As shown, this enables a way to help identify the type of node broadcasting and the location of the broadcasting node. However, if the broadcast RF output power level is fixed and known by the node type, only the node type needs to be identifiable from the exemplary advertisement data packets (such as packet 700).

[0149] Regarding how nodes communicate, exemplary nodes can be in one of several different communication modes. A node in advertise (or transmit or broadcast) mode is visible to any other node set to query (or scan or listen) mode. In embodiments, the frequency and length of the advertisers can depend on the application and power. For example, in normal operation, exemplary nodes will typically advertise periodically and expect to establish active connections to other nodes at regular intervals without requiring polling or response prompts from other nodes, which can be determined by conditions set by server 100. In embodiments, such conditions can be set individually for nodes by a server or a higher-level node in the network.

[0150] If an exemplary node does not receive an acknowledgment for an announcement packet within a specific time period, it may enter one or more alarm phases. For example, if an exemplary node does not receive an acknowledgment from another node for an announcement packet broadcast to it within a specific time period (often also referred to as an alarm interval), the exemplary node will enter alarm phase 1. This prompts the exemplary node to issue a follow-up announcement packet, one or more portions of which are modified to indicate the alarm phase 1 state. More specifically, this exemplary follow-up announcement packet may have a different announcement alarm header that instructs nearby nodes to send a SCAN_REQ message upon receiving the announcement packet.

[0151] If the exemplary node does not receive acknowledgment from the master node for the advertisement packet broadcast by that exemplary node within another time period (e.g., an active connection request and a successful connection from the master node), it will enter another alert phase, such as Alert Phase 2 state. This prompts the exemplary node to issue a follow-up advertisement packet, one or more portions of which are modified to indicate the Alert Phase 2 state. More specifically, this exemplary follow-up advertisement packet may have a different advertisement alert header that instructs a nearby master node to send a SCAN_REQ message upon receiving the advertisement packet.

[0152] If the exemplary node has data to upload to the backend, it can also enter another type of alarm phase. In one embodiment, for example, if the exemplary node has sensor data collected by the exemplary node (or sensor data received from one or more other nodes that are already communicating with the exemplary node), and that data needs to be uploaded to server 100, the exemplary node can enter an update alarm phase, such as alarm phase 3. This prompts the exemplary node to issue a follow-up notification packet, one or more portions of which are modified to indicate the alarm phase 3 status. More specifically, the exemplary follow-up notification packet may have a different notification alarm header that instructs a nearby master node to connect to the exemplary node so that data (e.g., sensor data 350) can be transferred from the exemplary node (e.g., ID node 120a) to a nearby master node (e.g., master node 110a). The transferred data can then be stored by the nearby master node as sensor data 450 in one or both of the master node's volatile memory 420 and memory storage device 415. After the storage operation, the nearby master node transmits the data (e.g., sensor data 450) to server 100.

[0153] like Figure 7 As illustrated in the diagram and explained in the above description of the alert level stages, in one or more embodiments, the status flag in the header of the exemplary notification data packet is a field used in the association logic. For example, in one embodiment, the presence of the status flag in the notification data packet allows a first node to communicate its status to a second node and allows the second node to report that status to a backend server (such as server 100) without an active direct connection from the first node to the server. In other words, the status flag helps facilitate passive interactions (such as passive associations) between nodes.

[0154] In a more detailed embodiment, several exemplary state types are established for communication with other nodes. For example, exemplary state types may include the following:

[0155] Alarm level 0 - No problem, operation is normal;

[0156] Alert Level 1 - The announcing node is requesting confirmation from any available node that it has received its announcing data packets;

[0157] Alert Level 2 - The announcing node is requesting confirmation from any available master node that it has received its announcing data packets;

[0158] Alert Level 3 - Upload Data – The node has captured data that can be uploaded via the master node; and

[0159] • Synchronization - Announcement nodes request to connect to devices or sensors that can synchronize data (such as timers or location information).

[0160] By broadcasting the status via, for example, a portion of the header in an announcement data packet, one or more nodes within the broadcast node range can determine the status of a node and, if requested in a status message, initiate an active connection.

[0161] In some embodiments, a request for more information from the advertising node may appear in the form of a SCAN_REQ message. Generally, an exemplary SCAN_REQ is a message sent from the scanning (listening) master node to the advertising node, requesting additional information from the advertising node. In this example, an alarm status bit may, for example, at the application layer, indicate to the scanning master node whether the advertising node is in a mode that will accept or not accept the SCAN_REQ. In one embodiment, the node advertising's unconnectable and discoverable modes conform to... Low Energy (BLE) standard.

[0162] In another embodiment, a node may have further different operating modes when scanning or listening to other nodes. For example, a node's query or scan mode can be active or passive. When a node scans in passive mode, it will receive advertisement data packets but will not acknowledge or send a SCAN_REQ. However, when a node scans in active mode, it will receive advertisement data packets and will acknowledge receipt by sending a SCAN_REQ. More detailed embodiments may be provided that conform to... Passive and active scanning or polling modes of the Low Energy (BLE) standard.

[0163] In this embodiment, the exemplary node is scanning because it is listening to other wireless nodes broadcasting on short-range radio. Such a scan can take the form of monitoring spontaneous signal broadcasts from other wireless nodes. The exemplary scanning node may capture, for example, the MAC address of the announcing node, the signal strength of the RF output signal transmitted from the announcing node, and any other metadata published by the announcing node (e.g., other information in the announcing data packets). Those skilled in the art will appreciate that the scope of "listening" can vary when a node is scanning. For example, the query may be limited. In other words, the scope that the node is particularly interested in and is listening to may be focused or otherwise limited. In such cases, for example, the information collected may be limited to specific information announced by short-range wireless nodes from a target group; however, information collection can be considered "open," where information is collected from any announcing device.

[0164] While a node is announcing or scanning, the embodiment may further utilize status flags and additional modes as part of how the node communicates and can be managed. In one example, when a scanning (listening) node receives an announcement data packet with a status flag indicating an alarm level of 1 or 2, and the scanning node is in "passive" scanning mode, it will switch to "active" scanning mode at certain intervals. However, if the scanning node is already in "active" scanning mode, it will send a SCAN_REQ message and receive a SCAN_RSP (e.g., a message providing additional information requested from the announcing node) from the announcing node. The scanning node will then switch back to "passive" scanning mode.

[0165] In another example, when an advertising (broadcasting) node receives a SCAN_REQ from a scanning node, the advertising node considers its advertising data packet to have been acknowledged. Furthermore, the advertising node resets its "alarm" status flag back to alarm level 0. This allows the advertising node to efficiently receive acknowledgments of its advertising without ever establishing a connection with the scanning node, which advantageously and significantly saves power.

[0166] In another example, when a scanning node receives an announcement data packet with an alarm level 3 status flag set, the scanning node will attempt to connect to the announcement device. Once the connection is established, the announcement device will attempt to upload its data to the connected device.

[0167] Therefore, an embodiment of the node announcement and query (scan) logic manager of code 325 can rely on one or more status flags, announcement modes, and scan modes, because nodes communicate with each other in a variety of advantageous ways.

[0168] Node Information Control and Exchange Manager

[0169] In an exemplary embodiment, the information control and exchange manager portion of node control and management code 325 determines whether and how information can be exchanged between nodes. In an exemplary embodiment, the information control and exchange manager establishes different node operating states, where information can be modified according to the desired paradigm of the state. More specifically, embodiments of the information control and exchange manager can establish different levels of information exchange between nodes having a "disconnectable announcement" state or operating mode, a "discoverable announcement" state or mode, and a "general announcement" state or operating mode. When a node is in the "disconnectable announcement" mode, node information exchange is restricted. For example, an announcing node may broadcast information captured by one or more querying (scanning) nodes, but bidirectional information exchange does not occur.

[0170] When a node is in "discoverable and advertised" mode and a scanning node is in "active" mode, node information exchange is enabled in both directions. For example, the advertising node sends an advertisement packet, and in response, the scanning node sends a SCAN_REQ packet. After receiving the SCAN_REQ requesting additional information, the advertising node sends a SCAN_RSP containing the requested information. Therefore, in "discoverable and advertised" mode, there is bidirectional information exchange, but no active connection is established between the two nodes exchanging information.

[0171] Finally, for advanced bidirectional information exchange, active connections can be used between nodes, allowing information to be exchanged in both directions, to and from different nodes. In a more detailed embodiment, at this level of bidirectional information exchange, nodes are first identified and then authenticated as part of establishing an active connection. Once authenticated and subsequently actively connected to each other, nodes can securely share information back and forth. In one example, a sensor node uploading previously captured environmental information to the master node may be in this mode or state. In another example, an ID node uploading the stored results of a node scan operation to the master node may be in this mode or state. In yet another example, a master node sharing timer and / or location information with corresponding nodes may be in this mode or state.

[0172] Node Power Manager

[0173] In an exemplary embodiment, the node power manager portion of node control and management code 325 focuses on managing power consumption and the advantageous use of power within the node (e.g., adjustable levels of RF output signal power). Generally, a node is powered either by a battery (such as battery 355 in an ID node) or by an interface to an external power source (such as battery / power interface 470 in a master node). In some embodiments, examples of external power sources may include power supplied from a receptacle or power connection within the facility, or power generated onboard by a means of transportation (e.g., a car, truck, train, airplane, ship, etc.). Those skilled in the art will appreciate that the interface to the external power source will generally be referred to as a “wired” power connection, and the node power manager can be informed whether the node is wired or powered by a battery (such as battery 355). Further embodiments may utilize wireless power transmission, such as via an induction coil, to implement the interface to the external power source.

[0174] In one embodiment, a node can manage the power used when performing a task. For example, a node can manage power when determining which node should perform a specific task. More specifically, the total power consumption of a group of devices can be managed by selecting wired nodes to perform specific tasks when feasible or desired, and saving battery-powered nodes for other less energy-intensive or less strenuous tasks. In another embodiment, historical data can inform the system of the power required to complete a specific task, and the system can determine which node should perform the specific task based on such historical data. In other embodiments, profile data (e.g., a sensor profile describing the power requirements of a sensor node that collects sensor data within a specific time period and under specific conditions) can also be used to inform the system of the power required to complete a specific task. The system can also determine which node should perform the specific task based on such profile data.

[0175] In another example, an exemplary node power manager can manage power when determining how best to use and adjust power to more accurately accomplish a specific task. In one embodiment, the RF signal output from a node (such as a short-range RF output signal from an ID node) can periodically move within a range of output power, or simply switch between two or more settings that differ in a detectable manner. As disclosed in more detail below, the variability and dynamic adjustment of the RF output signal power can allow other nodes (such as one or more master nodes) to see each node at a higher range of RF output signal power and only see nodes physically close to the advertised node at a lower range of signal power.

[0176] In another example, when a node is already associated with a physical location or another node using context data (such as context data 560 and association logic utilizing this type of information), an exemplary node power manager can cause a change in the characteristics of its RF output signal power. In one embodiment, the node may be instructed to change how frequently it communicates and / or the characteristics of its RF output power to conserve power.

[0177] In yet another example, all advertising nodes can have their respective node power managers periodically cause each corresponding node to broadcast at its maximum RF output signal power level, ensuring they remain within range of the scan ID node or master node. This increases the chances of being within communication range and allows for proper location and management of individual nodes within the network. The broadcast duration can be set or dynamically changed if needed to allow pairing to occur.

[0178] In some embodiments, an exemplary node power manager can adjust the node's RF receiver sensitivity rather than adjusting the RF output signal power level. This allows for adjustable reception range (as opposed to only adjustable broadcast range), which can be similarly used to manage power and enhance location determination, as discussed herein.

[0179] In yet another embodiment, a combined approach can be used, in which a node power manager can simultaneously and independently adjust the RF characteristics of more than one node. For example, an exemplary node power manager can adjust the RF output signal power level and, when a node is located and associated with other nodes, also adjust the node's RF receiver sensitivity. Those skilled in the art will recognize that this is particularly useful in areas with exceptionally dense node concentrations and in combinations of altered RF output signal power levels.

[0180] When adjusting the power characteristics of a node (e.g., power consumption, power usage, output signal frequency, output signal duty cycle, timing, power level, etc.), an exemplary embodiment of the node manager may refer to a power profile (e.g., profile data 330, 430 of exemplary type).

[0181] Node Association Manager

[0182] In an exemplary embodiment, the node association manager portion of node control and management code 325 focuses on how a node associates itself with other nodes in a combined and consistent manner with the server-side association manager in code 525, as discussed in more detail below. Therefore, when executed in a node, the exemplary node association manager uses input from the server to guide how the node associates with one or more other nodes (e.g., entering an active connection mode or generating association data reflecting temporary logical connections).

[0183] An exemplary node association manager can indicate through status flags whether a node requires acknowledgment or connection, or whether it has information that can be uploaded to the backend. Therefore, although a node may not yet be associated with or actively connected to another node, its status can be inferred from, for example, the status information in the node's broadcast header.

[0184] Regarding connections between nodes, secure and insecure connections are typically present. While embodiments may allow insecure connections between one or more groups of nodes, other embodiments rely on secure connections or authenticated pairing of nodes. In one embodiment, to pair a node with another node, an exemplary node association manager first identifies the node to be associated and sends an association request to a server. This request may include a specific request to pair the nodes and request corresponding pairing credentials from a server such as server 100. Such pairing can be considered a logical pairing of nodes, which can be tracked by server 100 (or other nodes in the network, such as master nodes, command nodes, external transceivers, or remote control centers located outside the delivery vehicle). Server 100 may have tiered pairing credentials on a particular node based on information indicating that the node will be within wireless proximity and that future pairing is likely. The visibility of node relationships may have been determined by scan notifications or third-party data (such as barcode scan information) indicating that the node is currently or in the future within proximity.

[0185] As described in more detail below, associated nodes may involve the local generation of associated data (e.g., associated data 340, 440, etc.) that reflects the logical pairings between associated nodes. Accordingly, the associated data can be manipulated as temporal data indicating logical connections between nodes, regardless of whether the nodes are actually communicating with each other.

[0186] When connecting or disconnecting to exchange information in the above exemplary node information exchange mode, the node typically operates in multiple states, which constitute the exemplary announcement cycle of the exemplary ID node. See below for reference. Figure 8 Furthermore, this exemplary notification cycle of nodes is further explained in conjunction with the server-side association manager in code 525, as discussed in more detail below.

[0187] Air transport mode program module

[0188] In one embodiment, node control and management code 325 may further include an air transport mode program module (not shown). In another embodiment, the air transport mode program module may be implemented as part of a node power manager program module of code 325. An exemplary air transport mode program module typically operates to manage the output power of the ID node's variable power short-range communication interface 375 when the ID node is operating in an aircraft. In some cases, operating wireless devices within an aircraft may have unintended effects on other electronic systems on the aircraft. More specifically, embodiments of the air transport mode program module may operate to switch the ID node from different states or modes depending on the specific operation and / or operating conditions of the aircraft. For example, an exemplary air transport mode program module may operate to switch the ID node from a state or mode (e.g., normal mode before takeoff, disabled mode during takeoff, air transport mode at high altitude, disabled mode during descent, and normal mode after landing) based on detected environmental conditions (e.g., pressure, altitude) and / or flight details associated with the aircraft. In this way, ID nodes can be allowed to operate normally while on an aircraft, or in some cases completely disabled, and can operate in aircraft modes that allow sensing and sensor data capture, but may limit the transmission of RF output signals to avoid interfering with the aircraft's avionics. Further information relating to methods for managing wireless devices (such as ID nodes) in an aircraft is disclosed in more detail in U.S. Patent Application Serial No. 12 / 761,963 entitled "System and Method for Management of Wireless Devices Aboard an Aircraft" (which is hereby incorporated by reference).

[0189] Node data

[0190] As previously noted, the volatile memory 320 may also include certain data (e.g., profile data 330, security data 335, associated data 340, shared data 345, sensor data, etc.) generated when the ID node 120a executes instructions such as those programmed or loaded from the memory storage device 315. Generally, data used on a node such as the ID node can be received from other nodes or generated by that node during operation.

[0191] In one embodiment, profile data 330 is a data type that defines the general behavioral types of the ID node, such as broadcast profiles (discussed in more detail below). In another embodiment where ID node 120a is a BLE device, profile data 330 may include information related to battery services (exposing the state of the battery within the device), proximity between BLE devices, or messaging between BLE devices. Compatible profile. Therefore, exemplary profile data 330 can exist as a data type defining node behavior parameters in volatile memory 320 and / or memory storage device 315.

[0192] In one embodiment, it may be desirable to allow secure pairing of nodes. As will be explained in more detail below, as part of secure pairing of nodes, a request to generate pairing credentials is sent to server 100. Thus, exemplary security data 335 (e.g., PIN data, security credentials, keys, etc.) may exist as a data type associated with providing a secure relationship between nodes (such as the requested security credentials) in volatile memory 320 and / or memory storage device 315.

[0193] Association data, such as association data 340, typically identifies the connection relationship between nodes. Such a connection can be an interactive exchange type of connection, but other embodiments may reflect a purely logical connection between nodes. For example, when ID node 120a moves within the range of master node 110a, and after the server initiates an association (with authorization) between the two nodes, ID node 120a may become associated with master node 110a. As a result, information identifying the relationship between ID node 120a and master node 110a can be provided to server 100, and at some point can be provided to each of ID node 120a and master node 110a. Therefore, exemplary association data 340 can exist as a data type identifying the association between nodes in volatile memory 320 and / or memory storage device 315. In another example, ID node 120a can detect an announcement signal broadcast from master node 110a without prompting master node 110a to broadcast such a signal (e.g., a spontaneous broadcast or non-polling association signal from master node 110a). In this scenario, even without a response from the master node 110a, the ID node 120a can passively associate with the master node 110a and generate association data 340 on the ID node 120a that reflects the logical relationship or connection between the ID node 120a and the master node 110a. This association data can be passed to the server 100, allowing the server to track which nodes are logically associated with the ID node 120a.

[0194] Shared data 345 can exist in volatile memory 320 and / or memory storage device 315 as a data type that can be exchanged between nodes. For example, context data (such as environmental data) can be one type of shared data 345.

[0195] Sensor data 350 may also exist as a data type recorded and collected from onboard sensors or from another node in volatile memory 320 and / or memory storage device 315. For example, sensor data 350 may include temperature readings from a temperature sensor on an ID node and / or from another ID node (e.g., from another ID node inside container 210, such as...). Figure 2 The humidity reading of the humidity sensor shown in the figure.

[0196] Therefore, ID nodes (such as Figure 3 The node 120a) shown is a low-cost wireless node that communicates with other ID nodes and master nodes via a short-range radio with variable RF characteristics. It can associate with other nodes, broadcast to and scan for other nodes, associate with other nodes, and store / exchange information with other nodes.

[0197] Master node

[0198] Master node (such as) Figure 4 The master node 110a, shown in more detail below, shares many ID node characteristics, but typically extends them to act as a bridge to higher-level network elements, such as server 100. Generally, while ID nodes are a lower-level type of node in the exemplary wireless node network, master nodes are a higher-level type of node (also referred to as mid-level network devices). Exemplary master nodes may be located in a fixed position or otherwise stationary, while other exemplary master nodes may be implemented as mobile and movable devices. As will be further explained below, one type of master node may include a command node that may be part of or attached to a shipping container, such as a ULD container.

[0199] Now for reference Figure 4 An exemplary master node 110a includes a processing or logic unit 400 coupled to a short-range communication interface 480, a memory storage device 415, a volatile memory 420, a clock / timer 460, and a battery / power interface 470. In some embodiments, the short-range communication interface 480 may have variable power characteristics, such as receiver sensitivity and RF output power levels. Those skilled in the art will appreciate that the processing unit 400 is logic such as a microprocessor or microcontroller, which typically performs calculations on data and executes operational and application code, as well as other program modules within the master node 110a.

[0200] Generally speaking, those skilled in the art should understand that, regarding Figure 4The hardware description of ID node 110a applies to similar hardware and software features present in every type of node, including master nodes. Those skilled in the art will appreciate that the exemplary master node 110a is a hardware-based component that, depending on the desired implementation, may utilize a single processor or logic unit, a more powerful multi-core processor, or multiple processors to implement processor 400. In one embodiment, processing unit 400 may be implemented using a low-power microprocessor and associated peripheral circuitry. Less complex microcontrollers or discrete circuitry may be used to implement processing unit 400, as well as more complex and sophisticated general-purpose or special-purpose processors.

[0201] In yet another embodiment, the exemplary processing unit 400 may be implemented by a low-power ARM1176JZ-F application processor used as part of a single-board computer such as the Raspberry Pi computer model B-Rev-2. The ARM application processor is embedded in the Raspberry Pi computer. In the BCM2835 System-on-Chip (SoC), a Raspberry Pi computer device operates as the core of an exemplary master node 110a and includes a Secure Digital Memory Card slot and a Flash Memory Card operating as a memory storage device 415, a 512-megabyte RAM memory storage device operating as volatile memory 420, an operating system (such as Linux) stored on the memory storage device 415 and running in the volatile memory 420, peripherals implementing a clock / timer 460, and a power supply operating as a power interface 470.

[0202] Like the short-range interface 375 in ID node 120a, the exemplary master node 110a includes a short-range communication interface 480 as a programmable radio and omnidirectional antenna coupled to the processing unit 400. In some embodiments, the short-range communication interface 480 may have variable RF power characteristics, such as receiver sensitivity and / or RF output signal power levels. In some embodiments, the interface 480 may use antennas with different antenna profiles when directivity may be desired. Those skilled in the art will appreciate that the short-range communication interface 480 (as described above with respect to interface 375) can be implemented using hardware, a combination of hardware and software, and as a software-defined radio (SDR). Examples of the short-range communication interface 480 may include additional hardware (not shown) for operatively coupling a device to a particular short-range communication path (e.g., Low-power (BLE) connectivity path (communication at 2.4 GHz). While BLE is used in one embodiment to enable a short-range communication protocol, the variable-power short-range interface 480 can utilize other low-power short-range communication protocols, such as the ultra-low-power communication protocol used with ultra-wideband pulse radio communication, the Purple Bee protocol, and the IEEE 802.15.4 standard communication protocol.

[0203] In one embodiment, various RF characteristics of the radio transceiver, such as RF output power and RF receiver sensitivity, can be dynamically and programmatically varied under the control of processing unit 400. In other embodiments, further RF characteristics of the radio transceiver, such as frequency, duty cycle, timing, modulation scheme, spread spectrum frequency hopping, etc., can be programmatically varied as needed, depending on the desired implementation and intended use of the exemplary master node 110a, to flexibly adjust the RF output signal as required. In other words, embodiments of master node 110a (or any other master node) can have programmably adjustable RF characteristics (such as adjustable RF output signal power, adjustable RF receiver sensitivity, the ability to switch to different frequencies or bands, etc.).

[0204] In addition to the short-range communication interface 480, the exemplary master node 110a includes a medium-range and / or long-range communication interface 485 to provide a communication path to the server 100 via the network 105. Those skilled in the art will appreciate that in some embodiments, the deployed exemplary communication interfaces can be considered to embody either a short-range communication interface (such as interface 480) or a medium-range / long-range communication interface (such as interface 485). However, in more general embodiments, references to communication interfaces may include interfaces that collectively implement multiple different exemplary data communication interfaces, while still generally being referred to as "communication interfaces" or "wireless communication interfaces." Furthermore, those skilled in the art will appreciate that communication interface 485 can be implemented using hardware, a combination of hardware and software, and as a software-defined radio (SDR).

[0205] More specifically, an exemplary embodiment of the communication interface 485 may be implemented using a mid-range radio in the form of an IEEE 802.11g conforming to a Wi-Fi transceiver. In another embodiment, the communication interface 485 may be implemented using a longer-range radio in the form of a cellular radio. In yet another embodiment, both the Wi-Fi transceiver and the cellular radio may be used when optimally available or according to priority (e.g., if available, the Wi-Fi transceiver may be used first due to potentially lower costs; and if not, the cellular radio may be relied upon). In other words, embodiments may rely on the longer-range cellular radio portion of the interface 485 as an alternative to the mid-range Wi-Fi transceiver radio, or when the mid-range radio is outside the range of the connectivity infrastructure radio within network 105. In a further embodiment, the interface 485 may be implemented as a module providing general signal processing at its core as part of a software-defined radio, which provides flexibility in terms of transmission technologies, software-defined antennas, and adaptive radio protocols that can be dynamically changed to implement different mid-range and longer-range interfaces. Therefore, in these embodiments, the medium-range and / or long-range communication interface 485 can be used to communicate captured node information (e.g., profile data 430, association data 440, shared data 445, sensor data 450, and location data 455) to the server 100.

[0206] In any of the embodiments described herein, communication interfaces 480 and 485 can be implemented as a single transceiver-based communication interface with both short-range and long-range communication capabilities (i.e., can act as both the first and second communication interfaces, as described in the various embodiments herein). Wider-range communication interfaces of this type can be implemented using LPWAN (Low Power Wide Area Network) connectivity such as LTE 5G, LTE-M, and NB-IoT (Narrowband IoT). LPWAN, often also referred to as Low Power Wide Area (LPWA) networks or Low Power Only (LPN) networks, is a type of wide area network wireless communication format that allows extended-range, low-bandwidth communication for power-sensitive applications such as devices utilizing battery-powered equipment (e.g., ID nodes, mobile master nodes, container nodes, and command nodes). Exemplary types of LPWANs may include Ultra Narrowband (UNB) technology from Sigfox, Random Phase Multiple Access (RPMA) technology from Ingenu, and other Long Range WAN protocols (LoRaWAN) technologies promoted by LoRa Alliance companies (e.g., IBM, Microchip, Cisco, Semtech, Singtel, KPN, Bouygues Telecom). LTE-M is a communication technology that allows node-based devices (such as sensor-based ID nodes or command nodes) to connect directly to Long Term Evolution (4G) cellular networks without gateways and reliance on batteries. NB-IoT is a low-power communication technology that applies a narrowband approach to cellular IoT (Internet of Things) communications, allowing the use of a portion of the GSM spectrum bandwidth in the unused 200kHz band.

[0207] The battery / power interface 470 of master node 110a typically powers the circuitry that implements master node 110a. In one embodiment, battery / power interface 470 may be a rechargeable power source. For example, the master node may have a rechargeable power source along with a solar panel for charging, which may help facilitate deployment of the master node in a remote location. In another embodiment, battery / power interface 470 may be a non-rechargeable power source intended for disposal after use. In yet another embodiment, battery / power interface 470 may be a power interface connector (such as a power cord and internal power source on master node 110a). Thus, when the exemplary master node is in a fixed or stationary configuration, it may be powered by a power cord connected to a power outlet coupled to an external power source. However, other mobile master nodes may use an internal power source, such as a battery.

[0208] The clock / timer 460 of the master node 110a typically provides one or more timing circuits used in applications such as time delay, pulse generation, and oscillator. In embodiments where the master node 110a saves power by entering a sleep or hibernation state for a predetermined period of time (as part of an overall power-saving technique), the clock / timer 460 auxiliary processing unit 400 manages the timing operations.

[0209] Alternatively, embodiments may also implement the master node 110a as including one or more sensors 465 (similar to sensor nodes deployed on ID-based nodes and referenced thereon). Figure 3 (The sensor described herein). Additionally, embodiments of master node 110a may also provide a user interface 405 to indicate status and allow basic interaction for viewing captured node data and interaction with nodes and server 100. In one embodiment, user interface 405 may provide a display, interactive buttons or soft keys, and pointing devices to facilitate interaction with the display. In a further embodiment, a data input device may also be used as part of user interface 405. In other embodiments, user interface 405 may take the form of one or more lights (e.g., status lights), auditory input and output devices (e.g., microphones and speakers), or a touchscreen.

[0210] As previously noted, an exemplary master node such as master node 110a may be located in a known fixed location, or alternatively, may include dedicated location positioning circuitry 475 (e.g., GPS circuitry) to allow the master node to determine its location itself or by itself. In other embodiments, positioning circuitry 475 (instead of GPS) may rely on alternative circuitry and techniques, such as positioning circuitry compatible with other satellite-based systems (e.g., the European Galileo system, the Russian GLONASS system, the Chinese BeiDou system), terrestrial radio-based positioning systems (e.g., cellular tower-based or Wi-Fi-based systems), infrared positioning systems, visible light-based positioning systems, and ultrasonic-based positioning systems.

[0211] Regarding memory storage device 415 and volatile memory 420, both are operatively coupled to processing unit 400 in exemplary master node 110a. Both memory components provide program elements used by processing unit 400 and maintain and store data elements accessible to processing unit 400 (similar to possible data elements stored in memory storage device 315 and volatile memory 320 in exemplary ID node 120a).

[0212] exist Figure 4In the illustrated embodiment, memory storage device 415 maintains a wide variety of executable program code (e.g., master control and management code 425), similar to the data held in memory storage device 315 of the ID node (e.g., profile data 430, security data 435, association data 440, shared data 445, sensor data 450, etc.), as well as other data more specifically related to the operation of master node 110a (e.g., location data 455 associated with the location of a particular node). Like memory storage device 315, memory storage device 415 is a tangible, non-transient computer-readable medium on which information (e.g., executable code / modules, node data, sensor measurements, etc.) can be held in a non-volatile and non-transitory manner.

[0213] Like the volatile memory 320 in ID node 120a, the volatile memory 420 is typically a random access memory (RAM) structure used by processing unit 400 during operation of master node 110a. When master node 110a is powered on, volatile memory 420 may be filled with operating programs (such as master control and management code 425) or specific program modules that facilitate specific operations of master node 110a. Furthermore, during operation of master node 110a, volatile memory 420 may also include certain data (e.g., profile data 430, security data 435, association data 440, shared data 445, sensor data 450, etc.) generated when master node 110a executes instructions such as those programmed or loaded from memory storage device 415.

[0214] Main control and management code

[0215] Typically, embodiments of the master control and management code 425 are collections of software features implemented as program functions or program modules that typically control the behavior of a master node, such as master node 110a. In other words, the master control and management code 425 may also include further program code specifically for using the master node functions (e.g., command node 26000 or command node 24160 implemented using the master node) as described in the embodiments described in more detail below. Accordingly, the collection of code executing on a master node such as master node 110a (or any other implementation of a master node or command node as described herein) is used to programmatically configure the master node or command node to go beyond general-purpose processing devices, so that, via such program code, the master node or command node is specifically adapted to operate in a non-conventional manner—either individually or as part of a system using the specific functions described herein.

[0216] In one embodiment, the master control and management code 425 typically includes several programming functions or program modules, including (1) a node announcement and query (scan) logic manager that manages how and when nodes communicate; (2) an information control and exchange manager that manages whether and how nodes can exchange information; (3) a node power manager that manages aspects of power consumption and RF output signal power and / or receiver sensitivity for variable short-range communication; (4) an association manager that focuses on how nodes associate with other nodes; and (5) a location awareness / capture module for determining node locations.

[0217] Master node program module and ID node module

[0218] In an exemplary embodiment, the program modules (1)-(4) of the master node control and management code 425 are typically referenced above. Figure 3 The described node control and management code 325 is functionally aligned with similarly named program modules (1)-(4). Additionally, since node control and management code 325 may also include an air transport mode program module, those skilled in the art will appreciate and understand that master node control and management code 425 may also include a similarly functional air transport mode program module to allow for advantageous operation of the master node during air transport. However, and consistent with the examples set forth below, such modules may differ somewhat from those used to control ID nodes when in the master node.

[0219] Position awareness / capture module

[0220] In addition to the exemplary program modules (1)-(4) of code 425, exemplary embodiments of master node control and management code 425 will further include an exemplary location-aware / capture module (more generally referred to as the master node's location manager module) related to node location. Generally, the exemplary location-aware / capture module deployed in the exemplary master node can determine its own location, and in some embodiments, determine the location of connected nodes. When determining the node location of other nodes, embodiments of the exemplary location-aware / capture module may work in conjunction with location manager program code residing in and operating on the server (e.g., as part of server control and management code 525), as discussed in more detail herein.

[0221] In one embodiment, the master node may be located in a known fixed location. In such an embodiment, an exemplary location awareness / capture module may sense that the master node's location is a known fixed location, which may be defined in a fixed, preset, or pre-programmed portion of the memory storage device 415 (e.g., information maintained in location data 455 in the memory storage device 415). Examples of such location information may include conventional location coordinates or other descriptive details identifying the master node's location. In another embodiment, where the master node may not be inherently known or is not always in a fixed location (e.g., for a mobile master node), the exemplary location awareness / capture module may communicate with positioning circuitry (such as GPS circuitry 475 on the master node) to determine the master node's current location.

[0222] In this embodiment, the location of the master node can be communicated to a server, which can use this location information as part of managing and tracking nodes in the wireless node network. For example, if the exemplary master node is mobile and has already determined a new current location using positioning circuitry 475, the master node can provide this new current location to the server. Additionally, when the exemplary location sensing / capture module of the master node determines the location of a node associated with the master node, the master node can also provide the server with the location of that associated node.

[0223] server

[0224] Although Figure 3 and Figure 4 The illustrations depict the hardware and software details of an exemplary ID node and an exemplary master node, respectively. Figure 5 More detailed diagrams are provided of an exemplary server that can operate as part of an exemplary wireless node network according to embodiments of the present invention. In an exemplary embodiment, server 100 may be referred to as an Association and Data Management Server (ADMS), which manages nodes, collects information from nodes, stores information collected from nodes, maintains or accesses contextual data related to the environment in which nodes are operating, and can provide information about nodes (e.g., status, sensor information, etc.) to requesting entities. Further details of various embodiments utilizing this functionality are explained below. Those skilled in the art will appreciate that node density, geographic installation characteristics, and network connectivity are all types of examples of factors that may influence the final architecture desired by embodiments of the wireless node network.

[0225] Now for reference Figure 5The exemplary server 100 is shown as a networked computing platform capable of connecting to and interacting with at least one wireless master node. In other embodiments, the exemplary server 100 may also connect to and interact with one or more user access devices. Those skilled in the art will appreciate that the exemplary server 100 is a hardware-based component that can be implemented in a variety of ways. For example, server 100 may use a single processor or may be implemented as one or more portions of a multiprocessor component that communicates with devices (such as user access devices 200, 205) and wireless nodes (such as master node 110a).

[0226] Generally, those skilled in the art will further appreciate that server 100 can be implemented as a single computing system, a distributed server (e.g., a single server for a single server-related task), a hierarchical server (e.g., a server implemented at multiple levels, where information can be maintained at different levels and, depending on the implementation, tasks are performed at different levels), or, from the perspective of a client device, a server cluster (e.g., devices 200, 205, or master node 110a) that logically allows multiple different components to act as a single server computing platform device. In some regional deployments, exemplary servers may include servers dedicated to a specific geographic region, as information collected in different regions may include and be subject to different regulatory controls and requirements implemented on the respective regional servers.

[0227] Similarly, although Figure 5 The embodiment shown illustrates a single memory storage device 515, but the exemplary server 100 may deploy more than one memory storage medium. Furthermore, the memory storage medium can be in various non-transitory forms (e.g., conventional hard disk drives, solid-state drives, flash memory, optical drives, RAID systems, cloud storage configuration storage, network storage devices, etc.).

[0228] At its core, Figure 5 The exemplary server 100 shown includes a processing or logic unit 500 coupled to a network interface 590, which facilitates and enables operational connections and communications via network 105 with one or more master nodes and, in some embodiments, with user access devices such as devices 200, 205. In one embodiment, server 100 may include a mid-range and / or long-range communication interface 595 used thereto for more direct communication with one or more master nodes. Using these communication paths and program code or program modules (such as server control and management code 525), server 100 typically operates to coordinate and manage information associated with the ID node when items associated with the ID node are physically moved from one location to another.

[0229] As a computing platform, the processing unit 500 of the exemplary server 100 is operatively coupled to a memory storage device 515 and a volatile memory 520, which together store and provide a variety of executable program code (e.g., server control and management code 525), similar to data (e.g., profile data 530, security data 535, associated data 540, shared data 545, sensor data 550, location data 555) and contextual data 560 (e.g., information generated within the wireless node network and information created outside the wireless node network) that are held in the corresponding memory storage device of the master node or ID node.

[0230] Like memory storage devices 315 and 415, memory storage device 515 is a tangible, non-transient computer-readable medium on which information (e.g., executable code / modules (e.g., server control and management code 525), node-related data (e.g., profile data 530, security data 535, association data 540, location data 555, etc.), measurement information (e.g., a type of shared data 545, sensor data 550, etc.) and information about the node's context (e.g., context data 560)) can be maintained in a non-volatile and non-transient manner.

[0231] Those skilled in the art will understand that the above identifiers of specific program code and data are not exhaustive, and embodiments may include further executable program code or modules and other data related to the operation of processing-based devices such as ID nodes, master nodes, and servers.

[0232] Context data

[0233] As noted above, server 100, as part of managing nodes in a wireless node network, can access context data 560. According to an embodiment, exemplary server 100 may contain a collection of such context data 560 in a context database 565. Figure 5As illustrated, the exemplary context database 565 is a single database accessible by the processing unit 500 within server 100. Those skilled in the art will readily understand that other configurations providing an accessible set of context data 560 are possible and conceivable within the scope and principles of these embodiments. For example, context database 565 may be an externally accessible database (or multiple databases), such as an accessible storage device maintained outside server 100 via a dedicated interface or network storage device (or network attached storage (NAS) unit). In yet another embodiment, the context database may be maintained separately by an external database server (not shown) different from server 100, but accessible via a communication path from server 100 to the separate database server (e.g., via network 105). Furthermore, those skilled in the art will appreciate that context database 565 can be implemented using cloud technology, which essentially provides distributed networked storage of a set of information accessible to server 100, such as context data 560, sensor data 550, shared data 545, etc.

[0234] Within the context database 565, an exemplary embodiment may maintain a collection of context data 560, which typically relates to the environment in which a node is operating or is expected to operate. More specifically, the context data 560 may typically relate to things experienced by similar nodes in similar environments, things that a given node is currently experiencing, or things that a given node is expected to experience when it moves.

[0235] In a typical example, the environment in which a node may actually operate or is expected to operate can include different types of environments—for example, an electronic communication environment (e.g., an RF environment that may be signal-laden or include materials or structures that may impede or otherwise shield RF communication), the physical environment of the expected path along with the identified node movement (e.g., temperature, humidity, security, and other physical characteristics), the transportation environment related to how the node can or is expected to move (e.g., the speed and other parameters of trucks, airplanes, conveyor systems), and the density environment related to the node density in the area near a particular node (e.g., how many nodes are expected to occupy a corridor, such as...). Figure 22 The structure 2200 shown in A, or the expected specific ID node will be transported through the storage facility it is being shipped to on its shipping path.

[0236] Given these different aspects of the operating environment of the nodes, exemplary context data 560 can provide information related to different structures and conditions concerning the movement of items (e.g., specific types of delivery equipment, vehicles, facilities, shipping containers, etc.). Such information can be generated by entities operating the wireless node network (such as shipping companies). Additionally, exemplary context data 560 can include third-party data generated outside the wireless node network. Therefore, according to embodiments of the invention, context data such as data 560 can include a wide variety of data generally related to the environment in which the node is operating, and can be used to advantageously provide enhanced node management capabilities.

[0237] Generally speaking, Figure 5 The illustration shows exemplary types of context data 560 maintained in database 565 and volatile memory 520. Those skilled in the art will appreciate that, in addition to maintaining such information in a database, or instead of maintaining such information in a database, context data 560 can also be maintained in other data structures. For example... Figure 5 As illustrated in the diagram, the exemplary type of context data 560 may include, but is not limited to, scan data 570, historical data 575, shipping data 580, layout data 585, RF data 587, and third-party data.

[0238] Scan data 570 is typically data collected for a specific item related to an event. For example, when an item is placed in a package (such as package 130), a tag can be generated and placed on the outside of the package. The tag may include a visual identifier that identifies the package when scanned by an appropriate scanning device capable of capturing it. Information generated in response to a scan identifier (a type of event) can be considered a type of scan data. Other scan data 570 may include, for example, general inventory data generated when package-related information is manually entered; captured package storage control data; and barcode scan data.

[0239] Historical data 575 is typically data previously collected and / or analyzed that relates to common characteristics. Historical data 575 embodies operational knowledge and know-how regarding specific characteristics relevant to the operation of the wireless node network. For example, common characteristics could be specific events (e.g., the movement of items from an open environment to a specific enclosed environment (such as a building), item types (e.g., type of package, type of contents being shipped, location, shipping route, etc.), success rates for specific items (e.g., successful shipments), etc. Another example of historical data 575 could include information related to how items were historically handled as they moved from one location to another (e.g., when moving within a specific facility, handling information could indicate that the item is on a specific conveyor and could include information about the conveyor (such as speed and how long the item is expected to remain on the conveyor)).

[0240] Shipment data 580 is typically data related to an item being moved from one location to another. In one embodiment, shipment data 580 may include a tracking number, contents information of the item being shipped, address information related to the origin and destination locations, and other characteristics of the item being moved.

[0241] Layout data 585 is typically data associated with physical areas of one or more portions of a planned path. For example, embodiments of layout data 585 may include building diagrams and physical dimensions of portions of buildings through which nodes may pass. Embodiments may further include density information associated with the physical areas to be traversed and the anticipated number of potential nodes in those areas as the type of layout data. In another example, embodiments of layout data may include configurations of how a set of packages can be assembled on pallets and placed into shipping containers (e.g., unit loading devices (ULDs)), facilitating the movement of collections of goods in various forms, either in a single mode or via intermodal transport.

[0242] RF data 587 is typically information about signal degradation in the signal path environment for a specific type of node, and may involve specific adverse RF conditions that could cause signal fluctuations, interference, or other degradation from the optimal signal path environment for that type of node. For example, RF data may include shielding effects when using specific packaging or locations, shielding effects when wrapped in a specific type of container or assembled as part of palletized shipments, shielding effects when shipping specific contents, and other physical and electronic interference factors.

[0243] Third-party data 589 is an additional type of contextual data 560, which typically includes data generated outside the network. For example, third-party data may include weather information associated with a specific area that an item will pass through as it moves along a predetermined path from one location to another. Those skilled in the art will appreciate that other types of third-party data related to the physical and environmental conditions faced by an item moving from one location to another can also be considered contextual data 560.

[0244] Using contextual data (such as contextual data 560 described above) advantageously helps server 100 better manage the movement of items, provides better location determination, enhances the intelligent operation and management of different levels of the wireless node network, and provides enhanced visibility into the current location and status of items during the operation of the wireless node network. In one embodiment, server control and management code 525 can provide such functionality as enabling the wireless node network to be context-aware and responsive.

[0245] Server control and management code

[0246] Typically, server control and management code 525 controls the operation of exemplary server 100. In embodiments, server control and management code 525 is a collection of software features implemented as programmable functions in code or individual program modules that typically control the behavior of server 100. Thus, exemplary server control and management code 525 may be implemented using several programmable functions or program modules, including but not limited to: (1) a server-side association manager that provides a framework for more robust and intelligent management of nodes in a wireless node network; (2) a context-based node manager that enhances node management in a wireless node network based on context data; (3) a security manager that manages secure pairing aspects of node management; (4) a node update manager that provides updated or different programming for specific nodes and shares information with nodes; (5) a location manager for determining and tracking the location of nodes in the network; and (6) an information update manager that serves requests for information related to the current state of a node, or typically provides information about a node or information collected from a node.

[0247] Server-side association manager

[0248] A server-side association manager (also known as a server-side association management function), typically a program module in Exemplary Code 525, is responsible for intelligently managing nodes in a wireless node network using a secure information framework. In embodiments, this framework can be implemented as a context-driven learning sensor platform. The framework also enables ways to securely share information (such as RF scans, location, date / time, and sensor data) across nodes, ways to modify node behavior, and ways to inform a node that it is considered “lost.” The framework established during the operation of the server-side association manager allows the node network to be managed as a system with enhanced and optimized accuracy in determining the physical location of each ID node. Further information regarding specific embodiments of such an association management framework and method is explained in more detail below.

[0249] Context-based association manager

[0250] A context-based node manager, typically a program module in Exemplary Code 525, is responsible for incorporating context data into management operations to provide an enhanced data foundation upon which node visibility can be provided. In some embodiments, the context-based node manager may be implemented as part of a server-side association manager, while in other embodiments, the context-based node manager may be implemented as a separate program module.

[0251] In one embodiment, the enhanced data foundation relies on contextual data, such as contextual data 560 (e.g., scan data 570, historical data 575, shipping data 580, layout data 585, and other third-party contextual data), which provides information about the conditions and environment surrounding an item and ID node moving from one location to another. Such contextual data (e.g., network know-how, building layout, and operational knowledge of nodes and shipping routes used with the wireless node network) can provide enhanced building blocks that allow server 100 to manage node tracking and location in a robust and rich contextual environment. In this embodiment, context-based management provides the system with visibility through data analytics into when and how a node should be associated as it travels through the wireless node network. In other embodiments, it can provide a basis for a better understanding of RF signal degradation, which may be caused by the operating environment, packaging, package contents, and / or other packages associated with the item and its ID node.

[0252] Security Manager

[0253] A security manager module, which can be implemented independently or as part of the association manager module in exemplary server control and management code 525, helps associate two nodes in a wireless node network by managing the secure pairing aspects of nodes. In one embodiment, the security manager module provides appropriate pairing credentials to allow a node to securely connect to another node. Therefore, when a node wishes to connect to another node, the embodiment requires the server to generate appropriate pairing credentials, provide them to the node, and observe within the node to allow for successful connection or association.

[0254] In operation, a node (such as master node 110a) identifies the address of a node (such as ID node 120a) that it wishes to connect to. Using this address, the node prepares a pairing request and sends it to server 110. Server 110 operates under the control of the security manager module of the association manager and determines whether the requesting node should connect to or otherwise associate with that other node. If not, the server does not issue the requested security credentials. If so, and according to the desired association management paradigm set by the association manager of code 525, the server provides the requested credentials necessary for successful wireless pairing and establishing secure communication between the associated nodes.

[0255] Node Update Manager

[0256] The exemplary server control and management code 525 may include a node update manager module that provides updated programming information to nodes within the wireless node network and collects information from such nodes (e.g., shared data 545, sensor data 550). In the exemplary server control and management code 525, the node update module may be implemented independently or as part of an association manager module.

[0257] Providing updates to node programming can facilitate and enable the distribution of node functionality, saving power and better managing nodes as a system. For example, one embodiment may, depending on the context or associated circumstances, change the functional responsibilities of different nodes by temporarily offloading the responsibility for a specific function from one node to another. Typically, the server guides other nodes to change their functional responsibilities. However, in some embodiments, the master node can guide other nodes to change their functional responsibilities.

[0258] Sharing information between nodes and with the server (e.g., via an exemplary node update manager) as part of the association management functionality of server 100 facilitates the collection of information from nodes and the sharing of information with other nodes. For example, one embodiment may collect and share RF scan data (a type of shared data 545), information about node locations (a type of location data 555), system information about dates / times (another type of shared data 545), and sensor measurements collected from sensor nodes (a type of sensor data 550).

[0259] Location Manager

[0260] Exemplary server control and management code 525 may include a location manager module that helps determine and track node locations. In a general embodiment, a node's location may be determined by the node itself (e.g., the ability of a master node to determine its own location via positioning circuitry 475), by a node associated with that node (e.g., where the master node can determine the location of an ID node), by the server itself (e.g., using location information determined using one or more techniques implemented as part of code 525), and by a combined effort of the master node and the server.

[0261] Generally, an exemplary ID node can directly or indirectly rely on a master node to determine its actual physical location. Embodiments may use one or more methods to determine node location. For example, and as described in more detail below, possible methods for determining node location may involve controlling the node's RF characteristics (e.g., RF output signal level and / or RF receiver sensitivity level), determining relative proximity, taking into account association information, adjusting the location based on contextual information and the RF environment, chained triangulation, and hierarchical and adaptive methods combining various positioning methods. Further information and examples of how an exemplary location manager module can determine node location based on such exemplary techniques are provided in more detail below.

[0262] Additionally, those skilled in the art will appreciate that it may also be possible to determine what constitutes an operable position relative to the actual position based on contextual information about the tracked item. For example, larger items may require relatively lower positioning accuracy than smaller items, making operational decisions and state updates easier to implement when the context is known. If the size of the item is known, the positioning accuracy can be adjusted accordingly. Therefore, if tracking a larger item, or if the system's context awareness allows for the use of lower positioning accuracy, a stronger signal can be employed, and thus a wider scanning area can be used, which can be helpful in situations where RF interference or shielding is a problem.

[0263] Information Update Manager

[0264] Exemplary server control and management code 525 may include an information update manager module that provides information related to the operation and node status of the wireless node network. Such information may be provided in response to requests from devices outside the wireless node network, such as user access device 200. For example, someone shipping goods may query the current status of the goods via their laptop or smartphone (a type of user access device), which will connect to server 100 and request such information. In response, the information update manager module can serve such requests by determining which node is associated with the goods, collecting status information related to the goods (e.g., location data), and providing the requested information in a targeted, timely, and useful form to the querying entity.

[0265] In another example, a user access device can connect to server 100 and request specific sensor data from a specific node. In response, the information update manager can coordinate with the node update manager and provide the collected sensor data 545 to the user access device according to the request.

[0266] Node Filter Manager

[0267] An embodiment of exemplary server control and management code 525 may optionally include a node filtering manager that utilizes a multi-level filtering mechanism to help manage node traffic. Filtering is essentially establishing rules to restrict potential associations and communications. An example of such node filtering management could be defining different filtering levels or patterns for the master node (e.g., which ID nodes the master node can manage as a way to limit communication and management burden on the master node).

[0268] In one example, a "local" mode can be defined where the ID node communicates with and is managed only by the assigned master node if the last wireless node contacts back to server 100 and / or third-party data indicates that the assigned master node and ID node are physically and wirelessly close. Therefore, for the "local" mode of traffic filtering, only the assigned master node communicates with and processes information from the assigned ID node that is physically close to it.

[0269] Moving up to a less restrictive filtering mode allows defining a "zone" mode for filtering, where the ID node can communicate with and be managed by master nodes located at the location where the last report returned to server 100 and / or at the location indicated by third-party data. Therefore, in a "zone" mode for traffic filtering, any master node near the ID node can communicate with and process information from it. This can be useful, for example, when restrictions on associations and pairings are desired within a specific facility.

[0270] In the least restrictive filtering mode, the "global" mode of filtering can be defined as essentially system-wide communication, where ID nodes can be allowed to communicate with and be managed by any master node. In other words, the "global" mode of traffic filtering allows any ID node within the wireless node network to communicate information through a specific master node near the ID node, which can then communicate and process information from that ID node.

[0271] Therefore, using such an exemplary filtering pattern, ID nodes under specific conditions (e.g., crisis, adverse environmental conditions, unfavorable node conditions, etc.) can signal the need to bypass any appropriate filtering mechanisms that help manage communication and association by using an "alert" status flag. In such an example, this would operate to override any filtering rules set at the master node level to allow the ID node to be "found" and connected to another node.

[0272] Therefore, when executing code 525 and accessing the aforementioned data types, exemplary server 100 is operable to manage nodes, collect information from nodes, store information collected from nodes, maintain or access context data related to the environment in which nodes operate, and provide requesting entities with information about nodes (e.g., status, sensor information, etc.).

[0273] Node communication and association examples

[0274] To better illustrate how exemplary management and communication principles can be implemented within an exemplary wireless node network Figure 8-12 Several examples are provided of how exemplary components of a wireless node network can typically communicate (announce and scan), associate, and exchange information during different types of operations in various embodiments. Figure 22 A-22C also provides a more detailed application of such exemplary association and communication activities in the embodiments when the exemplary ID node moves along a transport path (e.g., through a corridor) and is tracked and managed by different master nodes and servers.

[0275] Example of node notification cycle

[0276] As generally explained above, a node can have several different types of advertised states, where it can connect to and communicate with other nodes. Furthermore, as a node moves within the wireless node network, its advertised and connected states can change as it unassociates itself with previously connected nodes, associates with new nodes, or finds itself unassociated with other nodes. In some situations, a node may be fine and not connect to or associate with another node during normal operation. However, in other situations, if a node does not connect to any other node for a very long period, it may face the potential problem of being lost. Accordingly, a node can experience different types of advertised states under these different operational scenarios.

[0277] Typically, a node may be in a state where it cannot connect to other nodes for a certain period of time (also known as an unconnectable interval). However, later, in another state, the node may want to be connected and will announce this during a defined connectable period (also known as a connectable interval). When a node announces that it wants to be connected, it may expect to be connected at some point. In other words, there may be selectable time periods during which a node expects to connect to another node. However, if the node does not connect to another node during that time period (called an alert interval), the node may need to take specific or urgent actions depending on the situation. For example, if a node has not connected to another node for 30 minutes (e.g., the example alert interval), the node may internally change its operation to "more diligently" search for other nodes to connect to. More specifically, the node may change its status flag from alert level 0 (no problem, normal operation) to alert level 2 to request any available master node to acknowledge receipt of the announcement packet broadcast by the node seeking connection.

[0278] Figure 8 This is a diagram illustrating an exemplary announcement state (or information exchange and node connectivity state) of an exemplary ID node in a wireless node network according to an embodiment of the present invention, and the factors involved in the transitions between states. Referring now to... Figure 8 Three exemplary states of a node are illustrated as part of an exemplary advertising cycle for that node—namely, ID node unreachable advertising state 805, ID node discoverable advertising state 815, and ID node general advertising state 830. The transitions between these states will depend on factors related to the expiration of the aforementioned interval types. In an embodiment, the duration of each of these intervals will depend on the system implementation and the context in which the ID node operates. Such time intervals can, for example, be set by server 100 as part of data (e.g., profile data, associated data, context data) provided to the node when updating the node and managing its operations.

[0279] refer to Figure 8 In the example illustrated, an exemplary ID node may have an alarm interval set to, for example, 30 minutes, and be in ID node disconnectable announcement state 805, where the disconnectable interval is set to 5 minutes. In state 805, the ID node can broadcast or announce, but is disconnectable and will not receive SCAN_REQ messages (a type of request for more information sent from another node to the announcing node). Therefore, in this example, an ID node in state 805 can announce in a disconnectable manner for at least 5 minutes, but expects to be connected within 30 minutes.

[0280] If the alarm interval has not yet passed (factor 810) and the disconnection interval is still running (factor 825), the ID node simply remains in state 805. However, if the alarm interval has not passed (factor 810) and the disconnection interval has passed (factor 825), the ID node will enter a mode in which it wants to attempt to connect to another node within a time period (e.g., a 1-minute connectable interval), and will... Figure 8 In an exemplary advertising cycle, the ID node moves to general advertising state 830. In state 830, as long as the connectable interval is running, the ID node will remain in its connectable state and will receive requests of type SCAN_REQ from other nodes in response to advertising packets being broadcast by the ID node. However, when the connectable interval (e.g., a 1-minute period) passes or expires (factor 835), the ID node returns to the unconnectable advertising state 805 for the next unconnectable interval to pass (and the ID node attempts to connect again in state 830), or for the alarm interval to eventually pass (and the ID node finds itself in a situation where, despite its efforts to connect in state 830, it has not connected to another node).

[0281] When the alarm interval finally expires (factor 810), the ID node moves to ID node discoverable notification state 815. Here, the ID node is not yet connectable but will receive a SCAN_REQ type request from other nodes in response to a notification packet that the ID node is broadcasting. In state 815, an exemplary ID node can change its status flag to indicate and reflect that its alarm interval has expired and that the node is no longer in normal operation. In other words, the ID node can change its status flag to the alarm state type that is being broadcast to indicate that the ID node urgently needs to connect to another node. For example, depending on whether the node needs to upload data (e.g., alarm level 3 state) or whether it needs to synchronize timers or other data with another node (e.g., synchronization state), the status flag of the notification packet broadcast by the ID node can be changed to one of the higher alarm levels. With this change of status flag, and the ID node broadcasting in state 815, the ID node waits to receive a request from another node that has received the broadcast and is requesting more information via a SCAN_REQ message (factor 820) sent from that other node to the ID node. Once an ID node has received the SCAN_REQ message (factor 820), the ID node that entered alarm mode because it was not connected to another node during the alarm interval can connect to that other node, upload or share data as needed, and then switch back to state 805 and restart the alarm interval and disconnection interval.

[0282] Example of master node to ID node association

[0283] Announcements (broadcasts) and scans (listening) are the ways nodes can communicate during association operations. Figure 9-12 This provides how network elements (e.g., ID nodes, master nodes, and servers) of a wireless node network can communicate and operate when connected and associated as part of several exemplary wireless node network operations.

[0284] Figure 9 This is a diagram illustrating exemplary components of a wireless node network during an exemplary master node to ID node association according to an embodiment. Reference is now made to... Figure 9 An exemplary master node M1910a is illustrated within the communication range of exemplary ID node A 920a. Master node M1910a also has a communication path back to server 900. As shown, master node M1910a is in scanning or listening mode (e.g., by “M1...). 扫描 "Label indication), while ID node A 920a is in announcement or broadcast mode (e.g., indicated by "A"). 通告(Label indication). In this example, master node 910a of M1 has captured the address of ID node A 920a through an announcement in at least one announcement data group of A and reported it to server 900. In this way, the capture and reporting operation effectively creates a "passive" association and proximity-based custody control between nodes. Such associations can be recorded in a server such as server 900 as part of association data such as association data 540.

[0285] In another embodiment, the passive association between the master node and the ID node can be extended to an "active" association or connection. For example, refer to... Figure 9 In the embodiment shown, server 900 can instruct master node M1910a to associate, connect, or otherwise pair with ID node A 920a, and forward necessary security information (e.g., PIN credentials, security credentials, keys) to master node M1910a. Depending on the advertising state of ID node A 920a, ID node A 910a may only be visible (discoverable) but not connectable. In such a case, master node M1910a must wait until ID node A 920a is in a connectable state (e.g., the ID node is in a general advertising state) and can be paired. (Refer to the above...) Figure 8 The discussion focuses on each ID node having a specific time window during each time period during which it can be paired or connected.

[0286] In this example, when ID node A 920a successfully pairs with master node M1910a, ID node A 920a may no longer need to advertise its address. By default, only unassociated devices advertise their addresses. Paired or associated nodes only advertise their addresses when instructed to do so.

[0287] Example of ID node to ID node association

[0288] In various embodiments, an ID node may be associated with or connected to other ID nodes. Figure 10 This is a diagram illustrating exemplary components of a wireless node network during exemplary ID-to-ID node association according to an embodiment of the present invention. Referring now to... Figure 10 Example master node M1910a, ID node A920a, and server 900, etc. Figure 9 The arrangement is similar to that shown, but with the addition of ID node B920b within the communication range of ID node A920a. In this example, ID node A920a operates in query (scan) mode (e.g., A...). 扫描), listening to ID node B 920b. When ID node A 910a detects that ID node B 920b is making an announcement using one or more announcement data packets as part of an announcement message from ID node B 920b (e.g., B... 通告 When ID node A 920a identifies a status flag from the message, indicating that ID node B 920b has data for uploading (e.g., sensor data 350). As a result, ID node A 920a records the scan results (e.g., as a type of associated data 340), and when subsequently connected to master node M1910a, ID node A 920a uploads the captured scan log information to server 900. In this way, the ID node scanning, capturing, and reporting operations effectively create a "passive" association between different ID nodes. Such a passive association can be recorded in server 900 as part of associated data 540.

[0289] In another embodiment, the passive association between two ID nodes can be extended to an "active" association or connection. For example, refer to... Figure 10 In the embodiment shown, based on the status flags captured in this mode and the uploaded information about ID node B920b, server 900 can send a request to ID node A 920a via master node M1910a to actively connect to or pair with ID node B 920b for the purpose of downloading information from ID node B 920b. In one example, the security credentials authorizing the active connection between ID node A 920a and ID node B 920b are downloaded from master node M1910a to ID node A 920a, and master node M1910a receives the security credentials from server 900. In another example, the necessary security credentials may have been prepared in advance at ID node A 920a. And if M1 is within communication range of ID node B 920b, master node M1 may already be directly connected to ID node B 920b, rather than relying on an ID node-to-ID node connection.

[0290] Example of querying information from ID node to master node

[0291] The exemplary ID node can also send queries to other nodes (both the master node and the ID node). Figure 11 This is a diagram illustrating exemplary components of a wireless node network during an exemplary ID-to-master node query according to an embodiment of the present invention. Referring now to... Figure 11 Except for the exemplary master node M1910a being in announcement or broadcast mode (e.g., M1 通告 ID node A 920a is in scan mode (e.g., A). 扫描 In addition to ), there appeared such as Figure 9The diagram shows a similar group of nodes. In this configuration, ID node A920a can query information from master node M1910a. In one embodiment, the query can be initiated by setting the status flag of the ID node. The requested information can be information to be shared, such as the current time, location, or environmental information maintained by master node M1910a.

[0292] In the passive association example, at A 扫描 The ID node A 920a in this pattern may have already captured the address of the master node M1910a. However, since the ID node cannot directly connect to server 900 to request pairing security credentials (e.g., security PIN information authorizing an active connection between ID node A 920a and master node M1910a), a passive association and corresponding pairing will already be initiated from the master node. In another example, it might be possible for ID node A 920a to store the pairing credentials as security data 335 from a previous connection. This would allow ID node A 920a to initiate an active association with master node M1910a after the passive association.

[0293] Alert level notification example

[0294] As previously noted, in one or more embodiments, a node may enter an alarm phase or level. For example, if a node does not receive acknowledgment of a notification group from the master node within a set time period (e.g., an alarm interval as described in some embodiments), the node will enter a specific alarm phase for more specialized notification, allowing it to be "discovered" or to deliver information. Figure 12 This is a diagram illustrating exemplary components of a wireless node network during an exemplary alarm notification mode according to an embodiment of the present invention. Referring now to... Figure 12 Such as Figure 9 The diagram shows a similar node group, with the addition of another master node (master node M2910b) and another ID node (ID node B 920b). Exemplary ID node A 920a is in announcement or broadcast mode (e.g., A...). 通告 )and nodes M1, M2 and B are each in scan mode (e.g., M1 扫描 M2 扫描 and B 扫描 ). In such Figure 12In the example and configuration shown, the status flag in the announcement message from ID node A 920a has been set to a specific alarm level (e.g., alarm level 2) in the message header, requesting acknowledgment from any nearby master node. In one example, ID node A 920a can enter this mode if it has not connected to another node for a set time period or time interval. In another example, ID node A 920a can enter this dedicated announcement mode upon receiving an instruction (e.g., from server 900 or another nearby node) or upon triggering conditions (other than time)—such as when sensor input (e.g., light) is detected or otherwise registered, and when the node publishes continuous updates to its address as a security feature. ID node A 920a, set at this alarm level and in this dedicated announcement mode, is thus set in an active pairing mode, awaiting pairing credentials.

[0295] From a passive association perspective, any node in scan mode can be passively associated with such announcing node (e.g., ID node A 920a in this alarm mode). Therefore, in the embodiment, the alarm level 2 status flag in the announcement header broadcast by ID node A 920a indicates a request for urgent and proactive intervention, rather than merely passive association without proactive connection.

[0296] From a proactive association perspective, any node that uploads the special announcement header of ID node A 920a can forward security credentials from server 900. This allows nodes receiving such credentials to proactively associate or pair with ID node A 920a.

[0297] Although Figure 8 Examples of how nodes can announce are provided, and Figure 9-12 Examples are provided of how different exemplary devices (e.g., ID nodes, master nodes, and servers) can announce and associate in different ways, but Figure 22 The A-22C provides a set of progressive illustrations that extend how association and disassociation can be applied within an exemplary wireless node network. More specifically, Figure 22 A-22C illustrates, according to an exemplary embodiment of the invention, how association and deassociation can occur when an ID node moves through an exemplary transport path, and when a server and different master nodes track and manage the exemplary ID node.

[0298] Now for reference Figure 22Figure A illustrates a structure 2200 with entrance and exit points. In one example, structure 2200 may be a corridor or another part of a building or facility. In another example, structure 2200 may be a conveyor system that transports items and their ID nodes from the entrance point to the exit point. Master node M12210a is located near the entrance point of structure 2200, while master node M22210b is located near the exit point. Those skilled in the art will appreciate that other master nodes may be placed at additional points in structure 2200, but for convenience and simplicity in the subsequent explanation of the associated handover, they are not shown. Server 100 is operatively connected to each of master nodes M12210a and M22210b via network 105.

[0299] In one embodiment, server 100 may access contextual data 560 associated with structure 2200, such as layout data 585 regarding the dimensions and materials constituting structure 2200. Contextual data 560 may include historical data 575 regarding how ID nodes operated and were successfully tracked as they traversed structure 2200 from entry point to point of existence. For example, server 100 may have contextual data indicating that structure 2200 is a conveyor capable of transporting items and their ID nodes from entry point to exit point over a distance of 800 feet. The contextual data may further indicate that a typical item moves at a certain speed on the conveyor of structure 2200, and the nominal time from entry point to exit point may be approximately 5 minutes. Therefore, server 100 can access contextual data regarding the environment in which ID nodes are operating and can utilize this to manage ID nodes better and more accurately.

[0300] exist Figure 22 In example A, ID node A2220a is shown entering structure 2200 at the entry point. Here, ID node A2220a can announce its desire to connect to the master node when it enters structure 2200 with, for example, a 10-second disconnection interval and a 5-second connectability interval. In this example, server 100 knows that ID node A2220a is near the entry point and expects ID node A2220a to be close to master node M12210a at the entry point. Therefore, server 100 can accordingly set the connectability and disconnection intervals to provide ID node A2220a with sufficient opportunity to connect to the next master node along the predicted path of the ID node and according to its travel speed.

[0301] Additionally, in this case, server 100 can set the alarm interval to 1 minute. Here, if ID node A2220a does not connect to another node within 1 minute, ID node A2220a can broadcast or announce using a message with a status flag indicating a change in alarm status, allowing ID node A2220a to connect to a wider range of other nodes that see the urgency of ID node A2220a connecting and essentially being found. Depending on the context (e.g., type of conveyor, conveyor speed, node density near the entry point, etc.), those skilled in the art will appreciate that server 100 can adjust the announcement period interval to better adapt to the current environment of the ID node.

[0302] While master node M12210a is scanning (listening), it can initially detect advertisement packets from node A2220a during node A's unconnectable interval. However, when ID node A2220a changes its advertisement state and broadcasts as a connectable node in a normal advertisement state (i.e., during the connectable interval), master node M12210a can respond using a SCAN_REQ to acknowledge receipt of the broadcast message and request further information from ID node A2220a. Master node M12210a receives the requested information from ID node A2220a and then communicates with server 100 to notify the server of its passive association with ID node A2220a. Server 100 determines whether an active association is desired and can authorize the active association between master node M12210a and ID node A2220a by sending security credentials to master node M12210a, which allows nodes to securely connect and share information. Furthermore, the master node M12210a can determine the location of ID node A 2220a (or the server 100 can do so by bootstrapping the master node M1 and / or ID node A), and provide the server 100 with the location of ID node A 2220a. Therefore, when ID node A 2220a enters structure 2220 via at least an association, the server 100 is able to manage and track the location of ID node A 2220a.

[0303] exist Figure 22In B, ID node A 2220a has traversed a portion of the transport path through structure 2200 while maintaining association with master node M12210a. However, at some point, master node M12210a and ID node A 2220a lose their association in the direction of server 100 (or when they can no longer communicate). In one example where ID node A 2220a is located on a conveyor within structure 2200, server 100 may instruct ID node A 2220a to enter a low-power mode for a specific time period to, for example, conserve ID node power. In another example, the low-power mode may also provide better positioning accuracy. Because server 100 has access to contextual data, server 100 can know that at a given time, ID node A 2220a is associated with master node M12210a near the entry point and determines that ID node A 2220a will not be near the exit point before the end of the specific time period. When ID node A 2220a is programmed in this way, once a specific period has passed, ID node A 2220a should be near the exit point and can be put back into normal operating mode so that it can seek a connection with master node M22210b.

[0304] Similar to the association process discussed regarding ID node A and master node M1, when ID node A 2220a approaches master node M22210b near the exit point, ID node A 2220a and master node M22210b can be associated. Once connected, the node position and association data are updated on server 100. Furthermore, as ID node A 2220a continues to move through structure 2200, ID node A 2200a can reach... Figure 22 The exit point shown in C is where the node location and associated data are updated again on server 100.

[0305] Those skilled in the art should understand how these principles are applied to the further movement of ID nodes when ID nodes are transferred between other master nodes (e.g., via active / passive association and disassociation), and how these associations and node locations are kept tracked on server 100. Additionally, as server 100 tracks and monitors association, disassociation, and contextual operations, server 100 essentially learns how to better utilize contextual information to better track nodes, manage the power used by ID nodes, and enhance location accuracy.

[0306] Those skilled in the art should also understand the general trade-off between RF power levels and positioning accuracy. If a node's RF power level is set very high, it may be able to advertise and connect to other nodes at greater distances. However, at such high power levels, the system's ability to distinguish and locate different nodes can be challenging.

[0307] Association management within the wireless node network

[0308] As generally explained above, node management can rely on associations created and tracked between nodes, and reflect such logical associations as indicated by association data generated on one or more nodes. In some embodiments, the relied-upon associations can be active associations, where the server explicitly authorizes active connections between nodes. In other embodiments, the relied-upon associations can be passive associations, where a master node or command node (a type of management node) associates with another node but does not actively connect to that other node. With passive associations, the server may be able to keep track of and manage another node without requiring an active association. Therefore, those skilled in the art will appreciate that, in other embodiments, the associations relied upon for managing a wireless node network can include both active and passive associations, and can generally be authenticated, or more specifically, can be authorized, with a degree of protection for the connection and communication using that connection.

[0309] Context management within a wireless node network

[0310] As explained above, node management can depend on the node's context. Figure 5 As shown, server 100 can access a wide variety of different context data 560. According to embodiments of the invention, context data such as data 560 can include a wide variety of data generally related to the environment in which a node is operating, and can be used to advantageously provide enhanced node management capabilities. Accordingly, in embodiments, the use of such context data provides a data foundation that allows the server to better and more efficiently perform management tasks related to nodes in the network, and to adjust such tasks to take into account the relevant context data as nodes move within the network (e.g., when an ID node moves with items being shipped along an expected or predicted delivery path from origin to destination). For example, the server can leverage its ability to rely on relevant context data to advantageously change how it instructs node operation, how it associates a node with another node, how it can better locate nodes, and how it can more efficiently track and respond to requests to report node locations.

[0311] Node location determination method

[0312] According to one or more embodiments of the present invention, as part of managing and operating a network of wireless nodes, the location of a node can be determined. As explained above, an exemplary ID node may directly or indirectly rely on a master node to determine its location. In the embodiments discussed and described herein, the location of a node can typically include its current or past location. For example, if the node has not moved, an embodiment for determining the node's location may be its current location, but if the node is in motion, that location may necessarily be determined as its past location.

[0313] Similarly, the term "location" itself can include locations with varying degrees of precision. For example, location can encompass an actual position in three-dimensional space with defined coordinates, but the use of the term "location" can also include only relative positions. Therefore, unless explicitly limited to a more specific type of location, the term "location" is intended to have a general meaning.

[0314] Determining a node's location can be accomplished by a single master node, a single server, or a master node working in conjunction with a server. On such devices, embodiments can use one or more methods to determine and further refine the node's location. Such example methods may include, but are not limited to, methods that involve controlling the node's RF characteristics (e.g., RF output signal levels and / or RF receiver sensitivity levels), determining relative proximity, considering association information, adjusting for contextual information and the RF environment, chained triangulation, and hierarchical and adaptive methods combining various positioning methods. A more detailed description of these exemplary node location determination techniques is provided below.

[0315] Location by proximity

[0316] In one embodiment, signal strength measurements between two or more nodes can be used to determine the proximity of the nodes. If the actual locations of two nodes are unknown, one embodiment can infer the positional relationship between the two nodes based on their proximity.

[0317] Approximity when power characteristics change

[0318] For example, an exemplary method for determining the location of a node in a wireless node network may involve altering the power characteristics of the node, such as the output power of one of the nodes. Typically, and as referenced... Figure 13As explained, power characteristics can vary to identify nodes closer to the broadcasting node. A node broadcast can transmit one or more signals, while other nodes can report receiving one or more signals. Those other nodes that receive at least one signal broadcast from the transmitting node can be considered part of a group of nearby nodes. And as the power characteristics vary (increase or decrease or both), the group of closest nodes (or a single node) can be identified as the smallest group of nodes among those that receive at least one signal from the broadcasting node. Therefore, while not absolute, the location type of a broadcasting node can be determined based on the closest node or group of nodes. This can be repeated for adjacent nodes to generate closest node set information for each node. More specifically, exemplary closest node set information for each node can include which nodes are closest (via the lowest power characteristic) and, more robustly, supplement this information with which other nodes are incrementally further away (via increasingly larger power characteristics). Thus, closest node set information provides a basis for determining how close nodes in a network are to each other, providing a type of location determination for each node.

[0319] Additionally, in some embodiments, contextual data may be referenced to further enhance the determination of how close the nodes are to each other. For example, combining the set of closest node information with contextual data (such as scan information registered when items change custody controls in a delivery system) can further refine how the location of the nodes is determined. For example, scans and other contextual information will help determine whether one or more nodes are known to be in the same container, vehicle, or moving together on a conveyor belt. Therefore, this type of contextual data can be integrated into further steps of refining how close the nodes are to each other based on contextual data.

[0320] Generally, when the power characteristics of a node change or vary in a wireless node network, the node's location can be determined based on proximity. An exemplary method for determining location by changing the power characteristics of a node in a wireless node network, according to embodiments of the present invention, begins by instructing a first node to change the power characteristics of one or more signals broadcast by the first node. In a more detailed embodiment, such an instruction may cause the first node to incrementally decrease or incrementally increase the power characteristics (such as the output power level) between values, for example.

[0321] The method continues as follows: when the first node changes its power characteristics, based on those other nodes that have received at least one signal broadcast by the first node, a first group of other nodes in the wireless node network that are close to the first node is identified. In a further embodiment, as the first node incrementally changes the output power level of the signal broadcast, this identification step can incrementally identify which of the first group of other nodes are receiving at least one broadcast signal. The incrementally identified nodes can be considered as the set of nodes that are getting closer and closer to the first node.

[0322] The method continues as follows: when the first node changes its power characteristics, the closest one or more other nodes are identified as the closest group of other nodes that have received at least one of the one or more signals broadcast by the first node.

[0323] The method concludes by determining the location of the first node based on the nearest one or more other nodes. Therefore, as power characteristics change, the group of nodes that have received at least one signal broadcast by the first node can change, and the smallest such group is the group of nodes closest to the first node (even if it contains only one node). In a more detailed embodiment, this determination step may include determining the location of the first node based on the nearest one or more other nodes and a set of nodes that are increasingly closer to the first node, as this increasingly closer set of nodes provides more detailed proximity information for refined location determination.

[0324] For example, refer to Figure 14 The set of nodes that are getting closer and closer to ID node F 920f can include node M3, which is the furthest node, and M1, which is closer than M3. When the power characteristic of ID node F decreases incrementally and its output power level changes from P1 to P2, M3 can no longer receive a signal, but M1 and M2 can still receive a signal. Furthermore, as the power characteristic of ID node F continues to decrease incrementally and its output power level changes from P2 to P3, M1 can no longer receive a signal, but only M2, as the last node closest to ID node F, can receive a signal. Therefore, in this example, the location of ID node F can be determined based on the fact that M2 is the closest node, and the set of nodes that are getting closer and closer includes M1 and M3, where M1 is closer than M3.

[0325] In another embodiment, one or more further refinements to the location of the first node can be performed. In one example, the steps described above for location using proximity techniques can be repeated, wherein a second node is instructed to change the power characteristics of one or more signals broadcast by the second node, and the method can then further refine the location of the first node based on the location of the second node. In a more detailed example, the steps can be repeated, wherein the second node is instructed to change the power characteristics of one or more signals broadcast by the second node, and the method can then further determine the location of the first node based on the location of the second node and an increasingly closer set of nodes. With this increasing cross-correlation information about which nodes are closer to other nodes and to what extent, the information can be further repeated for additional nodes, and the embodiment can further refine the location of the first node within the network.

[0326] The method may further include determining context data associated with the first node, and refining the location of the first node based on the context data. In an embodiment where the power characteristic is the output power level, the incremental change of the output power level of the broadcast signal can be set according to the context data.

[0327] This method can also determine contextual data associated with the node closest to the first node and refine the location of the first node based on the contextual data. In yet another example, the method can determine contextual data associated with incrementally identified nodes in a set of nodes that are progressively closer to the first node and refine the location of the first node based on the contextual data. For example, the closest node and the progressively closer set of nodes may have scan data indicating that they are within the same container. This exemplary contextual data can be used to further refine the location of the node being located, which can help to effectively determine that the node is near the container. Accordingly, those skilled in the art will appreciate that the contextual data of the located node and the nodes identified as being close to it can provide relevant input to advantageously help to further refine the location of the node.

[0328] Those skilled in the art will appreciate that the proximity positioning method disclosed and explained above in various embodiments can be used on server devices running one or more portions of server control and management code 525 (e.g., a location manager), such as... Figure 5 This is implemented on the server 100 illustrated in the figure. Such code can be stored on a non-transitory computer-readable medium, such as the memory storage device 515 on the server 100. Therefore, when code 525 is executed, the server's processing unit 500 is operable to perform operations or steps from the exemplary methods disclosed above, including the method and variations thereof.

[0329] Embodiments of such a server device may include a server (such as server 100) operable to communicate with multiple nodes in a wireless node network. See reference... Figure 5 As explained, a server typically includes a server processing unit, server volatile memory, server memory storage device, and at least one communication interface. In this embodiment, the volatile memory, memory storage device, and communication interface are each coupled to the processing unit. The memory storage device maintains at least a program code segment and location data related to the location of one or more nodes. The communication interface provides a communication path that operatively couples the server to the nodes.

[0330] As mentioned above, the server processing unit, when running the program code segment, is operable to perform the steps and operations related to the above method as described above, and variations thereof, which are used for positioning by causing power changes through proximity.

[0331] Proximity when observing signal patterns and intensities over a period of time

[0332] In another embodiment, an improved method for determining node location through proximity may include analyzing signal patterns and strengths between announcing and listening nodes. In one embodiment, a threshold for association may be set based on observed message counts and / or recorded signal strengths over a specific time period, which can improve the ability to locate a node (e.g., an ID node) to another node (e.g., a master node). In some embodiments, the observed message counts may be implemented as an average count over repeated time periods. Further still, other embodiments may filter outliers in the observed dataset to help improve the data quality on which setting the association threshold depends, and thus determine the node's location.

[0333] In a more detailed example, an improved method for determining node location by proximity can show the count of captured announcement messages as a component for determining node location and direction of travel. In this example, two exemplary master nodes (e.g., master nodes M1910a and M2910b) can capture announcement messages from an ID node (e.g., ID node A920a). Master node M1 can observe and capture (e.g., record information related to the observation) 60 messages from ID node A within a 2-minute time period, while master node M2 ​​observes and captures only 7 announcement messages from ID node A within the same time period. Based on the difference in how frequently master node M1 observes messages from ID node A compared to how frequently master node M2 ​​observes messages, the system is able to determine that ID node A is closer to master node M1, and its location is known.

[0334] In a further embodiment, comparing the average timestamps of the captured records can allow the system to make more accurate location determinations. For example, if the average capture message increment found on master node M2 ​​becomes larger (e.g., the message takes longer to travel from ID node A to master node M2), this indicates that ID node A is moving away from master node M2. If the average capture message increment found on master node M2 ​​becomes larger, while the average capture message increment found on master node M1 becomes smaller, this indicates that ID node A is moving away from master node M2 ​​and towards master node M1. Therefore, the location of a node can also be enhanced or refined by relying on changes in message timing (from transmission to reception) over many observed time periods.

[0335] In another embodiment, the observed signal strength can be a component of location determination and estimation of direction of travel, and can allow the system to make more accurate location determinations. For example, two master nodes (M1910a and M2920b) may be capturing announcement messages from a node (ID node A 920a). M1 captures 60 messages from ID node A in 2 minutes, while M2 captures only 7 messages. Master node M1 observes a higher average signal strength for the signal from ID node A compared to the average signal strength observed by master node M2. Based on this observed signal strength information, the system will determine that ID node A is at M1, but the predicted path may indicate that ID node A is moving towards M2. As master nodes M1 and M2 continue to capture records, the system (e.g., management code 524 operating on server 900 communicating with M1 and M2) processes the continuous feed of captured records from M1 and M2. With this observed signal strength information, server 900 will anticipate an increase in the count and average signal strength of messages from ID node A during the observed time period (2 minutes) for the observation at M2, and a decrease for the observation at M1 as ID node A physically moves closer to M2 and further away from M1. Therefore, in this embodiment, changes in the observed power level and the frequency of observed messages can indicate actual node movement.

[0336] Determining node proximity and orientation based on observed signal patterns and characteristic strengths over a time period has the advantages of reducing the likelihood of unwanted and spurious signal anomalies causing incorrect determination of ID node locations. Furthermore, the exemplary methods described above for determining node movement characteristics (e.g., moving closer to a node, moving closer to a node but away from another node, etc.) can be applied in combination with various embodiments for determining node locations described herein as part of refining node locations.

[0337] Figure 17This is a flowchart illustrating an exemplary method for proximity localization of nodes in a wireless node network based on signal patterns and characteristics observed over a time period, according to an embodiment of the present invention. Referring now to... Figure 17 Method 1700 begins in step 1705 by instructing the first and second other nodes to detect any message broadcasts from a node within a time period. This time period can be set based on various factors such as context data. More specifically, the time period can be dynamically changed based on context data as a node moves to a different context.

[0338] Method 1700 causes the server to receive a first indication from a first other node in step 1710 and a second indication from a second other node in step 1715. Finally, at step 1720, method 1700 determines the location of a node based on the difference between the first and second indications.

[0339] The first indication relates to the characteristics of messages broadcast from a node and detected by a first other node during the time period. Similarly, the second indication relates to the characteristics of messages broadcast from a node and detected by a second other node during the time period. These indications may include, for example, the count of messages received by the respective other nodes, a transmission time factor (e.g., the average transmission time of messages to be detected after broadcast), and an average signal strength.

[0340] In one embodiment, the first indication may be a first count of messages broadcast from a node detected by a first other node during the time period, and the second indication may be a second count of messages broadcast from a node detected by a second other node during the time period. Accordingly, when the first count is greater than the second count, it is determined that a node's location may be closer to the location of the first other node compared to the second other node. Additionally, method 1700 may further include determining the actual direction of node movement based on a comparison of the first and second counts over multiple time periods. For example, method 1700 may repeatedly observe over several time periods and track the first and second counts over time to determine which is increasing and which is decreasing, and determine a node's movement based on these measurements over time.

[0341] In another detailed embodiment, the first indication may be a first time factor of a message broadcast from a node detected by a first other node during a predetermined time period, and the second indication may be a second time factor of a message broadcast from a node detected by a second other node during the same time period. The actual node movement direction of a node may be based on a comparison of the first and second time factors. In a more detailed embodiment, the first time factor may be the average transmission time of a message detected at the first other node from one node to the first other node, and the second time factor is the average transmission time of a message detected at the second other node from one node to the second other node. Accordingly, determining the location of a node may be that if the first time factor is less than the second time factor, the location is closer to the first other node than the second other node.

[0342] In another embodiment, the first indication may be a first average signal strength of a message broadcast from a node detected by a first other node during the time period, and the second indication may be a second average signal strength of a message broadcast from a node detected by a second other node during the time period. Accordingly, when the first average signal strength is greater than the second average signal strength, determining the location of a node may be that the location is closer to the first other node than the second other node.

[0343] In an embodiment, method 1700 may further include observing the degree of change of a first average signal strength and the degree of change of a second average signal strength over repeated time periods, and determining the actual node movement direction of a node based on comparing the degree of change of the first average signal strength and the degree of change of the second average signal strength.

[0344] In another embodiment, method 1700 may further refine the determined location of a node. In this embodiment, method 1700 may further include refining the location of a node based on at least one of a first updated location received from a first other node and a second updated location received from a second other node. For example, when the first other node is a mobile master node and it is the node closer to the located node of the two nodes, this embodiment may utilize location signaling on the first other node, which provides the current location of the first other node. This current location data may be transmitted by the first other node to the server to update the server in the server's calculation of the location of that node.

[0345] In yet another embodiment, method 1700 may layer context data with the determined location to refine the location of a node. The context data associated with a node may be determined by the server, and thus the location of a node may be refined based on that context data. In another example, when comparing the location of a node, the context data is associated with the closer of a first other node and a second other node. For example, the server may perceive that a particular master node is closer to the first node than a second master node, and that the particular master node is inside a container. Using this additional context data associated with the particular master node, the server may refine the location of a node based on the context data. When refining the location of a node, other exemplary types of associated context data may be relied upon, such as context data of a specific shielding associated with the environment near the particular master node (e.g., a particular type of ULD with known RF shielding characteristics, etc.).

[0346] Additionally, method 1700 may involve searching to see if a node behaves as expected. More specifically, a further embodiment of method 1700 may further compare the location of a node with the predicted path of that node to determine whether the node is outside the predicted path. This allows the server to use learned historical data when creating the predicted path and to keep tracking the node relative to an acceptable range associated with the predicted path. If the node is outside the predicted path, the method may also generate a notification. Thus, actionable tasks can then be taken to locate the node—e.g., changing the filtering mode options for nodes in a general area, etc.

[0347] Those skilled in the art will appreciate that the method 1700, as disclosed and explained above in various embodiments, can be used on a server (such as a location manager) that operates one or more parts of server control and management code 525 (e.g., a location manager). Figure 5 (Implemented on server 100 as shown in the figure). Such code can be stored on a non-transitory computer-readable medium such as memory storage device 515 on server 100. Therefore, when code 525 is executed, the server's processing unit 500 is operable to perform operations or steps from the exemplary methods disclosed above, including method 1700 and variations thereof.

[0348] Associative driven positioning with variable RF characteristics

[0349] As noted above, signal strength measurements between two or more nodes can be used to determine the relative distance between nodes. If one of the nodes (such as the master node M1910a) has a known location, the relative positions of one or more nodes within range of the node at the known location are generally a function of how accurately the system can determine the distance between the node with the known location and its associated nodes. In other words, embodiments can identify the relative positions of items and their associated nodes by determining the distance of a node from a known location using a variable low-power RF output signal that depends on the association drive.

[0350] Determined by the location of the master node announcement.

[0351] As typically mentioned above, determining node location can involve controlling the RF characteristics of the node (e.g., RF output signal level and / or RF receiver sensitivity level), and more specifically, can involve controlling various aspects of the master node's announcements. Figure 13 This is a diagram illustrating an exemplary location determination using master node announcements according to an embodiment of the present invention. Figure 13 In the illustrated embodiment shown, a master node with a known location, such as master node M1910a, is broadcasting announcement messages at different RF output power levels. Figure 13 The illustration shows exemplary different RF output power levels for concentric ranges 1305-1315 around the master node M1910a. Thus, the master node M1910a can broadcast at the maximum power P1 associated with range 1305, but can control the RF output power level and dynamically change it to P2 and broadcast to a smaller range 1310, or change it to P3 and broadcast to an even smaller range 1315.

[0352] In the illustrated embodiment, the receiving ID nodes AE 920a-920e are in query (scan) mode, and each can use the received signals at different levels to determine how far they are from the transmission M1. Those skilled in the art will appreciate that, although... Figure 13 The illustrated embodiment shown has all receiving nodes as ID nodes, but other embodiments may have master nodes, ID nodes, or a combination of nodes.

[0353] exist Figure 13In an exemplary embodiment, the location of node AE ​​can be determined based on the known location of master node M1910a. This location, plus a distance measurement taken when each of the corresponding receiving nodes AE last received a signal from node M1, and taking into account a confidence factor for the distance measurement, provides a location determination for the node based on the variable RF signal power. Depending on the quality of the distance measurement, each receiving node may or may not have a separately calculated location. In another embodiment, if third-party or contextual data, such as scanning information, is available, such data can be used as an additional confidence factor to determine a refined location. As the communication range of M1 is limited from P1 to P3, the accuracy of positioning via association improves.

[0354] exist Figure 13 The illustrated example describes an exemplary method for determining node location using master node announcements. First, when the master node M1's variable power short-range communication interface 480 is set to P1 (its maximum output), master node M1910a is seen by each of the ID nodes 920a-920e. Based on analysis or historical measurements, it may have previously been found that the outdoor performance (optimal range) of the radio in M1's variable power short-range communication interface 480 at the P1 power level is approximately 30 feet. Therefore, without checking the RSSI levels from individual ID nodes AE 920a-920e and without an active calibration phase, the system can know that ID node AE ​​is within 30 feet of master node M1910a.

[0355] Next, when the variable power short-range communication interface 480 of master node M1 is set to P2 (medium output level in this example), master node M1 is seen by nodes A and B. Based on previous analysis or historical measurements, the outdoor performance (optimal range) of the variable power short-range communication interface 480 of master node M1 operating at the P2 power level has been determined to be approximately 15 feet. Therefore, without checking the RSSI level from individual nodes, we know that ID nodes A 920a and B 920b are within 15 feet of master node M1. Furthermore, we know that ID nodes (e.g., ID nodes C 920c, D 920d, and E 920e) that are no longer receiving broadcast RF signals from master node M1 910a are located somewhere within 30 feet of master node M1 910a, but may be more than 15 feet away from M1.

[0356] Furthermore, when the master node M1's variable power short-range communication interface 480 is set to P3 (its minimum output level in this example), it is seen by the ID node B 920b. Based on previous analysis or historical measurements, the outdoor performance (optimal range) of the master node M1's variable power short-range communication interface 480 operating at the P3 power level has been determined to be approximately 5 feet. Therefore, without needing to check the RSSI level from a single ID node, we know that the location of ID node B920b is within 5 feet of the known location of master node M1910a.

[0357] The ranging steps, as discussed in the examples above, can then be repeated for any identified node to construct a more accurate depiction of the relative position of each node. The granularity of the RF characteristic settings (e.g., RF output signal power level settings) will provide more granularity of location differentiation when performing the ranging steps. In one embodiment, the ranging steps can be performed over a set of total RF characteristic settings (e.g., fewer settings within a wide range), and similar steps can then be performed within a wider range of choices for RF characteristic settings.

[0358] Figure 19 This is a flowchart illustrating an exemplary method for location determination using associations of one or more nodes in a wireless node network according to an embodiment of the present invention. Referring now... Figure 19 Method 1900 begins at step 1905, where the first node broadcasts one or more first messages at a first expected or predicted range distance. In one embodiment, the first expected range distance is the optimal range for the first node. For example, the radio in the first node's communication interface may have a maximum setting to allow the node to broadcast at maximum range assuming an unobstructed environment. Such a setting provides a known expected range distance. Figure 13 In the example, the master node M1910a can broadcast at a maximum power level P1, which reaches a first expected range distance from node M1. However, if node M1 is known to be in an adverse RF shielded environment, the first expected range distance can be a distance adjusted to take into account the context of such shielding (e.g., a type of context data). The expected range distance can be adjusted depending on one or more types of relevant context (e.g., one or more types of context data related to how RF output signals from the node can be blocked).

[0359] In step 1910, method 1900 identifies which nodes associated with the first node have received at least one first message. In one embodiment, as part of identifying which nodes are associated with it, the first node may be able to access and view associated data in its onboard memory storage device. In one example, the association with the first node may be a passive association (e.g., no active pairing and secure connection) or an active association (e.g., active pairing and the ability to securely connect and share data), or a combination of both types of association.

[0360] Next, in step 1915, the first node broadcasts one or more second messages at a second expected range distance, which is incrementally smaller than the first expected range distance. Figure 13 In the example, the master node M1910a can be the first node and is now broadcasting at a medium power level P2, which reaches the second expected range distance from node M1. By incrementally changing the RF power level in this way, the master node M1910a can no longer reach node CE, as... Figure 13 As shown in the image.

[0361] In step 1920, method 1900 terminates by determining the location of one or more identified associated nodes that have not received any second message but have received at least one first message, wherein the location is between a first and second expected range distance from the first node. Similarly, in Figure 13 In the example, master node M1910a can determine the location of node CE (assuming they have not received the message sent at the second expected range distance at RF power level P2) between the first expected range distance (when master node M1 broadcasts at power level P1) and the second expected range distance (when master node M1 broadcasts at power level P2) from the known location of master node M1.

[0362] In one embodiment, method 1900 may further cause the first node to broadcast one or more third messages at a third expected range distance (incrementally smaller than the second expected range distance), and determine the location of one or more identified associated nodes that have not received any third messages but have received at least one second message, wherein the location is approximately near the second expected range distance from the first node. Similarly, in Figure 13 In the example, by incrementally changing the power level down to P1 and broadcasting a third message at a expected range distance from the P1 level, the master node M1 can determine the location of node A (because node A received the second message but not the third message) to be approximately near the expected range distance from the master node M1's location at P2.

[0363] Additional embodiments of method 1900 can further refine such a determined location by updating the location of the first node. In one embodiment, the first node may be a mobile node. Accordingly, refinement may involve determining the current mobile location of the first node, and refining the locations of one or more identified associated nodes that have not received any second message but have received at least one first message based on the current mobile location of the first node. Thus, as the first node moves and updates its own location (e.g., via GPS signals received by the positioning circuit 475 on the master node), the first node is able to utilize its own updated location and advantageously refine the locations of its associated nodes.

[0364] Furthermore, in some embodiments, the refined location of associated nodes can be transmitted to the server. This provides the server with updates and helps in tracking and managing the locations of nodes in the network. Again, returning to the reference... Figure 13 For example, master node M1910a can use this method to locate associated nodes, such as ID nodes AE 920a-920e, and update server 100 with this new location data related to the current location of node M1 and any nodes associated with node M1.

[0365] Those skilled in the art will appreciate that the method 1900, as disclosed and explained above in various embodiments, can be implemented on a node running one or more portions of the main control and management code 425 (e.g., a location-aware / capture module). Figure 4 The master node 110a or Figure 13 (The master node M1910a in the example). Such code can be stored on a non-transitory computer-readable medium, such as a memory storage device 415 on the master node 110a. Therefore, when code 425 is executed, the processing unit 400 of the master node can be operable to perform operations or steps from the exemplary methods disclosed above, including method 1900 and variations thereof.

[0366] In another embodiment, a node device is described in a wireless node network, which uses location determination via association as described with reference to the steps associated with method 1900. As mentioned above, such a node device can be implemented using a master node having a node processing unit, node volatile memory, node memory storage device, and first and second communication interfaces. Each of the memory and communication interface is coupled to the node processing unit. Furthermore, the node memory storage device maintains at least program code segments, associated data, and location data, and sometimes also shipping information. The first communication interface provides a first communication path operatively coupling the node to a plurality of other nodes in the network, while the second communication interface provides a second communication path operatively and individually coupling the node to a server in the network.

[0367] In this embodiment, the node processing unit is operable to transmit one or more first messages via a first communication interface at a first expected range distance, and to identify which other nodes associated with the first node have received at least one first message. In one embodiment, the node processing unit may be operable to access associated data in a node memory storage device when identifying which nodes associated with the first node (e.g., passive, active, or both) have received at least one first message.

[0368] The first expected range distance can be the optimal transmission range for the first communication interface, and in a more detailed example, it can be adjusted based on context data (e.g., RF shielding inherent in the node's surrounding environment). In yet another embodiment, the first and second expected range distances can be adjusted based on one or more types of context data relating to how the RF output signal transmitted from the first communication interface can be impeded by the node's environment.

[0369] The node processing unit is also operable to transmit one or more second messages via a first communication interface at a second expected range distance (increment less than the first expected range distance), and to determine the location of one or more identified associated nodes that have not received any second messages but have received at least one first message. This location lies between a first expected range distance from the node's known location and a second expected range distance from the node's known location. In a further example, the node processing unit may be operable to store the determined location in a node memory storage device as part of location data.

[0370] The node processing unit is also operable to transmit one or more third messages via a first communication interface at a third expected range distance (increment less than the second expected range distance), and to determine the location of one or more identified associated nodes that have not received any third messages but have received at least one second message, wherein the location is between the second expected range distance from the known location of the node and the third expected range distance from the known location of the node.

[0371] In another embodiment, the nodes may be mobile, and the node processing unit may be further operable to refine the locations of one or more identified associated nodes that have received the first message but not the second message by updating the location of the first node. More specifically, the node processing unit may be operable to determine the current mobile location of the first node (e.g., by utilizing positioning circuitry on the node to check for a valid GPS signal and location locking based on such signal), and based on the current mobile location of the first node, refine the locations of one or more identified associated nodes that have received at least one first message but not any second message. The node processing unit may also be operable to transmit the refined locations to a server via a second communication interface.

[0372] Determined by the location of the ID node announcement

[0373] Although Figure 13 An example of location determination via master node announcements is provided, but Figure 14 The focus is on location determination via ID node announcements. Specifically, Figure 14 This is a diagram illustrating exemplary location determination using ID node announcements according to an embodiment of the present invention. Figure 14 In the illustrated embodiment shown, the exemplary ID node F 920f is in announcement mode, but its location is not known. Figure 13 Same, Figure 14 The exemplary different RF output power levels from ID node F 920f are illustrated as concentric ranges 1405-1415 with respect to ID node F 920f. Therefore, ID node F 920f can broadcast at the maximum power P1 associated with range 1405, but can control the RF output power level and dynamically change it to P2 and broadcast to a smaller range 1410, or change it to P3 and broadcast to even smaller ranges 1415. Master nodes M1-M3910a-910c are positioned relatively close to various known locations of ID node F 920f, which has an unknown location. Accordingly, as part of how the system can determine the location of ID node F through ID node announcements, ID node F 920f can utilize the ability to adjust the RF characteristics (such as the RF output signal power level) of its own short-range communication interface.

[0374] In the illustrated embodiment, the RF output signal power level of the ID node F 920f can be changed or dynamically adjusted via programmable settings (such as profile settings or parameters) related to the operation of the variable power short-range communication interface 375. Additionally, while the actual communication range may vary with the surrounding environment, the maximum expected communication range of the ID node's transmitter at each power level is known, assuming optimal operating conditions or the absence of significant RF shielding or interference. Therefore, a specific power level setting for a broadcast node is inherently associated with a corresponding expected range distance.

[0375] In an exemplary method of determining node location using ID node announcements, the RF output signal power level can vary across multiple power levels to improve location through master node association. More specifically, when the variable power short-range communication interface 375 of ID node F is set to P1 (its maximum output), ID node F 920f is seen by each of the master nodes M1-3910a-910c. It may have been previously discovered that the expected outdoor performance or range distance (optimal range, or range based on analysis or historical measurements) of the radio in the variable power short-range communication interface 375 of ID node F at the P1 power level is approximately 30 feet. Therefore, without any checks on the RSSI level from a single master node, the system knows that ID node F is within 30 feet of master nodes M1-M3.

[0376] Next, when the variable power short-range communication interface 375 of ID node F is set to P2 (medium output level in this example), ID node F 920f is seen by master nodes M1910a and M2910b. The expected outdoor performance or range distance (optimal range, or range based on analysis or historical measurements) of the radio in the variable power short-range communication interface 375 of ID node F operating at the P2 power level is approximately 15 feet. Therefore, without any checks on the RSSI level from individual nodes, we know that master nodes M1910a and M2910b are within 15 feet of ID node F 920f in this example. Furthermore, we know that the master nodes no longer receive broadcast RF signals from ID node F 920f (e.g., master node M3910c) somewhere within 30 feet of ID node F 920f, but in this example, are possibly more than 15 feet away from node F.

[0377] Furthermore, when the variable power short-range communication interface 375 of ID node F is set to P3 (its minimum output level in this example), ID node F 920f is only seen by the master node M2910b. The expected outdoor performance or range distance (optimal range, or range based on analysis or historical measurements) of the radio in the variable power short-range communication interface 375 of ID node F at the P3 power level is approximately 5 feet. Therefore, without any checks on the RSSI level from the master node, in this example, we know that the location of ID node F 920f is within 5 feet of the known location of the master node M2910b.

[0378] As discussed in the example above, the ranging step for the RF characteristics of changes in the notification ID node can then be repeated for any identified node in order to construct a more complete depiction of the relative position of each node.

[0379] Furthermore, the timing between such ranging steps can vary dynamically depending on whether the node moves. Those skilled in the art will appreciate that, when moving, a faster flow of such ranging steps will contribute to better accuracy, given that the node is moving. Therefore, when a node moves, it may be desirable to have a shorter time interval between instructing the node to broadcast one or more messages at a specific power level and then instructing the node to broadcast one or more messages at a different power level; this can be determined based on context data. For example, the context data might indicate that the node is within a node package on a moving conveyor system. Accordingly, the node moves relative to a stationary master node, which can be positioned along the conveyor system. Thus, the server can cause the first node to perform the ranging step, where the power changes in a relatively rapid sequence compared to a scenario where the context data indicates that the node is not moving or is substantially stationary.

[0380] Figure 20 This is a flowchart illustrating another exemplary method for location determination using associations of one or more nodes in a wireless node network according to an embodiment of the present invention. (Reference) Figure 20 The method 2000 begins in step 2005 by instructing a first node to broadcast one or more first messages at a first power level, which is related to a first expected range distance. In one example, the first expected range distance may be the optimal range for the first node (e.g., the transmission range assuming no obstructions and a clear signal path between nodes). In another example, the first expected range distance may be the optimal range for the first node adjusted based on contextual data (e.g., data related to the RF environment surrounding the first node).

[0381] In step 2010, method 2000 identifies which nodes associated with the first node have known locations. For example, this type of identification can be done by viewing association data that indicates which nodes are associated with the first node (e.g., via passive association, via active association, or via a combination of both), determining which nodes are associated with the first node based on the viewed association data, and identifying which of those associated nodes have known locations.

[0382] Method 2000 continues in step 2015 by determining which of the identified associated nodes received at least one first message. Next, in step 2020, method 2000 instructs the first nodes to broadcast one or more second messages at a second power level, wherein the second power level is related to a second expected range distance, and the second power level is incrementally smaller than the first power level. In a further example, the first expected range distance and the second expected range distance may be adjusted based on one or more types of context data related to how the RF output signal from the first node can be blocked.

[0383] In step 2025, method 2000 determines which of the identified associated nodes received at least one second message. Method 2000 ends in step 2030, wherein the method determines that the location of the first node is at a first expected range distance and a second expected range distance from each of the identified associated nodes that did not receive at least one second message but received at least one first message, or between the first expected range distance and the second expected range distance.

[0384] As mentioned above, determining the location of a node can be improved when movement is taken into account. Accordingly, embodiments of method 2000 can instruct a first node to broadcast one or more second messages within a time interval following an instruction to broadcast one or more first messages. In some implementations, this time interval can be predetermined, but in others, it can be a parameter dynamically set based on context data associated with the first node. More specifically, the time interval can decrease from a previous value when the context data associated with the first node indicates that the first node is moving, but can increase from a previous value when the context data associated with the first node indicates that the first node is substantially stationary.

[0385] In another embodiment, method 2000 may further include instructing the first node to broadcast one or more third messages at a third power level. Such a third power level relates to a third expected range distance and a range that incrementally decreases compared to a second expected range distance. Thereafter, the method may determine that the location of the first node is at or between the second and third expected range distances from each identified associated node that has not received any third messages but has received at least one second message.

[0386] In another embodiment, method 2000 may include refining the location of the first node using the updated locations of one or more identified associated nodes that have not received at least one second message but have received at least one first message. For example, if the first node is associated with a mobile master node, the location of the first node may be refined using the updated location of the mobile master node (which may be closer to the first node than previously determined).

[0387] In a further embodiment, the first node in the operation of method 2000 may not be aware of its own position. In another embodiment, the first node in the operation of method 2000 may have previously been aware of its own position, but may no longer be aware of its own position before broadcasting one or more first messages. More specifically, the first node may no longer be aware of its own position before broadcasting a first message due to changes in the environment surrounding the first node. Such changes in the environment could be, for example, when the first node has moved into a structure that prevents the first node from receiving position signals (e.g., a building, vehicle, aircraft, container, etc.).

[0388] Those skilled in the art will understand that the methods 2000 disclosed and explained above in various embodiments can be applied to nodes (e.g., Figure 4 Implemented on the master node 110a in the system, which (e.g., Figure 4 The master node 110a) runs one or more parts of the master control and management code 425 (e.g., a location-aware / capture module) to control ID nodes (such as... Figure 14 The operation of the ID node F in the process is part of the location determination announced via the ID node. Such code can be stored on a non-transitory computer-readable medium, such as a memory storage device 415 on the master node 110a. Therefore, when code 425 is executed, the processing unit 400 of the master node can be operable to perform operations or steps from the exemplary methods disclosed above, including method 2000 and variations thereof.

[0389] From an apparatus perspective, an exemplary node apparatus using location determination via association in a wireless node network may include a node processing unit, node memory (e.g., node volatile memory and node memory storage device) coupled to and used by the node processing unit. The node memory storage device maintains at least program code segments, association data, and location data. The node apparatus further includes a first communication interface that provides a first communication path coupled to the node processing unit and is operatively coupled to a plurality of other nodes in the network. For example, Figure 4 The main node 110 shown in the diagram includes this type of operational structure.

[0390] A node processing unit (e.g., processing unit 400 of master node 110a) is operable to perform specific functions or steps when at least executing a program code segment residing in the node's volatile memory. Specifically, the node processing unit is operable to transmit instructions via a first communication interface to a first other node (e.g., an ID node or a master node temporarily operating as an ID node) to cause the first other node to broadcast one or more first messages at a first power level, wherein the first power level is related to a first expected range distance.

[0391] The first expected range distance can be the optimal range for the first node, and more specifically, it is the optimal range for the first node adjusted based on context data. Even more specifically, the first expected range distance and the second expected range distance can be adjusted based on one or more types of context data related to how they can impede RF output signals broadcast from the first node.

[0392] The node processing unit is also operable to identify which nodes associated with the first node have known locations. To this end, the node processing unit can access and view association data stored in the node memory storage device (e.g., data indicating which nodes are passively or actively associated with the first other node), can determine which of the remaining other nodes are associated with the first other node based on the viewed association data, and can identify which of the remaining other nodes identified as being associated with the first other node have known locations.

[0393] The node processing unit is also operable to determine which of the identified associated nodes have received at least one first message, and to transmit another instruction to the first node via a first communication interface, such that the first node broadcasts one or more second messages at a second power level, wherein the second power level reaches a second expected range distance and is incrementally smaller than the first power level.

[0394] Finally, the node processing unit is operable to determine which of the identified associated nodes received at least one second message, and then determine the location of the first node at or between a first expected range distance and a second expected range distance from each of the identified associated nodes that did not receive at least one second message but received at least one first message.

[0395] In a further embodiment, the node processing unit may be operable to convey a third instruction to the first node via a first communication interface, causing the first node to broadcast one or more third messages at a third power level. The third power level is related to a third expected range distance and a range that incrementally decreases from a second expected range distance. Additionally, the node processing unit may then be operable to determine whether the first node's location is at or between the second and third expected range distances from each identified associated node that has not received any third messages but has received at least one second message.

[0396] In another embodiment, the node processing unit can take into account the movement of the first node using the time interval between instructions sent to the first node. Specifically, the node processing unit can be further operable to convey another instruction to the first node via a first communication interface to broadcast a second message within a time interval following an instruction to the first node to broadcast a first message. In a more detailed example, this time interval can be dynamically set based on context data associated with the first node. Even more specifically, when the context data associated with the first node indicates that the first node is moving (e.g., the first node is on a moving conveyor system), the time interval can be programmatically decreased from a previous value, and / or when the context data associated with the first node indicates that the first node is substantially stationary (e.g., the node is within a node package recently placed in a storage area), the time value of the interval can be increased from a previous value.

[0397] In a further embodiment, the node processing unit may be operable to refine the position of the first other node using the updated position of one or more identified associated nodes that have not received at least one second message but have received at least one first message, and cause a second communication interface (e.g., a mid-range / long-range communication interface 485 coupled to the processing unit 400) to transmit the refined position to the server.

[0398] From the server's perspective Figure 21 This is a flowchart illustrating yet another exemplary method for location determination using associations of one or more nodes in a wireless node network according to an embodiment of the present invention (similar to...). Figure 20Those skilled in the art should understand that although the server can be operated to implement the layout as described in method 2000 and the steps discussed above, Figure 21 Further details are provided regarding how a server processing unit (such as processing unit 500 running server code 525) can implement such a method at this level of the network via method 2100. In this more detailed embodiment, the server communicates directly with the master node (e.g., the first node) to bootstrap and control how the master node interacts with the ID node (e.g., the second node) and causes operations to be performed on the ID node (e.g., the second node). Thus, step 2105 is similar to step 2005, but more precisely, requires communication with the first node via a communication interface so that the second node in the network broadcasts one or more first messages at a first power level at the request of the first node, wherein the first power level is related to and corresponds to a first expected range distance. Similarly, step 2120 is similar to step 2020, but more precisely, requires communication with the first node via a communication interface so that the second node broadcasts one or more second messages at a second power level at the request of the first node, wherein the second power level is related to a second expected range distance and is incrementally smaller than the first power level. The other steps of method 2100 are similar to those illustrated and explained above relative to method 2000, and similar principles will apply to method 2100.

[0399] Those skilled in the art will understand that the method 2100, as disclosed and explained above in various embodiments, can be used on a server (e.g., Figure 5 Implemented on server 100), the server (e.g., Figure 5 Server 100 in the middle runs one or more parts of server control and management code 525 to bootstrap the master node control ID node (such as...). Figure 14 The operation of the ID node F in the process is part of the location determination announced via the ID node. Such code can be stored on a non-transitory computer-readable medium, such as a memory storage device 515 on server 100. Therefore, when code 525 is executed, the server's processing unit 500 is operable to perform operations or steps from the exemplary methods disclosed above, including method 2100 and variations thereof.

[0400] Similar to the node device described above, one embodiment includes an exemplary server device in a wireless node network that uses location determination via association. The exemplary server device typically includes a server processing unit, server memory (e.g., server volatile memory and server memory storage device) coupled to and used by the server processing unit. The server memory storage device maintains at least program code segments, association data, and location data. The server device further includes a communication interface coupled to the server processing unit and providing access to a communication path operatively coupling the server to at least a first node in the network.

[0401] When at least a program code segment residing in the server's volatile memory is executed, the exemplary server processing unit is operable to perform specific functions or steps. Specifically, the server processing unit is operable to communicate with a first node via a communication interface, such that a second node in the network, upon request from the first node, broadcasts one or more first messages at a first power level, wherein the first power level is related to a first expected range distance; identifies which of the remaining nodes in the network associated with the second node have known locations; determines which of the identified associated nodes have received at least one first message; communicates with the first node via the communication interface, such that the second node, upon request from the first node, broadcasts one or more second messages at a second power level, wherein the second power level is related to a second expected range distance and incrementally less than the first power level; determines which of the identified associated nodes have received at least one second message; and determines that the location of the second node is at or between a first expected range distance and a second expected range distance from each of the identified associated nodes that have not received any second messages but have received at least one first message. Furthermore, in a further embodiment, the processing unit of the server device may be further operable to store the determined location as part of location data in the server memory.

[0402] In another embodiment, the processing unit of the server device may be operable to communicate with the first node via a communication interface, such that the second node broadcasts one or more second messages within a time interval following communication with the first node, thereby causing the second node to broadcast one or more first messages. As previously mentioned, this type of time interval can be dynamically set based on context data associated with the second node. The context data can also be used as described above with respect to the node device, but here it is applied to the second node—in such a case, the first expected range distance is an optimal range for the second node adjusted based on the context data.

[0403] Determined by the location of the main node in the announcement.

[0404] In another embodiment, the master node may no longer know its location. This can occur, for example, when the master node determines its current location via GPS positioning circuitry 475, but finds itself unable to access a sufficient number of GPS signals (e.g., it cannot determine its location due to a lack of sufficient GPS signals from different GPS satellites). This can also occur when the master node moves indoors near structures that interfere with location signals.

[0405] In an exemplary embodiment where the master node attempts to determine its own location via an announcement technique, the master node may detect a loss of location confidence (e.g., when a GPS signal loss is detected; when a separate signal indicating that the master node's location is unknown is detected to the processing unit 400; when the processing unit 400 senses movement (e.g., via an accelerometer (not shown) etc.) but cannot confirm that the positioning circuit 475 is providing updated location information for the node, etc.). In other words, the master node becomes aware that it no longer has a known location.

[0406] Next, the master node will be similar to the reference. Figure 14 The ID node F 920f, as described, begins broadcasting one or more notification messages in response. This allows a master node with an unknown location to advantageously utilize the known locations of other nearby nodes. Accordingly, the embodiment can allow a type of leverage chain effect, whereby the known location of a particular type of node can be used to extend location information to other nodes (e.g., ID nodes) that do not know their location or to nodes that have detected a loss of location confidence (e.g., master nodes). Therefore, in situations where the signal from the conventional airborne positioning circuit 475 is unavailable, such an embodiment can be used to determine the indoor location of master nodes (including equipment equipped with master node functionality).

[0407] Return to the example method 2000 and Figure 20Method 2000 can make the first node unaware of its own location. This may occur when the first node (e.g., an ID node) is actually a master node that previously (e.g., via received GPS signals) was aware of its own location but (e.g., when GPS signals can no longer be received) no longer is aware of its location, and this master node has master node change operations operating as an ID node before broadcasting the first message. In other words, due to changes in the environment surrounding the master node, such as when the master node has moved into a structure that obstructs the master node from receiving location signals, the master node may no longer be aware of its location and begin operating as an ID node for location determination purposes before broadcasting the first message. Therefore, embodiments can advantageously allow nodes to adaptively change their operations when moving from an unobstructed outdoor environment to an indoor environment. And when such a master node temporarily operates as an ID node for positioning purposes, the server can interact with that master node.

[0408] Positioning using improved RSSI measurements

[0409] In another embodiment, proximity of nodes can be determined using signal strength measurements between two or more nodes by employing one or more improvements to conventional RSSI measurements. In conventional RSSI measurements, such as those utilizing Bluetooth 4.0, those skilled in the art will appreciate that adaptive frequency hopping, as part of spread spectrum techniques, can undesirably cause signal strength fluctuations. In other words, the advantages of using frequency hopping and spread spectrum for security and interference avoidance can negatively impact stable proximity-based location determination using such signals. Therefore, for location determination purposes, it may be desirable to emphasize signal stability and limit fluctuations.

[0410] In one embodiment, one type of improvement to RSSI measurement may include reducing the number of channels and / or the corresponding frequency range used during announcements from the node. For example, the node may enable processing units 300 / 400 to adaptively control the variable power short-range communication interface 375 / 480 to reduce the number of channels and / or frequency range used during node announcements. In some embodiments, such dynamic changes can be implemented by modifying the content of specific type of profile data 330 / 430, such as RF profile data that effectively defines the node's RF characteristics (e.g., frequency, power level, duty cycle, channel number, channel spacing, alternative fluctuation modes, etc.). In a further embodiment, a first fluctuation mode may be defined, which provides a default or more standard communication protocol, such as for... The conventional frequency hopping, spread spectrum, and channel allocation in communications. One or more alternative modes of one or more RF characteristics can be defined to provide increasingly stable and less volatile RF output signals from the node. Therefore, a node can be dynamically placed in one or more modes of RF characteristics that, for the purpose of enhancing location determination using RSSI measurements, increasingly emphasize the stability of the node's RF output signal and limit volatiles.

[0411] In another embodiment, one type of improvement to RSSI measurement may include ensuring the visibility of and advantageously managing an automatic gain control (AGC) circuit (not shown) that can cause the RF output signal to vary for the node. For example, a node may include a type of AGC circuit as part of a variable power short-range communication interface 375 / 480. This type of AGC circuit can allow the node processing unit 300 / 400 or other logic circuitry as part of the variable power short-range communication interface 375 / 480 to limit fluctuations under specific conditions (e.g., when attempting to use RSSI positioning techniques). In this example, different AGC circuit settings may be defined in exemplary RF profile data that effectively defines the RF characteristics of the node (e.g., frequency, power level, duty cycle, channel number, channel spacing, alternative fluctuation modes, etc.). This is yet another example of how nodes can be dynamically placed in one or more modes regarding such RF characteristics (including AGC road settings), which increasingly emphasize the stability of the node's RF output signal and limit fluctuations for the purpose of using RSSI measurements to enhance location determination.

[0412] Localization using adjustments to environmental factors in RF signal quality

[0413] Generally, those skilled in the art will appreciate that environmental factors can cause fluctuations in communication signals (such as RF signals), or cause them to be transmitted and received in ways that are undesirable depending on the environment along the signal path. Passive physical interference factors (e.g., in the form of electronic signal shielding) may be sufficiently close and cause a decrease in signal strength across the node's output range. Additionally, active radio interference factors may vary across the node's RF output range, depending on other active devices in the vicinity of the receiver. Therefore, the node's neighborhood environment can have many adverse factors that affect communication and thus the ability to locate the node.

[0414] In one embodiment, location determination can be enhanced using a data analysis-based approach that adjusts for and accounts for different RF environmental factors for similar types of nodes in similar environments. For example, for a given environment, the quality of the RF output signal of a particular type of node and its corresponding physical range to a receiver of known sensitivity can be determined. In this example, the system defines the maximum range of the signal based on predetermined conditions, such as open connectivity. This might assume no signal degradation due to interference or physical shielding in the environment. However, both interference and physical shielding can reduce the range of the node's RF output signal. In a dynamically adaptive and learning manner, the system can collect information about how a particular type of node operates in a specific environment under specific settings (e.g., corresponding settings for reported signal strength and RF output signal power levels). This analysis can be repeated for similar environments. In other words, through such data analysis of the expected environment faced by similar nodes, signal loss information can be generated and applied as a type of contextual data (i.e., RF data) to nodes in similar environments to refine location determination. Therefore, exemplary embodiments can refine location determination based on contextual understanding of the expected environment by leveraging adaptive signal loss characteristics (e.g., physical shielding, such as packaging, package contents, neighboring packages, neighboring package contents, and physical infrastructure that causes signal changes), without requiring a calibration phase.

[0415] Furthermore, these data points can be advantageously combined with third-party data describing the physical environment in which the node was located at that time, potentially refining the location even further. Such information can be used as RF data (a type of context data) in future efforts to manage and locate similar nodes expected to be in similar environments.

[0416] More specifically, in embodiments where location determination is refined based on context and data analysis to adjust for known RF obstructions, the maximum physical range of the node's RF output signal relative to a receiver with known RF sensitivity is determined. In one example, this first range value may be referred to as the theoretical or nominal open range of a similar type of transmitter-receiver node pair in a similar environment, but where there is essentially no physical shielding or signal interference negatively impacting the signal range. A second range value, which can be considered the actual RF range value, may be the signal range observed in a similar environment, but where contextual factors that reduce the communication range exist, including physical shielding due to factors such as packaging, package contents, neighboring packages, neighboring package contents, physical infrastructure, interference from other wireless sources, or shipper-specific information (such as vehicle or facility layout information). By accessing previous data analysis of the different range values ​​and utilizing knowledge of the operating environment in which the transmitting node is located (e.g., an environment similar to the neighboring environment of the node), a refined location can be determined using an approximation of the actual RF output range, which intelligently adjusts to the expected RF environment of the node. In other words, by knowing the appropriate context associated with a node (such as signal degradation information about how similar nodes operate in similar environments), improved location determination can be made to provide intelligent and efficient adjustments to the node's refined location (such as communication distance adjustment).

[0417] In an example, such as Figure 2 In the example shown, the master node 110b is located outside a container (such as a known unit loading equipment (ULD) container 210 used for transporting groups of items on an aircraft), which has ID nodes inside. A first or theoretical range value between the master node 110b and ID node 120b can be determined as 10 feet at a given RF output power level when it is known that a package (and associated ID node) is less than 10 feet away from the scanning node (e.g., master node 110b). At similar distances with similar types of nodes, but with loss of incident RF signal due to communication through the walls of container 210, a second range value can be between 4 and 5 feet. If contextual data, such as third-party information or scanning data, indicates that the transmitting node is inside the ULD container 210, the system will expect to limit the transmission range based on data analysis associated with that known RF obstacle (e.g., characteristics of transmission through the ULD container 210), thus reducing the number of possible scanning nodes that can see the broadcast node inside the ULD container, or requiring the transmitting node to increase its RF output power to be heard.

[0418] Figure 22This is a flowchart illustrating an exemplary method for determining the location of a first node in a wireless node network based on context data, according to an embodiment of the present invention. Referring now to... Figure 22 Method 2200 begins in step 2205 by having a network device (such as a master node or server) access first type of context data related to the neighborhood of the first node.

[0419] The first type of contextual data includes signal degradation information about how the second node will operate in an environment similar to the first node's neighboring environment when the second node is of a similar type to the first node. Therefore, the signal degradation information is not calibrated using actual measurements relative to the first node's current neighboring environment, but rather provides compensation information that can generally be expected in a more general neighboring environment based on how similar nodes can operate in similar environments. Since the similar environment of similar nodes is generally an approximation of the expected neighboring environment of the first node, this advantageously avoids the need for actual calibration of the neighboring environment. In one embodiment, the signal degradation information may be based on the difference between how the second node communicates when exposed to an unfavorable communication environment (such as an environment similar to the first node's neighboring environment) and how the second node communicates when exposed to a nominal communication environment (such as an environment unhindered by shielding and interference factors). Those skilled in the art will appreciate that the nominal communication environment does not need to perfectly eliminate all the effects of shielding or interfering with communication.

[0420] The type and aspects of signal degradation information can vary depending on a wide range of factors. In one embodiment, signal degradation information may be related to at least one of shielding and interference. Therefore, signal degradation information can include both passive and active factors affecting the communication environment.

[0421] In another embodiment, when the similar environment is an unfavorable communication environment, the signal degradation environment can be based on the degradation operation of the second node. More specifically, the signal degradation information can be based on the difference between how the second node communicates when exposed to an unfavorable communication environment and how the second node communicates when exposed to a substantially nominal communication environment (such as an open-air environment).

[0422] In yet another embodiment, the signal degradation information may at least relate to shipment data of one or more items shipped (e.g., currently shipped or previously shipped) and located in the vicinity of the first node. For example, a package near the first node may include metallic material that can obstruct or block RF signals, and the signal degradation information may be related to such information regarding a closed package shipped near the first node. In another example, the signal degradation information may at least relate to layout data of one or more physical structures in the vicinity of the first node. More specifically, the layout data may target one or more physical structures (e.g., walls, machines, fences, and vehicles) in the vicinity of nodes near the predicted path of the first node. In yet another example, the signal degradation information may at least relate to historical data of one or more analyzed previous operations of the second node.

[0423] In step 2210, a network device, such as a master node or server, can adjust the expected communication distance associated with the first node based on the first type of context data. In one example, the expected communication distance could be a theoretical broadcast distance based on the device's radio parameters. Such an expected communication distance is known because it is an estimate of the radio range. In one example, the adjusted communication distance includes an expected reduced range distance for transmissions from the first node. In another example, the adjusted communication distance includes an expected reduced receiver sensitivity distance for the first node.

[0424] In another example, communication distance can be adjusted by the network device adaptively adjusting the communication distance based on signal degradation information and a second type of context data. In other words, the communication distance can be adjusted based on signal degradation information taken into account along with other types of context data, such as how the first node is moved (e.g., the expected movement of the first node along its predicted transmission path) or the density of other nodes near the first node.

[0425] At step 2215, the network device determines the location of the first node based on the adjusted communication distance. In a further embodiment, the method may also update the adjusted communication distance by the network device based on the movement of the first node, and the updated adjusted communication distance may be used to refine the location of the first node. This may occur if the first node is a mobile master node capable of determining its own location.

[0426] Those skilled in the art will understand that the method 2200, as disclosed and explained above in various embodiments, can be used in network devices (e.g., Figure 4 Example master node 110a or Figure 5Implemented on server 100, the network devices execute one or more portions of their respective control and management code to perform the steps of method 2200 as described above. Such code can be stored on a non-transitory computer-readable medium such as memory storage device 415 on master node 110a or memory storage device 515 on server 100. Therefore, when such code is executed, the processing unit of the corresponding network device can be operable to perform operations or steps from the exemplary methods disclosed above, including method 2200 and variations thereof.

[0427] More specifically, an exemplary network device apparatus is used to determine the location of a first node in a wireless node network based on context data. The exemplary network device may include a processing unit, volatile memory coupled to the processing unit, and a memory storage device coupled to the processing unit. The exemplary network device further includes a communication interface coupled to the processing unit, and the communication interface provides a communication path operatively coupling the network device to the first node in the network.

[0428] The memory storage device used in this device maintains at least a program code segment and context data containing at least signal degradation information. As a type of context data, such signal degradation information is information about how the second node will operate in an environment similar to the first node's neighboring environment when the second node is of a similar type to the first node. Examples of signal degradation information can include those discussed above with respect to step 2205 of method 2200.

[0429] When residing in volatile memory, the processing unit of the network device is operable to perform the steps mentioned and described above with respect to method 2200 when executing at least a program code segment. More specifically, the processing unit is operable to connect at least to the memory storage device to access signal degradation information, adjust the communication distance associated with the first node (if necessary) based on the signal degradation information, determine the location of the first node based on the adjusted communication distance, and store the determined location of the first node as location data in the memory storage device.

[0430] Adjusting the communication distance via the processing unit can be accomplished as described above in step 2210 of method 2200. Furthermore, as mentioned above, the processing unit can be further operable to adaptively adjust the communication distance, taking into account other types of contextual data, such as movement and anticipated node movement as described above.

[0431] In a further embodiment, the network device may include a positioning circuit (such as...). Figure 4The exemplary master node 110a shown is a mobile master node with GPS circuitry 475. In this embodiment, the processing of the network device can be further operable to determine the location of the network device based on the output signal from the positioning circuitry received by the processing unit, and to determine the location of the first node based on the adjusted communication distance and the location of the network device. Accordingly, a first type of contextual data related to the vicinity of the first node is based on the determined location of the first node.

[0432] Those skilled in the art will also appreciate that in some operating environments, in this embodiment, signal degradation information may not require any adjustment to the communication distance. However, in other environments (e.g., adverse RF environments), in this embodiment, signal degradation information can provide a basis for adjusting the communication distance, even if not performed every time. Therefore, adjustment of the communication distance may not need to be performed in all neighboring environments of the first node, but can be performed based on the neighboring environment of the first node if necessary. The embodiment's ability to adjust the communication distance when needed and when required advantageously allows for more accurate positioning of the first node.

[0433] Positioning by triangulation

[0434] In some embodiments, various methods for determining node locations may rely at least in part on triangulation techniques. In other words, as wireless node networks collect data on receiver-transmitter pairs, other methods for determining the location of individual nodes, at least in part, using triangulation, may become possible. Figure 15 This is a diagram illustrating an exemplary location determination performed by triangulation within a wireless node network according to an embodiment of the present invention. Referring now... Figure 15 The illustrated embodiment shows three exemplary master nodes M1-M3910a-910c, each with a known location. Exemplary ID nodes AE 920a-920e are also shown, which are within communication range of at least one or more of the exemplary master nodes MA-M3910a-910c.

[0435] In the illustrated example, master nodes M1-M3 can detect and collect advertisement messages from ID node AE ​​at varying and known power levels. Master nodes M1-M3 forward the captured information to backend server 100, where location determination can be performed. For example, factors such as RSSI and the visibility of each node at each power level can be used to determine the location of nodes where sufficient information is available with greater accuracy.

[0436] For an exemplary system that performs triangulation on nodes, three nodes with known locations must have already seen the broadcasting node. In this example, two advertising ID nodes, A 920a and B 920b, are seen by three nodes (master nodes M1-M3910a-910c) with known locations. Based on the captured information, the locations of ID nodes A 920a and B 920b are calculated.

[0437] Chain triangulation

[0438] In another embodiment, a node with an inferred location can be used in conjunction with triangulation techniques to determine the location of another node in a wireless node network. Figure 16 This is a diagram illustrating an exemplary position determination performed by chain triangulation according to an embodiment of the present invention. The positions of ID nodes A 920a and B 920c have been determined by triangulation across master nodes M1-M3, as shown in... Figure 15 The exemplary embodiments illustrated herein. However, as shown... Figure 16 As illustrated in the diagram, the location of ID node C 920c can also be determined according to the embodiment.

[0439] For example, an exemplary method for determining node positions using chain triangulation begins by determining the calculated position of ID node B 920b (as referenced). Figure 15 (As explained). Next, a node closer to ID node B 920b can be used to obtain the vanishing third signal point required for triangulation. This can be achieved by placing ID node B 920b in query (scan) mode so that it listens for messages from ID node C 902c. ID node C is instructed to advertise, thus providing a signal that can be captured by ID node B. After capturing the signal profile of C, ID node B can communicate or share the captured information and forward it to backend server 100 via one of the master nodes M1 or M2. The obtained position determination of ID node C 920c may have a higher level of position error because it is based in part on the calculated reference (e.g., the position of ID node B), but the lever position determination of ID node C 920c can be accurate enough (or an actionable position) to allow the collection of useful information about ID node C 920c. For example, the lever or chain position of ID node C can be determined by using context data indicating that nodes M1, M2 and ID node B are all close enough to ID node C, and ID node C is determined to be within the same command nodes M1, M2 and ID node B.

[0440] Positioning via Proximity-to-Triangulation (LP2T)

[0441] As explained above, in embodiments where chain triangulation can determine location via proximity-to-triangulation (LP2T), the starting point can be based on a proximity method to determine the relative position of the ID node to the master node. However, once the relative position of the ID node has been determined, a more accurate or refined position of the ID node can be determined based on the positions of all master nodes capable of capturing the RF output signal broadcast from the ID node, and then triangulation is performed based on the observed signal strength of the ID node. In this example, the proximity-based position is used as input in the triangulation calculation to estimate the likely signal degradation observed historically between the node at the proximity-determined position and the scanning master node. In further embodiments, more accurate triangulation can be possible by considering historical data on signal degradation patterns, resulting in more accurate position determination.

[0442] Figure 23 This is a flowchart illustrating an exemplary method for determining the location of one of a plurality of nodes in a wireless node network having a server using chain triangulation, according to an embodiment of the present invention. Such exemplary node locations do not need to be precise or exact, but can be sufficiently accurate without absolute values.

[0443] Now for reference Figure 23 Method 2300 begins at step 2305, where the server receives the location of the first node from the first node. Next, at step 2310, the server receives the location of the second node from the second node. For example, refer to... Figure 16 In the example shown, master nodes M1910a and M2910b can transmit their respective position coordinates from their respective airborne positioning circuits to the server, so that the server has the current position of the two master nodes.

[0444] At step 2315, the server infers the location of the third node. For example, in Figure 16 In the example illustrated, the server can infer the location of ID node B 920b. In one embodiment, the inference may include enabling the server to determine the proximity-based location of a third node relative to another node with a known location, such that the proximity-based location is used as the inferred location of the third node.

[0445] In another embodiment, inferring the position of the third node may include having the server determine the relative position of the third node with respect to the first node (as a node with a known position) or with respect to the second node (as another node with a known position). In another embodiment, method 3300 may further include having the server adjust the inferred position of the third node to determine a refined position of the third node based on third node context data associated with the inferred position of the third node.

[0446] At step 2320, method 2300 ends with the server performing triangulation on the position of a node based on the determined distances to each of the first and second nodes, and the determined distances from the node to the inferred position of the third node.

[0447] In a more detailed embodiment, method 2300 can triangulate the position of a node by accessing first node context data related to the context environment near the first node and second node context data related to the context environment near the second node. Such context environment may include an environment on a conveyor system, within a specific facility, or adjacent to material that may degrade or shield signals received by a node. Next, more detailed triangulation may allow the server to adjust the determined distance from the node to the first node's position based on the first node context data to provide a refined distance from the node to the first node's position. The server can then triangulate the position of a node based on the adjusted determined distance from the node to the first node's position, the adjusted determined distance from the node to the second node's position, and the refined determined distance from the node to the third node's position.

[0448] In a further embodiment, method 2300 may also cause the server to transmit instructions to cause a node to broadcast multiple announcement signals over a period of time. In such an embodiment, the determined distance from the location of the first node to the location of the first node may be based on signals captured by the first node from the first node over a period of time and reported by the first node to the server. In another embodiment, the determined distance from the location of the first node to the location of the second node may be based on signals captured by the second node from the first node and reported by the second node to the server.

[0449] In yet another embodiment, the server may transmit instructions to cause the node to broadcast multiple announcement signals at different power levels. In such an embodiment, the determined distance from the location of the node to the first node may be based on signals captured by the first node from the node and reported to the server by the first node. In another embodiment, the determined distance from the location of the node to the location of the second node may be based on signals captured by the second node from the node and reported to the server by the second node.

[0450] In another embodiment, method 2300 may also enable the server to transmit location information to a requesting entity (e.g., another node, user access device, etc.) when it receives a request for the location of a node.

[0451] Those skilled in the art will appreciate that the method 2300, as disclosed and explained above in various embodiments, can be implemented in one or more portions of operational control and management code (such as code 525) on a server (such as in...) to achieve any of the above-described functions. Figure 5 This code is implemented on his exemplary server 100. Such code can be stored on a non-transitory computer-readable medium (such as memory storage device 515 in the exemplary server). Therefore, when such code is executed, the server's processing units (such as unit 500) can be operated to perform operations or steps from the exemplary methods disclosed above, including method 2300 and variations thereof.

[0452] The embodiments also describe a server apparatus for determining the location of one of a plurality of nodes in a wireless node network using chained triangulation. The server apparatus typically includes a server processing unit, server volatile memory, server memory storage device, and a communication interface. The server volatile memory, server memory storage device, and communication interface are each configured in a device such as coupled to the server processing unit. The server memory storage device maintains at least program code segments and location data associated with nodes in the network. In some embodiments, the server memory storage device may also maintain context data, such as first node context data and second node context data. The communication interface provides a communication path operatively coupling the server to nodes in the network, such as the first and second nodes.

[0453] When at least the program code segment residing in the server's volatile memory is executed, the server processing unit is operable to perform various functions, such as those described in the steps above related to method 2300. Specifically, the server processing unit is operable to receive a request for the location of a node via a communication interface. Based on the request, the server processing unit is then operable to receive the corresponding locations of the first and second nodes and store the locations as part of location data held in the server's memory storage device. The server processing unit is further operable to infer the location of a third node and store the inferred location of the third node as part of the location data held in the server's memory storage device. The server processing unit is then operable to triangulate the location of a node based on a determined distance from the location of the first node, a determined distance from the location of the second node, and a determined distance from the inferred location of the third node. Finally, the server processing unit is operable to transmit location information to the requesting entity via the communication interface in response to the request.

[0454] In one embodiment, the server processing unit may be further operable to infer the position of a third node by operablely determining the proximity-based position of the third node relative to another node having a known position, wherein the proximity-based position is used as the inferred position operation of the third node.

[0455] In another embodiment, the server processing unit may be further operable to transmit instructions via a communication interface to cause a node to broadcast multiple announcement signals over a period of time. In this embodiment, the determined distance from the location of the first node to the location of the first node may be based on signals captured by the first node from the first node and reported to the server by the first node over a period of time. Alternatively, the determined distance from the location of the first node to the location of the second node may be based on signals captured by the second node from the first node and reported to the server by the second node.

[0456] In another embodiment, the server processing unit may be further operable to transmit instructions via a communication interface to cause a node to broadcast multiple announcement signals at different power levels. In such an embodiment, the determined distance from the location of the first node to the location of the first node may be based on signals captured by the first node from the first node and reported to the server by the first node. Alternatively, the determined distance from the location of the first node to the location of the second node may be based on signals captured by the second node from the first node and reported to the server by the second node.

[0457] In yet another embodiment, the server processing unit may be further operable to infer the position of the third node by operablely determining the relative position of the third node with respect to the first node or alternatively with respect to the second node.

[0458] In yet another embodiment, the position can be refined using context data. More specifically, the server processing unit can be further operable to adjust the inferred position of the third node to determine the refined position of the third node based on the third node context data associated with the inferred position of the third node.

[0459] In a more detailed embodiment, the server memory storage device may further maintain context data, and the server processing unit may be further operable to perform triangulation by accessing first node context data, which is part of the context data maintained on the server memory storage device, wherein the first node context data is related to the context environment near the first node. Similarly, the server processing unit may be further operable to access second node context data, which is part of the context data maintained on the server memory storage device, wherein the second node context data is related to the context environment near the second node. The server processing unit may then be operable to adjust the determined distance from the node to the first node based on the first node context data to provide a refined distance from the node to the first node. Accordingly, the server processing unit may be operable to triangulate the position of a node based on the adjusted determined distance from the node to the first node, the adjusted determined distance from the node to the second node, and the determined distance from the node to the refined position of the third node.

[0460] Combinatorial methods for determining node positions

[0461] Given the examples for locating nodes explained above, those skilled in the art will appreciate that, when determining the refined location of nodes in a wireless node network, further embodiments explicitly consider using more than one of the aforementioned location determination techniques. For example, such a combined embodiment may apply an ordered or prioritized approach, thereby applying a first location technique to generate first location information about the location of a node in the wireless network. Subsequently, a second location technique may be selected from a set of ranked or prioritized techniques (some of which may work better in certain situations and are selected or dynamically prioritized based on context), and applied to generate second location information about the node's location or to refine the node's location. Other embodiments may apply additional location techniques to generate further refined location information.

[0462] In embodiments, information in the exemplary hierarchy typically identifies which technology might initially be preferred, and when other positioning technologies are applied in sorting groups or lists. Such information in the exemplary hierarchy may be fixed (based on historical data and experience of success), or may change dynamically over time as nodes move relative to each other, for example, based on contextual data that provides more information relative to the current or expected context.

[0463] Environmental anomaly detection and response mediation actions

[0464] Utilizing these types of hierarchical node elements and their association, location, and communication capabilities as part of further exemplary wireless node networks, various additional embodiments relate to node-based technical solutions that enhance and improve how to detect and automatically respond to hazardous conditions caused by environmental anomalies, such as fires, explosions, chemical leaks, radiation leaks, or combinations of environmental conditions indicating multiple environmental anomalies. Detecting such environmental anomalies and automatically generating alarms that selectively initiate different types of mediation responses can be performed in situations such as transporting packages in shipping containers of transport vehicles (such as aircraft). Accordingly, those skilled in the art will appreciate that the above-described basis of wireless node networks can be used and extended as part of embodiments of the systems, apparatus, and methods described below for improving environmental anomaly detection, enhanced hierarchical alarms for associated target mediation receivers, and initiating different types of mediation responses to such environmental anomalies using one or more elements of an adaptive, context-aware wireless node network.

[0465] Generally speaking, Figures 24A-24C The illustrations depict various general examples of systems that use exemplary wireless node network elements to detect environmental anomalies. More detailed, Figure 24A This is a diagram illustrating an exemplary wireless node network for detecting environmental anomalies using a command node and multiple ID nodes disposed within a shipping container, according to an embodiment of the present invention. Now refer to... Figure 24A An exemplary system 24000 is illustrated for monitoring a shipping container 24300 transported by a transport vehicle 24200 within a transport vehicle warehouse 24205. The shipping container 24300 is shown as maintaining packages 24400a-24400c and is being monitored for environmental anomalies by the system 24000 using a wireless node network. Such a system 24000 has multiple ID nodes 24120a-24120c disposed within the shipping container 24300, along with a command node 24160 installed to and associated with the shipping container 24300. In some embodiments, each of the ID nodes 24120a-24120c may be implemented with at least one environmental sensor (e.g., sensor 360). However, in other embodiments, the ID nodes 24120a-24120c do not need to include sensors because the command node can monitor the functionality of a particular ID node (rather than sensor data generated by the ID node) as part of detecting environmental anomalies.

[0466] In some embodiments, each of ID nodes 24120a-24120c may be specifically associated with one of the packages 24400a-24400c maintained within the shipping container 24300 (e.g., traveling with one of the packages, being secured to the outside or inside of one of the packages, or integrated as part of one of the packages). However, in other embodiments, ID nodes 24120a-24120c do not need to be specifically part of or associated with a particular package 24400a-24400c, and instead are located at different locations within the shipping container 24300.

[0467] Command node 24160 is a type of master node that can be implemented without self-localization circuitry (e.g., GPS positioning circuitry 475), but some embodiments of command node 24160 can be implemented as a self-localizing master node 110a as described above. Accordingly, and in embodiments involving the detection of environmental anomalies, command node 24160 is operable to communicate with each of the ID nodes 24120a-24120c within the shipping container 24300 and with the external transceiver 24150 located within and associated with the transport vehicle 24200.

[0468] In some embodiments, the external transceiver 24150 may be implemented without being specifically associated with the transport vehicle 24200. For example, an example of the external transceiver 24150 may be implemented by a handheld wireless communication device, such as the exemplary user access devices 200, 205 as explained above, which may be implemented by: computers, laptop computers, tablet devices (such as Apple devices). Touchscreen tablet devices), personal area network devices (such as...) Devices), smartphones (such as Apple) ), smart wearable devices (such as the Sumsang Galaxy Gear) TM Smartwatch or Google Glass TM Wearable smart optical devices, or other such devices capable of communicating with a remote server 24100 via a network 24105, which connects to the command node and ID node described herein via wired or wireless communication paths. Furthermore, the exemplary external transceiver 24150 may be a mobile device designed for easy movement (such as a tablet or smartphone), and may be a non-mobile device designed for operation from a fixed location (such as a desktop computer mounted on a transport vehicle 24200).

[0469] As explained in more detail below, embodiments of external transceiver 24150 can receive alarm notifications from command node 24160 and automatically respond to such alarms by initiating mediation responses associated with specific mediation actions based on detected specific environmental anomalies. Some responses may cause external transceiver 24150 to trigger fire suppression systems on transport vehicle 24200 and / or communicate with operators or logistics personnel on transport vehicle 24200 using display interfaces on the transceiver (e.g., LCD displays, touchscreen displays, status lights, speakers) and user input interfaces on the transceiver (e.g., touchscreen interfaces, buttons, keys, switches, microphones, or other feedback input devices). Furthermore, external transceiver 24150 can communicate with remote control center server 24100 via network 24105 to report detected environmental anomalies and any initiated mediation responses, as well as to receive information regarding packages 24400a-24400c, environmental threshold conditions associated with such packages, and other updated data for detecting environmental anomalies and initiating mediation responses. Accordingly, any alerts and user input regarding environmental anomalies can take the form of visual, auditory, or electronic messages (e.g., alerts on a visual screen on the external transceiver 24150, audible alarms as alerts, or electronic messages regarding anomalies and / or initiating response mediation actions).

[0470] In a further embodiment, command node 24160 may be able to send alarm notifications directly to onboard systems (such as displays in the cockpit or logistics support area of ​​transport vehicle 24200, or onboard fire suppression systems on transport vehicle 24200) without involving a separate external transceiver that receives the alarm notification and responds by initiating a mediation action in communication with such an onboard system. Thus, some embodiments may deploy exemplary onboard systems involving mediation actions, wherein the system can be considered to have a built-in communication interface that operates as a type of external transceiver, utilizing this external transceiver to communicate with command node 24160 of a specific shipping container 24300. Additional embodiments may also deploy transceiver 24150 inside the shipping container, or the command node and the internal transceiver initiating the mediation response action may be the same node-based transceiver device.

[0471] As noted above, each of ID nodes 24120a-24120c can be specifically associated with a package, or can be placed in different locations within shipping container 24300. More specifically, although... Figure 24AThe illustration shows a system 24000 according to different embodiments of the present invention, which uses command nodes 24160 and ID nodes 24120a-24120c disposed within a shipping container 24300, however Figure 24B This is an illustration of an exemplary system 24005, which uses command nodes 24160 and ID nodes 24120a-24120c to detect environmental anomalies on or within packages 24400d-244400f transported in shipping containers 24300, such as those placed in a warehouse 24205 of a transport vehicle 24200. In this manner, sensor data generated by each of the ID nodes 24120a-24120c deployed in system 24005 can be sensor data specific to the internal environmental conditions relating to a particular package (i.e., packages 24400d-24400f), while sensor data generated by each of the ID nodes 24120a-24120c deployed in system 24000 can be sensor data more specific to the environmental conditions adjacent to or outside a particular package (i.e., packages 24400d-24400f).

[0472] Furthermore, Figure 24C This is a diagram of yet another exemplary wireless node network according to an embodiment of the present invention. This exemplary wireless node network implements an exemplary system 24010 for detecting environmental anomalies using command nodes 24160 and ID nodes 24120a-24120f, which are less concentrated on specific packages and more geographically dispersed within shipping containers. Thus, Figure 24C The embodiment shown deploys ID nodes 24120a-24120f, so that different ID nodes are present in different parts of the shipping container 24300, allowing each ID node to monitor different spatial areas of the shipping container 24300.

[0473] Although Figures 24A-24C The exemplary transport vehicle 24200 is illustrated in general; however, those skilled in the art will appreciate that the embodiments may implement the exemplary transport vehicle 24200 as an aircraft, motor vehicle, rail transport vehicle, sea vessel, or other road transport vehicle (e.g., tractor trailer, etc.) capable of transporting containers to hold the shipped parcels. The shipment of containerized parcel groups (e.g., ULD-type containers manufactured to optimize air logistics handling of parcels) is an example of how mobile storage units (such as movable ULD containers) can be deployed when shipping node parcels in an air transport environment. For example, Figure 25AThis is an illustration of multiple shipping containers in the form of exemplary ULD containers 24300a-24300d, such as those loaded into a cargo warehouse of an aircraft according to an embodiment of the present invention. Referring now to FIG25, a cross-sectional perspective view of an exemplary aircraft fuselage 25000 is illustrated. In particular, the exemplary floor 25005 of the cargo storage area (a type of transport vehicle warehouse 24205) within the fuselage 25000 is shown as having multiple roller elements that facilitate the movement of goods within the cargo area. Additionally, although Figure 25A Not shown, but cargo storage areas and floor 25005 typically include structures and anchor points to help hold any cargo loaded within fuselage 25000. The cargo storage area within the exemplary fuselage 25000 can be divided into upper and lower areas by an additional floor 25008.

[0474] Figure 25A The cross-sectional perspective view shown in the figure illustrates the lower cargo area, which illustrates various ULD containers 24300a-24300d along with an exemplary air transport external transceiver 24150 on the aircraft. The exemplary external transceiver 24150 can be implemented using a master node or other wireless transceivers outside the ULD containers 24300a-24300d and is operable to communicate with a command node within each of the respective ULD containers 24300a-24300d as part of an embodiment for detecting environmental anomalies within such containers. While the exemplary external transceiver 24150 is shown as being located in the cargo storage area of ​​the aircraft, those skilled in the art will appreciate that other embodiments may place the external transceiver 24150 in another part of the aircraft (such as in the cockpit area or logistics support area), provided that it is deployed and configured to communicate with a command node within each of the respective ULD containers 24300a-24300d. Similar to... Figures 24A-24C As shown, Figure 25A The external transceiver 24150 shown in the diagram can communicate with a remote server (such as a remote control center server 24100) located outside the aircraft to, for example, report any detected environmental anomalies and receive updated information about cargo or related logistics transportation information, which can be used to help assess potential mediation response actions to be taken on the aircraft.

[0475] A further embodiment may have an exemplary external transceiver 24150 that is operatively communicable with other systems on the aircraft, such as a fire suppression system, which may be automatically triggered by the external transceiver 24150 in response to an alarm notification from one or more command nodes within ULD containers 24300a-24300d on the transport vehicle (e.g., an aircraft) for deployment. Figure 25B This is an illustration of multiple exemplary shipping containers in a cargo storage area of ​​an aircraft according to an embodiment of the present invention. The aircraft has an onboard exemplary fire suppression system that is selectively and responsively deployed as part of a possible targeted mediation response to environmental anomalies detected in one or more shipping containers. Reference now is made to... Figure 25B An exemplary fire suppression system 25010 is illustrated as having a corresponding deployable fire suppression module for each ULD container 24300a-24300d. Each module of the exemplary fire suppression system 25010 can be selectively activated using a signal to a controller that initiates a pressurized injection of extinguishing agent from an extinguishing agent storage chamber into its corresponding ULD container. This can be achieved using an articulated puncture device that forcefully creates an opening in the surface of the corresponding ULD container, through which the extinguishing agent can flow into the ULD container, thereby addressing an environmental anomaly detected within the ULD container. A more detailed embodiment of such an exemplary fire suppression system 25010 is described in U.S. Patent No. 9,901,764, assigned to FedEx Corporation, which is hereby incorporated by reference.

[0476] In a further embodiment, the exemplary external transceiver may be housed in other parts of the aircraft operated by aircraft personnel (e.g., as a pilot operator or logistics support staff) and may have one or more displays (e.g., screens, status lights, touchscreens for prompting messages) and user input interfaces (e.g., buttons, switches, keys, etc. for receiving feedback input). Figure 25C This is a diagram illustrating further exemplary external transceivers disposed in various control compartments of an exemplary aircraft transport vehicle according to an embodiment of the present invention. Referring now to... Figure 25C An exemplary aircraft 25100 is typically shown with a cockpit compartment 25105 at the forward of the aircraft 25100 and a cargo storage compartment 25110 within the fuselage of the aircraft 25100. In the illustrated embodiment, the cargo storage compartment 25100 includes an internal loading storage area 25120 (similar to...). Figure 25AAs shown in the cross-sectional view, goods / parcels to be shipped or transported can be loaded therefore for transport, and such goods are temporarily maintained there during transport. For example, ULD containers 24300a and 24300b are shown as secured within internal shipping storage area 25120. Additionally, palletized shipping items (PSI) 25300a-25300d are secured to pallets 25150 as another type of shipping container maintained within internal shipping storage area 25120. In the illustrated embodiment, cargo storage compartment 25110 also includes a logistics support area 25115 where logistics support personnel can be located, and in response to the detection of environmental anomalies, such personnel can be prompted from logistics support area 25115 to inspect one or more containers within area 25120.

[0477] Within cockpit compartment 25105, embodiments may include a cockpit transceiver 25150a, as a type of external transceiver operable to communicate with command nodes in shipping containers on the aircraft (transfer ULD containers 24300a, 24300b or command nodes associated with palletized PSIs 25300a-25300d fixed to pallets 25150). Accordingly, the command node for a specific shipping container can generate a tiered alarm notification to cockpit transceiver 25150a, which will identify the pilot operator working in cockpit compartment 25105 as a target mediator recipient to be notified of specific detected environmental anomalies regarding the shipping container. Similarly, the embodiment may alternatively or may also have a logistics transceiver 25150b as a type of external transceiver operable to communicate with command nodes in shipping containers on the aircraft (such as ULD containers 24300a, 24300b or command nodes associated with palletized PSIs 25300a-25300d fixed to pallets 25150). Accordingly, the command node of a particular shipping container can generate a tiered alert notification to the logistics transceiver 25150a, which identifies logistics personnel work...

Claims

1. An adaptive wireless node network system for detecting environmental anomalies associated with a shipping container and reporting layered alert notifications to an external transceiver associated with a transport vehicle transporting the shipping container, the system comprising: a set of wireless ID nodes disposed within a shipping container, wherein at least a portion of the ID nodes are associated with one or more objects being transported within the shipping container; A master command node disposed within a shipping container, the master command node being configured to: Monitor signal activity from ID nodes, Responsively identify environmental anomalies based on monitoring signal activity from ID nodes, responsive to identifying an environmental anomaly of the shipping container, generating a hierarchical alert notification associated with the environmental anomaly of the shipping container, wherein the hierarchical alert notification identifies a target mediation recipient, identifies a target mediation action, and establishes a mediation response priority, and transmitting a hierarchical alert notification to an external transceiver to initiate a mediation response associated with a target mediation action; and A designated survivor command node is mounted to a shipping container, the designated survivor command node being configured to communicate with a primary command node and to operate as a primary command node when the designated survivor command node is unable to communicate with the primary command node.

2. The system according to claim 1, wherein: The designated survivor command node includes a container node that is mounted to a shipping container and is operable to communicate directly with an ID node positioned inside the shipping container and directly with an external transceiver associated with a transport vehicle.

3. The system according to claim 2, wherein: The master command node is installed into a predetermined location within the shipping container.

4. The system according to claim 2, wherein: The master command node is removably mounted to a predetermined location within the shipping container.

5. The system according to claim 4, wherein: The master command node includes a mobile master node disposed in a shipping bag within or on the shipping container.

6. The system according to claim 2, wherein: The primary command node is associated with the object being transported within the shipping container.

7. The system according to claim 1, wherein: The master command node includes a container node that is mounted to a shipping container and is operable to communicate directly with an ID node positioned inside the shipping container and directly with an external transceiver associated with a transport vehicle.

8. The system according to claim 7, wherein: The designated survivor command node is installed into a predetermined location within the shipping container.

9. The system according to claim 8, wherein: The designated survivor command node includes a mobile master node disposed in a shipping bag within or on the shipping container.

10. The system according to claim 7, wherein: The designated survivor command node is associated with the object being transported within the shipping container.

11. An enhanced shipping container apparatus having integrated fire suppression and for use in maintaining a plurality of packages, the enhanced shipping container apparatus comprising: the portion of the container base that supports the package; a plurality of container walls, an edge of each container wall coupled to the container base portion; as well as a container top portion coupled to another edge of each container wall; wherein the container base portion, the container wall and the container top portion together define an interior storage space for maintaining packages; wherein at least one of the container walls provides a resealable access closure providing selective access to the interior storage space; as well as A fire extinguishing panel integrated as part of one of the group consisting of a container wall and a container roof portion, said fire extinguishing panel comprising: Supporting sheet made of refractory material, Internal exposed sheets made of temperature sensitive materials, a sealing border connecting the support sheets and the interior exposed sheets at a peripheral edge of each of the support sheets and the interior exposed sheets, wherein the combination of the sealing border and the support sheets and the interior exposed sheets defines a retention cavity; and an integrated fire extinguishing material occupying the entire holding cavity within the fire extinguishing panel from the supporting sheet to the internal exposed sheet; and Wherein when the temperature sensitive material of the internally exposed thin sheet is exposed to a threshold temperature, the temperature sensitive material of the internally exposed thin sheet releases the integrated fire extinguishing material from within the holding cavity.

12. The device according to claim 11, wherein When the temperature sensitive material is exposed to heat from a fire, the temperature sensitive material of the interior exposed sheet releases the integrated fire extinguishing material within the retention cavity.

13. The device according to claim 11, wherein: When the temperature sensitive material is exposed to heat from the explosion, the temperature sensitive material of the inner exposed sheet releases the integrated fire extinguishing material within the retention cavity.

14. The device according to claim 11, wherein: When the temperature sensitive material is exposed to heat caused by the chemical condition, the temperature sensitive material of the internal exposed sheet releases the integrated fire extinguishing material within the retention cavity.

15. The device according to claim 11, wherein The container top portion implements a first fire extinguishing panel, and wherein a plurality of other ones of the container walls implement a plurality of other fire extinguishing panels.

16. The device according to claim 11, wherein The temperature sensitive material of the interior exposed sheet releases the integrated fire extinguishing material from the holding cavity by failing to contain the integrated fire extinguishing material within the holding cavity when the temperature sensitive material melts upon exposure to the threshold temperature.

17. The device according to claim 11, wherein: When the temperature sensitive material releases the integrated fire extinguishing material in response to decomposition of the temperature sensitive material due to a thermal environment exceeding a threshold temperature, the temperature sensitive material of the internally exposed sheet releases the integrated fire extinguishing material from the holding cavity by failing to contain the integrated fire extinguishing material within the holding cavity.

18. The device according to claim 17, wherein: The integrated fire extinguishing material is released from the holding cavity into the interior storage space and onto at least a portion of the package.

19. A node-enabled battery system with integrated environmental detection and reporting, the system comprising: Battery; A sensor-based node attached to a battery, the sensor-based node comprising, Node processor, a node memory storage device coupled to the node processor, the node memory storage device maintaining at least a battery monitoring program code and a battery threshold metric value, a wireless communication interface coupled to the node processor, and a sensor coupled to the node processor, the sensor operable to sense a battery state condition of the battery; and The node processor is programmatically configured to, when executing the battery monitoring program code, operate to receiving status data from the sensor, the status data reflecting a battery status condition sensed by the sensor, automatically triggering generation of a tiered battery-related alert notification when the received status data is inconsistent with a battery threshold metric value, wherein the tiered alert notification identifies a target mediation action as a mediation response based on the degree to which the received status data is inconsistent with the battery threshold metric value, and The wireless communication interface is caused to broadcast a hierarchical alert notification to initiate an identified target mediation action related to a battery status condition of the battery.

20. The system of claim 19, wherein: The battery status condition sensed by the sensor on the sensor-based node includes a state of charge condition of the battery.

21. The system of claim 20, wherein: The node processor is programmatically configured to be operable to automatically trigger generation of a tiered alert notification when the battery threshold metric value includes a threshold voltage value and when received status data regarding a state of charge condition of the battery is less than the threshold voltage value.

22. The system of claim 19, wherein: The battery status condition sensed by the sensor on the sensor-based node includes a temperature condition of the battery.

23. The system of claim 22, wherein: The node processor is programmatically configured to be operable to automatically trigger generation of a tiered alert notification when the battery threshold metric value includes a threshold temperature value and when received status data regarding a temperature condition of the battery exceeds the threshold temperature value.

24. The system of claim 19, wherein: The sensor coupled to the node processor includes one of a plurality of battery sensors positioned at different points on the battery; and Therein, the battery state condition sensed by each battery sensor on the sensor-based node includes a plurality of temperature conditions of the battery, each temperature condition being at a relatively different point of the battery at which the corresponding battery sensor is positioned.

25. The system of claim 24, wherein: The node processor is programmatically configured to be operable to receive status data by receiving individual status information from each battery sensor as status data.

26. The system of claim 25, wherein: The node processor is programmatically configured to be operable to automatically trigger the generation of a tiered alarm notification related to the battery by automatically triggering the generation of a tiered alarm notification related to the battery when at least one of the received individual status information reflects that at least one of the temperature conditions of the battery exceeds a threshold temperature value of the battery.

27. The system of claim 24, wherein: The node processor is programmatically configured to be operable to receive status data by receiving individual status information from each battery sensor as status data over a period of time, and Wherein the node processor is programmatically configured to be operable to automatically trigger the generation of a hierarchical alert notification by being further operable to: monitoring the individual status information received from each battery sensor during the time period to identify a relative change in the individual status information during the time period, and When at least one of the identified relative changes in the individual status information within the time period exceeds a time-based relative temperature change threshold of the battery, generation of a tiered alert notification related to the battery is automatically triggered.

28. The system of claim 19, wherein: The node processor is programmatically configured to, when executing the battery monitoring program code, be operable to automatically activate the sensor-based node from a low power mode when the received status data is inconsistent with a battery threshold metric value.

29. A blanket apparatus for enhanced detection of environmental anomalies relative to a shipping container temporarily maintaining a plurality of packages, the apparatus comprising: A detection blanket positioned adjacent to multiple packages; and A plurality of sensor-based ID nodes are integrated as part of a detection blanket in a geographically dispersed configuration relative to the detection blanket, wherein each sensor-based ID node includes ID node processor, An ID node memory coupled to the ID node processor, the memory maintaining at least an ID node monitoring program code, at least one environmental sensor configured to generate sensor data related to an environmental condition proximate to the environmental sensor, wherein the sensor data related to the environmental condition indicates an environmental anomaly when the generated sensor data is above a threshold condition of the at least one environmental sensor, and A radio transceiver operably coupled to the ID node processor, the radio transceiver being configured to access sensor data generated by at least one environmental sensor when the ID node processor executes the ID node monitoring program code, and to broadcast the sensor data in response to a reporting command from the ID node processor.

30. The device according to claim 29, wherein: The detection blanket selectively connects to a plurality of attachment points within the shipping container to physically restrict movement of packages within the shipping container.

31. The device according to claim 29, wherein: The detection blanket is selectively connected to one or more attachment points within the shipping container to at least partially restrict movement of the detection blanket disposed within the shipping container.

32. The device according to claim 29, wherein: The detection blanket includes a plurality of regions; and Wherein the geographically dispersed configuration of the sensor-based ID nodes relative to the detection blanket further includes a regionally dispersed configuration of the sensor-based ID nodes, wherein different ones of the sensor-based ID nodes are positioned and integrated into different areas within corresponding areas of the detection blanket.

33. The device according to claim 29, wherein: The detection blanket includes at least a first rigid sheet within which sensor-based ID nodes are integrated in a geographically dispersed configuration.

34. The device according to claim 33, wherein The detection blanket includes at least a second buffer sheet attached to a first surface of the first rigid sheet.

35. The device according to claim 34, wherein The detection blanket includes at least a third buffer sheet attached to the second surface of the first rigid sheet.

36. The apparatus of claim 29, wherein: The detection blanket comprises a webbing wherein each sensor-based ID node is integrated into a different portion of the webbing as part of a geographically dispersed configuration.

37. The device according to claim 36, wherein The webbing includes a cargo net having each sensor-based ID node embedded in a different portion of the cargo net.

38. The device according to claim 36, wherein The environmental sensors on at least one sensor-based ID node include a continuity sensor configured to generate sensor data indicating a damage status of a webbing portion associated with at least one sensor-based ID node, wherein the sensor data generated by the continuity sensor exceeds a threshold condition when the sensor data changes from a predetermined first state indicating that the webbing portion associated with at least one sensor-based ID node is not damaged to a second state indicating that the webbing portion associated with at least one sensor-based ID node has been broken.

39. A package command node for detecting environmental anomalies associated with a shipping package being transported within a shipping container on a shipping vehicle, the shipping vehicle having an external transceiver, the shipping container maintaining a plurality of sensor-based ID nodes, each sensor-based ID node generating sensor data from a different portion of the shipping container, the package command node comprising: A command node housing housed with the shipping package; a command node processor disposed within the command node housing; a command node memory coupled to the command node processor and within the command node housing, the command node memory maintaining at least packaged command node environmental detection program code; and a command node wireless transceiver communication interface disposed within the command node housing and operatively responsive to the command node processor, the command node wireless transceiver communication interface configured to communicate with each ID node and with external transceivers; and When executing the package command node environment detection program code, the command node processor of the package command node is programmatically configured to be operable to Detect sensor data broadcast from sensor-based ID nodes using the command node wireless transceiver communication interface, Responsively identifying environmental anomalies of the shipping container when detected sensor data from the sensor-based ID node indicates environmental conditions that exceed environmental thresholds, In response to identifying an environmental anomaly of the shipping container, generating an alert notification associated with the environmental anomaly of the shipping container, and The command node wireless transceiver communication interface is caused to transmit an alarm notification to an external transceiver to initiate a mediation response associated with the environmental anomaly.

40. The package command node of claim 39, further comprising at least one environmental sensor disposed with the shipping package and operably coupled to the command node processor, wherein: The at least one environmental sensor is operable to generate shipping package sensor data related to the shipping package; and Wherein the command node processor is programmatically configured to be operable to responsively identify an environmental anomaly of the shipping container by further being programmatically configured to responsively identify an environmental anomaly of the shipping container when at least one of detected sensor data from the sensor-based ID node and shipping package sensor data indicates an environmental condition that exceeds an environmental threshold.

41. The package command node of claim 39, wherein: The command node processor is programmatically configured to be operable to responsively identify an environmental anomaly of the shipping container by further being programmatically configured to responsively identify an environmental anomaly of the shipping container in at least one of the following circumstances: (a) detected sensor data from the sensor-based ID node indicates an environmental condition that exceeds an environmental threshold, and (b) when the detected sensor data from the sensor-based ID node does not include sensor data from at least a threshold number of sensor-based ID nodes.

42. The package command node of claim 39, wherein: The command node memory further maintains context data identifying the sensor-based ID nodes that are expected to broadcast among the sensor-based ID nodes; and Wherein the command node processor is programmatically configured to be operable to responsively identify an environmental anomaly of the shipping container by further being programmatically configured to responsively identify an environmental anomaly of the shipping container in at least one of the following circumstances: (a) detected sensor data from the sensor-based ID nodes indicates an environmental condition that exceeds an environmental threshold, and (b) when the detected sensor data from the sensor-based ID nodes expected to be broadcast based on the context data does not include sensor data from at least a threshold number of sensor-based ID nodes expected to be broadcast.

43. The package command node according to claim 42, wherein: The command node processor is further programmatically configured to be operable to receive context data from the external transceiver.

44. The package command node according to claim 43, wherein: The context data from the external transceiver is initially provided to the external transceiver by the remote server.

45. The package command node of claim 39, wherein: The command node housing is separately located within the shipping package to travel with the shipping package as it is transported within the shipping container.

46. ​​The package command node of claim 39, wherein: The command node housing is attached to the shipping package.

47. The package command node of claim 46, wherein: The command node housing is temporarily attached to the shipping package.

48. The package command node of claim 39, wherein: At least one sensor-based ID node is attached to another shipping package placed within the shipping container.

Images