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

													Page 1/3

Source:	T2

To:	N1

Title:	LS on terminal capabilities

___________________________________________________________________________

T2 SWG6 appreciated responding LS N1-99591 regarding to our LS of the terminal capabilities TSGT2-2(99)282 and T2-(99)446.

We must apologise about previous our request that was not clear enough to N1 explaining our intention. 

The purpose of this LS is to ask N1 to study and find a minimum set of terminal baseline capability that defined as following Definitions.

And according to the additional Outline Condition stated below, please refer it and give us a minimum set of protocol that existing between Core-Network and Terminal handled by N1 work.
Outline Condition for Study 
1 Limit the process of terminal activities from Power-On to Registration. The said registration is only Power-On registration.
2 Exclude connection (and connectionless) process between Core-Network and Terminal that provide the user to access concrete service being defined by SA groups, such as speech, SMS, supplementary, data bearer services.
We think it may have a way to list necessary procedure (minimum set) names that is separated to Circuit-SW and Packet-SW.
Furthermore, If terminal is required to inform ability for some service implementation before and in registration process, please note it to us.
Definitions
For the purposes of the LS, the following terms and definitions apply.
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, synchronise 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.

													Page 2/3
Baseline Definition
The requirements for the baseline implementation capabilities can be defined by the functions required of a terminal to power on and attempt registration with a network. Note that successful completion of the registration procedure depends on the subscription and service capabilities of the terminal and user and is therefore outside the scope of the baseline requirements. The basic mandatory MS requirements are further explained in section 15 of 22.101 Service Principles [3]. The corresponding baseline implementation capabilities are referenced in Annex A. The registration attempt and maintenance is illustrated  in the state diagram of figure 1.

Perform Location Registration

No Network Found

Await Network Response

Ready for service

Ready to Transmit

Network Selected

Radio Access Mode Selected

Status OK to Register

Switched off

power on status check

select radio access mode

access node selection

Perform de-registration

perform registration

Registration Failed

search for networks

contact network

                                                  
Figure 1 - states required for baseline capability
The actions and states given in figure 1are defined below.
1 Switched off
The state “switched off” describes the terminal when no 3GPP system functions are operational.
2 Power-on status check
The action “power-on status check” describes starting the 3GPP functions within the terminal and checking that the terminal meets the 3GPP system requirements needed to start the registration procedure (e.g. an appropriate subscription). If no subscription is available, the terminal may still select an access node and enter an limited service state in which only emergency calls can be attempted.
[Editor’s note: any requirements here for response to power on stimulus?] 
3 Status OK to register
The state “status OK to register” describes the terminal when all checks have been performed and the terminal is ready to start 3GPP reception.
4 Select radio access mode
The action “select radio access mode” describes the terminal’s selection of an available radio access mode e.g. UTRA FDD/TDD mode or GSM/GPRS. The decision may be made manually or automatically.

5 Radio access mode selected
The state “radio access mode” describes the terminal when it has selected a radio access mode to use it its search for networks.
Page 3/3
6 Search for networks
The action “search for networks” describes the terminal’s attempt to detect and decode the information for all 3GPP networks in its immediate environment. The result of this attempt shall produce a list of available networks from which one can be selected on which to attempt registration. If no suitable networks can be found, the terminal can revert to its “OK to register” state and select another radio access mode if it has one available.
7 Network selected
The state “network selected” describes the terminal when a 3GPP network has been selected for a registration attempt. The particular network to be selected may be chosen either manually or automatically.
8 Access node selection
The action “access node selection” describes the terminal’s selection of one cell in which to attempt registration. This is described in 25.304 [1] as “camping on a cell” and enables the terminal to receive system information. More detailed descriptions of the procedures for selecting PLMN (including radio access mode selection), and cell selection/re-selection, are given in 25.304[1].

9 Ready to Transmit
The state “ready to transmit” describes the condition in which the terminal has regulatory permission to start transmitting at the 3GPP frequencies.
[Editor’s note: is this true for all regulatory regimes?]
10 Contact network
The action “contact network” describes the terminal’s act of transmitting a first signal to the network to indicate its desire to register. 
[Editor’s note: is this all this signal does?]
11 Await network response
The state “await network response” describes the condition in which the terminal is waiting for the network to respond to its first contact signal.
12 Perform registration
The action “perform registration” describes the procedures for authentication, capability negotiation and location registration. Note that in order to “perform registration” the terminal briefly enters a connected state as defined in [2].
[Editor’s note: are all the correct procedures listed here or alternatively should the requirements be stated in a non-procedural way?]
13 Ready for service
The state “Ready for service” describes the condition in which the terminal has successfully completed the registration procedures. If registration is unsuccessful the mobile can revert to the “radio access mode selected” state and try searching for another available network. At this point the terminal is ready to initiate or receive data for a specific service. Note that in order to maintain the “ready for service” state, the terminal will have to perform location registration regularly and when entering a new registration area.
14 Perform De-registration
The action “perform de-registration” describes the procedures for de-registering the terminal prior to power-off. After de-registration the terminal returns to the power-off state.