hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.1.3 Test purpose | 1) To verify that an MS with human interface, in a SETUP message sent to originate a call, includes the same "Number digits" in the "Called party BCD number" of the SETUP message as displayed.
2) To verify that an MS with MMI, when made to establish a call sends a SETUP message, which includes the "Numbering plan identification" in the "Called party BCD number" of the SETUP message for an outgoing call with the value "ISDN/telephony numbering plan (E.164/E.163)".
3) To verify that an MS with MMI, when made to establish a call without use of the "+-key" function, sends a SETUP message, which includes the "Type of number" in the "Called party BCD number" of the SETUP message for an outgoing call with the value "unknown".
4) To verify that an MS with MMI, implementing the "+-key" function, when made to establish a call with use of the "+-key" function, sends a SETUP message, which includes the "Type of number" in the "Called party BCD number" of the SETUP message for an outgoing call with the value "international number. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.1.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.1.4.1 Initial conditions | The MS is registered in a cell of the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.1.4.2 Procedure | a) A number (not including "+ function") is entered and then a call is set up.
b) After the SS has accepted the call the number displayed on the MS and the number received in the SS are compared.
c) The NPI and TON are examined in the SS.
d) Steps a) to c) are repeated, but in a), the number entered starts with the "+ function".
NOTE: This test may also be performed automatically using the EMMI. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.1.5 Test requirements | 1) In step b), both numbers shall be identical.
2) In step c), the NPI shall be "E164" and the TON shall be "unknown".
3) In step d), the NPI shall be "E164" and the TON shall be "international". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2 Indication of call progress signals | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.1 Definition | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.2 Conformance requirement | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.3 Test purpose | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.4 Ringing tone | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.4.1 Method of test | a) According to subclause "Structured procedures, Mobile originating call, early assignment, Method of test", paragraphs a) to j). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.4.2 Requirements | 1) According to subclause "Structured procedures, Mobile originating call, early assignment, Requirements", paragraphs 1) to 7).
2) The ringing tone characteristics shall be as follows:
Tone
Frequency
Tolerance
Type
Ringing tone
425 Hz
15 Hz
Periodic
tone on 1 s,
silence 4 s |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.5 Busy tone | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.5.1 Method of test | a) According to subclause "Structured procedures, Mobile originating call, early assignment, Method of test", paragraphs a) to h).
b) The SS then sends message DISCONNECT with cause number 17.
Message: DISCONNECT (3GPP TS 04.08 / 3GPP TS 24.008, subclause 9.3.7) to the MS:
Information element
Comment
Protocol discriminator
CM
Transaction identifier
MS orig.
Message type
Cause
- Coding standard
GSM
- Location
User
- Cause value
#17 "user busy" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.5.2 Requirements | 1) According to subclause "Structured procedures, Mobile originating call, early assignment, Requirements", paragraphs 1) to 5).
2) After the reception of DISCONNECT a busy tone shall be generated. The busy tone characteristics shall be as follows:
Tone
Frequency
Tolerance
Type
Busy tone
425 Hz
15 Hz
Periodic
tone on 500 ms,
silence 500 ms |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.6 Congestion tone | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.6.1 Method of test | a) According to subclause "Structured procedures, Mobile originating call, early assignment, Method of test", paragraphs a) to h).
b) The SS then sends message DISCONNECT with cause number 42.
DISCONNECT message: As in subclause 33.2.3.1 with cause value #42 "Switching equipment congestion" (0101010). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.6.2 Requirements | 1) According to subclause "Structured procedures, Mobile originating call, early assignment, Requirements", paragraphs 1) to 5).
2) After the reception of DISCONNECT a congestion tone shall be generated.
3) The congestion tone characteristics shall be as follows:
Tone
Frequency
Tolerance
Type
Congestion tone
425 Hz
15 Hz
Periodic
tone on 200 ms,
silence 200 ms |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.7 Authentication failure tone | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.7.1 Method of test | a) According to subclause "Structured procedures, Mobile originating call, early assignment, Method of test", paragraphs a) to e).
b) After reception of message AUTHENTICATION RESPONSE the SS sends message AUTHENTICATION REJECT.
Message: AUTHENTICATION REJECT (3GPP TS 04.08 / 3GPP TS 24.008, 9.2.1) to the MS:
Information element
Comment
Protocol discriminator
MM
Transaction identifier
not relevant
Message type |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.7.2 Requirements | 1) According to subclause "Structured procedures, Mobile originating call, early assignment, Requirements", paragraphs 1) to 4).
2) After reception of AUTHENTICATION REJECT a tone shall be generated indicating authentication failure.
3) The authentication failure tone is the error/special information tone with characteristics as follows:
Tone
Frequency
Tolerance
Type
Error/Special
950 Hz
50 Hz
Triple tone
Information tone
1400 Hz
50 Hz
tones on 330 ms
1800 Hz
50 Hz
silence 1,0 s |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.8 Number unobtainable tone | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.8.1 Method of test | a) According to subclause "Structured procedures, Mobile originating call, early assignment, Method of test", paragraphs a) to h).
b) The SS then sends message DISCONNECT with cause number 1.
DISCONNECT message: As in subclause 33.2.3.1 with cause value #1 "Unassigned (unallocated) number" (0000001). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.8.2 Requirements | 1) According to subclause "Structured procedures, Mobile originating call, early assignment, Requirements", paragraphs 1) to 5).
2) After reception of DISCONNECT a tone shall be generated indicating that the called number is unobtainable.
The number unobtainable tone is the error/special information tone with characteristics as in subclause 33.2.7.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.9 Call dropped tone | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.9.1 Method of test | a) According to subclause "Structured procedures, Mobile originating call, early assignment, Method of test", paragraphs a) to l). However, it shall be indicated in the system information messages that call re-establishment shall not be attempted (RACH control parameters).
b) When the call has been established the SS stops transmitting on the TCH/SACCH. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.2.9.2 Requirements | 1) According to subclause "Structured procedures, Mobile originating call, early assignment, Requirements", paragraphs 1) to 8).
2) After the radio link time-out period has expired a tone shall be generated indicating that the call has been dropped.
The call dropped tone characteristics shall be as follows:
Tone
Frequency
Tolerance
Type
Call dropped tone
425 Hz
15 Hz
Tone on 200 ms,
silence 200 ms
3 bursts of on/off |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3 Network selection / indication | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.1 Definition | Network selection and indication is the ability of the MS to correctly select a network and display to the user in accordance with 3GPP TS 02.11 and 3GPP TS 03.22.
Tests concerning the MS behaviour after having received a location updating reject message with specific causes are included in subclause 26.7.4.2.
Tests concerning the MS handling of the forbidden PLMN list are also included in subclause 26.7.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.2 Conformance requirement | 1) Upon switching on, when an IMSI is available and there is no registered PLMN on the SIM, the MS shall select its Home PLMN and perform the cell selection procedure.
2) If the MS loses radio coverage for its registered PLMN, and the MS is in automatic PLMN selection mode, it shall attempt to select its Home PLMN.
3) If the Registered PLMN is unavailable due to the loss of radio coverage and the MS is in automatic PLMN selection mode and the HPLMN is also unavailable, it shall attempt to select a suitable cell and access the PLMNs in turn, in the order of priority as stored in the SIM.
4) If there is no registered PLMN in the SIM or the registered PLMN is unavailable and If the Home PLMN is unavailable and the MS is in automatic PLMN selection mode, it shall attempt to select a suitable cell and accesses the PLMNs in turn, in the order of priority as stored in the SIM, upon switching on and when the IMSI is available.
5) An MS, roaming in a VPLMN whose MCC is the same as the MCC of the IMSI, shall periodically attempt to obtain service on its Home PLMN in automatic mode. For this purpose, a value T minutes, which is the HPLMN search period, may be stored in the SIM; T is either in the range 6 minutes to 8 hours in 6 minutes step or it indicates that no periodic attempt shall be made. If no HPLMN search value is available on the SIM the mobile equipment shall use a default value of 30 minutes.
6) At switch on, the MS selects and attempts to perform a Location Update on the Registered PLMN if it exists. If the registered PLMN is a VPLMN of the SIM's home country, the MS shall wait at least 2 minutes before attempting to obtain service on its home PLMN. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.3 Test purpose | 1) To verify that the MS with SIM containing in the PLMN selector field at least one PLMN different from the Home PLMN and containing no registered PLMN, when in automatic PLMN selection mode, selects its Home PLMN, if available, upon switching on and when the IMSI is available. (This is verified by observation of the location updating procedure).(Steps 1.1 through 1.5).
2) To verify that if the MS loses radio coverage for its registered PLMN, and the MS is in automatic PLMN selection mode, it shall attempt to select its Home PLMN. (Steps 1.14C through 1.16C).
3) To verify that the MS, when it looses radio coverage for its selected PLMN (i.e. Registered PLMN) and in automatic PLMN selection mode, selects the PLMN with the highest priority among the PLMNs stored on the SIM, if the Home PLMN is unavailable. (Steps 1.10 through 1.12).
4) If there is no registered PLMN in the SIM or the registered PLMN is unavailable and If the Home PLMN is unavailable and the MS is in automatic PLMN selection mode, it shall attempt to select a suitable cell and accesses the PLMNs in turn, in the order of priority as stored in the SIM, upon switching on and when the IMSI is available. (Steps 1.22 through 1.25).
5) To verify that an MS, roaming in a VPLMN whose MCC is the same as the MCC of the IMSI, shall attempt to obtain service on its Home PLMN in automatic mode with a period of T. To verify that the MS shall not attempt to obtain service on its home PLMN in automatic mode when T is set to "no periodic attempts shall be made". To verify that a default value of 30 min is used when no HPLMN search timer value is available on the SIM. (Steps 1.13 A through 1.15A, 1.13B through 1.15B and 1.13C.)
6) To verify that, at switch on, the MS selects and attempts to perform a Location Update on the registered PLMN if it exists. If the registered PLMN is a VPLMN of the SIM's home country, the MS shall wait at least 2 minutes before attempting to obtain service on its home PLMN. (Steps 1.25 through 1.28).
Reference
Requirements 1, 2, 3: see 3GPP TS 03.22 subclause 4.4.3.1.
Requirements 4: see 3GPP TS 03.22 subclause 3.1.
Requirement 5, 6: see 3GPP TS 03.22 subclause 4.4.3.3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.4 Method of Test | Procedure 1: This procedure applies to both automatic and manual mode for PLMN selection. This procedure is run for each of the following cases:
case A) Timer T is set to 6 min in the SIM.
case B) No HPLMN search timer value is available on the SIM.
case C) Timer T is set to "no periodic attempt to obtain service on the HPLMN shall be made" in the SIM.
Procedure 2: This procedure applies to the manual mode for PLMN selection.
Specific PICS Statements
• Country PLMN/Indication (TSPC_Feat_PLMNind)
PIXIT Statements
• |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.4.1 Procedure 1 | 1.1) The MS is set up with a SIM which contains, in the "PLMN selector" data field, a list of 3 PLMN in the priority order PLMN2 (highest priority), PLMN3, PLMN4 (lowest priority). PLMN1 is the Home PLMN of the MS as defined in the IMSI. The "Forbidden PLMN" data field shall contain NULL values. "registered PLMN" data field shall contain Null values.
case A) Timer T is set to 6 min in the SIM.
case B) No HPLMN search timer value is available on the SIM.
case C) Timer T is set to "no periodic attempt to obtain service on the HPLMN shall be made" in the SIM.
1.2) The SS transmits 4 BCCH carriers with the following parameters:
PLMN
Level dBVemf( )
Carrier 1
PLMN1 any value for MCC
28
Carrier 2
PLMN2 any value for MCC
33
Carrier 3
PLMN3 with the same MCC as PLMN1
38
Carrier 4
PLMN4 any value for MCC
43
Each carrier has the "IMSI attach" (ATT) flag set in the BCCH data. (The purpose of this is to force the MS to do location updating whenever it is switched on, so that the SS can determine which PLMN has been selected).
The other system information parameters are as in table 33-1.
1.3) The MS is brought into the "on" condition with automatic selection mode active.
1.4) The SS checks that the MS sends a "location updating request" on carrier 1.
1.5) The SS sends a "location updating accept" message to the MS on carrier 1. After 5 s, the MS "selected PLMN indicator" is checked.
1.6) The SS switches off carriers 1.
1.7) The SS checks that the MS sends a "location updating request" on carrier2.
1.8) The SS sends a "location updating accept" message to the MS on carrier 2. After 5 s, the MS "selected PLMN indicator" is checked.
1.9) Carrier 2 is turned off.
1.10) The SS checks that the MS sends a "location updating request" on carrier 3.
1.11) The SS sends a "location updating accept" message on carrier 3. After 5 s, the MS "selected PLMN indicator" is checked.
1.12) Carriers 1 and 2 are turned on with the same parameters as in step 1.2) above.
In case A for which T is set to 6 min, take branch A.
In case B for which default value for T is applied take branch B.
In case C for which T is set to "no periodic attempt shall be made", take branch C.
Branch A
1.13A) The SS checks that the MS does not send a "location updating request" on either carrier 1 or 2during 6 minutes after step 1.11 is completed.
1.14A) The SS checks that the MS sends a "location updating request" on channel 1 between 6 and 12 min after step 1.11 is completed.
1.15A) The SS sends a "location updating accept" message on carrier 1. After 5 s, the MS "selected PLMN indicator" is checked.
Branch B
1.13B) The SS checks that the MS does not send a "location updating request" on either carrier 1 or 2 during 30 minutes after step 1.11 is completed.
1.14B) The SS checks that the MS sends a "location updating request" on channel 1 between 30 and 60 min after step 1.11 is completed.
1.15B) The SS sends a "location updating accept" message on carrier 1. After 5 s, the MS "selected PLMN indicator" is checked.
Branch C
1.13C) The SS checks that the MS does not send a "location updating request" on either carrier 1 or 2 during 40 min.
1.14C) The SS switches off carrier 3.
1.15C) The SS checks that the MS sends a "location updating request" on channel 1.
1.16C) The SS sends a "location updating accept" message on carrier 1. After 5 s, the MS "selected PLMN indicator " is checked.
1.17) The SS switches off carrier 1 and switches on carrier 3.
1.18) The SS checks that the MS sends a "location updating request" on carrier 2.
1.19) The SS sends a "location updating accept" message on carrier 2. After 5 s, the MS "selected PLMN indicator" is checked.
1.20) The mobile station is switched off.
1.21) The SS switches off carrier 2.
1.22) The mobile station is switched on.
1.23) The SS checks that the MS sends a "location updating request" on carrier 3.
1.24) The SS sends a "location updating accept" message on carrier 3. After 5 s, the MS "selected PLMN indicator" is checked.
1.25) The MS is switched off.
1.26) The SS switches on carrier 1.
1.27) The mobile station is switched on.
1.28) The SS checks that the MS does not send a "location updating request" on carrier 1. After 2 minutes, the MS "selected PLMN indicator" is checked. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.4.2 Requirements 1 | Requirement 1.1) is mandatory for all MS. Requirements 1.2) only apply to MS capable of indicating PLMN.
1.1) The MS shall make a response as indicated in steps 1.4, 1.7, 1.10, 1.13A, 1.13B, 1.14A, 1.14B, 1.15C, 1.18, 1.23 above. In cases 1.4, 1.7, 1.10, 1.15C, 1.18 and 1.23, the MS shall respond within 30 s.
1.2) The selected PLMN shall be indicated:
End of Step
1.5
1.8
1.11
1.15A/B
1.16C
PLMN indicated:
PLMN1
PLMN2
PLMN3
PLMN1
PLMN1
End of Step
119
124
128
PLMN indicated:
PLMN2
PLMN3
PLMN3 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.4.3 Procedure 2 | 2a) The MS is set up with a SIM which contains NULL values in the "PLMN selector" data field. PLMN1 is the Home PLMN of the MS as defined in the IMSI. The "forbidden PLMN" data field shall contain PLMN3. the "registered PLMN" field is set to PLMN2.
2b) The SS transmits 4 BCCH carriers with the following parameters:
PLMN
Level dBVemf( )
Carrier 1
PLMN1
28
Carrier 2
PLMN2
33
Carrier 3
PLMN3
38
Carrier 4
PLMN4
43
Each carrier has the "IMSI attach" (ATT) flag set in the BCCH data. (The purpose of this is to force the MS to do location updating whenever it is switched on, so that the SS can determine which PLMN has been selected.)
The other system information parameters are as in table 33-1.
2c) The MS is brought into the "on" condition with manual selection mode active.
2d) The SS checks that the MS sends a "location updating request" on carrier 2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.3.4.4 Requirements 2 | 2.1) The MS shall make a response as indicated in step 2d). The MS shall respond within 30 s.
Table 33-1: Normal system information fields
Parameter
Reference in 3GPP TS 04.08 / 3GPP TS 24.008 / 3GPP TS 44.018
Abbreviation
Normal setting
Cell Channel Description
10.5.2.1
-
Any values
Max retrans
10.5.2.17
-
1
Tx-integer
10.5.2.17
-
Any value
CELL_BAR_ACCESS
10.5.2.17
CBA
0 (i.e. no barred)
AC CN
10.5.2.17
AC
All 0
RE
10.5.2.17
RE
0 (i.e. re-establishment allowed)
BA ARFCN
10.5.2.13
BA
One entry equal to the ARFCN of the carrier
NCC
10.5.2.15
NCC
Any value
Cell Identity
10.5.1.1
-
Any value
MCC, MNC
10.5.1.3
PLMN
Ref. 33.3.2, 1b) and 33.3.2, 2b)
LAC
10.5.1.3
LAC
1111 (Hex)
ATT, B_AG_BLKS_RES,T3212,
10.5.2.8
-
ATT = "1"
CCCH_CONF
Other parameters any values.
BS_PA_MFRMS
10.5.2.8
BPM
5 frames
Cell Options
10.5.2.3
-
Any values
CELL_RESELECT_HYSTERESIS
10.5.2.4
CRH
10 dB
MS_TXPWR_MAX_CCH
10.5.2.4
MTMC
Maximum RF output power of MS.
RXLEV_ACCESS_MIN
10.5.2.4
RAM
-95 dBm |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4 Invalid and blocked PIN indicators | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.1 Definition | - |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.2 Conformance requirement | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.3 Test purpose | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.4.1 Initial conditions | The MS contains a SIM with the PIN enabled, and the SIM unblocking counter set to zero by previous presentation of the personal unblocking key. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.4.2 Procedure | a) The MS is switched on.
b) Three wrong PIN are entered.
Activation may be either manual or via the EMMI. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.4.5 Test requirements | For the first and second incorrect PIN the MS shall indicate that the PIN code has been rejected.
For the third incorrect PIN the MS shall indicate that the PIN is blocked. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5 Service indicator | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.1 Definition | - |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.2 Conformance requirement | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.3 Test purpose | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.4.1 Initial conditions | a) The MS is in idle mode, unregistered.
b) The SS shall emulate perfect radio conditions so that the MS is able to register and to set up or receive a call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.4.2 Procedure | a) The MS is brought in an active state by either switching it on or by inserting a SIM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.5.5 Test requirements | 1) The successful registration and the good condition shall be indicated by the MS indicator and by the SS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6 Subscription identity management | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.1 Definition | Subscription identity management is the ability of the MS to prevent the establishment of MO (except MO emergency calls) and MT calls without a valid subscription. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.2 Conformance requirement | An MS can only be operated, if a valid IMSI is present. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.3 Test purpose | 1) To verify that during an established call: either
1.1) on removal of the SIM from an MS, the MS will perform an IMSI detach; or
1.2) after removing the power source from the MS, removing the SIM, and restoring the power source to the MS, the MS may perform an IMSI detach.
2) To verify that an MS without SIM card will not establish a MO call which is not an emergency call.
3) To verify that an MS without SIM card will not accept an incoming call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.4.1 Initial conditions | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.4.2 Procedure | a) A call is set up.
b) (Reserved).
c) Either:
(i) the SIM is removed; or
(ii) where this is not possible, the power source is removed from the MS, the SIM is removed and the power source is restored to the MS.
The SS observes whether or not the MS performs IMSI detach.
d) An attempt to establish a MO call is made (not an emergency call).
e) An attempt to establish a MT call is made. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.6.5 Test requirements | 1) Either:
1.1) in step c(i), the MS may send disconnect and shall perform an IMSI detach; or
1.2) in step c(ii), the MS sends nothing when power source is removed.
The MS may perform an IMSI detach when power is restored.
2) In step d) the MS shall not attempt to set up a new call via the Um interface.
3) In step e) the MS shall not respond to the attempt to set up a new call via the Um interface. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7 Barring of outgoing calls | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.1 Definition | The barring of outgoing calls is an optional feature. It is the ability of the MS to prevent all MO calls except emergency calls. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.2 Conformance requirement | An MS may have an optional facility to bar outgoing calls. Such barring facility shall not prevent the transmission on emergency calls. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.3 Test purpose | To verify that an MS for which a local facility to bar outgoing calls has been declared as being implemented, is able to establish an emergency call if this facility is activated. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.4.1 Initial conditions | Void. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.4.2 Procedure | a) The local facility to bar outgoing calls is activated.
b) Via MMI, the MS is actioned to establish an emergency call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.7.5 Test requirements | 1) The MS shall establish an emergency call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8 Prevention of unauthorized calls | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.1 Definition | The prevention of unauthorized calls is an optional feature in the MS. It is the ability of the MS to prevent unauthorized use by using a key or keyword protection facility. When activated the MS does not prevent the establishment of except emergency calls. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.2 Conformance requirement | An MS may have an optional facility to prevent unauthorized use. Such facility shall not prevent the transmission on emergency calls. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.3 Test purpose | To verify that an MS for which a local facility to prevent unauthorized use has been declared to be implemented, is able to establish an emergency call, if this facility is activated. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.4.1 Initial conditions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.4.2 Procedure | a) The local facility to restrict operation such that the MS can only be operated by using a key or a keyword is activated. The most restrictive situation is created.
b) Via MMI, the MS is actioned to establish an emergency call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 33.8.5 Test requirements | 1) The MS shall establish an emergency call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34 Short message service (SMS) | Ref.: 3GPP TS 03.40, 3GPP TS 04.11 (point to point)
3GPP TS 03.41, 3GPP TS 04.12 (cell broadcast) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.1 General | The purpose of these tests is to verify that the MS can handle GSM functions when submitting or receiving Short Messages (SM) between MS and a short message service centre as described in 3GPP TS 03.40.
The procedures are based upon services provided by the Mobility Management (MM) sublayer which is not tested in this case.
The SMS comprises three basic services. The SMS point to point services shall work in an active MS at any time independent of whether or not there is a speech or data call in progress. The SMS cell broadcast service only works when the MS is in idle mode.
The manufacturer shall declare whether SMS messages are stored in the SIM and/or the ME. This shall be referred to as the SMS message store in the following tests.
A timeout of 60s is applied throughout the tests with respect to the retransmission of CP-Data messages. This timeout is based on the maximum TR1M + 15s. The 15s is sufficient time to verify that the MS does not initiate more than the maximum number of retransmissions.
Unless otherwise stated default message contents from subclause 26.6.14 applies for GSM 900 and default message contents from subclause 26.6.15 applies for DCS 1 800 and default message contents from subclause 26.6.16 applies for GSM 450 and default message contents from subclause 26.6.17 applies for GSM 480 and default message contents from subclause 26.6.18 applies for PCS 1 900 and default message contents from subclause 26.6.19 applies for GSM 750 and default message contents from subclause 26.6.20 applies for GSM 850 and default message contents from subclause 26.6.21 applies for GSM 710 and default message contents from subclause 26.6.22 applies for T-GSM 810.
For the test cases in section 34.4 the default message contents shall be set as in "GPRS default conditions" clause 40. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2 Short message service point to point | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.1 SMS mobile terminated | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.1.1 Conformance requirements | An active MS shall be able to receive short message TPDU (SMS-DELIVER) at any time, independently of whether or not there is a speech or data call in progress. A report will always be returned to the SC, confirming that the MS has received the short message.
Reference
3GPP TS 03.40; 3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.1.2 Test purpose | To verify the ability of a MS to receive and decode the SMS where provided for the point to point service. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.1.3 Method of test | Initial Conditions
System simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in "Idle, updated" state.
The SMS message storage shall be empty.
Specific PICS Statements:
- SMS messages are stored in the SIM (TSPC_AddInfo_StoreRcvSMSSIM).
- SMS messages are stored in the ME (TSPC_AddInfo_StoreRcvSMSME).
PIXIT Statements:
- Description of the basic procedures to display a mobile terminated short message.
- Support for call control state U10.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) The SS initiates the transmission of a short message using a paging request. Upon response of the MS to the paging the SS assigns an SDCCH, authenticates the MS and activates ciphering. Then the SS establishes SAPI 3 by sending a SABM frame with SAPI 3 on the SDCCH.
When a UA frame (SAPI 3) is received in response, the SS sends a CP-DATA message. The information element of the CP-DATA message will be RP-DATA RPDU (SMS DELIVER TPDU).
b) The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
c) The SS sends a CP-ACK to the MS with no further CP-DATA messages and the SS initiates channel release.
d) Steps a), b) and c) are repeated but the first CP-DATA message from the MS is not acknowledged. The second CP-DATA message from the MS is acknowledged by a CP-ACK.
e) Steps a) and b) are repeated. The SS is configured not to send CP-ACK. Then maximum 3 CP‑DATA retransmissions may occur. The SS ensures that the MS disconnects the link within 60 s after the first CP-DATA not acknowledged by the SS. The 60 s is sufficient time to wait to verify that the MS does not send more than the maximum allowed (3) CP-DATA retransmissions.
f) The SMS message store shall be cleared manually by the operator.
g) A data or speech call is established on a TCH with the SS and the state U10 of call control is entered. The SS sends a SABM frame with SAPI-3 on the SACCH associated to the TCH.
When a UA frame (SAPI-3) is received in response, the SS sends a CP-DATA message. The information element of the CP-DATA message will be RP-DATA RPDU (SMS DELIVER TPDU). The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
h) The SS sends a CP-ACK to the MS with no further CP-DATA messages and the SS initiates channel release. The SMS message store shall be cleared manually by the operator.
i) Steps g) and h) are repeated but the first CP-DATA message from the MS is not acknowledged. The second CP-DATA message from the MS is acknowledged by a CP-ACK.
j) Step g) is repeated. The SS is configured not to send CP-ACK. Then maximum 3 CP-DATA retransmissions may occur. After a duration of 60 s after the first CP-DATA not acknowledged the SS initiates the channel release. The 60 s is sufficient time to wait to verify that the MS does not send more than the maximum allowed (3) CP-DATA retransmissions (during a call in progress).
k) A data or speech call is established on a TCH with the SS and the state U10 of call control shall be entered. The SS sends a SABM frame with SAPI-3 on the SACCH associated to the TCH. After the UA response on SAPI-3, the speech call is cleared by the SS with a disconnect message. (The call clearing is continued on the FACCH in parallel to the following exchange of messages related to SMS).
The SS sends a CP-DATA RPDU (SMS DELIVER TPDU) message. The information element of the CP-DATA message is RP-DATA.
The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
The SS sends a CP-ACK to the MS with no further CP-DATA messages and the SS initiates channel release.
The SMS message store shall be cleared manually by the operator.
l) A data or speech call is established on a TCH with the SS and the state U10 of call control is entered. The SS sends a SABM frame with SAPI-3 on the SACCH associated to the TCH. After the UA response on SAPI-3, the speech call shall be cleared from the MS. (The call clearing is continued on the FACCH in parallel to the following exchange of messages related to SMS).
The SS sends a CP-DATA message. The information element of the CP-DATA message is RP‑DATA RPDU (SMS DELIVER TPDU).
The SS waits a maximum of 25 s for the CP-ACK message and then a maximum of 60 s for the CP-DATA message containing the RP-ACK RPDU.
The SS sends a CP-ACK to the MS with no further CP-DATA messages and the SS initiates channel release.
The SMS message store shall be cleared manually by the operator.
Maximum Duration of Test
20 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST
2
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
3
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
4
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
7
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
8
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
9
SS
SS starts ciphering.
10
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
11
MS -> SS
UA (SAPI=3)
MS shall respond to SABM in step 10
12
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
13
SS
Waits max 25 s for CP-ACK
14
MS -> SS
CP-ACK
15
SS
Waits max 60 s for RP-ACK RPDU
16
MS -> SS
CP-DATA
Contains RP-ACK RPDU
17
SS -> MS
CP-ACK
18
MS
There should be no further CP-DATA messages until the MS aborts the RR connection (disconnection of layer 2).
19
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
20
SS -> MS
PAGING REQUEST
21
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
22
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
23
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
24
SS -> MS
AUTHENTICATION REQUEST
25
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
26
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
27
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
28
SS
SS starts ciphering.
29
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
30
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
31
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
32
SS
Waits max 25 s for CP-ACK
33
MS -> SS
CP-ACK
34
SS
Waits max 60 s for RP-ACK RPDU
35
MS -> SS
CP-DATA
First CP-DATA from MS, contains RP-ACK RPDU
36
SS
First CP-DATA message not acknowledged by SS
37
MS -> SS
CP-DATA
Retransmitted CP-DATA from MS contains RP-ACK RPDU
38
SS -> MS
CP-ACK
Second CP_DATA message is acknowledged
39
MS
There should be no further CP-DATA messages until the MS aborts the RR connection (disconnection of layer 2).
40
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
41
SS -> MS
PAGING REQUEST
42
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
43
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
44
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
45
SS -> MS
AUTHENTICATION REQUEST
46
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
47
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
48
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
49
SS
SS starts ciphering.
50
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
51
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
52
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
53
SS
Waits max 25 s for CP-ACK
54
MS -> SS
CP-ACK
55
SS
Waits max 60 s for RP-ACK RPDU
56
MS -> SS
CP-DATA
Contains RP-ACK RPDU
57
SS
First CP-DATA message not acknowledged by SS
58
MS -> SS
CP-DATA
Retransmitted CP-DATA from MS contains RP-ACK RPDU
59
SS
Retransmitted CP-DATA message not acknowledged by SS
60
MS
Depending upon the maximum number of CP-DATA retransmissions implemented, step 58 and 59 may be repeated.
61
MS -> SS
DISC
The main signalling link is released within 60 s after the first CP-DATA message not acknowledged by SS.
62
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
63
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
64
SS -> MS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
65
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
66
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
67
SS
Waits max 25 s for CP-ACK
68
MS -> SS
CP-ACK
69
SS
Waits max 60 s for RP-ACK RPDU
70
MS -> SS
CP-DATA
Contains RP-ACK RPDU
71
SS -> MS
CP-ACK
72-1
SS -> MS
DISCONNECT
Disconnect the active call
72-2
MS -> SS
RELEASE
72-3
SS -> MS
RELEASE COMPLETE
72-4
MS
There should be no further CP-DATA messages until the MS aborts the RR connection (disconnection of layer 2)
73
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
74
MS
Clear the SMS message store
75
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
76
SS -> MS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
77
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
78
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
79
SS
Waits max 25 s for CP-ACK
80
MS -> SS
CP-ACK
81
SS
Waits max 60 s for RP-ACK RPDU
82
MS -> SS
CP-DATA
First CP-DATA from MS, contains RP-ACK RPDU
83
SS
First CP-DATA message not acknowledged by SS
84
MS -> SS
CP-DATA
Retransmitted CP-DATA message contains RP-ACK RPDU
85
SS -> MS
CP-ACK
Second CP-DATA message is acknowledged
86-1
SS -> MS
DISCONNECT
Disconnect the active call
86-2
MS -> SS
RELEASE
86-3
SS -> MS
RELEASE COMPLETE
86-4
MS
There should be no further CP-DATA messages until the MS aborts the RR connection (disconnection of layer 2)
87
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
88
MS
Clear the SMS message store
89
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
90
SS -> MS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
91
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
92
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
93
SS
Waits max 25 s for CP-ACK
94
MS -> SS
CP-ACK
95
SS
Waits max 60 s for RP-ACK RPDU
96
MS -> SS
CP-DATA
First CP-DATA from MS, contains RP-ACK RPDU
97
SS
First CP-DATA message not acknowledged by SS
98
MS -> SS
CP-DATA
Transmitted CP-DATA message contains RP-ACK RPDU
99
SS
Retransmitted CP-DATA message not acknowledged by SS
100
MS
Depending on the maximum number of CP-DATA retransmissions implemented, step 98-99 may be repeated. The maximum number of retransmissions may however not exceed three.
101
SS -> MS
CHANNEL RELEASE
The main signalling link is released after a duration of 60 s after the first CP-DATA message not acknowledged by SS.
102
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
103
MS
Clear the SMS message store
104
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
105
SS -> MS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
106
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
107
SS -> MS
DISCONNECT
The speech call is cleared by the SS. The call clearing is continued on the FACCH in parallel to the following exchange of messages related to SMS.
108
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
109
SS
Waits max 25 s for CP-ACK
110
MS -> SS
CP-ACK
111
SS
Waits max 60 s for RP-ACK RPDU
112
MS -> SS
CP-DATA
Contains RP-ACK RPDU
113
SS -> MS
CP-ACK
114
MS
There should be no further CP-DATA messages until the MS aborts the RR connection (disconnection of layer 2).
115
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
116
MS
Clear the SMS message store
117
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
118
SS -> MS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
119
MS -> SS
UA (SAPI=3)
The MS shall respond to the SABM
120
MS -> SS
DISCONNECT
The speech call is cleared from the MS.
121
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
122
SS -> MS
RELEASE
This message is likely to be sent on the FACCH before all of the CP-DATA message has been sent on the SACCH.
123
MS -> SS
RELEASE COMPLETE
124
MS -> SS
CP-ACK
shall be sent before 25 s after the start of step 121
125
SS
Waits max 60 s for RP-ACK RPDU
126
MS -> SS
CP-DATA
Contains RP-ACK RPDU
127
SS -> MS
CP-ACK
128
MS
There should be no further CP-DATA messages until the MS aborts the RR connection (disconnection of layer 2).
129
MS
The MS shall indicate that an SM has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed
130
MS
Clear the SMS message store
NOTE: Time values for SS wait time are chosen sufficiently high to be sure that the MS has enough time to respond to the different messages.
Specific Message Contents:
SMS DELIVER TPDU
Information element
Comment Value
TP-MTI
SMS DELIVER "00"B
TP-MMS
more messages are waiting in SC "0"B
TP-RP
no reply path "0"B
TP-UDHI
TP-UD contains only the SM "0"B
TP-SRI
no status report returned "0"B
TP-OA
an international number coded E.164
TP-PID
default "00000000"B
TP-DCS
default alphabet "00000000"B
TP-SCTS
any legal value (cf. 3GPP TS 03.40)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters)
NOTE: The 160 characters shall include at least one occurrence of each character in the default alphabet (see 3GPP TS 03.40 annex 2). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.2 SMS mobile originated | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.2.1 Conformance requirements | An active MS shall be able to submit short message TPDU (SMS-SUBMIT) at any time, independently of whether or not there is a speech or data call in progress.
Reference
3GPP TS 03.40; subclause 3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.2.2 Test purpose | To verify that the MS is able to correctly send a short message where the SMS is provided for the point to point service. The test also verifies that the MS is capable of simultaneously receive a network originated SM whilst sending a mobile originated SM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.2.3 Method of test | Initial Conditions
System simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in "Idle, updated" state.
The SMS message storage shall be empty.
Specific PICS Statements
- SMS messages are stored in the SIM (TSPC_AddInfo_StoreRcvSMSSIM).
- SMS messages are stored in the ME (TSPC_AddInfo_StoreRcvSMSME).
PIXIT Statements
- Description of the basic procedures to display a mobile originated short message.
- Support for call control state U10.
- Maximum length (characters) of a mobile originated short message.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) The MS shall be set up to send a SM to the SS. The SS responds to the channel request message by allocating an SDCCH. The SS answers correctly to the SABM on SAPI 0 and then performs the authentication and ciphering procedures.
b) The SS responds with a UA frame SAPI-3 to the MS.
c) The SS responds to the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS with a CP-ACK message followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for the CP-ACK message.
d) The SS sends a channel release message to the MS.
e) Steps a) and b) are repeated. The SS is configured not to send the CP-ACK message. Then maximum 3 CP-DATA retransmissions may occur. The SS ensures that the MS disconnects the link within 60 s after the first CP-DATA not acknowledged by the SS. The 60 s is sufficient time to wait to verify that the MS does not send more than the maximum CP-DATA retransmissions and that TR1M has expired.
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
f) Steps a) and b) are repeated. On receipt of the CP-DATA from the MS the SS sends a CP-ERROR message containing a "Network Failure" cause. Then the SS initiates channel release.
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
g) A data or speech call is established on a TCH with the SS and the state U10 of call control is entered. The MS is setup to send an SM to the SS. After the reception of the CM SERVICE REQUEST, the SS sends a CM SERVICE ACCEPT message. The SS responds with a UA frame SAPI-3 to the SABM with SAPI-3 received from the MS.
h) The SS responds to the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS with a CP-ACK message followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for the CP-ACK message. Then the SS sends a channel release message to the MS.
i) Step g) is repeated. The SS is configured not to send the CP-ACK message or to respond to any other CM requests. Then maximum 3 CP‑DATA retransmissions may occur. After a duration of 60 s after the first CP-DATA not acknowledged the SS initiates channel release. The 60 s is sufficient time to wait to verify that the MS does not send more than the maximum CP-DATA retransmissions (during a call in progress).
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
j) The SS is configured to receive a mobile originated SM. Steps a) and b) are repeated and, using the end of the CP-DATA message from the MS as a trigger, the SS sends a SM to the MS. In this case a new transaction identifier shall be used in the CP messages of SMS mobile terminated.
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
k) The MS is set up to send an SM to the SS. On receipt of the CM SERVICE REQUEST the SS sends a CM SERVICE REJECT message with the reject cause set to "Service Option not supported" or "Service Option temporarily out of order". After 5 s the SS initiates channel release.
Any remaining message in the outbox should be removed. All requests from the MS during this time shall be ignored.
Maximum Duration of Test
20 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
Establishment cause is “Other procedures which can be completed with an SDDCH” NECI = 0
2
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
3
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM on SAPI 0. CM service type set to "Short message transfer"
4
SS -> MS
AUTHENTICATION REQUEST
5
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
6
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
7
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
8
SS
SS starts ciphering.
9
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
10
SS -> MS
UA (SAPI=3)
11
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
12
SS -> MS
CP-ACK
13
SS -> MS
CP-DATA
Contains RP-ACK RPDU
14
SS
Waits max 25 s for CP-ACK
15
MS -> SS
CP-ACK
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
17
MS -> SS
DISC (SAPI=0)
MS shall respond to channel release with a layer 2 DISC frame with SAPI 0
18
MS -> SS
CHANNEL REQUEST
Establishment cause is “Other procedures which can be completed with an SDDCH” (NECI=0)
19
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
20
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM on SAPI 0.
21
SS -> MS
AUTHENTICATION REQUEST
22
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
23
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
24
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
25
SS
SS starts ciphering.
26
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
27
SS -> MS
UA (SAPI=3)
28
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
29
SS
SS configured not to send CP-ACK
30
MS -> SS
CP-DATA
Retransmitted CP-DATA message
31
MS
Depending on the maximum number of CP-DATA retransmissions implemented, step 30 may be repeated. The maximum number of retransmissions may however not exceed three.
31a (Optio-nal)
MS -> SS
CP-ERROR
The MS may send CP-ERROR if TR1M expires
32a
MS -> SS
DISC (SAPI = 0)
The main signalling link is released within 60 s after the first CP-DATA message not acknowledged by SS.
32b
MS
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
33
MS -> SS
CHANNEL REQUEST
Establishment cause is “Other procedures which can be completed with an SDDCH” (NECI=0)
34
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
35
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. CM service type set to "short message transfer"
36
SS -> MS
AUTHENTICATION REQUEST
37
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
38
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
39
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
40
SS
SS starts ciphering.
41
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
42
SS -> MS
UA (SAPI=3)
43
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
44
SS -> MS
CP-ERROR
Sent containing "Network Failure" cause.
45
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
45a
MS -> SS
DISC (SAPI = 0)
MS shall respond to channel release with a layer 2 DISC frame with SAPI 0.
45b
MS
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
46
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
47
MS
The MS is set up to send an SM
48
MS -> SS
CM SERVICE REQUEST
Sent in a layer 2 frame on the FACCH. CM service type set to "short message transfer"
49
SS -> MS
CM SERVICE ACCEPT
50
MS -> SS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
51
SS -> MS
UA (SAPI=3)
52
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
53
SS -> MS
CP-ACK
54
SS -> MS
CP-DATA
Contains RP-ACK RPDU
55
SS
Waits max 25 s for CP-ACK
56
MS -> SS
CP-ACK
57
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
58
MS -> SS
DISC (SAPI =0)
The MS shall respond to channel release with a layer 2 DISC frame with SAPI 0.
59
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
60
MS -> SS
CM SERVICE REQUEST
Sent in a layer 2 frame on the FACCH. CM service type set to "short message transfer"
61
SS -> MS
CM SERVICE ACCEPT
62
MS -> SS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
63
SS -> MS
UA (SAPI=3)
64
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
65
SS
SS configured not to send CP-ACK
66
MS -> SS
CP-DATA
Transmitted CP-DATA message
67
MS
Depending on the maximum number of CP-DATA retransmissions implemented, step 66 may be repeated. The maximum number of retransmissions may however not exceed three. Any other CM requests from the MS shall be ignored.
67a (Optio-nal)
MS->SS
CP-ERROR
The MS may send CP-ERROR if TR1M expires
68
SS -> MS
CHANNEL RELEASE
The main signalling link is released after a duration of 60 s after the first CP-DATA message not acknowledged by SS.
69
MS -> SS
DISC (SAPI =0)
The MS shall respond to channel release
69a
MS
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
70
MS -> SS
CHANNEL REQUEST
Establishment cause is “Other procedures which can be completed with an SDDCH” (NECI=0)
71
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
72
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. CM service type set to "short message transfer"
73
SS -> MS
AUTHENTICATION REQUEST
74
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
75
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
76
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
77
SS
SS starts ciphering.
78
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
79
SS -> MS
UA (SAPI=3)
80
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
81
SS
The SS sends an SM to the MS triggered by the end of the CP-DATA message from the MS
82
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
83
MS
The MS shall correctly receive the SM and indicate that a message has arrived. If the MS provides the functionality to display MT messages, it is checked that the correct message is displayed. In the MO case the MS shall send the CP-ACK message with transaction identifier assigned to this transfer. In the MT case the MS shall send a CP-ACK message and a CP-DATA message containing the RP-ACK RPDU. The transaction identifier shall be the same as chosen by the SS for the MT transfer.
83a
MS
Any remaining message in the outbox should be removed prior to the next step. All requests from the MS during this time shall be ignored.
84
MS -> SS
CHANNEL REQUEST
Establishment cause is “Other procedures which can be completed with an SDDCH” (NECI=0)
85
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
86
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. CM service type set to "short message transfer"
87
SS -> MS
CM SERVICE REJ
Reject cause set to "Service Option not supported" or "Service Option temporarily out of order"
88
MS
The MS shall not establish SAPI-3
89
SS -> MS
CHANNEL RELEASE
Sent 5 s after CM SERVICE REJ
90
MS
Any remaining message in the outbox should be removed. All requests from the MS during this time shall be ignored.
NOTE: Time values for SS wait times are chosen sufficiently high to be sure that the MS has enough time to respond to the different messages.
Specific Message Contents:
SMS SUBMIT TPDU
Information element
Comment Value
TP-MTI
SMS SUBMIT "01"B
TP-VPF
not checked
TP-RP
no reply path "0"B
TP-UDHI
not checked
TP-SRR
not checked
TP-MR
not checked
TP-RD
not checked
TP-DA
not checked (an E164 number)
TP-PID
default "00000000"B
TP-DCS
default alphabet "00000000"B
TP-VP
not checked
TP-UDL
as applicable
TP-UD (140 octets max)
maximum number of characters (text of message) as defined by the manufacturer (see PICS/PIXIT) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.3 Test of memory full condition and memory available notification: | The Memory Available Notification provides a means for the MS to notify the network that it has memory available to receive one or more short messages. The SMS status field in the SIM contains status information on the "memory available" notification flag. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.3.1 Conformance requirement | 1. When a mobile terminated message is Class 2, the MS shall ensure that the message has been transferred to the SMS data field in the SIM before sending an acknowledgement to the SC. The MS shall return a protocol error message if the short message cannot be stored in the SIM and there is other short message storage available in the MS. If all the short message storage in the MS is already in use, the MS shall return "memory capability exceeded".
2. When the MS rejects a short message due to lack of available memory capability the need to transfer notification shall be stored in the SIM.
3. If the memory capability becomes available because memory is cleared, the value of the memory capability exceeded notification flag in the SIM is read. If the flag is set, the MS notifies the network that memory capability is now available. After a positive acknowledgement from the network, the ME unsets the memory capability exceeded notification flag in the SIM.
References
3GPP TS 03.40, subclause 9.2.3.10, 3GPP TS 03.38, clause 4.
3GPP TS 03.40, subclause 10.3 (operation 14).
3GPP TS 03.40, subclause 10.3 (operation 14). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.3.2 Test purpose | 1. To verify that the MS sends the correct acknowledgement when its memory in the SIM becomes full.
2. To verify that the MS sends the correct acknowledgement when its memory in the ME and the SIM becomes full, and sets the "memory exceeded" notification flag in the SIM.
3. To verify that the MS performs the "memory available" procedure when its message store becomes available for receiving short messages, and only at this moment. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.3.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS shall be in the idle updated state.
The SMS message storage shall not be full
The MS shall be connected to the SIM simulator. The following shall be present in the SIM simulator:
- EFSMS with at least one record;
- EFSMSstatus, with SMS "Memory Cap. Exceed" notification flag set to "memory available";
- Service no. 4 (SMS) in EFSST set to allocated and activated.
For storing of Class 1 Short Messages the MS shall be set up to store Short Messages in the ME memory (by way of MMI, as described in PICS/PIXIT statement).
Specific PICS Statements
- SMS messages are stored in the ME (TSPC_AddInfo_StoreRcvSMSME).
PIXIT Statements
- Description of the basic procedures to display a mobile originated short message.
- Description of the procedure to fill up MS memory (internal/external) to leave only memory for a limited number of SMS.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) step a) of subclause 34.2.5.3 (test of Class 2 Short Messages) is repeated until the MS sends a negative acknowledgement (RP-ERROR). The SIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the SIM.
b) a Class 1 Short Message is sent to the MS.
c) step b) is repeated until the MS sends a negative acknowledgement (RP-ERROR). The SIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the SIM.
d) a Short Message is sent to the MS with the DCS field of the SMS-DELIVER TPDU set to 0.
e) the SS prompts the operator to read a short message and to remove one or more messages from the message store of the MS.
f) the SS waits for a CHANNEL REQUEST from the MS, and sends an IMMEDIATE ASSIGNMENT allocating an SDCCH.
g) the SS answers correctly to the SABM on SAPI 0.
h) the SS answers correctly to the SABM on SAPI 3.
i) the SS answers to the RP-SMMA from the MS with a CP-DATA containing a RP-ACK RPDU.
j) after the MS has acknowledged the CP-DATA with a CP-ACK, the SS releases the channel with a CHANNEL RELEASE message. The SIM simulator shall indicate if the "memory capability exceeded" notification flag has been unset on the SIM.
k) step e) is repeated.
Maximum Duration of Test
-
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST
2
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
3
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
4
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
7
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
8
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
9
SS
SS starts ciphering.
10
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
11
MS -> SS
UA (SAPI=3)
12
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 2 Short Message
13
SS
Waits max 25 s for CP-ACK
14
MS -> SS
CP-ACK
15
SS
Waits max 60 s for RP-ACK RPDU
16
MS -> SS
CP-DATA
Contains RP-ACK RPDU
17
SS -> MS
CP-ACK
18
SS -> MS
CHANNEL RELEASE
The main signalling link is released. Step 1-18 is repeated until MS sends a negative acknowledgement (RP-ERROR) in step 16. The RP-ERROR RPDU cause field shall be "Protocol error, unspecified" if there is message capability in the ME, or "Memory capability exceeded" if there is no message capability in the ME. If the total memory store of the MS is full, the ME shall set the "memory capability exceeded" notification flag on the SIM.
19
SS -> MS
PAGING REQUEST
20
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
21
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
22
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
23
SS -> MS
AUTHENTICATION REQUEST
24
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
25
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
26
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
27
SS
SS starts ciphering.
28
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
29
MS -> SS
UA (SAPI=3)
30
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 1 Short Message
31
SS
Waits max 25 s for CP-ACK
32
MS -> SS
CP-ACK
33
SS
Waits max 60 s for RP-ACK RPDU
34
MS -> SS
CP-DATA
Shall contain RP-ACK RPDU if there is memory capability in the ME. If not it shall contain RP-ERROR RPDU which cause field shall be "memory capability exceeded". If the total memory store of the MS now becomes full at this step, the ME shall set the "memory cap. exceed" notification flag on the SIM.
35
SS -> MS
CP-ACK
36
SS -> MS
CHANNEL RELEASE
The main signalling link is released. Step 19-36 is repeated until the MS sends an RP-ERROR. The SIM simulator shall indicate if the "memory capability exceeded" notification flag has been set on the SIM.
37
SS -> MS
PAGING REQUEST
38
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
39
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
40
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
41
SS -> MS
AUTHENTICATION REQUEST
42
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
43
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
44
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
45
SS
SS starts ciphering.
46
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
47
MS -> SS
UA (SAPI=3)
48
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU) with TP-DCS set to 0
49
SS
Waits max 25 s for CP-ACK
50
MS -> SS
CP-ACK
51
SS
Waits max 60 s for RP-ACK RPDU
52
MS -> SS
CP-DATA
Shall contain RP-ERROR RPDU with error cause "memory capability exceeded".
53
SS -> MS
CP-ACK
54
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
55
SS
Prompts the operator to remove one or more messages from the short message store of the MS.
57
MS -> SS
CHANNEL REQUEST
Establishment cause "Other services which can be completed with an SDCCH" (NECI=0).
58
SS -> MS
IMMEDIATE ASSIGNMENT
SS allocates an SDCCH
59
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM. CM service type information element is set to "Short message transfer".
60
SS -> MS
CM SERVICE ACCEPT (UA)
SAPI 0
61
MS -> SS
SABM (SAPI=3)
MS shall establish SAPI 3
62
SS -> MS
UA (SAPI=3)
63
MS -> SS
CP-DATA
Contains RP-SMMA RPDU
64
SS -> MS
CP-ACK
65
SS -> MS
CP-DATA
Contains RP-ACK RPDU
66
MS -> SS
CP-ACK
Acknowledge of CP-DATA containing the RP-ACK RPDU. The ME shall unset the "memory capability exceeded" notification flag on the SIM.
67
SS -> MS
CHANNEL RELEASE
The main signalling link is released. The SIM simulator shall indicate if the "memory capability exceeded" notification flag has been unset on the SIM.
68
SS
Prompts the operator to remove one or more messages from the message store of the MS.
69
MS
Shall not attempt to send a RP-SMMA RPDU. This is verified by checking that the MS does not send a CHANNEL REQUEST message with the establishment cause "Other services which can be completed with an SDCCH"
NOTE: Time values for SS wait time are chosen sufficiently high to be sure that the MS has enough time to respond to the different messages.
Specific Message Contents:
SMS-DELIVER TPDU in step 12
Information element
Comment Value
TP-MTI
SMS DELIVER "00"B
TP-MMS
more messages are waiting in SC "0"B
TP-RP
no reply path "0"B
TP-UDHI
TP-UD contains only the SM "0"B
TP-SRI
no status report returned "0"B
TP-OA
an international number coded E.164
TP-PID
default "00000000"B
TP-DCS
default alphabet, class 2 "11110010"B
TP-SCTS
always set to the current time of the system simulator (cf. 3GPP TS 03.40)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters)
SMS-DELIVER TPDU in step 30
same as in step 12 except:
TP-DCS
default alphabet, class 1 "11110001"B
SMS-DELIVER TPDU in step 48
same as in step 12 except:
TP-DCS
default alphabet "00000000"B |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.4 Test of the status report capabilities and of SMS-COMMAND: | This test applies to MSs which support the status report capabilities. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.4.1 Conformance requirement | The SMS offers the SC the capabilities of informing the MS of the status of a previously sent mobile originated short message. This is achieved by the SC returning a status report TPDU (SMS-STATUS-REPORT) to the originating MS.
SMS-COMMAND enables an MS to invoke an operation at the SC.
The MS shall increment TP-MR by 1 for each SMS-SUBMIT or SMS-COMMAND being submitted.
References
3GPP TS 03.40; subclause 3.2.9.
3GPP TS 03.40; subclause 9.2.3.6. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.4.2 Test purpose | 1) To verify that the MS is able to accept a SMS-STATUS-REPORT TPDU.
2) To verify that the MS is able to use the SMS-COMMAND functionality correctly and sends an SMS-COMMAND TPDU with the correct TP-Message-Reference. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.4.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in the idle updated state.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) The MS is made to send a Mobile Originated short message as in steps a) to d) of test 34.2.2 (SMS Mobile originated).
b) The SS establishes a data link on SAPI-3 with the MS, then sends a CP-DATA message containing a RP-DATA RPDU itself containing an SMS-STATUS-REPORT TPDU.
c) The SS sends a CHANNEL RELEASE message.
d) The MS is made to send an SMS-COMMAND message enquiring about the previously submitted short message.
e) The SS responds to the MS so as to enable it to establish a data link on SAPI-3 on an SDCCH.
f) The SS acknowledges the CP-DATA message from the MS with a CP-ACK followed by a CP-DATA message containing an RP-ACK RPDU.
g) After receiving the CP-ACK from the MS, the SS releases the channel by using a CHANNEL RELEASE message.
h) The MS is made to send an SMS-COMMAND message requiring to delete the previously submitted short message.
i) steps e) to g) are repeated.
Maximum Duration of Test
-
Expected Sequence
Step
Direction
Message
Comments
1
MS -> SS
CHANNEL REQUEST
Establishment cause is "Other procedures which can be completed with an SDCCH " (NECI=0)
2
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
3
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
4
SS -> MS
AUTHENTICATION REQUEST
5
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
6
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
7
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
8
SS
SS starts ciphering.
9
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
10
SS -> MS
UA (SAPI=3)
11
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
12
SS -> MS
CP-ACK
13
SS -> MS
CP-DATA
Contains RP-ACK RPDU
14
SS
Waits max 25 s for CP-ACK
15
MS -> SS
CP-ACK
16
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
17
SS -> MS
PAGING REQUEST
18
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
19
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
20
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
22
SS -> MS
AUTHENTICATION REQUEST
23
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
24
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
25
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
26
SS
SS starts ciphering.
27
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
28
MS -> SS
UA (SAPI=3)
29
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS-STATUS-REPORT TPDU)
30
MS -> SS
CP-ACK
31
MS -> SS
CP-DATA
Contains RP-ACK RPDU
32
SS ->MS
CP-ACK
33
SS -> MS
CHANNEL RELEASE
34
MS
The MS is made to send an SMS-COMMAND message enquiring about the previously submitted SM
35
MS -> SS
CHANNEL REQUEST
Establishment cause "Other services which can be completed with an SDCCH".
36
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
37
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
38
SS -> MS
AUTHENTICATION REQUEST
39
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
40
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
41
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
42
SS
SS starts ciphering.
43
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
44
SS -> MS
UA (SAPI=3)
45
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS-COMMAND TPDU) which shall contain the correct TP-MR
46
SS -> MS
CP-ACK
47
SS -> MS
CP-DATA
Contains RP-ACK RPDU
48
MS -> SS
CP-ACK
49
SS -> MS
CHANNEL RELEASE
50
MS
The MS is made to send an SMS-COMMAND
message requiring to delete the previously submitted SM.
51
MS -> SS
CHANNEL REQUEST
Establishment cause "Other services which can be completed with an SDCCH".
52
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
53
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
54
SS -> MS
AUTHENTICATION REQUEST
55
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
56
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
57
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
58
SS
SS starts ciphering.
59
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
60
SS -> MS
UA (SAPI=3)
61
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS-COMMAND TPDU) which shall contain the correct TP-MR
62
SS -> MS
CP-ACK
63
SS -> MS
CP-DATA
Contains RP-ACK RPDU
64
MS -> SS
CP-ACK
65
SS -> MS
CHANNEL RELEASE
Specific Message Contents:
SMS SUBMIT TPDU
Information element
Comment Value
TP-MTI
SMS SUBMIT "01"B
TP-VPF
not checked
TP-RP
no reply path "0"B
TP-UDHI
not checked
TP-SRR
status report is requested "1"B
TP-MR
not checked
TP-RD
not checked
TP-DA
not checked (an E164 number)
TP-PID
default "00000000"B
TP-DCS
default alphabet "00000000"B
TP-VP
not checked
TP-UDL
as applicable
TP-UD (140 octets max)
maximum number of characters
SMS-STATUS-REPORT TPDU (SS to MS in step 29):
Information element
Comment Value
TP-MTI
SMS-STATUS-REPORT "10"B
TP-MR
same as previous SMS-SUBMIT
TP-MMS
no more messages "1"B
TP-SRQ
result of SMS-SUBMIT "0"B
TP-RA
same as the Destination address of the SMS-SUBMIT
TP-SCTS
any legal value (cf. 3GPP TS 03.40)
TP-DT
any legal value (cf. 3GPP TS 03.40)
TP-ST
SM received "00000000"B
first SMS-COMMAND TPDU (MS to SS in step 44)
Information element
Comment Value
TP-MTI
SMS-COMMAND "10"B
TP-MR
TP-MR in previous SMS-SUBMIT plus "1"
TP-SRR
status report requested (3GPP TS 03.40 9.2.3.19) "1"B
TP-PID
default "00000000"B
TP-CT
Enquiry relating to previously submitted
short message "00000000"B
TP-MN
not checked (TP-MR in previous SMS-SUBMIT)
TP-DA
not checked (an E164 number)
TP-CDL
not checked
TP-CD
not checked
second SMS-COMMAND TPDU (MS to SS in step 60)
Information element
Comment Value
TP-MTI
SMS-COMMAND "10"B
TP-MR
TP-MR in previous SMS-COMMAND plus "1"
TP-SRR
status report not requested "0"B
TP-PID
default "00000000"B
TP-CT
Delete previously submitted short message "00000010"B
TP-MN
not checked (TP-MR in previous SMS-SUBMIT)
TP-DA
not checked (an E164 number)
TP-CDL
not checked
TP-CD
not checked |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5 Test of message class 0 to 3 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.1 Short message class 0 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.1.1 Conformance requirement | When a mobile terminated message is class 0 and the MS has the capability of displaying short messages, the MS shall display the message immediately and send an acknowledgement to the SC when the message has successfully reached the MS irrespective of whether there is memory available in the SIM or ME. The message shall not be automatically stored in the SIM or ME.
References
3GPP TS 03.38, clause 4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.1.2 Test purpose | To verify that the MS will accept and display but not store a class 0 message, and that it will accept and display a class 0 message if its message store is full.
NOTE: failure of this test in a mobile could cause it to reject a class 0 message when its SMS memory becomes full. This could lead to unwanted repetitions between the MS and the service centre. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in the idle updated state.
The MS message store shall be empty.
Specific PICS Statements
- SMS messages are stored in the SIM (TSPC_AddInfo_StoreRcvSMSSIM).
- SMS messages are stored in the ME (TSPC_AddInfo_StoreRcvSMSME).
PIXIT Statements
- Description of the basic procedures to display a mobile terminated short message.
- Description of the procedure to fill up all MS memory (internal/external) to leave only memory for a limited number of SMS.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) The SS sends a class 0 message by using the method described in step a) of subclause 34.2.1 but with the TPDU described in this subclause.
b) The MS message store shall be filled (for example by using the method of 34.2.3 test of the memory available notification) with the same SMS-DELIVER TPDU except that TP-DCS is set to class 1.
c) The SS sends a class 0 message as in step a).
Maximum Duration of Test
-
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
PAGING REQUEST
2
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
3
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
4
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
7
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
8
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
9
SS
SS starts ciphering.
10
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
11
MS -> SS
UA (SAPI=3)
12
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 0 Short Message
13
MS -> SS
CP-ACK
14
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
15
SS -> MS
CP-ACK
16
SS -> MS
CHANNEL RELEASE
17
MS
The content of the short message shall be displayed by the ME. The MS shall not store the message. This can be checked by verifying that it is impossible to retrieve any short messages from the MS message store.
18
SS
The MS message store shall be filled (for example by using the method of 34.2.3) with Class 1 SMS-DELIVER TPDU.
19
SS -> MS
PAGING REQUEST
20
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
21
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
22
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
23
SS -> MS
AUTHENTICATION REQUEST
24
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
25
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
26
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
27
SS
SS starts ciphering.
28
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
29
MS -> SS
UA (SAPI=3)
30
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU), Class 0 Short Message
31
MS -> SS
CP-ACK
32
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
33
SS -> MS
CP-ACK
34
SS -> MS
CHANNEL RELEASE
35
MS
The content of the short message shall be displayed by the ME.
Specific Message Contents:
SMS-DELIVER TPDU (containing a class 0 message) (SS to MS):
Information element
Comment Value
TP-MTI
SMS-DELIVER "00"B
TP-MMS
more messages are waiting in SC "0"B
TP-RP
no reply path "0"B
TP-UDHI
TP-UD contains only the SM "0"B
TP-SRI
no status report returned 0
TP-OA
an international number coded E.164
TP-PID
default "00000000"B
TP-DCS
default alphabet, class 0 “1111 0000"B
TP-SCTS
any legal value (cf. 3GPP TS 03.40)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters)
SMS-DELIVER TPDU (containing a class 1 message to fill the MS message store) (SS to MS):
Information element
Comment Value
TP-MTI
SMS-DELIVER "00"B
TP-MMS
more messages are waiting in SC "0"B
TP-RP
no reply path "0"B
TP-UDHI
TP-UD contains only the SM "0"B
TP-SRI
no status report returned 0
TP-OA
an international number coded E.164
TP-PID
default "00000000"B
TP-DCS
default alphabet, class 1 "1111 0001"B
TP-SCTS
any legal value (cf. 3GPP TS 03.40)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.