M-MGw R2 basics
GSDC Melbourne MGw workshop
EPARASE 5/8/2004
WCMDA call flows
Basic
calls
http://eed.ericsson.se/services/tc-cn/CN_Architecture/open/CN20/2_basic_calls_K.pdf
MGw
selection
http://eed.ericsson.se/services/tc-cn/CN_Architecture/open/CN20/2_MGW-Sel-UG-revA.p
df
Further
reading
http://eed.ericsson.se/services/tc-cn/CN_Architecture/
UE to UE call summary, single MGw context
3. Service and number
analysis, select
media gateway
MSC
Server
20.
Alerting
19.
20.
24.
23.
32.
31.
Alerting
RAB
Connect
assignment
(cont)
acknowledge
response
13.
2.
6.
11.
10.
9.
16.
Call
RAB
1.
12.
RAB
Paging
Call
RAB
SETUP
SETUP
Proceeding
assignment
confirmed
assignment
assignment
response
(UE,
(UE,Arequest
Bresponse
sub)
request
sub)
(from
UE,
B
sub)
(from
(to
UE,
UE,
A
B
sub)
A
B
sub)
(to
(from
(BUE,
subscriber)
(initial
UE,
A
B subscriber)
BUE
subcriber)
subscriber)
message, location report,
GCP
authentication, security mode, setup)
RANAP
22.
28.
30.
4.
14.
25.
21.
27.
29.
15.
5. Seize
26.
Acknowledge
Acknowledge
Connect
Modify
Acknowledge
Resource
(A)
(B)
to Resource
termination
(modify
(Add
(disconnect
(connect
(AMR
(Addrequest
(modify
reply)
=reply)
receive
send/receive)
tonesender)
reply)
tonesender)
(add
create
add
only)
reply)
to new
context,
context,
create termination (B))
(A))
Call connection complete
UTRAN
BTS
RNC
A Sub: AMR send/receive ringing tone
B Sub: AMR inactive send/receive
7. Q.AAL2
Q.AAL2
ERQ
17.
8.
18.
Q.AAL2ECF
ECF
ERQ
(B subscriber connection)
A subscriber
B subscriber
Media
GW
A working example
The following pages will show interesting things to
observe on the MGw node when making a UE to UE call
on a single UMTS string (MSC-MGW-RNC)
This exercise will assume the string is working
(successful calls)
Not designed as a troubleshooting guide, rather to show
how theory is put into practise
Q.AAL2, main GPB6
Ans_aal2ap_proc
- message name
- SUGR parameter
Ans_cpsrc_proc
- froID of Q.AAL2 access point
- channel identifier (CID)
- path identifier
$ lhsh 000600
000600> te e all Ans_aal2ap_proc
000600> te e all Ans_cpsrc_proc
refer to ITU-T
standard Q.2630.1
-Counters do not show AAL2 switching
stats
-ERQ timeouts = resource reserved
but no ERQ received
GCP, main GPB10 (1st VMGw)
For
subsequent VMGws:
- LS1 GPB4, LS2 GPB4 and/or LS3 GPB4
- One VMGw per media gateway controller (MSC)
- VMGw concept updated in R3
contextManager
- GCP message name
- Contexts and terminations
UE to UE call, single GCP context
CONTEXT
TERMINATION (A)
AMR
to A subscriber
TS
TERMINATION (B)
AMR
to B subscriber
UE to UE call, single context
$ lhsh 490400
490400> te e trace1 trace2 trace3 contextManager
choose new context,
termination
for A sub
choose new termination
for context=1,
choose
new
added
context=1
(with
AMRtosend/receive)
termination
for
B
sub
termination
(with(ringing
AMR
add
tone sender
added
to
context=1
tone) toinactive)
termination (A)
stop sending ringing tone
for termination (A)
AMR stream mode set to to MGC to MGw rejects
receive for termination (B)
AMR stream mode set to
send/receive for
clearing
call, move
termination
(B)
termination
(A)
to
newof
Notify MGC of release
context (A)
termination
remove termination (A)
Notify from
MGCcontext
of release of
termination (B)
remove termination (B)
from context
MSF user plane
Resource
access, reservation and
connection of devices
CEP
CEP
CEP
AMR
CEP
TONE SENDER
CPP back plane
UE to UE call, single GCP context, device selection
Device reservation for termination (A side)
$ lhsh
resourcetype1 =
speech coder (AMR)
490400
490400> te enable trace4 Msf_racTop
streamMode3 = send/receive
CEP type = AAL2
CEP ID for internal/external
side and VPI/VCI in back plane
LS1 subrack
Device reservation for termination (B side)
speech coder (AMR)
streamMode0 = inactive
(specified in initial GCP add request
message for B termination. Later
changed to send/receive using GCP
add modify message from MGC)
Reserve another device for termination (A side)
resourcetype2 = tone sender
(for ringing tone, initiated using add
modify message for termination A
from MGC)
GCP context revisited
STREAM SEGMENTS CONNECTION SEGMENT
CONTEXT
TERMINATION (A)
AMR
TERMINATION (B)
TS
AMR
to A subscriber
to B subscriber
STREAM
(AAL2)
Examples of other device selection/call chains:
UE to PSTN call, one context
(eg. co-located MGC and TSC server, single MGw)
connection segment
AMR
adaptive multi-rate
TONE SENDER
ECHO
CANCELLER
UE to UE call, two contexts
(eg. two MGC using BICC logical contexts may reside in same or separate physical MGws)
connection segment
AMR
connection segment
TONE SENDER
MFH
MFH
media frame handler
media frame handler
AMR
UE to PSTN call, two contexts
(eg. one MGC and one TSC server using BICC logical contexts may reside in same or separate physical MGws)
connection segment
AMR
connection segment
MFH
MFH
media frame handler
media frame handler
TONE SENDER
ECHO
CANCELLER
MSC server, RANAP & GCP
RAB assignment request:
ON IN MUAMH SENDRANAPCO
RAB assignment response:
ON OU MUAMH RCVRANAPCO
last updated 05/8/2004
22
GATERM
From ALEX:
Interprets and responds to the orders for connection control
received from the GACON block by putting them in a format that
is meaningful for the Gateway Control Protocol (GCP) and
sending them to the Gateway Control Protocol Handler (GCPH).
Interprets and responds to information on the terminations in
the Media GateWay (MGW) received from the GCPH and
forwards information to the GACON block.
last updated 05/8/2004
23
NSAP (MGw
AE2A address)
BIR (binding
reference = sugr)
last updated 05/8/2004
24
What should I remember?
RANAP
RNC
MSC
server
Q.AAL2
GCP
AAL2
switch
Q.AAL2
MGw1
Establishing termination (A side):
Add Req (choose Ctx, choose Term, specify AMR, request BIR, request AE2A)
Add Reply (Ctx=1, Term = H28000001, BIR=A, AE2A=MGw1)
create Ctx = 1,
create Term = H28000001
Associate term to BIR=A
RAB assignment request
BIR=A, AE2A=MGw1)
ERQ (sugr=BIR=A, AE2A=MGw1)
AAL2 routing on
AE2A=MGw1
ERQ (sugr=A, AE2A=MGw1)
establish connection to
Term = H28000001 using sugr=A
ECF
ECF
RAB assignment response
And a similar scenario for the B termination
Note: for RTDM connections, termination ID is specified in Add Request message from MGC!
