1 / 26

The Problem of User Identification

The Problem of User Identification. Mike Pluke Castle Consulting Ltd. ETSI Specialist Task Force STF 157 Leader. When?. Started work 10 th January 2000 ETSI Guide to HF by end of July 2000 HF approval (?) September 2000. Who?. Mike Pluke, Castle Consulting Ltd. – STF Leader

hanzila
Download Presentation

The Problem of User Identification

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Problem of User Identification Mike PlukeCastle Consulting Ltd. ETSI Specialist Task Force STF 157 Leader

  2. When? Started work 10th January 2000 ETSI Guide to HF by end of July 2000 HF approval (?) September 2000 Who? Mike Pluke, Castle Consulting Ltd. – STF Leader Pedro Concejero, Telefónica I+D Derek Pollard, Parity Resources Ltd. STF157

  3. Today’s Complexities Which of these is Mike Miles?

  4. What’s Wrong? • If all you know is an email address you can’t phone someone • If their phone number has changed you’ve lost contact • If you can’t get in contact now it’s too late • No number/old number/no answer = a lost call • Lost calls=lost revenue and customer dissatisfaction

  5. People Not Terminals “People are outsiders in the current communications revolution. Computer hosts, pager terminals and telephones are addressable entities throughout the Internet and telephony systems.” Extract from “The Mobile People Architecture” from Stanford University

  6. Current Ways to Manage IDs When making a communication • New contacts  Directories: telephone directories, directory services, PeopleSearch, AnyWho, … • Existing contacts  Address Books: GSM Phone, MS Outlook,… Managing incoming communications Usage strategies: diversion, selective call barring, … UPT – mapping number to terminals, …

  7. High-level User Requirements • Resolving conflicting requirements of sender and receiver • Maintaining backward compatibility • Providing privacy • Trust – ensuring the sender and receiver are who they say they are

  8. Key User Requirements • One Identifier per individual or role - a Universal Communications Identifier (UCI) • An integrated UCI search mechanism • Automatic capture of UCIs • Intelligent agents to manage complexity for the calling and called parties • Stability of the UCI – over time and over technologies

  9. Surprise User Requirements Anonymity:An anonymous UCI can be created by anyone holding an authorised UCI Aliases:One or more alias UCIs can be created by anyone holding an authorised UCI People (or systems) receiving communications will be able to recognize that the UCI is anonymous or an alias

  10. Personal Identifier Proposal The proposed UCI has two primary parts: A label: that gives the most user friendly description of the person/role A unique numeric string: that gives uniqueness, the ability to input it from the most basic terminal and compatibility with the most basic network

  11. Personal Identifier Proposal An element is also being defined to enable anonymous and alias status to be transmitted

  12. A Possible Realisation

  13. A Possible Realisation

  14. A Possible Realisation

  15. A Possible Realisation

  16. The Personal Identifier In Use • The formatting shown is not a proposal

  17. How It Might Work?

  18. Delivering Stability Currently:Each new service/terminal may mean a changed or additional number S = ServiceT=Terminal N=Number/Name Change ISP and get N5 N4 Etc. Etc. N5 Etc. Etc. N5 S2/T5 (Prepay GSM) N6 Buy prepay GSM and get N6

  19. Delivering Stability

  20. Delivering Stability

  21. Delivering Stability

  22. Delivering Stability

  23. Delivering Stability

  24. Delivering Stability

  25. What next? • ETSI STF 157 will update and refine their user requirements • Civil Liberties and security issues will be further investigated – in conjunction with ETSI TC SEC • At the same time the potential solution(s) will be cross-checked against the requirements and against technologies

  26. Finally • ETSI STF 157 is very keen to liaise with all groups with an interest in this area • We are also very happy to receive ideas from individuals within these groups:My email is:Mike.Pluke@castle-consult.com • Standards/industry groups need to be aware of the proposals- and then develop standards to enable implementation of a solution

More Related