Could human-driven approach revolutionize our use of data? What is IHAN project all about in technical matter?

1. Could human-driven approach revolutionize our
use of data?
House rules:
1. Questions to Skype chat
2. Slides will be published
3. Be active
Future vision from Sitra

2. Agenda
What is the IHAN ® project on human-driven data economy about?
Jaana Sinipuro (15min)
What does IHAN® change?
Antti Larsio (15min)
What are the IHAN® technical specifications?
Jyrki Suokas (15 min)
IHAN® and industry pilot approach
Jyrki Suokas (5 min)
How is IHAN® project proceeded?
Juhani Luoma-Kyyny (20min)
What does IHAN® Standardisation (Cen-Cenelec) process mean?
Markus Kalliola (10min)
Questions and Answers
Everybody (20min)
Next steps
5 min
Webinar ends

3. 5 key facts about Sitra
1. A gift from Parliament to the 50-year-old
Finland.
2. An independent foresight agency:
futurologist, researcher, visionary,
developer, experimentalist, partner, trainer,
networker.
3. Funded by returns on endowment capital
and capital investments.
4. Envisages Finland as a successful pioneer in
sustainable well-being.
5. Its vision is supported by three themes, six
focus areas and dozens of projects.
+1
Building our future
together

4. What is the IHAN® project on human-driven data
economy about?
Jaana Sinipuro (15min)

5. Who creates the data in the future?
19901980 2015
Well-beingandtheeconomy
2000
Data collected by individuals /
unregulated data
Data collected by professionals /
regulated data
A H I S T O R I C C H A N G E

6. Trust
A H I S T O R I C C H A N G E

7. From storing data to sharing data (human-driven control)
A H I S T O R I C C H A N G E

8. The momentum is right now…
#GDPR
General Data Protection Regulation
#PSD2Payment Services Directive
#EIDASEU regulation on electronic
identification and trust services for
electronic transactions

9. EU strategies in support
# Digital single Market
Free flow of non-personal data
# European Data Economy
Data is an essential resource for economic growth
# Digitising European Industry
The Internet of Things (IoT), cloud computing, big data and data analytics,
robotics and 3D printing

11. GDPR Article 20 : Right to data portability
Current regulation is a good start, but even with Article 29
Working party clarifications*, it does not define the
format, governance nor method for personal data sharing
in our real-time, many-to-many world
“structured, commonly used and machine-readable format” needs to
be unambiguously and explicitly defined for personal data across all
industries so automated data interchange is possible
“… personal data transmitted directly from one controller to
another, where technically feasible. ” protocols for real-time transfer
of information do not exist and thus need to be created
“the data subject has given consent to the processing of his or her
personal data for one or more specific purposes; ” individuals do not
have a way to manage their consents across data processors
* http://ec.europa.eu/newsroom/document.cfm?doc_id=44099https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2016.119.01.0001.01.ENG

12. GDPR 2.0
Logical conclusion
A H I S T O R I C C H A N G E

13. IHAN®?

14. IHAN®
Our project aims to create an international
protocol that gives people control over how and
what their data is being used for.
Think of it as a kind of IBAN (International
Bank Account Number) for personal data.
I N T E R N A T I O N A L
H U M A N S ’ A C C O U N T
N E T W O R K

15. Establish key principles, rules & guidelines for human-driven
Data exchange Platform. Build awareness and engage people
across Europe
Test, develop and scale Platform to multiple industries and EU
countries. Ensure interoperability through technology Proof-
of-Concepts [ I H A N ® A P P R O V E D ]
Branding. Develop common Roadmap for fair Data exchange
Method. Build Common Governance Model [ I H A N ® A P P R O V E D ]
Our project in nutshell

16. What does IHAN® change?
what is the current situation and our target goal?
Antti Larsio (15min)

17. Data collectors
Current situation
Data about me is somewhere out there
I have to manage a lot of different accounts
I have to manually copy my data between service providers
Data about
me
Data collectors
Data collectors

18. Data collectors
Current situation - trend
Data companies have the data about people
I have to buy data from data companies – or die
Data companies will control service industries and me
Data about
me
Data collectors
Data collectors
How to get data for my services?
€ / £ / $
€ / £ / $

19. Data collectorsRisk
Data companies will control the whole service industry
There is an unfair cost to get data
Monopoly will decrease innovation
Extra cost for me and control of innovations
Data about
me
Data collectors
Data collectors
€
€
€
€
€

