CN101159921B - Method, system and equipment for called recovery in mobile switching center pool - Google Patents

Abstract

The invention discloses a method for recovering a called party in a mobile switching center pool, which is applied to the following steps: a home location register HLR and a plurality of mobile switching centers/visitor location registers MSC/VLR to form a mobile switching center POOL MSC POOL system, wherein a backup office of each MSC/VLR is arranged in the MSC POOL; if the service MSC/VLR of the user is down and the user does not initiate calling service or location update, when the user is taken as a called party, the method comprises the following steps: the HLR sends the call signaling to the backup office of the down MSC/VLR; the backup office initiates paging to the user and initiates location update of the user to HLR; the HLR registers the subscriber data of the subscriber in the backup office and updates the serving MSC/VLR of the subscriber to the backup office. The invention also discloses other methods, systems and switching equipment. The invention can solve the problem of called recovery in MSC POOL.

Description

Method, system and equipment for called recovery in mobile switching center pool

technical field

The present invention relates to mobile switching center pool (MSC POOL, Mobile Switch Center Pool) realization technology, relate in particular to the method for recovering called in MSC POOL, the system for recovering called in MSC POOL, switching equipment and signaling switching equipment.

Background technique

At present, the 3GPP organization has proposed a networking mode completely different from the traditional networking mode. In this networking mode, a base station controller (RNC/BSC, Radio Network Controller/Base Station Controller) can be connected to multiple servers (SERVER ), these SERVERs can form MSCPOOL. The advantages of this networking mode of MSC POOL are as follows: (1) within the MSC POOL, load sharing can be realized between each server; (2) the port between the server and the home location register (HLR, Home Location Register) can be reduced Signal volume; (3) Within the MSC POOL, reduce the amount of interface messages between SERVERs, thereby reducing the call drop rate; (4) During capacity expansion, the core network and access network can be planned separately.

In terms of disaster recovery, MSC POOL has an inherent caller disaster recovery function. After a user’s service server is down, when the user initiates a call service, there will be a new server in MSC POOL to serve the user; In terms of calling, the user cannot resume being called during a period of periodic location updating. When the user initiates location updating after waiting for a period of periodic location updating, there will be a new SERVER in the MSC POOL to serve the user. The specific meaning is: if a server in the MSC POOL goes down, the calling service of the user registered in the downtime server will not be affected, and if the user does not initiate a calling service within a periodic location update time, If it is a calling service, it cannot be used as the called party all the time.

FIG. 1 is a flow chart of called party signaling when a certain server is down in the prior art. MSC/Visitor Location Register A (VLR, Visitor Location Register) and MSC/VLR B are two servers in the MSC POOL, and a server in the MSC POOL is down (MSC/VLR A in the figure is down) Under the circumstances, the link from the HLR to the SERVER is broken. When the HLR receives the Send Routing Information (SRI, Send Routing Information) message from the Gateway Mobile Switching Center (GMSC, Gateway Switch Center), because the user is registered in the downtime MSC/VLRA, the HLR cannot send the Routing Number (PRN) message. ,, Provide Roaming Number) message to MSC/VLRA to obtain the user's roaming number therefrom, thus causing the called party to fail to be called, and the called party cannot be connected within a periodical location update time.

If the user initiates the calling service or initiates the location update during the periodic location update period, the user is registered in other SERVERs in the MSC POOL, and then the called party can be successfully called. However, if the user does not act as the calling party or update the location during the periodical location update, the user cannot be successfully called as the called party.

It can be seen that the called disaster recovery function of the existing MSC POOL is not complete enough. When the SERVER goes down, the user information cannot be recovered in time, so that the user cannot be successfully called as the called party.

Contents of the invention

The main purpose of the present invention is to provide a method, system and switching equipment for called recovery in a mobile switching center pool (MSC POOL), which can recover called after a certain MSC/VLR in the MSC POOL goes down.

Another main purpose of the present invention is to provide a method, system and switching equipment for calling party recovery in MSC POOL, which can recover the called party when a certain MSC/VLR in MSC POOL is down and recovers within a periodical location update period. .

The purpose of the present invention is also to provide signaling switching equipment, which can send signaling to the currently reachable relevant MSC/VLR when the MSC/VLR in the MSC POOL is down or recovers after the downtime, so as to assist in realizing the called recovery.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

The invention discloses a method for called recovery in a mobile switching center pool, which is applied to a system comprising a mobile switching center pool MSC POOL composed of a home location register HLR and a plurality of mobile switching centers/visitor location registers MSC/VLR. The backup office of each MSC/VLR is set in the MSC POOL; if the service MSC/VLR of the user is down and the user has not initiated calling service or location update, when the user is called, the method includes:

HLR sends call signaling to the backup office of the downtime MSC/VLR;

The backup office initiates paging to the user and initiates location update of the user to the HLR;

The HLR registers the user data of the user in the backup office and updates the user's serving MSC/VLR to the backup office.

In the above solution, the backup office initiates the user's location update to the HLR, and the HLR registers the user's user data in the backup office and updates the user's serving MSC/VLR to the backup office, including:

After receiving the user's paging response, the backup office sends a location update request to the HLR;

The HLR sends a cancel user location message to the backup office;

The backup office deletes the user data backed up by the downtime MSC/VLR in the office and returns the confirmation of canceling the user location to the HLR;

The HLR inserts the user's user data into the backup office, and records the user's serving MSC/VLR as the backup office.

In the above scheme, the HLR sends the call signaling and cancels the user location message to the backup office of the downtime MSC/VLR through the signaling transfer node STP; the STP is pre-configured: the direct route to the MSC/VLR has priority The priority is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; or, the signaling point of the backup office of the MSC/VLR is the SCCP load sharing signal of the signaling point of the MSC/VLR and the priority of the signaling point of the backup office of the MSC/VLR is lower than the signaling point of the MSC/VLR; the HLR sends call signaling to the backup office of the downtime MSC/VLR through STP , including: the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is down, the call signaling is sent to the backup office of the downtime MSC/VLR through a low-priority detour route; Or, the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is down, the call signaling is sent to the signaling point of the backup office of the downtime MSC/VLR of low priority; Said HLR sends the message of canceling the user location to the backup office through the STP, including: the HLR sends the message of canceling the user location to the STP; Cancel the subscriber location message and send it to the backup office of the downtime MSC/VLR; or, the HLR sends the cancellation subscriber location message to the STP, and when the STP determines that the MSC/VLR is downtime, it sends the cancellation subscriber location message The signaling point of the backup office of the downtime MSC/VLR with the lowest priority.

In the above scheme, if the service MSC/VLR of the user recovers within a periodic location update period after being down, and the user has never initiated a calling service or location update, the When the user is called, it further includes:

Said HLR sends the call signaling to the MSC/VLR recovered after the downtime;

The recovered MSC/VLR extracts the user's backup user data from its backup office;

The recovered MSC/VLR updates the location area information of the user after the downtime, extracts the user data of the user from the HLR and restores the user data, assigns the roaming number of the local office to the user and returns the assigned roaming number of the local office to the user HLR.

The invention also discloses a method for recovering the called party in the mobile switching center pool, which is applied to the system comprising: MSC POOL composed of HLR and multiple MSC/VLRs, and the backup of each MSC/VLR is set in the MSC POOL If the service MSC/VLR of the user recovers within a periodic location update period after downtime, and the user has not initiated the calling service or location update, the user as the called party during the period , the method includes:

Said HLR sends the call signaling to the MSC/VLR recovered after the downtime;

The recovered MSC/VLR extracts the user's backup user data from its backup office, updates the user's location area information, and extracts the user's user data from the HLR and restores the user data to provide the user Allocate the local office roaming number and return the allocated local office roaming number to the HLR.

In the above solution, the STP is pre-configured: the priority of the direct route to the MSC/VLR is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; or, the backup of the MSC/VLR The signaling point of the office is the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the priority of the signaling point of the backup office of the MSC/VLR is lower than the signaling point of the MSC/VLR; The HLR sends the call signaling to the recovered MSC/VLR through the STP, including: the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is valid, the high-priority direct The route sends the call signaling to the MSC/VLR that has recovered after the downtime; or, the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is valid, the call signaling is sent to the high-priority The signaling point of the MSC/VLR that recovers after the downtime.

The invention discloses a system for recovering a called party in a mobile switching center pool, comprising: an MSC POOL formed by an HLR and a plurality of MSC/VLRs, the MSC POOL further includes a backup office of each MSC/VLR; the HLR Used to send call signaling to the backup office of the downtime MSC/VLR when the user's service MSC/VLR is down and the user has not initiated a calling service or location update and the user is called. When the backup office initiates a location update, insert the user's user data into the backup office and update the user's service MSC/VLR to the backup office; the backup office is used to back up the user data of the MSC/VLR, and upon receiving When the call signaling from the HLR initiates paging to the user and initiates location update of the user to the HLR, registers the user data of the user inserted by the HLR.

The above system further includes: a user terminal and its RAN; after the backup office registers the user data of the user, it is further configured to assign a TMSI containing null-NRI to the user, and send the TMSI through the RAN and the TMSI reallocation command of the non-broadcast LAI to the user terminal of the user; the user terminal is used to initiate a location update request carrying a null-NRI to the RAN to which it belongs after receiving the non-broadcast LAI; The null-NRI assigns the new MSC/VLR in the MSC POOL as the serving MSC/VLR for the user.

In the above system, the HLR is further used to recover within a periodical location update period after the service MSC/VLR of the user goes down, and the user has not initiated a calling service during this periodical location update period. or location update and the user is called, send the call signaling to the MSC/VLR recovered after the downtime, output the user data of the user to the MSC/VLR recovered after the downtime, and from the downtime The MSC/VLR recovered after the shutdown receives the user's roaming number; the MSC/VLR is further used for, when recovering in a periodical location update period after the shutdown, from its backup after receiving the call signaling The central office extracts the user's backup user data to update the user's location area information, and extracts the user's user data from the HLR and recovers the user data, assigns the local office roaming number to the user and returns it to the HLR.

The present invention also discloses a system for called recovery in a mobile switching center pool, comprising: an MSC POOL formed by an HLR and a plurality of MSC/VLRs, the MSC POOL further includes a backup office of each MSC/VLR; HLR is used for, after the service MSC/VLR of described user goes down and recovers again in a periodical location update period, this user has not initiated calling business or location update and this user acts as When being called, send the call signaling to the recovered MSC/VLR after the downtime, output the user data of the user to the recovered MSC/VLR after the downtime, and from the recovered MSC/VLR The VLR receives the user's roaming number; the MSC/VLR is used to extract the user's backup user from its backup office after receiving the call signaling when the MSC/VLR recovers within a periodical location update period after a downtime Data updates the location area information of the user, and extracts the user data of the user from the HLR and restores the user data, assigns the roaming number of the local office to the user and returns it to the HLR.

The above two systems may further include: STP, used for sending call signaling from HLR to this MSC/VLR when MSC/VLR is valid; when MSC/VLR fails, sending call signaling from HLR to this MSC/VLR Backup office of MSC/VLR.

