Training Presentation for CPI Newbies

An Introduction to CPI and LTE CPI

this presentation is intended for ericsson-internal audiences only

Ericsson Cpi

What is CPI and how is it created, delivered and accessed?

LTE_presentation_Dallas_Feb_2011 | Ericsson Internal | 1/0341-3/FEA 101 8211 Uen, Rev A | 2011-03-08 | Page 3 (57)

Customer Product Information

› Customer Product Information (CPI) is the technical information needed to handle Ericsson products throughout the product life cycle.

› CPI is intended for Ericsson customers. › CPI does not include marketing or sales information.› CPI does not include information for Ericsson-internal

target groups.› Internal users of CPI are, e.g., services and training.

However, CPI is not adapted to their needs unless it benefits the external customer as well.


CPI Delivery Format and Tools

› CPI is published on CPI Store (Ericsson internal) and mirrored to CPI Extranet (external, for customers and partners).http://cpistore.ericsson.se

› CPI is published in a file container called an ALEX library. With the Active Library Explorer (ALEX) tool, the user can browse Ericsson ALEX libraries with a standard browser.

› All Ericsson CPI is required to follow the Generic CPI Structure, which specifies how the information is to be arranged and labelled in the ALEX library.

› Other Ericsson generic requrements on CPI cover areas such as high level information structure, writing style, formats, registration, and supply.


CPI Delivery Format and Tools

› The primary CPI display format is HTML, but PDF is normally also provided.

› CPI is developed in XML format using Tagtool with Ericsson CPI DTDs and style sheets. (Tagtool is a set of tools based on the Arbortext Editor (Epic) from PTC.)


http://cpistore.ericsson.se


ERICSSON Generic CPI Structure for ALEX Libraries


CPI Library IN ALEX BrowseR


CPI Store MIRRORED to CPI Extranet

CPI StoreAccess to all Ericsson CPI

CPI ExtranetAccess set by MU on folder levelFirewall

The internal viewfor all Ericsson

employees

The external viewfor Ericsson customers


Customer Access

CPICPI Extranet

CPI for lTE

* Cpi contacts at lte* LTE-specific Cpi directives and concepts


LTE CPI CONTACTS

› LTE CPI system managers:Fredrik SmidfeltAnikó Schmidt

› LTE CPI project manager:Gillian Mackay

› LTE RAN systems project office in Stockholm (Kista)

(March 2011)


Feedback on cpi?

› Email us.› Call us.› To be sure that action is taken:

Write a TR!› Please be very specific! Give examples. It significantly

increases the chances of a useful update.


Organization

› The main responsibility for LTE CPI is located to the LTE System Project Office.

› Anikó Schmidt and Fredrik Smidfelt are LTE CPI System Managers, responsible for e.g. strategic planning, processes and coordination.

› The CPI is developed in CPI projects that follow the system projects.› CPI is a system project delivereable, managed by system PjM. › There is a CPI project manager taking care of the CPI specific detail project

planning and management.› CPI is written by technical writers and system engineers, depending on

information type. Some CPI is auto-generated e.g. from the MOM (lists).

› Language review of all CPI is done by the CPI editor and all illustrations are created by an illustrator team. (Both these tasks are done off site by subcontractors.)

› A large part of the LTE CPI library is produced by other orginizations: CPP, PDU RBS, Site Products.


Interfacing Organizations

› The Product Information Discipline within R&D is the central CPIorganization responsible for generic requirements, methods, and tools.

› LTE CPI has interfaces to the CPI organizations for RBS6000, CPP, OSS, WCDMA RAN and Site Products.

› More than half of the documents included in an LTE ALEX are produced by other organizations, manily CPP and RBS.

› There are currently active CPI fora for cooperation, coordination and alignment on varying levels between LTE and: RBS HW, RBS SW, and CPP-based nodes.

› LTE also takes part in a forum for DU Radio CPI and in PI Discipline meetings and activities.

› Other important interfaces are OSS, RAN I&V and BUGS (=services).


The 70% Reduction objective

› When starting LTE CPI development, we had a requirement to reduce CPI by 70% as compared to WCDMA.

› What? size, volume, complexity, COST

› How?- Avoid “nice to know” information- Avoid describing textbook and standards information (3GPP), provide reference/link instead- Page count limit for some document types- Increase auto-generated CPI (lists)- Single source: system documentation = CPI- Simplified system and product = less to describe- All LTE CPI in one ALEX.


What else is new?

LTE CPI structure is based on and very similar to WCDMA CPI.

Some differences:› All LTE CPI contained in one single ALEX library› Slightly different concept and template for feature descriptions = “user

descriptions”› Managed Area Description (MAD) concept fully adopted from start› “Library Overview” replaced by “Finding Information in the Library” with

FAQ style information› “Parameter and Counter Limitations” (new document)› No man pages, except those instructing how to access man pages› Minor differences in alarm instructions due to different input data


LTE and wcdma Library structure

WCDMALTE

RBS xxxx RNC RXIRBS yyyy

RAN

Node

RAN + RBS xxxx + RBS yyyy

Collection

› Libraries on two levels, RAN and node› Uses collections to enable single-click download

› One library containing all CPI: RAN and node CPI for all RBS types

RAN


LTE CPI information structure

System and Node Description

UserDescriptions

FunctionalArea

Descriptions

ProcessDescriptions

Hardw

areO

PIs

ManagedA

reaD

escriptions

AlarmOPIs

Configuration

OP

Is Safety

MOM

EventDescription

ParameterDescriptions

DeltaDocuments

Glossary

Library Overview

InstallationInstructions

Operation & MaintenanceInstructions

DescriptionsALEX Instruction

Legal

Installation

For more information, click on the Document Type

KPIs

Emergency

Emergency

DTDs

File Examples

ReferenceDocuments

IWDs

UserDescriptions

FunctionalArea

Descriptions

UserDescriptions

FunctionalArea

Descriptions

UserDescriptions

FunctionalArea

Descriptions

UserDescriptions

FunctionalArea

Descriptions

UserDescriptions

FunctionalArea

Descriptions

ALEX Instruction

UserDescriptions

FunctionalArea

Descriptions

Finding Information in the Library ALEX Instruction

Unit

Descriptions

RBS

Descriptions

GU

ID

escriptions

Configuration

DataFunctional

AreaDescriptions

Dimensioning Guidelines

KPIs

DTDs

File Examples

KPIs

DTDs

IWDs

File Examples

KPIs

DTDs

EventDescription

IWDs

File Examples

KPIs

DTDs

Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs

Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs


Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs

MOM ParameterDescriptions

Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs

DeltaLists

MOM ParameterLists

Network Impact Report (NIR)

Glossary

Event List

IWDs

File Examples

KPIs

DTDs

UserDescriptions

Quick Guides

Limitations


Document Types Created by PDU LTE

= PDU LTE only= PDU LTE, CPP and PDU RBS

LTE uses CPI from the following designorganizations: PDU RBS, CPP and corporate.

= PDU LTE and PDU RBS


UserDescriptions

TechnicalProduct

Descriptions

FunctionalArea

Descriptions

ConfigurationData

GUIDescriptions

ProcessDescriptions

UnitDescriptions

Hardw

areO

PIs

ManagedA

reaD

escriptions

AlarmOPIs

Configuration

OP

Is Safety

MOM

EventDescription


DeltaDocuments

Glossary

Library Overview

InstallationInstructions

Operation & MaintenanceInstructions

DescriptionsALEX Instruction

Legal

Installation

KPIs

Emergency

Emergency

DTDs

File Examples

ReferenceDocuments

IWDs

UserDescriptions

FunctionalArea

Descriptions

ConfigurationData

UserDescriptions

FunctionalArea

Descriptions

GUIDescriptions

ConfigurationData

UserDescriptions

FunctionalArea

Descriptions

TechnicalProduct

Descriptions

GUIDescriptions

ConfigurationData

UserDescriptions

FunctionalArea

Descriptions

UnitDescriptions

TechnicalProduct

Descriptions

GUIDescriptions

ConfigurationData

UserDescriptions

FunctionalArea

Descriptions

ALEX Instruction

UnitDescriptions

TechnicalProduct

Descriptions

GUIDescriptions

ConfigurationData

UserDescriptions

FunctionalArea

Descriptions

Finding Information in the Library ALEX Instruction

UnitDescriptions

RBSDescriptions

GUIDescriptions

ConfigurationData

FunctionalArea

Descriptions

Dimensioning Guidelines

KPIs

DTDs

File Examples

KPIs

DTDs

IWDs

File Examples

KPIs

DTDs

EventDescription

IWDs

File Examples

KPIs

DTDs

Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs

Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs


Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs


Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs

DeltaDocuments



Glossary

EventDescription

IWDs

File Examples

KPIs

DTDs

UserDescriptions

Quick Guides

Limitations


More information

› CPI Storehttp://cpistore.ericsson.se

› LTE CPI on CPI Store: Radio Access Network -> LTE Radio Access Network ProductsorRadio Access Network -> Base Stations -> RBS 6000 Family -> RBS 6XXX -> LTE

› Customer Product Information (CPI) web page:http://internal.ericsson.com/page/hub_inside/support/rd/tools/cpi/index.jsp

› Product Information Discipline - R&D http://internal.ericsson.com/page/hub_inside/company/researchdevelop

ment/pmt/management/discipline_management/pi/index.jsp

Feature Description Concept for LTE RAN


background

› Concept idea by Greg Harman GSDC Australia temporarily working with EAB/FJL/SP in 2008. Previously on the operator side (Telstra).


Guiding Principles

› The concept for feature CPI for LTE RAN is based on

– The way Ericsson sells the system to the operators

– The way that the operators use CPI

– The goal to reduce LTE CPI by 70%.


TARGET User Profile

› The following profile is assumed for a CPI user who works for an operator

– Has 5 to 15 year experience in the wireless industry (or works for or with someone who fits this profile)

– Has attended Ericsson training (System Overview, Air Interface, Advanced System Techniques etc)

– Has a number of text books on the shelf describing the technology– Has accessed the 3GPP standards website to read selected parts of

the standard– May have worked at Ericsson in the past or may work for Ericsson

in the future


LTE RAN Feature CPI guidelines

› The following guidelines are used for developing LTE RAN feature CPI– Each licensed feature is described in one CPI document: a User

Description . The general rule is that the title is the same as the feature name.

– The content reflects Ericsson’s implementation of the system. Generic, “text book” details of how the system works are not included.

– If the operator can’t change the parameter they don’t need to read about it in CPI.

– A released User Description should only have to be updated if there is a change to the feature.

– The User Descriptions contains: * An impact statement detailing the impact on generic system functions, e.g., capacity, handover, coverage, etc.* Details on feature specific counters* Information on recommended use, based on the intended use of the feature at the time of CPI development


3GPP Protocol Support

1. Introduction2. Revision Details3. Feature Overview4. Parameters5. Impact on Network

5.1 Capacity5.2 Coverage5.3 Handover

6. Associated Features7. Counters and Performance8. O&M Information

Link Adaptation & Power Control




Dual Antenna Downlink




User Description Overview

Feature list› Updated for new Features / Releases› Long term → larger number of small documents

……….

……….

Intra LTE Handover

16QAM UL

64QAM DL

Dual Antenna DL

……….

Transport Network Termination

Scheduler

Link Adaptation & Power Control

3GPP Protocol Support

Feature Name => User Description Title

64QAM Downlink

1. Introduction2. Feature Overview3. Detailed Description of Operation4. Parameters5. Impact on Network



User Descriptions› Network impact stated in general terms› Only include what that operators can change› O&M information will be documented in other

referenced CPI documents

Document type definitions


Finding Information in the Library

› Introduces the CPI user to the content and structure of the ALEXlibrary

› The document is structured like an FAQ with answers to questionsabout where to find information.

› Target Groups: Everyone using the LTE ALEX libraries

› Decimal Classes: 1551-

› Folder in ALEX: Library Overview

› Examples of documents:– Finding Information in the Library

Back to LTE Document type Overview


ALEX Instructions

› This category contains documents that provide information on how to use and navigate the ALEX GUI.

› The documents are written on corporate level.



› Folder in ALEX: Library Overview

› Examples of documents:– How to get started with Active Library Explorer




› This category includes only one document used for all RBSs. The document covers both system and node.

It provides an overview of the system. It briefly describes the system and node functions as well as the architecture. For a description of the RBS HW, the document refers to the RBS 6000 document RBS Description.

› Target Groups: Everyone coming in contact with LTE


› Folder in ALEX: Product Overview

› Example of document:– System and Node Description

Back to LTE Document type Overview Back to LTE Document type Overview


RBS Description

› This document type provides information about the RBS cabinet including hardware, dimensions, external requirements, interfaces, standards, regulations, and dependability of the product.

› There is one RBS Description per cabinet type and the document is common for all access systems (LTE, WCDMA and GSM)

› The RBS Descriptions are written by PDU RBS

› Target Groups: Primarily Site Acq, SiteEngineering and ProductConfiguration. (also an intro-duction to the cabinet and HW)


› Folder in ALEX: Product Overview

› Template: owned by PDU RBS

› Examples of documents:– RBS Description (6102)



Unit Descriptions

› The Unit Descriptions provide information such as basic unit functions and interfaces for the RBS HW units. The documents also provide product data such as power consumption, size, and weight.

› There is one Unit Description per unit type.› The Unit Descriptions are written by PDU RBS.

› Target Groups: Primarily Site Engineering, Product Configuration and Field Technician. (also an introduction to the units)


› Folder in in ALEX: Product Overview


› Examples of documents:– Radio Unit Description– Digital Unit Description



User Descriptions

› The User Descriptions describe the commercial features for LTE. One commercial feature (FAJ) equals one User Description.

› The documents are based on Ericsson’s implementation of the system.› User Descriptions contain an impact statement for generic system

functionality, e.g., capacity, handover, coverage.

› Target Groups: Network Planner, ProductConfiguration, Network Operator, Network Optimizer

› Decimal Classes: 1553-› Template: 6/002 01-3/FEA101 8211› Examples of documents:

– Power Control– Scheduler



Functional Area Descriptions› The Functional Area Descriptions provide information about basic

functionality of LTE such as PM and FM etc.› The documents describe Ericsson’s implementation within each area. The

documents cover both RAN and node level and can also be seen as tutorials for each area.

› This category is separated from and should not be confused with the User Descriptions which describe the commercial features. The name Functional area description is chosen to avoid confusions with WCDMA’s Function Descriptions (internal documents) and also to connect to the naming of the Managed Area Description document type.

› The following documents belong to this category:

– Fault Management– Performance Management– License Management– Security Management– RAN Software Management

› Target Groups: Network Planner, Product Configuration, Field Technician, Network Operator, Network Optimizer, System Administrator

› Decimal Classes: 1551-› Template: 4/002 01-3/FEA 101 8211› Folders in ALEX: applicable subfolder in the Operation

and Maintenance folder› Examples of documents:

– See documents to the left



Dimensioning Guidelines› This document type provides guidelines and recommendations when planning,

designing and dimensioning the network. Why is dimensioning done?

To demonstrate Ericsson’s expertise and reliability as a telecom provider to customers and potential customers in RFI situations

To calculate an estimate of the air interface performance of an LTE system in a tender project› reliable data for pricing› a basis for license dimensioning› a starting point for TN dimensioning

To give help to system designwith an overall system

performance perspective

› Target Groups: Network Planner

› Decimal Classes: 100 56-

› Folder in ALEX: Planning

› Template: 11/002 01-3/FEA 101 8211

› Examples of documents: – Coverage and Capacity Dimensioning– Radio Wave Propagation– Deployment Guideline



Process Descriptions

› The Process Descriptions provide descriptions of the system use cases (such as Add RBS, Extend RBS Capacity, and, Add RBS Redundancy) The documents provide description of the process and not detailed instructions. The Process descriptions are written on RAN level and refers to more detailed descriptions on node and OSS level.

› Target Groups: Product Configuration, Field Technician, Network Operator

› Decimal Classes: 1551- (1543-)

› Template: 10/002 01-3/FEA 101 8211

› Folders in ALEX: several different folders

› Examples of documents:– Add RBS– Expanding to Multi-Standard Single Mode



Configuration Data

› This document type provides information about HW configurations in RBS 6000, for example basic configurations, site cell configurations, co-siting, antenna connection fields, antenna connectors and cabling information for RF and non-RF connections.

› These documents are primarily intended for Site Engineering and Product Configuration but are also used during O&M for identifying cableconnections.

› PDU RBS is document owner and responsible for these documents. › Target Groups: Site Engineering, Product

Configuration, Field Technician


› Folder in ALEX: Site Engineering

› Examples of documents:– RBS Configurations– Antenna and RF Connections– Non-RF Connections



GUI/UI Descriptions

› This document type provides information on the available GUIs and othertools for interacting with the products.

› Target Groups: Product Configuration, Field Technician, Network Operator, Network Optimizer, System Administrator

› Decimal Classes: 1551-/190 80-

› Folder in ALEX: Operation and Maintenance, and Manual Pages

› Examples of documents:– Element Manager– man (manual page)



Hardware OPIs

› This document type provides instructions for HW-related tasks, for example replacement of a HW unit.

› The HW OPIs for LTE are written by PDU RBS

› Target Groups: Field Technician, Installation Technician


› Folder in ALEX: Operation and Maintenance -> Hardware Management


› Examples of documents:– Replacing Radio Units– Replacing Power Units



Managed Area Description

› This document type provides information about Managed Areas (MAs). An MA represents a group of functions and Managed Objects (MO) within the node, where each MA is relatively independent of other MAs.

› The MA Description (MAD) explains concepts and gives readers an understanding of how an area is modeled, what functionality is related to the area and how this is managed.

› The MADs provide tool-independent* instructions on how to perform different tasks, for example Add/Remove Cell, Restarting a Fan etc.

› PDU LTE, PDU RBS and CPP write MADs

*Tool-independent means that the instructions only describes what MOs and attributes to set but not whattool to use or how.

› Target Groups: Field Technician, Network Operator, Network Optimizer, System Administrator, Network Planner


› Template: 002 01-3/FEA 101 8211

› Folder in ALEX: Operation and Maintenance -> Managed Object Management

› Examples of documents:– Radio Network– IP Transport– Support System



Configuration OPIs

› The Configuration OPIs provide instructions about how to perform tasks related to configuration of the products, for example Create Configuration Version, Lock Board, Restart Node etc.

› Most of the configuration infromation is covered by the Managed Area Description concept. Configuration OPIs are only written when exceptionally motivated.

› Target Groups: Field Technician, Network Operator, Network Optimizer, System Administrator


› Folder in ALEX: various subfolders to the Operation and Maintenance folder

› Template:

› Examples of documents:– Create Configuration Version– Lock Board– Restart Node



Alarm OPIs

› This document type provides instructions about how to act on specific alarms in order to correct the fault and cease the alarm.

› One alarm (SpecificProblem) equals one Alarm OPI› The SpecificProblem slogan is also the title of the corresponding Alarm OPI › The procedure is presented as a sequence of tasks with one task per step. › There are three origins of Alarm OPIs:

– PDU LTE only– CPP– Common SW

(common for GSM, WCDMA and LTE)

› Target Groups: Field Technician, Network Operator, Network Optimizer, System Administrator


› Examples of documents:– GeneralSwError– HwFault



Installation Instructions

› The Installation Instructions provide instructions about how to install the product (HW installation)

› This category also includes information about installation verification› The Installation Instructions used by LTE are created by PDU RBS

› Target Groups: Installation Technician, (Civil Work)


› Examples of documents:– Installing an RBS (RBS 6201)



Safety

› For legal reasons there must be CPI regarding safety and the target group is everyone coming in contact with the LTE products

› There are three documents in this category:– Personal Health and Safety Information Contains important information regarding health and safety in the

workplace and in the external environment. – System Safety Information Contains important information regarding product safety. – Radio Frequency Electromagnetic Fields Contains guidelines for the estimation of RF exposure levels and

compliance distances not already specified by Ericsson for RBS product configurations and antennas.– Radio Frequency Electromagnetic Exposure

› The documents are created on corporate level and by PDU RBS

› Target Groups: Everyone coming in contact with the LTE products


› Examples of documents:– Personal Health and Safety information– System Safety Information– Radio Frequency Electromagnetic Fields– Radio Frequency Electromagnetic Exposure


Emergency

› The Emergency documents provide instructions about how recover a node after major failure and how to set software licensing to emergency state

› Target Groups: Field Technician, Network Operator


› Examples of documents:– Emergency Restoring a Configuration Version

Backup




› The Network Impact Report (NIR) describes how a release, with new and changed features, affects the previous release and the operator's overall network. The document is intended to provide sufficient information at an early stage to Ericsson system operators to help plan the introduction of new products and upgrades to the networks. The document is is subject to change during the development of the new release.

› For LTE the NIR is closely connected to the following document types:– User Descriptions– Parameter Descriptions– Delta Documents– Event Descriptions– Limitation Documents

› Target Groups: Network Planner, Network Operator, Product Configuration, Network Optimizer, Site Acquisition, Site Engineering


› Template: 13/002 01-3/FEA 101 8211

› Folder in ALEX: Planning

› Examples of documents:– Network Impact Report (L11B)



Managed Object Model (MOM)

› This is the HTML-version of the MOM. Only MOs visible to the customer are included.

› The MOM contains LTE, PDU RBS and CPP parts

› Target Groups: Network Planner, Network Operator, Product Configuration, Network Optimizer, Field Technician




Parameter lists

› The Parameter Lists describe the LTE RAN Network Parameters. All information provided in these documents can also be found in the MOM but these excel files add support for filtering and sorting. The excel format alsoenables the users to e.g. use the information with scripts.

› The Parameter Lists are generated from the MOM using the PACE tool.› Parameter and Counter Limitations is a document listing counters and

parameters that are visible in the MOM but not yet supported (partly or at all).



› Examples of documents:– Radio Network Parameters– Parameter and Counter Limitations


Interworking Descriptions (IWDs)

› This category describes the RBS configuration files used for initial configuration and O&M configuration

› There following configuration files exist: – Autointegration RBS Summary File – Site Basic Configuration File– Site Installation File– Equipment Configuration File

› Target Groups: Network Operator, Product Configuration, Field Technician


› Examples of documents:– Configuration Files


Configuration File DTDs

› This category contains the DTDs for the RBS configuration files. (The files contain the configuration parameters that are used to configure an RBS.)

› The DTDs are included in their original format in ALEX.› There following configuration files exist:

– Autointegration RBS Summary File DTD– Site Basic Configuration File DTD– Site Installation File DTD– Equipment Configuration File DTD



› Examples of documents:– Site Basic Configuration File, DTD


Configuration File Examples

› This category contains examples of RBS configuration files. (The files contain the configuration parameters that are used to configure an RBS.)

› The examples are included in original format (.xml) in ALEX.› There following configuration file examples exist:

– Autointegration RBS Summary File – Site Basic Configuration File– Site Installation File– Equipment Configuration File


› Decimal Classes: TBD

› Examples of documents:– N/A


Event list

› The Event List is an excel file listing all* PM Events and their data › The file is generated from the MOM using the PACE tool› The following information is available in the document:

Sheet (in 10/…) ColumnspmEvents Event ID, pmEvent Name, Event Type, EventTriggerpmEventHeader Event Parameter Name, UE Mandatory, Cell Mandatory, RBS Mandatory, External MandatorypmEventFormat pmEvent Name, Event Parameter NameEventParams Event Parameter Name, Parameter Description, Parameter Size, Parameter Type, Logical value, Numeric

Value, Actual Parameter Value Range, Parameter Resolution, Parameter Unit

* available to the customers

› Target Groups: Network Planner, Network Optimizer


› Examples of documents:– Event Description


Delta lists

› The delta documents provide delta information (changes) between two LTE RAN Network releases (for example L10A and L10B).

› There are delta documents for:– Alarms– Parameters– Events

› The documents are in excel format supporting filtering and sorting. It alsoenables the users to e.g. use the information for scripts.

› The delta documents are generated from the MOM using the PACEtool.


› Decimal Classes: TBD ???

› Examples of documents:– <Radio Network Parameters> – <Transport Network Parameters>


KPI Descriptions

› This category describes the Key Performance Indicators (KPI) for LTE RAN for measuring subscriber perceived quality. The quality metrics are divided into six areas: Accessibility, Retainability, Integrity, Utilization, Mobility, and Availability.

› Target Groups: Network Optimizer, Network Operator, Network Planner


› Examples of documents:– <Radio Network KPIs>


Glossary

› The glossary defines the terms and acronyms used in the CPI documentation for LTE.

› PDU RBS creates a glossary for RBS 6000 that is used as input to the LTE glossary


› Decimal Classes: TBD

› Examples of documents:– <Glossary>