20. Data collectors
IHAN® future
Data about me is somewhere out there - but I do know where and what
It needs my authorization to use my data – I’m empowered
My data can be gathered for my service on fair and reasonable terms
Services will focus on value, quality and need – data is available by my consent
Data about
me
Data collectors
Data
collectors
LOG
Authorization
Service discovery
Identifier wallet
APIs
Metadata exhange
Data transfer
Protocol for data requests

21. IHAN® in a nutshell
Service Data
Authorization
to use
my data
Service provider
Requests for data
Data providers

22. What are IHAN® technical specifications?
How does IHAN® architecture and technology principles look like?
Jyrki Suokas (15min)

23. Identity
Data
Consent
Services
Log
End User Services and IHAN® services
End user-
Service
Data
Service provider Data providerEnd user
ServicesIHAN
Service provider Data providerEnd user

24. IHAN® Services components
End User Service Provider Data Provider
Identity
Data
Consent
Services
Log
Wallet of identifiers
Master Service Directory
End User Service Directory Service Provider Service Directory
End User Data Directory Data Provider Data DirectoryService Provider Data Directory
Service Order Data OrderConsent Directory
End User Logs Data Provider LogsService Provider Logs

25. IHAN® Technical Specification –
Document about WHAT, not HOW
- Contains documentation of all functional and non-
functional requirements for IHAN® service layer
- Architectural diagrams of components and data
flows for reference architecture
- Technical specification of IHAN® service messages
on field level
- IHAN® service documentation and how actual
services will use IHAN® services
- Governance
– Initially created by Sitra project team
– Maintained centrally by Sitra project team
– Updated through learnings from IHAN® pilots
- Initial version available 31.8.2018

26. IHAN® and industry pilot approach
What kind of support can service pilots expect
Jyrki Suokas ( 5 min)

27. Networks, industry expertise and business
development
- Sitra team can support Service projects with
industry expertise and networking cross-
pollination though our advisors
- ”IHAN® project starter kit” with easy to use tools
and templates to document and validate the new
service
Risto Tornivaara
Former CEO of
Danske Bank Finland
Hannu Hämäläinen
Former Ministerial adviser
at Finnish Ministry of
Social Affairs and Health
Antti Larsio
Former National Technology
Officer Microsoft / HUS CIO /
Telia IT Corporate Director

28. How is IHAN® project proceeded?
What kind of working methodology, tools and process will be used?
Juhani Luoma-Kyyny ( 20 min)

29. End User Services and IHAN® services
End user-
Service
Data
Service provider Data providerEnd user
ServicesIHAN
Service provider Data providerEnd user
Identity
Data
Consent
Services
Log

30. IHAN® technical component documentation
End User Service Provider Data Provider
Identity
Data
Consent
Services
Log
Wallet of identifiers
Master Service Directory
End User Service Directory Service Provider Service Directory
End User Data Directory Data Provider Data DirectoryService Provider Data Directory
Service Order Data OrderConsent Directory
End User Logs Data Provider LogsService Provider Logs

31. Pilot Project 1 creates initial components and
services
End User Service Provider Data Provider
Identity
Data
Consent
Services
Log
Wallet of identifiers
Master Service Directory
End User Service Directory Service Provider Service Directory
End User Data Directory Data Provider Data DirectoryService Provider Data Directory
Service Order Data OrderConsent Directory
End User Logs Data Provider LogsService Provider Logs

32. Pilot Project 2 adds new and creates alternative
components. More IHAN® services added
End User Service Provider Data Provider
Identity
Data
Consent
Services
Log
Wallet of identifiers
Master Service Directory
End User Service Directory Service Provider Service Directory
End User Data Directory Data Provider Data DirectoryService Provider Data Directory
Service Order Data OrderConsent Directory
End User Logs Data Provider LogsService Provider Logs
Wallet of identifiers
End User Logs

33. Pilot Project 3 adds yet new components. More
services to IHAN® layer
End User Service Provider Data Provider
Identity
Data
Consent
Services
Log
Wallet of identifiers
Master Service Directory
End User Service Directory Service Provider Service Directory
End User Data Directory Data Provider Data DirectoryService Provider Data Directory
Service Order Data OrderConsent Directory
End User Logs Data Provider LogsService Provider Logs
Wallet of identifiers
End User Logs

34. Pilot Project n adds new and creates alternative
components. IHAN® Service layer complete
End User Service Provider Data Provider
Identity
Data
Consent
Services
Log
Wallet of identifiers
Master Service Directory
End User Service Directory Service Provider Service Directory
End User Data Directory Data Provider Data DirectoryService Provider Data Directory
Service Order Data OrderConsent Directory
End User Logs Data Provider LogsService Provider Logs
Wallet of identifiers
End User Logs
Data Provider Data DirectoryService Provider Data Directory

