5.4 UE test loop procedures

36.5093GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Release 17Special conformance testing functions for User Equipment (UE)TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.4.1 General

The UE test loop function is intended for:

– E-UTRA RF receiver and transmitter testing to generate data transfer in downlink and uplink.

– E-UTRA layer 2 (MAC, RLC, PDCP) and data radio bearer testing to generate data transfer in downlink and uplink.

– EPC and E-UTRA layer 3 testing to verify data transfer continuation over RRC and EPC procedures.

– EPC NAS user-plane testing to verify uplink TFT handling.

– E-UTRA/EPC Inter-system testing to verify data transfer continuation over Inter-system change procedures to and from UTRA, GSM/GPRS and CDMA2000.

– E-UTRA/E-MBMS MCH performance testing.

– E-UTRA/E-MBMS layer 2 (MAC, RLC) and MTCH data radio bearer testing.

– E-UTRA/ProSe or V2X RF receiver and transmitter testing to generate data transfer in sidelink.

– E-UTRA/ProSe Direct Discovery layer 2 (MAC) SL-DCH performance testing.

– E-UTRA/ProSe Direct or V2X Communication layer 2 (MAC, RLC, PDCP) STCH and layer 1 (PHY) PSCCH/PSSCH performance testing.

– NB-IoT user plane testing.

– Control Plane layer 2 (MAC, RLC), layer 3 and NAS testing for CIoT.

5.4.2 Close UE test loop

Figure 5.4.2-1: Close UE test loop procedure in all but V2X communication in out-of-coverage state scenarios

Figure 5.4.2-2: Close UE test loop procedure by AT Command for V2X communication in out-of-coverage state scenarios

5.4.2.1 General

The SS uses the close UE test loop procedure to start the UE Test Loop function in the UE while in E-UTRA or NB-IoT mode or while in V2X out-of-coverage state.

A prerequisite for UE test loop mode A is that at least one bi-directional data radio bearer has been established between SS and UE.

A prerequisite for UE test loop mode B is that at least one EPS bearer context has been established between SS and UE.

A prerequisite for UE test loop mode C is that at least one MTCH data radio bearer has been established between SS and UE.

A prerequisite for UE test loop mode D is that the UE is pre-authorized for ProSe Direct Discovery operation.

NOTE 1: No radio bearer setup is required to transmit or receive ProSe Direct Discovery messages.

A prerequisite for UE test loop mode E is that the UE is pre-authorized for ProSe Direct or V2X Communication operation and pre-configured parameters are provided in the USIM.

NOTE 2: Explicit signalling for sidelink radio bearer (SLRB) is not required to transmit or receive STCH for ProSe Direct Communication.

A prerequisite for UE test loop mode F is that at least one SC-MTCH data radio bearer has been established between SS and UE.

The UE shall provide for normal layer 1, layer 2, RRC, EMM and ESM functionality while the UE test loop function is active. This includes (but is not limited to) handover procedures and normal disconnection of the data radio bearer.

For UE test loop mode A the loopback shall be maintained across handovers within E-UTRA and NB-IoT, but after data radio bearer release, the loopback shall cease to exist.

For UE test loop mode G and UE test loop mode H the loopback shall be maintained across handovers and cell re-selections within its RAT (e.g. within E-UTRA at handovers and re-selections for E-UTRA UE and between NB-IoT cells at cell re-selections for NB-IoT UE).

For UE test loop mode B the loopback shall be maintained across handovers within E-UTRA and between radio access system (E-UTRA to/from UTRA, E-UTRA to/from GSM/GPRS and E-UTRA to/from CDMA2000). This means that any buffered IP PDUs in the UE test loop function at the time of the intra- or inter-system change shall be kept in the UE test loop function and being scheduled for transmission transparently to the intra- or inter-system change.

For UE test loop mode A, or B, the UE shall not transmit any uplink U-plane data other than the data returned by the loopback entity.

For UE test loop mode G or I the UE shall not transmit any uplink ESM DATA TRANSPORT other than the ones initiated by the loopback entity.

For UE test loop mode D and E for Prose Discovery or Direct Communication, the UE (and not the test loop) shall provide full normal ProSe functionality as specified in TS 24.334 [38] and TS 36.331 [25] e.g. ProSe synchronization signals transmission and/or reception as configured by RRC, while the UE test loop is active.

For UE test loop mode E for V2X Communication, the UE (and not the test loop) shall provide full normal V2X communication functionality as specified in TS 24. 386 [38] and TS 36.331 [25] e.g. V2X communication reception and transmission, while the UE test loop is active.

5.4.2.1a UE test loop mode A PDCP SDU and UE test loop mode B IP PDU buffer size requirement

The minimum UE loopback buffer size for PDCP SDUs (UE test loop mode A) and IP PDUs (UE test loop mode B), when UE is operated in RLC AM or UM mode, shall be according to table 5.4.2.1a-1. The UE behaviour, when the loopback buffer capacity is exceeded, is unspecified.

Table 5.4.2.1a-1: Minimum loopback buffer size for different UE categories

UE Category	Minimum loopback buffer size [bytes] (Note 1,2)
Category NB1/NB2	4000
Category M1	4000
Category M2	4000
Category 0	4000
Category 1	60000
Category 2	60000
Category 3	60000
Category 4	60000
Category 5	60000
Note 1: Minimum loopback buffer size has been selected 1) for each UE category such that the UE shall be able to forward all data received in one TTI when the applicable maximum transport block size of the UE is used, and 2) to allow execution of MAC test cases 7.1.4.3 and 7.1.4.3a in TS 36.523-1 [30], which requires a minimum loopback buffer size of 3600 bytes for Category M1, Category M2, Category 0 and Category 1 (7.1.4.3a) and 57280 bytes for all other UE categories(7.1.4.3). Note 2: The minimum loopback buffer size requirement for Category NB1/NB2 is only applicable for NB-IoT UE that supports user plane data.

5.4.2.1b UE test loop mode G and UE test loop mode H buffer size, User data container size and TP-User-Data buffer size requirements

