26.6.23 Test of Repeated SACCH
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
26.6.23.1 Repeated SACCH / Downlink Repeated SACCH
26.6.23.1.1 Conformance requirement
If a downlink SACCH block is incorrectly decoded (prior to combining with any previously received SACCH block), and the next uplink SACCH block is not a repetition as per the Repeated SACCH procedure (see sub-clause 11.3), then the MS shall set the SACCH Repetition Request in the next uplink SACCH block to "Repeated SACCH required" (see 3GPP TS 44.004).
If a downlink SACCH block is correctly decoded (prior to combining with any previously received SACCH block), and the next uplink SACCH block is not a repetition as per the Repeated SACCH procedure (see sub-clause 11.3), the MS shall set the SACCH Repetition Request in the next uplink SACCH block to "Repeated SACCH not required".
References
3GPP TS 44.006 clause 11.2.
26.6.23.1.2 Test purpose
To verify that when the downlink SACCH block is wrongly decoded, the MS sends an uplink SACCH block containing SACCH Repetition Request set to "Repeated SACCH required" and when the downlink SACCH block is decoded correctly, the MS sends an uplink SACCH block containing SACCH Repetition Request set to "Repeated SACCH not required"
26.6.23.1.3 Method of test
Specific PICS statements:
–
PIXIT statements:
–
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Foreseen final state of the MS
U0, null.
26.6.23.1.4 Test procedure
a) A MS terminated call is set up according to the generic call set up procedure.
b) For 10 secs, the SS sends error free SACCH messages.
c) SS Sends one SACCH messages with unrecoverable errors.
d) For 10 secs the SS shall continuously send error free SACCH messages.
26.6.23.1.5 Test requirement
1) In step b, check that all the uplink SACCH messages have SACCH Repetition Request set to “Repeated SACCH not required”
2) After step c, check that the MS sends a SACCH message having SACCH Repetition Request set to “Repeated SACCH required”.
3) In step d, check that all the uplink SACCH messages have SACCH Repetition Request set to “Repeated SACCH not required”
Specific Message Contents
None.
26.6.23.2 Repeated SACCH / Uplink Repeated SACCH
26.6.23.2.1 Conformance requirement
At the MS side, if an uplink SACCH block contains a SAPI 0 frame and is not already a repetition, and if the last correctly received SACCH Repetition Order was set to "Repeated SACCH required", then the MS shall repeat this SACCH block at the next SACCH block period.
References
3GPP TS 44.006 clause 11.3.
26.6.23.2.2 Test purpose
To verify that the MS repeats an uplink SACCH block when the downlink SACCH blocks contains SACCH Repetition Order set to "Repeated SACCH required".
26.6.23.2.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS statements:
–
PIXIT statements:
–
Foreseen final state of the MS
U0, null.
26.6.23.2.4 Test procedure
a) A MS terminated call is set up according to the generic call set up on cell A.
b) For the duration of test case, power levels of serving cell is changed in a steps from –50dBm to –65dBm to –80dBm and back to –50dBm, by doing one change at every 480 ms. This is made to make sure that every report is different from the previous one.
c) For 10 sec, the SS sends SACCH messages, setting SACCH Repetition Order to “Repeated SACCH Not Required”.
d) SS Sends one SACCH messages setting SACCH Repetition Order to “Repeated SACCH Required”.
e) For 10 more secs, the SS shall continuously send SACCH messages with SACCH Repetition Order set to “Repeated SACCH Not Required”.
26.6.23.2.5 Test requirement
1) In step c, check that MS is not retransmitting the SACCH messages on uplink.
2) After step d, Check that the MS repeats the last message.
3) In step e, check that MS is not retransmitting the SACCH messages on uplink.
Specific Message Contents
None.
26.6.23.3 Repeated SACCH / Uplink Repeated SACCH with SAPI 3 frames
26.6.23.3.1 Conformance requirements
At the MS side, if an uplink SACCH block contains a SAPI 0 frame and is not already a repetition, and if the last correctly received SACCH Repetition Order was set to "Repeated SACCH required", then the MS shall repeat this SACCH block at the next SACCH block period. If a SAPI 3 frame was also scheduled to be sent at this next SACCH period, the MS shall delay the sending of the SAPI 3 frame by one SACCH period in order to make room for the repetition.
Reference
3GPP TS 44.006 clause 11.3.
26.6.23.3.2 Test purpose
To verify that the MS delays sending of a SAPI 3 frame by one SACCH period if a repeated SAPI 0 SACCH frame is to be repeated according to the SACCH Repetition Parameter in the downlink SACCH block.
26.6.23.3.3 Method of test
Initial Conditions
System simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in "Idle, updated" state.
Specific PICS Statements
–
PIXIT Statements
– Description of the basic procedures to display a mobile originated short message.
– Maximum length (characters) of a mobile originated short message.
Foreseen Final State of MS
U0, null.
Test Procedure
A data or speech call is established on a TCH with the SS and the state U10 of call control is entered. SACCH Repetition Order is set to “Repeated SACCH required” in all the downlink SACCH blocks. The MS is setup to send an SM. During an SMS transfer it is checked that every SAPI0 SACCH block is repeated once and no SAPI3 SACCH block is repeated.
For the duration of test case, power levels of serving cell is changed in a steps from –50dBm to –65dBm to –80dBm and back to –50dBm, by doing one change at every 480 ms. This is made to make sure that every report is different from the previous one.
Expected sequence
Step |
Direction |
Message |
Comments/actions/next state |
1 |
MS< -> SS |
MS is brought to U10 state. All the downlink SACCH message has SACCH Repetition Order set to “Repeated SACCH required”. |
|
2 |
MS |
The MS is set up to send an SM. |
|
3 |
MS -> SS |
CM SERVICE REQUEST |
Sent in a layer 2 frames on the FACCH. CM service type set to "short message transfer" |
4 |
SS -> MS |
CM SERVICE ACCEPT |
|
5 |
MS -> SS |
SABM (SAPI=3) |
Receive SAPI=3 uplink SACCH block |
6 |
SS -> MS |
UA (SAPI=3) |
|
7 |
MS -> SS |
CP-DATA |
Contains RP-DATA RPDU (SMS SUBMIT TPDU) |
8 |
SS -> MS |
CP-ACK |
|
9 |
SS -> MS |
CP-DATA |
|
10 |
MS -> SS |
CP-ACK |
MO SMS procedure is completed. |
11 |
During steps 7-10, check that the MS is retransmitting every SAPI0 SACCH message once, before sending the new one and no SAPI3 SACCH messages are retransmitted. |
||
12 |
CS call is released and the MS is brought in idle state. |
Specific Message Contents
None.