26.14.7 VGCS-VBS / Error Handling

3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS

26.14.7.1 VGCS-VBS / Error Handling / short message length, unknown message type and TI

26.14.7.1.1 Conformance requirement

1. Whenever a message is received specifying a transaction identifier which is not recognised as relating to an active transaction, if COMM = T, the MS shall send a STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and including, if possible, as diagnostics the complete message received (this may not be possible, e.g. due to length restrictions). and remain idle.

2. If COMM = T, the MS shall answer to a message received with TI value "111" by sending a STATUS message with same TI value, cause "invalid transaction identifier value", and including, if possible, as diagnostics the complete message received (this may not be possible, e.g. due to length restrictions).

3. When a message is received that is too short to contain a complete message type information element, that message shall be ignored.

4. If the GCC or BCC in the MS receives a message with message type not defined for the PD or not implemented by the receiver, the MS shall ignore the message except for the fact that, if COMM = T, it shall return a STATUS message with cause "message type non-existent or not implemented" and including as diagnostics the message type of the message received.

5. If the GCC or BCC in the MS receives a message not compatible with the protocol state, the MS shall ignore the message except for the fact that , if COMM = T, it shall return a STATUS message with cause " message type not compatible with protocol state" and including as diagnostic the message type of the message received.

6. When a message with semantically incorrect contents is received, the foreseen reaction of the procedural part are performed. If however no such reactions are specified, the MS shall ignore the message except for the fact that, if COMM = T, it returns a STATUS message with cause value "semantically incorrect message" and including, if possible, as diagnostics the complete message received (this may not be possible).

Reference(s)

3GPP TS 04.68 subclauses 7.2, 7.3, 7.4 and 7.8.

3GPP TS 04.69 subclauses 7.2, 7.3, 7.4 and 7.8.

26.14.7.1.2 Test purpose

To verify that:

1. Whenever a message is received specifying a transaction identifier which is not recognised as relating to an active transaction, if COMM = T, the MS sends a STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value and including, if possible, as diagnostics the complete message received (this may not be possible, e.g., due to length restrictions).

2. If COMM = T, the MS answers to a message received with TI value "111" by sending a STATUS message with same TI value, cause "invalid transaction identifier value", and including, if possible, as diagnostics the complete message received (this may not be possible, e.g., due to length restrictions).

3. When a message is received that is too short to contain a complete message type information element, that message is ignored.

4. If the GCC or BCC in the MS receives a message with message type not defined for the PD or not implemented by the receiver, the MS ignores the message. In addition, if COMM = T, it returns a STATUS message with cause "message type non-existent or not implemented" and including as diagnostics the message type of the message received.

5. If the GCC or BCC in the MS receives a message not compatible with the protocol state, the MS ignores the message. In addition, if COMM = T, it returns a STATUS message with cause " message type not compatible with protocol state" and including as diagnostic the message type of the message received.

6. When a message containing semantically incorrect contents is received and no reactions are specified in the procedural part, the MS ignores the message. In addition, if COMM = T, the MS returns a STATUS message with cause value "semantically incorrect message" and as diagnostics, including the complete message received, if possible (this may not be possible).

26.14.7.1.3 Method of test

Initial Conditions

System Simulator

1 cell with default parameters for ASCI testing.

Mobile Station:

The MS is in MM-state "idle, updated" with a TMSI allocated.

Specific PICS statements:

– Support VGCS originating (TSPC_AddInfo_VGCS_Originating)

– Support VGCS talking (TSPC_AddInfo_VGCS_Talking)

– Support VBS originating (TSPC_AddInfo_VBS_Originating)

PIXIT Statements:

–

Foreseen Final State of the MS

MM-state "Idle, updated".

Test Procedure

If the MS supports VGCS/VBS originating, the test starts from step 1, otherwise if the MS supports VGCS talking the test starts from step 30. If the MS supports VBS originating but no VGCS originating nor VGCS talking, the test stops on step 24.

