Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 3 railML 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 3railML 3
  • Issues
  • #386
Closed
Open
Issue created Jul 06, 2020 by IS Coordination@coordination.ISMaintainer

Radio Block Center

Description

railML 3.1 data model is missing the Radio Block Center (RBC). Since ETCS related applications require information about the RBC, it shall be modelled in railML 3.2.

Background

The railML ETCS use case working group discussed the functional model for a Radio Block Center.

The RBC shall contain information about:

  • several ETCS variables, e.g. NID_C, NID_RBC, NID_RADIO, NID_MN
  • link to ETCS version
  • reference to limiting RBC borders

The RBC border shall contain information about:

  • reference to the RBC which the RBC border belongs to
  • location and application direction
  • kind of transition

Links

  • Forum discussion
  • Karl-Friedemann Jerosch, 13.05.2020: [https://www.railml.org/forum/index.php?t=msg&th=727&start=0&]
  • Trac tickets
  • Wiki documentation

Proposed solution in railML 3.2

Implementation in IL:

Implementation in IS:

Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany