5.3.6 Transport Channel, Logical Channel and MAC-d flow Numbering

25.3013GPPRadio interface protocol architectureTS

The UE model for transport channel and logical channel numbering is defined by the following:

– For FACH transport channels:

– A transport channel identity is associated with each FACH transport channel. Each identity is unique within the downlink FACHs mapped onto the same physical channel.

– Transport channel identities can be allocated non sequentially.

– Transport channel identity is not used to determine the radio bearer mapping. The transport channels that can be used are determined from the available physical channels.

– Each downlink DCCH and DTCH has a unique logical channel identity.

– A MAC MBMS identity (MBMS-Id) is associated with each MBMS service carried on MTCH on FACH. The identity is unique within a FACH and the mapping of the MBMS service id to the MBMS-Id is provided on the MCCH.

– For RACH transport channels:

– A transport channel identity is associated with each RACH transport channel. Each identity is unique within the RACHs mapped onto the same PRACH.

– Transport channel identities can be allocated non sequentially.

– Transport channel identity is not used to determine the radio bearer mapping. The transport channels that can be used are determined from the available physical channels.

– Each uplink DCCH and DTCH has a unique logical channel identity.

– For downlink DCH and DSCH transport channels:

– A transport channel identity is associated with each downlink DCH transport channel. Each identity is unique within the downlink DCHs configured in the UE;

– Transport channel identities can be allocated non sequentially.

– A transport channel identity is associated with each DSCH transport channel. Each identity is unique within the DSCHs configured in the UE;

– A logical channel identity is associated with each logical channel that is multiplexed with other logical channels before being mapped to a transport channel. Each identity is unique within the logical channels mapped to the same transport channel.

– A logical channel that is mapped to DCH and DSCH simultaneously in TDD has one logical channel identity.

– For HS-DSCH, when MAC-hs is configured:

– A MAC-flow identity is associated with each MAC-d flow. Each identity is unique within the MAC-d flows configured in the UE;

– A logical channel identity is associated with each logical channel that is multiplexed with other logical channels before being mapped to a MAC-d flow. Each identity is unique within the logical channels mapped to the same MAC-d flow;

– A logical channel that is mapped to DCH and HS-DSCH simultaneously has one logical channel identity.

– For HS-DSCH, when MAC-ehs is configured:

– A reordering queue identity is associated with each reordering queue. Each identity is unique within the reordering queues configured in the UE;

– A logical channel identity is associated with each logical channel that is mapped to a reordering queue. Each identity is unique within the logical channels mapped to any reordering queue;

– A logical channel that is mapped to DCH and HS-DSCH simultaneously has one logical channel identity.

– For uplink DCH and USCH transport channels:

– A transport channel identity is associated with each uplink DCH transport channel. Each identity is unique within the uplink DCHs configured in the UE;

– Transport channel identities can be allocated non sequentially.

– A transport channel identity is associated with each USCH transport channel. Each identity is unique within the USCHs configured in the UE;

– A logical channel identity is associated with each logical channel that is multiplexed with other logical channels before being mapped to a transport channel. Each identity is unique within the logical channels mapped to the same transport channel.

– For E-DCH, when MAC-e/es is configured:

– A MAC-flow identity is associated with each MAC-d flow. Each identity is unique within the MAC-d flows configured in the UE;

– A logical channel identity is associated with each logical channel that is mapped to a MAC-d flow. Each identity is unique within the logical channels mapped to any MAC-d flow;

– A DDI (Data Description Identity) is associated with each MAC-d PDU. The DDI values are unique within the UE;

– In addition to indicating the MAC-d PDU size, the DDI value indicates MAC-d flow and logical channel for the MAC-d PDU within the MAC-e PDU.

– For E-DCH, when MAC-i/is is configured:

– A MAC-flow identity is associated with each MAC-d flow. Each identity is unique within the MAC-d flows configured in the UE;

– A logical channel identity is associated with each logical channel that is mapped to a MAC-d flow. Each identity is unique within the logical channels mapped to any MAC-d flow;

– A LCH-ID (Logical channel identity) is associated with each MAC-d PDU. The LCH-ID values indicate the logical channel for the MAC-d PDU within the MAC-i PDU.

– In FDD only, when the UE is in CELL_FACH state, an E-RNTI is associated with each MAC-d PDU until an E-AGCH with the UE’s E-RNTI has been received (through an ID-specific CRC attachment).
For FDD and 1.28 Mcps TDD, one LCH-id value in the MAC-is header identifies MAC-d flows containing CCCH data.