Keith Olson, NMT3, Los Alamos National Laboratory

1
Real-time Accessible Data Networking (RadNet)
101

• Keith Olson, NMT-3, Los Alamos National
  Laboratory
• Email Kolson_at_lanl.gov, Phone[phone]
• Mike Hoy, Aquila
• Email mhoy_at_Aquilagroup.com, Phone [phone]

2
What Is RadNet ?

• RadNet is a standard method for transmitting
  instrument data and status across the
  internet/intranet.

3
RadNets Mission Is To Allow Integration

• The purpose of RadNet is to provide a common
  mechanism for integration of instrumentation.
• In the computer industry, we see integration
  everywhere
• Microsoft Word
• Oracle database

4
Why is Integration Important?

• Effective maintainability
• Standardization
• Continuous Return on Investment
• Reduce Costs
• Scalability
• Redundancy

5
Four Questions That Any RadNet Protocol Must
Answer

• What Is It (CAM, PCM, etc)?
• Who/Where Is It?
• What Were The Readings?
• Was The Instrument Working Properly?

6
How TCP Works
7
How UDP Works
8
What Are Ports and Do They Matter?
Use of ports allow different applications to
access data coming from the network, which is why
one can read email and surf the Internet at the
same time.
HTTP Port 80
Internet
FTP Port 20
SMTP Port 25
9
What Is The OSI Model?

• Open systems Interconnection (OSI) is a set of
  ISO standards relating to data communication
• OSI was an international effort to create
  standards for computer communications
• It provides a framework for identifying where the
  functionality of various protocols fits into the
  overall scheme of things

10
TCP/UDP OSI Model Look Like
Application and Services
Application and Services
Presentation
TCP UDP
Session
IP
Transport
Data Link
Network
Physical
Data Link
Physical
11
Simplifying The OSI Model
Application and Services
Application, Platform, OS
TCP UDP
Internet Protocols
IP
Data Link
Network Interface
Physical
12
Where Does RadNet Fit Into The OSI Model?
Instrumentation Monitoring Computers
Application, Platform, OS
IP and UDP/TCP
Internet Protocols
RadNet
Network Interface
Network Interface
13
Network Settings Required To Connect To The
Network

• IP address - required
• Gateway (router) - optional
• Domain Name System (DNS) optional
• Host list (required for the instrument)
• Port (required for transmit and receive)

14
What Is A Host List?
Explains where the instrument sends the data.
15
How RadNet Is Packaged On A Ethernet Network
Ethernet Frame
IP Frame
TCP/UDP Frame
RadNet Data
16
How RadNet Compares to The Internet Protocol SNMP
Ethernet Frame
Ethernet Frame
IP Frame
IP Frame
UDP Frame
UDP Frame
RadNet Data
SNMP Data
17
RadNet is a Layered (component based) Approach

• Instrumentation
• Area Monitors
• Gamma
• Neutron
• Crit
• PCMs
• Whole body
• Hand foot
• Air Monitors
• Alpha
• Beta/Gamma
• Tritium

Data Stream
R A D N E T
N E T W O R K
E N C R Y P T I O N
18
Where Is RadNet Placed Within The Transport
Protocol
19
RadNet Data Structure
20
Simple Polling Architecture
Request Data
Transmit Data
MasterComputer
21
Old Communication Infrastructure

• RS-232/485 infrastructure was the bottleneck
• Data generated faster then could be requested or
  obtained
• Data was hard to route
• Dumb instruments
• Cost drove the features

22
Adapted to Internet Technologies

• Positional Protocol Format Router Technologies
  and Basic Internet Protocol Design
• Hardware OS Independent OSI Model
• Scalability Three Tier Architecture, Load
  Balancing
• Integration Basic Internet Design
• Flexibility Basic Internet and Hardware Design

23
New Communication (Internet/Intranet)
Infrastructure

• Now the instrumentation is the bottleneck
• Data can now be routed to where needed
• Smart instruments
• Costs still drive the features

24
Changes That Allow For These Technological Changes

• The Internet
• Faster CPUs
• Memory Density
• Increased Network Bandwidth

