8.4 System information blocks scheduling

34.123-33GPPPart 3: Abstract test suite (ATS)TSUser Equipment (UE) conformance specification

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

All SIBs specified in 3GPP TS 34.108 [3] are broadcast for all test cases in the present document. The repeat period of broadcasting of a complete SIB configuration is 64 frames (0,64 s) as the default configuration.

Except MIB and SB1, they have the highest scheduling rates, SIB7 has also a higher scheduling rate.

According to the default SIB contents in 3GPP TS 34.108 [3], SIB11 and SIB12 have 3 segments. SIB5/SIB5bis has 4 segments for FDD and 5 segments for 1.28 Mcps TDD. SIB 6 has 4 segments. MIB, SB1, SIB1, SIB2, SIB3, SIB4, SIB7 and SIB18 are not segmented, i.e. one segment for each. For the PDCP tests, SIB16 has 7 segments.

Use CMAC_SYSINFO_CONFIG_REQ, CMAC_SYSINFO_CONFIG_CNF and RLC_TR_DATA_REQ as interface to SS for broadcasting.

Two TSOs are defined, one for PER encoding function, the other for segmentation function. The TSOs shall be implemented in the tester.

8.4.1 Grouping SIBs for testing

The grouping of SIBs is defined in 3GPP TS 34.108 [3], clause 6.1.0a.1.

8.4.2 SIB configurations

SIB configurations are defined in 3GPP TS 34.108 [3], clause 6.1.0a.2.

8.4.3 Test SIB default schedule

The SIB default schedule is defined in 3GPP TS 34.108 [3], clause 6.1.0a.3.

8.4.3.1 Test SIB schedule for idle mode, measurement and Inter-RAT UTRAN to GERAN test cases

The SIB schedule is defined in 3GPP TS 34.108 [3], clause 6.1.0a.4.2.

8.4.4 Test SIB special schedule

8.4.4.1 Test SIB schedule for two S-CCPCH or two PRACH

The SIB schedule for two S-CCPCH or two PRACH is defined in 3GPP TS 34.108 [3], clause 6.1.0a.4.1.

8.4.4.2 Test SIB schedule for Inter-Rat Handover from GERAN to UTRAN Test

The SIB schedule for Inter-Rat Handover from GERAN to UTRAN Test is defined in 3GPP TS 34.108 [3], clause 6.1.0a.4.3.

8.4.5 Handling the transmission of SIB

According to the SIB repeat periods, SIBs need to be transmitted on a very regular basis during the operation of a test case. This transmission usually has no direct bearing on the operation of the test case, although the carried information ensures the correct configuration and operation of the UE during the test case.

To send this information repeatedly directly from each test case would make the test cases very complex to implement, difficult to understand and place real-time requirements upon them that are beyond the capabilities of most TTCN driven test engines.

Management of scheduling of System Information messages is performed by the system simulator. The SIB contents, usually determined in part by the individual tests, come from the TTCN test cases.

8.4.5.1 Delivery of System Information content

The content of the System Information messages is delivered as a fully encoded bit string to the TM-RLC SAP from the message content defined in the TTCN test case.

The IE ‘SFNprime’ in the SI messages is set to 0 by the TTCN, and the correct value of ‘SFNprime’ shall be inserted by the System Simulator prior to transmission of a SI message.

SI messages are ASN.1 packed encoded through a TTCN TSO and segmented another TTCN TSO into SIBs in the TTCN and sent only once to the TM-RLC SAP. Repetition of the SIB is the responsibility of the System Simulator lower layers.

SIBs are considered to be cached. That is, sending a SIB to the TM-RLC SAP will cause a previously sent copy of the SIB to be lost, and all future transmissions of the SIB will be the most recently sent version. This allows for the updating of System Information during the operation of a test case.

8.4.5.2 Scheduling of system Information blocks

The schedule for the transmission of SIBs is provided by the TTCN test case. It is sent using the CMAC_SYSINFO_CONFIG_REQ primitive sent to the CMAC SAP (CMAC_PCO).

Each CMAC_SYSINFO_CONFIG_REQ primitive carries scheduling information for the next SIB sent from the TTCN. Each primitive is followed by an associated SIB. Sending two CMAC_SYSINFO_CONFIG_REQ primitives in succession may cause an unspecified result.

8.4.5.3 Example of usage

The following example shows how the MIB, SB1 and all SIBs in subclause 8.4.3 are sent to the System Simulator lower layers for broadcasting. The 1^st parameter in CMAC_SYSINFO_CONFIG_REQ represents the repeat period in power of 2. The 2^nd parameter represents the repetition position. Two consecutive frames represent an available repetition position.

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (3, 0)

TM_PCO: MIB

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (4, 1)

TM_PCO: SB1

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 2)

TM_PCO: SIB7

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 3)

TM_PCO: SIB6 (segment 1 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 5)

TM_PCO: SIB6 (segment 2 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 6)

TM_PCO: SIB6 (segment 3 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 7)

TM_PCO: SIB6 (segment 4 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 10)

TM_PCO: SIB7 + SIB3 (concatenation)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 11)

TM_PCO: SIB1 + SIB2 (concatenation)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 13)

TM_PCO: SIB12 (segment 1 of 3)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 14)

TM_PCO: SIB12 (segment 2 of 3)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 15)

TM_PCO: SIB12 (segment 3 of 3)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 18)

TM_PCO: SIB7 + SIB18 (concatenation)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 19)

TM_PCO: SIB5/SIB5bis (segment 1 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 21)

TM_PCO: SIB5/SIB5bis (segment 2 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 22)

TM_PCO: SIB5/SIB5bis (segment 3 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 23)

TM_PCO: SIB5/SIB5bis (segment 4 of 4)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 26)

TM_PCO: SIB7 + SIB4 (concatenation)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 27)

TM_PCO: No segment

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 29)

TM_PCO: SIB11 (segment 1 of 3)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 30)

TM_PCO: SIB11 (segment 3 of 3)

CMAC_PCO: CMAC_SYSINFO_CONFIG_REQ (6, 31)

TM_PCO: SIB11 (segment 3 of 3)