21.3.9 Continued SC-PTM service reception after E-UTRAN release of unicast bearer

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.9.1 Test Purpose (TP)

(1)

with { UE in RRC Connected state on a SC-PTM cell and is prioritising MBMS service over unicast data }

ensure that {

when { UE receives the SystemInformationBlockType15 message broadcasted on the SC-PTM cell }

then { UE transmits an MBMSInterestIndication message including the mbms-Priority IE indicating that UE prioritises reception of MBMS frequencies above reception of any of the unicast bearers }

}

(2)

with { UE in E-UTRA RRC_Connected state with a unicast bearer configured AND is receiving SC-PTM service }

ensure that {

when { UE receives a RRCConnectionReconfiguration message to release the unicast bearer }

then { UE accepts the release of the unicast bearer and continues to receive MBMS service }

}

21.3.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.8.5.4. Unless otherwise stated these are Rel-13 requirements.

[TS 36.331 clause 5.8.5.4]

The UE shall set the contents of the MBMSInterestIndication message as follows:

1> if the set of MBMS frequencies of interest, determined in accordance with 5.8.5.3, is not empty:

2> include mbms-FreqList and set it to include the MBMS frequencies of interest sorted by decreasing order of interest, using the EARFCN corresponding with freqBandIndicator included in SystemInformationBlockType1 (for serving frequency), if applicable, and the EARFCN(s) as included in SystemInformationBlockType15 (for neighbouring frequencies);

NOTE 1: The EARFCN included in mbms-FreqList is merely used to indicate a physical frequency the UE is interested to receive i.e. the UE may not support the band corresponding to the included EARFCN (but it does support at least one of the bands indicated in system information for the concerned physical frequency).

2> include mbms-Priority if the UE prioritises reception of all indicated MBMS frequencies above reception of any of the unicast bearers;

2> if SystemInformationBlockType20 is broadcast by the PCell:

3> include mbms-Services and set it to indicate the set of MBMS services of interest determined in accordance with 5.8.5.3a;

NOTE 2: If the UE prioritises MBMS reception and unicast data cannot be supported because of congestion on the MBMS carrier(s), E-UTRAN may initiate release of unicast bearers. It is up to E-UTRAN implementation whether all bearers or only GBR bearers are released. E-UTRAN does not initiate re-establishment of the released unicast bearers upon alleviation of the congestion.

The UE shall submit the MBMSInterestIndication message to lower layers for transmission.

21.3.9.3 Test description

21.3.9.3.1 Pre-test conditions

System Simulator:

  • 1 E-UTRA Cell 1 is “Serving cell” as defined in TS 36.508 Table 6.2.2.1-1.
  • System information combination 25 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1.
  • SCPTMConfiguration message as defined in TS 36.508 [18] Table 4.6.1-18a is transmitted on Cell 1.

UE:

– The UE is supporting SC-PTM services.

Preamble:

– UE is in state Loopback Activated (State 4) with UE TEST LOOP MODE F on Cell 1 according to [18].

– The UE has one dedicated EPS bearer (DRB2) established.

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

– The UE is configured to prioritise reception of MBMS frequencies above reception of any unicast bearers.

– The UE is made aware that the SC-PTM service is active.

21.3.9.3.2 Test procedure sequence

Table 21.3.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging message including a systemInfoModification for cell1.

<–

Paging

–

–

2

From the beginning of the next modification period the SS transmits SystemInformationBlockType15 according to system information combination 27 as defined in TS 36.508[18] clause 4.4.3.1 including mbms-SAI-IntraFreq-r11 list indicating MBMS SAI=1.

<–

SystemInformationBlockType15

–

–

3

UE transmits MBMSInterestIndication message condition SC-PTM. Check: Does UE transmit an MBMSInterestIndication message including the mbms-Priority IE set to True?

–>

MBMSInterestIndication

1

P

4

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

–

–

–

–

–

Exception; Step 5 is repeated 5 times

–

–

–

–

5

The SS transmits 2 MBMS Packets on the SC-MTCH

<–

MBMS Packets

–

–

6

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

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

–

–

7

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

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

–

–

8

The SS transmits an RRCConnectionReconfiguration message to release the unicast bearer (DRB2 that established during preamble) due to congestion on the MBMS carrier(s)

<–

RRCConnectionReconfiguration

–

–

9

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the release.

–>

RRCConnectionReconfigurationComplete

–

–

–

Exception; Step 10 is repeated 5 times

–

–

–

–

10

The SS transmits 2 MBMS Packets on the SC-MTCH

<–

MBMS Packets

–

–

11

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

<–

UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST

–

–

12

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

–>

UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE

–

–

13

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

–

–

2

P
21.3.9.3.3 Specific message contents

Table 21.3.9.3.3-1: MBMSInterestIndication (step 1, Table 21.3.9.3.2-2)

Derivation Path: 36.508, Table 4.6.1-4AC condition SC-PTM

Information Element

Value/remark

Comment

Condition

criticalExtensions CHOICE {

c1 CHOICE{

interestIndication-r11 OF SEQUENCE {

mbms-FreqList-r11[1] SEQUENCE (SIZE (1..maxFreqMBMS-r11)) OF { INTEGER (0..maxEARFCN2) }

EARFCN of Cell 1

1 entry

mbms-Priority-r11

true

ENUMERATED {true}

}

}

}

Table 21.3.9.3.3-2: RRCConnectionReconfiguration (step 8, Table 21.3.9.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition DRB-REL