The MS is requested to initiate a VGCS/VBS call with setup procedure. After the MS sends SETUP message, the SS sends incorrect CONNECT messages which contains incorrect TI flag or incorrect TI value or TI value set to ‘111’B. It is checked that the MS ignores these messages and responds with STATUS messages containing cause #81. The SS sends a message which is too short to contain a complete message. It is checked that the MS ignores this short message. Finally the SS sends a undefined message, a message not compatible with current protocol state and a message semantically incorrect. It is checked that the MS ignores these messages and returns STATUS messages containing cause #97, #98, #95 respectively. The following steps is applicable to the MS supporting VGCS talking. The MS is brought into group transmit mode. The SS sends GET STATUS message with TI=’1001’B, the MS responds with STATUS message containing state U2sr, then the SS sends GET STATUS messages containing TI= ‘1111’B or ‘1010’B. It is checked that the MS ignores these messages and responds with STATUS messages containing cause #81.

Maximum Duration of Test

5 minutes.

Expected Sequence

The step 30 -46 are performed if the MS supports VGCS.

Step	Direction	Message	Comments
0	MS		The MS is in idle mode.
1	MS		MMI action to initiate VGCS/VBS call using setup procedure.
2	MS -> SS	CHANNEL REQUEST
3	SS -> MS	IMMEDIATE ASSIGNMENT	a TCH/FS
4	MS -> SS	CM SERVICE REQUEST	L2: SABM / UA
5	SS -> MS	CM SERVICE ACCEPT
6	MS -> SS	SETUP
7	SS -> MS	CONNECT	flag of TI set to ‘0’B, value of TI is the same as that of SETUP message in step 6.
8	MS -> SS	STATUS	cause #81, "invalid transaction id value".
9	SS -> MS	CONNECT	flag of TI set to ‘1’B, value of TI is different from that of SETUP message in step 6.
10	MS -> SS	STATUS	cause #81, value of TI is that of step 9.
11	SS -> MS	CONNECT	value of TI set to ‘111’B.
12	MS -> SS	STATUS	cause #81, value of TI is ‘111’B
13	SS -> MS	CONNECT	too short message without Call Reference and Originator Indication.
14	SS -> MS	GET STATUS
15	MS -> SS	STATUS	state U1 ORIG=T COMM=T D-ATT=F U-ATT=F.
16	SS -> MS	UNDEF MESSAGE TYPE	see specific message contents
17	MS -> SS	STATUS	cause #97, "message type non-existent or not implemented".
18	SS -> MS	TERMINATION REJECT
19	MS -> SS	STATUS	cause #98, "message type not compatible with the protocol state".
20	SS -> MS	CONNECT	value of Originator Indication set to not originator
21	MS -> SS	STATUS	cause #95, "Semantically incorrect message".
22	SS -> MS	TERMINATION
23	SS -> MS	CHANNEL RELEASE	The MS releases L2 multiple frame link L2:DISC/UA.
30	SS -> MS	NITIFICATION/NCH	with a description of VGCS channel and a VGCS call reference active in the MS
31	MS		MMI action to join the call
32	SS -> MS	UPLINK FREE
33	MS		MMI action to request to access uplink
34	MS -> SS	UPLINK ACCESS
35	MS -> SS	UPLINK ACCESS
36	SS -> MS	UPLINK BUSY
37	SS -> MS	VGCS UPLINK GRANT	Reference to step 34
38	MS -> SS	TALKER INDICATION	L2: SABM / UA
39	SS -> MS	GET STATUS	TI = ‘1001’B, GCC of the MS will take this value as the TI of the group call
40	MS -> SS	STATUS	state U2sr
41	SS -> MS	GET STATUS	TI=’1111’B
42	MS -> SS	STATUS	cause #81, value of TI is ‘111’B
43	SS -> MS	GET STATUS	TI=’1010’B
44	MS -> SS	STATUS	cause #81, value of TI is ‘010’B
45	SS -> MS	UPLINK RELEASE
46	SS -> MS	CHANNEL RELEASE	UI format

Specific message contents:

UNDEF MESSAGE TYPE

Information Element	value/remark
Protocol Discriminator	‘0000’B if the test is for VGCS; ‘0001’B if the test is for VBS.
Message Type	‘0x110111’B
Group call reference	PICS/PIXIT
Originator indication	Originator
Spare half octet

26.14.7.2 VGCS-VBS / Error Handling / incorrect information elements

26.14.7.2.1 Conformance requirement

1. When on receipt of a message containing "imperative message part" error or "missing mandatory IE" error or syntactically incorrect mandatory IE’s or unknown IE’s encoded as "comprehension required" or out of sequence IE’s encoded as "comprehension required", the MS shall ignore the message except for the fact that, if COMM = T, it shall return a STATUS message with cause "invalid mandatory information" and including, if possible, as diagnostics the complete message received.

