Transcript Train Network Management

Train Network Management
Services for remote device configuration, monitoring and diagnostics
standardized in IEC 61375
application to ROSIN Maintenance System (RoMain)
IEC Train Communication Network
TCN Network Management
1
1999 December, HK
IEC 61375 - Clause 5
Train Network Management
WTB
agent
agent
agent
managed objects
MVB
manager
SPY
agent
agent
agent
Network Management defines a set of services for:
• development, testing and conformance testing
• commissioning: configuration, downloading, routing and marshalling
• operation: error and performance monitoring
• maintenance: evaluation of error reports, access to equipment information
IEC Train Communication Network
TCN Network Management
2
1999 December, HK
IEC 61375 - Clause 5
Train Network Management Services
Train Network Management is a set of services implemented in each device, allowing:
• Remote Identification of the device
• Reservation of the device for configuration
• Download and Upload
• Start and Stop of tasks on the device
• Inventory of the supported functions
• Inventory of the exported and imported variables
• Remote access to network and internal variables
• Clock synchronisation
• Error Log reading (redundancy support)
• Identification of the supported equipment
The Network Management services allow full control of all attached devices.
It is the base for tool access to own devices and foreign devices
TNM controls the control system, not the applications (except start/stop).
IEC Train Communication Network
TCN Network Management
3
1999 December, HK
IEC 61375 - Clause 5
Summary of managed objects
station
objects
MVB link
objects
WTB link
objects
status
status
status
variable
objects
messenger
objects
domain
objects
status
domain
control
control
control
reservation
devices
topography
Function
Directory
clock
objects
journal
object
equipment
objects
task 1
task 2
task 3
Bindings
inventory
task
objects
Station
Directory
domain
task 4
bus
administrator
Group
Directory
Inspired from MMS (ISO 9506)
Node
Directory
All objects have read or write services, and special services such as:
reserve
release
force
unforce
bindings
attach
IEC Train Communication Network
TCN Network Management
set_up
start
download
stop
upload
verify_domain
4
1999 December, HK
IEC 61375 - Clause 5
Access to Managed Objects
User
manager
interface
User
MGI
Manager
agent
interface
AGI
AGI
Agent
(local to
manager)
User
Agent
object interface
(API+AMI+ASI)
call
(request)
managed
objects
reply
(confirm)
call
(indication)
MIB
reply
(response)
message
transfer
message
transfer
network
management messages
IEC Train Communication Network
TCN Network Management
5
1999 December, HK
IEC 61375 - Clause 5
Example of use: configuring Class 2 devices and bus administrator
load periodic list:
scan 2008 every 2 ms
manager
(station 004)
assign
point 3 to
port 2008
agent
periodic
list
download
task1 and
start
assign
point 1 to
port 2008
actual transfer
Bus administrator
(station 001)
port 2008
agent
agent
points 1 2 3 4 5 6 7 8
analog input
(station 077)
IEC Train Communication Network
TCN Network Management
port 2008
port 2008
agent
task 1
1 2 34
Event logging
(station 033)
Analog output
(station 048)
6
1999 December, HK
IEC 61375 - Clause 5
TNM access to managed objects
manager
user
UP UP
processes
agent
user
MIB
MSI
processes
user
maintenance
messages
messages
API
process
data
AMI
agent
UP UP UP UP
ASI
LME
Layer
Management
Entities
message
data
ASI
user
messages
API
AMI
process
data
message
data
LME
link
LME
link
LME
physical
LME
physical
LME
service messages
= managed objects
Train Communication Network
The manager commands remote agents by reading and writing their managed objects
IEC Train Communication Network
TCN Network Management
7
1999 December, HK
IEC 61375 - Clause 5
Access to Local Objects
management messages
UP
user processes
AGI
UP
memory
domains
memory
domains
agent
UP
AMI
API
variables
LME
ASI
messenger
LME
clock
= managed objects
MVB
bus
admin. link
LME
WTB
link
LME
Layer
Management
Entities
MVB
WTB
The agent accesses its objects through interfaces called LME (Layer Management Entity)
IEC Train Communication Network
TCN Network Management
8
1999 December, HK
IEC 61375 - Clause 5
Management Messages
Manager (caller)
Agent (replier)
session
network
session
Call_Request
Receive_Confirm
replier
time-out
execute
service
Reply_Request
time
Call_Confirm
Management messages use the RTP's Call-Reply Message Transfer Protocol.
The manager sends a call message, the agent responds by a reply message.
A time-out supervises the presence of the agent. The agent does not send spontaneouly
IEC Train Communication Network
TCN Network Management
9
1999 December, HK
IEC 61375 - Clause 5
Management Message Format (example)
0
2
mode
16 bits
destination device
proto
mode
link header
(defined in MVB)
source device
16 bits
destination device
proto
source device
4
6
8
10
packet size
final node
final station
origin node
origin station
connect
request
connection reference
12
message
header
(defined in
RTP)
message size
14
16
packet header
repeated in each
packet
(defined in RTP)
credit
size
session header
TNM_key
service identifier
18
20
nb_ranges
26
28
30
32
TS
size
type
2
TS
size
port
4
offset
6
val_offset
port
offset
first packet
IEC Train Communication Network
TCN Network Management
16
final node
final station
origin node
origin station
data
type
val_offset
TS
18
size
20
type
port
offset
val_offset
0
22
24
14
packet size
actual
management
message
void
8
10
12
second packet
10
1999 December, HK
IEC 61375 - Clause 5
TNM Messages Syntax
The message syntax specifies each bit and its position in the message.
A graphical view allows an intuitive view for the programmer.
A textual syntax based on ASN.1 (IEC/ISO 8824) allows to parse the messages
Graphical view
...
suitable_period
UNSIGNED8,
Text View
standard_type
desc_length
description
{
char
}
...
IEC Train Communication Network
TCN Network Management
ENUM16,
UNSIGNED8,
ARRAY[desc_length] OF
-- suitable period of the variable as power of
2 of 1 ms (e.g. 4 = 16 ms). If the variable
should be asked on demand, it equals ‘FF’H.
-- application-defined standard type.
-- length of the description in octets.
-- description of the meaning of the variable.
CHARACTER8,
11
1999 December, HK
IEC 61375 - Clause 5
Station Objects
Static information
Vendor, Serial Number, Version, Station ID and Station Name
List of services supported by the agent
Device class: (class 2/3, bus administrator, gateway)
List of supported link layers
Dynamic information
List of supported functions
Software Version
Station identifier (some device have a static identifier)
Services
Read inventory
Read status
Write reservation
Write control
Attach ports (Class 2 devices)
IEC Train Communication Network
TCN Network Management
12
1999 December, HK
IEC 61375 - Clause 5
MVB Link Management
Static information
Identification (Hardware, software)
Dynamic settings
Configuration of the bus administrator:
Periodic List
Known Devices List
Bus Administrators List
Turn duration
Reply Time
Control: enable, disable; switch lists, pass mastership
Dynamic status
Services
Device Statuses
Line redundancy
Link Error Counter
Device List
read status, read devices_list, write control, write configuration
IEC Train Communication Network
TCN Network Management
13
1999 December, HK
IEC 61375 - Clause 5
WTB Link Services
Static information
Identification (Hardware, software)
Dynamic settings
Node Types
Control: enable, disable mastership
Dynamic status
Link Status
Nodes List
Topography
Services
read status, read nodes list, read topography, write control
IEC Train Communication Network
TCN Network Management
14
1999 December, HK
IEC 61375 - Clause 5
Process Variables Management
Objects
clusters of variables in traffic stores identified by their PV_NAME
Services
read (with sink time supervision)
force
unforce
unforce_all
read traffic store configuration
included in supervisory interface:
creation of traffic store
definition of variables
definition of dataset lists
definition of cluster lists
IEC Train Communication Network
TCN Network Management
15
1999 December, HK
IEC 61375 - Clause 5
Messages Transfer Management
Static objects
Messenger ID and version
Settings
Number of Instances
Dynamic objects
Error Counter
Retries
Reply time-out
Packet life-time
Routing objects
function directory
station directory (if implemented)
group directory
Services
read status, read/write directories
IEC Train Communication Network
TCN Network Management
16
1999 December, HK
IEC 61375 - Clause 5
Memory Domain Management
Objects
Domains are down-loadable memory regions
Domains may be loaded into RAM or flash-EPROM
Domains may contain configuration tables, parameters, programs
Services
download_set_up
prepares downloading, verify, boot
download_segment
downloads a segment
read_memory
accesses individual variables
write_memory
IEC Train Communication Network
TCN Network Management
17
1999 December, HK
IEC 61375 - Clause 5
Task, Clock and User Services
Tasks
Managed objects
tasks (all tasks are treated as a whole)
Services
start, stop, reset, synchronize
Clock
Services
read clock, set clock
User-defined services
Services
call mechanism (server subscription)
description (short string)
IEC Train Communication Network
TCN Network Management
18
1999 December, HK
IEC 61375 - Clause 5
Differences with other Network Management
TNM services
MMS, FMS
encoding
plain
BER (ISO)
protocol
remote procedure call
own protocol (MMFS)
station descriptor
yes
Virtual Manufacturing Device
variables
read, write force
read, write (remote)
domains
upload, download, verify
upload, download
tasks
start/stop all
program invocations control
semaphores
reservation
various
events
done by messages
event management
journal
done by diagnostic task
journal management
files
none
uses FTAM
clock
read, set
none
IEC Train Communication Network
TCN Network Management
19
1999 December, HK
IEC 61375 - Clause 5
Strengths of TCN Network Management
• builds on MAP (MMS), Profibus (FMS), OSI (10164) and TCP/IP (SNMP)
• minimum set of objects and services
• no encoding information in PDU: all data types are predefined, simple parsing
• user-defined services can be included
• comprehensive domain download
• supports several link layers and routing
• tailored to the needs of the Train Communication Network
IEC Train Communication Network
TCN Network Management
20
1999 December, HK
IEC 61375 - Clause 5
Toward Plug & Play
The information provided by network management in the devices allows plug & play
All devices are self-identifying (manufacturer, software version, etc)
A (known) device can replaced by an off-the-shelf device and downloaded.
An unknown device can be inspected and its variables bound into the network
Network variables and Network functions can be bound separately
All equipment information is available as visible names of devices, variables, functions)
TNM is the base for integrating off-the-shelf and foreign devices
IEC Train Communication Network
TCN Network Management
21
1999 December, HK
IEC 61375 - Clause 5
Variables Marshalling
Vehicle Function (internals hidden)
physical
input
physical
output
visible by client
name
heat_on
overload
temp
named
equipment variables
type
address
period
BOOLEAN1
BOOLEAN1
554:23
1234:50
100 ms
100 ms
REAL32
exchange block
14:00 1000 ms
named
network variables
visible on the bus
The exchange block can be parametrized by network management services
The vehicle function itself is not user-programmable (but parametrizable)
IEC Train Communication Network
TCN Network Management
22
1999 December, HK
IEC 61375 - Clause 5
RoMain: Equipment Access over the Internet
Communicate with on-board equipment without previous knowledge
Any maintenance workshop in Europe can determine the configuration of a vehicle
Internet technology offers a very comprehensive set of functions
Device
Made by
Model
Serial Number
Software
Status
Openings
web client
(Netscape, Internet explorer)
slide door
Westinghouse
Crank2000
web server
manufacturer
data base
W23.11.129.43.4
TCP/IP
970602.122
closed
web server
1554
MVB
door
air condition
passenger info
light
power
brakes
vehicle equipment
IEC Train Communication Network
TCN Network Management
23
1999 December, HK
IEC 61375 - Clause 5
Vehicle and Equipment Identification
UIC
Manufacturer Name
Model Name
Hardware Version
Software Version
Description
Vehicle Identification
Configuration Parameters
Process Variables
Equipment Identification
Configuration Parameters
Equipments List
Process Variables
The Agent provides the equipment descriptors, which identify the equipment (not the device)
IEC Train Communication Network
TCN Network Management
24
1999 December, HK
IEC 61375 - Clause 5
RoMain bases on TNM
railways operators
equipment
manufacturers
remote
RoMain clients
operator
server
Manufacturer
server
Secure TCP/IP
Network
ROSIN server
miner
Data Miner
Client
(railways directory)
access to static
equipment information
(web pages)
train equipment
HTTP server
internet
proxy
proxy
RoGate
manager
RTP
proxy
TCN
access to dynamic
equipment information
(variable values, logs)
agent TCN agent
RTP devices RTP
TCN Management Messages
IEC Train Communication Network
TCN Network Management
25
1999 December, HK
IEC 61375 - Clause 5
TNM Services for RoMain
TNM allows the Web Proxy to access the TCN devices.
The alternative would be to implement directly TCP/IP (or DCE/IP) on each device.
Each device would become an internet server, which makes it too costly for simple I/O.
The following network management services have been added for RoMain:
• Equipment Descriptor: reads the static and dynamic basic information
• Bind / Unbind variables: read/write the variables exported and imported by the device
• Bind / Unbind functions: read/write the functions exported and imported by the device
• Read/Write physical variables (for retrofit)
• Files (event log for equipment, as opposed to journal for device)
IEC Train Communication Network
TCN Network Management
26
1999 December, HK
IEC 61375 - Clause 5
Conclusion
TNM provides the base for simpler engineering of own and foreign equipment
ROSIN / RoMain require TNM services to avoid costly special solutions for each new device.
Agent Implementation is simple (just a simple parser), but requires a close cooperation with
the devices builders.
The complexity lies in the implementation of the LME (Layer Management Entity), which is a
functionality which every designer implements sooner or later.
Implementing TNM now rather than later pays off in terms of simpler commissioning.
Although there are TCN-specific functions, TNM can also be used for other networks.
IEC Train Communication Network
TCN Network Management
27
1999 December, HK
IEC 61375 - Clause 5