IP Library Granted Patent US 12,579,504
Granted Patent B2
US 12,579,504 · App. 18/497,819 · Granted Mar 17, 2026

Apparatus, systems, and methods for enhanced interaction with a node-based logistics receptacle and a parcel customer operating a mobile user device

Inventor: Ole-Petter Skaaksrud (Germantown, TN)
Assignee: Federal Express Corporation
G06Q10/0836A47G29/141A47G29/20G06Q10/06315G06Q10/08G06Q10/0833G06Q20/382G06Q20/401G07C9/00309G07F17/13H04L41/082H04L67/12H04W4/029H04W4/38A47G2029/12105A47G2029/143A47G2029/145G05D2105/285G07C2009/0092H04W4/80
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,579,504
App. No.
18/497,819
Filed
Oct 30, 2023
Granted
Mar 17, 2026
Kind
B2
Examiner
ERB, NATHAN
Art Unit
3628
USPC
705/335
Abstract

A system for enhanced interaction with a node-based logistics receptacle. The system includes a wireless accessory sensor node disposed on the receptacle that monitors at least one of the storage receptacle components of the receptacle to generate internal sensor data, includes a bridge node disposed on the receptacle, and includes an external sensor that is in communication with the bridge node and that is operative to monitor a local environment proximate the receptacle to generate external sensor data. The bridge node includes a processor configured to detect a wireless communication signal, identify the wireless communication signal as corresponding to one of a plurality of anticipated drop off entities, receive the external sensor data, generate carrying confirmation data related to whether a parcel customer is carrying a delivery item, transmit a drop off verification message, receive a drop off verification response message, and transmit an alternative drop off information message.

Claims (185)

1 . A system for enhanced interaction with a node-based logistics receptacle and a parcel customer operating a mobile user device, the node-based logistics receptacle having a plurality of storage receptacle components, the system comprising:

a wireless accessory sensor node disposed on the node-based logistics receptacle, the wireless accessory sensor node having at least one internal sensor that collectively monitors at least one of the storage receptacle components of the node-based logistics receptacle and generates internal sensor data reflecting an interaction with the at least one of the storage receptacle components of the node-based logistics receptacle; and

a bridge node disposed on the node-based logistics receptacle, the bridge node comprising

a bridge node processor,

a bridge node memory coupled to the bridge node processor, the bridge node memory maintaining monitoring and management code for execution by the bridge node processor,

a communication interface coupled to the bridge node processor, the communication interface being operative to communicate with at least a backend server; and

an external sensor in communication with the bridge node, the external sensor being operative to monitor a local environment proximate the node-based logistics receptacle and generate external sensor data relative to the local environment proximate the node-based logistics receptacle; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to:

detect, using the communication interface, a wireless communication signal broadcast from the mobile user device operated by the parcel customer,

identify the wireless communication signal as corresponding to one of a plurality of anticipated drop off entities,

receive the external sensor data generated by the external sensor related to the local environment proximate the node-based logistics receptacle,

generate carrying confirmation data related to whether the parcel customer is carrying a delivery item based upon the external sensor data received from the external sensor,

transmit, using the communication interface, a drop off verification message to the mobile user device operated by the parcel customer when the carrying confirmation data indicates the parcel customer is carrying the delivery item, the drop off verification message requesting the parcel customer to verify that the parcel customer intends to place the delivery item with the node-based logistics receptacle,

receive, using the communication interface, a drop off verification response message from the mobile user device operated by the parcel customer, the drop off verification response message indicating the parcel customer does not intend to place the delivery item with the node-based logistics receptacle, and

transmit, using the communication interface, an alternative drop off information message to the mobile user device operated by the parcel customer in response to the drop off verification response message, the alternative drop off information message providing alternative drop off information related to at least one alternative drop off point for the delivery item.

2 . The system of claim 1 , wherein the alternative drop off information comprises location information for the at least one alternative drop off point.

3 . The system of claim 1 , wherein the alternative drop off information comprises address information for the at least one alternative drop off point.

4 . The system of claim 1 , wherein the alternative drop off information comprises a distance to the at least one alternative drop off point.

5 . The system of claim 4 , wherein the distance to the at least one alternative drop off point is less than a distance to at least another alternative drop off point.

6 . The system of claim 4 , wherein the at least one alternative drop off point comprises a closest one from a plurality of alternative drop off points relative to a location of the node-based logistics receptacle.

7 . The system of claim 1 , wherein the alternative drop off information comprises directions to the at least one alternative drop off point.

8 . The system of claim 1 , wherein the alternative drop off information comprises location information for a second node-based logistics receptacle as the at least one alternative drop off point.

9 . The system of claim 1 , wherein the alternative drop off information comprises traffic data relative to the at least one alternative drop off point.

10 . The system of claim 1 , wherein the alternative drop off information comprises weather data relative to the at least one alternative drop off point.

11 . The system of claim 1 , wherein the alternative drop off information comprises crime data relative to the at least one alternative drop off point.

12 . The system of claim 1 , wherein the alternative drop off information comprises seasonal activity data relative to the at least one alternative drop off point.

13 . The system of claim 1 , wherein the alternative drop off information comprises wait time data relative to the at least one alternative drop off point.

14 . The system of claim 1 , wherein the wait time data comprises historic wait time data relative to the at least one alternative drop off point.

15 . The system of claim 1 , wherein the alternative drop off information comprises operational timing data relative to the at least one alternative drop off point.

16 . The system of claim 15 , wherein the operational timing data comprises data identifying when items are accepted relative to the at least one alternative drop off point.

17 . The system of claim 15 , wherein the operational timing data comprises closing time data relative to the at least one alternative drop off point.

18 . The system of claim 15 , wherein the operational timing data comprises last pickup time data relative to the at least one alternative drop off point.

19 . The system of claim 1 , wherein the alternative drop off information comprises information for a staffed facility as the at least one alternative drop off point.

20 . The system of claim 1 , wherein the alternative drop off information comprises information on a plurality of alternative drop off points, a first of the alternative drop off points identifying a staffed facility and a second of the alternative drop off points identifying a second node-based logistics receptacle.

21 . The system of claim 20 , wherein the information on the first of the alternative drop off points further comprises location information on the staffed facility; and

wherein the information on the second of the alternative drop off points further comprises location information on the second node-based logistics receptacle.

22 . The system of claim 21 , wherein the information on the first of the alternative drop off points further comprises closing time data on the staffed facility; and

wherein the information on the second of the alternative drop off points further comprises last pickup time data on the second node-based logistics receptacle.

23 . The system of claim 21 , wherein the information on the first of the alternative drop off points further comprises wait time data on the staffed facility.

24 . The system of claim 1 , wherein the bridge node memory further maintains the alternative drop off information related to at least one alternative drop off point for the delivery item.

25 . The system of claim 24 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to receive, using the communication interface, an update for the alternative drop off information from the backend server.

26 . The system of claim 24 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to receive, using the communication interface, an update for at least a portion of the alternative drop off information from the backend server.

27 . The system of claim 24 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to receive, using the communication interface, an update for at least a portion of the alternative drop off information from a network storage data source.

28 . The system of claim 1 , wherein the bridge node memory further maintains the alternative drop off information related to a plurality of alternative drop off points including the at least one alternative drop off point for the delivery item.

29 . The system of claim 1 , wherein the bridge node processor, when executing the monitoring and management code, is further programmatically operative to:

detect, after transmitting the alternative drop off information message, receipt of the delivery item within the node-based logistics receptacle based upon information reflecting the interaction with the one or more of the storage receptacle components using the internal sensor data; and

transmit, using the communication interface, deposit information to the backend server in response to the detected placement of the delivery item, the deposit information being related to the detected receipt of the delivery item and causing the backend server to initiate a dispatched logistics operation related to the node-based logistics receptacle.

30 . The system of claim 29 , wherein the bridge node processor, when executing the monitoring and management code, is further programmatically operative to communicate with the mobile user device over the communication interface, in response to detecting placement of the delivery item with the node-based logistics receptacle, to establish a smart contract based connection with the mobile user device, the smart contract based connection providing terms for paid use of the node-based logistics receptacle.

31 . The system of claim 30 , wherein the smart contract based connection comprises a protocol for an automated transaction stored on a blockchain and run in response to meeting at least a payment condition for use of the node-based logistics receptacle as part of shipping the delivery item.

32 . The system of claim 30 , wherein the smart contract based connection provides for paid use of the node-based logistics receptacle under predetermined pricing terms as the payment condition.

33 . The system of claim 32 , wherein the predetermined pricing terms relate to a blockchain-based payment at a first pricing term for internal receipt of the delivery item within the node-based logistics receptacle.

34 . The system of claim 32 , wherein the predetermined pricing terms relate to a blockchain-based payment at a first pricing term for internal receipt of the delivery item within the node-based logistics receptacle, the first pricing term being at a lower rate compared to a second pricing term for external deposit of the delivery item proximate the node-based logistics receptacle.

35 . The system of claim 32 , wherein the predetermined pricing terms relate to a blockchain-based payment on a per-deposit basis for depositing one or more parcel items with the node-based logistics receptacle.

36 . The system of claim 1 , wherein the bridge node processor, when executing the monitoring and management code, is further programmatically operative to:

detect, after transmitting the alternative drop off information message, placement of the delivery item proximate the node-based logistics receptacle based upon subsequent external sensor data generated by the external sensor and without information reflecting the interaction with the one or more of the storage receptacle components using the internal sensor data; and

transmit, using the communication interface, external deposit information to the backend server in response to the detected placement of the delivery item, the external deposit information being related to the detected placement of the delivery item and causing the backend server to initiate a dispatched logistics operation related to the node-based logistics receptacle.

37 . The system of claim 36 , wherein the bridge node processor, when executing the monitoring and management code, is further programmatically operative to communicate with the mobile user device over the communication interface, in response to detecting placement of the delivery item proximate the node-based logistics receptacle, to establish a smart contract based connection with the mobile user device, the smart contract based connection providing terms for paid use of the node-based logistics receptacle.

38 . The system of claim 37 , wherein the smart contract based connection comprises a protocol for an automated transaction stored on a blockchain and run in response to meeting at least a payment condition for use of the node-based logistics receptacle as part of shipping the delivery item.

39 . The system of claim 37 , wherein the smart contract based connection provides for paid use of the node-based logistics receptacle under predetermined pricing terms as the payment condition.

40 . The system of claim 39 , wherein the predetermined pricing terms relate to a blockchain-based payment at a second pricing term for external deposit of the delivery item proximate the node-based logistics receptacle.

41 . The system of claim 39 , wherein the predetermined pricing terms relate to a blockchain-based payment at a first pricing term for internal receipt of the delivery item within the node-based logistics receptacle, the first pricing term being at a lower rate compared to a second pricing term for external deposit of the delivery item proximate the node-based logistics receptacle.

42 . The system of claim 39 , wherein the predetermined pricing terms relate to a blockchain-based payment on a per-deposit basis for depositing one or more parcel items with the node-based logistics receptacle.

43 . The system of claim 36 , wherein the external deposit information transmitted to the backend server related to the detected placement of the delivery item includes a priority level indicator to cause the backend server to initiate the dispatched logistics operation related to the node-based logistics receptacle with a heightened level of urgency.

44 . The system of claim 43 , wherein the priority level indicator reflects that the delivery item is deposited with the node-based logistics receptacle outside of a secured temporary storage area within the node-based logistics receptacle.

45 . The system of claim 43 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the external deposit information to the backend server related to the detected placement of the delivery item to cause the backend server to initiate the dispatched logistics operation with a logistics asset capable of completing the dispatched logistics operation under a predetermined condition.

46 . The system of claim 45 , wherein the predetermined condition comprises a timing criteria related to pickup of the delivery item deposited external to the node-enabled logistics receptacle.

47 . The system of claim 43 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the external deposit information to the backend server related to the detected placement of the delivery item to cause the backend server to initiate the dispatched logistics operation with a selected one of a plurality of logistics assets, the selected one of the logistics assets being capable of completing the dispatched logistics operation under a predetermined time window for pickup of the delivery item.

48 . The system of claim 47 , wherein at least one of the logistics assets comprises a for-hire logistics asset.

49 . The system of claim 48 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the external deposit information to the backend server to cause the backend server to initiate the dispatched logistics operation with the for-hire logistics asset through a smart contract based connection between the backend server and the for-hire logistics asset, the smart contract based connection providing terms for paid pickup of the delivery item disposed external to the node-based logistics receptacle.

50 . The system of claim 1 , wherein the bridge node processor, when executing the monitoring and management code, is further programmatically operative to:

detect, after transmitting the alternative drop off information message, deposit of the delivery item with the node-based logistics receptacle based upon at least one of (a) subsequent external sensor data generated by the external sensor and (b) information reflecting the interaction with the one or more of the storage receptacle components using the internal sensor data;

communicate with the mobile user device over the communication interface, in response to detecting the deposit of the delivery item with the node-based logistics receptacle, to establish a smart contract based connection with the mobile user device, the smart contract based connection providing terms for a first pricing term for deposit of the delivery item with the node-based logistics receptacle and second pricing term for an extended pickup time relative to the node-based logistics receptacle; and

transmit, using the communication interface, deposit information to the backend server in response to the detected deposit of the delivery item, wherein the deposit information is related to the detected deposit of the delivery item and extending the predetermined pickup time, wherein the receipt of the deposit information causes the backend server to initiate a dispatched logistics operation related to the node-based logistics receptacle consistent with extended pickup time.

51 . The system of claim 50 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the deposit information to the backend server to cause the backend server to initiate the dispatched logistics operation consistent with the extended pickup time with a logistics asset capable of conducting the dispatched logistics operation consistent with the extended pickup time.

52 . The system of claim 50 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the deposit information to the backend server to cause the backend server to initiate the dispatched logistics operation consistent with the extended pickup time with a logistics asset capable of conducting the dispatched logistics operation no earlier than the extended pickup time.

53 . The system of claim 52 , wherein the logistics asset comprises a for-hire logistics asset.

54 . The system of claim 53 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the deposit information to the backend server to cause the backend server to initiate the dispatched logistics operation with the for-hire logistics asset through a smart contract based connection between the backend server and the for-hire logistics asset, the smart contract based connection providing payment terms for the for-hire logistics asset to conduct the dispatched logistics operation related to pickup of the delivery item disposed external to the node-based logistics receptacle no earlier than the extended pickup time.

55 . The system of claim 1 , wherein the at least one internal sensor monitors an entrance opening to the node-based logistics receptacle as the one or more of the storage receptacle components, the at least one internal sensor comprising at least one from a group consisting of a first motion sensor detecting a change in motion of the entrance opening, a second motion sensor detecting the change in motion of the entrance opening and a failure to return to a prior state of the one or more of the entrance opening, a third motion sensor detecting movement of what passes through the entrance opening, an inertial sensor detecting a change in motion of the entrance opening, a status sensor detecting a change in orientation of the entrance opening, an accelerometer detecting a change in motion of the entrance opening, and a magnetic sensor detecting a change in position of the entrance opening.

