1 Issues Degree to which standardisation is needed for IMS services, like for example video conferencing? Same service across different terminals Terminal capabilities (UE capabilities) Content adaptation to fit terminal capabilities, service type and user preferences MMS not the same as 3GPP MMS Protection of Copyright content for legal or privacy reasons, e.g. with streaming - for certain content, the stream should not be copyable - needs to be ciphered Need terminal architecture which supports digital rights management How to prevent damage by harmful content - do we need more than MExE?

2 Issues (2) Personalisation - personal data common to many services Push services - what do we want and how is it pushed to the terminal? Easy handling at terminal key? Mailbox handling - how to control download or other handling of messages stored in the network (e.g. storage time control by sender or recipient) Notification - how external events are notified to the terminal Instant Messaging (excl. presence) Presence, including attach/detach issues, availability to game invitation etc. Uplink streaming (e.g. from a camera on the terminal to a server)

3 Issues (3) Location and direction (direction in which the handset is pointing) Downloading objects (e.g. ring tones, graphics) Point to multipoint or broadcasting of multimedia Terminal requirements for m-commerce? Multiple subscriptions on one UICC? Synchronisation of data across users’ multiple devices and network elements One stop login Advising the network how the user is authenticated to the terminal (plus additional authentication mechanisms) Control of storage time by recipient/sender Handling service data (eg. Messages) across multiple subscriptions Standardised codec for voice activation

4 Conclusions (1) Input needed from UMTS Forum work into S1 (next meeting May 7), explaining service concepts listed in “service matrix.doc” Matrix/O20 –Degree to which standardisation is required for IMS services like for example video conferencing? Status in 3GPP seems like this is being reviewed, perhaps no need for further action right now. –Service analysis work in 3GPP should cover delivery of services across different terminal types and the provision of information about the UE capabilities, service type and user preferences, e.g. for presentation of content. New Work Item for SA3 (2nd resp. SA4, T2)? –To cover protection of content for copyright or privacy reasons, should first be analysed by SA1 for requirements

5 Conclusions (2) Noted that “MMS” column in UMTS forum report is not the same as 3GPP MMS as specified in and SA1, SA2, SA3?, SA4?, T2? - need to look at requirements and an appropriate secure architecture for Digital Rights Management - also need to liaise and align with other bodies like SDMI Need for protection against harmful code (e.g. viruses) being downloaded into the terminal. This impacts not only MExE but also MMS and potentially other features. SA1 could consider this. Need for the ability for users and operators to go to a single place to personalise/customise all features. Facilities from outside world already existing need to be considered. SA1 could look into this.

6 Conclusions (3) SA1 should be invited to look at advising the network how the user is authenticated to the terminal (plus is there a need for additional authentication mechanisms?) SA1 should be invited to think about “one stop login” and requirements in this area SA1 should be invited to discuss Notification - how external events are notified to the terminal SA1 should be invited to discuss Instant Messaging (excluding presence) SA1 should be invited to consider whether stage 1 text is required for Uplink streaming (e.g. from a camera on the terminal to a server). SA1 should be invited to consider requirements for orientation (direction in which the handset is pointing) as part of the LCS work if it is not already covered.

7 Conclusions (4) SA1 to be invited to consider requirements for minimum formats for ringtones, graphics etc. to allow these and other objects to be exchanged between devices from different manufacturers. SA1 to be invited to consider requirements for multiple active subscriptions, for example multiple active USIMs, multiple IMSI etc. Also consider receipt of calls/messages etc. destined for inactive subscriptions when another subscription used by the same user is active. SA1 to be invited to consider requirements for synchronisation of data across users’ multiple devices and network elements SA1 to be invited to consider Mailbox handling - how to control download or other handling of messages stored in the network (e.g. storage time control by sender or recipient)