MSS All IP and

A over IP
Agenda
› General: All IP
› Iu over IP (condensed)
› A over IP: MSC-S
› A over IP Codec handling
› A over IP: M-MGw
› Network Aspects
› A over IP Migration

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 2

General
All IP MSS transport
› IP as converged transport technology
for all network domains (Access, CS
Today Core, PS Core, IMS etc.)
IMS

BSC
TDM TDM › Scales easy with growing traffic
M-MGw MSC-S

IP transport POI
RNC
TDM › Bandwidth efficiency through
ATM compressed speech and IP
Multiplexing

› Superior speech experience: end-2-

End TrFO and Wideband speech
interworking across interconnect
border
A over IP MSS All IP
IMS
BSC
IP
M-MGw MSC-S

IP transport POI
IP
RNC
IP
Nb over IP Mb
Iu over IP

All-IP in CN and towards RAN and POI

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 4
Iu over IP
All IP MSS transport
Iu over IP

IMS

BSC
TDM TDM
M-MGw MSC-S

IP transport POI
TDM
RNC
ATM

MSS All IP
IMS
BSC
IP
M-MGw MSC-S

IP transport POI
IP
RNC
IP
Broad deployment, also towards other vendor RNCs
Iu over IP Message from field: “9 MSC-S, 13 MGWs and 12 RNC nodes. So as of
today, all customer WCDMA nodes are on Iu cs over IP. No major
drama in the deployment. Pretty much routine.”

Available from MSS 5.1

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 6
Iu CS over IP, Protocol Stack
RANAP
SCCP BICC
M3UA Iu over IP CP
MSC-S MSC-S
SCTP
IPv4
Data Link
GCP GCP
Phys

RNC Iu CS over IP UP Nb over IP UP

M-MGw M-MGw
Iu UP Nb UP
RTP RTP
Iu framing UDP UDP
IPv4 IPv4
Data Link Data Link
Phys Phys

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 7

Iu CS bearer Selection – Determined by RNC
definition in the MSC-S
/ \
| ,RNCID=rncid, GLCNID=glcid |
| |
| ,RNCCODEC=rnccodec... |
| |
| / \ |
MGRIC:RNC=rnc+ | ALL | +;
| ,RRNCCODEC=+ + |
| | rrnccodec... | |
| \ / |
| |
| ,TB=tb TB=tb Transport Bearer |
\ / Bearer (TB)
The parameter indicates the Transport
supported by the RNC.
0 - ATM (default)
1 - IP
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 8
A over IP: MSC-S
All IP MSS transport
A over IP
Today
IMS

BSC
TDM TDM
M-MGw MSC-S

IP transport POI
TDM
RNC
IP

A over IP MSS 6.1

IMS
BSC
IP
M-MGw MSC-S

IP transport POI
IP
RNC
IP

Available from MSS 6.1

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 10
A-interface
› A-interface Control Plane (CP) signaling over IP
(SIGTRAN) has been introduced in 3GPP Release 7.
Ericsson MSS already supports SIGTRAN based A-
interface signaling from MSC-S R11 for MSS 3.1
› A-interface User Plane UP supported in MSS 6.1,
specified in 3GPP Release 8 specification1
– Support of IP transport for A-IF UP
– Codec handling
– Migration from TDM based to IP based A-IF UP interface

1
See relevant 3GPP specs in the speaker notes
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 11
A over IP, Protocol Stack
BSSAP
SCCP BICC
M3UA A over IP CP
MSC-S MSC-S
SCTP
IPv4
Data Link
GCP GCP
Phys

A over IP UP Nb over IP UP

BSC M-MGw M-MGw

Nb UP
RTP RTP
UDP UDP
IPv4 IPv4
Data Link Data Link
Phys Phys

› A over IP UP: RTP over UDP

› RTCP
optional in MSC, can not be switched off in BSC => Mandatory if both are from Ericsson
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 12
A over IP, Mechanics
BSC A Control Plane Nc-i/f
BSC (BSSAP)
MSC-S
TDM or IP
IP Address
CN
UDP Port Mc-i/f (GCP)
A User Plane
over IP
Nb-i/f
IP Address
UDP Port M-MGw

• In order to establish IP transport bearer for the A-IF user plane, the IP
addresses of the involved BSC and MGW has to be exchanged.

• The information is transported via BSSAP, and GCP

• There is no longer a SS7 relation between BSCs and M-MGws and

neither between M-MGws

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 13

A over IP - overview
› It simplifies the implementation of MSC in pool.

› Better speech quality due to the move of the transcoders from the BSS into the CN.

› E-2-E transcoder free calls in case compressed speech is supported in the CN &
saving the cost of transcoders

› Data and fax calls supported:

› The rate adaptation functionality remains in the BSS
› Payload for data/fax is transferred at 64 kbps over the A-interface using clear
channel mode as RTP profile.
› Payloads of CS data/fax are encapsulated into RTP packet, and are carried over
UDP/IP protocol.

› Main documents:
› AoIP Service package in Product catalog
› RS, Support of A-interface user plane over IP, MSC R14.1, 38/1056-FCP 101 4985/P
› A-interface user plane of IP, Method of Procedure, 81/1020-FAF 102 483 Uen

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 14

AoIP MO call
BSC MSC MGW

CL3 (CM Service Request)

(Codec List (BSS Supported))

Setup

Call Proceeding

IAM(SCL)

APM(SC)

ADD.request(T$, Preferred GERAN Codec)

Context (C1) Reserve RTP Connection Point +
ADD.reply(T1, MGW IP Address and Port Number) Change Through Connection
Context (C1)
Assignment Request (AoIP Transport Layer Address (MGW), Codec List (MSC Preferred), Call Identifier)

Assignment Complete (AoIP Transport Layer Address (BSS), Speech Codec(Chosen), {Codec List(BSS Supported)})

MOD.request(T1, Speech Codec (chosen), BSC IP Address and Port Number)

Context (C1) .
. Configure RTP Connection Point
Context (C1) .
MOD.reply(T1)

Plain RTP/UDP/IP
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 15
New BSC Route for AoIP
› Block MAIPCM administers one route pair per each AoIP capable BSC
– This AoIP route pair has no devices connected
– AoIP route is used for MGW selection
– AoIP route pair is used to define the SPC of the connected AoIP BSC (the SPC used in
M3UA/SCTP association used towards each BSC).
EXROI:R=OAOIP1&OAOIP2,DETY=MAIPCM,FNC=3,SP=2-1235,SI=SCCP;
MGBSI: BSC=BSC2, R1=OAOIP1, R2=IAOIP2;

› Note: MAIPCM is not replacing the existing TDM device owner (MRALT) since
the MSC Server will support the co-existence of Legacy and AoIP capable BSCs
within the same node.

› IP traffic restriction on AoIP route:

As soon as the IP route pair is defined by route administration procedures, the IP
restriction on traffic is by default indicating ’ON’ which means that no IP traffic is
allowed to be served. In order to allow IP traffic on the MSC-Server, command
MGRTC should be used.
Example
MGRTC: R1=OCIT5,R2=ICIT5,AOIPRESTR=OFF ;

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 16

Generalized MGG for AoIP
› The MGw Selection has for A@TDM used an MGw Group for BSC
explicitly stating the M-MGws with physical TDM connection to the
BSC.

› The same MGG can still be used.

› But if Extended A i/f over IP is used the MGG should be modified to

AnyMG and (all known) M-MGws on site* should be prioritized.
– With ANYMG parameter enabled for one MGG, all MGWs included in that specific
MGG are equally involved in the MGW selection mechanism*)

› Extended A i/f should be used with common sense, e.g. within an MSC
Pool Area.
Note: If not all MGWs connected to the same BSC are not identical, a market adaptation
can be developed in order in order to allow MGW selection based on MGW capacity factor.
– Similar MDEs developed in MSC release 14.1: WSMD-10427 or WSMD-10574

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 17

MGG A over TDM vs A over IP

MSC
(i &o) Server
1 A over IP Route (i&o)
outes (i&o
)
CR es
2
BS out
CR
BS MGG1
BSCMGG
MGG1 BSC
BSC
“Restricted”

M-MGw 1 M-MGw 3 IP
TDM MGG2
“Restricted”

M-MGw 2

MGG used for MGw selection

process

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 18

Steps needed to provide AoIP
› Feature activation
› Definition of a Media Gateway (MG) and Media Gateway
Group (MGG) on MSC
– Note: Introduction of AoIP requires a new GCP profile EP7.
› Connect AoIP BSC or Configure AoTDM BSC with AoIP
capability
› Activate RTCP capability on AoIP BSC
› Configure the MGG for AoIP BSC
› Configure the Preferred Bearer Set Up direction for AoIP
BSC
› Remove the IP restriction on traffic

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 19

A over IP and MSC Pool
MSC Pool

MSC-S 1 MSC-S 2

TDM TDM

TDM IP

BSC 2 TDM

BSC 1
TDM
IP M-MGw
M-MGw

A-IF bearer selection (TDM or IP):

› Statically configured in MSC-S for each BSC individually
› Configured in each MSC-S separately/independently
› BSC supports both TDM and IP in parallel
› Smooth migration

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 20

A over TDM (legacy)

MGw MGw

TDM IP
BSC
MGw
MGw POI
MGw

MGw MGw

› BSC connected with TDM Two M-MGws selected

to (pair) M-MGws for (majority) calls

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 21

A over IP
ONE M-MGw
selected for
MGw MGw
(majority) calls

IP
BSC
MGw POI

MGw MGw

M-MGw pooling for GSM traffic:

› Load distribution
› Efficient usage of network resources
› Network resilience (N+1)
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 22
MGw selection, IuCS-, A - over IP
BICC (FwBS)

MSC-S 1 MSC-S 2 BSC AoIP Route:

RNC Route:
MGG=ANYMGW
MGG=ANYMGW
MGP=M-MGw3&M-MGw4
MGP=M-MGw1&M-MGw2

M-MGw 1 M-MGw 3 POI

IP BB
RNC 1

1
BSC 1 BSC 2

M-MGw 4
M-MGw 2

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 23

MGw selection, IuCS-, A - over IP
BICC (FwBS)

MSC-S 1 MSC-S 2 BSC AoIP Route:

RNC Route:
MGG=ANYMGW
MGG=ANYMGW
MGP=M-MGw3&M-MGw4
MGP=M-MGw1&M-MGw2

2
M-MGw 1 M-MGw 3 POI
IP BB
RNC 1

BSC 1 BSC 2

M-MGw 4
M-MGw 2

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 24

MGw selection, IuCS-, A - over IP
BICC (FwBS)

MSC-S 1 MSC-S 2 BSC AoIP Route:

RNC Route:
MGG=ANYMGW
MGG=ANYMGW
MGP=M-MGw3&M-MGw4
MGP=M-MGw1&M-MGw2

M-MGw 1 M-MGw 3 POI

IP BB
RNC 1 3

BSC 1 BSC 2

M-MGw 4
M-MGw 2

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 25

MGw selection, IuCS-, A - over IP
BICC (FwBS)

MSC-S 1 MSC-S 2 BSC AoIP Route:

RNC Route:
MGG=ANYMGW
MGG=ANYMGW
MGP=M-MGw3&M-MGw4
MGP=M-MGw1&M-MGw2

4
M-MGw 1 M-MGw 3 POI
IP BB
RNC 1

BSC 1 BSC 2

M-MGw 4
M-MGw 2

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 26

MGw selection, IuCS-, A - over IP
BICC (FwBS)

MSC-S 1 MSC-S 2 BSC AoIP Route:

RNC Route:
MGG=ANYMGW
MGG=ANYMGW
MGP=M-MGw3&M-MGw4
MGP=M-MGw1&M-MGw2

2 4
M-MGw 1 M-MGw 3 POI
IP BB
RNC 1 3
1
BSC 1 BSC 2

M-MGw 4
M-MGw 2

In each call only ONE M-MGW is selected !

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 27
A over IP Codec handling
 AoIP in Layered Architecture (MSS6.1)
Out-of-Band Transcoder Control
via BICC

MSC MSC
Server Server

TrFO in Core Network

TFO on A-interface coded speech A over IP
GSM-EFR, GSM-FR, GSM-HR, GSM-EFR,
FR_AMR, HR_AMR FR_AMR, HR_AMR
FR_AMR-WB FR_AMR-WB,
CLEARMODE
GSM-FR, GSM-HR
PCM (+ TFO) GSM-EFR, "TrFO"
Legacy AoIP MS
MS FR_AMR(s1), HR_AMR(s1),
GERAN GERAN
UMTS_AMR2(s1), UMTS_AMR2(s7),
UMTS_AMR(s7)
FR_AMR-WB(s0), UMTS_AMR- PCM Legacy
WB(s0), PCM MS
AMR, AMR-WB GERAN
UE UTRAN MGW MGW PCM
via ATM or IP PSTN T

PCM IMS (SIP)

T ISDN
AMR, EFR, “VoIP” (SIP-I)
G729, PCM
Wireless (SIP-I)
Softswitch

Codec in Terminal Transcoding to PCM TFO (Decoding only)

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 29

OoBTC concepts
› Direct Codecs
– A Codec is called "Direct" Codec, when it can be used
between the served MS/UE and the M-MGw and the Nb-Interface
without transcoding

› Indirect Codecs
– A Codec is called "Indirect" Codec, when it can be used in the
M-MGw and on the Nb-Interface, but needs transcoding
towards the served MS/UE

› Supported Codec List (SCL)

– SCL is the offered list of codec types ordered by preference
› Direct Codec List (top position)
› PCM (as separator)
› Indirect Codec List (bottom position)

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 31

Codec negotiation concepts (with A oIP)
› Supported Codecs
– With the introduction of AoIP, all supported GSM compressed speech codecs are possible
to be used on AoIP interface – FR-AMR-WB(set 0), GSM-EFR, FR-AMR (set 1) and HR-
AMR (set 1) – can be used with OoBTC.
– PCM codec is not supported by Ericsson on the AoIP interface
› Ericsson E-2-E codec negotiation strategy:
– minimize the transcoding steps through all E-2-E path
– The weak side enforces the same codec on the distant side
– If TFO/TrFO is OFF, each side will select the best available codec for the radio network.
– If TFO/TrFO is ON, the MSC-S will select the best available codec for the transport network.
– This is perfect if the radio quality and capacity is sufficient (not optimal for all networks)
› In case the operator requests a different codec negotiation strategy:
– Read UG for Control Setting of AXE Supplier Parameters for Nb Codecs, 30/1553-CSA 121
01/3 Uen
– Adding support for additional codecs is very complex and has severe long-term drawbacks,
e.g. 3GPP specifies a maximum number of codec configurations in the codec negotiation
list later reconfigurations might require a lot of extra HW just during reconfiguration
– Not all combinations are possible: some combinations might require market adaptations
›

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 32

Ex.: Direct / Indirect Codec: AoIP call
SCL = {FR_AMR (Set 1), GSM_FR, GSM_HR, PCM, GSM_EFR, HR_AMR (Set 1), UMTS_AMR2 (Set 7)}

MSC

MS BSC MGw
FR_AMR_WB FR_AMR (Set 1) FR_AMR_WB(Set 0)
FR_AMR FR_AMR_WB(Set 0) FR_AMR (Set 1)
GSM_EFR GSM_EFR GSM_EFR
HR_AMR HR_AMR (Set 1) HR_AMR (Set 1)
GSM_FR GSM_FR UMTS_AMR2 (Set 1)
GSM_HR GSM_HR UMTS_AMR2 (Set 7)
CSData UMTS_AMR(Set 7)
GSM_FR
GSM_HR
(MS-SCL) (BSS-SCL) PCM
(call control) (Call Control)
(O&M)

Explanation for this example:

MS supports: FR_AMR_WB, FR_AMR, GSM_EFR, GSM_FR, GSM_HR (but not HR_AMR in this example)
BSC supports: FR_AMR(Set 1), FR_AMR_WB(Set 0), GSM_FR, HR_AMR(Set 1) and GSM_HR (but not GSM_EFR)
TSA supports: ALL
MGw1 supports: FR-AMR (Set 1), HR-AMR (Set 1), GSM_EFR, GSM_FR, GSM_HR, UMTS_AMR2 (Set 1), UMTS_AMR2 (Set 7), UMTS_AMR(Set 7) and
PCM (but not FR_AMR_WB(Set 0))

MSC defines:
Direct Codec List (DCL) = {FR_AMR (Set 1), GSM_FR, GSM_HR}
Indirect Codec List (ICL) = {GSM_EFR, HR_AMR (Set 1), UMTS_AMR2 (Set 7)}
Separator = PCM
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 33
Network Example 1
AoIP-AoIP call with identical codecs
TrFO
C : Codec
Codec Negotiation
OoBTC
MSC1 MSC2
BSSMAP BSSMAP
DTAP
DTAP
FR_AMR AoIP FR_AMR FR_AMR FR_AMR AoIP FR_AMR
MS C (set 1) (set 1) MGw1 (set 1) MGw2 (set 1) (set 1) C MS
BSC1 BSC2

TrFO is achieved with NB configuration Set 1

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 34

 Network Example 2
AoIP-3G call with compatible codecs
TrFO
C : Codec
Codec Negotiation
OoBTC
MSC1 MSC2
BSSMAP RANAP

DTAP DTAP

FR_AMR_WB AoIP FR_AMR_WB FR_AMR_WB UMTS_AMR_WB UMTS_AMR_WB

MS C (Set 0) (Set 0) MGw1 (Set 0) MGw2 (Set 0) RNC (Set 0)
C UE
BSC

