24.3.2 V2X Downlink Communication / UE in IDLE on an E-UTRAN cell / UE receives the V2X data via MBMS

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

24.3.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRAN RRC IDLE state on a cell broadcasting mcch-RepetitionPeriod-v1430, mcch-ModificationPeriod-v1430 and mch-SchedulingPeriod-v1430 }

ensure that {

when { UE is receiving an MBMS service }

then { UE shall start acquiring the MBSFNAreaConfiguration message that corresponds with the service that is being received, from the beginning of each modification period }

}

24.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.8.2.2 and 5.8.2.3.

[TS 36.331, clause 5.8.2.2]

A UE interested to receive MBMS services shall apply the MCCH information acquisition procedure upon entering the corresponding MBSFN area (e.g. upon power on, following UE mobility) and upon receiving a notification that the MCCH information has changed. A UE that is receiving an MBMS service shall apply the MCCH information acquisition procedure to acquire the MCCH that corresponds with the service that is being received, at the start of each modification period.

Unless explicitly stated otherwise in the procedural specification, the MCCH information acquisition procedure overwrites any stored MCCH information, i.e. delta configuration is not applicable for MCCH information and the UE discontinues using a field if it is absent in MCCH information unless explicitly specified otherwise.

[TS 36.331, clause 5.5.2.3]

An MBMS capable UE shall:

…

1> if the UE is receiving an MBMS service:

2> start acquiring the MBSFNAreaConfiguration message, that corresponds with the service that is being received, from the beginning of each modification period;

24.3.2.3 Test description

24.3.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

– System information combination 15 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells

– MBSFNAreaConfiguration as defined in Table 24.3.2.3.3-3 is transmitted on MCCH

UE:

– E-UTRAN UE supporting V2X communication Via Uu and MBMS services.

– The UE is equipped with below information in UE or in a USIM with V2X management data object in UE or in a USIM (as per TS 36.508 [18]).

Table 24.3.2.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

Service n°119 (V2X) supported

EFVST

As per TS 36.508 [18] clause 4.9.3.4

EFV2X_CONFIG

As defined in 36.508 [18], table 4.10.2

Preamble:

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

– The UE is made interested in receiving MBMS service in the PLMN of Cell 1 with MBMS Service ID 0.

24.3.2.3.2 Test procedure sequence

Table 24.3.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Wait for a period equal to the MCCH repetition period for the UE to receive MBSFNAreaConfiguration message

–

–

–

–

2

The generic procedures described in TS 36.508 subclause 4.5.3A.3 and 4.5.4.3 are performed on Cell 1 closing UE test loop Mode C

–

–

–

–

–

Exception: Step 3 is repeated 5 times

–

–

–

–

3

The SS transmits 2 MBMS Packets on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000001’ in the first MAC PDU of the MCH Scheduling Period.

Note: The frames matching the mcch-RepetitionPeriod-r9 shall be avoided to transmit MCCH and MTCH.

–

MBMS Packets.

–

–

4

The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST

–

–

5

UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE

–

–

6

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

<–

RRC: RRCConnectionRelease

–

–

7

SS transmits an updated system information [contents different from preamble]

–

–

–

–

8

SS transmits MBSFNAreaConfiguration message at the beginning of next modification period MPa.

<–

MBSFNAreaConfiguration

–

–

9

Wait until the start of the next modification period MPa for the duration of one repetition period for the UE to receive MBSFNAreaConfiguration message

–

–

–

–

–

Exception: Step 10 is repeated 10 times

–

–

–

–

10

The SS transmits 1 MBMS Packet on the MTCH in the next MCH Scheduling Period, with MCH Scheduling Information MAC Control Element with LCID=’00001’, Stop MTCH= ‘00000000000’ in the first MAC PDU of the MCH Scheduling Period.

Note: The frames matching the mcch-RepetitionPeriod-r9 shall be avoided to transmit MCCH and MTCH.

<–

MBMS Packets.

–

–

11

Steps 2 to 7 of the generic procedure described in TS 36.508 subclause 4.5.3A.3 are performed on Cell 1

–

–

–

–

12

The SS transmits an RRCConnectionReconfiguration message to configure data radio bearer(s) associated with the existing EPS bearer context

<–

RRC: RRCConnectionReconfiguration

–

–

13

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRC: RRCConnectionReconfigurationComplete

–

–

14

The SS transmits an UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST message.

<–

UE TEST LOOP MODE C MBMS PACKET COUNTER REQUEST

–

–

15

UE responds with UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE.

–>

UE TEST LOOP MODE C MBMS PACKET COUNTER RESPONSE

–

–

16

Check: Is the number of reported MBMS Packets received on the MTCH in step 15 greater than the value reported in step 5?

–

–

1

P

Note: The checking of UE received MBMS packets in steps 5 and 15 is to verify that MBMS reception is ongoing before and after the MBMS area configuration change in step 8.

24.3.2.3.3 Specific message contents

Table 24.3.2.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

mbsfn-SubframeConfiguration SEQUENCE {

radioframeAllocationPeriod

n1

radioframeAllocationOffset

0

FDD

0

TDD

subframeAllocation CHOICE{

oneFrame

‘110000’

FDD

‘010010’

TDD

}

}

}