The minimum UE loopback buffer size for user data for UE test loop mode G and UE test loop mode H shall be according to table 5.4.2.1b-1. The UE behaviour, when the loopback buffer capacity is exceeded, is unspecified.

The minimum User data container for UE test loop mode G and TP-User-Data buffer size for UE test loop mode H shall be according to table 5.4.2.1b-1. The UE behaviour, when the User data container for UE test loop mode G and TP-User-Data size for UE test loop mode H exceeds the values in table 5.4.2.1b-1, is unspecified.

Table 5.4.2.1b-1: Minimum loopback buffer size and minimum User data container size and TP-User-Data buffer size for different UE categories

UE Category	Minimum loopback buffer size for UE test loop mode G and H [octets] (Note 2)	Minimum User data container size in ESM DATA TRANSFER message for UE test loop mode G [octets] (note 2)	Minimum TP-User-Data buffer size for UE test loop mode H [octets] (Note 1,2)
Category NB1/NB2	1358	1358	140
Category M1	1358	1358	140
Category M2	1358	1358	140
Category 0	1358	1358	140
Category 1	1358	1358	140
Category 2	1358	1358	140
Category 3	1358	1358	140
Category 4	1358	1358	140
Category 5	1358	1358	140
Note 1: The minimum TP-User-Data buffer size is set to the maximum SMS size of 160 characters (140 octets). Note 2: The minimum loopback buffer size, the minimum User data container size and minimum TP-User-Data buffer size requirements for Category 0 and higher categories are only applicable for UE that supports control plane data. Note 3: The minimum loopback buffer size for UE test loop mode G and H and minimum user data container size in ESM DATA TRANSFER message for UE test loop mode G is set to 1358 octets as this is the maximum link MTU value in the IP configuration information set from the network to a UE that will prevent the IP layer fragmentation within the transport network between the UE and the GGSN/P-GW ([39] TS 23.060 clause 9.3).

5.4.2.2 Initiation

The SS can request the UE to close a test loop in mode A if at least one bi-directional data radio bearer is established and the UE test mode is active.

The SS can request the UE to close a test loop in mode B if at least one EPS bearer is established and the UE test mode is active. The SS can request the UE to close a test loop in mode C if at least one MTCH data radio bearer is established and the UE test mode is active.

The SS requests the UE to close its UE test loop mode A, UE test loop mode B, UE test loop mode C, UE test loop mode D or UE test loop mode E (when not utilised in V2X out-of-coverage scenarios) by transmitting a CLOSE UE TEST LOOP message.

The SS requests the UE to close its UE test loop mode E by transmitting an AT Command +CCUTLE when test loop mode E is utilised in V2X out-of-coverage scenarios.

5.4.2.3 Reception of CLOSE UE TEST LOOP message by the UE

Upon receiving the CLOSE UE TEST LOOP message the UE shall:

1> if UE test loop mode A has been selected;

2> if no bi-directional data radio bearers are established or if the UE test mode is not active; or

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or

2> if TEST_LOOP_MODE_C_ACTIVE = TRUE or TEST_LOOP_MODE_D_ACTIVE = TRUE or TEST_LOOP_MODE_E_ACTIVE = TRUE or TEST_LOOP_MODE_F_ACTIVE = TRUE or TEST_LOOP_MODE_G_ACTIVE = TRUE or TEST_LOOP_MODE_H_ACTIVE = TRUE or TEST_LOOP_MODE_I_ACTIVE = TRUE:

3> the UE behaviour is unspecified

2> else:

3> for LB_ID=0 MAX_ModeA_LB_entities -1:

4> set DRB_ID(LB_ID) to 0 (indicate no DRB mapped)

4> set UL_PDCP_SDU_scaling(LB_ID) to FALSE

3> set LB_ID to 0

3> for each established bi-directional data radio bearer in ascending order and starting with the data radio bearer with the lowest configured Data Radio bearer identity number:

4> if LB_ID is less than MAX_ModeA_LB_entities:

5> set DRB_ID(LB_ID) to the Data Radio bearer identity number

5> increment LB_ID by 1

4> else:

5> the UE behaviour is unspecified

3> if the UE test loop mode A setup IE is included:

4> for each LB Setup DRB IE in the LB setup list of the UE test loop mode A setup IE:

5> for LB_ID=0 to MAX_ModeA_LB_entities-1:

6> if DRB_ID(LB_ID) is equal to the Data Radio bearer identity number parameter of the LB Setup DRB IE:

7> if the LB Setup DRB(LB_ID) IE is included:

7> set UL_PDCP_SDU_scaling(LB_ID) to TRUE

7> set UL_PDCP_SDU_size(LB_ID) to UL PDCP SDU size parameter of the LB Setup DRB(LB_ID) IE

3> perform the UE actions for UE Test Loop Mode A operation as specified in subclause 5.4.3; and

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode B has been selected;

2> if no EPS bearer is established or if the UE test mode is not active; or

2> if the test loop is already active on one or more EPS bearers; or

3> the UE behaviour is unspecified.

2> otherwise:

3> set TEST_LOOP_MODE_B_ACTIVE to TRUE

3> set timer T_delay_modeB to the value of IP PDU delay timer parameter of the UE test loop mode B IE;

3> if the IP PDU delay timer parameter of the UE test loop mode B IE has a value larger than zero:

4> set BUFFER_IP_PDUs to TRUE

3> else:

4> set BUFFER_IP_PDUs to FALSE

3> set CDMA2000_INITIATED to FALSE

3> perform the UE actions for UE Test Loop Mode B operation as specified in subclause 5.4.4 and 5.4.4.1 to 5.4.4.11; and

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode C has been selected;

2> if no MTCH data radio bearer is established or if the UE test mode is not active; or

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or

3> the UE behaviour is unspecified.

2> otherwise:

3> set TEST_LOOP_MODE_C_ACTIVE to TRUE

3> set state variable MBMS_PACKET_COUNTER to zero;

3> perform the UE actions for UE Test Loop Mode C operation as specified in subclause 5.4.4a; and

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode D has been selected;

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or

3> the UE behaviour is unspecified.