• Entire Internet Stack/Wireless Interface On A
  Single Chip
• New Mobile Technologies
• New Web Interface Technologies

25
Residual Problems In The Instrumentation Field

• Polling still being used
• Still running RS-232/485
• Limited scalability
• Non-routable data
• Manufacturers still control interfaces by
  implementing propriety protocols
• Non-standard

26
Changes Needed In The Instrumentation Field

• Standardized open communication protocol
• Adapt the internet technologies and dollars being
  spent to the instrumentation field
• Adopt push technologies/methodology
• Utilize steaming data technologies and
  multicasting technologies
• Take advantage of smarter instruments
• Deploy and use internet hardware
  technologies/methodology

27
What Instrument Manufacturers Dont See

• More money invested in down stream infrastructure
  than the cost of the new instrumentation, such
  as
• Database
• Reporting systems and report development
• Analysis routine
• Wiring
• Monitoring interfaces
• Control interfaces
• When changes occur, they can break the entire
  back end

28
Monitoring Computer(s) Learn

• When the Instrument Sends The First Packet of
  Data, The Monitoring Computer Learns About It.
• Upon Receiving The Second Data Packet, The
  Monitoring Computer Learns Its Frequency.
• Note This allows instrument(s) to be placed on
  the network without reconfiguring the monitoring
  computers

29
Two Types Of Instrument Data Streams

• Continuous Data Instruments
• Area Monitors
• Continuous Air Monitors
• Portable Instruments
• Transactional Data
• Personal Contamination Monitors
• SNM Portal Monitors
• Portable Instruments

30
Number One Rule

• Upon Any Status Change, Push A Packet
• Upon Starting Up
• At The Normal Push Rate
• Upon Entering An Alarm/Trouble Condition
  (abnormal push rate)
• Upon Completing a Transaction

31
UDP/IP Directed Packet Example
Gateway Address 172.17.1.241
IP Address 172.17.1.2
Gateway Address 172.17.4.241
IP Address 172.17.1.1 Send to Addresses
172.17.1.2 172.17.4.2 172.17.5.2
IP Address 172.17.4.2
Gateway Address 172.17.5.241
IP Address 172.17.5.2
32
UDP/IP Router Based Broadcast Packet Example
Gateway Address 172.17.1.241
IP Address 172.17.1.2
IP Address 172.17.1.3
Gateway Address 172.17.4.241
IP Address 172.17.1.1 Send to Addresses
172.17.1.255 172.17.4.255 172.17.5.255
IP Address 172.17.4.1
IP Address 172.17.4.2
Gateway Address 172.17.5.241
IP Address 172.17.5.1
IP Address 172.17.5.2
33
IP/UDP Router/switch Based Broadcast Packet
Example
Gateway Address 172.17.1.241
IP Address 172.17.1.2
IP Address 172.17.1.3
IP Address 172.17.1.1 Send to Addresses
172.17.1.255 172.17.4.255 172.17.5.255
IP Address 172.17.4.1
IP Address 172.17.4.2
IP Address 172.17.5.1
IP Address 172.17.5.2
34
IP/TCP Overhead Example
Request To Connect
Ok To Connect
Connect
Data Transfer Between The Two
Request To Disconnect
Ok To Disconnect
Disconnect
35
Example Of TCP/IP Data Loss
Network Error Destination Port Unreachable
Data Transfer Between The Two
Request To Connect
Request To Connect
36
TCP vs. UDP Comparison Chart
37
TCP vs. UDP Broadcast Comparison Chart
Multiple Monitoring Computers, Single Reading (1
Data Packet) , Rate 1 minute
Note 250 monitoring computers would equal 1
subnet, 500 2, 750 3, 1000 4 and 1250 5,
etc. This chart assumes a router based network.
38
Three Ways To Connect Instruments To The Network
Ethernet
Inst
TPC
RadNet RS-232/485
Ethernet
RS-232/485
Inst
Aquila
Ethernet
Inst
39
How Data Flows
40
How Do You Detect If An Instrument Quits Sending
Data?

• First Packet Received - Monitoring Software
  Learns About the Instrument
• Second Packet Received - Monitoring Software
  Calculates Its Frequency
• Monitoring Computer Has Not Received A Packet
  Within The Given Frequency - Take Some Action
• Note Similar to someone turning off the power on
  an instrument. How does one detect that event
  with Process Control software?

41
What Actions Can Be Taken By The Monitoring
Computer?

• Issue A RadNet Request Message
• If No Response Is Received
• Page Users
• Email Users
• Make Database Entry
• Update Computer Screens.\
• Send A RadNet Message To All Monitoring Computers
  Indicating An Instrument Problem

42
RadNet Acknowledge Receipt Message

• Purpose - To allow a server/monitoring computer
  to acknowledge the receipt of data.
• Used in the event the RadNet system needs
  assurances that the monitoring computer has
  received the data from the instrument.

43
How RadNet Provides Data Assurance (Data
Reliability of TCP)
1) Instrument Sends Data on Port 16367
2) Monitoring Computer Sends Acknowledge Receipt
Message on Port 16368
44
Instruments Supported by RadNet

• Alpha/Beta/Tritium Continuous Air Monitors PING
• Personal Contamination Monitors
• Portable Radiation Instrument
• SNM Portal Monitors
• Gamma Spec
• Security Seals
• Meteorological Tower Protocol
• Generic Sensors
• Area and Criticality Monitors
• Item Monitors

45
RadNet Messages

• Normal Data Transmission
• Acknowledge Receipt
• Pass Through
• Diagnostic/Self-Check
• Source Check
• Request/Send Date/Time
• Request Reading/Data

46
RadNet Benefits

• Existing network architecture can be used for
  implementation
• RadNet compliant instruments currently available
• Off-the-shelf hardware can be used to implement a
  new system
• New existing RAD instruments can be networked

47
RadNet Benefits Continued

• Supports email, paging, databases
• Allows any computer technology (portable or
  stationary) to became an instrument display
• Security can be implemented at several levels
• The system works with different families of
  radiation instrumentation (CAMs, PCMs, area
  monitors)

48
Suggestions

• Talk To Your Network Team
• Start Small (instruments and down stream
  capabilities)
• Security, Security, Security
• Know your site bandwidth usage
• Tune your monitoring system to minimize bandwidth
  usage
• Realistic Monitoring
• Be prepared for very, very large amounts of data

49
Some RadNet Design Considerations

• What Type Of Network Structure (Flat/ Routable,
  Worldwide/Shadow/VPN)
• Wire or Wireless (RF/IR/Power line)
• Security Consideration (Encryption,
  Authentication, Firewalls)
• Existing Network or Dedicated
• Bandwidth Usage
• How Long Can You Wait For Abnormal Condition

50
Ethernet Rules Of Thumb

• At 30 of bandwidth usage, network collisions are
  noticeable
• At 80 of bandwidth usage, the network becomes
  unstable

51
FPS 140.2 Compliant RF Ethernet
52
Overview

• RF Remote Device
• Access Point
• Authentication and Encryption Server
• Checks Authentication Certification/
  Username/Password
• Enterprise Network

53
RF Remote Device

• Wireless Setup w/o Encryption
• Must know name ESSID for Access Point
• Must have Username, Password,
  Certificate
• Only MAC Addresses Visible
• Encryption and Authentication done on Remote host
  CPU NOT on Card

54
Open Systems Interconnection (OSI)
55
Server

• Access Control (Validation)
• SS H / SS L Require Certification
• Authenticate Password/Username
• User Interface
• SS H Login
• Manager Approach
• https web interface
• TELNET Access

56
Concluding Remarks

• Currently one vendor that is DOE approved
• DOE site has security approval to run RF-Ethernet
  in controlled area
• Available under Linux and Windows
• Applications look no different than Hard-Wire
  Network

57
Where RadNet is Deployed
Where RadNet is Deployed
Where RadNet is Deployed
58
RadNet Web Site

• Http//Drambuie.lanl.gov/RadNet
• Http//www.rad-net.net/

59
Questions?