This section is only applicable to the lab application.
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.
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.
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).
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.
GPIB Command: CALL[:CELL]:APPLication:SESSion[:TYPE]
Manual Operation: How Do I Change Call Parameters?
Enhanced Test Application Protocol
Multi-carrier Test Application Protocol
Packet Data Network Emulation in the Test Set
Release A Physical Layer Subtype
C.S0029 Test Application Specification Description (TAP/ETAP/MCTAP)