2. The GCC or BCC in the MS shall ignore all unknown information elements not encoded as "comprehension required" in the non-imperative part.

3. The GCC or BCC in the MS shall ignore all out of sequence information elements not encoded as "comprehension required" in the non-imperative part.

4. The GCC or BCC in the MS shall ignore all syntactically incorrect optional information elements in the non-imperative part.

5. If an information element with format T, TV, or TLV is repeated in a message in which repetition of the information element is not specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored.

Reference(s)

3GPP TS 04.68 subclauses 7.5, 7.6 and 7.7.

3GPP TS 04.69 subclauses 7.5, 7.6 and 7.7.

26.14.7.2.2 Test purpose

To verify that:

1. On receipt of a message containing "imperative message part" error or "missing mandatory IE" error or syntactically incorrect mandatory IE’s or unknown IE’s encoded as "comprehension required" or out of sequence IE’s encoded as "comprehension required", the MS ignores the message. In addition, if COMM = T, the MS returns a STATUS message with cause "invalid mandatory information" and including, if possible, as diagnostics the complete message received.

2. The MS ignores unknown information elements not encoded as "comprehension required" in the non-imperative part.

3. The MS ignores out of sequence information elements not encoded as "comprehension required" in the non‑imperative part.

4. The MS ignores syntactically incorrect optional information elements in the non-imperative part.

5. The MS ignores subsequent repetition of the information element for which repetition is not specified, only the contents of the information element appearing first are handled. For specified repeated information element, the MS ignores all subsequent repetitions of the information element beyond the limit on repetition, only the contents of information element appearing first up to the limit of repetitions are handled.

26.14.7.2.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters for ASCI testing.

Mobile Station:

The MS is in MM-state "idle, updated" with a TMSI allocated.

Specific PICS statements:

– Support VGCS originating (TSPC_AddInfo_VGCS_Originating)

– Support VGCS talking (TSPC_AddInfo_VGCS_Talking)

– Support VGCS listening (TSPC_AddInfo_VGCS_Listening)

– Support VBS originating (TSPC_AddInfo_VBS_Originating)

– Support VBS listening (TSPC_AddInfo_VBS_Listening)

PIXIT Statements:

–

Foreseen Final State of the MS

MM-state "Idle, updated".

Test Procedure

The MS is in idle updated mode. The SS sends NOTIFICATION/NCH messages with incorrect mandatory IE (skip=’0001’B) or with comprehension required IE. It is checked that the MS ignores these NOTIFICATION/NCH messages. The SS sends NOTIFICATION/NCH containing unknown IE not encoded as comprehension required in non-imperative part. It is checked that the MS ignores the unknown IE and accepts the NOTIFICATION/NCH message. If the MS supports VGCS/VBS listening only, the test stops here.

If the MS supports VGCS talking the test continues on step 7. The MS joins the call. The SS sends correct UPLINK BUSY message then sends UPLINK FREE message containing incorrect mandatory IE. It is checked that the UPLINK FREE message is ignored by the MS. The SS sends correct UPLINK FREE message and the MS is requested to access the uplink. During the uplink access procedure it is checked that the MS ignores the VGCS UPLINK GRANT message in which mandatory IE is missing. After the MS enters group transmit mode, it is brought back to idle updated mode. The test stops here if the MS supports VGCS talking but not VGCS originating.

If the MS supports VGCS/VBS originating the test proceeds on step 30. The MS is requested to originate a VGCS call. During the call establishment it is checked that the MS ignores the CONNECT messages that missing mandatory IE or containing unknown IE encoded as comprehension required, and that the MS ignores unknown IE which is in non-imperative part and is not encoded as comprehension required, it is also checked that the MS ignores subsequent repetition of the information element for which repetition is not specified.

Maximum Duration of Test

5 minutes.

Expected Sequence

The test steps 7 to 29 are performed if the MS supports VGCS talking. The test steps 30 to 56 are performed if the MS supports VGCS/VBS originating.

