Train Network Management

1. Train Network Management Services for remote device configuration, monitoring and diagnostics standardized in IEC 61375 application to ROSIN Maintenance System (RoMain)

2. Train Network Management WTB managed objects agent agent agent 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

3. 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. Summary of managed objects station MVB link WTB link variable messenger domain task clock journal equipment objects objects objects objects objects objects objects objects object objects status status status status task 1 domain Function control control control task 2 Directory devices topography reservation task 3 Bindings Station domain inventory task 4 Directory bus administrator Group Directory Inspired from MMS (ISO 9506) Node Directory All objects have read or write services, and special services such as: force set_up start reserve download stop unforce upload release bindings attach verify_domain

5. Access to Managed Objects User User User agent manager AGI MGI AGI interface interface Agent Manager (local to Agent manager) object interface (API+AMI+ASI) call (indication) call (request) managed objects reply (confirm) reply (response) MIB message message transfer transfer network management messages

6. Example of use: configuring Class 2 devices and bus administrator load periodic list: manager scan 2008 every 2 ms (station 004) assign assign download agent point 3 to point 1 to task1 and port 2008 port 2008 start periodic list actual transfer Bus administrator (station 001) port 2008 port 2008 port 2008 agent agent agent points 1 2 3 4 5 6 7 8 task 1 1 2 3 4 analog input Event logging Analog output (station 077) (station 033) (station 048)

7. TNM access to managed objects manager agent agent user user UP UP UP UP UP UP processes MIB processes MSI ASI user user ASI maintenance messages messages messages LME LME API AMI API AMI Layer Management process message process message Entities data data data data 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

8. Access to Local Objects management messages UP AGI memory UP agent user processes domains memory UP domains AMI API ASI variables LME messenger LME clock = managed objects MVB LME WTB bus Layer LME link link admin. Management Entities MVB WTB The agent accesses its objects through interfaces called LME (Layer Management Entity)

9. call message reply message 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

10. Management Message Format (example) 16 bits 16 bits 0 mode destination device mode destination device link header 2 (defined in MVB) proto source device proto source device 4 packet size final node packet header packet size final node 6 repeated in each final station origin node final station origin node packet 8 (defined in RTP) connect origin station origin station data request 10 connection reference type val_offset 14 message 12 header TS port 16 message size 14 (defined in size offset 18 RTP) 16 credit size session header type val_offset 20 18 TNM_key service identifier 0 20 nb_ranges actual 2 22 management TS port 4 message 24 size offset void 6 26 type val_offset 8 28 TS port 10 30 size offset 12 32 first packet second packet

11. 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, -- 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, } ... Text View

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

13. 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 Device Statuses Line redundancy Link Error Counter Device List Services read status, read devices_list, write control, write configuration

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

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

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

17. 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 downloads a segment download_segment read_memory accesses individual variables write_memory

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

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

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

22. Variables Marshalling Vehicle Function (internals hidden) physical input physical output visible by client named equipment variables name type address period heat_on BOOLEAN1 554:23 100 ms 100 ms 1234:50 overload BOOLEAN1 exchange block temp REAL32 14:00 1000 ms named visible on the bus network variables The exchange block can be parametrized by network management services The vehicle function itself is not user-programmable (but parametrizable)

23. 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 web client (Netscape, Internet explorer) slide door Device Westinghouse Made by Crank2000 Model web server manufacturer data base W23.11.129.43.4 Serial Number TCP/IP 970602.122 Software closed Status web server 1554 Openings MVB passenger info door air condition light power brakes vehicle equipment

24. Vehicle and Equipment Identification The Agent provides the equipment descriptors, which identify the equipment (not the device)

25. RoMain bases on TNM equipment manufacturers railways operators remote Manufacturer RoMain clients operator server server Data Miner Client Secure TCP/IP miner Network ROSIN server (railways directory) access to static equipment information (web pages) train equipment HTTP server internet proxy proxy proxy TCN manager agent agent TCN RoGate access to dynamic equipment information (variable values, logs) devices RTP RTP RTP TCN Management Messages

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

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