08- Session on Signalling, ISUP Release Cause Mapping...

ww

w.i3fo

rum

.org

i3 FORUM

Why we need a single

SIP <--> ISUP Release

Cause mapping

presented by

Dr. Ragnar Huslende

Ericsson

3GPP CT3 Chairman

May 26, 2011

Agenda

Wh

y is a

n u

na

mb

igu

ou

s S

IP

IS

UP

ma

pp

ing

im

po

rta

nt?

Wh

y c

oop

era

tio

n w

ith

3G

PP

Wo

rkin

g

Gro

up

CT

3 o

n m

ap

pin

g?

Su

mm

ary

of

ach

ieve

d r

esu

lts

Oth

er

po

ten

tia

l a

rea

s o

f fu

ture

co

op

era

tio

n

Basic reference architecture

Carrier 1

Carrier 2

Carrier N

Service

Provide A

Service

Provide A

Service

Provide A

Service

Provide B

SIP or ISUP

SIP or ISUP

SIP or ISUP

SIP or ISUP

VoIP,

TDM,

MNO,...

VoIP,

TDM,

MNO,...

Potentially many protocol mappings in the end-to-end path

End users

End users

Incorr

ect call

ha

nd

ling

E.g

. C

V 3

4 (

Lack o

f netw

ork

resourc

es) �

Re-r

outing, w

hile

CV

17 (

User

busy)

�N

o r

e-r

outing

Accou

ntin

g inaccura

cie

s d

ue t

o incorr

ect

dis

con

nect cause v

alu

es s

tore

d in C

DR

s

Impro

per

opera

tio

na

l han

dlin

g o

f S

LA

s b

etw

een

carr

iers

/op

era

tors

KP

I sta

tistics b

ased o

n C

V r

eport

ing m

ay g

ive w

rong v

alu

es e

.g. fo

r N

ER

, A

SR

Ineff

icie

nt O

&M

, tr

oub

le s

ho

otin

g:

Try

ing to f

ix the ”

wro

ng”

pro

ble

m

Dia

logue b

etw

een o

pera

tors

/carr

iers

Dia

logue w

ith v

endors

Possible implications of incorrect mapping

Disconnect Cause Value Mapping

Desired Behaviour(i3 Forum)

•M

appin

g G

ranula

rity

:•

A R

esponse C

ode o

r C

ause V

alu

e (

CV

) sh

ould

be u

sed in

only

on

e m

app

ing

•M

appin

g S

tabili

ty:

•W

hen t

he m

ap

pin

g g

ives t

he s

am

e r

esults r

egard

less o

f ho

w m

an

y f

urt

her

convers

ion

s t

ake p

lace

•S

ym

metr

ic M

appin

g:

•A

one-t

o-o

ne m

appin

g in b

oth

directio

ns t

ha

t is

inhere

ntly

sta

ble

, e.g

.:

•C

V 2

4 �

SIP

Respo

nse 4

33 �

CV

24

•S

IP R

esponse 4

33 �

CV

24 �

SIP

Respon

se 4

33

•Q

oS

/KP

I pre

serv

ation:

•A

void

map

pin

g f

rom

”U

ser

Cla

ss”

event

to ”

Netw

ork

Cla

ss”

event

and v

.v.

Network Effectiveness Ratio (NER)

NE

R is the a

bili

ty o

f

netw

ork

s to

deliv

er

calls

to

the fa

r-end t

erm

inal.

NE

R =

the r

ela

tionship

betw

een

the

num

ber

of

seiz

ure

s a

nd the

sum

of

the

num

ber

of

seiz

ure

s r

esultin

g

in e

ither

an

•answ

er

message, o

r

•a u

ser

busy,

or

•a r

ing n

o a

nsw

er,

or

•te

rmin

al

reje

ction/u

navaila

bili

ty.

Unlik

e A

SR

, N

ER

exclu

des

the e

ffects

of custo

me

r

behavio

ur

and te

rmin

al

behavio

ur.

% C

om

ple

ted

Seiz

ure

s

% N

etw

ork

Failu

res %

User

Failu

res

NER

ASR

ITU

-T R

ec.

E.4

25

Three approaches for interworking with ISUP

•S

IP R

eason H

eader

(RF

C 3

326)

–C

an inclu

de I

SU

P c

ause v

alu

es

–S

IP s

erv

ers

/clie

nts

are

fre

e t

o ignore

this

he

ader

field

–H

as n

o im

pact

on p

roto

co

l pro

cessin

g (

e.g

. R

e-r

outin

g)

–Locatio

n f

ield

info

is lost

(e.g

. N

etw

ork

/User

info

for

NE

R

calc

ula

tions)

•S

IP-I

in the c

arr

ier

netw

ork

–IS

UP

info

is p

reserv

ed b

y e

ncapsula

tion

–If

severa

l chain

ed c

arr

iers

, th

en inte

rwork

ing w

ith o

ther

inte

rcon

nect

types m

ay c

ause

inconsis

tencie

s,

e.g

. if

mappin

g t

o n

ative S

IP (

cf.

IM

S)

is e

ventu

ally

require

d.

•D

irect m

appin

g: S

IP S

tatu

s C

odes IS

UP

Cause V

alu

es

Available Mapping Standards

ITU

-T Q

.1912.5

3G

PP

TS

29.1

63 ”

Inte

rwork

ing B

etw

een I

P M

ultim

ed

ia

Netw

ork

s a

nd C

ircu

it S

witched N

etw

ork

s”

IET

F R

FC

339

8

Example of inconsistencies:

RFC 3388 :

ISU

P 2

”No r

oute

to n

etw

ork

”�

SIP

500

”Serv

er

inte

rnal err

or”�

ISU

P 1

”Unallo

cate

d/u

nassig

ned n

um

ber”

Q.1912.5:

ISU

P 2

”No r

oute

to n

etw

ork

”�

SIP

500

”Serv

er

inte

rnal err

or”�

ISU

P 127

”Inte

rwork

ing u

nspecifie

d”

In neither case the original

cause value is preserved

•No mapping is perfect, select the

most suitable standard

•Use the same standard in all the

interconnected networks

Agenda

Wh

y is a

n u

na

mb

igu

ou

s S

IP

IS

UP

ma

pp

ing

im

po

rta

nt?

Wh

y c

oop

era

tio

n w

ith

3G

PP

Wo

rkin

g

Gro

up

CT

3 o

n m

ap

pin

g?

Su

mm

ary

of

ach

ieve

d r

esu

lts

Oth

er

po

ten

tia

l a

rea

s o

f fu

ture

co

op

era

tio

n

About 3GPP

3rd

Genera

tion

Part

ners

hip

Pro

ject

3G

PP

is a

colla

bora

tive a

ctivity b

etw

een t

he f

ollo

win

g s

tan

dard

s

develo

pm

ent

org

aniz

ations (

Opera

tio

nal P

art

ners

, O

Ps):

376 I

ndiv

idu

al m

em

ber

com

panie

s h

ave jo

ined t

he p

art

ners

hip

via

the O

Ps.

(JA

PA

N)

(US

A)

(CH

INA

)

(EU

RO

PE

)(K

OR

EA

)(J

AP

AN

)

Cre

ate

d in 1

99

8 w

ith the s

cope t

o s

pecify a

3G

Mobile

Syste

m

Subseq

ue

ntly took o

ver

responsib

ility

for

GS

M (

2G

)

specific

atio

ns

LT

E &

EP

C h

igh-s

pee

d M

obile

Syste

ms

”Com

mon I

MS

”(input from ETSI TISPAN (fixed netw.), 3GPP2, ....)

Fix

ed/m

obile

inte

rwork

ing/c

onve

rgence

etc

.

About 3GPP

Scope of work

About 3GPP

Market Representation Partners

IMS

Fo

rum

TD

-Fo

rum

GS

A

GS

M A

ssocia

tion

IPV

6 F

oru

m

UM

TS

Fo

rum

4G

Am

ericas

TD

SC

DM

A Indu

str

y A

lliance

Info

Com

munic

ation U

nio

n

Fem

to F

oru

m

CD

MA

Develo

pm

ent

Gro

up

Cellu

lar

Opera

tors

Associa

tion o

f In

dia

(C

OA

I)

NG

MN

Alli

ance

About 3GPP

Some ways of working

17

Wo

rkin

g g

rou

ps, ty

pic

ally

4-7

me

etin

gs p

er

ye

arGERAN

x W

Gs (

GS

M E

DG

E R

adio

Access N

etw

ork

s)

RAN

x W

Gs (

Radio

Access N

etw

ork

s)

SA

x W

Gs (

Serv

ice &

Syste

ms A

spects

)

CT

x W

Gs (

Core

Netw

ork

& T

erm

inals

), e

.g. CT3

: In

terw

ork

ing, polic

y c

ontr

ol

Wo

rkin

g b

y c

on

sen

su

s

Ne

w R

ele

ase

s e

ve

ry 1

-1

.5 y

ea

rs

Active

ma

inte

na

nce

of

old

, ”f

roze

n”

rele

ase

s v

ia

Ch

an

ge

Re

qu

ests

”

Liv

ing

sp

ecific

atio

ns”

And, note that ......

Many o

f th

e i3 F

oru

m m

em

bers

are

als

o m

em

bers

of 3G

PP

!

Agenda

Wh

y is a

n u

na

mb

igu

ou

s S

IP

IS

UP

ma

pp

ing

im

po

rta

nt?

Wh

y c

oop

era

tio

n w

ith

3G

PP

Wo

rkin

g

Gro

up

CT

3 o

n m

ap

pin

g?

Su

mm

ary

of

ach

ieve

d r

esu

lts

Oth

er

po

ten

tia

l a

rea

s o

f fu

ture

co

op

era

tio

n

3GPP –i3Forum

SIP Status Code

� ��ISUP Cause Value Mapping

Mapping agreed for 3GPP TS 29.163 for Rel-7 with mirrored changes agreed

also for Rel-8, Rel-9 and Rel-10. Available in versions equal to or higher than:

•v 7.22.x (for Rel-7)

•v 8.14.x (for Rel-8)

•v 9.5.x (for Rel-9)

•v 10.1.x (for Rel-10)

Agreed Change Requests can be found here:

•http://w

ww

.3gpp.o

rg/ftp

/tsg_ct/W

G3_in

terw

ork

ing_ex-

CN

3/T

SG

C3_61_Lju

blja

na/D

ocs/

•http://w

ww

.3gpp.o

rg/ftp

/tsg_ct/W

G3_in

terw

ork

ing_ex-

CN

3/T

SG

C3_62_S

alt%

20Lake%

20C

ity/D

ocs/

All versions of 3GPP TS 29.163 can be found here:

•http://w

ww

.3gpp.o

rg/ftp

/Specs/h

tml-in

fo/2

9163.h

tm

i3F / 3GPP Agreed Changes

3GPP TS 29.163

Deutsche Telekom, ATT,

Telecom Italia

Mapping of SIP Response 604 to

ISUP Cause Value 2

C3-110402

C3-110670

C3-110671

C3-110672


Telecom Italia

Mapping of ISUP Cause Value 88 to

Response 606 and vice versa

C3-110266

C3-110267

C3-110268

C3-110269


Telecom Italia

Change of Cause code mapping

C3-110262

C3-110263

C3-110264

C3-110265


Telecom Italia

New Cause Code mappings of CV

23,38-47 and 65-79

C3-110258

C3-110259

C3-110260

C3-110261

Source Companies

Title

3GPP Doc.

Numbers

(Rel-7/8/9/10)

Agreed Changes: Interworking from ISUP to SIP (Part 1)

Receipt of REL message

503 Service Unavailable

Cause value No 47 (Resource unavailable, unspecified)

(class default)

500 Server Internal error

Cause value No 46 (Precedence call blocked)


Cause value No 44 (Requested channel not available)


Cause value No 43 (Access inform

ation discarded)


Cause value No 42 (Switching equipment congestion)


Cause value No 41 (Temporary failure)


Cause value No 38 (Network out of order)

501 (Not Implemented)

Cause value No 29 (Facility rejected)

410 Gone

Cause value No 23 (Redirection to new destination)

603 Decline IF location field is set to user

ELSE 403 Forbidden

Cause value No 21 (Call rejected)

604 Does not exist anywhere

Cause value No 3 (No route to destination)


Cause value No 2 (No route to specified transit network)

SIP Message, Status Code

REL Message, Cause Indicators parameter

Agreed Changes: Interworking from ISUP to SIP (Part 2)

Receipt of REL message

Cause value No111 (Protocol error, unspecified) (class default)

Cause value No 103 (Parameter non-existent or not implemented, passed

on)

Cause value No 98 (Message not compatible with call state or message

type non-existent or not implemented)

Cause value No 88 (Incompatible destination)

Cause value No 79 (Service or option not implemented, unspecified)(class

default)

Cause value No 70 (Only restricted digital inform

ation capability is

available)

Cause value No 69 (Requested facility not implemented)

Cause value No 65 (Bearer capability not implemented)

Cause value No 63 (Service option not available, unspecified) (class

default)

Cause value No 58 (Bearer capability not presently available)

Cause value No 57 (Bearer capability not authorised)

Cause value No 50 (Requested facility not subscribed)

REL Message, Cause Indicators parameter

400 Bad Request

501 Not Implemented

501 Not Implemented

606 Not Acceptable

501 Not Implemented

501 Not Implemented

501 Not Implemented


501 (Not Implemented)


603 Decline

488 Not acceptable here

SIP Message,

Status Code

Agreed Changes: SIP to ISUP mapping

Receipt of SIP Status Codes 4xx, 5xx, 6xx

606 Not Acceptable


502 Bad Gateway

501 Not implemented

488 Not acceptable here

421 Extension required

420 Bad Extension

416 Unsupported URI scheme

414 Request-URI too long

408 Request Timeout

403 Forbidden

400 Bad Request

4xx/5xx/6xx SIP Message

