8.1.1 Paging

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

8.1.1.1 Void

NOTE: The present test (RRC / Paging for connection in idle mode) is superseded by test case 9.3.2.1 (i.e. all requirements which the present test verified are verified in test case 9.3.2.1).

8.1.1.1a RRC / Direct Indication Information / Notification of BCCH modification in idle mode

8.1.1.1a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { network indicates availability of new system information by Direct Indication Information field to 1 on MPDCCH }

then { UE applies the new system information by Direct Indication Information about the correct prach-ConfigIndex in random access }

}

(2)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { network broadcast the extended modification period with modificationPeriodCoeff-v1310 set to n64 and network indicates availability of new system information by Direct Indication Information field to 1 on MPDCCH }

then { UE applies the extended modification period and reads the new system information }

}

8.1.1.1a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.2.1.3, 6.6, 5.2.2.3, 5.2.2.4, TS 36.212, clause 5.3.3.1.14

[TS36.331, clause 5.2.1.3]

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 and EAB modification, using Direct Indication information, as specified in 6.6 (or 6.7.5 in NB-IoT) and TS 36.212 [22].

…

For BL UEs or UEs in CE or NB-IoT UEs, the change of specific SI message can additionally be indicated by a SI message specific value tag systemInfoValueTagSI. If systemInfoValueTag included in the SystemInformationBlockType1-BR (or MasterInformationBlock-NB in NB-IoT) is different from the one of the stored system information and if systemInfoValueTagSI is included in the SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) for a specific SI message and is different from the stored one, the UE shall consider this specific SI message to be invalid. If only systemInfoValueTag is included and is different from the stored one, the BL UE or UE in CE should consider any stored system information except SystemInformationBlockType10, SystemInformationBlockType11, SystemInformationBlockType12 and SystemInformationBlockType14 to be invalid; the NB-IoT UE should consider any stored system information except SystemInformationBlockType14-NB to be invalid.

[TS36.331, clause 6.6]

Direct Indication information is transmitted on MPDCCH using P-RNTI but without associated Paging message. Table 6.6-1 defines the Direct Indication information, see TS 36.212 [22, 5.3.3.1.14].

When bit n is set to 1, UE shall behave as if the corresponding field is set in the Paging message, see 5.3.2.3. Bit 1 is the least significant bit.

Table 6.6-1: Direct Indication information

Bit	Direct Indication information
1	systemInfoModification
2	etws-Indication
3	cmas-Indication
4	eab-ParamModification
5	systemInfoModification-eDRX
6, 7, 8	Not used, and shall be ignored by UE if received.

[TS 36.331, clause 5.2.2.3]

The UE shall:

1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as the ‘required’ system information:

2> if in RRC_IDLE:

3> the MasterInformationBlock, SystemInformationBlockType1-BR and SystemInformationBlockType2;

NOTE: E-UTRAN may release BL UEs or UEs in CE or NB-IoT UEs to RRC_IDLE if these UEs need to acquire changed system information.

[TS 36.331, clause 5.2.2.4]

The UE shall:

1> apply the specified BR-BCCH configuration defined in 9.1.1.8;

1> if the procedure is triggered by a system information change notification:

2> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification period following the one in which the change notification was received;

NOTE 1: The UE continues using the previously received system information until the new system information has been acquired.

…

The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated with a received or a UE originated RRC message, e.g. an ongoing random access procedure.

NOTE 6: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer present, the UE should stop trying to acquire the particular SIB.

[TS 36.212, clause 5.3.3.1.14]

DCI format 6-2 is used for paging and direct indication.

The following information is transmitted by means of the DCI format 6-2:

– Flag for paging/direct indication differentiation – 1 bit, with value 0 for direct indication and value 1 for paging

– If Flag=0:

– Direct Indication information – 8 bits provide direct indication of system information update and other fields, as defined in [6]

– Reserved information bits are added until the size is equal to that of format 6-2 with Flag=1

…

8.1.1.1a.3 Test description

8.1.1.1a.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– DCI format 6-2 flag = 0

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2-CE) according to [18].

8.1.1.1a.3.2 Test procedure sequence

Table 8.1.1.1a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	1	P
3	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
4	The UE transmits an RRCConnectionSetupComplete message. This message includes a SERVICE REQUEST message.	–>	RRCConnectionSetupComplete	–	–
5	The SS transmits a SecurityModeCommand message.	<–	SecurityModeCommand	–	–
6	The UE transmits a SecurityModeComplete message.	–>	SecurityModeComplete	–	–
7	The SS transmits an RRCConnectionReconfiguration message.	<–	RRCConnectionReconfiguration	–	–
8	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
9	The SS transmits an RRCConnectionRelease message.	<–	RRCConnectionRelease	–	–
10	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
11	The SS changes the prach-ConfigIndex in the system information	–	–	–	–
12	The SS indicates a new system information by Direct Indication information with bit 1 and transmitted on MPDCCH using P-RNTI	<–	–	–	–
13	Wait for 240s for the UE to receive system information. (Note 1)	–	–	–	–
13A	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
14	Check: Does the UE re-transmit a random access using prach-ConfigIndex given in step 11?	–	–	1,2	P
15	The UE transmit an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
16	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
17	The UE transmits an RRCConnectionSetupComplete message. This message includes a SERVICE REQUEST message.	–>	RRCConnectionSetupComplete	–	–
18	The SS transmits a SecurityModeCommand message.	<–	SecurityModeCommand	–	–
19	The UE transmits a SecurityModeComplete message.	–>	SecurityModeComplete	–	–
20	The SS transmits an RRCConnectionReconfiguration message.	<–	RRCConnectionReconfiguration	–	–
21	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
22	The SS transmits an RRCConnectionRelease message.	<–	RRCConnectionRelease	–	–
23	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
24	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.2 indicate that the UE is in E-UTRA RRC_IDLE state on Cell 1?	–	–	1	–
Note 1: The modification period, expressed in number of radio frames= modificationPeriodCoeff * defaultPagingCycle. The extended modificationPeriodCoeff broadcasted in SIB1-BR is set to n64 and the defaultPagingCycle is configured as rf128. This means that the modification period is 64*128 = 8192 radio frames equals to 81.92 seconds. 240 seconds wait time is used to make sure the UE have been able to read the new system information.

8.1.1.1a.3.3 Specific message contents

Table 8.1.1.1a.3.3-0: RadioResourceConfigCommonSIB-DEFAULT (preamble and step 12, Table 8.1.1.1a.3.2-1)

Derivation Path: 36.508 Table 4.4.3-14
Information Element	Value/remark	Comment	Condition
RadioResourceConfigCommonSIB-DEFAULT ::= SEQUENCE {
bcch-Config-v1310 SEQUENCE {
modificationPeriodCoeff-v1310	n64
}
}

Table 8.1.1.1a.3.3-1: RRCConnectionRequest (step 2 and 15, Table 8.1.1.1a.3.2-1)

Derivation Path: 36.508 Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.1.1.1a.3.3-1A: RRCConnectionReconfiguration (step 7 and 20, Table 8.1.1.1a.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0)

Table 8.1.1.1a.3.3-2: SystemInformationBlockType1-BR-r13 (step 11, table 8.1.1.1a.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
systemInfoValueTag	1	Default value is 0
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE {
systemInfoValueTagList-r13 SEQUENCE (SIZE (1..maxSI-Message)) OF	2 entries	The same number of entries, and listed in the same order, as in SchedulingInfoList (without suffix)
SystemInfoValueTagSI-r13[1]	SystemInfoValueTagSI-r13[k]=1, where k is the entry corresponding to the system info including SystemInformationBlockType2. For all other entries the value is set to 0 (same as in the default SystemInformationBlockType1-BR-r13 message).
SystemInfoValueTagSI-r13[2]
}
}
}
}
}
}
}

Table 8.1.1.1a.3.3-2A: PRACH-ConfigSIB-v1310-DEFAULT (step 11, Table 8.1.1.1a.3.2-1)

Derivation Path: 36.508 Table 4.6.3-7b
Information Element	Value/remark	Comment	Condition
PRACH-ConfigSIB-v1310-DEFAULT ::= SEQUENCE {
prach-ParametersListCE-r13 SEQUENCE {
prach-ConfigIndex-r13[1]	5	Set to index which denote subframe numbers different from the default one.	FDD
prach-ConfigIndex-r13[1]	52		TDD
}
}

Condition	Explanation
FDD	FDD cell environment
TDD	TDD cell environment

8.1.1.2 RRC / Paging for notification of BCCH modification in idle mode

8.1.1.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives a Paging message including a systemInfoModification }

then { UE re-acquires and applies the new system information about the correct prach-ConfigIndex in random access }

}

8.1.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.2.3, 5.2.2.3, and 5.2.2.4.

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity and the cn-Domain to the upper layers;

1> if the systemInfoModification is included:

2> re-acquire the required system information using the system information acquisition procedure as specified in 5.2.2.

…

[TS 36.331, clause 5.2.2.3]

The UE shall:

1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as the ‘required’ system information:

2> if in RRC_IDLE:

3> the MasterInformationBlock and SystemInformationBlockType1 as well as SystemInformationBlockType2 through SystemInformationBlockType8, depending on support of the concerned RATs;

…

[TS 36.331, clause 5.2.2.4]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1;

1> if the procedure is triggered by a system information change notification:

2> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification period following the one in which the change notification was received;

…

NOTE 3: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer present, the UE should stop trying to acquire the particular SIB.

8.1.1.2.3 Test description

8.1.1.2.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.1.1.2.3.2 Test procedure sequence

Table 8.1.1.2.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	1	P
3	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
3A	The UE transmits an RRCConnectionSetupComplete message. This message includes a SERVICE REQUEST message.	–>	RRCConnectionSetupComplete	–	–
3B	The SS transmits a SecurityModeCommand message.	<–	SecurityModeCommand	–	–
3C	The UE transmits a SecurityModeComplete message.	–>	SecurityModeComplete	–	–
3D	The SS transmits an RRCConnectionReconfiguration message.	<–	RRCConnectionReconfiguration	–	–
3E	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
3F	The SS transmits an RRCConnectionRelease message.	<–	RRCConnectionRelease	–	–
3G	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
4	The SS changes the prach-ConfigIndex in the system information	–	–	–	–
5	The SS transmits a Paging message including a systemInfoModification.	<–	Paging	–	–
6	Wait for 15s for the UE to receive system information.	–	–	–	–
7	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
7A	Check: Does the UE re-transmit a random access using prach-ConfigIndex given in step 4?	–	–	1	P
8	The UE transmit an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
9	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
9A	The UE transmits an RRCConnectionSetupComplete message. This message includes a SERVICE REQUEST message.	–>	RRCConnectionSetupComplete	–	–
9B	The SS transmits a SecurityModeCommand message.	<–	SecurityModeCommand	–	–
9C	The UE transmits a SecurityModeComplete message.	–>	SecurityModeComplete	–	–
9D	The SS transmits an RRCConnectionReconfiguration message.	<–	RRCConnectionReconfiguration	–	–
9E	The UE transmits an RRCConnectionReconfigurationComplete message.	–>	RRCConnectionReconfigurationComplete	–	–
9F	The SS transmits an RRCConnectionRelease message.	<–	RRCConnectionRelease	–	–
9G	Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.	–	–	–	–
10	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.2 indicate that the UE is in E-UTRA RRC_IDLE state on Cell 1?	–	–	1	–

8.1.1.2.3.3 Specific message contents

Table 8.1.1.2.3.3-1: RRCConnectionRequest (step 2 and step 8, Table 8.1.1.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.1.1.2.3.3-2A: RRCConnectionReconfiguration (step 3D and step 9D, Table 8.1.1.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-8, condition SRB2-DRB(1, 0)

Table 8.1.1.2.3.3-2: Paging (step 5, Table 8.1.1.2.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList	Not present
systemInfoModification	true
}

Table 8.1.1.2.3.3-2A: SystemInformationBlockType1 (step 6, table 8.1.1.2.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	1	Default value is 0
}

Table 8.1.1.2.3.3-2B: SystemInformationBlockType1-BR-r13 (step 6 when UE under test is CAT M1, table 8.1.1.2.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3, Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	1
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
bandwidthReducedAccessRelatedInfo-r13 SEQUENCE {
systemInfoValueTagList-r13 SEQUENCE (SIZE (1..maxSI-Message)) OF	n entries	The same number of entries, and listed in the same order, as in SchedulingInfoList (without suffix)
SystemInfoValueTagSI-r13[1]	SystemInfoValueTagSI-r13[k]=1, where k is the entry corresponding to the system info including SystemInformationBlockType2. For all other entries the value is set to 0 (same as in the default SystemInformationBlockType1-BR-r13 message).
SystemInfoValueTagSI-r13[n]
}
}
}
}
}
}
}

Table 8.1.1.2.3.3-3: SystemInformationBlockType2 (step 6, Table 8.1.1.2.3.2-1)

Derivation Path: 36.508 Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
prach-Config SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigIndex	10 (9 for CAT-M1 UEs)		FDD
prach-ConfigIndex	52	Set to index which denote subframe numbers different from the default one.	TDD
}
}
prach-ConfigCommon-v1310 SEQUENCE {			CEModeA,CEModeB
prach-ParametersListCE-r13 SEQUENCE {
prach-ConfigIndex-r13	10 (9 for CAT-M1 UEs)		FDD
prach-ConfigIndex-r13	52		TDD
}
}
}
}

Condition	Explanation
FDD	FDD cell environment
TDD	TDD cell environment
CEmodeA	Used for CE mode A testing
CEmodeB	Used for CE mode B testing

8.1.1.2a RRC / Paging for notification of BCCH modification in idle mode / eDRX cycle longer than the modification period / eDRX cycle with eDRX Allowed/Not Allowed

8.1.1.2a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state using eDRX cycle longer than System Information Modification period }

ensure that {
when { UE receives a Paging message including IE systemInfoModification-eDRX-r13 }

then { UE re-acquires and applies the new system information from the next eDRX acquisition period defined by H-SFN mod 256 = 0 }

}

(2)

with { the UE applied extended DRX parameters received in Attach Accept and is in E-UTRA RRC_IDLE state }

ensure that {

when { UE receives a Paging message including a systemInfoModification-eDRX-r13 }

then { UE re-acquires and applies the new system information about eDRX not allowed}

}

(3)

with { the UE applied normal DRX parameters and is in E-UTRA RRC_IDLE state }

ensure that {

when { UE receives a Paging message including a systemInfoModification }

then { UE re-acquires and applies the new system information about eDRX allowed }

}

8.1.1.2a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.304 clause 7.3, TS 36.331 clauses 5.2.1.3, 5.2.2.4, and 5.3.2.3.

[TS 36.304, clause 7.3]

The UE may be configured by upper layers with an extended DRX (eDRX) cycle T_eDRX. The UE may operate in extended DRX only if the cell indicates support for eDRX in System Information.

If the UE is configured with a T_eDRX cycle of 512 radio frames, it monitors POs as defined in 7.1 with parameter T = 512. Otherwise, a UE configured with eDRX monitors POs as defined in 7.1 (i.e, based on the upper layer configured DRX value and a default DRX value determined in 7.1), during a periodic Paging Time Window (PTW) configured for the UE or until a paging message including the UE’s NAS identity is received for the UE during the PTW, whichever is earlier. The PTW is UE-specific and is determined by a Paging Hyperframe (PH), a starting position within the PH (PTW_start) and an ending position (PTW_end). PH, PTW_start and PTW_end are given by the following formulae:

The PH is the H-SFN satisfying the following equation:

H-SFN mod T_eDRX,H= (UE_ID_H mod T_eDRX,H), where

– UE_ID_H:

– 10 most significant bits of the Hashed ID, if P-RNTI is monitored on PDCCH or MPDCCH

– 12 most significant bits of the Hashed ID, if P-RNTI is monitored on NPDCCH

– T_eDRX,H : eDRX cycle of the UE in Hyper-frames, (T_eDRX,H =1, 2, …, 256 Hyper-frames) (for NB-IoT, T_eDRX,H =2, …, 1024 Hyper-frames) and configured by upper layers.

PTW_start denotes the first radio frame of the PH that is part of the PTW and has SFN satisfying the following equation:

SFN = 256* i_eDRX, where

– i_eDRX = floor(UE_ID_H /T_eDRX,H) mod 4

PTW_end is the last radio frame of the PTW and has SFN satisfying the following equation:

SFN = (PTW_start + L*100 – 1) mod 1024, where

– L = Paging Time Window length (in seconds) configured by upper layers

Hashed ID is defined as follows:

Hashed_ID is Frame Check Sequence (FCS) for the bits b₃₁^,b₃₀…, b₀ of S-TMSI

S-TMSI = <b₃₉, b₃₈, …, b₀> as defined in [35]

[TS 36.331, clause 5.2.1.3]

To enable system information update notification for RRC_IDLE UEs configured to use a DRX cycle longer than the modification period, an eDRX acquisition period is defined. The boundaries of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod 256 =0. For NB-IoT, the boundaries of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod 1024 =0

When the network changes (some of the) system information, it first notifies the UEs about this change, i.e. this may be done throughout a modification period. In the next modification period, the network transmits the updated system information. These general principles are illustrated in figure 5.2.1.3-1, in which different colours indicate different system information. Upon receiving a change notification, the UE not configured to use a DRX cycle that is longer than the modification period acquires the new system information immediately from the start of the next modification period. Upon receiving a change notification applicable to eDRX, a UE in RRC_IDLE configured to use a DRX cycle that is longer than the modification period acquires the updated system information immediately from the start of the next eDRX acquisition period. The UE applies the previously acquired system information until the UE acquires the new system information.

…

The Paging message is used to inform UEs in RRC_IDLE and UEs in RRC_CONNECTED about a system information change. If the UE is in RRC_CONNECTED or is not configured to use a DRX cycle longer than the modification period in RRC_IDLE, and receives a Paging message including the systemInfoModification, it knows that the system information will change at the next modification period boundary. A UE in RRC_IDLE that is configured to use a DRX cycle longer than the modification period, and receives in an eDRX acquisition period at least one Paging message including the systemInfoModification-eDRX, shall acquire the updated system information at the next eDRX acquisition period boundary. Although the UE may be informed about changes in system information, no further details are provided e.g. regarding which system information will change, except if systemInfoValueTagSI is received by BL UEs or UEs in CE.

[TS 36.331, clause 5.2.2.4]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1 or BR-BCCH configuration defined in 9.1.1.8;

1> if the procedure is triggered by a system information change notification:

2> if the UE uses an idle DRX cycle longer than the modification period:

3> start acquiring the required system information, as defined in 5.2.2.3, from the next eDRX acquisition period boundary;

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

…

if the UE is configured with a DRX cycle longer than the modification period and the systemInfoModification-eDRX is included:

2> re-acquire the required system information using the system information acquisition procedure as specified in 5.2.2.

8.1.1.2a.3 Test description

8.1.1.2a.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages ).

– The UE is in state Registered, Idle mode (state 2) according to [18]. UE sent “extended DRX parameters IE” in ATTACH REQUEST message and received “extended DRX parameters IE” in ATTACH ACCEPT message.

8.1.1.2a.3.2 Test procedure sequence

Table 8.1.1.2a.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS changes prach-ConfigIndex in SystemInformationBlockType2 and does not include eDRX-Allowed-r13 IE in the SystemInformationBlockType1.	–	–	–	–
2	The SS transmits a Paging message including IE systemInfoModification-eDRX-r13 in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX.	<–	Paging	–	–
3	Wait till the beginning of next eDRX acquisition time (next H-SFN for which H-SFN mod 256 =0).	–	–	–	–
4	After Step 3, wait for 10s for the UE to acquire the new system information.	–	–	–	–
5	The SS transmits a Paging message to the UE in a valid PO as per normal DRX.	<–	Paging	–	–
6	Check: Does the UE transmit a random access using prach-ConfigIndex given in step 1?	–	–	1	P
7	The UE transmits an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
8	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
9	Check: Does the UE transmit an RRCConnectionSetupComplete message including a SERVICE REQUEST message?	–>	RRCConnectionSetupComplete	2	P
10-13	Steps 6 to 9 of the generic radio bearer establishment procedure in TS 36.508 subclause 4.5.3.3 are executed to successfully complete the service request procedure.	–	–	–	–
14	SS releases the RRC Connection.	–>	RRCConnectionRelease	–	–
15	The SS sets eDRX-Allowed-r13 IE to true in SystemInformationBlockType1 and changes prach-ConfigIndex in SystemInformationBlockType2	–	–	–	.-
16	The SS transmits a Paging message including a systemInfoModification as per normal DRX	<–	Paging	–	–
17	Wait for 15 secs for the UE to acquire the new system information.	–	–	–	–
18	SS sends a Paging message to the UE in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX.	<–	Paging	–	–
19	Check: Does the UE transmit a random access using prach-ConfigIndex given in step 15?	–	–	3	P
20	The UE transmit an RRCConnectionRequest message.	–>	RRCConnectionRequest	–	–
21	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
22	Check: Does the UE transmit an RRCConnectionSetupComplete message including a SERVICE REQUEST message?	–>	RRCConnectionSetupComplete	3	P
23-26	Steps 6 to 9 of the generic radio bearer establishment procedure in TS 36.508 subclause 4.5.3.3 are executed to successfully complete the service request procedure.	–	–	–	–
27	SS releases the RRC Connection.	–>	RRCConnectionRelease	–	–

8.1.1.2a.3.3 Specific message contents

Table 8.1.1.2a.3.3-1: SystemInformationBlockType1 (Preamble)

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}
}
}
}
}

Table 8.1.1.2a.3.3-1A: SystemInformationBlockType1-BR-r13 (Preamble) when UE under test is CAT M1

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 8.1.1.2a.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	‘0001’B	2,56 seconds
eDRX value	‘0101’B	81,92 seconds

Table 8.1.1.2a.3.3-3: SystemInformationBlockType1 (step 1, table 8.1.1.2a.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	1	Default value is 0
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	Not present
nonCriticalExtension	Not present
}

Table 8.1.1.2a.3.3-3A: SystemInformationBlockType1-BR-r13 (step 1, table 8.1.1.2a.3.2-1) when UE under test is CAT M1

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	Not present
nonCriticalExtension	Not present
}
}

Table 8.1.1.2a.3.3-4: SystemInformationBlockType2 (step 1, Table 8.1.1.2a.3.2-1)

Derivation Path: 36.508 Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
prach-Config SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigIndex	9		FDD
prach-ConfigIndex	52	Set to index which denote subframe numbers different from the default one.	TDD
}
}
prach-ConfigCommon-v1310 SEQUENCE {			CEModeA,CEModeB
prach-ParametersListCE-r13 SEQUENCE {
prach-ConfigIndex-r13	9		FDD
prach-ConfigIndex-r13	52		TDD
}
}
}
}

Condition	Explanation
FDD	FDD cell environment
TDD	TDD cell environment
CEmodeA	Used for CE mode A testing
CEmodeB	Used for CE mode B testing

Table 8.1.1.2a.3.3-5: Paging (step 2, Table 8.1.1.2a.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList	Not present
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
redistributionIndication-r13	Not present
systemInfoModification-eDRX-r13	true
nonCriticalExtension	Not present
}
}
}
}
}

Table 8.1.1.2a.3.3-6: SystemInformationBlockType1 (step 15, table 8.1.1.2a.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	2	Default value is 0
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE {
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}

Table 8.1.1.2a.3.3-6A: SystemInformationBlockType1-BR-r13 (step 15, table 8.1.1.2a.3.2-1) when UE under test is CAT M1

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 8.1.1.2a.3.3-7: SystemInformationBlockType2 (step 15, Table 8.1.1.2a.3.2-1)

Derivation Path: 36.508 Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
prach-Config SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigIndex	3		FDD
prach-ConfigIndex	51		TDD
}
}
prach-ConfigCommon-v1310 SEQUENCE {			CEModeA,CEModeB
prach-ParametersListCE-r13 SEQUENCE {
prach-ConfigIndex-r13	3		FDD
prach-ConfigIndex-r13	51		TDD
}
}
}
}

Condition	Explanation
FDD	FDD cell environment
TDD	TDD cell environment
CEmodeA	Used for CE mode A testing
CEmodeB	Used for CE mode B testing

Table 8.1.1.2a.3.3-8: Paging (step 16, Table 8.1.1.2a.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList	Not present
systemInfoModification	true
}

8.1.1.3 RRC / Paging for connection in idle mode / Multiple paging records

8.1.1.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives a Paging message including only unmatched identities }

then { UE does not establish any RRC connection }

}

(2)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives a Paging message including any matched identity }

then { UE initiates RRC connection establishment and upon receipt of RRCConnectionSetup including uplinkPowerControlDedicated / deltaMCS-Enabled set to Ks value 1.25 the UE successfully establishes the RRC connection }

}

8.1.1.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.2.3, 5.3.3.2, 5.3.3.3 and 5.3.3.4.

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall

1> If in RRC_IDLE, for each of the Paging records included in the Paging message:

2> If the ue-identity included in the pagingRecordList matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity, the cn-Domain and the pagingCause to the upper layers.

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE state.

Upon initiation of the procedure, the UE shall:

…

1> If access to the cell, as specified above, is not barred:

2> apply the default configuration applicable for the antennaInformation as specified in 9.2.3, until explicitly receiving a configuration;

2> start timer T300;

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

NOTE 2: Upon initiating the connection establishment procedure, the UE is not required to ensure it maintains up to date system information applicable only for UEs in RRC_IDLE state. However, the UE needs to perform system information acquisition upon re-selection.

[TS 36.331, clause 5.3.3.3]

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the IE ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value and set the ue-Identity to this value;

NOTE 1 Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> Set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.

[TS 36.331, clause 5.3.3.4]

NOTE: Prior to this, lower layers allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> establish SRB1 in accordance with the received radioResourceConfiguration and as specified in 5.3.10;

1> if stored, discard the Inter-frequency priority information and the Inter-RAT priority information provided via dedicated signalling using the IE idleModeMobilityControlInfo;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> stop timer T320, if running;

1> enter RRC_CONNECTED state;

1> stop the cell re-selection procedure;

1> set the content of RRCConnectionSetupComplete message as follows:

2> set the selectedPLMN-Identity to the PLMN selected by upper layers [TS 23.122, TS 24.008] from the PLMN(s) included in the plmn-IdentityList broadcast, within SystemInformationBlockType1, in the cell where the RRC connection was established;

2> if upper layers provide the ‘Registered MME’, set the registeredMME as follows:

3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers, set the IE plmnIdentity to the value received from upper layers;

3> set the IEs mmegi and mmec to the value received from upper layers;

2> set the nas-DedicatedInformation to include the information received from upper layers;

2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the procedure ends.

8.1.1.3.3 Test description

8.1.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.1.1.3.3.2 Test procedure sequence

