Last updated: 2014-11-28
Automatic RRC State Transitions
This parameter determines the Radio Access Bearer configuration. The GPRS RABs available in the test set include:
64k UL / HSDPA DL PS Data RAB (3GPP TS 34.108 V8.0.0 S6.11.5.4.6.4)
384k UL / 384k DL PS Data RAB (3GPP TS 34.108 V11.1.0 S6.11.5.4.1.34). Refer to GPRS PS Data service for more information.
HSUPA UL / HSDPA DL PS Data RAB (3GPP TS 34.108 V11.1.0 S6.11.5.4.1.34).
This setting can only be changed while the Call/Data Status is Idle. Otherwise, it will post the error +201 (+200 through +299 Error Message Descriptions)
GPIB Command: CALL:SERVice:GPRS:RAB
You must set up the DUT IP before setting up a packet data connection.
DUT IP Address
This setting sets up the wireless device's IP address.
GPIB Command: CALL:MS:IP:ADDRess[1]
DUT Primary DNS Server IP Address
As part of the PS data call setup procedures, the UE can include PPP/IPCP messages that ask the network for the IP addresses of the DNS servers that it should use to resolve domain names. These PPP/IPCP messages are carried as part of the PDP Context Activation message and in them the UE can request either the Primary DNS Server address or the Secondary DNS Server address or both. If the UE requests either one or both of the DNS server addresses and they are set to 0.0.0.0, the test set does not respond to the UE, returns an error, and then proceeds with the PDP Context Activation. If the UE requests both of the DNS server addresses and either one contains a value other than 0.0.0.0, that address is sent to the UE.
GPIB Command:
DUT Primary DNS Server IP Address - CALL:MS:DNSServer:PRIMary:IP:ADDRess
DUT Secondary DNS Server IP Address - CALL:MS:DNSServer:SECondary:IP:ADDRess
When a packet data connection is established, the test set keeps a count of the number of Internet Protocol (IP) data units that are transferred on both the forward (network to UE) and reverse (UE to network) directions. The recorded information is displayed on the Counters table.
DUT IP TX Bytes - This is the total number of IPv4 Bytes received by the test set from the UE on all activated PDP context.
DUT IP TX Packets - This is the total number of IPv4 Packets received by the test set from the UE on all activated PDP context.
DUT IP RX Bytes - This is the total number of IPv4 Bytes sent from the test set and destined for the UE on all activated PDP context.
DUT IP RX Packets - This is the total number of IPv4 Packets sent from the test set and destined for the UE on all activated PDP context.
DUT IP TX Bytes / Packets: CALL:COUNt:MS:IP:TX:[TOTal]?
DUT IP RX Bytes / Packets: CALL:COUNt:MS:IP:RX:[TOTal]?
This action clears the contents of all the IP counters.
GPIB Command: CALL:COUNt:CLEar:MS:IP
The Data Throughput Monitor can analyze data transfer rates under various RF and call processing conditions. You can initiate the Data Throughput Monitor by pressing the Instrument selection key. It is displayed on the Measurement/Instrument screen (accessible using the MEASUREMENT key).
Data throughput is the rate of data transfer to and from a UE.
Two sets of statistics are available from the Data Throughput Monitor:
OTA Rx and OTA Tx
OTA (Over the Air) throughput counts the data transmitted and received by the test set's protocol stack. The location of the measurement point in the protocol stack is dependent upon system type; this data could be a byte stream from RLP (Radio Link Protocol) or RLC (Radio Link Control) or PPP (point to point protocol). OTA throughput does not count physical layer overhead such as mid-amble, guard, or tail bits, or bits added by the encoding process.
IP Rx and IP Tx
IP (Internet Protocol) throughput counts the data transmitted and received by the test set. It measures the IP data transferred between the external LAN connector and the protocol stack. It provides a measure of the IP data packets being transferred to/from the wireless device.
When the Data Throughput Monitor is selected and a data call is connected, the test set accumulates data throughput statistics. If a data call is disconnected, data accumulation is suspended until another connection is made and data accumulation continues. Data accumulation can be cleared by performing a measurement reset or clearing the graph.
The test set provides two tools to analyze data throughput:
Graphical trace
Summary table
The graphical trace presents up to the most recent 600 seconds (10 minutes) of data throughput statistics. Each of the following color-coded traces can be turned on or off:
OTA Tx - (Over The Air Transmitted bits-per-second). This is the rate of link-layer bit transfer sent from the wireless device. In other words, OTA translates into RLP (Radio Link Protocol) in cdma2000 and 1xEV-DO, or RLC (Radio Link Control) protocol in W-CDMA and GPRS, or PPP in GSM. Tx refers to the reverse or uplink channel direction.
OTA Rx - (Over The Air Received bits-per-second). This is the rate of link-layer bit transfer received by the wireless device. In other words, OTA translates into RLP (Radio Link Protocol) in cdma2000 and 1xEV-DO, or RLC (Radio Link Control) protocol in W-CDMA and GPRS, or PPP in GSM. Rx refers to the forward or downlink channel direction.
IP Tx - Internet Protocol Transmitted. This is the rate of network-layer bit transfer sent by the wireless device. Tx refers to the reverse or uplink channel direction.
IP Rx - Internet Protocol Received. This is the rate of network-layer bit transfer received by the wireless device. Rx refers to the forward or downlink channel direction.
Context 1 Tx - Internet Protocol Context 1 Transmitted. This is the rate of context 1 network-layer bit transfer sent by the wireless device. Tx refers to the reverse or uplink channel direction.
Context 1 Rx - Internet Protocol Context 1 Received. This is the rate of context 1 network-layer bit transfer received by the wireless device. Rx refers to the forward or downlink channel direction.
Four sets of Context <n> traces can be set: Context 1 Tx/Rx, Context 2 Tx/Rx, Context 3 Tx/Rx and Context 4 Tx/Rx. Totally there are 12 traces results are available form the Data Throughput Monitor, but six of them can be display on the screen at one time. The users can choose which traces are to be displayed by pressing Trace Display softkey.
Note that for an application that dose not support counters for multiple Contexts, the "Context<n>" counts will always be zero (a trace will still be available but every point will be "0").
A marker can be assigned to each trace to display instantaneous numeric data throughput values. Markers can be used in conjunction with the Freeze Graph feature to analyze points of interest on traces.
The summary table provides the latest statistics for the four monitored measurements. Each measurement is displayed with the following statistics:
Marker
The data rate at the measurement's marker position in bits-per-second.
Current
The measurement's instantaneous data in bits-per-second.
Average
The measurement's average data rate in bits-per-second over the length of the data connection or since the last time the measurement was cleared.
Peak
The measurement's peak data rate in bits-per-second over the length of the data connection or since the last time the measurement was cleared.
Data Transfer
The measurement's total data throughput count, in bytes, over the length of the data connection or since the last time the measurement was cleared
The automatic RRC state transitions are driven by a type of trigger as below:
Automatic RRC State Transitions
This setting controls whether the automatic RRC state transitions are enabled or not (including the transition based on downlink IP data).
GPIB Command: CALL:SERVice:PSData:RRC:TRANsition:AUTO
CELL_DCH Inactivity Timer Length
This setting controls the transaction that are triggered from PDP_ACTIVE state to IDLE.
GPIB Command: CALL:SERVice:PSData:RRC:TRANsition:ITIMer:DCH:VALue