8.1.10 Broadcast of system information

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

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

8.1.10.1 Dynamic change of segmentation, concatenation & scheduling and handling of unsupported information blocks

8.1.10.1.1 Definition

8.1.10.1.2 Conformance requirement

1. 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.

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

……..

– read and store the IEs of that system information block;

NOTE: There are options with and without scheduling blocks.

3. For system information blocks, not supported by the UE…….

– skip reading this system information block;

– skip monitoring changes to this system information block.

4. 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.

Reference

3GPP TS 25.331 clause 8.1.1.1.4, 8.1.1.5 and 8.1.1.6.

8.1.10.1.3 Test Purpose

1. To verify that dynamic change of System Information is identified, new information read and used.

2. To verify that the UE can support all segment types and "all" segment combinations.

3. To verify that the UE can dynamically use different configurations

4. To verify that the UE properly uses combinations of Default and assigned values.

NOTE: There are 4 segment types and 11 different SYSTEM INFORMATION segment combinations to interpret when re-assembling segments. There are many alternative SIB position offsets and repetition rates.

The allowed segment types are:

– First segment

– Subsequent segment

– Last segment

– Complete

The allowed segment combinations are:

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 (not fully tested)

11. Last segment of size 215 to 222

NOTE: Segment combinations 10 and 11 are more difficult to test as they require SIBs of a very specific size.

8.1.10.1.4 Method of test

Alternate two sets of System Information and generate a call after one or the other set has been broadcasted.

These two sets of System Information are based on the System Information specified in 34.108, section 6.

A "Minimum" configuration and a "Maximum" configuration of System Information are defined. The "Minimum" configuration does not contain all of the Information Blocks defined for Configuration 1 in section 6 of 34.108. On the other hand the "Maximum" configuration, defined by the scheduling information in Table 2, contains extra optional information blocks to ensure that the SIB configuration is consistent with the defined scheduling The contents of the SIBs remains the same (the contents of SIB11 changes for the "Maximum" configuration) while the contents of the MIB and SB is altered depending on the nature of the test, i.e. the schedule changes between the "Minimum" and "Maximum" configurations.

The four segment types and the eleven segment combinations are tested using the two configurations.

NOTE: The decoding of system information in the UE is only measurable by functional tests. A large number of functions utilize system information. An extensive test of the system information decoding thus creates a large number of functional tests, which is impractical. This test specification uses a "sample test", where only a few functions are invoked.

Initial Condition

System Simulator: 2 cells (Cell 1, Cell 2), settings for Cell 1 and Cell 2 according to TS 34.108, clause 6.1.5, table 6.1.2 (Cell 1 configured as the serving cell). The Minimum Configuration System Information is being broadcast in Cell 1. The Maximum Configuration System Information is being broadcast in Cell 2.

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

Test procedure

Table 8.1.10.1-1 illustrates the downlink power to be applied for the 2 cells.

Table 8.1.10.1-1

Parameter	Unit	Cell 1		Cell 2
Parameter	Unit	T0	T1	T0	T1
UTRA RF Channel Number		Mid Range Test Frequency		Mid Range Test Frequency
CPICH Ec	dBm/3.84 MHz	-60	-60	OFF	-60
P-CCPCH RSCP (TDD)	dBm	-60	-60	OFF	-60

Columns marked T0 denote the initial conditions.

The UE is in C1 in Camped Normally state. UE starts establishing a MO call/session. SS disconnects the call. UE shall enter IDLE state. The SS waits for a 2 sec interval and then sets the Cell Barred Indicator in SIB3 to "Barred". The SS notifies the UE of the changed System Information by sending the Paging Type 1 message including the IE BCCH Modification Info indicating that new System Information is available. SS applies the downlink power settings, according to the values in the columns “T1” of table 8.1.10.1-1. Based on the updated information in SIB3, the UE performs a cell reselection to Cell 2. The UE reads the System Information in Cell 2, i.e. Maximum Configuration System Information. UE starts establishing a MO call/session.

NOTE: If the UE fails the test because of a failure to reselect to a right cell, then the operator may re-run the test.

Expected sequence

Step	Direction		Message	Comment
	UE	SS
1	UE			Mobile originated call/session establishment
2	SS			Disconnection of call
2a	SS			SS waits for a 2 second to allow UE to enter Idle state.
3			System Information (Minimum Configuration)	System Information message is sent in Cell 1 with the Cell Barred Indicator in SIB3 set to "Barred".
3a			Void	SS applies the downlink power settings, according to the values in the columns “T1” of table 8.1.10.1-1
4			Paging Type 1	This message is to inform the UE in Idle State that System Information has been updated.
5	UE			Mobile originated call /session establishment
6			CALL C.3	If the test result of C.3 indicates that UE is in CELL_DCH state, the test passes, otherwise it fails.

Specific message content for "Minimum" configuration

The Minimum configuration is the same as the Configuration 1 System Information on 34.108, section 6 with some differences:

– Only SIB1, SIB3, SIB5/SIB5bis, SIB7, SIB11 are used, i.e. the Minimum number of SIBs is used.

– No SB is used; all scheduling information is contained in the MIB. The contents of this changed MIB are shown below.

– A different schedule is used. Details below.

– SIB11 lists eight cells (one serving cell and seven neighbouring cells). Only the first two of these are considered relevant.

Other characteristics of the Minimum configuration are:

– An unknown future System Information Block (SIB-F1) is included. SIB-F1 is used to test segment combination 10. However, it should be noted that, based on the scheduling information in the MIB, UEs may decide not to read segment combinations associated with SIBs that they do not support/comprehend. Hence, the use of SIB-F1 does not fully cover the verification of combinations 10. The tests really just verify that UE ignores it. There is no real verification that the UE can support segment combinations 10.

The following tables show (based on SIB_REP and SIB_POS in the MIB and SB) the schedule used for the Minimum configuration.

Table 1: The schedule in this table incorporates segment combinations 1, 2, 3, 4, 7, 8, 10.

Block

Type

MIB

SIB1

SIB3

SIB5/SIB5bis

SIB7

SIB11

SIB_REP

SEG_
COUNT

Frame No / SIB_POS	0	2	4	6	8	10	12	14
Block Type	MIB		SIB7		MIB

Frame No / SIB_POS	16	18	20	22	24	26	28	30
Block Type	MIB		SIB7/SIB3	SIB1	MIB		SIB-F1	SIB5 / SIB5bis

Frame No / SIB_POS	32	34	36	38	40	42	44	46
Block Type	MIB	SIB5/SIBbis	SIB5/SIB5bis/SIB7/SIB11	SIB11	MIB	SIB11

Frame No / SIB_POS	48	50	52	54	56	58	60	62
Block Type	MIB		SIB7		MIB

Table 1a: The schedule in this table incorporates segment combinations 1, 2, 3, 4, 7, 8, 10 (1.28Mcps TDD).

Block

Type

MIB

SIB1

SIB3

SIB5/SIB5bis

SIB7

SIB11

SIB_REP

SEG_
COUNT

Frame No / SIB_POS	0	2	4	6	8	10	12	14
Block Type	MIB		SIB7		MIB

Frame No / SIB_POS	16	18	20	22	24	26	28	30
Block Type	MIB		SIB7/SIB3	SIB1	MIB		SIB-F1	SIB5 / SIB5bis

Frame No / SIB_POS	32	34	36	38	40	42	44	46
Block Type	MIB	SIB5/SIBbis	SIB5/SIB5bis/SIB7	SIB11	MIB	SIB11	SIB5	SIB5

Frame No / SIB_POS	48	50	52	54	56	58	60	62
Block Type	MIB		SIB7		MIB			SIB11

Contents of Master Information Block PLMN type is the case of GSM-MAP

– MIB value tag	A valid MIB value tag as defined in TS 25.331
– Supported PLMN types
– PLMN type	GSM-MAP
– PLMN identity
– MCC digit	Set to the same Mobile Country Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– MNC digit	Set to the same Mobile Network Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– ANSI-41 Core Network information	Not Present
– References to other system information blocks and scheduling blocks
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	PLMN Value tag
– PLMN Value tag	A valid PLMN value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	22
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 1
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	20
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 3
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	30
– SIB_POS offset info
– SIB_OFF	4
– SIB_OFF	2
– SIB type	System Information Type 5 / System Information Type 5bis
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	16
– SIB_POS	4
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type 7
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	36
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	4
– SIB and SB type	System Information Type 11
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	28
– SIB_POS offset info	Not Present – use default
– SIB and SB type	System Information Type F1

Contents of Master Information Block PLMN type is the case of GSM-MAP (1.28Mcps TDD)

– MIB value tag	A valid MIB value tag as defined in TS 25.331
– Supported PLMN types
– PLMN type	GSM-MAP
– PLMN identity
– MCC digit	Set to the same Mobile Country Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– MNC digit	Set to the same Mobile Network Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– ANSI-41 Core Network information	Not Present
– References to other system information blocks and scheduling blocks
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	PLMN Value tag
– PLMN Value tag	A valid PLMN value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	22
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 1
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	20
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 3
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	5
– SIB_REP	64
– SIB_POS	30
– SIB_POS offset info
– SIB_OFF	4
– SIB_OFF	2
– SIB_OFF	8
– SIB_OFF	2
– SIB type	System Information Type 5 / System Information Type 5bis
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	16
– SIB_POS	4
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type 7
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	38
– SIB_POS offset info
– SIB_OFF	4
– SIB_OFF	20
– SIB and SB type	System Information Type 11
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	28
– SIB_POS offset info	Not Present – use default
– SIB and SB type	System Information Type F1

Contents of System Information Block type 5 (FDD)

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

– PRACH partitioning	A1, A2, A3
– Access Service Class
– ASC Setting		Not Present
– ASC Setting
– CHOICE mode		FDD
– Available signature Start Index		0 (ASC#1)
– Available signature End Index		7 (ASC#1)
– Assigned Sub-Channel Number		‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting		Not Present
– ASC Setting		Not Present
– ASC Setting		Not Present
– ASC Setting		Not Present
– ASC Setting		Not Present
– ASC Setting		Not Present

Condition	Explanation
A1	Band I, Band II, Band III
A2	Band V, Band VI, Band VII
A3	Band VIII & bands beyond Band X

Contents of System Information Block type 5bis (FDD)

The message structure of the System information block type 5bis should be the same as System information block type 5 defined above with the following exceptions as given below.

– Frequency Band Indicator	A1	FDD Band under test
– Frequency Band Indicator 2		Not Present
– Frequency Band Indicator	A2	Extension indicator
– Frequency Band Indicator 2		FDD Band under test

Condition	Explanation
A1	Band IV
A2	Band IX & Band X

Contents of System Information Block type 11

Use the same message type found in clause 6.1 of TS 34.108, with the exception of event 1a being disabled.

Specific message content for "Maximum" configuration

The Maximum configuration is the same as the Configuration 1 System Information on 34.108, section 6 with some differences:

– A different schedule is used. Details below.

– SIB11 lists eight cells (one serving cell and seven neighbouring cells). Only the first two of these are considered relevant. It should also include some of the optional IE’s to fit the scheduling information for maximum configuration.

– SIB6 and SIB12 includes some of the optional IEs even if having same values as correspondent IEs in SIB5 and SIB11 respectively (to facilitate implementation of the test case for the Maximum configuration) to fit the scheduling information for maximum configuration.

Other characteristics of the Maximum configuration are:

– one "unknown future" block (SIB-F2) is included. This SIB is concatenated with another SIB and is used to verify that the UE can receive an Information Block that it does not support and still process the Information Blocks that it does support in the correct way.

– The test of the segment combination 9 is verified if the UE is able to read SIB7 and the first segment of SIB5 in position 4.

– The test of the segment combination 11 is verified if the UE is able to read the last segment of SIB 5 / SIB 5bis. The SS ensures that this last segment shall have the length between 215 and 222 bits. Depending on the length of SIB 5 / SIB 5bis, the combination 11 occurs either in SIB_position 6, or in the most cases in SIB_position 10

The following tables show (based on SIB_REP and SIB_POS in the MIB and SB) the schedule used for the Maximum configuration.

Table 2: The schedule in this table incorporates segment combinations 1, 2, 3, 5, 6, 8, 9, 11.

Block

Type

MIB

SB1

SIB1

SIB2

SIB3

SIB4

SIB5/SIB5bis

SIB6

SIB7

SIB11

SIB12

SIB18

SIB_REP

SEG_
COUNT

Frame No / SIB_POS	0	2	4	6	8	10	12	14
Block Type	MIB	SB1	SIB7/ SIB5	SIB5/SIB5bis	MIB	SIB5	SIB3/SIB-F2	SIB11

Frame No / SIB_POS	16	18	20	22	24	26	28	30
Block Type	MIB	SB1	SIB11	SIB11	MIB	SIB11/SIB12	SIB12	SIB12

Frame No / SIB_POS	32	34	36	38	40	42	44	46
Block Type	MIB	SB1	SIB7/SIB18	SIB12	MIB	SIB6	SIB6	SIB6/SIB2

Frame No / SIB_POS	48	50	52	54	56	58	60	62
Block Type	MIB	SB1	SIB4		MIB	SIB1

Table 2a: The schedule in this table incorporates segment combinations 1, 2, 3, 5, 6, 8, 9, 11 (1.28Mcps TDD).

Block

Type

MIB

SB1

SIB1

SIB2

SIB3

SIB4

SIB5/SIB5bis

SIB6

SIB7

SIB11

SIB12

SIB18

SIB_REP

SEG_
COUNT

Frame No / SIB_POS	0	2	4	6	8	10	12	14
Block Type	MIB	SB1	SIB7/ SIB5	SIB5/SIB5bis	MIB	SIB5	SIB3/SIB-F2	SIB11

Frame No / SIB_POS	16	18	20	22	24	26	28	30
Block Type	MIB	SB1	SIB11	SIB11	MIB	SIB11/SIB12	SIB5	SIB5

Frame No / SIB_POS	32	34	36	38	40	42	44	46
Block Type	MIB	SB1	SIB7/SIB18	SIB12	MIB	SIB6	SIB6	SIB6/SIB2

Frame No / SIB_POS	48	50	52	54	56	58	60	62
Block Type	MIB	SB1	SIB12	SIB12	MIB	SIB1/SIB4	SIB6	SIB6

Contents of Master Information Block PLMN type is the case of GSM-MAP

Information Element	Value/remark
– MIB value tag	A valid MIB value tag as defined in TS 25.331
– Supported PLMN types
– PLMN type	GSM-MAP
– PLMN identity
– MCC digit	Set to the same Mobile Country Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– MNC digit	Set to the same Mobile Network Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– ANSI-41 Core Network information	Not Present
– References to other system information blocks and scheduling blocks
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	Cell Value Tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– Scheduling
– SEG_COUNT	1
– SIB_REP	16
– SIB_POS	2
– SIB_POS offset info	Not Present – use default
– SIB type	Scheduling Block 1
– Scheduling information
– CHOICE Value tag	PLMN Value tag
– PLMN Value tag	A valid PLMN value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	58
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 1
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	46
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 2
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	12
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 3
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	52
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 4
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	4
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	4
– SIB type	System Information Type 5 / System Information Type 5bis

Contents of Master Information Block PLMN type is the case of GSM-MAP (1.28Mcps TDD)

Information Element	Value/remark
– MIB value tag	A valid MIB value tag as defined in TS 25.331
– Supported PLMN types
– PLMN type	GSM-MAP
– PLMN identity
– MCC digit	Set to the same Mobile Country Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– MNC digit	Set to the same Mobile Network Codes stored in the test USIM card (TS 34.108 clause 8.3.2.2 EF IMSI(IMSI)).
– ANSI-41 Core Network information	Not Present
– References to other system information blocks and scheduling blocks
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	Cell Value Tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– Scheduling
– SEG_COUNT	1
– SIB_REP	16
– SIB_POS	2
– SIB_POS offset info	Not Present – use default
– SIB type	Scheduling Block 1
– Scheduling information
– CHOICE Value tag	PLMN Value tag
– PLMN Value tag	A valid PLMN value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	58
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 1
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	46
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 2
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	12
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 3
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	58
– SIB_POS offset info	Not Present – use default
– SIB type	System Information Type 4
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	5
– SIB_REP	64
– SIB_POS	4
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	4
– SIB_OFF	18
– SIB_OFF	2
– SIB type	System Information Type 5 / System Information Type 5bis

Contents of Scheduling Block 1 (FDD)

Information Element	Value/remark
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	42
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	2
– SIB and SB type	System Information Type 6
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	32
– SIB_POS	4
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type 7
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	4
– SIB_REP	64
– SIB_POS	14
– SIB_POS offset info
– SIB_OFF	6
– SIB_OFF	2
– SIB_OFF	4
– SIB and SB type	System Information Type 11
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	4
– SIB_REP	64
– SIB_POS	26
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	2
– SIB_OFF	8
– SIB and SB type	System Information Type 12
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	36
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type 18
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	12
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type F2

Contents of Scheduling Block 1 (1.28 Mcps TDD)

Information Element	Value/remark
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	5
– SIB_REP	64
– SIB_POS	42
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	2
– SIB_OFF	14
– SIB_OFF	2
– SIB and SB type	System Information Type 6
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	32
– SIB_POS	4
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type 7
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	4
– SIB_REP	64
– SIB_POS	14
– SIB_POS offset info
– SIB_OFF	6
– SIB_OFF	2
– SIB_OFF	4
– SIB and SB type	System Information Type 11
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	4
– SIB_REP	64
– SIB_POS	26
– SIB_POS offset info
– SIB_OFF	12
– SIB_OFF	14
– SIB_OFF	2
– SIB and SB type	System Information Type 12
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	36
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type 18
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	12
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type F2

Contents of Scheduling Block 1 (TDD 3.84 Mcps option and TDD 7.68 Mcps option)

Information Element	Value/remark
– References to other system information blocks
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	4
– SIB_REP	128
– SIB_POS	3
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	2
– SIB and SB type	System Information Type 6
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	16
– SIB_POS	2
– SIB_POS offset info	Not Present
– SIB type SIBs only	System Information Type 7
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	29
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	2
– SIB and SB type	System Information Type 11
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	3
– SIB_REP	64
– SIB_POS	13
– SIB_POS offset info
– SIB_OFF	2
– SIB_OFF	2
– SIB and SB type	System Information Type 12
– Scheduling information
– CHOICE Value tag	Cell Value tag
– Cell Value tag	A valid Cell value tag as defined in TS 25.331
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	54
– SIB_POS offset info	Not Present
– SIB type SB	System Information Type 18
– Scheduling information
– CHOICE Value tag	Not Present
– SEG_COUNT	1
– SIB_REP	64
– SIB_POS	6
– SIB_POS offset info	Not Present
– SIB and SB type	System Information Type F2

Contents of System Information Block type F1

Information Element	Value/remark
Data	Arbitrary data with a size of 226 bits

Contents of System Information Block type F2

Information Element	Value/remark
Data	Arbitrary data with a size of 50 bits

NOTE: For these future System Information Block types one of the available spare values for SIB type should be used

Contents of SYSTEM INFORMATION BLOCK TYPE 6 (FDD)

– PICH Power offset	-5 dB
– CHOICE Mode	FDD
– AICH Power offset	-5 dB
– Primary CCPCH info	present
– PRACH system information list
– PRACH system information
– PRACH info
– CHOICE mode	FDD
– Available Signature	‘0000 0000 1111 1111’B
– Available SF	64
– Preamble scrambling code number	0
– Puncturing Limit	1.00
– Available Sub Channel number	‘1111 1111 1111’B
– Transport Channel Identity	15
– RACH TFS
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC size	168
– Number of TB and TTI List
– Number of Transport blocks	1
– CHOICE Mode	FDD
– CHOICE Logical Channel List	Configured
– RLC size	360
– Number of TB and TTI List
– Number of Transport blocks	1
– CHOICE Mode	FDD
– CHOICE Logical Channel List	Configured
– Semi-static Transport Format information
– Transmission time interval	20 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	150
– CRC size	16
– RACH TFCS
– CHOICE TFCI signalling	Normal
– TFCI Field 1 information
– CHOICE TFCS representation	Complete reconfiguration
– TFCS complete reconfiguration information
– CHOICE CTFC Size	2 bit
– CTFC information	0
– Power offset information
– CHOICE Gain Factors	Computed Gain Factor
– Reference TFC ID	0
– CHOICE Mode	FDD
– Power offset Pp-m	0 dB
– CTFC information	1
– Power offset information
– CHOICE Gain Factors	Signalled Gain Factor
– CHOICE mode	FDD
– Gain factor ßc	11
– Gain factor ßd	15
– Reference TFC ID	0
– CHOICE Mode	FDD
– Power offset Pp-m	0 dB
– PRACH partitioning
– Access Service Class
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#1)
– Available signature End Index	7 (ASC#1)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#3)
– Available signature End Index	7 (ASC#3)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#5)
– Available signature End Index	7 (ASC#5)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– ASC Setting	Not Present
– ASC Setting
– CHOICE mode	FDD
– Available signature Start Index	0 (ASC#7)
– Available signature End Index	7 (ASC#7)
– Assigned Sub-Channel Number	‘1111’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number.
– Persistence scaling factor
– Persistence scaling factor	0.9 (for ASC#2)
– Persistence scaling factor	0.9 (for ASC#3)
– Persistence scaling factor	0.9 (for ASC#4)
– Persistence scaling factor	0.9 (for ASC#5)
– Persistence scaling factor	0.9 (for ASC#6)
– Persistence scaling factor	0.9 (for ASC#7)
– AC-to-ASC mapping table
– AC-to-ASC mapping	6 (AC0-9)
– AC-to-ASC mapping	5 (AC10)
– AC-to-ASC mapping	4 (AC11)
– AC-to-ASC mapping	3 (AC12)
– AC-to-ASC mapping	2 (AC13)
– AC-to-ASC mapping	1 (AC14)
– AC-to-ASC mapping	0 (AC15)
– CHOICE mode	FDD
– Primary CPICH TX power	31
– Constant value	-10
– PRACH power offset
– Power Ramp Step	3dB
– Preamble Retrans Max	4
– RACH transmission parameters
– Mmax	2
– NB01min	3 slot
– NB01max	10 slot
– AICH info
– Channelisation code	3
– STTD indicator	FALSE
– AICH transmission timing	0
– Secondary CCPCH system information
– Secondary CCPCH info
– CHOICE mode	FDD
– Secondary scrambling code	Not Present
– STTD indicator	FALSE
– Spreading factor	64
– Code number	1
– Pilot symbol existence	FALSE
– TFCI existence	TRUE (default value)
– Fixed or Flexible position	Flexible (default value)
– Timing offset	0
– TFCS	(This IE is repeated for TFC number for PCH and FACH.)
– CHOICE TFCI signalling	Normal
– TFCI Field 1 information
– CHOICE TFCS representation	Complete reconfiguration
– TFCS complete reconfiguration information
– CHOICE CTFC Size	4 bit
– CTFC information	0
– Power offset information	Not Present
– CTFC information	1
– Power offset information	Not Present
– CTFC information	2
– Power offset information	Not Present
– CTFC information	3
– Power offset information	Not Present
– CTFC information	4
– Power offset information	Not Present
– CTFC information	5
– Power offset information	Not Present
– CTFC information	6
– Power offset information	Not Present
– CTFC information	8
– Power offset information	Not Present
– FACH/PCH information
– TFS	(PCH)
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC Size	240
– Number of TB and TTI List
– Number of Transport blocks	0
– Number of Transport blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	230
– CRC size	16 bit
– Transport Channel Identity	12 (for PCH)
– CTCH indicator	FALSE
– TFS	(FACH)
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC Size	168
– Number of TB and TTI List
– Number of Transport blocks	0
– Number of Transport blocks	1
– Number of Transport blocks	2
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Convolutional
– Coding Rate	1/2
– Rate matching attribute	220
– CRC size	16 bit
– Transport Channel Identity	13 (for FACH)
– CTCH indicator	FALSE
– TFS	(FACH)
– CHOICE Transport channel type	Common transport channels
– Dynamic Transport format information
– RLC Size	360
– Number of TB and TTI List
– Number of Transport blocks	0
– Number of Transport blocks	1
– CHOICE Logical Channel List	ALL
– Semi-static Transport Format information
– Transmission time interval	10 ms
– Type of channel coding	Turbo
– Rate matching attribute	130
– CRC size	16bit
– Transport Channel Identity	14 (for FACH)
– CTCH indicator	FALSE
– PICH info
– CHOICE mode	FDD
– Channelisation code	2
– Number of PI per frame	18
– STTD indicator	FALSE
– CBS DRX Level 1 information	Not Present

System Information Block type 7

Use the same System Information Block Type 7 message as found in clause 6.1.0b of TS 34.108, with the following exceptions:

– PRACHs listed in system information block type6
– Dynamic persistence level	2

Contents of SYSTEM INFORMATION BLOCK TYPE 11 (FDD)

– Sib12 Indicator	TRUE
– FACH measurement occasion info	Present
– Measurement control system information
– Use of HCS	Not used
– Cell selection and reselection quality measure	CPICH RSCP
– Intra-frequency measurement system information
– Intra-frequency measurement identity	Not Present Absence of this IE is equivalent to default value 1
– Intra-frequency cell info list
– CHOICE intra-frequency cell removal	Not present (This IE shall be ignored by the UE for SIB11)
– New intra-frequency cells
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	Not present Absence of this IE is equivalent to default value 0 (0 dB)
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info	Present
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	Not present Absence of this IE is equivalent to default value 0 (0 dB)
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1.4
– Primary CPICH TX power	31
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info	Present
– Intra-frequency cell id	3
– Cell info	Same content as specified for Intra-frequency cell id=1 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1.4
– Intra-frequency cell id	7
– Cell info	Same content as specified for Intra-frequency cell id=1 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.7 (FDD)" in clause 6.1.4
– Intra-frequency cell id	8
– Cell info	Same content as specified for Intra-frequency cell id=1 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.8 (FDD)" in clause 6.1.4
– Cells for measurement	Not Present
– Intra-frequency measurement quantity
– Filter coefficient	Not present Absence of this IE is equivalent to the default value 0
– CHOICE mode	FDD
– Measurement quantity	CPICH RSCP
– Intra-frequency reporting quantity for RACH Reporting	Not Present
– Maximum number of reported cells on RACH	Not Present
– Reporting information for state CELL_DCH
– Intra-frequency reporting quantity
– Reporting quantities for active set cells
– Cell synchronisation information reporting indicator	FALSE
– Cell identity reporting indicator	TRUE
– CHOICE mode	FDD
– CPICH Ec/N0 reporting indicator	FALSE
– CPICH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Reporting quantities for monitored set cells
– Cell synchronisation information reporting indicator	TRUE
– Cell identity reporting indicator	TRUE
– CHOICE mode	FDD
– CPICH Ec/N0 reporting indicator	FALSE
– CPICH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Reporting quantities for detected set cells	Not Present
– Measurement reporting mode
– Measurement Report Transfer Mode	Acknowledged mode RLC
– Periodic Reporting/Event Trigger Reporting Mode	Event trigger
– CHOICE report criteria	Intra-frequency measurement reporting criteria
– Intra-frequency measurement reporting criteria
– Parameters required for each event	2 kinds
– Intra-frequency event identity	1b
– Triggering condition 1	Active set cells
– Triggering condition 2	Not Present
– Reporting Range Constant	10 (5 dB)
– Cells forbidden to affect Reporting range	Not Present
– W	1 (0.1)
– Hysteresis	0.0
– Threshold Used Frequency	Not Present
– Reporting deactivation threshold	Not Present
– Replacement activation threshold	Not Present
– Time to trigger	640
– Amount of reporting	Not Present
– Reporting interval	Not Present
– Reporting cell status
– CHOICE reported cell	Report cell within active set and/or monitored set cells on used frequency
– Maximum number of reported cells	3
– Intra-frequency event identity	1c
– Triggering condition 1	Not Present
– Triggering condition 2	Not Present
– Reporting Range Constant	Not Present
– Cells forbidden to affect Reporting range	Not Present
– W	Not Present
– Hysteresis	0 (0.0)
– Threshold Used Frequency	Not Present
– Reporting deactivation threshold	Not Present
– Replacement activation threshold	3
– Time to trigger	640
– Amount of reporting	4
– Reporting interval	4000
– Reporting cell status
– CHOICE reported cell	Report cell within active set and/or monitored set cells on used frequency
– Maximum number of reported cells	3
– Inter-frequency measurement system information
– Inter-frequency cell info list
– CHOICE Inter-frequency cell removal	Not present (This IE shall be ignored by the UE for SIB11)
– New inter-frequency cells
– Inter frequency cell id	4
– Frequency info
– CHOICE mode	FDD
– UARFCN uplink(Nu)	Not present Absence of this IE is equivalent to applying the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink(Nd)	Reference to table 6.1.2 for Cell 4
– Cell info
– Cell individual offset	Not present Absence of this IE is equivalent to default value 0 (0 dB)
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.4 (FDD)" in clause 6.1.4
– Primary CPICH Tx power	31
– TX Diversity Indicator	FALSE
– Cell Selection and Re-selection Info	present (same values as for serving cell applies)
– Inter frequency cell id	5
– Frequency info	Not Present Absence of this IE is equivalent to value of the previous "frequency info" in the list.
– Cell info	Same content as specified for Inter-frequency cell id=4 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.5 (FDD)" in clause 6.1.4
– Inter frequency cell id	6
– Frequency info	Not Present Absence of this IE is equivalent to value of the previous "frequency info" in the list.
– Cell info	Same content as specified for Inter-frequency cell id=4 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.6 (FDD)" in clause 6.1.4
– Cell for measurement	Not present
– Inter-RAT measurement system information	Not Present
– Traffic volume measurement system information
– Traffic volume measurement identity	5
– Traffic volume measurement object list	Not Present
– Traffic volume measurement quantity
– Measurement quantity	RLC Buffer Payload
– Time Interval to take an average or a variance	Not Present
– Traffic volume reporting quantity
– RLC Buffer Payload for each RB	TRUE
– Average of RLC Buffer Payload for each RB	FALSE
– Variance of RLC Buffer Payload for each RB	FALSE
– Measurement validity	Not Present
– Measurement Reporting Mode
– Measurement Reporting Transfer Mode	Acknowledged mode RLC
– Periodic Reporting/Event Trigger Reporting Mode	Periodical trigger
– Report Criteria Sys Inf
– Periodical Reporting Criteria
– Reporting Amount	Infinity
– Reporting interval	8000

Contents of SYSTEM INFORMATION BLOCK TYPE 12 (FDD)

– FACH measurement occasion info	Present
– Measurement control system information
– Use of HCS	Not used
– Cell selection and reselection quality measure	CPICH RSCP
– Intra-frequency measurement system information
– Intra-frequency measurement identity	Not Present Absence of this IE is equivalent to default value 1
– Intra-frequency cell info list
– CHOICE intra-frequency cell removal	Not present (This IE shall be ignored by the UE for SIB11)
– New intra-frequency cells
– Intra-frequency cell id	2
– Cell info
– Cell individual offset	Not present Absence of this IE is equivalent to default value 0 (0 dB)
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.1 (FDD)" in clause 6.1.4
– Primary CPICH TX power	Not Present
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info	Present
– Intra-frequency cell id	1
– Cell info
– Cell individual offset	Not present Absence of this IE is equivalent to default value 0 (0 dB)
– Reference time difference to cell	Not Present
– Read SFN indicator	TRUE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.2 (FDD)" in clause 6.1.4
– Primary CPICH TX power	31
– TX Diversity indicator	FALSE
– Cell Selection and Re-selection info	Present
– Intra-frequency cell id	3
– Cell info	Same content as specified for Intra-frequency cell id=1 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.3 (FDD)" in clause 6.1.4
– Intra-frequency cell id	7
– Cell info	Same content as specified for Intra-frequency cell id=1 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.7 (FDD)" in clause 6.1.4
– Intra-frequency cell id	8
– Cell info	Same content as specified for Intra-frequency cell id=1 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.8 (FDD)" in clause 6.1.4
– Cells for measurement	Not Present
– Intra-frequency measurement quantity
– Filter coefficient	Not present Absence of this IE is equivalent to the default value 0
– CHOICE mode	FDD
– Measurement quantity	CPICH RSCP
– Intra-frequency reporting quantity for RACH Reporting	Not Present
– Maximum number of reported cells on RACH	Not Present
– Reporting information for state CELL_DCH
– Intra-frequency reporting quantity
– Reporting quantities for active set cells
– Cell synchronisation information reporting indicator	FALSE
– Cell identity reporting indicator	TRUE
– CHOICE mode	FDD
– CPICH Ec/N0 reporting indicator	FALSE
– CPICH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Reporting quantities for monitored set cells
– Cell synchronisation information reporting indicator	TRUE
– Cell identity reporting indicator	TRUE
– CHOICE mode	FDD
– CPICH Ec/N0 reporting indicator	FALSE
– CPICH RSCP reporting indicator	TRUE
– Pathloss reporting indicator	FALSE
– Reporting quantities for detected set cells	Not Present
– Measurement reporting mode
– Measurement Report Transfer Mode	Acknowledged mode RLC
– Periodic Reporting/Event Trigger Reporting Mode	Event trigger
– CHOICE report criteria	Intra-frequency measurement reporting criteria
– Intra-frequency measurement reporting criteria
– Parameters required for each event	2 kinds
– Intra-frequency event identity	1b
– Triggering condition 1	Active set cells
– Triggering condition 2	Not Present
– Reporting Range Constant	10 (5 dB)
– Cells forbidden to affect Reporting range	Not Present
– W	1 (0.1)
– Hysteresis	0 (0.0)
– Threshold Used Frequency	Not Present
– Reporting deactivation threshold	Not Present
– Replacement activation threshold	Not Present
– Time to trigger	640
– Amount of reporting	Not Present
– Reporting interval	Not Present
– Reporting cell status
– CHOICE reported cell	Report cell within active set and/or monitored set cells on used frequency
– Maximum number of reported cells	3
– Intra-frequency event identity	1c
– Triggering condition 1	Not Present
– Triggering condition 2	Not Present
– Reporting Range Constant	Not Present
– Cells forbidden to affect Reporting range	Not Present
– W	Not Present
– Hysteresis	0 (0.0)
– Threshold Used Frequency	Not Present
– Reporting deactivation threshold	Not Present
– Replacement activation threshold	3
– Time to trigger	640
– Amount of reporting	4
– Reporting interval	4000
– Reporting cell status
– CHOICE reported cell	Report cell within active set and/or monitored set cells on used frequency
– Maximum number of reported cells	3
– Inter-frequency measurement system information
– Inter-frequency cell info list
– CHOICE Inter-frequency cell removal	Not present (This IE shall be ignored by the UE for SIB11)
– New inter-frequency cells
– Inter frequency cell id	4
– Frequency info
– CHOICE mode	FDD
– UARFCN uplink(Nu)	Not present Absence of this IE is equivalent to apply the default duplex distance defined for the operating frequency according to 3GPP TS 25.101 [21]
– UARFCN downlink(Nd)	Reference to table 6.1.2 for Cell 4
– Cell info
– Cell individual offset	Not present Absence of this IE is equivalent to default value 0 (0 dB)
– Reference time difference to cell	Not Present
– Read SFN indicator	FALSE
– CHOICE mode	FDD
– Primary CPICH info
– Primary scrambling code	Refer to clause titled "Default settings for cell No.4 (FDD)" in clause 6.1.4
– Primary CPICH Tx power	31
– TX Diversity Indicator	FALSE
– Cell Selection and Re-selection Info	present (same values as for serving cell applies)
– Inter frequency cell id	5
– Frequency info	Not Present Absence of this IE is equivalent to value of the previous "frequency info" in the list.
– Cell info	Same content as specified for Inter-frequency cell id=4 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.5 (FDD)" in clause 6.1.4
– Inter frequency cell id	6
– Frequency info	Not Present Absence of this IE is equivalent to value of the previous "frequency info" in the list.
– Cell info	Same content as specified for Inter-frequency cell id=4 with the exception that value for Primary scrambling code shall be according to clause titled "Default settings for cell No.6 (FDD)" in clause 6.1.4
– Cell for measurement	Not present
– Inter-RAT measurement system information	Not Present
– Traffic volume measurement system information
– Traffic volume measurement identity	5
– Traffic volume measurement object list	Not Present
– Traffic volume measurement quantity
– Measurement quantity	RLC Buffer Payload
– Time Interval to take an average or a variance	Not Present
– Traffic volume reporting quantity
– RLC Buffer Payload for each RB	TRUE
– Average of RLC Buffer Payload for each RB	FALSE
– Variance of RLC Buffer Payload for each RB	FALSE
– Measurement validity	Not Present
– Measurement Reporting Mode
– Measurement Reporting Transfer Mode	Acknowledged mode RLC
– Periodic Reporting/Event Trigger Reporting Mode	Periodical trigger
– Report Criteria Sys Inf
– Periodical Reporting Criteria
– Reporting Amount	Infinity
– Reporting interval	8000

8.1.10.1.5 Test requirement

After step 1 the UE shall have a call/session established in Cell 1.

After step 5 the UE shall have a call/session established in Cell 2.

8.1.10.2 BCCH Mapping on HS-DSCH for Transmitting System Information Change Indication

8.1.10.2.1 Definition

All UEs which support FDD and HS-PDSCH in CELL_FACH, except UEs that receive Master information block value tag autonomously before or parallel to receiving SYSTEM INFORMATION CHANGE INDICATION in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

- - - 1. Conformance requirement

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

…

1> 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.

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

…

The UE shall:

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

1> if the value tags differ:

2> read the master information block on BCH;

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.

…

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

…

1> and for FDD, for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH code listed in the IE "HS-SCCH channelization code" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

Reference

3GPP TS 25.331: 8.1.1.7.1, 8.1.1.7.3, 8.5.36

8.1.10.2.3 Test Purpose

To verify the correct use of system change indication for BCCH mapped on HS-DSCH
To verify operation of BCCH specific H-RNTI
To verify that BCCH reception on HS-DSCH uses the first indexed HS-SCCH code listed on the IE HS-SCCH channelization code with BCCH specific H-RNTI

8.1.10.2.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: CELL_FACH state with DCCH/DTCH mapped onto HS-DSCH as specified in clause 7.4 of TS 34.108 with dedicated H-RNTI and C-RNTI assigned.

Related ICS/IXIT statement(s)

– UE supports FDD

– UE supports HS-PDSCH in CELL_FACH

Test Procedure

The SS transmits the new SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis message. In the new SIB TYPE 5 / SIB TYPE 5bis message, the IE "HS-SCCH Channelisation Code” is different when compared to the original SIB TYPE 5 / SIB TYPE 5bis message. Master information block is transmitted with updated MIB value tag. Then SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE with BCCH mapped on HS-DSCH. The transmission of BCCH on HS-DSCH is performed by using BCCH-specific H-RNTI on the specific HS-SCCH code indicated in system information broadcast. The SYSTEM INFORMATION CHANGE INDICATION message shall include the IE "BCCH Modification Information" indicating the value tag of the modified master information block. After an elapsed time, required to read the new HS-SCCH channelization code in system information, the SS transmits a UE CAPABILITY ENQUIRY message on RB1 over HS-DSCH using HS-SCCH code 7. The UE does not respond to this. SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code 6. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

The SS transmits modified SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. In this message the IE "HS-SCCH Channelisation Code” is set to use HS-SCCH code 7. The Master information block is transmitted with updated MIB value tag. The SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE. This message is transmitted using HS-SCCH code 7. After an elapsed time, required to read the new HS-SCCH channelization code in system information, the SS transmits a UE CAPABILITY ENQUIRY message on RB1 over HS-DSCH using HS-SCCH code 7. The UE does not respond to this. SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code 5. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure

The SS modifies SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. In this message the IE "HS-SCCH Channelisation Code” is set to use HS-SCCH code 7. The Master information block is transmitted with updated MIB value tag. The SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE. This message is transmitted using HS-SCCH code 6. After an elapsed time, required to read the new HS-SCCH channelization code in system information, SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code 7. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1				The UE is in CELL_FACH state and configured for HS-DSCH reception with dedicated H-RNTI and C-RNTI assigned.
2			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is changed from "7" to "6" for first indexed HS-SCCH code and to “5” for the second indexed HS-SCCH code.
3			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting.
4			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 7 as defined in default SIB5 message.
5				SS waits 5s (to ensure that the UE has time to read the new system information)
6			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB1. Use default message but using HS-SCCH channelization Code 7. Use default message.
7				SS waits 10 seconds and checks that the UE does not respond.
8			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 6. Use default message.
9			UE CAPABILITY INFORMATION	Use default message.
10			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.
11			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is changed back to 7.
12			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the previous setting.
13			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 7.
14				SS waits 5s. A 3GPP compliant UE should not receive SYSTEM INFORMATION CHANGE INDICATION and not re-read System Information
15			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB1. Use default message but using HS-SCCH channelization Code 7. Use default message.
16				SS waits 10 seconds and checks that the UE does not respond.
17			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 5. Use default message.
18			UE CAPABILITY INFORMATION	Use default message.
19			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.
20			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is set to 7.
21			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the previous setting.
22			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 6.
				SS waits 5s (to ensure that the UE has time to read the new system information)
23			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 7. Use default message.
24			UE CAPABILITY INFORMATION	Use default message.
25			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.

Specific Message Contents

SYSTEM INFORMATION CHANGE INDICATION (Steps 4, 13, 22)

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

MASTER INFORMATION BLOCK (Step 3, 12, 21)

Information Element	Value/remark
MIB Value tag	As in SYSTEM INFORMATION CHANGE INDICATION in step 2
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

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

Use the same message type found in clause 6.1.0b of TS 34.108, configuration for HS-DSCH reception in CELL_FACH, with the following exception.

Information Element	Value/remark
– HS-SCCH system info
– DL Scrambling Code	Not Present
– HS-SCCH Channelisation Code Information	Use 2 HS-SCCH
– HS-SCCH Channelisation Code	6
– HS-SCCH Channelisation Code	5

SYSTEM INFORMATION BLOCK TYPE 5/ SYSTEM INFORMATION BLOCK TYPE 5bis. (Steps 11 & 20)(FDD)

Use the same message type found in clause 6.1.0b of TS 34.108, configuration for HS-DSCH reception in CELL_FACH

8.1.10.2.5 Test requirement

At step 7 the UE shall not respond to the UE CAPABILITY ENQUIRY message sent in step 6.

At step 9 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.

At step 16 the UE shall not respond to the UE CAPABILITY ENQUIRY message sent in step 15.

At step 24 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.

8.1.10.2a BCCH Mapping on HS-DSCH for Transmitting System Information Change Indication with autonomous reading of Master Information Block Value Tag

8.1.10.2a.1 Definition

UEs which support FDD and HS-PDSCH in CELL_FACH and receive Master information block value tag autonomously before or parallel to receiving SYSTEM INFORMATION CHANGE INDICATION in SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis.

8.1.10.2a.2 Conformance requirement

…

The UE shall:

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

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in subclause 8.1.1.5.

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.

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.

…

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

…

and for FDD, for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH code listed in the IE "HS-SCCH channelisation code" with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

…

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.

…

Reference

3GPP TS 25.331: 8.1.1.7.1, 8.1.1.7.3, 8.5.36, 8.1.1.6

8.1.10.2a.3 Test Purpose

1. To verify the correct use of system change indication for BCCH mapped on HS-DSCH

2. To verify operation of BCCH specific H-RNTI

3. To verify that BCCH reception on HS-DSCH uses the first indexed HS-SCCH code listed on the IE HS-SCCH channelisation code with BCCH specific H-RNTI

8.1.10.2a.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: CELL_FACH state with DCCH/DTCH mapped onto HS-DSCH as specified in clause 7.4 of TS 34.108 with dedicated H-RNTI and C-RNTI assigned.

Related ICS/IXIT statement(s)

– UE supports FDD

– UE supports HS-PDSCH in CELL_FACH

Test Procedure

SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code 6. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

The SS transmits modified SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. In this message the IE "HS-SCCH Channelisation Code” is set to use HS-SCCH code 7. The Master information block is transmitted with updated MIB value tag. The SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE. This message is transmitted using HS-SCCH code 7. After an elapsed time, required to read the master information block value tag and/or the new HS-SCCH channelization code in system information, the SS transmits a UE CAPABILITY ENQUIRY message on RB1 over HS-DSCH using HS-SCCH code 7. The UE responds to this and should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1				The UE is in CELL_FACH state and configured for HS-DSCH reception with dedicated H-RNTI and C-RNTI assigned.
2			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is changed from "7" to "6" for first indexed HS-SCCH code and to “5” for the second indexed HS-SCCH code.
3			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting. The UE receives Master information block value tag autonomously and reads the system infromation.
4				SS waits 5seconds (to ensure that the UE has time to read the new system information after receiving Master information block value tag autonomously).
5			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB1. Use default message but using HS-SCCH channelisation Code 7. Use default message.
6				SS waits 10 seconds and checks that the UE does not respond.
7			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelisation Code 6. Use default message.
8			UE CAPABILITY INFORMATION	Use default message.
9			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.
10			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	For FDD, at the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is changed back to 7.
11			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the previous setting.
12			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 7.
13				SS waits 5 seconds (to ensure that the UE has time to read the master information block value tag and/or new system information).
14			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB1. Use default message but using HS-SCCH channelisation Code 7. Use default message.
15			UE CAPABILITY ENQUIRY INFORMATION	The UE sends UE CAPABILITY ENQUIRY INFORMATION on UL SRB1 as the response to the UE CAPABILITY ENQUIRY in step 14.
16			UE CAPABILITY INFORMATION CONFIRM	The SS responds with a UE CAPABILITY INFORMATION CONFIRM.

Specific Message Contents

SYSTEM INFORMATION CHANGE INDICATION (Steps 12)

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

MASTER INFORMATION BLOCK (Step 3, 11)

Information Element	Value/remark
MIB Value tag	As in SYSTEM INFORMATION CHANGE INDICATION in step 2
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

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

Use the same message type found in clause 6.1.0b of TS 34.108, configuration for HS-DSCH reception in CELL_FACH, with the following exception.

Information Element	Value/remark
– HS-SCCH system info
– DL Scrambling Code	Not Present
– HS-SCCH Channelisation Code Information	Use 2 HS-SCCH
– HS-SCCH Channelisation Code	6
– HS-SCCH Channelisation Code	5

SYSTEM INFORMATION BLOCK TYPE 5/ SYSTEM INFORMATION BLOCK TYPE 5bis. (Steps 10)(FDD)

Use the same message type found in clause 6.1.0b of TS 34.108, configuration for HS-DSCH reception in CELL_FACH

8.1.10.2a.5 Test requirement

At step 6 the UE shall not respond to the UE CAPABILITY ENQUIRY message sent in step 5.

At step 8 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.

At step 15 the UE shall respond to the UE CAPABILITY ENQUIRY message sent on UL SRB1in step 15 after the UE receives Master information block value tag autonomously in step 14.

8.1.10.3 BCCH Mapping on HS-DSCH for Transmitting System Information Change Indication (1.28Mcps TDD)

8.1.10.3.1 Definition

All UEs which support 1.28Mcps TDD and HS-PDSCH in CELL_FACH.

8.1.10.3.2 Conformance requirement

…

The UE shall:

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

1> if the value tags differ:

2> read the master information block on BCH;

3> perform actions as specified in subclause 8.1.1.5.

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.

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.

…

Whenever the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, the UE shall:

…

1> and for 1.28 Mcps TDD, for BCCH reception perform HS-DSCH reception procedures by listening to the first indexed HS-SCCH according to the stored HS-SCCH configuration with "BCCH specific H-RNTI" as received in IE "HS-DSCH common system information".

NOTE : For 1.28 Mcps TDD, when performing HS-DSCH reception in CELL_FACH state, the UE shall use the table of transport block size for the HS-DSCH physical layer category 9 as specified in [15].

Reference

3GPP TS 25.331: 8.1.1.7.1, 8.1.1.7.3, 8.5.36

8.1.10.3.3 Test Purpose

To verify the correct use of system change indication for BCCH mapped on HS-DSCH
To verify operation of BCCH specific H-RNTI
To verify that BCCH reception on HS-DSCH uses the first indexed HS-SCCH code listed on the IE HS-SCCH channelization code with BCCH specific H-RNTI

8.1.10.3.4 Method of test

Initial Condition

System Simulator: 1 cell

UE: CELL_FACH state with DCCH/DTCH mapped onto HS-DSCH as specified in clause 7.4 of TS 34.108 with dedicated H-RNTI and C-RNTI assigned.

Related ICS/IXIT statement(s)

– UE supports 1.28Mcps TDD

– UE supports HS-PDSCH in CELL_FACH

Test Procedure

The SS transmits the new SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis message. In the new SIB TYPE 5 / SIB TYPE 5bis message, the IE "HS-SCCH Channelisation Code” is different when compared to the original SIB TYPE 5 / SIB TYPE 5bis message. Master information block is transmitted with updated MIB value tag. Then SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE with BCCH mapped on HS-DSCH. The transmission of BCCH on HS-DSCH is performed by using BCCH-specific H-RNTI on the specific HS-SCCH code indicated in system information broadcast. The SYSTEM INFORMATION CHANGE INDICATION message shall include the IE "BCCH Modification Information" indicating the value tag of the modified master information block. After an elapsed time, required to read the new HS-SCCH channelization code in system information, the SS transmits a UE CAPABILITY ENQUIRY message on RB1 over HS-DSCH using HS-SCCH code "16/11"and “16/12”. The UE does not respond to this. SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code "16/7"and “16/8”. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

The SS transmits modified SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. In this message the IE "HS-SCCH Channelisation Code” is set to use HS-SCCH code "16/11"and “16/12”. The Master information block is transmitted with updated MIB value tag. The SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE, This message is transmitted using HS-SCCH code "16/11"and “16/12”. After an elapsed time, required to read the new HS-SCCH channelization code in system information, the SS transmits a UE CAPABILITY ENQUIRY message on RB1 over HS-DSCH using HS-SCCH code "16/11"and “16/12”. The UE does not respond to this. SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code "16/9"and “16/10”. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure.

The SS modifies SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis. In this message the IE "HS-SCCH Channelisation Code” is set to use HS-SCCH code "16/11"and “16/12”. The Master information block is transmitted with updated MIB value tag. The SS transmits a SYSTEM INFORMATION CHANGE INDICATION message to the UE, This message is transmitted using HS-SCCH code "16/7"and “16/8”. After an elapsed time, required to read the new HS-SCCH channelization code in system information. SS transmits a UE CAPABILITY ENQUIRY message on RB2 over HS-DSCH using HS-SCCH code "16/11"and “16/12”. After receiving this message the UE should transmit a UE CAPABILITY INFORMATION message on the UL DCCH which indicates the requested capabilities. The SS transmits a UE CAPABILITY INFORMATION CONFIRM message to the UE to complete the UE capability enquiry procedure

Step	Direction		Message	Comment
Step	UE	SS	Message	Comment
1				The UE is in CELL_FACH state and configured for HS-DSCH reception with dedicated H-RNTI and C-RNTI assigned.
2			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	At the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is changed from "16/11"and “16/12” to "16/7" and “16/8” for first indexed HS-SCCH and to “16/9” and “16/10” for the second indexed HS-SCCH code.
3			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the original setting.
4			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 16/11 and 16/12 as defined in default SIB5 message.
5				SS waits 5s (to ensure that the UE has time to read the new system information)
.6			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 16/11 and 16/12. Use default message.
7				SS waits 10 seconds and checks that the UE does not respond.
8			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 16/7 and 16/8. Use default message.
9			UE CAPABILITY INFORMATION	Use default message.
10			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.
11			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	At the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is changed back to 16/11 and 16/12.
12			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the previous setting.
13			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 16/11 and 16/12.
14				SS waits 5s. A 3GPP compliant UE should not receive SYSTEM INFORMATION CHANGE INDICATION and not re-read System Information
15			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 16/11 and 16/12. Use default message.
16				SS waits 10 seconds and checks that the UE does not respond.
17			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 16/9 and 16/10. Use default message.
18			UE CAPABILITY INFORMATION	Use default message.
19			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.
20			SYSTEM INFORMATION BLOCK TYPE 5 / SYSTEM INFORMATION BLOCK TYPE 5bis	At the same time, SS starts to transmit the affected SIB TYPE 5/ SIB TYPE 5bis continuously. The value of IE "HS-SCCH Channelisation Code" is set to 16/11 and 16/12.
21			MASTER INFORMATION BLOCK	SS starts to transmit the MIB with the "MIB Value Tag" IE different from the previous setting.
22			SYSTEM INFORMATION CHANGE INDICATION	SS transmits the RRC message which comprises IE "BCCH Modification Information", with the "Value Tag" changed from the "MIB Value Tag" of the current Master Information Block. BCCH is mapped on HS-DSCH. HS-SCCH code is 16/7and 16/8.
				SS waits 5s (to ensure that the UE has time to read the new system information)
23			UE CAPABILITY ENQUIRY	RRC message sent on DL SRB2. Use default message but using HS-SCCH channelization Code 16/11 and 16/12. Use default message.
24			UE CAPABILITY INFORMATION	Use default message.
25			UE CAPABILITY INFORMATION CONFIRM	Use default message. SRB is sent on SRB2.

Specific Message Contents

SYSTEM INFORMATION CHANGE INDICATION (Steps 4, 13, 22)

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

MASTER INFORMATION BLOCK (Step 3, 12, 21)

Information Element	Value/remark
MIB Value tag	As in SYSTEM INFORMATION CHANGE INDICATION in step 2
SIB 5 Cell Value tag	Set to (Current SIB5 value tag + 1)

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

Use the same message type found in clause 6.1.0b of TS 34.108, configuration for HS-DSCH reception in CELL_FACH, with the following exception.

Information Element	Value/remark
– HS-SCCH Set Configuration	Use 2 HS-SCCH
– Timeslot number	0
– First Channelisation code	16/7
– Second Channelisation code	16/8
– Timeslot number	0
– First Channelisation code	16/9
– Second Channelisation code	16/10

SYSTEM INFORMATION BLOCK TYPE 5/ SYSTEM INFORMATION BLOCK TYPE 5bis. (Step 11, 20)

Use the same message type found in clause 6.1.0b of TS 34.108, configuration for HS-DSCH reception in CELL_FACH,

8.1.10.3.5 Test requirement

At step 7 the UE shall not respond to the UE CAPABILITY ENQUIRY message sent in step 6.

At step 9 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.

At step 16 the UE shall not respond to the UE CAPABILITY ENQUIRY message sent in step 15.

At step 24 the UE shall transmit a UE CAPABILITY INFORMATION message on the uplink DCCH to respond to the downlink UE CAPABILITY ENQUIRY message with correct contents.