|Published (Last):||18 October 2007|
|PDF File Size:||2.79 Mb|
|ePub File Size:||16.49 Mb|
|Price:||Free* [*Free Regsitration Required]|
Log In Sign Up. Nasir Ramal. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer.
All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co. It aims to ensure that the BSC can work properly by performing verification tasks related to equipment, BSC board software and data file loading, interfaces, and services. This document provides guidelines for commissioning the BSC Product Version The following table lists the product version related to this document. The software installation package, license, and MML command scripts required for commissioning must be ready.
Remote commissioning is performed by the remote engineer technical owner of the BSC and multiple BSCs can be commissioned simultaneously in the central equipment room. There is also another commissioning mode: remote commissioning through local assistance, which is performed by both the remote engineer and the site engineer. The basic services consist of speech service and data service.
Conventions Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text. General Conventions The general conventions that may be found in this document are defined as follows. Boldface Names of files, directories, folders, and users are in boldface.
For example, log in as user root. Italic Book titles are in italics. Courier New Examples of information displayed on the screen are in Courier New. Convention Description Boldface The keywords of a command line are in boldface. Italic Command arguments are in italics. One item is selected. One item is selected or no item is selected. A minimum of one item or a maximum of all items can be selected.
Several items or no item can be selected. Convention Description Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in boldface.
For example, click OK. Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Description Key Press the key. For example, press Enter and press Tab. Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn. Action Description Click Select and release the primary mouse button without moving the pointer. Double-click Press the primary mouse button twice continuously and quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the pointer to a certain position. Compared with issue 05 , this issue does not include any new topics. Boards 5. Compared with issue 05 , this issue excludes the following topics: l Creating Scheduled Tasks 05 This is the fifth commercial release of VRC Compared with issue 04 , this issue does not include any new topics.
Compared with issue 04 , this issue does not exclude any topics. Compared with issue 03 , this issue does not include any new topics.
Compared with issue 03 , this issue incorporates the following changes: Content Description 5. Compared with issue 03 , this issue does not exclude any topics. Compared with issue 02 , this issue includes the following new topics: l Compared with issue 02 , this issue does not exclude any topics. Compared with issue 01 , this issue includes the following new topics: l Compared with issue 01 , this issue does not exclude any topics. Compared with issue 04 of VRC00, this issue does not include any new topics.
Compared with issue 04 of VRC00, this issue incorporates the following changes: Content Description Creating Scheduled Tasks The procedure for creating scheduled tasks is changed. Compared with issue 04 of VRC00, this issue does not exclude any topics.
Requirements for Equipment Status Before commissioning, ensure that the equipment meets the conditions listed in Table Table Requirements for equipment status before commissioning Item Requirement BSC hardware The hardware is installed and passes the hardware installation inspection and power-on check. OMU Configured before delivery. Requirements for Commissioning the Network To ensure smooth verification of the Abis, Ater, A, and Gb interfaces, the network equipment in the commissioning network must meet the following requirements: l At least one BTS is connected to the local BSC The BTS should have passed the commissioning and can provide basic functions.
The CN equipment should have passed the commissioning and can provide basic functions. Figure shows a typical commissioning network. The quantity and type of cables are not specified. Other commissioning scenarios may be possible, as described in Table Figure shows the commissioning process. Prerequisite The BSC cabinet has passed the power-on check.
Procedure Step 1 Check whether the cabinet is powered on. The cabinet is not powered on, Go to step Step 2. The cabinet is powered on, Go to step Step 3. Step 2 Power on the cabinet by referring to Powering On the Cabinet. Step 3 Check the power supply to the cabinet components, as listed in Table Ensure that the hardware operates normally. Context 5. In this mode, the site engineer plugs the USB drive for commissioning into the OMU to complete the installation of the operating system.
The commission is performed through the collaboration between the remote engineer and site engineers. Select a verification method according to the actual scenario. Then, the OMU verification is performed through cooperation of the remote engineer. The information returned is running, 1. Go to Step 6. The information returned is unused, Go to Step 6.
The version of the OMU application is the Perform operations in Step 7 through Step same as that required by the operator, Then this task is complete. The version of the OMU application is 1. Perform operations in Step 7 through Step Perform operations in Step 14 through Step NOTE To view the help information of the omutool, run the. Step 8 Change the external fixed IP address, subnet mask, and the gateway IP address according to the plan of the operator.
Run the. For example, you can run the following command and then press Enter. In this case, the commissioning need not necessarily be performed in the BSC equipment room and can be performed in a centralized manner.
Huawei 3G RNC/2G BSC 6900 (Corporate Only)
Huawei 3G RNC/2G BSC 6900 – (5-Days)
Brief Introduction to Huawei Multimode Controller
BSC6900 Boards and its funtion