Agilent Confidential Export Allowed

W-CDMA/HSPA Multiple PDP Contexts User Guide

Revision 1, 14 October 2010

Description
Multiple PDP (packet data protocol) contexts is the phrase used to describe the configuration in W-CDMA/HSPA where more than one packet-switched (PS) data session is active simultaneously. This configuration is used frequently with two data applications simultaneously, e.g., reading e-mail and browsing the web. There are two types of PDP contexts. Primary PDP contexts require an independent Internet protocol (IP) address. Each primary PDP context allows access to a different packet data network (PDN). Secondary PDP contexts can be initiated from any already active primary PDP context. A secondary PDP context uses the same IP address as the primary PDP context, but still allows the use of data applications independent from the primary PDP context. A secondary PDP context allows access to the same PDN as the primary PDP context, but with different quality of service (QoS) attributes. The network determines whether any PDP context can be initiated by replying to and configuring requests from the wireless device or user equipment (UE). The UE can request primary or secondary PDP contexts, but only the network can activate a context. The UE can request specific QoS attributes for a PDP context, but only the network decides what QoS attributes are used. The network can also initiate PDP contexts directly without waiting for a request from the UE. Either the UE or the network can end an existing PDP context. All of this is done using layer 3 Radio Resource Control (RRC) messaging between the UE and the network. There are many QoS attributes to configure for each PDP context. The 3GPP standards define these attributes and the signaling used to configure them. Two 3GPP standards are the best references for QoS attributes: 3GPP TS 23.107 s6.4.4.1 and 3GPP TS 24.008 s10.5.6.5. More details about the attributes are provided later in this document. For reference, multiple PDP contexts are not the same as simultaneous services. In W-CDMA/HSPA, simultaneous services refer to the use of voice and data simultaneously. Multiple PDP contexts refer to the use of more than one PS data session simultaneously. The two can be combined, however, to provide voice and multiple PS data sessions simultaneously. Once again, this is a common configuration in networks, e.g., talking with a colleague while making a dinner reservation on line, and checking e-mail.

8960 Support of Multiple PDP Contexts

The 8960 supports multiple PDP contexts initially in the E6703G W-CDMA/HSPA LA revision G.01 officially released at the end of December 2010. This capability is not supported in the E1963A W-CDMA/HSPA TA. The following bullets describe what is and is not supported in this initial release. Future releases may add more capability.

Is Supported
Two primary PDP contexts (attempts to establish additional contexts ignored) Two IPv4, two IPv6 or one IPv4 and one IPv6 PDP contexts 64k UL/DL and HSPA UL/DL PS data RABs (other RABs rejected with an error message)
Page 1

Agilent Confidential Export Allowed

Settable independent QoS parameters as follows for each PDP context (parameters signaled to UE, but no physical changes made to 8960 downlink) - Traffic Class - Uplink Bit Rate Maximum - Downlink Bit Rate Maximum - Uplink Bit Rate Guaranteed - Downlink Bit Rate Guaranteed - Delivery Order - SDU Maximum Size - SDU Error Ratio - Residual Bit Error Ratio - SDU Error Delivery - Transfer Delay - Traffic Handling Priority - Signaling Indication Second primary PDP context initiated by the UE End Call used to end both PDP contexts PDP context reject codes applicable when either PDP context is requested PDP context activation ignore applicable when either PDP context is requested APNs defined for acceptance or rejection applicable when either PDP context is requested

Is Not Supported
More than two PDP contexts Second primary PDP context initiated by the 8960 RABs other than 64k UL/DL and HSPA UL/DL Secondary PDP contexts Voice call or CS data with two PDP contexts Multiple PDP contexts during 2-box soft handover Multiple PDP contexts with RRC states other than CELL_DCH Multiple PDP contexts using DL power control Multiple PDP contexts using ciphering Multiple PDP contexts with compressed mode enabled Multiple PDP contexts with CPC enabled

