7.4 Higher priority PLMN search handling
31.1213GPPRelease 16TSUICC-terminal interfaceUniversal Subscriber Identity Module (USIM) application test specification
7.4.1 UE recognising the search period of the Higher priority PLMN
7.4.1.1 Definition and applicability
The Higher priority PLMN list gives in priority order the Higher priority PLMN on which the UE shall register first. The Higher priority PLMN search period gives the time interval in which the UE shall search for a possible Higher priority PLMN registration.
The registration attempts initiated by the terminal accessing UTRAN depends on terminal’s capabilities and can be one of the following:
I. registration procedures for Ues supporting CS or
II. registration procedures for Ues supporting PS or
III. registration procedures for Ues supporting CS/PS
7.4.1.2 Conformance requirement
After registered onto a VPLMN the UE shall take into account the Higher priority PLMN search period timer and the priority order of the Higher priority PLMNs in the preferred list on the USIM.
– TS 22.011 [6], clauses 3.2.2 and 3.2.2.5.
– TS 24.008 [16], clause 4.7.5
7.4.1.3 Test purpose
To verify that the Higher priority PLMN timer is read and the Higher priority PLMN takes precedence over the VPLMN in which the UE is currently registered in.
7.4.1.4 Method of test
7.4.1.4.1 Initial conditions
For this test an UTRAN USS (in case of a Terminal accessing UTRAN) or a SS (in case of Terminal accessing a GERAN) is needed.
The USS (in case of a Terminal accessing UTRAN)/SS (in case of Terminal accessing a GERAN) transmits on BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/082/0001.
– RAI (MCC/MNC/LAC/RAC): 244/082/0001/05 (only for UTRAN cell).
– Access control: unrestricted.
After the registration of UE the USS (in case of a Terminal accessing UTRAN) or a SS (in case of Terminal accessing a GERAN) transmits on a second BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/081/0001.
– RAI (MCC/MNC/LAC/RAC): 244/081/0001/05. (only for UTRAN cell)
– Access control: unrestricted.
NOTE: In case of a GERAN no packet system information is transmitted
The default UICC shall be used with the following exception:
EFHPPLMN (Higher Priority PLMN Search period)
Logically: set to 6 minutes
|
Coding: |
B1 |
|
Hex |
01 |
The UICC shall be installed into the Terminal and the UE shall be set to automatic PLMN selection mode.
In case of a Terminal accessing UTRAN "Expected Sequence A" and in case of a Terminal accessing a GERAN "Expected Sequence B" shall be performed.
7.4.1.4.2 Procedure
Expected sequence A:
a) The UE shall be powered on.
b) After receipt of a RRC CONNECTION REQUEST from the UE, the USS shall send RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
c) Depending on which domain the UE is going to be registered on, one of the following sequences will be passed through:
I. During registration on CS and after receipt of a LOCATION UPDATING REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends LOCATION UPDATING ACCEPT to the UE with the following values:
LAI (MCC/MNC/LAC): 244/082/0001
TMSI: "34567890"
II. During registration on PS and after receipt of a ATTACH REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends ATTACH ACCEPT with the following values to the UE:
RAI (MCC/MNC/LAC/RAC): 244/082/0001/05
P-TMSI: "34567890"
P-TMSI signature value: "AB1234"
III. During registration on CS/PS and after receipt of a LOCATION UPDATING REQUEST and/or ATTACH REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT with some of the following values to the UE:
LAI (MCC/MNC/LAC): 244/082/0001
TMSI: "34567890"
RAI (MCC/MNC/LAC/RAC) 244/082/0001/05
P-TMSI "34567890"
P-TMSI signature value "AB1234"
d) Depending on which domain the UE is going to be registered on, one of the following sequences will be passed through:
I. After receipt of a TMSI REALLOCATION COMPLETE from the UE during registration on CS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
II. After receipt of a ATTACH COMPLETE from the UE during registration on PS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS or.
III. After receipt of a TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE from the UE during registration on CS/PS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
e) The USS starts to send on the second BCCH with the MCC/MNC 244/081. An internal timer shall start to run.
f) After receipt on the cell related to the BCCH transmitting MCC/MNC 244/081 of a RRC CONNECTION REQUEST from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS. The internal timer is stopped.
g) Depending on which domain the UE is going to be registered on, one of the following sequences will be passed through:
I. During registration on CS and after receipt of a LOCATION UPDATING REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends LOCATION UPDATING ACCEPT to the UE with following values:
LAI (MCC/MNC/LAC): 244/081/0001
TMSI: "12345678"
II. During registration on PS and after receipt of a ROUTING AREA UPDATE REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends ROUTING AREA UPDATE ACCEPT with the following values to the UE:
RAI (MCC/MNC/LAC/RAC): 244/081/0001/05
P-TMSI "12345678"
P-TMSI signature value "AB1234"
III. During registration on CS/PS and after receipt of a LOCATION UPDATING REQUEST and/or ROUTING AREA UPDATE REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends LOCATION UPDATING ACCEPT and/or ROUTING AREA UPDATE ACCEPT with some of the following values to the UE:
LAI (MCC/MNC/LAC): 244/081/0001
TMSI: "12345678"
RAI (MCC/MNC/LAC/RAC) 244/081/0001/05
P-TMSI "12345678"
P-TMSI signature value "AB1234"
h) Depending on which domain the UE is going to be registered on, one of the following sequences will be passed through:
I. After receipt of a TMSI REALLOCATION COMPLETE from the UE during registration on CS, the USS sends RRC CONNECTION RELEASE to the UE followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS or
II. After receipt of a ROUTING AREA UPDATE COMPLETE from the UE during registration on PS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS or.
III. After receipt of a TMSI REALLOCATION COMPLETE and/or ROUTING AREA UPDATE COMPLETE from the UE during registration on CS/PS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
i) The UE is soft powered down.
Expected sequence B:
a) The UE shall be powered on.
b) After receipt of a CHANNEL REQUEST from the UE, the SS shall send IMMEDIATE ASSIGNMENT to the UE.
c) After receipt of a LOCATION UPDATING REQUEST from the UE, the SS sends LOCATION UPDATING ACCEPT with:
LAI (MCC/MNC/LAC): 244/082/0001
TMSI: "34567890"
to the UE.
d) After receipt of a TMSI REALLOCATION COMPLETE from the UE, the SS sends CHANNEL RELEASE to the UE.
e) The SS starts to send on the second BCCH with the MCC/MNC 244/081. An internal timer shall start to run.
f) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE. The internal timer is stopped.
g) After receipt of a LOCATION UPDATING REQUEST from the UE, the SS sends LOCATION UPDATING ACCEPT with:
LAI (MCC/MNC/LAC): 244/081/0001
TMSI: "12345678"
to the UE.
h) After receipt of a TMSI REALLOCATION COMPLETE from the UE, the SS sends CHANNEL RELEASE to the UE.
i) The UE is soft powered down.
7.4.1.5 Acceptance criteria
1) After step e) the UE accessing a GERAN shall send CHANNEL REQUEST on the cell related to the BCCH transmittingMCC/MNC 244/081 to the SS and the UE accessing UTRAN shall send an RRC CONNECTION REQUEST on the cell related to the BCCH transmitting MCC/MNC 244/081 to the USS
2) After.step e) the UE accessing a GERAN shall send LOCATION UPDATING REQUEST to the SS and the UE accessing UTRAN shall send
I. LOCATION UPDATING REQUEST to the USS during registration on CS or
II. ROUTING AREA UPDATE REQUEST during registration on PS or
III. LOCATION UPDATING REQUEST and/or ROUTING AREA UPDATE REQUEST to the USS during registration on CS/PS.
3) After step g) the UE accessing a GERAN shall respond with TMSI REALLOCATION COMPLETE and the UE accessing UTRAN shall respond with
I. TMSI REALLOCATION COMPLETE to the USS during registration on CS or
II. ROUTING AREA UPDATE COMPLETE during registration on PS or
III. TMSI REALLOCATION COMPLETE and/or ROUTING AREA UPDATE COMPLETE to the USS during registration on CS/PS.
4) The value of the internal timer shall not exceed 6 minutes.
NOTE: To take the systems processing time into account, the value of the internal timer may allowed to be a guard time of 10 % greater than the required 6 minutes.
5) After step i) the USIM shall contain the following values:
For UEs accessing GERAN and UEs accessing UTRAN and supporting (CS and PS) or (CS only):
EFLOCI (Location Information)
Logically: LAI-MCC: 244
LAI-MNC: 081
TMSI: "12345678"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
12 |
34 |
56 |
78 |
42 |
14 |
80 |
xx |
xx |
xx |
00 |
For UEs supporting (CS and PS) or (PS only):
EFPSLOCI (Location Information)
Logically: RAI-MCC: 244
RAI-MNC: 081
P-TMSI: "12345678"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
12 |
34 |
56 |
78 |
xx |
xx |
xx |
42 |
14 |
80 |
xx |
|
Coding: |
B12 |
B13 |
B14 |
||||||||
|
Hex |
xx |
xx |
00 |
7.4.2 GSM/UmTS dual mode UEs recognising the search period of the Higher priority PLMN
7.4.2.1 Definition and applicability
The Higher priority PLMN handling is defined in TS 22.011 [6] . The Higher priority PLMN search period gives the time interval between searches for a higher priority PLMN.
The registration attempts initiated by the uE depends on UEs capabilities and can be one of the following:
I. registration procedures for UEs supporting CS or
II. registration procedures for UEs supporting PS or
III. registration procedures for UEs supporting CS/PS
To avoid a duplication of tests, this test supersedes the previous test case (7.4.1).
7.4.2.2 Conformance requirement
After registered onto a VPLMN the UE shall take into account the Higher priority PLMN search period timer and the priority order of the Higher priority PLMNs in the preferred lists on the USIM including the Access Technology Identifier.
– TS 22.011 [6], clauses 3.2.2 and 3.2.2.5.
7.4.2.3 Test purpose
To verify that the Higher priority PLMN timer is read and the Higher priority PLMN with the higher priority (defined according to the selection order in TS 22.011 [6]) takes precedence over the VPLMN in which the UE is currently registered in.
7.4.2.4 Method of test
7.4.2.4.1 Initial conditions
For this test both a GSM SS and an UTRAN USS are needed.
The GSM SS transmits on BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/082/0001.
– Access control: unrestricted.
After the registration of UE the GSM SS transmits on a second BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/081/0001.
– Access control: unrestricted.
At the same time as the SS sends on a second BCCH, the UMTS USS transmits on BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/081/0001.
– RAI (MCC/MNC/LAC/RAC): 244/081/0001/05.
– Access control: unrestricted.
The default UICC is used with the following exception:
EFHPLMNwACT (HPLMN selector with Access Technology)
Logically: Set to MCC 244 and MNC 081
Set to UTRAN
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Hex |
42 |
14 |
80 |
80 |
00 |
EFHPPLMN (Higher Priority HPLMN Search period)
Logically: set to 6 minutes
|
Coding: |
B1 |
|
Hex |
01 |
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
HPLMN selector with access technology available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
|
binary |
xx1x xx11 |
xxxx xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
xxxx x1xx |
The UICC is installed into the Terminal and the UE is set to automatic PLMN selection mode.
7.4.2.4.2 Procedure
a) The UE is powered on.
b) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
c) After receipt of a LOCATION UPDATING REQUEST from the UE, the SS sends LOCATION UPDATING ACCEPT with:
LAI (MCC/MNC/LAC): 244/082/0001
TMSI: "34567890"
to the UE.
d) After receipt of a TMSI REALLOCATION COMPLETE from the UE, the SS sends CHANNEL RELEASE to the UE.
e) The SS starts to send on the second BCCH with the MCC/MNC 244/081 and the USS starts to send with the Same MCC/MNC. An internal timer shall start to run.
f) After receipt of a RRC CONNECTION REQUEST on the UTRAN-cell related to the BCCH transmitting MCC/MNC 244/081 from the UE, the USS sends RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS. The internal timer is stopped.
g) Depending on which domain the UE is going to be registered on, one of the following sequences will be passed through:
I. During registration on CS and after receipt of a LOCATION UPDATING REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends LOCATION UPDATING ACCEPT with the following values to the UE:
LAI (MCC/MNC/LAC): 244/081/0001
TMSI: "12345678"
II. During registration on PS and after receipt of a ATTACH REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends ATTACH ACCEPT with the following values to the UE:
RAI (MCC/MNC/LAC/RAC) 244/081/0001/05
P-TMSI "12345678"
P-TMSI signature value "AB1234"
III. During registration on CS/PS and after receipt of a LOCATION UPDATING REQUEST and/or ATTACH REQUEST from the UE, the USS initiates authentication, starts integrity by using the security procedure and sends LOCATION UPDATING ACCEPT and/or ATTACH ACCEPT with some of the following values to the UE:
LAI (MCC/MNC/LAC): 244/081/0001
TMSI: "12345678"
RAI (MCC/MNC/LAC/RAC) 244/081/0001/05
P-TMSI "12345678"
P-TMSI signature value "AB1234"
h) Depending on which domain the UE is going to be registered on, one of the following sequences will be passed through:
I. After receipt of a TMSI REALLOCATION COMPLETE from the UE during registration on CS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS or
II. After receipt of a ATTACH COMPLETE from the UE during registration on PS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS or.
III. After receipt of a TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE from the UE during registration on CS/PS, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
i) The UE is soft powered down.
7.4.2.5 Acceptance criteria
1) After step e) the UE shall send an RRC CONNECTION REQUEST on the UTRAN-cell related to the BCCH transmitting MCC/MNC 244/081 to the USS.
2) After step e) the UE shall send
I. LOCATION UPDATING REQUEST to the USS during registration on CS or
II. ATTACH REQUEST during registration on PS or
III. LOCATION UPDATING REQUEST and/or ATTACH REQUEST to the USS during registration on CS/PS.
3) After step g) the UE shall respond with
I. TMSI REALLOCATION COMPLETE during registration on CS or
II. ATTACH COMPLETE during registration on PS or
III. TMSI REALLOCATION COMPLETE and/or ATTACH COMPLETE to the USS during registration on CS/PS.
4) The value of the internal timer shall not exceed 6 minutes.
NOTE: To take the systems processing time into account, the value of the internal timer may allowed to be a guard time of 10 % greater than the required 6 minutes.
5) After step i) the USIM shall contain the following values:
For UEs supporting (CS and PS) or (CS only):
EFLOCI (Location Information)
Logically: LAI-MCC: 244
LAI-MNC: 081
TMSI: "12345678"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
12 |
34 |
56 |
78 |
42 |
14 |
80 |
xx |
xx |
xx |
00 |
For UEs supporting (CS and PS) or (PS only):
EFPSLOCI (Location Information)
Logically: RAI-MCC: 244
RAI-MNC: 081
P-TMSI: "12345678"
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
12 |
34 |
56 |
78 |
xx |
xx |
xx |
42 |
14 |
80 |
xx |
|
Coding: |
B12 |
B13 |
B14 |
||||||||
|
Hex |
xx |
xx |
00 |
7.4.3 UE recognising the search period of the Higher priority PLMN – E-UTRAN
7.4.3.1 Definition and applicability
The Higher priority PLMN list gives in priority order the Higher priority PLMN on which the UE shall register first. The Higher priority PLMN search period gives the time interval in which the UE shall search for a possible Higher priority PLMN registration.
7.4.3.2 Conformance requirement
After registered onto a VPLMN the UE shall take into account the Higher priority PLMN search period timer and the priority order of the Higher priority PLMNs in the preferred lists on the USIM.
– TS 22.011 [6], clauses 3.2.2 and 3.2.2.5.
– TS 24.301 [26], clause 5.5.3.2
– TS 31.102 [4], clause 4.2.6.
7.4.3.3 Test purpose
To verify that the Higher priority PLMN timer is read and the Higher priority PLMN takes precedence over the VPLMN in which the UE is currently registered in. Hereby the new coding for RAT E-UTRAN/NB-IoT has to be handled correctly by the UE.
7.4.3.4 Method of test
7.4.3.4.1 Initial conditions
For this test an E-USS/NB-IoT is required.
The E-USS transmits on BCCH with the following network parameters:
— TAI (MCC/MNC/TAC): 244/008/0001.
– Access control: unrestricted.
After the registration of UE the E-USS transmits on a second BCCH with the following network parameters:
– TAI (MCC/MNC/TAC): 244/083/0001.
— Access control: unrestricted.
The NB-SS transmits on BCCH with the following network parameters:
— TAI (MCC/MNC/TAC): 244/008/0001.
– Access control: unrestricted.
After the registration of UE the NB-SS transmits on a second BCCH with the following network parameters:
– TAI (MCC/MNC/TAC): 244/083/0001.
— Access control: unrestricted.
The default E-UTRAN UICC shall be used with the following exception:
EFHPPLMN (Higher Priority PLMN Search period)
Logically: For an MS that does not only support any of the following or a combination of NB-S1 mode or GERAN EC-GSM-IoT or Category M1 of E-UTRAN enhanced-MTC mode, T is 6 minutes. Otherwise T is 2 hours.
|
Coding: |
B1 |
|
Hex |
01 |
The UICC shall be installed into the Terminal and the UE shall be set to automatic PLMN selection mode.
7.4.3.4.2 Procedure
a) The UE is powered on.
b) After receipt of an RRCConnectionRequest/RRCConnectionRequest-NB from the UE on the E-UTRAN-cell/NB-IoT-cell related to the BCCH transmitting MCC/MNC 244/008, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB to the UE, followed by RRCConnectionSetupComplete/ RRCConnectionSetupComplete-NB sent by the UE to the E-USS/NB-SS.
c) During registration and after receipt of a AttachRequest from the UE, the E-USS/NB-SS initiates authentication, starts integrity by using the security procedure and sends AttachAccept with to the UE:
TAI (MCC/MNC/TAC): 244/008/ 0001
GUTI: "24400800010266436587"
d) After receipt of the AttachComplete during registration from the UE, the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB.
e) The E-USS/NB-SS starts to send on the second BCCH with the MCC/MNC 244/083. An internal timer shall start to run.
f) After receipt of an RRCConnectionRequest/RRCConnectionRequest-NB from the UE on the E-UTRAN-cell/NB-IoT-cell related to the BCCH transmitting MCC/MNC 244/083, the E-USS/NB-SS sends RRCConnectionSetup/RRCConnectionSetup-NB to the UE, followed by RRCConnectionSetupComplete/RRCConnectionSetupComplete-NB sent by the UE to the E-USS/NB-SS.
g) During registration and after receipt of a TrackingAreaUpdateRequest from the UE, the E-USS/NB-SS initiates authentication, starts integrity by using the security procedure and sends TrackingAreaUpdateAccept with to the UE:
TAI (MCC/MNC/TAC): 244/083/ 0001
GUTI: "24408300010266436587"
h) After receipt of the TrackingAreaUpdatComplete during registration from the UE, the E-USS/NB-SS sends RRCConnectionRelease/RRCConnectionRelease-NB.
i) The UE is soft powered down.
7.4.3.5 Acceptance criteria
1.) After step e) the UE shall send a RRCConnectionRequest/RRCConnectionRequest-NB on the E-UTRAN-cell/NB-IoT-cell related to the BCCH transmitting MCC/MNC 244/083 to the E-USS/NB-SS.
2) After step f) the terminal shall send TrackingAreaUpdateReques to the E-USS/NB-SS.
3) After step g) the terminal shall respond with TrackingAreaUpdatComplete during registration.
4) After step i) the USIM shall contain the following values:
EFEPSLOCI (EPS Information)
Logically: GUTI: 24408300010266436587
Last visited registered TAI: 244/083/0001
EPS update status: updated
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
0B |
F6 |
42 |
34 |
80 |
00 |
01 |
02 |
66 |
43 |
65 |
|
B12 |
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||
|
87 |
42 |
34 |
80 |
00 |
01 |
00 |
7.4.4 E-UTRAn/EPC capable UEs recognising the search period of the Higher priority PLMN – GSM/E-UTRAN
7.4.4.1 Definition and applicability
The Higher priority PLMN handling is defined in TS 22.011 [6]. The Higher priority PLMN search period gives the time interval between searches for a higher priority PLMN.
To avoid a duplication of tests, this test supersedes the previous test case (7.4.3).
7.4.4.2 Conformance requirement
After registered onto a VPLMN the UE shall take into account the Higher priority PLMN search period timer and the priority order of the Higher priority PLMNs in the preferred lists on the USIM including the Access Technology Identifier.
– TS 22.011 [6], clauses 3.2.2 and 3.2.2.5.
7.4.4.3 Test purpose
To verify that the Higher priority PLMN timer is read and the Higher priority PLMN with the higher priority (defined according to the selection order in TS 22.011 [6]) takes precedence over the VPLMN in which the UE is currently registered in. Hereby the new coding for RAT E-UTRAN has to be handled correctly by the UE.
7.4.4.4 Method of test
7.4.4.4.1 Initial conditions
For this test both a GSM SS and an E-UTRAN E-USS are needed.
The GSM SS transmits on BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/082/0001.
– RAI (MCC/MNC/LAC/RAC): 244/082/0001/05.
– Access control: unrestricted.
After the registration of UE the GSM SS transmits on a second BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/081/0001.
– RAI (MCC/MNC/LAC/RAC): 244/081/0001/05.
– Access control: unrestricted.
At the same time as the SS sends on a second BCCH, the E- USS transmits on BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 244/081/0001.
— Access control: unrestricted.
The default E-UTRAN UICC is used with the following exception:
EFHPLMNwACT (HPLMN selector with Access Technology)
Logically: Set to MCC 244 and MNC 081
Set to
E-UTRAN
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Hex |
42 |
14 |
80 |
40 |
00 |
EFHPPLMN (Higher Priority HPLMN Search period)
Logically: set to 6minutes
|
Coding: |
B1 |
|
Hex |
01 |
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
HPLMN selector with access technology available
EPS Mobility Management Information available
Allowed CSG Lists and corresponding indications not available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Binary |
xx1x xx11 |
xxxx xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
xxxx x1xx |
xxxx xxxx |
xxxx xxxx |
|
B9 |
B10 |
B11 |
||||||
|
xxxx xxxx |
xxxx xxxx |
xx01 xxxx |
The UICC is installed into the Terminal, the UE is set to automatic PLMN selection mode and to auto GPRS attach..
7.4.4.4.2 Procedure
a) The UE is powered on.
b) After receipt of a CHANNEL REQUEST from the UE, the SS sends IMMEDIATE ASSIGNMENT to the UE.
c) After receipt of an ATTACH REQUEST from the UE, the SS sends ATTACH ACCEPT with:
RAI (MCC/MNC/LAC/RAC): 244/082/0001/05
TMSI: "34567890"
to the UE.
d) After receipt of a ATTACH COMPLETE from the UE, the SS sends CHANNEL RELEASE to the UE.
e) The SS starts to send on the second BCCH with the MCC/MNC 244/081 and the E-USS starts to send with the Same MCC/MNC. An internal timer shall start to run.
f) After receipt of an RRCConnectionRequest from the UE on the E-UTRAN-cell related to the BCCH transmitting MCC/MNC 244/081, the E-USS sends RRCConnectionSetup to the UE, followed by RRCConnectionSetupComplete sent by the UE to the E-USS.
g) During registration and after receipt of a TrackingAreaUpdateRequest from the UE, the E-USS initiates authentication, starts integrity by using the security procedure and sends TrackingAreaUpdateAccept with to the UE:
TAI (MCC/MNC/TAC): 244/081/ 0001
GUTI: "24408100010266436587"
h) After receipt of the TrackingAreaUpdatComplete during registration from the UE, the E-USS sends RRCConnectionRelease.
i) The UE is soft powered down.
7.4.4.5 Acceptance criteria
1.) After step e) the UE shall send a RRCConnectionRequest on the E-UTRAN-cell related to the BCCH transmitting MCC/MNC 244/081 to the e-USS.
2) After step f) the terminal shall send TrackingAreaUpdateReques to the E-USS.
3) After step g) the terminal shall respond with TrackingAreaUpdatComplete during registration.
4) After step i) the USIM shall contain the following values:
EFEPSLOCI (EPS Information)
Logically: GUTI: 24408100010266436587
Last visited registered TAI: 244/081/0001
EPS update status: updated
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
0B |
F6 |
42 |
14 |
80 |
00 |
01 |
02 |
66 |
43 |
65 |
|
B12 |
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||
|
87 |
42 |
14 |
80 |
00 |
01 |
00 |
7.4.5 E-UTRAn/EPC capable UEs recognising the search period of the Higher priority PLMN – UTRAN/E-UTRAN
7.4.5.1 Definition and applicability
The Higher priority PLMN list gives in priority order the Higher priority PLMN on which the UE shall register first. The Radio Access Technology identifier defines the Radio network in which the UE shall register. The list is stored on the USIM in the EFHPLMNwACT. The Higher priority PLMN search period gives the time interval in which the UE shall search for a possible Higher priority PLMN registration.
To avoid a duplication of tests, this test supersedes test 7.4.x.
7.4.5.2 Conformance requirement
After registered onto a VPLMN the UE shall take into account the Higher priority PLMN search period timer and the priority order of the Higher priority PLMNs in the preferred list on the USIM including the Access Technology Identifier.
– TS 22.011 [6], clauses 3.2.2 and 3.2.2.5.
7.4.5.3 Test purpose
To verify that the Higher priority PLMN timer is read and the Higher priority PLMN with the higher priority (defined by its position in EFHPLMNwACT) takes precedence over the VPLMN in which the UE is currently registered in. Hereby the new coding for RAT E-UTRAN has to be handled correctly by the UE.
7.4.5.4 Method of test
7.4.5.4.1 Initial conditions
For this test both a UTRAN USS and an E-UTRAN E-USS are needed.
The USS transmits on BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/009/0001.
– RAI (MCC/MNC/LAC/RAC): 244/009/0001/05.
– Access control: unrestricted.
After the registration of UE the USS transmits on a second BCCH, with the following network parameters:
– Attach/detach: disabled.
– LAI (MCC/MNC/LAC): 244/081/0001.
– RAI (MCC/MNC/LAC/RAC): 244/081/0001/05.
– Access control: unrestricted.
At the same time as the SS sends on a second BCCH, the E- USS transmits on BCCH, with the following network parameters:
– TAI (MCC/MNC/TAC): 244/081/0001.
— Access control: unrestricted.
The default E-UTRAN UICC is used with the following exception:
EFHPLMNwACT (HPLMN selector with Access Technology)
Logically: Set to MCC 244 and MNC 081
Set to
E-UTRAN
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
|
Hex |
42 |
14 |
80 |
40 |
00 |
EFHPPLMN (Higher Priority HPLMN Search period)
Logically: set to 6minutes
|
Coding: |
B1 |
|
Hex |
01 |
EFUST (USIM Service Table)
Logically: Local Phone Book available
User controlled PLMN selector available
Fixed dialling numbers available
Barred dialling numbers available
The GSM Access available
The Group Identifier level 1 and level 2 not available
Service n 33 (Packed Switched Domain) shall be set to ‘1’
Enabled Services Table available
HPLMN selector with access technology available
EPS Mobility Management Information available
Allowed CSG Lists and corresponding indications not available
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
|
Binary |
xx1x xx11 |
xxxx xxxx |
xxxx 1×00 |
xxxx x1xx |
xxxx xx11 |
xxxx x1xx |
xxxx xxxx |
xxxx xxxx |
|
B9 |
B10 |
B11 |
||||||
|
xxxx xxxx |
xxxx xxxx |
xx01 xxxx |
The UICC is installed into the Terminal, the UE is set to automatic PLMN selection mode and to auto GPRS attach.
7.4.5.4.2 Procedure
a) The UE is powered on.
b) After receipt of a RRC CONNECTION REQUEST from the UE, the USS shall send RRC CONNECTION SETUP to the UE, followed by RRC CONNECTION SETUP COMPLETE sent by the UE to the USS.
c) After receipt of an ATTACH REQUEST from the UE, the SS sends ATTACH ACCEPT with:
RAI (MCC/MNC/LAC/RAC): 244/009/0001/05
TMSI: "34567890"
to the UE.
d) After receipt of a ATTACH COMPLETE from the UE, the USS sends RRC CONNECTION RELEASE to the UE, followed by RRC CONNECTION RELEASE COMPLETE sent by the UE to the USS.
e) TheUSS starts to send on the second BCCH with the MCC/MNC 244/081 and the E-USS starts to send with the Same MCC/MNC. An internal timer shall start to run.
f) After receipt of an RRCConnectionRequest from the UE on the E-UTRAN-cell related to the BCCH transmitting MCC/MNC 244/081, the E-USS sends RRCConnectionSetup to the UE, followed by RRCConnectionSetupComplete sent by the UE to the E-USS.
g) During registration and after receipt of a TrackingAreaUpdateRequest from the UE, the E-USS initiates authentication, starts integrity by using the security procedure and sends TrackingAreaUpdateAccept with to the UE:
TAI (MCC/MNC/TAC): 244/081/ 0001
GUTI: "24408100010266436587"
h) After receipt of the TrackingAreaUpdatComplete during registration from the UE, the E-USS sends RRCConnectionRelease.
i) The UE is soft powered down.
7.4.5.5 Acceptance criteria
1.) After step e) the UE shall send a RRCConnectionRequest on the E-UTRAN-cell related to the BCCH transmitting MCC/MNC 244/081 to the e-USS.
2) After step f) the terminal shall send TrackingAreaUpdateReques to the E-USS.
3) After step g) the terminal shall respond with TrackingAreaUpdatComplete during registration.
4) After step i) the USIM shall contain the following values:
EFEPSLOCI (EPS Information)
Logically: GUTI: 24408100010266436587
Last visited registered TAI: 244/081/0001
EPS update status: updated
|
Coding: |
B1 |
B2 |
B3 |
B4 |
B5 |
B6 |
B7 |
B8 |
B9 |
B10 |
B11 |
|
Hex |
0B |
F6 |
42 |
14 |
80 |
00 |
01 |
02 |
66 |
43 |
65 |
|
B12 |
B13 |
B14 |
B15 |
B16 |
B17 |
B18 |
|||||
|
87 |
42 |
14 |
80 |
00 |
01 |
00 |