Transcript
IEEE WG-14 Meeting 3
March 22, 2001
Agenda • • • • • • •
8:30 AM 9:00 AM 9:15 AM 9:45 AM 10:45 AM 11:00 AM 12:00 Noon
• • • •
1:00 PM 2:30 PM 2:45 PM 4:00 PM
IEEE WG-14 Meeting 3
Coffee / Muffins Available Introductions General Overview of Standard (Bill Petit) Technical Overview of Standard (John Fayos) Break Continue Technical Overview Lunch (individuals responsible for lunch, menus to be brought in for lunch selection prior to break Continue Technical Overview / Addressing Discussions Break General Discussion Adjourn
2
Technical Overview • • • •
HRI Interface Overview Protocol Considerations & Requirements HRI Interface Architecture HRI Interface Protocols – – – –
Layers 6 & 7 Layer 4 Layer 3 Layers 1 & 2
• HRI Message Formats
IEEE WG-14 Meeting 3
3
HRI Data Communications Railroad System
Roadway System
Variable Message Signs Track Circuits
Traffic Signals
HRI Interface
Wayside Equipment Terminator
Advanced Transportation Controller
Surveillance
Vehicle Systems
Short Range Communications
Rail Operations Terminator
IEEE WG-14 Meeting 3
Traffic Management System
4
HRI Interface Wayside Equipment Terminator
Advanced Transportation Controller
ATC Functions
Wayside Equipment Terminator Functions
Crossing Controller
Grade Crossing Predictor
Internal Wayside Equipment Network
Wayside Equipment Gateway
Internal ATC Equipment Network
IEEE WG-14 Meeting 3
Traffic Controller
HRI Physical Interface ATC Gateway
Event Recorder
Wayside Function
Vehicle Presence Detector
Event Recorder
HRI Virtual Interface
ATC Function
5
HRI Interface Components • Wayside Functions – functions within the Wayside Equipment Terminator that obtain, calculate or otherwise generate railroad system information
• Wayside Gateway – HRI interface “bridge” controller • routes incoming messages to appropriate Wayside Function • routes outgoing messages to appropriate ATC Gateway
• ATC Gateway – companion to the Wayside Gateway
• ATC Functions – functions within the Advanced Traffic Controller that obtain, calculate or otherwise generate the roadway system information IEEE WG-14 Meeting 3
6
HRI Protocol Considerations • Railroad & Roadway System Independence – Limit impact of HRI interface protocols on existing equipment
• Multiple Interface Options – Enable local system designers to choose appropriate protocols for individual installations – One size does not fit all
• Cost Effectiveness – Select widely used standardized protocols (multiple suppliers)
• Limited Administration – Minimal level of cross-HRI installation coordination – Minimal, but not zero
IEEE WG-14 Meeting 3
7
HRI Protocol Requirements • Relatively limited set of technical requirements: – – – – –
Support point-to-point HRI configurations Support network HRI configurations Data rate of at least 19.2 kbps 128 byte transfer in less than 250 msec (nominal) Error detection scheme that meets the requirements for the transfer of safety-critical messages across the HRI interface
IEEE WG-14 Meeting 3
8
OSI Protocol Model • Layer 7: Application Layer. Selects appropriate service for the application. An application is the actual hardware and or software entity that performs a function in either the Railway or Roadway systems. • Layer 6: Presentation Layer. Provides data formatting (reformatting) and identification. • Layer 5: Session Layer. Coordinates the interaction between applications. • Layer 4: Transport Layer. Provides for end-to-end data integrity and quality of service in communications. • Layer 3: Network Layer. Switches and routes information. • Layer 2: Data Link Layer. Transfers units of information across a physical link. Provides media access control, synchronization, framing, and error detection and recovery. • Layer 1: Physical Layer. Moves bits across a medium.
IEEE WG-14 Meeting 3
9
HRI Interface Architecture Wayside Function
ATC Function HRI Information
Application Layer
Application Layer
HRI Messages
Presentation Layer
Wayside Gateway
Session Layer
Internal Transport Layer
Transport Layer
Presentation Layer
ATC Gateway HRI Message CRC ATCS Vital CRC * * *
Internal
Transport Layer
TCP UDP
Internal
Session Layer
Transport Layer Internal
ATCS Datagram * * * Network Layer
Internal
Network Layer
Link Layer
Internal
Link Layer
Physical Layer
Internal
Physical Layer
Internal Wayside Network
IEEE WG-14 Meeting 3
IP LonWorks RS485 ATCS
Ethernet LonWorks Serial
10/100BaseT LonWorks RS422 RS485
HRI Interface Network
Network Layer
Internal
Network Layer
Link Layer
Internal
Link Layer
Physical Layer
Internal
Physical Layer
Internal ATC Network
10
Layers 6 & 7 Message ID 9.4.40 9.4.41 9.1.41 9.4.42 9.4.43 9.1.43 9.4.44 9.4.45 9.1.45
Message Name
HRI Rail Crossing Operational State HRI Rail Crossing Configuration HRI Rail Crossing Configuration Request HRI Approaching Train Information HRI Wayside Equipment Status HRI Wayside Equipment Status Request HRI Roadway Obstacle Detection State HRI ATC Equipment Status HRI ATC Equipment Status Request
IEEE WG-14 Meeting 3
Source
Destination
Railroad System Railroad System Roadway System Railroad System Railroad System Roadway System Roadway System Roadway System Railroad System
Roadway System Roadway System Railroad System Roadway System Roadway System Railroad System Railroad System Railroad System Roadway System
11
Layer 4 • No Layer 5 protocols are specified for the HRI interface • Layer 4 protocol drivers: – Support safety-critical message transfer requirements – Limit local system administration and coordination between Wayside & ATC equipment
• Dual Layer 4 approach: – Upper level: • safety critical error detection • dependent upon HRI message type
– Lower level: • standard end-to-end error detection • not dependent upon HRI message type
IEEE WG-14 Meeting 3
12
Layer 4 -- Upper Level • Upper Level Protocols – All safety critical messages protected by ATCS Vital CRC • • • •
utilized extensively in the Railroad industry meets quantitative verification requirements in safety critical applications time tested and proven algorithms specified in ATCS specifications
– All HRI messages protected by a standard CRC-16 • standard error detection scheme used in communications systems
IEEE WG-14 Meeting 3
13
Layer 4 -- Upper Level • ATCS Vital CRC protects data between vital source and vital destination • Potential HRI interface source & destination combinations: ATCS Vital CRC
Wayside Function (vital source)
Wayside Function
Internal
Wayside Function
Internal
Wayside Function
Internal
IEEE WG-14 Meeting 3
Wayside Gateway (vital source)
Wayside Gateway (vital destination)
Wayside Gateway (vital destination)
ATC Gateway (vital destination)
ATCS Vital CRC
ATCS Vital CRC
ATC Gateway (vital destination)
ATC Gateway (vital source)
ATCS Vital CRC
Internal
ATC Function
Internal
ATC Function
Internal
ATC Function
ATC Function (vital source)
14
Layer 4 -- Lower Level • Provides end-to-end data transfer verification across the HRI physical interface Wayside Function
Internal
Wayside Gateway
TCP UDP No Protocol
ATC Gateway
Internal
ATC Function
• Specified Options: – TCP (Transmission Control Protocol) – UDP (User Datagram Protocol) – No Protocol
IEEE WG-14 Meeting 3
15
Layer 3 • Layer 3 protocol drivers: – Support safety-critical message transfer (Layer 4 ATCS Vital CRC) requirements – Limit local administration and coordination between Wayside & ATC equipment
• Dual Layer 3 approach: – Upper level: • ATCS network datagram
– Lower level: • multiple options
IEEE WG-14 Meeting 3
16
Layer 3 -- Upper Level • ATCS network addressing scheme I RRR NN DDDDDD
Address Type Identifier (0-9) Railroad Number (0-999) Network Node Number (0-99) Addressed Device Identifier (600000-699999)
– Address Type Identifier •
“3” -- Wayside Devices (wireline connected)
– Railroad Number • •
assigned to railroads by ATCS controlling authority single railroad number to be assigned to all ATC equipment
– Network Node Number •
assigned by local administrator
– Addressed Device Identifier •
IEEE WG-14 Meeting 3
“600000 - 699999”, assigned by local administrator
17
ATCS Network Datagram Byte #
Bit 7
Bit 6
0
0
0
1
0
0
0
0
0
0
2
0
0
0
0
0
3
0
0
0
0
0
4 5 6 7
1
0
1
0
Bit 5
Bit 4
Bit 3
Packet Type
0
1
Bit 2
Bit 1
Bit 0
Message Priority
0
1
Destination BCD Digit 3
Destination BCD Digit 5
1
Source BCD Digit 2
21
Message Label -- High Order Byte
Source BCD Digit 3
Source BCD Digit 4
22
Message Label -- Low Order Byte
13
Source BCD Digit 5
Source BCD Digit 6
23
Message Version
14
Source BCD Digit 7
Source BCD Digit 8
24
Application Data (N Bytes)
15
Source BCD Digit 9
Source BCD Digit 10
25 + N
Vital CRC (high order byte)
16
Source BCD Digit 11
Source BCD Digit 12
26 + N
Vital CRC
27 + N
Vital CRC
28 + N
Vital CRC (low order byte)
1
11
0
0
12
0
0
0
0
0
0
1
0
0
0
1
1
0
Destination BCD Digit 2
Destination BCD Digit 4
17
0
0
0
0
0
0
0
0
18
0
0
0
0
0
0
0
0
19
0
0
0
0
0
0
1
0
20
0
0
0
0
0
0
1
Vital
Destination BCD Digit 6
8
Destination BCD Digit 7
Destination BCD Digit 8
9
Destination BCD Digit 9
Destination BCD Digit 10
10
Destination BCD Digit 11
Destination BCD Digit 12
IEEE WG-14 Meeting 3
18
Layer 3 -- Lower Level • Routes information across the HRI physical interface
Wayside Function
Internal
Wayside Gateway
IP LonWorks RS-485 ATCS No Protocol
ATC Gateway
Internal
ATC Function
• Specified Options: – – – – –
IP (Internet Protocol) LonWorks RS-485 compatible network addressing ATCS No protocol (point-to-point configurations)
IEEE WG-14 Meeting 3
19
Layers 1 & 2 • Transfers data across the HRI physical interface
Wayside Function
Internal
Wayside Gateway
Ethernet LonWorks Serial / RS422 Serial / RS485
ATC Gateway
Internal
ATC Function
• Specified Options: – – – –
Ethernet (w/compatible physical link) LonWorks (w/compatible physical link) Serial RS-422 Serial RS-485
IEEE WG-14 Meeting 3
20
HRI Message Format Byte Location
Field Name
0
Message Length
1
Sequence Number
2 3 4 5 6 7– (7 + M) 8+M – 9+M
Time Stamp – month Time Stamp – day Time Stamp – hour Time Stamp – minute Time Stamp – second Message Data CRC-16
IEEE WG-14 Meeting 3
Field Description
Comment
Total Length of the HRI Message Packet, including the Message Length byte (10 + M bytes) Incremental sequence number for each message. Roll over at 255 to 0 Month (1-12) Day (1-31) Hour (0-24) Minute (0-59) Second (0-59) HRI Message Data (M bytes in length)
Max length = 128 bytes
16-bit CRC. Covers all bytes in the message packet prior to the CRC field. Specific algorithm needs to be specified.
GMT GMT GMT GMT GMT Max length = 119 bytes Calculated for all messages, vital and non-vital
21
HRI Message 9.4.40 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose:
HRI Rail Crossing Operational State 9.4.40 4904 Safety Critical (Vital) Wayside Device ATC Device 1 Once per second 1 packet Variable, Minimum of 5 bytes, Maximum of 33 bytes Provide safety critical railway crossing gate information to the roadway system
Notes:
IEEE WG-14 Meeting 3
22
HRI Message 9.4.40 Byte Location
Field Name
0 0 1 1 2
Number of Tracks Reserve Track Number Reserve WSA
2
CGU
2
CGD
2
DEF
2
ICO
2
STW
2 3-4
Field Description
Total number of tracks at the HRI (0-8) Not Used Track number (1-8) Not Used Warning System Activation 0 = Not Activated 1 = Activated Crossing Gates Up 0 = Crossing Gates Not Up 1 = Crossing Gates Up Crossing Gates Down 0 = Crossing Gates Not Down 1 = Crossing Gates Down Crossing Gate Defective 0 = Crossing Gate OK 1 = Crossing Gate Defective Island Circuit Occupied 0 = Island Circuit Unoccupied 1 = Island Circuit Occupied Second Train Warning 0 = No Second Train 1 = Second Train Present Not Used
Reserve Advance Pre-Emption Time Bytes 1-4 are repeated for each track present at the HRI Minimum packet length of 5 bytes (1 track) Maximum packet length of 33 bytes (8 tracks)
IEEE WG-14 Meeting 3
Comment
Max of 8 tracks Not Used, set to 0 Not Used, set to 0
Not Used, set to 0 LSB = 0.1 seconds
23
HRI Message 9.4.41 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose: Notes:
IEEE WG-14 Meeting 3
HRI Rail Crossing Configuration 9.4.41 4905 Informational Wayside Device ATC Device 1 On request or when there has been a change in status 1 packet TBD Provide railroad crossing configuration information to the roadway system Message information content and format is TBD
24
HRI Message 9.1.41 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose:
HRI Rail Crossing Configuration Request 9.1.41 4713 Query ATC Device Wayside Device 1 Determined by ATC Device 1 packet 1 byte Request the Wayside Device to send an HRI Rail Crossing Configuration Message
Notes:
IEEE WG-14 Meeting 3
25
HRI Message 9.4.42 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose: Notes:
HRI Approaching Train Information 9.4.42 4906 Informational Wayside Device ATC Device 1 1st transmission when train is 5 minutes from the crossing, once per minute thereafter until train enters the crossing 1 packet 7 bytes Provide train time of arrival estimates to the roadway system
Byte Location
Field Name
Field Description
0-1
Estimated Time of Arrival
2 -3
Estimated Time of Closure
4
Estimated Speed at Crossing Estimated Train Length
Estimated time until approaching train reaches the HRI crossing Estimated time that the crossing will remain closed Estimated speed of the train at the HRI crossing in mph Estimate of the train length in feet
5-6
IEEE WG-14 Meeting 3
Comment
LSB = 0.1 seconds LSB = 0.1 seconds LSB = 1 mph LSB = 1 foot
26
HRI Message 9.4.43 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose: Notes:
IEEE WG-14 Meeting 3
HRI Wayside Equipment Status 9.4.43 4907 Informational Wayside Device ATC Device 1 On request or when there has been a change in status 1 packet TBD Provide general status of the wayside equipment at the HRI to the roadway system Message information content and format is TBD
27
HRI Message 9.1.43 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose:
HRI Wayside Equipment Status Request 9.1.43 4715 Query ATC Device Wayside Device 1 Determined by ATC Device 1 packet 1 byte Request the Wayside Device to send an HRI Wayside Equipment Status Message
Notes:
IEEE WG-14 Meeting 3
28
HRI Message 9.4.44 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose:
HRI Roadway Obstacle Detection State 9.4.44 4908 Safety Critical (Vital) ATC Device Wayside Device 1 Once per second 1 packet 1 byte Provide safety critical railway crossing obstacle information to the railroad system
Notes: Byte Location
Field Name
0
OI
0
LTI
0
VAS
0
Reserve
IEEE WG-14 Meeting 3
Field Description
Obstacle Indicator 0 = No Obstacle 1 = Obstacle Present Long Term Obstacle Indicator 0 = No Obstacle 1 = Long Term Obstacle Present Vehicle Arrestor Barrier Status 0 = Vehicle Arrestor Barrier OK 1 = Vehicle Arrestor Barrier Not OK Not Used
Comment
Not Used, set to 0
29
HRI Message 9.4.45 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose: Notes:
IEEE WG-14 Meeting 3
HRI ATC Equipment Status 9.4.45 4909 Informational ATC Device Wayside Device 1 On request or when there has been a change in status 1 packet TBD Provide general status of the ATC equipment at the HRI to the railroad system Message information content and format is TBD
30
HRI Message 9.1.45 Name: Message Number: Message Label: Message Type: Source: Destination: Priority: Transmission Rate: Max Message Length: Packet Length: Purpose: Notes:
IEEE WG-14 Meeting 3
HRI ATC Equipment Status Request 9.1.45 4717 Query Wayside Device ATC Device 1 Determined by Wayside Device 1 packet 1 byte Request the ATC Device to send an HRI ATC Equipment Status Message
31
