Presentation on theme: "1 Implementation of CORBA Management Interface for B-PON System Hironori Terauchi (Mitsubishi Electric), Kouji Sato (Mitsubishi."— Presentation transcript:
1 Implementation of CORBA Management Interface for B-PON System Hironori Terauchi (Mitsubishi Electric), Kouji Sato (Mitsubishi Electric), Taichi Kawabata (NTT), Eisaku Morita (NTT-AT)
2 ONT Max 32 TV (Video Dist) TEL (Voice) Internet (Data) OLT Internet PON Section (155M/622Mbps) Multi Services Platform by ATM technology B-PON (Broadband Passive Optical Network) Exclusive Line(DS1/E1) SONET (TDM) PSTN SNI Video UNI 1. Introduction FTTH = Fiber To The Home
3 SNMP 2.1 Legacy Approach SNMP SMS (EMS) OMS (NMS) TL1 CMIP Management interface between OMS(=NMS) and SMS(=EMS) depends on network element. LANATMTDM(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 UML description for management interface requirements Network Element View Network View NMS (OMS) EMS (SMS) Q Q Q CORBA I/F (IDL) 2. Management Interface 2.2 Structure of Q.834 series Q 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 FTTX ISEM NMS TL1 3.1 B-PON: Multi-Service Platform FTTBFTTPFTTH 3. Prototype System
7 3.2 Q Prototype System 1. Prototyping for investigating... –Feasibility –Functionality –Interoperability 2. Test results are applied to Q Focused on Profile Management functions.
8 ISEM(B-PON SMS) CORBA Agent ORB HMI Agent NE Manager NE CORBA Navigator (OMS) Profile Object Repository COS NamingService COS NotificationService HMI RMI/Jini Q CORBA I/F 3.3 Q Prototype System Architecture LAN/ ISDN 3. Prototype System
9 4.1 Q 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 Interoperability Investigation
Summary of current interoperability problem 1. OMGs 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 Interoperability Investigation
Summary of current interoperability problem (cont.) OMG should properly update the latest specifications of CORBA2.4.*, Q Interoperability Investigation Interoperability between CORBA systems will be much improved.
12 Conclusion 1. This paper describes the prototype system based on Q specification. In the process of prototyping, implementation guidelines based on Q are highlighted. 5. Conclusion 2. Using the prototype system, feasibility of Q profile management functions for real operations is verified. Authors focused on B-PON management interface specified in Q using CORBA technology.