6.3 Data transmission

25.3033GPPInterlayer procedures in Connected ModeRelease 17TS

6.3.1 Void

6.3.2 Void

6.3.3 Void

6.3.4 Data transfer on USCH (TDD only)

In figure 23 a data transfer procedure on USCH is presented. It is assumed that the RB establishment has been performed for example with the RB Establishment procedure without Dedicated Physical Channel as illustrated in subclause 6.2.1.1.4 and that the RB is mapped on the USCH and DSCH transport channels. Use of the USCH is possible with or without an associated DCH.

In the UE the traffic measurement function decides to send a Capacity Request to the network using the SHCCH logical channel mapped on the RACH or USCH. In the C-RRC the USCH/DSCH scheduling function will decide to allocate physical resources to this logical channel and RRC in C-RNC sends a PhyShChAllocation to its peer entity in the UE. This message specifies the physical resources and the period of time the MAC-c/sh can transfer the data on the USCH transport channel.

Both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the USCH and at the specified time MAC-c/sh in the UE conveys the data using the specified PUSCH resources.

This operation may be repeated several times till the RLC buffer is empty.

In the diagram it is assumed that the PhyShChAllocation has allocated additionally to the PUSCH resources some PDSCH resources, so that at the time specified in the allocation message both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the DSCH and at the specified time MAC-c/sh in the C-RNC conveys the acknowledgement message of the UTRAN RLC to its UE peer entity using the specified PDSCH resources.

Transmitting the acknowledgement message via FACH is also possible.

Figure 23: Data transfer on USCH

6.3.5 Data transfer on DSCH (TDD only)

In figure 24 a data transfer procedure on DSCH is presented. It is assumed that the RB establishment has been performed for example with the RB Establishment procedure without Dedicated Physical Channel as illustrated in subclause 6.2.1.1.4 and that the RB is mapped on the USCH and DSCH transport channels.

Use of the DSCH is possible with or without an associated DCH.

In the C-RRC the USCH/DSCH scheduling function will decide to allocate physical resources in the downlink and RRC in C-RNC sends a PhyShChAllocation message to its peer entity in the UE using SHCCH mapped on the FACH or DSCH. This message specifies the physical resources and the period of time the MAC-c/sh can transfer the data on the DSCH transport channel.

Both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the DSCH and at the specified time MAC-c/sh in the C-RNC conveys the data using the specified PDSCH resources.

This operation may be repeated several times till the RLC buffer is empty.

In the diagram it is assumed that the PhyShChAllocation has allocated additionally to the PDSCH resources some PUSCH resources, so that at the time specified in the allocation message both RRC in the CRNC and the UE configure their respective Layer 1 and MAC for the data transfer on the USCH and at the specified time MAC-c/sh in the UE conveys the acknowledgement message of the UE to its C-RNC peer entity using the specified PUSCH resources.

Transmitting the acknowledgement message via RACH is also possible.

Figure 24: Data transfer on DSCH