intellectual property in software: the good, the bad and

51

Upload: others

Post on 18-Dec-2021

5 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Intellectual property in software: the good, the bad and
Page 2: Intellectual property in software: the good, the bad and

Intellectual property in software: the good, the bad and the ugly Catarina Maia

INESC TEC

Head of the Technology Licensing Office

SnT – 31/05/2018

Page 3: Intellectual property in software: the good, the bad and

3

INESC TEC Intellectual Property Rights Copyrights and Open Source Patents Trade secrets Technology and products

Page 4: Intellectual property in software: the good, the bad and

INESC TEC Academia Companies

To be an international player in the science and technology arena To be perceived as an important world player, in the domains of Computer Science, Industry and Innovation, Networked Intelligent Systems, and Power and Energy

Economic and social fabric development Contribute to the performance, competitiveness and internationalisation of Portuguese companies and institutions

Bringing academia, companies, public administration and society closer together

Mission

4

Vision

Research of excellence International recognition Social relevance

Page 5: Intellectual property in software: the good, the bad and

Associates

New model to improve the intervention capacity of the university and the polytechnic

5

Partnerships Privileged partners

Special Partnerships

Partnerships with International Universities FCT

Evaluation: Excellent

Page 6: Intellectual property in software: the good, the bad and

725 researchers (+350 PhDs) dedicated to R&D and advanced consulting

Hired staff (of which 25 have PhDs) Professors (mean time allocation: 50%)

60 210

Senior Researchers

Researchers

Other Collaborators

270

395

220

Support Services Organisation & Management Business Technical

45 10 20

Postdoctoral researchers Research assistants PhD students

70 180 145

75

6

Affiliated Researchers 60

100 105

15

External researchers Research trainees Special projects

(mean time allocation: 30%)

Page 7: Intellectual property in software: the good, the bad and

Maximising synergies to generate impact

EDP Installation of a smart meter that supports a bidirectional information flow, allowing for an increased efficiency in the operational, technical and commercial management of the electricity distribution network. EXAMPLE OF R&D CONTRACTS

Power and Energy

CLUSTER

Tools for Planning and Operating Grids

Renewable Energy Integration

Smart Grids

Electric Mobility

Forecasting Systems

Power Systems Reliability Evaluation

Computational Intelligent Tools 7

Page 8: Intellectual property in software: the good, the bad and

INE

SC

TE

C |

AP

RE

SE

NTA

ÇÃ

O IN

STI

TUC

ION

AL Internal and external

logistics systems for small series, with RFID product identification. Improved operations management.

Business Collaboration Networks

Operations Management and Logistics

Service Design and Engineering

Optimisation and Decision Support Systems

Performance Management

Industrial Robotics

Innovation and Technology

Management

Entrepreneurship

Maximising synergies to generate impact

EXAMPLE OF R&D CONTRACTS

Industry and Innovation

CLUSTER

KYAIA

8

Page 9: Intellectual property in software: the good, the bad and

Communication Networks

Robotics

Optical Sensors

Real-Time Systems

Medical Applications

Image and Video Technologies

Music Technologies

A. Silva Matos Development of an underwater platform for ocean monitoring and exploration.

Maximising synergies to generate impact

Networked Intelligent Systems

EXAMPLE OF R&D CONTRACTS

CLUSTER

9

Page 10: Intellectual property in software: the good, the bad and

Computer Graphics & Gamification

Software for Critical Systems

Big Data Processing

IT Security

Porto de Leixões

Maximising synergies to generate impact

Information system to manage port authority processes based on georeferenced information.

Information Management

Mobile and Wearable Computing

Data Mining

Cloud Computing EXAMPLE OF R&D CONTRACTS

Computer Science

CLUSTER

10

Page 11: Intellectual property in software: the good, the bad and

HASLab High-Assurance Software

LIAAD Artificial Intelligence and Decision Support

CRACS Advanced Computing Systems

CPES Power and Energy Systems

CSIG Information Systems and Computer Graphics

CRAS Robotics and Autonomous Systems

CITE Innovation, Technology and Entrepreneurship

CESE Enterprise Systems Engineering

CEGI Industrial Engineering and Management

CAP Applied Photonics

CTM Telecom. and Multimedia

C-BER Biomedical Engineering

Cluster Power and Energy Coordination

Cluster Networked Intelligent Systems Coordination Cluster Computer Science Coordination

CRIIS Robotics in Industry and Intelligent Systems

Council of R&D Centres Cluster Industry and Innovation Coordination

11

R&D Centres organised into Clusters: multidisciplinarity, flexibility, synergies and strategic alignment

Page 12: Intellectual property in software: the good, the bad and

Projects build a value chain to turn science into economic value

0% 20% 40% 60% 80% 100%

INESC TEC

Power and Energy

Industry and Innovation

Networked Intelligent Systems

Computer Science

% results

Advanced Training Papers in Scientific Journals Theses

Conference Proceedings Models

Prototypes Demonstrators

Consulting Patents Licensing Spin-offs People

Knowledge Production Applied Research Development Technology Transfer

Integrated value chain

12

TRL – Technology readiness levels

Page 13: Intellectual property in software: the good, the bad and

13

INESC TEC Intellectual Property Rights Copyrights and Open Source Patents Trade secrets Technology and products

Page 14: Intellectual property in software: the good, the bad and

14

The Good, the Bad, and the Ugly

Page 15: Intellectual property in software: the good, the bad and

15

Intellectual Property Rights

Source: European IPR Helpdesk

Page 16: Intellectual property in software: the good, the bad and

What does IP protection grant?

•  The right (but not the obligation)

•  To use

•  To exploit commercially •  To sell •  To license

16

Page 17: Intellectual property in software: the good, the bad and

17

Different IPRs in a product

Functionality •  Patent •  Trade secret

Design

Expression • Copyright

Trademark • Differentiation in

the market

Page 18: Intellectual property in software: the good, the bad and

18

Different IPRs in the same product

PAGERANKTM

Page 19: Intellectual property in software: the good, the bad and

19

Different IPRs in the same product

PAGERANKTM

Page 20: Intellectual property in software: the good, the bad and

20

IPRs through time

Patent Copyright Trademark

20 years 70 years Indefinite

No functionality High functionality

Max. validity of IPR

Functionality

Page 21: Intellectual property in software: the good, the bad and

21

INESC TEC Intellectual Property Rights Copyrights and Open Source Patents Trade secrets Technology and products

Page 22: Intellectual property in software: the good, the bad and

22

Copyright

“The domain of copyright is the protection of literary and artistic works. These include writings, music, and works of the fine arts, such as paintings and sculptures, and technology-based works such as computer programs“ – WIPO

Protects the creative expression - and not the ideas in it

Registration is not necessary, but possible

-  Use

-  Distribution

Page 23: Intellectual property in software: the good, the bad and

Classical copyright licenses – The Good

•  EULA – End User License Agreement •  Binary files •  Instructions manual •  No sublicensing rights •  One installation

•  Proprietary software licenses •  Binary files and/or source code •  Code documentation •  Code modification/reimplementation may be allowed •  With/without sublicensing rights •  Control over number of copies and installation

23

Page 24: Intellectual property in software: the good, the bad and

24

Free software (open source)

•  The freedom to run the program as you wish, for any purpose (freedom 0).

•  The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1).

•  The freedom to redistribute copies so you can help your neighbor (freedom 2).

•  The freedom to distribute copies of your modified versions to others (freedom 3).

Source: https://www.gnu.org/philosophy/free-sw.html

…but rather as in “free bird”.

Not free as in “free beer”…

Page 25: Intellectual property in software: the good, the bad and

Copyleft in Software

•  Copyright vs Copyleft •  Proprietary vs Free •  Contain vs Disseminate •  Use vs Modify •  Control vs Enable

•  “Copyleft is a general method for making a program (or other work) free, and requiring all modified and extended versions of the program to be free as well” - https://www.gnu.org/copyleft/copyleft.html

25

Page 26: Intellectual property in software: the good, the bad and

26

FOSS licenses – The Good

Source: European IPR Helpdesk

Page 27: Intellectual property in software: the good, the bad and

Public domain licenses

•  No restrictions

•  No attribution needed

•  Totally free to do whatever you want

Example: WTFPL

27

Page 28: Intellectual property in software: the good, the bad and

Academic Licenses

•  Very permissive, typically allowing sublicensing under proprietary licenses

•  Obligations often aimed at ensuring due attribution of copyright

•  These are not Copyleft licenses

Example: MIT, BSD, Apache

28

Page 29: Intellectual property in software: the good, the bad and

Reciprocal Licenses

•  Distribution of the SW requires that it be licensed under the same terms

•  Obligations mainly aimed at ensuring that the SW remains free (as a bird)

•  These are Copyleft licenses

Example: GNU GPL v2, GNU GPL v3, GNU AGPL

29

Page 30: Intellectual property in software: the good, the bad and

Contextual Licenses

•  Activation of Copyleft clause depends upon the context of use

•  Allow keeping the SW free without jeopardizing the confidentiality of the proprietary SW

Example: LGPL v3

30

Page 31: Intellectual property in software: the good, the bad and

Hybrid Licenses

•  Mixes elements of academic and reciprocal licenses

•  Allows integration with proprietary software without disclosure but obliges any modifications to be made available as open source

Example: MPL

31

