21.3.2 Cell reselection to inter-frequency cell to start SC-PTM service reception

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

21.3.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state on a cell broadcasting SIB15 and interested to receive a SC-PTM service }

ensure that {

when { SIB15 indicates that the SC-PTM service is available on a frequency of an inter-frequency neighbour cell }

then { UE performs cell reselection to the inter-frequency neighbour cell even if the serving cell is better and starts SC-PTM reception }

}

21.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.1 and TS 36.331, clause 5.2.2.4. Unless otherwise stated these are Rel-13 requirements.

[TS 36.304, clause 5.2.4.1]

Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCConnectionRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an E-UTRAN frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCConnectionReject unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values). While the UE is camped on a suitable CSG cell, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than any of the network configured values), irrespective of any other priority value allocated to this frequency if that cell can be accessed in normal coverage. If the UE capable of sidelink communication is configured to perform sidelink communication and can only perform the sidelink communication while camping on a frequency, the UE may consider that frequency to be the highest priority.

NOTE: The prioritization among the frequencies which UE considers to be the highest priority frequency is left to UE implementation.

If the UE is capable either of MBMS Service Continuity or of SC-PTM reception and is receiving or interested to receive an MBMS service and can only receive this MBMS service while camping on a frequency on which it is provided, the UE may consider that frequency to be the highest priority during the MBMS session [2] as long as the two following conditions are fulfilled:

1) Either:

– the UE is capable of MBMS service continuity and the reselected cell is broadcasting SIB13; or

– the UE is capable of SC-PTM reception and the reselected cell is broadcasting SIB20;

2) Either:

– SIB15 of the serving cell indicates for that frequency one or more MBMS SAIs included in the MBMS User Service Description (USD) [22] of this service; or

– SIB15 is not broadcast in the serving cell and that frequency is included in the USD of this service.

If the UE is capable either of MBMS Service Continuity or of SC-PTM reception and is receiving or interested to receive an MBMS service provided on a downlink only MBMS frequency, the UE may consider cell reselection candidate frequencies at which it can not receive the MBMS service to be of the lowest priority during the MBMS session [2], as long as the above mentioned condition 1) is fulfilled for the cell on the MBMS frequency which the UE monitors and as long as the above mentioned condition 2) is fulfilled for the serving cell.

NOTE: An example scenario in which the previous down-prioritisation may be needed concerns the case the MBMS frequency is a downlink only carrier on which camping is not possible, while the UE can only receive this MBMS frequency when camping on a subset of cell reselection candidate frequencies.

…

[TS 36.331, clause 5.2.2.4]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1;

1> if the procedure is triggered by a system information change notification:

2> if the UE uses an idle DRX cycle longer than the modification period:

3> start acquiring the required system information, as defined in 5.2.2.3, from the next eDRX acquisition period boundary;

2> else

3> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification period following the one in which the change notification was received;

NOTE 1: The UE continues using the previously received system information until the new system information has been acquired.

1> if the UE is in RRC_IDLE and enters a cell for which the UE does not have stored a valid version of the system information required in RRC_IDLE, as defined in 5.2.2.3:

2> acquire, using the system information acquisition procedure as defined in 5.2.3, the system information required in RRC_IDLE, as defined in 5.2.2.3;

…

1> if the UE is interested to receive MBMS services:

2> if the UE is capable of MBMS reception as specified in 5.8:

3> if schedulingInfoList indicates that SystemInformationBlockType13 is present and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType13;

2> if the UE is capable of SC-PTM reception as specified in 5.8a:

3> if schedulingInfoList indicates that SystemInformationBlockType20 is present and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType20;

2> if the UE is capable of MBMS Service Continuity:

3> if schedulingInfoList indicates that SystemInformationBlockType15 is present and the UE does not have stored a valid version of this system information block:

4> acquire SystemInformationBlockType15;

…

The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated with a received or a UE originated RRC message, e.g. an ongoing random access procedure.

NOTE 6: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer present, the UE should stop trying to acquire the particular SIB.

21.3.2.3 Test description

21.3.2.3.1 Pre-test conditions

System Simulator:

  • 2 E-UTRA cells with the same PLMN. Cell 1 and Cell 23 are inter-frequency cells. Cell 1 is "Serving cell" and Cell 23 is "Non-suitable cell" as defined in TS 36.508 Table 6.2.2.1-1.

