Patent ID: 12204976

DETAILED DESCRIPTION

I. Introduction

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

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

The term “module” may be hardware, software, or firmware or may be a combination or components thereof.

The term “tape node” refers to an adhesive tape platform or a segment thereof that includes wireless communications functionality and/or one or more of a sensor, a processor, a memory component, an energy source (e.g., a battery or an energy harvesting component). A tape node may have a variety of different form factors, including a multilayer roll or a sheet that includes a plurality of divisible adhesive segments. Once deployed, each tape node can function, for example, as an adhesive tape, label, sticker, decal, or the like, and as a wireless communications device. A “peripheral” tape node (also referred to as an “outer” node, a “leaf” node, and “terminal” node) refers to a tape node that does not have any child nodes.

In certain contexts, the terms “parcel,” “envelope,” “box,” “package,” “container,” “pallet,” “carton,” “wrapping,” and the like are used interchangeably herein to refer to a packaged item or items.

II. Exemplary Operating Environment

FIG.1is a schematic diagram of an example vehicle10transporting a pallet12of parcels14containing goods or other things. In some embodiments, a tertiary wireless network node13is fixed to the pallet12and is configured to communicate wirelessly with the peripheral nodes40and the second electronic logging device22. In this example, the vehicle10is a semi-trailer truck that includes a tractor unit16and a semi-trailer18that carries freight loaded through doors19and21. In general, the vehicle10may be any type of vehicle that can transport goods or other things from one place to another, including any type of motorcycle, car, truck, van, train, ship, or aircraft.

In the illustrated example, the tractor unit16includes a primary electronic logging device20(i.e., a primary ELD) and the semi-trailer18includes a secondary electronic logging device22(i.e., a secondary ELD). In some examples, the primary ELD20and the secondary ELD22each includes one or more wireless transceivers, processors, and memory devices storing programmatic instructions that enable wireless communications over multiple different wireless communications protocols and technologies across different power levels and ranges, such as, but not limited to, GSM, CDMA, TDMA, WCDMA, EDGE, OFDM, GPRS, EV-DO, LTE, WiFi, LoRaWAN, Bluetooth LE, Z-wave, and Zigbee. The secondary ELD22typically includes wireless communications interfaces that have lower power and shorter range than the communications interfaces in the primary ELD. The primary ELD20and the secondary ELD22have at least one communications interface (e.g., Bluetooth, LoRaWAN, and/or wired connection) in common so that they can communicate with one another.

In the illustrated example, the primary ELD20(“ELD 1”) wirelessly communicates with a server24of a first network service26and server28of a second network service30over respective cellular connections32with a cell tower gateway34and over a communications network36, which may be a private network or a public network (e.g., the Internet). Each of the network services26,30includes respective ones of the network servers24,28executing one or more applications and storing and retrieving data from respective data stores25,29. The network services26,30may be, for example, a driver performance assessment service and a logistics management service.

In the illustrated example, the primary ELD20in the tractor unit16typically communicates with the first and second network services26,30over one or more high-power, long-range communications interfaces. In addition, the primary ELD20wirelessly communicates with the secondary ELD22(“ELD 2”) in the semi-trailer18over a lower power, shorter-range wireless communications interface, such as LoRaWAN or Bluetooth LE. In some examples, the primary ELD20also may communicate with the secondary ELD22over a wired connection through a controller area network (CAN) bus system23, which is a vehicle bus standard designed to allow microcontrollers and devices to communicate with each other in applications using a message-based protocol without a host computer. The CAN bus system23also may connect the primary ELD20to the communications interface of a cellular modem that is installed in some embodiments of the tractor unit16of the semi-trailer truck10, thereby enabling the primary ELD20to share the cellular modem's existing cellular subscription service.

The parcels14are associated with peripheral wireless network node devices that include wireless communications, processing, sensing and data storage capabilities. In some examples, these peripheral wireless network node devices are implemented as wireless electronic tags that are carried in or otherwise attached to or integrated with the respective ones of the parcels14. Other examples incorporate the wireless communications, processing, sensing and data storage capabilities into a low-cost, multi-function adhesive tape platform40with a form factor that unobtrusively integrates the components useful for implementing a combination of different logistic functions and also is able to perform a useful ancillary function that otherwise would have to be performed with the attendant need for additional materials, labor, and expense. In some examples, the primary ELD20and the secondary ELD22are implemented as one or more segments of respective types of the adhesive tape platform described in US Patent Application Publication No. US-2018-0165568-A1, which was published on Jun. 14, 2018, and is incorporated in its entirety herein.

In an aspect, the adhesive tape platform is implemented as a collection of adhesive products that integrate wireless communications and sensing components within a flexible adhesive structure in a way that not only provides a cost-effective platform for interconnecting, optimizing, and protecting the components of the tracking system but also maintains the flexibility needed to function as an adhesive product that can be deployed seamlessly into various logistic applications and workflows, including person and object tracking applications, and asset management workflows such as manufacturing, storage, shipping, delivery, and other logistics associated with moving products and other physical objects, including logistics, sensing, tracking, locationing, warehousing, parking, safety, construction, event detection, road management and infrastructure, security, and healthcare. In some examples, the adhesive tape platforms are used in various aspects of logistics management, including sealing parcels, transporting parcels, tracking parcels, monitoring the conditions of parcels, inventorying parcels, and verifying package security. In these examples, the sealed parcels typically are transported from one location to another by truck, train, ship, or aircraft or within premises, e.g., warehouses by forklift, trolleys etc.

An adhesive tape platform includes a plurality of segments that can be separated from the adhesive product (e.g., by cutting, tearing, peeling, or the like) and adhesively attached to a variety of different surfaces to inconspicuously implement any of a wide variety of different wireless communications based network communications and transducing (e.g., sensing, actuating, etc.) applications. Examples of such applications include: event detection applications, monitoring applications, security applications, notification applications, and tracking applications, including inventory tracking, package tracking, person tracking, animal (e.g., pet) tracking, manufactured parts tracking, and vehicle tracking. In example embodiments, each segment of an adhesive tape platform is equipped with an energy source, wireless communication functionality, transducing functionality (e.g., sensor and energy harvesting functionality), and processing functionality that enable the segment to perform one or more transducing functions and report the results to a remote server or other computer system directly or through a network of tapes. The components of the adhesive tape platform are encapsulated within a flexible adhesive structure that protects the components from damage while maintaining the flexibility needed to function as an adhesive tape (e.g., duct tape or a label) for use in various applications and workflows. In addition to single function applications, example embodiments also include multiple transducers (e.g., sensing and/or actuating transducers) that extend the utility of the platform by, for example, providing supplemental information and functionality relating characteristics of the state and or environment of, for example, an article, object, vehicle, or person, over time.

Systems and processes for fabricating flexible multifunction adhesive tape platforms in efficient and low-cost ways also are described in US Patent Application Publication No. US-2018-0165568-A1. For example, in addition to using roll-to-roll and/or sheet-to-sheet manufacturing techniques, the fabrication systems and processes are configured to optimize the placement and integration of components within the flexible adhesive structure to achieve high flexibility and ruggedness. These fabrication systems and processes are able to create useful and reliable adhesive tape platforms that can provide local sensing, wireless transmitting, and locationing functionalities. Such functionality together with the low cost of production is expected to encourage the ubiquitous deployment of adhesive tape platform segments and thereby alleviate at least some of the problems arising from gaps in conventional infrastructure coverage that prevent continuous monitoring, event detection, security, tracking, and other logistics applications across heterogeneous environments.

Referring toFIGS.2and3, the primary ELD20(“ELD 1”) includes a set of tractor management modules50for collecting, analyzing, and presenting vehicle management and driver performance data to the driver performance assessment service26that generates evaluation data, including a driver evaluation for a driver of the vehicle10. The set of tractor management modules50also includes a set of facility scan modules for collecting, analyzing, and presenting logistic management data, including logistic schedule and parcel status information to the logistics management service30.

The primary ELD20includes a processor (not shown) that executes a vehicle status module52to read and transmit vehicle parameter data54that is associated with the driver and the vehicle to the driver performance assessment service26over time (FIG.3, block56). In some examples, the primary ELD20also performs calculations (e.g., aggregating vehicle parameter data54;FIG.3, block58) based on the collected vehicle parameter data54, which includes one or more of: vehicle speed, deceleration, braking, air bag state, 4-way flasher state, engine revolutions per minute, windshield wiper state, a fog light state, steering input information, geographic location information, engine oil pressure, coolant level, driver emergency button state, tire pressure, and the like. In some examples, the vehicle status and performance parameter data54is obtained from sensors that are associated with respective components of the vehicle10.

