Patent Description:
<CIT> discloses a vehicle with a monitoring system that can monitor a first zone of interest and a second zone of interest.

Accordingly, a need exists for automated item tracking mechanisms configured to automatically disable and/or enable wireless data transmissions to maximize the effectiveness of wireless item tracking mechanisms.

The present disclosure relates to a system for determining a location of one or more assets as defined in claim <NUM>.

Preferred embodiments are defined in the corresponding dependent claims.

The present disclosure further relates to a method for determining a location of an asset as defined in claim <NUM>.

Various embodiments are directed to systems and methods for tracking the location of containers and/or other assets via a plurality of beacons that may be configurable between a plurality of operating modes including an advertising mode, a listening mode, and a sleep mode. The various operating modes enables the beacons to be utilized in environments in which constant transmission of advertising data is not desirable (e.g., on aircraft), while enabling automatic location of the containers and/or assets during periods of time in which wireless data transmission is desirable.

Various embodiments of the present invention now will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the inventions are shown. Indeed, these inventions may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The term "or" is used herein in both the alternative and conjunctive sense, unless otherwise indicated. The terms "illustrative" and "exemplary" are used to be examples with no indication of quality level.

Embodiments of the present invention may be implemented in various ways, and include computer program products that comprise articles of manufacture. A computer program product may include a non-transitory computer-readable storage medium storing applications, programs, program modules, scripts, source code, program code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like (also referred to herein as executable instructions, instructions for execution, program code, and/or similar terms used herein interchangeably). Such non-transitory computer-readable storage media include all computer-readable media (including volatile and non-volatile media).

A non-volatile computer-readable storage medium as used herein may include a floppy disk, flexible disk, hard disk, solid-state storage (SSS) (e.g., a solid state drive (SSD), solid state card (SSC), solid state module (SSM)), enterprise flash drive, magnetic tape, or any other non-transitory magnetic medium, and/or the like. A non-volatile computer-readable storage medium may also include a punch card, paper tape, optical mark sheet (or any other physical medium with patterns of holes or other optically recognizable indicia), compact disc read only memory (CD-ROM), compact disc-rewritable (CD-RW), digital versatile disc (DVD), Blu-ray disc (BD), any other non-transitory optical medium, and/or the like. Such a non-volatile computer-readable storage medium may also include read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory (e.g., Serial, NAND, NOR, and/or the like), multimedia memory cards (MMC), secure digital (SD) memory cards, SmartMedia cards, CompactFlash (CF) cards, Memory Sticks, and/or the like. Further, a non-volatile computer-readable storage medium may also include conductive-bridging random access memory (CBRAM), phase-change random access memory (PRAM), ferroelectric random-access memory (FeRAM), non-volatile random-access memory (NVRAM), magnetoresistive random-access memory (MRAM), resistive random-access memory (RRAM), Silicon-Oxide-Nitride-Oxide-Silicon memory (SONOS), floating junction gate random access memory (FJG RAM), Millipede memory, racetrack memory, and/or the like.

A volatile computer-readable storage medium as used herein may include random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), fast page mode dynamic random access memory (FPM DRAM), extended data-out dynamic random access memory (EDO DRAM), synchronous dynamic random access memory (SDRAM), double information/data rate synchronous dynamic random access memory (DDR SDRAM), double information/data rate type two synchronous dynamic random access memory (DDR2 SDRAM), double information/data rate type three synchronous dynamic random access memory (DDR3 SDRAM), Rambus dynamic random access memory (RDRAM), Twin Transistor RAM (TTRAM), Thyristor RAM (T-RAM), Zero-capacitor (Z-RAM), Rambus in-line memory module (RIMM), dual in-line memory module (DIMM), single in-line memory module (SIMM), video random access memory (VRAM), cache memory (including various levels), flash memory, register memory, and/or the like. It will be appreciated that where embodiments are described to use a computer-readable storage medium, other types of computer-readable storage media may be substituted for or used in addition to the computer-readable storage media described above.

As such, the present invention may be implemented in apparatus, system, computing device, computing entity, and/or the like executing instructions stored on a computer-readable storage medium to perform certain steps or operations. However, embodiments of the present invention may also take the form of an entirely hardware embodiment performing certain steps or operations.

Examples of the present invention are described below with reference to block diagrams and flowchart illustrations. Thus, it should be understood that each block of the block diagrams and flowchart illustrations may be implemented in the form of a computer program product, an entirely hardware embodiment, a combination of hardware and computer program products, and/or apparatus, systems, computing devices, computing entities, and/or the like carrying out instructions, operations, steps, and similar words used interchangeably (e.g., the executable instructions, instructions for execution, program code, and/or the like) on a computer-readable storage medium for execution. For example, retrieval, loading, and execution of code may be performed sequentially such that one instruction is retrieved, loaded, and executed at a time. In some exemplary embodiments, retrieval, loading, and/or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and/or executed together. Thus, such embodiments can produce specifically-configured machines performing the steps or operations specified in the block diagrams and flowchart illustrations. Accordingly, the block diagrams and flowchart illustrations support various combinations of embodiments for performing the specified instructions, operations, or steps.

<FIG> provides an illustration of a system that can be used in conjunction with various embodiments of the present invention. As shown in <FIG>, the system includes one or more powered assets <NUM>, , and one or more containers <NUM>. The system may further include one or more non-powered assets <NUM> one or more items <NUM> (not shown), one or more mobile computing entities <NUM>, one or more tracking computing entities <NUM>, one or more Global Positioning System (GPS) satellites <NUM>, one or more location sensors <NUM>, one or more telematics sensors <NUM>, one or more information/data collection devices <NUM>, one or more networks <NUM>, and/or the like. Each of the components of the system may be in electronic communication with, for example, one another over the same or different wireless or wired networks including, for example, a wired or wireless Personal Area Network (PAN), Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), or the like. Additionally, while <FIG> illustrates certain system entities as separate, standalone entities, the various embodiments are not limited to this particular architecture.

In various embodiments, the term powered asset <NUM> is used generically. For example, a powered asset <NUM> may be a tug, tractor, truck, car, van, flatbed, vehicle, aircraft-pushback tractor, cargo loader, forklift, and/or the like. As will be recognized, in many cases, a powered asset <NUM> may be configured to push, pull, lift, or otherwise move a non-powered asset <NUM>. Further, each powered asset <NUM> may be associated with a unique powered asset identifier (such as a powered asset ID) that uniquely identifies the powered asset <NUM>. The unique powered asset ID may include characters, such as numbers, letters, symbols, and/or the like. For example, an alphanumeric powered asset ID (e.g., "AS445") may be associated with each powered asset <NUM>. In another embodiment, the unique powered asset ID may be a registration number or other identifying information/data assigned to the powered asset <NUM>.

<FIG> shows one or more computing entities, devices, and/or similar words used herein interchangeably that are associated with the powered asset <NUM>, such as an information/data collection device <NUM> or other computing entities. In general, the terms computing entity, entity, device, system, and/or similar words used herein interchangeably may refer to, for example, one or more computers, computing entities, desktop computers, mobile phones, tablets, phablets, notebooks, laptops, distributed systems, watches, glasses, beacons, key fobs, radio frequency identification (RFID) tags, ear pieces, scanners, televisions, dongles, cameras, wristbands, wearable items/devices, items/devices, kiosks, input terminals, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and/or any combination of devices or entities adapted to perform the functions, operations, and/or processes described herein. <FIG> provides a block diagram of an exemplary information/data collection device <NUM> that may be attached, affixed, disposed upon, integrated into, or part of a powered asset <NUM>. The information/data collection device <NUM> may collect telematics information/data (including location data) and transmit/send the information/data to the mobile computing entity <NUM>, the tracking computing entity <NUM>, and/or various other computing entities via one of several communication methods.

In one embodiment, the information/data collection device <NUM> may include, be associated with, or be in wired or wireless communication with one or more processors <NUM> (various exemplary processors are described in greater detail below), one or more location-determining devices or one or more location sensors <NUM> (e.g., Global Navigation Satellite System (GNSS) sensors), one or more telematics sensors <NUM>, one or more real-time clocks <NUM>, a J-Bus protocol architecture, one or more electronic control modules (ECM) <NUM>, one or more communication ports <NUM> for receiving telematics information/data from various sensors (e.g., via a CAN-bus), one or more communication ports <NUM> for transmitting/sending data, one or more RFID tags/sensors <NUM>, one or more power sources <NUM>, one or more information/data radios <NUM> for communication with a variety of communication networks, one or more memory modules <NUM>, and one or more programmable logic controllers (PLC) <NUM>. It should be noted that many of these components may be located in the powered asset <NUM> but external to the information/data collection device <NUM>. Thus, each of the components may be referred to individually or collectively as a powered asset computing entity.

