hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.4.3 Test purpose | To verify that the a CC-entity of the UE in CC-state U11, "Disconnect Request" having detected a lower layer failure returns to the idle mode. The CC entity is thus in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.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 U11 by using table 10.1.2/4.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.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.7.5 U11 disconnect request / unknown message received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.5.1 Definition | The call control entity of the UE being in the state, U11, an unknown message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.5.2 Conformance requirement | If a UE receives an RR, MM or CC message with message type not defined for the PD or not implemented by the receiver in acknowledged mode, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 97 "message type non-existent or not implemented".
References
TS 24.008 cla... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.5.3 Test purpose | To verify that a CC-entity of the UE in CC-state U11, "Disconnect Request", having received an unknown message from its peer entity returns a STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.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 U11 by using table 10.1.2/4.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.7.5.5 Test requirements | After step 1 the UE shall return a STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8 U12 disconnect indication | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.1 U12 disconnect indication / call releasing requested by the user | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.1.1 Definition | The call control entity of the UE being in the state, U12, the user requests to terminate the call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.1.2 Conformance requirement | Response from the upper layers:
i) If the upper layers request the clearing of the call, the call control entity of the UE shall:
- stop all running call control timers;
- send a RELEASE message;
- start timer T308; and
- enter the "release request" state.
References
TS 24.008 clause 5.4.4.2.2.1 |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.1.3 Test purpose | To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" being in network initiated call release phase, shall, upon receiving a call release request from the user sends a RELEASE to its peer entity and enters CC-state U19, "Release Request" |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.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 U12 by using Option A of table 10.1.2/1.
Test procedure
An MO circ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.1.5 Test requirements | After step 1 the UE being in network initiated call release phase, shall send a RELEASE message and enter CC-state U19, "Release Request". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.2 U12 disconnect indication / RELEASE received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.2.1 Definition | The call control entity of the UE being in the state, U12, a RELEASE message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.2.2 Conformance requirement | The call control entity of the UE in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state.
References
TS 24.008 clause 5.4.3.3 |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.2.3 Test purpose | 1) To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication", upon receipt of a RELEASE message returns to its peer entity the RELEASE COMPLETE message and enters the CC-state U0, "Null".
2) To verify that the UE on returning to the idle mode releases the MM-connection and that the CC-entities relat... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.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 U12 by using Option A of table 10.1.2/1.
Test procedure
An MO circ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.2.5 Test requirements | After step 1 the UE shall return the RELEASE COMPLETE message.
After step 3 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.8.3 U12 disconnect indication / lower layer failure | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.3.1 Definition | The call control entity of the UE being in the state, U12, 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.8.3.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 claus... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.3.3 Test purpose | To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" having detected a lower layer failure returns to idle mode. The CC-entity is thus in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.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 U12 by using Option A of table 10.1.2/3.
Test procedure
An MO circ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.3.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.8.4 U12 disconnect indication / unknown message received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.4.1 Definition | The call control entity of the UE being in the state, U12, an unknown message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.4.2 Conformance requirement | If a UE receives an RR, MM or CC message with message type not defined for the PD or not implemented by the receiver in acknowledged mode, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 97 "message type non-existent or not implemented".
References
TS 24.008 cla... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.4.3 Test purpose | To verify that a CC-entity of the UE in CC-state U12, "Disconnect Indication" having received an unknown message from its peer entity returns a STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.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 U12 by using Option A of table 10.1.2/3.
Test procedure
An MO circ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.8.4.5 Test requirements | After step 1 the UE shall return a STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9 Outgoing call / U19 release request | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.1 Outgoing call / U19 release request / timer T308 time-out | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.1.1 Definition | The call control entity of the UE being in the state, U19, if no response is then received from the SS, timer T308 expires at the UE side. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.1.2 Conformance requirement | The call control entity of the UE in the "release request" state shall at first expiry of timer T308 retransmit the RELEASE message and restart timer T308.
References
TS 24.008 clause 5.4.4.1.3.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.1.3 Test purpose | To verify that a CC-entity of the UE in CC-state U19, "Release Request" will, upon the first expiry of timer T308 send the RELEASE message to its peer entity and remain in the CC-state U19. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.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 U19 by using table 10.1.2/4.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.1.5 Test requirements | After step 1 upon the first expiry of timer T308 the UE shall send the RELEASE message and remain in the CC-state U19. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.2 Outgoing call / U19 release request / 2nd timer T308 time-out | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.2.1 Definition | The call control entity of the UE being in the state, U19, if no response is then received after timer T308 has expired two times in success at the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.2.2 Conformance requirement | At second expiry of timer T308, the call control entity of the UE shall: release the MM connection; and return to the "null" state.
References
TS 24.008 clause 5.4.4.1.3.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.2.3 Test purpose | 1) To verify that a CC-entity of the UE in CC-state U19, "Release Request", upon the 2nd expiry of the timer T308, enters the CC-state U0, "Null".
2) To verify that subsequently the UE proceeds with releasing the MM-connection and enters the idle mode with the CC entities relating to the seven mobile originating transa... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.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 U19 by using table 10.1.2/4.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.2.5 Test requirements | After step 5 upon the 2nd expiry of the timer T308 the UE shall enter the CC-state U0, "Null".
After step 10 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.9.3 Outgoing call / U19 release request / RELEASE received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.3.1 Definition | The call control entity of the UE being in the state, U19, a RELEASE message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.3.2 Conformance requirement | Clear collision can also occur when both sides simultaneously transfer RELEASE messages related to the same call. The entity receiving such a RELEASE message whilst within the "release request" state shall: stop timer T308; release the MM connection; and enter the "null" state (without sending a RELEASE COMPLETE messag... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.3.3 Test purpose | To verify that a CC-entity of the UE in CC-state U19, "Release Request", upon receipt of a RELEASE, shall release the MM-connection and enters the CC-state U0, "Null" with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.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 U19 by using table 10.1.2/4.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.3.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.9.4 Outgoing call / U19 release request / RELEASE COMPLETE received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.4.1 Definition | The call control entity of the UE being in the state, U19, a RELEASE COMPLETE message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.4.2 Conformance requirement | 1) A call control entity shall accept an incoming RELEASE COMPLETE message used to initiate the call clearing even though the cause information element is not included.
2) 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: sto... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.4.3 Test purpose | To verify that a CC-entity of the UE in CC-state U19, "Release Request", upon receipt of a RELEASE COMPLETE, shall release the MM-connection and enters the CC-state U0, "Null" with the CC entities relating to the seven mobile originating transaction identifiers in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.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 U19 by using table 10.1.2/1.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.4.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.9.5 Outgoing call / U19 release request / lower layer failure | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.5.1 Definition | The call control entity of the UE being in the state, U19, 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.9.5.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 claus... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.5.3 Test purpose | To verify that a CC-entity of the UE in CC-state U19, "Release Request", having detected a lower layer failure, returns to the idle mode, the CC entity is in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.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 U19 by using table 10.1.2/1.
Test procedure
An MO circuit switched... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.2.9.5.5 Test requirements | After step 4 CC the UE shall not send any message to the SS during 60 s. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3 Establishment of an incoming call / Initial conditions | The tables below describe message exchanges which bring the UE in the requested initial states in case of an incoming call.
A state may be taken as initial only when all the states which lead to this initial states have been validated. The order will be U0, U6, U9, U7, U8, U10, U26 etc. as in the following tables.
Tabl... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1 Incoming call / U0 null state | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1.1 Incoming call / U0 null state / SETUP received with a non supported bearer capability | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1.1.1 Definition | The call control entity of the UE being in the state, U0, a SETUP message is received with only one bearer capability and this bearer capability is not supported by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1.1.2 Conformance requirement | When the network is providing a basic service at the called side, the UE shall check that the basic service(s) offered by the network in the Bearer Capability information element(s) match(es) the basic services that the UE is able to support. If a mismatch is detected, then the UE shall proceed as follows:
- if the SET... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1.1.3 Test purpose | To verify that a CC entity of the UE, upon receipt of SETUP containing one bearer capability and this bearer capability is not supported, returns a RELEASE COMPLETE with correct cause value to its peer entity, and returns to the idle mode. To verify that the CC-entities relating to the seven mobile terminating transact... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1.1.4 Method of test | Related ICS/IXIT statements
- supported MT 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
A mobile terminated call is initiated. The UE receives a SETUP message that contains... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.1.1.5 Test requirements | After step 7 the UE shall return a RELEASE COMPLETE message with cause value #88 (incompatible destination) and return to the idle mode.
After step 9 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.3.2 Incoming call / U6 call present | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.2.1 Incoming call / U6 call present / automatic call rejection | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.2.1.1 Definition | Although the state U6 is transient, the ability to refuse a call (automatically) in this state is tested, if it is implemented at the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.2.1.2 Conformance requirement | If the mobile user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with the cause #21 "call rejected".
References
TS 24.008 clause 5.2.2.3.1 |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.2.1.3 Test purpose | To verify that a CC entity of the UE in CC-state U6, "Call Present", shall upon receipt of a rejection indication of the incoming call from the user, shall send RELEASE COMPLETE with the appropriate cause value to its peer entity and enter the CC-state U0, "Null". The CC entities relating to the seven mobile terminatin... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.2.1.4 Method of test | Related ICS/IXIT statements
- supported teleservices;
- the UE supports an ability to refuse a call after receipt of a SETUP message.
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 U6 by us... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.2.1.5 Test requirements | After step 1 the UE shall return a RELEASE COMPLETE message with cause value #21 (call rejected) and return to the idle mode.
After step 3 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.3.3 Incoming call / U9 mobile terminating call confirmed | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.1 Incoming call / U9 mobile terminating call confirmed / alerting or immediate connecting | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.1.1 Definition | The call control entity of the UE having entered the state, U9, with signal information received in the preceding SETUP message, the subsequent behaviour of the UE is tested. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.1.2 Conformance requirement | 1) The call control entity of the UE having entered the "mobile terminating call confirmed" state, if the call is accepted at the called user side, the UE proceeds as described in TS 24.008 clause 5.2.2.5. Otherwise, if the signal information element was present in the SETUP message user alerting is initiated at the UE... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.1.3 Test purpose | To verify that a CC entity in CC-state U9, "Mobile Terminating Call Confirmed", (if signalled by the network in previous SETUP message that it may alert) will either send a ALERTING message to its peer entity and enter state U7, or send a CONNECT message to its peer entity and enter U8. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.1.4 Method of test | Related ICS/IXIT statements
- supported MT circuit switched basic services;
- MT circuit switched basic services for which immediate connect is not used.
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 int... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.1.5 Test requirements | At step A1 the UE shall send a CONNECT message and enter U8 if the network has signalled in previous SETUP message that UE may not alert.
At step B1 the UE shall send an ALERTING message and enter state U7 if the network has signalled in previous SETUP message that UE may alert. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.2 Incoming call / U9 mobile terminating call confirmed / DTCH assignment | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.2.1 Definition | The call control entity of the UE being in the state, U9, a radio bearer establishment procedure is performed for traffic channel. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.2.2 Conformance requirement | 1) It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call establishment phase.
Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but may have some secondary effects (see e.g. TS 24.0... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.2.3 Test purpose | To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", when a traffic channel is allocated by the network performing the radio bearer establishment procedure, shall sends an ALERTING message and enters state U7. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.2.4 Method of test | Related ICS/IXIT statements
- supported MT circuit switched basic services;
- MT circuit switched basic services for which immediate connect is not used.
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 int... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.2.5 Test requirements | After step 1 the UE shall send an ALERTING message and enter state U7. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.3 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.4 Incoming call / U9 mobile terminating call confirmed / DISCONNECT received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.4.1 Definition | The call control entity of the UE being in the state, U9, a DISCONNECT message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.4.2 Conformance requirement | The call control entity of the UE in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon the receipt of a DISCONNECT message without progress indicator information element or with progress indicator different from #8:
- stop all running call control timers;... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.4.3 Test purpose | To verify that a CC-entity of the UE in CC-state U9, "Mobile Terminating Call Confirmed", upon receipt of a DISCONNECT returns a RELEASE message and enters the CC-state U19, "Release Request". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.4.4 Method of test | Related ICS/IXIT statements
- supported MT circuit switched basic services;
- MT circuit switched basic services for which immediate connect is not used.
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 int... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.3.4.5 Test requirements | After step 1 the UE shall return a RELEASE message and enter the CC-state U19, "Release Request". |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.