8960 Behavior with Multiple PDP Contexts QoS Attributes and PS Data Configurations
In a real network, the QoS attributes are requested by the UE and configured by the network. The 8960 allows the QoS attributes for each PDP context to be configured independently. However, the 8960 does not change its transmission and reception behavior according to the QoS attributes. The 8960 does signal the selected QoS attributes to the UE in the Active PDP Context Accept message. This means that the 8960 continues to establish the requested PDP context based on the radio access bearer (RAB) selected using the GPRS Radio Access Bearer parameter as has always
Page 2

Agilent Confidential Export Allowed

been done in the past. This RAB is used for both simultaneous PDP contexts. In the initial release, the 64k PS and HSUPA UL / HSDPAS DL PS RABs can be selected for use with multiple PDP contexts. All other selections cause the second primary PDP context request to be ignored by the 8960. A warning message is posted when this occurs. The PS Data SRB Mapping Mode must be selected as UL E-DCH/DL DCH for use with multiple PDP contexts. All other selections cause the second primary PDP context request to be ignored by the 8960. A warning message is posted when this occurs.

Activation and Deactivation of Multiple PDP Contexts

During the transition from a single active PDP context to two active PDP contexts, the 8960 uses the Radio Bearer (RB) Release and RB Setup procedures as defined in 3GPP TS 25.331. The RB Release procedure is used to reconfigure the RAB used by the single active PDP context. The RB Setup procedure is then used to set up the two active PDP contexts. Finally, the second PDP context is configured and the PDP Context Activation Accept message is sent from the network to the UE. This same process is used to transition from two active PDP contexts to a single active PDP context except in this case the Deactivate PDP Context Accept message is sent. During the procedure to activate the second PDP context, if the 8960 does not receive either the RB Release Complete or RB Setup Complete messages from the UE, an error is posted, but the activation procedure continues. Also, during the procedure to activate the second PDP context, if the UE sends an RB Setup Failure message as a response, the 8960 ignores the message and continues with the activation procedure. However, when the 8960 sends the Activate PDP Context Accept message to the UE, no response is received so the RRC connection is released. The existing capability to ignore Activate PDP Context Requests from the UE is applicable to multiple PDP contexts. If Activate PDP Context Ignore State is selected as On, any PDP Activation Request from the UE is ignored no matter which PDP context is requested. The existing capability to reject Activate PDP Context Requests from the UE is also applicable to multiple PDP contexts. If Activate PDP Context Reject State is selected as On, then any Activate PDP Context Request from the UE is rejected with the selected Session Management (SM) cause no matter which PDP context is requested. The existing access point name (APN) capability is also applicable to multiple PDP contexts. Any APN that is configured to be rejected by the 8960 is rejected when it is requested for use by the UE in any Activate PDP Context Request message no matter which PDP context is requested. During the procedure to deactivate one of the two active PDP contexts, if the 8960 does not receive either the RB Release Complete or RB Setup Complete messages from the UE, an error is posted, but the deactivation procedure continues. Also, during the procedure to deactivate one of the two active PDP contexts, if the UE sends an RB Setup Failure message as a response, the 8960 ignores the message and continues with the deactivation procedure. However, when the 8960 sends the Deactivate PDP Context Accept message to the UE, no response is received so the RRC connection is released.

Page 3

Agilent Confidential Export Allowed

Handling of Unsupported Configurations

The 8960 posts an error and does not allow any of the following functionality to start if two PDP contexts are currently active: two-box handovers, RRC state transitions, downlink (DL) power control, ciphering, compressed mode, continuous packet connectivity (CPC), and simultaneous services. Similarly, the 8960 posts an error and does not allow a second PDP context to be started when any of the following functionality is currently active: two-box handovers, RRC state transitions, DL power control, ciphering, compressed mode, CPC, and simultaneous services.

8960 Usage of Multiple PDP Contexts

Several new settings and results are added or modified to provide support for two primary PDP contexts. The following sections describe these settings and results and how to access them from the front panel and over GPIB. Unless otherwise noted, all settings can only be changed when the connection state is Idle.

DUT IP Settings
DUT IP 2 Version This setting allows selection of the IP version for the DUTs second primary PDP context. When a connection is negotiated, if this setting is IPv4, only IPv4 connections can be set up. If this setting is IPv6, only an IPv6 connection can be set up. If this setting is IPv4 + IPv6 (Dual), both IPv4 and IPv6 connections can be set up. The settings DUT IP 2 Version and the existing DUT IP Version are independent. There are several error conditions which are handled by the 8960 as follows. If DUT IP 2 Version is selected as IPv4 and the UE requests PDP Type Ipv4v6, the 8960 sets the PDP Type to IPv4 and the SM cause to #50, PDP Type IPv4 Only Allowed, when the Activate PDP Context Accept message is sent to the UE. If DUT IP 2 Version is selected as IPv6 and the UE requests PDP Type Ipv4v6, the 8960 sets the PDP Type to IPv6 and the SM cause to #51, PDP Type IPv6 Only Allowed, when the Activate PDP Context Accept message is sent to the UE. If DUT IP 2 Version is selected as IPv4 and the UE requests PDP Type Ipv6, the 8960 sets the SM cause to #50, PDP type IPv4 Only Allowed, and rejects the request by sending an Activate PDP Context Reject message to the UE. If DUT IP 2 Version is selected as IPv6 and the UE requests PDP Type Ipv4, the 8960 sets the SM cause to #51, PDP type IPv6 Only Allowed, and rejects the request by sending an Activate PDP Context Reject message to the UE. Range: IPv4, IPv6, IPv4 + IPv6 (Dual) Default: IPv4 GPIB: CALL:MS:IP:VERSion2 IP4|IP6|DUAL

Page 4

Agilent Confidential Export Allowed

This setting is located on the front panel under the IP Addressing Info menu. Press CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F5 IP Addressing Info, F2 DUT IP Setup.

DUT IP Address 2 This setting defines the IPv4 address for the second primary PDP context. This address is used if DUT IP 2 Version is selected as IPv4 or IPv4 + IPv6 (Dual) and the UE requests a second primary PDP context with PDP Type Ipv4 or Ipv4v6. Then the 8960 assigns the DUT IP Address 2 and signals it to the UE. DUT IP Address 2 must be on the same subnet as the 8960, so the 8960s Subnet Mask must be set to the same subnet as the DUTs. In addition, DUT IP Address 2 must differ from DUT IP Address which is the DUT IP address for the first primary PDP context. If either of these two conditions is not met, the 8960 posts an error message. If an IPv4 connection is requested by the UE during the Primary PDP Context Activation procedure and DUT IP Address 2 is blank, the 8960 rejects the request and posts an error message. This setting is saved across presets and power cycles. Range: or 0.0.0.0 to 225.255.255.255 Default: Blank GPIB: CALL:MS:IP:ADDRess2

Page 5

Agilent Confidential Export Allowed

This setting is located on the front panel under the IP Addressing Info menu. Press CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F5 IP Addressing Info, F2 DUT IP Setup.

DUT IP Address 1 Primary QoS Profile This setting allows the user to configure the QoS parameters for the first primary PDP context. If selected as None, the requested QoS attributes from the UE are used unless a value is out of the range allowed by the 8960. In this case, the 8960 uses its default value for this QoS parameter. If selected as QoS Profile 1, the requested QoS attributes from the UE are ignored and the 8960 sets the QoS attributes according to the values of the first QoS profile (QoS Profile 1 Traffic Class, QoS Profile 1 SDU Maximum Size, etc.). If selected as QoS Profile 2, the requested QoS attributes from the UE are ignored and the 8960 sets the QoS attributes according to the values of the second QoS profile (QoS Profile 2 Traffic Class, QoS Profile 2 SDU Maximum Size, etc.). The 8960 signals the QoS attributes to the UE in the Activate PDP Context Accept message. Range: None, QoS Profile 1, QoS Profile 2 Default: None GPIB: CALL:MS:IP:ADDRess[1]:CONText:PRIMary:QOService NONE| QOSProfile1|QOSProfile2

Page 6

Agilent Confidential Export Allowed

