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.3.5.6.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.3.5.6.3 Test purpose | 1) To verify that a CC entity of a UE in CC-state U8, "Connect Request", upon receipt of a RELEASE will return a RELEASE COMPLETE and enter 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 relating to the seven mobile terminating transac... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.6.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.
The UE is brought into the state U8 by using table 10.1.3/1.
Test procedure
An MT circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.6.5 Test requirements | After step 1 a UE shall return a 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.3.5.7 Incoming call / U8 connect request / lower layer failure | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.7.1 Definition | The call control entity of the UE being in the state, U8, 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.3.5.7.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.3.5.7.3 Test purpose | To verify that a CC entity of a UE in CC-state U8, "Connect Request", having detected a lower layer failure returns to idle mode, the CC entity is in state U0, "Null". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.7.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.
The UE is brought into the state U8 by using table 10.1.3/1.
Test procedure
An MT circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.7.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.3.5.8 Incoming call / U8 connect request / DTCH assignment | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.8.1 Definition | The call control entity of the UE being in the state, U8, a radio bearer establishment procedure is performed for traffic channel. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.8.2 Conformance requirement | 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.008 ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.8.3 Test purpose | To verify that a CC entity of a UE in CC-state U8, "Connect Request", when a traffic channel is allocated by the network performing the radio bearer establishment procedure, stays in the CC-state U8. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.8.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.
The UE is brought into the state U8 by using table 10.1.3/1.
Test procedure
An MT circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.8.5 Test requirements | After step 1 the CC-state U8, "Connect Request", shall remain unchanged. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.9 Incoming call / U8 connect request / unknown message received | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.9.1 Definition | The call control entity of the UE being in the state, U8, an unknown message is received by the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.9.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.3.5.9.3 Test purpose | To verify that a CC entity of a UE in CC-state U8, "Connect Request", having received an unknown message from its peer entity returns a STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.9.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.
The UE is brought into the state U8 by using table 10.1.3/1.
Test procedure
An MT circuit switched ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.3.5.9.5 Test requirements | After step 1 a UE shall return a STATUS message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4 In call functions | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1 In-call functions / DTMF information transfer | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1.1 In-call functions / DTMF information transfer / basic procedures | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1.1.1 Definition | Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system primarily used from terminal instruments in telecommunication networks. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1.1.2 Conformance requirement | 1) A user may cause a DTMF tone to be generated e.g. by depression of a key in the UE. The relevant action is interpreted by the UE as a requirement for a DTMF digit to be sent in a START DTMF message on an established FACCH. This message contains the value of the digit to be transmitted (0, 1, ..., 9, A, B, C, D, *, #... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1.1.3 Test purpose | 1) To verify that an UE supporting the Mobile originating DTMF protocol control procedure, having a CC entity for speech in state U10, "Active": when made to send a DTMF tone, sends a START DTMF message.
2) To verify that an UE supporting the Mobile originating DTMF protocol control procedure, having a CC entity for sp... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1.1.4 Method of test | Related ICS/IXIT statements
- supported teleservices;
- supported character set (e.g. 0‑9, #, *, A, B, C, D);
- if and how DTMF tone is indicated to the user.
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 brough... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.1.1.5 Test requirements | Upon a user making to send a DTMF tone the UE shall send a START DTMF message on the FACCH to SS.
The SS will verify that the transmitted information corresponds to the digit pressed in the UE.
After step s 2 and 7 (successful DTMF transmission) the CC-state U10, "Active", shall remain unchanged.
After step 12 (unsucce... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2 In-call functions / user notification | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2.1 In-call functions / User notification / UE terminated | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2.1.1 Definition | This is a case for testing user notification procedure terminated by the user equipment. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2.1.2 Conformance requirement | The mobile terminating user notification procedure allows the network to notify a mobile station of any appropriate call-related event during the "active" state of a call. The procedure consists in the network sending a NOTIFY message to the mobile station. No state change occurs at any of the interface sides following... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2.1.3 Test purpose | To verify that a CC entity of a UE in CC-state U10, "active", upon receiving of a NOTIFY message remains in the active state. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2.1.4 Method of test | Related ICS/IXIT statements
- supported 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 U10 "Active" by using table 10.1.2/1.
Test procedure
The UE being in ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.2.1.5 Test requirements | After step 1 the CC-state U10, "active", shall remain unchanged. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3 In-call functions / channel changes | The two following test cases are for testing some elementary radio resource level procedures during an active state of a call to ensure call maintenance also during Hard handover. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.1 In-call functions / channel changes / a successful channel change in active state/ Hard handover | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.1.1 Definition | This is a case to test a change of the frequency of a physical channel during active state of a call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.1.2 Conformance requirement | 1) The UE being in the active state after having successful completed a physical channel reconfiguration, shall remain in the active state.
References
TS 24.008 clause 5.3.4.3.2, TS 25.331 clause 8.3.5. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.1.3 Test purpose | To verify that the UE being in the active state after having successful completed a physical channel reconfiguration remains in the active state. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.1.4 Method of test | Related ICS/IXIT statements
- supported 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 U10 "Active" by using table 10.1.2/1.
Test procedure
The UE being in ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.1.5 Test requirements | After step 2 the UE shall remain in the active state. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.2 In-call functions / channel changes / an unsuccessful channel change in active mode/Hard handover | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.2.1 Definition | This is a case to test an unsuccessful change of the frequency of a physical channel during active state of a call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.2.2 Conformance requirement | 1) The UE, when returning to the old channel after physical channel reconfiguration failure, shall remain in the active state.
References
TS 24.008 clause 5.3.4.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.2.3 Test purpose | To verify that the UE, when returning to the old channel after physical channel reconfiguration failure, will remain in the active state. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.2.4 Method of test | Related ICS/IXIT statements
- supported 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 U10 "Active" by using table 10.1.2/1.
Test procedure
The SS sends a P... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.3.2.5 Test requirements | After step 2 the UE shall remain in the active state. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.4 In-call functions / UE terminated in-call modification | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.4.1 In-call functions / UE terminated in-call modification / modify when new mode is not supported | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5 In-call functions / UE originated in-call modification | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.1 In-call functions / UE originated in-call modification / a successful case of modifying | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.2 In-call functions / UE originated in-call modification / modify rejected | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.3 In-call functions / UE originated in-call modification / an abnormal case of acceptance | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.4 In-call functions / UE originated in-call modification / an abnormal case of rejection | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.5 In-call functions / UE originated in-call modification / time-out of timer T323 | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.6 In-call functions / UE originated in-call modification / a successful channel change in state mobile originating modify | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.7 In-call functions / UE originated in-call modification / an unsuccessful channel change in state mobile originating modify | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.8 In-call functions / UE originated in-call modification / unknown message received | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.1.4.5.9 In-call functions / UE originated in-call modification / a release complete received | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.2 Call Re-establishment | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.2.1 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.3 User to user signalling | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.3.1 Definition | The "user to user" information element is used to convey information between the mobile user and a remote ISDN user.
NOTE: There is no test for an UE originating call including a "user-user" information element since it is not a mandatory UE feature. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.3.2 Conformance requirement | The inclusion of the "user-user" information element in downlink call control messages shall cause no adverse effects on the operation of the UE.
References
TS 24.008 clauses 9.3.7, 9.3.23.1 and 10.5.4.25. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.3.3 Purpose of the test | The purpose of this test is to verify that inclusion of the "user-user" information element in either of the down link messages, SETUP or DISCONNECT causes no adverse effects on the operation of the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.3.4 Method of test | Related ICS/IXIT statements
- Supported MT circuit switched basic services.
- Support of user-user information element, and details of suitable codings.
Initial conditions.
System Simulator:
The SS simulates 1 cell, with default parameters.
User Equipment:
The UE is in MM-state "idle updated", with a valid TMSI and CKS... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 10.3.5 Test requirements | After steps 1 and 3 the inclusion of the "user-user" information element in downlink call control messages shall cause no adverse effects on the operation of the UE.
11 Session Management Procedures |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1 PDP context activation | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1 Initiated by the UE | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.1 Attach initiated by context activation/QoS Offered by Network is the QoS Requested | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.1.2 Conformance requirement | SM procedures for identified access can only be performed if a GMM context has been established between the UE and the network. If no GMM context has been established, the MM sublayer has to initiate the establishment of a GMM context by use of the GMM procedures as described in chapter 4, 3GPP TS 24.008. After GMM con... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.1.3 Test purpose | To check that the UE initiates a PS attach, if one is not already active, when PDP context activation is requested.
To test the behaviour of the UE when SS responds to the PDP context activation request with the requested QoS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.1.4 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
- PS Supported yes/no
- Auto Attach supported yes / no
- Method of context activation
Test procedure
The UE is attached, then ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.1.5 Test requirements | At step 0 the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Detach".
At step 3a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".
When requesting a PDP context activation, the UE shall:
- initiate PS ATTACH;
- when the SS... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.2 QoS offered by the network is a lower QoS | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.2.1 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.2.2 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.3 Dual priority / T3396 override | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.3.1 Definition | Void |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.3.2 Conformance requirement | If timer T3396 is running for a specific APN, because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.3.3 Test purpose | To verify that a UE configured for dual priority that has T3396 is running for a specific APN can send a request to activate or modify the same APN, with low priority indicator set to "MS is not configured for NAS signalling low priority" |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.3.4 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
The UE is configured for NAS signalling low priority
The UE is configured for NAS signalling low priority override
The UE is equipped with a USIM containin... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.3.5 Test requirements | Step 2: ACTIVATE PDP CONTEXT REQUEST message contains the Device properties IE set to ‘MS is configured for NAS signalling low priority’
Step 5: ACTIVATE PDP CONTEXT REQUEST message contains the Device properties IE set to ‘MS is not configured for NAS signalling low priority’. This message shall be sent before the exp... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.4 Dual priority / T3346 override | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.4.1 Definition | Void |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.4.2 Conformance requirement | The following abnormal cases can be identified:
…
m) Timer T3346 is running
The MS shall not start the service request procedure unless:
- the MS receives a paging; or
- the MS is an MS configured to use AC11 – 15 in selected PLMN; or
- the MS has a PDN connection for emergency bearer services established; or
- the MS ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.4.3 Test purpose | To verify that a MS configured for dual priority and which has sent a SERVICE REQUEST message indicating low NAS signalling priority, when it receives a SERVICE REJECT message with timer T3346 and MM cause value #22 “Congestion”, the UE sends an ACTIVATE PDP CONTEXT REQUEST message with the low priority indicator set t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.4.4 Method of test | Initial condition
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is equipped with a USIM containing default values except for those listed below.
USIM field
Value
EFUST
Service 96 is supported.
EFNASCONFIG
“NAS_SignallingPriority is set to “NAS signalling low priority” as defined in TS 24.368, cla... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.1.4.5 Test requirements | Step 4: SERVICE REQUEST message contains the Device properties IE set to ‘MS is configured for NAS signalling low priority’.
Step 7: SERVICE REQUEST message contains the Device properties IE set to ‘MS is not configured for NAS signalling low priority’. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.2 PDP context activation requested by the network, successful and unsuccessful | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.2.1 Definition | Void |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.2.2 Conformance requirement | 1) Successful PDP context activation requested by the network
In order to request a PDP context activation, the network sends a REQUEST PDP CONTEXT ACTIVATION message to the UE and starts timer T3385. The message contains an offered PDP address. If available, the APN shall be included in the REQUEST PDP CONTEXT ACTIVAT... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.2.3 Test purpose | To test behaviour of the UE upon receipt of a PDP context activation request from the SS:
a) When UE supports PDP context activation requested by the network
b) When UE supporting PDP context activation requested by the network, receives REQUEST PDP CONTEXT ACTIVATION message with transaction identifier relating to an ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.2.4 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in GMM-state "GMM-REGISTERED, normal service" with valid P-TMSI and CKSN.
Related ICS/IXIT statements
- PS Supported yes/no
Test procedure
A REQUEST PDP CONTEXT ACTIVATION message is sent by the SS. If UE does not accept PDP cont... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.2.5 Test requirements | The UE that is configured to support one or more PDP contexts simultaneously shall:
- accept PDP context activation initiated by the SS if number of active contexts is lower than the maximum.
- locally deactivate the old PDP context when a REQUEST PDP CONTEXT ACTIVATION message is received, specifying a transaction ide... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.1.3 Abnormal Cases |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.