IMN/OSS

M. Heinonen

REQUIREMENT
SPECIFICATION

1 (10)

16.11.2001

0.3

GSM-WCDMA INTERWORKING
REQUIREMENTS
FOR OSS
VERSION 0.3

NEOCommentedversion20.11.01inWorkshop

IMN/OSS
M. Heinonen

REQUIREMENT
SPECIFICATION

2 (10)

16.11.2001

0.3

RevisionHistory
Name

Date

Reason For Changes

Version

M. Heinonen

9.11.2001

Initial Version

0.1

M. Heinonen

12.11.2001

Some enhancements

0.2

M. Heinonen

16.11.2001

E-mail comments from several people added

0.3

TableofContents
GSM-WCDMA Interworking Requirements FOR OSS..........................................................................1
Version 0.1............................................................................................................................................ 1
1. OSS 3.1 Releases and the support for them.................................................................................3
2. Interworking solution..................................................................................................................... 4
2.1
Monitor.................................................................................................................................... 4
2.2
Reporter.................................................................................................................................. 4
2.3
Packet Core Configurator.......................................................................................................4
2.4
Radio Access Configurator.....................................................................................................4
2.5
Network Optimizer.................................................................................................................. 5
2.6
Administrator.......................................................................................................................... 5
2.7
UMA....................................................................................................................................... 5
2.8
Transmission........................................................................................................................ 65
3. REQUIREMENTS FOR Combined GSM & WCDMA Management.............................................76
Requirement (ID and name)...................................................................................................................

IMN/OSS
M. Heinonen

REQUIREMENT
SPECIFICATION

3 (10)

16.11.2001

0.3

1.
2.

OSS3 RELEASES AND THE GSM AND WCDMA INTERWORKING SUPPORT

There are the following OSS3 releases including interworking functionality:
1.

OSS3.1 Compatibility Release, which may not have the new NE features
supported, but the existing feature support must work with BSS10.5, RAN1.5
and PaCo3.

2.

OSS3.1 Enhancement Delivery (ED), which should offer the basic support for
the BSS10.5, RAN1.5 and PaCo3

3.

OSS3.5, which should offer the basic support for the BSS11, RAN2.0 and
PaCo4.

Note! The main issue in OSS3.1 ED is 2G-3G interoperability, so please consider all the
necessary functionalities related to OSS3.1 ED based on that. OSS3.1 ED will be the first
Nokia 2G-3G interworking increment that will be used in live networks, so it is not only for
testing purposes anymore. Due to this for example 2G-3G handover management with
related daily mass operating functionality needs to be there in OSS3.1 ED.
Note2! OSS3.1 ED is really an adaptation delivery, so it is not necessary to try to fit
everything new there.
Note3! OSS3.5 will have the advanced interworking support covering all the functionality
areas (FCAPS).

IMN/OSS
M. Heinonen
3.

INTERWORKING SOLUTION

3.1

Monitor

REQUIREMENT
SPECIFICATION

4 (10)

16.11.2001

0.3

The GSM and WCDMA alarms are stored in the same database structure. The applications
can access the alarms across the radio access technologies trough common IRPs. The
alarms are replicated between regional and global cluster in a common format that can be
used for WCDMA and GSM alarms.
The site object support will not be in OSS3.1 although it will be needed to provide a view to
the combined basestations in the future. The site object support is planned to be in
OSS3.5.
Site + antenna + antenna relations objects must be properly supported via IRPs in OSS3.1
ED. In Optimizer, there are currently planned workarounds.
3.2

Reporter
The measurement files and database structure is different in GSM and WCDMA. Reporter
gets for each data source an XML configuration file that tells how the data is structured and
how the topology is accessed. This allows Reporter to map different database structures to
its concepts and present them in a uniform manner to the user.
A use case could be, for example, that you have some similar performance indicators for
BSCs and RNCs. With Reporter, you could see the performance indicators combined in the
same chart. Or, you could display two lines in a graph displaying a "Call Success" for a
GSM and WCDMA cells respectable.
The schema of the database tables in the global cluster is a one-to-one copy of the regional
cluster, only that raw data is missing.
Common KPI storage for 2G/3G is needed. IRPs for accessing the data is necessary.

3.3

Packet Core Configurator

The WCDMA support will mean that the GGSN is upgrated and a few changes in
configuring it are introduced. PCC database schema supports different versions of GGSNs,
so PCC can handle GGSN1.5 (pure GPRS) and GGSN2.1 (both GPRS/WCDMA) in
parallel.

3.4

Radio Access Configurator

One common IRP for accessing 2G/3G CM data is needed.
RAC will not have WCDMA objects and attributes stored in the database in OSS3.1
Enhancement Delivery. WCDMA configuration is only supported by Plan Editor tool, which
can generate XML- files to be downloaded to the network with the OSS3.0 RAC solution.
The GSM parameters can be managed with the existing RAC applications, but WCDMA
parameters and intersystem adjacencies can only be managed by PlanEdit tool.
The goal in OSS3.5 is to have GSM and WCDMA objects and parameters in the same
database structure. The basic functionality needed is:

Configuration uploading from the RNC, BSC, SGSN and MSC to the regional database

IMN/OSS
M. Heinonen

REQUIREMENT
SPECIFICATION

5 (10)

16.11.2001

0.3

Plan provisioning from the regional database to RNC, BSC, SGSN and MSC.

Plan import and actual export IRPs/functionality for WCDMA and GSM data on top of
regional database.

Basic editing functionality for WCDMA and GSM configuration on top of regional
database.

Consistency checks of WCDMA and GSM configuration on top of regional database.

3.5

Network Optimizer

3.5.1

CM Data
Optimizer is heavily relying for RAC build on top of RAC functionality and IRPs, so if there
are no RAC IRPs to download and activate the WCDMA configuration in the network, then
there won't be many optimisationoptimizer features for GSM and WCDMA interworking.
One candidate is to include GAM functionality for mass creation of the adjacencies or do
real measurement based optimizing, if both the measurements and the plan provisioning
interfaces are available.
In OSS3.1 ED timeframe it could be possible to generate the XML- file (RAML2.0) including
adjacencies for PlanEditor, which then can be used for provisioning them into network.

3.5.2

PM data
Check from Reqs to Other docs if there are any requirements. Kimmo

3.6

Administrator
The HW management and SW management solutions are common for the WCDMA and
GSM network elements. The implemention is dependent on the availability of the network
element interfaces.
The time of GSM and WCDMA network element clocks must be adjusted according to
master clock in OSS.

3.7

UMA
UMA maps the WCDMA data to the regional database as follows:

Topology: The object information of the WCDMA objects is stored in the same topology
database as the GSM objects and they both can accessed by the same IRPs to the
applications. The WCDMA and GSM data uses the common replication mechanism
between regional and global clusters.

FM: The WCDMA NWI3 notifications are mapped into the same alarm pipe as the GSM
Q3 alarm events, so they stored in the same tables in the database. The alarm data is
transferred in the same format between regional and global cluster for WCDMA and
GSM.

PM: The measurement files and database structure is different in GSM and WCDMA,
so the uploading and storing of the measurements for WCDMA and GSM are different

IMN/OSS
M. Heinonen

REQUIREMENT
SPECIFICATION

6 (10)

16.11.2001

0.3

from the UMA point of view.

3.8

Service Quality Manager

Service Quality Manager (SQM) monitors services in 2G and 3G networks by observing
and reasoning on the data received by the 2G and 3G equipment. It stores its service
definitions, which can contain 2G and 3G elements at the same time, as well as the rules in
a generic format independent of the actual network.
The basic input to the rules are alarms, KPIs and service attribute values from any service
and network equipment, as long as the data can be obtained from the OSS alarm pipe, the
OSS PM Core and SQM itself. SQM provides ready-made rule packages for QoS
Monitoring of GSM networks, SMS and WAP monitoring, GPRS monitoring and 3G RAN
monitoring.

3.9

Transmission (Planning + Provisioning)

The transmission for PDH (GSM) and ATM (WCDMA) can be planned by Transmission
Planner for the basestation sites. The LACE concept must support both technologies.

3.10

Documentation
The critical information needs related to 2G/3G interworking will be covered in OSS3.1 user
documentation. In practice this means that the OSS3.1 user documentation will contain
- One new document titled 'Maintaining Inter-System Adjacencies'
- Taking the interworking into account in the existing 2G and 3G documents, with links to
the 'Maintaining Inter-System Adjacencies' document.

3.11

Architecture and Delivery

The both GSM and WCDMA software of the system component should have the same RTE
and be installable according to Plug&Play framework. How is the optionality of
GSM/WCDMA part handled (licence)?

3.12

NetAct Radio Planner & WCDMA Planner are missing

IMN/OSS
M. Heinonen

4.

REQUIREMENT
SPECIFICATION

7 (10)

16.11.2001

0.3

REQUIREMENTS FOR COMBINED GSM & WCDMA MANAGEMENT

Requirement
(ID and name)

Release

Priority

RAN1.5028OSS1
2G and 3G
Topology Upload
RAN1.5028OSS2
Common Topology
IRPs for 2G and
3G
RAN1.5028OSS3
2G and 3G
Monitoring

OSS3.1

Must

OSS
System
Component
UMA

OSS3.1

Must

UMA

OSS3.1

Must

MON

RAN1.5028OSS4
2G and 3G Alarm
Correlation
RAN1.5028OSS5
2G and 3G
Reporting

OSS3.5

Optional

MON

OSS3.1
ED

Must

REP

OSS3.1
ED
OSS3.1
ED

Must

REP

Optional

REP

RAN1.5028OSS6
2G/3G Handover
Reporting

Description

The both GSM and WCDMA topology

information is uploaded and stored in the same
database.
The topology information of GSM and WCDMA
objects can be accessed with common IRPs to
the applications utilizing the data.
There must be common monitoring capabilities
for GSM and WCDMA. The combined fault
status of both radio access technologies can
be viewed with the same applications.
The root cause can be found based on the site
information in WCDMA and GSM co-siting
case.
Common reporting capabilities for GSM and
WCDMA. It must be possible to make
combined reports including GSM and WCDMA
performance measurements.
IRP for accessing 2G/3G data
The GSM and WCDMA handover data can be
combined and the successful vs. failed
handovers over the radio access technologies
can be reported.

IMN/OSS
M. Heinonen
RAN1.5028OSS7
2G and 3G
Configuration
Upload

REQUIREMENT
SPECIFICATION

8 (10)

16.11.2001

0.3

Must

RAC

The both GSM and WCDMA RNW objects and

parameters can be uploaded and stored in the
same database.

Must

RAC

Must

RAC

Must

RAC

The RNW objects and parameters of GSM and

WCDMA can be accessed with common IRPs
to the applications utilizing the data. The
functionality of the IRPs should at least include
plan import and actual export functionality.
GSM and WCDMA objects and attributes can
be downloaded and activated as one single
plan. The system must take care of the
consistency of the incoming adjacencies over
RNC and BSC areas automatically.
All the GSM and WCDMA objects and
parameters (actuals and plans) can be viewed
and edited with the same tools.

Must

RAC
NEO

RAN1.5028OSS12
GSM Cell and
Incoming 2G and
3G Adjacency
Consistency

OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)
OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)
OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)
OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)
OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)
OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)

Must

RAC

RAN1.5028OSS13
WCDMA Cell and
Incoming 2G and
3G Adjacency
Consistency
RAN1.5028OSS14
2G and 3G
Adjacency Mass
Creation

OSS3.1
ED
(PlanEdit)
OSS3.5
(RAC)
OSS3.5
(OSS3.1
ED via
PlanEdit)

Must

RAC

Optional

NEO

RAN1.5028OSS15
2G and 3G
Adjacency
Optimization

OSS3.5
(OSS3.1
ED via
PlanEdit)

Optional

NEO

RAN1.5028OSS8
Common CM IRPs
for 2G and 3G
RAN1.5028OSS9
2G and 3G CM
Plan Provisioning
RAN1.5028OSS10
2G and 3G CM
Actual and Plan
Editing
RAN1.5028OSS11
2G and 3G
Adjacency
Management

Operator must be able to create, modify and

delete adjacencies within Nokia GSM and
WCDMA and between Nokia GSM and
WCDMA.
GAM functionality + more in Optimizer.
CI, LAC, RAC, BCCH, BSIC and TxPwrMax of
a GSM cell must be kept in syncronization with
the corresponding parameters in relevant
incoming GSM and WCDMA adjacencies
within Nokia system.
Are measurements available?
CI, LAC, RAC, RNC ID and Scrambling Code
of a WCDMA cell must be kept in
syncronization with the corresponding
parameters in relevant incoming GSM and
WCDMA adjacencies within Nokia System.
Operator must be able to create all the
adjacencies (GSM-WCDMA, GSM-WCDMA,
WCDMA-WCDMA, GSM-GSM) for the cell in
one go by Graphical Adjacency Tool.
Part of GAM functionality in Optimizer X.
Operator must be able to optimize (createdelete) all the adjacencies (GSM-WCDMA,
GSM-WCDMA, WCDMA-WCDMA, GSMGSM) for the cells based on the network
measurements.
Part of GAM functionality in Optimizer X.

IMN/OSS
M. Heinonen
RAN1.5028OSS16
2G and 3G
Adjacency
Planning

OSS3.1
ED

Must

OSS3.1
ED

Must

RAN1.5028OSS17
2G and 3G
Hardware
Management
RAN1.5028OSS18
2G and 3G
Software
Management
RAN1.5028OSS19
2G and 3G NE
User Management

OSS3.1
ED

REQUIREMENT
SPECIFICATION

9 (10)

16.11.2001

0.3

PLA

Operator must be able to plan all the

adjacencies (GSM-WCDMA, GSM-WCDMA,
WCDMA-WCDMA, GSM-GSM) for the GSM
and WCDMA cells.
Interface for getting planned adjacencies
from/to RAC (or PlanEdit)

Must

ADM

Operator must be able to manage the

hardware of the GSM and WCDMA network
elements with the same tools.

OSS3.1
ED

Must

ADM

Operator must be able to manage the software

of the GSM and WCDMA network elements
with the same tools.

OSS3.1
ED

Must

ADM

RAN1.5028OSS20
2G and 3G NE
Time Management

OSS3.1
ED

Must

ADM

Operator must be able to manage the users

with their access rights to the GSM and
WCDMA network elements with the same
tools.
Operator must be able to monitor and, if
necessary, adjust the time in the WCDMA and
GSM network elements.

RAN1.5028OSS21
2G and 3G
basetation
transmission
planning
RAN1.5028OSS22
2G and 3G MSC
radio parameter
management
RAN1.5028OSS23
2G and 3G
Basestation Site
Support
RAN1.5028OSS24
2G and 3G
common service
monitoring rules

OSS3.1

Must

PLA

Operator must be able to plan the PDH (GSM)

and ATM (WCDMA) transmission for the
basestation sites.

OSS3.5

Must

RAC

The MSC objects and parameters for GSM

and WCDMA can be uploaded from MSC,
edited and provisioned to MSC.

OSS3.5

Must

RAC
MON
UMA

See Juha Leino's feasibility study and

requirements for site support in OSS.
Link here

OSS3.5

Must

SQM

There must be common service definitions and

rules for both 2G and 3G networks.

OSS3.5

Must

SQM

IRP for accessing service definitions for all

current network technologies.

OSS3.5

Must

SQM

Service quality monitoring rule definition must

be possible with the same tools.

OSS3.5

Must

SQM

IRP for accessing rule definitions.

RAN1.5028OSS25
2G and 3G service
monitoring rule
definition tools

IMN/OSS
M. Heinonen

REQUIREMENT
SPECIFICATION

10 (10)

16.11.2001

0.3

RAN1.5028OSS26
2G only network

OSS3.5

Must/Opt

ALL

The applications including both GSM and

WCDMA management possibility must hide
the WCDMA part in GSM only network.

RAN1.5028OSS27
3G only network

OSS3.5

Must/Opt

ALL

The applications including both GSM and

WCDMA management possibility must hide
the GSM part in WCDMA only network.

RAN1.5028OSS28
Documenting
2G/3G interworking
solution.

OSS3.1

Must

SoDe/D
OC

The critical information needs related to 2G/3G

interworking must be covered in OSS3.1 user
documentation.
Description of "workaround" solution??? Why
not also OSS3.5?