Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
RBS 6402
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.
Trademark List
Contents
1 Introduction 1
1.1 Intended Audience 1
1 Introduction
PM ensures the most efficient use of the network, and includes the following
activities:
• Identification of trends
Monitoring the performance of the RBS 6402 and the WCDMA systems is a
crucial activity for reliable and efficient network operation. The PM functions
can provide detailed information about the network performance, which can be
used to ensure the most efficient network use.
Key
A Performance statistics are captured in PM counters located in the RBS
6402.
There are various PM counter-types referred to as measurement
methods:
• Accumulative Counter
• Peg
• Scan
• Gauge
• Probability Density Function (PDF)
• Condensed PDF
B PM counters increment as the software in the RBS 6402 performs
various tasks and functions.
C A Network Management System (NMS), such as the Operations
Support System for Radio and Core (OSS-RC), is used to manage the
performance data measurements and to analyze the measurement
results.
D The Ericsson Network IQ (ENIQ) can be used for additional
measurements and further processing and analysis of performance
data. ENIQ is proven best-in-class in terms of uploading, storing,
and accessing extensive volumes of data generated within
telecommunication networks.
ENIQ together with OSS-RC is called Next-generation ENIQ and
OSS-RC (NEO). It is an Ericsson solution on Business Intelligence.
ENIQ reports use an ENIQ server as a data warehouse and uses
Business Objects for the data query and presentation.
Key
A In the Managed Object Model (MOM), the performance statistics
measurements are defined in Managed Object (MO) Pm.
Each measurement is represented by an instance of MO
MeasurementType.
The measurement types are grouped into PM groups (MO PmGroup).
B The starting and stopping of a performance statistics measurement is
made in the OSS-RC through a PmJob.
It is recommended to manage PM jobs using the Operations Support
System for Radio and Core (OSS-RC), as the OSS-RC can also stop
and delete PM jobs that are not created by the OSS-RC.
C In the MOM, a PM job is represented by an instance of MO PmJob.
D For each performance statistics measurement, the result is presented in
a statistic file at the end of every Result Out Period (ROP).
E The ROP files are stored at the RBS 6402 for 25 hours, or until the file
storage space is full. Before that, the ROP files are collected by the
OSS-RC for analysis and storage. The supported granularity period and
the ROP are 15 minutes.
The performance statistics ROP files are in XML format. By default ROP
files are not compressed. ROP files can be compressed as GZIP files
by setting PmJob.compressionType = 0.
Note: In order for the OSS-RC to retrieve the PM files created on the RBS
6402, both the RBS node and the OSS-RC must have the same
timezone provisioned.
The PmJob starts the data collection process to gather selected counters
and produce the Result Out Period (ROP) files. Data collection is initiated
by creating a Profile using the OSS-RC. The profile identifies the NEs (RBS
6402s) to be configured to collect the selected Objects (counters). The Profile
is then activated to start the data collection process in the RBS 6402s.
To access the OSS-RC and to start a PMJob in the RBS 6402, the user must
have the proper credentials (Username and Password).
The splash screen displays showing the running version of the PMS:
Subscription types
From the drop-down menu, select a subscription type.
This adds the new profile to a specific tab in the PMS.
5. Click Next.
7. Click Next.
8. Click the network name to expand and view the RBS 6402s that exist in
the network and select the name of the RBS 6402 to be associated with
the profile.
To select multiple RBS 6402s, use ctrl or shift and click the names.
Note: Disconnected RBS 6402(s) are available in the list but the names
are dimmed. Do not select a disconnected RBS 6402.
In the following example, the RBS 6402 is in the RNC403 network and
is named otprb6301.
9. Click > (Select one button) to move the RBS 6402(s) from Available
MSRBS_V1(s) to Selected the MSRBS_V1(s).
SubNetwork PnP
Create a profile that is applied to the selected RBS
6402(s) and is automatically applied to any new RBS
6402(s) added to the subnetwork.
12. Click the class folder name to expand and view the counters that exist
in the class.
13. Click to select the name of the counter to be collected with the profile.
To select multiple counters, use ctrl or shift and click the names of the
counters.
To select all counters in a class folder, click the class folder name. To
select multiple folders, use ctrl or shift and click the names of the folders.
14. Move the desired counters or class folders from Available counters to
Selected counter(s) .
Click > (Select one button) to move the counters or class folders from
Available counters to Selected counter(s) or drag and drop the counters
or folders in Selected counter(s).
17. In the Periodic dates and time setup, set the Start date for the
measurements. Select the Month and Year, and click the date in the
calendar. A check displays on the selected date.
18. If the End date for the measurements is different than the Start date,
set the End date. Select the Month and Year and click the date in the
calendar. A check also displays on the selected date.
19. Select any dates between the Start date and the End date that require
measurements.
To repeat the measurements on specific days, select the days of the week
that require measurements. The choices are: Sun, Mon, Tue, Wed, Thu,
Fri, and Sat.
20. Set the Start time for the measurements. Select the Hour and the Minute
or click Use current time.
21. Set the Duration for ROP file creation. From the drop-down menus, select
the Days, Hours, and Minutes.
ROP files are produced every 15 minutes, and the ROP count is
automatically populated based on the Duration.
If the Duration is set to 0 Days, 0 Hours, and 15 Minutes, only 1 ROP file is
produced for each date selected in the Periodic dates and time setup.
If the Duration is set to 0 Days, 1 Hour, and 0 Minutes, 4 ROP files are
produced for each date selected in the Periodic dates and time setup.
The Summary tab displays the projected times of the measurements and
includes the projected Total ROPs (Day count x ROP count):
The Dates tab displays all the projected dates for the measurements:
The User defined statistics profiles tab is updated with the new entry
and is in Inactive state.
24. Activate the profile. Select the new profile row, right-click, and select
Resume profile... from the drop-down menu.
The profile is applied to all the RBS 6402s selected in the profile. The
PmJob starts in the selected RBS 6402s and the performance measurement
is activated.
28. To view the profile details, highlight the profile, right-click, and select Profile
details... Or double-click the profile on the profile display page.
To access the RBS 6402 and to start a PMJob using the CLI, the user must
have the following:
0 SystemAdministrator
0 SystemSecurityAdministrator
Note: To verify the roles in the RBS 6402, issue the following commands:
• get . roleName
By default, the created PmJob is in the requested job state ACTIVE, and
creates a ROP file in compressed format every 15th minute.
ROP files are created, starting from the first complete ROP.
Finally, the file availability notifications are sent to any subscribed consumer.
Any consumer can subscribe to these notifications and fetch the collected file
from the OSS-RC node. These notifications contain the URL to the target files.
Note: In order for the OSS-RC to retrieve the PM files created on the RBS
6402, both the RBS node and the OSS-RC must have the same
timezone provisioned.
• Subnetwork=NODE/MeContext/ or Subnetwork=ONRM_ROOT_MO_R/
MeContext/ underneath CELLTRACE/ and XML/ for ERBSs, where
Subnetwork is the RNS SubNetwork if the ERBS exists in an RNS or the
Root MO if the ERBS node exists directly under the Root MO.
0 The <TRACE REF> is the trace reference which the PMS user
assigned to the UE Trace profile on profile creation.
The following Directory Example shows the possible folders for one RNC, one
RBS, one pRBS (WRAN), and one RXI.
Directory Example:
dataroot/GPEH/SubNetwork=RNC01/MeContext=RNC01/
dataroot/UETR/SubNetwork=RNC01/MeContext=RNC01/
dataroot/CTR/SubNetwork=RNC01/MeContext=RNC01/
dataroot/XML/SubNetwork=RNC01/MeContext=RNC01/
dataroot/XML/SubNetwork=RNC01/MeContext=RNC01RBS01/
dataroot/GPEH/SubNetwork=RNC01/MeContext=RNC01RBS01/
dataroot/GPEH/SubNetwork=RNC01/MeContext=RNC01PICORBS01/
dataroot/XML/MeContext=RNC01RXI01
dataroot/XML/SubNetwork=ONRM_ROOT_MO_R/MeContext=ERBS01/
dataroot/XML/SubNetwork=LTERNS/MeContext=ERBS01/
dataroot/CELLTRACE/SubNetwork=ONRM_ROOT_MO_R/MeContext=ERBS01/
dataroot/CELLTRACE/SubNetwork=LTERNS/MeContext=ERBS01/
dataroot/UETRACE/272F011001000000/SubNetwork=ONRM_ROOT_MO_R/
MeContext=ERBS01/
dataroot/UETRACE/272F011001000000/SubNetwork=LTERNS/
MeContext=ERBS01/
Result Output Period (ROP) files are stored in the OSS Server based on
their retention period. PMS deletes files that are older than the retention
period every fifteen minutes based on the reporting period of the ROP files.
This retention period is set in the Parameter Editor (PED) by parameters
recordingFileStorageDays, oneMinrecordingFileStorageHours
and recordingFileStorageHours for recording files and by parameter
statisticsFileStorageDays for statistic files.
PMS can also delete files based on the storage space currently available for the
next ROP file. If PMS determines that there is insufficient space available for
the next ROP file, then the oldest recording files are deleted. This takes place
regardless of the recording files retention period.
The PM data file is in XML format for statistical measurements and binary
format for CTR, UETR, GPEH, CELLTRACE and UETRACE measurements.
CTR and UETR files are binary files with ASN.1 coded content and GPEH files
are bit-packed. CELLTRACE files have internal binary format with the External
Message contents optionally being ASN.1 coded.
XML file names have the suffix .xml and compressed binary file names have
the suffix .bin.gz
<EndTime> Indicates the time when the granularity period ends. The
structure is similar to the Starttime field, however,
the allowed values for the minute of the hour are 05, 10,
15, 20, 25, 30, 35, 40, 45, 50, 55, and 00.
<UniqueFDNFromONRM>
The NE Full Distinguished Name as configured by
the OSS-RC Configuration Management application
in the ONRM CS. This is given in the format
Subnetwork=<ROOT_MO_FROM_ONRM_CS>,
Subnetwork=<PARENTRNS>,MeContext=<NODEN
AME> where the ROOT_MO_FROM_ONRM_CS is
the Root MO stored in the ONRM CS. For example,
ONRM_ROOT_MO.
<UniqueFDNFromSegment>
The NE Full Distinguished Name as configured by
the OSS-RC Configuration Management application
in the Segment CS. This is given in the format
Subnetwork=<ROOT_MO_FROM_SEGMENT_CS>,
Subnetwork=<PARENTRNS>,MeContext=<NODENAM
E> where the ROOT_MO_FROM_ SEGMENT _CS is
the Root MO stored in the SEGMENT CS . For example,
ONRM_ROOT_MO_R
<ShortScannerId>
The integer used to identify the measurement on the
NE. This is unique to each NE and not network-wide.
<IMSI/IMEI/IMEI(SV)>
The IMSI/IMEI/IMEI(SV) number of the User Equipment
(UE) that the UE TRACE measurement file refers to.
If the OSS cannot map an IMSI/IMEI/IMEI(SV) to the
Trace Reference, the IMSI/IMEI/IMEI(SV) is unknown.
<Access_Cell> Full Distinguished Name of the UTRAN cell that the CTR
measurement file refers, as configured by the OSS-RC
Configuration Management application. This is given in
the format Subnetwork=, Subnetwork=,MeContext=,
ManagedElement=, RncFunction=,UTRANCell=.
When this field is used for RBS files, the value is always
n=1.
For example:
A20160909.1215+0000-1230+0000_SubNetwork=ONRM_ROOT_MO,MeCo
ntext=otenb2016_statsfile.xml
A20160909.1230+0000-1245+0000_SubNetwork=ONRM_ROOT_MO,MeCo
ntext=otenb2016_statsfile.xml
A20160909.1245+0000-1300+0000_SubNetwork=ONRM_ROOT_MO,MeCo
ntext=otenb2016_statsfile.xml
This example lists three ROP files created for network element “otenb2016”:
• A20160909 – indicates that all three ROP files were created on Sept 9th,
2016.
• The <StartTime> of the first ROP file is “1215+0000”. The file was started
at 12:15 (UTC). The “+0000” indicates that there is no time differential
from UTC.
• The <EndTime> of the first ROP file is 12:30 (UTC). This is the standard 15
minute collection period for ROP files on the RBS 6402 .
3.1 Counters
Accumulative Counter
An Accumulative Counter (ACC) measurement
increases by the value of a sample. It indicates the total
sum of all sample values taken during a certain time.
• Range1 = [0..25]%
• Range2 = [26..50]%
• Range3 = [51..75]%
• Range4 = [76..100]%
• Range1 = 1
• Range2 = 1
• Range3 = 2
• Range4 = 1
Compressed PDF
In a compressed PDF measurement, only the non-zero
values are reported. It is used where only a small part
of the range is used.
• [0] = 0
• [1] = 72
• [2] = 0
• [3] = 0
• [4] = 0
• [5] = 0
• [6] = 44
• [7] = 0
• [8] = 0
• [9] = 0
• [255] = 0
The ACC, Peg, and Scan measurement methods have the same settings in
attributes aggregation and collectionMethod: CC, and SUM.
The KPI HSDPA BLER is defined as the High Speed Downlink Packet Access
Block Error Rate.
Ideally, the number of NACKs is equal to 0, making the HSDPA BLER KPI
equal to 0%.
System Utilization
Hardware use, licenses, traffic and load, congestion,
transport network, and admission.
1. Open the most current WCDMA RBS 6402 Radio Node 16 library.
Two types of files display: Instances and Overviews. The RBS 6402
MSRBS_V1 standard instances that contain the counters are displayed.
The following example is an Overview file. The file shows the PMGroup
and the counters that are contained in that PMGroup.
Each MeasurementType line links to the counter detail. The counter details
are located in the Instance file identified at the top of the Overview file.
lt all
get
Note: This is a large list and takes time to display all the details.
get <counter_name>
get pmNoAllowedEul
In this example:
• PmGroup = EDchResourcesPmGroup
6. Use the pst command to list all the PmJobs configured in the NE.
pst
In this example, there is only one PmJob configured. The PmJob is:
• Currently ACTIVE
• Named: WCDMA_6402_counters
Where:
The PmJob identifier parameter is any portion of the PmJob that the
command can uniquely identify. For example: pgets WCDMA_6402,
pgets WCDMA_6402_counters, and pgets MEASJOB all return the
correct information.