Step	Direction	Message	Comments
0	MS		The MS is in Idle updated mode.
1	SS -> MS	NOTIFICATION/NCH	skip = ‘0001’B, with VGCS/VBS channel description and call reference active in the MS
2	MS		check that the MS ignores the NOTIFICATION/NCH message in step 1. This is checked for 10 s.
3	SS -> MS	NOTIFICATION/NCH	containing comprehension required IE, see specific message contents
4	MS		check that the MS ignores the NOTIFICATION/NCH message in step 3. This is checked for 10 s
5	SS -> MS	NOTIFICATION/NCH	unknown IE not encoded as comprehension required, see specific message contents
6	MS		check that the MS indicates the notified call
7	MS		MMI action to join the notified VGCS call
8	SS -> MS	UPLINK BUSY
9	SS -> MS	UPLINK FREE	message type = ‘11010’B, the MS shall ignore this message
10	MS		MMI action to request the uplink access
11	SS		check that there is no UPLINK ACCESS for 6 s.
12	SS -> MS	UPLINK FREE	as default
13	MS		MMI action to request the uplink access
14	MS -> SS	UPLINK ACCESS
15	MS -> SS	UPLINK ACCESS
16	SS -> MS	VGCS UPLINK GRANT	missing mandatory IE Timing Advance, request reference refers to step 14.
17	MS -> SS	UPLINK ACCESS	The MS ignores VGCS UPLINK GRANT.
18	MS -> SS	UPLINK ACCESS
19	SS -> MS	VGCS UPLINK GRANT	request reference does not refer to steps 14, 15, 17, 18.
20	SS -> MS	UPLINK BUSY
21	SS		check that there is no UPLINK ACCESS for 6 s
22	SS -> MS	UPLINK FREE
23	MS		MMI action to request uplink access
24	MS -> SS	UPLINK ACCESS
25	MS -> SS	UPLINK ACCESS
26	SS -> MS	UPLINK BUSY
27	SS -> MS	VGCS UPLINK GRANT	refer to the reference in step 25
28	MS -> SS	TALKER INDICATION	L2: SABM / UA
29	SS -> MS	CHANNEL RELEASE	The MS releases L2 multiple frame link L2:DISC/UA.
30	MS		MMI action to originate a VGCS/VBS call with setup
31	MS -> SS	CHANNEL REQUEST
32	SS -> MS	IMMEDIATE ASSIGNMENT	TCH/F, single RF channel GSM 450: 275, GSM 480: 322, GSM 900: 50, DCS 1 800: 750 PCS 1 900: 650 GSM710: 470 GSM 750: 470 T-GSM 810: 470 GSM 850: 177
33	MS -> SS	CM SERVICE REQUEST	L2: SABM / UA
34	SS -> MS	CM SERVICE ACCEPT
36	MS -> SS	SETUP
37	SS -> MS	CHANNEL MODE MODIFY
38	MS -> SS	CHANNEL MODE MODIFY ACKNOWLEDGE
39	SS -> MS	CONNECT	missing mandatory IE: Group call reference
40	MS -> SS	STATUS	cause #96
41	SS -> MS	CONNECT	unknown IE encoded as comprehension required, see specific message contents
42	MS -> SS	STATUS	cause #96
43	SS -> MS	GET STATUS	unknown IE in non-imperative part, see specific message contents
44	MS -> SS	STATUS	state U1
45	SS -> MS	CONNECT
46	SS -> MS	GET STATUS
			for VGCS test
A47	MS -> SS	STATUS	state U2sr
A48	MS		check the MS asks to indicate the desire of speaking
A49	MS		wait for time-out.
A50	MS -> SS	UPLINK RELEASE
A51	SS -> MS	GET STATUS	duplicated IE, see specific message contents
A52	SS		check that the MS does not respond
A53	SS -> MS	GET STATUS
A54	MS -> SS	STATUS	state U2r
			for VBS test
B47	MS -> SS	STATUS	state U2
55	SS -> MS	TERMINATOIN
56	SS -> MS	CHANNEL RELEASE	The MS releases L2 multiple frame link L2:DISC/UA.

Specific message contents:

NOTIFICATION/NCH – in step 3

Information Element	value/remark
L2 Pseudo Length	’15’B
RR Protocol Discriminator	‘0110’B
Skip Indicator	‘0000’B’
Message Type	‘00100000’B
Comprehension required IEI	‘00000000’B
– Length	1
– unrecognised IE contents	‘xxxxxxxx’B (arbitrary octet)
NT/N Rest Octets	As default

NOTIFICATION/NCH – in step 6

