ipr management report - cognet · d1.3 – ipr management report cognet version final page 3 of 23...

IPR Management Report

Gallico Domenico (IRT)

Matteo Biancani (IRT)

Document Number D1.3

Status Final

Work Package WP 1

Deliverable Type Report

Date of Delivery 31/October/2017

Responsible Unit IRT

Contributors Domenico Gallico, Matteo Biancani (IRT),

Alberto Mozo Velasco (UPM), Diarmaid

Brennan, Martin Tolan (WIT), Angel Martin,

Sean Gaines (VICOMTECH), Sandra Buda,

Haytham Assem (IBM), Olga Uryupina

(UNITN), Imen Grida Ben Yahia (Orange), Udi

Margolin (NOKIA), Antonio Perales, Diego

Lopez (TID), Mikhail Smirnov (Fraunhofer

FOKUS)

Keywords IPR management.

Dissemination level PU

D1.3 – IPR Management Report

CogNet Version final of 23

Change History

Version Date Status Author (Unit) Description

0.1 25/07/2017 Draft Domenico Gallico (IRT)

Matteo Biancani (IRT)

ToC definition

0.2 04/10/2017 Draft Domenico Gallico (IRT) IRT first contribution

0.4 09/10/2017 Draft Alberto Mozo (UPM) UPM contribution

0.5 10/10/2017 Draft Antonio Pastor, Diego

Lopez (TID)

TID first contribution

0.6 12/10/2017 Draft Diarmaid Brennan (WIT) WIT contribution

0.7 23/10/2017 Draft Domenico Gallico (IRT) Consolidated version

0.8 24/10/2017 Draft Gorka Velez, Angel

Martin, Sean Gaines (VIC)

VIC inputs

0.9 25/10/2017 Draft Domenico Gallico, Matteo

Biancani (IRT)

Ready for review version

1.0 27/20/2017 Draft Domenico Gallico (IRT) Reviewer’s comments addressed

1.0 31/10/2017 Final Domenico Gallico (IRT) Final Version



Executive Summary

This document is D1.3, titled “IPR Management Report”, and pertaining to

the WP1 “Project Coordination” of the H2020 CogNet project. The CogNet

research project aims at developing a real-time and high performing

network management platform able to process data gathered from wide

network infrastructures and to provide self-managing capabilities using

different machine learning algorithms.

This deliverable will analyse all the IPRs (Intellectual Property Rights)

involved in the project. This analysis will cover the list of all background

IPRs, sideground IPRs, and foreground IPRs, together with a description of

policies and practises the CogNet consortium adopted for IPR

management. Due to the collaborative nature of the CogNet project, the

outcomes (representing the foreground) are owned by the partners who

developed or contributed by developing the different components or

algorithms.

In the first section we will describe the guidelines adopted to protect IPR

that has been originated in the project, together with a short description

of the different license models taken into consideration for project

purposes. Section two will report about the way the consortium partners

have carried out the IPR analysis. The remaining sections list and describe

the background, sideground and foreground of the project. In this last

section we will associate the related license model or access right to each

software component or algorithm identified.



Table of Contents

1. IPR Management Guidelines ........................................................................................... 5

2. Licensing Models............................................................................................................... 7

2.1. Software Licensing ......................................................................................................................................... 7

2.2. Types of Software Licenses ........................................................................................................................ 7

3. IPR Management Process................................................................................................. 9

4. Background ..................................................................................................................... 10

5. Sideground ...................................................................................................................... 11

6. Foreground: assets identification .................................................................................. 12

7. Conclusion ....................................................................................................................... 15

Appendix A. Proprietary Licenses ..................................................................................... 17

A.1. VICOMTECH Foreground License .......................................................................................................... 17

A.2. IBM Proprietary License ............................................................................................................................. 17

A.3. Open5GCore License .................................................................................................................................. 17

A.4. UNITN research purpose license ............................................................................................................ 18

A.4.1. LIBLINEAR-LD ....................................................................................................................................... 18

A.4.2. LSP-CLUSTER ........................................................................................................................................ 19

A.4.3. LSSVM/LSP ............................................................................................................................................ 20



1. IPR Management Guidelines

Due to its intangible nature, the diversity of use and the various means available to create value

from it, the creation of software can become a complex asset to protect against fraud, illegal or

unauthorized use. With this in mind, an appropriate IPR management is an essential tool to

secure and protect value generated by software, especially considering that contract

formalization usually takes the form of licence agreements, imposing specific usage rules on third

parties intending to exploit the software. Developing software can be defined as a creative task,

relying on the coding and development abilities of a developer and also on the ability of

translating the functional and operational requirements defined during the designing phase into

a sequence of instructions. The schema reported below [1] describes a typical software

development process and the multiple IPRs that can be generated.

Figure 1-1: Software development process

The project CA defines all the guidelines that regulate the access rights to the different IPRs, both

for the contributed background, and for the foreground or results. These guidelines describe the

rights any of the actors have on the IPRs involved in the project. The actors that come into play

can be distinguished essentially in two categories: project partners, and external parties. In what

concerns project partners, they have granted free access to the foreground produced by any

other partner in the consortium during and after the project life span for purposes of achieving

interoperability of software, for commercial and non-commercial research, for dissemination and

for commercial and non-commercial demonstration while for other purpose they have access at

fair and reasonable conditions. On the other hand, the access rights to background owned by



other project partners shall be granted on Fair and Reasonable Conditions to be negotiated in

good faith between the concerned Parties.

In what concerns external parties, each project partner who has developed a

component/software or part of it, should decide whether to distribute or make available the code

under controlled and proprietary license terms or as open-source. This process has been

reflected and described in the following sections.



2. Licensing Models

The intention of using open-source licensing agreements was outlined in the proposal,

considered in the project DoW, and specifically discussed in the ‘Open Sources Strategy’ section

within the impact section of the grant agreement.

A central aim of the consortium is to provide benefit to the European research community. In

order to reach a wider audience and disseminate our research activities and its results, most of

the project partners will be either using Open Source code in their developed components or

contributing their deliverables to the Open Source communities. Furthermore, some of the

partners have contributed to open standardization bodies.

Subject to the internal processes of all partners for the management of their IPR, the CogNet

consortium intends to release a large proportion of the software modules and user prototype

services developed within the project as open source. This does not apply to pre-existing

(background) software that project partners have brought into the project, and extensions to be

developed thereof, and could be interacting with the developed open source components.

2.1. Software Licensing1

For a license to be valid it must be granted by the owner of the work's intellectual property

rights. Under the policies of most research institutions and commercial companies, developers

who have created a piece of software are unlikely to own full rights to their works. Instead, the

organization generally holds or shares legal right to developed software. Policies on IPR

ownership vary, but in most cases the organization will be the legal rights owner, and will be the

entity that grants the license chosen for the produced software.

2.2. Types of Software Licenses

Colloquially speaking, the spectrum of software licensing strategies can be divided into three

categories: “free and open source”, “proprietary” or a hybrid of the two.

Free and Open Source Software (FOSS) Licensing: Free and open source software (FOSS)

represents a fundamentally different approach from the proprietary software licensing.

The primary intent of FOSS is to give the licensor the ability to maximise the output of

1 http://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1002598#s3



their software by breaching barriers to software use, dissemination, and follow-on

innovation. There are some of the most used FOSS licenses, which are listed in D6.3 [2],

each with small but significant changes, but all grant free (as in freedom), open, and non-

discriminatory access and rights to modify licensed software and associated source code.

A common misconception is that FOSS is synonymous with “non-commercial.” In fact, as

described by the two most influential definitions of FOSS, “non-discriminatory” means

that no category of user or distributor can be prohibited, including for-profit commercial

entities. Due to this, FOSS-licensed software can be, and often is commercially exploited.

Due to the simplicity of the FOSS licenses and their non-discriminatory nature, they offer

continued development and collaboration when researchers switch organisations, and

when they collaborate across organisations. FOSS can also help to extend the useful

lifetime of a piece of software beyond the direct involvement of the creators.

Proprietary Licensing: The main purpose of a proprietary software license is to limit the

use of software. As a result, proprietary licenses are often very restrictive for end-users

because they are in line with the software owners’ business strategy. They typically allow

the user to interact with most of the software but in a restrictive manner. Other aspects of

a proprietary license are to only allow use on a single computer, to forbid users from

copying, redistributing, or altering the work, and specifically to prohibit the creation of

derivatives using parts of the work. Importantly, programs under proprietary licenses are

typically distributed only in binary form and forbid examination of the program code or

reverse engineering of any part of the program.

Hybrid Software Licensing: Some software developers find that their needs are not well

met by using either proprietary or FOSS licensing models. In these cases, hybrid

approaches—combining a FOSS license with a proprietary “closed” license—are

sometimes used. Under this strategy, the rights owner chooses which license to apply on

a case-by-case basis. When ownership and licensing rights are clear, these licensing

schemes can maintain some of the benefits of FOSS while also permitting creators to

employ multiple business models. The downside can be a significant added burden for

the rights owner in applying, administering, and enforcing multiple licenses. This has

generally limited the adoption of hybrid license models to large and very specific

software development initiatives.



3. IPR Management Process

The purpose of the IPR management process is to outline a strategy for the protection of the

project results aiming also at steering the exploitation roadmap of the partners. The process

is made of four steps and has been active and running for the whole project duration.

1. Background identification: This step started during the proposal phase, where some of

the partners have listed their know-how and/or software that forms the background of

the project.

2. Sideground identification: As for the previous step the identification of the possible

project sideground has been continuously updated during the project life span.

3. Foreground identification: all the partners who have developed software components

or machine learning algorithms have been requested to list and make them available on

the project code repository, namely github. The CogNet github repository is available at

this link: [https://github.com/CogNet-5GPPP]. This repository is private and accessible

only to project partners by means of credentials.

4. Foreground classification: each partner who has developed software components or

machine learning algorithms is in charge of deciding which license to be used for such

items, according to the license listed and described in section 6 of this document. The

resulting table is reported in section 6.

5. Rules and policies: all project partners have been requested to comply with the policies

and rules stated in the CA, and briefly summarized in section 1 of this document.



4. Background

All the CogNet partners brought some assets to the project such as data, know-how or software

that have been identified during the proposal phase and listed in our CA. These assets constitute

the project background.

To avoid that this use (or re-use) of background leads to any breach of obligations, or possibly an

infringement of intellectual property rights belonging to others, CogNet partners have identified

the background needed for the project and reported it in the following table

Background Type (software,

hardware,

patent…)

Owner Licensing

model/Access

model

OpenVIM Software TID Apache License

Version 2.0,

January 2004 [3]

OpenMANO Software TID Apache License

Version 2.0,

January 2004 [3]

Open5GCore toolkit Software Fraunhofer Open5GCore

License A.3

Open5GMTC toolkit Software Fraunhofer On demand

licensing (full

source code either

as a complete

testbed or as

individual

components for

R&D)

FOKUS NFV Orchestrator

and extensions towards

external machine learning

APIs

Software Fraunhofer Apache License

Version 2.0,

January 2004 [3]

FP7 ONTIC project results Software code of the

algorithms produced by

UPM in ONTIC

UPM Apache License

Version 2.0,

January 2004 [3]

Table 4-1: Project background



5. Sideground

The table below reports the project sideground, corresponding to software and knowledge

generated by the partners during the project period but outside it.

Sideground Type (software,

hardware, patent…)

Owner Licensing model/Access

model

Mouseworld Lab Software and Hardware TID & UPM Access model defined case-by-

case by direct MoU signature

between the accessor and the

owner(s)

Licensing: Multiples licenses

involved:

Traffic Generator:

(commercial license,

granted by a third party to

TID)

Tstat: GNU GPL version 3,

2007 license [4]

Table 5-1: Project sideground



6. Foreground: assets identification

The table below lists all the components or software modules that constitute the result of the

project R&D activity. For each of the components listed we specified the owner, the related WP

and the associated license type. Most of the foreground knowledge is associated to well-known

open source license types, while some of them can be used and distributed under proprietary

licenses, which are reported in Annex A of this document. Any other update should occur from

the time of this writing until the end of the Project it will be reported in D6.4.

Component Owner WP License

Common Infrastructure All 6 Apache License Version 2.0,

January 2004 [3]

ADE: Anomaly Detection with

LSTM

IBM 3 IBM Proprietary licence [A.2]

NDP: Network Demand

Prediction


NTC: Network Traffic

Classification

IBM 3 Apache License Version 2.0,

January 2004 [3]

RCMR: Recurrent Crowd Mobility

Recognition


TCDC IBM 3 Apache License Version 2.0,

January 2004 [3]

ModelsDiff: Log-based

Behavioural Differencing

Nokia 3 Apache License Version 2.0,

January 2004 [3]

ML4MQ Orange 3 Apache License Version 2.0,

January 2004 [3]

Forward EC: Forward Event-

Chain Monte Carlo simulation

Module

Orange 3 Apache License Version 2.0,

January 2004 [3]

FunPrev Orange 3 GNU GPL version 3, 2007 [4]

FunCo Orange 3 GNU GPL version 3, 2007 [4]



Network Threats (malware

detection with honeynet)

TID 5 Apache License Version 2.0,

January 2004 [3]

Traffic Classification TID / UPM 4 Apache License Version 2.0,

January 2004 [3]

NetSpark UNITN 3 Apache License Version 2.0,

January 2004 [3]

SPARK-TK: Machine Learning for

Structural Input

UNITN 3 Apache License Version 2.0,

January 2004 [3]

LSSVM-SP: Structured Output

Prediction

UNITN 3 UNITN research purpose license

[A.4.3]

GED (Geographical Event

Detection)

UNITN 4 Apache License Version 2.0,

January 2004 [3]

RelationalTextRanking UNITN 4 Apache License Version 2.0,

January 2004 [3]

Liblinear-ld UNITN 5 UNITN research purpose license

[A.4.1]

Lsp-cluster UNITN 5 UNITN research purpose license

[A.4.2]

Spark IterFS UPM 3 GNU GPL version 3, 2007 [4]

PICS/PPICS UPM 3 GNU GPL version 3, 2007 [4]

PSCEG: Parallel Subspace

Clustering using Exact Grids

UPM 3 GNU GPL version 3, 2007 [4]

TSDP: Time Series Data Pre-

processing

UPM 4 Apache License Version 2.0,

January 2004 [3]

MoSeS (Model Selection Service) UPM 4 Apache License Version 2.0,

January 2004 [3]

Connected-cars-ml: Mobility

Pattern Prediction

VICOM 3 VICOMTECH Foreground License

[A.1]

Connected-cars-ml:

Optimisation of Network

VICOM 4 VICOMTECH Foreground License

[A.1]



Configuration

Distributed Application

Performance Optimizer

VICOM 3 GNU GPL version 3, 2007 [4]

Table 6-1: Project foreground



7. Conclusion

This deliverable reports the IPR management practices within the CogNet project. Guidelines and

policies are aligned with the original provisions made by the Grant Agreement and the

Consortium Agreement.



Appendix A. Proprietary Licenses

In this Appendix we report the proprietary licenses issued by the different partners that regulate

the access rights of the respective components designed and developed within the CogNet

project.

A.1. VICOMTECH Foreground License

Under a foreground licensing scheme, the Results will be made available under the terms,

conditions and access regime set forth in the Consortium Agreement.

A.2. IBM Proprietary License

In accordance with the CogNet Consortium Agreement, access rights to results for exploitation

shall be granted to any interested Parties, subject to a separately negotiated written agreement,

on fair and reasonable conditions.

A.3. Open5GCore License

Open5GCore is available under a paid licensing model. The most common and best flexibility

model is that of source code license for internal use. However, also lower cost binary-only

options are available. On the upper range, Open5GCore modules code may be licensed even for

inclusion within commercial products. For more information, prices, as well as a customized offer

including all the licensing terms, please contact us with your requirements via email.

When you require additional equipment, such as LTE/5GBase Station and Prototypes, IMS Core

Network and Clients, suitable mobile phone and/or modems as well as SIM/USIM/ISIM/CSIM

cards, we would be happy to assist you towards building your comprehensive testbed. Best-effort

support for using the software is offered with each license and additional technical support

bundles are available upon request. Additional features, components or extensions of reference

points can be developed under the umbrella of defined R&D projects with Fraunhofer FOKUS.

The Open5GCore team is also offering coaching, training, tutorials on 5G/LTE, NFV/SDN and IMS,

as well as support for local deployment and integration activities.



A.4. UNITN research purpose license

The licenses reported below pertain to the access rights for the components developed by

UNITN. These licenses grant free access only for research and education purposes.

A.4.1. LIBLINEAR-LD

Available from the EU H2020 CogNet project repository.

Authors: Alessandro Moschitti ([email protected]), Iryna Haponchyk

([email protected]).

Department of Information Engineering and Computer Science – DISI.

Via Sommarive, 9 I-38123, Povo (TN), Italy.

LICENSING TERMS

This program is granted free of charge for research and education purposes. However you must

obtain a license from the author to use it for commercial purposes.

Scientific results produced using the software provided shall acknowledge the use of LIBLINEAR-

LD. Please cite as:

I. Haponchyk and A. Moschitti: “Don’t understand a measure? Learn it: Structured Prediction for

Coreference Resolution optimizing its measures”. ACL, 2017.

Moreover the authors of LIBLINEAR-LD shall be informed about the publications. The software

must not be modified and distributed without prior permission of the authors.

By using LIBLINEAR-LD you agree to the licensing terms.

NO WARRANTY.

BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY

FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT

WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER

PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND,

EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE

PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME

THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING



WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR

REDISTRIBUTE THE PROGRAM, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY

GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF

THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO

LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY

OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED

OF THE POSSIBILITY OF SUCH DAMAGES.

A.4.2. LSP-CLUSTER






This software extends the SVM-Struct software. Available at

https://www.cs.cornell.edu/people/tj/svm_light/svm_struct.html.

Author: Thorsten Joachims ([email protected])

Cornell University

Department of Computer Science

4153 Upson Hall

Ithaca, NY 14853

USA

LICENSING TERMS



Scientific results produced using the software provided shall acknowledge the use of LSP-

CLUSTER. Please cite as:





and

I. Tsochantaridis, T. Hofmann, T. Joachims, and Y. Altun: “Support Vector Learning for

Interdependent and Structured Output Spaces”. ICML, 2004.

Moreover the authors of LSP-CLUSTER shall be informed about the publications.

The software must not be modified and distributed without prior permission of the authors.

By using LSP-CLUSTER you agree to the licensing terms.

NO WARRANTY



















A.4.3. LSSVM/LSP








This software extends the SVM-Struct software. Available at

https://www.cs.cornell.edu/people/tj/svm_light/svm_struct.html.

Author: Thorsten Joachims ([email protected])

Cornell University

Department of Computer Science

4153 Upson Hall

Ithaca, NY 14853

USA

LICENSING TERMS



Scientific results produced using the software provided shall acknowledge the use of LSSVM/LSP.

Please cite as:



and

I. Tsochantaridis, T. Hofmann, T. Joachims, and Y. Altun: “Support Vector Learning for

Interdependent and Structured Output Spaces”. ICML, 2004.

Moreover the authors of LSSVM/LSP be shall informed about the publications. The software must

not be modified and distributed without prior permission of the authors.

By using LSSVM/LSP you agree to the licensing terms.

NO WARRANTY





References

[1] IPR management in software development (https://www.iprhelpdesk.eu/Fact-Sheet-IPR-

Management-in-Software-Development)

[2] D6.3 - Final release of the integrated platform and performance reports

[3] Apache License Version 2.0, January 2004 (https://www.apache.org/licenses/LICENSE-2.0)

[4] GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 (https://www.gnu.org/licenses/gpl-

3.0.en.html)

ipr management report - cognet · d1.3 – ipr management report cognet version final page 3 of 23...

Documents