# US 2024/0005436 A1 · Backend System for a Passenger Transport System

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0005436 A1
- Document ID: US20240005436A1
- Status: Published application
- Kind: A1
- Application number: 18/341,361
- Filed: 2023-06-26
- Published: 2024-01-04
- Earliest claimed: 2022-06-30
- Assignees: Scheidt & Bachmann GmbH
- Applicants: Scheidt & Bachmann GmbH
- Inventors: Kai Oelert; Marian Ka{hacek over (s)}{hacek over (s)}ovic
- Web page: https://patentgrep.com/patent/US20240005436A1

## CPC

- G06Q 50/40: Business processes related to the transportation industry (shipping G06Q10/083)
- G06Q 10/021: {Re-booking existing reservations}
- G06Q 30/04: Billing or invoicing
- G07B 15/02: taking into account a variable factor such as distance or time, e.g. for passenger transport, parking systems or car rental systems (G07B15/06 takes precedence; taximeters G07B13/00; parking meters per se G07F17/24)
- G07C 9/27: with central registration
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G07B: TICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
- G07C: TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE

## Abstract

A backend system for a passenger transport system includes: data memory for storing at least one user data set containing at least one electronic medium identifier authorizing the execution of a transport trip and at least one first transport usage condition linked to the electronic medium identifier; a receiving module configured to receive a change data set containing at least one second transport usage condition, at least one first time date and at least one user identifier for identifying a stored user data set; a change module configured to change the linkage between the electronic medium identifier stored in the identified user data set and the first transport usage condition for at least one future transport trip; a trip reconstruction module configured to reconstruct an executed transport trip at least based on a received user identifier; and a generation module configured to generate a billing data set.

## Claims

### Claim 1

A backend system for a passenger transport system, comprising:
at least one data memory configured to store at least one user data set, containing at least one electronic medium identifier authorizing the execution of a transport trip and at least one first transport usage condition linked to the electronic medium identifier,
at least one receiving module configured to receive a change data set generated by an interface device of the passenger transport system, the change data set containing at least one second transport usage condition, at least one first time date, and at least one user identifier for identifying a stored user data set,
at least one change module configured to change the linkage between the electronic medium identifier stored in the identified user data set and the first transport usage condition for at least one future transport trip based on the received second transport usage condition,
at least one trip reconstruction module configured to reconstruct an executed transport trip based at least on a check-in data set received from a validator device of the passenger transport system containing at least one electronic medium identifier and a provided check-out data set containing at least the same electronic medium identifier, and
at least one generation module configured to generate a billing data set at least based on the reconstructed transport trip and the transport usage condition of the user data set linked to the electronic medium identifier.

### Claim 2 (depends on 1)

The backend system according to claim 1, wherein
the backend system comprises a transmitting module configured to transmit a change message about the at least one second transport usage condition to the interface device after a change of the linkage,
and/or
the backend system comprises a transmitting module configured to transmit a change message about the at least one second transport usage condition to a communication address stored in the identified user data set after a change of the linkage.

### Claim 3 (depends on 1)

The backend system according to claim 1, wherein
the change data set contains at least one second time date indicating a validity time duration of the second transport usage condition,
wherein the backend system comprises at least one time module configured to set a timer according to the second time date, and
wherein the change module is configured to change the linkage between the electronic medium identifier stored in the identified user data set and the second transport usage condition upon detection of an expiration of the timer based on the first transport usage condition.

### Claim 4 (depends on 1)

The backend system according to claim 1, wherein
the change data set contains at least one trip number indicating the number of trips for which the second transport usage condition is valid,
wherein the backend system comprises at least one counter module configured to set a counter corresponding to the number of trips, and
wherein the change module is configured to change the linkage between the electronic medium identifier stored in the identified user data set and the second transport usage condition upon detection of an expiration of the counter based on the first transport usage condition.

### Claim 5 (depends on 1)

The backend system according to claim 1, wherein
the backend system comprises a transmitting module configured to transmit a received change data set to at least one further interface device of the passenger transport system after a change of the linkage.

### Claim 6

An interface device for a passenger transport system, wherein the interface device is arrangeable in a passenger transport vehicle and/or in a transport stop area, comprising:
at least one detection module configured to detect an electronic medium identifier of a ticket medium, wherein the electronic medium identifier is an electronic medium identifier authorizing the execution of a transport trip and linked to a first transport usage condition,
at least one sensing module configured to detect a second transport usage condition determined by means of a user interface of the interface device and linkable to the detected medium identifier,
at least one linking module configured to link a detected electronic medium identifier to the determined second transport usage condition,
at least one generation module configured to generate a change data set containing the detected electronic medium identifier, the second transport usage condition linked with the detected electronic medium identifier, and at least one first time date, and
at least one transmitting module configured to transmit the generated change data set to a backend system of the passenger transport system.

### Claim 7 (depends on 6)

The interface device according to claim 6, wherein
the interface device is a validator device.

### Claim 8 (depends on 7)

The interface device according to claim 7, wherein
the interface device comprises a checking module configured to check an admissibility of the detected electronic medium identifier based on a comparison of the detected electronic medium identifier with a plurality of electronic medium identifiers stored in a negative list, and
the interface device comprises a release module configured to release a passing through the interface device if the detected electronic medium identifier is a permissible electronic medium identifier,
wherein the release module is configured to block a passing through the interface device if the detected electronic medium identifier is a non-permissible electronic medium identifier.

### Claim 9 (depends on 6)

The interface device according to claim 6, wherein
the interface device comprises a receiving module configured to receive a change data set from a further interface device of the passenger transport system and/or from the backend system,
the interface device comprises a data memory configured to store the received change data set,
the interface device comprises a checking module configured to check the admissibility of the detected electronic medium identifier based on a comparison of the detected electronic medium identifier with the electronic medium identifier of the stored change data set, and
the interface device comprises a release module configured to release a passing through the interface device if the detected electronic medium identifier corresponds to the stored electronic medium identifier.

### Claim 10 (depends on 6)

The interface device according to claim 6, wherein
the interface device comprises a data memory configured to store the change data set and/or a check-in data set,
wherein the data memory is configured to provide the change data set and/or a check-in data set such that the change data set and/or a check-in data set is receivable by an inspection device via a data network.

### Claim 11 (depends on 6)

A passage barrier for a passenger transport system comprising:
an interface device according to claim 6,
at least one blocking element movable between a blocking position and a release position, and
at least one control module configured to control a moving of the blocking element between the blocking position and the release position.

### Claim 12 (depends on 11)

The passage barrier according to claim 11, wherein
the control module is configured to control a moving of the blocking element between the blocking position and the release position based on the transport usage condition associated with the detected electronic medium identifier.

### Claim 13 (depends on 12)

The passage barrier according to claim 12, wherein
the control module is configured to hold the blocking element in the release position for a release time duration,
where the length of the release time duration is based on the transport usage condition linked with the detected electronic medium identifier.

### Claim 14 (depends on 12)

The passage barrier according to claim 12, wherein
the passage barrier comprises at least one sensor configured to detect a passage through the passage barrier in the release position of the barrier element,
wherein the transport usage condition specifies as the scope of validity of a single electronic medium identifier detected by the interface device a specific number nN of users, and
the control module is configured to move the blocking element from the release position to the blocking position upon detection of a number nP of passages corresponding to the specified number nN of users.

### Claim 15 (depends on 14)

The passage barrier according to claim 14, wherein
the passage barrier comprises at least one timer that can be started after each detected passage, and
the control module is configured to move the blocking element from the release position to the blocking position upon an expiration of the timer.

### Claim 16 (depends on 1)

A passenger transport system having at least one backend system according to claim 1, the passenger transport system comprising:
at least one interface device,
wherein the interface device is configured to detect an electronic medium identifier of a ticket medium and/or a user identifier for identifying a stored user data set,
wherein the interface device is configured to detect a transport usage condition determined by means of a user interface of the interface device,
wherein the interface device is configured to generate a change data set containing at least the detected electronic medium identifier and/or user identifier, the determined transport usage condition, and at least one first time date,
wherein the interface device is configured to transmit the generated change data set to the backend system.

### Claim 17

A method for operating a passenger transport system having a backend system, comprising:
storing at least one user data set containing at least one electronic medium identifier authorizing the execution of a transport trip and at least one first transport usage condition linked to the electronic medium identifier,
receiving a change data set generated by an interface device of the passenger transport system, the change data set containing at least one second transport usage condition, at least one first time date, and at least one user identifier for identifying a stored user data set; and
changing the linkage between the electronic medium identifier stored in the identified user data set and the first transport usage condition for at least one future transport trip based on the received second transport usage condition,
reconstructing a performed transport trip based at least on a check-in data set received from a validator device of the passenger transport system, the check-in data set containing at least the electronic medium identifier, and on a provided check-out data set containing at least the same electronic medium identifier, and
generating a billing data set based at least on the reconstructed transport trip and a transport usage condition of the user data set linked with the electronic medium identifier.
