HOTARU(open source IMS) implementation and interoperability tests

NiCT /JGN2Plus / HOTARU Project

OKADA Yukio<okap@nict.go.jp> KEI Mochida<mochida@nict.go.jp>

Summary

HOTARU Project Comparison between SIP and IMS Design and Implementation of HOTARU IOT(SIPit24,SIPit25,Plugfest) results Conclusion and Futureworks

2009/10/14

NiCT

HOTARU Project

Overview system for HOTARU project

host Project leader Technical leader Partner

WIDEproject Hiroshi Esaki (NiCT , The University of Tokyo) Masafumi OE (NAOJ)

NiCT(National Institute of Information and Communications Technology)

NAOJ(National Astronomical Observatory of Japan) SIProp project Intec NetCore NEC-AT NTT-AT Softbank telecom NEC Fujitsu Fusion communication

System for development

2009/10/14

NiCT

Activity condition
NICT office
Associate partner commit 3-5days/week

NICT donate the participate fee of camp

1week Implementation camp (5times/year)

NICT donate the participate fee of IOTs

SIPit23 (2008/10/13-17, Lannion/FRANCE) SIPit24 (2009/5/18-22, Akihabara/TOKYO) SIPit25 (2009/9/14-18, UNH-IOL/USA) IMS Plugfest8(2009/10/5-8, UNH-IOL/USA) IMS Plugtests3(2009/10/16-23,Lannion/FRANCE)

2009/10/14

NiCT

Motivation of HOTARU
Purpose
Knowledge sharing by real-IMS implementation and interoperability tests
reference code implementation participate international IOT(Inter Operability Tests),private tests capability of international competitiveness international interoperate capability

Release as OSS(Open Source Software)

2009/10/14

NiCT

Target of HOTARU
IMS based on 3GPP TS24.229 Rel-8
3GPP collaborate closely with TTC/TTA/ARIB/ATIS/ETSI/3GPP2/ITU-T

Figure. Aspect of 3GPP release

2009/7

Rel-9 Rel-8 Rel-7 Rel-6 Rel-5

Rel-8 freeze

: TS 23.228 : TS 24.229 : TS 33.203 : TS 33.210

1999 2009/10/14

2001

2003

2005 NiCT

2007

2009 7

Scope of HOTARU
UNI: Gm interface CSCF-CSCF: Mw interface NNI: Mm interface ANI interface (TBD)
AS User management DB HSS SLF Circuit switch interconnection BGCF Media control MGCF SGW

service

Diameter
I-CSCF IBCF S-CSCF MGW

PSTN

MRFC MRFP

P-CSCF

P-CSCF IMS Core

Other-IMS

UEP-CSCF interoperability 2009/10/14

Inter-IMS interoperability NiCT

Our scope 8

Comparison between SIP and IMS

Comparison between SIP and IMS(SIP)

SIP(IETF:RFC3261(and 95 docs),RFC5411(index)) The Internet(v4/v6)
UAC: Telephone, softphone, UAS: SIP proxy server(e.g. user Authentication, signaling)

e.g. signaling
REGISTER dialog INVITE originator to destination(SIP/UDP) bearer data stream (RTP/UDP)
SIP(IETF)
SIP Proxy SIP Proxy

UA
2009/10/14

border
NiCT

Bearer(data stream) 10

Comparison between SIP and IMS(IMS)

IMS(3GPP TS24.229 et al)
Core Network with v4&v6&NAT environment
IBCF: Interconnect Border Control Function(Ici)
Filter signaling (remove or hide header)

TrGW: Transport Gateway(Izi)

Transport layer (L3/L4)treatmentIPv6/v4 conversionNAT address hiding

THIG:Topology Hiding Inter-network Gateway

Inter IPv6-IPv4 connectionsecurity

IMS(3GPP)
H.248 Diameter H.248/COPS RTP

S-CSCF P-CSCF PDF

I-CSCF

I-CSCF

S-CSCF P-CSCF PDF GGSN

BCF THIG ALG TrGW border

NiCT

BCF THIG ALG TrGW

UE
2009/10/14

PEP

UE
11

Bearer(data stream)

IMS(Contd)
ITU-T NGN( Recommendation Y.2001 et al) Liaison from ETSI et al.
IMS(Recommendation Y.2021) FMC(Recommendation Y.2808) IMS-based real-time conversational multimedia NGN(Recommendation Y.2211) End-to-end QoS (Recommendation Y.1541) services over

Bring communication protocol Convergence of Network(Diameter, SIP, Cops) Advantage for user Convergence and relationship of services Advantage for telecommunication provider Managing network node complexity and session complexity

2009/10/14

NiCT

12

Comarison between SIP and IMS

Managing Network Complexity

Managing Session Complexity

SIP/ Diameter /Cops (for QoS)

Advanced Function

SIP

encryption, compression, roaming session, IPv4/IPv6/NAT, QoS

IMS

extention
WPS(Wireless Priority Service), ESAP(Public Safety Answering Point)

merit
User: convergence Operator:management

2009/10/14

NiCT

13

Other OSS/BSS IMS implementations

OpenIMSCoreIMS CN subsystem
Develop by Fraunhofer FOKUS Enhanced SER P-CSCFS-CSCFI-CSCFHSS
Older release conforming

Insufficient Transport layer for release8

Mercuro UCT IMS ClientIMS Communicator(UE)

Older release conforming

SDS(BSS: Business support system)

Ericssons simulator Development platform For developer
Older release conforming

Necessity of new OSS which is according with new standard

2009/10/14

NiCT

14

Design and Implementation of HOTARU

HOTARU design
IMS/SIP layering Base Stack Variable Agent Layer
Agent Layer

Action description

BaseStack

TXNUser Layer Transaction Layer Transport Layer HOTARU Stack

Action scenario description

Agent layer message generationmessage receive TXNUser Layer management of user, event-pkg, relation of dialog and transaction , multiple-statement Transaction Layer duplicate reductionre-transmission Transport Layer SIPnetworkI/OsigcompIPsec
NiCT 16

2009/10/14

Specification of Multiple state selector control

Management multiple selector
UserID states selector Multiple DIALOG states selector Session states selector
UserID states selector

DIALOG state selector Session state selector

2009/10/14

NiCT

17

Necessity of IOT
Management of Many nodes, layers and states Carefully review Distributed Documents

2009/10/14

NiCT

18

IOT(InterOperability Tests)results

SIPit24
SIPit(Session Initiation Protocol Interoperability Test) Purpose
focusing particularly on capturing testing information and tracking interoperability Advancing the SIP standards through the IETF

Goal
refine both the protocol and its implementations.

2009/10/14

NiCT

20

SIPit24@Akihabara(2009/5)
NiCT hosted SIPit 24

Descriptions of HOTARU in theSIPit24

HOTARU implementation
3GPP Rel-8 base Apr Freeze UNI Agent(P-CSCF) IOT

REGIST

INVITE

CANCEL

BYE

UPDATE

PRACK

SUBSCRIBE

sigcomp TCP IPsec IPv4 / IPv6

2009/10/14 NiCT 22

UDP

Test infrastructure in the SIPit24

A target Hotaru Domain (based on Open IMS core)

Open IMS Open IMS HSS S-CSCF (IPv4/IPv6) / (TCP/UDP) + IPsec + Sigcomp + SIP Methods *

B C D

Not IMS

Hotaru P-CSCF

Not IMS? Not IMS

UE

E F G
H

* SIP Methods --- REGIST / INVITE / CANCEL .

Not IMS Not IMS

2009/10/14

NiCT

23

Result of SIPit24

IMS or A B C D E F G H
IMS Non-IMS IMS ? General SIP IMS Non-IMS Legacy SIP

capable
IPsec

REGISTRATION
SIGCOMP OK SUBSCRIBE OK OK No-reply of 2ndREGIST OK Implementation problem timeout timeout

INVITE
OK

O O O O O X X O

timeout

AS-system Non-IMS AKAv1 unsupported MD5 connection unsupport

2009/10/14

NiCT

24

Result of SIPit24(Contd)
Time-proven capability(UNI)

Signaling flow
Registration Procedure(IPv4) RegistrationProcedure(IPv6) Call Procedure(IPv4) Call Procedure(IPv6) Subscribe/Notify(IPv4) Subscribe/Notify(IPv6) Non-proven capability(UNI)

SIPextention
sigcmp IPsec(IPv4) IPsec(IPv6)

Renewed results

Implemented
TCP Precondition
2009/10/14 NiCT 25

Wrap up of SIPit24
Focus on IPv6 Few implementer 57% of the implementations supported SIP over IPv6 (This is a big increase over past events, and is related to where the event was held.)(SIPit HP)
typical of Japan 30% in last time(SIPit23)

2009/10/14

NiCT

26

SIPit25(2009/9/14-18)@UNH-IOL
9 interoperability tests
9 Gm interface(UE P-CSCF) tests

Result
3 party are excellent 1 party is almost good

Other partys issue

Implementation miss.
Complicated and distributed standard 3GPP TS issueMissing links

IMS connection capability shortage

Almost SIP

2009/10/14

NiCT

27

IMS Plugfest8(2009/10/5-8)@UNH-IOL
5 tests
2 interoperability Gm interface(UE P-CSCF) tests 3 interoperability Mw interface(P-CSCF CSCFs) tests

Result
1 UE party is excellent 1 UE party is almost good 2 CSCF party are excellent 1 CSCF party is almost good

Other partys issue

Message based Routing issue AKA mechanism Non-default argument

2009/10/14

NiCT

28

Conclusion
We proved as distributed documents and many system states occur complication and misimplementation. We proved necessity of OSS IMS

2009/10/14

NiCT

29

Future work
Public IOTs
IMS Plugtests 3(2009/10/16-23, Lannion/FRANCE)
Gm(UE-P-CSCF) Mw(CSCF) Mm(NNI)

Private IOTs
5 plans

We start to propose relationship with other OSS

2009/10/14

NiCT

30

Thank you.
Grazie. Merci. Danke. Gracias. Kiitos. Obrigado. Obrigada. Tack. Dank u. Grcies. Dkuji.

2009/10/14

NiCT

31