Cause value No 88 (Incompatible destination)

Cause value No 2 (No route to specified transit network)

Cause value No 27 (Destination out of order)

Cause value No79 (Service or option not implemented,

unspecified)

Cause value No50 (Requested facility not subscribed)

Cause value No111 (Protocol error, unspecified)




Cause value No102 (Recovery on timer expiry)

Cause value No79 (Service or option not implemented,

unspecified)


REL Message (cause value)

Agenda

Wh

y is a

n u

na

mb

igu

ou

s S

IP

IS

UP

ma

pp

ing

im

po

rta

nt?

Wh

y c

oop

era

tio

n w

ith

3G

PP

Wo

rkin

g

Gro

up

CT

3 o

n m

ap

pin

g?

Su

mm

ary

of

ach

ieve

d r

esu

lts

Oth

er

po

ten

tia

l a

rea

s o

f fu

ture

co

op

era

tio

n

3GPP Networks External Networks

TS

29

.163

Some interworking scenarios covered by CT3

TS

29.1

64

TS

29

.235

CS

(BICC or ISUP)

CS

(SIP-I)

CS

(BICC or ISUP)

CS

(BICC or ISUP)

CS

(SIP-I)

CS

(BICC or ISUP)

TS

29

.235

TS

29

.235

TS

29

.235

TS

29

.163

TS

29

.235

TS

29

.163

TS

29

.235

TS

29.1

63

TS

29

.163

TS

29

.235

TS

29.1

65

TS

29

.235

TS

29

.235

TS

29

.235

TS

29

.235

TS

29

.235

TS

29

.235

IMS

IMS

IMS

SIP

SIP

SIP

SIP

IMS

IMS

IMS

IMS

IMS

IMS

IMS

II-N

NI

CS

(ISUP)

CS

(SIP-I)

SIP

-ba

se

d

ne

two

rk

SIP

-I -

ba

sed

ne

two

rk

II-NNI

=

Inte

r-IM

S

Ne

tw-N

etw

Inte

rfa

ce

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

TS

29

.163

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

TS

29.1

63

TS

29

.163

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

TS

29.1

65

TS

29.1

63

TS

29

.163

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

TS

29

.162

/29

.061

TS

29.1

65

TS

29.1

63

TS

29

.163

TS

29

.235

TS

29

.235

TS

29.1

64

TS

29

.235

TS

29

.235

Policy Control (QoS, Charging)

PLMN

To/fro

m

oth

er

netw

ork

s

QoS

(Q

oS

Cla

ss Identifier,

bandw

idth

,

allo

cation/r

ete

ntion

priorities,M

)

Specia

l charg

ing p

er

applic

ation

Gold

/silv

er/

bro

nze

subscriptions

Blo

ckin

g o

f unallo

wed

traffic

Month

ly s

ubscription p

lans

etc

.

Polic

y c

ontr

olle

r can s

tore

polic

y r

ule

s for

the local

netw

ork

in the

ga

tew

ay p

er

user

sessio

n:

IMS

Packet

Gate

wa

y

Polic

y

Contr

olle

r

Other areas of common interest ?

Optim

al M

edia

Routing (

IMS

)R

em

ovin

g n

odes fro

m the e

nd-t

o-e

nd m

edia

path

Allo

win

g f

lexib

le b

usin

ess m

odels

Se 3

GP

P T

S 2

9.0

79

IP Inte

rconnection o

f S

erv

ices

Carr

ier-

gra

de e

2e p

erf

orm

ance b

etw

een u

sers

connecte

d to d

iffe

rent

netw

ork

s

Ref. e.g

IP

X w

ork

in G

SM

A

Ongoin

g w

ork

on s

erv

ice r

equirem

ents

and a

rchitectu

re in 3

GP

P g

roups

SA

1 a

nd S

A2

Hig

h-D

efinitio

n V

ideo C

onfe

rencin

g / T

ele

pre

sence,

(IM

S-b

ased)

?

Further contact with 3GPP

If y

our

com

pany is a

3G

PP

mem

ber,

just ta

lk to

your

colle

ague b

ein

g a

3G

PP

dele

gate

Bro

wse t

he w

eb:

ww

w.3

gpp.o

rg

All

3G

PP

specific

ation

s, m

eeting d

ocum

ents

,

work

pla

ns,

etc

can b

e d

ow

nlo

ad

ed f

rom

the

we

b

Fee

l fr

ee to c

onta

ct th

e C

ha

irm

an o

f th

e

rele

vant

Work

ing G

roup ☺

ww

w.i3fo

rum

.org

i3 FORUM

Thank You!

08- Session on Signalling, ISUP Release Cause Mapping...

Documents

Transcript of 08- Session on Signalling, ISUP Release Cause Mapping...