Model Features and Limitations

Model Features

The following table lists the main UMTS features included in the implementation of the UMTS model.

Table 234: Model Features

Feature Description
GPRS attach The GPRS attach procedure informs the SGSNs when the user equipment (UE) is at power-on and of its GPRS capability. The model assumes that a PS signaling connection is already set up.
For more information, see GPRS Attach.
GTP The GPRS Tunneling Protocol (GTP) protocol, which is used in the RNC/SGSN/GGSN nodes to encapsulate IP packets in the core network is modeled. The CN can be configured using Service GPRS Support Nodes (SGSN) and Gateway GPRS Support Nodes (GGSN). The core network supports IP, ATM, or Ethernet technologies as a part of the backbone that interconnects SGSN and GGSN nodes. GTP tunnels are extended up to the Radio Network Controller (RNC).
For more information, see CN Architecture.
PDP context activation On receipt of PDUs (protocol data units), the UE or network activates a PDP (Packet Data Protocol) context if one is not already activated. The PDP context activation includes the requested QoS (Quality of Service) profile associated with the traffic class of the PDUs received. Once activated, a PDP context remains active for the rest of the simulation. The model assumes that a PS (packet switched) signaling connection is already established for the PDP context activation procedure.
For more information, see PDP Context Activation and RAB Assignment (MS-Connected State).
RAB Setup, Release, Negotiation, Renegotiation, and Preemption When a UE receives data belonging to a traffic class for which a PDP context has already been activated, but no RAB (Radio Access Bearer) exists, it can dynamically request the setup of a RAB through the service request procedure. RABs are set up by the network, which later releases the RAB if it detects that the RAB has been idle for some time.
RABs can also be released due to preemption to free resources in the cell for the admission of higher priority QoS RABs.
RABs can also be released due to the failure of RAB modification.
An SGSN can also initiate a RAB for a UE that receives data for a QoS category for which it does not have an active RAB.
During setup, a RAB can be admitted with its maximum bit rate or guaranteed bir rate. Negotiation occurs when the RAB cannot be admitted with its maximum rate, but is admissible with a guaranteed rate that is lower than the maximum rate.
The admission of a high-priority RAB may cause a lower-priority RAB to be renegotiated instead of being preempted. When this occurs, the rate of the low-priority RAB is reduced from its maximum rate to its guaranteed rate.
For more information, see RAB Assignment with Prior PDP Activation (MS-Connected State).
Service Request See above (RAB setup/release).
Repeaters A repeater can be used to extend the coverage area of a Node-B cell, improve signal strength (especially in downlink), and get around physical obstacles.
RLC Modes: AM, UM, TrM Three RLC modes are supported: acknowledged mode (AM), unacknowledged mode (UM), and transparent mode (TrM). RLC modes impact throughput and delay due to their different algorithms.
For more information, see UE Process Model Architecture.
Priority handling of data flows based on traffic class at MAC Each traffic class is assigned a different priority and the MAC can handle data flows of different priority levels.
For more information, see UE Node Model Architecture.
Traffic classes The four traffic classes defined in UMTS are supported: conversational, streaming, interactive, and background. You can use a mix of different traffic classes for each UE.
One QoS profile per traffic class of a UE Each traffic class is associated with a configurable QoS profile (consisting of: data rate, priority level, preemption capability, vulnerability,…). This QoS profile is the QoS requested by the UE in the PDP context activation procedure.
Support of TCP/IP stack TCP (UDP) and IP layers are implemented at the UE. The IP layer is also implemented at CN nodes.
For more information, see UE Node Model Architecture.
W-CDMA air interface (FDD mode only) Only the FDD mode is supported. Packet dropping probability is based on curves obtained from another set of simulations of the W-CDMA air interface (accurate to the waveform level).
Admission Control Two admission control algorithms are modeled: a default algorithm and a throughput-based algorithm. The throughput-based admission control algorithm is implemented using formulae from "WCDMA for UMTS" by Holma et al. The default admission control algorithm is proprietary.
For more information, see RNC Process Model.
DCH Uplink and downlink dedicated signaling channels (DCHs) are used for all signaling messages between UE and UTRAN/CN. Signaling DCHs are established when needed and modeled with high fidelity. DCHs are configurable on a per-QoS basis for each RNC.
DSCH The model supports the DSCH (Downlink Shared Channel), which can be used by UEs in CELL_DCH state for downlink communications. Each RNC deploys a single DSCH for each cell it manages. All DSCHs of an RNC use the same customizable configuration.
For more information, see RNC Process Model.
FACH (Forward Access channel)
RACH (Random Access Channel)
The UE CELL_FACH state is modeled. A UE in the FACH state uses the RACH channel for uplink transmissions and the FACH channel for downlink transmissions. FACH scheduling follows a weighted round-robin approach and allows you to assign weights according to QoS class.
Contention in the RACH channel is based on the Slotted ALOHA approach with fast acquisition indication. The power ramp up procedure is modeled as an open loop power control feature. Access service classes are configurable and can be mapped from the UMTS QoS classes.
For more information, see UE Process Model Architecture.
UMTS RLC SDU (Service Data Unit) Concatenation The model supports RLC concatenation of SDUs. When this feature is enabled, the RLC layer may concatenate multiple SDUs on every transmission time interval (TTI). This feature is supported only for RLC acknowledged and unacknowledged modes. It can be enabled/disabled on per QoS basis within the data channel configuration (per QoS) at the RNC node.
Power control Outer loop power control is supported.
For outer loop power control, the model increases the receiver's target signal to noise ratio (Eb/No) by 1.0 dB for every received packet it rejects because of unrecoverable bit errors. When the receiver gets a packet that has no unrecoverable errors the model decreases the target Eb/No by x dB, where x is 1* requested BLER (block error rate). Then, by using the new target Eb/No, changes, the model adjusts the power accordingly. (Based on algorithm presented in Holma and Toskala—see Reference Documents.)
UE mobility Movement of a UE within a cell is modeled.
Logical and transport channels UMTS models allow the mapping of logical channels to transport channels, and enable a queuing scheme for logical channel to transport channel multiplexing.
UE can have up to 4 data transport channels for uplink and downlink, and 1 signaling transport channel for uplink and downlink. Three scheduling schemes will be used for logical channel multiplexing in the MAC: Strict Priority, Weighted Round Robin, and Modified Weighted Round Robin.
Signaling messages Signaling messages will be queued until signaling DCH is established. No expiration means no matter how long establishment takes, and Infinite queue means no matter how many messages must be queued. The following procedure will be followed for each signaling message to be sent: Send message on existing signaling DCH. If no existing signaling DCH, request one from admission control. If request is rejected, use common channels to forward the message.
Intra-RNC hard and soft handovers UMTS models both hard and soft handovers of the UEs between the Node-Bs of the same RNC. Soft handovers within an RNC is modeled based on 3GPP's release 1999 standards. UMTS also supports soft handover events 1A, 1B, and 1C (active cell addition, removal, and replacement procedures, respectively.
Softer handovers—among the cells/sectors of a Node-B—are also modeled.
For more information, see Signal Flows for Hard Handover and Signal Flows for Soft Handover.
IP Support between RNC and Node-B RNC and Node-B node models are enhanced to include the IP protocol stack. These enhancements provide the option of using IP transport for Radio Access Network (RAN) signaling, in addition to AAL5 transport.
RNC to SGSN connectivity An RNC node is able to connect to multiple SGSN nodes. Load sharing is possible between multiple SGSNs connected to a single RNC.