35. IHAN® architecture implementations
Collection of IHAN
reference
architectures

36. FOR IHAN® PILOT PROJECTS WE
ARE SEEKING EITHER ALREADY
ONGOING PROJECTS OR
PROJECTS THAT ARE
READY FOR A QUICK LAUNCH.

37. Pilot project criteria
1. Applicants: we are particularly seeking the kind of
applicants operating in co-operation networks that
involve various actors.
2. Implementation phase of the project: we are
looking for applicants belonging to already existing
ecosystems, with whom we can advance quickly.
3. User-oriented approach: the clear aim of the pilot
project is to improve people’s everyday lives and
opportunities for the management of their own
information.
4. Technical solution: the pilot project needs to solve
technical software component issues related to
IHAN® principles, specified more closely in the
application form.
5. Effectiveness: the pilot project aims to replace the
current operating model, where an individual’s
information is dispersed in the depths of various data
storages owned by different systems and companies,
with a human-oriented and fair exchange of data.
6. Visionary approach: the pilot project is aimed at
the future and has a “novelty value”.
7. Feasibility: the applicant must have sufficient
competence and, if necessary, a functioning
subcontractor network for the development, launch
and establishment of a feasible and economically
sound solution.
8. Repeatability: the lessons learned from the pilot
project and feasible solutions should also be able to be
used in other sectors and scaled up.
9. Continuity: the application demonstrates the
applicant’s strong commitment, resources and plans
for the continuation of the operations after the project
is over.
10. Transfer of intellectual property rights: the
applicant is prepared to transfer intellectual property
rights to the extent required by the pilot project, for
example, in connection with the EU-wide workshops.
11. Other criteria: in addition to the criteria listed
above, the pilot project meets the technical and other
similar criteria to be specified in the application form.

38. The stages of the call for funding applications
The applicant fills in the application form and submits the application from to Sitra
at the email address ihan@sitra.fi.
Meeting with Sitra and the applicant selected to continue the process for further
discussions (goals, schedule, resources) about the potential funding
Sitra will evaluate which projects it will fund based on the application form and the
common discussion.
Those selected to continue the process will prepare a specified project plan serve as
a basis for the funding agreements between Sitra and the applicants
5
.
2
3
1
4

39. MORE INFO:
WWW.SITRA.FI/IHAN

40. IHAN® Standardisation
What does (Cen-Cenelec) process mean? What will we standardise?
Markus Kalliola (10min)
®

41. Regulation vs. standardisation
- GDPR gives citizens new rights
– To have a copy of their data in an electronic format
– To transfer data from one service provider to another
– To have right to be forgotten
- GPDR doesn’t say how these new rights need to be implemented
- Standarisation is a process of developing compatible technologies and processes
- Multiple standards can exists to implement similar job
– Picture standards JPG, GIF, PNG etc.
– IHAN technical standard will be one standard among others to implement GDPR rights and other
necessary processes to make human driven data economy possible

42. CEN-CENELEC standardisation processes
- CEN-CENELEC
– European Standards (EN), European level, weighted vote
– Example: EN 14484:2003 Health informatics - International transfer of personal health data covered by the EU
data protection directive
– Harmonization Document (HD), three languages, replaces national standards
– Technical Specification (TS), National level, replaces national standards
– Amendment to EN/HD
– Technical Report (TR), done by a official Technical body, vote by simple majority
– Guide, made by CEN member, vote by simple majority
– Workshop Agreement (CWA)
- ISO
– Vienna agreement (1991) between ISO and CEN-CENELEC

43. IHAN® workshop
– Why CEN-CENELEC workshop?
– International co-operation
– Open process
– Credibility in EU
– Kick off meeting October
– A year long process
– Work Items
– Work Item 0: Coordination
– Work Item 1: Principles, architecture and requirements
– Work Item 2: Identity and Data identifiers
– Work Item 3: Orders and messages
– Work Item 4: Distributed Log system
– Work Item 5: Smart contract structure

44. Next steps
Jyrki Suokas ( 5 min)

45. Making
people’s life
easier, smarter
and happier!

46. Appendix

47. Main building blocks
Trust domains Trust domains
1 2
3
4
5
6
7
7
7
9
8
1
0
1
0