56 . The system of claim 1 , wherein the at least one internal sensor monitors a temporary storage area within the node-based logistics receptacle as the one or more of the storage receptacle components, the at least one internal sensor comprising at least one from a group consisting of an image sensor detecting a change in what is within the temporary storage area, a scale detecting a change in what is within the temporary storage area, a force sensor detecting a change in what has been deposited within the temporary storage area, a light sensor detecting a change in light within the node-enabled logistics receptacle, and a chemical sensor detecting presence of a chemical within the temporary storage area.

57 . The system of claim 1 , wherein the at least one internal sensor monitors a selectively accessible retrieval door on the node-based logistics receptacle as the one or more of the storage receptacle components, the at least one internal sensor comprising at least one from a group consisting of a motion sensor detecting a change in state of the selectively accessible retrieval door, a motion sensor detecting a change in state of the selectively accessible retrieval door and a failure to return to a prior state of the selectively accessible retrieval door, an inertial sensor detecting a change in inertial motion of the selectively accessible retrieval door, a gyroscopic sensor detecting a change in movement of the selectively accessible retrieval door, a status sensor detecting a change in orientation of the selectively accessible retrieval door, a magnetic sensor detecting a change in position of the selectively accessible retrieval door, and a lock sensor detecting a change in secured state of the selectively accessible retrieval door.

58 . The system of claim 1 , wherein the external sensor is disposed external to and separate from the node-based logistics receptacle.

59 . The system of claim 1 , wherein the external sensor is disposed on the node-based logistics receptacle.

60 . The system of claim 1 , wherein the external sensor comprises an image sensor that generates image sensor data as the external sensor data.

61 . The system of claim 60 , wherein the image sensor comprises a machine vision sensor that generates video sensor data as the image sensor data.

62 . The system of claim 60 , wherein the image sensor comprises a machine vision sensor operative to identify an object in the local environment proximate the node-based logistics receptacle based upon video sensor data and is further operative to detect a change in what has been placed within a predetermined range of the node-based logistics receptacle representative of the local environment proximate the node-based logistics receptacle based upon the identified object.

63 . The system of claim 1 , wherein the external sensor comprises one of a plurality of sensing elements of an external sensing infrastructure.

64 . The system of claim 63 , wherein the bridge node is further programmatically operative to receive the external sensor data generated by the external sensor related to the local environment proximate the node-logistics receptacle by being further operative to

communicate with the external sensing infrastructure over the communication interface to establish a smart contract based connection with the external sensing infrastructure, the smart contract based connection providing paid for use of data generated by the one of the sensing elements of the external sensing infrastructure, and

receive the external sensor data generated by the one of the sensing elements of the external sensing infrastructure under terms of the smart contract based connection with the external sensing infrastructure.

65 . The system of claim 64 , wherein the smart contract based connection comprises a protocol for an automated transaction stored on a blockchain and run in response to meeting at least a payment condition for receiving the data generated by the one of the sensing elements of the external sensing infrastructure.

66 . The system of claim 65 , wherein the smart contract based connection provides a cryptographically secure source of the data generated by the one of the sensing elements of the external sensing infrastructure.

67 . The system of claim 65 , wherein the smart contract based connection provides for receiving the data generated by the one of the sensing elements of the external sensing infrastructure under predetermined pricing terms as the payment condition.

68 . The system of claim 67 , wherein the predetermined pricing terms relate to a blockchain-based payment for access rights to the data generated by the one of the sensing elements of the external sensing infrastructure.

69 . The system of claim 67 , wherein the predetermined pricing terms relate to a blockchain-based payment for access rights to the data generated by any of the sensing elements of the external sensing infrastructure.

70 . The system of claim 67 , wherein the predetermined pricing terms relate to a blockchain-based payment on a per-access basis for access rights to the data generated by at least the one of the sensing elements of the external sensing infrastructure.

71 . The system of claim 64 , wherein the smart contract based connection provides for receiving the data generated by the one of the sensing elements of the external sensing infrastructure under predetermined access conditions.

72 . The system of claim 64 , wherein the external sensing infrastructure comprises a security system; and

wherein the one of the sensing elements comprises a first security camera from a set of security cameras used by the security system.

73 . The system of claim 72 , wherein the external sensor comprises the first security camera operably coupled to the bridge node through a remotely accessible interface of the security system; and

wherein the bridge node is further programmatically operative to receive the external sensor data generated by the external sensor related to the local environment proximate the node-logistics receptacle by being further operative to

establish the smart contract based connection with the security system through the remotely accessible interface of the security system, and

receive the external sensor data generated by the first security camera over the remotely accessible interface of the security system and the communication interface of the bridge node.

74 . The system of claim 72 , wherein the external sensor comprises the first camera operably coupled to the bridge node through a remotely accessible interface of the camera-based monitoring system; and

wherein the bridge node is further programmatically operative to receive the external sensor data generated by the external sensor related to the local environment proximate the node-logistics receptacle by being further operative to

establish the smart contract based connection with the camera-based monitoring system through the remotely accessible interface of the camera-based monitoring system, and

receive the external sensor data generated by the first camera over the remotely accessible interface of the camera-based monitoring system and the communication interface of the bridge node.

75 . The system of claim 64 , wherein the external sensing infrastructure comprises a camera-based monitoring system; and

wherein the one of the sensing elements comprises a first camera from a set of cameras used by the camera-based monitoring system.

76 . The system of claim 1 , wherein the external sensor comprises at least one of a plurality of sensing elements of an external sensing infrastructure disposed within a viewable range that includes the node-based logistics receptacle, the one of the sensing elements being operative to provide sensing element sensor data to the wireless accessory sensor node as the external sensor data.

77 . The system of claim 1 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the alternative drop off information message to the mobile user device operated by the parcel customer in response to the drop off verification response message, the alternative drop off information being related to at least one estimated reachable alternative drop off point for the delivery item.

78 . The system of claim 77 , wherein the at least one estimated reachable alternative drop off point for the delivery item is determined by the bridge node processor based upon a scheduled pickup time related to the at least one estimated reachable alternative drop off point and a distance from the location of the node-based logistics receptacle to the at least one estimated reachable alternative drop off point.

79 . The system of claim 77 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit the alternative drop off information message to the mobile user device operated by the parcel customer by being further operative to:

receive a pickup status related to each of a plurality of alternative drop off points from the backend server;

identify the at least one estimated reachable alternative drop off point from the alternative drop off points based upon the pickup status of each of the alternative drop off points; and

transmit the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information is related to the identified at least one estimated reachable alternative drop off point for the delivery item.

80 . The system of claim 77 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit the alternative drop off information message to the mobile user device operated by the parcel customer by being further operative to:

receive a pickup status related to each of a plurality of alternative drop off points from the backend server, the pickup status identifying if each of the alternative drop off points has been serviced;

identify the at least one estimated reachable alternative drop off point from the alternative drop off points based upon (a) the pickup status of each of the alternative drop off points and (b) a distance from the node-based logistics receptacle to each of the alternative drop off points; and

transmit the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information is related to the identified at least one estimated reachable alternative drop off point for the delivery item.

81 . The system of claim 77 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit the alternative drop off information message to the mobile user device operated by the parcel customer by being further operative to:

receive a pickup status related to each of a plurality of alternative drop off points from the backend server, the pickup status identifying a location of pickup entities assigned to service each of the alternative drop off points;

identify the at least one estimated reachable alternative drop off point from the alternative drop off points based upon (a) the pickup status of each of the alternative drop off points and (b) a distance from the node-based logistics receptacle to each of the alternative drop off points; and

transmit the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information is related to the identified at least one estimated reachable alternative drop off point for the delivery item.

82 . The system of claim 1 , wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to transmit, using the communication interface, the alternative drop off information message to the mobile user device operated by the parcel customer by being further operative to:

identify temperature sensitive shipment information for the delivery item based upon the drop off verification response message;

determine an environment appropriate alternative drop off point for the delivery item based upon the identified temperature sensitive shipment information for the delivery item; and

transmit, using the communication interface, the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information message provides the alternative drop off information related to the environment appropriate alternative drop off point for the delivery item.

83 . The system of claim 82 , wherein the environmental appropriate alternative drop off point for the delivery item comprises a climate controlled drop off point capable of maintaining the delivery item in an environmental condition consistent with the identified temperature sensitive shipment information.

84 . The system of claim 82 , wherein the bridge node memory further maintains weather data about a local operating environment of a plurality of alternative drop off points; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to determine the environment appropriate alternative drop off point for the delivery item from the plurality of alternative drop off points based upon the identified temperature sensitive shipment information for the delivery item and the weather data about the local operating environment of each of the plurality of alternative drop off points.

85 . The system of claim 82 , wherein the bridge node memory further maintains internal temperature information about an internal storage environment of a plurality of alternative drop off points; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to determine the environment appropriate alternative drop off point for the delivery item from the plurality of alternative drop off points based upon the identified temperature sensitive shipment information for the delivery item and the internal temperature information about the internal storage environment of each of the plurality of alternative drop off points.

86 . The system of claim 82 , wherein the bridge node memory further maintains internal temperature information about an internal storage environment of a plurality of alternative drop off points; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to determine the environment appropriate alternative drop off point for the delivery item from the plurality of alternative drop off points based upon

(a) the identified temperature sensitive shipment information for the delivery item,

(b) the internal temperature information about the internal storage environment of each of the plurality of alternative drop off points, and

(c) a pickup status related to each of the plurality of alternative drop off points.

87 . The system of claim 86 , wherein the pickup status comprises a time before scheduled pickup related to each of the plurality of alternative drop off points.

88 . The system of claim 82 , wherein the temperature sensitive shipment information for the delivery item comprises temperature rated packaging data that defines a desired thermal characteristic for the delivery item.

89 . The system of claim 82 , wherein the desired thermal characteristic for the delivery item comprises an upper temperature threshold.

90 . The system of claim 82 , wherein the desired thermal characteristic for the delivery item comprises a lower temperature threshold.

91 . The system of claim 82 , wherein the desired thermal characteristic for the delivery item comprises a temperature threshold and time period threshold.

92 . The system of claim 82 , wherein at least a portion of the external sensor data comprises external temperature data relative to the local environment proximate the node-based logistics receptacle; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to determine the environment appropriate alternative drop off point for the delivery item based upon

(a) the identified temperature sensitive shipment information for the delivery item,

(b) the external temperature data relative to the local environment proximate the node-based logistics receptacle, and

(c) a distance to each of a plurality of alternative drop off points; and

transmit, using the communication interface, the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information message provides the alternative drop off information related to the environment appropriate alternative drop off point for the delivery item.

93 . The system of claim 82 , wherein at least a portion of the external sensor data comprises external temperature data relative to the local environment proximate the node-based logistics receptacle;

wherein the bridge node memory further maintains weather data about a local operating environment of a plurality of alternative drop off points; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to determine the environment appropriate alternative drop off point for the delivery item based upon

(a) the identified temperature sensitive shipment information for the delivery item,

(b) the external temperature data relative to the local environment proximate the node-based logistics receptacle,

(c) the weather data about the local operating environment of each of the plurality of alternative drop off points, and

(d) a distance to each of the plurality of alternative drop off points; and

transmit, using the communication interface, the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information message provides the alternative drop off information related to the environment appropriate alternative drop off point for the delivery item.

94 . The system of claim 82 , wherein at least a portion of the external sensor data comprises external temperature data relative to the local environment proximate the node-based logistics receptacle;

wherein the bridge node memory further maintains weather data about a local operating environment of a plurality of alternative drop off points and internal temperature information about an internal storage environment of the plurality of alternative drop off points; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to determine the environment appropriate alternative drop off point for the delivery item based upon

(a) the identified temperature sensitive shipment information for the delivery item,

(b) the external temperature data relative to the local environment proximate the node-based logistics receptacle,

(c) the weather data about the local operating environment of each of the plurality of alternative drop off points,

(d) the internal temperature information about the internal storage environment of the plurality of alternative drop off points, and

(e) a distance to each of the plurality of alternative drop off points; and

transmit, using the communication interface, the alternative drop off information message to the mobile user device operated by the parcel customer, where the alternative drop off information message provides the alternative drop off information related to the environment appropriate alternative drop off point for the delivery item.

95 . A node-based logistics receptacle system for enhanced interaction with a parcel entity operating a mobile user device, the system comprising:

a storage receptacle comprising a plurality of storage receptacle components including at least

a receptacle housing,

an entrance opening disposed on the receptacle housing through which a delivery item may be inserted,

a temporary storage area within the receptacle housing for temporarily maintaining custody of the delivery item when inserted through the entrance opening, and

a selectively accessible retrieval door providing access to within the temporary storage area;

a wireless accessory sensor node disposed on the storage receptacle, the wireless accessory sensor node having at least one internal sensor that collectively monitors at least one of the storage receptacle components of the storage receptacle and generates internal sensor data reflecting an interaction with the at least one of the storage receptacle components of the storage receptacle; and

a bridge node disposed on the node-based logistics receptacle, the bridge node comprising

a bridge node processor,

a bridge node memory coupled to the bridge node processor, the bridge node memory maintaining monitoring and management code for execution by the bridge node processor,

a communication interface coupled to the bridge node processor, the communication interface being operative to communicate with at least a backend server; and

an external sensor in communication with the bridge node, the external sensor being operative to monitor a local environment proximate the storage receptacle and generate external sensor data relative to the local environment proximate the storage receptacle; and

wherein the bridge node processor, when executing the monitoring and management code, is programmatically operative to:

detect, using the communication interface, a wireless communication signal broadcast from the mobile user device operated by the parcel customer,

identify the wireless communication signal as corresponding to one of a plurality of anticipated drop off entities,

receive the external sensor data generated by the external sensor related to the local environment proximate the storage receptacle,

generate carrying confirmation data related to whether the parcel customer is carrying a delivery item based upon the external sensor data received from the external sensor,

transmit, using the communication interface, a drop off verification message to the mobile user device operated by the parcel customer when the carrying confirmation data indicates the parcel customer is carrying the delivery item, the drop off verification message requesting the parcel customer to verify that the parcel customer intends to deposit the delivery item with the storage receptacle,

receive, using the communication interface, a drop off verification response message from the mobile user device operated by the parcel customer, the drop off verification response message indicating the parcel customer does not intend to deposit the delivery item with the storage receptacle, and

transmit, using the communication interface, an alternative drop off information message to the mobile user device operated by the parcel customer in response to the drop off verification response message, the alternative drop off information message providing alternative drop off information related to at least one alternative drop off point for the delivery item.

Assignments (2)
MERGER Recorded Jul 23, 2024
From: FEDEX CORPORATE SERVICES, INC.
To: FEDERAL EXPRESS CORPORATION
Reel/Frame 068493/0092 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 8, 2023
From: SKAAKSRUD, OLE-PETTER
To: FEDEX CORPORATE SERVICES, INC.
Reel/Frame 065493/0607 →
Continuity (2)
Provisional Application 63434492 · Dec 22, 2022
Related Publication 20240211855A1 · Jun 27, 2024
References Cited (96)
US 5818336A · Varge et al. · 1998 [cited by applicant]
US 9371681B2 · Tompkins · 2016 [cited by applicant]
US 9609973B1 · Pleasant · 2017 [cited by applicant]
US 10097353B1 · Carlson · 2018 [cited by examiner]
US 10373100B2 · Goja · 2019 [cited by applicant]
US 10740717B2 · Skaaksrud · 2020 [cited by applicant]
US 10824774B2 · Santorone et al. · 2020 [cited by applicant]
US 11620866B1 · Goetz et al. · 2023 [cited by applicant]
US 11716444B2 · Ritchey et al. · 2023 [cited by applicant]
US 12093884B2 · Skaaksrud · 2024 [cited by applicant]
US 12093885B2 · Skaaksrud · 2024 [cited by applicant]
US 12131285B2 · Skaaksrud · 2024 [cited by applicant]
US 12260368B2 · Skaaksrud · 2025 [cited by applicant]
US 12277528B2 · Skaaksrud · 2025 [cited by applicant]
US 12361370B2 · Skaaksrud · 2025 [cited by applicant]
US 12367453B2 · Skaaksrud · 2025 [cited by applicant]
US 12406224B2 · Skaaksrud · 2025 [cited by applicant]
US 20050154602A1 · Hertz · 2005 [cited by applicant]
US 20060235739A1 · Levis et al. · 2006 [cited by applicant]
US 20080189161A1 · Daily et al. · 2008 [cited by applicant]
US 20130325231A1 · Park · 2013 [cited by applicant]
US 20140035721A1 · Heppe et al. · 2014 [cited by applicant]
US 20150102903A1 · Wilkinson · 2015 [cited by applicant]
US 20150106296A1 · Robinson et al. · 2015 [cited by applicant]
US 20150154542A1 · Skaaksrud · 2015 [cited by examiner]
US 20150154544A1 · Skaaksrud · 2015 [cited by examiner]
US 20150154547A1 · Skaaksrud · 2015 [cited by examiner]
US 20150154549A1 · Skaaksrud · 2015 [cited by examiner]
US 20150154555A1 · Skaaksrud · 2015 [cited by examiner]
US 20150178677A1 · Strand et al. · 2015 [cited by applicant]
US 20150339862A1 · Skaaksrud · 2015 [cited by applicant]
US 20150349917A1 · Skaaksrud · 2015 [cited by applicant]
US 20150363843A1 · Loppatto et al. · 2015 [cited by applicant]
US 20160025549A1 · Motoyama · 2016 [cited by applicant]
US 20160051073A1 · Heinz et al. · 2016 [cited by applicant]
US 20160232489A1 · Skaaksrud · 2016 [cited by applicant]
US 20160335594A1 · Czachor, Jr. et al. · 2016 [cited by applicant]
US 20170041451A1 · Wilkinson · 2017 [cited by applicant]
US 20170091710A1 · Van Dyke · 2017 [cited by applicant]
US 20170091711A1 · Akselrod et al. · 2017 [cited by applicant]
US 20170124510A1 · Caterino et al. · 2017 [cited by applicant]
US 20170278063A1 · Dixon · 2017 [cited by examiner]
US 20170323545A1 · Gillen et al. · 2017 [cited by applicant]
US 20180046978A1 · Tartal et al. · 2018 [cited by applicant]
US 20180186454A1 · Luckay et al. · 2018 [cited by applicant]
US 20180197140A1 · Goja · 2018 [cited by examiner]
US 20180365641A1 · Zhu · 2018 [cited by applicant]
US 20180374043A1 · Irwin et al. · 2018 [cited by applicant]
US 20190012625A1 · Lawrenson et al. · 2019 [cited by applicant]
US 20190130349A1 · Ferguson et al. · 2019 [cited by applicant]
US 20190287063A1 · Skaaksrud et al. · 2019 [cited by applicant]
US 20200189731A1 · Mistry et al. · 2020 [cited by applicant]
US 20200240166A1 · Graner · 2020 [cited by applicant]
US 20200311671A1 · Lundahl · 2020 [cited by applicant]
US 20210105435A1 · Ritchey et al. · 2021 [cited by applicant]
US 20220051183A1 · Franzo · 2022 [cited by applicant]
US 20220233010A1 · Sundaresan · 2022 [cited by applicant]
US 20230068077A1 · Kashi · 2023 [cited by applicant]
US 20230206174A1 · Li et al. · 2023 [cited by applicant]
US 20230410028A1 · O'Toole et al. · 2023 [cited by applicant]
US 20240211874A1 · Skaaksrud · 2024 [cited by applicant]
US 20250148857A1 · Ecton et al. · 2025 [cited by applicant]
CA 2829139A1 · 2014 [cited by applicant]
WO 2008113568A1 · 2008 [cited by applicant]
FD (Fair Disclosure) Wire, “United Parcel Service Inc Analyst Meeting—Final,” CQ-Roll Call, Inc., Sep. 15, 2011. [cited by examiner]
U.S. Appl. No. 18/212,751 Notice of Allowance mailed Dec. 13, 2024. [cited by applicant]
Perlmutter, “Pudo: What it is, and How it Can Make Your Delivery Process More Efficient”, Bringg, 3 pages, Mar. 24, 2022, bringg.com, Retrieved from https://www.bringg.com/bloglin-store-pickup/pudo-pick-up-drop-off/. [cited by applicant]
U.S. Appl. No. 18/212,738 Notice of Allowance mailed Jan. 21, 2025. [cited by applicant]
U.S. Appl. No. 18/226,239 Notice of Allowance mailed Feb. 18, 2025. [cited by applicant]
U.S. Appl. No. 18/226,239 Office Action mailed Jul. 30, 2024. [cited by applicant]
U.S. Appl. No. 18/226,243 Notice of Allowance mailed Nov. 15, 2024. [cited by applicant]
Faugere et al., “Hyperconnected City Logistics: Smart Lockers Terminals & Last Mile Delivery Networks”, IPIC 3rd International Physical Internet Conference Jun. 2016, pp. 1-14. [cited by applicant]
U.S. Appl. No. 18/240,146 Notice of Allowance mailed Apr. 22, 2024. [cited by applicant]
U.S. Appl. No. 18/240,173 Notice of Allowance mailed May 6, 2024. [cited by applicant]
Lee, “Optimization of Modular Drone Delivery System”, IEEE Xplore, 2004, 8 pages. [cited by applicant]
U.S. Appl. No. 18/226,241 Notice of Allowance mailed Jun. 10, 2024. [cited by applicant]
Plasilova et al., “RFID-based Multi-purpose Smart Post Boxes in Smart Cities”, 2022 6th International Conference on Smart Grid and Smart Cities (ICSGSC), Chengdu, China, 2022, pp. 184-189. [cited by applicant]
U.S. Appl. No. 18/226,248 Office Action mailed Apr. 3, 2025. [cited by applicant]
U.S. Appl. No. 18/497,801 Office Action mailed Apr. 24, 2025. [cited by applicant]
U.S. Appl. No. 18/479,042 Office Action mailed May 7, 2025. [cited by applicant]
U.S. Appl. No. 18/240,123 Office Action mailed May 8, 2025. [cited by applicant]
U.S. Appl. No. 18/212,756 Office Action mailed May 21, 2025. [cited by applicant]
Bachofner et al., “City Logistics: Challenges and Opportunities for technology providers”, Journal of Urban Mobility, Dec. 2022, pp. 1-10, vol. 2, Elsevier, https://doi.org/j.urbmob.2022.100020. [cited by applicant]
Wagner et al., “Delay Tolerant, radio frequency identification (RFID)-enabled sensing”, IEEE International Conference on Wireless for Space and Extreme Environments, Oct. 30, 2014, DOI: 10.1109/WISEE.2014.6973078. [cited by applicant]
U.S. Appl. No. 18/497,787 Notice of Allowance mailed Jul. 23, 2025. [cited by applicant]
U.S. Appl. No. 18/212,745 Office Action mailed Aug. 14, 2025. [cited by applicant]
U.S. Appl. No. 18/497,801 Notice of Allowance mailed Aug. 19, 2025. [cited by applicant]
U.S. Appl. No. 18/886,948 Office Action mailed Sep. 11, 2025. [cited by applicant]
U.S. Appl. No. 18/479,045 Notice of Allowance mailed Mar. 10, 2025. [cited by applicant]
U.S. Appl. No. 18/497,787 Office Action mailed Mar. 26, 2025. [cited by applicant]
U.S. Appl. No. 18/479,037 Office Action mailed Sep. 29, 2025. [cited by applicant]
U.S. Appl. No. 18/497,787 Notice of Allowance mailed Oct. 15, 2025. [cited by applicant]
U.S. Appl. No. 18/497,801 Notice of Allowance mailed Oct. 15, 2025. [cited by applicant]
U.S. Appl. No. 18/226,248 Notice of Allowance mailed Oct. 22, 2025. [cited by applicant]
Chou et al., “A Bluetooth-Smart Insulating Container for Cold-Chain Logistics”, 2013 IEEE 6th International Conference on Service-Oriented Computing and Applications, 2013, pp. 298-303. [cited by applicant]
U.S. Appl. No. 18/479,047 Office Action mailed Dec. 3, 2025. [cited by applicant]
Cited By (3)
US 12,639,660 US 12,664,512 US 12,699,953