hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.6.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE has a valid TMSI. It is "idle updated".
Related ICS/IXIT statements
None.
Test Procedure
A mobile originating CM connection is attempted. After the UE has sent the CM SERVICE REQUEST message to the SS, the SS waits for expir... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.6.5 Test requirement | The UE shall attempt MO CM connection (step 1).
At step 8 the UE shall send a MM STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7 MM connection / abortion by the network | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.1 MM connection / abortion by the network / cause #6 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.1.2 Conformance requirement | At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall delete any TMSI, LAI and ciphering key sequence number stored in the SIM, set the update s... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.1.3 Test purpose | To check that upon reception of an ABORT message with cause #6 during call establishment:
- the UE does not send any layer 3 message;
- after reception of an ABORT message and after having been deactivated and reactivated, the UE performs location updating using its IMSI as mobile identity and indicates deleted LAI and... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.1.4 Method of test | Initial Conditions
- System Simulator:
- 2 cells, default parameters.
- User Equipment:
- the UE has a valid TMSI, CKSN and CK, IK. It is "idle updated" on cell B.
Related ICS/IXIT Statement(s)
USIM removal possible while UE is powered Yes/No.
Switch off on button Yes/No.
Support of emergency speech call Yes/No.
Test p... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.1.5 Test requirement | 1) At step 10 the UE shall not send any layer 3 message.
2)
2.1 At step 14 the UE shall not initiate an RRC connection establishment (not perform normal location updating).
2.2 At step 16 the UE shall not initiate an RRC connection establishment.(not perform periodic location updating).
2.3 At step 18 the UE shall not ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.2 MM connection / abortion by the network / cause not equal to #6 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.2.2 Conformance requirement | At the receipt of the ABORT message the mobile station shall abort any MM connection establishment or call re-establishment procedure and release all MM connections (if any). If cause value #6 is received the mobile station shall delete any TMSI, LAI and ciphering key sequence number stored in the USIM, set the update ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.2.3 Test purpose | To check that when multiple MM connections are established, the UE releases all MM connections upon reception of an ABORT message, in the case when the two MM connections are established for a mobile originating call and a non call related supplementary service operation.
To check that the TMSI is not deleted from UE a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.2.4 Method of test | Initial Conditions
- System Simulator:
- 1 cell, default parameters.
- T3212 is set to 6 minutes.
- User Equipment:
- the UE is in state U10 of a mobile originating call.
Related ICS/IXIT Statement(s)
The UE supports a non call related supplementary service operation during an active call Yes/No.
Test procedure
A non c... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.7.2.5 Test requirement | After step 8 the UE shall release all MM connections.
After step 12 the UE shall perform periodic location updating with TMSI used as Mobile Identity. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8 MM connection / follow-on request pending | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.1 MM connection / follow-on request pending / test 1 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.1.2 Conformance requirement | The UE shall not attempt to establish a new MM connection after location updating on the same RRC connection if not allowed by the network.
Reference(s)
TS 24.008 clause 4.4.4.6. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.1.3 Test purpose | To check that when the network does not include the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that has a CM application request pending does not attempt to establish a new MM connection on that RRC connection. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.1.4 Method of test | Initial Conditions
- System Simulator:
- 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
- User Equipment:
- the UE has a valid TMSI and is deactivated.
Related ICS/IXIT Statement(s)
None.
Test procedure
The UE is activated and a CM connection is attempted during the location ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.1.5 Test requirement | After step 8 the UE shall not send any layer 3 messages. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.2 MM connection / follow-on request pending / test 2 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.2.2 Conformance requirement | A UE supporting the follow-on request procedure and having a CM connection request pending shall correctly establish an MM connection following a location update when allowed by the network.
Reference(s)
TS 24.008 clause 4.4.4.6. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.2.3 Test purpose | To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that supports the follow on request procedure and that has a CM application request pending establishes successfully a new MM connection on that RRC connection. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.2.4 Method of test | Initial Conditions
- System Simulator:
- 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
- User Equipment:
- the UE has a valid TMSI and is deactivated.
Related ICS/IXIT Statement(s)
UE supports the follow on request procedure Yes/No.
Test procedure
The UE is activated and a C... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.2.5 Test requirement | After step 6:
The UE shall send a CM SERVICE REQUEST if the UE supports the follow on request procedure.
The UE shall not send any layer 3 message if the UE does not support the follow on request procedure. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.3 MM connection / follow-on request pending / test 3 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.3.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.3.2 Conformance requirement | 1) The UE shall not set the follow on proceed IE in a LOCATION UPDATING REQUEST message if no MM connection request is pending.
2) When the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that has no CM application request pending shall not attempt to establish a new MM connection ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.3.3 Test purpose | 1) To check that a UE that has no CM application request pending sets the follow on proceed IE to No follow-on request pending in a LOCATION UPDATING REQUEST message.
2) To check that when the network includes the follow on proceed IE in a LOCATION UPDATING ACCEPT message, a UE that has no CM application request pendin... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.3.4 Method of test | Initial Conditions
- System Simulator:
- 1 cell, ATT flag is set to "MSs in the cell shall apply IMSI attach and detach procedure".
- User Equipment:
- the UE has a valid TMSI and is deactivated.
Related ICS/IXIT Statement(s)
Supported services on TCH.
Test procedure
The UE is activated. The UE performs location updati... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.8.3.5 Test requirement | At step 8 the UE shall not send any layer 3 message.
After step 9:
The UE shall send CALL CONFIRMED message if the UE supports a basic service on TCH.
The UE shall send RELEASE COMPLETE message if the UE does not support a basic service on TCH. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.9 MM connection / abnormal cases / CS domain barred because of domain specific access control | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.9.1 Definition | This test is applicable for Rel-5 UEs supporting DSAC and Rel-6 or later UEs. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.9.2 Conformance requirement | TS 24.008 clause 4.1.1.2.2
If the PS or CS domain is barred because of domain specific access control, a GPRS MS operating in mode A or B in a network that operates in mode II or III shall use the MM specific procedures or GMM specific procedures, respectively, in the domain which is unbarred. If the MS detects that a ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.9.3 Test purpose | To test the behaviour of the UE if the CS domain is changed from unbarred to barred because of domain specific access control in a network that operates mode II. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.9.4 Method of test | Initial condition
An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x. The UE is informed that the CS domain specific access class x is barred.
System Simulator:
One cell operating in network operation mode II.
CS domain specific access class x is barred .
User Equipment:
The... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 9.5.9.5 Test requirements | At step 2, the CS domain specific access class x is barred , the UE shall:
- not send a CM SERVICE REQUEST message.
At step 6, the CS domain specific access class x is not barred, the UE shall:
- send a CM SERVICE REQUEST message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10 Circuit Switched Call Control (CC) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1 Circuit switched Call Control (CC) state machine verification | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.1 General on CC state machine verification | The principle of checking the call control functions consists in the validation of each call control identified state.
State U0 as an initial state is not verified in the tests of 10.1.2 (establishment of an outgoing call).
State U0.1 is never verified.
The steps to be followed within each performed test are:
- bring t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2 Establishment of an outgoing call | Initial conditions
As a minimum requirement the UE is updated and has been given a TMSI, a ciphering key and cipher key sequence number, and the layer 2, RRC and MM functionalities have been verified.
There are as many CM initial conditions as states to be checked.
The tables below describe message exchanges which brin... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1 Outgoing call / U0 null state | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1.1 Outgoing call / U0 null state / MM connection requested | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1.1.1 Definition | The call control entity of the User Equipment requests the MM-sublayer to establish a mobile originating MM-connection. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1.1.2 Conformance requirement | If no RR connection exists, the MM sublayer requests the RR sublayer to establish an RR connection and enters MM sublayer state WAIT FOR RR CONNECTION (MM CONNECTION). This request contains an establishment cause and a CM SERVICE REQUEST message.
References
TS 24.008 clause 5.2.1.1 and clause 4.5.1.1 |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1.1.3 Test purpose | To verify that upon initiation of an outgoing basic call by user the UE initiates establishment of an MM connection, using as first MM message a CM SERVICE REQUEST message with CM service type "Mobile originating call establishment or packet mode connection establishment” or “ Emergency call establishment ". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1.1.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
Test procedure
An MO circuit switched basic service is selected that is supported by the UE; if the... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.1.1.5 Test requirements | After step 2 the UE shall initiate establishment of an MM connection, using as first MM message a CM SERVICE REQUEST message with CM service type "Mobile originating call establishment or packet mode connection establishment" or "Emergency call establishment". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2 Outgoing call / U0.1 MM connection pending | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.1 Outgoing call / U0.1 MM connection pending / CM service rejected | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.1.1 Definition | A request for MM connection is rejected by the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.1.2 Conformance requirement | If a CM SERVICE REJECT message is received by the UE, timer T3230 shall be stopped, the requesting CM sublayer entity informed. Then the UE shall proceed as follows:
- If the cause value is not #4 or #6 the MM sublayer returns to the previous state (the state where the request was received). Other MM connections shall ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.1.3 Test purpose | To verify that a CC entity of the UE in CC-state U0.1, "MM-connection pending", upon the UE receiving a CM SERVICE REJECT message, returns to CC state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.1.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U0.1 by using table 10.1.2/1.
Test procedure
An MO circuit switche... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.1.5 Test requirements | After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.2 Outgoing call / U0.1 MM connection pending / CM service accepted | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.2.1 Definition | A CM request is accepted for the MM-connection by the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.2.2 Conformance requirement | Having entered the "MM connection pending" state, upon MM connection establishment, the call control entity of the UE sends a setup message to its peer entity. This setup message is
- a SETUP message, if the call to be established is a basic call.
It then enters the "call initiated" state.
References
TS 24.008 clause 5... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.2.3 Test purpose | To verify that a CC entity of the UE in CC-state U0.1, "MM connection pending", after completion of the security mode control procedure, sends a SETUP message specifying the Called party BCD number that was entered into the UE and then enters CC state U1, "Call initiated". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.2.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U0.1 by using table 10.1.2/1.
Test procedure
An MO circuit switche... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.2.5 Test requirements | After step 1 the UE shall send a SETUP message specifying the Called party BCD number that was entered into the UE and then enter CC state U1, "Call initiated". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.3 Outgoing call / U0.1 MM connection pending / lower layer failure | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.3.1 Definition | The call control entity of the UE being in the state, U0.1, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.3.2 Conformance requirement | 1. RR connection failure or IMSI deactivation
If an RR connection failure occurs or the IMSI is deactivated during the establishment of an MM connection, the MM connection establishment is aborted, timers T3230 is stopped, and an indication is given to the CM entity that requested the MM connection establishment. This ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.3.3 Test purpose | To verify that the UE with a CC entity in state U0.1, "MM connection pending", aborts MM connection establishment, stops timer T3230 and returns to idle mode in case an RR connection failure occurs. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.3.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U0.1 by using table 10.1.2/1.
Test procedure
An MO circuit switche... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.2.3.5 Test requirements | After step 4 the UE shall not initiate RRC connection establishment during 60 s. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3 Outgoing call / U1 call initiated | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.1 Outgoing call / U1 call initiated / receiving CALL PROCEEDING | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.1.1 Definition | The call control entity of the UE being in the state, U1, a CALL PROCEEDING message is sent by the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.1.2 Conformance requirement | Having entered the "call initiated" state, when the call control entity of the UE receives a CALL PROCEEDING message, it shall enter the "mobile originating call proceeding" state.
References
TS 24.008, clauses 5.2.1.1, 5.2.1.2 and 5.2.1.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.1.3 Test purpose | To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a CALL PROCEEDING message, enters CC state U3, "Mobile originating call proceeding". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.1.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U1 by using table 10.1.2/1.
Test procedure
An MO circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.1.5 Test requirements | After step 1 the UE shall enter CC state U3, "Mobile originating call proceeding". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.2 Outgoing call / U1 call initiated / rejecting with RELEASE COMPLETE | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.2.1 Definition | The call control entity of the UE being in the state, U1, the call is rejected by a RELEASE COMPLETE message sent by the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.2.2 Conformance requirement | A call control entity of the UE in any call control state shall, upon receipt of a RELEASE COMPLETE message from its peer entity in the network: stop all running call control timers ; release the MM connection; and return to the "null" state.
References
TS 24.008, clause 5.4.4.1.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.2.3 Test purpose | 1) To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of a RELEASE COMPLETE message with valid cause value, enters CC state U0, "Null".
2) To verify that in returning to idle mode, the CC entities relating to the seven mobile originating transaction identifiers are in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.2.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U1 by using table 10.1.2/1.
Test procedure
An MO circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.2.5 Test requirements | After step 2 CC entities relating to all mobile originating transaction identifiers shall send RELEASE COMPLETE messages with cause value #81 (invalid TI value). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.3 Outgoing call / U1 call initiated / T303 expiry | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.3.1 Definition | The call control entity of the UE being in the state, U1, if no response is then received from the SS, timer T303 expires at the UE side. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.3.2 Conformance requirement | If timer T303 elapses in the "call initiated" state before any of the CALL PROCEEDING, ALERTING, CONNECT or RELEASE COMPLETE messages has been received, the clearing procedure described in TS 24.008 clause 5.4 is performed.
References
TS 24.008, clause 5.2.1.1 and clause 5.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.3.3 Test purpose | 1) To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon expiry of T303 sends a DISCONNECT message to its peer entity and enters state U11, "Disconnect request". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.3.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U1 by using table 10.1.2/1.
Test procedure
An MO circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.3.5 Test requirements | After step 1 upon expiry of timer T303 the UE shall send a DISCONNECT message and enter state U11, "Disconnect request". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.4 Outgoing call / U1 call initiated / lower layer failure | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.4.1 Definition | The call control entity of the UE being in the state, U1, a lower layer failure is accomplished at the UE and consequently, communication at layer 3 level with the peer entity is terminated. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.4.2 Conformance requirement | The MM sublayer shall indicate to all CM entities associated with active MM connections that the MM connection is interrupted, the subsequent action of the MM sublayer (call re-establishment, see TS 24.008 clause 4.5.1.6, or local release) will then depend on the decisions by the CM entities.
References
TS 24.008, clau... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.4.3 Test purpose | To verify that after the UE with a CC entity in state U1 "Call initiated", has detected a lower layer failure and has returned to idle mode, the CC entity is in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.4.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U1 by using table 10.1.2/4.
Test procedure
An MO circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.4.5 Test requirements | After step 4 the UE shall not send any message to the SS during 60 s. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.5 Outgoing call / U1 call initiated / receiving ALERTING | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.5.1 Definition | The call control entity of the UE being in the state, U1, an ALERTING message is sent to the UE as an indication that a call is being alerted at a called end. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.5.2 Conformance requirement | When the call control entity of the UE in the "call initiated" state or "mobile originating call proceeding" state receives an ALERTING message then, the call control entity of the UE shall stop timer T303 and T310 (if running) and shall enter the "call delivered" state.
References
TS 24.008, clause 5.2.1.1 and clause ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.5.3 Test purpose | To verify that a CC entity of the UE in CC-state U1, "Call initiated", upon receipt of an ALERTING message, enters CC state U4, "Call delivered". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.3.5.4 Method of test | Related ICS/IXIT statements
- supported MO circuit switched basic services.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in MM-state "idle, updated" with valid TMSI and CKSN.
The UE is brought into the state U1 by using table 10.1.2/4.
Test procedure
An MO circuit switched ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.