Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.
1.1Local drop off processing
What ifWhat if the receptacle controller handled drop off decisions without a backend server?
Claim language“a backend server”
The controller stores expected visitor identifiers and alternate drop off locations in local flash memory. It matches phone identifiers against the stored list, reads the sensors, and sends responses over a direct radio link to the phone. A service technician updates both lists through a wired maintenance port.
1.2Hardwired compartment door sensing
What ifWhat if passive door switches wired directly to the bridge replaced the wireless sensor node?
Claim language“a wireless accessory sensor node”
A magnet on each compartment door closes a reed switch on the frame when the door shuts. A two-conductor cable connects each switch to a digital input on the bridge, which debounces the contact and records the door state.
1.5Manual visit code entry
What ifWhat if the customer entered a visit code on the receptacle keypad to identify the visit?
Claim language“a wireless communication signal broadcast from the mobile user device”
The customer reads a six-digit visit code from the phone screen and enters it on a wired keypad. The controller matches the entry against active codes for expected visits, checks its expiration time, and marks the code as used after a successful match.
1.8Customer reports parcel presence
What ifWhat if the system recorded whether the customer was carrying a parcel from an explicit answer on the phone?
Claim language“based upon the external sensor data”
After the session starts, the phone displays yes and no buttons for reporting whether the customer has a parcel in hand. The controller stores the selected value with the session identifier and uses a yes response to trigger the drop off prompt.
1.9Verification at the receptacle
What ifWhat if the receptacle displayed the drop off verification prompt on its own screen?
Claim language“a drop off verification message to the mobile user device”
When the carrying status indicates a parcel is present, the bridge writes the prompt to a wired display and enables two sealed push buttons. The bridge reads the selected button through a digital input and associates the choice with the active visit.
Section 2 · machine-generated
Variations
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
Other field of use
Equipment returns at a lending cabinet
An equipment lending room uses a compartment cabinet with wireless door sensors, a bridge and an overhead depth sensor aimed at the return area. The lending server associates a short-lived identifier broadcast by a borrower's phone with an open loan, and the bridge checks the depth frames for an object moving with the borrower. The bridge sends a return confirmation prompt to the phone when the check is positive. If the borrower declines, the server sends the staffed counter's opening hours and the equipment categories it accepts.
Component substitution
Strain gauges for compartment interaction sensing
A strain-gauge load cell under each compartment floor serves as the internal sensor for a wireless accessory node mounted on the cabinet. The node samples the load cells through an instrumentation amplifier and records a load change when the reading settles at a new level after an interaction. It sends the compartment identifier, timestamp and signed load change to the bridge. A separate external sensor supplies the carrying check that triggers the phone prompt, and a declined prompt triggers a message about another drop-off point.
Parameter or scale variation
Multi-bay sensing with independent confirmation windows
A cabinet bank has 12 compartments grouped into four bays, with one wireless door-sensor node per bay and one bridge for the bank. Each bay has an overhead depth sensor aimed at a 1.2-meter-deep approach zone and sampled at 10 frames per second. A short-range receiver at each bay reports phone broadcasts to the bridge, which matches identifiers against the server's expected arrivals and assigns each identifier to the bay with the highest median signal strength over two seconds. The bridge maintains a separate 15-second confirmation window for each matched phone with a positive carrying check and sends drop-off information for another point after a decline.
Combination with existing systems
Drop-off routing with compartment reservations
The backend connects to a compartment reservation system that tracks free compartments by internal dimensions and permitted item weight. Each receptacle bridge forwards door and occupancy updates from its wireless accessory nodes, while its external sensor supplies the carrying check used to prompt the customer. When the customer declines the current drop-off, the backend uses the item's recorded dimensions and weight to place a temporary hold on a suitable compartment at another receptacle. The phone receives the hold expiration time and a one-time access code that the receiving bridge checks against the reservation before unlocking the compartment.
Automated or data-driven variant
Parcel detection from tracked depth frames
A depth camera above the approach area sends timestamped frames to the bridge, which runs a model trained on labeled sequences of people carrying parcels, walking empty-handed and pushing carts. The bridge tracks each person and each detected parcel through successive frames and records a positive carrying result when a parcel remains alongside the person's torso or hands and moves with them for at least one second. The server associates the result with an expected phone identifier when one tracked person and one matched phone are present in the approach zone. The bridge sends the verification prompt after a positive result and sends information about another drop-off point after a decline.
Alternate selection from recent sensor reports
Each receptacle bridge sends timestamped door and compartment occupancy reports from its wireless accessory nodes to the backend. The backend combines those reports with recorded compartment dimensions and a maintenance flag for each compartment. After a customer declines a drop-off prompt, the backend selects a receptacle with a closed, empty compartment that fits the parcel, has no active maintenance flag and has reported its state within the past minute. The originating bridge sends the selected point's identifier and accepted parcel dimensions to the phone.
Specific version of a part
Bridge with wired network access
A microcontroller in a gasketed enclosure on the receptacle executes monitoring and management code stored in serial flash memory. A wired network interface connects the bridge to the backend server, and a separate short-range radio interface handles nearby phone communications.
Overhead depth sensor
A time-of-flight depth sensor mounts above the receptacle and measures distance across the approach area at 15 frames per second. A wired connection delivers the depth frames to the bridge.
Expiring visit identifiers
The server assigns a random 128-bit identifier to each expected visit and sends the identifier to the customer’s phone and the bridge. The bridge compares the identifier in each received broadcast with its table of expected visits and accepts a match during the associated time window.
Decline response with session identifier
When the customer selects the decline button, the phone sends a response containing the session identifier and a decline code over the short-range radio connection. The bridge associates the response with the active prompt and records the customer’s choice.
Section 3 · quoted from USPTO records
Other work
Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.
The remote computer(s) 1144 can be a personal computer, a server, a router, a network PC, a workstation, a microprocessor based appliance, a peer device or other common network node and the like, and typically includes many or all of the elements described relative to computer 1112.
A · US 2009/0037302 A1 · ¶ 66
1.2a 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
In some of these embodiments, the node within the node-enabled logistics receptacle assembly may include at least one sensor that monitors for a deposited package the custody of which is temporarily maintained by the node-enabled logistics receptacle assembly. As discussed more with respect to FIGS. 89A-89D, such a sensor may be implemented with one or more internal sensors, external sensors, and/or door sensors to help detect packages.
B · US 2015/0154551 A1 · ¶ 634
1.3a 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 the backend server; and
Remote computer(s) 1144 is logically connected to computer 1112 through a network interface 1148 and then physically connected via communication connection 1150.
A · US 2009/0037302 A1 · ¶ 66
The node memory storage and communication interface are each coupled to the node processing unit. Further, the node memory storage maintains code for execution by the node processing unit as well as at least a user criteria level related to wireless communication signal activity near the node assembled with the receptacle.
B · US 2015/0154551 A1 · ¶ 14
1.4an 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
However, in FIG. 89D, node 8220 is coupled via wiring 8935 to an external sensor 8930 that is operative to monitor an area or region near the receptacle 8220.
B · US 2015/0154551 A1 · ¶ 777
1.5wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: detect, using the communication interface, a wireless communication signal broadcast from the mobile user device operated by the parcel customer,
The communication interface can detect a signal broadcast from a user access device and communicate with another network device in the wireless node network.
B · US 2015/0154551 A1 · ¶ 14
1.6wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: identify the wireless communication signal as corresponding to one of a plurality of anticipated drop off entities,
1.7wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: receive the external sensor data generated by the external sensor related to the local environment proximate the node-based logistics receptacle,
However, in FIG. 89D, node 8220 is coupled via wiring 8935 to an external sensor 8930 that is operative to monitor an area or region near the receptacle 8220.
B · US 2015/0154551 A1 · ¶ 777
1.8wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: 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,
1.9wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: 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,
1.10wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: 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
1.11wherein the combination of the bridge node processor, when executing the monitoring and management code, and the backend server and in conjunction with communications between the bridge node processor and the backend server about communications with the mobile user device, being programmatically operative to: 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.
An empty cell means only that no passage was reproduced there.
Statements in these documents
There is no convenient mechanism for asset verification based on a characteristic other than time.
A · US 2009/0037302 A1 · ¶ 5
The industrial environment can include various assets that can be verified and/or quality ensured, wherein at least two assets can be hierarchically arranged, such as one that is utilized to manufacture consumables, textiles, automobiles, or any other suitable industrial environment.
A · US 2009/0037302 A1 · ¶ 7
These tags typically only allow for basic tracking, but do not provide a way to improve asset management using information about the environment in which the items are tracked.
B · US 2015/0154551 A1 · ¶ 7
Sensor-based tracking systems are also known which can provide more information than RFID systems.
B · US 2015/0154551 A1 · ¶ 8
Cite aspatent.fyi, US 2026/0354609 A1, claim 1, first published 2026-11-19T00:49:41-05:00, https://patent.fyi/US20260354609/, SHA-256 bf9e40bdf7894428547ec118c8748312cc5f6e63a906aa17e1b2d1b89659184d