Transcript PowerPoint プレゼンテーション

APNOMS2003
Standardization of B-PON OSS-IF
- Report of FSAN OAM-WG activities APNOMS2003 in Fukuoka
October 3rd, 2003
NTT
Access Network Service Systems
Laboratories
Kenji Nakanishi
[email protected]
NTT-AT
Transport Network Division
Tatsuhiko Yoshida
[email protected]
(C)2003 NTT
1
Intents of standardization
APNOMS2003
Internationally standardized specifications
( ex. ITU-T Recommendations )
Guarantee of interoperability
Vendors can sell equipments
to any operators
reduction of risk
Operators can purchase equipments
from any vendors
reduction of investment
-Sharing development resources
-Market expansion by globalization
Cost reduction in a worldwide scale
- describing principles
Useful OSS-IF standards
- specialized for a particular system
(C)2003 NTT
2
Basic principle of PON
Downstream :
- OLT distributes all packets to every ONU
- Each ONU extracts only the packet addressed to itself.
APNOMS2003
NMS
OSS-IF
UNI
Upstream :
- OLT assigns the transmitting timing of each ONU.
- Each ONU transmits its packets according to the timing.
ONU#1
ONU#N
OLT
Optical splitter
(- 32 branches)
ONU#2
Optical fiber
EMS
PON
IF
Interface
conversion
multiplex
SNI
SNI
IF
ONU:Optical Network Unit
OLT Optical Line Terminal
SNI:Service Node Interface
UNI:User Network Interface
(C)2003 NTT
3
International standardizing bodies
Public organization
Private organization
United Nations
With
secretariat
ITU (International
Telecommunication Union)
TTC
Japan
Liaison
ETSI
Europe
Liaison
IETF
IEEE
ITU-D
ITU-R
ITU-T
ITU Telecommunication
standardization sector
Liaison
APNOMS2003
ATM-F
Liaison
ADSL-F
Without
secretariat
Contribution
ANSI
（T1) USA
TMF
FSAN
(C)2003 NTT
4
Participants to FSAN
Eirecom
APNOMS2003
Telia
Verizon
KT
BT
NTT
Bell Canada
KPN
Bezeq
DTAG
FT
SwissCom
TI
Chunghwa
SingTel
Telstra
Qwest
Telefonica
BellSouth
SBC
Malta
21 operators and 29 venders, as of Sep. 2003
AFC
Agere
Ericsson
FlexLight
Intel
Lucent
Nortel
OFN / Oki
ST Microelectronics
Alcatel
Broadcom BroadLight CISCO
Fujitsu
Hitachi
Iamba
Infineon
Marconi
Mitsubishi / Paceon
Motorola
Optical Solutions
Quantum Bridge
Samsung Terawave Vinci
Zonu
Entrisphere
INOVIA/ECI
NEC
(C)2003 NTT
5
Organization of FSAN
APNOMS2003
Board
Management Committee
Deployment Group
OAN-WG
OAM-WG
FS-VDSL Committee
( Optical Access
Network )
( Operation and
Maintenance )
(Full Service –VDSL)
Chairperson:
Chairperson:
Yoichi Maeda (NTT) Linda Garbanati (SBC)
Chairperson:
Don Clarke (BT)
WG : Working Group
(C)2003 NTT
6
OSS-IF of B-PON
Profile Object
Repository
Privileged
User
Other
OMSs
Data
Warehous
e
Secure File
Server
NT
NT
NT
Supplier
Managemen
t System
Non
Real-time
NNI
ONU
ONU
ONU
ONT
ONT
ONT
OMS
Notification
Service
OMS
Naming
Service
Real-time
SNI
ODN
UNI
APNOMS2003
OLT
BPON Network Elements
(C)2003 NTT
7
B-PON OSS-IF Recommendations
APNOMS2003
・The specifications are based on UML (Unified Modeling Language)
Managed Entity
(ME) definitions
NE view
ME definition
<Q.834.1>
Protocol independent
model
Protocol specified
model
NW view
ME definition
<Q.834.2>
Management model
based on UML
description
<Q.834.3>
CORBA specified
Management model
<Q.834.4>
Apr. 2001 Approved
May. 2004 To be revised
- Unified to combined view
- Addition of DBA functions
Dec. 2001 Approved
Oct. 2003 To be revised
- Addition of DBA functions
Jul. 2003 Approved
Oct. 2003 To be amended
- Addition of DBA functions
(C)2003 NTT
8
Combining NE view and NW view
NE view is useful in case
of maintenance and testing
APNOMS2003
NW view is convenient
in case of provisioning
FSAN proposed a new view that combines the both views
-The existing Recommendations are divided into NE view (Q.834.1)
and NW view (Q.834.2)
-The existing Q.834.1 and Q.834.2 realize a combined view in deed
by relating managed entities of both views using pointers
-A revised Q.834.1 will integrate the existing Q.834.1 and Q.834.2,
and will combine NE view and NW view in deed as well as in name.
(C)2003 NTT
9
Combined view model (PON layer)
APNOMS2003
ONT/ONU #1
OLT
ONT/ONU #2
APON LND
APON
Subnetwork
ONT
#1
NW
View
APON Link (Downstream)
OLT
APON
Subnetwork
APON
Subnetwork
APON Link (Upstream)
ONT
#2
APON Topological Link End
ONT/ONU #1
NE
View
OLT
PhysicalPathTTP
ONT/ONU #2
APON NetworkTTP
APON NetworkCTP
APON Trail
APON Link Connection
(C)2003 NTT
10
Combined view model (VP layer)
APNOMS2003
ONT/ONU #1
OLT
ONT/ONU #2
VP LND
VP
Subnetwork
NW
View
ONT
#1
VP Topological Link End
VP
Subnetwork
OLT
VP
Subnetwork
ONT
#2
ONT/ONU #1
NE
View
tcAdaptor
PhysicalPathTTP
ONT/ONU #2
VP NetworkTTP
VP NetworkCTP
VP Trail
OLT
VP Link Connection
(C)2003 NTT
11
Dynamic Bandwidth Assignment
APNOMS2003
DBA: Dynamic Bandwidth Assignment
- Adopting to upstream direction of PON.
- Sharing bandwidth between optical splitter and OLT.
- ONU can transmit upstream packets as much as the bandwidth permits
ONU-A
ONU-B
Optical splitter
OLT
ONU-C
ONU-D
Shared
bandwidth
Occupied
bandwidth
(C)2003 NTT
12
NW view for DBA
APNOMS2003
ONT/ONU #1
OLT
ONT/ONU #2
VP LND
VP Logical Link
VP
Subnetwork
ONT
#1
VP Topological Link
NW
View
OLT
VP
Subnetwork
VP Logical Link
VP
Subnetwork
ONT
#2
VP Topological Link
VP Logical Link
VP Topological Link End
TCONT (a subclass of Logical Link End)
VP NetworkCTP
VP Link Connection
(C)2003 NTT
13
NE view for DBA
APNOMS2003
- Some managed entities exist only in ONU for arranging packets.
- Priority Queue stores VP packets according to their priority.
- Output from Priority Queue will be pressured by WRR if needed,
then accommodated in T-CONT buffer in order by HOL.
ONT / ONU
VPCTP
PQPointerforUpstream
#1
Priority Queue #1
#2
#3
#4
#7
TC
HOL T-CONT Buffer #A
T-CONT Buffer #A
Priority Queue #2
Priority Queue #3
WRR
#5
#6
OLT
Traffic
scheduler
Priority Queue #4
HOL T-CONT Buffer #B
T-CONT Buffer #B
Priority Queue #5
WRR: Weighted Round Robin HOL: Head Of the Line
(C)2003 NTT
14
ME relationship diagram
ONT/ONU
NEAssignmentPtr.
TCONTbuffer
T-CONTBufferPtr.
LogicalLinkFPtr.
Zend
T-CONT
(Subclass of
logicalLinkEnd)
Aend
OLT
LogicalLinkFPtr.
T-CONT
(Subclass of
logicalLinkEnd)
VPLogicalLink
networkCTPsInLin
kEndList
TrafficScheduler
TCONTbuffer
networkCTPsInLin
kEndList
TrafficShedulerPtr.
PriorityQueue
PQPtrForUpstream
NEAssignmentPtr.
VPCTP
ZNetworkCTPPtr.
VPNetworkCTP
T-CONTBuffer
PMHistoryData
ANetworkCTPPtr.
VPLinkConnection
VPNetworkCTP
NEAssignmentPtr.
tcAdaptorPtr.
VPCTP
tcAdaptorPtr.
TXAdaptorDbaFairness
PMHistoryData
tcAdaptor
ZNetworkTTPPtr.
PhysicalPathTPFPtr.
NEAssignmentPtr.
APONTTP
APONNetworkTTP
ConnectivyPointerLis
t
APONCTP
APNOMS2003
ANetworkTTPPtr.
APONTrail
ZNetworkCTPPtr.
APONNetworkCTP
PhysicalPathTPFPtr.
NEAssignmentPtr.
APONNetworkTTP
ANetworkCTPPtr.
APONNetworkCTP
APONLinkConnection
tcAdaptor
NEAssignmentPtr.
APONTTP
ConnectivyPointerList
APONCTP
NEAssignmentPtr.
ONTTCAdaptorIdList
OLTTCAdaptorId
APONLink
APONtopLinkEnd
PhysicalPathTP
ZendList
Aend
APONLink
APONtopLinkEnd
PhysicalPathTP
(C)2003 NTT
15
UML description
APNOMS2003
UML:Unified Modeling Language
Suitable description of object-oriented systems and software development
Use case diagram
Relationship between OSS and its external
environments (High level requirements for OSS)
Sequence diagram Time ordered event description for each use case
Class diagram
Detailed relationship between managed entities
Q.834.3 is the first ITU-T Recommendation that
describes scenarios using UML strictly
(C)2003 NTT
16
Advantages of UML
APNOMS2003
Modeling is necessary for
- key component of developing systems
- omitting non-essential details, reducing complexity and facilitating
understanding
- offering multiple views with separation of concerns
UML helps to design models with
- intuitional and intelligible diagrams
- minimum and plain notations
(C)2003 NTT
17
Example of use case diagram
APNOMS2003
communicates
Use case
Process Incoming
communicates NE Events
communicates
BPON NE
NE Synchronisation
communicates
communicates
includes
Autodiscover NEs
and PlugInUnits
Publish BPON Event
Register OLT
communicates
communicates
Range ONT/ONU
Actor
communicates
External Event
Channel
OMS or Operator
Installation
[From ITU-T Q.834.3 Figure 5-8]
(C)2003 NTT
18
Example of sequence diagram
: Event
Screener
:
NESynchroniser
get&compare( )
: Discoverer
getNodeDetails( )
: Management
Model Maintainer
APNOMS2003
: EventSupplier
Class
queries( :) BPON NE
)
getEquipmentHolderList(queries(
)
getPlugInUnits( )
queries( )
get Software( )
queries( )
get managed entity( )
preparesMECreation/DeletionRecord( )
As needed.
notify( )
Event Triggered NE Synchronisation Sequence Diagram
[From ITU-T Q.834.3 Figure 5(C)200359]
NTT
19
Example of class diagram
APNOMS2003
Event Screener
queues to
Event Queue
sends events
triggers
Event
Class name
Attributes
operations
reads
OLT DCN
Restore
ONT or ONU
ONT or ONU
Ranging
Management Model Maintainer
Re-ranged
BPON NE
get details
queries()
and updates
queries
NESynchroniser
Discoverer
get&compare()
notifyInventoryMECreation()
getNodeDetails()
get details
getEquipmentHolderList()
EventSup
sends creation/deletion
notifyInventoryMEDeletion()
plier
events
notifyNewRegistration()
getPlugInUnits()
synchNE()
get Software()
notify()
preparesMECreation/DeletionRecord()
getEquipmentVersion()
wait()
triggers
scheduledSynchNE()
updates
getValue()
ActivityCompleti
BPON NE
NE resynch
onLog
triggers
Registrar
schedules activity
Scheduler
storeRecord()
viewRecords()
registers
Privileged User
NE Synchronisation Class Diagram
Operator
[From ITU-T Q.834.3 Figure 558]
(C)2003 NTT
20
CORBA framework in ITU-T
APNOMS2003
-A first draft of “Framework for corba-based telecommunications
management interfaces“ were proposed in August 1999 for the
purpose of adapting CORBA into Q interface.
-A fine grain model of the draft was approved in January 2001 as
X.780, and a coarse grain model was approved in July 2001as
X.780.1.
Q
BML
SML
NML
EML
OS
Q
OS
CORBA
CORBA proposed
Q
proposed
Q
CORBA
Q
OS
proposed OS
CORBA
proposed
CORBA
Q
proposed
Q
CORBA
Q
OS
proposed OS
CORBA
proposed
Q
CORBA
proposed
Q
OS
OS
CORBA
proposed
Q
NEL
Q
CORBA
proposed
CORBA
proposed
NE
OS
SNMP ?
SML X
CMIP
CORBA
EDI
OS
tML is
added
recentl
y
NE
(C)2003 NTT
21
CORBA framework and Q.834.4
Few
Simple
Easy
Q.834.4
model
Number of instances
Design
Implementation
Coarse grain
model (X.780.1)
APNOMS2003
Many
Complex
Difficult
Fine grain
model
(X.780)
-Q.834.4 specifies CORBA interface for PON, and X.780 and X.780.1 describe
CORBA framework in ITU-T.
- Q.834.4 model is based on service and system management, and can
implement more easier than CORBA framework models which are based on
network resources.
Q.834.4 refers X.780 and X.781, and adds some
general interface specifications using its own model.
(C)2003 NTT
22
OSS-IF interoperability test
APNOMS2003
-FSAN OAM-WG plans interoperability test between operator’s NMS
and vendor’s EMS based on Q.834.4.
-2 operators and 5 vendors will participate in the test.
-The test result between Mitsubishi and NTT is presented at another
session of this conference.
NMS
(NTT)
NMS
(SBC)
To be presented at
this conference
EMS
(Telawave)
EMS
(QB)
EMS
(Mitsunishi)
EMS
(NEC)
EMS
(Iamba)
B-PON
B-PON
B-PON
B-PON
B-PON
(C)2003 NTT
23
Future plan of FSAN OAM-WG
APNOMS2003
-Proposing revision and amendment of Q.834
series reflecting DBA function
-Interoperability test of OSS-IF based on Q.834.4
- The remaining issues should be completed in this year
- The WG meeting will go into recess in the next year
- The meeting will be reactivated when FSAN members
require
(C)2003 NTT
24
APNOMS2003
Thank you
The beckoning cat, Maneki Neko,
brings Luck.
(C)2003 NTT
25