9 OWG500210 Dual-Homing Principle and Configuration (VMSC) ISSUE1.0

Dual-homing
Principle and
Configuration
(VMSC)
Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.
www.huawei.com
References
MSOFTX3000 Dual-Homing User Manual
Page2
Objectives
Upon completion this course, you will beable to:
Understand the basic concept of dual-homing solution
Perform the data configuration of dual-homing VMSC

solution
Page3
Contents
1.
Dual-homing Concept
2.
Dual-homing Principle
3.
Data Configuration
4.
Operation and Maintenance
Page4
R4 Soft-Switch Solution
Management system Service system Billing system
MSC Server
MSC has been

separated into
MSC Server and
MGW
IP backbone network
MGW n
MGW1
VoIP
Page5
SS7 network
Redundancy and Security
MSC Server works as control plane, It

is very important to guarantee the
redundancy and security on MSC
Server side!
MSC Server
1.8 million subscribers
IP bearer
MGW1
MGW n
Page6
The Definition of Dual-homing

Active MSC Server
Assistant MSC Server
Active
standby
MGW
DH is a networking mode. In the 3GPP R4 networking and later, one

MGW is homed to two MSC Servers. Normally, an MGW registers with
the active MSC Server. When the active MSC Server becomes faulty,
the MGW registers with the standby MSC Server so that the
subscribers can still enjoy services.
Page7
The Definition of Dual-homing

Standby Server3
Active MSC Server1
Active Server2
Virtual Server0
Virtual Server1
Virtual Server2
Active
Standby
MGW1
MGW2
The active MSC Server
The standby MSC Server: we can also call it disaster recovery server, it is
used to backup the data and service for the active server;
The virtual MSC Server: the disaster recovery MSC Server is logically
partitioned into N+1 virtual MSC Servers. The virtual MSC Servers are
identified according to Server indexes. Server 0 always serves its own node
while others respectively serve as N (the number of virtual Servers except
Server 0) standby MSC Servers.
Page8
Advantage of Dual-homing
BSS1
BSS2
BSS3
BSS4
BSS1
Traditional networking mode
BSS2
BSS3
BSS4
The DH networking mode
In DH solution, one MGW is homed to two MSC Servers. When the active MSC Server becomes faulty, the MGW
registers with the standby MSC Server so that the subscribers can still enjoy services. So that we can say, it
improves the networks reliability.
When an active MSC Server is going to be moved or upgraded, you can manually transfer its services to the
standby MSC Server. It improves the services continuity.
There is no special requirement for other network nodes and terminals.
Page9
Different DH Schemes
1+1 Active and Standby Mode
1+1 Assistant Mode
N+1 Active and Standby Mode
N+1 Assistant Mode
Page10
DH 1+1 Active and Standby

Networking Mode
Active MSC Server1
MGW1
MGW2
Standby MSC Server2
MGW3
MGW4
1+1Active and Standby Mode: In two MSC Server, one

of them is active, the other is in the standby state.
Page11
DH 1+1 Assistant Mode

Active MSC Server1
MGW1
MGW2
Active MSC Server2
MGW3
MGW4
1+1 Assistant Mode: In this mode, there are no difference of

active server and standby server. Both of MSOFTX3000s are
active MSC Servers, and also assistant MSC Servers of each other.
Page12
DH N+1 Active and Standby

Mode
Active MSC Server1 Standby MSC Server3
MGW1
MGW2
Active MSC Server2
MGW3
MGW4
N+1 Active and Standby Mode: N MSOFTX3000s work as

active MSC Servers, the other one as the standby MSC Server.
Only N server are active, the other 1 server is always be

standby.
Page13
DN N+1 Assistant Networking

Mode
Active MSC Server1
MGW1
Standby MSC Server3
MGW2
MGW5
Active MSC Server2
MGW3
MGW4
N+1 Assistant Mode: N MSOFTX3000s work as

