Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
E-1
DS-1
E-3
Access
Edge
Metro
Core
Long-Haul
Core
DS-3
ATM
Optical Control
Plane
FR
10/100bT
IP
Ethernet
OC-3/12/48/192
Optical Control
Plane
STM-1o/4/16/64
FC
FICON
Optical Control
Plane
Internet serving
community of users
with common goals
and mutual trust:
Classical Internet
architecture
Commercialization of the
Internet:
More Business Critical
Infrastructure & Availability
Requirements
Bandwidth
request or
release from
clients
Management
System
X
Network failure
Control
Control
Plane
Plane
Signalling
Signalling
Routing
Routing
Discovery
Discovery
Improved
Improvedbandwidth
bandwidthusage/efficiency
usage/efficiency
Scheduled/unscheduled
Scheduled/unscheduledBoD
BoD
OSS
OSSsimplification
simplification
Autodiscovery
Autodiscovery
RFCs
Recommendations
IETF
GMPLS
Protocols
Interop Results
ASON/GMPLS E-NNI, UNI
Control
Plane
Mgmt.
OIF
Implementation
Agreements
Use Cases
Signalling for
Ethernet Services
TMF
Solution Sets
Ethernet
Services
MEF
Technical
Specifications
RFC
RFC
RFC
Control Plane
Solutions
IA
Rec.
RFC
RFC
RFC
RFC
RFC
IETF
10
IA
IA
OIF
Rec.
ITU-T
ITU-T
Requirements &
Architecture
TMF
509
RFC 3495
G.8080
AutoDiscovery
G.7714
G.7714.1
Signaling
G.7713
G.7713.2
RFC 4204
RFC 3474
G.7715
G.7715.1
RFC 4207
RFC 3473
RFC 3946
Routing
TMF
RFC 4208
RFC 4202
ENNI 1.0
ENNI 2.0
UNI 1.0
UNI 2.0
E-NNI
OSPF 1.0
OIF
G.7715.2
DCN/SCN
Management
11
G.7712
G.7718
G.7718.1
GMPLS
MIB RFCs
TMF
TMF
814
12
13
Routing
Security
OIF-UNI-01.0-R2
OIF-ENNI-01.0-OSPF OIF-SEP-01.0
OIF-UNI-01.0-R2-RSVP
OIF-SEP-02.1
OIF-ENNI-01.0
OIF-SMI-01.0
OIF-SMI-02.1
Management
OIF-CDR-01.0
Control Plane
Logging and Auditing
with Syslog
OIF-UNI-02.0
OIF-UNI-02.0-RSVP
OIF-ENNI-02.0
Draft
Straw Ballot
Letter Ballot
http://www.oiforum.com/public/impagreements.html
14
Approved IA
15
16
17
19
20
Services Heterogeneity
A wide range of services may be offered; e.g.,
Classical data (e.g., best effort Internet, Frame Relay)
Ethernet (e.g., EPL, EVPL, EPLAN, EVPLAN)
L1/L2/L3 Virtual Private Network (VPN)
SONET/SDH switched connection (e.g., STS-n, VC-n)
OTH switched connection (e.g., ODU, OCh)
21
22
NMS
EMS 1
EMS 2
23
Network Connection
SNC 2
E
X
A
M
P
L
E
24
NOBEL
25
26
27
28
29
30
DCN/SCN
G.7712
Signaling
G.7713
Autodisc
G.7714
Routing
initialization
Mgmt. FW
G.7715
G.7716
G.7718
Link State
G.7713.1
(PNNI-based)
G.7715.1
G.7713.3
(GMPLS-CR-LDP)
31
G.7715.2
Info Model
G.7718.1
Protocol
Specific
Recs.
G.7713.2
(GMPLS-RSVP-TE)
G.7714.1
(Discovery
SDH/OTN)
Remote Path
Query
Rec. G.8080
Automatically Switched Optical Network (ASON)
32
33
34
User
IP/MPLS
Provider
management
system
Management Plane
Router
Ethernet/
ATM / FR
SONET/ SDH
/ OTN
Router
Call
Control
Router
Provider
network
*Call
Control Optical Control Plane
Transport Plane
35
UNI
E-NNI
NE
Provider A
NE
NE
Provider B
NE
UNI enables:
36
I-NNI
E-NNI
Domain 1
E-NNI
Domain 2
UNI
UNI-C UNI-N
UNI-N UNI-C
E-NNI
NE
Provider A
NE
NE
Provider B
NE
E-NNI enables:
I-NNI
E-NNI
Domain 1
E-NNI
I-NNI supports:
37
Intra-domain connection
establishment
Explicit connection
operations on individual
switches
Domain 2
UNI
NE
NE
CALL
CONNECTIONS
38
UNI Call
Segment
Domain B
E-NNI
NE
NE
E-NNI Call
Segment
UNI
UNI Call
Segment
DCN
CONTROL PLANE
Data plane
39
C1
Provisioned
TN1
Provisioned
TN2
Permanent connection
C: Client network domain
TN:Transport Network provider domain
40
Provisioned
C2
C1
TN1
Permanent
connection
E-NNI
Switched
connection
TN2
C2
Permanent
connection
41
SC initiating domain
C1
TN1
UNI
TN2
E-NNI
Switched connection
C: Client network domain
TN:Transport Network provider domain
42
C2
UNI
43
44
DS1
X
3:3 DCS
45
DS3
X
3:1 DCS
SONET
X
Regen
SONET
X
3:1 DCS
SONET
X
3:3 DCS
DS1
Issues
Model specific to the technologies used in the NEs
Difficult to understand network topology without
understanding details of the NEs
Subject to differing interpretations of equipment
specifications/behaviors arising from natural language
description
Usage of different terminology; e.g., in doing a functional
decomposition, different specifiers may group
functionality in different ways but use the same term to
denote the functional block
46
47
48
49
DS3
Signal
DS3 payload
mapping into
C-3 Container
Multiplex
Section
Layer
VC-3 Path
overhead
insertion
Regenerator
Section Layer
Vertical
Conversion into STM-N
physical interface
STM-N
50
mux
DS1 Path
Connection
DS -1 Path Connection
DS -3 Path Trail
DS1 Line
Trail
DS -3 Path
Connection
DS -3 Line
Trail
STS -1 Trail
STS -1 Connection
3:3
DCS
SONET Line
Connection
SONET Line
Connection
Section
Trail
Section
Trail
Section
Conn
Section
Conn
Optical
Trail
STS -1
Connection
SONET
Line Trail
SONET
Line Trail
3:1
DCS
51
DS1 Line
Trail
DS -3 Path Connection
regen
Optical
Trail
DS1 Path
Connection
SONET
Line Conn
3:3
DCS
Section
Trail
Section
Conn
Optical
Trail
3:1
DCS
mux
Horizontal
subnetwork
53
link
Topological Entities
Points
Termination Connection Point (TCP): Any binding involving a termination function
source or sink
Connection Point (CP): Any binding involving an adaptation source or sink
Access Point (AP): Delimits a layer network
54
Payload
Payload
Trail
Network Connection
55
Payload
Adaptation Source
Converts client layer
characteristic information to a
form suitable for transport over a
trail in the server layer network
This is termed Adapted
Information
Adaptation Sink
Converts the adapted
information from the server layer
network to the client layer
characteristic information
56
Client Layer CI
Client Layer
Adapted Information
Trail
Server Layer CI
VC-3/DS3
Adaptation
VC-3 Trail
AP
VC-3 Trail
Termination
TCP
VC-3 Subnetworks
VC-3 SNC
STM-1 MS/VC-3
Adaptation
CP
AP
CP
STM-1 Trail
Adaptation
Trail Termination
TCP
57
STM-1 MS Trail
Termination
Etc.
VC-3 SNC
Key Observations
Each layer network has its own topology
NEs may have different neighbors in different layer
networks
NEs do not necessarily appear in all layer networks
NEs may perform different functions within a layer
network, or in different layer networks
58
Control Components
59
60
CP
Adaptation
Subnetwork
Trail Termination
TCP
SNC
SNP
Trail
SNP: Subnetwork Point
SNPP: SNP Pool
SNPP Link
61
SNC
62
Policy port
Config port
DA
LRM
CCC/
NCC
CC
PC
63
RC
TAP
TP
DA Discovery Agent
TAP Termination & Adaptation Performer
TP Traffic Policing Component
64
Monitor port
DA
LRM
CCC/
NCC
CC
PC
RC
TAP
TP
Call Controller
Responsible for providing a
service across the network
Orchestrates components to
meet service requested
Different domains can have
different policies
Invoked by Management
Request or by Signaling
messages
Interacts with peer Call
Controllers via Protocol
Controller
65
Monitor port
DA
LRM
CCC/
NCC
CC
PC
RC
TAP
TP
Connection Controller
Responsible for establishing
connections across a domain
Requests Route to use from
Routing Controller
Requests specific local link
resources from LRM
Interacts with peer Connection
Controllers via Protocol
Controller
66
Monitor port
DA
LRM
CCC/
NCC
CC
PC
RC
TAP
TP
Routing Controller
Responsible for providing paths
between two points in the
network
Maintains topology view
Paths are calculated to meet
service constraints
Signal type
Diversity
67
Monitor port
DA
LRM
CCC/
NCC
CC
PC
RC
TAP
TP
Protocol Controller(s)
Responsible for providing
protocol specific behavior
Can be separate per client
function, or a merged function
Monitor port
CCC/NCC and CC
CCC/
NCC
CC
PC
68
DA
LRM
RC
TAP
TP
Call Accept
Call Accept
Connection Indication
Path Computation
function in Routing
Component
NCC
CC
69
CC
CC
NCC
Identifiers
70
Categories of Identifiers
Management plane identifiers
Transport plane identifiers (G.805)
Identifiers for transport resources that are used by the
control plane
72
Identifier Spaces
MANAGEMENT PLANE (MP)
(e.g. CTP, TTP)
DCN
MCN/SCN addresses
UNI/E-NNI TRI
SNPP, SNP ID
DATA PLANE
(e.g., G.805 CP, TCP)
73
Node ID
74
75
76
77
78
RFC
RFC
IA
Rec.
RFC
RFC
RFC
RFC
RFC
IETF
79
IA
IA
OIF
Rec.
ITU-T
UNI
NE
NE
CALL
CONNECTIONS
80
UNI Call
Segment
NE
NE
E-NNI Call
Segment
UNI
Domain B
E-NNI
UNI Call
Segment
81
IETF base GMPLS signaling protocol RFCs Approved by IESG, published Jan. 03
RFC 3471, GMPLS Signaling Functional Description
RFC 3472, GMPLS CR-LDP Extensions
RFC 3473, GMPLS RSVP-TE Extensions
(aligned with G.7713.2 & G.7713.3) and IANA Code Point Assignments Approved
by IESG, published March 03
RFC 3474, IANA Assignments for GMPLS RSVP-TE Usage and Extensions for ASON
RFC 3475, IANA Assignments for GMPLS CR-LDP Usage and Extensions for ASON
RFC 3476, IANA Assignments for LDP, RSVP, and RSVP-TE Extensions for Optical UNI
Signaling
82
Updates UNI 1.0, but does not change UNI 1.0 functionality
Reflects subsequent developments in other standards bodies
Builds upon lessons learned from the OIFs multi-vendor interoperability event
conducted at OFC 2003
83
Base features
Support of Ethernet services (almost complete)
Support of G.709 (complete)
Enhanced security (complete)
Call/connection separation (complete)
Support of sub-STS1 granularity (complete)
84
85
Consistent
RFC3473 and
other base RFCs
Additionally specifies
detailed usage of
selected options in
protocols
Due to concerted effort, the signaling protocols are mostly the same!
Three new call-related objects, and some new C-Types associated with UNI and E-NNI
Need for usage of ResvTear/RevErr (no change to procedures if used)
86
Provider A
OIF
E-NNI
IETF
Provider B
Protocol
i/w
Provider C
Client
Client
87
IETF
UNI
RFC
RFC
RFC
RFC
3472
3473
3946
4203
RFC 4139
RFC 4208
88
Ethernet
callEthernet
call
completes
Client
SONET/SDH
call
OXC
UNI-C
Ethernet
call
progresses
OXC
Client
UNI-N
UNI-C
UNI-N
Ethernet
Ethernet
GFP
VCAT
Interlaye
r call
invoked
89
GFP
VCAT
UNI-N
UNI-N
SONET/SDH
connection
s
Ethernet
connection
Interlayer Signaling
Interlayer architecture enables business boundary between layers.
Service separation between layers is at interlayer NCC relationship
Note that VCAT is a separate layer
ETH NCC
ETH NCC
Layer boundary
VC-3 NCC
VC-3 NCC
Interlayer
Within Layer
90
91
Basics of IP Routing
IP routing protocol
Exchange of information between IP routers that allow them to
determine how to forward IP packets
There are different types of routing protocols
Distance Vector (RIP, IGRP)
Path Vector (BGP)
Link State (OSPF, IS-IS)
92
Node D
Node G
Node H
Node A
Node J
Node E
Node C
93
Node F
DB A Summary
DB B Summary
Node A
Node B
Topology
DB
Topology
DB
reliably flooded
94
C A
D
C A
2
NE
2
NE
4
1
NE
7
NE
1
NE
5
2
2
2
2
2
NE
3
NE
6
2
95
Disaster Recovery
Want timely information of whats available in the
network (nodes, link, spare capacity, etc)
96
97
Future work
PCE
98
ASON Routing
Routing Components
Monitor port
Policy port
Config port
RC
CCC/
NCC
CC
PC
CC - Connection Controller
RC - Routing Controller
LRM - Link Resource Manager
PC Protocol Controller
99
LRM
ASON Routing
OSPF
Topology
Database
IP router Peers
Shortest Path
Algorithm (Dijkstra)
G.7715 Compliant
Protocol
L1 Bearer
Topology
Control Plane
Source Route
Algorithm
Signaling
Data Plane
IP Forwarding
Table
SDH Path
Header
IP
Cross
Connec
t
Control Plane
Data Plane
SDH Path
100
ASON Routing
Some differences between IP and Transport Network Routing
Classic IP Routing
Distribution of Routing Always distributed
Protocol Entities
Domain-specific: may be
distributed or centralized
Path computation
Forwarding process
Forwarding
dependency
Looping
101
Transport Routing
ASON Routing
Specifications
102
103
ASON Routing
104
Capability
Usage
Characteristics
Signal Type
Mandatory
Optional
Link Weight
Mandatory
Optional
Resource Class
Mandatory
Optional
Local ConnectionType
Mandatory
Optional
Link Capacity
Mandatory
Optional
Link Availability
Optional
Optional
Diversity Support
Optional
Optional
Optional
Optional
Supported
105
Differences
Control plane and data plane topology may be different
Automated discovery of routing peers cannot be done based on SCN
topology data plane neighbors may not be neighbors in the SCN
106
Routing Implication
Must be able to separately identify the data plane entity
(link or node) from the routing controller
107
108
109
Assumes that any signal type can use the link, subject to
pure bandwidth availability
Does not take into account layering issues
110
OSPF and IS-IS have limited levels (see next slide for OSPF)
PNNI has richer hierarchy up to 104 theoretical levels
111
112
Level 1
RA.1
RA.3
Level 2
RA.2
RA.1.1
Level 3
RA.1.2
RA.2.2
RA.3
RA.2.1
113
IETF
Has begun work through analysis of ASON requirements and
evaluation of existing routing protocols
Some initial proposals for extensions are in progress
Will need review through OSPF and IS-IS groups
OIF
Has developed and tested prototype extensions to meet
ASON requirements
Working with IETF/ITU-T to extend the standards
114
115
Advertisement of TNA
TNA is OIFs terminology for client address
Reachability to TNA is advertised through OSPF prototype
extension
This supports a separate client namespace, in theory could be
non-IPv4
116
Routing Hierarchy
Currently not implemented but under study
Leaking of information up and down levels and protection
from looping are key elements
117
Domain A
Domain B
OIF UNI
NE
NE
NE
RC
Client
Device
NE
OIF UNI
RC
RC
SCN
Domain C
Carrier
Network
RC
RC
NE
NE
OIF UNI
118
1
Real domain
topology
2
3
Abstraction Models
1. Abstract node domain collapsed to a single
node; most scalable, least accurate
119
Abstract
topology
120
121
122
re
c
Di
Re
po
rt s
Supports
Directs
ts
123
cts
Control plane
re
Di
Reports
Supports
Directs
ts
Management plane
Reports
Transport plane
Adaptation
CTP
TTP
Subnetwork
Trail Termination
TCP
SNP
SNC
Link Connection
Transport entities
Adaptation function
Trail Termination function
CP: Connection point
TCP: Termination connection point
Management plane view
TTP: Trail Termination Point
CTP: Connection Termination Point
124
Trail
SNC
Management
Plane
NMS
ITU-T G.7718
EMS
EMS
EMS
OIF-CDR-0.10
GR-1110-CORE
ITU-T G.7718.1
MTNM
Control
Plane Transport
Plane
125
G.7718.1
G.7718
Network
Element
G.8080
G.7710
M.3010
126
Configuration management
Control plane resources
Identifiers, addresses, protocol parameters (signaling & routing)
Routing areas
RA hierarchies, (dis) aggregation, assignment of Cp resources
Policy
Fault management
Control plane components, resource/connection/call (service),
Performance management
Control plane components
Accounting management
Usage and call details record
127
TMF
TMF
TMF
TMF
Scope:
Limited to retrieval of Control Plane resources, retrieval of network
topology and end-to-end Call/Connection management (provisioning
of SPCs)
128
129
130
Interoperability Demonstrations
Objectives / Goals
OIF Perspective
Member evaluation, validation, proof of concept of current OIF draft
specifications & IA for interoperable network solutions
Feedback assessment from multi-vendor testing environment to
standardization/specification work
Carrier Perspective
Early adoption, evaluation, of interoperability testing results
demonstrated in multi-vendor environment.
Feedback to vendor community on early implementations and
integrations based on practical experiences and lessons learned
Industry Perspective
Showcase OIF contributions, build market awareness of emerging
technologies, services and networking solutions.
Public forums (Optical conference & exhibitions) utilized
131
Interoperability
Tests & demonstrations
Standards
Specifications
OIF
ITU-T
IETF
132
Field trials
Carrier
sites
OIF
Feedback
Carrier A
Domain
Carrier B
Domain
NE
Ethernet
UNI-C
OIF E-NNI
OIF E-NNI
OIF UNI
NE
Ethernet
Client
Carrier C
Domain
NE
NE
SDH
UNI-N
OIF UNI
NE
NE
Ethernet
UNI-N
UNI-C
133
134
Interoperability Demonstrations
Global Test Network Topology
USA
Avici
Ciena
Cisco
AT&T
Alcatel
Ciena
Cisco
Fujitsu
Lucent
Mahi
Nortel
Sycamore
Tellabs
Asia
Deutsche
Telekom
Alcatel
Ciena
Cisco
Marconi
Lucent
France
Telecom
Avici
Marconi
Sycamore
Verizon
135
Europe
Telecom
Italia
Marconi
Huawei
Lambda OS
Avici
Cisco
NTT
Avici
Fujitsu
Sycamore
Ciena
Huawei
China
Telecom
Middletow
n, NJ-USA
Beijing,
China
Berlin,
Germany
Torino,Italy
SuperComm 2005
booth
136
Musashino,
Japan
137
transport networks
7 participating carrier labs around the world: China,
Japan, France, Germany, Italy and USA
Public demonstration at ECOC2007, Sept 16 20th, 2007:
ECOC2007 Workshop on Global Interoperability in MultiDomain and Multi-Layer ASON/GMPLS Networks
ECOC2007 exhibition: Live demonstration of the OIF
Worldwide Interoperability Test results
ECOC2007 accompany program: Lab tours to DT premises,
demonstrating live the ASON/GMPLS functions of the OIF
Worldwide Test Network, the MUPBED European scale
network and enabling hands on real telecom world for
the visitors
138
139
SONET
Path 13
SONET
140
Site 3
Core Technologies
OTN Control Plane (E-NNI, I-NNI)
OTN Mgmt Plane (EMS/NMS SPC support)
Site 2
Path 1Site 1 2
SONET
A
SONET
Path 13
SONET
141
Path 23
Site 3
142
200
200 Mb/s
Mb/sec
160
120
100 Mb/s
80
40
19 Mar
(Th)
143
20 Mar
(F)
21 Mar
(Sa)
22 Mar
(Su)
23 Mar
(M)
24 Mar
(Tu)
25 Mar
(W)
Source: EMC
Weekdays
Schedule\Path
Path 1-2
Path 1-3
Path 2-3
Schedule\Path
Path 1-2
Path 1-3
Path 2-3
8 am 5pm
200M
100M
50M
8 am 5pm
50M
50M
50M
6pm 11pm
300M
200M
100M
6pm 11pm
50M
50M
50M
12am 7am
50M
500M
500M
12am 7am
10M
10M
10M
Site 2
Core Technologies
NG-SONET/SDH GFP/VCAT/LCAS
OTN Control Plane (E-NNI, I-NNI)
OTN Mgmt Plane (EMS/NMS w/scheduling support)
144
Site 1
Path 12
GbE
Path 23
GbE
Path 13
GbE
Site 3
Core Technologies
OTN
Site 2
UNI
Site 1
Path 2-3
GbE
Path 1-3
145
GbE
Path 1-2
UNI
GbE
Site 3
NG-OSS
Inventory
Customer
Assignments
Facility
Service Accountin
g
Assuranc
e
&
Security
Fault
Correlations Billing
Exceptions Admission
Control
Resource
Access Cntl
Transport Network
146
Transport Network
Core Technologies
OTN Control Plane (I-NNI, E-NNI)
OTN Mgmt Plane (EMS/OSS update)
Site 2
Path 1Site 1 2
SONET
147
SONET
Path 13
SONET
Path 23
Site 3
148
149
150
151
152
153
Thank you!!
Q&A
Hans-Martin.Foisel@t-systems.com
154
www.oiforum.com
Backup
Glossary
156
OIF Documents
OIF presentation and newsletters
www.oiforum.com
http://www.oiforum.com/public/meetOIW050806.html
http://www.oiforum.com/public/meetOIW073106testbeds.html
http://www.oiforum.com/public/meetOIW101606.html
157
ITU-T Recommendations
Accessibility Information
158
159
August 05 revision
ITU-T G.7715/Y.1706 - Architecture and Requirements for Routing in
the Automatic Switched Optical Networks, July 2002
ITU-T G.7715.1/Y.1706 - ASON Routing Architecture and requirements
for Link State Protocols, Feb. 04
ITU-T G.7712/Y.1703 - Architecture and specification of data
communication network*, March 03
ITU-T T G.7716 - Control Plane Initialization, Reconfiguration, and
Recovery, target Consent Nov. 06
http://www.amazon.com/gp/product/0890065780/ref=sib_rdr_dp/103-2003697-9480609
?%5Fencoding=UTF8&me=ATVPDKIKX0DER&no=283155&st=books&n=283155
http://www.amazon.com/gp/product/0890069999/ref=dp_return_1/103-20036
97-9480609?%5Fencoding=UTF8&n=283155&s=books
http://www.amazon.com/gp/product/0470091231/ref=sib_rdr_dp/103-20036
97-9480609?%5Fencoding=UTF8&me=ATVPDKIKX0DER&no=283155&st=books&n=28
3155
http://www.amazon.com/gp/product/0387240624/qid=1147161139/sr=1-1/ref=
sr_1_1/103-2003697-9480609?s=
books&v=glance&n=283155
160
161
Glossary
ACDR
AMA
ASON
AP
API
BAF
BoD
CC
CCC
CDR
CORBA
CP
Cp
DA
DCM
ECF
EMF
EMS
E-NNI
ETF
FCAPS
162
FTP
IA
I-NNI
LCAS
LRM
MIB
Mp
NCC
NE
NMS
MLRA
MLSNPP
ASCII CDR
Automatic message accounting
Automatically switched optical network
Access point
Application programming interface
Billing AMA Format
Bandwidth on Demand
Connection controller
Calling/called call controller
Call detail record
Common object request broker architecture
Connection point
Control plane
Discovery agent
Distributed Call and Connection Mngmt
Equipment control function
Equipment management function
Element management system
External NNI
Equipment transport function
Fault, Configuration, Accounting,
Performance, Security
File transfer protocol
Implementation agreement
Internal NNI
Link capacity adjustment scheme
Link resource manager
Management information base
Management plane
Network call controller
Network element
Network management system
Multi-layer routing area
Multi-layer SNPP
MTNM
NNI
OH
OSF
OSS
OTN
PC
RA
RC
SC
SCN
SNC
SPC
SNP
SNPP
SRG
STM
TAF
TAP
TCE
TCP
TNA
TP
Tp
TTP
UNI
UML
VC
VCAT
VLAN
WSF
XCDR
XML