The primary ELD20also executes an event detection module60to determine whether any of the vehicle parameter data54, taken alone or in combination, exceeds one or more predetermined thresholds which may constitute a driving event (FIG.3, block62). In some examples, the primary ELD processor executes one or more of the tractor management modules50to capture and store the detected vehicle parameter data54in a memory of the primary ELD20(FIG.3, block64). The primary ELD20executes the event detection module60to transmit vehicle parameter data54, which was captured before, during, and/or after the detected driving event, to the driver performance assessment service26for evaluation (FIG.3, block66).

The driver performance assessment network service26may use the transmitted vehicle parameter data together with ancillary information to determine a performance score for the driver (FIG.3, block68). For example, the driver performance assessment network service26may use information about the location of the event, as determined by reading a location tracker module70in the primary ELD20that obtains a series of GPS coordinates over time (seeFIG.2). In addition to or instead of geographic location information, the driver performance assessment network service26may use estimates of the speed of the driver's vehicle10relative the speeds of nearby drivers, as determined from analyses of video data captured before, during, or after the event. The driver performance assessment network service26generates a performance score for the driver of the vehicle10based on an evaluation of the person who is determined to have triggered or caused the event (FIG.3, block72). For example, the driver performance assessment network service26may give the driver a low evaluation score if the driver is determined to have triggered or otherwise was a significant factor in causing the event. On the other hand, the driver performance assessment network service26may give the driver a high evaluation score if the driver is determined to not to have triggered or have been a significant factor in causing the event.

Referring back toFIG.2, the tractor management modules50also includes a facility scan module74that includes a set of communications interface modules that perform wireless communications operations, including wirelessly identifying parcels and wirelessly determining the states of parcels in a facility. In some examples, the facility scan module74incorporates a hierarchy of communications modules, including a long-range gateway module76, a medium-range gateway module78, and a short-range peripheral module80. In the illustrated embodiment that facility scan module74also has logistic schedule module82that includes a manifest or list of the parcels that are scheduled for pick up, drop off, or other logistic event involving the semi-trailer truck10.

Referring toFIG.4, in an example, the primary ELD20starts scanning for assets in a target facility (e.g., a warehouse, a distribution center, or a retail establishment) when the vehicle10is within scanning range of the target facility (FIG.4, block84). In some examples, the primary ELD20broadcasts ping packets in response to a determination that the current GPS location of the vehicle10is within a predetermined scanning range of the target facility (e.g., 5 miles). In other examples, the primary ELD20may use one or more other criteria for determining when to start scanning a target facility.

In an example, the primary ELD20executes a long range (e.g., cellular) communications interface module76to broadcast to the target facility ping packets that include identifiers that have been assigned to the peripheral wireless network nodes (e.g., tape nodes) that are associated with the respective parcels in the manifest. In some examples, the target facility includes a gateway that includes a cellular communications interface and a short-range communications interface (e.g., Bluetooth LE). In these examples, the gateway receives the cellular ping packets broadcasted from the vehicle10and broadcasts the ping packets through a short-range communications interface (e.g., Bluetooth LE) within the target facility. The peripheral wireless network nodes that are associated with identifiers in the list and are present in the target facility respond to the ping packets by broadcasting response packets from their respective short-range communications interfaces (e.g., Bluetooth LE) to the gateway, which broadcasts the response packets to the vehicle10through its long-range communications interface (e.g., cellular).

Other examples may use different sets of hierarchical communications devices. For example, a large facility may include multiple gateways that have different sets of communications interfaces to achieve complete communication coverage of the peripheral wireless network nodes associated with parcels in the facility.

After scanning a facility, the primary ELD20stores and analyzes the scan results (FIG.4, block86). The scan results may confirm that all the parcels listed in the logistic schedule module82(FIG.2) are in the target facility. Alternatively, the scan results may reveal the occurrence of one or more predefined events relating to the parcels listed in the logistic schedule module82. For example, a “missing parcel” event occurs when a parcel listed in the logistic schedule module82does not respond to a ping packet or is not in the facility. A “misrouted parcel” event occurs when a parcel is loaded on the wrong vehicle. An “unfit parcel” event occurs when a parcel listed in the logistic schedule module82is damaged or otherwise unfit for delivery to the end customer. An “improper joinder” event occurs when a parcel is incorrectly designated as part of a group of parcels. An “improper removal” event occurs when a parcel is improperly removed from a designated group. The logistics management network service30may define other events as needed.

