1. The employment of TTCN-3 for testing the Application Server in the IMS network.
Damian Zolich, TTCN-3 User Conference 2011
Ericpol Telecom Sp. z o.o – 9 June Bled, Slovenia
Tel.:

2. Step 2 New test environment with TTCN-3 Step 3 Make testing easy
Agenda
Introduction
Step 1 Without TTCN-3
Step 2 New test environment with TTCN-3
Step 3 Make testing easy
Step 4 Our future

3. Our environment in numbers
About 7000 test cases
Up to 80 components in one test case
About 45 users
930 files
1,5 million code lines
Support for 7 different protocols
11 interfaces

4. Only one protocol (SIP) Very basic scenarios Simple environment
Step 1 Without TTCN-3
Only one protocol (SIP)
Very basic scenarios
Simple environment
Simple matching mechanism

5. Simple environment
Caller
Application
Server
Callee
Traffic Generator

6. New traffic generator (H.248) More and more complex scenarios
New challenges
New traffic generator (H.248)
More and more complex scenarios
New protocols in the near future
More and more pressure on matching mechanism

7. ? Second protocol H.248 Traffic Generator SIP Caller Application
Server
Callee
Traffic Generator
SIP
MRFP
H.248 ?

8. Preparation for the test execution
Test team problems
Preparation for the test execution
Exchanging information between traffic generators
No flexibility
Poor matching mechanism
Code reuse
Message synchronisation
Verification of correct message sequence
Timers

10. Solution
We need something completely different.
So let’s try TTCN-3

11. Step 2 New test environment with TTCN-3
Charging
SLF
Px App
Ro (online charging)
Rf (offline charging) Px Dh
Provisioning
Diameter/TCP
Diameter
Muta
LDAP
CM,PM
CAI3G/XCAP
IMS AS Mp Mr
H.248
LDAP Sh
SIP
MRFP
Audio & Video
Announcements
Audio & Video Conference
Diameter/TCP
ISC
SIP
MRFC
Voice &
Video mail Cx
S-CSCF
HSS
SIP
MGW Dx
I-CSCF
SIP
MGCF
PSTN/PLMN
SIP
P-CSCF
SIP
CSCF
other SIP network
CSCF
SBG
SIP NNI
or H.323

12. New challenges Test environment which enables:
Simulation of nodes around the Application Server
Support of all required interfaces
Support of all required protocols
Support of advance matching mechanism
Coordination between interfaces

13. TTCN-3 Function Test Environment IMS AS MTAS CCF ECF HSS Operator CMRf
(Diameter) Ro
(Diameter) Sh
(Diameter)
Operator PM
Operator PM
SLF
Muta
(LDAP)
PIPE Testport Dh
(Diameter)
IMS AS
MTAS
S-CSCF
CAI3G/
Ut (XCAP)
ISC (SIP)
S-CSCF MP
(H.248)
Provisioning
TTCN-3
MRFP
MRFP1
MRFP
MRFP2

14. Basic call setup vs. Test simulation
Alice
SIP: INVITE
SIP: 180 Ringing
SIP: 200 OK
SIP: ACK
Originating
IMS AS
Terminating
CSCF
Originating
CSCF
Primary CCF
Terminating network
SIP: INVITE
SIP: INVITE
SIP: INVITE
SIP: 180 Ringing
SIP: 180 Ringing
SIP: 180 Ringing
SIP: 200 OK
SIP: 200 OK
SIP: 200 OK
SIP: ACK
DIAMETER: Accounting-Request Start
DIAMETER: Accounting-Answer Start
SIP: ACK
SIP: ACK

15. Testing is time consuming Development of test cases difficult to learn
New test team problems
Testing is time consuming
Development of test cases difficult to learn
Lots of code to write for one test case
Test execution quite complex

16. Framework and Automation
Solution
We need a good test
Framework and Automation

18. TTCN-3 function library & API
Step 3 Make testing easy
TTCN-3 function library & API
Creation and initialization of test components, routing of
messages and verification of message content
Test automation scripts
Run before and after the TC call flow.
Ensures test environment integrity and checks for problems caused by TC execution.

19. Test Object – Service II
Directory Structure
Test Object – Service I
Test Object – Service II
Test module
Private functions …
Framework
Scripts
DIAMETER
H248
DNS
SIP
Test automation
Sh/Dh Rf Ro Mp Mr Ma
Isc

20. Messages exchange on ports between the SUT and the Framework components (defaults used)
Outgoing IMS AS
Port
IMS AS
Incoming IMS AS Port
3. Invite
2. Invite OK OK
5060 ISC1
SIP_DISPATCHER_CT
5061 ISC2
1. Invite
4. Invite OK OK
ISC_SESSION_CT ISC1
ISC_SESSION_CT ISC2

21. Framework component overview
Non-Session
Caller (ISC Session)
Sh session 1
HSS dispatcher
IMS AS
Sh session X
CSCF
(SIP dispatcher)
Rf Session 1
CCF dispatcher
Callee (ISC Session)
Sip caller and callee are together a SIP session
Rf Session X
Non-Session
Dispatchers uses list of keys to differientiate sessions
Non session
related data

22. Higher abstraction level for writing TCs
Framework benefits
Higher abstraction level for writing TCs
More readable/understandable test cases written in a consistent style
Complex and extensive common verification details are handled transparently and automatically
Simplifies TC maintenance and development
New checks can be added automatically to existing TCs via the framework

23. Majority of TC’s automated Full automated regression test
Framework benefits
Majority of TC’s automated
Full automated regression test
Flexibility in test case creation
User friendly

24. Examples of automated test activities
Pre execution activity:
cleaning environment
checking environment
run external applications (e.g. wireshark)
Post execution activity
collecting all logs into one archive file
monitor for hanging processes, memory leaks & system crashes

26. Environment very flexible to test new features required by customers
Step 4 Our future
Environment very flexible to test new features required by customers
Smart way of regression testing
More testing in shorter time

28. Thank you Damian Zolich, TTCN-3 User Conference 2011
Ericpol Telecom Sp. z o.o – 9 June Bled, Slovenia
Tel.: