1. CEN/ISSS Workshop eURI
- l’eURI est arrivé
Peter Tomlinson
Member of eURI Project team
January 2004

2. eURI What is it? Why was it done? What does it do? How is it done?
What is needed to support it?
Future Developments
Recommendations

3. eURI - What is it?
An electronic aide mémoire and hand to do the typing
User (Card Holder) data held in a smart card
A data access specification and a suggestion for how to send the information around a network
Compliant with ISO/IEC 7816 parts 4 & 6 (and with new part 4)

4. Overall data structure

5. To encourage sharing of information belonging to the user!
Why is it being done?
To encourage sharing of information belonging to the user!

6. What does it do?

7. How is it organised?

8. How is it organised?

9. Object Identifiers

10. eURI - What is needed to support it?
Today eURI has to be implemented at the application level in the card, selected using an ISO AID
ISO/IEC 7816 application
applet (optionally with separate data objects)
ITSO ‘private application’ is coming
Software is required in the terminal
browser plugin or similar

11. Data structure in more detail
Tag = 65
Intended to be used to automatically configure terminals (e.g. for DDA compliance). Uses EN 1332 parameters.
UCI-only eURI application can be issued and used anonymously.
Added in late 2003 was an optional UCI extension to allow more data to be stored.
UCI
Special Needs Code
Physical Access Code
Language Preferences
Minimum URI Implementation:
Mandatory UCI Component

12. Data structure in more detail
Tag = 65
The management information is needed if the information is to be backed up by the application issuer.
UCI
Special Needs Code
Physical Access Code
Language Preferences
Tag = EB
UCI
Management
Information
Pointer to:
Management Information
UCI with Management Component

13. Data structure in more detail
Tag = 65
UCI
Special Needs Code
Physical Access Code
Language Preferences
Important!
Some details were changed in late See published CWA 13987:2003
Tag = E1
Pointer to: Directory #1
Directory #1
Parent = null
Child = null
Tag = E4
Pointer to: Personal Profile
Personal Profile
Pointer to: URL
For use by terminal
Pointer to: AID
Tag = EC
Pointer to Management
Information
Management Information
URI with Personal Profile and Management Components

14. Data structure in more detail
Tag = 65
Tag = E1
Important!
Some details were changed in late See published CWA 13987:2003
UCI
Special Needs Code
Physical Access Code
Language Preferences
Directory #1
Parent = null
Tag = EE
Child = Directory #2
UCI 2000
Pointer to: UCI 2000
Pointer to: Directory #1
Pointer to: DISTINCT ID
Tag = EF
DISTINCT ID
Pointer to: UCI Management
Information
Directory #2
Tag = EB
Parent = Directory #1
UCI Management
Information
Child = Directory #2
Tag = E4
Pointer to: Personal Profile
Personal
Profile
Extended URI
Pointer to: URL
To/From CC
Directory Tag = E3
For use by terminal
Pointer to: AID
Tag = EC
Pointer to Management
Information
URI Management
Information

15. eURI Future Developments
To ISO/IEC 7816 add data objects at card platform level
Define a universal method for identifying card platforms
Ensure that other CEN specifications are harmonised

16. Recommendations for Harmonisation
ISO/IEC JTC1 SC17 WG4
ISO/IEC 7816 & card platform recognition
Reconciliation with the EMV specification
CEN/TC224 WG11
EN 1545 (surface transport data elements)
IOPTA (transport ticketing)

17. CEN/ISSS Workshop eURI
To download eURI CWA 13987:2003
Go to
Click on ‘Published CWAs’ in the menu
Click on ‘CWAs download area’ in the text
Look for CWA and download all 3 parts
To see the eURI Workshop papers
eURI information web site
Peter Tomlinson
and