The invention also discloses a switching device, which is used to control voice or data exchange, process call signaling interaction, and realize interconnection and intercommunication between access network devices; located in MSCPOOL composed of multiple MSCs/VLRs, the switching device As the backup office of at least one MSC/VLR in the MSC POOL, and the at least one MSC/VLR is used as the main office of the switching equipment, the switching equipment includes: a first module for storing the backup user data of the main office; The second module, when the called user of the call signaling is not the local office user and the call signaling is not the calling local office, extract the backup user data of the called user from the first module, page the called user, and initiate The location of the called user is updated, and then the backup user data of the called user is deleted from the first module, and the switching device where the user is located is updated as the service switching device of the called user.

In the above switching device, the second module includes: a control module, when the called user of the call signaling is not the local office user and the call signaling is not calling the local office, extract the backup of the called user from the first module User data and trigger the paging module; trigger the location update module when the user of the paging response is not registered in this office; delete the backup user data of the called user from the first module after the HLR confirms that the location of the called user is canceled; Extract the user data of the called user from the HLR and insert it into the registration unit; the location update module, after being triggered by the control module, initiates the location update of the called user to the HLR; the paging module, after being triggered by the control module After the module triggers, initiate paging to the called user according to the backup user data of the called user extracted by the control module, and receive a paging response; The user data registers the called user in the local office.

The above equipment may further include: a TMSI reallocation module; the control module further triggers the TMSI reallocation module after the registration unit registers the called user; the TMSI reallocation module, after being triggered by the control module, allocates The TMSI containing the null-NRI is given to the called user, and the TMSI reallocation command carrying the TMSI and non-broadcast LAI is sent to the RAN through the control module.

The above equipment may further include: a roaming number allocation module; the control module is further configured to extract the called user from the backup office of the switching device when the called user of the call signaling is not a user of the local office and the call signaling calls the local office. call the backup user data of the user, update the location area information of the called user, extract the user data of the called user from the HLR and restore it to the registration unit, and trigger the roaming number allocation module; the roaming number allocation module, After being triggered by the control module, a roaming number is assigned to the called user and provided to the HLR.

The invention also discloses a switching device, which is used to control voice or data exchange, process call signaling interaction, and realize interconnection and intercommunication between access networks. In the MSC POOL, and the MSC POOL also includes the backup office of the switching equipment, the switching equipment includes: a third module, used for when the called user of the call signaling is not the local office user and the call signaling calls the local office , extracting the backup user data of the called user from the backup office of the switching device, updating the location area information of the called user, recovering the user data of the called user, and providing the roaming number of the called user.

In the above equipment, the third module includes: a control module, when the called user of the call signaling is not the local office user and the call signaling calls the local office, extract the backup user of the called user from the backup office of the switching device Data, update the location area information of the called user, extract the user data of the called user from the HLR and output to the registration unit, and trigger the roaming number distribution module; the roaming number distribution module, after being triggered by the control module, is The called user assigns a roaming number and provides it to the HLR; the registration unit is used to recover the user data of the called user according to the user data from the control module.

The invention discloses a signaling forwarding device, which includes: a priority configuration unit, configured to configure the priority of the direct route to the switching device to be higher than the priority of the detour route to the switching device through the backup office of the switching device The signaling forwarding unit is used to receive call signaling from the HLR, determine the service switching equipment of the called user, inquire about the priority configuration unit, and when the service switching equipment is valid, send the call signaling through a high-priority direct route to the service switching device; when the service switching device fails, send the call signaling to the backup office of the service switching device through a low-priority detour route.

The present invention also discloses another signaling forwarding device, which includes: a priority configuration unit, configured to configure the signaling point of the backup office of the switching device as the SCCP load sharing signaling point of the signaling point of the switching device, And the priority of the signaling point of the backup office of the switching equipment is lower than the signaling point of the switching equipment; the signaling forwarding unit is used to receive call signaling from the HLR, determine the service switching equipment of the called user, and query the described The priority configuration unit, when the service switching device is valid, sends the call signaling to the signaling point of the high priority service switching device; when the service switching device fails, sends the call signaling to the service switching point of the low priority The signaling point of the backup office of the device.

To sum up, the present invention can completely solve the callee recovery problem caused by the downtime of MSC/VLR in MSC POOL, further improves the disaster recovery capability of MSC POOL, improves the robustness of the network, and improves the network operator's network efficiency. Service capabilities.

Description of drawings

FIG. 1 is a flow chart of called party signaling when a certain server is down in the prior art.

2A and 2B are respectively schematic diagrams of routing priority and signaling connection control part (SCCP) destination signaling point master-backup sharing in the present invention.

FIG. 3 is a schematic diagram of a network using chained VLR backup in the present invention.

Fig. 4 is a schematic diagram of a network using centralized VLR backup in the present invention.

Fig. 5 is a flow chart of the called signaling for the first time when the SERVER is down in the method of the present invention.

Fig. 6 is the signaling flowchart of recovering called user data after the SERVER crashes in the method of the present invention.

Fig. 7 is a structural diagram of the internal composition of the MSC/VLR as the backup office in the present invention.

FIG. 8 is a structural diagram of the internal composition of the MSC/VLR recovered after a downtime in the present invention.

Detailed ways

The method for called recovery in the MSC POOL provided by the present invention mainly includes: firstly, the SRI message sent by the HLR can be sent to a SERVER without downtime in the MSC POOL, and then the called party is paged on this SERVER, And after the paging response, update the user's implicit location, and then update the user's service MSC number to the HLR, so that when the user is called again, the call can be successfully established

Considering that the wireless area served by MSC POOL is very large, and each wireless area has multiple SERVER services, it is not possible to issue network-wide paging in MSC POOL. In order to solve this problem, the technology of VLR data backup (VDB, VLR Data Backup) backup needs to be used. That is, the user data is backed up at the site where the paging is issued, including: International Mobile Subscriber Identity (IMSI, International Mobile Subscriber Identity) and Location Area Identity (LAI, Location AreaIdentity) and other information.

The method mainly includes three parts: 1. Configuring routing priority or SCCP destination signaling point load sharing; 2. VLR data backup; 3. The process of obtaining called user data through signaling interaction between backup VLRs. The processing of these three parts will be described in detail below one by one.

1. Routing priority and SCCP destination signaling point active/standby sharing

In this method, one of the two can be configured. By configuring routing priority or SCCP destination signaling point load sharing, the SERVER where the called user data is registered can send the called first message to other There is no downtime on the SERVER.

1. Routing priority

As shown in Figure 2A, when MSC/VLRB is the backup office of MSC/VLRA, two routes should be configured on the signaling transfer node (STP, Signaling Transfer Point): 1. STP to signaling point AA of MSC/VLRA 2. The detour route for STP to reach the signaling point AA through the signaling point BB of the MSC/VLRB. Wherein, the direct route is configured as a high-priority route, and the detour route is configured as a low-priority route. At the same time, the addressing mode of STP and MSC POOL is required to be Destination Signaling Point Code (DPC, Destination Signaling Point Code) + subsystem number (SSN), and signaling point BB needs to be configured as signaling point AA in MSC/VLRB Mutual aid signaling points. In this way, when the MSC/VLRA is normal, the signaling sent by the HLR to the signaling point AA through the STP will be sent to the MSC/VLRA by the high-priority direct route, and when the MSC/VLRA fails, the STP will go to the signaling point The signaling of AA will be sent to MSC/VLRB by a low-priority detour route. Since the signaling point BB in MSC/VLRB is the mutual assistance signaling point of signaling point AA, at this time STP sends the signaling point AA The order will be processed at MSC/VLRB.

2. Active/standby sharing of SCCP destination signaling points

As shown in Figure 2B, when MSC/VLR B is the backup office of MSC/VLRA, the data on the STP is planned as follows: the addressing data of configuration global name 1 (GT, Global Title) is AA+SSN, and at the same time Configure signaling point BB as the SCCP load sharing signaling point of signaling point AA, and its priority is lower than that of signaling point AA. In this way, when MSC/VLRA is normal, the signaling sent by HLR to GT1 through STP will be sent to high-priority signaling point AA (ie: MSC/VLRA), when MSC/VLRA fails, STP will send to GT1 The signaling will be sent to the low-priority load sharing signaling point BB (namely: MSC/VLRB). At this time, the signaling sent by the STP to GT1 will be processed at the MSC/VLRB. It should be noted that this solution requires STP to support the SCCP load sharing function.

2. VLR backup

In this method, one of the two methods of chain backup and centralized backup can be used. Because the physical area covered by MSC POOL is large, and the same RNC/BSC is served by all servers in MSC POOL, it is generally not allowed to send network-wide paging in MSC POOL. In order to solve the problem of not being able to page, it is necessary to back up the user data (such as IMSI/LAI) of a server in the MSC POOL. The following briefly describes the networking in the above two backup modes.

FIG. 3 is a schematic diagram of a network using chained VLR backup in the present invention. As shown in Figure 3, the networking structure includes: HLR, STP1, gateway MSC (GMSC, Gateway MSC), MSC POOL and RAN. HLR can send call signaling to its connected GMSC and MSC/VLR in MSC POOL through STP1; GMSC can send call signaling from STP1 to external network or send call signaling from external network to MSC POOL Each MSC/VLR in the MSC POOL; each MSC/VLR in the MSC POOL can initiate paging to the called terminal through the RAN or exchange messages with the called terminal after receiving the call signaling. In the MSC POOL, each MSC/VLR forms a chain backup, wherein MSC/VLR B backs up MSC/VLRA, MSC/VLRC backs up MSC/VLRB, and MSC/VLRA backs up MSC/VLRC.

Fig. 4 is a schematic diagram of a network using centralized VLR backup in the present invention. Fig. 4 is similar to the networking structure shown in Fig. 3, which includes: HLR, STP1, GMSC, MSC POOL and RAN. HLR can send call signaling to its connected GMSC and MSC/VLR in MSC POOL through STP1; GMSC can send call signaling from STP1 to external network or send call signaling from external network to MSC Each MSC/VLR in the POOL; each MSC/VLR in the MSC POOL can initiate paging to the called terminal through the RAN or exchange messages with the called terminal after receiving the call signaling. The difference between the network structure shown in Figure 4 and the network structure shown in Figure 3 is that the MSC POOL further includes an MSC/VLR backup center, and each MSC/VLR can centrally back up their own data in the MSC/VLR backup center . As shown in Figure 4, MSC/VLRA, MSC/VLRB and MSC/VLRC are centrally connected to this MSC/VLR backup center, and their backup MSC/VLRs are all MSC/VLR backup centers; this MSC/VLR backup center also has a simple The MSC function can also initiate paging to the called terminal or exchange messages with the called terminal through the RAN.

VLR backup is to back up the user data of the main office to the backup office, including:

Step 1: Establish a backup link between the active office and the backup office.

For the chain backup shown in Figure 3, when MSC/VLRA is the master office, MSC/VLRB is the backup office of MSC/VLRA; when MSC/VLRB is the master office, MSC/VLRC is the backup office of MSC/VLRB; When MSC/VLRC is the main office, MSC/VLRA is the standby office of MSC/VLRC. For the centralized backup shown in Figure 4, MSC/VLRA, MSC/VLRB, and MSC/VLRC are the active offices, and the MSC/VLR backup center is the backup office for MSC/VLRA, MSC/VLRB, and MSC/VLRC.

Step 2, back up the user data of the main office to the backup office through the backup link.

The user data of the main office is backed up to the backup office through the backup link, that is, a backup interface is set between the main office and the backup office, and the backup interface is used to realize user data between the main office and the backup office. backup. Here, the third-level user adaptation layer (M3UA, MTP Level 3 User Adaptation Layer) link of the message transmission part is used as the backup link for illustration. Correspondingly, the backup protocol stack can use M3UA/Stream Control Transmission Protocol (SCTP, Stream Control Transmission Protocol)/Internet Protocol (IP, Internet Protocol/Media Access Control (MAC, Media Access Control), so that the user data that needs to be backed up can be carried between the main office and the backup office through the M3UA link.

M3UA can provide telecommunication-level reliable bearer services. You can use a single signaling point or a shared signaling point to establish an M3UA link. Considering the limited signaling point resources, you can use the extended service indicator (SI, Service Indicator) and use the shared Signaling point mode. Moreover, in order to avoid the impact of traffic during backup on intermediate devices such as STP, a direct M3UA link can be used between the primary office and the backup office without transit by other devices.

Before performing step 2, you need to trigger the backup between the active office and the backup office.

The timing of triggering the backup can be determined according to the actual situation, including automatic triggering and system maintenance triggering. The trigger timing of the automatic trigger is: user initialization (such as the user enters the main office for the first time), the location of the user in the main office changes, the user data in the main office is deleted, and when the user in the main office turns on and off, etc.

The backup from the main office to the backup office will be described below in two cases. First, the backup in the case of automatic triggering will be described.

In the case of automatic triggering, the specific implementation of step 2 can be as follows: the active office sends a backup data message (BKP_req) carrying user data to the standby office, and after receiving the backup data message, the standby office returns a backup data response (BKP_rsp) to the active office . The user data includes IMSI, LAI, user on/off status and so on.

Step 3 may also be included after step 2: the master office notifies the backup office to delete user data. The specific implementation of step 3 may be: the master office sends a delete user request (BKP_DELSUB_req) to the backup office as needed, and the delete user request carries the IMSI of the user to be deleted; after receiving the delete user request, the backup office deletes the The user data corresponding to the above IMSI returns a delete user response (BKP_DELSUB_rsp) to the master office.

Step 4 may also be included after step 2: when the backup office needs to back up user data again, send a notification carrying the user's IMSI to the active office, and re-backup the user data corresponding to the IMSI from the active office. The specific implementation of step 4 can be: when the backup office needs to back up the data of a single user again, it sends a single user notification (REBKP_SINGLE_notify) to the main office to notify the main office to send the user data to the backup office. The IMSI of the user who needs to be reset is carried in the single user notification.

The above steps 1 to 4 are descriptions of user data backup between the primary office and the standby office, involving various backup messages as shown in Table 1, and Table 1 also sets corresponding Message type code. Of course, the backup of user data between the main office and the backup office is not limited to the above description, and can be in many different situations according to actual needs.

message type message type code Backup data message (BKP_req) 101 Backup Data Response (BKP_rsp) 102 Delete user message (BKP_DELSUB_req) 103 Delete User Response (BKP_DELSUB_rsp) 104 Reset Single User Notify (REBKP_SINGLE_notify) 105

Table 1 Backup messages and corresponding message type codes

Various types of backup messages in Table 1 are described below. Table 2 to Table 11 respectively show the parameters (Parameter) and the corresponding types of parameters (Type (FVO) contained in various messages, F indicates that the length of the parameter is fixed, V indicates that the length of the parameter is variable, and O indicates the length of the parameter. Length is optional)), and the parameter length (Length(octets)).

The meanings of some parameters involved in the table are: Send Process ID indicates the identification of the sending module that sends this type of message; Receive Process ID indicates the identification of the receiving module that receives this type of message; Message Type Code indicates the message type code of this type of message; Message Length indicates the length of this type of message; Data indicates the data carried in this type of message; Message Serial Number indicates the serial number for sending the data. The module used for sending data in the sending module is called a sending processing module, and the module used for receiving data in the receiving module is called a receiving processing module. In all tables about data, Send Reference ID indicates the reference number of the sending processing module that sends the data, and Receive Process ID indicates the reference number of the receiving processing module that receives the data.

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 1 8

Table 2 backup data message

Parameter Length(octets) IMSI 8 Send Reference ID 3 Message Serial Number 1 Attach/Dettach Flag 1 LAI 5

Table 3 shows the parameters of Data in Table 2 and the length of the corresponding parameters

The IMSI in Table 3 represents the user identity, the Attach/Dettach Flag represents the on/off status of the user corresponding to the IMSI, and the LAI represents the location update message of the user corresponding to the IMSI.

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 6

Table 4 Backup Data Response

Parameter Length(octets) Return Code 1 Send Reference ID 4 Message Serial Number 1

Table 5 is the Data in Table 4

Return Code in Table 5 indicates the return code of data.

Parameter Type(FVO) Length(octets) Send Process ID f 1

Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 13

Table 6 Delete User Notification

Parameter Length(octets) IMSI 8 Reserved 1 Send Reference ID 3 Message Serial Number 1

Table 7 is the Data in Table 6

The IMSI in Table 7 represents the user identifier, and Reserved represents deleting the user data corresponding to the IMSI. The delete user response is the same as the backup data response, and the table will not be shown here.

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 10

Table 8 is the notification for resetting a single user

Parameter Length(octets) IMSI 8 Reserved 1 Priority 1

Table 9 is the Data in Table 8

Wherein, IMSI represents a user identifier, and Reserved and Priority represent re-backup of user data corresponding to the IMSI.

The following describes the case where backup is triggered by system maintenance. When triggered by system maintenance, a single user data can be backed up, and multiple specified users can also be backed up. Here, steps 1 to 4 are specifically described by taking the case of backing up all users in the primary office as an example.

If the backup office is triggered by system maintenance, the specific implementation of step 2 can be as follows: the backup office sends a backup request for all user data (CTRL_REBKP_req) to the active office, and after receiving the user data request, the active office sends all user data through Backup data messages are sent to the backup office one by one. For the backup data message, see the description about the automatic trigger. After receiving the user data request, the master office can send a backup all user data response (CTRL_REBKP_rsp) to the backup office.

If the active office is triggered by system maintenance, the specific implementation of step 2 may be: the active office sends all user data to the backup office one by one through backup data messages. For the backup data message, see the description about the automatic trigger.

The specific implementation of the step 3 can be: the primary office sends a delete all backup data request (CTRL_DELALL_req) to the backup office as needed, and after receiving the request, the backup office deletes all user data backed up, and returns to the primary office to delete all user data. Backup data response (CTRL_DELALL_rsp).

The specific implementation of step 4 may be: when the backup office needs to back up all user data again, it sends a notification to the main office to back up all user data, so as to notify the main office to send all user data to the backup office.

Step 5 may also be included after step 1: the master office controls the user data of the backup office. Step 5 can be realized by sending backup control parameter change notification (CTRL_MODIFY_notify) to the backup office.

Step 6 may also be included after step 1: the backup office notifies the main office to stop backing up user data. The specific implementation of step 6 can be: when the backup office needs to stop the backup of user data, if the storage space of the backup office is not enough, it can send a stop backup notification (CTRL_STOPBKP_notify) to the main office to stop the main office from sending users to the backup office data backup.

Table 10 shows various types of backup messages involved in the above-mentioned backup of system maintenance triggering conditions, and table 10 also sets corresponding message type codes for various types of messages. Of course, the backup of user data when system maintenance is triggered is not limited to the above description, and may be in many different situations according to actual needs.

message type message type code Backup all user data request (CTRL_REBKP_req) 1 Backup all user data response (CTRL_REBKP_rsp) 2 Delete all backup data requests (CTRL_DELALL_req) 3

Delete all backup data responses (CTRL_DELALL_rsp) 4 Backup control parameter change notification (CTRL_MODIFY_notify) 5 Stop Backup Notify (CTRL_StopBKP_notify) 6

Table 10 shows the message types and response codes involved in backing up user data when system maintenance is triggered

Various types of backup messages in Table 10 are described below. Tables 11 to 20 respectively show the parameters (Parameter) contained in various types of messages, the types corresponding to the parameters (Type (FVO)), and the parameter lengths (Length (octets)). The meanings of the parameters involved in the table are the same as those in Table 1. I won't go into details here.

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 2

Table 11 Backup all user data requests

Parameter Length(octets) Send Reference ID 1 Receive Reference ID 1

Table 12 is the Data in Table 11

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 3

Table 13 Backup All User Data Response

Parameter Length(octets) Send Reference ID 1 Receive Reference ID 1 Return code 1

Table 14 is the Data in Table 13

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 3

Table 15 delete all backup data requests

Parameter Length(octets) Send Reference ID 1 Receive Reference ID 1 Reserved 1

Table 16 is the Data in Table 15

The response to delete all backup data is the same as the response to back up all user data, and the table will not be shown separately here.

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 3

Table 17 Backup control parameter change notification

Parameter Length(octets) Send Reference ID 1 Receive Reference ID 1 Control Parameter 1

Table 18 is the Data in Table 17

Control Parameter in Table 18 represents the control parameter.

Parameter Type(FVO) Length(octets) Send Process ID f 1 Receive Process ID f 1 Message Type Code f 1 Message Length f 1 Data o 3

Table 19 Stop Backup Notification

Parameter Length(octets) Send Reference ID 1 Receive Reference ID 1 Stop Type 1

Table 20 is the Data in Table 19

Stop Type in Table 20 indicates the stop parameter.

Optionally, in order to improve the reliability and security of the backup, after step 2, it also includes: the backup office determines that the backup data message carrying the user data from the main office has not been received within the set time period, so as to perform backup of the user data If the backup is performed again, the user data corresponding to the IMSI carried in the backup data message is deleted.

Optionally, in order to improve the reliability and security of the backup, after step 2, the method further includes: the backup office regularly sends a backup command to the active office, so as to re-backup the user data of a certain user from the active office. In this way, the backed up user data can be kept as the latest user data, thereby improving the reliability and security of the backed up data.

In the embodiment of the present invention, the MSC POOL contains three MSC/VLRs (MSC/VLRA, MSC/VLRB and MSC/VLRC), but the present invention does not limit the number of MSC/VLRs contained in the MSC POOL. In addition, only one STP (STP1) and one MSC/VLR backup center are shown in this networking structure. In an actual network, there may be multiple STP and MSC/VLR backup centers, which are not listed one by one in the figure. Shows.

Based on the networking structure shown in Figure 3 or Figure 4 above, paging can be issued to users served under the downtime MSC/VLR; after the user responds to paging, an implicit location update is made to the user, and the user's location in the HLR The MSC number is updated, so that the user can get through the phone when he is called for the second time, that is, the called recovery is realized. The specific implementation of the called recovery based on the above networking structure is detailed in the following process.

3. The backup VLRs acquire the called user data through signaling interaction. This process will be described in detail below with reference to FIG. 5 and FIG. 6 .

Fig. 5 is a flow chart of the called signaling for the first time when the SERVER is down in the method of the present invention. Fig. 5 shows three SERVERs in MSC POOL: MSC/VLRA, MSC/VLRB and MSC/VLRC, form chain backup among these three SERVERs, wherein, the data backup of MSC/VLRA is in MSC/VLRB, The data of MSC/VLRB is backed up in MSC/VLRC, while the data of MSC/VLRC is backed up in MSC/VLRA. In addition, according to the above routing priority configuration method, the priority of the direct route to a certain MSC/VLR signaling point is higher than the detour route to the MSC/VLR signaling point through the MSC/VLR backup office signaling point. Routing, such as: the priority of the direct route to the signaling point AA of MSC/VLRA is higher than the detour route to the signaling point AA through the signaling point BB of MSC/VLRB, and when the MSC/VLRA is down, it will use The detour route to the signaling point AA via the signaling point BB of the MSC/VLRB.

When the MSC/VLRA is down, the signaling process when the user registered in the MSC/VLRA is called for the first time includes:

Step 1: HLR sends PRN message to MSC/VLRA through STP to get the user's roaming number.

Step 2: Due to the failure of MSC/VLRA, according to the setting of the aforementioned route priority, when the high-priority route is invalid, the low-priority route is selected. Therefore, the STP sends the PRN message to the MSC/VLRB, where the addressing mode is DPC+SSN.

Step 3: After MSC/VLRB receives the PRN message, it is determined that the message can be landed at the SCCP layer. In the mobile application part (MAP, Mobile Application Part) layer, the MSC number of the called office needs to be ignored, so that the MAP layer of MSCB processes the PRN message. PRN message. Wherein, when the MSC number of the user in the PRN message needs to be refreshed in the VLR, it is necessary to judge whether the MSC number is the MSC number of the local office, if not the MSC of the local office, then the MSC number of the user in the VLR is not refreshed.

When MSC/VLRB receives the PRN message, if the user is not registered in the local office and the MSC number in the PRN message is not the MSC number of the local office, then go to the backup office of MSC/VLRB (that is, the backup VLR of MSC/VLRB) to extract user data ; If the user data is in the backup VLR, then perform step 4; if the user data is not in the backup VLR, then perform step 7.

Step 4: If the called user is in the shutdown state, the MSC/VLRB sends back a PRN ACK message to the HLR, and indicates the absent user in the PRN ACK message, and executes step 8; otherwise, executes step 5.

Steps 5-6: MSC/VLRB sends a paging (PAGING) message to the radio access network (RAN, Radio Access Network). The PAGING message carries the user IMSI and the LAI in the backup user data to page the called user. Here, the MAC/VLRB will start the timer, and at the same time use the LAI in the backup user data to page the called party. In order to save network resources and reduce the impact on the network, and considering that the success rate of one paging is high enough, this embodiment Only perform one paging and prohibit multiple paging, and send back a PRN ACK message to the HLR after the timer expires. The PRN ACK message indicates that the user is unreachable, and step 8 is performed. Here, in order to prevent the user from dialing the called party again before the paging response or during the paging process, the PRN ACK message must be sent later, so the timer can be added, and its duration can be configured, and the PRN ACK message can be sent after the timer expires. PRN ACK message.

Step 7: MSC/VLRB starts a timer, and returns a PRN ACK message indicating that the user is unreachable to the HLR after the timer expires, and ends the signaling process.

Steps 8-9: RAN returns a paging response (PAGING RSP) message to the originating office MSC/VLRB of this paging. If the corresponding user is not registered in the MSC/VLRB (that is, the user is not registered in the local office) and the user identifier in the paging response message is IMSI, an implicit location update is performed and a location update request is sent to the HLR.

Steps 10-11: HLR sends the cancel user location message to MSC/VLRA, because MSC/VLRA fails, so, according to the routing priority setting, STP sends the cancel user location message to the backup office of MSC/VLRA—MSC/ VLRB.

Steps 12-13: MSC/VLRB does not delete the user data (mainly IMSI) of the active VLR but needs to delete the user data in the backup VLR when receiving the cancel user location message during the location update process. That is to say: only need to clear the MSC/VLRB primary office (MSC/VLRA) backed up user data in the local office (MSC/VLRB), without clearing the local office (MSC/VLRB) backup data in its backup office (MSC/VLRB) User data in MSC/VLRC). Then, a Cancel Subscriber Location Confirmation is sent back to the HLR.

Here, in each MSC/VLR, there are an active VLR and a standby VLR. The active VLR is used to save the data of the local office users, and the standby VLR is used to store the main office of the MSC/VLR to back up the MSC in the local office. /VLR's primary office user data; for MSC/VLRB, the user data of its local office (MSC/VLRB) is backed up in the backup VLR of its backup office (MSC/VLRC), while its primary office ( That is, the user data of MSC/VLRA) is backed up in the backup VLR in this office (that is, MSC/VLRB). Wherein, the address of the backup VLR of this office (can be understood as the VLR where the user data of this office is backed up) and the backup VLR of the main office (can be understood as the VLR where the user data of the main office is backed up) is determined by the data configuration. The "office" mentioned in the present invention refers to a switching node in the communication system, such as an MSC/VLR.

Steps 14-15: HLR inserts user data into MSC/VLRB, including all subscriber data of the user, such as: forwarding information, Came subscription data; ODB information, etc., and sends a location update acceptance message to MSC/VLRB.

Steps 16-17: If the paging response reassignment switch is turned on, the RAN to which the user belongs has enabled the Iu/A-Flex function, the user is not registered in the local office when receiving the paging response message, and the user location cancellation message is received during the location update process , then the MSC/VLRB allocates a Temporary Mobile Subscriber Identity (TMSI, Temporary Mobile Subscriber Identity) containing a null network resource identity (null-NRI) to the user, and simultaneously sends the assigned TMSI and a non-broadcast location area identity (non-broadcast The TMSI reallocation command of the LAI) is sent to the RAN to send the TMSI and the non-broadcast LAI to the user terminal. After receiving the non-broadcast LAI, the user terminal will initiate a location update process to the RNC. At this time, because the RNC has received an empty network resource identifier, it will allocate a new MSC/VLR for the user terminal, so that the original registration in the MSC/VLR Each user in the VLRA can evenly re-register to each MSC in the MSC POOL to realize load sharing in the MSC POOL; otherwise, MSC/VLRB allocates the local TMSI to the user, and sends a TMSI redistribution command carrying the allocated local TMSI to the RAN to send the TMSI to the UE.

Step 18: MSC/VLR B sends a user data backup command to its backup office——MSC/VLRB. The user data backup command carries information such as the user's IMSI, LAI, and user status, and ends the paging process.

Like this, the MSC number of the user recorded in the HLR is the number of the MSCB, so when the user is called for the second time, the HLR will call the user through the MSC/VLRB, thereby successfully recovering the called party.

In addition, if the downtime server in MSC POOL resumes service within a periodic location update period, and the original service user initiated the calling service or did not update the location to other servers in MSC POOL, then At this time, these users will never be able to be successfully called as the called party. In order to solve this problem, the downtime server needs to go to its backup server to fetch user data, and then send paging.

Fig. 6 is in the method of the present invention, the signaling flow diagram of recovering called user data after SERVER goes down. Fig. 6 shows three SERVERs in MSC POOL: MSC/VLRA, MSC/VLRB and MSC/VLRC, form chain backup among these three SERVERs, wherein, the data backup of MSC/VLRA is in MSC/VLRB, The data of MSC/VLRB is backed up in MSC/VLRC, while the data of MSC/VLRC is backed up in MSC/VLRA. In addition, according to the above routing priority configuration method, the priority of the direct route to a certain MSC/VLR signaling point is higher than the detour route to the MSC/VLR signaling point through the MSC/VLR backup office signaling point. For example, the priority of the direct route to signaling point AA of MSC/VLRA is higher than the detour route to signaling point AA via signaling point BB of MSC/VLRB.

If the downtime MSC/VLRA restores the service within a periodic location update period, but the original service user has not updated the location to other SERVERs in the MSC POOL, the signaling process for calling the user at this time includes :

Step 1-2: HLR sends PRN message to MSC/VLRA through STP to get the user's roaming number. Since the MSC/VLRA has resumed service, a high-priority route is selected according to the setting of the aforementioned route priority. Therefore, the STP sends the PRN message to the MSC/VLRA, where the addressing mode is DPC+SSN.

Step 3: If the user is not registered in the office (ie MSC/VLRA) and the MSC number in the PRN message is the MSC number of the office (ie the number of MSCA), then MSC/VLRA goes to its backup office (ie MSC/VLRB) Extract user data (the extracted user data is only a small part of the subscribed comprehensive user data, mainly IMSI and LAI). If the user is registered in the backup VLR (ie MSC/VLRB), then perform step 4; otherwise, perform step 7.

Wherein, if the user is registered in the MSC/VLRA, and the MSC/VLRA is processing the user's business, it can directly return a PRN ACK message to the HLR to indicate that the user is busy and end this service processing.

Step 4: If the user is in the shutdown state, the MSC/VLRA returns a PRN ACK message to the HLR through STP to indicate the absent user; otherwise, perform step 5.

Step 5: The MSC/VLRA updates the location area information of the user, and extracts and restores the user data of the user from the HLR. Wherein, if the restoration of user data fails, the MSC/VLRA returns a PRNACK message to the HLR to indicate that the user is unreachable, and ends this service processing. Here, the restored user data is the comprehensive user data subscribed in the HLR.

Step 6: MSC/VLRA assigns the roaming number of this office to the user, and returns the PRN ACK message carrying the roaming number to the HLR, so that the HLR can successfully obtain the roaming number of the user, complete the call, and end this service processing.

Step 7: If network-wide paging is permitted, interact with the HLR to restore user data; otherwise, execute step 9. Here, in the case of MSC POOL networking, the network-wide paging function switch is usually turned off by default.

Wherein, if the user data recovery fails, the MSC/VLRA returns a PRN ACK message to the HLR to indicate that the user is unreachable, and ends this service processing.

Step 8: MSC/VLRA allocates a local roaming number for the user, and returns a PRN ACK message carrying the roaming number to the HLR, so that the HLR can successfully obtain the user's roaming number, complete the call, and end this service processing.

Step 9: MSC/VLRA returns a PRN ACK message to HLR to indicate that the user is unreachable, and ends this service processing.

Based on above-mentioned method of the present invention, the present invention also provides two kinds of systems that the called party recovers in the mobile switching center pool, comprise: the MSC POOL that HLR and a plurality of MSC/VLR form, it is characterized in that, further include each in the described MSC POOL A backup office of MSC/VLR, these two kinds of systems correspond to two kinds of situations shown in above-mentioned Fig. 5 and Fig. 6 respectively: 1, the service MSC/VLR of the user goes down, and this user has not initiated calling service or location update The user is called, 2. The user's service MSC/VLR resumes within a periodical location update period after the user's service MSC/VLR goes down, and the user has not initiated a calling service or location update during this periodical location update period, and the user as called. In the following two situations, the connection relationship and realized functions in the system of the present invention will be described respectively.

1. The user serves as the called party when the user's service MSC/VLR is down, and the user has not initiated a calling service or location update.

Wherein, the HLR is used to send call signaling to the backup office of the downtime MSC/VLR, and when the backup office initiates a location update, the user data of the user is inserted into the backup office and the service MSC/VLR of the user is updated for the backup office. The backup office is used for backing up MSC/VLR user data, initiates paging to the user and initiates location update of the user to the HLR when receiving call signaling from the HLR, and registers the user data inserted by the HLR.

Here, the backup office can also back up the registered user data of the user in its own backup office.

