1 tcn network management iec train communication network iec 61375 - clause 5 1999 december, hk...

1

TCN Network ManagementIEC Train Communication Network IEC 61375 - Clause 5

1999 December, HK

Train Network Management

Services for remote device configuration, monitoring and diagnostics

standardized in IEC 61375

application to ROSIN Maintenance System (RoMain)

2


1999 December, HK

Network Management defines a set of services for:

development, testing and conformance testing

commissioning: configuration, downloading, routing and marshalling

operation: error and performance monitoring

•

•

•

MVB

WTB

agent

manager

SPY

agent

agentagentagent

managed objects

maintenance: evaluation of error reports, access to equipment information•

agent

Train Network Management

3


1999 December, HK

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).

4


1999 December, HK

Summary of managed objects

WTB linkobjects

topography

status

control

domainobjects

task 1

taskobjects

task 2

task 3

task 4

variableobjects

clockobjects

stationobjects

release

messengerobjects

status

devices

bus administrator

domain

MVB linkobjects

status

GroupDirectory

control

downloadforce

reservation

inventory

status

unforceupload

control

set_upreserve

bindingsattach verify_domain

equipmentobjects

domainFunctionDirectory

StationDirectory

All objects have read or write services, and special services such as:

Bindings

journalobject

stopstart

NodeDirectory

Inspired from MMS (ISO 9506)

5


1999 December, HK

Access to Managed Objects

message transfer

call(indication)

call(request)

message transfer

management messages

object interface (API+AMI+ASI)

manager interface

User

network

managed objectsreply

(confirm)reply(response)

MGIUseragent

interface AGI

MIB

UserAGI

Manager AgentAgent (local to

manager)

6


1999 December, HK

Example of use: configuring Class 2 devices and bus administrator

points

analog input (station 077)

Analog output (station 048)

1 2 3 4 5 6 7 8 1 2 3 4

periodic list

Bus administrator (station 001)

agent

task 1

assign point 3 to port 2008

load periodic list: scan 2008 every 2 ms

assign point 1 to port 2008

Event logging(station 033)

manager (station 004)

agent

download task1 and

start

actual transfer

port 2008 port 2008port 2008

agent agent

7


1999 December, HK

TNM access to managed objects

LayerManagementEntities

user processes

= managed objects service messages

physical

link

processdata

messagedata

LME

LME

LMEAMIAPI

maintenancemessages

UP UPuser

processes

physical

link

processdata

messagedata

LME

LME

LMEAMIAPI

manager agent agentUP UP

user messages

user messages

ASI

UP UP

ASIMSIMIB

The manager commands remote agents by reading and writing their managed objects

Train Communication Network

8


1999 December, HK

Access to Local Objects

memory domains

Layer Management Entities

= managed objects

UP

user processesAGI

ASI

MVB

WTB

agent

clockvariables messenger LME

MVB link

bus admin.

API

memory domainsUP

UP

WTB link LME

LME

LME

management messages

AMI

The agent accesses its objects through interfaces called LME (Layer Management Entity)

9


1999 December, HK

Management Messages

The manager sends a call message, the agent responds by a reply message.

Management messages use the RTP's Call-Reply Message Transfer Protocol.

A time-out supervises the presence of the agent. The agent does not send spontaneouly

network

Manager (caller)

Call_Request

Receive_Confirm

Call_Confirm

Reply_Request

time

session session

replier time-out

call message

reply message

Agent (replier)

execute service

10


1999 December, HK

Management Message Format (example)

destination devicemode

source device

packet size final node

final station origin node

origin station connectrequest

connection reference

session header

packet headerrepeated in each

packet(defined in RTP)

credit size

message header(defined in RTP)

destination devicemode

source device

packet size final node

final station origin node

origin station

first packet second packet

2

4

6

8

10

12

14

16

18

20

22

24

26

28

0

30

32

16 bits 16 bits

link header(defined in MVB)

val_offsettype

val_offset

port

offset

type

TS

size

TNM_key

proto proto

data

nb_ranges

val_offset

port

offset

port

offset

type

TS

size

TS

size

message size

void

actual management

message

2

4

6

8

10

12

14

16

18

20

service identifier 0

11


1999 December, HK

TNM Messages Syntax

...suitable_period UNSIGNED8, -- 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.

standard_type ENUM16, -- application-defined standard type.desc_length UNSIGNED8, -- length of the description in octets.description ARRAY[desc_length] OF -- description of the meaning of the variable.{ char CHARACTER8, } ...

Graphical view

Text View

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

12


1999 December, HK

Station Objects

List of supported functions

Station identifier (some device have a static identifier)

List of supported link layers

Software Version

