QoS classes-

Radio Access Bearers are mapped onto these classes- Each user will with a certain probability belong to
a certain class of users with identical QoS profiles
Probability distribution of the QoS class membership of all users is referred to as service mix
Challenge for the operator: which service mix needs to be specified for the capacity definition of the system; important
parameters:
pricing strategy for services for revenue maximization
competition in the different services and QoS classes
Traffic Class ['conversational', 'streaming', 'interactive', 'background']
Definition: Type of application for which the Radio Access Bearer service is optimized.
Purpose: By including the traffic class itself as an attribute, UTRAN can make assumptions about the traffic source and
optimize the transport for that traffic type. In particular, buffer allocation may be based on traffic class.
The type of application is indicated by reference to the UMTS traffic classes.
Current R99 RABs P4

A radio access bearer (RAB) connection via UTRAN is realised by two concatenated segments, the Iu bearer connection
and the radio bearer connection and slides 4-7 illustrate the mapping of radio bearer connections on logical, transport
and physical channels.
Each of the RABs (note: the discussion below only concerns the user plane in the right part of slides 4-4) is mapped onto
one or more radio bearers. More than one radio bearer may be used if the user data can be separated into different
subflows with different error protection needs.
Each radio bearer is mapped on one radio link control (RLC) entity.
Each RLC entity in the RNC communicates with its peer entity in the UE with one or more logical channels. Depending on
the service required from the RLC, logical channels are configured for operation in Transparent Mode (TM),
Unacknowledged Mode (UM) or Acknowledged Mode (AM) (the option of using different logical channels for transfer of
data and control PDUs (Protocol Data Units) in the RLC AM data is not used in UTRAN P1).
The logical channels carrying user plane traffic, i.e. DTCHs are mapped onto dedicated (DCH) or common (RACH/FACH)
transport channels as specified for each multiplexing option. A radio bearer may have more than one multiplexing
option, where each option specifies a particular mapping on dedicated or common physical channels.
Radio bearers using TM RLC for support of CS services require dedicated transport and physical channels, while radio
bearers using AM RLC for support of best effort packet data services can use either dedicated or common physical
channels.
The radio bearer logical channel, DTCH, is multiplexed with other logical channels on the RACH and FACH transport
channels used for transfer over the common physical channels PRACH and S-CCPCH
User data at the UTRAN service access points is represented as RAB SDUs (Service Data Units). Each RAB SDU is
transferred via the Iu interface in the payload field of a Iu user plane PDU (Protocol Data Unit).
The SDU size can be specified as one or more fixed sizes per RAB or as a variable size with a specified maximum.
A RAB SDU may be structured in RAB subflow SDUs, in which case the number of bits per subflow SDU is specified in the
SDU format information provided in the RAB assignment request.
Higher layer data units i.e. RAB or RAB subflow data units or RRC messages are mapped on SDUs of the RLC layer. These
SDUs are within the RLC layer mapped onto RLC PDUs. The mapping depends on the RLC mode (TM, UM or AM, called
TrD, UMD or AMD for RLC PDUs) used to handle the data flow for each RAB connection or RRC message.
Each RLC PDU is mapped onto one and only one transport block.
On dedicated transport channels, the transport block size is the same as the RLC PDU size except in the case of
multiplexing of logical channels on the same transport channel.
HSDPA RABs P4
Interactive 64/HS kbps PS RAB
UL: Interactive 64 kbps PS RB
DL: Interactive PS RB on HS-DSCH
Interactive 384/HS kbps PS RAB (optional)
UL: Interactive 384 kbps PS RB
DL: Interactive PS RB on HS-DSCH