22.2 Idle mode operations
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
22.2.1 NB-IoT / PLMN selection of RPLMN, HPLMN / EHPLMN, UPLMN and OPLMN / Automatic mode
22.2.1.1 Test Purpose (TP)
(1)
with { UE in Automatic network selection mode and RPLMN, HPLMN, UPLMN and OPLMN cells available and UE is fitted with a USIM indicating RPLMN should be selected }
ensure that {
when { UE is switched on or return to coverage }
then { UE selects a cell of the RPLMN and UE attempts Tracking area update on the selected cell and when successfully registered indicates the selected PLMN to the user }
}
(2)
with { UE camped on a VPLMN cell and cells of a higher priority PLMN available }
ensure that {
when { UE higher priority PLMN search timer T expires }
then { UE selects and camps on a cell of the highest priority PLMN and UE attempts Tracking area update on the selected cell and when successfully registered indicates the selected PLMN to the user }
}
(3)
with { UE in Automatic network selection mode and HPLMN, UPLMN and OPLMN cells available and UE is fitted with a USIM with Access Technology data files for each PLMN and there are no equivalent HPLMNs defined }
ensure that {
when { UE is switched on or return to coverage }
then { UE selects a cell of the highest priority PLMN and UE attempts Tracking area update on the selected cell and when successfully registered indicates the selected PLMN to the user }
}
(4)
with { UE camped on a VPLMN cell and cells of a HPLMN available }
ensure that {
when { UE higher priority PLMN search timer T expires }
then { UE selects and camps on a cell of HPLMN and UE attempts Tracking area update on the selected cell and when successfully registered indicates the selected PLMN to the user }
}
22.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1, 4.4.3.1.1 and 4.4.3.3. Unless otherwise stated these are Rel-13 requirements.
[TS 23.122, clause 4.4.3.1]
At switch on, or following recovery from lack of coverage, the MS selects the registered PLMN or equivalent PLMN (if it is available) using all access technologies that the MS is capable of and if necessary (in the case of recovery from lack of coverage, see clause 4.5.2) attempts to perform a Location Registration.
…
If successful registration is achieved, the MS indicates the selected PLMN.
If there is no registered PLMN, or if registration is not possible due to the PLMN being unavailable or registration failure, the MS follows one of the following two procedures depending on its PLMN selection operating mode. At switch on, if the MS provides the optional feature of user preferred PLMN selection operating mode at switch on then this operating mode shall be used.
…
NOTE 1: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and the MS does not store the previous registered PLMN for later use.
[TS 23.122, clause 4.4.3.1.1]
The MS selects and attempts registration on other PLMN/access technology combinations, if available and allowable, in the following order:
i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present) ;
ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
iv) …
v) …
When following the above procedure the following requirements apply:
a) …
b) …
c) In ii and iii, the MS should limit its search for the PLMN to the access technology or access technologies associated with the PLMN in the appropriate PLMN Selector with Access Technology list (User Controlled or Operator Controlled selector list). An MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead use the "PLMN Selector" data file, for each PLMN in the "PLMN Selector" data file, the MS shall search for all access technologies it is capable of and shall assume GSM access technology as the highest priority radio access technology.
d) …
e) …
f) In i, the MS shall search for all access technologies it is capable of. No priority is defined for the preferred access technology and the priority is an implementation issue, but "HPLMN Selector with Access Technology" data file on the SIM may be used to optimise the procedure.
g) …
h) …
NOTE 1: …
NOTE 2: …
NOTE 3: High quality signal is defined in the appropriate AS specification.
If successful registration is achieved, the MS indicates the selected PLMN.
[TS 23.122, clause 4.4.3.3]
If the MS is in a VPLMN, the MS shall periodically attempt to obtain service on its HPLMN (if the EHPLMN list is not present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a higher priority PLMN/access technology combinations listed in "user controlled PLMN selector" or "operator controlled PLMN selector" by scanning in accordance with the requirements that are applicable to i), ii) and iii) as defined in the Automatic Network Selection Mode in subclause 4.4.3.1.1. In the case that the mobile has a stored "Equivalent PLMNs" list the mobile shall only select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored in the "Equivalent PLMNs" list. For this purpose, a value of timer T may be stored in the SIM. The interpretation of the stored value depends on the modes supported by the MS:
– 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 (as defined in 3GPP TS 36.306 [13]): T is either in the range 6 minutes to 8 hours in 6 minute steps or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 60 minutes is used for T.
– For an MS that only supports 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 (as defined in 3GPP TS 36.306 [13]): T is either in the range 2 hours to 240 hours, using 2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used.
If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer.
The MS can be configured for Fast First Higher Priority PLMN search as specified in 3GPP TS 31.102 [40] or 3GPP TS 24.368 [50]. Fast First Higher Priority PLMN search is enabled if the corresponding configuration parameter is present and set to enabled. Otherwise, Fast First Higher Priority PLMN search is disabled.
The attempts to access the HPLMN or an EHPLMN or higher priority PLMN shall be as specified below:
a) The periodic attempts shall only be performed in automatic mode when the MS is roaming;
b) After switch on a period of at least 2 minutes and at most T minutes shall elapse before the first attempt is made;
c) The MS shall make the following attempts if the MS is on the VPLMN at time T after the last attempt;
d) Periodic attempts shall only be performed by the MS while in idle mode;
e) If the HPLMN (if the EHPLMN list is not present or is empty) or a EHPLMN (if the list is present) or a higher priority PLMN is not found, the MS shall remain on the VPLMN.
f) In steps i), ii) and iii) of subclause 4.4.3.1.1 the MS shall limit its attempts to access higher priority PLMN/access technology combinations to PLMN/access technology combinations of the same country as the current serving VPLMN, as defined in Annex B.
g) …
h) If the PLMN of the highest priority PLMN/access technology combination available is the current VPLMN, or one of the PLMNs in the "Equivalent PLMNs" list, the MS shall remain on the current PLMN/access technology combination.
22.2.1.3 Test description
22.2.1.3.1 Pre-test conditions
System Simulator:
– Four intra-frequency multi-PLMN Ncells as specified in TS 36.508 clause 8.1.4.1.2 are configured broadcasting PLMNs as indicated in Table 22.2.1.3.1-1.
– System information combination 2 as defined in TS 36.508 [18] clause 8.1.4.3.1 is used.
– The PLMNs are identified in the test by the identifiers in Table 22.2.1.3.1-1.
Table 22.2.1.3.1–1: PLMN identifiers
Ncell |
PLMN name |
MCC |
MNC |
1 |
PLMN4 |
001 |
01 |
2 |
PLMN1 |
001 |
11 |
4 |
PLMN2 |
001 |
21 |
11 |
PLMN3 |
001 |
31 |
UE:
– The UE is in Automatic PLMN selection mode.
– The UE is registered to PLMN1 before it is switched off.
– The UE is equipped with a USIM containing default values (as per TS 36.508) except for those listed in Table 22.2.1.3.1-2.
Table 22.2.1.3.1–2: USIM configuration
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN4. |
||
EFPLMNwAcT |
1 2 3 |
Default PLMN3 PLMN2 Remaining mandatory entries use default values |
Default All specified NB-IoT |
EFOPLMNwACT |
1 |
PLMN1 Remaining defined entries use default values |
All specified |
EFHPLMNwAcT |
1 |
PLMN4 |
NB-IoT |
EFUST |
Services 20, 42, 43 and 74 are supported. Service 71 is not supported (there is no EHPLMN list). |
||
EFHPPLMN |
1 (120 minutes) |
Preamble:
– The UE is made to camp on Ncell 2 and then Switched OFF (State 1-NB).
22.2.1.3.2 Test procedure sequence
Table 22.2.1.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions. Subsequent configurations marked “T1”,“T2” etc are applied at the points indicated in the Main behaviour description in Table 22.2.1.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 36.508.
Table 22.2.1.3.2-1: Ncell configuration changes over time
Parameter |
Unit |
Ncell 1 |
Ncell 2 |
Ncell 4 |
Ncell 11 |
Remarks |
|
T0 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
“Off” |
“Off” |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
T1 |
NRS EPRE |
dBm/15kHz |
-85 |
-79 |
-85 |
”Off” |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
T2 |
NRS EPRE |
dBm/15kHz |
-79 |
-85 |
-85 |
”Off” |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
T3 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
-79 |
“Off” |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
T4 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
-85 |
-79 |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
Table 22.2.1.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts Ncell levels according to row T1 of table 22.2.1.3.2-1 |
– |
– |
– |
– |
2 |
Power on the UE. |
– |
– |
– |
– |
3 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 2? |
–> |
RRCConnectionRequest-NB |
1 |
P |
4-15 |
Steps 3 to 14 of the registration procedure described in TS 36.508 subclause 8.1.5.2.3 are performed on Ncell 2. |
– |
– |
– |
– |
15A |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
<– |
RRCConnectionRelease-NB |
– |
– |
16 |
Check: Is PLMN1 indicated by the UE? |
– |
– |
1 |
P |
16A |
SS adjusts Ncell levels according to row T2 of table 22.2.1.3.2-1 |
– |
– |
– |
– |
17 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 1 after 120 seconds, but before 132 mins (Note 2) from power on? |
–> |
RRCConnectionRequest-NB |
4 |
P |
18-22 |
Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed on Ncell 1. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
23 |
Check: Is PLMN4 indicated by the UE? |
– |
– |
4 |
P |
24 |
SS adjusts Ncell levels according to row T3 of table 22.2.1.3.2-1 |
– |
– |
– |
– |
25 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 4? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
3 |
– |
26 |
SS adjusts Ncell levels according to row T4 of table 22.2.1.3.2-1 |
– |
– |
– |
– |
27 |
Check: Is PLMN2 indicated by the UE? |
– |
– |
3 |
P |
28 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 11 after 120 seconds, but before 132 mins after step 25? (Note 1 and 2) |
–> |
RRCConnectionRequest-NB |
2 |
P |
29-33 |
Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
34 |
Check: Is PLMN3 indicated by the UE? |
– |
– |
2 |
P |
Note 1: Following attempts to access the HPLMN/EHPLMN/higher priority PLMN in VPLMN is operator specific setting (Refer to TS 23.122 Rel-13). Hence, window between 120s to T+Tolerance is being used, where the high priority PLMN search timer T defined by EFHPPLMN Note 2: Tolerance of 12 min is added to allow time for the UE to find the proper PLMN |
22.2.1.3.3 Specific message contents
Table 22.2.1.3.3-1: SystemInformationBlockType3-NB for Ncells 2 and 4 (preamble and all steps, table 22.2.1.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.3-2 |
|||
Information Element |
Value/remark |
Comment |
|
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
|||
cellReselectionInfoCommon-r13 SEQUENCE { |
|||
q-Hyst-r13 |
dB24 |
||
} |
|||
} |
22.2.2 NB-IoT / PLMN selection of RPLMN, HPLMN / EHPLMN, UPLMN and OPLMN / Manual mode
22.2.2.1 Test Purpose (TP)
(1)
with { UE in Manual network selection mode and EHPLMN and HPLMN cells available and (E)RPLMN cell is not available and UE is fitted with a USIM containing the EHPLMN list and the UE supports the exception to manual mode selection mode }
ensure that {
when { UE is switched on }
then { UE selects a cell of the highest priority EHPLMN and when successfully registered indicates the selected PLMN to the user }
}
(2)
with { UE in Manual network selection mode and HPLMN and VPLMN cells available and (E)RPLMN cell is not available and UE is fitted with a USIM not containing or containing empty EHPLMN list and the UE supports the exception to manual mode selection mode }
ensure that {
when { UE is switched on }
then { UE selects a cell of the HPLMN and when successfully registered indicates the selected PLMN to the user }
}
(3)
with { UE in Manual network selection mode and camped normally on a cell and network has downloaded a list of equivalent PLMNs during the Attach procedure }
ensure that {
when { higher ranked cell is a cell of a PLMN in the downloaded equivalent PLMN list }
then { UE reselects to the equivalent PLMN cell. }
}
(4)
with { UE in Manual network selection mode and camped normally on a cell and network has downloaded a list of equivalent PLMNs during the Tracking Area Update procedure }
ensure that {
when { highest ranked cell is a cell of a PLMN not in the downloaded equivalent PLMN list }
then { UE does not reselect to the cell. }
}
22.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.1.2.2, TS 23.122 clauses 4.4.3.1 and 4.4.3.1.2.
[TS 36.304 clause 5.1.2.2]
The UE shall scan all RF channels in the E-UTRA bands according to its capabilities to find available PLMNs. On each carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN(s) the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN (see the PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value),
…
Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of that PLMN to camp on.
[TS 23.122, clause 1.2]
Equivalent HPLMN list: To allow provision for multiple HPLMN codes, PLMN codes that are present within this list shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on the USIM and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for PLMN selection purposes.
…
[TS 23.122 clause 4.4.3.1]
At switch on, or following recovery from lack of coverage, the MS selects the registered PLMN or equivalent PLMN (if it is available) using all access technologies that the MS is capable of and if necessary (in the case of recovery from lack of coverage, see subclause 4.5.2) attempts to perform a Location Registration.
…
EXCEPTION: At switch on, if the MS is in manual mode and neither registered PLMN nor PLMN that is equivalent to it is available but EHPLMN is available, then instead of performing the manual network selection mode procedure of subclause 4.4.3.1.2 the MS may select and attempt registration on the highest priority EHPLMN. If the EHPLMN list is not available or is empty and the HPLMN is available, then the MS may select and attempt registration on the HPLMN. The MS shall remain in manual mode.
NOTE 1: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and the MS does not store the previous registered PLMN for later use.
…
[TS 23.122 clause 4.4.3.1.2]
The MS indicates whether there are any PLMNs, which are available using all supported access technologies. This includes PLMNs in the "forbidden PLMNs" list, "forbidden PLMNs for GPRS service" list and PLMNs which only offer services not supported by the MS. An MS which supports GSM COMPACT shall also indicate GSM COMPACT PLMNs (which use PBCCH).
If displayed, PLMNs meeting the criteria above are presented in the following order:
i)- either the HPLMN (if the EHPLMN list is not present or is empty) or, if one or more of the EHPLMNs are available then based on an optional data field on the SIM either only the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order. If the data field is not present on the SIM, then only the highest priority available EHPLMN is presented;
ii)- PLMN/access technology combinations contained in the " User Controlled PLMN Selector with Access Technology " data file in the SIM (in priority order);
iii)- PLMN/access technology combinations contained in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
iv)- other PLMN/access technology combinations with received high quality signal in random order;
v)- other PLMN/access technology combinations in order of decreasing signal quality.
In ii and iii, an MS using a SIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present) shall instead present the PLMNs contained in the "PLMN Selector" data file in the SIM (in priority order).
In v, requirement h) in subclause 4.4.3.1.1 applies.
In i to v, requirements j), k) in subclause 4.4.3.1.1 apply.
In GSM COMPACT, the non support of voice services shall be indicated to the user.
The HPLMN may provide on the SIM additional information on the available PLMNs. If this information is provided then the MS shall indicate it to the user. This information, provided as free text may include:
– preferred partner,
– roaming agreement status,
– supported services
Furthermore, the MS may indicate whether the available PLMNs are present on the EHPLMN list, the Forbidden list, the User Controlled PLMN List or the Operator Controlled PLMN List. The MS may also indicate that the PLMN is not present on any of these lists.
The user may select his desired PLMN and the MS then initiates registration on this PLMN using the access technology chosen by the user for that PLMN or using the highest priority available access technology for that PLMN, if the associated access technologies have a priority order. (This may take place at any time during the presentation of PLMNs). For such a registration, the MS shall ignore the contents of the "forbidden location areas for roaming", "forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "forbidden PLMNs for GPRS service" and "forbidden PLMNs" lists.
NOTE 1: It is an MS implementation option whether to indicate access technologies to the user. If the MS does display access technologies, then the access technology selected by the user is only used for initial registration on the selected PLMN. If the MS does not display access technologies, then the access technology chosen for a particular PLMN should be the highest priority available access technology for that PLMN, if the associated access technologies have a priority order, and is only used for initial registration.
Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different PLMN unless:
i) the new PLMN is declared as an equivalent PLMN by the registered PLMN; or
ii) the user selects automatic mode.
If the user does not select a PLMN, the selected PLMN shall be the one that was selected before the PLMN selection procedure started. If no such PLMN was selected or that PLMN is no longer available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state.
NOTE 2: High quality signal is defined in the appropriate AS specification.
22.2.2.3 Test description
22.2.2.3.1 Pre-test conditions
System Simulator:
– Ncells 1, 3, 23 and 13, as specified in TS 36.508 clause 8.1.4.2 are configured as shown in Table 22.2.2.3.1-1.
– System information combination 3 as defined in TS 36.508 clause 8.1.4.3.1.1 is used.
Table 22.2.2.3.1-1: PLMN identifiers
Ncell |
PLMN names |
MCC |
MNC |
1 |
PLMN1 (during TC body); PLMN4 (during preamble) |
001; 004 |
01; 31 |
3 |
PLMN2 |
002 |
11 |
23 |
PLMN3 |
003 |
21 |
13 |
PLMN4 |
004 |
31 |
UE:
– The UE is in Manual PLMN selection mode.
– Two USIMs containing default values (as per TS 36.508) except for those listed in Table 22.2.2.3.1-2 and Table 22.2.2.3.1-3 will be used.
– The UE is registered to PLMN4 on Ncell 1 with USIM A.
Table 22.2.2.3.1-2: USIM A configuration
USIM field |
Priority |
Value |
Access Technology Identifier |
EFEPSLOCI |
PLMN4 (set in preamble) |
||
EFPLMNwAcT |
Empty |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFUST |
Service n°71 and n°74 are "available" |
||
EFEHPLMN |
1 2 |
PLMN2 PLMN1 |
Table 22.2.2.3.1-3: USIM B configuration
USIM field |
Priority |
Value |
Access Technology Identifier |
EFEPSLOCI |
PLMN4 |
||
EFPLMNwAcT |
Empty |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFUST |
Service n°74 is "available" |
||
EFEHPLMN |
Empty |
Preamble:
– The UE is in state Switched OFF (State 1-NB) according to TS 36.508.
22.2.2.3.2 Test procedure sequence
Table 22.2.2.3.21-1 shows the cell configurations used during the test. Subsequent configuration marked “T1”, “T2” etc. are applied at the points indicated in the Main behaviour description in Table 22.2.2.3.2-2.
Table 22.2.2.3.2-1: Cell configuration changes over time
Parameter |
Unit |
Ncell 1 |
Ncell 3 |
Ncell 23 |
Ncell 13 |
Remarks |
|
T1 |
RS EPRE |
dBm /15kHz |
-85 |
-85 |
“Off” |
“Off” |
|
T2 |
RS EPRE |
dBm /15kHz |
-97 |
“Off” |
-85 |
-73 |
|
T3 |
RS EPRE |
dBm /15kHz |
-85 |
“Off” |
-97 |
“Off” |
|
NOTE 1: The downlink signal level uncertainty is specified in TS 36.508 section 8.1.3.4.1 NOTE 2: Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1. |
Table 22.2.2.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS adjusts cell levels according to row T1 of table 22.2.2.3.2-1. |
– |
– |
– |
– |
2 |
Power on the UE with USIM A inserted. |
– |
– |
– |
– |
3 |
Check: Does the UE transmit an RRCConnectionRequest-NB on Ncell 3? |
–> |
RRCConnectionRequest-NB |
1 |
P |
4-16b1 |
Steps 2 to 14b1 of the generic test procedure in TS 36.508 subclause 8.1.5.2.3 are performed on Ncell 3. |
– |
– |
– |
– |
17 |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
<– |
RRC: RRCConnectionRelease-NB |
– |
– |
18 |
Check: Is PLMN 2 indicated by the UE? |
– |
– |
1 |
P |
19 |
If possible switch off is performed or the USIM is removed, otherwise the power is removed. |
– |
– |
– |
– |
– |
EXCEPTION: Steps 20a1 to 20a4 describe behaviour that depends on the UE capability. |
– |
– |
– |
– |
20a1-20a4 |
If pc_SwitchOnOff or pc_USIM_Removal then switch off procedure defined in TS 36.523-3 Table 10.5.2.1 Steps 2a1-2a4 is performed. |
– |
– |
– |
– |
21 |
The UE is brought back to operation with USIM B inserted. |
– |
– |
– |
– |
22 |
Check: Does the UE transmit an RRCConnectionRequest-NB on Ncell 1? |
–> |
RRCConnectionRequest-NB |
2 |
P |
23-35 |
Steps 2 to 14b1 of the generic test procedure in TS 36.508 subclause 8.1.5.2.3 are performed on Ncell 1. |
– |
– |
– |
– |
36 |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
<– |
RRC: RRCConnectionRelease-NB |
– |
– |
37 |
Check: Is PLMN 1 indicated by the UE? |
– |
– |
2 |
P |
38 |
The SS adjusts cell levels according to row T2 of table 22.2.2.3.2-1. |
– |
– |
– |
– |
39 |
Check: Does the UE transmit an RRCConnectionRequest-NB on Ncell 23? |
–> |
RRCConnectionRequest-NB |
3,4 |
P |
40-45 |
Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5-1 is performed on Ncell 23. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
46 |
Check: Is PLMN3 indicated by the UE? |
– |
– |
3,4 |
P |
47 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 1 or Ncell 13 within 120 seconds? |
– |
– |
4 |
F |
48 |
The SS adjusts cell levels according to row T3 of table 22.2.2.3.2-1. |
– |
– |
– |
– |
49 |
Set UE to Automatic PLMN selection mode. |
– |
– |
– |
– |
50 |
The generic test procedure in TS 36.508 subclause 8.1.5A.5-1 is performed on Ncell 1. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
22.2.2.3.3 Specific message contents
Table 22.2.2.3.3-1: SystemInformationBlockType5-NB for Ncell 1 (preamble and all steps, Table 22.2.2.3.2-2)
Derivation path: 36.508 Table 8.1.4.3.3-4 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
|||
interFreqCarrierFreqList-r13 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
dl-CarrierFreq-r13 [1] |
Same downlink EARFCN as used for Ncell 23 |
||
dl-CarrierFreq-r13 [2] |
Same downlink EARFCN as used for Ncell 13 |
||
} |
|||
} |
Table 22.2.2.3.3-2: SystemInformationBlockType5-NB for Ncell 23 (preamble and all steps, Table 22.2.2.3.2-2)
Derivation path: 36.508 Table 8.1.4.3.3-4 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
|||
interFreqCarrierFreqList-r13 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
|||
dl-CarrierFreq-r13 [1] |
Same downlink EARFCN as used for Ncell 1 |
||
dl-CarrierFreq-r13 [2] |
Same downlink EARFCN as used for Ncell 13 |
||
} |
|||
} |
Table 22.2.2.3.3-3: ATTACH ACCEPT for Ncell 1 (step 34a1/34b1/34c1, Table 22.2.2.3.2-2)
Derivation path: 36.508 Table 4.7.2-1 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Equivalent PLMNs |
PLMN3 |
Ncell 23 |
Table 22.2.2.3.3-4: TRACKING AREA UPDATE ACCEPT for Ncell 1 (step 43, Table 22.2.2.3.2-2)
Derivation path: 36.508 Table 4.7.2-24 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Equivalent PLMNs |
PLMN1 |
Ncell 1 |
22.2.3 NB-IoT / PLMN selection / Periodic reselection / MinimumPeriodicSearchTimer
22.2.3.1 Test Purpose (TP)
(1)
with { UE configured with “MinimumPeriodicSearchTimer“ and camped on an VPLMN cell and cells of a higher priority PLMN available }
ensure that {
when { the higher priority PLMN search timer T stored in the USIM or the default value for T is less than the MinimumPeriodicSearchTimer }
then { T shall be set to the MinimumPeriodicSearchTimer. After the first attempt to the higher priority PLMN cell is made, the UE shall not use a value for T that is less than the MinimumPeriodicSearchTimer. When the T expires the UE selects and camps on a cell of the highest priority PLMN and UE attempts a location registration on the selected cell and when successfully registered indicates the selected PLMN to the user }
}
22.2.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 4.4.3.1 and 4.4.3.3.1. Unless otherwise stated these are Rel-13 requirements.
[TS 23.122, clause 4.4.3.1]
At switch on, or following recovery from lack of coverage, the MS selects the registered PLMN or equivalent PLMN (if
it is available) using all access technologies that the MS is capable of and if necessary (in the case of recovery from lack
of coverage, see subclause 4.5.2) attempts to perform a Location Registration.
…
If there is no registered PLMN, or if registration is not possible due to the PLMN being unavailable or registration
failure, the MS follows one of the following two procedures depending on its PLMN selection operating mode. At
switch on, if the MS provides the optional feature of user preferred PLMN selection operating mode at switch on then
this operating mode shall be used. Otherwise, the MS shall use the PLMN selection mode that was used before
switching off.
…
NOTE 1: If successful registration is achieved, then the current serving PLMN becomes the registered PLMN and
the MS does not store the previous registered PLMN for later use.
[TS 23.122, clause 4.4.3.3.1]
If the MS is in a VPLMN, the MS shall periodically attempt to obtain service on its HPLMN (if the EHPLMN list is not present or is empty) or one of its EHPLMNs (if the EHPLMN list is present) or a higher priority PLMN/access
technology combinations listed in "user controlled PLMN selector" or "operator controlled PLMN selector" by scanning in accordance with the requirements that are applicable to i), ii) and iii) as defined in the Automatic Network Selection Mode in subclause 4.4.3.1.1. In the case that the mobile has a stored "Equivalent PLMNs" list the mobile shall only select a PLMN if it is of a higher priority than those of the same country as the current serving PLMN which are stored in the "Equivalent PLMNs" list. For this purpose, a value of timer T may be stored in the SIM. The interpretation of the stored value depends on the radio capabilities supported by the MS:
For an MS that does not only support any of the following or a combination of EC-GSM-IoT or Category M1 or Category NB1(as defined in 3GPP TS 36.306 [54]): T is either in the range 6 minutes to 8 hours in 6 minute steps or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 60 minutes is used for T.
For an MS that only supports any of the following or a combination of EC-GSM-IoT or Category M1 or Category NB1(as defined in 3GPP TS 36.306 [54]): T is either in the range 2 hours to 240 hours, using 2 hour steps from 2 hours to 80 hours and 4 hour steps from 84 hours to 240 hours, or it indicates that no periodic attempts shall be made. If no value for T is stored in the SIM, a default value of 72 hours is used.
If the MS is configured with the MinimumPeriodicSearchTimer as specified in 3GPP TS 24.368 [50] or 3GPP TS 31.102 [40], the MS shall not use a value for T that is less than the MinimumPeriodicSearchTimer. If the value stored in the SIM, or the default value for T (when no value is stored in the SIM), is less than the MinimumPeriodicSearchTimer, then T shall be set to the MinimumPeriodicSearchTimer
22.2.3.3 Test description
22.2.3.3.1 Pre-test conditions
System Simulator:
– Three multi-PLMN cells as specified in TS 36.508 clause 8.4.1.2 are configured broadcasting PLMNs as indicated in Table 22.2.3.3.1-1.
– System information combination 3 as defined in TS 36.508 [18] clause 8.1.4.3.1 is used.
– The PLMNs are identified in the test by the identifiers in Table 22.2.3.3.1-1.
Table 22.2.3.3.1–1: PLMN identifiers
Ncell |
PLMN name |
MCC |
MNC |
1 |
PLMN4 |
001 |
01 |
12 |
PLMN1 |
001 |
11 |
13 |
PLMN2 |
001 |
21 |
UE:
– The UE is in Automatic PLMN selection mode.
– The UE is registered to PLMN1 before it is switched off.
– The UE is configured with a value of MinimumPeriodicSearchTimer set to 120 minutes
– The UE is equipped with a USIM containing default values (as per TS 36.508) except for those listed in Table 22.2.3.3.1-2.
Table 22.2.3.3.1–2: USIM configuration
USIM field |
Priority |
Value |
Access Technology Identifier |
EFEPSLOCI |
PLMN1 (See preamble) |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN4. |
||
EFPLMNwAcT |
1 2 |
Default PLMN2 Remaining mandatory entries use default values |
Default All specified NB-IoT |
EFOPLMNwACT |
1 |
PLMN1 Remaining defined entries use default values |
All specified |
EFHPLMNwAcT |
1 |
PLMN4 |
NB-IoT |
EFUST |
Services 20, 42, 43, 74 and 96 are supported. Service 71 is not supported (there is no EHPLMN list). |
||
EFHPPLMN |
1 [120 minutes] |
||
EFNASCONFIG |
MinimumPeriodicSearchTimer set to [120 minutes] |
Preamble:
– The UE is made to camp on Ncell 12 and then Switched OFF (State 1).
22.2.3.3.2 Test procedure sequence
Table 22.2.3.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions. Subsequent configurations marked “T1”,“T2” etc are applied at the points indicated in the Main behaviour description in Table 22.2.3.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 36.508.
Table 22.2.3.3.2-1: Cell configuration changes over time
Parameter |
Unit |
Ncell 1 |
Ncell 12 |
Ncell 13 |
Remarks |
|
T0 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
“Off” |
Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1 |
T1 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
-85 |
Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1 |
T2 |
NRS EPRE |
dBm/15kHz |
-85 |
-85 |
-85 |
Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1 |
Table 22.2.1.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts cell levels according to row T1 of table 22.2.3.3.2-1 |
– |
– |
– |
– |
2 |
Power on the UE. |
– |
– |
– |
– |
3-15b1 |
Steps 2 to 14b1 of the registration procedure described in TS 36.508 subclause 8.1.5.2 are performed on Ncell 12. |
– |
– |
– |
– |
16 |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
<– |
RRC: RRCConnectionRelease-NB |
– |
– |
17 |
Check: Is PLMN1 indicated by the UE? |
– |
– |
1 |
P |
18 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 13 after 120 seconds, but before [120mins] (Note 1) from power on? |
–> |
RRCConnectionRequest-NB |
1 |
P |
19-23 |
Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed on Ncell 13. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
24 |
Check: Is PLMN2 indicated by the UE? |
– |
– |
1 |
P |
25 |
SS adjusts cell levels according to row T2 of table 22.2.1.3.2-1 |
– |
– |
– |
– |
26 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 1 after [120 mins] from step 18 |
–> |
RRCConnectionRequest-NB |
1 |
P |
27-31 |
Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
32 |
Check: Is PLMN4 indicated by the UE? |
– |
– |
1 |
P |
Note 1: Timers in Step 18 and 26 are derived from the value defined by the MinimumPeriodicSearchTimer. |
22.2.3.3.3 Specific message contents
None
22.2.4 NB-IoT / Cell selection / Qrxlevmin and Qqualmin / Serving cell becomes non-suitable (S<0 or barred or Srxlev > 0 and Squal < 0)
22.2.4.1 Test Purpose (TP)
(1)
with { UE in RRC_IDLE state }
ensure that {
when { a cell fulfils all requirements for a suitable cell except the cell selection criteria which are not fulfilled (Srxlev < 0)}
then { the UE does not consider the cell suitable and no camping on this cell can take place }
}
(2)
with { UE in RRC_IDLE state }
ensure that {
when { a cell fulfils all requirements for a suitable cell except the cell selection criteria which are not fulfilled (Srxlev > 0 AND Squal < 0)}
then { the UE does not consider the cell suitable and no camping on this cell can take place }
}
(3)
with { UE in RRC_IDLE state }
ensure that {
when { a cell fulfils all requirements for a suitable cell including the cell selection criteria for a cell which are also fulfilled (Srxlev > 0 AND Squal > 0)}
then { the UE considers the cell suitable and camps on it }
}
(4)
with { UE in RRC_IDLE state }
ensure that {
when { the serving cell becomes non-suitable (Srxlev < 0)and there is a suitable neighbour cell (Srxlev > 0) }
then { UE selects the suitable neighbour cell }
}
(5)
with { UE in RRC_IDLE state }
ensure that {
when { the serving cell becomes barred and there is a suitable neighbour cell}
then { UE selects the suitable neighbour cell }
}
(6)
with { UE in RRC_IDLE state }
ensure that {
when { the serving cell becomes non-suitable (Srxlev > 0 and Squal < 0)and there is a suitable neighbour cell (Srxlev > 0 and Squal > 0) }
then { UE selects the suitable neighbour cell }
}
22.2.4.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.300, clause 10.1.1.1 and TS 36.304, clause 4.1, 5.1.2.2, 5.2.1, 5.2.3.1, 5.2.3.2a , 5.2.4.6, 5.2.8a and 5.3. Unless otherwise stated these are Rel-13 requirements.1.
[TS 36.300, clause 10.1.1.1]
Cell selection:
– The UE NAS identifies a selected PLMN and equivalent PLMNs;
– The UE searches the E-UTRA frequency bands and for each carrier frequency identifies the strongest cell. It reads cell system information broadcast to identify its PLMN(s):
– The UE may search each carrier in turn ("initial cell selection") or make use of stored information to shorten the search ("stored information cell selection").
– The UE seeks to identify a suitable cell; if it is not able to identify a suitable cell it seeks to identify an acceptable cell. When a suitable cell is found or if only an acceptable cell is found it camps on that cell and commence the cell reselection procedure:
– A suitable cell is one for which the measured cell attributes satisfy the cell selection criteria; the cell PLMN is the selected PLMN, registered or an equivalent PLMN; the cell is not barred or reserved and the cell is not part of a tracking area which is in the list of "forbidden tracking areas for roaming";
– An acceptable cell is one for which the measured cell attributes satisfy the cell selection criteria and the cell is not barred;
[TS 36.304, clause 4.1]
When a UE is switched on, a public land mobile network (PLMN) is selected by NAS. For the selected PLMN, associated RAT(s) may be set [5]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use for cell selection and cell reselection.
With the cell selection, the UE searches for a suitable cell of the selected PLMN and chooses that cell to provide available services, further the UE shall tune to its control channel. This choosing is known as "camping on the cell".
The UE will, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of the chosen cell and as outcome of a successful Location Registration the selected PLMN becomes the registered PLMN [5].
[TS 36.304, clause 5.1.2.2]
The UE shall scan all RF channels in the E-UTRA bands according to its capabilities to find available PLMNs. On each carrier, the UE shall search for the strongest cell and read its system information, in order to find out which PLMN(s) the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN (see the PLMN reading in [3]) shall be reported to the NAS as a high quality PLMN (but without the RSRP value), provided that the following high quality criterion is fulfilled:
1. For an E-UTRAN and NB-IoT cell, the measured RSRP value shall be greater than or equal to -110 dBm.
Found PLMNs that do not satisfy the high quality criterion, but for which the UE has been able to read the PLMN identities are reported to the NAS together with the RSRP value. The quality measure reported by the UE to NAS shall be the same for each PLMN found in one cell.
…
Once the UE has selected a PLMN, the cell selection procedure shall be performed in order to select a suitable cell of that PLMN to camp on.
[TS 36.304, clause 5.2.1]
UE shall perform measurements for cell selection and reselection purposes as specified in [10].
The NAS can control the RAT(s) in which the cell selection should be performed, for instance by indicating RAT(s) associated with the selected PLMN, and by maintaining a list of forbidden registration area(s) and a list of equivalent PLMNs. The UE shall select a suitable cell based on idle mode measurements and cell selection criteria.
In order to speed up the cell selection process, stored information for several RATs may be available in the UE.
When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If a better cell is found, that cell is selected. The change of cell may imply a change of RAT. Details on performance requirements for cell reselection can be found in [10].
The NAS is informed if the cell selection and reselection results in changes in the received system information relevant for NAS.
For normal service, the UE shall camp on a suitable cell, tune to that cell’s control channel(s) so that the UE can:
– Receive system information from the PLMN; and
– receive registration area information from the PLMN, e.g., tracking area information; and
– receive other AS and NAS Information; and
– if registered:
– receive paging and notification messages from the PLMN; and
– initiate transfer to connected mode.
[TS 36.304, clause 5.2.3.1]
The UE shall use one of the following two cell selection procedures:
a) Initial Cell Selection
This procedure requires no prior knowledge of which RF channels are E-UTRA or NB-IoT carriers. The UE shall scan all RF channels in the E-UTRA bands according to its capabilities to find a suitable cell. On each carrier frequency, the UE need only search for the strongest cell. Once a suitable cell is found this cell shall be selected.
[TS 36.304, clause 5.2.3.2a]
The cell selection criterion S is fulfilled when:
Srxlev > 0 AND Squal > 0 |
where:
Srxlev = Qrxlevmeas – Qrxlevmin – Pcompensation – Qoffsettemp Squal = Qqualmeas – Qqualmin – Qoffsettemp |
where:
Srxlev |
Cell selection RX level value (dB) |
Squal |
Cell selection quality value (dB) |
Qoffsettemp |
Offset temporarily applied to a cell as specified in [3] (dB) |
Qrxlevmeas |
Measured cell RX level value (RSRP) |
Qqualmeas |
Measured cell quality value (RSRQ) |
Qrxlevmin |
Minimum required RX level in the cell (dBm) |
Qqualmin |
Minimum required quality level in the cell (dB) |
Pcompensation |
If the UE supports the additionalPmax in the NS-PmaxList, if present, in SIB1, SIB3 and SIB5: max(PEMAX1 –PPowerClass, 0) – (min(PEMAX2, PPowerClass) – min(PEMAX1, PPowerClass)) (dB); else: max(PEMAX1 –PPowerClass, 0) (dB); |
PEMAX1, PEMAX2 |
Maximum TX power level an UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in [TS 36.101]. PEMAX1 and PEMAX2 are obtained from the p-Max and the NS-PmaxList respectively in SIB1, SIB3 and SIB5 as specified in TS 36.331 [3]. |
PPowerClass |
Maximum RF output power of the UE (dBm) according to the UE power class as defined in [TS 36.101] |
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise and for NB-IoT this equals to Qoffsetfrequency. |
Qoffsettemp |
Offset temporarily applied to a cell as specified in [3] |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2 (5.2.3.2a for NB-IoT), but may exclude all CSG cells that are known by the UE not to be CSG member cells.
The cells shall be ranked according to the R criteria specified above, deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better ranked than the serving cell during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 36.304, clause 5.2.8a]
In this state, the UE shall attempt to find a suitable cell of any PLMN to camp on and searching first for a high quality cell, as defined in subclause 5.1.2.2.
The UE, which is not camped on any cell, shall stay in this state until a suitable cell is found.
[TS 36.304, clause 5.3.1]
Cell status and cell reservations are indicated in the SystemInformationBlockType1 message (or SystemInformationBlockType1-NB message) [3] by means of two fields:
– cellBarred (IE type: "barred" or "not barred")
In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs
– cellReservedForOperatorUse (IE type: "reserved" or "not reserved")
In case of multiple PLMNs indicated in SIB1, this field is specified per PLMN.
When cell status is indicated as "not barred" and "not reserved" for operator use,
– All UEs shall treat this cell as candidate during the cell selection and cell reselection procedures.
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
– UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate during the cell selection and reselection procedures if the field cellReservedForOperatorUse for that PLMN set to “reserved”.
– UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
NOTE 1: ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN; ACs 12, 13, 14 are only valid for use in the home country [4].
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
– The UE is not permitted to select/reselect this cell, not even for emergency calls.
– The UE shall select another cell according to the following rule:
– If the cell is to be treated as if the cell status is “barred” due to being unable to acquire the MasterInformationBlock (or MasterInformationBlock-NB), the SystemInformationBlockType1 (or SystemInformationBlockType1-NB), or the SystemInformationBlockType2 (or SystemInformationBlockType2-NB):
– the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds.
– the UE may select another cell on the same frequency if the selection criteria are fulfilled.
– else
– If the cell is a CSG cell:
– the UE may select another cell on the same frequency if the selection/reselection criteria are fulfilled.
– else
– If the field intraFreqReselection in field cellAccessRelatedInfo in SystemInformationBlockType1 (or SystemInformationBlockType1-NB) message is set to "allowed", the UE may select another cell on the same frequency if re-selection criteria are fulfilled.
– The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
– If the field intraFreqReselection in field cellAccessRelatedInfo in SystemInformationBlockType1 (or SystemInformationBlockType1-NB) message is set to "not allowed" the UE shall not re-select a cell on the same frequency as the barred cell;
– The UE shall exclude the barred cell and the cells on the same frequency as a candidate for cell selection/reselection for 300 seconds.
The cell selection of another cell may also include a change of RAT.
22.2.4.3 Test description
22.2.4.3.1 Pre-test conditions
System Simulator:
– Ncell 1 and Ncell 2 on frequency f1 but have different tracking areas according to TS 36.508 Table 8.1.4.2-6. Ncell 3 on frequency f2 according to TS 36.508 Table 8.1.4.2-6.
– System information combination 2 as defined in TS 36.508 [18] clause 8.1.4.3.1 is used.
– None.
Preamble:
– The UE is in state Switched OFF (state 1) ac-NB cording to [18 TS 36.508].
22.2.4.3.2 Test procedure sequence
Table 22.2.4.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cell at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause. Configurations marked "T1" , "T2", "T3" , "T4", "T5" and "T6" are applied at the points indicated in the Main behaviour description in Table 22.2.4.3.2-2
Table 22.2.4.3.2-1: Time instances of cell power level and parameter changes
Parameter |
Unit |
NCell 1 |
Ncell 2 |
Ncell 3 |
Remark |
|
T1 |
Cell-specific NRS EPRE |
dBm/15kHz |
-95 |
"Off" |
"Off" |
The power level value is such to satisfy Srxlev Ncell 1 < 0 but the UE is able to read the PLMN identity |
Qrxlevmin |
dBm |
-84 |
– |
– |
||
Pcompensation |
dB |
0 |
– |
– |
||
T2 |
Cell-specific NRS EPRE |
dBm/15kHz |
-95 |
"Off" |
"Off" |
The power level value is such to satisfy Srxlev Ncell 1 > 0 and Squal Ncell 1 < 0 but the UE is able to read the PLMN identity |
RSRQ |
dB |
-32 |
– |
– |
||
Noc |
dBm/15kHz |
-75 |
– |
– |
||
Qrxlevmin |
dBm |
-106 |
– |
– |
||
Qqualmin |
dB |
-18 |
– |
– |
||
Pcompensation |
dB |
0 |
– |
– |
||
T3 |
Cell-specific NRS EPRE |
dBm/15kHz |
-65 |
"Off" |
"Off" |
The power level is such that Srxlev Ncell 1 > 0 and Squal Ncell 1 > 0 |
RSRQ |
dB |
-5 |
– |
– |
||
Noc |
dBm/15kHz |
-75 |
– |
– |
||
T4 |
Cell-specific NRS EPRE |
dBm/15kHz |
"Off" |
-85 |
"Off" |
SrxlevNcell1 < 0 |
Srxlev* |
dB |
– |
25 |
– |
Ncell 2 becomes the strongest Ncell |
|
T5 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
"Off" |
-85 |
-91 |
SrxlevNcell 2 > 0, SrxlevNcell 3 > 0 , RNcell 3 < RNcell 2 |
Srxlev* (FDD) |
dB |
– |
25 |
19 |
||
Cell-specific NRS EPRE (TDD) |
dBm/15kHz |
"Off" |
-85 |
-89 |
||
Srxlev* (TDD) |
dB |
– |
25 |
21 |
||
cellBarred |
– |
– |
barred |
notBarred |
Serving Ncell becomes barred |
|
T6 |
Cell-specific NRS EPRE |
dBm/15kHz |
"Off" |
-85 |
-97 |
SrxlevNcell 3 > 0 and SqualNcell 3 < 0 |
RSRQ |
dB |
– |
-3.28 |
-26 |
||
Qrxlevmin |
dBm |
– |
-92 |
-106 |
||
Qqualmin |
dB |
– |
-20 |
-20 |
||
Pcompensation |
dB |
– |
0 |
0 |
||
Srxlev* |
dB |
– |
7 |
9 |
Ncell 2 is suitable Ncell |
|
Squal* |
dB |
– |
16.72 |
-6 |
Squal = Qqualmeas – Qqualmin |
|
Noc |
dBm/15kHz |
– |
"Off" |
-75 |
||
cellBarred |
– |
notBarred |
notBarred |
|||
NOTE 1: The downlink signal level uncertainty is specified in TS 36.508 section 8.1.3.4.1 NOTE 2: Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1. |
Table 22.2.4.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0A |
SS re-adjusts the cell-specific reference signal level of Ncell 1 according to row "T1" in table 22.2.4.3.2-1. |
– |
– |
– |
– |
0B |
Wait for 1.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
1 |
The UE is switched on. |
– |
– |
– |
– |
2 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 1 within the next 60 s? |
–> |
RRCConnectionRequest-NB |
1 |
F |
3 |
SS re-adjusts the cell-specific reference signal level of Ncell 1 level according to row "T2" in table 22.2.4.3.2-1. |
– |
– |
– |
– |
3A |
Wait for 1.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
4 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 1 within the next 60 s? |
–> |
RRCConnectionRequest-NB |
2 |
F |
5 |
SS re-adjusts the cell-specific reference signal level of Ncell 1 level according to row "T3" in table 22.2.4.3.2-1. |
– |
– |
– |
– |
6 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 1? |
–> |
RRCConnectionRequest-NB |
3 |
P |
7-18 |
Steps 3 to 14 of the registration procedure described in TS 36.508 subclause 8.1.5.2.3 are performed on Ncell 1. |
– |
– |
– |
– |
18A |
The SS transmits an RRCConnectionRelease-NB message to release RRC connection and move to RRC_IDLE. |
<– |
RRCConnectionRelease-NB |
– |
– |
19 |
SS re-adjusts the cell-specific reference signal level of Ncell 1 and Ncell 2 according to row "T4" in table 22.2.4.3.2-1. |
– |
– |
– |
– |
20 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 2? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
4 |
P |
21 |
SS changes Ncell 2 and Ncell 3 signal level and SIB1-NB IE cellBarred-r13 according to row "T5" in table 22.2.4.3.2-1 and transmits a Paging-NB message including systemInfoModification-r13. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased. |
<– |
Paging-NB |
– |
– |
22 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 3? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
5 |
P |
23 |
SS changes the SIB1-NB IE cellBarred-r13 according to row T6 in table 22.2.4.3.2-1 for Ncell 2 and waitst for 1.1* modification period to allow the new system information to take effect. |
– |
– |
– |
– |
23A |
SS re-adjusts the cell-specific reference signal level of Ncell 2 and Ncell 3 according to row "T6" in table 22.2.4.3.2-1. |
– |
– |
– |
– |
24 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 2? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
6 |
P |
22.2.4.3.3 Specific message contents
Table 22.2.4.3.3-0: MasterInformationBlock-NB for Ncell 1 (all steps, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-NB ::= SEQUENCE { |
|||
systemInfoValueTag-r13 |
The value is increased by 1 in step 0A, step 3, step 19. |
||
} |
Table 22.2.4.3.3-0A: MasterInformationBlock-TDD-NB for Ncell 1 (all steps, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.2-1A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-TDD-NB ::= SEQUENCE { |
|||
systemInfoValueTag-r15 |
The value is increased by 1 in step 0A, step 3, step 19. |
||
} |
Table 22.2.4.3.3-1: SystemInformationBlockType1-NB for Ncell 1 (step 0A, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2-3, Table 8.1.4.3.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType1-NB-r13 ::= SEQUENCE { |
|||
CellSelectionInfo-r13 SEQUENCE { |
|||
q-RxLevMin-r13 |
-42 (-84 dBm) |
||
} |
|||
} |
Table 22.2.4.3.3-2: SystemInformationBlockType1-NB for Ncell 1 (step 3, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2-3, Table 8.1.4.3.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType1-NB-r13 ::= SEQUENCE { |
|||
CellSelectionInfo-r13 SEQUENCE { |
|||
q-RxLevMin-r13 |
-53 (-106 dBm) |
||
q-Qualmin-r13 |
-18 dB |
||
} |
|||
} |
Table 22.2.4.3.3-3: SystemInformationBlockType1-NB for Ncells 1 and 2 (step 19, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2-3, Table 8.1.4.3.2-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB-r13 ::= SEQUENCE { |
|||
cellSelectionInfo-r13 SEQUENCE { |
|||
q-RxLevMin-r13 |
-55 (-110 dBm) |
||
} |
|||
systemInfoValueTagList-r13 SEQUENCE (SIZE (1.. maxSI-Message-NB-r13)) OF |
|||
{ |
|||
SystemInfoValueTagSI-r13[2] |
1 |
||
} |
|||
} |
Table 22.2.4.3.3-4: SystemInformationBlockType3-NB for Ncells 1 and 2 (step 19, table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.3, Table 8.1.4.3.3-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
|||
cellReselectionInfoCommon-r13 SEQUENCE { |
|||
q-Hyst-r13 |
dB0 |
||
} |
|||
intraFreqCellReselectionInfo SEQUENCE { |
|||
q-RxLevMin-r13 |
-55 (-110 dBm) |
||
t-Reselection-r13 |
s21 |
||
} |
|||
} |
Table 22.2.4.3.3-5: MasterInformationBlock-NB for Ncell 2 (step 21 and 23, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-NB ::= SEQUENCE { |
|||
systemInfoValueTag-r13 |
The value is increased by 1 |
||
} |
Table 22.2.4.3.3-5A: MasterInformationBlock-TDD-NB for Ncell 2 (step 21 and 23, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.2-1A |
|||
Information Element |
Value/remark |
Comment |
Condition |
MasterInformationBlock-TDD-NB ::= SEQUENCE { |
|||
systemInfoValueTag-r15 |
The value is increased by 1 |
||
} |
Table 22.2.4.3.3-6: SystemInformationBlockType1-NB for Ncell 2 (step 21, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.2-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB-r13 ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
cellBarred-r13 |
barred |
||
intraFreqReselection-r13 |
allowed |
||
} |
|||
} |
Table 22.2.4.3.3-7: Paging-NB (step 21, Table 22.2.4.3.2-2)
Derivation path: 36.508 Table 8.1.6.1-2 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Paging-NB ::= SEQUENCE { |
|||
PagingRecordList-r13 |
Not present |
||
systemInfoModification-r13 |
True |
||
systemInfoModification-eDRX-r13 |
Not present |
||
nonCriticalExtension SEQUENCE {} |
Not present |
||
} |
Table 22.2.4.3.3-8: SystemInformationBlockType1-NB for Ncell 2 (step 23, Table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.2-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB-r13 ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
cellBarred-r13 |
notbarred |
Ncell 2 |
|
intraFreqReselection-r13 |
notAllowed |
Ncell 2 |
|
} |
|||
cellSelectionInfo-r13 SEQUENCE { |
|||
q-RxLevMin-r13 |
-46 (-92 dBm) |
Ncell 2 |
|
q-QualMin-r13 |
-20 dB |
Ncell 2 |
|
} |
|||
systemInfoValueTagList-r13 SEQUENCE (SIZE (1.. maxSI-Message-NB-r13)) OF |
|||
{ |
|||
SystemInfoValueTagSI-r13[2] |
2 |
||
} |
|||
} |
Table 22.2.4.3.3-9: SystemInformationBlockType3-NB for Ncell 2 (step 23, table 22.2.4.3.2-2)
Derivation Path: 36.508 clause 8.1.4.3.2, Table 8.1.4.3.3-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
|||
cellReselectionInfoCommon-r13 SEQUENCE { |
|||
q-Hyst-r13 |
dB0 |
||
} |
|||
intraFreqCellReselectionInfo SEQUENCE { |
|||
q-RxLevMin-r13 |
-46 (-92 dBm) |
Ncell 2 |
|
q-QualMin-r13 |
-20 dB |
Ncell 2 |
|
t-Reselection-r13 |
s21 |
||
} |
|||
} |
22.2.5 NB-IoT / Intra-frequency Cell reselection / Qhyst, Qoffset, Treselection and Cell-specific reselection parameters
22.2.5.1 Test Purpose (TP)
(1)
with { UE in RRC_IDLE state, and the UE is not in high mobility state }
ensure that {
when { Qhyst is non-zero or its value changes in system information }
then { UE reselects the highest ranked cell taking the actual Qhyst value into account }
}
(2)
with { UE in RRC_IDLE state, and the UE is not in high mobility state }
ensure that {
when { cell reselection criteria are fulfilled during a time interval Treselection }
then { UE reselects the highest ranked cell }
}
(3)
with { UE in RRC_IDLE state, and the UE is not in high mobility state }
ensure that {
when { Qoffset is non-zero or its value changes in system information }
then { UE reselects the highest ranked cell taking the actual Qoffset value into account }
}
(4)
with { the UE is in RRC_IDLE and SystemInformationBlockType4-NB contain a cell-specific Qoffset for a neighbour intra frequency cell }
ensure that {
when { the neighbour cell has lower power than the serving cell but it is higher ranked due to the cell-specific Qoffset }
then { the UE reselects the neighbour cell with cell-specific Qoffset }
}
(5)
with { the UE is in RRC_IDLE and SystemInformationBlockType4-NB contain a black listed cell }
ensure that {
when { a black listed cell becomes higher ranked than the serving cell }
then { the UE remains camped on the serving cell }
}
(6)
with { UE in RRC_IDLE state, and the UE is not in high mobility state }
ensure that {
when { SintrasearchP is non-zero in system information }
then { UE perform measurement and reselects the highest ranked cell upon Srxlev < SintrasearchP }
}
22.2.5.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.300, clause 10.1.1.2; TS 36.304, clauses 5.2.1, 5.2.4.1, 5.2.4.2a and 5.2.4.6; TS 36.331, clause 6.7.3.1; TS 36.133, clause 4.2.2.4. Unless otherwise stated these are Rel-13 requirements.
[TS 36.300, clause 10.1.1.2]
A UE in RRC_IDLE performs cell reselection. The principles of the procedure are the following:
– The UE makes measurements of attributes of the serving and neighbour cells to enable the reselection process:
– There is no need to indicate neighbouring cells in the serving cell system information to enable the UE to search and measure a cell i.e. E-UTRAN relies on the UE to detect the neighbouring cells;
– For the search and measurement of inter-frequency neighbouring cells, only the carrier frequencies need to be indicated;
– Measurements may be omitted if the serving cell attribute fulfils particular search or measurement criteria.
– Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which involves measurements of the serving and neighbour cells, except for NB-IoT:
…
For NB-IoT, cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which involve measurements of the serving and neighbour cells as follows:
– Intra-frequency reselection is based on ranking of cells (potentially with cell specific offsets);
– Inter-frequency reselection is based on ranking of frequencies (potentially with frequency specific offsets);
– Blind redirection supported for load balancing.
[TS 36.304, clause 5.2.1]
When camped on a cell, the UE shall regularly search for a better cell according to the cell reselection criteria. If a better cell is found, that cell is selected.
[TS 36.304, clause 5.2.4.1]
The UE shall not consider any black listed cells as candidate for cell reselection.
[TS 36.304, clause 5.2.4.2a]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
– If the serving cell fulfils Srxlev > SIntraSearchP, the UE may choose not to perform intra-frequency measurements.
– Otherwise, the UE shall perform intra-frequency measurements.
– The UE shall apply the following rules for NB-IoT inter-frequencies which are indicated in system information:
– If the serving cell fulfils Srxlev > SnonIntraSearchP, the UE may choose not to perform inter-frequency measurements.
– Otherwise, the UE shall perform inter-frequency measurements.
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise and for NB-IoT this equals to Qoffsetfrequency. |
Qoffsettemp |
Offset temporarily applied to a cell as specified in [3] |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2 (5.2.3.2a for NB-IoT), but may exclude all CSG cells that are known by the UE not to be CSG member cells.
The cells shall be ranked according to the R criteria specified above, deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better ranked than the serving cell during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 36.331, clause 6.7.3.1]
The IE SystemInformationBlockType3-NB contains cell re-selection information common for intra-frequency, and inter-frequency cell re-selection as well as intra-frequency cell re-selection information other than neighbouring cell related.
The IE SystemInformationBlockType4-NB contains neighbouring cell related information relevant only for intra-frequency cell re-selection. The IE includes cells with specific re-selection parameters.
[TS 36.133, clause 4.2.2.4]
…
The UE shall be able to evaluate whether a newly detectable inter-frequency cell meets the reselection criteria defined in TS 36.304 within Kcarrier * Tdetect,EUTRAN_Inter if at least carrier frequency information is provided for inter-frequency neighbour cells by the serving cells when Treselection = 0 provided that the reselection criteria is met by a margin of at least 5dB for reselections based on ranking or 6dB for RSRP reselections based on absolute priorities or 4dB for RSRQ reselections based on absolute priorities.
22.2.5.3 Test description
22.2.5.3.1 Pre-test conditions
System Simulator:
– Ncells 1, 2, and 4 in different tracking areas according to TS 36.508 Table 8.1.4.2-6.
– System information combination 2 as defined in TS 36.508 [18] clause 8.1.4.3.1 is used.
– Tcell Offset for Ncell 2 and Ncell 4 is set to same value as Ncell 1.
UE:
None
Preamble:
– UE is in state 3-NB Idle mode on Ncell 1 according to TS 36.508 [18].
22.2.5.3.2 Test procedure sequence
Table 22.2.5.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause. Configurations marked "T1", "T2", "T3", "T4", "T5", "T6", "T7", "T8", "T9", "T10" and "T11"are applied at the points indicated in the Main behaviour description in Table 22.2.5.3.2-2.
Table 22.2.5.3.2-1: Time instances of cell power level and parameter change
Parameter |
Unit |
Ncell 1 |
Ncell 2 |
Ncell 4 |
Remark |
|
T1 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
-91 |
-85 |
Off |
Ncell 2 becomes stronger than Ncell 1 but Ncell 1 remains the highest ranked one due to QhystsCell1 |
Cell-specific NRS EPRE (TDD) |
-89 |
-85 |
||||
T2 |
Qhysts |
dB |
0 |
0 |
– |
QhystsCell1 change causes Ncell 2 to become highest ranked cell |
T3 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
-85 |
-91 |
Off |
Ncell 1 becomes the strongest and highest ranked one |
Cell-specific NRS EPRE (TDD) |
-85 |
-89 |
||||
Qoffsets,n |
dB |
24 |
0 |
– |
Qoffsets,nCell2 remains zero |
|
T4 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
-91 |
-85 |
Off |
Ncell 1 becomes weaker but it remains the highest ranked one due to Qoffsets,nCell1 |
Cell-specific NRS EPRE (TDD) |
-89 |
-85 |
||||
T5 |
Qoffsets,n |
dB |
0 |
0 |
– |
Ncell 2 becomes the highest ranked one due to Qoffsets,nCell1 change |
T6 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
-85 |
-91 |
Off |
Ncell 1 becomes the highest ranked one |
Cell-specific NRS EPRE (TDD) |
-85 |
-89 |
||||
Treselection |
s |
21 |
0 |
– |
||
T7 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
-91 |
-85 |
Off |
Ncell 2 becomes the highest ranked cell |
Cell-specific NRS EPRE (TDD) |
-89 |
-85 |
||||
T8 |
Cell-specific NRS EPRE |
dBm/15kHz |
Off |
-91 |
-85 |
Ncell 4 has higher power than Ncell 2 but is black listed |
T9 |
Cell-specific NRS EPRE (FDD) |
dBm/15kHz |
-91 |
-85 |
Off |
Ncell 1 becomes the highest ranked one |
Cell-specific NRS EPRE (TDD) |
-89 |
-85 |
||||
Treselection |
s |
0 |
0 |
– |
||
Qoffsets,n |
dB |
24 |
-24 |
– |
||
T9A |
Cell-specific NRS EPRE |
dBm/15kHz |
-91 |
-94 |
Off |
Ncell 1 remains highest ranked cell |
T10 |
Cell-specific NRS EPRE |
dBm/15kHz |
-85 |
Off |
Off |
Only Ncell 1 is on |
Qoffsets,n |
dB |
0 |
– |
– |
||
T11 |
Cell-specific NRS EPRE |
dBm/15kHz |
-91 |
-79 |
Off |
Srxlev of Ncell 1 is less than SintrasearchP |
SintrasearchP |
dB |
22 |
22 |
– |
Table 22.2.5.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0 |
Wait for 1 second to allow UE to enter RRC_IDLE state on Ncell 1. |
– |
– |
– |
– |
1 |
SS re-adjusts the cell-specific reference signal levels according to row "T1" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
2 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 2 within the next 10s? |
–> |
RRCConnectionRequest-NB |
1 |
F |
3 |
SS resets QhystsCell1 according to row "T2" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
4 |
The SS transmits a Paging-NB message on Ncell 1 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 1. |
<– |
Paging-NB |
– |
– |
5 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 2? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
6 |
SS changes Qoffsets,nCell1 according to rows "T3" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
7 |
The SS transmits a Paging-NB message on Ncell 2 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 2. |
<– |
Paging-NB |
– |
– |
8 |
Wait for 2.1* modification period (Note 1) to allow the new system information to take effect. |
– |
– |
– |
– |
8A |
SS re-adjusts cell-specific reference signal levels according to rows "T3" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
9 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 1? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
10 |
Wait for 1 second to allow UE to enter RRC_IDLE state on Ncell 1. |
– |
– |
– |
– |
11 |
SS re-adjusts cell-specific reference signal levels according to row "T4" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
12 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 2 within the next 10s? |
–> |
RRCConnectionRequest-NB |
3 |
F |
13 |
SS resets Qoffsets,nCell1 according to row "T5" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
14 |
The SS transmits a Paging-NB message on Ncell 1 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 1. |
<– |
Paging-NB |
– |
– |
15 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 2? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
3 |
– |
16 |
SS changes TreselectionCell1 according to rows "T6" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
17 |
The SS transmits a Paging-NB message on Ncell 2 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 2. |
<– |
Paging-NB |
– |
– |
18 |
Wait for 2.1* modification period (Note 1) to allow the new system information to take effect. |
– |
– |
– |
– |
18A |
SS re-adjusts cell-specific reference signal levels according to rows "T6" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
19 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 1? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
20 |
Wait for 1 second to allow UE to enter RRC_IDLE state on Ncell 1. |
– |
– |
– |
– |
21 |
SS re-adjusts cell-specific reference signal levels according to rows "T7" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
22 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 2 within the next 20s? |
–> |
RRCConnectionRequest-NB |
2 |
F |
23 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 2 within the next 26s? |
–> |
RRCConnectionRequest-NB |
2 |
P |
24 |
Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed on Ncell 2. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
25 |
The SS re-adjusts the cell-specific reference signal levels according to row "T8" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
26 |
Check: Does the UE initiate a random access procedure on Ncell 4 within the next 120s? |
– |
– |
5 |
F |
27 |
SS changes TreselectionCell1 according to rows "T9" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
28 |
The SS transmits a Paging-NB message on Ncell 2 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 2. |
<– |
Paging-NB |
– |
– |
29 |
Wait for 2.1* modification period (Note 1) to allow the new system information to take effect. |
– |
– |
– |
– |
29A |
SS re-adjusts cell-specific reference signal levels according to rows "T9" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
30 |
Steps 1 to 5 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed on Ncell 1 |
– |
– |
4 |
– |
30A |
SS re-adjusts cell-specific reference signal levels according to rows "T9A" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
30B |
SS releases the RRC connection |
<– |
RRCConnectionRelease-NB |
– |
– |
31 |
SS resets QhystsCell1 according to row "T10" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
32 |
The SS transmits a Paging-NB message on Ncell 1 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 1. |
<– |
Paging-NB |
– |
– |
33 |
Wait for 2.1* modification period (Note 1) to allow the new system information to take effect. |
– |
– |
– |
– |
33A |
The SS changes the SintrasearchP for Ncell 1 and N cell2 according to row “T11” in table 22.2.5.3.2-1 |
||||
33B |
The SS transmits a Paging-NB message on Ncell 1 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased on Ncell 1. |
<– |
Paging-NB |
||
33C |
Wait for 2.1* modification period (Note 1) to allow the new system information to take effect. |
– |
– |
– |
– |
34 |
The SS re-adjusts the cell-specific reference signal levels according to row "T11" in table 22.2.5.3.2-1. |
– |
– |
– |
– |
35 |
Check: Does the test result of generic procedure 8.1.5A.5 indicate that the UE is camped on Ncell 2? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
6 |
P |
36-40 |
void |
– |
– |
– |
– |
NOTE 1: The wait time of 2.1* modification period in step 8,step 18, step 29, step 33 and step 33C is to allow for the network to paging the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 90ms of the start of modification period. |
22.2.5.3.3 Specific message contents
Table 22.2.5.3.3-1: MasterInformationBlock-NB for Ncell 1 (preamble and all steps, Table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2-1 |
||
Information Element |
Value/remark |
Comment |
MasterInformationBlock-NB ::= SEQUENCE { |
||
systemInfoValueTag-r13 |
The value is increased by 1 in step 4, step 7, step 14, step 17, step 28 and step 32, step 33B |
|
} |
Table 22.2.5.3.3-1A: MasterInformationBlock-TDD-NB for Ncell 1 (preamble and all steps, Table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2-1A |
||
Information Element |
Value/remark |
Comment |
MasterInformationBlock-TDD-NB ::= SEQUENCE { |
||
systemInfoValueTag-r15 |
The value is increased by 1 in step 4, step 7, step 14, step 17, step 28 and step 32, step 33B |
|
} |
Table 22.2.5.3.3-2: SystemInformationBlockType3-NB for Ncell 1 (preamble, table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.3-2 |
|||
Information Element |
Value/remark |
Comment |
|
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
|||
cellReselectionInfoCommon-r13 SEQUENCE { |
|||
q-Hyst-r13 |
dB24 |
QhystsCell1 |
|
} |
|||
} |
Table 22.2.5.3.3-3: SystemInformationBlockType4-NB for Ncell 2 (all steps, Table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-3 |
||
Information Element |
Value/Remark |
Comment |
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
||
IntraFreqBlackCellList-r13 SEQUENCE { |
1 entry |
|
start[1] |
PhysicalCellID of Ncell 4 |
|
range[1] |
Not present |
|
} |
||
} |
Table 22.2.5.3.3-4: SystemInformationBlockType3-NB for Ncell 1 (step 4, table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.3-2 |
|||
Information Element |
Value/remark |
Comment |
|
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
|||
cellReselectionInfoCommon-r13 SEQUENCE { |
|||
q-Hyst-r13 |
dB0 |
QhystsCell1 |
|
} |
|||
} |
Table 22.2.5.3.3-5: SystemInformationBlockType4-NB for Ncell 1 (step 7, table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.3-3 |
|||
Information Element |
Value/remark |
Comment |
|
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
|||
intraFreqNeighCellList-r13 SEQUENCE (SIZE (1..maxCellIntra)) OF SEQUENCE { |
|||
physCellId [1] |
Physical cell identity of Ncell 2 |
||
q-OffsetCell [1] |
dB24 |
Qoffsets,nCell1 |
|
} |
|||
} |
Table 22.2.5.3.3-6: SystemInformationBlockType4-NB for Ncell 1 (step 14, table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.3-3 |
|||
Information Element |
Value/remark |
Comment |
|
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
|||
intraFreqNeighCellList SEQUENCE (SIZE (1..maxCellIntra)) OF SEQUENCE { |
|||
physCellId [1] |
Physical cell identity of Ncell 2 |
||
q-OffsetCell [1] |
dB0 |
Qoffsets,nCell1 |
|
} |
|||
} |
Table 22.2.5.3.3-7: SystemInformationBlockType3-NB for Ncell 1 (step 17, table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.3-2 |
|||
Information Element |
Value/remark |
Comment |
|
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
|||
cellReselectionInfoCommon-r13 SEQUENCE { |
|||
q-Hyst-r13 |
dB0 |
QhystsCell1 |
|
} |
|||
intraFreqCellReselectionInfo-r13 SEQUENCE { |
|||
t-Reselection-r13 |
s21 |
seconds |
|
} |
|||
} |
Table 22.2.5.3.3-8: MasterInformationBlock-NB for Ncell 2 (step 28 and step 32, Table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2-1 |
||
Information Element |
Value/remark |
Comment |
MasterInformationBlock-NB ::= SEQUENCE { |
||
systemInfoValueTag-r13 |
The value is increased by 1 |
|
} |
Table 22.2.5.3.3-8A: MasterInformationBlock-TDD-NB for Ncell 2 (step 28 and step 32, Table 22.2.5.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2-1A |
||
Information Element |
Value/remark |
Comment |
MasterInformationBlock-TDD-NB ::= SEQUENCE { |
||
systemInfoValueTag-r15 |
The value is increased by 1 |
|
} |
Table 22.2.5.3.3-9: SystemInformationBlockType4-NB for Ncell 1 (step 28, Table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-3 |
||
Information Element |
Value/Remark |
Comment |
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
||
IntraFreqNeighCellList-r13 { |
1 entry |
|
physCellId[1] |
PhysicalCellID of Cell 2 |
|
q-OffsetCell[1] |
dB24 |
|
} |
||
} |
Table 22.2.5.3.3-10: SystemInformationBlockType4-NB for Ncell 2 (step 28, Table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-3 |
||
Information Element |
Value/Remark |
Comment |
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
||
intraFreqNeighCellList-r13 SEQUENCE { |
1 entry |
|
physCellId[1] |
PhysicalCellID of Ncell 1 |
|
q-OffsetCell[1] |
dB-24 |
|
} |
||
} |
Table 22.2.5.3.3-11: SystemInformationBlockType3-NB for Ncells 1 (step 28, table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-2 |
||
Information Element |
Value/remark |
Comment |
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
||
intraFreqCellReselectionInfo-r13 SEQUENCE { |
||
t-Reselection-r13 |
s0 |
|
} |
||
} |
Table 22.2.5.3.3-12: SystemInformationBlockType4-NB for Ncell 1 (step 32, Table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-3 |
||
Information Element |
Value/Remark |
Comment |
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
||
IntraFreqNeighCellList-r13 { |
1 entry |
|
physCellId[1] |
PhysicalCellID of Ncell 2 |
|
q-OffsetCell[1] |
dB0 |
|
} |
||
} |
Table 22.2.5.3.3-13: SystemInformationBlockType4-NB for Ncell 2 (step 32, Table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-3 |
||
Information Element |
Value/Remark |
Comment |
SystemInformationBlockType4-NB-r13 ::= SEQUENCE { |
||
intraFreqNeighCellList-r13 SEQUENCE { |
1 entry |
|
physCellId[1] |
PhysicalCellID of Ncell 1 |
|
q-OffsetCell[1] |
dB0 |
|
} |
||
} |
Table 22.2.5.3.3-14: SystemInformationBlockType3-NB for Ncells 1and 2 (step 33A, table 22.2.5.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-2 |
||
Information Element |
Value/remark |
Comment |
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
||
intraFreqCellReselectionInfo-r13 SEQUENCE { |
||
s-IntraSearchP-r13 |
11 (22 dB) |
|
} |
||
} |
Table 22.2.5.3.3-14 to 17: Void
22.2.6 NB-IoT / Cell reselection using cell status and cell reservations / Access control class 0 to 9
22.2.6.1 Test Purpose (TP)
(1)
with { UE camped normally in state RRC_IDLE and UE fitted with a USIM with access class 0..9}
ensure that {
when { a higher ranked cell is found with cell status "barred" }
then { UE does not attempt to reselect to the higher ranked cell }
}
(2)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9}
ensure that {
when { a higher ranked cell is found "reserved" for Operator use }
then { UE does not attempt to reselect to the higher ranked cell }
}
22.2.6.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clauses 5.2.4.4 and 5.3.1.
[TS 36.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.4.6, for the best cell according to absolute priority reselection criteria specified in subclause 5.2.4.5, the UE shall check if the access is restricted according to the rules in subclause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1, the UE shall not consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
[TS 36.304, clause 5.3.1]
Cell status and cell reservations are indicated in the SystemInformationBlockType1 message (or SystemInformationBlockType1-NB message) [3] by means of two fields:
– cellBarred (IE type: "barred" or "not barred")
In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs
– cellReservedForOperatorUse (IE type: "reserved" or "not reserved")
In case of multiple PLMNs indicated in SIB1, this field is specified per PLMN.
When cell status is indicated as "not barred" and "not reserved" for operator use,
– All UEs shall treat this cell as candidate during the cell selection and cell reselection procedures.
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
– ….
– UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
….
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
– The UE is not permitted to select/reselect this cell, not even for emergency calls.
– The UE shall select another cell according to the following rule:
-If the cell is a CSG cell:
…
-else
– If the field intraFreqReselection in field cellAccessRelatedInfo in SystemInformationBlockType1 (or SystemInformationBlockType1-NB) message is set to "allowed", the UE may select another cell on the same frequency if re-selection criteria are fulfilled.
– The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
– If the field intraFreqReselection in field cellAccessRelatedInfo in SystemInformationBlockType1 (or SystemInformationBlockType1-NB) message is set to "not allowed" the UE shall not re-select a cell on the same frequency as the barred cell;
– The UE shall exclude the barred cell and the cells on the same frequency as a candidate for cell selection/reselection for 300 seconds.
22.2.6.3 Test description
22.2.6.3.1 Pre-test conditions
System Simulator:
– Three inter-frequency cells as specified in TS 36.508 clause 8.1.4.1.2 are configured broadcasting default NAS parameters as indicated in TS 36.508 Table 8.1.4.2-2, except that TAC values use the codes in TS 36.508 Table 8.1.4.2-6.
– SIB 1-NB of Ncell 3 and Ncell 6 indicate cellBarred-r13 = barred.
- Each cell has only a single PLMN identity.
- All cells are high quality.
- The cell power levels are configured as shown in Table 22.2.6.3.1-1.
- System information combination 3 as defined in TS 36.508 [18] clause 8.1.4.3.1 is used in NB-IoT cells.
Table 22.2.6.3.1-1: Cell power configuration
Parameter |
Unit |
Ncell 1 |
Ncell 3 |
Ncell 6 |
Remarks |
NRS-EPRE |
dBm/15kHz |
-97 |
-82 |
-67 |
S>0 for all cells |
Note 1: The default values (including “not present”) for all other parameters influencing cell reselection are suitable for this test. The values are defined in TS 36.508 clauses 8.1.4.3.2 and 8.1.4.3.3 |
UE:
– The UE is in Automatic PLMN selection mode.
Preamble:
– The UE is in state Registered, Idle Mode (State 3-NB) on Ncell 1 according to [18].
22.2.6.3.2 Test procedure sequence
Table 22.2.6.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts SIB1-NB of Ncell 3 to indicate cellBarred-r13 = notBarred |
– |
– |
– |
– |
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 3? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
3 |
The SS notifies the UE of change of System Information. |
<– |
Paging-NB |
– |
– |
4 |
SS adjusts SIB1-NB of Ncell 3 to indicate cellBarred-r13 = barred. (Ncell 3 and Ncell 6 are now both barred). |
– |
– |
– |
– |
5 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 1? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
6 |
SS adjusts SIB1-NB of both Ncell 3 and Ncell 6: Ncell 3 indicates cellBarred-r13 = notBarred; Ncell 6 indicates cellBarred-r13 = notBarred and cellReservedForOperatorUse-r13 = reserved. |
– |
– |
– |
– |
7 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 3? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
2 |
– |
8 |
The SS notifies the UE of change of System Information. |
<– |
Paging-NB |
– |
– |
9 |
SS adjusts SIB1-NB of Ncell 3 to indicate cellReservedForOperatorUse-r13 = reserved. |
– |
– |
– |
– |
10 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 1? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
2 |
– |
22.2.6.3.3 Specific message contents
Table 22.2.6.3.3-0: Conditions for specific message contents
in Tables 22.2.6.3.3-1, 22.2.6.3.3-2, 22.2.6.3.3-4, 22.2.6.3.3-5 and 22.2.6.3.3-7
Condition |
Explanation |
Ncell 3 |
This condition applies to system information transmitted on Ncell 3. |
Ncell 6 |
This condition applies to system information transmitted on Ncell 6. |
Table 22.2.6.3.3-1: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (pre-test conditions, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse-r13 |
notReserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred-r13 |
barred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
Table 22.2.6.3.3-2: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (step 1, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse-r13 |
notReserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred-r13 |
notBarred |
Ncell 3 |
|
Barred |
Ncell 6 |
||
} |
|||
} |
Table 22.2.6.3.3-3: Paging-NB for Ncell 3 (step 3, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.6.1-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Paging-NB ::= SEQUENCE { |
|||
systemInfoModification-r13 |
True |
Ncell 3 |
|
} |
Table 22.2.6.3.3-4: SystemInformationBlockType1-NB for Ncell 3 (step 4, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse-r13 |
notReserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred-r13 |
Barred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
Table 22.2.6.3.3-5: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (step 6, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1 ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse |
notReserved |
Ncell 3 |
|
reserved |
Ncell 6 |
||
} |
|||
cellBarred |
notBarred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
Table 22.2.6.3.3-6: Paging-NB for Ncell 3 (step 8, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.6.1-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Paging-NB ::= SEQUENCE { |
|||
systemInfoModification-r13 |
True |
Ncell 3 |
|
} |
Table 22.2.6.3.3-7: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (step 9, Table 22.2.6.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1 ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse |
reserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred |
notBarred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
22.2.7 NB-IoT / Cell reselection using cell status and cell reservations / Access control class 11 to 15
22.2.7.1 Test Purpose (TP)
(1)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9 and access classes 11..15 inclusive }
ensure that {
when { a higher ranked cell is found with cell status "barred" }
then { UE does not attempt to reselect to the higher ranked cell }
}
(2)
with { UE camped normally in state E-UTRA RRC_IDLE and UE fitted with a USIM with access class 0..9 and access classes 11..15 inclusive }
ensure that {
when { a higher ranked cell is found "reserved" for Operator use }
then { UE re-selects to the higher ranked cell }
}
22.2.7.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clauses 5.2.4.4 and 5.3.1.
[TS 36.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in subclause 5.2.4.6, for the best cell according to absolute priority reselection criteria specified in subclause 5.2.4.5, the UE shall check if the access is restricted according to the rules in subclause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in subclause 5.3.1, the UE shall not consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
[TS 36.304, clause 5.3.1]
Cell status and cell reservations are indicated in the SystemInformationBlockType1 message (or SystemInformationBlockType1-NB message) [3] by means of two fields:
– cellBarred (IE type: "barred" or "not barred")
In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs
– cellReservedForOperatorUse (IE type: "reserved" or "not reserved")
In case of multiple PLMNs indicated in SIB1, this field is specified per PLMN.
When cell status is indicated as "not barred" and "not reserved" for operator use,
– All UEs shall treat this cell as candidate during the cell selection and cell reselection procedures.
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN,
– UEs assigned to Access Class 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate during the cell selection and reselection procedures if the IE cellReservedForOperatorUse for that PLMN set to “reserved”.
– UEs assigned to an Access Class in the range of 0 to 9, 12 to 14 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN or the selected PLMN.
…
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
– The UE is not permitted to select/reselect this cell, not even for emergency calls.
– The UE shall select another cell according to the following rule:
-If the cell is a CSG cell:
…
-else
– If the field intraFreqReselection in field cellAccessRelatedInfo in SystemInformationBlockType1 (or SystemInformationBlockType1-NB) message is set to "allowed", the UE may select another cell on the same frequency if re-selection criteria are fulfilled.
– The UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
– If the field intraFreqReselection in field cellAccessRelatedInfo in SystemInformationBlockType1 (or SystemInformationBlockType1-NB) message is set to "not allowed" the UE shall not re-select a cell on the same frequency as the barred cell;
– The UE shall exclude the barred cell and the cells on the same frequency as a candidate for cell selection/reselection for 300 seconds.
22.2.7.3 Test description
22.2.7.3.1 Pre-test conditions
System Simulator:
– Three inter-frequency cells as specified in TS 36.508 clause 8.1.4.1.2 are configured broadcasting default NAS parameters as indicated in TS 36.508 Table 8.1.4.2-2, except that TAC values use the codes in TS 36.508 Table 8.1.4.2-6.
– SIB 1-NB of Ncell 3 and Ncell 6 indicate cellBarred-r13 = barred.
- Each cell has only a single PLMN identity.
- All cells are high quality.
- The cell power levels are configured as shown in Table 22.2.7.3.1-1.
- System information combination 3 as defined in TS 36.508 [18] clause 8.1.4.3.1 is used in NB-IoT cells.
Table 22.2.7.3.1-1: Cell power configuration
Parameter |
Unit |
Ncell 1 |
Ncell 3 |
Ncell 6 |
Remarks |
NRS-EPRE |
dBm/15kHz |
-97 |
-82 |
-67 |
S>0 for all cells |
Note 1: The default values (including “not present”) for all other parameters influencing cell reselection are suitable for this test. The values are defined in TS 36.508 clauses 8.1.4.3.2 and 8.1.4.3.3 |
UE:
– The UE is in Automatic PLMN selection mode.
– The UE is equipped with a USIM containing default values (as per TS 36.508) except for those shown in Table 22.2.7.3.1-2.
Table 22.2.7.3.1-2: USIM Configuration
USIM field |
Value |
EFACC |
Type “B” as defined in TS 34.108 clause 8.3.2.15 |
Preamble:
– The UE is in state Registered, Idle Mode (State 3-NB) on Ncell 1 according to [18].
22.2.7.3.2 Test procedure sequence
Table 22.2.7.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts SIB1 of Ncell 3 to indicate cellBarred-r13=notBarred |
– |
– |
– |
– |
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 3? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
3 |
The SS notifies the UE of change of System Information. |
<– |
Paging-NB |
– |
– |
4 |
SS adjusts SIB1 of Ncell 3 to indicate cellBarred-r13=barred. (Ncell 3 and Ncell 6 are now both barred). |
||||
5 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 1? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
6 |
SS adjusts SIB1 of both Ncell 3 and Ncell 6: Ncell 3 indicates cellBarred-r13=notBarred; Ncell 6 indicates cellBarred-r13=notBarred and cellReservedForOperatorUse-r13 = reserved |
– |
– |
– |
– |
7 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on NB-IoT Ncell 6? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
2 |
– |
22.2.7.3.3 Specific message contents
Table 22.2.7.3.3-0: Conditions for specific message contents
in Tables 22.2.7.3.3-1, 22.2.7.3.3-2, 22.2.7.3.3-3, 22.2.7.3.3-4 and22.2.7.3.3-5
Condition |
Explanation |
Ncell 3 |
This condition applies to system information transmitted on Ncell 3. |
Ncell 6 |
This condition applies to system information transmitted on Ncell 6. |
Table 22.2.7.3.3-1: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (pre-test conditions, Table 22.2.7.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse-r13 |
notReserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred-r13 |
barred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
Table 22.2.7.3.3-2: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (step 1, Table 22.2.7.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse-r13 |
notReserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred-r13 |
notBarred |
Ncell 3 |
|
Barred |
Ncell 6 |
||
} |
|||
} |
Table 22.2.7.3.3-3: Paging-NB for Ncell 3 (step 3, Table 22.2.7.3.2-1)
Derivation Path: 36.508 clause 8.1.6.1-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
Paging-NB ::= SEQUENCE { |
|||
systemInfoModification-r13 |
True |
Ncell 3 |
|
} |
Table 22.2.7.3.3-4: SystemInformationBlockType1-NB for Ncell 3 (step 4, Table 22.2.7.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse-r13 |
notReserved |
Ncell 3 Ncell 6 |
|
} |
|||
cellBarred-r13 |
Barred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
Table 22.2.7.3.3-5: SystemInformationBlockType1-NB for Ncell 3 and Ncell 6 (step 6, Table 22.2.7.3.2-1)
Derivation Path: 36.508 clause 8.1.4.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1 ::= SEQUENCE { |
|||
cellAccessRelatedInfo SEQUENCE { |
|||
PLMN-IdentityList-NB-r13 ::= |
|||
PLMN-IdentityInfo-NB-r13 ::= SEQUENCE { |
1 entry |
||
cellReservedForOperatorUse |
notReserved |
Ncell 3 |
|
reserved |
Ncell 6 |
||
} |
|||
cellBarred |
notBarred |
Ncell 3 Ncell 6 |
|
} |
|||
} |
Table 22.2.7.3.3-6: Void
22.2.8 NB-IoT / Cell reselection in shared network environment
22.2.8.1 Test Purpose (TP)
(1)
with { the UE is in RRC_Idle and registered on the HPLMN }
ensure that {
when { a cell of a different PLMN but shared with the HPLMN becomes highest ranked cell }
then { the UE reselects the cell shared with the HPLMN }
22.2.8.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 5.2.4.2 and TS 23.122 clause 4.4.3. Unless otherwise stated these are Rel-13 requirements.
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise and for NB-IoT this equals to Qoffsetfrequency. |
Qoffsettemp |
Offset temporarily applied to a cell as specified in [3] |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2 (5.2.3.2a for NB-IoT), but may exclude all CSG cells that are known by the UE not to be CSG member cells.
The cells shall be ranked according to the R criteria specified above, deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better ranked than the serving cell during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 23.122, clause 4.4.3]
…
When the MS reselects to a cell in a shared network, and the cell is a suitable cell for multiple PLMN identities received on the BCCH or on the EC-BCCH the AS indicates these multiple PLMN identities to the NAS according to 3GPP TS 44.018 [34], 3GPP TS 44.060 [39], 3GPP TS 25.304 [32] and 3GPP TS 36.304 [43]. The MS shall choose one of these PLMNs. If the registered PLMN is available among these PLMNs, the MS shall not choose a different PLMN.
…
22.2.8.3 Test description
22.2.8.3.1 Pre-test conditions
System Simulator:
– Ncell 1 (HPLMN)
– Ncell 2 (primary PLMN: same MCC like HPLMN but different MNC, secondary PLMN: HPLMN)
– System information combination 2 as defined in TS 36.508 [18] clause 8.1.4.3.1.
UE:
None.
Preamble:
– UE is in state 3-NB Idle mode on Ncell 1 according to TS 36.508 [18].
22.2.8.3.2 Test procedure sequence
Table 22.2.8.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 22.2.8.3.2-1: Time instances of cell power level and parameter change
Parameter |
Unit |
Ncell 1 |
Ncell 2 |
Remark |
|
T0 |
Cell-specific NRS EPRE |
dBm/15kHz |
-85 |
Off |
|
T1 |
Cell-specific NRS EPRE |
dBm/15kHz |
-85 |
-73 |
The power level values are assigned to satisfy SrxlevCell 2 > SrxlevCell 1 |
Table 22.2.8.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes Ncell 1 and Ncell 2 level according to the row "T1" in table 22.2.8.3.2-1. |
– |
– |
– |
– |
2 |
Check: Does the UE transmit an RRCConnectionRequest-NB on Ncell 2? |
–> |
RRCConnectionRequest-NB |
1 |
P |
3 |
The SS transmits an RRCConnectionSetup-NB |
<– |
RRCConnectionSetup-NB |
– |
– |
4 |
Check: Does the UE transmit an RRCConnectionSetupComplete-NB message indicating the HPLMN (second PLMN in the list)? Note: this message contains an TRACKING AREA UPDATE REQUEST message according to default message contents. |
–> |
RRCConnectionSetupComplete-NB |
1 |
P |
5 – 7 |
Steps 4 to 6 of the generic test procedure in TS 36.508 subclause 8.1.5A.5 are performed. NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
– |
– |
22.2.8.3.3 Specific message contents
Table 22.2.8.3.3-1: SystemInformationBlockType1-NB (Ncell 1, all steps, Table 22.2.8.3.2-2)
Derivation path: 36.508 Table 8.1.4.3.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
cellAccessRelatedInfo-r13 SEQUENCE { |
|||
plmn-IdentityList-r13 SEQUENCE (SIZE (1..6)) OF SEQUENCE { |
|||
plmn-Identity-r13[1] |
Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card |
||
} |
|||
} |
|||
} |
Table 22.2.8.3.3-2: SystemInformationBlockType1-NB (Ncell 2, all steps, Table 22.2.8.3.2-2)
Derivation path: 36.508 Table 8.1.4.3.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
CellAccessRelatedInfo-r13 SEQUENCE { |
|||
plmn-IdentityList-r13 SEQUENCE (SIZE (1..6)) OF SEQUENCE { |
|||
plmn-Identity-r13[1] |
Set to the same Mobile Country Code stored in EFIMSI on the test USIM, MNC=02 |
||
plmn-Identity-r13[2] |
Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card |
This is the same PLMN as Ncell 1 |
|
} |
|||
} |
|||
} |
Table 22.2.8.3.3-3: RRCConnectionSetupComplete-NB (step 4, Table 22.2.8.3.2-2)
Derivation Path: 36.508, Table 8.1.6.1-15 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCConnectionSetupComplete-NB ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcConnectionSetupComplete-r13 SEQUENCE { |
|||
selectedPLMN-Identity |
2 |
HPLMN |
|
} |
|||
} |
|||
} |
22.2.9 NB-IoT / Inter-frequency cell reselection
22.2.9.1 Test Purpose (TP)
(1)
with { UE in RRC_IDLE state }
ensure that {
when { UE detects both intra-frequency and equal priority inter-frequency neighbour cells and the inter-frequency cell is the highest ranked cell }
then { UE reselects the inter-frequency cell }
}
(2)
with { UE in RRC_IDLE state }
ensure that {
when { SnonintrasearchP is non-zero in system information }
then { UE perform measurement and reselects the cell which belong to the equal priority inter-frequency cell upon Srxlev < SnonintrasearchP }
}
(3)
Void
22.2.9.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause5.2.4.2a, 5.2.4.5 and 5.2.4.6. Unless otherwise stated these are Rel-13 requirements.
[TS 36.304, clause 5.2.4.2a]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
– If the serving cell fulfils Srxlev > SIntraSearchP, the UE may choose not to perform intra-frequency measurements.
– Otherwise, the UE shall perform intra-frequency measurements.
– The UE shall apply the following rules for NB-IoT inter-frequencies which are indicated in system information:
– If the serving cell fulfils Srxlev > SnonIntraSearchP, the UE may choose not to perform inter-frequency measurements.
– Otherwise, the UE shall perform inter-frequency measurements.
[TS 36.304, clause 5.2.4.5]
For NB-IoT inter-frequency cell reselection shall be based on ranking as defined in sub-clause 5.2.4.6.
…
Cell reselection to a cell on an equal priority E-UTRAN frequency shall be based on ranking for Intra-frequency cell reselection as defined in sub-clause 5.2.4.6.
…
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise and for NB-IoT this equals to Qoffsetfrequency. |
Qoffsettemp |
Offset temporarily applied to a cell as specified in [3] |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2 (5.2.3.2a for NB-IoT), but may exclude all CSG cells that are known by the UE not to be CSG member cells.
The cells shall be ranked according to the R criteria specified above, deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better ranked than the serving cell during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
22.2.9.3 Test description
22.2.9.3.1 Pre-test conditions
System Simulator:
– Ncell 1, Ncell 2 and Ncell 3 have different tracking areas.
– System information combination 3 as defined in TS 36.508 [18] clause 8.1.4.3.1.
UE:
None.
Preamble:
– UE is in state 3-NB Idle mode on Ncell 1 according to TS 36.508 [18].
22.2.9.3.2 Test procedure sequence
Table 22.2.9.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The configuration marked "T1", "T2" and "T3" is applied at the point indicated in the Main behaviour description in Table 22.2.9.3.2-2.
Table 22.2.9.3.2-1: Time instances of cell power level and parameter changes
Parameter |
Unit |
Ncell 1 |
Ncell 2 |
Ncell 3 |
Remark |
|
T0 |
Cell-specific NRS EPRE |
dBm/15kHz |
-91 |
-95 |
-95 |
The power level values are set so that Ncell1 > Ncell2 and Ncell3. |
T1 |
Cell-specific NRS EPRE |
dBm/15kHz |
-91 |
-85 |
-73 |
The power level values are set so that RNcell1 < RNcell2 < RNcell3. |
T2 |
Cell-specific NRS EPRE |
dBm/15kHz |
-79 |
Off |
-95 |
Srxlev of Ncell 3 is less than SnonintrasearchP |
Table 22.2.9.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0 |
The SS updates the SIB3-NB for Ncell 3 as per Table 22.2.9.3.3-5 specified below. |
– |
|||
0A |
The SS changes the cells power level setting according to the row "T0" in table 22.2.9.3.2-1 |
||||
0B |
SS waits for 60s. |
||||
1 |
The SS changes the cells power level setting according to the row "T1" in table 22.2.9.3.2-1. |
– |
– |
– |
– |
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on Ncell 3? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
3 |
Void |
– |
– |
– |
– |
3A |
The SS updates the SIB3-NB for Ncell 3 as per Table 22.2.9.3.3-1 specified below. |
– |
– |
– |
– |
4 |
The SS transmits a Paging-NB message on Ncell 3 to notify the UE of the system information change. The systemInfoValueTag-r13 / systemInfoValueTag-r15 in the MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is increased. |
<– |
Paging-NB |
– |
– |
5 |
Void |
– |
– |
– |
– |
6 |
The SS re-adjusts the cell-specific reference signal levels according to row "T2" in table 22.2.9.3.2-1. |
||||
7 |
Check: Does the test result of generic procedure 8.1.5A.5 indicate that the UE is camped on Ncell 1? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
2 |
P |
22.2.9.3.3 Specific message contents
Table 22.2.9.3.3-1: SystemInformationBlockType3-NB for Ncells 1 and 3 (step 4, table 22.2.9.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-2 |
||
Information Element |
Value/remark |
Comment |
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
||
cellReselectionServingFreqInfo-r13 SEQUENCE { |
||
s-NonIntraSearch-r13 |
8 (16 dB) |
|
} |
||
} |
Table 22.2.9.3.3-2: MasterInformationBlock-NB for Ncell 1 and 3 (step 4, Table 22.2.9.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2-1 |
||
Information Element |
Value/remark |
Comment |
MasterInformationBlock-NB ::= SEQUENCE { |
||
systemInfoValueTag-r13 |
The value is increased by 1 |
|
} |
Table 22.2.9.3.3-2A: MasterInformationBlock-TDD-NB for Ncell 1 and 3 (step 4, Table 22.2.9.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2-1A |
||
Information Element |
Value/remark |
Comment |
MasterInformationBlock-TDD-NB ::= SEQUENCE { |
||
systemInfoValueTag-r15 |
The value is increased by 1 |
|
} |
Table 22.2.9.3.3-3: SystemInformationBlockType5-NB for Ncell 3 (step 4, Table 22.2.9.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-4 |
||
Information Element |
Value/Remark |
Comment |
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
||
interFreqCarrierFreqList-r13 SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
1 entry |
|
dl-CarrierFreq-r13[1] |
EARFCN of Ncell 1 |
|
} |
||
} |
Table 22.2.9.3.3-4: Paging-NB (step 4, Table 22.2.9.3.2-2)
Derivation path: 36.508 Table 8.1.6.1-2 |
||
Information Element |
Value/Remark |
Comment |
Paging-NB ::= SEQUENCE { |
||
PagingRecordList-r13 |
Not present |
|
systemInfoModification-r13 |
true |
|
nonCriticalExtension SEQUENCE {} |
Not present |
|
} |
Table 22.2.9.3.3-5: SystemInformationBlockType3-NB for Ncell 3 (step 0, Table 22.2.9.3.2-2)
Derivation path: 36.508 table 8.1.4.3.3-2 |
||
Information Element |
Value/remark |
Comment |
SystemInformationBlockType3-NB-r13 ::= SEQUENCE { |
||
cellReselectionServingFreqInfo-r13 SEQUENCE { |
||
s-NonIntraSearch-r13 |
0 |
|
} |
||
} |
22.2.10 NB-IoT / Cell reselection / MFBI
22.2.10.1 Test Purpose (TP)
(1)
with { UE in RRC_IDLE state }
ensure that {
when { an equal priority Intra-frequency neighbouring cell which has been included in the multiBandInfoList provided by the serving cell becomes available, and, is better ranked than the serving cell during a time interval TreselectionRAT, and, more than 1 second has elapsed since the UE camped on the current serving cell }
then { the UE reselects the new cell }
}
(2)
with { UE in RRC_IDLE state }
ensure that {
when { an equal priority Inter-frequency neighbouring cell which has been included in the multiBandInfoList provided by the serving cell becomes available, and, is better ranked than the serving cell during a time interval TreselectionRAT, and, more than 1 second has elapsed since the UE camped on the current serving cell }
then { the UE reselects the new cell }
}
22.2.10.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 5.2.4.2a and 5.2.4.6, TS 36.331, clause 5.2.2.7, 5.2.2.12 and 6.7.3.1.
[TS 36.304, clause 5.2.4.2a]
When evaluating Srxlev and Squal of non-serving cells for reselection purposes, the UE shall use parameters provided by the serving cell.
Following rules are used by the UE to limit needed measurements:
– If the serving cell fulfils Srxlev > SIntraSearchP, the UE may choose not to perform intra-frequency measurements
– Otherwise, the UE shall perform intra-frequency measurements.
– The UE shall apply the following rules for NB-IoT inter-frequencies which are indicated in system information:
– If the serving cell fulfils Srxlev > SnonIntraSearchP, the UE may choose not to perform inter-frequency measurements.
– Otherwise, the UE shall perform inter-frequency measurements.
[TS 36.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Except for NB-IoT, equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency. For NB-IoT equals to QoffsetDedicatedfrequency for any frequency other than the frequency of the dedicated frequency offset, if QoffsetDedicatedfrequency is valid, otherwise this equals to Qoffsetfrequency (if QoffsetDedicatedfrequency is valid Qoffsetfrequency is not used). |
Qoffsettemp |
Offset temporarily applied to a cell as specified in [3] |
QoffsetSCPTM |
Offset temporarily applied to an SC-PTM frequency as specified below. The offset is applied to all cells on the SC-PTM frequency. If QoffsetSCPTM is valid, Qoffset for inter-frequency neighbour cells is not used. |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2 (5.2.3.2a for NB-IoT), but may exclude all CSG cells that are known by the UE not to be CSG member cells.
The cells shall be ranked according to the R criteria specified above, deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If a cell is ranked as the best cell the UE shall perform cell reselection to that cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better ranked than the serving cell during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 36.331, clause 5.2.2.7]
Upon receiving the SystemInformationBlockType1-NB, the UE shall:
1> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE; or
1> if one or more of the frequency bands indicated in the multiBandInfoList are part of the frequency bands supported by the UE:
2> forward the cellIdentity to upper layers;
2> forward the trackingAreaCode to upper layers;
2> if attachWithoutPDN-Connectivity is received for the selected PLMN:
3> forward the attachWithoutPDN-Connectivity to upper layers;
2> else
3> indicate to upper layers that attachWithoutPDN-Connectivity is not present;
2> if, for the frequency band selected by the UE (from freqBandIndicator or multiBandInfoList), the freqBandInfo is present and the UE capable of multiNS-Pmax supports at least one additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo:
3> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-PmaxList within freqBandInfo;
3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NS-PmaxList:
4> apply the additionalPmax;
3> else:
4> apply the p-Max;
2> else:
3> apply the additionalSpectrumEmission in SystemInformationBlockType2-NB and the p-Max;
1> else:
2> consider the cell as barred in accordance with TS 36.304 [4]; and
2> perform barring as if intraFreqReselection is set to notAllowed.
[TS 36.331, clause 5.2.2.12]
Upon receiving SystemInformationBlockType5-NB, the UE shall:
1> if in RRC_IDLE, or in RRC_CONNECTED while T311 is running:
2> if, for the frequency band selected by the UE (from multiBandInfoList) to represent a non-serving NB-IoT carrier frequency, the freqBandInfo is present and the UE capable of multiNS-Pmax supports at least one additionalSpectrumEmission in the NS-PmaxList within the freqBandInfo:
3> apply the first listed additionalSpectrumEmission which it supports among the values included in NS-PmaxList within freqBandInfo;
3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within NS-PmaxList:
4> apply the additionalPmax;
3> else:
4> apply the p-Max;
2> else:
3> apply the p-Max;
[TS 36.331, clause 6.7.3.1]
SystemInformationBlockType2-NB
The IE SystemInformationBlockType2-NB contains radio resource configuration information that is common for all UEs.
NOTE: UE timers and constants related to functionality for which parameters are provided in another SIB are included in the corresponding SIB.
…
SystemInformationBlockType2-NB field descriptions |
---|
multiBandInfoList A list of additionalSpectrumEmission i.e. one for each additional frequency band included in multiBandInfoList in SystemInformationBlockType1-NB, listed in the same order. |
…
SystemInformationBlockType5-NB
The IE SystemInformationBlockType5-NB contains information relevant only for inter-frequency cell re-selection i.e. information about other NB-IoT frequencies and inter-frequency neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency.
…
SystemInformationBlockType5-NB field descriptions |
---|
multiBandInfoList Indicates the list of frequency bands, with the associated additionalPmax and additionalSpectrumEmission values as defined in TS 36.101 [42, 6.2.4], in addition to the band represented by dl-CarrierFreq for which cell reselection parameters are common. |
22.2.10.3 Test description
22.2.10.3.1 Pre-test conditions
System Simulator:
– Ncell 1, Ncell 3, and Ncell 11 have different tracking areas according to TS 36.508 [18] Table 8.1.4.2-1A and are MFBI capable cells.
– Ncell 1 and Ncell 11 belong to the absolute centre frequency which overlaps between bands controlled by IXITs
px_MFBI_FrequencyBand and px_OverlappingNotSupportedFrequencyBandMFBI.
– Ncell 3 belongs to another absolute centre frequency which again overlaps between bands controlled by IXITs
px_MFBI_FrequencyBand and px_OverlappingNotSupportedFrequencyBandMFBI.
– System information combination 3 as defined in TS 36.508 [18] clause 8.1.4.3.1.1 is used in NB-IoT inter-frequency multi cell scenario.
UE:
– UE does not support the px_OverlappingNotSupportedFrequencyBand_MFBI band.
Preamble:
– The UE is in state Registered, Idle mode (State 3-NB) on Ncell 1 (serving cell) according to TS 36.508 [18] clause 8.1.5.1
22.2.10.3.2 Test procedure sequence
Table 22.2.10.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at
various time instants of the test execution. The configurations marked "T1" and "T2" is applied at the point indicated in the Main
behaviour description in Table 22.2.10.3.2-2.
Table 22.2.10.3.2-1: Cell configuration changes over time
Parameter |
Unit |
Ncell 1 |
Ncell 11 |
Ncell 3 |
Remarks |
|
T1 |
NRS EPRE |
dBm/15kHz |
-85 |
-79 |
“Off” |
The power level values are set so that Ncell 1 < Ncell 11. (NOTE 1) |
T2 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
-73 |
The power level values are set so that Ncell 1 < Ncell 11. (NOTE 1) |
Note 1: Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1. |
Table 22.2.10.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0 |
Wait 1 second. (to ensure that 1 second has elapsed since the UE camped on the current serving cell) |
– |
– |
– |
– |
1 |
The SS changes the cells power level setting according to the row "T1" in table 22.2.10.3.2- 1. |
– |
– |
– |
– |
2 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on E-UTRAN Ncell 11? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
1 |
– |
3 |
The SS changes the cells power level setting according to the row "T2" in table 22.2.10.3.2- 1. |
– |
– |
– |
– |
4 |
Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.5 indicate that the UE is camped on E-UTRAN Ncell 3? NOTE: The UE performs a TAU procedure and the RRC connection is released. |
– |
– |
2 |
22.2.10.3.3 Specific message contents
Table 22.2.10.3.3-0: SystemInformationBlockType1-NB for Ncell 1, Ncell 3 and Ncell 11 (preamble and all steps,
Table 22.2.10.3.2-2)
Condition |
Explanation |
NS_04 |
When using the NS_04 frequency table variants in TS 36.508 subclause 8.1.3.1 |
Table 22.2.10.3.3-1: SystemInformationBlockType1-NB for Ncell 1, Ncell 3 and Ncell 11 (preamble and all steps,
Table 22.2.10.3.2-2)
Derivation Path: 36.508 table 8.1.4.3.2.-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
freqBandIndicator-r13 |
FreqBandIndicator-NB-r13 An overlapping not |
Ncell 1 Ncell 3 Ncell 11 |
|
multiBandInfoList-r13 SEQUENCE { |
|||
freqBandIndicator-r13 |
An overlapping Band |
Ncell 1 Ncell 3 Ncell 11 |
|
freqBandInfo-r13 SEQUENCE{ |
|||
NS-PmaxList-NB-r13 SEQUENCE{ |
|||
additionalPmax-r13 |
Not Present |
Ncell 1 Ncell 3 Ncell 11 |
|
additionalSpectrumEmission-r13 |
1 (NS_01) |
A-MPR doesn’t |
|
4 (NS_04) |
NS_04 |
||
} |
|||
} |
|||
} |
|||
} |
Table 22.2.10.3.3-2: SystemInformationBlockType5-NB for Ncell 1, Ncell 3 and Ncell 11 (preamble)
Derivation Path: 36.508 table 8.1.4.3.3-4 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType5-NB-r13 ::= SEQUENCE { |
|||
interFreqCarrierFreqList-r13 SEQUENCE { |
The same number of entries as the configured inter-freq carriers. For Signalling test cases, see clause 8.3.2.3. |
n denotes the index of the entry |
|
dl-CarrierFreq-r13[n] |
Downlink EARFCN under test |
||
multiBandInfoList-r13 SEQUENCE { |
|||
freqBandIndicator-r13 |
An overlapping Band under test (px_MFBI_FrequencyBand). |
Ncell 1 Ncell 3 Ncell 11 |
|
freqBandInfo-r13 SEQUENCE{ |
|||
NS-PmaxList-NB-r13 SEQUENCE{ |
|||
additionalPmax-r13 |
Not Present |
Ncell 1 Ncell 3 Ncell 11 |
|
additionalSpectrumEmission-r13 |
1 (NS_01) |
A-MPR doesn’t |
|
4 (NS_04) |
NS_04 |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
22.2.11 Void
22.2.12 Void
22.2.13 NB-IoT / NTN / Multi-TAC
22.2.13.1 Test Purpose (TP)
(1)
with { UE in EMM-REGISTERED/RRC-IDLE and UE finds a cell which provides access by NB-IoT RAT }
ensure that {
when { systemInformationBlockType1-NB broadcast more than one TAC per PLMN }
then { UE forwards the trackingAreaList to upper layers for mobility management procedure }
}
22.2.13.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 36.331 clauses 5.2.2.7 and 6.7.2. Unless otherwise stated these are Rel-17 requirements.
[TS 36.331, clause 5.2.2.7]
Upon receiving the SystemInformationBlockType1-NB, the UE shall:
…
1> else:
2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, trackingAreaList and cellIdentity for the cell as received in the cellAccessRelatedInfo;
1> if the frequency band indicated in the freqBandIndicator is part of the frequency bands supported by the UE; or
1> if one or more of the frequency bands indicated in the multiBandInfoList are part of the frequency bands supported by the UE:
2> forward the cellIdentity to upper layers;
2> forward the trackingAreaCode to upper layers;
2> forward the trackingAreaList to upper layers, if present;
[TS 36.331, clause 6.7.2]
trackingAreaList A list of tracking area codes for the PLMN listed. For the first entry in plmn-IdentityList-v1700: If this field is present, the list of tracking area codes include the tracking area code in trackingAreaCode-r13 and the tracking area codes in trackingAreaList. If this field is absent, only trackingAreaCode-r13 applies. For other entries in plmn-IdentityList-v1700: If this field is present, the list of tracking area codes include the tracking area codes in trackingAreaList. If this field is absent, the list of tracking area codes of the preceding entry in plmn-IdentityList-v1700 applies. The total number of signalled tracking area codes across all PLMNs cannot be more than maxTAC-NB-r17. |
22.2.13.3 Test description
22.2.13.3.1 Pre-test conditions
System Simulator:
– Ncell 1 and Ncell 11 as specified in TS 36.508 clause 8.1.4.1.2 is configured.
– System information combination 9 as defined in TS 36.508 [18] clause 8.1.4.3.1.1 is used.
UE:
– The UE is in Automatic PLMN selection mode.
– The UE’s positioning engine (e.g., standalone GNSS receiver) should be enabled to allow it to acquire the position. This could be done by use of AT command, such as AT+CPOS or other commands. Otherwise, or in addition any other suitable method may also be used, e.g., GNSS simulator.
Preamble:
– The UE is in State 3-NB Registered, Idle Mode on Ncell 1 according to TS 36.508 [18].
22.2.13.3.2 Test procedure sequence
Table 22.2.13.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions. Subsequent configurations marked “T1” is applied at the points indicated in the Main behaviour description in Table 22.2.13.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 36.508 [18].
Table 22.2.13.3.2-1: Ncell configuration changes over time
Parameter |
Unit |
Ncell 1 |
Ncell 11 |
Remarks |
|
T0 |
NRS EPRE |
dBm/15kHz |
-85 |
“Off” |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
T1 |
NRS EPRE |
dBm/15kHz |
“Off” |
-85 |
Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1 |
Table 22.2.13.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts Ncell levels according to row T1 of table 22.2.13.3.2-1. |
– |
– |
– |
– |
2 |
Check: Does the UE send an RRCConnectionRequest-NB on Ncell 11 within 3 minutes? |
–> |
RRCConnectionRequest-NB |
1 |
F |
22.2.13.3.3 Specific message contents
Table 22.2.13.3.3-1: SystemInformationBlockType1-NB for Ncell 1 (preamble and all steps, table 22.2.13.3.2-2)
Derivation Path: TS 36.508 [18], Table 8.1.4.3.2-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SystemInformationBlockType1-NB ::= SEQUENCE { |
|||
nonCriticalExtension SEQUENCE { |
1350 |
||
nonCriticalExtension SEQUENCE { |
1430 |
||
nonCriticalExtension SEQUENCE { |
1450 |
||
nonCriticalExtension SEQUENCE { |
1530 |
||
nonCriticalExtension SEQUENCE { |
1610 |
||
nonCriticalExtension SEQUENCE { |
1700 |
||
cellAccessRelatedInfo-NTN-r17 SEQUENCE { |
|||
cellBarred-NTN-r17 |
notBarred |
||
plmn-IdentityList-v1700 SEQUENCE (SIZE (1..maxPLMN-r11)) OF PLMN-IdentityInfo-NB-v1700 SEQUENCE |
1 entry |
||
PLMN-IdentityInfo-NB-v1700[1] SEQUENCE { |
Entry 1 |
||
trackingAreaList-r17 SEQUENCE (SIZE (1..maxTAC-NB-r17)) OF TrackingAreaCode SEQUENCE { |
1 entry |
||
TrackingAreaCode[1] |
TAC-2 |
Entry 1 |
|
} |
|||
} |
|||
} |
|||
} |
|||
nonCriticalExtension |
Not present |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |