UC:IS:ExchangeOfLogicalTrainPositions

From railML 3 Wiki
Revision as of 16:54, 7 May 2021 by RailML Coord Documentation (talk | contribs) (Created page with "{{UseCase|IS|<version>|title=Exchange of Logical Train Positions|reporter=Siemens Mobility|IL=1|RS=1|TT=1}} {{UC title}} {{head|Exchange of Logical Train Positions}} {{UC desc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Exchange of Logical Train Positions
Subschema: Infrastructure
 
Related subschemas: IL TT RS 
Reported by: Siemens Mobility
Stift.png (version(s) <version>)
For general information on use cases see UC:Use cases


Use case / Anwendungsfall

Exchange of Logical Train Positions
 

Description / Beschreibung

Current train positions should be exchanged between a TMS and other systems. Current position means: the position of trains on the rail network are transmitted as soon as they are running. Ideally, other systems should be informed almost in real-time where the trains are at the moment. This information should be provided each time a train moves from one infrastructure element (e.g. track section, route, station, train number field, timetable element) to the next. For example, one use case is a TMS that provides the current (dispatching) timetable and train positions to a customer information system (CIS). The customer information system needs the current train positions to provide output (e.g. announcing an arriving train on a platform) at the correct time.

Data Flows and Interfaces / Datenflüsse und Schnittstellen

A TMS typically uses a separate topology layer for the logical train positions, consisting of something like 'train number fields'. In our TMS, a train number field is always placed between two consecutive main signals. When a train location is reported for a train number field, it means that the train is currently on that route (within the two delimiting main signals). When the train passes the signal at the end of the train number field, the train location is stepped to the next train number field. In addition to the exchange of train locations, it should also be possible to exchange the information when a route is set for a train (path reservation). This is also done based on train number fields, i.e. a train location or a path reservation can be reported for a train number field. When a train number field is no longer occupied by a train (train location or path reservation), the train number field is reported as cleared again. Normally there is one train number field between consecutive signals in the same direction, but there may be more than one train number field (e.g. at platforms for joining or splitting trains). Train number fields are used in both directions if there are signals in both directions (bidirectional traffic).

Interference with other railML® schemas / Interferenz mit anderen railML®-Schemen

Characterizing Data / Charakterisierung der Daten

How often do the data change (update)?

Real-time (seconds)

How big are the data fragments to be exchanged (complexity)?

Very small (element)

Which views are represented by the data (focus)?

Signaling

Which specific data do you expect to receive/send (elements)?