2> otherwise:

3> set TEST_LOOP_MODE_D_ACTIVE to TRUE

3> if the Discovery Announce or Monitor parameter in UE test loop mode D setup IE is set as zero;

4> set TEST_LOOP_MODE_D_TRIGGER to MONITOR

4> set state variable PROSE_DISCOVERY_MONITOR_N to the number of entities in the list of ProSe App Codes to individually monitor included in the UE test loop mode D setup IE;

4> if PROSE_DISCOVERY_MONITOR_N is greater than MAX_ModeD_Monitor_Entities:

5> the UE behaviour is unspecified.

4> for SL_ID = 0…(PROSE_DISCOVERY_MONITOR_N-1):

5> set state variable PROSE_DISCOVERY_APPCODE(SL_ID) to the parameter ProSe App Code (LSBs) #(SL_ID) to monitor of the UE test loop mode D setup IE;

5> set state variable PSDCH_PACKET_COUNTER(SL_ID) to zero;

4> set state variable PSDCH_PACKET_COUNTER(PROSE_DISCOVERY_MONITOR_N) to zero;

4> perform the UE actions for UE Test Loop Mode D operation as specified in subclause 5.4.4b;

3> if the Discovery Announce or Monitor parameter in UE test loop mode D setup IE is set as one;

4> set TEST_LOOP_MODE_D_TRIGGER to ANNOUNCE

4> perform the UE actions for UE Test Loop Mode D operation as specified in subclause 5.4.4b;

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode E has been selected;

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or

2> if the UE is unable to read the pre-configured parameters for ProSe Direct or V2X Communication from the USIM; or

2> when test loop mode E is utilised in V2X out-of-coverage scenarios:

3> the UE behaviour is unspecified.

2> otherwise:

3> set TEST_LOOP_MODE_E_ACTIVE to TRUE

3> if the Communication Transmit or Receive parameter in UE test loop mode E setup IE is set as zero;

4> set TEST_LOOP_MODE_E_TRIGGER to RECEIVE

4> set state variable PROSE_COMMUNICATION_MONITOR_N to the number of entities in the list of Group Destination IDs to individually monitor included in the UE test loop mode E setup IE;

4> if PROSE_COMMUNICATION_MONITOR_N is greater than MAX_ModeE_Monitor_Entities:

5> the UE behaviour is unspecified.

4> for SL_ID = 0…(PROSE_COMMUNICATION_MONITOR_N-1):

5> set state variable PROSE_COMMUNICATION_DEST_ID(SL_ID) to the parameter Group Destination ID #(SL_ID) to monitor of the UE test loop mode E setup IE;

5> set state variable STCH_PACKET_COUNTER(SL_ID) to zero;

5> set state variable PSCCH_PACKET_COUNTER(SL_ID) to zero;

5> set state variable PSSCH_PACKET_COUNTER(SL_ID) to zero;

4> set state variable STCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) to zero;

4> set state variable PSCCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) to zero;

4> set state variable PSSCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) to zero;

4> perform the UE actions for UE Test Loop Mode E operation as specified in subclause 5.4.4c;

3> if the Communication Transmit or Receive parameter in UE test loop mode E setup IE is set as one;

4> set TEST_LOOP_MODE_E_TRIGGER to TRANSMIT

4> perform the UE actions for UE Test Loop Mode E operation as specified in subclause 5.4.4c;

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode F has been selected;

2> if no SC-MTCH data radio bearer is established or if the UE test mode is not active; or

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or

2> if TEST_LOOP_MODE_C_ACTIVE = TRUE or TEST_LOOP_MODE_D_ACTIVE = TRUE or TEST_LOOP_MODE_E_ACTIVE = TRUE or TEST_LOOP_MODE_F_ACTIVE = TRUE: or TEST_LOOP_MODE_G_ACTIVE = TRUE or TEST_LOOP_MODE_H_ACTIVE = TRUE or TEST_LOOP_MODE_I_ACTIVE = TRUE

3> the UE behaviour is unspecified.

2> otherwise:

3> set TEST_LOOP_MODE_F_ACTIVE to TRUE

3> set state variable SCPTM_PACKET_COUNTER to zero;

3> perform the UE actions for UE Test Loop Mode F operation as specified in subclause 5.4.4d; and

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode G has been selected;

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or;

2> if TEST_LOOP_MODE_C_ACTIVE = TRUE or TEST_LOOP_MODE_D_ACTIVE = TRUE or TEST_LOOP_MODE_E_ACTIVE = TRUE or TEST_LOOP_MODE_F_ACTIVE = TRUE or TEST_LOOP_MODE_H_ACTIVE = TRUE or TEST_LOOP_MODE_I_ACTIVE = TRUE:

3> the UE behaviour is unspecified;

2> otherwise:

3> set TEST_LOOP_MODE_G_ACTIVE to TRUE;

3> if the uplink loopback operation mode parameter of the UE test loop mode GH setup IE has a value set to 1:

4> set GH_RLC_SDU_loopback to TRUE;

3> else:

4> set GH_RLC_SDU_loopback to FALSE;

3> set GH_NUMBER_UL_DATA_REPETITIONS to the value of number of repetitions parameter of the UE test loop mode GH setup IE;

3> set timer T_delay_modeGH to the value of Uplink data delay timer parameter of the UE test loop mode GH setup IE;

3> if the Uplink data delay timer parameter of the UE test loop mode GH setup IE has a value larger than zero:

4> set GH_BUFFER_CP_data to TRUE;

3> else:

4> set GH_BUFFER_CP_data to FALSE;

3> perform the UE actions for UE Test Loop Mode G operation in CP data loopback mode as specified in subclause 5.4.4e;

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement);

else if UE test loop mode H has been selected;

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or;

3> the UE behaviour is unspecified;

2> otherwise:

3> set TEST_LOOP_MODE_H_ACTIVE to TRUE;

3> if the uplink loopback operation mode parameter of the UE test loop mode GH setup IE has a value set to 1:

4> set GH_RLC_SDU_loopback to TRUE;

3> else:

4> set GH_RLC_SDU_loopback to FALSE;

3> set GH_NUMBER_UL_DATA_REPETITIONS to the value of number of repetitions parameter of the UE test loop mode GH setup IE;

3> set timer T_delay_modeGH to the value of Uplink data delay timer parameter of the UE test loop mode GH setup IE;

3> if the Uplink data delay timer parameter of the UE test loop mode GH setup IE has a value larger than zero:

4> set GH_BUFFER_CP_data to TRUE;

3> else:

4> set GH_BUFFER_CP_data to FALSE;

3> perform the UE actions for UE Test Loop Mode H operation as specified in subclause 5.4.4f.1; and

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else if UE test loop mode I has been selected;

2> if UE test loop mode A or UE test loop mode B operation is already closed on one or more data radio bearers; or;

3> the UE behaviour is unspecified;

2> otherwise:

3> set TEST_LOOP_MODE_I_ACTIVE to TRUE;

3> perform the UE actions for UE Test Loop Mode I operation as specified in subclause 5.4.4g.1; and

3> send CLOSE UE TEST LOOP COMPLETE message (the loopback shall be operational prior to the sending of the acknowledgement).

1> else;

2> the UE behaviour is unspecified.

5.4.2.4 Reception of AT Command +CCUTLE by the UE

Upon receiving the AT Command +CCUTLE=<status=0>[,<direction>[,<format>,<length>,<monitor_list>]] the UE shall:

1> if UE test loop mode E has been selected;

2> if TEST_LOOP_MODE_E_ACTIVE = TRUE; or

2> if the UE is unable to read the pre-configured parameters for V2X Communication from the USIM:

3> the UE behaviour is unspecified.

2> otherwise:

3> set TEST_LOOP_MODE_E_ACTIVE to TRUE

3> if the <direction> parameter in +CCUTLE set command is set as zero;

4> set TEST_LOOP_MODE_E_TRIGGER to RECEIVE

4> if the <format> parameter in +CCUTLE set command is set as 1

5> set state variable PROSE_COMMUNICATION_MONITOR_N to the number of entities in the list of Destination Layer-2 IDs to individually monitor included in the <monitor_list> parameter of +CCUTLE set command;

5> if PROSE_COMMUNICATION_MONITOR_N is greater than MAX_ModeE_Monitor_Entities:

6> the UE behaviour is unspecified.

5> for SL_ID = 0…(PROSE_COMMUNICATION_MONITOR_N-1):

6> set state variable PROSE_COMMUNICATION_DEST_ID(SL_ID) to the parameter Destination Layer-2 ID #(SL_ID) to monitor in the +CCUTLE set command;

6> set state variable STCH_PACKET_COUNTER(SL_ID) to zero;

6> set state variable PSCCH_PACKET_COUNTER(SL_ID) to zero;

6> set state variable PSSCH_PACKET_COUNTER(SL_ID) to zero;

5> set state variable STCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) to zero;

5> set state variable PSCCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) to zero;

5> set state variable PSSCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) to zero;

5> perform the UE actions for UE Test Loop Mode E operation as specified in subclause 5.4.4c;

4> else

5> the UE behaviour is unspecified.

3> if the <direction> parameter in +CCUTLE set command is set as one;

4> set TEST_LOOP_MODE_E_TRIGGER to TRANSMIT

4> perform the UE actions for UE Test Loop Mode E operation as specified in subclause 5.4.4c;

1> else;

2> the UE behaviour is unspecified.

5.4.3 UE test loop mode A operation

Upon receiving a PDCP SDU identified by LB_ID when operating in E-UTRA or NB-IoT mode with UE Test Loop Mode A active the UE shall:

1> if UL_PDCP_SDU_scaling(LB_ID) is FALSE:

2> take the PDCP SDU from the output of the PDCP Service Access Point (SAP) and provide it as input to the correspondent PDCP SAP in uplink and transmit, see Figure 5.4.3-1.

1> else:

2> if UL_PDCP_SDU_size(LB_ID) = 0:

3> discard the PDCP SDU (no data is returned).

2> else:

3> if the size of the received PDCP SDU in downlink is equal to UL_PDCP_SDU_size(LB_ID):

4> take the PDCP SDU from the output of the PDCP SAP and provide it as input to the correspondent PDCP SAP in uplink and transmit, see Figure 5.4.3-1.

3> else if the size of the received PDCP SDU in downlink is bigger than UL_PDCP_SDU_size(LB_ID):

4> create a UL PDCP SDU of size UL_PDCP_SDU_size(LB_ID) by taking the first K bits of the received PDCP SDU in downlink PDCP SAP, where K is equal to UL_PDCP_SDU_size(LB_ID) and provide it as input to the correspondent PDCP SAP in uplink and transmit, see Figure 5.4.3-2.

3> else if the size of the received PDCP SDU in downlink is less than UL_PDCP_SDU_size(LB_ID):

4> create a UL PDCP SDU of size UL_PDCP_SDU_size(LB_ID) by repeating the data received in downlink PDCP SDU in downlink to fill the UL PDCP SDU (truncating the last block if necessary), provide it as input to the correspondent PDCP SAP in uplink and transmit, see Figure 5.4.3-3.

Note: Size of the received PDCP SDUs in downlink shall be bit strings that are byte aligned (i.e. multiple of 8 bits) according to TS 36.323 [24] clause 6.2.1.

Figure 5.4.3-1: Loop back of PDCP SDU
(DL PDCP SDU size = UL PDCP SDU size = N)

Figure 5.4.3-2: DL > UL PDCP SDU block size
(DL PDCP SDU size = N, UL PDCP SDU size = K)

Figure 5.4.3-3: DL < UL PDCP SDU block size
(DL PDCP SDU size = N, UL PDCP SDU size = 2*N + K)

5.4.4 UE test loop mode B operation

5.4.4.1 Void

5.4.4.2 Reception of IP PDUs when UE is in E-UTRA or NB-IoT mode

Upon receiving a PDCP SDU (=IP PDU) when operating in E-UTRA or NB-IoT mode with UE Test Loop Mode B active the UE shall:

