f 106157666

6 RNC OM Subsystem

About This Chapter

The RNC OM subsystem is responsible for the operation and maintenance of the RNC.

6.1 Components of the RNC OM SubsystemThe RNC OM subsystem consists of the LMT, OMUa boards, SCUa boards, and OM moduleson other boards.

6.2 Working Principles of the RNC OM SubsystemThe RNC OM subsystem works in dual-plane mode through the OM network of the RNC.

6.3 RNC OM FunctionsThe RNC OM functions enable routine and emergency maintenance of the RNC.

6.4 RNC Active/Standby WorkspacesRNC active/standby workspaces consist of active/standby workspaces of the BAM and those ofFAM boards.

6.5 RNC Authority ManagementRNC authority management is performed to identify the user and define the authority of the user.

6.6 RNC Log ManagementRNC log management enables you to query the information about the operation and running ofthe RNC, thus facilitating fault analysis and location.

6.7 RNC Configuration ManagementRNC configuration management enables configuration and management of RNC data on theOM console (LMT or M2000).

6.8 RNC Performance ManagementRNC performance management enables the RNC to collect performance data.

6.9 RNC Alarm ManagementRNC alarm management facilitates you to monitor the running state of the RNC and informsyou of faults in real time so that you can take measures in time.

6.10 RNC Loading ManagementRNC loading management enables you to manage the process of loading program and data filesonto boards after the FAM boards (or subracks) start or restart.

RNCProduct Description 6 RNC OM Subsystem

Issue 02 (2007-08-15) Huawei Technologies Proprietary 6-1

6.11 BOOTP and DHCP on the Iub InterfaceThe RNC and NodeB support the BOOTP and DHCP functions. By the BOOTP or DHCPfunction, a NodeB can automatically get an IP address from an RNC and create an OM channelbetween the NodeB and the RNC. The BOOTP and DHCP functions are applicable to ATM andIP transport on the Iub interface respectively.

6.12 RNC Upgrade ManagementRNC upgrade refers to a process where the RNC is upgraded to a later version.

6 RNC OM SubsystemRNC

Product Description

6-2 Huawei Technologies Proprietary Issue 02 (2007-08-15)

6.1 Components of the RNC OM SubsystemThe RNC OM subsystem consists of the LMT, OMUa boards, SCUa boards, and OM moduleson other boards.

Figure 6-1 shows the components and physical connections of the RNC OM subsystem.

Figure 6-1 Components and physical connections of the RNC OM subsystem

NOTE

The RNC OM subsystem covers relevant modules on all boards of the RNC. Figure 6-1 shows only someof the boards.

LMT

The LMT is a computer installed with Huawei Local Maintenance Terminal software. It runsunder the Windows XP Professional operating system. The RNC can be configured with one ormore LMTs. The LMT is connected to the OMUa directly or through the hub and to the alarmbox through a serial cable.

OMUa Board

The OMUa board is the Back Administration Module (BAM) of the RNC. The OMUa boardsare connected to external devices through Ethernet cables.

The OMUa board serves as a bridge between Front Administration Module (FAM) and BAMof the RNC. Based on the OMUa board, the OM network of the RNC is divided into the followingnetworks:

l Internal network: serves the communication between the OMUa and the RNC host.



l External network: serves the communication between the OMUa board and the externaldevice, such as the OM terminal LMT or M2000.

NOTE

The RNC can be configured with one or two OMUa boards. In the latter case, the two boards work inactive/standby mode.

SCUa BoardThe SCUa is the switching and control board of the RNC. It is responsible for OM of its housingRSS subrack or RBS subrack. A subrack can be configured with two SCUa boards. In this case,the two boards work in active/standby mode.

The SCUa board performs OM on other boards in the same subrack through the backplanechannels. The SCUa boards in the RSS are connected to the SCUa boards in the RBSs throughEthernet cables.

NOTE

For details about the switching function of the SCUa board, refer to 3.2 Components of the RNCSwitching Subsystem.

6.2 Working Principles of the RNC OM SubsystemThe RNC OM subsystem works in dual-plane mode through the OM network of the RNC.

6.2.1 RNC OM SubnetsThe RNC OM network is divided into the external network, internal network, RSS network,RSS-RBS network, and RBS network. Each subnet is responsible for certain functions.

6.2.2 RNC OM Dual PlanesThe RNC adopts the OM dual-plane design to guarantee proper operation and maintenance inthe case of single-point failure.

6.2.1 RNC OM SubnetsThe RNC OM network is divided into the external network, internal network, RSS network,RSS-RBS network, and RBS network. Each subnet is responsible for certain functions.

Figure 6-2 shows the structure of the RNC OM subsystem.


Product Description


Figure 6-2 Structure of the RNC OM subsystem

NOTE

The RINT in the figure refers to the Iu/Iur/Iub interface board. You can choose to use different interfaceboards based on the requirements.

External NetworkThe external network refers to the network between the OMUa board and the OM console (LMTor M2000). The external network provides the interface for the OM console to access the OMsubsystem.

Internal NetworkThe internal network refers to the network between the OMUa board and the SCUa board in theRSS subrack. The internal network provides a bridge for the communication between the OMUaand the FAM.

RSS NetworkThe RSS network refers to the OM network between the SCUa board in the RSS subrack andthe other boards in the same subrack. The backplane in the RSS subrack is used to connectentities on this network.



RSS-RBS NetworkThe RSS-RBS network refers to the network between the SCUa board in the RSS subrack andthe SCUa in each RBS subrack. The connections between the SCUa board in the RSS subrackand the SCUa board in each RBS subrack through Ethernet cables comprise the RSS-RBSnetwork.

Through this network, the RNC can transmit the OM information to the SCUa board in eachRBS subrack through the SCUa board in the RSS subrack.

RBS NetworkThe RBS network refers to the OM network between the SCUa board in an RBS subrack andthe other boards in the same subrack. The backplane in the RBS subrack is used to connectentities on this network.

6.2.2 RNC OM Dual PlanesThe RNC adopts the OM dual-plane design to guarantee proper operation and maintenance inthe case of single-point failure.

The RNC OM subsystem adopts the dual-plane design, as shown in Figure 6-3.

Figure 6-3 OM dual planes

This design is realized by the hardware that works in redundancy mode. When the active part isfaulty but the standby part works properly, the active and standby parts can be switched overautomatically to guarantee proper working of the OM channel. The involved hardware is asfollows:l Active/Standby OMUa boards (if two OMUa boards are configured)


Product Description


l Active/Standby SCUa boards in the RSS subrack

l Active/Standby SCUa boards in an RBS subrack

The active/standby OMUa boards use one external virtual IP address when communicating withthe LMT or M2000 and use one internal virtual IP address when communicating with the SCUaboard. As shown in Figure 6-3, if the active OMUa board fails but the standby one worksproperly, the active and standby OMUa boards are switched over automatically. The standbyOMUa board takes the role of the active OMUa board to perform OM for the RNC. The internaland external virtual IP addresses remain unchanged. Thus, the proper communication betweenthe internal and external networks of the RNC is guaranteed.

6.3 RNC OM FunctionsThe RNC OM functions enable routine and emergency maintenance of the RNC.

The RNC has powerful OM functions, including authority management, log management,configuration management, performance management, alarm management, loadingmanagement, and upgrade management.

The OM software of the RNC can perform all-round management and maintenance of the RNC.

6.4 RNC Active/Standby WorkspacesRNC active/standby workspaces consist of active/standby workspaces of the BAM and those ofFAM boards.

6.4.1 Active/Standby Workspaces of the BAMThe active/standby workspaces of the BAM, that is, active/standby workspaces of the OMUaboard, are applied to upgrade and rollback of BAM and RNC versions, thus enabling quickswitching between versions.

6.4.2 Active/Standby Workspaces of RNC FAM BoardsRNC FAM boards refer to all the boards except the OMUa board. The active/standby workspacesof FAM boards are applied to file loading for the FAM boards, thus speeding up version upgradeand rollback.

6.4.1 Active/Standby Workspaces of the BAMThe active/standby workspaces of the BAM, that is, active/standby workspaces of the OMUaboard, are applied to upgrade and rollback of BAM and RNC versions, thus enabling quickswitching between versions.

Concept of BAM Active/Standby Workspaces

The active/standby workspaces of the BAM refer to the active and standby workspaces in theBAM divided to store different version files.

The active/standby workspaces are a relative concept. The active/standby relationship dependson the running version. The workspace that stores the running BAM version files is the activeworkspace, and the other is the standby workspace.



Working Principle of BAM Active/Standby WorkspacesThe BAM version upgrade process is as follows:

1. The standby workspace of the active BAM is upgraded to a new version.2. The standby workspace of the standby BAM is synchronized with the standby workspace

of the active BAM.3. The active and standby workspaces of the active BAM switch over. The standby workspace

that stores the new version of files becomes active, and the other workspace becomesstandby.

4. The active BAM runs the upgraded version.5. The active and standby workspaces of the standby BAM switch over to ensure that the

versions of the workspaces are consistent with those of the active BAM.6. The BAM version upgrade ends.

After the BAM version is upgraded, it can be rolled back as required. The version rollbackprocess is as follows:

1. The active and standby workspaces of the active BAM switch over. The running versionof the active BAM is rolled back to the pre-upgrade version.

2. The active BAM runs the pre-upgrade version.3. The active and standby workspaces of the standby BAM switch over to ensure that the

versions of the workspaces are consistent with those of the active BAM.4. The BAM version rollback ends.

During the switchover between the BAM active and standby workspaces, the OM of the BAMis interrupted for about one minute.

Relationship Between Intra-BAM Active and Standby WorkspacesThe active workspace of the BAM is independent of the standby workspace, or the other wayround. The operations in the active workspace do not change any information in the standbyworkspace.

Relationship Between Inter-BAM Active and Standby WorkspacesThe active and standby workspaces of the active BAM correspond to the active and standbyworkspaces of the standby BAM respectively. Between the active and standby BAMs, the filesin the active workspaces are automatically synchronized in real time, but those in the standbyworkspaces need to be synchronized manually through an MML command.

NOTE

The SYN BAMAREA command can be used to manually synchronize the standby workspaces betweenthe active and standby BAMs.

Relationship Between the Active/Standby Workspaces of FAM Boards and theActive/Standby Workspaces of the BAM

On the active workspaces of the FAM boards, files can be loaded from only the active workspaceof the BAM. On the standby workspaces of the FAM boards, files can be loaded from only thestandby workspace of the BAM. When the FAM boards are loaded, the active and standbyworkspaces of the FAM boards can be synchronized with the active and standby workspaces ofthe BAM respectively.


Product Description


NOTE

l The SYN BRDAREA command can be used to manually synchronize the active and standbyworkspaces of FAM boards with those of the BAM.

l The LOD BRD command can be used to forcibly load program files and data files of FAM boardsfrom the BAM and write the program files and data files to the active or standby workspaces of FAMboards.

6.4.2 Active/Standby Workspaces of RNC FAM BoardsRNC FAM boards refer to all the boards except the OMUa board. The active/standby workspacesof FAM boards are applied to file loading for the FAM boards, thus speeding up version upgradeand rollback.

Concept of FAM Board Active/Standby Workspaces

The active/standby workspaces of FAM boards refer to the active and standby workspaces inthe board flash memory divided to store program, data, and patch files for different versions.

The active/standby workspaces are a relative concept. The active/standby relationship dependson the running version. The workspace that stores the running version files of a board is theactive workspace, and the other is the standby workspace.

Working Principles of FAM Board Active/Standby Workspaces

Before loading program and data files, FAM boards choose the loading mode according to theloading control parameter. For details about loading RNC FAM boards, refer to 6.10 RNCLoading Management.

Relationship Between Intra-Board Active and Standby Workspaces

The active workspace of a FAM board is independent of the standby workspace of the sameboard, or the other way round. The operations in the active workspace do not change anyinformation in the standby workspace.

Relationship Between Inter-Board Active and Standby Workspaces

The active and standby workspaces of an active FAM board are independent of those of theassociated standby FAM board, or the other way round. The operations in the workspaces of theactive board do not change any information in the workspaces of the standby board.

Relationship Between the Active/Standby Workspaces of FAM Boards and theActive/Standby Workspaces of the BAM

On the active workspaces of the FAM boards, files can be loaded from only the active workspaceof the BAM. On the standby workspaces of the FAM boards, files can be loaded from only thestandby workspace of the BAM. When the FAM boards are loaded, the active and standbyworkspaces of the FAM boards can be synchronized with the active and standby workspaces ofthe BAM respectively.



NOTE

l The SYN BRDAREA command can be used to manually synchronize the active and standbyworkspaces of FAM boards with those of the BAM.

l The LOD BRD command can be used to forcibly load program files and data files of FAM boardsfrom the BAM and write the program files and data files to the active or standby workspaces of FAMboards.

6.5 RNC Authority ManagementRNC authority management is performed to identify the user and define the authority of the user.

The RNC supports multi-user operation. It performs hierarchical authority management for usersto ensure security. In this mode, the RNC provides multiple authority levels, each of which isconfigured for a type of operator. To log in to the RNC OM subsystem through the LMT, a usermust enter the correct user name and password, through which the RNC identifies the user.

User TypesThe users of the RNC are of the two types: local user and EMS user. For details, refer to RNCLMT User Types.

Command GroupsThe RNC provides 32 command groups: G_0 to G_31. Each command group contains severalMML commands or binary commands. For details, refer to RNC Command Groups.

6.6 RNC Log ManagementRNC log management enables you to query the information about the operation and running ofthe RNC, thus facilitating fault analysis and location.

The logs of the RNC are of three types: operation logs, running logs, and security logs.

Operation LogsOperation logs refer to the operation data saved in the BAM database in real time. The logmanagement module in the BAM records all the operations performed on the RNC. It supportsacquisition and deletion of logs.

Running LogsRunning logs refer to the information recorded in the RNC about the running of the RNC host.

Security LogsSecurity logs refer to security-related events recorded in the RNC. These events include userlogin, user management, and user authentication.

6.7 RNC Configuration ManagementRNC configuration management enables configuration and management of RNC data on theOM console (LMT or M2000).


Product Description


6.7.1 RNC Online and Offline StatesThe RNC can be in either online or offline data configuration state.

6.7.2 RNC Data Configuration ModesThe RNC supports three data configuration modes: online configuration, offline configuration,and dynamic batch configuration.

6.7.3 RNC Data Configuration Right ManagementRNC data configuration right management enables only one user to perform RNC dataconfiguration on only one configuration console at a time. The configuration console may bethe LMT or the M2000.

6.7.4 RNC Data Configuration RollbackRNC data configuration rollback is performed to restore configurations when errors occur. Ifdata configuration fails to achieve the expected result or even causes equipment or networkfaults, you can perform rollback to restore the configurations quickly. This ensures the properrunning of the RNC.

6.7.5 RNC Data Consistency CheckRNC data consistency check ensures consistency between the data in the BAM and that in theFAM. Data inconsistency between BAM and FAM affects the stable running of the RNC. Datainconsistency also leads to a scenario wherein a part of data configuration on the LMT does nottake effect at the host.

6.7.1 RNC Online and Offline StatesThe RNC can be in either online or offline data configuration state.

RNC Online State

If data configuration is performed on the RNC in online state, the relevant configuration datacan take effect in the FAM in real time.

When the RNC is online, you can adopt the online data configuration mode. For details aboutthe mode, refer to 6.7.2 RNC Data Configuration Modes.

RNC Online Configuration Commands

When the RNC is online, you can run all the configuration commands except those describedin Table 6-1.

Table 6-1 RNC offline configuration commands

Run... To...

ADD RNCBASIC Add the basic information of the RNC.

MOD RNCBASIC Modify the basic information of the RNC.

ADD OPC Add an originating signaling point.

MOD OPC Modify an originating signaling point.

MOD N7DPC Modify a destination signaling point.



Run... To...

RMV OPC Remove an originating signaling point.

SET SUBNET Set the number of the subnet of the RNC.

SET SCTPSRVPORT Set the service listening ports on the SCTP server.

SET CMBSWITCH Set the CMB switch.

ADD CNOPERATOR Add the ID of an operator.

RMV CNOPERATOR Remove the ID of an operator.

NOTE

The commands described in Table 6-1 are executable only in offline state.

RNC Offline StateIf data configuration is performed on the RNC in offline state, the relevant configuration datacan take effect only after the RNC is reset or switched to online state.

When the RNC is offline, you can adopt the offline data configuration and dynamic batchconfiguration modes. For details about the modes, refer to 6.7.2 RNC Data ConfigurationModes.

RNC Offline Configuration CommandsAll the configuration commands are executable when the RNC is offline.

6.7.2 RNC Data Configuration ModesThe RNC supports three data configuration modes: online configuration, offline configuration,and dynamic batch configuration.

RNC Online ConfigurationRNC online configuration can be performed only when the RNC is online. Such dataconfiguration is mainly applicable to dynamic configuration of RNC data.

Figure 6-4 shows the process of RNC online configuration.

Figure 6-4 Process of RNC online configuration

The process of RNC online configuration is as follows:


Product Description


1. The RNC is switched to online state.2. The configuration console (LMT or M2000) sends MML commands to the configuration

management module of the BAM.3. The configuration management module sends the configuration data to the database of the

related FAM board and writes the data to the BAM database DB.

RNC Offline ConfigurationRNC offline configuration can be performed only when the RNC is offline. Such dataconfiguration is mainly applicable to RNC initial configuration.

Figure 6-5 shows the process of RNC offline configuration.

Figure 6-5 Process of RNC offline configuration

The process of RNC offline configuration is as follows:

1. The RNC is switched to offline state.2. The configuration console (LMT or M2000) sends MML commands to the configuration

management module of the BAM.3. The configuration management module only sends the configuration data to the BAM

database DB.4. When a subrack or the RNC is reset, the BAM formats the configuration data in the DB

into a .dat file, loads the file onto the relevant FAM boards, and validates the configurationdata.

NOTE

During RNC offline configuration, you can start the quick configuration mode to improve efficiency.

RNC Dynamic Batch ConfigurationRNC dynamic batch configuration can be performed only when the RNC is offline. Such dataconfiguration is mainly applicable to RNC capacity expansion and NodeB reparent.

Figure 6-6 shows the process of RNC dynamic batch configuration.



Figure 6-6 Process of RNC dynamic batch configuration

The process of RNC dynamic batch configuration is as follows:

1. The RNC is switched to offline mode and dynamic batch configuration is enabled.

2. The configuration console (LMT or M2000) sends MML commands to the configurationmanagement module of the BAM.

3. The configuration management module sends the configuration data only to the BAMdatabase DB.

4. When the RNC is switched to online state and immediate validation of configuration datais enabled, the BAM sends the configuration data in the DB to the relevant FAM boardsand validates the data.

NOTE

Offline commands are not executable in dynamic batch configuration mode.

6.7.3 RNC Data Configuration Right ManagementRNC data configuration right management enables only one user to perform RNC dataconfiguration on only one configuration console at a time. The configuration console may bethe LMT or the M2000.

With the control, different users cannot configure data for the RNC at the same time. A user canperform data configuration for the RNC only after the user is granted the data configurationright.

6.7.4 RNC Data Configuration RollbackRNC data configuration rollback is performed to restore configurations when errors occur. Ifdata configuration fails to achieve the expected result or even causes equipment or networkfaults, you can perform rollback to restore the configurations quickly. This ensures the properrunning of the RNC.

RNC data configuration rollback consists of the following four types of operations:

l Undoing a single configuration command: After undoing the command, the RNC rolls backto the configuration state that existed before the relevant command was run. This operationis applicable to only the previous ten configuration commands.

l Redoing a single configuration command: After redoing the command, the RNC returns tothe configuration state that existed after the relevant command was run. This operation isapplicable to only the previous ten configuration commands that were rolled back.


Product Description


l Undoing configuration commands in batches: This operation is performed to undo all theconfiguration commands that were run after a specified rollback point. After the undoing,the RNC rolls back to the configuration of the specified rollback point.

l Redoing configuration commands in batches: This operation is performed to redo theconfigurations that were rolled back in batches. After the redoing, the RNC returns to eitherthe configuration of the specified rollback point or the configuration that existed before theundoing was performed.

6.7.5 RNC Data Consistency CheckRNC data consistency check ensures consistency between the data in the BAM and that in theFAM. Data inconsistency between BAM and FAM affects the stable running of the RNC. Datainconsistency also leads to a scenario wherein a part of data configuration on the LMT does nottake effect at the host.

RNC data consistency check can be initiated by an operator through the LMT, or it can beinitiated periodically by the MML Server module of the BAM through the configuration on theLMT. This task checks the data consistency between the BAM database and the databases ofFAM boards. The fundamental unit for the data consistency check is table records.

6.8 RNC Performance ManagementRNC performance management enables the RNC to collect performance data.

RNC Performance Management Process

The boards of the RNC collect performance measurement data and periodically report the datato the performance management module of the BAM. According to the task file, the performancemanagement module reports the measurement data to the M2000 periodically. The BAM storesthe performance measurement data generated in the last 168 hours, by deleting the earlierrecords.

Figure 6-7 shows the process of performance measurement.

Figure 6-7 Process of performance measurement

In the performance measurement process, the performance console on the M2000 controls theBAM to collect measurement data, based on a default measurement task file that is in .xmlformat. According to the task file, the RNC reports the measurement data at the granularityperiod of the measurement unit.



Measurement Object

Performance measurement objects are of two types: default measurement objects and optionalmeasurement objects.

l Default measurement objects

The RNC automatically measures all objects of this type. The default measurement taskfile supports dual periods. One is the normal measurement period with a default durationof 30 minutes. The other is the short measurement period with a default duration of fiveminutes. The latter one is used for real-time Key Performance Indicator (KPI) monitoring.The M2000 cannot add objects to the list of default measurement objects or remove objectsfrom the list.

l Optional measurement objects

By default, the RNC does not measure the objects of this type. The purpose of defining thisobject type is to avoid measuring these objects, which are of a large quantity, every time.The M2000 can add objects to the list of optional measurement objects or remove objectsfrom the list.

6.9 RNC Alarm ManagementRNC alarm management facilitates you to monitor the running state of the RNC and informsyou of faults in real time so that you can take measures in time.

RNC Alarm Management Function

RNC alarm management has the following functions:

l Setting the storage capacity and generation period for alarm logs

The RNC can store the information of the alarms generated in the last 90 days and amaximum of 100,000 alarm logs. You can set the storage capacity and log generation periodas required.

l Setting alarm levels

The RNC has the alarm level setting function. You can set a level for a specific alarm object.

l Masking alarms of certain objects

The RNC can mask specific alarm objects. The alarms that satisfy the masking conditionsare masked, that is, they are not reported to the alarm console.

l Masking derivative alarms

The RNC can mask derivative alarms, that is, the derivative alarms are not reported to thealarm console.

l Indicating alarms

When a fault alarm is generated, the RNC informs you of the alarm in any of the followingways: blinking of the icon, audible indication of the terminal, or audible and visibleindication on the alarm box.

l Processing alarms

You can browse real-time alarm information, query history alarm information, and handlealarms based on the handling suggestions available from the Online Help of the RNC.


Product Description


RNC Alarm Management Mechanism

The alarm management process consists of alarm generation, alarm reporting, and alarmhandling. Figure 6-8 shows the process of alarm management.

Figure 6-8 Process of alarm management

Each board automatically detects alarms and reports the alarms to the BAM in acknowledgedmode.

The alarm management module of the BAM has the following functions:

l Alarm storage

The module stores the alarms in the database DB of the BAM.

l Alarm processing

The module processes the operation commands sent from the alarm console and sends theresponses to the alarm console. The operation commands can be used to query active alarmsor alarm logs or to modify alarm configurations.

RNC Alarm Box Driving

The RNC uses the universal alarm box of Huawei. The alarm box provides audible and visibleindications of alarms. For appearance and functions of the alarm box, refer to RNC AlarmBox.

Figure 6-9 shows the process of driving the alarm box.

