3GPP TSG-T2 #6 / ETSI SMG4
Kyong-Ju Korea October 4nd-6th 1999	TSGT2#6(99)T2-99784	

Agenda Item:	Terminal Management 

Source:	Ericsson,Telia,Vodafone	

Title: 	Proposal for the definition of Terminal Management and a way forward	

Document for:	Discussion

___________________________________________________________________________

Introduction
Aspects on Terminal Management have recently been discussed in SA Plenary and SA5. This is not a new discussion, but has previously at great length been discussed in SMG Plenary, T3/SMG9 and T2/SMG4. As concluded in Tdoc TSGS5#4(99)106, it may be a concern of many groups. 

The purpose of this input is to help the understanding of the scope of Terminal Management and to propose a way forward. 

Definition 
Terminal Management (TM) is a secure mechanism that allows the network operator, with permission from the authenticated user, to remotely change settings within a terminal and obtain terminal diagnostic information.

Scope
TM allows
•	the network operator to assist the user 
•	terminal diagnostic information to be fed back to the network operator 
•	a population of unmanned terminals to be managed for a customer (user groups or machine-machine solutions)

Conclusions
•	The existing mechanisms SAT and MExE are suitable and sufficient for TM. 
•	We expect these mechanisms to evolve in their own right, as well as supporting changes in future TM functionality, such as new AT-commands.
•	Consequently, there is no need to invent new mechanisms to achieve TM functionality. 
•	Configuration of terminal software (by direct action of terminal manufacturers only) could be implemented by terminal manufacturers on a proprietary basis, or by using TM security mechanisms.
•	Remote software upgrades is too complex to be included in the TM scope.
•	Certain data for read-only purposes needs to be available without the user's consent. These are IMEI and an unformatted set of manufacturer specific data, that can include software revision/configuration, proprietary serial numbers etc. 
•	Security (user protection/privacy, network security) must be provided.

Proposed actions
•	TSG-T2 are asked to endorse the principles outlined in this paper. 
•	Current or planned TSG-T, SAT and MExE specifications shall adhere to the principles contained in this paper when appropriate.
•	We propose these principles to be included in the T2 Terminal Capabilities report 3G-TR 21.904, chapter 7.
•	The Terminal Management work shall be the responsibility of TSG-T.