hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.4.1 Introduction | The text in this subclause is intended to develop a standardized way of creating lower layer failures whilst testing the performance of Layer 3 signalling.
There are two groups of lower layer failures:
1) Detected by analysis of reception at Layer 1 (3GPP TS 05.08, 3GPP TS 04.08 / 3GPP TS 44.018),
2) Data link layer fa... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.4.2 Layer 1 reception failures | The absence of reception of correct frames on the SACCH until the S counter reaches value 0 will be interpreted as a Layer 1 failure. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.4.3 Data link layer failures | Many kinds of error cases can be caused in Layer 2. For example too many "T200 - time-out/retrying" - pairs.
NOTE 1: All types of data link failures are indicated similarly to the RR layer (Release Indication).
NOTE 2: All types of L1 failures are indicated similarly to each layer (Abort Indication, Error Indication). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.4.4 Lower layer failures, used for the tests in clause 25 | For L3 testing different lower layer failures are performed:
1) T100 time-out in Layer 1.
2) Too many T200 time-outs consecutively in Layer 2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.1 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions / unknown protocol discriminator | An MS ignores messages with unknown protocol discriminator. This allows for the introduction of new messages which will be ignored by MS of earlier phases. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.1.1 Conformance requirements | If the mobile station receives a standard L3 message with a protocol discriminator different from those specified in table 9.2/3GPP TS 04.07, the mobile station shall ignore the message.
References
3GPP TS 04.07, subclause 11.2.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.1.2 Test purpose | To verify that a MS supporting TCH and the call control protocol ignores a message containing an undefined protocol discriminator in the special case of a message coded otherwise like a CC STATUS ENQUIRY message received by the MS having a mobile terminating call in CC-state U10, "active". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has been paged and an RR connection has been established.
If the MS supports the call control protocol, the test may alternatively be performed with the MS having a mobile terminating call in the CC-state U10, "active".
Specific PIC... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions / TI and skip indicator | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1 TI and skip indicator / RR | The MS ignores RR messages with skip indicator different to 0. This allows for the introduction of new RR messages which will be ignored by MS of earlier phases, especially on the downlink CCCH and BCCH. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.1 TI and skip indicator / RR / Idle Mode | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.1.1 Conformance requirements | A radio resource message received with skip indicator different from 0000 shall be ignored.
Reference(s):
3GPP TS 04.08 / 3GPP TS 24.008, subclause 10.3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.1.2 Test purpose | To verify that the MS ignores an RR message with skip indicator different from H'0 in the special case of a PAGING REQUEST TYPE 1 message received in the MM-state "idle, updated" and in RR-idle mode. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle, updated" and in RR-idle mode. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS is in the MM-state "idle, updated" and in RR-idle mode. It has a vali... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.2 TI and skip indicator / RR / RR-Connection established | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.2.1 Conformance requirements | A radio resource message received with skip indicator different from H'0 shall be ignored.
Reference(s):
3GPP TS 04.08 / 3GPP TS 24.008, subclause 10.3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.2.2 Test purpose | To verify that the MS ignores RR messages with skip indicator different from H'0 in the case of a message being received during the RR-connection establishment in the MM-state "idle, updated" / "wait for network command" and in RR-connected mode. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.1.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters, max retrans = 2.
Mobile Station:
The MS is in the MM-state "idle, updated" and in RR-idle mode. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS is in the MM-state "idle, updated" and in RR-idle mo... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.2 TI and skip indicator / MM | The MS ignores MM messages with skip indicator different to 0. This allows for the introduction of new MM messages which will be ignored by MS of earlier phases. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.2.1 Conformance requirements | A mobility management message received with skip indicator different from 0000 shall be ignored.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 10.3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.2.2 Test purpose | To verify that the MS ignores an MM message with skip indicator different from H'0 in the special case of an IDENTITY REQUEST message received. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a mobile terminating call in CC-state U10, "active", or alternatively, the MS has been paged and an RR connection has been established.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
Same as in th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.3 TI and skip indicator / CC | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.3.1 Conformance requirements | a) Whenever any call control message except SETUP or RELEASE COMPLETE is received specifying a transaction identifier with a value different from 111, which is not recognized as relating to an active call or to a call in progress, the receiving entity shall send a RELEASE COMPLETE message with cause value #81 "invalid ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.3.2 Test purpose | a) To verify that the MS having a mobile terminating call in CC-state U10, "active", on receipt of a DISCONNECT message which includes a transaction identifier with a value different from 111, which is not recognized as relating to an active call or a call in progress, sends a RELEASE COMPLETE message with cause value ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.2.3.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a mobile terminating call in CC-state U10, "active". No other call is active or in progress.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a mobile terminating call in CC-state U10, "a... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions / undefined or unexpected message type | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.1 Undefined or unexpected message type / undefined message type / CC | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.1.1 Conformance requirements | If the Mobile Station receives a message with message type not defined for the PD, it shall ignore the message except for the fact that, if an RR-connection exists, it returns a status message (STATUS, RR STATUS or MM STATUS depending on the protocol discriminator) with cause value #97 "message type non-existent or not... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.1.2 Test purpose | To verify that a MS supporting the call control protocol for at least one BC, having a mobile terminating call in CC‑state U10, "active", on receipt of a message with CC protocol discriminator and an arbitrary undefined message type, returns a STATUS message with cause value #97 to the peer CC entity without changing t... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a mobile terminating call in CC-state U10, "active".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a mobile terminating call in CC-state U10, "active".
Test Procedure
The SS sends a me... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.2 Undefined or unexpected message type / undefined message type / MM | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.2.1 Conformance requirements | If the Mobile Station receives a message with message type not defined for the PD, it shall ignore the message except for the fact that, if an RR-connection exists, it returns a status message (STATUS, RR STATUS or MM STATUS depending on the protocol discriminator) with cause value #97 "message type non-existent or not... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.2.2 Test purpose | To verify that a MS supporting the call control protocol for at least one BC, having a mobile terminating call in CC‑state U10, "active", on receipt of a message with MM protocol discriminator and message type undefined for the mobility management protocol, returns an MM STATUS message with reject cause value #97 witho... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a mobile terminating call in CC-state U10, "active". The TI of that mobile terminating call has value 0.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a mobile terminating call in CC-s... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.3 Undefined or unexpected message type / undefined message type / RR | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.3.1 Conformance requirements | If the Mobile Station receives a message with message type not defined for the PD, it shall ignore the message except for the fact that, if an RR-connection exists, it returns a status message (STATUS, RR STATUS or MM STATUS depending on the protocol discriminator) with cause value #97 "message type non-existent or not... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.3.2 Test purpose | To verify that an MS in RR connected mode on receipt of a message with RR protocol discriminator and message type undefined for the RR protocol, returns an RR STATUS message with reject cause value #97 without changing its state (this is checked by observing that the MS does not send L3 messages). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.3.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has been paged and an RR connection has been established.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS is in "idle updated" state.
Test Procedure
The SS sends a message to the MS the PD of wh... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.4 Undefined or unexpected message type / unexpected message type / CC | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.4.1 Conformance requirements | If the Mobile Station receives a message not consistent with the protocol state, the Mobile Station shall ignore the message except for the fact that, if an RR-connection exists, it returns a status message (STATUS, RR STATUS or MM STATUS depending on the protocol discriminator) with cause value #98 "Message type not c... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.4.2 Test purpose | To verify that a MS supporting the call control protocol for at least one BC, having a call in CC-state U10, "active", on receipt of an inopportune CC message, returns a STATUS message with reject cause value #98 without changing the state of the active call (this is verified by use of the status enquiry procedure.) Th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.3.4.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a call in CC-state U10, "active".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a call in CC-state U10, "active".
Test Procedure
The SS sends a CALL PROCEEDING message to the MS. The S... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.4 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions / unforeseen information elements in the non-imperative message part | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.4.1 Unforeseen information elements in the non-imperative message part / duplicated information elements | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.4.1.1 Conformance requirements | 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.
References
3GPP TS 04.08... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.4.1.2 Test purpose | To verify that the MS ignores an unforeseen second occurrence of an information element with format T, TV, or TLV in the special case of the mobile identity IE which has format TLV in the LOCATION UPDATING ACCEPT message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.4.1.3 Method of test | Initial conditions
System Simulator:
2 cells A and B belonging to different location areas, default parameters.
Mobile Station:
The MS is in the MM-state "idle, updated" and in RR-idle mode, listening to the BCCH/CCCH of cell A. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State o... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions / non-semantical mandatory IE errors | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1 Non-semantical mandatory IE errors / RR | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1 Non-semantical mandatory IE errors / RR / missing mandatory IE error | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.1 Non-semantical mandatory IE errors / RR / missing mandatory IE error / special case | The MS shall accept a CHANNEL RELEASE message whether it contains an RR cause or not. This allows for the shortening of the message in the future. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.1.1 Conformance requirements | When on receipt of a message a "missing mandatory IE" error is diagnosed the MS shall proceed as follows: If the message is a CHANNEL RELEASE message, the actions taken shall be the same as specified for a normal RR-connection release.
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 8.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.1.2 Test purpose | To verify that the MS in RR connected mode releases the connection upon receipt of a CHANNEL RELEASE message with missing RR cause (which is "mandatory" in that message). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle, updated" and in RR-idle mode. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS is in the MM-state "idle, updated" and in RR-idle mode. It has a vali... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.2 Non-semantical mandatory IE errors / RR / missing mandatory IE error / general case | In the general case, the MS has to report an RR message with missing mandatory IE by the use of an RR STATUS message, but otherwise to ignore it. This is a recovery mechanism for unforeseen states. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.2.1 Conformance requirements | When on receipt of a message a "missing mandatory IE" error is diagnosed the MS shall proceed as follows: If the message is not one of the messages listed in subclauses 8.5.1, 8.5.2, and 8.5.3 of 3GPP TS 04.08 / 3GPP TS 24.008, the Mobile Station shall ignore the message except for the fact that, if an RR-connection ex... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.2.2 Test purpose | To verify that the MS in RR connected mode ignores a ciphering mode command message in which the ciphering mode setting IE and cipher response IE are missing except for the fact that it returns a RR STATUS message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.1.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle, updated" and in RR-idle mode. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS is in RR-connected mode.
Test Procedure
A mobile terminating RR conne... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.2 Non-semantical mandatory IE errors / RR / comprehension required | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.2.1 Conformance requirements | When an RR message containing an IE unknown in the message, but encoded as "comprehension required" (see subclause 10.5 of 3GPP TS 04.08 / 3GPP TS 24.008) is received, the MS shall proceed as follows: When the message is not one of the messages listed in 3GPP TS 04.08 subclauses 8.5.1, 8.5.2 and 8.5.3, the Mobile Stati... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.2.2 Test purpose | To verify that the MS having an RR-connection established ignores a HANDOVER COMMAND message containing in the non-imperative part an IE encoded as comprehension required except for the fact that it returns a RR STATUS message with cause # 96 "invalid mandatory information". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.1.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has an MT call in state U10, "active"; or alternatively, the MS has been paged and an RR-connection has been established.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
As in the initial conditions.
T... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 0000 0000 | length |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 0000 0001 | unrecognized IE contents
xxxx xxxx |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2 Non-semantical mandatory IE errors / MM | The MS shall ignore MM messages with syntactically incorrect mandatory IE. This allows to use reserved values in later phases. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.1 Non-semantical mandatory IE errors / MM / syntactically incorrect mandatory IE | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.1.1 Conformance requirements | When an MM message containing a syntactically incorrect mandatory IE is received, the Mobile Station shall ignore the message except for the fact that, if an RR-connection exists, it returns a MM STATUS message with cause value #96 "invalid mandatory information".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclause 8.... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.1.2 Test purpose | To verify that an MS supporting at least one BC, having a CC entity in state U10, "active", ignores an MM message with syntactically incorrect IE except for the fact that it sends an MM STATUS message with reject cause #96. This is tested in the special case of an IDENTITY REQUEST message in which the (mandatory) ident... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a mobile terminating call in the CC-state U10, "active".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a mobile terminating call in the CC-state U10, "active".
Test Procedure
The SS se... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.2 Non-semantical mandatory IE errors / MM / syntactically incorrect mandatory IE | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.2.1 Conformance requirement(s) | When an MM message containing a syntactically incorrect mandatory IE is received, the Mobile Station shall ignore the message except for the fact that, if an RR-connection exists, it returns an MM STATUS message with cause value #96 "invalid mandatory information".
Reference(s)
3GPP TS 04.08 / 3GPP TS 24.008, subclause... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.2.2 Test purpose | To verify that an MS having been paged and having an RR connection established ignores an MM message with syntactically incorrect IE except for the fact that it sends an MM STATUS message with reject cause #96. This is tested in the special case of an IDENTITY REQUEST message in which the (mandatory) identity type IE s... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has been paged; an RR connection has been established.
The MS has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen final state of the MS
The MS is in the MM-state "idle updated" listening to the BCCH/CCCH of th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.3 Non-semantical mandatory IE errors / MM / comprehension required | The "comprehension required" mechanism allows for the introduction of essential new information elements into messages, such that a message is ignored and a report is sent if the new information element is not understood. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.3.1 Conformance requirements | When an MM message containing an IE unknown in the message, but encoded as "comprehension required" (see subclause 10.5 of 3GPP TS 04.08 / 3GPP TS 24.008) is received, the MS shall ignore the message except for the fact that, if an RR-connection exists, it returns an MM STATUS message with cause value #96 "invalid mand... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.3.2 Test purpose | To verify that the MS on receipt of an MM message containing an IE unknown in the message, but encoded as "comprehension required" ignores the message except for the fact that it returns an MM STATUS message with cause value #96 "invalid mandatory information"; this in the special case of the MM message being a LOCATIO... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.2.3.3 Method of test | Initial conditions
System Simulator:
The SS simulates two cells, A and B, belonging to different location areas, default parameters.
Mobile Station:
The MS is in the MM-state "idle, updated" listening to the BCCH/CCCH of cell A. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State o... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3 Non-semantical mandatory IE errors / CC | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1 Non-semantical mandatory IE errors / CC / missing mandatory IE | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.1 Non-semantical mandatory IE errors / CC / missing mandatory IE / disconnect message | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.1.1 Conformance requirements | When on receipt of a message a "missing mandatory IE" error is diagnosed, the MS shall proceed as follows: If the message is a DISCONNECT message, a RELEASE message shall be returned with cause value # 96 "invalid mandatory information" and normal call clearing applies.
References
3GPP TS 04.08 / 3GPP TS 24.008, subcla... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.1.2 Test purpose | To verify that the MS having an MT call in state U10, "active", on receipt of a DISCONNECT message in which the mandatory cause IE is missing shall return a RELEASE message with cause value #96 "invalid mandatory information". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has an MT call in the CC-state U10, "active".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS is in the MM-state "idle, updated" and in RR-idle mode.
Test Procedure
The SS sends a DISCONNECT mes... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.2 Non-semantical mandatory IE errors / CC / missing mandatory IE / general case | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.2.1 Conformance requirements | When on receipt of a message a "missing mandatory IE" error is diagnosed, the MS shall proceed as follows: If the message is not a SETUP, RELEASE, DISCONNECT, RELEASE COMPLETE, HOLD REJECT or RETRIEVE REJECT message, it shall ignore the message except for the fact that it returns a STATUS message specifying cause value... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.2.2 Test purpose | To verify that the MS having an MT call in state U10, "active", on receipt of a STATUS message in which the mandatory cause IE and call state IE are missing shall ignore the message except for the fact that it return a STATUS message with cause value #96 "invalid mandatory information" (that the MS does not change stat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.1.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has an MT call in the CC-state U10, "active".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has an MT call in the CC-state U10, "active".
Test Procedure
The SS sends a STATUS message in which ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.2 Non-semantical mandatory IE errors / CC / comprehension required | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.2.1 Conformance requirements | When a CC message containing an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 04.08 / 3GPP TS 24.008, subclause 10.5) is received, the MS shall proceed as follows: When the message is not one of the messages listed in 3GPP TS 04.08 / 3GPP TS 24.008 subclauses 8.5.1, 8.5.2 and 8.5.3, th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.2.2 Test purpose | To verify that an MS supporting the call control protocol for at least one BC having a call control entity in state U3 ignores a CONNECT message containing in the non-imperative part an IE encoded as comprehension required except for the fact that it returns a STATUS message with cause value #96 "invalid mandatory info... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.5.3.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a call control entity in CC state U3.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a call control entity in CC state U3.
Test Procedure
The SS sends a CONNECT message containing an op... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6 Handling of unknown, unforeseen, and erroneous protocol data, and of parallel transactions / unknown IE, comprehension not required | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6.1 Unknown information elements in the non-imperative message part / MM | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6.1.1 Unknown IE, comprehension not required / MM / IE unknown in the protocol | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6.1.1.1 Conformance requirements | The MS shall ignore all IEs unknown in a message which are not encoded as "comprehension required".
References
3GPP TS 04.08 / 3GPP TS 24.008, subclauses 8.6.1, 8.6.2 and 10.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6.1.1.2 Test purpose | To verify that the MS on receipt of an MM message containing an IE unknown in the message and unknown in the MM protocol which is not encoded as "comprehension required" ignores that IE; this in the special case of the MM message being a LOCATION UPDATING ACCEPT responding to a LOCATION UPDATING REQUEST from the MS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6.1.1.3 Method of test | Initial conditions
System Simulator:
The SS simulates two cells, A and B, belonging to different location areas, default parameters.
Mobile Station:
The MS is in the MM-state "idle, updated" listening to the BCCH/CCCH of cell B. It has a valid TMSI.
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State o... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.5.6.1.2 Unknown IE, comprehension not required / MM / IE unknown in the message |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.