The system may further include: a user terminal and the RAN to which it belongs. At this time, after the backup office registers the user data of the user, it can allocate a TMSI containing null-NRI to the user, and issue a TMSI reallocation command carrying the TMSI and non-broadcast LAI to the user through the RAN. The user terminal of the user; after receiving the non-broadcast LAI, the user terminal can initiate a location update request carrying a null-NRI to the RNC in the RAN to which it belongs, and the RNC can allocate the MSC POOL for the user according to the null-NRI The new MSC/VLR acts as the serving MSC/VLR.

In this case, the processing of the system of the present invention corresponds to the flow chart in FIG. 5 , and the system can implement each step shown in FIG. 5 , and the system will not be further described in detail for each step in FIG. 5 here.

2. After the user's service MSC/VLR goes down, it resumes within a periodic location update period. During this periodic location update period, the user has never initiated a calling service or location update, and the user is called.

Wherein, the HLR can be used to send call signaling to the MSC/VLR recovered after the downtime, output the subscriber data of the user to the MSC/VLR recovered after the downtime, and recover from the downtime The MSC/VLR receives the user's roaming number; the MSC/VLR can be used to extract the user's backup user data from its backup office to update the user's location area information after receiving the call signaling, and extract the user's location area information from the HLR. User data and restore the user data, allocate the roaming number of the local office for the user and return to the HLR.

Here, when extracting the user data of the user from the HLR and restoring the user data, if restoring the user data fails, the MSC/VLR may further return a response indicating that the user is unreachable to the HLR. When extracting the user's backup user data from its backup office, if the user's backup user data is not in the backup office, the MSC/VLR can be further used to extract the user's user data from the HLR and recover, for The user allocates a local office roaming number, and returns the allocated local office roaming number to the HLR.

In this case, the processing of the system of the present invention corresponds to the flow chart in FIG. 6 , and the system can implement each step shown in FIG. 6 , and the system will not be further described in detail for each step in FIG. 6 here.

Above-mentioned two kinds of systems of the present invention can further comprise: STP, it is used for when MSC/VLR is effective (for example: when recovering again after downtime or running normally), the calling signaling from HLR is sent to this MSC/VLR; When the MSC/VLR fails (for example: downtime), the call signaling from the HLR is sent to the backup office of the MSC/VLR. Among them, it can be pre-configured in STP: the priority of the direct route to the MSC/VLR is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; The signaling point is the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the priority of the signaling point of the backup office of the MSC/VLR is lower than the signaling point of the MSC/VLR; thus, in the MSC When the /VLR is valid, the STP can send call signaling to the MSC/VLR through the high-priority direct route, or can send call signaling to the signaling point of the high-priority MSC/VLR; when the MSC/VLR fails In this case, the STP can send call signaling to the backup office of the MSC/VLR through a low-priority detour route, or can send call signaling to the signaling point of the backup office of the MSC/VLR with low priority.

In addition, in above-mentioned two kinds of systems of the present invention, two kinds of backup methods can be adopted: 1, centralized backup: one or more backup centers can be centrally set in the MSCPOOL, and each backup center is responsible for backing up the user data of one or more MSC/VLRs , the backup office of a MSC/VLR can be one of the backup centers; 2. Chain backup: the user data of an MSC/VLR is backed up in any other MSC/VLR in the MSC POOL, and the backup office of an MSC/VLR It is another MSC/VLR other than the MSC/VLR in the MSC POOL.

The backup office may include a backup interface, configured to receive user data sent by the backup interface of the main office through a backup link established between the main office and the backup office.

Optionally, after the backup interface of the backup office receives the user deletion notification sent by the backup interface of the active office, the backup office deletes the backup user data.

Optionally, the backup interface of the backup office is further configured to send a re-backup single user notification carrying the user's IMSI to the backup interface of the active office when user data needs to be backed up again, and the backup of the secondary office corresponds to the IMSI user data.

Optionally, the backup office is further used to determine that no backup data message carrying user data is received from the primary office within the set time period, so as to re-backup the user data, and then delete the backup data message carried in the backup data message. The user data corresponding to the IMSI.

Optionally, the backup office regularly sends a backup command to the backup interface of the active office through the backup interface of the backup office, so as to back up user data from the active office again.

The present invention also can provide a kind of above-mentioned two kinds of situations above-mentioned this system all can be applicable to the system that the callee recovers in the mobile switching center pool, promptly this system can realize all functions of above-mentioned two kinds of systems, just no longer do this kind of system here Further details.

In addition, the present invention also discloses two switching devices, which are used to control voice or data exchange, process call signaling interaction, and realize interconnection and intercommunication between access network devices, which are located in the MSC POOL composed of multiple MSC/VLRs . The following is an overview of these two types of switching devices:

1. The switching equipment is used as the backup office of at least one MSC/VLR in the MSC POOL, and the at least one MSC/VLR is used as the main office of the switching equipment. The switching equipment may include: a first module for storing the main office. The backup user data of the office; the second module, when the called user of the call signaling is not the local office user and the call signaling is not calling the local office, extract the backup user data of the called user from the first module, and page the called user Call the user, initiate the location update of the called user, delete the backup user data of the called user from the first module, and update the switching device where the user is located as the service switching device of the called user.

The first module may include a backup interface, configured to receive user data sent by the backup interface of the main office through a backup link established between the main office and the backup office.

Optionally, after the backup interface of the first module receives a user deletion notification sent by the backup interface of the master office, the first module deletes the backup user data.

Optionally, the backup interface of the first module is further configured to send a re-backup single user notification carrying the user's IMSI to the backup interface of the main office when user data needs to be backed up again, and the backup and the IMSI from the main office corresponding user data.

Optionally, the first module is further used to determine that no backup data message carrying user data is received from the main office within the set time period, so as to re-backup the user data, and delete the backup data message in the backup data message User data corresponding to the carried IMSI.

Optionally, the first module periodically sends a backup command to the backup interface of the active office through the backup interface, so as to back up user data from the active office again.

In practical applications, this kind of switching equipment is usually an MSC/VLR or a backup center as a backup office of a certain MSC/VLR in the MSC POOL, and the first module in it usually refers to the backup VLR in the MSC/VLR or the backup center in the backup center. A backup depository unit with a function similar to a backup VLR; the second module therein may include: a control module, a location update module, a paging module and a depository unit.

Wherein, the control module is used to extract the backup user data of the called user from the first module and trigger the paging module when the called user of the call signaling is not the local office user and the call signaling is not calling the local office; The location update module is triggered when the user of the paging response is not registered in this office; after the HLR confirms that the location of the called user is canceled, the backup user data of the called user is deleted from the first module; the called user is extracted from the HLR user data and insert into the register unit. The location updating module, after being triggered by the control module, initiates location updating of the called user to the HLR. The paging module, after being triggered by the control module, initiates paging of the called user according to the backup user data of the called user extracted by the control module, and receives a paging response. The registration unit (usually referring to the VLR in the MSC/VLR or the registration unit with similar VLR function in the backup center), registers the called user in the local office according to the user data of the called user inserted by the control module. Here, any one or any combination of the control module, location update module, paging module, and registration unit can adopt the existing functional modules in switching equipment such as MSC/VLR or backup center, and can also be new functional modules according to the present invention. The modules added in switching equipment such as MSC/VLR or backup center are not limited in the present invention, no matter what kind of internal module division method the above-mentioned switching equipment adopts, as long as the realized function is the same as the above-mentioned switching equipment, it is regarded as the present invention Variations of the embodiments do not fall within the protection scope of the present invention.

2. This kind of switching equipment is located in the MSC POOL composed of multiple MSCs/VLRs. The switching equipment is used as the main office, and the MSC POOL also includes the backup office of the switching equipment. This kind of switching equipment may include: a third module, used for extracting the backup user data of the called user from the backup office of the switching equipment when the called user of the call signaling is not the local office user and the call signaling calls the local office , updating the location area information of the called user, recovering the user data of the called user, and providing the roaming number of the called user. The third module may include: a control module, a roaming number assignment module and a registration unit. Here, this kind of switching equipment usually refers to the MSC/VLR in the MSC POOL as the master office.

Wherein, the control module is used to extract the backup user data of the called user from the backup office of the switching equipment when the called user of the call signaling is not the local office user and the call signaling calls the local office, and update the called user's location area information, extract the user data of the called user from the HLR and output it to the registration unit, and trigger the roaming number allocation module; the roaming number allocation module is used to allocate a roaming number for the called user after being triggered by the control module And provide it to HLR; the registration unit is used to restore the user data of the called user according to the user data from the control module. Here, the registration unit is usually the VLR in the MSC/VLR; any one or any combination of the control module, the roaming number distribution module and the registration unit can adopt existing functional modules in switching equipment such as MSC/VLR, or can In order to add modules in switching devices such as MSC/VLR according to the present invention, the present invention is not limited to this, no matter what kind of internal module division method the above-mentioned switching device adopts, as long as the function realized is the same as the above-mentioned switching device, it is regarded as The deformation of the embodiments of the present invention does not fall within the protection scope of the present invention.

The internal composition structures and implementation principles of the two switching devices are described below in conjunction with FIGS. 7 and 8 respectively.

Fig. 7 is the internal structure diagram of the MSC/VLR as backup office among the present invention, and a concrete example of this MSC/VLR is exactly the MSC/VLRB among Fig. 5, and the MSC/VLR shown in this Fig. 7 can realize Fig. 5 All the functions that the MSC/VLRB can realize. As shown in Fig. 7, this MSC/VLR connects HLR and RAN, and this MSC/VLR can comprise: control module, location updating module, VLR, paging module; This MSC/VLR can further comprise: backup VLR, it is used to preserve The backup user data of the primary office. Wherein, the control module, the location update module, the VLR and the paging module can be existing modules in the MSC/VLR, therefore, the basic functions realized by these modules belong to those skilled in the art, and will not be described herein, but Only added functions based on the present invention are explained. The functions realized by the MSC/VLR shown in Figure 7 include: when the user's serving MSC/VLR is down, and the user has not initiated a calling service or location update, and the user is called, the backup office of the serving MSC/VLR Handling done to recover the called.

Wherein, the control module can receive the call signaling from the HLR, when the called user is not registered in the office and the MSC number carried in the call signaling is not the MSC number of the office, get the backup user data of the called user from the backup VLR and send Trigger the paging module; receive the paging response from the RAN, trigger the location update module when the user of the paging response is not registered in the local office; delete the user of the called user from the backup VLR after the HLR confirms that the location of the called user is canceled Data; extract the user data of the called user from the HLR and insert it into the VLR. After being triggered by the control module, the location update module can initiate the location update of the called user to the HLR through the control module. After the paging module is triggered by the control module, the backup user data of the called user extracted by the control module can initiate paging of the called user to the RAN through the control module, and receive the paging from the RAN through the control module paging response. The VLR can receive the user data of the called user inserted by the control module, and register the called user in the local office, so that the MSC/VLR as the backup office shown in Figure 7 can be updated as the service MSC/VLR of the called user, Then the called recovery is realized. Here, when the control module extracts the user data of the called user from the backup VLR, if the user data of the called user is not in the backup VLR, the control module can return a response indicating that the user is unreachable to the HLR; User's user data is in this backup VLR but called user is in power-off state, then this control module can return the response indicating absent user to HLR; After a period of time, the control module may return a response indicating that the user is unreachable to the HLR.

