22.4.29 NB-IoT / Wake-up Signal / eDRX

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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

22.4.29.1 Test Purpose (TP)

(1)

with { UE in RRC_IDLE state and configured for eDRX and WUS }

ensure that {

when { network sends WUS followed by Paging message with a matched identity }

then { UE establishes RRC connection }

}

22.4.29.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 7.4

[TS 36.304, clause 7.4]

Paging with Wake Up Signal is only used in the cell in which the UE most recently entered RRC_IDLE triggered by:

– reception of RRCEarlyDataComplete; or

– reception of RRCConnectionRelease not including noLastCellUpdate; or

– reception of RRCConnectionRelease including noLastCellUpdate and the UE was using WUS in this cell prior to this RRC connection attempt.

If the UE is in RRC_IDLE, the UE is not using GWUS according to clause 7.5 and the UE supports WUS and WUS configuration is provided in system information, the UE shall monitor WUS using the WUS parameters provided in System Information. When DRX is used and the UE detects WUS the UE shall monitor the following PO. When extended DRX is used and the UE detects WUS the UE shall monitor the following numPOs POs or until a paging message including the UE’s NAS identity is received, whichever is earlier. If the UE does not detect WUS the UE is not required to monitor the following PO(s). If the UE missed a WUS occasion (e.g. due to cell reselection), it monitors every PO until the start of next WUS or until the PTW ends, whichever is earlier.

– numPOs = Number of consecutive Paging Occasions (PO) mapped to one WUS provided in system information where (numPOs≥1).

The WUS configuration, provided in system information, includes time-offset between end of WUS and start of the first PO of the numPOs POs UE is required to monitor. The timeoffset in subframes, used to calculate the start of a subframe g0 (see TS 36.213 [6]), is defined as follows:

– for UE using DRX, it is the signalled timeoffsetDRX;

– for UE using eDRX, it is the signalled timeoffset-eDRX-Short if timeoffset-eDRX-Long is not broadcasted;

– for UE using eDRX, it is the value determined according to Table 7.4-1 if timeoffset-eDRX-Long is broadcasted

Table 7.4-1: Determination of GAP between end of WUS and associated PO

		timeoffset-eDRX-Long
		1000ms	2000ms
UE Reported wakeUpSignalMinGap-eDRX	*40ms or not reported*	timeoffset-eDRX-Short	timeoffset-eDRX-Short
	*240ms*	timeoffset-eDRX-Short	timeoffset-eDRX-Short
	*1000ms*	timeoffset-eDRX-Long	timeoffset-eDRX-Long
	*2000ms*	timeoffset-eDRX-Short	timeoffset-eDRX-Long

The timeoffset is used to determine the actual subframe g0 as follows (taking into consideration resultant SFN and/or H-SFN wrap-around of this computation):

g0 = PO – timeoffset, where PO is the Paging Occasion subframe as defined in clause 7.1

For UE using eDRX, the same timeoffset applies between the end of WUS and associated first PO of the numPOs POs for all the WUS occurrences for a PTW.

The timeoffset, g0, is used to calculate the start of the WUS as defined in TS 36.213 [6].

22.4.29.3 Test description

22.4.29.3.1 Pre-test conditions

System Simulator:

– NCell 1 supports WUS.

UE:

– The UE is configured to request the use of eDRX (in ATTACH REQUEST message) and supports WUS.

Preamble:

– The UE is in state Registered, Idle Mode (State 3-NB) on Ncell 1 according to [18]. UE sent “extended DRX parameters IE” in ATTACH REQUEST message and received “extended DRX parameters IE” in ATTACH ACCEPT message.

22.4.29.3.2 Test procedure sequence

Table 22.4.29.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits WUS followed by Paging-NB message with a matched identity.	<–	Paging-NB	–	–
2	Check: Does the UE transmit an RRCConnectionRequest-NB message?	–>	RRC: RRCConnectionRequest-NB	1	P
3-5	Steps 3 to 5 of the generic test procedure in TS 36.508 subclause 8.1.5A.2 are performed.	–	–	–	–
6	The SS transmits an RRCConnectionRelease-NB message.	<–	RRCConnectionRelease-NB	–	–

22.4.29.3.3 Specific message contents

Table 22.4.29.3.3-1: SystemInformationBlockType2-NB (preamble and all steps, table 22.4.29.3.2-1)

Derivation Path: 36.508 clause 8.1.4.3.3, Table 8.1.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2-NB-r13 ::= SEQUENCE {
RadioResourceConfigCommon-r13 ::= SEQUENCE {
wus-Config-r15 ::= SEQUENCE {
maxDurationFactor-r15	one16th
numPOs-r15	n1
numDRX-CyclesRelaxed-r15	n1
timeOffsetDRX-r15	ms80
timeOffset-eDRX-Short-r15	ms160
timeOffset-eDRX-Long-r15	Not Present
}
}
}

Table 22.4.29.3.3-2: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1
Information Element	Value/remark	Comment	Condition
Extended DRX parameters
Paging Time Window	‘0000’B	2,56 seconds
eDRX value	‘0010’B	20,48 seconds