INFORMATION REGARDING HUAWEI BTS AND THEIR FUNCTIONS
WBBP Basd Band processing CEDescripción completa
HUAWEI RTWP.pdf
Full description
internet of things
Huawei SASU
HUAWEI TRACE RECORDING The most commonly used tracing features is the CHR (Call History Recording) and IOS (Cell Trace). Both log files are in form of binary files, CHR has different type of files PCHR, UCHR, and CHR. PCHR is Call history log files, not an event based log files like Ericsson GPEH for example. It’s contain all calls in the RNC. Hence the amount of data’s is a lot bigger than GPEH. Notice the speed on the process is a little slow and we are working on the performance to speed up the process. Available Tools in the market to Analyze Huawei tracing: Nastar (Commercial Huawei) PCHR Analyzer (Internal Huawei) Actix One, Aexio,Schema etc (Third Party) TEMS Visualization
There are few types of call log inside the PCHR, In current release TV will support log type 6. Log files is presented per call (IMSI) basis, imagine this is as the larger scale of Ericsson UETR. PCHR comes in different version and Model based on Huawei RAN releases. It’s reflected on the .xml file. Version = V900R013 Model = C00SPC200 We need to make sure we obtain these .xml file from the customer. The PCHR's log files are generated automatically and stored under the BAM folder as below: R12 : /bam/common/fam/famlogfmt R13 : /bam/common/fam/famlogfmt/pchr
DATA SOURCE TEMS .Cel file with neighbor information (same format) PCHR log files : download files from BAM folder, if files is not available then we activate the recording. Unlike GPEH once the recording is active it will be infinite until cancelled. Tracing activation can be done thru MML command SET PCHRCTRL RNC SET CHRSW NODE Use HUAWEI LMT tools to enable all the fields. EXP CFGMML Export Bulk CM, to be done per RNC. Phone Model File (same format)
LEGAL DISCLAIMER This document contains specific forward-looking statements, e.g. statements including terms like “believe”, “expect” or similar expressions. Such forward-looking statements are subject to known and unknown risks, uncertainties and other factors which may result in a substantial divergence between the actual results, financial situation, development or performance of Ascom and those explicitly presumed in these statements. Against the background of these uncertainties readers should not rely on forward-looking statements. Ascom assumes no responsibility to update forward-looking statements or adapt them to future events or developments.
