Co-MPT Base Station O&M Management

Transcription

1 Co-MPT Base Station O&M Management Hi, OSS Brother, could you show me this new type of base station called co-mpt base station? Q Sure! Let me introduce you its past and present! A 01 Past and Present of Co-MPT Base Stations Originally There are only single-mode base stations. Each of them has one main control board. Each main control board runs a base station of a single mode. RAT-L U 2000 / LMT GBTS NodeB Base Station Model (for example, enodeb) Base stations of different RATs are maintained separately on the U2000. O&M GUIs are different. O&M experience difference is large. O&M efficiency is low. enodeb O&M Mode Separate-MPT base stations are introduced in the SingleRAN solution. O&M of these base stations can be unified. or WMPT or LMPT Base Station Model (for example, MBTS UL GBTS MBTS NodeB enodeb NodeB O&M Mode RAT-L LTE GBTS RAT-U WCDMA U2000/LMT Then Base stations of different RATs require independent O&M teams, which is labor-consuming. or LMPT Base stations of different RATs adopt independent O&M channels. enodeb But Multiple single-mode base stations are bound on the U2000 and displayed as one base station for centralized management. Common resource sharing between base stations of different RATs is low. Main control board resources cannot be shared. The resource usage is low. A set of base station devices are managed by multiple main control boards. Configuration and maintenance are complex.

2 The co-mpt base station is introduced in the SingleRAN solution. Base stations of different RATs share a main control board. RAT-L RAT-U RAT-G U2000/ LMT So Now BTS 3900 RAT-G RAT-U RAT-L Base Station Model Q Base stations of different RATs (GO/UO/LO/GU/GL/UL/GUL) share the same main control board and O&M channel. Base station architecture evolves from separate architecture to integrated architecture. O&M of base stations of different RATs is unified, including GUIs, operations, and model difinitions. refers to objects related to transmission devices, which are common objects for different RATs. O&M Mode How can I operate and maintain co-mpt base stations on the U2000? Let me introduce you basic O&M knowledge on the U2000 first. A 02 Co-MPT Base Station Management Module The U2000 uses a layered management module for co-mpt base stations. It classifies data into physical data and Function data. Use GUL multimode base stations as an example. The following figure shows the management module on the U2000. Physical NE Node GSM N M S WCDMA LTE GBTSFunction NodeBFunction Function Node enodebfunction Physical NE Node GSM U WCDMA LTE WCDMA LTE GBTSFunction NodeBFunction Function Node enodebfunction GBSC NE GSM

3 Physical Data: Function Data: Physical data corresponds to Physical NE Node in the figure and represents common device data and transmission data. The O&M channel is established between this node and the U2000. Data is collected and sent over the O&M channel. Function data corresponds to Function Node in the figure and represents multi-rat logical functions provided by co-mpt base stations. Function nodes, such as GBTSFunction, NodeBFunction, and enodebfunction, are displayed as lower-level attribute information in the NE navigation tree. They are not physical entities and cannot be connected to NEs O&M channels. 03 Co-MPT Base Station Management Policy Physical NE Node Creation Policy Function Node Creation Policy Base Station Type Management Policy The creation process for the is the same as that for other base stations. The can be manually or automatically created on the U2000. After the is properly connected and synchronized, the U2000 can automatically detect each Function from configuration data and create them as subnodes in the topology view. Five physical base station types of the access the U2000 as the unified NE type () and use the same NE mediation. Only one NE mediation is required for all base sttion types of the same version. Distributed base station: DBS3900 Indoor macro base station: Outdoor macro base station: A Indoor large cabinet base station: L Outdoor large cabinet base station: AL Q Service Function Management Policy Functions that are not closely related to base station RAT information are managed in overall control mode. Functions that are closely related to base station RAT information are separately managed based on Functions. How can I manage co-mpt base stations on the U2000? Let me show you! A

4 NE Northbound Interconnection NE Maintenance NE creation Topology display Performance management Fault management Software management License management... NE RAT extension NE reconstruction NE northbound interconnection NE Reconstruction NE Access This poster mainly describes operation differences between the and common base stations. For details, see U2000 Online Help. 04 Access to the U Create the physical NE on the U2000. NE Creation Methods Es N g s ) in e at ch tic de re t a o C Ba om M in ut ch (A ear S The U2000 automatically searches for the NE based on the base station controller it belongs to. The automatic search process for the is the same as that for common NEs. Es N g s in e at ch e re t at C Ba pl in em e) (T od M The process for manually creating a single physical NE is the same as that for creating a common NE. C O rea ne ti by ng O NE ne s Prerequisites: The NE mediation software for the has been installed on the U2000. s E N tic g a t tin tom en a re u m C y A loy b ep D Fill NE information based on the template (in.csv or.ini format). The templatebased creation process for physical NEs is the same as that for common NEs. The is automatically created on the U2000 when the NE is commissioned using the automatic deployment function during the deployment. The creation process for the is the same as that for common NEs. For details about how to create a single physical NE, create physical NEs in batches, and create NEs using the automatic search function, see Topology Management > Creating Physical NEs in U2000 Online Help. For details about the NE automatic deployment function, see RAN Management > SON Management > NE Automatic Deployment Management in U2000 Online Help. Configuration Synchronization The configuration synchronization function is appliable to the entire rather than a single Function.

5 2. Display in the Topology NE Icon Co-MPT base station (NE type: ) The upper-right corner indicates the supported RATs (underlined): G, U, L, M, GU, GL, UL, or GUL The lower-right corner indicates the supported modes: F, T, or FT. Each RAT under the co-mpt base station is marked at the lower-left corner. RATs are separately displayed: GBTSFunction, UMTSFunction, enodebfunction, or NBBSFunction. Single-mode base station The upper-right corner indicates its RAT, such as G, U, and L Separate-MPT base station The upper-right corner indicates the supported RATs, such as TL, GU, GL, UL, GUL, WL, and GUM A single RAT under a separate-mpt base station The lower-right corner indicates the supported modes: F (FDD), T (TDD), or FT (FDD&TDD). Topology Navigation Tree Display After synchronization is complete, the U2000 mounts each RAT of Function based on synchronized configuration information. If the GSM and UMTS RATs are enabled on the, the configuration module matches the GBTSFunction and NodeBFunction with configuration data in the base station controller and displays the corresponding icons under the base station controller. If the LTE RAT is enabled on the, the enodebfunction icon is displayed under the subnet where the is located. Topology View Multimode View Displays the relationship between base stations/functions of different RATs under a multimode NE. Physical View Displays the relationship between GU base stations/functions under a multimode NE and their base station controllers and between LTE base stations/functions and their subnets. umts indicates UMTSFunction under the GBTS. umts is under the base station controller O&M on the U Performance Management Implementation The performance management function manages the as a single base station

6 Navigation Tree Display Object Type/Function Subset Navigation Tree Level-1 nodes are added, including GBTS Function, NodeB Function, enodeb Function, and NODE. The node of each RAT displayes RAT-specific data. The common node displayes common transmission data. Function subnets and object types of the are consistent with those of single-mode base stations. NE Navigation Tree After an object type/function subnet under a RAT is selected in the Object Type/Function Subnet navigation tree, the topology relationship between the and its subnet is displayed in the NE navigation tree. Object Type/Function Subset Navigation Tree Comm on d a ta RA RA T-sp e Tsp cific ec da ific ta da ta NE Navigation Tree After the GBTS or separate-mpt base station is reconstructed into the, the NE type changes, and the performance measurement result originally queried can no longer used. You need to modify or create a performance measurement result query template. 2. Fault Management Alarm Management Maintenance Alarm The maintenance modes of the and its base station controller must be set simultaneously. The query result of the maintenance mode of the GU includes three status records: base station status, status of the logical NodeB under the base station controller, and status of the logical GBTS under the base station controller. Alarm Management Policy The alarm management function manages the as a single base station. Alarm synchronization and alarm setting are performed based on physcial NEs. The operations are basically the same as those for single-mode base stations. Alarm query for the is slightly different from that for single-mode base stations: The U2000 supports Function-based alarm query for the. Alarm query based on MOs Main topology

7 Signaling Trace Management The trace/monitoring function manages the RATs under a co-mpt base station separately. However, the devices and transmission of a co-mpt base station are shared by GSM, UMTS, and LTE RATs. Therefore, the Base Station Device and Transport trace type is added to the navigation tree of the Signaling Trace Management window. The original trace items related to devices and transmission under each RAT node are moved under the Base Station Device and Transport node. 3. Software Management The software management function manages the as a single base station. U2000 NE File Management Client The following types of files can be transferred: Software Patch Data Upgrade risk check package Others External device version package The transmission directions supported vary based on file types. For details, see Software and Hardware Management > NE Version File Type in U2000 Online Help. NE Upgrade The can be upgraded only by using the Software Management Expert 3 Overall Upgrade Process on the Software Management Expert 2 1 Create a project. All base stations on the network can be upgraded, including base stations of the same NE type. The operations are the same as those for common NEs. Risk Check Before Download Create a batch. Risk Check Before Activation The Software Management Expert upgrades NEs by batch. The batches can be planned on the entire network or manually created. The operations are the same as those for common NEs. If the upgrade batch includes LTE NEs, license pre-check can be performed to check license validity. Download the new version file. View the reports. Activation Entire-network planning: Select the site region of the base station. Manual creation: Select the base station controller of the GU base station or the subnet of the LTE base station. Before downloading the new version file, check the risks in the upgrade project. 4 Download Before activating the new version file, check the risks in the upgrade project. View the reports, including the upgrade report and alarm comparison report before and after the upgrade. The operations are the same as those for common NEs. Activate the new version file. If the upgrade batch includes LTE NEs, the LTE NEs and their licenses are activated at the same time.

8 4. Configuration Report The configuration report is added to NE reports. The Base Station RAT parameter indicates the RATs enabled on the. 5. License Management After co-mpt base stations are introduced, the base station licenses are still managed based on RATs. GSM Base Station License Management UMTS Base Station License Management LTE and M Base Station License management Supported base stations: Co-MPT base station (GSM base station in it) Supported base stations: Single-mode NodeB Co-MPT base station (UMTS base station in it) (The management functions supported are the same as those for NodeBs.) Supported base stations: enodeb Co-MPT base station (LTE and M base stations in it) (The management functions supported are the same as those for enodebs.) USU erelay DBS3900 IBS The preceding part describes operation differences between the and common NEs. For details about the functions supported by the, the description of each function module in U2000 Online Help. 06 NE Reconstruction 1. RAT Extension Add services of another RAT to a deployed co-mpt base station. The difference between site deployment and RAT extension is as follows: RAT-L RAT-G Add LTE RAT-U RAT-G You need to incrementally upgrade the software package and configuration data of the new RAT without affecting any existing RAT. RAT-U The exists before you add a RAT. Therefore, you need to provide only details about the target RAT to be added. The NE automatic deployment function adds the RAT by using the same mechanism as that for site deployment. The NE automatic deployment function is used during RAT extension. For details about this function, see RAN Management > SON Management > NE Automatic Deployment Management in U2000 Online Help.

9 (Local and Remote) Commissioning Process for the RAT Added to the Remote engineers Controller CME Preparations 1 Make preparations on a controller side (when newly added NEs support the GSM and UMTS modes). Local engineers U Upload a software package. 3 Upload a commissioning license (when LTE services are to be enabled). 4 Prepare a data configuration file and a deployment list. 6 Check a transport network. 8 Prepare and load a preconfiguration script (Precfg.ini). 5 Prepare the device panel drawing. 7 Prepare dialing test tools. 9 Create an NE commissioning task. 10 Preinstall a software package for a new mode. 11 Start an NE commissioning task. Hardware Installation Check 12 Perform hardware installation and power-on checks. 13 Monitor the NE commissioning task. Commissioning 14 Test the installation and deployment quality. 15 Handle alarms. 16 Check NE health. 18 Acquire an NE commissioning verification report. 17 Test services. 19 Confirm that auto deployment tasks are complete. 20 Set the maximum output power for RF modules. 21 Set an NE to the NORMAL Mode. For details about the co-mpt base station commissioning process, see 3900 Series Base Station Commissioning Guide in 3900 Series Base Station Product Documentation 2. Base Station Reconstruction A base station other than Co-MPT base station a co-mpt base station No new mechanism is added to the NE automatic deployment function for this reconstruction scenario. The recconstruction is implemented based on the target version using the new deployment process. The following restrictions apply before and after the reconstruction: The NE name must be the same. (When a separate-mpt base station is reconstructed into a co-mpt base station, the NE name of the co-mpt base station must be the same as one NE name of the separate-mpt base station.) The O&M IP address cannot be changed. The NE type can be changed. The NE is not deleted from the U2000 during the reconstruction.

10 Base Station Reconstruction Scenarios Before Reconstruction After Reconstruction GBTS GSM RAT of the co-mpt base station NodeB UMTS RAT of the co-mpt base station enodeb LTE RAT of the co-mpt base station Separate-MPT base station(gu) Co-MPT GU Function Separate-MPT base station(gl) Co-MPT GL Function Separate-MPT base station(gul) Co-MPT GUL Function Separate-MPT base station(ul) Co-MPT UL Function 07 Northbound Interconnection The co-mpt base station is displayed as a single NE type () over the NBI regardless of its Function combinations. Various data is reported based on NEs. For details about the northbound interconnection, see Co-MPT Base Station Northbound Interface Overview U2000 and NE Versions Supported by Co-MPT Base Station Managment Wireless Network Information Center Product Version U2000 V200R013C00 and later versions SRAN SRAN 8.0 and later versions GBSS GBSS 15.0 and later versions UMTS UMTS 15.0 and later versions LTE eran 6.0 and later versions Tech Support SPO Information Dept Copyright Huawei Technologies Co., Ltd All rights reserved.