1. HFT 2008 Workshop: Guidelines for Generic UI Elements for 3G Mobile Devices, Services and Applications Bruno von Niman, Matthias Schneider & David Williams ETSI STF322 Leader and Experts

2. The home of the GSM™ standards…
ETSI
The home of the GSM™ standards…
… and ISDN, DECT, DAB, DVB …

3. …and a founding Partner in
ETSI
…and a founding Partner in

4. We need standards to ensure:
Compatibility of equipment and services from different suppliers
Full interoperability
Transfer of learning
Accessibility to equipment and services
Better safety and security
Load sharing, cost saving, co-operation of competitors 2

5. ETSI STF 322 Co-funded by ETSI Members and EC/EFTA Experts:
Bruno von Niman (ITS (SE), vonniman consulting), leader
Pekka Ketola (Nokia)
David Williams (Asentio Design)
Matthias Schneider (Nokia Group)
Following up on EG (STF231),
focusing on the 3G-specific aspects
Time plan:
Work started in March 2007
Final draft deliverable ready (TB approval) in September 2008
ETSI publication foreseen in December 2008, after membership voting

6. Introduction and background (1/2)
The capabilities offered by mobile solutions evolve,
from only being able to make a call and use voic to
downloadable personalization achieved through
ring signals,
software programs such as games and
the introduction of multimedia information services
such as navigation, mapping and directions,
traffic information,
text messaging and access,
quasi-cordless functionality,
music, TV and video call services.

7. Introduction and background (2/2)
Connectivity and interoperability between
telephony networks,
personal computing,
the Internet, and
ever-smarter mobile terminals and services
Offer enormous potential for improving life.
Concern about whether next-generation products, services and their content will provide a good user experience and be fully accessible to all people, including:
generic users,
less literate users,
children,
aging and disabled users.
Ensuring access to mobile communication for all is a common goal
vendors, operators, service providers,
users associations,
Policy makers (e-inclusive information society).

8. The “Usability Gap” “Featurism” - product complexity increasing
Range of mobile technology users broadening – from children to elderly and disabled

9. Decreasing the “Usability Gap”
Possible ways to decrease complexity include:
understanding of user needs;
excellent user interfaces;
simplicity of configuration;
personalization capabilities and
ease of operation.
Also the “usability gap” can be helped by:
technological advances (e.g. better speech recognition);
a maturing ICT industry.

10. Generic UI elements!

11. Scope (1/2)
Simplify end-user access to ICT services for end users and consumers from mobile 3G/UMTS telecommunication terminals
without restricting the ability of market players to further improve and develop their terminals, services and applications.
Expand scope of EG , “Human Factors: Guidelines for Generic Mobile User Interface Elements for Mobile Terminals and Services” (August 2004)
to 3G specific issues
Address specific and important 3G key issues from the end user's perspective
providing guidance on proposed generic user interface elements for basic and advanced mobile terminals, services and applications, including their accessibility.

12. Scope (2/2)
Consider user requirements and integrate available results of standardisation work
providing implementation oriented guidance.
Do not restrict ability of market players
to further improve and develop their devices and services.
Do not limit options to trademark UI elements or profile the user experience
of brand‑specific user interface implementations as a competitive edge.
Provide guidance on simplifying end-user access to basic and selected advanced functions of mobile communication services from mobile communication devices.
Adopt a Design-for-All approach, wherever possible
taking special needs of children and elderly users with physical and sensory disabilities into account.

13. Rationale for generic UI elements
Manufacturers differentiate their products through industrial and screen design, feature sets and UIs
Generic UI elements are accepted
in safety-relevant products (e.g. cars),
for products to be used by many people (products in public or work environments), and
In UIs following de-facto standards (GUIs in PC software or musical instruments).

14. Rationale for generic UI elements
Generic UI elements result from
De-facto standards (e.g. GUIs), and from
official standardisation (e.g. keypad arrangement on public phones).
Generic UI elements potentially benefit all,
end users,
manufacturers, and
service providers.
Can facilitate the uptake of new and emerging technologies and user interfaces, e.g.:
ETSI ES Character repertoires, ordering rules and keypad assignment (under expansion)
ETSI ES Generic spoken command vocabulary (under expansion)

15. Rationale for generic UI elements
Basic considerations of what makes a UI area a candidate for generic UI elements:
No barrier to innovation
No obstacle to good product-specific user interfaces
Only the semantic of a generic user-interface element should be specified, not the actual design and implementation
End-user aspects, such as learnability, familiarity, trust, configuration and access
Commercial aspects (quicker uptake of new technologies, larger user base)
Legal requirements and possible regulation

16. EG 202 132: GSM and GPRS-specific Guidelines
Terminology, symbols, acoustic signals and user guides
Configuration for service access, interworking, portability and error handling
Terminal and network related generic UI elements
Service and application specific UI elements

17. Terminal and network related generic UI elements
9.1 International access code
9.2 Safety and security indicators
9.3 Text entry, retrieval and control
9.4 Accessibility and assistive terminal interfaces
9.5 Common keys
9.6 Language selection mechanisms
9.7 Voice and speech user interfaces
9.8 Users’ data privacy, security and access control
9.9 Telephone number format and handling
9.10 Universal addressing in converging networks
9.11 Synchronization and back-up

18. Service and application specific UI elements
10.1 Emergency call services
10.2 Voice call services
10.3 Video call services
10.4 Mobile browsing and Internet services
10.5 Positioning-related services
10.6 Service and content presence, availability and connectivity
10.7 Payments, cost of services and content
10.8 Messaging services
10.9 Instant mobile messaging services

19. 3G/UMTS specifics currently addressed by DEG 202 972 (1/2)
Introduction of the present draft
Scope, methodology, topics
Approach
Collaboration with industry
Work plan and time schedule
Requirement collection
Dissemination plan
Reference group
Consensus building process and workshops
Infrastructure and device-related guidelines
Access, connectivity and QoS
Internet connectivity, access and use
Always-on, always on-line
Dedicated, device-native UIs
Accessibility applications
Other areas (under investigation)

20. Review of 3G/UMTS specifics currently addressed by DEG 202 972 (2/2)
Guidelines for services, media and applications
Data-intensive services and applications;
Distributed, non-device-native (local and remote) UIs;
Customization and operator-bundled packages;
Services of public interest (societal services/ services to the public);
Business/enterprise use;
Mobile Internet guidelines.
Other non 3G-specific but related guidelines
Application installation;
Computer access, bandwidth and cost issues;
IMS guidelines;
Accessibility applications (enabled by 3G).

21. Thank you! Your comments and input welcome: bruno.vonniman@etsi.org
Post-workshop updated public draft available at: