1 / 20

User Identification Solutions in Converging Networks

User Identification Solutions in Converging Networks. Mike Pluke Castle Consulting Ltd. Leader of :. ETSI Specialist Task Force STF 157. ETSI STF 157. The Human Factors group within the European Telecommunications Standards Institute (ETSI) is leading this work.

roanna-mclaughlin
Download Presentation

User Identification Solutions in Converging Networks

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. User Identification Solutions in Converging Networks Mike PlukeCastle Consulting Ltd. Leader of : ETSI Specialist Task Force STF 157 Document IPW-10

  2. ETSI STF 157 • The Human Factors group within the European Telecommunications Standards Institute (ETSI) is leading this work. • The Specialist Task Force comprises 3 people funded to study “User Identification Solutions in Converging Networks”and produce an “ETSI Guide” document on the topic.

  3. The Terms of Reference • Discover real user requirements for user identification • Develop an implementation-free expression of these requirements • Identify potential solution options • Create an implementation “Roadmap” for solutions • Solutions must work in a competitive environment

  4. So What Is The “User Identification” Issue • The number of communications systems is increasing • Each system has its own identification system • Telephone Numbers mean very little • Contacting people isn’t necessarily getting easier • Identification-system developments are uncoordinated

  5. A Typical Case A person can have: • A fixed telephone on their office desk • A mobile telephone • A fixed (shared) telephone at home • An email address used for work purposes • A personal email address used at home

  6. Which of these is Mike Miles?

  7. Communicating Today

  8. What’s Wrong? • The caller has to guess the most successful way to communicate • Most callers don’t know all the user identifiers • Terminals linked to communication type • User identifier schemes linked to communication type • Some user identifiers linked to terminals • Some user identifiers portable – telephony • Some user identifiers linked to provider – email • Terminals/user identifiers linked to users’ roles

  9. Solution Attempts • Supplementary services can match people to locationse.g. Call Diversion • Mobility solutions can map people to rolese.g. UPT solutions can locate the called party on one of a group of terminals • BUT frequently these systems give the wrong results

  10. Problems With Current Solutions • Many solutions lock users to 1 provider • Proprietary solutions are incompatible • Most solutions rely on fixes applied to legacy systems • Most solutions are unfriendly – to the caller and/or called party • There is probably no fully comprehensive global solution

  11. Human Communication Needs Modern communications systems can create new communication needs BUT Basic communication needs have changed very little since the dawn of man

  12. An Individual A Role A Place “Mary Jones” A local locksmith “23 Dearing Lane” Historic Communications Needs People have always needed to contact:

  13. Tomorrow People will still need to contact: Individuals, roles, groups and places

  14. 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

  15. High-level User Requirements • A unified way of setting up a communication • Reduce the complexity for the calling party • Make it easy for the called party to manage their communications • Give more options to the called and calling parties

  16. What’s Needed? • One user identifier per individual or role • An integrated user identifier search mechanism • Recognise that Martin Böcker = Martin Boecker • Protect privacy of personal data • Protect location privacy • Automatic capture of user identifiers • Intelligent agents to manage complexity for the calling and called parties • ……

  17. The User Identifier In Use • This format is not a proposal • The User Identifier must be unique • The format should be “user friendly”

  18. How It Might Be?

  19. What next? • ETSI STF 157 will continue to work on refining the user requirements for User Identification solutions • At the same time potential solutions will be investigated to validate the practicability of the requirements • A draft ETSI Guide will be available in August 2000 • Publication is likely in October 2000

  20. What next? • 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 (as STF Leader) is: Mike.Pluke@castle-consult.com • ETSI HF Chairman is Knut Nordby: knut.nordby@telenor.com

More Related