14.1.6 Generic test procedure for MBMS PTP radio bearers for HS-DSCH combinations
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
This procedure is used to test MBMS PTP radio bearer combinations for HS-DSCH. The procedure is run once for each sub-test of the actual MBMS PTP radio bearer test case. The generic test procedure has two branches: one for the MBMS Selective Service case and one for the MBMS Multicast Service case. The branch to use is specified in the specific test cases.
NOTE The testing of MBMS PTP radio bearer combinations on DPCH and HS-PDSCH is focusing on verifying that the UE is capable to establish the radio bearer combination and to verify correct data transfer using all the possible uplink TFS for transport channels mapped on DCH. This test procedure is based on the generic test procedure for radio bearer combinations on HS-DSCH and DCH in section 14.1.3.5. The main difference compared to the generic test procedure in 14.1.3.5 is that for DTCH mapped to HS-DSCH only one TFRC test point and one HARQ process alternative is tested.
Initial conditions
System Simulator: 1 MBMS cell
The UE is in idle mode state as specified in clause 7.6 of TS 34.108.
The UE has selected the broadcast service or joined the multicast service to be provided by the SS (included in MBMS_ACTIVATED_SERVICES variable).
Test procedure
a) The UE is in the idle mode state.
b) The UE shall detect the available MBMS services by acquiring the MBMS MODIFIED SERVICES INFORMATION (including IE “MBMS required UE action” set to “Request PTP RB”) and the MBMS GENERAL INFORMATION.
c) The UE shall request a p-t-p RB establishment.
d) The SS transmits a RADIO BEARER SETUP message to the UE. This message requests the establishment of a radio access bearer. The UE shall establish this radio bearer. Then the UE transmits a RADIO BEARER SETUP COMPLETE message using AM RLC. See note 1 and note 3.
e) The SS limits the UE allowed uplink transport format combinations according to the "Restricted UL TFCIs", as specified for the sub-test of the actual radio bearer test, using the RRC transport format combination control procedure. See note 2.
f) The SS closes the test loop using UE test loop mode 1 and setting the UL RLC SDU size parameter, for all radio bearers under test, according to the "UL RLC SDU size" value as specified for the sub-test of the actual radio bearer test.
g) The SS selects the first TFRC test point (NPDUs , M, Ncodes and TFRI) according to the applicable table in sub-clauses 14.1.3.3 (MAC-d PDU size=336) or 14.1.3.4 (MAC-d PDU size=656).
h) The SS sets HID = 0.
i) (void)
j) The SS transmits, for each DTCH mapped to HS-DSCH, a DL RLC SDU having the size equal the to the “Test data size” as specified for the sub-test concatenated into a MAC-hs PDU using the selected TFRC and HID. If the radio bearer combination under test includes downlink DTCHs mapped to DCH then the SS transmits, for all DTCHs mapped to DCH, one or more RLC SDUs having the size equal to the "Test data size" as specified for the sub-test of the actual radio bearer test case.
k) The SS checks that the content of the UE returned RLC SDUs have the correct content and are received having the correct transport format. See TS 34.109 [10] clause 5.3.2.6.2 for details regarding the UE loopback of RLC SDUs.
l) The SS opens the UE test loop.
m) Steps e) to l) are repeated for all sub-tests.
n) The SS release the radio bearer. See note 5.
o) The SS may optionally deactivate the radio bearer test mode.
NOTE 1: The SS configures the physical channel parameters according to the actual UE category under test. The number of soft channel bits per HARQ process is split equally among the number of HARQ processes configured for the actual sub-test – i.e. “Total number of soft channel bits” for the UE category according to table 14.1.3.1.1 divided by the number of HARQ processes under test. The number of reordering queues is 1 for single HS-DSCH radio bearer configurations. The MAC-hs window size, RLC Transmission window size and RLC Receiving window size shall be configured as specified for the actual sub-test.
NOTE 2: The restricted set of uplink TFCIs shall contain all possible TFCI that could happen in a sub-test. The actual TTI of the different radio bearers and signalling radio bearers as well as the possible UE processing delays shall be taken into consideration. The restricted set of TFCIs must comply with the minimum set of TFCIs as specified in TS 25.331, clause 8.6.5.2.
NOTE 3: The MAC-hs window size and RLC Receiver and transmitter window sizes need to be chosen such that the UE capability for “Minimum total RLC AM and MAC-hs buffer size” is not exceeded for the UE category under test.
NOTE 4: (void)
NOTE 5: The Secondary scrambling code in the RADIO BEARER RELEASE message is set to the same value used in the RADIO BEARER SETUP MESSAGE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
1 |
|
Void |
||
|
2 |
|
Void |
||
|
3 |
|
MBMS MODIFIED SERVICES INFORMATION |
"MBMS required UE action" set to Request PTP RB. |
|
|
4 |
The UE shall continue acquiring the above messages until it has received a consistent set of MCCH information in the same modification period. |
|||
|
5 |
|
MBMS GENERAL INFORMATION |
||
|
6 |
|
RRC CONNECTION REQUEST |
The UE transmits the message with Establishment cause set to “MBMS ptp RB request” and with the “MBMS Selected Services Short” IE referring to the concerned MBMS Selected service and the corresponding Modification period identity. |
|
|
7 |
|
RRC CONNECTION SETUP |
RRC state indicator set to Cell_DCH |
|
|
8 |
|
RRC CONNECTION SETUP COMPLETE |
||
|
9 |
|
MBMS MODIFICATION REQUEST |
Only for the MBMS broadcast case: The UE completing the RRC Connection Setup procedure shall initiate the MBMS MODIFICATION REQUEST procedure. This message may be received at any point after step 8 and before step 24. |
|
|
10 |
SS |
The SS verifies that the IE "Service type" in the received SERVICE REQUEST message is set to “MBMS Broadcast Service Reception” or “MBMS service used by the test case” respectively depending on the MBMS service used by the test case. |
||
|
11 |
|
SECURITY MODE COMMAND |
||
|
12 |
|
SECURITY MODE COMPLETE |
||
|
12a |
|
ACTIVATE RB TEST MODE |
||
|
12b |
|
ACTIVATE RB TEST MODE COMPLETE |
||
|
13 |
|
RADIO BEARER SETUP |
||
|
14 |
|
RADIO BEARER SETUP COMPLETE |
||
|
15 |
Void |
|||
|
16 |
Void |
|||
|
17 |
<– |
TRANSPORT FORMAT COMBINATION CONTROL (DCCH) |
RRC Transport format combinations is limited to "Restricted UL TFCIs", as specified for the sub-test |
|
|
18 |
<– |
CLOSE UE TEST LOOP (DCCH) |
The SS sets the HS-DSCH TFRC test point and the number of HARQ processes as specified for the sub-test. |
|
|
19 |
–> |
CLOSE UE TEST LOOP COMPLETE (DCCH) |
TC |
|
|
20 |
SS |
For each DTCHs mapped on HS-DSCH the SS creates test data for the first TFRC . The test data shall be dived into 4 RLC SDUs of size (NPDUs * MAC-d PDU payload size) / 4 – 8 bits. The SS sets HID = 0. |
||
|
21 |
<– |
DOWNLINK MAC-hs PDU (HS-DSCH#1) … DOWNLINK MAC-hs PDU (HS-DSCH#N) DL RLC SDU (DL DCH#1) … DL RLC SDU (DL DCH#M) |
For each DTCH mapped on HS-DSCH the SS sends test data. For each DTCH mapped on DCH the SS sends test data using the downlink transport format combination under test. |
|
|
22 |
–> |
UPLINK RLC SDUs |
The SS checks, for each DTCH, that the content and transport format of the received UL RLC SDUs are correct. |
|
|
23 |
<– |
OPEN UE TEST LOOP (DCCH) |
TC |
|
|
24 |
–> |
OPEN UE TEST LOOP COMPLETE (DCCH) |
TC |
|
|
25 |
SS |
The SS repeats steps 15 to 24 for each sub-test |
||
|
26 |
RB RELEASE |
RRC |
||
|
27 |
<– |
DEACTIVATE RB TEST MODE |
TC Optional step |
|
|
28 |
–> |
DEACTIVATE RB TEST MODE COMPLETE |
TC Optional step |
|
Specific Message Contents
MBMS MODIFIED SERVICES INFORMATION (Step 3)
|
Information Element |
Value/remark |
|
Modified services list |
Only 1 entry |
|
– MBMS Transmission identity |
MBMS Transmission identity |
|
– MBMS required UE action |
request PTP RB |
RRC CONNECTION REQUEST for the MBMS broadcast case (Step 6)
|
Information Element |
Value/remark |
|
Message type |
|
|
Initial UE identity |
Same as the registered TMSI or P-TMSI |
|
Establishment Cause |
MBMS ptp RB request |
|
Domain indicator |
PS domain |
|
MBMS Selected Services |
|
|
– MBMS Selected Services |
Only 1 entry |
|
– MBMS Selected Service ID |
MBMS short transmission identity referring to the service the UE has selected |
|
– Modification period identity |
Indicates the modification period the MBMS short transmission identities refer to |
RRC CONNECTION REQUEST for the MBMS muticast case (Step 6)
|
Information Element |
Value/remark |
|
Message type |
|
|
Initial UE identity |
Same as the registered TMSI or P-TMSI |
|
Establishment Cause |
MBMS ptp RB request |
|
Domain indicator |
PS domain |
RRC CONNECTION SETUP (Step 7)
|
Information Element |
Value/remark |
|
Message type |
|
|
Initial UE identity |
Set to same value as received in Step 7 |
|
RRC State Indicator |
Cell_DCH |