Data Channel Parameters

The parameters for selecting Service Option 33 (SO33)

If you select Service Option 33 (SO33), the following parameters can be configured to support the data channel function. The parameters you specified will be displayed on the Data Channel Information screen.

• SO33 Physical Channel Configuration
  

  There are four options for this setting:

  • FCH: Only fundamental channels are to be assigned. This is the default value to keep backward compatibility.
  • FCH + F-SCH: Only fundamental channels and the forward supplemental channel are to be assigned.
  • FCH + R-SCH: Only fundamental channels and the reverse supplemental channel are to be assigned.
  • FCH + SCH: Fundamental channels and supplemental channels are to be assigned, both forward and reverse.

  You can dynamically assign or unassign F-SCH or R-SCH when an SO33 data connection is established. (see CALL[:CELL]:SOPTion:SO33:CHANnel:CONFigure )

• F-SCH Data Rate

  The F-SCH data rate (see How Do I Set Up Data Channel Parameters? and CALL:SCHannel[:FORWard]:DRATe[:SELected] ) can be changed while maintaining an SO33 data connection (with F-SCH channel being assigned). The test set will inform the mobile station of the new data rate with signaling, and wait for a reply from the mobile station. When the mobile station acknowledges the new rate, the test set will change the over-the-air data rate. If the mobile station does not acknowledge the new data rate, the test set will display an error message which indicates that the mobile station has rejected a data rate change and the data rate will not be changed.

  
  See also Packet Data Service Data Rates .

• F-SCH Encoder Type (see CALL:SCHannel[:FORWard]:ENCoder )
• R-SCH Data Rate

  The R-SCH data rate (see How Do I Set Up Data Channel Parameters? and CALL:SCHannel:REVerse:DRATe[:SELected] ) can be changed while maintaining an SO33 data connection (with R-SCH channel being assigned). The test set will inform the mobile station of the new data rate with signaling, and wait for a reply from the mobile station. When the mobile station acknowledges the new rate, the test set will change the over-the-air data rate. If the mobile station does not acknowledge the new data rate, the test set will display an error message which indicates that the mobile station has rejected a data rate change and the data rate will not be changed.

  See Packet Data Service Data Rates

• R-SCH Encoder Type (see CALL:SCHannel:REVerse:ENCoder )
• DUT IP Address

  It is used to assign a valid IP address to wireless devices (see CALL:MS:IP ) when the External PDSN State is set to Off . It can be used to establish a packet data connection using Simple IP protocol (see Packet Data Service Example Procedure (via Simple IP) ) or used by Ping functionality ( Ping the DUT from the test set ).
  
  This setting has no effect when the External PDSN State is set to On where the DUT IP address is determined by the external MOB-IP-SIM. Moreover, the ping to a DUT functionality is disabled.

  The DUT IP Address and the test set's LAN IP address (see Configuring the Test Set's LAN ) 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 or by cycling the power.

• 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

  It specifies whether the PDSN simulation is provided by the external (MOB-IP-SIM) or internal (test set). See also Setting Considerations for External PDSN 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.

  • When the External PDSN State is set to Off , the test set's internal PDSN simulation is used and the mobile station's IP address is specified by the DUT IP Address . The mobile station's PPP connection is terminated by the test set, propagating the encapsulated IP packets directly to the test set's Ethernet interface.
  • When the External PDSN State is set to On , the external MOB-IP-SIM will provide PDSN service to the mobile stations, the test set will forward the PPP octets to the MOB-IP-SIM, which is responsible for actual termination of the PPP link. The MOB-IP-SIM will interpret all layers necessary to pass the end-to-end encapsulated IP packets directly onto the network (IP, UDP, MIP). See How Does Test Set Support Simple IP? for details.

  GPIB Command: CALL:DATA:PDSNode:EXTernal:STATe

• External PDSN IP Address

  It is used to specify the IP address of the external MOB-IP-SIM. You must specify a valid value (see CALL:DATA:PDSNode:EXTernal:IP:ADDRess ) before turning the External PDSN State to On . When the External PDSN State is Off , this setting has no effect.

  The IP addresses for the external MOB-IP-SIM and the test set should be unique, but without the requirement of being within the same subnet.

  • If the External PDSN IP Address is set to the same value as the test set's LAN IP address (see Configuring the Test Set's LAN ), an error "Configuration error; External PDSN IP address cannot be the same as instrument LAN address" will be generated and the new setting value is rejected.
  • When the test set's LAN IP address is set to the same value as the External PDSN IP Address, the External PDSN IP Address will be set to undefined.

  Changing the External PDSN IP Address while the External PDSN State is On will cause a data call (if connected) to be dropped and the External PDSN State to be Off .

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

• External PDSN TCP Port

  It is used to specify the TCP port of the external MOB-IP-SIM. You must specify a valid value ( CALL:DATA:PDSNode:EXTernal:TCP:PORT ) before turning the External PDSN State to On . When External PDSN State is Off , this setting has no effect.

  Changing the External PDSN TCP Port while the External PDSN State is On will cause a data call (if connected) to be dropped and the External PDSN State to be Off .

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

• External PDSN Connect Timeout

  It is used to set the maximum amount of time (1 - 19 seconds) 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 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 ).

Parameters for selecting SO33 (+F-SCH)

If you select SO33 (+F-SCH), the following parameters can be configured to support the data channel function and the effect is same as SO33 if SO33 Physical Channel Configuration is set to FCH+F-SCH. However, F-SCH can't be unassigned in this case.

Related Topics

Manual Operation: How Do I Set Up Data Channel Parameters?

Packet Data Service Data Rates

IP Address Requirements

Simple IP and Mobile IP