Table 8.1.1.3.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including only unmatched identities (incorrect S-TMSI).	<–	Paging	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message within 10s?	–>	RRCConnectionRequest	1	F
3	The SS transmits a Paging message including two unmatched identities and a matched identity.	<–	Paging	–	–
4	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	2	P
5	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
6	Check: Does the UE transmit an RRCConnectionSetupComplete message including SERVICE REQUEST to confirm the successful completion of the connection establishment?	–>	RRCConnectionSetupComplete	2	P
6A-6D	Steps 6 to 9 of the generic radio bearer establishment procedure in TS 36.508 subclause 4.5.3.3 are executed to successfully complete the service request procedure.	–	–	–	–
7	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?	–	–	2	–

8.1.1.3.3.3 Specific message contents

Table 8.1.1.3.3.3-1: Paging (step 1, Table 8.1.1.3.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE (1..maxPageRec)) OF SEQUENCE {	3 entries
ue-Identity[1] CHOICE {
s-TMSI	Set to the different value from the S-TMSI of the UE
}
cn-Domain [1]	ps
ue-Identity[2] CHOICE {
s-TMSI	Set to the different value from the S-TMSI of the UE
}
cn-Domain [2]	ps
ue-Identity[3] CHOICE {
s-TMSI	Set to the different value from the S-TMSI of the UE
}
cn-Domain [3]	ps
}
}

Table 8.1.1.3.3.3-2: Paging (step 3, Table 8.1.1.3.3.2-1)

Derivation Path: 36.508 Table 4.6.1-7
Information Element	Value/remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList SEQUENCE (SIZE (1..maxPageRec)) OF SEQUENCE {	3 entries
ue-Identity[1] CHOICE {
s-TMSI	Set to the different value from the S-TMSI of the UE
}
cn-Domain [1]	ps
ue-Identity[2] CHOICE {
s-TMSI	Set to the different value from the S-TMSI of the UE
}
cn-Domain [2]	ps
ue-Identity[3] CHOICE {
s-TMSI	Set to the value of the S-TMSI of the UE
}
cn-Domain [3]	ps
}
}

Table 8.1.1.3.3.3-3: RRCConnectionRequest (step 4, Table 8.1.1.3.3.2-1)

Derivation Path: 36.508 Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.1.1.3.3.3-4: RRCConnectionSetup-DeltaMCS (step 5, Table 8.1.1.3.3.2-1)

Derivation Path: 36.508, Table 4.6.1-17
Information Element	Value/remark	Comment	Condition
RRCConnectionSetup-DeltaMCS ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionSetup-r8 SEQUENCE {
radioResourceConfigDedicated	RadioResourceConfigDedicated-SRB1-DeltaMCS
}
}
}
}

Table 8.1.1.3.3.3-5: RadioResourceConfigDedicated-SRB1-DeltaMCS (Table 8.1.1.3.3.3-4)

Derivation Path: 36.508, Table 4.6.3-15,
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated-SRB1-DeltaMCS ::= SEQUENCE {
physicalConfigDedicated	PhysicalConfigDedicated–DeltaMCS using condition SRB1
}

Table 8.1.1.3.3.3-6: PhysicalConfigDedicated–DeltaMCS (Table 8.1.1.3.3.3-5)

Derivation Path: 36.508, Table 4.8.2.1.6-1
Information Element	Value/remark	Comment	Condition
PhysicalConfigDedicated–DeltaMCS ::= SEQUENCE {
uplinkPowerControlDedicated	UplinkPowerControlDedicated–DeltaMCS		SRB1
}

Table 8.1.1.3.3.3-7: UplinkPowerControlDedicated–DeltaMCS (Table 8.1.1.3.3.3-6)

Derivation Path: 36.508, Table 4.6.3-26
Information Element	Value/remark	Comment	Condition
UplinkPowerControlDedicated–DeltaMCS ::= SEQUENCE {
deltaMCS-Enabled	en1	Corresponds to Ks value 1.25 corresponding to “enabled”.
}

8.1.1.4 RRC / Paging for connection in idle mode / Shared network environment

8.1.1.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state having been registered in the TA of the current cell which has broadcasted a SystemInformationBlockType1 message including multiple PLMN identities }

ensure that {
when { UE receives a Paging message including an IE ue-Identity set to the S-TMSI which was allocated to the UE at the UE registration procedure }

then { UE establishes an RRC connection }

}

8.1.1.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.2.3, 5.3.3.2, 5.3.3.3 and 5.3.3.4.

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity and the cn-Domain to the upper layers.

…

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

…

1> if access to the cell, as specified above, is not barred:

2> apply the default physical channel configuration as specified in 9.2.4;

2> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

2> apply the default MAC main configuration as specified in 9.2.2;

2> apply the CCCH configuration as specified in 9.1.1.2;

2> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

2> start timer T300

2> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

…

[TS 36.331, clause 5.3.3.3]

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else

3> draw a random value in the range 0 .. 2⁴⁰-1 and set the ue-Identity to this value;

NOTE 1 Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

[TS 36.331, clause 5.3.3.4]

NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> enter RRC_CONNECTED;

1> stop the cell re-selection procedure;

1> set the content of RRCConnectionSetupComplete message as follows:

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:

3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers;

4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the ‘Registered MME’ received from upper layers;

3> set the mmegi and the mmec to the value received from upper layers;

2> set the dedicatedInfoNAS to include the information received from upper layers;

2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the procedure ends.

8.1.1.4.3 Test description

8.1.1.4.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.1.1.4.3.2 Test procedure sequence

Table 8.1.1.4.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	1	P
3	The SS transmit an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
4	Check: Does the UE transmit an RRCConnectionSetupComplete message including SERVICE REQUEST and an IE selectedPLMN-Identity corresponding to the PLMN on which the UE has been registered to confirm the successful completion of the connection establishment?	–>	RRCConnectionSetupComplete	1	P
4A-4D	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–
5	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?	–	–	1	–

8.1.1.4.3.3 Specific message contents

Table 8.1.1.4.3.3-1: SystemInformationBlockType1 (all steps, Table 8.1.1.4.3.2-1)

Derivation Path: 36.508 Table 4.4.3.2-3
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
cellAccessRelatedInformation SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE (1..6)) OF SEQUENCE {	2 entries
plmn-Identity[1] SEQUENCE {
mcc	See Table 8.1.1.4.3.3-1A
mnc	See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[1]	notReserved
plmn-Identity[2] SEQUENCE {
mcc	See Table 8.1.1.4.3.3-1A
mnc	See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[2]	notReserved
}
}
}

Table 8.1.1.4.3.3-1A: SystemInformationBlockType1-BR-r13 (all steps when UE under test is CAT M1, Table 8.1.1.4.3.2-1)

Derivation Path: 36.508 Table 4.4.3.2-3A
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
cellAccessRelatedInformation SEQUENCE {
plmn-IdentityList SEQUENCE (SIZE (1..6)) OF SEQUENCE {	2 entries
plmn-Identity[1] SEQUENCE {
Mcc	See Table 8.1.1.4.3.3-1A
Mnc	See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[1]	notReserved
plmn-Identity[2] SEQUENCE {
Mcc	See Table 8.1.1.4.3.3-1A
Mnc	See Table 8.1.1.4.3.3-1A
}
cellReservedForOperatorUse[2]	notReserved
}
}
}

