for conformance and functional testing - … · for conformance and functional testing. ......

Ready-to-Use Test SuitesFor Conformance and Functional Testing

Copyright Testing Technologies 2010. Confidential Information. All Rights Reserved. More Information at www.testingtech.com.© 2

Ready-to-Use Test Suites (1)

Developed in TTCN-3

Conform to ETSI / IETF standards

Compliance and regression testing

Test case administration, execution and analysis

PC-based test suites for VoIP (SIP, H.248 (MEGACO), M3UA , SCTP, SUA)IPv6MOST


Ready-to-Use Test Suites (2)

Tailor-made special packages

Ideally suited to the advanced development and/or compilation of company-own test cases

Rapid, optimal execution of complex compliance and regression testing

Editing and compiling new test cases for modifying or building existing ones

TTsuite-FemtocellAnalyzing Femto Access Points (FAP)

Copyright Testing Technologies 2010. Confidential Information. All Rights Reserved. More Information at www.testingtech.com.©

TTsuite-Femtocell Features (1)

21 full-featured tests for Femto Access Points including Broadcast System InformationRRC & NAS ConnectionRAB Management User PlaneLocal Management

Exhaustive set of context parameters For a flexible adaptation of the Femtocell tests to FAP implementations under test

5


TTsuite-Femtocell Features (2)

Fully automated test execution

Platform-independent test execution

Test tracing on different levels of detail

Test definition and documentation in the standardized test notation TTCN-3

Femtocell Access Points

6


TTsuite-Femtocell

7

© 2010 by Femto Forum at www.femtoforum.org

http://www.femtoforum.org/femto/

TTsuite-H248Analyzing Media Gateway and Media Gateway Controllers


H.248 Protocol Introduction

Developed jointly by the Internet Engineering Task Force (IETF) and International Telecommunication Union (ITU)

Device control protocol

RFC 2885 / RFC 2886 / RFC 3015

Synonymous and technically identical to IETF Megaco Protocol

Addresses the relationship between a Media Gateway Controller (MGC) and a Media Gateway (MG)

A Master/Slave protocol that removes intelligence from MGs


TTsuite-H248 Features (1)

Full-featured tests (total of 230 test cases) for H.248 Media Gateways and

Media Gateway Controllers including procedures usingAdd command Modify command Subtract command Move command AuditValue command Audit Capabilities command Notify command Service Change command

Administration and maintenance procedures

Transport related procedures SIP implementation under test


TTsuite-H248 Features (2)

Tests for valid and invalid H.248 protocol behavior

Exhaustive set of context parametersFor flexible adaptation of the H.248 tests to an H.248 implementation under test


Platform-independent test execution Executable tests can be ported onto various test devices and test platforms


Summary of test results

Test definition and documentation In the standardized test notation TTCN-3


TTsuite-H248 Standards

ITU-T H.248: Gateway control protocol.

ETSI ES 201 873-1 V3.1.1 (2005-06): The Testing and Test Control Notation version 3, Part 1: TTCN-3 Core Language.

ETSI DTS/MTS-0096-1 V0.0.1 (2003-10)

ETSI DTS/MTS-0096-2 V0.0.1 (2003-10)

ETSI DTS/MTS-0096-3 V0.0.1 (2003-10)

TTsuite-HSSThe Conformance Test Framework


What is TTsuite-HSS?

Home Subscriber Server (HSS) conformance test framework

Easy to use TTCN-3 frameworkSupport of 3GPP release 6 and 788 conformance test casesCx and Sh interfaceSimulating

I-CSCFS-CSCFAS


What is a Home Subscriber Server?

HSS (Home Subscriber Server)Standardized by 3GPPUser database in IMS networksContaining user profilesPerforms authentication and authorizationInformation about user’s physical location


Entities Interacting with HSS

I-CSCF (Interrogating Call Session Control Function)Queries the HSS over the Cx Interface to retrieve

The user locationThe assigned S-CSCF

S-CSCF (Serving Call Session Control Function)Central note of the signaling planeUses the Cx Interface to the HSS to

Download and upload user profiles

AS (SIP Application Server)Host and execute services e.g.

IPTV, Presence, Push2Talk, etc. …

Communicates with the HSS in local networks over the Sh Interface


Interfaces

The Cx interfaceEnables communication between the HSS and the I-CSCF or S-CSCFProvides operations for

Location Management ProceduresUser Data Handling ProceduresUser Authentication Procedures

The Sh interfaceConnects Application Server to the HSSAvailable operations are

User Data Handling ProceduresSubscription/Notification Procedures


Network Topology


Test Coverage

Interface MainFunctionality

Functionalities Subgroups

ValidBehavior

InvalidBehavior

User Registration Status Query (SQ)

X X

S-CSCF Registration/Deregistration Notification (RDN)

X X

Location Management Procedures (LM)

User Location Query (LQ)

X X

User Profile Download (PD)[1]

X XUser Data Handling Procedures (UH)

Cx

HSS Initiated User Profile Update (PU)

- -

Authentication Procedures (A)

Authentication (A) X X

Download (D) X XUser Data Handling Procedures (UH)

Sh

Update (U) X X

Request Notification (RN)

X XSubscription/Notification Procedures (SN)

Notification (N)[2] X X

[1] The test purposes for PD are included in RDN test purposes.[2] The test purposes for N are included in RN test purposes


Test Case Overview

Name Available TC's

Cx 58Interface

Sh 30

Location Management Procedures (LM) 51

Authentication procedures (A) 7

User Data Handling Procedures (UH) 19Main Functionality

Subscription/Notification Procedures (SN) 11

User Registration Status Query (SQ) 19

S-CSCF Registration/Deregistration Notification (RDN) 21

User Location Query (LQ) 11

User Profile Download (PD) 1 0

Authentication (A) 7

Download (D) 9

Update (U) 10

Request Notification (RN) 11

Functionalities Subgroups

Notification (N)² 0

invalid 40Behavior

valid 48

[1] The test cases for PD are included in RDN test case group.[2] The test cases for N are included in RN test case group.


Why is HSS so Important

The HSS is the heart of an IMS network

The main database in the IMS architecture

Containing access parameters to set up sessions

Enables the SIP service execution

It is the only one containing user and service data in IMS networks

All sensible data are stored there e.g.AuthorizationAccountingRoaming


Requirements

HSS must be accessible for the test suite

5 users must be set up in the HSS2 normal subscriber (full rights)3 special subscriber (restricted rights)

2 AS has to be configured in the HSSOne with full rightsThe other one with restricted rights

TTworkbench 1.1.3 MAINT-20080220 releaseTTsuite-HSS

Diameter Codec PluginXSD Codec PluginSh Data External Function PluginTCP Port PluginIP Utility External Function Plugin

TTsuite-IPv6Analyzing the Next Generation Internet Protocol


TTsuite-IPv6 Introduction

IPv6 Is the next generation InternetGives vastly increased address space and true end-to-end communicationHas improved security and mobility features and allows 'plug-and-play' connection to the network

IPv6 Testing Based on a joint ETSI-eEurope standardization project for the development of test specifications for IPv6


What is IPv6?

Internet Protocol Version 6 Designed to replace current Version 4 (20 years old)

Network layer standard for a packet switched network

Important improvements to IPv4Increases the number of available internet addresses

IPv4 - about 4.3×109

IPv6 - about 3.4×1038

World population 6.5x109

Routing and network autoconfiguration (Plug&Play)Jumbograms breaking the limit of IPv4 (64K)(True end-to-end communication (flowlabel, etc.))(Adding mobility, security, QoS – next phase)


TTsuite-IPv6 Features (1)

610 full featured tests for Core functionality Neighbor Discovery Stateless Address Autoconfiguration ICMPv6 Router Renumbering

Tests for IPv6 protocol behavior and syntax variations in IPv6 messages

Exhaustive set of context parameters for flexible adaptation of IPv6 tests to the IPv6 implementation under test


TTsuite-IPv6 Features (2)


Platform-independent test execution, executable tests can be ported onto various test devices and test platforms



Test definition and documentation in standardized test notation TTCN-3


TTsuite-IPv6 Applications

All applications using IPv6 (Hosts/Routers with IPv6 stack, IPv6 Implementations, VoIP, etc.)

Telnet/ SSH/ VNC WWW Email FTP IRC VoIP/ Videoconferencing/ Streaming Fileserver/ Webserver/ FTPServer


TTsuite-IPv6 Benefits

Standards-based testing according to IPv6 specifications

Rapid and simple test execution and analysis

Repeatability of tests and full support of test automation

Platform independence and rapid integration in existing test environments

Flexibility through further development in a worldwide standardized testing notation


TTsuite-IPv6 Standards

ETSI TS 102 514 v 1.1.1 IPv6 Core: Requirements Catalogue