In addition, the control module can also back up the user data of the called user registered in the VLR to the backup office of the MAC/VLR. In order to enable each user originally registered in the downtime MSC/VLR to be evenly distributed to other MSC/VLRs in the MSC POOL to realize load sharing, the MSC/VLR shown in Figure 7 may further include: a TMSI redistribution module. At this time, the control module can trigger the TMSI reallocation module after the VLR registers the user data of the called user; the TMSI reallocation module can distribute the TMSI containing null-NRI to the called user after being triggered by the control module , and send a TMSI reallocation command carrying the TMSI and non-broadcast LAI to the RAN through the control module. In this way, when the user terminal of the called user receives the non-broadcast LAI, it can initiate a location update process to the RNC in the RAN, and the RNC can allocate the MSC POOL for the user terminal according to the TMSI uploaded by the user terminal that contains the null-NRI. The new MSC/VLR serves as its serving MSC/VLR. Further, the TMSI redistribution module may be further configured when the paging response redistribution switch is turned on, the RAN enables the Iu/A-Flex function, and the called user is not registered at the local office when the paging response is received and the location update process When the user location cancellation message is received, the TMSI containing null-NRI is allocated to the called user, and the TMSI reallocation command carrying the TMSI and non-broadcast LAI is issued to the RAN through the control module; in other cases, the local office is allocated The TMSI is given to the called user, and the TMSI reallocation command carrying the local TMSI is sent to the RAN through the control module.

Fig. 8 is the internal composition diagram of the MSC/VLR that recovers again after the downtime among the present invention, and a specific example of this MSC/VLR is exactly the MSC/VLRA among Fig. 6, and the MSC/VLR shown in this Fig. 8 can realize All functions that MSC/VLRA in Fig. 6 can realize. As shown in Figure 8, the MSC/VLR includes: a VLR, a control module and a roaming number allocation module. Wherein, the control module, VLR and roaming number distribution module can be existing modules in the MSC/VLR, therefore, the basic functions realized by these modules belong to those skilled in the art. The function added by the present invention. The functions realized by the MSC/VLR shown in Figure 8 include: when the user's service MSC/VLR is down, and the user has not initiated a calling service or location update, if the user's service MSC/VLR is down after a periodic location update During the recovery period, and the user has not initiated the calling service or location update, when the user is called during the periodic location update period, the service MSC/VLR restored after the downtime is used for recovery Called processing.

Wherein, the control module can receive call signaling from the HLR, and when the called user is registered in the local office and the MSC number in the call signaling is the MSC number of the local office, the backup user data of the called user is extracted from the backup office of the MSC/VLR , updating the location area information of the called user in the VLR, extracting the user data of the called user from the HLR and recovering the user data of the called user in the VLR, and triggering a roaming number allocation module. After being triggered by the control module, the roaming number assignment module can assign the local office roaming number to the called user and return it to the HLR through the control module.

In addition, when restoring the user data of the called user, the VLR may return a response indicating that the user is unreachable to the HLR through the control module if the user data recovery fails. When the control module further extracts the backup user data of the called user from the backup office of the MSC/VLR, if the backup user data of the called user is not in the backup office, extract the user data of the user from the HLR. The data is recovered, and the roaming number allocation module is triggered. Here, if the backup user data of the called user is not in the backup office and the whole network paging is not allowed, the control module can further return a response indicating that the user is unreachable to the HLR; if the backup user data of the called user is in the In the backup office and the called user is turned off, the control module may further return a response indicating the absent user to the HLR.

In addition, the present invention can also provide another switching device, which integrates all the functions of the switching device shown in Figures 7 and 8, that is, the switching device at least includes: a control module, a backup VLR, a location update module, a VLR, a paging module and a roaming number allocation module, the switching device may further include a TMSI re-allocation module. When the user's serving MSC/VLR is down, and the user has not initiated the calling service or location update and the user is the called party, the switching device can be used as the backup office of the serving MSC/VLR to restore the called party. For specific implementation, see Figure 7: When the user's service MSC/VLR is down, and the user has not initiated a calling service or location update, if the user's service MSC/VLR is restored within a periodic location update period after the downtime, and the user has not Initiate the calling service or update the location. During this periodic location update period, when the user is called, the switching device can be used as the MSC/VLR to restore the called service after the downtime. The specific implementation is shown in Fig. 8.

The invention also discloses a signaling forwarding device, such as the STP in the system of the invention, which includes: a priority configuration unit and a signaling forwarding unit. Wherein, the priority configuration unit is used to configure the priority of the direct route arriving at the switching device to be higher than the priority of the detour route arriving at the switching device through the backup office of the switching device; at this time, the signaling forwarding unit can receive the call signal from the HLR order, determine the service switching equipment (such as serving MSC/VLR) of the called user of the call signaling, query the priority configuration unit, and when the service switching equipment is valid, the call signaling can be sent to by a high-priority direct route The service switching device can send call signaling to the backup office of the service switching device through a low-priority detour route when the service switching device fails. Or, the priority configuration unit can be used to configure the signaling point of the backup office of the switching equipment as the SCCP load sharing signaling point of the signaling point of the switching equipment, and the priority of the signaling point of the backup office of the switching equipment is low At the signaling point of the switching equipment; at this time, the signaling forwarding unit can receive the call signaling from the HLR, determine the service switching equipment of the called user in the call signaling place, query the priority configuration unit, and in the service switching equipment When valid, call signaling can be sent to the signaling point of the service switching equipment with high priority; when the service switching equipment fails, call signaling can be sent to the signaling point of the backup office of the service switching equipment with low priority . The signaling forwarding device of the present invention can complete all the functions that the STP shown in FIG. 5 and FIG. 6 can complete, which will not be repeated here, but are within the protection scope of the present invention.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention are included in the protection scope of the present invention.

Claims (67)

1. a method for called recovery in a mobile switching center pool, applied to include: the system of the mobile switching center pool MSC POOL formed by the home location register HLR and a plurality of mobile switching centers/visitor location registers MSC/VLR, characterized in that , the backup office of each MSC/VLR is set in the MSC POOL, and the backup user data including the International Mobile Subscriber Identity and the Location Area Identification are backed up in the backup office; if the service MSC/VLR of the user is down, and the user has not initiated Calling service or location update, when the user is called, the method includes: The HLR sends the call signaling to the backup office of the downtime MSC/VLR through the signaling transfer node STP, specifically including: when the serving MSC/VLR is valid, the STP sends the call signaling from the HLR to the serving MSC/VLR; When the serving MSC/VLR fails, the STP sends the call signaling from the HLR to the backup office of the serving MSC/VLR; The backup office initiates paging to the user and initiates location update of the user to the HLR; The HLR registers the user data of the user in the backup office and updates the user's serving MSC/VLR to the backup office. 2. The method according to claim 1, wherein the backup office initiates paging to the called party, comprising: When the backup office receives the call signaling, if the user is not registered in the office and the MSC number carried by the call signaling is not the MSC number of the office, then extract the user data backed up by the user's serving MSC/VLR in the office, and Initiate paging to the user according to the user data. 3. The method according to claim 1 or 2, wherein when initiating paging to the user, further comprising: returning a response indicating that the user is unreachable to the HLR. 4. The method according to claim 3, further comprising: setting a timer, starting the timer when initiating paging to the user, and sending the instruction that the user is unreachable after the timer expires the response to. 5. The method according to claim 1 or 2, characterized in that, when the backup office initiates paging to the user, it only paging the user once. the 6. The method according to claim 1, wherein the backup office initiates the user's location update to the HLR, and the HLR registers the user's user data in the backup office and sends the user's service MSC/VLR Updates for this backup board include: After receiving the user's paging response, the backup office sends a location update request to the HLR; The HLR sends a cancel user location message to the backup office; The backup office deletes the user data backed up by the downtime MSC/VLR in the office and returns the confirmation of canceling the user location to the HLR; The HLR inserts the user's user data into the backup office, and records the user's serving MSC/VLR as the backup office. 7. method according to claim 6, it is characterized in that, described HLR sends call signaling and cancel subscriber location message to the backup office of the MSC/VLR of this downtime by signaling transfer node STP; Pre-configuration in the STP: the priority of the direct route to the MSC/VLR is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; or, the signaling of the backup office of the MSC/VLR The point is the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the signaling point of the backup office of the MSC/VLR has a lower priority than the signaling point of the MSC/VLR; The HLR sends the call signaling to the backup office of the downtime MSC/VLR through the STP, including: the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is down, the low priority A detour at the level is by sending the call signaling to the backup office of the downtime MSC/VLR; or, the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is down, the call signaling is sent The signaling point of the backup office of the downtime MSC/VLR with the lowest priority; The HLR sends the message of canceling the user location to the backup office through the STP, including: the HLR sends the message of canceling the user location to the STP, and when the STP determines that the MSC/VLR is down, it will send The message of canceling the user location is sent to the backup office of the downtime MSC/VLR; or, the HLR sends the message of canceling the location of the user to the STP, and when the STP determines that the MSC/VLR is downtime, the message of canceling the location of the user is sent. Send to the signaling point of the backup office of the downtime MSC/VLR with low priority. 8. according to the described method of claim 1 or 6, it is characterized in that, after this HLR registers the subscriber data of this user at this backup office and the service MSC/VLR of this user is updated as this backup office, this method is further It includes: the backup office backups the user data of the registered user in its own backup office. 9. The method according to claim 6, characterized in that, after receiving the user's paging response, the backup office further comprises: If the user is not registered in the home office, the backup office sends a location update request to the HLR. 10. The method according to claim 1 or 6, characterized in that, after the subscriber data of the user is registered in the backup office by the HLR and the service MSC/VLR of the user is updated as the backup office, the method is further include: The backup office allocates a TMSI containing null-NRI to the user, and sends a TMSI reallocation command carrying the TMSI and non-broadcast LAI to the user terminal of the user through the RAN to which the user belongs, and the user terminal receives the non-broadcast LAI After the broadcast LAI, a location update request carrying a null-NRI is initiated to the RNC to which it belongs, and the RNC assigns a new MSC/VLR in the MSC POOL as a serving MSC/VLR for the user according to the null-NRI. 11. The method according to claim 1, wherein, if the user's service MSC/VLR is down and recovers within a periodical location update period, and the user has never initiated a calling service or location update, During this periodic location update period, when the user is called, it further includes: Said HLR sends the call signaling to the MSC/VLR recovered after the downtime; The recovered MSC/VLR extracts the user's backup user data from its backup office; The recovered MSC/VLR updates the location area information of the user after the downtime, extracts the user data of the user from the HLR and restores the user data, assigns the roaming number of the local office to the user and returns the assigned roaming number of the local office to the user HLR. 12. method according to claim 11 is characterized in that, described HLR sends calling signaling to the MSC/VLR that recovers again after the downtime by STP; Pre-configuration in the STP: the priority of the direct route to the MSC/VLR is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; or, the signaling of the backup office of the MSC/VLR The point is the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the signaling point of the backup office of the MSC/VLR has a lower priority than the signaling point of the MSC/VLR; The HLR sends the call signaling to the recovered MSC/VLR through the STP, including: the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is valid, the high-priority The direct route sends the call signaling to the recovered MSC/VLR after the downtime; or, the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is valid, it sends the call signaling to the high-priority The signaling point of the MSC/VLR that recovers after the downtime of the level. 13. The method according to claim 11, characterized in that, when the MSC/VLR recovering after the downtime extracts the user's backup user data from its backup bureau, further comprising: If the user's backup user data is in the backup office, then extract the user's backup user data from the backup office; otherwise, extract the user's user data from the HLR and recover, assign the user a roaming number of this office, and Return the allocated local office roaming number to the HLR. 14. The method according to claim 1, wherein the backup office of each MSC/VLR is set, comprising: one or more backup centers are centrally set in the MSC POOL, and each backup center is one Or the backup office of multiple MSC/VLRs; or, the backup office of an MSC/VLR is another MSC/VLR other than the MSC/VLR in the MSC POOL. 15. The method according to claim 1, wherein the backup office of each MSC/VLR is set, comprising: Establish a backup link between the primary office and the backup office; The user data of the active office is backed up to the backup office through the backup link. 16. The method according to claim 15, wherein before backing up the user data of the main office to the backup office through the backup link, it comprises: automatically triggering the backup of the main office; The method for backing up the user data of the main office to the backup office includes: through the backup link, the main office sends a backup data message to the backup office, backs up the user data of the main office to the backup office, and the message of the backup data message The type code is 101, including the identification of the sending module that sends the message with a length of 1 byte, the identification of the receiving module that receives this type of message with a length of 1 byte, and the message type code of this type of message with a length of 1 byte , the length of this type of message with a length of 1 byte, and the data carried in this message with an optional length; Alternatively, before backing up the user data of the main office to the backup office through the backup link, it includes: triggering backup through system maintenance; the method of backing up the user data of the main office to the backup office through the backup link includes: Through the backup link, the master office sends a request for backing up all user data to the backup office, and backs up all user data of the master office to the backup office. The message type code of the backup all user data request is 1, including a length of 1 character. The identification of the sending module that sends the message, the identification of the receiving module that receives this type of message with a length of 1, the message type code of this type of message with a length of 1 byte, and the length of this type of message with a length of 1 byte , and the data carried in this message of optional length. 17. The method according to claim 16, wherein the automatically triggering the master office to perform backup includes: triggering the master office to perform backup when the user initializes, triggering the master office to perform backup when the user location changes, and the user When it is deleted, it triggers the primary office to perform backup or when the user turns on and off the machine, it triggers the primary office to perform backup. 18. The method according to claim 15, characterized in that, after backing up the user data of the primary office to the backup office through the backup link, the steps include: The primary office sends a delete user message to the backup office to notify the backup office to delete user data, and the message type code of the delete user message is 103; or, The master office sends a request to delete all backup data to the backup office, instructing the backup office to delete all backup data, and the message type code of the request to delete all backup data is 3; or, The main office sends a backup control change notification to the backup office, so that the main office can control the user data of the backup office; the message type code of the backup control parameter change notification is 5; or, The backup office sends a backup stop notification to the active office to notify the active office to stop backing up user data; the message type code of the backup stop notification is 6. 19. The method according to claim 15, characterized in that, after backing up the user data of the primary office to the backup office through the backup link, the steps include: When the backup office needs to back up user data again, it sends a single user notification carrying the user's IMSI to the primary office, and re-backs up the user data corresponding to the IMSI from the primary office; the message of resetting the single user notification The type code is 105, including the identification of the sending module that sends the message with a length of 1, the identification of the receiving module that receives this type of message with a length of 1 byte, the message type code and length of this type of message with a length of 1 byte The length of this type of message is 1 byte, and the data carried in this message has an optional length. 20. The method according to claim 15, characterized in that, after backing up the user data of the primary office to the backup office through the backup link, the steps include: The backup office determines that no backup data message carrying user data is received from the master office within the set time period, so as to back up the user data again, and then deletes the user data. 21. The method according to claim 15, characterized in that, after backing up the user data of the main office to the backup office through the backup link, it includes: the backup office regularly sends a backup command to the main office to The master office backs up user data again. 22. A method for called recovery in a mobile switching center pool, applied to a system comprising: an MSC POOL formed by an HLR and a plurality of MSC/VLRs, characterized in that the MSC/VLR is set in the MSC POOL Backup office, where backup user data including IMSI and location area ID are backed up; if the user's service MSC/VLR is down and then restored within a periodic location update period, and the user has not initiated the calling service or location update, when the user is called during a periodical location update period, the method includes: Described HLR sends call signaling to the MSC/VLR recovered again after the downtime by STP, specifically includes: when serving MSC/VLR is valid, STP sends the calling signaling from HLR to serving MSC/VLR; When the /VLR fails, the STP sends the call signaling from the HLR to the backup office serving the MSC/VLR; The recovered MSC/VLR extracts the user's backup user data from its backup office, updates the user's location area information, and extracts the user's user data from the HLR and restores the user data to provide the user Allocate the local office roaming number and return the allocated local office roaming number to the HLR. 23. The method according to claim 22, characterized in that, the HLR sends the call signaling to the MSC/VLR recovered after the downtime by STP; Pre-configuration in the STP: the priority of the direct route to the MSC/VLR is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; or, the signaling of the backup office of the MSC/VLR The point is the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the signaling point of the backup office of the MSC/VLR has a lower priority than the signaling point of the MSC/VLR; The HLR sends the call signaling to the recovered MSC/VLR through the STP, including: the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is valid, the high-priority The direct route sends the call signaling to the recovered MSC/VLR after the downtime; or, the HLR sends the call signaling to the STP, and when the STP determines that the MSC/VLR is valid, it sends the call signaling to the high-priority The signaling point of the MSC/VLR that recovers after the downtime of the level. 24. The method according to claim 22, characterized in that, when the user is not registered in the office and the MSC number carried by the received call signaling is the MSC number of the office, then the MSC/VLR that has recovered after the downtime will start from its The backup user data of the user is extracted from the backup bureau. 25. The method according to claim 22, wherein, when the MSC/VLR recovering after the downtime extracts the user's backup user data from its backup bureau, further comprising: If the user's backup user data is in the backup office, then extract the user's backup user data from the backup office; otherwise, extract the user's user data from the HLR and recover, assign the user a roaming number of this office, and Return the allocated local office roaming number to the HLR. 26. The method according to claim 22, wherein the backup office of each MSC/VLR is set, comprising: one or more backup centers are centrally set in the MSC POOL, and each backup center is one Or the backup office of multiple MSC/VLRs; or, the backup office of an MSC/VLR is another MSC/VLR other than the MSC/VLR in the MSC POOL. 27. The method according to claim 22, characterized in that, said setting the backup office of each MSC/VLR comprises: Establish a backup link between the primary office and the backup office; The user data of the active office is backed up to the backup office through the backup link. 28. The method according to claim 27, characterized in that before backing up the user data of the main office to the backup office through the backup link, it comprises: automatically triggering the backup of the main office; The method for backing up the user data of the main office to the backup office includes: through the backup link, the main office sends a backup data message to the backup office, backs up the user data of the main office to the backup office, and the message of the backup data message The type code is 101, including the identification of the sending module that sends the message with a length of 1 byte, the identification of the receiving module that receives this type of message with a length of 1 byte, and the message type code of this type of message with a length of 1 byte , the length of this type of message with a length of 1 byte, and the data carried in this message with an optional length; Alternatively, before backing up the user data of the main office to the backup office through the backup link, it includes: triggering backup through system maintenance; the method of backing up the user data of the main office to the backup office through the backup link includes: Through the backup link, the master office sends a request for backing up all user data to the backup office, and backs up all user data of the master office to the backup office. The message type code of the backup all user data request is 1, including a length of 1 character. The identification of the sending module that sends the message, the identification of the receiving module that receives this type of message with a length of 1, the message type code of this type of message with a length of 1 byte, and the length of this type of message with a length of 1 byte , and the data carried in this message of optional length. 29. The method according to claim 28, wherein the automatically triggering the master office to perform backup includes: triggering the master office to perform backup when the user initializes, triggering the master office to perform backup when the user location changes, and the user When it is deleted, it triggers the primary office to perform backup or when the user turns on and off the machine, it triggers the primary office to perform backup. 30. The method according to claim 27, characterized in that, after backing up the user data of the primary office to the backup office through the backup link, the steps include: The primary office sends a delete user message to the backup office to notify the backup office to delete user data, and the message type code of the delete user message is 103; or, The master office sends a request to delete all backup data to the backup office, instructing the backup office to delete all backup data, and the message type code of the request to delete all backup data is 3; or, The main office sends a backup control change notification to the backup office, so that the main office can control the user data of the backup office; the message type code of the backup control parameter change notification is 5; or, The backup office sends a backup stop notification to the active office to notify the active office to stop backing up user data; the message type code of the backup stop notification is 6. the 31. The method according to claim 27, characterized in that, after backing up the user data of the primary office to the backup office through the backup link, the steps include: When the backup office needs to back up user data again, it sends a single user notification carrying the user's IMSI to the main office, and re-backs up the user data corresponding to the IMSI from the main office; the message type of the single user notification is The code is 105, including the identification of the sending module that sends the message with a length of 1, the identification of the receiving module that receives this type of message with a length of 1 byte, the message type code of this type of message with a length of 1 byte, and the length of 1 byte The length of this type of message is 1 byte, and the data carried in this message is optional. 32. The method according to claim 27, characterized in that, after backing up the user data of the primary office to the backup office through the backup link, the steps include: The backup office judges that it has not received the backup data message carrying the user data from the main office within the set time period, so as to back up the user data again, and then deletes the user data. 33. The method according to claim 27, characterized in that, after backing up the user data of the main office to the backup office through the backup link, it includes: the backup office regularly sends a backup command to the main office to The master office backs up user data again. 34. A system for called recovery in a mobile switching center pool, comprising: an MSC POOL formed by an HLR and a plurality of MSC/VLRs, characterized in that the MSC POOL further includes a backup office of STP and each MSC/VLR ; The HLR is used to send call signaling to the downtime MSC/VLR through STP when the user's serving MSC/VLR is down and the user has not initiated a calling service or location update and the user is called. the backup office; when the backup office initiates a location update, insert the user's user data into the backup office and update the user's serving MSC/VLR to the backup office; The backup office is used to back up the backup user data of the MSC/VLR including the international mobile subscriber identity and the location distinction identifier, and initiates paging to the user and initiates the location update of the user to the HLR when receiving the call signaling from the HLR , registering the user data of the user inserted by the HLR; STP is used to send the call signaling from the HLR to the MSC/VLR when the MSC/VLR is valid; when the MSC/VLR fails, send the call signaling from the HLR to the backup office of the MSC/VLR. 35. The system according to claim 34, wherein the backup office is further configured to back up the registered user data of the user in its own backup office. 36. The system according to claim 34 or 35, characterized in that the system further comprises: a user terminal and the RAN to which it belongs; After the backup office has registered the user data of the user, it is further used to allocate a TMSI containing null-NRI to the user, and issue a TMSI reallocation command carrying the TMSI and non-broadcastLAI to the user through the RAN user terminal; The user terminal is used to initiate a location update request carrying a null-NRI to the RAN to which it belongs after receiving the non-broadcast LAI; The RAN is used to assign the user a new MSC/VLR in the MSC POOL as a serving MSC/VLR according to the null-NRI. 37. The system of claim 34, wherein: The HLR is further used to recover within a periodical location update period after the service MSC/VLR of the user goes down, and the user has not initiated a calling service or location update during this periodical location update period. When the user is called, the call signaling is sent to the recovered MSC/VLR after the downtime, and the user data of the user is output to the recovered MSC/VLR after the downtime, and then recovered from the downtime The MSC/VLR receives the user's roaming number; The MSC/VLR is further used to extract the user's backup user data from its backup office to update the user's location area after receiving the call signaling when it resumes during a periodical location update period after a downtime Information, and extract the user data of the user from the HLR and restore the user data, distribute the roaming number of the local office for the user and return to the HLR. 38. The system according to claim 37, characterized in that, it is pre-configured in the STP: the priority of the direct route to reach the MSC/VLR is higher than the detour route to the MSC/VLR through the backup office of the MSC/VLR priority; or, the signaling point of the backup office of the MSC/VLR is the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the priority of the signaling point of the backup office of the MSC/VLR is lower than the MSC/VLR signaling point; When the MSC/VLR is valid, the STP sends call signaling to the MSC/VLR through a high-priority direct route, or sends call signaling to the signaling point of the high-priority MSC/VLR; When the MSC/VLR fails, the STP sends call signaling to the backup office of the MSC/VLR through a low-priority detour, or sends call signaling to the signaling of the low-priority backup office of the MSC/VLR point. 39. The system according to claim 34 or 37, characterized in that, one or more backup centers are centrally set in the MSC POOL, and the backup office of a MSC/VLR is one of the backup centers; or, an MSC/VLR The backup office is another MSC/VLR other than the MSC/VLR in the MSC POOL. 40. The system according to claim 34, characterized in that, the backup office includes a backup interface for receiving the data sent by the backup interface of the main office through the backup link established between the main office and the backup office. User data. 41. The system according to claim 40, wherein after the backup interface of the backup office receives the user deletion notification sent by the backup interface of the main office, the backup office deletes the backup user data. 42. The system according to claim 40, wherein the backup interface of the backup office is further configured to send a single user re-backup notification carrying the user's IMSI to the backup interface of the main office when user data needs to be backed up again , backing up the user data corresponding to the IMSI from the primary office. 43. The system according to claim 34, wherein the backup office is further used to determine that no backup data message carrying user data is received from the main office within the set time period, so as to perform user data If the backup is performed again, the user data corresponding to the IMSI carried in the backup data message is deleted. 44. The system according to claim 34, wherein the backup office regularly sends a backup command to the backup interface of the active office through the backup interface of the backup office, so as to back up user data from the active office again. 45. A system for called recovery in a mobile switching center pool, comprising: an MSC POOL formed by an HLR and a plurality of MSC/VLRs, characterized in that the MSC POOL further includes a backup office of STP and each MSC/VLR , the backup user data including the International Mobile Subscriber Identity and the Location Distinguishing Identity at the backup office; The HLR is used to recover within a periodical location update period after the service MSC/VLR of the user goes down, and the user has not initiated a calling service or location update during this periodical location update period and the When the user is called, the call signaling is sent to the recovered MSC/VLR through STP, and the user's user data is output to the MSC/VLR recovered after the crash, and restarted from the crash. The recovered MSC/VLR receives the user's roaming number; The MSC/VLR is used to extract the user's backup user data from its backup office to update the user's location area information after receiving the call signaling when it is restored within a periodical location update period after a downtime , and extract the user data of the user from the HLR and restore the user data, assign the roaming number of the local office to the user and return it to the HLR; The STP is used to send the call signaling from the HLR to the serving MSC/VLR when the serving MSC/VLR is valid; when the serving MSC/VLR fails, send the call signaling from the HLR to the serving MSC/VLR backup bureau. 46. The system of claim 45, further comprising: STP, the pre-configured priority of the direct route to the MSC/VLR is higher than the priority of the detour route to the MSC/VLR through the backup office of the MSC/VLR; when the MSC/VLR is valid, it is sent through the high-priority direct route The call signaling is sent to the MSC/VLR; when the MSC/VLR fails, the call signaling is sent to the backup office of the MSC/VLR through a low-priority detour route. 47. The system of claim 45, further comprising: STP, pre-configure the signaling point of the backup office of the MSC/VLR as the SCCP load sharing signaling point of the signaling point of the MSC/VLR, and the priority of the signaling point of the backup office of the MSC/VLR is lower than that of the MSC /VLR signaling point; when the MSC/VLR is valid, send call signaling to the high-priority MSC/VLR signaling point; when the MSC/VLR fails, send call signaling to the low-priority MSC/VLR The signaling point of the backup office of the VLR. 48. The system according to claim 45, characterized in that, one or more backup centers are centrally set in the MSC POOL, and the backup office of a MSC/VLR is one of the backup centers; or, the backup center of an MSC/VLR The backup office is another MSC/VLR other than the MSC/VLR in the MSC POOL. 49. The system according to claim 45, wherein the backup office includes a backup interface, which is used to receive the data sent by the backup interface of the main office through the backup link established between the main office and the backup office. User data. 50. The system according to claim 49, wherein after the backup interface of the backup office receives the user deletion notification sent by the backup interface of the main office, the backup office deletes the backup user data. 51. The system according to claim 49, wherein the backup interface of the backup office is further configured to send a single user re-backup notification carrying the user's IMSI to the backup interface of the primary office when user data needs to be backed up again , backing up the user data corresponding to the IMSI from the primary office. 52. The system according to claim 45, wherein the backup office is further used to determine that no backup data message carrying user data is received from the main office within the set time period, so as to perform user data If the backup is performed again, the user data corresponding to the IMSI carried in the backup data message is deleted. 53. The system according to claim 45, wherein the backup office regularly sends a backup command to the backup interface of the active office through the backup interface of the backup office, so as to back up user data from the active office again. 54. A switching device, used to control voice or data exchange, process call signaling interaction, and realize interconnection and intercommunication between access network devices; it is characterized in that it is located in an MSCPOOL composed of multiple MSCs/VLRs, the The switching equipment is used as the backup office of at least one MSC/VLR in the MSC POOL, and the at least one MSC/VLR is used as the main office of the switching equipment. The switching equipment includes: The first module is used to save the backup user data of the main user office, the backup user data includes the international mobile subscriber identity and the location distinction identifier; The second module, when the called user of the call signaling is not the local office user and the call signaling is not the calling local office, extract the backup user data of the called user from the first module, page the called user, and initiate The location of the called user is updated, and then the backup user data of the called user is deleted from the first module, and the switching device where the user is located is updated as the service switching device of the called user. 55. The device of claim 54, wherein the second module comprises: The control module, when the called user of the call signaling is not the local office user and the call signaling is not the calling local office, extract the backup user data of the called user from the first module and trigger the paging module; when the paging response Trigger the location update module when the user is not registered at the local office; delete the backup user data of the called user from the first module after the HLR confirms that the location of the called user is canceled; extract the user data of the called user from the HLR and insert the storage unit; The location update module, after being triggered by the control module, initiates the location update of the called user to the HLR; The paging module, after being triggered by the control module, initiates paging to the called user according to the backup user data of the called user extracted by the control module, and receives a paging response; The registration unit registers the called user in the local office according to the user data of the called user inserted by the control module. 56. The device according to claim 55, wherein the control module further backs up the user data of the called user registered in the registration unit in a backup office of the switching device. 57. The device according to claim 54 or 55, wherein the device further comprises: a TMSI reallocation module; The control module further triggers the TMSI reallocation module after the registration unit registers the called user; The TMSI redistribution module, after being triggered by the control module, distributes the TMSI containing the null-NRI to the called user, and sends the TMSI redistribution carrying the TMSI and non-broadcast LAI to the RAN through the control module Assign commands. 58. The device according to claim 55, further comprising: a roaming number allocation module; The control module is further used to extract the backup user data of the called user from the backup office of the switching device when the called user of the call signaling is not the local office user and the call signaling calls the local office, and update the called user data. The user's location area information extracts the user data of the called user from the HLR and recovers to the registration unit, and triggers the roaming number allocation module; The roaming number assignment module, after being triggered by the control module, assigns a roaming number to the called user and provides it to the HLR. 59. The device according to claim 54, characterized in that, the first module includes a backup interface, configured to receive data sent by the backup interface of the main office through the backup link established between the main office and the backup office. user data. 60. The device according to claim 59, characterized in that, after the backup interface of the first module receives a user deletion notification sent by the backup interface of the master office, the first module deletes the backup user data. 61. The device according to claim 59, wherein the backup interface of the first module is further used to send a backup single user carrying the user's IMSI to the backup interface of the primary office when user data needs to be backed up again Notify, and back up the user data corresponding to the IMSI from the primary office. 62. The device according to claim 54, wherein the first module is further configured to determine that no backup data message carrying user data is received from the primary office within the set time period, so as to save the user data If the backup is performed again, the user data corresponding to the IMSI carried in the backup data message is deleted. 63. The device according to claim 54, wherein the first module regularly sends a backup command to the backup interface of the active office through the backup interface, so as to back up user data from the active office again. 64. A switching device, used to control voice or data exchange, process call signaling interaction, and realize interconnection and intercommunication between access network devices, it is characterized in that the switching device is located as a primary office and is located in a plurality of MSC/ In the MSC POOL formed by the VLR, and the MSC POOL also includes the backup office of the switching equipment, the backup office includes the backup user data of the International Mobile Subscriber Identity and the location distinction identifier, and the switching equipment includes: The third module is used to extract the backup user data of the called user from the backup office of the switching equipment when the called user of the call signaling is not the local office user and the call signaling calls the local office, and update the called user's location area information, restore the user data of the called user, and provide the roaming number of the called user. 65. The device of claim 64, wherein the third module comprises: The control module extracts the backup user data of the called user from the backup office of the switching device and updates the location area information of the called user when the called user of the call signaling is not a local office user and the call signaling calls the local office , extracting the user data of the called user from the HLR and outputting it to the registration unit, and triggering the roaming number allocation module; The roaming number allocation module, after being triggered by the control module, allocates a roaming number for the called user and provides it to the HLR; The registering unit is used for recovering the user data of the called user according to the user data from the control module. 66. A signaling forwarding device, characterized in that the device comprises: A priority configuration unit, configured to configure the priority of the direct route to the switching device to be higher than the priority of the detour route to the switching device through the backup office of the switching device; The signaling forwarding unit is used to receive call signaling from the HLR, determine the service switching device of the called user, query the priority configuration unit, and send the call signaling through a high-priority direct route when the service switching device is valid To the service switching equipment; when the service switching equipment fails, send call signaling to the backup office of the service switching equipment through a low-priority detour route, in which the called user’s IMSI is backed up in the backup office Alternate user data identified by location and location. 67. A signaling forwarding device, characterized in that the device comprises: The priority configuration unit is used to configure the signaling point of the backup office of the switching equipment as the SCCP load sharing signaling point of the signaling point of the switching equipment, and the priority of the signaling point of the backup office of the switching equipment is lower than the signaling point of the switching equipment. Signaling point of switching equipment; The signaling forwarding unit is used to receive call signaling from the HLR, determine the service switching device of the called user, query the priority configuration unit, and send the call signaling to the high priority service switching device when the service switching device is valid. The signaling point of the equipment; when the service switching equipment fails, send call signaling to the signaling point of the backup office of the service switching equipment with low priority, in which the called user is backed up in the backup office, including international mobile users Alternate user data for identification and positional distinction identification. the

Images