Documente Academic
Documente Profesional
Documente Cultură
www.huawei.com
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page1
Release Evolution of WCDMA
Inherit all the services
Inherit all the services and and functions of R4
functions of R99 IM domain is adopted
Inherit all the services and CS domain change: control is
RAN evolved to IP
functions of 2G ( GSM separated from bearer, the
and GPRS ) function of MSC can be fulfilled Enhanced IP QoS ability ,
CN is composed of CS by MSC SERVER and MGW. supporting end to end IP
domain and PS domain Packet voice supported by CS multimedia service
Adopt WCDMA UTRAN domain, supporting ATM, IP,
TDM bearer
Iu interface between RAN
and CN is based on ATM
R5
R4
R99
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 2
R99 Network Architecture
MSC/VLR PSTN
GSM /GPRS BSS GMSC ISDN
BSC
BTS HLR/AUC
PCU SCE
SS7
RNC
SMS
NodeB SCP
GPRS骨干网/
Internet,
Intranet
UTRAN SGSN GGSN
CG BG
Other PLMN
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 3
R4 Network
Architecture GMLC/SMLC
HLR/EIR
SMS-C
MAP MAP
MAP
SCP
CAP
SIGTRAN
SS7
GMSC Server
BICC
VMSC Server PSTN/ISDN
MAP
RANAP
TDM/G.711
UTRAN BSSAP H.248
GSM/R99PLMN
AAL2 MGW
MGW
TDM/G.711
RTP(AAL2)/AMR
TDM
BSS
IP(ATM)
BackBone IP network
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 4
R4 Core Network-Interface and
Protocol (1)
/ISUP/TUP
MTP1 AAL5/ATM IP
MSC GMSC
Server Server
Nc
H.248
Mc Mc SCTP UDP MTP3B
Nb IP SSCF/SSCOP/AAL5
MGW MGW
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 5
Bearer and Control Separated
MSC
Control Bearer
Layer H.248 Layer
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 6
Distributed Architecture-Flexible
networking
The advantage of distributed networking:
Traffic route is the best, network performance is the
best.
Mostly suitable for the operators with wide coverage.
Traditional network Distributed network
Inter-working mode. inter-working mode.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 7
R5 Network Architecture
CS domain IP/ATM Backbone
MGW MGW
PSTN/PLMN
GSM /GPRS BSS
VMSC Server GMSC Server
BSC
BTS HLR/AUC/HSS
Iu-CS
SCE
PCU SS7
RNC SMS
SCP
NodeB Iu-PS
GPRS
Internet,
backbone Intranet
UTRAN SGSN
GGSN
MGW
PS MGCF
domain CG BG
IP backbone
P-CSCF S-CSCF
MRFC
MRFP
IMS domain
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page 8
Content
1. WCDMA Core Network Overview
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page9
What is MSC Pool?
MSC Pool
Iu-flex/A-flex
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page10
MSC Pool Network Architecture
Legacy network MSC Pool network
In an MSC Pool network, one RNC/BSC can be connected to multiple MSCs. In this way, the
MSCs in the MSC Pool as a whole provide services as a single MSC with a large capacity for
the radio network side.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page11
What are the advantages of the MSC Pool solution?
Enhance
Improved Reduced Better
d DHD JGDJ
resource signaling quality
network D J of
utilization traffic service
reliability
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page12
Improved Resource Utilization
HLR Location update HLR Only intra-MSC location
Occupied Total
Occupied Total update is required.
resource Total resource Occupied resource Total
resource resource Occupied resource
resource
resource
Inter-MSC
Inter-MSC
handover is
handover 500 K 600 K
200 K 900 K
800 unnecessary.
800 K 900 K
200 500 K 600 K
MGW MGW
BSC/RNC BSC/RNC
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page13
Enhanced Network Reliability
MSC server
Data can be backed up on multiple MSCs in the MSC Pool to implement disaster tolerance and
improve network reliability.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page14
Reduced Signaling Traffic and Better
QoS
No inter-MSC location update is
HLR performed in the MSC Pool area,
which reduces signaling traffic
The serving MSC
is not changed over the C/D interface.
when an MS/UE No inter-MSC handover is performed in
roams within the the MSC Pool area, which improve the
MSC Pool area. QoS.
MSC 1 MSC 2
No inter-MSC
handover is
required.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page15
Content
1. Overview
2. Basic Concepts
3. Principle
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page16
Content
2. Basic Concepts
2.1 MSC Pool and MSC Pool Area
2.3 NNSF
2.6 CN-ID
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page17
MSC Pool and MSC Pool Area
MSC Pool: a group of MSCs sharing
traffic in parallel.
MSC Pool Area: the area served by
an MSC Pool.
If one or more RNCs/BSCs are
connected to an MSC Pool, all the
service areas of the RNCs/BSCs
comprise an MSC Pool area, and all
subscribers in the Pool area are
served by the MSCs in parallel in the
MSC Pool.
Subscribers located in the MSC Pool
area need not to change the serving
core network node for roaming.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page18
Iu-Flex and A-Flex
Iu-Flex, short for intra-domain connection of RAN nodes to multiple CN nodes,
enables one RNC to connect to multiple CN nodes in the same CS/PS domain.
A-Flex enables one BSC to connect to multiple CN nodes in the same CS/PS
domain.
MSC 1 MSC 2
CN-CS
RAN
Iu-CS A
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page19
NNSF
NNSF : non-access stratum (NAS) node selection function.
The NNSF enables the selection of a serving MSC from an MSC Pool for an MS.
The entity that has the NNSF function is called an NNSF entity. The NNSF entity may
be BSC/RNC and MGW.
MSC server
MGW
An NNSF entity can be the Select a serving
BSC, RNC, or MGW. MSC for the MS/UE
BSC/RNC
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page20
TMSI and NRI
A temporary mobile subscriber identifier (TMSI) is a temporary identifier that is
assigned to an MS/UE when the MS/UE is registered with an MSC. The TMSI is
used to increase the security of subscriber data.
A network resource identifier (NRI) is used to identify an MSC serving a specific
MS/UE.
One NRI defines a unique MSC in an MSC Pool.
An MSC in one MSC Pool can be assigned with more than one NRI.
Each NRI must be unique in an individual MSC Pool and between neighboring
MSC Pools. Otherwise, the NNSF entity cannot balance the load when routing
traffic to the MSCs.
31 30 29 28 … 24 23 22 21 20 19 18 17 16 15 14 13 … 0
User ID User ID
CS/PS VLR restart NRI range
range range
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page21
Relationship Between NRI and User
ID
Number of MSCs in the MSC Number of Subscribers
NRI Length
Pool Served by the MSCs
5 25 = 32 2(29-5) = 16,777,216
6 26 = 64 2(29-6) = 8,388,608
7 27 = 128 2(29-7) = 4,194,304
8 28 = 256 2(29-8) = 2,097,152
In an MSC Pool network, the total number of bits used for NRI and user
ID is fixed.
If the NRI is longer, the user ID becomes shorter. Consequently, the
MSC/VLR serves less subscribers. If the user ID is longer, the NRI
becomes shorter. In this case, less MSCs can be included in the MSC
Pool.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page22
Increasing the Utilization of A-Interface Circuits
MSC server MSC server
Mc
Mc
MGW MGW
BSC BSC
Example: Assume that there are 100 people in a company and 10 cars are exactly enough for
use. The company is divided into 10 affiliate companies, each with 10 people and one car. In
this case, people in some affiliate companies will always find that cars are always unavailable,
whereas people in other affiliate companies may find that cars are always left unused.
How to use the limited resources efficiently?
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page23
Facilitating Planning, Operation and
Maintenance of A-Interface Circuits
MSC server 1 MSC server 2 MSC server 3 MSC server 4 Capacity expansion of the MSC
Pool
All the TDM resources of the A-
interface circuits must be planned
again and redistributed after an
MSC server is added to the MSC
Pool.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page24
Ensuring Effective Utilization of A-Interface
Circuits
MSC server 1 MSC server 2 MSC server 3 MSC server 4
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page25
Managing A-Interface Circuits on the MGW
MSC server 1 MSC server 2 MSC server 3
TDM circuits are shared
A-interface
circuit between multiple virtual MGWs
management to prevent resource waste if an
MSC server fails, and therefore
increase the reuse ratio of A-
interface circuits.
Managing A-interface circuits on
the MGW facilitates the
operation and maintenance of
Shared Shared Shared the MSC Pool. A-interface
A- A- A- circuits do not need to be
interface interface interface redistributed after an MSC
circuits circuits circuits server is added to the MSC
Pool.
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page26
Content
1. WCDMA Core Network Overview
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved. Page27
Application Scenarios of the AoIP Feature —
Background Information
A (IP or A (IP or
TDM) TDM)
Mc/IP Mc/IP
TRAU
TRAU
MGW MGW
A/TDM Nb A/TDM
= Signalling = Transcoder
= User p lane
In the 3GPP GERAN R7, the IP-based Signaling Transport (SIGTRAN) is added
over the A interface on the basis of the existing TDM signaling transmission, as
shown in the preceding figure. On the user plane, however, only the TDM
transmission is used. In addition, the transcoder is located in the BSS. Only the
PCM (G.711) codec is defined for the A interface over TDM (AoTDM).
In the 3GPP GERAN R8, the IP transmission protocol is introduced to the A
interface so that the low-cost intermediate IP network can be used for
transmission on the user plane of the A interface.
Beneficiary Description
The AoIP feature helps implement the TrFO throughout the call process,
Subscribers
improve the voice quality, and thus improve satisfaction of subscribers.
Signaling plane: receiving the The BSC directly selects a circuit based on the The BSC allocates and sends the IP address and port
Assignment Complete message CIC. Therefore, the BSC sends the Assignment number to the MSC server through the Assignment
through the interface at the access Complete message the MSC server, informing the Complete message.
side MSC server that assignment is complete.
Signaling plane: confirming the This step is not required. The MSC server sends the IP address and port number
termination at the access side allocated by the BSC to the MGW. The MGW then
through the Mc interface establishes the user plane between the MGW and the
BSC.
Signaling plane: intra-BSC The MSC need not take part in this step. The MSC must take part in this step.
handover
User plane: transcoder The transcoder is located on the BSC. The transcoder is located on the MGW.
TFO and TrFO: speech codec Only the G.711 uncompressed codec is Compressed codecs, such as FR, EFR, HR, and AMR
transferred. are transferred. This saves the bandwidth of the A
interface.
Data service codec When the bearer is being prepared, the MSC The MSC server sends the data service code.
server does not send any codec, but sends a
message that contains the information element
PLMNBC.
User experience The subscribers do not notice any difference between the AoTDM and the AoIP. They are not aware of whether
the A interface is TDM or IP based.
4. Assignment Request
The MGW sends the allocated IP address,
Assignment Complete
PayloadType, PTime, and ClockRate to the MSC Mod Req
server through the Add Reply message. Mod Reply
Call Identifier
Speech Codec
The MSC server sends a Mod Req message to the MGW. This message contains the IP
address and port number of the BSC. If the MSC server requires modification of the
codec type on the MGW, this message also contains the corresponding codec,
Payloadtype, PTime, ClockRate, and ACS.
During handover, the messages exchanged between the MSC server and the MGW are
modified in the same way as those in the basic call scenario. The Handover Request
and Handover Request Ack messages are modified in the similar way as the
Assignment Request、Assignment Complete message. Note the following difference:
In the basic call scenario, the MSC server can obtain the BSC bearer type through the
CM Service Request and Paging Response messages.
In the handover scenario, the MSC server can obtain the bearer type of the target BSC
by querying the relevant table.
Source BSC MSC Server MGW Target BSC
Handover Required
Add Req
Add Reply
Handover Request
Mod Req
Mod Reply
Handover Command
Handover Complete
Sub Req
Sub Reply
Handover Request
Handover Request ACK
The intra-BSC flow is added after the AoIP feature is implemented. Through
frequent handovers, the general voice quality of the network can be improved.
other, the BSC sends a Handover Request message to Handover Complete Mod Req
the MSC server and the MSC server takes part in the Mod Reply
intra-BSC handover. The MSC server sends the new IP Sub Req
Sub Reply
address, port number, and codec information of the
BSS to the MGW, instructing the MGW to use the
information to establish a termination. In this way, the
codec is modified.
According to the definition in 3GPP 43903, rate adaptation is implemented by the BSC during the data
service. The rate between the BSC and the UMG is fixed to 64 kbit/s. The packet time is 20 ms. The
RTP is encapsulated in compliance with RFC4040. The UMG needs to convert the bearer type of the
data. Only the PLMNBC and GSM channel coding need to be sent over the A interface. The UP
packets are not sent over the A interface. Based on the PLMNBC and GSM channel coding , the UMG
adds the IWF resource.
Like the codec negotiation during the voice call, the data service also has a redundancy negotiation
process.
Assignment Complete
Assignment Request