48. Wallet of identifiers
Authentication
- Collaboration with existing
authentication solutions and
development work
- Strong authentication
- Two factor authentication
- Dezentralized authentication
- OAuth, OpenID, OpenID Connect
- Distributed Ledger Technology
- FIDO, UAF, U2F
Uniform Resource Indentifier, Uniform
Resource Locator
- IHAN number
- Data
- Credentials
Wallet
- Various authentication mechanism
- Various URI/URL of data
- Credentials
- Combination of an individual and URI of
data = IHAN number?
- Cryptography
- Interfaces, protocols, APIs
1

49. Identifiers
Data object (a person)
Legitime data possessor
Legitime service provider
Individual / physical entity
Organization
Identity verified by a trusted 3rd party
Application
Web address
Identity known by a mutual agreement,
but not verified by 3rd party
Identity unknown to external parties,
known only by me
Data about data object
Device
privateID
agreedID
verifiedID
organizationID
applicationID
urlID
deviceID
dataID

50. IHAN number
(( privateID agreedID verifiedID) dataID ))
f
Generates asymmetric key-pair: Master key and Private key
Master key known to both parties
Private key known only by a person (data object)
Data object can prove the relationship to the data by using IHAN number
URI = scheme:[//authority]path[?query][#fragment]
authority = [userinfo@]host[:port]

51. Wallet of identifiers
(( privateID agreedID verifiedID) dataID ))
f
Secure collection of IHAN numbers
organizationID
applicationID
urlID
deviceID
Each connected to relevant dataID URI = scheme:[//authority]path[?query][#fragment]
primary access mechanism network location

52. Wallet of identifiers
MyWallet key
- Biometric
- Hardware
- Secured seed
- IHAN foundation secured blockchain secured hash
- Deterministic wallet
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
One ”card” per data possessor
or service provider
MyID may be verified, agreed or privateIHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
IHAN number (MyID and dataID)
Master key
Private key (encrypted by MyWallet key)
Service description
Data description
Service provider
Data provider
Metadata
Other

53. Authorization
- Content
- Metadata structure and process
- Encryption
- PKI
- IKE (Internet Key Exchange)
- Chained authorization
- Protocols
- APIs
- Log messages
2

54. Authorization
Data object (a person)
Legitime data possessor Auhorization to use data
(IHANAuth)
Legitime data possessor
New legitime data possessorLegitime service provider
New legitime service provider
If they have rights to give
an authorization
Data transfer

55. Metadata
Data about data
Wallet of
identifiers
Metadata: link
Data possessor
Used standard
XML - desciption

56. Metadata - interoperability
Data about data
Data possessor
A
Used standard
XML - desciption
Data possessor
B
Used standard
XML - desciption
Service provider
Based on metadata desciptions from both data
possessor solving the interoperability and usage
of data in order to provide services

57. Service Directory
- Personal Service Directory
– Contains list of service user currently is using or has used before
– If user opt-in/ shows intrest for new services (limited set) this allows service providers to propose new services in user’s Personal
Service Directory. Only services that are possible are shown - Service discovery by user based on his/her current metadata of user
data and what data of the user is accessible.
- Master Service Directory
– Service providers publish their services and describe what data of the user and what data from data sources is needed for the service
to be created
– Service discovery by user based on availability of users’ current metadata and data needed by services.
- Service Provider Directory
– Contains list of services users currently are using or have used before. Consent information and access mechanism to Data sources
- iOS, Windows, Android
- IE, Chrome, Mozilla, …
- APIs
- UI
- Use cases
- Similarity w X-Road
3

58. Registration
- Registration for service
– When user gives order for service provider to connect to one or more data sources the service provider
sends the consent related GDPR messages to data sources on behalf of the user
– Order can be time limited
– When user orders a service this triggers creation of
– Identifiers
– Service directory entry into Personal Service Directory and Service Provider Directory
– Basic authorization
– Terms of usage
- Content
- GDPR message
- API
4

59. Routing
- Focus on Internet messages and data transportation
- Authorization
- Data
- Blockchain
8

60. Routing (to be defined)
HTTPS
TLS
Log messages
Wallet of identifiers - seed
Permissioned blockchain – seed
Permissioned blockchain – MyLog hash
Provate blockchain - Mylog

61. Data management Console
- Functionality
- UI
- Security
- Use cases
- APIs
9

62. Data Management Console
Wallet of identifiers
UI forWallet of
identifiers
UI forWallet of
Logs
UI for
Authorization
messages
MyLog

63. Web communication
architecture, Interfaces, APIs
- Registration
- Authorization
- Data requests
- Data send, receive, (REST…)
- Service directory
- Trust domains
- Data management console
- Log
- Data transportation
- Wallet of identifiers
10

64. sitra.fi | seuraavaerä.fi
@sitrafund