TAP/ETAP/MCTAP Data Connection Processing States Lifecycle

TAP/ETAP/MCTAP Data Connection Processing States Lifecycle

Last updated: July 22, 2008

As shown in the figure below, there are several key state transitions in the data connection processing lifecycle when the test set is configured to use the Test Application protocols (TAP/ETAP/MCTAP) (see Test Application Configuration ). For the key steps and messaging to establish a test data connection (TAP/ETAP/MCTAP), see TAP/ETAP/MCTAP Data Connection Call Flow .

TAP/ETAP/MCTAP Data Connection Processing Lifecycle

  1. Once the access terminal (AT) is powered on, it acquires the system and then moves into Idle state (see Idle State ).
  2. Before the AT can send or receive any test data packet, it must first open a session with the test set. The test set can then open a test data connection with the AT. The test set can't send data to the AT unless the AT has established a session. Only the AT can initiate a session. The AT initiates a session by sending a UATI Request (see UATI Request State ).
  3. The session is then configured through the negotiation of configurable attributes (see Session Negotiate State ). A temporary traffic channel connection is established for the session negotiation because the session negotiation is performed on a traffic channel connection. This temporary connection is closed after the session negotiation is complete. The temporary connection is initiated by the AT by simply sends a connection request (see Connection Request State ).
  4. Once the session negotiation is complete, the session is open (see Session Open State ). To change any of the configurable attributes for the session, the session must be renegotiated. The test set must be configured to TAP or ETAP (see Session Application Type for how to configure) prior to establishing a test data connection for AT's performance tests.
  5. Once this is complete, you can then start a TAP or ETAP data connection from the test set. Page the AT by pressing the F3 (Start Data Connection ) which directs the AT to send a Connection Request message (see Paging Procedure ).
  6. The connection configuration is then negotiated during the Connection Negotiate State , such as TAP/ETAP parameters used for a test environment (see C.S0029 Test Application Specification Description (TAP/ETAP/MCTAP) ).
  7. Once this is complete, the data connection is open (see Connected State ). Now, the AT and the test set can use the assigned traffic channel to send application traffic to each other.
  8. The AT may handoff to a new frequency because it is moving out of the current frequency coverage area, or perhaps the current frequency is heavily loaded and the network wants to balance the load (see Handoff State ).
  9. The connection may be closed by either the test set or AT (see Connection Closing State ).
  10. The session may be closed by either the test set or AT (see Session Closing State ).

Access Network (AN): The network equipment providing data connectivity between a packet switched data network (typically the Internet) and the access terminals. An access network is equivalent to a base station in a cdma2000 system.

The test set can emulate an AN so that the term of the test set and the AN are interchangeable throughout this User's Guide.

Access Terminal (AT): A device providing data connectivity to a user. An access terminal may be connected to a computing device such as a laptop personal computer or it may be a self-contained data device such as a personal digital assistant. An access terminal is equivalent to a mobile station in a cdma2000 system.


Related Topics

TAP/ETAP/MCTAP Data Connection Call Flow

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

Data Connection State Synchronization

Idle State

UATI Request State

Session Negotiate State

Session Open State

Paging State

Connection Request State

Connection Negotiate State

Connected State


Connection Closing State

Session Closing State