CN100428829C - Base station node migration method and system thereof - Google Patents

Abstract

The invention relates to the field of mobile communication, and discloses a base station node relocation method and a system thereof, so that NodeB can be relocated efficiently and reliably. The invention divides the migration of NodeB into two stages of preparation and execution. In the preparation stage, export the relevant MML script for the migration from the RNC related to the base station node to be migrated, and extract the interface configuration data of NodeB from it for user modification; in the execution stage, by executing the modified MML script file, Realize the migration of NodeB. In the preparation stage, a backup database can also be established, and the MML script file can be modified and executed in the backup database to verify the legality of the data.

Description

Base station node migration method and system thereof

technical field

The invention relates to the field of mobile communication, in particular to the maintenance technology of the mobile network.

Background technique

With the rapid development of mobile communication services, the application of mobile data and multimedia communication will become more and more extensive. In the near future, it will even surpass traditional voice to become the main service carried by mobile communication. The traditional second-generation Global System for mobile communication (Global System for mobile Communication, referred to as "GSM") mobile communication network can no longer adapt to this new development trend. Therefore, GSM will gradually transition to the third-generation mobile communication system. Among them, the Wideband Code Division Multiple Access (WCDMA)/Universal Mobile Telecommunications System (Universal Mobile Telecommunications System) regulated by the 3rd Generation Partnership Project (3GPP for short), "UMTS" for short) has gradually developed into the main technology of the third-generation mobile communication with its continuous improvement and mature technical standards, flexible network architecture, smooth evolution mode, effective investment and many other advantages. Accepted by more and more mobile communication operators and equipment providers.

According to the relevant 3GPP agreement, the Terrestrial Radio Access Network (UMTS Terrestrial Radio Access Network, referred to as "UTRAN") of the WCDMA system consists of a base station node (also known as a B node, NodeB) and a radio network controller (Radio Network Controller, referred to as "RNC") )composition. Among them, the NodeB includes logic function modules such as the transmission interface unit and the base station control part. In UTRAN, RNC is in the control position, and is used to allocate and control the wireless resources of NodeB connected or related to it. NodeB completes the conversion of data flow between interfaces and also participates in part of wireless resource management. The main wireless resources in the NodeB are abstracted into local cells (LocalCell) and local cell groups (LocalCellGroup), and these resources will be used to establish cells (Cell) and access terminals. The interface between the NodeB and the RNC is an Iub interface, which is an open standard interface and supports the connection of devices of different equipment providers through the Iub interface. The standard protocol on the Iub interface includes the application protocol of the control plane, the NodeB Application Protocol (NodeB Application Protocol, referred to as "NBAP"). The main functions of the NBAP protocol are: sector configuration management; wireless link monitoring and management; common channel, dedicated channel measurement; system information management and so on. The Communication Control Port (CCP for short) of the Iub interface is an important channel for carrying NBAP signaling.

In the third-generation mobile communication network, users often need to adjust the position of NodeB in the network due to system load balancing, including the change of physical position or the adjustment of transmission link; starting from the relationship between NodeB and RNC, it can be divided into There are two cases of intra-RNC migration and inter-RNC migration. The migration of NodeB is shown in Figure 1. NodeB1 is relocated from RNC10 to RNC11. The dotted line represents the network before relocation, and the solid line represents the network after relocation. It is not difficult to find that when NodeB is relocated, the transmission links related to NodeB Resources such as resources, cells, and neighbor relationships need to be migrated.

Currently, users need to complete the migration of NodeB through the following operations:

1. Delete the cell and neighbor relationship on the NodeB;

2. Delete resources such as signaling links and control links associated with the NodeB;

3. Delete all permanent virtual circuit (Permanent Virtual Circuit, "PVC" for short) bearer links associated with the NodeB;

4. Delete the physical link of the NodeB;

5. Add the physical link of the NodeB;

6. Add all PVC bearer links associated with the NodeB;

7. Add resources such as signaling links and control links associated with the NodeB;

