14 UICC interface during eDRX
31.1273GPPnon-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specificationRelease 17TSUICC-terminal interaction
14.1 UICC interface during eDRX for E-UTRAN – eDRX is not supported by the UICC
14.1.1 Definition and applicability
In order to reduce power consumption when the UE uses extended idle mode DRX cycle, the UE may optionally deactivate the UICC during the extended idle mode DRX cycle.
14.1.2 Conformance requirement
CR 1 In case the UICC does not support the UICC suspension mechanism, the PIN of the USIM is disabled and deactivation of UICC is authorized in EFAD, the UE may optionally deactivate the UICC (as specified in clause 6A.1 of TS 31.101 [33]) during the extended idle mode DRX cycle.
Reference:
– TS 31.102 [19], clause 5.1.11;
– TS 24.301 [21], clauses 5.3.12.
– TS 23.401 [42], clause 5.13a.
– TS 31.101 [33], clause 6A.1.
14.1.3 Test purpose
1) To verify that UE does not deactivate the UICC in case the ME is not authorized to modify the polling interval and/or disable the UICC interface during extended DRX cycle in EFAD in USIM.
14.1.4 Method of test
14.1.4.1 Initial conditions
The UE is configured to request the use of eDRX (in the AttachRequest and TrackingAreaUpdate messages).
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The default E-UTRAN UICC is used with the following exceptions:
EFUMPC (UICC Maximum Power Consumption)
Logically:
UICC maximum power consumption: 60 mA
Operator defined time out (T_OP): 5 seconds
Additional information: UICC does not require increased idle current
UICC does not support the UICC suspension procedure
Byte 4 and byte 5: RFU
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Hex |
3C |
05 |
00 |
00 |
00 |
The PIN of the USIM is enabled and verified.
14.1.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The UE is switched on. |
|||
|
2 |
UE > TT |
The UE requests RRC Connection |
The TT responds with RCC Connection setup |
||
|
3 |
UE > TT |
The UE transmits an AttachRequest message including the eDRX parameters |
|||
|
4 |
TT > UE |
|
If AttachRequest in step 3) above also contains T3324, the AttachAccept message shall contain T3324 set to "deactivated". If AttachRequest in step 3) does not contain T3324, the AttachAccept message shall not contain T3324. |
||
|
5 |
UE > TT |
The UE transmits the AttachComplete during registration from the UE |
The TT sends RRCConnectionRelease / RRCConnectionRelease-NB. |
CR1 |
|
|
6 |
TT > UE |
The TT transmits Paging/Paging-NB using the S-TMSI in a valid paging occasion within the PTW of the paging Hyperframes as per Idle eDRX. |
CR1 |
||
|
7 |
UE > TT |
Send RRCConnectionRequest / RRCConnectionRequest-NB |
The TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
CR1 |
|
|
8 |
UE > TT |
Send RRCConnectionSetupComplete / RRCConnectionSetupComplete-NB |
CR1 |
||
|
9 |
UE > TT |
The UE sends ServiceRequest |
The TT sends ServiceAccept followed by RRCConnectionRelease / RRCConnectionRelease-NB |
CR1 |
|
|
10 |
UE |
|
14.1.5 Acceptance criteria
CR 1 is met if the UE does not deactivate the UICC or send SUSPEND UICC command after step 5).
14.2 UICC interface during eDRX for E-UTRAN – eDRX is not accepted by E-USS/NB-SS
14.2.1 Definition and applicability
In order to reduce power consumption when the UE uses extended idle mode DRX cycle, the UE may optionally deactivate the UICC during the extended idle mode DRX cycle.
14.2.2 Conformance requirement
CR 1 In case the UICC does not support the UICC suspension mechanism, the PIN of the USIM is disabled and deactivation of UICC is authorized in EFAD, the UE may optionally deactivate the UICC (as specified in clause 6A.1 of 3GPP TS 31.101 [39]) during the extended idle mode DRX cycle.
Reference:
– TS 31.102 [19], clause 5.1.11;
– TS 24.301 [21], clauses 5.3.12;
– TS 23.401 [42], clause 5.13a;
– TS 31.101 [33], clause 6A.1.
14.2.3 Test purpose
1) To verify that UE does not deactivate the UICC in case extended DRX cycle is not supported by the network
14.2.4 Method of test
14.2.4.1 Initial conditions
The UE is configured to request the use of eDRX (in the AttachRequest and TrackingAreaUpdate messages).
The E-USS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The NB-SS transmits on the BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 246/081/0001.
– Access control: unrestricted.
The default E-UTRAN UICC is used with the following exceptions:
EFAD (Administrative Data)
Logically: Normal operation + specific facilities;
Ciphering indicator feature disabled;
CSG Display Control: for every PLMN not included in EF_OCSGL, or for which a CSG display indicator tag is not present, all available CSGs can be displayed without any restriction;
ProSe services for Public Safety: the ME is not authorized for ProSe services for Public Safety usage without contacting the ProSe Function;
Extended DRX cycle: the ME is authorized to modify the polling interval and/or disable the UICC interface during extended DRX cycle;
Length of MNC in the IMSI: 3.
Coding:
|
Byte |
B1 |
B2 |
B3 |
B4 |
|
Hex |
01 |
00 |
08 |
03 |
The PIN of the USIM is disabled.
14.2.4.2 Procedure
|
Step |
Direction |
Action |
Comment |
REQ |
SA |
|
1 |
UE |
The UE is switched on. |
|||
|
2 |
UE > TT |
The UE requests RRC Connection |
The TT responds with RCC Connection setup |
||
|
3 |
UE > TT |
The UE transmits an AttachRequest message including the eDRX parameters |
|||
|
4 |
TT > UE |
|
If AttachRequest in step 3) above also contains T3324, the AttachAccept message shall contain T3324 set to "deactivated". If AttachRequest in step 3) does not contain T3324, the AttachAccept message shall not contain T3324. |
||
|
5 |
UE > TT |
The UE transmits the AttachComplete during registration from the UE |
The TT sends RRCConnectionRelease/RRCConnectionRelease-NB. |
CR1 |
|
|
6 |
TT > UE |
The TT transmits Paging/Paging-NB in a valid paging occasion as per normal DRX. |
CR1 |
||
|
7 |
UE > TT |
Send RRCConnectionRequest / RRCConnectionRequest-NB |
The TT responds with a RRCConnectionSetup / RRCConnectionSetup-NB |
CR1 |
|
|
8 |
UE > TT |
Send RRCConnectionSetupComplete / RRCConnectionSetupComplete-NB |
CR1 |
||
|
9 |
UE > TT |
The UE sends ServiceRequest |
The TT sends ServiceAccept followed by RRCConnectionRelease/RRCConnectionRelease-NB |
CR1 |
|
|
10 |
UE |
|
14.2.5 Acceptance criteria
CR 1 is met if the UE does not deactivate the UICC or send SUSPEND UICC command after step 5).
14.3 UICC interface during eDRX for E-UTRAN – UICC deactivation during eDRX
RFU – agreed method to verify contents of EF_ICCID, EF_IMSI and EF_EPSLOCI needed.
14.4 UICC interface during eDRX for E-UTRAN– SUSPEND UICC
Not applicable – verification of correct activation and deactivation procedure.