– System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA Cell 1.

– System information combination 26 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA Cell 23.

– SCPTMConfiguration as defined in TS 36.508[18] table 4.6.1-18a is transmitted on SC-MCCH on Cell 23.

UE:

– E-UTRAN UE supporting SC-PTM services.

Preamble:

– UE is in Registered, Idle mode, Test Mode Activated (State 2A) according to [18] in Cell 1 (serving cell).

– The UE is made interested in receiving SC-PTM service with MBMS Service ID=1 as broadcasted in SCPTMConfiguration .

21.3.2.3.2 Test procedure sequence

Table 21.3.2.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while row marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 21.3.2.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 23

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are assigned to satisfy R Cell 23 < RCell 1.

Table 21.3.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging message including a systemInfoModification for Cell1 and Cell 23.

<–

Paging

–

–

2

From the beginning of the next modification period the SS starts broadcast of SystemInformationBlockType15 including mbms-SAI-InterFreqList-r11 indicating MBMS SAI=1 according to system information combination 18 on Cell 1 and according to system information combination 28 on Cell 23.

<–

SystemInformationBlockType15

–

–

3

Void

–

–

–

–

–

EXCEPTION: the behaviour in table 21.3.2.3.2-3 runs in parallel with steps 4 and 5 below.

–

–

–

–

4

The UE executes the generic test procedure described in TS 36.508 subclause 6.4.2.7 and UE should camp on E-UTRA Cell 23.

NOTE: The UE performs a TAU procedure and the RRC connection is released.

–

–

–

–

5

Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration message on Cell 23.

–

–

–

–

–

EXCEPTION: In parallel to the events described in step 6, the steps described in Table 21.3.2.3.2-3 may take place, depending on the UE implementation.

–

–

–

–

6

The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 23 activating UE test loop Mode F.

–

–

–

–

7

The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.

<–

RRC: RRCConnectionRelease

–

–

–

Exception; Step 8 is repeated 5 times

–

–

–

–

8

The SS transmits 2 MBMS Packets on the SC-MTCH.

<–

MBMS Packets

–

–

–

EXCEPTION: In parallel to the events described in steps 9, 10 and 11, the steps described in Table 21.3.2.3.2-3 may take place, depending on the UE implementation.

–

–

–

–

9

Generic test procedure Generic Radio Bearer Establishment as described in TS 36.508 subclause 4.5.3 is executed.

–

–

–

–

10

The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message to set UE to Mode F.

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

–

–

11

UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

–

–

12

Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 11 greater than zero?

(Note: This verifies that UE has selected Cell 23 providing the SC-PTM service and starts SC-PTM reception)

–

–

1

P

Table 21.3.2.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

UE transmits a MBMSInterestIndication message.

–>

MBMSInterestIndication

–

–

21.3.2.3.3 Specific message contents

Table 21.3.2.3.3-1: SystemInformationBlockType15 for Cell 1 (step 2 and all later steps)

Derivation Path: 36.508 table 4.4.3.3-14, condition SCPTM_interFreq.

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType15 ::= SEQUENCE {

mbms-SAI-IntraFreq-r11 SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

Not present

mbms-SAI-InterFreqList-r11[1] SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE {

1 entry

dl-CarrierFreq-r11

Downlink EARFCN for Cell 23, see table 6.3.1.2-1.

mbms-SAI-List-r11[1] SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

1

1 entry

INTEGER (0..65535)

}

}

Table 21.3.2.3.3-2: SystemInformationBlockType15 for Cell 23 (step 2 and all later steps)

Derivation Path: 36.508 table 4.4.3.3-14, condition SCPTM_interFreq.

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType15 ::= SEQUENCE {

mbms-SAI-IntraFreq-r11 SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

Not present

mbms-SAI-InterFreqList-r11[1] SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE {

1 entry

dl-CarrierFreq-r11

Downlink EARFCN for Cell 1, see table 6.3.1.2-1.

mbms-SAI-List-r11[1] SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) }

1

1 entry

INTEGER (0..65535)

}

}

Table 21.3.2.3.3-3: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE F.

Table 21.3.2.3.3-4: CLOSE UE TEST LOOP (step 6)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE F