8.1.1 Paging

34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification

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

8.1.1.1 Paging for Connection in idle mode

8.1.1.1.1 Definition

8.1.1.1.2 Conformance requirement

A UE in idle mode, CELL_PCH state or URA_PCH state shall receive the paging information for all its monitored paging occasions. For an UE in idle mode, the paging occasions are specified in [25.304] and depend on the IE "CN domain specific DRX cycle length coefficient", as specified in subclause 8.6.3.1a. For a UE in CELL_PCH state or URA_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE "RRC State Indicator", as specified in subclauses 8.6.3.2 and 8.6.3.3 respectively.

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

If the UE is in idle mode, for each occurrence of the IE "Paging record" included in the message the UE shall:

1> if the IE "Used paging identity" is a CN identity:

2> compare the IE "UE identity" with all of its allocated CN UE identities:

2> if one match is found:

3> indicate reception of paging; and

3> forward the IE "CN domain identity", the IE "UE identity" and the IE "Paging cause" to the upper layers.

1> otherwise:

2> ignore that paging record.

In the UE, the initial direct transfer procedure shall be initiated, when the upper layers request establishment of a signalling connection. This request also includes a request for the transfer of a NAS message.

Upon initiation of the initial direct transfer procedure when the UE is in idle mode, the UE shall:

1> set the variable ESTABLISHMENT_CAUSE to the cause for establishment indicated by upper layers;

1> perform an RRC connection establishment procedure, according to subclause 8.1.3;

1> if the RRC connection establishment procedure was not successful:

2> indicate failure to establish the signalling connection to upper layers and end the procedure.

1> when the RRC connection establishment procedure is completed successfully:

2> continue with the initial direct transfer procedure as below.

Upon initiation of the initial direct transfer procedure when the UE is in CELL_PCH or URA_PCH state, the UE shall:

1> perform a cell update procedure, according to subclause 8.3.1, using the cause "uplink data transmission";

1> when the cell update procedure completed successfully:

2> continue with the initial direct transfer procedure as below.

The UE shall, in the INITIAL DIRECT TRANSFER message:

1> set the IE "NAS message" as received from upper layers; and

1> set the IE "CN domain identity" as indicated by the upper layers; and

1> set the IE "Intra Domain NAS Node Selector" as follows:

2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and

2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:

1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available;

2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;

3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.

1> calculate the START according to subclause 8.5.9 for the CN domain as set in the IE "CN Domain Identity"; and

1> include the calculated START value for that CN domain in the IE "START".

In CELL_FACH state, the UE shall:

1> include a measurement report in the IE "Measured results on RACH", as specified in the IE "Intra-frequency reporting quantity for RACH reporting" and the IE "Maximum number of reported cells on RACH" in System Information Block type 12 (or "System Information Block Type 11" if "System Information Block Type 12" is not being broadcast);

1> include in the IE "Measured results on RACH" all requested reporting quantities for cells for which measurements are reported.

The UE shall:

1> transmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3;

1> when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission:

2> confirm the establishment of a signalling connection to upper layers; and

2> add the signalling connection with the identity indicated by the IE "CN domain identity" in the variable ESTABLISHED_SIGNALLING_CONNECTIONS.

1> when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC:

2> the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.2 and 8.1.8, 3GPP TS 25.211 clause 5.3.3.10 (FDD), 3GPP TS 25.221 (TDD), 3GPP TS 25.304 clause 8.

8.1.1.1.3 Test purpose

1) For the CS domain

To confirm that the UE establishes an RRC connection after it receives a PAGING TYPE 1 message which includes IE "UE identity"(in IE "Paging Record") set to the IMSI of the UE, and responds with a correct INITIAL DIRECT TRANSFER message.

2) For the PS domain

To confirm that the UE establishes an RRC connection after it receives a PAGING TYPE 1 message which includes IE "UE identity"(in IE "Paging Record") set to the P-TMSI allocated by SS at initial attach and responds with a correct INITIAL DIRECT TRANSFER message.

8.1.1.1.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: MM-IDLE state and Updated update status with no TMSI (if CS supported)

GMM-Registered with a P-TMSI assigned (if PS supported)

the UE shall have an IMSI.

Test Procedure

SS transmits SYSTEM INFORMATION BLOCK TYPE 1 or 13 messages, depending on the CN type supported by the UE. The SS transmits a PAGING TYPE 1 message, which includes an unmatched CN UE identity for the UE in the idle state. The UE shall not change its state. The SS transmits a PAGING TYPE 1 message, which includes a matched CN UE identity for the UE in the idle state. During transmission of PAGING TYPE 1 messages, SS selects the correct paging indicator on the PICH in order to allow the UE to respond to paging. Then the UE transmits an RRC CONNECTION REQUEST to the SS, the SS transmits an RRC CONNECTION SETUP to the UE. When the UE receives this message, the UE establishes an RRC connection and transmits an RRC CONNECTION SETUP COMPLETE message and an INITIAL DIRECT TRANSFER message on the uplink DCCH.

NOTE: For UEs supporting GSM-MAP CN type only, SYSTEM INFORMATION TYPE 1 messages are to be sent by SS in this test case. On the other hand, SS transmits SYSTEM INFORMATION TYPE 13 messages if the UE under test supports only ANSI-41 CN type.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			SYSTEM INFORMATION BLOCK TYPE 13 or SYSTEM INFORMATION BLOCK TYPE 1	Transmit these messages on the BCCH. See default message contents in TS 34.108.
2			PAGING TYPE 1	The SS transmits the message, which includes an unmatched identity (incorrect IMSI), and the UE does not change its state.
3			PAGING TYPE 1	The SS transmits the message, which includes a matched identity. See default message contents in TS 34.108.
4			RRC CONNECTION REQUEST
5			RRC CONNECTION SETUP	SS assigns DPCH resources to allow UE to establish an RRC connection.
6			RRC CONNECTION SETUP COMPLETE
7			INITIAL DIRECT TRANSFER

Specific Message Contents

SYSTEM INFORMATION BLOCK TYPE 1 (Step 1) – for UEs supporting GSM-MAP core networks

Use the default message type found in TS 34.108, clause 6.1.

SYSTEM INFORMATION TYPE 13 (Step 1) – for UEs supporting ANSI-41 core networks

Use the default message type found in TS 34.108, clause 6.1.

PAGING TYPE 1 (Step 2)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
CHOICE Used paging identity	CN identity
– Paging cause	Terminating Call with one of the supported services
– CN domain identity	A Registered Domain (PS Domain or CS Domain)
– CHOICE UE Identity	IMSI
– IMSI	Set to an arbitrary octet string of length 7 bytes which is different from the IMSI value stored in the TEST USIM card.
BCCH modification info	Not Present

PAGING TYPE 1 (Step 3)

Use the default message type found in TS 34.108, clause 9.1.

Note that Separate message types are defined in TS 34.108 for the cases of TM (Speech in CS) and for TM (Packet in PS).

RRC CONNECTION REQUEST (Step 4)

Information Element	Value/remark
Message type
Initial UE identity	Same as the registered P-TMSI if PS supported by UE, otherwise the IMSI stored in the TEST USIM card.
Establishment Cause	Check to see if it is set to the same value as "Paging Cause" IE in the PAGING TYPE 1 message transmitted on step 3.
Protocol Error Indicator	Check to see if it is set to FALSE
Measured results on RACH	Not checked.

INITIAL DIRECT TRANSFER (Step 7) – for UEs supporting GSM-MAP core networks

Information Element	Value/remark
Message Type
Integrity check info	Not present
CN domain identity	CS domain or PS domain (as specified by the SS in the PAGING TYPE 1 message of Step 3)
Intra Domain NAS Node Selector
– CHOICE version	R99
— CHOICE CN type	GSM-MAP
— CHOICE Routing basis	IMSI (response to IMSI paging) in CS domain or Local (P)-TMSI in PS Domain
—- Routing parameter	If the IE "CN domain identity" is equal to "CS domain", bit string (10) consisting of DecimalToBinary [(IMSI div 10) mod 1000]. The first/ leftmost bit of the bit string contains the most significant bit of the result. If the IE "CN domain identity" is equal to "PS domain": The TMSI/ PTMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant. The "Routing parameter" is set to bits b14 through b23 of the TMSI/ PTMSI. The first/ leftmost/ most significant bit of the bit string contains bit b23 of the TMSI/ PTMSI.
— Entered parameter	Not checked
NAS message	Not checked
START	Not checked
Measured results on RACH	Not checked

INITIAL DIRECT TRANSFER (Step 7) – for UEs supporting ANSI-41 core networks

Information Element	Value/remark
Message Type
Integrity check info	Not present
CN domain identity	CS domain or PS domain (as specified by the SS in the PAGING TYPE 1 message of Step 3)
Intra Domain NAS Node Selector
– CHOICE version	ANSI-41 : Bitstring(14), all bits set to 0
NAS message	Not checked
START	Not checked
Measured results on RACH	Not checked

8.1.1.1.5 Test requirement

After step 2 the UE shall not respond to PAGING TYPE 1 message sent in step 2.

After step 3 the UE shall transmit RRC CONNECTION REQUEST message on the uplink CCCH.

After step 5 the UE shall have an RRC connection based on dedicated physical channel resources and transmit an RRC CONNECTION SETUP COMPLETE message and INITIAL DIRECT TRANSFER message on the uplink DCCH.

8.1.1.2 Paging for Connection in connected mode (CELL_PCH)

8.1.1.2.1 Definition

8.1.1.2.2 Conformance requirement

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below:

If the UE is in connected mode, for each occurrence of the IE "Paging record" included in the message the UE shall:

1> if the IE "Used paging identity" is a UTRAN identity and if this U-RNTI is the same as the U-RNTI allocated to the UE:

2> if the optional IE "CN originated page to connected mode UE" is included:

3> indicate reception of paging; and

3> forward the IE "CN domain identity", the IE "Paging cause" and the IE "Paging record type identifier" to the upper layers.

2> otherwise:

3> perform a cell update procedure with cause "paging response" as specified in subclause 8.3.1.2.

2> ignore any other remaining IE "Paging record" that may be present in the message.

1> otherwise:

2> ignore that paging record.

If the CELL UPDATE CONFIRM message:

– does not include "RB information elements"; and

– does not include "Transport channel information elements"; and

– does not include "Physical channel information elements"; and

– includes "CN information elements"; or

– includes the IE "Ciphering mode info"; or

– includes the IE "Integrity protection mode info"; or

– includes the IE "New C-RNTI"; or

– includes the IE "New U-RNTI":

the UE shall:

1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.

Reference

3GPP TS 25.331 clause 8.1.2, 8.3.1.7.

8.1.1.2.3 Test purpose

To confirm that the UE enters the CELL_FACH state after it receives a PAGING TYPE 1 message which indicates that the paging has originated from UTRAN. To verify that the UE performs cell update procedure after entering the CELL_FACH state.

8.1.1.2.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: CELL_PCH state (state 6-12) as specified in clause 7.4 of TS 34.108, with a valid U-RNTI already assigned by the SS.

Test Procedure

SS transmits SYSTEM INFORMATION BLOCK TYPE 1 or 13 messages, depending on the CN type supported by the UE. The SS transmits a PAGING TYPE 1 message, which includes an unmatched U-RNTI. The UE does not change its state. Then SS transmits a PAGING TYPE 1 message with a matched identifier but originates from the CN instead of UTRAN. The UE shall not change state after receiving this message. The SS transmits a PAGING TYPE 1 message, which includes a matched U-RNTI. Then the UE enters the CELL_FACH state and performs the cell updating procedure.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			SYSTEM INFORMATION BLOCK TYPE 13 or SYSTEM INFORMATION BLOCK TYPE 1	Transmit these messages on the BCCH, in addition to the normal BCCH transmissions. See specific message contents
2			PAGING TYPE 1	The SS transmits a message including an unmatched identifier. UE shall not respond to the paging.
3			PAGING TYPE 1	The SS transmits a message includes a matched identifier but with the used paging identity being a CN identity, UE shall not respond to the paging.
4			PAGING TYPE 1	The SS transmits the message with used paging identity being a UTRAN identity and including the UE’s assigned U-RNTI
5			CELL UPDATE	The UE enters the CELL_FACH state. UE performs cell updating procedure. The CELL UPDATE message shall contain the value "Cell Update Cause" set to "paging response".
6			CELL UPDATE CONFIRM	See message content.
7			UTRAN MOBILITY INFORMATION CONFIRM

Specific Message Contents

PAGING TYPE 1 (Step 2)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI
– SRNC Identity	Set to an arbitrary 16-bit string which is different from the SRNC identity assigned.
– S-RNTI	Set to an arbitrary 20-bit string which is different from the S-RNTI assigned.
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

PAGING TYPE 1 (Step 3)

Same as the PAGING TYPE 1 message as in step 3 of clause 8.1.1.1.4.

PAGING TYPE 1 (Step 4)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI
– SRNC Identity	Set to the same SRNC identity as previously assigned.
– S-RNTI	Set to the same S-RNTI as previously assigned.
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

SYSTEM INFORMATION BLOCK TYPE 13

Use the same SYSTEM INFORMATION BLOCK TYPE 13 message as specified in clause 8.1.1.1.4.

SYSTEM INFORMATION BLOCK TYPE 1

Use the same SYSTEM INFORMATION BLOCK TYPE 1 message as specified in clause 8.1.1.1.4.

CELL UPDATE CONFIRM (Step 6)

Use the message sub-type in default message content defined in [9] (TS 34.108) Clause 9, with the following exceptions.

Information Element	Value/Remarks
New C-RNTI	‘1010 1010 1010 1010’

UTRAN MOBILITY INFORMATION CONFIRM (Step 7)

Only the message type is checked.

8.1.1.2.5 Test requirement

After step 2 the UE shall not respond to the PAGING TYPE 1 message sent in step 2.

After step 3 the UE shall not respond to the PAGING TYPE 1 message sent in step 3.

After step 4 the UE shall enter the CELL FACH state and send a CELL UPDATE message with "Cell Update Cause" IE set to "paging response".

After step 6 the UE shall be in the CELL_FACH state and shall transmit UTRAN MOBILITY INFORMATION CONFIRM message.

8.1.1.3 Paging for Connection in connected mode (URA_PCH)

8.1.1.3.1 Definition

8.1.1.3.2 Conformance requirement

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below:

If the UE is in connected mode, for each occurrence of the IE "Paging record" included in the message the UE shall:

1> if the IE "Used paging identity" is a UTRAN identity and if this U-RNTI is the same as the U-RNTI allocated to the UE:

2> if the optional IE "CN originated page to connected mode UE" is included:

3> indicate reception of paging; and

3> forward the IE "CN domain identity", the IE "Paging cause" and the IE "Paging record type identifier" to the upper layers.

2> otherwise:

3> perform a cell update procedure with cause "paging response" as specified in subclause 8.3.1.2.

2> ignore any other remaining IE "Paging record" that may be present in the message.

1> otherwise:

2> ignore that paging record.

If the CELL UPDATE CONFIRM message:

– does not include "RB information elements"; and

– does not include "Transport channel information elements"; and

– does not include "Physical channel information elements"; and

– includes "CN information elements"; or

– includes the IE "Ciphering mode info"; or

– includes the IE "Integrity protection mode info"; or

– includes the IE "New C-RNTI"; or

– includes the IE "New U-RNTI":

the UE shall:

1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.

Reference

3GPP TS 25.331 clause 8.1.2, 8.3.1.7.

8.1.1.3.3 Test purpose

To confirm that the UE enters the CELL_FACH state after it receives a PAGING TYPE 1 message in which the IE "Used paging identity" is set to "UTRAN identity", and the UE takes the U-RNTI value assigned to it in the IE "U-RNTI".

8.1.1.3.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: URA_PCH state (state 6-13) as specified in clause 7.4 of TS 34.108, with a valid U-RNTI assigned by the SS.

Test Procedure

The SS transmits a PAGING TYPE 1 message, which includes an unmatched U-RNTI. The UE does not change its current state. The SS transmits a PAGING TYPE 1 message which includes a matched U-RNTI. Then the UE listens to it and enters the CELL_FACH state to transmit a CELL UPDATE message using uplink CCCH in respond to the paging.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			PAGING TYPE 1	The SS transmits the message that includes an unmatched identifier, but UE does not change its state.
2			PAGING TYPE 1	The SS transmits the message that includes a matched identifier.
3			CELL UPDATE	The UE enters the CELL_FACH state.
4			CELL UPDATE CONFIRM	See message content.
5			UTRAN MOBILITY INFORMATION CONFIRM

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI
– SRNC Identity	Set to an unused SRNC identity which is different from the SRNC identity assigned.
– S-RNTI	Set to an arbitrary 20-bit string which is different from the S-RNTI assigned.
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

PAGING TYPE 1 (Step 2)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI
– SRNC Identity	Set to the previously assigned SRNC identity
– S-RNTI	Set to previously assigned S-RNTI
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

CELL UPDATE CONFIRM (Step 4)

Use the message sub-type in default message content defined in [9] (TS 34.108) Clause 9, with the following exceptions.

Information Element	Value/Remarks
New C-RNTI	‘1010 1010 1010 1010’

UTRAN MOBILITY INFORMATION CONFIRM (Step 5)

Only the message type is checked.

8.1.1.3.5 Test requirement

After step 1 the UE shall not respond to the paging.

After step 2 the UE shall enter the CELL FACH state, and transmit CELL UPDATE message to initiate the cell updating procedure with the paging cause set to "paging response".

After step 4 the UE shall be in the CELL_FACH state and shall transmit UTRAN MOBILITY INFORMATION CONFIRM message.

8.1.1.4 Paging for notification of BCCH modification in idle mode

8.1.1.4.1 Definition

8.1.1.4.2 Conformance requirement

A UE in idle mode state shall receive the paging information for all its monitored paging occasions. For an UE in idle mode, the paging occasions are specified in TS 25.304 and depend on the IE "CN domain specific DRX cycle length coefficient".

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

…

If the IE "BCCH modification info" is included, any UE in idle mode state shall perform the actions as specified in TS 25.331 subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message.

The UE shall:

1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG.

1> if the value tags differ:

2> read the master information block on BCH;

2> if the value tag of the master information block in the system information is the same as the value in IE "MIB value tag" in "BCCH modification info" but different from the value tag stored in the variable VALUE_TAG:

3> perform actions as specified in TS 25.331 subclause 8.1.1.5.

…

Upon reception of the master information block, the UE shall:

1> compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG;

1> if the value tags differ:

2> store the value tag into the variable VALUE_TAG for the master information block;

2> read and store scheduling information included in the master information block.

….

For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE shall perform the following actions:

1> for all system information blocks with area scope "PLMN" or "Equivalent PLMN" that use value tags:

2> compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TAG for that system information block;

2> if the value tags differ:

3> store the value tag read in scheduling information for that system information block into the variable VALUE_TAG;

3> read and store the IEs of that system information block.

…

Reference

3GPP TS 25.331 clause 8.1.1, 8.1.2.

8.1.1.4.3 Test purpose

To confirm that the UE checks the new value tag of the master information block and reads the updated SYSTEM INFORMATION BLOCK messages after it receives a PAGING TYPE 1 message which includes the IE "BCCH Modification Information".

8.1.1.4.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

Test Procedure

The SS transmits a PAGING TYPE 1 message. This message addresses the UE using its (P)TMSI and the "paging cause" IE set to a terminating call type that is supported by the UE. The UE shall respond with RRC CONNECTION REQUEST message. Then SS shall transmit RRC CONNECTION REJECT message to UE.

At the paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses the UE using its (P)TMSI and the "paging cause" IE set to a terminating call type that is supported by the UE. The UE shall respond with RRC CONNECTION REQUEST message. Then SS shall transmit RRC CONNECTION REJECT message to UE.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			PAGING TYPE 1	SS starts to transmit this message on the PCCH at the correct paging occasion.
1a			RRC CONNECTION REQUEST
1b			RRC CONNECTION REJECT
2			PAGING TYPE 1	SS transmits the message including the IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block.
2a			Void
3	 		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. At the same time, SS starts to transmit the affected SIB TYPE 5 / SIB TYPE 5bis messages continuously. The IE "Available Signature" is changed from "0000 0000 1111 1111(B)" to "1111 1111 0000 0000(B)" (for FDD) and Available SYNC_UL codes is changed from “11110000(B)” to “00001111(B)”.
3a				SS waits 5s (to ensure that the UE has time to read the new system information)
4			PAGING TYPE 1	SS starts to transmit this message continuously on the PCCH at the correct paging occasion.
5			RRC CONNECTION REQUEST
6			RRC CONNECTION REJECT

Specific Message Contents

PAGING TYPE 1 (Step 1 and 4)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	CN identity
– Paging Cause	Terminating Call with one of the supported services
– CN Domain Identity	Supported Domain (PS Domain or CS Domain)
– CHOICE UE Identity	Local (P)TMSI
– Routing parameter	Same as registered TMSI or P-TMSI
BCCH modification info	Not Present

RRC CONNECTION REJECT (Step 1b)

Use the same message type found in [9] TS 34.108 clause 9.

PAGING TYPE 1 (Step 2)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
MIB Value Tag	Set to (Current MIB value tag + 1)
BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 3)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 2
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis (Step 3) (FDD)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	FDD
– Available Signature	‘1111 1111 0000 0000’B

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (1.28 Mcps TDD)

– PRACH system information list
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– SYNC_UL info
– SYNC_UL codes bitmap	"00001111"
– Access Service Class
– ASC Settings	(ASC#0 to ASC #7)
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– Available SYNC_UL codes indices	"00001111"

RRC CONNECTION REJECT

Use the same message type found in TS 34.108, clause 9.

8.1.1.4.5 Test requirement

After step 1 the UE shall transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1 messages sent in step 1, using an allowed signature according to original IE "Available signature"(FDD) )/ "Available SYNC_UL codes indices "(1.28 Mcps TDD) in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

After step 4 the UE shall transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1 messages sent in step 4, using an allowed signature according to modified IE "Available signature"(FDD)/ "Available SYNC_UL codes indices "(1.28 Mcps TDD) in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

8.1.1.5 Paging for notification of BCCH modification in connected mode (CELL_PCH)

8.1.1.5.1 Definition

8.1.1.5.2 Conformance requirement