In one embodiment, the one or more location sensors <NUM>, modules, or similar words used herein interchangeably may be one of several components in wired or wireless communication with or available to the information/data collection device <NUM>. Moreover, the one or more location sensors <NUM> may be compatible with GPS satellites <NUM>, such as Low Earth Orbit (LEO) satellite systems, Department of Defense (DOD) satellite systems, the European Union Galileo positioning systems, Global Navigation Satellite systems (GLONASS), the Chinese Compass navigation systems, Indian Regional Navigational satellite systems, and/or the like. Furthermore, the one or more location sensors <NUM> may be compatible with Assisted GPS (A-GPS) for quick time to first fix and jump starting the ability of the location sensors <NUM> to acquire location almanac and ephemeris data, and/or be compatible with Satellite Based Augmentation System (SBAS) such as Wide Area Augmentation System (WAAS), European Geostationary Navigation Overlay Service (EGNOS), and/or MTSAT Satellite Augmentation System (MSAS), GPS Aided GEO Augmented Navigation (GAGAN) to increase GPS accuracy. This information/data can be collected using a variety of coordinate systems, such as the Decimal Degrees (DD); Degrees, Minutes, Seconds (DMS); Universal Transverse Mercator (UTM); Universal Polar Stereographic (UPS) coordinate systems; and/or the like. Alternatively, triangulation may be used in connection with a device associated with a particular powered asset and/or the powered asset's operator and with various communication points (e.g., cellular towers or Wi-Fi access points) positioned at various locations throughout a geographic area to monitor the location of the powered asset <NUM> and/or its operator. The one or more location sensors <NUM> may be used to receive latitude, longitude, altitude, heading or direction, geocode, course, position, time, and/or speed information/data (e.g., referred to herein as telematics information/data and further described herein below). The one or more location sensors <NUM> may also communicate with the tracking computing entity <NUM>, the information/data collection device <NUM>, mobile computing entity <NUM>, and/or similar computing entities.

As indicated, in addition to the one or more location sensors <NUM>, the information/data collection device <NUM> may include and/or be associated with one or more telematics sensors <NUM>, modules, and/or similar words used herein interchangeably. For example, the telematics sensors <NUM> may include powered asset sensors, such as engine, fuel, odometer, hubometer, tire pressure, location, weight, emissions, door, and speed sensors. The telematics information/data may include, but is not limited to, speed data, emissions data, RPM data, tire pressure data, oil pressure data, seat belt usage data, distance data, fuel data, idle data, and/or the like (e.g., referred to herein as telematics data). The telematics sensors <NUM> may include environmental sensors, such as air quality sensors, temperature sensors, and/or the like. Thus, the telematics information/data may also include carbon monoxide (CO), nitrogen oxides (NOx), sulfur oxides (SOx), Ethylene Oxide (EtO), ozone (O <NUM>), hydrogen sulfide (H <NUM>S) and/or ammonium (NH <NUM>) data, and/or meteorological information/data (e.g., referred to herein as telematics data).

In one embodiment, the ECM <NUM> may be one of several components in communication with and/or available to the information/data collection device <NUM>. The ECM <NUM>, which may be a scalable and subservient device to the information/data collection device <NUM>, may have information/data processing capability to decode and store analog and/or digital inputs from powered asset systems and sensors. The ECM <NUM> may further have information/data processing capability to collect and present telematics information/data to the J-Bus (which may allow transmission to the information/data collection device <NUM>), and output standard powered asset diagnostic codes when received from a powered asset's J-Bus-compatible on-board controllers <NUM> and/or sensors.

Additionally, each powered asset <NUM> has one or more powered asset beacons <NUM> attached or affixed thereto. As will be recognized, a beacon may take many forms. For instance, a beacon may be a Bluetooth Low Energy (BLE) beacon (e.g., a URIBeacon, an AltBeacon, or an iBeacon), an RFID tag/sensor, a near field communication (NFC) device, a Wi-Fi device, and/or the like. The powered asset beacons <NUM> may include some or all of the following components: one or more input interfaces for receiving information/data, one or more output interfaces for transmitting information/data, a processor, a clock, memory modules, one or more sensors for sensing and detecting various information/data (e.g., wireless signal sensors), a camera, and a power source. The power source may be a source provided by the powered asset, an energy storage device (e.g., a battery, a supercapacitor, and/or the like), an energy harvesting device (e.g., a solar panel, a vibration energy harvester, a thermal energy harvester, a RF energy harvester, and/or the like), and/or the like. In one embodiment, each powered asset beacon <NUM> can store one or more unique identifiers, such as a global unique identifier (GUID), a universally unique identifier (UUID), a character string, an alphanumeric string, text string, and/or the like. The unique identifier may identify the associated powered asset <NUM> and/or powered asset beacon. Via various communication standards and protocols, the powered asset beacon <NUM> associated with the powered asset <NUM> can be communicated with, interrogated, read, and/or the like. For example, a container beacon <NUM> associated with a container <NUM> can communicate with the powered asset beacon <NUM> associated with the power asset <NUM> using multiple wireless communication standards and protocols, including Bluetooth, Wibree, NFC, Wi-Fi, ZigBee, and/or any other wireless protocol or standard. For example, the one or more powered asset beacons <NUM> may be configured to communicate with one or more container beacons <NUM> via one or more configurations as described in <CIT>. The one or more powered asset beacons <NUM> collective define a communication area within the powered asset <NUM> in which the container beacon <NUM> can communicate with one or more of the powered asset beacons <NUM>. Upon establishing a wireless communication connection with a threshold number of powered asset beacons <NUM> associated with a single powered asset <NUM>, the container beacon <NUM> may be determined to be associated with the powered asset <NUM>, as discussed in greater detail herein. The powered asset beacon <NUM> associated with the powered asset <NUM> may also be in direct or indirect communication with the tracking computing entity <NUM>, the information/data collection device <NUM>, mobile computing entity <NUM>, and/or similar computing entities over the same or different wired or wireless networks.

As will be recognized, a powered asset beacon <NUM> can be used to sense and/or detect various information/data. For example, a powered asset beacon <NUM> can be capable of sensing temperature information/data, pressure information/data, altitude information/data, vacuum information/data, vibration information/data, shock information/data, humidity information/data, moisture information/data, light information/data, air information/data, heading information/data, battery level information/data, and/or the like. In one embodiment, a powered asset beacon <NUM> may be operated in one or more operating modes, such as advertising mode, listening mode, sleep mode, and/or the like. In advertising mode, the powered asset beacon <NUM> transmits one or more advertising signals regularly, periodically (e.g., <NUM> times/second), and/or continuously. The one or more advertising signals includes one or more unique identifiers (e.g., powered asset information and/or unique powered asset beacon identifier) and received signal strength indicator (RSSI). The one or more advertising signals may also include other information/data. In listening mode, the powered asset beacon <NUM> is capable of receiving one or more signals transmitted by other beacons and/or other computing entities. In sleep mode, the powered asset beacon <NUM> may cut power to unneeded subsystems and place the other subsystems (e.g., receiver, processor) into a configurable low power state (e.g., with just sufficient power for the powered asset beacon <NUM> to detect triggers/events for it to change/switch from sleep mode into other operational modes (e.g., listening mode, advertising mode)). The change of the operational mode may be triggered by various configurable triggers/events, such as pressure, altitude, motion, location, light, sound, time, one or more signals transmitted from another beacon and/or an appropriate computing entity, a switch, a button, combinations thereof, and/or the like.

As noted, the powered asset beacon <NUM> comprises a camera (e.g., a video camera, a still camera, and/or the like) configured for collecting visual data regarding an environment surrounding the powered asset beacon <NUM>. The camera may have a fixed field of view (FOV) relative to the camera, comprising a defined angle within the FOV relative to the camera. For example, the FOV of the camera may comprise a <NUM> degree FOV (e.g., encompassing a cone having a <NUM> degree side-slope centered at a lens of the camera), a <NUM> degree FOV, a <NUM> degree FOV, and/or the like. Moreover, the FOV may extend a defined distance away from the camera (e.g., <NUM> feet, <NUM> feet, <NUM> feet, and/or the like). For example, the length of the FOV of the camera may correspond to the expected detection distance of the wireless signal receiver of the powered asset beacon <NUM>.

Moreover, the camera has a known orientation relative to the powered asset <NUM>, such that the heading of the powered asset (and/or powered asset beacon <NUM>) may be utilized to determine the location of the FOV of the camera relative to the heading of the powered asset <NUM>. In certain embodiments, the camera orientation may be fixed relative to the powered asset <NUM>, or the camera orientation may be movable relative to the powered asset <NUM>. In the latter embodiments, the orientation of the camera may be tracked to monitor the orientation of the camera relative to the heading of the powered asset <NUM>.

Thus, as discussed in greater detail herein, the detection of a container <NUM> (and/or other asset) within the FOV of the camera is utilized to determine the location of the container <NUM> relative to the powered asset <NUM> based on the known orientation of the FOV of the camera relative to the heading of the powered asset <NUM>. As a specific example, in an embodiment in which the FOV of the camera extends directly behind the powered asset <NUM> (as shown in <FIG>), and the powered asset <NUM> is known to be pointing due north at a given location, the detection of a container <NUM> within the FOV of the camera may be utilized to determine that the container <NUM> is due south of the powered asset <NUM> by a distance less than or equal to the length of the FOV of the camera relative to the given location.

