CN1260983C - A method of disaster recovery for home location register (HLR) with zero-time service take-over - Google Patents

Abstract

Disclosed is a home location register disaster recovery method for zero-time service takeover, which relates to the backup of HLR equipment in a mobile communication system. In the network including BOSS system, active and standby HLR and signaling network, user data is divided into static data and dynamic data. After the networking is completed: connect the signaling link connected to the active HLR to the standby HLR: import the user data in the primary HLR to the backup HLR, after which the static data in the primary and backup HLR is updated by the BOSS system and ensure its consistency; start the backup HLR, achieve real-time online, and obtain users from signaling dynamic data; when the active HLR breaks down, set the working state of the standby number segment in the standby HLR to the active state. By implementing the present invention, the HLR can back up the HLRs of different manufacturers, and the HLR can be used as the master and backup at the same time, and zero-time service takeover can be realized.

Description

A home location register disaster recovery method for zero-time service takeover

technical field

The invention relates to disaster recovery of HLR (Home Location Register) equipment in a mobile communication system.

Background technique

With the rapid development of communication technology, mobile communication has become increasingly important in people's daily life. At the same time, people have put forward higher requirements for communication systems, hoping to enjoy stable and reliable services at any time. Disaster recovery technology can improve the reliability of equipment. The important means of sex have been widely used in mobile communication systems.

The disaster recovery HLR is the backup device of the main HLR, and takes over its business when the main HLR fails. In order to take over the business of the main HLR in time, the disaster recovery HLR must use effective means to obtain the latest dynamic information of mobile users. Currently, the disaster recovery HLR generally adopts the following methods:

(1) System storage level data disaster recovery

System storage-level data disaster recovery is realized by remote disaster recovery products provided by storage equipment manufacturers. The data synchronization function of the disaster recovery products ensures that the data of the primary and backup HLRs are consistent and realizes zero-time business takeover. But it has several serious disadvantages: first, it has high requirements on the system network; second, it requires the main and backup HLR equipment to be products of the same manufacturer, and there will be a certain period of service interruption when the product is upgraded; third, the cost is high .

(2) Database-level data disaster recovery

Database-level data disaster recovery relies on distributed database data replication technology to achieve data synchronization between the primary and secondary HLRs. This technology has several disadvantages: first, the overhead of the system and network is large, which affects the performance of the primary HLR; second, the data The real-time synchronization is poor. When the active HLR fails, some dynamic data will be lost, and some users’ services will be affected. Third, the damaged data in the active HLR may also be synchronized to the standby HLR, causing system abnormalities; Fourth, the primary and secondary HLRs are required to be from the same manufacturer, and services will be interrupted for a certain period of time when the version is upgraded.

(3) Application-level data disaster recovery

Application-level data disaster recovery divides backup data into static data and dynamic data. Static data synchronization is guaranteed by the BOSS (Business & Operation Support System) system, but currently dynamic data in application-level data disaster recovery relies on the This method has high requirements on the network, and some dynamic data may be lost when the main device fails.

Contents of the invention

The invention proposes a new application-level data disaster recovery method, which can overcome the deficiencies of the prior art. The primary and secondary HLR equipment can use products from different manufacturers; zero-time service takeover can be realized; the secondary HLR can be used as the primary HLR at the same time.

The technical solution of the present invention is to divide user data into static data and dynamic data in the network including BOSS system, primary and backup HLR and signaling network, and the static data can only be modified by the business operation support system or the operation maintenance system The user information of the dynamic data user is the data that can be modified through the operation of the mobile terminal or changes with the status of the mobile terminal. After the networking is completed:

1) All signaling links connected to the active HLR are connected to the standby HLR with corresponding parallel lines;

2) Import the user data in the active HLR to the standby HLR, after which the static data in the active and standby HLR is updated by the BOSS system to ensure its consistency;

3) Start the backup HLR, achieve real-time online, and obtain the user's dynamic data from the signaling;

4) When the active HLR breaks down, set the working state of the standby number segment in the standby HLR to the active state.

Wherein, the method of importing the user data in the primary HLR into the standby HLR in the step 2) can be completed by using the import and export tool of the database itself, or can be completed by specially developing an import and export tool.

The steps for the BOSS system to update and keep the consistent static data in the active and standby HLRs are: the BOSS system sends a message to the active and standby HLR when opening an account, canceling an account, and revising user subscription information, and the HLR updates the HLR according to the message sent by the BOSS If the user is a user of the primary number segment, and the number segment is in the primary state, then the HLR will synchronize data to the VLR (Visitor Location Register) or SGSN (Serving GPRSSupport Node service GPRS support node); if the user is the primary User with a number segment, and the number segment is in the state of being taken over, then the HLR does not synchronize data to the VLR or SGSN, and the process ends; Synchronize the data, and the processing ends; if the user is a user of the standby number segment, and the number segment is in the active state, then the HLR synchronizes the data to the VLR or SGSN.

The step of obtaining dynamic data from the signaling is: if the signaling is initiated by a network entity that interacts with the HLR for signaling, when receiving the signaling: if it is a user of the main number segment, and the number segment is in the main use state, then the HLR processes the signaling according to the procedures stipulated in the GSM protocol; if it is a user in the primary number segment, and the number segment is in the state of being taken over, if the signaling affects the dynamic information of the user, then the HLR modifies it according to the content of the signaling User dynamic information, the modification of dynamic information follows the GSM protocol. At this time, HLR does not return any response. If the signaling does not affect user dynamic information, then HLR discards the signaling; state, then the HLR processes the signaling according to the procedures specified in the GSM protocol; if it is a user with a standby number segment, and the number segment is in a standby state, if the signaling affects the user's dynamic information, then the HLR modifies the user's dynamic information according to the signaling content , the modification of the dynamic information follows the GSM protocol. At this time, the HLR does not return any response. If the signaling does not affect the user dynamic information, the HLR discards the signaling;

If the signaling is initiated by the HLR, then: if it is a user of the main number segment, and the number segment is in the active state, then the HLR processes the signaling according to the procedures specified in the GSM protocol; if it is a user of the main number segment, and If the number segment is in the state of being taken over, the HLR will not process the signaling; if it is a user of the standby number segment and the number segment is in the active state, then the HLR will process the signaling according to the procedures specified in the GSM protocol; if it is a backup number segment user, and the number segment is in standby state, if the signaling affects the dynamic information of the user, then the HLR will not process the signaling.

By implementing the present invention, the dynamic data is synchronized through standard signaling, while the static data is guaranteed by the BOSS system, and the BOSS interface can be determined through negotiation among various manufacturers. As long as the main and backup HLRs are unified on the BOSS interface, the internal implementation details of the main and backup HLRs can be completely different, so the HLRs realized according to this method can back up the HLRs of different manufacturers. According to the number, the HLR can distinguish whether the currently processed user is a user in the primary number segment or a backup number segment user, so as to perform processing in different ways. In the same HLR, the main number section and the standby number section can coexist, so the HLR realized according to this method can be used as the main use and the standby at the same time. Since the backup HLR can obtain the user's dynamic information in real time, the information in the backup HLR is consistent with the actual status of the user. As long as the state of the standby number segment is set to the active state, the standby HLR will immediately operate in the active mode, realizing zero-time service takeover.

Description of drawings

Figure 1 is a schematic diagram of networking;

Figure 2 is a flow chart of static data management;

Figure 3 is a flow chart of dynamic data management when the other party initiates signaling;

Fig. 4 is a flow chart of HLR work in the present invention.

Detailed ways

Below in conjunction with schematic diagram, the specific implementation steps of this method are introduced:

Figure 1 shows the networking mode of the active and standby HLRs. It is required that all signaling links connected to the active HLR have corresponding parallel connections to the standby HLR. The standby HLR updates the user's dynamic information in real time through the processing of signaling, while the static data in the standby HLR is updated by the BOSS system.

The management of the user's dynamic data and static data in the standby HLR is different, and the management methods of the two types of data are introduced respectively below.

1. Static data management

When the standby HLR joins the system, the active HLR may have assigned the number and may have been running for quite a long time. In order to take over the business of the active HLR, the standby HLR must copy the subscriber's subscription information in the active HLR. User data replication can be done by using the import and export tools of the database itself, or by specially developing import and export tools. After the data replication is completed, the user subscription information in the primary and secondary HLRs is consistent, and the subsequent static data will be synchronized by the BOSS system. The BOSS system is shown in Figure 1.

When the BOSS system opens an account, cancels an account, and modifies the user's subscription information, the main and backup HLRs must be notified, so that both the main and backup HLRs can update the user's subscription information. After receiving the notification message from the BOSS, the HLR processes it according to the following steps, as shown in Figure 2 for the process flow.

