Session Application Type

Session Application Type

Last updated: August 17, 2009

This section is only applicable to the lab application.

   
NOTE
In the E1966A Test Application , the Session Application Type setting is not settable and implicitly fixed to the Test Application .

   

The 1x EV-DO system supports a number of different applications. Each application defines a unique set of procedures and capabilities.

The Session Application Type is a "Configurable Attribute" which is the Stream Protocol's StreamConfiguration, specifically the AssociatedFlow NN . The Session Application Type selected will determine what application the AN will negotiate on Stream X when a session is created. When a session is open, changing the Session Application Type results in a session re-negotiation (see Session Negotiate State for details).

Whether a certain Session Application Type is supported depends on the physical layer subtype which is dependent on the Protocol Rel . Look at the table below to see which Session Application Type selections are supported for each physical layer subtype.

Supported Session Application Type per Physical Layer and Protocol Release.
Internal Requested Physical Layer Subtype Supported Session Application Type
Subtype 0 Test Application (TAP)

Default Packet Application (DPA)

Subtype 2 Test Application (TAP)

Default Packet Application (DPA)

Multiflow Packet Application (MFPA)

Enhanced Multiflow Packet Application (EMPA)

Alternate Enhanced Multiflow Packet Application (AEMP)

Subtype 3 Test Application (TAP)

  • When the Test Application is selected, the test set is configured to either the Test Application Protocol (TAP), the Enhanced Test Application Protocol (ETAP) or the Multi-carrier Test Application Protocol (MCTAP). Which test application is being configured depends on the Protocol Rel and Release A Physical Layer Subtype or Release B Physical Layer Subtype settings as shown in the following table.

    Test Application Configuration

    When Session Application Type = Test Application

    Protocol Release

    Physical Layer Subtype

    Test Application Protocol

    0 (1xEV-DO-0)

    Subtype 0 (not settable)

    TAP

    A (1xEV-DO-A)

    Subtype 0

    TAP *

    Subtype 2

    ETAP

    B(1xEV-DO-B)

    Subtype 0

    TAP #

    Subtype 2

    ETAP #

    Subtype 3

    MCTAP

    Note:

    * C.S0029-A specifies that both the TAP and ETAP can operate with subtype 0 physical layer, but the test set only supports TAP operating with subtype 0 physical layer.

    # C.S0029-B specifies that the TAP, ETAP and MCTAP can all operate with subtype 0 physical layer, and the ETAP and MCTAP can operate with subtype 2 physical layer, but the test set only supports TAP operating with subtype 0 physical layer and ETAP operating with subtype 2 physical layer.

    The test application protocols as defined in the C.S0029 Test Application Specification (TAS) are mainly used for access terminal minimum performance tests in a factory/laboratory environment (test data packets are transmitted instead of real data).

    The C.S0029 TAS has evolved from release 0 (C.S0029-0) to release A (C.S0029-A) and further release B (C.S0029-B) to support the tests as required by the new air interface protocol release A (C.S0024-A) or release B (C.S0024-B). The C.S0029-A TAS defines three sets of test application protocols: Test Application Protocols (TAP), Enhanced Test Application Protocols (ETAP), and Broadcast Test Application Protocol (BTAP) whereas the test set only supports TAP and ETAP. The C.S0029-B TAS defines four sets of test application protocols: Test Application Protocols (TAP), Enhanced Test Application Protocols (ETAP), Broadcast Test Application Protocol (BTAP) and Multi-carrier Test Application Protocol (MCTAP) whereas the test set only supports TAP, ETAP and MCTAP. For details, see C.S0029 Test Application Specification Description (TAP/ETAP/MCTAP) .

  • The DPA as defined in the C.S0024 Air Interface Standard is an application layer protocol used in actual 1xEV-DO network. It provides Internet connectivity to access terminals for transporting real user data. See Packet Data Network Emulation in the Test Set for details.

    The test set currently supports Default Packet Application when Protocol Rel is A (1xEV-DO-A) and Release A Physical Layer Subtype is Subtype 2. In this configuration the test set supports to negotiate a Default Packet Application with the physical layer subtype 2 enabled, supports Radio Link Protocol (RLP) variable packet size required in Release A. And can achieve simultaneously 3.1Mbps/1.8Mbps peak data rate in the forward/reverse link.

  • The Multi-Flow Packet Application as defined in the C.S0024-A Air Interface Standard is an application layer protocol used in actual 1xEV-DO network. It provides multiple octet streams that can be used to carry octets between the Access Terminal and the Access Network. The test set supports Multi-Flow Packet Application only when Protocol Rel is A (1xEV-DO-A) and Release A Physical Layer Subtype is Subtype 2.

    The Multi-Flow Packet Application has all of the functionality of the Default Packet Application which is applicable to 1xEV-DO release 0 and release A including a single best effort default flow. If the AT doesn't request additional flows, then the functionality remains identical to Default Packet Application. See Multi-Flow Packet Application Description for details.

  • The Enhanced Multi-Flow Packet Application as defined in the C.S0063-A Air Interface Standard is an application layer protocol used in actual 1xEV-DO network. It is an application for real users data using multiple IP and RLP with Quality of Services (QoS) and has all of the functionality of the Multi-Flow Packet Application, but is further optimized for Voice over IP (VoIP).

  • The Alternate EMPA is used to enter the "eHRPD" mode (See eHRPD Support in the Test Set ). The packet application is EMPA with the Protocol ID for Flow00FlowProtocolParametersFwd and Flow00FlowProtocolParametersRev being set to 7 to indicate that VSNCP (Vendor Specific Network Control Protocol) and VSNP (Vendor Specific Network Protocol) protocols are used to support the eHRPD mode. The test set will only negotiate one personality for both the EMPA and Alternate EMPA.

    When Alternate EMPA is selected as the session application type, External PDSN must be set to Off in respect that only internal PDSN is used in the test set for eHRPD operation.

The Session Application Type is displayed on the Call Setup screen in the Application Configuration window in Active Cell operating mode.

Operating Considerations

  • The C.S0029-A specifies that the ETAP can operate with both the Subtype 0 and Subtype 2 physical layer protocols. However, the test set only supports TAP operating with subtype 0 physical layer and ETAP operating with subtype 2 physical layer. See Test Application Configuration .
  • The C.S0029-B specifies that the MCTAP can operate with the Subtype 0, Subtype 2 and Subtype 3 physical layer protocols. However, the test set only supports MCTAP operating with subtype 3 physical layer. See Test Application Configuration .
  • The test set does not support Broadcast Test Application Protocol (BTAP) as defined in the C.S0029 standard.
  • Other than that Call Limit Mode is on, Session Application Type can be changed at any time. If a session is established, the session will be re-negotiated. If a connection is established the connection will be closed as a result of the session negotiation and will not be re-established automatically.

Related Topics


GPIB Command: CALL[:CELL]:APPLication:SESSion[:TYPE]

Manual Operation: How Do I Change Call Parameters?

Test Application Protocol

Enhanced Test Application Protocol

Multi-carrier Test Application Protocol

Packet Data Network Emulation in the Test Set

Data Channel

Protocol Rel

Release A Physical Layer Subtype

C.S0029 Test Application Specification Description (TAP/ETAP/MCTAP)