14 UICC interface during eDRX
31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification
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
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 [4], clause 5.1.11;
– TS 24.301 [26], clauses 5.3.12.
– TS 23.401 [37], clause 5.13a.
– TS 31.101 [39] in 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 ATTACH REQUEST and TRACKING AREA UPDATE 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
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Coding: |
3C |
05 |
00 |
00 |
00 |
The PIN of the USIM is enabled and verified.
14.1.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and transmits an ATTACH REQUEST message to the E-USS/NB-SS including eDRX parameters.
c) The E-USS/NB-SS sends the ATTACH ACCEPT message containing eDRX set to eDRX_V and PTW set to PTW_V. If ATTACH REQUEST in step b) above also contains T3324, the ATTACH ACCEPT message shall contain T3324 set to "deactivated". If ATTACH REQUEST in step b) does not contain T3324, the ATTACH ACCEPT message shall not contain T3324.
d) After receipt of the AttachComplete during registration from the UE, the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB, to the UE.
e) The E-USS/NB-SS transmits Paging/Paging-NB to the UE using the S-TMSI in a valid paging occasion within the PTW of the paging Hyperframes as per Idle eDRX.
f) After receipt of RRCConnectionRequest/RRCConnectionRequest-NB message from the UE, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB message to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete–NB sent by the UE to the E-USS/NB-SS.
g) The terminal sends Service Request, the E-USS/NB-SS sends SERVICE ACCEPT followed by RRCConnectionRelease/RRCConnectionRelease-NB to the UE.
h) The UE is switched off.
14.1.5 Acceptance criteria
1) After step d) the UE shall not deactivate the UICC or send SUSPEND UICC command.
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
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:
– 3GPP TS 31.102 [4], clause 5.1.11;
– TS 24.301 [26], clauses 5.3.12.
– TS 23.401 [37], clause 5.13a
– 3GPP TS 31.101 [39] in 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 ATTACH REQUEST and TRACKING AREA UPDATE 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 installed into the Terminal with following exception:
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: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
01 |
00 |
08 |
03 |
The PIN of the USIM is disabled.
14.2.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and transmits an ATTACH REQUEST message to the E-USS/NB-SS including eDRX parameters:
c) The E-USS/NB-SS sends the ATTACH ACCEPT message where the eDRX parameters are not present. If ATTACH REQUEST in step b) above also contains T3324, the ATTACH ACCEPT message shall contain T3324 set to "deactivated". If ATTACH REQUEST in step b) does not contain T3324, the ATTACH ACCEPT message shall not contain T3324.
d) After receipt of the AttachComplete during registration from the UE, the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB, to the UE.
e) E-USS/NB-SS transmits Paging/Paging-NB to the UE in a valid paging occasion as per normal DRX
f) After receipt of RRCConnectionRequest/RRCConnectionRequest-NB message from the UE, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB message to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete–NB sent by the UE to the E-USS/NB-SS.
g) The terminal sends Service Request, the E-USS/NB-SS sends SERVICE ACCEPT followed by RRCConnectionRelease/RRCConnectionRelease-NB to the UE
h) The UE is switched off.
14.2.5 Acceptance criteria
1) After step d) the UE shall not deactivate the UICC.
14.3 UICC interface during eDRX for E-UTRAN – UICC deactivation during eDRX
14.3.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.
In this case, the UE shall re-activate the UICC, re-initialize the USIM and take appropriate steps to verify that the same USIM is used, before the end of the extended idle mode DRX cycle or before any other transmission to the network
14.3.2 Conformance requirement
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.
In this case, the UE shall re-activate the UICC (as specified in clause 6A.1 of 3GPP TS 31.101 [39]), re-initialize the USIM (as specified in clause 5.1.1 from [4]) and take appropriate steps to verify that the same USIM is used, before the end of the extended idle mode DRX cycle or before any other transmission to the network.
Verification shall include at least the check of the content of the following EFs: EFICCID, EFIMSI and EFLOCI, and/or EFPSLOCI and/or EFEPSLOCI (depending on which of these specific EFs containing LOCI the ME used prior to entering PSM).
Reference:
– 3GPP TS 31.102 [4], clause 5.1.11;
– TS 24.301 [26], clauses 5.3.12.
– TS 23.401 [37], clause 5.13a
– 3GPP TS 31.101 [39] in clause 6A.1.
14.3.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.
2) To verifies that UE when it leaves the PSM performs the following steps:
– re-activates the UICC.
– re-initializes the USIM
– verifies the following EFs: EFICCID, EFIMSI and EFEPSLOCI.
14.3.4 Method of test
14.3.4.1 Initial conditions
The UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE 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 installed into the Terminal with following exception:
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: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
01 |
00 |
08 |
03 |
The PIN of the USIM is disabled.
14.3.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and transmits an ATTACH REQUEST message to the E-USS/NB-SS including eDRX parameters:
c) The E-USS/NB-SS sends the ATTACH ACCEPT message containing eDRX set to eDRX_V and PTW set to PTW_V. If ATTACH REQUEST in step b) above also contains T3324, the ATTACH ACCEPT message shall contain T3324 set to "deactivated". If ATTACH REQUEST in step b) does not contain T3324, the ATTACH ACCEPT message shall not contain T3324.
d) After receipt of the AttachComplete during registration from the UE, the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB, to the UE.
e) The E-USS/NB-SS transmits Paging/Paging-NB to the UE using the S-TMSI in a valid paging occasion within the PTW of the paging Hyperframes as per Idle eDRX.
f) After receipt of a RRCConnectionRequest/RRCConnectionRequest-NB message from the UE, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB message to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete–NB sent by the UE to the E-USS/NB-SS.
g) The terminal sends Service Request, the E-USS/NB-SS sends SERVICE ACCEPT followed by RRCConnectionRelease/RRCConnectionRelease-NB to the UE.
h) The UE is switched off.
14.3.5 Acceptance criteria
1) After step d) the UE the UE deactivates the UICC.
2) After step e) the UE shall re-activate the UICC, re-initialize the USIM and verify the following EFs: EFICCID, EFIMSI and EFEPSLOCI
14.4 UICC interface during eDRX for E-UTRAN– SUSPEND UICC
14.4.1 Definition and applicability
In order to reduce power consumption when the UE uses extended idle mode DRX cycle, as defined in 3GPP TS 24.301 [26], in case the UICC supports the UICC suspension mechanism (SUSPEND UICC command), the ME may suspend the UICC during the extended idle mode DRX cycle. In this case, the ME shall resume the UICC successfully before the end of the extended idle mode DRX cycle or before any other transmission to the network.
14.4.2 Conformance requirement
In case the UICC supports the UICC suspension mechanism (SUSPEND UICC command), the ME may suspend the UICC during the extended idle mode DRX cycle. In this case, the ME shall resume the UICC successfully before the end of the extended idle mode DRX cycle or before any other transmission to the network.
Reference:
– 3GPP TS 31.102 [4], clause 5.1.11;
– TS 24.301 [26], clauses 5.3.12.
– TS 23.401 [37], clause 5.13a.
– 3GPP TS 31.101 [39] in clauses 6A.1 and 11.1.22.
14.4.3 Test purpose
1) To verify that UE does not send SUSPEND UICC command to the UICC in case the UICC does not indicates the support of SUSPEND UICC command in EFUMPC during the extended idle mode DRX cycle
2) To verify that UE sends SUSPEND UICC command to the UICC in case the UICC indicates the support of SUSPEND UICC command in EFUMPC during the extended idle mode DRX cycle.
3) To verify that UE resumes the UICC before the end of the extended idle mode DRX cycle or before any other transmission to the network.
14.4.4 Method of test
14.4.4.1 Initial conditions
The UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE 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 supports the UICC suspension procedure
Byte 4 and byte 5: RFU
|
Byte: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Coding: |
3C |
05 |
02 |
00 |
00 |
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: |
B1 |
B2 |
B3 |
B4 |
|
Hex |
01 |
00 |
08 |
03 |
The PIN of the USIM is enabled and verified.
14.4.4.2 Procedure
a) The UE is switched on.
b) The UE requests RRC Connection and transmits an ATTACH REQUEST message to the E-USS/NB-SS including eDRX parameters:
c) The E-USS/NB-SS sends the ATTACH ACCEPT message containing eDRX set to eDRX_V and PTW set to PTW_V. If ATTACH REQUEST in step b) above also contains T3324, the ATTACH ACCEPT message shall contain T3324 set to "deactivated". If ATTACH REQUEST in step b) does not contain T3324, the ATTACH ACCEPT message shall not contain T3324.
d) After receipt of the AttachComplete during registration from the UE, the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB, to the UE.
e) The UE sends SUSPEND UICC command to the UICC indicating "Minimum duration of the suspension proposed by the terminal" and the "Maximum duration of the suspension proposed by the terminal".
f) The UICC returns Maximum duration of the "suspension negotiated by the UICC" = "Minimum duration of the suspension proposed by the terminal", Resume token and SW 9000.
g) The E-USS/NB-SS transmits Paging/Paging-NB to the UE using the S-TMSI in a valid paging occasion within the PTW of the paging Hyperframes as per Idle eDRX.
h) After receipt of RRCConnectionRequest/RRCConnectionRequest-NB message from the UE, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB message to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete–NB sent by the UE to the E-USS/NB-SS.
i) The terminal sends Service Request, the E-USS/NB-SS sends SERVICE ACCEPT followed by RRCConnectionRelease/RRCConnectionRelease-NB to the UE.
j) The UE is switched off.
14.4.5 Acceptance criteria
1) After step f) the UE deactivates the UICC as specified in 3GPP TS 31.101 [39].
2) After step g) the UE resumes the UICC.