Introducing OSSii Simplifying SON interoperability

SON Conference
Berlin, 20/21st October 2015
Derek Farrell, Ericsson
Juha Rysk, Nokia
Mathias Gabrysch, Huawei

(version 1.0)

What is OSSii
An initiative started by Ericsson, Huawei and Nokia to enable interoperability between their,
and 3 party OSS systems for reducing integration costs and promoting competition
A commitment to offer licensing of their existing OSS interfaces for the purpose of
development, manufacture and sale off functionality,

1) to one another,
2) to 3rd parties subject to reciprocity (NEPs) or
3) to 3rd parties on fair and reasonable terms (ISVs without own OSS interfaces)
An addition to standardization, enabling interoperability by using the vendors existing
interfaces

An initiative instead of an industry body, forum or organization

The MoU made public available through a web portal
ISV = Independent Software Vendor

OSSii Ecosystem
ISV
ISV

ISV

NEP

ISV
ISV

ISV

ISV

NEP
ISV

ISV

ISV
ISV

NEP

Initiating Parties
2013

Scope of OSSii
MV OSS Systems
FM= Fault Management
CM= Configuration
Management

N-Itfs

Element Manager

C
M

Element Manager

NEP #1
RAN

CN

Event/
Trace

F
M

Stats

Event/
Trace

C
M

Stats

F
M

Stats= Statistics /Counters

for Performance
Management

NEP #2
RAN

CN

Event/Trace =
Event/Trace for
Performance Management
RAN = GSM,WCDMA,
LTE
CN= CS, PS, EPC

Scope of OSSii
MV OSS Systems
FM= Fault Management
CM= Configuration
Management

N-Itfs

Element Manager

C
M

Element Manager

NEP #1
RAN

CN

Event/
Trace

F
M

Stats

Event/
Trace

C
M

Stats

F
M

Stats= Statistics /Counters

for Performance
Management

NEP #2
RAN

CN

Event/Trace =
Event/Trace for
Performance Management
RAN = GSM,WCDMA,
LTE
CN= CS, PS, EPC

Example: SON and OSSii

MV C-SON Systems
1

Step 1: Data from network

is uploaded to MV C-SON
system

Element Manager

C
M

Element Manager

NEP #1
RAN

CN

Event/
Trace

F
M

Stats

C
M

Event/
Trace

F
M

Stats

N-Itfs

NEP #2
RAN

CN

Example: SON and OSSii

AN
R

MV C-SON Systems

ML
B

PSC

Step 2 Data is processed

by C-SON algorithm

Element Manager

C
M

Element Manager

NEP #1
RAN

CN

Event/
Trace

F
M

Stats

C
M

Event/
Trace

F
M

Stats

N-Itfs

NEP #2
RAN

CN

Example: SON and OSSii

MV C-SON Systems

Step 3: Configuration
changes are pushed back
to the network

Element Manager

C
M

Element Manager

NEP #1
RAN

CN

Event/
Trace

F
M

Stats

C
M

Event/
Trace

F
M

Stats

N-Itfs

NEP #2
RAN

CN

Challenge - Cost of interoperability

MV OSS Systems
N-Itfs

Element Manager
NEP #1

Element Manager
NEP #2

Wireless Network

Wireless Network

NEP #1

Wireless

NEP #2

Challenge - Upgrades
MV OSS Systems
Impact on NBI
caused by
release upgrade

N-Itfs

Element Manager
(Release n)

Element Manager
(Release n+1)

Element Manager

Wireless Network

Wireless Network

Wireless Network

NEP #1

NEP #1

Release n

Release N+1

Upgrade

WirelessNEP #2

OSSii is complementary to standards

OSS Northbound
Interface specification

Proprietary
elements

Standardised

Shared specifications under OSSii

include proprietary elements
Shared documents include, in
addition to specifications
Sample files
Roadmap
Compatibility plan
Testing possibility

OSSii - New collaboration model

With OSSii:

Without OSSii:
Operator

Operator

(dedicated Integration
Project)

(off-the shelf)

Strong
co-ordination
needed

NEP

No
business
relationship

ISVs for MV OSS

NEP

OSSii
License
agreement

ISVs for MV OSS

Advantages for Operators

Shorter Integration time

Less coordination

OSSii pre-integration
in NEP lab

Wit

Buy off-the shelf products

NBI
integration
on site

With OSSii
Without OSSii

GA
Communication channel between NEP and
ISV is built by OSSii.

Time

Before new/updated network version

Operator can by off-the-shelf products

reaches the live network, the NBI

instead of starting an integration project

NEP will support ISVs directly.

integration between NEP and ISV version

each time.

Less or no co-ordination needed by operators.

has already been done.

Advantages for ISVs / 3rd parties

From passive response to active planning

ISVs get the specifications in advance and

can develop products beforehand.

Via OSSii all NBI changes will be notified by
NEPs to ISV in advance.

Technical support from NEPs

Technical documents are provided

Life-cycle management of NBIs

.

From project to product

Sound framework to replicate NBI

integration in mass.

OSSii progress
2014

2013

2015

Bi-lateral
License
agreemen
t

Bi-lateral
License
agreements

Bi-lateral
License
agreemen
t

MoU

Bi-lateral
License
agreements

Bi-lateral
License
agreemen
t

2015
Bi-lateral
License
agreemen
t

Initiating parties signed a Memorandum of

Understanding
MoU is publically available at www.ossii.net

Initiating parties signed bilateral cross license

agreements
Interoperability tests are started

Bi-lateral
License
agreemen
t

First ISVs are signing license agreements using

OSSii framework with different NEPs
respectively

OSSii Progress and Growth of the ecosystem

> 2015
ISV
ISV

ISV

NEP

ISV

ISV
NEP

2015

Endorsement

Operators

ISV

ISV

ISV

Initiating Parties
2013/14

More ISVs are in the pipe

to sign license agreement
still in 2015!

How to sign an OSSii agreement

NDA

Bi-lateral
agreement

Post
Agreement

Get in contact with each vendor via www.ossii.net

As a very first step a NDA will be signed

Bi-lateral negotiations with all NEPs separately

Signature of bi-lateral license agreement (ISV NEP)

ISV will get access to all relevant interface documentations

Life-cycle management of interfaces: notification on NBIs updates
Possibility to gain access to a test service

Thanks for your attention!

www.ossii.net