Table 24.3.2.3.3-2: SystemInformationBlockType13 for Cell 1 (preamble)

Derivation Path: 36.508 table 4.4.3.3-13

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType13 ::= SEQUENCE {

mbsfn-AreaInfoList-r9 SEQUENCE (SIZE(1..maxMBSFN-Area)) OF SEQUENCE {

mcch-Config-r9 SEQUENCE {

mcch-RepetitionPeriod-r9

rf256

mcch-Offset-r9

0

FDD

0

TDD

mcch-ModificationPeriod-r9

rf1024

sf-AllocInfo-r9

‘100000’B

FDD

‘000010’B

TDD

signallingMCS-r9

n2

}

mcch-Config-r14 SEQUENCE {

mcch-RepetitionPeriod-v1430

rf4

mcch-ModificationPeriod-v1430

rf4

}

}

}

Table 24.3.2.3.3-3: MBSFNAreaConfiguration (preamble)

Derivation Path: 36.508 table 4.6.1-4A

Information Element

Value/remark

Comment

Condition

MBSFNAreaConfiguration-r9 ::= SEQUENCE {

commonSF-Alloc-r9 SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF SEQUENCE {

1 entry

MBSFN-SubframeConfig SEQUENCE {

radioframeAllocationPeriod

n1

radioframeAllocationOffset

0

FDD

0

TDD

subframeAllocation CHOICE {

oneFrame

‘100000’B

FDD

‘000010’B

TDD

}

}

}

commonSF-AllocPeriod-r9

rf4

pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {

1 entry

pmch-Config-r9 SEQUENCE {

sf-AllocEnd-r9

1

dataMCS-r9

0

mch-SchedulingPeriod-r9

rf1024

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

pmch-InfoListExt-r12 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {

1 entry

pmch-Config-r12 SEQUENCE {

sf-AllocEnd-r12

1

dataMCS-r12 CHOICE {

normal-r12

0

}

mch-SchedulingPeriod-r12

rf1024

mch-SchedulingPeriod-v1430

rf2

}

mbms-SessionInfoList-r12 SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF SEQUENCE {

1 entry

MBMS-SessionInfo-r9 SEQUENCE {

tmgi-r9 SEQUENCE {

plmn-Id-r9 CHOICE{

plmn-Index-r9

1

}

serviceId-r9

‘000000’O

OCTET STRING (SIZE (3))

}

sessionId-r9

Not present

logicalChannelIdentity-r9

1

}

}

}

}

}

}

Table 24.3.2.3.3-4: ACTIVATE TEST MODE (preamble)

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

Table 24.3.2.3.3-5: SystemInformationBlockType13 for Cell 1 (step 7, Table 24.3.2.3.2-1)

Derivation Path: 36.508 table 4.4.3.3-13

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType13 ::= SEQUENCE {

mbsfn-AreaInfoList-r9 SEQUENCE (SIZE(1..maxMBSFN-Area)) OF SEQUENCE {

mcch-Config-r9 SEQUENCE {

mcch-RepetitionPeriod-r9

rf256

mcch-Offset-r9

0

FDD

0

TDD

mcch-ModificationPeriod-r9

rf1024

sf-AllocInfo-r9

‘100000’B

FDD

‘000010’B

TDD

signallingMCS-r9

n2

}

mcch-Config-r14 SEQUENCE {

mcch-RepetitionPeriod-v1430

rf2

mcch-ModificationPeriod-v1430

rf2

}

}

}

Table 24.3.2.3.3-6: MBSFNAreaConfiguration (step 8, Table 24.3.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-4A

Information Element

Value/remark

Comment

Condition

MBSFNAreaConfiguration-r9 ::= SEQUENCE {

pmch-InfoList-r9 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {

pmch-Config-r9 SEQUENCE {

sf-AllocEnd-r9

0

dataMCS-r9

0

mch-SchedulingPeriod-r9

rf1024

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

pmch-InfoListExt-r12 SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF SEQUENCE {

pmch-Config-r12 SEQUENCE {

sf-AllocEnd-r12

0

dataMCS-r12 CHOICE {

normal-r12

1

}

mch-SchedulingPeriod-r12

rf1024

mch-SchedulingPeriod-v1430

rf1

}

mbms-SessionInfoList-r12 SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF SEQUENCE {

MBMS-SessionInfo-r9 SEQUENCE {

tmgi-r9 SEQUENCE {

plmn-Id-r9 CHOICE{

plmn-Index-r9

1

}

serviceId-r9

‘000000’O

OCTET STRING (SIZE (3))

}

sessionId-r9

Not present

logicalChannelIdentity-r9

1

}

}

}

}

}

}

Table 24.3.2.3.3-7: CLOSE UE TEST LOOP (step 2, Table 24.3.2.3.2-1)

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

Table 24.3.2.3.3-8: RRCConnectionReconfiguration (step 12, Table 24.3.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(2, 0)

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

dedicatedInfoNASList SEQUENCE (SIZE(1..maxDRB)) OF

Not present

}

}

}

}