1 / 12

Implementation of CORBA Management Interface for B-PON System

Implementation of CORBA Management Interface for B-PON System. Hironori Terauchi (Mitsubishi Electric), E-Mail:tera@isl.melco.co.jp Kouji Sato (Mitsubishi Electric), E-Mail:skouji@isl.melco.co.jp Taichi Kawabata (NTT), E-Mail:kawabata@exa.onlab.ntt.co.jp Eisaku Morita (NTT-AT)

fala
Download Presentation

Implementation of CORBA Management Interface for B-PON System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementation of CORBA Management Interface forB-PON System Hironori Terauchi (Mitsubishi Electric), E-Mail:tera@isl.melco.co.jp Kouji Sato (Mitsubishi Electric), E-Mail:skouji@isl.melco.co.jp Taichi Kawabata (NTT), E-Mail:kawabata@exa.onlab.ntt.co.jp Eisaku Morita (NTT-AT) E-Mail:eisaku@trans.ntt-at.co.jp

  2. UNI SNI 1. Introduction FTTH = Fiber To The Home B-PON (Broadband Passive Optical Network) Internet Internet (Data) PSTN ONT Max 32 TEL (Voice) OLT Video TV (Video Dist) PON Section (155M/622Mbps) SONET (TDM) Exclusive Line(DS1/E1) Multi Services Platform by ATM technology

  3. 2. Management Interface 2.1 Legacy Approach Individual Management Interface. For example… OMS (NMS) CMIP SNMP TL1 SMS (EMS) CMIP SNMP more… ATM LAN TDM(DS3) Management interface between OMS(=NMS) and SMS(=EMS) depends on network element.

  4. 2. Management Interface 2.2 New Approach • Requirements are • Interoperability • Time to market • Cost • OSS components are connected by generic software bus • CORBA • HTTP/XML • B-PON management • discussed in FSAN • standardized as ITU-T Q834.4

  5. 2. Management Interface 2.2 Structure of Q.834 series Q.834.3 UML description for management interface requirements NMS (OMS) Network View • 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 Q.834.2 Q.834.4 CORBA I/F (IDL) Q.834.3 Q.834.1 Network Element View EMS (SMS)

  6. 3.1 B-PON: Multi-Service Platform 3. Prototype System TL1 FTTX ISEM NMS FTTB FTTP FTTH

  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. 3. Prototype System 3.3 Q.834.4 Prototype System Architecture Q.834.4 CORBA I/F HMI Profile Object Repository RMI/Jini CORBA Navigator (OMS) ISEM(B-PON SMS) HMI Agent LAN/ ISDN RMI/Jini CORBA Agent NE Manager COS NamingService ORB COS NotificationService NE NE NE

  9. 4. Q.834.4 Interoperability Investigation 4.1 Q.834.4 Functional Feasibility • Testing based on a management scenario • create/delete a Traffic Descriptor Profile（TDP) • create/delete a connection using a TDP. • Implementation issues are... • naming conventions in the CosNameService. • the granularity difference of TDPs. • ambiguous behavior of a exception.

  10. 4. Q.834.4 Interoperability Investigation 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, howeveraccording its marshaling rule, it is 4-octet boundary.(before 2.4)

  11. 4. Q.834.4 Interoperability Investigation 4.2 Summary of current interoperability problem (cont.) OMG should properly update the latest specifications of CORBA2.4.*,2.5. Interoperability between CORBA systems will be much improved.

  12. 5. Conclusion Conclusion Authors focused on B-PON management interface specified in Q.834.4 using CORBA technology. 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. 2. Using the prototype system, feasibility of Q.834.4 profile management functions for real operations is verified.

More Related