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.1Reduced speed through curves
What ifWhat if the setter applies a reduced speed limit through a curve while allowing vehicles to pass?
Claim language“as a passage-prohibited area”
The controller stores a speed limit of 5 km/h between two track position markers. Each vehicle uses its odometry and braking curve to reach the limit before the first marker and holds that speed or less until its rear clears the second marker.
1.1Vehicle-specific departure hold
What ifWhat if the setter applies a departure hold to an individual vehicle identified by its fleet number?
Claim language“sets a predetermined area on the track”
The controller stores a hold flag against the selected vehicle and withholds its next departure command. Route allocation continues for other vehicles on tracks with confirmed clearance.
1.2Release based on switch position
What ifWhat if the controller checks switch position and lock status in place of second-user approval?
Claim language“a second user, different from the first user, has approved cancellation”
An operator requests release of a restriction associated with an out-of-position switch. The interlocking clears the restriction after position detector contacts agree with the commanded position and a separate lock detector confirms that the switch is mechanically locked.
1.3Traffic resumes on bypass
What ifWhat if the controller keeps the prohibited area active and restores traffic through a parallel track after approval?
Claim language“cancels the passage-prohibited area”
The controller keeps the restricted section blocked in its route table. After approval, the interlocking checks occupancy on the parallel track, locks the connecting switches, and authorizes movement along the bypass.
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
Restricted aisles for warehouse vehicles
A warehouse fleet controller marks an aisle as passage-prohibited by disabling its edges in the vehicle routing graph. A dispatcher submits a cancellation request that identifies the aisle and the active restriction record. The controller verifies approval from a distinct user account before restoring the edges and distributing the updated graph to the vehicles.
Component substitution
Relay logic for cancellation approval
A latching relay stores the prohibition state for a track section and opens the section's route-permission circuit when set. An authenticated cancellation station energizes a request relay and sends the track-section identifier and requester account identifier to a separate approval station. The approval station closes a normally open contact only for an authenticated approver with a different account identifier and a matching pending request. The request relay contact and approval contact are wired in series to energize the prohibition relay's reset coil.
Parameter or scale variation
Timed approval across adjacent blocks
The controller stores each passage prohibition as a list of 1 to 16 contiguous track blocks and assigns the list a revision number. A cancellation request identifies the list and its current revision and remains pending for 120 seconds. The controller clears all blocks in one transaction if a distinct user approves the matching revision within that window. An expired request or a revision mismatch leaves the prohibition active.
Combination with existing systems
Passage prohibition in route interlocking
The controller supplies a passage-prohibition input to a route interlocking for each track section. The interlocking denies route establishment whenever the requested route includes a section with an active prohibition. After verifying approval from a distinct user, the controller withdraws the prohibition input for the specified section. The interlocking then applies its normal track occupancy, point position and conflicting route checks before authorizing movement.
Automated or data-driven variant
Approval with worksite gate monitoring
A trackside work zone has monitored gate contacts that report whether each access gate is closed and locked. The controller associates the gate identifiers with the restricted track segment and checks that their status reports are current. It clears the passage prohibition only when all associated gates report closed and locked and a distinct user has approved the active cancellation request. An unlocked gate or a loss of current status leaves the prohibition active while the request is pending.
Approval routing from duty records
A duty roster maps each track section and shift interval to the accounts authorized to approve cancellation. When a cancellation request arrives, the controller reads the active shift, excludes the requester's account and sends the request to the remaining eligible accounts. At cancellation, it verifies that the approving account is still on duty for the section, differs from the requester and approved the current restriction record. The controller clears the prohibition after all three checks pass.
Specific version of a part
Scheduled release request
The controller stores a release request time with the restriction and opens a request when its clock reaches that time. An operator reviews the request and confirms release before the controller clears the restriction.
Restriction between track markers
The operator selects two reference markers on a track diagram. The controller flags the intervening track sections as passage-prohibited and rejects route requests that include any flagged section.
Separate authenticated operator approvals
The controller records the first user's account identifier and the restriction identifier with each cancellation request. It accepts approval for that request only from an authenticated session with a different account identifier and permission to approve cancellations.
Release tied to restriction revision
The controller associates the confirmed second-user approval with the restriction identifier and its current revision number. It clears the restriction only when both values still match and then recalculates route availability.
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.1a passage prohibition setter that sets a predetermined area on the track as a passage-prohibited area, and
The gate apparatus includes a determination device for determining whether the gate passage permission/non-permission information represents permission or non-permission based on the medium information read from the non-contact IC medium passing the gate apparatus; and a passage prohibition device for prohibiting passage when the determination result is non-permission.
A · US 2009/0251283 A1 · ¶ 7
The numerical controller sets and holds a partial area of the outer peripheral portion of the turret as an area (passage-prohibited area) prohibited from passing through the selected position and determines whether or not the selected tool is present in the passage-prohibited area or whether or not the passage-prohibited area passes through the selected position as the selected tool is moved to the selected position.
B · US 2018/0164771 A1 · abstract
1.2a passage prohibition canceler that executes, where a first user performs a cancellation operation for the passage-prohibited area, specific processing including a process of confirming whether a second user, different from the first user, has approved cancellation of the passage-prohibited area,
1.3wherein the passage prohibition canceler cancels the passage-prohibited area where it is confirmed that the second user has approved cancellation of the passage-prohibited area.
An empty cell means only that no passage was reproduced there.
Statements in these documents
In addition, such an object item management system is insufficient to prevent unlawful acts such as information leaks.
A · US 2009/0251283 A1 · ¶ 4
In light of the above-described problems, the present invention has an object of providing a property management system capable of managing a take-out state of a property item and preventing an unlawful act to improve the convenience for the user and the manager.
A · US 2009/0251283 A1 · ¶ 6
The present invention relates to a numerical controller, and more particularly, to a numerical controller capable of avoiding interference with rotation of a tool changer turret.
B · US 2018/0164771 A1 · ¶ 1
Cite aspatent.fyi, US 2026/0356403 A1, claim 1, first published 2026-11-20T01:05:31-05:00, https://patent.fyi/US20260356403/, SHA-256 631974a072e83b853150a2eb24310cfce49623c6b235ca7ae1649ac79caef561