This setting is located on the front panel under the Multiple PDP Contexts Parm menu. Press CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F4 Multiple PDP Contexts Info, F1 Multiple PDP Contexts Parm.

DUT IP Address 2 Primary QoS Profle This setting allows the user to configure the QoS parameters for the second primary PDP context. If selected as None, the requested QoS attributes from the UE are used unless a value is out of the range allowed by the 8960. In this case, the 8960 uses its default value for this QoS parameter. If selected as QoS Profile 1, the requested QoS attributes from the UE are ignored and the 8960 sets the QoS attributes according to the values of the first QoS profile (QoS Profile 1 Traffic Class, QoS Profile 1 SDU Maximum Size, etc.). If selected as QoS Profile 2, the requested QoS attributes from the UE are ignored and the 8960 sets the QoS attributes according to the values of the second QoS profile (QoS Profile 2 Traffic Class, QoS Profile 2 SDU Maximum Size, etc.). The 8960 signals the QoS attributes to the UE in the Activate PDP Context Accept message. Range: None, QoS Profile 1, QoS Profile 2 Default: None GPIB: CALL:MS:IP:ADDRess2:CONText:PRIMary:QOService NONE| QOSProfile1|QOSProfile2 This setting is located on the front panel under the Multiple PDP Context Parm menu. Press CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F4 Multiple PDP Contexts Info, F1 Multiple PDP Contexts Parm.
Page 7

Agilent Confidential Export Allowed

QoS Profile 1 Settings

The following settings define the QoS attributes to be used when QoS Profile 1 is selected. All of these values are sent to the UE in an Activate PDP Context Accept message when QoS Profile 1 is selected for either DUT IP Address 1 Primary QoS Profile or DUT IP Address 2 Primary QoS Profile. All of these settings are located on the front panel under the Multiple PDP Context Parm menu. Press CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F4 Multiple PDP Contexts Info, F2 QoS Profile 1 Setup.

QoS Profile 1 Traffic Class Range: Conversational, Streaming, Interactive, Background Default: Interactive GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:TCLass CONVersation| STReaming|INTeractive|BACKground QoS Profile 1 Uplink Bit Rate Maximum The value of this setting is signaled to the UE as the Maximum Bit Rate for Uplink and Maximum Bit Rate for Uplink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 1 Uplink Bit Rate Maximum must be greater than or equal to QoS Profile 1 Uplink Bit Rate Guaranteed. Values less than the currently selected value of QoS Profile 1 Uplink Bit Rate Guaranteed are rejected and an error message is posted.

Page 8

Agilent Confidential Export Allowed

Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 64 kbps GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:UPLink:BRATe[:MAXimum] QoS Profile 1 Downlink Bit Rate Maximum The value of this setting is signaled to the UE as the Maximum Bit Rate for Downlink and Maximum Bit Rate for Downlink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 1 Downlink Bit Rate Maximum must be greater than or equal to QoS Profile 1 Downlink Bit Rate Guaranteed. Values less than the currently selected value of QoS Profile 1 Downlink Bit Rate Guaranteed are rejected and an error message is posted. Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 64 kbps GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:DOWNlink:BRATe[:MAXimum] QoS Profile 1 Uplink Bit Rate Guaranteed The value of this setting is signaled to the UE as the Guaranteed Bit Rate for Uplink and Guaranteed Bit Rate for Uplink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 1 Uplink Bit Rate Guaranteed must be less than QoS Profile 1 Uplink Bit Rate Maximum. Values greater than or equal to the currently selected value of QoS Profile 1 Uplink Bit Rate Maximum are rejected and an error message is posted. Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 1 kbps GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:UPLink:BRATe:GUARanteed QoS Profile 1 Downlink Bit Rate Guaranteed The value of this setting is signaled to the UE as the Guaranteed Bit Rate for Downlink and Guaranteed Bit Rate for Downlink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 1 Downlink Bit Rate Guaranteed must be less than QoS Profile 1 Downlink Bit Rate Maximum. Values greater than or equal to the currently selected value of QoS Profile 1 Downlink Bit Rate Maximum are rejected and an error message is posted.
Page 9

