CN100463547C - HLR calamity manipulation method - Google Patents
HLR calamity manipulation method Download PDFInfo
- Publication number
- CN100463547C CN100463547C CNB2005100337891A CN200510033789A CN100463547C CN 100463547 C CN100463547 C CN 100463547C CN B2005100337891 A CNB2005100337891 A CN B2005100337891A CN 200510033789 A CN200510033789 A CN 200510033789A CN 100463547 C CN100463547 C CN 100463547C
- Authority
- CN
- China
- Prior art keywords
- attaching position
- position register
- hlr
- disaster tolerance
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 14
- 230000011664 signaling Effects 0.000 claims description 24
- 230000004044 response Effects 0.000 claims description 13
- 230000004048 modification Effects 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 9
- 238000012546 transfer Methods 0.000 claims description 5
- 230000008676 import Effects 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims description 4
- 238000012423 maintenance Methods 0.000 claims description 4
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 230000004913 activation Effects 0.000 claims 1
- 238000003032 molecular docking Methods 0.000 claims 1
- 230000002159 abnormal effect Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000000151 deposition Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000003745 diagnosis Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
Images
Abstract
The invention relates to an allowance method of positioning register. The BOSS system is modified according to the service interface standard provided by allowance HLR; connecting the allowance HLR into seven signal network as the backup subsystem of each main HLR; operator via BOSS modifies the user data of main HLR and send same user data modifying operation to the allowance HLR; when the main HLR is abnormal, the signal switch can realize the management on the main HLR service by allowance HLR. The invention can clear the difference between the user-data memory formats of different factory HLR.
Description
Technical field:
The present invention relates to communication field, relate in particular to the disaster tolerance of HLR in the communication field (Home Location Register, attaching position register).
Background technology:
HLR is a core component of mobile communcations system, is used to deposit mobile subscriber's CAMEL-Subscription-Information.Continuous development along with mechanics of communication, the capacity of HLR equipment increases gradually, in case equipment occurs will bringing influence to a large number of users unusually, therefore the stable and reliability service of HLR has been subjected to the common concern of domestic and overseas operators, is the main hot issue that also becomes networking with HLR outfit redundancy HLR.
Though HLR equipment all is to develop according to the protocol specification of standard, the external interface with standard is realized in inside, has very big difference between each producer, and it also is like this depositing form for user data among the HLR.In the reality, for bigger operator of most operators, particularly network size, the HLR equipment of a plurality of producers is arranged all generally on the core net, if each HLR of producer can only provide the disaster tolerance function for the HLR equipment of oneself, the economy of redundancy HLR will obviously descend so.Therefore overcome the difference of different manufacturers HLR equipment, realize that disaster tolerance each other just seems extremely important.
Summary of the invention:
Problem to be solved by this invention is: solve main stationary problem with user signing contract information between HLR and redundancy HLR, especially overcome the difference of different manufacturers HLR storage of subscriber data form, realize the disaster tolerance of HLR equipment between different manufacturers.
Technical scheme of the present invention is:
1.1 BOSS (Business Operation Support System, business operation support system) system transforms according to the service handling interface specification that redundancy HLR provides, realization is docked with redundancy HLR, and the service handling of describing in support standard instruction, the BOSS system can be operated the user data in the redundancy HLR, and can initiate identical data modification to disaster tolerance after with the success of the data manipulation among the HLR and operate main as BOSS;
1.2 redundancy HLR is inserted No. 7 signaling network, and redundancy HLR is used the standby subsystem of HLR as each master by configuration;
1.3 the realization master is synchronous with user data in the attaching position register and the user data in the disaster tolerance attaching position register:
1.3.1 with the user data that has existed among the HLR, main utilize export function that user signing contract information is exported to the file of certain format with HLR to main, redundancy HLR is by import tool, the importing of the user profile in file redundancy HLR then;
1.3.2 all pass through the BOSS system synchronization to redundancy HLR with the follow-up user who increases newly of HLR with to the modification of original user signing contract information to main;
1.4 main with HLR when unusual, switch by signaling and to realize that redundancy HLR is to main adapter with the HLR business.
Further, the concrete grammar of step 1.3.2 is:
The operator sends to the BOSS system by counter and Adds User CAMEL-Subscription-Information or user signing contract information revised request;
The BOSS system receives and asks the back to initiate data increase or modification to main with HLR;
Main with HLR has revised behind the user data to the BOSS system echo should, if successfully then return success response, otherwise time failure response;
After response was received by the BOSS system, judging if success response is then initiated same user data to redundancy HLR increased or retouching operation this data sync EO;
Redundancy HLR increases or has revised behind the user data to echo to the BOSS system and answered;
The BOSS system receives that responding the back judges that redundancy HLR increases or whether the modification user data is successful, if get nowhere then retransmit operation, otherwise this data sync EO;
Further, the concrete grammar of step 1.4 can be:
When the master used the HLR system exception, the operator blocked main all signaling links with HLR, and activated all signaling links of redundancy HLR;
STP (SIGNALLING TRANSFER PORT, Signalling Transfer Point) and local MSC/VLR (the MOBILESWITCH CENTER of fault HLR, mobile switching centre/VISITOR LOCATION REGISTER, VLR Visitor Location Register) and SGSN (SERVING GPRS SUPPORT NODE, GPRS serving GPRS support node) switch on the redundancy HLR sending to the signaling of fault master with HLR;
The operator sends out MAP_RESET by the VLR/SGSN that may there be the user of redundancy HLR in fault HLR in the Operation and Maintenance interface, and force users is initiated the position to redundancy HLR and upgraded;
After VLR/SGSN received MAP_RESET request, it is unreliable that all customer data that belongs to fault HLR is designated as, in case these user's access networks after this, VLR/SGSN just initiatively initiates the position renewal to redundancy HLR;
Redundancy HLR is received the position updating request of VLR/SGSN, upgrades user's multidate information.
Adopt beneficial effect of the present invention very obvious:
Use the BOSS system to main data sync operation, eliminated the difference of storage of subscriber data form between different manufacturers HLR, realized the disaster tolerance of different manufacturers HLR equipment room with HLR and redundancy HLR;
Compare with other disaster recovery methods, main do not need to bear data sync work to redundancy HLR with HLR, therefore main handling property with HLR is not affected; The master does not need to do any transformation with HLR, thereby makes enforcement convenient;
The data sync of usual treatments B OSS of redundancy HLR, duty ratio is lower, and therefore a redundancy HLR can provide the disaster tolerance function for a plurality of HLR, and economy is than higher.
Description of drawings:
Fig. 1 is the general structure schematic diagram of disaster tolerance system.
Fig. 2 is the schematic diagram that a kind of typical redundancy HLR inserts No. 7 signaling network.
Fig. 3 is a typical B OSS system group network schematic diagram.
Embodiment:
Fig. 1 is the general structure schematic diagram of disaster tolerance system, comprises the business operation back-up system, and is main with HLR, redundancy HLR etc.
Main with HLR when unusual, redundancy HLR requires to connect that let it be is professional, so it need be linked in the signaling network, and Fig. 2 is the mode that typical redundancy HLR inserts No. 7 signaling network.For when the master uses the HLR fault, redundancy HLR can be taken over business as early as possible, and some network elements in the network need be revised configuration data.Configuration data is amended as follows:
1, the direct-connected STP of redundancy HLR is if support standby subsystem function, so by disposing redundancy HLR as each main standby subsystem with HLR;
2, for using direct-connected local MSC/VLR or the SGSN (Serving GPRS SupportNode, GPRS serving GPRS support node) of HLR, if support standby subsystem function, so by disposing redundancy HLR as the standby subsystem of master with HLR with the master.
The groundwork of redundancy HLR comprises two aspects, and one is to keep under usual situation and main data consistent with HLR, is exactly on the other hand when the master is unusual with HLR, switches by signaling and realizes main adapter with the HLR business.From these two aspects, introduce the specific embodiment of the present invention below.
At first introduction is main with the data sync between HLR and redundancy HLR, and this process comprises the main HLR of using to redundancy HLR cutover available data and the main data sync with HLR and redundancy HLR of BOSS maintenance, and is specific as follows:
1, for main with the user data that has existed among the HLR, mainly utilize export function that user signing contract information is exported to the file of certain format with HLR, redundancy HLR is by import tool, the importing of the user profile in file redundancy HLR then;
2, all pass through the BOSS system synchronization to redundancy HLR for main with the follow-up user who increases newly of HLR and to the modification of original user signing contract information.
Consulting among Fig. 3 the A landlord below, to revise a user signing contract information with HLR be that example describes the BOSS data synchronization process:
1) operator sends CAMEL-Subscription-Information by A ground counter to A ground BOSS system and revises request;
2) BOSS system in A ground receives that the request back is to A ground HLR initiation data modification;
3) A ground HLR revised behind the user data to A ground BOSS system echo should, successfully then return success response if revises, otherwise time failure response;
4) after response is received by BOSS system in A ground, judge that the master has revised success with user data among the HLR, then to BOSS center hair user data modify instruction, if the main HLR of using data modification is failed then do not sent to the BOSS center;
5) the mind-set redundancy HLR is initiated the user data retouching operation among the BOSS;
6) redundancy HLR has revised that make sound to the BOSS center behind the user data should;
7) the BOSS center receives that response back judges that redundancy HLR revises whether success of user data, if get nowhere then retransmit retouching operation, otherwise this data sync EO;
By above-mentioned steps, the master has realized with the user data in HLR and the redundancy HLR synchronously.
When the master uses the HLR fault, send to main signaling and can switch to redundancy HLR by the mode of automatic or manual with HLR.Consider that from secure context the service take-over process suggestion of redundancy HLR is set to manual mode.Manual business adapter step is as follows:
1) the main HLR system exception of using, business can't normal process; The operator determines that through diagnosis system can not recover in the short time; The operator blocks main all signaling links with HLR, and activates all signaling links of redundancy HLR;
2) because the master is blocked with the HLR signaling, STP and main Message Transfer Part (MTP) the process link detecting of using local MSC/VLR and the SGSN of HLR find that the master has been that signaling is unreachable with HLR, so switch on the redundancy HLR automatically to signaling;
3) because the simultaneous user's of BOSS system CAMEL-Subscription-Information, not synchronous with more user-dependent multidate informations, normal in order to guarantee user's called service, the VLR/SGSN that the operator makes redundancy HLR may exist to the user by the Operation and Maintenance interface sends out attaching position register and resets and make (MAP_RESET), and force users is initiated the position to redundancy HLR and upgraded;
4) after VLR/SGSN received MAP_RESET request, it is unreliable that all customer data that belongs to fault HLR is designated as, in case these user's access networks after this, VLR/SGSN just initiatively initiates the position renewal to redundancy HLR; 5) redundancy HLR is received the position updating request of VLR/SGSN, upgrades user's multidate information, thereby realizes main adapter with the HLR business.
Claims (3)
1. HLR calamity manipulation method comprises:
1.1 business operation support system is transformed according to the service handling interface specification that the disaster tolerance attaching position register provides, can realize itself and the docking of disaster tolerance attaching position register, and the service handling of describing in support standard instruction, can operate the user data in the disaster tolerance attaching position register;
1.2 the disaster tolerance attaching position register is inserted No. 7 signaling network, and the disaster tolerance attaching position register is used the standby subsystem of attaching position register as each master by configuration;
1.3 realize main with the user data in user data in the attaching position register and the disaster tolerance attaching position register synchronously: to leading with the user data that has existed in the attaching position register, the master utilizes export function user signing contract information to be exported to the file of predetermined format with attaching position register, the disaster tolerance attaching position register imports the disaster tolerance attaching position register to the user profile in the file by import tool then; To main be to be synchronized to the disaster tolerance attaching position register with the follow-up user who increases newly of attaching position register with to the modification of original user signing contract information by business operation support system;
1.4 main with attaching position register when unusual, switch by signaling and to realize that the disaster tolerance attaching position register is to main adapter with the attaching position register business.
2. the described HLR calamity manipulation method of claim 1 is characterized in that, the method that business operation support system is synchronized to the disaster tolerance attaching position register of passing through in the described step 1.3 is:
2.1 send to business operation support system by counter and to Add User CAMEL-Subscription-Information or user signing contract information revised request;
2.2 business operation support system receives that the request back increases or retouching operation with attaching position register initiation data to main;
2.3 main with attaching position register newly-increased or has revised behind the user data to business operation support system echo should, if successfully then return success response, otherwise time failure response;
After 2.4 business operation support system is received response, judge, if failure response this data sync EO then if success response then increases or modify instruction to business operation support system hair user data;
2.5 after business operation support system was received increase or modify instruction, initiating user data to the disaster tolerance attaching position register increased or retouching operation;
2.6 the disaster tolerance attaching position register increases or has revised behind the user data to make sound to business operation support system and answered;
2.7 business operation support system receives that responding the back judges that the disaster tolerance attaching position register increases or whether the modification user data is successful, if get nowhere then retransmit operation, otherwise this data sync EO.
3. the described HLR calamity manipulation method of claim 1 is characterized in that, the implementation method of described step 1.4 is:
When 3.1 the master uses the attaching position register system exception, main all signaling links of blocking-up, and all signaling links of activation disaster tolerance attaching position register with attaching position register;
3.2 signaling transfer point and master switch to signaling on the disaster tolerance attaching position register automatically with the local mobile switching center of attaching position register and the Message Transfer Part of GPRS serving GPRS support node;
3.3 the VLR Visitor Location Register/GPRS serving GPRS support node that the disaster tolerance attaching position register may be existed by the Operation and Maintenance interface to the user is sent out the attaching position register signaling that resets, force users is initiated the position to the disaster tolerance attaching position register and is upgraded;
3.4 VLR Visitor Location Register/GPRS serving GPRS support node receives that attaching position register resets after the order request, it is unreliable that all customer data that belongs to the fault attaching position register is designated as, in case just initiatively initiating the position to the disaster tolerance attaching position register, these user's access networks after this, VLR Visitor Location Register/GPRS serving GPRS support node upgrade;
3.5 the disaster tolerance attaching position register is received the position updating request of VLR Visitor Location Register/GPRS serving GPRS support node, upgrades user's multidate information.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100337891A CN100463547C (en) | 2005-03-24 | 2005-03-24 | HLR calamity manipulation method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100337891A CN100463547C (en) | 2005-03-24 | 2005-03-24 | HLR calamity manipulation method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1838811A CN1838811A (en) | 2006-09-27 |
| CN100463547C true CN100463547C (en) | 2009-02-18 |
Family
ID=37016037
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100337891A Expired - Fee Related CN100463547C (en) | 2005-03-24 | 2005-03-24 | HLR calamity manipulation method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100463547C (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101378329B (en) * | 2007-08-30 | 2011-06-22 | 阿里巴巴集团控股有限公司 | Distributed business operation support system and method for implementing distributed business |
| CN101754169B (en) * | 2008-12-02 | 2013-01-23 | 中兴通讯股份有限公司 | Service management method and system for received instructions of home location register |
| CN110602685B (en) * | 2019-08-27 | 2022-05-10 | 中国—东盟信息港股份有限公司 | Safe privacy number disaster recovery backup method for number position non-sensing switching |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6067454A (en) * | 1998-04-14 | 2000-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Mobile switching center restart recovery procedure |
| JP2000244964A (en) * | 1999-02-19 | 2000-09-08 | Fujitsu Ltd | Mobile communication system |
| CN1428969A (en) * | 2001-12-24 | 2003-07-09 | 华为技术有限公司 | Method for setting backup attaching position register |
| CN1568027A (en) * | 2003-06-24 | 2005-01-19 | 中兴通讯股份有限公司 | A method of disaster recovery for home location register (HLR) with zero-time service take-over |
-
2005
- 2005-03-24 CN CNB2005100337891A patent/CN100463547C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6067454A (en) * | 1998-04-14 | 2000-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Mobile switching center restart recovery procedure |
| JP2000244964A (en) * | 1999-02-19 | 2000-09-08 | Fujitsu Ltd | Mobile communication system |
| CN1428969A (en) * | 2001-12-24 | 2003-07-09 | 华为技术有限公司 | Method for setting backup attaching position register |
| CN1568027A (en) * | 2003-06-24 | 2005-01-19 | 中兴通讯股份有限公司 | A method of disaster recovery for home location register (HLR) with zero-time service take-over |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1838811A (en) | 2006-09-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6115463A (en) | Migration of subscriber data between home location registers of a telecommunications system | |
| CN100391289C (en) | Method of updating remote subsystem in mobile communication system | |
| CN101610533B (en) | Method and device for realizing backup switching of access controller | |
| CN102111790B (en) | Communication means based on base station control device group, Apparatus and system | |
| CN101729305A (en) | Method and system for automatically restoring fault, and control network element | |
| CN101247568A (en) | Data fault-tolerance system and method and intermediate equipment | |
| CN101150830B (en) | Software packet upgrade method and device | |
| CN100388805C (en) | Data disaster tolerance method for attaching location registor | |
| CN104618127A (en) | Master and standby storage node switching method and system | |
| WO2003056756A1 (en) | A method of setting backup home location register | |
| CN100463547C (en) | HLR calamity manipulation method | |
| WO2003063522A1 (en) | Standby mobile switching center | |
| CN100512168C (en) | Apparatus for connecting wireless network with at least one other network | |
| CN101540699A (en) | Method and device for realizing remote maintenance of network equipment | |
| CN101217293A (en) | Media operation trusteeship switching system and method | |
| CN101217405B (en) | SGSN backup method and communication system, communication device | |
| CN101188787A (en) | Disaster tolerance method and system for home register | |
| CN1204762C (en) | Redundant disaster method for realizing adscription of location registers throuth mobile communication operating system | |
| CN102571310B (en) | The disaster recovery method of Voice Mail Service and device | |
| CN101335702B (en) | Disaster recovery method of serving GPRS support node | |
| CN102143473B (en) | Processing method and device for radio link addition with cell update and communication system | |
| CN101304339B (en) | System and method for monitoring back machine in double-ascription network | |
| CN103593369A (en) | Inquiry and update method and processing system of HSS (home subscriber server) data | |
| CN1984448A (en) | Method and system for realizing mobile user data safety backup by distributed business | |
| CN1984474B (en) | Method and system for realizing mobile user data safety backup |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| ASS | Succession or assignment of patent right |
Owner name: BEIJING YUANXIN TECHNOLOGY CO., LTD. Free format text: FORMER OWNER: ZTE CORPORATION Effective date: 20141103 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518057 SHENZHEN, GUANGDONG PROVINCE TO: 100176 DAXING, BEIJING |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20141103 Address after: 408, -27, room 100176, building 8, building 1, Bei Sheng North Street, Beijing economic and Technological Development Zone, Beijing, China Patentee after: BEIJING YUANXIN TECHNOLOGY CO., LTD. Address before: 518057 Nanshan District, Guangdong high tech Industrial Park, science and Technology Industrial Park, ZTE building, block A, layer 6, layer Patentee before: ZTE Corporation |
|
| DD01 | Delivery of document by public notice | ||
| DD01 | Delivery of document by public notice |
Addressee: BEIJING YUANXIN TECHNOLOGY CO., LTD. Document name: Notification of Termination of Patent Right |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090218 Termination date: 20170324 |