12
1 Implementation of CORBA Management Interface for B-PON System Hironori Terauchi (Mitsubishi Electric), E-Mail:[email protected] Kouji Sato (Mitsubishi Electric), E-Mail:[email protected] Taichi Kawabata (NTT), E-Mail:[email protected] Eisaku Morita (NTT-AT) E-Mail:[email protected]

Implementation of CORBA Management Interface for B-PON System

Embed Size (px)

DESCRIPTION

Implementation of CORBA Management Interface for B-PON System. Hironori Terauchi (Mitsubishi Electric), E-Mail:[email protected] Kouji Sato (Mitsubishi Electric), E-Mail:[email protected] Taichi Kawabata (NTT), E-Mail:[email protected] Eisaku Morita (NTT-AT) - PowerPoint PPT Presentation

Citation preview

1

Implementation of CORBA Management Interface for

B-PON System

Hironori Terauchi (Mitsubishi Electric),E-Mail:[email protected]

Kouji Sato (Mitsubishi Electric),E-Mail:[email protected]

Taichi Kawabata (NTT),E-Mail:[email protected]

Eisaku Morita (NTT-AT)E-Mail:[email protected]

2

ONTMax 32

TV (Video Dist)

TEL (Voice)

Internet (Data)

OLT

InternetInternet

PON Section(155M/622Mbps)

Multi Services Platform by ATM technology

B-PON(Broadband Passive Optical Network)

Exclusive Line(DS1/E1)

SONET(TDM)

SONET(TDM)

PSTNPSTN

SNI

VideoVideo

UNI

1. Introduction

FTTH = Fiber To The HomeFTTH = Fiber To The Home

3

SNMP

2.1 Legacy Approach

SNMP

SMS(EMS)

OMS(NMS)

TL1

CMIP

CMIP

Management interface between OMS(=NMS) and SMS(=EMS) depends on network element.

LANLANATMATM TDM(DS3)TDM(DS3)

For example…

more…

2. Management Interface

Individual Management Interface.

4

2.2 New Approach

1. Requirements are– Interoperability– Time to market– Cost

2. Management Interface

2. OSS components are connected by generic software bus

– CORBA– HTTP/XML

3. B-PON management– discussed in FSAN– standardized as ITU-T Q834.4

5

Q.834.3 UML description for management interface requirements

Network Element View

Network View

NMS(OMS)

EMS(SMS)

Q.834.1

Q.834.2Q.834.4CORBA I/F

(IDL)

2. Management Interface

2.2 Structure of Q.834 series

Q.834.3

- Provisioning installed network resources- Provisioning uninstalled network resources including capacity reservation- Service provisioning- Archive management- NE software management- NE configuration data backup and restore- Performance management- NE event publication- Profile management- Testing- Activity scheduling- Bulk transfer management- NE-EMS synchronization- Access control

6

FTTXFTTXISEMNMS

TL1

3.1 B-PON: Multi-Service Platform

FTTBFTTB FTTPFTTP FTTHFTTH

3. Prototype System

7

3. Prototype System

3.2 Q.834.4 Prototype System

1. Prototyping for investigating...– Feasibility– Functionality– Interoperability

2. Test results are applied to Q.834.4

3. Focused on Profile Management functions.

8

ISEM(B-PON SMS)

CORBAAgent

ORB

HMIAgent

NE Manager

NE NE NE

CORBA Navigator(OMS)

Profile Object Repository

COS NamingService

COS NotificationService

HMI

RMI/Jini

RMI/Jini

Q.834.4CORBA

I/F

3.3 Q.834.4 Prototype System Architecture

LAN/ISDN

3. Prototype System

9

4.1 Q.834.4 Functional Feasibility

1. Testing based on a management scenario– create/delete a Traffic Descriptor Profile( TDP)– create/delete a connection using a TDP.

2. Implementation issues are...– naming conventions in the CosNameService.– the granularity difference of TDPs.– ambiguous behavior of a exception.

4. Q.834.4 Interoperability Investigation

10

4.2 Summary of current interoperability problem

1. OMG’s CORBA2.4.*, 2.5 and other version.

Interoperability ???

2. The LocateReply Body of GIOP1.2–“aligned on an 8-octet boundary” (2.4.*, 2.5)–“marshaled immediately following the LocateReply

Header” (2.6 and higher version)• resulted to 4-octet boundary.

–without explicit description, however according its marshaling rule, it is 4-octet boundary.(before 2.4)

4. Q.834.4 Interoperability Investigation

11

4.2 Summary of current interoperability problem (cont.)

OMG should properly update the latest specifications of CORBA2.4.*,2.5.

4. Q.834.4 Interoperability Investigation

Interoperability between CORBA systems will be much improved.

12

Conclusion

1. This paper describes the prototype system based on Q.834.4 specification. In the process of prototyping, implementation guidelines based on Q.834.4 are highlighted.

5. Conclusion

2. Using the prototype system, feasibility of Q.834.4 profile management functions for real operations is verified.

Authors focused on B-PON management interface specified in Q.834.4 using CORBA technology.