Model Limitations

The following UMTS protocol features are not explicitly modeled.

  • IPv6 over UMTS. This type of configuration is not supported.
  • Synchronization at power-on. The various synchronization that occurs when a user powers-on is not modeled, with the exception of the GPRS attach procedure.
  • GMM-Idle mode. Only the GMM-Connected mode is modeled.
  • GPRS detach. It is assumed that a UE remains attached for the remainder of the simulation.
  • PDP context deactivation and reactivation. During a simulation, PDP context activation occurs only once for each QoS profile. The PDP context is not deactivated and is reused the next time a UE requests the QoS profile associated with the PDP.
  • QoS Parameters. Uplink and downlink data rates are the only negotiable QoS parameters. Maximum Bit Rate Uplink/Downlink are the desired data rates for a UE. Guaranteed Bit Rate Uplink/Downlink are the lowest data rates a UE can accept. The UE will accept either maximum bit rate or guaranteed bit rate through a negotiation or renegotiation process initiated by the RNC.
  • QoS negotiation/renegotiation. QoS negotiation during the relocation procedure (Section 7 in TS25.946) is not supported. QoS negotiation/ renegotiation are solely initiated by the RNC. The RNC knows all QoS parameters acceptable to the UE. The UE will always accept the negotiated/ renegotiated bit rates from the RNC.
  • No support for repeater chaining. Repeater chaining is not supported.
  • IP Support between RNC and Node-B. Only UDP will be used for Iub transport layer. Only IP transport will be supported for Node-B to RNC transport. Simultaneous use of ATM and IP interfaces for Node-B to RNC transport will not be supported.
  • No support for parallel spreading codes on dedicated channel. Dedicated channels do not support parallel codes. This limits the maximum data rate a single channel can support.
  • No support for high-speed downlink packet access (HSDPA). Though the model is based on Release-5, HSDPA is not supported.
  • CPCH, PCPCH. The common packet channel (CPCH) and the physical common packet channel (PCPCH) are not modeled.
  • System information, cell selection, and PLMN are not modeled.
  • No mobility prior to attachment. At start time, the model attaches each UE to the closest Node-B (determined based on path loss). No mobility is modeled prior to attachment and UEs begin monitoring their location after attachment.
  • RNC to SGSN connectivity. RNCs must be connected to SGSNs directly using ATM, Ethernet, or PPP links. The models do not support having routers or switches between RNCs and SGSNs. An RNC will be able to be served by any SGSN to which it is directly connected. There is no explicit signaling between the RNC and its SGSNs for discovery of serving SGSNs.
  • Load Sharing. User will configure each UE with the ID of the SGSN it is to use. Dynamic load sharing in the RNC will not be modeled.
  • Load Balancing. RNCs will not do load balancing. The UE will specify the serving SGSN.
  • Inter-RNC and inter-SGSN handovers. UE handovers are not supported between RNCs or between SGSNs.
  • Handover in FACH/RACH. Handover is not supported for UEs using the common channels FACH/RACH (that is, the UEs in the CELL_FACH state).