1 / 99

TOIMIALAVERKOT (TOVE) Communications Platform

TOIMIALAVERKOT (TOVE) Communications Platform. Project Group Vesa-Matti Puro. Professor Olli Martikainen Vesa-Matti Puro, project management Jari Katajavuori: PF and UNI, 1997-1998 Timo Kokkonen, CODERS and DEBUG, 1998 Petteri Koponen: VE, 1996

cosima
Télécharger la présentation

TOIMIALAVERKOT (TOVE) Communications Platform

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. HUT/TML TOIMIALAVERKOT (TOVE)Communications Platform Project Group Vesa-Matti Puro

  2. Professor Olli Martikainen Vesa-Matti Puro, project management Jari Katajavuori: PF and UNI, 1997-1998 Timo Kokkonen, CODERS and DEBUG, 1998 Petteri Koponen: VE, 1996 Pasi Nummisalo: CC, DCF, INGW, Java SCP, and PF, 1996-1998 Timo Pärnänen: GUI, ILMI, MTP3, PF, SCCP, SWITCH and TCAP, 1996-1998 Sami Raatikainen: BISUP and PF, 1998 Pasi Rautiainen Juhana Räsänen: SSCOP, SF and NNI-SSCF, 1996 Harri Sunila: GSMP and TRS, 1997-1998 Jussi Turunen, SSCOP and testing, 1998 Samu Uimonen: CODERS Saku Vaittinen: CODERS HUT/TML TOVE Project Group

  3. HUT/TML TOIMIALAVERKOT (TOVE)Communications Platform Introduction Vesa-Matti Puro

  4. HUT/TML TOVE Project • Helsinki University of Technology, Telecommunications Software and Multimedia Laboratory (TML) • Professor Olli Martikainen, Network Architectures • A three years long research project (communications platform part of the project) to develop open and standard based infrastructure for future broadband networks • Create a platform for developing and testing distributed call and connection control model in B-ISDN networks • VTT provides FSR switching hardware to the project • Funded by TEKES and industry partners: HPY, Nixu, Nokia, OES, Sonera, Tecnomen, Telia and X-Net.

  5. HUT/TML Goal 1996 • The aim for 1996 is to build a working ITU-T BISDN signalling stack on top of VTT’s FSR switch Call Control BISUP Q.2931 Switch control MTP-3 “UNI” side of the protocols is for User-to-Network Interface “NNI” side is the interface between network elements Call Control manages all active connections in the switch UNI SSCF NNI SSCF SSCOP API CPCS / SAR Switching hardware

  6. ATM Switch ATM Switch Controller Nodes HUT/TML ATM Switch Control

  7. Access : Q.2931 Internal : BISUP Fabric Control (GSMP, etc.) Fabric Control Agent HUT/TML Control Abstractions (INAP, CORBA, IDL, Java) Service Control Call Control Connection Control (switch/port config., port mgmt, conn. mgmt, statistics, event messages) Node Control Switch Control FSR

  8. Call Control BISUP Q.2931 Switch control MTP-3 UNI SSCF NNI SSCF SSCOP API CPCS / SAR Switching hardware HUT/TML Results 1996 • Results were distributed march 97 (release 97/1) • ATM virtual switch software consisting • call control (CC) • Q.2931 • SSCOP • UNI-SSCF • NNI-SSCF • FSR Virtual Exchange (VE) • BISUP is missing from 97/1 release

  9. HUT/TML Demonstration 1996 Switch Controller VAT (in Linux PC) with TOVE Linux Q.2931 VAT (in PC) FSR Switching Fabric controlled using FSR API VAT = Audio Conferencing tool (www-nrg.ee.lbl.gov/vat)

  10. HUT/TML Goal 1997 • Major goals are IN-Gateway and UNI Framework • IN-Gateway includes: IN triggers, modifications of Call Control, INAP translations, TCAP, SCCP and MTP3 • UNI Framework consists of UNI 3.1 and Q.2931 • Other goals: further development of OVOPS++, integration of CORBA OmniBroker ORB to OVOPS++ • GSMP (General Switch Management Protocol)

  11. Control requests CORBA interface Call Control Triggers Controller PC ATM connection to the FSR cluster Service workstations HUT/TML TOVE IN Interface

  12. HUT/TML Demonstration 1997 SCP Switch Controller VIC (in PC) with Linux ATM 0.34 VIC (in PC) FSR Switching Fabric controlled using open GSMP

  13. HUT/TML Goal 1998 • New features to old modules: switch framework and error handling • Finishing, reviews, commenting • Testing: interfaces and corrections • New modules: INGW, routing and management • Pilot applications and services

  14. HUT/TML TOVE Switch Architecture • MAIN = CAC + MIB + CC + protocols • GUI: configuration • LOG: OMG log not implemented • RT: routing • IN: INGW • ILMI/SNMP: management • FCF: fabric control • NS/ES: CORBA Services

  15. HUT/TML Modules Implemented • PF, framework for network programming • GUI, graphical user interface for switch configuration • SWITCH, implements the structure of the switch (ports / links) and encapsulates the switching fabric details (NB / BB) • TRS, hierarchical routing following PNNI model • ILMI, management interface, address registration • CC, call control containing triggers and IN interface • DCF & SCP & INGW, hierarchical component based user interface, excecution environment for IN services and CORBA-to-INAP -gateway

  16. GSMP ATM Switching hardware HUT/TML TOVE Protocols TOVE Call Control INGW FCF UNI 3.1 (Q.2931/ UNI 4.0) BISUP TCAP SCCP MTP-3 GSMP UNI-SSCF NNI-SSCF SSCOP OVOPS++ with CORBA Linux ATM API + ATM Card (CPCS / SAR)

  17. HUT/TML Protocols Implemented • SSCOP, ITU-T Q.2110, full, working, tested • UNI-SSCF, ITU-T Q.2130, full, working, tested • UNI 3.1, ATM Forum UNI 3.1, partial, working with Linux and ForeRunnerLE 100 -switch • MTP3, partial • NNI-SSCF, full • BISUP, partial • SCCP/TCAP, partial • GSMP, partial

  18. HUT/TML TOVE Project 1997-1999 • First year • Q.2931 signaling, CC, FSR API fabric control • works with project’s own Linux signalling • Second year • UNI 3.1 signaling, GSMP fabric control, Java SCP • works with Linux atm 0.31 UNI 3.1 signaling • Third year • UNI 3.1 p-mp, BISUP prototype, Switch FW, Interworking CC prototype, ILMI, routing, GUI, DCF, INGW, Java SCP • works with Linux atm 0.47 UNI 3.1 signaling and Fore

  19. Summary • Gained considerable experience of O-O, Frameworks, network programming and B-ISDN • TOVE switch provides a prototype of standard based ATM signalling software with open switching fabric (GSMP) and service control (INAP) • The IN Gateway is one of the first implementations of CORBA to IN adapters using generic ROSE translation

  20. HUT/TML TOIMIALAVERKOT (TOVE)Communications Platform Methods, tools and environment Vesa-Matti Puro

  21. HUT/TML Methods • Object-oriented Modeling • Design Patterns • Technical Reviews • C++ Programming Language • Java Programming Language • CORBA Object Request Broker

  22. HUT/TML Tools • OVOPS++ pf/sf Frameworks (Protocol Framework/Scheduling Framework) • ORBacus 3.0.1 C++ and Java ORBs (www.ooc.com) and JTC-1.0.3 • egcs 1.0.2 C++ Compiler • STL (Standard Template Library) part of egcs • SUN JDK 1.1.6 (Java Development Kit) • Borland JBuilder 2 • SUN Swing 1.0.3 • ObjectStore PSE Pro 2.0 (www.odi.com)

  23. HUT/TML Methods and Tools in Concert • C++ • RTTI, Exceptions, ... • STL • Data structures • Algorithms • Design Patterns • Reusable designs • CORBA integration • CORBA Services Protocol e.g. DSS2, UNI 3.1, UNI 4.0 Switch Framework UNI Framework PF SF Design Patterns STL ORB Services Drivers

  24. OVOPS++ • OVOPS ++ (Object Virtual OPerating System ++) frameworks • consists of pf (Protocol Framework) and sf (Scheduling Framework) • based on Conduits+ by University of Illinois • Conduits+ was used by ASCOM Tech AG • contains general reusable protocol components

  25. T S HUT/TML OVOPS++ Main Components • Adapter: Connects OVOPS++ world to the “outer world” • Protocol: Context of the protocol (state variables, parameters etc.) • State: Functionality of the protocol • Mux: Multiplexes connections by session keys extracted from the message • Factory: Creates new Conduit instances • Transporters: Travels through conduit graph • Messengers: Carries data • Timers: Provides timeouts • Scheduler: Gives runtime A M T P M F P P M P S A

  26. HUT/TML Development of OVOPS++ DUITS Design Patterns Conduits Conduits+ OVOPS++ JVOPS OVOPS CVOPS

  27. HUT/TML Environment • HP PCs w/75Mhz Pentium to 450Mhz PII • Linux RedHat 5.2 and kernel 2.1.117 (for SSP / C++) • ATM on Linux 0.47 • NT Server/Workstation 4.0 (for SCP / Java) • VTT FST 4 x 155 Mbit/s STM-1 MMF • ForeRunnerLE 155 155 4 x MMF 8 x UTP

  28. HUT/TML TOIMIALAVERKOT (TOVE)Communications Platform Software and protocol architecture Timo Pärnänen Harri Sunila

  29. CORBA HUT/TML TOVE architecture SNMP ILMI LOG RT IN FCF NS ES GUI SW

  30. GSMP ATM Switching hardware HUT/TML Protocols TOVE Call Control INGW FCF UNI 3.1 (Q.2931/ UNI 4.0) BISUP TCAP SCCP MTP-3 GSMP UNI-SSCF NNI-SSCF SSCOP CPCS adapter Linux ATM API + ATM Card (CPCS / SAR)

  31. HUT/TML SWITCH

  32. HUT/TML GUI

  33. HUT/TML FCF • The Fabric Control Functions (FCF) is used to hide switching functions (fabric) from call procedures • ATM FCF uses GSMP to control fabric Call Control GSMP ATM FCF Connect VPI/VCI SWITCH API NB FCF TimeSlot E1

  34. HUT/TML ILMI / SNMP • Integrated (Interim) Local Management Interface (ILMI) • Provides status and configuration information using the Simple Network Management Protocol (SNMP) and an ATM Interface Management Information Base (MIB) • Virtual Path/Channel Connections • Address registration NMS SNMP SNMP ILMI ILMI

  35. Managed Open System OPERATIONS CORBA NOTIFICATIONS OPERATIONS SNMP AGENT SNMP NOTIFICATIONS OPERATIONS OSI/TMN AGENT Q3 NOTIFICATIONS OPERATIONS Proprietary AGENT Proprietary NOTIFICATIONS Managed and Support Object HUT/TML ILMI / SNMP

  36. TOVE 3.2.1999 HUT/TML TOVE Route Service • Based on • ATM Forum PNNI 1.0 Specification • Management of routing information

  37. TOVE 3.2.1999 HUT/TML Services Provided • Routing information management • Hierarchical routing • Route information for Call control • Routing information exchanging (not implemented)

  38. TOVE 3.2.1999 HUT/TML Services Used • Distribution of routing databases with CORBA • PSE Pro object database for network topology information

  39. TOVE 3.2.1999 HUT/TML Implementation Structure Call control swSwitch Routing client Management client TOVE Route Server

  40. TOVE 3.2.1999 HUT/TML Implemented features • Hierarchical routing • Peer groups • Distribution of routing servers • Static routing information

  41. TOVE 3.2.1999 HUT/TML GSMP Overview • Based on • RFC 1987 • Controlling of the switching fabric • connection establishment and teardown • configuration management • statistics information

  42. TOVE 3.2.1999 HUT/TML Services Provided for FCF • Connection establishment, teardown and modifying • Switching fabric configuration information • Switching fabric configuration setup • Switching fabric statistics information • Notifications of asynchronous events

  43. TOVE 3.2.1999 HUT/TML Services Used • Provided by CPCS • DATA request/indication

  44. FCF Connection management Configuration management Event management Factory GSMP Adjacency protocol CPCS TOVE 3.2.1999 HUT/TML Implementation Structure

  45. TOVE 3.2.1999 HUT/TML Implemented features • Adjacency protocol • RFC 1987 • Synchronization error in specification fixed • GSMP • RFC 1987 • Connection management • Configuration management • Events

  46. HUT/TML TOIMIALAVERKOT (TOVE)Communications Platform Protocol implementations Sami Raatikainen Project Group

  47. Jari Katajavuori Sami Raatikainen TCAP Timo Pärnänen SCCP MTP-3 UNI-SSCF NNI-SSCF SSCOP CPCS Jussi Turunen HUT/TML Protocol Presentations UNI 3.1 BISUP

  48. HUT/TML Protocol Stack Protocols - Interfaces CALL CONTROL • downPrimitives (request/response) SIGIF • upPrimitives (indication/confirm) UNI 3.1 UAALIF UNI-SSCF PROTOCOL (n) AAIF SSCOP IFACE (n-1) PROTOCOL (n-1) CPCSIF CPCS

  49. HUT/TML SAAL • SAAL (Signalling ATM Adaptation Layer, specified in Q.2100) • used by signalling applications • USSCF/NSSCF, SSCOP, CPCS, AAL5 • Service Specific Part and Common Part • The purpose of SAAL is to convey information across UNI and NNI

  50. UNI/NNI UNI/NNI-SSCF SSCOP CS SAR ATM HUT/TML SAAL SSCS CPCS

More Related