1> if T_delay_modeB timer is running:

2> buffer the received PDCP SDU

1> else

2> if BUFFER_IP_PDUs is TRUE

3> buffer the received PDCP SDU

3> Start T_delay_modeB timer

2> else

3> submit the received PDCP SDU without any modification of the IP header to the UL TFT handling SAP for transmission in uplink. See note.

Note 1: The UL TFT function in the UE is mapping IP PDUs received from SDF to EPS bearer/radio bearer as configured by SS in the UL TFT IE sent as part of the EPS bearer establishment procedures. See figure 5.1-2.

Note 2: Size of the received PDCP SDUs in downlink shall be bit strings that are byte aligned (i.e. multiple of 8 bits) according to TS 36.323 [24] clause 6.2.1. The PDCP SDUs themselves shall contain a valid IPv4 or IPv6 Header in accordance with the PDN type (Ref. TS 24.301 [36]) accepted by the UE.

5.4.4.3 Expiry of T_delay_modeB timer when UE is in E-UTRA or NB-IoT mode

When timer T_delay_modeB expires when UE is operating in E-UTRA or NB-IoT mode and has UE Test Loop Mode B active then the UE shall:

1> submit the buffered PDCP SDUs in the same order as received (first-in-first-out) and without any modification of the IP header to the UL TFT handling SAP for transmission in uplink. See note 1.

1> set BUFFER_IP_PDUs to FALSE

NOTE 2: After the PDCP SDU buffer becomes empty the loopback will return any received PDCP SDU in uplink directly as specified in clause 5.4.4.2. In order to reactivate the loopback delay and PDCP SDU buffering the SS shall deactivate UE test loop B function first.

5.4.4.4 Reception of IP PDUs when UE is in UTRA mode

When UE receives a PDCP SDU when UE is operating in UTRA mode and has UE Test Loop Mode B active then the UE shall:

1> if T_delay_modeB timer is running:

2> buffer the received PDCP SDU

1> else

2> if BUFFER_IP_PDUs is TRUE

3> buffer the received PDCP SDU

3> Start T_delay_modeB timer

2> else

3> submit the received PDCP SDU without any modification of the IP header to the UL TFT handling SAP for transmission in uplink.

5.4.4.5 Expiry of T_delay_modeB timer when UE is in UTRA mode

When timer T_delay_modeB expires when UE is operating in UTRA mode and has UE Test Loop Mode B active the then UE shall:

1> submit the buffered IP PDUs in the same order as received (first-in-first-out) and without any modification of the IP header to the UL TFT handling SAP for transmission in uplink.

1> set BUFFER_IP_PDUs to FALSE.

NOTE: After the IP PDU buffer becomes empty the loopback will return any received PDCP SDU in uplink directly as specified in clause 5.4.4.4. In order to reactivate the loopback delay and PDCP SDU buffering the SS shall deactivate UE test loop B function and UE shall return to E-UTRA or NB-IoT mode first.

5.4.4.6 Reception of IP PDUs when UE is in GSM/GPRS mode

When UE receives a SNDCP SDU when UE is operating in GSM/GPRS mode and has UE Test Loop Mode B active then the UE shall:

1> if T_delay_modeB timer is running:

2> buffer the received SNDCP SDU.

1> else

2> if BUFFER_IP_PDUs is TRUE;

3> buffer the received SNDCP SDU;

3> Start T_delay_modeB timer.

2> else

3> submit the received SNDCP SDU without any modification of the IP header to the UL TFT handling SAP for transmission in uplink.

5.4.4.7 Expiry of T_delay_modeB timer when UE is in GSM/GPRS mode

When timer T_delay_modeB expires when UE is operating in GSM/GPRS mode and has UE Test Loop Mode B active then the UE shall:

1> submit the buffered IP PDUs without any modification of the IP header in the same order as received (first-in-first-out), to the UL TFT handling SAP for transmission in uplink.

1> set BUFFER_IP_PDUs to FALSE

NOTE: After the IP PDU buffer becomes empty the loopback will return any received SNDCP SDU in uplink directly as specified in clause 5.4.4.6. In order to reactivate the loopback delay and SNDCP SDU buffering the SS shall deactivate UE test loop B function and UE shall return to E-UTRA or NB-IoT mode first.

5.4.4.8 Reception of IP PDUs when UE is in CDMA2000 mode

When UE receives a RLP SDU when UE is operating in CDMA2000 mode and has UE Test Loop Mode B active then the UE shall:

1> if CDMA2000_INITIATED is FALSE:

2> if T_delay_modeB is running:

3> restart T_delay_modeB

2> else:

3> start T_delay_modeB

2> set CDMA2000_INITIATED to TRUE;

1> if T_delay_modeB is running;

2> deliver the received RLP SDU to upper layers;

1> else

2> submit the received RLP SDU without any modification of the IP header to the UL TFT handling SAP for transmission in uplink.

NOTE: When CDMA2000_INITIATED is FALSE or when T_delay_modeB is running, the UE may send RLP SDUs in uplink upon initiation from upper layers.

5.4.4.9 Expiry of T_delay_modeB timer when UE is in CDMA2000 mode

When timer T_delay_modeB expires when UE is operating in CDMA2000 mode and has UE Test Loop Mode B active then the UE shall not take any action.

5.4.4.10 Establishment of the RRC/RR connection in E-UTRA, NB-IoT, UTRA, GSM/GPRS and CDMA2000 mode

When the RRC or the RR connection and one or more EPS bearers are is established, in E-UTRA, NB-IoT, UTRA, GSM/GPRS and CDMA2000 mode then the UE shall:

1> if TEST_LOOP_MODE_B_ACTIVE is set to TRUE;

2> perform the UE actions for UE Test Loop Mode B operation as specified in subclause 5.4.4 and 5.4.4.1 to 5.4.4.11.

5.4.4.11 Release of RRC/RR connection in E-UTRA, NB-IoT, UTRA, GSM/GPRS and CDMA2000 mode after T_delay_modeB timer has expired

When the RRC or the RR connection is released in E-UTRA, NB-IoT, UTRA, GSM/GPRS and CDMA2000 mode then the UE shall:

1> if UE test loop mode B is active; and

1> if BUFFER_IP_PDUs is TRUE or T_delay_modeB timer is running:

2> keep UE test loop mode B active

1> else

2> the UE behaviour is unspecified.

5.4.4a UE test loop mode C operation

5.4.4a.1 Reception of MBMS packets

Upon receiving a MBMS packet on the MTCH identified by MTCH_ID when operating in E-UTRA idle or connected mode with UE test loop mode C active the UE shall:

1> if UE test loop mode C is active;

2> increment MBMS_PACKET_COUNTER by 1:

1> else:

2> the UE behaviour is unspecified.

5.4.4a.2 Release of RRC connection

When the RRC connection is released in E-UTRA mode then the UE shall:

1> if UE test loop mode C is active:

2> keep UE test loop mode C active.

5.4.4b UE test loop mode D operation

5.4.4b.1 Monitor or Announce ProSe Direct Discovery

When operating in E-UTRA idle or connected mode with UE test loop mode D active, the UE shall be able to either monitor or announce ProSe Direct Discovery message(s) based on the TEST_LOOP_MODE_D_TRIGGER being set as either MONITOR or ANNOUNCE, respectively. The UE shall:

1> if TEST_LOOP_MODE_D_ACTIVE is set to TRUE:

2> if TEST_LOOP_MODE_D_TRIGGER is set to MONITOR;

3> upon successful reception of SL-DCH MAC SDU for ProSe Direct Discovery message:

4> set MATCH to zero;

4> if PROSE_DISCOVERY_MONITOR_N > 0

5> for SL_ID = 0…(PROSE_DISCOVERY_MONITOR_N-1):

6> if LSBs (8..0) of ProSe App Code in the received SL-DCH MAC SDU equals PROSE_DISCOVERY_APPCODE(SL_ID):

7> increment PSDCH_PACKET_COUNTER(SL_ID) by 1;

7> set MATCH to one.

4> if MATCH equal zero:

5> increment PSDCH_PACKET_COUNTER(PROSE_DISCOVERY_MONITOR_N) by 1.

2> else if TEST_LOOP_MODE_D_TRIGGER is set to ANNOUNCE;

3> create the SL-DCH MAC SDU with the payload specified below, see Figure 5.4.4b.1-1 and Table 5.4.4b.1-1, and provide as input to MAC for possible transmission in each discovery period.

NOTE: The same SL-DCH MAC SDU is transmitted (if permitted by test specific Layer 1 and Layer 2 configuration) by the UE in every discovery period during the entire duration test loop mode D is closed.

2> else:

3> the UE behaviour is unspecified.

1> else:

2> the UE behaviour is unspecified.

The SL-DCH MAC SDU payload for ProSe Direct Discovery announce operation when UE test loop mode D is active shall be as specified in Figure 5.4.4b.1-1 and Table 5.4.4b.1-1.

Figure 5.4.4b.1-1: ProSe Direct Discovery Announce operation in UE test loop mode D

Table 5.4.4b.1-1: SL-DCH MAC SDU payload contents for ProSe Direct Discovery Announce operation in UE test loop mode D

Parameter	Size (bits)	Value
Msg Type	8	01000001
ProSe App Code	184	00…00
MIC	32	00…00
Cntr LSB	4	0000

5.4.4b.2 Release of RRC connection

When the RRC connection is released in E-UTRA mode then the UE shall:

1> if UE test loop mode D is active:

2> keep UE test loop mode D active

5.4.4c UE test loop mode E operation

5.4.4c.1 Receive or Transmit ProSe Direct or V2X Communication

When operating in E-UTRA idle or connected or any cell selection state or out-of-coverage state for V2X test scenarios, with UE test loop mode E active, the UE shall be able to either receive or transmit ProSe Direct or V2X Communication packets based on the TEST_LOOP_MODE_E_TRIGGER being set as either RECEIVE or TRANSMIT, respectively. The UE shall:

1> if TEST_LOOP_MODE_E_ACTIVE is set to TRUE:

2> if TEST_LOOP_MODE_E_TRIGGER is set to RECEIVE;

3> upon successful reception of a STCH PDCP SDU for ProSe Direct or V2X Communication data packet:

4> set MATCH to zero;

4> if PROSE_ COMMUNICATION_MONITOR_N > 0

5> for SL_ID = 0…(PROSE_COMMUNICATION_MONITOR_N-1):

6> if Group Destination ID in the received PSCCH corresponding to the STCH PDCP SDU equals PROSE_COMMUNICATION_DEST_ID(SL_ID):

7> increment STCH_PACKET_COUNTER(SL_ID) by 1;

7> set MATCH to one.

4> if MATCH equal zero:

5> increment STCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) by 1.

3> upon successful reception of a PSCCH PHY transport block for ProSe Direct Communication control packet:

4> set MATCH to zero;

4> for SL_ID = 0…(PROSE_COMMUNICATION_MONITOR_N-1):

5> if, in the received PSCCH PHY transport block, Group Destination ID for ProSe Direct Communication equals PROSE_COMMUNICATION_DEST_ID(SL_ID):

6> increment PSCCH_PACKET_COUNTER(SL_ID) by 1;

6> set MATCH to one.

4> if MATCH equal zero:

5> increment PSCCH_PACKET_COUNTER (PROSE_COMMUNICATION_MONITOR_N) by 1.

3> upon successful reception of a PSCCH PHY transport block for V2X Communication control packet:

4> increment PSCCH_PACKET_COUNTER(PROSE_COMMUNICATION_MONITOR_N) by 1.

3> upon successful reception of a PSSCH PHY transport block for ProSe Direct or V2X Communication data packet:

4> set MATCH to zero;

4> for SL_ID = 0…(PROSE_COMMUNICATION_MONITOR_N-1):

5> if, in the received PSSCH PHY transport block, Group Destination ID for ProSe Direct Communication or Destination Layer-2 ID for V2X Communication equals PROSE_COMMUNICATION_DEST_ID(SL_ID):