8. Add the cell and neighbor relationship on the NodeB.

It can be seen that in the actual migration process of NodeB, a large amount of data related to NodeB needs to be modified (the Iub interface protocol stack between NodeB and RNC is shown in Figure 2), including physical link number, cell location area, routing area , service area setting, cell neighbor relationship, etc., and involves the change of multiple RNC configuration data. Therefore, if the user uses the existing Man-Machine Language (MML) commands to manually implement the above-mentioned migration plan, the difficulty and risk are very high. Familiar, and once a manual operation error occurs during the relocation process, it is difficult to return to the initial state; and the entire relocation time will be very long, which will have a considerable impact on the business of the entire network; it is even more difficult to operate in the scenario of batch migration of NodeB implement.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a base station node relocation method and its system, so that NodeB can be relocated efficiently and reliably.

To achieve the above object, the present invention provides a base station node migration method, comprising the following steps:

The network side derives a script related to the migration from the radio network controller related to the base station node to be migrated, and modifies the script according to the information input by the user;

The network side changes the configuration of the radio network controller by executing the modified script to complete the migration of the base station node.

Among them, the following steps are also included:

The network side establishes a backup database of the current system database, modifies the script in the backup database, and executes the modified script, if the modified script is executed, the new interface configuration data of the base station node If it is correct, execute the modified script in the current system database to migrate the base station node.

In addition, in the method, if the new interface configuration data of the base station node is incorrect after the modified script is executed, the user is notified to re-input relevant information, and the derived The relevant scripts for the migration described above are modified.

In addition, in the method, the network side modifies the exported related scripts for the migration according to the information input by the user in the following manner:

The network side presets replacement rules;

The network side replaces the content satisfying the replacement rule according to the information input by the user.

In addition, in described method, also comprise following steps:

If the network side needs to perform the migration on at least two base station nodes, then migrate all the base station nodes at one time, or,

The base station nodes are migrated one by one, and after each base station node is migrated, it is checked whether the migration process is correct, and if so, the next base station node is migrated.

In addition, in the method, the script is a man-machine language script, and the information input by the user is the new interface configuration data of the base station node.

In addition, in the method, the relevant radio network controller includes one of the following or any combination thereof:

A source radio network controller, a radio network controller adjacent to the source radio network controller, a target radio network controller, and a radio network controller adjacent to the target radio network controller.

In addition, in the method, the network side derives relevant scripts for performing the migration from the radio network controller related to the base station node to be migrated according to the relational object model.

The present invention also provides a base station node migration system, which includes a base station node to be migrated and a wireless network controller related to the base station node, and also includes:

An export module, configured to export a related script for performing the migration from the related wireless network controller;

A modification module, configured to modify the script exported by the export module according to the information input by the user to generate a new script;

An executing module, configured to execute the new script modified by the modifying module to change the configuration of the radio network controller and complete the migration of the base station node.

Wherein, the system also includes:

A backup establishment module is used to establish a backup database of the current system database;

The modifying module modifies the script in the backup database established by the backup establishing module, and the executing module executes the modified script in the backup database, if executed by the executing module, the If the new interface configuration data of the base station node is correct, the execution module executes the modified script in the current system database to migrate the base station node.

In addition, in the system, the modification module replaces the content satisfying the preset replacement rules according to the information input by the user.

By comparison, it can be found that the main difference between the technical solution of the present invention and the prior art is that the relevant MML script for the migration is derived from the RNC related to the base station node to be migrated, and the interface configuration data of NodeB is extracted therefrom for the user Modify and generate a new MML script, and implement the migration of NodeB by executing the new MML script file after modification. In essence, the migration of base station nodes is divided into the preparation stage and the execution stage. The main work in the preparation stage is to generate correct scripts, but it does not make any changes to the actual configuration in the network. It is executed once in the execution stage. The method of modifying the configuration one by one in the network simplifies the manual operation, improves the reliability and security of the NodeB migration process, and further reduces the impact of the NodeB migration process on the system.

In the preparation stage, you can also modify the MML script file in the established backup database and execute the modified MML script file. If the new interface configuration data of NodeB is correct, execute the modified MML script file in the current system database document. Avoid the situation that the system cannot be rolled back due to manual errors during the migration process, and first modify and execute the MML script file in the backup database, and directly execute the correct MML script file after modification in the system database, to a greater extent This not only greatly simplifies the operation of batch migration of NodeBs, but also further improves the reliability and security of the NodeB migration process, and reduces the impact of the NodeB migration process on the system.

The replacement rules are set in advance, and the exported MML script files are modified according to the new interface configuration data input by the user in combination with the replacement rules, which facilitates the migration between different versions and reduces the coupling degree of the business.

Description of drawings

FIG. 1 is a schematic diagram of NodeB migration in the prior art;

Fig. 2 is the schematic diagram of Iub interface protocol stack in the prior art;

Fig. 3 is a flowchart of a NodeB migration method according to the first embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings.

The core of the present invention is to derive the relevant MML script for the migration from the RNC related to the NodeB to be migrated, and extract the interface configuration data of the NodeB therefrom for user modification. Modify the interface configuration data of the NodeB in the established backup database according to the information input by the user, and execute the modified MML script in the backup database. If the new interface configuration data of NodeB is correct, execute the modified MML script file in the current system database; Re-modify the interface configuration data of the NodeB.

The core of the present invention has been briefly described above, and the NodeB migration method of the first embodiment of the present invention will be described in detail below based on this principle.

As shown in FIG. 3, in step 301, the network side establishes a backup database of the current system database.

Next, enter step 302, the network side derives the MML script related to the NodeB migration from the relevant RNC, and extracts the interface configuration data of the NodeB therefrom. Since the NodeB relocation process involves multiple RNCs, such as the source RNC, the target RNC, the RNC adjacent to the source RNC, and the RNC adjacent to the target RNC, the network side in this embodiment is a network element management system (Element Management System) , referred to as "EMS") level network entity.

Specifically, the network side derives the MML script involved in the NodeB that currently needs to be migrated from the source RNC, the RNC adjacent to the source RNC, the target RNC, and the RNC adjacent to the target RNC according to the relationship object model, and according to the derived MML script The script automatically generates a NodeB interface configuration data list for users to modify. In practical applications, the data volume of the MML script exported from the relevant RNC is very large, but the data that needs to be modified by the user is relatively small, so it is very convenient to extract the interface configuration data of NodeB from the exported script for the user to modify user actions.

If multiple NodeBs need to be migrated, the network side can also generate multiple NodeB interface data for users to modify.

Next, in step 303, the user inputs the migration information of the NodeB. Specifically, the user chooses to migrate the list of NodeBs and the information of the RNC where the NodeB is located. If the NodeB to be migrated is from one RNC to another RNC, since the cell attribute will change during the migration process, the user also needs to input the target RNC information and neighboring RNC information of the NodeB.

Next, enter step 304, the network side modifies the MML script exported from the relevant RNC in the backup database according to the information input by the user and executes the modified MML script. Specifically, the network side presets the replacement rules, replaces the content satisfying the replacement rules in the backup database according to the new NodeB interface configuration data input by the user, modifies the NodeB interface configuration data, and generates a new MML script. The specific replacement can be divided into two situations, one is direct replacement according to the change of interface data, which is relatively simple; the other is conditional replacement, such as the relationship between adjacent cells. For example, when the type of the cell object changes and becomes an adjacent RNC cell, it needs to be replaced conditionally according to the replacement rule. The pre-set replacement rules on the network side are mainly custom rules for parameter replacement, which define how to generate new MML scripts based on interface parameters input by users, so as to avoid the coupling of tools and network element versions, thus facilitating the communication between different versions. Migrated and reduced business coupling.

Then, the newly generated MML script is executed in the established backup database, that is, the MML script modified according to the information input by the user is executed in the backup database. During the execution process, the processing of the neighboring RNC of the NodeB and the target RNC are different. For the neighboring RNC, it is necessary to delete all the relocated cell-related data first and then add it again; for the target RNC, in addition to first deleting all the relocated cell-related data and then adding it again, it is also necessary to add the relevant data of the relocated cell. In addition, Also pay attention to the order of configuration.

Next, enter step 305, the network side judges whether the new interface configuration data of the NodeB is correct. Specifically, after the network side executes the newly generated MML script in the backup database, it is judged whether the new interface configuration data of the NodeB to be migrated is correct, if correct, then enter step 307, otherwise, it indicates that the interface configuration data of the NodeB is wrong , go to step 306.

In step 306, the network side notifies the user to re-input the new interface configuration data of the NodeB, and re-modifies the MML script according to the user's input. Specifically, similar to step 304, the network side replaces the content satisfying the replacement rules in the backup database according to the new interface configuration data of the NodeB re-input by the user, re-modifies the interface configuration data of the NodeB, and generates a new MML script , and then execute the newly generated MML script in the backup database, that is, the MML script modified according to the information re-input by the user. After completing this step, return to step 305 to determine whether the new interface configuration data of the NodeB is correct.

It can be seen that the network side establishes the backup database of the current system database, modifies and executes the MML script in the backup database, to verify the correctness of the NodeB interface configuration data, and supports the rollback operation when the NodeB interface configuration data is wrong. It avoids the situation that the system cannot be rolled back due to manual operation errors during the migration process.

If the new interface configuration data of the NodeB to be migrated is correct, go to step 307, and the network side executes the newly generated MML script in the current system database, that is, the MML script modified according to the information input by the user. The network side changes the configuration of the RNC of the NodeB by executing the modified MML script to complete the migration of the NodeB. Of course, even if the new interface configuration data of the NodeB to be migrated is correct, the user can also decide not to migrate the NodeB, that is, not to enter this step, but in this embodiment, only discussing the general situation, when the user does not change the migration decision of the NodeB The operation process performed.

It is worth mentioning that if there are multiple NodeBs that need to be migrated, the MML scripts are executed on each RNC in sequence according to the order in which the NodeBs are imported to complete the data modification of each NodeB, and all NodeBs are migrated at one time.

It is not difficult to find that this embodiment essentially divides the migration of the NodeB into a preparation phase and an execution phase. Step 301 to step 306 is the preparation stage, the main work in the preparation stage is to generate the correct script, but does not make any changes to the actual configuration in the network; step 307 is the execution stage, in the execution stage, the modified MML is executed once Compared with the method of modifying the configuration one by one in the network, the script simplifies the manual operation, improves the reliability and security of the NodeB migration process, and reduces the impact of the NodeB migration process on the system. Moreover, because the network side first modifies and executes the MML script file in the backup database, the correct MML script file after modification is directly executed in the system database, which greatly shortens the migration time of NodeBs and makes it possible to realize the batch migration of NodeBs , further improving the reliability and security of the NodeB migration process, and reducing the impact of the NodeB migration process on the system.

The NodeB migration method of the second embodiment of the present invention is substantially the same as that of the first embodiment, the only difference being that in the first embodiment, if there are multiple NodeBs to be migrated, all NodeBs are migrated at once. However, in this embodiment, if there are multiple NodeBs to be migrated, the NodeBs are migrated one by one. After completing the migration of each NodeB, it is checked whether the migration process is correct. If so, the next NodeB is migrated.

In the third embodiment of the present invention, the NodeB migration system includes the NodeB to be migrated and the RNC related to the NodeB; the export module is used to export the relevant scripts for the NodeB migration from the relevant RNC; information to modify the script exported by the export module; the execution module is used to execute the script modified by the modification module to change the RNC configuration of the NodeB and complete the migration of the NodeB; and the backup establishment module is used to establish the current system The backup database for the database.

Specifically, the modification module modifies the script exported by the export module according to the information input by the user and the preset replacement rules in the backup database established by the backup establishment module, and the execution module executes the modified script in the backup database. If the script is executed by the execution module and the new interface configuration data of the NodeB is correct, then the execution module executes the modified script in the current system database, changes the RNC configuration of the NodeB, and completes the migration of the NodeB. By dividing the migration of the base station node into the preparation phase and the execution phase, the correct script is generated in the preparation phase, but does not make any changes to the actual configuration in the network, and is executed at one time in the execution phase. The method simplifies the manual operation, improves the reliability and security of the NodeB migration process, shortens the NodeB migration time to a large extent, and reduces the impact of the NodeB migration process on the system.

Although the present invention has been illustrated and described with reference to certain preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the present invention. The spirit and scope of the invention.

Claims (11)

1. a base station node emigration method is characterized in that, comprises following steps:

Network side is derived the associated script of carrying out described migration from the radio network controller relevant with the base-station node of need migration, and according to the information of user's input this script is made amendment;

Network side is finished the migration to described base-station node by carrying out the configuration that described amended script changes described radio network controller.

2. base station node emigration method according to claim 1 is characterized in that, also comprises following steps:

Described network side is set up the backup database of current system database, in this backup database, revise described script according to the information of described user's input, and carry out described amended script, if it is correct that described amended script is performed the new interface configuration data of the described base-station node in back, then in current system database, carry out described amended script again, described base-station node is moved.

3. base station node emigration method according to claim 2, it is characterized in that, after if described amended script is performed, the new interface configuration data of described base-station node is incorrect, then notify the user to re-enter relevant information, and according to the information of user's input the associated script of carrying out described migration of described derivation is made amendment again.

4. base station node emigration method according to claim 1 is characterized in that, described network side is made amendment to the associated script of carrying out described migration of described derivation according to the information of user's input in the following manner:

Described network side sets in advance Substitution Rules;

Described network side is replaced the content that satisfies described Substitution Rules according to the information of user's input.

5. according to each described base station node emigration method in the claim 1 to 4, it is characterized in that, also comprise following steps:

If described network side need carry out described migration at least two base-station nodes, the described base-station node that then disposable migration is all, perhaps,

Move base-station node one by one, whenever finish the migration of a base-station node after this transition process of check whether correct, if then carry out the migration of next base-station node again.

6. base station node emigration method according to claim 5 is characterized in that, described script is man-machine language scripts, and the information of described user's input is the new interface configuration data of described base-station node.

7. base station node emigration method according to claim 5 is characterized in that, described relevant radio network controller comprises one of following or its combination in any:

Source radio network controller, radio network controller, target radio network controller and with the target radio network controller adjacent radio network controller adjacent with source radio network controller.

8. base station node emigration method according to claim 5 is characterized in that, described network side is derived the associated script of carrying out described migration according to the relationship object model from the radio network controller relevant with the base-station node of need migration.

9. a base station node emigration system comprises the base-station node and the radio network controller relevant with this base-station node that need migration, it is characterized in that, also comprises:

Derive module, be used for deriving the associated script of carrying out described migration from described relevant radio network controller;

Modified module is used for according to the information of user's input the script that described derivation module is derived being made amendment, and generates new script;

Executive Module is used to carry out the configuration of changing described radio network controller through the amended new script of described modified module, finishes the migration to described base-station node.

10. base station node emigration according to claim 9 system is characterized in that described system also comprises:

Module is set up in backup, is used to set up the backup database of current system database;

Described modified module is set up in the backup database that module sets up in described backup and is revised described script, and in this backup database, carry out described amended script by described Executive Module, if after described Executive Module is carried out, the new interface configuration data of described base-station node is correct, then described Executive Module is carried out described amended script again in current system database, described base-station node is moved.

11. base station node emigration according to claim 9 system is characterized in that, described modified module is replaced the content that satisfies the Substitution Rules that set in advance according to the information of user's input.

Images