Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"signalStatusBlock2",
"OBJECT-TYPE",
"SYNTAX",
"OerString",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> An OER encoded string of the signalStatusTable2 structure as defined below. This object is used for uploading configuration data from the ASC in a bandwidth efficient manner. signalStatus2 ::= SEQUENCE { ascCurrentTick2.0, -- @NTCIP1202-v03B, Bytes 1 & 2 spatStatus2.0 -- 2 BYTES @NTCIP1202-v03B spatEnabledLanesCount.0 -- 1 BYTE @NTCIP1202-v03B spatEnabledLanesStatus.0 -- n BYTES signalGroupEntryCount.0 -- 1 BYTE signalData2 SEQUENCE OF SignalStatusData2 OPTIONAL } SignalStatusData2 ::== SEQUENCE { signalGroupEntryNumber.y -- 1 BYTE signalState2.y.x -- 1 BYTE @NTCIP1202-v03B signalStateMinEndTick2.y.x -- 2 BYTES @NTCIP1202-v03B signalStateMaxEndTick2.y.x -- 2 BYTES @NTCIP1202-v03B signalStateNextTick2.y.x -- 2 BYTES @NTCIP1202-v03B signalStateStartTick.y.x -- 2 BYTES @NTCIP1202-v03B } where: n = spatEnabledLanesCount. This is the number of octets in the OCTET STRING of spatEnabledLanesStatus signalGroupEntryCount is a count of the number of signalGroupEntryNumber included in this object. Only signalGroupEntryNumbers that are active (in use) are to be included. y is the signalGroupEntryNumber in the signalGroupEntryTable x is the movementEventNumber for the signalStatusTable2. Only a value of 1 (current interval) and 2 (next interval) are used. For example, if (y = ) signalGroupEntryNumbers 1, 2, 4, 8, 13 and 16 are included in this object, then signalGroupEntryCount.0 is equal to 6 and the SEQUENCE OF SignalStatusData2 is y = 1, 2, 4, 8, 13, and 16. x will still be 1, 2. Although this object theoretically allows up to 255 signalGroupEntryNumbers, check that the number does not exceed the Maximum Transmission Unit (MTU) of the lower layers used. An example of signalStatusBlock2 is provided in Annex F.3.3.3.1. See Annex E.2 for the equivalent object definition for the RSU. Note: It is necessary that the signalGroupIntersection and signalGroupID objects be SET in the RSU before the signalStatusBlock2 is SET to the RSU. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.18\"",
"::=",
"{",
"spat",
"18",
"}"
],
"syntax_tree": [
[
"row",
"OerString"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> An OER encoded string of the signalStatusTable2 structure as defined below. This object is used for uploading configuration data from the ASC in a bandwidth efficient manner. signalStatus2 ::= SEQUENCE { ascCurrentTick2.0, -- @NTCIP1202-v03B, Bytes 1 & 2 spatStatus2.0 -- 2 BYTES @NTCIP1202-v03B spatEnabledLanesCount.0 -- 1 BYTE @NTCIP1202-v03B spatEnabledLanesStatus.0 -- n BYTES signalGroupEntryCount.0 -- 1 BYTE signalData2 SEQUENCE OF SignalStatusData2 OPTIONAL } SignalStatusData2 ::== SEQUENCE { signalGroupEntryNumber.y -- 1 BYTE signalState2.y.x -- 1 BYTE @NTCIP1202-v03B signalStateMinEndTick2.y.x -- 2 BYTES @NTCIP1202-v03B signalStateMaxEndTick2.y.x -- 2 BYTES @NTCIP1202-v03B signalStateNextTick2.y.x -- 2 BYTES @NTCIP1202-v03B signalStateStartTick.y.x -- 2 BYTES @NTCIP1202-v03B } where: n = spatEnabledLanesCount. This is the number of octets in the OCTET STRING of spatEnabledLanesStatus signalGroupEntryCount is a count of the number of signalGroupEntryNumber included in this object. Only signalGroupEntryNumbers that are active (in use) are to be included. y is the signalGroupEntryNumber in the signalGroupEntryTable x is the movementEventNumber for the signalStatusTable2. Only a value of 1 (current interval) and 2 (next interval) are used. For example, if (y = ) signalGroupEntryNumbers 1, 2, 4, 8, 13 and 16 are included in this object, then signalGroupEntryCount.0 is equal to 6 and the SEQUENCE OF SignalStatusData2 is y = 1, 2, 4, 8, 13, and 16. x will still be 1, 2. Although this object theoretically allows up to 255 signalGroupEntryNumbers, check that the number does not exceed the Maximum Transmission Unit (MTU) of the lower layers used. An example of signalStatusBlock2 is provided in Annex F.3.3.3.1. See Annex E.2 for the equivalent object definition for the RSU. Note: It is necessary that the signalGroupIntersection and signalGroupID objects be SET in the RSU before the signalStatusBlock2 is SET to the RSU. <Object Identifier> 1.3.6.1.4.1.1206.4.2.17.1.18"
],
null,
null,
null,
null
]
}