8.1.1 Broadcast of system information

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

Figure 8.1.1-1: Broadcast of system information

Figure 8.1.1-1a: Broadcast of system information with system information broadcast channel (BCH on PCCPCH) and second system information broadcast channel (BCH on SCCPCH)

Figure 8.1.1-2: Notification of system information modification for UEs in idle mode,
CELL_PCH state and URA_PCH state

Figure 8.1.1-3: Notification of system information modification for UEs in CELL_FACH and CELL_DCH (TDD only) state

Figure 8.1.1-4: Reception of System Information Container

8.1.1.1 General

The purpose of this procedure is to broadcast system information from the UTRAN to UEs in a cell.

8.1.1.1.1 System information structure

The system information elements are broadcast in system information blocks. A system information block groups together system information elements of the same nature. Different system information blocks may have different characteristics, e.g. regarding their repetition rate and the requirements on UEs to re-read the system information blocks.

The system information is organised as a tree. A master information block gives references and scheduling information to a number of system information blocks in a cell. The system information blocks contain the actual system information. The master information block may optionally also contain reference and scheduling information to one, two or three scheduling blocks, which give references and scheduling information for additional system information blocks. Scheduling information for a system information block may only be included in either the master information block or one of the scheduling blocks.

For all system information blocks except System Information Block types 15.2, 15.3 and 16, the content is the same in each occurrence for system information blocks using value tag. System Information Block types 15.2, 15.3 and 16 may occur more than once with different content. In this case scheduling information is provided for each such occurrence of the system information block. System information blocks that do not use value tag may have different content for each occurrence.

8.1.1.1.2 System information blocks

Table 8.1.1 specifies all system information blocks and their characteristics.

The area scope column in table 8.1.1 specifies the area where a system information block’s value tag is valid. If the area scope is cell, the UE shall consider the system information block to be valid only in the cell in which it was read. If system information blocks have been previously stored for this cell, the UE shall check whether the value tag for the system information block in the entered cell is different compared to the stored value tag. If the area scope is PLMN or Equivalent PLMN, the UE shall check the value tag for the system information block when a new cell is selected. If the value tag for the system information block in the new cell is different compared to the value tag for the system information block stored in the UE, the UE shall re-read the system information block. If the area scope is PLMN, the UE shall consider the system information block to be valid only within the PLMN in which it was read. If the area scope is Equivalent PLMN, the UE shall consider the system information block to be valid within the PLMN in which it was received and all PLMNs which are indicated by higher layers to be equivalent.

For System information block types 15.2, 15.2bis, 15.2ter, 15.3, 15.3bis and 16, which may have multiple occurrences, each occurrence has its own independent value tag. The UE- shall re-read a particular occurrence if the value tag of this occurrence has changed compared to that stored in the UE.

The UE mode/state column when block is valid in Table 8.1.1 specifies in which UE mode or UE state the IEs in a system information block shall be regarded as valid by the UE. In other words, the indicated system information block becomes invalid upon change to a mode/state that is not included in this column. System Information Block Type 16 remains also valid upon transition to or from GSM/GPRS. In some cases, the states are inserted in brackets to indicate that the validity is dependent on the broadcast of the associated System Information Blocks by the network as explained in the relevant procedure subclause.

The UE mode/state column when block is read in Table 8.1.1 specifies in which UE mode or UE state the IEs in a system information block may be read by the UE. The UE shall have the necessary information prior to execution of any procedure requiring information to be obtained from the appropriate system information block. The requirements on the UE in terms of when to read the system information may therefore be derived from the procedure specifications that specify which IEs are required in the different UE modes/states in conjunction with the different performance requirements that are specified.

The UE shall:

1> if variable DEFERRED_MEASUREMENT_STATUS is set to FALSE:

2> if System Information Block type 11 is referenced in the master information block or in the scheduling blocks:

3> if System Information Block type 12 is not referenced in the master information block or in the scheduling blocks , or broadcast of System Information Block type 12 is not indicated in System Information Block type 11:

4> have read and acted upon System Information Block type 11, System Information Block type 11bis and System Information Block type 11ter, if scheduled on BCH, in a cell when the UE transmits an RRC message on RACH.

3> else:

4> have read and acted upon System Information Block type 11, System Information Block type 11bis and System Information Block type 11ter, if scheduled on BCH, in a cell before the UE transmits the RRC CONNECTION REQUEST message;

4> have read and acted upon both System Information Block type 11, System Information Block type 11bis and System Information Block type 11ter, if scheduled on BCH, and System Information Block type 12 in a cell when:

5> the UE transmits an RRC message on RACH in RRC connected mode; or

5> the UE receives a message commanding to enter CELL_DCH state.

1> else:

2> the UE may transmit an RRC message on RACH before having read and acted upon System Information Block type 11, System Information Block type 11bis, System Information Block type 11ter, System Information Block type 12, System Information Block type 18 and System Information Block type 19, if scheduled on BCH.

NOTE 1: There are a number of system information blocks that include the same IEs while the UE mode/state in which the information is valid differs. This approach is intended to allow the use of different IE values in different UE mode/states.

NOTE 2: System Information Block Type 16 is also obtained by a UE while in GSM/GPRS. The details of this are not within the scope of this specification.

NOTE 3: When DEFERRED_MEASUREMENT_STATUS variable is set TRUE, the E-UTRA capable UE should read SIB19 before initiating the RRC connection setup procedure except for the case when it is re-directed from E-UTRA.

NOTE 4: A UE supporting RAN-assisted WLAN interworking may transmit an RRC message before having read and acted upon System Information Block type 23.

The Scheduling information column in table 8.1.1 specifies the position and repetition period for the System Information Block.

The modification of system information column in table 8.1.1 specifies the update mechanisms applicable for a certain system information block. For system information blocks with a value tag, the UE shall update the information according to subclause 8.1.1.7.1 or 8.1.1.7.2. For system information blocks with an expiration timer, the UE shall, when the timer expires, perform an update of the information according to subclause 8.1.1.7.4.

Table 8.1.1: Specification of system information block characteristics

System information block	Area scope	UE mode/state when block is valid	UE mode/state when block is read	Scheduling information	Modification of system information	Additional comment
Master information block	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	SIB_POS = 0 SIB_REP = 8 (FDD) SIB_REP = 8, 16, 32 (TDD) SIB_OFF=2	Value tag	See Note 5
Scheduling block 1	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Specified by the IE "Scheduling information" in MIB	Value tag	See Note 3
Scheduling block 2	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Specified by the IE "Scheduling information" in MIB	Value tag	See Note 3
Scheduling block 3	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "SB3 information" in MIB SIB_POS = 4 SIB_OFF = 2	Value tag	See Note 3
System information block type 1	Cell	Idle mode CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Idle, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	Note: The area scope of SIB1 is Cell but for compliance to earlier versions of the specification the coding of the scheduling information for SIB1 contains the ‘PLMN value tag’ information element. See Note 3
System information block type 2	Cell	URA_PCH	URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 3	Cell	Idle mode, (CELL_FACH, CELL_PCH, URA_PCH)	Idle mode, (CELL_FACH, CELL_PCH, URA_PCH)	Specified by the IE "Scheduling information"	Value tag	See Note 5
System information block type 4	Cell	CELL_FACH, CELL_PCH, URA_PCH	CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	If System information block type 4 is not broadcast in a cell, the connected mode UE shall apply information in System information block type 3 in connected mode. See Note 3
System information block type 5 and 5bis	Cell	Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only))	Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only))	Specified by the IE "Scheduling information"	Value tag	System information block type 5bis is sent instead of system information block type 5 in cells that use Band IV or Band IX or Band X.
System information block type 6	Cell	CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Specified by the IE "Scheduling information"	Value tag	If system information block type 6 is not broadcast in a cell, the connected mode UE shall read System information block type 5 or System information block type 5bis. If some of the optional IEs are not included in System information block type 6, the UE shall read the corresponding IEs in System information block type 5 or System information block type 5bis. In TDD mode system information block 6 shall only be read in CELL_DCH if required for open loop power control as specified in subclause 8.5.7 and/or if shared transport channels are assigned to the UE. If in these cases system information block type 6 is not broadcast the UE shall read system information block type 5. See Note 3
System information block type 7	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)	Specified by the IE "Scheduling information"	Expiration timer = MAX(32 , SIB_REP * ExpirationTimeFactor)	In TDD mode system information block type 7 shall only be read in CELL_DCH if shared transport channels are assigned to the UE. See Note 3
System information block type 11	Cell	Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH)	Idle mode (CELL_FACH, CELL_PCH, URA_PCH)	Specified by the IE "Scheduling information"	Value tag
System information block type 11bis	Cell	Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH)	Idle mode (CELL_FACH, CELL_PCH, URA_PCH)	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 11ter	Cell	Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH)	Idle mode (CELL_FACH, CELL_PCH, URA_PCH)	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 12	Cell	CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	If system information block type 12 is not broadcast in a cell, the connected mode UE shall read System information block type 11. If some of the optional IEs are not included in System information block type 12, the UE shall read the corresponding IEs in System information block type 11. See Note 3
System information block type 13	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 13.1	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 13.2	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 13.3	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 13.4	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 14	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Specified by the IE "Scheduling information"	Expiration timer = MAX(32 , SIB_REP * ExpirationTimeFactor)	This system information block is used in 3.84 Mcps TDD and 7.68 Mcps TDD mode only. System information block type 14 shall only be read in CELL_DCH if required for open loop power control as specified in subclause 8.5.7. See Note 3
System information block type 15	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15bis		Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.1	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.1bis		Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.1ter	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.2	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	For this system information block there may be multiple occurrences See Note 3
System information block type 15.2bis	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	For this system information block there may be multiple occurrences See Note 3
System information block type 15.2ter	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	For this system information block there may be multiple occurrences See Note 3
System information block type 15.3	PLMN	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	For this system information block there may be multiple occurrences See Note 3
System information block type 15.3bis	PLMN	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	For this system information block there may be multiple occurrences See Note 3
System information block type 15.4	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.5	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.6	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.7	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 15.8	Cell	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 16	Equivalent PLMN	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Idle Mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	For this system information block there may be multiple occurrences. This system information block is also valid while in GSM/GPRS. See Note 3
System information block type 17	Cell	CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Specified by the IE "Scheduling information"	Expiration timer = SIB_REP	This system information block is used in TDD mode only. System information block type 17 shall only be read if shared transport channels are assigned to the UE. See Note 3
System Information Block type 18	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System Information Block type 19	Cell	Idle mode, CELL_FACH,CELL_PCH, URA_PCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System Information Block type 20	Cell	Idle mode, CELL_PCH, URA_PCH	Idle mode, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System Information Block type 21	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	If System information block type 21 is broadcast in a cell, the EAB capable UE shall first apply the extended access barring information in System information block type 21. If as a result access to the cell is not barred, and if the UE is not ACDC capable then apply the access class barring information in System information block type 3, otherwise apply the ACDC barring information in System information block type 25. See Note 3
System information block type 22	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	If some of the optional IEs are not included in System information block type 22, the UE shall read the corresponding IEs in System information block type 5 or System information block type 5bis. See Note 3
System information block type 23	Cell	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Idle mode, CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Value tag	See Note 3
System information block type 24	Cell	CELL_FACH, CELL_PCH, URA_PCH	CELL_FACH, CELL_PCH, URA_PCH	Specified by the IE "Scheduling information"	Expiration timer = MAX(32 , SIB_REP * 2ⁿ) where n = Expiration Time Factor 2)	See Note 3
System information block type 25	Cell	Idle mode	Idle mode	Specified by the IE "Scheduling information"	Expiration timer = MAX(32 , SIB_REP * 2ⁿ) where n = Expiration Time Factor 2)	If System information block type 25 is broadcast in a cell, the ACDC capable UE shall apply the ACDC barring information in System information block type 25. See Note 3

NOTE 3: The UE behaviour is unspecified if this system information block is received on a cell operating in MBSFN mode as indicated in subclause 8.1.1.6.3. A network should not send these system information blocks on a cell operating in MBSFN mode.

NOTE 4: For 1.28 Mcps TDD, if a cell is operating in MBSFN mode, system information blocks are transmitted on the MBSFN Special Timeslot [30].

NOTE 5: For FDD UEs supporting the Neighbour Cell SI acquisition capability, the UE can read the System Information Block type 3 and the Master Information Block of a neighbouring cell when in CELL_DCH state.

8.1.1.1.3 Segmentation and concatenation of system information blocks

A generic SYSTEM INFORMATION message and SYSTEM INFORMATION 2 message is used to convey the system information blocks on the BCCH. The SYSTEM INFORMATION message is sent on BCH mapped on PCCPCH, and SYSTEM INFORMATION 2 message is sent on BCH mapped on SCCPCH (second system information broadcast channel). A given BCCH may be mapped onto a BCH transport channel according to subclause 8.1.1.1.2. The size of the SYSTEM INFORMATION message, and also the size of SYSTEM INFORMATION 2 message, shall fit the size of a BCH transport block.

The RRC layer in UTRAN performs segmentation and concatenation of encoded system information blocks. If the encoded system information block is larger than the size of a SYSTEM INFORMATION message or SYSTEM INFORMATION 2 message, it will be segmented and transmitted in several messages. If the encoded system information block is smaller than a SYSTEM INFORMATION message or SYSTEM INFORMATION 2 message, UTRAN may concatenate several system information blocks, or the first segment or the last segment into the same message as specified in the remainder of this clause.

Four different segment types are defined:

– First segment;

– Subsequent segment;

– Last segment;

– Complete.

Each of the types – First, Subsequent and Last segment – is used to transfer segments of a master information block, scheduling block or a system information block. The segment type, Complete, is used to transfer a complete master information block, complete scheduling block or a complete system information block.

Each segment consists of a header and a data field. The data field carries the encoded system information elements. The header contains the following parameters:

– The number of segments in the system information block (SEG_COUNT). This parameter is only included in the header if the segment type is "First segment".

– SIB type. The SIB type uniquely identifies the master information block, scheduling block or a system information block.

– Segment index. This parameter is only included in the header if the segment type is "Subsequent segment" or "Last segment".

UTRAN may combine one or several segments of variable length in the same SYSTEM INFORMATION message or SYSTEM INFORMATION 2 message. The following combinations are allowed:

1. No segment;

2. First segment;

3. Subsequent segment;

4. Last segment;

5. Last segment + First segment;

6. Last segment + one or several Complete;

7. Last segment + one or several Complete + First segment;

8. One or several Complete;

9. One or several Complete + First segment;

10. One Complete of size 215 to 226 (BCH on PCCPCH) or size 225 to 236 (BCH on SCCPCH);

11. Last segment of size 215 to 222 (BCH on PCCPCH) or size 225 to 232 (BCH on SCCPCH).

The "No segment" combination is used when there is no master information block, scheduling block or system information block scheduled for a specific BCH transport block.

UEs are not required to support the reception of multiple occurrences of the same system information block type within one SYSTEM INFORMATION message or SYSTEM INFORMATION 2 message.

NOTE: Since the SIB type is the same for each occurrence of the system information block, the UE does not know the order in which the occurrences, scheduled for this SYSTEM INFORMATION message or SYSTEM INFORMATION 2 message, appear. Therefore, the UE is unable to determine which scheduling information, e.g., value tag relates to which occurrence of the system information block.

8.1.1.1.4 Re-assembly of segments

The RRC layer in the UE shall perform re-assembly of segments. All segments belonging to the same master information block, scheduling block or system information block shall be assembled in ascending order with respect to the segment index. When all segments of the master information block, scheduling block or a system information block have been received, the UE shall perform decoding of the complete master information block, scheduling block or system information block. For System Information Block types 15.2, 15.3 and 16, which may have multiple occurrences, each occurrence shall be re-assembled independently.

The UE shall discard system information blocks of which segments were missing, of which segments were received out of sequence and/or for which duplicate segments were received. The only valid sequence is an ascending one with the sequence starting with the First Segment of the associated System Information Block. Alternatively to the re-assembly in strict ascending order without gaps and duplicates, the UE may also receive segments out of sequence and duplicates, provided that any stored segments are discarded when the value tag for that system information block type has changed. The UE is not required to re-assemble segments received from different system information broadcast channels (i.e. BCH on PCCPCH and BCH on SCCPCH).

If the UE receives a Subsequent segment or Last segment where the index in IE "Segment index" is equal to or larger than the number of segments stated in IE "SEG_COUNT" in the scheduling information for that scheduling block or system information block:

1> the UE may:

2> read all the segments to create a system information block as defined by the scheduling information read by the UE;

2> store the content of the system information block with a value tag set to the value NULL; and

2> consider the content of the scheduling block or system information block as valid:

3> until it receives the same type of scheduling block or system information block in a position according to its scheduling information; or

3> at most for 6 hours after reception.

1> and the UE shall:

2> re-read scheduling information for that scheduling block or system information block.

If the UE receives a Subsequent segment or Last segment where the index in IE "Segment index" is equal to or larger than the number of segments stated in IE "SEG_COUNT" in the First segment, the UE shall

1> discard all segments for that master information block, scheduling block or system information block; and

1> re-read the scheduling information for that system information block;

1> then re-read all segments for that system information block.

8.1.1.1.5 Scheduling of system information

Scheduling of system information blocks is performed by the RRC layer in UTRAN. If segmentation is used, it should be possible to schedule each segment separately.

To allow the mixing of system information blocks with short repetition period and system information blocks with segmentation over many frames, UTRAN may multiplex segments from different system information blocks. Multiplexing and de-multiplexing is performed by the RRC layer.

The scheduling of each system information block broadcast on a BCH transport channel is defined by the following parameters:

– the number of segments (SEG_COUNT);

– the repetition period (SIB_REP). The same value applies to all segments;

– the position (phase) of the first segment within one cycle of the Cell System Frame Number (SIB_POS(0)). Since system information blocks are repeated with period SIB_REP, the value of SIB_POS(i), i = 0, 1, 2, … SEG_COUNT-1 must be less than SIB_REP for all segments;

– the offset of the subsequent segments in ascending index order (SIB_OFF(i), i = 1, 2, … SEG_COUNT-1)
The position of the subsequent segments is calculated using the following: SIB_POS(i) = SIB_POS(i-1) + SIB_OFF(i).

The scheduling is based on the Cell System Frame Number (SFN). The SFN of a frame at which a particular segment, i, with i = 0, 1, 2, … SEG_COUNT-1 of a system information block occurs, fulfils the following relation:

SFN mod SIB_REP = SIB_POS(i)

In FDD and TDD the scheduling of the master information block is fixed as defined in table 8.1.1. For TDD, UTRAN may apply one of the values allowed for the master information block’s repetition period. The value that UTRAN is using in TDD is not signalled; UEs have to determine it by trial and error.

For scheduling block 3 (SB3) on the second system information broadcast channel:

– SIB_POS(0) is 4;

– SIB_OFF(i) is 2 (i = 1, 2, … SEG_COUNT-1), i.e. segments are transmitted consecutively.

The number of segments (SEG_COUNT) and repetition period (SIB_REP) of SB3 are signalled in IE "SB3 information" in Master Information Block.

In case the UE stores scheduling information in the variable SYSTEM_INFORMATION_CONTAINER, the information above is not used.

8.1.1.2 Initiation

The system information is continuously broadcast on a regular basis in accordance with the scheduling defined for each system information block.

8.1.1.3 Reception of SYSTEM INFORMATION messages by the UE

The UE shall read SYSTEM INFORMATION messages broadcast on a BCH transport channel in idle mode and in the connected mode in states CELL_FACH, CELL_PCH, URA_PCH and CELL_DCH (TDD only).

If the IE "SB3 information" is present in the Master Information Block and the UE supports second system information broadcast channel, the UE shall read SYSTEM INFORMATION 2 messages broadcast on a BCH transport channel in idle mode and in connected mode in states CELL_FACH, CELL_PCH and URA_PCH.

In idle mode and connected mode different combinations of system information blocks are valid. The UE shall acquire the system information blocks that are needed according to table 8.1.1. However, when the variable READY_FOR_COMMON_EDCH is set to TRUE and IE "UL interference for common E-DCH" is included in SIB 5/5bis, the UE shall acquire the system information block 7 upon entering a new cell and shall consider the content of the system information block 7 as always valid and ingore any system information expiry timer.

The UE may store system information blocks with cell, PLMN or Equivalent PLMN area scope (including their value tag if applicable) for different cells and different PLMNs, to be used if the UE returns to these cells.

The UE shall consider all stored system information blocks as invalid after it has been switched off. Some information obtained from system information may be stored by the UE or in the USIM for use in a stored information cell selection.

When selecting a new cell the UE shall consider all current system information blocks with area scope cell to be invalid. If the UE has stored valid system information blocks for the newly selected cell, the UE may set those as current system information blocks.

After selecting a new cell and this cell broadcasts an IE "PLMN Identity" in the MIB which is different from the IE "PLMN Identity" broadcast in the MIB in the previously selected cell, the UE shall consider all current system information blocks with area scope PLMN to be invalid. If the UE has previously stored valid system information blocks for the selected cell of the new PLMN, the UE may set those as current system information blocks.

When NAS informs AS about a new selected PLMN, the UE shall consider all stored system information blocks with area scope Equivalent PLMN to be invalid.

8.1.1.4 Void

8.1.1.5 Actions upon reception of the Master Information Block and Scheduling Block(s)

When selecting a new cell, the UE shall read the master information block. The UE may use the pre-defined scheduling information to locate the master information block in the cell.

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

1> if the IE "Multiple PLMN List" is not present in the Master Information Block:

2> consider the IE "PLMN identity" in the Master Information Block as the PLMN identity of the cell.

1> else:

2> consider the PLMN identities in the IE "Multiple PLMN List" as the PLMN identities of the cell;

2> when reading the "Multiple PLMN List", read all the PLMN identities in the list as follows:

3> if the IE "MIB PLMN Identity" is set to TRUE:

4> read the "PLMN identity" IE in the MIB and consider it as a part of the "Multiple PLMN List".

3> if the IE "MIB PLMN Identity" is set to FALSE:

4> not consider the "PLMN identity" IE in the MIB as a part of the "Multiple PLMN List";

4> not consider the IE "PLMN identity" in the MIB as a PLMN identity of the cell;

4> not forward the PLMN in the IE "PLMN identity" of the MIB to upper layers.

3> if the MCC is not present when reading a IE "PLMN identity with Optional MCC" in the IE "Multiple PLMN List":

4> set the MCC of this PLMN identity equal to the MCC of the closest preceding "PLMN identity with Optional MCC" in the "Multiple PLMN List" that includes an MCC;

4> or, if no such "PLMN identity with Optional MCC" exists, the UE shall set the MCC of this PLMN identity to the MCC of the "PLMN identity" IE in the Master Information Block irrespective of the value of the IE "MIB PLMN Identity".

1> if the UE is operating in "ANSI-41 mode" and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41":

2> store the ANSI-41 Information elements contained in the master information block and perform initial process for ANSI-41.

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, or if no IEs for the master information block are stored:

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.

1> if the value tags are the same the UE may use stored system information blocks and scheduling blocks using value tag that were stored for this cell and this PLMN as valid system information;

1> if the IE "SB3 information" is present in the Master Information Block and the UE supports second system information broadcast channel:

2> configure the second system information broadcast channel with the signalled channelization code value;

2> acquire Scheduling Block 3 (SB3) on the second system information broadcast channel.

For all system information blocks or scheduling blocks (SB1, SB2 or SB3) 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, or if no IEs for the corresponding system information block are stored:

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.

2> if the value tags are the same the UE may use stored system information blocks using value tag that were stored in this PLMN as valid system information.

1> for all system information blocks or scheduling blocks with area scope cell that use value tags:

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

2> if the value tags differ, or if no IEs for the corresponding system information block or scheduling block are stored:

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

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

2> if the value tags are the same the UE may use stored system information blocks using value tags that were stored for this cell and this PLMN as valid system information;

2> for any of System Information Block type 11, System Information Block type 11bis, System Information Block type 11ter or System Information Block type 12, for FDD:

3> if the value tag read in scheduling information for the system information block differs with the value stored within the variable VALUE_TAG for that system information block; and

3> if the UE is reading the system information block as a result of receiving the IE "BCCH modification info":

4> clear the stored IE "Common E-RGCH info FDD", if any;

4> determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75.

1> for system information blocks which may have multiple occurrences:

2> compare the value tag and the configuration or multiple occurrence identity for the occurrence of the system information blocks read in scheduling information with the value tag and configuration or multiple occurrence identity stored within the variable VALUE_TAG:

3> if the value tags differ, or if no IEs from the occurrence with that configuration or multiple occurrence identity of the system information block are stored:

4> store the value tag read in scheduling information for that system information block and the occurrence with that configuration or multiple occurrence identity into the variable VALUE_TAG;

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

3> if the value tags and the configuration or multiple occurrence identity are identical to those stored, the UE may use stored occurrences of system information blocks that were stored for this cell and this PLMN as valid system information.

Upon reception of the master information block or scheduling blocks, the UE shall:

1> if the variable BCCH_MODIFICATION_ACCESS_PROHIBITION is set to TRUE:

2> if the value tag of the Master Information Block in the system information is different from the value tag stored in the variable VALUE_TAG; and

2> the scheduling information of system information block type 3 is present in the master information block and the value tags for system information block type 3 in the master information block are the same:

3> set the variable BCCH_MODIFICATION_ACCESS_PROHIBITION to FALSE and allow the access on the cell according to 8.1.8.2.

2> else if the scheduling information of system information block type 3 is present in any of the scheduling blocks:

3> if the value tags for system information block type 3 in any of the scheduling blocks received after the MIB value tag change are the same:

4> set the variable BCCH_MODIFICATION_ACCESS_PROHIBITION to FALSE and allow the access on the cell according to 8.1.8.2.

For system information blocks, not supported by the UE, but referenced either in the master information block or in the scheduling blocks, the UE may:

1> skip reading this system information block;

1> skip monitoring changes to this system information block.

If the UE:

1> receives a scheduling block at a position different from its position according to the scheduling information for the scheduling block; or

1> receives a scheduling block for which scheduling information has not been received:

the UE may:

1> store the content of the scheduling block with a value tag set to the value NULL; and

1> consider the content of the scheduling block as valid until it receives the same type of scheduling block in a position according to its scheduling information or at most for 6 hours after reception.

If the UE does not find a scheduling block in a position where it should be according to its scheduling information, but a transport block with correct CRC was found at that position, the UE shall:

1> read the scheduling information for this scheduling block.

If the UE does not find the master information block in a position fulfilling:

SFN mod 32 = 0

but a transport block with correct CRC was found at that position, the UE shall:

1> consider the master information block as not found; and

1> consider the cell to be barred according to [4]; and

1> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

NOTE: This permits a different repetition for the MIB in later versions for FDD. In TDD it allows for a variable SIB_REP in this and future releases.

If the cell is not operating in MBSFN mode (according to Section 8.1.1.6.3) then:

1> If system information block type 1 is not scheduled on BCH, and system information block type 13 is not scheduled on BCH, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> If the UE only supports GSM-MAP but finds a cell that broadcasts System Information Block type 13 but not System Information Block type 1, the UE shall:

2> consider the cell barred.

1> If system information block type 1 is not scheduled on BCH; and

1> if the UE is operating in "GSM-MAP mode"; and

1> if the IE "PLMN type" in the Master Information Block has the value "GSM-MAP" or "GSM-MAP and ANSI-41", the UE shall:

2> indicate to upper layers that no CN system information is available.

1> If in idle mode and System Information Block type 3 is not scheduled on BCH, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> If in connected mode and System Information Block type 3 is not scheduled on BCH, and System Information Block type 4 is not scheduled on BCH, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> If in idle mode and neither System Information Block type 5 nor type 5bis is scheduled on BCH, or System Information Block type 5 or type 5bis is scheduled but IE "AICH info" (FDD) or IE "PICH info" is not present, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> If in connected mode and neither System Information Block type 5 nor type 5bis is scheduled on BCH, and System Information Block type 6 is not scheduled on BCH, or any of System Information Block type 5, type 5bis or type 6 is scheduled but IE "AICH info" (FDD) or IE "PICH info" is not present, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> If System Information Block type 7 is not scheduled on BCH, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> In 3.84 Mcps TDD and 7.68 Mcps TDD, if System Information Block type 14 is not scheduled on BCH, the UE shall:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

If the cell is operating in MBSFN mode (according to section 8.1.1.6.3) then:

1> If neither System Information block type 5 nor System Information Block type 5bis is scheduled on the BCH the UE shall:

2> not consider this MBSFN cluster as candidate during the MBSFN cluster selection and MBSFN cluster re-selection procedures [4]. The UE may choose to not recheck the status of this MBSFN cluster during the time corresponding to the maximum value for T_barred.

1> If System Information Block type 11 is not scheduled on the BCH the UE shall:

If System Information Block type 5 and System Information Block type 5bis are both scheduled on BCH:

1> the UE behaviour is unspecified.

8.1.1.6 Actions upon reception of system information blocks

The UE may use the scheduling information included within the master information block and the scheduling blocks to locate each system information block to be acquired. For System Information Block type 15.1bis, 15.2bis, 15.2ter, 15.3bis, 15.6, 15.7 and 15.8 the scheduling information shall be used to associate a system information block with a GNSS.

The UE should only expect one occurrence of the scheduling information for a system information block in the master information block and any of the scheduling blocks except for System Information Block type 16, System Information Block type 15.2 and System Information Block type 15.3, which may have multiple occurrences. System Information Blocks 15.1bis, 15.6, 15.7 and 15.8 have one occurrence for each GANSS supported while System Information Blocks 15.2bis, 15.2ter and 15.3bis may have multiple occurrences for each GANSS. However, to enable future introduction of new system information blocks, the UE shall also be able to receive system information blocks other than the ones indicated within the scheduling information. The UE may ignore contents of such system information block.

If the UE:

1> receives a system information block in a position according to the scheduling information for the system information block; and

1> this system information block uses a value tag; or

1> this system information block uses a value tag and configuration or multiple occurrence identity:

the UE shall:

1> store the content of the system information block together with the value of its value tag or the values of configuration and multiple occurrence identity and the associated value tag in the scheduling information for the system information block; and

1> consider the content of the system information block valid until, if used, the value tag in the scheduling information for the system information block is changed or at most for 6 hours after reception.

If the UE:

1> receives a system information block in a position according to the scheduling information for the system information block; and

1> this system information block does not use a value tag according to the system information block type:

the UE shall:

1> store the content of the system information block;

1> if HS_DSCH_DRX_CELL_FACH_2CYCLE_STATUS is set to TRUE and if the system information block corresponds to System Information Block type 7; or

1> if HS_DSCH_DRX_CELL_FACH_STATUS is set to TRUE and if the system information block corresponds to System Information Block type 7; or

1> if HS_SCCH_DRX_CELL_FACH_STATUS is set to TRUE and if the system information block corresponds to System Information Block type 7:

2> start an expiration timer using a value set to 800.

1> else:

2> start an expiration timer using a value as defined in Table 8.1.1 for that system information block type.

1> consider the content of the system information block valid until, the expiration timer expires.

If the UE:

1> receives a system information block at a position different from its position according to the scheduling information for the system information block; or

1> receives a system information block for which scheduling information has not been received; and

1> this system information block uses a value tag:

the UE may:

1> store the content of the system information block with a value tag set to the value NULL; and

1> consider the content of the system information block as valid until it receives the same type of system information block in a position according to its scheduling information or at most for 6 hours after reception.

If the UE:

1> receives a system information block with multiple occurrences at a position different from its position according to the scheduling information for the system information block; or

1> receives a system information block with multiple occurrences for which scheduling information has not been received; and

1> this system information block uses a value tag and configuration or multiple occurrence identity:

the UE shall:

1> ignore this information.

If the UE does not find a system information block in a position where it should be according to its scheduling information, but a transport block with correct CRC was found at that position, the UE shall read the scheduling information for this system information block.

The UE shall act upon all received information elements as specified in subclause 8.6 unless specified otherwise in the following subclauses.

The UE behaviour is unspecified when the same system information block type with different content is transmitted on both BCH on PCCPCH (system information broadcast channel) and BCH on SCCPCH (second system information broadcast channel).

8.1.1.6.1 System Information Block type 1

The UE should store all relevant IEs included in this system information block if the UE is operating in "GSM-MAP mode" and the IE "PLMN type" in the Master Information Block has the value "GSM-MAP" or "GSM-MAP and ANSI-41". The UE shall also:

1> check that the cell, according to information included in IE "CN common GSM-MAP NAS system information", is suitable [4];

1> if in connected mode:

2> not forward the content of the IE "CN common GSM-MAP NAS system information" to upper layers.

1> if in idle mode:

2> forward the content of the IE "CN common GSM-MAP NAS system information" to upper layers.

1> for the IE "CN domain system information list":

2> for each IE "CN domain system information" that is present:

3> check that the cell, according to information included in IE "CN domain specific NAS system information", is suitable [4];

3> if in connected mode:

4> not forward the content of the IE "CN domain specific NAS system information" to upper layers.

3> if in idle mode:

4> forward the content of the IE "CN domain specific NAS system information" and the IE "CN domain identity" to upper layers;

4> use the IE "CN domain specific DRX cycle length coefficient" to calculate frame number for the Paging Occasions as specified in [4];

4> store the value of the IE "CN domain specific DRX cycle length coefficient" for use in connected mode.

2> if an IE "CN domain system information" is not present for a particular CN domain:

3> if in idle mode:

4> indicate to upper layers that no CN system information is available for that CN domain.

1> if the UE has not yet entered UTRA RRC connected mode:

2> store the values of the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS;

2> if the IE "T323" is not present:

3> clear any value of the timer T323 stored in the IE "UE Timers and constants in connected mode" in the variable TIMERS_AND_CONSTANTS.

1> use the values stored in the variable TIMERS_AND_CONSTANTS for the relevant timers and constants.

8.1.1.6.2 System Information Block type 2

If in connected mode the UE should store all relevant IEs included in this system information block. The UE shall:

1> if in state URA_PCH, start to perform URA updates using the information in the IE "URA identity".

If in idle mode, the UE shall not use the values of the IEs in this system information block.

8.1.1.6.3 System Information Block type 3

The UE should store all relevant IEs included in this system information block. The UE shall:

1> if in connected mode, and System Information Block 4 is indicated as used in the cell:

2> read and act on information sent in that block.

1> if IE "Deferred measurement control reading support" is present:

2> set variable DEFERRED_MEASUREMENT_STATUS to TRUE.

1> else:

2> set variable DEFERRED_MEASUREMENT_STATUS to FALSE.

With respect to Domain Specific Access Control and Paging Permission with Access Control, the UE shall:

1> if the IE "Multiple PLMN List" is not included in the Master Information Block:

2> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", and the paging permission with access control as indicated by the IE "Paging Permission with Access Control Parameters for PLMN Of MIB".

1> else:

2> if the PLMN specified by the IE "PLMN Identity" of the Master Information Block is chosen by the UE:

3> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", and the paging permission with access control as indicated by the IE "Paging Permission with Access Control Parameters for PLMN Of MIB".

2> else, if N-th (N=1..5) PLMN in the IE "Multiple PLMNs" contained in the IE "Multiple PLMN List" is chosen by the UE:

3> if the IE "Domain Specific Access Restriction List" of the IE "Domain Specific Access Restriction For Shared Network" is indicated:

4> if the IE "Domain Specific Access Restriction Parameters For OperatorN" is indicated:

5> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For OperatorN".

3> else:

4> if the IE "Domain Specific Access Restriction Parameters For All" of the IE "Domain Specific Access Restriction For Shared Network" is indicated:

5> apply the domain specific access restrictions as indicated by the IE "Domain Specific Access Restriction Parameters For All".

3> if the IE "Paging Permission with Access Control List" of the IE "Paging Permission with Access Control For Shared Network" is indicated:

4> if the IE "Paging Permission with Access Control Parameters For OperatorN" is indicated:

5> apply the paging permission with access control as indicated by the IE "Paging Permission with Access Control Parameters For OperatorN".

3> else:

4> if the IE "Paging Permission with Access Control Parameters For All" of the IE "Paging Permission with Access Control For Shared Network" is indicated:

5> apply the paging permission with access control as indicated by the IE "Paging Permission with Access Control Parameters For All".

The UE shall apply the following handling with respect to any Access Class Barring information:

1> if in idle mode:

2> if the IE "Paging Permission with Access Control Parameters For PLMN Of MIB", the IE "Paging Permission with Access Control Parameters For OperatorN" or the IE "Paging Permission with Access Control Parameters For All" to be applied according to the requirements above is included in System Information Block Type 3, the UE shall:

3> if Paging Response Restriction Indication is set to "None":

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79], act as if no Access Class is barred in the IE "Access Class Barred List" as specified in [4].

3> if Paging Response Restriction Indication is set to "PS":

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] from CS domain or CS SERVICE NOTIFICATION message specified in [79], act as if no Access Class is barred in the IE "Access Class Barred List" as specified in [4];

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] from PS domain, act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" (or IE "Access Class Barred list" if IE "Domain Specific Access Class Barred List" is not present) as specified in [4].

3> if Paging Response Restriction Indication is set to "CS":

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] from PS domain, act as if no Access Class is barred in the IE "Access Class Barred List" as specified in [4];

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] from CS domain or CS SERVICE NOTIFICATION message specified in [79], act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" (or IE "Access Class Barred list" if IE "Domain Specific Access Class Barred List" is not present) as specified in [4].

3> else (if Paging Response Restriction Indication is set to "All"):

4> when sending a response to any PAGING TYPE 1 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79] from PS or CS domain, act on the IE "Access Class Barred list" if the IE "Domain Specific Access Class Barred List" is not present.

3> when initiating a Location/Registration procedure to CS domain, act on the IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "CS", as specified in [4];

3> when initiating an access to CS domain for any other reason, act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" (or IE "Access Class Barred list" if IE "Domain Specific Access Class Barred List" is not present) as specified in [4];

3> when initiating a Location/Registration procedure to PS domain, act on the IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "PS", as specified in [4];

3> when initiating an access to PS domain for any other reason, act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" (or IE "Access Class Barred list" if IE "Domain Specific Access Class Barred List" is not present) as specified in [4];

3> upon transition to UTRA RRC connected, the UE shall:

4> store that Paging Permission with Access Control Parameters to the variable "PPAC_PARAM" and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released;

4> if the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", the IE "Domain Specific Access Restriction Parameters For OperatorN" or the IE "Domain Specific Access Restriction Parameters For All" to be applied according to the requirements above is included in System Information Block Type 3:

5> store that Domain Specific Access Restriction Parameters to the variable "DSAC_PARAM" and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released.

4> act on the stored IE "Paging Response Restriction Indicator" when sending a response to any PAGING TYPE 1 or PAGING TYPE 2 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79];

4> act on the stored IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "CS", when initiating a Location/Registration procedure to the CS domain, as specified in [4];

4> act on the stored IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "PS", when initiating a Location/Registration procedure to the PS domain, as specified in [4];

4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain for any other reason, as specified in [4];

4> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, for any other reason ,as specified in [4].

2> if neither the IE "Paging Permission with Access Control Parameters For PLMN Of MIB", the IE "Paging Permission with Access Control Parameters For OperatorN" nor the IE "Paging Permission with Access Control Parameters For All" to be applied according to the requirements above is included in System Information Block Type 3:

3> if the IE "Domain Specific Access Restriction Parameters For PLMN Of MIB", the IE "Domain Specific Access Restriction Parameters For OperatorN" or the IE "Domain Specific Access Restriction Parameters For All" to be applied according to the requirements above is included in System Information Block Type 3 the UE shall:

4> act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4]. If "no restriction" was indicated in restriction status, the UE shall act as if no Access Class is barred in the IE "Domain Specific Access Class Barred List", and ignore the IE "Access Class Barred List" in the IE "Cell Access Restriction";

4> act on the IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4]. If "no restriction" was indicated in restriction status, the UE shall act as if no Access Class is barred in the IE "Domain Specific Access Class Barred List", and ignore the IE "Access Class Barred List" in the IE "Cell Access Restriction";

4> upon transition to UTRA RRC connected, the UE shall:

5> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "CS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the CS domain, as specified in [4];

5> act on the stored IE "Domain Specific Access Class Barred List" if indicated in the IE "PS Domain Specific Access Restriction" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, as specified in [4].

3> else:

4> act on the IE "Access Class Barred list" when initiating RRC Connection establishment as specified in [4].

1> if in connected mode:

2> for the variable "DSAC_PARAM":

4> if the variable "DSAC_PARAM is not set, the UE shall:

4> else (the access class barring information is stored) UE shall:

5> update the variable "DSAC_PARAM" with that Domain Specific Access Restriction Parameters.

3> else:

4> if the variable "DSAC_PARAM" is set, the UE shall:

5> clear the variable "DSAC_PARAM".

2> for the variable "PPAC_PARAM":

3> if the IE "Paging Permission with Access Control Parameters For PLMN Of MIB", the IE "Paging Permission with Access Control Parameters For OperatorN" or the IE "Paging Permission with Access Control Parameters For All" to be applied according to the requirements above is included in the System Information Block Type 3:

4> if the variable "PPAC_PARAM" is not set, the UE shall:

5> store that Paging Permission with Access Control Parameters to the variable "PPAC_PARAM" and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released.

4> else (the access class barring information is stored) UE shall:

5> update the variable "PPAC_PARAM" with that Paging Permission with Access Control Parameters.

3> else:

4> if the variable "PPAC_PARAM" is set, the UE shall:

5> clear the variable "PPAC_PARAM".

2> the UE shall:

3> if the variable "DSAC_PARAM" is set:

4> if the variable "PPAC_PARAM" is set:

5> act on the stored IE "Paging Response Restriction Indicator" when sending a response to any PAGING TYPE 1 or PAGING TYPE 2 message, Paging message specified in [67] or CS SERVICE NOTIFICATION message specified in [79];

5> act on the stored IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "CS", when initiating a Location/Registration procedure to the CS domain, as specified in [4];

5> act on the stored IE "Location/Registration Access Class Barred List" if the IE "Location/Registration Restriction Indicator" is set to "All" or "PS", when initiating a Location/Registration procedure to the PS domain, as specified in [4];

4> if the variable "PPAC_PARAM" is not set:

3> else:

4> act as if no Access Class is barred.

With respect to "CSG Identity" IE, the UE shall:

1> if the IE "CSG Identity" is present:

2> forward the content of IE "CSG Identity" to the upper layers.

If the IE "MBSFN only service" is set to TRUE the UE shall:

1> consider this cell to operate in MBSFN mode;

1> for TDD consider that all slots operate in MBSFN mode;

1> for FDD, 3.84 Mcps TDD IMB and 3.84/7.68 Mcps TDD if the UE capabilities allow the reception of MBSFN in addition to the normal UE operation the UE may receive MBMS services from this cell in accordance with requirements for selection of a cell providing only MBSFN as specified in [4]. For 1.28 Mcps TDD, if the UE capabilities allow the reception of MBSFN in addition to the normal UE operation the UE may get synchronized to the MBSFN cluster as specified in [4].

With respect to "IMS Emergency Support Indicator" IE, the UE shall:

1> if the IE "IMS Emergency Support Indicator" is present:

2> forward the content of IE "IMS Emergency Support Indicator" to the upper layers.

For 1.28Mcps TDD, if the IE "Mapping Info" is present and the mapping info for 3.84 Mcps TDD is included, UE shall:

1> acquire and store the TDD frequencies and PCCPCH RSCP threshold information in the variable CELL_RESELECTION_INFO_LCRTDD for cell reselection from GERAN to 1.28Mcps TDD.

else

1> clear the variable CELL_RESELECTION_INFO_LCRTDD.

If the variable BCCH_MODIFICATION_ACCESS_PROHIBITION is set to TRUE, the UE shall:

1> set the variable BCCH_MODIFICATION_ACCESS_PROHIBITION to FALSE and allow the access on the cell according to 8.1.8.2.

8.1.1.6.4 System Information Block type 4

If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall:

1> if in connected mode:

2> read and act on information sent in this block;

2> read the System Information Block Type 3 for any Access Class Barring information and act on that information as described in subclause 8.1.1.6.3.

If in idle mode, the UE shall not use the values of the IEs included in this system information block.

8.1.1.6.5 System Information Block type 5 and 5bis

The UE should store all relevant IEs included in this system information block. The UE shall:

1> if the IE "Frequency band indicator" is included and set to a frequency band supported in the UE radio access capability, the IE "Frequency band indicator 2" is not included, and the IE "Frequency band indicator 3" is not included; or

1> if the IE "Frequency band indicator" is included and set to "extension indicator", and the IE "Frequency band indicator 2" is included and set to a frequency band supported in the UE radio access capability, and the IE "Frequency band indicator 3" is not included; or

1> if the IE "Frequency band indicator" is included and set to "extension indicator", and the IE "Frequency band indicator 2" is included and set to "extension indicator", and the IE "Frequency band indicator 3" is included and set to a frequency band supported in the UE radio access capability; or

1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 2110MHz-2170MHz, and Band I is part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 1930MHz – 1990MHz, and Band II is part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 1805MHz-1880MHz, and Band III is part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the UE supports multi-band signaling and the IE "Multiple Frequency Band indicator list" is included and contains a frequency band supported in the UE radio access capability:

2> consider the cell to be not barred according to [4].

1> else if the IE "Frequency band indicator" is included and set to a frequency band not supported in the UE radio access capability, and the IE "Frequency band indicator 2" is not included, and the IE "Frequency band indicator 3" is not included; or

1> if the IE "Frequency band indicator" is included and set to "extension indicator", if the IE "Frequency band indicator 2" is included and set to a frequency band not supported in the UE radio access capability, and the IE "Frequency band indicator 3" is not included; or

1> if the IE "Frequency band indicator" is included and set to "extension indicator", and the IE "Frequency band indicator 2" is included and set to "extension indicator", and if the IE "Frequency band indicator 3" is included and set to "extension indicator" or to a frequency band not supported in the UE radio access capability; or

1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 2110MHz-2170MHz, and Band I is not part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 1930MHz-1990MHz, and Band II is not part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included in System Information Block type 5, the DL frequency is in between 1805MHz-1880MHz, and Band III is not part of the frequency bands supported by the UE in the UE radio access capability; or

1> if the UE supports multi-band signalling and the IE "Multiple Frequency Band indicator list" is included and does not contain a frequency band supported in the UE radio access capability:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> else:

2> the UE behaviour is not specified.

1> if the IE "Frequency Bands Indicator Support" is included:

2> if the first frequency band is one of the frequency bands supported in the UE radio access capability:

3> set the "Support of the first Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to TRUE.

2> else:

3> set the "Support of the first Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to FALSE.

2> if the second frequency band is present and the second frequency band is one of the frequency bands supported in the UE radio access capability:

3> set the "Support of the second Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to TRUE.

2> else:

3> set the "Support of the second Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to FALSE.

1> else:

2> for FDD, clear the variable FREQUENCY_BAND_INDICATOR_SUPPORT.

2> for 1.28Mcps TDD,

3> if the frequency band e is one of the frequency bands supported in the UE radio access capability:

4> set the "Support of the first Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to TRUE.

3> else:

4> set the "Support of the first Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to FALSE.

3> if the frequency band f is one of the frequency bands supported in the UE radio access capability:

4> set the "Support of the second Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to TRUE.

3> else:

4> set the "Support of the second Frequency Band" in variable FREQUENCY_BAND_INDICATOR_SUPPORT to FALSE.

1> for FDD, if the IE "Adjacent Channel Interference level" is included and UE supports DL interference mitigation:

2> configure the lower layers with the IE "Adjacent Channel Interference level", which may be used to mitigate the DL interference, e.g. to apply an optimized Rx filtering.

1> if in connected mode, and System Information Block type 6 is indicated as used in the cell:

2> read and act on information sent in System Information Block type 6.

1> if System Information Block type 22 is indicated as used in the cell:

2> read and act on information sent in System Information Block type 22.

1> if the UE is in CELL_PCH state, determine the value for the HSPA_RNTI_STORED_PCH variable and take the corresponding actions as described in subclause 8.5.56;

1> determine the value for the READY_FOR_COMMON_EDCH variable and take the corresponding actions as described in subclause 8.5.47;

1> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46;

1> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

1> if the UE is in CELL_FACH state or Idle mode; and

1> if the UE does support E-DCH transmission in CELL_FACH state and Idle mode; and

1> if the IE "HS-DSCH common system information" is included in system information block type 5 or 5bis; and

1> if the IE "Common E-DCH system info" is included system information block type 5 or 5bis:

2> for 1.28 Mcps TDD, if the IE "Frequency info" is included in system information block type 5:

3> store and use the frequency indicated by the IE "Frequency info" as the secondary frequency for Enhanced Uplink transmission in CELL_FACH state and Idle mode;

3> if the IE "E-RUCCH Access Service class" and/or "E-RUCCH persistence scaling factor list" and/or "SYNC_UL info" and/or IE " PRACH Information" are included in the IE "E-RUCCH Info" in system information block type 5:

4> store and use the information contained in IE "E-RUCCH info".

3> else:

4> use the same configuration in the IE "PRACH system information list" on the secondary frequency indicated by the IE "Frequency info".

3> if the IE "UpPCH Position Info" is included:

4> store and use the UpPCH position indicated by the IE "UpPCH Position Info".

2> for 1.28 Mcps TDD, if the IE "Frequency info" is not included in system information block type 5:

3> use the primary frequency for Enhanced Uplink transmission in CELL_FACH state and Idle mode;

3> use the same configuration in the IE "PRACH system information list" on the primary frequency for the IE "E-RUCCH Access Service class" and/or "E-RUCCH persistence scaling factor list" and/or "SYNC_UL info" and/or IE " PRACH Information".

2> use the Enhanced Uplink in CELL_FACH state and Idle mode as specified in section 8.5.45 for FDD or 8.5.45a for 1.28 Mcps TDD and [15] for DTCH, DCCH and CCCH transmission;

2> for 1.28 Mcps TDD, if the IE "Treset Usage Indicator" is included:

3> store IE "Treset Usage Indicator".

2> else:

3> clear the stored IE.

1> else:

2> if the UE is in CELL_PCH state; and

2> if the UE does support E-DCH transmission in CELL_FACH state and Idle mode; and

2> if the IE "HS-DSCH paging system information" is included in system information block type 5 or 5bis; and

2> if the IE "Common E-DCH system info" is included system information block type 5 or 5bis; and

2> if the variables C_RNTI, E_RNTI and H_RNTI are set:

3> use the Enhanced Uplink in CELL_FACH state and Idle mode as specified in section 8.5.45 for FDD or 8.5.45a for 1.28 Mcps TDD and [15] for DTCH and DCCH transmission.

2> else:

3> replace the TFS of the RACH with the one stored in the UE if any;

3> let the physical channel(s) of type PRACH given by the IE(s) "PRACH info" be the default in uplink for the PRACH if UE is in CELL_FACH state;

3> start to receive the physical channel of type AICH using the parameters given by the IE "AICH info" (FDD only) when given allocated PRACH is used;

3> if the IE "Additional Dynamic Transport Format Information for CCCH" is included for the selected PRACH:

4> use this transport format for transmission of the CCCH.

3> else:

4> use the first instance of the list of transport formats as in the IE "RACH TFS" for the used RACH received in the IE "PRACH system information list" when using the CCCH.

1> for 3.84 Mcps and 7.68 Mcps TDD; or

1> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_FACH state; or

1> if the IE "HS-DSCH common system information" is not included; or

1> for 1.28 Mcps TDD, if the IE "Common E-DCH system info" is not included:

2> replace the TFS of the FACH/PCH with the one stored in the UE if any;

2> start to monitor its paging occasions on the selected PICH if UE is in Idle mode or in CELL_PCH or URA_PCH state;

2> start to receive the selected physical channel of type Secondary CCPCH using the parameters given by the IE(s) "Secondary CCPCH info" if UE is in CELL_FACH state;

2> in 3.84 Mcps TDD and 7.68 Mcps TDD:

3> use the IE "TDD open loop power control" as defined in subclause 8.5.7 when allocated PRACH is used.

2> in TDD:

3> if the IE "PDSCH system information" and/or the IE "PUSCH system information" is included:

4> store each of the configurations given there with the associated identity given in the IE "PDSCH Identity" and/or "PUSCH Identity" respectively. For every configuration, for which the IE "SFN Time info" is included, the information shall be stored for the duration given there.

2> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

1> else:

2> if the UE is in Idle mode:

3> if the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

4> for FDD, start to receive HS-DSCH according to the procedure in subclause 8.5.37;

4> for 1.28 Mcps TDD, if the IE "Frequency info" is included in system information block type 5:

5> start to receive HS-DSCH according to the procedure in subclause 8.5.37 at the frequency indicated by the IE "Frequency info".

4> for 1.28 Mcps TDD, if the IE "Frequency info" is not included in system information block type 5:

5> start to receive HS-DSCH according to the procedure in subclause 8.5.37 at the primary frequency.

3> else:

4> replace the TFS of the FACH/PCH with the one stored in the UE if any;

4> start to monitor its paging occasions on the selected PICH.

3> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

2> if the UE is in CELL_FACH:

3> if variable H_RNTI is set:

4> start to receive HS-DSCH according to the procedure in subclause 8.5.36.

3> else:

4> if the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

5> for FDD, start to receive HS-DSCH according to the procedure in subclause 8.5.37;

5> for 1.28 Mcps TDD, if the IE "Frequency info" is included in system information block type 5:

6> start to receive HS-DSCH according to the procedure in subclause 8.5.37 at the frequency indicated by the IE "Frequency info".

5> for 1.28 Mcps TDD, if the IE "Frequency info" is not included in system information block type 5:

6> start to receive HS-DSCH according to the procedure in subclause 8.5.37 at the primary frequency.

3> if the IE "HS-DSCH DRX in CELL_FACH Information" is included:

4> determine the value of the HS_DSCH_DRX_CELL_FACH_STATUS variable according to the procedure in subclause 8.5.48.

2> if the UE is in CELL_PCH or URA_PCH state:

3> for FDD and for 1.28 Mcps TDD, if the UE supports HS-DSCH reception in CELL_PCH and URA_PCH state; and

3> if IE "HS-DSCH paging system information" is included:

4> if this IE is not currently stored; and

4> if the value of the IE "SRNC identity" in the variable U_RNTI is not equal to the 12 MSBs of the received IE "Cell identity" in System Information Block type 3; and

4> if the UE is in URA_PCH state:

5> initiate the URA update procedure as specified in subclause 8.3.1, using the cause "periodic URA update".

4> for FDD; or

4> for 1.28 Mcps TDD, if both variable H_RNTI and variable C_RNTI are set:

5> start to monitor the paging occasions and PICH monitoring occasions determined according to subclauses 8.6.3.1a, 8.6.3.2 and 8.5.39 and receive PCCH on the HS-DSCH mapped on the HS-PDSCH, or DCCH and DTCH and BCCH on the HS-DSCH mapped on the HS-PDSCH and the associated HS-PDSCH selected by the UE according to the procedure in subclause 8.5.40 for FDD and 8.5.40a for 1.28 Mcps TDD.

3> else:

4> replace the TFS of the FACH/PCH with the one stored in the UE if any;

4> start to monitor its paging occasions on the selected PICH;

4> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

If a UE is a 12 kbps class UE according to [35] and the UE has a lower capability than required to support all transport channel configurations mapped on a specific Secondary CCPCH, the UE shall at a certain time instant still be able to decode those transport channels mapped on this Secondary CCPCH that do match the capability supported by the UE. The UE shall use the TFCI bits for that Secondary CCPCH, to distinguish a transport channel configuration that is supported by the UE from a transport channel configuration that is not supported by the UE.

In particular if the UE is a 12 kbps class UE according to [35] and it does not support the processing requirement at a given point in time for a Secondary CCPCH, it shall still be able to decode the same Secondary CCPCH when the processing requirement is consistent with the UE capability. Or if the UE does not support the number of TFs or the coding of a certain transport channel on a Secondary CCPCH, it shall still be able to decode other transport channels mapped on the same Secondary CCPCH that is consistent with what is supported by the UE.

The UE shall:

1> if the IE "Secondary CCPCH system information MBMS" is included:

2> apply the Secondary CCPCH and FACH indicated by the IE "FACH carrying MCCH" for receiving MCCH.

1> otherwise, if the IE "Secondary CCPCH system information" includes the IE "MCCH configuration information":

2> apply the Secondary CCPCH and FACH indicated by the IE “MCCH configuration information” for receiving MCCH.

1> for TDD, if the IE "TDD MBSFN Information" is included:

2> apply the scrambling codes (as referenced by the "Cell parameters ID") to each timeslot indicated by "TDD MBSFN Information".

8.1.1.6.6 System Information Block type 6

If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall:

1> if the IE "Frequency band indicator" is not included, the DL frequency is in between 2110MHz-2170MHz, and Band I is part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included, the DL frequency is in between 1930MHz – 1990MHz, and Band II is part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included, the DL frequency is in between 1805MHz-1880MHz, and Band III is part of the frequency bands supported by the UE in the UE radio access capability; or

1> if the UE supports multi-band signalling and the IE "Multiple Frequency Band indicator list" is included and contains a frequency band supported in the UE radio access capability:

2> consider the cell to be not barred according to [4].

1> if the IE "Frequency band indicator" is not included, the DL frequency is in between 2110MHz-2170MHz, and Band I is not part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included, the DL frequency is in between 1930MHz-1990MHz, and Band II is not part of the frequency bands supported by the UE in the UE radio access capability, or

1> if the IE "Frequency band indicator" is not included, the DL frequency is in between 1805MHz-1880MHz, and Band III is not part of the frequency bands supported by the UE in the UE radio access capability; or

1> if the UE supports multi-band signaling and the IE "Multiple Frequency Band indicator list" is included and does not contain a frequency band supported in the UE radio access capability:

2> consider the cell to be barred according to [4]; and

2> consider the barred cell as using the value "not allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "T_barred".

1> else:

2> the UE behaviour is not specified.

1> for FDD, if the IE "Adjacent Channel Interference level" is included and UE supports DL interference mitigation:

2> configure the lower layers with the IE "Adjacent Channel Interference level", which may be used to mitigate the DL interference, e.g. to apply an optimized Rx filtering.

1> if the UE is in CELL_FACH state; and

1> if the UE does support E-DCH transmission in CELL_FACH state and Idle mode; and

1> if the IE "HS-DSCH common system information" is included in system information block type 5 or 5bis; and

1> if the IE "Common E-DCH system info" is included system information block type 5 or 5bis:

2> use the Enhanced Uplink in CELL_FACH state and Idle mode as specified in section 8.5.45 for FDD or 8.5.45a for 1.28 Mcps TDD and [15] for DTCH, DCCH and CCCH transmission.

1> else:

2> if the UE is in CELL_PCH state; and

2> if the UE does support E-DCH transmission in CELL_FACH state and Idle mode; and

2> if the IE "HS-DSCH paging system information" is included in system information block type 5 or 5bis; and

2> if the IE "Common E-DCH system info" is included system information block type 5 or 5bis; and

2> if the variables C_RNTI, E_RNTI and H_RNTI are set:

3> use the Enhanced Uplink in CELL_FACH state and Idle mode as specified in section 8.5.45 for FDD or 8.5.45a for 1.28 Mcps TDD and [15] for DTCH and DCCH transmission.

2> else:

3> replace the TFS of the RACH with the one stored in the UE if any;

3> let the physical channel(s) of type PRACH given by the IE(s) "PRACH info" be the default in uplink if UE is in CELL_FACH state. If the IE "PRACH info" is not included, the UE shall read the corresponding IE(s) in System Information Block type 5 or System Information Block type 5bis and use that information to configure the PRACH;

3> start to receive the physical channel of type AICH using the parameters given by the IE "AICH info" when associated PRACH is used. If the IE "AICH info" is not included, the UE shall read the corresponding IE in System Information Block type 5 or System Information Block type 5bis and use that information (FDD only);

3> if the IE "Additional Dynamic Transport Format Information for CCCH" is included for the selected PRACH:

4> use this transport format for transmission of the CCCH (FDD only).

3> else:

4> use the first instance of the list of transport formats as in the IE "RACH TFS" for the used RACH received in the IE "PRACH system information list" when using the CCCH (FDD only).

1> for 3.84 Mcps and 7.68 Mcps TDD; or

1> for FDD and 1.28 Mcps TDD, if the UE does not support HS-DSCH reception in CELL_FACH state; or

1> if the IE "HS-DSCH common system information" is not included in System Information Block type 5 or System Information Block type 5bis; or

1> for 1.28 Mcps TDD, if the IE "Common E-DCH system info" is not included:

2> replace the TFS of the FACH/PCH with the one stored in the UE if any;

2> select a Secondary CCPCH as specified in [4] and in subclause 8.5.19, and start to receive the physical channel of type PICH associated with the PCH carried by the selected Secondary CCPCH using the parameters given by the IE "PICH info" if the UE is in CELL_PCH or URA_PCH state. If the IE "PICH info" is not included, the UE shall read the corresponding IE in System Information Block type 5 or System Information Block type 5bis and use that information;

2> start to monitor its paging occasions on the selected PICH if the UE is in CELL_PCH or URA_PCH state;

2> start to receive the selected physical channel of type Secondary CCPCH using the parameters given by the IE(s) "Secondary CCPCH info" if the UE is in CELL_FACH state. If the IE "Secondary CCPCH info" is not included, the UE shall read the corresponding IE(s) in System Information Block type 5 or System Information Block type 5bis and use that information;

2> in 3.84 Mcps TDD and 7.68 Mcps TDD: use the IE "TDD open loop power control" as defined in subclause 8.5.7;

2> in TDD: if the IE "PDSCH system information" and/or the IE "PUSCH system information" is included, store each of the configurations given there with the associated identity given in the IE "PDSCH Identity" and/or "PUSCH Identity" respectively. For every configuration, for which the IE "SFN Time info" is included, the information shall be stored for the duration given there;

2> take the corresponding actions as described in subclause 8.5.37a.

1> else:

2> if the UE is in CELL_FACH:

3> read and use the IE "HS-DSCH common system information" in System Information Block type 5 or System Information Block type 5bis;

3> if variable H_RNTI is set:

4> start to receive HS-DSCH according to the procedure in subclause 8.5.36.

3> else:

4> if the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE:

5> start to receive HS-DSCH according to the procedure in subclause 8.5.37.

2> if the UE is in CELL_PCH or URA_PCH state:

3> for FDD and for 1.28 Mcps TDD, if the UE supports HS-DSCH reception in CELL_PCH and URA_PCH state; and

3> if IE "HS-DSCH paging system information" is included in System Information Block type 5 or System Information Block type 5bis:

4> read and use the IE "HS-DSCH paging system information" in System Information Block type 5 or System Information Block type 5bis;

4> for FDD; or

4> for 1.28 Mcps TDD, if both variable H_RNTI and variable C_RNTI are set:

5> start to monitor the paging occasions and PICH monitoring occasions determined according to subclauses 8.6.3.1a, 8.6.3.2 and 8.5.39 and receive PCCH or DCCH and DTCH according to the procedure in subclause 8.5.40 for FDD and 8.5.40a for 1.28 Mcps TDD.

3> else:

4> replace the TFS of the FACH/PCH with the one stored in the UE if any;

4> select a Secondary CCPCH as specified in [4] and in subclause 8.5.19, and start to receive the physical channel of type PICH associated with the PCH carried by the selected Secondary CCPCH using the parameters given by the IE "PICH info". If the IE "PICH info" is not included, the UE shall read the corresponding IE in System Information Block type 5 or System Information Block type 5bis and use that information;

4> start to monitor its paging occasions on the selected PICH;

4> take the actions related to the HS_DSCH_RECEPTION_GENERAL variable as described in subclause 8.5.37a.

If in idle mode, the UE shall not use the values of the IEs in this system information block.

8.1.1.6.7 System Information Block type 7

The UE should store all relevant IEs included in this system information block.

8.1.1.6.8 Void

8.1.1.6.9 Void

8.1.1.6.10 Void

8.1.1.6.11 System Information Block type 11

If the cell is not operating in MBSFN mode according to subclause 8.1.1.6.3 the UE should store all relevant IEs included in this system information block. If the cell is not operating in MBSFN mode according to subclause 8.1.1.6.3 the UE shall:

1> if in idle mode:

2> clear the variable MEASUREMENT_IDENTITY.

1> if IE "FACH measurement occasion info" is included:

2> act as specified in subclause 8.6.7.

1> else:

2> may perform inter-frequency/inter-RAT measurements or inter-frequency/inter-RAT cell re-selection evaluation, if the UE capabilities permit such measurements while simultaneously receiving the S-CCPCH of the serving cell.

1> clear the variable CELL_INFO_LIST;

1> act upon the received IE "Intra-frequency cell info list"/"Inter-frequency cell info list"/"Inter-RAT cell info list" as described in subclause 8.6.7.3;

1> if the IE "Inter-frequency RACH reporting information" is included in the system information block:

2> read the IE and use that information for the inter-frequency measurements as specified in subclause 8.5.23.

1> if in idle mode; or

1> if in connected mode and if System Information Block type 12 is not broadcast in the cell:

2> if no intra-frequency measurement stored in the variable MEASUREMENT_IDENTITY was set up or modified through a MEASUREMENT CONTROL message:

3> if included, store the IE "Intra-frequency reporting quantity" and the IE "Intra-frequency measurement reporting criteria" or "Periodical reporting criteria" in order to activate reporting when state CELL_DCH is entered in the variable MEASUREMENT_IDENTITY. The IE "Cells for measurement" is absent for this measurement. The IE "Measurement Validity" is absent for this measurement after a state transition to CELL_DCH.

1> if in connected mode and if System Information Block type 12 is not broadcast in the cell:

2> read the IE "Traffic volume measurement system information";

2> if no traffic volume measurement with the measurement identity indicated in the IE "Traffic volume measurement system information" was set up or modified through a MEASUREMENT CONTROL message:

3> update the variable MEASUREMENT_IDENTITY with the measurement information received in that IE.

1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IE "intra-frequency cell info list", the IE "inter-frequency cell info list" or the IE "inter-RAT cell info list" in System Information Block type 11:

2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information".

1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following:

2> if IE "HCS neighbouring cell information" is not included for the first new cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 11:

3> use the default values specified for the IE "HCS neighbouring cell information" for that cell.

2> if IE "HCS neighbouring cell information" is not included for any other new cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 11:

3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 11.

1> if the value of the IE "Cell selection and reselection quality measure" is different from the value of the IE "Cell selection and reselection quality measure" obtained from System Information Block type 3 or System Information Block type 4:

2> use the value of the IE from this System Information Block and ignore the value obtained from System Information Block type 3 or System Information Block type 4.

1> if in connected mode, and System Information Block type 12 is indicated as used in the cell:

2> read and act on information sent in System Information Block type 12 as indicated in subclause 8.1.1.6.12.

1> if IE "MBSFN frequency list" is included:

2> act as specified in subclause 8.6.9.9ac.

1> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75;

For 1.28 Mcps TDD if the cell is operating in MBSFN only mode according to subclause 8.1.1.6.3 the UE shall:

1> store the frequencies and their corresponding "cell parameter ID" indicated in the IE "MBSFN LCR TDD frequency list" included in the IE "MBSFN frequency list".

If the cell is operating in MBSFN mode according to subclause 8.1.1.6.3 the UE may:

1> for FDD and 3.84/7.68 Mcps TDD consider the cells indicated in the IE "Intra-frequency cell info list" in the IE "Intra-frequency measurement system information" as candidates for the selection of the MBSFN cluster;

1> for 1.28 Mcps TDD consider there exist MBSFN clusters deployed with the frequencies and their corresponding "cell parameter ID" stored.

For 1.28 Mcps TDD if the cell is not operating in MBSFN only mode but associated with one or more MBSFN clusters the UE shall:

1> store the frequencies and their corresponding "cell parameter ID" indicated in the IE "MBSFN LCR TDD frequency list" included in the IE "MBSFN frequency list";

1> consider there exist MBSFN clusters deployed with the frequencies and their corresponding “cell parameter ID” stored;

1> search an MBSFN cluster in MBSFN only mode with its frequency and corresponding "cell parameter ID" for monitoring the MBMS services delivered in dedicated MBSFN frequency layer.

NOTE: The IE "Intra-frequency cell info list" may not include information about all neighbouring MBSFN clusters

8.1.1.6.11a System Information Block type 11bis

The UE should store all relevant IEs included in this system information block. The UE shall:

1> after reception of SIB 11 act upon the received IEs "Intra-frequency cell info list", "Inter-frequency cell info list" and "Inter-RAT cell info list" as described in subclause 8.6.7.3;

1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IEs "New Intra-frequency cells", "New Inter-frequency cells" or "New Inter-RAT cells" in System Information Block type 11bis:

2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information".

1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following:

2> if IE "HCS neighbouring cell information" is not included for the first new cell in the IEs "New Intra-frequency cells", "New Inter-frequency cells" or "New Inter-RAT cells" in System Information Block type 11bis:

3> use the default values specified for the IE "HCS neighbouring cell information" for that cell.

2> if IE "HCS neighbouring cell information" is not included for any other new cell in the IEs "New Intra-frequency cells", "New Inter-frequency cells" or "New Inter-RAT cells" in System Information Block type 11bis:

3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 11bis.

1> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75.

8.1.1.6.11b System Information Block type 11ter

The UE should store all relevant IEs included in this system information block. The UE shall:

1> after reception of SIB11 and SIB 11bis, if scheduled on BCH, act upon the received IE "Inter-frequency cell info list" as described in subclause 8.6.7.3;

1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IE "New Inter-frequency cells" in System Information Block type 11ter:

2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information".

1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following:

2> if IE "HCS neighbouring cell information" is not included for the first new cell in the IE "New Inter-frequency cells" in System Information Block type 11ter:

3> use the default values specified for the IE "HCS neighbouring cell information" for that cell.

2> if IE "HCS neighbouring cell information" is not included for any other new cell in the IE "New Inter-frequency cells" in System Information Block type 11ter:

3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 11ter.

8.1.1.6.12 System Information Block type 12

If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall:

1> after reception of System Information Block type 11; and

1> after reception of System Information Block type 11bis, if broadcast in the cell; and

1> after reception of System Information Block type 11ter, if broadcast in the cell:

2> update the variable MEASUREMENT_IDENTITY with the measurement information in the received IEs unless specified otherwise.

1> if IE "FACH measurement occasion info" is included:

2> act as specified in subclause 8.6.7.

1> else:

1> act upon the received IE "Intra-frequency cell info list"/"Inter-frequency cell info list"/"Inter-RAT cell info list" as described in subclause 8.6.7.3;

1> if any of the IEs "Intra-frequency measurement quantity", "Intra-frequency reporting quantity for RACH reporting", "Maximum number of reported cells on RACH" or "Reporting information for state CELL_DCH" are not included in the system information block:

2> read the corresponding IE(s) in system information block type 11 and use that information for the intra-frequency measurement.

1> if the IE "Inter-frequency RACH reporting information" is included in this system information block or in System Information Block type 11:

2> if the IE is not included in the system information block, read the corresponding IE(s) in System Information Block type 11;

2> use the received information for the inter-frequency measurements as specified in subclause 8.5.23.

1> if included in this system information block or in System Information Block type 11:

2> if no intra-frequency measurement in the variable MEASUREMENT_IDENTITY was set up or modified through a MEASUREMENT CONTROL message:

3> store the IE "Intra-frequency reporting quantity" and the IE "Intra-frequency measurement reporting criteria" or "Periodical reporting criteria" in order to activate reporting when state CELL_DCH is entered in the variable MEASUREMENT_IDENTITY. The IE "Cells for measurement" is absent for this measurement. The IE "Measurement Validity" is absent for this measurement after a state transition to CELL_DCH.

1> if the IE "Traffic volume measurement system information" is not included in this system information block:

2> read the corresponding IE in System Information Block type 11.

1> if the IE "Traffic volume measurement system information" was received either in this system information block or in System Information Block type 11:

2> if no traffic volume measurement with the measurement identity indicated in the IE "Traffic volume measurement system information" was set up or modified through a MEASUREMENT CONTROL message:

3> update the variable MEASUREMENT_IDENTITY with the measurement information received in that IE.

1> if in CELL_FACH state:

2> start or continue the traffic volume measurements stored in the variable MEASUREMENT_IDENTITY that are valid in CELL_FACH state.

1> if the IE "Cell selection and reselection info" is not included for a new neighbouring cell in the IE "Intra-frequency cell info list", the IE "Inter-frequency cell info list" or the IE "Inter-RAT cell info list" in System Information Block type 12:

2> use the default values specified for the IE "Cell selection and reselection info" for that cell except for the IE "HCS neighbouring cell information".

1> if the IE "Use of HCS" is set to "used", indicating that HCS is used, do the following:

3> use the default values specified for the IE "HCS neighbouring cell information" for that cell.

3> for that cell use the same parameter values as used for the preceding cell in the same cell info list in System Information Block type 12.

2> use the value of the IE from this System Information Block and ignore the value obtained from System Information Block type 3 or System Information Block type 4.

1> for FDD, determine the value for the READY_FOR_COMMON_ERGCH variable and take the corresponding actions as described in subclause 8.5.75.

If in idle mode, the UE shall not use the values of the IEs in this system information block.

8.1.1.6.13 System Information Block type 13

If in idle or connected mode, the UE should store all relevant IEs included in this system information block except for the IEs "CN domain specific DRX cycle length coefficient", "UE timers and constants in idle mode" and "Capability update requirement" which shall be stored only in the idle mode case. The UE shall read System Information Block type 13 and the associated System Information Block types 13.1, 13.2, 13.3 and 13.4 only when the UE is operating in "ANSI-41 mode" and the IE "PLMN type" in the Master Information Block has the value "ANSI-41" or "GSM-MAP and ANSI-41". The UE shall also:

1> forward the content of the IE "CN domain specific NAS system information" to the non-access stratum entity indicated by the IE "CN domain identity";

1> use the IE "CN domain specific DRX cycle length coefficient" to calculate frame number for the Paging Occasions and Page indicator as specified in [4].

Refer to TIA/EIA/IS-2000.5-A for actions on information contained in System Information Block types 13.1, 13.2, 13.3 and 13.4.

8.1.1.6.14 System Information Block type 14

This system information block type is used only in 3.84 Mcps TDD and 7.68 Mcps TDD.

The UE should store all relevant IEs included in this system information block. The UE shall:

1> use the IE "UL Timeslot Interference" to calculate PRACH, DPCH and PUSCH transmit power for TDD uplink open loop power control as defined in subclause 8.5.7.

8.1.1.6.15 System Information Block type 15

If the UE is in idle or connected mode, and supports GPS location services it should store all relevant IEs included in this system information block. The UE shall:

1> if the IE "GPS Data ciphering info" is included:

2> act as specified in the subclause 8.6.7.19.4.

1> act upon the received IE "Reference position" as specified in subclause 8.6.7.19.3.8;

1> act upon the received IE "GPS reference time" as specified in subclause 8.6.7.19.3.7;

1> if IE "Satellite information" is included:

2> act upon this list of bad satellites as specified in subclause 8.6.7.19.3.6.

NOTE: For efficiency purposes, the UTRAN should broadcast System Information Block type 15 if it is broadcasting System Information Block type 15.2.

8.1.1.6.15.0 System Information Block type 15bis

If the UE is in idle or connected mode, and supports GANSS location services it should store all relevant IEs included in this system information block. The UE shall:

1> act upon the received IE "Reference position" as specified in subclause 8.6.7.19.7.8;

1> act upon the received IE "GANSS reference time" as specified in subclause 8.6.7.19.7.7;

1> if IE "GANSS ionospheric model" is included:

2> act upon the received IE "GANSS ionospheric model" as specified in subclause 8.6.7.19.7.5.

1> if IE "GANSS additional ionospheric model" is included:

2> act upon the received IE "GANSS additional ionospheric model" as specified in subclause 8.6.7.19.7.12.

1> if IE "GANSS Earth orientation parameters" is included:

2> act upon the received IE "GANSS Earth orientation parameters" as specified in subclause 8.6.7.19.7.13.

8.1.1.6.15.1 System Information Block type 15.1

The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GPS_DATA. The UE shall:

1> act on "DGPS information" in the IE "DGPS Corrections" in a similar manner as specified in [13] except that the scale factors for PRC and RRC are different;

1> act upon the received IE "UE Positioning GPS DGPS corrections" as specified in subclause 8.6.7.19.3.3.

In this version of the specification, the UE shall:

1> ignore the following IEs: "Delta PRC2", "Delta RRC2", "Delta PRC3" and "Delta RRC3".

8.1.1.6.15.1a System Information Block type 15.1bis

This SIB has one occurrence for each GANSS supported. To identify the different GANSSs, the scheduling information for System Information Block type 15.1bis is associated with IE "GANSS ID". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> act on "DGANSS information" in the IE "DGANSS Corrections" in a similar manner as specified in [13] except that the scale factors for PRC and RRC are different;

1> act upon the received IE "UE Positioning DGANSS corrections" as specified in subclause 8.6.7.19.7.3.

8.1.1.6.15.1b System Information Block type 15.1ter

This SIB is for BDS only. If the UE supports BDS, then the UE shall:

1> if IE "UE positioning DBDS corrections" is included:

2> act upon the received IE "UE positioning DBDS corrections" as specified in subclause 8.6.7.19.7.17.

1> if IE "UE positioning BDS Ionospheric Grid Model" is included:

2> act upon the received IE "UE positioning BDS Ionospheric Grid Model" as specified in subclause 8.6.7.19.7.18.

8.1.1.6.15.2 System Information Block type 15.2

For System Information Block type 15.2 multiple occurrences may be used; one occurrence for one satellite. To identify the different occurrences, the scheduling information for System Information Block type 15.2 includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GPS_DATA. The UE shall:

1> compare for each occurrence the value tag of the stored occurrence, if any, with the occurrence value tag included in the IE "SIB occurrence identity and value tag" for the occurrence of the System Information Block with the same occurrence identity;

1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different:

2> store the occurrence information together with its identity and value tag for later use.

1> in case an occurrence with the same identity but different value tag was stored:

2> overwrite this one with the new occurrence read via system information for later use.

1> interpret IE "Transmission TOW" as a very coarse estimate of the current time, i.e., the approximate GPS time-of-week when the message is broadcast;

1> interpret IE "SatID" as the satellite ID of the data from which this message was obtained;

1> act upon the received IEs "Sat ID" and "GPS Ephemeris and Clock Corrections Parameter" as specified in subclause 8.6.7.19.3.4.

The IE "Transmission TOW" may be different each time a particular SIB occurrence is transmitted. The UTRAN should not increment the value tag of the SIB occurrence if the IE "Transmission TOW" is the only IE that is changed.

The UE may not need to receive all occurrences before it can use the information from any one occurrence.

8.1.1.6.15.2a System Information Block type 15.2bis

For System Information Block type 15.2bis multiple occurrences may be used; one occurrence for one satellite. To identify for which GANSS the occurrence is related to, the scheduling information for System Information Block type 15.2bis is associated with IE "GANSS ID". To identify the different occurrences within each GANSS, the scheduling information for System Information Block type 15.2bis includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different:

2> store the occurrence information together with its identity and value tag for later use.

1> in case an occurrence with the same identity but different value tag was stored:

2> overwrite this one with the new occurrence read via system information for later use.

1> act upon the received IEs "GANSS Navigation Model" as specified in subclause 8.6.7.19.7.4.

The UE may not need to receive all occurrences before it can use the information from any one occurrence.

8.1.1.6.15.2b System Information Block type 15.2ter

For System Information Block type 15.2ter multiple occurrences may be used; one occurrence for one satellite. To identify for which GANSS the occurrence is related to, the scheduling information for System Information Block type 15.2ter is associated with IE "GANSS ID". To identify the different occurrences within each GANSS, the scheduling information for System Information Block type 15.2ter includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different:

2> store the occurrence information together with its identity and value tag for later use.

1> in case an occurrence with the same identity but different value tag was stored:

2> overwrite this one with the new occurrence read via system information for later use.

1> act upon the received IE "GANSS additional navigation models" as specified in subclause 8.6.7.19.7.14.

The UE may not need to receive all occurrences before it can use the information from any one occurrence.

8.1.1.6.15.3 System Information Block type 15.3

For System Information Block type 15.3 multiple occurrences may be used; one occurrence for each set of satellite data. To identify the different occurrences, the scheduling information for System Information Block type 15.3 includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GPS_DATA. The UE shall:

1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different:

2> store the occurrence information together with its identity and value tag for later use.

1> in case an occurrence with the same identity but different value tag was stored:

2> overwrite this one with the new occurrence read via system information for later use.

1> interpret IE "Transmission TOW" as a very coarse estimate of the current time, i.e., the approximate GPS time-of-week when the message is broadcast;

1> if the IE "GPS Almanac and Satellite Health" is included:

2> interpret IE "SatMask" as the satellites that contain the pages being broadcast in this message;

2> interpret IE "LSB TOW" as the least significant 8 bits of the TOW [12];

2> act upon the received IE "GPS Almanac and Satellite Health" as specified in subclause 8.6.7.19.3.2.

1> if the IE "GPS ionospheric model" is included:

2> act upon the received IE "GPS ionospheric model" as specified in subclause 8.6.7.19.3.5.

1> if the IE "GPS UTC model" is included:

2> act upon the received IE "GPS UTC model" as specified in subclause 8.6.7.19.3.9.

The UE may not need to receive all occurrences before it can use the information for any one occurrence.

8.1.1.6.15.3a System Information Block type 15.3bis

For System Information Block type 15.3bis multiple occurrences may be used; one occurrence for each set of satellite data. To identify for which GANSS the occurrence is related to, the scheduling information for System Information Block type 15.3bis is associated with IE "GANSS ID". To identify the different occurrences within each GANSS, the scheduling information for System Information Block type 15.3bis includes IE "SIB occurrence identity and value tag". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> in case the UE has no SIB occurrence stored with the same identity or in case the occurrence value tag is different:

2> store the occurrence information together with its identity and value tag for later use.

1> in case an occurrence with the same identity but different value tag was stored:

2> overwrite this one with the new occurrence read via system information for later use.

1> if the IE "GANSS Almanac" is included:

2> act upon the received IE "GANSS Almanac" as specified in subclause 8.6.7.19.7.2.

1> if the IE "GANSS time model" is included:

2> act upon the received IE "GANSS time model" as specified in subclause 8.6.7.19.7.9.

1> if the IE "GANSS UTC model" is included:

2> act upon the received IE "GANSS UTC model" as specified in subclause 8.6.7.19.7.10.

1> if the IE "GANSS additional UTC models" is included:

2> act upon the received IE "GANSS additional UTC models" as specified in subclause 8.6.7.19.7.15.

1> if the IE "GANSS auxiliary information" is included:

2> act upon the received IE "GANSS auxiliary information" as specified in subclause 8.6.7.19.7.16.

The UE may not need to receive all occurrences before it can use the information for any one occurrence.

8.1.1.6.15.4 System Information Block type 15.4

If the UE is in idle mode or connected mode, the UE shall:

1> if the IE "OTDOA Data ciphering info" is included:

2> act as specified in subclause 8.6.7.19.4.

If the UE is in connected mode, the UE shall:

1> act as specified in subclause 8.6.7.19.2.

8.1.1.6.15.5 System Information Block type 15.5

If the UE is in idle or connected mode, the UE shall:

1> if the UE supports UE-based OTDOA positioning:

2> act as specified in subclause 8.6.7.19.2a.

8.1.1.6.15.6 System Information Block type 15.6

This SIB has one occurrence for each GANSS supported. To identify the different GANSSs, the scheduling information for System Information Block type 15.6 is associated with IE "GANSS ID". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> use IE "GANSS TOD" as a reference time for the data in IE "GANSS reference measurement information";

1> act upon the received IE "GANSS reference measurement information" as specified in subclause 8.6.7.19.7.1.

8.1.1.6.15.7 System Information Block type 15.7

This SIB has one occurrence for each GANSS supported. To identify the different GANSSs, the scheduling information for System Information Block type 15.7 is associated with IE "GANSS ID". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> act upon the received IE "GANSS data bit assistance" as specified in subclause 8.6.7.19.7.11.

8.1.1.6.15.8 System Information Block type 15.8

This SIB has one occurrence for each GANSS supported. To identify the different GANSSs, the scheduling information for System Information Block type 15.8 is associated with IE "GANSS ID". The UE should store all the relevant IEs included in this system information block in variable UE_POSITIONING_GANSS_DATA. The UE shall:

1> if the IE "GANSS Data ciphering info" is included:

2> act as specified in the subclause 8.6.7.19.4.

1> if the IE "GANSS real-time integrity" is included:

2> act upon the received IE " GANSS real-time integrity" as specified in subclause 8.6.7.19.7.6.

8.1.1.6.16 System Information Block type 16

If the IE "Uplink DPCH info Pre" is included in the PhyCH Information Elements for a predefined configuration the UE shall:

1> for FDD:

2> if the IE "Number of TPC bits" is not included:

3> use 2 TPC bits in the Uplink DPCH.

2> else:

3> if F-DPCH is not configured then the UE behaviour is unspecified.

For System Information Block type 16 multiple occurrences may be used; one occurrence for each predefined configuration. To identify the different predefined configurations, the scheduling information for System Information Block type 16 includes IE "Predefined configuration identity and value tag".

The UE should store all relevant IEs included in this system information block. The UE shall:

1> compare for each predefined configuration the value tag of the stored predefined configuration with the preconfiguration value tag included in the IE "Predefined configuration identity and value tag" for the occurrence of the System Information Block with the same predefined configuration identity;

1> in case the UE has no predefined configuration stored with the same identity:

2> store the predefined configuration information together with its identity and value tag for later use e.g. during handover to UTRAN.

1> in case a predefined configuration with the same identity but different value tag was stored:

2> overwrite this one with the new configuration read via system information for later use e.g. during handover to UTRAN.

The above handling applies regardless of whether the previously stored predefined configuration information has been obtained via UTRA or via another RAT.

The UE is not required to complete reading of all occurrences of System Information Block type 16 before initiating RRC connection establishment.

The UE is not required to store more than maxPredefConfig preconfigurations even in the case of multiple equivalent PLMNs.

8.1.1.6.17 System Information Block type 17

This system information block type is used only for TDD.

If in connected mode, the UE should store all relevant IEs included in this system information block. The UE shall:

1> if the IE "PDSCH system information" and/or the IE "PUSCH system information" is included, store each of the configurations given there with the associated identity given in the IE "PDSCH Identity" and/or "PUSCH Identity" respectively. This information shall become invalid after the time specified by the repetition period (SIB_REP) for this system information block.

If in idle mode, the UE shall not use the values of the IEs in this system information block.

8.1.1.6.18 System Information Block type 18

If the System Information Block type 18 is present, a UE shall obtain knowledge of the PLMN identity of the neighbour cells to be considered for cell reselection, and shall behave as specified in this subclause and in subclause 8.5.14a.

The UE should store all the relevant IEs included in this system information block.

A UE in idle mode shall act according to the following rules:

1> if System Information Block type 11ter is scheduled on BCH and the IE "Idle mode PLMN identities for SIB 11ter" is present:

2> any PLMN list of a given type (IEs "PLMNs of inter-frequency cells list" or "Multiple PLMNs of inter-frequency cells list") included in the IE "Idle mode PLMN identities for SIB 11ter" is paired with the list of cells of the same type derived from System Information Block type 11ter if scheduled on BCH.

1> if System Information Block type 11bis is scheduled on BCH; and the IE "Idle mode PLMN identities for SIB 11bis" is present:

2> any PLMN list of a given type (IEs "PLMNs of intra-frequency cells list" or "Multiple PLMNs of intra-frequency cells list", "PLMNs of inter-frequency cells list" or "Multiple PLMNs of inter-frequency cells list", "PLMNs of inter-RAT cell lists") included in the IE "Idle mode PLMN identities for SIB 11bis" is paired with the list of cells of the same type derived from System Information Block type 11 and System Information Block type 11bisif scheduled on BCH.

1> else:

2> any PLMN list of a given type (IEs "PLMNs of intra-frequency cells list" or "Multiple PLMNs of intra-frequency cells list", "PLMNs of inter-frequency cells list" or "Multiple PLMNs of inter-frequency cells list", "PLMNs of inter-RAT cell lists") included in the IE "Idle mode PLMN identities" is paired with the list of cells of the same type derived from System Information Block type 11 and System Information Block type 11bis if scheduled on BCH.

1> the PLMN identity located at a given rank in the PLMN list is that of the cell with the same ranking in the paired list of cells, the cells being considered in the increasing order of their associated identities ("Intra-frequency cell id", "Inter-frequency cell id", "Inter-RAT cell id");

1> if no identity is indicated for the first PLMN in a list, the UE shall assume that the neighbouring cell broadcasts the same PLMN configuration (i.e. IE "PLMN Identity" and IE "Multiple PLMN List") as the current cell;

1> if no identity is indicated for another entry in the list, the UE shall assume that the neighbouring cell broadcasts the same PLMN configuration (i.e. IE "PLMN Identity" and IE "Multiple PLMN List") as the previous cell in the list;

1> if the number of identities in a PLMN list exceeds the number of neighbour cells in the paired list (if any), the extra PLMN identities are considered as unnecessary and ignored;

1> if the number of identities in a PLMN list (if any) is lower than the number of neighbour cells in the paired list, the missing PLMN identities are replaced by the PLMN configuration for the last cell in the list.

A UE in connected mode shall act in the same manner as a UE in idle mode with the following modifications:

1> if System Information Block type 11ter is scheduled on BCH:

2> the PLMN lists to be considered are the ones included, when present, in the IE "Connected mode PLMN identities for SIB 11ter";

2> otherwise, the UE shall use, in place of any missing list, when present, the corresponding one in the IE "Idle mode PLMN identities for SIB 11ter".

1> if System Information Block type 11bis is scheduled on BCH:

2> the PLMN lists to be considered are the ones included, when present, in the IE "Connected mode PLMN identities for SIB 11bis";

2> otherwise, the UE shall use, in place of any missing list, when present, the corresponding one in the IE "Idle mode PLMN identities for SIB11bis";

2> otherwise, the UE shall use, in place of any missing list, when present, the corresponding one in the IE "Connected mode PLMN identities";

2> otherwise, the UE shall use, in place of any missing list, the corresponding one in the IE "Idle mode PLMN identities".

1> else:

2> the PLMN lists to be considered are the ones included, when present, in the IE "Connected mode PLMN identities";

2> otherwise, the UE shall use, in place of any missing list, the corresponding one in the IE "Idle mode PLMN identities".

1> the paired lists of cells are the ones derived from System Information Block type 11, System Information Block type 11bis and System Information Block type 11ter, if scheduled on BCH, and System Information Block type 12 if present.

If both the IEs "PLMNs of intra-frequency cells list" and "Multiple PLMNs of intra-frequency cells list" are included or if both the IEs "PLMNs of inter-frequency cells list" and "Multiple PLMNs of inter-frequency cells list" are included:

1> the UE behaviour is not specified.

8.1.1.6.19 System Information Block type 19

1> if the value of the IE "Priority status" in the variable PRIORITY_INFO_LIST equals "dedicated_priority":

2> clear every stored value of "Threshx_{, high}", "Thresh_{x, low}", "Threshx_{, high2}", "Thresh_{x, low2}" , "EUTRA-RSRQ-offsetWB" and "EUTRA-RSRQOnAllSymbolsO ffset" in every occurrence of the IE "Priority Info List" in the variable PRIORITY_INFO_LIST.

1> otherwise:

2> clear the variable PRIORITY_INFO_LIST.

1> clear the variable EUTRA_FREQUENCY_INFO_LIST;

1> act upon the received IE "UTRA priority info list" as described in subclause 8.6.7.3a;

1> if the IE "GSM priority info list" is present:

2> act upon the received IE as described in subclause 8.6.7.3b.

1> if the IE "E-UTRA frequency and priority info list" is present:

2> act upon the received IE as described in subclause 8.6.7.3c.

1> if the IE "E-UTRA frequency RACH reporting information" is present; and

1> if the UE supports E-UTRA RACH reporting:

2> store the IE "E-UTRA frequency RACH reporting information" into the variable EUTRA_FREQUENCY_INFO_LIST_FACH and act upon the received IE as described in subclause 8.5.23.

8.1.1.6.20 System Information Block type 20

If the cell is not operating in MBSFN mode according to subclause 8.1.1.6.3, the UE shall:

1> if the IE "HNB Name" is present:

2> forward the content of IE "HNB Name" to the upper layers.

8.1.1.6.21 System Information Block type 21

The EAB capable UE should store all relevant IEs included in this system information block. If the IE "EAB Parameters" is included, the EAB capable UE shall:

1> if the IE "EAB Parameters For All" is included in the IE "EAB Parameters":

2> select the IE "EAB Parameters For All".

1> else:

2> select the entry in the IE "EAB Parameters Per PLMN List" in the IE "EAB Parameters" corresponds to the PLMN chosen by the UE.

1> if in idle mode:

2> if the IE "CS Domain Specific EAB parameters" or the IE "Common EAB parameters" is included in the selected Domain Specific EAB Parameters:

3> act on the IE "EAB Access Class Barred List" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the CS domain, if upper layers indicate that the connection request is subject to EAB and the UE belongs to the category of UEs as indicated in the IE "EAB Category".

2> if the IE "PS Domain Specific EAB parameters" or the IE "Common EAB parameters" is included in the selected Domain Specific EAB Parameters:

3> act on the IE "EAB Access Class Barred List" when initiating RRC Connection establishment to send an INITIAL DIRECT TRANSFER message to the PS domain, if upper layers indicate that the connection request is subject to EAB and the UE belongs to the category of UEs as indicated in the IE "EAB Category".

1> if in connected mode:

2> store the selected Domain Specific EAB Parameters to the variable "EAB_PARAM" upon transition to RRC connected and maintain the variable until it is cleared, the PLMN chosen by the UE is changed or the RRC connection is released;

2> if the IE "CS Domain Specific EAB parameters" or the IE "Common EAB parameters" is included in the stored Domain Specific EAB Parameters in variable "EAB_PARAM":

3> act on the IE "EAB Access Class Barred List" when initiating an INITIAL DIRECT TRANSFER message to the CS domain, if upper layers indicate that the connection request is subject to EAB and the UE belongs to the category of UEs as indicated in the IE "EAB Category" and signalling connection to the PS domain is already established.

2> if the IE "PS Domain Specific EAB parameters" or the IE "Common EAB parameters" is included in the stored Domain Specific EAB Parameters in variable "EAB_PARAM":

3> act on the IE "EAB Access Class Barred List" when initiating an INITIAL DIRECT TRANSFER message to the PS domain, if upper layers indicate that the connection request is subject to EAB and the UE belongs to the category of UEs as indicated in the IE "EAB Category" and signalling connection to the CS domain is already established.

8.1.1.6.22 System Information Block type 22

The UE should store all relevant IEs included in this system information block.

8.1.1.6.23 System Information Block type 23

The UE that supports RAN-assisted WLAN interworking should store all relevant IEs included in this system information block. The UE that supports RAN-assisted WLAN interworking shall:

1> if the IE "WLAN Offload Information Per PLMN List" is included:

2> select the instance in the IE "WLAN Offload Information Per PLMN List" corresponding to the PLMN chosen by the UE.

1> else:

2> select the instance in the IE "WLAN Offload Information common for all PLMN".

1> store the received information elements of the selected instance in the variable SYSTEM_INFO_WLAN_OFFLOAD_INFO, clearing and replacing any previously stored information;

1> if the UE is in Idle mode, CELL_PCH, URA_PCH, or CELL_FACH state; and

1> if the variable WLAN_OFFLOAD_INFO is empty:

2> use the information stored in the variable SYSTEM_INFO_WLAN_OFFLOAD_INFO as specified in [4], and forward it to the upper layers.

8.1.1.6.24 System Information Block type 24

The UE should read and store all relevant IEs included in this system information block in the variable CONNECTED_MODE_ACCESS_CONTROL.

The UE shall:

1> if in CELL_FACH state:

2> if the n-th Bit in the IE "DTCH transmission blocked" in the variable CONNECTED_MODE_ACCESS_CONTROL is changed from 0 to 1, where n is the value stored in the IE "Access Group identity" in the variable CONNECTED_MODE_ACCESS_CONTROL:

3> configure RLC entities mapped onto the logical channel DTCH to not submit any data PDUs to lower layers.

2> else:

3> if the n-th Bit in the IE "DTCH transmission blocked" in the variable CONNECTED_MODE_ACCESS_CONTROL is changed from 1 to 0, where n is the value stored in the IE "Access Group identity" in the variable CONNECTED_MODE_ACCESS_CONTROL:

4> configure RLC entities mapped onto the logical channel DTCH to allow submitting data PDUs to lower layers.

1> if in CELL_PCH state or URA_PCH state:

3> not trigger a measurement report procedure or not initiate the cell update procedure with cell update cause "uplink data transmission".

NOTE: Measurement report and cell update procedures that are triggered by uplink RLC control PDU are permitted.

8.1.1.6.25 System Information Block type 25

The ACDC capable UE should store all relevant IEs included in this system information block in the variable ACDC_ACCESS_CONTROL.

The ACDC capable UE shall:

1> if the IE "ACDC Parameters For All" is included in the IE "ACDC Parameters":

2> if the PLMN chosen by the UE is the Home PLMN; or

2> if the PLMN chosen by the UE is not the Home PLMN and the "ACDC applicable for Roamer" IE is present:

3> in case of no ACDC category is indicated by upper layer, or in case that the ACDC category indicated by upper layers has no matching ACDC barring information in System Information Block type 25, act as if the ACDC category is equal to the lowest ACDC category broadcasted in System Information Block type 25;

3> when initiating an RRC Connection establishment to the PS domain, if the access for the ACDC category indicated by upper layers is barred according to the IE "ACDC Information", as specified in [4], indicate to upper layers that the access barring is due to ACDC;

3> if the access for the ACDC category indicated by upper layers is changed from barred to not barred, act on the IE "ACDC-ACB-barringBitmap" when initiating an RRC Connection establishment to the PS domain.

1> else:

2> select the entry in the IE "ACDC Parameters Per PLMN List" in the IE "ACDC Parameters" which corresponds to the PLMN chosen by the UE;

2> if the chosen PLMN is the Home PLMN of the UE; or

2> if the PLMN chosen by the UE is not the Home PLMN and the "ACDC applicable for Roamer" IE is present:

3> when initiating an RRC Connection establishment to the PS domain, if the ACDC category indicated by upper layers is barred according to the IE "ACDC Information", as specified in [4], indicate to upper layers that the access barring is due to ACDC;

For the ACDC capable UE, if ACDC access barring is configured, DSAC (PS domain) and ACB will be ignored.

8.1.1.7 Modification of system information

For System Information Block type 15.2, 15.3 and 16 that may have multiple occurrences, the UE shall handle each occurrence independently as specified in the previous; that is each occurrence is handled as a separate system information block.

NOTE: It should be noted that for the proper operation of the BCCH Modification Information sent on a PCH or on an HS-DSCH (FDD and 1.28 Mcps TDD only), the System Information should not be changed more frequently than can be accommodated by mobile stations operating at the maximum DRX cycle length supported by the UTRAN.

8.1.1.7.1 Modification of system information blocks using a value tag

Upon modifications of system information blocks using value tags on system information broadcast channel, UTRAN should notify the new value tag for the master information block in the IE "BCCH modification info". Upon modifications of system information blocks using value tags on second system information broadcast channel, UTRAN should notify the new value tag for the Scheduling Block 3 in the IE "BCCH modification info". The notification is 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;

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;

If both the IE "ETWS information" and the IE "BCCH modification info" are present in a PAGING TYPE 1, an ETWS capable UE in idle mode shall:

1> if the value of IE "MIB value tag" in the IE "BCCH modification info" is different from the value tag stored in the variable VALUE_TAG:

2> set the variable BCCH_MODIFICATION_ACCESS_PROHIBITION to TRUE;

2> prohibit any RRC connection establishment attempt according to 8.1.8.2.

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.

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

8.1.1.7.2 Synchronised modification of system information blocks

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 or scheduling block 3 in the IE "BCCH modification info" transmitted in the following way:

1> To reach UEs in idle mode, CELL_PCH state and URA_PCH state, 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_FACH state or TDD UEs in CELL_DCH with SCCPCH 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. For 1.28 Mcps TDD, the BCCH is transmitted on frequencies where CELL_FACH state UEs stay and UE detects the BCCH specific H-RNTI on its working frequency.

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 subclause 8.1.1.7.3 at the time, indicated in the IE "BCCH Modification Info".

8.1.1.7.3 Actions upon system information change

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 subclause 8.1.1.5.

2> if the value tag of the master information block in the system information is the same as the value tag stored in the variable VALUE_TAG:

3> for the next occurrence of the master information block:

4> perform actions as specified in subclause 8.1.1.7.3 again.

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

3> perform actions as specified in subclause 8.1.1.5;

3> if (VTCI-VTMIB) mod 8 < 4, where VTCI is the value tag in the IE "MIB value tag" in "BCCH modification info" and VTMIB is the value tag of the master information block in the system information:

4> for the next occurrence of the master information block:

5> perform actions as specified in subclause 8.1.1.7.3 again.

1> compare the value of IE "SB3 value tag" if present in the IE "BCCH modification info" with the value tag stored for the scheduling block 3 in variable VALUE_TAG;

1> if the value tags differ:

2> acquire Scheduling Block 3 (SB3) on the second system information broadcast channel.

8.1.1.7.4 Actions upon expiry of a system information expiry timer

When the expiry timer of a system information block not using a value tag expires

the UE shall:

1> consider the content of the system information block invalid;

1> re-acquire the system information block again before the content can be used.

In FDD for system information blocks other than System Information Block type 7, or in states other than CELL_FACH, or in state CELL_FACH and in the second DRX cycle after expiry of T329 as specified in subclause 8.5.49b; or

In TDD for system information blocks other than System Information Block type 14, or in states other than CELL_FACH or CELL_DCH:

the UE may:

1> postpone reading the system information block until the content is needed.

In FDD for System Information Block type 24:

1> if the UE in CELL_FACH state, CELL_PCH state or URA_PCH state:

2> if the UE does not have a value stored in the IE "Access Group identity" in variable CONNECTED_MODE_ACCESS_CONTROL; or

2> the UE does not have data to transmit:

3> the UE shall not re-acquire the system information block.

2> else

3> if the UE has a value stored in the IE "Access Group identity" in variable CONNECTED_MODE_ACCESS_CONTROL; and

3> if the UE is in CELL_FACH state, CELL_PCH state or URA_PCH state:

4> the UE may postpone reading the system information block until it has data to transmit.

In FDD for System Information Block type 25:

1> if the UE in Idle mode:

2> the UE may postpone reading the system information block until upper layers requests the establishment of a signalling connection towards the PS domain.

1> else:

2> the UE shall not re-acquire the system information block.

In FDD for System Information Block type 7, while in state CELL_FACH and not in the second DRX cycle after expiry of T329 as specified in subclause 8.5.49b, and in TDD for System Information Block type 14, while in state CELL_FACH or CELL DCH the UE shall always keep an up to date version of the relevant IEs, unless this is not possible because system information can not be received due to bad radio conditions or the UE uses System Information Block type 7 in the variable SYSTEM_INFORMATION_CONTAINER.

8.1.1.8 Reception of System Information Container by the UE

If the UE was redirected from a different RAT:

1> if the UE receives the System Information Container message corresponding to a cell, on which UE is camped after a cell selection procedure triggered by the redirection procedure:

2> the UE may store the System Information Container message into variable SYSTEM_INFORMATION_CONTAINER and use the stored master information block, scheduling blocks and system information blocks in the variable SYSTEM_INFORMATION_CONTAINER until the variable is cleared, and act as if this system information was scheduled on BCCH of this cell.

NOTE: The UE may assume that the System Information Container contains a set of system information, such that no reception of system information is needed on the cell where the UE is camped after a cell selection procedure triggered by the redirection procedure.