The PLMN Identity list broadcasted on the BCCH in Cell 1 shall be configured as defined in the table below.

Table 8.1.1.4.3.3-1A: PLMN Identity List broadcasted for Cell 1

Cell	PLMN Identity (1)		PLMN Identity (2)
Cell	MCC digits	MNC digits	MCC digits	MNC digits
1	PLMN 1	PLMN 1	PLMN 2	PLMN 2

The definition of each PLMN code is found in table below.

PLMN	MCC digit			MNC digit
	1	2	3	1	2	3
1	(NOTE 2)			(NOTE 2)
2	(NOTE 3)			0	2	–

NOTE 1: “–“ (dash) denotes “not present”

NOTE 2: Set to the same Mobile Country Code and Mobile Network Code stored in EF_IMSI on the test USIM card for PLMN 1.

NOTE 3: Set to the same Mobile Country Code stored in EF_IMSI on the test USIM card for PLMN 2.

Table 8.1.1.4.3.3-2: RRCConnectionRequest (step 2, Table 8.1.1.4.3.2-1)

Derivation Path: 36.508 Table 4.6.1-15
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.1.1.4.3.3-3: RRCConnectionSetupComplete (step 4, Table 8.1.1.4.3.2-1)

Derivation Path: 36.508, Table 4.6.1-17
Information Element	Value/remark	Comment	Condition
RRCConnectionSetupComplete ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionSetupComplete-r8 SEQUENCE {
selectedPLMN-Identity	Set to the PLMN selected by upper layers
}
}
}
}

8.1.1.5 Void

8.1.1.6 RRC / BCCH modification in connected mode

8.1.1.6.1 Test Purpose (TP)

with { the UE is in E-UTRA RRC_CONNECTED }

ensure that {

when { the UE receives a Paging message including the systemInfoModification }

then { the UE re-acquires the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 }

8.1.1.6.2 Conformance requirements

References: The conformance requirements covered in the present test case are specified in: TS 36.331 clauses 5.3.2.3, 5.2.2.3 and 5.2.2.4.

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

…

1> if the systemInfoModification is included:

2> re-acquire the required system information using the system information acquisition procedure as specified in 5.2.2.

…

[TS 36.331, clause 5.2.2.3]

The UE shall:

1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as the ‘required’ system information:

…

2> if in RRC_CONNECTED:

3> the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 as well as SystemInformationBlockType8, depending on support of CDMA2000;

…

[TS 36.331, clause 5.2.2.4]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1;

1> if the procedure is triggered by a system information change notification:

2> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification period following the one in which the change notification was received;

NOTE 1: The UE continues using the previously received system information until the new system information has been acquired.

…

NOTE 2: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer present, the UE should stop trying to acquire the particular SIB.

8.1.1.6.3 Test description

8.1.1.6.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18], and using the condition no_periodic_BSR_or_PHR.

8.1.1.6.3.2 Test procedure sequence

Table 8.1.1.6.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits a Paging message paging occasion including a systemInfoModification.	<–	Paging	–	–
2	From the beginning of the next modification period the SS transmits a modified SystemInformationBlockType1 and SystemInformationBlockType2 as specified.	–	–	–	–
3	During the first on duration period after the end of the modification period where SystemInformationBlockType2 was modified (see step 2), the SS transmits a PDCCH order including a dedicated preamble.	–	–	–	–
4	Check: Does the UE initiate a random access procedure using prach-ConfigIndex given in step 2 (i.e. for FDD n subframe number 7 and for TDD in subframe number 6)?	–	–	1	P
5	The SS transmits Random Access Response with RAPID corresponding to preamble in steps 3 and 4.	–	–	–	–

8.1.1.6.3.3 Specific message contents

Table 8.1.1.6.3.3-1: RRCConnectionReconfiguration (preamble, step 8, TS 36.508 table 4.5.3.3-1)

Derivation path: 36.508 table 4.6.1-8
Information Element	Value/Remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE {
rrcConnectionReconfiguration-r8 {
radioResourceConfigDedicated {
mac-MainConfig {
explicitValue {
drx-Config	Not present
}
}
}
}
}
}
}

Table 8.1.1.6.3.3-2: SystemInformationBlockType1 (step 2, table 8.1.1.6.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1 ::= SEQUENCE {
systemInfoValueTag	1	Default value is 0
}

Table 8.1.1.6.3.3-3: SystemInformationBlockType2 (step 2, table 8.1.1.6.3.2-1)

Derivation path: 36.508 Table 4.4.3.3-1
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
radioResourceConfigCommon SEQUENCE {
prach-Config SEQUENCE {
prach-ConfigInfo SEQUENCE {
prach-ConfigIndex	5	The default is 3	FDD
prach-ConfigIndex	52	The default is 51	TDD
}
}
}
}

8.1.1.7 RRC / Paging / EAB active

8.1.1.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state and configured for “Extended Access Barring” }

ensure that {

when { when EAB that applies to the UE’s Access Classes is being broadcast by the network and UE receives a Paging message including an ue-Identity set to the S-TMSI which was allocated to the UE at the UE registration procedure }

then { UE establishes an RRC connection }

}

8.1.1.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 24.301, clause 5.2.2.4, and D.1, TS 36.331, clause 5.2.1.6, 5.3.2.3, 5.3.3.2, 5.3.3.3, 5.3.3.12 and 5.3.3.4.

[TS 24.301, clause D.1]

When EMM requests the establishment of a NAS-signalling connection, the RRC establishment cause used by the UE shall be selected according to the NAS procedure as specified in table D.1.1. The EMM shall also indicate to the lower layer for the purpose of access control, the call type associated with the RRC establishment cause as specified in table D.1.1. If the UE is configured for EAB (see the "ExtendedAccessBarring" leaf of NAS configuration MO in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17]), the EMM shall indicate to the lower layer for the purpose of access control that EAB applies for this request except for the following cases:

– the UE is accessing the network with one of the access classes 11 – 15;

– the UE is answering to paging;

– the RRC Establishment cause is set to "Emergency call"; or

– the UE is configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of the NAS configuration MO as specified in 3GPP TS 24.368 [15A] or 3GPP TS 31.102 [17]) and receives an indication from the upper layers to override EAB.

[TS 36.331, clause 5.2.2.4]

The UE shall:

…

1> not initiate the RRC connection establishment subject to EAB until the UE has a valid version of SystemInformationBlockType14, if broadcast;

…

1> if the UE is EAB capable:

2> when the UE does not have stored a valid version of SystemInformationBlockType14 upon entering RRC_IDLE, or when the UE acquires SystemInformationBlockType1 following EAB parameters change notification or upon entering a cell during RRC_IDLE:

3> if schedulingInfoList indicates that SystemInformationBlockType14 is present:

4> start acquiring SystemInformationBlockType14 immediately;

