3GPP TSG-T2 #7 / ETSI SMG4
Ystad, SWEDEN, 22-26 November 1999	TSGT2#7(99)1030	

Liaison Statement

From: 3GPP TSG-T2/SWG1 (MExE)	

To: CN OSA ad hoc	

Cc: S1, S2, N2, T3, WAP UAProf

Subject: Response to liason statement on the interaction between MMS, SAT, MExE, non-MExE terminals and Camel/Open Service Architecture

___________________________________________________________________________

The T2/SWG1 (MExE) group thanks CN OSA ad hoc for their liaison statement on the interaction between MMS, SAT, MExE, non-MExE terminals and Camel/Open Service Architecture. 

Capability negotiation is an important part of the MExE specification. In capability negotiation the MExE group relies on the expertise of the WAP UAProf group. With the help of the UAProf group, the MExE group introduced two attributes to the UAProf specification: MexeSpec for indicating the MExE specification version and MexeClassmark for indicating the MExE classmark: 
•	Classmark1 includes WAP.
•	Classmark 2 includes java and support for WAP services
The MExE specification refers to the UAProf specification in capability negotiation and recommends MExE terminal to support a set of capability attributes defined in the UAProf specification. The MExE group therefore relies on the available mechanisms for capability negotiation and does not define such a mechanism by itself.

One of the future working items of the UAProf group is to define support for third-party requests to a gateway or proxy to retrieve, update, and manage profile information about a particular client or group of clients. However, there are confidentiality and security issues related to the possibility for terminal capabilities being publicly available e.g. for 3rd parties. Therefore also the security of capability information transmission, persistence and update is one of the future working areas indentified by the UAProf group. 

One possible approach to the problem for MExE terminals could also be the usage of an application, which is downloaded to the MExE terminal by the user, and which would, on the user permission, send the capability information to the parties needing that information. 

For non-MExE terminals this issue needs to be studied and initiated in SA2. Also a mechanism for indicating to the server that the terminal in question supports SAT should be studied in the T3 group.

As a summary, the MExE group encourages the usage of readily available capability indication mechanisms between terminals and servers offering services and encourages all interested parties to cooperate with the UAProf group. Further, the MExE group recommends the usage of one common method for capability indication and therefore minimizing standardization efforts.