6.5 SNPN and CAG Selection
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
6.5.1 SNPN Only Selection
6.5.1.1 SNPN Selection in Manual Mode
6.5.1.1.1 Test Purpose (TP)
(1)
with { UE in Manual network/SNPN selection mode and an SNPN cell is available for which an entry does not exist in the "list of subscriber data" }
ensure that {
when { UE is switched on or return to coverage }
then { UE does not indicate to the user any available SNPNs }
}
(2)
with { UE in Manual network/SNPN selection mode }
ensure that {
when { an SNPN cell is available for which an entry exists in the "list of subscriber data" }
then { UE indicates to the user that an SNPN is available and user selects the SNPN }
}
(3)
with { UE in Manual network/SNPN selection mode and has registered on an SNPN selected by the user }
ensure that {
when { an SNPN cell is available for which an entry exists in the "list of subscriber data" }
then { UE does not automatically register on the SNPN cell until the user selects automatic SNPN selection mode }
}
6.5.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.9.3.1.0 and 4.9.3.1.2. Unless otherwise stated these are Rel-16 requirements.
[TS 23.122, clause 4.9.3.1.0]
At switch on, or following recovery from lack of coverage, the MS selects the registered SNPN (if it is available) using NG-RAN access technology and if necessary (in the case of recovery from lack of coverage, see subclause 4.5.2) attempts to perform an LR.
NOTE 1: The MS in automatic SNPN selection mode can end the SNPN search procedure once the registered SNPN is found on NG-RAN access technology.
NOTE 2: An MS in automatic SNPN selection mode can use location information to determine which SNPNs can be available in its present location.
If successful registration is achieved, the MS indicates the selected SNPN.
If there is no registered SNPN, or registration is not possible due to the SNPN being unavailable or registration failure, the MS follows the procedure in subclause 4.9.3.1.1 or subclause 4.9.3.1.2 depending on its SNPN selection mode. At switch on, the MS shall use the SNPN selection mode that was used before switching off.
NOTE 3: If successful registration is achieved, then the current serving SNPN becomes the registered SNPN and the MS does not store the previous registered SNPN for later use.
If registration is not possible on recovery from lack of coverage due to the registered SNPN being unavailable, an MS may, optionally, continue looking for the registered SNPN for an implementation dependent time.
NOTE 4: An MS registered to an SNPN should behave as described above only if one or more PDU sessions are currently active.
[TS 23.122, clause 4.9.3.1.2]
The MS indicates to the user one or more SNPNs, which are available and each of them is identified by an SNPN identity in an entry of the "list of subscriber data" in the ME. This includes SNPNs in the list of "permanently forbidden SNPNs", and the list of "temporarily forbidden SNPNs". The MS may indicate to the user whether the available SNPNs are present in the list of "temporarily forbidden SNPNs" or the list of "permanently forbidden SNPNs". The order in which those SNPNs are indicated is MS implementation specific.
For each of the SNPNs indicated to the user, the UE shall forward a human-readable network name along with the SNPN identity to the upper layers if the system information broadcasted for the SNPN includes the human-readable network name for the SNPN.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
The user may select his desired SNPN and the MS then initiates registration on this SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from an entry of the "list of subscriber data", with the SNPN identity matching the selected SNPN (this may take place at any time during the presentation of SNPNs).
Once the MS has registered on an SNPN selected by the user, the MS shall not automatically register on a different SNPN unless the user selects automatic SNPN selection mode.
NOTE: Emergency services are not supported in SNPN access mode.
If the user does not select an SNPN, the selected SNPN shall be the one that was selected either automatically or manually before the SNPN selection procedure started. If no such SNPN was selected or that SNPN is no longer available, then the MS shall attempt to camp on any acceptable cell and enter the limited service state.
6.5.1.1.3 Test description
6.5.1.1.3.1 Pre-test conditions
System Simulator:
– 3 SNPN cells: NR Cell 1, NR Cell 2, and NR Cell 4 are configured broadcasting default SNPN IDs as indicated in TS 38.508-1 [4] Table 4.4.2-4.
– System information combination NR-12 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.
UE:
– The UE is in Manual SNPN selection mode.
– The UE is provisioned with a “list of subscriber data” to allow access to SNPN identified by NR Cell 2 and NR Cell 4.
Preamble:
– Ensure that the UE has cleared the Registered SNPN and the UE is in state Switched OFF (state 0-A).
6.5.1.1.3.2 Test procedure sequence
Table 6.5.1.1.3.2-1/2 shows the cell configurations used during the test. Subsequent configurations marked “T1”, “T2” “T3” “T4”etc are applied at the points indicated in the Main behaviour description in Table 6.5.1.1.3.2-3. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.1.1.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remarks |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“Off” |
“Off” |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
“Off” |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
-88 |
-78 |
|
T4 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“Off” |
-78 |
Table 6.5.1.1.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remarks |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T4 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
Table 6.5.1.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts cell levels according to row T1 of table 6.5.1.1.3.2-1/2. |
– |
– |
– |
– |
2 |
The UE is Switched ON. |
– |
– |
– |
– |
3 |
Manual selection of SNPN identified by NR Cell 1 is performed (NOTE 1). |
– |
– |
– |
– |
4 |
Check: Does the UE transmit an RRCSetupRequest on NR Cell 1 within the next 60 s? |
–> |
RRCSetupRequest |
1 |
F |
5 |
SS adjusts cell levels according to row T2 of table 6.5.1.1.3.2-1/2. |
– |
– |
– |
– |
6 |
Manual selection of SNPN identified by NR Cell 2 is performed (NOTE 1). |
– |
– |
– |
– |
7 |
Check: Does the UE send a RRCSetupRequest on NR Cell 2? |
–> |
RRCSetupRequest |
2 |
P |
8-25 |
Steps 3 to 20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 are performed on NR Cell 2. |
– |
– |
– |
– |
26 |
SS adjusts cell levels according to row T3 of table 6.5.1.1.3.2-1/2. |
– |
– |
– |
– |
27 |
Check: Does the UE send a RRCSetupRequest on NR Cell 4 within the next 60 s? |
–> |
RRCSetupRequest |
3 |
F |
28 |
SS adjusts cell levels according to row T4 of table 6.5.1.1.3.2-1/2 |
– |
– |
– |
– |
29 |
The user sets the UE in Automatic SNPN/Network selection mode (NOTE 1). |
– |
– |
– |
– |
30 |
Check: Does the UE send an RRCSetupRequest on NR Cell 4? |
–> |
RRCSetupRequest |
3 |
P |
31-47 |
Steps 3 to 20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 are performed on NR Cell 4. |
– |
– |
– |
– |
NOTE 1: This is performed via MMI or AT command. |
6.5.1.1.3.3 Specific message contents
Table 6.5.1.1.3.3-1: REGISTRATION REQUEST (step 9, 32 Table 6.5.1.1.3.2-3)
Derivation path: TS 38.508-1 Table 4.7.1-6 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
5GS registration type value |
‘001’B |
Initial registration |
6.5.1.2 SNPN Selection in Automatic Mode
6.5.1.2.1 Test Purpose (TP)
(1)
with { UE in Automatic SNPN selection mode and SNPN cell is available for which an entry does not exist in the "list of subscriber data" }
ensure that {
when { UE is switched on or return to coverage }
then { UE does not select the SNPN cell and continues searching for an allowable SNPN Cell }
}
(2)
with { UE in Automatic SNPN selection mode and a Registered SNPN cell along with another better ranked allowable SNPN cell becomes available }
ensure that {
when { UE is switched on or return to coverage }
then { UE selects the Registered SNPN cell and UE attempts a Registration on the selected cell }
}
(3)
with { UE in Automatic SNPN selection mode and Registration on a SNPN cell is unsuccessful}
ensure that {
when { UE continues searching for an allowable SNPN Cell and a new allowable SNPN cell becomes available }
then { the UE registers on the new SNPN cell }
}
6.5.1.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.9.3.1.0 and 4.9.3.1.1. Unless otherwise stated these are Rel-16 requirements.
[TS 23.122, clause 4.9.3.1.0]
At switch on, or following recovery from lack of coverage, the MS selects the registered SNPN (if it is available) using NG-RAN access technology and if necessary (in the case of recovery from lack of coverage, see subclause 4.5.2) attempts to perform an LR.
NOTE 1: The MS in automatic SNPN selection mode can end the SNPN search procedure once the registered SNPN is found on NG-RAN access technology.
NOTE 2: An MS in automatic SNPN selection mode can use location information to determine which SNPNs can be available in its present location.
If successful registration is achieved, the MS indicates the selected SNPN.
If there is no registered SNPN, or registration is not possible due to the SNPN being unavailable or registration failure, the MS follows the procedure in subclause 4.9.3.1.1 or subclause 4.9.3.1.2 depending on its SNPN selection mode. At switch on, the MS shall use the SNPN selection mode that was used before switching off.
NOTE 3: If successful registration is achieved, then the current serving SNPN becomes the registered SNPN and the MS does not store the previous registered SNPN for later use.
If registration is not possible on recovery from lack of coverage due to the registered SNPN being unavailable, an MS may, optionally, continue looking for the registered SNPN for an implementation dependent time.
NOTE 4: An MS registered to an SNPN should behave as described above only if one or more PDU sessions are currently active.
[TS 23.122, clause 4.9.3.1.0]
The MS selects another SNPN, if available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME. If more than one SNPN are available, allowable, and each of them is identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, how the MS selects one of those SNPNs is MS implementation specific.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
Once the MS selects the SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from an entry of the "list of subscriber data" with the SNPN identity matching the selected SNPN.
If successful registration is achieved, the MS indicates the selected SNPN.
If registration cannot be achieved because no SNPNs are available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, the MS indicates "no service" to the user, waits until a new SNPN is available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME and then repeats the procedure.
If there were one or more SNPNs which were available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME but an LR failure made registration on those SNPNs unsuccessful, the MS selects one of those SNPNs again and enters a limited service state.
6.5.1.2.3 Test description
6.5.1.2.3.1 Pre-test conditions
System Simulator:
– 3 SNPN cells NR Cell 1, NR cell 2, NR Cell 3 are configured broadcasting default SNPN IDs as indicated in TS 38.508-1 [4] Table 4.4.2-4.
– System information combination NR-12 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.
UE:
– The UE is in Automatic SNPN selection mode.
– The UE is provisioned with a “list of subscriber data” to allow access to SNPN identified by NR cell 1 and NR cell 3.
Preamble:
– Ensure that the UE has cleared the Registered SNPN. And the UE is in state Switched OFF (state 0-A).
6.5.1.2.3.2 Test procedure sequence
Table 6.5.1.2.3.2-1/2 shows the cell configurations used during the test. Subsequent configurations marked “T1”, “T2” and “T3” are applied at the points indicated in the Main behaviour description in Table 6.5.1.2.3.2-3. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.1.2.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 3 |
Remarks |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
-88 |
“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 |
-88 |
-88 |
“Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“Off” |
-78 |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
Table 6.5.1.2.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 3 |
Remarks |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
“Off” |
FFS |
“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 |
FFS |
FFS |
“Off” |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
“Off” |
FFS |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
Table 6.5.1.2.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts cell levels according to row T1 of table 6.5.1.2.3.2-1/2. |
– |
– |
– |
– |
2 |
Power on the UE. |
– |
– |
– |
– |
3 |
Check: Does the UE transmit an RRCSetupRequest on NR Cell 2 within the next 60 s? |
–> |
NR RRC: RRCSetupRequest |
1 |
F |
4 |
SS adjusts cell levels according to row T2 of table 6.5.1.2.3.2-1/2. |
– |
– |
– |
– |
5 |
Check: Does the UE send a RRCSetupRequest on NR Cell 1? |
–> |
NR RRC: RRCSetupRequest |
1 |
P |
6-23 |
Steps 3 to 20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 1 with ‘connected without release’. |
– |
– |
– |
– |
24 |
The UE is switched off by executing generic procedure in Table 4.9.6.3-1 in TS 38.508-1 [4] |
– |
– |
– |
– |
25 |
SS adjusts cell levels according to row T3 of table 6.5.1.2.3.2-1/2. |
– |
– |
– |
– |
26 |
The UE is Switched ON. |
– |
– |
– |
– |
27 |
Check: Does the UE send a RRCSetupRequest on NR Cell 1? |
–> |
NR RRC: RRCSetupRequest |
2 |
P |
28-34 |
Steps 3-9 of Table 4.5.2.2-2 in TS38.508-1 [4] are performed on NR Cell 1. |
– |
– |
– |
– |
35 |
The SS transmits a REGISTRATION REJECT with cause #75 (Permanently not authorized for this SNPN). |
<– |
NR RRC: DLInformationTransfer 5GMM: REGISTRATION REJECT |
– |
– |
36 |
The SS releases the RRC connection |
– |
– |
– |
– |
37 |
Check: Does the UE send a RRCSetupRequest on NR Cell 3? |
–> |
NR RRC: RRCSetupRequest |
3 |
P |
38-55 |
Steps 3 to 20a1 of Table 4.5.2.2-2 of the generic procedure inTS 38.508-1 [4] are performed on NR Cell 3. |
– |
– |
– |
– |
56 |
The generic test procedure in TS 38.508-1 Table 4.9.6.1-1 of Switch off procedure in RRC_IDLE are performed. |
– |
– |
– |
– |
57 |
The SS configures: – NR Cell 1 as the "Serving cell" – NR Cell 3 as a "Non-Suitable "off" cell ". |
||||
58 |
The UE is brought back to operation or the USIM is inserted. The UE is powered on or switched on. |
– |
– |
– |
– |
59 |
The UE is made to perform manual SNPN search and select SNPN identified by NR Cell 1 (Note 1, Note 2). |
– |
– |
– |
– |
60-78a1 |
Steps 2 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2 are performed on NR Cell 1. |
– |
– |
– |
– |
79 |
The user sets the UE in Automatic SNPN/Network selection mode (Note 1). |
– |
– |
– |
– |
Note 1: This is performed via MMI or AT command. Note 2: Step 59 is to ensure that UE clears NR Cell 1 from the "permanently forbidden SNPNs" list for the next test case. |
6.5.1.2.3.3 Specific message contents
Table 6.5.1.2.3.3-1: REGISTRATION REJECT for NR Cell 1 (step 35 Table 6.5.1.2.3.2-3)
Derivation Path: TS 38.508-1 [4], Table 4.7.1-9 |
|||
Information Element |
Value/remark |
Comment |
Condition |
5GMM cause |
‘01001011’B |
#75 (Permanently not authorized for this SNPN). |
Table 6.5.1.2.3.3-2: REGISTRATION REQUEST (step 39, Table 6.5.1.2.3.2-3)
Derivation path: TS 38.508-1 Table 4.7.1-6 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
5GS registration type value |
‘001’B |
Initial registration |
6.5.1.3 SNPN / User Reselection in Automatic Mode
6.5.1.3.1 Test Purpose (TP)
(1)
with { UE in Automatic SNPN selection mode and registered on an SNPN cell for which an entry exists in the "list of subscriber data" and another SNPN cell is made available for which an entry exists in the "list of subscriber data" }
ensure that {
when { UE is requested to initiate reselection and registration onto an available SNPN }
then { UE reselects to the SNPN cell }
}
6.5.1.3.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 23.122 clauses 4.9.3.2.0 and 4.9.3.2.1. Unless otherwise stated these are Rel-16 requirements.
[TS 23.122, clause 4.9.3.2.0]
At any time the user may request the MS to initiate reselection and registration onto an available SNPN, according to the following procedures, dependent upon the SNPN selection mode of the UE.
[TS 23.122, clause 4.9.3.2.1]
The MS selects an SNPN, if available, allowable, and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME in accordance with the following order:
i) an SNPN, which is available and identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, excluding the previously selected SNPN. If more than one SNPN different from the previously selected SNPN are available, allowable, and each of them is identified by an SNPN identity in an entry of the "list of subscriber data" in the ME, how the MS selects one of those SNPNs is MS implementation specific.
ii) the previously selected SNPN.
The MS shall limit its search for the SNPN to the NG-RAN access technology.
The previously selected SNPN is the SNPN which the MS has selected prior to the start of the user reselection procedure.
Once the MS selects an SNPN, if the selected SNPN is other than the previously selected SNPN, the MS attempts registrations on the selected SNPN using the NG-RAN access technology, the subscriber identifier and the credentials from an entry of the "list of subscriber data" with the SNPN identity matching the selected SNPN.
NOTE: If the previously selected SNPN is selected, and registration has not been attempted on any other SNPNs, then the MS is already registered on the SNPN, and so registration is not necessary.
6.5.1.3.3 Test description
6.5.1.3.3.1 Pre-test conditions
System Simulator:
– 2 SNPN cells NR Cell 1, NR Cell 2 are configured broadcasting default SNPN IDs as indicated in TS 38.508-1 [4] Table 4.4.2-4.
– System information combination NR-12 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cells.
UE:
– The UE is in Automatic SNPN selection mode.
– The UE is provisioned with a “list of subscriber data” to allow access to SNPN identified by NR cell 1 and NR cell 2.
Preamble:
– Ensure that the UE has cleared the Registered SNPN. And the UE is in state Switched OFF (state 0-B).
6.5.1.3.3.2 Test procedure sequence
Table 6.5.1.3.3.2-1/2 shows the cell configurations used during the test. Subsequent configurations marked “T1” and “T2” are applied at the points indicated in the Main behaviour description in Table 6.5.1.3.3.2-3. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.1.3.3.2-1: Time instances of cell power level and parameter changes for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remarks |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
“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 |
-88 |
-88 |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
Table 6.5.1.3.3.2-2: Time instances of cell power level and parameter changes for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
Remarks |
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
“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 |
FFS |
FFS |
Power level “Off” is defined in TS 38.508-1 [4] Table 6.2.2.1-3. |
Table 6.5.1.3.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
SS adjusts cell levels according to row T1 of table 6.5.1.3.3.2-1/2. |
– |
– |
– |
– |
2 |
Power on the UE. |
– |
– |
– |
– |
3-22 |
Steps 1 to 20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 1 with ‘connected without release’. |
– |
– |
– |
– |
23 |
SS adjusts cell levels according to row T2 of table 6.5.1.3.3.2-1/2. |
– |
– |
– |
– |
24 |
Cause the UE in Automatic network selection mode to initiate user reselection and registration onto an available SNPN identified by NR cell 2. (Note 1) |
– |
– |
– |
– |
25 |
Check: Does the UE send a RRCSetupRequest on NR Cell 2? |
–> |
NR RRC: RRCSetupRequest |
1 |
P |
26-44a1 |
Steps 2 to 20a1 of the generic test procedure in TS 38.508-1 Table 4.5.2.2-2 are performed on NR Cell 2. (Note 2) |
– |
– |
– |
– |
Note 1: MMI command “TRIGGER_USER_RESELECTION” to be used. AT command AT+COPS is not suitable to achieve the test purpose. Note 2: The 5GS registration type shall be only set as ‘Initial Registration’ according to TS 24.501 subclause 5.2.3.2.5 specified in Release 16. |
6.5.1.3.3.3 Specific message contents
Table 6.5.1.3.3.3-1: REGISTRATION REQUEST (step 27, Table 6.5.1.3.3.2-3)
Derivation path: TS 38.508-1 Table 4.7.1-6 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
5GS registration type value |
‘001’B |
Initial registration |
6.5.2 CAG (Closed Access Group)
6.5.2.1 CAG Selection in Manual Mode
6.5.2.1.1 Test Purpose (TP)
(1)
with { UE in Manual network selection mode and provided with CAG information list }
ensure that {
when { there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is included in the "Allowed CAG list" }
then { UE manually selects the CAG cell }
}
(2)
with { UE in Manual network selection mode and PLMN ID of the PLMN in the "CAG information list" and the CAG-ID are not included in the "Allowed CAG list" }
ensure that {
when { the available CAG cell broadcasts that the PLMN allows a user to manually select the CAG-ID }
then { UE manually selects the CAG cell that is outside the UE’s Allowed CAG list }
}
(3)
with { UE in Manual network selection mode }
ensure that {
when { there exists an entry for the presented PLMN in the "CAG information list" and the entry includes an "indication that the MS is only allowed to access 5GS via CAG cells" }
then { UE manually selects the CAG cell }
}
6.5.2.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122, clause 4.4.3.1.2. Unless otherwise stated these are Rel-16 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) or stored in the ME (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 i to v, if the MS supports CAG, for each PLMN/access technology combination of NG-RAN access technology, the MS shall present to the user:
a) the PLMN/access technology combination and a list of CAG-IDs composed of one or more CAG-IDs such that for each CAG-ID:
1) there is an available CAG cell which broadcasts the CAG-ID for the PLMN; and
2) the following is true:
i) there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is included in the "Allowed CAG list" of the entry; or
ii) the available CAG cell broadcasting the CAG-ID for the PLMN also broadcasts that the PLMN allows a user to manually select the CAG-ID.
For each of the presented CAG-ID, the MS may indicate to the user whether the CAG-ID is present in the "Allowed CAG list" stored in the UE; and
b) the PLMN/access technology combination without a list of CAG-IDs, if there is an available NG-RAN cell which is not a CAG cell for the PLMN. If there exists an entry for the presented PLMN in the "CAG information list" and the entry includes an "indication that the MS is only allowed to access 5GS via CAG cells", the MS may indicate to the user that the MS is only allowed to access the PLMN via CAG cells.
6.5.2.1.3 Test description
6.5.2.1.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2 and NR Cell 4.
– NR Cell 2 and NR Cell 4 are CAG cells.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used for NR Cell 1, NR Cell 2 and NR Cell 4.
– The PLMNs are identified in the test by the identifiers in Table 6.5.2.1.3.1-1 and the PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.
Table 6.5.2.1.3.1–1: PLMN and CAG identifiers
NR Cell |
PLMN name |
CAG IDs |
1 |
PLMN 1 |
– |
2 |
PLMN 3 |
1 |
4 |
PLMN 2 |
2 |
UE:
None.
Preamble:
– The UE is registered on NR Cell 1 using the procedure described in TS 38.508-1 [4] clause 4.5.2.2 except that the REGISTRATION ACCEPT message includes CAG information list with CAG-ID 1.
– The UE is set to Manual PLMN selection mode before it is in state Switched OFF (State 0N-B) as per TS 38.508-1 [4] Table 4.4A.2-0.
6.5.2.1.3.2 Test procedure sequence
Table 6.5.2.1.3.2-1 for FR1 and Table 6.5.2.1.3.2-2 for FR2 illustrate the downlink power to be applied for the cells at various time instants of the test execution. The configuration T0 indicates the initial conditions for preamble. Configurations marked "T1", "T2" and "T3"are applied at the points indicated in the Main behaviour description in Table 6.5.2.1.3.2-3.
Table 6.5.2.1.3.2-1: Time instances of cell power level and parameter changes for FR1
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
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 |
"Off" |
-88 |
"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" |
"Off" |
-88 |
Power level "Off" is defined in TS 38.508-1 [4] Table 6.2.2.1-3 |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
”Off” |
-88 |
"Off" |
Power level "Off" is defined in TS 38.508-1 [4] Table 6.2.2.1-3 |
Table 6.5.2.1.3.2-2: Time instances of cell power level and parameter changes for FR2
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
Remarks |
|
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
FFS |
FFS |
Table 6.5.2.1.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes cell power levels according to row "T1" in Table 6.5.2.1.3.2-1 for FR1 and Table 6.5.2.1.3.2-2 for FR2. |
– |
– |
– |
– |
2 |
The UE is switched on. |
– |
– |
– |
– |
3 |
The UE is made to perform manual CAG selection and selects NR Cell 2. |
– |
– |
– |
– |
4 |
Check: Does the UE send a RRCSetupRequest on NR Cell 2? |
–> |
NR RRC: RRCSetupRequest |
1 |
P |
5-22 |
Steps 3-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 2. Note: The UE performs initial registration procedure with REGISTRATION ACCEPT message including CAG information list with PLMN ID 2 and CAG only indication and the RRC connection is released. |
– |
– |
– |
– |
23 |
The SS changes cell power levels according to row "T2" in Table 6.5.2.1.3.2-1 for FR1 and Table 6.5.2.1.3.2-2 for FR2. |
– |
– |
– |
– |
24 |
The UE is made to perform manual CAG selection and select NR Cell 4. |
– |
– |
– |
– |
25 |
Void |
– |
– |
– |
– |
26-27A |
Steps 1 to 3 of the test procedure to check that UE is camped on a new cell belonging to a new TA as specified in TS 38.508-1 [4] subclause 4.9.5 are performed on NR Cell 4. |
– |
– |
2 |
P |
28-36 |
Void |
– |
– |
– |
– |
37 |
The SS transmits a DLInformationTransfer message and a REGISTRATION ACCEPT message. |
<– |
NR RRC: DLInformationTransfer 5G MM: REGISTRATION ACCEPT |
– |
– |
38-39 |
Steps 5 to 6a1 of the test procedure to check that UE is camped on a new cell belonging to a new TA as specified in TS 38.508-1 [4] subclause 4.9.5 are performed on NR Cell 4. |
– |
– |
– |
– |
40-43 |
Void |
– |
– |
– |
– |
44 |
Void |
– |
– |
– |
– |
45 |
Void |
– |
– |
– |
– |
46 |
Void |
– |
– |
– |
– |
46A |
The SS changes cell power levels according to row "T3" in Table 6.5.2.1.3.2-1 for FR1 and Table 6.5.2.1.3.2-2 for FR2. |
– |
– |
– |
– |
47 |
The UE is made to perform manual CAG selection and select NR Cell 2. |
– |
– |
||
48 |
Void |
– |
– |
– |
– |
49-53A |
Steps 1-6a1 of the test procedure to check that UE is camped on a new cell belonging to a new TA as specified in TS 38.508-1 [4] subclause 4.9.5 are performed on NR Cell 2. |
– |
– |
3 |
P |
6.5.2.1.3.3 Specific message contents
Table 6.5.2.1.3.3-1: REGISTRATION REQUEST (Preamble)
Derivation path: TS 38.508-1 [4], Table 4.7.1-6 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
5GS registration type |
‘0000 0001’B |
Initial registration |
|
5GMM capability |
|||
CAG |
‘1’B |
CAG supported |
Table 6.5.2.1.3.3-2: REGISTRATION ACCEPT (Preamble)
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 003; MNC : 21; CAG only : 0; CAG-ID 1 : 1 |
||
Length of CAG information list contents |
0000 0000 ‘0000 1001’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1000’B |
||
MCC |
MCC of NR Cell 2 |
See TS 38.508-1 [4] Table 4.4.2-3 |
|
MNC |
MNC of NR Cell 2 |
See TS 38.508-1 [4] Table 4.4.2-3 |
|
CAG only |
‘0’B |
||
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
Table 6.5.2.1.3.3-3: REGISTRATION ACCEPT (Step 16, Table 6.5.2.1.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 003; MNC : 21; CAG only : 1; CAG-ID 1 : 1 |
||
Length of CAG information list contents |
‘0000 0000 0000 1001’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1000’B |
||
MCC |
MCC of NR Cell 2 |
See TS 38.508-1 [4] Table 4.4.2-3 |
|
MNC |
MNC of NR Cell 2 |
See TS 38.508-1 [4] Table 4.4.2-3 |
|
CAG only |
‘1’B |
||
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
Table 6.5.2.1.3.3-4: SIB1 for NR Cell 4 (all steps in T2, Table 6.5.2.1.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
plmn-Identity-r16 SEQUENCE { |
|||
mcc |
002 |
PLMN2 MCC |
|
mnc |
11 |
PLMN2 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entr 1 |
||
cag-Identity-r16 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
|
manualCAGselectionAllowed-r16 |
true |
||
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 4 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 4 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 6.5.2.1.3.3-5: SIB1 for NR Cell 2 (all steps in Table 6.5.2.1.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
plmn-Identity-r16 SEQUENCE { |
|||
mcc |
003 |
PLMN3 MCC |
|
mnc |
21 |
PLMN3 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-Identity-r16 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
manualCAGselectionAllowed-r16 |
true |
||
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 2 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 2 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
6.5.2.2 CAG Selection in Automatic Mode
6.5.2.2.1 Test Purpose (TP)
(1)
with { UE in Automatic network selection mode and provisioned with an empty "CAG information list” }
ensure that {
when { UE is switched on or returned to coverage, and a cell which is not a CAG cell becomes available }
then { UE selects the cell }
}
(2)
with { UE in Automatic network selection mode provisioned with a "CAG information list” }
ensure that {
when { UE is switched on or returned to coverage, and a CAG cell with a CAG-ID present in the "Allowed CAG list" becomes available }
then { UE selects the CAG cell }
}
(3)
with { UE in Automatic network selection mode provisioned with a "CAG information list” }
ensure that {
when { UE is switched on and a cell which is not a CAG cell becomes available, and there is an entry with the PLMN ID of the PLMN in the "CAG information list" but the "indication that the MS is only allowed to access 5GS via CAG cells" is not included in the entry }
then { UE selects the cell }
}
6.5.2.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clauses 3.8, and 4.4.3.1.1. Unless otherwise stated these are Rel-16 requirements.
[TS 23.122, clause 3.8]
The MS may support CAG.
If the MS supports CAG, the MS can be provisioned with a "CAG information list", consisting of zero or more entries, each containing:
a) a PLMN ID;
b) an "Allowed CAG list". The "Allowed CAG list" contains zero or more CAG-IDs; and
c) an optional "indication that the MS is only allowed to access 5GS via CAG cells".
The "CAG information list" is stored in the ME.
NOTE: When the UE is registering or registered to a PLMN other than the HPLMN or EHPLMN, then the HPLMN will send a "CAG information list" consisting of CAG subscription information related to the serving PLMN only. When the UE is registering or registered to the HPLMN or EHPLMN then the HPLMN or EHPLMN can send CAG subscription information related to any PLMN in the "CAG information list".
If the MS supports CAG and a PLMN is selected as described in subclause 4.4.3.1.1, the automatic CAG selection is performed as part of subclause 4.4.3.1.1.
If the MS supports CAG and a PLMN is selected as described in subclause 4.4.3.1.2, the manual CAG selection is performed as part of subclause 4.4.3.1.2.
The NAS shall provide the AS with a "CAG information list", if available. If the contents of the "CAG information list" have changed, the NAS shall provide an updated "CAG information list" to the AS.
[TS 23.122, clause 4.4.3.1.1]
The MS selects and attempts registration on other PLMN/access technology combinations, if available and allowable, in the following order:
i) either the HPLMN (if the EHPLMN list is not present or is empty) or the highest priority EHPLMN that is available (if the EHPLMN list is present) ;
ii) each PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
iii) each PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (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.
When following the above procedure the following requirements apply:
…
m) In i to v, if the MS supports CAG and:
1) is provisioned with a non-empty "CAG information list", the MS shall consider a PLMN indicated by an NG-RAN cell only if:
A) the cell is a CAG cell and broadcasts a CAG-ID for the PLMN such that there exists an entry with the PLMN ID of the PLMN in the "CAG information list" and the CAG-ID is included in the "Allowed CAG list" of the entry; or
B) the cell is not a CAG cell and:
– there is no entry with the PLMN ID of the PLMN in the "CAG information list"; or
– there exists an entry with the PLMN ID of the PLMN in the "CAG information list" but the "indication that the MS is only allowed to access 5GS via CAG cells" is not included in the entry; or
2) is provisioned with an empty "CAG information list" or is not provisioned with a "CAG information list", the MS shall consider a PLMN indicated by an NG-RAN cell only if the cell is not a CAG cell.
n) In i to v, if the MS only supports control plane CIoT 5GS optimization (see 3GPP TS 23.501 [62]) and the MS camps on an E-UTRA cell connected to 5GCN, which is not NB-IoT cell (see 3GPP TS 36.304 [43], 3GPP TS 36.331 [22]), the MS shall not consider PLMNs which do not advertise support of 5GS services with control plane CIoT 5GS optimization.
o) In i to v, if the MS supports CIoT 5GS optimizations, the MS shall not consider the PLMN/access technology combinations for which the MS preferred CIoT network behaviour is not advertised as supported by the PLMN/access technology combination (see 3GPP TS 24.501 [64]).
NOTE 7: As an implementation option, the MS supporting CIoT 5GS optimizations that was not able to select any PLMN according to o) can perform a second iteration of i to v with no restriction.
p) In iii, the MS shall use the PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" stored in the ME, if the last received steering of roaming information contains the "list of preferred PLMN/access technology combinations"(see annex C) and is stored in the ME. Otherwise, the MS shall use the "Operator Controlled PLMN Selector with Access Technology" list retrieved from the SIM.
If successful registration is achieved, the MS indicates the selected PLMN.
If registration cannot be achieved because no PLMNs are available and allowable, and the MS does not support access to RLOS, the MS indicates "no service" to the user, waits until a new PLMN is available and allowable and then repeats the procedure.
If there were one or more PLMNs which were available and allowable, but an LR failure made registration on those PLMNs unsuccessful or an entry in any of the lists "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", or "CAG information list" prevented a registration attempt, the MS selects the first such PLMN again and enters a limited service state.
…
6.5.2.2.3 Test description
6.5.2.2.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2, NR Cell 4 and NR Cell 11.
– NR Cell 2 and NR Cell 4 are CAG cells.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used for NR Cell 1, NR Cell 2, NR Cell 4 and NR Cell 11.
– The PLMNs are identified in the test by the identifiers in Table 6.5.2.2.3.1-1 and the PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.
Table 6.5.2.2.3.1-1: PLMN identifiers
NR Cell |
PLMN name |
CAG IDs |
|||
2 |
PLMN2 |
1 |
|||
4 |
PLMN3 |
2 |
|||
11 |
PLMN2 |
– |
UE:
– The UE is in Automatic PLMN selection mode.
– There is an empty “CAG information list” provisioned in the UE.
Preamble:
– The UE is registered on NR Cell 1 using the procedure described in TS 38.508-1 [4] clause 4.5.2.2 except that the REGISTRATION ACCEPT message includes an empty CAG information list before it is in state Switched OFF (State 0N-B).
6.5.2.2.3.2 Test procedure sequence
Table 6.5.2.2.3.2-1 for FR1 and 6.5.2.2.3.2-2 for FR2 illustrate the downlink power levels 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. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.2.2.3.2-1: Cell configuration changes over time for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
NR Cell 11 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
"Off" |
"Off" |
"Off" |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
-88 |
"Off" |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
-88 |
"Off" |
"Off" |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
"Off" |
-88 |
Table 6.5.2.2.3.2-2: Cell configuration changes over time for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
NR Cell 11 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
"Off" |
FFS |
"Off" |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
FFS |
"Off" |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
FFS |
FFS |
"Off" |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
"Off" |
FFS |
Table 6.5.2.2.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
Power on the UE. |
– |
– |
– |
– |
2 |
Check: Does the UE send a RRCSetupRequest on NR Cell 1? |
–> |
NR RRC: RRCSetupRequest |
1 |
P |
3-13 |
Steps 3 to 13 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 1. NOTE: The UE starts registration. |
– |
– |
– |
– |
14 |
The SS transmits a DLInformationTransfer message and a REGISTRATION ACCEPT message containing the CAG information list with the CAG ID of NR Cell 2. |
<– |
NR RRC: DLInformationTransfer 5G MM: REGISTRATION ACCEPT |
– |
– |
15-20a1 |
Steps 15 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 1. NOTE: The UE completes registration and the RRC connection is released. |
– |
– |
– |
– |
21 |
The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4] |
– |
– |
– |
– |
22 |
SS adjusts cell levels according to row T1 of table 6.5.2.2.3.2-1 for FR1 and table 6.5.2.2.3.2-2 for FR2. |
– |
– |
– |
– |
23 |
Power on the UE. |
– |
– |
– |
– |
24 |
Check: Does the UE send a RRCSetupRequest on NR Cell 4 within the next 60 s? |
–> |
NR RRC: RRCSetupRequest |
2 |
F |
25 |
SS adjusts cell levels according to row T2 of table 6.5.2.2.3.2-1 for FR1 and table 6.5.2.2.3.2-2 for FR2. |
– |
– |
– |
– |
26 |
Check: Does the UE send a RRCSetupRequest on NR Cell 2? |
–> |
NR RRC: RRCSetupRequest |
2 |
P |
27-44a1 |
Steps 3 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 2. NOTE: The UE completes registration and the RRC connection is released. |
– |
– |
– |
– |
45 |
The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4] |
– |
– |
– |
– |
46 |
SS adjusts cell levels according to row T3 of table 6.5.2.2.3.2-1 for FR1 and table 6.5.2.2.3.2-2 for FR2. |
– |
– |
– |
– |
47 |
Power on the UE. |
– |
– |
– |
– |
48 |
Check: Does the UE send a RRCSetupRequest on NR Cell 11? |
–> |
NR RRC: RRCSetupRequest |
3 |
P |
49-66a1 |
Steps 3 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 11. NOTE: The UE performs registration and the RRC connection is released. |
– |
– |
– |
– |
6.5.2.2.3.3 Specific message contents
Table 6.5.2.2.3.3-1: REGISTRATION ACCEPT (step 14, Table 6.5.2.2.3.2-3)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 002; MNC : 11; CAG only : 0; CAG-ID 1 : 1 |
||
Length of CAG information list contents |
‘0000 0000 0001 0010’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1000’B |
||
MCC |
MCC of NR Cell 2 |
See Table 6.5.2.2.3.1-1 |
|
MNC |
MNC of NR Cell 2 |
See Table 6.5.2.2.3.1-1 |
|
CAG only |
‘0’B |
||
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
Entry 1 |
|||
Length of entry contents |
‘0000 1000’B |
||
MCC |
MCC of NR Cell 4 |
See Table 6.5.2.2.3.1-1 |
|
MNC |
MNC of NR Cell 4 |
See Table 6.5.2.2.3.1-1 |
|
CAG only |
‘1’B |
||
CAG_ID 1 |
4 |
CAG ID is coded as a 32 bit BITSTRING |
|
Equivalent PLMNs |
PLMN2 |
Table 6.5.2.2.3.3-2: REGISTRATION ACCEPT (Preamble)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
|||
Length of CAG information list contents |
‘0000 0000’B |
||
Entry 1 |
Not present |
Table 6.5.2.2.3.3-3: SIB1 for NR Cell 2 (all steps in Table 6.5.2.2.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
plmn-Identity-r16 SEQUENCE { |
|||
mcc |
002 |
PLMN2 MCC |
|
mnc |
11 |
PLMN2 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-Identity-r16 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 2 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 2 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 6.5.2.2.3.3-4: SIB1 for NR Cell 4 (all steps in Table 6.5.2.2.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
plmn-Identity-r16 SEQUENCE { |
|||
mcc |
003 |
PLMN3 MCC |
|
mnc |
21 |
PLMN3 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-Identity-r16 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
|
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 4 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 4 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
6.5.2.3 CAG / Limited Service / No Suitable cell
6.5.2.3.1 Test Purpose (TP)
(1)
with { UE in Automatic network selection mode provisioned with a "CAG information list” }
ensure that {
when { UE is switched on or returned to coverage, and a CAG cell with a CAG-ID not present in the "Allowed CAG list" becomes available }
then { UE does not select the CAG cell }
}
(2)
with { UE in Automatic network selection mode configured with "indication that the MS is only allowed to access 5GS via CAG cells" }
ensure that {
when { UE is switched on and a cell which is not a CAG cell becomes available, and there is an entry with the PLMN ID of the PLMN in the "CAG information list" but the "indication that the MS is only allowed to access 5GS via CAG cells" is included in the entry }
then { UE does not select the CAG cell }
}
(3)
with { UE in Automatic network selection mode provisioned with an empty "CAG information list” }
ensure that {
when { UE is switched on or returned to coverage, and a CAG cell with a PLMN ID becomes available }
then { UE does not select the CAG cell }
}
6.5.2.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 23.122 clause 3.5. Unless otherwise stated these are Rel-16 requirements.
[TS 23.122, clause 3.5]
There are a number of situations in which the MS is unable to obtain normal service from a PLMN or SNPN. These include:
…
i) MS supporting CAG is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and none of the CAG-ID(s) of the CAG cell are present in the "Allowed CAG list" associated with that PLMN in the "CAG information list";
j) MS supporting CAG is camped on a non-CAG cell belonging to a PLMN, the PLMN ID of the non-CAG cell without a CAG-ID is not manually selected by the user and the UE is configured with "indication that the MS is only allowed to access 5GS via CAG cells" for that PLMN in the "CAG information list"; and
k) MS supporting CAG is camped on a CAG cell belonging to a PLMN, the CAG-ID of the CAG cell is not manually selected by the user and the "CAG information list" does not contain an entry for the PLMN (e.g. because the UE is not (pre-)configured with a "CAG information list").
6.5.2.3.3 Test description
6.5.2.3.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 2, NR Cell 4 and NR Cell 11.
– NR Cell 2 and NR Cell 4 are CAG cells.
– System information combination NR-2 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used for NR Cell 1, NR Cell 2, NR Cell 4 and NR Cell 11.
– The PLMNs are identified in the test by the identifiers in Table 6.5.2.3.3.1-1 and the PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.
Table 6.5.2.3.3.1-1: PLMN identifiers
NR Cell |
PLMN name |
CAG IDs |
1 |
PLMN1 |
– |
2 |
PLMN1 |
1 |
4 |
PLMN1 |
2 |
11 |
PLMN1 |
– |
UE:
– The UE is in Automatic PLMN selection mode.
– There is an empty “CAG information list” provisioned in the UE.
Preamble:
– The UE is registered on NR Cell 1 using the procedure described in TS 38.508-1 [4] clause 4.5.2.2 except that the REGISTRATION ACCEPT message includes an empty CAG information list before it is in state Switched OFF (State 0N-B).
6.5.2.3.3.2 Test procedure sequence
Table 6.5.2.3.3.2-1 for FR1 and 6.5.2.3.3.2-2 for FR2 illustrate the downlink power levels 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", "T3" 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. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.2.3.3.2-1: Cell configuration changes over time for FR1
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
NR Cell 11 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
-88 |
"Off" |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
-88 |
"Off" |
"Off" |
"Off" |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
-88 |
"Off" |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
-88 |
"Off" |
"Off" |
|
T4 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
"Off" |
-88 |
Table 6.5.2.3.3.2-2: Cell configuration changes over time for FR2
|
Parameter |
Unit |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
NR Cell 11 |
Remarks |
T0 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
FFS |
"Off" |
|
T1 |
SS/PBCH SSS EPRE |
dBm/SCS |
FFS |
"Off" |
"Off" |
"Off" |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
FFS |
"Off" |
|
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
FFS |
"Off" |
"Off" |
|
T4 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
"Off" |
"Off" |
FFS |
Table 6.5.2.3.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
Power on the UE. |
– |
– |
– |
– |
2 |
Check: Does the UE send a RRCSetupRequest on NR Cell 4 within the next 60 s? |
–> |
NR RRC: RRCSetupRequest |
3 |
F |
3 |
SS adjusts cell levels according to row T1 of table 6.5.2.3.3.2-1 for FR1 and table 6.5.2.3.3.2-2 for FR2. |
– |
– |
– |
– |
4-16 |
Steps 1 to 13 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 1. NOTE: The UE starts registration. |
– |
– |
– |
– |
17 |
The SS transmits a DLInformationTransfer message and a REGISTRATION ACCEPT message containing the CAG information list with the CAG ID of NR Cell 2. |
<– |
NR RRC: DLInformationTransfer 5G MM: REGISTRATION ACCEPT |
– |
– |
18-23a1 |
Steps 15 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 1. NOTE: The UE completes registration and the RRC connection is released. |
– |
– |
– |
– |
24 |
The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4] |
– |
– |
– |
– |
25 |
SS adjusts cell levels according to row T2 of table 6.5.2.3.3.2-1 for FR1 and table 6.5.2.3.3.2-2 for FR2. |
– |
– |
– |
– |
26 |
Power on the UE. |
– |
– |
– |
– |
27 |
Check: Does the UE send a RRCSetupRequest on NR Cell 4 within the next 60 s? |
–> |
NR RRC: RRCSetupRequest |
1 |
F |
28 |
SS adjusts cell levels according to row T3 of table 6.5.2.3.3.2-1 for FR1 and table 6.5.2.3.3.2-2 for FR2. |
– |
– |
– |
– |
29-47a1 |
Steps 1 to 20a1 of the registration procedure described in TS 38.508-1 [4] subclause 4.5.2.2 are performed on NR Cell 2. NOTE: The UE completes registration and the RRC connection is released. |
– |
– |
– |
– |
48 |
The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4] |
– |
– |
– |
– |
49 |
SS adjusts cell levels according to row T4 of table 6.5.2.3.3.2-1 for FR1 and table 6.5.2.3.3.2-2 for FR2. |
– |
– |
– |
– |
50 |
Power on the UE. |
– |
– |
– |
– |
51 |
Check: Does the UE send a RRCSetupRequest on NR Cell 11 within the next 60 s? |
–> |
NR RRC: RRCSetupRequest |
2 |
F |
6.5.2.3.3.3 Specific message contents
Table 6.5.2.3.3.3-1: REGISTRATION REQUEST (Preamble)
Derivation path: TS 38.508-1 [4], Table 4.7.1-6 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
5GS registration type |
‘0000 0001’B |
Initial registration |
|
5GMM capability |
|||
CAG |
‘1’B |
CAG supported |
Table 6.5.2.3.3.3-2: REGISTRATION ACCEPT (Preamble)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
|||
Length of CAG information list contents |
‘0000 0000 0000 0000’B |
||
Entry 1 |
Not present |
Table 6.5.2.3.3.3-3: REGISTRATION ACCEPT (step 17, Table 6.5.2.3.3.2-3)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 002; MNC : 11; CAG only : 0; CAG-ID 1 : 1 |
||
Length of CAG information list contents |
‘0000 0000 0000 1001’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1000’B |
||
MCC |
MCC of NR Cell 2 |
See Table 6.5.2.3.3.1-1 |
|
MNC |
MNC of NR Cell 2 |
See Table 6.5.2.3.3.1-1 |
|
CAG only |
‘0’B |
||
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
Table 6.5.2.3.3.3-4: REGISTRATION ACCEPT (step 42, Table 6.5.2.3.3.2-3)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 002; MNC : 11; CAG only : 0; CAG-ID 1 : 1 |
||
Length of CAG information list contents |
‘0000 0000 0000 1001’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1000’B |
||
MCC |
MCC of NR Cell 11 |
See Table 6.5.2.3.3.1-1 |
|
MNC |
MNC of NR Cell 11 |
See Table 6.5.2.3.3.1-1 |
|
CAG only |
‘1’B |
Indication that the UE is only allowed to access 5GS via CAG cells (CAGonly) |
|
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
Table 6.5.2.3.3.3-5: SIB1 for NR Cell 4 (all steps in Table 6.5.2.3.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
plmn-Identity-r16 SEQUENCE { |
|||
mcc |
001 |
PLMN1 MCC |
|
mnc |
01 |
PLMN1 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-Identity-r16 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
|
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 4 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 4 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 6.5.2.3.3.3-6: SIB1 for NR Cell 2 (all steps in Table 6.5.2.3.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
plmn-Identity-r16 SEQUENCE { |
|||
mcc |
001 |
PLMN1 MCC |
|
mnc |
01 |
PLMN1 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-Identity-r16 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 2 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 2 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
6.5.2.4 CAG / cell reselection / Within allowed CAG / non-CAG cell to CAG cell
6.5.2.4.1 Test Purpose (TP)
(1)
with { UE in NR RRC_IDLE state on a non-CAG cell and UE’s Allowed CAG list is not empty }
ensure that {
when { UE detects an allowed CAG cell which becomes highest ranked cell }
then { UE reselects to the CAG cell }
}
(2)
with { UE in NR RRC_IDLE state }
ensure that {
when { UE detects the cell re-selection criteria are met for the CAG cell which belongs to the higher priority frequency }
then { UE reselects the cell which belongs to the higher priority frequency }
}
6.5.2.4.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.304: clauses 5.2.4.2, 5.2.4.5, 5.2.4.6 and 5.2.4.10. Unless otherwise stated these are Rel-16 requirements.
[TS 38.304, clause 5.2.4.2]
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-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority;
– Otherwise, the UE shall perform measurements of NR inter-frequency cells of equal or lower priority, or inter-RAT frequency cells of lower priority according to TS 38.133 [8].
– If the UE supports relaxed measurement and relaxedMeasurement is present in SIB2, the UE may further relax the needed measurements, as specified in clause 5.2.4.9.
[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 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, the highest ranked cell among the cells on the highest priority frequency(ies) meeting the criteria according to clause 5.2.4.6;
– If the highest-priority frequency is from another RAT, the strongest cell among the cells on the highest priority frequency(ies) meeting the criteria of that RAT.
[TS 38.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
Rs = Qmeas,s +Qhyst – Qoffsettemp Rn = Qmeas,n -Qoffset – Qoffsettemp |
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency. |
Qoffsettemp |
Offset temporarily applied to a cell as specified in TS 38.331 [3]. |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2.
The cells shall be ranked according to the R criteria specified above by deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If rangeToBestCell is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is found to be not-suitable, the UE shall behave according to clause 5.2.4.4.
If rangeToBestCell is configured, then the UE shall perform cell reselection to the cell with the highest number of beams above the threshold (i.e. absThreshSS-BlocksConsolidation) among the cells whose R value is within rangeToBestCell of the R value of the highest ranked cell. If there are multiple such cells, the UE shall perform cell reselection to the highest ranked cell among them. If this cell is found to be not-suitable, the UE shall behave according to clause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better than the serving cell according to the cell reselection criteria specified above during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
NOTE: If rangeToBestCell is configured but absThreshSS-BlocksConsolidation is not configured on an NR frequency, the UE considers that there is one beam above the threshold for each cell on that frequency.
[TS 38.304, clause 5.2.4.10]
In addition to normal cell reselection, a UE may optionally use an autonomous search function to detect CAG cells on serving and non-serving frequencies. However UE shall follow the cell reselection criteria based on dedicated frequency priorities and only follow the autonomous cell search result if the result fulfils also the existing cell reselection criteria based on dedicated frequency priorities.
6.5.2.4.3 Test description
6.5.2.4.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 3 and NR Cell 6.
– NR Cell 3 and NR Cell 6 are CAG cells.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used for NR Cell 1, NR Cell 3 and NR Cell 6.
– The PLMNs are identified in the test by the identifiers in Table 6.5.2.4.3.1-1 and the PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.
Table 6.5.2.4.3.1–1: PLMN and CAG identifiers
NR Cell |
PLMN name |
CAG IDs |
1 |
PLMN 1 |
– |
3 |
PLMN 2 |
1 |
6 |
PLMN 2 |
2 |
UE:
– There is no “CAG information list” provisioned in the UE.
Preamble:
– The UE is registered on NR Cell 1 and is brought to state 1N-A, RRC_IDLE Connectivity (NR), in accordance with the procedure described in TS 38.508-1 [4] Table 4.5.2.2-2, except that the REGISTRATION ACCEPT message includes CAG information list with CAG-ID 1 and CAG-ID 2, and that the REGISTRATION ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described in Table 6.5.2.4.3.3-1.
6.5.2.4.3.2 Test procedure sequence
Table 6.5.2.4.3.2-1/2 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions for preamble. Subsequent configurations marked “T1” and “T2” are applied at the points indicated in the Main behaviour description in Table 6.5.2.4.3.2-3. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.2.4.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 |
Remarks |
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, high. |
Table 6.5.2.4.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 |
Remarks |
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, high. |
Table 6.5.2.4.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS changes cell power levels according to row "T1" in Table 6.5.2.4.3.2-1 for FR1 and Table 6.5.2.4.3.2-2 for FR2. |
– |
– |
– |
– |
2 |
Check: Does the UE transmit an RRCSetupRequest message on NR Cell 3? |
–> |
NR RRC: RRCSetupRequest |
1 |
P |
3-7a1 |
Steps 2 to 6a1 of the mobility registration updating procedure described in TS 38.508-1 [4] Table 4.9.5.2.2-1 are performed on NR Cell 3. |
– |
– |
– |
– |
8 |
SS adjusts cell levels according to row T2 of table 6.5.2.4.3.2-1/2. |
– |
– |
– |
– |
9 |
Wait for 34[FR1]/130[FR2] seconds to allow UE to recognise the change. |
– |
– |
– |
– |
10 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.4.2.2-1 indicate that the UE is camped on NR Cell 6? |
– |
– |
2 |
– |
Note: The wait time at step 9 is Kcarrier*Tdetect,NR_Inter (as per TS 38.133 [30], clause 4.2.2.4). |
6.5.2.4.3.3 Specific message contents
Table 6.5.2.4.3.3-1: REGISTRATION ACCEPT for NR Cell 1 (preamble)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC: 002; MNC: 11; CAG only: 0; CAG-ID 1: 1; CAG-ID 2: 2 |
||
Length of CAG information list contents |
‘0000 0000 0000 1101’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1100’B |
||
MCC |
MCC of PLMN 2 |
See Table 6.5.2.4.3.1–1 |
|
MNC |
MNC of PLMN 2 |
See Table 6.5.2.4.3.1–1 |
|
CAG only |
‘0’B |
||
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
Equivalent PLMNs |
PLMN2 |
||
CAG_ID 2 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
Table 6.5.2.4.3.3-2: SIB2 of NR Cell 6 (preamble and all steps, Table 6.5.2.4.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.5.2.4.3.3-3: SIB4 of NR Cell 3 (preamble and all steps, Table 6.5.2.4.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 { |
1 entry |
||
InterFreqCarrierFreqInfo[1] SEQUENCE { |
entry 1 |
||
dl-CarrierFreq |
Same downlink ARFCN as used for NR Cell 6 |
||
threshX-HighP |
10 |
20 dB |
FR1 |
9 |
18 dB |
FR2 |
|
cellReselectionPriority |
5 |
||
} |
|||
} |
|||
} |
Table 6.5.2.4.3.3-4: SIB4 of NR Cell 1 (preamble and all steps, Table 6.5.2.4.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 ARFCN as used for NR Cell 6 |
||
cellReselectionPriority |
5 |
||
} |
|||
InterFreqCarrierFreqInfo[2] SEQUENCE { |
entry 2 |
||
dl-CarrierFreq |
Same downlink ARFCN as used for NR Cell 3 |
||
cellReselectionPriority |
4 |
||
} |
|||
} |
|||
} |
6.5.2.5 Void
6.5.2.6 CAG / cell reservation
6.5.2.6.1 Test Purpose (TP)
(1)
with { UE in Automatic network selection mode and provisioned with "CAG information list }
ensure that {
when { UE is switched on or returns to coverage, and a cell which is not a CAG cell with cell status “true” for other use becomes available }
then { UE does not attempt to reselect to the higher ranked cell }
}
(2)
with { UE camped normally in state NR RRC_IDLE on a CAG cell and UE’s Allowed CAG list is not empty }
ensure that {
when { a higher ranked CAG cell is found with cell status as “not barred” and “not reserved” for operator use and “true” for other use, and not “true” for future use }
then { UE does reselect to the higher ranked cell }
}
6.5.2.6.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.304: clauses 5.2.4.4, 5.2.4.6 and 5.3.1. Unless otherwise stated these are Rel-16 requirements.
[TS 38.304, clause 5.2.4.4]
For the highest ranked cell (including serving cell) according to cell reselection criteria specified in clause 5.2.4.6, for the best cell according to absolute priority reselection criteria specified in clause 5.2.4.5, the UE shall check if the access is restricted according to the rules in clause 5.3.1.
If that cell and other cells have to be excluded from the candidate list, as stated in clause 5.3.1, the UE shall not consider these as candidates for cell reselection. This limitation shall be removed when the highest ranked cell changes.
If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-frequency cell which is not suitable due to one or more of the following reasons:
– this cell belongs to a PLMN which is not indicated as being equivalent to the registered PLMN, or
– this cell is a CAG cell that belongs to a PLMN which is equivalent to the registered PLMN but with no CAG-ID that is present in the UE’s allowed CAG list being broadcasted, or
– this cell is not a CAG cell and the CAG-only indication in the UE is set, or
– this cell does not belong to a SNPN that is equal to the registered or selected SNPN of the UE in SNPN access mode,
the UE shall not consider this cell and, for operation in licensed spectrum, other cells on the same frequency as candidates for reselection for a maximum of 300 seconds.
For operation with shared spectrum channel access, when the highest ranked cell or best cell is not a candidate for reselection per the previous paragraph, the UE should continue to consider other cells on the same frequency for cell reselection, however if the second highest ranked cell on this frequency is also not suitable due to one or more of the above reasons, the UE may consider this frequency to be the lowest priority for a maximum of 300 seconds.
If the highest ranked cell or best cell according to absolute priority reselection rules is an intra-frequency or inter-frequency cell which is not suitable due to being part of the "list of 5GS forbidden TAs for roaming", the UE shall not consider this cell and other cells on the same frequency as candidates for reselection for a maximum of 300 seconds.
If the highest ranked cell or best cell according to absolute priority reselection rules is an inter-RAT cell which is not suitable due to being part of the "list of forbidden TAs for roaming" or belonging to a PLMN which is not indicated as being equivalent to the registered PLMN, the UE shall not consider this cell and other cells on the same frequency, as candidates for reselection for a maximum of 300 seconds.
If the UE enters into state any cell selection, any limitation shall be removed. If the UE is redirected under NR control to a frequency for which the timer is running, the limitation(s) on that frequency shall be removed.
[TS 38.304, clause 5.2.4.6]
The cell-ranking criterion Rs for serving cell and Rn for neighbouring cells is defined by:
Rs = Qmeas,s +Qhyst – Qoffsettemp Rn = Qmeas,n -Qoffset – Qoffsettemp |
where:
Qmeas |
RSRP measurement quantity used in cell reselections. |
Qoffset |
For intra-frequency: Equals to Qoffsets,n, if Qoffsets,n is valid, otherwise this equals to zero. For inter-frequency: Equals to Qoffsets,n plus Qoffsetfrequency, if Qoffsets,n is valid, otherwise this equals to Qoffsetfrequency. |
Qoffsettemp |
Offset temporarily applied to a cell as specified in TS 38.331 [3]. |
The UE shall perform ranking of all cells that fulfil the cell selection criterion S, which is defined in 5.2.3.2.
The cells shall be ranked according to the R criteria specified above by deriving Qmeas,n and Qmeas,s and calculating the R values using averaged RSRP results.
If rangeToBestCell is not configured, the UE shall perform cell reselection to the highest ranked cell. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
If rangeToBestCell is configured, then the UE shall perform cell reselection to the cell with the highest number of beams above the threshold (i.e. absThreshSS-BlocksConsolidation) among the cells whose R value is within rangeToBestCell of the R value of the highest ranked cell. If there are multiple such cells, the UE shall perform cell reselection to the highest ranked cell among them. If this cell is found to be not-suitable, the UE shall behave according to subclause 5.2.4.4.
In all cases, the UE shall reselect the new cell, only if the following conditions are met:
– the new cell is better than the serving cell according to the cell reselection criteria specified above during a time interval TreselectionRAT;
– more than 1 second has elapsed since the UE camped on the current serving cell.
[TS 38.304, clause 5.3.1]
Cell status and cell reservations are indicated in the MIB or SIB1 message as specified in TS 38.331 [3] by means of following fields:
– cellBarred (IE type: "barred" or "not barred")
Indicated in MIB message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common for all PLMNs and NPNs
– cellReservedForOperatorUse (IE type: "reserved" or "not reserved")
Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is specified per PLMN or per SNPN.
– cellReservedForOtherUse (IE type: "true")
Indicated in SIB1 message. In case of multiple PLMNs indicated in SIB1, this field is common for all PLMNs.
– cellReservedForFutureUse (IE type: "true")
Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is common for all PLMNs and NPNs.
NOTE 0: IAB-MT ignores the cellBarred, cellReservedForOperatorUse, cellReservedForFutureUse and intraFreqReselection (i.e. treats intraFreqReselection as if it was set to allowed) as defined in TS 38.331 [3]. IAB-MT also ignores cellReservedForOtherUse for cell barring determination (i.e. NPN capable IAB-MT considers cellReservedForOtherUse for determination of an NPN-only cell) as defined in TS 38.331 [3].
– iab-Support (IE type: "true")
Indicated in SIB1 message. In case of multiple PLMNs or NPNs indicated in SIB1, this field is specified per PLMN or per SNPN.
When cell status is indicated as "not barred" and "not reserved" for operator use and not "true" for other use and not "true" for future use,
– All UEs shall treat this cell as candidate during the cell selection and cell reselection procedures.
When cell broadcasts any CAG-IDs or NIDs and the cell status is indicated as "not barred" and "not reserved" for operator use and "true" for other use, and not "true" for future use:
– All NPN-capable UEs shall treat this cell as candidate during the cell selection and cell reselection procedures, other UEs shall treat this cell as if cell status is "barred".
When cell status is indicated as "true" for other use, and either cell does not broadcast any CAG-IDs or NIDs or does not broadcast any CAG-IDs and the UE is not operating in SNPN Access Mode,
– The UE shall treat this cell as if cell status is "barred".
When cell status is indicated as "true" for future use,
– The UE shall treat this cell as if cell status is "barred".
When cell status is indicated as "not barred" and "reserved" for operator use for any PLMN/SNPN and not "true" for other use and not "true" for future use,
– UEs assigned to Access Identity 11 or 15 operating in their HPLMN/EHPLMN shall treat this cell as candidate during the cell selection and reselection procedures if the field cellReservedForOperatorUse for that PLMN set to "reserved".
– UEs assigned to Access Identity 11 or 15 shall treat this cell as candidate during the cell selection and reselection procedures if the field cellReservedForOperatorUse for selected/registered SNPN is set to "reserved".
– UEs assigned to an Access Identity 0, 1, 2 and 12 to 14 shall behave as if the cell status is "barred" in case the cell is "reserved for operator use" for the registered PLMN/SNPN or the selected PLMN/SNPN.
NOTE 1: Access Identities 11, 15 are only valid for use in the HPLMN/ EHPLMN; Access Identities 12, 13, 14 are only valid for use in the home country as specified in TS 22.261 [12].
When cell status "barred" is indicated or to be treated as if the cell status is "barred",
– The UE is not permitted to select/reselect this cell, not even for emergency calls.
– The UE shall select another cell according to the following rule:
– If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the MIB:
– the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds.
– the UE may select another cell on the same frequency if the selection criteria are fulfilled.
– else:
– If the field intraFreqReselection in MIB message is set to "allowed":
– the UE may select another cell on the same frequency if re-selection criteria are fulfilled;
– If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1:
– the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds;
– else:
– the UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
– If the field intraFreqReselection in MIB message is set to "not allowed":
– If the cell is to be treated as if the cell status is "barred" due to being unable to acquire the SIB1:
– the UE may exclude the barred cell as a candidate for cell selection/reselection for up to 300 seconds;
– If the cell operates in licensed spectrum:
– the UE shall not re-select to another cell on the same frequency as the barred cell and exclude such cell(s) as candidate(s) for cell selection/reselection for 300 seconds;
– else:
– the UE may select to another cell on the same frequency if the reselection criteria are fulfilled.
– else:
– If the cell operates in licensed spectrum, or if this cell belongs to a PLMN which is indicated as being equivalent to the registered PLMN or the selected PLMN of the UE, or if this cell belongs to the registered SNPN or the selected SNPN of the UE:
– the UE shall not re-select to another cell on the same frequency as the barred cell and exclude such cell(s) as candidate(s) for cell selection/reselection for 300 seconds;
– else:
– the UE may select to another cell on the same frequency if the reselection criteria are fulfilled.
– the UE shall exclude the barred cell as a candidate for cell selection/reselection for 300 seconds.
The cell selection of another cell may also include a change of RAT.
NOTE 2: If barring of a cell is triggered by the condition of trackingAreaCode not being provided, as specified in TS 38.331 [3], the barring only applies to this PLMN and the UE can re-evaluate the barring condition again due to selection of another PLMN.
6.5.2.6.3 Test description
6.5.2.6.3.1 Pre-test conditions
System Simulator:
– NR Cell 1, NR Cell 3 and NR Cell 6.
– NR Cell 3 and NR Cell 6 are CAG cells.
– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used for NR Cell 1, NR Cell 3 and NR Cell 6.
– The PLMNs are identified in the test by the identifiers in Table 6.5.2.6.3.1-1 and the PLMN settings are defined in TS 36.523-1 [13] table 6.0.1-1.
– NR Cell 6 TAC is set to TAC=2.
Table 6.5.2.6.3.1–1: PLMN and CAG identifiers
NR Cell |
PLMN name |
CAG IDs |
1 |
PLMN 1 |
– |
3 |
PLMN 2 |
1 |
6 |
PLMN 2 |
2 |
UE:
– There is no “CAG information list” provisioned in the UE.
– The UE is in Automatic PLMN selection mode.
Preamble:
– The UE is registered on NR Cell 1 using the procedure described in TS 38.508-1 [4] Table 4.5.2.2-2, except that the REGISTRATION ACCEPT message includes CAG information list with CAG-ID 1 and CAG-ID 2 before it is in state Switched OFF (State 0N-B).
6.5.2.6.3.2 Test procedure sequence
Table 6.5.2.6.3.2-1/2 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions for preamble. Subsequent configurations marked “T1”, “T2” and “T3” are applied at the points indicated in the Main behaviour description in Table 6.5.2.6.3.2-3. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 38.508-1 [4] Table 6.2.2.1-3 for FR1 and Table 6.2.2.2-2 for FR2.
Table 6.5.2.6.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 |
Remarks |
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 |
-88 |
"Off" |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
-88 |
-78 |
The power level values are assigned to satisfy RNR Cell 3 < RNR Cell 6. |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
-88 |
"Off" |
Table 6.5.2.6.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 |
Remarks |
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" |
|
T2 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
FFS |
FFS |
The power level values are assigned to satisfy RNR Cell 3 < RNR Cell 6. |
T3 |
SS/PBCH SSS EPRE |
dBm/SCS |
"Off" |
FFS |
"Off" |
Table 6.5.2.6.3.2-3: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SIB1 for NR cell 1 is updated according to Table 6.5.2.6.3.3-2 |
– |
– |
– |
– |
1A |
Wait for 2.1* modification period second for the SS to transmit modified system information (Note 1) |
– |
– |
– |
– |
2 |
The UE is switched on. |
||||
3 |
Check: Does the UE transmit a RRCSetupRequest message on NR Cell 1 within 60s ? |
–> |
NR RRC: RRCSetupRequest |
1 |
F |
4 |
The SS changes cell power levels according to row "T1" in Table 6.5.2.6.3.2-1 for FR1 and Table 6.5.2.6.3.2-2 for FR2. |
||||
5-22a1 |
Steps 2-20a1 of Table 4.5.2.2-2 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 3. |
– |
– |
– |
– |
23 |
SS adjusts cell levels according to row T2 of table 6.5.2.6.3.2-1/2. |
– |
– |
– |
– |
24 |
Check: Does the UE transmit a RRCSetupRequest message on NR Cell 6 |
–> |
NR RRC: RRCSetupRequest |
2 |
P |
25-29 |
Steps 2-6a1 of Table 4.9.5.2.2-1 of the generic procedure in TS 38.508-1 [4] are performed on NR Cell 6. |
– |
– |
||
30 |
Void |
||||
31 |
SS adjusts cell levels according to row T3 of table 6.5.2.6.3.2-1/2. |
||||
32-36 |
Steps 1 to 5 of the generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 are performed on NR Cell 3. |
||||
Note 1: The modification period, expressed in number of radio frames = modificationPeriodCoeff * defaultPagingCycle. |
6.5.2.6.3.3 Specific message contents
Table 6.5.2.6.3.3-1: REGISTRATION ACCEPT for NR Cell 1 (preamble)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 002; MNC : 11; CAG only : 0;CAG-ID 1 : 1, CAG-ID 2 : 2 |
||
Length of CAG information list contents |
‘0000 0000 00001101’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1100’B |
||
MCC |
MCC of NR Cell 3 |
See Table 6.5.2.6.3.1–1 |
|
MNC |
MNC of NR Cell 3 |
See Table 6.5.2.6.3.1–1 |
|
CAG only |
‘0’B |
||
CAG_ID 1 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
CAG_ID 2 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
|
Equivalent PLMNs |
PLMN2 |
Table 6.5.2.6.3.3-2: SIB1 for NR Cell 1 (Step 1, Table 6.5.2.6.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
} |
|||
} |
Table 6.5.2.6.3.3-3: Void
Table 6.5.2.6.3.3-4: SIB1 for NR Cell 6 (preamble and all steps, Table 6.5.2.6.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
mcc |
002 |
PLMN2 MCC |
|
mnc |
11 |
PLMN2 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-identity-r16 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
|
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
000000000000000000000010 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 6 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 6.5.2.6.3.3-5: SIB1 for NR Cell 3 (preamble and all steps, Table 6.5.2.6.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.6.1-28 with condition SNPN and CAG |
|||
Information Element |
Value/Remark |
Comment |
Condition |
SIB1 ::= SEQUENCE { |
|||
CellAccessRelatedInfo SEQUENCE { |
|||
cellReservedForOtherUse |
true |
||
npn-IdentityInfoList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-IdentityInfo-r16 { |
1 entry |
||
NPN-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
npn-IdentityList-r16 SEQUENCE (SIZE (1..maxPLMN)) OF NPN-Identity-r16 { |
1 entry |
||
NPN-Identity-r16[1] CHOICE { |
entry 1 |
||
pni-npn-r16 SEQUENCE { |
|||
mcc |
002 |
PLMN2 MCC |
|
mnc |
11 |
PLMN2 MNC |
|
} |
|||
cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 { |
1 entry |
||
CAG-IdentityInfo-r16[1] SEQUENCE { |
entry 1 |
||
cag-identity-r16 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
|
} |
|||
} |
|||
} |
|||
} |
|||
trackingAreaCode-r16 |
TAC of NR Cell 3 |
||
cellIdentity-r16 |
Cell Identity of NR Cell 3 |
||
cellReservedForOperatorUse-r16 |
notReserved |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 6.5.2.6.3.3-6: REGISTRATION ACCEPT (Step 17, Table 6.5.2.6.3.2-3)
Derivation path: TS 38.508-1 [4], Table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
MCC : 002; MNC : 11; CAG only : 1; CAG-ID 1 : 2, CAG ID 2: 1 |
||
Length of CAG information list contents |
‘0000 0000 0000 1101’B |
||
Entry 1 |
|||
Length of entry contents |
‘0000 1100’B |
||
MCC |
MCC of NR Cell 6 |
See Table 6.5.2.6.3.1-1 |
|
MNC |
MNC of NR Cell 6 |
See Table 6.5.2.6.3.1-1 |
|
CAG only |
‘1’B |
||
CAG_ID 1 |
2 |
CAG ID is coded as a 32 bit BITSTRING |
|
CAG_ID 2 |
1 |
CAG ID is coded as a 32 bit BITSTRING |
Table 6.5.2.6.3.3-7: REGISTRATION ACCEPT (Step 35, Table 6.5.2.6.3.2-3)
Derivation path: TS 38.508-1 [4], table 4.7.1-7 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
CAG information list |
|||
Length of CAG information list contents |
‘0000 0000 0000 0000’B |
||
Entry 1 |
Not present |