Upload
eric-hodges
View
218
Download
0
Tags:
Embed Size (px)
Citation preview
Oreste Andrisano
Franco Davoli
Luigi Paura
Stefano Vignola
Sandro Zappatore
Bologna 25 Febbraio 2004
La Piattaforma LABNET per il Telelaboratorio
___________
LABNET:
A Telelaboratory Platform
MAIN GOALSTo develop a H/W and S/W architecture for the remote control of distributed real laboratory equipment at various complexity levels.
To offer access to the physical resources on the basis of different users’ needs, skills and fields.
High School University
User Classes
Research Educational SME
Telecommunication systems measurement & testing
Telecommunication networks measurements & testing
Other application fields in engineering and physics
Application fields
Bologna 25 Febbraio 2004
LABNET-Methodologies
•Design of the Software Architecture and development of LABNET Server and Client sides
•Design and set-up of experiments on the “Telecommunication Measurement Testbed”
•Design and set-up of experiments on the “Networking Testbed”
•Definition of interfaces for the interconnection of external laboratories (e.g., CIRA wind tunnel)
Development Guidelines
Bologna 25 Febbraio 2004
Main AchievementsTechnical and Methodological Aspects
the drivers for the control of the instrumentation
the Labnet Server
the End-User Interfaces (GUI)
the “Experience Manager”
Development of
Design and set-up of
the Experiences
the related Documentation
Bologna 25 Febbraio 2004
Scientific Aspects
Main Achievements
Study and Design of Protocols Suitable for the proposed Integrated Learning System (ILS)
Design of a Software Architecture for the remote access and control of the Laboratory Environment
Performance evaluation of the system
Study and design of scalable audio/video coders for multimedia network applications
Evaluation of the effects of satellite link fading on the video stream quality, using different coding schemes and/or data packetization
Bologna 25 Febbraio 2004
Heterogeneity of physical interfaces and communication protocols
Each class of instruments is characterized by a specific physical interface and communication protocol for the remote access to the equipment.
Why a specific Software Architecture
Heterogeneity of development environments
In general, each class of instruments is provided with a specific software development kit for data gathering and reporting (e.g., LabView for oscilloscopes, voltmeters, etc., HP-Openview for routers, etc.)
Bologna 25 Febbraio 2004
Educational Sessions often involve a great number of user stations The multimedia streams with the information produced by the instruments and by network and telecommunication facilities must reach the student stations in an efficient way (without waste of transmission resources)
Heterogeneity of the access technologes The system must allow an efficient use of the laboratories by users exploiting different types of access technology (e.g., ISDN, xDSL, leased lines, …)
Why a specific Software Architecture
Access management The system must be able to allocate the proper resources for each requested experience, thus avoiding conflicts among different users
Bologna 25 Febbraio 2004
Why a specific Software Architecture
• The attention of the users should be focused on the specific features of the experiment being performed
• Only a subset of the instrument’s front panel controls is actually reproduced on the client side, according to the specific experiment, the depth of the experience and, possibly, the users’ skills
• The GUI allows to reproduce more than one device on the same page, thus providing a unified view of the set-up ready to be used, rather than a mere group of instruments.
GUI suitably designed for the ILS mission
Bologna 25 Febbraio 2004
Reflecting the requirements in the implementationClient side
• To connect to the laboratory environment, only a generic browser with Java2 plug-in is needed
To the LABNET Server
Remote users INTERNET
• Two different client stationsLecturer/Instructor station
Student station
Bologna 25 Febbraio 2004
Reflecting the requirements in the implementationClient side
• Lecturer Station
fully controls the “virtual” devices involved in the experience
monitors the presence of the student stations
delegates the control of the experience to a specific student station
selects and initializes the desired experience
• Student Station
communicates with LNS by using unicast packets (TCP)
passively participates in the experience, showing the user the current state and values of the “virtual” devices
receives data from LNS by means of multicast packets
communicates with LNS by using unicast packets whenever designated by the lecturer
Network
Measurement
Testbed
Telecommunication
Measurement
Testbed
Other
Laboratories
LABNET SERVER
MulticastingAuthentication
Registration
ResourceManagement
Protocols
Experiences
Network Measurement System Control Module
Telecommunication Measurement System Control Module
Other Laboratories
Interaction Module between Network and Telco.
Measurement System
INTERNET
Reflecting the requirements in the implementationServer side
Bologna 25 Febbraio 2004
Browser
Web Server
LABNETData Server
Client/Server Architecture
Host Client LABNET Server
Data Flow Diagram
HTML
Applet
Get <HTML Page>
Send <HTML Page>
Send Applet
Send <Command>
Send <Result>
Bologna 25 Febbraio 2004
WINDOWS
Front-end Server
Bridge
Experience Manager Experience Manager
Labview VI Vi2 Vi3
LINUX
TLC Measurement Testbed Networking Testbed
Daemon Agents Scripts
Oscilloscope Spectrum AnalyzerFunction Generator Router Matrix PC
MulticastingInternet SuiteProtocols
Data Repository
Labnet Server Protocol
Labnet Server Architecture
Testbeds
Experience Manager
Experience Manager
LNS Experience IDs, variables
Device IDs, Commands/Results
Labnet Server Architecture
Bologna 25 Febbraio 2004
LNS Communication Protocol
LNSP is an ad-hoc communication protocol for data transfer between LNS and Experience Manager.
The Protocol Data Unit consists of a header (referring to a specific experience) and zero, one, or more data “containers”
The data “container” is a structure for the variable (scalar or vector) encapsulation.
LNSP exploits the Internet suite for the actual exchange
Experience Manager
LNSLNSP
LNSP
TCP/IP
TCP/IP
Labnet Server Architecture
Bologna 25 Febbraio 2004
Timestamp (Sec) Timestamp (microsec.)
Sequence Number EXP # Pack type command
Number of containers
Packet Length Frag # tot. frag. remote port
1 2 3 4 5 6 7 8
LSNPHeader(24 bytes)
bytes
ContainerHeader(16 bytes)
Total element Total element 2 elem type Variable Name
ACTUAL DATA OF THE MENTIONED VARIABLE
….. Variable Name (cont)
Total element Total element2 elem type Variable Name
ACTUAL DATA OF THE MENTIONED VARIABLE
….. Variable Name (cont)
Format of a LNS PacketLabnet Server Architecture
ContainerHeader(16 bytes)
Container Payload(max. 4056 bytes)
Container Payload(max. 4056 bytes)
As m
any containers as specified by the related field in the L
SN
P H
eader
Bologna 25 Febbraio 2004
Initialization of all the lists, tables and internal structures
Main Configuration
Open network sockets
Start
UDP or TCP Packet
Labnet Server Architecture
The Main Loop
Repository
Hash table of variables List of the
connected stations
Descriptors of the experiences
Internal ACLs
Wait for a Packet
Decode packet andrelated containers
(if present)
According to the LSP, prepare an
answer and send it to clients or
exp. manager
Client domain
Exp. Manager domain
LNS
Bologna 25 Febbraio 2004
An example: initialization (1)
Initialize Equipment 1 Equipment 1 successfully initialized
Initialize the experience N Experience N successfully initialized
Launch the experience N
LNS
Experience Manager
Testbeds
Initialize Equipment 2
Initialize Equipment M…….
Equipment 2 successfully initialized
Equipment M successfully initialized
LNS Communication ProtocolLabnet Server Architecture
…….
Bologna 25 Febbraio 2004
get_default_value_var 1 Let default_value_var 1 = x
LNS
Testbeds
Experience Manager
An example: initialization (2)LNS Communication Protocol
Labnet Server Architecture
Exp1 Var 1 Exp1 Var 2 Exp1 Var N
get_default_value_var 2
get_default_value_var M…..
Let default_value_var 2 = y
Let default_value_var M = z…..
Allocate var 1 of Exp 1 and set Exp_1_var 1 = x
Allocate var 2 of Exp 1 and set Exp_1_var 2 = y
Allocate var M of Exp 1 and set Exp_1_var M = z…..
Exp_1_var 1 = x
Exp_1_var 2 = y
Exp_1_var M = z…..
Bologna 25 Febbraio 2004
An example: initialization (client side)LNS Communication Protocol
Labnet Server Architecture
Initialize the experience N Experience N successfully initialized
Select the experience N
LNS
Master Station
Experience N ready: Launch the specific applets Display the default values of variables
Java Applet
Bologna 25 Febbraio 2004
Testbeds
Experience Manager
LNSExp1 Var 1 Exp1 Var 2 Exp1 Var N
Java Applet
Labnet Server ArchitectureThe actual communication
Bologna 25 Febbraio 2004
Function Generator
GPIB Bus
Ethernet Bus
Noise Figure Meter
Spectrum Analyzer
Oscilloscope Infinium
GPIB ENET Interface
Internet Advisor
Datacom Analyzer
To the local Labnet LAN
Switch Catalyst D
E R E S C a t y t 5 0
X L P W R
RF signal generator
Channel Simulator
Host Server
RF signal generator Noise generator
Signal Switching Matrix
Host Server
DSP
Telecommunication Measurement Testbed
Bologna 25 Febbraio 2004
SDSERIESCatalyst 3500 XL
PWR
SD
MADE IN USA
xxxxxxxxxxxxxxxxxxADCKentrox
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
!
!
AAC-3 Kentrox
SD
10021EXTENSION
MODULE
PCMCIASLOT
WARNINGDO NOT REMOVETHIS CARD WITH
SYSTEM POWERED
RJ-45
SD
XMT
DS-3(1)
RCV
10300SINGLE PORT
DS 3
SD
XMT
DS-3(1)
RCV
10300SINGLE PORT
DS 3
SD
XMT
DS-3(1)
RCV
10300SINGLE PORT
DS 3
SD
10303TRI-V.35/EIA-530SINGLE DSX-1
V.35/EIA-530
(1)
V.35/EIA-530
(2)
V.35/EIA-530
(3)
DSX-1(4)
SD
10303TRI-V.35/EIA-530SINGLE DSX-1
V.35/EIA-530
(1)
V.35/EIA-530
(2)
V.35/EIA-530
(3)
DSX-1(4)
SD
rCisco3600SERIES
CISCOYSTEMSS
SD
MADE IN USA
xxxxxxxxxxxxxxxxxxADCKentrox
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
!
!
AAC-3 Kentrox
SD
10021EXTENSION
MODULE
PCMCIASLOT
WARNINGDO NOT REMOVETHIS CARD WITH
SYSTEM POWERED
RJ-45
SD
XMT
DS-3(1)
RCV
10300SINGLE PORT
DS 3
SD
XMT
DS-3(1)
RCV
10300SINGLE PORT
DS 3
SD
XMT
DS-3(1)
RCV
10300SINGLE PORT
DS 3
SD
10303TRI-V.35/EIA-530SINGLE DSX-1
V.35/EIA-530
(1)
V.35/EIA-530
(2)
V.35/EIA-530
(3)
DSX-1(4)
SD
10303TRI-V.35/EIA-530SINGLE DSX-1
V.35/EIA-530
(1)
V.35/EIA-530
(2)
V.35/EIA-530
(3)
DSX-1(4)
SD
Cisco 3600SERIESCISCO YSTEMSS SD
Cisco 3600SERIESCISCO YSTEMSS
SD
CISCO YSTEMS
Cisco 7500 SERIES
POWERA
POWERB
NORMAL
S
Modem
Serial Local Control
Cisco 3640 Cisco 3620 Cisco 3620
Cisco 2620 Catalyst 3524-XL
Traffic GeneratorStations
Cisco 7513
SD
Cisco 3600SERIESCISCO YSTEMSS
FE FEFE
FEFE
FE FE FE FE FE FE
Network Measurement Testbed
Bologna 25 Febbraio 2004
External Laboratories
CIRA Wind Tunnel in Capua
• Connected via HDSL at 2 Mbps
•Measurement of total pressure loss on bi-dimensional model in wind tunnel CT1
• All main parameter setting remotely controllable and measurement displayed
Bologna 25 Febbraio 2004
“Telecommunication Measurement Testbed” Examples of Available Experiences
Radio Links and Modems Satellite Other Measurements (High School - University)
Synthesis of Digital Band-Pass Modulation
Systems via DSPs(BFSK, BPSK, QPSK,
WCDMA…)
Measurements on Nortel Dasa equipment (with or without emulated satellite
link)
Active filtering Fine-tuning of a free FM
oscillator
Multipath ISI (2- or 3-ray channel)
Measurements of noise effect on H.261 and MPEG coding (with emulated satellite link)
Analog Modulation AM FM DSB spectra / effect of synchronization loss RF Interference (Notch effect)
BER Measurements for QPSK, varying Eb/No and coding rate, with bandwidth estimation
Bologna 25 Febbraio 2004
Measurements on Measurements on networking networking equipmentequipment
RoutingRouting QoSQoS VoIPVoIP
Measurements at various Internet stack levels and on hetereogeneous access networks (Ethernet, ATM, Frame-Relay, … )
Building a network infrastructure based on a static/dynamic
routing policy
Video streams transmission on best-effort netwoks with: RSVP DiffServ
QoS and P-QoS evaluation by varying the traffic load offered to the channel
Performance evaluation of different protocolsTCP congestion control with different TCP implementations (Reno, Tahoe, Vegas), varying the channel bandwidth
RIP/OSPF Routing table visualization in the presence of network topology changes
Real time measurements of Jitter Queue length TCP goodput Packet loss
Signalling trace
“Networking Testbed”Examples of Available Experiences
Bologna 25 Febbraio 2004
KB
10 KB
20 KB
30 KB
40 KB
50 KB
0 60 120 180
time
By
tes
/s
In Bytes/s - link 128 kbps In Bytes/s - link 640 kbps
Measured traffic vs time during the session related to an experiment on analog modulation. The client is connected to the server via a transmission line at 640 kbps
(dotted line) and at 128 kbps (solid line).
Performance Evaluation
Bologna 25 Febbraio 2004
DIST – Università di GenovaClasses in Telecommunication Networks, Telematics, Digital Communications
Training courses for the Ministry of Communications Educational Project
ITIS “Augusto Righi” - Napoli
ITIS “Maserati” - Voghera
Evaluation of educational impact
Serveral experiences have been tested in both university and high school settings. In particular:
Bologna 25 Febbraio 2004
INTERNET
Networking Testbed
CNIT WAN
Remote users
Remote users
Capua Wind Tunnel
Labnet Server
The “Device Under Test” (DUT) and the Instrumentation of each Testbed are in the same location
Telecommunication Systems Testbed
From the current situation …
Future Developments
DUT
DUT
Labnet (GRID) Server
Measurement Network
Control Network
User
… to Distributed Cooperative Laboratories (EUROLABNET)
Instrumentation and DUTs
are distributed over the
various Labs involved
in the experiment
Future Developments
Thanks to
Luigi Battaglia Antonio IudiciGianluca Massei Marta PasiAmedeo Scarpiello Giuseppe SpanòNunzia Ristaldi Davide VicedominiAlfonso Vollono Andrea Zinicola
….. And also to
Nicola De Lorenzo Luigi Di FraiaPiergiulio Maryni Umberto PallottaGianmarco Romano
Bologna 25 Febbraio 2004
DATA IN
Probe IF out
IF out
Probe RF out
RF out
DATA OUT
RF in
IF in
A
CKSB
• Decodificatore di Viterbi con quantizzazione soft a 3 bit
• Traffico equivalente a 128 canali telefonici
• Ridondanza per rivelazione e correzione degli errori (FEC)
• Due canali di servizio a 64 Kb/s
Sistema radio digitale CTR 210 HD/7 Siemens Telecomunicazioni S.p.A. (MI)TX1
RX2
RX1
LO
• Segnale banda base: 8448 kbps
• Banda Radio Frequenza: 7,125 – 7,425 GHz
• Frequenze Intermedie: 231 MHz (Tx), 70 MHz (Rx)
• Codice: HDB3/NRZ
• Modulazione/codifica: 16 TCM (Trellis Code Modulation)
– BANCO DI MISURA –Maschera di emissione a frequenza intermedia e BER
DATACOM/TELECOM ANALYZER
RF SIGNAL GENERATORMIXER
NOISE GENERATOR
Directional Coupler
SPECTRUM ANALYZER
Data out Data inDATA IN
Probe IF out
IF out
Probe RF out
RF out
DATA OUT
RF in
IF in
A
CKSB
Pattern di bit a 8 Mb/s
Segnale a 231 MHz Portante
Segnale a 70 MHz
TX
RX
FC : 70 MHzSPAN : 10 MHz
Fqz. : 301 MHzLevel : 5 dBm
LO
TELEMISURA via HTTP
BANCO DI MISURA
Client
INTERNET
ServerCNIT NAPOLI
Server
PC
GPIB Board
LABVIEW
DataSocketSERVER
HTML
Applets JAVA
WEB SERVER
BROWSER
CODICE JSP
Applets JAVA
REMOTIZZAZIONE DEL BANCO DI MISURA RISPETTO AL WEB SERVER
BANCO DI MISURA
Client
CNIT PARMA
CNIT NAPOLI
INTERNET
PC
HTML
Applets JAVA
BROWSER
Server
GPIB Board
LABVIEW
DataSocketSERVER
PC
WEB SERVER
CODICE JSP
Applets JAVA
AMPLIAMENTO DEL BANCO DI MISURA:Diagramma ad occhio – Costellazione TCM
DATACOM/TELECOM ANALYZER
RF SIGNAL GENERATORMIXER
NOISE GENERATOR
Directional Coupler
SPECTRUM ANALYZER
Data out Data inDATA IN
Probe IF out
IF out
Probe RF out
RF out
DATA OUT
RF in
IF in
A
CKSB
Pattern di bit a 8 Mb/s
Segnale a 231 MHz Portante
Segnale a 70 MHz
TX
RX
FC : 70 MHzSPAN : 10 MHz
Fqz. : 301 MHzLevel : 5 dBm
OSCILLOSCOPE
TRA 1 TRA 2 TRIGGER
DIAGRAMMA
AD OCCHIO
COSTELLAZIONE
TCM 16 STATI
LO