3GPP TSG-T2#4 / ETSI SMG4
Miami, US, 14-16 June 1999	TSGT2#4(99)583	

Agenda Item:	

Source: 	TSG-T2-SWG6
	Co-ordinator – TSG-T2-SWG-6 to TSG-N1

Title: 	Liaison Statement to N1 on Baseline and Service Capabilities	
Request for Terminal Implementation Capabilities Information 
_______________________________________________________________________________________

Introduction

This Liaison Statement contains a Request for Terminal Implementation Capabilities Information from N1, requesting details of the Service Implementation Capabilities required for Release 99, to support Terminal Service Capabilities as agreed in S1. 

It also requests information on Terminal Implementation Capabilities Information for Terminal Baseline Capabilities, further to our prior LS’s T2(99)590, T2(99)282 and T2(99)446. 

This information is requested in time for T2 to consider it at Its 5th meeting In September 99.

Request for Terminal Implementation Capabilities

The Terminal Service Capabilities as shown in Annex B are among those agreed by S1 to be standardized as part of the 1999 Release of the UMTS standard. None of the capabilities identified below are mandatory in the terminal and unless otherwise stated, the support of one service in a terminal does not imply a requirement to support any other service. The requirements for the capabilities listed below, are elaborated in TS 22.100 which itself makes references to definitions of the capabilities in other 22.1xx specifications, as indicated.

The attached description shown in Annex C, Service Capabilities are on top of, Baseline Capabilities. 
Baseline Capabilities can considered as those required for a service-ready state In terminal (;not in service implementation state). Baseline Capabilities and Service Capabilities are provided via the associated Terminal Implementation Capabilities (i.e. Service Implementation Capabilities that is to say service achievement elements for service features and Baseline Implementation Capabilities that is to say baseline achievement elements for baseline features).

(1)	Request for Baseline Implementation Capabilities(same as the request of our prior LS’s)
T2 requests TSG N1 to identify the Implementation Capabilities as shown in the Annex A.1.2 for an example within its technical domain to support the Terminal Baseline Capabilities as defined in Annex C.

(2)	Request for Service Implementation Capabilities 
T2 requests TSG N1 to identify the Implementation capabilities as shown In Annex A.2.2 for an example within its technical domain to support the Terminal Service Capabilities listed in the Annex B. 

T2 request that these Implementation Capabilities be identified by (split into) each group of Baseline, and Service. Please see Annex B as reference.

TSG T WG2 looks forward to receiving details of the required Baseline and Service Implementation Capabilities by its 5th meeting (September 6-10, 1999).

 Annex A:   Example for Terminal Baseline Implementation Capabilities (BIC) and Terminal Service Implementation Capabilities (SIC) for Layer 3
A.1  Baseline
This information will hopefully assist you to achieve identifying the Terminal Baseline Implementation Capabilities in layer 3 domain for Example.

A.1.1	Baseline Capabilities

Table A.1.1: Baseline Capabilities (Reference)
Item	Baseline Capabilities	Ref. Doc	Section(s)	Terminal	Comments	
1	On / off switch	3GPP 21.904	4.1	O		
2	Power-on status check	3GPP 21.904	4.2	M		
3	Radio access mode selection	3GPP 21.904	4.4	M		
4	Network searching	3GPP 21.904	4.6	M		
5	Access node selection	3GPP 21.904	4.8	M		
6	Contact network	3GPP 21.904 	4.10	M		
7	Perform registration	3GPP 21.904 	4.12	M		
8	Perform de-registration 	3GPP 21.904 	4.14	M		

A.1.2	Layer 3 Baseline Implementation Capabilities (non-access stratum)