Device class: (class 2/3, bus administrator, gateway)

List of services supported by the agent

Static information

Vendor, Serial Number, Version, Station ID and Station Name

Dynamic information

ServicesRead inventory

Attach ports (Class 2 devices)

Read statusWrite reservationWrite control

13


1999 December, HK

MVB Link Management

Identification (Hardware, software)

Static information

Dynamic settingsConfiguration of the bus administrator:

Device Statuses

Device List

Periodic ListKnown Devices ListBus Administrators ListTurn duration

Line redundancyLink Error Counter

Reply Time

Dynamic status

Control: enable, disable; switch lists, pass mastership

read status, read devices_list, write control, write configurationServices

14


1999 December, HK

WTB Link Services

Identification (Hardware, software)

Static information

Dynamic settings

Link Status

Node Types

Nodes ListTopography

Dynamic status

Control: enable, disable mastership

read status, read nodes list, read topography, write control

Services

15


1999 December, HK

Process Variables Management

Objects

read (with sink time supervision)force

creation of traffic storedefinition of variables

definition of cluster lists

Services

included in supervisory interface:

unforce

clusters of variables in traffic stores identified by their PV_NAME

unforce_allread traffic store configuration

definition of dataset lists

16


1999 December, HK

Messages Transfer Management

RetriesError Counter

Number of Instances

Reply time-outPacket life-time

Dynamic objects

SettingsMessenger ID and version

Static objects

function directory

station directory (if implemented)

Routing objects

group directory

read status, read/write directories

Services

17


1999 December, HK

Memory Domain Management

Domains are down-loadable memory regions

Domains may be loaded into RAM or flash-EPROM

Services

download_set_up prepares downloading, verify, boot

Objects

Domains may contain configuration tables, parameters, programs

read_memory

write_memory

accesses individual variables

downloads a segmentdownload_segment

18


1999 December, HK

Task, Clock and User Services

tasksManaged objects

Servicesstart, stop, reset, synchronize

(all tasks are treated as a whole)

ClockServices

read clock, set clock

User-defined services

Servicescall mechanism (server subscription)description (short string)

Tasks

19


1999 December, HK

Differences with other Network Management

MMS, FMSTNM services

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

20


1999 December, HK

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

•

•

•

•

•

•

•

21


1999 December, HK

Toward Plug & Play

The information provided by network management in the devices allows plug & play

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)

All devices are self-identifying (manufacturer, software version, etc)

TNM is the base for integrating off-the-shelf and foreign devices

22


1999 December, HK

Variables Marshalling

Vehicle Function (internals hidden)

namednetwork variables

physicalinput

physical output

exchange block

heat_on

overload

The exchange block can be parametrized by network management services

The vehicle function itself is not user-programmable (but parametrizable)

temp

namedequipment variables

visible by client

visible on the bus

554:231234:50

14:00REAL32

BOOLEAN1

BOOLEAN1 100 ms100 ms

1000 ms

name addresstype period

23


1999 December, HK

RoMain: Equipment Access over the Internet

Device

TCP/IP

web server

powerair condition passenger info light

Communicate with on-board equipment without previous knowledge

brakesdoor

Any maintenance workshop in Europe can determine the configuration of a vehicleInternet technology offers a very comprehensive set of functions

slide door

Made by Westinghouse

Model Crank2000

Serial Number W23.11.129.43.4

Software 970602.122

vehicle equipment

web client(Netscape, Internet explorer)

MVB

web servermanufacturerdata base

Status closed

Openings 1554

24


1999 December, HK

Vehicle and Equipment Identification

Vehicle Identification

Configuration Parameters

Process Variables

Equipments List

UICManufacturer Name

Model NameHardware VersionSoftware Version

Description

Equipment Identification

Configuration Parameters

Process Variables

The Agent provides the equipment descriptors, which identify the equipment (not the device)

25


1999 December, HK

RoMain bases on TNM

remote RoMain clients

ROSIN server(railways directory)

Manufacturerserver

Data MinerClient

Secure TCP/IP Network

railways operators

equipmentmanufacturers

TCN Management Messages

HTTP servertrain equipment

proxy proxy proxyinternet

TCN

access to dynamic equipment information (variable values, logs)

access to static equipment information (web pages)

RoGate manager

RTPagent

RTP

agent

RTP

TCN devices

operatorserver

miner

26


1999 December, HK

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.

TNM Services for RoMain

• 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)

• Equipment Descriptor: reads the static and dynamic basic information

• Files (event log for equipment, as opposed to journal for device)

The following network management services have been added for RoMain:

27


1999 December, HK

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.

1 tcn network management iec train communication network iec 61375 - clause 5 1999 december, hk...

Documents