TrFO is achieved with WB configuration Set 0

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 35

 Network Example: HO to 3G with incompatible codec
TrFO :AoIP-AoIP call (FR-AMR(set 1) negotiated e-2-e)

MSC1 MSC2 C : Codec

OoBTC

FR-AMR(set 1) AoIP FR-AMR(set 1) FR-AMR(set 1) FR-AMR(set 1) AoIP FR-AMR(set 1)

MS C MGW1 MGW2 C MS
BSC1 BSC2

TrFO is achieved with Set 1

Intra-MSC inter-system HO to UMTS_AMR2(set 7)

T : Trans-Coder
MSC1 MSC2

UMTS_AMR2(set7) UMTS-AMR2(set7) FR-AMR(set1) FR-AMR(set1) AoIP FR-AMR(set1)

MS C RNC T MGW1 T MGW2 C MS
BSC2

Transcoding (UMTS-AMR2(s7) <-> FR-AMR (s1)) in MGW1

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 36
 Ericsson 2g-3G multirate

/// GERAN
A over IP /// UTRAN
Core Network
RAN RAN

12.2 12.2 12.2 12.2 12.2 12.2

7.4 7.4 7.4 7.95 7.95 7.95
5.9 5.9 5.9 5.9 5.9 5.9
4.75 4.75 4.75 4.75 4.75 4.75
Set(1) Set(1) Set(1) ! Set(14) Set(14) Set(14)

› Ericsson UTRAN does not implement recommended Set(1), it

support Set(14).
Set(1) and Set(14) are from a speech quality point of view
equivalent, but NOT compatible…
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 37
A over IP: M-MGw
Mgw Pool (RAN)
BSC
BSC RNC BSC
RNC
RNC MGw Pool
BSC BSC

RNC
RNC

M-MGW M-MGW M-MGW M-MGW BSC

BSC
RNC
RNC BSC
RNC BSC

› M-MGw seen as pooled resource from RAN

– Every RNC, BSC can virtually connect to any M-MGw via IP using Iu over
IP, A-over IP
› Any M-MGw can be selected
› MGW selection algorithm guarantee that available M-MGw is selected
› Load distribution
› N+1 redundancy
› Economical resilience
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 39
 Up to 25% capacity gain and N+1 network
redundancy by A over ip
2G: A over TDM A over TDM /
(3G: Iu over ATM) Iu over ATM

10 kE 10 kE
M-MGw M-MGw
12 kE IP backbone 12 kE

BSC/RNC BSC/RNC

10 kE 10 kE
Dedicated M-MGw nodes 1+1 redundancy
per BSC and RNC M-MGw M-MGw

2G: A over IP Distributed load and N+1

(3G: Iu over IP) redundancy among M- Better utilization of M-MGw
MGw nodes. Any M-MGw capacity, less overdimensioning
can switch the call.
10 kE
M-MGw

10 kE
M-MGw pool 10 kE 12 kE
12 kE M-MGw
A over IP / M-MGw BSC/RNC
BSC/RNC Iu over IP IP backbone

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 40

AoIP capacity
Network level capacity Additional AoIP
gain due to distributed capacity need in
load and N+1 the M-MGw node
redundancy among M- due to transcoding.
MGw nodes M-MGw M-MGw

IP backbone
BSC BSC

Less M-MGw SCC:s

on network level due to M-MGw M-MGw
one MGw per call
(extended A-interface)

› M-MGw AoIP capacity on the network level depends on the traffic

model. The more TrFO calls the better M-MGw capacity since less
transcoding needs.

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 41

2G Transcoder Free Operation

No BICC
transcoder BSSAP No
BSSAP MSC-S MSC-S transcoders

TrFO with AMR,

GCP EFR, HR, FR and GCP
WB-AMR

A over IP Nb/RTP/UDP/IP A over IP

BSC M-MGw M-MGw BSC

End-to-End TrFO improves TrFO with AMR HR, resource savings

speech quality and saves in radio, core and transport networks
transcoding resources

Improved Speech Quality and

resource savings in radio, core and transport networks
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 42
AoIP operator value
Other benefits

› Improved speech quality

– AoIP with TrFO provides the same speech quality improvement as
A over TDM with Tandem Free Operation (TFO)

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 43

AoIP & TrFO benefit compared to
PCM in CN => 46% less transcoders
1 transcoder in 70% of calls
(mobile to PSTN/PLMN calls)
PSTN/PLMN

A over A over
TDM TDM

BSC M-MGw BSC

2 transcoders in 30% of calls (mobile-to-mobile calls)

1 transcoder in 70% of calls

(mobile to PSTN/PLMN calls) PSTN/PLMN

AoIP AoIP

BSC M-MGw BSC

No transcoders in 30% of calls (mobile-to-mobile calls)

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 44

AoIP & TrFO benefit compared to compr. speech on Nb =>
65% less transcoders
-4 transcoders in 30% of calls
-3 transcoders in 15% of calls PSTN/PLMN
-1 transcoder in 55% of calls
MSC-S MSC-S

Compressed
A over A over
speech over Nb-i/f
TDM TDM

BSC M-MGw M-MGw BSC

45% of the calls between two M-MGw:s

-No transcoders in 30% of calls

-1 transcoders in 15% of calls
MSC-S
PSTN/PLMN -1 transcoder in 55% of calls

AoIP M-MGw AoIP AoIP

M-MGw BSC
BSC
No calls with 2 M-MGw:s due to extended A-i/f
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 45
AoIP capacity in M-MGw

› M-MGw R6.1 supports AoIP with GSM codecs FR, HR,

EFR, AMR FR, AMR HR and WB-AMR
› GSM capacity (Erlang) for AoIP in the M-MGw will be
roughly the same as estimated capacity in the M-MGw for
WCDMA. This is because both in AoIP and WCDMA
solutions speech codecs are located in the core network
› The high usage of HR codecs in the installed base (GMP
V3) may cause some additional capacity drop in the M-
MGw. This is due to capacity demanding and old HR codec
algorithm that will have an impact on MSB3 board efficiency

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 46

AoIP capacity in M-MGw, example

› BC 3024: GSM with A over TDM

– 100% GSM: 18 kE (reference capacity from PPD)
› BC 3024: GSM with AoIP
– 100% GSM with AoIP (70% AMR/EFR): ~17 kE
– 100% GSM with AoIP (60% HR): ~15 kE
Note: Capacity calculations are based on
› 100% GSM with AoIP
› 75% of access traffic towards POI
› 30% of POI traffic towards PSTN
› 70% of POI traffic towards PLMN
› TrFO is used for mobile-to-mobile calls within CN
› M-MGw capacity is depending on the traffic model. CANDI
tool calculations should be performed to get AoIP impact on
the M-MGw capacity
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 47
AoIP & flexible M-MGw selection
=> 31% less M-MGw SCCs
PSTN/PLMN
MSC-S MSC-S

A over A over
Nb-i/f
TDM TDM

BSC M-MGw M-MGw BSC

45% of the calls with 2 SCC:s

PSTN/PLMN
MSC-S MSC-S Two virtual MGw:s

AoIP M-MGw AoIP AoIP

M-MGw BSC
BSC
No calls with 2 SCC:s due to extended A-i/f

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 48

M-MGw (Re) use of GE boards
to share Iu, A, Nb & Mb traffic

M-MGw

IP ET-MFG/
UP,1
ET-IPG

IP ET-MFG/
UP,2
ET-IPG

› The same physical port and IP address shared

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 49

Security in IP Transport with traffic separation
Possibility to allocate IP
address per Iu, Nb,
M-MGw ET-IPG Mb/VoIP and A Possibility to
interfaces allocate VLAN per
IP-A for Iu
Iu, Nb Mb/VoIP
IP-B for Nb and A i/f traffic
VLAN-Iu
IP-D for A- RNC
interface VLAN-Nb
M-MGw
ET-IPG VLAN-A i/f

IP-C for BSC

Mb/VoIP
VLAN-VoIP
IMS,
Possibility to physically IP based
separate the IP hosts PSTN/PLMN

Traffic separation for access, network internal and network external traffic
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 50
Network Aspects
Example of site connectivity
Primary Site 1
Service Layer Nodes MSC Pool
(P1)

AUC, FNR,
SMS
SMSSC
SC SCP
(HLR) SCP
MSC-S MSC-S HLR
Legend:
STM-1

nxE1

Ethernet (100 Mb)

M-MGw Ethernet
M- MGw Switch
Ethernet (1000 Mb)

MUX
BSC Ethernet Ethernet (100 & 1000 Mb)
Switch
BSC
M-MGw
M- MGw
RNC MUX Router Router
BSC
RNC
BSC

PSTN/
ADM
PLMN

Secondary Secondary
Site 1 Site 2
(S1) Router (S2)
Ethernet
Ethernet
Router Switch
Switch
SDH

M-MGw
M- MGw
Router Ethernet
MUX Switch
Ethernet Router M-MGw
MGw -M
Switch BSC
BSC BSC
M-MGw
M- MGw ADM MUX
BSC
MUX
RNC
BSC
RNC
BSC RNC
BSC
RNC
BSC ADM
PSTN/ PSTN/
PLMN PLMN
AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 52
AoIP 10GE/GE
GE

Connectivity Site Router 1

Site Switch 1
GE

10GE/GE
10GE/GE

10GE/GE
FE

NWI-E
FE
GE
GE
10GE/GE
BSC
10GE
Site Router 2 Site Switch 2 M-MGw

FE

GE

10 GE

CMXB
Legend:

Media / SS7
Other Media /O&M FE MSC-S DB

AoIP (Media)
SS7
S S
L L
I I
GE

MSC
RR MSC
ee s MSC
s ili
liie e
n tn
t L
L TSC
IPLB 22 TSC
SS
Resi ww i
tic tc
lient hh
( (B EXB
L2B aa
cc k
kp
p
la la SPXSPX
1 1
nn
ee
IPLB ))
509-10-013-00 EXB

MSC-S BC

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 53

AoIP and VLANs
Meida_CS Meida_CS

A-Uerplane
Meida_PS
Media Meida_PS
VRF
OAM
SR_A_userplane
OAM

Media_CS_RNC1 SS7_1

SS7_2
Media_CS_RNCn
Site Switch 1

Site Router 1 RNCn RNC1 Meida_CS

M-PBN
Backbone
Meida_PS
BSC NWI-E

OAM

Meida_CS
SS7_1

SS7_2

Site Switch 2
Media
VRF
Meida_PS M-MGw_n

OAM

Media_CS_RNC1

Media_CS_RNCn

Site Router 2

M-MGw R6
RNCn RNC1

509-10-014-00

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 54

MSS feature structure
 Feature Structure
Enhanced for AoIP M-MGw
MSC-S

Compressed
AMR-WB Speech TrFO AMR-WB Speech Speech on Nb MBAC IP Multiplexing
FAJ 121 727 FAJ 121 528 FAJ 121 0163 Interface FAJ 121 400 FAJ 121 0344
FAJ 121 551
A-Interface over IP
FAJ 123 147

A over IP
[BSC]

A over IP
AoIP

FAJ 121 XXX FAJ 121 XXX

Supported codecs
in M-MGw: GSM A-interface IP Transport
- AMR FR FAJ 121 385 FAJ 121 378
New Features for AoIP
- AMR HR
- EFR
- GSM FR
- GSM HR Except AMR-WB, all
- AMR-WB Pre-requisite
codecs are Basic
Dependency

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 56

A-over IP Migration
Bearer selection for AoIP,
(MSC Pool)
MSC Pool

MSC-S
MSC-S

TDM TDM

TDM IP

BSC TDM

BSC TDM
IP M-MGw
M-MGw

A-IF bearer selection (TDM or IP):

› Statically configured in MSC-S for each BSC individually
› Configured in each MSC-S separately/independently
› BSC supports both TDM and IP in parallel

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 58

Migration possibilities
› Smooth A-over IP migration in MSC Pool environment
– BSC migrated at a time with additional possibility of fine control of
traffic on affected A interface by moving subscribers within the MSC
Pool
› A-over IP migration in non-MSC Pool environment
– BSC migrated at a time by changing bearer configuration

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 59

Smooth A-over IP migration in MSC Pool
environment
› In MSC Pool environment A-IF is controlled/shared by all MSC pool
members (all MSC-Ss).
› It’s possible to control traffic portion on A-IF in a BSC by controlling
number of subscriber in the MSC-S(s) which contribute to the traffic on
that particular A-IF.
› Smooth A-over IP migration idea is based on following steps
(illustrated in next slides):
– Starting with one BSC and one MSC-S, the A-IF traffic portion is reduced by
moving subscribers handled by the BSC and registered in the MSC-S
towards other MSC Pool members.
– A-over IP is configured and activated in the MSC-Ss with no (or very low
traffic) since there are no (or few) subscribers registered in the MSC-S
which contribute to the A-IF traffic on that particular BSC.
– Traffic can be ramp-up by moving subscribers back to the MSC-S.
– Process is repeated for all MSC-Ss in the pool.
– Process is repeated for all BSCs in the pool.

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 60

Smooth A-over IP migration (A)
MSC Pool
………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
TDM TD TDM
TDM M

TDM TDM
BSC …………… BSC

