NetHawk EAST for IMS testing
version 1.1
Introduction
IP Multimedia Subsystem (IMS) is a
standardized open Next Generation
Networking (NGN) architecture and it
enables real-time mobile and fixed line
multimedia services. These services
include the foundation services (voice,
video, messaging, conferencing, push-
to-talk, games, web-based services etc.)
and the composite services (rich Voice,
Games with trash talk etc.) developed
using Service enablers (presence, GMLS
etc.).
The IMS architecture was introduced by
3GPP in Release 5 for UMTS and TD-
SCDMA, and similar architecture is used
by 3GPP2 for cdma2000. With the
network evolution and convergence, IMS
architecture provides the foundation for
Fixed Mobile Convergence (FMC) and
NGN specified by ETSI TISPAN and
Packet Cable 2.0.
IMS Architecture
The IMS architecture consists of three
layers. The Service Layer comprises
application and content servers, for
example Presence and Group List
Management for PTT/PoC applications.
The Control Layer comprises network
control servers for managing
call/session set-up modification and
NetHawk EAST IMS Data Sheet > 1
Data Sheet
Solution in
brief
1. Powerful Scalable load
testing platform
2. Maximum flexibility with
fully customizable test
Figure 1. NetHawk EAST. cases
release. The Connectivity Layer
comprises the access network (wireless 3. Effective Multi-user/ Multi-
and wireline) and backbone network technology environment
(IPv6 and IPv4).
4. Existing test packages for
EAST Support for IMS the protocols used in IMS
interfaces
NetHawk EAST testing tool can be used
by telecom equipment manufacturers
and service providers for complete life
F1 Interop Solutions selects
cycle from production to deployment to
NetHawk EAST test solution
maintenance for:
for its independent
VOIP/PacketCable & IMS
> Feature Testing: IMS Nodes (P-
interoperability Lab.
CSCFs, etc.) and interfaces (Mw, ISC,
etc.) testing
> Subsystem Testing: one or more
IMS Node combination
> Network Testing: end-to-end
testing (M2M, L2M etc.)
> Load and Stress Testing
> Security Testing: HTTP Digest,
NetHawk EAST for IMS Testing
Figure 2.3GPP IMS network architecture.
TLS, IPSec, etc.
> Service Testing: OMA Compliant
PoC, Presence etc.
> Conformance Testing: H.248, SIP,
SIGTRAN, etc.
> Quality measurement and QoS:
PESQ, TOS, DSCP etc.
> Other IMS Related Testing:
Sigcomp, etc.
EAST can emulate multiple network
elements with one test case. EAST
provides a common environment for test
cases across all standard and
proprietary protocols. It supports
simultaneous multi-protocol testing,
assurance and validation.
NetHawk EAST IMS Data Sheet > 2
NetHawk EAST offers a scalable Load
Testing Platform with maximum
flexibility. It supports fully customizable
tests for positive and negative
evaluation. EAST has existing test
packages for the protocols used in IMS
interfaces.
THE DEVICE UNDER TEST
The DUT (Device Under Test) can be any
or any combined 3GPP/3GPP2 IMS, NGN
(TISPAN) and Packet Cable 2.0 network
nodes:
> P-CSCF, I-CSCF, S-CSCF,
> IBCF, IWF, BGCF, MGCF, MGFP,
> I-BGF, IM-MGW, MRFP,
> HSS, SLF, UPSF (Formerly HSS),
> NASS, RACS,
> PES, etc.
Signaling testing includes end-to-end
call setup and release. Bearer testing
includes:
>Voice (codec: AMR, G.711), video
(H.263), Data, Fax (T.38);
> Voice Quality Measurement (PESQ,
MOS)
> RTP stream and TDM
SIP
NetHawk EAST can simulate SIP Client,
Server, Agents and Terminals. EAST can
support IMS P-CSCF, I-CSCF, S-CSCF and
other SIP messaging network entities
and interfaces protocol testing.
DIAMETER
IMS Diameter provides an
authentication, authorization and
accounting (AAA) framework for
applications like network access and IP
mobility. It covers VoIP, UMTS and IMS
technologies. EAST supports testing IMS
NetHawk EAST for IMS Testing
Figure 3. TISPAN – NGN Reference Architecture.
nodes using base IETF DIAMETER
protocol and other 3GPP/3GPP2 IMS
flavors.
EAST provides test cases for both
originating and terminating sides. EAST
complies IPSec requirement for
accessing HSS.
COPS
COPS (Common Open Policy Service)
protocol is used to exchange policy
information between a policy server
(Policy Decision Point or PDP) and its
clients (Policy Enforcement Point or
NetHawk EAST IMS Data Sheet > 3
APPLICATION SERVERS AND
PEPs), and between IP network nodes. SERVICES
EAST supports COPS and its extensions NetHawk EAST provides support for
for IMS testing.
testing IMS Application Servers, which
offer value-added services, including
H.248, RTP AND OTHERS
SIP Application Server, OSA Application
NetHawk EAST supports H.248 and its
Server and CAMEL IM-SSF.
IMS flavors for both functional and load
testing. It provides Test Cases for both
PTT (Push-To-Talk)/PoC (PTT over
Media Gateway Controller and Media
Cellular), Presence, Conferencing, IM,
Gateway sides. EAST also supports RTP,
etc. are examples of OMA (Open Mobile
IPV4 and IPV6 stacks, SIGCOMP (both
Alliance) and 3GPP/3GPP2 defined IMS
Static and Dynamic), Provisioning (HTTP
standard services.
1.1, SOAP V1.2, XML 1.0 etc.) and QoS
(TOS, DSCP, etc.) testing.
NetHawk EAST for IMS Testing
Figure 4. PacketCable Reference Architecture.
NetHawk EAST supports testing both
Standardized services and customized
services for functional and load testing.
Security Support
IMS IPSec architecture has two parts:
Access security and Network Domain
Security. NetHawk EAST supports both.
From OSI model point of view, EAST
supports Application Layer (HTTP basic
& Digest), Transport Layer (TLS 1.0) and
IP Layer (IPSec).
Quality Measurement
NetHawk EAST supports IMS related
quality measurement for voice and
NetHawk EAST IMS Data Sheet > 4
video. It supports both active testing
(e.g. MOS) and passive testing (E.g. R-
Value)
IP QOS TESTING
NetHawk East as an end to end tester is
able to generate IP traffic supporting
QoS (InitServ and Diffserv). The System
or Device Under Test can be router or
switch. It enables IP classification
testing, multiport traffic generation
and it is possible to simultaneously
transmit and receive IPv4 and IPv6
packets in real time.
FMC/NGN
FMC (Fixed-Mobile Convergence) is
mainly based on ETSI TISPAN NGN (Next
Generation Network) standards
extensible to the 3GPP Release 7 IMS
architecture. It enables seamless
mobility and roaming between Fixed
and Mobile networks. It also offers
flexibility of multiple access networks:
> UMTS, cdma2000, TD-SCDMA, GPRS,
GSM
NetHawk EAST for IMS Testing
> WiFi/WLAN (Bluetooth, WiFi GAN
(UMA), WiFi SIP)
> WiMAX
> Wireline xDSL LAN
> PSTN, PLMN and other Packet Network
> Cable
Packet Cable 2.0 is based on Release 6
of the IMS as developed by the 3GPP.
Packet Cable defines enhancements to
the IMS in order to ensure PacketCable
addresses requirements that are not
addressed by the IMS.
Eventually cable labs enhancements will
be submitted/incorporated in to the
3GPP IMS Specifications.
NetHawk EAST supports end-to-end
testing simulating different access
networks. EAST complies with
3GPP/3GPP IMS (wireless) and ETSI-
TISPAN and Packet Cable (wireline)
standards for testing Network Nodes and
interfaces defined by these standard
bodies.
Specification support
EAST IMS SPECIFICATION SUPPORT –
3GPP
SIP/SDP:
> 3GPP TS 24.228: Signalling Flows for
the IP Multimedia Call Control based
on SIP and SDP (R5 v5.14.0 Dec. 2005)
> 3GPP TS 24.229: IP multimedia call
control protocol based on SIP and SDP
(R5 v7.2.0 Dec. 2005)
Diameter:
> 3GPP TS 29.228: IMS Cx and Dx
Interfaces- Signalling flows and
message contents (R7 v7.0.0 Dec 2005)
> 3GPP TS 29.229: Cx and Dx Interfaces
(R7 v7.0.0 Jan 2006)
> 3GPP TS 29.209: Policy Control of Gq
Interface (R6 v.6.4.0 Dec. 2005)
NetHawk EAST IMS Data Sheet > 5
> 3GPP TS 29.328: IM Subsystem Sh
interface - Signalling flows and
message contents (R7 v7.0.0 Dec 2005)
> 3GPP TS 29.329: Sh Interface based on
the Diameter protocol - Protocol
details (R7 v7.0.0 Dec 2005)
> 3GPP TS 32.299: Diameter Charging
Application (Rf and Ro), (R7 v7.0.0
Dec. 2005)
COPS:
> 3GPP TS 29.207: Policy Control of Go
Interface (R6 v6.5.0 Dec. 2005)
IPSEC:
> 3GPP TS 33.203: Access security for IP-
based services (R7 v7.0.0 Dec 2005)
> 3GPP TS 33.210: IP network layer
security (R7 v7.0.0 Dec 2005)
> 3GPP TS 33.978 - Security aspects of
early IMS (R6 v6.3.0 Dec. 2005)
Megaco:
> 3GPP TS 29.332: MGCF - IM Media
Gateway - Mn Interface (R7 v7.1.0
Dec. 2005)
Services:
> 3GPP TS 23.228: IMS - Stage 2 (R7
v7.2.0 Dec. 2005)
> 3GPP TS 23.218: IM session handling
(R7 v7.0.0 Dec. 2005)
> 3GPP TS 23.279: Combining CS and
IMS services - Stage 2 (R7 v7.1.0 Dec.
2005)
> 3GPP TS 24.229: IP Multimedia Call
Control Protocol based on SIP and SDP
- Stage 3 (R7 V7.2.0 Dec. 2005)
> 3GPP TS 23.976: Push Architecture (R6
v6.1.0 Jun 2004)
> 3GPP TS 23.979: PoC Services - Stage 2
(R6 v6.2.0 Jun 2005)
> 3GPP TS 24.247: Messaging service
using IM Core; - Stage 3 (R6 v6.4.0 Dec
2005)
> 3GPP TS 26.141: IMS Messaging and
Presence; Media formats and codecs
(R7 v7.0.0 Dec 2005)
Camel:
> 3GPP TS 23.078: CAMEL Phase X; Stage
2 (R7 v7.2.0 Dec 2005)
> 3GPP TS 29.078: CAMEL Phase X;
CAMEL Application Part (CAP)
specification (R7 v7.2.0 Dec 2005)
> 3GPP TS 29.278: CAMEL Application
Part (CAP) specification for IP
Multimedia Subsystems (IMS)
(R7 v7.0.0 Dec 2005)
MAP:
> 3GPP TS 29.002: Mobile Application
Part (MAP) specification (R7 v7.2.0
Dec 2005)
Others:
> 3GPP TS 29.240: 3GPP Generic User
Profile (GUP); Stage 3; Network (R7
v6.0.0 Dec 2005)
EAST SUPPORT FOR IMS SIP AND ITS
EXTENSIONS – IETF
> RFC 2976 (October 2000): "The SIP
INFO method".
> RFC 3261 (June 2002): "SIP: Session
Initiation Protocol".
> RFC 3262 (June 2002): "Reliability of
provisional responses in Session
Initiation Protocol (SIP)".
> RFC 3263 (June 2002): " Session
Initiation Protocol (SIP): Locating SIP
Servers".
> RFC 3264 (June 2002): "An
Offer/Answer Model with Session
Description Protocol (SDP)".
> RFC 3265 (June 2002): "Session
Initiation Protocol (SIP) Specific Event
Notification".
> RFC 3311 (September 2002): "The
Session Initiation Protocol (SIP)
UPDATE method".
> RFC 3313 (January 2003): "Private
Session Initiation Protocol (SIP)
NetHawk EAST for IMS Testing
Extensions for Media Authorization".
> RFC 3323 (November 2002): "A Privacy
Mechanism for the Session Initiation
Protocol (SIP)".
> RFC 3325 (November 2002): "Private
Extensions to the SIP for Network
Asserted Identity within Trusted
Networks".
> RFC 3326 (December 2002): "The
Reason Header Field for the Session
Initiation Protocol (SIP)".
> RFC 3327 (December 2002): "Session
Initiation Protocol Extension Header
Field for Registering Non-Adjacent
Contacts".
> RFC 3515 (April 2003): "The Session
Initiation Protocol (SIP) REFER
method".
> RFC 3420 (November 2002): "Internet
Media Type message/sipfrag".
> RFC 3608 (October 2003): "SIP
Extension Header Field for Service
Route Discovery During Registration".
> RFC 3680 (March 2004): "A Session
Initiation Protocol (SIP) Event Package
for Registrations".
> RFC 3428 (December 2002): "Session
Initiation Protocol (SIP) Extension for
Instant Messaging".
> RFC 3455 (January 2003): "Private
Header (P-Header) Extensions to the
SIP for the 3rd-Generation Partnership
Project (3GPP)".
> RFC 3388 (December 2002): "Grouping
of Media Lines in Session Description
Protocol".
> RFC 3581 (August 2003): "An Extension
to the Session Initiation Protocol (SIP)
for Symmetric Response Routing".
> RFC 4028 (April 2005): "Session Timers
in the Session Initiation Protocol
(SIP)".
> RFC 3892 (September 2004): "The
Session Initiation Protocol (SIP)
Referred-By Mechanism".
> RFC 3891 (September 2004): "The
Session Initiation Protocol (SIP)
NetHawk EAST IMS Data Sheet > 6
"Replaces" Header". > RFC 3084: "COPS Usage for Policy
> RFC 3911 (October 2004): "The Session Provisioning (COPS-PR)".
Initiation Protocol (SIP) "Join" Header".
> RFC 3840 (August 2004): "Indicating SIGCOMP:
User Agent Capabilities in the Session > RFC 3485: SIP and Session Description
Initiation Protocol (SIP)" Protocol (SDP) Static Dictionary for
> RFC 3842 (August 2004) "A Message Signaling Compression (SigComp)
Summary and Message Waiting > RFC 3486: Compressing the Session
Indication Event Package for the SIP Initiation Protocol (SIP)
> RFC 4244 (November 2005): "An > RFC 3320: Signaling Compression
Extension to the Session Initiation (SigComp)
Protocol (SIP) for Request History > RFC 3321 – Signaling Compression
(SigComp) - Extended Operations –
Information".
Dynamic Compression
> RFC 3903 (October 2004): "An Event
> RFC 3322: Signaling Compression
State Publication Extension to the
(SigComp) Requirements &
Session Initiation Protocol (SIP)".
Assumptions
> RFC 3857 (August 2004): "A Watcher
> RFC 4077: A Negative
Information Event Template Package
Acknowledgement Mechanism for
for the Session Initiation Protocol
Signaling Compression
(SIP)".
> RFC 3856 (August 2004): "A Presence
HTTP/XML:
Event Package for the Session
> RFC 2616: Hypertext Transfer Protocol
Initiation Protocol (SIP)".
– HTTP 1.1.
> RFC 3603 (October 2003): "Private SIP
> XML 1.0 support.
Proxy-to-Proxy Extensions for
Supporting the PacketCable
RTP/RTCP:
Distributed Call Signaling
> RFC 3550/1889: A Transport Protocol
Architecture".
for Real-Time Applications
> RFC 4145 (September 2005): "TCP-
> RFC 3551/1880: RTP Profile for Audio
Based Media Transport in the Session
and Video Conferences with Minimal
Description Protocol (SDP)".
Control
> RFC 4320 (January 2006): "Actions
Addressing Identified Issues with the
IP Security Type:
SIP Non-INVITE Transaction".
> RFC 4303: IP Encapsulating Security
Payload (ESP) RFC 4303 is the latest
DIAMETER:
spec.
> RFC 3588: Library based on Diameter
> RFC 2406: IP Encapsulating Security
base protocol
Payload (ESP)
> RFC 3589: Diameter Command Codes
for Third Generation Partnership
IPsec ESP Encrytion Algorithms
Project (3GPP) Rel 5
> RFC 2410: The NULL Encryption
Algorithm and Its Use With IPsec
COPS:
> RFC 2451: The ESP CBC-Mode Cipher
> RFC 2753: "A Framework for Policy-
Algorithms (DES-EDE3-CBC)
based Admission Control".
> RFC 3602: The AES-CBC Cipher
> RFC 2748: "The COPS (Common Open
Algorithm and Its Use with IPsec
Policy Service) Protocol".
NetHawk EAST for IMS Testing

IPsec ESP Integrity Algorithms

> RFC 2404: The Use of HMAC-SHA-1-96
within ESP and AH
> RFC 2403: The Use of HMAC-MD5-96
within ESP and AH

Extensible Authentication
> RFC 3310: Hypertext Transfer Protocol
(HTTP) Digest Authentication Using
Authentication and Key Agreement
(AKA)

Key Management
> RFC 4306: Internet Key Exchange
(IKEv2) Protocol
> RFC 4307: Cryptographic Algorithms
for Use in the Internet Key Exchange
Version 2
> RFC 4308: Cryptographic Suites for
IPsec
> RFC 2315: PKCS #7: Cryptographic
Message Syntax Version 1.5

NetHawk EAST IMS Data Sheet > 7

NetHawk EAST for IMS Testing

NETHAWK GLOBALLY
Germany Singapore
Finland (Headquarters) NetHawk GmbH NetHawk Pte. Ltd.
NetHawk Oyj Gmunder Str. 53 390 Orchard Rd., #09-01 Palais Renaissance
P.O. Box 100 München D-81379 238871
FIN-90501 Oulu Germany Singapore
Finland Tel. +49 (0)89 710 48 30 Tel. (65) 67355660
Tel. +358 (0)403 010 300 Fax +49 (0)89 710 48 320 Fax (65) 67357212
Fax +358 (0)403 010 301 Email: sales@nethawk.fi Email: sales@nethawk.fi
Email: sales@nethawk.fi
Hong Kong Sweden
NetHawk Ltd. NetHawk AB
China Room 35, 20/F, Central Tower, Isafjordsgatan 21
NetHawk Ltd. Beijing Representative Office Central, Hong Kong 28 Queen's Road Central, Kista 164 40
Room 2007, Air China Plaza No 36, Xiaoyun Hong Kong Sweden
Road Chaoyang District Tel. +852 2111 1799 Tel. +46 8 632 1940
China Fax +852 2110 0764 Fax +46 8 632 1941
Tel. +86 10 8447 5805 Email: sales@nethawk.fi Email: sales@nethawk.fi
Fax +86 10 8447 5807
Email: sales@nethawk.fi India United States of America
NetHawk Networks India Pvt. Ltd. NetHawk Corporation
France 5th floor, Tower 2000, Mancheswar 3400 Waterview Parkway, Suite 100
NetHawk S.A.R.L. Bhubaneswar, Orissa 751 010 Richardson, TX 75080
Immeuble Sésame, 8 rue Germain Soufflot India USA
Montigny le Bretonneux 78180 Tel. +91 674 2586133 / 3295284 Tel. +1 972-761-9271 and 1866-NETHAWK
France Email: sales@nethawk.fi Fax +1 972- 761-9067
Tel. +33 (0)1 30 64 52 51 Email: sales@nethawk.fi
Fax +33 (0)1 30 64 58 34 Japan
Email: sales@nethawk.fi NetHawk Inc.
Pacific City Nishi-Shinjuku 6F, 3-2-7 Nishi-
Shinjuku, Shinjuku-ku
Tokyo 160-0023
Japan
Tel. +81-3-5339-6748
Fax +81-3-5339-6759
Email: info-j@nethawk.fi

NetHawk EAST IMS Data Sheet > 8