hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.1.2 Structured sequence of the tests | The tests shall be performed in the order as indicated in the following table.
The validity of the tests depends upon the results of the tests performed before.
Channel request (basic test)
RR
26.2.1
Immediate assignment
RR
26.6.1
IMSI attach/detach (basic)
RR
26.2.2
Paging
RR
26.6.2
Test of the mobile station function... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.1.3 General rules for message parameters | The following rules concerning message parameters apply to clause 26:
1) Those values of parameters which are a consequence of the context of a test and which are not specific to that test need not be defined.
2) If the value of a parameter of an uplink message (MS to Network) is specified in a test, the implicit meani... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.1.4 General rules for layer 3 testing | Unless otherwise specified, before the SS pages the MS, the MS must be given the necessary time to be able to receive paging (see clause 20). In addition and unless otherwise specified,the SS must wait at least 1s after the last time slot of the message block containing a CHANNEL RELEASE, before sending a PAGING to the... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.1.5 Format of layer 3 test descriptions | In subclauses 26.2, 26.5, 26.6, 26.7, 26.9, 26.10 and 26.11 a rigorous description technique is used which is defined here.
For every test, a subclause titled "method of test" and a subclause titled "expected sequence" define the exact test steps and the verifications to be performed in the test. These subclauses are n... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2 Initial tests | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1 Channel request | The random access procedure is used by the MS to ask for resources to the network. If it is not performed correctly, the MS could prevent other MSs from obtaining resources, or the network could be overloaded if the MS does not respect the duration between 2 CHANNEL REQUEST messages. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.1 Channel request / initial time | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.1.1 Conformance requirement | 1) The MS shall start the initial access procedure at the latest 0,7 s after reception of the paging message.
2) The MS shall spread the initial CHANNEL REQUEST with equal probability on the correct number of time slots.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclauses 3.3.1.1.2 and 3.3.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.1.2 Test purpose | 1) To verify that the MS answers to a PAGING message by sending a CHANNEL REQUEST message within 0,7 s after reception of the PAGING message.
2 To verify that the MS does not always use the same delay between reception of paging message and sending of the CHANNEL REQUEST message. If an MS uses a fixed delay, there is a... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.1.3 Method of test | Initial Conditions
System Simulator:
1 cell, Tx-Integer = 5. The CCCH is either combined or not with SDCCH. This is arbitrarily chosen.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.1.4 Test requirements | S(n) = CARD {k | f(k) = n}
The following requirements shall be met:
S(n) 41 for all n.
NOTE: CARD {k | f(k) = n} is mathematical notation for the number of times that f(k) equals n. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.2 Channel request / repetition time | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.2.1 Conformance requirement | 1) The MS shall spread retransmissions of a CHANNEL REQUEST message, with equal probability on Tx-Integer timeslots and with the correct delay after the reception of the PAGING REQUEST.
2) The MS shall not retransmit another CHANNEL REQUEST message when Max-retrans is reached.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.01... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.2.2 Test purpose | 1) To verify that the MS spreads retransmission of a CHANNEL REQUEST message with equal probability on Tx-Integer time slots and correctly applies the fixed delay when the following conditions apply:
- the CCCH is combined or not combined with SDCCHs;
- the maximum number of retransmissions is equal to one of the follo... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.2.3 Method of test | Initial Conditions
System Simulator:
1 cell.
Tx-Integer is arbitrarily chosen in the set {6, 7, 8, 9, 10, 11, 12, 14, 16, 20, 25, 32, 50}.
Max_Retrans is arbitrarily chosen in the set {1, 2, 4, 7}.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Fi... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.3 Channel request / random reference | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.3.1 Conformance requirement | A CHANNEL REQUEST message sent by the MS shall include a random reference randomly drawn from a uniform probability distribution for every new transmission.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.3.1.1.23.3.1.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.3.2 Test purpose | To verify that an MS produces different random references for a CHANNEL REQUEST. If a MS always produces the same random reference, it makes possible that different MSs of the same product series produce the same random reference. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.3.3 Method of test | Initial Conditions
System Simulator:
1 cell, CCCH not combined with SDCCH.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is in the MM-state "idle, updated" and in the RR idle-mode.
Test Procedure
... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.1.3.4 Test requirements | At least D values of r(1), ..., r(k) shall be different.
NOTE: D has been computed such that the probability of refusing a correct MS is less than [0,027 %]. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.2 IMSI detach and IMSI attach | The IMSI detach/attach procedures are used to indicate to the network that the MS is deactivated/activated. Theses procedures are allowed or not by the network (ATT flag set to "MSs in the cell shall apply IMSI attach and detach procedure" or "MSs in the cell are not allowed to apply IMSI attach and detach procedure").... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.2.1 Conformance requirement | 1) When the Attach-detach flag in the Control Channel Description of the System Information Type 3 indicates "MSs in the cell are not allowed to apply IMSI attach and detach procedure", the MS shall not perform the IMSI detach procedure upon deactivation.
2) When the Attach-detach flag in the Control Channel Descriptio... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.2.2 Test purpose | 1) To verify that the MS correctly performs IMSI detach/attach procedures when it is required by the network and upon deactivation/activation or SIM removal/insertion and does not perform these procedures when not required.
2) To verify that the mobile station acknowledges a re-allocated TMSI during IMSI attach. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.2.3 Method of test | Initial Conditions
System Simulator:
1 cell, default parameters.
For procedures 1 and 2 ATT flag is set to "MSs in the cell are not allowed to apply IMSI attach and detach procedure".
For procedures 3 and 4 ATT flag is set to "MSs in the cell should apply IMSI attach and detach procedure".
Mobile Station:
The MS has a ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.3 Sequenced MM / CM message transfer | The RR sublayer of the MS shall have an associated send state variable V(SD) for sending MM and CM messages. This send state variable has been introduced to avoid the duplication of MM and CM messages. It is useful for the network after a handover or a change of channel to identify duplicated messages.
If the MS starte... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.3.1 Conformance requirement | The MS shall implement correctly the "send state variable V(SD)" ("Send duplicated"), included in transmitted MM and CM messages.
Reference(s)
3GPP TS 04.08 / 3GPP TS 44.018, subclause 3.1.4.3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.3.2 Test purpose | To verify that V(SD) is correctly set to 0 at the beginning of the establishment of the first RR connection and to verify that the MS handles correctly this variable in the special case of IDENTITY REQUEST messages, which are MM messages. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.3.3 Method of test | Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
-
PIXIT Statements:
-
Foreseen Final State of the MS
The MS has a valid TMSI. It is "idle updated".
Test Procedure
The MS is paged. After reception of the PAGING RESP... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.4 Establishment cause | The establishment cause set by the MS in the CHANNEL REQUEST message shall be consistent with the requested service or function, with the capabilities of the MS and with the indications given by the network.
If the MS uses a wrong establishment cause, the network might assign an inappropriate or incompatible resource.
... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.4.1 Conformance requirements | In the CHANNEL REQUEST message, the MS shall include an establishment cause which correspond to the establishment cause given by the MM sublayer and the broadcasted NECI value, or which correspond to one of the establishment causes "answer to paging" given by the RR entity in response to a PAGING REQUEST message includ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.4.2 Test purpose | To verify that the establishment cause sent by the MS in the Max-Retrans+1 CHANNEL REQUEST messages is consistent with the requested service, with the capabilities of the MS and with the indications of the network in the following cases:
1) If the MS supports a service on a traffic channel:
1.1 when the NECI bit is set... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.2.4.3 Method of test | Initial Conditions
System Simulator:
for all procedures: 1 cell, Max-Retrans = 7 slots. The NECI bit is set to 0.
Mobile Station:
The MS has a valid TMSI. It is "idle updated".
Specific PICS statements:
- a: MS supports speech on TCH/F (TSPC_AddInfo_Full_rate_version_1)
- b: MS supports speech on TCH/H (TSPC_AddInfo_Ha... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3 Test of MS functions in idle mode | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.1 Initial conditions | The SIM shall contain a PLMN-Selector that contains only the HPLMN of the MS, and an empty forbidden PLMN list.
Related PICS/PIXIT statements
During the tests in subclauses 26.3.2 and 26.3.3, the following parameters apply according to the above PICS/PIXIT statement:
RACH control parameters
In cells:
GSM 400: 1 to 7;
G... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.2 MS indication of available PLMNs | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.2.1 Test purpose | To verify that a MS can present the available PLMNs to the user when asked to do so in manual mode according to the requirements of 3GPP TS 05.08 and 3GPP TS 02.11. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.2.2 Method of test | a) The MS is switched on, equipped with a SIM containing default values except for those values listed under subclause 26.3.1 (initial conditions).
b) The MS is put into manual network selection mode (see PIXIT). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.2.3 Test requirements | 1) On entering manual network selection mode, the MS shall present a list of available PLMNs in all its bands of operation (MCC and MNC values, or any other valid indications, see PIXIT), within 2 minutes. Any PLMN shall only be presented once. The list shall include the MCC and MNC of:
GSM 400, GSM 710, GSM 750, T-GSM... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3 MS will send only if BSS is "on air" | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.1 Test purpose | To verify that the MS will not produce any RF transmission if no BSS is received. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.2 Method of test | a) The RF-signal for the BCCHs of:
GSM 400, GSM 710, GSM 750, T-GSM 810, GSM 850 and GSM 900: cell 1 to 8 is switched off.
DCS 1 800: cell 1 to 7 is switched off.
PCS 1 900: cell 1 to 7 is switched off.
Any Multiband: cell 1 to 8 is switched off.
b) The SS shall wait 20 s to allow the MS to detect the loss of cells.
c)... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.3 Test requirements | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.3.1 General test requirements | 1) The MS must not give "service indication".
2) In steps c) and d) the MS shall not produce any RF output. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.3.2 Test Procedures | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.3.2.1 Test Procedure 1 | For MS not supporting speech (see PICS) perform steps a, b, and c. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.3.3.2.2 Test Procedure 2 | For MS supporting speech (see PICS) perform steps a, b, c and d. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.4 Manual mode of PLMN selection | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.4.1 Conformance requirements | In manual mode, the MS can try to obtain normal service on any available VPLMN and it shall try to obtain normal service on a VPLMN if and only if the user makes a manual selection of this VPLMN.
Reference
3GPP TS 03.22 subclause 3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.4.2 Test purpose | To check that in manual mode the MS is able to obtain normal service on a PLMN which is neither the better nor a preferred PLMN and that it tries to obtain service on VPLMN if and only if the user selects it manually. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.3.4.3 Method of test | Initial conditions
System Simulator:
2 cells, defaults parameter unless otherwise specified.
The SS transmits 2 BCCH carriers in the supported band(s) of the mobile station (for a multiband MS carrier A and B shall be in different bands) with the initial following parameters:
level (dBVemf)
carrier A
PLMN 1
38
carrier... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 26.4 Lower layer failures in layer 3 testing | |
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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.