(C)2003 NTT1

APNOMS2003

Standardization of B-PON Standardization of B-PON

OSS-IFOSS-IF

- Report of FSAN OAM-WG - Report of FSAN OAM-WG

activities -activities -NTT Access Network Service Systems

LaboratoriesKenji Nakanishi

nakanisi@ansl.ntt.co.jp

NTT-ATTransport Network Division

Tatsuhiko Yoshidatyoshida@trans.ntt-at.co.jp

APNOMS2003 in FukuokaAPNOMS2003 in FukuokaOctober 3October 3rdrd, 2003, 2003

(C)2003 NTT2

APNOMS2003Intents of standardizationIntents of standardization

Internationally standardized specifications( ex. ITU-T Recommendations )

Internationally standardized specifications( ex. ITU-T Recommendations )

Cost reduction in a worldwide scaleCost reduction in a worldwide scale

Operators can purchase equipments from any vendors reduction of investment

Operators can purchase equipments from any vendors reduction of investment

-Sharing development resources-Market expansion by globalization

Vendors can sell equipments to any operators reduction of risk

Vendors can sell equipments to any operators reduction of risk

Guarantee of interoperability

- describing principles- specialized for a particular system

Useful OSS-IF standards

(C)2003 NTT3

APNOMS2003Basic principle of PON Basic principle of PON

Optical splitter (- 32 branches)

Optical fiber

PON IF

Interface conversion

multiplex

ONU:Optical Network UnitOLT Optical Line TerminalSNI:Service Node InterfaceUNI:User Network Interface

OLT

SNI

ONU#1

ONU#2

ONU#N

UNI

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.

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.

SNI IF

EMSEMS

NMSNMS

OSS-IF

(C)2003 NTT4

APNOMS2003International standardizing bodiesInternational standardizing bodiesPublic organization

United Nations

ITU (International Telecommunication Union)

ITU-DITU-R

ITU Telecommunication standardization sector

ITU-T

TTCETSI ANSI

（ T1)JapanEurope

USA

With secretariat

IEEE IETFTMF

ATM-F ADSL-F

Liaison

Without secretariat

FSAN

Private organization

LiaisonLiaison Contribution

Liaison

(C)2003 NTT5

APNOMS2003Participants to FSANParticipants to FSAN

21 operators and 29 venders, as of Sep. 2003

AFC Agere Alcatel Broadcom BroadLight CISCO Entrisphere Ericsson FlexLight Fujitsu Hitachi Iamba Infineon INOVIA/ECI Intel Lucent Marconi Mitsubishi / Paceon Motorola NECNortel OFN / Oki Optical Solutions Quantum Bridge ST Microelectronics Samsung Terawave Vinci Zonu

NTTKT

SingTel

Telstra

BellSouth

Bell Canada

SBC

Verizon

Qwest

ChunghwaBezeq

FT

BT

DTAG

TI

Eirecom

KPN

Telia

Malta

Telefonica

SwissCom

(C)2003 NTT6

APNOMS2003Organization of FSANOrganization of FSAN

WG : Working Group

Board

OAN-WG( Optical Access

Network )

OAM-WG( Operation and Maintenance )

Management Committee

Deployment Group

FS-VDSL Committee

(Full Service –VDSL)

Chairperson:Linda Garbanati (SBC)

Chairperson:Don Clarke (BT)

Chairperson: Yoichi Maeda (NTT)

(C)2003 NTT7

APNOMS2003

ONU

UNI

BPON Network Elements

NNISNI

Real-time

OSS-IF of B-PONOSS-IF of B-PON

ONU

ONTONT

NT NT

OLTODNONU

ONT

NT

Secure File Server

Supplier Managemen

t System

Data Warehous

e

Privileged User

Profile ObjectRepository

Other OMSs OMS

Notification Service

OMS Naming Service

Non Real-time

(C)2003 NTT8

APNOMS2003B-PON OSS-IF RecommendationsB-PON OSS-IF Recommendations

NE viewME definition<Q.834.1>

NW view ME definition<Q.834.2>

Management model based on UML

description<Q.834.3>

Management model based on UML

description<Q.834.3>

Protocol independent model

Protocol specified model

Managed Entity (ME) definitions

・ The specifications are based on UML (Unified Modeling Language)

Apr. 2001 　 ApprovedMay. 2004 　 To be revised - Unified to combined view - Addition of DBA functions

Jul. 2003 ApprovedOct. 2003 　 To be amended - Addition of DBA functions

Dec. 2001 　 ApprovedOct. 2003 　 To be revised - Addition of DBA functions

CORBA specified Management model

<Q.834.4>

CORBA specified Management model

<Q.834.4>

(C)2003 NTT9

APNOMS2003Combining NE view and NW viewCombining NE view and NW view

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.

NW view is convenient in case of provisioning

NE view is useful in case of maintenance and testing

(C)2003 NTT10

APNOMS2003

APON NetworkCTPAPON NetworkTTP APON Link ConnectionAPON Trail

APONSubnetwork

APONSubnetwork

APON LND

APONSubnetwork

APON Link (Upstream)

APON Link (Downstream)

ONT#1

ONT#2

OLT

ONT/ONU #1ONT/ONU #1

OLTOLT

ONT/ONU #2ONT/ONU #2

ONT/ONU #1ONT/ONU #1

OLTOLT

ONT/ONU #2ONT/ONU #2

NEView

NWView

PhysicalPathTTP

APON Topological Link End

Combined view model (PON layer)Combined view model (PON layer)

(C)2003 NTT11

APNOMS2003

VP NetworkCTPVP NetworkTTPVP Link ConnectionVP Trail

VP Topological Link (Bi-directional)

VP Topological Link (Bi-directional)

VPSubnetwork

VPSubnetwork

VPSubnetwork

ONT#1

ONT#2

OLT

ONT/ONU #1ONT/ONU #1

OLTOLT

ONT/ONU #2ONT/ONU #2

ONT/ONU #1ONT/ONU #1

OLTOLT

ONT/ONU #2ONT/ONU #2

NEView

NWView

PhysicalPathTTPtcAdaptor

Combined view model (VP layer)Combined view model (VP layer)

VP LND

VP Topological Link End

(C)2003 NTT12

APNOMS2003Dynamic Bandwidth AssignmentDynamic 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

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

OLT

ONU-A

ONU-B

ONU-C

ONU-D Shared bandwidth

Occupied bandwidth

Optical splitter

(C)2003 NTT13

APNOMS2003

VPSubnetwork

VPSubnetwork

VP LND

VPSubnetwork

ONT#1

VP Topological Link End

ONT#2

OLT

VP NetworkCTP VP Link Connection

ONT/ONU #1ONT/ONU #1

OLTOLTONT/ONU #2ONT/ONU #2

NWView

VP Topological Link

VP Topological Link

VP Logical Link

VP Logical Link

VP Logical Link

TCONT (a subclass of Logical Link End)

NW view for DBANW view for DBA

(C)2003 NTT14

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.

Priority Queue #1

Priority Queue #3

Priority Queue #4

TC VPCTP

PQPointerforUpstream

T-CONT Buffer #A HOL

T-CONT Buffer #B HOL

Priority Queue #2

#1

#2

#3

#4

#5

#6

#7

Traffic scheduler

WRR

Priority Queue #5

WRR: Weighted Round Robin HOL: Head Of the Line

NE view for DBANE view for DBA

ONT / ONU OLT

T-CONT Buffer #A

T-CONT Buffer #B

(C)2003 NTT15

APNOMS2003

PhysicalPathTP

tcAdaptor

PhysicalPathTPFPtr.

APONCTP

APONTTP

ConnectivyPointerList

APONNetworkCTPNEAssignmentPtr.

APONNetworkTTPNEAssignmentPtr.

VPNetworkCTP

PhysicalPathTP

tcAdaptor

PhysicalPathTPFPtr.

APONCTP

APONTTP

ConnectivyPointerList

APONNetworkCTPNEAssignmentPtr.

APONNetworkTTPNEAssignmentPtr.

VPNetworkCTP

APONTrail

VPLinkConnection

ANetworkCTPPtr.ZNetworkCTPPtr.

ANetworkCTPPtr.ZNetworkCTPPtr.

ANetworkTTPPtr.ZNetworkTTPPtr.

T-CONT(Subclass of

logicalLinkEnd)

networkCTPsInLinkEndList

VPCTP

tcAdaptorPtr.

NEAssignmentPtr.

PriorityQueue

TrafficScheduler

TCONTbuffer

ONT/ONU OLT

PQPtrForUpstream

TrafficShedulerPtr.

T-CONTBufferPtr.

T-CONT(Subclass of

logicalLinkEnd)

networkCTPsInLinkEndList

VPLogicalLink

LogicalLinkFPtr.LogicalLinkFPtr.Zend Aend

VPCTPNEAssignmentPtr.

tcAdaptorPtr.

APONLink

APONtopLinkEndAPONtopLinkEnd AendZendList

APONLink

APONLinkConnection

OLTTCAdaptorIdONTTCAdaptorIdList

NEAssignmentPtr.

T-CONTBufferPMHistoryData

TXAdaptorDbaFairnessPMHistoryData

TCONTbuffer

ME relationship diagramME relationship diagram

(C)2003 NTT16

APNOMS2003

UML:Unified Modeling LanguageSuitable description of object-oriented systems and software development

Use case diagram

Sequence diagram

Class diagram

Q.834.3 is the first ITU-T Recommendation that describes scenarios using UML strictly

Relationship between OSS and its external environments (High level requirements for OSS)

Time ordered event description for each use case

Detailed relationship between managed entities

UML description UML description

(C)2003 NTT17

APNOMS2003Advantages of UMLAdvantages 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

(C)2003 NTT18

APNOMS2003

External Event Channel

Process Incoming NE Events

NE Synchronisation

Autodiscover NEs and PlugInUnits

BPON NE

Register OLT

OMS or Operator

Range ONT/ONU

Publish BPON Event

includes

communicates

communicates

communicates

communicates

communicates

communicates communicates

communicates

Example of use case diagramExample of use case diagram

[From ITU-T Q.834.3 Figure 5-8]

InstallationInstallation

Use case

Actor

(C)2003 NTT19

APNOMS2003

[From ITU-T Q.834.3 Figure 5-59]

As needed.

: Event Screener

: NESynchroniser

: Discoverer

: BPON NE

: Management Model Maintainer

: EventSupplier

get&compare( ) getNodeDetails( )

getEquipmentHolderList( )

getPlugInUnits( )

get Software( )

queries( )

queries( )

queries( )

queries( )

get managed entity( )

preparesMECreation/DeletionRecord( )

notify( )

Event Triggered NE Synchronisation Sequence DiagramEvent Triggered NE Synchronisation Sequence Diagram

Example of sequence diagramExample of sequence diagram

Class

(C)2003 NTT20

APNOMS2003

ONT or ONU

Ranging

OLT DCN

Restore

Event

Operator

ONT or ONU

Re-ranged

BPON NE

queries()

Operator

Event Screener

sends events

Discoverer

getNodeDetails()

getEquipmentHolderList()

getPlugInUnits()

get Software()

getEquipmentVersion()

queries

Event Queue

queues to

Privileged User

Schedulerschedules activity

Management Model Maintainer

BPON NE

Registrar

registers

EventSup

plier

notify()

ActivityCompleti

onLog

storeRecord()

viewRecords()

NESynchroniser

get&compare()

notifyInventoryMECreation()

notifyInventoryMEDeletion()

notifyNewRegistration()

synchNE()

preparesMECreation/DeletionRecord()

wait()

scheduledSynchNE()

getValue()

triggers

get details

reads

NE resynchtriggers

get details

and updates

triggers

sends creation/deletion

events

updates

NE Synchronisation Class DiagramNE Synchronisation Class Diagram [From ITU-T Q.834.3 Figure 5-58]

Example of class diagramExample of class diagram

Class nameAttributes

operations

(C)2003 NTT21

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.

BML

SML

NML

EML

NEL

NE

Q

Q

Q

Q

Q

Q

Q

Q

CMIPCORBAEDI

CORBAproposed

CORBAproposed

CORBAproposed

CORBAproposed

NE

SNMP ?

QCORBAproposed

QCORBAproposed

Q

OS

OS

OS

OS

OS

OS

QCORBAproposed

OSOS

OS

OS

SML X

CORBAproposed

CORBAproposed

CORBAproposed

CORBAproposed

tML is added recentl

y

CORBA framework in ITU-TCORBA framework in ITU-T

(C)2003 NTT22

APNOMS2003

FewSimpleEasy

ManyComplexDifficult

Fine grain model

(X.780)

Coarse grain model (X.780.1)

Q.834.4 model

CORBA framework and Q.834.4CORBA framework and Q.834.4

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

Number of instancesDesign

Implementation

Q.834.4 refers X.780 and X.781, and adds some general interface specifications using its own model.

(C)2003 NTT23

APNOMS2003OSS-IF interoperability testOSS-IF interoperability test

B-PON B-PON B-PON B-PON

EMS(Telawave)

EMS(QB)

EMS(Mitsunishi)

EMS(NEC)

B-PON

EMS(Iamba)

NMS(SBC)

NMS(NTT)

To be presented at this conference

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

(C)2003 NTT24

APNOMS2003Future plan of FSAN OAM-WGFuture 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

(C)2003 NTT25

APNOMS2003

Thank you

The beckoning cat, Maneki Neko,brings Luck.