6> increment PSSCH_PACKET_COUNTER(SL_ID) by 1;

6> set MATCH to one.

4> if MATCH equal zero:

5> increment PSSCH_PACKET_COUNTER (PROSE_COMMUNICATION_MONITOR_N) by 1.

2> else if TEST_LOOP_MODE_E_TRIGGER is set to TRANSMIT;

3> create the STCH PDCP SDU with payload size and contents as specified below, see Figure 5.4.4c.1-1 and Table 5.4.4c.1-1 or Table 5.4.4c.1-2 and provide as input PDCP for transmission in every SC period as per TS 36.331 [25] or in the set of subframes according to subclause 5.14.1.1 of TS 36.321 [22] for V2X Communication.

NOTE: The same STCH PDCP SDU (1 packet) is transmitted (if permitted by test specific Layer 1 and Layer 2 configuration) by the UE in every SC period for ProSe Direct Communication or in the set of subframes for V2X Communication during the entire duration test loop mode E is closed.

2> else:

3> the UE behaviour is unspecified.

1> else:

2> the UE behaviour is unspecified.

The STCH PDCP SDU payload for ProSe Direct or V2X Communication packet when UE test loop mode E is active shall be as specified in Figure 5.4.4c.1-1 and Table 5.4.4c.1-1 or Table 5.4.4c.1-2. The UE shall also transmit the corresponding SCI control information on PSCCH accordingly in every PSCCH period for Prose Direct Communication or in the same subframe on which the STCH PDCP SDU is transmitted for V2X Sidelink Communication.

Figure 5.4.4c.1-1: ProSe Direct or V2X Communication Transmit operation in UE test loop mode E

Table 5.4.4c.1-1: STCH PDCP SDU payload contents for ProSe Direct operation in UE test loop mode E

Parameter	Value
Size (N)	40 bytes
Payload	00…00

Table 5.4.4c.1-2: STCH PDCP SDU payload contents for V2X Communication transmit operation in UE test loop mode E

Parameter	Value
Size (N)	300 bytes
Payload	00…00

5.4.4c.2 Release of RRC connection

When the RRC connection is released in E-UTRA mode then the UE shall:

1> if UE test loop mode E is active:

2> keep UE test loop mode E active

5.4.4c.3 Transition from RRC Idle/Connected to Any Cell Selection state

When the UE experiences radio link failure and transitions to RRC Any Cell Selection state in E-UTRA mode, then the UE shall:

1> if UE test loop mode E is active:

2> keep UE test loop mode E active

5.4.4c.4 V2X operation

In V2X test scenarios UE test loop mode E shall be kept active regardless of the radio environment situation and the UE state until de-activation has been explicitly requested.

5.4.4d UE test loop mode F operation

5.4.4d.1 Reception of MBMS packets

Upon receiving a MBMS packet on the SC-MTCH identified by SC_MTCH_ID when operating in E-UTRA idle or connected mode with UE test loop mode F active the UE shall:

1> if UE test loop mode F is active;

2> increment SCPTM_PACKET_COUNTER by 1:

1> else:

2> the UE behaviour is unspecified.

5.4.4d.2 Release of RRC connection

When the RRC connection is released in E-UTRA mode then the UE shall:

1> if UE test loop mode F is active:

2> keep UE test loop mode F active.

5.4.4e UE test loop mode G operation

5.4.4e.1 Reception of ESM DATA TRANSPORT message

Upon receiving an ESM DATA TRANSPORT message when operating in UE test loop G the UE shall:

if GH_NUMBER_UL_DATA_REPETITIONS is 0:

2> discard the received ESM DATA TRANSPORT message (no user data returned in uplink);

1> else if T_delay_modeGH timer is running:

2> discard any previously buffered user data;

2> buffer the content of the User data container of the received ESM DATA TRANSPORT message;

1> else:

2> if GH_BUFFER_CP_data is TRUE:

3> discard any previously buffered user data;

3> buffer the content of the User data container of the received ESM DATA TRANSPORT message;

3> Start T_delay_modeGH timer;

2> else:

3> if GH_NUMBER_UL_DATA_REPETITIONS is 1:

4> if GH_RLC_SDU_loopback is TRUE

5> submit the content of the User data container of each received ESM DATA TRANSPORT message in a RLC SDU to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

4> if GH_RLC_SDU_loopback is FALSE

5> submit the content of the User data container of each received ESM DATA TRANSPORT message to the EMM SAP for control plane data for transmission in uplink;

3> else if GH_NUMBER_UL_DATA_REPETITIONS is bigger than 1:

4> if GH_RLC_SDU_loopback is TRUE

5> submit the content of the User data container of each received ESM DATA TRANSPORT message in a RLC SDU repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

4> if GH_RLC_SDU_loopback is FALSE

5> submit the content of the User data container of each received ESM DATA TRANSPORT message repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the EMM SAP for control plane data for transmission in uplink;

5.4.4e.2 Expiry of T_delay_modeGH timer when UE test loop mode G is active

When timer T_delay_modeGH expires when UE is operating in UE Test Loop Mode G is active then the UE shall:

1> if GH_NUMBER_UL_DATA_REPETITIONS is 1:

2> if GH_RLC_SDU_loopback is TRUE

3> submit the content of the User data container of each received ESM DATA TRANSPORT message in a RLC SDU to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

2> if GH_RLC_SDU_loopback is FALSE

3> submit the content of the User data container of each received ESM DATA TRANSPORT message to the EMM SAP for control plane data for transmission in uplink;

1> else if GH_NUMBER_UL_DATA_REPETITIONS is bigger than 1:

2> if GH_RLC_SDU_loopback is TRUE

3> submit the content of the User data container of each received ESM DATA TRANSPORT message in a RLC SDU repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

2> if GH_RLC_SDU_loopback is FALSE

3> submit the content of the User data container of each received ESM DATA TRANSPORT message repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the EMM SAP for control plane user data for transmission in uplink;

1> set GH_BUFFER_CP_data to FALSE:

5.4.4f UE test loop mode H operation

