8.5.7 MBSFN Specific Procedures (FDD/TDD)
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
8.5.7.1 Cell Update: cell reselection in CELL_PCH (unicast carrier) during ongoing MBMS session in MBSFN mode
8.5.7.1.1 Definition
This test is applicable for UEs that support MBMS broadcast services in MBSFN mode and which support either both transmit and receive functions or MBSFN receive only function.
8.5.7.1.2 Conformance requirement
The UE reception of MBMS services provided in MBSFN mode shall not affect the UE behaviour on the unicast carrier. Especially the UE mobility on the unicast carrier is not affected by the reception of MBMS services provided on a cell operating in MBSFN mode and can imply that the reception of the MBMS service on the cell operating in MBSFN mode is impossible due to the limited support of combination of frequency bands for MBMS SFN reception and unicast reception.
…
A UE that is capable of receiving MBMS services on cells operating in MBSFN mode as specified in subclause 8.1.1.6.3 is operating in idle mode and acts on RRC messages and system information received from this cell operating in MBSFN mode independently from messages received from cells not operating in MBSFN mode. This implies that procedures executed based on messages and system information received from a cell operating in MBSFN mode shall not interact with messages and system information received from a cell not operating in MBSFN mode unless explicitly specified otherwise.
NOTE 1: This implies that the UE is operating an independent stack for the reception of MBMS services on cells operating in MBSFN mode as specified in subclause 8.1.1.6.3.
NOTE 2: For 1.28 Mcps TDD, if the cell is operating in MBSFN mode, system information and MCCH messages are transmitted on the MBSFN Special Timeslot [30].
…
A cell provides MBMS service in MBSFN mode if it is indicated so in system information, see subclause 8.1.1.6.3. A UE that supports MBSFN operation may receive MBMS services via a cell operating in MBSFN mode. For FDD, 3.84 Mcps TDDIMB and 3.84/7.68 Mcps TDD in order to receive an MBMS service via a MBSFN cluster the UE shall select the MBSFN cluster as specified in [4] in addition to selecting a cell for normal camping as specified in [4]. For 1.28 Mcps TDD in order to receive an MBMS service via an MBSFN cluster the UE shall at the first step camp on a unicast cell and get the frequency and "cell parameter ID" from the system information, and then get synchronized to the MBSFN cluster operating with that frequency and "cell parameter ID". For 3.84/7.68 Mcps TDD a cell shall be considered to be operating in MBSFN mode when individual scrambling codes are assigned to all timeslots (via the IE "TDD MBSFN Information").
…
Reference
3GPP TS 25.346 clauses 7.1A.
3GPP TS 25.331 clauses 7.2.1, 8.5.43.
8.5.7.1.3 Test purpose
To verify that the UE will perform a Cell Update on the unicast carrier while receiving an ongoing MBMS service via a p-t-m radio bearer on the MBSFN cluster.
8.5.7.1.4 Method of test
Initial condition
System Simulator:
– MBSFN carrier: 1 cell, Cell 31 (PLMN1). In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing session) according to subclause 11.2 of TS 34.108.
– Unicast carrier : 2 cells, Cell 1 and Cell 2 with default parameters.
User Equipment:
– On the unicast carrier the UE is in CELL_PCH (state 6-12) in Cell 1 as specified in clause 7.4 of TS 34.108.
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which a session will start on MBSFN Cell 31 (see TS 34.108 clause 11.2.4) during the test.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test procedure
The SS shall apply the downlink power settings as shown below:
Step 1-13:
Parameter |
Unit |
Cell 1 |
Cell 2 |
Cell 31 |
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
Ch. 2 |
|
P-CCPCH RSCP |
dBm |
-60 |
-69 |
-60 |
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-69 |
-60 |
P-CPICH (IMB) |
dBm/3.84MHz |
-60 |
||
T-CPICH (IMB) |
dBm/3.84MHz |
-50.5 |
Step 14-25:
Parameter |
Unit |
Cell 1 |
Cell 2 |
Cell 31 |
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
Ch. 2 |
|
P-CCPCH RSCP |
dBm |
-69 |
-60 |
-60 |
CPICH Ec (FDD) |
dBm/3.84MHz |
-69 |
-60 |
-60 |
P-CPICH (IMB) |
dBm/3.84MHz |
-60 |
||
T-CPICH (IMB) |
dBm/3.84MHz |
-50.5 |
a) The UE is camping on Cell 1 and Cell 31. For 3.84 Mcps TDD IMB, the UE is camping on the FDD unicast carrier cell 1 and IMB cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
d) The SS notifies on MCCH about the start of an MBMS session for one modification period. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (one PTM session starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
e) MCCH messages are then transmitted by the SS on Cell 31 using MBMS configuration C2 (one PTM session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
f) The UE establishes the p-t-m radio bearer for the activated service according to the specified service activation time (i.e. the first SFN of the modification period following the notification (step d). The UE closes the test loop and starts counting successfully received RLC PDUs on the MTCH. The UE will send CLOSE UE TEST LOOP COMPLETE.
g) The SS broadcasts 10 RLC SDUs on the MTCH configured on the MBMS p-t-m radio bearer for the activated service. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD) or a 124 kbps RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD) or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB).
h) The SS shall then send UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST. The UE shall respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is > 0. The SS shall store the counter value.
i) The SS adjusts the power settings for Cell 1 and Cell 2. When the UE detects the presence of cell 2, it moves to CELL_FACH state and transmits a CELL UPDATE message on the uplink CCCH. The value "cell reselection" shall be set in IE "Cell update cause" in CELL UPDATE message.
j) Upon reception of the CELL_UPDATE message, the SS replies with a CELL UPDATE CONFIRM message with the IE "RRC State Indicator" set to "CELL_PCH". After receiving this message, the UE returns to CELL_PCH state without transmitting any uplink message.
k) The SS calls for generic procedure C.4 to check that the UE is in CELL_PCH state.
l) The SS broadcasts 10 RLC SDUs on the MTCH configured on the MBSFN MBMS p-t-m radio bearer for the activated service.
m) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE corresponds to > 0 received RLC SDUs.
NOTE: If the UE fails the test because of a failure to reselect to the right unicarrier cell (Cell 2), then the operator may re-run the test.
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
U |
ACTIVATE RB TEST MODE |
||
2 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
3 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated on Cell 31 for the selected local service on MTCH. |
|
4 |
|
M |
MBMS MCCH Message Configuration C4 |
Includes the national service activated at UE in the modified services list for one modification period. |
|
5 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. One ongoing service corresponding to that activated at the UE 129.6(FDD) or 124(TDD) kbps PS RAB, 124.4 kbps (IMB) |
|
6 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE shall establish the indicated p-t-m radio bearer and close the test loop. |
|
7 |
SS |
M |
After delaying for a period equal to the MCCH modification period, the SS transmits 10 RLC SDUs on the MTCH. |
||
8 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
9 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. SS stores value. |
|
10 |
U |
The SS transmits 10 RLC SDUs on the MTCH starting at the indicated activation time. |
|||
11 |
|
U |
CELL UPDATE |
The UE moves to CELL_FACH state and transmits this message with the IE "Cell update cause" set to "cell reselection" |
|
12 |
|
U |
CELL UPDATE CONFIRM |
IE "RRC State Indicator" is set to "CELL_PCH". |
|
13 |
UE |
U |
The UE is in CELL_PCH state. |
||
14 |
|
U |
CALL C.4 |
If the test result of C.4 indicates that UE is in CELL_PCH state, the test passes, otherwise it fails. |
|
15 |
SS |
M |
The SS transmits 10 RLC SDUs on the MTCH. |
||
16 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
17 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. |
|
18 |
|
U |
OPEN UE TEST LOOP |
||
19 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
20 |
|
U |
DEACTIVATE RB TEST MODE |
||
21 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Specific message contents
With the following exceptions, all messages have the same content as defined in TS 34.108 clause 9.1.3 for the MBSFN carriers and in TS 34.108 clause 9.1.1 or 9.1.2 for the unicast carrier:
CELL UPDATE (Step 11)
Information Element |
Value/remark |
U-RNTI |
|
– SRNC Identity |
Check to see if set to ‘0000 0000 0001’ |
– S-RNTI |
Check to see if set to ‘0000 0000 0000 0000 0001’ |
Cell Update Cause |
Check to see if set to ‘Cell Re-selection’ |
CELL UPDATE CONFIRM (Step 162)
Information Element |
Value/remark |
RRC State Indicator |
CELL_PCH |
UTRAN DRX cycle length coefficient |
3 |
8.5.7.1.5 Test requirements
1) After step 9, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number > 0 for Cell 31 MTCH.
3) After step 11, the UE shall reselect to Cell 2 and transmit a CELL UPDATE message, containing the IE "Cell update cause" set to "cell reselection".
4) After step 13, the UE shall enter CELL_PCH state.
5) After step 17, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a number > 0 for Cell 31 MTCH.
8.5.7.2 Re-acquire MCCH – modified MBSFN inter frequency neighbour list / All MBSFN services notified
8.5.7.2.1 Definition
This test is applicable for UEs that support MBMS broadcast services in MBSFN mode and which support either both transmit and receive functions or MBSFN receive only function.
8.5.7.2.2 Conformance requirement
Upon receiving the MBMS GENERAL INFORMATION message, the UE should store all relevant IEs included in this message. The UE shall also:
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following.
…
For FDD 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD if the IE "MBSFN inter frequency neighbour list" is included and the UE does not receive a service from this MBSFN cluster, the UE shall:
1> consider that MBMS services transmitted in MBSFN mode are available on these frequencies;
…
1> if at least one frequency is listed for which "MBSFN services not notified" is indicated in the IE "MBSFN inter frequency neighbour list":
2> if the IE "All MBSFN services notified" is included for one frequency as defined in [21] for FDD and [22] for TDD on which the UE supports reception in MBSFN mode:
3> attempt to receive notifications on one of the frequencies for which the IE "All MBSFN services notified" is included according to subclause 8.7.3.
…
Upon receiving the MBMS MODIFIED SERVICES INFORMATION message, the UE shall act as follows for each of the services included in this messages provided that the service is included in variable MBMS_ACTIVATED_SERVICES and upper layers indicate that the session has not yet been received correctly (referred to as ‘applicable services’):
…
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following
…
If the UE receives the IE " MBMS re- acquire MCCH", the UE shall:
1> perform the MCCH acquisition procedure as specified in subclause 8.7.2.
Reference
3GPP TS 25.331 clauses 8.7.2.5, 8.6.9.9ad, 8.7.3.4, 8.6.9.6a.
8.5.7.2.3 Test purpose
1. To verify that the UE correctly re-acquires the MCCH information when the UE receives the IE MBMS re- acquire MCCH in a received MBMS MODIFIED SERVICES INFORMATION message.
2. To verify that the UE acts upon the modified IE MBSFN inter frequency neighbour list received in the re-acquired MBMS GENERAL INFORMATION message when a service not received on the current MBSFN cluster is present in the variable MBMS_ACTIVATED_SERVICES.
3. To verify that the UE attempts to receive notifications, for the service not received on the current MBSFN cluster, on one of the frequencies for which the IE "All MBSFN services notified" is included.
8.5.7.2.4 Method of test
Initial condition
System Simulator:
– MBSFN carrier: 3 cells, Cell 31, Cell 36 and Cell 38 (all PLMN1). Cell 36 and Cell 38 are powered off. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing session) according to subclause 11.2 of TS 34.108.
Unicast carrier: 1 cell, Cell 1 (PLMN1) default configuration.
User Equipment:
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains, as specified in clause 7.2.2 of TS 34.108.
– The UE is in MBSFN Idle mode with no activated service as specified in clause 7.6.3 of TS 34.108.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test procedure
The SS shall apply the downlink power settings as shown below:
Step 1-7:
Parameter |
Unit |
Cell 1 |
Cell 31 |
Cell 33 |
Cell 36 |
UTRA RF Channel Number |
Ch. 1 |
Ch. 2 |
Ch. 3 |
Ch. 4 |
|
P-CCPCH RSCP |
dBm |
-60 |
-60 |
OFF |
OFF |
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-60 |
OFF |
OFF |
P-CPICH (IMB) |
dBm/3.84MHz |
-60 |
OFF |
OFF |
|
T-CPICH (IMB) |
dBm/3.84MHz |
-50.5 |
OFF |
OFF |
Step 8-33:
Parameter |
Unit |
Cell 1 |
Cell 31 |
Cell 33 |
Cell 36 |
UTRA RF Channel Number |
Ch. 1 |
Ch. 2 |
Ch. 3 |
Ch. 4 |
|
P-CCPCH RSCP |
dBm |
-60 |
-60 |
-60 |
-70 |
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-60 |
-60 |
-70 |
P-CPICH (IMB) |
dBm/3.84MHz |
-60 |
-60 |
-70 |
|
T-CPICH (IMB) |
dBm/3.84MHz |
-50.5 |
-50.5 |
-60.5 |
a) The UE is camping on Cell 1 and Cell 31. For 3.84 Mcps TDD IMB, the UE is camping on the FDD unicast carrier cell 1 and IMB cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108. Note: The IE "MBSFN inter frequency neighbour list" is not present in MBMS GENERAL INFORMATION.
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on MTCH. The Short Transmission identity is set to value "0" corresponding to National Service 5 (see TS 34.108 clause 11.2.4) on either Cell 33 or Cell 36.
d) For Cell 31 in the IE "MBSFN inter frequency neighbour list" of the MBMS GENERAL INFORMATION message the SS adds (i) the frequency for Cell 36 with the IE "MBSFN services notification" set to "MBSFN services not notified" and with the option "All MBSFN services notified" included, and (ii) the frequency for Cell 33 with the IE "MBSFN services notification" set to "MBSFN services not notified" without the option "All MBSFN services notified". The SS sends MBMS MODIFIED SERVICES INFORMATION with IE "MBMS re- acquire MCCH" set to "True".
e) The UE shall re-perform the MCCH acquisition procedure on Cell 31.
f) The SS powers on Cell 33 and Cell 36. MCCH messages are transmitted by the SS on Cell 36 using MBMS configuration C2 (one PTM session ongoing – National Service 5) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108. MCCH messages are transmitted by the SS on Cell 33 using MBMS configuration C2 (one PTM session ongoing – National Service 5) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
g) National Service 5 is activated at the UE.
h) The UE shall retune to the frequency for Cell 36, perform MBSFN cluster reselection and shall perform the MCCH acquisition procedure on Cell 36.
i) The UE immediately establishes the p-t-m radio bearer for National Service 5. The UE closes the test loop and starts counting successfully received RLC PDUs on the MTCH. The UE will send CLOSE UE TEST LOOP COMPLETE.
j) On Cell 33 the SS broadcasts 10 RLC SDUs on the MTCH configured on the MBMS p-t-m radio bearer for National Service 5. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD) or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or a 124 kbps RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD).
k) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is = 0.
l) On Cell 36 the SS broadcasts 10 RLC SDUs on the MTCH configured on the MBMS p-t-m radio bearer for National Service 5. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD), or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or a 124 kbps RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD).
m) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is > 0.
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
M |
MBMS MCCH Message Configuration C1 |
No sessions ongoing. IE "MBSFN inter frequency neighbour list" not present in MBMS GENERAL INFORMATION |
|
2 |
|
U |
ACTIVATE RB TEST MODE |
||
3 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
4 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated with Short Transmission Identity = "0". |
|
5 |
|
M |
MBMS MCCH Message Configuration C1 |
Cell 31: IE "MBMS re-acquire MCCH" set to "True" in MBMS MODIFIED SERVICES INFO. Frequencies for Cell 33 and Cell 36 have been added to IE "MBSFN inter frequency neighbour list". |
|
6 |
UE |
M |
UE re-acquires MCCH on Cell 31. |
||
7 |
SS |
The SS powers on Cell 33 and Cell 36. |
|||
8 |
|
M |
MBMS MCCH Message Configuration C2 |
Cell 33: One PTM session ongoing (National Service 5). 129.6(FDD) or 124(TDD)kbps PS RAB, 124.4 kbps (IMB) |
|
9 |
|
M |
MBMS MCCH Message Configuration C2 |
Cell 36: One PTM session ongoing (National Service 5). 129.6(FDD) or 124(TDD)kbps PS RAB, 124.4 kbps (IMB) |
|
10 |
UE |
M |
National Service 5 is activated at the UE. |
||
11 |
UE |
M |
UE retunes to frequency for Cell 36 and acquires the MCCH. |
||
12 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE shall establish the indicated p-t-m radio bearer for National Service 5 and close the test loop. |
|
13 |
SS |
M |
The SS transmits 10 RLC SDUs on the MTCH for Cell 33. |
||
14 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
15 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is equal to zero. |
|
16 |
SS |
M |
The SS transmits 10 RLC SDUs on the MTCH for Cell 36. |
||
17 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
18 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. |
|
19 |
|
U |
OPEN UE TEST LOOP |
||
20 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
21 |
|
U |
DEACTIVATE RB TEST MODE |
||
22 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Specific message contents
With the following exceptions, all messages have the same content as defined in TS 34.108 clause 9.1.3 for the MBSFN carriers and in TS 34.108 clause 9.1.1 or 9.1.2 for the unicast carrier:
MBMS MODIFIED SERVICES INFORMATION (Step 1, Step 8, and Step 9)
Information Element |
Value/remark |
Version |
---|---|---|
Modified service list |
Not Present |
Rel-6 |
MBMS re- acquire MCCH |
Not Present |
Rel-6 |
MBMS dynamic persistence level |
Not Present |
Rel-6 |
End of modified MCCH information |
Not Present |
Rel-6 |
MBMS number of neighbour cells |
0 |
Rel-6 |
MBMS all unmodified p-t-m services |
Not Present |
Rel-6 |
MBMS p-t-m activation time |
Not Present |
Rel-6 |
MIB Value tag |
Not Present |
Rel-7 |
MBMS UNMODIFIED SERVICES INFORMATION (Dedicated National carrier) (Step 1 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
Not Present |
Rel-6 |
MBMS GENERAL INFORMATION (Step 1)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Not Present |
Rel-7 |
MBMS MODIFIED SERVICES INFORMATION (Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Modified service list |
Not Present |
Rel-6 |
MBMS re- acquire MCCH |
True |
Rel-6 |
MBMS dynamic persistence level |
Not Present |
Rel-6 |
End of modified MCCH information |
Not Present |
Rel-6 |
MBMS number of neighbour cells |
0 |
Rel-6 |
MBMS all unmodified p-t-m services |
Not Present |
Rel-6 |
MBMS p-t-m activation time |
Not Present |
Rel-6 |
MIB Value tag |
Not Present |
Rel-7 |
MBMS GENERAL INFORMATION (Step 5)(FDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 5)(TDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– All MBSFN services notified |
TRUE |
MBMS GENERAL INFORMATION (Step 5)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– IMB indication |
TRUE |
Rel-8 |
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– IMB indication |
TRUE |
Rel-8 |
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– All MBSFN services notified |
TRUE |
MBMS UNMODIFIED SERVICES INFORMATION (Step 8)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
4 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
’01’ |
|
– MBMS required UE action |
Acquire PTM RB info |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 1) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 2) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
MBMS UNMODIFIED SERVICES INFORMATION (Step 8)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
2 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
’01’ |
|
– MBMS required UE action |
Acquire PTM RB info |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
MBMS GENERAL INFORMATION (Step 8)(FDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 8)(TDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f1" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 8)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– IMB indication |
TRUE |
Rel-8 |
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– IMB indication |
TRUE |
Rel-8 |
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS UNMODIFIED SERVICES INFORMATION (Step 9)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
8 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 1) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 2) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 3) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 4) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
’01’ |
|
– MBMS required UE action |
Acquire PTM RB info |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
2 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
2 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 1) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
2 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 2) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
2 |
Rel-7 |
MBMS UNMODIFIED SERVICES INFORMATION (Step 9) (IMB)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
6 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 1) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 2) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 3) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 4) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
1 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
’01’ |
|
– MBMS required UE action |
Acquire PTM RB info |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
2 |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
2 |
Rel-7 |
MBMS GENERAL INFORMATION (Step 9)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f1" |
|
– CHOICE MBSFN services notification |
MBSFN services notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 9)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– IMB indication |
TRUE |
Rel-8 |
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– IMB indication |
TRUE |
Rel-8 |
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
8.5.7.2.5 Test requirements
1) After step 15, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report that zero RLC SDUs have been received.
2) After step 18, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report that > 0 RLC SDUs have been received.
8.5.7.3 Re-acquire MCCH – modified MBSFN inter frequency neighbour list / MBSFN services not notified
8.5.7.3.1 Definition
This test is applicable for UEs that support MBMS broadcast services in MBSFN mode and which support either both transmit and receive functions or MBSFN receive only function.
8.5.7.3.2 Conformance requirement
Upon receiving the MBMS GENERAL INFORMATION message, the UE should store all relevant IEs included in this message. The UE shall also:
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following.
…
For FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD if the IE "MBSFN inter frequency neighbour list" is included and the UE does not receive a service from this MBSFN cluster, the UE shall:
1> consider that MBMS services transmitted in MBSFN mode are available on these frequencies;
…
1> if at least one frequency is listed for which "MBSFN services not notified" is indicated in the IE "MBSFN inter frequency neighbour list":
2> if the IE "All MBSFN services notified" is included for one frequency as defined in [21] for FDD and [22] for TDD on which the UE supports reception in MBSFN mode:
…
2> else:
3> attempt to receive notifications on all frequencies for which the IE “MBSFN services not notified” is indicated as specified in subclause 8.7.3 on that band.
…
Upon receiving the MBMS MODIFIED SERVICES INFORMATION message, the UE shall act as follows for each of the services included in this messages provided that the service is included in variable MBMS_ACTIVATED_SERVICES and upper layers indicate that the session has not yet been received correctly (referred to as ‘applicable services’):
…
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following
…
If the UE receives the IE " MBMS re- acquire MCCH", the UE shall:
1> perform the MCCH acquisition procedure as specified in subclause 8.7.2.
Reference
3GPP TS 25.331 clauses 8.7.2.3, 8.7.2.5, 8.6.9.9ad, 8.7.3.4, 8.6.9.6a.
8.5.7.3.3 Test purpose
1. To verify that the UE correctly re-acquires the MCCH information when the UE receives the IE MBMS re- acquire MCCH in a received MBMS MODIFIED SERVICES INFORMATION message.
2. To verify that the UE acts upon the modified IE MBSFN inter frequency neighbour list received in the re-acquired MBMS GENERAL INFORMATION message when a service not received on the current MBSFN cluster is present in the variable MBMS_ACTIVATED_SERVICES.
3. To verify that in the absence of the IE "All MBSFN services notified" the UE attempts to receive notifications on all frequencies for which the IE “MBSFN services not notified” is indicated on that band.
8.5.7.3.4 Method of test
Initial condition
System Simulator:
– MBSFN carrier: 3 cells, Cell 31, Cell 36 and Cell 38 (all PLMN1). Cell 36 and Cell 38 are powered off. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (No ongoing session) according to subclause 11.2 of TS 34.108.
Unicast carrier: 1 cell, Cell 1 (PLMN1) default configuration.
User Equipment:
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains, as specified in clause 7.2.2 of TS 34.108.
– The UE is in MBSFN Idle mode with no activated service as specified in clause 7.6.3 of TS 34.108.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test procedure
The test shall be performed as two independent sub-tests with the UE and SS being returned to Initial Conditions between the sub-tests. The test method shall be the same for the two sub-tests with the exception that:
– In sub-test 1, Local Service 1 in Service Area 1 (Cell 33) shall be activated in the UE;
– In sub-test 2, Local Service 1 in Service Area 4 (Cell 36) shall be activated in the UE.
The SS shall apply the downlink power settings as shown below:
Step 1-7:
Parameter |
Unit |
Cell 1 |
Cell 31 |
Cell 33 |
Cell 36 |
UTRA RF Channel Number |
Ch. 1 |
Ch. 2 |
Ch. 3 |
Ch. 4 |
|
P-CCPCH RSCP |
dBm |
-60 |
-60 |
OFF |
OFF |
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-60 |
– |
– |
P-CPICH (IMB) |
dBm/3.84MHz |
-60 |
OFF |
OFF |
|
T-CPICH (IMB) |
dBm/3.84MHz |
-50.5 |
OFF |
OFF |
Step 8-33:
Parameter |
Unit |
Cell 1 |
Cell 31 |
Cell 33 |
Cell 36 |
UTRA RF Channel Number |
Ch. 1 |
Ch. 2 |
Ch. 3 |
Ch. 4 |
|
P-CCPCH RSCP |
dBm |
-60 |
-60 |
-60 |
-60 |
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-60 |
-60 |
-60 |
P-CPICH (IMB) |
dBm/3.84MHz |
-60 |
-60 |
-60 |
|
T-CPICH (IMB) |
dBm/3.84MHz |
-50.5 |
-50.5 |
-50.5 |
a) The UE is camping on Cell 1 and Cell 31. For 3.84 Mcps TDD IMB, the UE is camping on the FDD unicast carrier cell 1 and IMB cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108. Note: The IE "MBSFN inter frequency neighbour list" is not present in MBMS GENERAL INFORMATION.
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE.
c) The SS sends CLOSE UE TEST LOOP to activate RLC SDU counting on MTCH. The Short Transmission identity is set to value "2" corresponding to Local Service 1 (see TS 34.108 clause 11.2.4) on either Cell 33 or Cell 36.
d) For Cell 31 in the IE "MBSFN inter frequency neighbour list" of the MBMS GENERAL INFORMATION message the SS adds (i) the frequency for Cell 36 with the IE "MBSFN services notification" set to "MBSFN services not notified" and without the option "All MBSFN services notified", and (ii) the frequency for Cell 33 with the IE "MBSFN services notification" set to "MBSFN services not notified" without the option "All MBSFN services notified". The SS sends MBMS MODIFIED SERVICES INFORMATION with IE "MBMS re- acquire MCCH" set to "True".
e) The UE shall re-perform the MCCH acquisition procedure on Cell 31.
f) The SS powers on Cell 33 and Cell 36. MCCH messages are transmitted by the SS on Cell 36 using MBMS configuration C2 (one PTM session ongoing – Local Service 1) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108. MCCH messages are transmitted by the SS on Cell 33 using MBMS configuration C2 (one PTM session ongoing – Local Service 1) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
g) Local Service 1 for the Service Area determined by the sub-test number (see above) is activated at the UE.
h) The UE shall re-tune to the frequency for Cell 33 or Cell 36, perform MBSFN cluster reselection and shall perform the MCCH acquisition procedure. If the UE determines that the selected MBMS service is available on this cell then the UE proceeds to the next step. Otherwise, the UE re-tunes to the other frequency, performs MBSFN cluster reselection and again performs the MCCH acquisition procedure to find the selected MBMS service.
i) The UE immediately establishes the p-t-m radio bearer for Local Service 1. The UE closes the test loop and starts counting successfully received RLC PDUs on the MTCH. The UE will send CLOSE UE TEST LOOP COMPLETE.
j) On Cell 33 the SS broadcasts 10 RLC SDUs on the MTCH configured on the MBMS p-t-m radio bearer for Local Service 1. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD), or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or a 124 kbps RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD).
k) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check the counter returned by the UE for the MTCH in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS stores the value.
l) On Cell 36 the SS broadcasts 10 RLC SDUs on the MTCH configured on the MBMS p-t-m radio bearer for Local Service 1. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD), or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or a 124 kbps RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD).
m) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check the counter returned by the UE for the MTCH in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE, using the stored initial count from step k).
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
M |
MBMS MCCH Message Configuration C1 |
No sessions ongoing. IE "MBSFN inter frequency neighbour list" not present in MBMS GENERAL INFORMATION |
|
2 |
|
U |
ACTIVATE RB TEST MODE |
||
3 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
4 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated with Short Transmission Identity = "2". |
|
5 |
|
M |
MBMS MCCH Message Configuration C1 |
Cell 31: IE "MBMS re-acquire MCCH" set to "True" in MBMS MODIFIED SERVICES INFO. Frequencies for Cell 33 and Cell 36 have been added to IE "MBSFN inter frequency neighbour list". |
|
6 |
UE |
M |
UE re-acquires MCCH on Cell 31. |
||
7 |
SS |
The SS powers on Cell 33 and Cell 36. |
|||
8 |
|
M |
MBMS MCCH Message Configuration C2 |
Cell 33: One PTM session ongoing (Local Service 1). 129.6(FDD) or 124(TDD)kbps PS RAB. |
|
9 |
|
M |
MBMS MCCH Message Configuration C2 |
Cell 36: One PTM session ongoing (Local Service 1). 129.6(FDD) or 124(TDD)kbps PS RAB. |
|
10 |
UE |
M |
Local Service 1 is activated at the UE, for the Service Area determined by the sub-test execution number (see above). |
||
11 |
SS |
The SS shall set a timer value of 300 seconds to wait for CLOSE UE TEST LOOP COMPLETE from the UE. If a timeout occurs the test shall be deemed failed and execution continues from step 20. |
|||
12 |
UE |
M |
UE retunes to frequency for Cell 33 and/or Cell 36 and acquires the MCCH. |
||
13 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE shall establish the indicated p-t-m radio bearer for Local Service 1 and close the test loop. |
|
14 |
SS |
M |
The SS transmits 10 RLC SDUs on the MTCH for Cell 33. |
||
15 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
16 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks the number of reported RLC SDUs received on the MTCH. SS stores the value. |
|
17 |
SS |
M |
The SS transmits 10 RLC SDUs on the MTCH for Cell 36. |
||
18 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
19 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks the number of reported RLC SDUs received on the MTCH. |
|
20 |
|
U |
OPEN UE TEST LOOP |
||
21 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
22 |
|
U |
DEACTIVATE RB TEST MODE |
||
23 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Specific message contents
With the following exceptions, all messages have the same content as defined in TS 34.108 clause 9.1.3 for the MBSFN carriers and in TS 34.108 clause 9.1.1 or 9.1.2 for the unicast carrier:
MBMS MODIFIED SERVICES INFORMATION (Step 1, Step 8, and Step 9)
Information Element |
Value/remark |
Version |
---|---|---|
Modified service list |
Not Present |
Rel-6 |
MBMS re- acquire MCCH |
Not Present |
Rel-6 |
MBMS dynamic persistence level |
Not Present |
Rel-6 |
End of modified MCCH information |
Not Present |
Rel-6 |
MBMS number of neighbour cells |
0 |
Rel-6 |
MBMS all unmodified p-t-m services |
Not Present |
Rel-6 |
MBMS p-t-m activation time |
Not Present |
Rel-6 |
MIB Value tag |
Not Present |
Rel-7 |
MBMS UNMODIFIED SERVICES INFORMATION (Dedicated National carrier) (Step 1 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
Not Present |
Rel-6 |
MBMS GENERAL INFORMATION (Step 1)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Not Present |
Rel-7 |
MBMS MODIFIED SERVICES INFORMATION (Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
Modified service list |
Not Present |
Rel-6 |
MBMS re- acquire MCCH |
True |
Rel-6 |
MBMS dynamic persistence level |
Not Present |
Rel-6 |
End of modified MCCH information |
Not Present |
Rel-6 |
MBMS number of neighbour cells |
0 |
Rel-6 |
MBMS all unmodified p-t-m services |
Not Present |
Rel-6 |
MBMS p-t-m activation time |
Not Present |
Rel-6 |
MIB Value tag |
Not Present |
Rel-7 |
MBMS GENERAL INFORMATION (Step 5) (FDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 5) (TDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 5)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– IMB indication |
TRUE |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– IMB indication |
TRUE |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS UNMODIFIED SERVICES INFORMATION (Step 8)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
4 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 1) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
’01’ |
|
– MBMS required UE action |
Acquire PTM RB info |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 2) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
MBMS UNMODIFIED SERVICES INFORMATION (Step 8)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
2 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
MBMS GENERAL INFORMATION (Step 8)(FDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 8)(TDD)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f1" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 8)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– IMB indication |
TRUE |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– IMB indication |
TRUE |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS UNMODIFIED SERVICES INFORMATION (Step 9)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
4 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 1) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
’01’ |
|
– MBMS required UE action |
Acquire PTM RB info |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(Local Service 2) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
MBMS UNMODIFIED SERVICES INFORMATION (Step 9) (IMB)
Information Element |
Value/remark |
Version |
---|---|---|
Message type |
Rel-6 |
|
Unmodified service list |
2 services |
Rel-6 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 5) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
– MBMS Transmission identity |
||
– MBMS Service ID |
(National Service 6) |
|
– MBMS Service ID |
Refer to clause 11.2.4 "MBSFN service availability" |
|
– CHOICE PLMN identity |
SameAs-MIB |
|
– no data |
||
– MBMS Session ID |
Not Present |
|
– MBMS required UE action |
None |
|
– MBMS preferred frequency |
Not Present |
|
– MBSFN cluster frequency |
Not Present (MD) |
Rel-7 |
MBMS GENERAL INFORMATION (Step 9)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f1" |
|
– CHOICE MBSFN services notification |
MBSFN services notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services notified |
|
– no data |
MBMS GENERAL INFORMATION (Step 9)(IMB)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– IMB indication |
TRUE |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
||
– MBSFN frequency |
||
– CHOICE mode |
TDD |
|
– UARFCN (Nt) |
Refer to clause 5.1 "Test frequencies" for frequency "f3" |
|
– IMB indication |
TRUE |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
8.5.7.3.5 Test requirements
For sub-test 1:
1) After step 15, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a count > 0 for the number of RLC SDUs received.
2) After step 18, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a count corresponding to zero RLC SDUs.
For sub-test 2:
1) After step 15, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a count = 0 for the number of RLC SDUs received.
2) After step 18, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report a count > 0 for the number of RLC SDUs received.
8.5.7.4 MBSFN TDM Information / TDM services de-multiplexing
8.5.7.4.1 Definition
This test is applicable for UEs that support MBMS broadcast services in MBSFN mode and which support either both transmit and receive functions or MBSFN receive only function.
8.5.7.4.2 Conformance requirement
For cells operating in MBSFN mode as indicated in subclause 8.1.1.6.3 upon receiving the MBMS CURRENT CELL P-T-M RB INFORMATION message, the UE shall act as specified in subclauses 8.7.5.3.
…
The UE applies the MBMS p-t-m radio bearer configuration procedure whenever it detects that one of the activated services is provided by means of a p-t-m radio bearer. This may occur as part of the MCCH acquisition or the MBMS Notification procedure.
…
Upon completing the reception of the MBMS COMMON P-T-M RB INFORMATION and the MBMS CURRENT CELL P-T-M RB INFORMATION messages for an activated MBMS service, the UE shall:
1> if the UE is already receiving an MTCH and does not have the capability to receive the new service in addition:
2> the UE behaviour is undefined.
NOTE: In this case, the UE may request upper layers to prioritise the services and only receive the service(s) prioritised by upper layers.
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following;
1> if the UE previously received the service by means of a p-t-m radio bearer from a cell belonging to another MBMS cell group:
2> re-establish RLC;
2> re-initialise PDCP.
1> start immediately to use the indicated configuration unless specified otherwise;
1> start or continue receiving the indicated p-t-m radio bearers depending on its UE capabilities.
The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information i.e. the MBMS Modified services Information message, MBMS Unmodified services Information message, MBMS COMMON P-T-M RB INFORMATION and the MBMS CURRENT CELL P-T-M RB INFORMATION message should be acquired in the same modification period.
…
If the IE "MBSFN TDM Information List" is included, the UE shall:
1> assume that the MBMS service identified in IE "MBMS short transmission ID" can be received only in frame(s) with the CFN fulfilling the following equation:
(CFN div N) mod TDM_Rep = TDM_Offset + i, i = 0 to TDM_Length – 1
where
– N is the TTI (in number of 10ms frames) of the FACH
– TDM_Rep is the repetition period
– TDM_Offset is the offset
– TDM_Length is the number of TTIs the MBMS Service is transmitted, starting from TDM _Offset
– CFN is set according to subclause 8.5.15.3 (Initialisation for Cell_FACH).
Reference
3GPP TS 25.331 clauses 8.7.2.5, 8.7.5.2, 8.7.5.3, 8.6.9.9ae
8.5.7.4.3 Test purpose
1. To verify that the UE correctly acquires the MCCH, when two services included in the variable MBMS_ACTIVATED_SERVICES are broadcast in a time division multiplexed fashion in the current MBSFN cluster.
2. To verify that the UE correctly acts upon the IE MBSFN TDM Information List received in the MBMS CURRENT CELL P-T-M RB INFORMATION messages for the two services in the variable MBMS_ACTIVATED_SERVICES and correctly de-multiplexes the two sessions.
8.5.7.4.4 Method of test
Initial condition
System Simulator:
– MBSFN carrier: 1 cell, Cell 31 (PLMN1). In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 and Default1 MCCH scheduling (one ongoing session) according to subclause 11.2 of TS 34.108.
– Unicast carrier : 1 cell, Cell 1 with default parameters.
User Equipment:
– On the unicast carrier cell the UE is in registered Idle Mode on PS (state 3) if the UE only supports PS domain or registered Idle Mode on CS/PS (state 7) if the UE supports both CS and PS domains, as specified in clause 7.2.2 of TS 34.108.
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which a session will start on MBSFN Cell 31 (see TS 34.108 clause 11.2.4) during the test.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test procedure
a) The UE is camping on Cell 1 and Cell 31. For 3.84 Mcps TDD IMB, the UE is camping on the FDD unicast carrier cell 1 and IMB cell 31. In addition to broadcasting System Information, MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C1 (no session ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
b) The SS sends ACTIVATE RB TEST MODE on the unicast carrier and the UE responds with ACTIVATE RB TEST MODE COMPLETE. The SS then sends CLOSE UE TEST LOOP to activate RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
c) The SS notifies on MCCH, for one modification period, about the start of the MBMS sessions. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (two PTM sessions starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
d) From the first SFN of the next modification period the SS transmits MCCH messages on Cell 31 using MBMS configuration C2 (two PTM sessions ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108
e) The UE establishes the p-t-m radio bearer for the activated service according to the specified service activation time (i.e. the first SFN of the modification period following the notification (step c). The UE closes the test loop and starts counting successfully received RLC PDUs on the MTCH. The UE will send CLOSE UE TEST LOOP COMPLETE.
f) The SS then broadcasts 10 RLC SDUs on the MTCH configured for the MBMS service not activated by the UE. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD) or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or the RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD) of TS 34.108. The nominal data rate of the RB as given in TS 34.108 will be scaled down by the factor (TDM_Length/TDM_Rep) as described in TS 25.331 clause 8.6.9.9ae.
g) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is = 0.
h) The SS then broadcasts 10 RLC SDUs on the MTCH configured for the MBMS service activated by the UE. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD) or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB)or the RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD) of TS 34.108. The nominal data rate of the RB as given in TS 34.108 will be scaled down by the factor (TDM_Length/TDM_Rep) as described in TS 25.331 clause 8.6.9.9ae.
i) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is > 0.
j) The SS sends OPEN UE TEST LOOP. The UE responds with OPEN UE TEST LOOP COMPLETE.
k) MCCH messages are then transmitted by the SS on Cell 31 using MBMS configuration C1 (no sessions ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108.
l) The SS then delays for 5*modification period and then sends CLOSE UE TEST LOOP to re-start RLC SDU counting on Cell 31 MTCH (Transmission identity indicating the MBMS activated service).
m) The SS notifies on MCCH, for one modification period, about the start of the MBMS sessions. MCCH messages are transmitted by the SS on Cell 31 using MBMS configuration C4 (two PTM sessions starting) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108. A different TDM configuration from that notified in step c) is used.
n) From the first SFN of the next modification period the SS transmits MCCH messages on Cell 31 using MBMS configuration C2 (two PTM sessions ongoing) and Default1 MCCH scheduling according to clause 11.2 of TS 34.108
o) The UE establishes the p-t-m radio bearer for the activated service according to the specified service activation time (i.e. the first SFN of the modification period following the notification (step c). The UE closes the test loop and starts counting successfully received RLC PDUs on the MTCH. The UE will send CLOSE UE TEST LOOP COMPLETE.
p) The SS then broadcasts 10 RLC SDUs on the MTCH configured for the MBMS service not activated by the UE. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD) or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or the RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD) of TS 34.108. The nominal data rate of the RB as given in TS 34.108 will be scaled down by the factor (TDM_Length/TDM_Rep) as described in TS 25.331 clause 8.6.9.9ae.
q) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is = 0.
r) The SS then broadcasts 10 RLC SDUs on the MTCH configured for the MBMS service activated by the UE. The service is carried on a 129.6kbps RB for MTCH with 80 ms TTI as specified in clause 6.10.3.4.4.6(FDD) or a 124.4 kbps RB for MTCH with 80 ms TTI as specified in clause 6.11.7.2.2.1 (3.84 Mcps TDD IMB) or the RB for MBSFN MTCH with 80ms TTI as specified in clause 6.10.3.4.4.9 (3.84 Mcps TDD) or clause 6.11.5.4.4.9 (1.28 Mcps TDD) or clause 6.11.6.4.4.9 (7.68 Mcps TDD) of TS 34.108. The nominal data rate of the RB as given in TS 34.108 will be scaled down by the factor (TDM_Length/TDM_Rep) as described in TS 25.331 clause 8.6.9.9ae.
s) The SS sends UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST and waits for the UE to respond with UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE. The SS shall check that the counter returned by the UE for the MTCH of the activated service in the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE is > 0.
Expected sequence
Step |
Direction |
Carrier |
Message |
Comment |
|
UE |
SS |
||||
1 |
|
U |
ACTIVATE RB TEST MODE |
||
2 |
|
U |
ACTIVATE RB TEST MODE COMPLETE |
||
3 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated for the selected national service on MTCH. |
|
4 |
|
M |
MBMS MCCH Message Configuration C4 |
For one modification period. Two sessions starting, one of which is the activated service. |
|
5 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. Two sessions ongoing. |
|
6 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE shall establish the indicated p-t-m radio bearer and close the test loop. |
|
7 |
SS |
M |
Then SS transmits 10 RLC SDUs on the MTCH, for the service not activated by the UE. |
||
8 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
9 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH equals zero. |
|
10 |
SS |
M |
Then the SS transmits 10 RLC SDUs on the MTCH for the service activated by the UE. |
||
11 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
12 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. |
|
13 |
|
U |
OPEN UE TEST LOOP |
||
14 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
15 |
|
M |
MBMS MCCH Message Configuration C1 |
No sessions ongoing |
|
16 |
SS |
M |
SS delays for a period 5*modification period. |
||
17 |
|
U |
CLOSE UE TEST LOOP |
Loop back mode 3 is activated for the selected national service on MTCH. |
|
18 |
|
M |
MBMS MCCH Message Configuration C4 |
For one modification period. Two sessions starting, one of which is the activated service. |
|
19 |
|
M |
MBMS MCCH Message Configuration C2 |
No modified services. Two sessions ongoing |
|
20 |
|
U |
CLOSE UE TEST LOOP COMPLETE |
The UE shall establish the indicated p-t-m radio bearer and close the test loop. |
|
21 |
SS |
M |
Then SS transmits 10 RLC SDUs on the MTCH, for the service not activated by the UE. |
||
22 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
23 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH equals zero. |
|
24 |
SS |
M |
Then the SS transmits 10 RLC SDUs on the MTCH for the service activated by the UE. |
||
25 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
26 |
|
U |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC SDUs received on the MTCH is greater than zero. |
|
27 |
|
U |
OPEN UE TEST LOOP |
||
28 |
|
U |
OPEN UE TEST LOOP COMPLETE |
||
29 |
|
U |
DEACTIVATE RB TEST MODE |
||
30 |
|
U |
DEACTIVATE RB TEST MODE COMPLETE |
Specific message contents
With the following exceptions, all messages have the same content as defined in TS 34.108 clause 9.1.3 for the MBSFN carriers and in TS 34.108 clause 9.1.1 or 9.1.2 for the unicast carrier:
MBMS CURRENT CELL P-T-M RB INFORMATION (Step 4 and Step 5)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN TDM Info List |
Rel-7 |
|
– MBMS short transmission ID |
Index to the activated service |
|
– TDM_Rep |
8 |
|
– TDM_Offset |
4 |
|
– TDM_Length |
4 |
|
– MBMS short transmission ID |
Index to the not activated service |
|
– TDM_Rep |
8 |
|
– TDM_Offset |
0 |
|
– TDM_Length |
2 |
MBMS CURRENT CELL P-T-M RB INFORMATION (Step 18 and Step 19)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN TDM Info List |
Rel-7 |
|
– MBMS short transmission ID |
Index to the activated service |
|
– TDM_Rep |
4 |
|
– TDM_Offset |
0 |
|
– TDM_Length |
1 |
|
– MBMS short transmission ID |
Index to the not activated service |
|
– TDM_Rep |
4 |
|
– TDM_Offset |
1 |
|
– TDM_Length |
3 |
8.5.7.4.5 Test requirements
1) After step 9, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report an SDU count = 0.
2) After step 12, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report an SDU count > 0.
3) After step 23, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report an SDU count = 0.
4) After step 26, the UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE message shall report an SDU count > 0.
8.5.7.5 MBSFN Session Reconfiguration / Change of MBSFN Cluster frequency on notification via MCCH (FDD)
8.5.7.5.1 Definition
This test is applicable for UEs that support MBMS broadcast services in MBSFN mode and which support either both transmit and receive functions or MBSFN receive only function.
8.5.7.5.2 Conformance requirement
The UE applies the MCCH acquisition procedure to determine the MBMS services available in the cell and to initiate reception of the services that the UE has activated. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle, URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH).
…
The UE shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3.
…
For cells operating in MBSFN mode as indicated in subclause 8.1.1.6.3 the UE shall immediately acquire the MBMS GENERAL INFORMATION messages i.e. It shall not delay reception of these messages until it has completed the acquisition of the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION messages. Likewise for cells operating in MBSFN mode as indicated in subclause 8.1.1.6.3, the UE should immediately acquire the MBMS CURRENT CELL P-T-M RB INFORMATION.
The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information e.g. Both the MBMS MODIFIED SERVICES INFORMATION and the MBMS UNMODIFIED SERVICES INFORMATION message should be acquired in the same modification period.
…
When requested to acquire MBMS control information other than the MBMS Access Information message, the UE shall:
1> if requested to start reading MCCH at the next modification period:
2> start reading MCCH at the beginning of the next modification period.
1> otherwise
2> start reading MCCH at the beginning of the next repetition period.
1> if requested to stop reading MCCH at the end of the modification period:
2> continue reading MCCH until the required MBMS control information is received or until the UE detects a TTI in which no MCCH information is transmitted, whichever is first;
2> continue reading MCCH in this manner at every subsequent repetition period, until the information is received correctly or until the end of the modification period.
1> otherwise:
2> continue reading MCCH until the required MBMS control information is received or until the UE detects a TTI in which no MCCH information is transmitted, whichever is first;
2> continue reading MCCH in this manner at every subsequent repetition period, until the information is received correctly.
NOTE 1: The UE may combine information received at different repetition periods within a modification period.
…
The MBMS notification procedure is used by the UE to respond to a notification provided by UTRAN, indicating a change applicable for one or more MBMS services the UE has activated. The procedure applies to all UEs supporting MBMS, irrespective of their state (idle and connected mode: URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH). The actual notification mechanism to be used depends on the UE state.
…
The UE may:
1> monitor the MBMS notification Indicator Channel (MICH);
1> if a notification on the MICH for one or more of the MBMS services included in the variable MBMS_ACTIVATED_SERVICES is detected:
2> acquire the MBMS MODIFIED SERVICES INFORMATION message with delaying the reading of MCCH until the next modification period and with stopping at the end of the modification period, in accordance with subclause 8.7.1.3;
2> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.
The UE shall:
1> if in idle mode, URA_PCH, CELL_PCH or CELL_FACH state:
2> if not monitoring MICH during the current or the previous modification period:
3> acquire the MBMS MODIFIED SERVICES INFORMATION message from MCCH at the start of every modification period, in accordance with subclause 8.7.1.3;
3> handle the MBMS MODIFIED SERVICES INFORMATION message as specified in subclause 8.7.3.4.
…
If the IE "MBMS required UE action" is included and concerns an MBMS activated service the UE shall:
…
1> if the IE "MBMS required UE action" is set to ‘Acquire PTM RB info’; or
1> if the IE "MBMS required UE action" is set to ‘Acquire counting info– PTM RBs unmodified’ and the UE is not receiving a p-t-m RB for the concerned service:
2> continue acquiring the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION messages without delaying reading of MCCH until the next modification period and without stopping at the end of the modification period, in accordance with subclause 8.7.1.3
2> act upon the MBMS COMMON P-T-M RB INFORMATION, MBMS CURRENT CELL P-T-M RB INFORMATION and the MBMS NEIGHBOURING CELL P-T-M RB INFORMATION message, if received, in accordance with subclause 8.7.5;
…
Upon completing the reception of the MBMS COMMON P-T-M RB INFORMATION and the MBMS CURRENT CELL P-T-M RB INFORMATION messages for an activated MBMS service, the UE shall:
1> if the UE is already receiving an MTCH and does not have the capability to receive the new service in addition:
2> the UE behaviour is undefined.
NOTE: In this case, the UE may request upper layers to prioritise the services and only receive the service(s) prioritised by upper layers.
1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following;
1> if the UE previously received the service by means of a p-t-m radio bearer from a cell belonging to another MBMS cell group:
2> re-establish RLC;
2> re-initialise PDCP.
1> start immediately to use the indicated configuration unless specified otherwise;
1> start or continue receiving the indicated p-t-m radio bearers depending on its UE capabilities.
The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information i.e. the MBMS Modified services Information message, MBMS Unmodified services Information message, MBMS COMMON P-T-M RB INFORMATION and the MBMS CURRENT CELL P-T-M RB INFORMATION message should be acquired in the same modification period.
…
The UE shall:
1> if the IE "Secondary CCPCH system information MBMS" is included:
2> apply the Secondary CCPCH and FACH indicated by the IE "FACH carrying MCCH" for receiving MCCH.
1> otherwise, if the IE "Secondary CCPCH system information" includes the IE "MCCH configuration information":
2> apply the Secondary CCPCH and FACH indicated by the IE “MCCH configuration information” for receiving MCCH.
1> for TDD, if the IE "TDD MBSFN Information" is included:
2> apply the scrambling codes (as referenced by the "Cell parameters ID") to each timeslot indicated by "TDD MBSFN Information".
Reference
3GPP TS 25.331 clauses 8.7.2.1, 8.7.2.3, 8.7.1.3, 8.7.3.1, 8.7.3.3.1, 8.6.9.6, 8.7.5.3, 8.1.1.6.5
8.5.7.5.3 Test purpose
To verify that the UE correctly handles the notification procedure after receiving the MBMS MODIFIED SERVICES INFORMATION message via MCCH indicating a change in available services.
To verify that the UE acts upon service priority indications from upper layers that require a change in MBSFN cluster frequency.
To verify that the UE acquires the MBMS information on MCCH after selecting the new MBSFN cluster.
To verify that the UE, after acquiring the MBMS information on MCCH, starts the p-t-m reception of the higher priority MBMS service according to the information on MCCH..
8.5.7.5.4 Method of test
Initial condition
System Simulator:
– MBSFN carrier: 2 cells, Cell 31 and Cell 33, the tow cells are in deferent MBSFN cluster.
User Equipment:
– The UE is in MBSFN Idle mode with one activated service as specified in clause 7.6.4 of TS 34.108. The UE has selected (i.e. it is included in MBMS_ACTIVATED_SERVICES variable) a national service for which a session will start on MBSFN Cell 31 during the test.
Related ICS/IXIT statements
– MBMS Broadcast services in MBSFN mode application available on UE Yes/No.
– Support of transmit and receive functions available on UE Yes/No.
– Support of MBSFN receive only function available on UE Yes/No.
Test procedure
a) The UE camps on Cell 31 in idle state and establish to start receiving MBMS Service_1.
b) Another MBMS Service_2 is set up in Cell 33 and the SS sends a notification to the UE about the active services in Cell 31 by MCCH.
c) The UE gets the IE“MBSFN cluster frequency” which is updated and selects MBMS Service_2,then ,the UE shall stop receiving Service_1 and perform Cell Reselection from Cell 31 to Cell 33.
d) After selecting the new MBSFN cluster, the UE acquires the MBMS information on MCCH; the UE starts the p-t-m reception of the MBMS Service_2.
Expected sequence
Step |
Direction |
Message |
Comment |
|
UE |
SS |
|||
The UE camps on Cell 31 and starts reception of the MBMS Service_1 |
||||
1 |
|
MBMS MODIFIED SERVICES INFORMATION |
The MBMS Service_2 has been activated by upper layer in the other MBSFN cluster. The SS notifies the UE the MBMS Service_2 is available on the MCCH. |
|
2 |
|
MBMS General Information |
The UE gets the MBSFN inter frequency neighbour list including Cell 33. |
|
3 |
The UE selects the MBMS Service_2 |
|||
4 |
The UE performs Cell Reselection to select new MBSFN cluster. |
|||
5 |
|
MBMS MODIFIED SERVICES INFORMATION |
In Cell 33, the UE acquires the MBMS information on MCCH. |
|
6 |
|
MBMS Common p-t-m rb Information |
||
7 |
|
MBMS UNMODIFIED SERVICES INFORMATION |
The UE starts reception of the MBMS Service_2 on MTCH. |
|
8 |
|
CLOSE UE TEST LOOP |
||
9 |
|
CLOSE UE TEST LOOP COMPLETE |
Loop back mode 3 on MTCH is activated. |
|
10 |
SS |
The SS broadcasts 10 RLC SDUs of MBMS data on MTCH on the concerned MBMS radio bearer. |
||
11 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER REQUEST |
||
12 |
|
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE |
The SS checks that the number of reported RLC PDUs is greater than zero and records the value. |
Specific Message Contents.
MBMS MODIFIED SERVICES INFORMATION (Step 1)
Information Element |
Value/remark |
Modified service list |
|
– MBMS Transmission identity |
MBMS Transmission identity indicating MBMS activated service |
– MBMS required UE action |
Acquire PTM RB info |
– MBSFN cluster frequency |
2 |
MBMS General Information (Step 2)
Information Element |
Value/remark |
Version |
---|---|---|
… |
||
MBSFN inter frequency neighbour list |
Rel-7 |
|
– MBSFN frequency |
||
– CHOICE mode |
FDD |
|
– UARFCN downlink (Nd) |
Refer to clause 5.1 "Test frequencies" for frequency "f2" |
|
– CHOICE MBSFN services notification |
MBSFN services not notified |
|
– no data |
MBMS MODIFIED SERVICES INFORMATION (Step 5)
Information Element |
Value/remark |
Modified service list |
|
– MBMS Transmission identity |
MBMS Transmission identity indicating MBMS activated service |
– MBMS required UE action |
Acquire PTM RB info |
– MBSFN cluster frequency |
The Current MBSFN Cluster |
UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE (Step 7)
Information Element |
Value/remark |
RLC SDU Counter Value |
Check that the number is greater than zero. |
8.5.7.5.5 Test requirements
At step 4 the UE shall select new MBSFN Cluster and perform Cell Reselection from Cell 31 to Cell 33.
At step 12 the UE shall send a UE TEST LOOP MODE 3 RLC SDU COUNTER RESPONSE with a RLC SDU counter value greater zero.