User:RailML Coord Documentation/IS:baliseGroup: Difference between revisions

From railML 3 Wiki
Jump to navigation Jump to search
(Created page with "==== Introduction ==== Automatic train protection systems (ATP systems) consist of an onboard system part and a trackside system part. The communication between trackside and...")
 
m (RailML Orga Admin Wiki3 moved page User:Documentation/IS:baliseGroup to User:RailML Coord Documentation/IS:baliseGroup: Automatically moved page while renaming the user "Documentation" to "RailML Coord Documentation")
 
(22 intermediate revisions by one other user not shown)
Line 1: Line 1:
==== Introduction ====
==== Introduction ====


Automatic train protection systems (ATP systems) consist of an onboard system part and a trackside system part. The communication between trackside and onboard equipment is realized in various different technical solutions using different media like cables (for example ATP system “LZB” in Germany), inductive systems (for example ATP system “PZB” in Germany), balises (like ATP system “EBICAB” in Norway) or others.
Automatic train protection systems (ATP systems) consist of an onboard system part and a trackside system part. The communication between trackside and onboard equipment is realized in various different technical solutions using different media like cables (for example ATP system ''LZB'' in Germany), inductive systems (for example ATP system ''PZB'' in Germany), balises (like ATP system ''EBICAB'' in Norway) or others.


To provide information particular about balise based ATP systems, the railML element “baliseGroup” shall be used. However for ATP systems using other media (cable, inductive, mechanical, ….), the optional railML element “trainProtectionElement” and their child elements shall be used.
To provide information particular about '''balise based''' ATP systems, the {{rml}} element {{tag|is|baliseGroup}} shall be used. However for ATP systems using other media (cable, inductive, mechanical, ….), the optional {{rml}} element {{tag|is|trainProtectionElement}} and their child elements shall be used.


===== General attributes suitable for a balise group =====
===== General attributes suitable for a balise group =====


The railML element “railML/infrastructure/functionalInfrastructure/baliseGroups/baliseGroup“ can be used for every kind of a balise group.
The {{rml}} element ''railML/infrastructure/functionalInfrastructure/baliseGroups/baliseGroup'' can be used for every kind of a balise group.


This means concerning the hardware aspect, that the railML element baliseGroup can be used to describe a '''K'''VB balise group, an '''E'''bicab balise group or and '''R'''SDD balise group (usually known as KER balise systems), and of course also for a Eurobalise group with their software applications like GNT, ZBS, specific packet 44 applications (e.g. like TBL1+) or – most common – for ETCS.
This means concerning the hardware aspect, that the {{rml}} element {{tag|is|baliseGroup}} can be used to describe a '''K'''VB balise group, an '''E'''bicab balise group or and '''R'''SDD balise group (usually known as KER balise systems), and of course also for a Eurobalise group with their software applications like GNT, ZBS, specific packet 44 applications (e.g. like TBL1+) or – most common – for ETCS.


For all these various balise based ATP systems the general information below can be described with railML:
For all these various balise based ATP systems the general information below can be described with {{rml}}:
* the Location of the balise group (which is the location of the first balise of the balise group)<br>→see child {{tag|RTM|spotLocation}}
* the number of balises belonging to the considered balise group<br>→see {{@|numberOfBalisesInGroup}}
* the orientation of the balise group in relation to the netElement<br>→see {{@|mileageDirection}}
* information, if the balise group is covered (virtually or physically as e.g. by a metal plate which suppressed the transmission of information from the balise group)<br>→see {{@|coverage}}
* information of the balise group application, which can be a specific packet 44 application or ETCS or others<br>→see sub-element {{tag|is|applicationType}}<br>In case of {{tag|IS|applicationType|@=value}}=&quot;ETCS&quot;, the optional sub-element {{tag|is|isEurobaliseGroup}} shall be used to specify the information required for ETCS.


* the Location of the balise group (which is the location of the first balise of the balise group)
see spotLocation
* the number of balises belonging to the considered balise group
see numberOfBalisesInGroup
* the orientation of the balise group in relation to the netElement
* see mileageDirection
* information, if the balise group is covered (virtually or physically as e.g. by a metal plate which suppressed the transmission of information from the balise group)
* see coverage
* information of the balise group application, which can be a specific packet 44 application or ETCS or others
* see sub-element applicationType
<blockquote>In case of applicationType value=&quot;ETCS&quot;, then the optional sub-element isEurobaliseGroup shall be used to specify the information required for ETCS
</blockquote>
===== Information of the balise group function =====
===== Information of the balise group function =====


To equip a railway line with a balise based ATP system, often the balise group locations and their functions are determined during the design phase.
To equip a railway line with a balise based ATP system, often the balise group locations and their functions are determined during the design phase.


The railML element baliseGroup can describe balise group functions as below:
The {{rml}} element {{tag|is|baliseGroup}} can describe balise group functions as below:
 
* a relation to other elements located lateral at the track<br>→see child {{tag|is|connectedWithInfrastructureElement}}
* a relation to other elements located lateral at the track
* the functional type depending on the balise group orientation (nominal or reverse)<br>→see child {{tag|is|functionalType}}
 
* the name(s) of the balise based ATP system application(s)<br>→see child {{tag|is|applicationType}}
see connectedWithInfrastructureElement
 
* the functional type depending on the balise group orientation (nominal or reverse)
 
see functionalType
 
* the name(s) of the balise based ATP system application(s):
 
see applicationType


The ''balise group functions'', the track topology information and the infrastructure manager specific ATP operational rules are the basis to determine the ATP trackside equipment and if necessary also the software of the ATP elements (like for ETCS).
The ''balise group functions'', the track topology information and the infrastructure manager specific ATP operational rules are the basis to determine the ATP trackside equipment and if necessary also the software of the ATP elements (like for ETCS).


According to the use case “ETCS Track Net”, the railML element “baliseGroup” provides the attributes and elements to transfer the information of the design phase from an infrastructure manager to a signaling supplier via railML.
According to the use case ''[[UC:IS:ETCS track net|ETCS Track Net]]'', the {{rml}} element {{tag|is|baliseGroup}} provides the attributes and elements to transfer the information of the design phase from an infrastructure manager to a signaling supplier via {{rml}}.


===== Specific Information for an Eurobalise group for ETCS =====
===== Specific Information for an Eurobalise group for ETCS =====


In case if a balise group is an Eurobalise group, then the railML child element “isEurobaliseGroup” can be used to provide ETCS specific balise group information.
In case if a balise group is an Eurobalise group, then the {{rml}} child element {{tag|is|isEurobaliseGroup}} can be used to provide ETCS specific balise group information.


This is applicable for all ATP systems using a hardware device fulfilling UNISIG-SUBSET-036 (Specification of Eurobalise) together with an SRS ETCS based telegram language as for GNT, ZBS, ETCS or national ATP applications using ETCS-Packet 44.
This is applicable for all ATP systems using a hardware device fulfilling UNISIG-SUBSET-036 (Specification of Eurobalise) together with an SRS ETCS based telegram language as for GNT, ZBS, ETCS or national ATP applications using ETCS-Packet 44.


Relation between railML attributes and the corresponding UNISIG variables for ETCS:
;Relation between {{rml}} attributes and the corresponding UNISIG variables for ETCS:
 
In case of a Eurobalise group, the optional sub-element “isEurobaliseGroup“ shall be used to specify the ETCS related information:


<ul>
In case of a Eurobalise group, the optional sub-element {{tag|is|isEurobaliseGroup}} shall be used to specify the ETCS related information:
<li><blockquote><p>the value of UNISIG variable M_VERSION valid for all balises belonging to the considered balise group (provided in railML by attribute mVersion), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.79</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable NID_C (provided in railML by attribute countryID), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.86</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable NID_BG (provided in railML by attribute groupID), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.85</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable N_TOTAL (provided in railML by attribute numberOfBalisesInGroup; N_TOTAL = [value of numberOfBalisesInGroup]-1), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.82</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable Q_LINK (provided in railML by attribute isLinked), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.114</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable Q_LOCACC (provided in railML by attribute locationAccuracy), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.115</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable Q_LINKREACTION (provided in railML for train movements passing the balise group in nominal direction by attribute linkReactionNominal; provided in railML for train movements passing the balise group in reverse direction by attribute linkReactionReverse), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.117</p></blockquote></li></ul>


Remarks:
*the value of UNISIG variable M_VERSION valid for all balises belonging to the considered balise group (provided in {{rml}} by attribute {{@|mVersion|IS:isEurobaliseGroup}}), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.79
*the value of UNISIG variable NID_C (provided in {{rml}} by attribute {{@|countryID|IS:isEurobaliseGroup}}), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.86
*the value of UNISIG variable NID_BG (provided in {{rml}} by attribute {{@|groupID|IS:isEurobaliseGroup}}), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.85
*the value of UNISIG variable N_TOTAL (provided in {{rml}} by attribute {{@|numberOfBalisesInGroup|IS:baliseGroup}}; N_TOTAL = [value of numberOfBalisesInGroup]-1), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.82
*the value of UNISIG variable Q_LINK (provided in {{rml}} by attribute {{@|isLinked|IS:isEurobaliseGroup}}), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.114
*the value of UNISIG variable Q_LOCACC (provided in {{rml}} by attribute {{@|locationAccuracy|IS:isEurobaliseGroup}}), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.115
*the value of UNISIG variable Q_LINKREACTION (provided in {{rml}} for train movements passing the balise group in nominal direction by attribute {{@|linkReactionNominal|IS:isEurobaliseGroup}}; provided in {{rml}} for train movements passing the balise group in reverse direction by attribute {{@|linkReactionReverse|IS:isEurobaliseGroup}}), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.117


<ul>
;Remarks:
<li><blockquote><p>If a balise group shall be covered during a construction phase, then it is possible to specify if the coverage is executed physically by a metal plate (coverage=&quot;physical&quot;) or if the coverage is managed virtually using ETCS packet 0 (coverage=&quot;virtual&quot;). The optional railML element &lt;isValid from=&quot;&quot; to=&quot;&quot;/&gt; can be used to specify the period during which the balise group is to be covered.</p></blockquote></li>
*If a balise group shall be covered during a construction phase, then it is possible to specify if the coverage is executed physically by a metal plate (''{{@|coverage|IS:baliseGroup}}=&quot;physical&quot;'') or if the coverage is managed virtually using ETCS packet 0 ({{@|coverage|IS:baliseGroup}}=&quot;virtual&quot;''). The optional {{rml}} element '''&lt;[[RTM:isValid|isValid]] from=&quot;&quot; to=&quot;&quot;/&gt; can be used to specify the period during which the balise group is to be covered.
<li><blockquote><p>The values of the following UNISIG variables of the ETCS balise telegram header are implicitly provided if a railML element baliseGroup is used:</p></blockquote>
*The values of the following UNISIG variables of the ETCS balise telegram header are implicitly provided if a {{rml}} element baliseGroup is used:</p></blockquote>
<ul>
**Q_UPDOWN=1 (means: “Up-link telegram: track to train)
<li><p>Q_UPDOWN=1 (means: “Up-link telegram: track to train)</p></li>
**Q_MEDIA=0 (means: “Balise”)
<li><p>Q_MEDIA=0 (means: “Balise”)</p></li></ul>
*The values of the following UNISIG variables of the ETCS balise telegram header can be provided by the {{rml}} element balise (see section 2), if necessary:</p></blockquote>
</li>
**M_DUP
<li><blockquote><p>The values of the following UNISIG variables of the ETCS balise telegram header can be provided by the railML element balise (see section 2), if necessary:</p></blockquote>
**N_PIG
<ul>
**In case of ATP systems “GNT” and “ZBS”, {{@|mVersion|IS:isEurobaliseGroup}}=&quot;0&quot; shall be used. Further optional {{rml}} attributes describing UNISIG variables can be used if appropriate.
<li><p>M_DUP</p></li>
<nowiki />
<li><p>N_PIG</p></li></ul>
==== Examples ====
</li>
<li><p>In case of ATP systems “GNT” and “ZBS”, mVersion=&quot;0&quot; shall be used. Further optional railML attributes describing UNISIG variables can be used if appropriate.</p></li></ul>
 
==== Best Practice / Examples ====


===== Example 1 – Balise group with SMB (ETCS Level 2) =====
===== Example 1 – Balise group with SMB (ETCS Level 2) =====
<div class="res-img">
[[file:image1.pdf]]
</div>''Example 1 – Balise group with SMB (ETCS Level 2)''


Figure 1: Example 1 – Balise group with SMB (ETCS Level 2)
;Explanation:
 
Explanation:
 
A balise group is assigned to a stop marker board (SMB) 321 (ID inside the railML: ref=&quot;sig_SMB_321&quot;). The balise group is oriented in direction of increasing mileage (mileageDirection=&quot;nominal&quot;) and in consequence the internal numbering of the balises in the balise group is aligned with the increasing mileage.
 
The balise group has only a logical connection (type=&quot;logical&quot;) with the real signal / SMB on the trackside. The balises in this balise group are not covered virtually (coverage=&quot;none&quot;).<br />
The balise group consists of two balises (numberOfBalisesInGroup=&quot;2&quot;) used for ETCS (applicationType value=&quot;ETCS&quot;), which are allocated in Germany (countryID=&quot;127&quot; means Germany). It is the balise group No. 777 in Germany (groupID=&quot;777&quot;).
 
The balise group is announced by a linking information (isLinked=&quot;true&quot;) transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will trigger a trip procedure immediately (linkReactionNominal=&quot;trainTrip&quot;). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (linkReactionReverse=&quot;noReaction&quot;).
 
The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (locationAccuracy=&quot;5&quot;). UNISIG-baseline 3 is in use (mVersion=&quot;32&quot;).


Corresponding railML description:
A balise group is assigned to a stop marker board (SMB) 321 (ID inside the {{rml}}: {{@|ref|IS:connectedWithInfrastructureElement}}=&quot;sig_SMB_321&quot;). The balise group is oriented in direction of increasing mileage ({{@|mileageDirection|IS:baliseGroup}}=&quot;nominal&quot;) and in consequence the internal numbering of the balises in the balise group is aligned with the increasing mileage.


&lt;baliseGroups&gt;
The balise group has only a logical connection ({{@|type|IS:connectedWithInfrastructureElement}}=&quot;logical&quot;) with the real signal / SMB on the trackside. The balises in this balise group are not covered virtually ({{@|coverage|IS:baliseGroup}}=&quot;none&quot;).<br />
&lt;baliseGroup id=&quot;bg1&quot; mileageDirection=&quot;nominal&quot; coverage=&quot;none&quot;
The balise group consists of two balises ({{@|numberOfBalisesInGroup|IS:baliseGroup}}=&quot;2&quot;) used for ETCS ([[IS:applicationType|applicationType]] {{attr|value|IS:applicationType}}=&quot;ETCS&quot;), which are allocated in Germany ({{@|countryID|IS:isEurobaliseGroup}}=&quot;127&quot; means Germany). It is the balise group No. 777 in Germany ({{@|groupID|IS:isEurobaliseGroup}}=&quot;777&quot;).


numberOfBalisesInGroup=&quot;2&quot;&gt;
The balise group is announced by a linking information ({{@|isLinked|IS:isEurobaliseGroup}}=&quot;true&quot;) transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will trigger a trip procedure immediately ({{@|linkReactionNominal|IS:isEurobaliseGroup}}=&quot;trainTrip&quot;). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem ({{@|linkReactionReverse|IS:isEurobaliseGroup}}=&quot;noReaction&quot;).
&lt;name name=&quot;127-00777&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg1_sloc01&quot; netElementRef=&quot;ne_101&quot;


applicationDirection=&quot;both&quot; pos=&quot;45.0&quot;&gt;
The additional tolerance value on the regular accuracy towards the measured location is +/- 5m ({{@|locationAccuracy|IS:isEurobaliseGroup}}=&quot;5&quot;). UNISIG-baseline 3 is in use ({{@|mVersion|IS:isEurobaliseGroup}}=&quot;32&quot;).
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;100045.0&quot; /&gt;
&lt;/spotLocation&gt;
&lt;applicationType value=&quot;ETCS&quot; /&gt;
&lt;connectedWithInfrastructureElement ref=&quot;sig_SMB_321&quot; type=&quot;logical&quot; /&gt;
&lt;functionalType value=&quot;signal&quot; mileageDirection=&quot;nominal&quot; /&gt;
&lt;isEurobaliseGroup countryID=&quot;127&quot; groupID=&quot;777&quot; isLinked=&quot;true&quot;


linkReactionNominal=&quot;trainTrip&quot; linkReactionReverse=&quot;noReaction&quot;
;Corresponding {{rml}} description:
 
<syntaxhighlight lang=xml>
locationAccuracy=&quot;5&quot; mVersion=&quot;32&quot; /&gt;
<baliseGroups>
&lt;/baliseGroup&gt;
  <baliseGroup id="bg1" mileageDirection="nominal" coverage="none"
&lt;baliseGroups/&gt;
numberOfBalisesInGroup="2">
    <name name="127-00777" description="etcsName" language="EN"/>
    <spotLocation id="bg1_sloc01" netElementRef="ne_101"
applicationDirection="both" pos="45.0">
      <linearCoordinate positioningSystemRef="lps01" measure="100045.0" />
    </spotLocation>
    <applicationType value="ETCS" />
    <connectedWithInfrastructureElement ref="sig_SMB_321" type="logical" />
    <functionalType value="signal" mileageDirection="nominal" />
    <isEurobaliseGroup countryID="127" groupID="777" isLinked="true"
linkReactionNominal="trainTrip" linkReactionReverse="noReaction"
locationAccuracy="5" mVersion="32" />
  </baliseGroup>
</baliseGroups>
</syntaxhighlight>


===== Example 2 – Balise group with main signal (ETCS Level 1) =====
===== Example 2 – Balise group with main signal (ETCS Level 1) =====
<div class="res-img">
[[file:image2.pdf]]
</div>''Example 2 – Balise group with main signal (ETCS Level 1)''


Figure 2: Example 2 – Balise group with main signal (ETCS Level 1)
;Explanation:


Explanation:
A balise group is assigned to a signal “Signal A” (ID inside the {{rml}} file: {{@|ref|IS:connectedWithInfrastructureElement}}=&quot;sig_A&quot;), which is oriented in direction of decreasing mileage. The balise group is oriented in direction of decreasing mileage ({{@|mileageDirection|IS:baliseGroup}}=&quot;reverse&quot;) and in consequence the internal numbering of the balises in the balise group is aligned with the decreasing mileage.


A balise group is assigned to a signal “Signal A” (ID inside the railML: ref=&quot;sig_A&quot;), which is oriented in direction of decreasing mileage. The balise group is oriented in direction of decreasing mileage (mileageDirection=&quot;reverse&quot;) and in consequence the internal numbering of the balises in the balise group is aligned with the decreasing mileage.
The balise group has a physical connection ({{@|type|IS:connectedWithInfrastructureElement}}=&quot;physical&quot;) with the real signal on the trackside. The balises in this balise group are not covered virtually ({{@|coverage|IS:baliseGroup}}=&quot;none&quot;).<br />
The balise group consists of two balises ({{@|numberOfBalisesInGroup|IS:baliseGroup}}=&quot;2&quot;) used for ETCS (<[[IS:applicationType#value|applicationType value]]=&quot;ETCS&quot;), which are allocated in Germany ({{@|countryID|IS:isEurobaliseGroup}}=&quot;127&quot; means Germany). It is the balise group No. 787 in Germany ({{@|groupID|IS:isEurobaliseGroup}}=&quot;787&quot;).


The balise group has a physical connection (type=&quot;physical&quot;) with the real signal on the trackside. The balises in this balise group are not covered virtually (coverage=&quot;none&quot;).<br />
The balise group is announced by a linking information ({{@|isLinked|IS:isEurobaliseGroup}}=&quot;true&quot;) transmitted to the train. If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will trigger a trip procedure immediately ({{@|linkReactionNominal|IS:isEurobaliseGroup}}=&quot;trainTrip&quot;). If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem ({{@|linkReactionReverse|IS:isEurobaliseGroup}}=&quot;noReaction&quot;).
The balise group consists of two balises (numberOfBalisesInGroup=&quot;2&quot;) used for ETCS (applicationType value=&quot;ETCS&quot;), which are allocated in Germany (countryID=&quot;127&quot; means Germany). It is the balise group No. 787 in Germany (groupID=&quot;787&quot;).


The balise group is announced by a linking information (isLinked=&quot;true&quot;) transmitted to the train. If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will trigger a trip procedure immediately (linkReactionNominal=&quot;trainTrip&quot;). If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (linkReactionReverse=&quot;noReaction&quot;).
The additional tolerance value on the regular accuracy towards the measured location is +/- 5m ({{@|locationAccuracy|IS:isEurobaliseGroup}}=&quot;5&quot;). UNISIG-baseline 2 is in use ({{@|mVersion|IS:isEurobaliseGroup}}=&quot;16&quot;).


The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (locationAccuracy=&quot;5&quot;). UNISIG-baseline 2 is in use (mVersion=&quot;16&quot;).
;Corresponding {{rml}} description:
 
<syntaxhighlight lang=xml>
Corresponding railML description:
<baliseGroups>
 
  <baliseGroup id="bg2" mileageDirection="reverse" coverage="none"
&lt;baliseGroups&gt;
numberOfBalisesInGroup="2">
&lt;baliseGroup id=&quot;bg2&quot; mileageDirection=&quot;reverse&quot; coverage=&quot;none&quot;
    <name name="127-00787" description="etcsName" language="EN"/>
 
    <spotLocation id="bg2_sloc01" netElementRef="ne_102"
<blockquote>numberOfBalisesInGroup=&quot;2&quot;&gt;
applicationDirection="both" pos="985.0">
</blockquote>
      <linearCoordinate positioningSystemRef="lps01" measure="101985.0"/>
&lt;name name=&quot;127-00787&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
    </spotLocation>
&lt;spotLocation id=&quot;bg2_sloc01&quot; netElementRef=&quot;ne_102&quot;
    <applicationType value="ETCS"/>
 
    <connectedWithInfrastructureElement ref="sig_A" type="physical"/>
<blockquote>applicationDirection=&quot;both&quot; pos=&quot;985.0&quot;&gt;
    <functionalType value="signal" mileageDirection="reverse"/>
</blockquote>
    <isEurobaliseGroup countryID="127" groupID="787" isLinked="true"
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;101985.0&quot;/&gt;
linkReactionNominal="trainTrip" linkReactionReverse="noReaction"
&lt;/spotLocation&gt;
locationAccuracy="5" mVersion="16"/>
&lt;applicationType value=&quot;ETCS&quot;/&gt;
  </baliseGroup>
&lt;connectedWithInfrastructureElement ref=&quot;sig_A&quot; type=&quot;physical&quot;/&gt;
<baliseGroups/>
&lt;functionalType value=&quot;signal&quot; mileageDirection=&quot;reverse&quot;/&gt;
</syntaxhighlight>
&lt;isEurobaliseGroup countryID=&quot;127&quot; groupID=&quot;787&quot; isLinked=&quot;true&quot;
 
<blockquote>linkReactionNominal=&quot;trainTrip&quot; linkReactionReverse=&quot;noReaction&quot;
 
locationAccuracy=&quot;5&quot; mVersion=&quot;16&quot;/&gt;
</blockquote>
&lt;/baliseGroup&gt;<br />
&lt;baliseGroups/&gt;


===== Example 3 – Balise group for a stop-if-in-shunting panel (ETCS Level 1 and/or 2) =====
===== Example 3 – Balise group for a stop-if-in-shunting panel (ETCS Level 1 and/or 2) =====
<div class="res-img">
[[file:image3.pdf]]
</div>''Example 3 – Balise group for a stop-if-in-shunting panel (ETCS Level 1 and/or 2)''


Figure 3: Example 3 – Balise group for a stop-if-in-shunting panel (ETCS Level 1 and/or 2)
;Explanation:
 
Explanation:
 
A balise group is assigned to a stop-if-in-shunting panel (ID inside the railML: ref=&quot;panel_StopSH&quot;). The balise group is oriented in direction of increasing mileage (mileageDirection=&quot;nominal&quot;) and in consequence the internal numbering of the balises in the balise group is aligned with the increasing mileage.
 
The balise group has only a logical connection (type=&quot;logical&quot;) with the real stop-if-in-shunting panel on the trackside. The balises in this balise group are not covered virtually (coverage=&quot;none&quot;).<br />
The balise group consists of two balises (numberOfBalisesInGroup=&quot;2&quot;) used for ETCS (applicationType value=&quot;ETCS&quot;), which are allocated in Germany (countryID=&quot;127&quot; means Germany). It is the balise group No. 747 in Germany (groupID=&quot;747&quot;).
 
The balise group is announced by a linking information (isLinked=&quot;true&quot;) transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (linkReactionNominal=&quot;noReaction&quot;). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (linkReactionReverse=&quot;noReaction&quot;), too.
 
The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (locationAccuracy=&quot;5&quot;). UNISIG-baseline 2 is in use (mVersion=&quot;16&quot;).


Corresponding railML description:
A balise group is assigned to a stop-if-in-shunting panel (ID inside the {{rml}} file: {{@|ref|IS:connectedWithInfrastructureElement}}=&quot;panel_StopSH&quot;). The balise group is oriented in direction of increasing mileage ({{@|mileageDirection|IS:baliseGroup}}=&quot;nominal&quot;) and in consequence the internal numbering of the balises in the balise group is aligned with the increasing mileage.


&lt;baliseGroups&gt;
The balise group has only a logical connection ({{@|type|IS:connectedWithInfrastructureElement}}=&quot;logical&quot;) with the real stop-if-in-shunting panel on the trackside. The balises in this balise group are not covered virtually ({{@|coverage|IS:baliseGroup}}=&quot;none&quot;).<br />
&lt;baliseGroup id=&quot;bg3&quot; mileageDirection=&quot;nominal&quot; coverage=&quot;none&quot;
The balise group consists of two balises ({{@|numberOfBalisesInGroup|IS:baliseGroup}}=&quot;2&quot;) used for ETCS ([[IS:applicationType#value|applicationType value]]=&quot;ETCS&quot;), which are allocated in Germany ({{@|countryID|IS:isEurobaliseGroup}}=&quot;127&quot; means Germany). It is the balise group No. 747 in Germany ({{@|groupID|IS:isEurobaliseGroup}}=&quot;747&quot;).


<blockquote>numberOfBalisesInGroup=&quot;2&quot;&gt;
The balise group is announced by a linking information ({{@|isLinked|IS:isEurobaliseGroup}}=&quot;true&quot;) transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem ({{@|linkReactionNominal|IS:isEurobaliseGroup}}=&quot;noReaction&quot;). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@|linkReactionReverse|IS:isEurobaliseGroup}}=&quot;noReaction&quot;), too.
</blockquote>
&lt;name name=&quot;127-00747&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg3_sloc01&quot; netElementRef=&quot;ne_103&quot;


<blockquote>applicationDirection=&quot;both&quot; pos=&quot;500.0&quot;&gt;
The additional tolerance value on the regular accuracy towards the measured location is +/- 5m ({{@|locationAccuracy|IS:isEurobaliseGroup}}=&quot;5&quot;). UNISIG-baseline 2 is in use ({{@|mVersion|IS:baliseGroup}}=&quot;16&quot;).
</blockquote>
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;102500.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;applicationType value=&quot;ETCS&quot;/&gt;
&lt;connectedWithInfrastructureElement ref=&quot;panel_StopSH&quot; type=&quot;logical&quot;/&gt;
&lt;functionalType value=&quot;stopIfInShunting&quot; mileageDirection=&quot;nominal&quot;/&gt;
&lt;isEurobaliseGroup countryID=&quot;127&quot; groupID=&quot;747&quot; isLinked=&quot;true&quot;


linkReactionNominal=&quot;noReaction&quot; linkReactionReverse=&quot;noReaction&quot;
;Corresponding {{rml}} description:
 
<syntaxhighlight lang=xml>
locationAccuracy=&quot;5&quot; mVersion=&quot;16&quot;/&gt;
<baliseGroups>
&lt;/baliseGroup&gt;<br />
  <baliseGroup id="bg3" mileageDirection="nominal" coverage="none"
&lt;baliseGroups/&gt;
numberOfBalisesInGroup="2">
    <name name="127-00747" description="etcsName" language="EN"/>
    <spotLocation id="bg3_sloc01" netElementRef="ne_103"
applicationDirection="both" pos="500.0">
        <linearCoordinate positioningSystemRef="lps01" measure="102500.0"/>
    </spotLocation>
    <applicationType value="ETCS"/>
    <connectedWithInfrastructureElement ref="panel_StopSH" type="logical"/>
    <functionalType value="stopIfInShunting" mileageDirection="nominal"/>
    <isEurobaliseGroup countryID="127" groupID="747" isLinked="true"
linkReactionNominal="noReaction" linkReactionReverse="noReaction"
locationAccuracy="5" mVersion="16"/>
  </baliseGroup>
<baliseGroups/>
</syntaxhighlight>


===== Example 4 – Balise group for odometry purposes (ETCS Level 1 and/or 2) =====
===== Example 4 – Balise group for odometry purposes (ETCS Level 1 and/or 2) =====
<div class="res-img">
[[file:image4.pdf]]
</div>''Example 4 – Balise group for odometry purposes (ETCS Level 1 and/or 2)''


Figure 4: Example 4 – Balise group for odometry purposes (ETCS Level 1 and/or 2)
;Explanation:
 
Explanation:
 
This example shows a balise group for the odometry correction along a track. The internal orientation of the balise group is in direction of increasing mileage (mileageDirection=&quot;nominal&quot;).
 
The balise group consists of one balise (numberOfBalisesInGroup=&quot;1&quot;) used for ETCS (applicationType value=&quot;ETCS&quot;), which is allocated in Germany (countryID=&quot;127&quot; means Germany). It is the balise group No. 727 in Germany (groupID=&quot;727&quot;). The balise in this balise group is not covered virtually (coverage=&quot;none&quot;).
 
The balise group is announced by a linking information (isLinked=&quot;true&quot;) transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (linkReactionNominal=&quot;noReaction&quot;). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (linkReactionReverse=&quot;noReaction&quot;), too. The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (locationAccuracy=&quot;5&quot;). UNISIG-baseline 2 is in use (mVersion=&quot;16&quot;).
 
Corresponding railML description:


&lt;baliseGroups&gt;
This example shows a balise group for the odometry correction along a track. The internal orientation of the balise group is in direction of increasing mileage ({{@|mileageDirection|IS:baliseGroup}}=&quot;nominal&quot;).
&lt;baliseGroup id=&quot;bg4&quot; mileageDirection=&quot;nominal&quot; coverage=&quot;none&quot;


numberOfBalisesInGroup=&quot;1&quot;&gt;
The balise group consists of one balise ({{@|numberOfBalisesInGroup|IS:baliseGroup}}=&quot;1&quot;) used for ETCS (<[[IS:applicationType#value|applicationType value]]=&quot;ETCS&quot;), which is allocated in Germany ({{@|countryID|IS:isEurobaliseGroup}}=&quot;127&quot; means Germany). It is the balise group No. 727 in Germany ({{@|groupID|IS:isEurobaliseGroup}}=&quot;727&quot;). The balise in this balise group is not covered virtually ({{@|coverage|IS:baliseGroup}}=&quot;none&quot;).
&lt;name name=&quot;127-00727&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg4_sloc01&quot; netElementRef=&quot;ne_104&quot;


<blockquote>applicationDirection=&quot;both&quot; pos=&quot;210.0&quot;&gt;
The balise group is announced by a linking information ({{@|isLinked|IS:isEurobaliseGroup}}=&quot;true&quot;) transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem ({{@|linkReactionNominal|IS:isEurobaliseGroup}}=&quot;noReaction&quot;). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem ({{@|linkReactionReverse|IS:isEurobaliseGroup}}=&quot;noReaction&quot;), too. The additional tolerance value on the regular accuracy towards the measured location is +/- 5m ({{@|locationAccuracy|IS:isEurobaliseGroup}}=&quot;5&quot;). UNISIG-baseline 2 is in use ({{@|mVersion|IS:isEurobaliseGroup}}=&quot;16&quot;).
</blockquote>
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;103210.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;applicationType value=&quot;ETCS&quot;/&gt;
&lt;functionalType value=&quot;odometry&quot; mileageDirection=&quot;nominal&quot;/&gt;
&lt;isEurobaliseGroup countryID=&quot;127&quot; groupID=&quot;727&quot; isLinked=&quot;true&quot;


linkReactionNominal=&quot;noReaction&quot; linkReactionReverse=&quot;noReaction&quot;
;Corresponding {{rml}} description:
 
<syntaxhighlight lang=xml>
locationAccuracy=&quot;5&quot; mVersion=&quot;16&quot;/&gt;
<baliseGroups>
&lt;/baliseGroup&gt;<br />
  <baliseGroup id="bg4" mileageDirection="nominal" coverage="none"
&lt;baliseGroups/&gt;
numberOfBalisesInGroup="1">
    <name name="127-00727" description="etcsName" language="EN"/>
    <spotLocation id="bg4_sloc01" netElementRef="ne_104"
applicationDirection="both" pos="210.0">
      <linearCoordinate positioningSystemRef="lps01" measure="103210.0"/>
    </spotLocation>
    <applicationType value="ETCS"/>
    <functionalType value="odometry" mileageDirection="nominal"/>
    <isEurobaliseGroup countryID="127" groupID="727" isLinked="true"
linkReactionNominal="noReaction" linkReactionReverse="noReaction"
locationAccuracy="5" mVersion="16"/>
  </baliseGroup>
<baliseGroups/>
</syntaxhighlight>


===== Example 5 – Balise group for Temporary Speed Restrictions [TSR] (ETCS Level 1 and/or 2) =====
===== Example 5 – Balise group for Temporary Speed Restrictions [TSR] (ETCS Level 1 and/or 2) =====
<div class="res-img">
[[file:image2.pdf]]
</div>''Example 5 – Balise group to announce a Temporary Speed Restriction [TSR] (ETCS Level 1 and/or 2)''


Figure 5: Example 5 – Balise group to announce a Temporary Speed Restriction [TSR] (ETCS Level 1 and/or 2)
;Explanation:
 
Explanation:
 
This example shows a temporary balise (&lt;isValid from=&quot;2022-06-01&quot; to=&quot;2022-07-15&quot;/&gt;) group in approach of a zone with temporary speed restriction [TSR], for example due to track work. The internal orientation of the balise group is in direction of increasing mileage (mileageDirection=&quot;nominal&quot;).
 
The balise group consists of 4 balises (numberOfBalisesInGroup=&quot;4&quot;) used for ETCS (applicationType value=&quot;ETCS&quot;), which is allocated in Germany (countryID=&quot;127&quot; means Germany). It is the balise group No. 8003 in Germany (groupID=&quot;8003&quot;).
 
The balise in this balise group is not covered virtually (coverage=&quot;none&quot;). The balise group is marked as an unlinked balise group (isLinked=&quot;false&quot;) and therefore without linking properties (means, no use of the optional attributes linkReactionNominal, linkReactionReverse and locationAccuracy). UNISIG-baseline 2 is in use (mVersion=&quot;16&quot;).
 
Corresponding railML description:


&lt;baliseGroups&gt;
This example shows a temporary balise (&lt;[[RTM:isValid|isValid]] {{attr|from|RTM:isvalid}}=&quot;2022-06-01&quot; {{attr|to|RTM:isValid}}=&quot;2022-07-15&quot;/&gt;) group in approach of a zone with temporary speed restriction [TSR], for example due to track work. The internal orientation of the balise group is in direction of increasing mileage ({{@|mileageDirection|IS:baliseGroup}}=&quot;nominal&quot;).
&lt;baliseGroup id=&quot;bg5&quot; mileageDirection=&quot;nominal&quot; coverage=&quot;none&quot;


numberOfBalisesInGroup=&quot;4&quot;&gt;
The balise group consists of 4 balises ({{@|numberOfBalisesInGroup|IS:baliseGroup}}=&quot;4&quot;) used for ETCS (<[[IS:applicationType#value|applicationType value]]=&quot;ETCS&quot;), which is allocated in Germany ({{@|countryID|IS:isEurobaliseGroup}}=&quot;127&quot; means Germany). It is the balise group No. 8003 in Germany ({{@|groupID|IS:isEurobaliseGroup}}=&quot;8003&quot;).
&lt;name name=&quot;127-08003&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;isValid from=&quot;2022-06-01&quot; to=&quot;2022-07-15&quot;/&gt;
&lt;spotLocation id=&quot;bg5_sloc01&quot; netElementRef=&quot;ne_105&quot;


applicationDirection=&quot;both&quot; pos=&quot;650.0&quot;&gt;
The {{tag|IS|balise}} in this balise group is not covered virtually ({{@|coverage|IS:baliseGroup}}=&quot;none&quot;). The balise group is marked as an unlinked balise group ({{@|isLinked|IS:isEurobaliseGroup}}=&quot;false&quot;) and therefore without linking properties (means, no use of the optional attributes {{@|linkReactionNominal|IS:isEurobaliseGroup}}, {{@|linkReactionReverse|IS:isEurobaliseGroup}} and {{@|locationAccuracy|IS:isEurobaliseGroup}}). UNISIG-baseline 2 is in use ({{@|mVersion|IS:isEurobaliseGroup}}=&quot;16&quot;).
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;104650.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;applicationType value=&quot;ETCS&quot;/&gt;
&lt;functionalType value=&quot;TSR&quot; mileageDirection=&quot;nominal&quot;/&gt;
&lt;isEurobaliseGroup countryID=&quot;127&quot; groupID=&quot;8003&quot; isLinked=&quot;false&quot;


mVersion=&quot;16&quot;/&gt;
;Corresponding {{rml}} description:
&lt;/baliseGroup&gt;<br />
<syntaxhighlight lang=xml>
&lt;baliseGroups/&gt;
<baliseGroups>
  <baliseGroup id="bg5" mileageDirection="nominal" coverage="none"
numberOfBalisesInGroup="4">
    <name name="127-08003" description="etcsName" language="EN"/>
    <isValid from="2022-06-01" to="2022-07-15"/>
    <spotLocation id="bg5_sloc01" netElementRef="ne_105"
applicationDirection="both" pos="650.0">
      <linearCoordinate positioningSystemRef="lps01" measure="104650.0"/>
    </spotLocation>
    <applicationType value="ETCS"/>
    <functionalType value="TSR" mileageDirection="nominal"/>
    <isEurobaliseGroup countryID="127" groupID="8003" isLinked="false"
mVersion="16"/>
  </baliseGroup>
<baliseGroups/>
</syntaxhighlight>


==== Additional Information ====
==== Additional Information ====
===== Notes =====
''--- (no notes) ---''


===== Open Issues =====
===== Open Issues =====


If the general information provided by the railML element “baliseGroup” is not sufficient for a KER balise application, then please open a request in the railML forum reporting the missing information to be modelled in railML. RailML.org will provide a suggestion for modelling the missing information in railML, for example added by a new optional sub-element “railML/infrastructure/functionalInfrastructure/baliseGroups/baliseGroup/isEbicabBalise“ which includes the new requested information.
If the general information provided by the {{rml}} element “baliseGroup” is not sufficient for a KER balise application, then please open a request in the {{rml}} forum – {{site|https://forum.railml.org}} – reporting the missing information to be modelled in {{rml}}. {{rml}}.org will provide a suggestion for modelling the missing information in {{rml}}, for example added by a new optional sub-element ''railML/infrastructure/functionalInfrastructure/baliseGroups/baliseGroup/isEbicabBalise'' which includes the new requested information.


==== Semantic Rules applicable for railML element “baliseGroup” ====
==== Semantic Rules applicable for {{rml}} element “baliseGroup” ====
 
The following semantic rules are applicable for the use of element “baliseGroup” with raiML 3.2:
 
<blockquote>Rule 01: The element “baliseGroup” shall always use the railML option “spotLocation” to define the balise group location on the topology.
</blockquote>
Justification: According to UNISIG-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 3.4.2.2.1 and UNISIG-040 (versions 2.3.0, 3.3.0 or 3.4.0) section 3.3.1.3, a balise group (represented by the railML element “baliseGroup”) shall be considered as point-shaped element without extension. The reference location of the balise group is the location of the balise with N_PIG=0.
 
= The railML element “balise” =
 
==== Introduction ====
 
===== Relation between railML elements “baliseGroup” and “balise” =====
 
In balise based ATP systems, each “balise” belongs to a “balise group”.
 
Consequently, for balise based ATP systems, there are two levels of description: the higher level “balise group”, which is presented by the railML element “baliseGroup” and the more detailed level “balise”, presented by the railML element “balise”.
 
Usually, the definition of balise groups in the track layout is sufficient for the most purposes and it is not necessary additionally to give information about each balise of a balise group, because all relevant information for the ATP software engineering can be derived from the element “baliseGroup”. For example, all variables required for an ETCS balise telegram header according to SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 8.4.2.1, can be calculated from the information given by element “baliseGroup”.
 
Nevertheless, railML provides the possibility to specify each balise of a balise group, which can make sense in cases where the exact location of each balise in a balise group is important, for example for special test purposes or for the mounting and installation of the balises.
 
'''Conclusion:'''
 
The use of railML “balise” elements is optional.
 
But if railML “balise” elements are used, then the railML “baliseGroup” elements are mandatory. Each “balise” element must reference a “baliseGroup” element.
 
===== Concept of the railML element “balise” =====
 
Correspondent to the concept of railML element “baliseGroup”, also the railML element “balise” is suitable for all balise based ATP systems. This means, a railML element “balise” can be a '''K'''VB balise, an '''E'''bicab balise, a '''R'''SDD balise (together known as KER balises) or a Eurobalise.
 
The general information provided for all hardware types of balises is:
 
* the location of the balise (using sub-element spotLocation)
* to which balise group the balise belongs to (using attibute belongsToBaliseGroup)
* the distance to the predecessor balise within the group (using attribute distanceToPredecessorBaliseWithinGroup)
 
In case of Eurobalise, the optional sub-element “isEurobalise“ shall be used to specify the ETCS related information:
 
<ul>
<li><blockquote><p>the value of UNISIG variable N_PIG (provided in railML by attribute positionInGroup), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.81</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable M_DUP (provided in railML by attribute duplicate), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.63 and</p></blockquote></li>
<li><blockquote><p>the value of UNISIG variable M_VERSION (provided in railML by attribute mVersion), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.79</p></blockquote></li></ul>
 
==== Best Practice / Examples ====
 
===== Example 1 – Eurobalises belonging to a Eurobalise group consisting of 2 fix data balises =====
 
This example shows the balise elements belonging to the ETCS balise group presented in section 1.2.1 of railML element “baliseGroup”.
 
Figure 6: Example 1 – Balise group of 2 fix data balises
 
Corresponding railML description:
 
&lt;balises&gt;
&lt;balise id=&quot;bg1_bal0&quot; type=&quot;fixed&quot; belongsToBaliseGroup=&quot;bg1&quot;
 
distanceToPredecessorBaliseWithinGroup=&quot;0.0&quot;&gt;
&lt;name name=&quot;127-00777-0&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg1_bal0_sloc01&quot; netElementRef=&quot;ne_101&quot;
 
applicationDirection=&quot;both&quot; pos=&quot;45.0&quot;&gt;
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;100045.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;isEurobalise positionInGroup=&quot;0&quot; duplicate=&quot;no&quot; mVersion=&quot;32&quot;/&gt;
&lt;/balise&gt;
&lt;balise id=&quot;bg1_bal1&quot; type=&quot;fixed&quot; belongsToBaliseGroup=&quot;bg1&quot;
 
distanceToPredecessorBaliseWithinGroup=&quot;3.0&quot;&gt;
&lt;name name=&quot;127-00777-1&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg1_bal1_sloc01&quot; netElementRef=&quot;ne_101&quot;
 
applicationDirection=&quot;both&quot; pos=&quot;48.0&quot;&gt;
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;100048.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;isEurobalise positionInGroup=&quot;1&quot; duplicate=&quot;no&quot; mVersion=&quot;32&quot;/&gt;
&lt;/balise&gt;
&lt;balises/&gt;
 
===== Example 2 – Eurobalises belonging to a Eurobalise group consisting of 1 fix data balise and 1 controlled balise =====
 
This example shows the balise elements belonging to the ETCS balise group presented in section 1.2.2 of railML element “baliseGroup”.
 
Figure 7: Example 2 – Balise group of 1 fix data balise and 1 controlled balise
 
Corresponding railML description:
 
&lt;balises&gt;
&lt;balise id=&quot;bg2_bal0&quot; type=&quot;fixed&quot; belongsToBaliseGroup=&quot;bg2&quot;
 
distanceToPredecessorBaliseWithinGroup=&quot;0.0&quot;&gt;
&lt;name name=&quot;127-00787-0&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg2_bal0_sloc01&quot; netElementRef=&quot;ne_102&quot;
 
applicationDirection=&quot;both&quot; pos=&quot;985.0&quot;&gt;
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;101985.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;isEurobalise positionInGroup=&quot;0&quot; duplicate=&quot;no&quot; mVersion=&quot;16&quot;/&gt;
&lt;/balise&gt;
&lt;balise id=&quot;bg2_bal1&quot; type=&quot;controlled&quot; belongsToBaliseGroup=&quot;bg2&quot;
 
distanceToPredecessorBaliseWithinGroup=&quot;3.0&quot;&gt;
&lt;name name=&quot;127-00787-1&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg2_bal1_sloc01&quot; netElementRef=&quot;ne_102&quot;
 
applicationDirection=&quot;both&quot; pos=&quot;982.0&quot;&gt;
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;101982.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;isEurobalise positionInGroup=&quot;1&quot; duplicate=&quot;no&quot; mVersion=&quot;16&quot;/&gt;
&lt;/balise&gt;
&lt;balises/&gt;
 
===== Example 3 – A Eurobalise belonging to an Eurobalise group consisting of 1 fix data balise =====
 
This example shows the balise elements belonging to the ETCS balise group presented in section 1.2.4 of railML element “baliseGroup”.
 
Figure 8: Example 3 – Balise group of 1 fix data balise
 
Corresponding railML description:
 
&lt;balises&gt;
&lt;balise id=&quot;bg4_bal0&quot; type=&quot;fixed&quot; belongsToBaliseGroup=&quot;bg4&quot;
 
distanceToPredecessorBaliseWithinGroup=&quot;0.0&quot;&gt;
&lt;name name=&quot;127-00727-0&quot; description=&quot;etcsName&quot; language=&quot;EN&quot;/&gt;
&lt;spotLocation id=&quot;bg4_bal0_sloc01&quot; netElementRef=&quot;ne_104&quot;
 
applicationDirection=&quot;both&quot; pos=&quot;210.0&quot;&gt;
&lt;linearCoordinate positioningSystemRef=&quot;lps01&quot; measure=&quot;103210.0&quot;/&gt;
&lt;/spotLocation&gt;
&lt;isEurobalise positionInGroup=&quot;0&quot; duplicate=&quot;no&quot; mVersion=&quot;16&quot;/&gt;
&lt;/balise&gt;
&lt;balises/&gt;
 
==== Additional Information ====
 
===== Open Issues =====


If the general information provided by the railML element “balise” is not sufficient for a KER balise application, then please open a request in the railML forum reporting the missing information to be modelled in railML. RailML.org will provide a suggestion for modelling the missing information in railML, for example added by a new optional sub-element “railML/infrastructure/functionalInfrastructure/balises/<br />
The following semantic rules are applicable for the use of element {{tag|IS|baliseGroup}} with {{rml|3.2}}:
balise/isEbicabBalise“ which includes the new requested information.
{{semcon|
The element “baliseGroup” shall always use the {{rml}} option “spotLocation” to define the balise group location on the topology.
|id=001
|proposed=2021-12-20
|status=proposed
}}
Justification: According to UNISIG-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 3.4.2.2.1 and UNISIG-040 (versions 2.3.0, 3.3.0 or 3.4.0) section 3.3.1.3, a balise group (represented by the {{rml}} element {{tag|IS|baliseGroup}}) shall be considered as point-shaped element without extension. The reference location of the balise group is the location of the balise with N_PIG=0.

Latest revision as of 19:18, 4 January 2023

Introduction

Automatic train protection systems (ATP systems) consist of an onboard system part and a trackside system part. The communication between trackside and onboard equipment is realized in various different technical solutions using different media like cables (for example ATP system LZB in Germany), inductive systems (for example ATP system PZB in Germany), balises (like ATP system EBICAB in Norway) or others.

To provide information particular about balise based ATP systems, the railML® element <baliseGroup> shall be used. However for ATP systems using other media (cable, inductive, mechanical, ….), the optional railML® element <trainProtectionElement> and their child elements shall be used.

General attributes suitable for a balise group

The railML® element railML/infrastructure/functionalInfrastructure/baliseGroups/baliseGroup can be used for every kind of a balise group.

This means concerning the hardware aspect, that the railML® element <baliseGroup> can be used to describe a KVB balise group, an Ebicab balise group or and RSDD balise group (usually known as KER balise systems), and of course also for a Eurobalise group with their software applications like GNT, ZBS, specific packet 44 applications (e.g. like TBL1+) or – most common – for ETCS.

For all these various balise based ATP systems the general information below can be described with railML®:

  • the Location of the balise group (which is the location of the first balise of the balise group)
    →see child <spotLocation>
  • the number of balises belonging to the considered balise group
    →see @numberOfBalisesInGroup
  • the orientation of the balise group in relation to the netElement
    →see @mileageDirection
  • information, if the balise group is covered (virtually or physically as e.g. by a metal plate which suppressed the transmission of information from the balise group)
    →see @coverage
  • information of the balise group application, which can be a specific packet 44 application or ETCS or others
    →see sub-element <applicationType>
    In case of <applicationType>@value="ETCS", the optional sub-element <isEurobaliseGroup> shall be used to specify the information required for ETCS.
Information of the balise group function

To equip a railway line with a balise based ATP system, often the balise group locations and their functions are determined during the design phase.

The railML® element <baliseGroup> can describe balise group functions as below:

The balise group functions, the track topology information and the infrastructure manager specific ATP operational rules are the basis to determine the ATP trackside equipment and if necessary also the software of the ATP elements (like for ETCS).

According to the use case ETCS Track Net, the railML® element <baliseGroup> provides the attributes and elements to transfer the information of the design phase from an infrastructure manager to a signaling supplier via railML®.

Specific Information for an Eurobalise group for ETCS

In case if a balise group is an Eurobalise group, then the railML® child element <isEurobaliseGroup> can be used to provide ETCS specific balise group information.

This is applicable for all ATP systems using a hardware device fulfilling UNISIG-SUBSET-036 (Specification of Eurobalise) together with an SRS ETCS based telegram language as for GNT, ZBS, ETCS or national ATP applications using ETCS-Packet 44.

Relation between railML® attributes and the corresponding UNISIG variables for ETCS

In case of a Eurobalise group, the optional sub-element <isEurobaliseGroup> shall be used to specify the ETCS related information:

  • the value of UNISIG variable M_VERSION valid for all balises belonging to the considered balise group (provided in railML® by attribute @mVersion), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.79
  • the value of UNISIG variable NID_C (provided in railML® by attribute @countryID), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.86
  • the value of UNISIG variable NID_BG (provided in railML® by attribute @groupID), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.85
  • the value of UNISIG variable N_TOTAL (provided in railML® by attribute @numberOfBalisesInGroup; N_TOTAL = [value of numberOfBalisesInGroup]-1), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.82
  • the value of UNISIG variable Q_LINK (provided in railML® by attribute @isLinked), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.114
  • the value of UNISIG variable Q_LOCACC (provided in railML® by attribute @locationAccuracy), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.115
  • the value of UNISIG variable Q_LINKREACTION (provided in railML® for train movements passing the balise group in nominal direction by attribute @linkReactionNominal; provided in railML® for train movements passing the balise group in reverse direction by attribute @linkReactionReverse), which is defined by UNISIG in SUBSET-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 7.5.1.117
Remarks
  • If a balise group shall be covered during a construction phase, then it is possible to specify if the coverage is executed physically by a metal plate (@coverage="physical") or if the coverage is managed virtually using ETCS packet 0 (@coverage="virtual"). The optional railML® element '<isValid from="" to=""/> can be used to specify the period during which the balise group is to be covered.
  • The values of the following UNISIG variables of the ETCS balise telegram header are implicitly provided if a railML® element baliseGroup is used:

    • Q_UPDOWN=1 (means: “Up-link telegram: track to train)
    • Q_MEDIA=0 (means: “Balise”)
  • The values of the following UNISIG variables of the ETCS balise telegram header can be provided by the railML® element balise (see section 2), if necessary:

    • M_DUP
    • N_PIG
    • In case of ATP systems “GNT” and “ZBS”, @mVersion="0" shall be used. Further optional railML® attributes describing UNISIG variables can be used if appropriate.

Examples

Example 1 – Balise group with SMB (ETCS Level 2)

Image1.pdf

Example 1 – Balise group with SMB (ETCS Level 2)

Explanation

A balise group is assigned to a stop marker board (SMB) 321 (ID inside the railML®: @ref="sig_SMB_321"). The balise group is oriented in direction of increasing mileage (@mileageDirection="nominal") and in consequence the internal numbering of the balises in the balise group is aligned with the increasing mileage.

The balise group has only a logical connection (@type="logical") with the real signal / SMB on the trackside. The balises in this balise group are not covered virtually (@coverage="none").
The balise group consists of two balises (@numberOfBalisesInGroup="2") used for ETCS (applicationType value="ETCS"), which are allocated in Germany (@countryID="127" means Germany). It is the balise group No. 777 in Germany (@groupID="777").

The balise group is announced by a linking information (@isLinked="true") transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will trigger a trip procedure immediately (@linkReactionNominal="trainTrip"). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@linkReactionReverse="noReaction").

The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (@locationAccuracy="5"). UNISIG-baseline 3 is in use (@mVersion="32").

Corresponding railML® description
<baliseGroups>
  <baliseGroup id="bg1" mileageDirection="nominal" coverage="none" 
		numberOfBalisesInGroup="2">
    <name name="127-00777" description="etcsName" language="EN"/>
    <spotLocation id="bg1_sloc01" netElementRef="ne_101" 
		applicationDirection="both" pos="45.0">
      <linearCoordinate positioningSystemRef="lps01" measure="100045.0" />
    </spotLocation>
    <applicationType value="ETCS" />
    <connectedWithInfrastructureElement ref="sig_SMB_321" type="logical" />
    <functionalType value="signal" mileageDirection="nominal" />
    <isEurobaliseGroup countryID="127" groupID="777" isLinked="true" 
		linkReactionNominal="trainTrip" linkReactionReverse="noReaction" 
		locationAccuracy="5" mVersion="32" />
  </baliseGroup>
</baliseGroups>
Example 2 – Balise group with main signal (ETCS Level 1)

Image2.pdf

Example 2 – Balise group with main signal (ETCS Level 1)

Explanation

A balise group is assigned to a signal “Signal A” (ID inside the railML® file: @ref="sig_A"), which is oriented in direction of decreasing mileage. The balise group is oriented in direction of decreasing mileage (@mileageDirection="reverse") and in consequence the internal numbering of the balises in the balise group is aligned with the decreasing mileage.

The balise group has a physical connection (@type="physical") with the real signal on the trackside. The balises in this balise group are not covered virtually (@coverage="none").
The balise group consists of two balises (@numberOfBalisesInGroup="2") used for ETCS (<applicationType value="ETCS"), which are allocated in Germany (@countryID="127" means Germany). It is the balise group No. 787 in Germany (@groupID="787").

The balise group is announced by a linking information (@isLinked="true") transmitted to the train. If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will trigger a trip procedure immediately (@linkReactionNominal="trainTrip"). If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@linkReactionReverse="noReaction").

The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (@locationAccuracy="5"). UNISIG-baseline 2 is in use (@mVersion="16").

Corresponding railML® description
<baliseGroups>
  <baliseGroup id="bg2" mileageDirection="reverse" coverage="none" 
numberOfBalisesInGroup="2">
    <name name="127-00787" description="etcsName" language="EN"/>
    <spotLocation id="bg2_sloc01" netElementRef="ne_102" 
applicationDirection="both" pos="985.0">
      <linearCoordinate positioningSystemRef="lps01" measure="101985.0"/>
    </spotLocation>
    <applicationType value="ETCS"/>
    <connectedWithInfrastructureElement ref="sig_A" type="physical"/>
    <functionalType value="signal" mileageDirection="reverse"/>
    <isEurobaliseGroup countryID="127" groupID="787" isLinked="true" 
linkReactionNominal="trainTrip" linkReactionReverse="noReaction" 
locationAccuracy="5" mVersion="16"/>
  </baliseGroup>
<baliseGroups/>
Example 3 – Balise group for a stop-if-in-shunting panel (ETCS Level 1 and/or 2)

Image3.pdf

Example 3 – Balise group for a stop-if-in-shunting panel (ETCS Level 1 and/or 2)

Explanation

A balise group is assigned to a stop-if-in-shunting panel (ID inside the railML® file: @ref="panel_StopSH"). The balise group is oriented in direction of increasing mileage (@mileageDirection="nominal") and in consequence the internal numbering of the balises in the balise group is aligned with the increasing mileage.

The balise group has only a logical connection (@type="logical") with the real stop-if-in-shunting panel on the trackside. The balises in this balise group are not covered virtually (@coverage="none").
The balise group consists of two balises (@numberOfBalisesInGroup="2") used for ETCS (applicationType value="ETCS"), which are allocated in Germany (@countryID="127" means Germany). It is the balise group No. 747 in Germany (@groupID="747").

The balise group is announced by a linking information (@isLinked="true") transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@linkReactionNominal="noReaction"). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@|linkReactionReverse|IS:isEurobaliseGroup}}="noReaction"), too.

The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (@locationAccuracy="5"). UNISIG-baseline 2 is in use (@mVersion="16").

Corresponding railML® description
<baliseGroups>
  <baliseGroup id="bg3" mileageDirection="nominal" coverage="none" 
numberOfBalisesInGroup="2">
    <name name="127-00747" description="etcsName" language="EN"/>
    <spotLocation id="bg3_sloc01" netElementRef="ne_103" 
applicationDirection="both" pos="500.0">
        <linearCoordinate positioningSystemRef="lps01" measure="102500.0"/>
    </spotLocation>					
    <applicationType value="ETCS"/>
    <connectedWithInfrastructureElement ref="panel_StopSH" type="logical"/>
    <functionalType value="stopIfInShunting" mileageDirection="nominal"/>
    <isEurobaliseGroup countryID="127" groupID="747" isLinked="true" 
		linkReactionNominal="noReaction" linkReactionReverse="noReaction" 
		locationAccuracy="5" mVersion="16"/>
  </baliseGroup>
<baliseGroups/>
Example 4 – Balise group for odometry purposes (ETCS Level 1 and/or 2)

Image4.pdf

Example 4 – Balise group for odometry purposes (ETCS Level 1 and/or 2)

Explanation

This example shows a balise group for the odometry correction along a track. The internal orientation of the balise group is in direction of increasing mileage (@mileageDirection="nominal").

The balise group consists of one balise (@numberOfBalisesInGroup="1") used for ETCS (<applicationType value="ETCS"), which is allocated in Germany (@countryID="127" means Germany). It is the balise group No. 727 in Germany (@groupID="727"). The balise in this balise group is not covered virtually (@coverage="none").

The balise group is announced by a linking information (@isLinked="true") transmitted to the train. If a train running in the direction of increasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@linkReactionNominal="noReaction"). If a train running in the direction of decreasing mileage will not detect the balise group within the expectation window, then the ETCS onboard system will ignore this problem (@linkReactionReverse="noReaction"), too. The additional tolerance value on the regular accuracy towards the measured location is +/- 5m (@locationAccuracy="5"). UNISIG-baseline 2 is in use (@mVersion="16").

Corresponding railML® description
<baliseGroups>
  <baliseGroup id="bg4" mileageDirection="nominal" coverage="none" 
		numberOfBalisesInGroup="1">
    <name name="127-00727" description="etcsName" language="EN"/>
    <spotLocation id="bg4_sloc01" netElementRef="ne_104" 
applicationDirection="both" pos="210.0">
      <linearCoordinate positioningSystemRef="lps01" measure="103210.0"/>
    </spotLocation>					
    <applicationType value="ETCS"/>
    <functionalType value="odometry" mileageDirection="nominal"/>
    <isEurobaliseGroup countryID="127" groupID="727" isLinked="true" 
		linkReactionNominal="noReaction" linkReactionReverse="noReaction" 
		locationAccuracy="5" mVersion="16"/>
  </baliseGroup>
<baliseGroups/>
Example 5 – Balise group for Temporary Speed Restrictions [TSR] (ETCS Level 1 and/or 2)

Image2.pdf

Example 5 – Balise group to announce a Temporary Speed Restriction [TSR] (ETCS Level 1 and/or 2)

Explanation

This example shows a temporary balise (<isValid from="2022-06-01" to="2022-07-15"/>) group in approach of a zone with temporary speed restriction [TSR], for example due to track work. The internal orientation of the balise group is in direction of increasing mileage (@mileageDirection="nominal").

The balise group consists of 4 balises (@numberOfBalisesInGroup="4") used for ETCS (<applicationType value="ETCS"), which is allocated in Germany (@countryID="127" means Germany). It is the balise group No. 8003 in Germany (@groupID="8003").

The <balise> in this balise group is not covered virtually (@coverage="none"). The balise group is marked as an unlinked balise group (@isLinked="false") and therefore without linking properties (means, no use of the optional attributes @linkReactionNominal, @linkReactionReverse and @locationAccuracy). UNISIG-baseline 2 is in use (@mVersion="16").

Corresponding railML® description
<baliseGroups>
  <baliseGroup id="bg5" mileageDirection="nominal" coverage="none" 
		numberOfBalisesInGroup="4">
    <name name="127-08003" description="etcsName" language="EN"/>
    <isValid from="2022-06-01" to="2022-07-15"/>
    <spotLocation id="bg5_sloc01" netElementRef="ne_105" 
		applicationDirection="both" pos="650.0">
      <linearCoordinate positioningSystemRef="lps01" measure="104650.0"/>
    </spotLocation>
    <applicationType value="ETCS"/>
    <functionalType value="TSR" mileageDirection="nominal"/>
    <isEurobaliseGroup countryID="127" groupID="8003" isLinked="false" 
		mVersion="16"/>
  </baliseGroup>
<baliseGroups/>

Additional Information

Open Issues

If the general information provided by the railML® element “baliseGroup” is not sufficient for a KER balise application, then please open a request in the railML® forum – https://forum.railml.org (link to the railML® website) – reporting the missing information to be modelled in railML®. railML®.org will provide a suggestion for modelling the missing information in railML®, for example added by a new optional sub-element railML/infrastructure/functionalInfrastructure/baliseGroups/baliseGroup/isEbicabBalise which includes the new requested information.

Semantic Rules applicable for railML® element “baliseGroup”

The following semantic rules are applicable for the use of element <baliseGroup> with railML® 3.2:

Private-cloud-icon.png Proposed Semantic Constraint "001":
 

The element “baliseGroup” shall always use the railML® option “spotLocation” to define the balise group location on the topology.


 
Proposed on December 20th 2021
FIXME: add Link to discussion!
Please, recognize our guidelines on semantic constraints

Justification: According to UNISIG-026 (versions 2.3.0, 3.4.0 or 3.6.0), section 3.4.2.2.1 and UNISIG-040 (versions 2.3.0, 3.3.0 or 3.4.0) section 3.3.1.3, a balise group (represented by the railML® element <baliseGroup>) shall be considered as point-shaped element without extension. The reference location of the balise group is the location of the balise with N_PIG=0.

Retrieved from "https://wiki3.railml.org/index.php?title=User:RailML_Coord_Documentation/IS:baliseGroup&oldid=7013"