› Initial network, A-over TDM

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 61

Smooth A-over IP migration (B)
1 MSC Pool
………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
TDM IP TD TDM
IP M

1
TDM TDM
BSC …………… BSC
› First BSC upgraded for A-over IP (physical connectivity, configuration)
› Configuration for A over IP prepared in the first MSC-S (not activated yet)
› Subscribers (or part of them) originally handled by the BSC and registered in the first MSC-Ss moved to
other MSC-Ss (in order to limit traffic on new A-over IP IF)
› A-over IP activated in first MSC-S, test calls
› A-over IP traffic ramp-up by moving subscribers back to the first MSC-S
› Remaining MSC-Ss still run A-over TDM towards first BSC

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 62

Smooth A-over IP migration (C)
MSC Pool
………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
IP TD TDM
IP M

1
IP TDM
BSC …………… BSC

› Process repeated until all MSC-Ss are configured for A over IP towards first BSC
› After this first BSC migration completed, all traffic runs A-over IP

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 63

Smooth A-over IP migration (D)
MSC Pool
………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
IP IP
IP IP

IP IP
BSC …………… BSC

› Migration process repeated for all BSCs

› Finally, all traffic runs A-over IP

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 64

A-over IP migration in non-MSC Pool
environment
› BSCs controlled by one MSC-S are one by one migrated
towards A-over IP
› Not possible to have both transport types (TDM and IP)
active at the same time (no gradual migration possible)
› Process repeated for all MSC-Ss

› Note: If the operator is interested in AoIP but does not accept to do

migration due to the above, MDEs are available for simultaneous
access over both TDM and IP between the same MGW and BSC:
– E.g. Check the QS for WSMD-10809

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 65

A-over IP migration in non-MSC Pool
environment (A)
………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
M TD TDM TD TDM
TDM T D M M

BSC BSC
…………
BSC

› Initial network, A-over TDM

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 66

A-over IP migration in non-MSC Pool
environment (B)
1 ………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
TDM M IP TD TDM
TD M
1 IP

BSC BSC
…………
BSC

› First BSC controlled by the first MSC-S migrated towards A-over IP

– BSC connected to IP infrastructure
– Configuration done in the BSC and the MSC-S
– A-over IP activated for the BSC

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 67

A-over IP migration in non-MSC Pool
environment (C)
1 ………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
IP IP TD TDM
M
IP IP

BSC BSC
…………
BSC

› All BSCs under control of the first MSC-S migrated to A-over IP

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 68

A-over IP migration in non-MSC Pool
environment (C)
………………
MSC-S MSC-S

IP Transport

………….
M-MGw M-MGw
IP IP IP
IP

BSC BSC
…………
BSC

› A-over IP migration completed in all MSC-Ss and all MSCs

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 69

Possible A-over IP network deployment models
Scenario 1: Scenario 2:
MSS expansion with A-over IP Migration from A-over TDM towards
› Capacity added into network (or A-over IP in MSS network
moved from Monolythic part) by › Relacement of A-over TDM by A
deployment of GSM with A-over IP over IP
› Coexistence of A-over IP and A-over › Replacment can be done in steps,
TDM in the network e.g. smooth A-over IP migration
› Benefits from A-over IP also in part using smooth migration procedure
of the network not migrated yet (e.g.
optimal MGW selection for MS-MS
calls between A-over TDM and A-
over IP)

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 70

MSS expansion with A-over IP

MSC-S
MSC-S
MSC-S MSC-S MSC-S
MSC-S MSC-S MSC-S
MSC-S MSC-S
MSC-S MSC-S

IP Transport IP Transport M-MGw

M-MGw
M-MGw
M-MGw
BSC
M-MGw
M-MGw M-MGw
M-MGw M-MGw
M-MGw
M-MGw
M-MGw BSC BSC
BSC
TDM
MSC TDM
MSC

BSC MSC
BSC BSC
BSC
BSC TDM BSC
BSC
BSC

BSC BSC
BSC
Optional: Monolithic network

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 71

Migration from A-over TDM towards A-over IP
in MSS network

MSC-S MSC-S
MSC-S MSC-S
MSC-S MSC-S
MSC-S MSC-S

IP Transport IP Transport

M-MGw M-MGw
M-MGw M-MGw
M-MGw M-MGw
M-MGw M-MGw

TDM

BSC BSC
BSC BSC
BSC BSC
BSC BSC

AoIP | Ericsson Internal | © Ericsson AB 2012 | 2012-06-11 | Page 72