013 mgw overview v5
DESCRIPTION
Documentation for CORE Media Gateway 3G WirelessTRANSCRIPT
1 © Nokia Solutions Networks
Nokia Multimedia Gateway
Overview
Objectives
• Overview: MGW in two different networks• Reference Interfaces & Protocols • A4 Platform• Physical interfaces & handling of interface
resources• U2 and U2.1 Features
Road from Rel.99 to All-IP2001 2002 2003
Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
MSC Server concept Release 1U2 & M12 MGW Rel.4
U2.1 for MSC server Applications
Launch, GW Rel.99U1+ & M11
Trial, GW Rel.99U1 & M10
Commercial, GW Rel.99U1.5 & M11
U3/U5 & M13
Q1
Multimedia Gateway overview
• Nokia Multimedia Gateway is used for transmitting media between different types of interfaces.
• MGW allows operators to combine transport of both circuit switched and packet swithed connections into a single transport network
• Multimedia Gateway provides:• A-interface towards GSM BSS• Iu-interface towards 3G RAN• Circuit-switched TDM interface
towards PSTN• ATM and IP interfaces towards
backbone4 © NOKIA GW_Training / 6.2.2001 / O.Liinamaa
MGW in both MSC Server and All-IP Env.
IP/ATMBackbone MGWMGWMGW
HLR/ HSS
VMSSVMSSA
Iu-CS
Mc SIGTRAN,H.248
ISUP
ISUP (optional)
BICC CS-2or SIP-T
CAMEL/INAPCAMEL/INAP
MAP MAP
A
3G RAN
GSM BSS
SGSNGGSN
Iu-PSAll-IP RAN
GCSGCS
Iu-PS
CPSCPS
Mg SIP
TDM Based CS Domain
-PSTN-Own CS Domain-Other PLMN
mCreate
SIGTRAN, H.248
Nc
Nb
Gn
Gi
MAP
Same MGW can be used for transmitting the user
plane traffic in both circuit switched core
and All IP core
Same MGW can be used for transmitting the user
plane traffic in both circuit switched core
and All IP core
Gateway Main Characteristics
• User plane transport and conversion between ATM, IP and switched circuit networks
• Signalling transport between network interfaces and MSC Server or GCS
• IPv6 / IPv4 support • Media processing - Transcoding, Echo
Cancelling, Continuity Check, DTMF Generation and detection
• Tone and announcement generation & conference functionality
• TrFO&TFO Support• Handling of media resources under
control of GCS or MSC Server via H.248 (MEGACO)
6 © NOKIA GW_Training / 6.2.2001 / O.Liinamaa
MGW Interfaces & ProtocolsRel.4 Network
Iu-CS
RNC
MSCServer
AAL2ATM
TDM
H.248IP
MSCServer
Mc
MGW
Nc
AAL2/AAL5ATM Nb
McSigtran
IP
BICCATM/IP
• RANAP for radio access control
• BICC for call control• H.248 for MGW control• AAL2 for user data and
AAL5 for signaling over ATM
• RTP for user data over IP• Sigtran for transmitting
SS7 signaling over IP
HLR Services
MAP CAP
MGWRTPIP
PSTNRANAP
AAL5/ATM SS7
BSC
SigtranIP
A
TDM
BSSAP
H.248IP
MGW interfaces & protocolsAll-IP Network
SS7
RTP
IP
PSTN
GCSGCS
SIP
CPS
MGWMGW
SIGTRAN
TDM
H.248
SIP
• SIP for session control• H.248 for MGW control• RTP for user data over IP• Sigtran for transmitting
SS7 signaling over IP
PS CN domain
Gi
Gi
Gi
GGSNSGSN
NE
MU
EH
U
xMX
U/
0
SP
MU
/ 0
CA
CU
/ 0
CM
/ 0
NIS
1/0
VA
NU
xxSF
U /
0
NE
MU
WD
U /
0
OM
U /
0W
DU
/ 0
SF
10
x x CC
P10
NIS
0/0
/
CC
P10
CC
P10
CC
P10
MX
622-
BP
D20
EH
AT
ES
A12
MC
PC
2H
DS
(NE
MU
)
CC
P10
HD
S(O
MU
)
TB
UF
TS
S3
FD
U
xMX
U/
1
SP
MU
/ 1
CA
CU
/ 1
CM
/ 1
NIS
1/1
VA
NU
ISU
xSF
U /
1
WD
U /
1
OM
U /
1W
DU
/ 1
SF
10
x CC
P10
CC
P10
NIS
O/1
/
CC
P10
CC
P10
CC
P10
MX
622-
BP
D20
MD
S(O
MU
)
HD
S(N
EM
U)
CC
P10
HD
S(O
MU
)
TS
S3
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
x x A2S
U
A2S
U
ISU
(NIS
/ 3)
x
NIW
U/N
IP1
NIW
U/N
IP1
CD
SP
CD
SP
C
DS
P
CD
SP
CD
SP
C
DS
P
MX
U/
4P
D20
MX
U/
5
CD
SP
ES
A12
AL2
S
AL2
S
CC
P10
(IP
NIU
/ 1)
/
(NIS
/ 5)
TB
UF
TB
UF
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
x x A2S
U
A2S
U
ISU
(NIS
/ 2)
x
NIW
U/N
IP1
NIW
U/N
IP1
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
C
DS
P
MX
U/2
PD
20
MX
U/3
CD
SP
ES
A12
AL2
S
AL2
S
CC
P10
(IP
NIU
/ 0)
/
(NIS
/4)
TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
x x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/1
4P
D20
MX
U/1
5
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
x x TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
x x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
16P
D20
MX
U/
17
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
x x TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
x x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
18P
D20
MX
U/
19
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
x x TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
x x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
20P
D20
MX
U/
21
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
x x TB
UF
TB
UF
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
x x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
6P
D20
MX
U/
7
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
(NIS
/ 6)
(NIS
/ 8
TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
x x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
8P
D20
MX
U/
9
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
(NIS
/ 7)
(NIS
/9)
TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
(IP
NIU
/ 2)
x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
10P
D20
MX
U/
11
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
(NIS
/ 10
) /
(NIS
/ 12
)
TB
UF
TB
UF
TC
U
xxxTC
U
TC
U
TC
U
TC
U
TC
U
TC
U
xx TC
U
A2S
U
A2S
U
ISU
(IP
NIU
/ 3)
x
NIW
U
NIW
U
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
CD
SP
MX
U/
12P
D20
MX
U/
13
CD
SP
CD
SP
AL2
S
AL2
S
CC
P10
(NIS
/ 11
) /
(NIS
/ 13
)
TB
UF
TB
UF
3
2
3
1 5
3
3
4
4
5
5
5
5
MGW U2MAX HW
Max. Number of units:
- Base module (first two subracks in the first cabinet)
Additional units:IPNIU 2 pairNIS1/0 5+2 pairNIWU 20 pcsA2SU 14 pcsTCU 78 pcsISU 11 pcsESA 2 pcs
3GPP Referred Functionalitythree functional entities in one HW
• Terminates - SCN & Packet Media Termination• Tones and Announcements
• Similar Functionality as the Media Gateway
• IP to IP Calls only• Tones and Announcements• Conferencing Services
• Signalling Transfer Point• SS7 Transport Layer Conversion• Protocol Translation
Nokia Multime
dia Gatewa
y
Nokia Multime
dia Gatewa
y
Media Gateway - MGW
Multimedia Resource Function Processor - MRFP
Signalling Gateway - SGWMRFP
MGW
SGW
SGW in MGWMSC Server MSC Server
SGW
MGW
SGW
BSC
GSM BSS
RNCWCDMA
PSTN/PLMN
1) RANAP (SS7) / ATM <---> IP2) BSSAP (SS7) / TDM <---> IP3) MAP/CAP/INAP (SS7 SCCP) / TDM <---> IP4) ISUP/TUP/IUP (SS7 MTP3) / TDM <---> IP
ATM/IPBackbone
1.
2.
3.& 4.
TDM
ATM
IP/ATM
TDM
SIGNALINGTRANSPORT
IPA2800 Platform Evolution
A2 A3 A4.1
• Multimedia gateway, U1
• Radio Network Controller, RN1
• Capacity 5 Gbits/s
• MGW U1.5• RNC RN1.5• RNC RN2
• Capacity 10 Gbits/s
• MGW U2 • Capacity
10 Gbits/s
The IPA2800 is Nokia´s ATM based multipurpose product platform IPA2800 for mobile core and 3G radio access network elements. It is used in Radio Network Controller, Multimedia Gateway and CS-GW.
• MGW-CSGW U3• RNC RN3
• Capacity 20 Gbits/s
A5
20022001
2003
2004
• MGW U2.1• RNC RN2.1• CS-GW Rel.1 • Capacity
10 Gbits/s2002
A4.2
New HW in A4 Platform Release• IP-NIU interface unit for IP connections.
• Needed if media is transmitted over IP backbone.
• 1G Ethernet and 100M Eth.• VANU (Voice Announcement Unit)
• New functional unit for providing announcements.
• Mandatory, HW similar to other signaling units.• New signaling unit type CCP10
• Next generation of the CCPC2-A signaling unit• (equivalent to CP710-A in DX).• Basic signaling unit for new deliveries.
• IW1S1 interface unit for STM-1 VC-12 interface. • For providing TDM connections over STM-1
interface• Optional, available in A4.2 release.
Other HW similar to MGW Rel'99
MGW Functional Units
-POS-IP over ATM-Ethernet
SFU
MXU
MXU
MXU
NIWU
TCU
A2SU
EHU
IPS1 NIP1
OMU
SPMU
VANU
WDU
E1/T1/J1TDM
CACU
CM
Iu/ATM Core
PSTNAIWF
STM-1TDM
NEMU
NIS1STM-1ATM
FDU
Ethernet
100BaseT
IP Core
TBU
IPFE/GE/GO
ISU
PSTNAIWF IW1S1
E1/T1/JT1IMA/ATM Iu
(In U2.1)
LAN
ESA12
New Unitin U2
New Unitin U2.1
User Plane Data Flow ExampleCall from RAN to ATM backbone (TrFO)
MXU
SFU
MXU
TBUOMU
SPMU
ISU
WDU
Ethernet
100Base-TX
CM
NIS1
NIS1
MXU
TCU
A2SU
NEMU
Iu Media From RNC
MXUNIWU
AAL2 termination.
IU UP not terminated
Transcoder in 'idle state'
CACU
A2SU
AAL2 mux/demux
AAL2 mux/demux
ATMbackbone
ATM STM-1
Media to bb
VANU
Signaling FlowExample: RANAP from RNC to MSC Server
SFU
MXUISU
NIS1
IP-NIU
Iu RANAPover AAL5
ATM STM-1
RANAPover IP
MTP3 / M3UA interworking
RNC
MSCServer
FE
MGW
1G Ethernet
ATM Switching versus AAL2 Switching
AAL2
VC
VP
PHY
AAL2
VC
VP
PHYAAL2
VC
VP
PHY
AAL2
VC
VP
PHY
VC
VP
PHY
MGW ATM Switch
MGW
MGW
AAL2 Switch
AAL2 link
AAL2 link
AAL2 link
AAL2 Path
Utilizing MGW as ATM switch
MGW
• Since Iu-CS and Iu-PS use own ATM virtual connections, it is possible to route both CS and PS traffic inside the same STM-1 interface to the MGW/SGSN site.
• Iu-PS traffic is cross-connected on the ATM layer inside the MGW and routed to SGSN.
STM-1 VC-4Iu-CS & Iu-PS
STM-1 VC-4Iu-CS & Iu-PS
Iu-PS
SGSN
NIS1
RNC
SFU
Core Site
AAL2 Nodal Function in Iur and Nb
MSC Server
MGW1
RNC 1
MGW2
H.248
MSC server may request AAL2 bearer establishment from RNC directly to MGW2 (through all
MGWs in the middle)RANAP
No H.248 ctrl
TDM lines
RNC 2
Iur
AAL2 bearer establishment from RNC1 to MGW2 (Nb)
AAL2 bearer establishment from RNC1 to RNC2 (Iur)
Nb
ATM over SDH / STM-1or E1/T1/JT1 (IMA) used for:• Iu• ATM backbone
TDM used for:• A-interface• PSTN
IP used for:• H.248 control • IP user plane to backbone• SIGTRAN
Network interfaces
TDM
IPATM
STM-1Ethernet
Packet over SDH/Sonet
IP over ATM
MGWMGW
E1/T1/JT1
E1/T1/JT1 STM-1
(STM-1 in U2.1)
ATM Interfaces
SFU
NIS1
RNC
RNC
RNC
SDH
VC-4
MGW
NIP1
MXU
1…16 *E1
RNC
- Iu & ATM backbone interface plug-in-unit NI4S1- 4 STM-1 (155Mbit/s) interfaces per unit- Supported formats:VC-4 or 3*VC-3
- Iu & ATM backbone interface plug-in-unit NI4S1- 4 STM-1 (155Mbit/s) interfaces per unit- Supported formats:VC-4 or 3*VC-3
- E1/T1/JT1 IMA provided by NIP1 available for Iu interface in low bandwith applications
- E1/T1/JT1 IMA provided by NIP1 available for Iu interface in low bandwith applications
VC-3
IP User Plane Interfaces
IP connections are used for- H.248 signalling- SIGTRAN- User plane traffic over IP/ATM core
New i/f unit IP-NIU has two variants:1) IPS1 for STM-1 interfaces - 4 * STM-1 i/f per unit - Packet over SDH/SONET - IP over ATM2) IPFE/GE/GO for ethernet conn. -1G Eth + 8*100M Eth interfaces at one unit, only one type active.
IP connections are used for- H.248 signalling- SIGTRAN- User plane traffic over IP/ATM core
New i/f unit IP-NIU has two variants:1) IPS1 for STM-1 interfaces - 4 * STM-1 i/f per unit - Packet over SDH/SONET - IP over ATM2) IPFE/GE/GO for ethernet conn. -1G Eth + 8*100M Eth interfaces at one unit, only one type active.
SFU
IPS1
MGW
IP/ATM Backbone
8*FE
1G Eth
4*STM-1
IPFE/GE
IP Backbone
IP Backbone
Isolating Signaling from IP User Plane
• By default both signaling and user plane are routed via IP-NIU using either 100M or 1G ethernet interfaces.
• In 1G ethernet case it is not possible to separate signaling into own physical interface via IP-NIU.
• Signaling can be routed directly from ISU units into ESA12 Layer 2 switch in same cabinet thus enabling the isolation of signaling.
• New signaling unit CCP10 provides redundant LAN interface for signaling isolation.
Isolating Signaling from IP User Plane
IP/MPLS Backbone1G
1G
LAN1
LAN2
LAN3
UserPlane
H.248/Sigtran
O&M
ISU
OMU/NEMU
100MbNMS
E.g. Cisco OSR 7609
100Mb
MXUTCU
MXU
SFU
TCUTCU
IPFE/GEWO
IPFE/GESP
ESA12ESA12
MSC Server
TDM Interfaces• IW16P1 plug-in unit can be
used for following purposes:• A & PSTN -interface (NIWU unit)•Data connections towards IWF
• Supported formats:• 2 Mbit/s E1• 1.5 Mbit/s T1• 1.5 Mbit/s JT1
• 16 E1/T1/JT1 interfaces per unit.
• Same unit as in MGW Rel'99
ATM IMA
1…16 * E11…16 * E1
MGW
Iu-CSNIP1
RNC
• NI16P1 plug-in-unit available for ATM IMA (Inverse Multiplexing Access)
• For low bandwith ATM interface (<<155 Mbit/s).
• Several E1s can be used for one IMA group
STM-1 for TDM
New (optional) unit IW1S1 for TDM connections- One optical STM-1 i/f per unit- STM-1/VC-12 (63 PCM), Sonet (VC-11) (84 PCM) - Terminates 64k TDM channels and converts them to ATM virtual channels. - Terminates narrowband SS7 signaling links.
Available in U5 release
New (optional) unit IW1S1 for TDM connections- One optical STM-1 i/f per unit- STM-1/VC-12 (63 PCM), Sonet (VC-11) (84 PCM) - Terminates 64k TDM channels and converts them to ATM virtual channels. - Terminates narrowband SS7 signaling links.
Available in U5 release
IW1S1
MGW
SDH
PSTN
ADM
n* E1
STM-1
Direct interface to SDH (Sonet)
Allocating Resources for MSS
TDM
IPATM
MGWMGW
NIS1
NIP1 IP4S1
IPFGE
NIWU
IW1S1H.248 /IP
• MGW offers TDM, IP and ATM type resources to MSC Server.
• MSC server controls these resources via H.248.
• MGW hides the media transport layer from MSC server, e.g. MSC server does not know whether media uses STM-1 or Ethernet.
MSC ServerMSC Server
Virtual MGW
NIWU
ISU
ISU
NIS1IPNIU
ATM AAL2 Resourcesfor all MSSs
IP Resourcesfor all MSSs
H.248IP
MSS 2
CCSU/SIGU
MSS 1
CCSU/SIGU
H.248IP
NIWU
NIWU
ISU NIWU
CCSU/SIGU H.248
IP
• TDM and (AAL1 PVC) resources are dedicated to a certain MSC server.
• IP and ATM AAL2 resources all visible to all MSC servers and thus shared by all.
TDM resourcesfor Virtual MGW 2
TDM resourcesfor Virtual MGW 1
MGW Upgrade U1.5 -> U5
When M12 is updated to MSC, there are three options for MGW:
1) Rel.99 functionality in MGW is upgraded to Rel.4, i.e. MGW is upgraded from ATM module to MSC-server MGW
2) SW package is changed to U5, but the whole network element remains in Rel.99 phase.
3.) If MSC server functionality is not used in MSC M12 , then MGW may remain in U2 level.
Preparation Steps• SW package is first changed to U2 following the normal upgrade
procedures. MGW continues with Rel.99 functionality.• (other network element upgrades: (OSS, NEMU, MSC, optionally also RNC)• Mandatory HW changes are then done (Insertion of VANU mandatory, IP-
NIU is added if IP backbone is used). • Rel.4 specific modifications are then prepared (without affecting the
traffic):• Backbone interface units are added and interface specific management actions are done.• H.248 links between MGW and MSS are created.• Possible additional HW changes are done.
First Steps:1) SW package change2) Mandatory HW additions3) Backbone configuration With No Remarkable Service break
First Steps:1) SW package change2) Mandatory HW additions3) Backbone configuration With No Remarkable Service break
HW additions in U2 Upgrade• Voice announcements unit
(VANU)• VANU provides voice announcements like VANG unit in DX series. Processing capacity 400 000 BHCA per unit.
• IP-NIU unit, (not needed, if IP over ATM is used.)
• Other HW changes depend on the interfaces and needed capacity.
Rel.99 to Rel.4
MGWMGW
BSSAP'
E1/TDM
MSCServer
Backbone
• RNCs are locked in the MSC one at a time
• RANAP links are changed to MSC server over SIGTRAN (Signaling Point Code changes)
• User plane routing changes are done, Control of MGW connections is changed to H.248
• When configuring is ready, RNC is unlocked in MSC -> traffic starts again, now according to Rel.4
IP
SIGTRAN
H.248
RNC in Rel.4 use
RNC in Rel.99 use
4) RANAP link changes
Service break to one RNC at a time
4) RANAP link changes
Service break to one RNC at a time
MGW Capacity Roadmap
Year Release Number of Ports BHCA
2002
2003
2004
U2, U2.1
U5
30 000
30 000
600 000
600 000
600 00030 000U5
- Note. Maximum number of simultaneous calls is the number of ports divided by two, i.e. 15000.- If more capacity is needed, several MGWs can be placed to same site and clustered to establish a big capacity network element.
Main Features in U2• H.248• Transport Signalling Gateway• ATM AAL2 , IP and TDM connectivity• Speech processing: Echo cancellation, announcements, conference
functionality, In-band tones & Transcoding (Codecs: GSM FR, EFR and GSM/3G AMR, G.711)
• Statistics and subscriber trace• TrFO and TFO • Data calls • Upgrade from Rel.99 to Rel.4• IP QoS (DiffServ)• IPv4 & IPv6 dual-stack
• Multimedia Gateway Rel.99 functionality (no new features compared to U2 content)
U5 Features
• STM-1 VC-12 unit for TDM connections over STM-1
• AAL1 over SVC and PVC • UNI4.0 signalling• IPSec• Text Telephony (TTY)• AAL2 Bearer modification during call (AAL2
signalling CS2)• ABNF (text) coding for H.248 protocol
Further Reading• MGW U2 Product Description in Marketing intranet or in U2
program Web. Updated in November 2001• MSC server business program Web:
NET homepage --> IP Mobility Networks --> Mobile Core Networks --> MSC Server: - MSC Server Survival Kit (a lot of relevant links collected)- Technical Studies- Technical Training Material
• MGW features training material in U2 Program web site (Company Confidential): MCN --> Product Programs --> Mobile Switching Product Programs --> U2 --> Training
• Feature Web:http://www.net.nokia.com/NET/NWS/MSG/MSCHLR/features.nsf (Company Confifental)- M12 Features- U2 Features- U2.1 Features
Conclusions
• MGW commercially available from U2 release onwards, smooth evolution path to upcoming U releases.
• Rel.99 & Rel.4 functionality in the same U5 release.
• Same U5 release fulfills also the known requirements for All-IP networks.
• U5 release for commercial utilization, U5 brings some additional features.