A UE in CELL_PCH state shall receive the paging information for all its monitored paging occasions. For a UE in CELL_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE "RRC State Indicator", as specified in TS 25.331 subclauses 8.6.3.2 and 8.6.3.3 respectively.

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

…

If the IE "BCCH modification info" is included, any UE in CELL_PCH state shall perform the actions as specified in TS 25.331 subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message.

The UE shall:

1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG.

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in TS 25.331 subclause 8.1.1.5.

…

Upon reception of the master information block, the UE shall:

1> compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG;

1> if the value tags differ:

2> store the value tag into the variable VALUE_TAG for the master information block;

2> read and store scheduling information included in the master information block.

….

For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE shall perform the following actions:

1> for all system information blocks with area scope "PLMN" or "Equivalent PLMN" that use value tags:

2> compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TAG for that system information block;

2> if the value tags differ:

3> store the value tag read in scheduling information for that system information block into the variable VALUE_TAG;

3> read and store the IEs of that system information block.

…

Reference

3GPP TS 25.331 clause 8.1.1, 8.1.2.

8.1.1.5.3 Test purpose

To confirm that the UE, in addition to any actions caused by the IE "Paging record" occurrences in the PAGING TYPE 1 message, checks the new value tag of the master information block, and read the SYSTEM INFORMATION messages after it receives a PAGING TYPE 1 message which includes the IE "BCCH Modification Information".

8.1.1.5.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_PCH state (state 6-12) as specified in clause 7.4 of TS 34.108 with valid a U-RNTI assigned to it.

Test Procedure

The SS transmits a PAGING TYPE 1 message on the paging occasions assigned to the UE. The PAGING TYPE 1 message shall include the IE "BCCH Modification Information" indicating value tag of the modified master information block. Then it transmits the new master information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis message. In the new SIB TYPE 5 / SIB TYPE 5bis message, the IE "Available Signature" for FDD, "Available Channelisation codes indices " for TDD 3.84 Mcps and 7.68 Mcps options or "Available SYNC_UL codes indices " for TDD 1.28 Mcps option is different when compared to the original SIB TYPE 5 / SIB TYPE 5bis message. At the paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses the UE using its U-RNTI. The UE shall respond with a CELL UPDATE message and set IE "cell update cause" to "paging response". The SS shall transmit a CELL UPDATE CONFIRM message.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Void
2			PAGING TYPE 1	SS transmits the paging message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block.
2a			Void
3	 		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "Available Signature" is changed from "0000 0000 1111 1111(B)" to "1111 1111 0000 0000(B)". For TDD 3.84 Mcps and 7.68 Mcps options, at the same time, SS starts to transmit the affected SIB TYPE 6 continuously. The value of IE "Available Channelisation codes indices " is changed according to test purposes. For TDD 1.28 Mcps option, at the same time, SS starts to transmit the affected SIB TYPE 6 continuously. The value of IE "Available SYNC_UL codes indices " is changed according to test purposes.
3a				SS waits 5s (to ensure that the UE has time to read the new system information)
4			PAGING TYPE 1	SS transmits this message continuously on the PCCH at the correct paging occasion.
5			CELL UPDATE
6			CELL UPDATE CONFIRM	See message content.

Specific Message Contents

PAGING TYPE 1 (Step 2)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 3)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 2
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

SYSTEM INFORMATION BLOCK TYPE 5/ SYSTEM INFORMATION BLOCK TYPE 5bis. (Step 3)(FDD)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	FDD
– Available Signature	‘1111 1111 0000 0000’B

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 3.84 Mcps option)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps option
– Available Channelisation codes indices	To be defined (each bit indicates availability of a channelization code index)

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 1.28 Mcps option)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps option
– Available SYNC_UL codes indices	To be defined (each bit indicates availability of a SYNC_UL code index)

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 7.68 Mcps option)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps option
– Available Channelisation codes indices	To be defined (each bit indicates availability of a channelization code index)

PAGING TYPE 1 (Step 4)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI	Equal to the U-RNTI assigned earlier.
– SRNC Identity
– S-RNTI
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

CELL UPDATE (Step 5)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
U-RNTI	Checked to see if it is set to the same values as in step 4
– SRNC identity
– S-RNTI
Cell update cause	Paging response

CELL UPDATE CONFIRM (Step 6)

Use the same message type found in (TS 34.108) Clause 9, with the following exception:

Information Element	Value/remark
RRC State indicator	CELL_PCH
UTRAN DRX cycle length coefficient	3

8.1.1.5.5 Test requirement

After step 4 the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response", using an allowed signature according to modified IE "Available signature"(FDD) )/ " Available SYNC_UL codes indices "(1.28 Mcps TDD)/ "Available Channelisation codes indices " (3.84 Mcps and 7.68 Mcps TDD) in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

8.1.1.5a Paging on HS-DSCH for notification of BCCH modification in CELL_PCH

8.1.1.5a.1 Definition and applicability

All UEs which support FDD and HS-PDSCH in CELL_PCH and URA_PCH.

8.1.1.5a.2 Conformance requirement

Upon modifications of system information blocks using value tags, UTRAN should notify the new value tag for the master information block in the IE "BCCH modification info", transmitted in the following way:

1> to reach UEs in idle mode, and in CELL_PCH state and URA_PCH state with S-CCPCH assigned, the IE "BCCH modification info" is contained in a PAGING TYPE 1 message transmitted on the PCCH in all paging occasions in the cell;

1> to reach UEs in CELL_PCH state and URA_PCH state with HS-DSCH assigned and no dedicated H-RNTI assigned, the IE "BCCH modification info" is contained in a PAGING TYPE 1 message transmitted on the PCCH in all paging occasions in the cell;

…

Upon reception of a PAGING TYPE 1 message or a SYSTEM INFORMATION CHANGE INDICATION message containing the IE "BCCH modification info" containing the IE "MIB value tag" but not containing the IE "BCCH modification time", the UE shall perform actions as specified in subclause 8.1.1.7.3.

…

The UE shall:

1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG.

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in subclause 8.1.1.5.

…

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

If the UE is in idle mode, for each occurrence of the IE "Paging record" included in the message the UE shall:

1> if the IE "Used paging identity" is a CN identity:

2> compare the IE "UE identity" with all of its allocated CN UE identities:

2> if one match is found:

…

Reference

3GPP TS 25.331 clause 8.1.1.7, 8.1.1.7.1, 8.1.2.3

8.1.1.5a.3 Test purpose

To confirm that the UE, in addition to any actions caused by the IE "Paging record" occurrences in PAGING TYPE 1 mapped on HS-DSCH, checks the new value tag of the master information block, and reads the SYSTEM INFORMATION messages mapped on HS-DSCH after it receives a PAGING TYPE 1 message on HSDSCH which includes the IE "BCCH Modification Information".

8.1.1.5a.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_PCH (state 6-12) as specified in clause 7.4 of TS 34.108 with valid a U-RNTI but no dedicated H-RNTI assigned to it. HS-DSCH reception in CELL_PCH and URA_PCH is enabled by including the parameters for HS-DSCH reception in CELL_PCH and URA_PCH state in default SIB5, condition B1, TS 34.108, section 6.1.0b.

Test Procedure

The SS transmits a PAGING TYPE 1 message with PCCH mapped onto HS-DSCH on the paging occasions assigned to the UE. The PAGING TYPE 1 message shall include the IE "BCCH Modification Information" indicating value tag of the modified master information block. Then it transmits the new master information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis message. In the new SIB TYPE 5 / SIB TYPE 5bis message, the IE "Available Signature" for FDD is different when compared to the original SIB TYPE 5 / SIB TYPE 5bis message. At the paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses the UE using its U-RNTI. The UE shall respond with a CELL UPDATE message and set IE "cell update cause" to "paging response". The SS shall transmit a CELL UPDATE CONFIRM message.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			PAGING TYPE 1	SS transmits the paging message which comprises IE "BCCH Modification Information" on HS-DSCH, with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block.
2	 		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "Available Signature" is changed from "0000 0000 1111 1111(B)" to "1111 1111 0000 0000(B)".
3				SS waits 5s (to ensure that the UE has time to read the new system information)
4			PAGING TYPE 1	SS transmits this message continuously on the PCCH at the correct paging occasion.
5			CELL UPDATE
6			CELL UPDATE CONFIRM	See message content.

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 2)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 1
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

SYSTEM INFORMATION BLOCK TYPE 5/ SYSTEM INFORMATION BLOCK TYPE 5bis. (Step 3)(FDD)

Use the same message type found in clause 6.1.0b, condition B1, of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	FDD
– Available Signature	‘1111 1111 0000 0000’B

PAGING TYPE 1 (Step 4)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI	Equal to the U-RNTI assigned earlier.
– SRNC Identity
– S-RNTI
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

CELL UPDATE (Step 5)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
U-RNTI	Checked to see if it is set to the same values as in step 4
– SRNC identity
– S-RNTI
Cell update cause	Paging response
HS-DSCH in CELL_FACH	Check to see if set to TRUE

CELL UPDATE CONFIRM (Step 6)

Use the same message type found in (TS 34.108) Clause 9, with the following exception:

Information Element	Value/remark
RRC State indicator	CELL_PCH
UTRAN DRX cycle length coefficient	3

8.1.1.5a.5 Test requirement

After step 5 the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response" and “HS-PDSCH in CELL_FACH” set to TRUE, using an allowed signature according to modified IE "Available signature"(FDD) in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis

8.1.1.5b Paging on HS-DSCH for notification of BCCH modification in CELL_PCH (1.28Mcps TDD)

8.1.1.5b.1 Definition and applicability

All UEs which support 1.28Mcps TDD and E-DCH and HS-PDSCH in CELL_PCH and URA_PCH.

8.1.1.5b.2 Conformance requirement

1> to reach UEs in CELL_FACH state or TDD UEs in CELL_DCH with S-CCPCH assigned, the IE "BCCH modification info" is contained in a SYSTEM INFORMATION CHANGE INDICATION message transmitted on the BCCH mapped on at least one FACH on every Secondary CCPCH in the cell;

1> for FDD and 1.28 Mcps TDD, to reach UEs in CELL_FACH state with HS-DSCH assigned and in CELL_PCH with HS-DSCH and dedicated H-RNTI assigned, the IE "BCCH modification info" is contained in a SYSTEM INFORMATION CHANGE INDICATION message transmitted on the BCCH mapped on the HS-PDSCH indicated with the first indexed HS-SCCH code by the BCCH specific H-RNTI.

If the IE "BCCH modification time" is included the UE shall perform actions as specified in subclause 8.1.1.7.2.

…

The UE shall:

1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG.

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in subclause 8.1.1.5.

…

A UE in idle mode, CELL_PCH state or URA_PCH state shall receive the paging information for all its monitored paging occasions. For a UE in idle mode, the paging occasions are specified in [4] and depend on the IE "CN domain specific DRX cycle length coefficient", as specified in subclause 8.6.3.1a. For a UE in CELL_PCH state or URA_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE "RRC State Indicator", as specified in subclauses 8.6.3.2 and 8.6.3.3 respectively.

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

If the UE is in idle mode, for each occurrence of the IE "Paging record" included in the message the UE shall:

1> if the IE "Used paging identity" is a CN identity:

2> compare the IE "UE identity" with all of its allocated CN UE identities:

2> if one match is found:

3> indicate reception of paging; and

3> forward the IE "CN domain identity", the IE "UE identity" and the IE "Paging cause" to the upper layers.

1> otherwise:

ignore that paging record.

…

If the IE "BCCH modification info" is included, any UE in idle mode, CELL_PCH or URA_PCH state shall perform the actions as specified in subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message as specified above.

…

Reference

3GPP TS 25.331 clause 8.1.1.7.1, 8.1.1.7.3, 8.1.2.3

8.1.1.5b.3 Test purpose

8.1.1.5b.4 Method of test

Initial Condition

System Simulator: 1 cell.

Test Procedure

The SS transmits a PAGING TYPE 1 message with PCCH mapped onto HS-DSCH on the paging occasions assigned to the UE. The PAGING TYPE 1 message shall include the IE "BCCH Modification Information" indicating value tag of the modified master information block. Then it transmits the new master information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis message. In the new SIB TYPE 5 / SIB TYPE 5bis message, the IE " SYNC_UL codes bitmap " for "E-RUCCH Info" is different when compared to the original SIB TYPE 5 / SIB TYPE 5bis message. At the paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses the UE using its U-RNTI. The UE shall respond with a CELL UPDATE message on common E-DCH and set IE "cell update cause" to "paging response". The SS shall transmit a CELL UPDATE CONFIRM message.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			PAGING TYPE 1	SS transmits the paging message which comprises IE "BCCH Modification Information" on HS-DSCH, with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block.
2	 		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE " SYNC_UL codes bitmap " for "E-RUCCH Info" is changed from "00001111" to "11110000". The value of IE " SYNC_UL codes bitmap " for " PRACH info " is changed from "11110000" to "00001111".
3				SS waits 5s (to ensure that the UE has time to read the new system information)
4			PAGING TYPE 1	SS transmits this message continuously on the PCCH at the correct paging occasion.
5			CELL UPDATE
6			CELL UPDATE CONFIRM	See message content.

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 2)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 1
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

SYSTEM INFORMATION BLOCK TYPE 5/ SYSTEM INFORMATION BLOCK TYPE 5bis. (Step 2)( 1.28Mcps TDD)

Use the same message type found in clause 6.1.0b, condition B1, of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps TDD
– SYNC_UL info
– SYNC_UL codes bitmap	"00001111"
CommonEDCHSystemInfo
-CHOICE Mode
– CHOICE TDD option	1.28 Mcps TDD
– prach-PreambleForEnhancedUplink
– E-RUCCH Info
– SYNC_UL info
– SYNC_UL codes bitmap	"11110000"

PAGING TYPE 1 (Step 4)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI	Equal to the U-RNTI assigned earlier.
– SRNC Identity
– S-RNTI
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

CELL UPDATE (Step 5)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
U-RNTI	Checked to see if it is set to the same values as in step 4
– SRNC identity
– S-RNTI
Cell update cause	Paging response
HS-PDSCH in CELL_FACH	Check to see if set to TRUE
Support of common E-DCH	Check to see if set to TRUE

CELL UPDATE CONFIRM (Step 6)

Use the same message type found in (TS 34.108) Clause 9, with the following exception:

Information Element	Value/remark
RRC State indicator	CELL_PCH
UTRAN DRX cycle length coefficient	3

8.1.1.5b.5 Test requirement

After step 5 the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response" and “HS-PDSCH in CELL_FACH” and “Support of common E-DCH” set to TRUE, using common E-DCH in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis

8.1.1.6 Paging for notification of BCCH modification in connected mode (URA_PCH)

8.1.1.6.1 Definition

8.1.1.6.2 Conformance requirement

A UE in URA_PCH state shall receive the paging information for all its monitored paging occasions. For a UE in URA_PCH state, the paging occasions depend also on the IE "UTRAN DRX cycle length coefficient" and the IE "RRC State Indicator", as specified in TS 25.331 subclauses 8.6.3.2 and 8.6.3.3 respectively.

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

…

If the IE "BCCH modification info" is included, any UE in URA_PCH state shall perform the actions as specified in TS 25.331 subclause 8.1.1 in addition to any actions caused by the IE "Paging record" occurrences in the message as specified above.

The UE shall:

1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG.

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in subclause 8.1.1.5.

…

Upon reception of the master information block, the UE shall:

1> compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG;

1> if the value tags differ:

2> store the value tag into the variable VALUE_TAG for the master information block;

2> read and store scheduling information included in the master information block.

….

For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE shall perform the following actions:

1> for all system information blocks with area scope "PLMN" or "Equivalent PLMN" that use value tags:

2> compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TAG for that system information block;

2> if the value tags differ:

3> store the value tag read in scheduling information for that system information block into the variable VALUE_TAG;

3> read and store the IEs of that system information block.

…

Reference

3GPP TS 25.331 clause 8.1.1, 8.1.2.

8.1.1.6.3 Test purpose

To confirm that the UE checks the included new value tag of the master information block and reads the relevant SYSTEM INFORMATION block(s) after it receives a PAGING TYPE 1 message which includes the IE "BCCH Modification Information".

8.1.1.6.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: URA_PCH state (state 6-13) as specified in clause 7.4 of TS 34.108 with a valid U-RNTI assigned.

Test Procedure

The SS transmits a PAGING TYPE 1 message on the paging occasions assigned to the UE. The message shall include the IE "BCCH Modification Information" indicating the value tag of the master information block. Then it transmits the new master information block followed by the new SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. message. In the new SIB TYPE 5 /SIB TYPE 5bis message, the IE "Available Signature" for FDD, "Available Channelisation codes indices" for TDD 3.84 Mcps and 7.68 Mcps options or "Available SYNC_UL codes indices" for TDD 1.28 Mcps option is different when compared to the original SIB TYPE 5 /SIB TYPE 5bis message. At the next paging occasion, SS transmits a new PAGING TYPE 1 message. This message addresses the UE using its U-RNTI and the "paging cause" IE set to a terminating call type that is supported by the UE. The UE shall respond with a CELL UPDATE message and set IE "cell update cause" to "paging response". The SS shall transmit a CELL UPDATE CONFIRM message.

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS
1			Void
2			PAGING TYPE 1	SS transmits the paging message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block.
2a			Void
3	 		MASTER INFORMATION BLOCK SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5 / SIB TYPE 5bis message continuously. The value of IE "Available Signature" is changed from "0000 0000 1111 1111(B)" to "1111 1111 0000 0000(B)". For TDD 3.84 Mcps and 7.68 Mcps options, at the same time, SS starts to transmit the affected SIB TYPE 6 continuously. The value of IE "Available Channelisation codes indices" is changed according to test purposes. For TDD 1.28 Mcps option, at the same time, SS starts to transmit the affected SIB TYPE 6 continuously. The value of IE "Available SYNC_UL codes indices" is changed according to test purposes.
3a				SS waits 5s (to ensure that the UE has time to read the new system information)
4			PAGING TYPE 1	SS transmits this message continuously on the PCCH at the correct occasion.
5			CELL UPDATE
6			CELL UPDATE CONFIRM	See message content.

Specific Message Contents

PAGING TYPE 1 (Step 2)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
– MIB Value Tag	Set to (Current MIB value tag + 1)
– BCCH Modification time	Not Present

MASTER INFORMATION BLOCK (Step 3)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 2
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. (Step 3)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	FDD
– Available Signature	‘1111 1111 0000 0000’B

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 3.84 Mcps option)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	3.84 Mcps option
– Available Channelisation codes indices	To be defined (each bit indicates availability of a channelization code index)

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 1.28 Mcps option)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	1.28 Mcps option
– Available SYNC_UL codes indices	To be defined (each bit indicates availability of a SYNC_UL code index)

SYSTEM INFORMATION BLOCK TYPE 5 (Step 3) (TDD 7.68 Mcps option)

Use the same message type found in clause 6.1 of TS 34.108, with the following exception.

Information Element	Value/remark
– PRACH system information
– PRACH info
– CHOICE mode	TDD
– CHOICE TDD option	7.68 Mcps option
– Available Channelisation codes indices	To be defined (each bit indicates availability of a channelization code index)

PAGING TYPE 1 (Step 4)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	UTRAN identity
– U-RNTI	Equal to the U-RNTI assigned earlier.
– SRNC Identity
– S-RNTI
– CN originated page to connected mode UE	Not Present
BCCH modification info	Not Present

CELL UPDATE (Step 5)

Check to see if the same message type found in TS 34.108, clause 9 is received, with the following exceptions:

Information Element	Value/remark
U-RNTI	Checked to see if it is set to the same values as in step 4
– SRNC identity
– S-RNTI
Cell update cause	Paging response

CELL UPDATE CONFIRM (Step 6)

Use the same message type found in TS 34.108, clause 9 with the following exceptions.

Information Element	Value/Remarks
RRC State indicator	URA_PCH
UTRAN DRX cycle length coefficient	3

8.1.1.6.5 Test requirement

After step 4, the UE shall transmit a CELL UPDATE message with IE "cell update cause" set to "paging response", using an allowed signature according to modified IE "Available signature"(FDD) )/ "Available SYNC_UL codes indices" (1.28 Mcps TDD) / "Available Channelisation codes indices " (3.84 Mcps and 7.68 Mcps TDD) in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

8.1.1.6a Paging for notification of synchronised BCCH modification in idle mode using BCCH modification time

8.1.1.6a.1 Definition

8.1.1.6a.2 Conformance requirement

For modification of some system information elements, e.g. reconfiguration of the channels, it is important for the UE to know exactly when a change occurs. In such cases, the UTRAN should notify the SFN when the change will occur as well as the new value tag for the master information block in the IE "BCCH modification info"

When the UE receives a PAGING TYPE 1 message, it shall perform the actions as specified below.

…

Upon reception of a PAGING TYPE 1 message or a SYSTEM INFORMATION CHANGE INDICATION message containing the IE "BCCH modification info" containing the IE "MIB value tag" and containing the IE "BCCH modification time", the UE shall:

1> perform the actions as specified in TS 25.331 subclause 8.1.1.7.3 at the time, indicated in the IE "BCCH Modification Info".

…

The UE shall:

1> compare the value of IE "MIB value tag" in the IE "BCCH modification info" with the value tag stored for the master information block in variable VALUE_TAG.

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in TS 25.331 subclause 8.1.1.5.

…

Upon reception of the master information block, the UE shall:

1> compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG;

1> if the value tags differ:

2> store the value tag into the variable VALUE_TAG for the master information block;

2> read and store scheduling information included in the master information block.

….

For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE shall perform the following actions:

1> for all system information blocks with area scope "PLMN" that use value tags:

2> compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TAG for that system information block;

2> if the value tags differ:

3> store the value tag read in scheduling information for that system information block into the variable VALUE_TAG;

3> read and store the IEs of that system information block.

…

Reference

3GPP TS 25.331 clause 8.1.1, 8.1.2.

8.1.1.6a.3 Test purpose

To confirm that the UE checks the new value tag of the master information block and reads the updated SYSTEM INFORMATION BLOCK messages exactly when a change occurs at "BCCH modification time".

8.1.1.6a.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: Idle state (state 2 or state 3 or state 7) as specified in clause 7.4 of TS 34.108 with a CN UE identity, depending on the CN domain(s) supported by the UE.

Test Procedure

Expected sequence

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1			PAGING TYPE 1	SS starts to transmit this message on the PCCH at the correct paging occasion.
2			RRC CONNECTION REQUEST
3			RRC CONNECTION REJECT
4			PAGING TYPE 1	SS transmits the message including the IE "BCCH Modification Information", with the MIB "Value Tag" different from the "MIB Value Tag" of the current Master Information Block and “BCCH Modification time”.
5				Before “BCCH Modification time” SS changes S-CCPCH configuration from TS 34.108 Clause 6.1.0.b Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH in One SCCPCH to TS 34.108 Clause 6.1.1 SCCPCH configuration with Stand-alone SRB for PCCH in the first SCCPCH and Interactive/Background 32 kbps PS RAB + SRBs for CCCH/DCCH/BCCH in the second SCCPCH.
6			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting before BCCH Modification time.
6			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	At the same time, SS starts to transmit the new SIB TYPE 5 / SIB TYPE 5bis messages continuously. The SIB TYPE 5 / SIB TYPE 5 bis messages are changed from TS 34.108 Clause 6.1.0.b to TS 34.108 Clause 6.1.1.
7			PAGING TYPE 1	SS starts to transmit this message continuously on the PCCH using the new SCCPCH configuration broadcast in NEW SIB TYPE 5 / SIB TYPE 5 bis before the SFN of BCCH Modification Time -1000. SS checks to see UE transmits no RRC CONNECTION REQUEST before the SFN of BCCH Modification Time
8				SS waits 500 SFN after SFN of BCCH Modification Time (to ensure that the UE has time to read the new system information)
9			PAGING TYPE 1	SS starts to transmit this message continuously on the PCCH using the new SCCPCH configuration broadcast in NEW SIB TYPE 5 / SIB TYPE 5 bis at the correct paging occasion.
10			RRC CONNECTION REQUEST
11			RRC CONNECTION REJECT

Specific Message Contents

PAGING TYPE 1 (Step 1)

Information Element	Value/remark
Message Type
Paging record list	Only 1 entry
Paging record
– CHOICE Used paging identity	CN identity
– Paging Cause	Terminating Call with one of the supported services
– CN Domain Identity	Supported Domain (PS Domain or CS Domain)
– CHOICE UE Identity	Local (P)TMSI
– Routing parameter	Same as registered TMSI or P-TMSI
BCCH modification info	Not Present

Use the same SCCPCH in TS 34.108 clause 6.1.0b.

RRC CONNECTION REJECT (Step 3 and 11)

Use the same message type found in [9] TS 34.108 clause 9.

PAGING TYPE 1 (Step 4)

Information Element	Value/remark
Message Type
Paging record list	Not Present
BCCH modification info
MIB Value Tag	Set to (Current MIB value tag + 1)
BCCH Modification time	Set to (Current SFN +4088) MOD4096

Use the same SCCPCH configuration in TS 34.108 clause 6.1.0b.

MASTER INFORMATION BLOCK (Step 6)

Information Element	Value/remark
MIB Value tag	As in PAGING TYPE 1 in step 4
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis (Step 6) (FDD) (3.84 Mcps TDD) (1.28 Mcps TDD)

Use the same message type found in clause 6.1.1 of TS 34.108

PAGING TYPE 1 (Steps 7 & 9)

Use the same message as defined for Step 1.

Use the same SCCPCH configuration in TS 34.108 clause 6.1.1.

8.1.1.6a.5 Test requirement

After step 1 the UE shall transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1 messages sent in step 1, using an allowed SCCPCH configuration in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

After step 6 UE shall not try to receive MIB whose value tag is same as IE "BCCH modification info" in PAGING TYPE 1 continuously.

After step 7 UE shall not transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1 messages sent in step 7

After step 9 the UE shall transmit RRC CONNECTION REQUEST messages in response to the PAGING TYPE 1 messages sent in step 9, using an allowed SCCPCH configuration in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

8.1.1.7 Paging for Connection in connected mode (CELL_DCH)

8.1.1.7.1 Definition

8.1.1.7.2 Conformance requirement

When the UE receives a PAGING TYPE 2 message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere.

The UE shall:

1> indicate reception of paging; and

1> forward the IE "Paging cause" and the IE "Paging record type identifier" to upper layers.

…

….

The UE shall, in the INITIAL DIRECT TRANSFER message:

1> set the IE "NAS message" as received from upper layers; and

1> set the IE "CN domain identity" as indicated by the upper layers; and

1> set the IE "Intra Domain NAS Node Selector" as follows:

2> derive the IE "Intra Domain NAS Node Selector" from TMSI/PMTSI, IMSI, or IMEI; and

2> provide the coding of the IE "Intra Domain NAS Node Selector" according to the following priorities:

1. derive the routing parameter for IDNNS from TMSI (CS domain) or PTMSI (PS domain) whenever a valid TMSI/PTMSI is available;

2. base the routing parameter for IDNNS on IMSI when no valid TMSI/PTMSI is available;

3. base the routing parameter for IDNNS on IMEI only if no (U)SIM is inserted in the UE.

…

The UE shall:

1> transmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3;

1> when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission:

2> confirm the establishment of a signalling connection to upper layers; and

2> add the signalling connection with the identity indicated by the IE "CN domain identity" in the variable ESTABLISHED_SIGNALLING_CONNECTIONS.

1> when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC:

2> the procedure ends.

If the UE receives an RRC message on the DCCH, or addressed to the UE on the CCCH or on the SHCCH, or sent via a radio access technology other than UTRAN, with a mandatory IE having a value, including choice, reserved for future extension (spare) or a value not used in this version of the specification (e.g. a dummy value), the UE shall:

1> if a default value of the IE is defined:

2> treat the rest of the message using the default value of the IE.

1> if no default value of the IE is defined:

2> set the variable PROTOCOL_ERROR_REJECT to TRUE;

2> set the IE "Protocol error cause" in the variable PROTOCOL_ERROR_INFORMATION to "Information element value not comprehended";

2> perform procedure specific error handling according to clause 8.

Reference

3GPP TS 25.331 clause 8.1.8.2, 8.1.11.3, 9.4.

8.1.1.7.3 Test purpose

To confirm that the UE responds to a PAGING TYPE 2 message which includes the IE "Paging Cause" and the IE "Paging Record Type Identifier".

To confirm that the UE responds with a RRC STATUS message after it has received an invalid PAGING TYPE 2 message.

To Page with the Paging Record Type Identifier set to "IMSI", in order to test the UEs behaviour to this situation which may occur when details of the temporary identity have been lost in the core network.

8.1.1.7.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_DCH state (state 6-9 or state 6-10) as specified in clause 7.4 of TS 34.108 after executing a location registration and/or attach procedure. The UE has been registered in both CS and PS domains.

Test Procedure

The SS transmits an invalid PAGING TYPE 2 message. UE shall respond by transmitting a RRC STATUS message on the uplink DCCH using RLC-AM mode. Finally, SS transmits a PAGING TYPE 2 message, which includes a matched Paging Record Type Identifier. In the CS domain the UE shall respond to this message by the transmission of an INITIAL DIRECT TRANSFER message. In the PS Domain the UE will locally detach and then initiate a GPRS attach procedure (as per clause 4.7.9.1.2 of TS 24.008) also involving the transmission of an INITIAL DIRECT TRANSFER message.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Void
2			PAGING TYPE 2	SS pages UE from a new CN domain, see specific message contents.
3			RRC STATUS	The UE shall respond by reporting the protocol error to the SS.
4			PAGING TYPE 2	SS pages the UE with a matched identifier and with a valid "paging cause" IE from a new CN Domain.
5			INITIAL DIRECT TRANSFER	The UE shall respond to the paging message sent in step 4.

Specific Message Contents

PAGING TYPE 2 (Step 2)

SS sends a message containing a protocol error causing the UE to perform procedure specific error handling.

Use the same message type found in clause 9 of TS 34.108, with the following exceptions.

Information Element	Value/remark
Paging Cause	Set to value "Spare"
CN Domain Identity	Set to a new CN Domain
Paging Record Type Identifier	Set to "IMSI (GSM-MAP)" for UEs supporting GSM-MAP core network type or "IMSI (DS-41)" for UEs supporting ANSI-41 core network type.

RRC STATUS (Step 3)

Use the same message type found in TS 34.108, clause 9, with the following exception.

Information Element	Value/remark
Identification of received message
– Received message type	PAGING TYPE 2
– RRC transaction identifier	Checked to see if the value is identical to the same IE in the PAGING TYPE 2 message.
Protocol error information
– Protocol Error Cause	Information element value not comprehended

PAGING TYPE 2 (Step 4)

Use the same message type found in TS 34.108, clause 9, with the following exception.

Information Element	Value/remark
Paging cause	Terminating Call supported by the UE in the new domain
CN domain identity	New Domain supported by the UE
Paging record type identifier	Set to "IMSI (GSM-MAP)" for UEs supporting GSM-MAP core network type or "IMSI (DS-41)" for UEs supporting ANSI-41 core network type.

INITIAL DIRECT TRANSFER (Step 5) – for UEs supporting GSM-MAP core networks

Check to see if the same message type found in TS 34.108 clause 9 is received, with the following exceptions:

Information Element	Value/remark
CN domain identity	CS domain or PS domain as specified in the PAGING TYPE 2 message in Step 4.
Intra Domain NAS Node Selector
– CHOICE version	R99
— CHOICE CN type	GSM
— CHOICE Routing basis	local (P)TMSI – if CS Domain IMSI (cause UE initiated event) or IMSI (response to IMSI paging) – if PS Domain
—- Routing parameter	If the IE "CN domain identity" is equal to "CS domain": The TMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/ leftmost/ most significant bit of the bit string contains bit b23 of the TMSI/ PTMSI. If the IE "CN domain identity" is equal to "PS domain": The "Routing parameter" bit string consists of DecimalToBinary [(IMSI div 10) mod 1000]. The first/ leftmost bit of the bit string contains the most significant bit of the result.
— Entered parameter	Not checked
NAS message	Not checked

INITIAL DIRECT TRANSFER (Step 5) – for UEs supporting ANSI-41 core networks

Information Element	Value/remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
CN domain identity	CS domain or PS domain as specified in the PAGING TYPE 2 message in Step 4.
Intra Domain NAS Node Selector
– CHOICE version	ANSI-41 : Bitstring(14), all bits set to 0
NAS message	Not checked
START	Not checked
Measured results on RACH	Not checked

8.1.1.7.5 Test requirement

After step 2 the UE shall respond to the paging message by transmitting RRC STATUS on the DCCH, stating the protocol error as "Information element value not comprehended ".

After step 4 the UE shall respond to the paging message by transmitting an INITIAL DIRECT TRANSFER message on the uplink DCCH.

8.1.1.8 Paging for Connection in connected mode (CELL_FACH)

8.1.1.8.1 Definition

8.1.1.8.2 Conformance requirement

When the UE receives a PAGING TYPE 2 message, it shall not affect the state of any other ongoing RRC procedures, when not stated otherwise elsewhere.

The UE shall:

1> indicate reception of paging; and

1> forward the IE "Paging cause" and the IE "Paging record type identifier" to upper layers.

…

The UE shall, in the INITIAL DIRECT TRANSFER message:

…

In CELL_FACH state, the UE shall:

1> include in the IE "Measured results on RACH" all requested reporting quantities for cells for which measurements are reported.

The UE shall:

1> transmit the INITIAL DIRECT TRANSFER message on the uplink DCCH using AM RLC on signalling radio bearer RB3;

1> when the INITIAL DIRECT TRANSFER message has been submitted to lower layers for transmission:

2> confirm the establishment of a signalling connection to upper layers; and

2> add the signalling connection with the identity indicated by the IE "CN domain identity" in the variable ESTABLISHED_SIGNALLING_CONNECTIONS.

1> when the successful delivery of the INITIAL DIRECT TRANSFER message has been confirmed by RLC:

2> the procedure ends.

Reference

3GPP TS 25.331 clause 8.1.8.2, 8.1.11.

8.1.1.8.3 Test purpose

To confirm that the UE responds to a PAGING TYPE 2 message, which includes a matching value for IE "Paging Record Type Identifier".

8.1.1.8.4 Method of test

Initial Condition

System Simulator: 1 cell.

UE: CELL_FACH state (state 6-11) as specified in clause 7.4 of TS 34.108. The UE has been registered in both CS and PS domains.

Test Procedure

The SS transmits a PAGING TYPE 2 message. Then the UE shall respond by transmitting an upper layer message to answer this page.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1			Void
2			PAGING TYPE 2	The SS transmits the message includes a matched identifier.
3			INITIAL DIRECT TRANSFER	The UE responds by sending an upper layer message.

Specific Message Content

PAGING TYPE 2 (Step 2)

Use the same message type found in [9] (TS 34.108) Clause 9, with the following exception.

Information Element	Value/remark
Paging cause	Terminating Call supported by the UE
CN domain identity	CS
Paging record type identifier	Set to "TMSI (GSM-MAP)/P-TMSI" for UEs supporting GSM-MAP core network type or "TMSI (DS-41)" for UEs supporting ANSI-41 core network type.

INITIAL DIRECT TRANSFER (Step 3) – for UEs supporting GSM-MAP core networks

Only the message type IE for this message is checked.

Information Element	Value/remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
CN domain identity	CS domain
Intra Domain NAS Node Selector
– CHOICE version	R99
— CHOICE CN type	GSM
— CHOICE Routing basis	Local (P)TMSI
—- Routing parameter	The TMSI/P-TMSI consists of 4 octets (32bits). This can be represented by a string of bits numbered from b0 to b31, with bit b0 being the least significant. The "Routing parameter" bit string consists of bits b14 through b23 of the TMSI/ PTMSI. The first/ leftmost/ most significant bit of the bit string contains bit b23 of the TMSI/ PTMSI.
— Entered parameter	Not checked
NAS message	Not checked
START	Not checked
Measured results on RACH	Not checked

INITIAL DIRECT TRANSFER (Step 3) – for UEs supporting ANSI-41 core networks

Information Element	Value/remark
Message Type
Integrity check info
– Message authentication code	This IE is checked to see if it is present. The value is compared against the XMAC-I value computed by SS. The first/ leftmost bit of the bit string contains the most significant bit of the MAC-I.
– RRC Message sequence number	This IE is checked to see if it is present. The value is used by SS to compute the XMAC-I value.
CN domain identity	CS domain
Intra Domain NAS Node Selector
– CHOICE version	ANSI-41 : Bitstring(14), all bits set to 0
NAS message	Not checked
START	Not checked
Measured results on RACH	Not checked

8.1.1.8.5 Test requirement

After step 2 the UE shall respond to the PAGING TYPE 2 message by transmitting an INITIAL DIRECT TRANSFER message on the uplink DCCH.

8.1.1.9 Paging for Connection in idle mode (multiple paging records)

8.1.1.9.1 Definition

8.1.1.9.2 Conformance requirement