Step 8: Disconnect The Mobile Station From The Bse; Background - Agilent Technologies 8960 10 Series Reference Manual

Step 8: Disconnect the Mobile Station from the BSE

Step 8: Disconnect the Mobile Station from the BSE

Background

See "Step 4: Establish an Active Link with Mobile Station" for a discussion of call connect/disconnect
synchronization.
Using the Call Connected State Query for Call Disconnect Synchronization
The call-connected-state query only hangs if the call is in a transitory state, otherwise it immediately returns
a 1 (Connected state) or a 0 (Idle state). At the start of a call disconnect process the call state is Connected.
Sending a call-connected-state query at the start of a call disconnect process could immediately return a one if
the query is satisfied before the disconnection process has started (that is, moved from the Connected state
into one of the transitory states). For correct call disconnect synchronization it is necessary that the query be
temporarily held off until after the call disconnect process has started. The call-state-change-detector is
provided which can be used to temporarily hold off the query from returning an answer until the appropriate
state change has occurred.
Using the Call Connected Arm Command for Call Disconnect Synchronization
The call-state-change-detector arm command is used by the control program to tell the test set that it is
expecting a change to the state of a call prior to initiating the state change. By first arming the
call-state-change-detector, then querying the call connected state, and then attempting a BS or MS call
termination, the call-connected-state query will hang until the disconnection operation begins and then
reaches a final (Idle or Connected) state.
However, if the change detector is armed and a call disconnection is attempted but the call state never
progresses from the Connected state, the call-connected-state query would hang forever. This could easily
happen if the mobile is badly broken, no one pushes the "end" button on the mobile, etc.
The call-state-change-detector time-out timer is provided which is used to prevent the call-connected-state
query from hanging forever.
Using the Call State Change Detector Time-out for Call Disconnect Synchronization
The call-state-change-detector time-out mechanism allows the test set to disarm the call-state-change-detector
which releases the call connected state query if it is currently hanging.
The time-out timer is started whenever the call-state-change-detector is armed or gets rearmed when already
armed. The duration of the time-out is set using the call-connected-time-out command and should be set to the
maximum amount of time the control program should wait between arming and the disconnect process to
begin. Once the process starts and the call state has moved into one of the transitory states the GSM defined
protocol timers take over and prevent the call state from staying in a transitory state forever.
If the timer expires while the call is in the Idle or Connected state, the call-state-change-detector is disarmed,
which releases the call connected state query if it is currently hanging.
If the timer expires while the call is in one of the transitory states it is ignored as, once in any transitory state,
the GSM-defined protocol timers limit the amount of time that can be spent in any transitory state.
196
S:\Hp8960\E1960A GSM Mobile Test Application\A.04 Release\Reference_Manual\Chapters\prog_prog_guide_step8.fm