1 / 17

STF228 : User interoperability criteria

STF228 : User interoperability criteria. P-Y Hébert Afutt User Group Plenary - June 2003. Report framework. Summary of interoperability user requirements Generic recommendations Specific recommendations for interoperability improvement.

ali-griffith
Download Presentation

STF228 : User interoperability criteria

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. STF228 : User interoperability criteria P-Y HébertAfuttUser Group Plenary - June 2003

  2. Report framework • Summary of interoperability user requirements • Generic recommendations • Specific recommendations for interoperability improvement

  3. Survey of the user requirements on interoperability • Users from Belgium, France, Italy, India, UK, • 19 face to face interviews and 3 email inquiries • Market area • Administration 2 • Bank 2 • Insurance 1 • University 2 • Utility (Railways, Power) 5 • Service provider 3 • Consumer organisation 1 • Telecomm Business User organisation 2 • Telecomm User organisation 2

  4. Report framework • Summary of interoperability user requirements • Generic recommendations

  5. Principles for an interoperable communication environment (1) • Addressing the terminal: Checking network independent terminal addressing • Addressing the user: • Unified Communication Identifier development • Login: Unified login procedure implementation • Authentication harmonization: • a user configurable login and password • other more sophisticated means on the user choice • Directories: Common directory data modelling with appropriate protocol to ease the information exchanges

  6. Principles for an interoperable communication environment (2) • Management: • An effective and unified management of heterogeneous networks • Users' profile management interoperability • Billing management interoperability • Common QoS data modelling • Security: Checking security infrastructures interoperability • Interoperability check: an automated procedure for Interoperability failures identification

  7. Principles for service interoperability • Identification of terminal capabilities suited to access a service • Principles for choosing the terminal suited to access a service • Table 1: Terminal capabilities • Table 2: Minimal terminal capabilities suited to access a service • Definition of a list of services candidate to a committed interoperability(Table 3) • Principles for application interoperability: Agreements on common data modelling

  8. Table 1: Terminal capabilities

  9. Table 2: Minimal terminal capabilities suited to access a service

  10. Report framework • Summary of interoperability user requirements • Generic recommendations • Specific recommendations for interoperability improvement

  11. Terminals • Keyboard layout • Backward interoperability • A single communication handling

  12. Access • VoIP over every network • LAN, GPRS, xDSL Interoperability • Roaming • Interoperability of voice communications over Wi-Fi • Data transmission across fixed/mobile networks • Signalling across fixed/mobile networks

  13. Service • Interoperability of the supplementary services • A SMS/email acknowledgement • Interoperability of prepay services • A standard video format for mobile phones

  14. B2B/B2C • CTI/CRM Interoperability • LAN/WAN/Cellular Interoperability (on Board R-LAN, GPRS and WiFi)

  15. Teleconference • Unique H.323/SIP profile/interpretation • Minimum bandwidth availability

  16. Emergency call location • Emergency call location should be based on terminal location and not on user address

  17. THANKS FOR YOUR ATTENTION Comments are welcomed

More Related