Update the user data in the HLR according to the message sent by the BOSS;

If the user is a user of the main number segment, and the number segment is in the main state, then the HLR will synchronize data to the VLR or SGSN;

If the user is a user of the main number segment, and the number segment is in the state of being taken over, then the HLR does not synchronize data to the VLR or SGSN, and the process ends;

If the user is a user of a standby number segment, and the number segment is in a standby state, the HLR does not synchronize data to the VLR or SGSN, and the process ends;

If the user is a user of the standby number segment and the number segment is in the active state, then the HLR will synchronize data to the VLR or SGSN;

Note: Data synchronization includes inserting user data and deleting user data, which is the same as described in the GSM (Global System For Mobile Communication) protocol;

2. Dynamic data management

The dynamic information in the standby HLR is updated in real time according to the signaling. Since the standby HLR may also be the main HLR at the same time, in order to reduce the load on the equipment, the standby HLR only processes the signaling that affects the user's dynamic information. The specific steps are as follows, and the process is shown in Figure 2:

When receiving the signaling, if it is the user of the main number segment, and the number segment is in the active state, then the HLR processes the signaling according to the procedures stipulated in the GSM protocol, which is the same as the ordinary HLR;

When receiving the signaling, if it is the user of the main number segment and the number segment is in the state of being taken over, if the signaling affects the user's dynamic information, then the HLR modifies the user's dynamic information according to the signaling content, and the modification of the dynamic information follows the GSM The protocol stipulates that the HLR does not return any response at this time, and if the signaling does not affect the user's dynamic information, the HLR discards the signaling;

If it is a user of the standby number segment, and the number segment is in the active state, then the HLR processes the signaling according to the procedures specified in the GSM protocol;

If it is a user with a standby number segment, and the number segment is in a standby state, if the signaling affects the user's dynamic information, then the HLR modifies the user's dynamic information according to the signaling content, and the modification of the dynamic information follows the GSM protocol. At this time, the HLR does not return any information. In response, if the signaling does not affect the dynamic information of the user, the HLR discards the signaling.

It can be seen that the dynamic data is synchronized through standard signaling, while the static data is guaranteed by the BOSS system, and the BOSS interface can be determined through negotiation between various manufacturers. As long as the main and backup HLRs are unified on the BOSS interface, the internal implementation details of the main and backup HLRs can be completely different, so the HLRs realized according to this method can back up the HLRs of different manufacturers.

In the present invention, since the HLR can be used as both the primary and the backup, its working mode is different from that of the common HLR. For the part of the standby number segment, if the number segment is running in the active mode at this time, then the HLR uses the number and signaling point code of the active HLR when talking to other network elements, so other network elements think that the active HLR is still in use. Work. The working steps of the HLR are as follows, and the flow chart is shown in Figure 4.

If the signaling process is initiated by the other party, the processing method is the same as the dynamic data management part, see Figure 3;

If the signaling is initiated by the HLR, the HLR needs to classify and process the signaling according to the actual situation, as follows:

If it is the user of the main number segment, and the number segment is in the active state, then the HLR processes the signaling according to the procedures stipulated in the GSM protocol, which is the same as the ordinary HLR;

If it is a user of the main number segment and the number segment is in the state of being taken over, then the HLR does not process the signaling;

If it is a user of the standby number segment, and the number segment is in the active state, then the HLR processes the signaling according to the procedures specified in the GSM protocol;

If it is a user with a standby number segment, and the number segment is in a standby state, if the signaling affects the user's dynamic information, then the HLR will not process the signaling;

Seen from this working mode, HLR can distinguish whether the currently processed user is a user in the primary number segment or a backup number segment user according to the number, so as to perform different processing. In the same HLR, the main number section and the standby number section can coexist, so the HLR realized according to this method can be used as the main use and the standby at the same time.

Since the backup HLR can obtain the user's dynamic information in real time, the information in the backup HLR is consistent with the actual status of the user. As long as the state of the standby number segment is set to the active state, the standby HLR will immediately operate in the active mode, realizing zero-time service takeover.

When the main HLR breaks down, through the HLR operation and maintenance interface, manually set the working state of the standby number segment in the standby HLR to the active state. business takeover.

If the active HLR fails, but because it is not found in time, the system will also experience service interruption at this time. However, the standby HLR can still obtain the user's status information normally during this period, so as long as the user in the standby number segment is set as the active state, then the standby HLR can take over the business immediately, and the service will return to normal immediately after taking over, without a transition process. However, for the currently used disaster recovery method, the dynamic information during this period will be lost, and after the standby HLR takes over the business, the business of some users will be abnormal.

