TOVE 3.2.1999 HUT/TML 1
TOIMIALAVERKOT (TOVE)Communications Platform
Project GroupVesa-Matti Puro
TOVE 3.2.1999 HUT/TML 2
TOVE Project Group
• 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
TOVE 3.2.1999 HUT/TML 3
TOIMIALAVERKOT (TOVE)Communications Platform
IntroductionVesa-Matti Puro
TOVE 3.2.1999 HUT/TML 4
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.
TOVE 3.2.1999 HUT/TML 5
Goal 1996
• The aim for 1996 is to build a working ITU-T BISDN signalling stack on top of VTT’s FSR switch
CPCS / SARSSCOP
UNI SSCF NNI SSCF
Q.2931MTP-3BISUP
Call Control
API
Switchinghardware
Switchcontrol“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
TOVE 3.2.1999 HUT/TML 6
ATM Switch Control
NodesATM Switch ControllerATM Switch
TOVE 3.2.1999 HUT/TML 7
Control Abstractions
Fabric Control Agent
FSR
Service Control
Call Control
(INAP, CORBA, IDL, Java)
Connection Control
Node Control Switch Control Fabric Control (GSMP, etc.)
(switch/port config., port mgmt,conn. mgmt, statistics, event messages)
Access : Q.2931
Internal : BISUP
TOVE 3.2.1999 HUT/TML 8
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
CPCS / SARSSCOP
UNI SSCF NNI SSCF
Q.2931MTP-3BISUP
Call Control
API
Switchinghardware
Switchcontrol
TOVE 3.2.1999 HUT/TML 9
Demonstration 1996
FSR Switching Fabriccontrolled using FSR API
VAT (in Linux PC)with TOVE Linux Q.2931
VAT (in PC)
Switch Controller
VAT = Audio Conferencing tool (www-nrg.ee.lbl.gov/vat)
TOVE 3.2.1999 HUT/TML 10
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)
TOVE 3.2.1999 HUT/TML 11
TOVE IN Interface
Controller PC
Call Control
ATM connectionto the FSR cluster
CORBA interface
Service workstations
Control requests
Triggers
TOVE 3.2.1999 HUT/TML 12
Demonstration 1997
FSR Switching Fabriccontrolled using open GSMP
VIC (in PC)with Linux ATM 0.34
VIC (in PC)
Switch ControllerSCP
TOVE 3.2.1999 HUT/TML 13
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
TOVE 3.2.1999 HUT/TML 14
TOVE Switch Architecture
CORBA
MAIN GUI LOG RT IN
NS ESFCFSNMP ILMI
NM IN L R IN
• 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
TOVE 3.2.1999 HUT/TML 15
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
TOVE 3.2.1999 HUT/TML 16
TOVE Protocols
Linux ATM API + ATM Card (CPCS / SAR)
SSCOP
UNI-SSCF NNI-SSCF
UNI 3.1(Q.2931/UNI 4.0)
MTP-3
BISUP
TOVE Call Control
GSMP
FCFTCAP
INGW
ATM Switchinghardware
GSMP
SCCP
OVOPS++ with CORBA
TOVE 3.2.1999 HUT/TML 17
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
TOVE 3.2.1999 HUT/TML 18
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
TOVE 3.2.1999 HUT/TML 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
TOVE 3.2.1999 HUT/TML 20
TOIMIALAVERKOT (TOVE)Communications Platform
Methods, tools and environmentVesa-Matti Puro
TOVE 3.2.1999 HUT/TML 21
Methods
• Object-oriented Modeling• Design Patterns• Technical Reviews• C++ Programming Language• Java Programming Language• CORBA Object Request Broker
TOVE 3.2.1999 HUT/TML 22
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)
TOVE 3.2.1999 HUT/TML 23
Methods and Tools in Concert
• C++– RTTI, Exceptions, ...
• STL– Data structures– Algorithms
• Design Patterns– Reusable designs
• CORBA integration– CORBA Services
UNI Framework
PF
SF
Switch Framework
Design Patterns
Protocol e.g. DSS2, UNI 3.1, UNI 4.0
STL
ORB
Services
Drivers
TOVE 3.2.1999 HUT/TML 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
TOVE 3.2.1999 HUT/TML 25
OVOPS++ Main Components
A
A
F
P
PP
P
M
M
S
•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
T
S
T M
TOVE 3.2.1999 HUT/TML 26
Development of OVOPS++
Conduits
CVOPS
OVOPS
OVOPS++
JVOPS
Design Patterns
Conduits+
DUITS
TOVE 3.2.1999 HUT/TML 27
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
TOVE 3.2.1999 HUT/TML 28
TOIMIALAVERKOT (TOVE)Communications Platform
Software and protocol architectureTimo Pärnänen
Harri Sunila
TOVE 3.2.1999 HUT/TML 29
TOVE architecture
CORBA
SWGUI
LOG RT IN
NS ESFCF
SNMP ILMI
TOVE 3.2.1999 HUT/TML 30
Protocols
Linux ATM API + ATM Card (CPCS / SAR)
SSCOP
UNI-SSCF NNI-SSCF
UNI 3.1(Q.2931/UNI 4.0)
MTP-3
BISUP
TOVE Call Control
GSMP
FCFTCAP
INGW
ATM Switchinghardware
GSMP
SCCP
CPCS adapter
TOVE 3.2.1999 HUT/TML 31
SWITCH
PORTSWITCH
CONFIG SNMP ILMI
FCF
LINK
ROUTING
PORTFACTORY
PROTOTYPESMUXES
ETC. COMMON
SS7STACK
GSMP
CORBA
TOVE 3.2.1999 HUT/TML 32
GUI
TOVE 3.2.1999 HUT/TML 33
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
SWITCH
ATM FCF
NB FCF
GSMP
API
TimeSlot E1
ConnectVPI/VCI
TOVE 3.2.1999 HUT/TML 34
• 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
ILMI / SNMP
NMS
ILMI ILMI
SNMPSNMP
TOVE 3.2.1999 HUT/TML 35
ILMI / SNMP
SNMPAGENT
OSI/TMNAGENT
ProprietaryAGENT
OPERATIONS
NOTIFICATIONS
OPERATIONS
NOTIFICATIONS
OPERATIONS
NOTIFICATIONS
OPERATIONS
NOTIFICATIONSCORBA
Q3
SNMP
Proprietary
Managed andSupport Object
Managed Open System
TOVE 3.2.1999 HUT/TML 36
TOVE 3.2.1999 HUT/TML
TOVE Route Service
• Based on – ATM Forum PNNI 1.0 Specification
• Management of routing information
TOVE 3.2.1999 HUT/TML 37
TOVE 3.2.1999 HUT/TML
Services Provided
• Routing information management• Hierarchical routing• Route information for Call control• Routing information exchanging (not
implemented)
TOVE 3.2.1999 HUT/TML 38
TOVE 3.2.1999 HUT/TML
Services Used
• Distribution of routing databases with CORBA
• PSE Pro object database for network topology information
TOVE 3.2.1999 HUT/TML 39
TOVE 3.2.1999 HUT/TML
Implementation Structure
TOVE RouteServer
Call control
ManagementclientRouting client
swSwitch
TOVE 3.2.1999 HUT/TML 40
TOVE 3.2.1999 HUT/TML
Implemented features
• Hierarchical routing– Peer groups– Distribution of routing servers
• Static routing information
TOVE 3.2.1999 HUT/TML 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
TOVE 3.2.1999 HUT/TML 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
TOVE 3.2.1999 HUT/TML 43
TOVE 3.2.1999 HUT/TML
Services Used
• Provided by CPCS• DATA request/indication
TOVE 3.2.1999 HUT/TML 44
TOVE 3.2.1999 HUT/TML
Implementation Structure
Adjacencyprotocol
GSMP
Configurationmanagement
Connectionmanagement
Factory
Event management
CPCS
FCF
TOVE 3.2.1999 HUT/TML 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
TOVE 3.2.1999 HUT/TML 46
TOIMIALAVERKOT (TOVE)Communications Platform
Protocol implementationsSami Raatikainen
Project Group
TOVE 3.2.1999 HUT/TML 47
Protocol Presentations
UNI 3.1BISUP
MTP-3
TCAP
SCCP
SSCOP
UNI-SSCF NNI-SSCF
CPCS
Jari Katajavuori Sami Raatikainen
Timo Pärnänen
Jussi Turunen
TOVE 3.2.1999 HUT/TML 48
PROTOCOL (n-1)
Protocol Stack
IFACE (n-1)
PROTOCOL (n)
Protocols - Interfaces
UNI 3.1
SIGIF
CALL CONTROL
UAALIF
UNI-SSCF
AAIF
SSCOP
CPCSIF
CPCS
• downPrimitives (request/response)• upPrimitives (indication/confirm)
TOVE 3.2.1999 HUT/TML 49
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
TOVE 3.2.1999 HUT/TML 50
SAAL
SSCOP
CS
SAR
UNI/NNI-SSCF
UNI/NNI
ATM
SSCS
CPCS
TOVE 3.2.1999 HUT/TML 51
CPCS
• Common Part Convergence Sub-layer (specified in I.363)
• Doesn’t vary with the type of traffic being sent
• Uses AAL5 service provided by Linux ATM
• Uses Linux ATM API to access NIC
TOVE 3.2.1999 HUT/TML 52
SSCOP
• Service Specific Connection-Oriented Protocol (specified in Q.2110)
• Data-link layer protocol• Offers both assured and unassured data
transfer service for upper layer• Can be used with different SSCFs
TOVE 3.2.1999 HUT/TML 53
SSCOP Service
• Provides:– Sequence Integrity– Error Correction– Flow Control– Keep Alive– Local Data Retrieval– Connection Control– Status Reporting
TOVE 3.2.1999 HUT/TML 54
UNI-SSCF
• Service Specific Coordination Function at UNI (specified in Q.2130)
• Performs a coordination function between the service required by Layer 3 signalling function and the service provided by SSCOP
• Used by UNI and Q.2931
TOVE 3.2.1999 HUT/TML 55
UNI-SSCF Service
• Unacknowledged transfer of data• Assured transfer of data• Transparency of transferred information• Establishment and release of SAAL
Connections
TOVE 3.2.1999 HUT/TML 56
NNI-SSCF
• Service Specific Coordination Function at NNI (specified in Q.2140)
• Performs a coordination function between the service required by Layer 3 signalling function and the service provided by SSCOP
• Used by MTP-3
TOVE 3.2.1999 HUT/TML 57
NNI-SSCF Service
• Assured transfer of data• Transparency of transferred information• Establishment and release of SAAL
Connections• SDU retrieval• Signalling link error monitoring• Flow control
TOVE 3.2.1999 HUT/TML 58
UNI Overview
• Based on – The ATM-Forum UNI 3.1 Specification– ITU-T Q.2931 Recommendation
• OSI layer 3 Functionality
TOVE 3.2.1999 HUT/TML 59
Services Provided for CC
• Point-to-point Call Setup / Clearing• Point-to-multipoint Call Setup / Clearing /
Party control• SAAL connection control • Error control• Reset (not implemented)
TOVE 3.2.1999 HUT/TML 60
Services Used
• Provided by SAAL UNI-SSCF• DATA request/indication• ESTABLISH request/indication/confirm• RELEASE request/indication/confirm
TOVE 3.2.1999 HUT/TML 61
Implementation Structure
COORD
MUXRSNRRN
UNI UNI
TOVE 3.2.1999 HUT/TML 62
Setup SequenceCalling
UNI
CC
UNI
Called
SETUPpdu
SETUPpdu
CONNECT ACKpdu
SETUPind SETUPreq
CALL PROC.pdu
CONNECTpdu
PROCEEDINGreq
PROCEEDINGind
SETUPconfCONNECTpdu
CALL PROC.pdu
SETUPrespCONNECT ACKpdu
TOVE 3.2.1999 HUT/TML 63
BISUPBroadband ISDN User Part
• ITU-T Q.2761 Functional Description
• ITU-T Q.2762 General functions of messages and signals
• ITU-T Q.2763 Formats and codes
• ITU-T Q.2764 Basic call procedures
PublicNetwork
PublicNetwork
TOVE 3.2.1999 HUT/TML 64
BISUP• SS7 User Part for B-ISDN call control and bearer service control
• Uses services from MTP-3
• Provides services for Application Part (Call Control) Application
TCAP
SCCP
MTP-3
SAAL
ATM Layer
Physical Layer
BISUP
SS7 Stack
BISUP
SIGIF
CALL CONTROL
MTPIF
MTP-3
TOVE modules
TOVE 3.2.1999 HUT/TML 65
SACF
CC ASE
BCC ASE
MC ASE
UI ASE
NI (Network Interface)
AP
MTP-3
BISUP
CC
BISUP
NI
MTP-3
mux
mux
factory
mux
sigif
SIO = 9 mtpif
saal link
SID
TOVE 3.2.1999 HUT/TML 66
BISUP
BISUP
BISUP
CC
CC
RLC
IAMSETUPind
SETUPreq
IAA PROCEEDINGreqPROCEEDINGind
ALERTINGind ACM ALERTINGreq
ANMSETUPconfSETUPresp
RELRELEASEreqRELEASEind
RELEASErespRELEASEconf
Exchange A Exchange BCall setup example
TOVE 3.2.1999 HUT/TML 67
BISUPATM Forum’s solutions for NNI:• IISP (Interim Interswitch Signaling Protocol)
• Version 1.0, af-pnni-0026.000, Dec 1994• Provides minimum level of interoperability for multivendor private ATM networks
• B-ICI (Broadband Intercarrier Interface)• B-ICI 2.1, af-bici-0068.000, Nov 1996• Defines the protocol used between carrier networks
• PNNI (Private Network-to-Network Interface)• P-NNI V1.0, af-pnni-0055.000, Mar 1996• Signaling and routing
TOVE 3.2.1999 HUT/TML 68
SS7
mtp3
mtpif
sccp
sccpif
tcap
ss7Configure
nsscf
naalif
TC-User
Signaling System Number 7
TOVE 3.2.1999 HUT/TML 69
MTP3• ITU-T Recommendation Q.704, Signaling System No.7 - Signaling network functions and messages
• ITU-T Recommendation Q.2210, Message transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140 (SSCF at NNI)
• Signaling message handling• Message discrimination
• Message distribution
• Message routing
• User parts (SCCP and BISUP) and AAL connections
TOVE 3.2.1999 HUT/TML 70
MTP3
Signalling network functions
Signalling message handling
Signalling network management
Messagedistribution
Messagediscrimination
Message routing
Signallingroute
management
Signallingtraffic
management
Signalling linkmanagement
Level 3(MTP3)
Level 2(NNI-SSCF)
Level 4(User Parts)
Testing and maintenance (MTP) Signalling message flow
Indications and controls
TOVE 3.2.1999 HUT/TML 71
MTP3
User Mux
AAL Mux
NNI-SSCF
BISUP SCCP
User Parts
AAL Connections
MTP3
NNI-SSCFNNI-SSCF
TOVE 3.2.1999 HUT/TML 72
SCCP
• ITU-T Recommendations Q.711-Q.714, Signaling System No.7 - Signaling Connection Control Part
• Connectionless control (Basic connectionless service)
• Segmenting and reassembling not supported
• Message discarded when error occurs
• Routing control
• Address translation
TOVE 3.2.1999 HUT/TML 73
SCCP
SCCPRoutingcontrol(SCRC)
SCCPConnection-
oriented control(SCOC)
SCCPConnectionless
control(SCLC)
SCCPManagement
(SCMG)
MTP3SCCPSCCPUsers
TOVE 3.2.1999 HUT/TML 74
TCAP• ITU-T Recommendations Q.771-774, Signaling System No.7 - Transaction Capabilities Application Part
• Connectionless remote procedure call
TCAPTCAP
SCP
SSP SSP
• Operation class 1, structured dialogue and normal end
• Interworking between CORBA and TC systems (TcSignaling)
TOVE 3.2.1999 HUT/TML 75
TCAPTC-User
TcPduProviderFactory
TcPduProvider
tove.tcap
tcap
sccpif
sccp
TCAP
tove.idl.tcap
Dialogs, Invocation State Machines etc.
Java
C++
org.omg.TcSignaling
TOVE 3.2.1999 HUT/TML 76
TCAP
CORBAInputHandler
Dialogue
ISM
tcapAdapter
Protocol
ISM
ISM
N_UNITDATAreq
N_UNITDATAind
N_UNITDATAind
Java
C++CORBA IDL
TcPduProvider
TcPduProviderFactory
TcPduUser
create_tc_pdu_providerregisterderegister
component and dialoguehandling primitives
TOVE 3.2.1999 HUT/TML 77
TOIMIALAVERKOT (TOVE)Communications Platform
TestingJussi Turunen
Jari Katajavuori
TOVE 3.2.1999 HUT/TML 78
Protocol conformance testing
• The purpose of testing is to find bugs• Communication software needs to be tested
for interoperability with other vendors software
• Conformance testing is the process of verifying that an implementation performs in accordance with a particular standard.
TOVE 3.2.1999 HUT/TML 79
Protocol conformance testing
• Conformance testing is a formal method of testing
• Specified in ISO IS 9646• The testing is done according to particular
protocol conformance test suites• Test suites are provided by standardization
bodies or manufacturers
TOVE 3.2.1999 HUT/TML 80
SSCOP testing environment
Tester
N-1 stack
SSCOP
N-1 stack
UNI-SSCF
Impl.send
155 Mbit/s
Operatios
TOVE 3.2.1999 HUT/TML 81
Testing SSCOP
• Test suite from ATM-Forum– 317 test cases
• Testing software by OES and TOVE• Components:
– tester: provided by OES, executes the test suite– IUT: implementation under test, TOVE SSCOP
protocol
TOVE 3.2.1999 HUT/TML 82
Testing SSCOP
– N-1 stack: encodes data from tester to a form understood by IUT and vice versa
– operation server: executes the test suite defined operations for which a separate server was written
TOVE 3.2.1999 HUT/TML 83
Test runs
• Tests were run one state at a time• The execution of the whole suite lasted
hours faster this way• One-state-at-a-time -testing allowed also
fast debugging and concentration on state-specific bugs
• Only some test cases were run separately
TOVE 3.2.1999 HUT/TML 84
Testing SSCOP - experiences
• The distribution of binaries was a working solution
• Testing, finding and fixing errors separate tasks with some conflicts
• Original SSCOP was working with Linux and Fore, still errors were found– END PDU retransmission, size constraints
• Also the test suite contained errors
TOVE 3.2.1999 HUT/TML 85
UNI Testing• Test Adapter• Java Tester Plug• The ATM Forum Abstract Test Suite for UNI 3.1
ATM Signaling for Network Side– 661 test cases– 160 test runs so far
• Components:– 2 x N-1 stack– IUT
TOVE 3.2.1999 HUT/TML 86
UNI testing environment
Tester
N-1 stack
155 Mbit/s
UNI 3.1
N-1 stack
CC
UNI 3.1
N-1 stack
CC
N-1 stack
TOVE 3.2.1999 HUT/TML 87
TOIMIALAVERKOT (TOVE)Communications Platform
Intelligent NetworkPasi Nummisalo
TOVE 3.2.1999 HUT/TML 88
IN architecture
SS#7
SSF
CCF
SRF
CCAF
SRF
IP
SSP
SMF
SCEF
SMAF
SMP
SCF
SCP
SDF
SDF
SDP
User NetworkInterface
Service deployment
INAP
TOVE 3.2.1999 HUT/TML 89
InteractionCCF
SSME
FEAM
SCF
FEAMINAP
SSF FSM
state state
SSF
SCME
SLEE
SCF FSM
SLPI
CCFCCAF
SLPL
DP
PICDP
BCSM
PICTrigger tableTrigger 1 -Trigger 2 xTrigger 3 -
SIB 1 SIB 2
POI POR 2POR 1
SIB 3
SIB 4
BCP
SIB chains
TOVE 3.2.1999 HUT/TML 90
Messages
EventReportBCSM (EDP-N)
CC ServiceNull
Origination Attempt
InitialDP (TDP-R)
RequestReportBCSMEvent, Continue
Answer No AnswerBusy
Send Call
Active
Answer No AnswerBusy
Setup
calls = calls + 1
TOVE 3.2.1999 HUT/TML 91
TOVE IN
UNI
TOVE SMPTOVE B-SSP
NNIcc
GUI
B-ISDN
Services
Name service
RMIDCF
initiatormanage-ment
SCPSSP
INGW
SS#7
TOVE SLEEDCFresponder
factory
Deploy
TOVE 3.2.1999 HUT/TML 92
DCFGUI/Application creation Application logic
Event
User Component
Fixed interfaces
Visual JavaBeans Non visual JavaBeans
DCF Component
Context
DCF Environment
Java platformView, Control
Model
ManagedFacade
TOVE 3.2.1999 HUT/TML 93
IN implementationService creation (SCE) Service management system (SMS)/
Service logic execution (SLEE)
Event, CID
SIB
Fixed interfaces
Visual JavaBeans Non visual JavaBeans
DCF Component
DCF Context
DCF Environment
Java platform
View, Control Model
Facade
Service/HLSIB
CORBA
CORBA Services
IDL mapping of INAP
BCP
OVOPS++ platform with CORBA support
Service user (SSP) SLEE
BCSM
PIC
DP
Session controlFactory interface
TOVE 3.2.1999 HUT/TML 94
GUIGUI
TOVE 3.2.1999 HUT/TML 95
HierarchySLEE
Services
Service x
Subscriber x
BCP in
BCP out
SIB x
HLSIB x
SIB x
SSD
POI x
next
POR x
Trigger x
Context
TOVE 3.2.1999 HUT/TML 96
INGW
ORB
TC-userObject
CORBA DomainTC-CORBA GatewayTraditional SS7Domain
ProxyObject
TC PDUInterfaces
TC/SS7Stack
TC/SS7Stack
TraditionalTC-User
e.g SSP (initiator)
e.g SCP (responder)(Optional)
TOVE 3.2.1999 HUT/TML 97
InteractionGateway CORBA-domainIN Domain
Legacy SSP TCFactoryFinder TCUserFactoryTcPduUser,
SSP Proxybegin_ind(destGT,…)
resolve(destGT)
createResponder(own ref)
TCUser (SCP)
create
IDL operation for oper 1 ( possible result)
invoke_ind(dId,…)
decode
IDL operation for oper 2invoke_req(dId,…)
continue_req(dId,…) encode
end_associationend_req(dId,…)
TOVE 3.2.1999 HUT/TML 98
IDL interfacesIDL:interface <name>Initiator:TcSignaling::TcUser{ void connect(…); void releaseCall(…);}
interface <name>Responder:TcSignaling::TcUser{ void initialDP(…); void eventReportBCSM(…);};
interface TcUserFactory:TcSignaling::TcUserGenericFactory{ void <name>Initiator create<name>Initiator(); void <name>Responder create<name>Responder(<name>Initiator, …);};// e.g. name = CoreINAP_CS1_SSF_to_SCF_AC
TOVE 3.2.1999 HUT/TML 99
INAP-IDLASN.1
InitialDPArg ::= SEQUENCE { serviceKey [0] ServiceKey, bnumber [1] CalledPartyNumber}
initialDP OPERATION ::= { ARGUMENT InitialDPArg ERRORS { missingCustomerRecord | systemFailure } CODE local : 1 }
IDL
struct InitialDPArgType { ServiceKeyType serviceKey; CalledPartyNumberType bnumber;};
void initialDP( in InitialDpArgType arg, inout TcContext ctx ) raises MissingCustomerRecord, SystemFailure;