This section is only applicable to the lab application.
The test set can support up to a maximum of four primary PDP Contexts at present. Since each primary PDP Context has its own IP address and QoS Profile, there are four DUT IP addresses and four sets of QoS Profiles that can be configured in the test set. You can set the reliability class, traffic class and traffic handling priority of each QoS Profile.
You can enter up to a maximum of four DUT IP addresses for your DUT, each one associates with a PDP Context. All DUT IP addresses are constrained to be unique and within the same IP subnet as the LAN address of the instrument. Any attempt to enter a DUT IP address outside this range is rejected and an error message generated. If the LAN address of the instrument is changed to a value outside the current subnet then all configured DUT IP addresses are cleared and an error message generated. Similarly if the subnet mask is changed to a value that makes any DUT IP address is outside the same subnet as the instrument LAN address, the DUT IP addresses are cleared and an error message generated.
These settings are non-volatile (they persist across partial and full presets and power-cycling the test set).
See IP Address Requirements for more information.
GPIB command: CALL:MS:IP:ADDRess[1]|2|3|4
As part of the PS data call setup procedures, the MS 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 MS can request either the Primary DNS Server address or the Secondary DNS Server address or both. If the MS 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 MS, returns an error, and then proceeds with the PDP Context Activation. If the MS 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 MS.
These settings are non-volatile (they persist across partial and full presets and power-cycling the test set).
You can set the Primary and Secondary DNS Server IP Address for the DUT. The GPIB command to set the Primary DNS Server IP Address is CALL:MS:DNSServer:PRIMary:IP:ADDRess . Then GPIB command to set the Secondary DNS Server IP Address is CALL:MS:DNSServer:SECondary:IP:ADDRess .
During the PS data call setup procedure, the UE asks the network for one or more IPv4 address of the P-CSCF in the Protocol Configuration Options IE of the PDP Context Activation message. The test set supports two P-CSCF IPv4 addresses. If the UE requests more than two P-CSCF IPv4 addresses, the addtional P-CSCF IPv4 address requests are ignored.
GPIB command: CALL:MS:CSCF:PROXy:IP:ADDRess:IP4 , CALL:MS:CSCF:PROXy:IP:ADDRess2:IP4 .
For each DUT IP Address one Primary PDP context and up to three secondary PDP contexts are available in the test set. You can set the QoS Profile for each PDP context. Upon receiving the Activate PDP Context Request message from the DUT, the test set sends the Activate PDP Context Accept message to allocate a QoS Profile to the DUT. The allocation of QoS Profile is based on the following rules:
Insufficient Resources
.You can configure the Override Requested Reliability Class, Subscribed Reliability Class, Traffic Class and Traffic Handling Priority for each QoS Profile.
If the MS requests a particular reliability class in its Activate PDP Context Request message, you can configure the test set to override this request and instead, assign the reliability class you have chosen. This value is sent only if the state of the Override Requested Reliability Class parameter is turned on.
You can use CALL:PPRocedure[:QOSProfile[1]|2|3|4]:PDPContext:AACCept:QOService:RCLass:ENForce:STATe to set the Override Requested Reliability Class state, CALL:PPRocedure[:QOSProfile[1]|2|3|4]:PDPContext:AACCept:QOService:RCLass:ENForce:VALue to set the Override Requested Reliability Class value, use CALL:PPRocedure[:QOSProfile[1]|2|3|4]:PDPContext:AACCept:QOService:RCLass:ENForce:[SVALue] to set the state and value simultaneously.
Instead of requesting a specific reliability class, the MS can also request its subscribed class within the request message. You can specify the subscribed class to be sent to the MS. This value is sent only if the state of the Override Requested Reliability Class parameter is turned off.
The GPIB command to set Subscribed Reliability Class is CALL:PPRocedure[:QOSProfile[1]|2|3|4]:PDPContext:AACCept:QOService:RCLass:SUBScribed .
You can specify the Traffic Class for each QoS Profile. Traffic classes have increasing priority according to the order Background, Interactive, Streaming and Conversational. Conversational class is for traffic which is very delay sensitive while background class is the most delay insensitive traffic class.
Traffic Class is sent to MS if an Activate PDP Context request is accepted.
The GPIB command to set Traffic Class is CALL:PPRocedure[:QOSProfile[1]|2|3|4]:TCLass .
Traffic Handling Priority specifies the relative importance for handling of the SDUs (Service Data Units) for each QoS Profile. Traffic Handling Priority is ignored if the Traffic Class is conversational, streaming or background.
Traffic Handling Priority is sent to MS if an Activate PDP Context request is accepted.
The GPIB command to set Traffic Handling Priority is CALL:PPRocedure[:QOSProfile[1]|2|3|4]:THPRiority .
Packet Flow Contexts are optionally supported in the network to manage the Quality of Service (QoS) between multiple Packet Flows. A Packet Flow is used to identify the transfer through a collection of one or more Logical Link Control (LLC) layer Service Access Points (SAPs) which are governed by a similar Quality of Service (QoS). Individual Packet Flows are uniquely identified by a Packet Flow Identifier (PFI) value which is determined by the Serving GPRS Support Node (SGSN) in the core network. A Packet Flow Context (PFC) is essentially the information structure associated between the Base Station Subsystem (BSS) and the SGSN associated with a specific Packet Flow, whereby the PFC is addressed by a Packet Flow Identifier (PFI) value assigned by the SGSN.
The PFI associated with a particular packet flow between the network and the DUT is initially provided by the SGSN during PDP Context establishment. Multiple PDP Contexts may share or be associated to the same PFC and the PFC can be used to determine whether a common physical resource may be used to multiplex data from multiple PDP Contexts or whether individual resource/TBF are required for different PDP Contexts.
The Packet Flow Identifier can be set as one of the following values:
Before using the PFI parameter, you must set the Packet Flow Context State to ON, the GPIB command to set the Packet Flow Context State is CALL[:CELL]:PFContext[:STATe] . The GPIB command to set the PFI for each QoS Profile is CALL:PPRocedure[:QOSProfile[1]|2|3|4]:PFI .
The PDP Context Modification procedure is not supported in the test set, once a PDP context has been established changing the associated QoS Profile shall result in the deactivation of the PDP context.