Based on the analysis of the stored scan results and the event definitions, the primary ELD20on the tractor unit16of the vehicle10determines whether any of the predetermined events have been detected (FIG.4, block88).

For each event that has been detected, the primary ELD20determines whether or not the event can be resolved locally, without the intervention of the logistics management network service30(FIG.4, block90). In some examples, the primary ELD20accesses a contingency optimization module92(shown inFIG.2). In some examples, the contingency optimization module92contains a set of programmatic instructions or rules for resolving events without the intervention of the logistics management network service30.

For example, in response to the detection of a “missing parcel” event, the primary ELD20logs the event type and other details relating to the event in memory and, based on a mapping between the “missing parcel” event type and the instructions contained in the contingency optimization module92, the primary ELD20executes the relevant instructions in the contingency optimization module92. In some cases, the primary ELD20may be instructed to re-broadcast ping packets to the peripheral wireless network node associated with the non-responsive parcel using a different (e.g., higher) power level and/or a different communications protocol in an attempt to resolve the event (FIG.4, block94).

In another example, in response to a “misrouted parcel” event, the primary ELD20logs the event type and other details relating to the event in memory and, based on a mapping between the “missing parcel” event type and the instructions contained in the contingency optimization module92, the primary ELD20executes the relevant instructions in the contingency optimization module92. In some cases, the primary ELD20may be instructed to broadcast across the facility ping packets that include the identifier of the peripheral wireless network node associated with the parcel of the same type that was misrouted in an attempt to resolve the event (FIG.4, block94).

In another example, in response to the detection of an “unfit parcel” event resulting from exposure of a parcel to, for example, a temperature or an acceleration level greater than the respective threshold levels, the primary ELD20executes the relevant instructions in the contingency optimization module92. Based on the current geographic location of the vehicle10, the location of the nearest replacement part, and the timing of the next scheduled delivery for the vehicle10, the contingency optimization module92instructs primary ELD20to broadcast to the facility ping packets that include one or more identifiers of replacement parcels of the same type of the unfit parcel in an attempt to resolve the event (FIG.4, block94). The primary ELD20may also instruct the vehicle's driver interface system to display instructions to turn back to the last facility visited and obtain the replacement part instead of continuing directly to the next facility.

If the event is not resolvable locally (FIG.4, block90), the primary ELD20transmits the relevant data relating to the detected event to the logistics management network service30over a long-range (e.g., cellular) communications interface. The logistics management network service30evaluates the event data (FIG.4, block96) and resolves the event (FIG.4, block98). In some examples, the logistics management network service30executes a logistics optimization program that takes into account the current locations and costs of vehicles, facilities, and package contents, road and traffic conditions, costs of late or failed delivery, and other factors to determine a global optimal solution for resolving the event.

For example, in response to a “improper joinder” event, the primary ELD20logs the event type and other details relating to the event in memory and, based on a mapping between the “improper joinder” event type and the instructions contained in the contingency optimization module92, the primary ELD20executes the relevant instructions in the contingency optimization module92. In some cases, the primary ELD20may be instructed to log information retrieved from the improperly joined wireless tape node and report the improper inclusion of the identified wireless tape node to the logistics management network service30in an attempt to resolve the event (FIG.4, block94).

In another example, in response to a “improper removal” event, the primary ELD20logs the event type and other details relating to the event in memory and, based on a mapping between the “improper removal” event type and the instructions contained in the contingency optimization module92, the primary ELD20executes the relevant instructions in the contingency optimization module92. In some cases, the primary ELD20may be instructed to log information retrieved from the improperly removed wireless tape node and parcel, and report the improper removal of the identified wireless tape node to the logistics management network service30in an attempt to resolve the event (FIG.4, block98).

Referring toFIG.5, as explained above, the primary ELD20(“ELD 1”) in the tractor unit16communicates with the secondary ELD22(“ELD 2”) in the semi-trailer18over a wireless connection and/or a wired connection via the CAN bus23, as explained above. The secondary ELD22includes a set of trailer management modules100, including a tractor compatibility module102, a trailer scan module104, a logistic event detection module106, and a logistic schedule module108.

