ETSI STC SMG2 Handover ad-Hoc	Document	Tdoc 36/00
Revised Tdoc RPA000021	
Copenhagen, Denmark
6 – 8 March, 2000		e.g. for 3GPP use the format  TP-99xxx 
or for SMG, use the format  P-99-xxx	

CHANGE REQUEST	Please see embedded help file at the bottom of this
page for instructions on how to fill in this form correctly.	
	
	04.18	CR	A059r2	Current Version:	8.2.0		
					
GSM (AA.BB) or 3G (AA.BBB) specification number 		 CR number as allocated by MCC support team	
	
For submission to: 	SMG#31	for approval	X		strategic		(for SMG	
list expected approval meeting # here 	for information			non-strategic		use only)	
			
Form: CR cover sheet, version 2 for 3GPP and SMG        The latest version of this form is available from: ftp://ftp.3gpp.org/Information/CR-Form-v2.doc	
	
Proposed change affects:	(U)SIM		ME	x	UTRAN / Radio	x	Core Network		
(at least one should be marked with an X)	
	
Source:	Ericsson,Siemens	Date: 	000304	
	
Subject:	Measurement Command – Connected Mode	
	
Work item:	Handover GSM UMTS	
	
Category: 	F	Correction		Release: 	Phase 2		
	A	Corresponds to a correction in an earlier release			Release 96		
(only one category 	B	Addition of feature	X		Release 97		
shall be marked	C	Functional modification of feature	 		Release 98		
with an X)	D	Editorial modification			Release 99	X	
				Release 00		
	
Reason for 
change:
	In order to provide GSM network with UMTS measurements a new measurement order is introduced in connected mode. This new measurement order is sent on SACCH from the network to a UMTS capable multiband mobile to provide the mobile with information on neighbouring cells to be monitored and reported on within the cell. A new System Information message type 5gamma containing pointers to UMTS Scrambling Code and UMTS Radio Frequency combinations. A field to indicate the UMTS reporting mode (e.g. RSSI or Ec/Io shall be reported for UMTS measurements) is coded in the message. A threshold Qsearch  (defining when to start UMTS measurements) and offset  Moffset (to be used in comparing UMTS and GSM measurements) are sent to the mobile. In case RSSI (mapped Ec/Io ) values shall be reported for UMTS neighbouring cell measurements the downloaded offset shall be used.	
	
Clauses affected:	New chapters 9.1.53 and 10.5.2.22b, chapter 10.4	
	
Other specs	Other 3G core specifications		  List of CRs:		
affected:	Other GSM core specifications	X	  List of CRs:	05.08	
	MS test specifications		  List of CRs:		
	BSS test specifications		  List of CRs:		
	O&M specifications		  List of CRs:		
	
Other 
comments:		

  <--------- double-click here for help and instructions on how to create a CR.

	9.1.53 System Information Type 5gamma
This message is sent on the SACCH by the network to the mobile within the cell giving information on the BCCH allocation and the UMTS scrambling code and frequency allocation of the neighbouring cells. See table 9.1.53.1/GSM 04.18 . . It shall be transferred using the short header format for SACCH messages sent in unacknowledged mode specified in TS 24.007
Any change in the neighbour cells description must overwrite this part of any old data held by the mobile station. The mobile station shall, with the exception stated above, analyse all correctly received system information type 5gamma messages. 
Message type:	SYSTEM INFORMATION TYPE 5gamma
Significance:		dual
Direction:			network to mobile station

<SYSTEM INFORMATION TYPE 5gamma > ::= 	
  
	<RR short PD  : bit(1)>			  -- See 3G TS 24.007
	<message type : bit(5)>				  -- See 10.4
	<short layer 2 header : bit(2)>		  -- See GSM 04.07
		<UMTS Neighbour Cell Description : octet(20)>;		
Table 9.1.53.1/GSM 04.18: SYSTEM INFORMATION TYPE 5gamma message content

Max 17 octets information into this part

IE container part

	

	
10.4	Message Type
The message type IE and its use are defined in TS 24.007 [20]. Tables 10.1/GSM 04.18 and 10.1a/GSM 04.18 define the value part of the message type IE used in the Radio Resource management protocol.
Table 10.1/GSM 04.18 (page 1 of 2): Message types for Radio Resource management
 8 7 6 5 4 3 2 1                                   
                                                   
 0 0 1 1 1 - - -  Channel establishment messages:  
           1 0 0  - RR INITIALISATION REQUEST      
           0 1 1  - ADDITIONAL ASSIGNMENT          
           1 1 1  - IMMEDIATE ASSIGNMENT           
           0 0 1  - IMMEDIATE ASSIGNMENT EXTENDED  
           0 1 0  - IMMEDIATE ASSIGNMENT REJECT    
                                                   
 0 0 1 1 0 - - -  Ciphering messages:              
           1 0 1  - CIPHERING MODE COMMAND         
           0 1 0  - CIPHERING MODE COMPLETE        
                                                   
 0 0 1 1 0 - - -  Configuration change messages:   
           0 0 0  - CONFIGURATION CHANGE COMMAND   
           0 0 1  - CONFIGURATION CHANGE ACK.      
           0 1 1  - CONFIGURATION CHANGE REJECT    
                                                   
 0 0 1 0 1 - - -  Handover messages:               
           1 1 0  - ASSIGNMENT COMMAND             
           0 0 1  - ASSIGNMENT COMPLETE            
           1 1 1  - ASSIGNMENT FAILURE             
           0 1 1  - HANDOVER COMMAND               
           1 0 0  - HANDOVER COMPLETE              
           0 0 0  - HANDOVER FAILURE               
           1 0 1  - PHYSICAL INFORMATION           
                                                   
 0 0 0 0 1 0 0 0  - RR-CELL CHANGE ORDER           
 0 0 1 0 0 0 1 1  - PDCH ASSIGNMENT COMMAND        
                                                   
 0 0 0 0 1 - - -  Channel release messages:        
           1 0 1  - CHANNEL RELEASE                
           0 1 0  - PARTIAL RELEASE                
           1 1 1  - PARTIAL RELEASE COMPLETE       
                                                   
 0 0 1 0 0 - - -  Paging and Notification messages:
           0 0 1  - PAGING REQUEST TYPE 1          
           0 1 0  - PAGING REQUEST TYPE 2          
           1 0 0  - PAGING REQUEST TYPE 3          
           1 1 1  - PAGING RESPONSE                
           0 0 0  - NOTIFICATION/NCH               
           1 0 1  - NOTIFICATION/FACCH             
           1 1 0  - Reserved (see NOTE)            
 0 0 0 0 1 0 1 1  - Reserved (see NOTE)            	
	
(continued)	

NOTE:	This value was allocated but never used in earlier phases of the protocol.

Table 10.1/GSM 04.18 (page 2 of 2): Message types for Radio Resource management
 8 7 6 5 4 3 2 1                                   
 0 0 0 1 1 - - -  System information messages:     
           0 0 0  - SYSTEM INFORMATION TYPE 8      
           0 0 1  - SYSTEM INFORMATION TYPE 1      
           0 1 0  - SYSTEM INFORMATION TYPE 2      
           0 1 1  - SYSTEM INFORMATION TYPE 3      
           1 0 0  - SYSTEM INFORMATION TYPE 4      
           1 0 1  - SYSTEM INFORMATION TYPE 5      
           1 1 0  - SYSTEM INFORMATION TYPE 6      
           1 1 1  - SYSTEM INFORMATION TYPE 7      
                                                   
 0 0 0 0 0 - - -  System information messages:     
           0 1 0  - SYSTEM INFORMATION TYPE 2bis   
           0 1 1  - SYSTEM INFORMATION TYPE 2ter   
           1 0 1  - SYSTEM INFORMATION TYPE 5bis   
           1 1 0  - SYSTEM INFORMATION TYPE 5ter   
           1 0 0  - SYSTEM INFORMATION TYPE 9      
           0 0 0  - SYSTEM INFORMATION TYPE 13         
                                                   
 0 0 1 1 1 - - -  System information messages:     
           1 0 1  - SYSTEM INFORMATION TYPE 16     
           1 1 0  - SYSTEM INFORMATION TYPE 17     

 0 1 0 0 0 - - -  System information messages:
           0 0 1  - SYSTEM INFORMATION TYPE 19
                                                   
 0 0 0 1 0 - - -  Miscellaneous messages:          
           0 0 0  - CHANNEL MODE MODIFY            
           0 1 0  - RR STATUS                      
           1 1 1  - CHANNEL MODE MODIFY ACKNOWLEDGE
           1 0 0  - FREQUENCY REDEFINITION         
           1 0 1  - MEASUREMENT REPORT             
           1 1 0  - CLASSMARK CHANGE               
           0 1 1  - CLASSMARK ENQUIRY              
 0 0 1 1 0 1 1 0  - EXTENDED MEASUREMENT REPORT    
 0 0 1 1 0 1 1 1  - EXTENDED MEASUREMENT ORDER     
 0 0 1 1 0 1 0 0  - GPRS SUSPENSION REQUEST        
                                                   
                  VGCS uplink control messages:    
                                                   
 0 0 0 0 1 0 0 1  - VGCS UPLINK GRANT              
 0 0 0 0 1 1 1 0  - UPLINK RELEASE                 
 0 0 0 0 1 1 0 0  - Reserved (see NOTE)                    
 0 0 1 0 1 0 1 0  - UPLINK BUSY                    
 0 0 0 1 0 0 0 1  - TALKER INDICATION              

Bit 8 is reserved for possible future use as an extension bit, see TS 24.007.
NOTE:	This value was allocated but never used in earlier phases of the protocol.

Table 10.1a/GSM 04.18: Message types for Radio Resource management messages using the RR short protocol discriminator
 5 4 3 2 1                                         
                                                   
 0 0 0 0 0           SYSTEM INFORMATION TYPE 10    
 0 0 0 0 1           NOTIFICATION/FACCH            
 0 0 0 1 0           UPLINK FREE   
 0 0 0 1 1           SYSTEM IMFORMATION TYPE 5gamma                

	10.5.2.22b	UMTS Neighbour Cells Description 
The purpose of the UMTS Neighbour Cells Description  information element is to provide the UMTS absolute scrambling code  radio frequency channel number of the UMTS carrier to be monitored by the mobile stations in the GSM cell.
The UMTS Neighbour Cells Description information element is a type 3 information element with 20 octets length
Figure 10.5.54/GSM 04.18 UMTS Neighbour Cells Description  information element
<UMTS Neighbour Cells Description value part>::=
       <Multiband reporting : bit(2)>
        <BA-IND bit (1)>
        <Qsearch bit (6)> <Moffset bit (6)> 
         <UMTS Reporting Quantity : bit(2)> 
          <SI5ter bit(1)>

        01<UMTS FDD Neighbour List >: { 1< UMTS Neighbour List struct>} **0
        <spare paddings>;
        < UMTS FDD Neighbour List structure>::=
             <UMTS frequency bit(10)>
             <UMTS FDD/TDD bit(1)>
            <Scrambling Code List >: { 1< Scrambling Code List Struct>} **0;
 < Scrambling Code List Structure>::= <Scrambling Code bit(9)>;

Figure 10.5.54/GSM 04.18 UMTS Neighbour Cells Description  information element
Qsearch a binary representation of a RSSI value representing a treshold when the mobile shall start to measure on UMTS neighbours.
Qsearch is a binary coded representation of a corresponding GSM signal strength on the serving cell.
0 0 0   Qsearch threshold 1, -102 dBm
0 0 1   Qsearch threshold 2, -  86 dBm
0 1 0   Qsearch threshold 3, -  80 dBm
0 1 1   Qsearch threshold 4, -  74 dBm
1 0 0   Qsearch threshold 5, -  68 dBm
1 0 1   Qsearch threshold 6, -  62 dBm
1 1 0   Qsearch threshold 7, -  56 dBm
1 1 1   Qsearch threshold 8, 

Moffset is used when calculating the quality of the  UTRAN cell according to the formula specified in TS 25.304 . Moffset is a dimensionless binary representation of a corresponding interference level.

UTRAN REPORTING ,  Binary encoding of  UMTS reporting capability as specified in 05.08(.Additional cell reporting requirements for multi RAT MS)

UMTS Reporting Quantity field, Binary encoding (2 bits) of the UMTS measurement quantity to report. . 
BA-IND UMTS BA-list indication.The UMTS BA-IND is needed to allow the network to discriminate measurements results related to different UMTS BA-lists sent to the mobile, i.e. when BA-lists are updated. 

UMTS frequency, a binary representation of  UTRAN frequency.

UMTS scrambling code, a binary representation of UTRAN scrambling code.