hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.2.3.2.2 Conformance requirement | A collision of a UE and network initiated PDP context modification procedures is identified by the UE if a MODIFY PDP CONTEXT REQUEST message is received from the network after the UE has sent a MODIFY PDP CONTEXT REQUEST message itself, and both messages contain the same TI and the UE has not yet received a MODIFY PDP... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.2.3.2.3 Test purpose | To test behaviour of the UE when it identifies collision of the UE and SS initiated PDP context modification with the same TI. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.2.3.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
- Method of activating a PDP context
Test procedure
A PDP context is activated by the user and accepted b... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.2.3.2.5 Test requirements | In step 6, the UE shall terminate internally the UE initiated PDP context modification procedure and proceed with SS initiated PDP context modification. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3 PDP context deactivation procedures | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.1 PDP context deactivation initiated by the UE | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.1.2 Conformance requirement | In order to deactivate a PDP context, the UE sends a DEACTIVATE PDP CONTEXT REQUEST message to the network, enters the state PDP-INACTIVE-PENDING and starts timer T3390. The message contains the transaction identifier (TI) in use for the PDP context to be deactivated and a cause code that typically indicates one of the... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.1.3 Test purpose | To test the behaviour of the UE upon receipt of a DEACTIVATE PDP CONTEXT ACCEPT message from the SS in PDP context deactivation procedure initiated by the UE.
To test the behaviour of the UE upon receipt of a session management message (except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS) specifying a transaction identi... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.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
- Method of activating a PDP context
- Method of deactivating the PDP context
- Support of automatic PS a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.1.5 Test requirements | At step 1a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to one of the following causes:
• Originating Streaming Call;
• Originating Interactive Call or
• Originating Background Call
• OriginatingSubscribedTrafficCall
In PDP context deactivation procedure initiated by the UE, u... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.2 PDP context deactivation initiated by the network | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.2.2 Conformance requirement | In order to deactivate a PDP context, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the UE and starts timer T3395. The message contains the transaction identifier in use for the PDP context to be deactivated and a cause code that typically indicates one of the following causes:
# 36: regular PDP context... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.2.3 Test purpose | To test the behaviour of the UE upon receipt of a DEACTIVATE PDP CONTEXT REQUEST message from the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.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
- Method of activating a PDP context
- Support of automatic PS attach procedure at switch on yes/no
Test... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.2.5 Test requirements | At step 1a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to one of the following causes:
• Originating Streaming Call;
• Originating Interactive Call or
• Originating Background Call
• OriginatingSubscribedTrafficCall
Upon receipt of a request for deactivation of a PDP context ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3 Abnormal cases | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.1 T3390 Expiry | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.1.2 Conformance requirement | Expiry of timers
In the UE:
On the first expiry of timer T3390, the UE shall resent the message DEACTIVATE PDP CONTEXT REQUEST and shall reset and restart the timer T3390. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3390, the UE shall release all resources allocated and shall erase th... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.1.3 Test purpose | To test the behaviour of the UE when the SS does not reply to a DEACTIVATE PDP CONTEXT REQUEST message from the UE. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.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
- Method of activating a PDP context
- Method of deactivating a PDP context
Test procedure
A PDP context ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.1.5 Test requirements | If SS does not respond to the UE initiated PDP context deactivation procedure, the UE shall retransmit four more DEACTIVATE PDP CONTEXT Requests four times, with T3390 timer expiry between the successive messages, before releasing resources allocated to the PDP context and deleting PDP context related data. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.2 Collision of UE and network initiated PDP context deactivation requests | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.2.2 Conformance requirement | If the UE and the network initiated PDP context deactivation requests collide, the UE and the network shall each reply with the message DEACTIVATE PDP CONTEXT ACCEPT and shall stop timer T3390 and T3395, respectively.
Reference
3GPP TS 24.008 clause 6.1.3.4.3 b). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.2.3 Test purpose | To test the behaviour of the UE when there is a collision between an UE initiated and network initiated context deactivation. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.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
- Method of activating a PDP context
- Method of deactivating a PDP context
Test procedure
A PDP context i... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.3.3.2.5 Test requirements | When UE and SS initiated PDP context deactivation requests collide, the UE shall reply with DEACTIVATE PDP CONTEXT ACCEPT to the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4.1 Error cases | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4.1.2 Conformance requirement | The mobile station shall ignore a session management message with TI EXT bit = 0. Otherwise, the following procedures shall apply:
- Whenever any session management message, except REQUEST PDP CONTEXT ACTIVATION or SM-STATUS, is received by the UE specifying a transaction identifier which is not recognized as relating ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4.1.3 Test purpose | To test the behaviour of the UE when messages with unknown or unforeseen transaction identifiers or non-semantical mandatory information element errors occur. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4.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
- Method of context activation
Test procedure
A PDP context activation is requested by the SS with the t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.4.1.5 Test requirements | TBD. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.5 MBMS Context Activation | 11.5.1m MBMS Context Activation requested by the network, Successful and Unsuccessful procedure / MBMS Multicast Service
11.5.1m.1 Definition
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.5.1m.2 Conformance requirement
The purpose of this procedure is to establish an MBMS context in the M... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.6 MBMS Context deactivation | 11.6.1m MBMS Context deactivation requested by the network, Successful / MBMS Multicast Service
11.6.1m.1 Definition
This test case is applicable for Rel-6 UEs that support MBMS multicast services.
11.6.1m.2 Conformance requirement
The purpose of the MBMS context deactivation procedure is to deactivate an existing MBMS... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.6.2 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.6.3 Void | 11.7m Network Feature Support IE for MBMS / MBMS Multicast Service
11.7m.1 Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.7m.2 Conformance requirement
The network informs the MS about the support of specific features, such as LCS-MOLR or MBMS, in the "Network f... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8 MBMS Service Request | 11.8.1m MBMS Service request procedure not accepted by the network / MBMS Multicast Service
11.8.1m.1 Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.8.1m.2 Conformance requirement
If the Service request cannot be accepted, the network returns a SERVICE REJECT m... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8.2 MBMS Service Request procedure collision with Routing Area Update/ MBMS Selected Service | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8.2.1 Definition and applicability | This test is applicable for Rel-6 UEs supporting MBMS broadcast services. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8.2.2 Conformance requirement | The following abnormal cases can be identified:
…
e) Routing area update procedure is triggered
If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined before the security mode control procedure is completed, a SERVICE ACCEPT or SERVICE REJECT message has been re... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8.2.3 Test purpose | To verify that the UE correctly aborts a SERVICE REQUEST procedure if a ROUTING AREA UPDATE procedure is initiated before the SERVICE REQUEST procedure has been completed. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8.2.4 Method of test | Initial conditions
System Simulator:
2 MBMS cells, cell A in MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in MCC1/MNC1/LAC1/RAC2 (RAI-4).
Both cells are operating in network operation mode II.
User Equipment:
The UE is in "PMM-IDLE” mode and is interested in the selected service provided by the SS (included in MBMS_ACTIVATED_SE... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.8.2.5 Test requirements | In step 9 the UE shall send ROUTING AREA UPDATE REQUEST.
11.8.2m MBMS Service Request procedure collision with Routing Area Update / MBMS Multicast Service
11.8.2.1m Definition and applicability
This test is applicable for Rel-6 UEs supporting MBMS multicast services.
11.8.2.2m Conformance requirement
Same conformance ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9 UE routing of uplink packets | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9.1 UE routing of uplink packets | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9.1.2 Conformance requirement | References: The conformance requirements covered in the present TC are specified in: TS 23.060, clause 15.3.2.0 and TS 24.008, clause 10.5.6.12.
[TS 23.060, clause 15.3.2.0]
Each valid downlink- and uplink-packet filter contains a unique identifier within a given TFT, an evaluation precedence index that is unique among... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9.1.3 Test purpose | 1. To verify that the UE, when it has IP packets to transmit, evaluates the configured packet filters in the correct evaluation order and transmits IP packets in uplink on the bearer associated with the matched packet filter when having a primary and two secondary PDP contexts active
2. To verify that the UE, when it h... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9.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
- Method of activating a PDP context
- Support of automatic PS attach procedure at switch on yes/no
Test procedure
A PDP conte... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 11.9.1.5 Test requirements | To pass the test the UE shall:
- at step 20 transmit an IP PDU containing IP Packet#N on the radio bearer associated with the PDP context as specified by Table 11.9.1.4-2 for Sub-test index=N.
- at step 22 send a MODIFY PDP CONTEXT ACCEPT message.
- at step 24 transmit an IP PDU containing IP Packet#18 on the radio bea... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12 Elementary procedure for Packet Switched Mobility Management | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.1 Applicability, default conditions and default messages | All test cases for PS mobility management apply for all PS mobiles unless otherwise stated in a specific test. Within each test case, the ICS statement indicates whether the test shall be performed for mobiles that can only operate in mode - class A, only in mode - class C , or in both mode - class A and C. For some pr... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2 PS attach procedure | This procedure is used to indicate for the network that the IMSI is available for traffic by establishment of a GMM context. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1 Normal PS attach | The normal PS attach procedure is a GMM procedure used by PS UEs of UE operation mode A or C to IMSI attach for PS services only. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.1 PS attach / accepted | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.1.2 Conformance requirement | 1) If the network accepts the PS attach procedure (signalled by an IMSI) and allocates a P-TMSI, the UE shall acknowledge the P-TMSI and continue communication with the P-TMSI.
2) If the network accepts the PS attach procedure (signalled by P-TMSI) and reallocates a new P-TMSI, the UE shall acknowledge the new P-TMSI a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.1.3 Test purpose | To test the behaviour of the UE if the network accepts the PS attach procedure.
The following cases are identified:
1) P-TMSI / P-TMSI signature is allocated;
2) P-TMSI / P-TMSI signature is reallocated;
3) Old P-TMSI / P-TMSI signature is not changed. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.1.4 Method of test | Initial condition
System Simulator:
One cell operating in network operation mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE to prevent repeated CS domain registration and/or IMSI Detach by UEs in operation... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.1.5 Test requirements | At step 2a, 10a and 19a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Registration".
At step 6a and 22a the UE shall send an RRC CONNECTION REQUEST message with the IE Establishment cause set to "Terminating Interactive Call".
At step 8a, 17a and 24a the UE shall send an RR... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.2 PS attach / rejected / IMSI invalid / illegal UE | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.2.2 Conformance requirement | 1) If the network rejects a PS attach procedure from the User Equipment with the cause 'Illegal MS, the User Equipment shall consider USIM invalid for PS services until power is switched off or USIM is removed.
2) If the network rejects a PS attach procedure from the User Equipment with the cause 'Illegal MS the User E... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.2.3 Test purpose | To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'illegal MS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.2.4 Method of test | Initial condition
System Simulator:
Three cells (not simultaneously activated), cell A with MCC1/MNC1/LAC1/RAC1 (RAI-1), cell B in
MCC1/MNC1/LAC2/RAC1 (RAI-3), cell C in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All three cells are operating in network operation mode II (in case of UE operation mode A).
The SIB1 IE "CN domain speci... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.2.5 Test requirements | At step4, when the UE is powered up or switched on, UE shall:
- initiate the PS attach procedure with the information elements specified in the above Expected Sequence.
At step8, 10, 13 and 15, UE shall:
- not send the ATTACH REQUEST message to SS, even if there is an instruction of attach request from MMI or from AT c... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.3 PS attach / rejected / IMSI invalid / PS services not allowed | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.3.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.3.2 Conformance requirement | 1) If the network rejects a PS attach procedure from the User Equipment with the cause 'GPRS services not allowed', the User Equipment shall consider USIM invalid for PS services until power is switched off or USIM is removed.
2) If the network rejects a PS attach procedure from the User Equipment with the cause 'GPRS ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.3.3 Test purpose | To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'GPRS services not allowed' (no valid PS-subscription for the IMSI). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.3.4 Method of test | Initial condition
System Simulator:
Two cells (not simultaneously activated), cell A in MCC1/MNC1/LAC1/RAC1 (HPLMN, RAI-1) and cell B in MCC2/MNC1/LAC1/RAC1 (RAI-2).
Both cells are operating in network operation mode II.
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00"... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.3.5 Test requirements | At step4, when the UE is powered up or switched on, UE shall:
- initiate the PS attach procedure with information elements specified in the above Expected Sequence.
At step8, UE shall:
- not perform a PS attach procedure.
At step11, after the UE is switched on or a USIM is replaced, UE shall:
- perform the PS attach pr... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.4 PS attach / rejected / PLMN not allowed | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.4.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.4.2 Conformance requirement | 1) If the network rejects a PS attach procedure from the User Equipment with the cause 'PLMN not allowed' the User Equipment shall:
1.1 not perform PS attach when switched on in the same routing area or location area (except for the HPLMN).
1.2 not perform PS attach when in the same PLMN and when that PLMN is not selec... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.4.3 Test purpose | To test the behaviour of the UE if the network rejects the PS attach procedure of the UE with the cause 'PLMN not allowed'. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.4.4 Method of test | Proc 1: Test procedure 1
Initial condition
System Simulator:
Four cells (not simultaneously activated), cell A in MCC1/MNC2/LAC1/RAC1 (RAI-8), cell B in MCC1/MNC2/LAC1/RAC1 (RAI-8), cell C in MCC1/MNC2/LAC2/RAC1 (RAI-9) and cell D in MCC2/MNC1/LAC1/RAC1 (RAI-2).
All four cells are operating in network operation mode II... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.4.5 Test requirements | Test requirements for test procedure 1
At step4, when the UE is powered on or switched on, UE shall:
- initiate the PS attach procedure with information elements specified in the above Expected Sequence.
At step6, UE shall:
- not perform PS attach procedure.
UE shall perform the following actions depending on the PLMN ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.6 PS attach / abnormal cases / access barred due to access class control | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.6.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.6.2 Conformance requirement | 1) The UE shall not perform PS attach procedure, but stays in the current serving cell and applies normal cell reselection process.
2) The User Equipment shall perform the PS attach procedure when:
2.1 Access is granted.
2.2 Cell is changed.
Reference
3GPP TS 24.008 clause 4.7.3.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.6.3 Test purpose | Test purpose1
To test the behaviour of the UE in case of access class control (access is granted).
Test purpose2
To test the behaviour of the UE in case of access class control (Cell is changed). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.6.4 Method of test | Proc 1: Test procedure1
Initial condition
An access class x (0-15) is arbitrarily chosen. The USIM is programmed with this access class x. Communication with User Equipments using access class x is initially indicated to be barred.
System Simulator:
One cell operating in network operation mode II.
Access class x barred... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.6.5 Test requirements | Test requirements for Test procedure1
At step4, when the UE access class x is barred, UE shall:
- not perform a PS attach procedure.
At step7, when the UE access class x is granted, UE shall:
initiate the PS attach procedure.
Test requirements for Test procedure2
At step5, when the UE access class x is barred, UE shall... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.7 PS attach / abnormal cases / change of routing area | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.7.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.7.2 Conformance requirement | If a cell change into a new routing area occurs before an ATTACH ACCEPT or ATTACH REJECT message has been received, the GPRS attach procedure shall be aborted and re-initiated immediately.
Reference
3GPP TS 24.008 clause 4.7.3.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.7.3 Test purpose | To test the behaviour of the UE in case of procedure collision. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.7.4 Method of test | Initial condition
System Simulator:
One cell with MCC1/MNC1/LAC1/RAC1 (RAI-1)
The cell is operating in network operation mode II (in case of UE operation mode A).
The SIB1 IE "CN domain specific NAS system information", for the CS Domain, is set to value "00 00" (T3212 value is set to 0 and ATT flag is set to FALSE).
U... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.7.5 Test requirements | At step4, when the UE is powered up or switched on, UE shall:
- initiate the PS attach procedure with information elements specified in the above Expected sequence.
At step8, as the UE has received a new RAI in the UTRAN MOBILITY INFORMATION message before the ATTACH ACCEPT message or the ATTACH REJECT message is recei... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.8 PS attach / abnormal cases / power off | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.8.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.8.2 Conformance requirement | When power is switched off before ATTACH ACCEPT message is received by the UE, the UE shall abort the PS attach procedure and perform a PS detach procedure.
Reference
3GPP TS 24.008 clause 4.7.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.8.3 Test purpose | To test the behaviour of the UE in case of procedure collision. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 12.2.1.8.4 Method of test | Initial condition
System Simulator:
One cell operating in network operation mode II.
User Equipment:
The UE has a valid P-TMSI-1 and RAI-1.
Related ICS/IXIT statements
Support of PS service Yes/No
UE operation mode C Yes/No
UE operation mode A Yes/No
Switch off on button Yes/No
Automatic PS attach procedure at swi... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.