hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.2 Test of class 1 short messages | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.2.1 Conformance requirement | When a mobile terminated message is class 1, the MS shall send an acknowledgement to the SC when the message has successfully reached the MS and can be stored, either in the ME or in the SIM.
References
3GPP TS 03.38, clause 4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.2.2 Test purpose | This procedure verifies that the MS acts correctly on receiving a class 1 message, i.e. that it stores the message in the ME or SIM and sends an acknowledgement (at RP and CP-Layer). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.2.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 not be full.
For storing of class 1 Short Messages, the MS shall be set up to store Short Messages in the ME memory if supported, otherwise the message may be stored in the SIM (by way of MMI, as described in PICS/PIXIT statement).
Specific PICS Statements
- Support for Short message MT/PP (TSPC_Serv_TS21).
- 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.
-
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) the SS delivers a Short Message of class 1 to the MS as specified in subclause 34.2.1, step a).
b) the Short Message is recalled (e.g. by means of the MMI).
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 1 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 short message shall be recalled and displayed at the MS.
Specific Message Contents:
SMS-DELIVER TPDU (containing a class 1 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 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) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.3 Test of class 2 short messages | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.3.1 Definition | Class 2 Short Messages are defined as SIM specific, and the MS shall ensure that a message of this class is stored on the SIM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.3.2 Conformance requirement | When a mobile terminated message is Class 2, the MS shall ensure that the message has been correctly transferred to the SMS data field in the SIM before sending an acknowledgement to the SC. The MS shall return a "protocol error, unspecified" error message if the short message cannot be stored in the SIM and there is other short message storage available at the MS. If all the short message storage at the MS is already in use, the MS shall return "memory capacity exceeded".
Reference(s)
3GPP TS 03.40, subclause 9.2.3.10; 3GPP TS 03.38, clause 4; 3GPP TS 11.11, subclause 10.3.3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.3.3 Test purpose | This procedure verifies that the MS acts correctly on receiving a class 2 message, i.e. that it stores the message correctly in the SIM, and if this is not possible, returns a protocol error message, with the correct error cause, to the network.
There are 2 cases:
1) If the MS supports storing of short messages in the SIM and in the ME, and storage in the ME is not full, and the short message cannot be stored in the SIM, the error cause shall be "protocol error, unspecified".
2) If the MS supports storing of short messages in the SIM and not in the ME, and storage in the ME is not full, and the short message cannot be stored in the SIM, the error cause shall be "memory capacity exceeded".
NOTE: If the MS supports storing of short messages in the SIM and the ME, and storage in the ME is full, and the short message cannot be stored in the SIM, the error cause shall be "memory capacity exceeded". This case is not tested in this test. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.3.4 Test method | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in the idle updated state.
The ME message store shall be empty.
The ME shall be connected to the SIM simulator. The following shall be present in the SIM simulator:
- EFSMS with at least two free records and one full 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
- Support for Short message MT/PP (TSPC_Serv_TS21).
- SMS messages are stored in the SIM (TSPC_AddInfo_StoreRcvSMSSIM).
- SMS messages are stored in the ME (TSPC_AddInfo_StoreRcvSMSME).
PIXIT Statements
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) the SS delivers a Short Message of class 2 to the MS as specified in subclause 34.2.1, step b).
b) following an attempt by the ME to store the short message in a free record of EFSMS in the SIM, the SIM simulator returns the status response "OK" ("90 00").
c) step a) is repeated.
d) following an attempt by the ME to store the short message in a free record of EFSMS in the SIM, the SIM simulator returns the status response "memory problem" ("92 40").
Note: the ME may retry to store the short message several times to recover the memory problem. The SIM simulator shall return the status response "memory problem" ("92 40") for each attempt, even for a different record.
e) the SIM simulator indicates if an attempt was made in steps a) and c) to store the messages and if the messages are stored according to the requirement.
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
MS -> SS
CP-ACK
14
ME
The ME shall correctly store the short message in a free record of EFSMS in the SIM, i.e. - the ME shall use a free record - the first byte of the record shall indicate "message received by MS from network"
- the TS-Service-Centre-Address shall be correctly stored
- the TPDU shall be identical to that sent by the SS
- bytes following the TPDU shall be set to "FF"
15
SIM
The SIM simulator returns the status response "OK" ("90 00"). The SIM simulator shall indicate if an attempt was made by the ME to store the short message in the SIM.
16
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
16A
SS -> MS
CP-ACK
17
SS -> MS
CHANNEL RELEASE
18
SS -> MS
PAGING REQUEST
19
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
20
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
21
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 DELIVER TPDU), Class 2 Short Message
30
MS -> SS
CP-ACK
31
ME
The ME shall attempt to store the short message in a free record of EFSMS in the SIM.
32
SIM
The SIM simulator returns the status response "memory problem" ("92 40"). The SIM simulator shall indicate if an attempt was made by the ME to store the short message in the SIM.
Note: the ME may retry to store the short message several times to recover the memory problem. The SIM simulator shall return the status response "memory problem" ("92 40") for each attempt, even for a different record.
33
MS -> SS
CP-DATA
Contains RP-ERROR RPDU with error cause "protocol error, unspecified" if the MS supports storing of short messages in the ME, or error cause "memory capacity exceeded" if not.
33A
SS -> MS
CP-ACK
34
SS -> MS
CHANNEL RELEASE
Specific Message Contents:
SMS-DELIVER TPDU (containing a class 2 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 2 "1111 0010"B
TP-SCTS
any legal value (cf. 3GPP TS 03.40)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.5.4 Test of class 3 short messages | For further study. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.6 Test of short message type 0 (Ph2, R96…R99 and REL-4) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.6.1 Conformance requirement | When a mobile terminated message is type 0, the MS shall acknowledge receipt of the short message to the SC but may discard its contents.
Note: Ideally the MS is able to receive the type 0 message irrespective of whether there is memory available in the SIM or ME and does not indicate the receipt of the type 0 short message to the user. The message should not be automatically stored in the SIM or ME.
This test shall apply to all MSs that have a Ph2, R96…R99 or REL-4 short message type 0 implementation.
References
3GPP TS 03.40 / 3GPP TS 23.040, subclause 9.2.3.9. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.6.2 Test purpose | To verify that the MS will acknowledge receipt of the short message to the SC. The MS should discard its contents.
NOTE: failure of this test in a mobile could cause it to reject a type 0 message when the network is trying to reach the MS. This could lead to unwanted repetitions between the MS and the service centre. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.6.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
The SS sends a type 0 message by using the method described in step a) of section 34.2.1 but with the TPDU described in this section.
Maximum Duration of Test
1 minute
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), type 0 Short Message
13
MS -> SS
CP-ACK
14
MS -> SS
CP-DATA
Contains RP-ACK TP-Protocol-Identifier (TP-PID).
15
SS -> MS
CP-ACK
16
SS -> MS
CHANNEL RELEASE
17
MS
Ideally the MS is able to receive the type 0 message irrespective of whether there is memory available in the SIM or ME and does not indicate the receipt of the type 0 short message to the user. The message should not be automatically stored in the SIM or ME.
Specific Message Contents:
SMS-DELIVER TPDU (containing a type 0 message) (SS to MS):
Information element
Comment Value
TP-MIT
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
Type 0: "01000000"B
TP-DCS
default alphabet “0000 0000"B
TP-SCTS
any legal value (cf. 3GPP TS 03.40 / 3GPP TS 23.040)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters)
34.2.6a Test of short message type 0 (≥ REL 5)
34.2.6a.1 Conformance requirement
When a mobile terminated message is type 0, the MS shall acknowledge receipt of the short message to the SC but shall discard its contents. This means that
- the MS shall be able to receive the type 0 short message irrespective of whether there is memory available in the SIM or ME or not,
- the MS shall not indicate the receipt of the type 0 short message to the user,
- the short message shall neither be stored in the SIM nor ME.
This test shall apply to all MSs that have a ≥ REL-5 short message type 0 implementation.
References
3GPP TS 23.040, subclause 9.2.3.9.
34.2.6a.2 Test purpose
To verify that the MS will acknowledge receipt of the short message to the SC. The MS shall discard its contents. This means that
- the MS shall be able to receive the type 0 short message irrespective of whether there is memory available in the SIM or ME or not,
- the MS shall not indicate the receipt of the type 0 short message to the user,
- the short message shall neither be stored in the SIM nor ME.
NOTE: failure of this test in a MS could cause it to reject a type 0 message when the network is trying to reach the MS. This could lead to unwanted repetitions between the MS and the service centre. In addition service affecting restrictions could happen to the customer.
34.2.6a.3 Method of test
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall be in the idle updated state.
the ME- and SIM message store shall be empty.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) The SS sends a type 0 short message by using the method described in step a) of clause 34.2.1 but with the TPDU described in this section.
b) The ME- and SIM short message store shall be filled (for example by using the method of clause 34.2.3 test of the memory available notification).
c) The SS sends a type 0 short message as in step a).
Maximum Duration of Test
5 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)
12
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU), type 0 Short Message
13
MS -> SS
CP-ACK
14
MS -> SS
CP-DATA
Contains RP-ACK TP-Protocol-Identifier (TP-PID).
15
SS -> MS
CP-ACK
16
SS -> MS
CHANNEL RELEASE
17
MS
The MS shall discard the type 0 short message. This means that the MS does not indicate the receipt of the type 0 short message to the user. The MS shall not store the message in the SIM or ME. This can be checked by verifying that it is impossible to retrieve any short messages from the ME- and SIM message store.
18
SS
The ME- and SIM message store shall be filled (for example by using the method of clause 34.2.3).
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), type 0 Short Message
31
MS -> SS
CP-ACK
32
MS -> SS
CP-DATA
Contains RP-ACK TP-Protocol-Identifier (TP-PID).
33
SS -> MS
CP-ACK
34
SS -> MS
CHANNEL RELEASE
35
MS
The MS shall discard the type 0 short message. This means that the MS does not indicate the receipt of the type 0 short message to the user. The MS shall not store the message in the SIM or ME. This can be checked by verifying that it is impossible to retrieve any short messages from the ME- and SIM message store.
Specific Message Contents:
SMS-DELIVER TPDU (containing a type 0 message) (SS to MS):
Information element
Comment Value
TP-MIT
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
Type 0: "01000000"B
TP-DCS
default alphabet “0000 0000"B
TP-SCTS
any legal value (cf. 3GPP TS 03.40 / 3GPP TS 23.040)
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.7 Test of the replace mechanism for SM type 1-7 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.7.1 Definition | This test shall apply to MSs which support:
- Replace Short Messages; and
- display of received Short Messages.
34.2.7.2a Conformance requirement for MS with implementation up to and including Rel. 97
On receipt of a short message, the MS shall check to see if the associated Protocol Identifier contains a Replace Short Message Type code. If such a code is present, then the MS will check the associated SC address (RP-OA) and originating address (TP-OA) and replace any existing stored message having the same Protocol Identifier code, SC address and originating address with the new short message.
Reference(s)
3GPP TS 03.40; subclause 9.2.3.9.
34.2.7.2b Conformance requirement for MS with implementation after Rel.98 and later
On receipt of a short message, the MS shall check to see if the associated Protocol Identifier contains a Replace Short Message Type code. If such a code is present, then the MS will check the originating address and replace any existing stored message having the same Protocol Identifier code and originating address with the new short message and other parameter values. If there is no message to be replaced, the MS shall store the message in the normal way. The MS may also check the SC address as well as the Originating Address. However, in a network which has multiple SCs, it is possible for a Replace Message type for a SM to be sent via different SCs and so it is recommended that the SC address should not be checked by the MS unless the application specifically requires such a check.
Reference(s)
3GPP TS 03.40 / 3GPP TS 23.040, subclause 9.2.3.9. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.7.3 Test purpose | This procedure verifies the correct implementation of the replace mechanism for Replace Short Messages.
NOTE: The test will not check the correct SC address for any releases. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.7.4 Test method | 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
-
PIXIT Statements
- Description of the basic procedures to display a mobile terminated short message.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) two different numbers n and m are drawn randomly between 1 and 7. Two different addresses for TP-Originating-Address (TPOA1 and TPOA2) are drawn.
b) the SS delivers a short message to the MS as specified in subclause 34.2.1 step a). In the SMS‑DELIVER TPDU, the TP-Protocol-Identifier parameter is "Replace Short Message Type n", the TP-Originating-Address is TPOA1, and the RP-Originating-Address is RPOA.
c) step b) is repeated but with a different TP-Originating-Address (TPOA2), and different contents of TP-User-Data in the SMS-DELIVER TPDU. The other parameters are the same as in step b).
d) step c) is repeated but with the TP-Protocol-Identifier equal to "Replace Short Message Type m", and contents of TP-User-Data different from the former two messages. The other parameters are the same as in step c).
e) step d) is repeated but the contents of TP-User-Data are different from that used in step d).
f) the SS prompts the operator to display the Short Messages stored in the MS.
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) TP-PID is "Replace Short Message Type n", TP-OA is TPOA1 and RP-OA is RPOA
13
MS -> SS
CP-ACK
14
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
14A
SS -> MS
CP-ACK
15
SS -> MS
CHANNEL RELEASE
16
SS -> MS
PAGING REQUEST
17
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
18
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
19
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
20
SS -> MS
AUTHENTICATION REQUEST
21
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
22
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
23
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
24
SS
SS starts ciphering.
25
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
26
MS -> SS
UA (SAPI=3)
27
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type n", TP-OA is TPOA2 and RP-OA is RPOA, TP-UD different from step 12
28
MS -> SS
CP-ACK
29
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
29A
SS -> MS
CP-ACK
30
SS -> MS
CHANNEL RELEASE
31
SS -> MS
PAGING REQUEST
32
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
33
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
34
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
35
SS -> MS
AUTHENTICATION REQUEST
36
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
37
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
38
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
39
SS
SS starts ciphering.
40
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
41
MS -> SS
UA (SAPI=3)
42
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type m", TP-OA is TPOA2 and RP-OA is RPOA, TP-UD different from step 12 and 27
43
MS -> SS
CP-ACK
44
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
45
SS -> MS
CP-ACK
46
SS -> MS
CHANNEL RELEASE
47
SS -> MS
PAGING REQUEST
48
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
49
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
50
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
51
SS -> MS
AUTHENTICATION REQUEST
52
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
53
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
54
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
55
SS
SS starts ciphering.
56
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
57
MS -> SS
UA (SAPI=3)
58
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-PID is "Replace Short Message Type m", TP-OA is TPOA2 and RP-OA is RPOA, TP-UD different from step 42
59
MS -> SS
CP-ACK
60
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
61
SS -> MS
CP-ACK
62
SS -> MS
CHANNEL RELEASE
63
SS
Prompts the operator to display the Short Messages stored in the MS. Only the Short Messages delivered in step 12, 27 and 58 shall be retrievable and displayed
Specific Message Contents:
SMS-DELIVER TPDU
Information element
Comment Value
TP-MTI
SMS-DELIVER "00"B
TP-MMS
no more messages are waiting in SC "1"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 (see test method description)
TP-PID
binary 01000xxx, xxx represents n resp. m (see test method description)
TP-DCS
default alphabet "00000000"B
TP-SCTS
the time when the message was submitted according to 3GPP TS 03.40
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters) (see test method description) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.8 Test of the reply path scheme | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.8.1 Definition | This test applies to MSs which support:
- reply procedures (the class of MSs for which this is mandatory is described in 3GPP TS 03.40, annex 4):
- displaying of received Short Messages: and
- submitting Short Messages.
Steps b) and d) are only executed for MSs which support storing of Short messages. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.8.2 Conformance requirement | When a replying MS receives an original mobile terminated short message it has:
- originating SME = TP-Originating Address in the SMS-DELIVER TPDU;
- original SC = RP-Originating Address in the RP-MT-DATA.
When submitting the reply mobile originated short message, the replying MS should use parameters as follows:
- TP-Destination Address in SMS-SUBMIT TPDU = originating SME;
- RP-Destination Address in RP-MO-DATA = original SC.
Reference(s)
3GPP TS 03.40 annex 4, clauses 5 and 6. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.8.3 Test purpose | This procedure verifies that the MS is able to send a Reply Short Message back to the correct originating SME even if in the meantime it receives another Short Message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.8.4 Test method | 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
-
PIXIT Statements
- Description of the basic procedures to display a mobile terminated short message.
- Description of the basic procedures to send a mobile originated short message.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) the SS delivers a Short Message as specified in subclause 34.2.1, step b) with TP-Reply-Path set to 1.
b) step a) is repeated but with:
- different TP-Originating-Address for the originating SME;
- different RP-Originating-Address for the original SC; and
- different message contents TP-User-Data.
c) one of the two Short Messages is displayed (e.g. by means of the MMI) and the Reply Short Message is submitted (e.g. by means of the MMI).
d) step c) is repeated for the other Short Message.
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) TP-RP set to 1
13
MS -> SS
CP-ACK
14
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
14A
SS -> MS
CP-ACK
15
SS -> MS
CHANNEL RELEASE
16
SS -> MS
PAGING REQUEST
17
MS -> SS
CHANNEL REQUEST
Establishment cause is "Answer to paging"
18
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
19
MS -> SS
PAGING RESPONSE
Message is contained in SABM.
20
SS -> MS
AUTHENTICATION REQUEST
21
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
22
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
23
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
24
SS
SS starts ciphering.
25
SS -> MS
SABM (SAPI=3)
SS establishes SAPI 3
26
MS -> SS
UA (SAPI=3)
27
SS -> MS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU) TP-OA, RP-OA and TP-UD different from step 12
28
MS -> SS
CP-ACK
29
MS -> SS
CP-DATA
Contains RP-ACK RPDU.
29A
SS -> MS
CP-ACK
30
SS -> MS
CHANNEL RELEASE
31
MS
One of the two Short Messages is displayed and the Reply Short Message is submitted.
32
MS -> SS
CHANNEL REQUEST
33
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
34
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
35
SS -> MS
AUTHENTICATION REQUEST
36
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
37
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
38
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
39
SS
SS starts ciphering.
40
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
41
SS -> MS
UA (SAPI=3)
42
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU) RP-DA = RP-OA corresponding to the message displayed TP-DA = TP-OA corresponding to the message displayed
43
SS -> MS
CP-ACK
44
SS -> MS
CP-DATA
Contains RP-ACK RPDU
45
SS
Waits max 25 s for CP-ACK
46
MS -> SS
CP-ACK
47
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
48
MS
The other Short Message is displayed and the Reply Short Message is submitted.
49
MS -> SS
CHANNEL REQUEST
50
SS -> MS
IMMEDIATE ASSIGNMENT
SS assigns an SDCCH
51
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
52
SS -> MS
AUTHENTICATION REQUEST
53
MS -> SS
AUTHENTICATION RESPONSE
SRES specifies correct value.
54
SS -> MS
CIPHERING MODE COMMAND
SS starts deciphering after sending the message.
55
MS -> SS
CIPHERING MODE COMPLETE
Shall be sent enciphered. All following messages shall be sent enciphered.
56
SS
SS starts ciphering.
57
MS -> SS
SABM (SAPI=3)
MS establishes SAPI 3
58
SS -> MS
UA (SAPI=3)
59
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU) RP-DA = RP-OA corresponding to the Message displayed TP-DA = TP-OA corresponding to the message displayed
60
SS -> MS
CP-ACK
61
SS -> MS
CP-DATA
Contains RP-ACK RPDU
62
SS
Waits max 25 s for CP-ACK
63
MS -> SS
CP-ACK
64
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
Specific Message Contents:
SMS-DELIVER TPDU
Information element
Comment Value
TP-MTI
SMS-DELIVER "00"B
TP-MMS
no more messages are waiting in SC "1"B
TP-RP
Reply Path exists "1"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 (see test method description)
TP-PID
default "00000000"B
TP-DCS
default alphabet "00000000"B
TP-SCTS
the time when the message was submitted according to 3GPP TS 03.40
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters) (see test method description) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9 Multiple SMS mobile originated | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.1 MS in idle mode | This test applies to MS supporting the ability of sending multiple short messages on the same RR connection when there is no call in progress. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.1.1 Conformance requirements | For a R99 or earlier MS only:
If another short message or a memory available notification is to be sent, an originating SMR entity in the UE may choose to continue to use the same RRC connection. When the MS chooses to use the same RR connection, then:
- the MS shall transmit a CM SERVICE REQUEST for the new CM connection before the final CP‑ACK (e.g. the one that acknowledges the CP‑DATA that carried the RP‑ACK) for the old MM connection is transmitted;
- before transmission of the first CP‑DATA on the new MM connection, the MS shall transmit the CP‑ACK for the old MM connection;
- the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and
- the MS shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.
For a Rel-4 or later MS only:
In the case of a SMS transfer via the CS domain, when the UE chooses to use the same RR or CS signalling connection, then:
- the UE shall transmit a CM SERVICE REQUEST for the new CM connection before the final CP‑ACK (i.e. the one that acknowledges the CP‑DATA that carried the RP‑ACK) for the old MM connection is transmitted;
- before transmission of the first CP‑DATA on the new MM connection, the UE may transmit the CP‑ACK for the old MM connection; the UE shall not transmit the final CP-ACK after the new CP-DATA;
- the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and
- the UE shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.
References
3GPP TS 03.40; subclause 3.1
3GPP TS 04.11; subclause 5.4
3GPP TS 04.13; subclause 5.6 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.1.2 Test purpose | To verify that the MS is able to correctly send multiple short messages on the same RR connection when using an SDCCH. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.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 how to enter multiple SMS.
- Description of the basic procedures to display a mobile originated short message.
Foreseen final state of MS
Idle, updated.
Test procedure
a) The MS shall be set up to send 3 short messages as multiple 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 Transaction Identifier used on this MM connection is 'x'.
d) the MS shall transmit a CM SERVICE REQUEST for the new CM connection (for the second short message) before the final CP-ACK (the one that acknowledges the CP-DATA that carried the RP-ACK before) for the old MM connection is transmitted. The MS shall not initiate establishment of the new MM connection before the final CP-DATA (i.e. the one carrying the RP-ACK for the first short message) has been received. Before transmission of the first CP-DATA on the new MM connection:
The MS may transmit the CP-ACK for the old MM connection. The Transaction Identifier used on the new MM connection shall be y, where y <> x (see step c)). Thereby, the UE can transmit the final CP-ACK after either the sending of the CM SERVICE REQUEST for the new CM connection or the reception of the CM SERVICE ACCEPT for the new CM connection or not to send a CP-ACK at all, thus three cases are possible. These cases are specified using two branches for the transmission of the final CP-ACK where the transmission of the final CP-ACK for the old MM connection is optional. The two branches are specified in the expected sequence table like A and B respectively. The SS waits for the UE to transmit the final CP-ACK. If received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to transmit the first CP-DATA on the new MM connection (branch A). If the final CP-ACK is not received within 5 s then the SS transmits the CM SERVICE ACCEPT and then waits for the UE to send the final CP-ACK (optional) and/or the first CP-DATA on the new MM connection (branch B).
e) Void.
f) 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.
g) The MS shall transmit a CM SERVICE REQUEST for the new CM connection (for the third short message) before the final CP-ACK (the one that acknowledges the CP-DATA that carried the RP-ACK before) for the old MM connection is transmitted. Before transmission of the first CP-DATA on the new MM connection:
The MS may transmit the CP-ACK for the old MM connection. The Transaction Identifier used on the new MM connection shall be z, where z <> y (see step c)). Thereby, the UE can transmit the final CP-ACK after either the sending of the CM SERVICE REQUEST for the new CM connection or the reception of the CM SERVICE ACCEPT for the new CM connection or not to send a CP-ACK at all, thus three cases are possible. These cases are specified using two branches for the transmission of the final CP-ACK where the transmission of the final CP-ACK for the old MM connection is optional. The two branches are specified in the expected sequence table like A and B respectively. The SS waits for the UE to transmit the final CP-ACK. If received within 5 s then the SS transmits the CM SERVICE ACCEPT and waits for the UE to transmit the first CP-DATA on the new MM connection (branch A). If the final CP-ACK is not received within 5 s then the SS transmits the CM SERVICE ACCEPT and then waits for the UE to send the final CP-ACK (optional) and/or the first CP-DATA on the new MM connection (branch B).
h) Void
i) 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.
j) The SS waits a maximum of 5 s after sending CP-DATA for the CP-ACK message from the MS.
k) The SS sends a Channel Release message to the MS.
Maximum duration of test
5 minutes.
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 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 on DCCH
10
SS -> MS
UA (SAPI=3)
11
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 11, 12, 13 and 15 shall be x.
12
SS -> MS
CP-ACK
13
SS -> MS
CP-DATA
Contains RP-ACK RPDU
14
MS -> SS
CM SERVICE REQUEST
CM service type set to "Short message transfer".
15
MS -> SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
If CP-ACK received then continue at A16.
If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 14 then goto step B16-1.
Branch A
A16
SS -> MS
CM SERVICE ACCEPT
After having sent the CM SERVICE ACCEPT then goto step 17.
Branch B
B16-1
SS->MS
CM SERVICE ACCEPT
This branch is chosen if the MS does not send a CP-ACK within 5 s of step 14.
B16-2
(optional)
MS->SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
17
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 17, 18, 19 and 21 shall be y where y <> x (see step 11).
18
SS -> MS
CP-ACK
19
SS -> MS
CP-DATA
Contains RP-ACK RPDU
20
MS -> SS
CM SERVICE REQUEST
CM service type set to "Short message transfer".
21
MS -> SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
If CP-ACK received then continue at A22
If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 20 then goto step B22-1.
Branch A
A22
SS -> MS
CM SERVICE ACCEPT
After having sent the CM SERVICE ACCEPT then goto step 23.
Branch B
B22-1
SS->MS
CM SERVICE ACCEPT
This branch is chosen if the MS does not send a CP-ACK within 5 s of step 20.
B22-2
(optional)
MS->SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU
23
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 23, 24, 25 and 26 shall be z, where z <> y (see step 17).
24
SS -> MS
CP-ACK
25
SS -> MS
CP-DATA
Contains RP-ACK RPDU
26
MS -> SS
CP-ACK
Shall be sent within 5 s of step 25
27
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
28
MS -> SS
DISC (SAPI=0)
MS shall respond to channel release with a layer 2 DISC frame with SAPI 0
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
not checked
TP-DCS
not checked
TP-VP
not checked
TP-UDL
as applicable
TP-UD (140 octets max.)
the user data consist of an arbitrarily chosen amount of octets |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.2 MS in active mode | This test applies to MS supporting the ability of sending multiple short messages when there is a call in progress. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.2.1 Conformance requirements | For a R99 or earlier MS only:
If another short message or a memory available notification is to be sent, an originating SMR entity in the UE may choose to continue to use the same RRC connection. When the MS chooses to use the same RR connection, then:
‑ the MS shall transmit a CM SERVICE REQUEST for the new CM connection before the final CP‑ACK (e.g. the one that acknowledges the CP‑DATA that carried the RP‑ACK) for the old MM connection is transmitted;
‑ before transmission of the first CP‑DATA on the new MM connection, the MS shall transmit the CP‑ACK for the old MM connection;
‑ the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and
‑ the MS shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.
For a Rel-4 or later MS only:
In the case of a SMS transfer via the CS domain, when the UE chooses to use the same RR or CS signalling connection, then:
- the UE shall transmit a CM SERVICE REQUEST for the new CM connection before the final CP‑ACK (i.e. the one that acknowledges the CP‑DATA that carried the RP‑ACK) for the old MM connection is transmitted;
- before transmission of the first CP‑DATA on the new MM connection, the UE may transmit the CP‑ACK for the old MM connection; the UE shall not transmit the final CP-ACK after the new CP-DATA;
- the Transaction Identifier used on the new MM connection shall be different to that used on the old MM connection; and
- the UE shall not initiate establishment of the new MM connection before the final CP‑DATA (e.g. the one carrying the RP‑ACK) has been received.
References
3GPP TS 03.40; subclause 3.1.
3GPP TS 04.11; subclause 5.4.
3GPP TS 04.13; subclause 5.6. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.2.2 Test purpose | To verify that the MS is able to correctly send multiple short messages on the same RR connection when sent parallel to a call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.2.9.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 how to enter multiple SMS.
- Description of the basic procedures to display a mobile originated short message.
- Support for state U10 of call control.
Foreseen final state of MS
Idle, updated.
Test procedure
a) 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 set up to send 3 short messages as multiple 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.
b) Steps c) to k) of the test procedure in subclause 34.2.9.1.3 are repeated.
Maximum duration of test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS
A data or speech call is established on a TCH and the state U10 of call control is entered.
2
MS
The MS is set up to send 3 short messages as multiple SM
3
MS -> SS
CM SERVICE REQUEST
Sent in a layer 2 frame on the FACCH. CM service type set to "short message transfer"
4
SS -> MS
CM SERVICE ACCEPT
5
MS -> SS
SABM (SAPI=3)
Sent on SACCH associated with the TCH
6
SS -> MS
UA (SAPI=3)
7
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 7, 8, 9 and 11 shall be x.
8
SS -> MS
CP-ACK
9
SS -> MS
CP-DATA
Contains RP-ACK RPDU
10
MS -> SS
CM SERVICE REQUEST
Sent in a layer 2 frame on the FACCH. CM service type set to "short message transfer"
11
MS -> SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
If CP-ACK received then continue at A12.
If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 10 then goto step B12-1.
Branch A
A12
SS -> MS
CM SERVICE ACCEPT
After having sent the CM SERVICE ACCEPT then goto step 13.
Branch B
B12-1
SS->MS
CM SERVICE ACCEPT
This branch is chosen if the MS does not send a CP-ACK within 5 s of step 10.
B12-2
(optional)
MS->SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
13
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 13, 14, 15 and 17 shall be y where y <> x (see step 7).
14
SS -> MS
CP-ACK
15
SS -> MS
CP-DATA
Contains RP-ACK RPDU
16
MS -> SS
CM SERVICE REQUEST
Sent in a layer 2 frame on the FACCH. CM service type set to "short message transfer"
17
MS -> SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
If CP-ACK received then continue at A18
If CP-ACK is not received within 5 s from the CM SERVICE REQUEST was sent in step 16 then goto step B18-1.
Branch A
A18
SS -> MS
CM SERVICE ACCEPT
After having sent the CM SERVICE ACCEPT then goto step 19.
Branch B
B18-1
SS->MS
CM SERVICE ACCEPT
This branch is chosen if the MS does not send a CP-ACK within 5 s of step 16.
B18-2
(optional)
MS->SS
CP-ACK
The one that acknowledges the CP-DATA which carried the RP-ACK RPDU.
19
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU). The Transaction Identifier used in steps 19, 20, 21 and 22 shall be z, where z <> y (see step 13).
20
SS -> MS
CP-ACK
21
SS -> MS
CP-DATA
Contains RP-ACK RPDU
22
MS -> SS
CP-ACK
Shall be sent within 5.5 s (5 sec + 10% tolerance) of step 21
23
SS -> MS
CHANNEL RELEASE
The main signalling link is released.
24
MS -> SS
DISC (SAPI = 0)
MS shall respond to channel release with a layer 2 DISC frame with SAPI 0.
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
not checked
TP-DCS
not checked
TP-VP
not checked
TP-UDL
as applicable
TP-UD (140 octets max.)
the user data consist of an arbitrarily chosen amount of octets |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.3 Short message service cell broadcast | This test applies to all MSs. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.3.1 Conformance requirements | If the MS supports SMS-CB, it is responsible for recombination of the four blocks received via the radio path into a single block which constitutes the cell broadcast short message.
In idle mode, the MS listens to the BCCH and to the paging sub-channel for the paging group it belongs to. The MS is required to receive and analyse the paging messages and immediate assignment messages sent on the paging subchannel corresponding to its paging subgroup.
Reference
3GPP TS 03.41; clause 8.
3GPP TS 04.08 / 3GPP TS 44.018, subclauses 3.2.1 and 3.3.2.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.3.2 Test purpose | This test verifies that an MS supporting SMS-CB is able to receive SMS-CB messages.
This test verifies that an MS is able to respond to a paging requested during the transmission of a cell broadcast short message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.3.3 Test method | Initial conditions
System Simulator:
1 cell, default parameters, except BS_PA_MFRMS = 2.
The SS provides a BCCH/CCCH to support the MS in idle mode.
Periodic location updating is disabled.
Mobile Station:
The MS shall be in the idle updated state.
Specific PICS Statements
-
PIXIT Statements
- Description of the basic procedures to display a cell broadcasted short message.
Foreseen Final State of MS
Idle, updated.
Test Procedure
a) Three Cell Broadcast (CB) messages are sent by the SS on the CBCH with serial numbers 0,1,1.
b) Step a) is repeated, but the SS pages the MS during the transmission of the second CB message. This shall be achieved by paging the MS immediately after the first block of the CB message has been sent. The SS shall ensure that the page is transmitted on the radio interface prior to the transmission of the 4th block of the CB message.
NOTE: The use of BS_PA_MFRMS = 2 ensures that this can be achieved irrespective of the IMSI.
The MS shall respond to the page.
Maximum Duration of Test
-
Expected Sequence
Since the SMS-CB messages are sent continuously, a table is not applicable in this test.
Specific Message Contents:
Cell broadcast test message content
Information element
Comment Value
Serial Number
- Geographical scope
"00"B
- Message code
see test procedure "0000000000"B or "0000000001"B
- Update number
as applicable
Message identifier
"0"B
Data Coding Scheme
Default alphabet, English "00000001"B
Page parameter
"0001 0001"B
Contents of message
93 user characters using 93 different characters of default 7 bit coded alphabet
SYSTEM INFORMATION TYPE 4
As default except:
Information element
Value/remark
CBCH Channel Description
- Channel type and TDMA offset
SDDCH/4 + SACCH/C4 or CBCH (SDDCH/4)
- Timeslot number
time slot zero
- Training sequence code
5 (same as BCC)
- Hopping channel
Single RF channel
-Channel selector
Channel number 263 (for GSM 450 MS) Channel number 310 (for GSM 480 MS) Channel number 20 (for GSM 900 MS) Channel number 590 (for DCS 1 800 and PCS 1 900 MS) Channel number 457 (for GSM 710, GSM 750 and T-GSM 810 MS) Channel number 147 (for GSM 850 MS)
CBCH Mobile Allocation
Not included |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4 Short message service point to point over GPRS | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.1 SMS mobile terminated | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.1.1 Definition | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.1.2 Conformance requirements | An active MS shall be able to receive a short message TPDU (SMS‑DELIVER) at any time, independently of whether or not there is a speech or data call in progress. A report shall always be returned to the SC; either confirming that the MS has received the short message, or informing the SC that it was impossible to deliver the short message TPDU to the MS, including the reason why.
References
3GPP TS 23.040 clauses 3.1, 9.2.3.16. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.1.3 Test purpose | To verify the ability of a MS to receive and decode the SM where provided for the point to point service. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.1.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- Mobile Station:
- the MS shall be in GMM-state "GMM-REGISTERED";
- 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
- Support for session management state "PDP-ACTIVE".
- Maximum number of retransmissions of an unacknowledged CP-DATA message.
Test procedure
a) 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.
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 check during 60 s 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 PDP context is established with the SS and the state PDP-ACTIVE of session management is entered.
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. 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. The SS check during 60 s that the MS does not send more than the maximum allowed (3) CP-DATA retransmissions. (60 s the sufficient wait time while PDP context in progress).
k) The SS initiates a PDP context deactivation (The PDP context deactivation is continued 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.
The SMS message store shall be cleared manually by the operator.
l) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The PDP context shall be cleared from the MS. (The PDP context deactivating is continued 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.
The SMS message store shall be cleared manually by the operator.
Expected sequence
Step
Direction
Message
Comments
1
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
2
SS
Waits max 25 s for CP-ACK
3
MS -> SS
CP-ACK
4
SS
Waits max 60 s for RP-ACK RPDU
5
MS -> SS
CP-DATA
Contains RP-ACK RPDU
6
MS <- SS
CP-ACK
7
MS
There should be no further CP-DATA message.
8
MS
The MS shall indicate that an SM has arrived.
9
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
10
SS
Waits max 25 s for CP-ACK
11
MS -> SS
CP-ACK
12
SS
Waits max 60 s for RP-ACK RPDU
13
MS -> SS
CP-DATA
First CP-DATA from MS, contains RP-ACK RPDU
14
SS
First CP-DATA message not acknowledged by SS
15
MS -> SS
CP-DATA
Retransmitted CP-DATA from MS, contains RP-ACK RPDU
16
MS <- SS
CP-ACK
Second CP_DATA message is acknowledged
17
MS
There should be no further CP-DATA messages
18
MS
The MS shall indicate that an SM has arrived.
19
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
20
SS
Waits max 25 s for CP-ACK
21
MS -> SS
CP-ACK
22
SS
Waits max 60 s for RP-ACK RPDU
23
MS -> SS
CP-DATA
Contains RP-ACK RPDU
24
SS
First CP-DATA message not acknowledged by SS
25
CP-DATA
Retransmitted CP-DATA from MS, contains RP-ACK RPDU
26
SS
Retransmitted CP-DATA message not acknowledged by SS
27
MS
Depending upon the maximum number of CP-DATA retransmissions implemented, step 25 and 26 may be repeated.
28
MS
The SS verifies within 60 s after the first CP-DATA message not acknowledged by SS that the MS does not retransmit more than the maximum allowed.
29
MS
The MS shall indicate that an SM has arrived.
30
MS, SS
{PDP Context Activation}
Macro. PDP context activation from the MS.
31
MS <- SS
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
Contains RP-ACK RPDU
36
MS <- SS
CP-ACK
37
MS <- SS
DEACTIVATE PDP CONTEXT REQUEST
Deactivates the existing PDP context.
38
MS -> SS
DEACTIVATE PDP CONTEXT ACCEPT
39
MS
The MS shall indicate that an SM has arrived.
40
MS
Clear the SMS message store
41
MS
{PDP Context Activation}
Macro. PDP context activation from the MS.
42
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
43
SS
Waits max 25 s for CP-ACK
44
MS -> SS
CP-ACK
45
SS
Waits max 60 s for RP-ACK RPDU
46
MS -> SS
CP-DATA
First CP-DATA from MS, contains RP-ACK RPDU
47
SS
First CP-DATA message not acknowledged by SS
48
MS -> SS
CP-DATA
Retransmitted CP-DATA message, contains RP-ACK RPDU
49
MS <- SS
CP-ACK
Second CP-DATA message is acknowledged
50
MS <- SS
DEACTIVATE PDP CONTEXT REQUEST
Deactivates an existing PDP context.
51
MS -> SS
DEACTIVATE PDP CONTEXT ACCEPT
52
MS
The MS shall indicate that an SM has arrived.
53
MS
Clear the SMS message store
54
MS
{PDP Context Activation}
Macro. PDP context activation from the MS.
55
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
56
SS
Waits max 25 s for CP-ACK
57
MS -> SS
CP-ACK
58
SS
Waits max 60 s for RP-ACK RPDU
59
MS -> SS
CP-DATA
First CP-DATA from MS, contains RP-ACK RPDU
60
SS
First CP-DATA message not acknowledged by SS
61
MS -> SS
CP-DATA
Transmitted CP-DATA message, contains RP-ACK RPDU
62
SS
Retransmitted CP-DATA message not acknowledged by SS
63
MS
Depending on the maximum number of CP-DATA retransmissions implemented, step 61 and 62 may be repeated. The maximum number of retransmissions may however not exceed three.
64
MS
The SS verifies within 60 s after the last CP-DATA retransmission that the MS does not retransmit more than the maximum allowed.
65
MS
The MS shall indicate that an SM has arrived.
66
MS
Clear the SMS message store
67
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
68
MS <- SS
DEACTIVATE PDP CONTEXT REQUEST
The PDP context is deactivated by the SS. The PDP context deactivating is continued in parallel to the following exchange of messages related to SMS.
69
MS -> SS
DEACTIVATE PDP CONTEXT ACCEPT
This message may be transmitted after this step timing.
70
SS
Waits max 25 s for CP-ACK
71
MS -> SS
CP-ACK
72
SS
Waits max 60 s for RP-ACK RPDU
73
MS -> SS
CP-DATA
Contains RP-ACK RPDU
74
MS <- SS
CP-ACK
75
MS
The MS shall indicate that an SM has arrived.
76
MS
Clear the SMS message store
77
MS
{PDP Context Activation}
Macro. PDP context activation from the MS.
78
MS -> SS
DEACTIVATE PDP CONTEXT REQUEST
The PDP context is deactivated by the MS. The PDP context deactivation is continued in parallel to the following
79
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
80
MS <- SS
DEACTIVATE PDP CONTEXT ACCEPT
81
SS
Waits max 25 s for CP-ACK
82
MS -> SS
CP-ACK
83
SS
Waits max 60 s for RP-ACK RPDU
84
MS -> SS
CP-DATA
Contains RP-ACK RPDU
85
MS <- SS
CP-ACK
86
MS
The MS shall indicate that an SM has arrived.
87
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 (not containing a type 0 message)
Information element
Comment Value
TP-PID
Different from Type 0: “01000000”B
TP-UDL
160
TP-UD (140 octets)
text of message (160 characters)
NOTE: The 160 characters in TP-UD shall include at least one occurrence of each character in the default alphabet (see 3GPP TS 23.038, clause 6.2.1). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.2 SMS mobile originated | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.2.1 Definition | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.2.2 Conformance requirements | A GPRS MS shall be able to submit short message TPDU (SMS-SUBMIT) at any time, independently of whether or not there is a PDP context in progress.
References
3GPP TS 24.011 clause 5.3.2.2.
3GPP TS 23.040 clause 3.1, 9.2.3.16. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.2.3 Test purpose | To verify that a GPRS MS is able to correctly send a short message where the SMS is provided for the point to point service. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.2.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- Mobile Station:
- the MS shall be in GMM-state "GMM-REGISTERED";
- 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
- Support for state PDP-ACTIVE of session management.
- Maximum number of retransmissions of an unacknowledged CP-DATA message.
Test procedure
a) The MS shall be set up to send a short message to the SS. 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 CP-ACK message.
b) The MS shall be set up to send a short message to the SS. This time the SS will not acknowledge the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS. The MS retransmits the CP-DATA message. Now, the CP-DATA message will be acknowledged by a CP-ACK from the SS, followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for CP-ACK message.
c) The MS shall be set up to send a short message to the SS. The SS is configured not to send any CP-ACK to acknowledge the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS. Then maximum 3 CP-DATA retransmissions may occur. Following the last CP-DATA retransmission from the MS, the SS checks that the MS does not retransmit more than the maximum allowed.
d) The MS shall be set up to send a short message to the SS. On receipt of the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS, the SS sends a CP-ERROR message containing a “Network Failure” cause. The SS verifies within 60 seconds that the MS does not re-send any CP-DATA messages.
e) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The MS shall be set up to send a short message to the SS. 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 CP-ACK message.
f) The MS shall be set up to send a short message to the SS. The SS is configured not to send CP-ACK to acknowledge the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS. The MS retransmits the CP-DATA message. Now, the CP-DATA message will be acknowledged by a CP-ACK from the SS, followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for CP-ACK message.
g) The MS shall be set up to send a short message to the SS. The SS is configured not to send any CP-ACK to acknowledge the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS. Then maximum 3 CP-DATA retransmissions may occur. Following the last CP-DATA retransmission from the MS, the SS checks that the MS does not retransmit more than the maximum allowed.
h) The MS shall be set up to send a short message to the SS. On receipt of the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS, the SS sends a CP-ERROR message containing a “Network Failure” cause. The SS verifies that within 60 seconds the MS does not re-send any CP-DATA messages.
i) The MS shall be set up to send a short message to the SS. On receipt of the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS, the SS requests the deactivation of the previously active PDP context by sending DEACTIVATE PDP CONTEXT REQUEST, the MS responds with DEACTIVATE PDP CONTEXT ACCEPT. The SS responds 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 CP-ACK message.
j) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The MS shall be set up to send a short message to the SS. On receipt of the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS, the SS requests the deactivation of the previously active PDP context by sending DEACTIVATE PDP CONTEXT REQUEST, the MS responds with DEACTIVATE PDP CONTEXT ACCEPT. This time the SS will not acknowledge the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS. The MS retransmits the CP-DATA message. Now, the CP-DATA message will be acknowledged by a CP-ACK from the SS, followed by a CP-DATA message containing the correct RP-ACK RPDU. The SS waits a maximum of 25 s for CP-ACK message.
k) A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered. The MS shall be set up to send a short message to the SS. On receipt of the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS, the SS requests the deactivation of the previously active PDP context by sending DEACTIVATE PDP CONTEXT REQUEST, the MS responds with DEACTIVATE PDP CONTEXT ACCEPT. The SS is configured not to send any CP-ACK to acknowledge the CP-DATA containing RP-DATA RPDU (SMS SUBMIT TPDU) from the MS. Then maximum 3 CP-DATA retransmissions may occur. Depending on the maximum number of automatic repeat, MO SMS sending may be repeated. Following the last CP-DATA retransmission from the MS, the SS checks that the MS does not retransmit more than the maximum allowed.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is set up to send an SM.
2
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
3
SS MS
CP-ACK
4
SS MS
CP-DATA
Contains RP-ACK RPDU.
5
SS
Wait max 25 s for CP-ACK.
6
MS SS
CP-ACK
7
MS
The MS is set up to send an SM.
8
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
9
SS
SS configured not to send CP-ACK.
10
MS SS
CP-DATA
Retransmitted CP-DATA from MS.
11
SS MS
CP-ACK
12
SS MS
CP-DATA
Contains RP-ACK RPDU.
13
SS
Wait max 25 s for CP-ACK.
14
MS SS
CP-ACK
15
MS
The MS is set up to send an SM.
16
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
17
SS
SS configured not to send any CP-ACK.
18
MS SS
CP-DATA
Retransmitted CP-DATA from MS.
19
MS
Depending upon the maximum number of CP-DATA retransmissions implemented, step 18 may be repeated.
The maximum number of retransmissions shall however not exceed three.
20
SS
The SS verifies within 60 s after the first CP-DATA message not acknowledged by SS that the MS does not retransmit more than the maximum allowed.
21
MS
The MS is set up to send an SM.
22
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
23
SS MS
CP-ERROR
Containing “Network Failure” cause.
24
The SS verifies within 60 s after step 22 that the MS does not re-send any CP-DATA messages.
25
MS
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered.
26
MS
The MS is set up to send an SM.
27
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
28
SS MS
CP-ACK
29
SS MS
CP-DATA
Contains RP-ACK RPDU.
30
SS
Wait max 25 s for CP-ACK.
31
MS SS
CP-ACK
32
MS
The MS is set up to send an SM.
33
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
34
SS
SS configured not to send CP-ACK.
35
MS SS
CP-DATA
Retransmitted CP-DATA from MS.
36
SS MS
CP-ACK
37
SS MS
CP-DATA
Contains RP-ACK RPDU.
38
SS
Wait max 25 s for CP-ACK.
39
MS SS
CP-ACK
40
MS
The MS is set up to send an SM.
41
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
42
SS
SS configured not to send any CP-ACK.
Step
Direction
Message
Comments
43
MS SS
CP-DATA
Retransmitted CP-DATA from MS.
44
MS
Depending upon the maximum number of CP-DATA retransmissions implemented, step 43 may be repeated.
The maximum number of retransmissions shall however not exceed three.
45
SS
The SS verifies within 60 s after the first CP-DATA message not acknowledged by SS that the MS does not retransmit more than the maximum allowed.
46
MS
The MS is set up to send an SM.
47
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
48
SS MS
CP-ERROR
Containing “Network Failure” cause.
49
The SS verifies within 60 s after step 47 that the MS does not re-send any CP-DATA messages.
50
MS
The MS is set up to send an SM.
51
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
52
SS MS
DEACTIVATE PDP CONTEXT REQUEST
The PDP context is deactivated by the SS.
The PDP context deactivation is continued in parallel to the following exchange of messages related to SMS.
53
MS SS
DEACTIVATE PDP CONTEXT ACCEPT
54
SS MS
CP-ACK
55
SS MS
CP-DATA
Contains RP-ACK RPDU.
56
SS
Wait max 25 s for CP-ACK.
57
MS SS
CP-ACK
58
MS
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered.
59
MS
The MS is set up to send an SM.
60
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
61
SS MS
DEACTIVATE PDP CONTEXT REQUEST
The PDP context is deactivated by the SS.
The PDP context deactivation is continued in parallel to the following exchange of messages related to SMS.
62
MS SS
DEACTIVATE PDP CONTEXT ACCEPT
63
SS
SS configured not to send CP-ACK.
64
MS SS
CP-DATA
Retransmitted CP-DATA from MS.
65
SS MS
CP-ACK
66
SS MS
CP-DATA
Contains RP-ACK RPDU.
67
SS
Wait max 25 s for CP-ACK.
68
MS SS
CP-ACK
69
MS
A PDP context is established with the SS and the state PDP-ACTIVE of session management is entered.
70
MS
The MS is set up to send an SM.
71
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU).
72
SS MS
DEACTIVATE PDP CONTEXT REQUEST
The PDP context is deactivated by the SS.
The PDP context deactivation is continued in parallel to the following exchange of messages related to SMS.
73
MS SS
DEACTIVATE PDP CONTEXT ACCEPT
74
SS
SS configured not to send any CP-ACK.
Step
Direction
Message
Comments
75
MS SS
CP-DATA
Retransmitted CP-DATA from MS.
76
MS
Depending upon the maximum number of CP-DATA retransmissions implemented, step 75 may be repeated.
The maximum number of retransmissions shall however not exceed three.
77
SS
The SS verifies within 60 s after the first CP-DATA message not acknowledged by SS that the MS does not retransmit more than the maximum allowed.
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
None. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.3 Test of the status report capabilities and of SMS-COMMAND over GPRS: | This test applies to MSs which support the status report capabilities. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.3.1 Definition | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.3.2 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 23.040 clauses 3.2.9 and 9.2.3.6. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.3.3 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.4.3.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- Mobile Station:
- the MS shall be in GMM-state "GMM-REGISTERED".
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
a) The MS is made to send a Mobile Originated short message.
b) The SS sends a CP-DATA message containing a RP-DATA RPDU itself containing an SMS-STATUS-REPORT TPDU.
c) The MS is made to send an SMS-COMMAND message enquiring about the previously submitted short message.
d) 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.
e) The MS is made to send an SMS-COMMAND message requiring to delete the previously submitted short message.
Expected sequence
Step
Direction
Message
Comments
1
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
2
SS MS
CP-ACK
3
SS MS
CP-DATA
Contains RP-ACK RPDU
4
SS
Waits max 25 s for CP-ACK
5
MS SS
CP-ACK
6
SS MS
CP-DATA
Contains RP-DATA RPDU (SMS-STATUS-REPORT TPDU)
7
MS SS
CP-ACK
8
MS SS
CP-DATA
Contains RP-ACK RPDU
9
SS MS
CP-ACK
10
MS
The MS is made to send an SMS-COMMAND message enquiring about the previously submitted SM
11
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS-COMMAND TPDU) which shall contain the correct TP-MR
12
SS MS
CP-ACK
13
SS MS
CP-DATA
Contains RP-ACK RPDU
14
MS SS
CP-ACK
15
MS
The MS is made to send an SMS-COMMAND message requiring to delete the previously submitted SM.
16
MS SS
CP-DATA
Contains RP-DATA RPDU (SMS-COMMAND TPDU) which shall contain the correct TP-MR
17
SS MS
CP-ACK
18
SS MS
CP-DATA
Contains RP-ACK RPDU
19
MS SS
CP-ACK
Specific Message Contents
SMS SUBMIT TPDU
Information element
Comment Value
TP-SRR
status report is requested "1"B
SMS-STATUS-REPORT TPDU (SS to MS in step 6):
Information element
Comment Value
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-ST
SM received "00000000"B
First SMS-COMMAND TPDU (MS to SS in step 10)
Information element
Comment Value
TP-MR
TP-MR in previous SMS-SUBMIT plus "1"
TP-SRR
status report requested "1"B
TP-CT
Enquiry relating to previously submitted
short message "00000000"B
TP-MN
not checked (TP-MR in previous SMS-SUBMIT)
Second SMS-COMMAND TPDU (MS to SS in step 15)
Information element
Comment Value
TP-MR
TP-MR in previous SMS-COMMAND plus "1"
TP-CT
Delete previously submitted short message
"00000010"B
TP-MN
not checked (TP-MR in previous SMS-SUBMIT) |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.4 Test of capabilities of simultaneously receiving a short message whilst sending a mobile originated short message | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.4.1 Definition | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.4.2 Conformance requirements | An active MS shall be able to receive a short message TPDU (SMS-DELIVER) at any time, independently of whether or not there is an SMS mobile originated call (SMS-SUBMIT or SMS-COMMAND) in progress.
Reference(s):
3GPP TS 03.40 / 3GPP TS 23.040 clause 3.1, 9.2.3.16.
3GPP TS 04.11 / 3GPP TS 24.011 clause 3.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.4.3 Test purpose | The test verifies that the MS is capable of simultaneously receiving a network originated SM whilst sending a mobile originated SM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.4.4 Method of test | Initial Conditions
System Simulator:
- 1 cell, default parameters.
Mobile Station:
- the MS shall be in GMM-state "GMM-REGISTERED";
- the SMS message storage shall be empty.
Specific PICS Statements
-
PIXIT Statements
Test procedure
The MS is triggered to send an SM to the SS. Upon the reception of the CP-DATA, the SS sends an SM to the MS.
The MS shall use the correct transaction identifiers and correctly receive the SM and indicate that a message has arrived.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to send an SM.
2
MS -> SS
CP-DATA
Contains RP-DATA RPDU (SMS SUBMIT TPDU)
3
SS
The SS sends an SM to the MS triggered by the end of the CP-DATA message from the MS
4
MS <- SS
CP-DATA
Contains RP-DATA RPDU (SMS DELIVER TPDU)
5
MS -> SS
CP-ACK
6
MS -> SS
CP-DATA
Contains RP-ACK RPDU
7
MS <- SS
CP-ACK
8
MS <- SS
CP-ACK
9
MS <-SS
CP-DATA
Contains RP-ACK RPDU
10
MS -> SS
CP-ACK
Specific Message Contents
None. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.5 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.6 Concatenated MO SMS over GPRS | Concatenation allows short messages to be concatenated to form a longer message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.6.1 Conformance requirement | This facility allows short messages to be concatenated to form a longer message.
The Information‑Element‑Data field contains information set by the application in the SMS‑SUBMIT so that the receiving entity is able to re‑assemble the short messages in the correct order. Each concatenated short message contains a reference number, which together with the originating address and Service Centre address allows the receiving entity to discriminate between concatenated short messages sent from different originating SMEs and/or SCs
References
3GPP TS 23.040 Clause 9.2.3.24.1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.6.2 Test purpose | To verify that MS is able to send longer messages (user data exceeding 140 octets) using concatenation feature. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.6.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS shall be in GMM-state "GMM-REGISTERED"
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
a) The MS is made to send a short message with user data exceeding 140 octets
b) Repeat steps c) to e) for n=1..N; N is the total number of segments in SM triggered in step a)
c) MS sends CP-DATA containing RP-DATA with “TP User Data” as nth segment of SM
d) The SS responds to the CP-DATA in step c) with a CP-ACK message followed by a CP-DATA message containing the correct RP-ACK RPDU
e) The SS waits a maximum of 25 s for CP-ACK message
f) Check for 60 s that no CP-DATA is received from the MS.
Maximum Duration of Test
-
Expected sequence
Step
Direction
Message
Comments
1
MS
MS is setup to send SM with user data exceeding 140 octets
Repeat steps 2 to 6 for n = 1..N
2
MS SS
CP-DATA
Contains RP-DATA with “TP User Data” as nth segment of SM. See specific message contents below
3
SS MS
CP-ACK
4
SS MS
CP-DATA
Contains RP-ACK RPDU
5
SS
Waits max 25 s for CP-ACK
6 (Optional)
MS SS
CP-ACK
Depends on the MS implementation if the CP-ACK is received.
7
SS
Check for 60 s that no CP-DATA is received from the MS.
Specific Message Contents
TP USER DATA (8 bits / 16 bits concatenation reference numbers) in step 2
Information element
Comment Value
UDHL
05 (8 bits) / 06 (16 bits)
IEI
00 (8 bits) / 08 (16 bits)
IEI-Length
03 (8 bits) / 04 (16 bits)
IEI Data
MR
M, any value between 0 to 255 (8 bits) / 65535 (16 bits)
MAX SEGMENT COUNT
N, Total number of segments
SEQUENCE NUMBER
n, segment number
TP-UD (<=134 (8 bit) / 133 (16 bit) octets)
User data in nth segment of SM |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.7 Concatenated MT SMS over GPRS | Concatenation allows short messages to be concatenated to form a longer message |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.7.1 Conformance requirement | This facility allows short messages to be concatenated to form a longer message.
The Information‑Element‑Data field contains information set by the application in the SMS‑DELIVER so that the receiving entity is able to re‑assemble the short messages in the correct order. Each concatenated short message contains a reference number, which together with the originating address and Service Centre address allows the receiving entity to discriminate between concatenated short messages sent from different originating SMEs and/or SCs
The TP elements in the SMS‑DELIVER PDU, apart from TP‑UDL and TP‑UD, should remain unchanged for each SM that forms part of a concatenated SM; otherwise this may lead to irrational behavior.
References
3GPP TS 23.040 Clause 9.2.3.24.1 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.7.2 Test purpose | To verify that MS is able to combine concatenated message segments to form a long message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.7.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters
Mobile Station:
The MS shall be in GMM-state "GMM-REGISTERED"
The SMS message storage shall be empty.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
a) Repeat steps b) to d) for n= 1..N; N is the total number of segments in SM
b) The SS sends a CP-DATA message. The information element of the CP-DATA message will be RP-DATA (SMS DELIVER TPDU) with “TP User Data” as the nth segment of SM
c) 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.
d) The SS sends a CP-ACK to the MS.
Maximum Duration of Test
-
Expected sequence
Step
Direction
Message
Comments
Repeat steps 1 to 4 for n = 1..N
1
SS MS
CP-DATA
RP-DATA with “TP User Data” as the nth segment of SM
2
MS SS
CP-ACK
Wait for CP-ACK for 25 s
3
MS SS
CP-DATA
Waits max 60 s for RP-ACK RPDU
4
SS MS
CP-ACK
5
MS
SS prompts operator to verify stored long message
Specific Message Contents
TP USER DATA in step 1
Information element
Comment Value
UDHL
05
IEI
00
IEI-Length
03
IEI Data
MR
00
MAX SEGMENT COUNT
N, Total number of segments
SEQUENCE NUMBER
n, segment number
TP-UD (<=134 octets)
user data equal to 134 octets for n = 1, N-1 and
user data less than or equal to 134 octets for n = N |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8 Short Messaging Service – Handling of unknown, unforeseen, and erroneous protocol data | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.1 CP Error Handling | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.1.1 Conformance requirements | a) The Mobile Station shall ignore a CP message (CP‑DATA, CP‑ACK, CP‑ERROR) received with TI value "111".
b) Whenever a CP‑ACK message is received specifying a Transaction Identifier which is not associated with an active SM transfer, the mobile station shall discard the message and return a CP‑ERROR message with cause #81, "Invalid Transaction Identifier" using the received Transaction Identifier, if an appropriate connection exists
c) The Mobile Station shall ignore a CP‑ERROR message that is received specifying a Transaction Identifier, which is not associated with an active SM transfer.
d) The Mobile Station shall ignore a CP‑DATA message that is received specifying a Transaction Identifier which is not associated with an active SM transfer and with transaction identifier flag set to "1".
e) If the Mobile Station receives a message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message and return a CP‑ERROR message with cause #97 "message type non‑existent or not implemented", if an appropriate connection exists.
f) If the Mobile Station receives a message not consistent with the protocol state, the Mobile Station shall ignore the message and return a CP‑ERROR message with cause #98 "Message type not compatible with the short message protocol state", if an appropriate connection exists.
g) When on receipt of a message:
h) an "imperative message part" error; or
‑ a "missing mandatory IE" error.
is diagnosed or when a message containing a syntactically incorrect mandatory IE is received, the mobile station shall proceed as follows.
• When the corresponding SM transfer is not seen as successfully transferred, i.e. the transaction is not completed, the mobile station shall ignore the message and return a CP‑ERROR message with cause #96 "invalid mandatory information", if an appropriate connection exists.
Reference
3GPP TS 24.011clause 9.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.1.2 Test purpose | a) To Verify that MS ignores CP-DATA message with TI value "111".
b) To verify that MS ignores CP-ACK message with TI value not associated with active SMS transfer and sends CP-ERROR with cause # 81
c) To verify that MS ignores CP-ERROR with TI value not associated with active SMS transfer
d) To verify MS response when received CP-DATA with TI value not associated with active SMS transfer and “TI” flag set to ‘1’B
e) To verify that MS ignores a message with “message type” not defined for the PD ‘1001’B and returns CP-ERROR with cause#97
f) To verify that MS ignores a message not consistent with protocol state and returns CP-ERROR with cause#98
g) To Verify that MS ignores CP-DATA with “missing mandatory IE” and returns CP-ERROR with cause#96 when the corresponding SM transaction is not completed |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.1.3 Method of test | Initial Conditions
System simulator:
1 cell, default parameters
Mobile Station:
The MS shall be in GMM-state "GMM-REGISTERED"
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
a) The SS sends CP-DATA with TI value ‘111’B. Check for no response from MS for 60 s.
b) The MS shall be set up to send a short message to the SS. The MS sends CP-DATA containing RP-DATA (SMS SUBMIT PDU). SS send CP-ACK with TI value different from the TI value in CP-DATA received from MS. MS sends CP-ERROR with cause #81 (Invalid Transaction Identifier).
c) The MS shall be set up to send a short message to the SS. The MS sends CP-DATA containing RP-DATA (SMS SUBMIT PDU). SS send CP-ERROR with TI value different from the TI value in CP-DATA received from MS. SS sends CP-ACK and then CP-DATA containing RP-ACK. The SS waits a maximum of 25 s for the CP-ACK message.
d) The MS shall be set up to send a short message to the SS. The MS sends CP-DATA containing RP-DATA (SMS SUBMIT PDU). SS sends CP-ACK and then sends CP-DATA with TI value different from the TI value in CP-DATA received from MS. MS shall not send CP-ACK.
e) SS sends a message with PD value ‘1001’B and message type ‘00000010’B. MS sends CP-ERROR with cause #97 (Message type non-existent or not implemented).
f) The MS shall be set up to send a short message to the SS. MS sends CP-DATA (SMS SUBMIT PDU). SS sends CP-ACK twice. MS sends CP-ERROR with cause #98 (Message type not compatible with the short message protocol state)
g) The MS shall be set up to send a short message to the SS. MS sends CP-DATA (SMS SUBMIT PDU). SS sends CP-ACK and then sends CP-DATA with “CP‑User data” IE missing. MS sends a CP-ERROR message with cause #96 ("invalid mandatory information").
Maximum Duration of Test
10 min
Expected sequence
Step
Direction
Message
Comments
1
SS MS
CP-DATA
With TI value set to ‘111’B.
2
SS
Check for no response from the MS for 60 s
3
MS
The MS is set up to send an SM
4
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
5
SS MS
CP-ACK
With TI value different from CP-DATA in step 4.
6
MS SS
CP-ERROR
Cause #81
Complete the transaction initiated by MS.
7
MS
The MS is set up to send an SM
8
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
9
SS MS
CP-ERROR
With TI value different from CP-DATA in step 8.
10
SS MS
CP-ACK
11
SS MS
CP-DATA
Containing RP-ACK
12
SS
Wait 25 s for CP-ACK.
13
MS SS
CP-ACK
14
MS
The MS is set up to send an SM
15
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
16
SS MS
CP-ACK
17
SS MS
CP-DATA
With TI different from CP-DATA in step 15 and containing RP-ACK
18
SS
Check for no CP-ACK within 25 s
Complete the transaction initiated by MS.
19
SS MS
CP-Message
Message type ‘00000010’B and PD ‘1001’B
20
MS SS
CP-ERROR
Cause #97
21
MS
The MS is set up to send an SM
22
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
23
SS MS
CP-ACK
24
SS MS
CP-ACK
25
MS SS
CP-ERROR
Cause #98
Complete the transaction initiated by MS.
26
MS
The MS is set up to send an SM
27
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
28
SS MS
CP-ACK
29
SS MS
CP-DATA
With TI flag set to ‘1’B, TI value same as the TI value of CP-DATA in step 27 and Missing “CP-User-Data” IE.
30
MS SS
CP-ERROR
Cause#96
Complete the transaction initiated by MS.
Specific Message Contents
None |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.2 RP Error Handling | 34.4.8.2.1 Conformance Requirement
a) Whenever any RP‑ACK message is received specifying a Message Reference which is not associated with an active SM transfer, the mobile station shall discard the message and return an RP‑ERROR message with cause #81, "Invalid short message transfer reference value" using the received Message Reference, if an appropriate connection exists.
If the MS is attached to GPRS and the circuit-switched domain, and an SMS transfer via GPRS fails either due to a reception of an RP-ERROR message with cause #69 or due to the complete lack of network response, then the MS shall take the following actions:
The MS shall use the circuit-switched domain instead of GPRS for SMS transfer for an implementation dependent time. When a different PLMN is selected, if the MS preferred method is the sending of SMS over GPRS, the MS shall revert to trying an SMS transfer via GPRS.
b) When an RP‑ERROR message is received specifying a Message Reference, which is not associated with an active SM transfer, the mobile station shall discard the message.
c) If the Mobile Station receives a RP‑message indicating a value of the message type indicator (MTI) defined as reserved, it shall ignore the message and return an RP‑ERROR message with cause #97 "message type non‑existent or not implemented", if an appropriate connection exists.
d) If the Mobile Station receives a message (except RP‑ERROR) not consistent with the protocol state, the Mobile Station shall ignore the message and return a RP‑ERROR message with cause #98 "Message type not compatible with Short Message protocol state", if an appropriate connection exists.
e) If the Mobile Station receives an RP‑ERROR message not consistent with the protocol state, the Mobile Station shall ignore the message.
f) When on receipt of a message:
‑ an "imperative message part" error; or
‑ a "missing mandatory IE" error;
is diagnosed or when a message containing a syntactically incorrect mandatory IE is received, the mobile station shall (except for the case of a reserved value of the MTI as defined above) proceed as follows:
‑ when the message is an RP‑DATA or RP‑ACK, the mobile station shall ignore the message and return an RP‑ERROR message with cause #96 "invalid mandatorinformation", if an appropriate connection exists.
Reference
3GPP TS 24.011clauses 2.6, 9.3 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.2.2 Test Purpose | a) To verify that MS ignores RP-ACK with message reference which is not associated with active SM transfer and sends RP-ERROR with cause #81, “Invalid short message transfer reference value"
b) To verify that MS ignores RP-ERROR with message reference which is not associated with active SM transfer
c) To verify that MS ignores a RP-message with reserved MTI value and sends RP-ERROR with cause #97 "message type non‑existent or not implemented"
d) To verify that MS ignores the RP-ACK when SMR is in idle state and sends RP-ERROR with cause #98 "Message type not compatible with Short Message protocol state"
e) To verify that MS ignores RP-ERROR when SMR is in idle state
f) To verify that MS ignores RP-DATA with “missing mandatory IE” and sends RP-ERROR with cause #96, “Invalid mandatory information” |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.4.8.2.3 Method of test | Initial Conditions
System simulator:
1 cell, default parameters
Mobile Station:
The MS shall be in GMM-state "GMM-REGISTERED"
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
a) The MS shall be set up to send a short message to the SS. MS sends CP-DATA containing RP-DATA (SMS SUMBIT PDU). SS sends CP-ACK and CP-DATA containing RP-ACK with “RP Message Reference (RP-MR)” different from RP-MR in RP_DATA received. MS sends RP-ERROR with cause # 81, “Invalid short message transfer reference value”, if an appropriate connection exists. The MS may switch to CS domain for completing the transaction.
b) The MS shall be set up to send a short message to the SS. MS sends CP-DATA containing RP-DATA (SMS SUMBIT PDU). SS sends CP-ACK and CP-DATA containing RP-ERROR with “RP Message Reference (RP-MR)” different from RP-MR in RP_DATA received. Check for no CP-ACK 60 s. MS may switch to CS domain.
c) The SS sends CP-DATA containing RP-Message with TP-MTI value’010’B, “Reserved”. MS sends CP-DATA containing RP-ERROR with cause#97, “message type not compatible with short message state”
d) The SS sends CP-DATA containing RP-ACK when there is no active SMS transfer. MS sends CP-DATA containing RP-ERROR with cause#98, “Message type not compatible with short message protocol state”
e) The SS sends CP-DATA containing RP-ERROR when there is no active SMS transfer.
f) The SS sends CP-DATA containing “RP-DATA without RP‑User Data IE”. MS sends CP-DATA containing RP-ERROR with cause#96, “Invalid mandatory information”
Maximum Duration of Test
10min
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is set up to send an SM
2
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
3
SS MS
CP-ACK
4
SS MS
CP-DATA
Containing RP-ACK with RP-MR different from CP-DATA in step 2
5
MS SS
CP-ACK
6 (optional)
MS SS
CP-DATA
Containing RP-ERROR with cause #81
7 (conditional)
SS->MS
CP-ACK
Send if step 6 is performed
8
Complete the transaction initiated by MS.
MS may switch to CS domain.
9
MS
The MS is set up to send an SM
10
MS SS
CP-DATA
Containing RP-DATA (SMS SUBMIT PDU)
11
SS MS
CP-ACK
12
SS MS
CP-DATA
Containing RP-ERROR with RP-MR different from CP-DATA in step 10
13
MS SS
CP-ACK
14
SS MS
CP-DATA
Containing RP-ACK with correct RP-MR.
15 (optional)
MS SS
CP-ACK
MS may switch to CS domain.
16
SS MS
CP-DATA
Containing RP-Message with MTI value ‘010’B
17
MS SS
CP-ACK
18
MS SS
CP-DATA
Containing RP-ERROR with cause #97.
19
SS MS
CP-ACK
20
SS MS
CP-DATA
Containing RP-ACK
21
MS SS
CP-ACK
22
MS SS
CP-DATA
Containing RP-ERROR with cause #98.
23
SS MS
CP-ACK
24
SS MS
CP-DATA
Containing RP-ERROR
25
MS->SS
CP-ACK
26
SS
Check for no response from MS
27
SS MS
CP-DATA
Containing RP-DATA without RP-User Data IE.
28
MS SS
CP-ACK
29
MS SS
CP-DATA
Containing RP-ERROR with cause #96
30
SS MS
CP-ACK
Specific Message Contents
None |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 34.5 Default message contents | CP-DATA (including RP-DATA SS->MS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
any value from the set {0, ...., 6}
TI flag
0
Message type
00000001
CP-User data
length indicator
RP-DATA
max 248 octets
RP-Message Type
001 (RP-DATA SS->MS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
RP-Originator Address
see 3GPP TS 04.11 subclause 8.2.5.1
RP-Destination Address
length indicator set to 0
RP-User Data
length indicator
TP-DATA
max 233 octets
CP-DATA (including RP-DATA MS->SS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
any value from the set {0, ...., 6}
TI flag
0
Message type
00000001
CP-User data
length indicator
RP-DATA
max 248 octets
RP-Message Type
000 (RP-DATA MS->SS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
RP-Originator Address
length indicator set to 0
RP-Destination Address
see 3GPP TS 04.11 subclause 8.2.5.2
RP-User Data
length indicator
TP-DATA
max 233 octets
CP-DATA (including RP-ACK MS->SS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00000001
CP-User data
length indicator
RP-ACK
RP-Message Type
010 (RP-ACK MS->SS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
CP-DATA (including RP-ACK SS->MS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00000001
CP-User data
length indicator
RP-ACK
RP-Message Type
011 (RP-ACK SS->MS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
CP-DATA (including RP-ERROR MS->SS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00000001
CP-User data
length indicator
RP-ERROR
RP-Message Type
100 (RP-ERROR MS->SS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
RP-Cause
see 3GPP TS 04.11 subclause 8.2.5.4
RP_User Data
see 3GPP TS 04.11 subclause 8.2.5.3: optional, may be present or not
Length indicator
TP-Data
max 233 octets
CP-DATA (including RP-ERROR SS->MS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00000001
CP-User data
length indicator
RP-ERROR
RP-Message Type
101 (RP-ERROR SS->MS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
RP-Cause
see 3GPP TS 04.11 subclause 8.2.5.4
RP_User Data
see 3GPP TS 04.11 subclause 8.2.5.3 : optional, may be present or not
Length indicator
TP-Data
max 233 octets
CP-DATA (including RP-SMMA MS->SS)
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00000001
CP-User data
length indicator
RP-SMMA
RP-Message Type
110 (RP-SMMA MS->SS)
RP-Message Reference
see 3GPP TS 04.11 subclause 8.2.3
CP-ACK
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00000100
CP-ERROR
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TI value
TI flag
Message type
00010000
CP-Cause
Cause value
see 3GPP TS 04.11 subclause 8.1.4.2 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35 Low battery voltage detection | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.1 Definition | Low battery or shutdown voltage detection is used to trigger inhibition of all RF transmission before the MS supply voltage reaches a level where effective use of the radio frequency spectrum is no longer guaranteed. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.2 Conformance requirement | 1. The MS shall not make ineffective use of the radio frequency spectrum. In no case shall the MS exceed the transmitted levels as defined in 3GPP TS 05.05 for extreme operation.
3GPP TS 05.05, subclause D.2.2.
2. The MS shall inhibit all RF transmission when the power supply voltage is below the manufacturer declared approximate shutdown voltage.
3GPP TS 05.05, subclause D.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.3 Test purpose | 1. To verify that the MS does not make ineffective use of the RF spectrum.
2. To verify that the MS inhibits all RF transmission when the battery voltage falls below the manufacturer declared shutdown level. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.4.1 Initial conditions | The SS transmits a BCCH with a location updating time set to 0,1 hours.
The SS sends a paging request message to the MS.
The MS responds with a channel request message.
The SS sends an immediate assignment message establishing an SDCCH. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.4.2 Procedure | a) The SS gradually reduces the power supply voltage until the MS ceases the production of RF output.
The RF output spectrum shall be monitored for any anomalies while the supply voltage is being reduced.
NOTE 1: The declared approximate shutdown voltage gives an indication of the voltage where the MS will cease RF output.
NOTE 2: If any anomalies occur, then additional testing using the transmitter tests at the voltage where the anomaly occurred is performed to determine in an objective manner, whether or not the conformance requirement is met.
c) After 7 minutes, the SS sends a paging message to the MS.
d) The SS observes whether or not the MS produces any RF output.
This measurement is performed over the relevant transmit band.
The spectrum analyser is set to:
Bandwidth: 3 MHz.
Peak Hold.
e) The SS modifies the location area of the BCCH.
f) For 7 minutes, the SS observes whether or not the MS produces any RF output.
NOTE 3: It is anticipated that the MS might attempt location updating.
g) The MS is switched off and on.
h) The SS pages the MS.
i) The SS observes whether or not the MS produces any RF output. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 35.5 Test requirement | 1. In step a) no anomalies shall occur.
2. In step a), the MS shall cease the production of RF output.
3. In steps d), f) and i), the MS shall not produce any RF output above -30 dBm. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 36 Individual equipment type requirements and interworking - special conformance testing functions | Refer to 3GPP TS 04.14 for complete specification
37 to 39 Void
Void
40 GPRS default conditions, message contents and macros
Editor's note: From Rel-9 the PBCCH and PCCCH are removed from chapter 40.x but temporary test cases may still exist in 51.010 referencing to the macros using PBCCH and PCCCH. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1 Default test conditions | The following default test conditions shall apply if not otherwise stated within an individual test description.
The testcases for higher layers shall use the second set of default test conditions for channel combination v), xi) and xiii) as specified in subclause 40.3.
In the tables following, decimal values will normally be used. Where a hexadecimal value is used, it indicated with an "H". A binary value will be indicated with a "B".
For MSs that cannot be configured to send an exact number of octets in RLC data blocks of uplink data transfer, test cases specifying 'uplink transfer of n octets data' shall be interpreted as ' uplink transfer of at least n octets data', unless otherwise stated in the test case.
Rel-6 network simulation shall apply unless otherwise stated in the test case.
NOTE 1: In case when NC mode is different from NC2 and PBCCH is not present in the cell and where neighbour cells are indicated in the testcase and are indeed activated, the MS shall read system information on the target cell (e.g. SI3, SI4 ) for cell reselection calculations . In these cases, the MS may temporarily suspend ongoing TBF (see 3GPP TS 04.60/3GPP TS 44.060 sub-clause 5.5.1.4.2). Test case implementation should take this into account i.e. that blocks or control messages sent by SS are missed during these SI refreshes.
NOTE 2: In addition:
- When the MS is performing autonomous cell reselection or
- when a PACKET CELL CHANGE ORDER is received by MS and the IMMEDIATE_REL bit is set to "0" or
- when PACKET CELL CHANGE CONTINUE is received by MS and relevant PACKET NEIGHBOUR CELL DATA messages are not received
the MS may continue operation in the old cell and acquire certain system information for the target cell (as per 04.60/44.060). In cases listed above ongoing TBF might be suspended temporarily as well. Test case implementation should take this into account i.e. that blocks or control messages sent by SS are missed during these SI refreshes.
List of affected testcases (by NOTE 2):
42.4.2.3.4, 42.4.4.1, 42.4.4.2, 42.4.4.5, 42.4.5.1, 42.4.5.2, 42.4.5.4, 42.4.5.5, 42.4.5.6, 42.4.5.7, 42.4.5.9, 42.4.6.1, 42.4.8.1.4, 42.4.8.1.6, , 44.2.1.1.7, 44.2.2.1.8, , 44.2.3.1.1a, 44.2.3.1.6, 44.2.3.1.7, 44.2.3.2.8, 44.2.3.2.9, 44.2.7.3.5, 46.2.2.1.5, 47.3.1.1, 47.3.1.2, 47.3.1.3, 47.3.2.1, 47.3.2.2, 47.3.3.1.1, 47.3.3.1.2, 47.3.4.2, 47.4.1.
NOTE 3: ‘One phase access’ test cases may not be fully executed for MS requesting ‘Two phases access’.
The resulting step “If the MS requests two phase access the Test Case is terminated” should be interpreted as “Test case is not applicable for the MS”.
List of affected testcases (by NOTE 3):
41.2.3.4, 41.2.3.5, 41.2.3.6, 41.2.3.7, 41.2.3.8, 41.2.3.9, 41.2.3.10, 41.2.3.11. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1.1 Default settings for cell A | GSM 900
DCS 1 800
General signalling conditions for all carriers
Ciphering
Yes
Yes
General RF-conditions for all carriers
Frequency hopping mode
Non-hopping
Non-hopping
Propagation profile
Static
Static
Downlink Input Level
63 dBµVemf( )
63 dBµVemf( )
Uplink output power
Minimum according to MS power class
Minimum according to MS power class
Serving cell, BCCH/CCCH carrier
Channel ARFCN
20
590
Alternative channels
40 or 60
690 or 830
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
30
650
Alternative channels
110 or 115
760 or 850
Power Control Indicator
0
0
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
5, 80, 90,100, 110,120, 122, 124
515, 600, 700, 780, 810, 870, 875, 885
Alternative channels
15, 85, 95, 105, 115, 126, 128, 130
530, 610, 710, 790, 820, 822, 824, 880
Input level
53 dBµVemf( )
53 dBµVemf( )
Network dependent parameters
Cell identity
0001H
0001H
Mobile country code, MCC
001 (decimal)
001 (decimal)
Mobile network code, MNC
01 (decimal)
01 (decimal)
Location area code, LAC
0001H
0001H
Frequency List
Bit Map 0
Range 512
BCCH allocation sequence number(BA_IND)
0
0
Cell Channel Descriptor
Bit Map 0
Range 512
PLMN colour code, NCC
1
1
BS colour code, BCC
5
5
SMS Cell Broadcast
Not active
Not active
DTX
Not available
Not available
IMSI Attach-detach
MS shall apply IMSI attach and detach procedure
MS shall apply IMSI attach and detach procedure
For Non Combined
CCCH_CONF
000 (1 basic physical channel for CCCH)
000 (1 basic physical channel for CCCH)
BS_AG_BLKS_RES
3 blocks reserved
3 blocks reserved
For Combined
CCCH_CONF
001 (1 basic physical channel for CCCH)
001 (1 basic physical channel for CCCH)
BS_AG_BLKS_RES
2 blocks reserved
2 blocks reserved
BS_PA_MFRMS
6 multiframes
6 multiframes
CELL_BAR_ACCESS
not barred
not barred
Call-reestablishment (RE)
not allowed
not allowed
Emergency Call allowed
Allowed
allowed
Access Control Class (AC)
access for all classes allowed
access for all classes allowed
Radio_Link_Time-out
8
8
T3212 Periodic
0 periodic updating shall not be used
0 periodic updating shall not be used
Access control parameters
Max retrans
1
1
TX-integer
5
5
CELL_RESELECT_HYSTERESIS
12dB
12dB
MS_TXPWR_MAX_CCH
10
10
RXLEV_ACCESS_MIN
Minimum
minimum
NECI
New establishment causes are supported
New establishment causes are supported
ACS (additional reselection param IND)
No additional cell parameters are present in SI messages 7 and 8
No additional cell parameters are present in SI messages 7 and 8
P1 and C2 parameters
C2 parameters not present
C2 parameters not present
POI and POWER OFFSET
N/A
POWER OFFSET Parameter not present
CELL_BAR_QUALIFY
0
0
CELL_RESELECT_OFFSET
0
0
PENALTY_TIME
0
0
TEMPORARY_OFFSET
0
0
BA ARFCN
Both P-GSM and E-GSM ARFCNs are broadcast:
GSM ARFCNs 5, 20, 80, 90, 100, 110, 120, 122, 124 broadcast in SI 2
E-GSM ARFCNs 985, 989, 995, 1010, 1014 broadcast in SI 2bis
ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 broadcast in SI 2.
For multiband tests, the ARFCNs 5, 20, 80, 90, 100, 110, 120, 122, 124 are broadcast in SI 2 of GSM cell and in SI 2ter of DCS cell. The ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 are broadcast in SI 2 of DCS cell and in SI 2ter of GSM cell
GPRS Parameters
RA_CODE
00000101
00000101
ACC_BURST_TY
11 bits burst
11 bits burst
CONTROL_ACK_TYPE
RLC/MAC control block
RLC/MAC control block
NETWORK_CONTROL_ORDER
normal MS control
normal MS control
DRX_TIMER_MAX
non-DRX not supported
non-DRX not supported
PC_MEAS_CHAN
BCCH
BCCH
Network Mode of Operation
network operation mode I
network operation mode I
T3168
2 seconds
2 seconds
T3192
1.5 seconds
1.5 seconds
GPRS Ciphering
Enabled
Enabled
GSM 700, T-GSM 810
PCS 1 900
GSM 850
General signalling conditions for all carriers
Ciphering
Yes
Yes
Yes
General RF-conditions for all carriers
Frequency hopping mode
Non-hopping
Non-hopping
Non-hopping
Propagation profile
Static
Static
Static
Downlink Input Level
63 dBµVemf( )
63 dBµVemf( )
63 dBµVemf( )
Uplink output power
Minimum according to MS power class
Power control level = 10
Minimum according to MS power class
Serving cell, BCCH/CCCH carrier
Channel ARFCN
457
590
147
Alternative channels
462 or 482
690 or 730
167 or 187
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
467
650
157
Alternative channels
487 or 505
750 or 780
197 or 247
Power Control Indicator
0
0
0
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
438, 447, 467, 477, 487, 497, 502, 507
515, 600, 655, 700, 710, 740, 780, 810
137, 157, 177, 197, 207, 217, 227, 237
Alternative channels
452, 465, 485, 495, 505, 492, 496, 509
530, 610, 710, 740, 743, 746, 770,790
142, 212, 222, 232, 236, 239, 242, 249
Input level
53 dBµVemf( )
53 dBµVemf( )
53 dBµVemf( )
Network dependent parameters
Cell identity
0001H
0001H
0001H
Mobile country code, MCC
001 (decimal)
001 (decimal)
001 (decimal)
Mobile network code, MNC
011 (decimal)
011 (decimal)
011 (decimal)
Location area code, LAC
0001H
0001H
0001H
Frequency List
Range 128
Range 512
Range 128
BCCH allocation sequence number(BA_IND)
0
0
0
Cell Channel Descriptor
Range 128
Range 512
Range 128
PLMN colour code, NCC
1
1
1
BS colour code, BCC
5
5
5
SMS Cell Broadcast
Not active
Not active
Not active
DTX
Not available
Not available
Not available
IMSI Attach-detach
MS shall apply IMSI attach and detach procedure
MS shall apply IMSI attach and detach procedure
MS shall apply IMSI attach and detach procedure
For Non Combined
CCCH_CONF
000 (1 basic physical channel for CCCH)
1 basic physical channel for CCCH
000 (1 basic physical channel for CCCH)
BS_AG_BLKS_RES
3 blocks reserved
3 blocks reserved
3 blocks reserved
For Combined
CCCH_CONF
001 (1 basic physical channel for CCCH)
001 (1 basic physical channel for CCCH)
BS_AG_BLKS_RES
2 blocks reserved
2 blocks reserved
BS_PA_MFRMS
6 multiframes
6 multiframes
6 multiframes
CELL_BAR_ACCESS
not barred
Not barred
not barred
Call-reestablishment (RE)
not allowed
Not allowed
not allowed
Emergency Call allowed
Allowed
Allowed
allowed
Access Control Class (AC)
access for all classes allowed
Access for all classes allowed
access for all classes allowed
Radio_Link_Time-out
8
8
8
T3212 Periodic
0 periodic updating shall not be used
0 periodic updating shall not be used
0 periodic updating shall not be used
Access control parameters
Max retrans
1
1
1
TX-integer
5
5
5
CELL_RESELECT_HYSTERESIS
12dB
12dB
12dB
MS_TXPWR_MAX_CCH
10
10
10
RXLEV_ACCESS_MIN
Minimum
Minimum
minimum
NECI
New establishment causes are supported
New establishment causes are supported
New establishment causes are supported
ACS (additional reselection param IND)
No additional cell parameters are present in SI messages 7 and 8
No additional cell parameters are present in SI messages 7 and 8
No additional cell parameters are present in SI messages 7 and 8
C2 parameters
C2 parameters not present
C2 parameters not present
C2 parameters not present
POWER OFFSET
N/A
Parameter not present
N/A
CELL_BAR_QUALIFY
0
0
0
CELL_RESELECT_OFFSET
0
0
0
PENALTY_TIME
0
0
0
TEMPORARY_OFFSET
0
0
0
BA ARFCN
ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 broadcast in SI 2
ARFCNs 515, 590, 600, 655, 700, 710, 740, 780, 810 broadcast in SI 2
ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 broadcast in SI 2.
For multiband tests, the ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 are broadcast in SI 2 of the GSM 700 cell and in SI 2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM700 cell.
For multiband tests, the ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 are broadcast in SI 2 of the GSM 850 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
GPRS Parameters
RA_CODE
00000101
00000101
00000101
ACC_BURST_TY
11 bits burst
11 bits burst
11 bits burst
CONTROL_ACK_TYPE
RLC/MAC control block
RLC/MAC control block
RLC/MAC control block
NETWORK_CONTROL_ORDER
normal MS control
normal MS control
normal MS control
DRX_TIMER_MAX
non-DRX not supported
non-DRX not supported
non-DRX not supported
PC_MEAS_CHAN
BCCH
BCCH
BCCH
Network Mode of Operation
network operation mode I
network operation mode I
network operation mode I
T3168
2 seconds
2 seconds
2 seconds
T3192
1.5 seconds
1.5 seconds
1.5 seconds
GPRS Ciphering
Enabled
Enabled
Enabled |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1.2 Default settings for cell B | The default settings for cell B are identical to those of cell A with the following exceptions:
GSM 900
DCS 1 800
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
5
515
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
60
750
Cell identity
0002H
0002H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
20, 80, 90,100, 110,120,122,124
590, 600, 700, 780, 810, 870, 875, 885
Input level
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
Both P-GSM and E-GSM ARFCNs are broadcast:
GSM 5, 20, 80, 90,100, 110,120, 122, 124 broadcast in SI 2
E-GSM ARFCNs 985, 989, 995, 1010, 1014 broadcast in SI 2bis
515, 590, 600, 700, 780, 810, 870, 875, 885 broadcast in SI 2.
For multiband tests, the ARFCNs 5, 20, 80, 90,100, 110,120, 122, 124 are broadcast in SI 2 of GSM cell and in SI 2ter of DCS cell. The ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 are broadcast in SI 2 of DCS cell and in SI 2ter of GSM cell
GSM 700, T-GSM 810
PCS 1 900
GSM 850
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
447
515
137
Serving cell, PDTCH (PBCCH not present), SDCCH
Channel ARFCN
438
755
242
Cell identity
0002H
0002H
0002H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
438, 457, 467, 477, 487, 497, 502, 507
590, 600, 655, 700, 710, 740, 780, 810
147, 157, 177, 197, 207, 217, 227, 237
Input level
53 dBµVemf( )
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507, 510 broadcast in SI 2
ARFCNs 515, 590, 600, 655, 700, 710, 740, 780, 810 broadcast in SI 2
ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 broadcast in SI 2.
For multiband tests, the ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 are broadcast in SI 2 of the GSM 700 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
For multiband tests, the ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 are broadcast in SI 2 of the GSM 850 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1.3 Default settings for cell C | The default settings for cell C are identical to those of cell A with the following exceptions:
GSM 900
DCS 1 800
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
80
600
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
25
675
Cell identity
0003H
0003H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
5, 20, 90,100, 110,120,122,124
515, 590, 700, 780, 810, 870, 875, 885
Input level
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
Both P-GSM and E-GSM ARFCNs are broadcast:
GSM 5, 20, 80, 90, 100, 110,120, 122, 124 broadcast in SI 2
E-GSM ARFCNs 985, 989, 995, 1010, 1014 broadcast in SI 2bis
ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 broadcast in SI 2.
For multiband tests, the ARFCNs 5, 20, 80, 90,100, 110,120, 122, 124 are broadcast in SI 2 of GSM cell and in SI 2ter of DCS cell. The ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 are broadcast in SI 2 of DCS cell and in SI 2ter of GSM cell
GSM 700, T-GSM 810
PCS 1 900
GSM 850
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
438
600
207
Serving cell, PDTCH (PBCCH not present), SDCCH
Channel ARFCN
447
675
167
Cell identity
0003H
0003H
0003H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
447, 457, 467, 477, 487, 497, 502, 507
515, 590, 655, 700, 710, 740, 780, 810
137, 147, 157, 177, 197, 217, 227, 237
Input level
53 dBµVemf( )
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 broadcast in SI 2
ARFCNs 515, 590, 600, 655, 700, 710, 740, 780, 810 broadcast in SI 2
ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 broadcast in SI 2.
For multiband tests, the ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 are broadcast in SI 2 of the GSM 700 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
For multiband tests, the ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 are broadcast in SI 2 of the GSM 850 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1.4 Default settings for cell D | The default settings for cell D are identical to those of cell A with the following exceptions:
GSM 900
DCS 1 800
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
110
700
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
35
725
Cell identity
0004H
0004H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
5, 20, 80, 90,100,120,122,124
515, 590, 600, 700, 780, 810, 870, 875, 885
Input level
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
Both P-GSM and E-GSM ARFCNs are broadcast:
P-GSM 5, 20, 80, 90, 100, 110, 120, 122, 124 broadcast in SI 2
E-GSM ARFCNs 985, 989, 995, 1010, 1014 broadcast in SI 2bis
ARFCNs 515, 590, 600, 780, 810, 870, 875, 885 broadcast in SI 2.
For multiband tests, the ARFCNs 5, 20, 80, 90,100, 110, 120, 122, 124 are broadcast in SI 2 of GSM cell and in SI 2ter of DCS cell. The ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 are broadcast in SI 2 of DCS cell and in SI 2ter of GSM cell
GSM 700, T-GSM 810
PCS 1 900
GSM 850
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
477
700
217
Serving cell, PDTCH (PBCCH not present), SDCCH
Channel ARFCN
457
725
222
Cell identity
0004H
0004H
0004H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
438, 447, 457, 467, 487, 497, 502, 507
515, 590, 600, 655, 710, 740, 780, 810
137, 147, 157, 177, 197, 207, 227, 237
Input level
53 dBµVemf( )
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 broadcast in SI 2
ARFCNs 515, 590, 600, 655, 700, 710, 740, 780, 810 broadcast in SI 2
ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 broadcast in SI 2.
For multiband tests, the ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 are broadcast in SI 2 of the GSM 700 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
For multiband tests, the ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 are broadcast in SI 2 of the GSM 850 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1.5 Default settings for cell E | The default settings for cell E are identical to those of cell A with the following exceptions:
GSM 900
DCS 1 800
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
90
780
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
45
735
Cell identity
0005H
0005H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
5, 20, 80, 100, 110,120,122,124
515, 590, 600, 700, 810, 870, 875, 885
Input level
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
Both P-GSM and E-GSM ARFCNs are broadcast:
GSM ARFCNs 5, 20, 80, 90, 100, 110,120, 122, 124 broadcast in SI 2
E-GSM ARFCNs 985, 989, 995, 1010, 1014 broadcast in SI 2bis
ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 broadcast in SI 2.
For multiband tests, the ARFCNs 5, 20, 80, 90, 100, 110,120, 122, 124 are broadcast in SI 2 of GSM cell and in SI 2ter of DCS cell. The ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 are broadcast in SI 2 of DCS cell and in SI 2ter of GSM cell
GSM 700, T-GSM 810
PCS 1 900
GSM 850
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
467
780
227
Serving cell, PDTCH (PBCCH not present), SDCCH
Channel ARFCN
487
735
232
Cell identity
0005H
0005H
0005H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
438, 447, 457, 477, 487, 497, 502, 507
515, 590, 600, 655, 700, 710, 740, 810
137, 147, 157, 177, 197, 207, 217, 237
Input level
53 dBµVemf( )
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 broadcast in SI 2
ARFCNs 515, 590, 600, 655, 700, 710, 740, 780, 810 broadcast in SI 2
ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 broadcast in SI 2.
For multiband tests, the ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 are broadcast in SI 2 of the GSM 700 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
For multiband tests, the ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 are broadcast in SI 2 of the GSM 850 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.1.6 Default settings for cell F | The default settings for cell F are identical to those of cell A with the following exceptions:
GSM 900
DCS 1 800
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
120
810
Serving cell, PDTCH (PBCCH not present), SDCCH, TCH
Channel ARFCN
55
775
Cell identity
0006H
0006H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
5, 20, 80, 90,100, 110,122,124
515, 590, 600, 700, 780, 870, 875, 885
Input level
53 dBµVemf( )
53 dBµVemf( )
BA ARFCN
Both P-GSM and E-GSM ARFCNs are broadcast:
GSM ARFCNs 5, 20, 80, 90,100, 110, 120, 122, 124 broadcast in SI 2
E-GSM ARFCNs 985, 989, 995, 1010, 1014 broadcast in SI 2bis
ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 broadcast in SI 2.
For multiband tests, the ARFCNs 5, 20, 80, 90,100, 110, 120, 122, 124 are broadcast in SI 2 of GSM cell and in SI 2ter of DCS cell. The ARFCNs 515, 590, 600, 700, 780, 810, 870, 875, 885 are broadcast in SI 2 of DCS cell and in SI 2ter of GSM cell
GSM 700, T-GSM 810
PCS 1 900
GSM 850
Downlink Input Level
53 dBµVemf()
53 dBµVemf()
53 dBµVemf()
Serving cell, BCCH/CCCH carrier
Channel ARFCN
487
810
237
Serving cell, PDTCH (PBCCH not present), SDCCH
Channel ARFCN
477
775
187
Cell identity
0006H
0006H
0006H
Neighbouring cells BCCH/CCCH carriers
Channel ARFCN
438, 447, 457, 467, 477, 497, 502, 507
515, 590, 600, 655, 700, 710, 740, 780
137, 147, 157, 177, 197, 207, 217, 227
Input level
53 dBµVemf()
53 dBµVemf()
53 dBµVemf()
BA ARFCN
ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 broadcast in SI 2
ARFCNs 515, 590, 600, 655, 700, 710, 740, 780, 810 broadcast in SI 2
ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 broadcast in SI 2.
For multiband tests, the ARFCNs 438, 447, 457, 467, 477, 487, 497, 502, 507 are broadcast in SI 2 of the GSM 700 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
For multiband tests, the ARFCNs 137, 147, 157, 177, 197, 207, 217, 227, 237 are broadcast in SI 2 of the GSM 850 cell and SI2ter of the PCS1900 cell. The 515, 590, 600, 655, 700, 710, 740, 780, 810 are broadcast in SI 2 of the PCS1900 cell and SI 2ter of the GSM850 cell.
40.1a EC-GSM-IoT Default test conditions
The support of EC-GSM-IoT is indicated by the presence of EC-SCH
The EC-SCH INFORMATION message sent on EC-SCH consists of the following information:
RACH Access Control
0
A mobile station using CC1 in both the uplink and downlink shall not use timeslot 0
EC- BCCH CHANGE MARK
000B
Implicit Reject Status
00B
no barring |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2 Default message contents | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1 System Information messages | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1.1 Cell A | With the SYSTEM INFORMATION messages, the information elements are listed in alphabetic order (this is because some information elements occur in several SYSTEM INFORMATION types).
NOTE: BCCH can send 1 instance of SYSTEM INFORMATION 13.
40.2.1.1.1 Contents of information elements in SYSTEM INFORMATION TYPE 1 to 13 messages.
(CBCH) Channel Description
Not present.
(CBCH) Mobile Allocation
Not present.
Cell Channel Description
- Format identifier
For GSM 900:
Bit map 0.
For DCS 1 800 and PCS 1 900:
Range 512.
For GSM 700 and GSM 850:
Range 128.
- Cell Allocation ARFCN
For GSM 900:
Channel Numbers 10, 37, 40, 50, 60 and 80.
For DCS1800:
Channel Numbers 520, 530, 540 and 550.
For PCS 1 900:
Channel Numbers 520, 530, 540 and 550
For GSM 700, T-GSM 810:
Channel Numbers 447, 457, 477, 487, 497 and 509.
For GSM 850:
Channel Numbers 159, 161, 163, 165, 187 and 207.
Cell Identity
- Cell Identity Value
0001Hex
Cell Options
- Power Control Indicator
Power Control Indicator is not set.
- DTX Indicator
MS shall not use DTX.
- Radio_Link_Timeout
8 SACCH blocks.
Cell Selection Parameters
- Cell_Reselect_Hysteresis
12 dB.
- MX_TXPWR_MAX_CCH
Power control level 10.
- ACS
For SI3, spare (set to '0'); for SI4, No additional cell parameters are present in SYSTEM INFORMATION messages 7 and 8.
- NECI
New establishment causes are supported.
- RXLEV_ACCESS_MIN
Minimum level.
Control Channel Description
- MSCR bit
1 (MSC is R99 onwards)
- Attach-Detach allowed
MS shall apply IMSI attach and detach procedure.
For Non Combined
- BS_AG_BLKS_RES
3 blocks reserved for access grant.
- CCCH_CONF
000 (1 basic physical channel used for CCCH, not combined with SDCCHs.)
For Combined
- BS_AG_BLKS_RES
2 blocks reserved for access grant.
- CCCH_CONF
001 (1 basic physical channel used for CCCH, combined with SDCCHs.)
- BS_PA_MFRMS
6 multiframe periods for transmission of paging messages.
- T3212 Time-out value
0
L2 pseudo length
- System information 1
21
- System information 2
22
- System information 3
18
- System information 4
12
- System information 7
1
- System information 8
1
- System information 13
0
- System information 14
0
- System information 15
0
Location Area Identification
- Mobile Country Code
001 (Decimal)
- Mobile Network Code
01 (Decimal) for GSM 900 and DCS 1 800
011 (Decimal) for GSM 700, T-GSM 810, GSM 850 and PCS 1 900
- Location Area Code
0001(Hex)
Message Type
- System information 1
00011001 (Binary)
- System information 2
00011010 (Binary)
- System information 2bis
00000010 (Binary)
- System information 2ter
00000011 (Binary)
- System information 3
00011011 (Binary)
- System information 4
00011100 (Binary)
- System information 5
00011101 (Binary)
- System information 5bis
00000101 (Binary)
- System information 5ter
00000110 (Binary)
- System information 7
00011111 (Binary)
- System information 8
00011000 (Binary)
- System information 13
00000000 (Binary)
SI 14 and SI15 are only applicable for GSM 710 and T-GSM 810 bands (not for GSM 750 band):
- System information 14
00000001 (Binary)
- System information 15
01000011 (Binary)
Neighbour Cells Description
For SI 2
- Format identifier
For GSM 900: Bit map 0.
For DCS 1 800 and PCS 1 900: Range 512.
For GSM 700 and GSM 850: Range 128.
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122 and 124.
For DCS 1 800:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875 and 885.
For PCS 1 900
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780 and 810.
For GSM 700, T-GSM 810:
Channel numbers 438, 447, 457, 467, 477, 487, 497, 502 and 507.
For GSM 850:
Channel numbers 137,147, 157, 177, 197, 207, 217, 227 and 237.
- EXT-IND
For GSM 900, this IE carries only part of the BA.
For DCS 1 800, PCS 1 900, GSM 700 and GSM 850, this IE carries complete BA.
Neighbour Cells Description
SI 2bis for GSM 900
- Format identifier
For GSM 900: Range 256
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 985, 989, 995, 1010 and 1014.
- EXT-IND
This IE carries only part of the BA.
Neighbour Cells Description 2
SI2ter
- Multiband Reporting
00 (Binary)
- Format identifier
For GSM 900: Range 512
For DCS 1 800: Range 1024
For PCS 1 900: Range 1024
For GSM 700, T-GSM 810: Range 512
For GSM 850: Range 512
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875 and 885.
For DCS 1800:
Channel Numbers 5, 20, 80, 90, 100, 110, 120, 122 and 124.
For PCS 1900:
GSM 850 Channel numbers 137, 147, 157, 177, 197, 207, 217, 227 and 237 (for a GSM 850/PCS 1900 Network); or
GSM 700, T-GSM 810 Channel numbers 438, 447, 457, 467, 477, 487, 497, 502 and 507 (for a GSM 700, T-GSM 810 / PCS 1900 Network).
For GSM 700, T-GSM 810:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780 and 810.
For GSM 850:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780 and 810.
NCC Permitted
0000 0010
RACH Control Parameters
- Max Retrans
Max 1 retrans.
- Tx-integer
5 slots used.
- Cell Barred for Access
Cell is not barred.
- Call Reestablishment Allowed
Not allowed.
- Access Control Class
Access is not barred.
- Emergency Call allowed
Yes.
SI 1 Rest Octets
- {0|1<NCH Position>}
0 (NCH Position not present)
- BandIndicator
L for GSM 700 or T-GSM 810 or GSM 850 or GSM 900 or DCS 1 800
H for PCS 1 900
- spare padding
Spare Padding
SI 2bis Rest Octets
Spare Padding
SI 2ter Rest Octets
Spare Padding
SI 3 Rest Octets
- Optional Selection Parameters
L (no optional selection parameters)
- Optional Power Offset
L (no optional power offset)
- System Information 2ter Indicator
L (for GSM 700 or T-GSM 810 or GSM 850 or GSM 900 or DCS 1 800 or PCS 1 900 single band tests, no SI2ter exists)
Or
H (for multiband tests, i.e GSM900/GSM1800 or GSM850/GSM1900, SI2ter does exists)
- Early Classmark Sending Control
H (perform early classmark sending)
- Scheduling if and where
L(no system information type 9)
- GPRS Indicator
H (GPRS supported)
- RA COLOUR
001(Binary)
- SI13 POSITION
On BCCH Norm
- spare padding
Spare Padding
SI 4 Rest Octets
- Optional Selection Parameters
L (no optional selection parameters)
- Optional Power Offset
L (no optional power offset)
- GPRS Indicator
H (GPRS supported)
- RA COLOUR
001(Binary)
- SI13 POSITION
On BCCH Norm
- spare padding
Spare Padding
SI 7 Rest Octets
Same as SI 4 Rest Octets
SI 8 Rest Octets
Same as SI 4 Rest Octets
SI 13 Rest Octets
-
H (SI 13 Rest Octets are not spare)
- BCCH_CHANGE_MARK
000
- SI_CHANGE_FIELD
0 Update of unspecified message
- {0|1
GPRS Mobile Allocation IE present
- SI13 CHANGE MARK
00
-HSN
000000 Sequence 0
-{0|1<RFL number list>}
0 Number list not present
-{0
0 using MA BITMAP
-MA_LENGTH
000101 (for GSM 700, T-GSM 810, GSM 850 and GSM900).
000011 (for DCS 1 800 and PCS 1 900).
-MA_BITMAP}
001111 4 belonging (for GSM 700, T-GSM 810, GSM 850 and GSM900).
1111 4 belonging (for DCS 1 800 and PCS 1 900).
- {0 | 1
0 (PBCCH not present in cell)
- RAC
00000101(Binary)
-SPGC_CCCH_SUP
1 supported
-PRIORITY_ACCESS_THR
11 PA allowed for priority level 1 to 4
-NETWORK_CONTROL_ORDER
00 NC0
-GPRS Cell Options
Present
-Network Mode of Operation
NMO I
-T3168
2 seconds
-T3192
1.5 seconds
-DRX_TIMER_MAX
000 Non-DRX not supported
-ACCESS_BURST_TYPE
1 Use 11 bits access burst
-CONTROL_ACK_TYPE
1 RLC/MAC control block
-BS_CV_MAX
0111 value 7
-PAN_DEC
011 value 3
-PAN_INC
011 value 3
-PAN_MAX
010 Max value for counter N3102=12
-Optional extension information
0 Extension information not present
For R99/Rel 4/Rel 6 network simulation:
Optional extension information
1 Extension information present
- Extension length
R99: 000011
Rel 4: 000101
Rel 6: 001001
- {0|1 <Extension Information>}
0 EGPRS not supported by the cell.
- PFC_FEATURE_MODE
0 Packet Flow Context Procedures not supported
- DTM_SUPPORT
Default:
0.....The cell does not support DTM procedures
For DTM test cases:
1.....The cell supports DTM procedures
- BSS_PAGING_COORDINATION
0 Circuit-Switched paging coordination not supported
in cell
For Rel 4 network simulation
- CCN_ACTIVE
0 CCN is disabled in the cell
- NW_EXT_UTBF
0 Ext UL TBF not supported in the cell
For Rel 6 network simulation
- MULTIPLE_TBF_CAPABILITY
0 Cell does not support multiple TBF procedures
- EXT_UTBF_NO_DATA
0 MS shall send a PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network
- DTM_ENHANCEMENTS_CAPABILITY
0 Cell does not support enhanced DTM CS establishment and enhanced DTM CS release procedures
- { 0 | 1 }
0 -- MBMS procedures not supported by the cell
End Rel 6
End Rel 4
End R99
-GPRS Power Control Parameters
Present
-ALPHA
0000 Alpha = 0.0
-T_AVG_W
01100 value 12
-T_AVG_T
01100 value 12
-PC_MEAS_CHAN
0 BCCH
-N_AVG_I
0111 value 7
For R99/Rel 4/Rel 6 network simulation:
- Additions in R99
H
- SGSNR bit
1 SGSN is Release '99 onwards
- Additions in Rel 4
H
- SI_STATUS_IND bit
0 PACKET SI STATUS message not supported
- Additions in Rel 6
H
{LB_MS_TXPWR_MAX_CCH}
1 LB_MS_TXPWR_MAX_CCH present
- LB_MS_TXPWR_MAX_CCH
01010
- SI2n_SUPPORT
00
For Rel 11 network simulation
- SI_CHANGE_ALT
L Disabled in the cell
For Rel 13 network simulation
- PEO_DSC
0 PEO disabled
- FCC
000B (if PEO enabled)
- C1_DELTA
0 MS to use default value from 45.008
End Rel 13
End Rel 11
End Rel 6
End Rel 4
End R99
-spare padding
Spare Padding
SI 14 Rest Octets
Only applicable for GSM 710 and T-GSM 810 bands
- SI14_INDEX
0
- SI14_COUNT
0
- DM_CHANGE_MARK
0
- DYNAMIC ARFCN MAPPING Description
Present
- GSM_Band
0110 for GSM 710 band
0111 for T-GSM 810 band
- ARFCN_FIRST |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 110110110 ARFCN 438 | - BAND_OFFSET
000000000
- ARFCN_RANGE
1001010 74 channels |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1.2 Cell B | The contents of SYSTEM INFORMATION TYPE 1 to 13 messages for cell B are identical to those of cell A with the following exceptions:
Cell Channel Description
- Format Identifier
For GSM 900:
Bit map 0.
For DCS 1800 and PCS 1900:
Range 512.
For GSM 700, T-GSM 810 and GSM 850:
Range 128.
- Cell Allocation ARFCN
For GSM 900:
Channel Numbers 15, 70, 97, 100, 110, 120
For DCS 1800:
Channel numbers 560, 570, 580, 585.
For PCS 1900:
Channel numbers 560, 570, 580, 585.
For GSM 700, T-GSM 810:
Channel numbers 439, 441, 443, 445.
For GSM 850:
Channel numbers 179, 181, 183, 185
Cell Identity
- Cell Identity Value
0002H
Neighbour Cells Description
For SI 2
- Format identifier
For GSM 900: Bit map 0.
For DCS 1800 and PCS 1900: Range 512.
For GSM 700, T-GSM 810 and GSM 850: Range 128.
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For DCS 1800:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885
For PCS 1900
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 700, T-GSM 810:
Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507
For GSM 850:
Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237
Neighbour Cells Description 2
SI2ter
- Multiband Reporting
00 (Binary)
- Format identifier
For GSM 900: Range 512
For DCS 1800: Range 1024
For PCS 1900: Range 1024
For GSM 700, T-GSM 810: Range 512
For GSM 850: Range 512
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885.
For DCS 1800:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For PCS 1900:
GSM 850 Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237 (for a GSM 850/PCS 1900 Network); or
GSM 700, T-GSM 810 Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507 (for a GSM 700, T-GSM 810 / PCS 1900 Network).
For GSM 700, T-GSM 810:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
For GSM 850:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
SI 13 Rest Octets
present
-MA_LENGTH
000101 (for GSM900).
000011 (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900).
-MA_BITMAP}
001111 4 belonging (for GSM900).
1111 4 belonging (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1.3 Cell C | The contents of SYSTEM INFORMATION TYPE 1 to 13 messages for cell C are identical to those of cell A with the following exceptions:
Cell Channel Description
- Format Identifier
For GSM 900:
Bit map 0.
For DCS 1800 and PCS 1900:
Range 512.
For GSM 700, T-GSM 810 and GSM 850:
Range 128.
- Cell Allocation ARFCN
For GSM 900:
Channel Numbers 65, 75, 85, 95, 105 and 115.
For DCS 1800:
Channel numbers 605, 610, 620 and 630
For PCS 1900:
Channel numbers 605, 610, 620 and 630
For GSM 700, T-GSM 810:
Channel numbers 449, 451, 453, 455
For GSM 850:
Channel Numbers 169, 171, 173, 175.
Cell Identity
- Cell Identity Value
0003H
Neighbour Cells Description
For SI 2
- Format identifier
For GSM 900: Bit map 0.
For DCS 1800 and PCS 1900: Range 512.
For GSM 700, T-GSM 810 and GSM 850: Range 128.
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For DCS 1800:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885
For PCS 1900
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 700, T-GSM 810:
Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507
For GSM 850:
Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237
Neighbour Cells Description 2
SI2ter
- Multiband Reporting
00 (Binary)
- Format identifier
For GSM 900: Range 512
For DCS 1800: Range 1024
For PCS 1900: Range 1024
For GSM 700, T-GSM 810: Range 512
For GSM 850: Range 512
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885.
For DCS 1800:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For PCS 1900:
GSM 850 Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237 (for a GSM 850/PCS 1900 Network); or
GSM 700, T-GSM 810 Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507 (for a GSM 700, T-GSM 810 / PCS 1900 Network).
For GSM 700, T-GSM 810:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 850:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
SI 13 Rest Octets
present
-MA_LENGTH
000101 (for GSM900).
000011 (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900).
-MA_BITMAP}
001111 4 belonging (for GSM900).
1111 4 belonging (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1.4 Cell D | The contents of SYSTEM INFORMATION TYPE 1 to 13 messages for cell D are identical to those of cell A with the following exceptions:
Cell Channel Description
- Format Identifier
For GSM 900:
Bit map 0.
For DCS 1800 and PCS 1900:
Range 512.
For GSM 700, T-GSM 810 and GSM 850:
Range 128.
- Cell Allocation ARFCN
For GSM 900:
Channel Numbers 22, 42, 62, 82, 102 ,122.
For DCS 1800:
Channel numbers 640, 655, 660, 670
For PCS 1900:
Channel numbers 640, 655, 660, 670
For GSM 700, T-GSM 810:
Channel numbers 459, 461, 463, 465
For GSM 850:
Channel numbers 139, 141, 143, 145.
Cell Identity
- Cell Identity Value
0004H
Neighbour Cells Description
For SI 2
- Format identifier
For GSM 900: Bit map 0.
For DCS 1800 and PCS 1900: Range 512.
For GSM 700, T-GSM 810 and GSM 850: Range 128.
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For DCS 1800:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885
For PCS 1900
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 700, T-GSM 810:
Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507.
For GSM 850:
Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237
Neighbour Cells Description 2
SI2ter
- Multiband Reporting
00 (Binary)
- Format identifier
For GSM 900: Range 512
For DCS 1800: Range 1024
For PCS 1900: Range 1024
For GSM 700, T-GSM 810: Range 512
For GSM 850: Range 512
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885.
For DCS 1800:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For PCS 1900:
GSM 850 Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237 (for a GSM 850/PCS 1900 Network); or
GSM 700, T-GSM 810 Channel numbers 437, 447, 457, 467, 477, 487, 497, 502, 507. (for a GSM 700, T-GSM 810 / PCS 1900 Network).
For GSM 700, T-GSM 810:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 850:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
SI 13 Rest Octets
present
-MA_LENGTH
000101 (for GSM900).
000011 (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900).
-MA_BITMAP}
001111 4 belonging (for GSM900).
1111 4 belonging (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1.5 Cell E | The contents of SYSTEM INFORMATION TYPE 1 to 13 messages for cell E are identical to those of cell A with the following exceptions:
Cell Channel Description
- Format Identifier
For GSM 900:
Bit map 0.
For DCS 1800 and PCS 1900:
Range 512.
For GSM 700, T-GSM 810 and GSM 850:
Range 128.
- Cell Allocation ARFCN
For GSM 900:
Channel Numbers 12, 32, 52, 72, 92, 112
For DCS 1800:
Channel numbers 680, 690, 705, 710
For PCS 1900:
Channel numbers 680, 690, 705, 710
For GSM 700, T-GSM 810:
Channel numbers 489, 491, 493, 495
For GSM 850:
Channel numbers 149, 151, 153, 155
Cell Identity
- Cell Identity Value
0005H
Neighbour Cells Description
For SI 2
- Format identifier
For GSM 900: Bit map 0.
For DCS 1800 and PCS 1900: Range 512.
For GSM 700, T-GSM 810 and GSM 850: Range 128.
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For DCS 1800:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885
For PCS 1900
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 700, T-GSM 810:
Channel numbers 438, 447, 467, 457, 477, 487, 497, 502, 507
For GSM 850:
Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237
Neighbour Cells Description 2
SI2ter
- Multiband Reporting
00 (Binary)
- Format identifier
For GSM 900: Range 512
For DCS 1800: Range 1024
For PCS 1900: Range 1024
For GSM 700, T-GSM 810: Range 512
For GSM 850: Range 512
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 515, 590, 600, 700, 780, 810 870, 875, 885.
For DCS 1800:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For PCS 1900:
GSM 850 Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237 (for a GSM 850/PCS 1900 Network); or
GSM 700, T-GSM 810 Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507 (for a GSM 700, T-GSM 810 / PCS 1900 Network).
For GSM 700, T-GSM 810:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
For GSM 850:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
SI 13 Rest Octets
present
-MA_LENGTH
000101 (for GSM900).
000011 (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900).
-MA_BITMAP}
001111 4 belonging (for GSM900).
1111 4 belonging (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 40.2.1.6 Cell F | The contents of SYSTEM INFORMATION TYPE 1 to 13 messages for cell F are identical to those of cell A with the following exceptions:
Cell Channel Description
- Format Identifier
For GSM 900:
Bit map 0.
For DCS 1800 and PCS 1900:
Range 512.
For GSM 700, T-GSM 810 and GSM 850:
Range 128.
- Cell Allocation ARFCN
For GSM 900:
Channel Numbers 7, 27, 47, 67, 87, 107
For DCS 1800:
Channel numbers 720, 730, 740, 770
For PCS 1900:
Channel numbers 720, 730, 740, 750
For GSM 700, T-GSM 810:
Channel numbers 479, 481, 483, 485
For GSM 850:
Channel numbers 189, 191, 193, 195
Cell Identity
- Cell Identity Value
0006H
Neighbour Cells Description
For SI 2
- Format identifier
For GSM 900: Bit map 0.
For DCS 1800 and PCS 1900: Range 512.
For GSM 700, T-GSM 810 and GSM 850: Range 128.
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For DCS 1800:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885
For PCS 1900
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810
For GSM 700, T-GSM 810:
Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507
For GSM 850:
Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237
Neighbour Cells Description 2
SI2ter
- Multiband Reporting
00 (Binary)
- Format identifier
For GSM 900: Range 512
For DCS 1800: Range 1024
For PCS 1900: Range 1024
For GSM 700, T-GSM 810: Range 512
For GSM 850: Range 512
- BCCH Allocation Sequence
0
- BCCH Allocation ARFCN
For GSM 900:
Channel numbers 515, 590, 600, 700, 780, 810, 870, 875, 885.
For DCS 1800:
Channel numbers 5, 20, 80, 90, 100, 110, 120, 122, 124.
For PCS 1900:
GSM 850 Channel numbers 137, 147, 157, 177, 197, 207, 217, 227, 237 (for a GSM 850/PCS 1900 Network); or
GSM 700, T-GSM 810 Channel numbers 438, 447, 457, 467, 477, 487, 497, 502, 507 (for a GSM 700, T-GSM 810 / PCS 1900 Network).
For GSM 700, T-GSM 810:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
For GSM 850:
Channel numbers 515, 590, 600, 655, 700, 710, 740, 780, 810.
SI 13 Rest Octets
present
-MA_LENGTH
000101 (for GSM900).
000011 (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900).
-MA_BITMAP}
001111 4 belonging (for GSM900).
1111 4 belonging (for GSM 700, T-GSM 810, GSM 850, DCS 1800 and PCS 1900). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.