Page 32: Intellectual property in software: the good, the bad and

32

Compatibility – the Bad

Source: European IPR Helpdesk

Page 33: Intellectual property in software: the good, the bad and

FOSS issues in successful market adoption – the Ugly

•  Lack of proper documentation of FOSS included in the code •  Provisions regarding the use of FOSS in the contract

•  Incompatible licenses

•  Static linkage •  Code contamination with GPL/LGPL

•  Lack of license in GitHub •  Full copyright

•  Patent provisions in the FOSS license (Apache 2.0, GPL3) •  Disclosure can save time

33

Page 34: Intellectual property in software: the good, the bad and

34

INESC TEC Intellectual Property Rights Copyrights and Open Source Patents Trade secrets Technology and products

Page 35: Intellectual property in software: the good, the bad and

What can be patented? – The Good

•  A invention: a new, technical solution to a technical problem •  Discoveries

•  Disclosure (vs. trade secret)

•  Protection up to 20 years

•  Geographic right

35

Page 36: Intellectual property in software: the good, the bad and

What is patentable in software?

36

Software patents

Improvements in computer operation

Controlling machines

Interaction with real world Protocols

Data compression

Technical simulations

Page 37: Intellectual property in software: the good, the bad and

Patentability criteria – the Bad

•  Novelty •  Not known to the public at patent application

•  Inventive step (non-obviousness) •  Should not derive, as a consequence, of the state of the art

•  Industrial application (utility) •  An invention which can be made/used in some kind of industry

37

Page 38: Intellectual property in software: the good, the bad and

Common pitfalls – the Ugly

•  Premature disclosure

•  Unintentional disclosure

•  Lack of inventive step

•  Open source licenses with anti-patenting clauses

38

Page 39: Intellectual property in software: the good, the bad and

39

INESC TEC Intellectual Property Rights Copyrights and Open Source Patents Trade secrets Technology and products

Page 40: Intellectual property in software: the good, the bad and

40

Trade secrets

•  Methods

•  Technology

•  Algorithms

•  Code

•  Know-how

•  Commercially valuable

•  Commercial advantage derives from the secret

•  Technical and non-technical measures in place •  Different access levels •  NDA

Page 41: Intellectual property in software: the good, the bad and

41

Trade secrets – the Good and the Bad

•  No time limit

•  No fees

•  No geographical restrictions

•  Publication is not possible

•  Technical measures can be hard to implement

•  Non-technical measures can be inefficient

•  Expensive to keep

Page 42: Intellectual property in software: the good, the bad and

42

Secret Patent

Others can build on your

technology

Exclusive right

Appropriation

No advancement of science

The balance between secrets and disclosure – the Ugly

Page 43: Intellectual property in software: the good, the bad and

INESC TEC

Intellectual Property Rights

Copyrights and Open Source

Patents

Trade secrets

Technology and products

43

Page 44: Intellectual property in software: the good, the bad and

What kind of scientist are you?

Stokes (1997) – Pasteur’s Quadrant

Page 45: Intellectual property in software: the good, the bad and

People buy products

Page 46: Intellectual property in software: the good, the bad and

46

The Ugly – how can we reach the market?

When do I have an invention?

Technology

Novelty

Inventive step

"Eureka arkimedi" by Arlindi1999 - Own work. Licensed under CC BY-SA 3.0 via Wikimedia Commons http://commons.wikimedia.org/wiki/File:Eureka_arkimedi.jpg#mediaviewer/File:Eureka_arkimedi.jpg

Page 47: Intellectual property in software: the good, the bad and

47

The Ugly – how can we reach the market?

When can I publish?

After filing a patent

After validating that your code

- Is protected

- Is not a secret

- Has a proper license in place

Page 48: Intellectual property in software: the good, the bad and

48

When should I contact the TTO?

Idea

Research Disclosure to the TTO

Lab testing

and validation

Market strategy

Protection strategy Prototype

Marketing Licensing

Page 49: Intellectual property in software: the good, the bad and

49

The invention disclosure

Patentability analysis

Ownership analysis – coordination with third parties

Conduct initial market assessment

Determines what is the asset we are discussing for valorization

Page 50: Intellectual property in software: the good, the bad and

50

A few tips…

Premature publication

Unintentional disclosure

IP contamination

FOSS incompatibility

- Patentability

- Incompatibility among licenses

- Incompatibility with the business model

… Patent literature is over 10x larger - conducting patent searches can help you not to reinvent the wheel!

Page 51: Intellectual property in software: the good, the bad and

•  INESC TEC

•  R DR. ROBERTO FRIAS

•  4200-465 PORTO

•  PORTUGAL

T +351 222 094 000 F +351 222 094 050 in [email protected] t www. inesctec.p t