Information Element	value/remark
L2 Pseudo Length	’15’B
RR Protocol Discriminator	‘0110’B
Skip Indicator	‘0000’B’
Message Type	‘00100000’B
Unknown IEI	‘11101001’B
– Length	1
– unrecognised IE contents	‘xxxxxxxx’B (arbitrary octet)
NT/N Rest Octets	As default

CONNECT – in step 41

Information Element	value/remark
Protocol Discriminator	‘0000’B for GCC, ‘0001’B for BCC
Transaction identifier	depending on the context of the test
Message Type	‘0x110011’B
Group call reference	PICS/PIXIT
Comprehension required IEI	‘00000000’B
– Length	1
– unrecognised IE contents	‘xxxxxxxx’B (arbitrary octet)
Originator indication	Originator
Spare half octet	‘0000’B

GET STATUS – in step 43

Information Element	value/remark
Protocol Discriminator	‘0000’B for GCC, ‘0001’B for BCC
Transaction identifier	depending on the context of the test
Message Type	‘0x111001’B
Mobile identity	PICS/PIXIT
Unknown IEI	‘11101001’B
– Length	1
– unrecognised IE contents	‘xxxxxxxx’B (arbitrary octet)

GET STATUS – in step A51

Information Element	value/remark
GCC Protocol Discriminator	‘0000’B
Transaction identifier	depending on the context of the test
Message Type	‘0x111001’B
Mobile identity	not address the MS
Mobile identity	PICS/PIXIT

26.14.7.3 VGCS-VBS / Messages not addressing VGCS receive mode

26.14.7.3.1 Conformance requirement

In group receive mode the MS shall ignore messages which are allowed in group receive mode but not sent in UI format on the VGCS or VBS channel downlink.

Mobile stations in group receive mode shall ignore all messages which are not sent in UI format or which are not related to the following procedures: channel mode modify, notification and paging information, uplink status messages, channel release message, information on channel restructuring.

Reference(s)

3GPP TS 04.08 / 3GPP TS 44.018 subclause 3.4.15.1.2.

26.14.7.3.2 Test purpose

To verify that the MS in group receive mode ignores:

1. Messages which are applicable to group receive mode but not sent in UI format.

2. ASSIGNMENT COMMAND and HANDOVER COMMAND messages in which the target mode information element indicates "dedicated mode".

3. Messages which are not applicable to group receive mode.

26.14.7.3.3 Method of test

Initial Conditions

System Simulator:

1 cell with default parameters for ASCI testing.

Mobile Station:

The MS is in MM-state "idle, updated" with a TMSI allocated.

Specific PICS statements:

–

PIXIT Statements:

– Way to configure VGCS or VBS.

– Way to indicate a call notification.

– Way to accept a VGCS or VBS.

– Way to verify the downlink speech path.

Foreseen Final State of the MS

"Idle, updated", with TMSI allocated.

Test Procedure

The MS is brought into group receive mode. The SS sends, in UI format, the messages which are not applicable to group receive mode. It is checked that the MS ignores these messages. The SS sends, in L2 I format, messages which are applicable to group receive mode. It is checked that the MS ignores these messages.

Maximum Duration of Test

5 minutes.

Expected Sequence

Step	Direction	Message	Comments
0	MS		The MS is in Idle updated mode.
1	SS -> MS	NOTIFICATION/NCH
2	MS		MMI action to join VGCS/VBS call.
3	SS -> MS	IMMEDIATE ASSIGNMENT	UI format.
4	MS		check that the MS ignores the above message.
5	SS -> MS	IMMEDIATE ASSIGNMENT EXTENDED	UI format.
6	MS		check that the MS ignores the above message.
7	SS -> MS	CIPHERING MODE COMMAND	UI format.
8	MS		check that the MS ignores the above message.
9	SS -> MS	ASSIGNMENT COMMAND	sent in the L2 I format.
10	MS		check that the MS ignores the above message.
11	SS -> MS	HANDOVER COMMAND	sent in the L2 I format.
12	MS		check that the MS ignores the above message.
13	SS -> MS	FREQUENCY REDEFINITION	sent in the L2 I format.
14	MS		check that the MS ignores the above message.
15	SS -> MS	CHANNEL MODE MODIFY	sent in the L2 I format.
16	MS		check that the MS ignores the above message.
17	SS -> MS	CHANNEL RELEASE	I format
18	MS		check that the MS ignores the above message.
19	SS -> MS	CHANNEL RELEASE	UI format.