active MSC Servers, the other one as the standby
MSC Server.
All the N+1 Server are active.
Page14
Summary
Dual-homing basic concept
The advantage of Dual-homing
The application of the dualhoming networking
Page15
Contents
1.
Dual-homing Concept
2.
3.
Data Configuration
4.
Page16
The Switch Mode of Dualhoming

Abnormality, switch
Virtual MSC
Server0
Virtual MSC Server1

Active
Deactive
Recovered, switch
Virtual MSC
Server1
Virtual MSC
Server0
Active
Deactive
The MSC Server supports the following four DH switch

modes:
Auto switch; Manual switch; Auto backward; Manual
backward.
Page17
Triggering Condition of DH
Switch
MSC Server2
MSC Server1
Virtual MSC Server0
UDP heartbeat
VMSC Server1
Triggering
Virtual MSC Server1

Virtual MSC Server0
Condition of Manual Switch: Manually setting the DH
status.
Triggering Condition of Auto Switch: Heartbeat detection and
MGW
registering request.
Both of these two modes are in applied in the current network.
Page18
DH Virtual MSC Server Service

Takeover
Acitve the
disaster recovery
servers local
office information
Deactive
Active
Active
MGW and
correlative
signaling
switch
MSC
Server0
Virtual MSC Server1
Active BICC
Page19
Impacts of DH Switching on
Caller
MS
MGW
SVR1
SVR2
MS
MGW
SVR1
DH 1+1 Assistant scheme-the

process of making a call
MS is SVR1s attach subscriber. In normal
condition, it will initiate call process to SVR1.
When the SVR is faulty MGW will register to
SVR2, change the signaling route, sent call request to
SVR2
In SVR2s VLR, there are no subscriber of this MS.
So, it will return failure, the reason is absent subscriber;
MS initiate LAU process, then the call process can
success.
SVR2
DH 1+1 Active and Standby schemethe process of making a call

MS is SVR1s attach subscriber. In normal
condition, it will initiate call process to SVR1.
When the SVR is faulty ,SVR2 will receive the
MSs calling request.
In SVR2s VLR, there are no subscriber of this
MS. So, it will return failure, the reason is absent
subscriber;
MS initiate LAU process, then the call process
can success.
In the call process, all of the signaling and route reelect are
completed by the MGW, it has no relationship with BSC/RNC!
Page20
Impacts of DH Switching on
Callee X
X
PSTN/MSC
HLR
SVR1
SVR2
PSTN/MSC
HLR
SVR1
DH 1+1 Assistant scheme

callee process
The caller MS sends SRI request to the
HLR;
HLR gets the MSRN from the backup
SVR1 in the SVR2;
In the VLR of backup SVR2, there are no
subscribers data. So, the SVR2 will send data
recovery request to the HLR;
HLR inserts subscribers data into the
backup VLR of SVR2;
SVR2 will backup the PRN RSP which is
returned by the SVR1. Then the callee process
will continue.
STP/SG helps to complete this process.
SVR2
DH N+1 Active and Standby

scheme callee process
The caller MS sends SRI request to the
HLR;
SVR2 receives PRN message from HLR,
HLR neednt to change the route
arithmetic(SVR2 uses the same signaling point);
In the VLR of backup SVR2, there are no
subscribers data. So, the SVR2 will send data
recovery request to the HLR;
HLR inserts subscribers data into the
SVR2;
SVR2 return PRN RSP, the callee process
will continue.
STP/SG helps to complete the redirectional and backup process.
Page21
Impacts of DH on Calling and

Billing
Impact on calling
During the DH switching, MGW will change the registered Server. The
resource will be provided by this MGW. All calls, being processed by the
original active MSC Server, will be interrupted. The MGW reclaims all
resources;
During the DH switching or backward, the MSC Server, which will take
over services, initiate reset to the trunk group. Then, terminals
(including callers and callees) will be released .
Impact on Billing:
During the DH switching, bills will be lost because they wouldnt be

generated by the original MSC Server in time,.
After switching, bills are generated on the iGWB of an current activated
MSC Server. The billing center connect the current iGWB to get bills.
Page22
Summary
DH switching modes and its triggering condition
DH switching impact on calling and billing
Page23
Contents
1.
Dual-homing Concept
2.
3.
Data Configuration
4.
Page24
Contents
3
Data Configuration
3.1 Dedicated Data of DH
3.2 Internal Data Configuration
3.3 Interconnection Data Configuration
3.4 Service Data
Page25
Dedicated Data Configuration

Steps
If Switch mode of a virtual Server node in the local
office is set to Automatic, configuration steps are as

following:
Step 1: Use the command SET DHWM to set Work mode of

virtual Server node 0 to Assistant, Switch mode to Manual, and
Force state to Activated.
Step 2: Use the command ADD SRVNODE to set the assistant

MSOFTX3000 of a local one (for example, virtual Server node 1)
to a DH MSC Server node.
Step 3: Use the command ADD DHHCFG to add a DH heartbeat

link between a local MSOFTX3000 and its assistant
MSOFTX3000.
Step 4: Use the command SET DHWM to set Work mode of the
virtual
Server
node corresponding
toreserved.
the assistant
Copyright
2006 Huawei
Technologies
Co., Ltd. All rights
MSOFTX3000
Page26
Set DH Working Mode
SET DHWM
Work mode, a parameter, is used to define the work

mode of a local office in a network. You can use the
command SET DHWM to set Work mode to Standalone or
Assistant.
Standalone: indicates the local MSOFTX3000 does not work in DH

mode.
Assistant: indicates the local MSOFTX3000 works in the DH mode.
It is only valid when Work mode is set to Assistant. It

defines the switch mode of a certain virtual Server node
in the local office.
It is valid when Switch mode is set to Automatic. It
defines the takeover mode when a certain local virtual
Server node is switched over automatically. The system
supports all the modes.
Handshake timeout (*5s)
Page27
Setting DH Virtual Server Node
ADD SRVNODE
In the table of virtual Server nodes, item 0 is always configured for

a local MSC Server, while other items are configured for assistant or
standby MSC Servers.
Before adding a virtual Server node in the MSC Server, set Work
mode of the virtual Server node 0 to Assistant with the command
SET DHWM to activate the dualhoming function of the local office.
index
index
server
SX-1
SX-A
SX-1
server
SX-A
index
server
SX-1
SX-2
SX-2
SX-A
...
...
SX-n
index
server
SX-n
SX-A
SX-2
SX-A
......
SX-n
Page28
Setting Local Port of DH

Heartbeat Link (Optional)
SET DHLOCPORTNO
Signals of DH heartbeat link are transmitted

through the UDP protocol;
By default, the UDP port number used by the
heartbeat link of the local MSOFTX3000 is 1000.
Page29
Setting DH Heartbeat Link
ADD DHHCFG
Considering safety, configure two heartbeat links

if the system has two pairs of WIFMs or more.
Encryption method : It specifies whether the
heartbeat signals needs encrypting or not. The
default type is MD5.
Key: It specifies the key required by the MD5
encryption algorithm. The value should be a
character string of at most 16 characters.
Page30
Contents
3
Data Configuration
3.4 Service Data
Page31
Local
Data
The local data is used to define:
Signaling point code, Country code and area code,

National toll area code, Multi-area statistics index, DN
set, Call source code, Local MSC number, Local VLR
number
Configure dualhoming dedicated data and add

corresponding virtual Server nodes, then configure
corresponding local information for each virtual Server
node.
NOTE: In configuration, Multi-area flag should be set

as Yes.
Page32
Local Data
ADD MASI
Add Multi-area statistics index;
Multi-area information (MASI) indicates the index of

a virtual Server
Page33
Contents
3
Data Configuration
3.4 Service Data
Page34
Mc Interface Data for

Connecting
to
MGW
ADD MGW
The data for connecting to the MGW is an interconnection

data of the MSOFTX3000. It defines the following
information:
The data of H.248 links between the MSOFTX3000 and the
MGW
The Media connection relationship between MGWs
The information of paths between MGWs
The parameter MGW index (ADD MGW) is directly

associated with the index of virtual Server nodes and
determines the virtual Server node to which the MGWs
belong.
Page35
Data Configuration of Mc Link

BSG1 BSG2 BSG3
BSG1 BSG2 BSG3
Note:
UMG1
2 2
PPU1 PPU2 PPU3
2 2
1
1
1
SX2
1
1
SX1
PPU1 PPU2 PPU3

UMG2
1. The direction of arrowhead means CLIENT to SERVER. For SX1, UMG1 is

master,
and UMG2 is standby.
2. SX1 and SX2 are backup. Follow the load-share principle to select the WBSG.
Page36
Signaling Interface Data

MTP Configuration
If a local SP related to the MTP DSP belongs to virtual

Server node 0, the MTP DSP and subsequent data to be
configured are also in charge of virtual Server node 0.
Configuration procedure of the M2UA-based MTP3 are as

following:
Configure active N7DSP, N7LKS, N7RT and N7LNK for virtual MSC
Server node 0.
Configure standby N7DSP, N7LKS, N7RT and N7LNK for other virtual
MSC Server nodes.
Follow the load-share principle to select the WBSG.
Page37

M2UA Configuration
The Homing Server of M2UA link sets and links are determined
by ESG.
If the ESG is homed to virtual Server node 0, the link sets and
links of M2UA are in charge of virtual Server node 0. Proceed as
follows to implement the M2UA configuration:
Configure active ESG, M2UA link sets and links for virtual Server node 0.
Configure standby ESG and M2UA links and link sets for other virtual Server
nodes.
Configure one M2UA link set for the MGW (embedded ESG). The link set
contains two links, one of which is connected to an active MSC Server and the
other is connected to a standby MSC Server.
Configure an M2UA link on the MGW (embedded ESG). Then the M2UA link set
makes the link be managed by the virtual Server node that manages itself.
Page38

M3UA Configuration
The Homing Server of M3UA configuration (M3DE,

M3LKS, M3RT and M3LNK) are determined by local SP.
If local SP node 0 is specified for M3LE, the configuration

of its subsequent data is in the charge of local SP node
0.
Proceed as follows to implement the M3UA

configuration:
Configure active M3UA local entities, destination entities, link sets,

routes and links for virtual Server node 0.
Configure standby M3UA local entities, destination entities, link

sets, routes and links for other virtual Server nodes.
Follow the share-alike principle to select the WBSG module on the

MSOFTX3000 and try to make all WBSGs share services of one SG.
Page39
DH Signaling ConfigurationLink Priority Level

Direction of link
set is A->C
Active MSC Server
Disaster recovery MSC Server
Master
OPC:A
Master link
Mster OPC:B
Slave OPC:A
Standby lonk
OPC:C
MGW/SG
Direction of link
set is C->A
Direction of link set

is A->C, when the
master link is active,
the slave link is deactive
Page40
DH Signaling ConfigurationRoute Priority Level

Direction of
route is A->C
Master MSC Server
Disaster recovery MSC Server
Master
OPC:A
Direction of route is
B->C master OPC
and the slave OPC is
standby signaling
point relationship
OPC:C
MGW/SG
Master
OPC:B
Slave OPC:A
Through route
direction is C->A
bypass route
direction is C->B->A
Page41
Comparison between Two

Signaling Configuration Modes
Link Priority
Link availability
Route Priority
In TDM network, half of
High Link
links cant be used
availability
Active and de-active
Switch time delay
link switch to each
Smooth switch
other, time delay exist
The influence to
the nearby
Need the function

No influence
priority
network elements
Suitable scene
to support the link
TDM/IP network
TDM/IP network
Page42
Summary
Local information associate with virtual node index directly;
INOFFMSC associate with its virtual node by the corresponding

relationship with the OFI.
MASI information manage virtual node index directly. It confirm which

virtual node that MSC in multi-area belong to.
MGW associate with the virtual node index directly. The MCLNK associate
with the virtual node by the MGW it belongs to.
BSC, RNC and LAI/GAI and so on associate with the virtual node by the
local information that OPC belong to.
ISUP, TUP, PRA, R2 office direction associate its virtual node by the media
gateway that trunk group belong to.
BICC office direction associate with the virtual node by the BICCSCTPLNK.
Page43
Contents
3
Data Configuration
3.4 Service Data
Page44
DH Mobility Management
Standby MSC Server
Active MSC Server
Active link
Standby link
MGW/SG
MGW/SG
LAI-1
LAI-2
LAI-3
LAI-4
LAI-5
Every virtual MSC Server has its own mobility data, such as RNC,
BSC, LAI/GCI. So after the DH switch, if the MSC Servers signaling
sub system can be active, then the update location in virtual MSC
Server/VLR can completed successfully. For example, in the picture,
one terminals location update from LAI5 to LAI4.
Be more careful about the location update flow between the virtual
MSC Server/VLR. For example, the terminals location update from
LAI4 to LAI3.
Page45
LU-Between Virtual Nodes in

One MSC Server
MS
MSC1/VLR1/LAI1
MSC2/VLR2/LAI2
1.Location Update Req

(old LAI = LAI1,new LAI = LAI2)
HLR
2.UpdateLocation (MSC2,VLR2)
3.CancelLocation
4.CancelLocationRes
5.InsertSubData
6.InsertSubDataRes
8.Location Update Acc
7.UpdateLocationRes
(HLR)
VLR initiates the location update to the HLR to inform the HLR the
subscribers location. It can use necessary method (inside
implement), so to avoid the conflict between the flow of insert data
and delete data; The data configuration just like in normal situation.
The inside implement is used to adapt the change of DH switch.
Page46
DH Data Recovery and Paging

BSC
MSC2/VLR2/LAI2
HLR
1.ProvideRoamingNbr MSC2
2.Restore Data
3.RestoreDataRes
4.ProvideRoamingNbrRes
5.IAM
6.Paging (LAI in MSC area)
When the subscribers make the first call after the DH

switching without location updating. To the caller service, if
it find there are no subscriber data, or the caller service
route to the new MSC but find no subscriber, then the
recovery flow will be triggered.
Page47
DH Handover Flow
Intra-office handover data: The handover between location

areas in a same virtual Server node is the intra-office
handover. The data configuration is the same as that in
common cases. The handover from LAI-1 to LAI-2 or LAI-3
are all intra-office handover.
Inter-office handover data between different virtual Server

node: A location area whose local office is configured with a
virtual Server node will be configured as a local VLR location
area cell/service area. The LAI-3,LAI-4 are local VLRs
service area. But their virtual node is different. So, the
switch from LAI-3 to LAI-4 is intra-office handover.
Inter-office handover data between different MSC Servers is

same as common data.
Page48
Handover Procedure and

Configuration After Switching
VirtualServer2/VLR2
/LAI2
BSC
2.HandoverReq (CGI)
Virtual Server1
1.PrepareHandoverReq
MSC,CGI
3.HandoverReqAck
Link to MSC Number by CGI, and
allocating the handover numbers
according to this
4. PrepareHandoverRes
MSC Number.
5.IAM HON
After the DH Switching, the handover between two virtual Server is inter-MSC
handover.
In ADD LAIGCI/LAISAI the type of LAI in to-be-taken-over virtual node
should be configured as local VLR LAI.
Page49
DH Trunk Office Direction

Scheme
A interface/ISUP/TUP/R2/PRA/BICC office
direction, sub route, route, route analysis,

trunk group, circuit data are configured same
as common data.
Page50
DHs Number Analysis and

Routing Function
Standby MSC Server
Active MSC Server
De-active link
Active link
MGW2
MGW1
LAI-1
LAI-2
LAI-4
LAI-5
The caller MS belongs to MGW1, the called MS belongs to the MGW2. After
DH switching, the MGW1 and the MGW2 are also intra-office circuit. So, it is
impossible to establish mesne bearing. The call can not be separated in
logic. Before DH, it is intra-office call, if we dont differentiate different
virtual nodes roaming number prefix, then, after DH, it will become intraoffice call. In local information, if we assign roaming number according to
MSC/VLR, then the roaming number in two virtual nodes can be separated.
Page51
DH Roaming Number and

Handover Number Assignment
get MSC Number from
UserInfo In VDB
MSC and MSRN/HON mapping relation Table

Msc Number
86139075500
86139075501
(1)
MSRN/HON Suffix ID
0
1
......
(2)
MSRN/HON suffix configuration Table

ID
0
1
Prefix ID
0
1
Suffix Start
00
00
Suffix End
99
99
......
(3)
MSRN/HON prefix configuration Table

ID
0
1
MSRN/HON Prefix
86139075500
86139075501
......
Page52
DH Roaming Number and

Handover Number Assignment
Note to Configuration
ADD VLRCFG
MSRN/HON number assignment mode
need to be according to MSC number
ADD MHPREFIX Add roaming/switch number prefix
ADD MHSUFFIX According to need, add roaming/switch

number postfix;
ADD MHMSCCFG Set roaming/switch number prefix and

postfixs mapping relationship.
Page53
DN set and Call Source

Configuration
MSC Server
Virtual Server0
DnSet 0
MGW1
Call Source 20
Virtual Server1 Call Source 21

DnSet 1
Call Source 1
LAI-2
Plan on node 0
BICC
MGW2
Call Source 0
LAI-1
BICC
LAI-4
LAI-5
Plan on node 1
According to virtual SERVER node number to plan DN set. For

example, the virtual node 0s DN set is 0, virtual node 1s DN set is
1.
Planning the call source according to the requirements inside one

node, For example, the call source code in one node are planned as
following: 0-9 are assigned for LAIs, 10-19 are assigned for ISUP
trunk, 20-29 are reserved for BICC trunk, the DN set of all the call
Copyright
2006
Co., Ltd. All rights reserved.
source
are Huawei
set asTechnologies
0.
Page54
MSC SERVER B Interface Data

Configuration (Assistant)
get call source code from LAIGCI
table or N7TG table or Office (for
BICC only)
call source table

source no.
0
1
10
11
......
(1)
DnSet
0
1
0
1
name
LAI-1
LAI-4-5
SX-2 from SX-1
SX-1 from SX-2
prefix
861390001
861390001
861390002
861390002
861390003
861390003
route
null
2
0
null
1
3
(2)
callee ana table

DnSet
0
1
0
1
0
1
......
Number analysis according to each node. The DN set is used to

differentiate the different node. For example, node 0s caller number
analysis DN set is 0.
Page55
Summary
DH Data Configuration
Internal and interconnection data configuration
Service conception and data configuration
Page56
Contents
1.
Dual-homing Concept
2.
3.
Data Configuration
4.
Page57
DH Switch and Backward

Auto
Switch
Operation
The interruption of heartbeat links is the unique triggering condition

of auto switch.
Through data configuration, you can specify whether switch and

backward is allowed.
In the N+1 backup DH network, to perform the auto switch, use the
command SET DHWM to set Work mode of all nodes to
Assistant, Switch mode to Automatic, and Takeover mode to
Auto takeover. Then if any active MSOFTX3000 is faulty, and the
heartbeat link is interrupted, the standby MSOFTX3000 will auto
take over all services.
NOTE:
C/D interface congestion.

Paging channel congestion.
Page58

Manual Switch
Carry out the command SET DHWM on the active MSC Server, and
set the status of the active Server node 0 to Deactivated. Then,
carry out the command SET DHWM on the standby MSC Server,
and set the status of the proper virtual Server node to Activated.
Thus, services of the active MSC Server are taken over by the
corresponding virtual Server node on the standby MSC Server.
NOTE
Avoiding the C/D interface congestion.
Avoiding the paging channel congestion.
In addition, before the DH manual switch, make sure that the standby
MSC Server works normally. Otherwise, services will be interrupted after
the manual switch.
Page59

Auto Backward
After switched to a standby MSC Server, the active MSC Server will
auto switch back and take back all services from the standby MSC
Server, if it is recovered and restarted, and its heartbeat link is
recovered.
Before the DH switch, use the command SET DHWM to set Work
mode of all virtual Server nodes to Assistant, Switch mode to
Automatic, and Takeover mode to Auto backward. Then, when
the active MSC Server recovers, all services can auto transfer from
the standby MSC Server to the active MSC Server.
NOTE: In actual use, auto switch and manual backward are

recommended to minimize the time of service interruption and
avoid repeated switches during system abnormality.
Page60

Manual Backward
Manually setting the DH status is the unique triggering condition of

manual backward. In this case, whether to perform dualhoming
backward completely depends on manual setting.
Carry out the command SET DHWM on the standby MSC Server,
and set the status of the standby virtual Server node to
Deactivated. Then, carry out the command SET DHWM on the
active MSC Server, and set the status of the active virtual Server
node 0 to Deactivated. Thus, the virtual Server node 0 takes back
all services from the standby MSC Server.
NOTE: Before the manual backward, make sure that the active MSC
Server recovers. Otherwise, services will be interrupted after the
manual backward.
Page61
Summary
Precaution in DH Switch and Backward
Page62
Thank you
www.huawei.com

9 OWG500210 Dual-Homing Principle and Configuration (VMSC) ISSUE1.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

9 OWG500210 Dual-Homing Principle and Configuration (VMSC) ISSUE1.0

Încărcat de

Drepturi de autor:

Formate disponibile

Dual-homing

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

MSOFTX3000 Dual-Homing User Manual

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Upon completion this course, you will beable to:

Understand the basic concept of dual-homing solution

Perform the data configuration of dual-homing VMSC

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Operation and Maintenance

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

MSC has been

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Redundancy and Security

MSC Server works as control plane, It

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

The Definition of Dual-homing

Assistant MSC Server

DH is a networking mode. In the 3GPP R4 networking and later, one

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

The Definition of Dual-homing

Active MSC Server1

The active MSC Server

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Traditional networking mode

The DH networking mode

There is no special requirement for other network nodes and terminals.

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

DH 1+1 Active and Standby

Standby MSC Server2

1+1Active and Standby Mode: In two MSC Server, one

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

DH 1+1 Assistant Mode

Active MSC Server2

1+1 Assistant Mode: In this mode, there are no difference of

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

DH N+1 Active and Standby

Active MSC Server2

N+1 Active and Standby Mode: N MSOFTX3000s work as

Only N server are active, the other 1 server is always be

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

DN N+1 Assistant Networking

Standby MSC Server3

Active MSC Server2

N+1 Assistant Mode: N MSOFTX3000s work as

All the N+1 Server are active.

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Dual-homing basic concept

The advantage of Dual-homing

The application of the dual- homing networking

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

Operation and Maintenance

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

The Switch Mode of Dualhoming

Virtual MSC Server1

The MSC Server supports the following four DH switch

Virtual MSC Server1

Condition of Manual Switch: Manually setting the DH

DH Virtual MSC Server Service

Virtual MSC Server1

Copyright 2006 Huawei Technologies Co., Ltd. All rights reserved.

DH 1+1 Assistant scheme-the

DH 1+1 Active and Standby schemethe process of making a call