In certain embodiments, the camera and/or other aspects of the powered asset beacon <NUM> may be configured for performing optical character recognition (OCR) on one or more images collected by the camera. As discussed in greater detail herein, containers <NUM> may have identifying information (e.g., alphanumeric strings) printed or otherwise disposed on one or more sidewalls of the containers. The powered asset beacon <NUM> may thus be configured to recognize the identifying information on a container visible within the FOV of the camera (e.g., via OCR), and may utilize the recognized identifying information to augment and/or improve the accuracy of the wireless information/data to precisely and accurately identify the location of the container <NUM>.

As indicated, a communication port <NUM> may be one of several components available in the information/data collection device <NUM> (or be in or as a separate computing entity). Embodiments of the communication port <NUM> may include an Infrared information/data Association (IrDA) communication port, an information/data radio, and/or a serial port. The communication port <NUM> may receive instructions for the information/data collection device <NUM>. These instructions may be specific to the powered asset <NUM> in which the information/data collection device <NUM> is installed, specific to the geographic area in which the powered asset <NUM> will be traveling, specific to the function the powered asset <NUM> serves within a fleet, and/or the like. In one embodiment, the information/data radio <NUM> may be configured to communicate with a wireless wide area network (WWAN), wireless local area network (WLAN), wireless personal area network (WPAN), or any combination thereof. For example, the information/data radio <NUM> may communicate via various wireless protocols, such as <NUM>, general packet radio service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access <NUM> (CDMA2000), CDMA2000 1X (1xRTT), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), IEEE <NUM> (Wi-Fi), Wi-Fi Direct, <NUM> (WiMAX), ultra wideband (UWB), infrared (IR) protocols, NFC protocols, Wibree, Bluetooth protocols (including Bluetooth Low Energy (BLE)), wireless universal serial bus (USB) protocols, and/or any other wireless protocol.

In various embodiments, a non-powered asset <NUM> may be any dolly, trailer, chassis, stacker truck, side loader, pallet truck, hand truck, handcart, roller deck, slave pallet, container trailer, pallet trailer, cargo trailer, cargo cart and/or the like. As will be recognized, a non-powered asset <NUM> may be configured to be pushed, pulled, lifted, or otherwise moved. The non-powered asset <NUM> may transport one or more one or more containers <NUM> storing one or more items <NUM> (which may be stored in containers <NUM>). Further, each non-powered asset <NUM> may be associated with a unique non-powered asset identifier (such as a non-powered asset ID) that uniquely identifies the non-powered asset <NUM>. The unique non-powered asset ID may include characters, such as numbers, letters, symbols, and/or the like. For example, an alphanumeric non-powered asset ID (e.g., "7221A445533AS449") may be associated with each non-powered asset <NUM>.

In one embodiment, each non-powered asset <NUM> may be associated with one or more RFID tags/sensors, beacons, computing entities, and/or the like. In one embodiment, each non-powered asset <NUM> can be capable of sensing temperature information/data, pressure information/data, altitude information/data, vacuum information/data, vibration information/data, shock information/data, humidity information/data, moisture information/data, light information/data, air information/data, heading information/data, battery level information/data, and/or the like. Thus, each non-powered asset may be configured to collect information/data and communicate various information/data using multiple wireless communication standards and protocols, such as GPRS, UMTS, CDMA2000, 1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any other wireless protocol.

In certain embodiments, the non-powered assets <NUM> may comprise and/or be associated with one or more non-powered asset beacons (not shown) having a configuration analogous to the powered asset beacons <NUM> described herein. In such embodiments, the various container beacons <NUM> may be configured to selectably initiate wireless communication with the non-powered asset beacons in a manner described in reference to the wireless communication between the container beacons <NUM> and the powered asset beacons <NUM>.

Moreover, the non-powered assets beacons may comprise one or more cameras having known orientations relative to the non-powered assets, as discussed in reference to the powered asset beacons <NUM>, above. Accordingly, as discussed above, the non-powered asset beacons may be utilized to determine a directional location of one or more containers relative to the position of the non-powered asset <NUM>.

In one embodiment, a container <NUM> is configured to store and transport one or more items (e.g., shipments, packages, pallets, etc.) of varying shapes and sizes. For instance, in various embodiments, a container <NUM> may be a unit load device (ULD) used to store and transport items <NUM> on an aircraft. An item <NUM> may be any tangible and/or physical object. In one embodiment, an item may be or be enclosed in one or more packages, envelopes, parcels, bags, goods, products, loads, crates, items banded together, drums, the like, and/or similar words used herein interchangeably.

In one embodiment, each container <NUM> and/or item <NUM> may include and/or be associated with unique a tracking identifier, such as an alphanumeric identifier. Such tracking identifiers may be represented as text, barcodes, tags, character strings, Aztec Codes, MaxiCodes, information/data Matrices, Quick Response (QR) Codes, electronic representations, and/or the like. A unique tracking identifier (e.g., 1Z123456789) may be used by a carrier to identify and track containers <NUM> and items <NUM> as they move through a carrier's transportation network. For example, information/data comprising a tracking identifier can be read, scanned, transmitted, and/or the like to provide and/or identify/determine the location of a container <NUM> and/or item <NUM>. As will be recognized, items <NUM> can be associated with a container <NUM> and therefore associated items <NUM> can considered to be located in the container <NUM> at the determined location of the container <NUM>. These can be referred to as "logical" scans/determinations or "virtual" scans/determinations.

Such tracking identifiers can be affixed to items by, for example, using a sticker (e.g., label) with the unique tracking identifier printed thereon (in human and/or machine readable form). In other embodiments, a container beacon <NUM> or an RFID tag may be affixed to or associated with each container <NUM> and/or item <NUM> and store a unique tracking identifier. As previously noted, a beacon may take many forms. For example, a beacon may be a BLE beacon (e.g., a URIBeacon, an AltBeacon, or an iBeacon), an RFID tag/sensor, an NFC device, a Wi-Fi device, and/or the like. The container beacon <NUM> can include some or all of the following components: one or more input interfaces for receiving information/data, one or more output interfaces for transmitting information/data, a processor, a clock, memory modules, one or more sensors for sensing and detecting various information/data, and a power source. The power source may be an energy storage device (e.g., a battery, a supercapacitor, and/or the like), an energy harvesting device (e.g., a solar panel, a vibration energy harvester, a thermal energy harvester, a RF energy harvester, and/or the like), and/or the like. In one embodiment, each container beacon <NUM> can store one or more unique identifiers, such as a GUID, a UUID, a character string, an alphanumeric string, text string, and/or the like. The unique identifier may identify the associated container <NUM> (and/or item <NUM>) and/or container beacon <NUM>. Via various communication standards and protocols, the container beacon <NUM> associated with the container <NUM> and/or item <NUM> can be communicated with, interrogated, read, and/or the like. For example, the container beacon <NUM> associated with the container <NUM> and/or item <NUM> can communicate with a powered asset beacon <NUM> associated with a powered asset <NUM> using multiple wireless communication standards and protocols, including Bluetooth, Wibree, NFC, Wi-Fi, ZigBee, and/or any other wireless protocol or standard. The container beacon <NUM> associated with the container <NUM> and/or item <NUM> may also be in direct or indirect communication with a tracking computing entity <NUM>, an information/data collection device <NUM>, a mobile computing entity <NUM>, and/or similar computing entities over the same or different wired or wireless networks.

As will be recognized, a container beacon <NUM> can be used to sense and detect various information/data. For example, a container beacon <NUM> can be capable of sensing temperature information/data, pressure information/data, altitude information/data, vacuum information/data, vibration information/data, shock information/data, humidity information/data, moisture information/data, light information/data, air information/data, heading/directional information/data, battery level information/data, and/or the like. In one embodiment, a container beacon <NUM> may be operated in one or more operating modes, such as advertising mode, listening mode, sleep mode, and/or the like. In advertising mode, the container beacon <NUM> may transmit one or more advertising signals regularly, periodically (e.g., <NUM> times/second), and/or continuously. The one or more advertising signals may include one or more unique identifiers (e.g., unique container identifier and/or unique container beacon identifier), RSSI, and/or other information/data. In listening mode, the container beacon <NUM> is capable of receiving one or more signals transmitted by other beacons, and/or an appropriate computing entities. In sleep mode, the container beacon <NUM> may cut power to unneeded subsystems and place the other subsystems (e.g., receiver, processor) into a configurable low power state (e.g., with just sufficient power for the container beacon <NUM> to detect triggers/events for it to change/switch from sleep mode into other operational modes (e.g., listening mode, advertising mode)). The change of the operational mode may be triggered by various configurable triggers/events, such as pressure, altitude, motion, light, location, sound, time, one or more signals transmitted from another beacon and/or an appropriate computing entity, a switch, a button, combinations thereof, and/or the like.

Although the following discussion focuses on the tracking and/or monitoring of the location of containers <NUM> specifically, it should be understood that concepts discussed herein may be utilized to track and/or monitor the location of any of a variety of assets, including, without limitation, containers <NUM> (as discussed directly herein), powered assets <NUM>, nonpowered assets <NUM>, employees (e.g., carrying a beacon), mobile computing entities, objects, and/or the like.

<FIG> provides a schematic of a tracking computing entity <NUM> according to one embodiment of the present invention. The tracking computing entity can be operated by a variety of entities, including a carrier. A carrier may be a traditional carrier, such as United Parcel Service (UPS), FedEx, DHL, courier services, the United States Postal Service (USPS), Canadian Post, freight companies (e.g. truck-load, less-than-truckload, rail carriers, air carriers, ocean carriers, etc.), and/or the like. However, a carrier may also be a nontraditional carrier, such as Coyote, Amazon, Google, Uber, ride-sharing services, crowd-sourcing services, retailers, and/or the like.

In general, the terms computing entity, entity, device, system, and/or similar words used herein interchangeably may refer to, for example, one or more computers, computing entities, desktop computers, mobile phones, tablets, phablets, notebooks, laptops, distributed systems, gaming consoles (e.g., Xbox, Play Station, Wii), watches, glasses, beacons, key fobs, RFID tags, ear pieces, scanners, televisions, dongles, cameras, wristbands, wearable items/devices, items/devices, powered assets, kiosks, input terminals, servers or server networks, blades, gateways, switches, processing devices, processing entities, set-top boxes, relays, routers, network access points, base stations, the like, and/or any combination of devices or entities adapted to perform the functions, operations, and/or processes described herein. Such functions, operations, and/or processes may include, for example, transmitting, receiving, operating on, processing, displaying, storing, determining, creating/generating, monitoring, evaluating, comparing, and/or similar terms used herein interchangeably. In one embodiment, these functions, operations, and/or processes can be performed on data, content, information, and/or similar terms used herein interchangeably.

As indicated, in one embodiment, the tracking computing entity <NUM> may also include one or more communications interfaces <NUM> for communicating with various computing entities, such as by communicating data, content, information, and/or similar terms used herein interchangeably that can be transmitted, received, operated on, processed, displayed, stored, and/or the like. For instance, the tracking computing entity <NUM> may communicate with powered assets <NUM>, mobile computing entities <NUM>, and/or the like.

As shown in <FIG>, in one embodiment, the tracking computing entity <NUM> may include or be in communication with one or more processing elements <NUM> (also referred to as processors, processing circuitry, and/or similar terms used herein interchangeably) that communicate with other elements within the tracking computing entity <NUM> via a bus, for example. As will be understood, the processing element <NUM> may be embodied in a number of different ways. For example, the processing element <NUM> may be embodied as one or more complex programmable logic devices (CPLDs), microprocessors, multi-core processors, coprocessing entities, application-specific instruction-set processors (ASIPs), and/or controllers. Further, the processing element <NUM> may be embodied as one or more other processing devices or circuitry. The term circuitry may refer to an entirely hardware embodiment or a combination of hardware and computer program products. Thus, the processing element <NUM> may be embodied as integrated circuits, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), hardware accelerators, other circuitry, and/or the like. As will therefore be understood, the processing element <NUM> may be configured for a particular use or configured to execute instructions stored in volatile or non-volatile media or otherwise accessible to the processing element <NUM>. As such, whether configured by hardware or computer program products, or by a combination thereof, the processing element <NUM> may be capable of performing steps or operations according to embodiments of the present invention when configured accordingly.

In one embodiment, the tracking computing entity <NUM> may further include or be in communication with non-volatile media (also referred to as non-volatile storage, memory, memory storage, memory circuitry and/or similar terms used herein interchangeably). In one embodiment, the non-volatile storage or memory may include one or more non-volatile storage or memory media <NUM> as described above, such as hard disks, ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/or the like. As will be recognized, the non-volatile storage or memory media may store databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like. The term database, database instance, database management system entity, and/or similar terms used herein interchangeably may refer to a structured collection of records or information/data that is stored in a computer-readable storage medium, such as via a relational database, hierarchical database, and/or network database.

In one embodiment, the tracking computing entity <NUM> may further include or be in communication with volatile media (also referred to as volatile storage, memory, memory storage, memory circuitry and/or similar terms used herein interchangeably). In one embodiment, the volatile storage or memory may also include one or more volatile storage or memory media <NUM> as described above, such as RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and/or the like. As will be recognized, the volatile storage or memory media may be used to store at least portions of the databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like being executed by, for example, the processing element <NUM>. Thus, the databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like may be used to control certain aspects of the operation of the tracking computing entity <NUM> with the assistance of the processing element <NUM> and operating system.

As indicated, in one embodiment, the tracking computing entity <NUM> may also include one or more communications interfaces <NUM> for communicating with various computing entities, such as by communicating data, content, information, and/or similar terms used herein interchangeably that can be transmitted, received, operated on, processed, displayed, stored, and/or the like. For instance, the tracking computing entity <NUM> may communicate with computing entities or communication interfaces of the powered asset <NUM>, mobile computing entities <NUM>, and/or the like.

Such communication may be executed using a wired information/data transmission protocol, such as fiber distributed information/data interface (FDDI), digital subscriber line (DSL), Ethernet, asynchronous transfer mode (ATM), frame relay, information/data over cable service interface specification (DOCSIS), or any other wired transmission protocol. Similarly, the tracking computing entity <NUM> may be configured to communicate via wireless external communication networks using any of a variety of protocols, such as GPRS, UMTS, CDMA2000, 1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any other wireless protocol. Although not shown, the tracking computing entity <NUM> may include or be in communication with one or more input elements, such as a keyboard input, a mouse input, a touch screen/display input, audio input, pointing device input, joystick input, keypad input, and/or the like. The tracking computing entity <NUM> may also include or be in communication with one or more output elements (not shown), such as audio output, video output, screen/display output, motion output, movement output, and/or the like.

As will be appreciated, one or more of the tracking computing entity's <NUM> components may be located remotely from other tracking computing entity <NUM> components, such as in a distributed system. Furthermore, one or more of the components may be combined and additional components performing functions described herein may be included in the tracking computing entity <NUM>. Thus, the tracking computing entity <NUM> can be adapted to accommodate a variety of needs and circumstances.

<FIG> provides an illustrative schematic representative of a mobile computing entity <NUM> that can be used in conjunction with embodiments of the present invention. In one embodiment, a mobile computing entity may be carried for use by carrier personnel. In one embodiment, the mobile computing entities <NUM> may include one or more components that are functionally similar to those of the tracking computing entity <NUM> and/or as described below. As will be recognized, mobile computing entities <NUM> can be operated by various parties, including personnel loading, unloading, delivering, transporting containers <NUM> and/or items <NUM>. As shown in <FIG>, a mobile computing entity <NUM> can include an antenna <NUM>, a transmitter <NUM> (e.g., radio), a receiver <NUM> (e.g., radio), and a processing element <NUM> that provides one or more signals to and receives one or more signals from the transmitter <NUM> and receiver <NUM>, respectively.

The one or more signals provided to and received from the transmitter <NUM> and the receiver <NUM>, respectively, may include signaling information/data in accordance with an air interface standard of applicable wireless systems to communicate with various entities, such as powered assets <NUM>, tracking computing entities <NUM>, and/or the like. In this regard, the mobile computing entity <NUM> may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. More particularly, the mobile computing entity <NUM> may operate in accordance with any of a number of wireless communication standards and protocols. In a particular embodiment, the mobile computing entity <NUM> may operate in accordance with multiple wireless communication standards and protocols, such as GPRS, UMTS, CDMA2000, 1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR protocols, Bluetooth protocols, USB protocols, and/or any other wireless protocol.

Via these communication standards and protocols, the mobile computing entity <NUM> can communicate with various other entities using concepts such as Unstructured Supplementary Service information/data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-Frequency Signaling (DTMF), and/or Subscriber Identity Module Dialer (SIM dialer). The mobile computing entity <NUM> can also download changes, add-ons, and updates, for instance, to its firmware, software (e.g., including executable instructions, applications, program modules), and operating system.

According to one embodiment, the mobile computing entity <NUM> may include location determining aspects, devices, modules, functionalities, and/or similar words used herein interchangeably. For example, the mobile computing entity <NUM> may include outdoor positioning aspects, such as a location module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, direction, heading, speed, UTC, date, and/or various other information/data. In one embodiment, the location module can acquire data, sometimes known as ephemeris data, by identifying the number of satellites in view and the relative positions of those satellites. The satellites may be a variety of different satellites, including LEO satellite systems, DOD satellite systems, the European Union Galileo positioning systems, GLONASS, the Chinese Compass navigation systems, Indian Regional Navigational satellite systems, and/or the like. Additionally, the location module may be compatible with A-GPS for quick time to first fix and jump starting the ability of the location module to acquire location almanac and ephemeris data, and/or be compatible with SBAS such as WAAS, EGNOS, MSAS, and/or GAGN to increase GPS accuracy. Alternatively, the location information/data may be determined by triangulating the mobile computing entity's <NUM> position in connection with a variety of other systems, including cellular towers, Wi-Fi access points, and/or the like. Similarly, the mobile computing entity <NUM> may include indoor positioning aspects, such as a location module adapted to acquire, for example, latitude, longitude, altitude, geocode, course, direction, heading, speed, time, date, and/or various other information/data. Some of the indoor aspects may use various position or location technologies including RFID tags, indoor beacons or transmitters, Wi-Fi access points, cellular towers, nearby computing devices (e.g., smartphones, laptops) and/or the like. For instance, such technologies may include iBeacons, Gimbal proximity beacons, BLE receivers and/or transmitters, NFC receivers and/or transmitters, and/or the like. These indoor positioning aspects can be used in a variety of settings to determine the location of someone or something to within inches or centimeters.

The mobile computing entity <NUM> may also comprise a user interface (that can include a display <NUM> coupled to a processing element <NUM>) and/or a user input interface (coupled to a processing element <NUM>). For example, the user interface may be an application, browser, user interface, dashboard, webpage, and/or similar words used herein interchangeably executing on and/or accessible via the mobile computing entity <NUM> to interact with and/or cause display of information. The user input interface can comprise any of a number of devices allowing the mobile computing entity <NUM> to receive data, such as a keypad <NUM> (hard or soft), a touch display, voice/speech or motion interfaces, scanners, readers, or other input device. In embodiments including a keypad <NUM>, the keypad <NUM> can include (or cause display of) the conventional numeric (<NUM>-<NUM>) and related keys (#, *), and other keys used for operating the mobile computing entity <NUM> and may include a full set of alphabetic keys or set of keys that may be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface can be used, for example, to activate or deactivate certain functions, such as screen savers and/or sleep modes. Through such inputs the mobile computing entity can collect contextual information/data as part of the telematics data.

The mobile computing entity <NUM> can also include volatile storage or memory <NUM> and/or non-volatile storage or memory <NUM>, which can be embedded and/or may be removable. For example, the non-volatile memory may be ROM, PROM, EPROM, EEPROM, flash memory, MMCs, SD memory cards, Memory Sticks, CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, and/or the like. The volatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, and/or the like. The volatile and non-volatile storage or memory can store databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, byte code, compiled code, interpreted code, machine code, executable instructions, and/or the like to implement the functions of the mobile computing entity <NUM>.

In one embodiment, the user computing entities <NUM> may each include one or more components that are functionally similar to those of the tracking computing entity <NUM> and/or the mobile computing entity <NUM>. For example, in one embodiment, each of the user computing entities <NUM> may include: (<NUM>) a processing element that communicates with other elements via a system interface or bus; (<NUM>) a user interface; (<NUM>) transitory and non-transitory memory; and (<NUM>) a communications interface. As previously noted, the user computing entity <NUM> may comprise a user interface. For example, the user interface may be an application, browser, user interface, dashboard, webpage, and/or similar words used herein interchangeably executing on and/or accessible via the user computing entity <NUM> to interact with and/or cause display of information/data from the tracking computing entity <NUM> and/or the mobile computing entity <NUM>, as described herein. These architectures are provided for exemplary purposes only and are not limiting to the various embodiments.

Reference will now be made to <FIG> is a flowchart illustrating operations and processes that can be used in accordance with various embodiments of the present invention.

Described herein are embodiments for a flight-safe container (and/or other asset) tracking that allows tracking using beacons. In one embodiment, a container beacon <NUM> associated with a container <NUM> can support enablement of a flight-safe operational mode, which includes stopping the advertising operation of the container beacon <NUM> and keeping the container beacon <NUM> in the listening mode or the sleep mode as necessary (e.g., after being loaded onto a plane). After being unloaded from the plane, the container beacon <NUM> associated with the container <NUM> can receive one or more trigger signals to enable its advertising mode. The container beacon <NUM> can then transmit one or more signals to a powered asset beacon <NUM> associated with a powered asset <NUM>, for example, to enable location tracking using Bluetooth Low Energy Beacons for the corresponding container <NUM>.

In one embodiment, before the plane loaded with the container <NUM> starts to move, a flight-safe operational mode of the container beacon <NUM> associated with the container <NUM> may be enabled. The following operations/steps describe an exemplary enablement of a flight-safe operational mode. The enablement may be achieved by setting the listening mode as the default operational mode of the container beacon <NUM> associated with the container <NUM>. Thus, for instance, after losing connection with a powered asset beacon <NUM> (or some other entity), the container beacon <NUM> may automatically stop the advertising mode and enter into the listening mode. Alternatively, the container beacon <NUM> can receive one or more trigger signals to stop the advertising mode and enable the listening mode or sleep mode. The one or more trigger signals can be transmitted from a device affixed to the plane, a device that is local to the corresponding plane location, or a device that is remotely located. The one or more trigger signals may be transmitted constantly, and/or periodically, such that the container beacons <NUM> may periodically or continuously receive the trigger signals to maintain the sleep mode of the container beacons <NUM> during flight.

In one embodiment, the container beacon <NUM> may switch/change modes from the listening mode to the power-saving sleep mode upon detecting the occurrence of one or more configurable triggers/events. The configurable triggers/events may be a value, a change, and/or a rate of change, of pressure, altitude, motion, light, combinations thereof, and/or the like; a location; a sound, a time; one or more sleep signals transmitted from another beacon (or other appropriate computing entity, such as a beacon secured within an aircraft); a switch; a button; and/or the like. The configurable triggers/events may be preconfigured, determined adaptively by the container beacon <NUM> associated with the container <NUM>, transmitted from another beacon, and/or the like. For example, the container beacon <NUM> can enter into the sleep mode upon detecting that the altitude of the plane loaded with the container <NUM> has reached a configurable threshold, upon detecting that the container beacon <NUM> is inside or outside of one or more configurable geo-fences, upon detecting a unique sound signature (e.g., via a sound sensor) indicating the engaging of floor latch securing hardware, upon detecting the presence of a group of beacons exceeding a configurable threshold, upon detecting an elapsed period of time without receiving a signal, or after not having been moved for a configurable period of time. Alternatively, the container beacon <NUM> associated with the container <NUM> may switch/change from the listening mode to the sleep mode upon receiving one or more sleep trigger signals transmitted from an appropriate computing entity. For example, the container beacon <NUM> may enter a sleep mode for a fixed period of time upon receipt of a sleep trigger signal (e.g., a message) causing the container beacon <NUM> to enter the sleep mode. Accordingly, the container beacon <NUM> may periodically "wake-up" (switch from the sleep mode into an active mode) into a listening mode to determine whether the sleep trigger signals are still being broadcast. Upon determining that another sleep trigger signal is received, the container beacon <NUM> may reenter the sleep mode until such a time that the container beacon <NUM> wakes up and no sleep trigger signal is detected.

In one embodiment, the container beacon <NUM> may switch/change modes from the sleep mode to the listening mode upon detecting the occurrence of one or more configurable triggers/events. The configurable triggers/events may be a value, a change, and/or a rate of change, of pressure, altitude, motion, light, combinations thereof, and/or the like; a location, a sound, a time; one or more wake signals transmitted from another beacon (or other appropriate computing entity, such as a beacon secured within an aircraft); a switch; a button; and/or the like. As previously noted, the configurable triggers/events may be preconfigured, determined adaptively by the container beacon <NUM> associated with the container <NUM>, transmitted from another beacon, and/or the like. For example, the container beacon <NUM> can enter into the listening mode upon detecting that the altitude of the plane loaded with the container <NUM> has reached a configurable threshold value, or determining a plane landing motion by detecting change of velocity, acceleration, altitude, combinations thereof, and/or the like. Alternatively, the container beacon <NUM> associated with the container <NUM> may switch/change from the sleep mode to the listening mode upon receiving one or more wake trigger signals transmitted from an appropriate computing entity.

In one embodiment, after being unloaded from the plane, the container beacon <NUM> may switch/change from the listening mode to the advertising mode upon detecting the occurrence of one or more configurable triggers/events. In another embodiment, the one or more wake trigger signals may be signals transmitted from a powered asset beacon <NUM> associated with a powered asset <NUM> (or any other computing entity, such as a device affixed to the plane).

In one embodiment, the container <NUM> is loaded to a non-powered asset <NUM> that is to be moved by a powered asset <NUM> (e.g., see <FIG>). The container beacon <NUM> associated with the container <NUM> may receive one or more signals transmitted from a powered asset beacon <NUM> associated with the powered asset <NUM>. The one or more signals transmitted by the powered asset beacon <NUM> may include a unique identifier (e.g., GUID, UUID, and/or the like). The container beacon <NUM> may, upon verifying that the received identifier is one that it should respond to, generate and transmit one or more signals, which may include the unique identifier, received signal strength indicator (RSSI), and/or other information/data. The powered asset beacon <NUM> may, upon receiving the one or more signals transmitted by the container beacon <NUM>, identify and register the container <NUM> and transmit one or more confirmation signals. The container beacon <NUM> may then enter into the advertising mode.

In one embodiment, the powered asset beacon <NUM> (with which the container beacon <NUM> associated with the container <NUM> is registered) may transmit one or more signals to an appropriate computing entity (e.g., a mobile computing entity, a tracking computing entity) to associate the container <NUM> with the powered asset <NUM>, and/or update the location of the container <NUM> as being the location of the powered asset <NUM> regularly, periodically, continuously, during certain time periods or time frames, upon determining the occurrence of one or more configurable triggers/events, in response to requests, in response to determinations/identifications, combinations thereof, and/or the like.

In one embodiment, the powered asset beacon <NUM> associated with the powered asset <NUM> may, upon detecting the connection/communication loss with the container beacon <NUM> associated with the container <NUM>, deregister the container <NUM>, and/or transmit one or more signals to the appropriate computing entity to de-associate the container <NUM> with the powered asset <NUM>. The appropriate computing entity may record the last known container location and stop tracking the container <NUM> location via the powered asset's <NUM> location.

In one embodiment, the container beacon <NUM> associated with the container <NUM> may, upon detecting the connection/communication loss with the powered asset beacon <NUM> associated with the powered asset <NUM>, switch/change to the listening mode. Alternatively, the container beacon <NUM> associated with the container <NUM> may maintain the advertising mode, upon detecting the connection/communication loss with the powered asset beacon <NUM> associated with the powered asset <NUM>, until receiving one or more other trigger signals. As will be recognized, a variety of approaches and techniques can be used to adapt to various needs and circumstances.

In one embodiment, the process may begin with a powered asset beacon <NUM> associated with a powered asset <NUM> transmitting one or more signals for use by a container beacon <NUM> associated with a container <NUM>. As shown in <FIG>, which shows a schematic view of a powered asset <NUM> transporting a plurality of non-powered assets <NUM> and containers <NUM>, the powered asset beacon <NUM> may transmit one or more signals (e.g., registration/confirmation signals, discussed in greater detail herein) within a communication range 150a to be received by various container beacons <NUM> located within the communication range 150a (e.g., container beacons associated with containers A and B). To avoid undesirably linking containers <NUM> that are not being transported by the powered asset <NUM> (e.g., container C, shown in <FIG>), the communication range 150a may be configured to encompass an area around the powered asset <NUM> in which transported containers <NUM> are expected to be located (e.g., behind and/or on the powered asset). Certain embodiments may be configured to simply locate various containers however, regardless of whether those containers are connected to the powered asset <NUM>. In such embodiments, the communication range 150a of a powered asset beacon may be generally circular surrounding the powered asset beacon <NUM>, and may encompass areas beyond where a particular container <NUM> may be pulled and/or associated with the powered asset. The powered asset beacon <NUM> may transmit the one or more signals regularly, periodically, continuously, during certain time periods or time frames, on certain days, upon determining the occurrence of one or more configurable triggers/events, in response to requests, in response to determinations/identifications, combinations thereof, and/or the like. As previously noted, the one or more signals transmitted by the powered asset beacon <NUM> may include one or more unique identifiers. The unique identifiers may identify the relevance of the powered asset beacon <NUM> (and corresponding powered asset <NUM>) to the container beacons <NUM> within range. For instance, the one or more signals may include a powered asset identifier and/or a powered asset beacon identifier (e.g., powered asset information/data).

As an alternative, the process may begin with an appropriate computing entity (e.g., an information/data collection device <NUM>, a mobile computing entity <NUM>, a powered asset computing entity, and/or the like) transmitting one or more signals for use by container beacons <NUM> within range. As yet another alternative, the process may begin with a device affixed to a plane, or a device that is local to the corresponding plane location, transmitting one or more signals for use by a container beacon <NUM> associated with a container <NUM> being unloaded from the plane. As will be recognized, a variety of other approaches and technique can be used to adapt to various needs and circumstances.

In one embodiment, a container beacon <NUM> can have a preconfigured interest in powered asset beacon <NUM> signals of a particular class/type and/or appropriate computing entity signals of a particular class/type. The signals may include one or more unique identifiers that uniquely identify the corresponding powered asset <NUM> and/or powered asset beacon <NUM> (e.g., powered asset information/data). Using this approach, in listening mode, the container beacon <NUM> can ignore all powered asset beacon <NUM> signals and/or computing entity signals for which it is not registered. Similarly, the container beacon <NUM> can respond to a number of different types of powered asset beacon signals and/or computing entity signals.

Accordingly, as shown in <FIG>, each of the container beacons <NUM> associated with containers A, B, and C may be in listening mode, until detecting the presence of a powered asset beacon <NUM> as discussed in greater detail herein. As an example, the container beacons <NUM> associated with containers A and B were in listening mode until receiving one or more signals from the powered asset beacon <NUM>, and then the container beacons <NUM> associated with containers A and B entered advertising mode, as discussed herein. However, because the container beacon <NUM> associated with container C is not within a communication range of the powered asset beacon <NUM>, the container beacon associated with container C remains in listening mode.

In one embodiment, after receiving one or more signals from a powered asset beacon <NUM> of a particular class/type (e.g., a powered asset beacon <NUM> for which the container beacon <NUM> has a preconfigured interest), the container beacon <NUM> may generate and transmit one or more signals for the powered asset beacon <NUM> to detect and process, as illustrated in <FIG>. For example, the powered asset beacon <NUM> (or a plurality of powered asset beacons <NUM> associated with a single powered asset <NUM>) may detect the presence of the container beacon <NUM> using one or more methodologies described in <CIT>, which is incorporated herein by reference in its entirety. The one or more signals (e.g., advertising signals) from the container beacon <NUM> may include the powered asset's unique identifier, the powered asset beacon's unique identifier, the container's unique identifier, the container beacon's unique identifier, RSSI, and/or other information/data. Moreover, the powered asset beacon <NUM> may be configured to detect and monitor the strength of the received signal, and may be configured to compare the actual received signal strength against an expected signal strength as indicated by the RSSI data, and may utilize the determined difference between the actual and expected signal strength to estimate a distance between the powered asset beacon <NUM> and the container beacon <NUM>. In one embodiment, the container's information/data (e.g., unique container identifier and/or unique container beacon identifier) may identify relevance of the container beacon <NUM> to the powered asset beacon <NUM> (and/or the appropriate computing entity). Thus, the powered asset beacon <NUM> may receive the one or more signals transmitted from the container beacon <NUM> with the container information/data.

In certain embodiments, the container's information/data as transmitted by the container beacon <NUM> may be detected by a plurality of powered asset beacons <NUM> (e.g., disposed on a respective plurality of powered assets <NUM>). Each of the plurality of powered asset beacons <NUM> detecting the presence of the container beacon <NUM> may monitor various aspects of the received signal, such as the RSSI data, the detected signal strength, and/or the like to ascertain an estimated distance between the container beacon <NUM> and each powered asset beacon <NUM>. Each powered asset beacon <NUM> (and/or another computing entity, such as the tracking computing entity <NUM>) may compare the estimated distance between the powered asset beacons <NUM> and the container beacons <NUM> to triangulate the estimated location of the container <NUM>, relative to the known locations of the powered assets <NUM> (e.g., as determined based at least in part on location sensors disposed on each powered asset <NUM>).

Moreover, in embodiments in which the powered asset beacons <NUM> contain and/or are associated with cameras having known orientations relative to the powered asset beacons <NUM>, the powered asset beacons may be configured to identify an estimated location of a detected container <NUM> that is visible within an FOV of the camera to augment and/or improve the accuracy of a determined location of a container <NUM> as determined based at least in part on the wireless information/data received from the container beacon <NUM>. For example, the powered asset beacons <NUM> may be configured to ascertain an estimated distance between the powered asset beacons <NUM> and a detected container beacon <NUM> based at least in part on a comparison between the RSSI data and an actual detected signal strength. Moreover, upon detecting the container within an FOV of the camera (e.g., utilizing OCR to recognize container identifiers printed or otherwise disposed on a side of the container), the powered asset beacon <NUM> (and/or another computing entity, such as the tracking computing entity <NUM>), may be configured to identify the location of the powered asset <NUM> and the orientation of the FOV of the camera disposed on the powered asset <NUM>. Based on the known location of the powered asset <NUM> and orientation of the camera on the powered asset <NUM>, the powered asset beacon <NUM> (and/or another computing entity, such as the tracking computing entity <NUM>) may be configured to determine a relative orientation of the container <NUM> relative to the powered asset <NUM>. Based at least in part on the known location of the powered asset <NUM>, the known orientation of the camera, and the estimated distance between the powered asset beacon <NUM> and the container beacon <NUM>, the powered asset beacon <NUM> (and/or another computing entity, such as the tracking computing entity <NUM>) may be configured to determine an estimated location of the container <NUM>. As a specific example with reference to <FIG> (which illustrates a schematic diagram of a located container <NUM> relative to a powered asset <NUM>), the location of the container <NUM> may be estimated based on a known location of a single powered asset <NUM>. The powered asset <NUM> may have a known location and heading, and the orientation of the FOV of the camera of the powered asset beacon <NUM> may be known to be directly opposite of the heading of the powered asset <NUM>. In the embodiment of <FIG>, the container beacon <NUM> may transmit container information/data to the powered asset beacon <NUM>, including RSSI data. Based at least in part on the RSSI data and the detected signal strength received from the container beacon <NUM>, the powered asset beacon <NUM> may estimate a distance between the powered asset beacon <NUM> and the container beacon <NUM>. Moreover, because the container is located within the FOV of the camera of the powered asset beacon <NUM>, the powered asset beacon <NUM> may be configured to identify the container based on the identifying information (indicated by the "A" on the container <NUM>), and may determine an estimated location of the container <NUM> as being the estimated distance away from the powered asset beacon <NUM>, and being located in the direction of the FOV of the camera of the powered asset beacon <NUM>.

In certain embodiments, the wireless information/data collected by the powered asset beacon <NUM> (e.g., signals received from the container beacons <NUM>) may be utilized to augment and/or improve the OCR process for recognizing information/data via the camera. For example, the wireless information/data may limit the possible data matches that may be utilized to ascertain the identity of identifying information viewable with the FOV of the camera. In certain embodiments, the powered asset beacon <NUM> may be configured to apply OCR concepts to determine that any viewable identifying information/data within the FOV of the camera must match identifying information of container <NUM> detected via wireless transmissions received by the powered asset beacon <NUM>. As a specific example, the powered asset beacon <NUM> may detect wireless signals transmitted by container beacons <NUM> associated with containers 123ABC, 456DEF, and 789GHI. Therefore, upon identifying a container <NUM> within the FOV of the camera, the powered asset beacon <NUM> may be configured to compare the identifying information on the container <NUM> against each of character strings "123ABC," "456DEF," and "789GHI" to identify which of these character strings most closely resembles the identifying information/data on the container <NUM>.

Moreover, in certain embodiments, the identifying information/data received via the camera of the powered asset beacon <NUM> (e.g., via OCR) may be utilized to augment and/or improve the information/data received wirelessly via the powered asset beacon <NUM> from the one or more container beacons <NUM>. In certain embodiments, the powered asset beacon <NUM> may be configured to link or otherwise associate the powered asset <NUM> with a particular container <NUM> only if the container <NUM> is visible within the FOV of the camera. In such embodiments, if wireless information/data is detected from other container beacons <NUM>, the powered asset beacon <NUM> may not associate with those other container beacons <NUM>.

In one embodiment, after receiving the one or more signals in operation/step <NUM>, the powered asset beacon <NUM> may register the container <NUM> using the container's information/data (e.g., unique container identifier and/or unique container beacon identifier) transmitted by the container beacon <NUM>. In one embodiment, the powered asset beacon <NUM> (or other computing entity) may further transmit the one or more new container registration signals to an appropriate computing entity to initiate the process of associating the container <NUM> with the powered asset <NUM>, such as to a tracking computing entity <NUM>. The one or more transmitted registration signals may include the container information/data, the powered asset information/data, and/or the like. The communication between the powered asset beacon <NUM> and the appropriate computing entity may be executed using a wired connection, for example, a bus, a wired PAN, or the like, or via wireless communication networks, for example, a wireless PAN, LAN, MAN, WAN, and/or the like. As an alternative embodiment, the function of associating the container <NUM> with the powered asset <NUM> may be executed by the powered asset beacon <NUM>.

In one embodiment, the powered asset beacon <NUM> (or other appropriate computing entity) may send one or more confirmation signals to the container beacon <NUM> to inform the container beacon <NUM> of a positive identification and registration of the corresponding container <NUM>. Responsive to receiving the one or more confirmation signals, the container beacon <NUM> may enter advertising mode. In advertising mode, the container beacon <NUM> may regularly, periodically, and/or continuously transmit one or more advertising signals (as illustrated in <FIG>) for use by the powered asset beacon <NUM> and/or the appropriate computing entity to track its location. To do so, the one or more advertising signals may include the container information/data (e.g., unique container identifier and/or unique container beacon identifier), RSSI, and/or other information/data.

In one embodiment, if the container beacon <NUM> associated with the container <NUM> determines/detects that it is no longer in communication with the powered asset beacon <NUM>, the container beacon <NUM> may switch/change from the advertising mode to the listening mode. Similarly, if the container beacon <NUM> determines/detects that it is still in communication with the powered asset beacon <NUM>, the container beacon <NUM> may continue advertising in advertising mode. In certain embodiments, the container beacon <NUM> may periodically enter listening mode for a brief period of time while in advertising mode to determine whether the container beacon <NUM> remains in connection with one or more powered asset beacons <NUM>. For example, while in listening mode, the container beacon <NUM> may determine whether the container beacon <NUM> detects transmissions emitted by the powered asset beacon <NUM>. Upon determining that the container beacon <NUM> detects transmissions emitted by the powered asset beacon <NUM>, the container beacon <NUM> may reenter advertising mode to continue broadcasting container information/data to the powered asset beacon <NUM>. However, upon determining that the container beacon <NUM> does not detect signals emitted by the powered asset beacon <NUM> while in listening mode, the container beacon <NUM> may remain in listening mode until a signal emitted from a powered asset beacon <NUM> is detected.

In one embodiment, the mobile computing entity <NUM> (or other appropriate computing entity) may associate the container <NUM> with the powered asset <NUM> upon receiving the one or more container <NUM> registration signals from the powered asset beacon <NUM>. In one embodiment, to track the container <NUM>, the mobile computing entity <NUM> may generate and transmit one or more signals to the tracking computing entity <NUM> to initiate the process of tracking the container <NUM> and/or update the location of the container <NUM> as being the location of the corresponding powered asset <NUM>. The one or more transmitted signals may include the powered asset information, container information/data of the newly registered container <NUM>, a timestamp for initiating the association of the container <NUM> with the powered asset <NUM>, and location information/data of the powered asset <NUM>. The location information/data of the powered asset <NUM> (and thereby the container <NUM>) may be identified/determined using GPS technologies by acquiring, for example, latitude, longitude, altitude, and/or geocode data corresponding to workers/users. Additionally or alternatively, the location information/data may be collected and provided via triangulation of various communication points (e.g., cellular towers, Wi-Fi access points, etc.) positioned at locations throughout a geographic area. Such embodiments allow the location and/or movement of powered assets <NUM> and associated containers <NUM> to be monitored and tracked. As will be recognized, a variety of other approaches and techniques can be used to adapt to various needs and circumstances. The location of each of these can be updated and stored in a tracking database, for example, by the tracking computing entity <NUM>. The location of the powered assets <NUM> and containers <NUM> can be monitored, tracked, and updated regularly, periodically, continuously, upon determining the occurrence of one or more configurable triggers/events, and/or the like.

In one embodiment, the powered asset beacon <NUM> may receive one or more signals transmitted by a container beacon <NUM> in advertising mode to confirm that the container beacon <NUM> is within communication range and has normal connection with the powered asset beacon <NUM>. This validates the continuing association of the container <NUM> with the powered asset <NUM>, which indicates no action is needed to de-associate the container <NUM> with the powered asset <NUM>. And as noted, the location of the powered assets <NUM> and containers <NUM> can be updated regularly, periodically, continuously, upon determining the occurrence of one or more configurable triggers/events, and/or the like. As will be recognized, these steps/operations can be performed by a variety of computing entities. The location of the containers <NUM> relative to the powered assets <NUM> may be determined and/or updated periodically based on the detected signal strength of the signal emitted by a container beacon <NUM> and received by a powered asset beacon <NUM> (e.g., compared against an emitted signal strength, as indicated in the RSSI data).

As discussed herein, the powered asset beacon <NUM> may continuously or periodically transmit one or more signals to the associated container beacons <NUM>. As discussed below, the container beacons <NUM> may be configured to continuously and/or periodically monitor the connection with the powered asset beacon <NUM> (e.g., by periodically switching into listening mode), based at least in part on one or more detected signals transmitted from the powered asset beacon <NUM>. Upon determining that no powered asset beacon <NUM> signals are detected, the container beacons <NUM> may be configured to switch from an advertising mode to a listening mode to conserve power. Thus, to ensure continued communication between the container beacons <NUM> and the powered asset beacons <NUM> (and vice versa), the powered asset beacons <NUM> may transmit one or more signals to be received by the associated container beacons <NUM>.

In certain embodiments, the container beacons <NUM> may be wirelessly connected with a plurality of powered asset beacons <NUM> simultaneously. As the container beacons <NUM> broadcast container information/data while in advertising mode, a plurality of powered asset beacons <NUM> may receive the broadcast container information/data, and may monitor various aspects of the container beacon <NUM> based on the received container information/data. For example, each of a plurality of powered asset beacons <NUM> may receive the container information/data, and may determine a relative location of the powered asset beacon <NUM> relative to the container <NUM> (e.g., based on the received signal strength and/or the RSSI data broadcast by the container beacon <NUM>). In certain embodiments, the location of each of the plurality of powered asset beacons <NUM> are known (e.g., based on location devices on each of the powered assets), and accordingly an estimated location of the container <NUM> may be determined by triangulation, utilizing the determined distances between the container <NUM> and each of the plurality of powered assets. For example, each of the plurality of powered asset beacons <NUM> may transmit container information/data including the determined distance between the container and the powered asset, to tracking computing entity, which may utilized the determined distances detected by a plurality of powered asset beacons <NUM> to triangulate the location of the container <NUM>.

In one embodiment, a container beacon <NUM> may switch/change to the listening mode from the advertising mode upon determining the occurrence of one or more configurable triggers/events. As previously described, the configurable triggers/events may be a value, a change, and/or a rate of change, of pressure, altitude, motion, light, combinations thereof, and/or the like; a location, a sound, a time; one or more signals transmitted from another beacon (or other appropriate computing entity; a switch; a button; and/or the like). The configurable triggers/events may be preconfigured, determined adaptively by the container beacon <NUM> associated with the container <NUM>, transmitted from another beacon, and/or the like. For example, in one embodiment, the container beacon <NUM> may, while in the advertising mode, enable the listening mode during certain time periods or time frames to detect if the container beacon <NUM> is in normal communication with a powered asset beacon <NUM> associated with a powered asset <NUM> (and/or another appropriate computing entity). The container beacon <NUM> may switch/change into the listening mode, and stop advertising if necessary, upon detecting that the container beacon <NUM> is no longer in communication with the powered asset beacon <NUM> (and/or another appropriate computing entity). Alternatively, the container beacon <NUM> may switch/change into the listening mode and stop advertising upon receiving one or more trigger signals transmitted from a device (or other appropriate computing entity) affixed to a plane, local to the corresponding plane location, or remotely located.

In one embodiment, a container beacon <NUM> may switch/change from the listening mode to the sleep mode to save energy upon determining the occurrence of one or more configurable triggers/events. In an alternative embodiment, a container beacon <NUM> may switch/change directly from the advertising mode to the sleep mode to save energy upon determining the occurrence of one or more configurable triggers/events. For example, as shown in <FIG>,, the container beacon <NUM> may switch/change from the listening mode to the sleep mode upon detecting that a plane (in which the container <NUM> is loaded) has reached/exceeded a configurable altitude threshold and/or detecting a predefined motion event. In the illustrated embodiment of <FIG>, the container beacons <NUM> associated with each of containers D and E remain below the altitude threshold, and therefore the container beacons <NUM> associated with containers D and E remain active. Specifically, the container beacon <NUM> associated with container D may be in advertising mode, because the container beacon <NUM> is located within the transmission range 150a associated with the powered asset beacon <NUM>, and the container beacon <NUM> associated with container E is in listening mode. Container F shown in <FIG> is being transported by plane, and is located above the altitude threshold. Accordingly, the container beacon <NUM> associated with container F is in sleep mode and may remain in sleep mode until the container beacon <NUM> determines that it is located below the altitude threshold.

Alternatively, the container beacon <NUM> may enter into the sleep mode upon detecting that, for a configurable period of time, the container <NUM> has not been moved and/or the container beacon <NUM> has not been in communication with a powered asset beacon <NUM> for a configurable period of time. As will be recognized, a variety of other approaches and techniques can be used to adapt to various needs and circumstances.

As yet another example, the container beacon <NUM> may enter into the sleep mode upon receiving a trigger signal, for example, transmitted from a beacon located within an aircraft. The container beacon <NUM> may be configured to enter the sleep mode for a period of time upon detecting the trigger signal, and may be configured to awaken at the end of the period of time. Upon awakening, the container beacon <NUM> may monitor for one or more additional sleep mode trigger signals which, if received, cause the container beacon <NUM> to reenter the sleep mode for a period of time. In certain embodiments, the period of time may be predetermined (e.g., <NUM> minute, <NUM> minutes, <NUM> hour, and/or the like), or the period of time may be defined as a part of the data transmitted within the sleep mode trigger signal. For example, in the latter embodiment, the sleep mode trigger signal may comprise data identifying a period of time for the container beacon <NUM> to remain asleep (e.g., a period of time at least substantially equal to the expected length of a flight).

Similarly, the container beacon <NUM> may switch/change from the sleep mode to the listening mode upon determining the occurrence of one or more configurable triggers/events. For example, in one embodiment, the container beacon <NUM> may switch/change from the sleep mode to the listening mode upon detecting a plane, in which the container <NUM> is loaded, reaches a configurable altitude (e.g., ground level) and/or detecting a predefined motion event. Alternatively, the container beacon <NUM> may enter into the listening mode upon receiving one or more trigger signals transmitted from a device (or other appropriate computing entity) affixed to a plane, local to the corresponding plane location, or remotely located.

In one embodiment, a powered asset beacon <NUM> may detect the connection/communication loss with a container beacon <NUM> with which it is registered. In response, the powered asset beacon <NUM> (or other appropriate computing entity) may initiate the process to deregister the container <NUM> from the corresponding powered asset <NUM>. Alternatively, a powered asset beacon <NUM> (or other appropriate computing entity) may generate and transmit one or more request signals to a registered container beacon <NUM> upon detecting the connection/communication loss with the container beacon <NUM>. The one or more request signals may include triggers for the container beacon <NUM> to (a) switch/change to the advertising mode from the listening mode and/or the sleep mode and/or (b) request one or more advertising signals from the container beacon <NUM>. If the powered asset beacon <NUM> (or other appropriate computing entity) does not receive a response from the container beacon <NUM> after one or multiple attempts to establish the connection, the powered asset beacon <NUM> (or other appropriate computing entity) may confirm the loss of connection with the container beacon <NUM> and/or initiate the process to deregister the container <NUM> accordingly.

After deregistering a container <NUM>, the powered asset beacon <NUM> (or other appropriate computing entity) may transmit a request to de-associate the container <NUM> with the powered asset <NUM>. In one embodiment, the request to de-associate the container <NUM> may include a timestamp with location information/data for the last normal communication between the container beacon <NUM> and the powered asset beacon <NUM> (or other appropriate computing entity).

In one embodiment, responsive to an appropriate request, a container <NUM> may be de-associated with the powered asset <NUM> with which the container <NUM> was previously associated. In one embodiment, the de-association may include transmitting a request to tracking computing entity <NUM> to stop updating the container's <NUM> location as being the location of the previously associated powered asset <NUM>. Correspondingly, the tracking computing entity <NUM> may record the last known container <NUM> location in the tracking database as being the location for the last normal communication between the container beacon <NUM> and the powered asset beacon <NUM> (or other appropriate computing entity). The appropriate computing entity records this location as the container <NUM> location until one or more new valid update signals are received for the container. For instance, the one or more new update signals may be requests to initiate location tracking of the container <NUM> via a powered asset <NUM> (or other appropriate computing entity), one or more signals informing that the container <NUM> is loaded onto a plane or moved into a warehouse, a scan or other reading of the container information/data at one or more points in the carrier's transportation and logistics network, and/or the like.

Claim 1:
A system for determining a location of one or more assets (<NUM>) , the system comprising:
a location determining device (<NUM>) coupled to a powered asset (<NUM>), the location determining device configured to detect a location and heading of the powered asset;
one or more powered asset beacons (<NUM>) secured to the powered asset (<NUM>), wherein the one or more powered asset beacons (<NUM>) are configured to detect signals transmitted from an asset beacon (<NUM>) secured to an asset (<NUM>) while the asset beacon (<NUM>) is positioned within a transmission range of a powered asset beacon (<NUM>) of the one or more powered asset beacons;
at least one camera contained in and/or associated with the powered asset beacon and having a known orientation and field of view relative to the powered asset beacon; and
one or more computer processing components configured to:
detect a signal emitted from the asset beacon secured to the asset;
detect the asset within an image captured by the at least one camera; and
determine a location of the asset (<NUM>) based at least in part on the location and the heading of the powered asset (<NUM>), a signal strength of the signal emitted from the asset beacon, and the known orientation and field of view of the at least one camera,
wherein the powered asset beacons (<NUM>) define a communication area within the powered asset (<NUM>) in which the asset beacon (<NUM>) can communicate with one or more of the powered asset beacons,
wherein upon establishing a wireless communication connection with a threshold number of powered asset beacons (<NUM>) associated with a single powered asset, the powered asset beacon is arranged to operate in an advertising mode, wherein said powered asset beacon is arranged to transmit one or more advertising signals regularly, periodically and/or continuously, the one or more advertising signals including one or more unique identifiers and received signal strength indicator.