3> else:

4> discard SystemInformationBlockType14, if previously received;

NOTE 4: EAB capable UEs start acquiring SystemInformationBlockType14 as described above even when systemInfoValueTag in SystemInformationBlockType1 has not changed.

NOTE 5: EAB capable UEs maintain an up to date SystemInformationBlockType14 in RRC_IDLE.

[TS 36.331, clause 5.2.1.6]

Change of EAB parameters can occur at any point in time. The EAB parameters are contained in SystemInformationBlockType14. The Paging message is used to inform EAB capable UEs in RRC_IDLE about a change of EAB parameters or that SystemInformationBlockType14 is no longer scheduled. If the UE receives a Paging message including the eab-ParamModification, it shall acquire SystemInformationBlockType14 according to schedulingInfoList contained in SystemInformationBlockType1. If the UE receives a Paging message including the eab-ParamModification while it is acquiring SystemInformationBlockType14, the UE shall continue acquiring SystemInformationBlockType14 based on the previously acquired schedulingInfoList until it re-acquires schedulingInfoList in SystemInformationBlockType1.

NOTE: The EAB capable UE is not expected to periodically check schedulingInfoList contained in SystemInformationBlockType1.

…

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity, and the cn-Domain to the upper layers.

…

1> if in RRC_IDLE, the eab-ParamModification is included and the UE is EAB capable:

2> consider previously stored SystemInformationBlockType14 as invalid;

2> re-acquire SystemInformationBlockType1 immediately, i.e., without waiting until the next system information modification period boundary as specified in 5.2.1.6;

2> re-acquire SystemInformationBlockType14 using the system information acquisition procedure as specified in 5.2.2.4;

…

[TS 36.331, clause 5.3.3.2]

The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE.

Upon initiation of the procedure, the UE shall:

1> if upper layers indicate that the RRC connection is subject to EAB (see TS 24.301 [35]):

2> if the result of the EAB check, as specified in 5.3.3.12, is that access to the cell is barred:

3> inform upper layers about the failure to establish the RRC connection and that EAB is applicable, upon which the procedure ends;

…

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> apply the CCCH configuration as specified in 9.1.1.2;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> start timer T300;

1> initiate transmission of the RRCConnectionRequest message in accordance with 5.3.3.3;

…

[TS 36.331, clause 5.3.3.3]

The UE shall set the contents of RRCConnectionRequest message as follows:

1> set the ue-Identity as follows:

2> if upper layers provide an S-TMSI:

3> set the ue-Identity to the value received from upper layers;

2> else:

3> draw a random value in the range 0 .. 2⁴⁰-1 and set the ue-Identity to this value;

NOTE 1: Upper layers provide the S-TMSI if the UE is registered in the TA of the current cell.

1> set the establishmentCause in accordance with the information received from upper layers;

The UE shall submit the RRCConnectionRequest message to lower layers for transmission.

[TS 36.331, clause 5.3.3.4]

NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo or inherited from another RAT;

1> stop timer T300;

1> stop timer T302, if running;

1> stop timer T303, if running;

1> stop timer T305, if running;

1> perform the actions as specified in 5.3.3.7;

1> stop timer T320, if running;

1> enter RRC_CONNECTED;

1> stop the cell re-selection procedure;

1> consider the current cell to be the PCell;

1> set the content of RRCConnectionSetupComplete message as follows:

2> set the selectedPLMN-Identity to the PLMN selected by upper layers (see TS 23.122 [11], TS 24.301 [35]) from the PLMN(s) included in the plmn-IdentityList in SystemInformationBlockType1;

2> if upper layers provide the ‘Registered MME’, include and set the registeredMME as follows:

3> if the PLMN identity of the ‘Registered MME’ is different from the PLMN selected by the upper layers:

4> include the plmnIdentity in the registeredMME and set it to the value of the PLMN identity in the ‘Registered MME’ received from upper layers;

3> set the mmegi and the mmec to the value received from upper layers;

…

2> set the dedicatedInfoNAS to include the information received from upper layers;

…

2> submit the RRCConnectionSetupComplete message to lower layers for transmission, upon which the procedure ends.

[TS 36.331, clause 5.3.3.12]

The UE shall:

1> if SystemInformationBlockType14 is present and includes the eab-Param:

2> if the eab-Common is included in the eab-Param:

3> if the UE belongs to the category of UEs as indicated in the eab-Category contained in eab-Common; and

3> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the eab-BarringBitmap contained in eab-Common is set to one:

4> consider access to the cell as barred;

3> else:

4> consider access to the cell as not barred due to EAB;

8.1.1.7.3 Test description

8.1.1.7.3.1 Pre-test conditions

System Simulator:

– Cell 1.

– System information combination 21 as defined in TS 36.508[18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

– The UE is configured for “Extended Access Barring”

– The UE belong to access class 0

The UE is equipped with a USIM containing values shown in Table 8.1.1.7.3–1.

Table 8.1.1.7.3-1: USIM Configuration

USIM field	Value
EF_UST	Service 96 is supported.
EF_NASCONFIG	“ExtendedAccessBarring is set to 1 which indicate the extended access barring is applied for the UE” as defined in TS 24.368, clause 5.6.
EF_NASCONFIG	“NAS_SignallingPriority is set to NAS signalling low priority” as defined in TS 24.368, clause 5.3.

NOTE: As per 23.401 cl. 4.3.17.4, UE’s configurations of low access priority and Extended Access Barring shall match each other.

Preamble:

– The UE is in state Registered, Idle mode (state 2) according to [18].

8.1.1.7.3.2 Test procedure sequence

Table 8.1.1.7.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
0	The SS transmits a Paging message including eab-ParamModification. The SS start transmitting SystemInformationBlockType14 as defined in Table 8.1.1.7.3.3-1 in the same system information modification period.	<–	Paging	–	–
1	Wait for 15s for the UE to receive system information.	–	–	–	–
2	The SS transmits a Paging message including a matched identity.	<–	Paging	–	–
3	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	1	P
4	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
5	Check: Does the UE transmit an RRCConnectionSetupComplete message including SERVICE REQUEST to confirm the successful completion of the connection establishment?	–>	RRCConnectionSetupComplete	1	P
6-9	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–
10	Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?	–	–	1	P
11	SS initiates Detach procedure with the Detach Type IE “re-attach not required” and no EMM cause IE included, as defined in Table 8.1.1.7.3.3-1.	<–	DETACH REQUEST	–	–
12	The UE transmits a DETACH ACCEPT message on Cell 1.	–>	DETACH ACCEPT	–	–
13	The SS releases the RRC connection.	–	–	–	–

8.1.1.7.3.3 Specific message contents

Table 8.1.1.7.3.3-1: SystemInformationBlockType14 (all steps in table 8.1.1.7.3.2-1)

Derivation path: 36.508 Table 4.4.3.3-13A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType14-r11 ::= SEQUENCE {
eab-Common-r11 ::= SEQUENCE {
eab-Config-r11 ::= SEQUENCE {
eab-Category-r11	‘a’	All UEs
eab-BarringBitmap-r11	‘1000000000’	EAB active for access class 0
}
}
lateNonCriticalExtension	Not present
}

Table 8.1.1.7.3.3-2: RRCConnectionRequest (step 3, Table 8.1.1.7.3.2-1)

Derivation Path: 36.508 Table 4.6.1-16
Information Element	Value/remark	Comment	Condition
RRCConnectionRequest ::= SEQUENCE {
criticalExtensions CHOICE {
rrcConnectionRequest-r8 SEQUENCE {
establishmentCause	mt-Access
}
}
}

Table 8.1.1.7.3.3-3: SystemInformationBlockType14 (preamble)

Derivation path: 36.508 Table 4.4.3.3-13A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType14-r11 ::= SEQUENCE {
eab-Common-r11 ::= SEQUENCE {
eab-Config-r11 ::= SEQUENCE {
eab-Category-r11	‘a’	All UEs
eab-BarringBitmap-r11	‘0000000000’	EAB not active
}
}
lateNonCriticalExtension	Not present
}

Table 8.1.1.7.3.3-4: Message ATTACH REQUEST (preamble)

Derivation path: TS 36.508 Table 4.7.2-4
Information Element	Value/Remark	Comment	Condition
Device properties	1	“MS is configured for NAS signalling low priority”

Table 8.1.1.7.3.3-5: Paging (step 0, Table 8.1.1.7.3.2-1)

Derivation path: 36.508 Table 4.6.1-7
Information Element	Value/Remark	Comment	Condition
Paging ::= SEQUENCE {
pagingRecordList	Not present
systemInfoModification	Not present
etws-PrimaryNotificationIndication	Not present
nonCriticalExtension SEQUENCE {
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
cmas-Indication-r9	Not present
nonCriticalExtension SEQUENCE {
eab-ParamModification-r11	true
nonCriticalExtension SEQUENCE {}	Not present
}
}
}
}

