6.4 UE Procedures in RRC_INACTIVE state
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
6.4.1 NG-RAN Only PLMN Selection in RRC_INACTIVE state
6.4.1.1 PLMN Selection/Higher priority/HPLMN in Automatic PLMN Selection Mode
6.4.1.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_INACTIVE state on an NG-RAN VPLMN cell }
ensure that {
when { UE performs PLMN Selection to a PLMN that is equivalent PLMN of the registered PLMN }
then { UE remains in RRC_INACTIVE state after moving to the Equivalent PLMN cell. }
}
(2)
with { UE in NR RRC_INACTIVE state on an NG-RAN VPLMN cell and cells of a higher priority NG-RAN PLMN available }
ensure that {
when { Higher priority PLMN search timer T expires }
then { UE selects the higher priority PLMN cell, moves to RRC_IDLE and attempts Registration on the selected cell. }
}
6.4.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.4.3.3, TS 38.304 clauses 4.1 and clauses 4.2 and TS 24.501 clauses 5.3.1.4. Unless otherwise stated these are Rel-15 requirements.
[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 radio capabilities supported by the MS:
– For an MS that does not support any of the following: EC-GSM-IoT, 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, 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.
– For an MS that supports both:
a) any of the following or a combination of: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]); and
b) any access technology other than the following: EC-GSM-IoT, Category M1 or Category NB1 (as defined in 3GPP TS 36.306 [54]),
then T is interpreted depending on the access technology in use as specified below:
1) if the MS is using any of the following at the time of starting timer T: EC-GSM-IoT, 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; and
2) if the MS is not using any of the following at the time of starting timer T: EC-GSM-IoT, 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 use
for T.
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 does not stop timer T, as described in 3GPP TS 24.008 [23] and 3GPP TS 24.301 [23A], when it activates power saving mode (PSM) (see 3GPP TS 23.682 [27A]).
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, and not while the MS is attached for emergency bearer services, is registered for emergency services, has a PDU session for emergency services or has a PDN connection for emergency bearer services;
b) The MS shall make the first attempt after a period of at least 2 minutes and at most T minutes:
– only after switch on if Fast First Higher Priority PLMN search is disabled; or
– after switch on or upon selecting a VPLMN if Fast First Higher Priority PLMN search is enabled.
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;
d1) Periodic attempts may be postponed while the MS is in power saving mode (PSM) (see 3GPP TS 23.682 [27A]).
d2) Periodic attempts may be postponed while the MS is receiving eMBMS transport service in idle mode (see 3GPP TS 23.246 [68]).
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) Only the priority levels of Equivalent PLMNs of the same country as the current serving VPLMN, as defined in Annex B, shall be taken into account to compare with the priority level of a selected PLMN.
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.
[TS 38.304, clause 4.1]
The RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes:
– PLMN selection;
– Cell selection and reselection;
– Location registration and RNA update.
PLMN selection, cell reselection procedures, and location registration are common for both RRC_IDLE state and RRC_INACTIVE state. RNA update is only applicable for RRC_INACTIVE state. When UE selects a new PLMN, UE transitions from RRC_INACTIVE to RRC_IDLE, as specified in TS 24.501 [14].
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, as specified in TS 23.122 [9]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use for cell selection and cell reselection.
With cell selection, the UE searches for a suitable cell of the selected PLMN, chooses that cell to provide available services, and monitors its control channel. This procedure is defined as "camping on the cell".
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of the chosen cell. As an outcome of a successful Location Registration, the selected PLMN then becomes the registered PLMN, as specified in TS 23.122 [9].
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRC_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed.
If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in TS 23.122 [9] and search for a suitable cell if another PLMN has been selected by NAS.
If the UE loses coverage of the registered PLMN, either a new PLMN is selected automatically (automatic mode), or an indication of available PLMNs is given to the user so that a manual selection can be performed (manual mode).
Registration is not performed by UEs only capable of services that need no registration.
The purpose of camping on a cell in RRC_IDLE state and RRC_INACTIVE state is fourfold:
a) It enables the UE to receive system information from the PLMN.
b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of tracking areas (in RRC_IDLE state) or RNA (in RRC_INACTIVE state) in which the UE is camped. It can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The UE will then receive the paging message and can respond.
d) It enables the UE to receive ETWS and CMAS notifications.
When the UE is in RRC_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all idle mode tasks.
[TS 38.304, clause 4.2]
Table 4.2-1 presents the functional division between UE non-access stratum (NAS) and UE access stratum (AS) in RRC_IDLE state and RRC_INACTIVE states. The NAS part is specified in TS 23.122 [9] and the AS part in the present document.
Table 4.2-1: Functional division between AS and NAS in RRC_IDLE state and RRC_INACTIVE state
RRC_IDLE and RRC_INACTIVE state Process |
UE Non-Access Stratum |
UE Access Stratum |
---|---|---|
PLMN Selection |
Maintain a list of PLMNs in priority order according to TS 23.122 [9]. Select a PLMN using automatic or manual mode as specified in TS 23.122 [9] and request AS to select a cell belonging to this PLMN. For each PLMN, associated RAT(s) may be set. Evaluate reports of available PLMNs from AS for PLMN selection. Maintain a list of equivalent PLMN identities. |
Search for available PLMNs. If associated RAT(s) is (are) set for the PLMN, search in this (these) RAT(s) and other RAT(s) for that PLMN as specified in TS 23.122 [9]. Perform measurements to support PLMN selection. Synchronise to a broadcast channel to identify found PLMNs. Report available PLMNs with associated RAT(s) to NAS on request from NAS or autonomously. |
Cell Selection |
Control cell selection for example by indicating RAT(s) associated with the selected PLMN to be used initially in the search of a cell in the cell selection. Maintain a list of "Forbidden Tracking Areas" and provide the list to AS. |
Perform measurements needed to support cell selection. Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS. Search for a suitable cell. The cells broadcast one or more ‘PLMN identity’ in the system information. Respond to NAS whether such cell is found or not. If associated RATs is (are) set for the PLMN, perform the search in this (these) RAT(s) and other RATs for that PLMN as specified in TS 23.122 [9]. If a cell is found which satisfies cell selection criteria, camp on that cell. |
Cell Reselection |
Maintain a list of equivalent PLMN identities and provide the list to AS. Maintain a list of "Forbidden Tracking Areas" and provide the list to AS. |
Perform measurements needed to support cell reselection. Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS. Change cell if a more suitable cell is found. |
Location registration |
Register the UE as active after power on. Register the UE’s presence in a registration area, for instance regularly or when entering a new tracking area. Deregister UE when shutting down. Maintain a list of "Forbidden Tracking Areas". |
Report registration area information to NAS. |
RAN Notification Area Update |
Not applicable. |
Register the UE’s presence in a RAN-based notification area (RNA), periodically or when entering a new RNA. |
[TS 24.501, clause 5.3.1.4]
This subclause is only applicable for UE’s 5GMM mode over 3GPP access.
The UE is in 5GMM-CONNECTED mode with RRC inactive indication when the UE is in:
a) 5GMM-CONNECTED mode over 3GPP access at the NAS layer; and
b) RRC_INACTIVE state at the AS layer (see 3GPP TS 38.300 [27]).
Unless stated otherwise, the UE behaviour in 5GMM-CONNECTED mode with RRC inactive indication follows the UE behaviour in 5GMM-CONNECTED over 3GPP access, except that:
a) the UE shall apply the mobility restrictions; and
b) the UE shall perform the PLMN selection procedures as in 5GMM-IDLE mode over 3GPP access.
The UE shall transition from 5GMM-CONNECTED mode over 3GPP access to 5GMM-CONNECTED mode with RRC inactive indication upon receiving an indication from the lower layers that the UE has transitioned to RRC_INACTIVE state.
…
The UE shall trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon selection of a PLMN that is not an equivalent PLMN to the registered PLMN. The UE shall not trigger a transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode upon entering a new PLMN which is in the list of equivalent PLMNs.
6.4.1.1.3 Test description
6.4.1.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 12, NR Cell 13 and NR Cell 1 are configured according to TS 38.508-1 [4], Table 4.4.2-3.
– The PLMNs are identified in the test by the identifiers in Table 6.4.1.1.3.1-1 and the PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1..
Table 6.4.1.1.3.1–1: PLMN identifiers
NR Cell |
PLMN name |
12 |
PLMN15 |
13 |
PLMN16 |
1 |
PLMN1 |
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cells.
UE:
– The UE is in Automatic PLMN selection mode.
– USIM configuration as defined in TS 38.508-1 [4] Table 6.4.1-1 will be loaded. The high priority PLMN search timer T defined by EFHPPLMN is 6min.
Preamble:
– The UE is in state Switched OFF (state 0-A) according to TS 38.508-1 [4].
6.4.1.1.3.2 Test procedure sequence
Table 6.4.1.1.3.2-1 for FR1 and Table 6.4.1.1.3.2-2 for FR2 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 initial conditions after preamble, while column marked "T1"is to be applied subsequently in the Main behaviour. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 6.4.1.1.3.2-1: Cell configuration changes over time for FR1
|
Parameter |
Unit |
NR Cell 12 |
NR Cell 13 |
NR Cell 1 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“Off” |
“Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3 |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-115 |
-78 |
“Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3 |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-88 |
-88 |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3 |
Table 6.4.1.1.3.2-2: Cell configuration changes over time for FR2
|
Parameter |
Unit |
NR Cell 12 |
NR Cell 13 |
NR Cell 1 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-82 |
“Off” |
”Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2 |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
”Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2 |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
FFS |
FFS |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2 |
Table 6.4.1.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0A |
SS adjusts cell levels according to row T0 of table 6.4.1.1.3.2-1/2. |
– |
– |
– |
– |
0B |
The UE is switched on. |
– |
– |
– |
– |
0C1-0C19a1 |
The steps 1-19a1 specified in generic procedure TS 38.508-1 Table 4.5.3.2-1 are performed. |
– |
– |
– |
– |
0D |
SS starts timers of tmin = 2min and tmax = (6 min + 5min) (Note 1). |
– |
– |
– |
– |
0Ea1-0F |
The steps 19Aa1-20 specified in generic procedure TS 38.508-1 Table 4.5.3.2-1 are performed. |
– |
– |
– |
– |
1 |
SS adjusts cell levels according to row T1 of table 6.4.1.1.3.2-1/2. |
– |
– |
– |
– |
2 |
Check: Does the UE transmit an RRCResumeRequest message on NR Cell 13? |
– |
NR RRC: RRCResumeRequest |
1 |
P |
3 |
The SS transmits an RRCResume message. |
<– |
NR RRC: RRCResume |
– |
– |
4 |
The UE transmits an RRCResumeComplete message and a REGISTRATION REQUEST message indicating "mobility registration updating" is sent to update the registration of NR Cell13. |
–> |
NR RRC: RRCResumComplete 5GMM: REGISTRATION REQUEST |
– |
– |
4A-4B |
Steps 4 to 5 of the generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 with condition MOBILITY are performed. |
– |
– |
– |
– |
5 |
The SS transmits an RRCRelease message with suspend. |
<– |
NR RRC: RRCRelease |
– |
– |
6 |
Void |
– |
– |
– |
– |
7 |
The SS transmits a Paging message including a matched identity (correct fullI-RNTI) on NR Cell 13. |
<– |
NR RRC: Paging |
– |
– |
8 |
Check: Does the UE transmit an RRCResumeRequest message to resume RRC Connection by setting resumeIdentity to the stored shortI-RNTI value on NR Cell 13? |
–> |
NR RRC: RRCResumeRequest |
1 |
P |
9 |
The SS transmits an RRCResume message. |
<– |
NR RRC: RRCResume |
– |
– |
10 |
The UE transmits an RRCResumeComplete message. |
–> |
NR RRC: RRCResumeComplete |
– |
– |
11 |
The SS transmits an RRCRelease message with suspend. |
<– |
NR RRC: RRCRelease |
– |
– |
12 |
SS adjusts cell levels according to row T2 of table 6.4.1.1.3.2-1/2. |
– |
– |
– |
– |
13 |
Check: Does the UE send an RRCSetupRequest message on NR Cell 1 after tmin expires but before tmax expires (Note 1)? |
–> |
NR RRC: RRCSetupRequest |
2 |
P |
14 |
Steps 3-4 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed |
– |
– |
2 |
P |
– |
EXCEPTION: Steps 14a1 to 14b5a1 describe behaviours which depend on procedure parameters; the "lower case letter" identifies a step sequence that take place if a procedure parameter has a particular value. |
– |
– |
– |
– |
14a1-14a16a1 |
IF 5GS registration type is set as Initial Registration in step 14, THEN steps 5 to 20a1 of the registration procedure described in TS 38.508-1 [4] Table 4.5.2.2-2 are performed on NR Cell 1. Note 2 |
– |
– |
– |
– |
14b1-14b5a1 |
ELSE IF 5GS registration type is set as Mobility Registration in step 14, THEN steps 4 to 6a1 of the generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 are performed on NR Cell 1. Note 2 |
– |
– |
– |
– |
Note 1: Following attempts to access the HPLMN/EHPLMN/higher priority PLMN in VPLMN is operator specific setting (Refer to TS 23.122 [38] Rel-15).Hence, window between 2min to T+Tolerance is being used, where the high priority PLMN search timer T defined by EFHPPLMN. Tolerance of 5min is added to allow time for the UE to find the proper PLMN. Note 2: The 5GS registration type shall be only set as Mobility Registration for R16 UEs according to TS 24.501 [22] subclause 5.2.3.2.5 specified in Release 16. The EXCEPTION description applies only to R15 UEs. |
6.4.1.1.3.3 Specific message contents
Table 6.4.1.1.3.3-1: SIB4 for NR Cell 12 (preamble and all steps, Table 6.4.1.1.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB4 ::= SEQUENCE { |
|||
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo { |
2 entries |
||
InterFreqCarrierFreqInfo[1] SEQUENCE { |
entry 1 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 13 |
||
cellReselectionPriority |
4 |
||
} |
|||
InterFreqCarrierFreqInfo[2] SEQUENCE { |
entry 2 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 1 |
||
cellReselectionPriority |
4 |
||
} |
|||
} |
|||
} |
Table 6.4.1.1.3.3-2: SIB4 for NR Cell 13 (preamble and all steps, Table 6.4.1.1.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB4 ::= SEQUENCE { |
|||
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo { |
2 entries |
||
InterFreqCarrierFreqInfo[1] SEQUENCE { |
entry 1 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 12 |
||
cellReselectionPriority |
4 |
||
} |
|||
InterFreqCarrierFreqInfo[2] SEQUENCE { |
entry 2 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 1 |
||
cellReselectionPriority |
4 |
||
} |
|||
} |
|||
} |
Table 6.4.1.1.3.3-3: REGISTRATION ACCEPT for NR Cell 12 (step 0D, Table 6.4.1.1.3.2-3; step 14, TS 38.508-1 [4], Table 4.5.3.2-1)
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Equivalent PLMNs |
PLMN16 |
Table 6.4.1.1.3.3-4: RRCResumeRequest (Step 2, Table 6.4.1.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-19 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCResumeRequest ::= SEQUENCE { |
||||
rrcResumeRequest SEQUENCE { |
||||
resumeCause |
mo-Signalling |
|||
} |
||||
} |
6.4.1.2 Cell reselection of ePLMN in manual mode
6.4.1.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_INACTIVE state on a NR cell in manual PLMN Selection mode and network has downloaded a list of equivalent PLMNs during the Registration 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 , and attempts Registration with mobility on the selected cell. }
}
(2)
with { UE in NR RRC_INACTIVE state on a cell and network has downloaded a list of equivalent PLMNs during Registration procedure for mobility }
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. }
}
6.4.1.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.4.3.1.2 and TS 38.304, clauses 4.1 and clauses 4.2. Unless otherwise stated these are Rel-15 requirements.
[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) and l) 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", "5GS forbidden tracking areas for roaming", "forbidden location areas for regional provision of service", "forbidden tracking areas for regional provision of service", "5GS 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 MS has registered on a PLMN selected by the user, the MS shall not automatically register on a different PLMN unless:
i) the new PLMN is declared as an equivalent PLMN by the registered PLMN;
ii) the user selects automatic mode;
iii) the user initiates an emergency call while the MS is in limited service state and either the network does not broadcast the indication of support of emergency calls in limited service state, the registration request for emergency services is rejected by the network or the attach request for emergency bearer services is rejected by the network; or
iv) the user initiates access to RLOS, while the MS is in limited service state and either the network does not broadcast the indication of support of RLOS in limited service state, or the EPS attach request for access to RLOS is rejected by the network.
NOTE 2: If case iii) or iv) occurs, the MS can provide an indication to the upper layers that the MS has exited manual network selection 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 3: High quality signal is defined in the appropriate AS specification.
[TS 38.304, clause 4.1]
The RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes:
– PLMN selection;
– Cell selection and reselection;
– Location registration and RNA update.
PLMN selection, cell reselection procedures, and location registration are common for both RRC_IDLE state and RRC_INACTIVE state. RNA update is only applicable for RRC_INACTIVE state. When UE selects a new PLMN, UE transitions from RRC_INACTIVE to RRC_IDLE, as specified in TS 24.501 [14].
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, as specified in TS 23.122 [9]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use for cell selection and cell reselection.
With cell selection, the UE searches for a suitable cell of the selected PLMN, chooses that cell to provide available services, and monitors its control channel. This procedure is defined as "camping on the cell".
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of the chosen cell. As an outcome of a successful Location Registration, the selected PLMN then becomes the registered PLMN, as specified in TS 23.122 [9].
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRC_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed.
If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in TS 23.122 [9] and search for a suitable cell if another PLMN has been selected by NAS.
If the UE loses coverage of the registered PLMN, either a new PLMN is selected automatically (automatic mode), or an indication of available PLMNs is given to the user so that a manual selection can be performed (manual mode).
Registration is not performed by UEs only capable of services that need no registration.
The purpose of camping on a cell in RRC_IDLE state and RRC_INACTIVE state is fourfold:
a) It enables the UE to receive system information from the PLMN.
b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of tracking areas (in RRC_IDLE state) or RNA (in RRC_INACTIVE state) in which the UE is camped. It can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The UE will then receive the paging message and can respond.
d) It enables the UE to receive ETWS and CMAS notifications.
When the UE is in RRC_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all idle mode tasks.
[TS 38.304, clause 4.2]
Table 4.2-1 presents the functional division between UE non-access stratum (NAS) and UE access stratum (AS) in RRC_IDLE state and RRC_INACTIVE states. The NAS part is specified in TS 23.122 [9] and the AS part in the present document.
Table 4.2-1: Functional division between AS and NAS in RRC_IDLE state and RRC_INACTIVE state
RRC_IDLE and RRC_INACTIVE state Process |
UE Non-Access Stratum |
UE Access Stratum |
---|---|---|
PLMN Selection |
Maintain a list of PLMNs in priority order according to TS 23.122 [9]. Select a PLMN using automatic or manual mode as specified in TS 23.122 [9] and request AS to select a cell belonging to this PLMN. For each PLMN, associated RAT(s) may be set. Evaluate reports of available PLMNs from AS for PLMN selection. Maintain a list of equivalent PLMN identities. |
Search for available PLMNs. If associated RAT(s) is (are) set for the PLMN, search in this (these) RAT(s) and other RAT(s) for that PLMN as specified in TS 23.122 [9]. Perform measurements to support PLMN selection. Synchronise to a broadcast channel to identify found PLMNs. Report available PLMNs with associated RAT(s) to NAS on request from NAS or autonomously. |
Cell |
Control cell selection for example by indicating RAT(s) associated with the selected PLMN to be used initially in the search of a cell in the cell selection. Maintain a list of "Forbidden Tracking Areas" and provide the list to AS. |
Perform measurements needed to support cell selection. Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS. Search for a suitable cell. The cells broadcast one or more ‘PLMN identity’ in the system information. Respond to NAS whether such cell is found or not. If associated RATs is (are) set for the PLMN, perform the search in this (these) RAT(s) and other RATs for that PLMN as specified in TS 23.122 [9]. If a cell is found which satisfies cell selection criteria, camp on that cell. |
Cell |
Maintain a list of equivalent PLMN identities and provide the list to AS. Maintain a list of "Forbidden Tracking Areas" and provide the list to AS. |
Perform measurements needed to support cell reselection. Detect and synchronise to a broadcast channel. Receive and handle broadcast information. Forward NAS system information to NAS. Change cell if a more suitable cell is found. |
Location registration |
Register the UE as active after power on. Register the UE’s presence in a registration area, for instance regularly or when entering a new tracking area. Deregister UE when shutting down. Maintain a list of "Forbidden Tracking Areas". |
Report registration area information to NAS. |
RAN Notification Area Update |
Not applicable. |
Register the UE’s presence in a RAN-based notification area (RNA), periodically or when entering a new RNA. |
6.4.1.2.3 Test description
6.4.1.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 12 and NR Cell 13 are configured according to TS 38.508-1, Table 4.4.2-3.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cell 1 and NR cell 12.
– System information combination NR-1 as defined in TS 38.508-1 [4] clause 4.4.3.1.2-1 is used in NR cell 13.
UE:
– The UE is in Manual PLMN selection mode.
Preamble:
– The UE is registered on NR Cell 1 except that the REGISTRATION ACCEPT message indicates the PLMN of NR Cell 12 in the Equivalent PLMN list as described in Table 6.4.1.2.3.3-4.
– The UE is in state 2N-A as defined in TS 38.508-1 [4], Table 4.4A.2-2 on NR Cell 1.
6.4.1.2.3.2 Test procedure sequence
Table 6.4.1.2.3.2-1 for FR1 and Table 6.4.1.2.3.2-2 for FR2 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 initial conditions after preamble, while columns marked "T1", "T2" and "T3" are to be applied subsequently in the Main behaviour. The exact instants on which these values shall be applied are described in the texts in this clause.
Table 6.4.1.2.3.2-1: Cell configuration changes over time for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 12 |
NR Cell 13 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-99 |
-88 |
-78 |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
“Off” |
“Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3 |
Table 6.4.1.2.3.2-2: Cell configuration changes over time for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 12 |
NR Cell 13 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
“Off” |
“Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.2-2 |
Table 6.4.1.2.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts cell levels according to row T0 of table 6.4.1.2.3.2-1/2. |
– |
– |
– |
– |
2 |
Check: Does the UE transmit an RRCResumeRequest message on NR Cell 12? |
–> |
NR RRC: RRCResumeRequest |
1 |
P |
3-6 |
Steps 2 to 5 of the generic test procedure in TS 38.508-1 Table 4.9.5.2.2-1 with condition MOBILITY are performed. (Note 1) |
– |
– |
– |
– |
6A-6D |
Steps 5 to 8 of the generic test procedure in TS 38.508-1 Table 4.5.4.2-3. (Note 3) |
– |
– |
– |
– |
7 |
The SS transmits an RRCRelease message with suspend. |
–> |
NR RRC: RRCRelease |
– |
– |
8 |
Check: Does the UE send an RRCResumeRequest on NR Cell 13 and NR Cell 1 within 60s? |
–> |
NR RRC: RRCResumeRequest |
2 |
F |
9 |
SS adjusts cell levels according to row T1 of table 6.4.1.2.3.2-1/2. |
– |
– |
– |
– |
10 |
Set UE to Automatic PLMN selection mode. (Note 2) |
– |
– |
– |
– |
Note 1: The REGISTRATION REQUEST is accepted with the PLMN of NR Cell 1 listed as an Equivalent PLMN. Note 2: Steps 10 is to ensure UE is set back to automatic PLMN selection mode for the next test case. Note 3: No SERVICE ACCEPT message should be included in step 6C (corresponding to step 7 of Table 4.5.4.2-3 in TS 38.508-1 [4]). |
6.4.1.2.3.3 Specific message contents
Table 6.4.1.2.3.3-1: SIB4 for NR Cell 1 (preamble and all steps, Table 6.4.1.2.3.2-2)
Derivation path: 38.508-1 [4] Table 4.6.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB4 ::= SEQUENCE { |
|||
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo { |
2 entries |
||
InterFreqCarrierFreqInfo[1] SEQUENCE { |
entry 1 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 12 |
||
cellReselectionPriority |
4 |
||
} |
|||
InterFreqCarrierFreqInfo[2] SEQUENCE { |
entry 2 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 13 |
||
cellReselectionPriority |
4 |
||
} |
|||
} |
|||
} |
Table 6.4.1.2.3.3-2: SIB4 for NR Cell 12 (preamble and all steps, Table 6.4.1.2.3.2-2)
Derivation path: 38.508-1 [4] Table 4.6.2-3 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB4 ::= SEQUENCE { |
|||
interFreqCarrierFreqList SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo { |
2 entries |
||
InterFreqCarrierFreqInfo[1] SEQUENCE { |
entry 1 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 1 |
||
cellReselectionPriority |
4 |
||
} |
|||
InterFreqCarrierFreqInfo[2] SEQUENCE { |
entry 2 |
||
dl-CarrierFreq |
Same downlink NR ARFCN as used for NR Cell 13 |
||
cellReselectionPriority |
4 |
||
} |
|||
} |
|||
} |
Table 6.4.1.2.3.3-3: REGISTRATION ACCEPT for NR Cell 1 (preamble)
Derivation path: 38.508-1 [4] Table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Equivalent PLMNs |
The PLMN of NR Cell 12 |
Table 6.4.1.2.3.3-3A: RRCResumeRequest (Step 2, Table 6.4.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-19 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCResumeRequest ::= SEQUENCE { |
||||
rrcResumeRequest SEQUENCE { |
||||
resumeCause |
mo-Signalling |
|||
} |
||||
} |
Table 6.4.1.2.3.3-4: REGISTRATION ACCEPT for NR Cell 12 (step 5, Table 6.4.1.2.3.2-2)
Derivation path: 38.508-1 [4] Table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
Equivalent PLMNs |
The PLMN of NR Cell 1 |
||
Allowed NSSAI |
|||
S-NSSAI |
|||
Length of S-NSSAI contents |
‘0000 0010’B |
||
Mapped HPLMN SST |
Same as SST |
Table 6.4.1.2.3.3-4A: RRCReconfiguration for NR Cell 12 (step 6C, Table 6.4.1.2.3.2-2)
Derivation path: 38.508-1 [4] Table 4.6.1-13 with condition NR |
|||
Information Element |
Value/Remark |
Comment |
Condition |
dedicatedNAS-MessageList |
Not Present |
Table 6.4.1.2.3.3-5: RRCRelease (step 7, Table 6.4.1.2.3.2-2)
Derivation Path: 38.508-1 [4], Table 4.6.1-4B |
|||
Information Element |
Value/remark |
Comment |
Condition |
RRCRelease ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
rrcRelease SEQUENCE { |
|||
suspendConfig SEQUENCE { |
NR_RRC_INACTIVE |
||
ran-NotificationAreaInfo CHOICE { |
|||
cellList SEQUENCE { |
|||
plmn-Identity |
PLMN ID of NR Cell 12 |
||
ran-AreaCells SEQUENCE { |
|||
cellIdentity |
See Table 4.4.2-2 and 4.4.2-3 in TS 38.508-1 [4] |
Cell Identity of NR Cell 12 |
|
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
6.4.2 Cell Selection/Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE state)
6.4.2.1 Cell Selection/Qrxlevmin & Cell Reselection (Intra NR in RRC_INACTIVE state)
6.4.2.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { serving cell fulfils all requirements for a suitable cell except the cell selection criteria which are not fulfilled (Srxlev<0) }
then { UE does not consider the cell as suitable , leaves RRC_INACTIVE state and does not remain camped on that cell }
}
(2)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { UE detects a cell ranked as the best cell }
then { UE reselects to the new cell and continues to remain in RRC_INACTIVE state }
}
6.4.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.300, clause 9.2.1.1, and TS 38.304, clause 4.1, 4.5, 5.2.1, 5.2.3.1 and 5.2.3.2. Unless otherwise stated these are Rel-15 requirements.
[TS 38.300, clause 9.2.1.1]
The principles of PLMN selection in NR are based on the 3GPP PLMN selection principles. Cell selection is required on transition from RM-DEREGISTERED to RM-REGISTERED, from CM-IDLE to CM-CONNECTED and from CM-CONNECTED to CM-IDLE and is based on the following principles:
– The UE NAS layer identifies a selected PLMN and equivalent PLMNs;
– Cell selection is always based on CD-SSBs located on the synchronization raster (see subclause 5.2.4):
– The UE searches the NR frequency bands and for each carrier frequency identifies the strongest cell as per the CD-SSB. It then 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.
Transition to RRC_IDLE:
On transition from RRC_CONNECTED or RRC_INACTIVE to RRC_IDLE, a UE should camp on a cell as result of cell selection according to the frequency be assigned by RRC in the state transition message if any.
Recovery from out of coverage:
The UE should attempt to find a suitable cell in the manner described for stored information or initial cell selection above. If no suitable cell is found on any frequency or RAT, the UE should attempt to find an acceptable cell.
In multi-beam operations, the cell quality is derived amongst the beams corresponding to the same cell (see subclause 9.2.4).
[TS 38.304, clause 4.1]
The RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes:
– PLMN selection;
– Cell selection and reselection;
– Location registration and RNA update.
PLMN selection, cell reselection procedures, and location registration are common for both RRC_IDLE state and RRC_INACTIVE state. RNA update is only applicable for RRC_INACTIVE state. When UE selects a new PLMN, UE transitions from RRC_INACTIVE to RRC_IDLE, as specified in TS 24.501 [14].
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, as specified in TS 23.122 [9]. The NAS shall provide a list of equivalent PLMNs, if available, that the AS shall use for cell selection and cell reselection.
With cell selection, the UE searches for a suitable cell of the selected PLMN, chooses that cell to provide available services, and monitors its control channel. This procedure is defined as "camping on the cell".
The UE shall, if necessary, then register its presence, by means of a NAS registration procedure, in the tracking area of the chosen cell. As an outcome of a successful Location Registration, the selected PLMN then becomes the registered PLMN, as specified in TS 23.122 [9].
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRC_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed.
…
The purpose of camping on a cell in RRC_IDLE state and RRC_INACTIVE state is fourfold:
a) It enables the UE to receive system information from the PLMN.
b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of tracking areas (in RRC_IDLE state) or RNA (in RRC_INACTIVE state) in which the UE is camped. It can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The UE will then receive the paging message and can respond.
d) It enables the UE to receive ETWS and CMAS notifications.
When the UE is in RRC_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all idle mode tasks.
[TS 38.304, clause 4.5]
The cells are categorised according to which services they offer:
acceptable cell:
An "acceptable cell" is a cell on which the UE may camp to obtain limited service (originate emergency calls and receive ETWS and CMAS notifications). Such a cell shall fulfil the following requirements, which is the minimum set of requirements to initiate an emergency call and to receive ETWS and CMAS notification in an NR network:
– The cell is not barred, see subclause 5.3.1;
– The cell selection criteria are fulfilled, see subclause 5.2.3.2.
suitable cell:
A cell is considered as suitable if the following conditions are fulfilled:
– The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list and trackingAreaCode is provided for that PLMN;
– The cell selection criteria are fulfilled, see subclause 5.2.3.2.
According to the latest information provided by NAS:
– The cell is not barred, see subclause 5.3.1;
– The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas" (TS 22.261 [12]), which belongs to a PLMN that fulfils the first bullet above.
barred cell:
A cell is barred if it is so indicated in the system information, as specified in TS 38.331 [3].
reserved cell:
A cell is reserved if it is so indicated in system information, as specified in TS 38.331 [3].
Following exception to these definitions are applicable for UEs:
– if a UE has an ongoing emergency call, all acceptable cells of that PLMN are treated as suitable for the duration of the emergency call.
– camped on a cell that belongs to a registration area that is forbidden for regional provision of service; a cell that belongs to a registration area that is forbidden for regional provision service (TS 23.122 [9], TS 24.501 [14]) is suitable but provides only limited service.
[TS 38.304, clause 5.2.1]
UE shall perform measurements for cell selection and reselection purposes as specified in TS 38.133 [8].
When evaluating Srxlev and Squal of non-serving cells for reselection evaluation purposes, the UE shall use parameters provided by the serving cell and for the final check on cell selection criterion, the UE shall use parameters provided by the target cell for cell reselection.
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 RRC_IDLE or RRC_INACTIVE state measurements and cell selection criteria.
In order to expedite the cell selection process, stored information for several RATs, if available, may be used by 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 TS 38.133 [8].
The NAS is informed if the cell selection and reselection result in changes in the received system information relevant for NAS.
For normal service, the UE shall camp on a suitable cell, monitor control channel(s) of that cell 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.
For cell selection in multi-beam operations, measurement quantity of a cell is up to UE implementation.
For cell reselection in multi-beam operations, the measurement quantity of this cell is derived amongst the beams corresponding to the same cell based on SS/PBCH block as follows:
– if nrofSS-BlocksToAverage is not configured in SIB2/SIB4; or
– if absThreshSS-BlocksConsolidation is not configured in SIB2/SIB4; or
– if the highest beam measurement quantity value is below or equal to absThreshSS-BlocksConsolidation:
– derive a cell measurement quantity as the highest beam measurement quantity value, where each beam measurement quantity is described in TS 38.215 [11].
– else:
– derive a cell measurement quantity as the linear average of the power values of up to nrofSS-BlocksToAverage of highest beam measurement quantity values above absThreshSS-BlocksConsolidation.
[TS 38.304, clause 5.2.3.1]
Cell selection is performed by one of the following two procedures:
a) Initial cell selection (no prior knowledge of which RF channels are NR frequencies):
1. The UE shall scan all RF channels in the NR bands according to its capabilities to find a suitable cell.
2. On each frequency, the UE need only search for the strongest cell.
3. Once a suitable cell is found, this cell shall be selected.
b) Cell selection by leveraging stored information:
1. This procedure requires stored information of frequencies and optionally also information on cell parameters from previously received measurement control information elements or from previously detected cells.
2. Once the UE has found a suitable cell, the UE shall select it.
3. If no suitable cell is found, the initial cell selection procedure in a) shall be started.
NOTE: Priorities between different frequencies or RATs provided to the UE by system information or dedicated signalling are not used in the cell selection process.
[TS 38.304, clause 5.2.3.2]
The cell selection criterion S is fulfilled when:
Srxlev > 0 AND Squal > 0
where:
Srxlev = Qrxlevmeas – (Qrxlevmin + Qrxlevminoffset )– Pcompensation – Qoffsettemp
Squal = Qqualmeas – (Qqualmin + Qqualminoffset) – 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 TS 38.331 [3] (dB) |
Qrxlevmeas |
Measured cell RX level value (RSRP) |
Qqualmeas |
Measured cell quality value (RSRQ) |
Qrxlevmin |
Minimum required RX level in the cell (dBm). If the UE supports SUL frequency for this cell, Qrxlevmin is obtained from q-RxLevMinSUL, if present, in SIB1, SIB2 and SIB4, additionally, if QrxlevminoffsetcellSUL is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell; else Qrxlevmin is obtained from q-RxLevMin in SIB1, SIB2 and SIB4, additionally, if Qrxlevminoffsetcell is present in SIB3 and SIB4 for the concerned cell, this cell specific offset is added to the corresponding Qrxlevmin to achieve the required minimum RX level in the concerned cell. |
Qqualmin |
Minimum required quality level in the cell (dB). Additionally, if Qqualminoffsetcell is signalled for the concerned cell, this cell specific offset is added to achieve the required minimum quality level in the concerned cell. |
Qrxlevminoffset |
Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN, as specified in TS 23.122 [9]. |
Qqualminoffset |
Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN, as specified in TS 23.122 [9]. |
Pcompensation |
If the UE supports the additionalPmax in the NR-NS-PmaxList, if present, in SIB1, SIB2 and SIB4: max(PEMAX1 –PPowerClass, 0) – (min(PEMAX2, PPowerClass) – min(PEMAX1, PPowerClass)) (dB); else: max(PEMAX1 –PPowerClass, 0) (dB) |
PEMAX1, PEMAX2 |
Maximum TX power level of a UE may use when transmitting on the uplink in the cell (dBm) defined as PEMAX in TS 38.101 [15]. If UE supports SUL frequency for this cell, PEMAX1 and PEMAX2 are obtained from the p-Max for SUL in SIB1 and NR-NS-PmaxList for SUL respectively in SIB1, SIB2 and SIB4 as specified in TS 38.331 [3], else PEMAX1 and PEMAX2 are obtained from the p-Max and NR-NS-PmaxList respectively in SIB1, SIB2 and SIB4 for normal UL as specified in TS 38.331 [3]. |
PPowerClass |
Maximum RF output power of the UE (dBm) according to the UE power class as defined in TS 38.101-1 [15]. |
The signalled values Qrxlevminoffset and Qqualminoffset are only applied when a cell is evaluated for cell selection as a result of a periodic search for a higher priority PLMN while camped normally in a VPLMN (TS 23.122 [9]). During this periodic search for higher priority PLMN, the UE may check the S criteria of a cell using parameter values stored from a different cell of this higher priority PLMN.
6.4.2.1.3 Test description
6.4.2.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2.
– System information combination NR-3 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cells.
UE:
None.
Preamble:
– The UE is in state 2N-A on NR Cell 1(serving cell) according to TS 38.508-1 [4] Table 4.4A.2-2.
6.4.2.1.3.2 Test procedure sequence
Table 6.4.2.1.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the NR 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. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 6.4.2.1.3.2-3.
Table 6.4.2.1.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
Off |
The power level values are assigned to ensure the UE registered on NR Cell 1. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-115 |
Off |
The power level values are assigned to satisfy Srxlev NR Cell 1 < 0. |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-78 |
The power level values are assigned to satisfy RNR Cell 2 > RNR Cell 1. |
Note 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
Table 6.4.2.1.3.2-2: Time instances of cell power level and parameter changes for FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
Off |
The power level values are assigned to ensure the UE registered on NR Cell 1. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
Off |
The power level values are assigned to satisfy Srxlev NR Cell 1 < 0. |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
The power level values are assigned to satisfy RNR Cell 2 > RNR Cell 1. |
Note 1: The uncertain downlink signal level is specified in TS 38.508-1 [4] section FFS. |
Table 6.4.2.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes NR Cell 1 SSS level according to the row "T1" in table 6.4.2.1.3.2-1/2. |
– |
– |
– |
– |
2 |
Void |
– |
– |
– |
– |
2A |
Wait 15s. (Note 1) |
– |
– |
– |
– |
3 |
The SS transmits a Paging message. |
<– |
NR RRC: Paging |
– |
– |
4 |
Check: Does the UE attempt to transmit an uplink message within the next 10s? |
– |
– |
1 |
F |
5 |
The UE is switched off. |
– |
– |
– |
– |
6 |
Void |
– |
– |
– |
– |
6A |
Void |
– |
– |
– |
– |
6B |
The SS changes NR Cell 1 SSS levels according to the row "T0" in table 6.4.2.1.3.2-1/2. |
– |
– |
– |
– |
6C |
The UE is switched on. |
– |
– |
– |
– |
7 |
Generic procedure specified in TS 38.508-1 Table 4.5.3.2-1 are performed, in which the RRCRelease message includes the suspendConfig with NR_RRC_INACTIVE condition thereby moving the UE to RRC_INACTIVE. |
– |
– |
– |
– |
8-15 |
Void |
– |
– |
– |
– |
16 |
The SS changes NR Cell 2 SSS level according to the row "T2" in table 6.4.2.1.3.2-1/2. |
– |
– |
– |
– |
17 |
Void |
– |
– |
– |
– |
18 |
Check: Does the UE transmit an RRCResumeRequest message on the NR Cell 2? |
–> |
NR RRC: RRCResumeRequest |
2 |
P |
18A |
The SS transmits an RRCResume message. |
<– |
NR RRC: RRCResume |
– |
– |
18B |
The UE transmit an RRCResumeComplete message. |
–> |
NR RRC: RRCResumeComplete |
– |
– |
19 |
The SS transmits an RRCRelease message including suspendConfig with NR_RRC_INACTIVE condition. |
<– |
NR RRC: RRCRelease |
– |
– |
Note 1: As specified in TS 38.133 [30] clause 4.2.2.2, UE will wait DRXCycle * 2 to evaluate serving cell. If the UE in RRC_IDLE has not found any new suitable cell based on searches and measurements using the intra-frequency, inter-frequency and inter-RAT information indicated in the system information for 10 s, the UE shall initiate cell selection procedures for the selected PLMN.The wait time is selected to cover DRXCycle * 2 = 1280ms * 2 = 2.56s + 10s = 12.56s rounded up to 13s. Therefore, the actual wait time is selected to 15s, in order to be greater than 13s. |
6.4.2.1.3.3 Specific message contents
Table 6.4.2.1.3.3-1: SIB3 of NR Cell 1 (preamble and all steps, Table 6.4.2.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB3 ::= SEQUENCE { |
|||
intraFreqNeighCellList SEQUENCE (SIZE (1.. maxCellIntra)) OF IntraFreqNeighCellInfo { |
1 entry |
||
IntraFreqNeighCellInfo[1] SEQUENCE{ |
entry 1 |
||
physCellId |
Physical cell identity of NR Cell 2 |
||
q-OffsetCell |
0 |
||
} |
|||
} |
|||
} |
Table 6.4.2.1.3.3-1A: RRCResumeRequest (Step 18, Table 6.4.2.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-19 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCResumeRequest ::= SEQUENCE { |
||||
rrcResumeRequest SEQUENCE { |
||||
resumeCause |
rna-Update |
|||
} |
||||
} |
Table 6.4.2.1.3.3-2: RRCResume (step 18A, Table 6.4.2.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-17 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCResume ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcResume SEQUENCE { |
||||
masterCellGroup := SEQUENCE { |
CellGroupConfig |
Table 6.4.2.1.3.3-3 |
||
} |
||||
} |
||||
} |
Table 6.4.2.1.3.3-3: CellGroupConfig (Table 6.4.2.1.3.3-2)
Derivation Path: 38.508-1 [4], Table 4.6.3-19 with condition RESUME |
|||
Information Element |
Value/remark |
Comment |
Condition |
CellGroupConfig ::= SEQUENCE { |
|||
spCellConfigDedicated |
ServingCellConfig |
||
} |
Table 6.4.2.1.3.3-4: ServingCellConfig (Table 6.4.2.1.3.3-3: CellGroupConfig)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-167 with condition RESUME |
|||
Information Element |
Value/remark |
Comment |
Condition |
ServingCellConfig ::= SEQUENCE { |
|||
initialDownlinkBWP |
BWP-DownlinkDedicated |
||
} |
Table 6.4.2.1.3.3-5: BWP-DownlinkDedicated (Table 6.4.2.1.3.3-4: ServingCellConfig)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-11 |
|||
Information Element |
Value/remark |
Comment |
Condition |
BWP-DownlinkDedicated ::= SEQUENCE { |
|||
pdcch-Config |
Not present |
||
pdsch-Config CHOICE { |
|||
setup |
PDSCH-Config |
||
} |
|||
} |
Table 6.4.2.1.3.3-6: PDSCH-Config (Table 6.4.2.1.3.3-5: BWP-DownlinkDedicated)
Derivation Path: TS 38.508-1 [4], Table 4.6.3-100 |
|||
Information Element |
Value/remark |
Comment |
Condition |
PDSCH-Config ::= SEQUENCE { |
|||
dmrs-DownlinkForPDSCH-MappingTypeA |
Not present |
||
tci-StatesToAddModList SEQUENCE(SIZE (1.. maxNrofTCI-States)) OF TCI-State { |
1 entry |
||
TCI-State[1] SEQUENCE { |
entry 1 |
||
tci-StateId |
0 |
||
qcl-type1 SEQUENCE { |
|||
referenceSignal CHOICE { |
|||
ssb |
SSB index #n |
SSB index of NR Cell 2 |
|
} |
|||
} |
|||
} |
|||
} |
|||
prb-BundlingType |
Not present |
||
} |
6.4.2.2 Inter-frequency cell reselection according to cell reselection priority provided by SIBs in RRC_INACTIVE state
6.4.2.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the equal priority frequency }
then { UE reselects to the cell which belongs to the equal priority frequency and remains in RRC_INACTIVE state }
}
(2)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the higher priority frequency }
then { UE reselects to the cell which belongs to the higher priority frequency and remains in RRC_INACTIVE state }
}
(3)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { UE detects the cell re-selection criteria are met for the cell which belongs to the lower priority frequency }
then { UE reselects to the cell which belongs to the lower priority frequency and remains in RRC_INACTIVE state }
}
6.4.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 4.1, 5.2.4.1, 5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 4.1]
The RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes:
– PLMN selection;
– Cell selection and reselection;
– Location registration and RNA update.
PLMN selection, cell reselection procedures, and location registration are common for both RRC_IDLE state and RRC_INACTIVE state. RNA update is only applicable for RRC_INACTIVE state. When UE selects a new PLMN, UE transitions from RRC_INACTIVE to RRC_IDLE, as specified in TS 24.501 [14].
…
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRC_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed.
If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in TS 23.122 [9] and search for a suitable cell if another PLMN has been selected by NAS.
If the UE loses coverage of the registered PLMN, either a new PLMN is selected automatically (automatic mode), or an indication of available PLMNs is given to the user so that a manual selection can be performed (manual mode).
Registration is not performed by UEs only capable of services that need no registration.
The purpose of camping on a cell in RRC_IDLE state and RRC_INACTIVE state is fourfold:
a) It enables the UE to receive system information from the PLMN.
b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of tracking areas (in RRC_IDLE state) or RNA (in RRC_INACTIVE state) in which the UE is camped. It can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The UE will then receive the paging message and can respond.
d) It enables the UE to receive ETWS and CMAS notifications.
When the UE is in RRC_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all idle mode tasks.
[TS 38.304, clause 5.2.4.1]
Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an NR frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCRelease unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values).
The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
In case UE receives RRCRelease with deprioritisationReq, UE shall consider current frequency and stored frequencies due to the previously received RRCRelease with deprioritisationReq or all the frequencies of NR to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running irrespective of camped RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection is performed on request by NAS (3GPP TS 23.122 [9]).
NOTE: UE should search for a higher priority layer for cell reselection as soon as possible after the change of priority. The minimum related performance requirements specified in TS 38.133 [8] are still applicable.
The UE shall delete priorities provided by dedicated signalling when:
– the UE enters a different RRC state; or
– the optional validity time of dedicated priorities (T320) expires; or
– a PLMN selection is performed on request by NAS (3GPP TS 23.122 [9]).
NOTE 2: Equal priorities between RATs are not supported.
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e. T320 in NR and E-UTRA), if configured, at inter-RAT cell (re)selection.
NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.
[TS 38.304, clause 5.2.4.2]
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 and Squal > SIntraSearchQ, 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 NR inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
– For a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies according to TS 38.133 [8].
– For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current NR frequency:
– If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority;
– Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority according to TS 38.133 [8].
[TS 38.304, clause 5.2.4.5]
If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > ThreshX, HighQ during a time interval TreselectionRAT
Otherwise, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection as defined in sub-clause 5.2.4.6.
If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority NR or E-UTRAN RAT/ frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT.
Otherwise, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a higher priority RAT/frequency shall take precedence over a lower priority RAT/frequency if multiple cells of different priorities fulfil the cell reselection criteria.
If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
– If the highest-priority frequency is an NR frequency, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
– If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.
6.4.2.2.3 Test description
6.4.2.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 3 and NR Cell 6.
– System information combination NR-4 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cells.
UE:
– None.
Preamble:
– The UE is in state 2N-A on NR Cell 1(serving cell) according to TS 38.508-1 [4] Table 4.4A.2-2.
6.4.2.2.3.2 Test procedure sequence
Table 6.4.2.2.3.2-1/2 illustrates the downlink power levels and other changing parameters to be applied for the NR 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. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1", "T2" and "T3" are applied at the points indicated in the Main behaviour description in Table 6.4.2.2.3.2-3.
Table 6.4.2.2.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
NR Cell 6 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
Off |
Off |
The power level values are assigned to ensure the UE registered on NR Cell 1. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-78 |
Off |
The power level values are assigned to satisfy RNR Cell 1 < RNR Cell 3. |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
Off |
-78 |
-78 |
The power level values are assigned to satisfy SrxlevNR Cell 1 < 0 and SrxlevNR Cell 6 > ThreshNR Cell 6, highP. |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
Off |
-78 |
-98 |
The power level values are assigned to satisfy SrxlevNR Cell 6 < Threshserving, lowP and SrxlevNR Cell 3 > ThreshNR Cell 3, lowP, SrxlevNR Cell 1< 0. |
Note 1: Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
Table 6.4.2.2.3.2-2: Time instances of cell power level and parameter changes for FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 3 |
NR Cell 6 |
Remark |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
Off |
Off |
The power level values are assigned to ensure the UE registered on NR Cell 1. |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
Off |
The power level values are assigned to satisfy RNR Cell 1 < RNR Cell 3. |
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
Off |
FFS |
FFS |
The power level values are assigned to satisfy SrxlevNR Cell 1 < 0 and SrxlevNR Cell 6 > ThreshNR Cell 6, highP. |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
Off |
FFS |
FFS |
The power level values are assigned to satisfy SrxlevNR Cell 6 < Threshserving, lowP and SrxlevNR Cell 3 > ThreshNR Cell 3, lowP, SrxlevNR Cell 1< 0. |
Note 1: The uncertain downlink signal level is specified in TS 38.508-1 [4] section FFS. |
Table 6.4.2.2.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes NR Cell 3 SSS level according to the row "T1" in table 6.4.2.2.3.2-1/2. |
– |
– |
– |
– |
2 |
Void |
– |
– |
– |
– |
3 |
Check: Does the UE transmit an RRCResumeRequest message on the cell 3? |
–> |
NR RRC: RRCResumeRequest |
1 |
P |
4 |
The SS transmits an RRCRelease message including suspendConfig with NR_RRC_INACTIVE condition. |
<– |
NR RRC: RRCRelease |
– |
– |
5 |
The SS changes NR Cell 1 and NR Cell 6 SSS levels according to the row "T2" in table 6.4.2.2.3.2-1/2. |
– |
– |
– |
– |
6 |
Void |
– |
– |
– |
– |
7 |
Check: Does the UE transmit an RRCResumeRequest message on the cell 6? |
–> |
NR RRC: RRCResumeRequest |
2 |
P |
8 |
The SS transmits an RRCRelease message including suspendConfig with NR_RRC_INACTIVE condition. |
<– |
NR RRC: RRCRelease |
– |
– |
9 |
The SS changes NR Cell 6 SSS level according to the row "T3" in table 6.4.2.2.3.2-1/2. |
– |
– |
– |
– |
10 |
Void |
– |
– |
– |
– |
11 |
Check: Does the UE transmit an RRCResumeRequest message on the cell 3? |
–> |
NR RRC: RRCResumeRequest |
3 |
P |
12 |
The SS transmits an RRCRelease message including suspendConfig with NR_RRC_INACTIVE condition. |
<– |
NR RRC: RRCRelease |
– |
– |
6.4.2.2.3.3 Specific message contents
Table 6.4.2.2.3.3-1: Conditions for specific message contents in Tables below
Condition |
Explanation |
NR Cell 1 |
This condition applies to system information transmitted on NR Cell 1. |
NR Cell 3 |
This condition applies to system information transmitted on NR Cell 3. |
NR Cell 6 |
This condition applies to system information transmitted on NR Cell 6. |
Table 6.4.2.2.3.3-2: SIB2 of NR Cell 6 (preamble and all steps, Table 6.4.2.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB2 ::= SEQUENCE { |
|||
cellReselectionServingFreqInfo SEQUENCE { |
|||
threshServingLowP |
10 |
20 dB |
|
cellReselectionPriority |
5 |
||
} |
|||
} |
Table 6.4.2.2.3.3-3: SIB4 of NR Cell 1, NR Cell 3 and NR Cell 6 (preamble and all steps, Table 6.4.2.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-3 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB4 ::= SEQUENCE { |
|||
interFreqCarrierFreqList SEQUENCE SIZE (1..maxFreq) OF SEQUECNCE { |
2 entries |
NR Cell 1 |
|
1 entry |
NR Cell 3 and NR Cell 6 |
||
dl-CarrierFreq[1] |
Same downlink ARFCN as used for NR Cell 6 |
NR Cell 1 |
|
Same downlink ARFCN as used for NR Cell 6 |
NR Cell 3 |
||
Same downlink ARFCN as used for NR Cell 3 |
NR Cell 6 |
||
threshX-HighP[1] |
10 |
20 dB |
NR Cell 3 |
cellReselectionPriority[1] |
5 |
NR Cell 1 |
|
5 |
NR Cell 3 |
||
4 |
NR Cell 6 |
||
dl-CarrierFreq[2] |
Same downlink ARFCN as used for NR Cell 3 |
NR Cell 1 |
|
cellReselectionPriority[2] |
4 |
NR Cell 1 |
|
} |
|||
} |
Table 6.4.2.1.3.3-5: RRCResumeRequest (Step 3, 7 and 11, Table 6.4.2.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-19 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCResumeRequest ::= SEQUENCE { |
||||
rrcResumeRequest SEQUENCE { |
||||
resumeCause |
rna-Update |
|||
} |
||||
} |
6.4.3 Inter-RAT Cell Reselection
6.4.3.1 Inter-RAT cell reselection From NR RRC_INACTIVE to E-UTRA RRC_IDLE (lower priority & higher priority, Srxlev based)
6.4.3.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { UE detects the cell re-selection criteria are met for the neighbour cell which belongs to the higher priority E-UTRA frequency }
then { UE reselects to the E-UTRA cell and transitions to E-UTRA RRC_IDLE State }
}
(2)
with { UE in NR RRC_INACTIVE state }
ensure that {
when { UE detects the cell re-selection criteria are met for the neighbour cell which belongs to the lower priority E-UTRA frequency }
then { UE reselects to the E-UTRA cell and transitions to E-UTRA RRC_IDLE State }
}
6.4.3.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in TS 38.304: clause 4.1, 5.2.4.1, 5.2.4.2 and 5.2.4.5. Unless otherwise stated these are Rel-15 requirements.
[TS 38.304, clause 4.1]
The RRC_IDLE state and RRC_INACTIVE state tasks can be subdivided into three processes:
– PLMN selection;
– Cell selection and reselection;
– Location registration and RNA update.
PLMN selection, cell reselection procedures, and location registration are common for both RRC_IDLE state and RRC_INACTIVE state. RNA update is only applicable for RRC_INACTIVE state. When UE selects a new PLMN, UE transitions from RRC_INACTIVE to RRC_IDLE, as specified in TS 24.501 [14].
…
If the UE finds a more suitable cell, according to the cell reselection criteria, it reselects onto that cell and camps on it. If the new cell does not belong to at least one tracking area to which the UE is registered, location registration is performed. In RRC_INACTIVE state, if the new cell does not belong to the configured RNA, an RNA update procedure is performed.
If necessary, the UE shall search for higher priority PLMNs at regular time intervals as described in TS 23.122 [9] and search for a suitable cell if another PLMN has been selected by NAS.
If the UE loses coverage of the registered PLMN, either a new PLMN is selected automatically (automatic mode), or an indication of available PLMNs is given to the user so that a manual selection can be performed (manual mode).
Registration is not performed by UEs only capable of services that need no registration.
The purpose of camping on a cell in RRC_IDLE state and RRC_INACTIVE state is fourfold:
a) It enables the UE to receive system information from the PLMN.
b) When registered and if the UE wishes to establish an RRC connection or resume a suspended RRC connection, it can do this by initially accessing the network on the control channel of the cell on which it is camped.
c) If the network needs to send a message or deliver data to the registered UE, it knows (in most cases) the set of tracking areas (in RRC_IDLE state) or RNA (in RRC_INACTIVE state) in which the UE is camped. It can then send a "paging" message for the UE on the control channels of all the cells in the corresponding set of areas. The UE will then receive the paging message and can respond.
d) It enables the UE to receive ETWS and CMAS notifications.
When the UE is in RRC_IDLE state, upper layers may deactivate AS layer when MICO mode is activated as specified in TS 24.501 [14]. When MICO mode is activated, the AS configuration (e.g. priorities provided by dedicated signalling) is kept and all running timers continue to run but the UE need not perform any idle mode tasks. If a timer expires while MICO mode is activated it is up to the UE implementation whether it performs the corresponding action immediately or the latest when MICO mode is deactivated. When MICO mode is deactivated, the UE shall perform all idle mode tasks.
[TS 38.304, clause 5.2.4.1]
Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an NR frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCRelease unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values).
The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.
In case UE receives RRCRelease with deprioritisationReq, UE shall consider current frequency and stored frequencies due to the previously received RRCRelease with deprioritisationReq or all the frequencies of NR to be the lowest priority frequency (i.e. lower than any of the network configured values) while T325 is running irrespective of camped RAT. The UE shall delete the stored deprioritisation request(s) when a PLMN selection is performed on request by NAS (3GPP TS 23.122 [9]).
NOTE: UE should search for a higher priority layer for cell reselection as soon as possible after the change of priority. The minimum related performance requirements specified in TS 38.133 [8] are still applicable.
The UE shall delete priorities provided by dedicated signalling when:
– the UE enters a different RRC state; or
– the optional validity time of dedicated priorities (T320) expires; or
– a PLMN selection is performed on request by NAS (3GPP TS 23.122 [9]).
NOTE 2: Equal priorities between RATs are not supported.
The UE shall not consider any black listed cells as candidate for cell reselection.
The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e. T320 in NR and E-UTRA), if configured, at inter-RAT cell (re)selection.
NOTE 3: The network may assign dedicated cell reselection priorities for frequencies not configured by system information.
[TS 38.304, clause 5.2.4.2]
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 and Squal > SIntraSearchQ, 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 NR inter-frequencies and inter-RAT frequencies which are indicated in system information and for which the UE has priority provided as defined in 5.2.4.1:
– For a NR inter-frequency or inter-RAT frequency with a reselection priority higher than the reselection priority of the current NR frequency, the UE shall perform measurements of higher priority NR inter-frequency or inter-RAT frequencies according to TS 38.133 [8].
– For a NR inter-frequency with an equal or lower reselection priority than the reselection priority of the current NR frequency and for inter-RAT frequency with lower reselection priority than the reselection priority of the current NR frequency:
– If the serving cell fulfils Srxlev > SnonIntraSearchP and Squal > SnonIntraSearchQ, the UE may choose not to perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority;
– Otherwise, the UE shall perform measurements of NR inter-frequencies or inter-RAT frequency cells of equal or lower priority according to TS 38.133 [8].
[TS 38.304, clause 5.2.4.5]
If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority NR or EUTRAN RAT/frequency fulfils Squal > ThreshX, HighQ during a time interval TreselectionRAT
Otherwise, cell reselection to a cell on a higher priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– A cell of a higher priority RAT/ frequency fulfils Srxlev > ThreshX, HighP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a cell on an equal priority NR frequency shall be based on ranking for intra-frequency cell reselection as defined in sub-clause 5.2.4.6.
If threshServingLowQ is broadcast in system information and more than 1 second has elapsed since the UE camped on the current serving cell, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Squal < ThreshServing, LowQ and a cell of a lower priority NR or E-UTRAN RAT/ frequency fulfils Squal > ThreshX, LowQ during a time interval TreselectionRAT.
Otherwise, cell reselection to a cell on a lower priority NR frequency or inter-RAT frequency than the serving frequency shall be performed if:
– The serving cell fulfils Srxlev < ThreshServing, LowP and a cell of a lower priority RAT/ frequency fulfils Srxlev > ThreshX, LowP during a time interval TreselectionRAT; and
– More than 1 second has elapsed since the UE camped on the current serving cell.
Cell reselection to a higher priority RAT/frequency shall take precedence over a lower priority RAT/frequency if multiple cells of different priorities fulfil the cell reselection criteria.
If more than one cell meets the above criteria, the UE shall reselect a cell as follows:
– If the highest-priority frequency is an NR frequency, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria according to section 5.2.4.6;
– If the highest-priority frequency is from another RAT, a cell ranked as the best cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.
6.4.3.1.3 Test description
6.4.3.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1.
– NR Cell 1 is configured to operate in FR1 bands as defined in TS 38.508-1 [4] clause 6.2.3.
– System information combination NR-6 as defined in TS 38.508-1 [4] Table 4.4.3.1.2-1 is used in NR cell.
– E-UTRA Cell 1 and E-UTRA Cell 3.
– System information combination 31 as defined in TS 36.508 [7] Table 4.4.3.1.1-1 is used in E-UTRA cell 1 and E-UTRA cell 3.
UE:
– None.
Preamble:
– With E-UTRA Cell 1 "Serving cell" and NR Cell 1 "Non-suitable "Off" cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state RRC_IDLE using generic procedure parameters Connectivity (E-UTRA/EPC) and Unrestricted nr PDN (On) in accordance with the procedure described in TS 38.508-1 [4], clause 4.5.2. 4G GUTI and eKSI are assigned and security context established
– the UE is switched-off
– With E-UTRA Cell 1 "Non-suitable "Off" cell" and NR Cell 1 "Serving cell" in accordance with TS 38.508-1 [4], Table 6.2.2.1-3, the UE is brought to state 2N-A, RRC_INACTIVE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4], Table 4.5.3.2-1. 5G-GUTI and ngKSI are assigned and security context established.
6.4.3.1.3.2 Test procedure sequence
Table 6.4.3.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the NR 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. The configuration "T0" indicates the initial conditions. Subsequent configurations marked "T1" and "T2" are applied at the points indicated in the Main behaviour description in Table 6.4.3.1.3.2-3.
Table 6.4.3.1.3.2-1: Time instances of cell power level and parameter changes for conducted test environment
Parameter |
Unit |
NR Cell 1 |
E-UTRA Cell 1 |
E-UTRA Cell 3 |
Remark |
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
– |
Off |
Off |
The power level values are assigned to ensure the UE registered on NR Cell 1. |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
– |
– |
||
T1 |
Cell-specific RS EPRE |
dBm/15kHz |
– |
-78 |
Off |
The power level values are assigned to satisfy SrxlevE-UTRA Cell 1 > ThreshE-UTRA Cell 1, HighP. |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
– |
– |
||
T2 |
Cell-specific RS EPRE |
dBm/15kHz |
– |
Off |
-76 |
The power level values are assigned to satisfy SrxlevNR Cell 1 < Threshserving, LowP, SrxlevE-UTRA Cell 3 > ThreshE-UTRA Cell 3, lowP, and SrxlevE-UTRA Cell 1 < 0. |
SS/PBCH SSS EPRE |
dBm/SCS |
-98 |
– |
– |
||
Note 1: Power level “Off” of NR cell is defined in TS 38.508-1 [4] Table 6.2.2.1-3. Note 2: Power level “Off” of E-UTRA cell is defined in TS 36.508 [7] Table 6.2.2.1-3. |
Table 6.4.3.1.3.2-2: Void
Table 6.4.3.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes E-UTRA Cell 1 SSS level according to the row "T1" in table 6.4.3.1.3.2-1. |
– |
– |
– |
– |
2 |
Void |
– |
– |
– |
– |
3 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.7.2.2-1 indicate that the UE is camped on E-UTRA Cell 1? |
– |
– |
1 |
P |
4 |
The SS changes NR Cell 1 SSS levels according to the row "T0" in table 6.4.3.1.3.2-1. |
– |
– |
– |
– |
5 |
Void |
– |
– |
– |
– |
6 |
Steps of the generic test procedure in TS 38.508-1 [4] Table 4.9.9.2.2-1 are performed on NR Cell 1. |
– |
– |
– |
– |
7 |
The SS transmits an RRCRelease message. |
<– |
NR RRC: RRCRelease |
– |
– |
7A-7H |
Steps 1-8 as defined in TS 38.508-1 [4] Table 4.5.4.2-3 |
– |
– |
– |
– |
7I |
The SS transmits an RRCRelease message including suspendConfig with NR_RRC_INACTIVE condition. |
<– |
NR RRC: RRCRelease |
– |
– |
8 |
The SS changes NR Cell 1, E-UTRA Cell 1 and E-UTRA Cell 3 SSS level according to the row "T2" in table 6.4.3.1.3.2-1. |
– |
– |
– |
– |
9 |
Void |
– |
– |
– |
– |
10 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.7.2.2-1 indicate that the UE is camped on E-UTRA Cell 3 with condition ‘connected without release‘? |
– |
– |
2 |
P |
11 |
At the end of this test procedure sequence, the UE is in end state E-UTRA connected (E2_T3440) according to TS 36.508 [7]. |
– |
– |
– |
– |
6.4.3.1.3.3 Specific message contents
Table 6.4.3.1.3.3-1: SIB2 of NR Cell 1 (preamble and all steps, Table 6.4.3.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB2 ::= SEQUENCE { |
|||
cellReselectionServingFreqInfo SEQUENCE { |
|||
threshServingLowP |
10 |
20 dB |
|
cellReselectionPriority |
5 |
||
} |
|||
} |
Table 6.4.3.1.3.3-2: SIB5 of NR Cell 1 (preamble and all steps, Table 6.4.3.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.6.2-4 |
|||
Information Element |
Value/remark |
Comment |
Condition |
SIB5 ::= SEQUENCE { |
|||
carrierFreqListEUTRA SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA { |
2 entries |
||
CarrierFreqEUTRA[1] SEQUENCE { |
entry 1 |
||
carrierFreq |
Same downlink ARFCN as used for E-UTRA Cell 1 |
||
cellReselectionPriority |
6 |
||
} |
|||
CarrierFreqEUTRA[2] SEQUENCE { |
entry 2 |
||
carrierFreq |
Same downlink ARFCN as used for E-UTRA Cell 3 |
||
cellReselectionPriority |
4 |
||
} |
|||
} |
|||
} |
Table 6.4.3.1.3.3-3: SystemInformationBlockType24 for E-UTRA Cell 1 (preamble and all steps, Table 6.4.3.1.3.2-3)
Derivation path: 36.508 [7] table 4.4.3.3-20 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType24-r15 ::= SEQUENCE { |
|||
carrierFreqListNR-r15 SEQUENCE (SIZE (1..maxFreq)) OF CarrierFreqNR-r15 { |
1 entry |
||
CarrierFreqNR-r15[1] SEQUENCE { |
entry 1 |
||
carrierFreq-r15 |
Same downlink ARFCN as used for NR Cell 1 |
||
cellReselectionPriority-r15 |
5 |
||
} |
|||
} |
|||
} |
Table 6.4.3.1.3.3-4: TRACKING AREA UPDATE REQUEST (Step 3, Table 6.4.3.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.9.7.2.3-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
EPS update type Value |
‘010’B |
Combined TA/LA updating with IMSI attach |
combined_TA_LA |
‘000’B |
TA updating |
TA_only |
|
NOTE: The message shall be integrity protected using the 5GS security context available in the UE. |
Table 6.4.3.1.3.3-5: TRACKING AREA UPDATE REQUEST (Step 10, Table 6.4.3.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.9.7.2.3-1 |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS update type |
|||
EPS update type Value |
‘001’B |
Combined TA/LA updating |
combined_TA_LA |
‘000’B |
TA updating |
TA_only |
|
UE radio capability information update needed |
Not Check |
UE radio capability information update needed |
|
NOTE: The message shall be integrity protected using the 5GS security context available in the UE. |
Condition |
Explanation |
TA_only |
This condition applies if the UE is configured to initiate EPS attach or if explicitly specified. |
combined_TA_LA |
This condition applies if the UE is configured to initiate combined EPS/IMSI attach or if explicitly specified. |
Table 6.4.3.1.3.3-6: REGISTRATION REQUEST (Step 6, Table 6.4.3.1.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.7.1-6. |
|||
Information Element |
Value/remark |
Comment |
Condition |
EPS NAS message container |
TRACKING AREA UPDATE REQUEST message |
See Table 6.4.3.1.3.3-7 |
Table 6.4.3.1.3.3-7: TRACKING AREA UPDATE REQUEST (Table 6.4.3.1.3.3-6)
Derivation Path: TS 38.508-1 [4], Table 4.9.9.2.3-2 with condition Mapped EPS security context |
Table 6.4.3.1.3.3-8: SystemInformationBlockType24 for E-UTRA Cell 3 (preamble and all steps, Table 6.4.3.1.3.2-3)
Derivation path: 36.508 [7] table 4.4.3.3-20 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SystemInformationBlockType24-r15 ::= SEQUENCE { |
|||
carrierFreqListNR-r15 SEQUENCE (SIZE (1..maxFreq)) OF CarrierFreqNR-r15 { |
1 entry |
||
CarrierFreqNR-r15[1] SEQUENCE { |
entry 1 |
||
carrierFreq-r15 |
Same downlink ARFCN as used for NR Cell 1 |
||
threshX-High-r15 |
10 |
||
} |
|||
} |
|||
} |