Standardization%20of%20B-PON%20OSS-IF

1
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 nakanisi_at_ansl.ntt.co.
jp
NTT-AT Transport Network Division Tatsuhiko
Yoshida tyoshida_at_trans.ntt-at.co.jp
2
Intents of standardization
Internationally standardized specifications ( ex.
ITU-T Recommendations )
Guarantee of interoperability
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
• specialized for a particular system

Useful OSS-IF standards
3
Basic principle of PON

• Downstream
• OLT distributes all packets to every ONU
• Each ONU extracts only the packet addressed to
  itself. Upstream
• OLT assigns the transmitting timing of each ONU.
• Each ONU transmits its packets according to the
  timing.

NMS
OSS-IF
EMS
UNI
OLT
ONU1
Optical splitter (- 32 branches)
SNI
Interface conversion
PON IF
SNI IF
ONU2
multiplex
Optical fiber
ONUOptical Network Unit OLT Optical Line
Terminal SNIService Node Interface UNIUser
Network Interface
ONUN
4
International standardizing bodies
Public organization
Private organization
United Nations
With secretariat
ITU (International Telecommunication Union)
IETF
IEEE
TMF
ADSL-F
ATM-F
ITU-T
ITU Telecommunication standardization sector
Liaison
Without secretariat
Liaison
Contribution
Liaison
Liaison
FSAN
TTC
ANSI (T1)
ETSI
Japan
USA
Europe
5
Participants to FSAN
21 operators and 29 venders, as of Sep. 2003
AFC Agere Alcatel Broadcom BroadLight CISCO E
ntrisphere Ericsson FlexLight Fujitsu Hitachi
Iamba Infineon INOVIA/ECI Intel
Lucent Marconi Mitsubishi / Paceon Motorola NEC
Nortel OFN / Oki Optical Solutions Quantum
Bridge ST Microelectronics Samsung Terawave
Vinci Zonu
6
Organization of FSAN
Board
Management Committee Deployment Group
OAM-WG ( Operation and Maintenance )
OAN-WG ( Optical Access Network )
FS-VDSL Committee (Full Service VDSL)
Chairperson Linda Garbanati (SBC)
Chairperson Don Clarke (BT)
Chairperson Yoichi Maeda (NTT)
WG Working Group
7
OSS-IF of B-PON
Profile Object Repository
Other OMSs
OMS Notification Service
Privileged User
Data Warehouse
OMS Naming Service
Supplier Management System
Secure File Server
Non Real-time
Real-time
NNI
ONU
NT
ONU
NT
ONU
NT
SNI
OLT
ODN
UNI
ONT
ONT
ONT
BPON Network Elements
8
B-PON OSS-IF Recommendations
The specifications are based on UML (Unified
Modeling Language)
Apr. 2001 Approved May. 2004 To be revised -
Unified to combined view - Addition of DBA
functions
NW view ME definition ltQ.834.2gt
NE view ME definition ltQ.834.1gt
Managed Entity (ME) definitions
Management model based on UML description ltQ.834.3
gt
Dec. 2001 Approved Oct. 2003 To be revised -
Addition of DBA functions
Protocol independent model
CORBA specified Management model ltQ.834.4gt
Protocol specified model
Jul. 2003 Approved Oct. 2003 To be amended -
Addition of DBA functions
9
Combining NE view and NW view
NE view is useful in case of maintenance and
testing
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.

10
Combined view model (PON layer)
ONT/ONU 1
OLT
ONT/ONU 2
APON LND
APON Subnetwork
APON Subnetwork
ONT 1
APON Link (Downstream)
NW View
OLT
APON Link (Upstream)
APON Subnetwork
ONT 2
APON Topological Link End
ONT/ONU 1
OLT
NE View
ONT/ONU 2
PhysicalPathTTP
APON NetworkTTP
APON NetworkCTP
APON Link Connection
APON Trail
11
Combined view model (VP layer)
ONT/ONU 1
OLT
ONT/ONU 2
VP LND
VP Subnetwork
VP Subnetwork
ONT 1
VP Topological Link (Bi-directional)
OLT
NW View
VP Topological Link End
VP Topological Link (Bi-directional)
VP Subnetwork
ONT 2
ONT/ONU 1
OLT
NE View
tcAdaptor
ONT/ONU 2
PhysicalPathTTP
VP NetworkTTP
VP NetworkCTP
VP Trail
VP Link Connection
12
Dynamic Bandwidth Assignment

• 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
13
NW view for DBA
ONT/ONU 1
OLT
ONT/ONU 2
VP LND
VP Topological Link
VP Subnetwork
VP Subnetwork
ONT 1
OLT
VP Logical Link
NW View
VP Topological Link
VP Subnetwork
ONT 2
VP Logical Link
VP Logical Link
VP Topological Link End
VP NetworkCTP
VP Link Connection
TCONT (a subclass of Logical Link End)
14
NE view for DBA

• 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
OLT
VPCTP
TC
PQPointerforUpstream
1
Priority Queue 1
T-CONT Buffer A
T-CONT Buffer A
2
HOL
Priority Queue 2
3
4
Priority Queue 3
Traffic scheduler
WRR
5
Priority Queue 4
T-CONT Buffer B
6
T-CONT Buffer B
HOL
7
Priority Queue 5
WRR Weighted Round Robin HOL Head Of the Line
15
ME relationship diagram
ONT/ONU
OLT
Zend
Aend
LogicalLinkFPtr.
LogicalLinkFPtr.
NEAssignmentPtr.
T-CONT (Subclass of logicalLinkEnd)
TCONTbuffer
VPLogicalLink
TCONTbuffer
T-CONT (Subclass of logicalLinkEnd)
T-CONTBufferPtr.
networkCTPsInLinkEndList
TrafficScheduler
networkCTPsInLinkEndList
T-CONTBuffer PMHistoryData
TrafficShedulerPtr.
PriorityQueue
ANetworkCTPPtr.
ZNetworkCTPPtr.
PQPtrForUpstream
NEAssignmentPtr.
VPNetworkCTP
VPNetworkCTP
VPLinkConnection
VPCTP
VPCTP
NEAssignmentPtr.
tcAdaptorPtr.
tcAdaptorPtr.
TXAdaptorDbaFairness PMHistoryData
tcAdaptor
tcAdaptor
PhysicalPathTPFPtr.
ANetworkTTPPtr.
ZNetworkTTPPtr.
PhysicalPathTPFPtr.
NEAssignmentPtr.
NEAssignmentPtr.
APONTTP
APONNetworkTTP
APONTTP
APONNetworkTTP
APONTrail
ConnectivyPointerList
ConnectivyPointerList
ANetworkCTPPtr.
ZNetworkCTPPtr.
APONCTP
APONNetworkCTP
APONCTP
APONNetworkCTP
APONLinkConnection
NEAssignmentPtr.
NEAssignmentPtr.
OLTTCAdaptorId
ONTTCAdaptorIdList
APONLink
APONtopLinkEnd
APONtopLinkEnd
Aend
ZendList
PhysicalPathTP
PhysicalPathTP
APONLink
16
UML description
UMLUnified Modeling Language Suitable
description of object-oriented systems and
software development
Relationship between OSS and its external
environments (High level requirements for OSS)
Use case diagram
Sequence diagram
Time ordered event description for each use case
Detailed relationship between managed entities
Class diagram
Q.834.3 is the first ITU-T Recommendation that
describes scenarios using UML strictly
17
Advantages of UML
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
18
Example of use case diagram
Use case
Actor
Installation
From ITU-T Q.834.3 Figure 5-8
19
Example of sequence diagram
Class
Event Triggered NE Synchronisation Sequence
Diagram
From ITU-T Q.834.3 Figure 5-59
20
Example of class diagram
Class name
Attributes
operations
NE Synchronisation Class Diagram
From ITU-T Q.834.3 Figure 5-58
21
CORBA framework in ITU-T

• 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.

22
CORBA framework and Q.834.4
Few Simple Easy
Number of instances Design Implementation
Many Complex Difficult
Coarse grain model (X.780.1)
Fine grain model (X.780)
Q.834.4 model

• 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.
23
OSS-IF interoperability test

• FSAN OAM-WG plans interoperability test between
  operators NMS and vendors 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
24
Future plan of FSAN OAM-WG

• 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

25
Thank you
The beckoning cat, Maneki Neko, brings Luck.