ETSI TS 102 515 v 1.1.1 IPv6 Core: Conformance TSS & TP

ETSI TS 102 516 v 1.1.1 IPv6 Core: Conformance Test Suite

RFC 2460 (1998): Internet Protocol, Vers. 6 (IPv6) Specification

RFC 2461 (1998): Neighbor Discovery for IP Version 6 (IPv6

RFC 2462 (1998): IPv6 Stateless Address Autoconfiguration

RFC 2463 (1998): Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification

RFC 2894 (2000): Router Renumbering for IPv6


Integrators of IPv6 (Examples)

Government entitiesETSI project was an EU projectDepartment of Defense and Civilian agencies of the U.S. Federal Government have both mandated the adoption of IPv6 by 2008

Non-government entitiesHP, Cisco, Apple, IBM, Nokia, Sun Microsystems, Microsoft, Sony, British Telecom, NEC, Hitachi, Matsushita, Juniper Networks, …

TTsuite-M2PAAnalyzing the M2PA Peers


TTsuite-M2PA Features (1)

92 full-featured tests for M2PA peers including Link state controlASP traffic maintenanceTransmission failureProcessor outage controlDelimitation alignment error detectionTransmission reception controlCongestion control

Exhaustive set of context parameters For a flexible adaptation of the M2PA tests to M2PA implementations under test

33


TTsuite-M2PA Features (2)





34


TTsuite-M2PA

Applications Signaling Gateway (SG)Media Gateway Controller (MGC)IP Signaling Point (IPSP)etc.

BenefitsStandards-based testing according to M2PA specificationsFast and simple test execution and analysisRepeatability of tests and full support of test automationPlatform independence and rapid integration in existing test environmentsFlexibility through usage of the constantly evolving standardized test notation TTCN-3

35


TTsuite-M2PA Standards

RFC 2960 „Stream Control Transmission Protocol“, SCTP: Stream Control Transmission Protocol, 2000-10

RFC 3309 „Stream Control Transmission Protocol (SCTP) Checksum Change“, update RFC 2960, 2002-09

RFC 4165 Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Peer-to-Peer Adaptation Layer (M2PA), 2005-09

draft-bidulock-sigtran-m2pa-test-08, SS7 MTP2-User Peer-to-Peer Adaptation Layer Test Specifications M2PA-TEST, 2007-02

ISO/IEC 9646-1: „Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“

ISO/IEC 9646-2: „Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“

ETSI ES 201 873-1 TTCN-3 Core Language V4.1.1, 2009-06

36


TTsuite-M2PA

37

TTsuite-M3UASignaling Gateway and Application Server Analysis


M3UA Protocol Introduction

SS7 Message Transfer Part 3 User Adaptation Layer

Carrying SS7 over IP in 3G networks

Replaces MTP3 on the SS7 stack

Supporting the transport of any SS7 MTP3-User signaling (e.g. ISUP or SCCP messages) over the IP Network

M3UA is used for interworking packet switched and circuit switched networks at the Signaling Gateway or Softswitch

M3UA Layer uses the services of SCTP


TTsuite-M3UA Features (1)

Full-featured tests (total of 196 test cases) for M3UA peers including

ASP State Maintenance ASP Traffic Maintenance Message Transfer Routing Key Management SS7 Signaling Network Management SCTP Connection Management

Tests for valid, invalid and inopportune M3UA protocol behavior



TTsuite-M3UA Features (2)

Exhaustive set of context parameters For a flexible adaptation of M3UA tests to M3UA implementations under tests

Platform-independent test executionExecutable tests can be ported onto various test devices and test platform




TTsuite-M3UA Standards (1)

RFC 2960 (2000): "Stream Control Transmission Protocol", SCTP: Stream Control Transmission Protocol.

RFC 3309 (2002): "Stream Control Transmission Protocol (SCTP) Checksum Change", Update RFC 2960.

RFC 3332 (2002): Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA).

Draft RFC 3332 bis (2004): Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA).

ES 201 873-1 (2005):TTCN-3 Core Language, Version: 3.1.1


TTsuite-M3UA Standards (2)

ETSI TS 102 381 V1.1.1 (2004): Methods for Testing and Specifications (MTS); SS7 Message Transfer Part 3 - User Adaptation Layer; (IETF RFC 3332); Test Suite Structure and Test Purposes (TSS&TP).

ISO/IEC 9646-1: "Information Technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts".

ISO/IEC 9646-2: "Information Technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification".

