Data Channel Parameters

Last updated: April 27, 2013

This section is only applicable to the lab application.

Before an access terminal (AT) initiates a packet data connection either through the test set's internal PDSN or via the external PDSN (MOB-IP-SIM), the following data channel parameters must be correctly set.

• DUT IP Address

  Sets an IP address for the AT (see CALL:MS:IP:ADDRess[1]|2|3|4[:IP4] ). It is used to establish a packet data connection using test set's internal PDSN with the AT (see Packet Data Service Example Procedure (via Simple IP) ) or used by Ping functionality ( Ping the DUT from the test set ).

  This setting can be changed when in Data Connection states of Idle, Session Open, or Connected and is applied when the Session Application Type is set to Default Packet Application or M-Flow Packet Application or Enhanced M-Flow Pkt App and the External PDSN State is set to Off .

  When the External PDSN State is On , the DUT IP address is assigned by the external MOB-IP-SIM and the ping to a DUT functionality does not function.

  The DUT IP Address and the test set's LAN IP address should be unique and in the same subnet (see also IP Address Requirements ). The DUT IP Address setting is stored in nonvolatile RAM and will NOT be changed by a reset, power cycle operations.

  DUT IPv4 Address is only applicable when Session Application Type is Default Packet, MFPA, EMPA, or Alternate EMPA, External PDSN State is set to off, External EPC Connection Status is Disconnected, and DUT IP Version is IPv4 or IPv4+IPv6.

  If DUT IPv4 Address is changed when it is applicable and in use: if the Session Application Type is Default Packet, MFPA, or EMPA, any existing PPP data connection (A10 interface) and the connection between Testset and DUT will be ended with signaling.

  If the Session Application Type is Alternate EMPA (eHRPD), the current PDN connection will be kept. The new DUT IPv4 takes effect in the next PPP session negotiation after closing the current PDN connection, or when VSNCP resynchronization is conducted.

  DUT IPv6 Prefix is applicable when Session Application Type is Default Packet, MFPA, EMPA, or Alternate EMPA, External PDSN State is set to off, External EPC Connection Status is Disconnected, and DUT IP Version is IPv6 or IPv4+IPv6.

  If DUT IPv6 Prefix is changed when it is applicable and in use:

  • if the Session Application Type is Default Packet, MFPA, or EMPA, the PPP session and the data connection between Testset and DUT will be dropped. If there is an existing session established, the session will be maintained and the end Data Connection Status will be session open.
  • if the Session Application Type is Alternate EMPA (eHRPD), the current PDN connection will be kept. The new DUT IPv6 Prefix takes effect in the next PPP session negotiation after closing current data connection, or when VSNCP resynchronization is executed.
  • if DUT IPv6 Prefix is not applicable, the DUT IPv6 Prefix will be saved yet invalid.
     

  NOTE

  You should better change the DUT IP address and perform PDN resynchronization after establishing PDN connection, since there might be a competition case that a DUT IP address is changed when the PDN connection is in progress.

  In Use DUT IPv6 Prefix

  In Use DUT IPv6 Prefix is used to specify the IPv6 Prefix of the UE during an active IPv6 data connection. When there is no PDN connection with a negotiated DUT IPv6 address, the In Use DUT IPv6 Prefix is a blank string. Otherwise, the PDN connection will have an In Use IPv6 address, which should match the DUT IPv6 Prefix setting that was previously used to establish the PDN connection. After establishing PDN connection, you can change DUT IPv6 Prefix value different from the In Use IPv6 Prefix.

     

  NOTE

  If Multiple PDN connections are active, each In Use DUT IPv6 Prefix represents the IPv6 Prefix of the negotiated DUT IPv6 address for a PDN connection.

  ---

     

• Internal Mobile IP State

  Sets whether Simple IP or Mobile IP is used, if External PDSN State is set to Off , when a data connection is established between a DUT and the test set ( CALL:DATA:MIP:STATe ). Simple IP is used when the setting is set to Off , and Mobile IP is used when the setting is set to On .

  If Internal Mobile IP State is changed during a packet data call, no matter from On to Off or from Off to On , the data connection is dropped.

  When External PDSN State is set to Off , Internal Mobile IP State is in scope and if it is set to Off (default value),the test set works in Simple IP mode and no Mobile IP message is processed by the test set. When a data connection is started in this mode,

  • if a DUT is configured as "Simple IP only", the IP address proposed by the test set is accepted by the DUT and this address is used for the packet data transfer between the DUT and internet.
  • if a DUT is configured as "Mobile IP only", the PPP negotiation will fail and the data connection can not be established.
  • if a DUT is configured as "Mobile IP with Simple IP fall back", it can work when the test set in Simple IP mode, but there are two rounds of negotiation. Simple IP is used by the DUT in the second round of negotiation after Mobile IP registration fails in the firstround.

  If Internal Mobile IP State is in scope and set to On , the test set simulates a subset of the Mobile IP functionality, without any additional external device. When a data connection is started in this mode,

  • if a DUT is configured as "Simple IP only", it can not work in this mode and data connection can not be established.
  • if a DUT is configured as "Mobile IP only", MD5 authentication is performed after Mobile IP Registration Requestis received, if passed, DUT IP Address is sent to the DUT as Home Address. DUT uses this IP address for the packet data transfer between the DUT and internet.
  • if a DUT is configured as "Mobile IP with Simple IP fall back", it can work when the test set is in Mobile IP mode, and there is only one round of negotiation, just like the DUT configured as "Mobile IP only".

• Home Agent Shared Secret (Hex)

  Sets the secret key used at the Home Agent and Mobile during the MD5 Authentication procedure ( CALL:DATA:MIP:HAGent:SECRet ). Home Agent Shared Secret (Hex) setting must be equal to the MN-HA (Mobile Node - Home Agent) secret programmed in the mobile phone. When the test set receives a Mobile IP Registration Request (RRQ) message from a DUT, it authenticates the RRQ using the MN-HA shared key. A mismatched secret results in a response code = 131 (authentication failure) in the Mobile IP Registration Reply message,which causes registration failure.The test set supports both RFC2002 and RFC2002bis (SPI included) MN-HA authenticator calculation method. The test set can automatically identify the authentication method used by the DUT, and use the same method in forward Mobile IP messages. Home Agent Shared Secret (Hex) is only in scope when Internal Mobile IP State setting is On .

  According to RFC2002 and RFC1828, the length of MN-HA shared secret is up to 128 bits. Any particular key may be shorter. In test set, the type of this setting is defined as a 32-char hex string to support this flexibility(see For Example: How to configure Home Agent Shared Secret ). The number of hex digits in Home Agent Shared Secret (Hex) must be even number. If an odd number of hex digits are set, the user setting is rejected and an error "Operation rejected; Even number of hexadecimal digits is required" is generated.

• External PDSN State

  Sets whether to use the test set's internal PDSN or the external PDSN simulator (MOB-IP-SIM) ( CALL:DATA:PDSNode:EXTernal:STATe ). In addition, it also decides which group of settings work. If it is Off , settings related to the External PDSN, i.e. External PDSN IP Address , External PDSN TCP Port and External PDSN Connect Timeout , are of no effect. If It is On , settings related to test set internal PDSN, i.e. DUT IP Address , Internal Mobile IP State , and Home Agent Shared Secret (Hex) , are of no effect. If External PDSN State is changed to On during a mobile IP packet data call, the call will be dropped.

• External PDSN IP Address

  Sets an IP address for the external MOB-IP-SIM ( CALL:DATA:PDSNode:EXTernal:IP:ADDRess ).

  It should be set before turning the External PDSN State to On . If the External PDSN State is On , you can not change the External PDSN IP Address.

  The external MOB-IP-SIM's IP address and the test set's LAN IP address should be unique, but without the requirement to be within the same subnet. See also IP Address Requirements .

• External PDSN TCP Port

  Sets a TCP port for the external MOB-IP-SIM ( CALL:DATA:PDSNode:EXTernal:TCP:PORT ).

  It should be set before turning the External PDSN State to On . If the External PDSN State is On , you can not change the External PDSN TCP Port.

• External PDSN Connect Timeout

  Sets the maximum amount of time (1 - 19 seconds) that the test set will wait for an acknowledgment when trying to connect to the external PDSN (MOB-IP-SIM). See CALL:DATA:PDSNode:EXTernal:TIMeout[:CONNect] .

  If the External PDSN Connect timeout timer expires or the External PDSN rejects the connection request, the test set will generate an error. When External PDSN State is Off , this setting has no effect.

  The External PDSN Connect Timeout value is stored in nonvolatile RAM and will NOT be changed by a reset, power cycle, or save/recall operations.

     

  NOTE

  The External PDSN Connect Timeout is allowed to be set to the range of 0 to 19 seconds in the earlier E6706A firmware revisions (A.01 and A.02). However, you should not set the External PDSN Connect Timeout to zero. Otherwise, changing the External PDSN State to On will result in an error message indicating that the External PDSN is not available and the state will remain Off .

  If the value is set to zero and you boot up into a newer version of firmware (E6706A A.02.10 and above), the value stored in NVRAM will be changed to one second on power-up.

  ---

     

• DUT Primary DNS Server IP Address

  Set the Primary DNS Server IP Address for the DUT (see DUT DNS Server Addresses Setup ).

• DUT Secondary DNS Server IP Address

  Set the Secondary DNS Server IP Address for the DUT (see DUT DNS Server Addresses Setup ).

• Route 192.168.104.0/24 Traffic to DUT

  Set whether to use the router function of the DUT (see DUT Routing State ).

• Data Channel Dormancy Timer

  Sets the Dormancy Timer State and Dormancy Timer Value:

  • Dormancy Timer State . When Data Channel Dormancy Timer is set to ON and there is an active data connection with the DUT, the test set will monitor the activity of data channel. During the monitoring, if the test set detects no data flow or signalling transmission for the specified timer, it will close the physical connection to save channel efficiency. You can also set Data Channel Dormancy Timer to OFF to disable the function, then the Dormancy Timer takes no effect.
  • Dormancy Timer Value . After Data Channel Dormancy Timer is set to ON, you can set the maximum value of dormancy timer. So the test set will actively close the physical connection if no traffic is detected when the timer is timeout. The test set will be forced to Dormant state when dormancy timer expires and the following conditions are fulfilled.
    • The Dormancy Timer State is set to ON
    • The Data Connection Status is Connected
    • The Session Application Type is set to Default Packet , MFPA , EMPA , or Alternate EMPA
    • No traffic flow or signalling transmission is detected for the specified timer duration

    When the execution is completed, the DUT will receive a connection close message from the test set and the Data Connection Status will switch to Dormant . And the Dormancy Timer will reset to the initial specified value whenever acitve data flow or signalling transimission is detected, or the Data Connection Status is changed.

    You can change the Dormancy Timer Value whenever you want. Even if the timing has already initiated, the test set will automatically restart with the new timer value.