KR100524740B1 - Management method for mobile network controller in mobile communication system - Google Patents

Abstract

The present invention relates to a method for managing a wireless network controller of a mobile communication system. In particular, the present invention relates to an RNC without modifying or replacing a software block or programmable language data (PLD) even when a mobile switching center (MSC) structure is changed to an integrated or separate type. The purpose is to make this possible. The present invention for this purpose is a first step of defining the MSC structure information in a specific field of the RNC (110 or 210) PLD, and the MSC type in the EMS (Element Management System) of the BSM (130 or 250) by analyzing the MMC of the administrator A second step of determining whether the change is made; and a third step of updating, by the BSM 130 or 250, MSC structure information defined in a specific field of the PLD to be appropriate for the MSC type if it is determined that the MSC type is changed. Configure to perform.

Description

MANAGEMENT METHOD FOR MOBILE NETWORK CONTROLLER IN MOBILE COMMUNICATION SYSTEM}

The present invention relates to a mobile communication system, and more particularly, to a method for managing a radio network controller (RNC).

A packet controller (PCP; hereinafter referred to as a PCP) mounted on a radio network controller (RNC) of a mobile communication system is a software block that handles signaling system No. 7 configuration information. It is mounted.

No.7 configuration information is a signal link that is a set of own station signal point information and station signal point information, signal link information for establishing a logical connection between the station signal point and the station signal point, and signal links from the station signal point to the same station signal point. Means information composed of set information.

The local signal point information includes a local point code for identifying itself in the signal network and a local signal point name for describing the local signal point so that the operator can easily recognize the local signal point.

The power signal point information includes a power point code for identifying the power in the signal network, a power signal name for explaining the power signal point for the operator to recognize the power, and routing information for providing a routing path from the RNC to the power. It consists of.

Signaling link is one of the physical ATM (Asynchronous Transfer Mode) links between the local station and the large station called VP / VC (Virtual Path / Virtual Channel), hereinafter VP / VC ) Is used to provide a logical path. And the signal link set is a set of signal link information directed to a specific power.

1 is a diagram illustrating a connection configuration between an RNC and a Mobile Switching Center (MSC), according to an embodiment of the prior art, as shown therein, between an RNC 110 and an MSC 120. Is configured to transmit the No. 7 configuration information over the signal link using the ATM resource VP / VC (7/31).

The MSC 120 is composed of an integrated MSC.

In the drawing, reference numeral 130 denotes a base station management (BSM) (or NMS: network management system) connected to the RNC 110 to control a base station (or a network).

Referring to the operation of one embodiment of the prior art as follows.

In the RNC 110 serving as the local signal point, the point code has a point code of 0x205 and the name RNC00. The MSC 120 serving as the power of the RNC 110 is an integrated type. It is assumed that 0x2000, Name is MSC, and Routing information is RNC-MSC Server.

Therefore, the signaling message from the RNC 110 to the MSC 120, which is a large power, has a point code that is its own signal point information and a point code that is the power information, and a signal link and an RNC-MSC having an ATM resource of 7/31. It is transmitted using routing information.

By the way, the current IMT-2000 system is equipped with an MSC in which the MSC server and the media gateway are integrated into one, but if R4 (Release 4) of 3GPP (Third Generation Partnership Project) is applied to the MSC, the MSC is integrated by the operator's choice. It may be configured as a separate or separate structure, that is, a structure in which an MSC is separated into an MSC server and a media gateway (Media GateWay).

Therefore, the RNC must manage No. 7 configuration information and PLD (Programmable Language Data) information differently according to the MSC type, that is, separate or integrated.

FIG. 2 is a connection diagram showing another embodiment of the prior art in which an integrated MSC is replaced with a separate MSC in FIG. 1.

In FIG. 2, the detachable MSC is a structure in which the integrated MSC 120 of FIG. 1 is logically divided into an MSC server 220 and a media gateway 230.

That is, in FIG. 2, the RNC 210 transmits a No. 7 signaling message to the MSC server 220 through a signal link using a VP / VC (7/32), which is an ATM resource, via a CAN 240, and transmits an ATM resource. And a No. 7 signaling message to the media gateway 230 via the signal link with the VP / VC 7/33.

Reference numeral 250 in the figure is a base station management (BSM) (or NMS: network management system) connected to the RNC 210 to control the base station (or network).

Referring to the operation of the other embodiment of the prior art as follows.

In the RNC 210 that is a local signal point, the point code has a point code of 0x205 and a name of RNC00. The counter signal point of the MSC server 220 has a point code of 0x2000, a name of MSC_Serve, and routing information of an RNC. Assume that you have a CAN-MSC Server.

Therefore, when transmitting a signaling message to the MSC server 220, which is a large country, the RNC 210 has a point code, which is national signal point information, and a point code, which is a country information, and a signal link and an RNC having an ATM resource of 7/32. -Routing information which is CAN-MSC Server is used.

In addition, it is assumed that the point code of the media gateway 230 is 0x3000, the name is Media GateWay, and the routing information is RNC-MediaGateWay.

Accordingly, when the RNC 210 transmits a signaling message to the media gateway 230, which is a large player, the RNC 210 has a point code, which is local signal point information, and a point code, which is a player information, and a signal link and an RNC-MediaGateway, which are 7/33 ATM resources. Use routing information.

That is, in the prior art, signal messages are exchanged between the own station and the large station using No. 7 configuration information as described above.

However, in the prior art, it can be seen that the RNC must manage different No. 7 configuration information to be processed in the software block according to the MSC type, i.e., integrated or detached, which is a large power. Because the information must be managed differently, changing the MSC type to integrated or detached requires modification and replacement of software blocks or programmable language data (PLD), which causes problems such as software inconsistencies and PLD inconsistencies within RNC. Let's do it.

Therefore, the prior art has a problem that the mobile communication system malfunctions due to software mismatch and PLD mismatch when the MSC type is changed to integrated or detached.

Accordingly, the present invention provides a method for managing a wireless network controller of a mobile communication system invented so that it can be matched with an RNC without modifying or replacing a software block or a PLD even when the MSC structure is changed to an integrated or separate type in order to improve the conventional problem. The purpose is to provide.

In order to achieve the above object, the present invention provides a method for managing a wireless network controller (RNC), the method comprising: defining MSC structure information in a specific field of a PLD, determining whether the MSC type is changed, and the MSC type above. If it is determined that the change of the MSC structure information characterized in that configured to perform the step of updating to suit the MSC type.

Whether or not the MSC type is changed is determined by the BSM (or NMS) by the administrator's MMC.

The MSC structure information is characterized by determining routing information among No. 7 configuration information.

That is, the present invention defines a specific field for managing the MSC structure information in the PLD of the PCP mounted in the RNC, and the NMS (Network Management System) or BSM (Base Station Management) according to the MSC structure change. By manipulating MMC (Man Machine Command) of MSC structure information and routing information according to it, the operator can manage the operation without having to replace software block or PLD.

The BSM may be configured to include an element management system (EMS).

Therefore, the present invention operates and manages No. 7 configuration information (routing information) in accordance with the structure of the MSC in the software block inside the PCP by the MMC such as MSC related creation / modification, so that the MSC structure changes in the prior art. Solve problems such as software inconsistencies and PLD inconsistencies caused by modifications and replacements of blocks or PLDs.

Hereinafter, the present invention will be described in detail with reference to the drawings.

The connection configuration of the RNC and the MSC for the embodiment of the present invention is the same as that of FIGS.

In the embodiment of the present invention, a process similar to the flowchart of FIGS. 3 and 4 is performed.

That is, according to the embodiment of the present invention, as shown in the operation flowchart of FIG. 3, the first step of defining MSC structure information in a specific field of the PLD inside the RNC 110 or 210 and the MMC of the manager are analyzed to determine the BSM. A second step of determining whether the MSC type is changed in the element management system (EMS) of 130 or 250; and if it is determined that the MSC type is changed, the BSM 130 or 250 sends information to the RNC 110 or 210; Transmits and updates the MSC structure information defined in a specific field of the PLD to be appropriate for the MSC type.

Whether to change the MSC type in the second step is performed by an MMC (Man Machine Command) of the administrator.

The PLD updating step of the third step may include a first step of inputting power information, a second step of analyzing the MSC type information and determining whether the MSC type is an integrated type or a separate type, as shown in the operation flowchart of FIG. 4; The third step of changing routing information defined in a specific field of the PLD to RNC-MSC if the MSC type is determined as integrated; and if the MSC type is determined as separate, whether the MSC type is an MSC server or a media gateway A fourth step of determining a second step; and a fifth step of changing routing information defined in a specific field of a PLD to an RNC-CAN-MSC server if the MSC server is determined in the fourth step; If it is determined, a sixth process of changing routing information defined in a specific field of the PLD to an RNC-Media Gateway is performed.