5.4.4f.1 Reception of TPDU

Upon receiving a TPDU (SMS-DELIVER) when operating in UE test loop H the UE shall:

1> if GH_NUMBER_UL_DATA_REPETITIONS is 0:

2> discard the received TPDU (no user data returned in uplink);

1> else if T_delay_modeGH timer is running:

2> discard any previously buffered TP-User-Data;

2> buffer the TP-User-Data received in the TPDU via the Downlink NAS Transport message;

1> else

2> if GH_BUFFER_CP_data is TRUE:

3> discard any previously buffered TP-User-Data;

3> buffer the TP-User-Data received in the TPDU via the Downlink NAS Transport message;

3> Start T_delay_modeGH timer;

2> else:

3> if GH_NUMBER_UL_DATA_REPETITIONS is 1:

4> if GH_RLC_SDU_loopback is TRUE

5> submit the TP-User-Data for each received TPDU (SMS-DELIVER) in a RLC SDU to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

4> if GH_RLC_SDU_loopback is FALSE

5> submit the TP-User-Data for each received TPDU (SMS-DELIVER) to the SM-TL SAP for control plane data for transmission in uplink in TPDU (SMS-SUBMIT);

3> else if GH_NUMBER_UL_DATA_REPETITIONS is bigger than 1:

4> if GH_RLC_SDU_loopback is TRUE

5> submit the TP-User-Data for each received TPDU (SMS-DELIVER) in a RLC SDU repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

4> if GH_RLC_SDU_loopback is FALSE

5> submit the TP-User-Data for each received TPDU (SMS-DELIVER) repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the SM-TL SAP for control plane data for transmission in uplink in TPDU (SMS-SUBMIT);

5.4.4f.2 Expiry of T_delay_modeGH timer when UE test loop mode H is active

When timer T_delay_modeGH expires when UE is operating in UE Test Loop Mode H is active then the UE shall:

1> if GH_NUMBER_UL_DATA_REPETITIONS is 1:

2> if GH_RLC_SDU_loopback is TRUE

3> submit the TP-User-Data for each received TPDU (SMS-DELIVER) in a RLC SDU to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

2> if GH_RLC_SDU_loopback is FALSE

3> submit the TP-User-Data for each received TPDU (SMS-DELIVER) to the SM-TL SAP for control plane data for transmission in uplink in TPDU (SMS-SUBMIT);

1> else if GH_NUMBER_UL_DATA_REPETITIONS is bigger than 1:

2> if GH_RLC_SDU_loopback is TRUE

3> submit the TP-User-Data for each received TPDU (SMS-DELIVER) in a RLC SDU repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the RLC AM-SAP of SRB1bis for NB-IoT UE or to the RLC AM-SAP of SRB2 for E-UTRA UE for transmission in uplink;

2> if GH_RLC_SDU_loopback is FALSE

3> submit the TP-User-Data for each received TPDU (SMS-DELIVER) repeated GH_NUMBER_UL_DATA_REPETITIONS of times to the SM-TL SAP for control plane data for transmission in uplink in TPDU (SMS-SUBMIT);

1> set GH_BUFFER_CP_data to FALSE;

5.4.4g UE test loop mode I operation

5.4.4g.1 Reception of ESM DATA TRANSPORT message

Upon receiving an ESM DATA TRANSPORT message when operating in UE test loop I the UE shall:

1> submit the received IP PDU in the User data container of each received ESM DATA TRANSPORT without any modification of the IP header to the UL TFT handling SAP for transmission in uplink. See note.

Note 1: The UL TFT function in the UE is when UE is operated in Control Plane CIoT EPS optimization controlling uplink transmissions of IP PDUs based on UL TFT filters as configured by SS in the UL TFT IE sent as part of the EPS bearer establishment procedures. See figure 5.1-16.

Note 2: The IP PDUs shall contain a valid IPv4 or IPv6 Header in accordance with the PDN type (Ref. TS 24.301 [36]) accepted by the UE.

5.4.5 Open UE test loop

Figure 5.4.5-1: Open UE test loop procedure

Figure 5.4.5-2: Open UE test loop procedure by AT Command

5.4.5.1 General

The SS uses the procedure open UE test loop to deactivate the UE test loop function in the UE.

5.4.5.2 Initiation

The SS requests the UE to open all closed test loops by transmitting an OPEN UE TEST LOOP message or by transmitting an AT Command +CCUTLE.

5.4.5.3 Reception of OPEN UE TEST LOOP message or AT Command +CCUTLE by the UE

When UE receives the OPEN UE TEST LOOP message or AT Command +CCUTLE=<status=1> then the UE shall:

1> If no test loops are closed:

2> the UE behaviour is unspecified;

1> else if one or more test loops are closed:

2> open all test loops;

2> if TEST_LOOP_MODE_B_ACTIVE is TRUE

3> set TEST_LOOP_MODE_B_ACTIVE to FALSE

2> if TEST_LOOP_MODE_C_ACTIVE is TRUE

3> set TEST_LOOP_MODE_C_ACTIVE to FALSE

2> if TEST_LOOP_MODE_D_ACTIVE is TRUE

3> set TEST_LOOP_MODE_D_ACTIVE to FALSE

2> if TEST_LOOP_MODE_E_ACTIVE is TRUE

3> set TEST_LOOP_MODE_E_ACTIVE to FALSE

2> if TEST_LOOP_MODE_F_ACTIVE is TRUE

3> set TEST_LOOP_MODE_F_ACTIVE to FALSE

2> if TEST_LOOP_MODE_G_ACTIVE is TRUE

3> set TEST_LOOP_MODE_G_ACTIVE to FALSE

2> if TEST_LOOP_MODE_H_ACTIVE is TRUE

3> set TEST_LOOP_MODE_H_ACTIVE to FALSE

2> if TEST_LOOP_MODE_I_ACTIVE is TRUE

3> set TEST_LOOP_MODE_I_ACTIVE to FALSE

2> send OPEN UE TEST LOOP COMPLETE message;

NOTE: The UE test mode is still active so the UE continues behaving as described in 5.3.2.3