TSG-T2
Yokohama, JP, 19-21 April 1999	TSGT2#3(99)338

Agenda Item:	SWG6 (General Features)

Source:	NTT DoCoMo

Title:	Proposed LSs on terminal capabilities

Document for:	Discussion / Decision

Proposed Liaison Statement to TSG-SA and TSG-S1

Source:	TSG-T2 (Services & Capabilities)

Liaison To:	TSG-SA, TSG-S1

CC:	other relevant WGs

Title:	Classification of services on terminal capabilities

1.	 Introduction

TSG-T2 requested all WGs to identify the terminal capabilities and has received the following LS answers. 

STC_DOC	Subject	Source	
T2-99332	LS to TSG-T on Terminal Capabilities	TSG-S4	
T2-99360	LS from TSG RAN WG1 on UE physical layer capabilities	TSG RAN WG1	
T2-99361	LS from TSG RAN WG4 on Baseline Terminal Capabilities	TSG RAN WG4	
T2-99363	LS from TSG RAN WG3 on Terminal Capabilities	TSG RAN WG3	
T2-99388	Reply from TSG-N2 on terminal capabilities	TSG-N2 chairman	
T2-99389	TSG-S4 Multimedia Discussions Summary	TSG-S4 Chairman	
T2-99397	LS from RAN2 on  Baseline Implementation Capabilities	RAN2	
T2-99398	Answer from S1 chairman on Terminal Capabilities	S1 chairman	
T2-99399	LS from CN3 on Terminal Capabilities	CN3	

But the need for common understanding of the approach to its completion has been found because more detailed identifications in accordance with the classification of services are required.

2.	Classification of services for the investigation of terminal capabilities

The classification of services from the terminal perspective to identify terminal capabilities is proposed in the y-axis of Annex B. According to the classification of services, service implementation capabilities for each technical domain should be considered.

The primary intention of this classification for services is to clarify the services related with the service implementation capabilities that have an impact on the completion of specifications and the test conformances, and the implementation of terminals. As a result, these categorisations are more dependent on or closer to the radio interfaces such as the type of bearers and its speed which affect on especially hardware implementation. In other words, categorised services from the application like higher layers than IP are out of its scope. If we would consider application layers over IP, there would be too many possibilities to be listed up and investigated within 3GPP.

There are differences of viewpoints for services between TSG-SA and TSG-T2. TSG-SA has considered and investigated services from the application perspective if anything. On the other hand, it is required that services should be overviewed from the layers close to radio which has an impact on the implementation, especially hardware of terminals, for the identification of terminal capabilities. But there is no contradiction in these two approaches, so it has no effect on the outputs delivered from TSG-SA.

TSG-SA and TSG-S1 are asked to review of this classification of services on terminal capabilities during each next meeting and send back LS answers to TSG-T2 as soon as possible. After being agreed or modified by TSG-SA and TSG-S1, Annex B will be attached to Annex A and forwarded to other relevant WGs by TSG-T2. Even If some modifications of Annex B would be required, the speed of data should be specified in LS answers as it has an impact on RF parameters in particular.

3.	The required actions by all WGs following the agreed service classification

Annex B is also a proposed table for the correspondence of capabilities to each technical domain; i.e. RF parameters, channels, radio layer 1~3 and codec. Service-less and service capabilities to identify baseline implementation capabilities and service implementation capabilities of each service respectively are listed in the y-axis. It is required that the all relevant WGs should identify a minimum set of implementation capabilities as mandatory ones and the other possible implementation capabilities as options according to each cells in this table.

4.	The required consideration on service capabilities

TSG-SA and TSG-S1 are required to consider the service requirements that should permit the free combination of service capabilities for terminal implementation. The primary principle of UMTS is to deliver a wide variety of services and a wide range of terminals. From the terminal perspective, all services should be optional at least for terminals. TSG-T2 has recognised that some service capabilities might be mandatory for network in order to realise the interoperability. But it is required that certain service capability or combinations of them should be implemented on terminals without any restriction by their selection of manufactures, operators and requests from users.

Annex A. Proposed Liaison Statement to all WGs

Source:	TSG-T2 (Services & Capabilities)

Liaison To:	all WGs

CC:	TSG-SA, TSG-S1

Title:	Identification of terminal capabilities

1.	 Introduction

TSG-T2 requested all WGs to identify the terminal capabilities and has received some LS answers. 
But the need for common understanding of the approach to its completion has been found because more detailed identifications in accordance with the classifications of services agreed by TSG-SA and TSG-S1 are required.

2.	 The required actions by all WGs following the decided service classification

Annex B is a table for the correspondence of capabilities to each technical domain; i.e. RF parameters, channels, radio layer 1~3 and codec. Service-less and service capabilities to identify baseline implementation capabilities and service implementation capabilities of each service respectively are listed in the y-axis. It is required that the all relevant WGs would identify a minimum set of implementation capabilities as mandatory ones and the other possible implementation capabilities as options according to each cells in this table.

On the other hand, basically there are 4 terminal types based on radio transmission and reception; i.e. single-mode FDD, single-mode TDD, dual-mode FDD/TDD and dual-mode FDD/2G. One of the terminal types is applied to each terminal. If there are differences in the required implementation capabilities among the terminal-modes, it is required that they should be clarified by checking appropriate terminal types in the first line of Annex B.

Also it is necessary to study the combinations of capabilities and UD 384K (64K*6). These could be considered for the realisation of Multi-call.

Tdoc T2#3(99)332, Tdoc T2#3(99)361, Tdoc T2#3(99)397 and Tdoc T2#3(99)399 and can be applied to the appropriate cells. But all WGs are asked to reconsider terminal capabilities in accordance with both the classification of services and terminal types.
Annex B.  Correspondence of capabilities to each technical domain according to the classification of services

•	Terminal type : FDD TDD FDD/TDD   FDD/2G

Layer
Capability	RF parameter	Radio Layer 1 	Channels	Radio Layer 2	Radio Layer 3	Codec	
	Mandate	Option	Mandate	Option	Mandate	Option	Mandate	Option	Mandate	Option	Mandate	Option	
Service-less	Baseline implementation capabilities	
	Tdoc T2#3(99)361			Tdoc T2#3(99)397	Tdoc T2#3(99)397	Tdoc T2#3(99)397			
Services	Service implementation capabilities	
Circuit switched data	Speech											Tdoc T2#3(99)332	
	Audio Video											Tdoc T2#3(99)332	
	Non-transparent 	14.4K FAX											Tdoc T2#3(99)399	
		14.4K Modem													
		28.8K Modem													
		33.6K Modem													
		64K													
	UD 64K													
Packet switched data	Point-to-point 
Uplink	64K													
		128K													
		384K													
	Point-to-point Downlink	64K													
		128K													
		384K													
SMS	Point-to-point													
	Cell broadcast													
Supplementary services														

•	Procedure
-	The appropriate terminal type(s) should be selected in the first line. 
-	All implementation capabilities should be identified as mandatory or option.
-	All cells should be reconsidered by relevant WGs.

•	Policy
-	Mandated implementation capabilities should be minimised.
-	Implementation capabilities still under discussion should be regarded as option because our time limit.

•	Note
-	It is required that the implementation capabilities of Radio Layer 3 for interworking with PSTN and ISDN should be considered.
-	For non-transparent circuit switched data, “modem” means data communication interworked with PSTN, and 64.4k is needed to interwork with ISDN.
-	The above-mentioned speed of data is correspondent to general capabilities of PSTN and ISDN.