8.14.2 MSCH scheduling and service data on MTCH

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

Multiple ordered SCHEDULING INFORMATION messages are sent by using RLC_UM_MSCH_Msg_REQ. Each SCHEDULING INFORMATION corresponds to a scheduling period, a ‘noSend’ MSCH_Message indicates that no MBMS services are scheduled in that scheduling period for all MTCH. The first SCHEDULING INFORMATION message is sent on the scheduledSFN and successively the remaining messages are sent in every scheduling period.

The MBMS service data are fed by RLC_UM_TestDataReq. However the real MBMS service transmissions for multiple scheduling periods on each MTCH are controlled by CRLC_MTCH_Scheduling_REQ. Within each scheduling period the information on the discontinuous service transmissions are conveyed through a list of pairs of (start, duration). The IE noServiceData as NULL being provided for a scheduling period indicates no service transmission on that MTCH.

The simulation of the continuous MBMS services is provided if an empty CRLC_MTCH_Scheduling_REQ is sent without scheduling configuration parameter and scheduling information.

RLC_UM_MSCH_Msg_REQ precedes CRLC_MTCH_Scheduling_REQ and RLC_UM_TestDataReq.

Figure 8.14.2: MSCH scheduling and MTCH data transfer

8.14.2.1 Scheduled service data on MTCH without MSCH configured

The scheduled service is a mechanism for synchronization of the initialization of the MBMS services announced on MCCH and the start of transmission the service data on MTCH. The mechanism can also be used at the SS side when MSCH is not configured.

In a PTM test session two separate sequences of critical MCCH messages are transmitted in an order of C4 – C2 or C5 – C3 in two consecutive modification periods. The MBMS MODIFIED SERVICES INFORMATION message in C4/C5 generally does not contain MBMS p-t-m activation time for the UE immediate reception of MBMS services. However, the SS shall not start test data transmission until on the 1^st TTI of the next modification period to ensure that the UE can have a nearly full modification period to obtain critical MCCH messages and to apply the configuration required by the test.

Figure 8.14.2.1 illustrates the relationship of the service scheduling on MTCH and the default1 MCCH information scheduling. The SS waits until the 2^nd half of the last repetition period in the modification period when the C4 messages are sent before closing test loop. The test data are transmitted on the 1^st TTI of the modification period when the C2 messages are sent. The whole test sequence is:

CPHY_SFN_REQ, calculating next MICH CFN,

MP n: next MICH CFN set MICH and transmit NI,

MP n+1: next MICH CFN+1 mp set modified services list (C4 or C5), set PTM activation time if necessary,

MP n+2: next MICH CFN+2 mp set unmodified service list and transmit data (C2 or C3).

Figure 8.14.2.1: Synchronized MTCH data sending, no MSCH configured

If the test loop is already closed and the service data is to be sent the ASPs follow the order:

CPHY_SFN_REQ, CRLC_MTCH_Scheduling_REQ and RLC_UM_TestDataReq.