8 UICC/ME test interface
34.1093GPPRelease 17Special conformance testing functionsTerminal logical test interfaceTS
8.1 General description
A special interface is required in order to perform the tests of the UICC/ME interface.
8.2 Formal aspects
It shall be possible to connect the UICC/USIM simulator to the ME. If an adapter is to be used, the manufacturer of the ME shall provide it.
When using the UICC/USIM simulator, the ME does not necessarily conform to all RF requirements.
When the UICC/USIM simulator is connected the ME shall be able to correctly send and receive on a DTCH and associated channels under ideal radio conditions.
8.3 Hardware and logical aspects of the interface
The signals on this interface are specified in TS 31.101 [7].
8.4 Mechanical characteristics of the interface
The mechanical interface is specified in TS 31.101 [7].
Annex A (informative):
UE test loop use scenarios
A.1 Measurement of receiver characteristics (BER) using UE test loop mode 1 and RLC TM
SS can use the UE test loop mode 1 and RLC TM for measuring BER. For UE to be able to return all data it receives form SS it is required that the DL and UL transport block size are the same. It is also required that the UL RLC SDU size parameter of the CLOSE UE TEST LOOP message is set to the same value as the DL and UL transport block size.
A.1.1 Measurement of receiver characteristics (BER) – DL reference measurement channel (12.2 kbps)
In FDD mode, for measuring BER for the DL and UL reference measurement channel 12.2 kbps according to TS 34.121 [8], Annex C the configuration should be:
– DL and UL transport block size = 244 bits (RLC TM);
– UE test loop mode 1 parameter UL RLC SDU size = 244 bits.
In TDD mode, for measuring BER for the DL and UL reference measurement channel 12.2 kbps according to TS 34.122 [9], Annex C.
A.2 Measurement of receiver performance (BLER) using UE test loop mode 1 and RLC AM
To measure BLER UE test loop mode 1 can be used by having the DL RLC protocol operating in acknowledged mode (AM). The SS can calculate BLER from the ratio of number of UE retransmission requests and the total number of blocks sent by the SS.
In AM the UE indicates missing protocol units (=transport blocks) in the STATUS PDU message. There are different triggers for sending the STATUS PDU message. For the purpose of SS BLER measurement a timer based trigger such as receiver timer based STATUS PDU transfer can be used (see TS 25.322, subclause 9.7.2). The figure below illustrates the SS BLER measurement procedure. In the example in the figure block errors are detected by the UE of a total of N blocks. The BLER calculated by the SS is 4 / N.
Figure A.2.1: Measuring BLER using UE test loop mode 1 and DL RLC AM
A.2.1 Measurement of receiver performance (BLER) – DL reference measurement channel (64,144,384 kbps)
By having downlink transport block size set to size of user data part according to the 64, 144 or 384 kbps reference measurement channels and using RLC acknowledge mode the UE test loop mode 1 can be used to measure BLER.
A.3 Measurement of receiver performance (BLER) using UE test loop mode 2
In addition to the method described in A.2 UE test loop mode 2 can be used to measure BLER if the UL transport block size is bigger or equal to the sum of DL transport block size and number of DL CRC bits.
The SS can calculate BLER by checking returned data and CRC and count number of block errors and the total number of sent blocks.
A.3.1 Measurement of receiver performance (BLER) – DL reference measurement channel (12.2 kbps)
TS 34.121 [8], subclauses C.2.1 and C.3.1 defines the DL and UL reference measurement channel 12.2 kbps for FDD mode.
TS 34.122 [9], subclauses C.2.1 and C.3.1 defines the DL and UL reference measurement channel 12.2 kbps for TDD mode.
To be able to measure BLER using UE test loop mode 2 the SS needs to configure the uplink transport block size to 260 bits to fit downlink transport block size (244 bits) and downlink CRC bits (16 bits), see figure A.3.1.
Figure A.3.1: UE test loop mode 2 operation for the 12.2 kbps BLER measurement case
A.3.2 Measurement of receiver performance (BLER) – DL reference measurement channel (64,144 and 384 kbps)
TS 34.121 [8], subclause C.2 defines the DL and UL reference measurement channel for 64, 144 and 384 kbps for FDD mode.
TS 34.122 [9], subclause C.2 defines the DL reference measurement channel for 64, 144 and 384 kbps for TDD mode.
If a UE supports downlink reference measurement channels for 64,144 or 384 kbps and also the correspondent uplink reference measurement channel then it is possible to use UE test loop mode 2 for measuring BLER for these reference measurement channels.
A.4 Measurement of transmitter characteristics
The SS sets up the radio bearer for DL and UL reference measurement channels 12.2 kbps using the generic setup procedure.
See TS 34.108 [10], clause 7 for specification of the generic setup procedure.
See TS 34.121 [8], subclauses C.2.1 and C.3.1 for definition of the DL and UL reference measurement channel 12.2 kbps for FDD mode.
See TS 34.122 [9], subclauses C.2.1 and C.2.2 for definition of the DL and UL reference measurement channel 12.2 kbps for TDD mode.
The SS orders the UE to close its UE test loop by transmitting a CLOSE UE TEST LOOP CMD message.
When the SS receives the CLOSE UE TEST LOOP COMPLETE message from the UE the SS starts transmission of data to the UE.
Perform the transmitter test.
The SS sends the OPEN UE TEST LOOP message to the UE to open the UE test loop.
A.5 Measurement of transmitter DTX characteristics
The SS requests the UE to enable DTX and sets up the radio bearer for DL and UL reference measurement channels 12.2 kbps using the generic setup procedure.
See TS 34.108 [10], clause 7 for specification of the generic setup procedure.
See TS 34.121 [8], subclauses C.2.1 and C.3.1 for definition of the DL and UL reference measurement channel 12.2 kbps for FDD mode.
See TS 34.122 [9], subclauses C.2.1 and C.2.2 for definition of the DL and UL reference measurement channel 12.2 kbps for TDD mode.
The SS orders the UE to close its UE test loop using UE test mode 1 by transmitting a CLOSE UE TEST LOOP message.
The UE confirms that the UE test loop is closed by sending the CLOSE UE TEST LOOP COMPLETE message to the SS.
Perform the transmitter DTX testing.
The SS sends the OPEN UE TEST LOOP message to the UE to open the UE test loop.
A.6 Using UE test loop mode 2 for testing of UE Blind Transport Format Detection (FDD mode)
When a UE operates in UE test loop mode 2 then the received downlink transport block and the downlink CRC data bits shall be returned in the uplink transport block, see subclause 5.3.2.7. The UE shall select the uplink transport format with the smallest transport block size, which fits both the received downlink transport block and the downlink CRC bits. Table A.6.1 gives an example of an uplink radio bearer configuration for variable rate having three transports formats TF0, TF1 and TF2. Table A.6.2 gives some examples of UE selected uplink transport format versus size of received downlink transport block and downlink CRC bits.
The SS can use UE test loop mode 2 for testing UE blind transport format detection by taken the possible downlink transport formats into consideration when configuring the uplink transport formats. I.e. for every downlink transport format there should be an uplink transport format for which the transport block size is equal to the sum of the downlink transport block size and the number of downlink CRC bits. Thus the SS can check the TFI of the UE transmitted transport format to verify that the UE has detected the correct downlink transport format. Table A.6.3 gives an example of a configuration for testing blind transport format detection using 9 possible downlink transport formats TF0 to TF8. The right hand column shows the minimum uplink transport block sizes the SS has to set-up to be able to test the UE blind transport format detection behaviour.
Table A.6.1: Uplink transport formats
|
UL transport format |
Transport block size |
|
TF0 |
0 |
|
TF1 |
55 bits |
|
TF2 |
111 bits |
Table A.6.2: Selected uplink transport format versus size
of received downlink transport block and downlink CRC bits
|
DL transport block size |
Number of DL CRC bits |
Selected UL TF |
Comment |
|
39 bits |
16 bits |
TF1 |
39 + 16 = 55 i.e. TF1 ok |
|
40 bits |
16 bits |
TF2 |
TF1 not possible (40 + 16 = 56 > 55) TF2 OK (56 < 111) |
|
95 bits |
16 bits |
TF2 |
TF2 OK (95+16=111) |
|
96 bits |
16 bits |
TF2 |
96 + 16 = 112 is bigger than TF2 block size but no bigger TF available i.e. TF2 is selected and returned DL data and CRC is truncated (one bit of the DL CRC is not returned) |
Table A.6.3: Example of configuration for testing behaviour of UE blind transport format detection
|
DL TFI of DTCH |
UL TFI of DTCH Minimum required UL transport block size if DL CRC size=12 |
||
|
TF0 |
39 bits |
TF0 |
51 bits (39 + 12) |
|
TF1 |
95 bits |
TF1 |
107 bits (95 + 12) |
|
TF2 |
103 bits |
TF2 |
115 bits (103 + 12) |
|
TF3 |
118 bits |
TF3 |
130 bits (118 + 12) |
|
TF4 |
134 bits |
TF4 |
146 bits (134 + 12) |
|
TF5 |
148 bits |
TF5 |
160 bits (148 + 12) |
|
TF6 |
159 bits |
TF6 |
171 bits (159 + 12) |
|
TF7 |
204 bits |
TF7 |
216 bits (204 + 12) |
|
TF8 |
244 bits |
TF8 |
256 bits (244 + 12) |
A.7 Using UE test loop mode 1 for protocol testing
The parameter UL RLC SDU in CLOSE UE TEST LOOP message is used to control the behaviour of the UE test function behaviour regarding the uplink RLC SDU size.
In downlink the SS can control the downlink RLC SDU size by creating test data blocks of the size required for the test purpose.
Table A.7.1 describes the UE test function behaviour when operating in UE test loop mode 1 for different settings of DL and UL RLC SDU sizes:
Table A.7.1: UE test loop behaviour for different settings of DL and UL RLC SDU sizes.
|
UL RLC SDU size |
UE test loop behaviour |
|
= 0 |
Nothing is returned by UE in uplink |
|
= DL RLC SDU size |
All received data is returned by UE in uplink |
|
< DL RLC SDU size |
Received data is truncated by UE and sent in uplink |
|
> DL RLC SDU size |
Received data is repeated until UL RLC SDU block is filled and sent in uplink |
Examples of different configurations are shown in figures A.7.1 and A.7.2.
Figure A.7.1 illustrates a configuration for testing of RLC reassemble and segmentation. SS sends DL RLC SDU block size > DL RLC PDU block size and have configured UL RLC SDU block size = DL RLC SDU size > UL RLC PDU block size.
NOTE: For this type of configuration the UE receiver buffer limitations need to be considered when designing the test.
Figure A.7.2 illustrates a configuration for BER measurements. SS sends DL RLC SDU block size = DL RLC PDU block size and have configured UL RLC SDU block size = UL RLC PDU block size = DL RLC PDU block size. RLC and MAC are configured for transparent mode.
Figure A.7.1: Configuration for testing of RLC reassembly in downlink
and RLC segmentation in uplink
Figure A.7.2: Example of a configuration used for BER measurement
Annex B (informative):
Change history
|
Change history |
||||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
|
06/2000 |
TP-08 |
– |
– |
Approved at TSG-T #8 and placed under Change Control |
3.0.0 |
|||
|
09/2000 |
TP-09 |
TP-000162 |
001 |
Clarification of UE test loop mode 2 loop back scheme |
3.1.0 |
|||
|
TP-09 |
TP-000162 |
002 |
Clarification of loopback delay requirement |
3.1.0 |
||||
|
TP-09 |
TP-000162 |
003 |
Change Request about specification TS 34.109 |
3.1.0 |
||||
|
TP-09 |
TP-000162 |
004 |
UE test loop mode 1, loopback of PDCP SDUs |
3.1.0 |
||||
|
11/2000 |
– |
– |
– |
Handover of responsibility from TSG-T to TSG-RAN |
– |
|||
|
12/2000 |
RP-10 |
RP-000579 |
005 |
1 |
Setting up UE test loop for multiple radio bearer configurations |
3.2.0 |
||
|
03/2001 |
RP-11 |
RP-010036 |
006 |
Electrical Man Machine Interface |
3.3.0 |
|||
|
RP-11 |
– |
– |
Upgrade to Release 4 – no technical change |
4.0.0 |
||||
|
06/2001 |
RP-12 |
RP-010319 |
008 |
Clarification to Loopback Delay requirement & BTFD in TDD mode |
4.1.0 |
|||
|
RP-12 |
RP-010319 |
010 |
Expanding UE test loop buffering capabilities to enable testing of 2048 kbps radio bearers |
4.1.0 |
||||
|
03/2002 |
RP-15 |
RP-020077 |
012 |
Clarifications of UE conformance test functions |
4.2.0 |
|||
|
RP-15 |
– |
– |
Upgrade to Release 5 – no technical change |
5.0.0 |
||||
|
06/2002 |
RP-16 |
RP-020338 |
015 |
Correction to UE test loop mode 2 |
5.1.0 |
|||
|
RP-16 |
RP-020338 |
018 |
Clarification of test loop performance requirements |
5.1.0 |
||||
|
12/2002 |
RP-18 |
RP-020728 |
022 |
Reference Measurement Channels references |
5.2.0 |
|||
|
03/2003 |
RP-19 |
RP-030162 |
025 |
1 |
Removal of uplink dummy DCCH transmission function in UE |
5.3.0 |
||
|
09/2004 |
RP-25 |
RP-040329 |
029 |
UE test loop mode with PDCP configuration |
5.4.0 |
|||
|
RP-25 |
RP-040329 |
033 |
1 |
Addition of RESET UE POSITIONING STORED INFORMATION message |
5.4.0 |
|||
|
RP-25 |
RP-040337 |
034 |
Increase of maximum number of loopback entities |
5.4.0 |
||||
|
12/2004 |
RP-26 |
– |
– |
Upgrade to the Release 6. No technical change |
6.0.0 |
|||
|
06/2005 |
RP-28 |
RP-050301 |
0036 |
Clarification of loopback behaviour for uni-directional radio bearers |
6.1.0 |
|||
|
09/2006 |
RP-33 |
RP-060571 |
0037 |
Introduction of UE test loop mode 3 (SDU counters) to support MTCH performance testing |
6.2.0 |
|||
|
RP-33 |
– |
– |
Upgrade to the Release 7. No technical change |
7.0.0 |
||||
|
12/2006 |
RP-34 |
RP-060716 |
0040 |
Enhancements of UE test loop mode 1 for E-DCH RF performance testing |
7.1.0 |
|||
|
03/2007 |
RP-35 |
RP-070153 |
0042 |
2 |
Correction of max RLC SDU size |
7.2.0 |
||
|
09/2008 |
RP-41 |
RP-080680 |
0043 |
Enhancement of UE test loop mode 3 for testing reception of MBMS services operating in MBSFN mode |
7.3.0 |
|||
|
12/2008 |
RP-42 |
– |
– |
– |
Upgrade to Release 8 – no technical change |
8.0.0 |
||
|
12/2009 |
RP-46 |
– |
– |
– |
Upgrade to Release 9 – no technical change |
9.0.0 |
||
|
09/2010 |
RP-49 |
RP-100861 |
0044 |
– |
Addition of RESET command for GNSS (contact: Qualcomm) |
9.1.0 |
||
|
03/2011 |
RP-51 |
RP-110263 |
0048 |
– |
Introduction of UE test loop mode 4 for testing of network initiated secondary PDP context |
9.2.0 |
||
|
03/2011 |
RP-51 |
– |
– |
– |
Upgrade to Release 10 – without technical change |
10.0.0 |
||
|
12/2011 |
RP-54 |
RP-111715 |
0050 |
– |
Corrections to UE test loop mode 4 |
10.1.0 |
||
|
09/2012 |
RP-57 |
– |
– |
– |
Upgrade to Release 11 – without technical change |
11.0.0 |
||
|
03/2013 |
RP-59 |
RP-130238 |
0053 |
1 |
Addition of Location Information functionality to 34.109 |
11.1.0 |
||
|
03/2014 |
RP-63 |
RP-140344 |
0056 |
– |
Update to UE radio bearer test mode for CSG proximity testing |
11.2.0 |
||
|
09/2014 |
RP-65 |
– |
– |
– |
Upgrade to the Release 12 – no technical change |
12.0.0 |
||
|
12/2015 |
RP-70 |
– |
– |
– |
Upgrade to the Release 13 – no technical change |
13.0.0 |
||
|
03/2017 |
RP-75 |
Upgrade to Release 14 – no technical change |
14.0.0 |
|||||
|
07/2018 |
RP-80 |
Upgrade to Release 15- no technical change |
15.0.0 |
|||||
|
07/2020 |
RP-88 |
Upgrade to Release 16- no technical change |
16.0.0 |
|||||
|
03/2022 |
RP-95 |
Upgrade to Release 17- no technical change |
17.0.0 |
|||||