Agilent Confidential Export Allowed

Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 1 kbps GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:DOWNlink:BRATe: GUARanteed QoS Profile 1 Delivery Order If selected as On, the Deliver Order IE in the Activate PDP Context Accept message is signaled as With Delivery Order. If selected as Off, it is signaled as Without Delivery Order. Range: On, Off Default: On GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:DORDer ON|1|OFF|0 QoS Profile 1 SDU Maximum Size If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. Range: 10 to 1500 bits with resolution 10 bits, 1502 bits, 1510 bits, 1520 bits Default: 1500 bits GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:SDU:SIZE[:MAXimum] QoS Profile 1 SDU Error Ratio Range: 1E-2, 7E-3, 1E-3, 1E-4, 1E-5, 1E-6, 1E-1 Default: 1E-4 GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:SDU:ERATio R1ENegative2|R7ENegative3|R1ENegative3|R1ENegative4| R1ENegative5|R1ENegative6|R1ENegative1 QoS Profile 1 Residual Bit Error Ratio Range: 5E-2, 1E-2, 5E-3, 4E-3, 1E-3, 1E-4, 1E-5, 1E-6, 6E-8 Default: 1E-4 GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:RBERatio R5ENegative2| R1ENegative2|R5ENegative3|R4ENegative3|R1ENegative3| R1ENegative4|R1ENegative5|R1ENegative6|R6ENegative8 QoS Profile 1 SDU Error Delivery Range: No Detect, Delivered, Not Delivered Default: Not Delivered GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:SDU:EDELivery NDETect| DELivered|NDELivered

Page 10

Agilent Confidential Export Allowed

QoS Profile 1 Transfer Delay Range: 10 to 150 ms with resolution 10 ms, 200 to 950 ms with resolution 50 ms, 1000 to 4000 ms with resolution 100 ms Default: 100 ms GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:TDELay QoS Profile 1 Traffic Handling Priority Range: 1, 2, 3 Default: 2 GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:THPRiority QoS Profile 1 Signaling Indication Range: Optimised, Not Optimised Default: Not Optimised GPIB: CALL:SERVice:PSData[:QOSProfile[1]]:SINDication OPTimised| NOPTimised

QoS Profile 2 Settings

The following settings define the QoS attributes to be used when QoS Profile 2 is selected. All of these values are sent to the UE in an Activate PDP Context Accept message when QoS Profile 2 is selected for either DUT IP Address 1 Primary QoS Profile or DUT IP Address 2 Primary QoS Profile.

Page 11

Agilent Confidential Export Allowed

All of these settings are located on the front panel under the Multiple PDP Context Parm menu. Press CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F4 Multiple PDP Contexts Info, F2 QoS Profile 2 Setup.

QoS Profile 2 Traffic Class Range: Conversational, Streaming, Interactive, Background Default: Interactive GPIB: CALL:SERVice:PSData:QOSProfile2:TCLass CONVersation| STReaming|INTeractive|BACKground QoS Profile 2 Uplink Bit Rate Maximum The value of this setting is signaled to the UE as the Maximum Bit Rate for Uplink and Maximum Bit Rate for Uplink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 2 Uplink Bit Rate Maximum must be greater than or equal to QoS Profile 2 Uplink Bit Rate Guaranteed. Values less than the currently selected value of QoS Profile 2 Uplink Bit Rate Guaranteed are rejected and an error message is posted. Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 64 kbps GPIB: CALL:SERVice:PSData:QOSProfile2:UPLink:BRATe[:MAXimum]

Page 12

Agilent Confidential Export Allowed

