1 Call Origination

This scenario describes call origination in the case that the A2p bearer information is sent from the
serving BS to the serving MSCe in the Assignment Complete message.
MGW MSCe
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
BS
2 3
Serving Network IP Network
MS
5 4
23
IOS: CM Service Request
IOS: Assignment Complete [ 2 ]
SIP: 183 Session Progress [SP!"]
H.248: A [ R#P$ %3$ SP!2$ sen&recv] A [R#P$ %'$ recvonl(]
H.248: Repl( [ SP!3$ SP!' ]
SIP: )*+)#, [SP!'- )AM]
IOS: Assignment Request
SIP: 18. Ringing [ACM] or 183 Session Progress [ACM]
SIP: PRAC/
SIP: 2.. 0/ 1PRAC/2
SIP: PRAC/ 11832
SIP: 2.. 0/ 1PRAC/2
IOS: Be3rer 4p&3te Request [ 3 ]
IOS: Be3rer 4p&3te Response
H.248: M0)56 [SP!3$ Ring73c8 o99] M0)56 [SP!'$ Remote:SP!"$ sen&recv]
H.248: Repl( [ ]
B
Termintion!Si"e #ing$%k
SIP: 2.. 0/ 1)*+)#,2 [A*M]
SIP: AC/
24
Origintion!Si"e #ing$%k
H.248: Repl( [ ]
A
H.248: M0)56 [SP!3$ Ring73c8 on ]
IOS: Be3rer 4p&3te Request [ 3 ]
IOS: Be3rer 4p&3te Response
1
Figure 1 Call Origination (Assignment Complete)
1
1. A CM Service Request message is received by the MSCe.
2. The MSCe sends an Assignment Request message to the BS to request assignment of
radio resources.
. After the radio traffic channel has been established! the BS sends the Assignment
Complete message to the MSCe. The Assignment Complete message contains the BS
connection information "2#! a list of MS codecs and a list of BS transcoders.
$. The MSCe establishes a conte%t &ith a M'(. The ).2$* message consists of t&o ADD
commands. The first ADD command establishes a termination "# to the base station "BS#
for an +T, bearer connection. The termination mode is set to sendrecv. The ADD
command also includes S-,.2 that contains the remote connection information for the
BS that the M'( is to send +T, pac/ets.
The second ADD command establishes a termination! $! to&ards the 0, 1et&or/ for a
bearer channel using +T,. The mode is set to recvonly. The termination is set to this
mode for fraud prevention.
2. The M'( replies to the ).2$* message. The Reply message contains a local S-,.$ for
the termination to the 0, net&or/ and a local S-,. for the termination to&ards the base
station. The local S-,s contain connection information "e.g.! 0, address# and a list of
codecs that the M'( supports for sending and receiving.
3. The MSCe sends a INVITE message to the MSCe including S-,.$! containing an offer
&ith the list of codecs and transcoders supported by the M'(! and an encapsulated IAM.
4. The MSCe receives a 18 Ringing message! if origination.side ringbac/ is to be
provided5 else! a 18! Session "rogress message is received. An ACM is encapsulated in
these messages.
*. 0n response to the 18 Ringing or 18! Session "rogress message! a "RAC# message is
sent to the 0, net&or/.
6. The MSCe receives a $ %# response to the "RAC# message.
%ption&A is included '(en t(e MSCe is instructed to request t(e M)* to provide
origin+tion&side c+ll progress tone, i-e-, it received 18 Ringing in step .-
17. 0f 8ption A9 After receiving the 18 Ringing message! the MSCe sends a /e+rer 0pd+te
Request message to the BS. This contains the M'( connection information! ! including
the bearer format that the BS should be prepared to receive for origination.side ringing.
11. 0f 8ption A9 The BS sends the MSCe a /e+rer 0pd+te Response message.
12. 0f 8ption A9 The MSCe sends an ).2$* message containing an M%DI12 command to the
M'(. The M%DI12 command initiates 8rigination.Side +ingbac/ for termination "#
to&ards the base station.
1. 0f 8ption A9 The M'( ac/no&ledges the ).2$* message &ith a Reply message.
1$. 0f 8ption A9 The M'( sends 8rigination.Side +ingbac/ to the mobile station.
12. The MSCe receives a 18! Session "rogress message containing S-,.2! &hich includes a
selected codec in the S-, ans&er.
13. After receiving the 18! Session "rogress message! the MSCe sends an ).2$* message to
the M'(. This may contain t&o M%DI12 commands.
The first M%DI12 command turns off the 8rigination.Side +ingbac/ "if 18 Ringing &as
received in step 4# and may also modify the codec for termination "# to&ards the base
station.
The second M%DI12 command sets the mode of S-,.$ to sendrecv and includes the
remote S-,.2! containing the connection information for the 0, net&or/.
2
14. The M'( ac/no&ledges the ).2$* M%DI12 message &ith a Reply message.
%ption / is used to select 3e+rer 4orm+t5s6 o44ered 3y t(e /S in t(e Assignment Complete
mess+ge, i4 %ption A '+s N%T included- %ption / is +lso used i4 %ption A '+s included,
3ut t(e 3e+rer 4orm+t5s6 sent to t(e /S in step 1 +re to 3e c(+nged-
1*. 0f 8ption B9 The MSCe sends a /e+rer 0pd+te Request message to the BS. This message
contains the M'( connection information! ! including the bearer format"s# that the BS
should be prepared to receive.
16. 0f 8ption B9 The BS ac/no&ledges &ith the /e+rer 0pd+te Response message.
27. The MSCe sends a "RAC# :+;C232< message to the 0, 1et&or/.
21. The MSCe receives a $ %# response to the "RAC# message.
22. 0f Termination.Side +ingbac/ is provided! then +ingbac/ from the 0, net&or/ is sent
through the M'( and the base station to the calling MS.
2. (hen the call is ans&ered! the MSCe receives a $ %# message ac/no&ledging that the
INVITE message has succeeded. The message encapsulates an ANM.
2$. The MSCe sends a AC# message to the 0, 1et&or/. The AC# message confirms the
reception of the final response! i.e.! $ %#.
3
2 Call Termination
This scenario presents the bearer control &hen the terminating BS=MS capabilities and assignments are
e%changed in the ASS0'1M>1T?C8M,@>T> and B>A+>+?A,-AT> messages.
0t is assumed here that the TBSC "e.g. the terminating BS=MS capabilities and assignments# are sent in
the ASS0'1M>1T?C8M,@>T> message "Step.17! belo&#. )ere! TBSCB includes the transport
address for the serving +A1 and a prioritiCed codec list containing the mobile codec and optionally the
S.BS codec capabilities. Moreover! if the TBSCB is included in the ASS0'1M>1T C8M,@>T>
message! it is not sent in previous messages.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
MSCe ;<R BS
MGW
IOS: PAG)*G R,SP0*S, [ ]
H.248: A [ ]
IOS: ASS)G*M,*# R,=4,S# [ ]
IOS: ASS)G*M,*# C0MP<,#, [#BSC>]
H.248: R,P<6 [ ]
SIP: 183 Session Progress [)S4P>$ SP!A]
H.248: R,P<6 [ ]
SIP: PRAC/ [ ]
SIP: 2.. 0/ 1PRAC/2
IOS: C0**,C#
SIP: AC/ 1)*+)#,2
SIP: )*+)#, [SP!0$ )AM>]
TI&!41: <0CR,= [ #GS)A<]
TI&!41: locreq
IOS: PAG)*G R,=4,S# [0!Be3rer 5orm3t]
IOS: Be3rer 4p&3te Response [ ]
Serving Network IP Network
21
22
SIP: 18. Ringing [ACM>]
A
SIP: 2.. 0/ 1PRAC/2
C
SIP: PRAC/ [ ]
H248: M0)56 [ ]
SIP: 2.. 0/ [A*M>] 1)*+)#,2
IOS: Be3rer 4p&3te Request [#MGWC>]
B
Figure 2 SIP Call to a Local Subscriber in a Serving Network (Assignment Complete)
4
1. 0ncoming call for the subscriber is presented to the serving net&or/ via a INVITE. The
INVITE contains the S-, 8ffer "S-,.8# including the transport address of the
originating side bearer entity and codec list in priority order.
The INVITE could optionally contain an encapsulated IAM "i.e. IAMB! &hich is sho&n in
light letters here to indicate that it is not included in this scenario#.
2. The Serving MSCe sends a 7%CRE8 to the )@+ associated &ith the called MS.
. The )@+ returns a locreq return result. The locreq indicates that the subscriber is being
served by this system.
$. The MSCe pages the terminating mobile "T.MS#. The "A)IN) RE80EST optionally
offers the Serving BSC "S.BSC# the highest priority bearer format in the S-,.8 "e.g. 8.
Bearer?;ormat# if the bearer format identifies a mobile codec.
8ption.A may be included to indicate to the 8riginating MSCe that it is to handle
originating side call progress indication or media.
2. 0f 8ption A9 The serving MSCe returns a 18 Ringing call progress. This indicates to the
8riginating side that the originating side &ill provide call progress media.
1ote9 0t is assumed for this scenario that no IAM &as included in the INVITE in Step.1.
The optional ACM is not included in the 18 Ringing and out of.band call progress is the
responsibility of the originating system.
3. 0f 8ption A9 The 8riginating system ac/no&ledges the prior 18 Ringing &ith a "RAC#.
4. 0f 8ption A9 The "RAC# is ac/no&ledged &ith a $ %#.
*. (hen the T.MS responds to the page! a "A)IN) RES"%NSE is sent from the serving BS
to the serving MSCe.
6. The MSCe responds &ith an ASSI)NMENT RE80EST.
>%isting procedures to establish a traffic channel bet&een the S.BS and T.MS follo& the
ASSI)NMENT RE80EST.
17. The S.BS responds &ith an ASSI)NMENT C%M"7ETE. This response &ill include
TBSCB.
The ne%t steps! labeled as thread B! are dependent on the receipt of the terminating side
capabilities! illustrated in the diagram as TBSC "Terminating BS Capabilities#.
11. Thread B9 The S.MSCe sends a ADD to the S.M'(
Any time after the S.MSCe receives the serving +A1 transport address "TBSC#! it can
request a termination for T2 "at the S.M'( to&ards the originating side# and T! the
termination to&ards the S.+A1.
12. Thread B9 The M'( responds &ith a +eply &ith the requested assignments and
ac/no&ledges the transcoder assignments from the previous step.
1. Thread B9 The MSCe returns a 18! Session "rogress to the originating side containing
the S-,.A! &hich includes the transport address of the S.M'( to &hich the originating
side &ould listen for C, and the codec format that &as chosen by the S.MSCe. This
indicates to the 8riginating MSCe that the serving side is assuming responsibility for
providing call progress "e.g. audible#! to the originating party.
1ote9 The 0SA,B is optional and not included here since an IAM &as not received in the
INVITE in Step.1. ")ad the 0SA,B! been included! it &ould be represented by a C")
indication if 8ption A &as used in the scenario or an ACM if 8ption A &as not chosen.
5
1$. Thread B9 The 8riginating system ac/no&ledges the prior 18! Session "rogress &ith a
,+ACD.
12. Thread B9 The "RAC# is ac/no&ledged &ith a $ %#.
13. The MSCe sends a /e+rer 0pd+te Request! including the TM'(C to let the BS /no& to
&hich port it should be connected. 0nformation about these connections is available
follo&ing the ).2$* operations after Step.11=Step.12.
To minimiCe any possible clipping of the voice &hen the subscriber ans&ers! the BS
&aits to send alert to the MS until after receiving the Bearer Apdate +equest.
Currently the 08S :08S%%%< sends the Alert 'it( In4o message from the BS to the MS
follo&ing Assignment Complete. This is to cause ringing at the MS. This specification
requires changes at the BS to delay the Alert &ith 0nfo "&hen not all bearer connection
information is /no& at the Assignment Complete# until it receives the /e+rer 0pd+te
Request message.
14. This step provides for a /e+rer 0pd+te Response from the BS to the MSCe. This
ac/no&ledges the request in the previous step. This message is still under consideration.
1*. Apon T.MS ans&er! the S.BS responds &ith a C%NNECT.
8ption C9 The serving MSCe prepares for cut.through of the media path and the end of
terminating side call progress.
16. 8ption C9 The serving MSCe prepares for cut.through of the media path. A M%DI12 is
sent to the M'( remove the call progress indication if it &as provided "e.g. in Step.11#.
27. 8ption C9 The M'( ac/no&ledges the changes &ith a Reply.
21. Any time after Step.1* MSCe ac/no&ledges the connect &ith a $ %# to close out the
INVITE in Step.1
1ote9 The optional ANMB is not included here! since the IAM is not received in the
INVITE in Step.1.
22. The 8.MSCe responds &ith an AC# to the $ %# 5INVITE6.
6
3 Call Clearing
Call Clearing Initiated By The MS
MGW MSCe
1
2
3
4
5
6
7
BS
2 3
Serving Network
MS
4
IOS: C<,AR R,=4,S#
SIP: 2.. 0/ 1B6,2
IOS: C<,AR C0MMA*
IOS: C<,AR C0MP<,#,
H.248: S4B#RAC# [3] S4B#RAC#[']
H.248: Repl( [ ]
SIP: B6,
1
Figure 3 Call Clearing Initiated by te !S (SIP)
1. The serving BS decides to terminate the call and sends a Cle+r Request message to the
serving MSCe.
2. The serving MSCe sends a /2E message to notify the other party.
. The serving MSCe receives a $ %# 5/2E6 message in response to the /2E message.
$. Apon receipt of the Cle+r Request message in Step 1! the serving MSCe responds to the
serving BS by sending a Cle+r Comm+nd message.
2. The serving BS returns a Cle+r Complete message to the serving MSCe.
3. Apon receipt of the Cle+r Request message in Step 1! the serving MSCe sends t&o
S0/TRACT command to the serving M'( to remove terminations and $.
4. The serving M'( responds to the serving MSCe &ith a Reply message.
Call Clearing Initiated By The Network (SIP)
7
MSCe MGW
1
2
3
4
5
6
BS
7 5
Serving Network
MS
6
SIP: 2.. 0/ 1B6,2
IOS: C<,AR C0MMA*
IOS: C<,AR C0MP<,#,
H.248: S4B#RAC# ["] S4B#RAC# [?]
H.248: Repl( [ ]
SIP: B6,
8
Figure 4 Call Clearing Initiated by te Network (SIP)
1. A /2E message is received by the serving MSCe.
2. The serving MSCe sends a $ %# 5/2E6 message in response to the /2E message.
. Apon receipt of the /2E message in Step 1! the serving MSCe sends a Cle+r Comm+nd
message to the serving BS.
$. The serving BS returns a Cle+r Complete message to the serving MSCe.
2. Apon receipt of the /2E message in Step 1! the serving MSCe sends t&o S0/TRACT
commands to the serving M'( to remove terminations 2 and 3.
3. The serving M'( responds to the serving MSCe &ith a Reply message
8
4 Handof
Handof-Forward
A media e%change is already established bet&een the mobile subscriber in the Anchor System and the
B.,arty served in another system. -ue to the topology! the initial e%change is illustrated here in folded
fashion "B#.E"$#"2#.E"3#.E"MS#.
MGW MSCe
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
B!P3rt(
B!P3rt(
MS
MGW
9
BS
10
BS
6 5
&n%'or Network Trget Network
MSCe
MS
4
4
7 8
23
24
IOS: ;A*055 R,=4)R,
TI&!41: 5AC)R2 [ vC)C ]
IOS: ;A*055 R,=4,S#
SIP: 2.. 0/ 1)*+)#,2 [SP!8]
H.248: A [ %8- %@- sen&recv]
H.248: Repl( [ SP!8- SP!@ ]
IOS: ;A*055 R,=4,S# AC/ [ 1. ]
IOS: C<,AR C0MMA*
IOS: C<,AR C0MP<,#,
H.248: A [ R#P$ %A$ sen&recv]
H.248: Repl( [ SP!A ]
IOS: B,AR,R 4PA#, R,=4,S# [ @ ]
IOS: B,AR,R 4PA#, R,SP0*S,
IOS: ;A*055 C0MM,*C,
IOS: ;A*055 C0MP<,#,
TI&!41: 93c&ir2
H.248: S4B#RAC# ["]
IOS: ;A*055 C0MMA*
TI&!41: MS0*C; [ ]
H.248: Repl( [ " ]
SIP: )*+)#, [ SP!A- vC)C ]
HOT(12
H.248: M0)56 [ SP!A$ Remote:SP!8 ]
H.248: Repl( [ SP!A ]
SIP: AC/
Figure 5 "ando## $orward between two L!S% Step & Systems
9
1. 0t is determined that a )ard )andoff "))8# is necessary bet&een the Anchor and Target
1et&or/s. A 9AND%11 RE80IRED message is sent from the serving Anchor BS to the
Anchor MSCe containing the list of ))8 candidate cells.
2. The Anchor MSCe sets up the bearer information at the Anchor M'(. An ADD
command requests a M'( termination "4# to be associated &ith the Target system.
. The Anchor M'( ac/no&ledges the results of the ADD &ith a Reply containing the
initial S-, for M'( termination 4.
$. MSCe to initiate a )andoff.;or&ard tas/. The 0nterMSCCircuit0- of the 1ACDIR$
message contains a Fvirtual Circuit 0dentification CodeG "vC0C# value. The vC0C is used
to indicate that an 0, bearer facility is to be used in the hand.off. This allocation of inter.
MSCe capabilities and vC0C assignment is by prior agreement. A value of the
0nterMSCCircuit0- parameter in the vC0C range is also the trigger to the Target MSCe to
initiate a pac/et handoff! and that it should receive a INVITE! if one has not already been
received.
2. The Anchor MSCe sends a INVITE to the Target 1et&or/. The INVITE contains the
bearer address "4# and the codecs offered by the Anchor System. The vC0C value is
included to allo& the Anchor MSCe to associate the INVITE &ith the previously received
1ACDIR$ "Step $#! or to e%pect a 1ACDIR$! if it &as not previously received.
ContributorHs 1ote9 0t is suggested that the vC0C parameter in the S0, 01I0T> may ta/e
one of the follo&ing forms9
INVITE SIP:0xaaaa@host;user=vcic SIP/2.0, or
INVITE SIP:vcic-0xaaaa@host SIP/2.0
(here aaaa is a he% string representing the 2 binary octets of the 0nterMSCCircuit0-
parameter defined in T0A.$1. The host field is in the form of a domain name or an 0,
address and identifies the Anchor MSCe.
3. Apon receiving both the 1ACDIR$ and the INVITE! the Target MSCe sends the
9AND%11 RE80EST to the Target BS. 0n this case the 9AND%11 RE80EST is used to
trigger an offer of BS capabilities at the Target BS.
4. The BS responds &ith a 9AND%11 RE80EST AC#! and includes the 0, address and
codec capabilities for the BS termination "17#.
*. Apon receiving the 9AND%11 RE80EST AC#! the Target MSCe sends a ADD
command to the Target M'( requesting t&o terminations! one to be paired &ith the
Anchor M'(! and another termination from the Target M'( to&ards the Target BS! i.e.
"*# and "6#! respectively.
6. The Target M'( responds &ith the S-, information for the t&o terminations.
17. A /EARER 0"DATE RE80EST message is sent to the Target BS &ith the M'( 0,
address "6# and selected codec.
11. The Target BS responds &ith a /EARER 0"DATE RES"%NSE message.
12. The Target MSCe sends a 4+cdir$ to the Anchor MSCe.
1. The Target MSCe sends a $ %# 5INVITE6 &ith the S-, ans&er containing the address
and codec for the Target M'( termination *.
1$. ;ollo&ing the receipt of the $ %# from the Target system! the Anchor MSCe updates
the bearer information at the Anchor M'(. An M%DI12 command updates the M'(
termination "4# to be associated &ith "*# in the Target system.
12. The Anchor M'( ac/no&ledges the results of the M%DI12 &ith a Reply.
13. The Anchor MSCe sends a AC# to the Target MSCe in response to the $ %#.
10
14. Anytime after receipt of the 4+cdir$ "Step 12#! the Anchor MSCe sends a 9AND%11
C%MMAND to the Anchor BS and the MS FretunesG for the hand.off.
1*. The Anchor BS sends a 9AND%11 C%MMENCED to the Anchor MSCe &hen it detects
the MS has retuned.
16. The Target BS sends the MSCe a 9AND%11 C%M"7ETE message &hen it detects the
MS has established communication &ith the Target BS.
27. The Target MSCe sends the Anchor MSCe a Mobile 8n Channel! MS%NC9! message to
indicate that the handoff is complete on the Target 1et&or/.
The hand off is a success &hen the Anchor MSCe receives either the 9AND%11
C%MMENCED or the MS%NC9 or both.
21. The Anchor MSCe uses the S0/TRACT command to remove the bearer path to the
Anchor BS "2#.
22. 8nce the mobile is on channel in the target system "Step 27#! the MSCe sends a C7EAR
C%MMAND to the BS.
2. The Anchor M'( ac/no&ledges the S0/TRACT &ith a Reply.
2$. The Anchor BS responds to the C7EAR C%MMAND "Step 22# &ith a C7EAR
C%M"7ETE.
11