Referring to the operation and effect of the embodiment of the present invention configured as described above are as follows.

First, the BSM 130 or 250 determines whether the type of the MSC (mobile switching center) connected to the RNC 110 or 210 is changed.

Subsequently, when it is determined that the MSC type is changed by the MMC input of the manager, the BSM 130 or 250 transmits the MMC to the RNC 110 or 210 using the EMS, so that the MSC structure information defined in a specific field of the internal PLD, Update routing information.

Accordingly, in a subsequent operation, the PLD information provided in the RNC 110 or 210 and the corresponding software block recognize all subsequent MMCs according to the MSC type by referring to the MSC structure information included in a specific field of the updated PLD. This action will be performed.

Meanwhile, the PLD update process in the RNC 110 or 210 will be described below.

First, when an MSC is created / changed by the MMC input of the administrator, the RNC 110 or 210 checks OPC (Own Point Code) information input from the BSM (or NMS), and the MSC type currently generated / changed is separated. Determine if it is integrated or integrated.

At this time, if it is determined that the MSC type to be created / modified is an integrated type, the RNC 110 or 210 updates the PLD, that is, routing information of a specific field, to the RNC-MSC in accordance with the integrated software.

On the contrary, when the creation / change of the MSC is made, the MSC type is determined as a separate type, and the RNC 110 or 210 checks whether the MSC type is an MSC Server or a Media Gateway, and the software block operates according to the check result. Update routing information defined in a specific field. That is, if it is determined as an MSC server, the routing information is updated to the RNC-CAN-MSC Server, and if it is determined as a media gateway, the routing information is updated to the RNC-Media Gateway.

Therefore, in the embodiment of the present invention, even if the MSC structure is changed by the above process, the signal point which is No.7 configuration information of the MSC can be generated / modified without replacing / modifying the software block or PLD.

As described in detail above, the present invention can manage the PLD and the software block in response to the MSC structure change even without changing the MSC structure even if the MSC structure changes, so that the system does not cause a software block mismatch or a PLD mismatch as in the prior art. It can operate stably and also provides the administrator with convenience in operation management.

1 is a connection diagram between a conventional radio network controller (RNC) and an integrated MSC.

Figure 2 is a connection diagram between a conventional radio network controller (RNC) and a separate MSC.

3 is an operation flowchart showing a PLD update process in an embodiment of the present invention;

4 is a detailed operation flowchart of the PLD update process in FIG.

Explanation of symbols on the main parts of the drawings

110,210: RNC (wireless network controller) 120: MSC (mobile telephone switchboard)

130,250 BSM (Base Station Management Office) 220: MSC Server

230: Media Gateway 240: CAN

Claims (5)

In the mobile communication system management method, A first step of defining the MSC structure information in a specific field of the PLD; A second step of determining whether the MSC type is changed, If it is determined that the MSC type is changed, a third step of updating the MSC structure information to be suitable for the MSC type is performed. The third step includes a first process of determining MSC information from a BSM (or NMS), a second process of analyzing the MSC information to determine whether the MSC type is integrated or detachable, and wherein the MSC type is determined to be integrated. A third process of changing routing information defined in a specific field of the PLD to an RNC-MSC; a fourth process of determining whether the MSC type is an MSC server or a media gateway when the MSC type is determined to be detachable; A fifth step of changing routing information defined in a specific field of the PLD to an RNC-CAN-MSC server if the MSC server is determined in the fourth step; and a definition of a specific field of the PLD if the media gateway is determined in the fourth step And a sixth process of changing the routing information to the RNC-Media Gateway. The method of claim 1, wherein the second step determines whether the MSC type is changed in the BSM (or NMS) by the manager's MMC. The method of claim 1, wherein the third step includes the RNC checking MSC information from the BSM (or NMS) and updating the MSC structure information according to the MSC type. The method of claim 1 or 3, wherein the MSC structure information is A method for managing a wireless network controller in a mobile communication system, characterized in that the routing information is among No. 7 configuration information included in a specific field of the PLD. delete