Figure 6-9 Process of driving the RNC alarm box

The alarm box is connected to the LMT through the serial port. When an alarm is reported, theLMT transfers it to the alarm box. The alarm box then emits audible and visible indications.

NOTE

The RNC can control alarm reporting by the alarm box. Through settings on the alarm box, the RNC canmask specified alarm objects and all the alarms under the specified alarm level.



6.10 RNC Loading ManagementRNC loading management enables you to manage the process of loading program and data filesonto boards after the FAM boards (or subracks) start or restart.

RNC Files to Be LoadedThe RNC files to be loaded consist of program files and data files.l All the boards of the RNC must be loaded with program files.

l The SCUa and SPUa boards must be loaded with data files, in addition to program files.

RNC Loading ModesYou can use the SET LODCTRL command to set the loading control parameter to specify theloading mode.

The following loading modes are applicable to RNC program and data files:l Always loading from the BAM and writing to the flash memory of the board

NOTE

This mode is mainly applicable to loading patches.

l Negotiated loading

Negotiated LoadingThe loading of program files and that of data files differ in terms of the negotiation mode.

To negotiate the loading mode for program files, the RNC compares the versions of the programfiles stored in the active and standby workspaces of the flash memory of a board with the versionsof current program files in the BAM.l If the versions are inconsistent, the board loads program files from the BAM and writes the

files to the active workspace of the flash memory of the board.l If the versions are consistent, the board loads program files directly from the active or

standby workspace of the flash memory of the board.

NOTE

If the board loads program files from the standby workspace of the flash memory, the standby workspaceswitches to be active automatically, and the other workspace becomes standby.

To negotiate the loading mode for data files, the RNC compares the Cyclic Redundancy Check(CRC) value of the data files in the active workspace of the flash memory of a board with thatin the BAM.l If the CRC values are inconsistent, the board loads data files from the BAM and writes the

files to the active workspace of the flash memory of the board.l If the CRC values are consistent, the board loads data files directly from the active

workspace of the flash memory of the board.

NOTE

If a board fails to load program or data files from the flash memory after negotiation, the board loads thefiles from the BAM and writes the files to the flash memory.


Product Description


Process of Loading RNC Program FilesFigure 6-10 shows the process of loading RNC program files. During the loading process, theRNC loads the SCUa boards in the RSS and RBSs before loading the other boards in the subracks.

Figure 6-10 Process of loading RNC program files

The process of loading RNC program files is as follows:

1. After starting up, the RNC boards broadcast BOOTP request messages to the BAM.2. After receiving the BOOTP request message from the SCUa, the BAM generates a BOOTP

response message and sends it to the SCUa board. The response message contains theloading control parameter, IP address, and version information.

3. The SCUa board receives the response message and then loads the program files accordingto the loading control parameter.

4. After the loading, the SCUa board forwards the BOOTP request messages of other boardsin the subrack to the BAM.

5. The BAM receives the BOOTP request messages of other boards and sends responsemessages to the boards.

6. The boards receive the response messages and then load the program files according to theloading control parameter.

7. The loading of RNC program files ends.

Process of Loading RNC Data FilesRNC data files are loaded after RNC program files are loaded. Figure 6-11 shows the processof loading RNC data files.



Figure 6-11 Process of loading RNC data files

The process of loading RNC data files is as follows:

1. After the RNC program files are loaded, the SCUa board loads the data files according tothe loading control parameter.

2. After the SCUa board finishes loading the data files, it loads the data files according to theloading control parameter.

3. The loading of RNC data files ends.

6.11 BOOTP and DHCP on the Iub InterfaceThe RNC and NodeB support the BOOTP and DHCP functions. By the BOOTP or DHCPfunction, a NodeB can automatically get an IP address from an RNC and create an OM channelbetween the NodeB and the RNC. The BOOTP and DHCP functions are applicable to ATM andIP transport on the Iub interface respectively.

Concept of BOOTP and DHCPThe Bootstrap Protocol (BOOTP) is usually used to boot diskless workstations. BOOTP issimilar to the Dynamic Host Configuration Protocol (DHCP), but the former can be implementedmore easily than the latter.

In a TCP/IP network, DHCP provides configuration information for hosts on the Internet. DHCPis based on BOOTP. DHCP retains the relay function as provided by BOOTP and adds thecapability of automatic allocation of reusable network addresses and additional configurationoptions.

NOTE

Currently, the Iub interface is applied with static IP address allocation of DHCP instead of dynamicallocation of IP addresses.

Working Mechanisms of BOOTP and DHCPBOOTP and DHCP work in client/server mode. The client applies towards the server forconfiguration parameters, including the requested IP address, subnet mask, and default gateway.


Product Description


The server responds with relevant configuration information according to certain strategy. Theresponse messages are encapsulated by UDP.

NOTE

l DHCP is extended from BOOTP. A DHCP server can interoperate with a BOOTP client.

l In a RAN system, an RNC acts as a server and a NodeB acts as a client.

The UDP port number of the BOOTP/DHCP client is 68, and that of the BOOTP/DHCP serveris 67. BOOTP and DHCP are applicable to only the scenario where the client and the server arelocated in the same subnet. When the client and the server are located in different subnets, theDHCP/BOOTP relay is required in the subnet where the client resides. The DHCP/BOOTP relaycan be implemented by an Internet host or a router.

A BOOTP signaling procedure includes interaction of only a request and a response. Thesignaling interaction of DHCP is more complicated than that of BOOTP.

NOTE

l The DHCP server can receive at least the following datagrams from the client: DHCPDISCOVER,DHCPREQUEST, DHCPDECLINE, DHCPRELEASE, and DHCPINFORM.

l The DHCP client can receive at least the following datagrams from the server: DHCPOFFER,DHCPACK, and DHCPNAK.

Benefits of BOOTP and DHCPl In the case that the OM channel between the RNC and the NodeB is broken, BOOTP and

DHCP enable the channel to be automatically repaired.l BOOTP and DHCP reduce the necessity for local NodeB maintenance, thus increasing

maintainability of NodeBs and reducing the operation costs.

6.12 RNC Upgrade ManagementRNC upgrade refers to a process where the RNC is upgraded to a later version.

Upgrade ScenariosThe RNC may be developed to support new features, higher specifications, or later protocolstandards, or to have defects remedied. In such cases, an RNC needs to be upgraded to a laterversion so that it can provide better services.

Upgrade ModeThe RNC upgrade adopts the remote mode. You can use the dedicated upgrade tool to upgradean RNC remotely through the OM network of the RNC. Figure 6-12 shows the RNC remoteupgrade.



Figure 6-12 RNC remote upgrade

NOTE

The upgrade tool supports batch upgrade for RNCs.

Process of Remote UpgradeThe RNC is upgraded remotely by the dedicated upgrade tool, which consists of the upgradeclient and the upgrade server. The remote upgrade process is as follows:

1. The user sends the version files required for the upgrade and the upgrade server programto the specified directories of the active and standby BAM through the upgrade network.

2. The user starts the upgrade client at the local end and sets up connection between theupgrade client and the upgrade server.

3. The user uses the upgrade client to remotely start the upgrade server.4. The upgrade server backs up the RNC data before the upgrade.5. The upgrade server upgrades the program and data files in the standby workspace of the

active BAM.6. The upgrade server issues a command to synchronize the standby workspace of the standby

BAM and that of the active BAM.7. The upgrade server issues a command to load the host program, DSP, BOOTROM, and

data files in the standby workspaces of the BAMs onto the standby workspaces of the boardsso that the standby workspaces of the boards are synchronized with those of the BAMs.

8. The upgrade server issues a command to switch over the active and standby workspacesof the active BAM so as to upgrade the active BAM.

9. The upgrade server issues a command to reset all the boards of the RNC.10. After the reset, the RNC boards negotiate the loading of version files with the BAMs. The

boards automatically load the program and data files from the standby workspaces of theirflash memories to upgrade the boards.

11. The upgrade server prompts the user to verify services.12. After the service verification is passed, the upgrade server issues a command to switch over

the active and standby workspaces of the standby BAM so as to upgrade the standby BAM.13. The RNC upgrade ends.


Product Description


f 106157666

Documents