Table A.1.2: Baseline Implementation Capabilities (Example)
(From Mobile Management Procedure)
Baseline Implementation. Capabilities	Ref. Doc	Section(s)	Mandatory/ Optional for Terminal	Comments	
non-GPRS	MM common procedures	TMSI reallocation procedure	GSM04.08
(7.0.1)	4.3.1			
		Authentication procedure	ditto	4.3.2			
		Identification procedure	ditto	4.3.3			
		IMSI detach procedure	ditto	4.3.4			
		Abort procedure	ditto	4.3.5			
		MM information procedure	ditto	4.3.6			
	MM specific procedure	Location updating procedure	ditto	4.4.1			
		Periodic updating procedure	ditto	4.4.2			
		IMSI attach procedure	ditto	4.4.3			
		Generic Location 
Updating procedure	ditto	4.4.4			
GPRS	GMM common procedures	P-TMSI reallocation procedure	ditto	4.7.6			
		Authentication and ciphering procedure	ditto	4.7.7			
		Identification procedure	ditto	4.7.8			
		GMM Information procedure	ditto	4.7.12			
	GMM specific procedure	GPRS attach procedure	ditto	4.7.3			
		GPRS detach procedure	ditto	4.7.4			
		Routing area updating
Procedure	ditto	4.7.5			

A.2 Service 
As required to N1 for protocol standardization works according to service capabilities among agreed by S1 under 3GPP release ‘99 requirements. Please see Annex B for Service Capabilities for your reference listed by T2.If N1 find more services defined (or will be certainly defined) by S1, please add those also.
This information will hopefully assist you to achieve identifying the Terminal Service Implementation Capabilities in layer 3 domain for Example.

A.2.1	Service Capabilities (non-access stratum)

Table A.2.1: Service Capabilities (Example)
Item	Service Capabilities	Ref. Doc	Section(s)	Mandatory/ Optional for Terminal	Comments	
1		3GPP 22.xxx				
2						
3						
4						

A.2.2	Layer 3 Service Implementation Capabilities (non-access stratum)
A.2.2.1 Service Implementation Capabilities from Mobility Management (&GMM) procedures
Table A.2.2.1: SIC for MM and GMM (Example)
Service Implementation. Capabilities	Ref. Doc	Section(s)	Mandatory/ Optional for Terminal	Comments	
non-GPRS	MM procedures	Paging procedure	GSM04.08
(7.0.1)	4.7.9			
GPRS	GMM procedure	Paging procedure	Ditto	4.7.9			
		Receiving a GMM STATUS Message by a GMM entity	Ditto	4.7.10			
		GMM support for anonymous  Access	Ditto	4.7.11			
		GMM Information procedure	Ditto	4.7.12			

A.2.2.2 Service Implementation Capabilities from Call Control and Session Management procedures
Table A.2.2.2: SIC for CC and SM (Example)
Service Implementaion Capabilities	Ref. Doc	Section(s)	Mandatory/ Optional for Terminal	Commentst	
non-GPRS		Mobile originating call Establishment	GSM04.08
(7.0.1)	5.2.1			
		Mobile terminating call Establishment	Ditto	5.2.2			
		Call clearing	Ditto
	5.4.2			
				5.4.3			
				5.4.4			
		Miscellaneous Procedures	Ditto
	5.5.1			
				5.5.2			
				5.5.3			
				5.5.4			
				5.5.5			
				5.5.6			
				5.5.7			

GPRS		PDP context activation	Ditto	6.1.3.1			
		PDP context modification procedure	Ditto	6.1.3.2			
		PDP context deactivation procedure	Ditto	6.1.3.3			
		AA PDP context activation	Ditto	6.1.3.4			
		AA PDP context deactivation	Ditto	6.1.3.5			
		Receiving a SM STATUS message by a SM entity	Ditto	6.1.3.6			
		GMM support for anonymous 
Access	Ditto	4.7.11			
		GMM Information procedure	Ditto	4.7.12			

Annex B:   Details of standardised Service Capabilities to be evaluated by N1 (MM,CC,SM)

In 3G TS 22.105:

•	Speech (AMR)
•	Emergency Call (Note that support of Emergency call is mandatory for terminals supporting narrowband speech)
•	Short Message Service - Point to Point (SMS-PP) 
•	Short Message Service - Cell Broadcast (SMS-CB) 
•	Fax
•	Circuit Switched data with information transfer rate and quality attributes (e.g. Bit Error Ratio, Maximum transfer delay, Delay variation, etc.) as defined in 22.105 (Note, may be redefined according to new definitions in 23.907)
•	Packet Switched data with information transfer rate and quality attributes (e.g. Bit Error Ratio, Maximum transfer delay, Delay variation, etc.) as defined in 22.105 (Note, may be redefined according to new definitions in 23.907)
•	GSM system features
•	Network Identity and Time Zone (NITZ)
•	Support of Localized Service Area (SoLSA)
•	Unstructured Supplementary Service Data (USSD)

Supplementary services GSM R’99. Examples:
•	Call Forwarding (02.82)
•	Advice of Charge (02.86)
•	Explicit Call transfer (02.91)

In 3G TS 22.121:
•	Mobile station Execution Environment (MExE)
•	Location Services (LCS) 
•	SIM Application Toolkit (SAT) 

Priority Information;

T2 is proceeding along its defined work program. This is contained in T2-99(282) which states the following -
•	The prime work priority is to achieve stable specification for the baseline implementation capabilities.
•	Among the service capabilities, the specification work for the capabilities to support the speech service is of priority.

For the stated Services, TSG T WG2 asks N1 to deal with these as the ones with the greatest priority – 
Baseline capabilities; 
Speech; 
SMS (point to point); 
Circuit-switched data at 64 kb/s. 

Annex C:   Description of Terminal Baseline/Service capabilities and associated Implementation Capabilities 
Definitions for use in describing Terminal Capabilities

We hope this information will assist you in your goals to achieve stable specifications for the terminal capabilities.

T2 is proceeding along its defined work program. This is contained in T2-99(282) which states the following -
•	The prime work priority is to achieve stable specification for the baseline implementation capabilities.
•	Among the service capabilities, the specification work for the capabilities to support the default speech service is of priority.

The following is reproduced from TSGT2(99)446 and 282

Service capabilities: capabilities that can be used either singly or in combination to deliver services to the user. The characteristic of service capabilities is that their logical function can be defined in a way that is independent of the implementation of the UMTS system (although all service capabilities are of course constrained by the implementation of UMTS). Examples: a data bearer of 144 kbps; a high quality speech Teleservice; an IP Teleservice; a capability to forward a speech call.

Baseline capabilities: capabilities that are required for a service-less terminal to operate within a network. The baseline capabilities for a terminal include the capabilities to search for, synchronize with and register (with authentication) to a network. The negotiation of the terminal and the network capabilities, as well as the maintenance and termination of the registration are also part of the required baseline capabilities.  

Implementation capability: a capability that relates to a particular technical domain. Example (in the domain of the physical layer): a spreading factor of 128; Examples (in the domain of security): the A5 algorithm; a 64 bit key length; Example (in the domain of transmitter performance): a power output of 21 dBm; Example (in the domain of the Codec): support of AMR Codec; Example (in the domain of the USIM): support of CHV1;

Baseline implementation capabilities: set of Implementation capabilities, in each technical domain, required to enable a terminal to support the required Baseline capabilities.  

Service implementation capabilities: set of Implementation capabilities, in each technical domain, required to enable a terminal to support a set of Service capabilities.

Service-less terminal: a terminal that has only the Baseline capabilities.

For the purposes of testing, minimum tests should be based on a combination of the Baseline capabilities and the appropriate Service capabilities.

Baseline Implementation
Capabilities

Figure 1.  Baseline, Service and Implementation, Capabilities

2

3

4

5

n

1

Baseline 
Capabilities

Implementation
Capabilities:
•	L1
•	L2
•	L3
•	Security
•	Etc…

Service 
Capabilities

Service
Implementation
Capabilities