Table 8.1.1.7.3.3-6: Message DETACH REQUEST (step 11, Table 8.1.1.7.3.2-1)

Derivation path: 36.508 Table 4.7.2-12
Information Element	Value/Remark	Comment	Condition
Detach type	‘010’B	“re-attach not required”
EMM cause	Not present

8.1.1.8 RRC / Paging / DRX Operation / Enhanced Coverage / WUS

8.1.1.8.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state in enhanced cell coverage and configured for and WUS }

ensure that {

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

then { UE establishes RRC connection }

}

8.1.1.8.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]

When 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 the UE supports GWUS and GWUS configuration is provided in system information, UE shall monitor WUS using the GWUS parameters provided in System Information as defined in clause 7.5. 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].

8.1.1.8.3 Test description

8.1.1.8.3.1 Pre-test conditions

System Simulator:

– Cell 1 supports CE.

UE:

– None

Preamble:

– The UE is in state Registered, Idle mode (state 2-CE) according to [18].

8.1.1.8.3.2 Test procedure sequence

Table 8.1.1.8.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits WUS followed by Paging message with a matched identity	<–	Paging	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	1	P
3	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
4	UE transmits RRCConnectionSetupComplete message including SERVICE REQUEST to confirm the successful completion of the connection establishment	–>	RRCConnectionSetupComplete	–	–
5-8	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–

8.1.1.8.3.3 Specific message contents

Table 8.1.1.8.3.3-1: SystemInformationBlockType2 (preamble and all steps, table 8.1.1.8.3.2-1)

Derivation Path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
RadioResourceConfigCommonSIB-DEFAULT ::= SEQUENCE {
wus-Config-r15 ::= SEQUENCE {
maxDurationFactor-r15	one16th
numPOs-r15	n1
freqLocation-r15	n0
timeOffsetDRX-r15	ms80
timeOffset-eDRX-Short-r15	ms160
timeOffset-eDRX-Long-r15	Not Present
}
wus-Config-v1560 ::= SEQUENCE {
powerBoost-r15	dB0
}
}
}

8.1.1.9 RRC / Paging / eDRX Operation / Enhanced Coverage / WUS

8.1.1.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state in enhanced cell coverage and configured for eDRX and WUS }

ensure that {

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

then { UE establishes RRC connection }

}

8.1.1.9.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]

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

– 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].

8.1.1.9.3 Test description

8.1.1.9.3.1 Pre-test conditions

System Simulator:

– Cell 1 supports CE.

UE:

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

Preamble:

– The UE is in state Registered, Idle mode (state 2-CE) according to [18]. UE sent “extended DRX parameters IE” in ATTACH REQUEST message and received “extended DRX parameters IE” in ATTACH ACCEPT message

8.1.1.9.3.2 Test procedure sequence

Table 8.1.1.9.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits WUS followed by Paging message with a matched identity	<–	Paging	–	–
2	Check: Does the UE transmit an RRCConnectionRequest message?	–>	RRCConnectionRequest	1	P
3	The SS transmits an RRCConnectionSetup message.	<–	RRCConnectionSetup	–	–
4	Check: Does the UE transmit an RRCConnectionSetupComplete message including SERVICE REQUEST to confirm the successful completion of the connection establishment?	–>	RRCConnectionSetupComplete	–	–
5-8	Steps 6 to 9 of the generic radio bearer establishment procedure (TS 36.508 4.5.3.3-1) are executed to successfully complete the service request procedure.	–	–	–	–

8.1.1.9.3.3 Specific message contents

Table 8.1.1.9.3.3-1: SystemInformationBlockType1-BR-r13 (all steps, table 8.1.1.9.3.2-1)

Derivation path: 36.508 Table 4.4.3.2-3A
Information Element	Value/Remark	Comment	Condition
SystemInformationBlockType1-BR-r13 ::= SEQUENCE {
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
nonCriticalExtension SEQUENCE{
hyperSFN-r13	Current H-SFN Value
eDRX-Allowed-r13	true
nonCriticalExtension	Not present
}
}

Table 8.1.1.9.3.3-2: SystemInformationBlockType2 (all steps, table 8.1.1.9.3.2-1)

Derivation Path: 36.508 clause 4.4.3.3, Table 4.4.3.3-1
Information Element	Value/remark	Comment	Condition
SystemInformationBlockType2 ::= SEQUENCE {
RadioResourceConfigCommonSIB-DEFAULT ::= SEQUENCE {
wus-Config-r15 ::= SEQUENCE {
maxDurationFactor-r15	one16th
numPOs-r15	n2
freqLocation-r15	n4
timeOffsetDRX-r15	ms80
timeOffset-eDRX-Short-r15	ms160
timeOffset-eDRX-Long-r15	Not Present
}
wus-Config-v1560 ::= SEQUENCE {
powerBoost-r15	dB0
}
}
}

Table 8.1.1.9.3.3-3 ATTACH ACCEPT (Preamble)

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