You must purchase a feature license (E1966A-102 for release A and E1966A-103 for release B) from Agilent Technologies to enable this functionality in a licensed test application or order a special free feature license (E67066A-102 for release A and E6706A-103 for release B) from Agilent Technologies to enable this functionality in a licensed lab application. However, having the feature license E1966A-102 from Agilent Technologies does not grant you use of the Qualcomm® proprietary Release A functionality, and also having the E1966A-103 feature license from Agilent Technologies does not grant you use of the Qualcomm® proprietary Release B functionality. You must obtain consent from Qualcomm® to utilize this feature, as explained in the following statement:
NOTICE
THE DELIVERY OF THE AGILENT PRODUCT DOES NOT CONVEY A LICENSE NOR IMPLY ANY RIGHTS TO USE THE "1xEV-DO REVISION A" CAPABILITY CONTAINED IN THE AGILENT PRODUCT. SUCH USE REQUIRES THE EXPRESS CONSENT OF OR A SEPARATE LICENSE FROM QUALCOMM INCORPORATED. CUSTOMERS AND PRODUCT USERS SHALL BE SOLELY RESPONSIBLE TO OBTAIN SUCH CONSENT OR LICENSE FROM QUALCOMM INCORPORATED IN CONJUNCTION WITH THE USE OF THE "1XEVDO REVISION A" CAPABILITY.
Release A Concepts
1xEV-DO Release A uses 1.2288 Mcps as the spread rate and has the backwards compatibility with 1xEV-DO Release 0.
Release A supports three physical channel modes: Subtype 0 physical layer is the same as the original air interface in Release 0. Subtype 1 physical layer is very similar to subtype 0, but with support for variable rate R-Access Channel operation. Subtype 2 physical layer supports a new, high rate R-Traffic Channel along with increased data rates and support for smaller packets on the F-Traffic Channel (see
Release A Physical Layer Subtype
). Besides, Release A has a number of new applications:
-
The Multi-Flow Packet Application provides multiple octet streams that can be used to carry octets between the access terminal and the access network. See
Multi-Flow Packet Application Description
.
-
The 3G1X Circuit Services Notification Application allows cdma2000 messages to be tunneled through the 1xEV-DO air interface. Thus a dual mode mobile (cdma2000/1xEV-DO) can remain camped onto the 1xEV-DO channel and still send/receive circuit services messages. This allows the mobile to register, receive SMS messages, and receive pages from the cdma2000 system while physically listening to the 1xEV-DO network. This mode of operation eliminates the need for the Hybrid Mode where the phone must periodically tune to the cdma2000 1x to check for messages. See
Hybrid Mode
.
-
The new Multi-Mode Capability Discovery Application allows the network to discover if an AT supports such features as Hybrid Mode, Receiver Diversity or multiple TX and/or RX chains.
Release B Concepts
1xEV-DO Release B uses 1.2288 Mcps as the spread rate and has the backwards compatibility with Release 0 and Release A. To obtain increased data throughput, Release B can optionally support multiple combined RF channels. The following new protocols are added to support multi-carrier operation: Multi-carrier Forward Traffic Channel MAC Protocol, Multi-carrier Reverse Traffic Channel MAC Protocol and Subtype 3 Physical Layer Protocol (see
Release B Physical Layer Subtype
).
The new Subtype 3 Physical Layer Protocol supports multiple carriers in the forward and reverse links to increase data throughput. Moreover, with 64-QAM modulation, Subtype 3 Physical Layer Protocol supports new optional forward link rates up to 4.915 Mbps which makes the theoretical peak data throughput for three Forward/Reverse channels to be 3 x 4.915 Mbps = 14.745 Mbps in the forward Link and 3 x 1.8432 Mbps = 5.5296 Mbps in the reverse link.
Release B supports three multi-carrier multiplexing modes: No Feedback Multiplexing mode, Basic Feedback Multiplexing mode and the Enhanced Feedback Multiplexing mode. The test set only supports for the No Feedback Multiplexing mode in which each pair of forward/reverse channels operates as a stand alone pair. In the No Feedback Multiplexing mode, the feedback channels (R-DRC, R-ACK and R-DSC) for each forward channel are transmitted on a paired reverse channel using the same user long code sequences just as in Release A. See
Multi-carrier Multi-unit (MCMU)
for the Release B solution supported by the test set.
Operating Considerations
-
If a session is open in Active Cell operating mode, changing the protocol release results in a session re-negotiation (see
Session Negotiate State
). If a data connection is open, changing the protocol release results in the connection dropped with signaling. You will have to re-open the connection.
-
(
Lab Application Only
) 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
.
-
Not all Session Application Type are supported in all protocol release or physical layer subtypes. In Active Cell operating mode, if a protocol release that do not support a certain
Session Application Type
is selected, the selection will be rejected. See
Supported Session Application Type per Physical Layer and Protocol Release.
for which applications are supported in a certain protocol.
-
The test set currently supports protocol release A (1xEV-DO-A) and protocol release B (1xEV-DO-B) in IS-856 Test operating mode.
-
The test set does not support Subtype 1 Physical Layer protocol and Enhanced Control Channel MAC Protocol as defined in the C.S0024-A standard. See
Current Physical Layer Subtype and Associated Protocols
.
-
Due to a change in the signaling when 1xEV-DO Release A was introduced (the SCP Configuration Request contains a new field called "ATSupportedApplicationSubtypes" which was added in the 3GPP2 C.S0024 -A v3.0 standard), the test set running the E1966A Test Application version A.05.11 or E6706A Lab Application A.02.11 and earlier releases can not open a session with the 1xEV-DO Release A capable Access Terminals operating in 1xEV-DO Release 0 mode. The test set with these firmware versions cannot decode the new field and so a session failure will occur. Upgrading to newer firmware revisions will enable the test set to properly decode this parameter and will allow a session to be opened when the newer Release A phones are operating in Release 0 mode.