3GPP TSG SA WG2 May 25-28, 1998 Sophia Antipolis, France

TDoc S2-99-340

Title: Date: Source: Key !!ue:

Architecture to Support Multimedia in UMTS May 25-28, 1998

Multimedia "all "ontrol protocol! in #$

ntroduction

The purpose of this paper is to compare and contrast the two different options for supporting a multimedia call control model in UMTS that are presented in Tdoc S2-99339 and propose a way forward.

2 The T%o Alternati&e!

There are two main possibilities. Using H.323 for illustration these are as follows!

2.1

Definition of External H.323 entities:

"n this case the #ate$eeper and the gateway functionality are logically independent of the S#S% and ##S% but are a part of the &'M%. The H.323 peers are the MS and the H.323 #ate$eeper(#ateway. )igure * illustrates this scenario. Thus a mobile wishing to initiate a multimedia call re+uests the establishment of a &,& -onte.t towards the ##S% associated with a H.323 #ate$eeper /#01#0. 2ll signaling between MS and #0 is routed 3ia this &,& conte.t /as stated in 4ption c1. The #0#0 initiates acti3ation of separate &,& conte.t/s1 between MS and #ateway to support the re+uested Multimedia call. The 5oS of this &,& conte.t/s1 is determined by the characteristics of the Multimedia ser3ice.

MS

AN

SGSN

GGSN

!"323 Gate#eeper $ Gate%ay

!"323 si&nalin& peers

Fi&'re 1( )e*inition o* !"323 +ntities in,epen,ent o* the SGSN$GGSN )igure 2 shows the call flow diagram associated with the establishment of an H.323 multimedia in this scenario.

3GPP TSG SA WG2 May 25-28, 1998 Sophia Antipolis, France

Terminal ()#2# ()#2# $ate Keeper

TDoc S2-99-340

S$S'

$$S'

()#2# $ate%ay

0reate P)P 0onte1t e/'est APN23!"323-Gate4eeper

0reate P)P 0onte1t esponse 0reate P)P 0onte1t esponse G 5$G0F 5$ 0F A 5 A0F Set'p 0all Procee, Set'p

Alert Alert 0onnect 0onnect A',io, 6i,eo )ata Trans*er

Figure 2: Call Flow for establishment of a H 323 session for Scenario ! The call flow assumes that the MS is already attached to the "& domain. 2 Mobile wishing to initiate a multimedia call acti3ates a &,& conte.t by sending an 62cti3ate &,& -onte.t7 to the 2&%89H.323-#ate$eeper9. The S#S% locates the appropriate ##S% supporting H.323 gate$eeper functionality from the ,%S and proceeds with the establishment of the &,& conte.t. Thus it is possible to use a H.323 #ateway0eeper local to the ser3ing networ$ or one in the home networ$. 4nce the &,& conte.t has been established the mobile registers with the #0 through the #:5(#-) and ::5(:-) message sets. Subse+uently the H.323 Mobile performs an 2dmission :e+uest /2:51 towards the #0. "f the Mobile is admitted the #0 answers with 2dmission-onfirm /2-)1 otherwise 2dmission:e;ect /2:<1. The mobile finally initiates the H.323 connection by sending a 5.93* Setup message to the #0 when the 2-) has been recei3ed. The #0 answers with a 5.93* -all &roceeding to terminal 2 and sends a 5.93* Setup message to #ateway /or alternati3ely to the destination terminal *1. The #0 then sends the Setup message onto the #ateway for further routing.=3entually the #0 then responds to the mobile with the 2lert and -onnect messages respecti3ely. %ow the mobile and the #ateway can e.change multimedia traffic o3er an :T& stream. %ote that the abo3e illustration is only an e.ample and se3eral additional points must be noted!
1

The call *lo% ill'strate, here ass'-es that a GGSN %ith !"323 Gate%ay capa.ility is re/'ire," 2

3GPP TSG SA WG2 May 25-28, 1998 Sophia Antipolis, France

TDoc S2-99-340

*. 2. The signaling between the ##S%(#ateway and the destination Terminal or #ateway is not shown for simplicity. 3. Similar call flow diagram can be drawn for Mobile terminated H.323 calls.

2.2

Architecture of Tdoc S2-99191

The te*t and +i,ure in thi! !ection i! e*tracted +rom Tdoc S2-99191) )igure 2 shows a Multimedia -all between two H.323 terminals within an "MT-2>>> operator domain. Terminal 2 and ? ha3e performed #ate$eeper "dentification and #ate$eeper :egistration using a ?est =ffort /?=1 :adio 2ccess ?earer /:2?1. Thereafter the terminal 2 sets up a :eal Time /:T1 :adio 2ccess ?earer /:2?1 to decrease the time for the H.323 control signalling. This need of a :eal Time :adio 2ccess ?earer can be indicated from the terminal application to the mobile terminal through the 2pplication &rogramming "nterface /2&"1. The terminal 2 performs &,& -onte.t acti3ation /see figure 21 to set up the :eal Time :adio 2ccess ?earer. )rom now on the established :eal Time :adio 2ccess ?earer can be used for H.22@.> :2S control signalling and 5.93* control signalling. 2fter the :eal Time :adio 2ccess ?earer is established the H.323 terminal 2 performs an 2dmission :e+uest /2:51 towards the #ate$eeper. "f the terminal 2 is admitted the #ate$eeper answers with 2dmission-onfirm /2-)1 otherwise 2dmission:e;ect /2:<1. Terminal 2 initiates the H.323 connection by sending a 5.93* Setup message to the #ate$eeper when the 2-) has been recei3ed. The #ate$eeper answers with a 5.93* -all &roceeding to terminal 2 and sends a 5.93* Setup message to terminal ? on a ?est =ffort /?=1 :adio 2ccess ?earer /:2?1. Terminal ? performs &,& -onte.t 2cti3ation to S#S% and ##S% to set up a :eal Time :adio 2ccess ?earer and performs an 2dmission :e+uest towards the #ate$eeper on this :eal Time :adio 2ccess ?earer. 2fter this terminal ? answers the recei3ed 5.93* Setup message with a 5.93* 2lert and -onnect message to the #ate$eeper on receipt of the 2dmission -on)irm /2-)1 message. The #ate$eeper forwards these two messages to the terminal 2. The :eal Time &rotocol /:T&1 is now established between the terminal 2 and ? for transmission of audio 3ideo or data streams /see figure 21. The #ate$eeper relays the data streams but is not always completely transparent. The #ate$eeper can perform interwor$ing functions e.g. %etwor$ 2ddress Translation /%2T1 etc between different networ$s. The 3oice transcoding is performed end-to-end in the H.323 terminal.

()#2#
/codec1

3GPP TSG SA WG2 May 25-28, 1998 Sophia Antipolis, France UT:2% S$S'
G 5$G0F 5$ 0F

",T-2000 -+erator Domain

TDoc S2-99-340 $$S'

G 5$G0F 5$ 0F

$$S'

$K

S$S'

UT:2%

()#2#
/codec1

7+ A7 Set'p T A7

AP= Acti8ate P)P 0onte1t e/" 0reate P)P 0onte1t e/ 0reate T A7 0reate P)P 0onte1t esp" Acti8ate P)P 0onte1t Acc"
7+ A7

T A7 esta.l"

AP= A 5 A0F Set'p 0all Procee, Set'p AP= 0reate P)P 0onte1t e/ Acti8ate P)P 0onte1t e/" 0reate T A7
Set'p T A7

T A7

0reate P)P 0onte1t esp" Acti8ate P)P 0onte1t Acc" AP= A 5 A0F Alert 0onnect elay Alert 0onnect
T A7 T A7 esta.l"

!"225"@, AS control

!"225"@, 5"931 control

A',io$6i,eo$,ata ; TP<

)igure 3! "MT-2>>> H.323 A H.323 call e.ample

# "ompari!on o+ Alternati&e!
7e*ore %e procee, %ith a co-parison o* the t%o alternati8es %e ass'-e that in .oth cases !"323 is the stan,ar,i9e, call control -o,el *or -'lti-e,ia in :MTS ;this is not the ass'-ption -a,e in T,oc S299191 *ro- %hich the architect're o* section 2"2 has .een e1tracte,<" The ,isa,8anta&es o* not ha8in& a stan,ar,i9e, call -o,el *or -'lti-e,ia are ,isc'sse, in T,oc S2-99339 an, %ill not .e repeate, here" 1" The si&nalin& an, .earer paths in architect're o* section 2"1 are opti-al since a local &ate4eeper an, the -ost appropriate &ate%ay is chosen to ser8e the -'lti-e,ia call re/'est" The sa-e ho%e8er can not .e sai, *or the architect're o* section 2"2 since the &ate4eeper is the one chosen .y the -o.ile ;an, %ill .e locate, in the ho-e net%or4 %hich co'l, .e hal* the %ay aro'n, the %orl,<" The sa-e is tr'e *or the 'ser ,ata strea-s since in proposal o* section 2"2 the &ate4eeper -'st relay those as %ell" =n the architect're o* section 2"2 the -'lti-e,ia call is co-pletely transparent to the :MTS net%or4 an, there*ore it %ill not .e possi.le *or a :MTS operator to pro8i,e either 8al'e-a,,e, ser8ices an,$or .ill *or a -'lti-e,ia call" >n the other han,, the sa-e ,oes not apply to the alternati8e ,escri.e, in section 2"1 "t must be obser#e$ that none of the two architectures $iscusse$ re%uire an& change to e'isting ()*S +rotocols"

2"

3"

3GPP TSG SA WG2 May 25-28, 1998 Sophia Antipolis, France ?"

TDoc S2-99-340

=n .oth cases sea-less han,o8ers can .e achie8e, since all -o.ility is hi,,en *ro- the &ate4eeper an, Gate%ay"

- "onclu!ion! and .ropo!al

Gi8en the ,isc'ssion o* Section 2 an, Section 3 it is propose, that the architect're presente, in section 2"1 is a&ree, as the architect're to s'pport -'lti-e,ia in :MTS" To this en, %e propose that 1" Section 2"1 is incl',e, in section A"? o* +T 23"2@ 2" An BS incl',in& section 2"1 is sent to 0N1 an, 0N3 to in,icate the ,ecisions -a,e re&ar,in& the s'pport o* -'lti-e,ia in :MTS"