ETSI: Protocol & Testing Competence Centre: www.etsi.org/ptcc

TTsuite-PresenceTesting Presence Service in IMS Networks


TTsuite-Presence Features (1)

287 full-featured tests for Presence Clients (Watcher and Presentity)Presence ServerResource List ServerXCAP Client, XCAP Server

Tests of valid and invalid Presence protocol behavior and syntax variations in Presence messages

Exhaustive set of context parameters Flexible adaptation of SIP tests to the Presence implementation under test



TTsuite-Presence Features (2)





Full control of presence information

SIP, HTTP and XML framework

XML data validation

Detailed analysis of the involved protocols

46


TTsuite-Presence Benefits

Standards-based testing according to IMS specifications by IETF, 3GPP, OMA

Fast and simple test execution and analysis

Repeatability of tests and full support of test automation

Platform independence and rapid integration in existing test environments

Flexibility through usage of the constantly evolving standardized test notation TTCN-3

47


TTsuite-Presence Standards (1)

IETFRFC 3265, 3856, 3863, 3903, 4479, 4480, 4483, 4662, 4745, 4825, 4826, 5025draft-ietf-sipping-config-framework-15draft-ietf-sip-xcap-config-00.txtdraft-ietf-simple-common-policy-caps-01draft-ietf-simple-pres-policy-caps-01draft-ietf-simple-xcap-diff-08draft-rosenberg-simple-xcap-change-log-00

3GPPTS 22.141; Presence service; Stage 1TS 23.141; Presence service; Architecture and functional description; Stage 2TS 24.141; Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3

48


TTsuite-Presence Standards (2)

ETSITS 122 141 Universal Mobile Teleco System (UMTS)

Presence service; Stage 1Presence service; Architecture and functional description; Stage 2Digital cellular telecommunications system (Phase 2+); Presence service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3

ES 201 873-1 Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language

OMAOMA-TS-Presence-SIMPLE-V1_0-20060725-A

49

TTsuite-SCTPAnalyzing its End Points


TTsuite-SCTP Features (1)

Full-featured tests (total of 124 test cases) for SCTP endpoints including

Association startup and takedown Sequenced delivery within streams User data fragmentation Acknowledgement and congestion avoidance Chunk bundling Packet validation Path management

Tests for valid, invalid and inopportune SCTP protocol behavior and syntax variations in SCTP messages


TTsuite-SCTP Features (2)

Exhaustive set of context parameters For flexible adaptation of SCTP tests to a SCTP implementation under test


Platform-independent test executionExecutable tests can be ported onto various test devices and test platforms





TTsuite-SCTP Standards

RFC 2960 (2000): SCTP: Stream Control Transmission Protocol.

RFC 3309 (2002): Stream Control Transmission Protocol (SCTP) Checksum Change, Update RFC 2960.


TTsuite-SIPAnalyzing the 3G Signaling Protocol


TTsuite-SIP Introduction


TTsuite-SIP Features (1)

Full-featured tests (total of 608 test cases) for User agent behaving as a client or server Proxy – outbound and simple proxy Redirect server Registrar

Tests for valid, invalid and inopportune SIP protocol behavior and syntax variations in SIP messages

Exhaustive set of context parameters For flexible adaptation of SIP tests to the SIP implementation under test


TTsuite-SIP Features (2)







TTsuite-SIP Extensions

Support of additional SIP extensionRFC 2778, RFC 3262, RFC 3265RFC 3311, RFC 3313, RFC 3327RFC 3455, RFC 3515, RFC 3608RFC 3680, RFC 3863, RFC 3903

Test Suite Framework enabling own test suite definition


TTsuite-SIP – Development

Outline View

TTCN-3CL Editor

Problems

TTCN-3Compiler Button

Project View


TTworkbench – Test Management

ResultAnalyzer

Online Logging, Filter, Reporting

Test ReportTest Campaign

Designer(Test Automation)

Test Parametrization

Test Execution

DevelopersPerspective

for Modification


TTsuite-SIP Standards (1)

RFC 2327, SDP (1998): Session Description Protocol.

RFC 3261, SIP (2002): Session Initiation Protocol.

RFC 3262, SIP (2002): Reliability of Provisional Responses.

RFC 3263, SIP (2002): Locating SIP Servers.

RFC 3264 (2002): An Offer/Answer Model with the SDP.

RFC 3265, SIP (2002): Specific Event Notification.

RFC 3311, SIP (2002): UPDATE Method.

