4.4A Test states
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
4.4A.1 General
The purpose of the test states is to get the UE into specific 5GC and RRC protocol states in the initial condition of test cases. Each test state is identified by a test state ID. The syntax used for test state IDs is described in sub-clause 4.4A.4. The list of defined test states and the associated UE 5GC and RRC/ N3AN protocol states are specified in sub-clause 4.4A.2.
A test case may request that one or more test functions and/or configurations are activated/configured by the SS as part of the procedure used for the requested test state. The test case requests the additional test functions and/or configurations by specifying one or more test state parameters. The list of defined test state parameters is specified in sub-clause 4.4A.3.
4.4A.2 Test states and associated 5GC and RRC protocol states
Table 4.4A.2-0: 5GC and RRC/N3AN protocol states for UE Switched Off
|
5GS state ID |
Connectivity |
RRC/N3AN state |
5GMM modes |
5GMM sublayer |
5GSM sublayer |
Comments |
|
0-A |
– |
– |
– |
– |
– |
UE switched off. No change to PLMN stored in the USIM |
|
0N-B |
NR |
– |
– |
– |
– |
UE switched off with the PLMN under test stored in the USIM |
|
0E-B |
E-UTRA |
– |
– |
– |
– |
|
|
0W-B |
WLAN |
– |
– |
– |
– |
Table 4.4A.2-1: 5GC and RRC/N3AN protocol states for IDLE
|
5GS state ID |
Connectivity |
RRC/N3AN state |
5GMM modes |
5GMM sublayer |
5GSM sublayer |
|
1N-A |
NR |
NR RRC_IDLE |
5GMM-IDLE |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
1E-A |
E-UTRA |
EUTRA RRC_IDLE |
5GMM-IDLE |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
1W-A |
WLAN |
Ipsec_SA_Released |
5GMM-IDLE |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
1N-B |
NR |
NR RRC_IDLE |
5GMM-IDLE |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
Table 4.4A.2-2: 5GC and RRC protocol states for INACTIVE
|
5GS state ID |
Connectivity |
RRC state |
5GMM modes |
5GMM sublayer |
5GSM sublayer |
|
2N-A |
NR |
NR RRC_INACTIVE |
5GMM-CONNECTED |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
2E-A |
E-UTRA |
EUTRA RRC_ INACTIVE |
5GMM-CONNECTED |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
Table 4.4A.2-3: 5GC and RRC/N3AN protocol states for CONNECTED
|
5GS state ID |
Connectivity |
RRC/N3AN state |
5GMM modes |
5GMM sublayer |
5GSM sublayer |
|
3N-A |
NR |
NR RRC_ CONNECTED |
5GMM-CONNECTED |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
3E-A |
E-UTRA |
EUTRA RRC_ CONNECTED |
5GMM-CONNECTED |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
3W-A |
WLAN |
Ipsec_SA_Established |
5GMM-CONNECTED |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
|||||
|
3N-B |
NR |
NR RRC_ CONNECTED |
5GMM-CONNECTED |
5GMM-REGISTERED |
PDU SESSION INACTIVE |
|
PDU SESSION ACTIVE |
Table 4.4A.2-4: 5GC and RRC/N3AN protocol states for Out of Coverage
|
5GS state ID |
Connectivity |
RRC/N3AN state |
5GMM modes |
5GMM sublayer |
5GSM sublayer |
|
4-A |
– |
– |
– |
– |
– |
4.4A.3 Test state parameters
Table 4.4A.3-1 lists the test functions and configurations that a test case can request to be activated/configured. A test case requests a test function or configuration to be used in the preamble by including the test state parameter text in the preamble statement of the test case in italics.
Editor’s Note: The test state parameters are currently limited to test functions required by standalone NR. Additional test state parameters will be added in future as needed. E.g. for EN-DC, NE-DC and NGEN-DC there will be a need for parameters for bearer type (MCG and SCG, MCG and split or MCG only).
Table 4.4A.3-1: Test state parameters
|
Test state parameter |
Description |
|
UE test loop mode <X> prepared |
If included the UE test mode is activated in the preamble indicating that UE test loop mode <X> will be activated in the test case test procedure, where <X> is A, B or E. |
|
UE test loop mode <X> active |
If included the UE Test Mode and UE test loop mode <X> will be activated in the preamble, where <X> is A, B or E. |
|
Note 1: See TS 38.509 [11], clause 5.2.2 for details of UE test mode. Note 2: See TS 38.509 [11], clause 5.3.4.1 for details of UE test loop mode A. Note 3: See TS 38.509 [11], clause 5.3.4.2.2 for details of UE test loop mode B. Note 4: See TS 38.509 [11], clause 5.3.4.3 for details of UE test loop mode E. |
|
4.4A.4 Test state ID syntax
A test state ID is defined as:
<RRC state><Connectivity>-<Variant>
, where <RRC state>, <Connectivity> and <Variant> are defined in Table 4.4A.2-1.
Table 4.4A.4-1: Test state fields
|
Test state field |
Value |
Description |
|
<RRC state> |
0 |
Indicates that the requested test state will end up in SWITCHED_OFF state. |
|
1 |
Indicates that the requested test state will end up in RRC_IDLE/Ipsec_SA_Released state. |
|
|
2 |
Indicates that the requested test state will end up in RRC_INACTIVE state. |
|
|
3 |
Indicates that the requested test state will end up in RRC_CONNECTED/Ipsec_SA_Released state. |
|
|
4 |
Indicates that the requested test state will end up in Out_of_Coverage state. |
|
|
<Connectivity> |
E |
E-UTRA is used as the initial access. |
|
N |
NR is used as the initial access. |
|
|
W |
Un trusted non 3GPP Access over WLAN is used as the initial access |
|
|
<Variant> |
A |
A, B, C etc. used to represent different variants within a <RRC state><Connectivity> group of test states. |
4.4A.5 Mapping of test state IDs and test parameters to generic procedures, generic procedure parameters and specific message conditions
Depending on the test case preamble requested test state ID and test parameters the SS shall:
1> use the applicable generic procedure as specified in Table 4.4A.5-1 using the:
2> applicable generic procedure parameters as specified in Table 4.4A.5-1 and Table 4.4A.5-2; and
2> applicable message conditions as specified in Table 4.4A.5-2.
Table 4.4A.5-1: Test state ID mapping to generic procedures and Connectivity generic procedure parameter
|
Test state ID |
Generic Procedure |
||||||||||||
|
RRC state field |
Connectivity field |
Variant field |
Name |
Generic procedure parameter (Note 1) |
Clause |
||||||||
|
0 |
– |
A |
SWITCHED_OFF |
4.5.5 |
|||||||||
|
0 |
N |
B |
SWITCHED_OFF |
Connectivity=NR |
4.5.5 |
||||||||
|
0 |
E |
B |
SWITCHED_OFF |
Connectivity=E-UTRA |
4.5.5 |
||||||||
|
0 |
W |
B |
SWITCHED_OFF |
Connectivity=WLAN |
4.5.5 |
||||||||
|
1 |
N |
A |
RRC_IDLE |
Connectivity=NR |
4.5.2 |
||||||||
|
1 |
E |
A |
RRC_IDLE |
Connectivity=E-UTRA |
4.5.2 |
||||||||
|
1 |
W |
A |
Ipsec_SA_Released |
Connectivity=WLAN |
4.5.2 |
||||||||
|
1 |
N |
B |
RRC_IDLE_with_SL |
Connectivity=NR, Sidelink = On |
4.5.2 |
||||||||
|
2 |
N |
A |
RRC_INACTIVE |
Connectivity=NR |
4.5.3 |
||||||||
|
2 |
E |
A |
RRC_INACTIVE |
Connectivity=E-UTRA |
4.5.3 |
||||||||
|
3 |
N |
A |
RRC_CONNECTED |
Connectivity=NR |
4.5.4 |
||||||||
|
3 |
E |
A |
RRC_CONNECTED |
Connectivity=E-UTRA |
4.5.4 |
||||||||
|
3 |
W |
A |
Ipsec_SA_Established |
Connectivity=WLAN |
4.5.4 |
||||||||
|
3 |
N |
B |
RRC_CONNECTED_with_SL |
Connectivity=NR, Sidelink = On |
4.5.4 |
||||||||
|
4 |
– |
A |
Out_of_Coverage |
Sidelink = On |
4.5.7 |
||||||||
|
Note 1: In addition to the Connectivity parameter specified in this table the applicable additional generic procedure parameters and conditions as stated in Table 4.4A.5-2 shall be used |
|||||||||||||
Table 4.4A.5-2: Additional generic procedure parameters and message conditions
|
Test state |
Additional generic |
Specific message conditions |
|
|
parameter |
procedure parameter(s) |
Message |
Condition |
|
UE test loop mode A prepared |
Test Mode=On |
Note 1 |
Note 1 |
|
UE test loop mode B prepared |
Test Mode=On |
ACTIVATE UE TEST MODE (see subclause 4.7A.1) |
UE test loop mode B |
|
UE test loop mode E prepared |
Test Mode=On |
ACTIVATE UE TEST MODE (ee subclause 4.7A.1) |
UE test loop mode E |
|
UE test loop mode A active |
Test Loop Function=On |
Note 1 |
Note 1 |
|
UE test loop mode B active |
Test Loop Function=On |
ACTIVATE UE TEST MODE (see subclause 4.7A.1) |
UE test loop mode B |
|
CLOSE UE TEST LOOP |
UE test loop mode B |
||
|
UE test loop mode E active |
Test Loop Function=On |
ACTIVATE UE TEST MODE (see subclause 4.7A.1) |
UE test loop mode E |
|
CLOSE UE TEST LOOP |
UE test loop mode E |
||
|
Note 1: For test state parameters UE test loop mode A prepared and UE test loop mode A active there is no specific message conditions needed as the default UE test loop mode in the messages ACTIVATE UE TEST MODE and CLOSE UE TEST LOOP is UE test loop mode A. |
|||