Referring toFIG.6, a processor of the secondary ELD22executes the tractor compatibility module102to communicate with the primary ELD20in the tractor unit16. In one example, to communicate with the primary ELD20, the secondary ELD22advertises its presence with a specific authentication identifier and credentials (FIG.6, block110). When the primary ELD20receives data from the secondary ELD22, the primary ELD20establishes a handshake with the secondary ELD22on the corresponding advertisement channel (FIG.6, block112). Then the primary ELD20hands off communication with the secondary ELD22to a data channel (e.g., a Bluetooth LE data channel). The primary ELD learns the secondary ELD's product identification number (PIN) and type identification number (TIN) of the secondary ELD22(FIG.6, block112) and transmits that information to the logistics management service30to let it know that the primary ELD20is communicating with the secondary ELD22(FIG.6, block114).

After establishing the data channel with the primary ELD20in the truck unit16, the secondary ELD22in the semi-trailer18broadcasts the parameters, requirements, and itinerary of the semi-trailer18to the primary ELD20in the tractor unit16(FIG.6, block116). The primary ELD20in tractor unit16broadcasts its capabilities and evaluates the parameters and requirements received from the semi-trailer18(FIG.6, block118). The following descriptive language provides examples of the types and values of parameters and requirements for the tractor unit16and the semi-trailer18:

var tractor = {“vehicle_type” : “tractor”,“owner” : “wallmart”,“max_acceleration” : “2.25 ft/s2”,“max_haul_weight” : “20,000 lbs”,“max_shock” : “2.1 ft/s2”}var itinerary = [{“goods_type” : “light_bulbs”“quantity” : “3,000”“destination” : “distribution_center_abc”,“est_time_of_arrival” : “9:05am_01_04_2019”},{“goods_type” : “light_bulbs”“quantity” : “1,000”“destination” : “distribution_center_cde”,“est_time_of_arrival” : “5:00_pm_01_06_2019”},{“goods_type” : “eggs”“quantity” : “1,500”“destination” : “warehouse_xyz”,“est_time_of_arrival” : “9:30_am_01_06_2019”}]var trailer = {“vehicle_type” : “trailer”,“owner” : “wallmart”,“max_acceleration” : “2.5 ft/s2”,“weight” : “15,000 lbs”,}var freight = [{“goods_type” : “light_bulbs”“quantity” : “4,000”“max_shock” : “4.1 ft/s2”“scheduled_delivery_date” : “01_05_2019”“expiration_date” : “01_2029”},{“goods_type” : “eggs”“quantity” : “1,500”“max_shock” : “2.1 ft/s2”“scheduled_delivery_date” : “01_18_2019”“expiration_date” : “02_18_2019”}]

In this example, the primary ELD20in the tractor unit16and the secondary ELD22in the semi-trailer18are configured to automatically evaluate each other's capabilities and requirements based on the exemplary descriptive language specifications for the tractor unit16and the semi-trailer18. In the illustrated example, the tractor specification meets the trailer's requirements. For example, the tractor unit16and semi-trailer18are owned by the same company (i.e., Walmart), the maximum acceleration of the tractor unit16is below the maximum allowable trailer acceleration, the maximum shock level of the tractor unit16meets the maximum shock level for the freight carried by the semi-trailer18, the scheduled delivery dates for the goods being conveyed in the trailer unit16are later than the estimated time of arrival. As a result, the capabilities and requirements of the tractor unit16meet all of the compatibility requirements of the semi-trailer18(FIG.6, block120) and the tractor unit16is matched to the semi-trailer18(FIG.6, block122).

If one or more of the capabilities of the tractor unit20did not meet one or more of the trailer unit22requirements, the secondary ELD22would determine whether or not the incompatibility is resolvable locally (FIG.6, block124). For example, the estimated time of arrival for the light bulbs at the “distribution_center_cde” is “5:00_pm_01_06_2019”, which is after the scheduled delivery date of “01_05_2019”. However, in some examples, the contingency optimization module92in the primary ELD20includes programmatic instructions or rules that instruct the primary ELD processor to accept a time of arrival that is not later than one day after the scheduled delivery date for non-perishable goods. In these examples, the incompatibility would be waived and the tractor unit16would be matched to the semi-trailer18(FIG.6, block126).

If the incompatibility between the tractor unit16and the semi-trailer18cannot be resolved locally, the primary ELD20reports the incompatibility to the logistics management network service30. The logistics management network service30may resolve the incompatibility in any of a variety of different ways, ranging from waiving one or more incompatibilities to identifying another available tractor unit that matches or is at least a better match than the current tractor unit16(FIG.6, block102).

Referring back toFIG.5, in addition to the tractor compatibility module102, the trailer management modules100further include the trailer scan module104, the logistic event detection module106, and the logistic schedule module108.

The secondary ELD20executes the trailer scan module104and the logistic schedule module108to perform wireless communications operations, including wirelessly identifying parcels and wirelessly determining the states of the parcels in the semi-trailer18. In some examples, the trailer scan module104communicates with peripheral wireless network nodes that are associated with the parcels in the semi-trailer18over a short-range communications interface (e.g., Bluetooth LE).

FIG.7shows example components of an exemplary peripheral wireless network node130. The peripheral wireless network node130includes a number of communication systems132,134. Example communication systems132,134include a GPS system that includes a GPS receiver circuit136(e.g., a receiver integrated circuit) and a GPS antenna138, and one or more wireless communication systems each of which includes a respective transceiver circuit140(e.g., a transceiver integrated circuit) and a respective antenna142. Example wireless communication systems include a cellular communication system (e.g., GSM/GPRS), a Wi-Fi communication system, an RF communication system (e.g., LoRa), a Bluetooth communication system (e.g., a Bluetooth Low Energy system), a Z-wave communication system, and a ZigBee communication system. The peripheral wireless network node130also includes a processor150(e.g., a microcontroller or microprocessor), one or more sensors and energy storage devices152(e.g., non-rechargeable or rechargeable printed flexible battery, conventional single or multiple cell battery, and/or a super capacitor or charge pump), one or more transducers154(e.g., sensors and/or actuators, and, optionally, one or more energy harvesting transducer components). In some examples, the conventional single or multiple cell battery may be a watch style disk or button cell battery that is associated with electrical connection apparatus (e.g., a metal clip) that electrically connects the electrodes of the battery to contact pads on, for example, a flexible circuit board.

Examples of sensing transducers154include a capacitive sensor, an altimeter, a gyroscope, an accelerometer, a temperature sensor, a strain sensor, a pressure sensor, a piezoelectric sensor, a weight sensor, an optical or light sensor (e.g., a photodiode or a camera), an acoustic or sound sensor (e.g., a microphone), a smoke detector, a radioactivity sensor, a chemical sensor (e.g., an explosives detector), a biosensor (e.g., a blood glucose biosensor, odor detectors, antibody based pathogen, food, and water contaminant and toxin detectors, DNA detectors, microbial detectors, pregnancy detectors, and ozone detectors), a magnetic sensor, an electromagnetic field sensor, and a humidity sensor. Examples of actuating (e.g., energy emitting) transducers94include light emitting components (e.g., light emitting diodes and displays), electro-acoustic transducers (e.g., audio speakers), electric motors, and thermal radiators (e.g., an electrical resistor or a thermoelectric cooler).

In some examples, the peripheral wireless network node130includes a memory156that stores data including, for example, profile data, state data, event data, sensor data, localization data, security data, and one or more unique identifiers (ID)158associated with the peripheral wireless network node130, such as a product ID number (PN), a type ID number (TIN), and a media access control (MAC) ID, and control code160. In some examples, the memory156may be incorporated into one or more of the processor150or transducers154, or may be a separate component that is integrated in the peripheral wireless network node130as shown inFIG.7. The control code typically is implemented as programmatic functions or program modules that control the operation of the peripheral wireless network node130, including a communication manager that manages the manner and timing of peripheral wireless network node communications, a peripheral wireless network node power manager that manages power consumption, and a peripheral wireless network node connection manager that controls whether connections with other network nodes are secure connections or unsecure connections, and a peripheral wireless network node storage manager that securely manages the local data storage on the peripheral wireless network node. The peripheral wireless network node connection manager ensures the level of security required by the end application is used and supports various encryption mechanisms. The peripheral wireless network node power manager and peripheral wireless network node communication manager work together to optimize the battery consumption for data communication. In some examples, execution of the control code by the different types of peripheral wireless network nodes described herein may result in the performance of similar or different functions.

