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.1Periodic timer starts verification
What ifWhat if a local timer starts verification every 15 minutes?
Claim language“when a verification instruction is received”
A periodic task in the onboard controller reads the approved version from the line data storage unit when the timer expires. The task compares that value with the active map version and starts a download only when the values differ.
1.1Map content digest verification
What ifWhat if the controller verifies the contents of the active map using a stored digest and the map carries no version identifier?
Claim language“determining whether a data version in use is consistent with an authorized version”
The line data storage unit holds a signed manifest containing the expected digest of the map files. The controller hashes the active files in the order specified by the manifest and retrieves the package named in the manifest if the digests differ.
1.1Refresh on every check
What ifWhat if the controller refreshes the onboard map even when the active version matches the approved version?
Claim language“skipping updating”
The controller retrieves a fresh copy of the approved map on every verification cycle. It checks the package signature and file digests, writes the verified files to an inactive storage bank, and switches banks while the train is stationary.
1.2Technician starts package transfer
What ifWhat if a version mismatch displays a maintenance prompt and a technician starts the map download?
The maintenance screen displays the active and approved version identifiers and enables a download control while the train is stationary. When the technician selects the control, the controller requests the approved package, verifies its signature, and stages it for activation.
1.3Wayside nodes hold map packages
What ifWhat if line-side storage nodes hold the updated map packages and distribute them over station wireless links?
Claim language“stored in the global download server”
Each node holds signed packages for its line on local flash storage. After detecting a version mismatch, the onboard controller requests the package for the approved version from the node at its next station stop and resumes any incomplete transfer at a subsequent station.
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
Route updates for warehouse vehicles
An automated warehouse vehicle stores an aisle map with lane directions, stopping points, and docking positions. A warehouse controller provides the approved map version for each floor, and a central server stores the corresponding map packages. When the dispatch system assigns a job, the vehicle compares its local version with the approved version for the assigned floor. If the versions differ, the vehicle downloads and verifies the package before accepting the job.
Component substitution
Signed manifests for line version records
A signed manifest cached on the vehicle replaces the version record read from the line data storage unit. The manifest contains the line identifier, approved release identifier, package digest, and expiration time, and a dispatcher service distributes it to the fleet. On receipt of a verification instruction, the onboard controller checks the manifest signature and expiration, then compares its release identifier with the active map release. If the releases differ, the controller downloads the identified package from the central server and checks its digest before staging it.
Depot caches for map package delivery
A depot cache replaces the central download server as the package source used by onboard controllers. Each cache receives map packages from a publication service and indexes them by line identifier and release identifier. The onboard controller reads the approved release from the line data storage unit and requests that release from the depot cache when its active release differs. The controller checks the package signature before staging the map for activation.
Combination with existing systems
Map status in depot maintenance systems
A depot maintenance system receives the active map release and download status from each onboard controller through the depot wireless network. When a train is assigned a maintenance bay, the maintenance system sends a verification instruction to its controller. The controller reads the approved release from the line data storage unit and retrieves any required package from the central server. The maintenance system records the installation result against the train's maintenance work order.
Automated or data-driven variant
Timetable driven map package staging
An onboard scheduler reads the train's next two hours of assignments from the dispatch feed and extracts the line identifiers in order of first use. When an assignment changes, the scheduler retrieves the approved release for each listed line and compares it with the corresponding locally stored release. The scheduler queues missing or outdated packages in first-use order and downloads them from the central server. The controller verifies each package and stages it in a separate storage slot for activation at an authorized stop.
Specific version of a part
Per-line integer version comparison
The line data storage unit holds an unsigned 32-bit approved version number for each line. On receipt of the verification instruction, the controller reads the value for its assigned line and compares it with the number in the active map header. Equal values end the check without a package transfer.
Resumable automatic map download
A version mismatch causes the controller to request the map package using the line identifier and approved version. The controller saves received bytes in staging storage and requests the remaining byte ranges after a link interruption. It verifies the completed package before making it available for activation.
Version-indexed server package storage
The global download server stores each compressed map package as a read-only file indexed by line identifier and version number. The index identifies the file path, byte length, and digest for each package so the server can locate and return the requested version.
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.
1.1the following steps: when a verification instruction is received, determining whether a data version in use is consistent with an authorized version stored in the line data storage unit: if the data version in use is consistent with the authorized version, skipping updating
Illustrated is a system and method to receive an instruction to access a set of identified data structures, where each identified data structure is associated with a version data structure that includes annotations of particular dependencies amongst at least two members of the set of identical data structures.
A · US 2012/0109914 A1 · abstract
1.2or if the data version in use is not consistent with the authorized version, automatically downloading updated map data corresponding to the authorized version
For example, if data structure “A” version “1” (e.g., [A, 1] as denoted in the version data structure) is dependent upon “F” version “1” to execute, yet the node executing “A” version “1” only has “F” version “0” residing locally, then a version mismatch exists. This mismatch is resolved by delaying the execution of “A” version “1” until a refresh update in the form of “F” version “1” is received.
A · US 2012/0109914 A1 · ¶ 15
If updated software apk1.2 of an upgrade version is released, in the foregoing step 401, a differential upgrade package pack2 for the software apk1.0 of the original version can be downloaded, where the differential upgrade package pack2 is a file obtained by performing differential processing between the updated software apk1.2 of the upgrade version and the software apk1.0 of the original version.
B · US 2015/0220326 A1 · ¶ 53
1.3wherein the updated map data is stored in the global download server.
In the prior art, a mobile phone manufacturer uses a differential file of a latest version such as apk1.1 and an original version such as apk1.0, as an upgrade package, and places the upgrade package in an upgrade server; and a mobile phone downloads, by using an FOTA upgrade, the upgrade package from the server to a cache partition of the mobile phone, and then a differential upgrade program upgrades, by using the upgrade package, the apk1.0 in a system partition to the late
B · US 2015/0220326 A1 · ¶ 6
An empty cell means only that no passage was reproduced there.
Statements in these documents
Issues of forward and backward compatibility most often arise when one wants to perform code upgrades while such systems are on-line.
A · US 2012/0109914 A1 · ¶ 1
FIG. 3 is a diagram of a propagation sequence, according to an example embodiment, whereby through adding a version data structure that includes dependencies we can delay modify updates to simulate a processing order regardless of delays, in the propagation of refresh updates.
A · US 2012/0109914 A1 · ¶ 5
There is an increasingly intense need for version upgrades of a mobile terminal, such as a mobile phone, a tablet computer, a netbook, and a Personal Digital Assistant (PDA).
B · US 2015/0220326 A1 · ¶ 3
The upgrade package apk1.1 is downloaded to a cache partition and an upgrade is performed in the system partition, the original software apk1.0 of the reference version is changed to the apk1.1, and the original version apk1.0 is completely overridden by the version apk1.1 and cannot be retained.
B · US 2015/0220326 A1 · ¶ 8
Cite aspatent.fyi, US 2026/0356401 A1, claim 1, first published 2026-11-20T01:05:31-05:00, https://patent.fyi/US20260356401/, SHA-256 f6be604839e071e8d82bb3c10c4450916a69bc45eb4c1181a889bddff59df723