Introducing OSSii - Simplifying SON interoperability

SON Conference

Berlin, 20/21st October 2015

Derek Farrell, Ericsson

Juha Röyskö, 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

Initiating Parties

ISV

ISV

NEP

ISV

ISV

ISV

NEP

ISV

ISV ISV

2013

NEP

ISV

ISV ISV

Scope of OSSii

RAN CN

RAN = GSM,WCDMA,

LTE

CN= CS, PS, EPC NEP #1

Element Manager

NEP #2

RAN CN

Element Manager

MV OSS Systems

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

FM= Fault Management

CM= Configuration

Management

Stats= Statistics /Counters

for Performance

Management

Event/Trace =

Event/Trace for

Performance Management

N-Itfs

Scope of OSSii

RAN CN

RAN = GSM,WCDMA,

LTE

CN= CS, PS, EPC NEP #1

Element Manager

NEP #2

RAN CN

Element Manager

MV OSS Systems

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

FM= Fault Management

CM= Configuration

Management

Stats= Statistics /Counters

for Performance

Management

Event/Trace =

Event/Trace for

Performance Management

N-Itfs

Example: SON and OSSii

RAN CN

NEP #1

Element Manager

NEP #2

RAN CN

Element Manager

MV C-SON Systems

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

Step 1: Data from network

is uploaded to MV C-SON

system

N-Itfs 1 1

Example: SON and OSSii

RAN CN

NEP #1

Element Manager

NEP #2

RAN CN

Element Manager

MV C-SON Systems

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

2 Step 2 Data is processed

by C-SON algorithm

PSC

MLB

ANR

N-Itfs

Example: SON and OSSii

RAN CN

NEP #1

Element Manager

NEP #2

RAN CN

Element Manager

MV C-SON Systems

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

F

M

C

M Sta

ts

Eve

nt/

Tra

ce

Step 3: Configuration

changes are pushed back

to the network

N-Itfs

3

Challenge - Cost of interoperability

Element Manager

NEP #1

Wireless Network

MV OSS Systems

Wireless NEP #1

Wireless Network

NEP #2

N-Itfs

Element Manager

NEP #2

Challenge - Upgrades

MV OSS Systems

Element Manager

(Release n)

Wireless Network

NEP #1 Release n

Wireless

Element Manager

Wireless Network

NEP #2

N-Itfs

Element Manager

(Release n+1)

Wireless Network

NEP #1 Release N+1

Impact on NBI

caused by

release upgrade

Upgrade

OSSii is complementary to standards

• Shared specifications under OSSii

include proprietary elements

• Shared documents include, in

addition to specifications

– Sample files

– Roadmap

– Compatibility plan

– Testing possibility

OSS Northbound

Interface specification

Proprietary

elements

Standardised

OSSii - New collaboration model

Without OSSii:

No

business

relationship

Strong

co-ordination

needed

Operator (dedicated Integration

Project)

NEP ISVs for MV OSS

With OSSii:

OSSii

License

agreement

Operator (off-the shelf)

ISVs for MV OSS NEP

Advantages for Operators

Wit Shorter Integration time Buy off-the shelf products

Time GA

OSSii pre-integration in NEP lab

NBI integration on site

Before new/updated network version

reaches the live network, the NBI

integration between NEP and ISV version

has already been done.

Operator can by off-the-shelf products

instead of starting an “integration project”

each time.

Less coordination

Communication channel between NEP and

ISV is built by OSSii.

NEP will support ISVs directly.

Less or no co-ordination needed by operators.

With OSSii

Without OSSii

Advantages for ISVs / 3rd parties

Technical support from NEPs From passive response to active planning From project to product

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 documents are provided

Life-cycle management of NBIs

.

Sound framework to replicate NBI

integration in mass.

OSSii progress

Initiating parties signed a Memorandum of

Understanding

MoU is publically available at www.ossii.net

2013

MoU

2014

2015

Initiating parties signed bilateral cross license

agreements

Interoperability tests are started

Bi-lateral

License

agreemen

t

Bi-lateral

License

agreemen

t

Bi-lateral

License

agreemen

t

Bi-lateral

License

agreemen

t

2015

Bi-lateral

License

agreements

Bi-lateral

License

agreemen

t

Bi-lateral

License

agreements

First ISVs are signing license agreements using

OSSii framework with different NEPs

respectively

OSSii Progress and Growth of the ecosystem

Initiating Parties

ISV

ISV

NEP

ISV

ISV

ISV

NEP

ISV

ISV

Operators Endorsement

ISV

2013/14

2015

> 2015

More ISVs are in the pipe to sign license agreement still in 2015!

How to sign an OSSii agreement

NDA

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

• As a very first step a NDA will be signed

Bi-lateral agreement

• Bi-lateral negotiations with all NEPs separately

• Signature of bi-lateral license agreement (ISV – NEP)

Post Agreement

• 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