FIG.8shows an example method of detecting and responding to events involving assets in a trailer. The peripheral wireless network nodes130typically are associated with respective parcels in the semi-trailer18. In some examples, the logistics management network service30programs the logistic schedule module82with programmatic code that is executed by the secondary ELD22in the semi-trailer18to scan peripheral wireless network nodes according to a fixed and/or a dynamic schedule. For example, the scheduled scan times may be one or a combination of irregular scan intervals, regular (e.g., periodic) intervals, and ad hoc intervals triggered, for example, by detected events.

In some examples, the secondary ELD22executes the trailer scan module78to read the IDs of the peripheral wireless network nodes in the semi-trailer18and also collect sensor data stored in the memories136of the peripheral wireless network nodes110in the semi-trailer18(FIG.8, block162). In some examples, the secondary ELD22aggregates the collected sensor data by data type (FIG.7, block164).

After scanning the semi-trailer18, the secondary ELD22stores and analyzes the scan results to detect events (FIG.8, block166). Based on the analysis of the scan results and the event definitions, the secondary ELD processor in the semi-trailer18of the vehicle10determines whether any events have been detected. The scan results may confirm, for example, that all the parcels listed in the logistic schedule module82are in the semi-trailer18. Alternatively, the scan results may reveal that one or more predefined events relating to the parcels occurred. For example, a “missing parcel” event occurs when a parcel listed in the logistic schedule module82does not respond to a ping packet broadcasted by the secondary ELD22or when such a parcel is not in the semi-trailer18. An “unfit parcel” event occurs, for example, when a parcel listed in the logistic schedule module82is damaged or otherwise unfit for delivery to the end customer. For example, when a temperature sensor in a peripheral wireless network node130associated with a parcel registers one or more temperature readings that exceed or fall below a specified threshold temperature over a specified period of time, the contents of that parcel will be designated as being unfit for delivery. Similarly, when an acceleration or shock sensor in a peripheral wireless network node130associated with a parcel registers one or more acceleration or shock levels that exceed the specified threshold acceleration or shock levels over a specified period of time, the contents of that parcel will be designated as being unfit for delivery. The logistics management network service30may define other semi-trailer events as needed.

For each detected event (FIG.8, block166), the secondary ELD22stores the relevant data in memory (FIG.8, block168) and reports the event to the primary ELD20in the tractor unit16(FIG.8, block170). For each event that has been detected, the primary ELD20determines whether or not the event can be resolved locally, without the intervention of the logistics management network service30(FIG.8, block172). In some examples, the primary ELD20accesses the contingency optimization module92(FIG.2), which contains a set of programmatic instructions or rules for resolving events without the intervention of the logistics management network service30.

For example, in response to the detection of a “missing parcel” event, the primary ELD20in the tractor unit16logs the event type and other details relating to the event in memory and, based on a mapping between the “missing parcel” event type and the instructions contained in the contingency optimization module92, the primary ELD20executes the relevant instructions in the contingency optimization module92. In some cases, the primary ELD20may be instructed by the contingency optimization module92to re-broadcast ping packets to the peripheral wireless network node associated with the non-responsive parcel using a different (e.g., higher) power level and/or a different communications protocol in an attempt to resolve the event (FIG.8, block174).

In another example, in response to the detection of an “unfit parcel” event resulting from exposure to a temperature or an acceleration level greater than the respective threshold levels for these parameters, the primary ELD20executes the relevant instructions in the contingency optimization module92. Based on the current geographic location of the vehicle10, the location of the nearest replacement part, and the timing of the next scheduled delivery for the vehicle10, the primary ELD20may be instructed to broadcast to the facility ping packets that include one or more identifiers associated with replacement parcels of the same type of the unfit parcel in an attempt to resolve the event (FIG.8, block174). In another example, the primary ELD20may instruct the vehicle's driver interface system to display instructions to turn back to the last facility visited and obtain the replacement items instead of directly continuing on to the next facility on the scheduled route.

If the event is not resolvable locally (FIG.8, block172), the primary ELD20transmits the relevant data relating to the detected event to the logistics management network service30over a long-range (e.g., cellular) communications interface. The logistics management network service30evaluates the event data (FIG.8, block176) and resolves the event (FIG.8, block178). In some examples, the logistics management network service30executes a logistics optimization program that takes into account the current locations of vehicles and facilities, their respective contents, road and traffic conditions, and other resources to determine a global optimal solution for resolving the event.

FIG.9shows an example embodiment of the primary ELD20that includes the tractor management modules50described above and further includes additional components that assist in providing the various functionalities of the primary ELD20. These additional components may be implemented in computer or processor readable software or hardware instructions, firmware, hardware, or a combination of software, firmware, and hardware. For example, the features of the tractor management modules50described herein may be implemented in or executed by a combination of processor(s)180, memory182, data store184, one or more communications interfaces186, and an optional graphical or verbal user interface188. In an example, the tractor management modules50may be encoded in a non-transitory computer-readable medium, such as the memory182or the data store184. In addition, the communications components186are configured to interface with the processor160, the memory182, the data store184, and the optional user interface188over one or more data buses. The communications components186also are able to establish wireless communications connections with remote systems, devices, and modules. The user interface of the primary ELD20may be configured to receive inputs and, in response, generate outputs. The user interface component188may include one or more input devices (e.g., a computer keyboard, a computer mouse, and a microphone) and one or more output devices (e.g., a computer monitor and speakers).

FIG.10shows an example embodiment of the secondary ELD22that includes the trailer management modules100described above and further includes additional components that assist in providing the various functionalities of the secondary ELD22. These additional components may be implemented in computer or processor readable software, hardware instructions, firmware, hardware, or a combination of software, firmware, and hardware. For example, the features of the trailer management modules100described herein may be implemented in or executed by a combination of processor(s)190, memory192, data store196, and one or more communications interfaces194. In an example, the trailer management modules100may be encoded in a non-transitory computer-readable medium, such as the memory192or the data store196. In addition, the communications components194are configured to interface with the processor190, the memory192, and the data store196over one or more data buses. The communications components194also are able to establish wireless communications connections with remote systems, devices, and modules. The communications interface(s) of the secondary ELD22may be configured to receive wireless inputs and, in response, generate outputs.

FIG.11shows an example embodiment of the driver performance assessment service26that includes a driver performance assessment module212. In some examples, the driver performance assessment service26includes one or more server computers200at least one of which includes the driver performance assessment module212for producing a driver evaluation and additional components that assist in providing the various functionalities of the driver performance assessment service26. These additional components may be implemented in computer or processor readable software, hardware instructions, firmware, hardware, or a combination of software, firmware, and hardware. For example, the features of the driver performance assessment module212described herein may be implemented in or executed by a combination of processor(s)202, memory204, one or more communications interface components206, a data store208, and a user interface210. In an example, the driver performance assessment module212may be encoded in a non-transitory computer-readable medium, such as the memory204or the data store208. In addition, the communications interface components206are configured to interface with the one or more processors202, the memory204, and the data store208over one or more data buses. The communications interface components206also are able to establish wireless communications connections with remote systems, devices, and modules. The communications interface components206of the server computer(s)200may be configured to receive wireless inputs and, in response, generate outputs.

FIG.12shows an example embodiment of the logistics management service30that includes a logistics contingency resolution module226. In some examples, logistics management service30includes one or more server computers at least one of which includes a logistics contingency resolution module226for resolving events and additional components that assist in providing the various functionalities of the logistics management service30. These additional components may be implemented in computer or processor readable software, hardware instructions, firmware, hardware, or a combination of software, firmware, and hardware. For example, the features of the logistics contingency resolution module226described herein may be implemented in or executed by a combination of one or more processors216, memory218, one or more communications interfaces220, a data store222, and a user interface224. In an example, the logistics contingency resolution module226may be encoded in a non-transitory computer-readable medium, such as the memory218or the data store222. In addition, the one or more communications interface components220are configured to interface with the one or more processors216, the memory218, and the data store222over one or more data buses. The one or more communications interface components220also are able to establish wireless communications connections with remote systems, devices, and modules. The communications interface component(s) of the one or more server computers214may be configured to receive wireless inputs and, in response, generate outputs.

III. CONCLUSION

Other embodiments are within the scope of the claims.