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

Agenda Item:	SWG6 – 2.3 (Proposed changes to TR21.904)  

Source:	NEC

Title:	Terminology

Document for:	Discussion 

___________________________________________________________________________

Introduction

In TR21.904, terminology such as “mandatory”, “optional” and “conditional” are currently used to describe the level of requirement.  However none of them seems to be defined clearly in 3GPP document.   Also “mandatory” is used in various places in 3GPP documents in inconsistent manner.   It is noted that following discussion took place in the last T Plenary meeting in Korea (TP-99225).

“Following discussions in the TSG T plenary meeting, it was decided that there was a need for clarification of the use of the term “mandatory” in 3GPP documents. 
•	The term “mandatory” is associated with regulatory requirements, and should not be used in 3GPP specifications. It may however, be used in reports describing regulatory requirements. Given that, the term “mandatory” is in common use in 3GPP working groups, but that there is no common understanding of what is meant by the term, we propose that its use should be replaced by the term “Core Requirement” when describing functionality which is essential for the proper operation of the 3G system. 
•	Core Requirements in the terminal can be conditional on that terminal’s ability to support a specific function or service. Thus, there are certain Core Requirements of a terminal supporting only the baseline functionality (i.e. not supporting any service(s)). A terminal supporting a given service will have additional Core Requirements.”  

However the outcome of SA meeting which followed the T Plenary meeting was not clear.   Its draft minutes (T2-991015) states as follows.   

“TSG T suggest that the term "mandatory" in testing specifications should be replaced with the "core" specification. This caused some comments and questions from the TSG SA delegates. It was suggested  that these comments are made directly to TSG T, as they consider this to be the best solution. In general, TSG T believes the term "mandatory" should be avoided in test specifications and should only be used for regulatory mandates.”

Discussion

In order to avoid further confusion in our report TR21.904 as well as in other 3GPP specifications/reports, terminology to describe the level of requirements should be clearly defined and commonly used throughout all 3GPP documents.  

Following the decision by SA to produce and maintain sole and common vocabulary document (TR21.905) in 3GPP, following the request by Mr. Michele Zarri (T2-991019),  SWG6 should aim at including key terms and definitions in the common vocabulary document TR21.905.

Proposal

Following terms and conditions should be agreed in SWG6 and sent to T2 Plenary for endorsement with further expectation that T2 sends appropriate LS to S1 so that these terms and definitions will be included in TR21.905.

Mandatory UE Requirement ; Regulatory requirement which is applicable to 3G UEs.   It is determined by each country/region and beyond the scope of 3GPP specification.
e.g. Spurious emission in UK 

Essential UE Requirement (Unconditional); Requirement which has to be implemented in any 3G UE in order to exist in and communicate with 3G network.
e.g. Chiprate of 3.84Mcps

Essential UE Requirement (Conditional) ; Requirement which has to be implemented under certain Service conditions.  
e.g. AMR codec in UE which supports speech service

Optional UE Requirement ; Any other requirements than 3 requirements listed above.   It is totally up to individual manufacturer to decide whether it should be implemented or not. 
e.g.

Although it was suggested in the last T Plenary meeting to use “Core Requirement” instead of “Mandatory”, it may be confusing as similar term “Core Specification” has been used at least in T2 in completely different meaning.