WO2007000094A1 - Procede pour effectuer un raccordement a double anneau de central de commutation mobile - Google Patents
Procede pour effectuer un raccordement a double anneau de central de commutation mobile Download PDFInfo
- Publication number
- WO2007000094A1 WO2007000094A1 PCT/CN2006/001215 CN2006001215W WO2007000094A1 WO 2007000094 A1 WO2007000094 A1 WO 2007000094A1 CN 2006001215 W CN2006001215 W CN 2006001215W WO 2007000094 A1 WO2007000094 A1 WO 2007000094A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- msc server
- msc
- virtual
- physical
- dual
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/14—Backbone network devices
Definitions
- the present invention relates to dual-homing techniques, and more particularly to a method of implementing dual-homing of a Mobile Switching Center (MSC).
- MSC Mobile Switching Center
- the MSC is a key node of the core network circuit domain, which is used to control the mobility management of the circuit domain and various call related services. Therefore, the MSC device Stable operation reflects the reliability of the entire mobile network.
- MSCs are divided into two parts: MSC Server and Media Gateway (MGW).
- MSC Server can manage multiple MGWs, each The range controlled by the MSC Server and the supported user capacity far exceed the MSC in the 2G system, so the reliability level and disaster tolerance requirements of the MSC are particularly important.
- the disaster recovery solution for the MSC is not provided in the existing 2G network.
- An MSC in the network fails, all services within its jurisdiction will be interrupted until the MSC returns to normal.
- the Iu-Flex solution proposed by the 3rd Generation Partnership Project (3GPP) standardization organization in the R5 version provides the following solutions for disaster recovery on the core network side, namely: simultaneous connection of multiple MSCs through the access network and service of general packet radio
- 3GPP 3rd Generation Partnership Project
- the way of core network entities such as Service Support Nodes (SGSN) improves the reliability of the entire system.
- SGSN Service Support Nodes
- a pool area As shown in FIG. 1, the concept of a pool area is proposed in the 3GPP standard TS23.236, that is, a plurality of radio access network (RAN) nodes cover a pool area, such as: multiple radio network controllers ( The area covered by the RNC or the base station controller (BSC) constitutes a pool area, and one pool area is usually served in parallel by a number of core network nodes, which may be MSCs or SGSNs.
- MSC 1, MSC 2, and MSC 3 manage Area 1, Area 2, Area at the same time.
- the pool area 1 composed of the four areas of 5 and Area 6; the MSC 4, the MSC 5, and the MSC 6 simultaneously manage the pool area 2 composed of four areas of Area 2, Area 3, Area 6, and Area 7.
- each core network node is assigned one or several network resource identifiers (NIs).
- NIs network resource identifiers
- the disaster recovery solution shown in Figure 1 has the following problems in practical applications: 1) The implementation is complicated.
- the scheme shown in Figure 1 is a network-wide solution involving core network entities such as MSC and SGSN. Access network entities such as RNC and BSC must be modified accordingly, especially on the MSC side, due to new concepts such as NI and pool areas.
- the introduction of the business process has a great impact on the business process such as location update and handover. It is necessary to consider not only the service situation under the Iu-Flex node in the pool area, but also the interaction and compatibility between the pool area and the non-Iu-Flex node.
- the complexity of the core network side business logic is greatly increased.
- the network topology is complex.
- the access network entity needs to establish a connection with multiple core network entities, which increases the complexity of the network topology and is not conducive to operation and maintenance.
- the called service is defective after the MSC Server fails.
- VLR visitor location register
- HLR Home Location Register
- MGW resources are unavailable when the MSC Server fails.
- MSC Server 1 When a fault occurs, all MGW user plane resources under its jurisdiction will be idle and cannot be put into use. This situation is more prominent when the MSC Server has a large jurisdiction. Because MGW provides a variety of voice processing resources such as TC, EC, and ⁇ bridge, it is very valuable.
- the architecture shown in Figure 2 is not conducive to resource sharing and effective. Load sharing. Summary of the invention
- the main object of the present invention is to provide a method for implementing dual-homing of a mobile switching center, which can implement dual-homing of a mobile switching center, improve security and reliability of the mobile communication network, and is simple and flexible.
- a method for implementing dual-homing of a mobile switching center MSC which divides a physical MSC Server into more than one virtual MSC Server, establishes a dual-homing relationship between different virtual MSC Servers and different physical MSC Servers, and sets the state of the virtual MSC Server to be idle.
- the virtual MSC Server determines whether the handover is required by heartbeat detection. If necessary, sets the state of the virtual MSC Server to active; otherwise, continues normal operation and detection.
- the method further includes: setting a virtual MSC Server in the physical MSC Server to manage and control all subordinate network nodes of the physical MSC Server to which it belongs, and setting the state of the virtual MSC Server to be active.
- the physical MSC Server is each physical MSC Server of all physical MSC Servers; or is a physical MSC Server of all physical MSC Servers having a network node to be managed.
- the virtual MSC Server detects a heartbeat connection between the physical MSC Server to which the user belongs and the physical MSC Server that establishes a dual-homing relationship with the MSC Server, and determines whether the heartbeat is lost or the physical MSC Server is in the heartbeat connection. Whether the status is fault, if it is, you need to switch; otherwise, you do not need to switch.
- the dual-homing relationship between the virtual MSC Server and the physical MSC Server is a dual-homed backup relationship or a dual-homed mutual assistance relationship.
- the dual-homed backup relationship or the mutual-help relationship is a 1+1 backup relationship or a mutual assistance relationship, or an N+1 backup relationship or a mutual assistance relationship, or an N+M backup relationship or a mutual assistance relationship.
- the method further includes: the virtual MSC Server establishing its own signaling link to the subordinate network node of the physical MSC Server having the dual-homing relationship.
- the method further includes: when the user data changes, the physical MSC Server backs up the user data in real time to the VLR corresponding to the virtual MSC Server having the dual-homing relationship.
- the MSC Server is divided into several virtual MSC Servers, the existing physical entities in the network are directly utilized, and new concepts and entities need not be introduced, and the compatibility between the existing entities and the newly introduced nodes is not required, and the implementation is simple. Convenient; and the network topology is simple, which is conducive to operation and maintenance.
- the MSC Server is divided into several virtual MSC Servers, and each virtual MSC Server has its own independent processing subsystem, different virtual MSC Servers are used to establish dual-homing relationship with multiple MSC Server physical entities at the same time. It not only saves the resources of the core network node, but also applies to various networks, such as 2G network and 3G network; and the effect actually embodied in the application is the same as establishing the dual ownership between the physical entities of the MSC Server.
- each virtual MSC Server and the functions and functions provided are completely equivalent to one physical entity of the MSC Server. Therefore, after the double-homed switching occurs, the service logics such as call and handover do not change. There is no additional impact on accounting and statistics. Moreover, there is no special requirement for network elements other than the MSC Server. When the switching occurs, there is no impact on the external network elements. ⁇ 6)
- the dual-homed switchover of the present invention can also be applied to a large-differential version upgrade, which can minimize the impact of the upgrade on the existing network service.
- Figure 1 is a schematic diagram of the Iu-Flex networking
- Figure 3 is a schematic diagram of the MSC implementing dual-homing networking
- Figure 4 is a schematic diagram of the composition of the MSC Server physical entity divided into multiple virtual MSC Servers
- Figure 5 is a schematic diagram of the 1+1 backup networking mode based on the virtual MSC Server
- FIG. 6 is a schematic diagram of a 1+1 mutual assistance networking mode based on a virtual MSC Server
- FIG. 7 is a schematic diagram of an N+1 backup networking mode based on a virtual MSC Server;
- FIG. 8 is a schematic diagram of an N+1 mutual assistance networking mode based on a virtual MSC Server;
- FIG. 9 is a N+M based on a virtual MSC Server.
- FIG. 10 is a schematic diagram of an embodiment of an N+M mutual assistance networking mode based on a virtual MSC Server;
- FIG. 12 is a schematic diagram of a dual-homing network of an Iu interface;
- Figure 13 is a schematic diagram of A-interface dual-homing networking
- FIG. 14 is a schematic diagram of implementing a location update after dual-homing switching
- Figure 15 is a schematic diagram of the implementation of a call between virtual MSC Servers after dual-homing switching. Mode for carrying out the invention
- dual-homing In the context of comprehensive consideration of factors such as equipment integration, cost, disaster tolerance and network security, the concept of dual-homing has been introduced in mobile communication systems, and its role is to prevent large-scale network disasters or sudden disasters. A mechanism for urgent communication during an accident, providing the ability to quickly recover equipment communications in the event of extreme anomalies.
- the so-called dual-homing refers to a special connection mode.
- MGW 1 and MGW 2 are connected to MSC Server A and MSC Server B, and are configured in both MSC Server A and MSC Server B. There are phases of MGW 1 and MGW 2 For the data, MSC Server A and MSC Server B maintain and negotiate the status through the heartbeat connection.
- MGW 1 belongs to MSC Server A, and only MSC Server A provides services.
- MGW 2 belongs to MSC Server B, and only MSC Server B provides services.
- MSC Server A takes over MGW 2 to provide service for MGW 2 until MSC Server B returns to normal.
- the state maintenance and negotiation by the heartbeat connection generally means that two physical entities communicate with each other by using an interactive heartbeat message or a handshake message to notify the other party of the state. Then, whether the heartbeat message is detected or detected in the heartbeat message is detected.
- the information contained is generally referred to as heartbeat detection.
- I is: The physical entity of any MSC Server is divided into more than one virtual MSC Server.
- the physical entity of the MSC Server is referred to as the physical MSC Server.
- One virtual MSC Server is used to manage and control all the subordinates of the physical MSC Server to which it belongs.
- MSC Server A is a physical MSC Server, which can divide MSC Server A into more than one virtual MSC Server by function. For example: According to different service objects
- I MSC Server A is divided into MSC Server-0, MSC Server-1, MSC Server-2 MSC
- MSC Server-N where MSC Server-0 is responsible for managing and controlling all MGWs belonging to MSC Server A, providing services for all MGWs belonging to MSC Server A; the remaining MSC Server-1,
- MSC Server-2 MSC Server-N can be associated with MSC Server B, MSC Server C, etc.
- N-1 physical MSC Servers establish dual-homing relationships, correspondingly, in MSC Server-K MSC
- Server-2 MSC Server-N is configured with data of all MGWs under the jurisdiction of N-1 physical MSC Servers such as MSC Server B and MSC Server C, and other related network elements.
- the data of entities such as HLR, VLR, SMC, etc., so that when a physical MSC Server fails, the corresponding virtual MSC Server provides services for all MGWs under the jurisdiction of the physical MSC Server with dual-homing relationship.
- Each virtual MSC Server is independent of each other and has its own independent processing mechanism, including: signaling subsystem, gateway subsystem, relay subsystem and service subsystem. All virtual MSC Servers share the switching decision in MSC Server A. Mechanism, heartbeat control mechanism, and operation and maintenance management (0&M) mechanism.
- Each virtual MSC Server has its own management status, including: Active (ACTIVE) and Idle (IDLE).
- Active ACTIVE
- Idle Idle
- the virtual MSC Server related signaling network data is activated
- the virtual MSC Server related gateway control data is activated
- the relay data service data is activated
- the virtual MSC Server is in a normal working state.
- the signaling, gateway, relay, and service data owned by the virtual MSC Server are in an inactive state, and the virtual MSC Server cannot provide services.
- each virtual MSC Server is maintained through a heartbeat connection between the physical MSC Server and its physical MSC Server. Normally, all virtual MSC Servers under the physical MSC Server are virtual except for the MGW managed by itself. When the MSC Server is in the active state, the other virtual MSC servers are in the idle state. Only when a virtual MSC Server detects a heartbeat loss or the physical MSC Server status in the heartbeat connection is faulty, indicating that dual-homing switching is required, the virtual MSC Server is The management state is switched under the decision of the switching decision module, from idle to active.
- the dual-homing handover refers to automatic handover, that is, after the virtual MSC Server detects that the physical MSC Server with the dual-homing relationship fails, the virtual MSC Server automatically switches the management state under the decision of the switching decision module, and sets its own state to activation.
- a passive switching mode which may also be referred to as manual switching.
- the switching decision module of a physical MSC Server receives the command to be switched through the O&M, and then sends the corresponding virtual MSC Server to the corresponding virtual MSC Server.
- the switching instruction or the change status command is sent, wherein the switching command sent by the O&M to the switching decision module indicates the virtual MSC Server to be switched; the corresponding virtual MSC server receives the switching instruction of the switching decision module or changes the status command, and sets its own state. For activation. Passive switching can be performed at any time. It is only necessary to send a switching command to the switching decision module through O&M.
- Each physical MSC Server can be divided into more than one virtual MSC Server. Therefore, there are multiple flexible networking modes based on the virtual MSC Server. As shown in Figure 5 to Figure 10, none of the Figure 5 to Figure 10 is considered.
- Network entity Various types of dual-homing networking can be divided into two categories: backup networking mode and mutual-assisted networking mode.
- the so-called backup networking mode refers to a MGW that is not managed by a physical MSC Server itself, and is completely used as another physical MSC Server. Backup;
- the so-called mutual-assisted networking mode means that two physical MSC Servers manage and control one or more MGWs respectively, and the two physical MSC Servers are mutually backed up.
- the physical MSC Servers with dual-homing relationships maintain and negotiate state through heartbeat connections.
- all heartbeat connections are indicated by dotted lines.
- all the thick solid lines indicate the connection between the MGW and the associated physical MSC Server, and the thin solid line indicates the connection between the MGW and the backup or mutual-assisted physical MSC Server.
- FIG. 5 is a 1+1 backup networking mode based on a virtual MSC Server.
- MSC Server A and MSC Server B are two physical MSC servers, and MSC Server A is divided into two virtual networks.
- the MSC Server-0 and the MSC Server-1 know the state of the MSC Server A.
- the state of the MSC Server-1 is maintained through a heartbeat connection with the MSC Server B.
- FIG. 6 is a 1+1 mutual aid networking mode based on a virtual MSC Server.
- MSC Server A and MSC Server B are two physical MSC Servers, where MSC Server A and MSC Server B are respectively divided.
- MSC Server-0 and MSC Server-1 are two virtual MSC Servers, as shown in Figure 11.
- MSC Server-0 in MSC Server A is responsible for providing services for MGW1, MGW2 and MGW3, MSC Server-1 establishes dual-homing relationship with MSC Server B; MSC Server-0 in MSC Server B is responsible for providing services for MGW4, MSC Server- 1 Establish a dual-homing relationship with MSC Server A, and maintain the heartbeat connection between MSC Server A and MSC Server B.
- the state of MSC Server-1 in MSC Server A is maintained through a heartbeat connection with MSC Server B; the state of MSC Server-1 in MSC Server B is maintained through a heartbeat connection with MSC Server A.
- Normally, MSC Server-1 is idle. If MSC Server-1 detects a heartbeat loss or the state of the physical MSC Server in the heartbeat connection is faulty, the state of MSC Server-1 changes from idle to active.
- FIG. 7 is an embodiment of an N+1 active/standby networking mode based on a virtual MSC Server.
- FIG. 7 is an example of three physical MSC servers, where N is 2.
- MSC Server A, MSC Server B, and MSC Server C are three physical MSC Servers.
- MSC Server A and MSC Server C are divided into two virtual MSC Servers: MSC Server-0 and MSC Server-1.
- MSC Server-0 and MSC Server-1 As shown in FIG. 11, three virtual MSC Servers can be divided under MSC Server B, and two virtual MSC Servers can also be divided, because MSC Server B does not manage the MGW itself.
- MSC Server-0 is responsible for providing services for MGW1, MGW2 and MGW3, and MSC Server-1 establishes dual-homing relationship with one virtual MSC Server of MSC Server B.
- MSC Server C MSC Server-0 is responsible for MGW5, MGW6 and MGW7 provide services, and MSC Server-1 establishes a dual-homing relationship with another virtual MSC Server in MSC Server B.
- MSC Server A, MSC Server C and MSC Server B are respectively maintained by heartbeat connection. It is assumed that two virtual MSC Servers are divided under MSC Server B. Under normal circumstances, the two virtual MSC Servers of MSC Server B are idle. A heartbeat loss is detected or the state of the physical MSC Server in a heartbeat connection is faulty. For example, if the MSC Server A fails, it is associated with MSC Server A. The state of the virtual MSC Server establishing the dual-homing relationship changes from idle to active, and is responsible for providing services for MGW1, MGW2, and MGW3.
- FIG. 8 is an embodiment of an N+1 mutual assistance networking mode based on a virtual MSC Server.
- FIG. 8 is an example of three physical MSC servers, where N is 2.
- MSC Server A, MSC Server B, and MSC Server C are three physical MSC Servers.
- MSC Server A and MSC Server C are divided into two virtual MSC Servers: MSC Server-0 and MSC Server-1.
- the MSC Server B is divided into three virtual MSC Servers, one virtual MSC Server is responsible for providing services for the MGW8, and the other two virtual MSC Servers are dual-homed with the MSC Server A and the MSC Server C respectively.
- MSC Server A MSC Server-0 is responsible for providing services for MGW1, MGW2 and MGW3, and MSC Server-1 establishes dual-homing relationship with MSC Server B.
- MSC Server C MSC Server-0 is responsible for providing services for MGW5, MGW6 and MGW7.
- the MSC Server-1 establishes a dual-homing relationship with another virtual MSC Server in the MSC Server B.
- the MSC Server A, the MSC Server C, and the MSC Server B are respectively maintained through a heartbeat connection. Under normal circumstances, the two virtual MSC Servers that establish dual-homing relationship with MSC Server A and MSC Server C under MSC Server B are idle.
- a state of the heartbeat is lost or the state of the physical MSC Server in a heartbeat connection is faulty.
- the MSC ServerA fails, the state of the virtual MSC Server that establishes the dual-homing relationship with the MSC Server A changes from idle to active, and is responsible for the MGW1. MGW2 and MGW3 provide services.
- MSC Server A or MSC Server C MSC Server A is taken as an example. Under normal circumstances, MSC Server-1 in MSC Server A is idle. If heartbeat loss or heartbeat connection is detected, MSC Server B is detected. If the status is faulty, the status of MSC Server-1 in MSC ServerA changes from idle to active, and is responsible for providing services for MGW8.
- FIG. 9 and FIG. 10 are respectively an embodiment of the N+M active/standby networking mode and the mutual assistance networking mode based on the virtual MSC Server.
- MSC Server A, MSC Server B, MSC Server C, and MSC Server D are four physical MSC Servers.
- MSC Server A and MSC Server C are respectively divided into three virtual MSC Servers.
- MSC Server A as an example, one virtual MSC Server is responsible for providing services for MGW1, MGW2, and MGW3, and the other two virtual MSC Servers are respectively associated with MSC.
- Server B and MSC Server D establish a dual-homing relationship.
- MSC Server C is divided into MSC Server A.
- MSC Server B and MSC Server D can be divided into three virtual MSC Servers, or two virtual MSC Servers can be divided because MSC Server B MSC Server D does not manage the MGW itself.
- the MSC Server A and MSC Server C are divided as shown in Figure 9.
- Both MSC Server B and MSC Server D are divided into three virtual MSC Servers, and one virtual MSC Server is responsible for serving the MGWs managed by itself, such as MGW4 or MGW8.
- the other two virtual MSC Servers establish a dual-homing relationship with MSC Server A and MSC Server C, respectively.
- the working principles of MSC Server A and MSC Server C are the same as those of MSC Server A and MSC Server C in Figure 7, the working principle of MSC Server B and MSC Server D and the working principle of MSC Server B in Figure 7. the same.
- the working principles of MSC Server A and MSC Server C are the same as those of MSC Server A and MSC Server C in Figure 8, the working principle of MSC Server B and MSC Server D and the working principle of MSC Server B in Figure 8.
- the virtual MSC Server in the MSC Server A or the virtual MSC Server in the MSC Server C provides services.
- the principle setting is also the same as that described in FIG. 8.
- any two physical MSC servers with heartbeat connections form a dual-homing relationship, and all physical MSC Servers form an N+1 or N+M affiliation relationship.
- the dual-homing of the signaling subsystem is the basis for realizing the dual-homing of the MSC Server.
- the idea of dual-homing the signaling subsystem is:
- the physical MSC Server does not directly provide narrow-band signaling connection.
- the port is forwarded by the broadband signaling of the IP bearer between the MGW/SG and the physical MSC Server.
- the physical connection of the signaling link of other network elements to a physical MSC Server can be configured to the MGW/SG.
- the MGW/SG can flexibly have a dual-homing relationship through the SIGTRAN link with the physical MSC Server. Switch between MSC Servers.
- MSC Server A, MSC Server B, and MSC Server C are three physical MSC Servers, wherein MSC Server A is a mutual MSC Server of MSC Server B and MSC Server C, specifically: based on the present invention
- MSC Server A is a mutual MSC Server of MSC Server B and MSC Server C, specifically: based on the present invention
- the dual-homing idea is divided into three virtual MSC Servers under MSC Server A, which are assumed to be MSC Server-0, MSC Server-1 and MSC Server-2, wherein MSC Server-0 is used to manage and control MGW2, MSC Server-1 And MSC Server-2 establish a dual-homed mutual assistance relationship with MSC Server B and MSC Server C respectively.
- an M3UA link is configured and established between each physical MSC Server and its own managed MGW, such as: between MSC Server A and MGW 2, between MSC Server B and MGW 1, and between MSC Server C and MGW 3. M3UA links are configured between them.
- An MTP3b link is configured and established between each MGW and the RNC under its jurisdiction, and the MGW acts as a signaling gateway (SG) for signaling link forwarding.
- the thick solid line in Figure 12 indicates the primary link.
- M3UA links to MGW1 and MGW3 are respectively configured, but the configured links are not established before the dual-homed switching, as shown by the dotted line in FIG.
- the MSC Server-1 or the MSC Server-2 of the MSC Server A initiates the establishment of the corresponding status to the MGW 1 or the MGW 3 only after the dual-homing switchover occurs, that is, the state of the MSC Server-1 or the MSC Server-2 becomes active.
- the flow of the M3UA link is shown that the MSC Server-1 or the MSC Server-2 of the MSC Server A initiates the establishment of the corresponding status to the MGW 1 or the MGW 3 only after the dual-homing switchover occurs, that is, the state of the MSC Server-1 or the MSC Server-2 becomes active. The flow of the M3UA link.
- the MSC Server MSC Server B and the MSC Server C are three physical MSC Servers, wherein the MSC Server A is a mutual MSC Server of the MSC Server B and the MSC Server C, specifically: According to the attribution idea, there are three virtual MSC Servers under MSC Server A, which are assumed to be MSC Server-0, MSC Server-1 and MSC Server-2, where MSC Server-0 is used to manage and control MGW2, MSC Server-1 and MSC. Server-2 establishes a dual-homed mutual assistance relationship with MSC Server B and MSC Server C respectively. Support A interface double return The M2UA link is configured to carry MTP3 signaling between each physical MSC Server and the MGW, as shown by the thick solid line.
- the MGW3 signaling is carried between the MGW and the BSC through the narrowband MTP2. As indicated by the dotted line, the MGW performs SG forwarding. At this time, MGW does not need to configure signaling points.
- the M2UA and MTP3 links identified by the dotted lines in Figure 13 are not established on the MSC Server A.
- the MSC Server B fails, the virtual MSC Server-1 in the MSC Server A initiates. Establish an M2UA link to MGW 1, as shown in Figure 13, M2UA link-1; and establish an MTP3 link to BSC 1, as shown in Figure 13 MTP3 link-L
- each virtual MSC Server has its own mobility data, such as an RNC belonging to a virtual MSC Server, a BSC> a location area cell, etc.
- MSC Server A and MSC Server B are two physical MSC Servers, and MSC Server A and MSC Server B are respectively divided into two virtual terminals MSC Server: MSC Server-0 and MSC Server- 1.
- MSC Server-0 and MSC Server- 1 As shown in FIG. 14,
- MSC Server-0 in MSC Server A and MSC Server B are respectively used to provide services for MGW1 and MGW2, and MSC Server-1 in MSC Server A establishes dual-homing relationship with MSC Server B.
- MSC Server-1 in MSC Server B establishes a dual-homing relationship with MSC Server A.
- the thin dotted line in Figure 14 indicates that the MSC Server B is faulty, and the dual-homing switchover occurs. That is, the state of the MSC Server-1 in the MSC Server A changes from idle to active, so that the MSC Server-1 in the MSC Server A provides services for the MGW2. This change is reflected in the actual application that MSC Server A provides services for both MGW1 and MGW2.
- LAI5 When LAI4 performs location update, since LAI5 and LAI4 belong to the same MSC Server-1, the related data is inside the same VLR. Therefore, as long as MSC Server-1 is activated normally, the location update will succeed.
- the location update of LAI4 to LAI3 belongs to the virtual MSC Server VLR.
- Location update the process of location update is the same as the prior art, but in this case, the message of inserting user data and deleting user data between the HLR and the two virtual MSC Server VLRs may be triggered.
- the MSC Server VLR activates the corresponding timer for protection to eliminate this competition.
- the user under the MSC Server that has been switched for the first time needs to send the entire network paging because there is no location information, and then the HLR can be sent through the HLR.
- the VLR numbers recorded in the match are matched, and only paging is sent to the VLR range to avoid the simultaneous transmission of paging under multiple virtual MSC Servers, resulting in overload of the access network. For example, after the MSC Server-1 in the MSC ServerA in Figure 14 takes over the MGW2, if the VLR corresponding to the MSC Server-1 does not perform data backup, the user in the LAI4 and LAI5 areas needs to send a page.
- the VLR numbers recorded in the HLR are matched to ensure that only paging is sent to the LAI4 and LAI5 areas, and no paging is sent to the LAI1 LAI3.
- the call within the virtual MSC Server after switching, or the call routing and switching between other network elements does not change.
- the call routing between the MSC Servers that are switched over will not change due to the switching, which can be achieved through the interworking of the signaling subsystems in the virtual MSC Server.
- MSC ServerA and MSC Server B are two physical MSC Servers, and MSC Server A is divided into two virtual terminals MSC Server: MSC Server-0 and MSC Sei-ver-1, MSC Server. - 1 has a dual-homing relationship with MSC Server B.
- the dotted line in Fig. 15 indicates that the MSC Server B has failed, and the state of the MSC Server-1 changes from idle to active, and dual-homing switching occurs. If UE1 accesses UE2 under RNC2 from RNC1, before dual-homed switching, The call is handled as an outgoing call at MSC Server A and as an incoming call at MSC Server B.
- each virtual MSC Server has its own independent processing subsystem. Therefore, the call still needs to communicate with the signaling subsystem between the virtual MSC Servers, that is, through the MSC to which the RNC-1 belongs.
- the same is true for switching.
- the service logics such as call and handover do not change, and there is no additional impact on billing and statistics.
- the VLR data backup is not started, after the dual-homed switchover, the original VLR data does not exist on the new MSC Server.
- the calling service if no user data is found, the call fails and the mobile phone location update is triggered.
- the called service if there is no user data after routing to the new MSC Server, the data recovery process is triggered. Although this situation has no effect on the calling and called services, it will affect the HLR for a certain period of time. The impact depends on the number of specific users in the VLR and the time when the switching occurs.
- the physical MSC Server backs up the user data to the VLR corresponding to the backup or mutual help virtual MSC Server in real time, so that after the dual-homed switchover, the calling and called services are not affected. Affects and reduces the load shock to the HLR.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Hardware Redundancy (AREA)
- Paper (AREA)
- Crystals, And After-Treatments Of Crystals (AREA)
Description
一种实现移动交换中心双归属的方法 技术领域
本发明涉及双归属技术, 尤指一种实现移动交换中心(MSC )双归属的方 法。 发明背景
在第二代(2G )、 第三代(3G )移动通信系统中, MSC是核心网电路域 的关键节点, 用于控制电路域的移动性管理和各种呼叫相关业务, 因此, MSC 设备的稳定运行体现了整个移动网絡的可靠性程度。随着移动通信网络的飞速 发展, MSC的容量越来越大,特别是在 3G R4的架构下, MSC分为 MSC Server 和媒体网关 (MGW ) 两部分, 一个 MSC Server可以管理多个 MGW, 每个 MSC Server所控制的范围和支持的用户容量远远超过 2G系统中的 MSC, 因 而 MSC的可靠性程度和容灾需求显得尤为重要。
现有 2G网络中没有提供针对 MSC的容灾解决方案, 当网络中某个 MSC 出现故障后, 其所辖范围内的业务将全部中断直到该 MSC恢复正常。 第三代 合作伙伴计划 ( 3GPP )标准化组织在 R5版本中提出的 Iu-Flex方案对核心网 侧的容灾提供了以下解决方案, 就是: 通过接入网同时连接多个 MSC以及服 务通用分组无线业务支持节点(SGSN )等核心网实体的方式, 提高整个系统 的可靠性程度。
如图 1所示, 3GPP标准 TS23.236中提出了池区域的概念, 即: 将若干个 无线接入网络(RAN )节点覆盖的区域组成一个池区域, 如: 将多个无线网络 控制器(RNC )或基站控制器(BSC )覆盖的区域组成一个池区域, 一个池区 域通常由若干个核心网节点并行地提供服务, 所述核心网节点可以是 MSC或 SGSN。 比如: 图 1中 MSC 1、 MSC 2、 MSC 3同时管理 Area 1、 Area 2、 Area
5和 Area 6这四个区域构成的池区域 1; MSC 4、 MSC 5、 MSC 6同时管理 Area 2、 Area 3、 Area 6和 Area 7这四个区域构成的池区域 2。 为标识核心网节点, 每个核心网节点会被分配一个或若干个网络资源标识(N I ), 当移动终端建 立与核心网节点的非接入层(NAS )连接时, RAN节点会根据初始 NAS消息 中携带的 NRI, 将该初始 NAS消息路由到 NRI对应的核心网节点。 以池区域 1为例, 池区域内的每个 RAN节点都同时连接到 MSC 1、 MSC 2、 MSC 3上, 如果其中任何一个 MSC发生故障, 接入网就会取消对故障 MSC的选路, 将 新发起的话务疏导到其它 MSC上, 从而达到容灾的效果。
但是, 图 1所示的这种容灾解决方案在实际应用中存在以下的问题: 1 ) 实现复杂。 图 1 所示方案属于全网解决方案, 涉及到核心网实体如 MSC和 SGSN,接入网实体如 RNC和 BSC都要进行相应修改,特别是在 MSC 一侧, 由于 N I、 池区域等新概念的引入, 对位置更新、 切换等业务流程都产 生很大影响, 不仅需要考虑池区域内 Iu-Flex节点下的业务情况, 同时还要考 虑池区域与非 Iu-Flex节点间的交互和兼容, 大大增加了核心网侧业务逻辑的 复杂性。
2 )在 2G网絡如 GSM中实施困难。 Iu-Flex技术是在 3GPP R5中引入的, 2G网络中的 BSC设备都不能支持, 如果要支持需要进行大量升级操作, 如此 不利于在 GSM网络开展。
3 )网络拓朴复杂。 在 Iu-Flex的解决方案中, 接入网实体要与多个核心网 实体建立连接, 增加了网络拓朴的复杂性, 不利于运行维护。
4 ) MSC Server故障后被叫业务存在缺陷。参见图 2,在图 2所示的 Iu-Flex 组网下, MSC Server 1发生故障后, 如果原来在 MSC Serverl对应的访问位置 寄存器(VLR )下注册的用户不发起位置更新流程或主叫业务流程, 则这些用 户将一直不能被成功呼叫, 因为在归属位置寄存器(HLR )内记录的这些用户 的 VLR地址为 MSC Serverl下的 VLR地址。
5 ) MSC Server故障时 MGW资源不可使用。 如图 2所示, 在 MSC Server
1发生故障时, 其管辖的所有 MGW用户面资源将处于闲置状态, 不能投入使 用。 这种情况在 MSC Server管辖范围大的时候问题更为突出, 因为 MGW要 提供 TC、 EC、 ΜΡΊΎ网桥等多种语音处理资源, 都很宝贵, 图 2所示架构不 利于资源共享和有效的负荷分担。 发明内容
有鉴于此,本发明的主要目的在于提供一种实现移动交换中心双归属的方 法, 能实现移动交换中心的双归属, 提高移动通信网络的安全可靠性, 且实现 简单灵活。
为达到上述目的, 本发明的技术方案是这样实现的:
一种实现移动交换中心 MSC双归属的方法,将物理 MSC Server划分为一 个以上虚拟 MSC Server, 建立不同虚拟 MSC Server与不同物理 MSC Server 之间的双归属关系, 并设置虚拟 MSC Server的状态为空闲, 虚拟 MSC Server 通过心跳检测判断是否需要切换, 如果需要, 则将虚拟 MSC Server的状态设 置为激活; 否则, 继续正常工作和检测。
该方法进一步包括:设置物理 MSC Server中的一个虚拟 MSC Server管理 和控制自身所属物理 MSC Server的所有下属网络节点, 并设置该虚拟 MSC Server的状态为激活。 这里, 所述物理 MSC Server为所有物理 MSC Server中 的每个物理 MSC Server; 或者为所有物理 MSC Server中具有需管理的网络节 点的物理 MSC Server。
上述方案中, 所述判断是否需要切换为: 虚拟 MSC Server检测自身所属 物理 MSC Server和与自身建立双归属关系的物理 MSC Server之间的心跳连 接, 判断心跳是否丟失或心跳连接中物理 MSC Server的状态是否为故障, 如 果是, 则需要切换; 否则不需要切换。 或者, 所述判断是否需要切换为: 虚拟 MSC Server判断是否收到切换命令或更新状态命令, 如果收到, 则需要切换; 否则不需要切换。
上述方案中,所述虚拟 MSC Server与物理 MSC Server之间的双归属关系 为双归属备份关系、 或为双归属互助关系。 其中, 所述双归属备份关系或互助 关系为 1+1备份关系或互助关系、 或为 N+1备份关系或互助关系、 或为 N+M 备份关系或互助关系。
当需要切换时, 该方法进一步包括: 虚拟 MSC Server建立自身到具有双 归属关系的物理 MSC Server下属网络节点的信令链路。
该方法进一步包括: 用户数据发生变化时, 物理 MSC Server将用户数据 实时备份到具有双归属关系的虚拟 MSC Server对应的 VLR中。
本发明所提供的实现移动交换中心双归属的方法, 具有以下的优点和特 点:
1 )由于在 MSC之间建立了双归属关系, 因此大大提高了移动通信网络的 安全可靠性, 提供了应对因自然、 人为等不可抗拒因素引发灾难的解决方案。
2 ) 由于是将 MSC Server划分为若干个虚拟 MSC Server, 直接利用网络 中已有的物理实体, 不需要引入新的概念和实体, 无需考虑已有实体与新引入 节点的兼容性, 实现简单、 方便; 且网络拓朴结构简单, 利于运行维护。
3 ) 由于将 MSC Server划分为若干个虚拟 MSC Server, 且每个虚拟 MSC Server拥有各自独立的处理子系统, 所以, 利用不同的虚拟 MSC Server同时 与多个 MSC Server物理实体之间建立双归属关系, 不仅能节省核心网节点资 源, 适用于各种网絡,.如 2G网络、 3G网络; 而且在应用中实际体现出的效 果与 MSC Server物理实体间建立双归属一样。
4 ) 由于实际使用的物理实体少, 所以在出现因故障引发的倒换过程中, 对现网业务影响最小、 对现网资源利用率最高。
5 )本发明中,每个虛拟 MSC Server的组成以及所提供的功能和作用完全 相当于一个 MSC Server物理实体, 所以, 在发生双归属倒换后对呼叫、 切换 等业务逻辑不会发生变化,对计费、统计也没有附加影响;并且,对 MSC Server 以外的网元也无特殊需求, 倒换发生时对外部网元无影响。
■ 6 )本发明的双归属倒换还可应用于大差异性的版本升级, 能尽量减少升 级对现网业务的冲击。 附图简要说明
图 1为 Iu-Flex组网示意图; 图 3为 MSC实现双归属的组网示意图;
图 4为 MSC Server物理实体划分为多个虚拟 MSC Server的组成示意图; 图 5为基于虚拟 MSC Server的 1+1备份组网方式示意图;
图 6为基于虛拟 MSC Server的 1+1互助组网方式示意图;
图 7为基于虚拟 MSC Server的 N+1备份组网方式一实施例示意图; 图 8为基于虚拟 MSC Server的 N+1互助组网方式一实施例示意图; 图 9为基于虚拟 MSC Server的 N+M备份组网方式一实施例示意图; 图 10为基于虚拟 MSC Server的 N+M互助组网方式一实施例示意图; 图 12为 Iu接口双归属组网示意图;
图 13为 A接口双归属组网示意图;
图 14为双归属倒换后位置更新实现示意图;
图 15为双归属倒换后虚拟 MSC Server间呼叫实现的示意图。 实施本发明的方式
在综合考虑设备集成度、 成本、 容灾能力及网络安全性等几方面因素的情 况下,移动通信系统中引入了双归属的概念,其作用在于防止网络大面积瘫痪、 或在出现突发灾害事故时能够紧急提供通信的机制,提供在极端异常情况发生 时设备通信的迅速恢复能力。 所谓双归属, 实际是指一种特殊的连接方式, 如 图 3所示, MGW 1、 MGW 2均与 MSC Server A和 MSC Server B建立有连接 关系, 且 MSC Server A和 MSC Server B中都配置有 MGW 1和 MGW 2的相
关数据, MSC Server A和 MSC Server B之间通过心跳连接进行状态的维护和 协商。 在正常运行情况下, MGW 1归属于 MSC Server A, 仅由 MSC Server A 提供服务, MGW 2归属于 MSC Server B, 仅由 MSC Server B提供服务; 当某 个 MSC Server如 MSC Server B发生故障时,则由 MSC Server A接管 MGW 2 , 为 MGW 2提供服务, 直到 MSC Server B恢复正常为止。 这里, 所述通过心 跳连接进行状态维护和协商通常是指:两个物理实体之间通过交互心跳消息或 称握手消息, 告知对方自身的状态, 那么, 检测心跳消息是否存在或检测心跳 消息中所含的信息一般就称为心跳检测。
为了在实现双归属的同时更节省核心网节点的资源, 本发明的基本思想
I 是: 将任意一个 MSC Server物理实体划分为一个以上虚拟 MSC Server, 下文 将 MSC Server物理实体均筒称为物理 MSC Server,其中一个虚拟 MSC Server 用于管理和控制自身所属物理 MSC Server 的所有下属网络节点, 比如所有 MGW,如果自身所属物理 MSC Server下没有需管理的网络节点,该虚拟 MSC Server可以不设置;其余每个虚拟 MSC Server可分别与不同的物理 MSC Server
; 建立双归属关系, 在其余每个虚拟 MSC Server 中分别配置相应物理 MSC Server的所有相关数据, 比如: 配置物理 MSC Server所管辖的所有 MGW的 数据, 相关其它网元如 HLR、 VLR、 SMC等实体的数据。
如图 4所示, MSC Server A为一个物理 MSC Server, 可以按功能将 MSC Server A划分为一个以上虚拟 MSC Server, 比如: 根据提供服务对象的不同将
I MSC Server A划分为 MSC Server-0, MSC Server- 1 , MSC Server-2 MSC
Server-N, 其中, MSC Server-0负责管理和控制归属于 MSC Server A的所有 MGW,为所有归属于 MSC Server A的 MGW提供服务;其余的 MSC Server- 1 ,
MSC Server-2 MSC Server-N可以分别与 MSC Server B、 MSC Server C等
N-1 个物理 MSC Server建立双归属关系, 相应的, 在 MSC Server- K MSC
; Server-2 MSC Server-N中分别配置有 MSC Server B、 MSC Server C等 N-1 个物理 MSC Server各自所管辖的所有 MGW的数据, 以及相关其它网元如
HLR、 VLR、 SMC等实体的数据, 以便在某个物理 MSC Server发生故障时, 由对应的虚拟 MSC Server为具有双归属关系的物理 MSC Server所管辖的所有 MGW提供服务。
每个虛拟 MSC Server相互独立, 分别拥有各自独立的一套处理机制, 包 括: 信令子系统、 网关子系统、 中继子系统和业务子系统, 所有的虚拟 MSC Server共享 MSC Server A中的倒换判决机制、 心跳控制机制以及操作和维护 管理 (0&M )机制。
每个虚拟 MSC Server拥有自己的管理状态, 包括: 激活 (ACTIVE )和 空闲 (IDLE )。 当某个虚拟 MSC Server激活时, 该虚拟 MSC Server相关的信 令网数据激活、 该虚拟 MSC Server相关的网关控制数据激活, 从而中继数据 业务数据都激活,该虚拟 MSC Server处于正常工作状态可以提供相应的服务。 反之, 如果某个虚拟 MSC Server处于空闲状态, 则该虚拟 MSC Server拥有的 信令、 网关、 中继、 业务数据都处于非激活状态, 该虚拟 MSC Server不能提 供服务。
每个虚拟 MSC Server的状态通过与其具有双归属关系的物理 MSC Server 之间的心跳连接进行维护, 正常情况下, 物理 MSC Server下的所有虚拟 MSC Server中, 除了为自身管理的 MGW提供服务的虚拟 MSC Server处于激活状 态以外, 其余虚拟 MSC Server均处于空闲状态, 只有在某个虚拟 MSC Server 检测到心跳丟失或者心跳连接中物理 MSC Server状态为故障时, 说明需要双 归属切换, 该虚拟 MSC Server才在倒换判决模块的判决下切换管理状态, 由 空闲变为激活。
这里, 所述双归属切换指的是自动切换, 即: 虚拟 MSC Server检测到具 有双归属关系的物理 MSC Server发生故障后, 就在倒换判决模块的判决下自 动切换管理状态, 设置自身的状态为激活。 在实际应用中, 还存在一种被动切 换方式, 也可以称为人工切换, 具体说就是: 某个物理 MSC Server的倒换判 决模块通过 0&M接收到需要切换的命令后, 则向相应的虚拟 MSC Server发
送切换指令或更改状态指令, 其中, 0&M向倒换判决模块发送的切换命令中 会指示需切换的虚拟 MSC Server; 相应虚拟 MSC Server收到倒换判决模块的 切换指令或更改状态指令, 设置自身的状态为激活。 被动切换可随时进行, 只 要通过 0&M向倒换判决模块发切换指令即可。
由于每个物理 MSC Server都可以划分为一个以上虚拟 MSC Server,所以, 基于虚拟 MSC Server存在多种灵活地组网方式, 如图 5至图 10所示, 图 5至 图 10中均未考虑接入网实体。 各种类型的双归属组网方式可分为两大类: 备 份组网方式和互助组网方式, 所谓备份组网方式是指一个物理 MSC Server自 身没有管理的 MGW, 完全作为另一个物理 MSC Server的备份; 所谓互助组 网方式是指两个物理 MSC Server分别管理和控制一个或一个以上 MGW, 且 两个物理 MSC Server之间互为备份。 无论备份组网方式还是互助组网方式, 具有双归属关系的物理 MSC Server之间通过心跳连接进行状态的维护和协 商, 图 5至图 10中, 所有心跳连接用点划线表示。 图 5至图 10中, 所有的粗 实线表示 MGW与所属物理 MSC Server之间的连接, 细实线表示 MGW与备 份或互助物理 MSC Server之间的连接。 下面分别结合每个附图详细说明基于 虚拟 MSC Server的组网方式:
如图 5所示, 图 5为基于虚拟 MSC Server的 1+1备份组网方式, 图 5中 MSC Server A和 MSC Server B为两个物理 MSC Server, 其中, MSC Server A 下划分有两个虚拟 MSC Server: MSC Server-0和 MSC Server- 1 ,如图 11所示, MSC Server-0负责为 MGW1、 MGW2和 MGW3提供服务, MSC Server- 1与 MSC Server B建立双归属关系, MSC Server A和 MSC Server B之间通过心跳 连接进行维护, MSC Server-0和 MSC Server- 1知道 MSC Server A的状态, MSC Server- 1的状态通过与 MSC Server B之间的心跳连接进行维护, 正常情况下, MSC Server- 1处于空闲状态, 如果 MSC Server- 1通过检测 MSC Server A和 MSC Server B之间的心跳连接发现心跳丟失或心跳连接中 MSC Server B的状 态为故障, 则 MSC Server- 1的状态由空闲变为激活。
如图 6所示, 图 6为基于虚拟 MSC Server的 1+1互助组网方式, 图 6中 MSC Server A和 MSC Server B为两个物理 MSC Server, 其中, MSC Server A 和 MSC Server B下分别划分有两个虚拟 MSC Server: MSC Server-0和 MSC Server- 1,如图 11所示。 MSC Server A中的 MSC Server-0负责为 MGW1、 MGW2 和 MGW3提供服务, MSC Server- 1与 MSC Server B建立双归属关系; MSC Server B中的 MSC Server-0负责为 MGW4提供服务, MSC Server- 1与 MSC Server A建立双归属关系, MSC Server A和 MSC Server B之间通过心跳连接 进行维护。 MSC Server A中 MSC Server- 1的状态通过与 MSC Server B之间的 心跳连接进行维护; MSC Server B中 MSC Server- 1的状态通过与 MSC Server A之间的心跳连接进行维护。正常情况下, MSC Server- 1处于空闲,如果 MSC Server- 1检测心跳丢失或心跳连接中物理 MSC Server的状态为故障, 则 MSC Server-1的状态由空闲变为激活。
如图 7所示, 图 7为基于虚拟 MSC Server的 N+1主备组网方式的一个实 施例,图 7以三个物理 MSC Server为例,其中 N为 2。图 7中, MSC Server A、 MSC Server B和 MSC Server C为三个物理 MSC Server, 其中, MSC Server A 和 MSC Server C下都划分有两个虚拟 MSC Server: MSC Server-0和 MSC Server-1 , 如图 11所示, MSC Server B下可以划分三个虚拟 MSC Server, 也 可以划分两个虚拟 MSC Server,因为 MSC Server B自身未管理 MGW。在 MSC Server A中, MSC Server-0负责为 MGW1、 MGW2和 MGW3提供服务, MSC Server-1与 MSC Server B中的一个虚拟 MSC Server建立双归属关系; MSC Server C中, MSC Server-0负责为 MGW5、 MGW6和 MGW7提供服务, MSC Server-1与 MSC Server B中的另一个虚拟 MSC Server建立双归属关系。 MSC Server A, MSC Server C与 MSC Server B之间分别通过心跳连接进行维护,假 设 MSC Server B下划分了两个虛拟 MSC Server, 正常情况下, MSC Server B 的两个虚拟 MSC Server处于空闲, 当检测到某个心跳丟失或某个心跳连接中 物理 MSC Server的状态为故障, 比如 MSC Server A故障, 则与 MSC Server A
建立双归属关系的虚拟 MSC Server的状态由空闲变为激活, 负责为 MGW1、 MGW2和 MGW3提供服务。
如图 8所示, 图 8为基于虚拟 MSC Server的 N+1互助组网方式的一个实 施例,图 8以三个物理 MSC Server为例,其中 N为 2。图 7中, MSC Server A、 MSC Server B和 MSC Server C为三个物理 MSC Server, 其中, MSC Server A 和 MSC Server C下都划分有两个虚拟 MSC Server: MSC Server-0和 MSC Server- 1 , 如图 11所示, MSC Server B下划分有三个虚拟 MSC Server, —个 虚拟 MSC Server负责为 MGW8提供服务, 另外两个虚拟 MSC Server分别与 MSC Server A和 MSC Server C建立双归属关系。 MSC Server A中, MSC Server-0负责为 MGW1、 MGW2和 MGW3提供服务, MSC Server- 1与 MSC Server B建立双归属关系; MSC Server C中 , MSC Server-0负责为 MGW5、 MGW6和 MGW7提供服务, MSC Server- 1与 MSC Server B中的另一个虚拟 MSC Server建立双归属关系。 MSC Server A、 MSC Server C与 MSC Server B 之间分别通过心跳连接进行维护,正常情况下, MSC Server B下与 MSC Server A和 MSC Server C建立双归属关系的两个虚拟 MSC Server处于空闲, 当检测 到某个心跳丢失或某个心跳连接中物理 MSC Server的状态为故障, 比如 MSC ServerA故障, 则与 MSC Server A建立双归属关系的虚拟 MSC Server的状态 由空闲变为激活, 负责为 MGW1、 MGW2和 MGW3提供服务。 同理, 对于 MSC Server A或 MSC Server C来说, 以 MSC Server A为例, 正常情况下, MSC Server A中的 MSC Server- 1处于空闲状态, 如果检测到心跳丟失或心跳 连接中 MSC Server B的状态为故障,则 MSC ServerA中 MSC Server- 1的状态 由空闲变为激活, 负责为 MGW8提供服务。这里,如果 MSC ServerA和 MSC Server C中的 MSC Server- 1都检测到 MSC Server B故障, 可以设置一定的原 则来确定由 MSC Server A的 MSC Server- 1还是 MSC Server C的 MSC Server- 1 为 MGW8提供服务, 比如: 设置谁先检测到由谁提供服务, 或者根据当前负 载状况等等。
图 9和图 10分别为基于虚拟 MSC Server的 N+M主备组网方式和互助组 网方式的一个实施例,图 9、图 10均以四个物理 MSC Server为例,其中,N=2, M=2。 图 9和图 10中, MSC Server A、 MSC Server B、 MSC Server C和 MSC Server D为四个物理 MSC Server。 对于图 9, MSC Server A和 MSC Server C 下分别划分三个虛拟 MSC Server,以 MSC Server A为例,一个虚拟 MSC Server 负责为 MGW1、 MGW2和 MGW3提供服务, 另外两个虚拟 MSC Server分别 与 MSC Server B和 MSC Server D建立双归属关系, MSC Server C的划分与 MSC Server A一样; MSC Server B和 MSC Server D可以划分三个虚拟 MSC Server, 也可以划分两个虛拟 MSC Server, 因为 MSC Server B、 MSC Server D 自身未管理 MGW。 对于图 10, MSC Server A和 MSC Server C的划分与图 9 一样, MSC Server B和 MSC Server D均划分三个虚拟 MSC Server, 一个虚拟 MSC Server负责为自身管理的 MGW, 如 MGW4或 MGW8提供服务, 另外 两个虚拟 MSC Server分别与 MSC Server A和 MSC Server C建立双归属关系。 图 9中, MSC Server A和 MSC Server C的工作原理与图 7中 MSC Server A和 MSC Server C的工作原理相同, MSC Server B和 MSC Server D的工作原理与 图 7中 MSC Server B的工作原理相同。图 10中, MSC Server A和 MSC Server C的工作原理与图 8中 MSC Server A和 MSC Server C的工作原理相同, MSC Server B和 MSC Server D的工作原理与图 8中 MSC Server B的工作原理相同, 当 MSC Server B或 MSC Server D发生故障后, 具体由 MSC Server A中的虚 拟 MSC Server还是由 MSC Server C中的虚拟 MSC Server提供服务, 原则的 设定也与图 8所述相同。
在图 7至图 10的组网方式下, 任意两个具有心跳连接的物理 MSC Server 之间形成双归属关系, 所有的物理 MSC Server之间形成 N+1或 N+M归属关 系。
在上述各种组网方式下, 信令子系统双归属是实现 MSC Server双归属的 基础。 信令子系统双归属的思想是: 物理 MSC Server不直接提供窄带信令接
口, 而是通过 MGW/SG与物理 MSC Server之间的 IP承载的宽带信令进行转 接。 这样, 对于其它网元到达某个物理 MSC Server的信令链路物理连接都可 以配置到 MGW/SG, MGW/SG通过与物理 MSC Server之间的 SIGTRAN链路, 可以灵活的在具有双归属关系的 MSC Server之间切换。
如图 12所示, MSC Server A、 MSC Server B和 MSC Server C为三个物理 MSC Server, 其中, MSC Server A是 MSC Server B和 MSC Server C的互助 MSC Server, 具体来说就是: 基于本发明的双归属思想, MSC Server A下划分 有三个虚拟 MSC Server,假设为 MSC Server-0、MSC Server- 1和 MSC Server-2, 其中, MSC Server-0用于管理和控制 MGW2, MSC Server- 1和 MSC Server-2 分别与 MSC Server B和 MSC Server C建立双归属互助关系。 图 12中, 每个 物理 MSC Server与自身管理的 MGW之间配置并建立有 M3UA链路, 比如: MSC Server A与 MGW 2之间、 MSC Server B与 MGW 1之间、 MSC Server C 与 MGW 3之间均配置有 M3UA链路。 每个 MGW和所辖的 RNC之间配置并 建立有 MTP3b链路, MGW作为信令网关(SG )进行信令链路转发, 图 12 中的粗实线表示主用链路。在 MSC Server- 1和 MSC Server-2的信令子系统中, 分别配置有到达 MGW1和 MGW3的 M3UA链路, 但所配置的这些链路在双 归属倒换前没有建立, 如图 12中虚线所示, 只有发生双归属倒换后, 即 MSC Server- 1 或 MSC Server-2的状态变为激活时, 才由 MSC Server A的 MSC Server- 1或 MSC Server-2向 MGW 1或 MGW 3发起建立相应 M3UA链路的流 程。
如图 13所示, MSC Server MSC Server B和 MSC Server C为三个物理 MSC Server, 其中, MSC Server A是 MSC Server B和 MSC Server C的互助 MSC Server, 具体来说就是: 基于本发明的双归属思想, MSC Server A下划分 有三个虚拟 MSC Server,假设为 MSC Server-0, MSC Server-1和 MSC Server-2, 其中, MSC Server-0用于管理和控制 MGW2, MSC Server-1和 MSC Server-2 分别与 MSC Server B和 MSC Server C建立双归属互助关系。支持 A接口双归
属的每个物理 MSC Server与 MGW之间配置 M2UA链路承载 MTP3信令,如 粗实线所示; MGW和 BSC之间通过窄带 MTP2承载 MTP3信令, 如点线所 示, MGW做 SG转发, 此时 MGW不需要配置信令点。 在双归属倒换前, 图 13中虚线标识的 M2UA和 MTP3链路在 MSC Server A上没有建立,双归属倒 换发生时,比如 MSC Server B发生故障, MSC Server A中的虚拟 MSC Server-1 会发起建立到 MGW 1的 M2UA链路, 如图 13中所示 M2UA link-1; 同时建 立到 BSC 1的 MTP3链路, 如图 13中所示 MTP3 link-L
图 12和图 13所述方式同样适用于物理 MSC Server与其它网元通过窄带 信令通信的情况, 比如 HLR、 SCP、 SMC等实体。 当外部网元比如 HLR、 SCP 等支持 SIGTRAN时, 物理 MSC Server也可以直接采用宽带信令与这些实体 进行连接。
对于实现 MSC双归属的方案, 还需要解决倒换后的移动性管理、 呼叫路 由以及数据备份问题。
针对移动性管理, 由于每个虚拟 MSC Server都拥有自己的移动性数据, 比如归属于某个虚拟 MSC Server的 RNC、 BSC> 位置区小区等等, 那么, 只 要倒换后的虚拟 MSC Server中的信令子系统能够正常激活,虚拟 MSC Server, VLR内的位置更新就可以成功完成。 如图 14所示, 图 14中, MSC Server A 和 MSC Server B为两个物理 MSC Server, MSC Server A和 MSC Server B下 分别划分有两个虚拟终端 MSC Server: MSC Server-0和 MSC Server-1 , 如图 11所示, MSC Server A和 MSC Server B中的 MSC Server-0分别用于为 MGW1 和 MGW2提供服务, MSC Server A中的 MSC Server-1与 MSC Server B建立 双归属关系, 同样, MSC Server B中的 MSC Server-1与 MSC Server A建立双 归属关系。 图 14中细虚线表示 MSC Server B发生故障, 则发生双归属倒换, 即 MSC Server A中 MSC Server-1的状态由空闲变为激活,从而使 MSC Server A中 MSC Server-1为 MGW2提供服务,这种变化在实际应用中就体现为 MSC Server A同时为 MGW1和 MGW2提供服务。 此时, 如果某个终端从 LAI5到
LAI4进行位置更新时, 由于 LAI5和 LAI4同属于 MSC Server- 1管辖,相关数 据在同一个 VLR内部, 所以, 只要 MSC Server-1正常激活, 位置更新就会成 功。
当某个终端从 LAI4到 LAI3进行位置更新时, 由于 LAI4和 LAI3分别属 于不同的虚拟 MSC Server,每个虚拟 MSC Server对应自己的 VLR,因此, LAI4 到 LAI3的位置更新属于虚拟 MSC Server VLR之间的位置更新, 位置更新的 处理过程与现有技术相同, 但这种情况下, 可能会引发 HLR与两个虚拟 MSC Server VLR之间插入用户数据和删除用户数据的消息竟争, 可以通过在虚拟 MSC Server VLR启动相应定时器进行保护的方式, 消除这种竟争。
在具有双归属关系的 MSC Server对应的 VLR不进行数据备份的情况下, 发生倒换的 MSC Server下的用户首次做被叫时由于没有位置信息需要下发全 网寻呼, 这时, 可通过 HLR中记录的 VLR号码进行匹配, 只向这个 VLR范 围下发寻呼, 以避免在多个虚拟 MSC Server下同时下发寻呼导致接入网絡的 过载。 比如: 图 14中 MSC ServerA中的 MSC Server- 1接管 MGW2后, 如果 MSC Server- 1对应的 VLR没有进行数据备份,则对 LAI4和 LAI5区域内的用 户需要下发寻呼, 此时, 就利用 HLR中记录的 VLR号码进行匹配, 保证仅向 LAI4和 LAI5区域发寻呼, 而不会向 LAI1 LAI3下发寻呼。
针对呼叫路由问题, 由于本发明中虚拟 MSC Server拥有各自呼叫路由数 据, 所以, 倒换后虚拟 MSC Server内呼叫、 或者与其它网元之间的呼叫路由 与倒换前不发生改变。 特别是发生倒换的 MSC Server之间的呼叫路由也不会 因为发生倒换而改变,这可以通过虚拟 MSC Server中信令子系统的互通实现。
如图 15所示, 图 15中, MSC ServerA和 MSC Server B为两个物理 MSC Server, MSC Server A下划分有两个虚拟终端 MSC Server: MSC Server-0和 MSC Sei-ver-1 , MSC Server- 1与 MSC Server B具有双归属关系。 图 15中虚线 表示 MSC Server B发生故障, 则 MSC Server- 1的状态从空闲变为激活, 发生 双归属倒换。如果 UE1从 RNC1接入呼叫 RNC2下的 UE2,在双归属倒换前,
该呼叫在 MSC Server A被处理为出局呼叫,在 MSC Server B处理为入局呼叫。 双归属倒换后, 由于每个虚拟 MSC Server都有自己独立的一套处理子系统, 因此, 该呼叫仍需要通过虚拟 MSC Server之间信令子系统的互通, 即: 通过 RNC-1所属的 MSC Server-0与 RNC-2所属的 MSC Server- 1之间信令子系统之 间的交互, 故此, 在两个虚拟 MSC Server上仍然被处理为一个出局呼叫和入 局呼叫, 虚拟 MSC Server之间的切换也是一样。 这样的处理使得双归属 MSC Server倒换前后, 呼叫、 切换等业务逻辑均不会发生变化, 对计费、 统计也没 有附加影响。
对于 MSC Server VLR之间的数据备份, 存在互助或备份关系的 MSC Server VLR之间, 可以选择启动数据备份机制:
如果不启动 VLR数据备份,发生双归属倒换后,原 VLR数据在新的 MSC Server上不存在。 这种情况下, 对于主叫业务, 如果发现没有用户数据, 则呼 叫失败同时触发手机位置更新; 对于被叫业务, 如果路由到新 MSC Server后 发现没有用户数据, 则触发数据恢复流程。这种情况虽然对主被叫业务都没有 影响,但对 HLR在一定时间内会有一定影响 ,影响大小依赖与发生倒换的 VLR 内的具体用户数量和倒换发生的时间。
如果启动 VLR数据备份机制,则当用户数据发生变化时,物理 MSC Server 实时将用户数据备份到备份或互助虚拟 MSC Server对应的 VLR中, 如此,发 生双归属倒换后, 主被叫业务都不受影响且减小了对 HLR的负荷冲击。
以上所述,仅为本发明的较佳实施例而已, 并非用于限定本发明的保护范 围。
Claims
1、一种实现移动交换中心 MSC双归属的方法,其特征在于,将物理 MSC Server划分为一个以上虚拟 MSC Server, 建立不同虚拟 MSC Server与不同物 理 MSC Server之间的双归属关系, 并设置虚拟 MSC Server的状态为空闲,虚 拟 MSC Server通过心跳检测判断是否需要切换, 如果需要, 则将虚拟 MSC Server的状态设置为激活; 否则, 继续正常工作和检测。
2、 根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 设置 物理 MSC Server中的一个虚拟 MSC Server管理和控制自身所属物理 MSC Server的所有下属网络节点, 并设置该虚拟 MSC Server的状态为激活。
3、根据权利要求 2所述的方法, 其特征在于, 所述物理 MSC Server为所 有物理 MSC Server中的每个物理 MSC Server; 或者, 所述物理 MSC Server 为所有物理 MSC Server中具有需管理的网络节点的物理 MSC Server。
4、 根据权利要求 1、 2或 3所述的方法, 其特征在于, 所述判断是否需要 切换为:虚拟 MSC Server检测自身所属物理 MSC Server和与自身建立双归属 关系的物理 MSC Server之间的心跳连接, 判断心跳是否丢失或心跳连接中物 理 MSC Server的状态是否为故障, 如果是, 则需要切换; 否则不需要切换。
5、 根据权利要求 1、 2或 3所述的方法, 其特征在于, 所述判断是否需要 切换为: 虚拟 MSC Server判断是否收到切换命令或更新状态命令, 如果收到, 则需要切换; 否则不需要切换。
6、根据权利要求 1、2或 3所述的方法,其特征在于,所述虚拟 MSC Server 与物理 MSC Server之间的双归属关系为双归属备份关系、 或为双归属互助关 系。
7、 根据权利要求 6所述的方法, 其特征在于, 所述双归属备份关系或互 助关系为 1+1备份关系或互助关系、或为 N+1备份关系或互助关系、或为 N+M 备份关系或互助关系。
8、 根据权利要求 1、 2或 3所述的方法, 其特征在于, 需要切换时, 该方 法进一步包括: 虛拟 MSC Server建立自身到具有双归属关系的物理 MSC Server下属网络节点的信令链路。
9、 根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 用户 数据发生变化时, 物理 MSC Server将用户数据实时备份到具有双归属关系的 虚拟 MSC Server对应的 VLR中。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AT06742101T ATE476841T1 (de) | 2005-06-27 | 2006-06-05 | Verfahren zur realisierung einer zweifachen heimat einer mobilvermittlungsstelle |
DE602006015958T DE602006015958D1 (de) | 2005-06-27 | 2006-06-05 | Verfahren zur realisierung einer zweifachen heimat einer mobilvermittlungsstelle |
EP06742101A EP1895785B1 (en) | 2005-06-27 | 2006-06-05 | Method for realizing dual home of mobile switching center |
US11/962,787 US8452331B2 (en) | 2005-06-27 | 2007-12-21 | Method and system for implementing mobile switch center dual homing |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB2005100799937A CN1327728C (zh) | 2005-06-27 | 2005-06-27 | 一种实现移动交换中心双归属的方法 |
CN200510079993.7 | 2005-06-27 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/962,787 Continuation US8452331B2 (en) | 2005-06-27 | 2007-12-21 | Method and system for implementing mobile switch center dual homing |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007000094A1 true WO2007000094A1 (fr) | 2007-01-04 |
Family
ID=36923706
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2006/001215 WO2007000094A1 (fr) | 2005-06-27 | 2006-06-05 | Procede pour effectuer un raccordement a double anneau de central de commutation mobile |
Country Status (6)
Country | Link |
---|---|
US (1) | US8452331B2 (zh) |
EP (1) | EP1895785B1 (zh) |
CN (1) | CN1327728C (zh) |
AT (1) | ATE476841T1 (zh) |
DE (1) | DE602006015958D1 (zh) |
WO (1) | WO2007000094A1 (zh) |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1327728C (zh) | 2005-06-27 | 2007-07-18 | 华为技术有限公司 | 一种实现移动交换中心双归属的方法 |
CN101202655B (zh) * | 2006-12-12 | 2011-05-11 | 华为技术有限公司 | 用于互为备份软交换设备的心跳检测方法和装置 |
CN101227437B (zh) * | 2007-01-19 | 2012-04-04 | 华为技术有限公司 | 实现媒体网关资源共享的方法、系统及设备 |
CN101159757B (zh) * | 2007-10-25 | 2011-11-30 | 中兴通讯股份有限公司 | 双归属同步数据传输方法 |
CN101447886B (zh) * | 2007-11-26 | 2011-07-27 | 华为技术有限公司 | 一种比较海量数据的方法及装置 |
GB2461501B (en) * | 2008-06-27 | 2010-07-28 | Motorola Inc | Communication system and a method and call processor for use in the system |
CN101335702B (zh) * | 2008-07-07 | 2011-12-28 | 中兴通讯股份有限公司 | 一种gprs业务支持节点容灾的处理方法 |
CN101742644B (zh) * | 2008-11-07 | 2012-10-10 | 中兴通讯股份有限公司 | 通知方法、用户设备及无线网络控制器 |
CN101998512B (zh) * | 2009-08-20 | 2013-06-19 | 中国移动通信集团公司 | 移动交换中心池间的负载均衡方法、移动交换中心及系统 |
US8379636B2 (en) * | 2009-09-28 | 2013-02-19 | Sonus Networks, Inc. | Methods and apparatuses for establishing M3UA linksets and routes |
CN101772221B (zh) * | 2010-02-05 | 2014-12-31 | 中兴通讯股份有限公司 | 一种完成平滑割接的方法及割接操作执行设备及装置 |
US8634832B2 (en) * | 2010-08-09 | 2014-01-21 | Telefonaktiebolaget L M Ericsson (Publ) | Mobile location recovery for MSC pooling |
JP5221622B2 (ja) * | 2010-10-26 | 2013-06-26 | 株式会社エヌ・ティ・ティ・ドコモ | 無線ネットワーク制御装置、パケット交換機、回線交換機及び情報通知方法 |
JP5223952B2 (ja) * | 2011-08-12 | 2013-06-26 | 日本電気株式会社 | 移動体通信システム、移動局、交換局および移動局の位置登録方法 |
CN103188617B (zh) * | 2011-12-27 | 2016-11-23 | 华为技术有限公司 | 实现集群业务的方法、实体及系统 |
JP5537600B2 (ja) * | 2012-05-15 | 2014-07-02 | 株式会社Nttドコモ | 制御ノード及び通信制御方法 |
CN102970700A (zh) * | 2012-11-13 | 2013-03-13 | 中兴通讯股份有限公司 | 根据注册网关数量进行双归属自动倒换判决方法及系统 |
US9571340B2 (en) * | 2014-03-12 | 2017-02-14 | Genband Us Llc | Systems, methods, and computer program products for computer node resource management |
EP3018931B1 (en) | 2014-11-06 | 2019-04-17 | ADVA Optical Networking SE | Method and system for establishing a self-organized mobile core in a cellular communication network |
US10932164B2 (en) * | 2017-01-27 | 2021-02-23 | Parallel Wireless, Inc. | CDMA/EVDO virtualization |
CN108934036B (zh) * | 2018-07-11 | 2021-07-20 | 中国联合网络通信集团有限公司 | 基站状态信息的获取方法和装置 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6408182B1 (en) * | 1999-07-16 | 2002-06-18 | Ericsson, Inc. | Redundant mobile switching center (MSC) architecture for a radio telecommunications network |
CN1434574A (zh) * | 2002-01-24 | 2003-08-06 | 华为技术有限公司 | 一种移动交换中心的备份方法 |
CN1545345A (zh) * | 2003-11-12 | 2004-11-10 | 中兴通讯股份有限公司 | 移动软交换网络的容灾方法 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
BR9205331A (pt) * | 1991-06-28 | 1994-06-21 | Ericsson Telefon Ab L M | Processo de estruturaçao e sistema de software para controlar uma central de telecomunicaçoes controlada por programa amazenado |
US5761500A (en) * | 1996-04-18 | 1998-06-02 | Mci Communications Corp. | Multi-site data communications network database partitioned by network elements |
US6662308B1 (en) * | 1999-12-21 | 2003-12-09 | Lucent Technologies Inc. | Dual-homing select architecture |
US7562110B2 (en) * | 2001-01-11 | 2009-07-14 | F5 Networks, Inc. | File switch and switched file system |
US20030176163A1 (en) * | 2002-03-18 | 2003-09-18 | Samsung Electronics Co., Ltd. | System and method for on-line upgrade of call processing software using load sharing groups |
US7308491B2 (en) * | 2002-03-18 | 2007-12-11 | Samsung Electronics Co., Ltd. | System and method for on-line upgrade of call processing software using group services in a telecommunication system |
CN1536819B (zh) | 2003-04-11 | 2010-08-04 | 华为技术有限公司 | 下一代网络中双归属的实现方法 |
US7463610B2 (en) * | 2003-05-15 | 2008-12-09 | Samsung Electronics Co., Ltd. | System and method for providing an online software upgrade |
CN100488299C (zh) | 2003-06-19 | 2009-05-13 | 中兴通讯股份有限公司 | 一种虚拟移动交换中心的实现方法 |
US7379419B2 (en) * | 2003-08-13 | 2008-05-27 | Samsung Electronics Co., Ltd. | Apparatus and method for performing an online software upgrade of resource servers |
EP1673954B1 (en) * | 2003-10-14 | 2007-04-25 | Telefonaktiebolaget LM Ericsson (publ) | Automatic distribution of capability and configuration information between mobile switching centers in a mobile communications network |
CN1279789C (zh) | 2004-08-05 | 2006-10-11 | 华为技术有限公司 | 在一个物理移动交换中心覆盖的多子网间实现通信的方法 |
CN1327728C (zh) | 2005-06-27 | 2007-07-18 | 华为技术有限公司 | 一种实现移动交换中心双归属的方法 |
-
2005
- 2005-06-27 CN CNB2005100799937A patent/CN1327728C/zh active Active
-
2006
- 2006-06-05 EP EP06742101A patent/EP1895785B1/en not_active Not-in-force
- 2006-06-05 WO PCT/CN2006/001215 patent/WO2007000094A1/zh not_active Application Discontinuation
- 2006-06-05 AT AT06742101T patent/ATE476841T1/de not_active IP Right Cessation
- 2006-06-05 DE DE602006015958T patent/DE602006015958D1/de active Active
-
2007
- 2007-12-21 US US11/962,787 patent/US8452331B2/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6408182B1 (en) * | 1999-07-16 | 2002-06-18 | Ericsson, Inc. | Redundant mobile switching center (MSC) architecture for a radio telecommunications network |
CN1434574A (zh) * | 2002-01-24 | 2003-08-06 | 华为技术有限公司 | 一种移动交换中心的备份方法 |
CN1545345A (zh) * | 2003-11-12 | 2004-11-10 | 中兴通讯股份有限公司 | 移动软交换网络的容灾方法 |
Also Published As
Publication number | Publication date |
---|---|
ATE476841T1 (de) | 2010-08-15 |
DE602006015958D1 (de) | 2010-09-16 |
US8452331B2 (en) | 2013-05-28 |
CN1822685A (zh) | 2006-08-23 |
CN1327728C (zh) | 2007-07-18 |
EP1895785A4 (en) | 2009-01-14 |
EP1895785B1 (en) | 2010-08-04 |
EP1895785A1 (en) | 2008-03-05 |
US20080096547A1 (en) | 2008-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2007000094A1 (fr) | Procede pour effectuer un raccordement a double anneau de central de commutation mobile | |
TWI451775B (zh) | 網路節點冗餘 | |
US7577090B2 (en) | Method and system for providing availability and reliability for a telecommunication network entity | |
US8576700B2 (en) | Geographic redundancy for call servers in a cellular system based on a bearer-independent core network | |
JP2011211710A (ja) | ステートフルな(通信状態を維持する)地理的冗長性を有するモビリティ管理エンティティ(mme)の効率的な配備 | |
US20080161054A1 (en) | Node selection function for multipoint radio network configurations | |
WO2006024225A1 (fr) | Procede de realisation d'une double inscription | |
JP5161971B2 (ja) | 移動無線ネットワークにおいて回路交換コールを確立する方法及び移動無線ネットワーク | |
WO2012089025A1 (zh) | 基于基站控制设备群组的通信方法、装置及系统 | |
WO2011079721A1 (zh) | 一种通信方法和本地管理系统 | |
CN100388814C (zh) | 一种移动软交换服务器的容灾方法 | |
CN104244297B (zh) | 一种基于td-lte的宽带集群故障弱化通信方法和基站 | |
WO2011094992A1 (zh) | 一种完成平滑割接的方法、割接操作执行设备及装置 | |
CN101754488B (zh) | 一种逻辑控制类通信设备及通信方法 | |
CN100574486C (zh) | 通信网络中双归属组网的系统及其方法 | |
WO2006038592A1 (ja) | 通信路切り替えシステム及び方法 | |
CN101227437A (zh) | 实现媒体网关资源共享的方法、系统及设备 | |
WO2011110109A2 (zh) | 连接建立方法、故障处理方法、通信系统及相关设备 | |
WO2007006198A1 (fr) | Procédé de réalisation de guidage double dans un réseau avec contrôle et orientation séparés | |
WO2006136075A1 (fr) | Procédé pour implémenter une double appartenance dans la séparation entre le réseau de contrôle et le réseau de relèvement | |
WO2012097604A1 (zh) | 网关故障时的消息处理方法、系统和网关 | |
CN103124443A (zh) | 多个核心网与无线网络控制器之间的互联装置及方法 | |
CN102006187A (zh) | 一种软交换关口局的组网方法及网络 | |
EP2550793A1 (en) | A node with an improved back up protocol | |
CN102457875B (zh) | 业务倒换方法和系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 11962787 Country of ref document: US Ref document number: 2006742101 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 2006742101 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 11962787 Country of ref document: US |