RFC 3313, SIP (2003): Private Extensions for Media Authorization.



RFC 3323, SIP (2002): Privacy Mechanism.

RFC 3325, SIP (2002): Private Extensions for Asserted Identity within Trusted Networks.

RFC 3326, SIP (2002): The Reason Header Field.

RFC 3327, SIP (2002): Extension Header Field for Registering Non-Adjacent Contacts.

RFC 3329, SIP (2003): Security Mechanism.

RFC 3428, SIP (2002): Extension for Instant Messaging.

RFC 3455, SIP (2003): Private Header Extensions for the 3rd-Generation Partnership Project (3GPP).



RFC 3515, SIP (2003): Refer Method.

RFC 3608, SIP (2003): Extension Header Field for Service Route Discovery During Registration.

RFC 3680, SIP (2004): Event Package for Registrations.

RFC 3841, SIP (2004): Caller Preferences.

RFC 3891, SIP (2004): Replaces Header.

RFC 3892, SIP (2004): Referred By.

RFC 3903, SIP (2004): Extension for Event State Publication.

RFC 3911, SIP (2004): Join Header.



RFC 4028, SIP (2005): Session Timers.

ETSI ES 201 873-1 V3.3.1 (2005-06):The Testing and Test Control Notation version 3, Part 1: TTCN-3 Core Language.

TS 102 027-2 Ver. 2.1.1 (RTS/TIPHON-06021-2[2]):Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Technology Compliance.


TTsuite-SIP Standards on Request

RFC 2617 (1999): HTTP Authentication: Basic and Digest Access Authentication.

RFC 2833 (2000): RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals.

RFC 2976 (2000): The SIP INFO Method.

RFC 3312 (2002): Integration of Resource Management and Session Initiation Protocol (SIP).

RFC 3320 (2003): Signaling Compression (SigComp).

RFC 3420 (2002): Internet Media Type message/sipfrag.

RFC 3485, SIP/SDP (2003): Static Dictionary for Signaling Compression (SigComp).

TTsuite-SUAAnalyzing the Signaling Gateway and Application Server


TTsuite-SUA Features (1)

Full-featured tests (total of 108 test cases) for SUA peers including (ASP/SGP/Common)

State and Traffic Maintenance (ASP/SGP) Signaling Network Management (ASP/SGP) Management (ASP/SGP) Connectionless Data Transfer (Common) Routing Procedures (Common) Reassembly Procedures (Common) Connection Oriented Procedures (Common) SCTP Connection Management

Tests for valid, invalid and inopportune SUA protocol behavior


TTsuite-SUA Features (2)

Exhaustive set of context parameters For flexible adaptation of SUA tests to a SUA implementation under test






TTsuite-SUA Standards (1)

RFC 2960 (2000): “Stream Control Transmission Protocol”, SCTP: Stream Control Transmission Protocol.

RFC 3309 (2002): “Stream Control Transmission Protocol (SCTP)Checksum Change”, Update RFC 2960.

RFC 3868 (2004): Signaling Control Part User Adaptation Layer (SUA).


TTsuite-SUA Standards (2)

ISO/IEC9646-1: “Information technology - Open Systems Interconnection -Conformance testing methodology and framework,Part 1: General concepts”.

ISO/IEC9646-2: “Information technology - Open Systems Interconnection -Conformance testing methodology and framework, Part 2: Abstract Test Suite specification”.


TTsuite-VoiceQualityRTPTesting Voice Quality in VoIP Networks


VoiceQualityRTP Features

42 test cases to measure voice quality (PESQ, E-Model)

SIP protocol to build up a connection

Speech analyzing (MOS) according to E-Model (ITU-T Rec. G. 107)PESQ (ITU-T Rec. P.862)

Gathering RTP session parameters RTPPackets and RTCPPacketsBytes, PacketLoss and SSRCdeltaTMean, TMax and deltaTMin

Testing the voice quality of SIP signaled RTP stream User agents / clientsNetworks

72


TTsuite-VoiceQualityRTP

Supported Audio CodecsPCMUPCMA GSM G.723 G.726/32 G.729 iLBC

BenefitsFast and simple test execution and analysisRepeatability of tests and full support of test automationPlatform independence and rapid integration to existing test environmentsFlexibility through usage of the constantly evolving standardized test notation TTCN-3

73


Speech Analysis for VoIP Network

74

for conformance and functional testing - … · for conformance and functional testing. ......

Documents