1 / 26

User Identification Solutions in Converging Networks

Mike Pluke ETSI STF 157 - “User Identification in Converging Networks”. User Identification Solutions in Converging Networks. Today’s Complexities. Which of these is Mike Miles?. Communicating Today. Communicating Today. Communicating Today. Communicating Today. What’s Wrong?.

larue
Télécharger la présentation

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. Mike Pluke ETSI STF 157 - “User Identification in Converging Networks” User Identification Solutions in Converging Networks

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

  3. Communicating Today

  4. Communicating Today

  5. Communicating Today

  6. Communicating Today

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

  8. Current Partial Solutions • UPT • Personal Numbering schemes • Fax via email • Email via phone • Etc.

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

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

  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. What’s Needed? • One user identifier per individual or role • An integrated user identifier search mechanism • Automatic capture of user identifiers • Intelligent agents to manage complexity for the calling and called parties

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

  17. How It Might Be?

  18. How It Might Be?

  19. How It Might Be?

  20. How It Might Be?

  21. How It Might Be?

  22. How It Might Be?

  23. How It Might Be?

  24. Why IP could help? • Integrated search mechanisms will not work effectively if a connection must be established to do each search • Search results will define the destination uri • Communication can start immediately the search results/uri is returned

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

  26. 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 is: Mike.Pluke@castle-consult.com

More Related