QoS Profile 2 Downlink Bit Rate Maximum The value of this setting is signaled to the UE as the Maximum Bit Rate for Downlink and Maximum Bit Rate for Downlink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 2 Downlink Bit Rate Maximum must be greater than or equal to QoS Profile 2 Downlink Bit Rate Guaranteed. Values less than the currently selected value of QoS Profile 2 Downlink Bit Rate Guaranteed are rejected and an error message is posted. Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 64 kbps GPIB: CALL:SERVice:PSData:QOSProfile2:DOWNlink:BRATe[:MAXimum] QoS Profile 2 Uplink Bit Rate Guaranteed The value of this setting is signaled to the UE as the Guaranteed Bit Rate for Uplink and Guaranteed Bit Rate for Uplink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 2 Uplink Bit Rate Guaranteed must be less than QoS Profile 2 Uplink Bit Rate Maximum. Values greater than or equal to the currently selected value of QoS Profile 2 Uplink Bit Rate Maximum are rejected and an error message is posted. Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 1 kbps GPIB: CALL:SERVice:PSData:QOSProfile2:UPLink:BRATe:GUARanteed QoS Profile 2 Downlink Bit Rate Guaranteed The value of this setting is signaled to the UE as the Guaranteed Bit Rate for Downlink and Guaranteed Bit Rate for Downlink (extended) IEs in the Activate PDP Context Accept message. If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. QoS Profile 2 Downlink Bit Rate Guaranteed must be less than QoS Profile 2 Downlink Bit Rate Maximum. Values greater than or equal to the currently selected value of QoS Profile 2 Downlink Bit Rate Maximum are rejected and an error message is posted. Range: 1 to 63 kbps with resolution 1 kbps, 64 to 568 kbps with resolution 8 kbps, 576 to 8640 kbps with resolution 64 kbps, 8700 to 16000 kbps with resolution 100 kbps, 17 to 128 Mbps with resolution 1 Mbps, 130 to 256 Mbps with resolution 2 Mbps Default: 1 kbps GPIB: CALL:SERVice:PSData:QOSProfile2:DOWNlink:BRATe:GUARanteed

Page 13

Agilent Confidential Export Allowed

QoS Profile 2 Delivery Order If selected as On, the Deliver Order IE in the Activate PDP Context Accept message is signaled as With Delivery Order. If selected as Off, it is signaled as Without Delivery Order. Range: On, Off Default: On GPIB: CALL:SERVice:PSData:QOSProfile2:DORDer ON|1|OFF|0 QoS Profile 2 SDU Maximum Size If a value outside the allowed range is entered, the operation is accepted but the value is changed to the closest value within the allowed range. Range: 10 to 1500 bits with resolution 10 bits, 1502 bits, 1510 bits, 1520 bits Default: 1500 bits GPIB: CALL:SERVice:PSData:QOSProfile2:SDU:SIZE[:MAXimum] QoS Profile 2 SDU Error Ratio Range: 1E-2, 7E-3, 1E-3, 1E-4, 1E-5, 1E-6, 1E-1 Default: 1E-4 GPIB: CALL:SERVice:PSData:QOSProfile2:SDU:ERATio R1ENegative2| R7ENegative3|R1ENegative3|R1ENegative4|R1ENegative5| R1ENegative6|R1ENegative1 QoS Profile 2 Residual Bit Error Ratio Range: 5E-2, 1E-2, 5E-3, 4E-3, 1E-3, 1E-4, 1E-5, 1E-6, 6E-8 Default: 1E-4 GPIB: CALL:SERVice:PSData:QOSProfile2:RBERatio R5ENegative2| R1ENegative2|R5ENegative3|R4ENegative3|R1ENegative3| R1ENegative4|R1ENegative5|R1ENegative6|R6ENegative8 QoS Profile 2 SDU Error Delivery Range: No Detect, Delivered, Not Delivered Default: Not Delivered GPIB: CALL:SERVice:PSData:QOSProfile2:SDU:EDELivery NDETect| DELivered|NDELivered QoS Profile 2 Transfer Delay Range: 10 to 150 ms with resolution 10 ms, 200 to 950 ms with resolution 50 ms, 1000 to 4000 ms with resolution 100 ms Default: 100 ms GPIB: CALL:SERVice:PSData:QOSProfile2:TDELay

Page 14

Agilent Confidential Export Allowed

QoS Profile 2 Traffic Handling Priority Range: 1, 2, 3 Default: 2 GPIB: CALL:SERVice:PSData:QOSProfile2:THPRiority QoS Profile 2 Signaling Indication Range: Optimised, Not Optimised Default: Not Optimised GPIB: CALL:SERVice:PSData:QOSProfile2:SINDication OPTimised| NOPTimised

Multiple PDP Contexts Results

The following results are located on the IP Addressing Information screen (CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F5 IP Addressing Info). The following results are also located on the Multiple PDP Contexts Information screen (CALL SETUP, Call Control 3 of 6, F4 Data Channels, Data Channels 3 of 3, F4 Multiple PDP Contexts Info).

Current DUT IPv4 Address 2

This result provides the negotiated IPv4 address currently in use by the second primary PDP context. Range: or 0.0.0.0 to 225.255.255.255 GPIB: CALL:STATus:MS:IP:ADDRess2:IP4?

Current DUT IPv6 IID 2

This result provides the interface identity (IID) portion of the negotiated IPv6 address currently in use by the second primary PDP context. The complete DUT IPv6 address is formed by combining this reported IID with the link-local prefix or the selected IPv6 prefix. The 8960 assigns the IPv6 IID either by accepting a valid value proposed by the UE or by generating a random IID. Range: or 0000:0000:0000:0000 to FFFF:FFFF:FFFF:FFFF [19 char, 64 bit field], string-hex GPIB: CALL:STATus:MS:IP:ADDRess2:IP6:IID?

Page 15

Agilent Confidential Export Allowed

Set Up for Testing with Two Primary PDP Contexts on the 8960
This section briefly describes the sequence of steps to set up the 8960 and a UE on a PS data connection with two primary PDP contexts active. 1. On the 8960, choose whether to use IPv4, IPv6 or IPv4 and IPv6 addresses for the DUT with the two PDP contexts (DUT IP Version and DUT IP 2 Version settings). 2. Configure the two DUT IP addresses as desired (DUT IP Address and DUT IP Address 2 settings). 3. Configure the subnet mask of the 8960 to match that being used by the UE (Subnet Mask setting). 4. If desired, configure the QoS parameters for the two available profiles (QoS Profile 1 Setup and QoS Profile 2 Setup menus). 5. Select which of the QoS profiles to use with each PDP context (DUT IP Address 1 Primary QoS Profile and DUT IP Address 2 Primary QoS Profile settings). If you do not choose a profile (use the default setting of None, then the UEs requested QoS parameters are used to set up the connection. 6. If desired, configure the 8960 to ignore a PDP context activation request from the UE (Activate PDP Context Ignore State setting). 7. If desired, configure the 8960 to reject a PDP context activation request from the UE (Activate PDP Context Reject State and Activate PDP Context Reject SM Cause settings). 8. If desired, configure the APNs that can be accepted or rejected by the 8960 during a PDP context activation procedure (1st to 6th Access Point State, 1st to 6th Access Point Name, and 1st to 6th Access Point Name Reject SM Cause settings). 9. Select either 64k PS or HSUPA UL / HSDPA DL PS as the RAB for use with the PS data connection (GPRS Radio Access Bearer setting). 10. Configure any other UE or 8960 settings as desired for the PS data connections. 11. Initiate a PS data connection from the UE. The 8960 shows PDP Active in the Call Status box at the bottom of the screen. 12. Start sending PS data through the active PDP connection. This is usually done with a PC acting as a network server. 13. Use the data throughput monitor (open under the Instrument Selection button) to view the throughput being sent through the 8960. If you are using the HSPA RAB, you can also use the HSPA Information screen to view BLER, throughput, block counts and ACK/NACK counts (open under the Additional Screens menu). 14. Initiate another PS data connection from the UE. You can use the Multiple PDP Contexts Information screen or the IP Addressing Information screen to view the IP addresses of the two active PDP contexts. 15. Start sending PS data through the second active PDP connection. 16. The data throughput monitor shows the combined throughput of the two PDP contexts. The HSPA Information screen also shows the combined throughput and statistics of the two PDP contexts. 17. End the connections from the UE or by using End Call on the 8960.
Page 16