22.4.30 NB-IoT / NTN / Ephemeris information update / T317 Expiry / T318 Expiry

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

22.4.30.1 Test Purpose (TP)

(1)

with { UE has acquired SystemInformationBlockType31-NB and starts timer T317 with the duration ul-SyncValidityDuration }

ensure that {

when { T317 expires in RRC_CONNECTED state }

then { UE informs lower layers that the UL synchronization is lost and start T318 }

}

(2)

with { UE has starts T318 in RRC_CONNECTED state }

ensure that {

when { T318 expires }

then { UE considers radio link failure and initiates the connection re-establishment procedure }

}

22.4.30.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clauses 5.2.1.3, 5.2.2.4, 5.2.2.39, 5.3.18 and 5.3.11.3 Unless otherwise stated these are Rel-17 requirements.

[TS 36.331, clause 5.2.1.3]

In RRC_CONNECTED, BL UEs or UEs in CE or NB-IoT UEs are not required to acquire system information except when T311 is running, or upon handover where the UE is only required to acquire the MasterInformationBlock in the target PCell, or for UEs in CE to receive ETWS/CMAS information, or upon expiry of T317 where the UE is only required to acquire the SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT). In RRC_IDLE, E-UTRAN may notify BL UEs or UEs in CE or NB-IoT UEs about SI update, and except for NB-IoT, ETWS and CMAS notification, EAB modification and UAC modification, using Direct Indication information, as specified in 6.6 (or 6.7.5 in NB-IoT) and TS 36.212 [22].

NOTE 2: Upon system information change essential for BL UEs, UEs in CE, or NB-IoT UEs in RRC_CONNECTED, E-UTRAN may initiate connection release.

NOTE 3: When acquiring SIB31(-NB) in RRC_CONNECTED, UE may assume that the scheduling is unchanged.

[TS 36.331, clause 5.2.2.4]

The UE shall:

…

1> if the UE is NTN capable:

2> if schedulingInfoList indicates that SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT) is present:

3> immediately before establishing, resuming or re-establishing an RRC connection; or

3> if in RRC_CONNECTED and T317 is not running:

4> acquire SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT);

[TS 36.331, clause 5.2.2.39]

Upon receiving SystemInformationBlockType31 (SystemInformationBlockType31-NB), the UE shall:

1> start or restart timer T317 with the duration ul-SyncValidityDuration from the subframe indicated by epochTime.

[TS 36.331, clause 5.3.18]

The UE shall:

1> if in RRC_CONNECTED:

2> inform lower layers that the UL synchronisation is lost;

2> start timer T318;

2> acquire SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT) as specified in 5.2.2;

2> upon successful acquisition of SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT):

3> stop timer T318;

3> inform lower layers that the UL synchronisation is restored;

NOTE: SystemInformationBlockType31 (SystemInformationBlockType31-NB in NB-IoT) may be broadcast on a different narrowband or different NB-IoT carrier than the one configured to the UE.

[TS 36.331, clause 5.3.11.3]

The UE shall:

…

  1. upon T318 expiry; or

…

2> consider radio link failure to be detected for the MCG i.e. RLF;

…

3> else:

4> initiate the connection re-establishment procedure as specified in 5.3.7;

22.4.30.3 Test description

22.4.30.3.1 Pre-test conditions

System Simulator:

– Ncell 1 is configured according to Table 8.1.4.2-3 and Table 8.1.4.2-5 in TS 36.508 [18].

– System information combination 8 as defined in TS 36.508 [18] clause 8.1.4.3.1.1 is used.

UE:

– The UE is in Automatic PLMN selection mode.

– The UE’s positioning engine (e.g., standalone GNSS receiver) should be enabled to allow it to acquire the position. This could be done by use of AT command, such as AT+CPOS or other commands. Otherwise, or in addition any other suitable method may also be used, e.g., GNSS simulator.

Preamble:

– The UE is in State 1-NB switched off according to TS 36.508 [18].

22.4.30.3.2 Test procedure sequence

Table 22.4.30.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Power on UE.

–

–

–

–

2

UE acquires SystemInformationBlockType31-NB and start T317 = 60 seconds.

–

–

–

–

3-18

Steps 1 to 16b1 of the Attach, connected mode and test mode activated procedure described in TS 36.508 [18] subclause 8.1.5.2A.3 with TEST LOOP MODE A are performed on Ncell 1.

–

–

–

–

19

SS stops broadcasting SystemInformationBlockType31-NB.

–

–

–

–

20

Wait until expiry of T317 and UE starts T318.

–

–

–

–

21-22

Steps 1 to 2 of the UE Test Loopback Activated procedure described in TS 36.508 [18] subclause 8.1.5.2B.3 are performed on Ncell 1.

–

–

–

–

23

The SS transmits a MAC PDU containing an RLC SDU.

<–

MAC PDU (RLC SN=0)

–

–

24

The SS schedules UL grants at the beginning of the next 10 UE specific search spaces, allowing the UE to return the RLC SDU as received in step 23.

<–

(UL Grant (known C-RNTI))

–

–

25

Check: Does the UE transmit a MAC PDU corresponding to grant in step 24?

–>

MAC PDU

1

F

26

Wait until expiry of T318.

–

–

–

–

27

Check: Does the UE transmit an RRCConnectionReestablishmentRequest-NB message on SRB0?

–>

RRCConnectionReestablishmentRequest-NB

2

P
22.4.30.3.3 Specific message contents

Table 22.4.30.3.3-1: SystemInformationBlockType2-NB (preamble, table 22.4.30.3.2-1)

Derivation Path: TS 36.508 [18], Table 8.1.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2-NB-r13 ::= SEQUENCE {

radioResourceConfigCommon-r13 SEQUENCE {

ntn-ConfigCommon-r17 SEQUENCE {

t318-r17

ms8000

}

}

}

Table 22.4.30.3.3-2: SystemInformationBlockType31-NB (preamble, table 22.4.30.3.2-1)

Derivation Path: TS 36.508 [18], Table 8.1.4.3.3-10

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType31-NB-r17 ::= SEQUENCE {

servingSatelliteInfo-r17 SEQUENCE {

ul-SyncValidityDuration-r17

s60

Value of T317

}

}