Does anyone know about the internal workings of the system used for tracking for these package delivery services? Specifically, I’m wondering how the data gathered in the field by drivers gets to the shipper and customer.
For fixed stations like post offices and sorting centers, which undoubtedly have direct connections thru the internet, that seems like a no-brainer. But when a delivery comes to a house in the country, the tracking number is scanned by a hand-held device and eventually gets reported to some central location. What is the mechanism of this data transmission?
Is it by cellphone? Satellite? Is data sent one at a time, or in batches, and if in batches, are the batches made up after some time has elapsed?
I suspect the handheld device doesn’t transmit to a fixed end-point, but to the truck, which relays data elsewhere. But I also don’t think the data is accumulated over hours, as I often get a notification of delivery by internet in less than a hour of actual delivery.
I’m wondering what happens if the truck can’t communicate with the central location. Is the data just held until a connection can be made? Is one phone call made for each package? In my neighborhood or in the mountains, cell coverage is spotty, and it might be some time before a connection can be established as the truck goes around our many curves and hills.
While I was writing this post, our USPS postperson came to my door with a package. I asked her this question, but she didn’t know the answer. Then I checked my inbox and found a delivery with a timestamp of 12:46PM. I had scribbled a note to myself that it was delivered at 12:48, and I imagine she entered the data before coming to my porch, and we talked for 30 seconds, so that means to me that the data was sent PDQ with no significant delay at all. At least this time.
Any experts around that can elaborate on this technology?
Somewht related: my employer has a small fleet of service vans which are tracked in near realtime via Trimble. They recently had to have the tracking hardware upgraded because they used 3G cellular service which is being shut down.
In the late 80s, UPS was working on a proprietary communication system. It raised a ruckus in the amateur radio world because the project took some our precious spectrum in the 220 MHz band. Their system never made it off the ground and, of course, hams don’t get our spectrum back.
Hell, I’ve gotten delivery notices fast enough to see the driver getting into the truck. So pretty much instant, at least in my fairly densely populated area.
It’s really not that much data. My pool company has started sending me photos of the pool after they have serviced it - again they arrive almost instantly.
I don’t always get the data instantly. Sometimes there is a 30-45 minute lag between delivery and notification. I haven’t yet determined if this varies by which service (UPS, Fedex, USPS) is being used.
Dewey_Finn, thanks. I was hoping for a little more technical info than just a DIAD is in use. How often is the data transmitted from hand device to central location, and what happens if no cell tower can be contacted right away? Is the DIAD in continuous communication, regularly (like a call every 15 minutes) or sporadically?
I did a gig for UPS during the 2020 holidays; the DIAD I used was literally just a cell phone running a UPS app, so it was in nearly constant contact (as constant as is possible in rural Wyoming, anyway).
For the record, it is possible to forget to scan the parcel on drop-off, and only remember to do it at the next stop when you see that the previous address is still at the top of the list; the driver then has the ability to log it as delivered. The DIAD, though, also logs the location of the driver when a package is scanned out… both to ensure the driver is at the right place, as well as to help build a database of “correct” delivery locations. One of the major reasons I got that gig where I did was because I’d been a land surveyor in the area for many years so knew my way around, when your typical GPS application might send you to an area that is literally miles from the house you are supposed to be delivering to!
You keep using the word “call” which is the wrong term to use when talking about cellular data. It’s not like some dial up modem where the cell phone has to make a call to establish contact with some data center on the other. Data can just go to cell towers whenever there’s a connection, and if there’s no connection undoubtledly the data is queued up and ready to go when it does establish a connection. It’s really not any different from checking e-mail on your smartphone. As the system is updated, it probably sends a small message like “package 19825812543 delivered 1103” and maybe the picture if the driver took one. It’s just a continuous trickle of data, same as any phone app you get or send regular updates from.
It’s an obvious issue, so presumably whoever wrote the DIAD-type app thought of it.
Here’s how I would have constructed the app:
Add the data to the queue - time, date, GPS location, parcel number, the method the deliver was registered - scan, manual entry, signature, etc…
Make a web connection and try to upload the data.
(analogous to “open the web page” then if it does, “fill in the web page form”)
If there’s no connection keep the data in the queue.
Wait for the “upload succeeded” response.
If there’s no acknowledgement of the upload succeeding, keep the data in the queue.
Every so often when there’s data in the queue - try the upload again.
Have an option for manual upload by wifi (and if that fails, USB) when the delivery unit returns to local depot.
Flag situations where duplicate data contains disagreeing information (i.e. scan location and manual entry location disagree…)
The thing is, if you can think about a “what if…” situation, presumably so have the program designers. After all, half their business is assuring correct delivery and ensuring losses are minimized.
Absolute worst case, I presume, is “the DIAD unit fried and never uploaded some data…”
Presumably the result is a reconciliation when the truck returns - complete the list manually to the best of the driver’s ability?
The server presumably can alert - “the following went out on Truck ABC and I have no resolution for them - delivery success or failure”?
For tracking, perhaps that’s the worst, but for package survival, there are worse situations. This just happened on Monday. Check the guy nearly getting smoked at about 40s:
On the Virtual Railfan channel there have been a number of intermodal trains passing through Cajon Pass (Hesperia) with quite a few containers having open doors.
UPS routes a lot of packages through a Chicago-area facility called CACH by rail. About 1.5 million per day, and that ramps up to about 3 million a day in December. Half of that is on rails - either in semi trailers or containers. And similar to the FedEx Worldport in Memphis, CACH also acts as a fulfillment center for some products. I order frozen Chicago-style pizzas now and then, and they originate at CACH.
The originator of that was Qualcomm, but now there are several competitors in the GPS tracking and monitoring world. Twenty years ago, the tracking was usually on the entire trailer, but now, something about the size of a stack of credit cards can be placed in an individual crate or attached to a machine.
I doubt the driver would have to wait until they return to the depot to upload the data. Even if they’re in a spot with no cell service (and even that is going to be rare nowadays), surely they’ll get service further along the route.