Professional Documents
Culture Documents
Smart Grid Communications
Smart Grid Communications
Smart Grid Communications
Slide I 2
Communications Requirements
Slide I 3
Evolution of Telecommunications
TDM
Manual network era
Extent of
Deployment
Manual
switching
1920
1940
2-motion
selector
switching
Semielectronic
switching
1960
Ethernet
1980
Packet
based
switching
Digital
switching
2000
2020
24
64 Kbps
.
.
.
.
TDM
.
MUX
.
.
.
64 Kbps
64 Kbps
1
......................
1.544 Mbps
AGGREGATE
24
TDM
MUX
.
.
.
.
.
.
.
.
64 Kbps
24
24
Slide I 5
TDM Networking
Slide I 6
Conventional substation
communications
Slide I 7
Requirements
Data
Delay (latency)
tolerance*
Jitter (variation in
delay) tolerance*
Stream/burst
transmission
Error tolerance
Voice
High
High
Moderate
Bursts
Stream
Low
Moderate,
by
the
Packet/data loss
application requesting
tolerance
retransmission
Yes, by the application
Interruption
requesting
tolerance
retransmission
Proprietary/
Protocol standard
standardized
High
Some data loss is
acceptable until voice
quality becomes too low
Moderate (0.5 sec)
Protection
communications
Very low
(<20 ms)
Very low
Stream
Very low
No
None/very low
Standardized
Proprietary
Slide I 8
Slide I 9
Ethernet
Ethernet packets
Mesh network
Slide I 10
Why Ethernet?
Cost!
1/10/100 Gbps over the same fiber
Plug-and-play no configuration required
More efficient bandwidth utilization
Slide I 12
MPLS Benefits
Is expected to meet latency requirements for real-time
data
Teleprotection trial by Alcatel Lucent: 15 ms end-to-end delays
Label Switching
In a traditional IP network:
Each router performs an IP lookup (routing), determines a next-hop based
on its routing table, and forwards the packet to that next-hop
Rinse and repeat for every router, each making its own independent routing
decisions, until the final destination is reached
Slide I 15
Architecture
Slide I 16
MPLS Basics
Customer Edge
(CE) router
managed by
customer
Provider Edge
(PE) router
managed by
service provider
Slide I 17
Combined CE/PE
Slide I 18
VRF = virtual route forwarding; tables created and used to create traffic separation
Implementing QoS guarantees complete control of resources (bandwidth, priority, and so
on)
Implementing QoS allows peaceful coexistence of several traffic types (network
management, physical security management) with missioncritical traffic (SCADA, PMU,
GOOSE)
Slide I 19
MPLS VPN
By properly provisioning one physical MPLS VPN capable
infrastructure, several network overlays are possible
SCADA
PMU
GOOSE
Slide I 20
Communications considerations
Bandwidth (cost)
Latency (end-to-end delays)
Latency Control and QoS
Reliability (cost redundancy)
Monitoring
Management
Security
What is the availability requirements for the application
If data are lost, what are the consequences?
Slide I 21
Bandwidth
Slide I 22
Slide I 23
Latency
Slide I 24
Traffic segmentation
Slide I 25
PMU
Slide I 26
Conclusions
Properly engineered MPLS promises to provide QoS suitable
for real-time data
Testing is needed
Slide I 27
28
29