7.1 Basic Generic Procedures
34.1083GPPCommon test environments for User Equipment (UE)Conformance testingRelease 15TS
7.1.1 UE Test States for Basic Generic Procedures
This clause describes a set of procedures for use by test cases in 3GPP TS 34.123-1 [1]. Describing these procedures in a generic manner allows their use in many test cases. By using these procedures, test case descriptions need not detail signalling that is not relevant to its purpose or understanding.
The procedures are based upon default values that are adapted to the most common usage. Test cases that require values different from the default will, when specifying the Basic Generic Procedure, also specify those parameters that are modified.
Figure 7.1.1: UE Test States for Basic Generic Procedures
In order that the UE can set up a call in UTRAN, there are a number of procedures to be undertaken in a hierachical sequence to move between known states. The sequences are shown in figure 7.1.1 and the status of the relevant protocols in the UE in the different states are given in table 7.1.1.
Table 7.1.1: The UE states
|
RRC |
CC |
MM |
SM |
GMM |
||
|
State 1 |
Power OFF |
—– |
null |
null |
pdp-inactive |
GMM-null |
|
State 2 |
CS Registered Idle Mode |
idle |
null |
idle |
pdp-inactive |
GMM-deregistered |
|
State 3 |
PS Registered Idle Mode |
idle |
null |
null |
pdp-inactive |
GMM-registered |
|
State BGP4 |
RRC Connection |
connected |
null |
as previous |
pdp-inactive |
as previous |
|
State BGP5 |
Generic RB Establishment |
connected |
null |
as previous |
pdp-inactive |
as previous |
7.1.2 Mobile terminated establishment of Radio Resource Connection
7.1.2.1 Initial conditions
System Simulator:
The system simulator will start from the default idle state. Parameters will the default parameters for a single cell, unless otherwise specified in the test case.
User Equipment:
Unless otherwise specified in the test case, the UE will be in the following state:
– Default test operating conditions.
– The UE shall have followed the generic registration procedure for CS or PS operations, and will be in Idle Mode, Camped-on (State 2 or State 3).
7.1.2.2 Definition of system information messages
The default system information messages are used.
7.1.2.3 Procedure
– The SS sends a PAGING TYPE 1 message to the UE on the appropriate paging block, and with the IE "Paging record" containing the TMSI or P-TMSI of the UUT.
– The SS receives an RRC CONNECTION REQUEST message from the UE.
– On receipt of the RRC CONNECTION REQUEST the SS shall transmit a RRC CONNECTION SETUP message to the UE. The SS shall wait for the receipt of an RRC CONNECTION SETUP COMPLETE message from the UE.
– On receipt of an RRC CONNECTION SETUP COMPLETE message, the procedure is complete.
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
¬ |
SYSTEM INFORMATION (BCCH) |
Default SI messages |
|
|
2 |
¬ |
PAGING TYPE 1 (PCCH) |
Sent on appropriate cycle |
|
|
3 |
® |
RRC CONNECTION REQUEST (CCCH) |
RRC |
|
|
4 |
¬ |
RRC CONNECTION SETUP (CCCH) |
RRC |
|
|
5 |
® |
RRC CONNECTION SETUP COMPLETE (DCCH) |
RRC |
|
7.1.2.4 Specific message contents
7.1.2.4.1 PAGING TYPE 1
This message is sent from the SS to the UE, using the TM RLC SAP, on the PCCH logical channel.
|
Information Element |
Value/Remark |
|||
|
Message Type |
PAGING TYPE 1 |
|||
|
UE Information elements |
||||
|
Paging record list |
Paging record |
CN originator |
Paging cause |
Terminating Speech Call (note) |
|
CN domain identity |
CS domain (note) |
|||
|
UE Identity |
TMSI (GSM-MAP) As specified during Registration procedure |
|||
|
Other information elements |
||||
|
BCCH modification info |
omit |
|||
|
NOTE: These defaults are applied if no subsequent procedure is to be run. Otherwise, the Paging cause, CN domain identity and UE Identity are selected in accordance with the requirements of the following procedure. |
||||
7.1.2.4.2 RRC CONNECTION REQUEST
This message is sent by the UE to the SS using the TM-RLC SAP. It is sent on the CCCH Logical channel.
|
Information Element |
Value/Remark |
||
|---|---|---|---|
|
Message Type |
RRC CONNECTION REQUEST |
||
|
UE information elements |
|||
|
Initial UE identity |
TMSI and LAI |
TMSI (GSM-MAP) |
As specified during Registration procedure |
|
LAI (GSM-MAP) |
As specified by default 1 cell environment |
||
|
Initial UE capability |
Maximum number of AM entities |
As declared in UE ICS |
|
|
Establishment cause |
As appropriate |
||
|
Protocol error indicator |
FALSE |
||
|
>UE Specific Behaviour Information 1 idle |
This IE will not be checked by default behaviour, but in specific test case. |
||
|
Measurement information elements |
|||
|
Measured results on RACH |
Not checked |
||
|
NOTE: These defaults are applied if no subsequent procedure is to be run. Otherwise, the UE Identity is selected in accordance with the requirements of the following procedure. |
|||
7.1.2.4.3 RRC CONNECTION SETUP
This message is sent from the SS to the UE using the UM-RLC SAP. The message is sent on the CCCH Logical channel.
The default RRC CONNECTION SETUP message for the transition to connected mode CELL_DCH is used except for the IE fields specified below.
|
Information Element |
Value/Remark |
|||
|
Message Type |
RRC CONNECTION SETUP |
|||
|
UE Information Elements |
||||
|
Initial UE identity |
TMSI and LAI |
TMSI (GSM-MAP) |
As specified during Registration procedure |
|
|
LAI (GSM-MAP) |
As specified by default 1 cell environment |
|||
|
RB Information Elements |
||||
|
Use default |
||||
|
TrCH Information Elements |
||||
|
Use default |
||||
|
PhyCH Information Elements |
||||
|
Frequency info |
As specified by default 1 cell environment |
|||
|
Uplink radio resources |
||||
|
Use default |
||||
|
Downlink radio resources |
||||
|
Use default |
||||
|
NOTE: These defaults are applied if no subsequent procedure is to be run. Otherwise, the UE Identity is selected in accordance with the requirements of the following procedure. |
||||
7.1.2.4.4 RRC CONNECTION SETUP COMPLETE
This message is sent by the UE to the SS using AM-RLC SAP. The message is sent on the DCCH Logical channel.
|
Information Element |
Value/Remark |
||
|---|---|---|---|
|
Message Type |
RRC CONNECTION SETUP COMPLETE |
||
|
UE Information Elements |
|||
|
Hyper frame number |
Not checked |
||
|
UE radio access capability |
Conformance test compliance |
R99 |
|
|
PDCP capability |
Support for lossless SRNS relocation |
Not checked |
|
|
Supported algorithm types |
Not checked |
||
|
RLC capability |
Total RLC AM buffer size |
Not checked |
|
|
Maximum number of AM entities |
Not checked |
||
|
Transport channel capability |
Downlink |
||
|
Max no of bits received |
Not checked |
||
|
Max convolutionally coded bits received |
Not checked |
||
|
Max turbo coded bits received |
Not checked |
||
|
Maximum number of simultaneous transport channels |
Not checked |
||
|
Max no of received transport blocks |
Not checked |
||
|
Maximum number of TFC in the TFCS |
Not checked |
||
|
Maximum number of TF |
Not checked |
||
|
Support for turbo decoding |
Not checked |
||
|
Uplink |
|||
|
Max no of bits transmitted |
Not checked |
||
|
Max convolutionally coded bits received |
Not checked |
||
|
Max turbo coded bits received |
Not checked |
||
|
Maximum number of simultaneous transport channels |
Not checked |
||
|
Max no of transmitted transport blocks |
Not checked |
||
|
Maximum number of TFC in the TFCS |
Not checked |
||
|
Maximum number of TF |
Not checked |
||
|
Support for turbo encoding |
Not checked |
||
|
RF capability |
UE power class |
As declared for UE |
|
|
Tx/Rx frequency separation |
Not checked |
||
|
Physical channel capability |
Downlink |
||
|
Maximum number of simultaneous CCTrCH |
Not checked |
||
|
Max no DPCH/PDSCH codes |
Not checked (PDSCH: R99 and Rel-4 only) |
||
|
Max no physical channel bits received |
Not checked |
||
|
Support for SF 512 |
Not checked |
||
|
Support of PDSCH |
Not checked (R99 and Rel-4 only) |
||
|
Simultaneous reception of SCCPCH and DPCH |
Not checked |
||
|
Max no of S-CCPCH RL |
Not checked |
||
|
Uplink |
|||
|
Maximum number of DPDCH bits transmitted per 10 ms |
Not checked |
||
|
Support of PCPCH (R99 and Rel-4 only) |
Not checked |
||
|
UE multi-mode/multi-RAT capability |
Multi-RAT capability |
||
|
Multi-mode capability |
FDD or FDD/TDD |
||
|
Security capability |
Ciphering algorithm capability |
Not checked |
|
|
Integrity protection algorithm capability |
Not checked |
||
|
LCS capability |
Standalone location method(s) supported |
Not checked |
|
|
UE based OTDOA supported |
Not checked |
||
|
Network Assisted GPS support |
Not checked |
||
|
GPS reference time capable |
Not checked |
||
|
Support for IPDL |
Not checked |
||
|
Measurement capability |
Need for downlink compressed mode |
Not checked |
|
|
FDD measurements DL |
Not checked |
||
|
TDD measurements DL |
Not checke |
||
|
GSM 900 DL |
Not checked |
||
|
DCS 1800 DL |
Not checked |
||
|
GSM 1900 DL |
Not checked |
||
|
Multi-carrier measurement DL |
Not checked |
||
|
Need for uplink compressed mode |
Not checked |
||
|
FDD measurements UL |
Not checked |
||
|
TDD measurements UL |
Not checked |
||
|
GSM 900 UL |
Not checked |
||
|
DCS 1800 UL |
Not checked |
||
|
GSM 1900 UL |
Not checked |
||
|
Multi-carrier measurement UL |
Not checked |
||
|
UE system specific capability |
Not checked |
||
7.1.3 Radio Bearer Setup Procedure
7.1.3.1 Initial conditions
The procedure specified in clause 7.1.2 will be run. This procedure starts from the successful completion of clause 7.1.2.
7.1.3.2 Definition of system information messages
The default system information messages are used.
7.1.3.3 Procedure
– The SS sends a RADIO BEARER SETUP message to the UE on the DCCH established by the RRC Connection Establishment procedure.
– The SS receives a RADIO BEARER SETUP COMPLETE message from the UE in RLC Acknowledged mode on the DCCH.
On receiption of the RADIO BEARER SETUP COMPLETE the procedure is complete.
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
¬ |
RADIO BEARER SETUP (DCCH) |
RRC |
|
|
2 |
® |
RADIO BEARER SETUP COMPLETE (DCCH) |
RRC |
|
7.1.3.4 Specific message contents
7.1.3.4.1 RADIO BEARER SETUP
The RADIO BEARER SETUP message is sent from the System Simulator to the UE, using AM-RLC on the DCCH logical channel.
The default RRC CONNECTION SETUP message for the setup of a speech radio access bearer is used except for the IE fields specified below.
|
Information Element |
Value/Remark |
|
|
Message Type |
RADIO BEARER SETUP |
|
|
UE Information Elements |
||
|
CN Information Elements |
||
|
RB Information Elements |
||
|
RAB information for setup |
Default parameters for 12.2 kbps speech RAB + 3.4 kbps signalling radio bearer according to clause 6.10.2.4.1.4 for FDD, clause 6.10.3.4.1.4 for 3.84 Mcps TDD and 6.11.5.4.1.4 for 1.28 Mcps TDD |
|
7.1.3.4.2 RADIO BEARER SETUP COMPLETE
The RADIO BEARER SETUP COMPLETE message is sent from the UE to the System Simulator, using AM-RLC on the DCCH logical channel.
The default RADIO BEARER SETUP COMPLETE message is used.
|
Information Element |
Value/Remark |
|
Message Type |
RADIO BEARER SETUP COMPLETE |
|
Use default |
|