After the active HLR returns to normal, the standby number segment in the standby HLR is restored to the standby state through the operation and maintenance interface, and the main HLR handles the user's business. If the main HLR is not implemented according to this method, the dynamic information of some users in the main HLR may have changed at this time, and the service of these users may appear abnormal after the main use takes over the business. If the main HLR is also implemented according to this method, then when the main HLR takes over the service again, no business abnormality may occur. The method is that after the main HLR returns to normal, set the main number segment to be taken over through the operation and maintenance interface. At this time, the main HLR runs in the backup mode, and the backup HLR still runs in the main mode. After running for a period of time, the dynamic information in the active and standby HLRs will be consistent, and then the standby HLR will return to the standby state, and the active HLR will be switched to the active state, thereby realizing a smooth transition of services.

Claims (3)

1, a kind of disaster recovery method of attaching position register of zero-time service take-over, in comprising business operation support system, active and standby network with HLR and signaling network, user data is divided into static data and dynamic data, static data is the user profile that can only make amendment by business operation support system or Operation ﹠ Maintenance System, the dynamic data user can make amendment or changes the data that change with the mobile phone SOT state of termination by mobile phone terminal operation, after networking is finished:

1) all being connected to the master all uses corresponding doubling to be connected to standby HLR with the signaling link of HLR;

2) import among the standby HLR with the user data among the HLR main, after this active and standbyly upgrade by business operation support system and guarantee its consistency with the static data among the HLR;

3) start standby HLR, accomplish real-time online, from signaling, obtain user's dynamic data;

4) when the master is broken down with HLR, the operating state of standby number segment among the standby HLR is arranged to the main state of using.

2, the disaster recovery method of the attaching position register of the described zero-time service take-over of claim 1, it is characterized in that, described business operation support system is upgraded also and is kept active and standby step with the static data unanimity among the HLR to be: business operation support system open an account, when cancellation, modification user signing contract information, send out message and give the active and standby HLR that uses, the user data among the information updating HLR that HLR sends according to business operation support system; If the user main use the number segment user, and this number segment is to lead to use state, and HLR is to VLR or SGSN synchrodata so; If the user main use the number segment user, and this number segment is by the adapter state, and HLR is to VLR or SGSN synchrodata so, the processing end; If the user is standby number segment user, and this number segment is in stand-by state, and HLR is not to VLR or SGSN synchrodata so, and processing finishes; If the user is standby number segment user, and this number segment is in and main uses state, and HLR is to VLR or SGSN synchrodata so.

3, the disaster recovery method of the attaching position register of the described zero-time service take-over of claim 1 is characterized in that, the described step that obtains dynamic data from signaling is:

If 3.1 signaling is initiated by the network entity that carries out Signalling exchange with HLR, when then receiving signaling: if mainly use the number segment user, and this number segment is in to lead and uses state, and HLR is according to this signaling of the flow processing of stipulating in the gsm protocol so; If the master uses the number segment user, and this number segment is in by the adapter state, influence user's multidate information as this signaling, HLR is according to signaling content modification user multidate information so, the gsm protocol regulation is followed in the modification of multidate information, this moment, HLR did not return any response, if signaling does not influence user's multidate information, HLR abandons this signaling so; If standby number segment user, and number segment is in and mainly uses state, and HLR is according to this signaling of the flow processing of stipulating in the gsm protocol so; If standby number segment user, and number segment is in stand-by state, influence user's multidate information as this signaling, HLR is according to signaling content modification user multidate information so, the gsm protocol regulation is followed in the modification of multidate information, this moment, HLR did not return any response, did not influence user's multidate information as signaling, and HLR abandons this signaling so;

If 3.2 signaling is initiatively initiated by this HLR, then: if main use the number segment user, and this number segment is in to lead and uses state, and HLR is according to this signaling of the flow processing of stipulating in the gsm protocol so; If main use the number segment user, and this number segment is in by the adapter state, and HLR does not handle this signaling so; If standby number segment user, and number segment is in and mainly uses state, and HLR is according to this signaling of the flow processing of stipulating in the gsm protocol so; If standby number segment user, and number segment is in stand-by state, influences user's multidate information as this signaling, and HLR does not handle this signaling so.

Images